A phased ERP proposal can still leave an important question unanswered: what happens if the first live workflow must stop?

“We can roll back” is not a complete plan. The team needs to distinguish returning to an older process from dealing with records already created during the pilot.

Define what would trigger a pause

Choose observable conditions relevant to the workflow: unexplained totals, missing required records or an access problem that prevents authorized staff from completing work. Have the implementation team and business owner agree on the actual thresholds.

Do not borrow arbitrary percentages from a generic checklist. The seriousness of a discrepancy depends on what the workflow does and the controls around it.

Name the person who can stop it

Record the decision-maker, their backup and the communication route. Staff need to know how to report a problem and where to find the current operating instruction.

Specify which automated actions pause and which business activities continue. “Stop the pilot” should not leave every department guessing.

Account for work already performed

Use an illustrative order workflow. If records were created in the new system before the pause, who identifies them? How will the team prevent the same work from being entered again in the old process? Which system is the reference for resolving discrepancies?

These are design questions for the actual implementation. Do not assume that restoring an application automatically reverses external actions, payments or messages.

Rehearse with an appropriate test

Ask the implementation team to demonstrate the pause and reconciliation process in a suitable test environment. Keep the result with the pilot acceptance record. If a step still depends on an undocumented manual decision, name it and assign an owner before launch.

Vanteliq’s Sales to Delivery page distinguishes its defined workflow scope from later phases. Bring a rollback scenario to the fit discussion and verify the controls available for your proposed configuration. The aim is a bounded pilot with a credible response to trouble, not a promise that trouble cannot happen.

Request an ERP fit assessment

Featured image: AI-generated editorial illustration.