The order record says “navy.” The customer says the product page showed a cream item when they clicked buy. Both may be reporting what they saw. Your first job is to reconstruct the path, not to assume that the customer misread the option or that the site selected the wrong variant.
Shopify merchants have described variant and gallery mismatches and selector/image disagreement. Shopify's variant documentation clarifies how each option combination is recorded. These sources show a real class of issue, but they do not identify the cause on your store. This article is about what the store can prove after an order. If a fresh test adds the wrong variant to cart, document that prepurchase failure separately from the customer's existing order record.
Preserve the order evidence first
Record the order number, product URL, selected option text, SKU, cart line, checkout line, confirmation email, and fulfillment pick record. Save the relevant screenshots with a timestamp, but remove customer details before sending them to an outside developer. If the buyer provided a screenshot, note when it was taken; the product page may have changed since the order.
Then test the same product on a phone and desktop. Select each relevant color or size and watch the image, label, price, availability, URL, and cart line. A product image can be merely illustrative, but if it changes to represent the selected option, the relationship should be consistent. A mismatch can come from media assignment, theme behavior, a third-party app, caching, or a fulfillment mapping. The evidence chain narrows the possibilities.
Decide which promise the buyer saw
Read the visible option label and the photo together. Was the label clearly next to the purchase button? Did the image change before or after selection? Did a thumbnail show one item while the full image showed another? Did the cart and confirmation make the chosen variant explicit? If the only clear record appears after payment, the page leaves too much work to the buyer.
For customer support, avoid asserting the site was correct solely because the database recorded a SKU. Likewise, a buyer screenshot alone does not prove the final cart state. Explain what you have verified, resolve the individual case under your existing policy, and separately fix the page if it can mislead another buyer.
Turn a complaint into a release test
Create a small matrix for every affected product: option chosen; image shown; text label; cart variant; order variant; fulfillment SKU. Test the matrix after theme, app, or catalog changes. If it fails, pause promotion of that product until the purchase path is dependable. Keep the test focused on the affected SKUs first rather than rebuilding the entire store without evidence.
ARCHV can review the page-to-cart explanation and scope a commerce QA project. Theme code, product data, apps, and fulfillment integrations require custom discovery. Send the affected URL and a redacted order trail through the website estimate; describe which step disagrees with the shopper's expectation.