Scheduled hours and actual availability are different numbers

Scheduled hours are what a restaurant told a delivery platform it would trade, while actual availability is the share of those hours in which a customer could really place an order, and restaurant chains report the first as though it were the second. The two are not close. Careem will not let an outlet change status outside its operating hours at all. Deliveroo returns an error if you try to open a site outside its schedule. And a schedule nobody maintains quietly redefines every availability number built on top of it.

What are scheduled hours on a delivery platform, and where do they live?

In a different place on every app, under a different name, and often in more than one place on the same app. Deliveroo keeps opening hours in Partner Hub, with “Days Off” and “Special Opening Hours” as separate one off overrides. Careem calls them Ops Hours and separates them from the live status, telling operators in the Outlet Management panel that “Here you can preview and manage the current outlet operational status. You are not impacting weekly operational hours.” Snoonu splits them across three tabs, “Main Hours”, “Special Hours” and “Ramadan & Eid Timings”. Jahez runs “Business Hours”, “Today’s Working Hours”, “Ramadan Hours” and “Bulk working hours”.

noon Food removed the separate schedule tab entirely, stating that “The independent, shared Schedule tab used for all the use-cases is discarded” and that the schedule now lives “in the outlet editor itself for a given outlet”. It also refuses an incomplete answer: “Users must either close the outlet for the day or select a schedule, they cannot mark an outlet as open but not select a time. In this case, they will get an error message.”

The important property of all of these is the same. A schedule is a declaration made by the operator. It is an intention, not an observation, and nothing about publishing it makes it true.

Why does a listing fail to open at its scheduled time?

Because on several platforms opening is an event that somebody has to cause, and the schedule alone does not cause it. Deliveroo is explicit that automatic opening is an opt in privilege rather than a default. Auto-open “opens your site on the Deliveroo app the moment your scheduled opening time begins”, but it has to be requested, and the published condition is “At least 95% availability to request Auto-open”.

Without it, Deliveroo runs a check in. Open Reminder “pops up with sound alerts 30 minutes before your restaurant’s scheduled opening time”, “will keep sounding every 10 minutes until it is acknowledged”, and the article answers its own question directly: “Can I ignore the Open Reminder notification? No. If you don’t respond, your business will stay closed on the app until someone confirms you’re ready to open.” The two buttons are “Ready to open at your scheduled time” and “Remain Closed”. Deliveroo adds that a scheduled Day Off cancels auto-open as well.

Talabat and HungerStation run the same idea under the same name and with the same window. Both state that check in lets a partner “confirm the upcoming opening of your shop up to 30 minutes before its scheduled opening hours”, and that “If the partner fails to acknowledge, the shop will remain closed even if it is scheduled to be open”. Both also state that the feature is off by default and is switched on by an account manager, which is why one chain has never heard of it while another loses mornings to it.

This is a distinct category of failure and worth counting separately from an interruption. In July 2026 our UAE panel recorded 3,759 failures to open, of which 2,906 did not come online within the check window and 853 opened late. The Kuwait panel recorded 124.

Why can a branch not simply open outside its schedule?

Because two of these platforms refuse the command. Careem’s portal carries the message “Outlet status change is not allowed outside operating hours”, so a branch standing ready to trade at an hour its Ops Hours do not cover cannot switch itself on. The fix is to edit the hours, and Careem’s own FAQ quotes “Operational hours = 24 hours” as the turnaround for that. Deliveroo says the same thing to machines: “Please note that it is not allowed to open a site outside of its opening hours, the call will return 400 (bad request) error.” Talabat documents OPEN as working only “if it’s within opening hours according to schedule”.

That inverts the usual assumption about which number is authoritative. On those platforms the schedule is not a description of trading, it is the boundary of what trading is permitted, and a stale schedule is a hard constraint rather than a piece of untidy data.

Snoonu goes further and attaches a penalty to an unconfirmed schedule. Its portal warns: “Please confirm the special hours for this store by reviewing and re-saving them. Failure to do so will result in an indefinite closure.” It also enforces a floor, refusing a schedule with “Operating hours can not be less than {{hrs}} hours”, and spends several strings pushing partners to keep hours current, including “Keep your branches running, update their hours to avoid closures.”

Which hours are separate from the ones you thought you set?

More than most operators expect, and each of them produces a customer complaint that looks like an outage. Just Eat keeps collection and delivery hours independent and warns that “If you update your collection hours, this will NOT also update your delivery hours”, so a branch fixed in one place is orderable through one channel and absent from the other. Uber Eats attaches hours to the menu as well as the store, returning OUT_OF_MENU_HOURS, documented as “Restaurant is outside of business hours”, which is a configuration fault that repeats at the same time every day until the menu is edited.

Jahez runs a separate cutoff for scheduled orders, described as the “Maximum hours before close time for same-day scheduling (e.g., if set to 3 hours, no orders can be scheduled within 3 hours of closing)”. Deliveroo notes that a closed site stops pre orders too: “If a site is closed, no scheduled orders can be placed until the site re-opens again.” None of these is the store’s main schedule, and all of them can make a branch unreachable while the main schedule says open.

What does a wrong schedule do to every number built on it?

It redefines them, silently and in both directions. Availability is a ratio, and the schedule is its denominator. A location whose schedule claims 24 hours accrues measured downtime for every hour it was dark, including the hours it never meant to trade, and its availability figure will look terrible for reasons that have nothing to do with operations. A location whose schedule is narrower than its real opening hours shows a clean record while turning customers away in the uncounted hours.

That is not a flaw in the measurement, it is the measurement doing exactly what it says. Downtime is counted only inside stated trading hours, which is why 64 percent of unexpected interruptions in our July 2026 UAE panel began between 22:00 and 04:00: those hours sit inside the stated windows of stores that trade past midnight, and hours outside a stated window are not counted at all. The full definition, including how overnight windows are handled, is at our methodology.

The practical consequence for a chain is that a schedule audit has to come before an availability target. Setting a branch a 99 percent availability goal while its schedule says it trades around the clock is setting it a goal about paperwork.

How large is the gap in practice?

Large enough to change decisions. Across our UAE panel in July 2026, listings were unavailable for 1.68 percent of their own stated trading hours, which came to an average of 9.5 hours of lost trading time per listing over the month. Per platform the figure ran from 0.74 percent on noon Food to 2.94 percent on Careem Food. In Kuwait the panel figure was 0.54 percent, and in Saudi Arabia 2.88 percent across the whole panel and 0.77 percent among listings that were actually trading.

Every one of those numbers is a comparison between two things a restaurant already owns: the hours it declared and the hours it delivered. Because no merchant dashboard reports the second against the first, that comparison is what Kitchain (kitchain.co) produces from the customer side. When a branch turns out to have been dark inside its own window, the next question is who caused it, and the tells for that are at paused by the branch or closed by the platform.