Incorrect mapping
Two distinct SKUs with different barcodes and product data were merged under a single ASIN.
Client success story · CS22
Separating two SKUs merged under one ASIN
A catalogue error driving returns, warnings and deactivation risk
- PlatformAmazon Seller Central
- Issue typeASIN–SKU mis-mapping
- Risk levelPerformance warning, deactivation risk
- 2SKUs separated from one ASIN
- Near zeroreturn rate after correction
- Clearedaccount health warnings
Client background
A single ASIN was incorrectly linked to two SKUs, so customers received the wrong product. Return rates climbed, customer dissatisfaction grew, and both revenue and operational stability were affected.
As returns rose, Amazon issued a performance warning and the account faced potential deactivation. Multiple internal attempts had failed against catalogue-level conflicts.
Problem
Operational challenges
The objective was to find the root cause, correct the mapping, and align each SKU to the right ASIN — restoring accurate order processing and stabilising account health before the warning became a deactivation.
Persistent reversion
The mapping kept reverting despite repeated update attempts.
Rising returns and account risk
Wrong fulfilment drove returns up and triggered account warnings.
Standard fixes failed
File uploads and manual updates could not override the backend conflict.
Relisting ineffective
SKUs remapped incorrectly even after the listings were recreated.
Support delays
Repeated case rejections slowed resolution.
Inventory constraint
Reserved inventory blocked direct correction, requiring backend intervention.
Solution
Custom solution executed
-
01
Issue diagnosis
SKU–ASIN relationships were analysed to identify the root cause and the conflicts holding it in place.
-
02
Multiple fix attempts
Inventory uploads, backend edits and listing updates were each tested to establish what the constraint actually was.
-
03
Case escalation
Support cases were followed up persistently and escalated rather than refiled.
-
04
Leadership intervention
Escalation to Amazon leadership confirmed the reserved inventory issue that was blocking every direct correction.
-
05
Mapping correction
Internal removal of the incorrect catalogue constraints was enabled.
-
06
Data cleanup
SKU data was reset to clear the conflicting values.
-
07
Controlled re-listing
Listings were recreated with the correct ASIN mapping, coordinated with support so the fix held.
Impact
Business value delivered
- Incorrectly merged SKUs successfully separated
- Each SKU correctly mapped to its own ASIN
- Accurate product listings and order fulfilment restored
- Return rate reduced from critical levels to near zero
- Customer experience and trust recovered
- Account health risks and warnings eliminated
- Improved sales performance and profitability
What it changed for the client
- A catalogue stabilised against recurrence, not just corrected once
- Deactivation risk removed from the account
- Fulfilment accuracy restored at the source rather than managed downstream
In short
Some catalogue problems cannot be fixed from the surface. When uploads, edits and relisting all revert, the constraint is upstream — and the only route is persistent, evidenced escalation until someone with backend access can remove it.
Services this story used
Related case studies
Have a version of this problem?
Describe it in a sentence. We will tell you what we would do about it, and whether it is something we should be doing at all.