1 · Freeze the launch scope

List only what must be live for the first complete visitor journey. That may be a single-page creator home, a portfolio, a resource hub, a service/contact site, a store, or a combination. Do not add products, subscriptions or complex features simply because Shopify can support them.

• Primary domain or launch URL identified.
• Required launch pages identified.
• Main visitor route and primary next action identified.
• Optional post-launch work moved to a later queue.

2 · Carry forward the brand and message

Use the identity, audience, message and public-language decisions already made in Modules 5–8. Do not restart branding because you reached Shopify.

• Creator/project identity is consistent.
• Page copy matches the intended audience and point of view.
• Claims, prices, deliverables and boundaries are accurate.
• Visual choices support recognition and readability rather than replacing strategy.

3 · Verify Shopify ownership and dependencies

Confirm the operational controls established in Module 9: domain/registrar authority, Shopify admin ownership, billing responsibility, recovery method, renewal responsibility, essential apps and any external services. Do not store passwords or recovery codes in a public worksheet.

4 · Test the visitor journey

Open the public-facing experience as a visitor, not only from the Shopify admin or theme editor. Test on desktop and mobile.

• Navigation reaches the intended pages.
• The primary CTA leads to the correct destination.
• Contact, signup, download, booking or checkout works if used.
• Confirmation and delivery/follow-up make sense.
• No required page depends on an unpublished theme, preview URL or admin session.

5 · Check trust and policy essentials

Use only the policies and disclosures relevant to what the site actually does. Commerce may require additional shipping, refund, payment or fulfilment information; newsletters and forms require appropriate consent/privacy handling. Record legal questions for qualified review rather than making unsupported compliance claims.

6 · Check products and delivery only if they are part of this launch

If the site sells or distributes something, verify the complete path from offer page through action, confirmation and fulfilment. If the creator is launching a portfolio, information site or contact path instead, skip this branch.

• Public description matches the actual deliverable.
• Price/free terms and access duration are accurate.
• Checkout or signup is tested where applicable.
• Download, member access, booking, service or shipping route works.
• Support/correction path is visible.

7 · Check discovery and measurement

Confirm the page titles, navigation and internal routes established in Module 11. Make sure the basic measurement layer can observe the journey you intend to launch. Do not delay launch to build an elaborate analytics system.

8 · Run the final public preflight

• Domain resolves to the intended live experience.
• Core pages load without obvious errors.
• Mobile text, buttons and forms are usable.
• Images/media load and have useful context or alt text where appropriate.
• Broken links and wrong destinations are corrected.
• Primary continuation path works end to end.
• A basic measurement signal can be recorded.

Free supporting checklist

The existing Bee Righteous Pre-Launch Checklist remains available as an optional Wix/Shopify implementation aid. Use it only where it matches the current build; the canonical completion standard is Module 12.

Open the Free Pre-Launch Checklist

Stage 3 APPLY Path · Return to Module 12

Educational implementation support. No traffic, sales, monetization or business outcome is guaranteed. Verify current Shopify pricing, product features, platform policies and any legal/tax requirements from appropriate current sources before relying on them.