← Back to Feed

Poland Just Made 65,000 Airbnb Hosts Get a License. Every European Hotel Market Is Watching.

Poland's new short-term rental registry forces every Airbnb-style operator to register, display an ID number, and meet fire and safety standards... or face fines up to €11,600. If you're an independent hotel operator who's been competing against unregulated apartments, the question is whether this actually levels the playing field or just adds paperwork to a problem that needed enforcement.

Poland Just Made 65,000 Airbnb Hosts Get a License. Every European Hotel Market Is Watching.

So here's what actually happened. Poland drafted legislation that reclassifies any rental under 30 days as a hotel service. That means roughly 65,000 short-term rental apartments... many of which have been operating with zero oversight, zero fire safety compliance, and zero tax accountability... now need to register with a national database called CWTON, get a unique ID number, and display that number on every listing. Platforms like Airbnb and Booking.com aren't just passive middlemen anymore. They're required to verify registration numbers and share monthly data with authorities. Fines for non-compliance hit up to PLN 50,000 (about €11,600). And here's the part that matters most for hotels: local municipalities can now designate zones where short-term rentals are restricted or banned entirely.

This isn't Poland inventing something new. It's Poland catching up to EU Regulation 2024/1028, which went into effect May 20, 2026. But Poland still hasn't finalized its national implementation legislation (the draft is called UC135, with a proposed transition deadline of October 1, 2026), which means right now there's a grey zone where nobody... operators, platforms, local authorities... knows exactly what's enforceable. The estimated grey market is 30-35% of the sector. That's roughly 20,000 apartments operating completely off the books. The question isn't whether regulation is coming. It's whether the enforcement infrastructure actually exists to make it mean something.

Look, I've been in technology evaluation meetings where someone presents a beautiful compliance dashboard and I ask "okay, but who's checking the data?" That's the fundamental issue with every STR registry I've seen proposed or implemented. The technology to build the database is trivial. I could build CWTON in a weekend (I'm not even exaggerating... it's a registration form, a unique ID generator, and an API for platforms to query). The hard part is enforcement. Who verifies that the apartment listed as "fire-safety compliant" actually has a working smoke detector? Who checks that the operator displaying registration number PL-47291 on their Airbnb listing is the same person who registered that number? Who follows up when a property gets three noise complaints and should be removed from the registry? If the answer is "local authorities," then you need to ask what local authorities' technology stack looks like and how many staff they have dedicated to this. In most European municipalities, that answer is "not enough."

The platform accountability piece is actually the most interesting part of this architecturally. Requiring Airbnb and Booking.com to verify registration numbers before allowing listings to go live... that's pushing compliance enforcement upstream to entities that actually have the technical infrastructure to do it. It's smart. But it only works if the platforms cooperate meaningfully, and their track record on that across Europe is mixed at best. Airbnb has historically preferred to negotiate city-by-city, delay implementation, and argue about data-sharing scope. Monthly data reporting to authorities is a significant operational change for platforms, and I'd want to see the actual API specification and data schema before I believed it was anything more than a PDF export someone runs manually.

For hotel operators competing against unregulated STRs... this is directionally good but operationally uncertain. The 30-35% grey market isn't going to disappear because a law passed. It'll shrink, maybe significantly, but enforcement determines the actual competitive impact. What I'd watch is whether municipalities actually use the zoning powers they're being given. That's the real lever. A registration requirement raises the cost of operating an STR. A zoning restriction removes supply from the market entirely. Those are very different outcomes for your comp set.

Operator's Take

Here's what I'd tell any operator running a hotel in a European market right now. Poland is one domino. The EU regulation applies to every member state, and each one is building its own version of this registry. If you're competing against STR supply in your market... and if you're in any urban European market, you are... start tracking what your local municipality is doing with zoning authority. That's the number that moves your RevPAR, not the registry itself. Build a simple tracker: how many active STR listings in your comp set radius today, and check it quarterly as enforcement kicks in. If supply actually shrinks, you've got rate power you didn't have before. Don't wait to see it in the data... have the conversation with your revenue manager now about what your pricing strategy looks like if 15-20% of nearby STR inventory goes dark. That's a real scenario. Plan for it.

— Mike Storm, Founder & Editor
Source: Google News: Airbnb
📊 Hotel tax accountability 🏢 Airbnb 🏢 Booking.com 📊 EU Regulation 2024/1028 📊 Hotel fire and safety compliance 🌍 Poland hotel market 📊 Short-term rental regulation
The views, analysis, and opinions expressed in this article are those of the author and do not necessarily reflect the official position of InnBrief. InnBrief provides hospitality industry intelligence and commentary for informational purposes only. Readers should conduct their own due diligence before making business decisions based on any content published here.