invent.sale
Supply · Forecasting and replenishment

Compute each location's need, not a network average

The core figure is days of cover: how long the current stock lasts at the current rate of sale. Everything else is ranked by it, and the order quantity is derived from it.

who this is for

buyer, operations director, owner

layer
Supply

What is wrong today

  • Orders are placed “as usual”, unrelated to a location's actual cover.
  • Write-offs and returns land in sales statistics and inflate the next order.
  • Slow movers drop out of the calculation while sitting on the shelf.

How it works

Demand from movements, not from a sales report

Write-offs, returns and transfers are excluded. Not a hypothetical: in one network a write-off document counted as a sale, so the system kept reordering yesterday's bin contents.

Lead time and safety stock per supplier

One supplier delivers in three days, another in two weeks — the need follows that, not a network-wide norm.

Rounding to what actually ships

Pack multiples and minimum lots are the supplier's constraint. If the lot exceeds a week of demand, that is visible before the order goes out.

the working screen

What it looks like in use

Sorted by cover: what runs out first sits on top, not what costs more.

invent.sale · Supply · Demand forecastcomputed today, 05:40
All locationsRuns out before delivery23Overstock51
ItemLocationDaily salesOn handDays of coverState
Drinking water 0.5 lLocation A3441012 daysfine
Drinking water 0.5 lLocation B51962 dayswill not make it
Wet wipes, 60 pcsLocation C864080 daysoverstock
Toothpaste 100 mlLocation D1720512 daysfine
this supplier's lead time is 5 days · red rows run out before itGo to replenishment
The forecast sits next to the stockA sales number alone means nothing. It gains meaning next to how many days of stock are left.
Lead time drives the highlighting“Two days” is a stockout when the supplier takes five. The comparison is against lead time, not zero — and it comes early.
Broken down by location, not by networkA network average hides both the stockout and the dead stock: empty in one location, eighty days of cover in another.

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

What it is built on

  • Dead stock and the cash in it are computed per location today — the same calculation, minus the expiry date.
  • Transfers between locations already work: the mechanism is ready, what is missing is the trigger to fire it in time.
  • Write-offs are already excluded from demand — otherwise an expiry product would reorder exactly what it just wrote off.

Who stays in control

Any line can be edited by hand, and the edit is stored with its author and timestamp. A large order can require explicit confirmation — then it never leaves on its own.

How it is measured

By comparing the system's calculation with what a person would have ordered over a parallel period: where it matched, where it did not, and why. Then by cover and the share of lines needing no manual edit.

what to read next

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.

Forecasting and replenishment — invent.sale