Phase 2 · Node Layer 11 · The Delay

EMEA deferred. H1 2027 target.
The cascade is on the record.

Tennant disclosed that the North America SAP go-live was November 2025 and that the recovery target is H1 2027 — approximately 18 months later. In the interim, Tennant disclosed that the EMEA deployment has been deferred beyond 2026. That is the deferral cascade: the initial disruption pulled forward the remediation timeline, which pulled forward the EMEA deployment, which pulls forward every region that follows. The window between disruption and recovery is 3 to 8 months from October 2026. The parallel layer operates inside that window without changing Tennant's stated timeline.

Nov 2025 go-live H1 2027 target EMEA deferred beyond 2026 3–8 month window Layer operates inside
Disclosed Recovery Window · Live
The window doesn't move. The cost inside it does.

Tennant's stated recovery target is H1 2027. From October 2026 that is a 3 to 8 month window. The parallel layer operates inside the window — it does not extend or shorten Tennant's stated timeline.

3–8 mo
to H1 2027 · disclosed
The Cascade

Five stages. One cause.
Every downstream effect.

Click any stage to see what it is, what it cost, and where it landed on the record. The cascade is not speculation — every stage is a disclosed or directly-inferable effect of the November 2025 disruption.

Deferral Cascade · Click any stage
01

Go-Live Disruption

Nov 2025
Order-to-cash disrupted
02

Remediation Committed

Q4 2025 — 2026
$20M+ program spend
03

EMEA Deferred

Beyond 2026
Region on legacy systems
04

Next Regions Deferred

Rolling
Downstream from EMEA
05

Recovery Target

H1 2027
Full remediation horizon
Stage 01 · Go-Live Disruption

The North America SAP go-live disrupts order-to-cash.

Tennant's North America SAP implementation went live in November 2025. It immediately disrupted order entry, shipping, and service capability. The system was "not providing correct demand signals to suppliers." Manual oversight and manual purchase orders were deployed as interim workarounds. This is stage one of the cascade — every downstream effect traces back to this event.

The Ledger

Every dated entry.
Click any row to open.

Each entry in this ledger is either a Tennant public disclosure or a directly-inferable downstream effect. Click any row to see the specific language or reasoning behind it.

Delay Record · Delay Ledger
Six entries · all dated
START Nov 2025 · North America SAP go-live disrupts order-to-cash Q4 2025 ›
Tennant's disclosed language: the North America ERP implementation "introduced several functionality issues that limited our ability to enter orders, ship products, and service our customers." The disruption began on the day of go-live and has continued since.
IMPACT $30M sales impact disclosed Q4 2025 — Q1 2026 ›
Tennant disclosed an estimated $30 million sales impact from the November 2025 disruption. This is the revenue side of the cascade — orders that did not close on time, or at all, during the weeks of limited order entry, shipping, and service capability.
COST $20M+ remediation committed against $5M budget 2026 ›
The original SAP program budget was approximately $5 million. Projected 2026 remediation cost now exceeds $20 million. The overrun is a direct downstream effect of the November 2025 disruption — the remediation budget absorbed the cost of restoring what the go-live broke.
DEFERRAL EMEA deployment deferred beyond 2026 2026 ›
Tennant disclosed that the EMEA SAP deployment has been deferred beyond 2026. The region remains on legacy systems while remediation focuses on the North American deployment. This is the first region-level deferral in the cascade.
CASCADE Downstream regions pull forward from EMEA deferral Rolling ›
The EMEA deferral cascades forward. Every deployment that would have followed EMEA inherits the deferral — either by pivoting to support the North American recovery or by extending their own schedules. This is a downstream effect, not a separate disclosure.
TARGET H1 2027 recovery target — full remediation H1 2027 ›
Tennant's stated recovery target is H1 2027 — approximately 18 months after the November 2025 go-live. From October 2026 that leaves a 3 to 8 month window. The parallel layer operates inside this window without changing Tennant's stated timeline.
The Numbers

Four numbers that define the delay.

Four numbers describe the delay record: 18 months from go-live to recovery target, 3-8 months remaining in the window, one region deferred, and one year of disclosed EMEA slip.

Go-Live
Nov 2025
North America SAP implementation
Recovery Target
H1 2027
~18 months from go-live
Remaining Window
3–8 mo
From Oct 2026 to H1 2027
EMEA Deferral
Beyond 2026
Region on legacy systems
Delay Timeline · Click any marker
Nov 2025
Q1 2026
Mid 2026
Late 2026
H1 2027
Post-2027
Nov 2025 · North America SAP go-live disrupts order-to-cash
The Contrast

Wait the window out.
Or close the window.

The window is the same either way. The question is whether Tennant carries the operational cost of the wait — manual POs, incorrect signals, order-to-cash disruption — or whether the parallel layer absorbs that cost while SAP remediation proceeds.

Wait the Window Out

Current Path
  • Manual POs continue through the full window
  • Incorrect signals to suppliers
  • Order-to-cash disruption continues
  • EMEA stays on legacy systems
  • Cost compounds month over month
  • Timeline unchanged — H1 2027

Close the Window

Activate Path
  • Manual POs return to zero inside the window
  • Signals recomputed from live orders
  • Order-to-cash closes normally
  • EMEA de-risked for future activation
  • Cost flattens on activation
  • Timeline unchanged — H1 2027
Questions

The delay, answered.

Tennant disclosed that the EMEA SAP deployment has been deferred beyond 2026. The region stays on its legacy systems while remediation focuses on the North America deployment. This is a downstream effect of the November 2025 disruption — EMEA pulls forward from the recovery effort.

Tennant's stated recovery target is H1 2027 — approximately 18 months after the November 2025 go-live. From October 2026, that leaves a 3 to 8 month window. The parallel layer operates inside this window without changing Tennant's stated timeline.

The North America SAP go-live was November 2025. The disruption has been active continuously since then — through multiple quarters of disclosed operating cost, ongoing manual workarounds, and the manual PO burden that continues to this day.

The cascade runs: go-live disruption → remediation spend → EMEA deferral → next-region deferral → overall timeline extension. Every downstream effect pulls forward from the initial disruption. The cascade is not speculation — every stage is either a disclosed event or a directly-inferable downstream effect.

No. The parallel layer operates inside the disclosed window — the same 3 to 8 months — restoring order-to-cash operations while SAP remediation proceeds on its own schedule. Tennant's stated H1 2027 target is unchanged. The layer does not extend or shorten the timeline; it closes the operational cost inside it.

The window is on the record.

3 to 8 months to H1 2027. The parallel layer operates inside that window — without changing Tennant's timeline.