On this page
Wix now powers a meaningful share of independent apparel storefronts, yet most Wix Stores merchants still rely on a static size chart PDF or table embed. That gap matters: shoppers who can't answer "what size am I" on the spot either abandon the cart or buy two sizes and return one. Fixing it on Wix takes a page embed and, if you want it wired into product variants, a short Velo script.
Wix wasn't built with a native size-recommendation layer, but its Custom Element / HTML iframe embed and its Velo (Wix's JavaScript dev platform) APIs give you two practical paths to add one. This guide walks through both, shows exactly where the widget should sit on the product page, and covers how to confirm it's actually reading variant data from Wix Stores rather than just floating on top of it.
Why Wix Stores Needs This More Than It Looks Like
Wix Stores product pages are templated: the same gallery-plus-buy-box layout repeats across the catalog, which is great for speed but leaves little room for fit guidance beyond a size dropdown. Apparel and footwear already carry return rates well above the retail average, and shoe returns in particular are among the highest of any product category. On a platform where most merchants are small-to-mid apparel or footwear brands, that structural gap compounds — there's no in-house dev team quietly patching it with custom fit logic the way a larger platform's merchants might.
The upstream cost is well documented at the industry level even if your own dashboard doesn't break it out. The National Retail Federation puts the 2024 US returns figure at roughly $890 billion, with online return rates running near 19-20% (nrf.com), and McKinsey estimates returns cost fashion brands north of $40 billion globally per year (mckinsey.com). A size widget doesn't eliminate that cost, but it targets the single largest driver of apparel returns: not knowing which size to click before checkout.
Two Ways to Embed a Widget in Wix
Wix gives you two realistic integration routes, and which one you pick depends on how deep you want the widget wired into your catalog.
1. HTML embed (Custom Element / Embed a Widget). In the Wix Editor, go to Add Elements → Embed → Custom Embeds → HTML iframe, drop it onto the product page template, and paste the widget's embed snippet (typically a <script> tag plus a mount <div>). This is the fastest path — no code beyond copy-paste — and it works on any Wix Stores plan that allows custom code embeds.
2. Velo (Wix's dev platform). If you want the widget to read the shopper's selected variant, pass product ID/SKU context automatically, or write a confirmed size back into the product options before add-to-cart, you'll want Velo. Enable Dev Mode on the site, add a <htmlComponent> (or use the same iframe element) on the Product Page template, and use $w.onReady() plus the Wix Stores Product Page APIs (wixStoresFrontend / $w('#productPage') context) to pass product data into the widget and listen for its size-selected event.
The table below is a quick way to decide which route fits your situation:
| Need | Route |
|---|---|
| Just show fit guidance, no data passthrough | HTML embed, no code |
| Auto-detect product ID/category on load | Velo, pass context on $w.onReady() |
| Write recommended size into the variant selector | Velo, listen for widget's postMessage event |
| Multiple product templates (e.g., dresses vs. shoes) | Velo, conditional mount per template |
Placing the Widget on the Product Page
Placement decides whether the widget gets used at all. On Wix product page templates, the buy box (price, variant dropdown, add-to-cart button) sits in a fixed column, and the size widget should live directly beneath or beside the size selector — not buried under the description or in a separate tab.
A few placement notes specific to Wix's editor:
- Anchor the embed element to the same section as the variant dropdown so it scrolls with the buy box on mobile, not with the product gallery.
- Wix's mobile editor treats desktop and mobile layouts separately — you'll need to reposition the embed on the mobile view independently, since Wix doesn't always inherit desktop placement 1:1.
- If you're running the widget across multiple product templates (Wix Stores supports several), repeat the embed step for each template rather than assuming one placement covers the catalog.
- Keep the trigger visible without scrolling on mobile; a widget that only appears after a scroll gets a fraction of the engagement.
This is the same principle covered in how to add a size recommendation widget to Shopify — the platform changes, but proximity to the buy box is what drives usage regardless of storefront.
Validating the Integration Against Wix Stores
Before calling it done, run through a short validation pass. This catches the two failure modes that show up most often on Wix: the widget mounting but not reading product context, and the widget working on desktop but not the mobile editor's separate layout.
- Load the live product page (not just the editor preview) — Wix's iframe sandboxing behaves differently in preview vs. published mode.
- Confirm variant awareness. If you're using Velo to pass product ID or category, check the browser console for the widget's initialization payload and verify it matches the product you're viewing.
- Test the mobile layout separately, since Wix maintains an independent mobile editor state.
- Check the add-to-cart flow if you wired a size-selected callback — confirm the recommended size actually populates the Wix variant dropdown rather than just displaying inline.
- Cross-check a few SKUs, including any with unusual size runs (petite, plus, wide-width), to make sure the widget doesn't silently fail on non-standard variant structures.
None of this requires custom backend work if you're using the HTML embed route — it's mostly editor and browser inspection. Velo integrations warrant a bit more testing since you're relying on Wix's frontend APIs staying stable across editor updates.
Where YourSizer Fits
YourSizer's widget is designed to drop into exactly this kind of embed slot — it mounts via a lightweight script tag, so the HTML embed route in Wix works out of the box without any Velo code required. For merchants who do want tighter integration (auto-detecting the product's category, or writing the recommended size back into the variant dropdown), the same embed exposes the hooks Velo needs to read and act on its output.
It doesn't require migrating your product catalog or replacing Wix Stores' native size options — it sits alongside them, asking a shopper a handful of quick questions (or reading saved measurements on repeat visits) and returning a size recommendation mapped to your existing size chart. For Wix merchants specifically, that means no backend changes and no dependency on Wix's more limited app marketplace integrations.
Frequently Asked Questions
Does adding a size widget to Wix require the Wix Business plan or above?
It depends on the embed method. The HTML/Custom Element embed is available on Wix plans that support custom code, which for Wix Stores generally means anything above the most basic non-commerce tiers. Velo (Dev Mode) is free to enable on any site plan that includes Wix Stores, so the coding-based route isn't gated behind a higher-cost plan on its own — cost considerations usually come from the size-recommendation vendor, not from Wix's platform fees.
Will a size widget slow down my Wix product page?
A well-built widget loads asynchronously and shouldn't block the initial render of the product page, since it mounts into its own iframe or container after the core page content loads. The bigger risk on Wix specifically is stacking too many third-party embeds (chat, reviews, upsells, size widget) on one template, which can add up even if each individual script is lightweight. It's worth checking page speed before and after adding any embed, using Wix's own site performance tools or a general tool like PageSpeed Insights.
Can the widget write the recommended size directly into Wix's variant selector?
Yes, but only through the Velo route. The HTML embed alone can display a recommendation to the shopper, but it can't reach into Wix Stores' native variant dropdown without Velo code listening for the widget's output event and calling the Wix Stores Product Page API to set the selected option. This is a common next step once a merchant has validated the basic embed and wants to reduce the extra click between "see recommendation" and "add correct size to cart."
Conclusion
Wix's editor and Velo platform are flexible enough to support a size-recommendation widget without a full storefront rebuild, but the value only shows up if the widget sits where shoppers are already looking — next to the size selector, not below the fold. As more Wix Stores merchants in apparel and footwear treat fit guidance as a baseline feature rather than a nice-to-have, the platforms and integrations that make this a quick embed rather than a custom-dev project will end up setting the norm for the rest of the catalog.
