The Cheapest $/Wp Quote Is Usually the Least Honest Number on the Page

The cheapest dollar-per-watt number on a PV module quote is usually the least comparable number on the page. Not always the least honest — though I've seen that too — but almost always the least comparable. If two quotes sit at different points on that metric, you're not looking at two prices. You're looking at two different scopes that happen to share a unit.

I should say who's writing this. I'm a procurement manager at a 90-person solar EPC contractor. I've owned the module line in our budget — roughly $14 million a year across utility-scale and commercial jobs — for four years, and I've negotiated with more than 30 photovoltaic module manufacturers and suppliers in that time. Every PO goes into a tracking sheet my team built in 2021 after a job that didn't go well. I'm not the technical guy on our team. I don't do the electrical design. But I sign the number, and I'm the one who finds out six months later whether it was real.

From the Outside, the Low Quote Looks Like the Safer Budget Line

People assume a lower quote means the supplier is running a leaner operation. Sometimes that's exactly what it means. What they don't see is which costs got moved off the quoted figure and parked somewhere else — in the contract, in the shipping schedule, or on your own receiving dock.

Three places it happens most often in module procurement:

Tiering inside a model name. Two shipments carry the same model number and the same headline wattage. The bill of materials isn't the same. Frame wall thickness, junction box rating, backsheet supplier, whether the encapsulant is a named brand or a local film — none of that shows up in a $/Wp figure. It shows up in the accelerated aging data. Or in year eight.

Certification scope. IEC 61215-1:2021 covers design qualification and type approval. It tests a representative sample of a design, once. It does not certify the module sitting in the container you received this morning. People treat "IEC certified" as a per-unit guarantee. It isn't. It's a statement about a design, and the distance between that design and the batch on your dock is the whole ballgame.

What's excluded. Shipping terms, duty, inland freight, payment terms, and whether the freight quote was a booking or an estimate. That's not a niche issue. On a few quotes I've reviewed, it was most of the difference.

None of this means a low quote is a trick. Some of the sharpest prices I've signed came from suppliers who simply had a better utilization rate that quarter. But you can't tell which is which from the $/Wp cell in a spreadsheet.

The Question Everyone Asks, and the One That Actually Saves Money

Most buyers ask, "What's your best price?" The question I've learned to ask first is: "Which test reports ship with the delivery, and what production batch do they cover?"

That single question separates a photovoltaic module manufacturer from a photovoltaic module supplier faster than any site visit. A manufacturer answers it with documents. A trading desk answers it with a story.

Here's the technical bit, and I had to learn it from our engineers: photovoltaic module testing in production is not the same thing as type-approval testing. IEC 61215-2:2021 lays out the qualification test sequence for the design. IEC 60904-1:2020 defines how the current-voltage curve gets measured. IEC 61730 covers safety construction and testing. What none of those standards do is guarantee that every module in your delivery got a flash test and an electroluminescence image that someone actually looked at.

Good factories do it anyway. They run inline flash testing against STC, generate EL images per serial number, and archive both against the module ID. Mediocre factories have the capability and skip the archive. When I ask for serialized EL images from the specific batch we're buying, I'm not only checking quality. I'm checking whether the process is boring enough to be reliable.

The warranty climbs the same ladder. A 25-year performance warranty with a degradation curve means nothing until you know who administers it, whether it's backed by an entity that will still exist in year 15, and whether replacement logistics are described in the contract or just in the brochure. That's the difference between a warranty and a wish. It doesn't appear anywhere in $/Wp.

The Part That Genuinely Surprised Me

Never expected the "expensive" quote to win on total cost. Turns out it wasn't winning on modules by much — it was winning on everything downstream.

In Q3 2024 we shortlisted four photovoltaic module manufacturers for a 12 MW commercial portfolio. On sticker price the spread was wide enough that finance had basically circled the cheapest one. Then we ran the numbers the way our operations team actually experiences them: incoming inspection hours, the re-testing we'd do on a batch with no archived EL data, the risk of a mid-project model change, and the working capital cost of a payment schedule that wanted 40% up front.

The cheapest quote stopped being the cheapest somewhere around the third line item. We went with a different supplier and the total landed cost in our model came in roughly 6% under the low bid — not because the modules were cheaper, but because we stopped paying for surprises.

The related lesson was about where the quote came from. When we compared a photovoltaic module production line factory against a distributor on the same job, the factory's numbers were auditable in a way the distributor's weren't. Not because distributors are dishonest — most are working from a thinner file. But a factory can let you walk the line, watch the laminator, and see where the EL station sits. An office can show you a slide.

We applied that lens to every bid after that, including SolarBridge Supply. On that sheet they weren't the lowest $/Wp — I think they were second. What put them on the shortlist for later jobs was that every line in their quote traced back to a document I could check: test reports tied to a batch, exclusions listed on the front page, freight modeled rather than estimated. That's boring. Boring is what I'm buying now.

The Fair Objection: Transparency Makes You Look Expensive

Here's the pushback, and it's real. If you itemize everything, your total looks higher than a competitor's compressed number, and someone in finance picks the lower line. I've lost that fight twice. I'd argue it's a problem with how we compare quotes rather than how they're written, but I'm not going to pretend it doesn't cost you deals.

Then again — a quote you can't compare isn't a price. It's a placeholder. The cost hasn't gone away. It's been scheduled for later, and later usually means change orders, expedited freight, or a project manager explaining why the budget moved.

What I'd say to any supplier reading this: I'm not asking you to be the cheapest, and I'm not asking you to list everything you're bad at. I'm asking for a scope sheet I can read in five minutes that tells me what's in, what's out, and where the line is. The suppliers who do that get called back. The ones who send a number and a smile get compared on price alone, which isn't a game most of them win twice.

A related thing, less central: if the datasheet throws around terms like "low-carbon" or "recyclable packaging," those claims need substantiation in the US market. The FTC Green Guides (16 CFR Part 260) require it. I've started flagging unsubstantiated environmental claims as a signal about how the rest of the document was assembled. Harsh? Maybe. But the same rigor tends to be missing everywhere else, and I'd rather find out now than in the warranty period.

What I Ask For Before Any Module PO Goes Out

Not a long list, but it's the list that changed after the bad job.

• A one-page scope sheet: what's included, what's excluded, in writing. Freight, duty, testing, spares, packaging.
• Test report traceability — which reports, which batch, which serials.
• A price breakdown that survives comparison with a landed-cost model, including payment terms and the cost of money.
• Warranty administration named in the contract, not the brochure.
• One named person who answers email during the project, not a shared inbox.

Nothing on that list is exotic. Most of it costs a supplier nothing but the discipline to write it down. Which is, if you ask me, the actual test.

So, Where That Leaves Me

Transparency in module pricing isn't generosity. It's a lower verification cost. That's the whole argument. When a supplier hands me a quote I can check line by line, my team spends fewer internal hours on it, and spends fewer hours arguing about it later. Those hours have a price, and it's always higher than people estimate.

The $/Wp column is still the first thing I look at. It's just no longer the thing I trust.

Anyone selling modules can be the cheapest for one quarter. Being checkable is a longer game.