On March 14, 2024, a pallet of 480 ceiling mounted occupancy sensors showed up at our warehouse. I opened the first carton, pulled out a unit, and flipped it over. The voltage label said 120V. Our spec sheet said 277V. I stood there for a second, holding it, and just said out loud: "Well, that's not right."
That moment kicked off two of the more frustrating weeks of my year. Not because the problem was hard to fix — it wasn't — but because I should've caught it before the purchase order ever went out. If you're sourcing occupancy sensors for a commercial project right now, I'd rather have you learn from my mistake than make it yourself. So let me walk you through it.
How it started: a "simple" sensor order
I manage quality and brand compliance for a lighting supplier. Part of my job is reviewing every sensor submittal that goes out the door — roughly 200+ unique items a year, across commercial, industrial, and retrofit work. I've been doing this for about four years.
Back in February 2024, we took on a project for a mid-size distribution center. The client needed occupancy sensors for three zones: a front office area (ceiling mounted, standard ceiling height), a warehouse floor with 18-foot ceilings (high bay), and two bathrooms with manual switches being replaced. Budget was $18,000 for the sensor package, install and commissioning included.
I sent out RFQs to four vendors. Three came back within a week. One came back in a day with a price 30% lower than the others.
Here's where I made the classic rookie mistake. I'd done this enough times to know better, and I still did it. I approved that lower quote because the product sheet said "commercial occupancy sensor." I assumed "commercial" meant the same thing to them that it meant to me. It didn't.
The decision that kept me up at night
Before that, I had a real struggle — the kind that doesn't seem like a big deal on paper but does in practice. We had two viable paths:
Option A: Go with the established vendor we'd used on three previous commercial builds. Reliable, documented specs, submittal packages that were easy to hand to the client. Pricing was fair but not the cheapest. Lead time was 4 weeks.
Option B: Go with a newer supplier whose quote was 30% lower and promised 2-week delivery. Their catalog listed ceiling mounted occupancy sensors, high bay occupancy sensors, and line voltage occupancy sensors — everything we needed, in one place.
On paper, Option B made sense. A 30% savings on $18,000 is $5,400. That's not nothing. But my gut said something was off, mainly because the spec sheet for their high bay line was thin — I'm talking two pages, no photometric data, no ASHRAE compliance reference.
I went back and forth for almost a week. Eventually I chose Option B — but with a compromise. I asked for a sample unit of each type (ceiling, high bay, line voltage PIR) before authorizing the full order.
Two of the three samples were fine. The third was the problem.
The turning point: what a "within tolerance" claim really means
The high bay occupancy sensor they sent was rated for 277V application, which matched what we'd asked for. But the internal wiring diagram showed the driver section was labeled 120-277V — a universal input. That sounds fine, right? Universal input = flexible.
Except the mounting base and the terminal block were sized for 120V conductor spacing. On a 277V commercial circuit, that's an installation code issue waiting to happen. When I flagged it, the vendor said the unit was "within industry standard."
I pushed back and asked for the UL file number. They sent a certificate for a different model. That's when I stopped negotiating and started writing the rejection email.
We rejected the full batch of 480 units — the 240 ceiling mounted occupancy sensors, the 180 high bay units, and the 60 line voltage units for the bathrooms. They redid the order at their cost, which they're obligated to do when the delivered spec doesn't match the PO. But we lost 12 days, and the install crew sat idle for three of them.
That one decision cost us roughly $4,200 in rescheduled labor and pushed commissioning back by almost two weeks. On an $18,000 sensor package.
I'm not 100% sure the alternative vendor would've been better. But I am sure the cheaper quote wasn't actually cheaper.
What I now specify before every occupancy sensor order
After that project, I rewrote our sensor spec template. Every RFQ now requires the vendor to confirm, in writing, five things. No exceptions, no matter how good the relationship is.
1. Voltage class, not voltage range
"120-277V universal" is not the same as "277V rated with listed terminal block." Ask which class the unit is certified under. Line voltage occupancy sensors on a 277V commercial circuit need conductors, spacing, and terminals rated for 277V. If the datasheet only shows a range, ask for the UL file or the specific certification document.
2. PIR sensor coverage pattern, in writing
PIR occupancy sensors are not interchangeable by category. A ceiling mounted PIR rated for 450 sq ft at 8-foot mounting height is a completely different product from one rated for the same coverage at 18 feet. Ask for the coverage diagram at the actual mounting height of the install. If they can't send one, they don't have it.
3. High bay lens and detection zone
High bay occupancy sensors — especially passive infrared units — depend heavily on lens geometry. A high bay sensor designed for a 40-foot warehouse ceiling won't perform at 15 feet, and vice versa. Confirm the lens type matches the mounting height in your scope of work.
4. Compatibility claims, with evidence
If a sensor is going into a lighting control system or a networked setup, don't accept "compatible with most systems." Ask for the specific protocol documentation, the tested integration list, or a sample commissioning procedure. We now require a written compatibility statement signed by the vendor's technical contact.
5. Certifications matched to the model number
This one sounds obvious. It isn't. Twice now I've received UL or ETL certificates where the model number on the certificate didn't exactly match the model number on the datasheet. Sometimes it's a suffix. Sometimes it's a different revision. Either way, match them character by character before you approve anything.
For reference, the standards I lean on when I'm reviewing submittals: NEMA WD-7 covers occupancy sensor performance terminology, and ASHRAE 90.1 sets the energy code baseline for most commercial projects. California Title 24 is stricter in some categories and worth checking if the project is there. Verify the specific edition that applies to your project — codes get updated and local jurisdictions sometimes lag behind. Don't take my word for it; pull the current version.
The lesson I keep relearning
I'd rather spend 20 minutes walking a buyer through what a PIR sensor specification actually needs to say than spend two weeks fixing a rejected batch. Informed customers ask better questions. They order the right product the first time. And they don't blame you when the installer opens a box and finds the wrong voltage label.
If you're sourcing occupancy sensors — ceiling mounted, high bay, line voltage, PIR, whatever the application — my advice is simple. Don't buy on price alone. Don't buy on the datasheet alone. Buy on confirmed specs, in writing, matched to the actual install conditions. The cheapest quote on paper has a way of becoming the most expensive order in practice.
That's not a marketing claim. It's what 480 rejected units taught me.