Shopify Product Variant QA: A Pre-Publish Checklist
Keep Shopify listings accurate with source-of-truth fields, change approvals and checks for variants, images and stock before updates go live.
Check each sellable option combination against an approved source before publication.
The check must cover the SKU, option values, image, price, availability, and supporting evidence. A correct product page can still contain one incorrect variant.
Build the variant audit matrix
Use one row for each variant.
| Field | Source value | Shopify draft | Result | Evidence |
|---|---|---|---|---|
| Option 1 | Approved value | Draft value | Pass or fix | Catalog row or approval |
| Option 2 | Approved value | Draft value | Pass or fix | Catalog row or approval |
| SKU | Approved SKU | Draft SKU | Pass or fix | Inventory source |
| Image | Approved asset | Draft image | Pass or fix | Asset ID |
| Price | Approved price | Draft price | Pass or fix | Price approval |
| Availability | Approved state | Draft state | Pass or fix | Launch plan |
Shopify treats each option combination as a variant. Variant-level settings can include price, inventory, shipping details, images, SKUs, and barcodes. See Shopify's variant guide.
Use this pre-publish checklist
Product structure
- The option names match the approved naming system.
- Every approved option value exists.
- No unapproved option value exists.
- Every required combination has one variant.
- No exact duplicate combination exists.
Variant identity
- Each SKU matches the source record.
- The SKU is not copied to a different sellable item.
- The barcode matches the source when one is required.
- The variant title is clear on the storefront.
Customer-facing values
- The price matches the approved price source.
- The image shows the selected variant.
- The availability state matches the launch plan.
- The selected options remain visible in the cart.
Evidence and approval
- Each correction links to its source.
- A reviewer approved changes with business impact.
- The reviewer is different from the editor when policy requires separation.
- The final check time and reviewer are recorded.
Walk through a small illustrative catalog
Assume a shirt has two colors and two sizes.
| Variant | SKU | Image | Price | Availability |
|---|---|---|---|---|
| Blue / Small | SH-BLU-S | Blue shirt | $30 | Available |
| Blue / Large | SH-BLU-L | Blue shirt | $30 | Available |
| Green / Small | SH-GRN-S | Green shirt | $30 | Available |
| Green / Large | SH-GRN-L | Green shirt | $32 | Draft only |
This is a fictional example. It does not describe a Stealth Agents client.
The matrix shows one business-impact exception. The Green / Large variant has a different price and is not ready for sale. The editor must verify both facts before publication.
Recheck the storefront
The admin record is not the final view.
- Open the product on the preview storefront.
- Select each option combination.
- Confirm the image and price change correctly.
- Add each approved variant to the cart.
- Confirm the selected options and price in the cart.
- Record the preview URL and check time.
Keep the scope narrow
This checklist does not write listing copy. It does not reinstate marketplace listings. It also does not reconcile warehouse inventory.
See the product listing virtual assistant guide for broad listing support. See ecommerce operations support for recurring store work.
If the catalog has many approved changes, an assistant can maintain the audit matrix. The store owner must retain price and publication authority.