A bundle block that shows a loading state and never resolves usually cannot fetch its configuration. Republish the bundle first: that rewrites the configuration and fixes it most of the time. If it persists, the causes are almost always a conflicting app, a caching layer serving stale files, or a JavaScript error from something else on the page.
In this article:
Step 1: Republish the bundle
Open the bundle in Atlas.
Confirm it reads
Bundle is active.Select
Publish Bundle.Wait for
Bundle saved successfully!Reload the product page in a private window.
Republishing rewrites the bundle configuration that the block reads on the storefront. If that data was incomplete, this fixes it.
Step 2: Test in a clean browser
Open the product page in a private or incognito window, and on a different device if you can.
Result | What it means |
Loads correctly in private | A caching or extension problem on your own browser, not a store problem |
Still stuck in private | A real problem. Continue. |
Stuck on desktop, fine on mobile, or the reverse | A theme or app issue specific to that layout |
Step 3: Check for a conflicting app
⚠️ A store can only have one bundle app active. Another bundling, volume-discount or product-page app competing for the same part of the page is a common cause of a block that never finishes loading.
List the apps that modify your product page: bundling apps, upsell apps, variant pickers, sticky add-to-cart bars, currency converters, review widgets.
Disable them one at a time, checking the product page after each.
When the bundle loads, you have found the conflict.
Step 4: Check for JavaScript errors
An error thrown by any script on the page can stop later scripts running, including the bundle block.
Open the product page in Chrome.
Press F12 to open developer tools, and select the Console tab.
Reload the page.
Look for errors in red.
You do not need to interpret them. If you see errors, copy the text and send it to support: it usually identifies the script responsible immediately.
ℹ️ An error naming another app's script means that app is breaking the page for everything after it, including Atlas. The fix belongs with that app.
Step 5: Clear caches
Clear the cache in any performance or speed app on your store.
Wait a few minutes for Shopify's CDN to catch up.
Reload in a private window.
If you recently republished, give it a moment before concluding it did not work.
If it only happens on mobile
Check whether the block is inside a collapsible section, a tab, or an accordion that only appears on mobile. A block inside a hidden container can fail to initialise until the container opens.
Try moving the Atlas Bundler block out of any collapsible section in your theme editor, directly into the main product section.
What to send support
Start a chat from the bubble in the bottom right of Atlas, or email support@helloatlas.io. Either way, include:
your store URL
the product URL where it hangs
your theme name
a list of other apps that affect your product page
any console errors from step 4
whether it happens in a private window
whether it happens on mobile, desktop, or both
The console errors and the app list are the two most useful items. Between them they usually identify the cause without any back and forth.