A supersession happens when a manufacturer replaces one part number with another. The old part is discontinued; the new part is the official replacement. On a KTM, Husqvarna, or GasGas catalog, a single physical component might have been superseded three or four times across its life — each old number pointing forward to the next.
At the counter, a good microfiche tool resolves this automatically: look up the old number, get told the current one. Online, almost nothing handles it, and that gap quietly costs dealers money every day.
What a supersession chain looks like
Supersessions form a chain. Consider a clutch cover that has been revised twice:
| Original SKU | Superseded by | Status |
|---|---|---|
| 5480xxxx00 | 5480xxxx01 | Discontinued |
| 5480xxxx01 | 5480xxxx02 | Discontinued |
| 5480xxxx02 | — | Current / orderable |
Only the last number in the chain — the terminal SKU — can actually be ordered. Every earlier number should resolve to it. A rider searching an old diagram or an old receipt will type any of these numbers, and your store has to do the right thing regardless.
The core rule
Search should match any number in the chain. Purchase should always resolve to the terminal SKU. Reviews, stock, and pricing should consolidate on that terminal SKU — not scatter across dead numbers.
How unhandled supersessions bleed sales
- Phantom out-of-stock: a customer searches the old number, lands on a discontinued product with zero inventory, and leaves — even though the replacement is in stock.
- Selling the dead SKU: if the old product page is still purchasable, you take an order you can't fulfill, then scramble to explain the swap.
- Split SEO and reviews: three product pages for one physical part dilute ranking signals and scatter reviews.
- Wrong-fit confusion: superseded parts sometimes change fitment or supersede across models, so naive redirects can send a customer to a part that no longer fits their bike.
Four ways to handle supersessions online
- Manual redirects (worst): a store admin manually 301-redirects old handles to new ones. Doesn't scale, breaks on the next catalog update, and loses the old numbers as searchable aliases.
- Alias fields: store superseded numbers as searchable aliases on the terminal product so search matches them. Better, but you still have to maintain the mapping.
- Supersession pipeline (best): ingest the OEM supersession table, resolve every chain to its terminal SKU automatically, and keep old numbers as search aliases on the live product. Updates flow through on each catalog sync.
- Fitment-aware resolution: the pipeline above, plus a fitment check so the customer is warned if a superseding part changed compatibility for their model.
How Parts Finder Software resolves them
Parts Finder Software ingests OEM supersession data as part of catalog sync. When a shopper searches or lands on a product via any historical number, the widget resolves the chain to the current terminal SKU, surfaces live price and stock for the orderable part, and keeps the old numbers as searchable aliases. The compatibility check then confirms the resolved part still fits the customer's bike.
The technical mechanics — schema, chain resolution, and DMS stock alignment — are covered in integrating KTM and Husqvarna parts databases with Shopify. For the wider strategy, see selling OEM powersports parts online.