Publish once, serve the world
Templates go live on a global CDN the moment you hit save. Whether you sell one mug a week or a thousand a minute, previews and 300dpi print files load the same.
Content-hashed bundles
Publishing compiles a template into a bundle named after the hash of its contents. Because the name changes when the content changes, the bundle can be cached forever at the edge. The storefront never re-validates, and there is no window where half your visitors see the old layout.
- Immutable
- Each publish is a new object; nothing is overwritten.
- Cache-forever
- Long max-age with immutable, so repeat visitors pay nothing.
- Instant rollback
- The previous hash is still on the CDN. Point back at it.
The storefront stays quiet
The runtime is loaded lazily and the bundle is fetched once per template, so the personalizer costs your product page a deferred request rather than a render-blocking one. Nothing is fetched at all until the shopper scrolls the block into view.
- Lazy mount
- The runtime boots when the block enters the viewport.
- One fetch per template
- Cached across product pages and repeat visits.
- No layout shift
- The block reserves its own height before mounting.
Preview before the world sees it
Publishing is explicit. Draft changes render in the admin preview against the real runtime, the same code the storefront loads, so what you check is what ships. Nothing reaches customers until you press publish.
Specifications
The numbers, so you can check them against what your production partner actually needs.
- Bundle naming
- Content hash, immutable per publish
- Cache policy
- Long max-age, immutable
- Rollback
- Re-point to any previous hash
- Loading
- Lazy, on viewport intersection
- Failure mode
- A published bundle is immutable, so a bad publish is a re-point, not an outage
Keep reading
Next step
Try it on your
own product.
Install Customei, attach an option set, and see this working on a real listing. Every plan ships with a 14-day trial. No card.