Switch new orders to 2.0

Step 8 of migrating from TWICE 1.0. This is the switch itself. It is a short day if the previous seven steps are done, and a long one if they are not.

​

Set the date

Pick a date in your quietest trading period. Set the staff training date and the readiness check date before it, and move all three together if the date moves — a switch date that slips while the training date does not means staff trained on something they then wait a month to use.

​

Readiness check

One named person signs off, on a date, against every line below. Run it about two weeks out, not the day before: its entire value is that there is still time to fix what it finds. No-go is a normal and cheap outcome at that distance. Signed off by ____________ on ____________

• Every case in step 5 passed, unaided.
• Staff are trained.
• Settings are configured.
• Payments are connected, and a live-mode transaction is proven.
• Catalog and inventory reconcile against 1.0.
• The rollback condition is written down, and everyone knows who decides.

​

On the switch date

1. Close 1.0 to new orders — every channel at once: website, booking widget, phone workflow, and the counter. After this you only finalise existing orders in 1.0. All new orders are handled in 2.0.
2. Open 2.0 — store address live, links updated, payments in live mode.
3. Place a real transaction yourself and check the order, the payment, and the confirmation email. Do not wait for a customer to find the first problem.
4. Tell every person who can take an order that new orders go into 2.0 only.

​

Done when

• Every 1.0 intake channel is confirmed closed.
• 2.0 is open, on its live address, with payments in live mode.
• You have placed a real transaction and verified the order, the payment and the confirmation.
• Everyone who can take an order knows where orders go now.

​

Related articles