Manufacturing ERP cost: what you pay and where it goes

Manufacturing ERP cost on SAP runs from $80,000 to $500,000 for a small manufacturer and $500,000 to $2 million for a mid-sized one. Large manufacturers should plan for $2 million to $10 million or more, and global groups $10 million to $50 million or more.

Short answer: the software is not the big number. Partner services take 35 to 50 percent of the total, and in a plant the rest goes on master data, shop-floor integration, testing and finance design.

I have implemented ERP in plastics, steel and defence manufacturing. In any plant, the licence quote is the easy part to read; the harder costs sit around it.

If you have not chosen a system yet, start with my comparison of the best ERP for manufacturing. This article is about the bill.

These are the total programme ranges I use for SAP. They cover subscription or licences, partner services, data, testing, training and hypercare.

The table adds what typically pushes a manufacturer up its band:

Company size	Total cost (USD)	Typical SAP route	What pushes a manufacturer up the range
Small (under 200 staff)	$80K to $500K	SAP Business One, or S/4HANA Cloud Public Edition	BOM and routing cleanup, a first MES or scanner interface
Mid-market (200 to 1,000)	$500K to $2M	S/4HANA under GROW with SAP, or Private Edition	Several plants, batch traceability, integration to the shop floor
Large (1,000 to 10,000)	$2M to $10M+	S/4HANA Private Edition under RISE with SAP	Multi-plant MES rollout, product costing design, test scope
Global group (10,000+)	$10M to $50M+	S/4HANA Private Edition or on-premise	Many countries and plants, regulation, rollout waves

Add 10 to 20 percent contingency on top of whichever band you land in. Hold it on your side, not inside the partner's price.

Time is cost too. A GROW with SAP programme takes about 6 to 9 months and a RISE with SAP programme 9 to 18 months. Every extra month carries the partner team, your own people on the project and, often, the old system still running.

Small manufacturers and SAP Business One

For a small manufacturer, SAP Business One costs $25,000 to $150,000 or more and goes live in 90 to 150 days. It is a real manufacturing option, not only an accounting package.

SAP's own training material shows production bills of materials, production orders with manual or backflush issue, and an MRP run that recommends production and purchase orders (SAP Learning, Business One production). Check that those functions match how your plant actually runs before you compare price.

The general SAP cost picture, day rates and the budget formula are in my guide to how much SAP implementation costs. The rest of this article is what is different when the company makes things.

On paper the split looks like any ERP programme. Partner services are the largest line, then subscription or licences, then development, data, training, hosting and hypercare.

In a plant, the effort concentrates in four places. Most of it never appears as a separate line in a partner quote.

30-40%

of programme effort goes on data migration, much of it your own people's time

Source: Noel D'Costa, confirmed working range

Master data: BOMs, routings and work centres

In my experience data migration takes 30 to 40 percent of the effort. In manufacturing, that means bills of materials, routings or master recipes, work centres, material masters and open production orders.

A partner quote usually covers the load tools and the technical team. The cleansing, the engineering sign-off on every BOM and the plant-by-plant validation fall on your engineers, planners and controllers. Budget their time, or backfill their day jobs.

Discrete, process and mixed-mode plants carry different master data. How a discrete plant gets set up depends on what that client needs, with no single template, so the data effort cannot come from a template either. My guide to SAP discrete vs process manufacturing explains the differences.

Testing across planning, production and costing

Testing takes about 35 percent of the effort. A manufacturer has more chains to test than most businesses: plan to produce, procure to pay, order to cash and the month-end costing run.

Each chain crosses production planning, materials, quality and controlling. Test them together, with real BOMs and routings, or the problems surface on the shop floor after go-live.

Shop-floor integration

This is the line that most often sits outside the original budget. It has its own section below.

Finance design

This is the cost that decides whether the rest is wasted. It also has its own section below.

An ERP plans and costs production. An MES runs it on the line and reports back, and the interface between them is a project in its own right.

The MES and shop-floor systems I have worked with are SAP Digital Manufacturing, Siemens Opcenter and Kinexon. SAP Digital Manufacturing and Siemens Opcenter sit on top of the ERP. Each one brings its own licence, its own configuration and its own interface to build and test.

What each one needs from the ERP side is documented by the vendors:

1. SAP Digital Manufacturing. SAP's integration guide describes master data, BOMs and production orders flowing from S/4HANA or SAP ERP into Digital Manufacturing, with confirmations such as yield and scrap sent back (SAP Help, integration with SAP S/4HANA or SAP ERP).
2. Siemens Opcenter. Siemens describes the ERP sending production demand, master data and BOMs down, and the MES returning order status, consumption, scrap and completions (Siemens Opcenter blog).
3. Kinexon. Kinexon sells real-time location and sensor tracking for assets, tools and orders, and describes its software as connecting that data to ERP, MES and warehouse systems (Kinexon).

The budget questions are the same for all three. Use this table to make sure each one has an owner and a number before the statement of work is signed.

Cost line	What it covers	Where it usually hides
MES or tracking licence	Subscription or licence for the shop-floor system	A separate contract, often signed by operations, not by the ERP programme
Interface build	Order, master data and confirmation flows between ERP and MES	Listed as "integration" in the partner quote with no count of flows
Master data alignment	Same material, work centre and routing in both systems	Assumed to come free with the ERP data migration
Integrated testing	Orders released, executed, confirmed and costed across both systems	Tested separately by two vendors
Plant connectivity	Machines, scanners and network on the shop floor	Plant IT budget, discovered late

