Five years ago, we used to tell clients that the best ERP was the one that adapted to industry in general. Today we know we were wrong. The best ERP is the one that makes your industry look obvious.

In a textile factory in the Vale do Ave with 120 employees, we implemented a "big-brand" ERP in 18 months. It cost 250 thousand euros. In the end, the team still needed a parallel spreadsheet to manage colours and sizes. In another garment manufacturer in Famalicão, the client bought a generic system to control production hours. Three months later, they discovered they could not trace a batch for the client brand that demanded compliance with the EU Strategy for Sustainable and Circular Textiles. Neither of these stories is about vendor incompetence. It is that the vendor was not listening to the sector.

The difference between signing a contract with a generic vendor and choosing a vertical solution is the difference between buying a made-to-measure suit and buying a suit from a big retailer. The latter is cheaper, it fits the body, but it does not let you breathe at the shoulders.

What "vertical fit" really means

Vertical fit is not a marketing word. It is the answer to a very simple question: has this ERP already solved the problems that my sector has?

Not the problems the sector should have. The problems the sector actually has.

In a footwear factory, vertical fit means the system understands that an SKU is not just a code and a price. An SKU is a combination of model, colour, size, width, fit and, often, a sample version for two or three international buyers who visit in August (men's collection) and February (women's collection). If the ERP sees the SKU as a simple number, it will force you to create 12 thousand product records for a collection of 800 base articles. We have seen this happen — and the client spent six months cleaning up data.

In a food distribution warehouse, vertical fit means the system knows that picking is not just picking — it is full-case picking, split-case picking, cross-docking picking, returns picking, all in parallel, all running against the clock before the train leaves Lousada. A generic ERP sees picking as picking. The result: the warehouse manager is left offline for hours because the system cannot cope with operational reality.

In a garment manufacturer, vertical fit means the system understands that production is not linear. The same order may have three fabric suppliers, four finishing processes, two button suppliers, and all of this has to be traceable down to batch level for compliance. An ERP that thinks in terms of "production order" and "raw material receipt" will create 40 stock movements for an order that, in reality, has only five critical operations. The result is noise — a lot of noise — and the impossibility of tracing what matters.

A vertical ERP is not more expensive because it has more features. It is more expensive because it has the right features — and does not waste time on the wrong ones.

The five questions no vendor wants you to ask

When a generic ERP vendor walks into a meeting room with your CEO, CFO and IT director, they come with slides about "flexibility", "modularity" and "scalability". These are true words. They are also words that mean "we are going to adapt the system to your processes, and that will take time and cost money".

Before you sign any contract, ask these five questions. It does not matter if the vendor does not like the answers. In fact, it is a good sign if they feel uncomfortable.

Question 1: how many of your clients, of my size and in my sector, have been using this ERP in production for more than three years? Don't ask for references — ask for numbers. If the answer is "we have some textile clients", ask for names. If they refuse, you know what this means: they have few, and they don't want you asking embarrassing questions about what went wrong. A vendor with vertical fit knows the names by heart.

Question 2: what is the average implementation time for a company like mine? If the answer is "it depends", they are trying to buy time. Press: "Over the last 12 months, what was the average time?" If it was 14 weeks, they should say so. If it was 28 weeks, likewise. If they have no data, it is because they don't control implementations — which is a red flag.

Question 3: how many of my processes — concrete, specific to my sector — are already parameterised in the system? The answer is: "Let's list them." Then they list them. If the list covers 80% of what you do, the fit is real. If it covers 40%, you are buying an ERP that will force you into heavy customisation — and customisation is the black hole of the budget.

Question 4: if I discover, six months after go-live, that the system cannot do X (a critical process in my sector), how much does it cost to fix? If the answer is "that won't happen", they are lying. If the answer is "it depends on the complexity", they are dodging. If the answer is "on average, Y hours of development, at Z euros/hour", now they are being honest.

Question 5: what is the real TCO — not the slide-deck TCO, the TCO that includes implementation, customisation, training, maintenance and those 200 hours of consultancy that nobody anticipates? If they cannot answer with a realistic range, it is because they don't know. And if they don't know, they will not be able to control your project.

The problem nobody talks about: the factory doesn't want a new ERP, it wants to keep working

There is an uncomfortable truth that vendors hide: implementing a new ERP is like changing production machines. It interrupts production. It costs money. It leaves people stressed.

