Review and launch your product

Answer four launch questions#

A launch is ready when the content, public invitation, checkout and delivery agree. Product Overview explains the next action. Launch review is the separate place to resolve required-content checks, inspect delivery, approve the exact saved version and publish delivery. Price & access owns commercial terms and checkout availability; Sales page owns the public invitation.

• Content: is the product useful and approved for the intended audience?
• Public page: does the published invitation show the right offer and media?
• Checkout: are payment setup, price, currency and renewal terms ready?
• Delivery: can an entitled customer reach the correct content or service?

Open the exact repair action#

In Price & access, Before you start selling explains each unmet requirement and gives a repair action. Set price opens the product’s price settings; Finish seller setup opens your account’s payment setup. These are different tasks.

Fix required content opens the first missing content location. Review this version and Review & publish delivery open Launch review. Meeting and availability actions open the relevant service settings. After a repair saves, return to Price & access and recheck what remains. Server checks still run before selling is enabled.

1. 1

   Save your current draft.

2. 2

   Resolve required content in Launch review and inspect the delivery preview.

3. 3

   Record editorial approval for the exact saved version, then explicitly publish delivery.

4. 4

   Review price, payments and service availability in Price & access, then explicitly start selling.

5. 5

   Publish the intended Sales page separately and inspect the signed-out buyer route.

Publication and selling are different#

Publishing page changes updates the public design. Publishing or reviewing product delivery sets the content customers receive. Starting or pausing new sales controls checkout availability. These actions have different effects on existing customers.

Read the review summary before updating a live product. Some changes can pause new sales until the offer is reviewed again; do not assume editing a draft immediately changes the public offer.

Use simulation for inspection#

The buyer journey check can validate internal relationships and render sample access without charging a card. It does not create a real order, grant access, send email or prove a provider webhook completed.

Use View as member to inspect the delivery interface. Use the page preview to inspect the invitation. Neither replaces a controlled payment test.

Verify a controlled buyer lifecycle#

Use an approved sandbox to test successful and failed checkout, duplicate or delayed payment events, receipts, access, return login, cancellation, refund and access end. Keep live charges separate from test mode.

Before sharing, open the canonical public page as a signed-out visitor. Confirm that public copy is visible while paid lessons and files remain protected.