Why I Trust a Supplier Who Says 'That's Not Our Specialty'

Last Quarter I Rejected a Quote Because They Said 'We Can Do Everything'

I'm a quality/brand compliance manager at an industrial controls company. I review every deliverable before it reaches customers—roughly 200 items a year. In 2024, I rejected about 12% of first deliveries for spec drift. As of February 2025, that number isn't improving.

The quote in question was for a control panel with an Omron PLC NX processor. The sales rep wrote:

We can handle just about anything.

That should have been reassuring. It wasn't. In my opinion, the most trustworthy automation supplier is the one who tells you what they won't do.

Before you label me cynical, hear me out. 'omron-plc' is a search query, not a solution. What matters is how a supplier turns that query into a deliverable—and whether they know where their own expertise ends.

When 'No' Sounds More Confident Than 'Yes'

Earlier this year, we sent the same I/O list to two suppliers. One came back with a detailed Omron PLC NX proposal and a note: 'We don't design the high-voltage section. Here's a partner who does.' The other sent a one-page quote that said, 'No problem, we handle it all' (which, honestly, was the most expensive thing they could have sent me).

When I compared the specialist's quote and the generalist's quote side by side—same I/O list, same Omron PLC NX processor, same delivery expectations—I finally understood why boundary statements are a quality signal. A boundary is a form of specification. It says the vendor read your drawings and knows exactly which part of the scope they own.

Why does this matter? Because a quote that refuses to overpromise gives you a clear baseline for acceptance. You know what you're getting, and you know what you're not getting. That's infinitely better than a vague 'we'll take care of it.'

Last year I ran a quick test with our team: same drawing set, two cover pages—one from a focused controls firm, one from a broad electrical service company. Every senior reviewer identified the focused firm's package as more professional before they saw the name. The difference wasn't the logo. It was the boundary notes on the drawing.

A Control Panel Is Not a Control Panel

Here's the thing: the term 'control panel' covers a lot of ground. A motor control center, an Omron PLC NX cabinet, a plane control panel, and the Whirlpool Cabrio control panel behind your washing machine all share the same noun. They do not share the same wire sizes, thermal loads, certification paths, or safety margins.

A plane control panel has redundant channels and avionics-level validation. The Whirlpool Cabrio control panel is a sealed module that gets replaced, not field-programmed. A machine control panel with an NX controller is its own animal, with I/O mapping, safety ratings, and a grounding plan. A supplier who promises all of them is either enormous or uninformed.

Ask that supplier which standard they build to. If the answer is 'we do whatever the customer wants,' run. A quality audit needs a reference point. Without one, every acceptance test becomes an argument.

I'd rather work with a specialist who knows their limits than a generalist who overpromises. That sentence should be printed on every RFQ.

The Generalist's Quote Costs More Than the Price

In 2023—before we tightened our verification protocol—we approved a vendor who had no qualms about saying 'yes' to a custom HMI project on an Omron PLC NX series. The HMI was a mess. Screens didn't match the machine sequence, tags were named randomly, and the FAT had to be stopped after two hours. (mental note: never waive FAT on a custom HMI.)

That quality issue cost us a $22,000 redo and delayed our launch. A lesson learned the hard way. The PLC itself was fine. The problem was a supplier who had never said 'this isn't our strength.'

We now budget for Omron PLC training courses for our maintenance techs—not because the manuals are unclear, but because a trained team can catch those issues during FAT instead of after installation.

Here's something vendors won't tell you: 'standard lead time' often includes buffer time. It's not a promise that your order takes exactly that long; it's the latest date they'll commit to. A specialist who gives you a realistic lead time with buffer for commissioning is more useful than a generalist's optimistic date with no margin.

The Car Air Filter Test

Real talk: I know how to change air filter in car. I watched the same two-minute video everyone watches. That doesn't make me an automotive technician, and it definitely doesn't mean I should give axle-replacement advice. The same logic applies to content and capability.

When a vendor writes a detailed guide on how to change air filter in car, and also claims to be a deep resource for safety PLCs, I want to know who's actually writing the PLC content. Content boundaries mirror capability boundaries.

Since I implemented our verification protocol in 2022, I've tracked quotes that contain at least one 'we can do that' outside the vendor's demonstrated history. I don't have the exact number in front of me, but I'd guess it's around a third of the failures we catch. Not ideal, but workable—we ask more questions now.

The Fix Isn't 'Everything,' It's Structure

Per FTC guidelines (ftc.gov), advertised claims have to be truthful and substantiated. I'd extend that to engineering proposals. If you claim you can build any control panel, the burden of proof is on your drawing set, not your sales page.

That's why standards exist. IEC 61131-3 defines the five PLC programming languages—Ladder Diagram, FBD, ST, IL, SFC. UL 508A sets the benchmark for industrial control panels in North America. A specialist works within those structures. A generalist says 'it's basically the same thing' when it isn't.

Structure creates trust. The Omron PLC NX series supports structured programming, and Omron PLC training courses reinforce it. But training doesn't turn a good controls engineer into a multi-industry superhero. It makes them a better controls engineer. That's the kind of concentration I value.

The Objection I Hear Every Time

Now, you might say: 'But Omron itself sells a huge variety of products. PLCs, sensors, safety relays, robots. Isn't that a generalist?' Good question.

The difference is depth versus breadth. A company can have a broad product portfolio and still be disciplined about application design. The NX series and CP1L are both Omron PLCs, but they solve different problems. A competent supplier will tell you which one fits your I/O count and cycle time. They won't pretend a CP1L can do what an NX processor does just because they're both Omron.

Another objection: 'We need one supplier for everything; isn't that easier?' I get it. Procurement teams love a single vendor. But in practice, one vendor who subcontracts clear pieces is easier than one vendor who improvises. I'd rather manage a contract with a named partner for the high-voltage section than clean up an ungrounded panel.

That's also why I believe a supplier who says 'this is outside our specialty—here's a better fit' deserves the next project. The vendor who said 'this isn't our strength—here's who does it better' earned my trust for everything else. I'd rather work with a specialist who knows their limits than a generalist who overpromises.

Bottom Line: Boundaries Are Specs

When I compare a deliberately scoped proposal with a broad 'we can do it all' promise, I know which one will survive a quality audit. The scoped proposal has a drawing set that matches the I/O list. The broad promise has a logo and a hope. (Not that hope is a bad thing; it just shouldn't be part of an engineering contract.)

Take this with a grain of salt if you want, but I've been on the receiving end of too many 'minor revisions' that were actually full redraws. In my opinion, the most professional phrase in an automation quote is not 'we can do it.' It's 'we don't do that, and here's who does.' It shows the supplier read the spec, knows the standards, and cares more about the project than the invoice. I'll take that over a blank check every time.