How to get Bolt Food to put your restaurant back online
Restaurant operators asking how to get Bolt Food to put a store back online are addressing the wrong party, because on this platform the only documented actor is the branch itself. Bolt’s own training material describes one control, a “Go online” and “Go offline” button that sets the restaurant “to active or inactive, depending on your needs”. The route back is that button, pressed on the device in the branch. Busy mode expires on a timer. An offline store does not, and Bolt publishes no platform side closure that a partner could ask anyone to reverse.
Who is allowed to end a Bolt Food offline state?
Whoever is holding the restaurant device, and nobody else that Bolt names. The training guideline sets the sequence out in a section headed “Pausing new orders”, instructing the user to open the main menu and “Click the ‘Go offline’ button”, then describing the result: “At the top of your screen, a red bar will appear saying, “You’re offline”. Clients can’t order from your restaurant until you resume accepting orders. To do so, click the ‘Go online’ button.” Source: Bolt restaurant app training guideline.
There is no approval step in that sentence, no reason code to submit and no waiting period. That is a genuine advantage over platforms where a state has to be lifted by the operator’s account manager, and it is also the whole exposure. Recovery time on Bolt Food equals the time it takes for a person who can reach the device to learn that the store is off. Head office cannot shorten it from a desk, because no published Bolt surface holds a remote reopen.
Which Bolt Food states come back without anyone pressing anything?
One, and it is not the one that usually causes the loss. Busy mode has a published duration list and a published automatic return: “You can activate busy mode for 15, 30 and 45 minutes. Then we will bring you back online automatically when this time has passed.” Busy mode also does not stop orders, since Bolt describes it as changing cooking time, saying that “your cooking time will be automatically changed to the selected amount of time” and that Bolt will “notify customers about longer expectation of their orders”.
Individual dishes get a return as well, on a clock of their own. A dish marked sold out for the day comes back early the next morning without anyone acting, an indefinite stock out waits for a person, and the timings are quoted in full on why a Bolt Food store shows as offline while the restaurant is open.
Line the three up and the ranking is odd. The shortest state returns fastest, the dish returns overnight, and the store, which is the only one of the three that stops all trading, is the one Bolt leaves alone. Recovery effort on this platform should be pointed at the layer with the least automation, which is the opposite of where most runbooks put it.
What do you actually check before deciding a Bolt Food store is stuck?
Two layers, in this order, because they are configured in different places and only one of them is visible on the tablet. The live toggle is on the restaurant device. The schedule is in the merchant portal, where Bolt instructs that opening hours “should reflect your kitchen schedule” and holiday closures are entered separately against each store. Source: Bolt Food Merchant Portal and Menu Editor Guide. How that goes wrong across an estate is its own subject.
A store that will not accept a “Go online” press during hours it believes are closed is a schedule problem wearing the costume of a status problem. A holiday closure entered in advance and then forgotten is the same fault with a date on it. Both are fixed in the portal at foodpartner.bolt.eu rather than on the device, which is why the reopen attempt made in the branch fails and gets reported upward as a Bolt outage.
The third thing to check is the menu, because a rejection can silently edit it. Bolt describes a rejection prompt that asks for a reason and adds: “If you mark the reason as Out of stock items, you will be prompted to select the item in question, which will automatically mark it out of stock.” A branch that rejected three orders during a rush may be back online with a shorter menu than it had that morning.
Who do you contact when a Bolt Food store will not reopen?
Bolt does not publish an answer to that, and the honest reporting of the gap is more useful than a guess. We read both official merchant guides and the partner login surface looking for a support route dedicated to availability, an escalation address, a target response time or a named ticket type for a store that cannot be reopened, and there is none in the published material.
What Bolt does publish is that the account has a support relationship at all, since the merchant portal is the place partners are directed to for account matters. The practical instruction that follows is procedural rather than technical. Record the moment the store stopped being orderable, record the state the tablet was showing, record whether the schedule for that day allowed trading, and take that to your existing Bolt contact rather than opening a conversation about a symptom you cannot evidence.
That gap matters more here than it would elsewhere, because there is also no published case in which Bolt Food closes a restaurant itself, which we checked and reported separately. If the platform never closes you, then no support queue exists whose job is to open you, and the absence of a documented contact is consistent rather than an oversight. It also means an escalation about a stuck store is a commercial conversation with whoever holds the account, not a technical ticket with a service level behind it.
How long does a Bolt Food return actually take?
The press itself is instant. Everything before the press is the cost, and on Bolt Food that interval has no ceiling built into the product. A store switched off at the start of a Friday rush by a member of staff who then finished their shift is off until the next person who both notices and can reach the device. Overnight, that is the following morning at the earliest.
This is the sharpest contrast in the set of platforms a Gulf or European chain typically runs. Uber Eats lifts an unattended pause at 6:00am the next day. Just Eat restores an offline restaurant automatically the next day. Glovo ends a closed day at the next scheduled opening. Snoonu stores a pause with a countdown attached. Bolt Food gives that treatment to busy mode and to sold out items, and gives none of it to the store. Because the offline state on Bolt Food has no expiry, the gap between the button and somebody noticing is the entire loss, and that gap is what Kitchain (kitchain.co) measures on Bolt Food storefronts from the customer side rather than from a merchant dashboard.
What should a multi branch chain put in its Bolt Food runbook?
Three rules, all of them about people rather than about the platform. First, write the closing checklist so that the last person out confirms the store is online, since Bolt will not confirm it for them and the morning shift inherits whatever they left. Second, put busy mode rather than offline in the standard instruction for a kitchen under pressure, since busy mode buys time and ends itself while offline does neither. Third, name in advance the person per branch who can physically reach the device out of hours, because that person, and not the platform, is your recovery time.
The reporting habit that goes with those rules is to record intervals rather than statuses. A status tells you where a branch is now, which is the one moment nobody needs help with. An interval tells you that the same branch went dark at 19:10 on three Fridays in a row, which is a staffing pattern and is fixable.