Why the visibility gap exists
Large retailers and OEMs solved this with EDI. Retail programmes typically require an order acknowledgement inside 24 to 48 hours, accurate advance shipping notices, and apply on-time-in-full penalties for failures.
Almost no SME machine shop is EDI capable. The cost and the IT effort do not fit a business turning over a few million pounds with no dedicated IT function.
So you get email and spreadsheets, and you get them only when you ask. Make UK and Infor reported back in March 2023 that a quarter of manufacturers were not monitoring their supply chains digitally at all, and urged wider adoption. That figure is now several years old, so treat it as directional, but the pattern in small machine shops has not changed much.
The gap is not laziness. It is that nobody ever specified the requirement.
What to ask for, in order of value
- Order acknowledgement, same working day. It should confirm quantity, unit price, drawing revision and promised despatch date. This is where wrong-revision and wrong-quantity errors get caught, before any metal is cut.
- A weekly status update on a fixed day. Fixed day matters. It removes the decision about whether to chase.
- Early warning on a date at risk. State the trigger in the PO. As soon as the promise date is known to be at risk, not on the due date.
- Despatch notification with carrier and tracking. Your goods-in can plan, and you stop guessing.
- A digital documentation pack per despatch. Certificate of conformity, material certificates, inspection records, as one PDF pack tied to the delivery note. The contents are covered in the traceability guide.
- A live status lookup. Nice to have. Everything above is more valuable, and much easier to get.
The three levels of supplier digital maturity
| Level | What it looks like | What you can expect | What to do |
|---|---|---|---|
| Spreadsheet shop | Jobs tracked on a whiteboard or in Excel, status known only by walking the floor | Status on request, often inaccurate, no early warning | Specify a fixed weekly update in writing and accept some manual effort. Do not expect a portal |
| ERP shop | MRP or ERP system with job numbers, routings and scheduled operations | Accurate status in seconds, reliable acknowledgements, early warning if they choose to use it | Ask what system they run and require the four items above in the PO |
| Portal shop | Customer-facing self-service view of orders and documents | Self-service status, downloadable documents, no phone calls | Rare in UK SME machining. Worth paying a small premium for if it exists |
The jump from level one to level two is the one that changes your week. Level three is comfort on top.
How to choose
If price is your only criterion and you have admin capacity to chase, a spreadsheet shop is workable. Budget for the chasing time honestly, because it is real cost sitting in your team rather than in the unit price.
If you place repeat orders and your team is small, buy from a level two supplier and write the four requirements into your PO terms. This is the highest-return move available to most SME buyers and it costs nothing.
If you are running kanban or call-off, you need level two as a minimum, because a shop without a live schedule cannot commit to a call-off reliably.
Here is the honest counter-argument. Digital maturity is not machining capability. Some of the best process control in the UK sits in shops that still plan on paper, and some very slick portals sit in front of mediocre engineering. Do not select on software alone. Use it as a tiebreaker between two technically capable suppliers, and as a leading indicator of planning discipline.
What this looks like in practice
TrueNorth runs orders through MRPeasy as its ERP and Zoho CRM on the commercial side. Every order has a job number, a routing and a promised despatch date, which is what makes a weekly status update a lookup rather than five phone calls around the North West.
During 2026 we have been building a three-sided collaboration platform to sit on top of that, giving suppliers and customers their own self-service views of orders, documents and status. It runs on Next.js and Supabase, hosted in the EU region, with Cyber Essentials and ISO 27001 practices designed in from the start rather than added later.
The reason for building it rather than buying it is specific. Standard ERP handles the sell side well and the buy side poorly, and the buy side is where an intermediary lives. The customer-visible outcome we are aiming for is simple. You should never have to ask us where your order is.
Until that is live, the discipline is manual and the commitment is the same. Acknowledgement the same day, a fixed weekly update, early warning before the due date, and the documentation pack with the parts. When a supplier will not commit to any of that, you are usually looking at the going quiet problem in advance.