Why Product Hierarchy Matters?
Retraced uses a hierarchical product structure:
Style → Variant → SKU
This structure allows you to manage shared product information efficiently while still supporting differences at lower levels.
How Attribute Inheritance Works?
When you create a Variant or SKU, it automatically inherits certain attributes from its parent. This means:
Variants inherit from Styles
SKUs inherit from Variants
Updates at the parent level cascade down — unless overridden
Inheritance ensures consistency across large product catalogs.
Product Attribute States
Every product attribute in the hierarchy can be in one of three states:
1) Linked (Default state)
This means the attribute:
Comes from the parent
Updates automatically when the parent changes
Is synchronized across levels
Example:
Style Season = SS26
→ Variant Season = SS26
→ SKU Season = SS26
If the Style changes to FW26, all linked Variants and SKUs update automatically.
This is the default behavior for most shared attributes.
2) Overridden
This means the attribute:
Has its own value at the child level
Stops syncing with the parent
Becomes independent
If you want to override a value just edit the Variant or SKU field and save the changes. You will see:
A warning before saving
A broken chain icon after saving
Once overridden, future parent changes will NOT cascade down.
Important: Once a field is overridden, it can only be linked to the parent again if you manually set the value to the same value as the parent.
3) Locked
The attribute:
Cannot be edited at that level
Must always match the parent
Locked attributes enforce structural consistency.
Inheritance Between Style → Variant
When a Variant is created, it inherits the following from its parent Style:
Inherited & Overridable at Variant level:
Description
Brands
Departments
Seasons
Collections
Claim Intentions
Main Supplier
Suppliers
Vendors
Weight
Gender
Images
Additional Attributes (for certain product types)
Bill of Materials (BOM)*
Raw Material Compositions (RMC)*
Important: Note that changing any line of the Bill of Materials (BOM) or Raw Material Compositions (RMC), or setting a new main BOM or RMC will unsync the corresponding BOM/RMC from the parent.
If the Variant overrides one of these values:
The field now becomes independent
Future changes on the Style level will no longer cascade down for that field
When making a change to an attribute look for the little warning label, which let’s you know an attribute is being overridden and will stop syncing.
Finally, after an attribute has been un-synced the icon with a broken chain will remind you which attributes have been overridden.
To continue click “Yes, Update Anyway”.
Once you click save, you will also see a pop-up window informing you that an attribute will be overridden. It will let you know which attributes are affected.
Inherited & Locked at Variant Level:
The following fields must always match the parent Style:
Style Level
Style Type
They cannot be edited at Variant level.
Not Inherited (Variant-Specific Fields):
These attributes belong only to the Variant:
Variant Codes
Color
Variant Name
Badges
QR Code
Product Certificates
Story Active
A Variant must always belong to exactly one Style and cannot be reassigned later.
Inheritance Between Variant → SKU
When a SKU is created, it inherits attributes from its parent Variant.
Inherited & Overridable at SKU Level:
Description
Brands
Departments
Seasons
Collections
Claim Intentions
Main Supplier
Suppliers
Vendors
Weight
Gender
Images
Additional Attributes (for certain product types)
Bill of Materials (BOM)*
Raw Material Compositions (RMC)*
Important: Note that changing any line of the Bill of Materials (BOM) or Raw Material Compositions (RMC), or setting a new main BOM or RMC will unsync the corresponding BOM/RMC from the parent variant.
If one of these values is overridden in SKU
The field now becomes independent
Future changes on the Style level will no longer cascade down for that field
Inherited & Locked at SKU Level:
The following must always match the parent Variant
Style Level
Style Type
Color
These fields cannot be edited at SKU level
SKU-Specific Fields (Not inherited):
SKUs can define their own:
SKU Codes
Size
If no name is set, the system auto-generates one. Following the structure “parent name + SKU ID”.
Practical Example
You create:
Style: Basic T-Shirt
Variant: Blue
SKU: Blue - Size M
If you update the Style’s season to “SS26”:
The Variant and SKU update automatically
Unless either has overridden Season
If you change the Variant’s color:
The SKU updates
Because color is locked to the Variant
When Should You Override?
Override only if:
The attribute truly differs at that level
You want independent reporting
The variation cannot be managed at parent level
If unsure, keep it linked.