From demand to cash — in one operating network
invent.sale connects customer demand, pricing, assortment, inventory, suppliers and working capital — turning an export from your accounting system into executed decisions.
Cover dropped to three days
Demand is computed from goods movement, excluding write-offs and returns.
Platform logs as of 4 August 2026. No effect percentages here: the comparison baseline has not been agreed with clients.
One network. Different participants. One operation.
Each sees their own slice of the cycle and their own job — yet everyone works on the same order.
Keep availability without inflating stock or breaking payments.
- Need across every location in one list
- What a transfer covers, and what must be bought
- Which orders are waiting for confirmation
From a customer signal to a repeat purchase
Ten steps that usually live in different systems and different heads. Here they are one chain, with a record at every step.
- 1DemandA customer takes an item off the shelf
- 2DemandPrice and assortment decide what they found at all
- 3SupplyDemand is recomputed from goods movement
- 4SupplyA location's need appears, in days of cover
- 5SupplyThe hub splits stock; the rest becomes an order
- 6NetworkThe order goes to the supplier on schedule
- 7NetworkThe supplier confirms or amends lines
- 8NetworkReceiving is recorded, discrepancies included
- 9CashThe obligation enters the payment calendar
- 10DemandThe item is back on the shelf — and the customer returns
Four layers. One trading cycle.
Layers switch on one at a time and share one core. Start with any of them; the rest need no migration.
What to order, how much, when, where to, and from whom?
Compute each location's need, not a network average
A daily store request nobody has to assemble by hand
Split scarce stock deliberately, not evenly
Prevent a write-off before the goods lose their value
Build a supplier order on the full economics, not on price alone
One interface to the whole ecosystem
Director is not a chatbot on top of a dashboard but one interface to every product. An answer always carries its data source, its period, and what happens if the action is confirmed.
What runs out in seven days?
34 items across four locations, 11 of them with no open order. Cover and stock are shown per line.
Who has not confirmed an order?
Six suppliers this week. For two of them the channel does not deliver at all — that is a separate problem, not silence.
Why will there be a gap in two weeks?
Three approved orders share a payment date. Moving one of them closes the gap — the scenario is ready to confirm.
One data graph. One decision core.
That is why a decision made in analytics reaches the supplier without anyone re-keying data, and the supplier's answer lands back on the very product record where it started.
Three companies running on this every day
We have no wall of logos. We have three clients in production — and for each you can see what runs and where we got it wrong.
Daily hub-to-store allocation, and a separate order for every supplier — on their day, in their format.
What we found: A cut-off threshold was quietly dropping slow movers: cosmetics and orthopaedics vanished from the calculation while sitting on the shelf.
Scheduled auto-ordering to 535 suppliers, and a one-tap reply right in the messenger.
What we found: A write-off document counted as a sale — the system kept reordering yesterday's bin contents. After the fix, ordering in two stores fell 16% and 7% at the same availability.
Supplier price lists parsed: the same part is reconciled across dozens of files, showing who is cheaper for it right now.
What we found: Not every client needs the whole platform. A distributor has no shelf and no allocation — exactly one piece runs, and that is fine.
Why this is one system
Price drives demand. Demand drives stock. Stock creates an order. An order creates a payment obligation. On-shelf availability decides whether the customer returns. You can split that chain across separate systems — but then every link is optimised on its own, at the expense of the next one.
Runs on top of your existing infrastructure
We do not promise “any ERP in 15 minutes”. We start read-only, check data quality and choose a safe integration route. The timeline depends on your configuration and the readiness of the sources.
1C (OData or file export), POS, warehouse systems, supplier price lists in XLSX, CSV exports, SQL and REST.
The file route matters as much as the direct one: in some networks 1C sits in a closed environment with no outside access.
Every company's data is isolated
The platform is meant to be neutral market infrastructure — and neutrality rests on how access is built, not on a promise.
- Each network has its own tenant: database, keys and schedules. One client's request cannot technically reach another's data.
- A connection starts read-only. Write-back is enabled by a separate client decision, not at deployment time.
- A supplier sees the order addressed to them and nothing beyond it.
- One network's data never reaches another — anonymised extracts included. We neither sell it nor use it for third-party market analytics.
- We hold no ISO or SOC 2 certification and do not imply one with badges. If your policy requires it, say so in the first conversation.
Deployment without replacing your ERP
You can stop after any step and still keep the result. We do not quote “first results in 14 days”: it depends on what your export actually contains.
- 1Process and data reviewus and whoever knows your 1C
- 2Read-only integrationus, with your administrator
- 3Data quality baselinejointly with your 1C integrator
- 4Shadow modeyour buyer, two to three weeks
- 5Controlled launchthe owner decides, the buyer agrees
- 6Automationthe platform, watched by your team
- 7Expansionyour process sets the pace
“You still need a person”
Yes. The system takes over recalculation, order assembly and distribution. What is left to a person is what they answer for with money: terms, exceptions, and the decision to send.
- You can see where the number came from
A recommendation shows demand, cover, stock on hand and the supplier's lot.
- Any line can be edited
The edit is stored with author and time — and later it is clear who was right.
- Large orders need confirmation
The threshold is set by the network owner. A big order never leaves silently.
- The system's own failure is surfaced first
An empty send, a dead channel, a failed export — these are incidents, not silence.
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.