Pricing, Purchasing, Category Managementexport separate files
.avif)
The final price is determined by three distinct factors (purchasing [supplier terms], category management [product assortment], and pricing [arbitrage]), and 85% of companies believe they have significant room for improvement in their pricing (Bain & Company, 2018), often due to a lack of a shared workflow among these three functions. The issue of a shared workflow is distinct from that of decision-making governance: one concerns the available information, while the other concerns the authority to make decisions.
A price is never determined by a single department, even when there is a single file labeled “pricing.” Purchasing manages supplier terms, category management oversees the product mix and shelf space, and pricing sets the final price—and all too often, these three departments work on three separate files that don’t communicate with one another.
This guide details the actual cost of this compartmentalization—which is distinct from the question of who has the final say on a price—and what a shared workflow among these three functions entails in practice.
Three business lines, three files, one pricing decision
In a typical retail organization, a product’s final price is determined by three distinct factors. The procurement department negotiates supplier terms, purchase costs, discounts, and logistics terms. Category management oversees the product assortment, shelf space, and consistency of the offering within each category. The pricing department sets the final selling price, taking into account these two factors and the company’s competitive positioning.
Each of these three functions has its own tracking tool—often an Excel file specific to its scope. The problem isn’t the existence of these files per se; it’s that they don’t communicate with one another. A change to a purchasing term negotiated on a Monday may not be reflected in the pricing file until several weeks later.
The Hidden Cost of a Non-Shared Workflow
85% of companies believe they have significant room for improvement in their pricing, even though the issue is identified as a priority, according to a Bain & Company survey of more than 1,700 companies (“Is Pricing Killing Your Profits?”, 2018).
There are several reasons for this disconnect between stated priorities and actual results, but one of the most common is operational rather than strategic: the pricing team does not have timely access to the information held by the procurement and category management teams. This is not a lack of intent; it is a lack of coordination between the functions.
The cost of this compartmentalization remains largely invisible until it is explicitly measured: a slightly inaccurate margin on a product does not trigger any alerts. It is a diffuse cost, spread across thousands of individual decisions, but it is real and cumulative.
What “collaborative” actually means
Purchasing, terms visible in real time: An updated supplier negotiation must be visible in the pricing system without having to wait for a manual synchronization.
Category management, visible margin impact prior to decision-making: An assortment plan must be able to incorporate an estimate of the margin impact, not just available space.
Pricing, arbitrage based on up-to-date data: a price set based on outdated purchase terms leads to a flawed decision from the start.
All three have cross-validation workflows: a significant change on one side triggers a notification on the other.
An example of a common desynchronization issue
A common scenario plays out time and again: the procurement team secures better supplier terms for a particular SKU. The category management team then plans a promotional campaign for that same SKU. The pricing team, unaware of either development, makes decisions based on a purchase cost that is already outdated.
The result: an incorrect margin calculation, a promotional campaign that does not take advantage of the new purchasing terms, and a correction that is discovered weeks later—if at all. The problem is structural, not human.
Building a Shared Perspective Without Merging Functions
At Booper, the “ Pricing Optimization Software ” approach does not involve combining pricing, purchasing, and category management into a single team; each function retains its own scope. Instead, it involves giving them access to a shared view of the data that informs decisions on pricing, purchasing terms, product assortment planning, and real-time margins, with approval workflows that notify each function when data relevant to it changes elsewhere.
What Changes When the Three Functions Share Their Data
1. Decisions are based on up-to-date data; a renegotiated purchase term is immediately reflected in the margin calculation.
2. Sales activities become more consistent; a promotional campaign can be aligned with improved purchasing terms.
3. The time spent reconciling data is eliminated, and manual synchronization meetings are replaced by continuous visibility.
4. Margin errors become apparent before—not after—a discrepancy between actual cost and allocated cost is detected at the time the decision is made.
Errors That Cause Files to Remain Separate
- Treat this as an organizational chart issue. Reorganizing teams without changing the workflow will simply recreate the same silos.
- Waiting for a meeting to synchronize data. A quarterly review isn't enough to correct decisions made in the meantime.
- Confusing "shared view" with "shared decision-making." Providing access to the same information does not mean that each function must approve the decisions made by the other two.
- Don't measure the cost of compartmentalization until after a visible incident occurs. The cost exists continuously, long before a margin error becomes large enough to be noticed.
Frequently Asked Questions
This is because, historically, each department has had its own tracking tool, with no common system linking them. The problem isn't the existence of these files as such; it's that they don't communicate with each other: a change to a purchase term negotiated on a Monday may not be reflected in the pricing file until several weeks later.
Decisions made based on incomplete or outdated information—this cost remains largely invisible until it is explicitly measured. It is a diffuse cost, spread across thousands of individual decisions (a slightly inaccurate margin on a single product does not trigger any alerts), but it is real and cumulative when considered across an entire catalog.
No, it's not a matter of the organizational chart but of workflow. The three functions retain their own scope. Reorganizing the teams without changing the workflow simply reproduces the same silos in a different form; it is the shared view—not the merger—that corrects the problem.
By centralizing the data that drives pricing decisions in a shared system with cross-functional validation workflows. Specifically: purchasing terms visible in real time on the pricing side, margin impact visible before a decision is made on the category management side, and cross-functional notifications as soon as data relevant to another function changes anywhere.
Yes. Decision-making governance concerns who has the authority to make decisions. Shared workflow concerns the availability of information at the time a decision is made. A shared view does not mean a shared decision: giving all three functions access to the same information does not mean that each must approve the decisions of the other two.
See also in this series: Before deploying a pricing tool, ensure your data is reliable · Switching pricing tools without repeating past mistakes · Managing your pricing tiers with limited sales data.
It has become increasingly common to compare two implementations of the same general-purpose language model before deciding which one to use to drive pricing; but the real question isn’t which one to choose, but where to position each one.
A general-purpose LLM lacks four key components required for pricing decisions: access to real-world data, explicit business rules, impact simulation, and explainable governance—these are the responsibilities of a specialized solution, not the LLM alone.
Generative AI projects that combine in-house expertise with that of a specialized partner have a significantly higher success rate than those developed solely in-house: 67% versus 22%.
Auditing a rule verifies that a calculation was executed correctly. Explaining a decision reconstructs the data, the expected demand, elasticity, cannibalization, the rules applied, and margin-volume trade-offs. According to Sage & IDC, 71% of financial executives would reject an AI tool that is 99% accurate if it cannot explain its answer.
A pricing tool faithfully processes the data provided to it; the quality of the results depends first and foremost on the quality of the input data. Three tasks are priorities before any configuration: a product catalog free of duplicates, synchronized prices and costs, and a continuous sales history. There’s no need to wait for perfect data to get started: an initial setup using files allows you to gradually improve reliability.
This is precisely what BOOPER’s Change Management module addresses: supporting teams to ensure that this data analysis does not hinder the adoption of the new tool.