ERP for Factories 2026: A Guide for Small and Mid-Size Manufacturers

Factory owners describe almost the same problem. Sales has taken an order but nobody knows if there is enough raw material. Production asks about stock over LINE. Accounts closes month-end costs from several Excel files that never agree. When a customer asks “when will it be ready?”, someone has to walk the floor asking each line supervisor. This is exactly where a factory ERP earns its keep.

A factory ERP is software that keeps sales, purchasing, warehouse, production, quality control and costing in one database, so every department works from the same numbers. What sets it apart from a trading-company ERP is that it has to handle turning raw materials into products, which brings recipes, process steps and waste into the picture.

This guide is written for small and mid-size manufacturers in Thailand, such as food processors, rubber and seafood plants, furniture makers and OEM producers, who are starting to feel that Excel can no longer keep up. If you want to compare ready-made packages first, see our comparison of popular ERP software.

Why factories need ERP more than most businesses

A shop buys one item and sells one item. A factory buys dozens of raw materials, combines them by recipe, runs them through several stations, loses some along the way, and ends up with finished goods. That complexity scatters data very quickly.

Common problems in factories without a system:

Ordering raw materials by guesswork. Some items run out and stop the line; others pile up until they expire.
Not knowing the real unit cost. Prices get set by feel or by material cost alone, leaving out labour and overhead.
No lot traceability. When a customer complains about one batch, you cannot trace which material lot or supplier it came from.
No production planning. You accept more work than capacity allows, or machines sit idle while orders wait.
Duplicate paperwork. The same data is typed into several places, which wastes time and invites errors.

ERP does not fix everything on its own, but it lets data flow from sales order to production plan to material issue to cost, without copying by hand.

Core modules a factory ERP should have

You do not need every module on day one, but you should know what each one does so you can prioritise correctly.

1. BOM (Bill of Materials)

A BOM lists the materials and quantities needed to make one unit. For example, one jar of chilli paste uses chilli, garlic, oil, a lid, a label and a carton, each in a set amount. A good BOM supports multiple levels (semi-finished goods used in other products) and a waste allowance. The BOM sits at the heart of everything: if it is wrong, stock, purchasing and cost will all be wrong too.

2. Production orders (work orders)

A work order says what to make, how many and by when. The system calculates the materials to issue from the BOM and tracks status: waiting, in progress, completed, actual output and scrap. Multi-step plants may also need routing, which defines the stations a product passes through and how long each takes.

3. Inventory

Separate warehouses for raw materials, work in progress (WIP) and finished goods. Support for multiple units of measure (buy by the sack, use by the kilo), lots and expiry dates, and stock counts. If inventory is your biggest headache, see our inventory management system service.

4. Purchasing

From purchase requisition and purchase order to goods receipt and payables. A good system suggests what to order and how much, based on the production plan and minimum stock levels. That part is called MRP, which we cover on the MRP material planning system page.

5. Quality control (QC)

Record inspection results for incoming materials, in-process checks and final inspection, all tied to lots. Anything that fails is held so it cannot be issued. This is critical for food plants that need traceability for standards such as GMP or HACCP.

6. Production costing

Combine material cost, direct labour and production overhead to get cost per unit and per lot, then compare standard cost against actual cost to find leaks. This module is often pushed back to a later phase, yet it is the one owners get the most value from.

Module summary

Module	Question it answers	When to start
BOM	What does this product use, and how much?	Phase one (essential)
Work orders	What are we making, when, and how much came out?	Phase one
Inventory	Where is it, how much is left, which lot?	Phase one
Purchasing / MRP	What do we need to order, and when?	Phase one or two
QC	Did this lot pass, and can we trace it?	As your industry requires
Costing	What is the real cost per unit?	Phase two, once data is stable
Sales / accounting	Who owes us, and what is the margin?	Depends on whether you keep your current accounting software

Rolling out a factory ERP without stalling

ERP projects rarely fail because of the software. They fail because of planning. The order we recommend:

Map your current process first. From order intake to delivery: who does what, which documents are used, where things slow down or go wrong.
Pick the two or three most painful problems as phase-one goals, such as “stock doesn’t match” and “we don’t know when to reorder materials”.
Clean up master data. Item codes, material codes, units, BOMs and supplier lists. This always takes longer than expected.
Choose your approach: off-the-shelf, customised or built from scratch (see the next section).
Pilot with a small product group. Pick a few items or a single line and run it alongside the old method for a while.
Train the people on the floor, especially warehouse staff and line supervisors, because they enter the real data.
Do an opening stock count. Opening balances must be right, or every report afterwards will be wrong.
Expand to other modules such as costing, QC or accounting integration once phase one is stable.

