Know what must be true before a storefront carries real customer journeys.

Products and collections

• Name the source of truth for products, variants, attributes, media, and availability
• Identify the collections and filters customers actually use
• Record missing, uncertain, duplicate, or restricted product data

Customer journeys

• Map verified purchase, request, pickup, visit, and staff-help paths
• Name where staff confirmation or policy review is required
• Separate desired booking, rental, POS, or account features from accepted capabilities

Content, brand, and accessibility

• Inventory required product, collection, policy, service, and company content
• Name approved brand assets and meaningful alternatives
• Plan keyboard, focus, zoom, reduced-motion, heading, and responsive checks

Operations, migration, and ownership

• Assign owners for catalog, content, requests, publication, and support
• List source systems and data types that need separate migration assessment
• Define approval, denial, recovery, and rollback paths before launch

Evidence: A useful readiness record names sources, owners, unknowns, boundaries, and the smallest private preview that can test the workflow.

Boundary: Completing this checklist does not approve public provisioning, payment activation, provider changes, DNS, tenant publication, or a launch.

Readiness checklist questions

• Do we need every answer before planning? No. Unknowns should be explicit and assigned.
• Does readiness mean StoreMason is live? No. Readiness supports a bounded planning decision.
• What happens next? Review the smallest private preview and agree on acceptance evidence before commitment.