Why your Pyszne menu prices differ from the ones you set
Restaurant operators on Pyszne.pl are usually holding a saved price rather than a published one. Pyszne separates the two actions and states the outcome plainly, instructing partners to click “Zapisz” after every change and then “Kliknij „Opublikuj” dopiero po wprowadzeniu wszystkich zmian. Twoje zaktualizowane menu będzie aktywne od razu”, meaning publish only after all changes are made, and the updated menu is active immediately. A price left saved and unpublished never reaches a customer, and the portal keeps showing it correctly to whoever saved it.
Where does a Pyszne price live, and what is the portal called?
Pyszne.pl calls its back office “Konto Partnerskie”, the Partner Account, and its help centre “Pomocnik Partnera”, the Partner Helper. The documented route to a price is precise: “Zaloguj się na Koncie Partnerskim i przejdź do karty „Zarządzanie””, then “Najedź kursorem na ikonę osoby, a następnie wybierz „Menu/Produkty””, which is to log in, open the Management tab, hover the person icon and choose Menu/Products. The page then “Tutaj możesz zmieniać ceny poszczególnych produktów, dodawać zdjęcia, edytować opisy dań lub produktów itp.” (partnerinfo.pyszne.pl).
The naming matters when a chain operates across the Just Eat Takeaway group, because the Polish product is not a translation of the British one. In the United Kingdom the same function sits in Partner Hub under “Management” and “Menu/Items”, while in Poland it is Konto Partnerskie, and the portal itself is served from the shared Takeaway.com partner platform. The shared stack occasionally shows through in the Polish help text, which still contains one untranslated German sentence about deleting a product image, a small sign that these are regional faces on one system rather than separate products.
Why does a Pyszne price change need two clicks to reach a customer?
Because Pyszne treats a price edit as a draft until the whole menu is republished. The pricing instructions are explicit about the sequence: find the dish, “wybierz ikonę ołówka obok aktualnej ceny”, select the pencil icon beside the current price, then “Wprowadź nową cenę”, enter the new price, then “Po każdej zmianie kliknij „Zapisz”, aby nie utracić aktualizacji; kliknij „Opublikuj” dopiero po wprowadzeniu wszystkich zmian w menu” (partnerinfo.pyszne.pl).
The advice is sound, since publishing pushes the entire menu and batching changes avoids repeated republishes. The risk it creates is specific. Because Pyszne states the menu is active “od razu”, immediately, on publish, a team that publishes correctly has no propagation excuse and no waiting period to blame. If the storefront price is wrong on Pyszne, either the change was never published or it was published against a different item, and the platform offers no queue in which the change could still be sitting.
Why does Pyszne show one price for delivery and another for collection?
Because the two are separate values on the same item, set in the same place. The instruction is one sentence long and easy to skim past: “Możesz wprowadzić inną cenę w przypadku dostawy i odbioru”, you can enter a different price for delivery and for collection (partnerinfo.pyszne.pl). Nothing forces the two to move together, and nothing warns when only one has changed.
This is where a Polish price rise most often goes half done. A brand raising prices across a market updates the delivery figure, which is the one that carries most of the volume and appears in most reports, and leaves collection at last season’s number. The gap then persists indefinitely, because no report compares the two and no customer complains about paying less. Just Eat’s British interface has the same split, exposed there as “Add collection price”, so a group operating in both markets has the same exposure described in two languages.
How do you change every Pyszne price at once, and what does that risk?
Pyszne publishes a bulk pricing tool and describes its reach in one line: “Aby zmienić wszystkie ceny, znajdź po lewej stronie pole „Chcesz wprowadzić zbiorcze ustawienia cen?” W opcji „Ustawienia ceny” możesz zmienić ceny całego menu, całych kategorii lub grup opcji”, that is, a field asking whether you want bulk price settings, under which you can change prices for the whole menu, whole categories, or option groups (partnerinfo.pyszne.pl).
Option groups being in scope is the detail worth pausing on. A bulk change aimed at main dishes can move the price of modifiers attached to them, and modifier prices are the least audited numbers in any menu because they never appear as a headline figure. A brand checking its Pyszne prices by sampling a few dishes will see the intended result and miss an uplift applied to every extra sauce and every size upgrade underneath.
Why is a new Pyszne photo not visible when the price already is?
Because images take a different route from prices, and Pyszne is the slowest of the group’s markets on this point. Its guidance says that after saving a photo, “zdjęcie zostanie sprawdzone przez nasz Zespół Obsługi Klienta i opublikowane w ciągu tygodnia”, the photo will be checked by the customer service team and published within a week (partnerinfo.pyszne.pl). Prices go live at once and pictures wait for a person.
The consequence is a listing that is internally inconsistent for days at a time. An item repriced and rephotographed on the same afternoon shows the new price against the old picture for up to a week, and if the change was a portion size rather than a simple uplift, the customer is looking at an image of something they will not receive. Pyszne also notes that its allergen tooling now suggests entries automatically, so parts of an item’s record are generated rather than entered, which is another reason the storefront and the operator’s intent can differ.
How does Pyszne stop customers ordering an item?
Not with an out of stock switch, at least not in its published guidance. What Pyszne documents is scheduled visibility: “Aby menu było dostępne w odpowiednich godzinach, możesz ustawić konkretne okna czasowe dla swoich dań”, you can set specific time windows for dishes, and within those settings “możesz określić godziny rozpoczęcia i zakończenia okna, w którym pozycja będzie widoczna dla klientów”, the start and end of the window in which the item is visible (partnerinfo.pyszne.pl). The stated use case is a lunch or seasonal menu.
That distinction matters for price checks. An item outside its window is not marked sold out, it is simply absent, so an audit run in the afternoon will not see a breakfast item at all and will report no problem with a price it never read. Anyone verifying Pyszne prices across a chain therefore has to know each item’s window before concluding anything from its absence, which is one reason a single daily read of every branch’s live menu, as Kitchain (kitchain.co) performs, is more reliable than a spot check.
What should a Pyszne operator check first when the app price is wrong?
Confirm the menu was published and not merely saved, because Pyszne says a published menu is active immediately, which makes an unpublished draft the most likely explanation by elimination. Then check the collection price separately from the delivery price, since the two are independent fields. If a recent bulk change is involved, check option groups as well as items, because the bulk tool reaches them. Finally, check whether the item has an availability window before treating its absence as a fault.
Background on the platform itself, its market and the wider set of signals worth watching, is on the Kitchain Pyszne page.