A multi-market franchise on a regional platform
The same catalogue operated in several countries on a platform with no public API, where every market has its own prices, its own compliance answers and its own idea of what a product is called.
In development · founding partners onboarding from Q4 2026
For distributors & franchise operators
One catalogue, several operations, and buyers who are companies.
Distribution and franchise operations are not a different product — they are the same records with price contexts, B2B intake and shared availability on top. Most of that layer is planned, and this page marks every part of it.
Three shapes we recognise
Described from the operation, not from a customer.
B2B orders next to retail orders
A buyer who is a company: a VAT id, reverse charge, a price context that is not the retail one, and an order that arrives as a file rather than through a checkout.
Availability shared with suppliers
The people upstream need to know what you can promise, and the people downstream need to know what you have. Today that is a spreadsheet emailed on a Monday.
The B2B operating mode
Four parts, and three of them are planned.
Price contexts per customer type
PlannedRetail, B2B and per-contract prices as contexts on the same variant rather than as duplicate products.
B2B order intake
PlannedOrders from business customers land in the same worklists as marketplace orders, with the VAT id and the tax treatment attached.
Availability sharing
PlannedAvailable-to-promise, shared upstream and downstream, computed from the same reservations the channels see.
Multi-market operation
In developmentReadiness resolved over the markets a channel serves, so an obligation in one country is not assumed to hold in the next.
What exists today
The records the mode is built on.
- Product MasterBuiltlocal build · synthetic data
One record for a catalogue that several operations sell from.
- Inventory & OrdersBuiltlocal build · synthetic data
Availability per location and reservations on the local runtime. The B2B mode above sits on these records.
- Import & ConnectorsIn development
The contract is how a regional platform without an API becomes an integration on day one.
FAQ
Two objections worth making
Our platform has no public API. Are we out?
That is the case TOVIA is built for, and it is why the import contract comes before the connectors. If your platform can produce a file of orders, lines, refunds, customers or products, the contract is the integration — and it is published in full so you can check an export against it today.
Most of what you describe for B2B is planned. Why talk to you now?
Because the parts underneath it are not planned — one product record, availability, reservations and order intake exist on the local runtime. The B2B mode is an operating mode of those records rather than a second product, and founding partners decide the order in which it is built.
Tell us what your platform can export.
A file of orders and a file of products is enough to see your own operation in TOVIA — before any connector exists.