Hello Amazon moderators,
Could an Account Health moderator refer this case for a joint account-enforcement and catalogue-history review? Related support cases: 13288716402 and 13289253842. The UK deactivation is dated 8 September 2026 and concerns ASIN B0GV5RHJ3L. My latest appeal was rejected on 25 September.
I accept responsibility for inadequate rights checks and publication controls. I do not hold permission for the affected artwork and am not asking to reinstate the product. I am requesting review of the account-level decision after withdrawal and clarification of the remaining requirements.
I repeatedly received notices for products I believed I had deleted. My workflow involved third-party publication and international distribution. I cannot yet prove whether these were new automated uploads, retained catalogue contributions, or further enforcement of historical events. I also recall an earlier acknowledgement/correction process, but its outcome and scope need verification. I am not claiming that an acknowledgement automatically cleared the account.
What has changed:
- The UK inventory was cleared on 15 September and checked at zero listings on 24 September and again on 6 October, without a search filter.
- As account owner, I confirmed by 24 September that all connections used to publish to Amazon were disabled. Exact historical feed and revocation timestamps have not been independently established.
- Our wider European cleanup recorded report entries not visible in sampled live searches and three German records persisting after deletion attempts. These are separate examples requiring reconciliation, not proof that the UK Star Wars product was re-uploaded.
- The affected artwork will stay withdrawn. Before any future listing I will personally document artwork rights, permitted products and territories, and approve the destination marketplace. Before any reconnection I will review source products, queued feeds and international targets. Future notices will trigger a stop to the affected publishing workflow and a check of all variants. These are operating commitments, not a claim that historical technical audits have already been completed.
Please review:
1. Whether subsequent notices followed new submissions or retained/historical records, and the outcome of any earlier acknowledgement.
2. The exact account-level basis and whether a repeat-violation threshold applies; correct only verified duplicate or misattributed events.
3. Whether withdrawn UK offers, item-data contributions or images remain, and the deletion-only route while suspended.
4. Whether the authorised team can consider account reinstatement with the product permanently withdrawn, and exactly which evidence remains missing if it cannot.
Relevant Amazon guidance:
Michelle_Amazon explains infringement notices involving previously listed products and full contribution removal:
https://sellercentral.amazon.com/seller-forums/discussions/t/4c6c0459-b82d-455c-bbe7-81d5becb9383
Troy_Amazon referred another seller's repeated-enforcement issue for further research:
https://sellercentral.amazon.com/seller-forums/discussions/t/8a286589-53a7-44a0-9f65-0801617d2572
Roxy_Amazon contacted the responsible team and requested specific corrective and preventive details:
https://sellercentral.amazon.com/seller-forums/discussions/t/dac05e6a-3d37-4596-92c6-2053ac4bc0fb
I recognise that these discussions do not establish an entitlement to reinstatement. I can provide the detailed chronology, current inventory screenshot and corrective-control record privately. Please review the existing cases and the 6 October supplemental appeal rather than treating removal of a visible violation as proof that the account issue is resolved. Thank you.
@Spencer_Amazon @Kai_Amazon @Manny_Amazon
We urgently need assistance from an Amazon Forum Moderator and escalation to the internal Featured Offer / Buy Box team.
Hi everyone,
We are currently experiencing a serious and recurring Featured Offer / Buy Box issue on Amazon.de and I would like to ask whether anyone else has seen the same behaviour recently.
Our seller account has experienced similar incidents several times in the past, including cases where our Buy Box share suddenly collapsed across a large part of the catalogue without any clear account-health or pricing reason.
This is now happening again.
What we are seeing:
* Buy Box / Featured Offer share has dropped dramatically across a meaningful part of our Amazon.de catalogue.
* Several FBA offers have available inventory, but our offer is either missing from the live offer set or is not surfacing correctly.
* Some affected ASINs still show our offer as technically Featured Offer eligible.
* In several cases our pricing is competitive, and in some cases we are even the lowest FBA offer, but we still do not receive the Featured Offer.
* Suppressed / stranded listing reports do not show a broad issue.
* Our account remains healthy and many other offers on the same account are still active and eligible.
This is why we do not believe this is a normal pricing, stock, or individual-ASIN issue.
We have experienced very similar behaviour before.
Previous relevant cases include:
* Case 11700683532 – recurring account-wide Featured Offer / Buy Box issue on Amazon.de
* Cases 10549790012 and 10618075902 – previous Executive Escalations related to similar problems
* We also experienced a similar issue in the UK marketplace, where Buy Box performance dropped from around 65% to approximately 8% across hundreds of active ASINs
In one previous Germany incident, our Buy Box rate dropped from roughly 43% to 1–2%, while sales fell from around 120 units per day to approximately 20 units per day.
The current Seller Support case is:
**13348702952**
We have now escalated this again because the issue appears broader than normal Buy Box rotation and may involve offer availability, listing materialization, or an account-level Featured Offer issue.
Has anyone else experienced recently:
* FBA inventory available but your offer missing from the live Amazon offer set?
* Offers still marked Buy Box eligible but receiving almost no Featured Offer share?
* A sudden catalogue-wide Buy Box collapse without any visible account-health issue?
* The same issue recurring after Amazon previously fixed it?
If yes, I would really appreciate hearing what team eventually resolved it and whether there was any internal flag or technical issue behind it.
At this point the recurring nature of the problem is becoming extremely damaging to the business because inventory remains in FBA while sales drop sharply without any clear operational reason.
I’ve been using FBA since 2012, although I now send far less stock due to ongoing issues.
We recently sent sealed pallets to Amazon under shipment FBA15M1DH8TJ, but Amazon claims 8 units are missing.
The concerning part is that the claim was raised and rejected at exactly 00:13 on 3 September 2026 and then automatically rejected at exactly 00:13 on 3 September 2026! It is difficult to see how any investigation could have taken place when the claim was rejected at the same time it was created.
We have established packing procedures, delivery confirmation and CCTV evidence showing the shipment being prepared, but Amazon is now not responding to our emails.
Could an Amazon moderator please help escalate this for a manual review? We are happy to provide the supporting evidence.
Has anyone else experienced an FBA shortage claim being automatically rejected in this way, and if so, how did you get it properly investigated?
It is ridiculous, i used SSA for 5 days to try it and it wasn't matching up, i set my settings correctly, 2 days handling time and tracked 24 as shipping option as this is how i operate, yet amazon was telling me to deliver it next day, i know tracked 24 is usually next day but its not guareented, so for example it would say to me post by thursday deliver by friday, so there was literally no buffer incase any parcels get delivered the next day. So then when i changed it to tracked 48 it was then showing delivery in 8 days time which is ridiculous. Not only that add on top amazon seem to think Royal Mail can deliver on sundays everywhere. With SSA enabled they make it really hard to deliver on time, either that or have ridiculous delivery in 8 days and get no sales.
Since then ive downgraded again and changed back to 1 day handling time, however amazons deliver by dates are now exactly how i need them to be. How long until they force SSA on us fully i have no idea.
@Seller_RSwABJNHpHnEZ more feedback here to pass on ^
I am sure that many seller out there are frustrated with getting their VAT verified
I have been trading for over 30 years and with Amazon over 26 years with a valid VAT Registration and UK address and I am nearing the end of my patience with trying to explain that I am here and not trying to do the wrong thing.
I have spoken to Health support many times (well over 8 hours in total) I am told what I submit is OK, I then get an email saying I have submitted the wrong information from the said health support advisor
any ideas would be helpful
Hi all,
I'm hoping an Amazon moderator can help, because I've run out of options through Seller Support.
Shipment: FBA15LZPQ7QV
Booked with Amazon Freight, Amazon's own carrier. Collected on 7 July, delivered on 8 July to BHX4.
The shipment shows as delivered, but 0 units have ever been received.
On 18 August, Amazon Freight confirmed in writing that delivery went through, and that the FC then moved the goods internally to XBR2 because of dock congestion, where they were waiting to be unloaded. They said they'd update me once unloading was confirmed. That was almost two months ago. In the meantime I have followed up and been given the generic responses "we are collaborating with multiple teams to get this unloaded"
I've raised this with Seller Support three times, all within the claim window:
13106079992
13150770262 (reimbursement claim)
13216028972
Every reply has been generic, and none of them mention the Amazon Freight confirmation. Today I opened a new case with all the evidence, and it was automatically merged into 13150770262. That case is closed and can't be reopened, so nobody is looking at the evidence at all.
To be clear: Amazon's carrier delivered this stock, and Amazon's network then moved it internally. It has never left Amazon's custody. I'm not asking for anything unusual. I just want either:
Someone to trace the load at XBR2 and get it received, or
Reimbursement under the FBA inventory reimbursement policy if it can't be found.
@Amazon moderators: could you please escalate this to FC Investigations or Inbound Operations? I'm happy to send the Amazon Freight email, invoices and any other details privately.
Has anyone else had stock stuck at XBR2, or been redirected there after delivery? Any advice on how you got it resolved would be really appreciated.
Thanks,
Toby
@Seller_hzIJKXzwjDVso @Seller_8hQgfj6OVZYse @Seller_xkwDczt8sPSmx @Seller_lmwzklfLOK2Ob @Seller_l7Jtck9jxnEA0 @Seller_XUNeUuvrQDpgP @Seller_VygaQRBv4Ssmh @Seller_OOVUXZLmb2UEH @Seller_mIRnuhdx7l5sN @Seller_mb0h6u450arka @Seller_zukQNO61PzGck @Seller_khUF6HPR2AHxu @Seller_j9Bd91CW3ZVpr @Seller_DNQGSsdC7DccM @Seller_Huz6FT08OxHAR @Seller_z3k8APxGfbQEK @Seller_hnDMgUKxMh1V4 @Seller_Udi0JNbTrsmUV @Seller_XUNeUuvrQDpgP@Seller_dnxnrsZIeTNo3
Hi Xander
I receive this below response from Amazon
--------------------------------------------------------------------------------------------------------------
Hello from Amazon Selling Partner Support,
Thank you for your continued patience regarding removal order uQrJbWwms2 and the disposal of your inventory associated with FNSKU X0027WMNJN (ASINs B0DT4X1TJR and B0DT4ZHQ71). We understand this matter involves stock valued at over 7,000 GBP and has caused significant concern for your business over the past several weeks. We sincerely appreciate the detailed information you have provided throughout this case, and we want to address each of the points raised in your most recent message directly.
We have reviewed the detailed information you provided, including your shipment references FBA15L67106L (closed January 6, 2026) and FBA15L8W695R (closed April 7, 2026), as well as the screenshot of your Automated Fulfillable Settings showing Disabled. We have completed a thorough review and are writing to provide you with a definitive response.
Regarding the order source label in your Inventory Removal Report: We understand that your Seller Central Removal Order Detail page records the order source as "Amazon-initiated Automated Aged fulfillable Removal System." We want to clarify that this label is a system-generated description used in seller-facing reports. The internal classification of this removal order is MAR_ONETIME_REMOVAL, which is a mandatory capacity management action. These orders are created through an internal tool to address fulfillment center capacity constraints based on inputs from regional operations. The seller-facing report label does not change the nature or classification of the removal order. We acknowledge that the difference between the report label and the explanation provided in our previous response may have caused confusion, and we appreciate you bringing this to our attention.
Regarding your request to halt the remaining 706 units: Because this removal order was created as a mandatory capacity management action, it cannot be cancelled by sellers or by our support teams. We are not able to place a hold on or halt the processing of the remaining units under this order.
Regarding the 365-day threshold: We understand your inventory was shipped in January and April 2026, well within the 365-day period. The 365-day threshold referenced in the notification you received applies specifically to the aged inventory surcharge policy. Mandatory capacity removal orders operate under a separate process and can be triggered based on fulfillment center capacity needs, independent of how long the inventory has been stored.
Regarding your Automated Fulfillable Settings showing as Disabled: There are two separate settings involved. The Automated Fulfillable Settings toggle you referenced is distinct from the Auto Removal Setting History. The Auto Removal Setting History records the disposition that the system references when a mandatory removal is triggered. Our records show that your Auto Removal Setting History for the UK store was configured with a Destroy disposition. This was first set on November 8, 2024, and last updated on July 2, 2025. At the time this removal order was created on August 26, 2026, Destroy remained the active disposition. When a mandatory removal is triggered, the system references this configured disposition. The Disabled status on the Automated Fulfillable Settings does not prevent mandatory removals from being created. It also does not override the disposition recorded in the Auto Removal Setting History.
Regarding your reference to a legacy setting: We understand your concern that a setting configured over a year ago was used to determine the disposition. The Auto Removal Setting History retains the most recent configured disposition until it is actively changed by the account holder. Because the Destroy disposition was not updated to Return before the removal order was created, the system applied the Destroy disposition that was on record.
Regarding your concern about notification and grace period: Mandatory capacity removal orders are system-generated based on fulfillment center capacity needs. These orders reference the most recent configured disposition in the Auto Removal Setting History at the time of creation. The process for mandatory capacity removals does not include a pre-removal notification or grace period for sellers to select a different disposition. We understand this is not the experience you expected, and we recognize the impact this has had on your business.
Regarding your request for reimbursement of the 151 disposed units: The disposal was carried out in line with the Destroy disposition recorded in your account at the time. The disposed units are not eligible for reimbursement under our policy.
Regarding the disposal fees of approximately 2,300 GBP charged to your account: The disposal fees associated with this removal order are also not eligible for reimbursement under our policy.
Regarding your request for escalation: This case has been thoroughly reviewed by our specialist team, including a full investigation of your removal order details, your account settings history, and the applicable policies. The determination provided above is final.
To help prevent this from happening in the future, we recommend updating your Auto Removal Setting History to select Return as the disposition.
=======================================
My question is how Amazon can take two year old settings and destroy my inventory. Please guide me what I do in this situation.
Hello @Seller_2oAtlj7UwEmtU,
I understand the concern about the delivery dates showing 7-8 days when your items are shipped Tracked 24 and typically arrive within 1-2 days. I have reviewed case 13319280452 and it appears the issue has been addressed.
Could you confirm if the delivery dates are now displaying correctly, or if you are still experiencing the same problem? If the issue persists, please let me know and I will look into it further.
Kind regards,
-Josh
All my items are shipped tracked 24 and will arrive within 1-2 days. Yet my delivery dates are showing 7-8 days for delivery. It’s absolutely ridiculous I have went from selling £4000 a day to selling £700. Can’t sustain my business this way, if it was true fair enough but it’s so incredibly inaccurate. I send same day until 2pm so I would say 50% AT LEAST arrives next day and 50% 2 days MAX.
Hi @Seller_RSwABJNHpHnEZ

Thanks. The Seller Support Case ID is 13323401792.
The issue remains unresolved and the delivery promises have worsened. As of today, our customer-facing dates are:
- 8-box — Wednesday 7 October
- 12-box — Tuesday 13 October
- Christmas 8-box — Wednesday 7 October
- Christmas 4×4 — Wednesday 7 October
All of these promises are later than our fulfilment configuration should produce, with the 12-box then receiving a further six-day extension despite using the same 0-day handling, shipping template and SSA/DPD ExpressPak setup as the 8-box.
I spoke to Seller Support again today. They have now expanded the internal technical investigation to look at the root cause of the extended delivery promises across our catalogue, rather than just the 12-box discrepancy, and have asked the internal team to prioritise it due to the impact on conversion and advertising.
If you're able to review Case 13323401792 and help progress the technical investigation, we'd really appreciate it.