Back to resources

Stop Optimizing $/W: What Actually Determines Solar Module Sourcing Cost

A module manufacturer's rush-order specialist explains why the lowest $/W quote is usually the most expensive solar procurement decision, and what informed B2B buyers check first.

If Your First Question Is "Who Has the Lowest $/W?" You've Already Lost Money

Let me be direct: picking PV modules by headline $/W is the most expensive shortcut in B2B solar sourcing. Not the riskiest. The most expensive. There's a difference.

I coordinate emergency orders at a Tier-1 module manufacturer. Over the past two and a half years I've handled 200+ rush shipments — everything from 3-pallet pilot runs to 60MW+ rooftop projects, some booked with 36 hours' notice. Almost every time I get a panicked 11pm call, the problem wasn't that the factory was too slow. It was that the buying team optimized the wrong number from day one.

Here's what I think too many solar buyers get wrong on their first procurement cycle — and what an informed buyer figures out before they even send an RFQ.

Argument 1: $/W Is Not Your Cost

$/W is a number. Your cost is that number plus everything attached to it.

I once shipped a batch where the buyer "saved" about 0.4 cents per watt — roughly $2,600 across a 6MW order. Then they discovered the factory uses a non-standard pallet that fits 28 modules instead of 31, and their installation team had planned unloading for 31. Reslotted logistics cost $3,800 and cost them four days. The "cheap" batch was the expensive one.

Real landed cost includes at minimum:

  • Module price per watt (obviously)
  • Certifications that match your actual project requirements — not the ones on the marketing datasheet
  • Pallet and container efficiency — how many modules per container, and whether that matches your logistics plan
  • Warranty terms you can actually enforce, not just read
  • Rush and delay exposure — what a slipped delivery date costs your project

Bottom line question: is the few cents per watt you "saved" bigger or smaller than the cost of one day of project delay on site?

Argument 2: Capacity Numbers Don't Tell You When Modules Arrive

In H1 2024, Tier-1 manufacturers shipped somewhere in the 30-35GW range globally. Our own number was 34GW for the half-year, which we publish in our disclosures. Buyers sometimes quote this back at me as proof that "capacity is fine, so lead time must be fine."

Capacity and lead time are not the same thing.

When a fab is running near full utilization, rush demand has to squeeze in. Everyone buying urgently assumes there's flexible capacity waiting — but there isn't infinite room. If you call me in peak season asking for 5MW in 10 days, I'm not giving you a yes/no on availability. I'm telling you how much scheduling flexibility exists and what has to move for you to fit.

The honest answer is usually: "If you can accept this SKU, yes — but we'd be pulling it from another line's slot." That's a real lead-time conversation. It's not "yes" and it's not "no."

I can only speak to original-manufacturer supply. If your sourcing runs through spot markets or third-party traders, the calculus is different and I'd be out of my depth.

Argument 3: Informed Buyers Decide Faster — and They Win

The biggest thing I've learned in this seat: educating the buyer is better for us than negotiating with a vague one.

When a procurement team genuinely understands what they're buying, quote verification moves faster, technical review moves faster, and purchase orders get confirmed faster. They stop asking "can you go cheaper?" and start asking "if we move from 550W to 580W, how does BOS cost shift?" — the kind of question I can answer in two minutes.

I won't pretend that's not self-serving. It is. But it cuts both ways: deals won on information asymmetry come back as customers who go elsewhere next cycle. Buyers who understand total cost come back with better questions, and I actually like those questions.

That's why I now send a cost breakdown alongside the quote. Some buyers ignore it. The ones who engage with it almost always end up ordering.

Counter-argument: "My Boss Only Looks at $/W"

Fair. I hear it constantly. If your manager or approval committee anchors on $/W, you have two options.

  1. Resubmit with a total landed cost model — include rush fees, logistics change orders, warranty enforceability risk, and delay contingency. The "expensive" option often has the lowest total.
  2. If that still doesn't fly, split by project risk: for low-urgency, wide-window projects, $/W-first is fine. For deadline-critical projects, argue on a different axis.

I'll also flag my own blind spot: I've only seen the sourcing question from the manufacturer side. If your purchasing runs through spot markets or trading houses, the cost structure can look completely different, and there are probably things I'm not aware of.

So What Should Buyers Actually Ask?

The alternative isn't "ignore price" — that's the other extreme. The sensible order is:

  1. Fix the project parameters first: grid-connection date, BOS layout, certification requirements.
  2. Ask the factory: at those parameters, can you deliver? If yes, when? If no, what changes?
  3. Then compare $/W — within the set of quotes that actually satisfy the requirements.

If I had to compress it into one line: price is a constraint, not the objective function.

The fastest projects I've shipped weren't the cheapest quotes. They were the ones where the buyer already knew what was negotiable and what wasn't.

That's also why I'd rather spend 10 minutes explaining options than deal with mismatched expectations three weeks later.

When was the last time you locked onto a $/W number, only to pay more later for something that wasn't on the quote?