Credentials, platform hours, payment mapping, product matching and price belong to the branch-and-channel intersection, not to the branch; the catalog sits under all of it, written once.
The first control on the screen is the branch. Matching belongs to that branch's store on the platform; switch branches and both the list and the counterparts change.
Your catalog product is the heading; under it, line by line, is the name and price it carries on each platform. The names do not have to agree. The link does.
The unmatched-platform filter leaves only the rows with no link. When you open a new branch, that filter is what tells you where the gap is.
The side rail splits matching into its four surfaces: products, categories, option groups and options, combos. All four are per branch.
The cards are built from the channels open at that branch. A closed channel does no work here; it is opened on the Branches and Channels screen first.
Turn it off and that branch's store on that platform stops taking orders. You do not touch the menu, the catalog stays put, and the other branches keep going.
With no driver, you turn off courier availability without closing the store. The dining room and dine-in orders are untouched.
At the foot of the card sit the average prep time and rating the platform keeps. These are the platform's own numbers, not a dojofood calculation.
A platform's row carries four things at once: open or closed, API settings, manage matching, and the switch itself. Opening a channel and entering its credentials finishes on that row.
The moment a channel opens, the row gains platform opening hours and platform payment methods. On a closed channel neither appears, because there is no cell to write to yet.
Phone order, take-away and dine-in carry their own switches on the strip at the foot of the card. The QR menu is there too, and its design opens on its own page.
Opening hours, order settings, checkout types and payment methods sit directly above the platform rows. The channel call is made on the same screen.
The search box at the top of the dialog matches branch names as well as channel names. In a ten-branch chain you land on the row you want without scrolling.
A branch header says how many channel overrides that product carries. The counter only counts prices that genuinely differ; a row repeating the standard is not an override.
A channel price is written over that branch's standard price rather than the catalog price. Change the branch price and every channel without an override moves with it.
In a chain, a channel gets discussed like a brand decision and then lives as a cell. Where one branch meets one platform there is a separate identity, a separate clock, a separate matching and a separate price. Press a cell in the diagram below and you see what that intersection carries.
LocalKadıköy branchModa6 of 8 channels taking ordersPhone order openTake-away openDine-in openBeşiktaş branchSinanpaşa4 of 8 channels taking ordersPhone order closedTake-away openDine-in openBostancı branchBağdat Avenue3 of 8 channels taking ordersPhone order closedTake-away openDine-in openOne card for every platform the branch has open:
One catalog underneath. The mix on top is each branch's own call; closing one intersection touches no other.
Kadıköy branch · Uber Eats · open.
You opened the second branch. The platform does not see one brand; it sees a separate store with its own id, its own panel, its own key. A system that holds one account per platform simply cannot connect the second branch.
Credentials are held per branch and per platform. One branch's key belongs to that branch and the next branch's to the next, and both run off the same catalog.
Every new branch means rewriting the same hundred and forty products, rebuilding the same option groups, redefining the same combos. It takes a day and somewhere in it a typo survives.
The catalog, products, option groups, combos and recipes are held at the business level. A new branch inherits all of it; the only work left is that branch's platform matching.
One platform will not put a driver in your second branch's area, or there is simply no demand there. Turning the channel off across the whole chain is not an option either; at the flagship it is the best-selling channel you have.
The channel call is made on the branch's card. You turn the switch off at that branch and the others keep running the same platform. Nothing in the catalog changes.
It is eight o'clock and one branch's kitchen is buried. Orders keep landing, times stretch, the rating slides. You cannot see a way out short of deleting the menu.
You turn off the Orders switch on that branch's platform card on Home. The store stops taking orders on that platform and at that branch alone, and you switch it back on when the rush passes.
Your driver is off and the platform has none free either. Close the store outright and you lose the take-away orders too.
Courier availability is a separate switch. You turn that off and the store stays open on the platform; the dining room and dine-in orders are untouched either way.
The dining room runs until midnight but for the last half hour the kitchen wants to serve tables only. Going into each platform's own panel to change hours is a separate errand for every branch.
Every branch defines opening hours day by day for every platform it runs. The room's clock and the platform's clock do not have to agree, and both are managed from one screen.
The same burger cannot carry the same price at both branches; the rent is different, the area is different, what the platform takes is different. Defining the product twice splits the catalog in half.
The product is one and the price runs on three levels: the catalog price, the branch standard, and where needed that branch's amount on that channel. A channel price is written as a number.
Three branches and five platforms is fifteen possibilities. Nobody quite knows who is open where, and one branch has spent weeks waiting for orders on a channel that was closed.
The branch rail carries a number beside every branch: how many of the eight channels are taking orders. You read the state of the estate without opening a list.
This is the thing that gets muddled most in a chain. Whether a channel is connected and whether it is taking orders at this moment are two separate decisions, and dojofood puts them on two separate screens.
The first switch is on the Branches and Channels screen and describes the setup: is this branch connected to this platform. The moment you open it the cell exists, and you enter the credentials, set the platform's opening hours, map the payment methods and attach the products. Close it and the cell stops; the settings are not deleted.
The second switch is on Home and describes the moment: is this branch taking orders on this platform right now. The card reads the state back from the platform itself; the Orders switch closes that branch's store there, and the Courier switch cuts only the delivery side. Beside them sit the average prep time and rating the platform keeps.
Keeping the two apart has a practical payoff: when the rush passes, all you do is switch one thing back on. You do not re-enter credentials, you do not rebuild the matching, you do not resend a menu. The setup stays where it is and only the open-or-closed state moves.
Everything complicated about the channel side of a chain comes down to one sentence: the platform knows you store by store, not as a single brand. dojofood holds it the same way.
A branch's record on a platform carries four things. Credentials: API key, secret key, supplier id and the store id the platform issued you. They belong to that branch and are not copied to another. Order ingestion: how the order arrives. Three platforms carry this setting, its default is polling, and without it ingestion never starts at that branch, which is why the setting lives on the channel's own row.
Platform opening hours: day by day, for that branch and that platform. Payment method mapping: the platform's tender types are mapped to that branch's payment methods, so at the end of the day it is clear which money came from where. That last one has a real limit: Trendyol Go does not support the mapping. dojofood does not hide it; it tells you when you press the button.
The fifth thing is product matching and it lives on its own screen. The platform's list is pulled from that branch's store and set beside your catalog product. The names need not be identical; once the link exists the order lands as your product regardless of what the platform calls it. The unmatched-platform filter shows at a glance where a new branch still has gaps.
The full mechanics of channel pricing are covered in catalog and menu management; what matters here is that the base is the branch standard rather than the catalog, and that a channel price is written as an absolute amount.
On the delivery side, what dojofood cannot do is as clear as what it can. Setting up a chain, you need both.
The channel switch · credentials · platform opening hours · payment method mapping · product, category, option and combo matching · the branch standard and the branch × channel price · order automation settings · opening and closing the store on a platform · courier availability.
Catalog · products · option groups · combos · recipes · stock items · menus and their schedules · roles · company details. A new branch inherits all of it and you do not edit these from the branch.
Pushing a menu from the catalog to a platform · switching a single platform item on or off from dojofood · a channel closing itself when stock runs out · a channel breakdown in end-of-day reports · a platform commission line and a profit-and-loss table · a percentage rule on channel prices.
Some of that is the platforms' own limit: menu push and closing a single item remotely are not writable, so dojofood does not promise them. What you can close is the store itself, and that genuinely works. A channel does not close itself when stock runs out; dojofood warns you and the call stays yours.
The channel-split end-of-day report and the commission line are missing on our side. Home carries one platform tile with an order count and it counts delivery only; do not read it as a profit-and-loss table. Which branch earns what is covered by restaurant analytics, and the total at the centre by multi-branch management.
Deciding channels per branch is not a feature on its own; it stands on the catalog, the order board and the branch model.
What operators ask about delivery channels across branches.
Yes. Which of the eight channels takes orders is written on each branch's own card. One branch can run a single platform while another runs three; both work off the same catalog.
Yes. Credentials are held per branch and per platform: API key, secret key, supplier id and the store id the platform gave you. On the platform's side a chain is a separate storefront at every branch.
No. The switch writes to that branch's record on that platform. Other branches keep running the same platform and the catalog does not move.
Yes. Price runs on three levels: the catalog price, the branch standard, then the branch-and-channel intersection. A channel price is an absolute amount, not a percentage added to a base.
Yes. Every branch defines opening hours day by day for every platform it runs. The dining room can stay open half an hour longer while the platform closes first.
Mostly yes. A platform's tender types are mapped to that branch's payment methods. Trendyol Go does not support this mapping and dojofood says so on screen rather than failing quietly.
Yes. Home shows a card for every platform the branch has open; the Orders switch stops the store on that platform alone. The dining room and the other platforms keep going.
Yes. The platform's product list is pulled from that branch's store and matched to your catalog. A product is written once; the matching is done per branch and per platform.
Uber Eats, Wolt, Bolt Food, Deliveroo and Just Eat in the global edition, and the Turkish set on the Türkiye site. If the platform you use is missing, say so when you book the demo; when a real operator needs it we put it in the plan.
No. Matching runs the other way: the platform's list comes into dojofood and you attach it to a catalog product. You cannot switch a single platform item on or off from dojofood; what you can close is the store itself.
No. Reports are per branch and carry no channel breakdown. Home has one platform tile that does show a split, and it counts delivery only. The full report family is on restaurant analytics.
Yes, per branch. With auto confirm on, an incoming order moves to preparing without waiting for an operator. A busy branch switches it on; a quiet one confirms by hand.
Partly. The catalog, products, combos and recipes are inherited ready-made. What belongs to the branch alone is its channel mix and each channel's credentials and matching.
Around 10 minutes to be usable, and every business gets a customer manager who walks you through the branch and channel setup. Platform account approvals run on the platforms' own timelines.
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.
