One subscription for the whole system
We do not sell modules and we do not count seats. The price depends on the size of the network — how many locations and warehouses the system serves. Everything else is included from day one.
No modules, no per-user fees, suppliers pay nothing. Locations and warehouses are what count.
What you are charged for
And, more to the point, what will not appear on the invoice six months in.
The store manager, the buyer, the accountant and the owner all work in the system with no per-head fee. Charging per seat makes two people share one login — and then the log cannot say who changed the order.
The supplier receives the order in an ordinary messenger and answers with a button. They install nothing, register nowhere and buy no access from us — otherwise half of them would never connect.
When a new calculation appears, it is switched on in settings. We do not come back a year later to say the part you need is now priced separately.
The export from your accounting system, reconciling catalogues, configuring suppliers and schedules — that is work on our side, and it is not billed as a separate implementation project.
If the network needs till hardware, scanners or third-party services, they are bought directly and cost what the vendor charges. We do not make money on that.
What the number depends on
The more locations and warehouses, the more decisions the system makes per day — and the more it costs. Within a band the capability set is identical.
Up to five locations
A single store or a small network with one warehouse. Usually starts with need calculation and supplier ordering.
The start takes weeks: all it needs is a regular export from your accounting system.
Six to thirty locations
A network with a hub and allocation. This is where transfers, shelf life and the payment calendar appear.
Store work from a phone and supplier document flow join the calculation.
Thirty-plus locations and distribution
A network with its own warehouse and field reps, or a distributor working someone else's shelf.
This usually calls for our own accounting system plus API access to the data for an internal BI.
What the subscription includes
The same set at every band. Nothing on this list is sold as a separate licence.
- The books: catalogue, stock, receiving
A product record with packs and multiples, stock per location and hub, receiving with discrepancies, recounts, write-offs and transfers. The reason people buy an accounting system in the first place.
- The till and store work
Sale, refund, discount, shift and end of day. A daily action list for the store manager — on a phone, because they are not at a desk.
- Need and ordering
Forecast, replenishment, allocation from the hub, the supplier order and the supplier's reply. Most accounting systems have none of this; where they do, it is a separate licence and a separate project.
- Document flow with suppliers
Order, confirmation, delivery, receipt and discrepancy — one chain, each step stamped with a time and a name. The supplier installs nothing.
- Money: payables and the payment calendar
Who is owed what, what falls due this week, how much cash is parked in stock and what frees up if the pile is cleared.
- The owner's screen and access to the data
A morning summary in a messenger, questions in plain text, big-order sign-off in the same place. Plus read access to your own data over an API — pull it into your BI without asking us.
What people ask before signing
Because an honest number depends on what is in your data. Ten locations with a clean export and ten locations where half the catalogue is entered twice are different jobs. We quote after seeing the export, and the quote does not move afterwards.
No. We can compute on top of yours and write nothing back. Moving onto our system is a separate decision, taken later and for its own reasons — not as a condition of starting.
The data is yours. You get a machine-readable export, and API access works to the end of the paid period. We do not hold a network hostage by keeping its catalogue and history.
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.