Again today I have £37 of additional shipping charges paid out of my account to Evri for their fraudulent adjustments of parcel weight and dimensions. This needs to stop as it only happens on Amazon - Packlink never do this? So how is it that it keeps happening to thousands on Amazon?
Contacted seller support via chat which was a waste of time as always is and was told to contact Evri myself?????
Absolutely furious as its neverending .... All my dimensions are correct and carrier states the same? WHY DOES NO-ONE AT AMAZON CHECK THIS BEFORE PAYING AS CLEARLY THEY KNOW THERES A BIG PROBLEM WITH SELLERS BEING INCORRECTLY OVERCHARGED? EXAMPLE BELOW OF WHICH I HAVE 6 THE SAME AND THEN A FURTHER CHARGE OF £12.00 FOR ANOTHER PARCEL THEY CLAIM IS 5KG WHEN THE ITEM IS 1.2KG AND GOES OUT BUBBLEWRAPPED? SOUL DESTROYING
Transaction date: 26/04/2026
Tax:
Customer-Entered Dimensions: 61 X 46 X 46 CM
Weight: 500 G
Carrier-Audited Dimensions: 61 X 46 X 46 CM
Weight: 500 G
Other chargeback
-£4.16
Other chargeback
-£0.83
Amount already paid:
£2.95
Total Charge from Carrier
-£5.99
Revised Tax from Carrier
-£0.51
Other
Carrier delivery label adjustment due to under-charged delivery label:
-£2.53
Transaction Total
-£3.04
i have been hit with surcharges by evri
an example
Customer-Entered Dimensions: 30 X 24 X 15 CM
Weight: 500 G
Carrier-Audited Dimensions: 30 X 24 X 15 CM
Weight: 500 G
Other chargeback
-£8.32
Other chargeback
-£1.67
Amount already paid:
£2.95
Total Charge from Carrier
-£11.99
Revised Tax from Carrier
-£1.51
Other
Carrier delivery label adjustment due to under-charged delivery label:
-£7.53
Transaction Total
-£9.04
evri agree exactly with my measurements and weight but added another £9.04 for a £2.95 parcel
anyone know how i can appeal these charges, its happened today on a dozen orders
thanks
peter
Hi all,
I wanted to raise a serious issue we’ve recently experienced, partly to document it for others, and partly in the hope that a moderator can escalate this internally.
Context
We are a high-volume UK used book seller, and all of the affected inventory was used stock only — we do not list these items as new.
What happened
We ran a bulk update via the SP-API to change shipping templates on our FBM used book listings (~10,000 SKUs).
API used: putListingsItem (PUT)
Intent: update merchant_shipping_group only
We did NOT include condition_type in the payload
Following this update, a large number of listings were surfaced on Amazon as “New”, despite our internal data still showing them as used.
Timeline / Mitigation
The issue was not immediately apparent because we experienced a noticeable increase in sales following the update, which we initially attributed to improved shipping settings.
Once we identified that listings were incorrectly being surfaced as “New”, we acted immediately:
Placed the account into holiday mode to prevent further orders
Investigated and identified the root cause
Implemented a fix (migrated to PATCH requests)
Began correcting affected listings
By this point, approximately 600 orders had already been placed under the incorrect condition display.
Amazon’s response (important)
In Case ID 12422628992, Amazon has confirmed:
PUT replaces attributes and drops anything omitted
Because condition_type was not included, it was effectively removed
Listings then defaulted/surfaced as New
The API returned 200 ACCEPTED with no warning or validation error
There are currently no safeguards in place to prevent this
So to be clear — this is confirmed platform behaviour, not speculation.
Impact
As a direct result:
Customers purchased items believing they were New
They received correctly described used books from our inventory
This led to:
Negative feedback
Returns
Refunds
Return postage costs
Account health impact
Example feedback:
“I ordered a new book and received a used one”
“Advertised as new but looked worse than a library book”
“Ordered NEW and received a damaged used copy”
Current situation
We’ve fixed our integration (now using PATCH)
We are correcting listings
API support have been helpful in explaining the cause
However:
Seller Support is refusing to remove feedback
No reimbursement is being offered
The position is essentially: “feedback reflects customer experience”
The problem
The customer experience was incorrect because:
Amazon displayed the wrong condition at the point of sale
Given we only sell used inventory, this was not a listing or stock error on our side.
So we are in a position where:
Amazon acknowledges the root cause
But the seller absorbs all consequences
Financial impact
So far:
Dozens of refunds issued
Return postage costs incurred
Outbound shipping losses
Current estimated impact is already £500+ and rising as returns continue.
Why I’m posting
Warning to other sellers/developers
If you are using putListingsItem, be extremely careful
Omitting attributes like condition_type can silently alter listings
Request for moderator escalation
There is a clear gap between:
acknowledged platform behaviour
and seller-impact resolution
Request
Could a moderator please review and escalate this internally?
Specifically:
Whether feedback caused by incorrect condition display can be removed
Whether losses directly caused by this behaviour can be reimbursed
Whether safeguards are being considered for this type of scenario
Happy to provide:
Case ID (12422628992)
Order IDs
Transaction breakdowns
API logs
Thanks in advance,
I have circa 190 asins that have had their brand name changed to WHAPELQ, this asins were originally set up using the brand LessThanTenQuid unfortunately this mark the IPO did not approve.
The listings were created in 2016 and the rules were a little different then, I recall having that brand in my brand registry but at some point it dropped off most probs as there was no valid trademark for it.
I`m now at a position where I have most ASINs blocked as I need approval for this hijacked brand value (relates to chinese company accoding to IPO)
I have requested Amazon to revert but met with no success, I have over 500 units in FBA which are now sat there and I`m at wits end what to do.
I do however have a brand that is in brand registry which I attempted to migrate to but Amazon rejected this and also stated my previous brand which was no longer in brand registry was tombstoned. At the very least I`d like to revert back to LessThanTenQuid for now.
Case ID = 12256032482
Are any of the mods able to help at all pls - @Seller_PIHyltK09pbl3
Afternoon @Defect Prevention & Reconciliation team,
I am in a situation where stock is "unable to be located" after being checked in to the warehouse, it's been over a year with nearly 15 cases opened through the account support team and now I am not even getting responses back to open cases.
What can be done to rectify this, i have the same conversations with the FBA team who agree that i am due a refund of stock return but once i come off the phone i get nothing back except an automated response about not eligible for refund and stock can't be located and with cases not being responded to I am at a loss with significant impact on my business and a value of stock I cant return, sell or get a reimbursement on.
The warehouse team are just ignoring the cases and I really need an answer and my stock returned, they are the fastest moving items of circa 500+ in total and this not only impacts myself but is money amazon are not getting from sales.
See below 3 of the most recent cases opened for the same topic dating back to december with no response.
Case notes ending;
7402
2462
6902
Please can someone come back to me with a resolution
Thanks
Hello, I would like to ask you if the 500 kg limit in pallet weight is rigorous or there is tolerance for some kilos more. As not all industrial pallets have the same weight and there are times that with one more carton you have a total flat top on pallet, which will give you more safety during shipping.
Here is our help page on that topic: Shipping and routing requirements
"Regardless of pallet option, pallets must not exceed 500 kg in gross weight including the weight of the pallet."
Hello, I would like to ask you if the 500 kg limit in pallet weight is rigorous or there is tolerance for some kilos more. As not all industrial pallets have the same weight and there are times that with one more carton you have a total flat top on pallet, which will give you more safety during shipping.
For example if a pallet reach the f.c and weights 510kg is there possibility warehouse to reject it?
All best
REMOVAL ORDER QUESTION:
Why does Amazon's system sometimes cancel units from Removal orders?
For example, we might have 500 units of a particular SKU in FBA, arrange a removal order for 50 units and then Amazon only ships out 47 and cancels 3 from the removal order. It's really frustrating as it means we have to keep checking each and every order on Amazon's system to see what they decided to send and what they decided to cancel. Amazon wouldn't do this for customer orders, so why does it get done for removal orders?
Dear Amazon Team,
CASE ID: 12550908942 - Last Amazon reply: (No Reply) - Deactivated Overnight on 24 April 2026. Operational Address Verification failed despite having invoices and my driver's license at that address. A complete disaster!
I am writing on behalf of our UK-based brand, a 7-figure global seller operating across the UK, EU, UAE, Saudi Arabia, and the USA since 2021. We own the brand "FoldWise", where all our products are patented, designed and sold only by us. We hold a perfect Account Health score of 500, carry no violations, no penalties, and no overdue payments to Amazon, HMRC, or Companies House. We are a fully registered, VAT-compliant, actively trading limited company with physical operations in the UK at the VAT address.
We are proud members of the Amazon DAA programme, hold a Strategic Account with Amazon Ads, and in 2024 were personally invited to Amazon Headquarters as part of the Amazon Accelerator Programme, a testament to the trust and credibility we have built with Amazon over the years.
On 24 April 2026, our account was deactivated overnight without prior warning, and without any opportunity to respond in a manner entirely inconsistent with Amazon's own stated processes. We were registered with the Account Health Assurance (AHA) programme, which explicitly guarantees accounts will not be deactivated without Amazon first working with the seller to resolve the issue. That guarantee was not honoured.
The root cause appears to be a technical error on Amazon's side: when we attempted a minor, routine business address edit on Seller Central, Amazon's system automatically pre-populated outdated documents in the background. Saving that edit, a standard, innocent action, instantly triggered deactivation. We made no erroneous submissions. Our documents fully meet Amazon's KYC and verification standards, and we have a comprehensive, verified document trail to prove it.
The deactivation notice we received read as follows:
After the deactivation, I have received the following deactivation notice:
1. “My name is Becky, and I am a member of the Amazon Escalations Team that has previously contacted you. Your
account has failed our verification process. As a result, your selling account has been deactivated, and your listings have
been removed. Continue to ship open orders and respond to customer inquiries to avoid further impact on your account.
Funds will not be transferred to you but will stay in your account while we work with you to address this issue in
accordance with our Funds disbursement eligibility policy:
https://sellercentral.amazon.co.uk/gp/help/external/help.html?itemID=9RA9LYBJ3QP27M6
We leveraged a combination of automated means and expert human review to identify this issue and make this decision.
Why is this happening? We took this action because the business documentation that you submitted could not be
verified. The document does not meet our requirements.” (Amazon Payments UK)
— Amazon Escalations Team / Amazon Payments UK
We submitted multiple detailed appeals with full documentation. Every single appeal received one of the following template responses — with no substantive review, no explanation, and no path forward offered:
"We took this action because the business documentation that you submitted could not be verified."
"Having reviewed your account thoroughly, we have decided that your account will remain closed."
"We reviewed the information that you provided, and we have decided that you do not meet our requirements for a Selling on Amazon account."
"This decision has been reached because we have not been able to successfully process your application to open a Selling on Amazon payment account."
None of these responses addresses the substance of our appeals. No specific document has been identified as deficient. No guidance has been given on what to correct. We are being refused access to our own account with no actionable path to resolution, a process that gives the appearance of review while offering none.
To compound matters, since the deactivation:
Phone support has been cut off entirely for our account.
The AHA team has not contacted us and remains unreachable, despite our enrollment.
The "Business Address" and "Identity Verification" sections in Seller Central are completely locked — we are unable to update or correct anything.
We have multiple full shipping containers of stock held at Amazon fulfilment centres, entirely inaccessible to us.
All listings across all marketplaces are deactivated, with estimated losses of £8,352 per day — now amounting to a significant five-figure sum and rising daily.
We have active loans, supplier contracts, wages, and a team whose livelihoods depend on this account. This deactivation was not caused by any wrongdoing on our part. It was caused by a system-level error that we had no way to anticipate or prevent, and we are now being denied any meaningful channel to resolve it.
We are fully cooperative, fully compliant, and ready to provide every document requested. We are asking Amazon to urgently review this case, restore access to our account, and assign a dedicated contact, something that, as a Strategic Account, DAA programme member, and former Amazon Accelerator participant, we would reasonably expect to have access to.
We respectfully ask fellow sellers and any Amazon representatives monitoring this forum to escalate this matter. Every day without resolution causes further irreversible damage to a legitimate, long-standing Amazon business that has done nothing wrong.
Kind regards,
Mihai Gaina
Owner - FoldWise
@Seller_khUF6HPR2AHxu
@Seller_Z6JEwkZB24rWj
@Seller_X881ZiELfGPFD
@Seller_mIRnuhdx7l5sN
@Seller_XUNeUuvrQDpgP
@Seller_8NNB08xpdcirG
@Seller_Udi0JNbTrsmUV
@Seller_a4DFomhAJFJQ6
@Seller_WIFV02H2XUFgS
@Seller_VJ4XoAkjDpjPH
@Seller_fgtTzyHQfOM1x
@Seller_lZRcl2vvP1C8Q
@Seller_b91S9zQ2eKxLt
@Seller_VJ4XoAkjDpjPH
@Seller_XUNeUuvrQDpgP
@Seller_z3k8APxGfbQEK
@Seller_lmwzklfLOK2Ob
@Seller_XUNeUuvrQDpgP
@Seller_FJwyF3iu5qxUY
@Seller_8hQgfj6OVZYse
So, I already have a recent thread regarding the injustice of losing a £500 claim due to the loss of a buyer's return using an Amazon-issued label but I am now fighting separately to get the negative ODR removed on this and another not at fault claim.
1) Order ID: 205-7462711-9911565 - When I originally lost the claim my ODR was marked as not at fault, as they rightly said the parcel being lost was beyond my control. After I appealed, lost with same reason given, my ODR suddenly changed to being negative! Nothing whatsoever changed between the first loss and the appeal, the parcel being lost being out of my control still applied so why suddenly change the ODR from not impacted to negatively impacted?
Hoping a mod will come on and help me overturn this transparent injustice. The Case ID is 12281902882.
2) Order ID: 203-0116317-7372367 - this is a claim I lost only due to not being able to provide a signature - tracking still shows it was delivered, it was posted on time and delivered before estimated date. I have had other similar claims where my ODR was not impacted as tracking shows I sent the item and any subsequent non-delivery was beyond my control. However, yet again they choose to negatively impact my ODR.
Again, could a mod please assist in overturning this. The case ID is 12280722212
@Seller_CnfW62x6yxvJw@Seller_hnDMgUKxMh1V4 @Seller_XUNeUuvrQDpgP @Seller_Udi0JNbTrsmUV @Seller_TSXM2A5nxWSuH @Seller_mIRnuhdx7l5sN