A vertical ERP reduces this cost because the system already understands your processes. It doesn't need to recreate them from scratch. A textile factory implementing a vertical ERP takes 12 to 14 weeks to go-live. The same factory, with a generic ERP, takes 24 to 32 weeks. Twice the time. Twice the stress. And even so, with a greater risk of failure.

At month-end, when the warehouse manager is calling the IT director because picking is not syncing with the ERP, it doesn't matter whether the system is "flexible" or "modular". What matters is whether the system has seen this before and has a ready solution. A vertical ERP has seen this before. Many times. The vendor has documentation, has tested processes, has the answer in the drawer.

The real cost of an ERP is not the licence contract. It is the time the operation stands still while the system is being implemented. It is the production that doesn't come out because nobody can enter data. It is the warehouse working with radios because the WMS cannot keep up. Multiply those weeks of delay by the hourly cost of your factory. Then compare it with the price of a vertical ERP that takes half the time.

Choosing a generic ERP because it is "cheaper" is like buying a cheap car because it has wheels. In the end, you pay the difference in fuel, maintenance and time stuck in the garage.

How to assess vertical fit before signing

There are three signs that show you whether a vendor has real vertical fit or is just using the word as a sales argument.

Sign 1: Documentation specific to your sector. Ask the vendor for the documentation of one of their clients in your sector — anonymised, of course. Technical sheets, process guides, configuration examples. If the vendor has this, it means they have implemented enough to document it. If they don't, they are improvising. Documentation is the proof that the vendor has solved the same problems you have now.

Sign 2: Participation in sector associations. A vendor with real vertical fit is an active member of ATP (textiles), APICCAPS (footwear), or similar associations. Not as marketing — as a participant in working groups. This means the vendor is listening to the real problems, not just the problems clients bring when they ask for help. If the vendor doesn't know the names of the associations in your sector, it is because they are not investing in vertical fit.

Sign 3: Public case studies (or private ones, if you sign an NDA). Ask for real cases in your sector. Not generic success stories. Specific stories: "We implemented in 14 weeks, OEE went from 58% to 73%, and the team learned the system in two weeks". If the vendor can be concrete, it is because they have real data. If they can only talk about "digital transformation" or "process optimisation", they are selling smoke.

One last piece of advice: talk to the vendor's clients — not the ones they recommend to you, but those you can find through direct contacts. Ask them the most important question: "If you could go back, would you make the same choice?" If the answer is "yes, but...", they are worried. If it is "yes, without reservations", you have found vertical fit. If it is "no", know that the vendor will struggle to explain why your case will be different.

The honest truth about what a vertical ERP doesn't do

A vertical ERP does not solve management problems. If your factory has poor planning, a vertical ERP will let you see the poor planning faster — and that is good. But it will not solve it on its own. You need to change processes, and that is your work, not the software's. The ERP is a mirror. If the image is ugly, the mirror is not to blame.

A vertical ERP also does not replace discipline. If your employees don't use the system because "it's easier to do it by hand", no ERP — vertical or generic — will work. Vertical fit helps, because the system is more intuitive for your sector. The warehouse manager doesn't need three weeks of training to understand how picking works — the system already speaks their language. But discipline is always necessary.

And a vertical ERP is not "ready to use". Implementation, parameterisation, training — all of this is necessary. The difference is that the time is 40 to 50% shorter, because the vendor already knows where the problems are. They don't need to discover them during the project. They have solved them ten times before.

Before you sign, ask yourself this: how much does it cost me for my current ERP not to be optimised for my sector? How much time does my team spend on workarounds — parallel spreadsheets, manual processes, duplicated data? How many person-hours are lost on processes that the ERP should automate but cannot because it was not designed for my sector?

Calculate that number. Multiply it by the working hours lost per week. Multiply by 52 weeks. Then compare it with the cost of implementing a vertical ERP. In most cases, the ERP pays for itself in 18 to 24 months — with the efficiency gained alone.

If your current ERP has not paid for itself yet, perhaps the problem is not the price. It is that it has no fit.

Sources

  • European Commission, EU Strategy for Sustainable and Circular Textiles (2022) — official reference on regulatory compliance in textiles
  • ISO/IEC 27001:2022 standard — traceability and compliance requirements in industrial information systems
  • IAPMEI (Institute for the Support of Small and Medium-sized Enterprises and Innovation), Digital Transformation Guide for Industrial SMEs — guidance on implementing ERP systems in the Portuguese context
  • INE (Statistics Portugal), Statistics of the Portuguese Manufacturing Industry — data on textile, garment manufacturing and food distribution companies in Portugal