For many manufacturers, the problem isn't that they don't have software.
It's that their systems don't work together.
Sales has its forecast. Production has its plan. Purchasing has another view of demand. Stock figures aren't always trusted. Finance often sees the true manufacturing cost after the event.
Somewhere between them are spreadsheets, manual workarounds and people spending time reconciling information that should already agree.
The result isn't simply inefficient administration.
It can mean buying materials too early or too late. Carrying more stock than necessary. Rescheduling production at short notice. Promising delivery dates without a reliable view of capacity. Struggling to understand true product margins. Or spending management meetings debating whose numbers are correct.
This is the problem manufacturing ERP is supposed to solve.
But choosing an ERP system is only part of the answer.
Manufacturers also need to understand what should be integrated, which processes genuinely need changing, what data the system will depend on, how people will use it and what measurable improvement should look like after implementation.
This guide looks at manufacturing ERP from that practical perspective.
Not simply:
What features does ERP have?
But:
What should a good ERP environment actually help a manufacturer do better?
0110 signs your manufacturing systems are holding you back
ERP problems don't always arrive as an obvious system failure.
Often, they appear gradually as the organisation grows.
One spreadsheet becomes five. A manual workaround becomes a normal business process. A report that used to take an hour takes a day. Another person is recruited because existing staff cannot keep up with the administration.
Individually, those issues may appear manageable.
Together, they can indicate that the way information moves through the business is beginning to restrict performance.
Sign 1Production planning depends heavily on spreadsheets
Spreadsheets are useful tools.
The problem comes when a spreadsheet effectively becomes the production planning system.
If planners are continually exporting ERP data, manipulating it manually and then maintaining a separate production plan, the business can end up with two versions of operational reality.
Changes made in one may not immediately appear in the other.
Sign 2People don't fully trust the stock figure
A system can show 500 units in stock.
That doesn't necessarily mean 500 units are available.
Some may already be committed to customers, allocated to production, under inspection, sitting at another location or physically missing.
If planners continually walk to the warehouse or telephone colleagues to check what is really there, the stock figure isn't doing its job.
Sign 3Purchasing finds out about production changes too late
Demand changes.
Customers increase orders. Delivery dates move. Production priorities change.
If purchasing only becomes aware after planners send an email or update a spreadsheet, procurement is reacting rather than working from the same demand picture.
That can lead to shortages, expediting costs or unnecessary inventory.
Sign 4Information is manually rekeyed between systems
An order starts in one system.
Somebody enters it into another.
Production information is copied somewhere else.
Finance receives another version.
Every manual hand-off creates delay and another opportunity for error.
Sign 5Actual manufacturing cost is difficult to establish
Many businesses know their expected product cost.
Fewer can easily compare that with what actually happened.
Materials changed. Labour took longer. Scrap increased. An outside process cost more than expected.
If those variances aren't visible, product margin can look healthier than it really is.
Sign 6BOM changes create downstream problems
The Bill of Materials sits at the centre of many manufacturing processes.
If different teams are using different versions, or changes aren't controlled properly, the impact can spread quickly into purchasing, planning, production and costing.
Sign 7Management reporting depends on spreadsheet consolidation
A director asks a straightforward question:
“How are we performing?”
And several people spend the next day collecting information from different systems.
That is a reporting problem, but it is often also an integration and data-structure problem.
Sign 8Different departments have different versions of the truth
Sales sees one delivery date.
Production sees another.
Finance sees a different margin.
Purchasing has different demand.
When each department operates from its own information, meetings become exercises in reconciliation rather than decision-making.
Sign 9Customer commitments aren't connected to genuine capacity
Taking an order is easy.
Knowing whether the business can manufacture it when promised is harder.
If sales commitments are disconnected from inventory, material availability, production capacity and existing demand, promised dates can become optimistic guesses.
Sign 10Growth means adding people rather than improving processes
Growth will often require more people.
But if every increase in transaction volume creates an equivalent increase in administration, the underlying process may not be scalable.
ERP should help a business handle more complexity without simply creating more manual work.
02What manufacturing ERP actually does
ERP stands for Enterprise Resource Planning.
That definition doesn't tell a manufacturer very much.
In practical terms, manufacturing ERP should connect the information required to plan, buy, make, store, sell and account for products.
The important word is connect.
A manufacturer can have excellent accounting software, a warehouse system, production planning tools, CRM and spreadsheets.
Individually, each may do its job.
The problems start when people have to continually translate information between them.
A well-designed ERP environment should help connect areas such as:
- customer demand;
- sales orders;
- forecasting;
- inventory;
- purchasing;
- Bills of Materials;
- routings;
- material requirements;
- production planning;
- work orders;
- shop-floor activity;
- quality;
- warehousing;
- fulfilment;
- costing;
- invoicing;
- financial reporting.
The real value isn't that every department has software.
It is that an operational event can update the rest of the business without people continually translating information between systems.
03How ERP connects your manufacturing operation
Consider a simplified manufacturing information flow.
- Customer demand
- Sales order or forecast
- Demand planning
- Material requirements
- Purchasing and available inventory
- Bill of Materials and routing
- Capacity and production planning
- Work orders
- Shop-floor activity
- Quality and traceability
- Finished goods
- Warehouse and dispatch
- Invoice
- Actual cost and margin
Each stage affects another.
- If customer demand changes, material requirements may change.
- If a supplier delays a component, production may need to be rescheduled.
- If production consumes more material than expected, actual cost changes.
- If an order is delayed, customer service and sales need to know.
- If scrap rises, operations need to understand the cause while finance needs to understand the commercial impact.
The objective isn't simply to record all of these events.
It is to make their relationships visible.
That is where ERP starts becoming operationally valuable.
04ERP vs MRP vs MES vs WMS vs APS vs PLM
Manufacturing technology comes with an impressive collection of acronyms.
Understanding the basic distinction helps because these systems frequently overlap.
| System | Main job | Typical question it answers |
|---|---|---|
| ERP | Connect business operations and financials | What is happening across the business? |
| MRP | Calculate material requirements from demand | What materials do we need, and when? |
| MES | Capture and manage production execution | What is actually happening on the shop floor? |
| WMS | Manage warehouse activity | Where is inventory and how should it move? |
| APS | Support advanced planning and scheduling | What should we make, on which resource, and when? |
| PLM | Manage product information and lifecycle | What exactly are we designing or manufacturing? |
The boundaries aren't always neat.
ERP platforms may contain MRP, warehouse, planning or manufacturing functionality. Specialist applications may then extend those capabilities where operational requirements become more sophisticated.
The right architecture therefore isn't necessarily:
“Put everything in one system.”
Nor is it:
“Buy a specialist application for everything.”
The better question is:
Which information needs to be controlled where, and how should those systems work together?
05What type of manufacturer are you?
Manufacturing businesses don't all operate in the same way.
That matters when evaluating ERP.
A system that works extremely well for a high-volume make-to-stock manufacturer may not suit a highly engineered make-to-order business in the same way.
Understanding your manufacturing model should come before comparing product demonstrations.
Make-to-stock
Operational reality: Products are manufactured in anticipation of future customer demand.
What becomes difficult? The business has to balance availability against excess inventory. Produce too little and customers wait. Produce too much and cash sits in stock.
ERP needs to help with:
- forecasting;
- demand planning;
- material requirements;
- inventory optimisation;
- production planning;
- warehouse management;
- replenishment;
- product costing.
Make-to-order
Operational reality: Production begins in response to actual customer demand.
What becomes difficult? Sales needs to quote realistic lead times while operations needs a dependable view of materials and capacity.
ERP needs to help with:
- sales-order-driven demand;
- material planning;
- capacity visibility;
- production scheduling;
- work orders;
- job or production costing;
- customer delivery visibility.
Engineer-to-order
Operational reality: Engineering forms a significant part of fulfilling the customer requirement. Products may be designed or substantially adapted after the order is received.
What becomes difficult? Commercial, engineering, procurement and production information all need to remain aligned while requirements evolve.
ERP needs to help with:
- project control;
- revision management;
- flexible BOMs;
- engineering integration;
- purchasing;
- long lead-time materials;
- project or job costing;
- change control.
Configure-to-order
Operational reality: Customers choose from predefined options or combinations that create a finished configuration.
What becomes difficult? The organisation must translate a commercial configuration into the correct price, components and manufacturing requirement.
ERP needs to help with:
- product configuration;
- pricing;
- rules-based options;
- dynamic BOMs;
- manufacturing instructions;
- inventory;
- order automation.
Process manufacturing
Operational reality: Production is often based on formulas, recipes, batches or continuous processes rather than assembling discrete components.
What becomes difficult? Yield, batch consistency, quality, traceability and expiry or shelf-life requirements may become critical.
ERP needs to help with:
- formulas or recipes;
- batch control;
- lot traceability;
- quality;
- yield;
- expiry dates;
- material consumption;
- costing.
Many organisations also combine manufacturing approaches.
The important point is not to force your operation into a software vendor's preferred terminology.
Document how your business actually works first.
06The 12 manufacturing ERP capabilities that actually matter
Feature lists are easy to compare.
Operational capability is harder.
Rather than asking whether software has a feature, ask whether the feature can support the way your organisation needs to work.
Capability 1Bill of Materials management
Don't simply ask:
“Does it support BOMs?”
Ask:
- Can it support the complexity of our products?
- Can we manage revisions appropriately?
- Can alternative components be controlled?
- Can engineering and production work from consistent information?
- What happens downstream when a BOM changes?
A BOM is not merely a list of components.
It can influence purchasing, planning, work orders, stock and product cost.
Capability 2Material requirements planning
The important question isn't:
“Does it have MRP?”
It is:
“Can the planning output become something our production and purchasing teams genuinely trust?”
That depends on the quality of information behind it.
Demand. Lead times. Stock. Existing purchase orders. Production orders. Safety stock. BOMs.
If those inputs are wrong, sophisticated planning logic can still produce an unusable answer.
Capability 3Inventory visibility
Planners need more than a total stock figure.
They may need to understand:
- what is physically on hand;
- what is available;
- what is committed;
- what has been allocated to production;
- what is under inspection;
- what is expected from suppliers;
- what is held at another site;
- what is becoming obsolete.
Good inventory information should help people make decisions, not simply tell them how many units were recorded at some point in the past.
Capability 4Routings
A BOM answers:
What do we need?
A routing helps answer:
How do we make it?
Depending on the manufacturing environment, this may include operations, work centres, labour, machine resources, setup times and run times.
If routing information is central to planning and costing, assess how well the ERP reflects the real process.
Capability 5Capacity and scheduling
A materials plan isn't the same as a production plan.
You may have every component required but insufficient machine or labour capacity to complete the work when promised.
Manufacturers should therefore understand how the proposed environment deals with:
- work centres;
- available capacity;
- constraints;
- sequencing;
- setup;
- competing demand;
- production priorities.
For some organisations, native ERP functionality is sufficient.
Others may require specialist planning or APS capabilities.
Capability 6Work orders and production control
The system needs to translate planning into executable production activity.
Consider how operators and planners will interact with:
- work orders;
- material issues;
- component consumption;
- operation completion;
- finished quantities;
- scrap;
- labour or machine time;
- variance.
Do not evaluate this solely from the perspective of someone sitting in an office.
Look at how information will actually be captured where the work happens.
Capability 7Traceability
For some manufacturers, traceability is desirable.
For others, it is fundamental.
Requirements can include the ability to understand:
- which materials went into a finished product;
- which supplier lot was used;
- where affected finished goods were shipped;
- which customers received them;
- what happened during production.
The required depth will depend on industry, product and regulation.
Capability 8Quality management
Quality shouldn't always be treated as a separate administrative exercise.
Consider where inspection, non-conformance and quality information needs to intersect with:
- receiving;
- production;
- inventory;
- supplier performance;
- customer returns.
The important question is whether quality events can influence the operational process appropriately.
Capability 9Manufacturing costing
Manufacturing costing becomes especially valuable when it moves beyond:
“What did we think this product would cost?”
towards:
“What did it actually cost, and why was it different?”
Useful analysis may include:
- standard versus actual material cost;
- labour variance;
- overhead;
- scrap;
- outside processing;
- purchase-price variance;
- production variance.
This is where manufacturing and finance need to speak the same language.
Capability 10Warehouse and fulfilment
Manufacturing doesn't stop when production finishes.
Finished goods need to be stored, picked and dispatched.
Raw materials need to arrive in the right location.
Depending on complexity, manufacturers may need capabilities around:
- bins;
- barcode scanning;
- picking;
- put-away;
- replenishment;
- multiple locations;
- mobile warehouse processes.
Capability 11Finance
One of ERP's potential advantages is connecting operational activity to its financial consequence.
Manufacturing transactions don't happen in isolation.
- Purchasing affects liabilities and inventory.
- Production changes the value and location of stock.
- Shipments become revenue and cost of goods sold.
- Variances affect margin.
Manufacturing and finance therefore shouldn't need to build separate versions of what happened.
Capability 12Reporting and analytics
Avoid evaluating reporting by counting dashboards.
Ask what decisions management needs to make.
Can you answer questions such as:
- Which orders are at risk?
- Which materials are creating shortages?
- Where is excess stock building up?
- Which products are generating margin?
- What is causing production variance?
- Are customer delivery commitments being met?
- Where is working capital tied up?
A dashboard is useful only if the information underneath it can be trusted.
07How to evaluate manufacturing ERP software
ERP selection can easily turn into a feature contest.
Vendor A ticks 87 boxes.
Vendor B ticks 91.
Vendor B wins.
The danger is obvious: not every requirement matters equally.
A better approach is to evaluate the software against real operating scenarios.
Instead of asking:
Does it support inventory?
Ask:
Can planners distinguish stock on hand from stock committed to customers, allocated to production, under inspection or expected from suppliers?
Instead of:
Does it support reporting?
Ask:
Can the production manager and finance director look at the same underlying transaction and understand its operational and financial impact?
Instead of:
Does it support multiple locations?
Ask:
If one site is short of a component and another has available stock, how does the system help us see and manage that?
Instead of:
Does it have workflow?
Ask:
Can the approval and exception processes that genuinely matter be controlled without creating unnecessary bureaucracy?
A useful evaluation framework might include:
| Area | Question to ask |
|---|---|
| Production | Can it handle the way we actually manufacture? |
| MRP | Will planners and buyers be able to trust the output? |
| BOM | Can we control the product structures and revisions we need? |
| Scheduling | Can we understand material and capacity constraints? |
| Inventory | Can we distinguish what exists from what is genuinely available? |
| Traceability | Can we trace materials through production where required? |
| Quality | Can quality events be integrated into relevant processes? |
| Costing | Can we understand standard versus actual manufacturing cost? |
| Finance | Do operational and financial information remain connected? |
| Integration | Can the ERP exchange information reliably with other critical systems? |
| Reporting | Can people answer operational questions without constant spreadsheet manipulation? |
| Scalability | Can the environment support future sites, entities and complexity? |
Most importantly:
Demonstrations should follow your scenarios.
Do not simply watch the vendor's favourite demo.
08Seven reasons manufacturing ERP projects underperform
Choosing suitable software matters.
But ERP performance also depends on what the business does around the software.
1. Automating bad processes
A new system does not automatically create a good process.
If the old process contains unnecessary approvals, duplicate entry or historical workarounds, recreating it digitally can simply make the inefficiency more permanent.
Implementation provides an opportunity to ask:
Why do we do this?
Not merely:
How do we put this into the new system?
2. Poor master data
BOMs. Routings. Lead times. Suppliers. Items. Units of measure. Locations. Customer information.
A manufacturing system depends heavily on master data.
If the data is unreliable, the process built on top of it becomes unreliable too.
Data preparation should therefore begin far earlier than many organisations expect.
3. Stock isn't accurate
MRP cannot manufacture reality from inaccurate stock records.
If the system believes materials exist when they don't, recommendations will reflect that assumption.
If materials physically exist but haven't been recorded correctly, unnecessary supply may be created.
Improving stock accuracy can therefore be as important as changing planning software.
4. Everything gets customised
ERP replacement often begins with dissatisfaction with an old system.
Yet organisations sometimes attempt to reproduce every historical behaviour inside the new one.
That can create excessive customisation and preserve processes that should have been challenged.
Customisation isn't inherently wrong.
The question is whether each change creates enough business value to justify its complexity.
5. ERP becomes an IT project
Technology matters.
But manufacturing ERP affects sales, purchasing, production, warehousing, finance and management.
Operations must therefore own operational decisions.
IT can support the project.
It shouldn't be expected to decide how the factory should run.
6. Users discover the system at go-live
Training isn't simply teaching people which button to press.
People need to understand:
- how their role changes;
- why certain information matters;
- what happens downstream when they enter something incorrectly;
- how the new process improves the organisation.
If users see the system properly for the first time shortly before launch, adoption problems should not be surprising.
7. Nobody agreed what success meant
“Go live with ERP” is a project milestone.
It isn't a business objective.
Better goals might include:
- improve stock accuracy;
- reduce manual order entry;
- shorten production-planning time;
- improve on-time delivery;
- increase visibility of manufacturing cost;
- reduce spreadsheet reporting;
- decrease excess inventory.
ERP success should ultimately be judged by what changes in the business.
09What should good manufacturing ERP tell management?
ERP isn't only about processing transactions.
It should improve management information.
The exact KPIs will differ by manufacturer, but the questions behind them are broadly useful.
Can we deliver what we've promised?
Potential measures:
- on-time delivery;
- OTIF;
- schedule attainment;
- order lead time;
- production-plan adherence.
Are we holding too much inventory?
Potential measures:
- inventory turns;
- days inventory;
- obsolete stock;
- slow-moving inventory;
- stock accuracy.
Is production performing as expected?
Potential measures:
- throughput;
- cycle time;
- downtime;
- schedule performance;
- OEE where appropriate.
Are we making money on what we manufacture?
Potential measures:
- product margin;
- job margin;
- standard versus actual cost;
- production variance;
- material variance.
Are quality problems costing us?
Potential measures:
- scrap;
- rework;
- first-pass yield;
- returns;
- cost of poor quality.
The goal isn't to produce more KPIs.
It is to give managers better answers.
10Cloud vs on-premise manufacturing ERP
The cloud versus on-premise question is sometimes presented as though one answer is universally correct.
It isn't.
A cloud ERP environment can reduce the amount of infrastructure an organisation has to manage itself and can make access across sites easier.
It may also simplify aspects of upgrading and platform maintenance.
But manufacturers should still examine practical requirements such as:
- internet resilience;
- integrations;
- shop-floor connectivity;
- latency-sensitive applications;
- specialist equipment;
- data requirements;
- security;
- regulatory obligations;
- upgrade management;
- total cost over time.
The decision shouldn't be ideological.
It should be based on operational requirements, risk and long-term maintainability.
11Which systems should ERP integrate with?
ERP doesn't need to perform every possible business function itself.
Manufacturers may operate specialist systems for:
- CRM;
- eCommerce;
- CAD;
- PLM;
- MES;
- WMS;
- EDI;
- transport management;
- quality;
- maintenance;
- business intelligence;
- payroll;
- specialist industry applications.
The important issue is not simply whether an integration is technically possible.
Ask:
Who owns the data?
Which system is the source of truth?
How quickly does information need to move?
What happens if the integration fails?
How will errors be identified and corrected?
Who is responsible for maintaining it?
An integration should remove manual effort.
It should not create a new invisible process that nobody understands.
12Before you replace your ERP, establish what is actually broken
Not every ERP problem requires an ERP replacement.
This is worth establishing before beginning a major selection exercise.
There are broadly four possibilities.
Replace
The current platform genuinely cannot support the organisation's requirements.
Perhaps it no longer fits the manufacturing model, cannot scale, creates unacceptable technical risk or prevents necessary integration.
Replacement may be justified.
Optimise
The system may contain capabilities the organisation isn't using effectively.
Configuration has drifted. Processes have deteriorated. Reports aren't useful. Users rely on workarounds.
In that situation, improving the existing environment may create more value than replacing it.
Integrate
The ERP itself may be acceptable, while important information remains trapped elsewhere.
Better integration could remove manual entry and improve visibility without replacing the core platform.
Automate
The underlying process works but contains unnecessary manual steps.
Workflow, integration or targeted automation may solve the problem.
The right answer is not always:
“Buy another ERP.”
Understanding the actual constraint should come first.
13What should you fix before talking to ERP vendors?
ERP selection improves considerably when manufacturers know what they are asking vendors to solve.
Before demonstrations begin, document the current operation.
That might include:
- manufacturing models;
- BOM structures;
- routings;
- item and master-data quality;
- warehouses and locations;
- current stock accuracy;
- current planning process;
- existing integrations;
- critical spreadsheets;
- reporting requirements;
- approval processes;
- quality requirements;
- operational pain points;
- regulatory obligations;
- growth plans;
- target KPIs.
Also identify the spreadsheets people cannot live without.
They frequently reveal a requirement that the current systems are failing to meet.
Then separate requirements into categories.
Must have
Without this capability the solution cannot support the business.
Should have
The capability creates meaningful value but may have alternatives.
Could have
Useful, but not at the expense of more important requirements.
A better ERP selection process starts with understanding the operation, not comparing software demonstrations.
14AI won't fix poor manufacturing data
AI is becoming part of the ERP conversation.
That can be useful.
It can also distract from more basic issues.
Manufacturers are increasingly being offered AI-assisted forecasting, analysis, automation and decision support.
Potential applications include:
- identifying planning exceptions;
- analysing demand patterns;
- detecting unusual transactions;
- highlighting cost or margin anomalies;
- summarising operational information;
- helping users interrogate business data;
- assisting forecasting;
- supporting maintenance analysis where appropriate data exists.
But AI depends heavily on the information available to it.
If stock information is unreliable, BOMs are wrong and lead times haven't been maintained, adding an AI interface doesn't remove those underlying problems.
There is a more practical order of operations:
- Get the data right.
- Get the process right.
- Connect the information.
- Then use automation and AI where they genuinely improve the outcome.
AI can make a good operational environment better.
It shouldn't become a way of avoiding the fundamentals.
15How to measure manufacturing ERP ROI
ERP ROI shouldn't begin with a generic industry percentage.
Start with your own baseline.
What is the business trying to improve?
For example:
Inventory
Can you reduce:
- excess stock;
- obsolete materials;
- emergency purchases;
- stock discrepancies?
Productivity
Can you reduce:
- manual entry;
- spreadsheet manipulation;
- duplicate administration;
- time spent reconciling information?
Planning
Can you improve:
- forecast visibility;
- production-plan creation;
- schedule adherence;
- purchasing responsiveness?
Commercial performance
Can you improve:
- margin visibility;
- costing accuracy;
- pricing decisions;
- delivery performance?
Management
Can you reduce:
- report preparation;
- manual consolidation;
- time spent resolving different versions of the truth?
If a manufacturer spends 80 hours each month manually creating reports, that can be measured.
If stock write-offs are £200,000 a year, that can be measured.
If planners spend two days producing the production plan, that can be measured.
The strongest ERP business cases connect investment with specific operational change.
16Where NetSuite can fit
Only after the requirements are understood should the ERP platform become the focus.
For some manufacturers, NetSuite can provide a strong foundation because it combines operational and financial information within the same cloud ERP environment.
Its manufacturing capabilities include areas such as work orders, Work in Process, manufacturing routings, work centres and demand and supply planning. Oracle's current NetSuite documentation describes routings that can define manufacturing steps, work centres, labour and machine resources, together with WIP processes that track materials through production and demand-planning functionality that can generate suggested purchasing or manufacturing supply.
That doesn't automatically make NetSuite the correct answer for every manufacturer.
Nor should ERP selection start with:
“How do we make our requirements fit NetSuite?”
It should start with:
“How does our business need to operate?”
Then:
“Can NetSuite support that effectively, natively or as part of a sensible wider architecture?”
For a manufacturer evaluating NetSuite, useful areas to explore include:
- inventory;
- purchasing;
- demand and supply planning;
- work orders;
- Bills of Materials;
- manufacturing routings;
- WIP;
- costing;
- warehouse processes;
- financials;
- multi-company operations;
- reporting;
- integration.
Oracle's documentation also shows that manufacturing routings can be used to define operation sequences, work centres, setup/run times and manufacturing cost information, while WIP tracks production from material issue through work-order completion.
The question for any implementation partner should then be:
How will this work in our business?
Not simply:
Can you show us the feature?
That distinction matters.
Going deeper on NetSuite? Read our practical UK guide to NetSuite for manufacturing.
17A practical manufacturing ERP checklist
Before selecting or changing ERP, can you answer these questions clearly?
Strategy
- Why are we considering change?
- What business problems are we trying to solve?
- What measurable improvements do we expect?
- What happens if we do nothing?
Manufacturing
- What manufacturing models do we operate?
- How are BOMs controlled?
- How are routings maintained?
- How is production planned?
- Where are the current constraints?
Materials and stock
- How accurate is inventory today?
- How do we calculate material requirements?
- How reliable are supplier lead times?
- Where do shortages normally originate?
Data
- How clean is our item data?
- Who owns master data?
- Which spreadsheets contain critical information?
- What needs cleansing before migration?
Systems
- Which applications must remain?
- What needs integrating?
- Which system should own each major data type?
- Where is information currently being rekeyed?
People
- Who owns the business processes?
- Which teams will be affected?
- Who will make design decisions?
- How will users be involved before go-live?
Reporting
- Which decisions should the system help management make?
- What KPIs matter?
- Which reports currently take excessive manual effort?
- Which information can't we currently see?
Implementation
- What processes should change?
- What genuinely needs customisation?
- How will testing work?
- How will data be validated?
- How will users be trained?
- How will success be measured after go-live?
If those questions are difficult to answer, that isn't a reason to rush into software demonstrations.
It is a reason to do the discovery properly.
18Frequently asked questions about manufacturing ERP
What is manufacturing ERP?
Manufacturing ERP is an Enterprise Resource Planning environment that connects operational and financial processes involved in manufacturing.
Depending on requirements, this can include sales, purchasing, inventory, BOMs, planning, work orders, production, warehousing, costing and finance.
What is the difference between ERP and MRP?
MRP focuses primarily on calculating the materials and supply required to satisfy demand.
ERP has a wider role, connecting areas such as finance, purchasing, sales, inventory, manufacturing and reporting.
MRP functionality may form part of a wider ERP environment.
Do manufacturers need ERP and MES?
Not necessarily.
The answer depends on the depth of shop-floor control, data collection and production execution required.
Some manufacturers can manage effectively using ERP manufacturing functionality.
Others need specialised MES capabilities integrated with ERP.
The requirement should determine the architecture.
When should a manufacturer replace its ERP?
Consider replacement when the existing environment creates significant operational constraints that cannot reasonably be solved through optimisation, integration or automation.
Examples could include inability to support the required manufacturing model, poor scalability, excessive technical risk or fundamental integration limitations.
Replacement should be a business decision rather than an assumption.
How long does manufacturing ERP implementation take?
There is no meaningful universal answer.
The timescale depends on factors including organisational size, process complexity, manufacturing model, number of sites, data quality, integration requirements, customisation and the availability of internal decision-makers.
A smaller, well-prepared organisation can be very different from a multi-site manufacturer with complex legacy systems.
Beware of implementation estimates that have been produced before those factors have been understood.
What data should be prepared before an ERP implementation?
Typical areas include:
- item records;
- customers;
- suppliers;
- BOMs;
- routings;
- inventory;
- locations;
- open sales and purchase orders;
- financial information;
- pricing;
- lead times;
- units of measure.
The precise migration scope should be deliberately agreed.
Moving every historical record simply because it exists isn't always valuable.
How important is inventory accuracy for MRP?
Very.
MRP recommendations rely on underlying information about demand, supply and available stock.
If inventory records are materially inaccurate, planning output can also become unreliable.
Technology doesn't remove the need for stock discipline.
Should manufacturing ERP replace spreadsheets?
Not every spreadsheet.
Spreadsheets remain extremely useful analytical tools.
The concern is when a spreadsheet becomes the uncontrolled operational system for a process that should be governed by ERP.
A good test is:
If the person who owns this spreadsheet is absent tomorrow, can the business still reliably operate the process?
Is cloud ERP suitable for manufacturing?
For many manufacturers, yes.
But suitability depends on the actual operating environment.
Connectivity, shop-floor systems, integrations, specialist machinery, regulatory requirements and business-continuity considerations should all form part of the assessment.
How should manufacturers choose an ERP implementation partner?
Don't evaluate the partner solely on software knowledge.
Look at whether they understand the operational questions behind the software.
A good partner should be prepared to challenge requirements, understand manufacturing processes, discuss data quality, explain trade-offs and identify where standard functionality is more sensible than customisation.
You should leave discovery meetings feeling that the partner understands how your business works, not merely which ERP modules you might buy.
19ERP should make the manufacturing operation clearer, not simply more digital
Manufacturing ERP isn't valuable because it puts more processes on screens.
It is valuable when it helps a business make better operational decisions.
- When sales can understand whether an order can realistically be delivered.
- When purchasing can see changing material demand.
- When planners trust the stock information they are working with.
- When production works from controlled product and routing data.
- When finance can understand manufacturing cost without waiting for somebody to rebuild it in a spreadsheet.
- When management can see the same operational picture.
- And when growth doesn't automatically mean more manual administration.
That outcome depends on software.
But it also depends on process design, data quality, integration, people and implementation decisions.
Which is why the right place to start isn't usually a product demonstration.
It's understanding how your manufacturing operation works today, what is getting in the way and what you need it to do better.
Talk through your manufacturing requirements with Web Control
If you're reviewing manufacturing ERP, considering NetSuite, or trying to establish whether the real problem is your ERP, your integrations or the way the existing environment has been implemented, Web Control can help you work through the requirements before jumping to a solution.
We can look at the operational processes, data, systems and reporting behind the problem and help determine what needs replacing, improving, integrating or automating.
Start with the manufacturing problem. Then decide what technology genuinely needs to change.