From Excel to ERP: what small manufacturers need to know

Every small manufacturer has the same story. It starts with Excel. One file for orders, another for inventory, another for production planning. It works — until it doesn't.

At some point, the spreadsheets start causing more problems than they solve. Data is entered twice, in slightly different formats. Someone updates the wrong version. A customer order gets missed because it was in an email, not the spreadsheet. The production planner can't see what's in stock without calling the warehouse.

This article explains when that limit is actually reached, what an ERP transition looks like for a company with 10 to 50 employees, and what the common mistakes are.

When is Excel no longer enough?

The honest answer is: earlier than most manufacturers think. The symptoms are usually present for a year or two before anyone treats them as a structural problem rather than a temporary inconvenience. Some specific signals that the Excel limit has been reached:

• More than one person needs to access the same file at the same time — and conflicts arise.
• You have more than 3–4 spreadsheets that need to stay in sync with each other.
• You can't tell in real time what's in stock without manually checking.
• Orders are sometimes missed or delayed because information is in email, not in the system.
• You can't quickly tell which orders are profitable and which aren't.
• Month-end reporting takes more than half a day because data has to be assembled from multiple sources.
• A new team member takes months to understand the file system well enough to work independently.

If three or more of these are true in your operation, the cost of staying on Excel is probably already higher than the cost of moving to an ERP.

What does "ERP" actually mean for a small manufacturer?

ERP stands for Enterprise Resource Planning — a term that immediately makes small manufacturers think it's not for them. In its original enterprise form, it isn't: SAP implementations at large manufacturers cost millions and take years. But the underlying problem an ERP solves is not an enterprise problem. It's about having one place where orders, stock, production, purchasing, and invoicing all live and stay in sync.

For a manufacturing company with 10 to 50 employees, the requirements are more specific:

• Order intake and production planning in one place
• Purchase orders linked to what's needed for production
• Inventory that updates when goods arrive or are consumed
• Invoicing that flows from completed orders
• Dashboards that show what's on order, what's in stock, and what the margin is

This doesn't require a SAP implementation. Several Dutch-market ERP systems are built for exactly this scale — Exact Online and AFAS are the most common. There are also purpose-built solutions for manufacturers at this scale that include production-specific functionality like BOM management and work order tracking.

The transition: what does it actually involve?

The biggest fear small manufacturers have about ERP implementation is that it will be a year-long disruption. That fear is justified if you're implementing a large enterprise ERP with a large implementation partner. It's not justified if the approach is right.

The key factors that determine how long and painful a transition is:

Data quality going in
The hardest part of most ERP migrations is cleaning up the existing data — customer lists with duplicates, product codes that aren't consistent, historical orders in five different formats. Before you start, a realistic audit of what data you have and what state it's in will tell you how much migration work you're facing.

Process documentation before implementation
An ERP implements your processes. If your processes aren't documented — if different people handle the same situation differently — the ERP will embed that inconsistency. Spend time documenting exactly how orders are processed, how purchasing decisions are made, how invoicing works. This is the work that determines whether the ERP actually helps or just moves the chaos to a new system.

Phased go-live
The most common reason ERP implementations fail is trying to go live with everything at once. For a small manufacturer, a better approach is: start with order intake and invoicing (the highest-value, highest-pain processes), get stable on those, then add production planning and inventory. Two months of a clean order-to-invoice cycle is more valuable than a year trying to perfect a full implementation.

The common mistakes

1. Choosing the ERP first, then fitting processes to it
The ERP should serve your processes, not the other way around. Start from your specific requirements — what do you need to track, what decisions does the system need to support — and evaluate systems against those. Generic demos of feature lists don't tell you whether the system will work for your specific situation.

2. Underestimating the change management side
The technology is not the hard part. Getting your team to use it consistently — to trust the system instead of their old spreadsheets — is. A phased rollout with clear training and early wins matters more than the specific ERP you choose.

3. Not including AI document processing from the start
An ERP solves the data-in-one-place problem. It doesn't solve the data-entry problem — orders still need to get into the system, invoices still need to be checked, purchase orders still need to be created. If you don't automate the document layer around the ERP at the same time, you've moved from "data scattered across spreadsheets" to "data in one place, but still typed in by hand." That's a partial win.

What does it cost?

The range is wide. A full enterprise ERP implementation is not relevant here. For a company of 10–50 employees, the relevant cost components are:

• Software licence: €100–500/maand afhankelijk van het systeem en het aantal gebruikers.
• Implementation: the biggest variable. A standard Exact Online or AFAS implementation with a certified partner runs €5,000–15,000 for a company at this scale, depending on complexity and data migration work.
• Document automation layer: if you add agentic AI automation for order intake, invoice verification, and purchase order processing, add this as a separate fixed-price build — typically 3 weeks.

The break-even is usually 6–12 months. A company that reduces manual admin by 2 hours per day at an average labour cost of €35/hour recovers €17,000/year in productive capacity. Implementation costs are typically paid back within the first year.

The right starting point

If you're still running on email, Excel, and paper — and you're at the point where that's clearly limiting growth — the right first step is not to pick an ERP. It's to map your processes clearly enough to know exactly what you need the system to do.

A free Process Scan does exactly that: it maps where your current operation is losing time and capacity, calculates what fixing it is worth, and recommends the right approach — whether that's an ERP, automation, or a combination of both.