Cross-reference partner codes
Lesson 13 of 21 6 min read
When EDI partners and marketplaces use their own product codes, build a cross-reference table and get it into Supply Lens before go-live.
Retailers, wholesalers and marketplaces often have their own codes for your products, and you can't ask them to change. Supply Lens handles this with cross-references: records that translate an external code into your internal SKU on every Document. This lesson shows you how to prepare them.
Build the cross-reference table
- Get the partner's product code list. For EDI, this is usually part of the setup documentation the partner provides. For Amazon, it's your Merchant SKU list.
- Build a table mapping each external code to your internal SKU.
- Get the cross-references into Supply Lens before the Integration goes live. The help centre recommends contacting Support to have them configured.
A simple table is all you need:
| Partner | Partner's code | Your SKU | Notes |
|---|---|---|---|
| Greenleaf Wholesale | GL-44871 | HT-HOUSE-250 | Ordered by the case of 6 |
| Greenleaf Wholesale | GL-44872 | HT-DECAF-250 | Ordered by the case of 6 |
How cross-references relate to master data
In the Master data course you added partner codes to Products as identifiers, such as a Buyer Product Code scoped to the partner's Party, and barcodes such as GTIN-14. Those identifiers are how Supply Lens recognises a partner's code on a Document and links it to your Product. Scoping a partner's code to its Party means it only applies on that partner's Documents.
If you maintain many partner codes, a Product export and import lets you load them in bulk from your table.
Which identifier type?
Which identifier type a partner's code should use depends on the Integration and what the partner sends. Confirm this with Support when you set up an EDI or marketplace Integration.
Don't forget units
Partners who use their own codes often order in cases or outers too. While you're building the table, note the pack size each partner orders in. Each needs a conversion on the Product, as covered in the Master data course, or orders in that pack size will fail.
Greenleaf's cross-references
Greenleaf sends a catalogue of 40 product codes with Hilltop's SKUs alongside. Priya:
- Checks every Hilltop SKU in the list exists in Unleashed (two are old codes; she corrects them).
- Adds a "pack size" column: all cases of 6, except the 1kg lines in cases of 4.
- Sends the table to Support with her EDI setup, and loads the codes onto her Products as Buyer Product Codes scoped to Greenleaf.
- Confirms each Product has a conversion for its case size.
One code, one product
Two Products claiming the same partner code at the same scope make that code ambiguous, and Documents using it will error. Check your table for duplicates before loading it.
Recap
- Use cross-references for partners whose codes you can't change, such as EDI partners and marketplaces.
- Get the partner's code list, build a table to your SKUs, and get it into Supply Lens before go-live.
- Partner codes live on your Products as identifiers, scoped to the partner where they're partner-specific.
- Note each partner's pack sizes and make sure the conversions exist.
- Check for duplicate codes before loading.
Quick guides for this topic
Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.