All articles

Enterprise Systems8 min read

How to Choose an ERP for a Small Manufacturer: BOMs, MRP, Shop Floor and Costing

A small manufacturer should choose an ERP by testing it against its own production model: how bills of materials, routings, planning, shop floor reporting, costing and quality actually work on the floor. This guide gives the requirements, a scorecard and the package versus custom decision.

Written byUsama AsifPublished

The right ERP for a small manufacturer is the one that models how your factory actually makes things: your bills of materials, routings, planning method, shop floor reporting, product costing and quality checks. Choose by running your own products and a real order through each option, not by comparing feature lists. Fit to your production model matters more than brand or size.

Most small manufacturers start ERP selection when spreadsheets stop coping: stock counts never agree, nobody knows the true cost of a job, and planning lives in one person's head. This guide is for owners, operations managers and finance leads in the US, UK and UAE who need to choose well the first time. If you already know your process is unusual enough that packages will bend it, our manufacturing ERP software page explains how we build production systems around the way a plant really runs.

What production model are you running?

Start by naming your production model, because it decides which ERP features matter. A system built for repetitive assembly can struggle with engineer-to-order work, and the reverse is also true.

Production modelWhat it looks likeERP features that matter most
Make-to-stockStandard products built to forecast and held in finished goodsDemand forecasting, MRP, reorder points, batch or lot tracking
Make-to-orderStandard designs built only after an order arrivesOrder-driven MRP, capacity planning, promised delivery dates
Configure-to-orderOptions chosen by the customer (size, finish, motor)Product configurator, rules-based BOMs, quote-to-order flow
Engineer-to-orderEach job is partly or fully designed for the customerProject or job costing, engineering change control, milestone billing
Process or batchRecipes, mixing, yields, co-productsFormulas, potency or yield handling, lot traceability, expiry
Mixed modeSeveral of the above in one plantFlexibility to run more than one model without workarounds

If you are in food, drink or another process industry, read our sibling guide on ERP for food and beverage manufacturers, which covers lots, expiry and recall in detail.

Which manufacturing features should a small manufacturer insist on?

Insist on the six areas below working with your data during demonstrations. Everything else (CRM, HR, marketing) can come later or be integrated.

Bills of materials

A bill of materials (BOM) lists the components and quantities needed to make one unit. Check that the system handles multi-level BOMs (sub-assemblies inside assemblies), phantom assemblies, scrap allowances, alternative components and units of measure that differ between buying and using (you buy steel by the sheet and consume it by the part). Ask how engineering changes are versioned: when a BOM changes, can you see which orders were built to which revision?

Routings and work centres

A routing is the sequence of operations, the work centre for each, and the set-up and run times. Without routings the ERP cannot plan capacity or cost labour and machine time. Check how the system treats subcontracted operations, such as sending parts out for plating, because that step is often where small plants lose track of stock.

MRP and planning

Material requirements planning (MRP) works out what to buy and make, and when, from demand, stock, open orders, BOMs and lead times. Test it with a real week of your orders. Look at whether planners can understand and override the suggestions, whether it plans to finite or infinite capacity, and whether it respects minimum order quantities and supplier lead times. An MRP run nobody trusts becomes a spreadsheet again within months.

Shop floor reporting

Operators need to report starts, completions, scrap and time with as little typing as possible: tablets at the work centre, barcode scans on job travellers, or terminals per cell. Ask to see the operator screen, not the manager dashboard. If the floor will not use it, every downstream number is wrong.

Product and job costing

Decide whether you need standard costing (a set cost per item, with variances reported), actual costing per job, or both. Check how labour, machine and overhead rates are applied from the routing, and how variances post to the general ledger. Your accountant should sit in on this part of every demonstration.

Quality

At minimum: inspection steps on receipt and in production, non-conformance records, quarantine stock that cannot be issued, and lot or serial traceability from supplier batch to customer shipment. If you hold a quality certification or supply regulated sectors, list the records your auditor asks for and test that the system produces them.

Which systems does a manufacturing ERP need to connect to?

Most small manufacturers need four to six connections, and each one should be named before you choose. Integration gaps are where rekeying and errors come back after go-live.

  • Accounting or payroll, if the ERP will not replace them on day one.
  • CAD or PLM, so engineering BOMs flow into manufacturing BOMs without retyping part lists.
  • E-commerce or EDI, if customers or distributors order electronically.
  • Carriers, for labels, tracking and freight costs.
  • Machines or sensors, if you want counts or run times captured automatically rather than reported by operators.

For each, decide which system is the master of the data and how often it syncs, and whether the connection is real time, scheduled or a manual import.

Should a small manufacturer buy a package or build a custom ERP?

Most small manufacturers with standard processes should start by evaluating packaged ERPs with manufacturing modules. Custom ERP is worth considering when your production model, costing method or shop floor reality is the thing that makes you competitive and packages force you to work around it.

SituationUsually better fit
Standard make-to-stock or make-to-order, conventional costingA packaged ERP with a manufacturing edition
Mostly standard, one or two unusual stepsPackage plus a small custom app or integration for the unusual step
Configure-to-order with complex pricing and rulesEither: test the package configurator hard before deciding
Engineer-to-order, project-style jobs, unusual costingCustom ERP or a package built specifically for job shops
Mixed mode across several plants or entitiesCustom, or a larger suite with an experienced implementation partner

For the general buy-versus-build trade-offs, see our ERP vs custom development comparison. If you choose a package, our ERP implementation services page explains how we help configure and roll it out.

How should you score ERP options for manufacturing?

Use a weighted scorecard filled in after scripted demonstrations using your own data. Agree the weights before you see any vendor, so the best presenter does not win by default.

