What we do
Tools
Industries
Department
How we workLet's talk →
Home/Industries/Manufacturing
Manufacturing

Manufacturing ERP That Goes Live on Numbers Your Floor Agrees With

ERP projects rarely fail on the software. They fail on bills of materials nobody updated, stock counts that were never right, and orders that still arrive by email after go-live. Start with how your plant builds things, because that narrows the field faster than any feature list. Then get the data ready, and connect what the ERP doesn't reach.

2manual handoffs
0automated
KEY IN BY HANDRECOUNT WEEKLYBuyer POsemail + portalsERPorders + BOMsFloor + bookscounts + costs
Your people are doing the work of connectors.

Carrying data from one system to the next by hand is slow, error-prone and costly, and it isn’t what they’re here for. It’s not a people problem. It’s a plumbing problem.

How you build decides the shortlist

Headcount matters less than production style. A make-to-order shop with 15 people has more in common with a 150-person job shop than with a 15-person bottling line.

How your plant works ERPs that usually make the list Make the demo prove this
Small batches made to stock, sold through your own store and a few wholesale accounts Katana, Odoo, or Fishbowl alongside QuickBooks What happens to a wholesale order that arrives as a PDF, not through the store connection.
Make-to-order or job shop: quotes, routings, every job a little different A job-shop ERP, or Acumatica or Dynamics 365 Business Central with manufacturing set up Quote to job to invoice on one of your real jobs, with actual hours and scrap posted against it.
Batches, lots and expiry dates: food, drink, chemicals, supplements A process ERP with lot tracking. See food manufacturing ERP and brewery software A mock recall: trace one finished lot back to its supplier lots in minutes. More on food traceability software.
Outgrowing QuickBooks, more than one entity or warehouse NetSuite, Acumatica or Business Central How intercompany transfers and landed cost are handled. Some firms stay on QuickBooks Enterprise with Advanced Inventory a while longer, and our QuickBooks Enterprise vs NetSuite page weighs that call.
Several plants, often across countries, with a corporate parent SAP or Dynamics 365 Who owns the integrations after the partner leaves. That bill outlasts the license.

Five things to know about your own plant before the first demo

Vendors bring tidy sample data. Answer these first and you'll see quickly which ERP bends to your process and which one asks you to bend.

  • How many of your BOMs match what the floor actually builds?

    If the honest answer is "most, roughly", costing will be wrong in any ERP until they're fixed.

  • When was stock last counted, and how far off was it?

    Go-live starts from a count. A system loaded with wrong quantities loses the floor's trust in the first week.

  • Where do orders arrive today?

    Email, buyer portals, EDI, phone and your own store each need a route in. List them all before anyone quotes you an implementation.

  • What does the floor write on paper?

    Travelers, time sheets and scrap logs are where actual cost lives. If none of it reaches the ERP, job costing is a guess.

  • Who will own the system once the consultants leave?

    Every ERP needs someone inside who knows where the settings are. Without that person, workarounds pile up in spreadsheets again.

Getting your data ready for go-live

This is the part vendors tend to hand back to you. It decides whether the new system is believed.

  1. 1

    Clean the item master

    Merge duplicate part numbers, retire items nobody has bought in years, and settle units of measure. A part bought by the box and used by the each needs both, with the conversion.

    Watch for: parts that exist twice under a supplier's number and your own. They split stock and double the reorders.

  2. 2

    Rebuild BOMs and routings from the floor, not the old file

    Walk each product with the lead hand who builds it. Add the components and steps everyone knows about but nobody wrote down, and the real run and setup times.

  3. 3

    Count stock and pick the cutover date together

    Count as close to the switch as you can, with receiving and shipping held for the day. The opening balance in the new ERP is that count, valued at the cost your accountant signs off.

  4. 4

    Carry open orders across with their history

    Open sales orders, purchase orders and work orders move with what's already been shipped, received or completed against them, so nothing is shipped or bought twice.

  5. 5

    Close the first month in both, then retire the old one

    Run the first month-end close in the new system and check inventory value and margins against the old reports. Then set the old system to read-only.

    Watch for: a gap in inventory value. It usually points to a BOM or a unit of measure from step one.

What still lands on a person once the ERP is live

A manufacturing ERP holds the plan. It doesn't go and fetch what happens outside it, and these gaps keep someone retyping.

A buyer's PO arrives as a PDF

How you'll know: Someone opens the email, checks stock, keys the sales order and writes back with a date. Four steps, every order, and the busy day is when one gets missed.

Fix: Read the PO, create the sales order, check it against stock and open work orders, and send the buyer a scheduled date, with a person only for the exceptions.

Engineering changes a part, and the BOM finds out later

How you'll know: A revision is released in CAD, but production builds the old version for another week because the ERP's BOM was never updated.

Fix: Send released revisions to the ERP as a BOM change for someone to approve, with the effective date on it.

The floor still runs on paper travelers

How you'll know: Hours, scrap and completions are written down and typed in at the end of the week, so costs on a job only show up after it ships.

Fix: Capture time and quantities at the station, on a tablet or by scan, posted to the work order as it happens.

Retail customers want their own shipping paperwork

How you'll know: A big buyer requires an advance ship notice and its own label format, so someone builds both by hand for every shipment.

Fix: Produce the ship notice and labels from the shipment record and send them in the format that customer asks for.

Floor counts and the books drift apart

How you'll know: Inventory value in accounting no longer matches the stock report, and month end turns into a hunt.

Fix: Post every receipt, issue and completion to the ERP and the books from one transaction, and flag the ones that don't match before the close.

What this looks like in practice

Small Batch Manufacturer

A contract manufacturer running Katana for production, selling through its own site and two wholesale accounts.

Wholesale orders land in Katana automatically as soon as they arrive, checked against live stock and production capacity, with a confirmation sent back to the buyer without anyone touching the order in between.

ERP and inventory systems we connect

Choose yours to see what we usually build around it.

SAP logoNetSuite logoDynamics 365 logoOdoo logoAcumatica logoZoho Inventory logoCin7 logoKatana logoFishbowl logoBrightpearl logoinFlow logoDEAR logo
Let's talk

Choosing an ERP, or living with one that never settled in?

n-frames helps manufacturers shortlist an ERP that fits how they build, gets BOMs, routings and stock counts ready for the switch, and connects it to the order inbox, the floor and the books so nobody keys the same order twice.

Book an ERP fit call →

Questions manufacturers ask

We already have an ERP. Is this still useful?

Yes, and it's the most common case. Most of the work is around the ERP you have: getting orders into it from email and portals, getting floor data back, and making its stock numbers match the books.

Can you handle our odd production steps?

Usually. An outside finishing step, a rework loop or a cure time can be modelled as a routing step or built as a workflow beside the ERP, so you don't have to change how the floor works to fit the software.

Is this manufacturing automation software?

Not a separate product. We build manufacturing automation into the ERP and shop-floor tools you already run, so there's no extra system for your team to learn.

What is the best ERP for a small manufacturer?

It depends on how you build. Small make-to-stock brands often start with Katana or Fishbowl next to QuickBooks. Job shops need quoting, routings and job costing first. Batch producers need lot tracking. The table at the top of this page sorts that out.

How long does a manufacturing ERP implementation take?

For a small plant with clean data, a few months is realistic. Most of the time goes on BOMs, routings, stock counts and open orders rather than on setting up the software, which is why the prep steps above matter so much.

Who moves our BOMs, routings and open orders into the new ERP?

n-frames does, alongside your team and the ERP partner if you have one. We rebuild the data from what the floor actually does, load it, and check the first month-end close against your old reports.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.