Tennant's November 2025 SAP go-live disrupted order-to-cash. Thirty million dollars in sales impact. Manual purchase orders replacing automation. Demand signals that don't reach suppliers. This is the parallel order flow layer that restores the pipeline — order in, signal out, fulfillment routed — while SAP is being remediated underneath.
Every order that enters the system is captured, signaled, routed, sourced, built, and shipped — without waiting for SAP's order-to-cash modules to be repaired. The layer sits between intake and fulfillment, and reconciles back to SAP when SAP recovers.
Orders captured at every channel — dealer portal, direct, EDI — and admitted to the pipeline the moment they arrive.
→Real demand computed from live orders, not from broken SAP forecasts. Signals recomputed continuously as order mix shifts.
→Material requests and purchase orders routed to the correct suppliers — replacing the manual POs currently issued by hand.
→Inbound materials tracked against the signal. Shortages surfaced before they hit the line, not after.
→Build schedule driven by the restored signal, coordinated across Tennant's manufacturing footprint.
→Fulfillment confirmed against the original order. Order-to-cash closes cleanly at the shipment boundary.
Same orders. Same suppliers. Same factories. The difference is where the signal is computed and how the order is routed.
Tennant's systems stay where they are. The order flow layer meets them at their interfaces — the SAP Adapter for reconciliation, IRIS for telemetry-derived signals, Pro-Panel for dealer and service visibility. Nothing is ripped out. Nothing is rebuilt twice.
Bidirectional reconciliation between the restored layer and SAP. Orders, materials, and confirmations flow back to SAP on the schedule SAP can absorb — without requiring SAP to be correct in the interim.
Tennant's connected-equipment platform. Telemetry from deployed machines feeds usage and service signals into the demand computation, so the layer sees real-world consumption — not just order history.
Dealer and service visibility layer. Order status, ETA, and fulfillment confirmation surface here for Tennant's field organization — so dealers see accurate state throughout the pipeline.
Tennant's own disclosure puts SAP recovery at H1 2027 — over a year from now. The order flow layer does not wait on that timeline. It restores order-to-cash on its own schedule, then reconciles back to SAP as SAP catches up.
North America deployment goes live. Order flow, demand signaling, and supplier routing degrade immediately. Manual workarounds introduced.
$30M sales impact disclosed. Capitalized and expensed costs recognized. 2026 remediation projected above $20M against an original $5M budget.
The layer deploys alongside SAP. Order intake, demand signal, supplier routing, material flow, production, and shipment run continuously outside the broken path.
Manual purchase orders eliminated. Demand signals reaching suppliers correctly. Order-to-cash closing cleanly at shipment.
The layer runs until SAP is remediated. Then it reconciles — SAP resumes primary role, the layer hands back control without rework or duplication.
Tennant's stated recovery horizon. The layer has been operating order-to-cash for over a year by this point — no lost quarters waiting.
Every month SAP is unremediated is another month of manual purchase orders, incorrect signals to suppliers, and sales impact. The parallel layer closes that gap. It doesn't compete with SAP remediation — it runs underneath it, so the business keeps operating while the fix proceeds.
The node is live. The pipeline is running. Activation is a one-time fee plus monthly operation — priced after the layer is built, not before.