How to get Glovo to put your restaurant back online
Restaurant operators on Glovo are in the comfortable position of working with a platform that writes the return into the closure. A store set to busy reopens after thirty minutes without anybody touching it. A store closed for the day comes back at the next scheduled opening. A closure sent through the partner API carries a mandatory end timestamp. The single state with no return attached is the one nobody chose, which is the scheduled opening that was never confirmed, and Glovo describes the recovery for it as a manual status change.
Every Glovo closure you set yourself already has a return built into it
Glovo says so option by option rather than leaving it to a help article, and in both cases the sentence ends on the return rather than on the choice. For a day closure the guidance finishes on it: “When you choose ‘Close for the day’, choose an accurate reason (7). Pick the accurate reason, and then click ‘Update’. Your store will remain closed until your next opening time is set.” Source: sell.glovoapp.com. For the short one it is a timer: “If you select ‘Busy for 30 minutes’, it will close your store for 30 minutes and automatically reopen after 30 minutes.” Source: sell.glovoapp.com.
Both of those are genuine returns performed by the platform, which puts Glovo ahead of Bolt Food, Keeta and Ninja, where at least one state waits indefinitely for a person. It also means a Glovo store that is still unorderable past its own stated return is an anomaly worth investigating rather than a forgotten switch.
Glovo also protects work already in the kitchen when either option is used, stating in a note attached to both: “When choosing any of these options, your already accepted orders won’t be cancelled to ensure the best customer experience.” So the decision to close costs future orders and not the ones on the pass, which is worth knowing for anyone hesitating during a rush.
The exact taps that end a Glovo busy state early
Three, and they are not the ones an operator guesses. Glovo publishes the sequence: “Click the ‘Busy’ icon (4). ‘Change Vendor Status’ (5). Then click ‘Open’ (6).” The store status icon is the entry point in both directions, and the same route works for a closed day: “If you decide to reopen your store earlier, you can click the store status icon again and then click ‘Open’.”
Three steps sounds trivial and is not, because they have to happen at the busiest point of a shift on a device that is being used for orders. That is the mechanism by which a thirty minute pause quietly becomes the full thirty minutes every single time it is used, and over a month of Friday services those half hours add up to a shift.
One caution before a group writes that sequence into a manual. The button names above come from Glovo’s restaurant order taking application, and its grocery and retail application labels the same controls slightly differently, so a procedure copied from the wrong guide sends a branch hunting for a control that is not on their screen. Which application a site runs is not uniform across an estate, and confirming it costs one question per branch and saves the confusion at the moment it is most expensive.
The one Glovo state with no return is the opening nobody confirmed
Opening is a confirmation on Glovo, not an automatic event. A reminder reaches the store device shortly before each scheduled opening hour, it can be deferred, and the storefront starts trading only once somebody answers it. The mechanism itself, with Glovo’s wording for both buttons, is set out on why a Glovo store shows as closed when the restaurant is open. What concerns a return to trading is the state this leaves behind, and the state is peculiar. Nothing was closed, so there is nothing to reopen, and the usual recovery question of what to switch off does not apply.
The recovery is stated as a workaround and contains the whole failure: “If you don’t check in at the designated time, you can manually change the status by clicking the store status button at the top left corner.” A store that was never confirmed open is not closed by any decision, has no closure record and no reason code, and looks correct in the Manager Portal, where the schedule still says the store opens at eleven.
This is the Glovo failure that costs the most and shows the least. Nothing expires, because nothing was ever set. The only route back is a person opening the application and pressing open, and the only way to notice it is to check whether the store could be ordered from at the hour it published.
How an integration removes a Glovo closure, and what happens next
Cleanly, and with a documented consequence. Glovo’s public partner API exposes one resource for switching a store off, at /webhook/stores/{storeId}/closing, and the operation that matters for recovery is the one that deletes an existing closure. The specification states plainly what the store does afterwards: “After the removal, the store will continue following their regular schedule.” Source: api-docs.glovoapp.com.
Read that sentence carefully before building anything on top of it, because it is the whole recovery contract. Removal returns a store to its schedule, it does not force the store open. A removal performed outside trading hours therefore produces no visible change at all, and a team testing recovery tooling at nine in the evening will conclude the call failed when it worked exactly as documented. Test inside opening hours, or read the store’s own timetable before deciding anything went wrong.
One warning for a team integrating several platforms at once. Glovo’s public specification does not publish store status enum values, and status vocabulary from other vendors does not appear in it. Do not carry a status name across from another platform’s documentation and expect Glovo to accept it.
What do Glovo’s partner terms say about a restriction Glovo applied?
They reserve the power broadly and attach a notice period only to the final step. The partner terms allow Glovo to restrict, suspend or delete a partner’s products, services or profile at any time and for an indefinite period, and undertake to communicate the decision fifteen days before a profile is finally deleted, with an explanation. Source: Glovo partner terms. The clause is quoted in full on does Glovo tell you when your restaurant goes offline.
Read the two halves separately, because they are not the same promise. Fifteen days of notice and an explanation apply to deletion of the profile. A restriction or suspension short of that carries no published notice period, no stated route of appeal and no response time, and we did not find one anywhere in Glovo’s published material. A brand in that position is relying on its commercial contact rather than on a documented process.
Where does a closed Glovo store cost money beyond the lost orders?
In cancellation charges, because Glovo names the exact situation this page is about. Among the reasons an order cancellation is treated as attributable to the partner, the terms list the case where “his store is closed during the specified working hours”. So the delay between a closure starting and somebody ending it is not only unsold covers, it is exposure to a charge, and the amounts sit inside each national version of that agreement rather than in one global figure.
That changes what the check in failure is worth. A store that never opened at eleven is not merely missing a morning of orders, it is exposed to charges on anything that arrived against a schedule saying it was trading. The way to keep that exposure at zero is to make the confirmation reliable and to detect the mornings it did not happen, which means recording whether each store was actually orderable at its own published opening time rather than reading a status afterwards. That is the record Kitchain (kitchain.co) keeps on Glovo stores from the customer side.