Find and fix phantom inventory: a 30-minute weekly workflow

Phantom inventory manifests in a few patterns: an ASIN shows available quantity but no offer is active; sales occur but available quantity doesn't decrease; units are reserved for orders that never ship; or units are stuck in inbound/adjustment limbo. Any mismatch between the inventory ledger you trust (ERP/WMS) and Amazon's available quantity costs either lost sales or extra handling.

Treat phantom inventory as a symptom, not a root cause. The symptom is the mismatch; causes include inbound receiving errors, labeling mistakes, listing-level issues, FBA processing delays, returns not processed correctly, or catalog data problems that split inventory across variations or ASINs.

Run this checklist on a fixed day each week. Break it into three 10-minute passes: identify, triage, and act. Use your seller reports or dashboard filters to assemble the views below before you start so the 30 minutes are focused.

Filter ASINs where recent sales exist but available quantity is zero or where available quantity is significantly different from your warehouse ledger. Prioritize by velocity and margin: a mismatch on a top-selling SKU is higher impact than on a slow mover.

Run these quick checks and capture 10–25 ASINs: those with recent orders but no available quantity, ASINs showing available stock but with suppressed or blocked listings, and SKUs with inventory reserved for orders older than the threshold you set. Also include ASINs with inbound shipments that show 'received' but whose available quantity hasn't moved.

For each ASIN in your short list, pick one of three actions: immediate fix, investigation ticket, or monitor. Use this decision matrix: if your warehouse has physical stock and Amazon shows zero, open an investigation with Amazon and prepare proof of shipment; if Amazon shows stock but the listing is suppressed, fix the listing first; if units are reserved or in 'unfulfillable' states, move to remove or reconcile depending on condition.

Record the chosen action, the owner, and a target resolution date. Keep the list tight—focus on ASINs where fixing will return sales in the short term.

Execute the quick wins first: unsuppress listings, correct child/parent relationships, reconcile obvious inbound label issues with your receiving team. For lost or miscounted units, assemble documentation and open a case with Amazon; include shipment IDs, tracking, carrier proof, and photos. For units that are confirmed unfulfillable, decide whether to remove, liquidate, or have them disposed.

If an issue needs more investigation (complex adjustments, multiple shipments), assign an owner and calendar a follow-up. The goal in this last pass is to convert identification into concrete actions so the same ASINs don't show up in next week's list.

Set thresholds so the weekly list stays manageable: velocity cutoff, age of the discrepancy, and expected inbound processing time. Adjust thresholds as your catalog changes. Keep a separate watchlist for long-tail ASINs that repeatedly generate tickets—repeat offenders indicate a process weakness rather than a one-off problem.

Instrument three automated alerts if your tools allow it: a) sales without inventory movement, b) inbound marked received but no change to available, and c) listing suppressed while available > 0. These reduce the manual scan time and surface anomalies between weekly checks.

Most phantom inventory is preventable. Standardize your inbound labeling and receiving checks, require scanned counts at pick-and-pack stages, and ensure your PO and shipment workflows reconcile before closing a shipment. Keep tight catalog hygiene to avoid split inventory across multiple ASINs or incorrect variation structures.

If you use a third-party warehouse, add an outbound checklist: verify FBA labels match ASINs, confirm carrier pickup manifests, and retain photos of pallet labels. When you receive vendor returns back into your system, reconcile those to Amazon return reports to ensure units are routed correctly.

If the same ASINs produce repeated investigations, or you see an increasing trend of inventory adjustments from Amazon, schedule a full audit: reconcile SKU-level ledgers to FBA shipments for the last several months, review inbound shipment exceptions, and audit your labeling and packing processes. Persistent patterns suggest systemic issues—warehouse process gaps, misconfigured integrations, or catalog errors—that need longer remediation projects.

MySellerHQ is a read-only dashboard that surfaces the signals this workflow relies on: inventory available versus shipped counts, inbound receipt anomalies, reserved/unfulfillable flags, and listing suppression indicators. It aggregates the data so you can run the 30-minute pass without hunting through multiple screens. Decisions and actions—opening cases, creating removals, or changing processes—remain with your team; MySellerHQ simply makes the inconsistencies visible sooner so you can act.