CGetChargeback

Walmart Chargeback Code 21: Store-Level Shortage

Walmart Code 21 is a shortage found at the store, not the DC. Learn why store-level shortages happen, what they cost, and how suppliers prevent them.

Executive Summary & Quick Answer

Executive summary: Code 21 is the shortage that surfaces last — not at the DC dock, but when a store receives the shipment. That distance from your dock makes it the hardest shortage code to see coming and one of the hardest to dispute without airtight counts, labels, and delivery proof. For DSD suppliers, it's the primary shortage exposure.

Quick answer: Walmart Chargeback Code 21 is a deduction for a shortage discovered at the store rather than at the distribution center. Walmart deducts the value of units the store found missing. Common causes include DC-to-store handling loss, receiving miscounts, and direct-store-delivery discrepancies — prevented with accurate counts, scannable labels, and signed delivery records.


Deep Dive: What Triggers Code 21

Most Walmart shortage codes reconcile at the DC. Code 21 fires later in the chain: the DC receipt looked fine (or wasn't the control point at all), but store receiving logged fewer units than the paperwork claims. Two supply paths produce it:

Path 1 — through the DC network. Your freight passed DC receiving, was broken down, and cross-docked to stores. Units lost or mis-sorted between DC and store surface as a store-level shortage — attributed back to your invoice.

Path 2 — DSD (Direct Store Delivery). You deliver to the store yourself. The store's count at the back door is the receiving record. A rushed check-in, a mixed pallet, or an unscannable carton label becomes a Code 21 with no DC record to fall back on.

Why labels matter here: cartons that scan cleanly get counted correctly. A carton whose GS1-128 label is damaged or mismapped is exactly the carton that gets missed at a busy store back door — label quality quietly feeds shortage codes.


Business & Financial Impact

  • Deduction = value of units short at the store.
  • Weak visibility: the discrepancy happens downstream of your control, and the deduction may arrive weeks after delivery.
  • Dispute difficulty is the real cost. For DC-path freight, your evidence ends at the DC receipt; for DSD, everything rides on what your driver had signed at the back door.
  • DSD suppliers with many store drops see Code 21 as a steady bleed — small per store, large in aggregate.

Root Causes (Ranked)

  1. DSD check-in discrepancies — store counts differ from the delivery record; no signature or a partial signature.
  2. DC-to-store handling loss — units lost in breakdown/cross-dock after clean DC receipt.
  3. Mixed or mislabeled cartons — store receiving can't scan/verify, units go uncounted.
  4. Pallet-level counting — store signs for pallets, later finds inner cartons short.
  5. Paper-only delivery records — nothing scannable or signed to anchor a dispute.

Step-by-Step Prevention Workflow

pack/label (scan-verified) ──► ship/deliver ──► signed, itemized delivery record
        │                                                  │
   carton counts accurate,                        DSD: driver gets line-level
   labels scannable                               signature BEFORE leaving
        │                                                  │
        └────────► weekly: Code 21 sweep ◄─────────────────┘
                   match deductions to signed records → dispute or fix
  1. Scan-verify carton contents and labels at pack-out. Store receiving can only count what it can scan.
  2. For DSD: itemized signature, every stop. Line-level counts signed at the back door — not a pallet-level scribble. That signature is the entire dispute case.
  3. Keep case-pack integrity. Store-bound cartons with consistent case packs count faster and more accurately than mixed cartons.
  4. Archive delivery records by store/PO. Retrieval speed determines whether disputing is economical.
  5. Weekly sweep: map Code 21 deductions to delivery records; dispute documented ones in the APDP, and look for store- or SKU-level patterns in the rest.

Code 21 vs Code 22 (where was the shortage found?)

Code 21 Code 22
Shortage surfaces at The store The DC / invoice match
Typical path DC→store handling, DSD Billed more than DC received
Your evidence Signed store delivery record Signed POD/BOL at the DC
Dispute difficulty Higher — furthest from your dock Moderate — POD usually decides

Related: Code 22 · Code 24 · Code 23


Supplier Checklist

  • Carton contents scan-verified at pack-out; labels print-quality checked
  • Case packs consistent for store-bound freight
  • DSD: line-level counts signed at every back door, archived by store/PO
  • 856 hierarchy matches physical cartons/pallets
  • Weekly Code 21 sweep: dispute documented shortages, pattern-hunt the rest

FAQs

What is Walmart chargeback Code 21? A deduction for a shortage discovered at the store rather than at the distribution center. Walmart deducts the value of the units the store found missing.

How is Code 21 different from Code 22? Code 22 is a billed-versus-received gap caught at the DC/invoice match. Code 21 surfaces later, at store receiving — after the DC record looked clean, or on a direct store delivery.

Can I dispute Code 21? Yes, via the APDP in Retail Link — but only as strong as your delivery evidence. For DSD, an itemized signed delivery record is essential; pallet-level signatures rarely win.

Why do DSD suppliers see more Code 21? Because the store's back-door count is the only receiving record. Any rushed check-in or unscannable carton becomes a shortage with no DC receipt to fall back on.

Does label quality really affect shortage codes? Yes. Cartons that don't scan get miscounted. Damaged or mismapped GS1-128 labels are a recurring hidden cause of store-level shortages.


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.