PlainlyCase Study · Systems, Data & Automation · UK Retailer
Maintaining retail continuity during an SAP Business One upgrade
A UK retailer needed to upgrade a live SAP Business One environment connected to several operational systems. I planned and tested the change, coordinated two third-party suppliers and used the retailer's offline capability to keep stores trading while the live system was upgraded.
The Challenge
An upgrade that couldn't be treated as an isolated technical change
The SAP Business One environment supported live retail operations. It included interfaces, scheduled tasks and add-ons, and had dependencies on connected systems including retail checkout, a promotions engine and a loyalty platform.
An upgrade could not be treated as an isolated technical change. Each dependency needed to be understood and tested, two suppliers needed to work to one coordinated plan, and stores needed a practical way to continue operating during the live deployment.
What I Did
Six steps, in this order
Planned and mapped dependencies
Planned the upgrade and mapped the operational dependencies across the connected environment, covering interfaces, scheduled tasks and add-ons.
Built a structured test plan
Created a test plan covering the connected environment, not just SAP Business One in isolation, so that interactions between systems were validated.
Aligned two suppliers on one plan
Coordinated two third-party system suppliers around a single deployment plan.
Assessed risk and set mitigations
Assessed the risks across the deployment and put practical mitigations in place before committing to a live change.
Tested before go-live
Tested and evaluated the change across the connected environment before live deployment, rather than discovering issues during it.
Kept stores trading
Used the retailer's offline capability to maintain store operation while the live system was upgraded, giving stores a tested route to keep serving customers.
Results
What changed
The upgrade was completed with stores still trading
The SAP Business One upgrade was completed while retail stores continued to trade using offline capability. This was not a claim of zero downtime. The live system was being upgraded, but the operating plan gave stores a tested route to continue serving customers during that period.
Dependencies were tested, not assumed
Interfaces, scheduled tasks and add-ons across connected systems were identified and tested before go-live rather than being discovered during the deployment.
Two suppliers worked to one plan
Two third-party suppliers were aligned around a single coordinated deployment plan, removing the gaps and hand-off risks that arise when suppliers work to separate schedules.
Continuity was built in, not bolted on
Operational continuity was designed into the deployment approach from the start, rather than being left as a last-minute workaround. The result connected technical delivery with the realities of retail trading.
Facing a complex systems change?
Let's make sure the operational dependencies aren't left to chance.
If an ERP, retail or integrated-system change has dependencies that can't be left to chance, I can help you review the deployment and continuity plan before you commit to it.