Every retailer has its own code for your product.
Stop translating between them in your head.

Your internal code for a 1.4 kg blue wheel might be CB-BLUE-1.4. Tesco calls it TES-FBWHL14-742. SuperValu calls it SVAL-CB-14. M&S has its own EAN. Aldi has another one. Multiply that by 40 SKUs and 8 retailers and the translation work becomes a full-time job for one person — usually the same person who runs dispatch. Keystone maps every code automatically. Search either way; the system translates.

• Bidirectional mapping between your internal code and customer codes
• Search by your code OR by any customer code
• EAN-13 / GTIN handling for retailer barcode requirements
• Bulk import from supplier specs or EDI catalogues

One person becomes a translation service.

If customer SKU translation lives in someone's head — usually the dispatch lead or a long-serving QA team member — you have created an operational risk. They go on holiday, dispatches lurch. They leave, you lose institutional memory. They make a typo, a Tesco pallet gets rejected. None of this is their fault — it is a workflow that should not live in human memory in the first place.

Codes are first-class data, not spreadsheet cells.

Forward trace by customer code, not just your code.

When a retailer complains 3 weeks after dispatch, they will quote their code, not yours. Keystone resolves that to the right batch chain immediately — the same way you would resolve a complaint quoted in your own code. Forward trace works both directions: your internal trace and the retailer-facing trace return the same chain.

Questions buyers actually ask.