Two identities: one the customer sees, one the database uses.
Status at ebf7cf0: Aligned — order numbers are assigned at dispatch and existing-customer suffixing is implemented.
| Identity | Purpose |
|---|---|
| Hidden stable database ID (UUID) | Every relationship. Never displayed. |
| Staff/customer-facing reference | Display only. PREFIX-YYMMDD-XXXX, four uppercase hex characters. |
Examples: CUS-260816-A12F · ORD-260816-B34E · JOB-260816-C56D · ITM-260816-D78C · PMT-260816-E90A.
Changing an authorised display reference never breaks relationships. Job Logs, snapshots, payments and refunds link through the hidden key, not the display number.
Order numbers run per trade with a branch variant — AC, ING, JING, PST. The other twelve trades are not yet set.
The Johor running number continues from the old system. AppSheet reached JSM0170, so the module starts at JSM0171.
Story. As staff, I want an Order Number created only when the work is first dispatched, so that incomplete drafts do not consume customer references.
Acceptance. The number is unique and uses the configured branch and service sequence.
Story. As the system, I want later Orders for the same customer to reuse the base and add the next available letter suffix, so that related references are recognisable.
Acceptance. Suffix allocation is atomic and cannot duplicate under concurrency.
Story. As the system, I must never reuse a cancelled or soft-deleted number, so that external documents remain trustworthy.
Acceptance. Restoration returns the original number and relationships continue to use stable IDs.
Order numbers are assigned at dispatch and existing-customer suffixing is implemented.
The older EB-YYYY-NNNNN save-time scheme is superseded.
Applying Reference IDs consistently across every record type, while keeping UUID relationships, remains a P1 item.
New to these terms? See the Glossary.