MES for Machine Shops: Route Cards, Batches, Inventory

Most machine shops don't lose money on machining. They lose it in the gaps between machining: a batch waiting two days for the next operation nobody knew it was ready for, material that ran out mid-order, a rejected part discovered only at final inspection. A manufacturing execution system (MES) exists to close those gaps - and it doesn't have to be an enterprise monster to do it.

What an MES Does That Your ERP and Spreadsheets Don't

An ERP knows the order exists. A spreadsheet knows what someone last typed into it. Neither knows what is happening on the floor right now. An MES sits exactly there: it takes an order, breaks it into process steps, and tracks every batch through those steps as operators complete them.

For a machine shop, the useful core is small:

• Process flow per part - the sequence of operations (saw, mill, deburr, inspect, coat, ship), defined once and reused on every order.
• Route Cards - the document that physically travels with the batch, with a barcode, the step list, and space for quantities and rejection notes.
• Batch tracking - who completed which step, when, how many passed, how many were rejected and why.
• A live board - kanban and Gantt views so planning sees every order's position without walking the floor.

The Route Card Is Still the Backbone

Digital or printed, the Route Card remains the single most effective shop-floor tool ever invented: one page that answers "what is this, what has been done to it, and what happens next." A modern MES doesn't replace it - it generates it. The card is printed from the system with a barcode, operators record step completions against it, and the digital record stays in sync with the paper that travels with the parts.

Inventory Control Belongs in the Same System

A production plan that doesn't see stock is fiction. When inventory control lives inside the MES, the loop closes:

• Material catalog and stock ledger - every receipt, allocation, and consumption is a movement in one ledger, not a cell in a spreadsheet.
• Allocation to parts and orders - material is reserved when production is planned, so two orders can't silently claim the same bar stock.
• Minimum stock alerts - the system flags material below threshold before it stops a job, not after.
• Purchase orders and suppliers - replenishment is tracked to the same catalog, so incoming material lands in the ledger the moment it arrives.

Quality Data in the Production Flow, Not Beside It

The most expensive words in manufacturing are "we found it at final inspection." When inspection is a step inside the process flow, quality data attaches to the batch as it moves: measurements recorded at in-process checks, rejection reasons captured per step with a category the whole team shares, and audit-ready inspection reports generated from the same records. Traceability stops being a binder-hunting exercise - the batch history is the trace.

This is also where the business side connects. Orders, customers, deliveries, and production status draw from one dataset, so quoting a delivery date or answering a customer's "where is my order" takes seconds - and the same records feed whatever ERP or business tools you already run.

What "Right-Sized" MES Looks Like

Signal	Enterprise MES	Right-sized for a shop
Setup	6-18 month implementation project	Define process flows, print first Route Card the same week
Operators need	Training courses	A browser and a barcode
Process changes	Consultant visit	Edit the step template yourself
Quality	Separate QMS module, extra license	Inspection is a step in the flow
Inventory	Interface to another system	Same platform, same records

QA-Report's MES production planning was built on the right-hand column: process constructor, Route Cards with barcodes, batch split and merge, live kanban and Gantt boards, rejection tracking, and inventory control with stock movements, allocations, minimum-stock alerts and purchase orders - all in the same platform as the inspection reports.