How to Fix Shopify Markets Cache Issues When Products Disappear After a Catalog Split
You split your catalogue with Shopify Markets. Domestic buyers get one range and pricing. International visitors get another. The admin looks correct.
Then the storefront starts lying.
Old banner images reappear. Products you added after the split vanish from collection pages. Click through and you get a 404. Reload once and the product exists. Reload again and it is gone. Sometimes even password protection does not stick for your home market.
That pattern is terrifying because it feels random. It is usually not random. It is a catalog publishing gap, an asset CDN cache, or edge propagation lag after a Markets configuration change, and the fix path is diagnosable once you stop treating it as a theme glitch.
This reflects patterns we see regularly across the Shopify merchant and developer community after international catalog splits: intermittent missing products, stale creative assets, and storefront state that does not match admin. The instinct is to rebuild the theme or uninstall apps. Frequently the faster path is verifying market catalog inclusion, Online Store publishing, and cache busting before opening a support ticket with the right evidence.
Introduction
Shopify Markets gives established brands a native way to sell multiple regions from one store: market-specific catalogs, variable pricing, subfolders or domains, and localized buyer experiences without spinning up separate shops.
The configuration step is deceptively simple. Pick regions, assign catalogs, set prices, publish. Merchants expect the storefront to reflect admin immediately.
Platform reality is more layered. Markets introduces buyer context: the combination of market, catalog, sales channel publication, and routing that determines which products exist, at what price, on which URL, for which visitor. Products excluded from a market catalog are omitted from lists and return not-found when queried in that context, behaving like archived items even when they look fine in admin.
When you add edge caching and CDN-backed assets on top of that context switch, you get failure modes that look supernatural: password pages that sometimes do not apply, banners from last season, and SKUs that exist only on every other refresh.
We audit multi-market Shopify builds where the business trigger is growth into new regions, often on Shopify Plus or Advanced plans approaching Plus complexity. The Markets split goes live, trading looks fine for a week, then post-split product launches become unreliable. This guide walks through how to diagnose that pattern, what merchants miss in catalog versus channel publishing, how to bust asset cache safely, and when the right move is Shopify Support with evidence rather than another theme edit.
If your differentiation lives in theme architecture, pair this with The Anatomy of a High-Performance Shopify Theme so you know whether the issue is Markets propagation or structural theme debt.
What merchants are running into
The community version of this problem follows a recognisable script.
A merchant enables Shopify Markets to separate a home country catalogue from international selling, often with variable pricing on selected SKUs. Subfolder or domain routing is configured. Existing products mostly behave. New products added after the split are the troublemakers.
Reported symptoms cluster like this:
- Stale creative assets, an old homepage banner displays even after replacement in admin
- Missing new products on collection and search surfaces for the home market
- Intermittent product 404s, the same handle works on one reload and fails on the next
- Inconsistent storefront state, password protection or pre-split content occasionally appears for domestic visitors
- Apparent fix on refresh, which pushes teams toward blaming the theme or a front-end app
Merchants verify the obvious admin settings: products are active, not draft, in stock, assigned to shipping zones, synced to both catalogues. They clear browser cache, test multiple devices, make minor theme edits to force a refresh. Nothing stabilises.
The critical detail is intermittency tied to market context. Issues often concentrate on the home market even when international configuration triggered the project. Products that existed before the split continue to work more reliably than net-new SKUs. That timing clue matters for diagnosis.
Why this happens
1. Market catalog versus Online Store publishing
Shopify separates where a product is allowed to sell (market catalog and catalog publication rules) from whether it is syndicated to a sales channel (Online Store, POS, or custom channels).
After a Markets split, merchants frequently confirm catalog membership in Markets admin but skip the equivalent publishing check for new products on the Online Store channel in the market context where buyers browse.
A partial state is possible: product added to the market catalog, Online Store publication incomplete or applied before market association finished. Storefront behaviour in that state can flicker between visible and not-found because different requests hit different layers of the publishing graph.
Shopify's developer documentation is explicit that products excluded from a market catalog are omitted from buyer-facing queries in that context. Merchants experience that as 404s and empty collection slots, not as a polite admin warning.
2. Products added after the split miss inherited workflow
The split event becomes a process breakpoint. Pre-split products went through an older publish path. Post-split products need the same market catalog assignment and channel publication discipline, but teams often assume "active in admin" is enough.
If your merchandising workflow is "create product, assign collection, done," Markets adds silent gates. Without a checklist, every launch after the split carries intermittent visibility risk.
3. Asset CDN cache is separate from catalog sync
Replacing a banner image by overwriting the same file in admin often leaves the old URL cached at the CDN edge. Visitors keep seeing the previous creative even when product data is correct.
That explains why stale banners coexist with missing new products. Two different cache layers: asset delivery versus catalog routing. Fixing one does not fix the other.
4. Edge cache propagation after major Markets changes
When merchants report password protection failing intermittently or pre-split storefront content appearing for the home market, that is not a Liquid bug. It suggests stale edge pages served for a region while backend catalog state has moved on.
Propagation delays are more common immediately after enabling Markets, changing subfolder structure, or rebalancing catalogs across regions. They should converge. If they do not after verified publishing fixes, platform intervention is reasonable.
5. Localization apps and legacy theme patterns
Apps that manipulate currency, geolocation, or swatches on the front end can conflict with native Markets routing if they pre-date the Markets configuration. A single front-end product app may not break the whole store, but it can amplify intermittent URL or context resolution issues.
Custom theme code that still reads cart.currency or hardcoded country lists instead of Shopify's localization and routes objects is a recurring audit finding. Online Store 2.0 reduced some of that debt, but Markets migrations often expose shortcuts that survived earlier replatforms.
6. Why reload roulette misleads your team
Intermittent success trains the wrong mental model. Someone refreshes until the product appears, declares victory, and ships more SKUs into the same broken pipeline.
Reload variance usually means multiple cache or context paths, not that the underlying issue healed itself. Treat every flicker as data for diagnosis, not as proof the store is fine.
On Plus and Advanced builds with multiple catalogs, price lists, and B2B company locations in play, the publishing graph gets wider fast. A product can pass one availability check in admin while still failing another on the storefront, which is why we document both legacy and new SKUs side by side before changing theme code.
How to diagnose it
Work top-down. Confirm buyer context before opening the theme.
Step 1: Reproduce with market and network discipline
Pick one failing product handle and one healthy pre-split product handle. Test both on the home market URL your domestic buyers use (subfolder, domain, or default).
Load both URLs twice from office Wi-Fi, then twice from cellular without clearing cache between attempts. Note whether failure is synchronized across networks or device-specific.
| Observation | Likely layer |
|---|---|
| Different results on Wi-Fi vs cellular at the same time | Platform propagation or regional edge cache |
| Same missing product on all networks, consistently | Catalog or publishing misconfiguration |
| Only new post-split SKUs fail | Post-split workflow gap |
| Stale banner but products correct | Asset CDN cache |
| Password page or old homepage intermittently | Edge cache serving pre-split pages |
Step 2: Verify market catalog inclusion
In Markets admin, open the affected market's catalog. Confirm the product is included, not excluded, and that any catalog rules or exclusions you set during the split did not silently omit new tags or product types.
For multi-catalog setups, check that the product sits in the catalog actually linked to the market your testers browse, not only a parent or secondary catalog used for pricing experiments.
Step 3: Verify Online Store channel publication
Open the product in admin and inspect Sales channels and apps. Confirm Online Store publication is active. If your workflow uses market-managed availability, re-check that the product is published in the Online Store context for the market where it fails.
This is the step teams skip because the product already appears in admin search. Admin visibility is not storefront visibility in a market context.
Step 4: Compare pre-split versus post-split products
Export a small comparison sheet: five working legacy SKUs and five failing new SKUs. Diff catalog assignment, channel publication, tags, templates, and inventory locations. The delta usually reveals a missing publish action or a collection rule that treats new products differently.
Step 5: Isolate front-end apps and custom market code
Temporarily disable non-essential localization or currency front-end apps and retest one failing handle. Review theme snippets that build product URLs, market switchers, or hreflang links. If you maintain custom Liquid for Markets, read Liquid Explained for Store Owners and audit against Shopify's localization objects rather than assumptions from pre-Markets builds.
Step 6: Document before escalating
Capture screen recordings showing two reloads with opposite outcomes on the same URL, plus admin screenshots proving catalog and channel state. Note market, timezone, and exact timestamps. Support resolves intermittent 404s faster with that bundle than with a general "Markets broke my site" message.
How to fix it
Fix A: Complete the publishing path for post-split products
For each affected SKU:
- Confirm inclusion in the correct market catalog
- Publish to Online Store for that market context
- Re-save the product to trigger propagation if admin already looked correct
- Re-test from two networks after five minutes, then again after thirty
Bake this into merchandising SOP so launches after the split cannot skip market steps. One checklist beats heroic refreshes.
Fix B: Bust asset CDN cache with new filenames
For stale banners or section images:
- Download the current asset
- Re-upload with a new filename (for example
hero-summer-v2.jpg) - Point the theme section at the new file URL
- Verify on cellular without hard refresh tricks
Do not rely on overwriting the same filename alone.
Fix C: Reduce theme and app conflicts
If isolation testing implicates a front-end app, configure it for native Markets or remove it until catalog behaviour is stable. Replace hardcoded country or currency switches with Shopify's supported localization patterns from your theme architecture baseline.
Fix D: Escalate to Shopify Support with edge-cache evidence
Open a ticket when publishing is verified and intermittency persists across networks. Lead with:
- Product URLs that 404 intermittently
- Proof that password protection or pre-split content sometimes appears
- Market region affected (especially home market)
- Timestamps and screenshots from simultaneous network tests
That evidence set signals stale regional edge cache and requests targeted cache invalidation rather than generic troubleshooting loops.
Fix E: Structural review when Markets exposed deeper debt
If catalog fixes stabilise some SKUs but metafield-driven merchandising, app-sourced inventory, or ERP-synced titles still disagree with admin, you are past a cache issue. The Markets split surfaced integration and data architecture debt similar to what we map in The Hidden Cost of Running a Shopify Store When 12 Apps Quietly Eat Your Margins. Schedule a stack audit before adding more markets or channels.
For teams still running legacy multi-currency snippets or pre-OS 2.0 section architecture, Markets is often the first time those shortcuts fail under real buyer context. Common Theme Mistakes That Kill Conversion Rates focuses on conversion, but the same lesson applies here: invisible theme debt becomes visible the moment you add regional routing and catalog rules on top.
| Symptom | First fix to try | Effort | When it is enough |
|---|---|---|---|
| New products missing after split | Market catalog + Online Store publish checklist | Low | Publishing gap was the only issue |
| Old banner despite new upload | Re-upload asset under new filename | Low | Creative cache only; catalog stable |
| 404 flicker on reload | Cross-network test, then Support with timestamps | Medium | Edge propagation; needs platform purge |
| Password page intermittently absent | Support escalation with regional evidence | Medium | Stale edge pages; not theme password setting |
| Issues only with one app enabled | Disable localization app; fix market routing code | Medium–High | Conflict isolated to app or custom snippet |
| Admin and storefront never agree | Stack audit or integrations review: apps, metafields, ERP sync map | High | Data model debt beyond Markets config |
When to get help
Bring in senior Shopify development when:
- You have verified catalog and channel publishing, busted asset CDN cache, and intermittent 404s still block launches
- Multiple markets, B2B catalogs, and ERP-fed availability rules interact and admin screens no longer match how buyers experience the store
- Custom theme market routing, hreflang, or collection filtering was built pre-Markets and needs refactoring to supported APIs
- Leadership wants to open more regions while product data quality across apps is already inconsistent
A Markets configuration fix can stabilise visibility quickly. It does not replace ordered diagnosis across theme, apps, data model, integrations, and checkout when the underlying stack was fragile before the split.
Conclusion
Shopify Markets cache issues feel chaotic because they stack catalog context, channel publishing, asset CDN, and edge propagation into one storefront experience. The merchant who refreshes until a product appears is treating a systems problem like a browser glitch.
Start with the six-check audit grid: market catalog, Online Store publish, post-split workflow, asset filename bust, cross-network testing, and support-ready evidence. Most missing-product reports after a catalog split resolve when publishing discipline catches up to the new market graph. Stale banners and password-page flicker point at CDN and edge layers that need filename changes or platform cache invalidation, not a theme reinstall.
If your store already runs a bloated app stack or inconsistent catalogue data, Markets will amplify that mess in every new region. Book a stack assessment or see Shopify Stack Audit. We will map what is a Markets propagation fix versus what needs structural rebuild before you scale internationally.
