How to Choose Smart Lighting for Wholesale: 7 Questions from a Buyer Who's Paid for the Answers

Smart lighting looks simple from the outside. A few connected switches, some fixtures, an app on your phone. Then you start sourcing for wholesale, and you quickly find out there's an entire hidden layer — driver compatibility, firmware support, compliance paperwork, protocol decisions — that nobody mentions until it costs you money.

I've been a purchasing lead handling lighting and control orders for six years. I've personally made — and documented — 14 significant mistakes totaling roughly $46,000 in wasted budget. Now I maintain our team's pre-order checklist. This FAQ is that checklist, minus the tuition you'd normally pay to learn it.

One note before we get into it: I'm a procurement person, not an engineer. These answers come from real orders and real mistakes, not from a lab bench.

Here's what we'll cover:

• What actually makes smart lighting "smart"?
• Can Savant controls work with fixtures from another manufacturer?
• What specs really matter for downlight sourcing?
• What's the catch with spotlight private label programs?
• Which compliance certifications should I look for?
• Who handles firmware after I sell products with my brand on them?
• Zigbee or Wi-Fi — how do I choose for my wholesale line?

1. What actually makes smart lighting "smart"?

Honestly, "smart lighting" has become a marketing term. It gets applied to everything from a single connected bulb to a full commercial control system. Here's how I explain the difference to my customers, because it affects what you should stock and what you should promise.

A system coordinates devices. When we talk about a Savant lighting system, we're talking about switches, dimmers, sensors, and fixtures that work as one ecosystem. Someone walks into a room, the occupancy sensor tells the dimmer, the dimmer adjusts the driver, and the scene shifts based on time of day. Nobody's pulling out a phone. That's a system.

A collection of connected fixtures isn't a system. Each piece might have its own app. Each might respond to voice control. But they don't cooperate — so the experience gets worse as you add devices, not better.

Why does this matter for wholesale? Because your customers are buying an outcome: lights that do the right thing without micromanagement. If your product line can't deliver that, the support calls will quietly eat your margin.

2. Can Savant controls work with fixtures from another manufacturer?

Short answer: yes, in most cases. The longer answer includes a warning I learned the hard way.

"Compatible" is the most dangerous word in lighting. In 2022, we ordered 320 downlights from a manufacturer whose datasheet said "TRIAC dimmable." They were going into a project with Savant in-wall dimmers. The samples looked great. The full order looked great at the warehouse. Then the contractor called: buzzing at 25% brightness, lights dropping out below 15%.

I'm not an electrical engineer, so I can't analyze the driver circuit. What I can tell you from a procurement perspective is this: "TRIAC compatible" usually means the fixture worked with one specific dimmer in the supplier's lab. Not with your dimmers.

What we do now:

• Ask for a verified compatibility test using the exact dimmer model we plan to sell.
• Check the dimmer's minimum load requirement against the fixture's wattage — smart dimmers often need a minimum load to stay stable.
• Order three samples and test them together before committing to volume pricing.

The sample test has caught seven compatibility problems in the past 18 months. Three samples cost a few hundred dollars. A retrofit in the field costs thousands.

3. What specs really matter for downlight sourcing?

When I first started doing downlight sourcing, I treated spec sheets as complete technical documents. They're not. They're marketing documents with numbers in them.

From my perspective, three specifications tell you more than everything else combined:

• Driver lifetime at operating temperature. 50,000 hours at 25°C is a very different story at 60°C case temperature — and in a sealed ceiling cavity, the driver gets hot.
• Low-end dimming behavior. A fixture that dims to 5% in a lab can still flicker at 12% with a real-world control setup.
• R9 value. CRI 90 is pretty much table stakes now. R9 measures saturated red rendering, and it's the line that separates decent color from genuinely good. It's also rarely on the first page of a datasheet.

And here's something vendors won't tell you: those datasheet numbers usually come from a lab sample, not from production batches. Ask whether the specs were verified on actual production units. That one question has revealed more about supplier quality than any factory audit I've been on.

4. What's the catch with spotlight private label programs?

Before you put your brand on someone else's hardware, it's worth understanding what "private label" actually includes.

