Applied Architecture // Catalog Design

Product Taxonomy
Architecture

281 categories built from actual SKU data, not leadership assumptions or inherited structures. A four-level hierarchy designed for findability, merchandising scalability, and structured data ingest into the commerce platform.

Download Blank Template ↓

Why This Structure
Not Another

Leadership initially dictated four top-level categories without data backing. The project lead pushed back, mined actual SKU data, forced a GM to justify his logic, and built an L1 through L4 hierarchy grounded in how customers actually search for the catalog.

Principle 01
Data Over Opinions
Category structure derived from SKU attributes and search patterns, not organizational chart logic or inherited catalog conventions.
Principle 02
Depth Over Breadth
L3 and L4 categories created to support filtering, faceted navigation, and future merchandising. Shallow taxonomies create dead-end browsing.
Principle 03
Ingest-Ready Structure
Categories designed to support CSV bulk import with External IDs, parent-child relationships, and sequence numbering. Manual entry does not scale.
Principle 04
Platform-Native
Built within the platform's native category framework. No workarounds. No custom fields. No structures that break on platform updates.

Four Levels
One Logic

L1 L2 L3 L4
Camping Shelter Tents Backpacking tents
Camping Shelter Tents 3-season tents
Camping Shelter Tarps Ultralight tarps
Camping Cooking Stoves Canister stoves
Camping Cooking Stoves Liquid-fuel stoves
Climbing Protection Harnesses Sport harnesses
Climbing Protection Carabiners Locking carabiners
Climbing Hardware Belay Devices Assisted-braking devices
Paddling Watercraft Kayaks Touring kayaks
Paddling Watercraft Kayaks Whitewater kayaks
Paddling Safety PFDs Inflatable PFDs
Apparel Layering Insulation Down jackets

Numbers That Matter

281
Grandchild Categories
4
Hierarchy Levels
100+
SKUs at Launch
0
Categories from Assumption

Taxonomy is quietly one of the hardest parts of e-commerce because it determines findability, conversion rate, and future merchandising capability. A shallow or assumption-driven category structure creates technical debt that compounds with every SKU added. The taxonomy was designed to be correct first and convenient second.

Back to Case Study