Orders, bookings, rentals, and invoices belong together.
The words change for the trade. The records underneath remain connected.
Built for every way your merchants work.
Made to match how they work.
Less admin, more business.
View all capabilitiesProducts become dishes, treatments, rooms, courses, or tickets.
Packages appear when the business needs them.
Different on the surface. One engine underneath.
A catalogue shape
Menus, variants, services, rooms, and ticket tiers use the same catalogue model, presented as each trade expects.
A set of packages
Bookings for a clinic, tables for a restaurant, subscriptions for a gym, or invoices for a consultant.
A default configuration
Opening hours, tax treatment, fulfilment choices, and staff roles give every merchant a useful first version.
One merchant sees their trade. You see the whole network.
One deployment, not a portfolio
Eight kinds of business on one engine means one operating model, one upgrade path, and one security review.
Comparable records
A restaurant order and a clinic booking share a model with different fields, giving the institution a coherent view.
A new trade is configuration
Add a catalogue shape and package set instead of commissioning another platform and maintaining another fork.
Build one platform for every merchant you serve.
Start with a working shape.
Choose a template for the trade, then let the merchant change the details before anything goes live.
Browse templates