Get 10% back on your first $70,000 CDN in branded sales. Learn how
Get 10% back on your first $70,000 CDN in branded sales. Learn how
    Seller Forums
    ForumsHomeDiscussionsGroups
    ForumsHomeDiscussionsGroups

    Browse discussions

    Update your preferences for improved recommendations
    user profile
    Seller_AqvInUPukiOkW
    ∙
    user profile
    Seller_1JtWN7OO6rhPF
    ∙
    user profile
    Seller_sFKBT7qazvo4e
    ∙
    user profile
    Seller_1JtWN7OO6rhPF
    ∙
    user profile
    Seller_xjt8Ben8YGWWl
    ∙
    user profile
    Seller_oytPcY72GCa1k
    ∙
    user profile
    Seller_cNKkO2rWFDInA
    ∙
    Sort by
    RecommendedLatest activityRecently createdMost viewedMost voted
    Filters
    Date/timeAll timePast dayPast weekPast monthPast 3 monthsPast yearDate range
    Quick filters
    Discussions
    Categories
    Tags

    Browse discussions

    Update your preferences for improved recommendations
    user profile
    Seller_AqvInUPukiOkW
    ∙
    user profile
    Inventory stuck in Reserved since 5/5 at YXX1 – high-selling ASIN, being charged LTSF, Case #20395834891
    by Seller_AqvInUPukiOkW

    I’m really desperate and hoping someone here has been through this and found a way out.

    My inventory has been showing as Reserved​ since May 5th. The products arrived at Amazon about 4 months ago, and the ASIN is a top-performing, fast-moving item. Currently my listing is effectively out of stock because the units are stuck in reserve.

    Here’s what happened:

    First case: CS told me the inventory is at YXX1, described as a special type of warehouse that “replenishes regular FCs.”

    I requested a transfer to a standard fulfillment center. Each time, they said it would take 8–10 business days.

    After each waiting period, when I followed up, they told me the transfer had failed. This cycle has repeated multiple times.

    Yesterday I opened another case. The reply was that the “transfer center is handling it” and they cannot intervene with the operations center.

    To make things worse, I am still being charged Long-Term Storage Fees (LTSF)​ on this reserved inventory, even though I have no available stock to sell.

    Latest case ID: 20395834891​

    Has anyone successfully escalated a similar YXX1 reservation issue? Is there any way to force a transfer or get an exemption/adjustment for the LTSF? Any advice would be greatly appreciated—this is killing my best-selling link.

    Thanks in advance.

    2 votes
    0 votes
    30 views
    1 reply
    Latest activity
    user profile
    Seller_1JtWN7OO6rhPF
    ∙
    user profile
    URGENT: Amazon Claims ZERO Units Received for Signed FBA Delivery. Retail Value $20,214.60. Leadership Review Needed.
    by Seller_1JtWN7OO6rhPF
    Amazon replied

    Hello Amazon Seller Forums team,

    We are requesting urgent assistance from an Amazon representative regarding a severe FBA inbound failure that Seller Support has refused to escalate, despite clear proof of delivery and significant financial impact.

    Shipment ID: FBA1930BCZT2

    Case ID: 19150496031

    Marketplace: Amazon.ca

    Retail value of shipment at risk: $20,214.60 CAD

    This is not a minor discrepancy. This is a high value retail shipment that Amazon is asserting was received as zero units, despite a signed Proof of Delivery confirming Amazon accepted the shipment.

    Summary of the issue

    Amazon Seller Support is denying reimbursement on the basis that no units were received at all, while simultaneously acknowledging that the shipment was delivered to an Amazon fulfillment center.

    Key facts:

    • The shipment was delivered to Amazon and signed for by Amazon, with a valid Proof of Delivery provided.
    • Amazon is not claiming a partial shortfall. They are explicitly asserting that zero units were received.
    • The carrier has confirmed delivery and refuses to open an insurance claim because the shipment was accepted by Amazon.
    • Seller Support continues to redirect us to the carrier, despite the delivery being completed and signed.

    This creates an impossible situation where:

    1. Amazon confirms delivery occurred.
    2. Amazon claims receipt of zero inventory.
    3. The carrier confirms delivery and denies liability.
    4. The seller is left with no escalation path.

    Retail value calculation of denied inventory

    Qty FNSKU Unit Price Total

    288 X002S81ODF $13.99 $4,029.12

    192 X004O6WCZN $19.99 $3,838.08

    176 B0B34CRNTJ $39.99 $7,038.24

    48 B0952GJZQQ $48.00 $2,304.00

    30 B093ZB6VFL $23.99 $719.70

    18 B0848HWH2Z $29.99 $539.82

    18 B0949PSB7L $21.99 $395.82

    18 B0952FPLTG $74.99 $1,349.82

    Total Retail Value $20,214.60

    This inventory did not vanish prior to delivery. Amazon accepted the shipment.

    Amazon’s stated position

    “Proof of delivery only confirms that the carrier made a delivery at our fulfillment center and isn't confirmation that Amazon received the exact items and quantities stated in your shipping plan.”

    This response does not apply to the facts of this case.

    Amazon is not disputing quantities. Amazon is claiming zero units received, which is fundamentally incompatible with a signed delivery and acceptance.

    Why this requires leadership escalation:

    • A shipment cannot be delivered, signed for by Amazon, and recorded as zero units received without a serious internal receiving failure.
    • Seller Support has refused to escalate to Captive Team or Amazon Leadership.
    • The seller is being instructed to pursue carrier insurance that is contractually unavailable due to completed delivery.
    • Over $20,000 CAD in retail inventory has effectively disappeared inside Amazon’s network with no accountability.

    We are experienced FBA sellers and fully understand standard shortfall processes. This is not a routine inbound discrepancy. This is a systemic receiving failure with material financial impact.

    We respectfully request assistance from an Amazon representative to ensure this case is reviewed properly.

    Please see case ID 19150496031 for the signed POD + invoice exactly matching this shipment.

    8 votes
    0 votes
    688 views
    38 replies
    Latest activity
    user profile
    Seller_sFKBT7qazvo4e
    ∙
    user profile
    Shipping cost to Amazon
    by Seller_sFKBT7qazvo4e

    Has anyone noticed crazy shipping prices to Amazon today or is there just a glitch in the system? Usually we pay about $20 to send a case of our product to the Amazon warehouse. Today they wanted between $194 and $286 to send it. We thought we did something wrong but reentered the date and it was $90 more the second time.

    2 votes
    0 votes
    203 views
    17 replies
    Latest activity
    user profile
    Seller_1JtWN7OO6rhPF
    ∙
    user profile
    Grand Theft Larceny by Amazon - Again. URGENT: $8,000 CAD Shipment "Lost" by Amazon FBA with No Reimbursement – Denied for Illogical Reason (FBA18VF6CGDB)
    by Seller_1JtWN7OO6rhPF
    Amazon replied

    This is now the third large shipment since Amazon implemented its new reimbursement policy where we’ve effectively been robbed of thousands of dollars in inventory with no valid justification.

    FBA Shipment ID: FBA18VF6CGDB

    Total units missing: 252 (151 + 101 units)

    Estimated retail value: $7,660 CAD

    Case IDs: 18072530981, 17929419731

    We opened support cases. Amazon responded with copy-paste boilerplate rejections, refusing reimbursement with no coherent rationale.

    Their official reply:

    "We are denying your reimbursement claim for the following units because we received an unexpected item when compared to your shipping plan. This was caused by sending items with the wrong UPC, or items having missing or incorrect labels:

    Expected FNSKU B06XDSZP7H/151 arrived as ASIN B06XDSZP7H

    Expected FNSKU B004GINGOY/101 arrived as ASIN B004GINGOY"

    This response makes no sense:

    FNSKU B06XDSZP7H = ASIN B06XDSZP7H (they are the same item)

    FNSKU B004GINGOY = ASIN B004GINGOY (again, identical)

    There is no mismatch, no unexpected ASINs, and no labeling error. On the same shipment, the exact same FNSKUs were correctly received on other units, so why would only some be rejected?

    If Amazon somehow thinks these units were mislabeled or unscannable:

    Why aren’t they showing in our stranded inventory?

    Where are the 252 bags?

    Why is there no bin discrepancy or reconciliation offered?

    We have received zero rational explanations and Amazon Support has stopped replying.

    This amounts to a loss of ~$8,000 CAD and raises serious concerns about FBA's new claim policies and accountability. We need a real human to investigate. This cannot be chalked up to “unexpected item” or “labeling error” when the product ID matches exactly what was shipped and received partially.

    We are hoping forum moderators or senior escalation reps can step in and help.

    Combined with the other 2 large shipments where this has happened, we are looking at a loss approaching $20,000 CAD. Unbelievable, and unsustainable - and presumably illegal.

    18 votes
    0 votes
    1.1K views
    49 replies
    Latest activity
    user profile
    Seller_xjt8Ben8YGWWl
    ∙
    user profile
    ERROR -"You are already at the maximum inventory allowed for this product, due to capacity or other restrictions"
    by Seller_xjt8Ben8YGWWl
    Amazon replied

    Hi, we have been having this error for over 6 months now when trying to replenish the ASIN getting the message “You are already at the maximum inventory allowed for this product, due to capacity or other restrictions” when trying to send in an FBA shipment. in the past 3 years of selling we've never had this issue once.

    The overall storage capacity is nowhere near the limit, and all other ASINs in the same category are working fine. This is happening even when I try to send 1 unit, and my inventory for this ASIN shows 0 units across all statuses.

    I have opened and followed up with seller support through cases with no resolution? Can someone please, escalate the issue to the specific internal team for this what it seems a system error.

    Case ID: 19614011621

    @Seller_ZyGdB49sb7An4

    @Seller_xkwDczt8sPSmx @Seller_WIFV02H2XUFgS @Seller_seuhA2HFFSUGv

    4 votes
    0 votes
    304 views
    11 replies
    Latest activity
    user profile
    Seller_oytPcY72GCa1k
    ∙
    user profile
    I have had 60 items be destroyed by Amazon when I have it set to return to me
    by Seller_oytPcY72GCa1k
    Amazon replied

    I had talked to someone at Amazon and we had put a stop to the remaining 30 after we’ve noticed that it was getting destroyed and was but nothing. I don’t know why these people think that they can just destroy items as a default, steal my items and destroy them, but I am ticked off and it is almost impossible to talk to a person. I think I might just go down to the closest warehouse myself. thousands, now that they owe me maybe 10 this is criminal activity. And now they’ve cancelled my account because they can’t charge me for it.

    3 votes
    0 votes
    383 views
    10 replies
    Latest activity
    user profile
    Seller_cNKkO2rWFDInA
    ∙
    user profile
    Can't send inventory when I have ZERO inventory
    by Seller_cNKkO2rWFDInA
    Amazon replied

    Anyone else dealing with this? Amazon support is beyond useless, I can’t send any new shipments into inventory for a specific SKU. It says I have hit the maximum inventory allowed even though I have zero inventory left for that SKU and there's no restrictions at all, I have plenty of space left for inventory when I check that also. I waited two weeks now and it's still not letting me send in anything. Amazon support said it would "reset" on specific dates which were a complete lie. Ideas?

    3 votes
    1 vote
    280 views
    27 replies
    Latest activity