Product options: trace the selection from the catalog to the order

The order and the buyer's account are two reports

The buyer can remember one option while the order shows another. Either report can be incomplete. The comparison uses the order's own line, the confirmation the buyer received, and the variation as it exists now. Where those three disagree, write the disagreement. Do not pick the version that is easiest to fulfill.

This page stops at the catalog identity of the option. It is not the page for a parcel that contained a different physical item after the order was correct, and it is not the page for search results that never opened this product. Inventory that changes between the cart and checkout is a different fact. Here the question is which published option the order names.

A WooCommerce variation is its own record

WooCommerce's variable-product documentation says each variation can have its own SKU. If the parent has an SKU and the variation's SKU is left blank, the variation uses the parent SKU. Two options can then look identical on an order that shows only the SKU. The label the customer selected, not the shared SKU, is what distinguishes them.

On the storefront, the customer selects each required option, and the page updates to that variation's price, image, and availability before it can be added to the cart. The same documentation says that if you set default form values, a variation is already selected when the page opens, and the shopper can add it without making a selection. A buyer who says they did not choose an option may have added the default. The default is a catalog setting you can read. It is not proof of what the buyer intended.

The documentation uses ordinary retail examples to explain the controls. Those examples are not your catalog. Your labels are the words on your variations. Do not rename an option to describe a use, a person, or an outcome.

Some catalog setups select a different variation than the screen suggests

WooCommerce says that a variation set to "any" value for an attribute can act as a fallback, and that the store uses the first match from the top of the sorted variation list. If a broad "any" variation is sorted above a specific combination, the specific combination is never used. Price, stock, and the label can then come from the fallback. The documented remedy is to define every attribute on every variation, or to sort specific combinations above the fallback and test the result.

When a variable product has more than 30 variations, the same page says the dropdowns no longer limit themselves to available combinations. An unavailable combination shows the message that no products matched the selection and asks the customer to choose a different combination. That message means the selection was not added. It is not an order line. Do not treat that error as the option-mismatch this page is about.

Attribute order on the product page follows the order saved in the admin. Changing that order changes what the customer sees. It does not rewrite orders already placed.

What you can correct, and what the old order still says

You can change a blank SKU, remove a default you do not want preselected, sort specific variations above an "any" fallback, and make two labels distinct. You can read the option text on the order, the cart if it still exists, the confirmation, and the fulfillment note, and see whether they name the same label.

You cannot treat today's variation screen as the option that was stored if the catalog changed after the order. You cannot decide from this page that a payment provider chose the variation. The provider charges the order it was sent. Which label was sent is in the store's order. If the admin screen does not show a product or variation identifier, leave that cell blank rather than copying an identifier from a different system.

A Prism consultation can discuss a catalog question you describe without customer names or order dumps. Confirm any catalog-editing scope separately; a consultation alone does not authorize a refund. Scope, fees, and terms are discussed before work. What remains unknown is a checkout customization this WooCommerce document does not describe. If the store is not WooCommerce, use that platform's variation documentation and leave the WooCommerce rows blank.

Option-label map

Use one real order. Copy labels from the screens. Do not invent an identifier, a SKU, or a product. If the catalog was edited after the order, say so instead of treating today's variation as the historical one. Worksheet entries are not submitted by this worksheet or saved by this site. Use only non-sensitive summaries; do not enter credentials, government identifiers, card or bank-account numbers, private receipt links, or customer details.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. The consultation form does not include these entries.