When Not to Use Virtual Try-On

Why Write the Anti-Pitch at All

A company that sells virtual try-on writing about when not to use it is either a gimmick or the most useful thing we can publish. We think it is the second, for a structural reason: Looksy bills usage-based through Shopify with no contracts. A merchant who installs into a bad fit discovers the mismatch quickly, uninstalls, and gains nothing — and neither do we. There is no lock-in to hide behind, so honest scoping is simply the better business. We are also early. Our listing currently shows 4.6 stars from six reviews, which is to say: every merchant experience shapes what this product is publicly. Wrong-fit installs are the most expensive kind for a small app, because they convert into the most accurate negative reviews. So this post draws the boundary as plainly as we can. If your store falls on the far side of it, we would genuinely rather you skip us — or run the free tier as a test — than install on hope.

Categories Where the Question Never Comes Up

Try-on earns its place on a product page when "how does this look on me" is the barrier between interest and purchase. In apparel and adjacent categories, that question dominates. In plenty of others, it never arises, and a try-on block there is furniture. Think about what actually blocks the purchase in your category. Consumables are bought on ingredients, reviews, and price. Hard goods are bought on specs and dimensions. Most home goods hinge on how something looks in a room, which is a different question than the one a personal try-on answers. Replacement purchases — a shopper rebuying something they already own — carry no appearance uncertainty at all. The test is unglamorous but reliable: read your own support threads and product questions. If shoppers rarely ask how something will look on them, a block answering that question adds interface without adding information. No feature survives being the answer to a question nobody on the page is asking.

Run Your Own Arithmetic Before Installing

The published numbers are small but not zero: paid tiers run from $14.99 to $79 per month, and overage credits cost between $0.10 and $0.14 depending on plan. Whether that is trivial or material depends entirely on numbers only you have — your price points, your margins, your traffic. We will not hand you a threshold, because we would be inventing it. Instead, run the questions: at your volumes, what would a month of try-ons plausibly cost, and what would you need to believe about the feature's effect to justify that line item? If the honest answer is that you cannot yet say, that is an argument for the free tier, not a paid one. Traffic matters for a second, less obvious reason. Looksy's analytics reports what shoppers try on, add to cart, and buy — but a store with very little traffic accumulates that signal slowly. If months would pass before the data said anything, the feature cannot teach you much yet, whatever it costs.

If the Base Imagery Is Weak, Fix That First

Virtual try-on augments a product page; it does not rescue one. The generated preview sits alongside your product photography, your descriptions, and your data — and it inherits their quality problems rather than solving them. The dependency is concrete in at least one place: Looksy's Size Help works from your own size charts. If your charts are missing, outdated, or wrong, that feature has nothing sound to present. The app supplies the surface; the substance is yours, and no install changes that. So sequence honestly. If your product photography is inconsistent, your descriptions thin, or your size data unreliable, those fixes come first — they improve every visit, with or without try-on, and they are prerequisites for the feature doing its best work. A try-on block on top of weak fundamentals is an upgrade to the least broken part of the page. Foundations first is slower advice than install now, and it is the correct order.

If Nobody Will Operate It, Defer

Some Looksy features are install-and-done. Others are operated, and a feature nobody operates quietly becomes shelf-ware you pay for. Email Follow-Up is the clearest case: it runs through Klaviyo or Shopify Flow, which means someone has to connect the integration, decide what the follow-up says, and own it afterward. Analytics is the same in a softer way — Looksy will report what shoppers try on, add to cart, and buy, but a report nobody reads changes nothing. Even size charts, once they power Size Help, need an owner who updates them when products change. None of this is heavy work, but it is nonzero work, and the honest pre-install question is simply: whose? If your team has a name for it, proceed. If the answer is that you will figure it out later, later is also a fine time to install. An app that arrives when someone can receive it performs unrecognizably better than the same app installed into a vacuum.

The Cheap Way to Find Out

If you have read this far and are genuinely unsure which side of the line your store falls on, the good news is that the question is testable at low cost — with your own traffic, not our marketing. The free tier exists for exactly this. It includes unlimited try-ons, carries Looksy branding, and caps attributed additional revenue at $100 — enough room to watch real shoppers meet the feature and see what your analytics says about what they try on, cart, and buy. The technical risk is similarly small: Looksy installs as a theme app extension, so there are no edits to your theme code, and the listing notes a clean uninstall if the answer turns out to be no. Run it for a defined period, decide in advance what you would need to see, and let the data settle the argument. That is a more honest close than a pitch: the categories and stores in this post exist, yours might be one of them, and the cheapest way to know is to check.

Facts in this post come from the public Shopify App Store listing for Looksy. Last checked 29 July 2026.