Trade is the second largest line in most consumer brands and the least legible. The plan lives in a spreadsheet by account, the commitment lives in an email, the money leaves as a deduction on a remittance six weeks later, and the lift it bought is somewhere in a retailer file that arrives on a different calendar.
Every category of trade spend management software claims to close that loop. The way to compare them is to follow one promotion through it, because each category breaks at a different point, and the point where it breaks tells you what the tool was built for.
Follow one promotion end to end
Take a four-week feature at one account, planned in March, executed in May, deducted in June, reviewed in July. Six things have to line up for the review to mean anything.
- The plan: which products, which weeks, which mechanic, and the spend committed against it.
- The accrual: what finance booked while the promotion ran, and on which volume basis.
- The shipments: what moved to the account in the promotion window, which is rarely aligned to the weeks you planned.
- The deduction: what the account took off the invoice, described in their reference format rather than yours.
- The sell-through: what left the shelf during the feature and in the two weeks after it, which is where the borrowed volume shows up.
- The baseline: what would have sold without the promotion, which is a modelled number and needs to be labelled as one.
The failure mode is almost never the maths on any one of those. It is that the six live in five systems with three product identifiers and two calendars, so matching a deduction to the promotion that caused it becomes a person with a spreadsheet and a good memory (the same person every quarter, and they know it). Brands that cannot make that match do not know their trade ROI, whatever number the deck says.
The categories of trade spend management software
Trade promotion management suites are built around the plan. They hold the promotional calendar, the funds by account, the approval workflow and the accrual, and they are the right purchase when the planning process itself is the mess: commitments made in email, no view of remaining funds, a national account manager who overspends because nobody could tell them what was left. Their weak point is the back half of the loop. A suite knows what you planned to spend, and it learns what you actually spent only if the deductions and shipments flow into it cleanly from systems it does not own.
Deduction and claims specialists start from the other end. They live on the remittance: coding deductions, matching them to agreements, and chasing the invalid ones. Where a brand is losing real money to unauthorised deductions and short pays, this is the fastest payback of anything in the category, and it is a narrow tool by design. It will not tell you whether the promotion was worth running.
Revenue growth management and analytics platforms model the question you care about: elasticity, promotion lift against a baseline, which mechanic works at which account. The modelling is the easy half. Every one of them assumes a clean, joined history of shipments, sell-through, price and spend, and the assumption is doing more work than the model. Ask what happens when the retailer restates a month.
Spreadsheets and ERP deduction reports remain the honest baseline for a brand with a handful of accounts. NetSuite or QuickBooks codes the deduction, your spreadsheet holds the plan, and the gap between them is filled by a person. That works until the fourth retailer arrives, or until the person takes a holiday during the quarter close.
| Category | Owns | Leaves to you |
|---|---|---|
| Trade promotion management suite | Plan, funds, approvals, accruals | Matching real spend and lift back to the plan |
| Deduction and claims specialist | Coding, validity, recovery of short pays | Whether the promotion earned its money |
| Revenue growth management analytics | Baseline, lift, elasticity models | The joined history the model assumes |
| Spreadsheet and ERP reports | The plan and the raw deduction codes | The join, every cycle, by hand |
Where we fit, and where we do not
We are not a trade promotion management suite. We do not hold your promotional calendar, run an approval workflow, or raise a claim against a retailer, and a brand whose planning process is the problem should buy a suite for that.
Permute is the layer that makes the loop joinable. We connect the ERP, the retailer portals, the distributor files, the spreadsheets where the plans live, and the rest of the systems we connect, then resolve accounts and products so a deduction reference, a shipment line and a retailer item number land on the same record. Net revenue, promotional spend and lift are defined once as explicit rules in the Ontology layer, so the ROI a trade manager quotes and the ROI finance quotes come from the same definition rather than two workbooks that were right in different ways. Ask which promotions ran below their planned return last quarter and the answer arrives with the deductions, shipments and sell-through rows behind it, which is what makes it survive a conversation with the account. Access is governed in the same place, so a broker sees their own accounts and no one else, and a retailer restating a month shows up as a restatement instead of moving a number you already presented.
Two further limits. We read from the systems we connect and never write back, so the accrual entry and the claim are still raised where they belong. And the baseline in any lift calculation stays a modelled number: we can hold the definition and the inputs, and we are not a forecasting engine that produces the counterfactual for you.
Match one quarter of deductions to their promotions
Connect your ERP, a retailer feed and the plan spreadsheet, then see how much of the spend lands on a promotion.
The questions to ask a vendor
Bring a real promotion and a real remittance to the demo, ideally one that went badly. Then ask the four questions that separate the tools.
- Show me this deduction matched to this promotion, using our reference format, without a manual mapping step.
- Show what happens to last quarter's reported ROI when a retailer restates a month after we closed it.
- Show the same lift number to a trade manager and to finance, and tell me where the definition of net revenue is written down.
- Show which of our accounts a broker can see, and prove they cannot see the account next door.
- Show what the number rests on: the source rows for one deduction, without an export.
A tool that handles the first two is doing the work. For the wider tooling picture, CPG analytics software: what to look for before you buy sets out which category owns which part, and How to automate POS data analysis covers the retailer feeds every lift calculation depends on. Consumer brands weighing this against a headcount will want what it costs alongside the software quotes.
Bring one promotion that went badly
We will trace it from plan to deduction across your systems and show where the trail goes cold.
Questions finance teams ask about trade spend
Should we buy a planning suite or an analytics tool first?
Buy for the half that is failing. If commitments are made in email and nobody knows the remaining funds by account, the planning suite pays for itself in control. If the plan is orderly but no one can say what a promotion returned, the problem is the joined history rather than the calendar.
Brands that buy analytics while their spend data is unmatched usually end up with a well-presented version of a number they already distrusted.
How should off-invoice and billback spend be handled?
As two different events with one definition of net revenue. Off-invoice reduces the price at the point of sale, billback arrives later as a deduction or claim, and treating them as interchangeable makes net revenue depend on which mechanic the account happened to prefer.
The rule to write down is where each one lands relative to gross sales, and then to apply it the same way in the trade review and the management accounts.
What about spend that runs through distributors?
Distributor markets are the hardest part, because the depletion data arrives later, in the distributor format, and often without the store detail that would let you attribute lift. Treat the distributor report as its own feed with its own lag rather than folding it into retailer numbers.
The practical target is knowing which depletions sat inside a promotion window, even where store-level attribution is not available.
Does this help with invalid deductions?
Indirectly, and it is worth being precise about the difference. A claims specialist chases the recovery, which is the part that gets money back. What a governed layer contributes is the evidence: the agreement, the shipment and the sell-through behind a disputed deduction, assembled before the window to contest it closes.
Most of the loss we see in practice comes from deductions nobody had time to investigate rather than from claims that were fought and lost.