QA and Launch Checklist

Complete this checklist in the same build that will be promoted.

Eligibility and catalogue

• [ ] The experience appears only on approved products.
• [ ] Every enabled product maps to the correct garment and variant.
• [ ] Garment states are Ready before launch.
• [ ] Disabled and unsupported products have a normal shopping path.

Functional

• [ ] Try-On opens and completes on a representative product.
• [ ] Sizing returns the expected interface when included.
• [ ] Variant changes send the correct identifier.
• [ ] Add to Cart uses the retailer’s existing cart behavior.
• [ ] Back, close, Escape, and outside-click behavior are predictable.
• [ ] A failed or unavailable experience does not block checkout.

Browser and device

• [ ] Current Chrome desktop and Android.
• [ ] Current Safari desktop and iOS.
• [ ] Current Edge desktop.
• [ ] Representative small and large mobile layouts.
• [ ] Slow network and first-load behavior.

Accessibility

• [ ] Entry points have accessible names.
• [ ] All controls are keyboard reachable.
• [ ] Focus moves into and returns from the experience correctly.
• [ ] Focus is visible.
• [ ] Text and controls meet the retailer’s contrast requirements.
• [ ] Reduced-motion behavior remains usable.

Visual quality

• [ ] Color and texture are faithful.
• [ ] Logos and patterns are not distorted.
• [ ] The correct product and variant appear.
• [ ] The experience fits the brand’s product-page hierarchy.
• [ ] The brand has approved the representative results.

Performance and observability

• [ ] Product-page loading was measured before and after integration.
• [ ] The experience is not initialized more times than intended.
• [ ] Analytics events fire once per action.
• [ ] Logs redact credentials and customer imagery.
• [ ] A support runbook identifies the environment, owner, and rollback path.

Go live

• [ ] The staged build passed QA.
• [ ] The exact garments to enable are listed.
• [ ] The publishing owner and launch window are confirmed.
• [ ] The prior theme or build remains available for rollback.
• [ ] Monitoring is active after release.
• [ ] The live URL is checked on a new browser session after promotion.