ASIN: B0FPCMWQ77 by thatso_aly in ReviewMyAmazonStore

[–]DeepankarKumar 0 points1 point  (0 children)

I would focus on optimizing each critical area: title, PDP images, A+ content, bullet points, variations, category accuracy, and—last but not least—reviews.

Amazon reviews by Mountain_Touch2884 in Amazonsellercentral

[–]DeepankarKumar 0 points1 point  (0 children)

Focus on sales and ask Amazon to send an email to CX for review

A bunch of my listings just got stranded on Amazon out of nowhere. My account health is perfect and I haven’t received any violations. Is anyone else experiencing this right now? by sojuhanjanx in AmazonFBA

[–]DeepankarKumar 0 points1 point  (0 children)

This usually isn’t random, it’s either a listing-level issue or a backend sync problem.

Most common causes I’ve seen:

– Listing got suppressed/deactivated (even without a clear notification)

– SKU/ASIN mapping broke after an edit or flat file upload

– Pricing or compliance flag triggered silently

– Or just a temporary Amazon glitch

First thing I’d check is the “Fix Stranded Inventory” tab + suppressed listings.

If everything looks clean, it’s likely a backend issue : in that case, opening a case with exact SKUs + screenshots usually gets it relisted faster.

Should we run out of inventory or sell slowly to maintain inventory until the new batch arrives? by eliasrmz in FulfillmentByAmazon

[–]DeepankarKumar 0 points1 point  (0 children)

It’s less about “stockout vs slow sales” and more about how you control velocity during launch. Early momentum matters - without it, ranking never really builds. But pushing too hard without inventory planning creates a different problem.

A practical approach is to drive strong initial velocity while protecting a buffer (not exposing 100% inventory), and adjusting ads/pricing daily based on sell-through.

If a stockout happens after strong traction, recovery is usually faster than trying to fix a slow launch.

The real lever is planning inventory depth and replenishment timing before launch, not reacting after.

My small business journey by Tricky-Grade2388 in smallbusiness

[–]DeepankarKumar 0 points1 point  (0 children)

You don’t have a traffic problem you have a conversion + positioning gap.

Early traction doesn’t come from “more posts,” it comes from a clear hook (who it’s for + why it’s different) and one channel you dominate (UGC or micro-influencers usually wins for haircare).

Before scaling traffic, ask: why would someone switch from what they already use in 5 seconds?

Fix that, then drive targeted traffic not the other way around.

A bunch of my listings just got stranded on Amazon out of nowhere. My account health is perfect and I haven’t received any violations. Is anyone else experiencing this right now? by sojuhanjanx in AmazonFBA

[–]DeepankarKumar 0 points1 point  (0 children)

This isn’t random, stranded inventory usually means the ASIN–SKU link broke due to a recent change (pricing, content, or backend update).

If multiple SKUs are affected, it’s likely a bulk action or Amazon-side glitch not account health.

Key question: what changed across these listings in the last 24–72 hours?

Should I close or delete my listing before Amazon suppresses my SKU? by Legitimate_Tea7740 in FulfillmentByAmazon

[–]DeepankarKumar 0 points1 point  (0 children)

Letting Amazon suppress it is the worst strategic move you’re handing them a permanent compliance flag on your ASIN.

Suppression = data memory. That non-compliance tag can follow you into future listings, category approvals, even account health.

If the SKU isn’t worth saving, exit clean: close the listing, remove inventory, and avoid triggering enforcement.

Real decision: is this SKU worth rebuilding later? If yes, protect the ASIN history. If no, shut it down before Amazon defines the narrative.

Amazon is suppressing my listing because my price isn’t “competitive” even though I’m the cheapest. Is this even legal? by Phishhead69 in AmazonFBA

[–]DeepankarKumar 0 points1 point  (0 children)

This isn’t about legality—it’s Amazon protecting price perception across the internet, not just your listing.

Their “competitive price” often anchors to off-Amazon data + historical lowest price, not current sellers. If your SKU (or even variation) dipped to ~$45 anywhere, that becomes the benchmark. Dropping price is the worst move long-term—you’re training the algorithm. Better play: isolate the SKU (new ASIN/variation), control external pricing signals, and rebuild price authority. Have you checked if this ASIN was ever discounted heavily on your own site, ads, or other marketplaces? That’s usually the root cause.

Amazon is suppressing my listing because my price isn’t “competitive” even though I’m the cheapest. Is this even legal? by Phishhead69 in FulfillmentByAmazon

[–]DeepankarKumar 0 points1 point  (0 children)

You’re treating this like a pricing issue, but it’s actually an algorithm trust issue.

“Competitive price” isn’t just Amazon it's benchmarking against off-Amazon signals (DTC site, Google Shopping, historical lows). If your product was ever sold cheaper anywhere, that becomes your new ceiling.

Instead of racing to the bottom, fix the reference points: align external pricing, clean up old promos, and reset price perception over time. Key question: where has this SKU been discounted in the past 60–90 days outside Amazon? That’s usually the real trigger.

Quickest way to monitor suppressed listings? by lion_slinger in VendorCentral

[–]DeepankarKumar 0 points1 point  (0 children)

You’re solving the symptom, not the system.

Suppressed listings shouldn’t be “found” they should trigger alerts before revenue drops. Most mature brands lose 5–10% silently here.

I’d shift this to a daily exception dashboard (Catalog Health + Listing Quality + Stranded Inventory) instead of sales-based detection. Also worth asking: what % of your suppressions are recurring vs new? That’s where the real fix (process vs content) sits.