2026-10-22 · Ingrid Bauer
Small Siemens PLC Orders Get Sloppier Inspections—and Buyers Are Paying for It
A quality compliance manager argues that small-batch Siemens PLC orders quietly get fewer verification checks than large ones—and names the five specific checks most buyers never ask for.
The Problem With "It's Just a Small Order"
I sent back a 12-panel batch last month. Not because anything failed catastrophically—because a stack of small things added up: one mislabeled terminal, inconsistent comments in the PLC code, and a typo on the Siemens PLC touch screen that would've embarrassed my customer in front of their own client.
The supplier's rep told me, flat out: "We don't spend as much time on orders this small."
Small-batch siemens-plc orders don't get lower standards—they get worse enforcement of the same standards. And if you're the buyer, you're the only one who can push back.
I'm a quality and brand compliance manager at an industrial automation integrator. I review every panel assembly and control system before it reaches a customer—roughly 300 units a year. I've rejected 22% of first deliveries in 2024—no, 23% if I count the partial rebuilds, I'd have to pull the log. The rejection rate on orders under 25 units was nearly double the rate on larger runs.
What Actually Gets Skipped
Here's something vendors won't tell you: inspection protocols scale with order size. A 500-unit run gets a formal first-article inspection, a signed test log, and a second reviewer. A 12-unit run gets what I'd call "representative sampling"—which in practice means somebody looked at two units and assumed the rest were fine.
On a small siemens-plc order, here's what typically gets cut:
1. Programming documentation
When you program PLC Siemens equipment, the code usually works. What gets rushed is everything around the code—tag naming, comment consistency, version control, the as-built archive.
I've caught Temp1 and Temp_01 used for the same signal in the same program. On a large run, a reviewer catches it. On a small run, it reaches a maintenance tech at 2 a.m., and now they're guessing.
2. HMI verification
The Siemens PLC touch screen powers on, the main screen loads, and everyone signs off. Nobody tests the alarm history. Nobody checks user permissions. Nobody asks what happens when the HMI loses comms with the PLC mid-cycle.
Most buyers focus on "does it display the right values" and completely miss "does it display the right alarm at the right time under load." Those are different tests.
3. Real electrical testing
I've watched assemblers verify a 24V circuit with a quick continuity beep and call it done. That's not verification—that's a smoke test.
If you're checking signal integrity, you need to see the DC symbol on the multimeter and read the actual voltage under load, not just confirm that a path exists. A loose neutral or a marginal supply will pass continuity and fail at load. On a small order, nobody's testing under load.
4. Application-specific calibration
I had a batch of heat control panel assemblies where the thermocouple compensation was configured for a different sensor type than the spec called for. On a 200-unit run, that would've tripped a calibration check at first-article. On an 8-unit run, it slipped through. The heater ran 12 degrees hot—not a meltdown, but enough to ruin a batch.
5. Terminology confusion in the spec
This one sounds minor. It isn't.
There's a persistent confusion around electrical panel vs breaker box terminology—sometimes in the buyer's own spec. A breaker box is the enclosure that holds breakers. An electrical panel is the broader assembly: bus bars, breakers, wiring, controls, terminals. When a spec says "breaker box" but the job needs a full control panel, the supplier builds to the literal words and the buyer gets something that isn't what they meant.
On a large order, somebody clarifies this before production. On a small order, it gets built, shipped, and then disputed.
The Counterintuitive Part: Small Orders Need More Documentation
Most people assume small orders need less paperwork. I get why—there's proportionally less money at stake, and buyers don't want to drown in forms for a 10-unit run.
But here's the thing: small orders are often pilots. If you're testing a new supplier with a 10-unit order, that order is your only data point for whether to scale to 200. If the documentation is thin—no test log, no calibration record, no spec sheet showing what was actually built—you don't know whether the order passed because the process works or because nobody looked.
Part of me thinks this is just the industry's default, and that a small order doesn't justify a formal report. Another part of me knows that the two suppliers who sent me clean, fully documented 8-unit orders back in 2021 are the ones I still call for 200-unit runs. I've settled on asking every vendor the same question upfront: "What does your inspection look like on a 10-unit run?" The answer sorts them quickly.
Refuting the Obvious Objection
To be fair, full inspection costs money. A signed test log and a second reviewer aren't free. If a supplier charged full inspection rates on a 10-unit order, the per-unit price would look inflated, and some buyers would walk.
Granted. But you don't need a 40-point inspection plan on every small order. You need a standard plan that doesn't get conveniently shortened when the quantity drops. Verifying every panel against the as-built drawing—not just a sample—costs a few hours. Skipping it costs a callback and a customer conversation.
More to the point: the NFPA 70 (National Electrical Code) sets minimum construction requirements for panels, but it says nothing about documentation standards for small orders. That gap is on the buyer to close in the spec. If you don't define it, you get whatever the vendor's scheduling allows.
What to Actually Ask For
If you're buying a small batch of siemens-plc panels or controls, here's the short list I'd push for in writing:
- A wiring check against the as-built drawing—every unit, not a sample
- The program archive with commented code—including the tag database, not just the running project
- HMI alarm test results—what fires, when, and what the operator actually sees
- Voltage readings under load—with the meter's DC symbol visible on the report, not just the word "passed"
- A one-page spec reconciliation—confirming electrical panel vs breaker box scope, sensor types, and anything else a vendor might interpret loosely
That's not a big ask. On a 10-unit order, it's maybe three extra hours. If a supplier resists, that tells you something about how they'd handle an actual problem.
Restating the Point
Small orders aren't test runs for the vendor—they're real money and real risk for the buyer. Treating them as low-priority is a choice, not a necessity.
The vendors who treated my $300 orders with the same rigor as my $30,000 ones earned the larger business later. The ones who told me "we don't spend as much time on orders this small" didn't get a second call.
If a supplier's quality process only kicks in above a certain order value, that's not a quality process. That's a filter. And you're on the wrong side of it.
