Pre-launch checklist

Use this as a final walk-through after the detailed guides. A tick is a reminder to verify something, not an automatic readiness claim.

Store and scope

• The intended product, variant, collection, or storefront scope is selected.
• Product availability and inventory are suitable for the launch.
• The schedule and timezone are correct and still in the future where required.
• Your plan has sufficient launch, entry, waiting-time, email, and simultaneous-room allowance for the intended use.

Theme and shopper journey

• The protection embed is saved in the intended theme.
• The optional signup form is on the correct product template.
• Countdown, waiting, admitted, and other configured messages are readable on desktop and mobile.
• The actual storefront journey was tested, including reconnect and supported checkout.
• Admission messaging does not promise reserved stock or a guaranteed purchase.

Access and protection

• Admission order, rate, active limit, checkout window, and queue capacity match the intended launch.
• Any invite-code, priority, or enabled customer-tag path was tested with both allowed and rejected entries.
• Inventory thresholds and per-order limits match the protected scope.
• The Bot Protection default/override and checkout failure mode are understood.
• Progress messages and inactivity/reconnect settings suit the shopper journey.

Notifications, if used

• A monitored reply-to address is saved.
• Sender verification, sending preference, list state, and subscriber eligibility were each checked.
• Subject, copy, destination, and consent purpose match.
• Store defaults versus list overrides and the availability/opening/admission trigger are correct.
• A controlled test covered receipt and the message’s unsubscribe path.
• No test data or unintended recipients remain in the intended audience.

Launch operation

• Someone is responsible for watching the room and responding to issues.
• That person understands pause, resume, recovery, and the appropriate end action.
• Support details and the planned response to a launch issue are available.
• The app’s final publication checks pass and its resulting state was verified.

If a check fails, fix that item before proceeding. Start with troubleshooting or contact support.