Before You Buy Manufacturing ERP: Five Checks for a Small Team

Before buying manufacturing ERP, find out whether it fixes your main problem, whether your people can run it, and how much work will still fall to you.

In a small shop, the person evaluating software may also buy material, quote jobs, and answer customer calls. You need to know what you're taking on before adding another responsibility.

Use these five checks to narrow your choices and decide.

1. What work will this let us stop doing?

Pick the recurring problem that makes the change worth the trouble. Describe what should improve in terms your team can check:

• Purchasing can see what's already on order before buying more.
• Customer service can find what's holding up a job without interrupting production.
• The bookkeeper can stop entering the same invoice twice.

Name the spreadsheet, duplicate entry, or daily chase you expect to retire. During the evaluation, make the vendor show how that happens. If you'll still maintain the same information in two places, understand why.

If you already own an ERP, ask why this isn't working today. Missing capability, poor setup, and a process nobody follows need different fixes. Buying another system may leave the same problem in place.

If your accounting setup works, keeping it and adding a narrower inventory or production tool may be enough. Compare that path with replacing everything, including the work of keeping the systems connected.

Also put your few nonnegotiables in front of the vendor early. If your business depends on lot traceability, outside processing, or a particular accounting connection, say so before sitting through a general tour. Ask whether it works in the version being quoted and what extra setup it requires. Get an early price and setup estimate so you can rule out options you cannot afford or staff. Save hands-on time for one or two realistic finalists.

2. Can our people run it, including the books?

Bring a recently completed job you understand. Use a small, fictionalized version of its records in a test environment. Ask the vendor to show the parts of that job the proposed system will handle. After a short orientation, let your people repeat their parts.

Include the person who actually receives material or closes work orders, even if that person is you. Let them use the instructions and support included in the proposed purchase. Notice what they enter twice, where they get stuck, and whether they can find their place after an interruption.

Then try one ordinary problem: a short delivery, a partial shipment, or a quantity entered incorrectly. Pick something that happens in your shop. Check that the remaining work and corrected quantities are clear to the next person.

Bring your bookkeeper in before choosing. In a 2021 account from a nine-person manufacturer, the administrator said production was working six months after launch while bookkeeping remained difficult. The administrator also reported being told that some problems were setup issues. That is a reason to test bookkeeping separately from production.

If you're keeping QuickBooks or another accounting package, test the exact edition and connection you will use. Have your bookkeeper follow an invoice and a correction through both systems, check the resulting records, and find out who fixes a failed transfer. If you're replacing accounting, have them try their normal reconciliation and month-end work.

Some learning is reasonable. Requiring you to rescue the same everyday task indefinitely is a different commitment. If the test goes wrong, let the vendor check the setup and explain the process, then have your employee try again.

3. Who does the work the vendor doesn't?

Ask the person responsible for implementation to split the work into two lists: what they will do and what your team must do.

Be specific about who prepares and checks imports, sets up parts and bills of materials, verifies opening balances, and teaches each person their job. Ask what the quoted help includes and what becomes an extra charge.

A public account from a 14-person family manufacturer is useful here. The writer initially questioned continuing with ERP. In a later reply, they said they had continued and were happy with the implementation specialists. What they had underestimated was the work of changing processes, training people, and maintaining procedures.

Put a name against your share of the work and reserve time for it. Ask the vendor for an estimate based on your records and scope. If that person already has a full week, decide what can come off their plate.

Then look past launch. Who records receipts, material use, scrap, and finished work? Who updates a changed bill of materials? Where will they enter it, and who covers when they're away?

Walk through those tasks with the people involved. A report that needs information nobody has time to enter will not give you reliable answers.

4. What exactly are we paying for?

Get a written quote for the setup you actually tested, including the users, modules, integrations, and support you need. Include any required terminals, scanners, printers, or outside services.

Compare the total cost to get running and the recurring bill for the same scope. If one quote includes migration or training that another leaves to you, get that gap priced before choosing the lower figure. Keep your team's setup time visible too. Confirm what happens if data cleanup takes longer, another training session is needed, or an integration needs repair.

Ask one concrete support question: “If we can't complete this task after launch, who helps us, through what channel, and what will that cost?” Clarify who handles configuration problems as well as software bugs.

Also check the commitment you're making: contract length, renewal and cancellation terms, and any implementation refund or exit provisions. Ask how to retrieve your records and attachments if you leave. Try an export and open it.

If an important capability depends on future development, leave it marked unproven until you can test it. Price and promises don't resolve a missing requirement.

5. What does this look like in a shop like ours?

Ask to speak with someone doing similar work with similar staffing and outside help. Headcount alone isn't enough. A shop with a full-time system administrator has support you may not have.

In a 2023 discussion on Practical Machinist, a buyer said visiting a nearby, similar shop was the deciding factor. They saw the workstations and actual workflow, including an Excel tool tracker still used alongside the ERP. That is useful detail to uncover before buying.

Ask the reference:

• How much of your own time did setup take, and who helped?
• What do you still keep outside the system?
• What needs attention every week, and who does it?
• What happened the last time you needed support?

If a visit isn't practical, ask them to walk through an ordinary job on a call. A vendor-selected reference is one person's experience, but it can give you specific things to verify with your own team.

Make the decision on one page

For each finalist, write a short answer to the five questions. Record what you actually tested, the unresolved gaps, and who would own any extra work.

• Proceed when testing shows the system addresses your main problem, your people can do the work, and the remaining effort and costs are acceptable.
• Retest when a necessary step is unclear or depends on a setup change. Agree on the result you need to see before committing.
• Rule it out when a must-have fails or the system needs more time, expertise, or outside help than you can provide.

A modest workaround can be acceptable if you understand it and someone can maintain it. Don't let a long list of attractive features outweigh a problem that will land on your desk every day.

If PAX is on your shortlist, apply the same checks to us. Our fit guide explains the kinds of shops and workflows PAX is built for, along with the cases where another system may make more sense.