The weekly cost-letter triage: a category manager's workflow

If you run a category team in 2026, the most predictable item in your week is the email titled "Cost adjustment - effective [date]." It comes from a different supplier each time, the format is never quite the same, and the date is almost always inside the next four weeks. Multiply that by a few hundred suppliers and the math is obvious: cost-letter triage has moved from a corner of the procurement queue into the centre of the pricing workflow.

This is the operational counterpart to a question that gets framed too often at the boardroom level - "what's our tariff pass-through rate?" - and almost never at the desk level, where the actual decisions get made. The boardroom number is a portfolio. The desk number is one letter, one SKU set, one Friday afternoon. The retailers who are protecting margin through the 2026 tariff cycle are the ones who have built a weekly cost-letter triage workflow that a single category manager can run without drowning.

This piece is that workflow. It is not glamorous. It is what category managers we work with at mid-market retailers across CEE actually do on a Monday morning, and it is the difference between a clean book at month end and a queue of unresolved exceptions that nobody can explain.

What a cost letter actually contains (and what it leaves out)

The first operational mistake is treating the supplier cost letter as if it were a complete instruction. It is not. A typical letter contains: an effective date, a list of items or item groups, an old price, a new price, and a one-line reason ("raw material costs", "logistics", "tariff schedule", or - increasingly - "see attached schedule"). What it does not contain is everything you actually need to decide what to do about it.

What is missing, in roughly the order it matters:

• The tariff line breakout. If the letter cites tariffs, you need the specific share of the cost increase attributable to the tariff schedule, not just the total. Without that, you cannot model what happens when the schedule changes, and the schedule will change.
• The pre-letter unit cost. Many suppliers send the new price but not the old one, on the assumption that you know what you were paying. You do. Your pricing system might not - so the diff has to be computed and stored, not just the new figure overwritten.
• Effective-date precision. "Effective June 1" means different things depending on what cost you ship out of and what cost you apply on the shelf. The letter rarely distinguishes; the workflow has to.
• The replenishment cycle. A cost change on a slow-turning item arrives on your P&L months after the letter date. A cost change on a fast-turning item arrives in days. The letter never tells you this; your inventory data has to.
• The contract clause. Half the letters you receive are within the bounds of an existing contract. Half are not, and require a negotiation step before any pass-through decision is made. The letter never tells you which is which.

The first move in any cost-letter triage is to enrich. Treat the inbound letter as the trigger, not the answer.

Why batching to a quarterly review is the wrong cadence

Until roughly 2023, most mid-market category teams batched cost-change letters into a quarterly review. There was a reason. Cost letters were rare enough that batching produced a manageable agenda, and the consumer was anchored enough that a quarterly catch-up didn't produce visible shelf chaos.

That world is gone. The shift is documented in the academic literature - the Cavallo, Llamas and Vazquez paper estimates retail tariff pass-through at roughly 20 percent so far, with the rest still sitting upstream and rolling forward as inventory turns. Dallas Fed research from April now describes a "full pass-through" of tariff costs in aggregate. That aggregate is made up of thousands of individual supplier letters arriving at category desks, and the inventory cushion that used to slow them down has thinned to almost nothing.

The practical consequence: a letter that lands in week one of a quarter and waits until week twelve to be processed will have rolled through one full replenishment cycle on most fast-moving items. You will be retailing pre-letter prices on post-letter cost - which is exactly the gap that quietly costs two or three points of category margin and never shows up in a single review meeting.

Weekly is the right cadence not because supplier behaviour has become more aggressive, but because the lag the old cadence used to absorb is no longer there.

The Monday-to-Friday triage workflow

Here is the workflow we recommend, and the one a category team of any reasonable size can run with one analyst owning the queue.

Monday: ingest and enrich

The analyst opens the cost-letter inbox, sorts by effective date ascending, and enriches each letter with five fields before anything else happens. Old cost. New cost. Tariff-line share of the change. Affected SKU IDs. Replenishment-cycle bucket (fast, medium, slow). This is data work, not pricing work. If it takes more than ninety minutes for a week's worth of letters, your enrichment is being done by hand somewhere it should be done by rule. The output is a queue, not a decision.

Tuesday: classify into four buckets

Every enriched cost line lands in exactly one of four buckets. The bucket determines what happens next, and most lines should be obvious within ten seconds once the data is there.

Pass through (full or near-full). The item sits in the margin-sensitive middle of the assortment - real volume, weak external reference. The policy says pass through at near 100 percent. The line is auto-approved by rule, the change is queued for the next weekly wave, and the analyst moves on. Most of your queue lives here, and most of your queue should never see a human decision.

Defer to competitive reference. The item is in the competitive reference set - a key value item, a traffic driver, an item where the consumer is comparing against another shelf. The policy says pass-through is bounded by the reference set, not the supplier letter. Defer until the next competitive scan confirms what the reference set is doing. If the reference set moves, you move; if it doesn't, you hold and recover margin somewhere else.

Negotiate. The letter is outside the contract envelope, or the increase is meaningfully steeper than the supplier's recent track record, or the affected SKUs are private-label adjacencies where you have unusual leverage. These lines go to procurement before any retail change is contemplated. Mark them, do not act, escalate.

Reject or roll forward. The letter is malformed, ambiguous, or duplicates a previous notice that has not yet been actioned. Send back. Do not let unparseable lines sit in the queue - they distort the size of the exception backlog and demoralise the analyst running it.

