Product

One engine, two lenses on supply and demand.

Promising turns an order into a dated plan; Policy sets the stock rules behind it. Both read the same picture, so they never disagree.

Book a demo

Fulfilment plan · proposed

SO-48213 · 1 300 u · requested 21 Nov

On time

Likely 18 Nov range 16–21 Nov

600 u confirmed · 400 u scheduled · 300 u estimated

T1 · 600 u

T2 · 400 u

T3 · 300 u

10 Nov13161922

Tranche	Source	Date	Reliability
T1 · 600 u	Lyon DC, on hand	2026-11-13	Confirmed
T2 · 400 u	Rotterdam, PO-7731	2026-11-16	Scheduled
T3 · 300 u	Brno supplier, lead-time stats	2026-11-18 (16–21)	Estimated

Supply order to emit

PO · 300 u · Brno · order by 2026-11-04

Fictional order, for illustration.

Adjust Commit plan

Lens 1

Promising

A real order becomes a fulfilment plan: tranches by quantity, source, date and reliability tier, plus the supply orders to emit. Feasibility and likely lateness are stated with their range.

Read about Promising

Lens 2

Policy

Reorder point, order quantity, safety stock and default mode for each item and location, with the service-vs-cost trade-off shown as options you compare.

Read about Policy

How it works

Onboard any org by declarative mapping.

Provisor reads your existing objects. You describe where orders, stock and supply live; no custom code is written in your org.

01 · Map
Describe your data model
Point Provisor at the objects that hold orders, stock snapshots, purchase orders and transfers.
02 · Derive
Derive statistics, with sources
Lead-time and demand statistics are derived from your receipt and order history. Each one shows the records it came from.
03 · Decide
Preview, refine, commit
Your planners review proposals in the cockpit and commit the ones they accept.

Mapping · illustrative

order        → Order
order_line   → OrderItem
stock        → Inventory_Snapshot__c   (daily, 06:00 UTC)
supply       → Purchase_Order__c, Transfer__c
receipt      → Goods_Receipt__c
lead_time    ← derived from receipt history
location     → Warehouse__c

Object names are examples. Provisor validates each mapping and reports gaps before the first proposal.

In the cockpit

The same plan, inside Salesforce.

Confirmed

On hand, or a date the supplier has confirmed.

Scheduled

A planned receipt with a date, not yet confirmed.

Estimated

Derived from lead-time statistics, shown with its range.

Fill rate against holding cost

SKU 40-118 · Lyon DC

Fill rate is likely value; B shows its P10–P90 range. Derived from 26 weeks of demand and 14 supplier receipts. Fictional data.

Proposed policy, option B

Reorder point: 820 u
Order quantity: 450 u
Safety stock: 210 u
Default mode: Make to stock
Fill rate, likely: 97% (95–98%)
Holding cost per year: €20 750

210 u safety stock

Demand · 26 weeks, mean 118 u/week, σ 38 u Lead time · Rotterdam, P50 10 d, P90 12 d, 14 receipts Target · fill rate 97%, set by you

Compare with C Commit policy

See both lenses on your data model.