-
The 6-Step PV Module Compliance Checklist
-
Step 1: Verify the certificate's validity and scope
-
Step 2: Check the factory on the certificate vs. the actual shipping factory
-
Step 3: Confirm your supplier is on the project's approved vendor list
-
Step 4: Match the datasheet to your site's climate
-
Step 5: Demand itemized, transparent pricing
-
Step 6: Demand the test report, not just the certificate
-
Step 1: Verify the certificate's validity and scope
-
Common Mistakes I Still See (and Have Made)
If you're bidding on an ACWA Power project, you already know the stakes. The company has grown from a Saudi independent power producer into a global player in renewables and desalination. Their procurement teams don't mess around. A missed compliance detail can take months to fix. I found that out the hard way.
I've spent 7 years sourcing PV modules for EPC contractors on large utility-scale solar jobs, including ACWA Power sites. In that time, I've personally made (and documented) three significant mistakes that together cost roughly $250,000 in wasted budget and delays. Now I keep a checklist pinned to my team's wall. Maybe it'll save you the same pain.
Whether you're scrolling acwa power news today for the latest tender announcements or reading their company overview for the first time, one thing is constant: ACWA Power's projects demand PV module compliance that goes beyond a photocopied IEC certificate. Here's the checklist I use.
The 6-Step PV Module Compliance Checklist
Step 1: Verify the certificate's validity and scope
The first thing most people do is ask for the IEC 61215 and IEC 61730 certificates. Good. But then they glance at the date and file it. That's not enough.
Check. The. Certificate. Not just that it exists. Look at the standard version. There's a world of difference between IEC 61215:2005 and the current edition. The certificate should match the standard your project specifies.
Also check that it covers the exact module model and wattage class you're ordering. A certificate for a 540 W model doesn't automatically cover a 550 W model with a different cell count. According to the International Electrotechnical Commission's certification framework, changes in materials or design can invalidate type approval. This was true 10 years ago when module designs were stable for years. Today, products update every 18 months. That 'valid certificate' might be for a version that no longer exists.
Checkpoint: Certificate standard, module model, wattage class, and issue date all match.
Step 2: Check the factory on the certificate vs. the actual shipping factory
OK, the second one is where it gets ugly. The certificate lists a manufacturer and a factory. The module you get must come from that exact factory. I learned this after a $45,000 mistake in 2022.
We had an approved seller with a valid IEC certificate. The modules arrived, and during the factory audit the client noticed the serial numbers didn't match the certified location. Turned out the supplier had shifted production to another facility without updating the certification. The batch was rejected. We spent $20,000 on re-testing and $25,000 on replacement modules for that shipment.
I assumed 'same specifications' meant identical results across factories. Didn't verify. Now we cross-check the factory address on the certificate against the shipping documents and the manufacturer's own database.
Checkpoint: Certificate's factory address matches the warehouse and the module's factory code.
Step 3: Confirm your supplier is on the project's approved vendor list
ACWA Power projects typically maintain an approved vendor list (AVL). If your module supplier isn't on it, you might be wasting your time—even if the module is IEC certified. The AVL isn't public, but your tender documents or project pre-qualification pack will tell you if a supplier is acceptable.
So glad I checked this before a bid in 2024. We were 24 hours away from submitting with a manufacturer that had great pricing and a perfect certificate. A quick call to the procurement lead confirmed they weren't approved. We swapped suppliers just in time. One more day and we'd have been disqualified.
Ask your client for the AVL or the eligibility criteria. If your supplier isn't on it, either start their qualification process or find one who is. Simple.
Step 4: Match the datasheet to your site's climate
Compliance isn't only about certificates. It's about whether the module you're buying actually fits the project's climate. When you're flipping through a solar module catalog, it's tempting to focus on price and wattage. Don't.
Check the temperature coefficient (Pmax), NOCT (the newer term is NMOT), and low-light performance. A module with amazing STC ratings can underperform in high heat or low irradiance. ACWA Power projects span from Saudi deserts to Central Asian plains. The right module for one site isn't necessarily right for another.
We once picked a module based on its flash test results, ignoring the temperature coefficient. In a 45°C desert environment, the nameplate capacity was a dream. The actual output was 8% lower than expected. We nearly failed the performance guarantee test.
Ask for the datasheet values that correspond to your site's conditions. If they don't provide them, walk away.
Step 5: Demand itemized, transparent pricing
Now the pricing part. I'm a big believer in transparency. Real talk: the vendor who lists all fees upfront—even if the total looks higher—usually costs less in the end.
We had a supplier quote a price that was $0.01/W lower than the next one. Looked great. Then we discovered the price excluded inland freight, export insurance, and bank charges. By the time we added the actual logistics, the 'cheap' module cost $0.03/W more than a transparent quote from another vendor.
So ask for a full breakdown. Ex-works, freight, insurance, duties, taxes, final delivery to site. Every item. If a fee doesn't appear in writing, assume it's going to appear later. (Note to self: this is the step I skipped in 2019, and it cost us $18,000 in unexpected port charges.)
I've learned to ask 'what's NOT included' before 'what's the price.' That one question catches more hidden costs than any contract review I've done.
Step 6: Demand the test report, not just the certificate
Finally, don't accept a certificate copy as proof of performance. Certificates are summaries. The actual test report contains the data you need: measured Pmax, fill factor, degradation rate, LID, LeTID, and whether the batch showed cracked cells.
When we audit a factory, we review the type test report and compare the measured values to the datasheet. A certificate for a '1.0% annual degradation' module means nothing if the test report shows 1.8% for the actual batch. In one instance, the test report revealed that the module's LID exceeded the allowable limit—a detail the datasheet had glossed over. Catching that saved us from a project-wide generation shortfall.
According to IEC TS 62941, manufacturers should also have a quality management system that ensures production consistency. Ask for their quality plan and recent inspection results. If they hesitate, be cautious.
Common Mistakes I Still See (and Have Made)
Here's the thing: most sourcing teams don't fail because they're incompetent. They fail because they're in a hurry and they skip the boring steps. Final list of things that don't look like compliance issues but are:
- Trusting a certificate photocopy. Verify it online or via the certification body's database. If the supplier can't provide a verification link, that's a red flag.
- Ignoring certificate revisions. The 2005 edition of IEC 61215 is not the same as the current edition. Check what your project specifies.
- Comparing only unit prices. The total landed cost is what matters. A cheaper module can be the most expensive one after freight and delays.
- Not putting compliance in the contract. Write the IEC standard, the factory location, and the AVL requirement into the purchase order. That way, if anything changes, you have legal leverage.
This checklist isn't perfect. But it's the one I use, and it's caught 47 potential errors in the past 18 months. That's 47 $0 mistakes. I'd rather keep it that way.
