What a franchisee can change on a delivery app without telling head office
Delivery platform accounts are held by whoever operates the site, so restaurant chains that franchise are handing over a set of switches rather than a set of screens. The powers a branch level login carries are wider than most brand teams assume and quieter than any of them expect. A franchisee can take the store off the app, rewrite the trading hours everything else is measured against, remove dishes from sale, change how long the kitchen claims to need, and reissue the credential that keeps the integration alive. None of those actions notifies the brand.
Why does the franchisee hold these switches in the first place?
Because the platform’s relationship is with the operator of the location, and the tools are built for the person standing in the kitchen. Every portal in this category is organised around a branch, and the roles inside it are operational rather than corporate. Deliveroo states which of them reach the closure controls, confirming that “Hub users with the Admin, Admin (limited), Manager, or Manager (limited) role can access the Site Status feature” from the Settings page in Hub. Manager is a shift level role.
There is usually a second channel as well, and it does not care about roles at all. Deliveroo confirms that alongside the Hub, “a store can still be manually opened or closed using the Deliveroo tablet”. Talabat says the same of its own hardware, telling partners that “Using our tablet, you can pause your store from collecting orders for a specific time period.” A tablet on a counter is a switch available to anybody who can reach it, and no permission model applies to a person tapping it.
What can a franchisee do to the storefront itself?
Take it off sale, in a single action, with a duration attached. Snoonu’s portal offers “Pause Orders” on a branch card under the prompt “How long until you can start accepting orders again?”, and a bulk mode labelled “Mark branches busy” with checkboxes and “Select All” that pauses several branches in one request. Jahez offers “Set As Busy” with a “Set Duration” field, and a separate “Re-Set As Busy” for repeating it. Careem’s portal exposes “Active” and “Offline”, the second also shown as “Temporarily Offline” with “Back online on {{ time }}”, and it requires a reason to be selected, prompting “Select reason for taking outlet {{ selectedStatus }}”.
That reason field is worth noticing, because it is the only place in this list where the platform captures an explanation. It is captured for the platform, not for the brand. A franchisee who pauses a branch has told Careem why, and has told head office nothing, and the two facts sit in the same system.
Which schedule changes are the most consequential and the least visible?
Trading hours, by a wide margin, because every other number is measured against them. Jahez gives a branch “Set Business Hours for Your Branch”, a “Bulk working hours” tool for doing it across branches at once, and a separate “Ramadan Hours” object. Snoonu splits the same thing into tabs labelled “Main Hours”, “Ramadan & Eid Timings” and “Special Hours”, and describes the last as a way to “Add special hours or closures for holidays, special events, or other exceptional events. This will temporarily replace your main hours.” Careem has “Edit Ops Hours” under “Operational hours settings”.
Narrowing the declared hours is the single most effective way for a branch to make an availability problem disappear from every report anyone runs. Downtime is measured inside declared hours on any sane basis, our own included, so a site that trims two difficult evening hours out of its schedule stops accruing downtime in them and starts turning customers away instead. The record improves and the trading falls, and only the second of those is visible in the brand’s numbers, months later.
What can a franchisee remove from sale without removing the branch?
Individual dishes, with the same effect on a customer and none of the visibility of a closure. Careem’s item level control is a snooze, and its dialogue asks “When should we make this item available again?” with options including “Unavailable until Tomorrow”, “Next Business Day” and “After specific time”, capped by the note “Maximum value is 24 hours”. Snoonu’s equivalent marks an item “Out of Stock” with durations “For the next 2 hours”, “Until Tomorrow”, “Indefinitely” and “Until manually reactivated”, and warns that “Stockouts can only be reported once per item. Please verify before confirming.”
An indefinite stockout on a signature item is a permanent menu change made by a shift manager. The branch is open, the rating is unaffected, the availability record is clean, and the dish that the brand’s advertising is built on cannot be ordered at that location. Careem’s own portal counts these for the operator under “Unavailable Items ({{count}})” and describes them exactly as they are, “Items that customer cannot order”, which is a better summary than most brands have of the same problem.
What can a franchisee change that breaks the integration outright?
Credentials, and the platform warns about it at the moment of the click. Jahez’s partner credentials screen confirms that “Generating a new key will deactivate the previous one and may affect active integrations.” A franchisee troubleshooting a connection by reissuing a key has terminated the working connection rather than repaired it, and the failure surfaces as orders that stop arriving in the point of sale.
The order channel can be split without any change of settings at all. Deliverect’s guidance for Jahez describes what happens when both channels stay live: an order failure occurs “when an order was already accepted on the Jahez tablet or dashboard instead of through Deliverect”, and the recommended remedy is to “stop accepting orders on the Jahez tablet or dashboard” once integrated. Whether the tablet is used is a habit rather than a setting, so it is entirely within a branch’s discretion and entirely outside the brand’s view.
What can a franchisee change that quietly costs the brand its ratings?
Preparation times, and at least one platform says so on screen. Snoonu warns a branch at the moment it pads its own estimate that “Putting higher than preset delivery times may result in ratings lower than 3.5!” Padding is a rational local decision under pressure and a poor brand level one, and it is taken by the person under the pressure.
Scheduled orders are a second example of the same shape. Snoonu exposes them per branch with “Control Scheduled Orders by Branch”, an invitation to “Quickly see which branches aren’t accepting scheduled orders”, and a counter reading “{{enabled}}/{{total}} branches”. A branch that turns the feature off has removed a whole ordering mode for its catchment, the storefront stays live, and the loss looks like softer demand.
What is genuinely outside a franchisee’s control, and why does that matter?
A short list, and knowing it prevents the wrong escalation. Careem blocks status changes outside the schedule, stating that “Outlet status change is not allowed outside operating hours”, and its “Outlet Closed” state carries the instruction “To reactivate your outlet, please reach out to Careem”. Deliveroo’s Forced Closure “can only be enacted by Deliveroo” and a partner attempting to lift one is told “This closed period can only be updated by Deliveroo.” On Jahez, visibility is a separate axis and the documented remedy for a hidden store is to “Ask Jahez to set your store’s visibility status back to “Visible.””
So the powers a franchisee holds are precisely the reversible, undocumented, silent ones, and the powers the platform holds are the loud ones that generate a support conversation. That asymmetry is the argument for measuring branch behaviour from the customer side rather than asking for it, which is the position Kitchain (kitchain.co) takes across a franchised estate. What the brand can and cannot see through the platform’s own tools is set out at franchise delivery monitoring.