Run both systems until 1.0 is finished

Run both systems until 1.0 has nothing left in it. Keep fulfilling pre-switch orders in 1.0, and take everything from the switch onward in 2.0. Plan for longer than you expect. Your longest-dated booking decides how long this runs, not you: bookings a season ahead keep 1.0 open a season, and a catalog fulfilled at the point of sale closes it in days.

​

Working 1.0

Fulfil collections, returns, extensions, cancellations and refunds for pre-switch orders in 1.0. Release deposits in 1.0, from the 1.0 order. Treat bookings dated after the switch as 1.0’s. Fulfil a customer who booked in 1.0 for a date next month in 1.0 on that date, even though 2.0 has been live for weeks by then. Do not re-enter pre-switch orders in 2.0. Stock that is out on a 1.0 order is not available in 2.0, so block it there with an internal reservation if you need accurate availability.

​

Watching 2.0

For the agreed period after the switch, check daily:

• Every order received its confirmation email.
• The day’s collections and returns match what actually happened at the counter.
• Payouts arrive, and the amounts are correct.
• Whether anyone is working around the system. Treat a workaround as the most useful signal you have. It is a defect report from someone too busy to file one.

Hold the scheduled check-in with TWICE for the agreed period. Bring the workarounds.

​

Closing 1.0

Keep 1.0 readable until all of these are true:

• Every pre-switch order is closed.
• Every deposit taken in 1.0 is released or charged.
• Every refund owed on a 1.0 payment is handled.
• Finance exports and retained records are stored outside TWICE.
• Your accountant has confirmed they have what they need.

​

Common questions

Your 1.0 and 2.0 admin live at the same address. Switch between them with the two-arrows icon in the top right of the admin.

​

Related articles