How do I document try-on for my team?

One page beats a manual

Try-on has a small configuration surface, so the documentation should match: a single page in whatever tool your team already uses — Notion, a shared doc, the store wiki. A long manual goes stale the first time someone changes a setting and forgets to update chapter four. The one-pager holds the facts that change rarely and get asked about often, and it links out to anything role-specific: a brief for a VA handling try-on questions, or talking points for customer support, each of which deserves its own short document rather than a section buried here. Assign one owner; a runbook nobody owns is a runbook nobody trusts.

Record the setup: products enabled and the photo standard

List which products have try-on enabled, and one line on why — best-sellers, apparel with fit doubt, whatever your logic was. Then write down the photo standard those products meet, because Looksy's published guidance is concrete: clear, product-focused images generate the best results, and full views beat cropped shots for apparel. When a teammate adds a new product, the document should answer their two immediate questions — does this product get try-on, and do its photos meet the bar — without a Slack thread. Note where the try-on block sits in your theme so a redesign does not silently drop it.

Record the plan, credit budget, and who reads analytics

Write down the plan you are on and what it includes, because credits are the budget line teammates will ask about: Free has unlimited try-ons with Looksy branding, Starter at $14.99 per month includes 100 photo credits, Growth at $29 includes 300, and Scale at $79 includes 600 photo or video credits, with additional credits at $0.14, $0.12, and $0.10 respectively. Billing runs usage-based through Shopify with no contracts, so a plan change is a documented decision, not a negotiation. Then name the person who reads analytics weekly — what shoppers try on, add to cart, and buy — so the numbers get acted on, not just collected.

Write the escalation path to Looksy

The last block is what to do when the document cannot answer a question. Point teammates first at Looksy's App Store listing and this FAQ, and then name who on your team contacts Looksy support when those do not resolve it. One named escalation owner prevents the failure mode where three people independently contact support about the same glitch, or nobody does. Keep a short changelog at the bottom of the page: date, what changed, who changed it. When a result complaint or a billing question surfaces months from now, that history is usually the fastest answer.

Sources: the public Shopify App Store listing for Looksy. Last checked 27 July 2026.

Related questions: Should try-on be above or below the fold? · How do I time try-on around a rebrand? · Does try-on work with Shopify page builders?