Go-live checklist

Going live is one click on a domain. This list is what has to be true before the click. Each item is a question with a yes-or-no answer; if you cannot answer yes, the link is where you go. The long version, screen by screen, is Pre-launch checks.

ERP connected?

The order that a buyer places at 22:14 has to be in your ERP by the morning without anyone typing it, and the article that was discontinued yesterday has to be gone from the shop. That is what "connected" means: articles, stock and list prices flowing in, orders flowing out, on a schedule someone has watched for at least a fortnight. Open Integration Studio › Runs and read the last two weeks: every nightly run present, record counts in the usual range, no run that succeeded with zero records. Then confirm a test order reached the ERP and came back acknowledged. If you have no connection yet, decide which system owns which field first, because an integration built before that decision maps every field twice. See Monitor your syncs and Deciding your system of record.

Product data ready?

Not "the catalog is done". The specific completeness number for the channel and locale you are launching, read from the products list filtered on that channel. Below 100 % means articles that will not publish, or will publish with a blank where the pressure rating belongs. Spot-check ten products across different families for missing images, missing units of measure and untranslated names. If the channel is set to hidden until assigned, confirm products are assigned to it; an empty shop at launch is nearly always this. See Completeness and readiness.

Pricing verified?

A buyer who sees the wrong price does not file a ticket. They phone, get the right number by voice, and keep phoning. Resolve a price for at least one article in each market and confirm the currency and the net-or-gross basis. Sign in as one contract customer and confirm their price, not the list price. Read the price list grid once across: exactly one default, every customer list with an account under Applies to and Logged-in buyers only set, no two active lists with the same scope and priority, no entry at 0.00. See Check a price and Price list hygiene.

Customers imported?

Every company that may order exists as an organization with its ERP customer number, its price list code and its payment terms, and has at least one contact who may sign in. Companies with orders but no customer number are usually duplicates waiting to happen. If registration is open on the storefront, it is in approval mode with real notification addresses, because an empty recipient list means applications wait in a queue nobody knows about. Sign in as a standard customer and as a contract customer and confirm each sees their own assortment and terms. See Organizations and hierarchies and Self-registration.

Storefront live?

In Experience Studio › Sites, the Live column reads Yes, not Out of date. The domain's status is live, its certificate has a valid-until date in the future, http:// redirects to https://, and one of apex and www redirects to the other. Imprint, terms and privacy pages exist and are reachable from the footer; in Germany that is the cheapest thing on this list to get wrong expensively. Every page you intend to publish is published in every language the market serves. Open the shop on a phone. See Domains and going live.

Order flow tested?

One real order, placed by a real test contact on the real domain, through checkout with the delivery address, the payment method and the buyer's own order number, then found in Order Management › Orders, acknowledged, shipped and completed, with the confirmation mail arriving in the right language from the right sender. Then the partial case: ship six of ten and confirm the order reads in_fulfillment / partial and the open quantity is four. If the ERP is connected, confirm this order arrived there exactly once. See Process an order and Partial deliveries and backorders.

Then go live

Use Go-Live on the domain. Re-check the pricing and storefront items immediately afterwards, because the access protection coming off is exactly when a misconfigured price becomes public. Then put four screens on a weekly rotation: Sites for build status, the domain's certificate validity, Messaging for confirmations that stopped arriving, and Integration Studio › Runs. Add the search's zero-results list once a month; it is the only one of the five that tells you about revenue you are not getting.

Next

• Pre-launch checks: the same list, every screen.
• Launch a B2B shop: the full project this checklist ends.