What a $180K Retrofit Taught Me About Motion Sensor Manufacturers and OEM vs. Private Label

Q2 2024: The Budget Nobody Wanted to Own

I'm a procurement manager at a 220-person facilities services company. In Q2 2024, I inherited a $180,000 commercial lighting retrofit budget across six sites. That included 1,200 occupancy sensors, about 40 lighting control panels, and a lot of old switches that were failing one by one. The goal was simple: cut energy waste, standardize controls, and stop the maintenance team from chasing parts every week.

What I didn't expect was how much time I'd spend on one question: OEM or private label? Specifically, for motion sensors and lighting controls. I went in thinking private label would save us 20-30%. I came out with a different answer.

Before that project, our lighting controls were a patchwork. Three brands of sensors, two gateways, and a spreadsheet that nobody trusted. Every time a tenant moved out, we'd lose another afternoon figuring out which zone map was current. Efficiency wasn't a buzzword for us—it was the difference between a proactive maintenance team and a reactive one.

Eight Vendors, Three Months, One TCO Spreadsheet

I started by listing every motion sensor manufacturer and controls supplier we'd used since 2021. Eight vendors made the first cut. I built a TCO spreadsheet that tracked unit price, MOQ, lead time, firmware and commissioning support, warranty length, return rates from our maintenance system, and hidden fees.

The spreadsheet had five tabs: one for sensors, one for controls, one for gateways, one for labor, and one for risk. I forced myself to fill in every cell, even if the number was a guess. I also added a column for what I called the 'phone call cost'—how many hours per month we'd spend managing each vendor.

Two vendors stood out.

Vendor A was an OEM manufacturer. They quoted $48 per sensor, $2,400 for a custom firmware profile, and 10-week lead time. They offered a 5-year warranty and said they could private-label the sensors with our company logo. Their controls spoke Zigbee and had DLC Networked Lighting Controls listed products. Not cheap, but the quote was clear.

Vendor B was a private label supplier. They quoted $31 per sensor, 4-week lead time, and no setup fee. Their pitch was straightforward: same factory as the big brands, just without the brand tax. I almost signed. The difference on 1,200 sensors was $20,400 before any negotiation.

I went back and forth for two weeks. Vendor B's savings would cover two more sites. Vendor A's warranty and support felt safer. I kept asking myself: is $20,400 worth potentially blowing the install schedule?

For reference, publicly listed prices in January 2025 for commercial occupancy sensors look like this: basic private-label units run $12-$30 each; OEM or DLC-listed networked sensors run $35-$75 each; Zigbee modules add $8-$15. Installation labor averages $25-$60 per device depending on ceiling type. These are ballpark figures from online distributor listings and manufacturer quote sheets—verify current pricing for your project.

The Hidden Fees That Didn't Show Up Until Page 4

Then I read Vendor B's fine print. The $31 unit price excluded:

• Firmware customization for our existing control zones: $2,500
• Zigbee certification support if we wanted to keep our network open: $1,800
• Rush replacement for DOA units: $45 per unit, shipped at our cost
• Commissioning support beyond a 1-hour call: $180/hour

That changed the math. Vendor B's TCO for year one was closer to $43,800, not $37,200. Vendor A was $57,600. Still a gap, but not as big. And Vendor A's price included commissioning support, a spare-parts kit, and a documented firmware path.

I'm not an electrical engineer, so I can't speak to every protocol detail. What I can tell you from a procurement perspective is that lighting controls OEM vs private label isn't a sticker-price decision. It's a support and compatibility decision.

I called two references for Vendor B. One said the sensors worked fine but the gateways dropped devices every few months. The other said support was responsive until the warranty claim, then went quiet. Neither was a dealbreaker on its own. Together, they pushed me to look harder at the risk column.

Where Current Lighting and Current Commercial Lighting Came In

While I was comparing vendors, our electrical contractor asked why we weren't standardizing on a known commercial lighting platform. We already had a few Current Lighting fixtures in two buildings. Their current commercial lighting controls worked with our existing Zigbee network, and the local rep had documentation for every SKU. I added them to the spreadsheet as a benchmark.

Current Lighting wasn't the lowest quote. But their current lighting commercial lighting ecosystem was already in our buildings. That mattered. We wouldn't need to train the maintenance team on a new app or buy another gateway. The efficiency gain was real: fewer SKUs, one support line, one warranty process.

