What I Check Before I Approve a Lighting Controls Order: A QC Manager's FAQ

I run quality and brand compliance for a lighting controls distributor. Every order that leaves our dock, and every spec submittal that goes out under a manufacturer's name, passes my desk first. Last year that was roughly 4,800 line items across a little over 300 purchase orders.

The same questions come up over and over, from contractors, from OEM buyers, and from our own sales team. So here they are, answered.

What do you actually check on a Lutron motion sensor switch before you approve the shipment?

Not the box count. Counting cartons against a packing list is a receiving task, not an inspection.

Three things generate almost all of our callbacks: coverage pattern against the real mounting height, the sensor's behavior profile (auto-on/auto-off versus vacancy-only), and the part-number revision. That third one sounds trivial. It isn't.

In my first year doing incoming QC, I made the classic rookie error: I signed off on a shipment because the cartons matched the packing slip. I still kick myself for not opening them. We then shipped 240 occupancy sensors to a tenant improvement job, and 60 of them were the wrong coverage pattern for a 12-foot ceiling. The part numbers differed by two characters. The redo cost us freight both ways plus a week of the electrician's schedule — a little over $4,000 all in.

Now every contract we sign carries a written coverage-pattern and behavior-profile requirement. Vendors complained about it for a quarter. They also stopped sending us the wrong pattern.

Is "Lutron-compatible" the same thing as Lutron?

No, and I learned that one the hard way.

I assumed "compatible" meant the device would talk to the system we specified. Didn't verify. Turned out the third-party sensor spoke the protocol fine but sat on a firmware revision our processor didn't recognize — worked on the bench, dropped off the network in the field.

What I mean is: compatibility is a chain, not a checkbox. Before you accept "compatible" on a submittal, get three things in writing. Which processor and firmware revision it was tested against. Whether the integration runs over the wired link or the wireless one — those two fail in completely different ways. And who owns the integration warranty when the two devices come from different manufacturers.

If a supplier can't answer those three, they haven't tested it. They've assumed it.

What changes when the project is a Lutron lighting system in Huntington Beach, CA?

Huntington Beach is a California job, so the big one isn't local — it's Title 24 Part 6, the state's building energy efficiency standards, which apply statewide, not just along the coast. The current edition took effect January 1, 2026. Rather than quote sections at you, here's what it means practically: certain space types require occupancy or vacancy sensing, and the standards get quite specific about how the control behaves — which spaces need manual-on rather than auto-on, how partial-off works, how the sensor interacts with daylighting. Check the current edition at energy.ca.gov before you lock a sequence of operation. The requirements have moved between editions.

Two more things bite people on coastal Orange County jobs. Salt air is real — outdoor and semi-exposed enclosures and contact materials degrade faster here than they do inland, and I've processed warranty returns that were corrosion, not electronics. And utility rebate paperwork (Southern California Edison serves the area) has to be assembled before the fixtures go in, not after. Retroactive rebate claims on lighting controls are genuinely painful to reconstruct.

Worth saying out loud, too: a system that passes a Title 24 inspection is not automatically an "energy-saving system" you can market as one. Those are different claims with different evidence requirements. More below.

For a smart lighting OEM or private label program, what should the buyer demand?

Test data, not assurances. A factory that says "our LED drivers are high quality" has told you nothing you can use in a warranty dispute.

What I ask for: LM-79 reports on the finished fixture; LM-80 data plus a TM-21 projection for the LED package if lumen maintenance is part of your claim; ISTMT for thermal; and a written CCT and flux tolerance expressed in MacAdam ellipse steps. If the factory won't name the driver manufacturer, that's a red flag — when the driver fails in year three, "we source from several" is not a warranty answer.

Get the firmware and control protocol documented in writing too, including the revision you're signing off on. Private label means your name goes on the label. Once it's in the channel, whatever that product does in the field is your problem, not the factory's.

Every downlight distributor buying guide covers CRI and beam angle. What do they leave out?

Serviceability. And driver transparency.

A downlight distributor buying guide will walk you through CRI, beam angle, and cutout size — which is fine as far as it goes. What gets left out is what happens in year four and year six.

Can you replace the driver from below the ceiling, or does the fixture have to come out? Will the product still exist in three years, and if not, what's the replacement path? Cross-run color consistency matters here too: two batches of "3000K" from the same factory can land meaningfully apart on color, and if you're lighting a corridor in phases, your customer will see the seam.

I should add that this is the stuff that lands on your sales team, not on the factory. The factory never hears about it.

Why do premium lighting control systems still fail?

People assume that more expensive controls deliver better reliability. In the jobs I audit, the causation largely runs the other way: systems that hold up are the ones where somebody paid for commissioning and as-built documentation — and projects with a commissioning budget tend to be the ones that specified better hardware in the first place. The hardware didn't make the system reliable. The process did.

The most common failure I see isn't a dead sensor. It's a sensor that was installed correctly, never programmed to the sequence of operation, and has been sitting on factory defaults since day one. Nobody notices in a warehouse. Everybody notices in a conference room.

At least, that's been my experience on commercial and multi-family work. A single-family job with three zones doesn't need a commissioning agent — a half hour with the homeowner and a one-page written sequence will do.

Can I put an energy savings percentage on the sell sheet?

Not without substantiation, and this is where distributors get themselves into real trouble.

Per FTC advertising guidance (ftc.gov/business-guidance/advertising-marketing), objective claims must be truthful, not misleading, and substantiated with evidence before you make them.

An energy savings percentage is an objective claim. So is "up to 60% savings." So is any comparison against a baseline you never measured. Without test data or a documented calculation behind it, don't print it.

Same logic on environmental language — the FTC Green Guides (16 CFR Part 260) require qualification on claims like "recyclable" when the recycling infrastructure to back it up isn't broadly available to consumers.

And hold onto the distinction: a fixture that satisfies a code requirement is compliant. That does not make it efficient. Separate claims, separate evidence.

What does transparent pricing actually look like on a lighting controls order?

It looks like a quote that names the things most quotes leave out.

I've learned to ask "what's not included" before I ask "what's the price." On lighting controls specifically, the items that surprise people are commissioning labor, firmware updates during construction, freight on replacement units, restocking fees on returns, expedite fees when a reflash pushes the schedule, and project registration paperwork for the warranty. None of those are unreasonable charges. What's unreasonable is discovering them in month three.

Here's the thing: the vendor who lists all of that upfront — and yes, their total sometimes looks higher — usually costs less by the end of the job. And more to the point, I know what I'm budgeting against. A quote I can't reconcile isn't a lower price. It's an unquantified one.

To be fair, nobody I buy from is hiding anything on purpose. Those costs are legitimately hard to estimate before you've seen the site. So ask for the range, not the figure. A vendor who says "commissioning runs $1,200 to $2,800 depending on zone count" has handed you something you can plan around. A vendor who says "we'll work it out later" has handed you a problem.