Manufacturers stopped investing in systems. For some of them that's a mistake.

The production planner gets in at 6:45. She exports open orders from the ERP into Excel, sorts them by ship date, adjusts for the machine that's been down since Tuesday, and prints the schedule. Someone walks it to the floor.

At the end of second shift, the supervisor writes counts and scrap on a clipboard. The next morning somebody types those numbers into the ERP. Quality holds live in a third system, so when a customer calls asking where their order is, the planner checks three screens and a whiteboard before she can answer.

Nobody designed it this way. It grew one workaround at a time, and it works, as long as the same three people show up every day.

Where the cost actually lands

When systems don't talk, the gap doesn't disappear. A person fills it. Every field typed twice is labor, and it's usually labor from your most experienced people, because they're the ones who know which number goes where and which numbers to distrust.

That cost shows up three ways. Hours: a planner spending a big piece of her morning moving data instead of planning. Errors: a transposed count that turns into a short shipment. And lag: you don't know what happened yesterday until mid-morning today, which is a long time when a machine is down or a customer is upset.

The bigger problem is what happens when you grow. Add a shift, add a line, add a customer with weekly releases, and the re-keying grows right along with it. The next increase in volume means looking for another planner or another inventory clerk, which is exactly the hire manufacturers say they can't make.

Why pulling back on systems is often the right call

To be fair to the people who cut that budget: they're not wrong most of the time.

An ERP replacement is a long, expensive, disruptive project, and plenty of them go badly. Costs are up and tariffs make planning hard. Putting money into equipment that adds capacity on the floor is a reasonable choice. If your systems mostly work and the pain is concentrated in a few handoffs, a new ERP is the wrong answer to a narrow problem.

So I wouldn't argue for the big system project. I'd argue against ignoring the gaps between the systems you already have. Those gaps are where your people's hours go.

What fixing the gap looks like

You don't need a new ERP to stop re-keying. You need a narrow tool that sits between the systems you have and does the moving for you.

In the plant above, that tool would pull open orders from the ERP each morning, build the schedule in the format the floor already uses, and take shift counts from a tablet or a photo of the clipboard. It posts them back to the ERP and flags anything that doesn't reconcile: counts that don't match the order, scrap above normal, a quality hold on a job that's scheduled to ship. The planner still makes the calls. She just starts the day with the data already in place.

Roughly how it gets built:

1. Map the handoffs. Follow one order from PO to shipment and write down every place a person moves data between systems.
2. Build a working prototype against last month's real orders and counts, and check its output against what actually happened.
3. If it holds up, build the full version, connected to your systems. You own the code, so it doesn't depend on any one vendor staying in business.

Where it breaks: older ERPs with no clean way to read or write data, handwriting nobody can read, and master data that's been wrong for years (duplicate part numbers, units of measure that don't match). Some of that has to get cleaned up first, and a good build tells you that up front instead of hiding it.

When I'd tell you not to build:

• Your ERP or MES can already do it with configuration nobody turned on. Turn it on.
• Volume is low and steady, and the re-keying takes an hour a week. Leave it.
• You're truly replacing the ERP next year. Don't build a bridge to a system that's going away.

The goal is the same planner handling a third shift's worth of orders without starting at 5:30.

What the survey says

CADDi's 2026 Manufacturing Outlook Study, run with the Society of Manufacturing Engineers and based on a survey of more than 200 US manufacturing professionals, found that 79% of manufacturing leaders say the skilled labor shortage is their greatest challenge. Manufacturing departments feel it most (90%), followed by operations (48%).

At the same time, planned investment in operational systems like ERP and MES fell to 33%, down from 60% the year before. Planned investment in physical assets such as robots and equipment went up. 61% of respondents cited rising costs and inflation, and 47% said tariffs and unclear trade policy make planning harder.

Read those together and the logic is easy to follow: money is tight, equipment adds visible capacity, and systems projects feel slow. The risk is that the labor shortage doesn't stop at the shop floor. It's in the planning office and the shipping desk too, and that's where disconnected systems quietly use it up.

Try this before Friday

Pick one order that shipped last week. Follow it from the customer's PO to the bill of lading. Every time a person typed something that already existed in another system, make a tick mark. Then multiply the ticks by the number of orders you ship in a week.

That number is the hidden workload your growth plan is sitting on.

One next step

If the tally surprised you, book a 20-minute scoping call. Bring the order you traced. We'll look at the handoffs and I'll tell you whether a build makes sense or whether a settings change in the system you already own will do it.