Tennant's ERP Failure Is Now a Securities Investigation: What Every Implementation Team Should Learn

In February 2026, Tennant Company, the Minneapolis-based manufacturer of industrial floor cleaning equipment, disclosed that its new ERP system had disrupted its ability to process and ship customer orders. The share price fell 23.4% in a single day. Within weeks, securities lawyers were investigating whether the company had misled investors about the state of the project.

What makes the Tennant story worth studying is not the go-live failure itself. ERP go-lives fail with depressing regularity, and we have covered the most famous ERP disasters before. What is different here is the second-order consequence: the gap between what management told the market and what was actually happening inside the programme has become a potential securities law problem.

For anyone running an ERP implementation at a listed company, or advising one, this case moves the goalposts. Readiness reporting is no longer just a project governance question. It is a disclosure question.

1. What Happened at Tennant

On paper, Tennant's ERP programme was a sensible modernisation. The company had accumulated eight separate legacy ERP systems across its global operations and set out to consolidate them into a single global instance of SAP S/4HANA, with a major consultancy supporting the implementation. The rollout was phased by region: Asia-Pacific first, then North America.

Throughout the programme, management's message to investors was reassuring. The project was described as progressing as anticipated, on time and on budget. The Asia-Pacific launch was characterised as successful, with disruptions mitigated and operations stabilised.

Then came the North American go-live. This was the region carrying the bulk of Tennant's revenue, and the rollout caused severe operational disruption. The company found itself unable to process and ship customer orders reliably. When the scale of the problem was disclosed on 24 February 2026, the market reaction was brutal: a 23.4% share price drop in one session.

The financial damage went beyond the share price. Tennant attributed roughly $30 million in lost sales to the disruption and now expects to spend more than $20 million on remediation in 2026, against an original plan of around $5 million. A project positioned as on budget ended up quadrupling its stabilisation costs.

2. The Statements Under Scrutiny

The securities investigation is not about the ERP failure itself. Companies are allowed to run difficult projects, and markets understand that big system changes carry risk. The investigation is about the distance between what was said and what happened.

Investigators are examining whether Tennant made false or misleading statements about the progress, timeline, and budget of the implementation. The specific phrases now under the microscope are the ones every ERP steering committee has heard, and probably said:

• "Progressing as we've anticipated": a statement of confidence in the plan, made while the hardest phase was still ahead
• "On time and on budget": the classic reassurance, which the subsequent $20 million remediation bill directly contradicts
• A "successful" Asia-Pacific launch with "mitigated disruptions and stabilized operations": language that framed early problems as solved rather than as warnings

None of these statements is unusual. That is exactly the point. This is the standard vocabulary of programme status reporting, repeated up the chain from project teams to executives to earnings calls. When the underlying readiness data does not support the vocabulary, a listed company has a problem that no amount of post-go-live firefighting can fix.

3. The Phased Rollout Trap

Phased rollouts are supposed to reduce risk. Prove the design in a smaller region, learn the lessons, then take on the bigger ones. Tennant followed the playbook: Asia-Pacific first, North America second. So why did the second phase fail so badly?

Because a phased rollout only reduces risk if each phase is honestly assessed. The trap works like this:

• The first phase is declared a success: partly because it is smaller, partly because the programme needs a win, and partly because problems get labelled as "stabilisation activities" rather than defects
• The success narrative hardens: once leadership has told the market that phase one went well, the organisation becomes invested in that story. Raising fundamental concerns now means contradicting the CEO
• The next phase inherits unearned confidence: testing scope, contingency plans, and readiness criteria for the bigger region are calibrated against the sanitised version of phase one, not the real one
• Scale differences get underestimated: a template that coped with a smaller region's volumes, integrations, and process variants meets the full complexity of the core market for the first time in production

The lesson is not that phased rollouts are wrong. It is that the gate between phases must be a genuine readiness assessment, not a narrative checkpoint. If the first phase needed months of firefighting to stabilise, that is data. Treating it as a footnote guarantees the same problems will reappear at larger scale, as covered in our guide to ERP risks in 2026.

4. When Readiness Reporting Becomes a Liability

For years, the cost model of a failed ERP go-live had three familiar lines: remediation spend, lost revenue, and reputational damage. The Tennant case adds a fourth that changes the calculus for listed companies: securities exposure.

The mechanics are straightforward. Public statements about a major implementation are material information. Investors make decisions based on them. If the statements paint a healthier picture than the programme's internal data supports, and the share price falls when reality emerges, shareholders who bought at the inflated price have losses to point to. That is exactly the fact pattern securities lawyers look for, and in Tennant's case they moved within weeks of the disclosure.

This should sharpen minds in two places. First, in the boardroom: executives repeating "on time and on budget" to analysts need to know what evidence sits underneath that sentence. Second, in the programme itself: the project team's status reporting is now, in effect, the raw material for market disclosures. A RAG status flipped to green under deadline pressure does not stay inside the project. It propagates upwards into earnings calls.

5. Evidence Beats Optimism

The uncomfortable question the Tennant case poses to every ERP programme is simple: if your CEO said "on time and on budget" tomorrow, could you produce the evidence that supports it?

In most programmes, the honest answer is no. Readiness lives in scattered spreadsheets, test results sit in email threads, and the official status is whatever survived the last steering committee. Nobody is lying, exactly. But nobody could reconstruct, from records, what the organisation knew about system readiness on any given date.

That reconstruction is precisely what matters when things go wrong. A well-run user acceptance testing cycle produces it as a by-product:

This evidence works in both directions. It stops premature go-lives, because a dashboard showing failed order-to-cash scenarios is much harder to override than a verbal "we'll manage". And if problems emerge anyway, it demonstrates that the organisation's statements were grounded in the best available information at the time. That is the difference between a difficult project and a securities case.

6. Lessons for Your ERP Programme

Whether you are a consultant delivering implementations or a project manager inside the business, the Tennant case translates into five concrete practices: