Connected architecture: DALI-2 · 0-10V · occupancy · daylight harvesting

Cooper Lighting Systems: Three Buying Scenarios (And How to Tell Yours Apart)

Which Lighting Problem Are You Actually Solving?

Purchasing has one uncomfortable truth baked into it: almost every problem has more than one right answer, and the answer depends on which problem you're actually facing.

I run purchasing for a company of about 400 people across three locations — roughly 60 to 80 orders a year, spread over eight vendors. Between 2021 and 2024 we did three facility refits. Every single one opened with the same question — which fixture do we buy — and every single one turned out to be a different problem wearing a fixture-shaped disguise. One was really about brand consolidation. One was about protocol compatibility. And one, embarrassingly, was about geometry: we bought perfectly good fixtures and put them where they couldn't do their job.

So instead of writing one recommendation, here are three scenarios. Find yours first. The advice only makes sense after that.

  • Scenario A: You're standardizing across sites and want one system, not one fixture.
  • Scenario B: You already have fixtures. You're adding controls.
  • Scenario C: Your request doesn't fit a catalog line item at all.

Scenario A: Multi-Site Standardization

This is the scenario where a name like Cooper Lighting Systems actually means something. And here's where I got it wrong at first.

When I first started buying lighting in 2021, I treated every fixture as a standalone SKU. Lowest unit price wins, order it, done. Three refits later, I understand that the value in a portfolio brand isn't in any single product — it's in the fact that a downlight, a high-bay, an exit sign, and a wall pack can share one warranty, one rep relationship, and one controls architecture.

Cooper's portfolio covers a lot of ground: Halo for residential and commercial downlighting, Metalux for high bays and linear fixtures, plus outdoor, emergency, and exit signage. The Metalux SPHB high-bay line shows up constantly in warehouse and shop-floor quotes. If you're specifying SPHB against a competing high bay, resist the urge to compare lumens-per-watt alone. Ask three questions instead:

  1. What's the L70 rating, and is it based on LM-80 data collected at the actual drive current?
  2. What driver platform does it use, and can it be field-replaced?
  3. Does it ship with a controls-ready option, or will you be adding that later?

That third question is where most of my rework came from. We installed a batch of high bays in 2022 without controls ports, then paid an electrician to come back eighteen months later and add sensors. That second visit cost roughly as much as the controls themselves (this was 2023 pricing — assume it's moved since).

One prevention note: before you commit the whole portfolio, run one site. Order the fixtures for a single floor or a single aisle, install them, and live with them for a month. Ten percent more time upfront beats a full retroactive swap. Every time.

Also worth knowing: Signify acquired Cooper Lighting in 2020. That matters for contracts, warranty administration, and rep continuity. It's not a reason to avoid the brand — it's a reason to confirm who your service contact actually is before signing a three-year standardization deal.

Scenario B: Adding Controls to Fixtures You Already Own

This is the Zigbee conversation. And the conventional wisdom is mostly wrong here.

Everything I'd read said to buy the cheapest compatible controller. In practice, with lighting controls, compatible is doing an enormous amount of work in that sentence.

Zigbee controllers are built on the Zigbee 3.0 specification, which the Connectivity Standards Alliance maintains and which sits on top of IEEE 802.15.4 at 2.4 GHz. That sounds reassuringly standardized. It is — at the radio and transport layer. It is not a guarantee that any controller will talk to any fixture's driver in the way you need. Interoperability is a certification and implementation question, not a protocol-version question.

From the outside, buying controls looks like a device purchase. The reality is you're buying a support relationship. When a room won't dim correctly at 6 a.m. on a Tuesday, someone has to own that. If your controller is from one vendor and the fixtures are from another, you will personally become the integration layer. I've been that integration layer. It's not a good use of a purchasing department's week.

Cooper's own wireless platform (WaveLinx) is built on Zigbee, which is why a mixed deployment often ends up being more work than the catalog suggests. That's not a knock on open standards — it's an observation about where the troubleshooting burden lands.

What actually helped us: writing a compatibility requirement into the quote request before anything was purchased.

"Vendor must confirm in writing that the proposed controller is certified interoperable with the specified driver platform, and must identify the party responsible for on-site commissioning support."

Two of the five vendors we asked couldn't put that in writing. That told us more than any datasheet did.

If you're doing networked controls at any scale, also check the DesignLights Consortium's Networked Lighting Controls qualification — utility rebates in a lot of territories are tied to it, and a controller that doesn't qualify can quietly kill a rebate worth thousands.

Scenario C: Requests That Don't Fit a Catalog Line

This is the one nobody warns you about. Two flavors show up most often.

The "downlight, but outdoors" problem

People assume an outdoor downlight is just an indoor downlight with a different label. What they don't see is the enclosure rating that determines whether it survives a year.

For open-air soffits and covered entries, you're working inside NEC Article 410.10 — the location classification for damp versus wet. A damp-rated fixture is fine under a roof overhang. A fixture hit by rain, sprinkler runoff, or washdown needs to be rated for wet locations and carry an enclosure rating under IEC 60529 — IP65 or IP66 depending on the conditions. Indoor cans rated for indoor use will fail, and they'll fail after the warranty window in my experience, not during it.

The "indirect light" problem

The one that genuinely surprised me. We had a request to light a nursing room and a small greenhouse off the break area. Someone had proposed a grow-light setup and wanted to know "how to get indirect light with grow lights."

My initial approach was completely wrong. I thought: brighter fixture, moved further away. That's not indirect light — that's just dim light with a longer throw.

Indirect lighting is a surface decision, not a fixture decision. The direction the photons leave the fixture matters less than what they bounce off. Standard design guidance puts office surface reflectance at roughly 70–80% for ceilings, 50–70% for walls, and 20–40% for floors. If you're bouncing light off a dark-painted wall, you lose most of it before it reaches the plant — no fixture specification will save that.

And here's the part that isn't in any lighting catalog: horticultural needs and office needs are different design problems. What a plant needs (intensity at the canopy, specific spectrum) doesn't map cleanly onto what a room needs (glare control, uniformity, color rendering for people). A grow light chosen for plants and a luminaire chosen for people are rarely the same device.

The prevention move here: ask what the light is landing on. If the answer involves a reflective surface you're adding anyway, you may need a smaller fixture than you budgeted for. If it involves a dark surface, you're going to spend money twice.

How to Tell Which Scenario You're In

Ask three questions in this order, and stop at the first one that isn't obvious.

1. Is this more than one building? If yes — Scenario A. You're buying a system, not a fixture, and the total cost question dominates the unit price question. Budget the time to run one site first.

2. Are the fixtures already installed? If yes — Scenario B. The question is no longer what to buy but who supports it. Get the compatibility confirmation in writing before the purchase order, not after.

3. Does at least one person in the request have a different definition of "done" than you do? If yes — Scenario C. You're not buying a fixture, you're resolving a design problem. Do a site walk before you open a catalog.

If none of those land clearly, you're probably in Scenario A but haven't admitted it yet. That happened to me twice. The second time cost us a five-figure rework bill.

Five minutes of verification beats five days of correction. It's not a slogan — it's the only purchasing lesson I've never regretted.