Woven Looks Add to your store

For Shopify apparel stores

See it on you
before it ships.

Shoppers upload one photo and watch the garment land on them โ€” with a size that actually fits and the rest of the outfit styled around it. Fewer returns, fewer abandoned carts, no photo ever kept.

25 free renders ยท installs as a theme block ยท no code

Three steps

One photo in. A whole outfit out.

The shopper never leaves your product page. The window opens over it, takes what it needs, and hands back a preview.

  1. 01

    Photo

    A single selfie is enough. It is downscaled in the browser before it goes anywhere, which strips the GPS data phones bury in every image.

  2. 02

    Style

    We pair the garment with pieces from your own catalogue โ€” trousers for a top, a layer over a dress โ€” so the preview shows a look, not an item.

  3. 03

    Size

    Height, weight and how they like things to sit, read against your size chart. They get a recommendation with the reasoning attached.

What you get

Built for the shop, not the demo.

Outfits, from your catalogue

A classifier sorts your products into tops, bottoms, outerwear and one-pieces during a single catalogue scan, then the picker suggests what goes with what. Merchants can overrule it โ€” corrections stick and are never re-classified.

Sizes with a reason

Not a guess. The recommendation cites the measurement it turned on, so a shopper can disagree with it intelligently.

Lookbook & Fit card

Signed-in shoppers get their previews and measurements kept for next time โ€” one more reason to make an account with you.

Installs as a theme block

Drop it onto the product template in the theme editor. Non-apparel products never render the button, or the script.

Identical renders are never paid for twice

The same shopper photo against the same garment resolves from cache instead of the model. It is the single biggest lever on what this costs to run, which is why cache hits do not count against your plan.

The part most apps skip

We never store the photo.

A shopper's face is sent to the render, used, and dropped. It is not written to a bucket, not kept for "improvements", and never used to train a model. All that survives is a hash โ€” enough to recognise the same request twice, not enough to reconstruct anyone.

Generated previews expire on a schedule you set, and uninstalling takes the data with it.

  • Photos discarded after rendering
  • Downscaled in-browser, EXIF stripped
  • Renders expire on your schedule
  • Never used for model training

Pricing

Pay for renders, not seats.

Every plan includes size recommendations. Cache hits are free on all of them.

Free

$0

25 renders, one time

  • Size recommendations
  • Theme block install
Try it out

Starter

$149/mo

1,000 renders a month

  • Size recommendations
  • Free cache hits
Choose Starter
Most complete

Growth

$279/mo

2,500 renders a month

  • Everything in Starter
  • Outfit pairing
Choose Growth

Scale

$549/mo

6,000 renders a month

  • Everything in Growth
  • Priority rendering
Choose Scale

Questions

The things merchants ask first.

Do shoppers need an account?

No. Anyone can try a garment on as a guest. Signing in only adds the Lookbook and the saved Fit card, which is why it tends to earn you accounts rather than cost you conversions.

What happens on products that aren't clothing?

Nothing renders. Eligibility is decided in Liquid before the page is built, so a kettle costs you no button, no script and no request.

Will it match my theme?

The button inherits your theme's type and takes your brand colour. The try-on window is deliberately self-contained so it looks the same on every store rather than inheriting a theme's heading styles and breaking.

How long do previews last?

You set the retention window; the default is 24 hours. Expired renders are deleted from storage, not just hidden.

Let them see it on before they buy it.

25 renders free. It installs in about the time this took to read.

Add to your store