Wednesday: apply

Take the pass-through bucket from Tuesday and apply it. In a structured pricing system this is a single weekly run that respects charm pricing, promotional cadence, and any KVI guardrails already in policy. Without a structured system, this becomes a spreadsheet, and the spreadsheet becomes the single largest source of category-margin error. If you are still doing this by hand on more than fifty SKUs a week, the operational problem is no longer the cost letters - it is the absence of a rule engine.

Thursday: measure

The analyst pulls the realised margin on every item touched in the previous week and compares it to the model. Two things are being measured. First, did the system apply the rule we asked it to? (A surprising amount of operational drift hides here.) Second, did the consumer respond the way we expected? (Volume drop, basket change, traffic change.) Thursday is short. The output is a two-line note: what behaved, what surprised us. Surprises feed back into policy.

Friday: decide what to escalate

The category manager - not the analyst - reviews everything that was deferred or flagged for negotiation. The Friday decision is what to escalate this week, what to roll forward, and which policies the week's data suggests are out of date. If three Friday reviews in a row land on the same policy, that policy gets rewritten, not patched.

What a healthy exception queue looks like

The single most useful operational metric in a cost-letter triage is the share of decisions that need a human. A well-run weekly queue should land somewhere around 5 to 10 percent of lines requiring category-manager judgement; the rest should clear through policy. If your queue is at 40 percent human decisions, the policy is too vague. If it is at 1 percent, the policy is probably too aggressive somewhere and you are about to discover where.

The diagnostic for "queue health":

• Queue size, week over week. Should be roughly flat. A growing backlog is the earliest warning that the rest of the workflow is broken.
• Time from letter to decision. Target five business days. Anything over ten is a sign that the Tuesday classification step is being skipped or done badly.
• Exception bucket composition. If "Negotiate" is more than 20 percent of the queue, your contracts are not protecting you. If "Reject" is more than 10 percent, your suppliers are sending you garbage and you should push back at the procurement layer, not absorb it in pricing.
• Realised margin vs. modelled margin. The variance should be small and unbiased. If you are systematically below model, the pass-through rule is leaving money on the table; if you are above, the consumer is absorbing more than your elasticity assumption predicted - which is a hint to revisit elasticity, not to celebrate.

Three traps that quietly break the workflow

Three patterns we see repeatedly in retailers who think they have a triage process but who are still leaking margin through the cost cycle:

Trap one: the cost letter becomes a folder, not a queue. The letter arrives, gets saved into a shared drive, and waits for "the next review." There is no enrichment step, no classification, no SLA. The folder grows. Margin erodes. The fix is operational, not cultural: the letter is a queue item the moment it lands, with a Tuesday classification deadline, or the inbox is broken.

Trap two: pricing and procurement talk to each other only at quarterly steering committees. The "Negotiate" bucket is meaningless if it has no operational handoff. The fix is a standing fifteen-minute Tuesday call between the analyst running the queue and the relevant buyer, focused only on the lines that landed in the "Negotiate" bucket this week. Most of those calls take five minutes. The ones that take fifteen are worth the slot.

Trap three: the analyst becomes the policy. This is the most dangerous trap because it looks like efficiency. One person learns the catalog, internalises every supplier's quirks, and starts making clean decisions without writing them down. When that person leaves - or just goes on holiday - the queue falls apart. The fix is to insist that every recurring decision the analyst makes is captured as a rule the system applies on its own. The analyst is the source of policy, not the substitute for it.

Where this fits in the wider pricing architecture

The triage workflow above is one specific operating routine inside a wider rules-based pricing model. It connects upstream to procurement (which negotiates the contract and the cost line) and downstream to the rest of the pricing engine (which applies the change, respects guardrails, and measures the response). If any of those three pieces is missing, the workflow above will fail in a predictable place.

The structured-pricing approach our team has been documenting at Retailgrid across pilots in CEE and the broader European mid-market is what makes the Wednesday "apply" step routine rather than a heroic spreadsheet effort. Most of what we hear from category managers we work with is not a request for more analytical sophistication; it is a request for fewer manual touchpoints in exactly this workflow. The triage discipline is the visible part. The boring rule engine sitting underneath it is what makes the discipline survive a busy quarter.

A one-page setup for next Monday

If none of the above exists yet in your team, the cleanest first move is one page, on Monday, owned by one analyst:

• A shared inbox or label that collects every supplier cost letter automatically.
• A spreadsheet (or, better, a queue in your pricing tool) with one row per cost line and the five enrichment fields above.
• A one-line policy per bucket - written down, not in someone's head.
• A 09:30 Tuesday slot to classify and a 14:00 Friday slot to escalate.
• One metric reported up to the C-suite weekly: queue size, human-touch rate, time-to-decision.

You will not need anything more than that for the first month. After that you will see exactly where the bottleneck sits, and the next investment - rule engine, competitive monitoring, contract overhaul - becomes obvious.

The retailers who are quietly holding margin through the 2026 cost cycle are not the ones with the most sophisticated elasticity models. They are the ones who have made cost-letter triage a routine instead of a heroic effort. The workflow above is the routine.

If you want a copy of the classification rule template our team uses with pilot retailers, we are happy to share it - drop a note via retailgrid.io/contact.