A default variation was added without the buyer choosing it

Separate a saved default from a buyer action

Open the product’s saved default form values and record each attribute exactly as named in the catalog. Then compare them with the selection displayed when the current product page first opens, before any option is changed. Record the URL and observation time. If no historical page observation exists, today’s configuration only establishes today’s default behavior.

WooCommerce’s variable-product documentation says defaults can make a variation available to add without a new selection. That means “I did not choose an option” can coexist with a cart containing a variation. The useful question is whether the store preselected that variation and whether the merchant intended it to do so. Do not treat the presence of an option in the cart as proof that the buyer actively chose it.

Trace the selected attributes through the variation list

Preserve the variation order and the attribute conditions on each possible match. In WooCommerce, a variation with Any for an attribute can match more than one selection; matching uses the first applicable variation from the top of the list. A default attribute value describes the form’s selected value, while the matching variation is the catalog record the store resolves from that selection. Keep both in the comparison.

For the displayed combination, identify which variation is the first match and whether a broader Any row sits above a more specific row. That can explain why a merchant’s expected specific variation is not the one being used. Do not reorder or delete rows before recording this relationship; otherwise the evidence you need to understand the existing cart may be lost.

The storefront is documented to update to the selected variation before add to cart. Compare its displayed option, price, image and availability with the matching variation. If the selection shown on the page does not agree with the configuration you recorded, leave that disagreement open for the storefront maintainer rather than attributing it to the buyer.

Use cart identity as the next record in the chain

For a genuine affected cart that is still available, compare its parent product, variation identifier where exposed, and selected attribute values with the pre-cart display. Record only identifiers the store actually exposes. A blank variation SKU can use the parent SKU in WooCommerce, so matching the SKU alone may not distinguish two variations.

If defaults, the first matching variation, the displayed selection and the cart all agree, the records support configured preselection for that observed path. They do not establish the buyer’s intention. If the cart identifies something different, preserve the mismatch for investigation of the handoff into the cart. If the cart or earlier display is unavailable, say which link is missing rather than claiming that current settings reconstruct the past.

A completed order dispute has additional records, including the stored order line and the confirmation. Keep that investigation separate from this narrower decision about what the page made purchasable before the cart was created. Changing a current default does not establish what an older order contained.

Decide which default behavior the merchant actually wants

The merchant should state whether this product is intended to open with a specific option already selected or require an explicit choice. If a deliberate default is intended, compare the intended combination with both the displayed selection and the variation that actually wins the match. If a fresh choice is intended, have the authorized catalog owner review the saved defaults and the storefront behavior against that requirement.

Where Any matching chooses the wrong catalog record, the change needs to address the attribute conditions or match order that produced the result. Removing an unwanted default and changing which variation matches are different edits. Preserve the original settings and specify the intended result before authorizing either. After the change, observe the current selection behavior and compare available real cart evidence; do not claim an old buyer action was verified by a new configuration.

For a Prism checkout consultation, provide the public product URL and a non-sensitive summary of the default-to-cart discrepancy. Keep the description within the research-only catalog. Confirm catalog or checkout investigation scope, implementation responsibilities, fees and terms before work begins.

Default-variation decision record

Complete this for one real product and an affected cart where available. Record current and historical observations separately. Agreement across the rows supports the configured selection path; a missing cart or prior display limits what you can conclude about an earlier visit.

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. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.