I Bought the Wrong Siemens S7-1200 G2 PLC. The Real Problem Wasn't Me.

March 2024: The Box Nobody Opened

In March 2024, I approved the purchase of a Siemens S7-1200 G2 PLC. Total cost: $1,340, including the memory card and shipping. I checked publicly listed distributor prices (as of that month, the CPU 1212C was running $475–560, plus $200–450 for the memory card depending on capacity). The price seemed reasonable. The request came from our controls engineer, who had never once asked me to buy something unnecessary.

The box sat in our receiving area for three weeks.

When the engineer finally opened it, he said: "This is the wrong one." Not wrong as in defective. Wrong as in unnecessary. He'd been evaluating Beckhoff vs Siemens for a conveyor upgrade since January. He was leaning Beckhoff—the EtherCAT ecosystem made more sense for their existing servo drives. But he'd submitted a Siemens purchase request "just to see lead times."

I paid $1,340 for a PLC nobody needed because I didn't know enough to question the request. Or rather—and this matters—because the system didn't require anyone to know enough.

What I Mistook for a Buying Decision Was Actually a Technical One

Here's what the request said: "Siemens S7-1200 G2 PLC, CPU 1212C, for Line 3 upgrade." I saw a product name, a model number, and a destination. I did what any admin buyer does: I checked our approved vendor list, compared pricing from two distributors, and placed the order.

I manage procurement for a 60-person manufacturing operation—roughly $180,000 annually across 14 vendors. I report to both the operations manager and the CFO. My job is to buy things at competitive prices from reliable suppliers. Nobody has ever asked me to understand what a PLC actually does.

What I didn't know—what I had no way to know—was that "Line 3 upgrade" was still in the planning phase. The Beckhoff vs Siemens PLC 2025 comparison was unresolved. The request was a placeholder. The engineer needed lead-time data for a spreadsheet, and the fastest way to get it was to submit a purchase request and let me do the legwork.

People think procurement errors happen because the buyer doesn't understand the technology. Actually, the causation runs the other way: procurement errors happen because companies assign technical decisions to non-technical people and label it a "purchasing request." The assumption is that the requester has done the technical thinking. Sometimes they have. Sometimes they've submitted a placeholder while they finish comparing protocols.

We didn't have a formal technical specification review process. (Note to self: we still don't, but I'm working on it.) Requests came in through email, marked "urgent" or "ASAP," and I processed them the way I process any order: verify the item exists, compare prices, confirm delivery date.

The Cost of Not Knowing What You Don't Know

The S7-1200 G2 sat in receiving for three weeks—$1,340 tied up in a box nobody opened. The return process took two more weeks and cost us a 15% restocking fee. More importantly, the conveyor upgrade slipped by a month while the engineer re-quoted the Beckhoff components. That delay cost the production team an estimated $4,200 in overtime to meet a customer deadline.

But the PLC was the small problem. The bigger one showed up three weeks later.

A maintenance tech asked me to order a 12V gel battery charger for our backup power testing station. I ordered a standard automotive trickle charger—$45, competitive price, decent reviews. It arrived. The tech looked at it and said, "This will overcharge a gel battery. We need a smart charger with a gel profile."

I apologized. I ordered the correct one—$120 this time. The first one went into the returns pile. (Should mention: the $45 unit still works fine for our lead-acid batteries, so I didn't waste the money entirely. But that's not why I bought it.)

Then someone asked for a cigarette lighter battery charger for the service van. I bought a $19 unit from a gas station brand. It worked, technically. It also took 14 hours to charge a battery that a $60 model would have handled in four. The tech didn't complain. I saw the time logs anyway.

And then there was the multimeter question. A technician—new hire, three weeks on the job—asked me: "Hey, what's the symbol for continuity on a multimeter?" I didn't know. I told him I'd look it up. I Googled it, found the answer (typically a diode/arrow symbol, though some models use a sound wave icon), and passed it along.

That exchange took eight minutes of my time and made me realize something uncomfortable: I was being asked to function as a technical reference. I had no business being one. If I'd given him the wrong answer—and I could have; multimeter symbology varies by manufacturer—he could have spent an hour diagnosing a circuit that wasn't actually broken.

The Assumption That's Costing You Money

The assumption is that "procurement" is a single skill—that the person who negotiates pricing and manages vendor relationships can also evaluate battery charger specifications or explain multimeter symbols. The reality is that procurement is a logistics function. It is not an engineering one.

I'm good at my job. I've reduced our vendor count from 19 to 14 over four years. I negotiated a 12% discount on packaging supplies in 2023. I caught a duplicate invoice that would have cost us $800. But I cannot tell you the difference between a smart gel charger and a trickle charger, and I should not be expected to.

The financial case for change is straightforward, even if it's uncomfortable to admit: my hourly cost is lower than an engineer's, but my error cost is higher—not because I make more mistakes, but because I can't recognize them until someone else points them out. The S7-1200 G2 sat in a box for three weeks. A gel battery charger nearly damaged a $400 battery. A cigarette lighter charger added 10 hours of labor to a simple task.

What We Changed (And What I Wish We'd Changed Sooner)

After the PLC incident and the charger follow-up, I proposed a two-part process change to the operations manager. It's not glamorous. It works.

First: technical sign-off. Any request with a model number or a specification requires a one-line justification from the requester stating which alternative was considered and why this one won. For the PLC, that would have read: "Comparing Beckhoff vs Siemens for Line 3—this request is for lead-time data only, not a purchase authorization." I would have waited. The $1,340 would have stayed in the budget.

Second: a technical questions buffer. When a technician asks me "what does this symbol mean" or "which charger is right for this battery," I now forward the question to the controls engineer or maintenance lead. It adds 10 minutes to the response time. It saves the 45-minute round trip of ordering the wrong item, receiving it, learning it's wrong, and returning it.

I'd rather work with a specialist who knows their limits than a generalist who overpromises. That applies to vendors. It applies to me, too.

If your company expects the person who negotiates office supply contracts to also choose between Siemens and Beckhoff, you're not saving money on procurement. You're just moving the cost somewhere harder to track—into delayed projects, restocking fees, and the quiet overtime that never shows up on the purchase order.