Tennant Company, a global manufacturer of industrial cleaning equipment, is facing the operational and financial fallout of a troubled ERP rollout, after system issues disrupted order processing and triggered a sharp market reaction.
The company disclosed in late February that the North American deployment of its new ERP system caused significant disruptions, leaving it unable to process and ship customer orders. The impact was immediate: Tennant reported approximately $30 million in lost sales tied to the rollout, along with remediation costs expected to exceed $20 million in 2026, far above initial projections.
The announcement sent shares down more than 23% in a single day, showing how deeply ERP execution risk can affect core business performance.
ERP Failure Impacts Revenue
The Tennant case reflects a recurring pattern in large-scale ERP transformations. What begins as a back-office modernization effort can quickly cascade into front-line operational failure when core processes are disrupted.
In this instance, the system breakdown directly affected order fulfillment, one of the most critical revenue-generating functions. The inability to process and ship orders highlights how tightly ERP systems are now coupled to real-time operations, particularly in manufacturing and distribution environments.
The scale of the financial impact suggests that stabilization challenges extended beyond initial go-live issues, requiring significant additional investment to restore system functionality and operational continuity.
Analysis
What this means: ERP failures are increasingly visible at the business level. Tennant’s inability to process orders shows how deeply ERP systems are embedded in revenue operations. When implementations fail, the impact usually is immediate, measurable, and not confined to IT. Organizations should treat go-live readiness as a revenue protection exercise, including stress-testing order-to-cash workflows under real operating conditions.
Investor Scrutiny Follows Operational Breakdown
Following the disclosure, select law firms announced investigations into Tennant’s prior statements about the ERP rollout, focusing on whether the company accurately represented the project’s progress and risk.
These investigations are common in the wake of sharp stock declines tied to operational issues. They do not establish wrongdoing but reflect heightened investor sensitivity to execution risk in large transformation programs.
For enterprise leaders, the episode highlights a growing reality: ERP implementations are material business events with direct implications for financial performance, market confidence, and executive accountability.
Analysis
What this means: Execution discipline is a market-facing issue. Investor reactions and subsequent scrutiny show ERP programs are now judged not just on long-term outcomes, but on short-term execution and transparency. Clear internal escalation paths and transparent external communication plans should be in place well before go-live to manage operational and reputational risk.
Execution Risk Remains Defining Challenge
Tennant’s experience highlights the gap that can exist between ERP planning and execution, particularly in complex, multi-region rollouts.
Even when earlier phases appear stable, scaling deployments across regions can introduce new variables, from process inconsistencies to data and integration challenges. North America, often the largest and most complex operating region, can expose issues that were not evident in earlier rollouts.
The result is a compression of risk into the go-live window, where failures are no longer contained but immediately visible in revenue, customer experience, and financial results.
Analysis
What this means: Phased rollouts do not eliminate risk, they redistribute it. Success in one region does not guarantee stability at scale, particularly when process and geography variability and operational complexity increase. Leading teams mitigate this by running parallel environments and validating region-specific processes before full cutover.
