# Shopify Checkout / Revenue QA Sample

This is a sanitized sample of the handoff format for a focused Shopify, Shopify Plus, checkout, cart, tracking, or post-launch QA pass.
It is not a client deliverable and does not contain private store data.

## Input

- Target: Shopify or Shopify Plus storefront, theme preview, checkout flow, cart drawer, app stack, or post-launch issue
- Reported issue: checkout drop-off, broken discount, missing shipping/payment option, tracking mismatch, Klaviyo event gap, app conflict, mobile bug, or unclear post-launch regression
- Available material: staging/theme preview URL, product or test order path, screenshots, app list, browser error, analytics symptom, exported event sample, and expected result

## QA Pass

1. Reproduce the revenue-adjacent flow with a safe test product, theme preview, staging store, or guided owner session.
2. Capture browser console errors, failed network requests, visible cart/checkout states, event payload symptoms, and screenshots.
3. Isolate likely failure source: theme JavaScript, cart drawer logic, discount rule, shipping profile, payment visibility, Checkout UI extension, app embed, tracking pixel, Klaviyo event, localization, or mobile layout.
4. Apply a focused safe fix when the scope allows it, or produce a precise change plan when store-owner credentials, payment configuration, tax/legal settings, or irreversible production changes are required.
5. Validate the same flow again and leave a short handoff with what changed, what was tested, and what still needs owner confirmation.

## Checks

- Product page, variant selection, add-to-cart, cart drawer, quantity updates, coupon/discount behavior, and checkout handoff
- Shopify Functions, Checkout UI extensions, app embeds, app blocks, theme app extensions, and post-purchase/thank-you-page changes where relevant
- Shipping/payment visibility, inventory edge cases, localization/currency, gift cards, subscriptions, bundles, and free-shipping threshold logic
- Klaviyo, analytics, web pixels, Meta/Google tags, server-side events, and event naming consistency using safe test events
- Mobile Safari/Chrome layout, console errors, network failures, slow assets, stale scripts, and broken theme interactions
- Webhooks, order status, email/event triggers, fulfillment handoff, and admin-side status mapping when the owner provides safe access or exports

## Output

A useful first pass should produce one of these:

- a focused fix for the isolated cart, checkout, theme, tracking, or app conflict;
- a reproducible QA report with screenshots, console/network evidence, and likely root cause;
- a safe theme/app/config change plan ready for owner review;
- a tracking/event sanity report with sample payloads, missing events, and next checks.

## Acceptance Check

Run the same flow after the change:

- the same product, discount, cart, checkout, tracking, or test order path reaches the expected state;
- browser console and network output are captured for the final pass;
- expected Klaviyo/analytics/pixel/order/admin event appears or the missing owner-side step is named clearly;
- rollback notes and untouched settings are listed so the owner can keep or revert the change safely.

## Boundaries

- No destructive production checkout, payment, shipping, tax, legal, or payout changes without explicit owner approval.
- No stored credentials, cookies, recovery codes, card data, tax data, bank data, or payout information.
- No CAPTCHA bypass, hidden scraping, account abuse, or attempts to bypass Shopify/app/platform controls.
- Store-owner actions such as login, 2FA, paid apps, payment setup, KYC, tax, legal, billing, and final production approval stay with the human account owner.

## Handoff

Deliverables for a first pass:

- issue summary and likely root cause;
- exact theme files, app settings, checkout extensions, events, or test paths reviewed;
- screenshots, log snippets, console/network notes, or safe event samples used as evidence;
- acceptance check result;
- remaining risk and what needs real owner access, production confirmation, or app/vendor support.