CriterionSuggested weightWhat a 5 out of 5 looks like
BOM and routing fit20Your three most complex products set up without workarounds
Planning (MRP)15Suggestions for a real week of demand that your planner agrees with
Shop floor usability15An operator reports a job in under a minute without training notes
Costing and finance15Job cost and variances your accountant can explain line by line
Quality and traceability10Supplier lot to customer shipment trace in one query
Integration10Clear APIs for e-commerce, CAD or PLM, carriers and accounting
Total cost and support10Written costs for licences or build, implementation and support
Vendor or partner fit5References from plants of similar size and process

Our ERP selection criteria checklist expands each line into questions to ask.

Illustrative example: a 40-person metal fabrication shop

This scenario is illustrative, not a client case. A fabrication shop makes brackets and enclosures, half to stock for distributors and half to customer drawings. Today it quotes from a spreadsheet, plans on a whiteboard and costs jobs at month end.

  • Production model: mixed: make-to-stock for catalogue parts, engineer-to-order for drawings.
  • Critical needs: quoting from routings, job costing per order, laser and press brake capacity, subcontracted powder coating, material certificates linked to jobs.
  • What the scorecard showed: two packages handled the catalogue parts well; both needed workarounds for quoting one-off drawings and for tracking parts out at the coater.
  • Decision path: the shop could choose a package and add a small custom quoting tool, or build a custom ERP starting with quoting, jobs and shop floor reporting. The deciding factor was whether quoting speed was a competitive advantage. It was, so a custom quoting and job module was piloted first.

When is a full ERP not the right move for a small manufacturer?

A full ERP is not always the next step. Consider something smaller if:

  • You have fewer than a handful of products and no sub-assemblies. Good inventory software plus your accounting package may be enough for now.
  • Your problem is one process, not the whole business. A shop floor reporting app or a scheduling tool can fix the pain without a full replacement.
  • Nobody can own the project. ERP needs a named internal owner with time. Without one, postpone.
  • Your data is not ready. If BOMs and routings exist only in people's heads, document them first; that work is needed whatever you choose.

Small manufacturer ERP checklist

  • Production model named and written down
  • Three most complex products prepared as demo data (BOMs, routings, costs)
  • One real week of orders ready for an MRP test
  • Operator screens seen and tried by a real operator
  • Costing method agreed with your accountant
  • Quality records your customers or auditors require listed
  • Integrations listed (accounting, e-commerce, CAD, carriers, payroll)
  • Data migration plan started: which items, BOMs, open orders and stock balances move, and who checks them
  • Internal project owner named with protected time
  • Rollout sequence drafted (see which ERP modules to implement first)

How to start

Before talking to any vendor or developer, prepare four things: a one-page description of your production model, demo data for your three hardest products, a list of reports finance and production need each week, and a list of systems the ERP must connect to. Our ERP RFP template gives you a structure for putting this in writing.

Then discuss the project with us. If a package fits, we will say so. If your process needs a custom system, Timeline Digital builds 2 to 3 key modules, typically planning, shop floor reporting or job costing, as a free pilot before the full project starts, so you can judge working software on your own floor.

Frequently asked questions

What is the most important ERP feature for a small manufacturer?

Fit to your production model. A system must handle your bills of materials, routings and planning method without workarounds, because MRP, costing and shop floor reporting all depend on them. Test it with your three most complex products and a real week of orders. A long feature list matters less than whether those core records behave the way your factory works.

Do small manufacturers need MRP?

If you buy components against demand, have multi-level products or regularly run short of materials, yes. MRP turns orders, stock, bills of materials and lead times into purchase and production suggestions. If you make a few simple products from stock materials, reorder points in an inventory system may be enough for now. Either way, planners must trust and understand the suggestions.

Should a small manufacturer choose packaged or custom ERP?

Start by evaluating packaged ERPs with manufacturing editions if your processes are conventional. Consider custom ERP when your production model, quoting or costing is what differentiates you and packages force workarounds there. A hybrid is common: a package for finance and stock, with a custom module for the one process that does not fit.

How do we test an ERP for shop floor usability?

Ask an actual operator, not a manager, to report a job start, completion and scrap on the screen they would use, with barcode scanning if you plan it. Time the task and note every question they ask. If they cannot do it quickly without help, shop floor data will be late or wrong, and every cost and plan built on it will be too.

What data should a manufacturer prepare before ERP demonstrations?

Bills of materials and routings for your three most complex products, standard or recent actual costs, a week of real sales and production orders, current stock for those items, and a list of the quality records customers or auditors ask for. Giving every vendor the same data makes demonstrations comparable and exposes workarounds early.

What is the difference between standard costing and job costing?

Standard costing sets an expected cost per item and reports variances when actual material, labour or overhead differs. Job costing collects the actual cost of each order or job. Make-to-stock plants often use standard costing; engineer-to-order and job shops usually need job costing. Many manufacturers need both, so confirm with your accountant before choosing a system.

Topics in this article

  • Manufacturing ERP
  • ERP Selection
  • MRP
  • Bill of Materials
  • Job Costing
  • Small Business ERP

Start a conversation

Tell us how your business works.

Describe what is slowing your team down. We will help you work out what to build, and how a free pilot lets you judge our work before the full project.

Prefer WhatsApp? Start a chat

What happens next

  1. You send a short brief

    The problem, the people involved and any target date. A senior engineer replies within 4 business hours.

  2. We understand your workflow

    A first call about how your business works today. An NDA can be signed before you share details.

  3. You test a free pilot

    You choose 2 to 3 key modules and we build them first, so you judge real software before the full project.