Does Just Eat tell you when your restaurant goes offline?
Restaurant operators on Just Eat are told what the platform concluded and not that it acted. Just Eat publishes the rule in a single sentence: “If you do miss the order and it is rejected, your restaurant will be taken offline under the assumption that you are closed or too busy to accept incoming orders.” That is an unusually frank explanation of the platform’s reasoning. What sits next to it is nothing. Just Eat’s published material describes no message, email or push that accompanies the moment a restaurant is taken off the app.
What does Just Eat publish about the moment it takes a restaurant offline?
The trigger and the reasoning, both in the same answer, and no delivery mechanism. On the trigger, an order left unanswered for five minutes “will be automatically rejected”. On what follows, the sentence quoted above. Source: partnerinfo.just-eat.co.uk.
Read that sentence for what it assumes rather than for what it does. Just Eat is describing an inference about the restaurant, and an inference is exactly the kind of conclusion a party would normally be given a chance to correct. Here it is acted on immediately and the restaurant is told nothing, so the platform holds a belief about the branch that the branch cannot see, cannot contest and will not learn about until a customer mentions it.
The absence of a message is also the absence of a reason code. Even after the fact, nothing published gives a partner a way to ask the platform why a particular restaurant was off between two particular times, which means the account cannot confirm the very thing Just Eat has already written down as its own reasoning.
Which Just Eat popups exist, and who reads them?
Two, and both belong to the person operating the toggle. Just Eat documents the control as “Toggle the ‘Taking orders’ slider to change your status”, with a confirmation popup reading “You went offline until tomorrow”, and the reverse action confirmed with a popup reading “You’re back online”. Source: partnerinfo.just-eat.co.uk.
Those are acknowledgements of an action rather than announcements of a state. They appear on the screen where the slider was moved, which is either Partner Hub on somebody’s browser or the Orderpad on the counter.
The gap that follows is specific and worth naming. Just Eat publishes popup text for the offline a person chooses, and publishes no popup text for the offline the platform applies after a missed order. We looked for one and did not find it, so the honest statement is that the published material does not describe a notice for the automatic case, not that no pixel ever appears anywhere.
The device is part of the story too. That five minute clock runs on the Orderpad sitting in the branch, which means the same conditions that stop it being answered, an exhausted battery, a lost network, a handset carried through to the pass, are also the conditions under which nobody was watching whatever the screen went on to display.
Why does overnight restoration remove the evidence of a Just Eat outage?
Because the state ends before anyone reviews it. The documented behaviour of the short offline is written as a bracketed note: “(Please note, this feature automatically puts you back online the next day.)”
Automatic restoration is a genuine protection and a genuine problem for evidence. A restaurant taken offline at twenty past seven on a Friday is back on the app by Saturday morning, so the Partner Hub a manager opens over the weekend shows a restaurant that is online and has always been online as far as the current view is concerned.
What remains is a quiet Friday evening, which is the single easiest thing in hospitality to attribute to weather, a match, a slow week or a competitor’s promotion. Nobody investigates a problem that has already fixed itself, and the platform’s kindest feature is therefore also the reason these events repeat unchallenged for months.
The consequence for a chain is that the argument has to be built from outside data or not at all. There is no internal artefact to produce in a conversation with an account manager.
Does Just Eat tell a partner in advance how long a compliance outage will run?
Yes, and it is one of the few places any platform in this set publishes an expected duration. On food hygiene, a partner holding the lowest inspection score is “no longer allowed to trade on Just Eat” until that score improves. Reinstatement follows a fresh inspection, and Just Eat warns about the publication lag behind it, noting that “it can take up to 28 days for your new rating to appear on the websites”. Source: partnerinfo.just-eat.co.uk.
Twenty eight days on top of an inspection cycle is a planning horizon rather than an incident, and publishing it in advance is genuinely useful. Notice, though, what kind of telling that is. It is a rule written down once, in an article, for anybody who goes looking. It is not a message about a particular restaurant on a particular day, and the partner still has to work out for themselves that the rule is now describing them.
That distinction runs through everything on this page. Just Eat is unusually open about its policies and entirely silent about its actions. A brand can read exactly what would cause a restaurant to be removed and cannot find out that one has been.
Which Just Eat change has to go through support rather than a setting?
A longer closure. Going offline beyond the automatic overnight restoration is not self service, and Just Eat routes it through a ticket: “Select ‘Extend Temp Offline’ as the topic and send us a message.” A refit, a holiday closure or a kitchen rebuild therefore starts with a conversation rather than with a control.
That is worth knowing because it inverts the usual expectation about who initiates. On the short outage the platform acts and says nothing. On the long one the restaurant has to ask and wait.
There is a third case that produces the same customer complaint and generates no notice through either route, because no state is entered at all. A restaurant can be configured so that one fulfilment type is unavailable while the other trades normally, which reads to a customer as a closed restaurant and to the branch as an ordinary evening. How that arises across an estate is covered on our page about branches offline on Just Eat while the rest are fine.
What does a Just Eat brand write down before the Orderpad is answered?
The interval, because it is the only thing that will still exist tomorrow. When did the listing stop being orderable, when did it come back, and did that sit inside the hours the restaurant published for that day. Three facts, recorded from the customer side, survive the overnight restoration that erases everything else.
Repetition is what turns those intervals into an argument worth having. Three quiet Fridays in a row at one site, each starting around the same hour, describes a rota or a piece of hardware rather than coincidence, and it becomes fixable the moment somebody can see the shape. Reading the storefront the way a guest does, and keeping what that produces, is what Kitchain (kitchain.co) does on Just Eat listings.
One last note for groups trading under more than one brand of the same parent. The rules quoted above are published on the United Kingdom partner site, and the sibling national sites of this group do not all publish the same set, so a policy that is documented in one country may be undocumented rather than absent in another.