A growing CPG brand found a 70% trade rate at a single grocery account, hidden inside a distributor deduction bucket labeled Turnover. Every line in it was valid: free fills, case stacks, displays and show deals, and each one cleared correctly. Until someone grouped and added them up by retailer, there didn't seem to be a problem. In this article, I explain how trade spend leaks into catch-all deduction codes, why line-by-line processing (AI included) can still miss it, and what the outcome of this finding was.
Recently my team was on a client’s weekly trade call. Ordinary agenda. Next year’s budget was due in a few weeks, private label data was getting loaded, somebody needed a list of food service items with case costs. Then one of our client managers pulled up a retailer view and the room went quiet.
One grocery account. A little over $100K in sales for the fiscal year. Deductions came to roughly 70 cents of every one of those dollars.
Seventy percent. At a single retailer.
The fair question is whether that is simply what it costs to get going in a new account. It was not. Nobody had approved a 70% trade rate. No budget line carried it. Several of the programs inside it ran against what the brand had told its broker it wanted. And nobody had ever seen it as one number, so nobody had the chance to object.
I have been doing this for 20 years and reading the notes still made my stomach drop, because I know exactly how that happens and I know how many brands have the same number sitting in their report right now, under a label they have never opened.
The money came through the distributor and landed in a bucket called “Turnover.”
Turnover sounds self-explanatory. Product went out, product came back, the cost of doing business in grocery. On UNFI’s published code list it means a one-time order discount for a store or group of stores, written by the broker or by the vendor. Perfectly legitimate. But also perfectly vague.
Here is what was actually in it:
Free fills for new item placements.
A free case to get a SKU on shelf.
Free fills for distribution voids. Same thing, used to patch holes where the item should already have been.
Case stack deals the broker’s impact team set up.
Displays at rates the brand never priced as a promotion.
Show deals at a 50% MCB (manufacturer chargeback). Negotiated at a trade show, entered as a chargeback, filed under the closest thing.
Not one of those lines is wrong. Every one of them has a story a reasonable person would nod at. A few hundred dollars here. A free case there. A display for a week.
And that is the whole mechanism. Trade spend does not get away from you in one bad promotion. It gets away from you in a bucket nobody owns, growing line by plausible line, until the total is the worst trade rate on your customer list and the label still says Turnover.
Trade spend is one of the largest lines on a CPG P&L, often second only to cost of goods. The part of it you did not decide to spend is the part that lives in buckets like this one.
An accurate report of a bad program looks exactly like an accurate report of a good one. Most brands assign someone to clear that bucket. Almost none assign someone to read it.
This is the part I want brand leaders and executives to sit with.
If our client had relied on an AI-led deduction tool alone, every one of those lines would have been handled flawlessly. Pulled from the portal. Coded to T for Turnover. Backup attached. Cleared. Month after month, the dashboard would have shown the Turnover total, and it would have been correct. And the brand would have kept absorbing it without question into the next year, and beyond.
> Read: 7 Reasons AI Alone Won’t Solve Deduction Management Challenges
Why? Because a line-level tool using AI to process deductions answers one question per line: what is this, and is it valid? It is very good at answering that question. Our deduction platform (part of our CPGenius Deductions service) uses AI to do most of the reading, coding and matching, and I would not run a deduction operation without it.
But a deduction can be contractually valid and still be evidence of a program that should not exist.
There are additional questions that only a human with experience would ask if they reviewed those lines. Questions like: “Should this spend exist at all?” or “What does it say about how we are selling to this retailer?” and “Who agreed to a 50% MCB at a trade show, and would they agree to it again if they had to write it down first?”
Nothing in a single line looks wrong. So nothing in a single-line workflow will flag it. The 70% trade rate only becomes apparent when the lines are aggregated by retailer. Software (like CPGenius Trade) can do that math and flag a high trade rate. But a flag on a screen still doesn’t kill a case stack program, set a free fill approval policy, or sit across from the distributor. That takes a human with experience to know that the number is insane — with the authority to change the program, and the standing to make it stick.
The biggest problem with AI-led deduction management tools is not even with the vendors — it’s with buyers that assume they are getting a complete solution and strategy from an automation platform.
When nobody owns asking the questions, the problem tends to surface months later as a budget variance, rather than on the day a person could have done something about it.
Same data. Same platform. The difference was who was in the room and what they were allowed to decide. Four things came out of that call, and I want to be specific about why each one is a judgment call and not a workflow.
Somebody had to say the broker’s display program was not worth what it cost and take it out of the plan. That is a commercial decision that will annoy a broker. A tool does not make decisions that annoy brokers.
Free fills are a real tool. The problem was that they were being written by the broker and the sales team without anyone on the brand side approving them. Now two named people have to say yes. That is a policy, and it needs someone with authority to set it and someone with a spine to enforce it.
You cannot negotiate with a high-level dashboard. You negotiate with a person who understands the detail behind what those codes actually mean — and can confidently dispute what is Turnover and what is not.
The distributor’s own velocity and late shipment reports show these claims early. The sales team validates them with supply chain and pushes back while they are still claims. Compliance fees are published and individually small — a missing packing slip or a late ASN runs from around $100 to a few hundred dollars — and they arrive constantly. Somebody had to decide that catching them upstream was worth building a weekly habit around.
None of those decisions needed new software. They needed people who read the bucket, understood what it meant, and had the standing to change it.
Here is what I believe after 20 years of this, first as a brand founder on the receiving end of the deductions and then as someone who has watched hundreds of brands go through the same thing:
A brand does not have a fighting chance against retailers and distributors unless there is someone on its side whose job is to read the money, not just clear it.
Someone who looks at trade rate by retailer as a decision, not a report. Someone who knows what normal looks like because they have seen enough distributor programs to recognize a show deal hiding under a Turnover code. Someone with the authority to say a program dies next year, and the standing to sit across from the distributor and make it stick.
That person can be on your payroll. If you are big enough to justify an experienced trade analyst who has seen enough to know what is insane, hire them and give them the data and the authority. Most brands between $10M and a few hundred million are not there. The volume does not justify a full team, and the person who can do the job is expensive and rare.
That is why expert teams exist, embedded or outsourced. The point is to get the judgment without carrying the headcount, from people who see the same pattern across many brands and know to open a bucket like that before it becomes the worst number on the customer list.
I run a company built on exactly that model, expert-led and AI-assisted, so weigh my opinion accordingly. But I built it that way because I had bought software before, used a fraction of it, and watched the trade rate drift anyway while every deduction was technically handled.
Whoever you use, in-house or partner, ask them five things. Ask for the evidence, not the answer.
Show me trade rate by retailer for an account like mine — the actual report you would hand me in month two, not a sample dashboard.
When a bucket grows, who opens it, and when? Name the person and tell me the last time it happened.
Who has the authority to recommend killing a program, and when did they last do it?
Will you sit in the distributor conversation with us? Tell me about the last one you sat in and what you asked for.
What gets disputed before it becomes a deduction, and who owns it? Show me a claim you killed before it posted.
If the answers come back as “the dashboard shows it,” you bought processing. Processing is necessary. It is not a fighting chance.
If you have a Turnover bucket, open it this week. Not the total. The lines. You might be surprised by what you find.