Stuart Totterdell
Technical Director
Horizontal ERP vendors sell breadth: one suite for finance, inventory, purchasing, projects, and CRM, with a slide somewhere that says your industry is supported too. Mid-market manufacturers, distributors, construction firms, and field service businesses buy that story, and then spend years forcing industry reality into generic modules and a growing graveyard of bolt-ons.
The fit never really arrives. The workarounds do instead. This is not a complaint that software should somehow read your mind - it is a recognition that industry mechanics are not optional extras. Batch genealogy, catch-weight, configurators, site-based costing, plant maintenance, mobile field jobs, subcontractor retention, delivery slotting - these are not "nice to have" reports. They are how money and risk actually move through the operation, and a horizontal core that only approximates them will always leak into spreadsheets, specialist tools, and tribal process eventually.
Generic modules plus bolt-ons is the default trap
The pattern is a familiar one. Finance and basic stock go live first, while industry-critical processes get parked for phase two. Phase two becomes a partner customisation, which becomes a third-party bolt-on, which becomes an integration nobody fully trusts. The ERP remains the system of record as far as the board is concerned, while the vertical reality runs somewhere else entirely.
In manufacturing, planning and shop-floor execution end up living outside the suite because the horizontal APS or MES story was always thin. In distribution, warehouse and carrier processes live inside a WMS and a set of carrier portals, while the ERP pretends it still owns fulfilment. In construction and field service, job costing, variations, and mobile completion struggle inside project modules that were designed for a different world entirely. Each individual bolt-on can be justified in isolation, but together they quietly recreate the exact fragmentation the ERP purchase was supposed to end - with a more expensive centre of gravity underneath it.
Industry fit is a deal-breaker, not a preference
When ops managers say the system "does not fit," they are often told they simply need better change management, more training, or the next release. Sometimes that is a fair response. Often, though, they are naming a genuinely structural mismatch that no amount of training will resolve.
If your competitive edge depends on configure-to-order, regulated batch control, complex pricing, multi-site replenishment, or field engineer utilisation, a horizontal package that treats those as edge cases will tax the business forever. That tax shows up as slower quotes, weaker compliance evidence, bloated inventory, and supervisors who quietly manage the real process off-system. Industry fit should be an explicit gate in any ERP renewal or platform shortlist, not a demo script where the vendor shows a reference customer from a vaguely adjacent sector - it deserves a proper working session built around your top ten industry workflows, with your real data shapes, your actual exceptions, and your regulatory constraints on the table.
Do not confuse a vertical gap with needing a bigger ERP
This is where mid-market leadership so often gets sold the wrong upgrade. The pain is real - the current horizontal system genuinely under-serves industry process - but the proposed cure is often simply a larger horizontal suite with more modules, more licences, and a longer implementation timeline. That can increase generic coverage without closing the vertical gap at all, leaving you with a bigger footprint, the same bolt-on pattern, and a considerably higher total cost of ownership.
A clearer pattern for many mid-market businesses is a strong finance and control core, paired with best-fit vertical capability for the industry processes that actually differentiate delivery, connected through deliberate data and systems integration between the two. Vertical SaaS or specialist operational platforms are not a failure of ERP strategy when they carry the workflows the suite will never love - they are simply an admission that one horizontal product rarely owns the entire operating model on its own. The failure mode is accidental architecture, where vertical tools get added in panic, poorly integrated, with nobody owning the handoffs between them. The success mode is intentional: decide deliberately what the core must own for financial integrity and inventory truth, and what should live instead in industry systems built specifically for the work.
What to demand before you buy more breadth
Ask vendors and partners to show you the industry process itself, not the module list. How does a variation get costed and approved in your actual model? How does a catch-weight receipt land correctly in stock and costing? How does a field job close cleanly to payroll, stock, and invoice without a clerk rekeying everything by hand? Where do exceptions go when reality inevitably diverges from the happy path shown in the demo?
If the answer involves customisation, a future roadmap, or a partner ISV you have never actually evaluated, believe that answer and price the real estate accordingly: licences, integration, dual keying, and the ongoing ops cost of permanent misfit. Pair that thinking with IT and process strategy that clearly separates "we hate our ERP" from "our industry process was never going to live happily inside a horizontal box." Those are genuinely different problems, and they need different remedies entirely.
Fit over fashion
Horizontal ERP will never fully fit your industry if your industry has specialised physics of its own. That does not mean abandoning the core - it means abandoning the pretence that breadth automatically equals fit.
Choose where horizontal control is non-negotiable, choose vertical systems where industry depth is non-negotiable, and integrate the two with real intent. Refuse the reflex that treats every operational gap as something a bigger generic suite will eventually solve. The businesses that manage to calm down their ERP conversations are usually the ones that stopped asking one product to be everything, and started designing an estate that actually matches how their industry works.
