Retailer dispatch

Tesco does not care if your dispatch is correct.
They care if it's correct in their format.

Every Irish food producer learns this the hard way. Your dispatch is technically right — accurate weight, correct batch, valid COA. But it is not in Tesco's exact format, with the right block layout, the right SSCC, the right code on the right line. Result: pallet rejected at depot, your phone rings, somebody drives over. Keystone ships with retailer-specific templates for the formats that actually matter to Irish producers.

Live templates for Tesco IE, Lidl, M&S, SuperValu, Centra, SPAR, Musgrave
Customer SKU mapping for retailer private-label codes
Per-retailer dispatch note + pallet label + COA combinations
Founding partner ships to nine retailer chains across multiple markets

Book a discovery call See pricing

The retailer dispatch reality

Every multiple has its own format — and its own patience.

Tesco wants a specific dispatch-note block. Lidl wants a specific barcode pattern on the pallet. M&S wants the EAN-13 and customer SKU positioned a certain way. SuperValu and Centra share a Musgrave-group format with their own quirks. SPAR has its own EDI-adjacent format. Each retailer treats deviations from its template as a rejection, not a suggestion. Your team learns these rules by getting pallets rejected — Keystone gets your team out of that loop.

What you get

Right format, right code, right scan, every time.

Per-retailer dispatch note

The retailer template applies automatically based on the customer record — no human selection of templates.

Per-retailer pallet label

SSCC, GS1-128 and EAN-13 positioned exactly as the retailer expects. Test-scanned in-system before printing.

Per-retailer COA

Some retailers require a COA in their specific layout. Templates per retailer; per-batch values pulled from QC.

Customer SKU translation

Your internal code maps to the retailer's private-label code automatically. The dispatch note shows both. No mental translation at the dock.

Audit trail per dispatch

Every dispatch logged with the exact template version used, the user, the time, the destination email.

Where this sits

Production layer next to your accounts package.

Keep AccountsIQ, Sage or QuickBooks. Keystone owns retailer dispatch end-to-end — order, batch allocation, dispatch note, pallet label, COA, post-dispatch invoice publish to your accounts package.

FAQ

Questions buyers actually ask.

What if a retailer changes its template?

Update the template in the designer. Effective immediately. No code release, no support ticket.

Can we add a retailer that's not in your default list?

Yes — the designer handles any retailer. Our default list is the Irish multiples and Musgrave-group retailers; international retailers are added via the same designer.

Does this include retailer EDI?

Manual upload to retailer portals works out of the box. Full EDI integrations are scoped bolt-ons — typical fee €3,500–€8,500 per retailer.

What about retailer-specific labelling auditors?

Some retailers require periodic label-format audits. Keystone keeps the version history of every template you have ever used — straight evidence.

Can dispatch staff do this themselves?

Yes — once configured, dispatch is point-and-click. Trained dispatch staff run it without IT involvement.

Ready to see if Keystone fits your floor?

20-minute discovery call. No sales pitch. Written scope within 48 hours if we fit — referral to someone better if we don't.

Talk to us

Tesco does not care if your dispatch is correct.They care if it's correct in their format.