If you've ever approved a lighting purchase order and then found a compatibility issue three weeks later, you know that sinking feeling. The fixture looks right. The Zigbee module is on the compatibility list. The driver's specs match. But something doesn't communicate the way it should, and now you're explaining it to a customer.
I'm a procurement manager at a 45-person lighting distribution company. I've managed our lighting controls budget for about six years—$1.4M a year, maybe $1.45M if you include freight. I've negotiated with more than 40 vendors and tracked every order in our cost system. I'm not writing this to blame manufacturers. I'm writing it because I keep seeing the same mistake: choosing a quote as if it were a list of parts, instead of choosing a system.
The real problem isn't the unit price. It's the spec sheet.
Everything I'd read about procurement says get three quotes, compare the line items, and pick the lower one. In practice, that advice has cost me more than it saved. At least, that's been my experience with mid-sized distribution.
Here's why: smart lighting looks like a collection of separate things. Downlights, switches, sensors, Zigbee modules. The quote treats them as components. But the moment they're installed, they become one system. And systems have hidden requirements that no individual datasheet will show you.
Take recessed lighting private label. You've chosen a driver, an LED board, and a heat sink. Now you need a Zigbee module to make the fixture smart. A component vendor says their module is $0.55 cheaper. On paper, it's the same protocol. But if that module hasn't been tested with your driver, you're not saving $0.55. You're buying a future integration problem.
A good Zigbee manufacturer sends you the certified stack details, interoperability test results, and antenna placement notes. A component vendor sends you a datasheet and a smile. The difference only shows up in the field.
So the surface problem most buyers complain about—'lighting projects keep going over budget'—isn't really about inflation or surprise shipping fees. It's about comparing components instead of systems. The deeper problem is that we've all been trained to evaluate quotes with a spreadsheet, not with an installation perspective.
The hidden costs of compliance and integration
Let me give you a concrete example. In Q2 2024, we compared six motion sensor manufacturers for a new commercial project. One supplier's quote came in $2.10 lower per unit than the incumbent. Maybe it was $1.90—I'd have to pull the spreadsheet, but the exact number isn't the point. On 500 units, that's about $1,050 in apparent savings. I want to say the order was 500 units, but don't quote me on that.
I almost took it. My procurement policy at the time said get three quotes and go with the best value. This looked like the best value. But I'd been burned before, so I asked a question that's not on most RFQ templates: 'Have you tested this sensor with the control system we're using? Can I see the interoperability test report?'
The answer was a marketing brochure. We paid a consultant $350 to run a bench test. The sensor failed. Not dramatically—just enough to cause intermittent occupancy detection in about 40% of the layouts we'd planned. The $350 test saved us an estimated $12,000 in field rework. That's the cheapest money I've ever spent.
Looking back, I should have asked for the test report during the RFQ, not after the quote. At the time, I was in a hurry and the price gap was tempting. It was a mistake.
And that's just the component level. The bigger hidden cost is compliance.
When you're building a recessed lighting private label line, the fixture is not your product. The specification is. Your name goes on the box, so you inherit the certification burden. If the manufacturer hasn't already documented UL/ETL, FCC, energy performance, and driver compatibility for your target market, you pay for that engineering later.
I've seen a product sit in a warehouse for six weeks because the LM-79 data wasn't formatted correctly for the utility rebate program. The unit price was fine. The carrying cost was not.
Why 'we'll make it work at installation' is expensive
Every time I've heard a supplier say 'don't worry, the integrators can fix it during commissioning,' the fix turned into a change order. Installers charge by the hour. Integrators charge more. A $0.30 component decision can easily become a $4,800 integration invoice. I'm not exaggerating—that happened on a project in 2023.
The conventional wisdom is that verification costs time. But 5 minutes of verification beats 5 days of correction.
5 minutes of verification beats 5 days of correction.
I've made this mistake enough times that I now have a 12-point checklist for lighting control components. It takes about 30 minutes to run through on a new product. Since I started using it, we've avoided at least three major issues. I estimate it's saved us $18,000 in potential rework over two years.
I want to say that checklist is the solution to everything. It's not. But it's a start.
How to evaluate lighting manufacturers before you sign the PO
You don't need to become an engineer to buy smart lighting well. You just need to ask different questions.
- Ask for system-level evidence. A component datasheet is not integration proof. Ask: 'Which control systems have you tested this with? Can I see the test report?' If they say it's under NDA, ask for a summary of the testing process.
- Check the Zigbee qualifications. Not every module with a Zigbee label behaves the same. Ask about the certified stack version, firmware update process, and what happens if the end device goes offline. A manufacturer that treats Zigbee as a commodity may not be a good partner for a system that depends on reliable communication.
- For private label projects, ask for the full documentation package. BOM, UL/ETL files, FCC IDs, LM-79 data, driver compatibility list, and a written change notification commitment. If they can't produce these, your 'cheap' private label line just became an engineering project.
- Run a pilot before the full order. Even 20 units will reveal integration issues. The cost of a pilot is always less than the cost of a recall.
- Calculate total cost, not unit cost. Unit price + engineering time + certification paperwork + bench testing + probability of rework. I built a spreadsheet for this after my second expensive mistake. It takes 20 minutes to update and has paid for itself many times over.
How to evaluate motion sensor manufacturers
For motion sensors specifically, the checklist is a little tighter. I ask three questions now:
- What is the current draw at idle and active? Does it fit the power budget of the control system?
- Can the sensor be configured for both occupancy and vacancy behavior? Some cheap sensors lock you into one.
- Where did the detection pattern data come from? A '10-meter range' from a manufacturer's brochure is not the same as a certified performance test with the specific mounting height you're planning.
That last one has caught more than one procurement team off guard.
Bottom line: the cheapest quote is the one you've verified
I'm not saying the lowest quote is always a trap. I'm saying you can't know if it's a trap until you've checked the things that actually drive cost: compatibility, compliance documentation, and the manufacturer's willingness to be transparent.
If the customer has specified a Savant smart lighting system, the whole chain—fixtures, drivers, sensors, modules—needs to fit that Savant lighting system's requirements. A generic Zigbee module may work in a lab and fail in production. Savant has integration documentation for a reason. A manufacturer who has already worked through that process is worth more than one who says they'll 'figure it out later.'
So, if you're comparing quotes for a smart lighting project, slow down. Pull out the spec sheets. Ask for system-level evidence. Do the 30-minute verification. Because the 5 minutes you save by skipping that check could turn into five very expensive days of rework.
Trust me on this one. I've been the one holding the invoice.
