Customer work, connected.

Help & supportMyAccount
Module setup, access and architecture

Understand Delivery Note reference numbering

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Explain the generated `DN-YYYYMMDD-INV{id}-sequence` reference and collision fallback.

Audience: Delivery operations and auditorsPermission: Delivery Note: ViewModule v1.0.0
Jump to steps
Where to goAdmin Area → Delivery Note → Open note → Reference

What this guide helps you do

Explain the generated `DN-YYYYMMDD-INV{id}-sequence` reference and collision fallback. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.

Follow these steps

  1. Go to a delivery note detail page.
  2. Read the generated reference.
  3. Compare the date and source invoice ID with the record.
  4. Use the reference when tracing email, PDF and event evidence.

Fields and options

  • Configurable prefix, default `DN`
  • Creation date in `YYYYMMDD`
  • Source invoice ID
  • Four-digit sequence from 0001 to 9999
  • Eight-character token-derived fallback after sequence exhaustion

Rules and limits

  • Reference generation checks uniqueness before insert.
  • The reference has a unique database index.
  • Changing the prefix affects future generated references only; the supplied code has no prefix settings screen.

Check it worked

  • Every note receives an attributable, unique reference linked visibly to its invoice.

Safety checks and troubleshooting

  • Do not overwrite references directly in the database.
Stay within the supported flowDo not force database values, expose secure tokens, bypass permission checks, replace a stored signature or invent a status or interface that the supplied code does not implement.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page