We have our own accounting system
You can keep your accounting and compute on top of it. You can move onto ours — it exists, and locations and warehouses run on it. The difference from a classic ERP is that there is nothing to buy on top: one subscription, everything included.
Pay for one product, get every capability
There are no modules. Everything below is in the subscription from day one: nothing is sold as an extra licence or spun off into a separate rollout.
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.
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.
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.
Order, confirmation, delivery, receipt and discrepancy — one chain, each step stamped with a time and a name. The supplier installs nothing.
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.
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.
How ERP is usually sold, and how it works here
The difference is not the feature list but what you are charged for, and when the first value appears.
| Question | Usually | Here |
|---|---|---|
| What the price is made of | a core plus modules: ordering, analytics, mobile — each priced apart | one subscription; everything above is in it |
| When you need something new | a new licence and a new implementation project | switched on in settings; the price does not move |
| What is counted | per seat and per module | by the size of the network: locations and warehouses |
| Time to the first result | months: the whole rollout first, value afterwards | weeks: the maths on your data first; the move later, if you want it |
An anonymised example: the dataset is shared across every screen on this site.
Three ways
Connected
The accounting system works and nobody plans to change it. What is missing are the decisions: need, allocation, supplier ordering.
We read an export or connect directly, compute, and send the order. Nothing is written back until you allow it.
Decision quality is capped by export quality: what is missing from the data is missing from the maths.
Hybrid
Some processes are easier here — usually supplier ordering and store work — while accounting and the warehouse stay put.
We agree where the system of record lives for each entity, and enable write-back only for those.
It demands discipline: two systems of record for one entity is the fastest way to a mismatch.
Native
There is no accounting system, it cannot carry the network, or it is run in spreadsheets. Then we become the retail or distribution system.
Catalogues, stock, orders, receiving and store operations live here. Bookkeeping stays with the bookkeepers.
It is the longest route: what moves across is data, habits and people — not just tables.
The three ways side by side
In all three cases bookkeeping stays in your system: we do not replace it and do not intend to.
| What | Connected | Hybrid | Native |
|---|---|---|---|
| Product catalogue | in your system | yours, with a reconciled copy here | here |
| Stock per location | read from the export | kept here, pushed to accounting | here |
| Supplier order | here; the file goes to the supplier | here, returned into accounting | here |
| Receiving and discrepancies | in your system | here; the document goes to accounting | here |
| Till and receipts | your till; we read the sales | yours or ours | our till |
| Bookkeeping and reporting | in your system | in your system | in your system |
| How long the start takes | fastest: an export is all it takes | longer: the system of record must be agreed | longest: data and habits both move |
An anonymised example: the dataset is shared across every screen on this site.
When the whole system is needed
Two builds: one for a network of locations, one for distribution. They differ not in styling but in whose shelf it is and who decides.
When there are many locations and accounting lives in spreadsheets — or in a system that cannot compute need — we cover the network's whole operational loop.
A distributor's goods live on someone else's shelf, and the decision is made by a rep on the spot. That calls for a warehouse and a view across outlets and people.
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.