Blog

A Bad GS1-128 Pallet Label Is a Chargeback You Cannot Dispute

Walmart charges $50-500 for a GS1-128 label that will not scan, and the deduction is marked not usually disputable.

6 min read

A pallet label that does not scan is one of the few retail chargebacks you cannot argue with.

Walmart calls it WM-LBL: a non-compliant or unscannable GS1-128 label. It runs $50-500 per incident, and it is marked not usually disputable. Costco's version is COST-SSCC, the same event with one extra rule, the SSCC label on both sides of the carton, and the same verdict.

On a labeling charge, the money is not lost in the portal. It is lost at the dock.

What an SSCC is, and what it is for

An SSCC is the serial number that identifies one specific pallet. Not your product, not the purchase order, not the shipment, one physical pallet. Target's ASN-accuracy document list calls it SSCC-18, an 18-digit code carried in a GS1-128 barcode.

It exists for reconciliation. The 856 advance ship notice you transmit before the truck moves tells the distribution centre how many cartons are coming on how many pallets. The SSCC is how the DC records which physical object that claim referred to. Without a scan, the DC holds a count and a claim with no way to tie them together.

That is the reason the code is rigid. It is also why the message carrying the same numbers deserves the same attention: what the 856 actually says.

Five ways a pallet label fails

It is on one face and the retailer wants two. Costco requires the SSCC label on both sides of the carton, and the evidence it asks for is label images for both sides, GS1-128 barcode verification, and pallet configuration photos. You cannot supply the second face after the fact.

It will not scan. Walmart's word for it is unscannable, and it describes a physical outcome: damage, creasing, print the reader cannot resolve, a surface the scanner cannot read. Nothing was wrong at print time; it stopped being a barcode between the label printer and the DC scanner.

The number is right and the data behind it is wrong. An SSCC is only meaningful against the master data behind it. Print it from a stale template or a maintenance table somebody edited last year, and the scan resolves to a different pallet, a different company, or nothing. Walmart's WM-ASN, an SSCC mismatch or missing carton, is usually disputable. Same physical failure, opposite verdict.

The pallet was reconfigured after the label went on. An SSCC belongs to a pallet as it was built. If the load is consolidated, a partial pallet broken down, or the stack rebuilt to fit the trailer, the label describes a configuration that no longer exists. Your own process will not warn you, because the rebuild is one of the last things before the doors close.

One physical event files under two codes. A label the DC cannot read becomes a missing carton in the receiving record. That is a labeling violation and an ASN accuracy failure from the same carton, one not usually disputable and the other usually is. You fight the one you can win and absorb the other.

What each retailer does about it

RetailerCodeWhat it meansUsually disputableWindow
WalmartWM-LBLNon-compliant or unscannable GS1-128 labelNo30 days
CostcoCOST-SSCCMissing or non-compliant SSCC label, two sides requiredNo60 days
Sam's ClubSC-CLUBPKClub-pack non-complianceNo30 days
PetcoPC-LBLLabeling violation, NASC documents if certifiedYes60 days

Costco's incident structure is $50-200, or 1-5% of PO value, and does not separate labeling out. We are not going to guess which end a missing second face lands in.

Sam's Club files this as a packaging code rather than a barcode code: the club pack has to be display-ready, the unit count exact, and the pallet configuration the one the specification sheet describes.

Petco is the exception worth knowing. PC-LBL is marked usually disputable, and the reason is a document requirement rather than a generous policy. If your product carries NASC certification (the National Animal Supplement Council seal), the chargeback pulls in NASC documentation, label artwork, and GS1 compliance documentation. A certified product is easier to argue about, and only because more is asked of you.

What the evidence is actually made of

RetailerDeduction typeDocuments requested
CostcoSSCC / LabelingSSCC label images, both sides of carton; GS1-128 barcode verification; pallet configuration photos
WalmartLabeling violationLabel artwork approval, GS1 barcode verification, carton label photos
WalmartSQEP / ASN errorASN transmission log with timestamp, EDI 856 confirmation, carrier SSCC scan records
Sam's ClubClub-pack complianceClub-pack specification sheet, unit count verification, packaging configuration photos
PetcoLabeling violation, NASCNASC certification documentation, label artwork, GS1 compliance documentation
TargetASN accuracyASN data file, Target item master comparison, SSCC-18 barcode records

Every line on it is retrievable, which is why the ASN row is winnable and the labeling row usually is not. The two describe the same carton.

The honest part

WM-LBL, COST-SSCC and SC-CLUBPK are all marked not usually disputable, and the reason is structural rather than procedural. A label either scans or it does not. No document you attach turns a physical non-compliance into a bookkeeping correction.

The second reason is procedural, and it is Walmart's. Labeling and ASN deductions are compliance chargebacks, accounts-receivable items running through HighRadius, not the AP Disputes Portal. Filing in the wrong queue does not merely slow you down: APDP and HighRadius are not the same queue.

So the money is not recovered afterwards. It is saved upstream, in the template your 3PL loads and the printer on the dock.

A malformed 856 fails loudly. A bad label fails silently.

This explains why the ASN earns your attention and the label never does.

A strict 856 parser is unforgiving, and usefully so. An 856 with no BSN segment is rejected outright, and so is a missing TD1 carton count, a missing PRF PO reference, a missing LIN and SN1 item loop, or an unparseable transmitted date and time. Each is a hard failure at transmission, hours before the dock opens. You find out while the load is still on your floor, and the fix is a resend.

A pallet label has no equivalent failure moment. The 856 parses, the ASN goes out, the trailer is sealed, the shipment arrives. The only signal that anything was wrong is a deduction line on a remittance advice weeks later, by which time the pallet is broken down at the DC and the cartons are on shelves.

There is no error message for a barcode that will not scan. There is only a charge.

Photograph the pallet before it leaves the dock

Costco states this more plainly than anyone: Costco disputes often require physical documentation of the pallet and SSCC configuration, photography of the actual shipment is frequently required, and warehouse teams should photograph every Costco shipment before it leaves the dock.

Do it for everyone. A photograph is the only artefact in this chain that cannot be reconstructed. The pallet as you actually built it existed for about four minutes, and after that the only version of it is a file nobody took.

Windows and portals for all of them are in every retailer's dispute window, in one table.

Costco gives you 60 days to file a labeling charge and Sam's Club gives you 30. A photograph of a pallet is not something you can take 60 days late, and Walmart's $50-500 per incident is not a number you can argue down with a document nobody shot. Put a phone on the dock tomorrow and photograph the pallet and both label faces before the forklift moves.

Keep reading

Want to know what you're owed right now?

Join the waitlist for early access to Disputek.

Join the waitlist →