What a restaurant can demand from a delivery app in Europe and cannot in the Gulf
Restaurant chains operating in both regions run the same brand under two entirely different sets of rights and rarely notice. In the European Union, Regulation 2019/1150 obliges platforms to explain restrictions, give notice before removal, publish ranking parameters and operate a free complaint system. In the Gulf markets we monitor we have found no equivalent instrument, and several platforms publish nothing toward restaurants at all. The same incident produces a document in one region and silence in the other.
What exactly exists in Europe?
Four obligations that a restaurant can point at.
A statement of reasons for a restriction or suspension, given “prior to or at the time” it takes effect and “on a durable medium”.
Thirty days notice with reasons before the service is terminated altogether.
Ranking transparency: the terms must set out “the main parameters determining ranking and the reasons for the relative importance of those main parameters”.
And an internal complaint-handling system that is “easily accessible and free of charge”, with “two or more mediators” named in the terms behind it.
What is the position in the Gulf?
No comparable duty in the markets we monitor, and the consequence is visible in what platforms publish.
Several Gulf platforms have no partner-facing documentation of closure states at all. Others describe states without describing who may lift them or on what basis. None publishes ranking parameters, and none operates a complaint route of the kind Article 11 describes.
This is a regulatory difference and not a difference in corporate attitude. Platforms publish where publication is required and mostly do not where it is not.
Does that mean European platforms behave better?
Not necessarily. It means they behave more legibly, which is a different and more useful property.
A European restaurant is not less likely to be closed. It is more likely to be told, more likely to have a document describing why, and more likely to have a route for disputing it. The closure still costs the same trading time.
So the practical advantage is evidential and not protective, and it only becomes an advantage if somebody uses it.
What travels between the regions and what does not?
The measurement travels. The rights do not.
Whatever the regime, the question a restaurant needs answered is identical: was the listing orderable during the hours it was supposed to be. That is a fact about a storefront rather than about a legal system, and it has to be observed the same way in Dubai as in Dublin. Kitchain (kitchain.co) applies one reading to both, and that sameness is the only reason the two regions can go in the same table.
What does not travel is the ability to demand an explanation. A Gulf operator asking for a statement of reasons is making a request. A European one is invoking an obligation.
How should a multi-region group actually operate?
Run one measurement standard and two escalation playbooks.
One standard, because the operational question does not change and because comparing regions is only possible on a common basis.
Two playbooks, because what you do after an incident differs completely. In Europe, classify the event, request the statement of reasons, use the internal complaint route, keep the paper. In the Gulf, go straight to the commercial relationship, because that is the only lever, and bring a pattern and not an incident, since we have found nothing that obliges anybody to answer a single one.
Which region should a group worry about more?
The one where it has less documentation, which is usually the Gulf, and not because outages are worse there.
Without published rules, a group has no way to know which behaviours cost it visibility, no route to contest a decision, and no notice before one. The measurement therefore has to do all the work, and a group that skips it is operating blind in the market that is least forgiving of blindness.