How gift product data loads & caching

When you change a gift product in Shopify or in the campaign customizer, you expect the storefront widget to match right away. Usually it does within a few minutes — but not always instantly. This page explains how the Gift-with-Purchase (GWP) widget pulls gift product data, why a short cache sits between Shopify and what your shoppers see, and exactly how to force a refresh when you can't wait.

Why this matters

You flip a gift product from Unlisted to Active, drop its price, swap the image, fix a translated title, or restock a sold-out variant — then you refresh the storefront and see the old value. Nothing is broken. The widget is showing data it already fetched a few minutes ago and held onto.

Knowing this saves you from chasing a "bug" that isn't one:

• You won't keep editing the product over and over thinking the change didn't save.
• You'll know when to simply wait, and when to force a refresh.
• You can give shoppers and teammates an accurate answer ("it'll update within ~5 minutes") instead of guessing.

The rest of this page sets those expectations precisely and gives you the levers to speed things up.

How gifts are loaded (plain English)

Normal storefront browsing — collection pages, search, "you may also like" listings — works by searching or listing your catalog. Shopify's listing/search results deliberately exclude unlisted products, so anything hidden from search simply never shows up in those places.

The GWP widget works differently. It doesn't search your catalog. It already knows exactly which products are gifts in your campaign, so it fetches each gift product directly by its ID — one targeted lookup per gift, by name, not a search.

That direct-by-ID approach is the reason an unlisted gift product can still appear in the widget: fetching a product by its specific ID reaches any product published to your Online Store sales channel, including ones hidden from search. A catalog search could never surface that same unlisted product.

Here is the contrast in one view:

A simple way to picture the GWP flow:

Your campaign already holds the gift product IDs
        │
        ▼
Widget asks Shopify: "give me product 123, product 456" (by ID, not a search)
        │
        ▼
Shopify returns each gift directly — including unlisted ones
        │
        ▼
Result is cached client-side in the browser for ~5 minutes, then re-fetched

The ~5-minute cache

To keep the widget fast and avoid hammering Shopify on every page view, the storefront caches the gift product data it fetches in the browser's memory for about 5 minutes. This is a client-side, in-memory cache — not an HTTP or CDN cache — and it's keyed by the exact query string the widget sends, so each distinct query gets its own entry. During that window, the widget reuses what it already pulled instead of asking Shopify again. Once the window passes, the next load re-fetches fresh data.

That cache covers essentially everything the widget reads off a gift product. After you change any of the following in Shopify admin, the storefront can keep showing the previous value until the cache expires:

In other words: if a value lives on the Shopify product, expect the ~5-minute delay. The filtering toggles (Hide unlisted products, Hide out-of-stock) depend on the product's status and inventory, so a change to those filters only becomes visible once the underlying product data is re-fetched too.

What updates immediately vs after the cache

Not every change is subject to the 5-minute wait. The dividing line is where you made the change.

The fastest way to push a Shopify product change through without waiting is to re-sync the campaign (covered next). Re-syncing is the recommended action whenever you've edited a gift in Shopify and need it live sooner than the cache would deliver on its own.

Recipe: a status change that depends on the filter

A common sequence makes the interaction concrete. Say a gift is Active and showing in the widget:

1. You change it to Unlisted in Shopify admin. With Hide unlisted products OFF (the default), the gift still appears once the cache refreshes — direct-by-ID lookup reaches unlisted products too.
2. You then turn Hide unlisted products ON in the customizer. Now the gift is filtered out — but only after the product data refreshes and the widget sees it as unlisted.
3. Later you switch the product back to Active in Shopify. After the cache expires, it reappears regardless of the toggle, because the filter no longer matches it.

Every Shopify-side step in that sequence is subject to the ~5-minute window; the customizer toggle itself is not, but it can only judge "unlisted" against whatever product data is currently loaded.

Recipe: combining Hide unlisted and Hide out-of-stock

The two filters work independently, so the gifts a shopper sees are whatever survives both. Use this as a quick reference when a gift unexpectedly appears or disappears:

Country & language context

Gift data isn't fetched once globally — it's fetched per market and per language, so each shopper sees prices and translated titles appropriate to where they are.

• Per country: the widget requests gift data in the shopper's country context, so a gift's price reflects that market's pricing.
• Per language: translated titles and descriptions are fetched for the active storefront language.

Because each country/language combination is fetched separately, each one is also cached separately. The practical consequence when you're testing:

If a price or translated title looks wrong, first confirm you're viewing the market/language you actually edited, then check whether that specific context's cache has had time to refresh.

How to force a refresh

When you can't wait out the window, here are your options, from most reliable to simplest:

Troubleshooting

Most "the storefront still shows the old value" reports come down to the cache. Find your symptom below.

Related pages