Aller au contenu
DocumentationStore health alerts

Store health alerts

The Store health panel on your dashboard tells you when something is quietly broken or at risk, names exactly what, and gives you one clear next step. Here is what each alert means and how to clear it.

Discount tools tend to fail silently: a discount that did not publish, a widget that is switched off, an offer whose rules never match a real cart. You lose sales and never see a warning. Store health exists to catch exactly those cases. It re-checks your store every time you open the dashboard, shows the most serious issues first, and each card names the specific campaign, product, or setting involved so you are never left guessing.

Tip

Self-healing

You do not dismiss these cards by hand. The moment the underlying cause is resolved, the alert clears on its own on the next dashboard load. When nothing is wrong, the panel says "Everything looks healthy" rather than sitting empty.

How this differs from Store insights

Store health and Store insights answer two different questions. Health asks "is anything broken or at risk right now?" and points you at a fix. Insights asks "where is the opportunity to sell more?" and suggests something to try, such as clearing aging stock or rewarding your best sellers. A healthy store still gets insights; a store with a problem still gets a health alert even when there is nothing new to try. In short: health is about fixing, insights is about growing.

Reading a card

Every alert carries a severity so you know what to do first.

  • Critical means money is actively affected right now, for example a discount that did not go live or a store price that is stuck edited. Handle these first.
  • Warning means things are working but something is at risk or not set up fully, for example a widget that is off or an offer that has not fired yet.

What each alert means and how to clear it

You will seeWhat it meansHow to clear it
A discount did not publish (critical)We tried to push a campaign to Shopify and it was rejected. The most common reason is that your store already has Shopify’s maximum of 25 live automatic discounts.Open the named campaign and choose Publish again. If you are at the limit, pause or remove another automatic discount (yours or a native Shopify one) to free a slot, then retry.
Your storefront widget is turned off (warning)The app embed that powers your on-store widgets is not enabled and saved on your live theme, so shoppers do not see tier tables, savings, or progress bars.Use "Turn on the widget" to open the theme editor, switch the Stackable app embed on, and click Save. Changes only take effect once the theme is saved; the alert clears once we detect it live.
An offer is not firing (warning)A campaign has been live for a couple of days and your store took orders, but none of them used its discount. That usually means its rules do not match the carts shoppers actually build.Open the simulator from the card, build a cart you expect to qualify, and see why it does not fire. Adjust the tier, minimum, or targeting and save.
Your targeting has drifted (warning)A product moved into or out of a collection or tag your campaign targets after you published, so the set of discounted products changed without you editing anything.Open the campaign and review its targeting. Keep the change, adjust the scope, or turn on auto-join so new products are included automatically. The discount keeps applying correctly at checkout in the meantime.
A discount may conflict (warning)One of your offers overlaps a Shopify or other-app discount that is set not to combine, so only one of them will apply for some shoppers.Open Discounts to see the overlap, then set the offers to combine, change their schedules so they no longer overlap, or remove the one you do not need.
You are near Shopify’s code limit (warning or critical)Your store is approaching, or has passed, the total number of discount codes Shopify allows across all apps.Open Discount codes and prune unused codes from ended campaigns, or hold off on new bulk generation. Critical means large new batches may be rejected until you free space.
A code batch did not finish (warning)A bulk code import stopped part-way, most often because some codes clashed with codes that already exist.Open the codes page to see which rows failed and why, resolve the clash, and re-generate just those codes.
Store health alerts, what triggers them, and the fix.
Note

After a bulk price edit or a channel price sync, a critical alert can also appear if a price could not be restored to its original. This one matters because a customer-facing price may still be changed; open the batch it names and retry the revert.

An alert will not clear?

  • Health re-checks on dashboard load, so give the page a refresh after you make the fix.
  • For the widget alert specifically, make sure you clicked Save in the theme editor; an unsaved toggle does not count and will not clear the alert.
  • If a fix genuinely took effect but the alert stays, reach out from the Support page and we will look into it.

Nous utilisons des cookies essentiels pour faire fonctionner ce site et, uniquement avec votre autorisation, des cookies d'analyse pour comprendre le trafic. Consultez notre Politique de cookies.