My Swedish restaurant is offline on the delivery app
Restaurant operators in Sweden have a detection problem on top of the ordinary availability problem, and it comes from the shape of demand. Delivery volume swings hard between seasons and between weekdays, so a soft evening is entirely plausible for reasons that have nothing to do with the listing. That plausibility is what lets an outage run. The kitchen is staffed, the tablet looks normal, no orders arrive, and everybody has a ready explanation that happens to be wrong.
What makes an outage hard to spot here?
The absence of a reliable baseline at the hour it matters.
A city centre site with steady demand produces a visible gap when it goes dark. A site whose Tuesday evening volume varies by a factor of three across the year produces a gap that fits inside the normal range. The signal disappears into the variance.
That is a structural argument against inferring availability from sales, and it applies with more force in seasonal markets than anywhere else.
What should I check instead?
Whether a customer could order, observed directly.
Open the listing from an address in the catchment and look. If it is absent or closed, you have the answer immediately. If it is present and orderable, all you have learned is that it was fine at the minute you looked, and in a market where the baseline moves this much one clean look is very easy to mistake for reassurance.
For that reason the useful version is not a check but a schedule, run at an interval short enough that an evening outage cannot hide between two observations. That is the interval Kitchain (kitchain.co) keeps against a Swedish listing, and it is set by how small an incident you want to be able to see.
What are the usual causes?
Ordinary, and two of them take on a seasonal flavour that is worth planning around.
Schedules drift because sites change hours between seasons and update one platform and not another, so a listing can carry winter hours into the spring for weeks. And devices are more likely to be left unattended during quiet periods, so a failure that begins in a slow week runs unnoticed into a busy one and is discovered by the takings rather than by anybody looking.
What can I demand if it was the platform?
An explanation, and immediately, and the wording matters.
Regulation 2019/1150 requires a platform restricting or suspending its service to give a statement of reasons “prior to or at the time of the restriction or suspension taking effect”, on a durable medium. Article 4(3) adds a right to clarify the facts within the internal complaint process, which Article 11 requires to be “easily accessible and free of charge for business users”.
Ask in those terms and keep the reply. The value is in the accumulation, not in any single answer.
Does seasonality affect what platforms grade me on?
Order volume criteria, yes. Availability criteria, no, provided the published hours are honest.
That distinction is worth acting on. A site that reduces its published hours in a quiet season is not penalised for the hours it no longer claims, and it removes a stretch of time in which an unnoticed closure could occur. Publishing hours you do not reliably staff works against you twice.
What should a Swedish group do first?
Fix the published hours per site and per season, then measure availability against them for a month.
Doing it in that order matters. Measuring availability against hours nobody keeps produces a number that describes the schedule rather than the restaurant, and the resulting list points at the wrong sites.