Why is my Pyszne.pl restaurant offline when the kitchen is open?
Restaurant chains selling on Pyszne.pl are using Just Eat Takeaway partner tooling under a Polish name, and that matters more than it sounds. The back office is called Konto Partnerskie, the switch is a slider labelled “Przyjmowanie zamówień”, and taking a restaurant offline produces a confirmation reading “Włączono tryb offline do jutra”, offline mode enabled until tomorrow. The Polish knowledge base documents how to go offline. It does not document how to come back, or the automatic rules that operate on the same platform elsewhere.
What does “Włączono tryb offline do jutra” mean on Pyszne.pl?
It means the restaurant has been taken off the app and will be put back tomorrow. The Polish partner article on opening hours describes the procedure under the heading “Jak tymczasowo przejść w tryb offline”, how to temporarily go into offline mode, and carries this note in brackets: “(Uwaga: ta funkcja automatycznie przywraca status online następnego dnia.)”, which translates as a note that the feature automatically restores online status the next day. The step itself reads “Przełącz suwak ‘Przyjmowanie zamówień’, aby zmienić status”, toggle the Taking orders slider to change your status. Source: partnerinfo.pyszne.pl.
Two consequences follow from that one bracketed note. First, an accidental offline on Pyszne.pl repairs itself, so nobody ever has to explain it the next morning. Second, and less comfortably, the automatic restoration also hides the event. The evening that was lost leaves no artefact in the partner account, and the only place it existed was on the customer’s screen.
One thing the confirmation does not describe is what the customer meets, and that gap is worth closing before anyone answers a complaint. Pyszne.pl does not publish the customer facing wording for a restaurant in this state, so a Polish operator cannot say from the documentation whether the listing disappears from the results, appears greyed with a note, or accepts a scheduled order for later. Those three produce three different customer stories, and a manager arguing from the partner article alone will get the story wrong.
Closing for a whole day is a different control, in the hours editor rather than on the home screen. The article describes it as a checkbox: “Zarządzając godzinami otwarcia i zamknięcia, masz również możliwość zamknięcia restauracji na dany dzień poprzez zaznaczenie odpowiedniego pola”, when managing opening and closing hours you also have the option to close the restaurant for a given day by ticking the relevant box. A successful change to hours confirms with a popup reading “Zaktualizowano godziny otwarcia”.
Is Pyszne.pl the same system as Just Eat, and does that matter?
It is the same system, and we verified it rather than assuming it. The Pyszne.pl partner knowledge base at partnerinfo.pyszne.pl runs the identical front end as the Just Eat partner knowledge base at partnerinfo.just-eat.co.uk, down to the same build filename, and that front end carries a host list mapping each national partner site to its locales, and partnerinfo.pyszne.pl sits in it alongside partnerinfo.just-eat.co.uk, partnerinfo.lieferando.de, partnerinfo.thuisbezorgd.nl, partnerinfo.justeat.it, partnerinfo.bistro.sk and partnerinfo.skipthedishes.com.
The Polish articles also link partners into hosts that carry the group name rather than the Polish one, including partner-hub.takeaway.com for account settings, next to partner-hub.pyszne.pl for the menu.
Why it matters is practical rather than trivial. A Polish operator searching in Polish will find a short article. The same product, documented for the United Kingdom, has published rules that the Polish version does not mention at all, and an operator who does not know the two are the same platform will never think to look.
What does the Polish documentation not tell you?
The behaviour that would explain an offline nobody chose. Just Eat’s English order management article, written for this same tooling, publishes an automatic rule: an order not acknowledged within five minutes is rejected automatically, and the restaurant is then taken offline “under the assumption that you are closed or too busy to accept incoming orders”. Source: partnerinfo.just-eat.co.uk. The Polish knowledge base carries no translation of that rule.
We are not going to claim it operates in Poland, because Pyszne.pl does not publish it, and we are not going to tell a Polish operator it has been ruled out, because nothing published says that either. What the silence actually does is delete a whole category of explanation from a Polish incident review. A British manager who finds a restaurant dark and no member of staff willing to admit pressing anything has a documented candidate to test against the order log. A Polish manager in the same room has no published candidate at all, so the review ends at somebody must have touched it, and the same evening happens again.
The return procedures are missing from the Polish article too. Because those belong to the recovery rather than to the cause, they are set out on our page about how to get Pyszne.pl to put your restaurant back online instead of here.
What can a Pyszne.pl operator actually control?
Three settings, and they are worth separating because only one of them expires. The live slider is a state that Pyszne.pl undoes by itself the next morning. The weekly opening hours are a schedule that stays exactly as typed until somebody edits it again. The day closure box is a dated instruction that keeps its date. An operator who files all three under being shut will treat a schedule fault as an incident, wait for it to clear the way an offline does, and lose the same hours every day while waiting.
That distinction decides what a diagnosis should start with. A restaurant that was orderable yesterday and is not today has almost certainly had its state changed by a person or by the platform. A restaurant that has been missing at the same hour for a fortnight has had nothing changed at all, and the fault is sitting in the hours editor where nobody looks during service. The Polish FAQ points partners at the live control in the Konto Partnerskie panel and at the equivalent on the order handling device, and which of those two surfaces a manager should check first during a recovery belongs with the return procedure.
How do you catch a Pyszne.pl restaurant that went offline?
By checking whether the listing can be ordered from, minute by minute, against the hours the restaurant published for that day. On this platform that is the only method that works, for a specific reason: the offline state restores itself overnight, so by the time anybody reviews the partner account the evidence is gone and the account looks correct.
Two properties of the interval carry all the diagnostic value. Its length separates an offline somebody caught from one that simply ran until the platform undid it, because the restoration is the deadline everything is measured against. Its recurrence separates an accident from a rota, because the same restaurant losing the same part of the same weekday is a person or a handset, not luck. Konto Partnerskie holds neither, since it reports the state now and Pyszne.pl has already corrected the state by now, so the interval has to be captured while it is still open, which is what Kitchain (kitchain.co) does by reading Pyszne.pl listings as a customer sees them.
What Pyszne.pl is and who owns it is on our page at kitchain.co/aggregators/pyszne/. If your group also trades under other brands of the same parent, and the host list inside the shared knowledge base names several including Lieferando, Thuisbezorgd, Just Eat Italy and Bistro, the tooling will look familiar while the published rules will not match. That is worth checking before assuming a policy transfers from one country to another.