Received my order, and the quantity against the price I’ve been charged it absolutely r...

GetHuman2898387's Return an Order issue with Amazon.com (UK) from May 2019

Help with my Amazon.com (UK) issue
First: share to improve GetHuman2898387's odds
Strength in numbers! Companies respond better when others are watching.
Before contacting them, items GetHuman2898387 may need:
Order number, Billing address, Email address on the account (if applicable), and Name on account
The issue in GetHuman2898387's own words
Received my order, and the quantity against the price I’ve been charged it absolutely ridiculous!! ** little sweets for £*.**!!! I want to return the item to seller but for some reason they are saying it will be £*.** deducted from the amount to go back to me!! There’s is absolutely no way on earth the size of this packet or weight of it will cost £*.** to be sent. They didn’t even charge me p&p to send it!! How do I go about sending it back without it costing me the amount they want to charge me?!
GetHuman2898387 did not yet indicate what Amazon.com (UK) should do to make this right.
I have an issue with Amazon.com (UK) too
How GetHuman2898387 fixed the problem
We are waiting for GetHuman2898387 to fix the problem and share the solution with the rest of us customers.
Please help with my Amazon.com (UK) issue
Do you have a customer issue as well?
We can help you get Amazon.com (UK)'s attention and get better help faster. Tap below to get started.
Having Amazon.com (UK) issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
This email address isn't valid

Amazon.com (UK)

Return an Order issue
Reported by GetHuman2898387
May 10th, 2019 - 2 mons ago
I have an issue with Amazon.com (UK) too
Not resolved
Seen by 4 customers so far
Similar issue to 17920 others
0 customers following this
Timeline
GetHuman2898387 started working on this issue
May 10th 12:12pm
GetHuman2898387 indicated the issue is not fixed yet.
May 10th 10:23pm
GetHuman2898387 indicated the issue is not fixed yet.
May 11th 9:35pm