Before you start

Settle these six decisions before you open the admin. Each one is cheap to make now and expensive to revisit in week six.

​

Name one person to own the launch

Name one person, not a department. Tell the team who it is. That person holds the date, answers the questions that come back, and decides when something is good enough to go live. Everyone else contributes a part.

​

Pick a date outside your season

Pick the date, then check it against your busiest weeks. Launch before your season starts rather than during it. Then work backwards, so anything the check finds is fixable without moving the date:

​

Start the payment application today

Start your payment provider application today, before you configure anything. Have ready: company documents, beneficial-owner identity, and bank details. Connect payments is step 2 and covers the wait and what it gates. See Payments for the providers.

​

Pick one source for your data

Pick one of these three, and do not mix two halfway through. Mixing sources is how duplicates happen. Decide at the same time how long your old system stays readable. Deposits and rentals already out have to settle somewhere, so the old system usually stays open for reading long after it stops taking orders. Read stock items and SKUs first, because the words do not mean what they meant in 1.0, then the glossary.

​

Check which plan you are on

Read Check what your plan includes, and write down the counts your agreement names before anyone creates a second location. Your plan sets what the account can do and how locations are billed. A few later steps depend on capabilities that are tier-gated, and what counts as a billable location is not always what people assume.

​

Decide who owns admin access

Name the person who owns admin access on your side. If your team signs in with Google or Microsoft accounts, name the person who administers that directory too. Raise it now, because half of it is not yours to do. Creating a group or agreeing who approves an access request goes through an IT department on its own timetable, and nobody at TWICE Commerce can reach your directory. Read Decide who owns admin access for the boundary between the two systems, and what to agree before you restrict how people sign in.

​

Done when

• One named person owns the launch, and the team knows who.
• The date is set, outside your busiest weeks, with training and the pre-launch check booked back from it.
• Your payment provider application is submitted.
• You have picked one data source and know how long the old system stays readable.
• You have your plan’s location and capability counts written down.
• Admin access has a named owner, and so does the directory your team signs in with.

​

Related articles