Manage product variants

Update the Wilson Running Shoe product to include three sizes and two colorways as variants: sizes 8, 9, 10 and colors Carbon and Sunburst. Set Carbon/9 as the default buy button combination. Enter SKU WIL-CR-9 for that variant, set inventory to 25, and make the Sunburst color backorderable with a restock date of August 3. Save and publish so the storefront reflects the default immediately.

Before I publish the new variant setup for the Wilson Running Shoe, make it easy for the merchandiser to approve: put price and inventory for the default variant up top, surface any variants missing SKUs or images, flag combinations that currently have zero inventory or conflicting weight/dimensions, and highlight if two variants share the same barcode. Suggest the minimal changes to avoid purchase errors during checkout.

I added size and color variants to the Wilson Running Shoe and set Carbon/9 as default, but two customers received Sunburst/9 instead. The warehouse says they picked the SKU on the packing slip; the site shows Carbon/9 at checkout. I don’t know whether the issue is on the frontend, variant mapping, or our fulfillment labels. What is the most likely cause and what immediate checks will tell me where to intervene so fulfillment stops shipping the wrong color?

Over the last five launches we’ve had recurring mistakes: wrong SKUs, duplicate barcodes, and missing variant images, which cause returns and slowdowns. I’m patching each by hand. Where in my variant creation and QA routine am I leaking accuracy, and what repeatable habit or checklist will prevent wrong SKUs and mismatched variant data from going live?