There's No Single Right Way to Specify Outdoor Lighting
I still remember the first batch of bollard lights I rejected. Sixteen units, all with a powder-coat finish that looked properly matte on the spec sheet but arrived with a visible sheen under direct sunlight. The vendor called it "within industry tolerance." Maybe it was. But our client had approved a matte sample, and I wasn't going to sign off on a visible mismatch. We sent them back. The redo cost the vendor roughly $2,400 and pushed installation back two weeks.
That was almost five years ago. Since then I've reviewed around 200 outdoor lighting SKUs annually—step lights, path lights, wall luminaires, spotlights—and I reject about 15% of first deliveries. The reasons are consistent: finish inconsistencies, dimming behavior that falls apart below 10%, or IP-rating paperwork that doesn't match the actual test report (I always cross-check against IEC 60529 documentation, not the marketing sheet).
Here's the thing: the right specification approach depends entirely on your scenario. I’ve worked on projects where a full bega lighting catalogue review with a bega lighting rep saved us weeks of back-and-forth. I've also worked on retrofits where the only real question was how to wire a light switch to a light without cutting into a finished wall. Different problems, different answers.
So let me break it down into three scenarios. Most projects fit into one of them—and the advice for each is not the same.
Scenario A: New Construction With a Full Landscape Package
This is the scenario where upfront specification work pays off. You're starting fresh—no existing wiring, no legacy control system, no finish samples already approved by a client who will notice a half-shade difference in color temperature.
In this case, the bega lighting catalogue is genuinely useful, not just marketing. Why? Because architectural outdoor lighting has a lot of variables that don't show up in a two-line product description: beam angles, glare control accessories, mounting options, finish durability standards. When I spec a new build, I want the full picture before I commit to a photometric layout.
A bega lighting rep earns their keep here too—but not for the reason most people assume. It's not about getting a "deal." It's about reducing the number of revision cycles. I've tracked this: on projects where we involved a rep early (before schematic design), we averaged two sample rounds instead of four. That's not just efficiency for its own sake—it's fewer chances for a finish mismatch or a beam-angle surprise to slip through.
What to watch out for
Most buyers in this scenario focus on the fixture price and completely miss the mounting and accessory line items. On one project, the fixtures came in under budget by 12%, but the glare shields and mounting brackets added 18% back. The catalogue lists them separately. Ask for a complete bill of materials, not just fixture SKUs.
Also: if you're specifying downlight wall fixtures—the recessed wall-wash type used on facades—confirm the trim finish matches the adjacent step lights. I've seen a project where the wall downlights were specified in a different finish family than the bollards. Under daylight, it looked like two different projects stitched together.
Scenario B: Retrofit or Repair on Existing Wiring
This is where things get messy. You're not choosing a system—you're working around one that already exists. Maybe the client wants to replace old halogen wall fixtures with LED equivalents. Maybe a failed driver needs swapping. Maybe someone asked you how to wire a light switch to a light because the old switch loop doesn't match modern color-coding conventions.
My advice here is almost the opposite of Scenario A: don't start with a catalogue. Start with a multimeter and a ladder.
Why? Because retrofit specs depend on what's actually behind the wall, not what's in a product brochure. I've seen retrofit projects fail because the new LED fixture drew less current than the old one, and the existing dimmer—designed for a minimum load—started flickering at low output. The fixture was fine. The control was not.
On the wiring question specifically: if you're replacing a switch and light on an existing circuit, the most common mistake is assuming the white wire is always neutral. In older installations, it might be a switch leg. Verify with a tester before you trust the color code. This sounds basic, but I've seen licensed electricians get burned by it on Friday-afternoon service calls.
What to watch out for
Here's the blind spot: most people replacing outdoor wall lights check the voltage and the mounting hole spacing. They forget to check the depth of the junction box. A new fixture with an integrated driver might need more clearance than the old incandescent housing allowed. Measure twice, order once.
Scenario C: Smart-Controlled Outdoor System
This is the scenario where zigbee lights and similar mesh protocols enter the conversation. And this is where I see the most oversimplification.
It's tempting to think that if a fixture is Zigbee-certified, it'll just work with whatever gateway or control platform you're using. But Zigbee is a protocol family, not a guarantee of interoperability. I've tested fixtures from three different manufacturers on the same Zigbee 3.0 gateway. Two paired cleanly. One required a firmware update that the distributor didn't have on hand. The project timeline slipped by 11 days waiting for a file transfer.
So my rule for smart-controlled outdoor lighting: don't specify Zigbee fixtures until you've confirmed—in writing—that the specific model's firmware is compatible with your specific control platform. "Zigbee compatible" on a datasheet is not enough. Ask for the firmware version and the gateway compatibility list. If the supplier can't provide it, that's a red flag.
The efficiency argument for standardizing on one protocol is real. When it works, commissioning time drops dramatically—I've seen a 40-fixture landscape install go from a full day of manual addressing to about two hours with auto-discovery. But that only happens when the compatibility is verified upfront.
How to Tell Which Scenario You're In
If you're still not sure which scenario applies, answer these three questions honestly:
- Is there existing wiring and a working control system? If yes, you're in Scenario B. Start with a site survey, not a catalogue.
- Are you coordinating more than three fixture types across a single project? If yes, you're in Scenario A. Get the full bill of materials and involve a rep early.
- Does the client expect app control, scheduling, or scene-setting? If yes, you're in Scenario C. Verify firmware compatibility before you commit to any fixture.
And if you're in more than one scenario at once—which happens on phased projects—prioritize the scenario with the longest lead time. That's usually the smart-control verification, because firmware issues can't be solved with a purchase order.
One last thing: none of these scenarios reward rushing the sample review. I've rejected more fixtures for finish and dimming issues than for any other reason. The specification work is the efficiency play. Skipping it just moves the cost downstream.