invent.sale
Demand · Shelf Price

Manage retail price and gross margin at the level of every SKU

One habitual markup costs money twice: where the price sits below the market you give away margin, and where it sits above you lose demand. This product measures both, line by line.

who this is for

commercial director, category manager, CFO

layer
Demand

What is wrong today

  • The markup is the same across a category, though price sensitivity differs line by line.
  • Promotions run unmeasured: nobody knows what the discount delivered beyond baseline sales.
  • Markdowns start late, once the goods have already lost value.

How it works

A market range over matched products

Each match to a market equivalent carries a confidence score. An unconfirmed match never feeds a recommendation.

A margin floor as a hard constraint

A recommendation cannot fall below the threshold set for an item or a category — that is the network's rule, not the model's suggestion.

A demand forecast next to the price

As the price moves, expected demand, gross profit and days of cover move with it on the same screen. The decision is made on all three at once.

the working screen

What it looks like in use

One row is one item. The decision rests on three numbers at once: your margin, the market, and the risk of losing the shopper.

invent.sale · Demand · Pricingrecomputed today, 06:00
Whole categoryWorth changing12Below market4
ItemPriceMarketMarginSuggestedRisk
Drinking water 0.5 l3.203.10 – 3.9014%3.50low
Nourishing cream 75 ml34.9029.00 – 38.0041%keepnone
AA batteries, 4 pcs18.0015.40 – 17.2026%16.90high
Shampoo 400 ml22.4022.00 – 26.5031%23.90low
12 items of 340 · the category manager decidesApprove selected
Price and market side by sideNo second tab with competitors' sites, no keeping in your head where you are expensive. The gap is right in the row.
The risky row is highlightedA price that drives customers away no longer hides among three hundred rows — it surfaces on its own.
“Approve”, not “apply”The system does not reach into the till silently. A price changes when a person agreed, and the log shows who.

An anonymised example: locations are lettered and the dataset is shared across every screen on this site.

What it is built on

  • Sales and cost per item are already read from the accounting system — actual margin is computed on them.
  • Days of cover are computed today: without them, changing a price is blind — you can drive demand for goods you do not have.
  • Approvals and the action log already work: the “proposed, approved by a person, recorded” mechanism is in place for orders.

Who stays in control

A price never reaches the till on its own. Every recommendation goes through approval, every change has an author, and write-back to the accounting system is enabled by a separate decision.

How it is measured

Through a control group: some items keep their price, and the effect is the difference in differences. Without a control group the product reports “not enough data”.

Show us one critical process. We will show how it runs here.

We look at your cycle: how an order is assembled today, who decides, where time leaks and what the system takes over.

Start with one critical process

Connect replenishment, supplier ordering or another first workflow, then expand across one platform.

Shelf Price — invent.sale