Roughly ten thousand products across four trading-card franchises lacked a structured set-data model. API-created records also defaulted to drafts, requiring explicit publication handling.
Web & data / CASE STUDY
From product titles to structured catalog data.
Catalog engineering at 10,000 SKUs
MY CONTRIBUTION
Designed the card-set data model, published set records through the administration API, and built a backfill connecting products to their set data.
218+structured set records published
EXPLORE THE SYSTEM
Explore a small fictional catalog and the relationships behind it.
CATALOG EXPLORER6 fictional products
6 sample products
Synthetic catalog · the project’s real scope is described separately
Model sets as structured records and connect them to products through custom fields, handling record creation, publication, and product backfill through the platform API.
A structured schema, 218+ published set records, and a product backfill supporting set-based filtering, grouping, and merchandising instead of relying on free-text titles.
The public diagram explains a generalized franchise, set, and product relationship. It contains no client product records or credentials; it is not a view into the live catalog.
Technical diagramView the full overview
A CLEAR SCOPE. A USEFUL NEXT STEP.What needs
What needs
to work better?
Tell me where things stand, what’s getting in the way, and what you need to happen next.
Discuss your project Ontario, Canada · English & Spanish