Frequently asked questions

The shopper enters height and weight, which the engine turns into a full body estimate shown as a 3D body model in the size flow. They can tune chest, waist and hip. That model is matched against the size chart that applies to the specific product on the page, adjusted for how tolerant the garment is and how the brand intends it to fit.

The result is one recommended size, plus an explanation when the shopper sits between two.

Accuracy is dominated by one thing: the quality of the size chart behind the product. A precise body model matched against a vague chart produces a vague answer. That is why onboarding spends most of its time on charts, why published charts are versioned and immutable, and why the dashboard flags products with missing or implausible charts instead of silently falling back to a default.

We would rather you A/B test it on your own store than take a benchmark on trust.

No. Height and weight are enough to get a recommendation. Entering real measurements improves the result, so the interface offers it — but it is never required, and no photo or body scan is needed to get a size.

Body measurements are treated as personal data under GDPR and KVKK: defined retention, soft delete, and a right-to-erasure path. Merchants see aggregate sizing insight, not individual shopper profiles, and data is isolated per merchant at several layers. Technical detail →

Yes, on its own template rather than the adult flow. Children’s sizing follows the European height-grid convention with a growth-percentile anchor, because a child’s size is driven by height and age far more than by weight.

The 3D body model is part of the size flow: it is shaped by the shopper’s measurements and it is what the recommendation is based on. Virtual try-on is photo-based — the shopper uploads one ordinary photo and gets an image of the product on themselves. Try-on never overrides the computed size, and it is a separate entitlement that can be enabled per store and per product.

Shopify (the app is listed on the Shopify App Store as YourSizer), ikas, Ticimax, T-Soft, IdeaSoft and Faprika, through ready integrations. WooCommerce is coming soon. Until then — and on any other store — the widget is added with one loader script tag copied from the merchant panel. Full coverage matrix →

The widget renders inside an isolated root, so your CSS cannot leak into it and its styles cannot leak into your storefront. It also carries stacking defences against third-party overlays. On mobile it renders as an edge-to-edge bottom sheet rather than a desktop modal.

No. The portal is self-service and identifies the order without a login. On Shopify the portal can also be served from your own domain, so the shopper never leaves the store.

From the delivery date reported by your storefront platform. If no delivery event exists yet, no deadline is shown — a countdown started from the order date would not be the period the law describes.

The statutory withdrawal period is stored separately from your own return policy window, so a shorter shop policy cannot shorten a legal right.

Yes. Reasons, sub-reasons, which reasons require evidence, which items are non-returnable, the return window and what each reason may result in are all configured per merchant.

It executes. Refunds, exchanges and store credit are written back through your platform’s own APIs, so your commerce system stays the source of truth. Restock is an explicit, logged decision, and the stock movement is written back to the platform when the store has granted the inventory permission.

Eligibility and the exact deadline for an order, the status of an existing request, refund method and timing, cargo drop-off instructions in the shopper’s language, and tracking state. All of it comes from a deterministic engine reading real order state — the language model only interprets the question and phrases the answer, and the assistant hands over instead of guessing when it has no answer.

ResReturn is live on Shopify, Ticimax and ikas. T-Soft is in early access. WooCommerce, IdeaSoft, Faprika and custom storefronts are planned. The Shopify app is in App Store review — until it is listed, stores are set up through a demo or early-access link. Full coverage matrix →

The packshot you already produced for the catalogue — the product on a plain background. Plus the category and the size you want represented.

That is the point of a fixed model library. The same model, pose and lighting are reused across a collection, so the product is the only thing that changes between images and a category page reads as one shoot.

Not by accident. Publishing is append-only and every publish can be rolled back in one operation. Setting a variant image — the one write that can replace your own photography — requires its own explicit confirmation, and write access to a store is off by default.

A body-fidelity gate scores how faithfully the generated body matches the requested size before the image is accepted, and sizes map to models explicitly rather than being inferred. Output that renders an XXL as a sample size is rejected.

Prices are published, and each product can be bought on its own. YourSizer plans are set by monthly orders:

Paid plans include unlimited products and size charts. Virtual try-on is billed per generated image at $0.25. On Shopify, YourSizer is billed through Shopify and starts with a 30-day free trial. YourSizer pricing →

ResReturn and NoShot publish their own prices on resreturn.com/pricing and noshot.co/pricing.

On a supported platform, connecting the store and placing the widget is a same-day job. The variable is size-chart preparation, which is also the part that determines accuracy — so it is worth spending the time there.

Yes. All three ship independently. They share a data layer when you run more than one, which is where return reasons start informing size charts — but none of them requires the others.

Write to contact@yoursizer.com or see the company page for how to reach us.