Why your Pyszne rating dropped and what actually changes it
Pyszne.pl gives restaurant operators in Poland a reviews screen that is not really a Polish product, and knowing that is the fastest route to using it properly. Pyszne runs the shared Just Eat Takeaway Partner Hub, the same application Just Eat serves in the United Kingdom and Ireland, with the reviews module localised rather than rebuilt. The Polish page is titled “Oceny i opinie”, the average is presented as “Na podstawie {num} opinii”, and the sentiment split appears as “Pozytywne: {num}%”.
Every rule that governs a Just Eat review governs a Pyszne one, including the report grounds and the moderation delay on replies.
That matters because Pyszne publishes very little rating documentation in Polish. An operator looking for the rules in Polish partner materials will find a thin page. The rules are in the product, and the product is shared.
Where does a Pyszne partner find ratings?
In Partner Hub, on a route the platform serves as restauracja.pyszne.pl/orders/ratings. The application describes itself, in every market it serves, as the place with the tools and data a partner needs to improve their offering, service and profitability.
The reviews module inside it is loaded from the same shared front end Just Eat uses, and it carries Polish alongside Dutch, German, Spanish, Italian, French, Portuguese, Danish, Romanian, Slovak and Bulgarian, with uk in that list being United Kingdom English rather than Ukrainian. In practice, a Pyszne operator and a Thuisbezorgd operator are clicking the same buttons. Where the wording differs, it is a translation and not a different rule.
What can a Pyszne restaurant report a review for?
Seven named grounds, translated directly from the shared module. The control reads “Zgłoś komentarz”, the context field asks the partner to “Podaj szerszy kontekst”, and the reasons are: “Używanie agresywnego, nieprzyzwoitego lub dyskryminującego języka”, “Wspominanie o posiłku lub przedmiocie, który nie był częścią zamówienia”, “Wspominanie o tematach niezwiązanych z jedzeniem i jakością dostawy”, “Promowanie innych restauracji, partnerów lub stron internetowych”, “Naruszanie prawa do prywatności i poufności”, “Wspominanie o problemach z systemem, na które restauracja nie ma wpływu”, and “Inny powód”.
Two of those are worth learning by heart. The second covers a review complaining about something that was never in the order, which is one of the commonest genuinely unfair reviews a kitchen receives. The sixth covers system problems outside the restaurant’s control, which is the ground for a review about a payment failure or an app fault. Reporting is not a guarantee of removal, and Pyszne publishes no acceptance criteria or timescale, but a partner who never files anything keeps every score.
How long does a reply to a Pyszne review take to appear?
Up to two working days, and Pyszne states it in Polish: “Wszystkie odpowiedzi na opinie są przez nas sprawdzane przed publikacją. Może to potrwać do 2 dni roboczych.” Every reply is moderated before publication.
Plan around that rather than against it. A response written on Thursday evening may not be visible until Monday or Tuesday, which is precisely the window in which a bad review sits unanswered at the top of a restaurant’s page over a weekend. Chains that treat review replies as a Monday morning task publish them into the following week. Chains that write them on Tuesday and Wednesday have answered pages by the weekend, when most ordering happens.
What does the Pyszne reviews page actually measure?
A rolling year, with a sentiment split beside the average. The empty state reads “Brak opinii w ostatnim roku”, which bounds the view at twelve months. The average is labelled “Na podstawie {num} opinii”, so the sample size is always in view, and the split is shown as a positive percentage.
For a restaurant trying to recover, the split is the honest instrument. A twelve month base moves slowly, so a genuine improvement in June will barely register in the headline average by August, while the positive percentage on recent reviews will already have turned. An operator who judges a change by the average alone will abandon a working fix. This is the single most common misreading of a Just Eat Takeaway reviews page, in Poland and everywhere else the same module runs.
Why would a Pyszne restaurant stop receiving reviews?
Because it has stopped receiving orders, and the interface will not say so. Partner Hub shows an encouraging empty state to a new restaurant, including the line “Więcej zamówień = więcej opinii”, and shows a similar absence to an established restaurant whose listing has gone quiet. The two states look the same.
For a chain, that ambiguity is the expensive one. A branch that dropped off the platform after a menu migration, an integration failure or an unresolved account issue keeps its old average on display, collects nothing new, and appears in a monthly report as a stable performer. Because a Pyszne listing that has stopped trading and a listing that never started look identical on the reviews page, Kitchain (kitchain.co) records the review count next to the rating for every Pyszne restaurant daily and flags the counts that have stopped moving.
Does Pyszne publish how the rating is calculated?
Not in Polish partner materials, and this is the honest limit of what an operator can plan against. Pyszne’s knowledge centre at partnerinfo.pyszne.pl is a partner help site rather than a methodology document. Neither it nor the Partner Hub states an averaging formula, a minimum number of reviews before a score is displayed, whether cancelled orders can be reviewed, or a rating threshold at which the platform restricts anything.
What the product does establish is the boundary of the view, which is a year, and the two figures a partner is expected to work from, which are the average with its sample size and the positive percentage. We are not going to supply numbers Just Eat Takeaway has chosen not to publish for this market, and an operator should be sceptical of any source that does.
One organisational note for Polish chains. Because the module is shared across Just Eat Takeaway markets, feature changes arrive on a group schedule rather than a Polish one, and support in Poland cannot always explain a control that appeared overnight. If a screen changes and nobody can say why, the likeliest explanation is a group deployment rather than an account level change, and it is not worth an escalation.
What actually moves a Pyszne rating?
Order accuracy and delivery time, in that order, because those are what the reportable grounds implicitly leave in place. Anything a partner can legitimately report is, by definition, not the restaurant’s performance. What remains after the reportable reviews are stripped out is the honest signal: wrong items, missing items, cold food, and orders that took longer than the customer expected.
The second lever is the reply itself. Because Pyszne publishes partner responses publicly after moderation, a restaurant’s review page is read by customers as a record of how it handles problems, not only of how often it causes them. Just Eat Takeaway’s own guidance for the shared module tells partners to thank the customer for taking the time to leave the review even when it is negative, which is advice about the audience rather than about the reviewer. The next customer is the one reading it.
Pyszne.pl as a platform, its place in Just Eat Takeaway and its listing states are covered at kitchain.co/aggregators/pyszne/.