We use Google Analytics 4 to see which pages are useful. It loads only if you accept it, and then sets two cookies, _ga and _ga_C372PEK7KT. Nothing is stored until you choose, and nothing it records is used for advertising or sold.
Size Passport gives your customers one consistent size across every channel, so they buy the right fit the first time. The result is lower return rates, shorter fitting-room cycles, higher conversion, and more lifetime value, online and in store.
A customer who already knows their size in your sizing does not order three and send two back. Approved operators work from a record that already holds measurements, fit history and prior garment outcomes, instead of restarting the guess at every checkout.
Size uncertainty is an abandonment reason, not only a returns reason. Removing it at the point of decision converts visitors you are already paying for, and shortens fitting-room cycles in store.
You receive a size recommendation, not raw body measurements. Access is explicit, attributable to the operator who used it, and revocable by the customer. That is a materially easier position to hold under GDPR than keeping body data in your own silo.
01
Thirty minutes on your operating model, your return rate by category, and where size uncertainty is actually costing you. You leave with a view of whether this is worth piloting, including if the answer is no.
02
We map your operators to the permission model before any data moves: what you can read, what you can contribute, how long access lasts, and how a customer revokes it. Written down, not assumed.
03
One channel, one category, measured against your existing return rate. In-store fitting, made-to-measure intake or post-purchase alteration, whichever already generates the most size friction for you.
Fit is not a small share of the returns problem. It is most of it, which is why sizing accuracy moves the return rate in a way that better photography and longer descriptions do not.
Our permission model: you receive a size, not a body
Published industry benchmarks, not Size Passport results. We are pre-launch, and we will not present someone else's figures as our own performance.
Three surfaces, all live in the product today. None of them asks you to store body data or to build a size engine of your own.
The customer presents their code, your associate scans it, and the approval prompt goes to the customer's device. The scan resolves to a size for the garment in hand, not to a measurement sheet. Any phone camera works; nothing to install on your side.
OAuth 2.0 with scoped, revocable grants, published through standard discovery at /.well-known/oauth-authorization-server. Your systems ask for a size for a specific product, and the grant, the scope and the operator identity are all recorded against the customer's record.
The same surface is exposed over MCP and an RFC 9727 API catalogue, so an assistant acting for your customer can retrieve a size under the same permission model a human operator uses. Built, not planned.
Most fit tools are built for one retailer and end at its checkout. The distinction matters commercially, because it decides who carries the data risk and whether the accuracy improves or resets when the customer shops somewhere else.
| In-house size recommender | Size Passport | |
|---|---|---|
| Where the fit data lives | In that retailer's systems | With the customer, referenced by permission |
| Works at another brand | No, it resets | Yes, the same record travels |
| What the brand receives | Body measurements, in most implementations | A size for the specific product |
| Who can revoke access | Governed by the retailer's policy | The customer, at any time |
| In-store use | Rarely, usually web only | QR at the counter, same record |
| If the operator shuts down | The fit history goes with it | The record stays with the customer |
Questions brands ask first
Every meaningful access begins with explicit customer permission. Depending on the granted scope, that access can persist for an ongoing relationship or a tightly limited session.
Operator contributions become part of the customer's record and remain attributable to the contributing brand or atelier. The customer owns the composite record.
Yes. The architecture is being shaped to support integration without turning Size Passport into a brand-specific database. Pilot conversations help define the right sequencing.
The current public rollout is best suited to luxury retail, made-to-measure, tailoring, atelier workflows, and any operator where fit continuity meaningfully affects service quality.
No, and that is the point. Your systems receive a size for a specific product, not the underlying measurements. The body data stays in the customer's record, which means it is not in your breach surface, your retention schedule or your subject-access workload.
Size Passport is free for shoppers, and partner terms are set per pilot rather than published as a price list, because the shape of an integration differs sharply between a single atelier and a multi-store retailer. The scoping call covers commercials openly; nobody signs anything to have it.
Against your existing return rate in the piloted category, over a defined window, using your numbers rather than ours. If it does not move, that is a result worth having early, and we would rather find it in one flow than after a full rollout.
Request partner access
Share a concise view of your brand, your role, and the fit problem you care about. We will use it to shape the right follow-up conversation.
Not ready to talk? The Fit Library sets out the whole model in the open, with no form. Open the Fit Library
Want the conceptual layer first?
The Fit Library explains the logic behind Body Passport, measurement portability, and trusted cross-operator access.