SSCC-18, Handling Units, Labels, and EDI Mapping: Getting Your ASN Right to Avoid Chargebacks

If you've ever received a chargeback related to your ASN, you know how frustrating it can be - especially when you did ship the right product on time. The issue is often not what you shipped, but how the ASN was built and whether it matched what was physically on the truck. Getting that alignment requires four things working together: your SSCC-18 numbers, your handling units in SAP, your carton labels, and your EDI 856 mapping. Miss any one of them, and you're at risk.

What is an SSCC-18 and why does it matter?

The SSCC-18 (Serial Shipping Container Code) is an 18-digit barcode that uniquely identifies a handling unit - a carton, a pallet, whatever you're shipping in. Your customer will scan that barcode when the shipment arrives. If the number on the label doesn't match what's on the ASN, or if the same number shows up twice, you have a problem. In SAP, that means setting up your number ranges correctly upfront so there's no risk of duplication across shipments to the same customer.

How Handling Units tie it all together

In SAP, the handling unit connects your physical pack to your EDI data. When you pack items into a carton on the outbound delivery, that carton becomes an HU with an assigned SSCC-18 - holding the item, quantity, and barcode your customer wants to see on the 856. Without HU management in use, you lose that linkage and likely end up with an item-level ASN only, which many customers won't accept.

The label piece - often an afterthought

Many customers have their own label requirements - specific layouts, barcode symbology, sometimes their own item numbers alongside yours. That often means custom label development per customer, which takes time and needs to be tested before go-live.

Timing matters:

• The label needs to print and the carton needs to be packed in SAP before post goods issue
• The ASN should only go out after PGI

If that sequence gets mixed up, you end up with ASNs that don't reflect what actually shipped.

EDI 856 mapping - where it all has to come together

Even if your HUs are set up correctly and your labels are right, your EDI mapping still has to translate all of that SAP data into the structure your customer expects. The 856 requires a specific hierarchy - typically Shipment > Order > Pack > Item - and SAP's standard IDoc output doesn't hand that to you neatly.

Your EDI solution needs to:

• Read the HU data
• Group items by carton
• Carry the SSCC-18 into the correct segment
• Meet any customer-specific requirements on top of that

A weak mapping layer means all the work you did in SAP doesn't land correctly on the other end.

Getting it right

The most common failure points are:

• The SSCC on the ASN doesn't match the label
• The ASN is sent before packing is complete
• Pack detail is missing because HUs weren't used
• The EDI mapping doesn't reflect the correct hierarchy

What it takes to avoid these is co-ordination across your SAP configuration, label design, and EDI mapping - all built with your customer's specific requirements in mind. When it's done right, the chargeback risk goes away.

If you're setting up ASNs for the first time or troubleshooting compliance issues, the CONTAX team has worked through these scenarios across hundreds of implementations. Reach out at info@contax.com .