Amazon SP-API: "Product Not in Catalog" Offer Error — Cause & Fix

When publishing a product through the Amazon SP-API (Listings Items / Feeds), the catalog item and the offer are two separate steps. If you send the offer before Amazon has finished creating and approving the catalog record, the API rejects the offer with a "product not in catalog" or "can't find a matching ASIN" error — even though your submission data is correct.

The error messages

These are returned in the marketplace's locale, so you may see the same underlying issue in Swedish, German, or another language:

Ditt erbjudande till SKU kan inte läggas till eftersom produkten inte finns i katalogen. Kontrollera dina inlämningsdata... Om du hade tagit bort din SKU tidigare kan du försöka skicka in den ursprungliga UPC/GTIN istället för en föreslagen ASIN.

Deine Angebotszuordnung zur SKU kann nicht hinzugefügt werden, da das Produkt nicht im Katalog enthalten ist. Überprüfe deine übermittelten Daten... versuche, sie mit dem ursprünglichen UPC/GTIN statt einer vorgeschlagenen ASIN erneut einzureichen.

Deine Produktdetails sind nicht vollständig genug, um eine passende ASIN zu finden oder eine neue zu erstellen... überprüfe, ob deine Produktkennzeichnungen (UPCs 12 Ziffern, EANs 13 Ziffern, ISBNs 10 Ziffern) korrekt sind. Attributes: ["externally_assigned_product_identifier"]

Why this happens

The catalog item and the offer are decoupled on Amazon's side. When you publish, Amazon first has to create (or match) the catalog record for your identifier, then propagate and approve it across the target marketplace. This propagation is not instant — it can take several hours to 24–48 hours. If your offer submission arrives before the catalog record is live and approved, Amazon has nothing to attach the offer to, so it reports the product as "not in catalog" or claims the details aren't complete enough to resolve an ASIN. The submission data itself is usually fine; the timing is the problem.

The "not complete enough to find an ASIN" variant points at externally_assigned_product_identifier for the same reason — Amazon can't yet resolve your UPC/EAN/GTIN to a catalog record that exists on that marketplace.

How to fix it

First, confirm the identifier format is valid: UPC = 12 digits, EAN = 13 digits, ISBN = 10 digits. If the identifier is correct and you're still getting the error, this is a propagation delay, not a data error:

1. Do not keep resubmitting immediately — it won't help and can pile up feed errors.
2. Wait 24–48 hours for Amazon to finish creating and approving the catalog record on the target marketplace.
3. Resubmit the offer. Once the catalog item is live, the same payload goes through.
4. If you deleted the SKU previously, resubmit with the original UPC/GTIN rather than a suggested ASIN.
5. When listing from one marketplace to another, check that SKU creation on the target marketplace has completed before attaching offer data.

This is one of many timing and sequencing edge cases you'll hit when publishing products across Amazon and other marketplaces. Having built multi-channel integrations across 20+ sales channels — Amazon SP-API, eBay, Shopify, TikTok Shop and more — I've run into and solved most of them. If you need help with eCommerce support or marketplace API integration, check out Netalith's eCommerce support service or reach out to me directly on LinkedIn.