Someone completing a SKU should not be presented with fields that only make sense at range level. This demonstration shows the taxonomy controlling which attributes appear where, using an automotive example: year range surfaced at SKU level, vehicle make and model at product level. Each record shows what is relevant to it, which is what keeps data entry quick and accurate.
With Pimberly’s taxonomy, you can:
- Maintain the taxonomy yourself as a business user, with no development support needed
- Select a node to define which attributes surface on it and at which product type
- Use the parent-child relationship in the product types to tier attributes — year range at SKU level, vehicle make and model at product level, for example
- Show each record only the attributes relevant to it, so people working on a SKU aren’t presented with range-level fields they can’t meaningfully complete
- Combine this with deep hierarchies, inheritance, controlled overrides and multiple taxonomies, all configurable by the business
See how it works in the video below:
