Does Glovo tell you when your restaurant goes offline?
Restaurant chains on Glovo do have a written notice period, and it is attached to the wrong event. The partner terms let Glovo restrict, suspend or delete a listing “at any time and for an indefinite period”, then undertake to communicate a decision “fifteen (15) days prior to the final deletion of its profile”. Fifteen days before permanent removal, and nothing stated before a restriction that empties a storefront tomorrow. Every other message Glovo publishes concerns the ten minutes before a shift starts.
Which notice period does Glovo commit to in writing, and what does it cover?
Deletion, and deletion alone. The clause bundles three powers together, restriction, suspension and removal, then attaches an undertaking to the last of them, promising communication in advance “together with an explanation of the facts and circumstances that justify it”. Source: glovoapp.com partner terms.
Committing to an explanation as well as a deadline is rare in this category, and it deserves credit before the caveat. Very few platform contracts in this space bind themselves to say why.
The caveat is scope. Restriction and suspension sit in the same sentence, are available immediately and for an unbounded period, and carry no stated warning. A brand whose listing is restricted on a Thursday morning finds out the way any other brand does, which is by noticing. The undertaking only starts running once the platform has decided to remove the profile permanently, and by then the trading loss has already happened.
One reading note. This document is published in national variants, so an operator should open the one covering the country their branches trade in rather than whichever loads by default.
What is the one Glovo prompt that repeats until somebody answers it?
The opening check in, which belongs to the start of a shift rather than to an interruption during one. Glovo describes it plainly, saying that “10 minutes before each scheduled opening hour, you will see a reminder to open your store”. Source: sell.glovoapp.com.
The prompt does not give up easily. Choosing to defer schedules another ask a few minutes later, the guidance stating that “‘Later’ (2) is you will be asked 3 minutes later if you are ready to open”, and it returns if the application is closed and reopened. Keep deferring and, in Glovo’s own words, “you will get a notification every 3 minutes”.
Three minutes is the tightest repeat published by any platform in this set. Deliveroo’s equivalent reminder repeats every ten. So Glovo has built persistence into its merchant tooling, and it has aimed that persistence at one predictable moment in the day rather than at the unpredictable ones.
Can a Glovo reminder be postponed forever without anyone else finding out?
Yes, because deferral has no floor. Each repetition offers the same choice, and a member of staff who keeps deferring is producing an unopened storefront plus a local notification loop that never leaves the device it is running on.
Glovo then describes the recovery in language written as assistance, telling a merchant that “you can manually change the status by clicking the store status button at the top left corner”. The sentence assumes somebody has realised the shift began without the store opening. If nobody has, the storefront was simply never switched on.
That produces the emptiest failure in this whole category. No closure exists to be examined, no reason was recorded against anything, and the hours configured centrally continue to describe a store that should have been trading since eleven. There is nothing on the platform to find later, which is a different problem from a record that is hard to reach.
Does Glovo charge a restaurant for a closure it never announced?
The terms treat the symptom as the partner’s responsibility. Among the circumstances in which a cancelled order counts against the restaurant, the document names the case where “his store is closed during the specified working hours”, with the charges themselves set inside each country’s version of the agreement.
Now hold that next to the previous section. A storefront that nobody opened is a store closed during its own specified working hours. Nothing told head office, and cancellations arising from it are chargeable under a rule the brand agreed to.
Most platforms in this set leave an unnoticed outage as revenue that did not arrive. Glovo has written a clause under which the same silence can also generate a cost, which raises the value of finding out quickly rather than eventually and makes the fifteen day undertaking above look narrower still.
Which Glovo closures carry an end time, and who is told when it passes?
All of the self service ones, and no one. The thirty minute busy state is described as closing the storefront and bringing it back on a timer, the guidance stating that Glovo will “automatically reopen after 30 minutes”. Source: sell.glovoapp.com. Closing for a day hands the ending to the schedule instead, with the store remaining closed until the next configured opening.
The integration behaves the same way. Glovo’s public partner specification exposes one closing resource, whose write operation is described as the way to “close a store temporarily until a specified date and time in the future”, with removal returning the store to its normal timetable. Source: api-docs.glovoapp.com.
Because a future timestamp is a required part of that request, a Glovo store cannot be left switched off forever by an integration that forgot to finish the job. That is a genuine safeguard and it is not a notification. Both ends of the interval happen on their own, and no message marks either of them.
What evidence is left behind by a Glovo outage nobody was told about?
Almost none, and that is the part worth planning around. Every message described above travels to a device inside one store, is answered or dismissed there, and leaves nothing behind that a head office can read afterwards. The platform holds a status, which is a present tense fact, and the status of a store that has since been opened by hand looks exactly like the status of a store that opened on time.
So a brand asking on Monday how many of its Glovo listings were trading at eleven on Saturday has no source that can answer, and the people who could answer were the ones too busy to notice at the time. Anything that is going to be measured here has to be recorded while it is happening, from outside the store, because no party to the event is keeping a record of it.
That check does not depend on which application a branch runs or on any message reaching anyone. One measurement covers all three of the Glovo states above, because a busy period that ran past its half hour, a day closure chosen during evening service and an opening that never happened are indistinguishable to a customer and identical in shape once timed: a stretch of published trading hours in which no order could be placed. Kitchain (kitchain.co) keeps that interval for Glovo listings, and in the third case it is the only evidence that will ever exist, because nothing on the platform recorded the morning that never started.
One further reason to keep that record rather than rely on memory. Because the chargeable clause above turns on whether a store was shut inside its stated working hours, the useful artefact is not a screenshot of a status but a comparison between availability and published hours, held over time, per branch.