Food, retail and supermarkets run as modules on one platform — the same customer accounts, the same dispatch, the same reporting. Here a vertical is configuration, not a rebuild.
A module is a vertical's worth of behavior configured on top of layers every vertical already shares. It is not a second app, a second tenant or a second deployment.
The distinction decides what expansion costs you. Bolt a second vertical onto a food-only system and you inherit two merchant onboarding flows, two dispatch systems, two apps for a customer to install and two sets of numbers that never quite reconcile. Keep the shared layers shared, and the module only has to supply the part that genuinely differs.
One account, one address book, one saved payment method, one wallet and loyalty balance, one app on the phone. A new vertical shows up as a section of the app your customers already have — not a second download and a second signup.
One onboarding flow, one merchant dashboard, one settlement and payout run — whether the merchant is a restaurant, a corner shop or a supermarket chain.
One dispatcher panel and one driver pool across every vertical, with auto-dispatch scoring distance, load and vehicle type, plus third-party delivery on demand when your own fleet is stretched.
One analytics stack reading across verticals, so a customer who orders dinner on Friday and groceries on Sunday shows up as one customer in one report.
Because those four are shared, the marginal cost of a vertical is configuration rather than construction — which is why "can we add groceries later?" has a boring answer here. The layers themselves are documented capability by capability on the platform features page, and the team that builds and runs them is described on the about page.
Everything a module adds sits on top of the four shared layers above. What follows is what each one contributes — the catalog, the ordering flow and the merchant tooling that vertical actually needs.
Complete restaurant ordering ecosystem with menu management, kitchen printing, real-time order tracking, and delivery coordination for seamless food ordering experiences.
Comprehensive retail ordering platform supporting grocery, pharmacy, electronics, and specialty stores with per-outlet stock tracking and customer ordering capabilities.
Large-scale supermarket ordering platform with bulk ordering, scheduled deliveries, and comprehensive category management for grocery and household essentials.
Transportation services platform with driver management, intelligent route optimization, dynamic fare calculation, and real-time tracking.
Comprehensive logistics and courier services with package tracking, delivery confirmation, and fleet management systems.
Service booking platform for salons, healthcare, consultations, and professional services with calendar management.
The first list is what you stop paying for twice. The second is what each vertical genuinely needs of its own — knowing it up front is what makes a second launch smooth.
The longer version of this argument — including what an expansion does to your unit economics — is in Adding a Second Marketplace Vertical.
You can start on any single module and add the others as the business grows. This is the order the additions tend to work in.
No second tenant, no parallel install, no migration. Your customers, merchants, drivers and order history stay exactly where they are, and the new vertical appears beside the one you already run.
This is the real work of a second vertical, and it is worth doing narrowly: ten well-run stores with clean catalogs beat fifty half-onboarded ones. Catalog quality is the make-or-break variable in grocery and retail.
An announcement inside an app you already own beats any acquisition campaign. The account, the address and the payment method are already there — which is the single biggest asset the second vertical inherits.
Shared couriers are an advantage right up until scheduled grocery windows collide with the dinner rush, so monitor cross-vertical load early. Because the platform bills per order, a slow-starting vertical stays a small line item that grows only as it earns.
None of that renegotiates your economics. A second vertical adds order volume to the plan you are already on rather than a second subscription, and the per-order rate falls at every step up the plan ladder — so more verticals push your unit cost down, not up.
Three verticals are live. Three are not, and the labels on them are the whole of what we promise about them.
2 of them are marked “Upcoming” and 1 is marked “Planned”. Those labels are the entire commitment: no ship dates are published for them, no price is quoted against them, and nothing anywhere on this site counts an unreleased vertical as something you are buying today. Choose the platform for the 3 modules that are live.
When one does ship, it arrives the way any module does. Existing customers get priority access, the vertical integrates into the platform you are already running, and there is no rebuild and no data migration — the shared layers it needs are the ones your marketplace is already using. If a roadmap vertical is the reason you are evaluating us, say so when you book the demo and we will tell you where it actually stands rather than where we would like it to be.
Launch food delivery, retail, and more on one white-label platform — live in days.
Book a live demo on a real marketplace · Setup in days