Let's Talk About the Elephant in the Spec Sheet
The spec sheet says Cooper Lighting. But when you start digging, you find out Eaton sold the entire lighting division to Signify back in 2020. And suddenly a bunch of questions come up:
- Is Cooper Lighting still a real brand, or just a label on a box?
- Will replacement parts still be around in five years?
- Do the controls I'm specifying work with the sensors I already have?
- And why does every distributor give me a different answer to all of the above?
I run procurement for a mid-sized facility management company. We order somewhere between $80,000 and $120,000 in lighting products per year across 12 commercial properties. For the past six years, I've tracked every order—part numbers, prices, lead times, failure rates—in our internal cost system. So when the "Eaton sold Cooper Lighting to Signify in 2020" news cycle hit, I didn't just nod and move on. I audited our installed base to figure out what that deal actually changed for us.
Short answer: less than you'd think, but more than you'd expect.
What the 2020 Acquisition Actually Changed
The handoff between Eaton and Signify didn't change product names overnight. Halo, Metalux, WaveLinx—those sub-brands stayed in place. For us, the immediate impact wasn't about the fixtures at all. It was about what happened around them.
Channel Confusion
Distributors we'd used for years suddenly had to re-qualify as Signify partners. Sales reps got reassigned. Quotes started coming in slower. For about eight months, I had more pricing uncertainty than I've seen in a decade of doing this job.
Controls Compatibility
This was the big one. When Eaton owned Cooper, the controls roadmap had one trajectory. After Signify took over, the integration path shifted. We had to re-verify which cooper lighting control components worked with the Zigbee motion sensors we'd standardized on back in 2018.
Here's the thing nobody puts in the spec sheets: compatibility isn't just about wireless protocols. It's about voltage, dimming curves, mounting configurations, and a dozen other variables that only surface after you've already committed to a product.
Brand Architecture Confusion
Since the acquisition, the public-facing branding has been... let's call it "evolving." You see "Cooper Lighting Solutions" in some places, "Signify" in others, "Halo" and "Metalux" as product lines in between. For someone who isn't in the industry full-time, decoding that is genuinely hard.
I can't tell you how many procurement colleagues have asked me, completely seriously, "Wait, does Eaton still make Cooper products?" The answer is no. Eaton sold Cooper Lighting to Signify for $1.4 billion. The deal was announced in October 2019 and closed in March 2020.
But here's what most people get wrong: even though Signify is the parent company behind Philips-branded products, the Cooper Lighting product lines retained their own engineering teams, their own catalogs, and largely their own supply chains. Philips didn't rebrand everything overnight. And as far as I can tell, they haven't tried to.
What the Confusion Costs in Real Money
Brand confusion and controls uncertainty aren't abstract problems. They have direct, measurable costs. Here's what I've seen in our own portfolio and in conversations with other buyers:
Cost #1: Compatibility Rework
We approved a retrofit of a 20,000-square-foot office floor in Q2 2023. The spec called for Cooper Lighting LED panels with a specific driver, plus a Zigbee motion sensor in each zone. The contractor ordered panels and sensors separately, which was the first mistake. When they went to install, the sensors wouldn't join the network.
The sensor firmware version shipped that quarter wasn't compatible with the panel drivers we'd specified. We had to manually flash every single sensor. That added about 14 hours of labor—roughly $3,800 in costs we hadn't budgeted for.
The numbers said the sensor we picked was the right one—same Zigbee chipset, same profile, same join mechanism. Something felt off about the sparse documentation compared to the alternative. I went with the numbers anyway. I should've listened to the gut that was questioning the vendor's documentation. Turns out, "lightly documented" was a preview of "firmware incompatibility."
Cost #2: Spot vs. Flood Specification Errors
The spot light vs flood light distinction is one of the most misapplied specification choices I see. It sounds elementary. A spot has a narrow beam; a flood has a wide one. But in practice, beam angles are sold differently across product lines, and the same fixture can be configured in six different variations.
I've seen specs where someone wrote "flood light" for a narrow corridor accent application, and the distributor—correctly interpreting the literal words—quoted flood fixtures with a 90-degree beam angle. The install looked like a visual mess, and the client demanded a redo. That's not a product problem. That's a spec problem. And it's entirely avoidable if you confirm beam spread on each line item before ordering.
Cost #3: The Cheap LED Bulb Trap
I know the "bulb led" search results look tempting. A $2.79 LED bulb that claims to replace a 60-watt incandescent? That's hard to pass up, especially when you're managing a tight budget.
But if you're buying for a commercial facility, the $2.79 consumer bulb is almost never the right call. The difference between that and a $7–$12 commercial-grade LED bulb goes well beyond the sticker price:
- Lumen maintenance over rated life
- Color consistency between batches
- Driver reliability in enclosed fixtures
- Warranty and support terms
There's also a sharp line between what a manufacturer can legally claim and what's just marketing. Per FTC advertising guidelines, energy-savings claims have to be truthful and substantiated. That's why you'll see carefully worded footnotes referencing DOE test procedures. The claims are true—under those test conditions. Real-world performance, with your specific drivers, dimming setups, and operating hours, can vary. That's not a manufacturer lying. It's just that lab conditions aren't your conditions.
In practice: a cheap bulb that fails at 20,000 hours of a 50,000-hour rated life costs you labor, disposal, and downtime. In high-ceiling environments, the replacement labor alone can exceed ten times the bulb's original price. That's a total-cost-of-ownership failure, not a "great deal."
Cost #4: Controls Ecosystem Lock-in
If you choose a proprietary controls system, you're implicitly betting on that vendor's roadmap. I want to be careful here because there are legitimate reasons to choose a proprietary system. The software might be genuinely better. The integration depth might be superior. The local dealer support might be excellent.
But you should make that choice deliberately. When Eaton sold Cooper Lighting to Signify in 2020, customers who had invested heavily in Eaton's legacy controls platform had to make hard decisions: migrate to the Signify roadmap, stay on the legacy platform, or switch vendors entirely. Every option costs money.
The alternative isn't "no controls." That's a false choice. The alternative is evaluating controls platforms the way you'd evaluate any long-term infrastructure bet: check the protocol (Zigbee, DALI, 0-10V, wireless proprietary), verify the backward compatibility claims, and ask about end-of-life policies before you commit, not after.
What We Changed in Our Procurement Process
I didn't have a neat epiphany that fixed everything. I made mistakes, wrote them off as experience, and gradually refined our approach. Here's what actually works:
1. Verify Product Lineage
For any Cooper Lighting product we spec, we confirm whether it's still in Signify's current catalog and what the replacement plan looks like. Signify has been consolidating some of the older Cooper SKUs. A fixture that was in the 2019 catalog isn't necessarily still manufactured in 2025.
2. Map the Compatibility Chain
Every order goes through a compatibility review: fixture → driver → sensor → controller → gateway. If any link in that chain has a question mark, we get written confirmation from the distributor before we issue the PO. I learned that one the hard way with the Zigbee motion sensor firmware issue.
3. Calculate Total Cost of Ownership
This sounds more burdensome than it is. We use a simple spreadsheet that tracks:
- Unit cost × quantity
- Expected rated life (hours) vs. annual operating hours
- Lumen depreciation curve, if available
- Labor cost per replacement
- Energy cost per kWh × wattage × operating hours
That's it. Fifteen minutes per line item. We caught a $6,200 energy-cost difference on a 40-fixture order that a simple per-unit price comparison would've missed completely.
4. Ask the Honest Question
I've learned to ask distributors and manufacturer reps a direct question: "What is this product not good at?" The reps who give an honest answer—who say things like, "this sensor is great for open offices but struggles in high-bay"—earn my trust for everything else. The reps who say "it handles anything" go on my watch list. I've never once been burned by a product that an honest rep warned me about. I've been burned many times by products that were oversold.
That's the part that feels counterintuitive, especially in a market where every supplier wants to sound like they can do everything. But I'd rather work with a specialist who knows their limits than a generalist who overpromises.
Bottom Line
The Eaton-to-Signify transition has been, on balance, less disruptive than I feared it would be. Cooper Lighting's sub-brands are still producing solid fixtures. The controls ecosystem is evolving, not dying. But the transition created enough confusion—in the channel, in documentation, and in people's heads—that you can't afford to buy on autopilot.
I don't have hard data on industry-wide lighting order error rates. What I can say anecdotally, from six years of tracking our own purchases, is that 8–12% of our lighting-related headaches came from not asking the compatibility question early enough. We've cut that number significantly just by adding the verification step.
As for the spot vs. flood mistakes and the LED bulb gambles: you'll pay for getting them wrong, either in rework or in lighting quality. That's not a dramatic statement. It's just math.
This approach worked for us, but our situation was specific: a mid-size FM company with predictable retrofit cycles and solid distributor relationships. If you're a large enterprise managing thousands of SKUs, or a small contractor working on tight margins, your mileage will vary. The TCO framework scales fine. The specific vendor choices probably won't.
