I Spec'd the Wrong Flos Light on a $12K Order — And Why I Now Use a Pre-Check Checklist

It was a Tuesday afternoon in March 2022, and I was staring at a purchase order for twelve Flos IC Lights S1 — six floor lamps, six suspension. A hotel lobby project. The spec sheet was approved. The budget was signed off. I felt good.

Forty-five days later, I was staring at something else: a $12,400 invoice plus a $2,500 expedite fee, with the wrong lamps in a warehouse in New Jersey.

Here's what happened, and the three-step checklist I now use to make sure it never happens again.

The Setup: A Project That Seemed Straightforward

This was my second year handling lighting specification for an independent design-build firm — a mid-range commercial studio doing boutique hospitality work. We'd previously specified Flos on a handful of residential projects without issues. But this was my first time managing a multiple-unit commercial order solo.

The spec called for twelve units of the Flos IC Lights S1 in the suspension version. Clean. Minimal. The architect had used them before, so I plugged the product code from our last purchase order: FL.IC.S1.SUS. The code matched a previous invoice. Good to go, right?

Wrong.

That code, it turns out, was for the floor version. The suspension version's code was FL.IC.S1.SUSP. One extra letter. (Not that the vendor's system caught it either — surprise, surprise.)

The Turning Point: When Everything Unraveled

The shipment arrived on a Friday. The boxes were beautiful — white card, embossed logo, exactly what you'd expect from an Italian design house. I signed for them, visually inspected one unit, and ticked the delivery as complete.

On Monday, the installer called. "These don't hang."

I rushed to the site. Pulled one out of the box. Looked at the base. Looked at the canopy. No suspension mechanism. No ceiling plate. These were floor lamps — IC Lights S1 in the floor configuration, not suspension. Twelve of them.

My stomach dropped. The client's timeline: assembly starting Wednesday. The lead time for the correct units: eight weeks, minimum. The rush fee for a swap: through the roof.

The Cost Breakdown (Note to Self: This Hurts)

• Incorrect order value: $12,400
• Return restocking fee (25%): $3,100
• Expedite for correct units: $2,500
• Installer idle time billed to us: $1,200
• Total out-of-pocket waste: $6,800
• Client trust damage: priceless (and negative)

The 8-week lead time turned into 10, because everyone in the supply chain scrambles when they smell urgency. The project was delayed by six weeks. I got pulled from the client account for three months. (Fair.)

The Fix: A Three-Step Pre-Check List

After the dust settled, I did what I should have done before: I sat down and designed a workflow for verifying lighting specs — especially for high-value orders where a single digit or missing letter can derail a project.

The checklist is simple. It takes maybe twenty minutes. But it catches the exact kind of error that caught me.

Step 1: Cross-Reference the Product Code — Twice

Never trust a single source. Here's my process:

• Pull the product code from the manufacturer's website (Flos's official product database, at flos.com). Not from a previous PO. Not from a distributor's catalog. From Flos's own source.
• Confirm the code matches the form factor you need: suspension vs. floor vs. table vs. wall. Flos uses suffixes like -W (wall), -T (table), -P (floor) on some lines. On the IC series, it's SUS vs SUSP — a one-letter difference that costs thousands.
• Check the spec sheet for dimensions, mounting requirements, and voltage. The IC S1 suspension requires a specific ceiling plate and a minimum ceiling height. The floor version doesn't. Two entirely different products sharing 95% of the same name.

This sounds obvious. I know. But in a busy week with multiple projects and overlapping deadlines, it's exactly the step that gets skipped. (To be fair, I was also on email at 11 PM. That never helps.)

Step 2: Visual Match, Not Just Code Match

A product code alone is insufficient. I now keep a folder of product images — actual photos, not renderings — for every model I spec. When the order arrives, I open the image on my phone and walk through the checklist:

• Does the shape match? The IC S1 floor lamp has a marble base approximately 30cm in diameter. The suspension has no base — just a ceiling plate and a longer cable drop.
• Does the shade angle match? The IC table lamp's diffuser sits at a different angle than the suspension version.
• Is it the right kind of light? This hotel project needed ambient downlight from above, not task light from below. The suspension was right; the floor lamp was wrong artistically and functionally.

I also do a visual check at the distributor's loading dock before signing. If the canopy diameter doesn't match the spec sheet photo, that's my red flag. (Worse than expected, but caught before it reaches the client.)

Step 3: Enforce a 24-Hour Review Window

My firm now has a policy: every purchase order over $5,000 sits in a review queue for 24 hours before submission. No exceptions. It's a hard rule. I lost that $6,800 because I submitted the PO at 10:30 PM and hit 'send' without a second pair of eyes.

In Q3 2024, we tested this policy on a batch of 14 orders. We caught three errors: two wrong finish specifications and one incorrect voltage requirement. The total saved: approximately $4,200 in avoided re-orders and rush fees (Source: internal audit, October 2024). The cost of the policy: zero — it's a process change, not a purchase.

As of 2025, we've caught 47 potential errors using this checklist across roughly 200 orders. That's a 23% error catch rate. (Which honestly tells me something about how many near-misses we've had without knowing it.)

Rethinking Other Lamp Choices on That Project

That hotel project also gave me a new appreciation for making nuanced product selections beyond just codes. Because the lobby had a split lighting plan — ambient from the IC suspension, accent illumination from tracks, and task lighting at the check-in desks with table lamps. The original design called for Flos' iconic Arco floor lamps in the lounge area, but we changed course after the delay. In hindsight, that choice re-opened the question of downlight spotlight placement vs ambient washes, and even the eternal debate of tube light vs LED bulb for the indirect cove lighting. Different projects favor different solutions. But having the discipline to think through why you choose one over the other — that's where mistakes turn into standards.

Another thing I've learned: Supreme Flos Bellhop Lamp and the IC Lights line are design behemoths for a reason. They're timeless. But you need to spec them intentionally. The Bellhop is a portable rechargeable lamp — brilliant for flexibility, but wrong if the client wants a wired table lamp. The IC Lights have the floating disc effect, but you need the right voltage driver, and you need to confirm it's compatible with your dimming system (many aren't — that's a post for another day).

The key takeaway: verification isn't optional. It's a process that pays for itself.

Closing Thoughts: A Gift From My Younger Self

I keep that original incorrect PO framed in my office. Not as a trophy — as a reminder. When I'm tired, when the deadline is tight, when the client says 'just use the same code as last time,' that framed document says: slow down.

The lighting industry moves fast. New collections drop. Lead times shift. Codes get deprecated. Flos, for example, updated its entire product numbering system for the IC series in late 2023 (this was accurate as of Q2 2024; verify current codes if you're reading this later). The old codes still work in some distributor systems but not all. That's exactly the kind of situation where a quick code-pull from a previous PO will fail you.

If you take one thing from this story: build a pre-check process for your next order. The ten minutes you spend on verification today will save you from a week of crisis management tomorrow.

And if you've got a story of your own — a spec error that cost you time or money — I genuinely want to hear it. Because the more we share these, the better our industry gets at preventing them.