I review every lighting control SKU before it goes on our shelf or into a quote package. Around 240 items a year. In 2024 I rejected 22% of first deliveries — and not because the product was bad. The paperwork, the listing, or the wiring documentation didn't hold up.
Almost every one of those rejections came down to the same fork: branded controls (Legrand, or any established line) versus private-label Zigbee hardware from an OEM.
Both can work. I've approved plenty of each. So instead of arguing one is better, here's the framework I actually use — four dimensions, and where each side tends to win.
The four things I compare, and why the order matters
- Who owns the compliance paper — the listing, the certification, the code documentation
- Wiring and installer documentation — the part nobody budgets for
- Lead time and delivery certainty — a date vs. an estimate
- Cost across the project, not per unit
The order matters because a failure at #1 ends the conversation. You can't fix a listing problem with a better price.
1. Who owns the compliance paper
With a branded sensor, the manufacturer holds the UL file, the certification ID, and often the energy-code compliance statements you need for submittals. You inherit that. You don't build it.
With private label, the listing may sit under the OEM factory's name rather than yours. That's fine — but you need to be able to answer the question. When the AHJ or the specifier asks who the listed entity is, 'the factory, I think' is not an answer.
Here's what I actually check, and it takes about ten minutes per SKU:
- Does the model number on the submittal match the model number on the label, exactly?
- Does the UL file number in the paperwork resolve to a live listing? UL Product iQ is public. Use it.
- For occupancy sensors specifically: is there coverage test data? NEMA WD 7 is the reference standard for occupancy motion sensor coverage patterns and mounting-height testing. If your OEM lists to UL 916 for energy management equipment but has no coverage data behind the pattern printed on the box, you're the one defending that claim — not them.
- If the spec cites ASHRAE 90.1 or California Title 24 Part 6, does the documentation actually address the control sequence being specified, or does it just say 'Title 24 compliant' in the marketing copy? Those aren't the same thing.
Where this lands: branded wins, most of the time. Not because an OEM can't be compliant — plenty are — but because branded means you inherit the proof instead of manufacturing it. Verify the current edition of any standard you cite; these get revised on roughly three-year cycles.
2. Wiring documentation — the counterintuitive one
You'd think private label saves money across the board. It doesn't. It moves cost somewhere else.
Wiring diagrams. I've had an electrician call me from a job site holding a private-label sensor and a two-page PDF that showed, essentially, a sticker. No terminal layout. No line/load/neutral positions. No indication of whether the dimming pair is Class 2 wiring per NEC Article 725.
NEC 110.3(B) requires equipment to be installed in accordance with its listing and labeling instructions. If the instructions are thin, the electrician is guessing — and the inspector can fail it. That's a red flag I check before I look at price.
Branded lines usually publish per-model diagrams, and the good ones include load ratings for LED inrush. That matters more than people think. NEMA 410 addresses inrush current for lighting control devices, and a switch rated at 600W incandescent is not automatically rated for twenty LED drivers. I've watched a private-label switch fail on exactly that point — arced contacts at about eight months.
The most frustrating part of this job: it's the same gap, every time. You'd think a spec sheet would state terminal torque and contact rating. But a lot of private-label literature stops at 'compatible with Zigbee' and calls it a datasheet.
Same story with 0-10V dimming. If the OEM references IEC 60929 Annex E, get the actual dimming curve and confirm it matches what the driver expects. '0-10V' describes a range, not a behavior.
Where this lands: branded wins, and it isn't close — unless your OEM will commit to producing custom documentation to your template. Some will. Get a sample before you place the order, not after.
3. Lead time and delivery certainty
Private label usually means a factory run, a minimum order quantity, and a shipping window. The unit price is better. The timeline is softer.
I have mixed feelings about rush premiums. Part of me thinks they're gouging. Another part has watched what happens when a spec deadline slides, and I've stopped arguing with the second part.
March 2024, a school retrofit: 240 sensors. The private-label option came in about $1.90 cheaper per unit — roughly $456 saved. The quote said six to eight weeks, subject to factory scheduling. We took it. Week seven, the factory pushed to week eleven. The GC's inspection window was week nine. We air-freighted 240 units at $4,800. Net position: minus $4,344, plus one very unpleasant phone call.
Saved $456. Spent $4,800. That's the entire lesson in two numbers.
What you're buying with a premium for a confirmed ship date isn't speed. It's the fact that someone has inventory on a shelf and a date they'll stand behind when it slips. 'Subject to factory scheduling' is not a date. I've started treating that phrase as a deal-breaker on any job with a hard inspection milestone.
Where this lands: stocked domestic supply wins on certainty. Private label wins on cost — when the schedule has slack. If you don't know how much slack you have, you don't have any.
4. Cost across the project, not per unit
Add it all up: unit cost, freight, duty, the hours your team spends chasing compliance documents, field support, reorder risk, and the cost of one missed inspection.
That $1.90 delta on 240 units is $456. A two-week slip on a final inspection was worth more than $456 in GC back-charges alone. So on that job, private label wasn't cheaper. It just looked cheaper.
Now run the same delta on our 12,000-unit annual sensor order. $1.90 becomes $22,800. At that scale, absorbing the documentation burden is absolutely worth a conversation — and often the right call.
Scale changes the math. That's the whole tension. Per-unit thinking gets you the wrong answer on small jobs; per-unit dismissal gets you the wrong answer on big ones.
So which one do you actually pick?
Go private label / OEM Zigbee when:
- The spec doesn't name a basis-of-design manufacturer
- Your AHJ has already accepted this listing on a prior project
- You've got four weeks or more of schedule float
- Volume is high enough that the per-unit delta covers the documentation labor
- The OEM will sign off on a documentation template you wrote
Go branded when:
- The spec names a basis-of-design product
- The schedule has no float, or the inspection date is immovable
- The AHJ is strict, or the install is highly visible
- Nobody on your team has bandwidth to chase compliance paperwork
One caution before you commit to a private-label run: don't assume Zigbee means interoperable with your existing gateway. CSA Zigbee 3.0 certification is a floor, not a feature guarantee. Commission a sample against your actual gateway and controller before you sign off on production. I've seen certified devices fail on the pairing flow, and once the run is made, that's your problem.
And for what it's worth, I don't think this is a permanent decision either way. A primary-plus-backup arrangement adds SKU complexity — I've gone back and forth on whether it's worth it. Then 2022 happened. Redundancy isn't elegant, but it's cheaper than a stopped job.
Bottom line: branded costs more per unit and less per project. Private label is the reverse. Pick whichever risk you can actually absorb — and be honest with yourself about which one that is.