Whether product data stays accurate comes down to how individual fields are set up. This demonstration walks through one attribute: data type and input type, values drawn from a filtered data set so the list offered is already correct, localisation, scoping and faceting. Source and master settings then decide who or what may set a value and who may overwrite it, so a field can be reserved for a particular feed, or protected so an automation cannot overwrite what a person has confirmed.
With Pimberly’s attributes, you can:
- Set a name, label, description and data type for every attribute, with the input type configured separately
- Draw values from a filtered data set, so the list offered is already restricted to what’s valid — shippable countries for a given product, for example
- Control assignment and validation: a default value, minimum and maximum sizes, and whether the field is read-only
- Localise and scope an attribute, holding a different value per language or per context
- Facet an attribute to surface it as a filter in the product grid, with a sequence number controlling where it appears
- Use source and master settings to decide who or what can set or overwrite a value — reserving a field for a particular feed, or protecting it from automation
See how it works in the video below:
