Unsaleables Spike? Audit Excessive Defectives Fast
- The HRG Team
- Mar 2
- 3 min read
If your month-end feels weird lately—sales look fine, but net receipts don’t—“excessive defectives” is one of the first places finance should look.
Not because every claim is wrong. Some are absolutely valid.
But because defectives/unsaleables are where real-world chaos (handling, rotation, returns, damage) collides with automated systems, shifting retailer rules, and messy data. That’s the perfect recipe for overbilling, miscoding, and duplicates.
And the broader pressure is enormous. NRF projected total retail returns at $890B in 2024 (16.9% of sales) and $849.9B in 2025 (15.8%). When retailers are fighting that level of cost, they’re tightening controls and pushing harder on recovery. Suppliers often feel pressure downstream due to defectives, unsaleables, and chargebacks.
The only definitions leaders actually need
Teams get stuck arguing labels. Finance should care about mechanics:
Defectives: product deemed unsellable for a reason (damage, spoilage, etc.).
Unsaleables: a broader bucket that may include defectives plus other non-sellable outcomes.
OS&D (over/short & damaged): often tied to shipping/receiving discrepancies and damage events.
Why it matters: the “bucket” can drive which policy, window, and rate gets applied.
Wrong bucket = wrong rules.
A clearly fictional scenario (but very common)
Imagine you’re shipping steadily. No packaging change. No route change.
Then defective deductions jump 35%—but only in one region. Operations starts investigating packaging. Sales shrugs. AP logs it and moves on.
Later, you find the “spike” began the same week a DC changed how it coded unsaleables. Some claims were valid. Some were duplicates. A chunk was outside the allowable timing window. Nothing about your product changed.
Only your cash did.
Seven red flags that usually point to recoverable leakage
Duplicate hits (same event, different codes or cycles)
Out-of-window claims (timing doesn’t fit the retailer’s own rules)
Wrong rate/program applied
DC or region spikes with no shipment change
SKU/pack transitions triggering bad mapping
Thin support (deducted first, explained later—if ever)
Math that won’t reconcile (units/cases/weights don’t tie to shipment reality)
30-minute “Excessive Defectives Hot Map” that finance teams love
You don’t need a giant data project to diagnose this.
Pull every defective/unsaleables line you can for a defined window and capture just these fields: Retailer, code, invoice/PO, ship date, claim date, DC/store/region, SKU/UPC, units, dollars, reason.
Then sort into three ways:
Top DCs by dollars
Top SKUs by frequency
First date the spike began (trend break)
That’s it. If a single DC is responsible for a disproportionate share, you have a lead. If a single SKU or pack transition correlates with a lead, you have a lead. If the timing is clustered, you have a lead.
This is where “it’s just the cost of doing business” often falls apart.
The proof checklist that actually closes disputes
Disputes die when the evidence is vague. A strong challenge typically needs:
A traceable reference from the deduction line to the alleged event
Disposition/inspection documentation, where applicable
Timing evidence (when the event occurred vs. when it was claimed)
Unit and value logic that ties back to shipment truth
If you can’t tie a deduction to a provable event, it shouldn’t get a free pass just because it has a scary label.
Prevent repeat hits (the fixes that pay back)
The best recovery programs don’t just win dollars; they reduce recurrence.
Common preventers:
Packaging and pallet pattern adjustments targeted to the specific DCs, creating damage
Item setup hygiene during UPC/pack transitions (a big source of “wrong vendor/wrong SKU” charging)
A simple monthly KPI dashboard: defectives $ as % of net sales, $ by DC, recovery rate, cycle time, top 3 root causes
Where HRG fits
Most supplier teams aren’t ignoring defectives because they don’t care. They’re ignoring them because the claims are high-volume, cross-functional, and annoying to validate.
HRG helps teams separate valid from invalid, build dispute-ready support, recover what’s recoverable, and—just as important—identify the patterns that keep defectives from becoming a permanent margin haircut.
