Launch Checklist

Run this checklist before connecting ads, announcing a new site, or pointing a production domain at a workspace.

Identity And Access

This section proves the team is operating in the right tenant with the right public identity. Do not proceed if workspace selection, team access, currency, timezone, or visible test data is uncertain; those mistakes can spread into orders, bookings, notifications, and reporting.

Domain And Email

• Domain resolves to the intended site.
• DNS records are verified.
• Email sender identity is configured.
• Critical notifications use the right sender and reply-to path.
• Email preference and unsubscribe links work.

Verify domain and email from the customer’s final URL and final inbox experience. A preview route can look healthy while production DNS, sender authentication, reply-to routing, or customer email links still point at the wrong host.

Payments

• Stripe Connect account is connected and requirements are clear.
• Checkout and tax settings are intentional.
• Product checkout works.
• Booking deposit or final-payment link works if enabled.
• Invoice send, refund, cancellation, and manual-payment recording have been tested where applicable.
• Apple Pay or other wallet domain requirements are satisfied when those wallets are enabled.

Products

• Products have titles, descriptions, prices, images, variants, inventory, tax, shipping, and SEO.
• Collections and navigation expose the right products.
• Out-of-stock, archived, and unavailable products behave correctly.
• Cart and checkout totals match the console.

Test at least one product that represents the riskiest launch path: variants, discounts, tax, shipping, inventory, and checkout provider behavior. A simple product can pass while the product customers actually buy still fails because a required option, package dimension, or tax rule is missing.

Record the tested product, cart total, shipping result, checkout boundary, and order state. That record becomes the support reference if launch traffic reports a pricing, inventory, or fulfillment issue.

Services And Bookings

• Services have duration, buffer, staff, location, pricing, tiers, add-ons, and waivers.
• Availability shows real bookable times.
• Deposits and payment timing are correct.
• Confirmation, reschedule, cancellation, pay-link, and calendar flows work.
• Calendar sync status is visible for connected providers.

Customer Portal

• Customer sign-in works.
• Orders, bookings, billing, tickets, saved items, profile, and notification preferences are reachable.
• Sensitive pages require authentication.
• Guest checkout or guest booking can be claimed when that workflow is expected.

Portal checks protect customer trust after the first transaction. Use a test customer with at least one order or booking so the team can confirm that history, billing, tickets, and profile data are scoped to the correct workspace and customer.

Content And Discovery

• Homepage and major pages are complete.
• Policies are published.
• Stories and help content are ready if enabled.
• Forms submit to the correct console surface.
• Sitemap, robots, Open Graph image, and llms.txt are correct.
• Redirects and short links are tested.

Integrations

• GA4 Measurement ID is valid if analytics is enabled.
• Google Ads Conversion ID and optional conversion label are valid if ads are enabled.
• Cookie consent state matches analytics and ads posture.
• Google Business Profile is connected if reviews are synced.
• Calendar integrations are connected if bookings sync externally.
• Shipping provider settings are complete if labels are bought through the console.

Operational Readiness

• Team knows where to watch: Insights, Sales, Scheduling, Customers, Inbox, Products, Shipping, and Payments.
• Support inbox is monitored.
• Refund, reschedule, cancel, and no-show policies are understood.
• A rollback plan exists: set site to draft/protected, pause ads, disable checkout, or disconnect conversion tags as needed.

Operational readiness is the difference between a site that can accept traffic and a business that can respond to it. Assign owners for the first day: payments, bookings, orders, forms, inbox, domain/email, ads/analytics, and customer support. Each owner should know the console surface they watch, the alert or report they trust, and the first rollback action for their area.

Before launch, write down the narrow rollback plan. Examples: hide one product collection, disable one booking service, pause Google Ads, disable checkout, switch site status, pause an automation, or remove a broken navigation link. Narrow rollback keeps the working parts of the workspace live while the team fixes the failing path.