Tennant disclosed a $30 million sales shortfall tied to disruption from an enterprise resource planning (ERP) rollout, according to reporting from ERP Today. The industrial cleaning equipment manufacturer now faces heightened investor scrutiny over how the deployment unfolded and what governance allowed the impact to reach the revenue line.

The headline figure, as reported by ERP Today, refers to lost sales during the rollout disruption rather than a broader project write-down. A $30 million revenue impact is material enough to force a management response and reshape the full-year outlook at any mid-cap industrial manufacturer.

What does the $30 million figure cover?

The $30 million represents revenue that did not book during the affected quarter because order-to-cash processes failed inside the cutover window. In manufacturing ERP rollouts, the most common ways a deployment translates into lost sales include:

• Missed ship dates and delayed order fulfillment
• Backorder accumulation that pushes revenue into subsequent periods
• Pricing concessions offered to retain customers affected by late deliveries

Whether the lost sales recover in subsequent quarters or prove permanent will determine the longer-term damage to Tennant's guidance and the credibility of the deployment plan.

Why are investors reacting now?

ERP implementations have moved from back-office utilities to board-level risk categories following high-profile cost overruns and operational disruptions at manufacturers and consumer goods companies. A disclosed revenue hit tied directly to a system rollout tells analysts that internal controls around the deployment broke down and that customer-facing operations were affected.

When a company confirms that an IT system — rather than market demand or pricing pressure — drove a revenue miss, the market typically targets the credibility of the CIO function and the deployment governance, not just the project manager.

What remains unclear from the current disclosure?

ERP Today's headline does not surface several operational details enterprise IT leaders would need to benchmark the case:

• The ERP vendor and version
• The go-live date and the cutover window
• Whether the deployment is now stable or still causing friction
• Specific manufacturing or distribution sites affected
• The executives who confirmed the figure

Without those specifics, IT leaders cannot yet draw vendor or implementation-partner conclusions from the case.

What should CIOs take from the incident?

Even with the limited disclosure, the headline offers three warnings for ERP programs in flight at other manufacturers:

• Revenue exposure from a cutover is rarely confined to the IT budget line — it can move the P&L directly
• A $30 million hit is large enough to trigger board-level questions regardless of company size
• Vendor and implementation-partner selection are now under the same investor lens as execution discipline

CIOs at firms with active ERP rollouts should review their cutover communications to sales, customer service, and supply chain teams now, before quarter-end disclosures force the conversation.

Tennant's next earnings call will determine whether management frames the ERP hit as a one-quarter anomaly or a structural issue requiring extended remediation. The vendor and timeline details, once disclosed, will determine whether this case becomes a cautionary tale for the broader mid-cap manufacturing ERP market.