Moving beyond cost-plus with price optimization software

Cost-plus pricing has one enormous advantage: you can always explain it. Cost, markup, price. Anyone in the room can follow the logic, and nobody has ever been fired for applying a 45% markup.

It also has one structural blind spot that no amount of discipline fixes. Cost-plus pricing knows exactly what you paid and absolutely nothing about what a shopper will pay or what the competitor two clicks away is charging. That gap is what price optimization software exists to close.

What you are leaving on the table

Apply a flat markup across a catalog and two errors happen simultaneously, in opposite directions.

On known-value items - the SKUs shoppers actually price-check - a uniform markup often leaves you visibly expensive. That does damage beyond the item itself, because shoppers generalize from a handful of comparisons to your entire assortment.

On long-tail items nobody compares, the same markup leaves real money uncollected. Some of those products could carry 15 points more margin without a single lost sale, and cost-plus has no mechanism for telling you which ones.

Most retailers running flat markups are simultaneously overpriced where it hurts and underpriced where it would not.

What optimization actually adds

Three inputs cost-plus does not have.

Elasticity. How volume responds to price, measured per SKU rather than assumed for the category. This is where the counterintuitive findings live - the item where a 6% increase barely moves units, the one where a 3% cut triples them.

Competitive position. Where you sit right now, per channel, on the items that matter. Not where you sat when the file was built.

Product role. Traffic drivers, margin generators, and long-tail items should not be priced by the same logic. Classifying SKUs by product role is what makes differentiated pricing manageable rather than a spreadsheet of one-off exceptions.

Retailgrid's price optimization engine combines these to propose the margin-optimal or revenue-optimal price per SKU, scored for confidence, returned as a regular price, promotion, or markdown.

The objection worth taking seriously

"We tried optimization and the team overrode everything."

This is the most common failure and it is usually not a modelling problem. It happens when a system produces a number without reasoning. A category manager handed €47.30 with no explanation cannot defend it to a CFO, so they revert to something they can justify - and once overrides become routine, you are paying for pricing analytics software that changes nothing.

The fix is structural. Every recommendation should open to show which rules applied, which were violated, the feasible price range, and the margin impact before you commit. When the reasoning is visible, overrides drop to the cases that genuinely need human judgment.

Cost-plus does not disappear

This is the part vendors undersell. Optimization does not replace your cost discipline - it sits on top of it.

The right architecture keeps cost-plus as a hard floor that no recommendation can breach, then optimizes above it based on demand and competitive signals. You keep the guarantee that nothing sells below a defensible margin, and you stop capping your upside at whatever markup someone picked in 2019.

That also means cost-plus stays the right primary method where it belongs: thin-data categories, private label, deep long tail where competitive data is sparse.

Where to start

Not with the whole catalog. Pick one category with decent sales history and real competitive data, set the margin floor, run recommendations alongside your existing method for a few weeks, and compare.

If you want to size the opportunity before running anything, the ROI calculator estimates the gross-profit upside from your own catalog numbers - a more grounded starting point than a vendor's average.