Why "Which Motion Sensor Is Best?" Is the Wrong Question
I've been doing procurement for six years now. In that time, I've handled roughly $2.8 million in lighting controls spending. And in the early years, when I'd ask suppliers "which motion sensor is best?" — they'd usually quote me a model number. Then I'd order 300 units and find out it wasn't right for our ceiling height, or our wiring setup, or the specific color temperature a tenant wanted.
The answer I've landed on: there's no universal best. It depends on how many you're buying at once, where they're going, and whether you'll be buying again in three years.
So here's how I'd break it down. Three scenarios. No hierarchy — just different playbooks. I've bought in all three ranges, and each one has its own set of rules.
- Small trial / first order — 50 to 500 units. Testing a market or outfitting a single site.
- Mid-size rollout — 500 to 5,000 units. Multiple locations, consistent specs.
- OEM / bulk contract — 5,000+ units. Private label or long-term supply.
If you already know which one you're in, skip ahead. If you're not sure — read the "How to Tell Which Scenario You're In" section first, then come back.
Scenario 1: Small Trial / First Order (50–500 Units)
Here's what most people get wrong about this scenario: they optimize for the wrong thing.
When you're ordering in small quantities, the lowest unit price shouldn't be your top priority. A single reinstallation — having an electrician come back out because the sensor programming didn't work with your setup — costs $200 to $400 in labor. That's almost always more than whatever you'd save switching from one supplier to another.
So what I look at instead: how easy is this sensor to configure on-site?
The Legrand light switch models with built-in motion sensors, for example — their settings are either dip-switch or a simple rotary dial, depending on the series. You can adjust them in 10 to 15 seconds. No app, no laptop, no gateway. That matters way more for a small project than a spec sheet full of features you'll never use.
Compare that to a "feature-rich" sensor that requires a mobile app, a hub, and a commissioning walkthrough. On a 12-sensor warehouse install, that extra setup could easily eat a full day of labor.
"What most people don't realize is that 'free programming support' on a small order usually means you're dependent on the vendor's schedule. If nobody answers your call, you're stuck. And that electrician crew is standing around on the clock."
Another thing — don't assume you have no negotiating room just because the order is small. My smallest order was 180 sensors. I got about 8% off just by asking: "What's your payment terms if I take care of logistics on my end?" Saved us maybe $1,200 — hard to say exactly, I'd have to pull the invoice. But it taught me a habit I've kept.
I'll say this plainly: small orders shouldn't be treated as unimportant. I was the person placing $200 orders once. The vendors who took those seriously? I'm still buying from them at a $20,000 level now. If a supplier makes you feel like you're bothering them with a 200-unit inquiry — that's a red flag. Trust me on this one.
Scenario 2: Mid-Size Rollout (500–5,000 Units)
This is where total cost of ownership actually starts to matter.
Say you're outfitting 15 buildings with 2,000 sensors across a regional portfolio. At that volume, you're likely dealing with networked or addressable controls. That means you're now balancing sensor cost against installation compatibility — and those two things don't always pull in the same direction.
Here's the trade-off I've gone back and forth on more than once:
- Brand-name motion sensors (think Legrand, or similar tier) — better documentation, deeper integration support, existing spec relationships. Higher upfront cost.
- Compatible third-party sensors — lower unit price, but you own the integration risk.
I spent two weeks on this decision for a 1,800-unit school district project. The third-party option was roughly 18% cheaper on paper. But when we ran a pilot, the sensors wouldn't hold their settings after a power cycle. Every time the HVAC room cycled, the occupancy delay reset to factory default. That 18% savings evaporated after one re-programming service call — which cost us about $45 per unit to fix.
The assumption is that expensive means better. In lighting controls, it's often the reverse — sensors that hold their configuration across real-world conditions are the ones that can command a premium. The causation runs the other way. Price doesn't cause reliability. Reliability causes the price.
What actually kills your budget at this scale isn't the sensor itself — it's everything around the settings:
- Is the motion sensor configured for three-way or multi-way operation?
- Does it have daylight harvesting, or will it run at full power when natural light is available?
- Do the units require a proprietary communication protocol — or do they play nice with your existing BMS?
These questions have real dollar values attached. But they almost never show up on the initial quote.
Scenario 3: OEM / Bulk Contract (5,000+ Units)
At this level, you're in commercial lighting manufacturer territory. Your role shifts from buyer to supply partner — or competitor, if you're private-labeling.
And the game changes. Unit price matters less than you'd think. Here's what actually drives cost at scale:
- Warranty terms and claims process. A 5-year warranty with a smooth RMA process is worth more than a 10-year warranty with a fight attached.
- Lead time consistency. Can they hold a 6-week standard, or does every quarter slip by two weeks?
- Batch consistency. Same model, same firmware, same behavior — every shipment. If firmware changes between batches, your field support costs go up.
- Payment and inventory terms. Net-60 vs. Net-30. Consignment vs. direct. These matter more than a 3% unit discount.
If you're also sourcing fixtures — say, working with a track lighting supplier for the same project — you've got a compatibility matrix to manage. Sensors from one manufacturer, fixtures from another, and you're the one holding the bag when they don't talk to each other. I tell people: get the sensor manufacturer to sign off on fixture compatibility in writing before you place the bulk order. A verbal "yeah, it'll work" is worthless.
One of my biggest regrets at this stage: we once locked in a great unit price on 8,000 motion sensors but didn't confirm the BMS gateway compatibility until after the PO was signed. Turned out we needed an additional interface module — roughly $4,000 in hardware and a week of integration delays. Not catastrophic. But unnecessary. The unit-price negotiation felt like a win at the time. It wasn't.
How to Tell Which Scenario You're In
Stop guessing. Ask three questions:
- What's your per-order volume? Under 500 = Scenario 1. 500 to 5,000 = Scenario 2. 5,000+ = Scenario 3.
- Do you need programming or system integration? If you're running standalone sensors with no network connection, you're in Scenario 1 — even at higher volumes. If integration is required, treat it as Scenario 2, even for a smaller order.
- Will you buy again within 12 months? If yes, you're building a relationship, not making a one-off purchase. That shifts you toward Scenario 2 thinking, regardless of current order size.
One more note: these scenarios overlap. You might be buying 3,000 sensors for one project and 200 for another — same quarter. That's normal. I keep two different supplier lists for exactly this reason.
Bottom line: the question isn't "which motion sensor is best." It's "which scenario am I in right now — and what does that scenario actually demand?" Get that right, and the product choice mostly makes itself.