Fit records reset at every brand boundary. What real interoperability requires and why the industry has not built it.
TL;DR — Fashion interoperability means a fit record created at one brand can be read and trusted at another without manual re-entry or semantic loss. That infrastructure does not exist today. The gap drives roughly 70% of EU online fashion returns and costs retailers an estimated €23 billion each year. Closing it requires three things in sequence: a shared vocabulary, a shared permission model, and a neutral carrier no single brand controls.
Fashion interoperability exists when two separate systems can exchange fit information and then meaningfully act on what they received. Almost no part of the current fashion stack satisfies that definition. A body measurement record created at a Zara fitting session does not travel to Brunello Cucinelli. A bespoke pattern archived at a Milanese atelier does not follow its owner to a London tailor. The record resets at every brand boundary, and the customer pays for that reset in wasted time, misfit garments, and returned orders.
This is not a software gap. The industry has abundant software — Salesforce Commerce Cloud, Shopify, custom ERP systems, fit-tech startups raising hundreds of millions of dollars. The gap is structural: fashion built its digital infrastructure as isolated brand assets, each with a proprietary vocabulary, a closed permission model, and incentives that reward lock-in over portability.
Definition
Fashion Interoperability
A shared schema, vocabulary, and permission model that allows fit records — body measurements, preferred ease, body geometry, alteration notes — to travel meaningfully between operators without semantic loss, manual re-entry, or violation of the customer's data rights under GDPR Article 20.
Fashion interoperability is not the same as integration. Integration connects two specific systems through a bespoke bridge. Interoperability means any two conforming systems can exchange records without prior arrangement — the same way any two email servers can send messages to each other via SMTP. That distinction matters because bespoke bridges do not scale: the EU fashion market involves approximately 40,000 active brands, hundreds of platform vendors, and over 340 million online shoppers.
Measuring whether a system is truly interoperable requires asking three precise questions. First: does a record from System A carry enough semantic structure that System B can parse it without guessing? Second: do the permissions that governed the record in System A transfer correctly into System B? Third: does the customer retain control throughout, consistent with GDPR Article 20's right to receive personal data in a machine-readable format and transmit it to another controller?
Today's fashion stack fails all three tests. Field names differ between platforms — 'chest circumference' in one system becomes 'bust' in another and 'pecho' in a third. Permissions do not travel with the record; they live inside the issuing brand's database. And GDPR portability rights, while legally real, produce export files that no downstream system can practically ingest.
Returns are the most visible and quantifiable symptom of the fashion interoperability gap. According to McKinsey's State of Fashion 2024, EU online fashion return rates sit at 25–35% of total orders, with sizing cited as the primary driver in approximately 70% of cases. The European Environment Agency estimates the broader textile return and waste cycle costs EU retailers roughly €23 billion annually — making this not primarily a logistics problem but an information failure.
When a customer has purchased successfully at Brand A, the fit signal is already captured. Brand A knows the customer's chest measurement, waist, inseam, and preferred ease in that brand's specific cut. But Brand B has none of that. It asks the customer to guess a size from an opaque chart, receive the garment, discover the misfit, and return the item. The information that would have prevented the return already exists — it simply cannot cross the boundary between two brand databases.
In made-to-measure operations, this problem appears in a different form. When a client returns after eighteen months, most ateliers begin the measurement session from scratch — not because their previous record was deleted, but because there is no standard format to retrieve and verify it. A tailor in Milan cannot confirm whether a pattern file sent by a client's previous tailor in Paris uses the same ease conventions or the same reference posture. The record exists; the shared vocabulary to interpret it does not.
Three structural gaps explain why fashion interoperability has not emerged organically from the market. Each gap is solvable using established technology. Together, they require coordinated investment that no single brand has an incentive to fund unilaterally — a classic public-good coordination failure.
Real fashion interoperability is not a single technology choice. It is a coordinated stack of three components that must be resolved in order — vocabulary first, then permissions, then carrier. Skipping any layer produces a partial solution that breaks under real-world conditions: a shared vocabulary without a permission model creates a privacy risk; a permission model without a neutral carrier creates a monopoly risk.
The challenge is partly technical, but mostly institutional. No single brand captures all the upside of interoperability. That asymmetry of incentives is exactly why no single brand will fund public infrastructure on its own — and why the solution must be governed outside the competitive layer.
The W3C Verifiable Credentials Data Model 2.0 — a W3C Recommendation as of May 2023 — offers the closest existing analogy to what fit interoperability requires. A verifiable credential is a tamper-evident, cryptographically signed claim: for example, 'this person's chest circumference is 98cm, measured on 2025-11-14 by Operator X under consent reference Y.' The holder — the customer — controls disclosure. Any downstream verifier can confirm the claim's authenticity without contacting the original issuer.
Applied to fit data, this model means each operator issues a signed measurement credential into the customer's wallet — either a software wallet or a governed platform. When the customer shops at a new brand, they share the relevant credential. The brand verifies measurement provenance, accepts or queries it, and completes the transaction without re-measurement. Mapping this against the three structural gaps: the VC model directly addresses both the vocabulary problem (the credential schema carries ISO-aligned field names) and the permission problem (the holder controls selective disclosure). The remaining gap is still the neutral carrier — a governed trust registry willing to maintain the schema and anchor the credential chain.
The market has not solved fashion interoperability because the economic incentives are structurally misaligned. The brand that invests in measuring a customer's body captures some of the value — through reduced returns and higher repeat-purchase rates. But the larger share of the value accrues to the customer and to the industry as a whole: every future brand that customer shops at benefits from not needing to re-measure. That benefit does not flow back to the brand that paid for the measurement.
This is a textbook public-good problem. Zara's proprietary fit data creates switching costs that benefit Zara. H&M's incompatible size charts benefit H&M. Neither brand has a rational incentive to make their fit data readable by the other — and both have active incentives to prevent it. Smaller brands free-ride on whatever imperfect data they can extract from returns and customer surveys.
Comparable coordination failures in other industries were resolved by standards bodies — GS1 for product identifiers, IETF for internet protocols, ISO for measurement — or by regulatory mandate, as PSD2 did for bank data portability in the EU. Fashion has neither a binding standard for fit data exchange nor a regulatory mandate analogous to PSD2. Until one or both conditions change, the interoperability gap persists by design rather than by technical necessity.
Interoperable fit data would restructure several layers of the fashion stack simultaneously. According to McKinsey's modelling, customers who carry a verified fit record experience 15–25% fewer size-related returns. Customer onboarding at new brands would compress from a multi-order discovery process to a single confirmed purchase. Made-to-measure operators, who currently rely on customer recall for repeat clients, would begin each new commission from a verified body record rather than a blank measurement sheet.
Once fit records become interoperable, trust compounds across relationships instead of resetting inside each walled garden. Returns become addressable at the information layer. And the tailoring intelligence built at one operator becomes an asset the customer carries permanently — not a locked record that disappears when they change their wardrobe.
The sustainability case is equally material. The EU Strategy for Sustainable and Circular Textiles explicitly identifies fashion returns as a driver of avoidable textile waste. A customer who returns three garments per year to find the right fit at a new brand generates approximately 1.5kg of avoidable CO₂e emissions and consumes packaging, last-mile logistics, quality inspection, and restocking resources on each cycle. Interoperable fit data cuts this at the information layer — before the garment is manufactured, shipped, returned, and processed.
The infrastructure moat effect also shifts. A competitor can copy a product line. They cannot copy five years of a customer's verified measurement history, updated across dozens of orders, refined by garment feedback and body change. Fit interoperability does not eliminate competitive advantage — it relocates it from the brand's database to the customer's portable record, making the advantage durable rather than captive.
No. A universal size standard would require every brand to agree on what 'size M' means — a coordination challenge the industry has failed to resolve for over a century. Fashion interoperability is a different goal: it allows each brand to keep its own sizing system while enabling fit records — body measurements, not brand sizes — to travel between systems. The measurement is the stable data point; brand sizes are just labels applied to it.
GDPR Article 20 grants a right to receive personal data in a structured, commonly used, machine-readable format and to transmit it to another controller. In principle this covers fit data processed by consent or contract. In practice, the exported file is rarely in a format any receiving system can ingest — because there is no shared schema defining what the fields mean. The legal right exists; the technical implementation does not. Interoperability closes that gap between legal entitlement and practical usability.
Virtual try-on features — like those deployed by Zara, ASOS, and several independent fit-tech vendors — are proprietary, single-brand tools. They help a customer evaluate a specific product on a digital avatar within one brand's interface. They do not generate a portable, signed record. Fit interoperability is an infrastructure layer: it produces a verified, shareable credential that any conforming brand can consume. The two are complementary — a virtual try-on session could contribute measurements into an interoperable record — but they address different problems at different layers.
ISO 8559-1:2017 defines body measurement terminology and procedures for garment construction and is the strongest existing candidate for the vocabulary layer. W3C JSON-LD 1.1 provides the serialisation format that would allow ISO-aligned field names to be embedded in linked-data records readable by any system. GS1 Digital Link demonstrates how a neutral standards body can maintain a globally adopted product identifier vocabulary — the equivalent model for person-level fit data remains to be built on top of these foundations.
A neutral carrier is a governed entity — not owned by or commercially aligned with any single brand — that maintains the shared schema, operates the permission registry, and holds the cryptographic audit trail for fit records. It functions as infrastructure rather than product: the way the internet's DNS system resolves domain names without any single company controlling the process. Without a neutral carrier, any 'shared' fit data system becomes a de facto monopoly operated by whichever brand or platform built it first.
Sources
Related concepts