Home /
Guides / How should pallet labels match SSCC and ASN data?
How should pallet labels match SSCC and ASN data?
The pallet’s physical label and its electronic despatch record must identify the same logistics unit and contents. Printing successfully is only one part of that process.
Test the exceptions that change the contents record
A mixed pallet can contain more than one product or batch. Keep that detail in a controlled record rather than squeezing an incomplete contents list onto the label. Where parent-child aggregation is required, define exactly which case or logistics-unit identities are associated with the pallet and when that association closes.
- A case is removed after the pallet has been labelled: revise the contents record and apply the agreed unit-identity rules before dispatch.
- A pallet is split or rebuilt: distinguish a replacement label for the same unit from creation of a genuinely different unit. Apply GS1 and receiver requirements rather than blindly reusing the old print job.
- Two adjacent pallets exchange positions: prove that the system does not label by queue order alone when the physical sequence can change.
- The ASN cannot be transmitted: use the agreed hold or escalation process; do not treat a successful print as proof of successful electronic despatch.
- A barcode is damaged: authorise the replacement against the original unit record and prevent the rejected label from creating ambiguity.