A recessed linear fixture with three pages of documentation looks reassuring. IP20. 3000K. Ra>90. CE mark, IES file attached. The distributor checked it. The specifier signed off. The PO went out.
Then Monday, 8 a.m., the site calls: the middle of a 40-meter continuous run reads noticeably cooler than the ends.
You open the spec sheet. The model number is right. The color temperature is right. Nothing is off.
I've spent a little over four years as a quality and brand compliance manager at a lighting distributor that works primarily on architectural and commercial jobs, with a strong recessed lighting side. I review somewhere north of 200 project-specific configurations a year. Last year, roughly 15% of first shipments came back for rework—and very few of those were stopped because the fixture itself was defective. Most were cases of “the product is fine, the project isn't.”
The Spec Sheet Looks Compliant
In most distribution workflows, compliance is a checkbox. CE mark? Yes. IES file? Yes. IP rating matches the spec? Yes. Ship it.
The problem is that this checkbox only proves the fixture is safe on its own. It doesn't prove the fixture fits the job.
EN 60598-1 certification means electrical safety. EN 12464-1 sets what a given space needs in terms of illuminance, UGR limits, and minimum color rendering. Those are two different languages—one describes the product, the other describes the room.
Product compliance ends the moment the fixture leaves the factory. Project compliance doesn't exist until the fixture, the controls, and the installation method all line up.
November last year, a boutique hotel. A 40-meter continuous linear run went in, and the site came back with “the middle section looks cooler.” The test confirmed it: adjacent-bin 3000K had been mixed in, and at a 40-meter sightline the eye picks it up immediately. The manufacturer was willing to swap. They swap fixtures. They do not swap the sealed gypsum ceiling.
Rework cost: $14,000. Schedule slip: seven days. The distributor ate it—not for the $14,000, but for the next drawing set from the same designer.
The Gap Between Product Certification and Project Compliance
I've seen this pattern enough times to stop blaming the batch. On the surface, it looks like a problem with one batch, one particular fixture, one operator. What's actually behind it is a default assumption in this industry:
We treat compliance as a product attribute.
It isn't one. It's a project attribute.
The same linear fixture in an office and in a hotel corridor carries different compliance requirements. The office cares about illuminance levels and glare control. The hotel cares about rendering, consistency across batches, and reliable dimming integration. Same product. Different project. Different compliance boundary.
This isn't specific to one brand. Our range includes architectural lighting brands like iGuzzini alongside a handful of smaller European manufacturers, and the gap shows up anywhere serious commercial specifications go. Even a floor lamp catalog—textbook stuff—now carries IP/IK ratings and photobiological safety certifications on every line item. The catalog keeps moving with the project requirements. Most distributors just don't read it that way.
Why Compliance Issues Surface Behind the Ceiling
The most frustrating part of compliance work: the moment a problem surfaces is always the wrong one. Too late—the run is already installed. Or too early—it's still a PDF and a handful of photos, and nobody wants to redo a review for a problem that might happen.
That was workable ten years ago, when fixtures were judged on brightness and looks. Commercial lighting systems have gotten more complicated since. Dimming protocols have to talk to the building management system. Photobiological safety (EN 62471) documents go to the design team. ErP Directive 2009/125/EC efficiency classes have to land in the closeout package. A commercial building's compliance file routinely runs past 200 pages.
Thicker files mean more room for error. And the cost of an error stopped being “one fixture” a long time ago.
If the problem gets caught at the factory, the cost is a rework ticket. If it gets caught in the warehouse, the cost is a repack plus a possible delay penalty. If it gets caught behind the ceiling, the cost is demolition, patching, repainting—and then the owner's trust. In the cases I've worked through, that last version costs at least ten times the first two.
Once that happens, it's not a compliance problem anymore. It's a relationship problem. And relationship problems do not get priced back in.
Turning Compliance Into a Process Instead of a Signature
Concretely. We put a process in place in 2022 that took first-shipment rework from 22% down to 9%. Nothing technically complicated. Three things:
1. Check the project before you check the product
Before SKU review, do a project-level check. Illuminance targets, glare limits, rendering requirements, dimming protocols, IP/IK ratings—work through them by space type instead of trying to force a catalog against the room.
2. Retain a sample from every batch, with bin records
Not spot checks. One retained fixture per batch, photographed, bin recorded, filed with the project. So if something does go wrong later, you can trace it back to a batch and a cause instead of saying “the factory should be fine.”
3. Run a 1:1 mockup before the first shipment
Even if it's a meter long. Data reads as parameters. The site reads as perception. Those two don't always agree.
The process isn't cheap. Extra labor, samples, and time add up to a few thousand dollars a year. Against a ceiling rework, that number is a rounding error.
Bottom line: product compliance is the entry ticket. Project compliance is the line that actually gets paid. And it has to be earned again on every new job.
