Skip to main content

​
Serving And Caching

Shoppex serves hosted Liquid storefronts through its storefront edge. It handles:
  • custom-domain and shop-domain routing
  • cache lookup and cache writes
  • cache purge handling
  • versioned public asset serving
  • Liquid HTML delivery
Theme packages do not own:
  • product stock calculation
  • pricing rules
  • checkout rules
  • platform cache behavior
  • fallback template lookup

​
Request Flow

buyer request
  -> Shoppex storefront edge
  -> resolve shop and active artifact
  -> serve cached HTML or public asset
  -> on HTML cache miss, render Liquid HTML
  -> cache and return rendered HTML

​
Assets

Public assets are served from the published theme artifact under assets/. Use assetUrl in Liquid: 
<img src="{{ 'assets/hero.png' | assetUrl: ctx }}" alt="{{ shop.name }}">
The private Liquid source package is not served from the public artifact path.

​
Blocked Paths

_shoppex/ is reserved for platform internals and is not a public storefront path. Do not put theme-owned public assets under _shoppex/.

​
Cache Behavior

In simple terms:
  • HTML can be purged when a theme publishes or settings change.
  • Versioned assets can be cached longer because the artifact path changes.
  • Preview sessions are isolated from live storefront cache.
If a page looks stale, check that you are not viewing an old preview URL and that the latest publish completed.

​
Custom Domains

Custom domains are handled by Shoppex. Theme packages do not need custom-domain code.

​
Next Steps

Server Liquid Rendering

How Shoppex builds Liquid HTML.

Troubleshooting

Fix stale pages, missing assets, and preview confusion.