Product Categories
1. Overview & Category Taxonomy
What are Product Categories?
2. When to Use Product Categories
Multi-Tier Departmental Taxonomy (Supermarket / Retail)
Structuring tens of thousands of SKUs across departmental hierarchies (e.g. Fresh Groceries > Dairy & Chilled > Probiotic Yogurts).
POS Touchscreen Quick-Pick Tabs (FnB / Fast-Moving Retail)
Frontline cashiers in busy cafes or convenience counters need single-tap access to fast-moving items like Coffees, Pastries, or Ice without scanning barcodes.
Omnichannel Marketplace Taxonomy Mapping (Shopee / TikTok)
Synchronizing enterprise product catalog with external e-commerce marketplaces requiring specific category leaf classifications.
Gross Margin & Departmental Profitability Analytics
Executive management evaluates sales velocity and profit margins across diverse merchandise lines (e.g. Accessories at 60% margin vs Hardware at 15%).
Raw Material vs Finished Goods Operational Segregation
Manufacturing operations require strict isolation between raw ingredients (Flour, Sugar) and saleable retail items (Artisan Bread, Pastries).
3. Hierarchical Tree Architecture
The category tree uses a self-referencing relationship (parentId -> categories.id). When a new child category is added:
When deleting or moving nodes, the system checks whether the former parent still has remaining children and automatically resets isLeaf = true when appropriate.
4. Data Dictionary & Field Specifications
Column definitions for the recursive categories table:
| Field / Column | Input Type | Requirement | Description & Operational Guide |
|---|---|---|---|
code | Text (Category Code) | Required | System-wide unique identifier for the category node. Example: CAT-ELEC, CAT-APP-MEN |
name | Text (Category Name) | Required | Human-readable title displayed in navigation menus and POS counter tabs. Example: Consumer Electronics, Men Apparel |
parentId | Dropdown (Parent Category, Optional) | Optional | Parent category in the hierarchy. Leave empty to create a top-level department category. Example: None (Top Level) or Men Apparel |
level | Number (Hierarchy Level) | Optional | Hierarchy depth level (Level 1 for Root, Level 2 for Sub-category, Level 3 for Sub-department). Example: 1 (Main Department), 2 (Sub-category) |
isLeaf | System Status (Product Assignable) | Optional | Indicates whether products can be assigned directly to this category branch. Example: Yes |
status | Select (Active / Inactive) | Required | Operational status toggle. Inactive categories hide child items from POS. Example: Active |
5. Interface Preview & Category Trees
6. Workflow: Adding Tree Nodes
Open Category Tree View
Categories Menu LinkNavigate to Master Data -> Categories from the left sidebar.
Specify Hierarchy & Node Code
Add Category ModalClick "Add Category". If creating a subcategory, choose the parent node in the Parent Category selector. Enter a unique Code and Name.
Save Category
Save Category ButtonClick "Save Category" to register the new category in your store directory.
7. Workflow: Updating Category Hierarchy
Locate Category Node
Category Tree SearchFind the category in the hierarchical tree or list table using search.
Modify Details or Reparent Node
Edit Action IconClick "Edit" to modify Name or Code. If reparenting, select a new parent category.
Save Changes
Save Changes ButtonConfirm the edit to apply changes across the tree hierarchy.
8. Deactivation & Leaf Deletion Rules
Hierarchy Integrity Guardrails
isLeaf = true) with zero attached products can be deleted.Check Children & Product References
Category Detail PaneVerify that the category has no active child categories and is not linked to existing products.
Deactivate or Delete Node
Delete / Deactivate ActionIf referenced by products, set Status to Inactive. If completely empty and created by mistake, click "Delete" to remove it permanently.
9. Cross-Module Impact & POS Navigation
Categories render as primary touch tabs on POS registers, filtering visible menu products for fast checkout.
Every product must belong to an active Category. Category code forms the foundation of product catalog classification.
Financial summaries aggregate sales revenue, gross margin, and stock turnover by product category.
Taxonomy Best Practices
- Keep your category tree between 2 to 3 levels deep for optimal POS cashier screen speed and user ergonomics.
- Use standardized category code prefixes (e.g., BEV-HOT, BEV-COLD) for clear document reporting.