The Q4 deduction cliff runs October through February and hits three separate waves. OTIF fines and ASN failures peak in November when volume is highest against the tightest routing windows. Shortage and receiving claims peak in December when DC receiving speeds up and error rates rise. Markdown deductions under code 10 and returns under codes 92, 93, and 94 peak in January and February, after post-holiday sell-through gets counted. A supplier that plans against one flat Q4 chargeback rate underestimates the risk in each specific window.
Based on public deduction and OTIF documentation from BOLD VAN, Endless Commerce, SPS Commerce, SupplyPike, and Supply Chain Dive, September 2026. Retailer deduction volumes and program details vary by account and year.
You’re the Director of Finance at a $50 million CPG supplier. Your last three January remittances arrived with the same complaint from the Ops team: “Something’s wrong with Walmart, our chargebacks doubled.” Your CFO wants a Q4 forecast for deduction exposure before the board meeting in early October. You have three years of data, and the pattern in it is not what your team has been calling it.
The Q4 deduction cliff is not one big spike. It is three separate waves that arrive on different remittances, driven by different root causes, requiring different dispute plays. A team that treats them as one problem staffs its dispute capacity wrong, disputes the wrong lines first, and misses the seven-day window on the ones worth fighting.
The Endless Commerce recovery window closes fast: 75 to 80 percent win rates inside seven days, 15 to 20 percent after 60. When your November fine, your December shortage claim, and your January returns all hit inside 90 days of each other, an overloaded dispute team means you cover the wrong ones. Understanding the cliff month by month is the setup for staffing to it.
Wave 1: OTIF and ASN chargebacks peak in November
October is the ramp. November is the peak. Volume climbs against routing windows that either narrow for peak (Target, Home Depot) or hold flat while volume rises (Walmart), and the fill-rate math turns against you either way. Walmart’s OTIF fine is a program-level chargeback measured on your aggregate on-time and in-full rate, and the rate math punishes a bad November harder than a bad June because your November denominator is larger.
The failure modes are the same ones you see mid-year, just at higher volume. EDI 856 rejections that were a small percent of transmissions in July become a large absolute number in November. Missed appointments that were 3 or 4 a month become 15 or 20. Every one of them is a per-shipment ASN chargeback under a code like Amazon’s ASN Accuracy or Target’s ASN Accuracy Violation, on top of the aggregate OTIF hit.
The measurement window and the payment window are not the same. Your November scorecard lands on the November measurement, but the fine itself often hits your check in December or early January. If your finance team measures deduction risk by remittance date, the November miss looks like a January problem, and root cause traces get muddled by the offset.
Wave 2: Shortage and receiving claims peak in December
December runs your co-packer, your DC, and your carrier network at maximum throughput. Retailer receiving runs the same way. When receivers process at speed, the count-error rate rises, and Walmart code 22 shortage claims, Walmart code 25 no merchandise, and Target SIFR short-ship claims rise with it. Some of those are real shortages. Many of them are counting failures at receipt that a portal comparison would resolve.
The dispute economics on shortage claims are the best in the deduction stack when handled fast. A walmart shortage claim has strong evidence available if you have signed BOL and receiver-scan detail, and the seven-day window closes on the exact December remittance dates when your Ops team is busiest with peak execution. This is the mismatch that costs suppliers the most recoverable dollars: the disputes with the highest odds sit unfilled because the team is buried.
The remittance parsing routine becomes the load-bearing daily task in mid-December. If it is not already automated, it will not be automated in time, and manual parsing at peak is where the seven-day window gets missed.
Wave 3: Markdown and returns deductions peak in January and February
The largest single line on many CPG suppliers’ January remittance is not an OTIF fine or an ASN chargeback. It is a markdown deduction under Walmart code 10 or a returns deduction under one of the returns family codes: 92 for overstock, 93 for damaged, or 94 for defective.
The lag is structural. Consumer returns from Black Friday and December sit in stores or reverse logistics for weeks. Post-holiday markdown decisions get made in early January and processed against supplier accounts over the following six weeks. By February, the returns wave is still landing. That is why the two remittances after the peak often run larger than any remittance during it. The volume is there in December, it is just not counted yet.
Two of the three returns codes carry a strong dispute case if your team has the documentation. Code 93 damaged and code 94 defective often reflect handling and reverse-logistics wear rather than pre-shipment quality failures. The dispute play depends on inspection photos, receiving condition records, and a per-unit shipment trail that is expensive to reconstruct after the fact. Suppliers who capture this data at outbound QC as a matter of routine dispute successfully. Suppliers who do not, cannot.
The month-by-month table
| Month | Wave 1 (OTIF/ASN) | Wave 2 (Shortage) | Wave 3 (Markdown/Returns) | What to staff for |
|---|---|---|---|---|
| October | Ramp, moderate | Moderate | Low | Baseline dispute team |
| November | Peak: OTIF fine measured on aggregate | Rising | Low | Add capacity for ASN chargeback triage |
| December | Elevated, tapering | Peak: code 22, 25, SIFR | Rising | Staff seven-day dispute window on shortage claims |
| January | Fine payments land, tapering | Elevated | Peak: code 10, 92, 93, 94 | Reserve capacity for markdown and returns disputes |
| February | Low | Elevated tail | Elevated tail | Close out Q4 disputes before windows expire |
The staffing implication is direct. If your dispute team runs at flat capacity through the quarter, they cover the wrong months. The seven-day window on December shortage claims closes while they are still writing up November OTIF disputes. The seven-day window on January returns closes while they are still working December shortages. Staggered peak load, staggered dispute effort.
How to plan against the cliff
Three moves cover the majority of the recoverable exposure.
The first is dispute staffing to the calendar. If your dispute team is one full-time person, they need surge capacity or a queue-priority system for December and January. The seven-day rule is not a preference. It is the difference between 75 percent and 20 percent recovery odds.
The second is evidence capture during peak, not after it. Every shipment in November and December needs signed BOL, driver photo of loaded trailer, and receiver-scan detail pulled and stored within 48 hours. The retail deduction evidence pack covers what a defensible dispute file looks like. If your team does not have that pack ready by October, it will not be ready in time for the December shortage window.
The third is remittance parsing that runs on a daily cadence during Q4. Weekly is too slow. If a Walmart code 22 hits your account on December 12 and your team sees it on December 22, the seven-day window is already closed on half the batch. The Monday morning deduction triage becomes a Tuesday-through-Friday routine during the peak, not a weekly review.
What to do next
Pull three years of monthly deduction totals for October through February. Sort by deduction code family. The pattern in the data tells you whether Wave 1, Wave 2, or Wave 3 is your biggest exposure. Then staff and evidence-capture against that specific wave first, not against a general sense that Q4 is expensive.
The OTIF Deduction Assessment traces the recoverable share of your last 90 days of scorecard and remittance data, which is the right lens if Wave 1 is your biggest line. The Forecasting Assessment is the right lens if Wave 3 dominates, since post-holiday markdowns and returns trace back to a peak-plan decision made in September.
For a rough number on the aggregate exposure, the OTIF deduction calculator gives you a 5-minute estimate on the OTIF band of the cliff. To convert this timing view into a per-account plan, read how peak-season routing guides tighten at each retailer alongside this calendar.
The disclaimer: retailer program details, chargeback thresholds, and dispute windows change without notice. Verify current specifics in your own retailer portal before acting on anything reported here.
Frequently Asked Questions
- Which deduction types actually spike in Q4?
- Three families spike, at different times. OTIF fines and ASN-related chargebacks peak in November because peak volume runs against tighter routing windows. Shortage and receiving deductions like Walmart code 22 and Target SIFR peak in December because DC receiving throughput rises and error rates rise with it. Markdown deductions like Walmart code 10 and returns under codes 92, 93, and 94 peak in January and February, when the retailer counts through post-holiday sell-through and returns.
- When does the peak-season OTIF fine window end?
- The measurement window and the payment window are different. The measurement window at Walmart, Target, and Kroger typically covers the receiving month, so a November miss shows up on your November scorecard. The fine itself often lands on the following month's remittance, so a November scorecard fine may not hit your check until late December or January. If your team measures deduction risk by remittance date rather than shipment date, the November miss looks like a January problem, and the root cause looks blurry.
- Why do returns deductions land in January instead of during the holiday?
- Retailers batch returns processing. Consumer returns from Black Friday and December sales sit in stores or reverse-logistics centers for weeks before they process against your account. Walmart returns codes 92, 93, and 94 typically show up on remittances 30 to 90 days after the Christmas peak. That is why the January remittance often runs materially larger than any month in Q4 itself. The volume is there, it is just not counted yet.
- Should I reserve dispute capacity for Q4, or spread it evenly?
- Do not spread it evenly. Endless Commerce reports dispute win rates of 75 to 80 percent when filed within seven days and 15 to 20 percent after 60 days. Your November OTIF fine hits your check in December. Your December shortage claim hits in January. Your January returns hit in February. If your dispute team is running at capacity through the peak, they miss the seven-day window on the exact deductions with the highest recovery odds. Staff the dispute window to the calendar, not to an average month.
- How large is a typical Q4 deduction cliff for a $50M CPG supplier?
- Deduction burden varies with retailer mix and program details, but a common pattern for a $50 million CPG supplier at a Walmart, Target, Amazon 1P, and Kroger mix: November through February deductions run 1.5 to 3 times the mid-year monthly average, driven by OTIF, shortage, and returns codes in sequence. That is $50,000 to $150,000 of additional exposure across the four-month window compared to a mid-year baseline, before any specific program change lands.
Find out what your deductions are actually costing you.
A 30-minute call with the founder, who will tell you which of the three scans fits your problem, or that none of them do.