Why is my Wolt venue showing as offline when the restaurant is open?

Restaurant chains selling on Wolt meet a distinction that most delivery platforms do not make. Wolt keeps being open and being online as two separate facts about the same venue, and its API returns them as two separate booleans, is_open and is_online. A venue can be inside its scheduled hours, which makes it open, and still be unable to take orders, which makes it offline. The most common route into that state is not a decision at all. Wolt warns that some tablets go offline after around twenty minutes of no activity, and an offline venue is invisible to customers.

What does offline mean on a Wolt venue, and how is it different from closed?

Wolt’s Merchant API exposes a venue status object containing three booleans: is_open, is_online and is_ipad_free. Source: developer.wolt.com. The first describes the schedule, the second describes whether the venue is actually taking orders right now, and the third describes whether the venue runs without a Wolt tablet.

Holding those apart is what makes Wolt legible. On most platforms an operator has one flag and has to guess whether an unorderable listing is a scheduling problem or an operational one. On Wolt the two questions have different answers in different fields, and the failure this page is about is the one where the schedule says open and the venue is not online.

The write side of the API uses a two value enum. The endpoint that updates a venue’s online status takes a status field described as “The new store status to use”, with ONLINE and OFFLINE as the permitted values. Alongside it sits until, described as “The date and time (ISO 8601 format) when the venue is to be set offline. Use null or omit the field completely to set venue offline indefinitely.”

In the merchant app the same state has a friendlier face. Wolt describes the control as a status button and says: “This button shows your venue’s current status. A green dot with ‘Open’ means you’re ready to accept orders.” Source: merchant.wolt.com. Note the word on the button is Open while the field underneath it is online, which is exactly the confusion the API avoids and the interface reintroduces.

Why can a Wolt venue go offline when the tablet is left alone?

Because the merchant app has to stay awake for the venue to stay online, and Wolt says so in its own availability guidance: “Some tablets go offline after about 20 minutes of no activity. To avoid this, just check your tablet a few times a day to make sure the app is on and your venue is online.” Source: merchant.wolt.com.

Two things about that sentence are worth reading carefully. It says some tablets, not all, and it says about twenty minutes rather than committing to a threshold. Wolt is describing device behaviour it does not fully control, which means the rule differs by hardware and cannot be planned around precisely. The same guidance is explicit about the consequence: an app that is closed during business hours leaves the venue invisible to customers with no orders arriving.

For a single restaurant this is a habit problem. For a chain it is a structural one, because venue availability now depends on the screen state of one device per branch, and no head office system reports whether an app is in the foreground. A branch can be fully staffed, fully stocked and completely absent from Wolt because a tablet dimmed itself during a quiet spell after lunch.

Wolt also automates the routine part of availability, stating that the app opens and closes the venue based on the hours the merchant has set. That is useful and it is also the reason the failure is quiet. When opening happens by itself, nobody develops the habit of confirming that it happened.

Why does a Wolt venue stay offline once it gets there?

Because Wolt reads a missing end time as an instruction rather than as an omission. The API guidance states: “To schedule the venue to be offline until a certain time, set status=OFFLINE and until to the desired date and time. Otherwise, the venue will be put offline indefinitely.” Source: developer.wolt.com. Nothing is malfunctioning in that case. The venue is holding the state it was given, and it will keep holding it.

That is what separates a Wolt outage from a Wolt closure. A closure carrying an end time is a decision that expires. A closure without one is a decision that persists, and the two are identical on the storefront, which is why the length of an offline period on its own says nothing about what produced it. A venue dark for six hours may have been paused at four in the afternoon by somebody who then went home, and a venue dark for twenty minutes may be a tablet that has done exactly the same thing every day for a month.

How a venue is brought back, why the return cannot be booked in advance the way the departure can, and which control branch staff should be allowed to touch are a separate procedure, set out on how to get Wolt to put your restaurant back online.

What does an offline Wolt venue lose besides the orders?

Position, and Wolt publishes the rule rather than leaving it to be worked out. In its account of how its search and recommender systems work, Wolt states that venues “that are closed or with ‘pick up only’ options are downranked in the results”, and that on category pages “Offline or currently unavailable venues are sorted at the end of the page.” Source: press.wolt.com.

So an hour spent offline is an hour at the bottom of the category page for everyone browsing that area, and the position a venue holds on its return is not automatically the position it had when it left. That turns a short availability fault into a longer visibility one, and it explains a complaint that sounds unrelated to the original problem: a manager reporting thin volume for days after an incident that was resolved in an afternoon.

The second cost is scored rather than counted. Wolt’s Best of Wolt programme lists uptime among the metrics behind a venue’s monthly level and states that “Your overall level is based on the metric where you have the most room to improve.” Source: merchant.wolt.com. A venue with strong food scores and weak uptime is graded on the uptime, which makes the tablet on the counter a rating input on this platform and not only an availability one.

How do you catch a Wolt venue that went offline by itself?

By checking the thing the customer checks, because that is the only place the two axes collapse into one visible answer. A venue that is open on schedule but not online looks, on the consumer app, exactly like a venue that is closed for the night, and nothing in the merchant view will flag the difference unless somebody opens the app on the tablet in question.

The signature to look for is repetition rather than duration. A venue that disappears in the same part of the day, week after week, is reporting a device or a habit rather than a run of accidents, and that shape only exists in a record kept over time, because the venue status object describes this minute and nothing before it. Kitchain (kitchain.co) collects orderability on Wolt venues from the customer side and reads it against the hours each venue published, which is what makes a repeated quiet hour distinguishable from an hour that was simply quiet.

One last vocabulary warning for anyone comparing reports across platforms. Wolt calls a location a venue and treats open and online as two different things, so a Wolt availability number and a number from a platform with a single flag are not measuring the same event. Background on the platform itself is at kitchain.co/aggregators/wolt/.