How Web Agencies Can Offer Virtual Try-On to Fashion Clients

Web agencies can offer virtual try-on to fashion clients by picking the right integration route for each client's platform: an app for Shopify, a script tag for WooCommerce, Wix, Squarespace or custom sites, and a REST API for headless builds and apps. The agency's value is in choosing the route, preparing product images and size charts, and testing before launch.

This guide is for agencies and freelance developers who build fashion stores. It uses ZeDaq.ai as the worked example. For the full technical reference, see our guide to the virtual try-on API for developers.

What can an agency actually offer a fashion client?

You can offer two shopper-facing tools and one set of setup work.

• Try it on. The shopper uploads one photo and sees the client's real garment on their body, rendered from the product image.
• Find my size. The shopper uploads one photo and types their height. Measurements are taken on the shopper's device and matched to the client's own size chart.
• Setup and tuning. Choosing the route, writing the template change, entering size charts, cleaning product images and testing on real devices.

Clients who sell glasses or sunglasses can also add live-camera eyewear try-on. Clients who are tailors can use the ZeDaq.ai tailor tools, but that is a separate offer from a storefront build.

Which integration route fits each client?

Match the route to the platform. This table is the quick version you can share in a proposal.

Client platform	Route	What you deliver
Shopify	Shopify app	Install, size charts, app embed settings, testing
WooCommerce, Wix, Squarespace, BigCommerce	Script tag	Template edit, domain-locked key, size charts, testing
Custom or headless storefront	Script tag or REST API	Template edit or a custom button and result view
Client's own mobile app	REST API	Server-side calls, image upload flow, result screen

Shopify clients

Install the ZeDaq.ai Shopify app on the client's store and switch on its app embed in the Theme Editor. There is no code to write, so your work is size charts, image quality and testing.

Script-tag clients

Paste one line into the product template:

<script src="https://www.zedaq.ai/widget/zedaq.js" data-key="YOUR_WIDGET_KEY" data-garment-type="upper_body" defer></script>

The key must be locked to the client's domain in Dashboard → API keys. Unlocked widget keys are refused, which stops another site from copying the key. The widget adds the "Try it on" and "Find my size" buttons.

Before you paste anything, check the client's product pages are ready. The guide on preparing a non-Shopify store covers templates, image sizes and garment types.

API clients

Call POST /api/v1/tryon with an x-api-key header, a person image and a product image. The optional garment_type field takes upper_body, lower_body or dresses. A slow render returns a job_id and a poll URL, so build a loading state. The API reference lists the request fields and error codes.

How do you scope a try-on project?

Keep scope tight. Most work sits in a few clear tasks:

1. Audit the catalog. Count products by garment type and flag images that are cropped, on busy backgrounds or shot at an angle.
2. Collect size charts. Ask for one chart per garment type: tops, outerwear, dresses and bottoms. Body measurements work better than flat garment widths.
3. Choose the route. Use the table above.
4. Build and place the button. Put it near the size selector, and keep "Add to cart" visible on a phone screen.
5. Test on real devices. Run try-ons and scans on at least one iPhone and one Android phone.
6. Hand over. Show the client where the key, size charts and plan settings live.

For WooCommerce, Magento or fully custom builds, the guide to try-on for custom fashion stores compares the widget and API options platform by platform.

What mistakes should agencies avoid on try-on projects?

A few slips cause most launch-week problems:

• Skipping the image audit. Cropped or busy product photos can produce weak try-on images, and the client sees them first.
• Leaving the key on the staging domain. Lock a key to the live domain before launch, or requests from the real site are refused.
• Using one garment type everywhere. A dress template that sends upper_body can give a poor render. Check the setting on each template.
• Promising results. Describe what the tools do, and let the client measure their own outcomes.
• Skipping handover notes. Without them, the next developer has to rediscover every setting.

Who should own the account and the key?

The client should. Have the client create the ZeDaq.ai account in the business's name, with their own login and billing. That keeps billing, data and the domain-locked key with the business that owns the store.

This matters when the relationship ends. If the key sits in your agency account, the client's try-on stops working when you close it. ZeDaq.ai's pricing and API pages don't describe an agency or reseller plan, so plan for one account per client.

Write the handover down. Include the account owner, the domain the key is locked to, which garment type each template uses, and who to call if a render fails.

How do you price try-on work for clients?

Separate your fee from the software plan. Your fee covers setup and tuning. The plan is a monthly cost the client pays directly.

ZeDaq.ai has a Free plan with 3 try-ons and 3 measurements a month, which is enough for a staging test. Paid plans are Micro at $14 a month, Starter at $49, Growth at $129 and Scale at $299. You can try it free for 3 days with no card required, and the first month of every paid plan is discounted. Check the current plan limits before you write the quote.

Some agencies add a small monthly retainer for tuning, such as fixing size charts when a new collection lands. That work is real, because each new garment type needs its own chart.

How do you explain the value without overselling?

Clients will ask whether try-on will cut returns or lift sales. Be honest. ZeDaq.ai doesn't publish results figures, and it has no App Store reviews yet.

Explain what the tools do instead. Try-on shows the shopper the garment on their own photo. Find my size gives one size label from the client's own chart, and it sizes up when the shopper falls between two sizes. Suggest the client tracks their own returns and exchange reasons before and after launch, so the decision rests on their data.

If the client wants the wider business case, our piece on why try-on matters for fashion brands covers the shopper problem it addresses.

FAQs

Can I test try-on on a staging site?

Lock the key to the staging domain while you build, then lock a key to the live domain at launch. Requests from any other origin are refused.

Do shoppers need an account or an app?

No. Shoppers use try-on and Find my size on the client's product page. There is no shopper sign-up and no app to install.

Is the shopper's photo sent for sizing?

No. For sizing, pose detection runs on the shopper's device and only measurements are sent. For try-on, the photo is sent so the image can be rendered.

Is there a WordPress plugin?

No. WooCommerce and other WordPress stores use the script tag in the product template, or the REST API for custom builds.