The cost increase request: how to actually move COGS through a retailer's gate.

Your factory just sent the email. Resin is up 18 percent, the ocean lane added a $1,400 surcharge, and the new tariff line item on the steel components lands on the August invoice. Your landed cost on the SKU just moved $0.41 per unit. Your first instinct is to forward it to your buyer with a one-line explanation and an ask for a price relief.

That email is almost always the wrong move. Cost increase requests at national retail are a structured, document-heavy, calendar-driven process — not a conversation. The vendors who get their CIRs approved walk in with a 12- to 18-page packet, a 120-day runway, and an index-based methodology the buyer's category-finance team can audit. The ones who fire off an email get a polite "submit through the portal" reply and a quiet rejection 60 days later.

Here's the actual machinery behind a cost increase at a major retailer, and the timing and documentation discipline that decides whether your number gets through.

What a cost increase request actually triggers inside the retailer

The moment your CIR hits the buyer's portal, it kicks off an internal review chain that most vendors don't see. At a typical Walmart, AutoZone, or O'Reilly the sequence runs roughly like this:

1. Buyer triage. Did the request arrive with a complete documentation packet? Is it inside the policy window? If not, it's bounced back with a generic "resubmit with required documentation" response and a 30- to 60-day delay built in.
2. Category finance review. A category-finance analyst — not the buyer — audits the math. They check your component cost story against published commodity indexes, verify your freight numbers against published lane rates, and compare your request against other vendors in the category who may have already filed.
3. Buyer recommendation. The buyer drafts a position: approve, partial approve, reject, or counter. The buyer's recommendation is the single biggest factor in the outcome, but it's not the final word.
4. Category leadership sign-off. Anything above a threshold dollar value — typically anything that moves category retail price by more than two or three percent — escalates to the senior category director, sometimes to the divisional VP.
5. Pricing rollout decision. If approved, the retailer decides whether to absorb the increase (eat it themselves, hold retail), pass it through to retail (move shelf price), or split the difference (eat some, pass some). This decision often takes longer than the approval itself.

The entire chain runs 60 to 120 days from clean submission to effective date. A messy submission can stretch to 180. And every retailer has a window during the year — typically 90 to 120 days before a category line review — when CIRs are functionally frozen because the category is already in planning mode.

The documentation packet retailers actually expect

The single biggest reason CIRs get rejected is incomplete or unverifiable documentation. A serious cost increase packet has six sections, and missing any of them adds 30 to 60 days to the review:

1. Component cost bridge. A line-by-line breakdown of the SKU's cost stack — resin, steel, electronics, paperboard, labor, freight, overhead, factory margin — showing the old number and the new number for each line. The buyer's category-finance team is going to rebuild this themselves, and they want the bridge that matches what they're going to find. Hide nothing.

2. Third-party supporting documentation. Mill quotes for resin moves. Published bunker fuel indexes. Ocean carrier rate sheets. Section 232 / Section 301 tariff filings. The buyer doesn't take your word for any of it. Every line in your bridge needs an external source they can verify in 90 seconds. The retailers who run CIRs hardest — Walmart and AutoZone in particular — have analysts who can pull a CME resin index, a Drewry container rate, and an HTS-coded tariff schedule before lunch. Don't make them go looking.

3. Index methodology, not a snapshot. If you anchor your request to a one-week snapshot of the resin market and resin softens two weeks later, your request looks opportunistic and gets rejected. Anchor to a trailing 90-day or 180-day index average. Show the trend line. Make the methodology auditable.

4. The mitigation paragraph. What have you already absorbed before submitting this request? Have you re-sourced? Renegotiated with the factory? Cut overhead? The buyer is grading you on whether you tried to solve this internally first. A vendor who eats the first $0.12 of a $0.41 move and asks for $0.29 looks like a partner. A vendor who passes through every cent looks like a problem.

5. The competitive context. What does the same cost move mean for the competitive set? If your competitors face the same input pressures, the buyer's finance team will assume so. Acknowledging it openly — "we expect similar requests across the category in the next 60 days" — actually strengthens your position, because it tells the buyer your number isn't an outlier.

6. The retail impact analysis. What does the request mean at shelf? Do you propose passing through, absorbing, or splitting? If you're proposing a retail change, run the elasticity math on the new price point. Show the buyer you understand the GMROI consequence at the new cost.

A complete packet runs 12 to 18 pages plus appendices, and takes a real vendor's pricing and finance team three to five weeks to assemble. Smaller vendors who treat this as a one-page request consistently lose to larger vendors who treat it as a finance-grade deliverable.

The math: a $0.41 cost move on a 600,000-unit program

