ERP for industrial SMEs: where to start without making mistakes

When the leader of an industrial SME decides to launch an ERP project, the first mistake is almost always the same: trying to cover everything at once. Production, accounting, HR, purchasing, CRM — too wide a scope from the start is the primary cause of deployments that drag on or grind to a halt. The concrete answer: start with the module that is most blocking your operations — usually production and inventory management — stabilize that perimeter, then expand.

An industrial ERP is not an enhanced accounting package. It is a cross-functional system that touches work orders, bill-of-materials management, raw material inventory and production planning all at once. These specificities call for a different implementation approach than a CRM or an HR tool.

What an industrial ERP manages — and why it is different

A generic ERP covers functions common to most businesses: accounting, invoicing, contact management. An industrial ERP adds modules specific to manufacturing:

• Work orders (WO): tracking what has been launched, is in progress, has been delivered.
• Bills of materials and routings: which materials go into which product, in what order, on which machine.
• Real-time inventory: raw materials, work in progress, finished goods — with replenishment alerts.
• MRP/MRPII planning: calculating material and capacity requirements from the order book.
• Traceability and quality: batch numbers, in-process controls, non-conformities.

These modules are absent or very limited in ERP systems designed for service businesses or retail. If your SME manufactures, repairs or transforms physical products, these building blocks are the foundation of everything.

To compare the main categories of management software, our guide CRM, ERP or EOS: which solution to choose for your business lays out the decision framework.

Why ERP projects go off the rails — and how to avoid it

Implementing an ERP is one of the most demanding projects an SME can undertake. The Standish Group (CHAOS Report 2020) data is clear: only 31% of software projects are fully completed on time and within budget, 50% are delivered late, over budget or with a reduced scope, and 19% fail entirely. Large projects fare even worse.

In industrial ERP projects, the causes of derailment come up repeatedly:

• Too wide a scope from the start: integrating too many modules simultaneously dilutes attention, multiplies configuration and makes testing impossible to manage.
• Poor quality initial data: incomplete bills of materials, inaccurate stock counts, duplicate references — a botched data migration poisons the project for months.
• Unanticipated resistance from teams: line operators, warehouse staff, production managers are changing how they work. If nobody is involved in the project upstream, adoption fails.
• No internal project owner: an ERP is not a project you hand over entirely to an integrator. You need a dedicated internal contact who knows the business and validates the configuration.

For more on mistakes to avoid when choosing a management system, our article The most costly mistakes when choosing a software solution details the classic pitfalls.

The method: 5 steps to get started without mistakes

1. Map your workflows before choosing a software

Before opening any ERP catalogue, document your actual processes: how a work order is created, who validates it, how materials are consumed, where your bottleneck sits. This mapping often reveals that the bulk of value — and configuration complexity — is concentrated on a handful of key processes.

2. Define the functional scope of the go-live — and only that

List the modules that are essential at go-live, and those that can wait. For an industrial SME, inventory management + work orders + basic purchasing typically constitute a solid starting perimeter. Accounting can remain in the existing tool while production processes are stabilized in the ERP.

3. Choose between a market solution and custom development

This decision has a major impact on timelines, costs and future flexibility. Our article Custom software or off-the-shelf solution: how to decide offers a complete decision grid. In summary: if your manufacturing process resembles what most peers in your sector do, an off-the-shelf solution with tailored configuration is often the best value-for-time ratio. If your process has specificities not covered by market solutions, custom development or a significant extension may be warranted.

4. Clean your data before migration

This is the most underestimated step. A successful ERP migration requires clean data: complete and validated bills of materials, unified item references, counted and verified stock, deduplicated suppliers. Plan a data clean-up workstream running in parallel to configuration — it determines success more than the choice of software.

5. Involve business users from the requirements stage

Production managers, warehouse staff and planners know the real constraints that generic packages often ignore. Involving them in writing the requirements and testing configuration accelerates adoption and reduces rework after go-live. The Standish Group identifies user involvement as one of the three most decisive factors in software project success — alongside management support and a clear statement of requirements.

Reference table — which phase to start with

Phase	Modules to deploy	Complexity	Immediate benefit
Phase 1 — Operational core	Inventory, work orders, purchasing	High	Real-time visibility on production
Phase 2 — Planning	MRP, capacity management, auto-replenishment	Very high	Fewer stockouts and overstock situations
Phase 3 — Commerce & finance	CRM, invoicing, integrated accounting	Moderate	End-to-end data, fewer manual re-entries
Phase 4 — Quality & traceability	Quality controls, batches, non-conformities	Variable	Regulatory compliance, simplified recalls

This table is a guide, not an absolute: the sequence depends on your priorities. If customer invoicing is your priority, start with phase 3. If inventory shortages are disrupting production, start with phase 1.

Signs that your SME is ready for an ERP

If you are not yet certain you need an ERP, certain warning signals are characteristic. Our article 10 signs your business needs a business software solution lists the most telling indicators. For industrial SMEs, the most common are:

• Inventory poorly known, with time-consuming and inaccurate cycle counts.
• Work orders managed in Excel or a notebook, with regular re-entries.
• Material shortages that halt production without having been anticipated.
• Customer deadlines missed due to lack of visibility on the order book.
• Month-end closings that require significant manual reworking.

If you recognise three or more of these signals in your daily operations, the threshold has likely been reached. The article Why Excel always ends up becoming a problem illustrates the concrete limits of office tools for managing production.

Frequently asked questions (FAQ)

How long does an ERP deployment take in an industrial SME?

Duration depends on scope and upstream preparation. A deployment limited to the production core can be completed in a few months for a well-organised SME. A project covering all functions (production, commerce, finance, quality) often exceeds a year. The most decisive factor is not the software chosen — it is the quality of the starting data and the involvement of business teams.

Do you need to replace your accounting software at the same time as the ERP?

Not necessarily at go-live. Many industrial SMEs deploy the production/inventory module first, and keep their existing accounting tool in place while operational workflows stabilise in the ERP. Accounting integration can come in a later phase, once production processes are mastered.

Market ERP or custom ERP: how to choose for industry?

If your manufacturing process resembles what most peers in your sector do, an off-the-shelf solution with tailored configuration is often sufficient and less risky. If your process is genuinely specific — complex routings, non-standard traceability, very particular customer specifications — custom development or a significant extension may be warranted. Our guide Custom software or off-the-shelf solution details the decision grid.

How do you manage team resistance to an ERP change?

Resistance is normal and predictable. It is reduced by involving future users as early as possible — from the scoping phase, not just in training. Show them concretely what the new tool simplifies for them (fewer re-entries, fewer calls to check stock levels), and designate business champions in each team who become the internal relays for the project.

Can you deploy an industrial ERP without an external consultant?

Theoretically possible with the most accessible packages, but rare in practice for industrial functions. The complexity of configuring bills of materials, routings and MRP often justifies bringing in an integrator specialised in your sector. The risk to avoid: a generalist integrator who does not know the specificities of your industry.