Separate a stable internal identity from the reference people use in conversation. Names and labels can change without making a customer, job, or order a different record.
Prepared with AI assistance. These are practical scoping recommendations; examples are illustrative, not client results.
Understand human references
Staff may use a job number, customer code, or branch prefix to find work. Preserve useful conventions where practical, but document what they mean and whether they can change. A readable reference helps communication; it should not force the system to confuse two records when a label is reused.
Map external identities
Connected systems may each assign their own identifier. Keep those references associated with the same business record and specify which integration owns each link. Do not assume that matching display numbers across systems implies a shared identity, especially after imports or account changes.
Plan corrections and merges
If a customer is renamed or two records are linked, decide which identifiers remain searchable. Preserve enough history for old documents and staff notes to find the correct record. Avoid changing identity merely to make an exported list look cleaner.
Test real retrieval
Search using a current name, an old reference, and an external system's identifier. Verify that users reach the intended record without ambiguity. Then test two similarly named customers. The identity model should support dependable operations and integration while giving people practical references they can recognize and communicate.