Virtual Try-On on Ecwid: What Are Your Options?

ZeDaq.ai does not have an Ecwid-specific app, so virtual try-on on Ecwid works one of two ways: a script-tag widget added to your product pages, or the REST API called from your own code. The widget route only works if your Ecwid setup lets you add a script to the page, so check that first.

This guide is for Ecwid store owners and the developers who support them. If you run WooCommerce instead, the guide to virtual try-on for WooCommerce covers that platform.

Does ZeDaq.ai have an Ecwid app?

No. ZeDaq.ai is available as a Shopify app, a REST API, and a script-tag widget for WooCommerce, Wix, Squarespace, BigCommerce and custom sites. Ecwid is not on that list, and there is no Ecwid plugin.

That does not rule Ecwid out. It means any setup is a custom one. The two building blocks below are the same ones used on other platforms.

What is Ecwid's own route for custom work?

Ecwid's developer site says you can create apps to extend the platform, use site templates to control design, connect outside services through webhooks, and build headless sites through its API. You can see this on the Ecwid developer site (checked November 2026).

We could not confirm from Ecwid's public pages whether you can paste a script into a product page on every plan. Treat that as an open question, and confirm it in Ecwid's documentation or with their support before you plan any work.

How does the widget option work?

The widget is one script tag. You paste it into the product template, and it adds a "Try it on" button and a "Find my size" option.

<script src="https://www.zedaq.ai/widget/zedaq.js" data-key="YOUR_KEY" defer></script>

A few rules apply:

1. Lock the key to your domain. In the dashboard, go to API keys and lock the key to your store's domain. Because the key is visible in your page source, an unlocked key is refused.
2. Add it where product pages load. It needs to run on the page that shows the product.
3. Check your images. The widget can only fetch product images from your own domain or common store CDNs.

Full setup steps are in the widget documentation.

How does the REST API option work?

If you build your own storefront or use Ecwid's headless approach, you can call the API directly. Send POST /api/v1/tryon with your key in an x-api-key header.

Keep server keys on your server. Never place a key that is not domain-locked in browser code. The API reference lists the request format and the error codes.

This route needs a developer. It gives you full control over how the button and result look in your design.

Which option should you pick?

Use this table to decide.

Question	Widget	REST API
Can you add a script to product pages?	Needed	Not needed
Do you have a developer?	Not required	Required
Do you want your own button and layout?	Limited	Full control
How fast can you test?	Fastest	Slower

If you are unsure, start with the widget on a single product and check the result on a phone. A short test tells you more than reading about it.

How do you size products if you sell different garment types?

You enter your own size guide in the ZeDaq.ai dashboard, under Size charts, with one chart per garment type: tops, outerwear, dresses and bottoms. The scan recommends your store's own labels, and picks the larger size when a shopper falls between two.

Set the garment type on the widget so it picks the right chart. If no chart exists, shoppers get a generic UK, US, EU or AU size.

Try-on suits different categories in different ways. For a swim example, the swimwear try-on guide shows how charts map to products.

How do you test the setup before launch?

Test on one product first. Open the live product page on a phone, because most shoppers will.

1. Check the button appears. If "Try it on" is missing, the script did not load on that page.
2. Run a photo through. Use a full-length photo of yourself and see the garment render.
3. Try "Find my size." Enter your height and compare the answer with your chart.
4. Check the error messages. The docs list the codes, such as missing_api_key for no key, invalid_api_key for a wrong or revoked key, and domain_lock_required when the key is not locked to your domain.

If something fails, read the code before you change anything. Most setup problems are a key that is missing, wrong or not domain-locked.

What should you tell shoppers about their photos?

Be plain about it on your product page. For sizing, the photo is analyzed in the shopper's browser and only the measurements are sent. If the shopper also runs a try-on, that photo is sent to render the image.

A short line next to the button, such as "Your photo is used only to show this garment on you," must match how you configure the tool. Check the facts against your own privacy policy before you publish.

What questions should you ask before you start?

A few quick checks save a lot of wasted effort. Write the answers down before you commit time to the project.

• Can I add a script to my product pages? Ask Ecwid's support or read their documentation.
• Do I have my own domain? The widget key must be locked to your store's domain.
• Who will maintain it? Someone should own the key, the size charts and the test routine.
• Which products come first? Pick a handful of popular items and test those.

If the answer to the first question is no, the REST API on a custom or headless front end may be the only route.

What other platforms work the same way?

Other platforms without a dedicated app follow the same pattern: widget if you can add a script, API if you can build. See the guides for virtual try-on on Webflow and virtual try-on on OpenCart.

What does it cost to test?

The Free plan includes 3 try-ons, 3 measurements and 5 invoices a month, enough for a small test. Paid plans start with Micro at $14 a month, and every paid plan has a 3-day free trial with no card required. See the current pricing for all plans.

FAQs

Can I install ZeDaq.ai from the Ecwid app market?

No. There is no Ecwid app or plugin. You can use the script-tag widget if your store allows it, or the REST API.

Is the widget key safe to show in my page source?

Yes, if you lock it to your store's domain in the dashboard. Requests from other domains are refused, and an unlocked key is rejected by the widget.

Do shoppers need an account?

No. Shoppers use try-on and "Find my size" on your product page, with no sign-up.

Which should I try first, the widget or the API?

Try the widget if you can add a script, because it is quicker to test. Use the API if you need full control of the design.