Versions & Cache
WandStore does not generate AI content on the shopper’s page load. Merchants generate drafts from the app, then theme blocks read the live version cache-first on the storefront.
Version model
Section titled “Version model”Each generated experience has:
- Experience identity - Store, audience scope, subject, page type, placement key, and kind.
- Versions - Immutable generated outputs.
- Aliases - Pointers for live, draft, and latest versions.
- Events - Generation, promotion, rollback, archive, and tracking history.
Promotion changes which version is live. It does not rewrite previous HTML.
Draft and live lifecycle
Section titled “Draft and live lifecycle”- Generate draft - Studio queues AI generation and creates a draft version.
- Preview - The merchant reviews the draft with a private storefront link.
- Set selected live - The selected version becomes the live version for that surface and audience.
- Iterate - A new draft can be generated from an existing version and change instruction.
- Roll back - Any previous valid version can be set live again.
- Deactivate - The experience stops rendering but history and analytics remain available.
Storefront delivery
Section titled “Storefront delivery”On page load, a WandStore block requests the live experience for its placement:
kind + page type + placement key + visitor contextIf a live version exists, the block receives generated HTML. If not, WandStore returns no content and the native Shopify theme remains in place.
What is cached or stored
Section titled “What is cached or stored”WandStore stores operational data needed to render and manage experiences:
| Data | Purpose |
|---|---|
| Generated versions | Render live widgets and preserve version history. |
| Draft/live aliases | Decide what renders and what remains private. |
| Prompt/debug context | Help merchants understand and iterate generated output. |
| Theme style profile | Guide theme-native widget generation. |
| Customer profile metadata | Support customer-specific personalization. |
| Customer Account tokens | Support customer-account features where available. |
| Analytics events | Report performance by experience and version. |
When to regenerate
Section titled “When to regenerate”Regenerate when:
- Product merchandising changes.
- A widget needs a clearer offer or stronger CTA.
- The theme design changed and the style profile was refreshed.
- A promotion or discount changed.
- The audience changed.
- Analytics show weak visibility, click, or conversion performance.
Clearing and deactivating
Section titled “Clearing and deactivating”For the current Studio workflow, prefer version actions over manual cache clearing:
- Use Generate next version to improve content.
- Use Set selected live to promote or roll back.
- Use Discard draft to remove an unwanted private draft.
- Use Deactivate to stop rendering while keeping history.
Impact on Shopify theme performance
Section titled “Impact on Shopify theme performance”WandStore delivery is independent of Shopify’s theme asset cache. It does not change:
- Shopify CDN caching for theme assets
- Liquid rendering for non-WandStore sections
- Browser caching of theme CSS and JavaScript
If no generated live version exists, the block remains empty and the rest of the page continues normally.