Stylab bills through Shopify by successful try-on — not installs, not page views. Picking the wrong plan either wastes budget on unused credits or throttles a widget that was starting to work. This guide helps apparel merchants estimate volume before committing.
Plans at a glance
- Free — $0 / 50 try-ons — proof of concept on 1–3 SKUs with low traffic
- Starter — $19 / 300 — small catalog pilots and seasonal drops
- Growth — $49 / 1,000 — multiple hero SKUs with steady mobile traffic
- Scale — $149 / 4,000 — broader catalog or paid traffic spikes
Only successful generations count. Failed attempts should not consume credits — verify current billing behavior in the app before citing exact numbers in customer comms.
Estimate volume without guessing
Step 1 — Enabled SKUs only
Do not divide store-wide sessions by ten. Count monthly product page views for SKUs where try-on is actually enabled.
Step 2 — Try-on rate assumption
Early pilots often see 2–8% of PDP viewers start try-on when the button is visible above the fold on mobile. Use 3% for conservative planning, 5% if your audience is young/streetwear-heavy.
Step 3 — Completion rate
Not every start finishes — upload friction, privacy hesitation, or slow generation reduce completions. Plan for 60–80% of starts becoming successful try-ons after you fix mobile UX.
Example
5 SKUs × 2,000 mobile PDP views/month each = 10,000 views. At 4% start rate → 400 starts. At 70% completion → ~280 successful try-ons → Starter fits with headroom.
Use the free ROI calculator on the resources page to plug in your numbers.
When to stay on Free
- Testing try-on on one jersey or hoodie with under ~1,500 relevant PDP views/month
- Running an A/B test where half of traffic never sees the widget
- Internal QA before customer-facing launch
When to upgrade
- Starter → Growth — dashboard shows 240+ successful try-ons/month for two consecutive months, or you expand beyond ~8 enabled SKUs
- Growth → Scale — paid campaigns drive predictable spikes, or you enable try-on on 20+ products with consistent adoption
- Any plan — shoppers see “limit reached” or generations queue — upgrade before a product drop, not after
Cost vs return (honest framing)
Do not promise ROI multiples. Instead, compare plan cost to:
- Margin on one incremental order from try-on-influenced carts
- Cost of a single product photoshoot or UGC campaign
- Support tickets about fit uncertainty on the same SKUs
Pair spend with an A/B test so you know whether try-on shifts add-to-cart on enabled products.