How much — really —
does retail pricing
software cost

A pricing software RFP usually goes one of two ways. Either you ask for budgetary numbers up front and get nothing back for two weeks, or you sit through three discovery calls before anyone will write a number on a slide. The vendors aren't being difficult — pricing genuinely is complicated. But the asymmetry is the problem: you need to budget, and they need to qualify, and "we'll send pricing once we understand your business" turns a six-week evaluation into a six-month one.

This article is the version you'd get from a friend who's been through three of these evaluations. Real pricing models, real cost bands, and the line items the demo decks skip. None of this replaces vendor-specific quotes — but it lets you walk into the next call with a working budget instead of asking blind.

Part one · The four pricing models

How vendors
actually charge

Vendors in this category use any of four pricing models — and most contracts blend two or three of them. The right question isn't which model is "correct" but how the specific blend behaves when your usage grows, contracts, or expands into a new module. Get this wrong and the bill in year three is a different conversation than the demo led you to expect.

Most contracts blend two or three of these. A common mid-market mix: per-user licence plus modular pricing, often with a small implementation fee per module activated. Less common in non-food but worth recognising: a per-SKU base licence with an outcome-based variable component on top, used by some optimisation specialists.

A fifth model exists for the largest deals — fixed enterprise contracts that wrap everything into one number, with seven-figure totals and 12–18 month rollouts. Mid-market non-food retailers rarely sign these directly, but the structure is worth knowing because some vendors will quote one to your CFO if your assortment is large enough.

What matters more than picking "the right model" is reading the contract for how the model behaves under change. Three real-world scenarios where mid-market retailers consistently get caught:

• Use grows fast. Per-SKU contracts can balloon when a retailer expands assortment by 30% in a year. Per-user contracts barely move. Per-GMV contracts grow proportionally — fine if the platform is helping drive that growth, frustrating if it isn't. Always model the bill at +50% of current scope before signing.
• Use shrinks. A retailer that consolidates from three banners to one, or trims an underperforming category, suddenly has more capacity than it pays for. Most contracts don't allow mid-term reductions. Negotiate a renewal clause that lets you right-size at year two or three without penalty.
• You add a new module mid-contract. This is where modular pricing earns its name and breaks its promise simultaneously. Most modular vendors charge a separate implementation fee per module, plus a multi-week rollout project. If those terms aren't in the original contract, you negotiate them later, when leverage has shifted to the vendor.

The single most useful question to ask vendors during evaluation: "Can you show me the contract terms for adding a future module — pricing, implementation fee, timeline, and whether activation requires a new SOW?" A vendor that can answer in writing has been through this with mid-market customers before. A vendor that says "we'll work that out when you're ready" is asking you to negotiate without leverage in eighteen months.

The pricing model is also a signal about who the vendor was built for. Per-user pricing usually means the vendor was originally a B2B SaaS team building a tool for analysts. Per-SKU pricing usually means the vendor came up through retail consulting and prices like a data provider. Modular pricing usually means the vendor has worked with mid-market enough to know that big-bang deployments don't work. Per-GMV pricing — rare in non-food — usually means the vendor wants to look more like a partner than a tool. Each background shows up in the product, not just the price.

Part two · Vendor archetypes

Software, consultancy,
or both

Non-food pricing is genuinely consultative. The questions are not just "what algorithm do we run" but "how should we cluster categories," "what's our promotional cadence," "where does this brand sit competitively." That's why the vendor landscape splits into three archetypes that look similar in a feature checklist but represent fundamentally different commercial relationships.

Most mid-market non-food retailers end up between Archetypes A and C. Archetype B (consultancy software) is genuinely valuable when the project is a major repositioning — entering a new market, restructuring categories post-acquisition, defending against a disruptor — and your board needs senior strategic credibility on the slide. The challenge is what happens when the consultants leave. Often the tool leaves with them. Or stays, but at a price point that no longer makes sense without the senior partners attached.

The honest mid-market path: start with Archetype A or C for the day-to-day pricing operation, then bring in a strategy firm for specific transformation projects when you actually need that senior view. Bundling them inside one vendor relationship usually overpays for one or undersells the other.

Ask any vendor in evaluation: "What's the percentage of your revenue from software licence versus services?" The answer reveals which archetype they're actually running, regardless of the marketing. A vendor at 80%+ licence revenue is Archetype A. A vendor at 30% licence is Archetype B with a tool attached. Archetype C usually sits between 60–75%.

Part three · The full bill

What "year one"
actually adds up to

The license fee is the first line item. The bill that hits your finance team is bigger. Here's a worked example for a typical mid-market non-food deployment — €600M revenue, 80 stores, 25,000 active SKUs.

The numbers in the "realistic" column are not high — they're median for a healthy mid-market non-food deployment that goes live on time. The "low end" column shows what happens when the vendor pre-built integrations to your ERP, your master data is unusually clean, and your team can dedicate someone full-time. That combination exists; it's just rarer than the demo decks suggest.

What matters most: year one is not the right comparison frame. A platform that costs €120K year one and €120K every year after costs €600K over five years. A platform that costs €375K year one and €180K every year after costs €1.1M. Same software category, same retailer size, very different five-year decision. Vendors will quote year one because that's the most flattering number. Insist on a five-year TCO model before signing.

Part four · Hidden costs

The line items
vendors don't volunteer

Most pricing software contracts have at least three of these. None of them are reasons to walk away — they're reasons to negotiate before you sign.