Non-Standard Automation Equipment in China: Is Your Product Ready for the Production Line?

Last time, we talked about whether your organization is ready to receive equipment. This time the question is different — and in some ways more fundamental.

Is your product ready for the equipment?

It sounds like a strange question. The customer defines the product. The supplier builds the equipment to match. What could go wrong?

Quite a lot, as it turns out. And the cases where it goes wrong tend to be the most expensive ones.

Three Situations Where the Product Is Ready

Before getting to the problem cases, it is worth being clear about the situations where the product-equipment relationship works smoothly — because they are real, and they represent the majority of non-standard automation projects in China.

The first is a mature product with minor updates. The customer has been making this product for years. They know its characteristics, its tolerances, its failure modes. They are building a new line to replace an older one, increase automation, or improve stability. The product is not the unknown — it is the known starting point around which the equipment is designed.

The second is a stable product currently made with high labor content. Semi-automatic processes, significant manual handling, operators managing what a machine should be doing. The product itself is understood. The objective is to automate it. The engineering challenge is real, but the product requirements are fixed.

The third is a product currently made with manual fixtures and high operator skill — usually found in early-stage or startup production. The product is understood, the tooling is simple, and automation comes later when volume justifies it.

In all three situations, the product is a known quantity. The equipment can be designed against a real specification, acceptance testing can be done against real samples, and the relationship between equipment and product is manageable.

What Happens When the Product Isn’t Ready

The situation that causes the most serious problems has become increasingly common as product lifecycles have shortened.

A customer arrives with a new product. Sometimes there are drawings. Sometimes there is a prototype. Sometimes there is neither — just a concept and a target date. The customer needs a production line, and they need it soon because their own customer is already expecting product.

The supplier designs and builds the equipment against whatever specification exists at the time. Design reviews are conducted. The design is frozen. Work begins.

Then the product evolves.

It evolves because it is new. Because early prototypes reveal issues the original design didn’t anticipate. Because the customer’s own customer changed a requirement. Because the manufacturing process for the product is still being developed in parallel with the equipment being built to run it.

When samples finally arrive on the line, they don’t behave the way the equipment was designed to expect. Dimensions that were nominal on the drawing vary more than the equipment can accommodate. A feature assumed to be consistent turns out to depend on a process variable that wasn’t controlled. The equipment needs to change — sometimes significantly.

Why Companies Do This Anyway — and Why That’s Understandable

Before going further, something important needs to be said.

Proceeding with equipment before the product is fully stable is not always a management failure. Sometimes it is a rational decision made under real competitive pressure.

Product cycles in automotive are now measured in months. In consumer electronics, the window between concept and market launch has compressed to the point where sequential development — finish the product, then build the line — is simply not compatible with the speed the market demands.

A company that waits for perfect product stability before starting equipment design may find, when their line is finally ready, that the market window has closed. A competitor who was willing to take the risk got there first. That competitor may have spent more on equipment modifications. They may have had a difficult ramp. But they have revenue and market position. The cautious company has a clean project record and no orders.

This is a real tension. In markets where product iteration is the competitive battleground, running product development and equipment development in parallel — and accepting the risk that comes with it — can be the difference between a company that survives and one that doesn’t.

The point is not that parallel development is always wrong. It is that parallel development carries costs and risks that need to be understood and planned for explicitly — not discovered during commissioning when the budget is spent and the timeline is already broken.

Who Is Responsible When Things Go Wrong

This is the conversation nobody wants to have — but that always happens eventually, usually at the worst possible moment.

The supplier’s position is straightforward: the equipment was built to the agreed specification. Design reviews were conducted. The design was frozen and approved. If the product has changed, the equipment needs to change too — and that change has a cost.

The customer’s position is also understandable: the equipment isn’t working with their product. They paid for a production line, and it doesn’t produce.

The honest answer, in most of the cases I have seen, is that both sides share responsibility. The supplier for not building enough flexibility into the design to accommodate the normal variability of a product still under development. The customer for proceeding to equipment design before the product specification was stable enough to design against.

And in practice, the cost of modifications — engineering time, hardware changes, retesting — falls on both parties regardless of what the contract says, because the contract was written when neither side fully understood what they were agreeing to.

The Timeline Pressure That Makes Everything Worse

When a product is still in development while the equipment is being built, the production schedule becomes the enemy of good engineering.

The launch date doesn’t move. The equipment has to be ready. The product samples are late. Testing takes longer than expected because every test reveals something that needs to change. The supplier’s engineers are on-site not for commissioning but for redesign — against a product that may still be changing.

The cost of this situation is not just financial. It is in the quality of the outcome. Equipment significantly modified during commissioning, under time pressure, with a product still in flux, is not the same equipment as equipment designed correctly from the start, built against a stable specification, and tested against mature samples.

It can be made to work. But it will carry the marks of how it was made — in its reliability, in its maintenance requirements, in the gap between what it was designed to do and what it actually does.

The Case That Stayed With Me

One customer I worked with was running equipment modification and product production simultaneously. The line was being changed while it was being used.

When the final acceptance was signed, the product run was also complete. The line had done what it needed to do — but only barely, and only because the supplier’s team and the customer’s team had co-managed a continuous engineering project for months.

Then the product changed again. The line that had just been accepted needed to be replaced.

From the outside, this looked like a successful project. From the inside, it was one of the least efficient uses of equipment investment I have witnessed. The line never reached the throughput it was designed for. The supplier spent more than twice the budgeted engineering time on-site. The customer got production — but not the production capability they had paid for.

What This Means in Practice

Product readiness is not a binary condition. It is a spectrum — and where a product sits on that spectrum when equipment design begins determines how much risk is being absorbed into the project.

A fully stable product with mature samples and fixed tolerances carries minimal product-related risk. A product that exists only as drawings, with no physical samples and dimensions still changing, carries maximum risk.

Between those two extremes are the situations most companies actually face: a product mostly defined but still evolving in specific areas, with some dimensions fixed and others in flux. These are manageable — but they require explicit acknowledgment of where the risk sits, design decisions that build in appropriate flexibility, and contract terms that address how the cost of product-driven changes will be handled before the equipment design is frozen, not after the commissioning engineer has been on-site for three months.

The companies that navigate this well are not the ones who wait for perfect product stability. They are the ones who go in with clear eyes about what they know and what they don’t, build that uncertainty into the project structure, and have the hard conversations about risk allocation at the start — when there is still time to act on them.

I have spent over a decade managing non-standard automation projects in China — across products that were mature and products that were still becoming — watching how that distinction determined the trajectory of the project more reliably than almost anything else.

Now I work exclusively for the buyer, providing independent technical risk advisory for foreign manufacturers procuring custom equipment in China.

Honzer Industrial & Independent Risk Consulting Suzhou, China

#NonStandardAutomation #EquipmentProcurement #ManufacturinginChina #ProductReadiness #ForeignManufacturers #ProductionLine #RiskManagement #IndependentRiskAdvisory #QualityControl #ChinaManufacturing