A Launch-Week Checklist for Virtual Try-On

Before Day One: Pick a Plan You Can Explain Back

Launch week goes smoother when the plan decision is already made. Looksy's published tiers are straightforward. Free offers unlimited try-ons with Looksy branding and a cap of $100 in additional revenue. Starter, at $14.99 a month, includes 100 photo credits, a $500 cap, branding removal, and unlimited size help, bundles, and email capture, with extra credits at $0.14. Growth, at $29, moves to 300 credits, a $1,000 cap, and $0.12 extra credits. Scale, at $79, includes 600 photo or video credits, no revenue cap, realtime video try-on, and $0.10 extra credits. Billing is usage-based through Shopify, with no contracts. For a first week, the practical question is which meters you want to be watching. Free lets you validate the experience with the revenue cap as the ceiling. Paid tiers add credits as a second meter. Pick the one you can explain to yourself in one sentence, because you will be reading its numbers all week.

Day One: Install and Confirm the Widget Appears

Looksy installs as a theme app extension, which means no edits to your theme code, and the listing notes a clean uninstall if you change your mind. Day one is simply install, enable, and verify. Open a handful of product pages as a shopper would — different templates if your store has them, desktop and phone. Confirm the try-on entry point renders where you expect and does not collide with your existing page elements. On the Free plan, remember that Looksy branding will be visible; that is part of the published tier, not a defect. Resist the urge to configure everything today. A launch week works because each day has one job, and day one's job is a widget that reliably shows up.

Day Two: Run the Shopper Flow End to End

The published flow is short: a shopper uploads one photo, and the result appears on the product page in about 20 seconds, with no app to download, no account to create, and no camera permission to grant. Day two is experiencing that flow yourself, repeatedly. Try it on your best product images and your worst ones. Use retry to see how results vary, use download to keep copies for comparison, and note where the feedback and share options sit, because those are part of what your shoppers will see. The goal is not a verdict on the technology. It is knowing exactly what a shopper experiences before you tell anyone the feature exists — how long 20 seconds feels on your connection, what the result looks like for your catalog, and what you would want a shopper to do next.

Day Three: Load Size Charts and Turn On Bundles

Size Help runs on your own size charts — that is how the listing describes it — so day three starts with gathering the charts you actually trust and getting them into the app. If your sizing lives in a supplier PDF nobody has checked in a year, this is the forcing function to fix that. The same day, look at Bundles & Upsells. Decide which products belong together deliberately rather than accepting whatever pairing seems obvious, since these suggestions will sit inside the try-on experience you tested yesterday. One plan note: the listing associates unlimited size help, bundles, and email capture with the Starter tier and above. If you launched on Free, check inside the app which of these features your plan currently includes before you build the day around them.

Day Four: Connect Email Follow-Up

Looksy's Email Follow-Up works with Klaviyo or Shopify Flow, and the listing's works-with line covers Checkout, Shopify Admin, Flow, and Klaviyo. Day four is wiring the connection and deciding what the follow-up should actually say. If you already run Klaviyo, this is a question of where try-on-driven email fits among your existing flows. If you use Shopify Flow, it is a question of which trigger and action make sense for your store. Either way, send a test to yourself before anything reaches a shopper. Keep the first version modest. A follow-up that references what a shopper tried on is a new kind of message for your list, and week one is for confirming it works, not for building your most ambitious automation.

Day Five: Check the Experience in Your Shoppers' Languages

The listing enumerates 47 supported languages. What it does not spell out is exactly what supported covers — how deep translation goes for the shopper-facing widget versus the merchant dashboard, for instance. That makes day five a verification day, not a configuration day. List the languages your storefront actually serves. For each, open a product page as a shopper in that language and walk the try-on flow: the entry point, the upload step, the result screen, and the retry and share controls. Note anything that appears untranslated or awkward. If a language you need behaves in a way you did not expect, that is worth resolving before you announce the feature rather than after. Verifying with your own storefront settings is the only way to know what your shoppers will actually see.

Days Six and Seven: Read the Meters and Decide

By the weekend you have real usage, however small. Looksy's analytics reports what shoppers try on, add to cart, and buy — read all three, in that order, and resist comparing them to numbers from anywhere else. Week one is your baseline, not your verdict. Then check the meters that belong to your plan. On Free, that is progress toward the $100 additional-revenue cap. On paid tiers, it is credits consumed against the 100, 300, or 600 included, with extras at $0.14, $0.12, or $0.10 depending on tier. Since billing is usage-based through Shopify with no contracts, changing plans is a decision you can revisit. Close the week by writing down three things: what shoppers did, what surprised you, and what you will change in week two. A launch is not the end of the checklist; it is the first data point.

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