Catalog architecture for a UK origin construction materials distributor with 2,800+ SKUs and a five year old website showing only 100 products

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.

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.

Multi brand engagement coordination. The work spans catalog architecture at FICAITION, website design and product pages at NERDSEY, and Tally standardization and inventory management at OSFORBIZ. One client, three brand engagements running in coordinated sequence.

Multi brand engagement coordination on a single client takes more upfront scope definition than a single brand 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.