ERP for Factories: Which Module Should You Start With?

By · 16 November 2026 · 4 min read

Illustration of factory ERP modules: warehouse stock in the centre, connected to sales, purchasing, production and finance

The stock figure in the system doesn't match what is in the warehouse. Sales promise delivery dates without knowing whether there is enough raw material. The production plan lives in a spreadsheet only one person understands. Then an ERP offer arrives with a dozen modules, and every one of them sounds important.

The more useful question isn't "which modules are there?" but "where do we start?" An ERP rolled out to every department at once often overwhelms the team. This article covers a sensible order for a factory, and the reasons behind it.

Start with the most expensive problem

Before comparing modules, gather your department heads and answer a few simple questions:

  • Where is money lost most often? Stock discrepancies, expired raw materials, late orders, or invoices nobody remembered to send?
  • Which work gets retyped from one file to another the most?
  • Which management questions take the longest to answer?

Write the answers down, then rank them by their impact on the business, not by which department asks the loudest. Those answers decide the first module. An ERP isn't a project to move every process into a new system at once, but a way to connect processes one by one, starting with the one that matters most.

For most factories: stock and warehouse first

Almost every other module depends on stock data. Sales needs to know which finished goods are available, purchasing needs to know which raw materials are running low, production needs to know which materials can be used, and finance needs the value of inventory. If the stock figures can't be trusted, the other modules can't be trusted either.

What needs sorting out at this stage:

  • A clean item list. One code per item, no duplicates, with clear units. For example, if a material is bought by the sack but used by the kilogram, the conversion must be recorded.
  • Storage locations. Raw material warehouse, production area, finished goods warehouse and quarantined goods.
  • Every stock movement recorded whenever goods come in, go out or change location.
  • Regular stock counts to match the system with what is physically there.
  • The inventory valuation method. The international accounting standard IAS 2 uses the FIFO or weighted average cost formula for interchangeable items. Agree the method your company uses with your accountant from the start, because it is hard to change once the system is running.

Then sales and purchasing

Once stock can be trusted, connect its two main flows. On the sales side: quotations, orders, deliveries and invoices. When an order comes in, sales can see the stock of finished goods, and the warehouse knows what to prepare.

On the purchasing side: purchase requests, orders to suppliers and goods receipts. Goods received go straight into stock, and finance knows which bills are coming. These two modules usually pay off quickly, because they remove a lot of retyping between sales, warehouse, purchasing and finance.

Production: start with an accurate recipe

The production module is often the most eagerly awaited, but it also depends most on clean data. The key is the bill of materials (BOM), the material "recipe" for each product. If the BOM is inaccurate, the material requirements and production costs the system calculates will be inaccurate too.

Start simple:

  1. Build and check the BOMs for the products you make most often.
  2. Record production orders, the materials actually used and the output, including rejects and scrap.
  3. Compare actual material use with the BOM. The differences show where the recipes need correcting.
  4. Once this data is stable, move on to material requirements planning and production scheduling.

Finance: connected, not necessarily replaced

Many factories already use accounting software that their finance team and auditors trust. An ERP doesn't have to replace it at the start. It is often safer to send transactions from sales, purchasing and stock into the existing accounting software, so nothing is retyped. A full finance module can follow once the operational modules are running smoothly. Also agree the chart of accounts and cost centres with finance from the start, so figures from the ERP and the accounting software can be reconciled.

Common mistakes

  • Moving old habits across as they are. If a process is convoluted, an ERP just makes it convoluted digitally. Tidy the flow first.
  • Migrating old data without cleaning it. Duplicate item codes and inconsistent units will spoil reports from day one.
  • Only the IT team is involved. Warehouse, production and finance must help decide how the system works.
  • Waiting for every module to be finished before anything is used. The benefits are delayed by months, and user feedback comes too late.

Getting started without disrupting production

  • Appoint an owner for each module from your own team, not just from the vendor. They are the ones who know how the process really works.
  • Count opening stock carefully before the system goes live. Wrong starting data carries on forever.
  • Start with one warehouse or one production line, then expand once it runs smoothly.
  • Run alongside the old way for a short time, and compare the results.
  • Train users for their own modules. Warehouse staff don't need to learn the finance module.
  • Set access rights from the start, so everyone only sees and changes the data their role requires.

The same step-by-step approach applies to other systems too, such as an HRIS for managing attendance, overtime and pay.

A successful ERP rarely starts with every module. It usually starts with one figure every department can finally trust: stock.

We build ERP as custom development that follows your factory's processes, module by module, starting with the one that matters most. Want to discuss which module is the right place to start? Get in touch.