.png)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Procurement Guide How Are Trade Promotion Management TPM Platforms Priced for Consumer Goods Enterprises
For a consumer goods enterprise, the difficult question in a Trade Promotion Management procurement is rarely whether the platform can plan a promotion. SAP, Salesforce, Anaplan, Aforza, UpClear, Visualfabriq and Vistex all offer versions of promotion planning, forecasting, fund management, settlement or post-event analysis. The harder question is what the enterprise will actually pay once more countries, users, products, customers, records, integrations and adjacent revenue-growth capabilities enter the system. As of 14 August 2026, the market makes that question unusually hard to answer: SAP publishes a record-based TPM metric, Aforza publishes a per-user metric, Salesforce leaves TPM itself at “contact sales”, and several specialists disclose subscription structures without disclosing the unit that ultimately determines the invoice.
That opacity matters because TPM sits between sales, finance, demand planning and the ERP. SAP’s current product, for example, covers promotion planning, fund allocation, claims, accruals and settlement; Anaplan’s current TPM application spans calendars, funding, approvals, forecasting and P&L impact. A contract that looks small while TPM is confined to a few planners can therefore become materially larger when the programme succeeds and spreads through the commercial organisation.
Monetizely’s position is that consumer goods buyers in 2026 should procure TPM around a fixed annual platform fee for defined markets or business units, with broad user access and a generous, contractually bounded record or data-capacity band. Records or usage can serve as a capacity guardrail, but they should not become an uncapped invoice meter. Three-year TCO, not the first-year subscription quote, should decide the winner.
The licence quote is only one part of the price buyers are accepting
TPM procurement often starts too late in the pricing discussion. A buyer receives an annual subscription number, negotiates a discount and then turns to implementation. By that point, the three decisions most likely to drive future cost - what is included, what makes the bill grow and how that growth is measured - may already be embedded in the vendor’s proposal.
Monetizely’s 5-Step Pricing Framework gives procurement a better sequence. As set out in Monetizing Agentic AI, Goals & Segmentation asks what commercial objective the offer serves and which customers or use cases it is designed for; Packaging decides which capabilities, services and terms are sold together; Pricing Metric determines what unit makes the customer’s bill rise, such as a user or record; Rate Setting determines the price charged against that unit and the discount structure; and Operationalization makes the model work in contracts, entitlements, measurement, billing and customer communication. For a TPM buyer, the framework is valuable because a 30% discount at the Rate Setting step cannot rescue a contract whose Packaging forces unwanted modules, whose Pricing Metric grows faster than the business, or whose Operationalization leaves “record”, “user” or “indirect access” open to interpretation.
The framework changes what procurement should regard as a good price. A $400,000 subscription with a poorly bounded meter may be more expensive than a $500,000 fixed fee. Conversely, a generous discount on year-one licences has little value when premium support is charged as a percentage of net licence fees or when a successful rollout immediately creates another paid population. Salesforce’s Consumer Goods pricing page, accessed 14 August 2026, makes the first point tangible: Premier Success is priced at 30% of net licence fees, while its TPM product itself remains quote-only.
UpClear provides another useful signal. Its official TPM procurement guidance states that SaaS TPM normally involves a subscription and also a rollout fee, with some subscriptions paid monthly and others annually in advance. Its advice to customers is explicitly to ask how those costs change over time.
The procurement problem, then, is not simply “licence plus implementation”. Buyers need to establish the denominator of the licence, the boundaries of the package and the rules that govern expansion before comparing rates.
Public pricing signals reveal a market split between seats, records and opaque enterprise subscriptions
Published TPM pricing is sparse, but the information vendors do disclose is enough to expose very different economics. We should not fill gaps with estimates presented as fact. Where a vendor does not publish the underlying unit, procurement should record that fact as a risk to be resolved in the RFP rather than assuming the model resembles a competitor’s.
The comparison below uses current official vendor disclosures as of 14 August 2026, except where Anaplan’s former public-company filing provides the latest Tier A disclosure of its historical subscription mechanics.
The table exposes the central procurement fact: there is no common TPM unit that lets buyers compare quoted ARR directly. A $500,000 SAP quote can represent a record entitlement, an Aforza proposal can expand with people, and a specialist vendor may quote a subscription whose underlying scaling rules appear only in the order form.
Applying the Packaging, Pricing Metric and Operationalization steps of Monetizely’s 5-Step Pricing Framework sharpens the diagnosis. The question is not whether a model is commercially legitimate. We want to know where each one is most likely to make a buyer pay for growth that was not priced into the original business case.
| Vendor | Packaging failure to test | Pricing-metric failure to test | Operationalization failure to test |
|---|---|---|---|
| SAP | TPM economics sit alongside a prerequisite SAP ERP or S/4HANA estate. | A record count can rise because the data model becomes more granular even when the number of human planners is unchanged. This is a buyer-side inference from SAP’s “individual data object” definition. | Procurement needs an agreed inventory of chargeable record types, counting logic and treatment of archived or duplicate objects. |
| Salesforce | TPM is quote-only while integrations, apps and other products may cost extra; Salesforce also says some products may need to scale together. | The TPM meter is not public, leaving the buyer unable to assess denominator growth before receiving the proposal. | The order form must state which products scale together and what triggers an added licence or product charge. |
| Aforza | A single connected platform can span TPM, CRM, retail execution and B2B commerce. | Paying per user means successful cross-functional adoption can itself expand ARR. | Role definitions, dormant accounts, service users and temporary users need precise entitlement rules. |
| Anaplan | A TPM application can sit inside a much broader planning platform covering additional functions and use cases. | Anaplan’s 2022 filing explicitly linked subscription revenue to customer and user counts and described expansion through additional users, use cases and geographies. | Historical two-to-three-year, generally non-cancellable subscriptions make the baseline committed at signing particularly important. |
| UpClear | Planning, promotions, accruals, deductions and related processes can involve several components. | The public material does not define the subscription’s chargeable unit. | Rollout fees and the way subscription costs change over time need to be priced before selection. |
| Visualfabriq | TPM/TPO sits alongside RGM, IBP and other modular capabilities. | No public TPM rate or unit lets the buyer independently forecast expansion cost. | Each additional module, geography and production environment should have a pre-agreed commercial treatment. |
| Vistex | TPM can be bought within a broader environment covering rebates, pricing, channel programmes and other processes. | “Pay-as-you-go subscription” does not, by itself, tell procurement what quantity drives the invoice. | Meter capture, invoice reconciliation and ERP integration responsibilities need to become contractual rather than descriptive. |
One pattern cuts across all seven vendors. Packaging expansion and meter expansion are separate risks. A company can hold its seat count flat and still spend more because it adds TPO or RGM; it can also hold the package flat while a record or user denominator increases.
That distinction is why Monetizely does not recommend a pure seat model as the buyer’s preferred architecture for enterprise TPM. TPM becomes more valuable when sales, finance and other stakeholders actually use it. Charging for every additional participant places a toll on the adoption the buyer is trying to create. A bounded platform fee for defined markets, with users broadly included and data capacity controlled through negotiated bands, better protects the enterprise business case.
Year-one ARR is a poor comparison measure because the commercial models compound differently. Procurement can expose the difference by giving every bidder the same three-year reference case and asking it to price the case contractually rather than merely providing a current-state quote.
Consider a programme receiving a $500,000 year-one software quote. The following model keeps the starting software spend identical while changing only how the contract responds to normal expansion. It demonstrates why the meter deserves at least as much negotiating attention as the initial rate.
| Contract design | Year one software | Year two software | Year three software | Implementation, data and expansion work | Three-year TCO | Difference from fixed model |
|---|---|---|---|---|---|---|
| Buyer-preferred fixed platform fee | $500k | $500k | $500k | $750k | $2.25m | Baseline |
| Seat-led model - users grow 15% annually; rate rises 4% | $500k | $598k | $715k | $750k | $2.56m | +14% |
| Record/usage-led model - chargeable quantity grows 25% annually | $500k | $625k | $781k | $750k | $2.66m | +18% |
| Package-expansion model - additional capabilities and markets enter in years two and three | $500k | $700k | $900k | $1.00m | $3.10m | +38% |
The table is not arguing that every seat contract will cost 14% more or every modular platform 38% more. It shows the mechanism: starting ARR explains much less of three-year spend than the rules governing adoption, capacity and scope.
Published vendor economics show why those extra lines belong in the model. Salesforce currently charges Premier Success at 30% of applicable net licence fees; at $500,000 of net licences, the arithmetic is another $150,000 annually where that plan applies. Salesforce also states that MuleSoft licences or partner work may be needed for some external integrations.
UpClear separately tells prospective TPM buyers to budget a rollout fee, while Anaplan’s last public filing before going private reported professional services for implementation, consulting and training and noted that implementations generally took one to six months depending on engagement scope.
Cash timing deserves similar attention. Anaplan disclosed in 2022 that it generally billed annually in advance and that new subscriptions typically ran two to three years; SAP’s current TPM page allows 12-to-60-month contracts and lists auto-renewal. A procurement team comparing only P&L expense can therefore overlook materially different cash commitments and exit flexibility.
Our view is to require two numbers from every finalist: committed three-year cash cost at the current footprint, and three-year cash cost under a pre-agreed expansion case. The gap between them is the commercial risk the vendor is asking the buyer to retain.
The biggest software shocks have come from the meaning of the meter, not the sticker price
Enterprise software history offers a more severe warning. Two of the most instructive cases involve consumer goods companies themselves and the interaction between SAP and third-party systems.
In SAP UK Ltd v Diageo Great Britain Ltd, decided in February 2017, SAP sought £54,503,578 in additional licence and maintenance fees associated with alleged direct or indirect access by Diageo’s Salesforce-based systems to SAP. Diageo argued, among other points, that it had already licensed SAP Process Integration based on message volumes. The dispute demonstrates what can happen when paying for one integration mechanism does not settle the licensor’s view of the users or activity behind it.
AB InBev disclosed an even larger dispute in its 2016 Form 20-F filed on 22 March 2017. SAP America had begun arbitration alleging breaches of a September 2010 software licence agreement involving employees’ direct and indirect use of SAP systems and data; the brewer disclosed claimed damages potentially exceeding $600 million. The parties later settled, with the amount not publicly disclosed.
Those disputes were not TPM SaaS subscriptions, and the contractual regimes were different from current SAP Trade Management. They remain directly relevant to TPM procurement because current TPM deployments exchange sales, customer, product, accrual, deduction and settlement data with ERP and other enterprise systems. SAP’s current TPM product itself promotes integration between CX and ERP and requires an existing SAP ERP Central Component or S/4HANA purchase.
Two more recent SaaS examples show that a buyer can suffer a large increase without any licensing dispute at all.
| Documented pricing case | Figure | What procurement should learn |
|---|---|---|
| SAP v Diageo, 2017 | SAP sought £54.5m in additional licence and maintenance fees | Integration rights and indirect use must be explicit; buying middleware does not automatically settle every software entitlement question. |
| SAP v AB InBev, disclosed 2017 | Claimed damages potentially above $600m | A disputed definition of licensed use can dwarf the software budget itself. Interface and entitlement terms belong in commercial diligence, not only technical design. |
| GitLab Premium, 2023 | List price rose from $19 to $29/user/month, a 52.6% increase; existing users received a temporary $24 transition price | A steep renewal increase can overwhelm a strong original discount. Buyers need to negotiate the future price base, not merely year one. |
| Salesforce enterprise products, 2025 | Average list-price increase of 6%, effective 1 August 2025, for Enterprise and Unlimited editions across Sales, Service, Field Service and selected Industries products | Even major platforms reset list prices. A contractual ceiling matters more than assuming today’s rate card will persist. The announcement was not specific to Consumer Goods TPM. |
These cases span different products and legal settings, but their procurement lesson is remarkably consistent: the contract must survive a future interpretation of the meter and a future change in the rate. Negotiating one without the other leaves half the risk untouched.
GitLab illustrates the second half especially clearly. A buyer receiving a 20% discount on the former $19 list price would have paid $15.20 per user. Moving the reference list price to $29 creates a much larger renewal base even before the next discount is discussed. The vendor offered a temporary $24 transition price to existing Premium customers until April 2024, but the underlying list-price reset remained.
Salesforce demonstrates a less extreme but more recent version. Its June 2025 announcement lifted average list prices by 6% across specified Enterprise and Unlimited products while simultaneously changing AI packaging elsewhere in the portfolio. A procurement team buying a multi-product Consumer Goods estate should therefore separate the TPM commercial schedule from general platform pricing wherever the vendor will agree to it.
A good TPM contract turns every path to a bigger invoice into a bounded number
The practical answer is not to demand that every vendor adopt the same public rate card. The buyer should demand the same degree of economic certainty.
Our preferred structure has a fixed annual platform fee tied primarily to named markets or business units, because those boundaries are easy for both sides to verify and do not discourage adoption. Users should be broadly included. Where infrastructure or database economics require a capacity measure, a record band can sit underneath the platform fee with substantial headroom and a pre-agreed ceiling rather than monthly consumption overages.
SAP’s current model shows why the capacity band needs a precise dictionary. SAP defines a record as each individual data object managed through the cloud service and sells the entitlement in 1,000-record blocks. Before signing, a buyer therefore needs to know whether a new SKU-customer combination, copied promotion, historical object, test object or archived item changes the licensed quantity.
Aforza demonstrates the corresponding problem with seats. Its published rule says any user needing access to the functionality is priced per user per month. The commercial question is therefore not simply “How many TPM planners do we have today?” It is “How many people will require access after finance approvers, key-account teams, field roles and new markets adopt the process?”
The negotiation checklist should force those questions into the order form rather than leave them for a true-up discussion:
Write the billable unit as a formula. For records, state which object types count and when. For users, define paid roles, free viewers, approvers, service accounts and inactive users. For any consumption model, specify the source system that produces the invoice quantity.
Buy capacity in bands rather than accepting open-ended overages. Establish the contracted baseline, included headroom, the price of the next band and a maximum annual increase. Automatic retrospective true-ups should be replaced by prospective purchases wherever possible.
Separate core TPM from optional packaging. Price TPO, RGM, deductions, advanced analytics, additional environments, new countries and other adjacent products individually even when the initial commercial package bundles them.
Fix the services boundary before signature. The SOW should state which integrations, data migrations, hierarchy loads, testing cycles, environments, training and rollout work are included, along with rates for additional work. UpClear’s public guidance confirms that rollout fees are a normal part of TPM economics.
Put integration rights in the commercial schedule. List ERP, CRM, data lake, retailer-data, deduction and planning interfaces and state whether activity passing through them creates additional software entitlements. The Diageo and AB InBev disputes show the scale of the risk when direct and indirect use is contested.
Cap renewal movement against the contracted net rate. A cap tied only to future list price can preserve the vendor’s ability to reset the starting base. GitLab’s 2023 move from $19 to $29 per user and Salesforce’s 2025 average 6% increase show why the reference price matters.
Make support arithmetic explicit. State whether support is included, fixed or calculated as a percentage, and what happens to that percentage when licences expand or contract. Salesforce currently publishes Premier Success at 30% of net licence fees.
Pre-price geographic expansion. A global CPG should obtain the price for the next market, business unit or deployment wave at signing rather than reopening the entire commercial discussion after the platform is embedded.
Protect contraction and exit. Specify data-export formats, extraction charges, transition access, treatment of unused capacity and the ability to reduce the contracted footprint at renewal.
The synthesis is straightforward: a disciplined negotiation does not merely lower the vendor’s unit rate. It reduces the number of circumstances in which the unit rate can unexpectedly apply to more things.
For a seat-priced vendor, that means broad role rights and pre-priced growth bands. For SAP, the emphasis moves to record definitions and capacity. For quote-only modular specialists, procurement should insist on seeing the commercial mechanics before functional scoring is finalised. Opacity is not automatically expensive, but unresolved opacity should carry a cost in the procurement evaluation.
TPM systems are unusually susceptible to the paradox of successful adoption. A programme begins with key-account planners and a few markets, delivers enough value to attract finance and sales, incorporates more retailer and product detail, and then expands into optimisation, RGM or connected planning. Several vendors openly design their platforms for exactly that broader footprint: Aforza connects TPM with CRM and retail execution; Anaplan connects promotion planning with wider enterprise planning; Visualfabriq spans TPM/TPO, RGM and IBP; Vistex can connect trade programmes with pricing, rebates and channel management.
Procurement should welcome that adoption operationally while refusing to leave its economics open-ended. Pure per-seat pricing works against broad participation. Uncapped record or transaction charging puts budgeting at the mercy of data granularity. A vague enterprise subscription postpones the same problem until expansion is already under way.
That is why Monetizely’s position is specific rather than neutral. The best buyer architecture in 2026 is a fixed enterprise platform commitment scoped to named markets or business units, broad access for the people who need to participate, and a generous record or data band used as a capacity boundary rather than a running toll. Vendors can still be compensated for genuine increases in infrastructure and enterprise scope, but the buyer should know the price of that growth before creating it.
The commercial decision should follow from that principle:
Make every finalist price the same future enterprise, not the buyer’s current footprint. Give bidders a three-year reference case covering the intended market rollout and business scale. Rank the resulting TCO alongside functional fit so a cheap pilot cannot win by postponing the cost of success.
Use a representative complex market to measure denominator growth before global commitment. A country with large retailer hierarchies, substantial promotion volume and ERP integration will reveal how quickly users, objects and operational work grow in the real system.
Gate geographic expansion on realised business value. Fund the next deployment wave when the prior wave demonstrates better planning, control or trade-spend outcomes rather than treating every country rollout as an automatic continuation of the software programme.
Keep the second-ranked supplier commercially viable through final contracting. Procurement leverage falls sharply once technical teams, executives and implementation partners treat one bidder as inevitable. The credible ability to switch late in the process is worth more than another round of percentage-point discounting.
Choose the pricing architecture before choosing the cheapest rate inside it. A slightly higher fixed platform fee with bounded growth can beat a deeply discounted seat, record or modular quote over three years. The objective is not the lowest ARR on signature day; it is the lowest credible cost of achieving the adoption the business case requires.
Assumptions
The three-year TCO exhibit is a Monetizely model, not vendor quotation data. It uses a common $500,000 year-one software baseline; $750,000 of implementation/data work for the fixed, seat and record cases; $1 million where broader package expansion requires additional work; 15% annual seat growth plus a 4% annual rate movement in the seat case; and 25% annual chargeable-volume growth in the record case. Taxes, foreign exchange, internal labour, financing effects and vendor-specific discounts are excluded. Public prices and commercial terms cited elsewhere are vendor disclosures or filings available as of 14 August 2026 unless a historical date is stated.
Footnotes
https://www.amazon.com/Monetizing-Agentic-AI-Handbook-Transformation/dp/B0H7Z13VKJ/
https://www.sap.com/mena/products/crm/trade-management.html
https://www.salesforce.com/consumer-goods/pricing/
https://aforza.com/studio-marketplace-aforza-consumer-goods/
https://www.sec.gov/Archives/edgar/data/1540755/000154075522000040/plan-20220430.htm
https://www.anaplan.com/applications/trade-promotion-management-app/
https://www.anaplan.com/industries/consumer-goods/
https://upclear.com/5-things-to-do-for-tpm/
https://visualfabriq.com/
https://www.vistex.com/cloud-solutions/trade-promotion-management/
https://www.vistex.com/resources/everything-about-vistex-cloud/
https://www.bailii.org/ew/cases/EWHC/TCC/2017/189.html
https://www.sec.gov/Archives/edgar/data/1668717/000119312517092177/d259136d20f.htm
https://about.gitlab.com/blog/gitlab-premium-update/
https://www.salesforce.com/news/stories/pricing-update-2025/