StrategyMay 26, 2026·10 min read

The mid-market pricing software gap: between Excel and enterprise

Mid-market retailers (€10M-€500M) sit between broken spreadsheets and unaffordable enterprise suites. The category shift closing the gap, and what it means for the C-suite.

There's a quiet truth inside most mid-market retail businesses that nobody likes to say in the boardroom: the pricing function runs on spreadsheets. Not modern, integrated mid-market pricing software. Not a category-management platform with a real data model. Spreadsheets - dozens of them, owned by the people who happen to still remember how the formulas work.

This isn't a failure of ambition. Mid-market retailers - call it €10M to €500M in revenue, 10k to 200k SKUs - have looked at the alternatives. The enterprise suites cost six figures, take 6-12 months to implement, and were designed for a category director with three analysts under them. The cheap competitor-monitoring tools handle one slice of the problem and stop there. So the spreadsheet keeps the lights on, and pricing keeps happening one VLOOKUP at a time.

The gap between those two worlds - the spreadsheet that's quietly breaking and the enterprise platform that's quietly unaffordable - is the most under-discussed structural problem in retail technology right now. It's where margin leaks live. It's where most "we need to be more data-driven" conversations stall. And it's the gap that, in 2026, is finally getting closed.

Why the gap exists at all

The retail pricing software market is not small. It's projected to grow from roughly $1.14B in 2025 to $1.27B in 2026, at an 11% CAGR. But the bulk of that spend has historically gone to large enterprises - retailers north of $1B in revenue with internal data science teams, dedicated pricing analysts, and the change-management capacity to absorb a year-long implementation. One industry breakdown shows large enterprises holding around 55% of pricing software utilization, with SMEs as the fast-growing segment that hasn't yet caught up.

That asymmetry is structural, not accidental. Enterprise pricing platforms are built around four assumptions:

  1. The retailer has clean master data sitting in a modern PIM or data warehouse.
  2. The retailer has a dedicated team that will use the software full-time.
  3. The retailer can absorb 6-12 months of implementation before the first usable output.
  4. The retailer needs sophisticated optimization - elasticity models, multi-objective solvers, scenario engines - and is willing to trust the outputs without seeing the math.

None of those assumptions hold cleanly in mid-market retail. Master data is messy, often spread across an ERP, an e-commerce platform, and a handful of spreadsheets. The pricing team is two people, one of whom also owns promotional planning. A 6-month implementation isn't an implementation - it's a project the CEO will quietly defund at the next budget review. And the team doesn't want a black-box optimizer; they want to see why a price moved, because they're the ones who will have to defend it to the buyer, the brand, and the boss.

Excel handles those mid-market realities better than any enterprise platform - until it doesn't. The breaking point is predictable. It usually arrives when the assortment crosses 20,000 SKUs, when the team starts pulling competitor prices from three different scraping tools, or when someone in the C-suite asks "what's our actual margin position by category, this week" and the answer takes four days.

What mid-market retailers actually need

Two years of talking to category directors and commercial leads at retailers in this band has produced a fairly consistent shortlist. The needs are unglamorous, but they're real:

One workspace that holds the whole picture. Products, competitor prices, costs, sales, margins, rules - in one grid, not in seven tabs across three systems. The grid has to be queryable the way a spreadsheet is: filter, sort, group, derive a new column from existing ones. Anyone who has tried to get a pricing analyst to leave Excel for a "modern" tool with a fixed dashboard knows why this matters. The dashboard breaks the moment the analyst needs to ask a question the product manager didn't anticipate.

Rules a human can read. "Match the lowest of our three named competitors, but never go below cost plus 15%, and round to the nearest 0.99" should be one sentence in plain English, not a 200-line config file. When the rule produces a price the team disagrees with, they need to see exactly which clause fired and why. Explainability isn't a nice-to-have; it's the prerequisite for trusting the system enough to let it actually run.

Days to first usable output, not months. Mid-market retailers won't sign a six-month implementation. They've been burned. The bar is: upload my catalog and competitor list on Monday, see a working pricing view by Friday, run my first real repricing the following week.

Pay-as-you-go economics. A €60K annual contract is a non-starter for a retailer doing €25M in revenue, even if the ROI math works out. The pricing model has to scale with usage - one-time audits, periodic strategy work, then dynamic repricing once the team is bought in. This is the same shift that happened in BI tooling and in customer support: tiered, self-serve, expand-over-time.

Owned by the commercial team, not IT. The pricing function is closer to merchandising than to engineering. The tool has to be configurable by the people who know the business, not gated behind a quarterly IT roadmap.

If you put all of those needs in a single sentence, it reads: Excel-feel, with real data underneath, that the commercial team can run themselves. That's the gap.

Retailgrid pricing grid showing live competitor prices alongside SKUs, costs, and margin columns
A workspace that holds the whole picture: SKUs, costs, competitor prices, and margins in one grid.

What the enterprise suites get wrong for this segment

The enterprise pricing platforms aren't bad. They're built for a different customer. The problems that show up when a mid-market retailer tries to use one are predictable:

The data model is too opinionated. Enterprise platforms assume a clean dimensional structure - product hierarchies, location hierarchies, time hierarchies - that maps to how a Walmart or a Carrefour organizes data, not how a 12-store specialty chain organizes data. Forcing the mid-market retailer's reality into that model is a four-month consulting engagement before anyone writes a single rule.

The optimization is overspecified. A €40M home goods retailer doesn't need a multi-objective optimizer balancing revenue, margin, and inventory turnover with elasticity coefficients estimated from 18 months of transaction data. They need: "competitor X is 8% below us on these 200 SKUs; what should we do?" The enterprise tool can answer the second question, but only after you've configured the first.

