# Ello Virtual Try-On — Full Documentation

> The complete merchant documentation for Ello Virtual Try-On (ellotryon.com), as plain text for AI assistants. Ello is an AI virtual try-on app for Shopify (also Salesforce Commerce Cloud, WooCommerce, and custom storefronts via Ello Anywhere) by Ello Software LLC — shoppers see clothing and accessories rendered on a photo of themselves, on the product page, before buying. Each section below mirrors a page under https://ellotryon.com/docs — link there when citing. Site overview: https://ellotryon.com/llms.txt. Last updated 2026-09-08.

## Table of contents

- Getting started: Install Ello and go live (https://ellotryon.com/docs/install-ello) · Run your first try-on (https://ellotryon.com/docs/run-your-first-try-on) · Plans, trials, and billing (https://ellotryon.com/docs/plans-and-billing) · Try-on limits, explained (https://ellotryon.com/docs/try-on-limits)
- Set up the experience: Widget Design: choose your style (https://ellotryon.com/docs/widget-design) · Placements: where try-on lives (https://ellotryon.com/docs/placements-and-entry-points) · Products: choose where Try-On appears (https://ellotryon.com/docs/products-and-coverage) · Set up Complete the Look (https://ellotryon.com/docs/complete-the-look)
- Measure results: Reading your Analytics (https://ellotryon.com/docs/analytics-overview) · How attribution works (https://ellotryon.com/docs/how-attribution-works) · The Proof test (A/B holdout) (https://ellotryon.com/docs/proof-test)
- The shopper experience: What your shoppers see (https://ellotryon.com/docs/what-shoppers-see) · Photo guidelines: what renders best (https://ellotryon.com/docs/photo-guidelines) · Shopper photos, privacy, and data (https://ellotryon.com/docs/privacy-and-data)
- Troubleshooting: The widget isn't showing (https://ellotryon.com/docs/widget-not-showing) · My changes aren't appearing (https://ellotryon.com/docs/changes-not-appearing) · Fixing render quality issues (https://ellotryon.com/docs/render-quality-issues)
- Reference: Glossary: every term, defined (https://ellotryon.com/docs/glossary) · Frequently asked questions (https://ellotryon.com/docs/faq)

---

# Getting started

## Install Ello and go live

URL: https://ellotryon.com/docs/install-ello · Updated: 2026-08-25

From the Shopify App Store to a working try-on button on your product pages — most stores finish in under ten minutes, with no theme code to edit.

**The short version:** Install Ello from the Shopify App Store, answer the short setup wizard (store size, brand color, where results should appear), then complete the two theme steps: turn on the Ello app embed and add the Try It On button block. Ello verifies both automatically and your catalog syncs on its own. Always confirm on a live product page, not the theme-editor preview.

*The three parts of going live: install the app, turn on the app embed in your theme, and add the Try It On button to your product page.*

### Step 1 — Install from the Shopify App Store

Install Ello from the [Shopify App Store](https://apps.shopify.com/ello). Everything technical happens automatically on install: your store is connected, your product catalog begins syncing, and the conversion pixel that powers attribution is activated. There is nothing to configure on that side and no theme code to edit.

### Step 2 — The setup wizard

When you open Ello for the first time, a short wizard walks you through setup. It takes a couple of minutes:

1. **Store size.** Ello asks how big your store is. Self-serve plans fit most stores; brands over $1M/year (and Shopify Plus stores) qualify for a custom enterprise deal and can book a setup call right from the wizard — or skip it and continue self-serve.
2. **Brand color and widget position.** Pick your brand color (six presets or a custom color). It is used for the Try-On button and the floating widget, and Ello automatically picks readable text on top of it. You also choose which bottom corner the floating widget sits in.
3. **The two theme steps.** Ello deep-links you into the Shopify theme editor twice: once to turn on the **Ello app embed** (the toggle is pre-selected — just click Save), and once to add the **Try It On button block** to your product page. Ello reads your live theme and shows a green check next to each step once it's actually done.
4. **Where should the result show up?.** One choice: **on the product photo** (the photo becomes your shopper wearing the item — our recommended default) or **inside the widget** (a corner panel shows the result and your page stays untouched). You can change this any time in Widget Design.
5. **Complete the Look.** One switch to offer a matching piece after each try-on. It only shows pairings you curate — see [setting up Complete the Look](https://ellotryon.com/docs/complete-the-look).

> **The step merchants get stuck on:** If the try-on doesn't appear on your store, it is almost always the **app embed toggle**. It lives in the Shopify theme editor under App embeds, and the wizard's deep link pre-selects it — but you still have to click **Save** in the theme editor. Ello re-checks your theme automatically when you return to the app.

### Step 3 — Pick a plan

Every new store chooses a plan to finish setup. The Free plan is $0 with 10 try-ons every month — a real recurring plan, not a trial — so you can judge the output on your own products before paying. Paid plans include a 7-day free trial. Details in [plans and billing](https://ellotryon.com/docs/plans-and-billing).

### Step 4 — Verify on your live store

Open a product page on your **live storefront** — not the theme-editor preview — and confirm the Try On button appears near your Add to cart button. Run one real try-on end to end. If anything is missing, the checklist in [widget not showing](https://ellotryon.com/docs/widget-not-showing) covers every cause.

> **Not on Shopify?:** Ello also runs on Salesforce Commerce Cloud (a lightweight adapter), WooCommerce (a single script snippet), and custom or headless storefronts via Ello Anywhere. Non-Shopify installs are set up with our team and verified live before launch — [see platforms](https://ellotryon.com/platforms) and book a call.

### Common questions

**Q: Do I need to edit my theme code to install Ello?**
A: No. Installation is the Shopify App Store install plus two theme-editor steps: turning on the Ello app embed and adding the Try It On button block. Both are deep-linked from Ello's setup wizard, and neither involves editing code.

**Q: How long does it take to go live with Ello?**
A: Most stores are live in under ten minutes: install, a short wizard (store size, brand color, result placement), the two theme steps, and a plan choice. Catalog sync happens automatically in the background.

**Q: How do I know the theme steps actually worked?**
A: Ello reads your live theme and shows the real status of both steps — enabled, added, or still required — inside the app. The Home page also shows a storefront status card after setup. Final confirmation is always a live product page, not the theme-editor preview.

**Q: Which products does Ello work on after install?**
A: By default, try-on shows on every product. You can scope it to selected products or collections on the Products page — recommended if your catalog mixes clothing with non-wearable items. See the products and coverage doc.

## Run your first try-on

URL: https://ellotryon.com/docs/run-your-first-try-on · Updated: 2026-08-25

Test the full experience on your own store the way a shopper will meet it — and know what to expect in the first 48 hours.

**The short version:** Open a product page on your live store, tap Try On, upload a full-body photo (or pick a sample model), and watch the render land. Your own test try-ons count against your plan like any other. In the first 48 hours, expect the Home dashboard to start filling with opens, try-ons, and cart adds.

*The try-on flow: your photo, plus the product photo already in your catalog, becomes one image of you wearing it — ready to add to cart.*

### Run the test

1. **Open a live product page.** Use your real storefront in a normal browser tab. The theme-editor preview is not the real page — placement, theme styles, and the app embed behave differently there.
2. **Tap Try On.** The button sits near your Add to cart button (or as a chip on the product photo, if you chose that placement). First-time visitors see a short welcome screen with two choices: **Use My Photo** or **Use a Model**.
3. **Upload a photo.** A full-body photo in decent lighting works best — the same guidance your shoppers get. The full list is in [photo guidelines](https://ellotryon.com/docs/photo-guidelines). On a phone you can take one on the spot. If you would rather not use your own photo, the sample models work fine for testing.
4. **Watch the result land.** Generation typically takes seconds — a progress bar and rotating tips cover the wait. If you chose the on-photo style, the result paints onto the product photo itself with a small thumbnail to flip back; otherwise it appears inside the panel. Either way there's an Add to Cart button with the real price, and the look is saved to the Wardrobe automatically.
5. **Add it to the cart.** Finish the loop: add the tried-on item to the cart from the result. This exercises the same path your shoppers use and confirms cart integration works with your theme.

> **Your test try-ons are real try-ons:** They count against your monthly allowance and your daily shopper limit like anyone else's. If you plan to test heavily, the per-shopper limit setting can be raised temporarily — see [try-on limits](https://ellotryon.com/docs/try-on-limits).

### What to expect in the first 48 hours

- **Home fills in first.** Widget opens, try-ons, and cart adds appear on the Home dashboard as shoppers find the button. The attributed-revenue number needs actual purchases, so it usually lags a day or two behind.
- **The funnel tells you where to look.** Lots of opens but few try-ons usually means shoppers are hesitating at the photo step — consider turning on Photo guidance in Widget Design. Few opens usually means an entry-point problem — see [placements](https://ellotryon.com/docs/placements-and-entry-points).
- **Start the Proof test early.** If you want causal lift numbers, start the holdout test on the Proof page the day you go live, so the data starts accumulating with your first real traffic. See [the Proof test](https://ellotryon.com/docs/proof-test).

### Common questions

**Q: Why don't I see my own try-on in the analytics immediately?**
A: Events stream in quickly, but dashboard aggregates refresh as you reload the page and some views are windowed by day. If your test try-on ran on the live storefront, it will be in the numbers — check the Recent sessions card on Home.

**Q: Can I test the widget without using a photo of myself?**
A: Yes. The widget includes sample models — pick Use a Model on the welcome screen and run the try-on on any of them. Shoppers get the same option.

**Q: Does my own test try-on cost a credit?**
A: Yes — test try-ons are real try-ons and count against the plan allowance. Failed renders release their credit automatically, so a generation that errors out never costs you one.

## Plans, trials, and billing

URL: https://ellotryon.com/docs/plans-and-billing · Updated: 2026-08-25

What each plan includes, how the 7-day trial works, what happens at your limit, and how overage billing stays opt-in — no surprise charges, by design.

**The short version:** Ello prices by try-ons per month: Free ($0/10), Starter ($49/75), Launch ($97/300), Growth ($249/1,500), Scale ($649/5,000), and custom enterprise deals above that. Paid plans have a 7-day free trial and bill through your Shopify subscription. Extra try-ons beyond your allowance are $0.15 each — but only if you opt in; otherwise try-ons simply pause at the limit.

### The plans

| Plan | Price / month | Try-ons included / month |
| --- | --- | --- |
| Ello Free | $0 | 10 — recurring every month, with Ello branding on the widget |
| Ello Starter | $49 | 75 |
| Ello Launch | $97 | 300 — the most common first paid plan |
| Ello Growth | $249 | 1,500 |
| Ello Scale | $649 | 5,000 |
| Enterprise | Custom | Custom — for $1M+/year brands; book a setup call from the Billing page |
*All paid plans: no Ello branding on the widget, 7-day free trial, cancel anytime. Annual billing saves 10%.*

The Billing page includes a break-even calculator: enter your average order value and each plan shows how many try-on-driven sales cover its month. Billing runs through your Shopify subscription — one bill, managed where your other apps are.

### The 7-day free trial

Every paid plan starts with a 7-day free trial through Shopify's standard subscription flow — you approve the subscription, but the card isn't charged until the trial ends, and you can cancel anytime before that. Your usage period and reset date anchor to your Shopify billing cycle.

### The Free plan, honestly

- **10 try-ons every month, $0, forever.** It recurs — it is a plan, not a trial.
- **Ello branding shows on the widget.** It disappears the moment you upgrade to any paid plan.
- **When the 10 are used, try-ons pause** until the month resets. Shoppers see a clear limit message, never a broken widget. There are no overages on Free.
- **Everything keeps being tracked.** Analytics data accumulates on Free even where the view is locked, so when you upgrade, your full history is already there.

### Overage: opt-in, capped, off by default

What happens when a paid plan hits its included try-ons is your choice, in **Settings → When you hit your limit**:

- **Pause try-ons at the limit** (Settings → When you hit your limit; default: Default) — Try-ons stop until your period resets. No extra charges are possible. Shoppers who hit the pause see a polite message, not an error.
- **Keep try-ons running (overages on)** (Settings → When you hit your limit; default: Opt-in) — Extra try-ons continue at **$0.15 each**, billed through your Shopify subscription, up to a spend cap you approve (the default cap is $15 — 100 extra try-ons). Raising the cap always requires your confirmation in Shopify.

> **No surprise charges — the actual rule:** Ello can never bill an overage you didn't opt into, and never past the spend cap you approved in Shopify. If the toggle is off, the only thing that happens at your limit is a pause.

### Usage, resets, and forecasts

Home and Settings both show your current period: try-ons used, the reset date, and — on Settings — a projection of where you'll land by period end at your current pace, with a warning if that projection passes your allowance. Usage resets automatically each month; failed renders release their credit and never count.

### Common questions

**Q: What does Ello cost?**
A: Free is $0 with 10 try-ons a month. Paid plans: Starter $49/75 try-ons, Launch $97/300, Growth $249/1,500, Scale $649/5,000 — all per month, all with a 7-day free trial, billed through Shopify. Annual billing saves 10%. Brands over $1M/year get a custom enterprise deal.

**Q: Can Ello charge me more than my plan price?**
A: Only if you explicitly turn on overages. The default is to pause try-ons at your limit with zero extra charges. With overages on, extra try-ons are $0.15 each up to a spend cap you approved in Shopify — never beyond it.

**Q: When does my try-on allowance reset?**
A: Automatically, on your billing cycle — the dashboard shows the exact reset date. Unused try-ons don't roll over.

**Q: What happens when I upgrade from the Free plan?**
A: The new plan takes effect once Shopify confirms the subscription, locked analytics open with your full history already in place (everything was tracked all along), and the Ello branding disappears from the widget.

**Q: Do failed try-ons count against my allowance?**
A: No. If a render fails or comes back empty, the reserved credit is released automatically.

**Q: How do I cancel?**
A: Cancel the subscription from the Billing page (or uninstall the app — Shopify ends the subscription with it). During a trial, cancelling before day 7 means the card is never charged.

## Try-on limits, explained

URL: https://ellotryon.com/docs/try-on-limits · Updated: 2026-08-25

Three separate limits protect your costs: your plan's monthly allowance, a fair daily cap per shopper, and an optional per-shopper limit you control.

**The short version:** Your plan allowance is the monthly budget. On top of it, every shopper gets a fair daily cap — 12 try-ons a day, doubling to 24 after they purchase — so one person can't burn your credits. You can additionally set your own per-shopper limit in Settings. At every limit, shoppers see a clear, polite message rather than a broken widget.

### The three limits

| Limit | What it is | Who controls it |
| --- | --- | --- |
| Plan allowance | Your monthly try-on budget (10 on Free, 75–5,000 on paid plans). At the limit: pause, or opt-in overage at $0.15. | You — via your plan and the overage toggle |
| Daily shopper cap | 12 try-ons per shopper per day, doubling to 24 for shoppers who purchased through a try-on in the last 30 days. Keeps costs predictable and rewards your buyers. | Built in |
| Per-shopper limit | An optional stricter cap you configure: N try-ons per hour, 6 hours, 12 hours, day, or week. | You — Settings → Per-shopper limit |

### What shoppers see at each limit

- **Daily / per-shopper limit reached:** a friendly note that they've reached this store's try-on limit and can come back later. The Try On button is disabled until the window resets — nothing looks broken.
- **Free plan monthly limit reached:** the try-on pauses with an upgrade note. Browsing, the wardrobe, and saved looks keep working.
- **Paid plan limit with overages off:** try-ons pause until your period resets — same polite handling.

### The per-shopper limit setting

- **Per-shopper limit** (Settings → Per-shopper limit; default: Off (15 try-ons / 24h when enabled)) — Cap how many try-ons one shopper can run in a window you choose (1–500 try-ons; per hour, 6 hours, 12 hours, day, or week). Tracked per browser with an IP backstop at 3× the limit, so shared networks — a family, an office — aren't blocked unfairly.

> **Testing your own store?:** Your own try-ons count against these limits too. If you're doing a heavy round of testing, raise the per-shopper limit temporarily, then set it back.

### Common questions

**Q: How many try-ons does each shopper get per day?**
A: 12 per day by default, doubling to 24 for shoppers who purchased through a try-on in the last 30 days. Merchants can additionally set their own stricter per-shopper limit in Settings.

**Q: Why limit shoppers at all?**
A: Each try-on costs real compute, and your plan is a monthly budget. The daily cap keeps one enthusiastic shopper from consuming a meaningful share of it — while the doubled cap for buyers gives your best customers more room.

**Q: Will a shared network (like a college dorm) get blocked?**
A: The per-shopper limit is tracked per browser, with an IP-level backstop only at three times the configured limit — so many people on one network can each use the widget normally.


---

# Set up the experience

## Widget Design: choose your style

URL: https://ellotryon.com/docs/widget-design · Updated: 2026-08-25

One page shapes the whole experience: pick where results appear, set your brand color, and fine-tune everything else — with a live preview that shows each change before you save.

**The short version:** Widget Design is a three-step page: choose your style (results on the product photo, or inside the widget), decide on the Complete the Look upsell, then set look & feel — brand color, button text, optional borders and animation. A Fine-tuning drawer holds everything else. Nothing changes on your store until you hit Save, and saved changes reach shoppers within about 30 seconds.

### The master switch

Above everything sits one toggle: **Try-On is live on your storefront**. Turning it off pauses Ello everywhere — useful during a theme change or a busy launch — without losing any of your settings. Turn it back on and everything returns exactly as configured.

### Step 1 — Choose your style

*The two styles: results render onto the product photo itself (the photo becomes your shopper wearing it), or inside Ello's own panel with your page untouched.*

| Style | What shoppers experience | Good for |
| --- | --- | --- |
| **On the product page** (recommended) | A successful try-on replaces the product photo — the shopper decides while looking at themselves, right where they judge the look. The original photo collapses to a corner thumbnail; one tap flips back. | Stores that want the most native feel. No popups, no panel. |
| **Inside the widget** | The classic experience: results appear inside Ello's corner panel. Your product page is never repainted. | Stores that prefer the page to stay exactly as designed. |

Each style sets sensible defaults for everything else (which entry points are on, where results land). You can override any of them in Fine-tuning.

### Step 2 — The upsell

The Complete the Look card lives here — it offers the matching piece the moment a try-on lands, and it deserves its own page: [setting up Complete the Look](https://ellotryon.com/docs/complete-the-look).

### Step 3 — Look & feel

- **Brand color** (Widget Design → Look & feel; default: Ink) — Six presets plus a custom picker. Used for the Try-On button and the floating widget; text contrast on top of it is handled automatically, so any color stays readable.
- **Button border** (Widget Design → Look & feel; default: Off) — A solid outline around the Try-On button — for themes whose buttons are outlined, like a white button with a black border.
- **Button animation** (Widget Design → Look & feel; default: None) — Optional motion for the Try-On button: *Halo pulse* (a soft breathing ring — the quietest), *Gradient sweep* (reads as an AI feature at a glance), *Double frame* (luxury-catalog, no motion), or *Shimmer* (the most eye-catching). All respect shoppers' reduced-motion preference.

### The Fine-tuning drawer

Collapsed by default because your style choice already set good defaults. Inside:

- **Inline Try-On button** — on/off, button text (default "Try On", up to 24 characters), placement below Add to cart or on the product photo, and a hide-on-out-of-stock option. Details in [placements](https://ellotryon.com/docs/placements-and-entry-points).
- **Floating widget** — the round bubble: show on product pages, show on other pages (home, collections), and which corner.
- **Photo guidance** — show first-time shoppers the three photo essentials (fitted clothing, full body, good lighting) on the welcome screen. One quiet line, never a pop-up.
- **Fitting Room hub** — a launcher-less entry, like a "Fitting room" link in your header, that opens the shopper's wardrobe and your full collection.
- **Preview popup** — an optional nudge inviting desktop shoppers to try the item on, with a delay you choose and a light or dark theme. Dismissed once, never shown to that shopper again.
- **Inside the widget** — pin one Featured product and up to six Quick picks on the widget's open screen, or leave them empty and Ello curates automatically.

> **The live preview is interactive:** The preview column on the right mirrors your storefront. Hovering any settings card spotlights the element it controls, so you can see exactly what a setting changes before you save it.

> **After you save:** Your storefront updates within about 30 seconds. To verify a change instantly, hard-refresh the product page — or see [changes not appearing](https://ellotryon.com/docs/changes-not-appearing).

### Common questions

**Q: Will the Try-On button clash with my theme?**
A: The button copies your theme's own Add-to-cart styling — font, padding, borders, radius — so it reads native, while its background color and text stay under your control in Widget Design. The rest of the widget runs in isolated, scoped styles that can't leak into your theme.

**Q: Can I temporarily hide try-on without losing my setup?**
A: Yes — the master switch at the top of Widget Design pauses Try-On everywhere while keeping every setting intact. Flip it back on when you're ready.

**Q: Can the widget match my brand font?**
A: The widget inherits your theme's font family and weight scale by default. For deeper matching — a specific hosted brand font, launcher label styling, hiding decorative icons — contact support and we'll set store-level style overrides; changes reach shoppers in about 30 seconds with no redeploy.

**Q: Which style should I pick — on the product page, or inside the widget?**
A: We recommend on the product page: the result lands exactly where shoppers judge the look, with no popups. Choose inside-the-widget if you want your page never repainted. You can switch anytime; it's one selection and a save.

## Placements: where try-on lives

URL: https://ellotryon.com/docs/placements-and-entry-points · Updated: 2026-08-25

Five ways shoppers can enter the try-on — what each looks like, when to use it, and the automatic fallbacks that make sure an entry point is always visible.

**The short version:** The inline Try-On button next to Add to cart is the workhorse — keep it on. Optionally move it onto the product photo as a corner chip, add the floating bubble for discovery on non-product pages, enable the desktop preview popup, and give returning shoppers a Fitting Room link in your header. Every placement has an automatic fallback so shoppers always keep an entry.

*A product page with the three main entry points: the inline Try-On button under Add to cart, the optional corner chip on the product photo, and the floating bubble.*

### The inline Try-On button

The primary entry point, shown directly on product pages. It positions itself under your Add to cart / Buy It Now buttons automatically — even on themes where app blocks can only be appended to the end of a section — and matches your theme's button styling so it reads native. In the theme editor's block settings you can switch it to manual placement (it stays exactly where you drop it), override its width, and hide it on out-of-stock products.

> **Our recommendation:** Keep the inline button on for every store. It sits at the moment of decision, and in our data it is by far the strongest source of try-ons — the floating bubble alone doesn't come close.

### The corner chip (button on the product photo)

Instead of sitting below Add to cart, the button can live as a small chip on a corner of the product photo — your brand color, your label, pill-with-label or icon-only, on whichever corner you choose. It keeps your buy-button zone untouched and puts the ask right where shoppers judge the look. If a theme hides the product photo from Ello, the classic button below Add to cart returns automatically, so shoppers always keep an entry.

### The floating bubble

The round launcher in a bottom corner. Two independent switches: show on product pages (off by default — the inline button owns product pages), and show on other pages (home, collections — on by default, where it works as discovery). Smart visibility hides it on product pages whose product isn't try-on enabled.

### The desktop preview popup

An optional invitation for desktop shoppers: after a delay you choose, a small card slides in — the product, a photo tile, and a generate button. It's polite by design: it waits for the shopper's first activity, and once dismissed it never shows again for that shopper. Light or dark theme.

### The Fitting Room hub

A launcher-less entry for returning shoppers: a "Fitting room" link in your header or navigation opens a full panel with their saved wardrobe and your complete collection — no bubble needed anywhere. Two ways to add it: drop the **Ello Fitting Room** block into your header in the theme editor, or add a normal menu link whose address contains `ello-fitting-room` (for example `#ello-fitting-room`) — Ello binds it automatically, which also covers headers that don't accept app blocks.

### Which placements should you run?

| Setup | What's on | Best for |
| --- | --- | --- |
| The default | Inline button + bubble on non-product pages | Almost every store — decision on the PDP, discovery elsewhere |
| Photo-first | Corner chip + bubble on non-product pages | Visual brands that want the buy-button zone untouched |
| Quiet | Inline button only | Minimal themes; no floating elements anywhere |
| Full | Inline button + bubble everywhere + preview popup + Fitting Room link | Stores leaning into try-on as a signature feature |

### Common questions

**Q: Can I move the Try-On button somewhere else on the page?**
A: Yes. In the theme editor, the button block's Position setting switches from automatic (it finds your Add-to-cart button and sits under it) to manual, where it stays exactly where you placed the block. You can also move it onto the product photo as a corner chip from Widget Design.

**Q: Why isn't the floating bubble showing on my product pages?**
A: By default the bubble is off on product pages — the inline button owns them — and on for the rest of the store. You can turn it on for product pages in Widget Design → Fine-tuning → Floating widget.

**Q: What happens to the corner chip if my theme hides the product image?**
A: Ello detects it and automatically brings back the classic button below Add to cart, so there is never a product page without an entry point. It's still worth confirming one entry is visible after you switch placements.

**Q: Can shoppers open their saved looks without a product page?**
A: Yes — that's the Fitting Room hub: a header or menu link that opens the shopper's wardrobe and your full collection in a full panel. Add the Ello Fitting Room block to your header, or any nav link containing ello-fitting-room.

## Products: choose where Try-On appears

URL: https://ellotryon.com/docs/products-and-coverage · Updated: 2026-09-08

Scope try-on to the right products, turn it off for the ones that shouldn't have it, see what the catalog scan decided at a glance, and fix a garment's design side or a bag's carry style yourself.

**The short version:** Three coverage modes: whole catalog, selected products, or chosen collections — plus an on/off switch on every product, so a gift card or sticker can be excluded without leaving whole-catalog mode. Four tiles at the top say how many products Try-On is live on, how many the scan has read, how many get an extra view (front + back, or a bag's carry views), and how many need a look. Open any product to set where its design sits, how a handbag is carried (crossbody, shoulder, handheld, clutch), and which photo the render works from. Your corrections are never overwritten by later scans.

### Coverage modes

| Mode | What it does | When to use it |
| --- | --- | --- |
| Whole catalog | Try-On shows on every product on your Online Store (the default). | Catalogs that are mostly wearable — switch off the few exceptions per product. |
| Selected products | Pick specific products with the product picker. | Testing on bestsellers first, or curating a capsule. |
| By collection | Try-On shows on every product in the collections you choose. | The cleanest way to scope a mixed catalog — point it at your apparel collections. |

> **Scope try-on to wearable products:** If your catalog mixes clothing with non-wearable items — stickers, mugs, gift cards — either scope by collection or flip the switch off on those products. A try-on button on a gift card is a bad first impression for exactly the shopper you wanted to impress.

### Turning Try-On off for one product

Every product row has an on/off switch. Off hides the Try-On button on that product in every coverage mode, and the product shows up under the *Off* filter so you can find it again. This is the quickest fix for a handful of non-wearable items in an otherwise wearable catalog — no need to switch to selected products and hand-pick everything else.

### The health strip

Four tiles above the product list tell you the state of your catalog at a glance: **Try-On live on** (products shoppers can try on right now), **Auto-scanned** (products the catalog scan has read, and how many are still waiting), **Front + back** or **Carry views** (products that get an extra view), and **Needs a look** (products where the scan could not decide). Click a tile to filter the list to those products. Each product carries a one-word verdict — Ready, Front + back, Carry views, Needs a look, Not scanned, or Off — and a line saying what shoppers get and whether it was auto-detected or set by you.

> **"Needs a look" is not broken:** A product flagged Needs a look still renders today with a standard front view. The flag means the scan could not tell where a garment's design sits or how a bag is carried, so the better view is waiting on a one-tap answer from you. Open the product and pick — the flag clears immediately.

### Custom try-on photos

Renders work from each product's featured image by default. If another shot is clearer — front-facing, on a model, better lit — set it as the try-on photo for that product. This changes which image the render works from, not where Try-On appears. As a rule: the cleaner and more front-on the product photo, the better the render.

### Front and back: the print side

For products whose design lives on the back — back-print tees, hoodies, backpacks — Ello renders front and back views in a single generation, and shoppers flip between them. One render, one credit, two views. Ello scans your product photos to detect which side carries the design automatically; each product row shows what was detected ("design on front / back / front & back", auto-detected or set by you).

- **Where is the design on this product?** (Products → product row → Edit; default: Auto-detected) — Front / Back / Front & back / No design. Correct it if the automatic detection got a product wrong — your setting sticks and is never overwritten by later scans. Choosing Back or Front & back asks you for a photo of the back; until one is picked, shoppers see the front view only. The front photo you pick is the one the render works from.
- **How can shoppers carry it?** (Products → handbag row → Edit; default: Auto-detected from photos and listing text) — Crossbody / Shoulder / Handheld / Clutch — pick every way the bag can be worn. Two or more give shoppers a toggle between the strap view and the in-hand view; one gives a single view. The row also shows the size Ello read from your listing. Your choice is never overwritten by later scans.

### Bags: backpacks and handbags

**Backpacks** get the front-and-back treatment automatically: Ello detects a backpack from the product title (backpack, rucksack, knapsack, daypack) and one generation renders both views — the front with the straps worn over the shopper's own outfit, and the back showing the pack's outer face. If the catalog scan or your print-side setting names a strap-side photo and an outer-face photo, each view renders from the right one; with a single product image, both views come from it.

**Handbags** render the way they are carried. Ello reads each bag's product photos and listing text together to learn its carry options; a bag with a strap and handles gets two views from one generation — *Crossbody* (or *Shoulder*, when the strap is shorter) and *Handheld* — and the shopper flips between them on the result. Chain bags that double up get Crossbody and Shoulder; a chain pochette gets Crossbody and Clutch. A listed strap drop counts even when the photos show the bag without its strap. Bags with one way to carry them render a single view.

**Size comes from your listing.** When a handbag's description states its measurements — width, height, depth, handle drop, strap drop, in inches or centimeters, in any of the common phrasings — the render draws the bag at that scale on the shopper's body and places it where the strap drop puts it. Without stated measurements, the render works from the product photo alone. Both views still count as one try-on.

> **Correcting a bag:** For a backpack, the print-side setting is the control: *Front & back* keeps the two-view render (and lets you pick the strap-side and outer-face photos), *Front* or *No design* switches it to a single view. For a handbag, open the row and tick how it can be carried — Crossbody, Shoulder, Handheld, Clutch — and the render follows your choice from the next try-on. Manual settings are never overwritten by later scans.

> **If a back-print product renders oddly:** The usual cause is the print side: the product's main photo shows the back, but the setting says front (or the reverse). Fix it in the product row — details in [render quality issues](https://ellotryon.com/docs/render-quality-issues).

### Pushing changes live

Saves propagate to your storefront within about 30 seconds. The **Refresh widget** button at the top of the page forces it through in seconds — useful right after big catalog edits. If products are still waiting for the scan, **Scan catalog now** reads them in the background; reload the page a few minutes later to see what it found.

### Common questions

**Q: Can I enable try-on for only some of my products?**
A: Yes — Products offers three modes: whole catalog, selected products (pick them individually), or by collection (every product in the collections you choose). On top of any mode, every product has its own on/off switch, so a few non-wearable items can be excluded without changing the mode.

**Q: Which product image does the try-on render from?**
A: The featured image by default. You can override it per product with a custom try-on photo — pick the clearest, most front-facing shot. For back-print products you can set a photo for each side.

**Q: Does a front-and-back render use two credits?**
A: No. Both views come from a single generation — one render, one credit, two views the shopper can flip between.

**Q: Ello thinks my design is on the wrong side. How do I fix it?**
A: Open the product's row on the Products page and set the print side manually (Front / Back / Front & back / No design). Your correction sticks — automatic rescans never overwrite a manual setting.

**Q: Does Ello show the back of a backpack?**
A: Yes. Backpacks are detected from the product title and render front and back from one generation: the front view with the straps worn over the shopper's own outfit, the back view showing the pack's outer face. The shopper flips between them with the Front | Back toggle. One try-on, one credit.

**Q: How does Ello decide whether a handbag renders crossbody or handheld?**
A: It reads the product photos and the listing text together. A bag with a strap and handles renders both — Crossbody (or Shoulder, when the strap is shorter) and Handheld — from one generation, and the shopper flips between them. Stated dimensions (width, height, depth, strap and handle drop) set the bag's size in the render. To correct a specific bag, open its row on the Products page and tick how it can be carried; your choice is kept through every later scan.

## Set up Complete the Look

URL: https://ellotryon.com/docs/complete-the-look · Updated: 2026-08-25

Offer the matching piece the moment a try-on lands — layered onto the same photo, added to the cart in one tap. You curate every pairing; nothing is random.

**The short version:** Complete the Look shows a complementary item after each try-on, lets the shopper try it on too — layered on the same photo — and adds both to the cart in one tap. Pairings come only from what you curate in Shopify's free Search & Discovery app: no pairing set, no offer shown. Pick one of five intro styles to match your brand, and measure the order-value lift with the outfit test on the Proof page.

### How it works for shoppers

1. **A shopper tries a piece.** The try-on lands — on the product photo or in the panel, per your style.
2. **Ello offers the pair.** The complementary item you curated appears, in the intro style you chose.
3. **They try it on too.** One tap layers the second piece onto the same photo of them — now they're wearing the outfit.
4. **Both go in the cart.** "Add both to cart" with the live total. Pieces can be toggled off, and the cart follows the selection.

### Step 1 — Curate your pairings

Pairings come from **Shopify Search & Discovery** (Shopify's free app): set *complementary products* there, and Ello reads exactly those selections. Widget Design links you straight to it. If a product has no pairing set, no offer is shown for it — deliberately. A wrong pairing costs trust; no rail beats a bad rail.

> **Curate like an outfit, not a category:** The best pairings complete an outfit: the shorts for that tee, the jacket over that dress. Start with your top ten products and give each one intentional pair — that covers most of your try-on traffic.

### Step 2 — Choose how the offer appears

| Intro style | The feel |
| --- | --- |
| The Pairing | One floating piece: a quiet label, the item, one ask. No price up front. |
| The Whisper | Just a tiny chip. Tapping it unfolds the full offer — the shopper opts in. |
| The Drop | The product lands with a price tag and a button. Playful, product-first. |
| The Row | A slim shop-the-look bar along the photo's bottom edge. The photo stays clean. |
| Classic | The original full-width card with name and price. |

- **Keep the offer inside the try-on panel** (Widget Design → The upsell; default: Off) — Shown when Complete the Look is on and you use the on-photo style: one surface instead of two — the result and the offer stay in Ello's panel, and your product photo is never repainted.

### Step 3 — Prove it lifts order value

Want the causal number, not a hunch? The outfit test on the [Proof page](https://ellotryon.com/docs/proof-test) splits shoppers 50/50 — with the offer and without — and reports average-order-value lift with statistical confidence, from your own orders.

### Common questions

**Q: Why isn't the Complete the Look offer showing?**
A: Three usual causes: the toggle is off in Widget Design; the product the shopper tried on has no complementary products set in Shopify Search & Discovery (no pairing means no offer, by design); or an outfit test is running and that shopper is in the without-offer group.

**Q: Where do the suggested products come from?**
A: From you. Ello reads the complementary-product selections you set in Shopify's free Search & Discovery app — exactly those, nothing algorithmically random.

**Q: Does trying on the suggested item cost another credit?**
A: Yes — layering the second piece is a real render, so it uses a try-on like any other. Taking pieces off afterwards is instant and free (Ello restores earlier snapshots rather than re-rendering).

**Q: Can shoppers buy the whole outfit at once?**
A: Yes. The result shows one adaptive button — "Add both to cart" with the live total — and if the shopper toggles a piece off, the button and price follow the selection.


---

# Measure results

## Reading your Analytics

URL: https://ellotryon.com/docs/analytics-overview · Updated: 2026-08-25

A tour of the Analytics page: the headline numbers, the four tabs, what every metric means, and the one mistake to avoid when reading per-product revenue.

**The short version:** Analytics leads with what matters — attributed revenue, buy rate after try-on, opens, and try-ons — then breaks the story into four tabs: Funnel (where shoppers drop off), Performance (which products and pages work), Engagement (how deeply shoppers use it), and Preview widget. The attribution window is adjustable (7, 14, or 30 days) and every stat is labeled with it. Read the store-level revenue number as the headline; never sum the per-product rows.

### The headline band

The top of the page answers "is this working?" in one line — try-ons drove $X in sales, up or down vs the prior period — and flags your weak spot: the funnel step with the biggest drop-off. Under it, four tiles:

| Tile | Definition |
| --- | --- |
| Attributed revenue | Sales of tried-on items, counted under the attribution rules — same shopper session, order within your attribution window, only the tried-on line at the price actually paid, refunds netted. The strict version of the story. |
| Buy rate after try-on | The percentage of try-on sessions that went on to purchase. |
| Shoppers who opened it | Widget opens in the period — every open counts; unique sessions are shown separately in the Funnel tab. |
| Total try-ons | Renders in the period, with successful ones counted separately. Failed renders release their credit and don't count. |

### The attribution window control

Next to the time range you can set how long after a try-on an order still counts: **7, 14, or 30 days**. Every stat is labeled with the window in effect, so numbers are never ambiguous. Billing statements always stay on the standard 7-day basis regardless of what the dashboard shows — the dial changes your analytics view, never your invoice. Full mechanics in [how attribution works](https://ellotryon.com/docs/how-attribution-works).

### The four tabs

*The session funnel: widget opens, then try-ons, then cart adds, then purchases — each step a smaller share, and the biggest drop is where your attention should go.*

- **Funnel** — daily activity, the conversion funnel (opens → try-ons → carts → purchases), activation and bounce rates, photo-upload friction (how many uploads start, succeed, and fail — grouped by reason), purchases, first-time-shopper cohorts, and the mobile/desktop split.
- **Performance** — most tried-on products, a per-product table (try-ons, carts, conversion, revenue), which page types try-ons happen on (product, collection, home, cart), which entry points start them (inline button, bubble, preview popup), and fit-risk products — items tried a lot but bought rarely, worth a look at photos or pricing.
- **Engagement** — open-to-try-on rate, average try-ons per session, multi-try sessions, engagement over time, and a peak-times heatmap.
- **Preview widget** — impressions, engagement, and completions for the desktop preview popup, so you can judge whether it earns its place.

> **Never sum the per-product rows:** The per-product view is product-influenced: an order containing two tried-on items is credited under each of them, so the rows intentionally add up to more than the store total. The store-level number is order-deduplicated — that's the headline. The two won't match, by design.

### Exports

Export CSV offers five raw datasets for your own analysis: try-on events, widget events, cart events, purchases, and aggregated sessions — each scoped to the selected time range.

> **On the Free plan:** Free includes the core layer — the headline band and funnel basics. Engagement, Preview, and the advanced Performance views unlock on paid plans, and because everything is tracked from day one, upgrading reveals your full history immediately.

### Common questions

**Q: What exactly counts as attributed revenue?**
A: A shopper ran a successful try-on and then bought that same product within the attribution window, in the same shopper session. Only the tried-on line items count, at the discounted price actually paid — never shipping, taxes, or the rest of the cart — and refunds are subtracted when they happen.

**Q: What's the difference between widget opens and unique sessions?**
A: Opens count every time the widget is opened; unique sessions count distinct shopper sessions that opened it at least once. Device splits use distinct sessions, not raw opens.

**Q: Why is my per-product revenue total bigger than the store total?**
A: Per-product rows are product-influenced — a multi-item order is credited under each tried-on item in it — while the store total is order-deduplicated. Read the store total as the headline; use per-product rows for ranking, not summing.

**Q: Can I change how far out a purchase still counts?**
A: Yes — the attribution window selector offers 7, 14, or 30 days, and every stat labels the window in effect. Invoices and billing statements always use the standard 7-day basis regardless of the dashboard setting.

**Q: What is a fit-risk product?**
A: A product tried on frequently but purchased rarely — at least five try-ons with a conversion rate at half your store average or less. It's a signal to check that product's photos, description, or pricing.

## How attribution works

URL: https://ellotryon.com/docs/how-attribution-works · Updated: 2026-08-25

The exact rules behind every revenue number Ello shows you — strict enough to hand to a CFO, and auditable down to the Shopify order ID.

**The short version:** A dollar is attributed only when the same shopper session tried on a product and then bought that same product within the window. Only the tried-on line counts, at the discounted price actually paid — never shipping, tax, or the rest of the cart. Refunds within 45 days come back off automatically. Every attributed sale carries its Shopify order ID, and attribution is never used to claim lift — that's the Proof test's job.

*A shopper tries on the tee, then orders the tee plus an untried tote. Only the tee's discounted line price is attributed — the tote, shipping, and tax never count.*

### The four rules

1. **Same shopper, same session.** The try-on and the purchase happen in one shopper session. No cross-device guessing, no lookalike modeling.
2. **Try-on first, purchase after.** Events are ordered by time. A try-on after checkout counts for nothing.
3. **The tried-on product is in the order.** The order must contain the exact product that was tried on, matched at the line-item level.
4. **Within the window.** The order lands within the attribution window — 7 days on the standard (and invoice) basis; your analytics view can widen to 14 or 30 days, always labeled.

### What gets counted — and what never does

| Counts | Never counts |
| --- | --- |
| The tried-on line items, at the discounted price actually paid — if a code took the $40 tee to $32, Ello attributes $32 | Shipping, taxes, and every untried item in the cart |
| Orders tied to a real Shopify order ID — the Receipts table lists every one, exportable | View-through conversions, modeled or projected revenue, industry benchmarks dressed as store numbers |
| Net figures, after refunds | Refunded value — a tried-on item refunded within 45 days is subtracted automatically |

### Attribution is not lift

Attributed revenue answers "how much revenue flowed through try-on?" — an association. Some of those shoppers might have bought anyway; try-on users are higher-intent by nature. That is why lift is only ever claimed from the [Proof test](https://ellotryon.com/docs/proof-test), where a real control group of your own shoppers browses without try-on. Ello keeps the two numbers separate on purpose.

> **Auditing your numbers:** The Receipts table on the Proof page lists every attributed order with the product tried on, the timestamps, and the order value — matched to Shopify order IDs you can open yourself. Stores on revenue-share deals also get a Billing statement page where every billed line is itemized the same way.

### Common questions

**Q: Does Ello count the whole order when one tried-on item is in it?**
A: No. Only the tried-on line items count, at the discounted price actually paid. A $111 order containing a $38 tried-on shirt attributes $38 — the untried tote, shipping, and tax are excluded.

**Q: What happens when a tried-on item is refunded?**
A: Refunds within 45 days of purchase are subtracted from attributed revenue automatically, via Shopify's refund webhooks. The number you see (and any revenue-share invoice) is the net one.

**Q: How long is the attribution window?**
A: 7 days on the standard basis, which is also what invoices use. In Analytics you can view 7, 14, or 30 days — every stat labels which window it's on. Most attributed purchases actually land the same day as the try-on.

**Q: Is attributed revenue the same as revenue Ello generated?**
A: No — and Ello won't pretend it is. Attribution measures association (tried on, then bought). Causal lift is measured separately by the Proof test's holdout, where part of your traffic browses without try-on as a control.

## The Proof test (A/B holdout)

URL: https://ellotryon.com/docs/proof-test · Updated: 2026-08-25

A slice of your shoppers browses without try-on. Every lift number is measured against them — causation on your own store, not a vendor claim.

**The short version:** Start the Proof test and a percentage you choose (10% recommended) of shoppers never sees any Ello surface — they're the control. The dashboard compares conversion with vs without try-on and only calls a verdict at 95% statistical confidence with at least 200 sessions in each group and 10 buyers between them. If Complete the Look is on, an outfit test rides along measuring order-value lift. Past tests are kept forever.

*The holdout split: most shoppers see try-on, a fixed slice never does. Comparing the two groups' purchase rates is what makes the lift number causal.*

### How the test works

- **Assignment is deterministic and sticky.** Each shopper session is bucketed by a stable algorithm — the same shopper stays in the same group for the whole test, so nobody flickers between seeing and not seeing try-on.
- **Holdout shoppers see nothing.** Not a hidden button — no Ello surface at all. They shop your store exactly as it was before Ello.
- **Both groups count every visitor** from their first page. That's what makes the comparison fair — and it's why both percentages sit below Shopify's product-page conversion figure. For Shopify comparisons, use the "On product pages" figure shown alongside.
- **Their purchases count fully.** Holdout shoppers aren't lost sales — they're the measurement. That's the whole point of a control group.

### Starting a test

1. **Open the Proof page.** Pick a holdout size: 5%, 10% (recommended), 20%, or 50%. Bigger holdouts reach a verdict faster but show try-on to fewer shoppers.
2. **Start it the day you go live, ideally.** The earlier it starts, the sooner the sample builds. Promote try-on to your list during the test — the test stays fair because promotion reaches both groups.
3. **Let it run.** Stop any time; every past test is kept forever in the history dropdown, and selecting one re-reads the whole page over that test's window.

### When does it call a verdict?

The lift verdict unlocks only when the math is real: **95% statistical confidence**, with at least **200 sessions in each group and 10 buyers across the two**. Until then the page says it's still collecting — deliberately. A small store may take weeks to get there; that isn't the test failing, it's the test refusing to guess.

> **Why your test percentages look lower than Shopify's:** Shopify's conversion rate usually divides by sessions that reached a product page; the Proof test divides by all visitors in each group, from their first page, because that's the fair basis for a controlled comparison. The Proof page also shows an "On product pages: X of Y bought" figure for apples-to-apples reading.

### The outfit test (order-value lift)

If [Complete the Look](https://ellotryon.com/docs/complete-the-look) is on when you start the Proof test, a 50/50 outfit test rides along automatically: half the exposed shoppers get the outfit offer, half don't, and the dashboard reports average-order-value lift with its own confidence gates. One holdout, every answer. It can also run standalone from the Proof page.

### Returns and Receipts

- **Returns** — do tried-on items come back less often? The page compares your store-wide return rate against tried-on-before-buying items, from your own orders and refunds — not an industry stat.
- **Receipts** — every attributed order in a table (order, product tried on, time from try-on to purchase, order value), exportable as CSV, each row tied to a Shopify order ID.

### Common questions

**Q: Do holdout shoppers hurt my sales?**
A: They shop normally — they just don't see try-on, exactly like every shopper before you installed Ello. Their purchases count fully. A 10% holdout means 90% of traffic gets the feature while the test runs.

**Q: How long until I get a verdict?**
A: The verdict unlocks at 95% confidence with at least 200 sessions in each group and 10 buyers across the two. How fast you get there depends on traffic — days for a high-traffic store, weeks for a small one. The test won't call it early, on purpose.

**Q: Why does the test show lower conversion than my Shopify analytics?**
A: Different denominators. The test counts every visitor in each group from their first page (the fair basis for a controlled comparison); Shopify typically measures shoppers who reached a product page. Use the test's "On product pages" figure for direct comparison.

**Q: Can I run the test more than once?**
A: Yes. Stop and start tests whenever you like — every past test is kept forever, and you can re-open any of them to see its full results over its own window.

**Q: Is the incremental revenue number exact?**
A: It's computed from the conversion-rate difference and deliberately floored — presented as a floor, not a ceiling. Ello would rather understate lift than inflate it.


---

# The shopper experience

## What your shoppers see

URL: https://ellotryon.com/docs/what-shoppers-see · Updated: 2026-08-25

The full journey from the shopper's side — first visit, photo, render, outfits, wardrobe, and checkout — so you know exactly what you've turned on.

**The short version:** First-timers get a three-beat welcome — your photo, the item, the try-on — then upload a photo or pick a sample model. The render lands in seconds with an add-to-cart button at the real price. Every look saves automatically to an on-device Wardrobe, outfits build across product pages with instant take-off, and browse inside the widget covers your whole enabled catalog with a search that tolerates typos.

*The shopper journey: photo (or sample model) → pick an item → the render lands → add to cart. Every result auto-saves to their wardrobe.*

### The first visit

The first time a shopper opens the try-on on your store, a short welcome screen sets expectations — see it on you, instantly — with two clear paths: **Use My Photo** or **Use a Model** (a small roster of sample models, for shoppers not ready to upload). A quiet consent line links your shoppers to the terms and privacy policy. If you've turned on Photo guidance, the three photo essentials appear right there — fitted clothing, full body, good lighting — as one line with a see-examples link, never a pop-up.

### Photo upload

On phones, shoppers choose camera or gallery; on desktop, a file picker. Ello checks the photo — file type, size, and a body check that needs shoulders and hips visible — and gives specific, friendly feedback rather than a generic error. The photo is remembered on their device, so return visits skip straight to trying things on. Full details in [photo guidelines](https://ellotryon.com/docs/photo-guidelines).

### The render

Generation takes seconds. A progress screen shows both images — the product and their photo — with rotating tips while they wait. The result keeps the shopper's own photo framing (no cropped heads or feet), and for back-print products it arrives with a front/back toggle. With a saved photo, tapping Try On on any product fires immediately — one tap, zero extra screens.

### Where the result lands

Per your [Widget Design](https://ellotryon.com/docs/widget-design) style: on the product photo itself (the photo becomes them wearing it, original a tap away) or inside Ello's panel. Either way the result carries an **Add to Cart** button with the live price and a size picker when the product needs one. Adding to cart uses your theme's own cart — count updates, drawer opens if your theme does that — without reloading the page, so the result stays on screen.

### Outfits: build, layer, take off

Shoppers can layer pieces across product pages — try the tee, open the shorts, add them on top. A "your look" row shows each piece as a chip; tapping a piece takes it off *instantly* (Ello restores the earlier image rather than re-rendering — taking off is free and immediate). The add-to-cart button adapts to the selection: add one piece, add both, add the look, with a live total.

### The Wardrobe

Every result saves automatically to My Wardrobe — stored on the shopper's own device, with no item caps. It holds their photo, every saved look (front and back where applicable), and full outfits as editable cards: reopen a look, toggle pieces, add to cart from the wardrobe viewer. It's the reason return visits convert — the fitting room remembers.

### Browse and search inside the widget

The widget includes your full enabled catalog: a Featured product and Quick picks you can pin (or Ello curates), category chips, price sort, sold-out badges, and a search that handles word order, plurals, misspellings, and synonyms — "sweatshirt" finds hoodies. A dead-end search never strands anyone: no-result screens offer popular picks.

> **What Ello never does to your page:** The widget never moves, covers, or re-wires your theme's buy box; its styles are isolated so they can't leak into your theme; new features ship off by default; and if anything fails to load, Ello hides itself rather than showing your shoppers an error.

### Common questions

**Q: Do shoppers have to upload a photo?**
A: No. The welcome screen offers sample models, so shoppers can see the product on a model instantly and upload their own photo whenever they're ready. Uploading their own photo is what makes the experience personal, so most engaged shoppers do.

**Q: Do shoppers need to create an account?**
A: No account, no login, no email required. Their photo and wardrobe live on their own device. Email is only requested if you enable the optional lead-capture prompt, and it never blocks the result.

**Q: Does the try-on show how a garment will fit?**
A: No — and we're direct about that. Ello shows the look: the item on the shopper's own photo, their framing preserved. It doesn't measure bodies or predict size, so the widget notes that body shapes and personal features may not be represented exactly.

**Q: What happens on a slow connection or an ad blocker?**
A: The widget loads lazily so it never slows your page, and if it can't load at all it hides itself completely — your product page looks exactly as it would without Ello, never broken.

**Q: Can shoppers share or save their try-on?**
A: Every render lands in their on-device Wardrobe automatically and stays there across visits. From the result they can save the look, keep building an outfit, or add to cart.

## Photo guidelines: what renders best

URL: https://ellotryon.com/docs/photo-guidelines · Updated: 2026-08-25

Three essentials cover almost everything — and the widget coaches shoppers through the rest. Here's exactly what's checked, what's rejected, and why.

**The short version:** The three essentials: fitted clothing, full body, good lighting. The only hard rejection is a photo with no visible body (shoulders to hips required — except on shoe pages, where feet in frame is what matters). Everything else — brightness, resolution, framing — produces friendly advice, not a block. You can surface the essentials to first-time shoppers with the Photo guidance switch in Widget Design.

*What works: a full-body, front-facing photo in even lighting with fitted clothing. What struggles: sitting, facing away, baggy layers, harsh shadows, busy backgrounds.*

### The three essentials

1. **Fitted clothing.** The render replaces what the shopper is wearing — fitted clothes give the model a clear read of their silhouette. Baggy layers over the outfit area are the most common cause of odd results.
2. **Full body.** Shoulders to hips must be visible; head-to-toe is better. Full-body framing is also what lets the result keep natural proportions.
3. **Good lighting.** Even, reasonably bright light. Harsh shadows and backlighting cost detail exactly where the garment needs it.

### What the widget checks

| Check | What happens |
| --- | --- |
| File type & size | JPEG, PNG, WebP, or GIF, up to 10MB. Anything else gets a clear message. Photos are compressed on the shopper's device before upload, so normal phone photos are always fine. |
| Brightness, contrast, resolution, framing | Advisory only — the shopper sees a specific tip ("low contrast", "use a full-body portrait") but is never blocked. Real photos are imperfect; blocking them costs try-ons. |
| Body detection | The one hard gate: if no body is detected (shoulders + hips), the photo is rejected with a friendly ask for another one. This runs on the shopper's device. |
| Shoe pages | The body check relaxes — a legs-and-feet photo passes, and the copy switches to "upload a photo with your feet visible." |

### The full tips list (what shoppers see in "Photo tips")

- **Good:** full body · good lighting · just you in frame · no hands in pockets · plain background · fitted clothing · high resolution.
- **Avoid:** sitting down · facing backwards · baggy clothes · harsh shadows · busy backgrounds · low resolution.

> **Turn on Photo guidance:** In Widget Design, the Photo guidance switch shows first-time shoppers the three essentials right on the welcome screen — one quiet line with a see-examples link. It's informational, never a gate: we tested a mandatory tips screen and it cost roughly a third of shoppers between tap and upload, so Ello will never block the flow with advice.

> **The honest limitation:** Ello depicts the look; it doesn't measure the body. The widget says so to shoppers: body shapes and personal features may not be represented exactly. Never present try-on as a sizing tool — it's a confidence tool.

### Common questions

**Q: Why was a shopper's photo rejected?**
A: The only hard rejection is the body check: shoulders and hips must be visible. Sitting, heavy cropping, or facing fully away are the usual causes — the fix is a standing, full-body photo. On shoe product pages the check relaxes so feet-visible photos pass.

**Q: Is there a photo size limit?**
A: Files up to 10MB are accepted, and photos are compressed on the shopper's device before upload — a normal phone photo, front or back camera, is always within bounds.

**Q: Do dark or low-resolution photos get blocked?**
A: No — quality checks are advisory. The shopper gets a specific tip about what to improve, but the try-on proceeds. Only a photo with no detectable body is turned away.

**Q: What photo advice should I give my own customers?**
A: The three essentials: fitted clothing, full body, good lighting. If you want Ello to deliver that message for you, turn on Photo guidance in Widget Design — first-timers see it on the welcome screen.

## Shopper photos, privacy, and data

URL: https://ellotryon.com/docs/privacy-and-data · Updated: 2026-08-25

Where photos live, what Ello stores and what it deliberately doesn't, and how data is deleted — written to be shown to your own customers if they ask.

**The short version:** Shopper photos and saved looks live on the shopper's own device. For each render, the photo is sent to the try-on model to generate the image and is not persistently stored on Ello's servers — Ello keeps anonymous usage events, not photos. Consent is presented at upload, the camera-based live mirror asks explicitly, and Shopify's GDPR deletion webhooks are fully implemented: uninstall the app and your event data is purged.

### Where the photo lives

- **On the shopper's device.** The uploaded photo and every saved look in the Wardrobe are stored in the shopper's own browser. Clearing browser data removes them; there is no server-side copy of the wardrobe.
- **Per render, in transit.** When a try-on runs, the photo is sent to the AI model to generate the result image, and the result comes back. Ello does not persistently store the photo or facial/body geometry on its servers.
- **The body check runs locally.** The is-there-a-person check happens in the shopper's browser, before anything is uploaded.

### What Ello does store

Anonymous usage events: a random session identifier (no name, no email, no account), which products were tried on, which pages and entry points were used, and cart/purchase events for attribution. This is what powers your analytics. Emails exist only if you enable the optional lead-capture prompt — and shoppers are told plainly: no spam, unsubscribe anytime.

### Consent, plainly presented

- **Photo upload:** a notice at every upload point — by uploading, the shopper agrees to the terms and privacy policy, linked right there.
- **Live Try-On (if you've enabled it):** explicit, active consent before the camera turns on, with plain-language disclosure: the camera streams securely to the AI partner, and the replay stays on the shopper's device and disappears when they close the mirror.

### Deletion and GDPR

| Event | What happens |
| --- | --- |
| Shopper clears browser data | Photo and wardrobe are gone — they only ever lived on the device. |
| Photo fails the body check | Any previously saved photo is actively cleared, not just ignored. |
| Customer data request / redact (GDPR) | Handled via Shopify's official privacy webhooks, verified and automated. |
| You uninstall Ello | Shopify sends the shop-redact webhook (~48h later) and Ello purges the store's event data — try-ons, widget events, carts, purchases, exposures. Retention is simple: kept while you have the app, deleted after. |

> **If a customer asks you about their photo:** The honest one-liner: "Your photo stays on your device; it's sent once per try-on to generate the image and isn't stored on the servers." The full policy lives at [ellotryon.com/legal](https://ellotryon.com/legal?tab=privacy).

### Common questions

**Q: Does Ello store my customers' photos?**
A: No. The photo is forwarded to the try-on model to generate the result image and is not persistently stored on Ello's servers. The shopper's photo and saved looks live in their own browser, on their own device.

**Q: Is Ello GDPR compliant for my store?**
A: Ello implements all three of Shopify's mandatory privacy webhooks — customer data request, customer redact, and shop redact — with verification. Uninstalling the app triggers a purge of the store's event data.

**Q: Does Ello collect my customers' emails?**
A: Only if you turn on the optional lead-capture prompt, which asks after a number of try-ons you choose and never blocks the result. Captured emails are listed on the Leads page with CSV export.

**Q: Can shoppers use the try-on without being tracked personally?**
A: Shoppers are identified only by a random session ID — no name, email, or account. That anonymous ID is what connects a try-on to a later purchase for your attribution.


---

# Troubleshooting

## The widget isn't showing

URL: https://ellotryon.com/docs/widget-not-showing · Updated: 2026-08-25

Nine causes cover essentially every case — run this checklist top to bottom and you'll find yours.

**The short version:** Check in this order: you're on the live store (not the editor preview) · the app embed is on and saved · the button block is added · the master switch is on · the product is enabled for try-on · a Proof test isn't hiding it for you on purpose · the placement didn't move it · your settings just haven't propagated yet · an ad blocker isn't eating it. The app's Home page shows live theme status for the first two.

### Run the checklist

1. **Are you on the live storefront?** The theme-editor preview is not the real page — placement and the app embed behave differently there. Open your store in a normal tab (an incognito window is even better; it also sidesteps stale caches and your own holdout bucket).
2. **Is the app embed on — and saved?** The number-one cause. Shopify theme editor → App embeds → Ello Virtual Try-On must be toggled on *and saved*. Ello's Home page reads your live theme and shows this status with a one-click fix link; it even detects the embed being present but toggled off.
3. **Is the Try It On button block added?** Second theme step: the button block must be in your product-page template. Home shows this too, with an add-button deep link.
4. **Is the master switch on?** Widget Design → the toggle at the top. "Try-On is hidden" pauses everything everywhere; it's easy to forget after a theme change.
5. **Is this product enabled?** If coverage is set to selected products or collections, the button hides on everything else — and the floating bubble's smart mode hides on those pages too. Check the Products page; the summary line says exactly what's covered.
6. **Is a Proof test running?** During a holdout test, a slice of shoppers — possibly including you — deliberately sees no Ello surface at all. That's the control group working. Add `?ello_preview=1` to the product-page URL to always see the widget regardless of test bucket.
7. **Did the placement move it?** With the corner-chip placement on, the button lives on the product photo, not under Add to cart. If the theme hides the photo from Ello, the classic button returns automatically — but confirm one of the two is visible.
8. **Did your change just not propagate yet?** Settings reach shoppers within about 30 seconds, and your own browser may hold a cached config. Hard-refresh the page (Cmd/Ctrl+R) or use `?ello_preview=1`. See [changes not appearing](https://ellotryon.com/docs/changes-not-appearing).
9. **Ad blocker or privacy extension?** Some block the widget's domain (widget.ellotryon.com). Ello fails invisible by design — no error is ever painted on your page — so a blocked load looks like "nothing there." Test in a clean incognito window with extensions off.

> **Why Ello hides instead of erroring:** On any load failure, Ello empties and hides its container rather than showing your shoppers a broken element. Good for shoppers — but it means "widget missing" is the symptom for every cause above, which is why the order of this checklist matters.

> **Still missing after all nine?:** Email [andrew@ellotryon.com](mailto:andrew@ellotryon.com) with your store URL and a product-page link. Headless and heavily customized storefronts sometimes need a store-level adjustment on our side — it's usually a same-day fix.

### Common questions

**Q: The try-on button shows and then disappears after a second — why?**
A: That's the catalog gate: the button renders, then hides once Ello confirms this product isn't enabled for try-on. Enable the product (or its collection) on the Products page and it will stay.

**Q: The widget shows for me but a customer says they can't see it. Who's right?**
A: Probably both of you. If a Proof test is running, a slice of shoppers deliberately sees no try-on — that's the control group. Ad blockers are the other common cause. If analytics show steady try-on activity, the widget is working.

**Q: Does the widget work in the Shopify theme editor preview?**
A: The editor preview is not a reliable test — blocks render in design mode and the embed state can differ from the published theme. Always verify on the live storefront.

**Q: I switched themes and the widget vanished. What do I re-do?**
A: App embeds and blocks are per-theme: turn on the Ello app embed and re-add the Try It On button block in the new theme. Ello's Home page will show both as missing and deep-link the fixes.

## My changes aren't appearing

URL: https://ellotryon.com/docs/changes-not-appearing · Updated: 2026-08-25

You saved a setting and the storefront looks the same. Almost always, that's caching doing its job — here's how to see your change right now.

**The short version:** Saved settings reach shoppers within about 30 seconds, but your own browser may hold a cached copy a little longer. Hard-refresh the product page, or add ?ello_preview=1 to the URL for a guaranteed-fresh look. After big catalog edits, the Refresh widget button on the Products page forces everything through in seconds.

### How changes propagate

Ello caches your widget configuration close to shoppers so product pages stay fast. Every save bumps your store's config version, and shopper browsers pick up the new version within about 30 seconds on their next page view. Returning visitors also keep an instant local copy — refreshed the same way.

### See your change immediately

1. **Hard-refresh the product page.** A reload (Cmd/Ctrl+R) tells Ello to skip every cache and fetch your live settings. This is the everyday answer.
2. **Or use the preview flag.** Add `?ello_preview=1` to any product-page URL. It always fetches fresh settings, always shows the widget (even inside a holdout test), and logs nothing to your analytics — the clean way to check work-in-progress.
3. **After catalog changes, use Refresh widget.** The button at the top of the Products page pushes catalog and settings changes through every cache within seconds — the strongest lever, best after enabling products or changing coverage.

> **The dashboard preview is always current:** Widget Design's live preview reads your unsaved edits directly, so it can be ahead of your storefront by design: preview shows the future, the storefront shows the last save (within ~30 seconds). If the preview looks right and the store doesn't, you're just waiting on the cache — or you haven't hit Save.

### Common questions

**Q: How long until shoppers see a saved change?**
A: About 30 seconds, applied on their next page view. Your own browser can hold a local copy slightly longer — a hard refresh clears it instantly.

**Q: What exactly does ?ello_preview=1 do?**
A: It forces a fresh settings fetch, always shows the widget regardless of any running holdout test, and excludes the session from your analytics and experiments — so you can verify changes without polluting your data.

**Q: I enabled a product but its page still has no button. Now what?**
A: Hit Refresh widget on the Products page (pushes catalog changes in seconds), then hard-refresh the product page. If it's still missing, run the widget-not-showing checklist — coverage mode is the usual culprit.

## Fixing render quality issues

URL: https://ellotryon.com/docs/render-quality-issues · Updated: 2026-08-25

When a try-on looks wrong, the cause is almost always one of four things — the shopper's photo, the product's photo, the print side, or the product type. Each has a fix.

**The short version:** Work through the four causes in order: the shopper's photo (fitted clothing, full body, good lighting fix most complaints), the product photo (renders work from it — set a cleaner one on the Products page), the print side (back-design products need the front/back setting right), and the product type (simple silhouettes render best; exact fit is out of scope by design). Results always keep the shopper's photo framing — heads and feet never crop.

### Cause 1 — The shopper's photo

Most "the render looks off" reports trace to the input: baggy layers over the outfit area, sitting poses, heavy crops, harsh shadows. The render can only be as good as what it can see. The fix is the [three essentials](https://ellotryon.com/docs/photo-guidelines) — and turning on Photo guidance in Widget Design so first-time shoppers get them before uploading.

### Cause 2 — The product's photo

Renders work from the product image, so a cluttered, angled, or back-view product shot produces a weaker result than a clean, front-facing one. On the Products page you can set a custom try-on photo per product — pick the clearest front-on shot, ideally on a plain background. This is the highest-leverage fix for a specific product that consistently renders poorly.

### Cause 3 — The print side

If a back-print product renders with the design missing, doubled, or on the wrong side, the print-side setting is the fix. Ello auto-detects which side carries the design from your photos, but detection can be wrong on unusual shots. Set it manually in the product's row — Front / Back / Front & back — and pick the best photo for each side. Your setting sticks. Details in [products and coverage](https://ellotryon.com/docs/products-and-coverage).

### Cause 4 — The product type

| Renders best | Needs care |
| --- | --- |
| Tops, tees, dresses, outerwear, hats — clear silhouettes with clean product photos | Heavily layered or complex garments — occasionally a piece in a stacked outfit edit needs a re-try |
| Front-and-back print products with the print side set correctly | Products with intricate all-over back graphics — verify a render before featuring them |
| Shoes on their own product page (feet-visible photos) | Exact-fit questions — Ello depicts the look; it never measures fit or size, on any product |

### Things that are already handled

- **Cropped heads or feet:** results keep the shopper's own photo shape, and on-photo results are letterboxed into your theme's image box rather than stretched or cropped. If you ever see cropping, report it — that's a bug, not a setting.
- **Color drift:** renders preserve garment color (pale pink stays pale pink). Variant-specific try-ons render the exact color the shopper picked.
- **Failures:** a failed render releases its credit automatically, and an automatic fallback engine keeps try-ons running if the primary engine has a bad moment.

> **A quick product audit:** Before featuring try-on on a product — in an email, on socials — run one yourself on that product. Thirty seconds tells you whether the product photo and print side are set up to shine.

### Common questions

**Q: A specific product always renders badly. What's the fastest fix?**
A: Set a custom try-on photo for it on the Products page — the clearest, most front-facing shot you have. If it's a back-print product, check the print-side setting too. Those two fixes resolve most per-product complaints.

**Q: Why did the back of my hoodie come out garbled?**
A: Usually the print side: the product's main photo shows the back, but Ello is treating it as a front. Set the print side manually on the product's row and assign the right photo to each side — back designs then render as a proper front/back pair.

**Q: Does Ello crop the shopper's head or feet off?**
A: No — aspect-ratio fidelity keeps the shopper's original photo framing, and on-photo results are letterboxed into the theme's image box rather than cropped. If you see cropping, something is wrong; contact support.

**Q: Can shoppers re-run a try-on they don't like?**
A: Yes — each try-on is independent, so they can simply run it again (each run uses a credit within their daily limit). A better photo, per the guidelines, is usually what improves the result.


---

# Reference

## Glossary: every term, defined

URL: https://ellotryon.com/docs/glossary · Updated: 2026-08-25

The exact meaning of every term you'll meet in Ello's dashboard and docs — so a number is never ambiguous.

**The short version:** Precise definitions for every Ello term: try-on, session, attributed revenue, attribution window, holdout, placement, app embed, wardrobe, overage, and the rest. When a dashboard number surprises you, start here.

| Term | Definition |
| --- | --- |
| Try-on | One AI generation placing a product on the shopper's photo. A front-and-back render for a back-print product is still one try-on and one credit. Failed renders release their credit and don't count. |
| Widget open | The shopper opening the try-on experience. Counted per event; unique sessions are deduplicated separately. |
| Session | A shopper's identity window — a random anonymous ID with a 7-day sliding lifetime (extended if your attribution window is 14 or 30 days). It connects opens, try-ons, and purchases without any personal information. |
| Attributed revenue | Revenue from orders where the same session tried on a product and then bought that product within the attribution window — tied at line-item level, at the discounted price actually paid, order-deduplicated, refunds netted. Also called qualified revenue. |
| Attribution window | How long after a try-on an order still counts: 7 days standard (and always the invoice basis); viewable at 7/14/30 days in Analytics, labeled. |
| Buy rate after try-on | The share of try-on sessions that purchased. Sometimes shown as try-on → purchase. |
| Holdout / Proof test | A deterministic slice of shoppers who never see any Ello surface — the control group. Lift = exposed vs holdout, with a verdict gated at 95% confidence, 200 sessions per group, and 10 buyers across the two. |
| Outfit test | The same holdout mechanism pointed at order value: with vs without the Complete the Look offer, reporting average-order-value lift. |
| Placement | Where the try-on entry lives: inline button below Add to cart, corner chip on the product photo, or the floating bubble — plus where results land (product photo or panel). |
| App embed | The Shopify theme-editor toggle that loads Ello on your storefront. Required, along with the button block, for the widget to appear. |
| Complete the Look | The post-try-on complementary-item offer, fed only by your Shopify Search & Discovery curation. Intro styles: Pairing, Whisper, Drop, Row, Classic. |
| Wardrobe | The shopper's saved looks — stored on their own device, uncapped, with editable outfit cards. |
| Fitting Room hub | A launcher-less entry (header block or nav link) opening the shopper's wardrobe and your full collection. |
| Overage | Opt-in billing for try-ons beyond your plan's allowance: $0.15 each, up to a spend cap you approved. Off by default — the default at your limit is a pause. |
| Daily try-on limit | The per-shopper fairness cap: 12 try-ons a day, doubling to 24 for shoppers who purchased through a try-on in the last 30 days. |
| Fit-risk product | A product tried on at least 5 times whose conversion sits at half your store average or less — a photos/pricing signal, not a verdict. |
| Returns intelligence | The return rate of tried-on items vs your store-wide baseline, computed from your own orders and refunds. |
| Config propagation | The ~30 seconds between saving a setting and shoppers' browsers picking it up. Hard refresh or ?ello_preview=1 to see changes instantly. |

### Common questions

**Q: What's the difference between attributed revenue and lift?**
A: Attributed revenue is an association: shoppers who tried on and then bought, counted under strict rules. Lift is causal: the difference between shoppers who could see try-on and a holdout who couldn't. Ello reports them separately and never dresses one up as the other.

**Q: What is a shopper session in Ello?**
A: A random, anonymous identifier with a 7-day sliding lifetime that connects a shopper's opens, try-ons, and purchases. No name, email, or account is involved.

## Frequently asked questions

URL: https://ellotryon.com/docs/faq · Updated: 2026-08-25

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.

### Setup

#### Do I need to edit theme code?

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](https://ellotryon.com/docs/install-ello).

#### Can I run Ello on a non-Shopify store?

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](https://ellotryon.com/platforms).

#### Can I try Ello without showing it to shoppers?

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.

### Product types

#### What can shoppers try on?

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.

#### Does Ello work for shoes?

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.

#### My designs are on the back of the garment — will they show?

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](https://ellotryon.com/docs/products-and-coverage).

#### Can Ello show the back of a backpack, or a handbag crossbody and handheld?

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](https://ellotryon.com/docs/products-and-coverage).

#### Does try-on tell shoppers what size to buy?

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.

### Billing

#### Can I get a surprise bill?

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](https://ellotryon.com/docs/plans-and-billing).

#### Is the Free plan really free forever?

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.

#### Do my own test try-ons count?

Yes — a render is a render. Failed renders release their credit automatically.

### Analytics

#### How does Ello prove it's working?

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](https://ellotryon.com/docs/proof-test).

#### Why is my per-product revenue more than the store total?

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](https://ellotryon.com/docs/analytics-overview).

#### Can I export my data?

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.

### Performance

#### Will Ello slow my store down?

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.

#### Will Ello break my theme?

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.

### Shoppers & privacy

#### Do you store my customers' photos?

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](https://ellotryon.com/docs/privacy-and-data).

#### How many try-ons does each shopper get?

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](https://ellotryon.com/docs/try-on-limits).

#### What do shoppers see when a limit is reached?

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.

### Common questions

**Q: Where do I get help that isn't covered in the docs?**
A: 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.

**Q: Does Ello have an API or a way for AI assistants to read these docs?**
A: 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.

---

Support: andrew@ellotryon.com · Install: https://apps.shopify.com/ello · All docs: https://ellotryon.com/docs