Poland built a very large residential installer base during the net metering years, and net metering made the software job easy. One number, the annual kilowatt-hour total, told the customer everything they needed to know. New prosumers are on net billing now, and that single number no longer answers the question. The hour a kilowatt-hour arrives decides what it is worth.
Direct answer. Solar software in Poland splits into six layers: design and simulation, sales and proposal, OSD connection and commissioning documentation, monitoring, CRM and operations, and procurement. The Polish distinctive sits in the proposal layer. Under net billing, surplus sells at a market-linked rate and is bought back at retail, so the proposal has to produce an hourly generation profile matched against the load curve rather than an annual total.
TL;DR
- Six layers, and in Poland the proposal layer carries the weight that design carries elsewhere.
- Net billing replaced net metering for new prosumers, so timing of generation now sets its value.
- Battery attach rates rise under net billing, and sizing depends on the shape of the generation curve.
- Compliance means OSD notification, PN-EN 62446 commissioning tests, and prosumer scheme paperwork.
- Total stack cost runs from roughly 2,000 zl to 145,000 zl a year depending on stage.
What “Solar Software” Actually Means in Poland
Design and simulation. Layout, string sizing, shading, and yield, at latitudes above 50 degrees north where winter shadows run long.
Sales and proposal. Customer-facing savings documents. Under net billing this is the hardest layer in the Polish stack, because the output has to be hourly.
OSD connection and commissioning documentation. Notification to the regional distribution system operator, commissioning tests to PN-EN 62446, and prosumer scheme administration for residential subsidy claims.
Monitoring. Post-commissioning production data, now read alongside consumption rather than on its own.
CRM and operations. Lead handling, survey scheduling, and installer dispatch.
Procurement. Distributor sourcing.
The Polish Solar Software Stack, Layer by Layer
| Layer | Representative tools | Who uses it | Typical cost per year |
|---|---|---|---|
| Design and simulation | PVsyst, SurgePV, PV*SOL, HelioScope | Designers | 2,000 zl to 12,000 zl per seat |
| Sales and proposal | SurgePV, PV*SOL, sector tools | Sales team | 0 zl to 12,000 zl per seat |
| OSD and commissioning documentation | Operator portals plus internal process | Administration | Process cost, not licence |
| Monitoring | Inverter vendor portals | O&M | Usually bundled with hardware |
| CRM and operations | HubSpot, sector CRMs | Everyone | 1,000 zl to 6,500 zl per seat |
| Procurement | Distributor portals | Purchasing | Usually free |
Currency figures use roughly 4.05 zloty to the US dollar, which is illustrative rather than a quote. Most of these platforms bill in euro or dollars, so the zloty cost of the stack moves with the exchange rate as well as with the vendor’s price list.
The Layer That Is Specific to Poland
The Polish compliance layer is real work, but it is not a modelling problem.
A new installation is notified to the regional distribution system operator, the OSD for the area. Commissioning tests follow PN-EN 62446, which sets out what has to be measured and recorded when a system is handed over. Residential subsidy claims run through prosumer scheme administration, with its own forms and evidence requirements.
All three are form-filling and process. They reward a checklist, a document template, and someone who owns the queue. They do not reward a simulation licence. Buying software to solve them is a common misdiagnosis, and it leaves the actual Polish problem untouched.
That problem sits one layer up, in sales and proposal.
Net Billing Rewrote the Proposal Layer
Under net metering, the grid behaved like a store. Energy exported in July came back in January at a defined ratio. Total annual yield was the number that mattered, and everything else was detail.
Net billing removed the store. Surplus is sold at a market-linked rate and bought back later at retail. Those two prices are not the same, and the gap is where the customer’s money goes. A kilowatt-hour consumed inside the house at the moment it is generated is worth full retail. The same kilowatt-hour exported at noon in June is worth whatever the market pays at noon in June, which is when everyone else’s array is also exporting.
So the value of a Polish solar system is no longer set by how much it generates. It is set by when.
That changes what the proposal layer has to produce. An annual kilowatt-hour figure cannot answer the only question that now matters, which is how much of the generation lands inside the household’s load curve. The required output is an hourly generation profile for the full year, matched hour by hour against consumption, with the self-consumed fraction and the exported fraction priced separately.
This is a meaningfully harder calculation than the one Polish sales teams have been running for a decade. Lighter proposal tools do not do it. They were built for the net metering question and they answer it well.
Why the Shading Study Has to Come Before Battery Sizing
Net billing makes storage attractive, because a battery converts an exported kilowatt-hour worth market price into a self-consumed kilowatt-hour worth retail. Attach rates rise for that reason alone.
Battery sizing depends on the shape of the generation curve, not on the annual total. Two roofs producing the same annual yield can need very different batteries. A clean south roof produces a tall midday peak with a large exportable surplus. A partially shaded east and west roof produces a flatter curve with less surplus and a different daily pattern of shortfall.
The sequence matters and it is often run backwards. Sizing storage first, then discovering the shading, produces a battery matched to a generation curve that does not exist. The customer paid for capacity that never fills, or bought too little to catch the surplus that is actually there. Neither error shows up until the second or third month of operation.
Run the shading and yield study first. Then size the battery against the curve the study produced. The extra step costs nothing on site.
Latitude Above 50 Degrees North Changes Where Losses Land
Poland sits high. Warsaw is above 52 degrees north, Gdansk above 54. Winter sun angles are low, so shadows from a chimney, a neighbouring building, or a row in front run much longer than the same obstruction would cast in southern Europe.
Under net metering that mattered less, because a winter loss could be recovered against a summer surplus. Under net billing it cannot. Winter is when household load is highest, when generation is scarcest, and when retail electricity is most valuable. A shadow that costs a small percentage of the annual total can cost a much larger share of the annual value, because it falls precisely on the hours that price best.
An annual loss percentage hides this completely. An hourly model shows it, and shows it in the months where remediation actually pays for itself.
Try the software behind this guide
Quote the hours, not the annual total
SurgePV runs 8,760 hours of shading and yield so you can match generation against the load curve before you size a battery under net billing, then exports the drawings from the same file.
Book a free SurgePV demo →No credit card. 20-minute walkthrough on one of your own projects.
What Stack You Need at Your Size
Residential installer, under 200 systems a year. Two to three layers. An hourly design and proposal tool that can model self-consumption against a load profile, plus a CRM. The hourly capability is not optional here, because it is the whole basis of the sale.
Residential with storage as a standard offer. Three to four layers, with the shading and yield study formalised as a step that precedes battery sizing rather than following it.
Commercial rooftop. Four to five layers. Commercial load curves are flatter and better matched to generation than household curves, which changes the storage answer and often improves the project.
Large commercial and utility-scale. Six layers with PVsyst as the engine of record, and hourly market-linked pricing as a development input rather than a sales detail.
Pricing the Whole Stack in Zloty
| Company stage | Layers | Realistic annual software spend |
|---|---|---|
| Residential under 200 systems | 2 to 3 | 2,000 zl to 16,000 zl |
| Residential with storage | 3 to 4 | 16,000 zl to 45,000 zl |
| Commercial rooftop | 4 to 5 | 45,000 zl to 90,000 zl |
| Large commercial and utility-scale | 6 plus | 145,000 zl upward |
Figures convert at roughly 4.05 zloty to the dollar and are illustrative. Per-platform detail is in our solar design software pricing breakdown.
What Most Polish Installers Get Wrong
They still quote a single annual figure.
The habit is inherited, and it was correct for years. Under net metering, one annual kilowatt-hour number or one annual shading loss percentage described the economics accurately. Under net billing the same number is close to meaningless, because it averages across hours whose value now differs by a factor of several.
Here is the concrete failure. A proposal reports a 6 percent annual shading loss. The customer accepts it as small. But that 6 percent is not distributed evenly. Most of it falls in the low-sun months, in the mornings and late afternoons, on the hours the household is at home and drawing at retail price. The same 6 percent, if it fell at noon in June when the surplus was going to be exported at a market rate anyway, would cost a fraction as much. The single percentage cannot tell those two cases apart, so the customer cannot tell which hours they are losing, and neither can the person selling to them.
The opinionated version: in Poland the proposal layer is now more important than the design layer. A rigorous simulation reported as an annual total is worth less than a decent simulation reported hour by hour. The number was never the deliverable. The profile is.
Fix it by changing the output, not the tool set. Report generation and losses by month and by hour block, show the self-consumed and exported fractions separately, and price them separately. The site survey does not change.
When Software Is Not the Answer
If the roof cannot carry the array, or the mounting cannot take Polish snow and wind loading, no amount of hourly modelling helps.
Our solar civil and structural engineering team produces snow, wind, and ballast assessments delivered as STAAD Pro report calculations, with solar rooftop detailed engineering design for the construction pack. See the sample design pack or talk to our team.
Conclusion
- Quote hours, not annual totals. Net billing prices generation by when it arrives, so the profile is the deliverable.
- Run shading before sizing storage. A battery matched to the wrong curve is capacity the customer paid for and cannot use.
- Treat compliance as process. OSD notification and PN-EN 62446 commissioning need a checklist and an owner, not a licence.
In this country series: best solar design software in Poland, best solar proposal software in Poland, shading analysis software in Poland, Pvsyst review. Tool deep dives: Helioscope review, Aurora Solar review.
More from our network
Disclosure and accuracy note
Commercial relationship. Heaven Designs and SurgePV are part of the same group. Treat our recommendation of SurgePV as a vendor making its own case, not an independent verdict. We have tried to describe every other product fairly, and to say plainly where a competitor is the better choice.
Pricing. All prices are indicative, compiled from public sources when this page was written. They vary by tier, region, contract term and exchange rate, and change without notice. Several vendors quote rather than publish, and some price in currencies other than the US dollar, so a converted figure moves with the exchange rate. Confirm current pricing with the vendor before you decide anything.
Trademarks and corrections. All product names and trademarks belong to their respective owners, and are used here for identification and comparison only. Their use does not imply affiliation with or endorsement by those companies. If anything here is out of date or wrong, tell us and we will correct it.
FAQ
What is solar software? An umbrella term for six categories: design and simulation, sales and proposal, connection and commissioning documentation, monitoring, CRM and operations, and procurement. In Poland the proposal layer carries the most weight.
What changed when Poland moved to net billing? Surplus is now sold at a market-linked rate and bought back at retail instead of being netted off. That makes the timing of generation decisive, so an annual kilowatt-hour total no longer describes the economics.
How much does solar software cost in Poland? Roughly 2,000 zl to 16,000 zl a year for a small residential installer, and 45,000 zl to 90,000 zl for a commercial rooftop business. Figures convert at about 4.05 zloty to the dollar and are illustrative.
Do I need hourly modelling for residential work? Yes, under net billing. The self-consumed fraction and the exported fraction carry different prices, and only an hourly profile matched against the load curve separates them.
Should I size the battery before or after the shading study? After. Battery sizing depends on the shape of the generation curve, and the shading study is what produces that shape. Sizing first means matching storage to a curve that does not exist.
Does OSD notification or PN-EN 62446 require specific software? No. Connection notification and commissioning testing are process and documentation obligations. They need templates, records, and a person who owns the queue, not a simulation platform.
Related: the design layer in depth is in best solar design software in Poland, the sales layer in best solar proposal software in Poland, and shading specifically in best solar shading analysis software in Poland.
