You check sales every morning. You watch ACoS, conversion rate, and Buy Box percentage like a hawk. And yet a meaningful chunk of your catalog can be losing money right now, quietly, with no red flag on your main dashboard. That is the nature of an operational leak: it does not show up as a bad day. It shows up as a slow, permanent tax on revenue that nobody notices until someone finally reconciles units shipped against units sold.

Stranded inventory is the classic example, but it is far from the only one. These issues share a pattern: they are not driven by demand or competition, they are caused by something breaking quietly on Amazon's side or yours, and they persist until a human goes looking for them. Most brand owners do not go looking, because nothing prompts them to. That is the problem this post is about.

What Stranded Inventory Actually Costs You

Stranded inventory means units are sitting in an Amazon fulfillment center but are not available for sale. No listing is live to match them. This happens for mundane reasons: a listing got suppressed, a variation relationship broke, a barcode mismatch confused the catalog, or a category-specific requirement (like a compliance document) expired without you noticing.

The direct cost is obvious. Units that could be selling are not. But the compounding cost is worse. Every day those units are stranded, you are also paying long-term storage fees on inventory you cannot sell, and you are losing the sales velocity that keeps your organic rank where it is. A product that goes from steady daily sales to zero for even a week can take real ad spend to recover the rank it lost, a dynamic we cover in inventory planning so you never lose rank to a stockout. Stranded inventory is functionally a stockout you inflicted on yourself, except you are still paying to store the product that isn't selling.

The fix is a habit, not a one-time cleanup. Check the Stranded Inventory report in Seller Central weekly, not monthly. It lives under Inventory Planning, and it will show you the ASIN, the reason code, and the action needed. Most fixes take minutes once you know they exist. The expensive part is not knowing.

Suppressed Offers Nobody Told You About

A suppressed listing does not always announce itself with a banner on your dashboard. Sometimes a single variation in a parent-child relationship gets flagged for a missing attribute, and it quietly drops out of the buy box rotation while the rest of the family looks fine in your top-line numbers. If you are only glancing at aggregate catalog sales, a suppressed child ASIN can bleed for weeks before anyone isolates it.

A number that never moves is not always a number that is fine. Sometimes it is a number that stopped being measured.

This is why per-ASIN review matters more than category-level review. If you have not already built the habit of walking every active listing for suppression flags, the response plan for the day a listing gets suppressed is worth having ready before you need it, not after. The Listing Quality dashboard and the Account Health page both surface active suppressions, but they only help if someone opens them on a schedule.

Buy Box Gaps That Look Like Normal Fluctuation

Buy Box percentage moves around for legitimate reasons: price changes, competitor stock, fulfillment method shifts. That normal noise is exactly why a real problem can hide inside it. A brand owner sees Buy Box percentage dip from 98 percent to 91 percent and assumes it is a pricing blip. Sometimes it is. Sometimes it is a third-party seller who got a foothold on your listing, or a fulfillment delay that Amazon is quietly penalizing.

The fix is to treat any sustained Buy Box drop, even a small one, as a question that needs an answer, not a number that needs to be watched. Pull the Business Report by ASIN and compare Buy Box percentage against unit sessions for the same period. If sessions are flat but Buy Box percentage is down, you are losing sales you would otherwise have made, and that gap is invisible unless you go looking for it, similar in spirit to the detail-page issues covered in the listing mistakes quietly costing you the Buy Box.

Unauthorized Sellers and Counterfeit Listings

A less obvious revenue leak: someone else selling on your listing, whether through unauthorized inventory or an outright counterfeit. Every unit they move is a unit you did not sell, at a price you did not set, potentially with product quality you cannot control. Reviews from those units can also drag down your rating on a listing you thought you were fully managing.

Brand Registry gives you the tools to catch this early, but only if you are monitoring proactively rather than reacting to a customer complaint. The playbook in protecting your brand from hijackers and counterfeits covers the monitoring cadence and the documentation you need to get a bad actor removed quickly. The point for this post is simpler: unauthorized sellers are a revenue leak that hides inside your own sales data, because their units still count as "sold" in the category, just not by you.

Building the Weekly Check

None of these leaks require sophisticated tooling to catch. They require a short, repeatable checklist that someone actually runs:

If that sounds basic, it is. The leaks described here are not exotic. They are boring, procedural, and completely fixable once someone owns the checklist. If your reporting cadence already tracks the leading indicators discussed in the metrics that actually predict Amazon growth, adding these four checks is a small addition with an outsized payoff, because unlike ad optimization or creative testing, fixing an operational leak has no ramp-up time. The revenue was already there. You just have to stop losing it.

What to Do This Week

Pick one afternoon this week and run the four-report checklist above against your full catalog, not just your top sellers. Stranded inventory and Buy Box gaps tend to hide in mid-tier and slower-moving ASINs precisely because nobody is watching them closely. Write down what you find, fix what you can immediately, and put a recurring calendar reminder in place so this becomes a weekly habit rather than a one-time audit.