Pallet labels

Pallet labels that scan first time.
SSCC. GS1-128. Per-pallet variants. Designed in-system.

Retailer scanners have no sympathy. If the GS1-128 fails to parse, the SSCC is the wrong format, or the EAN is on the wrong row — the pallet is rejected at the dock and you are on the phone for an hour. Keystone treats pallet labels as a first-class production artefact, designed in-system, scanned in test before printing, and stamped against a real batch and dispatch line.

SSCC and GS1-128 standards built in
Per-pallet, per-case and per-line variants — designed in the in-app designer
Audit trail on every label printed — who, when, against which dispatch
Retailer templates: Tesco, Lidl, M&S, SuperValu, Centra, SPAR, Musgrave

Book a discovery call See pricing

Why pallet labels go wrong

Each retailer treats its labels as gospel.

Tesco expects a different SSCC layout from Lidl. M&S wants the customer SKU larger than your internal code. SuperValu wants the consignment number above the batch line. None of this is in any spec a generic ERP comes with — you discover each rule by getting a pallet rejected. Keystone ships with retailer-specific templates already configured, refined against real production at our founding partner.

How the designer works

A WYSIWYG designer with retailer presets.

Drag-and-drop layout

Position text, barcodes and logos on a real-size canvas. Preview at print size. No PostScript, no XML files.

SSCC and GS1-128 native

Application Identifiers (AI) configured visually. Test-scan your design with a USB scanner before saving.

Per-pallet variants

Mixed pallets are first-class — different cases per pallet, different SKUs per layer, all reconciled against the dispatch.

Variable-weight aware

Per-pallet weight pulled from the actual case-by-case weights captured at pack — not assumed.

Audit trail

Every label print is logged against the dispatch, the user, the printer and the timestamp. A scan-failure 3 days later is investigatable.

Where this sits

Operations layer — finance untouched.

Pallet labels are operational. Keystone owns them — generated from the dispatch, against real batches, printed locally to your label printer. Your accounts package keeps doing accounts. No double-entry, no Excel intermediate step, no manual SSCC counter.

FAQ

Questions buyers actually ask.

Do you support Zebra and SATO label printers?

Yes — ZPL output to any Zebra-compatible printer, plus PostScript for SATO and other standard label printers.

What about an SSCC counter that has to be globally unique?

Keystone maintains your SSCC counter per company prefix and reserves ranges per printer if needed. No collisions.

Can a single dispatch use multiple label templates?

Yes — different customers, different pallets on the same dispatch, different templates. The system tracks which template applied to which pallet.

Can dispatch staff design labels themselves?

Yes — the designer is in-app and permissioned. Most customers have one or two trained super-users who own templates.

What happens if a label is misprinted?

Void the label in the system, reprint, audit trail captures both. No silent re-labelling.

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

Pallet labels that scan first time.SSCC. GS1-128. Per-pallet variants. Designed in-system.