Product Linking: Automatically Link Prices to One Another
On this page
Do you lose your price history every time the EAN changes?
Let's plan an exchangeDiscover our product matching solutionProduct chaining involves linking successive SKUs of the same product over time, despite changes in packaging, EAN codes, names, or internal SKUs. It reconstructs the product’s complete history to analyze its prices, sales, and performance over time.
The Essentials
- Product chaining links successive versions of the same product over time, not different products.
- Failing to link an EAN change breaks the history: elasticity is then calculated based on a truncated series.
- It determines any decision based on a trend: without a continuous history, forecasts and elasticity lose their foundation.
In 6 Questions
Link an old and a new part number for the same product.
Pricing teams, product data teams, and category managers.
With every reformulation, packaging change, or ERP migration.
Especially in the fashion, high-tech, cosmetics, food, and personal care industries.
Maintain a continuous history of trends and elasticities.
Cross-reference attributes, dates of birth and death, volumes, and prices to identify estates.
Why Chain-Linked Prices Are Essential for Price Analysis
Because without it, every time the reference number changes, the product history is erased.
- Analyze long-term trends, even if the benchmark has changed in the meantime.
- Calculate reliable elasticities, which require a continuous history.
- Oversee product launches and redesigns while monitoring the shift in sales toward the new version.
Real-world example: two EANs, a single history
A reformulated laundry detergent gets a new EAN; the product linking system causes it to inherit the entire history of the old SKU.
Two EAN codes, one price history
Laundry Detergent · Reference Series, Before/After Reformulation
Discontinued item · includes price and sales history
New reference · chained to inherit the entire history
“X Laundry Detergent 2L” (EAN 123) is being replaced by “X Eco Laundry Detergent 2L” (EAN 456). The system identifies the succession (same brand, same size, launched at the same time the old product was discontinued) and links the data: the retailer compares performance before and after and adjusts its price accordingly.
How does product chaining work?
Algorithms cross-reference attributes, launch dates, volumes, and prices to identify logical sequences.
It is particularly critical when product lines are frequently updated (fashion, high-tech, cosmetics), when manufacturers change their packaging (food, personal care), or when a retailer migrates its product database (ERP, merger). This should be distinguished from product matching, which links products across catalogs at a given point in time: chaining creates a lasting link over time. Both are at the heart of our product matching, cloning, and chaining solution, which also ensures the reliability of our competitor price reports. See also:competitive monitoring and product matching.
3 Mistakes to Avoid in Product Chaining
Linking different products, ignoring overlaps, or failing to document anything.
- Grouping different products: “X Laundry Detergent 2L” and “X Sensitive Laundry Detergent 2L” are not the same product, despite their similar names.
- Ignore overlaps: the old and new products sometimes coexist for a few weeks.
- Do not document the chains of references: keep a record so you can audit and correct them.
Frequently Asked Questions
Short answers to the most frequently asked questions about product chaining.
What does product chaining do?
Product traceability involves linking successive product references over time—despite changes in packaging, EAN codes, trade names, or internal references—to reconstruct the product’s complete history.
What is the difference between matching and product chaining?
Matching identifies, at a given moment, identical or equivalent products across multiple catalogs—for example, your product SKU and that of a competitor. Chaining works over time: it creates a lasting link between successive versions of the same product, even when it is replaced, renamed, or repackaged. The two complement each other. Matching is used for price comparisons, while chaining preserves the historical data needed for forecasting and measuring price elasticity.
How does a product chaining engine work?
It compares the old and new SKUs based on a set of criteria: EAN, brand, product name, characteristics, packaging, weight, images, launch dates, and sales volumes. An SKU that disappears at the exact moment another, very similar one appears is a strong candidate for succession. Advanced solutions use AI to identify these successions even when the descriptions differ significantly. Uncertain cases should undergo human validation before being linked.
What are the benefits for pricing teams?
Chaining automates a time-consuming task—often performed manually in spreadsheets—that involves matching old and new SKUs. It reduces matching errors and improves the quality of analyses, since forecasts and elasticity measures are based on a complete historical record rather than a truncated one. Pricing teams then spend less time preparing data and more time making pricing decisions.
What happens to the sales history when a product code is changed?
Without chaining, it is lost: the new SKU starts with no history, and both forecasting and elasticity models treat it as a new item. Chaining allows you to link the history of the old SKU to the new one, enabling you to continue forecasting and measuring from day one.
Does the product chaining apply to changes in packaging?
Yes, and that is its most common use case. A code change related to a new recipe, new packaging, or a change in supplier creates a separate reference in the system, even though it is the same product from the customer’s perspective. Chaining restores this continuity that the repository does not recognize.
Should you re-label a product whose volume has changed?
Yes, but by standardizing. Aggregating data without accounting for changes in weight distorts the forecast just as much as not aggregating at all, since the volumes are no longer comparable. Continuity must be based on a stable unit—price per kilogram or per liter—not on the number of units sold.
Key Takeaways
- Product chaining links successive versions of the same product.
- It preservesthe historical data essential for identifying trends and elasticities.
- It must be rigorous and well-documented to avoid false positives.
Would you like to track the price of a product even if its product code changes?
Booper tracks a product's price history across its successive versions.
Let's talk about your product history →Discover our product matching solutionThese articles can interest you
Product matching is the foundation of competitive monitoring: it prevents companies from lowering prices based on a false price difference between two non-equivalent products. Cases of doubt are referred to business-unit review.
According to Diamart Group (2026), about 50% of French retailers still perform their price matching manually, while 94% collect competitive data.
Strategic pricing defines, for a period of six to twelve months, the role of each category, the target price level, and the parameters within which daily prices may fluctuate. It does not set prices; rather, it defines the range within which each price is allowed to fluctuate.
A pricing strategy rarely falls apart all at once; rather, it erodes under the weight of accumulated tactical decisions and an ever-growing list of image products. Drawing the line between strategic, tactical, and operational considerations is more important than the sophistication of the calculations.
Automated pricing delegates the preparation, verification, and implementation of prices to a system, within limits defined by the team. The first thing to automate is not price changes but the detection of anomalies, which protects margins and builds trust.
Once automation is in place, the bottleneck becomes the validation process: everything hinges on sorting between prices that are processed automatically and exceptions. Projects rarely fail because of the algorithm; they almost always fail because of the data, the constraints, and the team’s habits.