Ghost SKUs
A ghost SKU is a product record that still exists in a system after the product itself is gone, discontinued or was never real.
What is Ghost SKUs?
A ghost SKU is a product record that still lives in a database, feed or webshop while the product behind it no longer exists, was discontinued, or was only ever a placeholder or test entry. It is also called a phantom, orphaned or zombie SKU. Ghost SKUs appear when one system deletes or retires a product and the others never hear about it, or when imports create duplicates and test items that nobody removes. They differ from out of stock SKUs: an out of stock product is real and will come back, a ghost SKU has nothing behind it. They clutter search and filters, send broken items to channels and distort stock and sales reports. A clear end-of-life process is the best prevention, as the catalog lifecycle guide shows.
Why Ghost SKUs matters for e-commerce
Ghost SKUs cost money in quiet ways. Shoppers find products they cannot buy, marketplaces receive listings that fail or get cancelled, and ad budget goes to items with no stock behind them. Reports also suffer: a catalog that looks twice as big as it is hides which products actually sell. The problem grows with every new channel and integration. Each extra system is another place where a retired product can linger. Regular cleanups and one central product record that decides what is active keep the catalog honest across every channel.
Examples of Ghost SKUs
- 1Record: Winter jacket 2022, size XL, Status in ERP: Deleted, Status in webshop: Still live
- 2Record: TEST-PRODUCT-01, Origin: Created during a platform migration, never removed
- 3Record: Same blender imported twice under two SKUs, Effect: One copy has no stock and no images
- 4Record: Discontinued phone case, Status in feed: Still sent to Google Shopping
Exorcise Your E-Commerce: The Ghost SKU Survival Guide
How WISEPIM Helps
- Keep one central product record and set a status, so retired products stop going to channels.
- Use Quality Guard rules to flag products without images, price or stock data, which often points to a ghost SKU.
- Clean up old or duplicate records in bulk with bulk editing instead of one by one.
- Undo a cleanup that went too far with Rollback Import or Operation history undo on paid plans.
Common mistakes with Ghost SKUs
- Deleting a product in one system without removing it from feeds and marketplaces.
- Leaving test and placeholder products in the live catalog after a migration.
- Hiding ghost SKUs instead of retiring them, so they keep showing up in exports and reports.
- Reusing an old SKU code for a new product, which mixes history from two items.
Tips for Ghost SKUs
- Compare SKU lists between your ERP, PIM and each channel every quarter.
- Give products an explicit status (active, discontinued, archived) instead of deleting them in one place.
- Never reuse SKU codes; generate new ones with a fixed pattern, for example with the SKU generator.
- Remove test products right after a migration or integration project.
Trends around Ghost SKUs
- More channels per store means more places where retired products can linger.
- Automated catalog audits flag records with no stock, sales or images over a set period.
- Clear end-of-life rules are becoming part of product data governance.
Tools for Ghost SKUs
Related Terms
Also Known As
Frequently Asked Questions
Still have questions?
Can't find the answer you're looking for? Please get in touch with our team.
Contact Support