Pick the shape you trade in
Each model lists what it turns on, who operates it day to day, and the number that decides whether it fits.
Single restaurant
One restaurant taking its own orders and running its own delivery, or handing drops to a courier. The lightest configuration: no vendor onboarding, no commission engine, no settlement runs.
Single brand, multi-location
One brand, many restaurants. A shared catalogue with per-restaurant pricing, hours, stock, and delivery zones, and orders routed to whichever location can actually serve the address.
Multi-vendor marketplace
You operate the channel; vendors trade on it. Onboarding, commission, payouts, and disputes are the product — the ordering app is just where they surface.
Fleet operator / mobility network
Driver supply is the business. Shifts, utilisation, incentives, and matching latency are what you manage daily, and the same fleet can carry delivery alongside rides.
Enterprise & logistics
High volume, existing systems, and a procurement process. Integration and reporting matter more than the app store listing, and the deployment is usually dedicated.
Side by side
The four decisions that differ. Everything not in this table is identical across all five.
Changing model later
The common growth paths, what each one switches on, and how long the change window runs.
Single restaurant to marketplace
Multi-location to marketplace
Marketplace to fleet network
Model Questions
Commission, fleet ownership, and what happens when your operation is two models at once.
Still unsure? Describe your operation
Can one deployment run two models at once? +
Yes, and it is common. A brand with its own restaurants that also lists third-party vendors runs both on one instance: vendor onboarding, commission, and dispatch rules are configured per group rather than per platform. Your own locations sit in a group with commission off, third-party vendors in a group with commission on.
Does the model change what we pay? +
It changes the configuration effort, so it changes the quote. What it does not change is what you own: branding, the API, the data, and the store listings are in every deployment regardless of model. Pricing is quoted against the configuration spec written in the first three days.
How is commission actually calculated? +
Per vendor, per category, or per order value, with a floor and a cap if you need them. Rules are set in the admin console and take effect on the next order, not the next release. Adjustments, refunds, and disputes are applied against the payout run rather than the individual order.
Do we have to own a fleet? +
No. Every model supports own fleet, third-party couriers, or a hybrid where your riders take what they can and a courier picks up the overflow. The rule is set per zone, so a dense city can run own-fleet while an outlying zone runs entirely on couriers.
What if none of the five describe us? +
Then the answer is a scoping session rather than a model. The five cover almost every operator we deploy for, but the engine underneath is the same in all of them — an unusual operation is normally a combination of two models plus a connector, not a sixth shape.
Tell Us How You Trade Today
Restaurants, cities, order volume, who delivers, and what you run now. We'll map it to a model, a configuration, and a timeline before you spend anything.