Since 11 July 2025, a Polish developer no longer decides whether to show flat prices. An amendment to the developer act, known as the price transparency act, requires publishing them on the developer's own website and reporting them daily to the state portal dane.gov.pl. Since 11 September 2025 this also applies to developments whose sales started earlier - which today means practically all of them.
The rule sounds simple, but in practice many developers meet it only partly. The consumer protection office (UOKiK) has received over 1,500 reports of irregularities, and its president has sent 39 formal requests to developers - most often about missing prices of parking spaces and storage units, or missing price history. In this article we break the duty down: who it applies to, what exactly must be on the website, how to show prices clearly, how daily reporting works, which mistakes keep recurring, and how to implement it so nobody has to watch it by hand seven days a week.
Short answer: a developer must run its own website and publish on it, from the day sales start, the price per square metre and the total price of every flat and house on offer, prices of parking spaces, storage units and other adjoining premises, other payments the buyer has to make, and the price history - all gross. The same data goes to dane.gov.pl every day, even without changes. Breaches can end in a UOKiK fine of up to 10% of annual turnover.
Kluczowe wnioski
- Prices must be published on the developer's own website - a portal or an agent is not enough.
- The duty covers price per square metre, total price, parking, storage, other payments and price history, all gross.
- The data goes to dane.gov.pl every day, even when nothing has changed.
- It is safest when the website and the report draw on one data source rather than manual retyping.
Who the duty applies to, and since when
The duty applies to developers as defined in the developer act, meaning companies selling new-build flats and single-family houses. There are two dates:
- 11 July 2025 - for new development projects.
- 11 September 2025 - for developments whose sales were already under way.
Three things are often missed. First, prices must be on the developer's own website - publishing only on a listing portal or through an agent does not meet the duty. Second, the website must be live from the day sales start, and if you sign reservation agreements earlier, before the first of them. Third, the duty does not end with the website: the same data has to be reported to the minister of digital affairs every day.
What must be on the website
- Price per square metre of usable floor area for every flat and house on offer.
- The total price of every unit and house.
- Prices of adjoining premises and rights: parking spaces, garages, storage units.
- Other payments the buyer must make to the developer.
- Price history with the dates of changes.
- All prices gross, including VAT.
- The general part of the information prospectus, contact details and the development's location.
The act does not prescribe the site's design, but it requires this information to be published. If a price is visible only after leaving an email address, or in a file you have to stumble upon, it is hard to call that publication in the spirit of the rules.
How to show prices: lawfully and clearly
The simplest solution that meets the duty and helps sell at the same time is a table or unit finder in which every flat shows:
- the total price and the price per square metre - both, because buyers compare developments in both terms;
- the unit's status - available, reserved, sold;
- related parking spaces and storage units with prices, or clear information that they are bought separately and what they cost;
- the price history - for example an expandable list of changes with dates next to the unit, not a separate document nobody finds;
- other payments the buyer has to make to the developer, shown with the unit or in one easy-to-find place.
Consistency is key. The price on the website should be the same price the sales office, the listing portal and the file sent to dane.gov.pl give. A mismatch between them is the easiest route to a complaint, and dane.gov.pl data is public - buyers, journalists and competitors compare it.
Daily reporting to dane.gov.pl
The second part of the duty is reporting price data to the minister of digital affairs every day. It ends up in a public dataset on dane.gov.pl. In practice it works like this:
1. You register a data source. The request to create a data source for a development is sent to kontakt@dane.gov.pl. 2. You publish a file at a permanent address. The portal automatically downloads the data from a file you host on your server. The file's structure is described in the Ministry of Digital Affairs' instructions, and the portal provides a ready template. The instructions do get updated, so check the current version on dane.gov.pl before you start. 3. You update the data every day, seven days a week - even when no price has changed.
The practical conclusion: the dane.gov.pl file and the prices on the website should come from one source, such as the sales system or the unit database that feeds the website. Retyping prices in two places sooner or later ends in a mismatch - usually on a Friday evening, when someone changed a price at the sales office and the file waits until Monday.
The most common mistakes
Do
- Price per square metre and total price for every unit, in a table or unit finder
- Parking spaces and storage units with prices, shown next to the flats
- Price history next to the unit, with the dates of changes
- The same data on the website, at the sales office, on portals and in dane.gov.pl
Avoid
- Prices only on a listing portal or with an agent
- A price list hidden in a download or behind a contact form
- Token prices such as 1 zloty instead of real ones
- A dane.gov.pl file updated only on working days
Token prices deserve a separate word. Some developers entered, for example, 1 zloty instead of real prices. UOKiK points out that the average consumer knows nobody sells flats for one zloty, so it is hard to treat that as bait advertising - but such a price tells the buyer nothing and invites the charge that the duty to publish was not met. It is safer simply to show the price.
What a breach can cost
Failing to meet the act's duties is a practice infringing collective consumer interests. The president of UOKiK can impose a fine of up to 10% of the previous year's turnover, even when the breach was unintentional. The office does not just wait for complaints - it analyses developers' websites and sends formal requests, and buyers even have websites for reporting missing public prices.
The fine is one thing; trust is another. A buyer who cannot find the price of a storage unit, or sees a different price than at the sales office, starts wondering what else in the offer does not add up.
Who in the company is responsible
In practice price transparency is a process, not a one-off change to the website. It works when a few things are clearly settled:
- One person owns the price list - usually the head of sales. They approve price changes, not everyone who has access to the website.
- Every price change starts in one place and only from there reaches the website, the report and the sales office.
- Someone checks every day that the report has updated. Automation that quietly stopped working is worse than none, because it gives a false sense of security.
- The price history is protected when the website changes. When rebuilding the site or switching agencies, it is easy to lose the history of price changes since sales began. Before switching the old site off, make sure the history has been carried over.
How to implement it: three routes
| Route | When it makes sense | Risk |
|---|---|---|
| Manual: a table on the site and a file updated by hand | one small development, rare price changes | daily work seven days a week and mismatches with every change |
| A ready-made service for dane.gov.pl reporting | the site already shows prices well; only the report is needed | a second database to watch; the site and the report can drift apart |
| Integration: site and report from one data source | several developments, frequent price changes, a sales system | a higher one-off implementation cost |
Whatever the route, the key rule is the same: prices are entered in one place, and the website, the report and the sales materials all use it. How to build a development website with a unit finder, and what it costs, is covered in A website for a property developer.
Price transparency is also a sales argument
Since every developer has to show prices, the advantage is no longer hiding them but clarity. The offer that wins is the one where buyers immediately see the full cost - flat, parking space, storage unit - and can compare units easily. An honest price history helps too: it shows the price does not depend on who is asking. How to use this in a campaign is covered in property development marketing.
Frequently asked questions
Does the duty apply to developments whose sales started before 11 July 2025?
Yes. For those developments the rules provided a two-month transition period, which ended on 11 September 2025. Since then the duty has applied to every development on sale.
Is publishing prices on a listing portal enough?
No. The act requires the developer to run its own website and publish prices there. Portals can show the same prices, but they do not replace the developer's own site.
Do I have to show price history?
Yes. The website should show the history of price changes with dates, so buyers can see how a unit's price has changed since sales began.
Should prices be net or gross?
Gross, including VAT - as the buyer will pay them.
Do I have to report to dane.gov.pl if prices have not changed?
Yes. Data is reported every day, seven days a week, whether or not anything changed.
This article sets out the duties and practice but is not legal advice - in an unusual situation, such as sales through a special purpose vehicle or unusual adjoining premises, it is worth consulting a lawyer.
Summary
Price transparency means two duties: full, clear prices on your own website from the day sales start, and the same data reported daily to dane.gov.pl. Most often, prices of parking spaces and storage units and the price history are missing, and manual retyping of data in several places causes the most problems. One source of prices for the website, the report and the sales office solves most of them.
If you want the prices on your website and the dane.gov.pl data to come from one place, write to us.