Four years ago, I treated inbound parts inspection as a formality — something to sign off between phone calls. Then we sent 34 PLCs to a customer with the wrong firmware revision. The machine builder caught it on their test bench, and the rework cost us a $22,000 credit plus freight.
That delivery changed how I work. Today I'm the quality and compliance manager who reviews every automation order before it reaches a customer — roughly 350 line items a year, split between Omron PLCs, contactors, relays, and the VFD drives that ride on the same POs.
If you're doing controller sourcing for a systems integrator, an OEM, or an in-house maintenance team, this is the routine I'd recommend. Nine checks, ordered the way I use them, from purchase order to shelf. Most take about ten minutes once you know what you're looking for.
Before you order: checks 1-4
1. Put acceptance terms in the PO before the price is agreed
The wording on your PO is your only contract once a shipment is disputed. It feels like extra admin, but I copy the same lines into every RFQ:
- factory-sealed packaging with original labels intact
- hardware revision and firmware level current as of the delivery date
- certificate of conformance with serial numbers actually shipped
- no re-labeled or re-printed nameplates
I didn't always do this. In 2022, about 11% of our first deliveries had a spec mismatch. When I moved acceptance terms into the RFQ stage in 2023, that rate dropped below 3% by 2025. Same suppliers, same products — earlier expectations changed the conversation.
2. Ask for traceability evidence, not just a channel name
“Authorized distributor” is a phrase, not evidence. I don't have hard data on industry-wide grey-market volumes, but in our own incoming checks since January 2023, roughly 6% of units bought outside our normal supply line had one discrepancy or another: wrong regional code, a label laminated over another label, or a date code that didn't match the carton.
So ask for the serial numbers that will ship and confirmation of where the seller got the units. A legitimate supply chain can usually produce that in a day. If the seller won't, ask yourself why you're the one carrying the risk.
3. Specify complete part numbers, not family names
“Omron PLC” isn't a part number, and neither is “CP1E.” In the same family, relay output and transistor output versions have different part numbers; AC-powered and DC-powered versions change the number again. A one-letter difference changes how the cabinet is wired and which loads the outputs can switch.
We apply the same rule to VFDs on the same PO. The complete catalog code includes EMC filter configuration and braking options — not just “3 kW, three-phase.” If the line item is vague, someone downstream will make a decision you didn't intend.
4. VFD OEM vs private label: decide on evidence, not the logo
If the order includes drives, this is the step we forget most often. The VFD OEM vs private label question tends to get framed as “OEM good, private label bad.” That's not how it works. We've had good service from both — and we've sent both back. The difference is verification.
When a VFD distributor quotes a badged unit, I want three things before price gets compared: the underlying model or catalog code, who owns the certification on the nameplate, and whether parameter defaults or firmware differ from the OEM version. If the seller can't answer, that's a risk, not a deal.
Earlier this year, we benchmarked two 7.5 kW drives for a pump package — one OEM-badged and one private-labeled by the VFD distributor. Under load, they behaved the same: same torque, same speed regulation. The difference was documentation. The private-label declaration didn't reference the product standard our customer's spec required. We chose the OEM-badged unit for that contract, not because the hardware was better, but because the compliance paperwork matched the label. On another order, the answer could easily be different.
When the delivery lands: checks 5-8
5. Inspect the packaging before you sign for the cartons
Receiving teams count boxes; they don't inspect them. If the delivery is supposed to be factory-sealed, the condition of the carton is part of the spec. I look for cartons that have been opened and re-taped, labels laminated over other labels, and price stickers covering serial numbers. Any one of those gets a unit quarantined until we can confirm where it came from.
A relabeled unit isn't automatically fake. It might be a returned unit, a regional transfer, or perfectly good stock that a distributor re-boxed. What it is, is unknown. And unknown doesn't belong in a new machine.
6. Record date codes and hardware revisions before stocking
When I follow Omron PLC news — firmware releases, hardware revisions, phase-out notices — the same lesson keeps surfacing: the same part number can change on the inside over its life. That's normal manufacturing refinement, but it matters for field spares, support calls, and future firmware updates.
So record the serial number, date code, and any visible version label before the unit goes into stock. It takes two minutes at the bench and is impossible to reconstruct a year later from memory.
7. Match the certificates to the serial range
The documentation gap we see most is not missing paperwork; it's paperwork that describes a model family rather than the exact units received. I compare the certificate of conformance with the packing list before approving the delivery. No serial numbers on the CoC? I ask for a version that includes them.
The declaration of conformity should also cite a product standard. For adjustable-speed drives, that usually means IEC/UL 61800-5-1 for safety plus IEC 61800-3 for EMC, depending on region. For PLC hardware, IEC 61131-2 is the relevant equipment standard. If the certificate doesn't cite any standard, treat it as marketing.
8. Run one functional spot check per batch
We don't test every PLC or drive — that's not realistic. But we test at least one unit from each serial batch before the whole lot is accepted. If the PLC has high-speed pulse outputs, and your spec says it must deliver a 6 MHz pulse train, program it to output a known number of pulses and verify what actually appears on the output. If it's a VFD, run it on a test motor and confirm output voltage and current balance on each phase.
The goal isn't to catch every possible fault. It's to catch the systematic ones — wrong firmware, wrong region code, counterfeit internals — before the batch gets scattered across four customer orders.
After acceptance: one more thing
9. Register the warranty while the packing slip is still in reach. If the manufacturer offers online serial registration, do it now and keep the confirmation. Note which project or customer each serial number goes to when it leaves your stock. At claim time, the difference between “we installed it in March” and “we don't know where that serial went” is usually the difference between a covered repair and a write-off.
The mistake I still make
Last September, a regular customer needed an extra drive line on a skid with a two-day deadline. I had two hours to decide between a bundle from our usual supplier — an Omron PLC with two private-label VFDs — and a bid that needed a longer lead time. Normally I'd order a sample and run it through the bench before committing. There wasn't time. I approved the bundle on paper. The drives arrived on schedule, but at commissioning the EMC declaration didn't match the destination's requirements.
The fix cost a site visit, replacement drives, and a blunt conversation with the customer. In hindsight, I should have pushed back on the schedule instead of letting urgency replace verification. That project is the reason this checklist starts with the PO, not with the receiving dock.
Five minutes of verification regularly beats five days of correction — and the correction is usually more expensive than you think. Decide what evidence you need before you order. Verify it when the delivery lands. Register the warranty while the unit is still in your building. That's the entire job, and it's worth doing right the first time.
