Why your restaurant is not showing in Pyszne search

Pyszne.pl puts its ranking explanation somewhere restaurant operators rarely look, which is the customer help centre rather than the partner hub. The Polish partner contract carries a section headed “SYSTEMY POLECANIA I PARAMETRY KLASYFIKACJI”, recommender systems and ranking parameters, and it points partners to a public page for consumers at pyszne.pl about the restaurant list, stating that this description forms part of the agreement. The document explaining your position is written for the people ordering from you, not for you, and it is binding on both sides.

Where does Pyszne actually explain how restaurants are ordered?

In its consumer support section, under a topic about the restaurant list, with a dedicated article on how search results are positioned. The partner contract does not restate the parameters. It cites the consumer page and incorporates it, which is a meaningful design choice: Pyszne has decided that customers and restaurants should read the same explanation, rather than giving partners a separate account of the same machinery.

For a chain operating in Poland, that has a practical consequence worth acting on. The authoritative Pyszne ranking document is in Polish, on the consumer site, and will not be found by anyone searching an English partner hub. Teams working across several countries routinely miss it for exactly that reason, then conclude that Pyszne publishes nothing, then start guessing. The page exists, the contract points at it, and reading it is the first step rather than the last.

What is the Pyszne paid placement called and how is it billed?

It is called TopRank, and its Polish supplemental terms are explicit about the exchange being made. The programme “umożliwia zwiększenie widoczności na Platformie, na przykład w wynikach wyszukiwania prezentowanych Klientom”, allowing an increase in visibility on the platform, for example in the search results presented to customers. The remuneration is per order, described as “stała opłata za każde Zamówienie”, a fixed fee on each order, charged for as long as the campaign is active.

The terms also state a limit on what the money does: users of TopRank are restricted in how far they can improve their position, because Pyszne wants the other ranking parameters determining an organic position to remain important. And they refuse any guarantee outright, stating that no particular ranking benefit, improvement, visibility or position is guaranteed at any time in any way. A restaurant buying TopRank is buying an improvement of unknown size on a position it must already hold.

Why does the Pyszne sponsored label catch out non-Polish teams?

Because it is a Polish word with Polish grammar. The terms state that while a campaign is active, “Twoja firma zostanie oznaczona na Platformie jako ‘sponsorowana'”, your business will be marked on the platform as sponsored. The form is “sponsorowana”, agreeing with the feminine noun for business, not the English “sponsored” and not the neutral dictionary form either.

A regional team auditing Pyszne listings by scanning for an English label, or even for a Polish stem they half remember, will record every competitor as organic. That single error inverts the conclusion of the entire exercise. It turns a rival’s paid campaign into apparent evidence that your restaurant has slipped, and it produces a remedial plan aimed at a problem that does not exist. Knowing the exact string is not pedantry on this platform, it is the difference between a correct reading and a backwards one.

The problem generalises beyond this one word. Polish is an inflected language, so any label, filter or status string on Pyszne can appear in more than one grammatical form depending on what it is describing. A monitoring rule written as a plain text match against a single form will silently miss the others, and it will miss them consistently rather than randomly, which is the kind of error that never announces itself.

Does the same TopRank campaign behave the same way everywhere?

The mechanics are shared across Just Eat Takeaway’s brands, and the terms are published per market in the local language, which is why the Polish document reads as a translation of the same programme. What is not shared is the local competitive picture. The terms make this concrete with a worked example. If another business in your geographic area is also running TopRank, that business may end up in a better position than you. Where it lands depends on all the ranking parameters applying to both of you at that moment, distance from the specific customer among them.

So a campaign that produced a visible lift in one Polish city can produce nothing in another, with no fault on either side, because the number of local competitors also bidding is a variable neither the platform nor the restaurant controls. The only way to know which of those two situations you are in is to have measured position at the same addresses before the campaign started. Starting the campaign first and looking afterwards produces a number with nothing to compare it against.

Can Pyszne campaigns run without anyone remembering they are on?

Yes, and the terms describe exactly how. A campaign scheduled for a particular day and time is activated recurringly, so a slot chosen once, for example a Monday morning window, repeats every Monday until somebody stops it, and does not apply on days and times that were not selected. Campaigns are managed and stopped through the TopRank interface at any time.

For a chain that is two things at once. It is a spend that continues without a decision being retaken, appearing on invoices as a separate TopRank line. And it is a pattern in the data: a restaurant whose position looks strong on certain weekday mornings and ordinary the rest of the week may simply be looking at its own recurring schedule. Any Pyszne position series that is not timestamped consistently will mix those two states together and produce an average that describes neither.

The fix is to measure at fixed hours rather than whenever someone remembers. A reading taken at noon every day is comparable with the last one. A reading taken whenever a complaint arrives is taken disproportionately during bad moments, which builds a record that looks worse than reality and cannot be used to argue anything. On a platform where paid position is scheduled by the hour, the clock is part of the measurement, not an administrative detail around it.

What should a Pyszne operator record?

The address, the time, the position, and whether anything above the listing carried “sponsorowana”. Because the ranking explanation is contractual and public, a Polish operator is in the strong position of being able to compare observations against a document rather than against a hunch, and that comparison only works with dated readings taken from consistent points.

The parameter the contract cannot help with is whether the restaurant was actually available when the customer looked, since a listing that is not trading is not being ranked badly, it is not being ranked at all. Kitchain (kitchain.co) records the state of the listing alongside its position at each measured point and time, which is what keeps a Pyszne series honest when a slot that looks like a ranking drop turns out to be a closed kitchen. What else we watch on this platform is at https://kitchain.co/aggregators/pyszne/.