How are parent and child ASIN relationships handled in reporting?
Learn how MerchantSpring handles parent and child ASIN relationships in product reporting.
Amazon often organizes products into variation families, which consist of a parent ASIN and multiple child ASINs. These relationships allow customers to choose between product variations such as size, colour, or style.
MerchantSpring retrieves this catalog structure from Amazon and reflects it in product reporting.
Parent ASIN
The parent ASIN represents the main product listing that groups multiple variations together.
Parent ASINs typically do not have direct sales activity.
Instead, they act as a container for the variation listings.
Child ASINs
Child ASINs represent individual product variations within the parent listing.
Examples include:
- Different sizes
- Different colours
- Different packaging options
Sales activity typically occurs at the child ASIN level.
How MerchantSpring Reports Variation Data
MerchantSpring retrieves product performance data from Amazon at the level provided by the API.
In most cases:
- Sales occur at the child ASIN or SKU level
- Parent ASINs act as grouping identifiers
Some reports may allow aggregation across variations for a consolidated product view.
Notes:
- Parent ASINs usually do not generate direct revenue.
- Most performance metrics are tied to child ASINs or SKUs.
- Aggregated reporting across variations may depend on report configuration.