Run the numbers on a typical wiper or detailing SKU at a mid-tier national program:

• Annual units: 600,000
• Old landed cost: $4.10
• New landed cost: $4.51 (a $0.41 / 10 percent increase)
• Old wholesale: $7.00
• Annual COGS impact, unmitigated: 600,000 × $0.41 = $246,000

Three scenarios for what happens after submission:

Scenario A — vendor eats it (no CIR filed): $246,000 straight out of gross margin. On a program previously running 41 percent gross margin ($1.74M GM), the new margin runs $1.49M — a drop from 41 percent to 36 percent. Five points of margin gone in one quarter.

Scenario B — full pass-through approved: Wholesale moves to $7.41. Retailer either absorbs (their margin compresses by 41 cents) or passes through to retail. If retail moves from $13.99 to $14.49 to preserve retailer margin, elasticity kicks in. A 3.5 percent retail increase on a price-sensitive consumable typically pulls 4 to 7 percent of unit velocity. Units drop from 600,000 to roughly 565,000. Your COGS recovery is full, but the program shrinks by $35,000 in unit count — and the buyer's category dollars shrink with it.

Scenario C — split (you eat $0.12, retailer takes $0.29): Most common real-world outcome at a national chain. You absorb $72,000 of the $246,000, the retailer absorbs the rest through either margin compression or a controlled retail bump. Your margin moves from 41 percent to roughly 40 percent. Manageable.

The vendors who file disciplined CIRs end up in scenario C far more often than scenario A. The vendors who file no CIR — or file a sloppy one — sit in scenario A by default.

Timing: the calendar window that decides the outcome

The most expensive mistake on a CIR is filing it inside the wrong window. Every major retailer has a category-planning calendar, and CIRs filed during planning hit a wall.

For a category whose line review lands in March, the buyer's internal planning kicks off the prior September. The CIR window for cost increases that need to be effective by the new program year (typically February-March) is roughly June through August — 90 to 150 days ahead of the planning kickoff. File in October and your request is technically still accepted, but the buyer's response is some variant of "we'll address this at line review." That answer is functionally a six-month delay.

For a fall reset (September-October line review), the corresponding CIR filing window is January through March.

The rule of thumb that works across retailers: file CIRs 120 to 150 days before the category line review you want them effective for. Inside 90 days, the buyer rolls everything into the line review negotiation. Outside 180 days, your request sits in a queue and gets reviewed in batches.

Three CIR failure modes that show up over and over

The three reasons CIRs most commonly get rejected, in order of frequency:

1. Insufficient external documentation. "Resin is up" is a claim. "PE film resin spot pricing rose 14 percent on the CME contract over the trailing 90 days, attached" is a verifiable fact. The buyer's analyst will take 30 seconds to confirm the second one. The first one bounces.
2. No mitigation story. Filing a CIR without showing what you've already done internally — re-sourcing efforts, alternative materials evaluated, factory negotiation summary — signals to the buyer that the vendor is using the CIR as a first response, not a last resort. Buyers reject these reflexively.
3. Timing inside the line review window. A CIR that lands while the buyer is in active line review prep — typically the 90 days before pitches — gets bundled into the line review conversation, which is the worst possible position for the vendor. You lose the ability to negotiate cost separately from program structure, and the buyer can now trade pricing relief against case-pack changes, MOQ commitments, or MDF concessions that would otherwise be separate conversations.

The internal discipline you need before the first CIR

Vendors who run CIRs well share three operational habits:

• A monthly cost-of-goods review that flags any SKU whose landed cost has moved more than two percent since the last review. The review surfaces the request candidates before the factory invoice forces the conversation.
• A standing relationship with a pricing analyst — whether internal or fractional — who can build the documentation packet on demand. The vendors who lose CIRs are the ones whose CEO is also the de facto pricing analyst on top of every other job.
• A CIR calendar by retailer that maps each major account's line review windows and works backward 120 to 150 days to identify the filing windows for each. The calendar is built once and updated annually.

What this means for your next line review

If you're sitting in June and you have a known cost move coming in Q3 or Q4, the right move is to file the CIR now — not at line review. The vendors who walk into a line review with their CIRs already filed and the new wholesale already approved have a clean negotiation in the room. The vendors who walk in with the cost story still open are negotiating two things at once — cost and program — and they almost always lose at least one of them.

The rule that matters: cost is a separate conversation from program structure. File the CIR on its own calendar, with its own packet, in its own window. By the time the line review starts, the cost stack should already be settled — and the only thing left to negotiate is the program itself.

That's the operating discipline that separates vendors who hold margin from vendors who quietly bleed it across the program year.