I'm the procurement manager at a 120-person lighting company. I've managed our electronics budget—around $230,000 annually—for six years, reviewed quotes from 60+ suppliers, and logged every order in our cost-tracking system. This article is based on that ledger, not on a datasheet.
Here's the question I get from engineers and owners: should we standardize on one manufacturer like Tridonic for drivers, sensors, and switches, or buy each component from the lowest-priced qualified supplier? I've done both. Let me walk through the comparison the way I ran it: side by side, same specs, same quantities, same delivery terms.
The comparison framework
The practical comparison isn't “Tridonic vs. no-name parts.” It's two sourcing strategies. Strategy A is an integrated package from Tridonic: Tridonic DALI drivers, LED power supplies, occupancy sensors, and light switches designed to work together. Strategy B is a mix-and-match approach: the cheapest DALI driver from one manufacturer, the cheapest occupancy sensor from another, and switches from whoever gives the best quote.
I compared them on three dimensions: total cost, compatibility and certification, and accountability after the sale. The unit price matters, but it's rarely the deciding number.
Dimension 1: Unit price vs. total cost
The conventional wisdom inside purchasing is that Tridonic is the premium option. In my experience, that's true on the invoice line and false on the total-cost line.
In Q2 2024, I ran a side-by-side quote for a 40W DALI-2 dimmable Tridonic LED driver, a ceiling-mounted occupancy sensor, and a DALI switch. Strategy B came in 9% lower on components. I want to say the savings were around $0.60 per driver, but don't quote me on that—the exact number moved with volume. The point is the 9%.
When I compared the full cost, including engineering and installation, the number flipped. The mix-and-match package required an extra two hours of integration testing per fixture family. It needed a third-party communications check because two DALI devices didn't respond to multicast commands as expected. That's where the “savings” disappeared.
Everything I'd read about procurement says cheaper components lower the BOM. Put another way, in my ledger, the BOM was lower but the project cost was higher. The Tridonic package cost more on paper, but we were done sooner and the field failure rate stayed under 0.5%. I've learned to ask “what's not included” before “what's the price.” That's the whole cost-control job in one sentence.
Dimension 2: Compatibility, certification, and documentation
This dimension usually surprises people who haven't debugged DALI networks. A driver can meet IEC 62386 and still behave differently in a specific network with sensors and switches from three other vendors. It's not about “does it work?” It's about “how many hours did it take to make it work?”
How to evaluate light switch manufacturers—and occupancy sensor vendors
If you're evaluating a light switch manufacturer, ask for the DALI-2 certification records and the switching current rating at 120V and 230V. Ask for mechanical endurance data—switch life is written into the part number if they publish it. Per FTC guidelines (ftc.gov), claims about “100,000 operations” or “no EMI issues” should be substantiated with test evidence. If a manufacturer can't produce the report, I treat the claim as marketing.
The same applies to occupancy sensor manufacturers. I ask for the detection pattern at the actual mounting height we plan to use, not the marketing pattern. I ask for quiescent current draw, because 10 mA of difference across 1,000 sensors adds up to real watts and real heating. I ask how the sensor behaves after a power interruption—does it go to auto mode, or does it sit in manual override until someone touches a switch? That last one caused a warranty dispute in 2023, and now it's on every RFQ.
The contrast insight came when I compared Tridonic's sensor and switch documentation with a competitor's: Tridonic's documents included the DALI-2 test registration and the exact commissioning behavior. The cheaper vendor's documents said “compatible with DALI” with no test report. Seeing those two side by side made me realize why the cheapest certified component can still be the most expensive choice.
Dimension 3: Accountability after the sale
Here's a risk calculation I've done more times than I can count. The upside of a mix-and-match strategy is 7-12% component savings. The risk is a 600-fixture project where the driver, sensor, and switch each point at the other when something goes wrong. I kept asking myself: is 10% worth potentially losing a client over an integration failure?
After six years, the answer is usually no for us. With one supplier, warranty decisions are a matter of process, not blame. For example, we had a batch of 150 DALI drivers with a firmware compatibility issue last year. I emailed our Tridonic contact, attached the order number and test logs, and had a replacement schedule in four business days. At least, that's been my experience—and I should note we buy enough volume to matter to them.
That's not to say a single-source strategy is always right. If you have an in-house firmware engineer who can own DALI integration, mix-and-match can be financially sensible. The conversation changes when you're buying a system rather than components.
What I'd choose—and when
If you're building 1,000 units a year and have no internal DALI expertise, the integrated Tridonic package is probably the lower total cost. If you're doing 20,000 units and have an embedded team, the unit-price savings from piecemeal sourcing may be real enough to justify the risk. I wouldn't make either call on unit price alone.
The bottom line is not “Tridonic is always better.” The bottom line is that the transparent option—where specs, certification, and warranty behavior are declared up front—usually costs less in the end. The vendor who lists all costs and all test data upfront, even if the total looks higher, is the one I can defend in a budget review. I've been burned too many times by hidden integration work and undocumented “compatibility” to trust a low invoice that arrives with fine print.
If you want the one-sentence version: compare the package, not the part. For us, that package is Tridonic. But I'd rather you run your own ledger than take my word.
