Works where you sell.
Clione writes through each platform's own API, so the signals are part of the page your store sends, not something a script adds later. Pick your platform to see exactly where it writes.
Where Clione writes.
Metafields and two app embeds
Signals stored in metafields, put on the page by two embeds you switch on in one click.
Shopify →Rendered on the server
The graph goes out through the Widget API, as part of the HTML the store sends.
BigCommerce →Printed by your own server
Signals written through the REST API and printed in the page by the Clione plugin for WordPress.
WooCommerce →Any storefront that renders on the server
Catalyst, Hydrogen, Next.js, Nuxt or your own build, set up with your developers.
Headless →What Shopify's AI reads
Shopify's agentic storefronts draw on the same product data. Here is what they find.
Shopify's AI →ChatGPT, Gemini and the rest
What an assistant reads from a product page when it builds an answer.
AI assistants →What people ask about platforms.
My platform isn't here. Can I still use Clione?
Write to us. A headless storefront works whatever it is built with, and we set it up with your developers. For anything else, tell us what you sell on: it shapes what we connect next.
Does it work the same on every platform?
What Clione writes is the same: the enrichment, the questions, the structured data and the check of the live page, on products, categories or collections, and content pages. Where it writes follows each platform's own way of doing it, which is what each platform page explains.
Do I need a developer on either platform?
No. On Shopify and BigCommerce you connect the store from the Clione dashboard and switch the storefront side on from there. On WooCommerce you paste an API key and upload the Clione plugin. Only a headless storefront needs its developers.
Bring your store. See where it would write.
On a short call we open one product from your store: what it serves today, and what Clione would publish.