Should I roll out an ERP in phases or all at once?

Phased rollout or big-bang go-live? How small D2C brands can sequence ERP modules and channels to reduce risk while getting value early.

Anadoris Digital · · 4 min read

Pure white stairway
Photo: Liane Metzler / Unsplash (CC0)

A big-bang go-live switches every process to the new ERP on the same day. A phased rollout moves processes or locations across in stages. Each approach has supporters, and each can work. For small D2C brands with lean teams and daily dispatch commitments, the balance usually favours phases.

The reason is simple: small teams cannot absorb many changes at once while also shipping orders. Phasing spreads the learning and limits the damage if something goes wrong.

A typical phase plan for a D2C brand

  • Phase one: item master, warehouses, inventory and purchase orders to manufacturers and suppliers.
  • Phase two: sales channel integrations, order processing, invoicing and returns.
  • Phase three: accounting, either full migration or a reliable link to Tally.
  • Phase four: reconciliation of marketplaces and COD, reporting and dashboards.
  • Later: batch-level analytics, demand planning, approvals, portals and automation.

The order can change. A brand whose biggest pain is overselling may put channel integration in phase one. A brand with batch-controlled products may need batch tracking from the very start. The principle is to tackle the foundation and the biggest pain first.

Advantages of phasing

  • Each phase is smaller, so it is easier to test and train.
  • Problems are found and fixed before the next phase builds on them.
  • The team sees value early, which builds confidence.
  • Budget and effort can be spread over time.
  • Lessons from early phases improve later ones.

Drawbacks to manage

Phasing means running some processes in the new system and others in the old one for a while. That creates temporary interfaces, such as exporting invoices from the ERP to Tally until accounting moves. Keep these temporary links simple and well documented, and set a target date for each phase so the in-between period does not become permanent.

Phasing also needs sustained attention. A project that stalls after phase one leaves the business with half a system.

When big-bang can work

A single go-live can suit a very small operation with few SKUs, one warehouse, one or two channels and a team that can dedicate time to the switch. It can also make sense when the old system is being switched off on a fixed date and running two systems is not possible. Even then, rehearse the go-live with real data first.

Phase readiness checklist

  • Scope of the phase is written and agreed.
  • Data for the phase is cleaned and test-imported.
  • Users have been trained on their own scenarios.
  • A rehearsal or parallel run has been completed.
  • Temporary links with old systems are tested.
  • Go-live date avoids sales events and festive peaks.
  • Support is available for the first weeks after the phase goes live.
  • Success measures for the phase are defined.

Phasing by location or channel

Another option is to phase by location or channel rather than module. For example, move one warehouse or one channel to the new system first, then add others once it runs smoothly. This works well when the full process must change together but the business has natural divisions.

Combining both is common: phase one covers inventory and purchasing for the main warehouse, phase two adds channels and the 3PL, and so on.

Avoid starting any phase in the weeks before a major sale or festive season. The time saved by rushing is small compared with the cost of disruption during peak demand.

Deciding when a phase is finished

A phase is not finished when the system goes live. It is finished when the team trusts it. Set simple measures for each phase before it starts. For an inventory phase, that might be stock accuracy on counted SKUs and no parallel spreadsheets in use. For a channel phase, it might be orders imported without manual fixes and no oversells caused by sync.

Only start the next phase when the current one meets its measures for a few weeks in a row. Starting early piles new change on an unstable base and makes it hard to tell which phase caused a problem.

Keep a short log of issues and decisions for each phase. It becomes the training material for new staff and a record of why the system works the way it does, which is useful when the next phase raises the same questions.

Share progress with the whole team at the end of each phase, including what improved and what is still being fixed. People are more patient with the next round of change when they can see that the last one made their work easier.

Where to start

  • List your processes and rank them by pain and dependency.
  • Group them into three or four phases.
  • Set target months for each, avoiding peak seasons.
  • Define what success looks like for phase one.
  • Start phase one with a small, well-prepared scope.

Anadoris Digital usually plans ERP projects in phases and can help sequence modules and channels to suit your peak seasons and team capacity.

Related service: ERP Solutions · More on this topic: ERP Solutions articles

Common questions

How long should each ERP phase take?

It depends on scope, data quality and team availability. Keep each phase small enough to complete, test and stabilise before the next begins. A phase that keeps growing is a sign that scope needs to be split.

Can I run the old and new system in parallel?

Yes, for a short period, to compare results and build confidence. Running both for too long doubles the workload and creates confusion about which is correct. Agree a parallel period and a clear switch-off date.

What should always be in the first phase?

A clean item master and accurate inventory, because nearly every other process depends on them. Purchasing usually belongs in the first phase too, since it changes stock and is often a major pain point for brands using contract manufacturers.

Your next chapter

Let’s build what comes next.

A new website. A better system. A simpler way to work. Tell us where you want to begin.

Discuss your project