Walmart Chargeback Code 26: Carton Shortage Explained
Walmart Code 26 is deducted when fewer cartons arrive than the shipment documents show. Learn the ASN/BOL reconciliation that stops it, and how to dispute.
Executive Summary & Quick Answer
Executive summary: Code 26 is the plain-vanilla carton shortage: Walmart received fewer cartons than your shipment documentation said were coming, and deducted the value of the missing ones. What makes it worth studying isn't the definition — it's the anatomy. The "shipment documentation" is really three documents (the 856 ASN, the BOL, the 810 invoice) that are supposed to describe one physical load, and Code 26 fires whenever any of them promises more cartons than the dock delivers. Some of those gaps are real transit losses; the rest are paperwork inflations you shipped to Bentonville yourself. The prevention program is a single idea applied ruthlessly: one scan-verified count, propagated to every document.
Quick answer: Walmart Chargeback Code 26 is a carton shortage deduction — Walmart received fewer cartons than the shipment documentation indicated and deducts the value of the missing cartons. Prevention means reconciling the ASN, BOL, and physical load to one scan-verified count; disputes run through the APDP with signed delivery proof.
Deep Dive: What Triggers Code 26
Every shipment tells Walmart its carton count three times before the truck arrives — and Code 26 is what happens when the physical count can't cash the check.
┌── 856 ASN ────── "500 cartons coming"──┐
ONE PHYSICAL ├── BOL ────────── "500 cartons tendered"─┼──► DC RECEIVES 495
LOAD └── 810 Invoice ── "500 cartons billed" ──┘ │
▼
Code 26: deduct 5 cartons
The failure has exactly two shapes:
- The paper was wrong. The ASN or BOL carried a count higher than what was actually loaded — a pack-out miscount, or documents generated from the PO instead of from the load. The invoice bills the inflated number, and the "shortage" was born in your office, not on the road.
- The load was right, then shrank. Cartons genuinely lost in transit — LTL cross-dock leakage, split shipments, cartons left on a dock. The paper was honest; the physical count dropped in carrier custody.
The two shapes demand opposite responses (fix your documents vs. claim against your carrier), and the only way to tell them apart after the fact is evidence you created before the fact: loading scans and a signed delivery record.
Business & Financial Impact
- Deduction = cost of the missing cartons, per the record.
- Silent and recurring: a systematic pack-out or ASN-generation error produces a small Code 26 on every PO — the kind of leak that hides inside "normal" deduction noise for quarters.
- Freight paid on ghosts: when the paper was inflated, you also paid to ship cartons that never existed on the invoice's terms.
- Disputable when documented: the record's own prevention list includes keeping signed delivery proof for APDP disputes — meaning recoverable money for suppliers who can retrieve a POD quickly.
Root Causes (Ranked)
- Carton count on the ASN or BOL higher than what arrived — the leading cause: documents that promised more than the load carried, whether from generation-from-PO habits or unpropagated short-ship corrections.
- Cartons lost in transit — real physical loss in carrier custody; the paper was right and the network leaked.
- Miscount at pack-out — the upstream feeder for cause 1: the count was wrong before any document was cut, and every document inherited it.
Note the asymmetry: two of the three causes are self-inflicted and fully preventable at origin. Only one belongs to the carrier.
Step-by-Step Prevention Workflow
The record gives three levers; in practice they chain into one pipeline:
- Scan cartons at loading to confirm the count. The count of record comes from scans at the trailer door — not the pick list, not the PO. This is the single source of truth everything else must match.
- Reconcile carton counts across the ASN, BOL, and physical load. Hard gate before the truck departs: 856 carton count = BOL carton count = loading-scan count. Any mismatch stops the ASN transmission, not the truck alone. Short-picked? Correct all three documents, then ship.
- Keep signed delivery proof to dispute in the APDP. Archive signed PODs indexed by PO and invoice. When a Code 26 lands and your loading scans say the full count shipped, the POD is what converts "we're sure we shipped it" into a winnable dispute — or, if the POD is also short, into a carrier claim.
- Trend it monthly. Split Code 26 hits into "paper inflated" vs "transit loss" using your scan/POD pairs. The first bucket drives process fixes; the second drives carrier/lane decisions.
The Dispute Path
- Pull the deduction detail in Retail Link: PO, invoice, cartons claimed missing.
- Check your loading scans — did the full count physically ship?
- Full count shipped + POD shows full delivery → file in the APDP (Retail Link) with POD and BOL attached.
- Full count shipped + POD short → the deduction reflects reality, but the loss is the carrier's: file the freight claim.
- Loading scans short → don't dispute; fix pack-out and document generation.
Code 26 in the Shortage Family
| Code | The story | Where the count broke |
|---|---|---|
| 26 | Fewer cartons than documentation indicated | Paper vs. physical, anywhere in the chain |
| 24 | Freight bill signed short at the DC | Documented at the delivery signature |
| 23 | SLC load the supplier counted | Presumed at your dock |
Code 26 is the general case; 24 is the variant where the shortfall is captured in the carrier's signed delivery record; 23 is the variant where you loaded and counted, so the presumption is against you from the start.
Supplier Checklist
- Carton scans at loading are the count of record — never the pick list
- Hard gate: 856 = BOL = loading scans before ASN transmission
- Short-ship corrections propagate to ASN, BOL, and invoice before departure
- Signed PODs archived and retrievable by PO/invoice in minutes
- Weekly: Code 26 deductions matched to scans + POD — dispute, claim, or fix
- Monthly: Code 26 split "paper vs. transit" — trend both buckets
FAQs
What is Walmart chargeback Code 26? A carton shortage deduction: Walmart received fewer cartons than the shipment documentation indicated, and deducts the value of the missing cartons.
Is Code 26 my fault or the carrier's? It splits. If the ASN or BOL carried a count higher than what was loaded, the shortage is documentary and yours. If loading scans and the BOL were accurate and cartons vanished in transit, it's a carrier loss — and your evidence decides which story you can prove.
How do I dispute a Code 26 deduction? Through the APDP in Retail Link. The core exhibit is signed delivery proof showing the full carton count, backed by the BOL and your loading-scan records.
How is Code 26 different from Code 24? Both are carton shortages. Code 24 is specifically tied to the freight bill being signed short at the DC; Code 26 is the broader documentation-vs-received gap. The prevention discipline — one verified count across ASN, BOL, and load — is identical.
What's the fastest process fix for recurring Code 26? Stop generating the ASN from the purchase order. Generate it from loading scans, and gate transmission on the three-way match. Most chronic Code 26 patterns die with that one change.
Is your next shipment at risk for Walmart?
Run one shipment's PO, ASN, invoice, and delivery data through the free scanner and see the chargeback risks before the truck leaves — no signup, nothing uploaded.
Scan a shipment free →Get ahead of the next chargeback
Join the early-access list for automated pre-shipment audits that flag compliance errors across every shipment — before they become deductions.
GetChargeback is not affiliated with Walmart.This guide is compiled from industry sources for general information and is not legal, financial, or compliance advice. Verify current requirements in the retailer's official vendor portal before acting. Last reviewed 2026-07-10.