Installer SupportResource Center

2026-09-30 · Renata Silva

Solar Module Compliance Requirements: Why 'Certified' Panels Still Get Rejected

A field-tested look at why IEC-certified solar modules still fail port clearance and site acceptance — the compliance gaps most buyers don't see until the container is already on the water.

The Container That Sat in Port for 19 Days

In September 2022, I had 1,240 solar modules stuck at Mundra. Or maybe it was 1,180 — I keep mixing it up with the Jaisalmer order from that same quarter. Either way, every morning the customs agent called, the demurrage number got a little bigger. I'd step out of the procurement meeting, phone in one hand, the other hand gripping a folder I was absolutely sure contained every document we needed. IEC certificates. Factory inspection reports. Packing list. Bill of lading. The whole stack.

"You're missing one thing in the compliance file," he said. "It's a list problem."

It took me three days to understand which list he meant — and longer to admit the mistake was mine, not the freight forwarder's, not the supplier's. That container eventually cleared, but the lesson cost more than the demurrage. I've moved roughly 340 solar module containers since then, and I still haven't allowed myself to skip that checklist.

That's what I want to walk through here. Not a compliance manual — those exist. What I want to unpack is why solar module compliance requirements keep blindsiding experienced buyers who genuinely think they've done the work.

The Problem You Think You Have (It Isn't)

If you'd asked me before 2022 what solar module compliance meant, I'd have shrugged. "Our supplier has IEC certificates. What else do you need?"

Nothing else, I assumed. Compliance = manufacturer holds certificates. Certificates get handed to you. You drop them in the tender pack. Client nods. Done.

That's the paper view. Reality is different. And reality doesn't announce itself until a container is already on the water, or worse, already at site, with the receiving team looking at the paperwork and then at you.

The Deeper Issue: Certificates Aren't Issued to Manufacturers

This is the part that took me a full year and a fairly expensive invoice to internalize.

IEC 61215 and IEC 61730 are the two standards most people quote. The first covers design qualification and type approval. The second covers safety qualification. Both matter. Both are also narrower than buyers assume.

IEC 61215 and IEC 61730 certificates apply to specific module models produced at specific manufacturing sites — not to a company, not to a brand, and not to an entire product family.

In plain terms: a 545W TOPCon monofacial module produced at one plant may be certified while the 580W bifacial version from the same plant is not. Change the frame thickness, and in some jurisdictions the paperwork has to be reissued. Move production to a different facility within the same group, and the certificate may not follow.

I once said "IEC compliant." The supplier said "yes, compliant." Both of us were telling the truth. We were just telling different truths.

And compliance isn't static — that's the piece that really broke me in year one. Certificates expire. Standards get revised. Regulators add requirements that didn't exist when you last checked. India's ALMM list is the clearest example: being on IEC doesn't guarantee you're on the list, and being on the list is a moving target. What was standard practice in 2020 — shipping without checking ALMM status — is a non-starter in 2026. Five years ago, buyers could wave through documentation that would today stop a container before it leaves the port.

The fundamentals of "is this module safe and rated for its output" haven't changed. The execution of proving it has transformed entirely.

What the Mistake Actually Costs

The 2022 incident ran me about $4,200 in demurrage — annoying, but not catastrophic. What hurt more was the unplanned re-packing and re-booking, plus a site milestone that slipped by eleven days. Site managers don't forget slipped milestones.

The truly expensive part was credibility. The client's project director read the acceptance report twice and asked a question I couldn't deflect: "So have you been shipping without checking these on every batch?"

There isn't a good answer to that question. There's only the next ninety containers, handled with zero shortcuts, until the trust comes back.

I've seen worse since. One developer had a shipment rejected at the substation gate because the certificate covered a different power bin than the modules on the pallets. That happened two weeks before monsoon cut the installation window. Thirty crew members sat idle for four days while three companies argued about whose compliance department had dropped the ball. I was on the call. Nobody wanted to be the one presenting that to the client.

Another case: two modules built on the same underlying cell technology, same visual design, same approximate wattage — but from different factories, with certificates that covered different things. A one-character difference in the model code was enough for the buyer's compliance team to flag the entire batch as non-conforming. Full return. Every module.

The most frustrating pattern I've seen in ten years of this: companies treat compliance as a one-time project. You assemble the file at tender, and it lives in a shared drive until somebody needs it. The failures come from files that were correct in month one and out of date by month fourteen.

The Short Version: What Actually Needs Checking

No long checklist. Just the items that have repeatedly saved my orders, condensed from a much longer internal document.

1. What the certificate actually covers.

Read the model codes, factory codes, and rated power range. If the exact specification you're buying isn't inside the scope, don't sign. "Close enough" isn't a regulatory category.

2. Destination-specific requirements.

IEC is the global baseline. It's not the finish line. India adds ALMM and BIS. The EU adds CE and WEEE-related obligations. North America layers in UL and local fire codes. Ask your customs broker or an in-market compliance consultant for the destination list before contracting — not after the vessel sails.

3. Validity and revision status.

Certificates have expiry dates. Standards have editions. Build renewal dates into your procurement calendar with at least six months of buffer.

4. Who the certificate is actually issued to.

In OEM and private-label arrangements, the named holder matters. Some jurisdictions care about the legal manufacturer; others care about the brand owner. Getting this wrong only shows up at the port.

Manufacturers running large-scale operations — Adani Solar included — tend to have better-documented compliance stacks. But "tends to" isn't "always." Verify every supplier's paperwork the same way, regardless of brand size. Especially the parts of the paperwork nobody wants to read.

Where This Lands

The goal isn't to have an answer ready if someone asks. It's to have the answer already on the table. Not "our supplier has IEC certificates" — but "this shipment's specific model, factory, certificate number, scope, validity, and destination requirements have all been reconciled." Same number of words. Different value entirely.

I still use the checklist from 2022. Once or twice a year, I catch myself skipping a step — telling myself "what are the odds." Then I remember the phone ringing from Mundra, and I go back and do the work.

The standards will keep evolving. New lists will get published. Modules that were compliant last year will, in some markets, require re-documentation next year. That's not a problem to resent. It's just the environment. The habit that beats it hasn't changed at all: reconcile every line before you sign, and reconcile it again before the container sails.