ZeDaq.ai
Shopper using virtual try-on on her phone

How Long Does It Take to Launch Virtual Try-On?

By the ZeDaq.ai team · · 6 min read

On this page
  1. What decides how long a launch takes?
  2. How long does each stage take?
  3. What does setup look like on each platform?
  4. What can you do before you install?
  5. What does a realistic launch plan look like?
  6. What commonly delays a launch?
  7. Who needs to be involved?
  8. How do you know the launch is done?
  9. What should you do if the timeline slips?
  10. How can you test before you commit?

You can launch virtual try-on as fast as you can prepare your products and size charts, because the install itself is the short part. On Shopify it is an app install, a size chart and one theme setting. On other platforms it is a script tag pasted into your product template.

What takes time is the preparation around it. This guide breaks a launch into stages so you can plan it, and it assumes you are adding try-on to a virtual fitting room for a clothing website.

What decides how long a launch takes?

Four things set your timeline, and only one of them is technical:

  • Platform. Shopify uses an app. WooCommerce, Wix, Squarespace, BigCommerce and custom sites use a script-tag widget. Developers can also call the REST API directly.
  • Size charts. If your size guide already lists body measurements, this is quick. If it only lists garment widths, someone has to convert it.
  • Product photos. Try-on is built from your product photo, so clear front-facing images save you reshoots.
  • Approvals. A solo founder decides in a minute. A larger team may need sign-off from design, legal and customer service.

How long does each stage take?

Time depends on your store, so treat this as an order of work, not a promise.

Stage What happens What slows it down
Prepare Pick products, check photos, list size charts Charts in the wrong format
Install Add the app, widget or API call Theme or template quirks
Test Try it on your own products and phone Poor product photos
Brief Tell support and sales how it works Large teams
Go live Switch on for a few products first Waiting for approvals

What does setup look like on each platform?

Shopify

Install the ZeDaq.ai Shopify app, add your size chart in the app, then switch on the app embed in the theme editor. Set the garment type for each product. The store needs an Online Store 2.0 theme. A step-by-step version is in our guide to adding virtual try-on to Shopify.

WooCommerce, Wix, Squarespace, BigCommerce and custom sites

Paste a script tag into the product template, with a key locked to your store's domain. This adds the "Try it on" and "Find my size" buttons. The details are in the widget documentation, and our page on virtual try-on for WooCommerce covers that platform in particular.

Custom builds

If you call the REST API, your developer controls the timeline. It is one endpoint, POST /api/v1/tryon, with an x-api-key header. The work is mostly in your own interface.

What can you do before you install?

Most delays come from missing prep, so do these first:

  1. Choose a small set of products to start with.
  2. Write down body measurements for each size, one chart per garment type: tops, outerwear, dresses and bottoms.
  3. Check that each product has a clear photo of the whole garment.
  4. Decide who answers shopper questions.

The try-on launch checklist for fashion brands turns this into a full list. If you sell eyewear, the plan differs, so read try-on for sunglasses stores.

What does a realistic launch plan look like?

Here is a plan for a small store with one owner. Larger teams add time for approvals, but the order stays the same.

Sitting one: decide and prepare

Choose your first products and write down the body measurements for each size. Check the photos and note which need a reshoot. This sitting is where most of the real work happens.

Sitting two: install and test

Install the app or paste the widget. Test on your own phone, with your own photo, on every product you chose. Write down anything that looks wrong, such as color or length, and fix the product photo before moving on.

Sitting three: tell your team and go live

Explain to support what the buttons do and what the shopper uploads. Switch the feature on for your first products. Keep the rest off until you have looked at the early results.

After launch: review and expand

Look at which products shoppers use it on, what support is asked and which photos need work. Then add the next group of products. Some stores finish this in a few days and others spread it over weeks. Both are fine.

What commonly delays a launch?

Most delays are about information, not software:

  • Size charts in the wrong format. Charts written as garment widths need converting into body measurements.
  • Missing garment types. Each product needs a type, such as tops or dresses, so the right chart is used.
  • Weak product photos. A dark or cropped image gives a poor result, and a reshoot takes longer than the install.
  • Waiting for a developer. Custom builds that use the API depend on someone's calendar. If you can, start on Shopify or the widget first.
  • Too many products at once. A large first batch makes mistakes hard to spot.

Who needs to be involved?

For most stores, three roles are enough, and they can be the same person:

  1. Owner or merchandiser. Picks products and approves the charts.
  2. Photographer or designer. Fixes product photos.
  3. Support lead. Learns what shoppers will ask.

A developer is only needed for API builds or heavily customized templates.

How do you know the launch is done?

A launch is done when four things are true. Your first products show the buttons, the size suggestions match what your team would say in a fitting room, your support team knows what shoppers see, and you have a short list of the next products to add.

Do not wait for perfection. A small, checked launch teaches you more than a long preparation phase.

What should you do if the timeline slips?

Cut scope, not quality. Launch on fewer products, or on one garment type, and add the rest later. A narrow launch on good photos beats a wide one on weak photos.

If the delay is a size chart, use the fallback. Shoppers without a store chart get a standard UK, US, EU or AU size, so you can go live and add your own chart after.

How can you test before you commit?

You do not need to decide on a full rollout on day one. The Free plan includes 3 try-ons and 3 measurements a month, and every paid plan has a 3-day free trial with no card required. Use them on your own products and your own body before you tell customers.

Pricing starts with Micro at $14 a month, and the first month is $1 on monthly plans, then $14 a month. That offer applies once per store, on its first paid plan. See pricing for the current plans.

Start with a few products and test

FAQs

Can a non-developer launch try-on alone?

On Shopify, yes: it is an app install and theme settings. The widget needs a script tag pasted into a template, which many store owners can also do.

Do I need to launch on every product at once?

No. Start with a few products, check the results and add more.

What slows launches down most?

Size charts that only list garment dimensions, and product photos that are dark or cropped. Fix those before installing.

Does launching require shopper accounts?

No. The shopper uploads a photo on your product page. There is no sign-up and no app to download.

Try ZeDaq.ai free

Virtual try-on and Find my size for your store, plus client, order and invoicing tools for tailors, in one subscription.

Related articles