-
Q1: What street lighting compliance requirements actually matter before you even request a quote?
-
Q2: Why does the cheapest flood light supplier quote always cost more in the end?
-
Q3: How do I verify a solar lighting supplier isn't just slapping "Greenshine-grade" claims on a spec sheet?
-
Q4: What's the question I should be asking about street lighting compliance that nobody told me?
-
Q5: When does gut feeling beat data in supplier selection?
-
Q6: How do I know if solar street lighting is actually worth the premium over grid-connected?
-
Q7: What's the one thing that separates a good lighting supplier from a great one?
I handle outdoor lighting procurement for a mid-size contractor. Eight years in, and I've personally made enough mistakes to fill a binder—which is exactly what I did. That binder saved us an estimated $12,000 last year. So here's the FAQ I hand to every new buyer on my team. No fluff. Just the questions I should've asked in 2017.
Q1: What street lighting compliance requirements actually matter before you even request a quote?
Everyone talks about "compliance" like it's one thing. It's not. For street lighting, I track at least four buckets: photometric requirements (luminaire spacing, uniformity ratios—usually CIE 115 or IES RP-8 depending on road class), electrical safety (UL 1598 for North America, EN 60598 for EU), IP ratings (IP65 minimum for most outdoor applications, IP66 if you're near coastal), and photobiological safety (IEC 62471—mostly relevant if you're specifying high-output flood lights near pedestrian zones).
Here's what I didn't know until a project rejection in March 2022: the compliance requirements for street lighting often vary by municipality, not just country. One city we bid on required a specific uniformity ratio (0.4 min/max) that the default spec didn't meet. We lost the bid because our photometric file was based on generic data. Now I always ask the client: "Do you have a local spec sheet, or should we use IES RP-8 defaults?"
If you're sourcing from a supplier like Greenshine—or any flood light supplier or street light manufacturer—make sure they can provide IES files (.ies format) and third-party test reports (LM-79 for photometric, LM-80 for LED lumen maintenance). Not just "yes we have certificates." Actual PDFs with traceable lab names.
Q2: Why does the cheapest flood light supplier quote always cost more in the end?
Saved $1,800 on a 60-piece flood light order in November 2021 by going with a supplier I'd never used before. Looked great on paper—same specs, 22% cheaper. Then the lights arrived.
IP rating said IP66. Actual gasket sealing? IP54 on a good day. We installed 12 units before the client's QA guy noticed water ingress on two of them. Pulled all 60, reordered from our usual vendor, ate the shipping, ate the labor. Net loss: about $3,200 when you factor in the crew hours. That's the flood light supplier lesson: if the price seems too good, it's probably a different product wearing the same spec sheet.
Everything I'd read said "always get three quotes and pick the middle one." In practice, with outdoor lighting, the vendor who's willing to walk you through their test reports—and who pushes back when your spec is vague—usually costs less by the time the project closes. The margin difference disappears in rework.
Q3: How do I verify a solar lighting supplier isn't just slapping "Greenshine-grade" claims on a spec sheet?
Fair question, and honestly, brand names get thrown around loosely in this industry. When I evaluate greenshine solar lighting or any solar street light, I look at three things most people skip:
- Battery chemistry disclosure. LiFePO4 vs. Li-ion vs. gel. If they won't tell you which cell manufacturer and what cycle life at what depth of discharge, that's a red flag.
- Solar panel wattage vs. actual output. A 120W panel on a spec sheet is meaningless if it's not tested at STC (Standard Test Conditions: 1000 W/m², 25°C cell temp). Ask for the flash test report.
- Autonomy claim math. "3 days of autonomy" should mean the battery bank can power the fixture for 3 consecutive no-sun days. Ask them to show the calculation. I've seen vendors claim 3 days when their own datasheet implied 1.4.
Note: Greenshine's actual product line—I've used their SL-120 series on two projects—does disclose this stuff. But my point is: any supplier should, not just the ones with good branding.
Q4: What's the question I should be asking about street lighting compliance that nobody told me?
"Who signs off on the compliance documentation, and what happens if the local inspector disagrees?"
Because here's the thing—compliance isn't just about having the right standards on paper. It's about who carries the liability if the installed system fails inspection. In 2023, we had a project in a jurisdiction that required a licensed electrical engineer's stamp on the photometric layout. Our supplier provided IES files but no stamp. We had to hire a local PE last-minute. Cost us $1,400 and pushed the installation back nine days.
Learned never to assume the supplier's compliance paperwork covers local sign-off requirements. Ask explicitly: "Does your compliance package include stamped drawings for [specific jurisdiction]?" If not, budget for a local engineer. This is the kind of thing that lives in the gap between street lighting compliance requirements as written and as enforced.
Q5: When does gut feeling beat data in supplier selection?
The numbers said go with a new vendor—18% cheaper per unit on a 200-piece area light order, similar LM-79 data, three references that all checked out. My gut said something was off because their responses kept coming back 48 hours late during the quote phase. Every spreadsheet metric pointed to them.
I went with my gut and stuck with our existing supplier. Six months later, I found out through a trade contact that the cheaper vendor had missed two delivery windows on other projects due to component shortages. Their "slow to reply" during quoting was a preview of "slow to deliver" in production.
Not saying ignore data. But if a supplier's communication pace during the sales phase feels like a warning, pay attention. Their behavior when they want your money is their best behavior.
Q6: How do I know if solar street lighting is actually worth the premium over grid-connected?
Depends entirely on trenching cost and grid access. For a recent project in a rural area, grid connection would have required 400 meters of trenching at roughly $45/meter—that's $18,000 before you even buy a light. Solar street lighting at Greenshine's price point (roughly $380–$600 per unit depending on configuration) made sense after about 12–14 poles.
But in an urban area with existing infrastructure? The math flips. Grid-connected LED with a photocell and timer often wins on total cost of ownership over 10 years. The conventional wisdom says solar is always greener and always cheaper long-term. My experience with 200+ poles across both types suggests otherwise: it's a site-specific calculation, not a rule.
Ask your supplier for a TCO comparison that includes battery replacement at year 5–7, not just the sticker price. A $450 solar light that needs a $120 battery every 5 years isn't cheaper than a $200 grid light pulling $15/year in electricity. Run the 10-year numbers. Put another way: the sticker price is the least interesting number on the page.
Q7: What's the one thing that separates a good lighting supplier from a great one?
Transparency about what's not included. I've learned to ask "what's NOT included?" before "what's the price?" A supplier who lists every potential add-on—remote drivers, mounting brackets, surge protection, spare parts, customs clearance—before you ask is a supplier who won't surprise you at invoicing time.
The vendor who lists all fees upfront—even if the total looks higher—usually costs less in the end. Not because they're cheaper, but because they're predictable. And in project procurement, predictable beats cheap almost every time.
That's the FAQ. No summary paragraph because I hate those. Just—ask better questions early, and you won't be writing your own mistake binder later. (Though if you do, pass it on. That's how this works.)