Skip to content
Notifly Docs

Widget Not Showing

Work through this checklist in order. Most cases are resolved by step 3 or 4.

Step 1 — Check the product and trigger status

Section titled “Step 1 — Check the product and trigger status”

The widget is working correctly if no button is showing and the conditions for a button aren’t met. Confirm:

  • Is the variant you’re looking at out of stock? If yes, the back-in-stock button should show.
  • Is the variant in stock with price drop alerts enabled? If yes, the price drop button should show.
  • Has the product been added to Notifly? Go to Notifications in the dashboard and confirm the product is in the list. If it isn’t, add it — the widget won’t show buttons for products not added to Notifly.
  • Are the triggers enabled in your theme? On OS 2.0 themes, check the Enable Back-in-Stock Alerts and Enable Price Drop Alerts toggles in the Notifly app block settings. On legacy themes, check data-enable-back-in-stock and data-enable-price-drop in notifly-widget.liquid.

If everything looks correct and a button should be showing, continue to step 2.

Step 2 — Confirm the widget is on the page

Section titled “Step 2 — Confirm the widget is on the page”

Open the product page in your browser and view the page source (right-click → View Page Source, or Ctrl+U / Cmd+U).

Search for notifly-widget. If you see it, the widget HTML is being rendered. If you don’t, the widget hasn’t been added to your theme correctly.

OS 2.0 themes: Return to the theme editor, confirm the Notifly block is in the Product information section and saved. Make sure you’re viewing a product page, not the Home page, when checking.

Legacy themes: Confirm {% render 'notifly-widget' %} is in product.liquid (or product-template.liquid) and the file was saved. Also confirm the snippet files notifly-widget.liquid and notifly-modal.liquid exist under Snippets.

Step 3 — Check that assets are loading

Section titled “Step 3 — Check that assets are loading”

Open the product page, open your browser’s developer tools (F12 or right-click → Inspect), and go to the Network tab. Reload the page and filter by notifly.

You should see:

  • notifly-widget.css — status 200
  • notifly-widget.js — status 200

If either returns a 404, the asset files aren’t in your theme’s Assets folder. Contact support — the assets may need to be re-deployed.

If the files load but the buttons still don’t appear, continue to step 4.

Step 4 — Check the browser console for errors

Section titled “Step 4 — Check the browser console for errors”

With developer tools open, go to the Console tab, reload the page, and look for any red errors. Errors mentioning notifly, Uncaught TypeError, or Failed to load indicate a JavaScript issue.

A common error on legacy themes is a duplicate <script> tag causing a conflict. Search your theme.liquid for notifly-widget.js — it should appear exactly once, before the closing </body> tag.

Step 5 — Check the metafield

Section titled “Step 5 — Check the metafield”

The widget reads shop.metafields.notifly.app_url to know where to send API requests. If this metafield is missing, the widget will render but won’t function correctly.

In your Shopify admin, go to Settings → Custom data → Metafields → Shop and look for a notifly namespace entry. If it’s missing, try uninstalling and reinstalling Notifly — installation registers this metafield automatically.

Still not working?

Section titled “Still not working?”

Contact support at support@littleforgedigital.com with:

  • Your Shopify store URL
  • The product URL where the widget isn’t showing
  • Your theme name and version (visible in Online Store → Themes)
  • Any console errors you found in step 4
  • A screenshot of the product page