Walmart Chargeback Code 71: Incorrect Item Numbers on Labels

Executive Summary & Quick Answer

Executive summary: Code 71 is a labeling-data failure: the item number printed on the label doesn't match the product inside. The goods may be exactly what Walmart ordered — but automated receiving doesn't open cartons, it scans labels. When the scan resolves to the wrong item, the DC's automation breaks and Walmart charges a per-unit or per-carton fee for the manual intervention. The dangerous property of Code 71 is fan-out: label data is templated, so one wrong mapping doesn't mislabel one unit — it mislabels the entire run, and the fee multiplies by everything that went out the door.

Quick answer: Walmart Chargeback Code 71 is assessed when items carry labels with incorrect item numbers — the label doesn't match the actual product, disrupting automated receiving. Walmart charges a per-unit or per-carton fee for mislabeled items. Prevention means validating label data against the item file and scan-checking samples before shipping.

---

Deep Dive: Three Records, One Item — and Only the Label Gets Scanned

Every unit arriving at a Walmart DC exists as three records that must agree:

PHYSICAL PRODUCT ◄──must match──► LABEL (item number / UPC)
        ▲                              ▲
        └────────── EDI 856 (ASN) ─────┘
              "here's what's coming"

Receiving automation trusts the label. A scanner reads the item number or barcode, resolves it against the item file, and books the inventory — no human looks inside the carton. When the label carries the wrong item number:

What's true	What the scan says	What the DC experiences
Correct product inside	Wrong item number on label	Received "wrong" item; automation halts, manual handling
Label disagrees with the 856	ASN promised item A, label scans as item B	Reconciliation exception on the receipt
Whole print run shares the template	Every unit scans wrong	Fee multiplied across the shipment

Note what Code 71 is not: it's not about barcode print quality (smudged, unscannable) and not about shipping the wrong product. The product is typically right; the data on the label is wrong. That's a mapping problem — a label template pointed at the wrong item record, or a UPC-to-item-number crosswalk that drifted — which is why it recurs identically until someone fixes the source data.

---

Business & Financial Impact

• Per-unit or per-carton fee for mislabeled items — the record's fine basis. Unit-level fees scale with volume, which is exactly how a template error becomes a five-figure deduction.
• Fan-out risk: one wrong mapping mislabels an entire production run. The fee doesn't correlate with the mistake's size — it correlates with how much you shipped before catching it.
• Downstream inventory noise: goods booked under the wrong item number distort on-hand accuracy on both sides until corrected.
• Repeat-offender exposure: because the root cause is templated data, Code 71 recurs on every shipment until the template or crosswalk is fixed — it doesn't self-resolve.

---

Root Causes (Ranked)

1. The wrong item number printed on labels — bad source data flowing straight into print.
2. A label template mapped to the wrong item — the template pulls from the wrong item record; every unit printed from it is wrong.
3. UPC / item-number mismatch — the barcode and the human-readable item number resolve to different items, or the UPC-to-item crosswalk is stale.
4. Item file drift — item numbers updated in one system (ERP, item file, label software) but not the others.
5. Manual label runs — one-off labels printed outside the governed template flow, numbers keyed by hand.

---

Step-by-Step Prevention Workflow

ITEM FILE ──► LABEL TEMPLATE ──► PRINT RUN ──► SCAN-CHECK SAMPLE ──► 856 MATCH ──► SHIP
 (source of      (validated         (governed)     (label = item?)     (label = ASN?)
   truth)         mapping)

1. Validate label item numbers against the item file before printing. The label template must pull from the same item master the 856 is built from — one source of truth, not two.
2. Verify the UPC-to-item mapping. Confirm the barcode on the label resolves to the same item as the printed item number. Re-verify whenever items are added or renumbered.
3. Scan-check a label sample before shipping. Pull units from the run, scan them with a reader, and confirm the decode matches the physical product. Thirty seconds per run kills the fan-out risk.
4. Match labels against the 856. The item numbers on the cartons and the items promised on the ASN must reconcile before the truck leaves.
5. Lock down manual label printing. Off-template label runs are where hand-keyed item numbers sneak in.

---

The Dispute Path

1. Pull the deduction detail from the APDP in Retail Link: PO, items cited, units/cartons fined.
2. Check your label records and scan-check logs for that run. Can you show the labels carried correct item numbers?
3. If your evidence shows correct labels (retained samples, verification scans, label-file records): file in APDP with that documentation.
4. If the labels were wrong: the deduction stands. Spend the effort on the template or crosswalk fix instead — Code 71 recurs until the source data is corrected.

---

Code 71 vs Code 95: Wrong Label or Wrong Product?

	Code 71	Code 95
What's wrong	The label's item number	The physical item vs the PO
The goods	Usually correct product	Wrong product entirely — returned
Deduction basis	Per-unit / per-carton mislabel fee	Cost of the wrong items returned
Typical root cause	Label template / UPC-item mapping	Wrong item picked or shipped
Fix lives in	Label data and print process	Picking and order fulfillment

Both trace back to item/UPC data integrity — which is why suppliers who see one often see the other. Related: Code 95

---

Supplier Checklist

• Label templates pull item numbers from the same item master as the 856
• UPC-to-item-number mapping verified, re-verified on any item change
• Scan-check sample from every print run before it hits cartons
• Label item numbers reconciled against the 856 before shipping
• Manual/off-template label printing locked down
• Weekly: Code 71 deductions traced to template or crosswalk — fixed at the source

---

FAQs

What is Walmart chargeback Code 71? A deduction assessed when items are labeled with incorrect item numbers — the label doesn't match the actual product, which disrupts automated receiving. Walmart charges a per-unit or per-carton fee for the mislabeled items.

How much does Code 71 cost? The record shows a per-unit or per-carton fee for mislabeled items. Because label errors are templated, the fee typically applies across the whole run — the total scales with shipment volume, not with the size of the mistake.

Is Code 71 the same as shipping the wrong product? No. With Code 71 the product is usually correct — the item number on the label is wrong. Shipping the wrong physical item against the PO is Code 95, and Walmart returns those goods.

Can I dispute a Code 71 deduction? Through the APDP in Retail Link, if you can document that the labels carried correct item numbers — retained samples, scan-verification logs, or label-file records for that run.

Why does Code 71 keep recurring on my shipments? Because the root cause is source data: a label template mapped to the wrong item or a stale UPC-to-item crosswalk mislabels every subsequent run identically until it's fixed.

What single habit prevents the most Code 71 pain? Scan-check a sample from every label run before shipping, and validate the decode against both the physical product and the item file.

---