styleprofile. — home

Solutions · Ecommerce platforms

Add virtual try-on to any storefront

There are two ways to put StyleProfile in front of shoppers: a no-code widget that installs on Shopify today, and a REST API with a JavaScript SDK for every other stack. Both call the same render engine and return the same outfit.

Async embed · No render-blocking scripts · Your theme, your fonts

A product photography setup: a softbox on a stand lighting an ivory poplin shirt hung on a small wooden rack on a shooting table.
The setup try-on replaces: one shirt, one light, one afternoon.

Two ways in

Widget or API — pick by who is doing the work

The widget is faster and needs nobody technical; the API gives you control over placement and the response. Nothing about the renders differs between them.

Live on Shopify

The no-code widget

A merchandiser installs an app and places a block in the product template. No repository is touched and no deployment is scheduled.

Available on
Shopify and Shopify Plus today
Who does the work
Whoever edits your theme
Code you write
None
Where it renders
A panel on your own product page

What it takes to go live

  1. 01Install the StyleProfile app on your store.
  2. 02Let the catalogue sync pull products, images and size charts.
  3. 03Drop the try-on block into your product template and set placement.
  4. 04Publish. The widget picks up your theme fonts and colours.
Any stack

The REST API and SDK

Your team calls the render engine directly and decides where the result appears. Use it when you are not on Shopify, or when the product page is not where try-on belongs.

Available on
Anything that can make an HTTPS request
Who does the work
Your front-end and back-end engineers
Code you write
A catalogue mapping and a render call
Where it renders
Wherever you put it — PDP, category, app

What it takes to go live

  1. 01Request sandbox access and we set your keys up with you.
  2. 02Map your catalogue to the product schema — images, categories, size charts.
  3. 03Call the render endpoint with a selection and receive the rendered look.
  4. 04Embed the result with the JavaScript SDK, or handle the response yourself.

Same engine either way

Two front doors, one render pipeline

Whichever path you take, the request lands in the same place and the shopper gets the same image back. The widget is the API with a UI on top of it — there is no cut-down engine behind the no-code route.

REST · SDK · Shopify app live today

Implementation

A typical rollout takes a week

Most Shopify stores go from install to live inside a week, and the work is front-loaded into the first two days. This is the shape of a normal rollout, not a service-level commitment.

  1. Day 1

    Install and sync

    The app goes on (or the sandbox keys come out) and the catalogue sync runs. An afternoon for most catalogues; a very large one takes longer to pull.

  2. Day 2

    Styles and QA

    We render a sample across your categories and you look at them together with us. Anything that renders badly usually traces back to a source image, and we say which ones.

  3. Week 1

    Live on the product page

    The block goes into the template, placement is set, and you publish. Heavily customised themes and internal sign-off are the two things that most often add a week.

Custom builds on the API run to your own release calendar. We do not publish a guaranteed go-live date for work we are not doing ourselves.

Security and data

What the embed touches

The embed loads asynchronously and reads nothing from your checkout. Shopper photos are processed to produce a render and for nothing else, are not used to train our models without explicit consent, and are deleted on request. We describe our actual practices rather than displaying certification badges we have not earned.

Platform support

What is actually built

Shopify is the integration that exists today, and it is the only one with a page. WooCommerce, Magento and Adobe Commerce, BigCommerce and Salesforce Commerce Cloud are in development — the hub lists each one with its real status and no target dates. Everything else runs on the API in the meantime.

FAQ

Integration questions

On Shopify, no — the app installs and the try-on block is placed from the theme editor, which is a merchandiser’s job rather than an engineer’s. On any other stack you do need engineering time, because you are calling the API and deciding where the render appears yourself.

Next step

Ship try-on without shipping a rebuild

Try the live demo in your browser now, or take 30 minutes with us and we will scope the integration against your stack.

Cancel anytime · No long-term contract · Live on your store in minutes