The change management is too heavy. Enterprise rollouts assume the retailer will reshape its commercial process around the software. Mid-market retailers don't have that slack. The software has to fit into the existing weekly trading rhythm - Monday cost-letter review, Wednesday competitor scan, Friday price publish - or it gets abandoned.

The pricing is built for a different buyer. Enterprise contracts are negotiated by procurement, paid annually, and justified by a multi-year business case. Mid-market commercial teams want to see value in the first quarter, expand into a second use case in the second quarter, and not have a CFO conversation until the tool is clearly working.

None of this is a criticism of how the enterprise tools are built. It's a recognition that the mid-market needs a different architecture, not a stripped-down version of the same architecture.

What's actually closing the gap

Three shifts in the last two years have made the mid-market pricing problem solvable in a way it wasn't before.

The first is cloud-native, self-serve onboarding. The same shift that put BI tools (Looker, Metabase, Mode) into the hands of analysts who used to wait six months for IT has reached pricing. Around 42% of mid-tier businesses now deploy cloud-hosted pricing platforms to centralize price decisions across channels. The implementation isn't an implementation anymore; it's a CSV upload and a configuration wizard.

The second is explainable AI. The "AI pricing" pitch in 2018 was a black-box model that promised 3% margin uplift if you'd just stop questioning it. The 2026 pitch is different: AI helps the team configure rules faster, surface anomalies they'd otherwise miss, and explain price changes in plain English. The model isn't replacing the category manager; it's giving them leverage. That distinction matters because mid-market category managers are accountable - they have to defend their pricing position to suppliers, to franchise partners, to the boss. They won't trust a system they can't explain.

Retailgrid plain-English rule configuration showing a competitive pricing rule being created from a natural language description
Rules a human can read: configure a competitive pricing rule by describing it in plain English.

The third is the spreadsheet-native interface. The last decade of B2B software design pushed everyone toward fixed dashboards and rigid wizards. That worked for tools where the user has a defined workflow. It doesn't work for pricing, where the question changes every week. The interface that actually fits is the grid - rows of products, columns of metrics, derived columns the user can add, formulas they can write, filters they can save. The shift here is not nostalgia for Excel; it's recognition that the spreadsheet's fundamental data model - the grid - is the right primitive for this work. What was broken about Excel was the file format, not the metaphor.

What this means for the C-suite

For a CEO or commercial director at a mid-market retailer reading this, the practical implication is straightforward. The "Excel is breaking but enterprise is too heavy" trade-off you've been living with for the last five years is no longer the only option. The category of tooling that fits the mid-market specifically exists now, and the economic case for adopting it is clearer than it was even 18 months ago.

A few questions to push on with your team:

  • How much margin is currently leaking through the spreadsheet? Most mid-market retailers can't answer this with a number. The honest first step is an audit: pull last quarter's pricing actions, classify each one as rules-driven, exception-driven, or "we noticed late," and add up the margin impact of the third bucket. It's usually larger than expected.
  • What would it cost to get the first usable output in days, not months? The right benchmark is not "what does the enterprise platform cost," but "what does it cost to test the assumption that structured pricing beats reactive pricing, with a 90-day pilot, on one category?"
  • Who owns this? If pricing lives between merchandising, finance, and IT, and none of them owns it cleanly, no tool will fix the underlying organisational ambiguity. Mid-market retailers that get the most out of pricing software have one accountable owner with a clear mandate, even if the team is small.
  • What does "explainable" mean to your team? If your category managers can't defend a price change to a supplier or a buyer because they don't know why the system recommended it, the tool won't get used. Explainability is a usage prerequisite, not a feature.

What this doesn't change

Closing the mid-market pricing software gap doesn't fix everything. It doesn't magically clean up master data; the retailer still has to invest in product hierarchies and cost feeds. It doesn't replace commercial judgment; the category manager still decides whether to match a competitor's promotion or hold price and ride out the dip. It doesn't substitute for a coherent pricing strategy; if the retailer hasn't decided whether they're competing on price leadership, range, or service, no software will sort that out.

What it does is close the execution gap between strategy and reality. The mid-market retailer that knows it wants to compete on price leadership in 200 KVI SKUs and hold margin elsewhere now has a way to actually run that strategy, daily, without three analysts and a six-month rollout. That's a meaningful shift. The work is no longer in tooling; it's in deciding what to do with the leverage.

Retailgrid price analysis drawer showing the explainable breakdown of why a recommended price was set, with rule attribution and margin impact
Explainability as default: every recommended price shows which rule fired, what it competed against, and the margin impact.

The mid-market moment

The retail pricing software market has been bifurcated for a decade: enterprise tools for the top 5%, spreadsheets for everyone else. That structure is dissolving, and the segment that benefits most is the one that's been underserved the longest - retailers in the €10M to €500M band who outgrew Excel years ago but couldn't justify a six-figure platform commitment.

The retailers who'll get the most out of the next two years are the ones who treat this as a category shift, not a tooling upgrade. The tools that fit the mid-market exist now. The economics are different. The implementation timeline is measured in days, not quarters. The question is no longer whether to make the move; it's whether to make it before the competitor down the street does.

If any of this resonates - the spreadsheet that's quietly breaking, the enterprise quote that's quietly unaffordable, the pricing function that's quietly leaking margin - we'd be happy to compare notes. Retailgrid is built for exactly this segment, and we spend most of our time talking to commercial leads who are living in the middle of this gap.

See the agentic pricing platform behind the writing.

A 20-minute walkthrough of Retailgrid on a real retail dataset. No signup. No sales script.