How to Fix Amazon Error 13013: SKU Not Found in Catalog
Explains Amazon feed error 13013, which occurs when sellers try to update a SKU that doesn't exist in the catalog. Covers causes, resolution steps, and prevention strategies.
Overview
Error 13013 is a common feed processing error that Amazon sellers encounter when attempting to update or manage a SKU that doesn't actually exist in Amazon's catalog. This error blocks updates to pricing, inventory, images, and shipping overrides until the underlying product listing issue is resolved. Understanding what triggers this error and how to fix it can save sellers significant time and frustration when managing their catalog.
Key Points / What Sellers Need to Know
- Root cause — This error fires when you try to modify a SKU that was never successfully created in Amazon's catalog, or one that has been deleted.
- Affected feed types — The error can appear in inventory feeds, pricing feeds, shipping override feeds, and XML product data feeds.
- Not always a problem — If you intentionally deleted a product and then see this error on a deletion feed, no action is needed.
- 24-hour waiting period — If you deleted a SKU and want to recreate it, you must wait at least 24 hours before resubmitting.
- Original identifiers required — When resubmitting product data, use your original UPC or GTIN rather than a suggested ASIN to avoid catalog matching issues.
Common Causes
Error 13013 typically surfaces when there is a disconnect between the product data you are submitting and what actually exists in Amazon's catalog. The most frequent scenario is attempting to update pricing, inventory levels, or images for a SKU that failed its initial creation. This can happen silently — a product data feed may appear to have processed, but individual SKUs within that feed may have been rejected due to errors. Sellers also trigger this error when submitting shipping override files that reference SKUs not yet established in the catalog, or when trying to post XML feeds for products that were never successfully added through a product data feed.
Another common trigger is attempting to modify a SKU that was recently deleted. Amazon's catalog system requires a cooling-off period before a deleted SKU can be recreated, and any feed submissions referencing that SKU during that window will return error 13013.
Analysis & Recommendations
Why This Matters
Sellers who manage inventory through feeds can encounter this error and lose time troubleshooting. Knowing the causes and fixes helps resolve catalog issues quickly and keep product data flowing.
Key Takeaways
- Error 13013 means you're trying to update a SKU that doesn't exist in Amazon's catalog or was deleted
- Always check feed processing reports to catch failed SKU creations before submitting follow-up feeds
- Wait at least 24 hours before attempting to recreate a deleted SKU
- Use original UPC/GTIN identifiers when resubmitting product data, not suggested ASINs
Recommended Actions
- →Review your feed processing reports in Seller Central after every product data submission to catch SKU creation failures early
- →Establish a feed sequencing workflow: product data feed first, then inventory/pricing/shipping feeds only after confirming successful creation
- →When recreating deleted SKUs, enforce a 24-hour waiting period before resubmission
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!