Kadıköy · flagship · all channels
Full Turkish stack
Yemeksepeti ON +8% · Trendyol Go ON +10% · Getir Yemek ON +8% · Wolt off · Migros Yemek ON +8%.
Multilocation · Marketplace
Branch A on Wolt. Branch B on Yemeksepeti. One catalog runs both.
One catalog underneath. Different marketplace mix per branch. HQ sets the policy, branches opt in.
The branch-marketplace matrix
One catalog. Different marketplaces per branch.
Real estates don't have the same marketplace mix at every branch. Neighbourhood, country, kitchen capacity — they all change the math. So the marketplace mix is a per-branch decision, with per-channel pricing on top of the same catalog.
Bağdat Caddesi · premium · YS only
One channel by choice
Yemeksepeti ON +12% · Trendyol Go off · Getir Yemek off · Wolt off · Migros Yemek off.
Beşiktaş · mid · 3-channel
Selective mix
Yemeksepeti ON +8% · Trendyol Go ON +10% · Getir Yemek off · Wolt off · Migros Yemek off.
Amsterdam · Centrum · EU stack
EU channels only
Wolt ON +9% · Turkish marketplaces n/a (channel not active in country).
ON · live on this channel. off · disabled at branch. n/a · channel not active in country. Same menu underneath every row. Different mix on top. The matrix isn't a spreadsheet — it's the live configuration HQ runs from.
Per-branch overrides
HQ sets the policy. Branches opt in per marketplace.
HQ owns the brand: which marketplaces are allowed, the default markup, the catalog. Branches decide which channels they actually run and how much capacity to give each one. Same brain, branch-level control.
01 · HQ-level policy
The brand decides which marketplaces are allowed.
HQ approves the marketplace list, sets the catalog standard, and defines the default markup bands. A branch can't turn on a channel that the brand hasn't authorised. The estate stays on-brand.
02 · Branch-level opt-in
Each branch decides which marketplaces to actually run.
Bağdat Caddesi only does Yemeksepeti — the chef hates Trendyol's commission. Fine, turn it off at the branch. Kadıköy runs the full Turkish stack. Also fine. Per branch, per marketplace.
03 · Per-channel pricing override
Branch can override the markup band within policy.
HQ allows 6-12% markup on Trendyol. A branch with a higher-margin neighbourhood sets 10%. A branch with thin margins sets 12%. The catalog stays one menu. The markup is per branch, per channel.
04 · Availability per slot
Close a channel for an hour without touching the menu.
Friday 8pm and the kitchen is buried — pause Wolt for 30 minutes at this branch only, dine-in and the other branches keep going. The catalog doesn't move. The availability does.
Per-country compliance
Different countries, different marketplaces alive.
A Türkiye branch runs Yemeksepeti, Trendyol Go, Getir Yemek, Migros Yemek. A Netherlands branch runs Uber Eats and Wolt. dojofood only shows the marketplaces live in that country — no manual filtering, no "why is this Turkish app on my Amsterdam branch?"
Türkiye
Yemeksepeti · Trendyol Go · Getir Yemek · Migros Yemek. Live integrations on the Turkish stack today. The four marketplaces operators actually use, with TR-side rules and KVKK compliance baked in.
Netherlands
Uber Eats · Wolt · Deliveroo (coming). The EU mix for an Amsterdam branch. GDPR data residency, EU-side commission rules, EUR-denominated reporting.
Beyond
Missing your country's marketplaces? Tell us. About two weeks. Coming: Bolt Food, Just Eat, Lieferando. Tell us yours when you book the demo — we add new integrations in about two weeks once a real operator needs them.
Reporting roll-ups
See which branch + marketplace combos earn vs leak.
A marketplace that prints money at Kadıköy bleeds margin at Bağdat Caddesi. The combo matters. Roll-up reports show net revenue, commission, food cost, and contribution margin per branch × per marketplace — so HQ kills the bad combos without killing the channels.
01
Per-branch per-marketplace P&L
Net revenue, marketplace commission, food cost, contribution margin — broken out per branch and per channel. The leaky combinations show up in red.
02
Channel mix trends
Which marketplace is growing at Beşiktaş this quarter? Which one is shrinking at Şişli? Branch-level channel trends, not estate-level averages that hide the truth.
03
Kill the combos that don't work
One-tap to turn off a channel at a branch where it's leaking. The catalog stays put. The combo goes away. No menu deletion, no branch shutdown, no email chain.
A real operator scene
The same catalog, different mix per branch.
Bağdat Caddesi branch on Yemeksepeti only — chef hates the Trendyol commission. Kadıköy branch on Yemeksepeti + Trendyol Go + Getir Yemek. Same catalog. Different markup on Trendyol. Different availability windows. One HQ view across both.
HQ raises the burger price by ten cents. Catalog updates. Kadıköy's Trendyol listing reflects +10c +10% markup. Bağdat's Yemeksepeti listing reflects +10c +12% markup. No copy-paste. No spreadsheet. No "did Bağdat get the update?" check on Monday. One catalog. Per-branch per-marketplace rules. One brain at HQ.
See Multilocation Management → See Marketplace Integrations →
Have questions? Let's talk.
Show us your branch list. We'll show you the matrix.
Bring your branches, your marketplace mix, your markup policy. We'll show you the live matrix — and what changes when HQ stops chasing Yemeksepeti updates across spreadsheets.