SKU Range Catalog vs. Product Categories
When to use each product classification structure, and why both can coexist.
📊 General Comparison
This document explains the difference between two key structures in product management: the SKU range catalog and the product category catalog (the platform's shared categories table). Both can coexist and complement each other.
| Aspect | SKU Ranges | Product Categories |
|---|---|---|
| Classification basis | Numeric or alphanumeric (e.g. SKU, SAT code) | Semantic or descriptive (e.g. "Textiles," "Vinyls") |
| Main purpose | Automation, validation, internal rules | Visual organization, navigation, marketing |
| Typical applications | Bulk updates, filtering by range | Search filters, grouping by type |
| Flexibility | Scales without renaming anything | Requires keeping hierarchies clear |
| Example use | "Update prices for SKUs between 5000 and 5999" | "Show every product in the Textiles category" |
🔢 What the Range Catalog is Good For
- Bulk updates: prices, taxes, or discounts by batch.
- Validation: catching out-of-range or duplicate SKUs.
- Rule automation: applying conditions based on range (e.g. packaging, exclusions).
- Reporting: by SKU group without relying on text labels.
- Hierarchical view: each range can represent a critical product line or category for the business.
🏷️ What the Category Catalog is Good For
- Visual organization: clear navigation by product type.
- Search filters: by material, use, or function.
- Commercial presentation: grouping for customers, catalogs, or interfaces.
- Semantic documentation: useful for reports, labels, or display.
On the platform: categories live in the shared
categories table, distinguished via category_type_map → category_types (for example, "Product Categories" is just one category_type among several sharing the same table).
✅ Conclusion
Both catalogs serve different, complementary purposes. The range catalog lets you automate and validate internal processes, while categories make external organization and presentation easier. Using both together gives clearer, more scalable product management.