Welcome to the MLP Arena!
Site Announcements Arena Tutorials Sigs & Site Support Introductions Pony Corral Swap Talk! Pony Fairs! MLP Nirvana Nirvana Sales Pony Brag Arena Off Topic Dollhouse Toy Box & Games Cupboard Customs Custom Sales Arts & Crafts Corral Adoptables For Sale - For Auction For Trade Wanted Trader & Classifieds Support What's Your Problem Private Messages Contact Us!
0 Members and 1 Guest are viewing this topic.
Huh, so now I'm a bit confused. So the ebay calculated shipping cost was the $3.04 which is based upon the weight of the item she entered, is that correct? Then why did she say it was wrong and charge me more? Wasn't the estimate based upon the weight and size that the seller entered?Apologies, I'm not a seller, so I don't know how these things work.Edit: By the way, we resolved it completely amenably, so all is good.
I'm glad that you and the seller managed to sort it out in the end its no fun to have to pay more than you expected and ebay does not allow the seller to charge more ..unless it was an estimate using the calculator as PL said.Personally I never use the calculator. I use digital scales to figure out the costs before I list the item so its pretty accurate ..but If I do happen to stuff up the shipping costs I never ask the buyer for more money, I just cover the cost myself.
LittleSpiffy, as a seller, what do you do if the shipping is wrong and is more than what was stated in the auction? Do you absorb the cost or do you charge the extra to the buyer? This is where my confusion comes in. Lots of people have had issues where they are initially overcharged in an auction, but that cost was specified right from the start, and then sometimes they get a refund. This is a case where I agreed to a shipping charge that was stated both in the ebay calculated shipping area and in the seller's description and then it was changed to a higher amount after the end of the auction via invoice. It was also not due to combined shipping.I've purchased hundreds of ponies in hundreds of ebay auctions since 2000, and I've never had an issue like this.
Edit: By the way, we resolved it completely amenably, so all is good.