Problem:
In environments with multi-tiered product data structures (e.g., Parent > Child > SKU), it’s common for relevant data to be stored at different levels depending on the attribute’s purpose. However, Pimberly workflows currently do not support referencing or writing attribute values across product hierarchy levels.
This creates challenges when building automation or enrichment logic using Workflows or Decision Tables, as it prevents from:
- Accessing parent-level data in child workflows
- Utilising child-level data to inform decisions at the parent level
- Writing data from one level to another (e.g., copying a value from a parent to all children, or aggregating child values at the parent level)
This limitation often forces users to implement workaround solutions using channel feed loops or manual imports, which add unnecessary complexity and reduce efficiency.
This request is for Pimberly workflows to allow product data inheritance across parent/child products as well as to write data from product to its parent or children.
Suggestion:
We would like to see enhanced support in Pimberly workflows and decision tables that enables:
- Read access to attributes across tiers – for example, referencing a parent attribute within a child record’s workflow logic.
- Write access across tiers – allowing workflows to update attributes up (e.g., SKU → Parent) or down (e.g., Parent → SKU) the hierarchy.
- Conditional logic based on hierarchical relationships – such as applying updates to all children when a parent meets certain criteria, or vice versa.
Comments
Please sign in to leave a comment.
100% agree we need this.
This would be great for us, especially reducing reliance on unsupported overnight SQL processes.
This would be a game changer for us
All for this update!