-
The 7-Point Allen-Bradley PLC Buying Checklist
-
1. Lock the exact CPU part number and firmware level
-
2. Confirm the power supply, battery, and panel layout
-
3. Match the I/O and communication modules
-
4. Don't forget software, licensing, and training
-
5. Compare quotes on total cost, not list price
-
6. Check warranty, returns, and lead time
-
7. Test before you install—especially if the PLC is used
-
1. Lock the exact CPU part number and firmware level
-
When This Checklist Isn't Enough
If you're searching 'allen-bradley-plc' or 'Allen Bradley PLC for sale' because you need a processor that won't die on a Monday morning, this checklist is for you. It's also for the person who gets handed a PO and has to make sure the thing actually works when it gets to the shop floor.
I'm a procurement manager at a 140-person manufacturing company. I've managed our automation parts budget—about $220,000 a year—for six years, negotiated with 30+ vendors, and tracked every order in our ERP. I'm not a controls engineer. I'm the person who signs the PO and then has to explain why the PLC was the wrong one. That's why this checklist exists.
This is a checklist for buying one or two units from stock. If you're designing a plant-wide control system, or you're doing a large migration, you need a system integrator and a proper spec, not a blog checklist. Honest limitation: this works for 80% of replacement purchases. Here's how to know if you're in the other 20%—you'll see it below.
The 7-Point Allen-Bradley PLC Buying Checklist
-
1. Lock the exact CPU part number and firmware level
Allen-Bradley PLCs come in three main families: the Micro800 line, the CompactLogix line, and the ControlLogix line. A CompactLogix 5069-L306ER is not the same as a 5069-L310ER. Same physical look, different memory, different price.
When I audited our 2023 spending, I found that most of our wrong-part returns were actually wrong firmware revision. The CPU number was fine. The firmware was not compatible with the program we planned to load. So before you search for a price, open your existing project in Studio 5000 or RSLogix 5000 and check the processor type and revision. If you don't have the software, ask the person who owns the program for a screenshot of the controller properties. Then verify compatibility on Rockwell's Product Compatibility and Download Center (compatibility.rockwellautomation.com) before you commit to a purchase.
-
2. Confirm the power supply, battery, and panel layout
PLCs need clean DC power. Some processors include a power supply, some don't. If the PLC is in a remote panel powered by a solar power battery charger, verify the charger's output under load. A 24V nominal bus can hit 29V in bulk charge mode, and that can kill a CPU.
I once saw a PLC reset every time a fuel pump cycled. It wasn't the PLC. A low-cost EFI fuel pump kit on the same 24V bus was pulling the voltage down. The fix wasn't a new processor. It was a bigger power supply. Use a multimeter to check the bus voltage before you blame the PLC.
-
3. Match the I/O and communication modules
Counting I/O is not the same as counting modules. You need to know the number of input points, output points, analog points, and spare slots. Then add 15% spare capacity—if no one else in your company has ever wanted a spare point, you haven't been here long enough.
Also verify the communication protocol. A CPU with EtherNet/IP will not talk to a remote rack that expects ControlNet. And a 1756 chassis can accept many modules, but not all of them are compatible with your firmware. That's the 'plc bradley allen' trap: listings are often garbled, and the part number is the only thing that matters.
-
4. Don't forget software, licensing, and training
This is where the total cost calculation goes sideways. The CPU quote looks great until you realize you need a Studio 5000 license and your team has only RSLogix 5000. Different families use different software: Micro800 usually uses Connected Components Workbench, and CompactLogix/ControlLogix use Studio 5000. They are not interchangeable.
What I mean is that the lowest-price option isn't just about the sticker price—it's about the total cost including your time, the risk of delays, and the potential need for a redo. If you're buying from a reseller, ask if the software license is transferable. It usually isn't. Add training if anyone new has to support it.
-
5. Compare quotes on total cost, not list price
When you see 'Allen Bradley PLC for sale' on a surplus website, the price is the bait. The real price includes shipping, handling, a possible restocking fee, a firmware alignment fee, and the cost of your time when the part doesn't work.
'The lowest quoted price is not the lowest total cost.'
Use a simple spreadsheet. Three things: unit price, lead time, warranty. In that order. One authorized distributor quoted $4,200 and included next-day shipping. A surplus site quoted $3,650 but added a $450 compatibility test and $350 for shipping. The total was higher. And the warranty? It didn't have one.
I had two hours to make that call once because of a plant shutdown. Normally I'd compare three quotes, but there was no time. I went with the authorized distributor. In hindsight, I should have pushed back on the deadline. But with the line down, I made the best call I could with the information I had.
-
6. Check warranty, returns, and lead time
If the PLC dies in a month, who pays? Authorized distributors have a return path. Some brokers don't. That doesn't mean brokers are always avoidable. They often have stock that official channels don't. But you need to know the risk you're taking.
Lead time is also a hidden killer. Some Allen-Bradley CPUs are stock, but some have lead times measured in weeks, not days. If your line depends on it, buy a spare. When I hit 'confirm' on a $6,800 order once, I immediately thought 'did I just overpay?' I didn't relax until the parcel showed up with the right label and the right firmware.
-
7. Test before you install—especially if the PLC is used
The final step is the one everyone skips. We didn't have a formal incoming-inspection process for PLCs. It cost us when a used module arrived with a blown input and nobody noticed until the machine was half-assembled.
Here's a quick test sequence:
- Check the backup battery voltage with a multimeter. Need to know how to check battery voltage with multimeter? Set it to DC volts, touch the probes to the battery connector leads, and compare the reading with the value printed next to the battery. A spec is usually 3.0V or 3.6V. Low voltage means replace it before mounting.
- Power up the CPU in program mode and watch for faults on the status LED.
- Download your test program or the actual project, and cycle a few inputs.
- If the PLC is powered by a solar power battery charger, check the DC bus voltage under load with the multimeter while the charger is in its normal cycle.
When This Checklist Isn't Enough
If you're replacing a PLC in an existing machine, this checklist is enough. If you're building a new process line or migrating fifty PLCs to a new architecture, don't buy a single part until a controls engineer signs off on the design. A checklist can't replace a system design. It can only keep you from buying the wrong thing first.
That's it. Seven steps. The most expensive one to skip is the first.