By PoppeloPublished Updated
A customer SKU cross-reference maps the part number a specific buyer places on a purchase order to the item your business uses internally. The mapping should be customer-scoped, traceable, and refused when one buyer code could resolve to more than one valid item.
Scope aliases to the customer who uses them
The same short code can mean different products to different buyers. Store the buyer identifier, the raw buyer part number, the internal catalogue item, and any unit or pack-size context together rather than treating the alias as global.
Keep stable source-system identifiers alongside readable names. Names and descriptions can change; a source identifier helps preserve the relationship without pretending that an external standard identifier and a customer alias serve the same purpose.
Make ambiguity a review outcome
Exact matches are useful only when the mapping is active and the surrounding quantity and unit make sense. Multiple candidates, inactive catalogue items, and conflicting pack sizes should stop automatic approval.
When a reviewer corrects a match, preserve the source line and decision. Poppelo can use repeated correction evidence to propose a rule, but a person activates it and can later retire it.
A six-step cross-reference maintenance loop
Identify the buyer
Resolve the customer before applying customer-specific part-number vocabulary.
Normalize without destroying evidence
Trim predictable spacing or case differences while retaining the original line for review and audit.
Match within customer scope
Look for an active mapping tied to that buyer and catalogue source rather than a global text coincidence.
Validate item and unit context
Check that the internal item is active and that quantity, unit, and pack expectations do not conflict.
Review ambiguous or missing mappings
Let a reviewer choose, correct, or reject instead of silently selecting the first candidate.
Govern the mapping lifecycle
Record approval evidence, monitor later corrections, and retire mappings when the source catalogue or buyer vocabulary changes.
| Observed state | Workflow decision | Reason |
|---|---|---|
| One active customer-scoped mapping with compatible unit context | Use the proposed item, subject to remaining validation | The mapping and order context agree |
| More than one valid item or conflicting pack size | Send to review | Text alone does not select a safe commercial result |
| Inactive or missing catalogue item | Hold or reject | A historical alias must not silently reactivate an unavailable item |
What this method does not establish
- Cross-references do not resolve missing quantities, prices, units, or other required order fields.
- Global aliases can create false matches when different customers reuse the same code.
- Saved corrections are evidence for customer context and proposed rules, not proof that future documents will always be interpreted correctly.
Primary references
- GS1 General Specifications
Primary standard for globally unique GS1 identification keys; customer-specific aliases still require their own governed mapping.