Managing a price list is not pricing

In many companies, what is called “pricing” is actually managing a price list. There is a table: products, channels, customer groups and the prices against them. This table is updated, distributed, loaded into systems. Someone is responsible for this work, and it is called “pricing.”

But managing a price list and doing pricing are two completely different jobs.

A price list is an operational document. It is the record of decisions already made: this product sells at this price. It is static, backward-looking and a maintenance task. Keeping the list correct, current and accurately reflected in systems — these are necessary but mechanical tasks.

Pricing is a decision. It is answering the question “what should this price be?” among demand, competition, margin, stock, customer behaviour and strategic intent. It is forward-looking, requires judgement and creates value.

Conflating the two takes pricing out of being a decision and reduces it to a maintenance task. The list is updated, but what the price should be is never questioned.

The right question is not “is the price list current?” It is:

Are these prices the right decisions against demand, competition and margin, or just numbers set once, entered into a list and never questioned again?

A list records, pricing decides

The difference between a price list and pricing is the difference between a record and a decision.

A list stores decisions already made. “This product, in this channel, at this price.” This information is useful — necessary for operations to run — but it belongs to the past. The list does not tell you why the price is at that level, whether it is still right or whether it should change.

Pricing is a continuous question. Has demand changed? Where is the competitor? Is margin under pressure? What is the stock situation? What is the customer behaviour record? Against these questions, you have to keep deciding “is this price still right?” The list can stay static; but the pricing decision is dynamic.

Companies often focus on keeping the list current and forget to question the pricing decision. The result is a price structure that is technically correct but strategically frozen.

The hidden cost of a frozen price

Reducing pricing to list management has a hidden cost: prices, once set, live on without being questioned.

A price was set last year under certain conditions. Since that day, cost may have risen, the competitor may have moved, demand may have changed, customer behaviour may have shifted. But the price stays the same, because there is no mechanism questioning it. The list is kept current — that is, the format is correct — but the price itself has disconnected from reality.

The cost of these frozen prices is silent. Some prices stay too low and lose margin; some stay too high and lose volume. None looks like an error, because the list is orderly and current. But the pricing decision has long since gone stale.

Turning pricing into a decision

Separating pricing from list management means tying the price to a decision process.

This does not mean questioning every price continuously — that too would be unmanageable. It means defining which signals trigger a price review: when cost crosses a certain threshold, when the competitor reaches a certain level, when margin falls below a certain band, when demand shifts in a certain direction. These signals trigger a decision that says “review this price.”

This way, the price stops being a number set once and forgotten and becomes part of a decision flow: signal → review → decision → application → tracking. The list is still kept, but it is no longer a frozen document; it is the record of a living decision.

This is the pricing version of the “not a report, but a decision system” principle: keeping the list is operations, managing the price is a decision.

A list is also necessary; but not enough

This does not mean a price list is worthless. Operations need a correct, current and consistent list to run. Without a list, neither sales, nor invoicing, nor systems work.

But a list is not pricing. A list answers “what is the price?”; pricing answers “what should the price be?” The first is an operational necessity, the second a strategic decision. A healthy structure separates the two: it manages the list properly but treats the price as a decision.

Closing

In many companies, what is called “pricing” is actually managing a price list: a static, backward-looking, mechanical maintenance task. But pricing is a decision — answering “what should this price be?” among demand, competition, margin, stock and customer behaviour. Conflating the two takes pricing out of being a decision and leaves prices to freeze unquestioned.

The solution is to tie the price to a decision flow: defining which signals trigger a review and treating the price as a living decision. A list is still necessary, but not enough. A list is operations, a price is a decision.

The right question is:

Are we asking whether our price list is current, or whether these prices are still the right decisions against demand, competition and margin?