Delivery platform orders, managed alongside your dine-in and takeaway orders. You never run delivery from a separate screen, and you never run it from a separate set of numbers.
DeliverooJust EatUber Eats and the local delivery platforms our operators already run on are live today. Wolt, Bolt Food, Just Eat and Deliveroo are on the integration roadmap, and a new platform takes about two weeks of our development time once we have its API. Tell us which platforms you run on and we will tell you exactly what is live in your country. Whichever ones you end up using come with your plan, with no surcharge per channel.
Delivery orders land on the same screen as your dine-in, phone and takeaway orders. Your team looks in one place, sees where each order came from and runs all of them from there.
Watch every order at once, or filter down to one or two delivery platforms and see only those.
You accept an order or reject it with a reason. Either way the platform is told immediately, so the guest is not left waiting.
A mapped item takes its recipe ingredients off stock even when the order came from a delivery platform. Your evening count reflects reality.
Whether the order is a single burger or a combo holding a burger, fries and a drink, dojofood splits the items and sends each one to its own kitchen. The hot line does not sort through the bar's work.
Tickets print according to the printer rules you set. You do not build a separate layout for delivery orders.
For each kitchen you define a warning and a critical threshold in minutes. An order past the threshold changes colour and sounds an alert, so a delay in the kitchen is noticed at once.
Delivery orders are visually distinct on the kitchen screen. They never blend into table orders, and it is obvious at a glance that they need packing.
Kitchen staff mark items ready in one tap, all at once or item by item. Everyone reads the order's state off the screen, so nobody walks back to the kitchen to ask.
When you mark the order ready, when it leaves and when it is handed over, the status goes back to the platform. The guest follows it in their own app.
The platform's courier can take it, your own courier can run it, or the guest can collect it. You manage all three from the same screen.
You manage your restaurant's state on the delivery platforms from dojofood. You do not open the platform's panel and do the same job twice.
If the kitchen is behind, you close your restaurant to orders from dojofood without going to the platform's screen. You decide how long it stays closed.
If your own courier is unavailable at that hour, you turn off delivery only. The restaurant stays open and takeaway orders keep coming.
You see how many orders came from each delivery platform and what they earned, consolidated or platform by platform.
A delivery order lands in dojofood, goes to the kitchen, and every status change is reported back to the platform automatically. Orders reach the kitchen under the names of the mapped items in your catalog. Kitchen operations stay clean.
enabled per branch
same catalog
one order screen
guest notePlease don't ring the bell
hot kitchen
bump by item
the order arrives in dojofoodthe status travels back to the platform
Uber Eats, delivery order. Status: Pending. This channel has 7 steps.
The blockages operators running several delivery platforms describe most often, and how dojofood resolves them.
Either three or four tablets sit next to the till, each with its own beep, or one screen carries a stack of open tabs. In a rush, working out which platform an order came from takes time on its own. Managing sales and merging reports means going through every platform separately.
Every delivery order lands on the same screen as your dine-in and takeaway orders. Your team looks in one place and runs the order from there.
The more platforms you put your items on, the further their descriptions, contents and prices drift apart, until nobody is sure which one is right. Even with an integration in place, without the infrastructure to map items, what you think is one item is really being managed as several separate records. Recipes then do not work, ingredients never come off stock and nobody can tell you what that item earns. Merging and cleaning the data falls to you.
You map the platform's items to the items in your dojofood catalog. Mapping happens once. After that every order for that item is written against the right item card, its recipe comes off stock and your sales report reflects reality.
You may want to sell at a different price on each delivery platform, but most integrations do not allow it. Anyone who wants separate prices ends up defining the same item a second and third time. Those copies drift apart over time, it becomes unclear which one is current, and the reports turn into a mess.
The item is singular and the price varies by branch and channel. The branch's standard price applies everywhere; if you want to sell differently on one delivery channel, you change the price on that channel. You never create a new item to do it.
Saturday night, the kitchen fills up and the orders keep coming. Closing means opening the platform's panel, remembering the password and finding the right screen. Most of the time it never happens and orders run late. When it does happen, reopening gets forgotten and the restaurant sits closed for nothing.
You close your restaurant to orders on the delivery platforms from dojofood, without touring screen after screen, and write how long it should stay closed; it reopens on its own when the time is up. Courier availability is a separate setting: if your own courier is unavailable you turn off delivery, and the restaurant stays open for collection.
A business with three branches and four delivery platforms at each has twelve platforms to manage. Items, prices and recipes change; something has to be pulled from sale or a new item added. Running all of that separately is a heavy operational burden. You tell the branch staff, and they do it, or they don't, or they forget. The result is confusion, workload and a chain nobody can govern.
In a chain you run every delivery platform through dojofood too. Which branch is open on which platform, the branches' working hours and the courier hours are all set from there. A shared item catalog and channel level prices let you make changes centrally.
A delivery integration is a layer binding your order management software to the delivery platforms: it carries data between two systems somebody else built. Keeping that connection alive is hard in practice, and a change on either side can cut the conversation. A poorly monitored integration can stop at your busiest moment.
At dojofood we monitor whether the integrations are working. When something falters we usually see it before you do, contact the platform and follow the resolution on your behalf.
Operators in this industry complain that after buying an order management system they pay separately for every module. A QR menu costs extra, connecting the first delivery platform costs extra, and if you need a second one, that costs extra as well.
At dojofood every feature is included in your plan. How many delivery integrations you use makes no difference; you start using them on the plan you already have. Instead of separate module invoices, you use all of dojofood with your attention on growing the business.
When orders arrive from delivery channels, you are not left managing each platform's orders and financial data separately. You run the order from arrival to handover inside dojofood; the line on the order is an item from your catalog, and its recipe takes ingredients off your stock. You stop dealing with platforms one by one and read order and financial data in one place.
From a cloud kitchen to a neighbourhood cafe, the same integration is set up around how your business runs. Pick your business type and see what we do for operations like yours.
What operators ask about delivery integrations.
Integrations are built per market. Uber Eats and the local delivery platforms our operators already run on are live today, and Wolt, Bolt Food, Just Eat and Deliveroo are on the integration roadmap. Tell us which platforms you run on and we will tell you what is live in your country and what we would build. Whatever you end up using is included in every plan; you pay nothing extra per channel.
On the Branches and Channels screen you pick your branch and switch on the delivery channel you want to connect. You enter the API credentials that platform issued you. Credentials are stored per branch and per channel, so each branch connects with its own account. Once the connection is up, you move on to item mapping.
Tell us on the demo call or through the contact page. A new delivery integration takes about two weeks once we have API access to that platform. That is our development time; the platform granting you access can take longer on its own.
On the same order screen as your dine-in, phone, takeaway and QR menu orders. The channel tabs across the top show only the delivery platforms that are switched on for that branch, so you can watch all of them at once or move to a single channel. A new order lands without delay and sounds an alert.
Yes. When you accept it, start preparing it, mark it ready and hand it over, the status travels back to the platform. You never open the platform's own panel to mark the same step twice. A delivery order moves through seven steps: pending, accepted, preparing, ready, on the way, delivered, completed. Orders from your own channels finish at ready.
They do. Item options, removed ingredients and whatever the guest typed stay attached to the order, and they appear exactly the same on the kitchen screen and on the kitchen ticket. Because each item's kitchen is set on its item card, a delivery order reaches the right station too.
In part. dojofood does not push a menu to a delivery platform. It pulls that platform's items into dojofood and you map each one to the matching item in your catalog; you map categories, option groups and combo groups the same way. Once the mapping is in place, an order from that channel is written against the right item card, its recipe comes off stock and your channel price applies. You also open and close mapped items for sale on that platform from dojofood. The item's name and photo on the platform stay in that platform's own panel.
From the Branches and Channels screen you close that channel and write how long it should stay closed. When the rush passes you open it again in the same place. Courier availability is a separate switch, so if your own courier is unavailable you can turn only that off and keep the restaurant open.
Yes. For every branch and every channel you define working hours day by day. The hours the restaurant is open and the hours the courier works are set separately. If your branch closes at 23:00 on weekdays and 02:00 at weekends, you write that once and every delivery channel follows the same calendar.
Your branch's standard price applies on every channel. If you want to sell at a different price on one delivery channel, you set that item's price for that channel. Prices are entered as amounts; there is no percentage rule. Because the channel price sits on the item itself, you never define the same item twice or keep a separate menu.
Yes. You decide which platform is open at which branch. One branch can run on three platforms while another runs on none. API credentials are held per branch as well, so branches never use each other's accounts. The catalog stays shared and branches work from the same items.
They do for items you have mapped that have a recipe. Whatever channel the order arrives from, the recipe's ingredients come off stock in their base unit. When stock falls below the threshold you set, it appears on the alert list; whether to keep the item on sale is your call.
You map the platform's payment methods to your own, so they land on the right line in your reports. Cancellation reasons are mapped the same way. Mapping is done per platform, and not every platform's API exposes payment methods; where one doesn't, dojofood tells you so on the mapping screen.
No new orders arrive from that channel and everything else keeps running. You keep taking dine-in orders, using your kitchen screen and serving orders from your other delivery platforms. If the outage is on the platform's side you write to your account manager, who follows it up on your behalf.
Yes. The home screen shows revenue and order count per platform, along with your best performing delivery platform. You take end of day reports with a channel breakdown and export them as Excel or CSV. Item level cost uses your recipe cost; platform commission is not part of that calculation today.
You import your menu with AI, finish the basics with the setup wizard in about 10 minutes, and start using dojofood. Delivery integrations are separate: platforms granting API access and running their approvals can take a few days. Every business has an account manager, and you write to them directly when you get stuck.
No. The delivery integrations you use are included in every plan. There is no per channel surcharge and no separate connector fee. You try dojofood free for 7 days, and a 30 day money back guarantee applies after that.
Walk us through your current stack, your marketplace list, your volume. We'll show you exactly how dojofood fits, what it replaces, how to get started, and what it costs.
