Walmart Chargeback Code 14: Seal Intact, Shipment Short

Executive Summary & Quick Answer

Executive summary: Code 14 is the shortage that arrives with the seal still on. The trailer shows up at Walmart's DC untouched — seal number matching, no sign of tampering — yet the count inside doesn't match what you billed, or product inside is damaged. Because nothing entered or left the trailer after sealing, the discrepancy is presumed to have happened at origin: your dock, your loaders, your count. That presumption is what makes Code 14 hard to dispute and — for the same reason — highly preventable. The fix lives entirely inside your four walls, before the seal clicks shut.

Quick answer: Walmart Chargeback Code 14 is a deduction taken when a trailer arrives with its seal intact but the shipment is short or damaged. The unbroken seal points the discrepancy back to a load or count issue at the supplier's origin dock. The deduction equals the cost of the affected units.

---

Deep Dive: What Triggers Code 14

An intact seal is a chain-of-custody statement: whatever was in the trailer when it was sealed at your dock is what arrived at Walmart's DC. So when the DC breaks a matching seal and finds fewer units than the invoice bills — or units damaged in a way transit can't explain — the inference is mechanical. The problem was loaded in, or never loaded at all.

Where the documents meet the physical load:

Document	What it claims	Where Code 14 exposes it
856 (ASN)	What you told Walmart is on the truck	ASN quantity built from the order, not the actual load
BOL	What the carrier signed for	Count copied from paperwork nobody physically verified
810 (Invoice)	What you're billing	Bills the ASN/BOL number, inheriting the origin error
Seal record	Custody unbroken since your dock	Eliminates transit as the explanation

The dangerous pattern is documentary inheritance: the 856 is generated from the PO, the BOL copies the 856, the 810 bills the BOL — and no document was ever reconciled against what physically went on the trailer. An intact seal collapses all the alternative explanations and leaves that reconciliation gap as the answer.

Damage works the same way under Code 14: crushed or leaking product behind an unbroken seal was damaged before sealing — at pick, at staging, or during loading.

---

Business & Financial Impact

• Deduction = cost of the short or damaged units. Per the record, the fine equals the value of the affected product.
• Weak dispute posture: the intact seal is Walmart's evidence, not yours. Without origin proof (loading scans, photos of the loaded trailer), you're arguing against physics.
• Margin leak that scales with volume: a systematic count error at pack-out repeats on every load until someone finds it.
• Signal value: recurring Code 14 is one of the cleanest indicators of a broken pick/load verification process — it's the code that can't blame the carrier.

---

Root Causes (Ranked)

1. Miscount or mis-load at the supplier's dock before sealing — the top cause in the record: pick errors, staging mix-ups, cartons left on the dock as the doors closed.
2. BOL count higher than what was actually loaded — paperwork generated from the order rather than the load; the invoice bills units that never shipped.
3. Damage that occurred before the trailer was sealed — forklift strikes, crushed bottom tiers, product staged in weather — sealed in and discovered at destination.
4. No verification step between pick and seal — not listed as a cause per se, but the process gap underneath all three: nobody counts the load as loaded, so errors ride to Bentonville undetected.

---

Step-by-Step Prevention Workflow

All three prevention levers in the record sit at the dock door, in sequence:

PICK ──► STAGE ──► LOAD ──► [COUNT + INSPECT] ──► PHOTOGRAPH ──► SEAL ──► RECONCILE BOL
                                  │                                            │
                            gate: physical                              gate: paper
                            matches paper?                              matches physical?

1. Verify the loaded count and condition before sealing. A physical count at the trailer door — scans, not eyeballs — against the 856. Damaged cartons come off the truck here, not at Walmart's expense later.
2. Photograph the sealed, loaded trailer. Time-stamped photos of the loaded trailer interior and the applied seal are your only affirmative dispute evidence for a code whose premise is "origin fault." Cheap insurance, taken in seconds.
3. Reconcile the BOL to the actual loaded quantity. The BOL states what was counted onto the truck — never a number copied from the PO or ASN. If the count came up short, correct the 856 and the 810 before they transmit.
4. Close the loop weekly. Match any Code 14 deductions against loading records; a hit with clean scan/photo evidence goes to dispute, a hit without it goes to root-cause review of the pick/load process.

---

The Dispute Path

1. Pull the deduction detail in Retail Link: PO, invoice, units claimed short or damaged.
2. Assemble origin evidence — loading scan records, the count-verified BOL, photos of the loaded trailer and seal.
3. File in the APDP (Retail Link) with that evidence attached. The argument you're making: the billed quantity physically left in good condition behind that seal.
4. No origin evidence? Take the loss, then audit the pick/load step — Code 14 without documentation is rarely worth contesting, but it's always worth fixing.

---

Code 14 in the Shortage Family

Code	The story	Custody question
14	Seal intact, shipment short/damaged	Presumed origin — your dock
23	SLC load you counted — presumption against you	Contractually yours
24	Freight bill signed short at the DC	Carrier chain in play

Code 14 and Code 23 share a presumption against the supplier; Code 24 is the one where the carrier's custody is genuinely in question. The seal is the pivot: intact seal → 14, documented short delivery → 24.

Related: Code 23 · Code 24

---

Supplier Checklist

• Physical count (scan-based) at the trailer door before every seal
• Condition inspection at loading — damaged cartons pulled, not sealed in
• Time-stamped photos of loaded trailer + applied seal, archived by PO
• BOL reconciled to the actual loaded quantity, never copied from the PO
• 856 and 810 corrected before transmission when the load count changes
• Weekly: Code 14 deductions matched to loading evidence — dispute or root-cause

---

FAQs

What is Walmart chargeback Code 14? A deduction taken when a trailer arrives with its seal intact but the shipment is short or damaged. Because the seal was unbroken, the discrepancy points to a load or count issue at origin, and Walmart deducts the cost of the affected units.

Why does the intact seal matter so much? It removes transit from the list of explanations. Nothing entered or left the trailer after your dock sealed it, so a shortage or pre-existing damage is presumed to have originated with the loading process.

Can I dispute a Code 14 deduction? Yes, through the APDP in Retail Link — but you need affirmative origin evidence: loading scans, a count-verified BOL, and ideally photos of the loaded trailer and seal. Without those, the seal's presumption stands.

How is Code 14 different from Code 24? Code 24 is a shipment signed short at the DC, where carrier custody is in question. Code 14's intact seal takes the carrier out of the story and points at origin.

What's the single highest-leverage prevention step? Verify the loaded count and condition before sealing the trailer, and reconcile the BOL to that count. Every Code 14 cause in the record is upstream of the seal.

Does Code 14 cover damage as well as shortage? Yes. Damage found behind an intact seal is treated as pre-seal damage — it occurred before the trailer was closed, so the same origin presumption applies.

---