Tourist Cheque stays cannot go through Booking.com: a direct room calendar
Warmia-Masuria Tourist Cheque: 300 zł, two nights minimum, booking only with the property. The list is due in mid-September; first round 29 September. A guesthouse without its own calendar cannot take the code.
On 24 August 2026 the Warmia-Masuria Regional Tourism Organisation set out the regional Tourist Cheque: a 300 zł electronic code, a stay of at least two nights, and a booking made only directly with the property. On 26 August Bankier.pl reported the same rules and three application rounds, with the first round planned for 29 September. The list of participating properties is due in mid-September. For a guesthouse that sells almost every room through an online travel agency, the programme does not start with marketing. It starts with a practical question: where does the guest actually enter the code, if the intermediary is excluded.
The Ministry of Sport and Tourism announced the scheme on 28 May 2026: 6 million zł gross, one-off electronic codes, people aged 60+ and Large Family Card holders, bookings made by participants themselves at participating properties. The Warmia-Masuria edition adds the amount, the round dates and — this is the operational core — a ban on using popular online booking intermediaries. A hotel and guesthouse reservation system is no longer “a website with a calendar”. It is the only place where the subsidy can be accepted, the room blocked, and the same dates not sold twice.
Tourist Cheque rules a property needs before the list is published
The ministry programme is a pilot in four voivodeships: Lublin, Subcarpathia, Podlaskie and Warmia-Masuria. Bankier reports a pool of 1.5 million zł for each. The ministry’s stated aim is to support regions that have seen fewer visitors because of the geopolitical situation, and to encourage trips after the summer peak. The subsidy covers a defined hotel service, in a defined window, at properties on the organiser’s list — and for now only in four voivodeships.
In Warmia-Masuria the grant agreement was signed on 13 August 2026. The task is worth 4.028 million zł, of which 1.5 million zł comes from the ministry. The cheque is worth 300 zł and takes the form of an individual code tied to the participant. It may be used for one reservation of at least two nights, only at a programme property and only in the round in which the code was generated. Each participant receives one cheque for the whole programme. A code that expires does not roll into the next round. A guest who generates it “just in case” and then finds no rooms loses the subsidy and does not get a second code.
The May ministry notice spoke of a value from 300 to 600 zł. The Warmia-Masuria edition, according to W-M ROT and Bankier, sets 300 zł. Do not mix those figures on the rate sheet or on the website. A guest who read a national summary and expects 600 zł, then hears 300 zł at reception, leaves a review before anyone explains the difference between the ministry pilot and the regional rules. Until the regulations appear — promised for early September, with the property list in mid-month — a property can prepare the workflow. It should not promise an amount taken from a headline.
W-M ROT names three eligible groups: people aged 60 on the day the code is generated, adult holders of a valid Large Family Card, and — only in this regional edition — an open group of adult Polish citizens, funded by the organisation without the ministry grant. Farm-stay properties, ROT has said, are not excluded in advance; the conditions will follow from the regulations. A property that does not yet know whether it will be listed still needs a direct-booking channel. Without one there is nothing to apply with.
The Warmia-Masuria dates are still planned. The organiser says they may change, and that current dates will be published on the programme site:
- first round: applications 29 September 2026, stays 30 September to 18 October
- second round: applications 19 October, stays 20 October to 8 November
- third round: applications 9 November, stays 10 to 30 November
- property list: mid-September; regulations for guests and for properties — from early September
Bankier recalls that the previous Warmia-Masuria tourist-voucher round was cancelled after a login-system error. Users could see other people’s data — names, email addresses, phone numbers, places of residence — and in some cases download or generate a voucher assigned to someone else. That is a fact from the last edition, not a rumour about the new one. For a property it yields one conclusion that does not depend on who writes the application portal this time: copies of ID documents, scans of the Large Family Card and guest phone numbers should not travel by email between reception, the bookkeeper and the owner “just in case”. GDPR does not start at the office. It starts in the inbox into which someone dropped a scan because it seemed easier for settling the cheque.
Direct booking: phone, email or a form, not an intermediary portal
W-M ROT describes the sequence plainly. After generating the code, the visitor contacts the chosen property. The booking may be made by phone, email or a contact form provided by the property. The cheque may not be used when booking through popular online intermediaries that sell accommodation. The May ministry notice said the same more briefly: participants book by themselves, directly at participating properties.
That shuts the path through which most guests from outside the county now arrive. A portal shows availability, takes a deposit and sends a voucher with a booking number. Reception scans a code from a phone and need not know how the guest found the house. For the Tourist Cheque that path is closed. The guest holds a subsidy code and must reach someone who, at that moment, can see a free room for two nights inside the round window. If the only “truth about a free room” is the calendar in the intermediary’s extranet, the person answering the phone is guessing. They either promise a room that disappears an hour later in a portal booking, or they refuse while the room is empty because nobody took it off sale.
The channel is not a detail. A phone call at the peak of Saturday check-out loses dates, headcount, the code, diet and an extra bed. Email leaves a trail, but in the owner’s private inbox it drowns between spam and the electricity bill. A form on the property’s site works only if someone reads it and replies before the guest generates a code and wastes the round. Your own online reservation system does not replace the cheque-application portal — that stays with the organiser. It does give a place where the guest picks dates, leaves the data needed for check-in and receives a confirmation before the code is tied to a specific stay.
Not every property needs online payment to take part. The programme requires a direct booking, not an online shop. A four-room guesthouse where the owner answers the phone and immediately marks a square in a notebook meets the channel test, provided the notebook is the only calendar and nobody is selling the same dates through a portal in parallel. The problem starts where there are several channels and the person on the phone cannot see them in one view. Then the Tourist Cheque does not “fail because of the office”. It fails because the property cannot tell the guest within a few minutes: yes, those two nights are free, we take the code, we take the room off the other channels.
What to record against a code before the property regulations appear
The regulations for properties are due in September. Until then we do not know the settlement form, the list of attachments, or whether the code is entered in a ROT system or only in the property’s own records. From the published description one can still derive a minimum set without which any later settlement will fall apart. The code is individual. There is one reservation. The stay is at least two nights. The dates must sit inside the round window. The property must be on the list. A participant may hold only one cheque. That implies a register that a spreadsheet with an “notes” column usually cannot carry when several codes arrive on one weekend and one date is wrong.
A guesthouse with a dozen rooms, for example, will take first-round guests who call on 29 September with a code for a stay from 30 September. Reception has to bring together: the code, the name from an identity document, arrival and departure dates, the room number, the booking source (“cheque”, not the portal), and confirmation that the room has come off other channels. If that information lives in a notebook, an email and a note on a booking in the intermediary’s extranet, after two weeks nobody can reconstruct which code was used and which guest never arrived. An empty night after a promised arrival already costs linen, cleaning and a lost weekend. With a cheque there is the extra risk that the organiser will ask about a code the property cannot link to a registration card.
We are not inventing fields the regulations have not announced. We do not assume the property must collect a PESEL number, a scan of the Large Family Card or a declaration of age — the published notices do not say so. Eligibility checks, according to the ministry and ROT, sit with the system that generates the code. The property accepts the code and provides the stay. The fewer spare copies of personal data are created “just in case”, the smaller the surface for a leak if another portal fails. GDPR in web applications also applies to the panel where reception records a booking: who can see the guest’s phone number, how long it is kept, and whether a copy goes by email to the bookkeeper without a need.
Settlement with the organiser will have its own form. The ministry competition pack includes a report on the public task — that is a document on the operator’s side, not the hotel’s. A property should still be able, in October and November, to answer three questions: how many codes were accepted, for which stays, and whether each stay met the two-night rule and the round window. If the answer means digging through a mailbox, the programme ends as a manual spreadsheet on Sunday evening. If a booking has a source flag and a code field, the report is a filter, not a research project.
A room calendar that sees the portal, the phone and the cheque together
In a small property the channel clash looks trivial and is therefore dangerous. The portal keeps October open because the season is ending and it seems a waste to close dates. A guest with a code calls for two nights from Friday. Reception confirms. An hour later a portal booking arrives for the same room on the same Friday. One of the two people will be told that “the system got out of sync”. With the Tourist Cheque that error has an extra cost: the code is one-off and bound to a round. A guest whose stay you cancel may not find another listed property before the window closes.
Accepting a code therefore does not end with writing the guest into a notebook. It ends with taking those dates off the other channels. Where a property already has a channel manager or iCal sync with a portal, that means a block in the source calendar, not a sticky note on the monitor. Where the portal calendar is updated “when someone remembers in the evening”, the Tourist Cheque forces a different discipline: the direct booking must live in the same tool that publishes availability. Otherwise weekend shifts end in closing rooms by hand in three panels.
The two-night rule also has to be enforced in the calendar, not in someone’s head. A guest with a code who wants one night “because we are driving on” does not meet the programme condition. Reception that accepts such a stay in good faith risks a subsidy that will not clear, while the room is occupied anyway. Conversely, three nights inside the round window meet the minimum, provided the whole stay sits inside the round. The planned Warmia-Masuria windows are short — the first round is under three weeks. A stay that arrives on 17 October and leaves on 20 October cuts across two windows. Whether that stay can be settled at all will be in the regulations. Until they appear, it is safer to keep cheque bookings inside a single round, not on its edge.
The calendar must also tell a cheque booking from an ordinary direct booking and from the portal. Otherwise, after the season, nobody can count how much subsidy actually reached the till and how much was simply a quiet October. That figure will matter when the property decides whether to stand on the list again and hold rooms for direct booking. On 20 August 2026 W-M.pl reported a conference in Białystok: deputy minister Ireneusz Raś said work would start on the possibility of running the Tourist Cheque systematically nationwide in 2027. There is no decision yet; it depends on the Sejm budget and on the results of this year’s pilot.
A lower price on your own site after the ban on parity clauses
The Tourist Cheque coincides with another, already binding legal position. On 14 November 2024 the European Commission confirmed that Booking Holdings, as a gatekeeper, must apply the Digital Markets Act to Booking.com. Parity clauses are prohibited. Hotels, car-rental firms and other travel providers may offer different — including better — prices and conditions on their own website or another channel than on Booking.com. The platform may not, in response, raise commission or delist an offer because the business showed a different price elsewhere. It must also give business users access to data that they and their customers generate on the platform.
The obligation follows from Regulation 2022/1925 and has applied to Booking.com since November 2024. Earlier, on 19 September 2024, the Court of Justice of the European Union in case C-264/23 held that parity clauses — wide and narrow — in contracts between reservation platforms and properties do not fall outside Article 101(1) TFEU as “ancillary restraints”. In other words: a property that shows a lower price on its own site, or a breakfast package not available through the intermediary, does not breach the mere fact of being listed. It may still breach its own current contract — that document has to be read. DMA and the CJEU judgment do, however, remove the old automatic rule that “it cannot be dearer on the intermediary, so it cannot be cheaper with us”.
On 26 August 2026 Law.com reported that the value of European antitrust claims against Booking had risen above €4.5 billion and was set to grow; the opening sentence named parity clauses and commission rates. That is a report of damages litigation, not a new duty on a Polish guesthouse. It does not decide whether a given Polish property will recover anything, or when. For reception, the live point is what is already lawful on the direct channel: showing a guest with a Tourist Cheque the stay price after the subsidy, without pulling that transaction onto a portal that cannot process it anyway. A site that can book two nights and take a code stops being a brochure. It becomes the only till that can legally cash this subsidy.
When a notebook is enough, when a ready-made programme is, and when a dedicated panel is
A three-room property where the owner answers every call and does not sell the same dates through a portal in parallel can get through three rounds on paper or in a spreadsheet. The condition is strict: one calendar, updated at once, with the code and the dates noted. If in October the owner is away and family covers the desk, the notebook stops being a tool. It becomes a source of mistakes. Then a simple shared calendar — even without online payment — is cheaper than one double booking on a long weekend.
A ready-made hotel programme or channel manager makes sense when the property already runs on it and the calendar truly drives availability on the portals. Many such systems allow a manual booking, a source flag and a note. If you can store the code there, enforce two nights and take the room off the OTA in one step, there is no reason to buy a separate application “for the cheque”. The Tourist Cheque runs from September to November. It does not justify replacing a whole PMS in August. It does justify checking whether the current tool can accept a booking that never appeared in the intermediary channel.
There are cases where a ready-made product stops being enough. Several buildings with separate calendars; a site on which the guest should pick a room and pay a deposit; breakfast packages settled differently from the room itself; invoices for companies after KSeF; an export of codes for the organiser in a format the PMS does not provide. A ready-made programme can then cost more than a fit, because the property starts bending the process around licence limits: the code in a notes field, two-night stays watched on paper, the OTA block done by hand an hour later. Integrating the existing calendar with a simple form on your own domain is often enough. A dedicated panel appears only when that stack is already three tools and one person who remembers how to wire them.
We do not replace the official cheque-generation system. We do not replace the intermediary’s extranet. We do not claim that your own site will “throw Booking out of the property”. The portal still brings guests who have never heard of the Tourist Cheque. The point is that a booking the portal is not allowed to handle has somewhere to land before you sell the room to someone else.
A reservation panel that takes the code and takes the room off the other channels
GESOFT builds web applications and panels for firms, including reservation calendars for lodging. We do not sell a “Tourist Cheque module” as a boxed product. If, after mapping the flow, a field in the current PMS and discipline on the phone are enough, that is what should be done. If the property needs, on its own domain, a room calendar, a booking source, a code field and a date block, that can be designed around the process rather than the other way round.
The frictions described above yield a short list of functions, not a catalogue of everything a hotel system sometimes contains. A calendar per room or unit, from which reception can see occupancy across the two or three weeks of a round. A booking with a source: portal, phone, email, form, cheque. A code field and a check that the stay is at least two nights in one window. A date block which — if the property uses iCal or a channel manager — reaches the other channels, instead of staying in the duty manager’s head. A list of cheque bookings for settlement, with dates and status (confirmed, arrived, no-show, cancelled). Guest data limited to what check-in and any settlement rules require, with restricted access.
There is also something that meets the Tourist Cheque only on the calendar: from 1 October 2026 businesses entered in CEIDG before 2025 must have an e-Delivery address, unless they obtained one earlier when updating their entry. Biznes.gov.pl states that date outright. Most small guesthouses are sole traders. Correspondence from the marshal’s office, the tax office or the sanitary inspectorate will not wait for the reception notebook. The e-Delivery inbox remains the official inbox — a reservation panel does not replace it. The panel can, however, keep a simple register of matters next to the calendar (deadline, subject, who replied), so a letter about an inspection is not lost in the owner’s private mail on the weekend when the second cheque round begins.
If a similar flow — several sales channels, subsidy codes, short windows and a person who is not always at the same computer — is today a notebook and an extranet, the first step is to write down which piece of information must be unique. Only then is it clear whether an integration, a field in a ready-made programme, or a separate contact about a calendar on your own domain is the right next move.
Describe your project