Order-history settings

Turn recent orders into a Cart recommendation strategy

The GoScript Smart Cart Recommendations WordPress plugin uses WooCommerce Analytics order history for products that use global smart recommendations. The order-history settings let you decide which recent orders should count, how much shared-purchase evidence a relationship needs, how closely candidates should match the Cart’s catalogue context, and what happens when useful matches are limited.

These controls let you move from a broad discovery strategy to a more selective one as your order history and merchandising confidence grow.

Choose the history window

Select the recent order-history period Smart Cart Recommendations should use for global co-purchase logic: 30, 60, 90, or 180 days. The right window depends on how quickly your catalogue changes and how often customers typically purchase complementary products together.

Shorter windowKeep the logic closer to the most recent customer buying patterns when your catalogue or demand shifts quickly.

Longer windowGive more qualifying purchase history a chance to reveal useful product relationships when buying cycles are slower.

Start with the window that best reflects your store’s normal purchase rhythm, then test the resulting Cart recommendations with representative products.

Choose the current order statuses that count

Select which current WooCommerce order statuses should contribute to the qualifying history. This lets you decide which completed stages of your own order workflow represent meaningful purchase evidence for recommendation logic.

Use statuses that reflect the orders you want to treat as reliable signals in your store, then keep the choice aligned with the way your team handles fulfilment, payment, and order updates in WooCommerce.

Set the minimum shared-order evidence

The minimum shared-order setting controls how many qualifying orders need to contain a product relationship before it can contribute to a history-based recommendation. Raising the threshold makes the logic more selective; lowering it allows the plugin to explore more emerging relationships.

Optionally narrow candidates by category or tag

Use the optional matching rule when automatic candidates should share the same category, the same tag, or either the same category or tag as the relevant Cart products. Leave the rule off when co-purchase evidence should have room to surface useful relationships across the wider catalogue.

This rule applies to global history-based recommendations. Manual product selections remain direct merchant choices, while final availability and global-exclusion checks continue to protect every source.

Choose the fallback that completes the experience

When the available global and manual candidates do not fill every selected product space, you can use qualifying best sellers, newest products, or no fallback. A fallback is considered only after the smart and manual candidates have been evaluated.

Use it to keep Cart discovery useful as co-purchase data develops, or choose no fallback when you want the section to remain strictly selective.

Review Analytics readiness before refining rules

Global history-based recommendations need WooCommerce Analytics and the required wc_order_product_lookup and wc_order_stats tables. The plugin surfaces this status in Settings so you can confirm the data foundation before spending time tuning history rules.

Saving Settings clears the recommendation cache. That makes it easy to adjust one control, refresh a representative Cart, and see how your latest logic performs in the live Cart context.