AI for small manufacturers. When the order travels through the building.

In production everything hangs on dates that other people set: the supplier promises a week, the customer expects a day, and the machine sits between the two. Here is which part of the administration can be handed over.

One order, many stations

In a small manufacturing business an order passes through six to eight stations, and each one generates paper. The effort does not sit in any single station, it sits in the handovers.

• Enquiry and quotation, usually with line items taken from an earlier order.
• The purchase order to the supplier and the order confirmation that has to be checked.
• Goods inward: did what was ordered actually arrive, in the right quantity and on the right date.
• Production paperwork and feedback from the workshop.
• Despatch: delivery note, haulier, collection, advice note.
• Invoice, payment received, and a reminder when it is late.

The order confirmation is the sore point

Several messages arrive from the supplier between order and delivery. The second or third often contains a change, and it looks exactly like the first.

If you read them but never check them against the purchase order, you find out at goods inward. By then the machine is booked, the customer date is fixed, and a part is missing.

This is where the biggest gain sits, and it is not a technical one: every message about a live order gets held against the purchase order, every time, even when it is the fourth that week.

Certificates and documentation

In manufacturing an order often carries documentation with it: material certificates, test reports, declarations of conformity. They arrive by email, sit in a portal, or come on paper with the goods.

They are needed when there is trouble, and that is years later. Filing that happens by itself and attaches the certificate to its order is, in a warranty dispute, the difference between ten minutes and a lost afternoon.

Despatch is the last mile, and it often goes wrong

At the end comes the handover to a haulier, and two things reliably happen there. First, the haulier has no idea what it is meant to unload, because the assembly drawing is buried in the quotation and the quotation contains prices.

Second, nobody finds out that the delivery has moved, because the haulier's message lands in an inbox nobody is looking at that day.

For the first there is a clean solution: the drawings are pulled out of the order paperwork, without prices and without supplier details. What matters is that content is genuinely redacted, not painted over. A white rectangle on top of a figure looks right on screen while the text is still sitting in the file.

For the second the same rule applies as for the order confirmation: every message about a live order gets looked at and checked against the date.

What is NOT worth automating here

Production scheduling itself. Who gets which machine and when depends on set-up times, skill and how the day is going. That sits in the head of the foreman, and it is in good hands there.

Quality judgement stays with people too. A machine can record that an inspection happened, not whether the result is acceptable.

The gain sits in the administration around production, not in production itself.

Common questions

We already have an ERP system. Does this fit alongside it?

Usually yes, because the gaps are rarely inside the ERP. They are before and after it: the email from the supplier, the receipt in a chat, the test report as a PDF.

Is it worth it with twenty employees?

Yes, but the reasoning is different from a one-person business. There it is about getting your evening back. Here it is about a rule living in one place instead of in five heads.

What happens if the automation fails?

The same work as before, by hand. Which is why one rule holds: a failure has to be reported. A silent automation that has quietly stopped doing anything is worse than none at all.