# When to Kill a Product: The Discontinue Decision Author: Himanshu Gaba Author URL: https://sellerview.ai/blog/author/himanshu-gaba Published: 2026-07-24 Category: Amazon Data & Analytics Category URL: https://sellerview.ai/blog/category/amazon-data-and-analytics Meta Title: When to Discontinue an Amazon Product (Not Just Margin) Meta Description: When to kill a product: the discontinue decision most sellers avoid. Why it is forward-looking not a margin line, and how to call it without emotion. Tags: Amazon Advertising, Amazon Product Research, Amazon Data & Analytics, Amazon Product Validation Tag URLs: Amazon Advertising (https://sellerview.ai/blog/tag/amazon-advertising), Amazon Product Research (https://sellerview.ai/blog/tag/amazon-product-research), Amazon Data & Analytics (https://sellerview.ai/blog/tag/amazon-data-and-analytics), Amazon Product Validation (https://sellerview.ai/blog/tag/amazon-product-validation) URL: https://sellerview.ai/blog/when-to-kill-a-product-the-discontinue-decision ![Lifestyle illustration of an Amazon seller reviewing product profitability on a laptop dashboard with declining sales, negative profit, and inventory costs, representing when to discontinue an unprofitable SKU to improve Amazon FBA margins and business performance.](https://prod.superblogcdn.com/site_cuid_cmlqlveae00u901w0q414cvzy/images/chatgpt-image-jul-5-2026-102350-am-1783227239315-compressed.png) You have a SKU you launched two years ago. It sells a few units a month, never lost a dramatic amount, so it is still there. You have been meaning to look at it. Meanwhile it is freezing four thousand dollars of capital your winner could use, aging toward a [storage surcharge](https://sellerview.ai/blog/amazon-storage-fees-monthly-vs-long-term), and dragging your account average down. Every month you do not decide, it costs you more. You are not keeping it because the math told you to. You are keeping it because killing it feels like admitting you were wrong. When to kill a product: the discontinue decision most [sellers](https://sellerview.ai/blog/amazon-seller-software-see-your-real-profit) avoid is not really a math problem, even though it looks like one. Sellers know how to calculate a margin. What they avoid is the decision itself, because it feels like failure, because the loss is a slow invisible bleed while the exit is a visible one-time hit, and because without a clear per-SKU number the whole thing stays a gut call, and gut calls default to doing nothing. The fix is to make the decision a number instead of a feeling, which is exactly what Sellerview.ai does. Here is the framework for calling it cleanly. * * * ### Key Takeaways - The kill decision is forward-looking, not a margin threshold. What you already spent on inventory is sunk and irrelevant. The only question is whether keeping the SKU loses more than exiting it. - "Negative margin equals cut, marginal equals fix" is too crude. A fixable negative SKU is worth saving, and a break-even SKU can be worth killing if its capital earns more elsewhere. - [Opportunity cost](https://sellerview.ai/blog/amazon-calculator-sku-scale-investment) is the hidden killer. Capital frozen in a thin SKU is capital your winners cannot use, so even a break-even product can be a loss in disguise. - Sellers avoid the decision because they cannot see the number, so it stays emotional. Make per-SKU profit visible and the call stops being scary. - Sellerview.ai shows true contribution, capital tied up, and forward trajectory per SKU, turning the discontinue decision from a gut call into a clean one. * * * ## Why Sellers Avoid the Kill Decision ![Minimal lifestyle illustration of an Amazon FBA seller analyzing an unprofitable product on a laptop, representing why sellers delay discontinuing poor-performing SKUs due to sunk costs, emotional attachment, and profit decision bias.](https://prod.superblogcdn.com/site_cuid_cmlqlveae00u901w0q414cvzy/images/chatgpt-image-jul-5-2026-103050-am-1783227657661-compressed.png) Killing a product should be routine portfolio management. It rarely feels routine, and the reasons are psychological before they are financial. First, it feels like admitting failure. You researched the product, sourced it, launched it, and defended it. Discontinuing it reads as a verdict on your own judgment, so you delay. Second, the loss is invisible. A dying SKU does not crash, it seeps, costing you a little every month in storage, ad waste, and frozen capital, and a slow bleed never triggers the alarm that a sudden loss would. Third, and most important, you cannot see the number. Without true per-SKU profit in front of you, the decision is a gut call, and gut calls under uncertainty default to inaction. Keeping the SKU feels safe because you never priced what keeping it costs. Calling out the phrase that keeps zombies alive: "let me keep an eye on it." That is not a decision, it is a deferral, and deferral has a price that compounds every month. The reason sellers avoid the kill decision is not that they are sentimental. It is that they are flying blind, and a blind decision always feels safer as a no. Sellerview.ai removes the blindness by putting the real forward cost of every SKU on the screen, so the decision has a number attached instead of a feeling. * * * ## When Should You Discontinue an Amazon Product? Here is where the standard advice fails you. Every guide reduces the kill decision to a margin threshold: negative means cut, marginal means fix, healthy means scale. That is a reflex, not a decision, and it gets the call wrong in both directions. It tells you to kill a SKU that is only negative because of a fixable listing or a bad price. And it tells you to keep a break-even SKU that is quietly strangling your growth by hoarding capital. The real kill decision is forward-looking and financial. It has nothing to do with what the SKU did last quarter or what you paid for the inventory. It has everything to do with what happens next: does keeping this product lose you more money, in cash and in opportunity, than exiting it would. That is a different question than "is its margin positive," and it produces different answers. Answering it well takes four inputs, not one threshold: the forward loss of keeping the SKU, the cost and odds of fixing it, the opportunity cost of the capital it freezes, and the cost of the cheapest exit. The next sections build each one, because the difference between sellers who prune cleanly and sellers who drown in zombie SKUs is whether they run this decision on numbers or on nerves. Sellerview.ai supplies the numbers. * * * ## The Sunk Cost Trap The single biggest reason sellers keep losing products is the money they already spent, and that money is exactly the number they should ignore. Say you spent $8,000 on 1,000 units. You sold 600, and 400 are left. On those remaining units, once you count the storage and the ad spend it takes to move a slow SKU, you lose about $2 each going forward. Your instinct screams that you cannot "throw away" $8,000 of inventory. But the $8,000 is gone either way. It is sunk. It is not part of the decision. The only live question is what the 400 remaining units do to you from here. The forward math Keep and sell through Kill now Loss on remaining 400 units 400 x −$2 = −$800 already sunk, stops here Removal fee (about $0.97/unit) $0 −$388 Months of storage and frozen capital continues ends today Forward cost −$800 plus the drag −$388 Killing now costs you about $388 and stops the bleed. Keeping the SKU costs you $800 in forward losses plus months of storage and locked capital. The math is not close. Yet sellers anchor on the $8,000, feel the exit as the "real" loss, and keep the slow bleed running because it hurts less to watch. The number you paid is history. The number that matters is forward cost versus exit cost, and Sellerview.ai shows you both per SKU so the sunk cost stops driving the decision. * * * ## The Kill Decision Tree ![Lifestyle-style illustration of an Amazon FBA seller evaluating a product decision tree on a laptop, showing a simple framework to determine whether to optimize, keep, or discontinue an unprofitable SKU based on contribution margin, growth potential, and long-term profitability.](https://prod.superblogcdn.com/site_cuid_cmlqlveae00u901w0q414cvzy/images/chatgpt-image-jul-5-2026-104314-am-1783228400932-compressed.png) Here is the framework. Run every questionable SKU through these four questions in order, and the answer resolves itself. **1\. Is it losing money forward, ignoring what you paid?** Count the real forward contribution: sale price minus [COGS](https://sellerview.ai/blog/how-to-track-cogs-history-amazon-profitability), fees, storage, returns, and the ad spend it actually takes to move it, per Amazon's [published fee schedule](https://sellerview.ai/blog/amazon-fba-fees-explained). If that number is negative at every realistic price, the SKU is a candidate. If it is positive, go to question three. **2\. Can it be fixed cheaply, with a real chance of working?** A SKU negative because of a weak listing, wrong price, or high returns might be fixable. But fixing has a cost and a probability. If a listing rebuild or a price test has a genuine shot and costs little, fix it, with a deadline. If the SKU is structurally negative, meaning fees and COGS exceed its ceiling price no matter what, no fix saves it. Kill it. **3\. Is its capital worth more somewhere else?** Even a positive SKU can fail this test. If the cash frozen in its inventory would earn more behind a stronger product, holding it is an opportunity loss. A break-even SKU that ties up capital your winners are starving for is a kill, not a keep. **4\. What is the cheapest exit, and when?** Killing has a cost: a [removal order](https://sellerview.ai/blog/amazon-reimbursement-recovery), liquidation at a recovery of pennies on the dollar, or a controlled sell-through. Pick the cheapest path and time it before the next storage or aging charge lands, so the exit itself does not become another slow leak. Four questions, one clean answer. The tree works because it replaces a single emotional threshold with a sequence of financial ones, and Sellerview.ai feeds every input, so you are answering with your real numbers instead of a guess. * * * ## The Zombie SKU That Isn't Even Negative The hardest kills are the SKUs that are not obviously losing money. They post a thin positive margin, so they never trip the "negative equals cut" reflex, and they live forever. These are the real zombies, and they are more expensive than the obvious losers. A SKU running a 4% [contribution margin](https://sellerview.ai/amazon-fba-profit-calculator) looks alive. But it is consuming shelf space in your catalog, diluting your ad efficiency, adding to your management overhead, and, above all, freezing capital. That capital has an opportunity cost. If the same dollars behind a break-even zombie could earn a healthy margin behind one of your winners, the zombie is not "a small earner," it is a drag wearing the costume of a contributor. Portfolio compression, cutting the weak tail and concentrating capital behind fewer strong bets, usually beats broad, thin coverage. This is the kill most sellers never make, because nothing screams. The SKU is technically profitable, so it hides behind its own positive sign while quietly costing you the growth that capital could have funded elsewhere. Seeing it requires ranking your catalog by contribution and by capital efficiency, not just by whether each SKU clears zero, and that ranking is exactly what Sellerview.ai produces, so the profitable-looking zombies stop hiding in the middle of your catalog. * * * ## How to Make the Call Without Emotion Concrete sequence. 1. **Get true forward contribution per SKU.** Not last quarter, not the account average. What each product earns or loses going forward after every cost. This is the input every other step depends on. 2. **Run the Kill Decision Tree.** Forward loss, fixability, capital opportunity cost, exit cost. Let the sequence, not your attachment, produce the verdict. 3. **Ignore what you paid.** Sunk cost is history. Decide on forward cost versus exit cost only. 4. **Deadline your fixes.** If you choose to fix a SKU, set a date and a target. If it has not turned by then, the fix failed and the SKU is a kill. No indefinite "keep an eye on it." 5. **Exit cheaply and on time.** Choose the lowest-cost exit and execute it before the next storage or aging charge, so killing does not create its own leak. The through-line: the discontinue decision is not the emotional gamble it feels like. It feels that way because you are making it blind, and a blind decision always defaults to keeping the zombie alive. Strip out the sunk cost, count the forward loss, weigh the fix against the kill, and price the capital the SKU is freezing, and the answer stops being a feeling and becomes a number you can act on without flinching. Sellerview.ai puts that number in front of you for every SKU, so the products worth killing get killed, the ones worth fixing get a deadline, and your capital flows to the winners that actually deserve it. * * * ## FAQ **When should I discontinue an Amazon product?** When keeping it loses more than exiting it, going forward. Count real forward contribution after all costs. If a SKU is structurally negative at every realistic price and cannot be cheaply fixed, kill it. Even a break-even SKU is a candidate if its frozen capital would earn more behind a stronger product. **Should I keep a product I already spent a lot to source?** The money you spent is sunk and irrelevant to the decision. Keeping a losing SKU because you paid for the inventory just adds forward losses to a cost you already ate. Compare the forward bleed of keeping it against the one-time cost of exiting. Usually the exit is cheaper. **Is a negative margin always a reason to kill?** No. A SKU negative because of a fixable listing, a wrong price, or high returns may be worth saving, with a deadline. Only structurally negative SKUs, where fees and COGS exceed the ceiling price no matter what, are automatic kills. Match the action to the cause, not to the sign. **Why should I kill a product that is still slightly profitable?** Because of opportunity cost. Capital frozen in a thin 4% SKU is capital your winners cannot use. If those dollars would earn a healthy margin behind a stronger product, the break-even SKU is a drag, not a contributor. Concentrating capital behind fewer strong bets usually beats broad, thin coverage. **How do I exit a product cheaply?** Choose the lowest-cost path: a removal order to pull units out, liquidation to recover some value, or a controlled sell-through with a modest discount. Time it before the next monthly storage or aging surcharge lands, so the exit does not add another charge to the loss you are trying to stop. **How does Sellerview.ai help me decide what to cut?** Sellerview.ai shows true forward contribution, capital tied up, and margin trajectory per SKU, so you can run the kill decision on real numbers instead of gut feel. It surfaces the structurally negative SKUs and the break-even zombies alike, turning the discontinue decision from an emotional gamble into a clean financial call. * * * ## Turn the Kill Decision Into a Number The discontinue decision only feels like a gamble because you are making it blind. Sellerview.ai shows true forward profit per SKU, the capital each one freezes, and where that money would earn more, so you kill the products worth killing, fix the ones worth fixing, and stop letting zombie SKUs bleed you a little every month. Run your catalog through the free profit calculator and start a free trial at [sellerview.ai](https://sellerview.ai/), and make the call on math instead of nerves. * * * ## FAQs Q: When should I discontinue an Amazon product? A: When keeping it loses more than exiting it, going forward. Count real forward contribution after all costs. If a SKU is structurally negative at every realistic price and cannot be cheaply fixed, kill it. Even a break-even SKU is a candidate if its frozen capital would earn more behind a stronger product. Q: Should I keep a product I already spent a lot to source? A: The money you spent is sunk and irrelevant to the decision. Keeping a losing SKU because you paid for the inventory just adds forward losses to a cost you already ate. Compare the forward bleed of keeping it against the one-time cost of exiting. Usually the exit is cheaper. Q: Is a negative margin always a reason to kill? A: No. A SKU negative because of a fixable listing, a wrong price, or high returns may be worth saving, with a deadline. Only structurally negative SKUs, where fees and COGS exceed the ceiling price no matter what, are automatic kills. Match the action to the cause, not to the sign. Q: How do I exit a product cheaply? A: Choose the lowest-cost path: a removal order to pull units out, liquidation to recover some value, or a controlled sell-through with a modest discount. Time it before the next monthly storage or aging surcharge lands, so the exit does not add another charge to the loss you are trying to stop. Q: How does Sellerview.ai help me decide what to cut? A: Sellerview.ai shows true forward contribution, capital tied up, and margin trajectory per SKU, so you can run the kill decision on real numbers instead of gut feel. It surfaces the structurally negative SKUs and the break-even zombies alike, turning the discontinue decision from an emotional gamble into a clean financial call. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. ---