Norway: why a restaurant can be invisible while the kitchen is open
Restaurant operators in Norway describe this as the app being broken and it is usually one of three ordinary things. The storefront is not orderable, so nobody can buy. The delivery zone does not reach the address the customer is standing at, so they never see you. Or the listing is ranked low enough that a browsing customer stops scrolling first. All three produce zero orders from that customer, all three are invisible from the kitchen, and each needs a different response.
How do I separate the three?
Two searches and one comparison, done on a phone and not in a portal.
First, from an address beside the site, try to reach a checkout and not merely to find the listing. If you cannot, the storefront is the problem and the other two are irrelevant. Second, repeat from the far edge of the catchment. Present at one address and absent at the other is the zone. Third, browse the category instead of typing the name. Findable by name and not by browsing is ranking.
Five minutes, and it redirects most of these investigations away from where they would otherwise have gone.
Which of the three is most often the real one?
The storefront, by a wide margin, and it is the one operators check last because it feels least likely.
The reason it is so common is that it fails silently. A device asleep, a state somebody set, a schedule that does not match today. None of those produces an error and all of them look like a slow evening from inside.
Why does the zone matter more here than in some markets?
Because geography and settlement patterns make catchments narrow, and a small reduction removes a disproportionate share of addresses.
Coverage is also partly a platform decision that responds to courier supply, and it changes without notice. That is not a fault to report so much as a fact to know about, and it explains soft evenings that otherwise get attributed to weather or to competitors.
Because coverage is a property of the map rather than of the listing, it cannot be read from a portal at all. Testing it means trying to order from the edge of the catchment and not only from beside the door, repeatedly, which is one of the things Kitchain (kitchain.co) does on a Norwegian estate.
What can I demand if a platform restricted the listing?
That depends on where the restaurant is established, and it is worth checking instead of assuming.
Regulation 2019/1150 is written by reference to business users established in the Union. We have not verified how it applies to restaurants established in Norway, so we do not state a position. What is safe to say is that the platforms operating across European markets generally publish partner terms and ranking material, and those documents are readable and usable in a conversation whatever the regulatory basis for their existence.
Read your own platform’s terms for what it commits to about suspension, notice and complaints, and hold it to that.
What should be measured?
Availability against published hours, coverage from real addresses, and position over time. In that order of priority.
Availability is the largest and most immediate loss. Coverage explains the persistent shortfall that availability cannot. Position explains the slow decline that neither of the other two accounts for.
What is the first thing a Norwegian group should do?
Decide which of the three it is for each site that is underperforming, before deciding anything else.
Groups skip this and buy visibility for sites that are not visible for a reason no amount of spend will fix. A storefront that is unorderable does not benefit from promotion. A site outside a customer’s delivery area does not benefit from ranking better inside it.
One pass of the three way test across the estate costs an afternoon and reassigns most of the budget that was about to be spent in the wrong place.