Why There's No Single 'Best' Supplier for ABB PLC, Timers, or Drives
In 2019, I approved a batch of 240 contactors and 65 timers from a supplier who undercut everyone else by 22%. Same specs on paper, same certifications, way less money. It felt like a win.
Nineteen of those units failed within six months. Rework, expedited replacements, one unhappy customer — the batch cost me roughly $4,300 in cleanup, against $1,800 I thought I'd saved.
I'm not telling you this to say "cheapest is always worst." That's lazy advice. I've also seen budget components run for years in the right application. The real takeaway is more uncomfortable: the right supplier depends entirely on which kind of buyer you are. And that's not about your industry or company size — it's about what you're actually buying and what you're delivering.
Here's how I break it down now.
The 3 Buyer Scenarios (And What Actually Matters in Each)
After seven years of sourcing AC500 PLCs, Automation Builder software licenses, timers, relays, and drives — across distribution, OEM, and panel shop channels — I keep seeing the same three patterns. The evaluation criteria that matter in each scenario sometimes contradict the ones in the others. That's the whole problem with generic "supplier checklist" articles.
Scenario A: The Volume Distributor Reselling Components
You stock timers, relays, and contactors by the shelf. Margins are thin. You're comparing supplier quotes quarter by quarter and picking the lowest landed cost that can hit the delivery window.
The obvious move is to squeeze every quote to the floor — switch suppliers constantly, never commit volume to anyone.
Here's what surprised me: that's usually the most expensive option.
I had a relay supplier once that I rotated away from four times in a single year over a few points on price. By Q4, nobody answered my calls. Rush orders took six days. Returns sat in a queue labeled "next shipment."
The "savings" I booked in January and April — maybe 6% or 7% — cost me roughly four hours a week in firefighting by year-end, plus two relationships I had to rebuild from scratch. Bottom line, I traded a stable partner for a rotating cast of strangers.
What I actually look for in this scenario now:
- Predictable lead times on repeat orders (not fastest — predictable)
- A returns and RMA process that doesn't require three follow-up emails
- Honest stock flags instead of "in stock" that becomes a three-week backorder
If you're moving under, say, 500 units a month, a local distributor at +3% is almost always the better trade. You're not really buying the part — you're buying someone who answers the phone.
Scenario B: The OEM Integrating PLCs and Drives Into Machines
You source to a specification, integrate it into equipment your customer will run for five-plus years, and you depend on software tooling to do it. This is where ABB PLC software, drive configuration utilities, and the broader Automation Builder ecosystem actually matter.
The trap every junior buyer falls into is comparing only the hardware quote on the PLC. But when a line is down, what costs you isn't the CPU price — it's compatibility with the software stack and whether anyone on the supplier side can actually help you untangle what you built.
Under IEC 61131-3, the programming languages themselves are standardized. In theory, code should be portable. In practice, project structures, library dependencies, and HMI bindings don't migrate cleanly. I've watched a "minor platform swap" turn into a three-week revalidation because two timing functions behaved differently at the edge cases.
On a packaging line project where we used AC500, what saved me wasn't getting the lowest unit price. It was:
- A supplier with someone who understood the software, not just the logistics
- Fast access to firmware updates and parameter files
- Willingness to share wiring diagrams or EPLAN macros before the order, not after
I still kick myself for the 2022 drive selection. We picked the cheapest drive manufacturer on the quote sheet and saved about $400 per unit. Eight months later, when the customer wanted a network reconfiguration, the support window was gone and spares were a scavenger hunt. The real cost of that decision — respec, emergency sourcing, downtime — worked out to roughly $2,100 per drive. A $42,000 "saving" that turned into a $168,000 cleanup.
Scenario C: The Panel Builder or Contractor With Compliance Requirements
Your customer names the standard. Your product needs to be traceable. Your documentation has to hold up in an audit. You're working with safety PLCs, UL-listed components, and certification paperwork that someone downstream will actually read.
In this scenario, the sourcing conversation isn't about price at all. It's about whether you can pull a certificate without five emails, whether you can confirm a part change across a product line for the last three years, and whether the last three digits of a specification sheet still match when a third-party inspector asks.
Put another way: bad documentation and weak traceability are deal-breakers. Everything else is negotiable.
I've worked with suppliers who were competitive on price but needed three weeks to produce an efficiency certificate. Those suppliers cost me time and cost my customer trust. I now ask one question before quoting: "Can you send me the compliance packet for every part on the BOM within 24 hours?" The answer tells you everything.
How to Figure Out Which Scenario You're In
Here's the checklist I use — after several painful mistakes taught me to build one:
- Do you program and integrate, or do you resell? If you resell, software support is irrelevant. If you integrate, it's the whole game. Don't let a parts-pricing mindset distract you from what actually drives your cost.
- How specified is your end customer? If the spec names ABB PLC or a specific drive series, your room to maneuver on price shrinks — but your room to compete on delivery certainty and traceability grows.
- Who carries the cost of failure three years out? If it's you, prioritize spares availability and software longevity over initial price. If it's the customer, put what you need in writing.
- Where are you in your project cycle? If you're evaluating drive manufacturers, don't just compare spec sheets. Ask how they handle version changes, what their end-of-life policy looks like, and where their regional stocking position is. That's where the real cost hides.
For ABB PLC lineups specifically, this usually means getting clear on which channel you're actually buying through. Authorized distribution and gray-market sources can look almost identical at the quote stage — and diverge wildly the moment something goes wrong.
Bottom Line
With ABB PLC, software, drives, timers, and relays, if you optimize only on unit price you're negotiating maybe a quarter of your actual cost — and often at the expense of the other three quarters.
I'll be honest about the limits of what I know. I don't have hard industry-wide data on failure rates or total cost benchmarks. What I can speak to is roughly 200 mid-size projects across the US Midwest — batch sizes between a few dozen and a few thousand, customers in manufacturing, food processing, and municipal systems. If you're running consumer-electronics volume or international projects, your trade-offs will shift.
But even accounting for that, the mistake that's cost me the most money hasn't changed: treating a scenario-dependent decision like it has one universal answer. Figure out which of the three you are first. The rest gets a lot simpler.