The Quote That Looked Like a Win
The cheapest Allen-Bradley PLC quote came in $1,850 below our regular supplier. I signed it. That decision ended up costing us $4,200 and three days of production downtime.
I'm not blaming the vendor. This one's on me.
Context: I'm the office administrator for a 250-person manufacturing company. I manage all equipment purchasing—roughly $300,000 a year across dozens of vendors. I report to both operations and finance, which means I feel pressure from both directions. Operations wants things that work. Finance wants things that are cheap.
When I took over purchasing in 2020, I thought I had it figured out. Compare specs. Compare prices. Pick the best deal. Same part number, same brand, so what's the risk? Turns out, plenty.
My job is an industrial version of "everything else." One week I'm comparing fuel filter connector suppliers for the service trucks. The next, I'm researching submersible control panels for a pump station upgrade. Somewhere in there, I had to figure out how to use a multimeter to test a car battery because our fleet manager was out for surgery and the maintenance crew needed an answer before morning inspection. So maybe it's no surprise that I treated PLC procurement the same way I handle a reorder of safety gloves: check the unit cost, pick the best price.
That worked for gloves. It very much failed for PLCs.
What a PLC Quote Doesn't Itemize
The controller I ordered was genuine. Delivery was on time. The hardware was identical to what our regular supplier offered. But the hardware is only a fraction of what you're actually buying.
Here's the thing: an Allen-Bradley PLC doesn't run itself. It needs programming software. It needs to be wired and configured and integrated with the rest of your equipment. It needs technicians who can troubleshoot it. And it needs somebody to call when it acts up at an inconvenient hour—which is when PLCs always act up.
Software is the first line item people miss. Studio 5000, the programming environment for modern Allen-Bradley controllers, is licensed separately from the hardware. If this is a new product family for your plant, that license is a real cost. The cheaper vendor mentioned it in a footnote in their quote. Our regular supplier had just included it in their proposal.
Training is the second. Allen-Bradley PLC training is something you don't think about as a buyer until you're staring at a controller that won't do what you need it to do. Formal training for your technicians isn't cheap. But it's a bargain compared to the hourly rate of an outside integrator who has to learn your system while your production line waits.
And then there's support, which leads directly to my $4,200 lesson.
The $4,200 "Saving"
Our regular supplier had always answered the phone when our electrician called with questions. I never thought about it. It was just part of the relationship. Apparently, it was also part of their pricing.
The cheaper vendor was a different model. Ship the hardware, process the order, move on. They could tell me my order status, but technical support? Not their business.
So when our electrician got stuck configuring the new Micro850, he called the number we had. They had no one to talk to. Not their model.
We called a local integrator instead. $95 an hour. They were booked, so we waited two days. Then a technician spent about twelve hours over a weekend getting the controller running. Meanwhile, the line that depended on it sat idle.
Let me add this up the way I did in my post-mortem to the plant manager:
$1,850 — what we "saved" on the purchase order
$1,140 — the integrator's invoice (12 hours at $95)
$2,300 — estimated lost production during downtime
$320 — overtime for our electrician and the line supervisor through the weekendTotal: just over $4,200.
I still kick myself over that. The frustrating part is, the original vendor's quote wasn't inflated. They charged more because they included things we'd always needed—a support line, technical guidance, coordination with spare parts—but they never itemized them, and I never asked them to. So when a cheaper quote arrived, the difference looked like markup. It was actually services I was about to purchase separately, at a higher price.
Since then, I've watched the same pattern play out in other purchases around our plant. The integrator we now keep on retainer has told me horror stories about companies that bought a submersible control panel on price alone, only to discover the panel wasn't configured for their pump motors and nobody was available to fix it for a week. Same thinking, same trap.
How I Evaluate an Allen-Bradley PLC Purchase Now
I want to be upfront: my experience is based on roughly 200 purchase orders over four years for a mid-sized manufacturing operation in northern Mexico. If you're in a different industry or region, some of these specifics will shift. The framework won't.
Here's the checklist I go through now, every time somebody in engineering hands me a request with a part number on it:
- Hardware. Controller, power supply, I/O, communication modules, any accessories. This is the number everyone compares first. Write it down.
- Software licensing. Do we already own Studio 5000 for this controller family? If not, price it out. Per Rockwell Automation's product documentation, Studio 5000 licenses are tied to specific controller families, so a license for one product line may not cover another. Worth confirming before you compare quotes.
- Training. Can our technicians configure and troubleshoot this controller? If not, find an Allen-Bradley training course and add the cost. It's cheaper than the day of downtime when someone gets stuck.
- Spare parts. What happens if this unit fails? For a critical production line, the answer should be "we have a spare." One spare processor and power supply is a rounding error compared to an emergency shipment.
- Support. Who do we call when it breaks at 2am? Does the vendor offer technical assistance after the sale? Does their quote say so in writing? If not, get it in writing.
- Lead time. Does the quote match our need date? The cheapest option that shows up three weeks late is the most expensive option in the room.
That last one is how I reframe the Siemens vs Allen-Bradley PLC market share debate that comes up every time we scope a new project. In my experience across plants here in Mexico, both brands have serious installed bases—food and beverage skews heavily Allen-Bradley, automotive is more mixed—but the market share conversation misses the point. What matters is alignment with your team and your local ecosystem. If your technicians were trained on Allen-Bradley PLCs, your distributor stocks Allen-Bradley spares, and there are training classes in your city, then buying a slightly cheaper controller from another brand isn't a saving. It's a whole onboarding project you haven't budgeted for.
Total cost thinking isn't complicated. It's just a habit of asking, "what else does this purchase touch?" The $1,850 I saved that day touched software, training, support, and a production line. That's the real quote.
If you're in a buying role, I feel you. The pressure from finance to cut costs is real. The pressure from operations to keep things running is real. But take it from someone who learned the hard way: the regular supplier's extra $1,850 wasn't markup. It was insurance. And I found out I needed it the moment I'd thrown it away.
