GS1-128 at the dock: what a compliant label carries.
GS1-128 is the workhorse of logistics labeling: the barcode on most of the carton and pallet labels that cross a receiving dock. This is the receiving side of the story: what the codes mean, what gets checked at the door, and what a good record looks like when a label fails.
What the label carries.
Each field starts with an Application Identifier, a short numeric prefix that says what the next field means. The symbology underneath is Code 128; a special FNC1 character marks the data as GS1-formatted. The human-readable line under the bars must say exactly what the bars encode.
What receiving actually checks.
It reads.
Print contrast, bar quality, and the quiet zone, the blank margin around the bars, decide whether the code scans at all.
It matches the ASN.
The SSCC on the pallet ties to the advance ship notice already sent to your ERP or WMS. No match, no clean receive.
The words match the bars.
The human-readable line must say what the barcode encodes. When they disagree, something upstream was keyed or printed wrong.
It sits where it can be scanned.
Logistics labels belong where the reader, human or camera, can see them as the pallet comes off the trailer.
When a label fails at the door.
A failed label does not stop the trailer. The item gets received by hand, the flow slows down, and the failure usually goes undocumented, which is exactly backwards: the moment a label fails is the moment you need a record of it. A photo of the label as it crossed, with the exact time, is the difference between telling a supplier their labels are failing and showing them.
Flowtally checks label compliance on every read.
A failed or non-compliant label is flagged as an exception with its picture. The evidence assembles itself at the door.
See how Flowtally reads the dockCommon questions from the dock.
What is the difference between GS1-128 and Code 128?
Code 128 is the underlying symbology, the pattern of bars that encodes full ASCII data. GS1-128 is a stricter application of it: the data inside must follow the GS1 system of Application Identifiers, each a short numeric prefix that says what the next field means, such as (01) for the item number or (00) for the pallet's SSCC. Every GS1-128 barcode is a Code 128 barcode, but not the other way around.
What is an SSCC and why does it matter at receiving?
The Serial Shipping Container Code is an 18-digit number that identifies one specific logistics unit, usually a pallet, the way a license plate identifies one vehicle. When the sender transmits an advance ship notice, the SSCC ties the physical pallet at your door to the shipment data already in your ERP or WMS, which is what makes scan-and-receive possible.
What do receiving teams actually check on a pallet label?
Four things carry most disputes: the barcode reads at all, the SSCC or item data matches the advance ship notice, the human-readable line matches what the barcode encodes, and the label sits where it can be scanned. Print quality and the quiet zone, the blank margin around the bars, decide most read failures.
What happens when a label fails at the dock?
The item still has to be received, so someone keys the number in by hand and the flow slows down. What matters afterward is whether the failure was documented: a photo of the label at the moment it crossed, with the timestamp, turns an argument with the supplier into a record you can send them.
Label compliance, checked on every read.
Every read is paired with its photo and the exact time, with label compliance checked as part of the receive itself.