SKU Mapping

Translate product codes automatically — so every partner sees the SKU they expect.

Your internal SKU rarely matches a retailer’s item code. That’s where errors start: rejected orders, incorrect dispatch data, invoice disputes, and endless “which SKU is this?” emails.

SKU Mapping aligns your product identifiers with each trading partner’s codes, keeping documents accurate from order to invoice.

The problem it solves

Product codes create friction when partners use different identifiers:

• partner SKUs don’t match your internal SKUs

• GTIN/EAN and supplier part numbers are inconsistent

• product updates aren’t reflected across every partner

• orders fail validation due to missing or incorrect item codes

• despatch and invoice references don’t line up with goods-in

SKU Mapping keeps product identity consistent across your whole network.

What SKU Mapping does

Map internal SKUs to partner item codes

Maintain mappings per trading partner so outgoing documents always use the correct identifiers.

Reduce rejects and operational errors

Avoid common failures caused by mismatched product references and missing item codes.

Improve goods-in and fulfilment accuracy

When item identifiers match what the partner expects, scanning and reconciliation becomes smoother.

Keep product data manageable at scale

Manage mappings across multiple partners without building one-off workarounds for each new connection.

How it works

1) Store SKU relationships
Link your internal SKU to partner-specific identifiers (e.g. retailer SKU, GTIN/EAN, supplier part number where relevant).

2) Apply mappings automatically
As documents are sent/received, XEDI uses mappings to translate item references correctly.

3) Validate before delivery
Catch missing mappings early, before a document is sent and rejected.

4) Maintain and update cleanly
Update mappings as products change, new ranges launch, or partners revise their item files.

Key benefits

• Fewer rejects: reduce failures caused by incorrect item codes

• Less manual work: stop chasing product code mismatches

• Smoother fulfilment: improve goods-in and order accuracy

• Cleaner invoicing: reduce invoice disputes linked to item references

• Scales with growth: add partners without multiplying SKU chaos

Best-fit use cases

• Suppliers selling into multiple retailers or marketplaces

• Businesses with frequent product range changes

• Teams dealing with partner-specific SKUs and item files

• Operations struggling with goods-in mismatches

• Finance teams seeing disputes from incorrect product references

FAQ

Is SKU Mapping per trading partner?
Yes — mappings can be maintained per partner so each customer sees the identifiers they expect.

Does this work with GTIN/EAN codes?
Yes — GTIN/EAN can be included as part of the mapping approach, depending on the document requirements.

What happens if a SKU isn’t mapped yet?
You can surface missing mappings as exceptions so they’re fixed before documents are sent or before fulfilment is affected.

Does SKU Mapping help with invoice disputes?
It can. Many invoice queries start with “that item code doesn’t match our records”. Correct identifiers reduce that friction.