Switzerland: delivery platforms for restaurant groups, and what they owe you
Restaurant operators in Switzerland work against the same platforms as their neighbours and not necessarily under the same rules, which is worth establishing before an argument and not in the middle of one. Regulation 2019/1150 is written by reference to business users “that have their place of establishment or residence in the Union”. Switzerland is not in the Union. We have not verified how, or whether, the obligations reach a Swiss-established restaurant, so we do not assert that they do. What follows from that uncertainty is practical, not legal.
What should a Swiss operator assume?
Nothing about entitlement, and everything about the platform’s own terms.
Read what your platform commits to in its Swiss partner terms specifically, rather than reading a European document and assuming it applies. Platforms frequently maintain market-specific terms, and the differences between them are exactly where this question is answered.
Where a platform has published ranking material or a complaint process for European markets, ask whether the same applies to Switzerland. That is a reasonable question and the answer, whichever way it goes, is worth having in writing.
Does the uncertainty change what I do operationally?
Not at all, and that is the useful part.
Whether a customer could reach a checkout is settled by the storefront and not by a legal system, so the measurement does not change at the border. Kitchain (kitchain.co) answers it for a site in Basel on exactly the terms it answers it for one in Freiburg, twenty minutes up the road and inside the Union.
What changes is what you do with the answer. Where an obligation exists, the record supports a demand. Where it may not, the record supports a commercial conversation. In both cases you need the record.
What is the practical difference in escalation?
The language, and how much weight a single incident carries.
In a market with a documented complaint route, a single well-evidenced incident can be filed and answered. Without one, single incidents are absorbed and only patterns move anything. So a Swiss operator should put the effort into accumulating a quarter of dated evidence instead of contesting individual nights.
That is also the more effective approach in the Union, so it is not a downgrade so much as a narrowing of the available options.
What about a group operating across the border?
Expect different answers for a site in Basel and a site twenty kilometres away, and do not let head office generalise from either.
The failure mode is a policy written for one and applied to both. A German or French site can invoke specific articles. A Swiss site’s position has to be established from its own contract. Same brand, same platform, different footing.
What should be in the Swiss playbook?
Three things.
The platform’s Swiss partner terms, read once, with the suspension, notice and complaint clauses noted.
A written answer from the account manager about whether the platform applies its European complaint and ranking commitments here.
And the availability record, per site and per platform, because it is the one asset that works regardless of how the first two turn out.
What about the language regions?
They are a configuration problem before they are a market problem.
A Swiss brand can be carrying German, French and Italian versions of the same menu, and each is a place where a listing can drift from the standard without producing an error anywhere. A group already running a French listing across the border will be tempted to reuse it, and the pricing behind it will not transfer.
Keep the language versions as separate objects to check, and never assume a Geneva listing can be cloned from a Lyon one.