Dispatch notes the retailer will actually accept.
Per-customer format. Per-batch COA attached. Audit trail per send.

Every retailer thinks its dispatch-note format is the only sensible format. Tesco wants its block. Lidl wants its barcode. M&S wants its EAN-13 on the line. SuperValu, Centra, SPAR and Musgrave each want their own quirks. In Excel you handle this with five templates and one person who remembers which is which. In Keystone, dispatch notes generate from the order in the format the destination customer expects, every time.

• Built-in templates: Tesco IE, Lidl, M&S, SuperValu, Centra, SPAR, Musgrave
• Auto-attach per-batch COA on every dispatch
• Audit trail of every send, who, when, to which address
• Email straight from the system or one-click PDF

A bad dispatch note is rejected at the gate.

It does not matter how good the cheese is if the dispatch note is wrong. A missing batch reference, a wrong customer SKU, a missing weight, a CMR-style address mismatch, and the pallet sits at the depot until somebody from your team drives over. Keystone treats the dispatch note as a serious operational artefact: every field is sourced from the batch, the order and the customer record, with the customer-specific template applied automatically.

A dispatch note built from the order, not retyped.

Operations layer, finance stays where it is.

Keystone publishes invoiced sales to AccountsIQ, Sage, Xero or QuickBooks when the dispatch ships. Your accounts team does not change anything. The dispatch note itself is operational, it lives in Keystone, with the batch chain, the COA, the customer SKU and the audit trail all linked.

Questions buyers actually ask.