What happens if the SSCC on the label does not match the ASN?

Mismatches can cause receiving delays, manual investigation, or chargebacks because distributors rely on the SSCC to reconcile physical pallets with electronic data.

First B2B shipment? How to handle GS1-128 pallet labels and SSCCs (without overthinking it)

Q: Is an SSCC the same as a GTIN?

No. A GTIN identifies a product, while an SSCC identifies a specific pallet or shipment unit.

Q: Do SSCCs need to be included in the ASN?

Yes. Most distributors require the SSCC to appear both on the GS1-128 pallet label and in the ASN so pallets can be matched to expected shipments.

Q: Can SSCCs be generated manually?

They can be, but manual generation increases the risk of duplication or errors. Best practice is to generate SSCCs systematically using a GS1 Company Prefix.

If you’re shipping B2B wholesale for the first time, label requirements can feel deceptively familiar.

Most suppliers are already comfortable with GS1-128 carton labels. These typically appear on individual cases and carry product-level information that helps retailers and distributors identify what’s inside each carton.

Pallet labels are different. In this article, we’re focusing specifically on SSCC.

A GS1-128 pallet label identifies the pallet itself as a logistics unit. Instead of describing the product, it uses an SSCC (Serial Shipping Container Code) to uniquely identify that specific pallet for receiving, tracking, and reconciliation against the Advance Ship Notice (ASN).

That distinction matters, especially when a distributor requests “GS1-128 pallet labels with SSCCs.” It’s easy to assume this is just an extension of carton labeling, when in reality it’s a separate requirement tied to shipping and receiving workflows.

What is an SSCC (and why distributors care)

An SSCC (Serial Shipping Container Code) is a unique number used to identify a specific pallet or logistics unit.

Think of it this way:

GTIN = identifies what the product is
SSCC = identifies this exact pallet in this exact shipment

Distributors like KeHE use SSCCs to:

Track pallets through receiving
Match physical pallets to ASNs (EDI 856)
Reduce receiving errors and manual research

That’s why they typically require:

A GS1-128 barcode
An SSCC
The purchase order number printed on the label

Do SSCCs come from EDI?

This is where a lot of first-time wholesale shippers get stuck.

SSCCs are not inherently created by EDI alone

In practice, this depends on how EDI is implemented. Many traditional EDI setups transmit SSCCs only after they already exist. Platforms like Lingo go a step further by generating SSCCs as part of the shipping workflow and allowing teams to associate cartons with pallets, so the same identifier flows cleanly into labels and the ASN.

In most real-world setups:

The warehouse or shipping process generates the SSCC
That SSCC is then:
- Printed on the GS1-128 pallet label
- Included in the Advance Ship Notice (ASN / EDI 856)

Some EDI tools can store and transmit SSCCs once they exist, but they are not always the system of record for creating them. This is especially common when shipping directly for the first time or operating without a 3PL.

How SSCCs are typically generated

SSCCs follow a GS1-defined structure and must be globally unique.

Suppliers generate SSCCs:

Using their GS1 Company Prefix
With a sequential serial reference
At the time of packing or palletizing

This can happen in an ERP, WMS, or shipping workflow. The key requirement is that the same SSCC flows consistently into:

The pallet label
The ASN
Downstream receiving systems

For a deeper look at how identifiers move cleanly across systems, see our guide to integrating EDI with your ERP and warehouse.

Labeling best practices for KeHE and similar distributors

While requirements can vary slightly by trading partner, distributors like KeHE generally expect:

GS1-128 barcode with:
- (00) SSCC
Human-readable SSCC text
Purchase order number printed on the label
Label placed consistently on the pallet (usually multiple sides)

The important thing is consistency between:

What’s on the pallet label
What’s in the ASN
What arrives physically at the dock

Small mismatches here are one of the most common causes of receiving delays and chargebacks.

You can read more about how these “small gaps” show up later in the process here.

Where teams run into trouble

For first-time wholesale shipments, issues usually come from:

SSCCs being created manually without a clear sequence
Labels printed correctly, but SSCCs missing from the ASN
EDI handled in one system, shipping handled in another, with no clean handoff

None of these are huge problems on their own. They become expensive when volume increases or when multiple retailers are involved.

That’s why many growing suppliers move toward a more unified setup where:

SSCCs are generated once
Flow cleanly into labels, ASNs, and invoices
Stay consistent across ERP, WMS, and EDI

How eZCom helps simplify this

At eZCom, we help suppliers run EDI as part of a connected workflow, not a standalone task.

With Lingo, teams can:

Keep shipment identifiers aligned across systems
Generate SSCCs and control how cartons are assigned to pallets
Ensure those SSCCs flow correctly into pallet labels and ASNs
Reduce last-minute fixes during packing and shipping
Support distributor requirements like KeHE without custom workarounds

Final takeaway

If this is your first direct B2B delivery, here’s the simple version:

SSCCs are created operationally, not magically by EDI
EDI’s role is to communicate them accurately
Consistency matters more than tooling

Get that foundation right early, and future shipments get much easier.

If you’d like help reviewing your setup before volume ramps up, our team is always happy to sanity-check your workflow.

FAQ: GS1-128 Pallet Labels and SSCCs

What information is included on a GS1-128 pallet label?

A standard GS1-128 pallet label typically includes:

The SSCC encoded in a GS1-128 barcode
Human-readable SSCC text
The purchase order number
Supplier and shipment reference information, depending on the distributor

What is an SSCC?

An SSCC (Serial Shipping Container Code) is a unique GS1 identifier used to track an individual pallet or logistics unit through the supply chain. It allows distributors to link a physical pallet to electronic shipping documents like the ASN.

Is an SSCC the same as a GTIN?

No. A GTIN identifies the product itself. An SSCC identifies a specific pallet or shipment unit. One shipment may contain many GTINs but only one SSCC per pallet.

Do SSCCs need to be included in the ASN?

Yes. Most distributors require the SSCC on both the GS1-128 pallet label and in the ASN (EDI 856). This allows receiving teams to scan the pallet and immediately match it to the expected shipment.

Are SSCCs generated by EDI systems?

Typically, no. SSCCs are usually generated during packing or palletizing and then passed into the EDI workflow. Many EDI systems simply transmit SSCCs once they exist, rather than acting as the system of record for creating them. With eZCom’s Lingo, SSCCs can be generated as part of the shipping workflow, assigned to specific pallets and cartons, and then carried through to pallet labels and the ASN.

Can SSCCs be generated manually?

They can be, but manual creation increases the risk of duplication or sequencing errors. Best practice is to generate SSCCs systematically using your GS1 Company Prefix and a controlled serial reference.

What happens if the SSCC on the label doesn’t match the ASN?

Mismatches can lead to receiving delays, manual research, and usually a chargeback. Distributors rely on the SSCC to reconcile physical pallets with electronic documents, so consistency is critical.

Is this different when shipping to distributors like KeHE?

Requirements are generally aligned across major distributors, though label placement and formatting rules may vary. The core expectation remains the same: a valid SSCC on the pallet label that matches the ASN.