Onboarding Your Team to Virtual Try-On

Give Try-On an Owner Before It Needs One

Looksy installs as a theme app extension — you add a block through the theme editor, with no theme code edits — so the technical setup rarely needs more than one person. The operational side is different. Virtual try-on touches product photography, size charts, support answers, email follow-up, and reporting, and on most teams each of those belongs to a different job. The simplest fix is to name an owner before launch. One person holds the overall picture: which plan the store is on, how many photo credits it includes, what happens when they run out, and who is responsible for each feature. Everything else in this post — the role mapping, the internal doc, the support briefing — flows from that decision. Without an owner, questions like why try-on disappeared after a theme change, or whose job the size chart is, get answered by whoever happens to be closest. That is how inconsistency starts, and it is entirely avoidable with one assignment made early.

Start Everyone With the Shopper's Flow

The fastest way to onboard a team is to have each person run the try-on the way a shopper does. On a product page, the shopper uploads a single photo and sees the result on that same page in about 20 seconds. For the photo flow there is no app to download, no account to create, and no camera permission to grant. Afterward the shopper can retry, leave feedback, download the result, or share it. Ten minutes of first-hand use answers most of the questions a briefing document would otherwise have to. Support hears the pacing of the wait. Merchandisers see how their product imagery comes through. Marketing sees where email capture sits in the journey. Ask each person to try one product they know well and one they do not — the second run is usually where the honest observations come from. Keep the session unscripted. The goal is not to demonstrate the feature working; it is to let the team form the same mental model a shopper will have, including any rough edges, so internal answers match the external experience.

Map Features to Roles

Looksy's feature set maps onto jobs most stores already have. Merchandising owns the catalog side: product imagery, and the size charts behind Size Help, which draws on your own charts rather than a generic database. If the charts are missing or stale, the sizing answer a shopper receives is only as good as what merchandising maintains. Marketing owns Email Follow-Up, which runs through Klaviyo or Shopify Flow, and often the Bundles & Upsells pairings as well, since both shape what a shopper is offered next. Support owns the shopper-facing mechanics covered in the briefing below. Whoever owns reporting should hold Analytics, which shows what shoppers try on, add to cart, and buy — a direct read on where the catalog is working. That leaves billing and plan management with the overall owner. Looksy bills usage-based through Shopify with no contracts, and paid plans carry a monthly credit allowance and a revenue cap, so someone needs to watch consumption the way they would watch ad spend.

Write the One-Page Internal Doc

Once roles are mapped, write them down, along with the plan facts your team would otherwise have to look up mid-conversation. One page is enough: which plan the store is on and what it includes, who owns each feature, and where the assets live. The plan facts are worth recording precisely. The Free plan allows unlimited try-ons with Looksy branding, up to $100 in additional revenue. Starter, at $14.99 per month, includes 100 photo credits, a $500 revenue cap, branding removal, and unlimited size help, bundles, and email capture, with extra credits at $0.14. Growth, at $29, carries 300 credits and a $1,000 cap, with extra credits at $0.12. Scale, at $79, includes 600 photo or video credits, no revenue cap, and Realtime video try-on, with extra credits at $0.10. Add two operational lines: what the team does when credits run low in a busy week, and who decides whether to change plans. Those are the two moments when a missing doc turns into a scramble.

Brief Support on Mechanics, Not Scripts

Support does not need a script; it needs the mechanics. Agents should know that photo try-on asks for one uploaded photo and returns a result on the product page in about 20 seconds, that no account or app download is required, and that the shopper's on-page options are retry, feedback, download, and share. They should also know which plan the store is on, because Realtime video try-on is a Scale-plan capability — if the store is not on Scale, the honest answer to a video question is that photo try-on is what is available. Two areas deserve preparation rather than improvisation. Privacy questions — what happens to an uploaded photo, and how long anything is retained — are not spelled out on the app listing, so source those answers from Looksy's current documentation and your own privacy policy before launch, and write the agreed wording into the support doc verbatim. Language is similar. Looksy lists 47 supported languages, but the listing does not detail exactly what that covers for a given storefront. Test the try-on in your store's language end to end before agents promise a fully translated experience.

Revisit at Every Plan or Theme Change

Onboarding is not a launch artifact; it decays as the store changes. Four events should trigger a review of the doc and a quick re-run of the shopper flow: a plan change, because credit allowances, caps, and available features shift with it; a theme migration, because Looksy lives in your theme as an app block and a new theme needs it added again; a new hire in any of the mapped roles; and a season change that turns over a meaningful share of the catalog. The review itself is short. Re-run one try-on as a shopper, confirm the plan facts on the doc still match your Shopify billing, and check that each named owner still holds the role. A review like that fits comfortably into a quarterly routine. The payoff is boring in the best way: support answers stay consistent, size charts stay current, and nobody discovers a missing app block from a customer email. Treat the doc as part of store operations, the same as shipping settings or tax configuration.

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