That's when the efficiency argument clicked. The cheapest sensor isn't the cheapest system. Every extra vendor adds a login, a PO process, a spare-parts bin, and a phone call. For a 220-person company with six sites, that overhead adds up faster than the unit-price savings.

I also ran a quick scenario. If we used Current Lighting for all 1,200 sensors, the upfront cost was higher by about $16,000. But we'd eliminate one gateway, one training session, and roughly 6 hours per month of vendor management. At a loaded labor rate of $65 per hour, that's $4,680 per year. Over a 5-year warranty period, the gap narrows to about $7,000. Not nothing, but smaller than it looked on day one.

The Risk I Almost Underestimated

Vendor B agreed to match Vendor A's warranty on paper. But their lead time slipped from 4 weeks to 7 weeks after I asked for a small firmware change. The project couldn't wait. Our facilities team had already scheduled electricians for a narrow window between tenant moves.

I calculated the worst case: a 3-week delay would push commissioning into Q4, when overtime rates were 1.5x. That was roughly $6,800 in added labor. Best case: we saved $13,800. The expected value still said go with Vendor B, but the downside felt catastrophic. If the controls failed during a tenant event, my team would own that failure.

I chose a mixed approach. We used OEM sensors from Vendor A for the 480 sensors in critical zones—lobbies, conference rooms, and after-hours areas. We used private label sensors from Vendor B for the 720 standard corridors and storage rooms. But I added a clause: Vendor B had to provide a 5% spare kit and a 48-hour replacement SLA. They agreed, but only after we increased the order by 40 units.

That decision wasn't elegant. It created two spare-parts bins and two firmware versions. But it balanced savings with schedule risk. If I had to do it again, I'd probably simplify to one platform and accept the higher upfront cost. The management overhead was more than I modeled.

Six Months Later: What the Maintenance Data Showed

By January 2025, we had installed about 1,150 sensors—I'd have to check the exact number, maybe 1,180. The OEM sensors had 3 failures. The private label sensors had 22 failures. Our maintenance system logged each swap, and the average replacement took 25 minutes plus travel time.

That's a 4.4% failure rate for the private label units versus 0.6% for the OEM units. At $65 per truck roll, the private label failures added about $1,430 in labor. Add the spare parts and the higher commissioning time, and the private label savings dropped from $13,800 to roughly $9,200. Still positive, but not the 25% win I'd pitched to my director.

There's something satisfying about finally closing that spreadsheet. After all the back-and-forth, the mixed approach kept us on schedule and gave us a documented failure baseline. The best part: no more 3am worry sessions about whether a container of sensors would clear customs.

I should note that our sample size is small. Six months isn't a full reliability picture, and our private label units were installed in corridors with more foot traffic than some of the OEM zones. That said, the failure trend was consistent enough that I'd ask harder questions next time.

What I'd Tell Another Procurement Manager

First, motion sensor private label can work—but only for standard zones where compatibility and downtime are low-risk. If you're buying private label motion sensors, ask for the factory's DLC listing, the firmware version, and the exact replacement SLA. If they can't provide those, the savings are fake.

Second, motion sensor manufacturer relationships matter more than unit price when you have multiple sites. A manufacturer that supports commissioning and spare parts will save you more than a distributor that dropships boxes.

Third, run the TCO over 3-5 years, not one order. Include truck rolls, spare kits, gateway compatibility, and staff training. That's where the real number lives.

Industry reference: The DesignLights Consortium (DLC) Networked Lighting Controls Technical Requirements require qualified products to meet specific interoperability, energy monitoring, and cybersecurity criteria. Always verify current listings at designlights.org before specifying controls. For California projects, Title 24 Part 6 also sets mandatory occupancy sensing and control requirements. These standards are updated regularly—check the current version.

I'm still not a lighting designer. This gets into photometric and code compliance territory, which isn't my expertise. I'd recommend consulting a lighting engineer or your local code official before finalizing a controls spec. What I can tell you is how to evaluate the total cost.

At least, that's been my experience with retrofits. If your sites are simple and your downtime tolerance is high, private label might be the right call. But if efficiency is your competitive edge—and in facilities services, it is—then the cheaper unit price is only one line in the spreadsheet.

We're now standardizing on one commercial lighting platform for the next phase. Current Lighting is on the shortlist again, not because they're the cheapest, but because their controls already fit our buildings. That's the kind of efficiency that pays back every quarter.