Before you start
Done when: one person owns the launch, a target date is set, the payment application is submitted, and you know where your data is coming from.
Set up the foundation
Done when: your business details, locations, taxes, attributes and users are in place. Nothing is imported before this is true.
Bring in inventory and catalog
Done when: your stock is registered and a listing shows real availability for a real date.
Make it sellable
Done when: payments are connected, a checkout is attached, and your terms, documents and emails carry your details.
Shape the storefront
Done when: the storefront looks like you and reads in your customers’ language. Never hold a launch for this step.
Test end to end
Done when: a real order has gone through checkout, landed in a real inbox, and been refunded and returned.
Train your staff
Done when: each person can do their own job in the admin without help.
Go live
Done when: the domain points at TWICE, the first real order is verified, and the old system has stopped taking new bookings.
First weeks live
Done when: you can read your own numbers and know where to go when something looks wrong.
What this path is not
It is not a reference. Its guides are written for the launch job and stop there — enough to get you live, not everything the product can do. For the full detail on any one area, and for the day-to-day tasks that come after launch, see Working in TWICE in the sidebar. Where a launch guide is still being written, the step says so and points at the reference pages that cover the same ground in the meantime.Related articles
TWICE Commerce overview
What TWICE Commerce is and what it is for.
The TWICE approach
How the system is modelled, and why it is shaped this way.
Glossary
Every term used across these steps, defined once.