From the outside, it looks like a logo deal: pick a spotlight, add your brand, put it in the catalog. The reality is that a smart spotlight is also software. You're private labeling the firmware, the app experience, and the long-term maintenance — whether the contract mentions it or not.

I found this out the hard way. In my first year (2019), I approved a spotlight private label order that looked great on paper. Eight months later, the factory pushed a firmware update that changed how the fixture responded to a standard scene command. We had no agreement on update control, no visibility into the release process, and a customer whose installation suddenly behaved differently than specified. A $9,800 order became a trust problem that outlasted the relationship.

None of this means private label is a bad move — plenty of buyers do it well. The point is that software deserves the same rigor as hardware specs. The program we work with now (Savant's B2B OEM/private label support) treats firmware governance as part of the agreement, not an add-on.

If a supplier can't explain their firmware process in writing, keep looking. The hardware might be perfect today, but a smart lighting product lives for years through updates — and that lifecycle is part of what you're buying.

5. Which compliance certifications should I look for?

This is where I risk sounding boring on purpose, because the cost of skipping this question isn't boring at all.

First, safety. Look for UL or equivalent certification on the specific model you're buying — not just on the factory's other products. The listing needs to cover exactly what you're importing.

Second, radio. If the fixture has a Zigbee, Wi-Fi, or Bluetooth radio, it's an intentional radiator and needs FCC Part 15 authorization in the U.S. market. Ask for the FCC ID and check it in the FCC's online database. I used to treat this as "the factory's problem." It's not — importers have their own obligations.

Third, claims. If a supplier hands you a marketing line like "50% energy savings," ask for the test report. Per the Federal Trade Commission's business guidance on advertising (ftc.gov/business-guidance/advertising-marketing), claims have to be truthful and substantiated. If your brand is on the product, that claim is yours — the FTC doesn't care which factory wrote it.

I'm not a lawyer, so take this with a grain of salt. What I can tell you from procurement is that suppliers who get defensive when you ask for evidence tend to have a reason.

6. Who handles firmware after I sell products with my brand on them?

Here's the question nobody asks in the first sourcing conversation — and the one I'd go back and change if I could.

A smart lighting product doesn't ship and then get forgotten. It gets firmware updates for years: security patches, compatibility fixes, behavior improvements. If you sell it under your brand, your customers come to you when something misbehaves. You own the experience, whether you planned to or not.

In March 2023, a customer called about a spotlight we'd sold fourteen months earlier. The app had stopped connecting. When we contacted the factory, we learned they'd updated their cloud API, and the older firmware needed a new release. Who was responsible for releasing it? We didn't have access to the tooling. The factory assumed someone on our side was managing the software. We assumed they were. Nobody was.

The fix isn't complicated — it just has to be written down: who controls firmware releases, how updates are tested and announced, and what happens when a product reaches end of life. Any B2B lighting manufacturer with real OEM experience can answer those questions in an afternoon. If they can't, I'd treat that as a strong signal.

7. Zigbee or Wi-Fi — how do I choose for my wholesale line?

If you're building a smart lighting product line, the protocol choice is one you'll live with for years. Here's the way I think about it.

Zigbee, from my perspective, is the better backbone for lighting — especially for larger installations. It's a low-power mesh protocol built for dense device counts. Hundreds of fixtures can talk to each other without depending on the customer's Wi-Fi network, and it degrades gracefully: if one node drops, the mesh routes around it.

Wi-Fi is easier for small residential upgrades. No extra hub, familiar setup, and customers already have a router. But it has a congestion ceiling. Every Wi-Fi fixture competes for network airtime with phones, laptops, TVs, and access points. In a commercial building with dozens of fixtures per floor, that becomes a real problem.

Here's something vendors won't tell you: "Zigbee compatible" doesn't mean it works with any Zigbee gateway. The radio layer is standardized, but the application layer can still differ between implementations. That's why a Savant lighting system qualifies specific fixtures and modules rather than trusting the Zigbee logo alone. We've started doing the same.

Matter is changing part of this picture, and in a few years the interoperability conversation may look completely different. But as of early 2025, I still verify device compatibility on the specific system I'm recommending. The promise is getting closer; the reality just needs one more check.