Walmart Chargeback Code 92: Returned Merchandise Deduction

Executive Summary & Quick Answer

Executive summary: Code 92 is different from most codes in this catalog: often, nothing failed. Walmart returned merchandise to you — overstock you agreed to take back, product you recalled, or defective/safety-related returns — and deducted the value of the returned goods from payment. The compliance question isn't "how do I stop this" (a recall is a recall); it's "does the deducted amount match what actually came back, at the right cost?" Suppliers who treat Code 92 as noise leak money through quantity mismatches, cost discrepancies, and deductions for returns that never physically arrived. The discipline here is reconciliation, not prevention.

Quick answer: Walmart Chargeback Code 92 is a deduction taken when Walmart returns merchandise to the supplier — typically overstock returns or a supplier recall — and deducts the value of the returned goods. It is a returns accounting event, not a compliance fine; the job is reconciling the deduction against actual returns.

---

Deep Dive: What Triggers Code 92

Three events in the DB record put goods on a truck back to you under Code 92: a supplier product recall, an agreed return of overstock inventory, and defective or safety-related returns. In each case Walmart deducts the cost of the returned merchandise — the deduction and the physical return are two halves of one transaction.

That's exactly where the money leaks. The deduction arrives on remittance immediately; the goods arrive later, in whatever condition and count the return process produced. Most suppliers book the deduction and never close the loop.

The reconciliation loop:

WALMART DEDUCTS ────────────► REMITTANCE (Code 92, $X)
      │                              │
      ▼                              ▼
GOODS SHIP BACK ──► YOUR DOCK ──► COUNT + COST CHECK ──► match? ──► close
                                                          │
                                                     no ──┴──► APDP dispute

EDI insight — the 810 connection: Code 92 lands against invoices you already transmitted. The deduction should reconcile three ways: the original 810 line cost for the item, the authorized return quantity, and the physical receipt at your dock. Any leg of that triangle disagreeing — deducted cost above the invoiced cost, deducted units exceeding received units — is disputable variance, not background noise.

Reconciliation leg	Source of truth	Common leak
Unit cost	Original 810 invoice line	Deduction priced above invoiced cost
Quantity	Return authorization + dock count	More units deducted than returned
Existence	Physical receipt	Deduction with no corresponding return

---

Business & Financial Impact

• Deduction = cost of the returned merchandise — for a recall or overstock event, that can be one of the largest single deductions a supplier sees all year.
• Cash timing: the deduction hits remittance before the goods hit your dock; large events create working-capital gaps.
• Variance leakage: unreconciled quantity and cost mismatches are pure loss — small per event, systematic across events.
• Recovery value of returns: overstock that comes back sellable has residual value only if it's received, inspected, and restocked promptly.
• Signal value: repeated defective/safety-related Code 92 events point at product quality problems that will cost far more than the deductions.

---

Root Causes (Ranked)

1. Supplier product recalls — you initiated it; the deduction follows automatically.
2. Agreed overstock returns — negotiated inventory givebacks flowing through the return channel.
3. Defective or safety-related returns — product problems surfacing after receipt.
4. Reconciliation gaps (the controllable one) — deductions never matched to authorizations, counts, or costs, so variances go unnoticed and undisputed.
5. Missing return paperwork — without documentation of what was authorized and received, even legitimate disputes can't be evidenced.

---

Step-by-Step Reconciliation Workflow

Code 92 prevention isn't about stopping returns — it's about making every deducted dollar prove itself.

1. Log every return authorization. Recall notices, overstock agreements, and return approvals go into one register with expected quantities and costs.
2. Receive returns like inbound freight. Count, inspect, and record condition at the dock. A returned pallet nobody counted is a deduction nobody can check.
3. Three-way match each Code 92. Deduction ↔ authorization ↔ physical receipt. Match on units and on cost against the original invoice.
4. Dispute variances within the window. Over-deducted cost, quantity gaps, deductions with no received goods — file them while records are fresh.
5. Route recall/quality events to the source. Recurring defective-return deductions belong on the quality team's desk, not just the deduction analyst's.

---

The Dispute Path

1. Pull the deduction detail: item, units, cost deducted.
2. Assemble the return file: authorization, receiving count, condition notes, original invoice cost.
3. File in APDP (Retail Link) for the variance — not the whole deduction, unless goods never arrived at all.
4. Keep the return documentation; the DB record is explicit that documentation is what validates (or challenges) the deducted amount.

---

Code 92 in the Returns Family

Walmart's 92–95 return codes differ by why the goods came back:

Code	Why it came back
92	Overstock or recall — often agreed or supplier-initiated
93	Visible damage on arrival
94	Defective, but not visibly damaged
95	Wrong item versus the PO

92 is the one where the return itself may be legitimate by design — which is why its discipline is reconciliation while 93–95 reward prevention.

Related: Code 93 · Code 94 · Code 95

---

Supplier Checklist

• Single register of all return authorizations (recall, overstock, defect)
• Returns received with full counts and condition notes at the dock
• Every Code 92 three-way matched: deduction ↔ authorization ↔ receipt
• Deducted cost checked against the original invoice line
• Variances filed in APDP within the dispute window
• Return documentation archived per event, retrievable by PO/invoice

---

FAQs

What is Walmart chargeback Code 92? A deduction taken when Walmart returns merchandise to the supplier — for example due to overstock or a supplier recall — deducting the value of the returned goods.

How much does Walmart deduct under Code 92? The cost of the returned merchandise. The deduction should equal the returned units at the invoiced cost — which is exactly what you verify.

Can I dispute a Code 92 deduction? Yes, through the APDP in Retail Link — typically for variances: cost deducted above invoice, quantities exceeding what was received, or deductions with no corresponding return. Keep return documentation; it's the evidence.

Is Code 92 a compliance failure? Often not. Recalls and agreed overstock returns are legitimate events. The failure mode is on your side of the ledger: absorbing deductions without reconciling them.

How is Code 92 different from Codes 93, 94, and 95? All four deduct returned merchandise. 92 covers overstock and recalls; 93 is visible damage; 94 is defects without visible damage; 95 is the wrong item versus the PO.

---