Do you need a new ERP to stop retyping orders?

You asked how to stop retyping customer orders, and the answer you got was a new ERP. A reseller walked through a migration plan with a timeline measured in quarters. Your controller asked what happens to 15 years of order history. Your plant manager asked who will learn the new screens during the busy season. The meeting ended with “let’s revisit next year,” and your order desk went back to typing.

Meanwhile the system you run still works. It prints pick tickets. It ships orders. It invoices. The only thing wrong with it is that every order still has to be keyed in by hand.

This page is about what changes for your order desk when that typing stops without a new system. It also covers the few times replacing the system really is the right call.

Why the “new ERP first” answer keeps people typing

The idea sounds reasonable. Newer systems are sold as ready to take orders from outside. Older ones, the thinking goes, were built for a person at a keyboard, so nothing can change until the system is replaced.

In practice that turns one problem into a much larger one. Retyping orders is a daily cost you can measure. An ERP replacement is a project that touches purchasing, inventory, production, shipping and accounting all at once. It needs data cleanup, new reports and retraining for everyone who touches an order. Many plants put it off for good reason.

So the retyping continues. It continues on ERPs that were set up before the people running them were hired. It continues on packaged accounting systems that grew into order systems, and on custom databases a programmer built in-house years ago and still maintains on weekends.

The order desk is waiting on a project that may never start. It doesn’t need to.

What a normal day on the order desk looks like

It’s 8:15 on a Monday. Eleven POs came in over the weekend. One is a PDF from a customer’s purchasing system with 40 lines. One is a spreadsheet where the quantities sit in a column nobody expected. Three are short emails from buyers who write the way they talk: “Need the usual brackets but double it this time, and send half to the Irving dock.”

Your order desk opens each one, finds the customer, then goes line by line. The customer’s part number has to be turned into yours, so someone pulls up the binder or the spreadsheet kept beside the keyboard. The quantity is in cases, but you stock in eaches. The price on the PO looks low, so someone digs out last month’s quote to see whether it changed.

By lunch the weekend pile is in. By then the morning’s new POs are waiting. The orders that came in after 3 p.m. on Friday ship a day later than the customer hoped, and two of those customers call to ask where their confirmation is.

What waiting costs on the order desk

The cost lands in a few places. Your order desk spends hours a week as typists. Orders that come in late in the day wait until morning. A mistyped quantity or a wrong unit of measure turns into a reship and a credit memo. When the one person who knows the old screens best is out, orders slow to a crawl.

There is a quieter cost too. The longer a plant runs on retyped orders, the more of its order knowledge lives in people instead of records. Which customer always means the 12-pack. Which ship-to belongs to the Irving dock. Which price on the PO is a typo and which is a new quote. None of it is written down, because nobody was ever asked to write it down. Replacing the ERP doesn’t capture any of it either.

You can size the hours yourself. Here is an example for a plant with two people who each spend about 8 hours a week entering customer orders. Put in your own headcount, hours and loaded rate.

People doing it

2

Hours each, per week

8

Loaded cost per hour

$30

Hours per month

69

Cost per year

$24,960

Hours back per month

35–49

An estimate from the numbers above, not a client result. It assumes 50%–70% of the work can be taken off your team; your audit checks that against your own numbers.

In that example, the desk spends 832 hours a year on keying. None of those hours depend on the age of your ERP. They depend on whether a person has to type every line.

Where your system stops and the work begins

Your ERP is good at holding orders once they’re in. It knows your items, your customers and your prices. What it was never asked to do is read a buyer’s email and work out what they meant. That step is where the hours go, and it is the same step on an old system as on a new one.

What changes once the typing stops

Here is the same Monday after order entry is taken off your team. Your customers don’t change a thing. They keep sending orders the way they always have.

Every PO is read, whatever it looks like. The 40-line PDF, the odd spreadsheet and the “double it this time” email are all read the way your order desk reads them. The order details are found wherever the buyer put them.

Each order is matched to the right customer, item, units and price. The customer’s part number becomes your part number. Cases become eaches. The PO price is compared with what you expect to charge that customer.

The checks your team makes from memory run on every order. Is this ship-to on file? Is the quantity far off what this customer usually orders? Is the price below the last quote? Those checks get written down once, then run every time, including on the Friday afternoon order nobody wanted to touch.

Clean orders go in. An order that passes every check goes into your ERP, or waits for one person to approve it if you’d rather keep a hand on it. You choose for each customer, and you can change it later.

Anything unclear goes to a person, with the question marked. A part number with no match. A ship-to that isn’t on file. A price that doesn’t fit the quote. Your team sees the original PO and the exact question, answers it and moves on.

Answers are kept. When someone maps a new customer part number, it is remembered. The same question doesn’t come back next week.

None of that depends on how new your ERP is. A system installed years ago gets the same checks as one bought last month.

When replacing the ERP really is the answer

Sometimes the honest answer is that the system has to go. These are the signs we look for.

The vendor no longer supports it. If nobody issues fixes for it, every year on it carries more risk. Check your vendor’s published end-of-support dates. If yours has one, that date is worth planning around now.

It can’t run on a supported operating system. Some older systems only run on old servers or old desktops that no longer get security updates. A system that can’t move off an unsupported machine is a security problem before it is an order entry problem.

The business has outgrown it. You need multiple companies, multiple warehouses or a costing method it can’t handle. Your team keeps side spreadsheets because the system can’t hold what they need.

Nobody can maintain it. The custom database depends on one programmer who is retiring, and nobody else understands it.

If any of these is true, replacing the ERP is the right project. Taking order entry off your team won’t fix it. Plan how orders will reach the new system as part of that project, not as an afterthought once it goes live. And the checks your team wrote down in the meantime go with you.

Plants that have run the same system for decades

Many plants in North Texas are long established. The Great Southwest Industrial District, which sits in south Arlington and Grand Prairie, saw work start on its first warehouse in 1956, according to the Handbook of Texas. If your plant has been in a place like that for a long time, and so has your ERP, keeping the system and stopping the retyping can both be true.

For more on order automation for manufacturers, see our guides for manufacturing. For how this works across the order desk at manufacturers and distributors, see order automation for distribution and manufacturing. For a closer look at what happens to an emailed PO, see how distributors stop retyping emailed POs.

What changes for your order desk

Your ERP stays where it is. Your team keeps the screens they know, and the reports keep running.

What stops is the typing. Orders go in the day they arrive, so the Friday afternoon POs ship on time and the chasing calls fade. Fewer wrong units reach the warehouse, so there are fewer reships and credit memos to sort out. Your order desk spends its time on the orders that need a decision, not on the ones that don’t.

And when the person who knows every customer’s habits takes a week off, the orders keep moving, because what they know is written down.

Where to start

Keep the first step small.

1. List your heaviest senders. The handful of customers whose POs your desk keys most often.
2. Save a few weeks of their orders. The real PDFs and emails, exactly as they arrived.
3. Write down what your desk checks. The ship-tos, the case sizes and the prices people double-check before they type.
4. Count the time. Have the desk note how long a normal week of entry takes for those customers, plus every reship and chasing call.
5. Go live with one customer. Your first workflow goes live within 14 days of access to your tools. Add the next customer once the first one runs clean.

It runs on the tools you already use. It starts with a free 20-minute audit call, where we look at how orders reach you today and how they get into the ERP you already run. You get a written plan within 48 hours and a fixed-scope quote after the audit.