Paris / Sydney FREN

Connect your store

Book A Demo
Book a demo, then connect. JS SDK, REST API, or a private connector app.
01 — How it works MF / SETUP

Book a demo. Install Magic Fit. Start your 30 day free trial.

  1. 01

    Book a demo

    A short discovery call where we get to know your brand and understand the metrics that define success for you. Sign up and your Magic Fit account and your billing account are set up together, in one step, before anything touches your storefront.

  2. 02

    Install Magic Fit

    A one-click install whatever platform you’re on. Not on one of the major e-commerce platforms? That’s fine — a drop-in JS SDK and a REST API support any storefront, and we handle the work as part of onboarding.

  3. 03

    Start your 30 day free trial

    30 days on your storefront before you pay anything, with usage-based pricing beginning when the trial ends. Depending on the size of your store, we can also run a randomised holdout test for you, should you want it.

    See the Motto holdout
02 — Surfaces 5

One account, every surface.

Every region, your app, and the AI agents now shopping for your customers. Same engine, one account.

MF / REGIONS

Every geography

US, UK, EU, AU, APAC — every regional storefront on one account, reporting into one dashboard.

MF / APP

Your mobile app

Your iOS or Android app calls the same engine over the REST API. Same shopper, same size, in the app or on the site.

MF / AGENTS

Agentic shopping

AI assistants buying for your customers need a size. They get yours from the same API, not a guess.

MF / STACK

Any storefront

Shopify, WooCommerce, Magento, BigCommerce, Webflow, or headless on Next.js, Nuxt or Hydrogen. No platform lock-in.

MF / TEAMS

One agreement

Every storefront, region and channel you connect sits on one subscription and one invoice — nothing to renegotiate as you grow.

One account. One invoice. Every channel.

03 — Onboarding MF / ONBOARDING

Easy onboarding. We do the fitting.

Four steps from signed to live, and your team barely touches it.

  1. 01

    Designed to your brand

    We build the Magic Fit experience to match your storefront — type, colour, copy and placement. Almost everything in the UX is yours to shape. The one thing we hold firm is the input questions: we can't ask fewer, and we won't ask more.

  2. 02

    Size charts, wherever they live

    A spreadsheet, your PIM, tech packs, or the size guide already sitting on your product pages. We take your fit data in whatever shape it exists — there is nothing new for your team to build or maintain.

  3. 03

    Calibration

    We calibrate the engine to your own fit system, style by style, starting with the best sellers that cover at least 80% of revenue and working down the long tail from there.

  4. 04

    Go live

    You sign it off, we ship it. Most brands are live in 7–14 days, with usage and results reporting into your customer portal from day one.

Magic Fit platform powering size recommendations

The platform does the thinking.

196 million data points, a digital twin built from simple biometrics, and nine years of refinement. The Magic Fit engine runs in the cloud — channel-agnostic, and the same engine powers every integration.

Magic Fit connectors as private post-signup integrations

Wherever your customers shop next.

How people shop is changing fast — new regions, new platforms, and now AI agents buying on your customers' behalf. Add a storefront, replatform or go headless: your account, your sizing data and your pricing come with you, so changing how you sell never means starting over.

04 — How it works

FAQS

How quickly can we launch?

Most brands can launch in 7–14 days. Pilot timelines depend on assortment complexity and implementation requirements, but we are built for fast time-to-value.

Who does the onboarding?

We do 99.9% of the work so your team can focus on what they do best. You point us at your size charts and product data and tell us what good fit means for your brand; we handle the integration, the fit configuration and the QA. Where a connector exists we issue a private install link; anywhere else we do the front-end work as part of onboarding.

What do you need from us to get started?

Your size charts and whatever product measurements you already hold, plus your product team's fit intent if it is written down anywhere. We start with the styles covering at least 80% of revenue — usually your best sellers — and work down the long tail from there. Messy data is normal; sorting it out is part of onboarding, not a prerequisite for it.

How does the install actually work?

Once you've signed up and activated your account in the customer portal, we issue a private install link for your storefront. Our connectors aren't listed in public app stores — they're issued to Magic Fit customers as part of onboarding, and they plug your existing account into your theme. Where there's no connector for your platform, you integrate via the JS SDK or REST API instead.

Learn more: Service terms

How will we know it is actually working?

Usage and results report into your customer portal from day one. If your store has the traffic for it, we can also run a randomised holdout during the trial — half your shoppers see Magic Fit, half do not — so you get lift measured against a control group rather than an estimate. One brand ran exactly that across 102,706 sessions and measured a 6.6% lift in conversion.

Learn more: Holdout test

Can I use Magic Fit via API or headless?

Yes. Magic Fit exposes a REST API and a JS SDK so you can integrate the sizing engine into any storefront — Next.js, Nuxt, custom builds, WooCommerce, or mobile apps. Same engine, same accuracy, same account and pricing as any platform connector. If you can make an API call or load a script, you can run Magic Fit.

Will Magic Fit affect my site speed?

No it won't. Magic Fit is a few lines of code and doesn't pre-load anything. It is completely optional on the user side — data transfer occurs only when somebody initiates the experience. This is true whether you're using a platform connector, the JS SDK, or a headless API integration.

How does billing work?

Pricing is usage-based: you pay per size result the engine returns, and per saved fit profile applied as that shopper browses, so one engaged shopper raises more than a single charge while traffic that never asks for a size raises none. It is billed directly by Magic Fit, and those same two events count however you connect, whether that's a platform connector, the SDK, the API or headless. Signing up with us sets up your account and your billing together (they are the same account) and one subscription covers every channel. Fees begin after your trial. You'll never be charged separately inside your store platform.

Learn more: Usage-based pricing, Service terms

We run several regional storefronts. Is that one account or several?

One. Brands run Magic Fit across several regional storefronts — NZ, AU and US, for example — on a single account. Connect as many storefronts, regions or channels as you need: one subscription covers all of them, and usage for every store reports into the same customer portal.

Learn more: Service terms

Full commercial terms are set out in our service terms.