Fachbeitrag zu ERP- und Business-Central-Projekten
Article · Governance

Why does the ERP bill often arrive only after go-live? Three cases from October 2026

In October 2026, LKQ, Erasmus University Rotterdam and Oriola published figures on ERP projects that worked technically and still became expensive. What the cases have in common, and how to plan the months after the cut-over date.

Frank Maier16.11.20267 min read

What this article is about

  • LKQ: around 95 million US dollars of revenue and 43 million of earnings in the third quarter, the CEO left
  • Erasmus University: budget up 70 per cent, start postponed by a year; Oriola: from 35 to around 54 million euros
  • Nowhere was the software the bottleneck; data, enablement and steering were
  • Before the cut-over: data test, enablement test and operations test by the business departments
  • Plan the months afterwards as a project phase, with budget, metrics and an owner on the customer side

What did LKQ, Erasmus University and Oriola report in October 2026?

In October 2026, three organisations published figures on ERP projects that worked technically and still became expensive. The US car parts distributor LKQ reported preliminary quarterly figures on 23 October: revenue of 3.32 billion US dollars after 3.50 billion in the prior year, an organic decline of 9.8 per cent in Europe and a segment margin of 4.1 to 5.1 per cent after 10.0 per cent before. The release names the cause as “operational disruptions associated with the ERP implementation in Germany”. On the same day the CEO and the head of Europe left the company, and full-year guidance was withdrawn (LKQ, press release, 23.10.2026).

In the analyst call on 29 October, CFO Rick Galloway put the revenue loss from the implementation at the German subsidiary Stahlgruber at around 95 million US dollars for the quarter and the earnings effect at around 43 million. Daily sales were running at about 85 per cent of the prior year. In the second quarter, LKQ had still estimated the lost revenue at around 140 million US dollars and named faulty data as one cause (Motley Fool, transcript, 29.10.2026; carwing.ch, 26.10.2026). LKQ does not say which software is in use.

Erasmus University Rotterdam is replacing its administrative software, moving from SAP to Oracle. According to the university magazine, the budget of 11.9 million euros has risen to 20.2 million, an increase of 70 per cent, and the start has been postponed from early 2026 to 1 January 2027. The postponement alone costs 4.5 million euros. A review by PwC found that too little project management and support had been planned, and the university's own staff lacked the time and specialist knowledge for a project of this size (Erasmus Magazine, 29.10.2026).

The Finnish pharmaceutical wholesaler Oriola has re-planned its ERP and warehouse programme after the first deployment stage in Sweden: completion moves from 2027 to 2028, investment costs rise by around 11 million euros and licence costs by around 8 million. The roughly 35 million euros announced in 2024 thus become around 54 million. The company has strengthened its internal governance and changed its integration partner (Oriola, stock exchange release, 01.10.2026; interim report, 29.10.2026). A fourth case from Mexico fits the picture: at the food group Grupo Herdez, overheads rose by 14.7 per cent in the third quarter, mainly through staff and licences for stabilising the new ERP (quarterly commentary by Ve por Más, 28.10.2026).

Why does the bill only arrive when the project meets day-to-day operations?

The three cases have different causes but a common moment. The budget was approved while the project was still a plan. The bill arrived when the plan met everyday work: at LKQ after go-live, at Oriola after the first deployment stage, at Erasmus the moment it became clear that the organisation would not be ready on the cut-over date. In all three cases the bottleneck was not the software but data, people and steering.

That is no coincidence but a property of ERP budgets. Licences, consulting days and development can be estimated in advance. What a warehouse does when stock levels are wrong, what a customer does when the second delivery fails to arrive, and how long an accounting team needs before it trusts the new month-end close appear in no proposal. These costs arise on the customer's side, not the service provider's, and they arise after the date on which the project was officially delivered. We showed what abandoned projects look like in three cases from summer 2026 . The October cases are the other side: projects that ran, and whose price only became visible later.

Go-live is not the end of the project. It is the day the customer gets to see the bill.

What does “faulty data” mean in a wholesaler with 155 branches?

