In development · founding partners onboarding from Q4 2026
Inventory & Orders
Availability per location, reservations that hold stock while an order is decided, order intake into worklists an operator can actually work — on the local runtime today, connector-fed tomorrow.
Builtlocal build · synthetic dataLocal runtime, synthetic data. No connector is live.
The record
On-hand is what is on the shelf. Reserved is what is already promised. Available-to-promise is the only one a channel should ever be told about — and the only one worth arguing over at month end.
| Location | On hand | Reserved | Available |
|---|---|---|---|
| Marbella · main | 1 240 | 86 | 1 154 |
| Bucharest · 3PL | 512 | 144 | 368 |
| Warsaw · overflow | 96 | 0 | 96 |
The arithmetic
What exists, and what does not
On-hand per location, reserved, available-to-promise — three numbers, kept apart, because collapsing them into one is what oversells a listing. A reservation is held while an order is decided and released with the order's state, rather than by a nightly job.
Orders land in a queue. Anything that cannot proceed becomes a worklist item with an owner, a note and a resolution, and a command centre shows what is stuck and why — which is the difference between an operations tool and a dashboard.
Order state is visible end to end, from intake to dispatch. Carrier and AWB integration is planned: couriers are an integration class here, in the same directory as the marketplaces.
No marketplace or shop connector is live today. The order is deliberate: the import contract lands orders and stock first, read-only connectors follow, and write-back comes only after reconciliation can prove what happened.
Order intake from B2B customers, availability shared with suppliers, and price contexts per customer type — designed as an operating mode of the same records rather than as a separate product, because a distributor's catalogue is not a different catalogue.
Versus the alternatives
| Shop's native stock | A marketplace's inventory | Spreadsheet | WMS | TOVIA | |
|---|---|---|---|---|---|
| Sees every channel | no | no | manually | no | yes |
| Reservations while an order is decided | partial | no | no | warehouse-side | yes, local runtime |
| Per-location availability | rarely | no | manually | yes | yes, local runtime |
| Joined to the product master | one shop | one marketplace | no | no | yes |
| Stays current without a person | yes, one channel | yes, one channel | no | yes | planned — connectors are not live |
FAQ
No. That is planned, and the order matters: the documented import contract first, then read-only connectors, then write-back once reconciliation can prove what happened. Anything that writes to a marketplace before it can be reconciled is a way to lose money quietly.
Locations are first-class. On-hand, reserved and available-to-promise are computed per location and rolled up, so a 3PL and your own shelf are the same kind of thing to the system.
Planned. Couriers are an integration class — DPD, GLS, DHL, InPost, Sameday, Fan Courier and regional 3PLs are in the connector directory with their states.
No, and it should not. A WMS is warehouse-side: bins, picking, packing. TOVIA is channel-side, and it reads what the warehouse says rather than telling it how to work.
What changes for you
Stock you have promised to somebody else stops being counted as stock you can sell.
Operations and customer service
BuiltAvailability, reservations and order intake
An order from any channel lands in the same worklist, in the same shape, whoever it came from.
Order desk
BuiltAvailability, reservations and order intake
When connectors are live, the number a marketplace is told will be the number the system computed — not one a nightly job approximated.
Head of ecommerce operations
PlannedInventory and order sync
Orders, lines and refunds against the import contract. That is the honest way to see this module on your own numbers before a connector exists.