How product variations are handled

One product family, one clear recommendation signal

WooCommerce variations let shoppers choose the exact size, colour, or other option that suits them. For Cart recommendation logic, the GoScript Smart Cart Recommendations WordPress plugin normalises variation products to their parent products before it evaluates the Cart.

This gives the plugin a consistent product-level foundation for finding co-purchase relationships, even when the Cart contains a specific variation rather than the parent product itself.

What normalising a variation means

When a shopper adds a variation to the Cart, Smart Cart Recommendations uses its parent product as the source product for the recommendation lookup. The plugin can then evaluate the parent product’s qualifying WooCommerce purchase history and the product-level recommendation configuration attached to that product family.

Variation in the CartThe shopper keeps the specific product option they chose as part of their own WooCommerce Cart.

Parent product for logicThe recommendation lookup works from the parent product’s historical relationship foundation.

Normalisation is used for recommendation evaluation. It does not turn the shopper’s selected Cart variation into a different product choice.

Why parent-level logic is useful

Purchase patterns are often strongest at the product-family level. Normalising variations to a parent product helps Smart Cart Recommendations use the available co-purchase evidence consistently instead of fragmenting the recommendation signal across individual options.

That can make it easier for a Cart containing one selected variation to benefit from the same relevant complementary-product relationships that the wider product family has built through real customer orders.

Product-level strategy still guides the experience

The parent-product recommendation configuration remains part of the Cart logic. Global smart recommendations can use qualifying co-purchase history, while manual mode can introduce merchant-selected products for a product family. Cart suppression can also prevent the recommendation section from appearing when the relevant product is in the Cart.

Final candidate checks still apply after the variation has been normalised for lookup: the suggested products need to be eligible, available, not already in the Cart, and outside your global exclusions.

Test the variations your shoppers use most

Add a few representative variations to a test Cart and review the resulting section. Compare them with the parent product’s available co-purchase history, manual recommendations, exclusions, and Cart suppression setting to see how the product-family logic works in your own catalogue.

If you update the relevant settings or product-level controls, save your changes or clear the recommendation cache before testing the Cart again.

Keep the recommendation decision focused

Variation normalisation is one step in preparing the Cart recommendation lookup. The final section still depends on the current Cart, the products that qualify from global or manual logic, your category/tag and exclusion rules, final availability checks, and any fallback you have chosen.