They wanted snacks. Show them the rest of the pantry.

The food and snacks problem

Flavour, dietary fit, portion — and a catalog the visitor didn't finish.

A visitor lands on a single product page from an Instagram ad or a recipe blog. The flavour was close but not exactly what they wanted, or the bag size is too big for a one-person household, or the ingredient list has something they avoid. They reach for the back button — and at that moment, the storefront has done one of two things. Either nothing happens and the visit ends, or a popup appears asking for an email in exchange for 10% off, which addresses none of the actual mismatch.

The actual problem is that the store has the same item in two other flavours, a smaller portion size in the same flavour, and an adjacent dietary-fit option the visitor never reached. Premium food catalogs are unusually wide on these dimensions — flavour, format, dietary tag, packaging — and the discovery surface during a single visit rarely covers the full breadth. The recovery page is the cheapest place to fix that.

Live in production

Running on Wild Tree today.

Wild Tree — a UAE-based premium nuts and snacks brand — runs Before You Go on every product page. A visitor browsing a single variety of pistachios sees a recovery page populated with the adjacent flavours, portion sizes, and gift-format options the catalog already contained. Click through to see the actual recovery experience on a live storefront — same code path their visitors hit.

Wild Tree

Nuts & snacks · UAE

See the recovery page live →

Why this matters for food and snacks

Three things food has that other categories don't.

• Adjacency along multiple axes at once. Flavour, format, portion, dietary tag — a single SKU has half a dozen axes of variation, and the catalog has dozens of products. The recovery page surfaces adjacency along whichever axis the visitor was actually exploring rather than along an arbitrary “related products” rule.
• Repeat purchase intent built in. Food catalogs sell consumables, so a recovered visit often turns into a recurring customer. The discovery moment is disproportionately high-value because the lifetime value of a converted browse is multiple orders, not just the first one.
• Gift-format and seasonal context. Premium snack and food brands often sell the same core product in gift bundles, seasonal packaging, or tasting flights. A visitor who left because the standard format wasn't right for their occasion may convert on a gift bundle of the same catalog — the recovery page surfaces those without manual merchandising rules.

• Does the recovery page work for stores selling perishable or limited-stock items?

  Yes. Recommendations only surface products that are in stock and available for the visitor's region — out-of-stock SKUs and region-restricted items are filtered out automatically before the page renders. For perishable items with short shelf lives, the engine respects your storefront's existing inventory and availability rules without extra configuration.

• Can it surface dietary-fit alternatives — gluten-free, vegan, sugar-free, allergen-free?

  If those attributes are tagged on your products in Shopify or Shopware (as collections, product tags, or metafields), the content-similarity model picks them up automatically. A visitor browsing gluten-free snacks tends to see other gluten-free options in the recovery page, and the behavioural signals (co-views, co-clicks, co-purchases) reinforce the pattern over time as more shoppers reveal their dietary preferences through actual purchases.

• What about subscription and bundle products — do they get recommended?

  Subscription products are surfaced in the same way as one-time products, ranked by purchase affinity against the anchor product the visitor was browsing. Bundles render in the recovery page using your storefront's existing bundle-product display logic. If you want subscriptions or bundles to be boosted or suppressed in recommendations, the admin includes per-product boost and suppress controls for that.

• How does it handle international stores in different currencies and languages?

  The recovery page renders inside your store's own theme, so it inherits your storefront's currency formatting, locale, and number conventions automatically. The UI strings are localized into eight languages with shop-level overrides if a particular phrase needs a different translation. Multi-storefront setups that route different markets to different theme variations work out of the box — a UAE shopper sees AED, a UK shopper sees GBP.

• Will the recovery page interfere with our cart upsell or checkout flow?

  No. The recovery page only renders when a visitor is about to leave a product page without adding anything to the cart. Once an item is in the cart and the visitor is in checkout, the recovery page doesn't fire. Cart upsell apps, checkout extensions, and post-purchase upsell tools work in their normal surfaces without conflict.