Cart-specific recommendations are designed to respond to the Cart in front of them
The GoScript Smart Cart Recommendations WordPress plugin is built for the main WooCommerce Cart, not for a single catalogue-wide recommendation list. Each result starts with the products a shopper has currently added, then applies your recommendation source, settings, and final eligibility safeguards.
That means different Cart combinations can naturally show different suggestions-or no section at all when a display condition is not met. The variation is often a useful sign that the Cart logic is staying relevant to the shopper’s current buying context.
1. Cart contents shape the available recommendation evidence
For global smart recommendations, the plugin combines qualifying co-purchase evidence across the eligible products in the Cart. A Cart containing one product can have a different candidate pool from a Cart containing that product alongside other items.
Manual recommendation lists also depend on which product is currently in the Cart. Test the combinations your shoppers are most likely to build rather than relying on one sample Cart alone.
2. Display conditions can deliberately hide the section
Check the minimum Cart subtotal, whether recommendations are enabled, and whether the main Cart is the surface being tested. A Cart below the configured subtotal will not show the recommendation section, even if it contains products with useful relationships.
Also check for a Cart product with product-level suppression enabled. When that product is present, the Cart recommendation section remains hidden for the entire Cart.
3. Candidate sources and final eligibility can differ by Cart
Global candidates depend on the current Cart, qualifying order history, included statuses, minimum shared-order evidence, and any category or tag matching rule. Manual candidates depend on the product-level list saved for the Cart products that are present. Fallbacks can fill available spaces only after smart and manual candidates have been evaluated.
4. The final product checks protect the customer experience
Before display, the plugin removes products already in the Cart, duplicate candidates, unpublished products, hidden products, out-of-stock products, non-purchasable products, and products excluded by your global product, category, or tag rules.
When one Cart has a healthy visible section and another does not, compare those conditions first. A small change in stock, availability, exclusions, or Cart contents can make the final result meaningfully different.
5. Compare Carts with a simple test plan
- Build a focused Cart with one product that has known co-purchase history or a saved manual list.
- Record whether the section appears and which products it shows.
- Add a second product and compare the new Cart recommendation result.
- Repeat above and below your minimum Cart subtotal, then check for any suppressed Cart product or product availability change.
This approach makes the recommendation logic visible: you can see which Cart condition changes the result, then decide whether that behavior supports your intended strategy.
6. Refresh when you are testing a changed strategy
Recommendation results are cached by normalised Cart products, relevant context, settings signature, and cache version. Saving Settings advances the cache version, while the dedicated cache-clear action lets you refresh saved results without changing other settings.
Use a fresh Cart review after a meaningful adjustment so you are judging the current strategy-not a previous cached result.
Use Cart variation to make recommendations more useful
Cart-specific behavior gives you a powerful way to support different shopper needs without showing the same generic products everywhere. Use the reports, product-level preview, and live Cart testing to recognise the combinations that are creating the most useful discovery moments.