Definition
A product identifier crosswalk is a maintained mapping between identifiers in different systems and the commerce entity they represent. It can connect a warehouse SKU, supplier code, and channel variant ID to one internal variant. Each mapping needs source context: the same text code in two systems does not necessarily identify the same item.
Why It Matters
- Unmatched identifiers can split one product across reports, while incorrect merges can attach returns or stock to the wrong variant.
- Product names are useful matching evidence but can omit size, color, revision, or pack count. Similar wording alone is insufficient for an operational join.
- A Commerce Intelligence OS needs entity identity before it can connect catalog knowledge, order lines, and return outcomes reliably.
How It Works
- List source namespaces and identifier types. Define whether the target is a product family, sellable variant, pack, or individual serialized unit.
- Build proposed mappings using authoritative source records and validated attributes. A GTIN can provide trade-item identity evidence; retain the packaging level it identifies.
- Separate exact equivalence from relationships such as contains or replaces. Route ambiguous matches for review instead of merging them silently.
- Version accepted mappings with effective dates and evidence. Validate joins for missing matches and unexpected row multiplication, then monitor source-code reuse or remapping.
Ecommerce Example
Context: Illustrative example: a storefront code and a warehouse SKU describe the same blue shirt in size M, while a supplier carton code represents twelve such shirts.
Recommended move: Map the first two to the sellable variant. Represent the carton through a contains relationship and quantity, rather than treating one carton as one shirt.
Why it matters: Order and return analysis can join at the correct entity level. This is an architectural example, not a claim that any connector is already deployed.
iKawn Framework
Identify
The iKawn ontology framework distinguishes product, variant, pack, and unit.
Map
Retain the source namespace and evidence behind each crosswalk.
Validate
Check join coverage, ambiguity, and accidental duplication.
Maintain
Preserve mapping history so historical commercial evidence remains interpretable.
Concise Summary
A crosswalk connects identifiers without flattening their meaning. Source namespaces, entity levels, and versioned evidence make product joins more reliable.