Marketplace integrations

Every marketplace your operators already use.

Live today: Uber Eats, plus the local marketplaces your operators already use. Coming next: Wolt, Bolt Food, Just Eat, Deliveroo. Missing yours? About two weeks once we have the API.

Book a 20-min walk-through →Request a new integration
Live today
Coming next
DeliverooJust Eat
Live today

Fully integrated. Not just "we have an API."

A lot of vendors will tell you they "support" a marketplace and what they mean is they receive the order. That's the easy part. Here is what integrated actually covers on dojofood:

Order receipt with every modifier preserved

No-onions, extra cheese, milk-on-the-side, allergen note — what the customer typed on Uber Eats is what the kitchen reads on the KDS. Modifier loss between marketplace and POS is the most common silent error in this category. We don't lose it.

Status sync, both directions

Accept, reject, ready, dispatched, delivered — the marketplace and dojofood agree on the state of every ticket, every step. The customer's app updates the second the kitchen bumps the ticket.

Menu push, catalog to marketplace

Change an item in the dojofood catalog and the marketplace listing updates from the same source. New burger? Appears on every channel. Discontinued combo? Disappears from every channel. No multi-tab afternoon.

Per-marketplace pricing rules

One marketplace at +a%, another at +b%, a third at parity — whatever the commission math demands. Set the rule once on the channel; the catalog stays singular.

Branch availability schedule

Branch 02 closes the kitchen at 23:00 weekdays, 02:00 weekends. Each marketplace gets that schedule per branch. No "we're showing open but the branch is shut" calls.

Automated 86 and downtime propagation

Stock runs out, dojofood marks it unavailable on every marketplace inside seconds. The Wi-Fi drops at the branch, dojofood pauses incoming on every marketplace, then resumes when it comes back.

These are live in real restaurants today. Each one fully integrated in the senses above.

How one integration works

One catalog → one marketplace → one queue. Same shape, every channel.

  1. You manage the menu once. Items, modifiers, photos, allergens, branch availability — all in the dojofood catalog. The marketplace listing reads from this.
  2. The order arrives. An Uber Eats order lands in the dojofood queue side by side with your dine-in and takeaway. Modifiers intact, customer note attached, dispatch window timed.
  3. You accept, prep, mark ready. Each status hop is sent back to the marketplace automatically. No double-tap, no second tablet.
  4. Stock and pricing stay honest. Item runs out → every marketplace marked unavailable. Price changes → every one updated, each one's markup rule applied.
  5. End of night, one set of numbers. Channel mix is a single dashboard. Each channel against dine-in — one screen, one source.

One integration is not magic. Several working at once, the same way, with the same controls — that's the operational claim.

Built in-house

No bridge between someone else's POS and someone else's marketplace layer.

There is a category of tool that sits as a bridge between your POS and your marketplaces. It runs as a layer between two systems someone else built. Works, until something breaks at the seam.

dojofood is built differently. The POS, the KDS, the catalog, the marketplace integrations — all one product, same team, one data model. An Uber Eats order enters the same queue as your dine-in tickets because the queue was built to receive them both.

We charge less

No three vendors stacked on each other. One subscription, monthly billing.

One number to call when something breaks

Not "the bridge says it's the POS, the POS says it's the marketplace, the marketplace says it's the bridge."

New integrations are a feature we build

Not a contract we renegotiate. Two-week SLA applies because we own the code, not because we own a queue at a partner.

We're not going to pretend the alternative doesn't work. It does. We just don't think you should be stitching together our POS with someone else's bridge when you don't have to.

The boring questions, answered

What operators ask before they sign.

Does Uber Eats let you push the menu from your side?

Yes. We built the marketplace push first — managing the menu inside the marketplace's own panel while the rest lives somewhere else is exactly the drift problem we exist to remove.

What happens when a marketplace's API is down?

We mark that channel paused, let the rest run, and queue the catch-up for when it returns. Your dine-in keeps running. KDS keeps running.

Can each branch be on a different set of marketplaces?

Yes. Branch 01 on a couple of marketplaces, Branch 02 on all of them, Branch 03 marketplace-off — same catalog, separate channel enablement per branch.

Can I see the commission impact on margin per item?

Yes. Cost Management shows per-item, per-channel margin with the marketplace fee folded in.

Are there hidden charges per integration?

No. Every live marketplace integration is in the base plan. No per-marketplace surcharge. No "premium connector" tier.
Have questions? Let's talk.

Don't see your marketplace? Tell us — about two weeks.

20 minutes with our team. Bring your current marketplace mix, the volume per channel, and the integrations you wish you had. We'll show you what's live, what's in flight, and what the two-week path looks like if yours isn't on the list. Live human, your language, under two hours when it breaks. Monthly billing. No per-marketplace fee. No payment-processing lock-in.

Book a 20-min walk-through →Request a new integration