In Q1 2024, we ordered 600 replacement tires for our haul fleet. The purchase order said "Continental, WSG spec." The quote confirmed it. The delivery matched the paperwork. Then our maintenance lead called me: "These don't fit the rims."
We hadn't ordered the wrong brand. We'd ordered the wrong product.
A different Continental line carried the same WSG code on the datasheet but a different load rating in practice. The tires looked identical. They weren't. We caught it before the full shipment went into service—but not before 40 tires were mounted and run for 800 hours. The wear pattern was off by 22% against our baseline.
That mistake cost us $34,000 in re-mounting labor, downtime, and a rush reorder. It also taught me something I should've learned in my first year: a brand name isn't a specification.
What We Thought the Problem Was
My first read of the situation was simple: the supplier sent the wrong product. Maybe the warehouse picked the wrong SKU. Maybe the sales rep misunderstood. Either way, it felt like someone else's error.
That's the easy story. It's also wrong.
I spent two days composing emails that essentially said "please fix your mistake." The supplier responded politely, attached the original quote, and highlighted the line where the product family was listed. It was there. I just hadn't read it. In my first year on this job, I made the classic specification error: assumed "standard" meant the same thing to every vendor. Cost me a $600 redo and a week of embarrassment. I told myself I'd learned the lesson. But brand names have a way of making you forget. When you see "Continental" on a quote, your brain fills in the blanks. It assumes quality. It assumes consistency. It stops reading the fine print.
The supplier shipped exactly what our order described. "Continental, WSG spec" is a valid product identifier—for at least three different product families. When I pulled up the quote later, I saw the product family name buried in a footnote: it was a line designed for lighter-duty applications than our haul trucks.
We didn't get scammed. We got a mirror held up to our own procurement process. Our order form was a wish, not a spec.
Why "Brand + Code" Fails
Here's what I didn't understand: Continental runs multiple business units. There's the tire side (passenger, commercial, off-highway), the automotive components side, and industrial solutions. That's a feature, not a bug—the diversification is why they can supply everything from hydraulic hoses to new Continental tires for our underground loaders.
But it creates a trap for procurement teams. When our system says "Continental," it can pull up a dozen product families. When our spec sheet says "WSG," it might refer to one code in one division and a completely different code in another.
This isn't unique to Continental. It happened to us before, with optical inspection equipment. Our quality lab needed cameras for surface defect detection. Someone searched "Continental optical" and found a supplier page for Continental Optical—same brand name, different division, different lead times, different support model. The quote looked fine. The response time didn't match anything we'd ever experienced from the tire side.
My lab lead put it best: "It's like asking someone the difference between a hawk and a falcon. Both birds of prey. Both fast. Completely different in the hand."
That's what brand extension does to procurement. It creates false confidence. You see a familiar name and assume the same standards apply. Usually they do. But "usually" isn't a spec.
Then there's the code problem. "WSG" worked in our old system because everyone knew what it meant. When we migrated to a new ERP in 2023, the code came along but the context didn't. Our new procurement analyst—sharp, careful, thorough—had no way of knowing that "WSG" on a tire order meant something different from "WSG" on a conveyor component order. The system didn't tell her. The supplier didn't ask.
The Real Cost of Vague Specs
Let me be clear about where the money went. The $34,000 broke down like this:
- $18,000: rush reorder of the correct tires (expedited freight, premium pricing)
- $9,000: labor to pull 40 tires, remount, and recalibrate two haul trucks
- $7,000: downtime on the Millennium line during the swap
We recovered part of that through a warranty credit, but the time cost was gone. The Millennium upgrade schedule slipped by three weeks. That's not a tire problem. That's a production problem.
And here's the part that stings: the supplier wasn't at fault. They shipped what we asked for. We just didn't ask for enough.
Per FTC guidelines (ftc.gov), product claims must be truthful and not misleading—and that cuts both ways. Suppliers need to be clear about what a code means. Buyers need to be clear about what they're asking for.
I ran a post-mortem with our procurement team. The finding was uncomfortable: our spec sheets relied on shorthand. We assumed "WSG" meant one thing because it had always meant that thing in our old system. When we switched ERP platforms in 2023, the code migrated but the context didn't.
Even after we fixed the order form, I kept second-guessing. What if the revised spec sheets were too complicated for our suppliers to parse? What if the sample approval step added a week we didn't have? The month until our next shipment arrived was stressful. I didn't relax until the first batch cleared QC without a single flag.
What Changed (And What Didn't)
I'd love to tell you we overhauled the entire procurement process. We didn't. We made three changes that took a week to implement and have prevented four similar issues since.
- Every branded industrial component order now includes the exact product family name, not just the brand. No more "Continental, WSG spec." It's "Continental [product family], [full model number], [load rating], [application]."
- We require a physical spec sheet cross-reference for any code-based order. If a supplier can't map their code to a published specification, we don't place the order.
- First orders require sample approval. It slows down new supplier onboarding by about ten days. It's saved us more than it's cost.
None of this is glamorous. It's the kind of process improvement that doesn't make a good slide deck. But it works.
The other change was mental. I stopped assuming that a brand name answers the question "what is this?" A brand name tells you who made it. A spec sheet tells you what it does. You need both.
And when a supplier says "we can do that" to every request, I get nervous now. The vendor who said "this code doesn't cover your application—here's what does" earned my trust for everything else. That's the difference between a generalist who overpromises and a specialist who knows their limits.
If you're specifying industrial equipment and your order form says "brand + code," take thirty seconds and ask yourself: would someone new to the company understand exactly what to ship? If the answer is "probably," fix that before you hit send.