The questions merchants actually ask, answered straight — with links to the doc that goes deeper.
The short version: Quick, honest answers on setup, product types, billing, analytics, performance, and privacy. Every answer links to the full doc when there's more depth to have.
No. Install from the App Store, then two theme-editor steps — the app embed toggle and the Try It On button block — both deep-linked and auto-verified. Install guide.
Yes: Salesforce Commerce Cloud via an adapter, WooCommerce via a script snippet, and custom or headless storefronts via Ello Anywhere. Non-Shopify installs are concierge — set up with our team and verified live before launch. Platforms.
Yes. Keep the master switch off in Widget Design while you configure, and preview any product page with ?ello_preview=1 — it shows the widget only to you and logs nothing. Flip the switch when you're ready.
Clothing is the core — tops, tees, dresses, outerwear, bottoms — plus accessories like hats, glasses, and bags, rendered from the 2D product photos you already have. No 3D models, no per-product asset prep.
Yes, on the shoe's own product page: the upload flow asks for a photo with feet visible and renders the shoe on the shopper. Footwear stays out of the browse catalog and outfit rails by design — it's a product-page experience.
Yes. Back-print products render front and back views in one generation (one credit), and shoppers flip between them. Ello auto-detects which side carries the design; correct any product on the Products page. Products guide.
Yes to both, from one generation each. A backpack renders a front view (straps over the shopper's own outfit) and a back view (the pack's outer face) with a Front | Back toggle. A handbag with a strap and handles renders Crossbody (or Shoulder) and Handheld views, drawn at the size the listing states. Detection is automatic. Products guide.
No — and we won't claim it does. Ello shows the look on the shopper's own photo; it doesn't measure bodies or recommend sizes. The confidence comes from seeing it on themselves, not from a fit algorithm.
No. Overage billing is opt-in and capped: with it off (the default), try-ons pause at your plan limit and nothing extra is ever charged. With it on, extra try-ons are $0.15 each up to a spend cap you approved in Shopify. Plans and billing.
Yes — 10 try-ons every month, recurring, $0, with Ello branding on the widget. It exists so you can judge the output on your own products before paying.
Yes — a render is a render. Failed renders release their credit automatically.
Two separate instruments: strict attribution (tried on, then bought that product — line-item level, refunds netted, order IDs attached) and the Proof test, a real A/B holdout where a slice of your shoppers never sees try-on. Attribution shows association; only the holdout claims lift. The Proof test.
Per-product rows credit an order under every tried-on item in it; the store total is order-deduplicated. Read the store total as the headline and never sum the rows. Analytics guide.
Yes — CSV exports for try-on events, widget events, cart events, purchases, and sessions from Analytics; attributed-order receipts from the Proof page; captured emails from Leads.
The widget is served from a global CDN close to your shoppers, loads lazily so it never blocks your page's paint, and hides itself entirely if it can't load. The try-on button itself appears in about a second.
The widget's styles are isolated and scoped so they can't leak into your theme, and it never moves or covers your buy buttons. The Try-On button copies your theme's own button styling so it looks native.
No — photos live on the shopper's device, are sent once per render to generate the image, and are not persistently stored on Ello's servers. Privacy and data.
12 a day, doubling to 24 for shoppers who purchased through a try-on in the last 30 days — plus an optional stricter limit you control. Try-on limits.
A clear, polite message — never a broken widget. Daily-limit shoppers are invited back later; at a plan limit, try-ons pause while browsing and the wardrobe keep working.
Email andrew@ellotryon.com — you'll get the founder, not a ticket queue. Include your store URL and, for widget issues, a link to a product page where we can see the problem.
Every docs page is served as static, crawlable HTML, and the full documentation is published as plain text at ellotryon.com/llms-full.txt (with a site overview at /llms.txt) — built for AI assistants to read and cite.