How to Get Shop Floor Visibility Without Replacing Your ERP

Most manufacturers know exactly what their problem is. They cannot see what is happening on the shop floor. Jobs go into production and disappear for three weeks. Nobody can say with confidence whether an order will ship on Friday until Thursday afternoon, when somebody walks the floor and counts.

The frustrating part is what happens next. You go looking for a fix, and the answer that comes back is that your ERP is the problem and you need a new one. Eighteen months. Six figures. A data migration project that swallows your operations manager for a year. All to solve a problem your finance system was never causing in the first place.

You do not need to replace your ERP to see your shop floor. In most cases you should not.

This is not a criticism of your ERP. It is a description of what ERP is for.

ERP systems were designed to run the commercial and financial spine of a business. Sales orders. Purchase orders. Stock valuation. Nominal ledger. Invoicing. VAT. They are systems of record, and they are good at it. If your Sage or your Business Central is doing that job properly, replacing it buys you nothing.

The shop floor works on a completely different timescale. ERP thinks in transactions, posted after the fact. Your shop floor moves in minutes. An operator finishes op 3 and moves the batch to the grinder. A machine goes down. An inspection fails and the job goes back two operations. None of that is a financial transaction, so none of it is something an ERP is built to capture as it happens.

So the gap gets filled the way it always gets filled. Paper travellers. A whiteboard. A spreadsheet somebody rebuilds every Monday morning. And a production meeting where everybody reports what they think is true rather than what is actually true.

The phrase gets used loosely, so it is worth being specific. You have shop floor visibility when you can answer these five questions right now, from a screen, without ringing anybody:

Where is job 4471 and which operation is it sitting on? How many hours have gone into it against the hours you quoted? Which work centre is the bottleneck this week? Which jobs are going to be late, and how much notice have I got? Did we make money on the last one we ran for this customer?

If answering any of those takes a phone call or a walk, you do not have visibility. You have a reporting habit.

Notice that none of those five questions are financial questions in the ERP sense. They are operational questions about work in progress. That is the tell. The gap is not in your system of record. It is in the layer between your orders and your accounts, where the actual making happens.

A Manufacturing Execution System sits between your ERP and your machines. Your ERP holds the order. The MES runs the job. The two talk to each other.

In practice, the division of labour looks like this.

Your ERP keeps doing what it does well: customer and supplier records, sales and purchase orders, stock valuation, invoicing, and everything your accountant cares about.

The MES takes over from the moment a job hits the floor: routings and operations, live job tracking, operator clocking, actual labour and material against the job, work centre capacity, scheduling, NCRs and inspection sign-off, and job level costing.

Then the two exchange the handful of things that genuinely need to cross the boundary. Orders and BOMs flow down from the ERP. Completions, actual costs, stock movements and dispatch data flow back up. DynamxMFG does this through its API, and we have production integrations running into finance systems including Sage, so the commercial record stays in one place while the operational detail lives where it belongs.

You end up with one version of the truth on the floor and one version of the truth in the accounts, and they agree with each other.

This is the first objection every time, and it is a fair one. Nobody wants two systems and double the admin.

Handled properly, it is the opposite. Right now most manufacturers already have three or four systems: the ERP, the whiteboard, the planning spreadsheet, and the paper travellers that get typed up at the end of the week by somebody who would rather be doing something else. That is the double entry. It is just informal, so it does not show up on any software line in the budget.

An integrated execution layer removes that. The operator books time once, at the machine, on a tablet or a terminal. That single entry drives the job status, the costing, the schedule, and the data that posts back to your ERP. The retyping stops.

“Our ERP vendor says they have a shop floor module.” Ask to see it running, on a tablet, with an operator using it. Some are genuinely good. Many are a data entry screen bolted onto a finance product, priced as an extra module, and requiring the same 12 month project you were trying to avoid.

“We tried software before and it failed.” Usually it failed because the scope was the whole business and the timeline was two years. Scoping it to the shop floor is a smaller, faster and much more testable project. You know inside three months whether it works.

“We are too busy to implement anything.” Being too busy to see your own production is the symptom, not the reason to wait. This is also why the timeline matters more than the feature list.

Layering an execution system onto an existing ERP is a 90 day job, not an 18 month one. With DynamxMFG that breaks down roughly as follows.

Weeks 1 to 4 are discovery and configuration: mapping your work centres, routings and operations as they actually run, and setting up the integration points with your ERP. Weeks 5 to 8 cover data migration and testing, including running live jobs in parallel so you can see the numbers reconcile. Weeks 9 to 12 are go-live and training on the floor.

Your finance system does not move. Your chart of accounts does not change. Your team does not spend a year in workshops.

Gloucestershire Machining Centre, a precision CNC business, increased capacity by 40% and went live in 90 days. Their MD, Paul B, put the value plainly: “DynamxMFG enabled us to monitor machine time and see whether we’re making a profit or loss on each component.”

CPL, which handles complex vehicle builds, now runs at 99.9% on-time delivery. Protea, a gas analyser manufacturer, needed BOMs it could change after release, something most ERP systems will not entertain. Their MD called it the single biggest improvement to the business.

Across our client base the typical picture is a 15% efficiency gain, a 10% reduction in downtime and a 20% cut in inventory costs. None of them replaced their finance system to get there.

If the pain is late deliveries, jobs you cannot find, quotes you cannot trust and margins you cannot explain, that is a shop floor visibility problem. Fix the shop floor.

If the pain is genuinely in your commercial and financial processes, then yes, look at your ERP. But be clear about which problem you are solving, because the two projects are wildly different in cost, risk and duration.

Most UK SME manufacturers we speak to have the second-cheapest option available to them and do not realise it. Keep the system that works. Add the layer that is missing.

See it running. Book a 30 minute demo of DynamxMFG and we will show you live job tracking, job costing and how it connects to the ERP you already have. No pitch, just the system doing what it does.