How to Specify a Custom Control Board for Packaging Machines: 7 Specs to Define Before You Buy

A buyer sends a photo of an old control board and a message: “Can you make this?”

The supplier replies with a price. A few months later the boards arrive, the connectors are on the wrong side, one input signal is the wrong voltage, and the firmware is locked to a vendor nobody can reach. The board works — it just does not work here.

Here is the claim this article defends: custom control board projects rarely fail in the factory. They fail in the RFQ, before a single component is placed. The manufacturing part is solved; the specification part is where money quietly disappears.

You would think sending the old board is the fastest route to an accurate quote. It is the fastest route to a plausible one. A photo tells a supplier what the board looks like. It tells them almost nothing about what the machine needs the board to do.

Why a photo is not a specification

A control board is not a component you buy. It is an interface between a machine and the physical world: signals in, signals out, power, timing, environment. Two boards can look identical and behave completely differently — one drives 24 V solenoid valves directly, the other only sends logic-level signals to a separate relay bank. Same footprint, same connectors, different machine.

When you send a photo, you are asking a supplier to guess the parts you cannot see. Every guess becomes an assumption, and every assumption either gets buried in a price you cannot audit or surfaces later as a change order. The cheapest quote in a custom-electronics tender is usually the one that assumed the most.

The seven specifications to fix before you ask for a price

1. Inputs and outputs, counted and typed. Not “about twenty signals”. Write out every input and output: digital inputs (sensors, limit switches, e-stop), digital outputs (valves, relays, indicators), analogue channels (temperature, pressure, load cell), and their voltage and current levels. The I/O list is the single biggest driver of board complexity and cost.
2. Voltage and power budget. The board’s logic supply is usually low-voltage DC, but what it switches is often not. State the supply voltage, the total current draw, and whether any output drives an inductive load — solenoids and motors generate back-EMF that will destroy a board designed without suppression. This is where “it worked on the bench” gets decided.
3. Communication protocol. Modbus RTU, Modbus TCP, CAN, EtherNet/IP, or a plain serial link to the HMI? A mismatched protocol is not a firmware tweak; it can force a redesign. If the board has to talk to an existing PLC or touchscreen, name the exact model and protocol — not the brand alone.
4. Environmental rating. Packaging halls are wet, dusty and warm. Specify the ingress protection needed, the operating temperature range, humidity, vibration, and whether the board will be washed down. A board rated for a clean cabinet will fail in a washdown zone, and no warranty conversation will make that a supplier’s fault if the requirement was never written down.
5. Form factor and mounting. Dimensions, mounting hole positions, connector types and connector orientation, and how the board is held — standoffs, DIN rail, edge guides. Connector orientation alone causes a surprising share of “it doesn’t fit” returns, and it is free to specify.
6. Firmware ownership and update path. Who owns the firmware? Can you get the source, or at least the ability to modify parameters? Can the board be updated in the field, and how? A board you cannot update is a board you cannot fix — and if the original developer disappears, you own a brick. Settle this in writing before the first unit is built.
7. Certification, documentation and traceability. Which certifications does the finished machine need, and which of them fall on the board? Ask for the bill of materials, the schematic, the test procedure and the serial-number traceability record. If a certification body later asks how a unit was tested, the answer has to exist on paper.

You would think you can settle these details after the quote. You can’t. Every one of them changes the price, and a supplier who quotes without them is quoting a different board from the one you need.

What this costs — and why the number is not the point

Custom electronics pricing moves with layer count, I/O count, connector count, enclosure and certification scope. For a moderate-complexity industrial control board, engineering and tooling typically land in the low thousands of USD, with per-unit cost falling as volume rises. Treat that as a shape, not a quote: the range is wide, and the two things that move it most are the I/O list and the certification requirement.

The reason this matters more than the price itself is what a bad board costs downstream. When a control board fails to fit, or cannot be updated, or its protocol will not talk to the HMI, the money you lose is not the board. It is the production days. A board is a rounding error next to a stopped line — which is why spending an extra week on the specification is almost always the cheaper choice.

Frequently asked questions

Do I need a custom control board, or can I use an off-the-shelf PLC?
Often an off-the-shelf PLC is the right answer. A custom board is justified when you need tight integration, a specific form factor, high channel counts, or a cost point a PLC cannot reach at volume. Ask the supplier to name which of those applies to your machine — a supplier who recommends a custom board for every project is not giving you engineering advice.

Can you copy an existing board exactly?
A functional replacement is usually possible; a literal copy often is not, and copying an obsolete design locks in the same obsolescence you are trying to escape. Expect the supplier to ask for the I/O list and protocol so they can rebuild the function rather than the artwork.

How long does a custom board project take?
It moves with complexity and certification scope. Treat any lead time quoted before the I/O list and the protocol are fixed as provisional.

What happens if the supplier stops supporting the board?
This is why firmware ownership belongs in the contract. If you hold the source, or at least parameter access and the documentation, another competent electronics supplier can pick the board up later. If you don’t, you are dependent on one vendor for the life of the machine.

How we handle it

We source control boards for the packaging and wet wipes machines we deal in, so we sit on both sides of this: the buyer who needs a board and the supplier who builds it. The projects that go smoothly are the ones where the I/O list and the protocol were nailed down before anyone discussed price.

If you are replacing an obsolete controller, or developing a machine and need a custom board, send us the I/O list, the protocol, and the environment. If you only have a photo, send that too — we will tell you honestly which of the seven specifications above are still missing, before it costs you a redesign.

WhatsApp: +852 9702 5284 — Get a quote in 24 hours: sales@zhenbaotrading.com

Maggie (岳乙晴)
Founder / Sales Director
Zhenbao Trading | Machinery Sales & China Sourcing Agent
sales@zhenbaotrading.com
WhatsApp: +852 9702 5284
www.zhenbaotrading.com