Agree which system owns each record, such as confirmations, scrap and batch genealogy, before either is configured. My guide to ERP and MES in manufacturing covers who owns what.

The most common reason manufacturing ERP projects fail, in my experience, is that the design is not agreed in its totality, especially in finance. Everything else can be on track while this one gap grows underneath it.

In a plant, finance design means product costing, work in progress, variances, inventory valuation and how production confirmations reach the ledger. Each of those depends on decisions taken in production planning and materials. If finance signs off its part separately, the pieces do not meet.

The cost shows up late. A design gap found in integration testing means rework across modules, more test cycles and often a moved go-live, all at full team cost.

Defence manufacturing adds its own layer. There the areas that mattered most were contract costing and project systems, using SAP Project System (PS), so the finance design has to cover how cost flows to each contract. My guide to ERP for defence manufacturing goes into that.

Sign the finance design off as one piece with production and materials, before build starts. It is the cheapest point in the programme to find the gap.

Across the 21 SAP programmes I have led or rescued, the biggest mistake I see is not planning properly at the start. Budgets get hit in the Explore phase, as the list of reports, interfaces, conversions, enhancements, forms and workflows (WRICEF) grows.

In manufacturing, these are the costs most often missing from the first quote:

1. Shop-floor interfaces. Scanners, label printers, weighbridges, test rigs and machine connections each add an interface to build and test.
2. Cutover of in-flight production. Open production orders, partly consumed materials and work in progress have to be closed, moved or valued at cutover.
3. Production downtime around go-live. Plan how the plant runs while the systems switch over, and what it costs if output drops for a few days.
4. Shift-based training. Operators on three shifts cannot all attend one classroom session. Price training per shift and per role.
5. Extra test cycles. A failed integration test across ERP and MES means another full cycle with both vendors in the room.
6. Hypercare on every shift. Problems on the night shift need support on the night shift.
7. Old system running in parallel. If go-live slips, the legacy ERP keeps its maintenance and support costs.

None of these is unusual. They are simply easy to leave out when the quote is built from module scope alone.

My piece on why SAP projects go over budget covers the Explore-phase pattern in detail.

My rule is SAP for manufacturing, public sector and regulated, operations-heavy organisations, and Oracle for finance-led organisations and professional services. Cost is part of why size matters in that choice.

For a mid-sized manufacturer of about 200 to 1,000 staff, I recommend Epicor Kinetic. Outside SAP, the other systems I would consider for manufacturers are IFS and Infor.

I only quote figures for SAP in this article. For any other vendor, ask for a written price on your own scope, and apply the same tests: who pays for data, testing, shop-floor integration and finance design.

Build the budget from your plant outwards, not from the licence inwards. This order keeps the hidden costs visible:

1. Count your master data. Materials, BOMs, routings or recipes and work centres, per plant, with a named owner for each.
2. List every shop-floor system and interface. MES, tracking, scanners, machines and quality instruments, with who owns each record.
3. Agree the finance design as one piece. Product costing, work in progress and variances signed off with production and materials.
4. Size data at 30 to 40 percent and testing at about 35 percent of effort. Include your own people's time, not only the partner's.
5. Pick the band and the timeline. Use the size ranges above and the GROW or RISE timeline that fits.
6. Add 10 to 20 percent contingency, held on your side.

The concrete next step: pull a count of active BOMs, routings and work centres for each plant this month, and note who owns each list. It tells you more about your cost than any vendor demo.

If you want an independent view on a manufacturing ERP budget or a partner proposal, I help organisations with this. You can contact me here.

How much does ERP cost for a manufacturing company?

On SAP, plan for $80,000 to $500,000 for a small manufacturer under 200 staff and $500,000 to $2 million for 200 to 1,000 staff. Large manufacturers should plan for $2 million to $10 million or more, and global groups $10 million to $50 million or more. Add 10 to 20 percent contingency on top.

How much does SAP Business One cost for a small manufacturer?

Plan for $25,000 to $150,000 or more, with go-live in 90 to 150 days. Business One covers production bills of materials, production orders and MRP, so check those against how your plant runs before you compare price.

What are the hidden costs of a manufacturing ERP implementation?

Shop-floor interfaces, cutover of in-flight production, downtime around go-live, shift-based training, extra integrated test cycles and hypercare on every shift. Your own people's time on data cleansing and testing is the largest hidden cost, because it rarely appears in a partner quote.

Does an MES add to the cost of a manufacturing ERP?

Yes. An MES such as SAP Digital Manufacturing or Siemens Opcenter brings its own licence, configuration, interfaces and testing. Budget it as its own line, and agree which system owns confirmations, scrap and genealogy before either is configured.

How long does a manufacturing ERP implementation take?

On SAP, a GROW with SAP programme takes about 6 to 9 months and a RISE with SAP programme 9 to 18 months. SAP Business One goes live in 90 to 150 days. Several plants, an MES rollout or heavy data migration push you toward the long end.

Why do manufacturing ERP projects go over budget?

The most common reason they fail is a design that is not agreed in its totality, especially in finance. Budgets also get hit in the Explore phase as reports, interfaces and enhancements grow. Agree the finance design as one piece with production and materials, and write the scope yourself before a partner prices it.