Please note this is a channel-specific article only applicable to Amazon.


There are situations where a single SKU sold on Amazon can produce two or more identical FBM listings on the offer page. One of those FBM offers will be fully controlled via the Inventory screen on Amazon Seller Central and will deduct stock levels properly. Whereas the other one will just stay there with unchanged stock levels - allowing buyers to keep buying this product despite the SKU being out of stock in the Seller Central.


These listings are called "ghost" listings or "phantom" listings on Amazon. As far as we know, the solution to this problem is deleting the SKU from the Amazon inventory and then adding it back.


For more information on this and maybe new and better solutions to this problem, please refer to Amazon Seller Central forums and a general search on Google for the following keywords: Amazon ghost listings.


How to get a list of potential ghost listings:


In Dashboards > Query Data > Query type: Amazon - Potential Ghost Listings report will show you all the SKUs that may potentially have a ghost listing created. Please see here for full details on the selection criteria and reported values. You can then pass the list of Amazon SKUs to Amazon directly for them to assist you with removing them. 


How to check whether a specific order is from a ghost listing in Linnworks:


When you encounter an overselling case with an item you have listed as an FBA listing, then via Linnworks the simplest way to check whether this is due to a ghost listing is as follows:


  1. a) Open Orders screen: Right-click on the order -> View -> View Order XML
    b) Open Orders BETA: Right-click on the order -> View order -> Properties -> Order XML

  2. In the XML check OrderWithItems -> Order -> FulfilmentChannel - in a ghost listing case this would say MFN even though the SKU is from an FBA listing.



  3. Now check Items -> OrderItem -> SellerSKU. If you already know that this is the SKU on your FBA listing, then it is clear that you have a ghost listing case. If you are not sure, proceed to step 4.



  4. Go to Settings -> Channel Integrations -> Mapping button on the channel line the order came from

  5. Search for the SKU from the XML. If there is a tick on the FBA column, then you are dealing with a ghost listing.


Alternatively, you can check whether the Amazon SKU is present in the specified report from Dashboards > Query Data > Query type: Amazon - Potential Ghost Listings. 


Why ghost listings can happen when using Linnworks:


By default whenever you list or link an FBA listing in Linnworks, then the system automatically enables the Ignore sync setting. This is done to prevent Linnworks from sending any stock level updates to this listing as all stock levels for FBA listings should be handled by Amazon themselves. If the Ignore Sync tick is removed, then Linnworks sends stock level updates and an extra listing - as described at the beginning of this article - is created.


Mostly this happens in two cases:

  1. The Ignore Sync is unticked by a user.
  2. The Ignore Sync is unticked when you are using Stock Item Linking import without specifying a value in the Ignore Sync column.


Linnworks automatically adds the Ignore Sync tick back to the listing if it still remains an FBA during the next Listing Download sync, but this only runs once every 12 hours. If there is a stock level update to the SKU prior to the sync finishing, updates are sent to the channel for the FBA listing as well.


To prevent the issue:

  1. Make sure your users know not to untick Ignore sync for FBA listings.
  2. When using Stock Item Linking import, be sure to add the value TRUE to the Ignore Sync column for any FBA SKUs you are linking.
    If you are not sure which SKUs are FBA, use the Channel Linking report in Linnworks to receive a CSV where any FBA listings are marked with Source Amazon FBA.