The Fit LibraryFit & Measurements

Measurement Portability

Data portability for fit

The ability for body and fit data to move with the customer across brands, ateliers, and platforms.

What it means Why it matters Related readings Trust & foundations FAQ

Definition

Measurement Portability is the mechanism within Size Passport that lets a person's fit data move from one brand, atelier or platform to another without re-measurement, data loss or lock-in to any operator. It is not the same as being able to download a file. Portability in this sense means the receiving system can read the record, interpret it correctly and act on it: the field names mean the same thing on both sides, the permissions travel with the data, and the provenance of each measurement is legible to whoever receives it.

For the person

It means not repeating the same measurements every time a new tailor, brand or stylist enters the relationship. You are measured properly once and present the record thereafter. If you commission in Milan and later in London, the second cutter starts from what the first established rather than from scratch — and if you stop working with either of them, the record leaves with you.

For the ecosystem

Portability is the wedge that turns fragmented tailoring data into a network layer with interoperability potential. It is also the feature no incumbent will build, because the value it creates accrues mostly outside the operator that funds it — which is exactly why it has to come from a neutral party. That asymmetry is the opportunity: a neutral carrier captures the coordination value that no single brand can justify capturing alone, and becomes more valuable with each operator that joins rather than with each one it excludes.

Why it matters

Why this page matters in the wider system.

It reframes fit as customer-owned infrastructure rather than operator-owned residue from a transaction. Today the measurement a tailor takes belongs, in practice, to the tailor: it sits in their book or their CRM and stops being useful to the person the moment they walk out. That arrangement quietly transfers the cost of every subsequent relationship onto the customer, who pays for the same discovery work over and over. Portability moves the asset to the person it describes, which changes the economics: a measurement taken once earns its cost across every order that follows, at any operator, for as long as the body holds.

Normalises body and garment measurements into reusable records with stable field names, so a receiving system does not have to guess what a number refers to.

Attaches permission logic to the record itself, so portability does not break privacy: moving the data does not mean exposing it.

Keeps historical context alongside the current values, so the receiving operator can tell a stable measurement from a recent one.

Records provenance per measurement — who took it, when, under what protocol — because a self-reported number and a fitter's number deserve different weight.

Degrades gracefully: a partial record is still useful, and a receiving operator can see which dimensions are missing rather than silently assuming defaults.

This idea becomes clearer through the others around it.

Depends onSharing & Access

Trusted Record System

Trusted system for shared fit records

Portability only scales when the storage and permission model are not brand-bound.

EnablesFit Across Brands

Cross-Brand Sizing

Brand-neutral fit translation

Cross-brand sizing is impossible if measurements cannot travel.

SupportsSharing & Access

Shared Fit Language

Shared language for fit records

Interoperability begins with portable data definitions.

Questions answered clearly

Direct answers for people, search, and AI systems.

Is portability only about export?

No. Export is one expression of it. Portability also means shared interpretation, permissions and continuity across approved operators. A file you can download but nobody can read is not portability; it is compliance theatre. The test is whether the receiving system can act on the record without a human retyping it.

Why is portability a category-level idea?

Because it changes who owns the data relationship, and that makes the platform useful across many brands instead of inside a single stack. A feature improves one product. A category-level idea changes what everyone in the market has to offer: once customers expect to carry their measurements, an operator who cannot read them is at a disadvantage they did not previously have.

What is the difference between portability and data export?

Data export is a one-time action that produces a file. Portability is a standing architecture: fit data remains continuously reusable, shareable and interpretable across any approved operator, not only when a manual export is triggered. The practical difference shows up at the receiving end — an export usually needs someone to retype it, a portable record does not.

Is measurement portability a legal right as well as a technical feature?

GDPR Article 20 establishes data portability as a legal right for EU residents, and body measurements processed on consent or contract fall within it. The right has existed for years without changing much, because the exported file is rarely in a form another system can ingest. The technical work is what turns the entitlement into something a person can actually use.

What stops a brand from simply keeping a copy?

Nothing technical, and pretending otherwise would be dishonest. A brand that has legitimately received measurements to cut a garment holds them. What the permission model governs is future access and future use: revocation stops a brand reading the current record, contributing to it, or relying on it for a subsequent order. The record's value is in staying current, and a stale copy stops being useful quickly.

Does portability require the whole industry to adopt a standard first?

No, and waiting for that would mean waiting indefinitely. A neutral carrier can operate the portability layer between any two operators that agree to use it, which is how every successful standard started: enough bilateral adoption to make the schema worth conforming to. Industry-wide standardisation makes portability cheaper; it is not a precondition for it existing.