Point at any element on your live storefront, describe the change, and save the result as a servable variant.
The Visual Editor is a live view of your storefront with an AI editor attached. You navigate to the page you want, click the element you want to change, describe the change in plain language, and Xenia generates a variant of that element. Saved variants become something a journey can serve.
It is available to Shopify merchants once the store is connected. See Shopify app.
The two modes
The preview is your real storefront, and it has two modes:
Switch to Select and hover to see what you are about to change. When you click, the editor picks up that element and the section around it, so you can widen your selection from a single button up to the whole block it sits in.
Making a change
Select an element
In Select mode, click the headline, button, banner, or section you want to change.
Describe the change
In the chat panel, say what you want: "make this headline speak to first-time buyers", "tighten the copy and make the CTA more urgent", "use a warmer tone and mention free shipping".
Review the result
The editor shows the rewritten element, any styling it changed, and why it made those choices. The preview updates in place, in your real theme, so you are looking at the real thing rather than a mockup.
Iterate or save
Keep refining in the same conversation, or save. Saving asks for a name, and remembers which page and which element the variant belongs to.
Conversations are kept in a history sidebar, so you can return to how a variant was arrived at, or continue the thread later.
Saved variants
The left sidebar lists every variant saved for the connected store. Each card shows the variant name, the selector it targets, and the page it belongs to. Click the name to rename it in place.
Preview stays inside the editor. If the variant belongs to a page you are not currently on, the preview moves to that page first, then patches the element in place. Press Undo to put the original element back. Previewing a second variant undoes the first, so you are always looking at one at a time.
Refresh at the bottom of the sidebar re-fetches the list. It does not change what is currently applied in the preview.
From a variant to an A/B test
Journey is a shortcut out of the editor. It creates a draft journey from the Shopify A/B test template, pre-filled with the store and the variant you clicked, and opens it in the Journey Orchestrator.
What you land on is three nodes:
Shopify trigger
Fires on a page view for your store.
Multivariant Split
Two arms at 50/50.
Shopify Variant
Sitting on arm A, already pointed at your variant.
Arm B is intentionally left unconnected. That is the control: half your traffic falls through to the unmodified page, which is what makes the result a test rather than a rollout. Wire something onto B only if you want to compare two treatments instead of treatment against control.
The journey is saved as a draft, so nothing reaches shoppers until you finish configuring it and make it active.
A variant points at a specific element on a specific page. If a theme update moves or renames that element, the variant has nothing to attach to and quietly stops appearing. After any theme change, preview your active variants rather than assuming they survived.
Previewing on the real storefront
The editor's Preview button never leaves the editor. To see a variant on your actual storefront, open the journey that serves it in the Simulation tab and use the preview action on the Shopify Variant node.
That generates a single preview link covering every variant selected on that node and opens your live storefront with those variants applied for you. This is the honest test: real theme, real data, real device, without publishing anything to shoppers.
Serving a variant
Variants are delivered through a journey. The Journey button above is the quick path; you can also build one yourself. Add the Shopify Variant node, which is a terminal node, and pick the variants it should serve. The node takes an ordered list, so you can control precedence when several variants target the same page.
Because delivery goes through a journey, everything the journey knows applies to the variant: the trigger that brought the visitor in, any rules that branched them, and any audience check that gated them. A "returning VIP sees a different hero" experience is a page view trigger, a rule, and a variant node.
What this is good for
- Testing copy and offers on high-traffic pages without a theme deploy
- Giving a segment a different hero, banner, or CTA
- Trying a change quickly, then handing the winning version to whoever owns the theme
What this is not
It is not a theme editor. Variants patch specific elements at delivery time, they do not modify your theme files, and they disappear if the app embed is off. Use it for targeted, reversible changes, and put permanent changes in the theme itself.