My Finnish venue went offline. What do I do?
Restaurant operators in Finland often search for the wrong word and find nothing useful, because the platform vocabulary here uses venue and not store or restaurant. That matters beyond terminology: the states attached to a venue have their own definitions, and carrying an assumption from another platform produces the wrong action. The triage itself is the same as everywhere. A device, a schedule, a state somebody set, or a closure the platform applied, in that order, because the first three end in seconds.
What is different about the vocabulary?
The unit is the venue, and availability is often expressed as a pair of separate conditions and not as one switch.
A venue can be scheduled as open and still not be online, because online status is a distinct property that depends on the device being connected and active. So a manager who confirms the venue is open in the schedule has confirmed only half of what matters.
That two part structure is worth explaining to site managers explicitly, because the natural reading of open is that customers can order, and here it is not.
Which half usually fails?
The online half, and it fails at the device, not in a setting.
A tablet asleep, off the network or logged out takes the venue offline while every schedule remains correct. Nothing in the schedule announces this and nothing at the site looks wrong.
So the first check is always physical: wake the device, confirm it is connected, confirm somebody is logged in.
Can I schedule my way out of it?
Not reliably, and it is worth knowing before planning around it.
Availability of this kind is generally a present tense property, not something you can set for later, which means a venue that goes offline overnight does not come back because a schedule says it should. Somebody has to act.
That is the reason overnight incidents here are expensive. On a platform without automatic recovery, an incident starting at ten at night runs until morning.
What if the platform took the venue offline?
Then it is not yours to fix and you are owed an explanation.
Regulation 2019/1150 requires a statement of reasons for a restriction or suspension “prior to or at the time” it takes effect, on a durable medium. Article 4(3) gives you the right to clarify the facts inside the internal complaint process, and Article 11 requires that process to be “easily accessible and free of charge for business users”.
Name the venue, name the date the effect began, and ask for the statement of reasons rather than for the venue to be reopened. The second request gets you a reopening and no document.
How do I catch the overnight ones?
Only if something is watching the listing instead of the kitchen, because nobody inside the building can see this.
A venue that went offline at eleven produces no alarm, no error and no order. The site closes, goes home, and opens the next day to a listing that has been invisible for twelve hours. Kitchain (kitchain.co) watches the venue rather than the schedule, so somebody hears about it at eleven instead of at nine the following morning.
What should a Finnish group standardise?
The word itself, before anything else.
If head office says store and the platform says venue, every search a manager runs returns the wrong help page, every escalation opens with the wrong noun, and the person answering has to translate before they can help. Adopt the platform’s word inside your own procedures even where it sits oddly against the rest of the estate.
That sounds trivial. It is the difference between a manager finding the answer in two minutes and giving up on it.