TP TP ExchangeConversion POC

Specification-driven public demonstration

One Tech Pack.
A different format.

This POC converts a public basic-skirt Tech Pack into a different public Excel template. It exposes every mapping decision, preserves where each value came from, and sends uncertainty to review.

What this provesA repeatable conversion mechanism on public data. It does not claim to represent Birdy or any buyer’s private workflow.

Try the conversion

Source in. Evidence out.

The adapter deliberately supports one published source specification. Uploading an unrelated file will fail clearly rather than produce a plausible-looking result.

01 Source format
First page of the public FW21-002 Basic Skirt Tech Pack, showing metadata, measurements and technical flats
FW21-002 Basic Skirt Tech PackUniversity of Fashion · PDF · 3 pages
PDF

Public sample is ready.

02 Process
  1. Verify source specFile identity, format and adapter
  2. Extract fieldsMetadata, materials, trims and measurements
  3. NormalizeAliases, units and canonical field names
  4. Map or escalateConfidence, provenance and exceptions
  5. Write destinationPublic four-sheet Excel template

Waiting to process.

03 Destination format
No destination yet Run the conversion to create the Excel Tech Pack.

Before and after

Same information. Different operating burden.

The comparison is about the handling of evidence, not a claim that every conversion becomes fully automatic.

Before

A merchandiser interprets and re-keys the document.

  • Find values across pages and formats
  • Decide whether labels mean the same thing
  • Copy data into a new template
  • Remember what was skipped or assumed
Primary riskSilent interpretation becomes production data.
After

The specification handles routine mappings and exposes judgment.

  • Extract each value with its source location
  • Normalize defined aliases and units
  • Populate only supported destination fields
  • Route mismatches and visual content to review
Primary outcomeA usable destination file plus a traceable exception list.

The conversion specification

The rules are a product asset.

This POC is deterministic. The adapter declares what it accepts, what it can map, and when it must stop.

Source contract

University of Fashion basic-skirt PDF

Expected metadata labels, measurement rows, three-page structure and file fingerprint.

Canonical model

Product, materials, trims, measurements

Source terminology is normalized without losing the original label or value.

Destination contract

GetTemplated four-sheet Excel Tech Pack

Cells and fields are populated only where the destination meaning is compatible.

Safety rule

Nothing gets silently lost

Unmapped, ambiguous and visual-only content appears in the conversion report.

What the next POC must prove

Public data validates the mechanism.
Partner data validates the business.

The next step is to run the same pipeline on two anonymized incoming Tech Packs and one real downstream template from a buying house. That is where we test coverage, exception rates, review time and operational trust.