Hierarchy of Product Edits
It is important to understand how the hierarchy of edits works in Xada, as it determines which data takes precedence when multiple updates apply to the same product.
Xada manages product data across three distinct layers, in the following order of priority:
- Manual edits
- Rules
- Original data
Manual edits
Manual edits represent any data that has been updated directly via the Xada dashboard or through CSV imports. This layer has the highest priority and will always override changes made by rules or supplier data.
When a product is sourced from a supplier feed, any changes you make through the interface or CSV are stored as manual edits, allowing the original supplier data to remain intact.
Rules
Rules are applied only to the original data layer. This means:
- Rules will never override manual edits
- Rules are evaluated after original data is received but before manual edits are considered
Rules are commonly used to automate changes while still allowing manual overrides where needed.
Original data
Original data is the base data used when the product was first created. This can originate from:
- A supplier data feed
- A product created directly in Xada
This layer serves as the foundation on which rules and manual edits operate.
How precedence works in practice
- For supplier-sourced products:
- Manual changes update the manual edits layer
- Original supplier data is preserved
- Rules continue to apply to the original data only
- For products created within Xada:
- There is no separate manual edits layer
- Any changes made through the interface update the original data directly
- Rules apply to that original data
As a result, products created within Xada do not accumulate manual overrides in the same way as supplier-sourced products.