, 01/ 03
Construction materials distributors get flattened by generic ecommerce catalog systems. The SKU depth requires architecture work that respects category taxonomy.
FICAITION · case file · bcr-industries.case
Catalog architecture for a UK origin construction materials distributor with 2,800+ SKUs and a five year old website showing only 100 products
2,800+ SKUs across tile trims, shadow gap profiles, expansion joints, floor transitions
Catalog Architecture · 2,800+ SKUs · Full Stack Engagement
SHIPPED
OWNED BY CLIENT
bcr-industries.case● LIVE
› CLASSCatalog Architecture
› STATUSSHIPPED
› OUTCOME2,800+
› OWNERSHIPCLIENT
› SOURCEFICAITION STUDIO · DXB
── THE SITUATION
Where it started.
Construction materials distributors carry SKU depth that consumer ecommerce does not. Tile trims alone fragment into dozens of profiles, finishes, and dimensions. Shadow gap profiles, expansion joints, and floor transition strips each carry their own taxonomy reality. A catalog architecture that does not respect that depth flattens the business into a fraction of what it actually distributes.
BCR Industries arrived with 2,800+ SKUs in the operational reality and only 100 of them on the website. Five year old website. Tally inventory naming chaos with duplicates and inconsistencies. The catalog architecture work had to handle the SKU depth and the naming hygiene at the same time.
── WHAT WE BUILT
The build.
Catalog architecture for 2,800+ SKUs covering tile trims, shadow gap profiles, expansion joints, and floor transition strips. Each category mapped to its own taxonomy reality, not flattened into a generic product schema.
Naming standardization framework across 2,500+ SKUs. The Tally chaos was carrying duplicates and inconsistencies that broke any clean catalog build. The naming framework resolved both before the catalog deployment.
Duplicate resolution at the SKU level. Every duplicate SKU identified and resolved against the canonical product reality.
Website catalog population strategy for the 2,700 products missing from the live site. The architecture supported staged population so the live catalog never broke during the build.
Full stack engagement coordination. The work spanned catalog architecture, website design and product pages, and Tally standardization and inventory management, all in house. One client, one studio, three workstreams running in coordinated sequence.
── THE RESULTS
The numbers.
SKU coverage on website
Catalog architecture supporting the full SKU depth
from 100 products on a 2,800+ SKU business
Naming hygiene
Standardization framework across 2,500+ SKUs
from Tally chaos with duplicates and inconsistencies
Catalog taxonomy
Category specific taxonomies respecting product reality
from Generic product schema flattening the business
Engagement scope
Full stack engagement, catalog plus web plus inventory in house
from Single discipline scope
── WHAT MADE THIS WORK
The decisions behind it.
, 02/ 03
Naming standardization is not a cosmetic fix. It is the foundation that any clean catalog build sits on top of.
, 03/ 03
Full stack engagement coordination on a single client works when each workstream owns its scope cleanly and the handoffs are documented from day one.
── WHAT WE'D DO DIFFERENTLY
› POST SHIP REVIEW · THE HONEST LOG
A full stack engagement on a single client takes more upfront scope definition than a single discipline engagement. The BCR work required clean boundaries between the catalog architecture, the website design, and the Tally standardization scope. We absorbed that scope definition time because the alternative is overlap and gaps that show up later in deployment.
Client details anonymized under NDA. Detailed case studies with metrics available on request.
YOUR BUILD NEXT
Ready for results like these?
Tell us what is costing you money. We will show you what we would build to fix it.