Common mistakes when factories implement ERP

Buying a system that is too big. Every module goes live at once, staff can’t cope, and everyone drifts back to Excel.
BOMs that don’t match reality. The recipe in the system differs from what the floor actually uses, so stock goes negative every week.
Not recording scrap and over-issues, which makes cost figures look better than they really are.
Letting IT or the developer design it alone, without production and warehouse people involved from the start.
Data-entry screens that are too hard for people standing on a factory floor. Design for tablets and phones with barcode scanning.
No internal system owner, so when problems come up nobody makes the call.
No plan for backups and user permissions, so everyone can see every cost and price.

Off-the-shelf, customised or custom-built: how to choose

There are three main paths, each suited to a different situation.

Criteria	Off-the-shelf (SaaS)	Customised open source, e.g. Odoo	Custom-built
Time to go live	Fastest	Moderate	Slower, needs design and development
Fit with your process	You adapt to the system	Highly adaptable, but needs experts	Closest fit
Screen complexity	Often more features than you need	Depends on configuration	Only what you use
Long-term maintenance	Handled by the vendor	You manage versions and add-ons	Needs a developer to maintain it
Ownership of data and code	Depends on vendor terms	You own the installation	You own everything

How we usually decide:

If your production process is fairly standard and the team is willing to adapt, starting with off-the-shelf software gives the best value.
If you want a full feature set but have a few unusual requirements, look at Odoo or another open-source ERP and compare it with a custom build. Our article on custom software vs SaaS covers the trade-offs.
If your process is genuinely unique, such as recipes that change with raw material quality, grading agricultural produce, or make-to-order jobs where no two are alike, a custom system that starts small and grows is often the better fit.

Whichever you choose, always check the vendor’s current terms on user counts, data export and Thai-language support for documents such as tax invoices.

Examples from factories in Southern Thailand

Factories in the South have traits worth designing for:

Seafood processing plants. Raw material size and grade vary by lot, and yield changes with the season. The system must make it easy to record actual weight in and weight out.
Rubber and rubberwood plants. Material prices change daily, so cost per lot matters more than average cost.
Halal food or OTOP producers scaling up. Material traceability and supplier certificate records are essential.
Make-to-order plants such as furniture or parts makers need work orders tied to each customer order.

What they all share: the floor must be able to enter data as quickly as possible. A system that looks good but is slow to fill in will be abandoned within months.

What to prepare before talking to a developer or vendor

Have these ready and the conversation will be focused and quotes easier to compare:

An approximate list of products and materials, and how many BOMs you have
A rough diagram of your production steps
Documents you use now: work orders, issue slips, goods receipts, management reports
Number of users and their roles, and who needs to see what
Systems you need to connect to, such as accounting software, scales or barcode printers
Your top three problems

If you want the back office to talk to other systems later, ask about APIs from the start.

Southern Whale is a freelance team that helps factories analyse their processes, then designs and builds an ERP system starting with the modules you actually need and growing from there. If you’d like to talk through your shop-floor problems before deciding, message us on LINE OA.

Frequently asked questions about factory ERP

How is a factory ERP different from a general ERP?

A general ERP focuses on sales, purchasing, inventory and accounting. A factory ERP adds BOMs, work orders, material issues, scrap recording and production costing.

Does a small factory with a few dozen staff need ERP?

It doesn’t need a large system. But once stock stops matching, materials get ordered wrongly or you can’t see real costs, starting with a small system covering BOM, inventory and work orders helps a lot.

What is the difference between ERP and MRP?

MRP focuses on planning material requirements from the production plan and BOM. ERP covers the whole organisation. In practice, MRP is usually part of a factory ERP.

How long until it is actually in use?

It depends on data volume, how ready your BOMs are and how many modules you start with. Working in phases and beginning with one production line gets you live faster than switching everything on at once.

Can we keep our current accounting software?

In many cases, yes. The ERP can send sales and purchase data to the accounting software, or export files in a format it accepts. Check what your accounting software supports first.

Can our existing Excel data be moved into the new system?

Yes, but it needs cleaning first: merging duplicate codes, standardising units and checking each BOM. This is the most important step of going live.