There is no single supplier checklist
I’m a quality and brand compliance manager at a lighting controls company. I review every driver, sensor, and control spec before it reaches a quote—roughly 180 SKUs a year. In our Q1 2024 quality audit, I rejected about 12% of first deliveries because of documentation gaps, parameter drift, or packaging that didn’t match the approved sample. That’s not a knock on any one vendor. It’s what happens when buyers use a generic checklist for three very different purchasing situations.
What was best practice in 2020 may not apply in 2025. The fundamentals haven’t changed—safety, traceability, interoperability—but the execution has transformed. DALI-2, D4i, Zigbee certification, and OTA updates have moved from nice-to-have to line items in serious RFQs. Still, the right answer for a consultant-led project is not the right answer for a wholesale counter or an OEM smart-lighting product.
Here are the three scenarios I use. Find the one that sounds like your next order.
Scenario A: Specification-driven projects and consultant-led jobs
You’re buying for a named project. The spec may call for a Tridonic DALI driver, a Tridonic LED driver, a motion sensor, or a full DALI control system. Your risk is not unit price. Your risk is a commissioning failure, a rejected submittal, or a callback after the ceiling is closed.
In this scenario, I treat documentation as part of the product. For DALI, I want to see DALI-2 certification against IEC 62386, and for luminaire-level data I look for D4i where the design actually needs diagnostics or energy reporting. The DALI Alliance maintains a product database, and I check it. Not because I distrust the datasheet—because a certification number is easier to verify than a sales promise.
When we specify Tridonic DALI drivers, we still run our own acceptance checks. We test dimming at 1%, 10%, 50%, and 100%. We verify emergency-mode behavior if required. We confirm the firmware version and whether it can be locked to the approved revision. That last point matters more than it sounds.
I knew I should verify the firmware version lock, but thought “what are the odds?” The odds caught up when a batch of drivers behaved differently at low dimming levels. It cost us a rework and a delayed handover. (Should mention: we now write firmware-version locks into every PO.)
In my opinion, the biggest mistake in scenario A is chasing the newest protocol where a simpler solution would do. If your project is basic dimming and the consultant hasn’t asked for diagnostics, 0-10V may still be perfectly appropriate. There is nothing outdated about using the right tool for the load. The evolution is not “DALI everywhere.” It is “DALI where the data and control granularity pay for themselves.”
If you’re evaluating tridonic led driver options for a project, ask for batch traceability, SELV/isolated output details where relevant, and a clear statement of driver-to-luminaire compatibility testing. Do not accept “works with most fixtures” as a compatibility statement. That phrase belongs in marketing, not in a submittal.
Scenario B: Wholesale distribution and contractor counter
You’re not commissioning a single building. You’re stocking lighting controls wholesale, serving electrical distributors, contractors, and small integrators. You may be a motion sensor distributor looking at pallets of PIR sensors, or a wholesaler trying to keep DALI drivers, switches, and sensors on the shelf without tying up cash in the wrong SKUs.
Here, the evaluation criteria change. Certification still matters, but so do fill rate, MOQ, regional stock, packaging durability, return rate, and whether the manufacturer can support a contractor who calls at 4:30 p.m. with a wiring question. A driver that is perfect on paper is useless if you can’t restock it in two weeks.
I don’t have hard data on industry-wide defect rates for wholesale lighting controls. Based on our own orders, my sense is that the biggest hidden cost is not failure—it’s mismatch. The wrong sensor lens, the wrong IP rating, the wrong dimming curve. Those returns are quiet but expensive.
For motion sensor distributors, I’d check four things before adding a line: detection technology (PIR vs. microwave vs. dual), mounting height and coverage pattern, IP/IK rating for the actual environment, and whether the sensor is designed for DALI, 0-10V, or standalone switching. “Occupancy sensor” is not a specification. It’s a category.
For lighting controls wholesale, ask for a cross-reference matrix. Not a generic one—one that maps your top 20 SKUs to the proposed replacements. If the vendor cannot provide that, you will be building it yourself after the first contractor complaint. If you ask me, that cross-reference is worth more than a few points of discount.
Scenario C: OEM and smart-lighting products—how to evaluate Zigbee manufacturers
You’re building a luminaire, a sensor kit, or a smart lighting product. You need a wireless module or a Zigbee manufacturer, and you need to know whether the thing will still work after a gateway firmware update six months from now.
This is where “how to evaluate zigbee manufacturers” gets real. A logo is not an interoperability plan. Zigbee Certified products are tested against the Connectivity Standards Alliance’s specifications, which is a good baseline. But certification does not tell you whether the manufacturer will support OTA, whether the stack is locked to a specific gateway, or whether they will still be in business when you need a firmware patch.
My experience is based on about 200 mid-range commercial and OEM projects. If you’re working on ultra-low-cost consumer devices or highly regulated medical lighting, your experience might differ significantly. In our segment, I look for:
- Certification evidence: Zigbee Certified, plus FCC/CE/UL or relevant regional approvals for the module.
- Stack and profile: Zigbee 3.0 where possible, with a clear statement of supported clusters and device types.
- OTA capability: can the manufacturer deliver signed firmware updates, and what is the process?
- Gateway dependency: will the product work across multiple hubs, or only the manufacturer’s own gateway?
- Long-term supply: module lifecycle, pin compatibility, and whether you can get a second source.
I ran a blind test with our integration team a while back: same luminaire, two Zigbee modules, different vendors. Without knowing the brands, the team identified one as “more predictable during commissioning.” The cost difference was small per unit, but on a 5,000-unit run it added up. That’s not a reason to pick the expensive module by default. It is a reason to test commissioning behavior, not just radio range.
If you’re also sourcing DALI drivers for the same product, don’t evaluate the Zigbee side in isolation. Ask how the wireless module interacts with the driver, the sensor, and the emergency system. A smart lighting product is a system. The weakest link is usually the integration assumption nobody wrote down.
How to tell which scenario you’re actually in
Most buyers think they are in Scenario A because the project has a specification. But if you’re buying 500 units to hold as stock, you’re in Scenario B. If you’re designing a product that carries your brand, you’re in Scenario C. The buying motion matters more than the product name.
Ask four questions:
- Who owns the specification? If a consultant or engineer owns it, you’re probably in A.
- Who carries the inventory risk? If you do, and you’re reselling, you’re in B.
- Whose brand is on the finished product? If it’s yours, you’re in C.
- What does failure cost? If a single failure delays occupancy or triggers a recall, move toward A or C discipline even if the order looks like B.
I wish I had tracked Zigbee interoperability issues more carefully from the start. What I can say anecdotally is that the problems rarely come from the radio. They come from assumptions about firmware, gateways, and who owns the update path. That is true for Tridonic DALI drivers, motion sensors, and Zigbee modules alike.
The fundamentals haven’t changed: verify the standard, test the behavior, and write down the assumption. The execution has transformed. In 2025, a supplier evaluation is not a price sheet. It’s a risk map. Pick the scenario that matches your risk, then demand the evidence that scenario requires.