LKQ operates around 155 branches in Germany. In the analyst call, the CFO said the problem was not a system issue “per se” but a “training opportunity” for the weaker branches. Three quarters of the branches were delivering on time and in full again in the third quarter; in the second quarter the rate across the region had still been below 80 per cent (Motley Fool, transcript, 29.10.2026). Taken together, that describes fairly precisely what a data problem looks like in distribution: not as an error message, but as a delivery that does not arrive.

In a parts wholesaler, a wrong stock level does not mean a wrong number but a workshop that cannot finish a vehicle and orders elsewhere next time. A wrongly assigned item means a delivery that comes back. Each of these errors is small on its own and can be fixed with retraining or a correction. In total and over months they add up to the revenue that moves to a competitor. Who is responsible for this on the business side is described in our answer on responsibility for data quality in the ERP : not IT, but the business.

How do you tell before the cut-over date whether data and people will hold up?

The uncomfortable news is that all three organisations could have answered this question beforehand. Three tests are enough, and none of them is expensive. The first is the data test: the business departments run their critical transactions with real, migrated data, not with the project team's test data. The second is the enablement test: at every site there are named people who can complete the core transactions in the new system without help, and this has been measured, not assumed. The third is the operations test: for the first weeks after the start it is clear who decides when stock levels, prices or deliveries are wrong, and who fixes the cause rather than just the individual case.

None of these tests needs an additional tool. They need a date on which someone is allowed to say “not yet” without it counting as failure. Which criteria a go-live should meet, and why a green test report alone is not readiness, is described on our page on go-live readiness in Business Central.

How do you plan the months after go-live as a project phase?

The second lever lies after the cut-over date. In many project plans the period afterwards is called hypercare and lasts two to four weeks with a reduced team. The October cases show that the disruption lasts longer: LKQ went live in spring and was still working on stabilisation in October, and at Herdez the costs of stabilisation were still weighing on earnings a quarter after the start. Whoever plans the months after go-live as a project phase, with its own budget, with criteria for its end and with an owner on the customer side, only makes visible the costs that would otherwise be hidden in operations.

In practice this means: the project team stays at full strength until the delivery rate, the throughput time in order entry and the month-end close are back to where they were before the change-over. Every company knows these three figures from its old system, and they are a more honest yardstick than a date. Only when they are right is the project over.

How we support go-live and the months afterwards

We have been supporting ERP projects for more than 25 years, many of them international, and Business Central is our home. We treat go-live not as a date but as a decision: with criteria that the business side signs off, and with the right to say “not yet”. We plan the months afterwards as a phase of their own, with budget, metrics and an owner on your side. How we keep steering and delivery together is described under Governance and delivery.

Is your go-live coming up in the next six months? Then we are happy to look at the criteria with you rather than at the calendar. The first conversation is about your questions, without a presentation and without a proposal.

Frequently asked questions

Isn't hypercare there for exactly this?
Yes, but usually too short and too thinly staffed. Two weeks with half a team are enough for error reports, not for stabilising data and processes. The October cases show disruptions over several months. Plan the phase by metrics, not by weeks.

How do I tell that our budget does not cover the time after go-live?
When the plan after the start date only says “support” and there is no budget for data corrections, retraining and decisions on the customer side. And when nobody can say at which figures the project counts as complete.

Does this apply to mid-sized companies too, or only to large groups?
The pattern is the same, the buffer smaller. A large group can carry a weak quarter. A mid-sized company whose delivery rate stays below 90 per cent for three months loses customers who do not come back.

Invitations by email

Stay on top of things without tracking everything yourself.

Once a month, Frank Maier puts into context what is moving in the ERP world. Plus the invitation to the next live webinar.

Thank you, you are signed up.
Related

More insights

What industry knowledge does ERP consulting still need today?
Article · Governance

What industry knowledge does ERP consulting still need today?

Industry experience is among the first questions when choosing a partner. It used to mean knowing the industry solution. Today something else counts: understanding where a company works differently from its industry, and mapping that in the standard.

09.11.2026Read →

Where does your project really stand?

At DGP you speak with an experienced consultant, not with a sales team.

Arrange a conversation