My restaurant went offline on a Polish delivery app. What do I do?
Restaurant operators in Poland work against an unusually crowded marketplace, which changes the first move. A brand there can be carrying listings on Pyszne.pl, Glovo, Bolt Food, Wolt and Uber Eats simultaneously, each with its own portal, its own closure vocabulary and its own rules about who may end a closure. So the useful first question is not why the restaurant is offline but on which listing, because the answer determines whether you can fix it yourself in seconds or need to write to somebody.
Why does the platform matter so much here?
Because the recovery paths genuinely differ, and assuming they are the same wastes the evening.
Some closures carry a timer and lift themselves. Some are set by the restaurant and cleared by the restaurant. And some are applied by the platform and cannot be reversed by the partner at all, which turns the incident from a task into a support queue.
A Polish operator with five listings has all three categories in play at once, so the diagnosis has to name the platform before it names the cause.
Which listing do I look at first?
Whichever ones are still up, because the comparison is the diagnosis.
If the Glovo listing is trading and the Pyszne listing is not, this is one platform’s problem and the kitchen is irrelevant. If all of them are down together, look at the site: the network, the devices, or something done centrally to the menu.
That single comparison is the fastest diagnostic available in a multi-platform market, and Poland is exactly the market where it works best because the platform count is high.
What can I demand if the platform closed me?
An explanation, and this is where operating in Poland differs sharply from operating in the Gulf.
Regulation 2019/1150 requires a platform restricting or suspending service to provide a statement of reasons “prior to or at the time of the restriction or suspension taking effect”, on a durable medium. Ending the service altogether requires “at least 30 days” notice with reasons.
So a listing closed by the platform without explanation is not merely inconvenient, it is a failure of an obligation. Ask for the statement of reasons in writing and name the article.
Is documentation the same across the Polish platforms?
No, and the differences are worth knowing before you need them.
Pyszne.pl publishes noticeably less in Polish than the same product publishes in English for the United Kingdom, which is a documentation gap rather than a difference in how the product behaves. Wolt, Glovo and Bolt Food each publish ranking material of the kind Article 5 requires.
The practical effect is that on some platforms you can quote a document at your account manager and on others you cannot, and that shapes which arguments are available.
How do I know when it started?
From your own record, because no portal keeps one you can audit and because the site will not remember.
This matters more in a five platform market than anywhere else, because the number of listings that can quietly fail is five times larger and nobody is watching all of them. Kitchain (kitchain.co) keeps a separate record per listing, so Pyszne and Glovo and Wolt can be set side by side for the same site on the same evening.
What should a Polish group do differently?
Decide which platforms it is actually going to maintain, and drop the ones it will not.
Five listings per site is a real maintenance load: five schedules, five menus, five sets of holiday hours. A listing nobody maintains becomes wrong within a quarter and dark within two, and a wrong listing damages the brand more than a missing one.