Implement a pricing tool: Define the scope of the project before making a choice
April 16, 2026
A pricing tool project is based on a pricing decision that takes effect today, not on a list of features. The scope defines this decision—an initial, representative but narrow scope—and determines the price once the tool is in place.
The generalization criterion is defined before the test and is evaluated against a control set. There is no requirement to go through an intermediate step between a spreadsheet and a more advanced tool: this often doubles the scope of the project without reducing the risk.
Management has approved the concept of a pricing tool. Before comparing vendors, we still need to decide what the project should change, where to test it, and how to determine whether to roll it out.
This article focuses on this framework: the decision in question, the initial scope, governance, and the criteria for generalization.

Implementing a pricing tool: What does that mean?
Implementing a pricing tool means deciding which pricing decisions the company wants to make more effectively, within what scope, with whom, and under what conditions it will roll them out. The choice of software comes later.
This article focuses on the process of defining the scope and making decisions. Team adoption and the replacement of an existing tool are covered in separate articles. The complete process is summarized in our selection and deployment guide, linked at the end of this article.
Our belief, as a publisher and consultant with experience in retail pricing since 2014: most projects that fall short were poorly defined, not poorly executed. A project scope should be summarized on a single page. If it takes twenty pages, the decision hasn’t been made yet.
Start with a decision that involves a cost, not a list of features
A project that’s off to a good start can be summed up in one sentence: “We’re losing profit margins on this product line because our prices don’t keep up with our costs,” or “Our competitors’ product launches take three days and arrive too late.”
Put this way, the sentence already specifies what to measure, where to test, and what type of tool to look for. A list of forty features, on the other hand, yields responses from vendors that all sound the same.
Signs That Indicate a Tool Is Needed
Three situations come up repeatedly: a catalog with several thousand items, purchase costs that change faster than the price tags, and multiple stores or retail chains where prices must remain consistent.
In all three cases, the spreadsheet doesn't crash all at once. It slows down, then makes mistakes without warning. The limitations of Excel when it comes to managing prices rarely result in a single, major issue; instead, they manifest as a series of small, repeated errors.
Some teams find a spreadsheet error every week, and 22% find one every day. In a pricing file, the error isn’t noticeable until it’s on the shelf.
(DOSS, survey published in May 2026)
Quantifying the stakes before looking for a tool helps avoid sizing the project arbitrarily. Here’s an example: on €50 million in revenue, a half-point margin represents €250,000 per year.
This calculation doesn't guarantee anything. It establishes the order of magnitude of what the project might cost—in terms of both licensing and team time—in order to remain profitable.
Scope: The Most Underestimated Decision in the Scoping Process
The initial scope must be broad enough to be convincing, and narrow enough to be measured accurately: a product family, a retail chain, or a type of store.
There are two opposite pitfalls to watch out for. Choosing the easiest family leads to a success that no one believes. Choosing the most atypical one leads to a failure that proves nothing.
Another counterintuitive point: there’s no need to use an “enhanced version of Excel” as a stepping stone to a more advanced tool. This intermediate step often doubles the project’s scope without reducing the risk.
The first scope is not intended for optimization; it is intended for decision-making. Within one to three months, it must produce a result that management will be willing to review when compared to a control group.
Anything that does not serve this decision (full integrations, all brands, all channels) can wait until the solution is rolled out across the board. This is the discipline that is most often lacking in projects that get bogged down.
Booper Team, Pricing Consulting and Implementation
Order is more important than speed: first prove it within a limited scope, then expand it. The framework doesn't have to anticipate everything that follows—only the condition that triggers it.
Multiple brands or business units: one common rule, one initial focus area
When dealing with multiple brands, the temptation is to cast a wide net so that no one feels left out. The result is often the opposite: rules negotiated to the lowest common denominator, and no clear outcome.
We recommend that we work together to define common elements (positioning, margin thresholds, consistency across formats) and demonstrate value in a single market. Other brands can then adopt this proven framework.
Who Sets the Price: The Question to Decide Before Signing
A pricing tool shifts the decision-making process. What the buyer or product manager used to decide on their own now becomes a recommendation to be approved, revised, or rejected.
This shift is determined at the planning stage, not at the launch: who sets the rules, who approves them, who can override them, and on what grounds. If put off, it turns into a territorial conflict.
How to get the teams on board next is a matter of adoption, which is covered in “Successfully Managing Change During a Pricing Rollout.”
On average, companies don’t even implement half of the price increases they’ve decided on. Value is lost between the decision and the price tag.
(Simon-Kucher, Global Pricing Study 2025, more than 2,200 executives, 28 countries)
Our take: This gap between decision-making and execution is a governance issue rather than a tool issue. A project that doesn't specify who makes decisions simply perpetuates the gap—with the added complication of software.
Data: What's Really Holding Us Back—and What Can Be Fixed Along the Way
Waiting for perfect data before getting started means you’ll never get started. The scope, however, must distinguish between what prevents the initial scope from being achieved and what can be corrected during the test.
The main obstacles almost always boil down to three factors: sales history, current prices, and purchase costs within the selected scope. The rest improves along the way, as our article on data quality in pricing shows.
Incorporating Competitive Intelligence into the Project
Competitors' prices are not stored in the ERP system or at the register. They come from online data collection, store reports, or panelist data—often provided by different service providers.
When it comes to framing the issue, the key factor is frequency rather than technique: competitive data updated once a month is not as useful as prices revised weekly.
At Booper, online data collection is integrated into the platform: see our price tracking and web scraping features. This is supplemented by in-store data and panelist data provided by the retailer.
Deciding to generalize: a criterion written before the test
The decision to generalize is made before the test, not after. Once the results are in, everyone interprets the numbers in a way that suits them.
The metric is compared to a control group, never to the “before” figure alone. Illustrative example: If the group being tested gains 0.8 percentage points and the control group gains 0.2 percentage points over the same period, the effect attributable to the tool is 0.6 percentage points.
The time saved is quickly apparent. The margin requires more precision, which is why it makes sense to separate the two right from the start.
Our benchmark, based on teams that manage their pricing with Booper: a margin increase of +0.5 to +3 points in just a few months, and a 70 to 90% reduction in pricing preparation time.
These ranges must be verified within your scope; they cannot be assumed. That is the whole point of establishing a criterion in writing before the test.
What a frame Should Not Freeze in Place
A framework is not a detailed deployment plan. It defines the intended decision, the scope, the governance structure, and the criteria for widespread adoption. The fine-tuning takes place during testing, in collaboration with the teams.
If you're replacing an existing tool rather than Excel, the first step is to understand why the previous tool wasn't adopted: that's the focus of our article on switching tools, which you'll find below.
See also in this feature
- The Booper Solution: Managing Change in a Pricing Project
- Selecting and Implementing a Pricing Tool: From Identifying the Need to Going Live
- SaaS Platform for Retail Pricing Management: The Benefits
- Food Retailer Case Study: Managing Prices Across a National Network
- Changing Pricing Tools Without Repeating Past Mistakes: The Assessment
FAQ: Setting Up a Pricing Tool
Allow a few weeks to get started in an initial scope, followed by one to three months of testing to measure the impact on margins.
The total time required depends primarily on the condition of the data and the number of stores involved, much more so than on the tool itself.
Work together to define common elements (positioning, margin thresholds, consistency across formats), then demonstrate the value using a single brand or a single family. Covering the entire scope all at once multiplies the number of negotiated rules and makes the result difficult to understand.
The other business units then adopt a framework that has already been tested, with shared metrics.
A product line, a retail chain, or a type of store—broad enough to be convincing and narrow enough to be compared to a control group.
Avoid the most ordinary family, whose success won't convince anyone, as well as the most unusual one, whose failure won't prove anything.
The scope of the test includes: sales history, current prices, and purchase costs. Competitors' prices are also included if market positioning is a factor in the decision being made.
The rest can be refined during testing, provided that we know from the outset what is a roadblock and what is not.
Either through periodic import (file or API) of collected prices, or using a solution that already includes price collection.
In both cases, make sure that the update frequency of the concurrent feed matches your price revision schedule: monthly data isn't useful for weekly decisions.
Compare the tested scope to a control scope over a period determined before the start of the project, then subtract the total cost: licensing, integration, and team time.
Consider the time saved in preparing prices separately, as this is more immediately apparent than the margin.
There is no overall ranking: the best value depends on the initial scope. For the same scope, compare the total cost, the time to the first actionable recommendations, and the measured improvement in a test.
Reject any claimed ROI that isn't backed by explicit assumptions.
Sources: DOSS, Survey on Spreadsheet Errors, May 2026 · Simon-Kucher, Global Pricing Study 2025 · Booper figures: interview with Hugues Lafitte, Informations Entreprise, September 15, 2026. The numerical examples provided for illustrative purposes are theoretical calculations, not actual client results.
Quicklizard is a dynamic pricing platform that originated in e-commerce and has been extended to stores with electronic price tags. At Intersport Germany, it manages e-commerce, not the stores.
For a chain of stores in France, look for a software provider with deep industry expertise and built-in compliance with French regulations, such as BOOPER. For an online-focused retailer, consider Competera or Omnia Retail. For market intelligence, try Minderest. In the B2B sector, consider Pricemoov.
Management doesn't approve a price; it approves a trade-off between margin, volume, and price image. Presenting a single recommendation means asking management to trust you. Presenting the cost of each option gives management the information it needs to make a decision.
A sound projection provides a range rather than a single figure, specifies what is being excluded, and anticipates the gap between the projected increase and the actual increase. When compared with actual results, it establishes the credibility of the next projection.
A franchisor cannot impose a minimum resale price: doing so is punishable by law; the franchisor may only recommend a price or set a maximum. A franchisee’s margin is therefore governed by a documented target, defined by network segment and applied uniformly across each segment.
The best indicator of this governance is not adherence to the suggested retail price, but the rate of compliance with it by segment. A suggested retail price that franchisees in a given area do not follow often signals a poorly set price, not a lack of discipline.
