Cross-reference registry + safe replay
EDI mapping software that remembers the business identity behind every code
Resolve partner-specific party, store, warehouse, product and operational codes to workspace-owned canonical records—then replay a held document only after an exact mapping is approved.
Direct answer
Direct answer
EDI mapping software needs two distinct controls. A source recipe maps columns or paths to canonical document fields; an identity registry maps partner values such as customer codes, store numbers, warehouse aliases, GLNs, Peppol participant identifiers, SKUs, GTINs, EANs and article numbers to one workspace-owned party, location or product. Shipment Sentry uses exact, effective-date-aware matches with partner-specific precedence. Missing or conflicting values remain unresolved instead of selecting the first record.
Why mapping needs a controlled workflow
A field map says where a value came from; it does not prove what that value means. Keeping identity cross-references separate allows the same canonical product or warehouse to carry multiple buyer, supplier and route-specific aliases without adding another customer-shaped table. It also creates a durable approval trail: source hash, mapping recipe, partner-pack version, generated output hash, validation findings and release actor remain connected.
What the control should check
- 01Keep parties, locations and products as canonical workspace records rather than retailer-shaped duplicates.
- 02Store identifiers with scheme, scope, effective dates, verification evidence and packaging level where applicable.
- 03Treat EAN and UPC as members of the GTIN family; validate the GS1 check digit before approval.
- 04Apply a partner-specific exact match before a global workspace alias, and quarantine multiple active matches.
- 05Keep UOM, tax, carrier, service, Incoterms and document-purpose translations in approved code lists.
- 06Retain held source bytes encrypted, replay from their immutable hash, and validate the exact generated output before release readiness.
Working example
PARTY CUSTOMER-ACME
GLN / GLOBAL 9501234567893
PARTNER_ALIAS / AMAZON VENDOR-01842
LOCATION WH-JHB-01
WAREHOUSE_CODE / GLOBAL JHB1
STORE_CODE / WALMART-US 00421
PRODUCT SKU-104
GTIN / CASE 04012345678901
PARTNER_ARTICLE / ACME A-7782
held source hash → approved exact recipe → output hash → validation → release_readyThe identifiers are illustrative. GS1 keys require valid allocation and check digits; Peppol participant identifiers require the correct scheme; partner aliases remain scoped to their route and agreement.
Failure modes worth catching
- A warehouse and a retail store share the same unqualified location code.
- One barcode column silently mixes each, case and pallet GTINs.
- An expired partner article alias continues to resolve after a catalogue change.
- A corrected mapping overwrites the source or the output version used for an earlier release.
Put it into the dispatch workflow
- 1Create canonical parties, locations and products with readable internal codes.
- 2Attach verified global or partner-scoped identifiers and effective dates.
- 3Approve operational code translations for the receiving route.
- 4Review the exact source-layout proposal attached to a held API, email or SFTP document.
- 5Replay from encrypted immutable input, validate the generated bytes, then explicitly release the cleared version.
Questions
Implementation answers
Should customer, supplier and partner codes use separate tables?
Usually no. Store one canonical party with roles such as buyer, supplier, customer or carrier, then attach scheme- and partner-scoped identifiers. This avoids duplicate organizations that drift apart.
Should stores and warehouses be separate?
Use one canonical location model with roles such as store, warehouse, distribution centre, ship-from, ship-to and bill-to. A location may have a GLN plus different partner store or warehouse aliases.
Is an EAN or barcode the same as a product?
No. A product can have several GTIN-family identifiers for each, inner, case or pallet packaging. Barcode symbology is how an identifier is rendered; serial, lot and SSCC values belong to physical instances or logistics units.
What happens to a document while its mapping is missing?
For API, authenticated email and SFTP intake, Shipment Sentry stores the source encrypted with its content hash and reason. Approving the exact proposed recipe replays that input, saves a new immutable output version and validates it before the document can become release-ready.
Does the resolver use fuzzy matching?
No. Production resolution is exact and fail-closed. Partner scope takes precedence over a global alias; no match is unresolved and more than one active match is a conflict.
Sources and limits
Reviewed 2026-07-20. Public references cannot establish every partner-specific rule. Current implementation guides and agreements remain controlling.
Keep investigating