FEATURE Smart factories & software
Ashish Kumar, director, Web Alliance, outlines why so many manufacturing ERP projects fail, and offers insight into how to get it right
CREATING A CULTURE FOR ERP SUCCESS
E
nterprise Resource Planning (ERP) systems are the backbone of modern manufacturing. They promise visibility across production,
procurement, finance, stock and customer management, hand-in-hand with an increase in efficiency, control and scalability. But ERP failure rates in manufacturing remain stubbornly high. Budgets overrun. Timelines slip. Staff disengage. Systems go live but never truly embed. In some cases, businesses quietly revert to spreadsheets and manual workarounds within months. The uncomfortable truth is that most ERP
failures are not caused by technology but are instead caused by decisions made long before the system is built or even selected. The good news is that most failures are predictable, which means they are absolutely avoidable. One of the most common mistakes in manufacturing ERP projects is digitising processes that have never been clearly defined in the first place. Many manufacturers operate with a mix of legacy systems, spreadsheets and specific knowledge held by experienced staff. Production managers know how things work; estimators understand the margins; procurement teams have the supplier relationships. But very often, no one has formally mapped the end-to-end workflow. When businesses rush into ERP implementation without documenting how orders move from enquiry to delivery, for example, they simply automate confusion. Questions frequently go unasked: How does a quote translate into a works order? Where do approvals sit? How are material shortages flagged? How does shop-floor data feed back into costing? Where are margin leaks occurring? If these processes aren’t clarified before system selection or development, all that happens is the ERP becomes a digital version of
18 May 2026 | Automation
an already inefficient structure. Successful projects begin with operational mapping. That means sitting with each department, identifying handovers, bottlenecks and duplication, all to challenge legacy habits. Technology should then support an optimised workflow, rather than preserving and sometimes exacerbating inefficiencies. Another frequent pitfall is assuming that a generic, off-the-shelf ERP will flex easily to suit complex manufacturing needs. Many mainstream platforms are designed to serve broad industries and can work very well in standardised environments. However, manufacturing (particularly engineering-led or project-based manufacturing) rarely fits neatly into standard templates. Manufacturers often require complex Bill of Materials structures, multi-stage production workflows, variable pricing models, shop- floor data capture, traceability and compliance tracking, as well as integration between CRM, production and finance. When manufacturing businesses attempt to force their sometimes- unique workflows into rigid systems, they end up compromising on process efficiency or reporting accuracy, or even both. This doesn’t mean that every manufacturer needs a fully bespoke ERP, but it does mean that careful evaluation is essential. The selection process must assess how configurable the system is, whether it supports real manufacturing workflows, the cost and feasibility of customisation and long-term scalability.
Choosing software purely on brand
recognition or initial licence cost can prove to be more expensive than originally thought as the implementation progresses. ERP systems in manufacturing impact everyone: directors, production managers,
warehouse teams, sales, finance, supply chain partners and even customers. Yet many projects are led by a small decision- making group without enough meaningful involvement from the very people who will be using the system. The result is predictable resistance.
When shop-floor teams feel a system has been imposed on them, adoption suffers. Data accuracy declines and workarounds appear. The most effective implementations treat
ERP as a business transformation project, not an IT purchase. That means involving department heads early, running workshops across operational teams, testing real-life scenarios before go-live and continuously gathering feedback.
When users see their actual workflows
reflected in the system, engagement increases dramatically, as cultural buy-in can often be just as important, if not more so, than features and functionality. Moving from verbal job allocation to system scheduling, replacing manual stock checks with live inventory management, enforcing structured data entry where informal notes were previously accepted and shifting from reactive problem-solving to preventative analytics all require quite a bit of behavioural adjustment. To overcome this cultural challenge, what’s needed is effective leadership, communication and training.
Change management must include clear communication on why the system is being implemented, training tailored to each role, champions within each department and measured rollout phases rather than abrupt transitions. Without visible senior buy-in, employees may see ERP as additional administrative burden rather than operational
automationmagazine.co.uk
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40
