Why does my Deliveroo site status say closed when I am open?

Deliveroo separates two things most platforms merge, and restaurant chains lose orders in the gap between them. “Site Status” carries OPEN, CLOSED and READY_TO_OPEN, while kitchen load is a second, independent axis of QUIET, BUSY and MODERATE. Being busy keeps a site selling here. Being closed does not, and two of the mechanisms that close a site cannot be reversed from Partner Hub at all: a “Forced Closure”, which only Deliveroo can lift, and automatic closure after three rejected orders inside fifteen minutes. Neither announces itself to the operator.

Deliveroo listings in the UAE were offline for 2.28 percent of stated trading hours in July 2026, average interruption 3 hours 10 minutes. In Kuwait the figure was 0.55 percent and 2 hours 03 minutes. Both are measured against the hours each site told Deliveroo it would trade.

What does a Deliveroo Forced Closure mean and who can lift it?

A Forced Closure is a closure applied by Deliveroo that the restaurant is structurally unable to reverse. Deliveroo announced it in the Partner API changelog in these words: “Deliveroo introduced an additional tool, called Forced Closure, to support Partners in reducing the risk of appearing open for orders during periods when they are actually closed. This new tool can only be enacted by Deliveroo.” Source: api-docs.deliveroo.com.

The same changelog spells out the route back: “if Partners wish to open their restaurant when a Forced Closure is active, they will need to contact Deliveroo by calling our Partner Support team. As only Deliveroo can open a site during an active Forced Closure, the Partner will not be able to open the site from their side.” An integration that tries anyway gets an HTTP 400 and the message “This closed period can only be updated by Deliveroo.”

For a chain this changes where the fix lives. The state is legible to an integration, which receives a named reason for the closed period rather than a blank, so a team reading the API can at least say what happened. A team working only in Partner Hub sees a site that will not open and no explanation of why the button does nothing. The elapsed time is then set by a phone call to Partner Support, not by anything happening in the restaurant.

Does Deliveroo close a site automatically after rejected orders?

Yes, and Deliveroo is one of very few platforms that publishes the rule. Among the conditions its Site API documents as blocking a reopen, one describes the closure as automatic and gives the trigger: “When the restaurant was closed because they experienced three auto-rejections within 15 consecutive minutes”. The site comes back as CLOSED_PERIOD, the same code used for a day off the partner set deliberately. Source: api-docs.deliveroo.com/docs/site.

Three rejections inside fifteen minutes is a low bar during a rush. It is also reachable without anyone rejecting anything on purpose, because an order that is never accepted becomes an auto rejection. A tablet that lost its connection, a tablet somebody carried into the back, a shift change that left nobody watching the screen, all of these produce the same three events, and the site closes.

The wording matters for how the closure then reads in reporting. It is not filed as an incident, an outage or a fault. It is filed as a closed period, indistinguishable in code from a scheduled day off, which is precisely why it so often survives to the end of a service before anyone notices it happened.

What happens if nobody answers the Deliveroo Open Reminder?

The site stays closed. Deliveroo’s help centre describes the mechanism: “Open Reminder pops up with sound alerts 30 minutes before your restaurant’s scheduled opening time” and “The alert will keep sounding every 10 minutes until it is acknowledged. This check-in is required at the start of every shift.” The article then asks and answers the 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”. Source: help.deliveroo.com.

Automatic opening exists, but it is not the default and not universal. Deliveroo describes it as a feature you have to qualify for and request: “Auto-open opens your site on the Deliveroo app the moment your scheduled opening time begins, so no one has to remember to do it manually”, with the entry condition stated as “At least 95% availability to request Auto-open” and the process being to submit a request in Partner Hub. Source: help.deliveroo.com. A scheduled day off cancels it in any case, which Deliveroo states in a different article: “When you have a Day Off scheduled, your business won’t auto-open on the app.” Source: help.deliveroo.com.

This is the sentence to take away for a multi site brand. Two branches of the same chain, with identical schedules, can behave differently on Deliveroo, because one has Auto-open enabled and the other is still waiting for a human to acknowledge a reminder every single shift.

What is the difference between Site Status and busy mode on Deliveroo?

Site Status and busy mode are separate fields with separate values on Deliveroo, and confusing them costs orders in both directions. Site status is documented in the OpenAPI schema as "status": {"type":"string","enum":["OPEN","CLOSED","READY_TO_OPEN"]}, with the note that “When opening a site outside of its opening hours, its status will be set to READY_TO_OPEN“. Source: api-docs.deliveroo.com.

Kitchen load lives in a different object, which the documentation labels “Workload (Busy Mode)”, with the values QUIET, BUSY and MODERATE. Busy mode does not take the site off the app. Deliveroo says so plainly: “When ‘Busy mode’ is switched on, we won’t send any new orders to you without giving you at least the minimum time you have asked for.” It does have a visibility cost, which Deliveroo also states: “Switching on ‘Busy mode’ may also move you down the restaurant list on the app, because your orders will take longer to reach customers.” Source: help.deliveroo.com.

Bulk closure is a third thing again. Partner Hub carries a “Site Status” tab described as a tool that “lets you open or close multiple sites in bulk, fast”, with buttons labelled “Open selected sites” and “Close selected sites”, available to users holding the Admin, Admin (limited), Manager or Manager (limited) role. Two warnings from the same article are worth repeating. Closing a site also kills pre orders: “If a site is closed, no scheduled orders can be placed until the site re-opens again.” And the tablet stays an independent switch, since “a store can still be manually opened or closed using the Deliveroo tablet”. Source: help.deliveroo.com.

How often are Deliveroo sites offline in the UAE and Kuwait?

The two figures given above, 2.28 percent and a mean of 3 hours 10 minutes, place Deliveroo in the middle of the UAE field, worse than Talabat, Keeta and noon Food and better than Careem Food. The Kuwait pair is quieter on both counts, and the same brand can sit in both distributions at once.

The mean length is the number worth staring at. Three hours is not the shape of a mistake somebody caught. It is the shape of a mechanism nobody was watching: a Forced Closure waiting on a support call, three auto rejections during a rush, or a reminder that nobody acknowledged at the start of a shift. All three of those close a site quietly and none of them ends on a timer, which is why the cost of a Deliveroo closure is set by how long it takes an operator to notice. Kitchain (kitchain.co) puts a number on that interval by asking each site the question a customer asks, against the hours that site itself published.

Worth knowing before you go looking for an app to install: Deliveroo publishes no merchant application in either app store, and the mobile route into Partner Hub is an installable web app rather than a native one. Our page on the platform itself is at kitchain.co/aggregators/deliveroo/.