Why You Should ALWAYS Check Your Receipt

I went to Wal-Mart to get groceries today. I was super excited because I was getting a good deal with price-matching and couponing. Not a huge deal, but saving some–which is always good.
My final price came out to be about $40 more than I expected. I was a little distraught, but sometimes that happens. I took the receipt, put my groceries in the cart, and moved aside. 
Then, I did what I always do–checked the receipt.
Now, I don’t doubt the ability of cashiers. Mainly, I’m curious. Justin and I like to see what the most expensive things we buy are (typically bags of chicken tenderloins, extra large bags of cereal, and toilet paper). For the most part, our groceries are all under $3 each. 
So, you can imagine my surprise when I saw $17 on the receipt twice for two items.
WHAT!?!?!?!

I looked closer. 14 lettuce heads for $17 charged two different times….
What the heck?!?!
As you can see on this receipt:
1) She charge 14 iceberg lettuce head for $17.92
2) Realized her mistake and charged 1 for $1.28
3) Needed to make a void, but voided the 1 for $1.28
4) Then put in 14 for $17.92 again thinking she had fixed the problem
5) Then 1 iceberg for $1.28
I had no idea what her thinking was.
I mentioned it to her, she was a little abrupt and told me to go to customer service. So, I did.
The lady read the receipt with me and agreed that something was messed up here. 
She asked if it was “that cashier” and pointed to mine. I said “Yes.” She then gave a knowing, “Ohhhhh.”
Something implied there, I wonder?
Well, she refunded me.
So, the lesson of all this:
Do what I do and ALWAYS check your receipt before you leave!!!!
Tayler is a work at home mom. She does free lance articles and dabbles in graphic design and virtual assisting for bloggers. She spent 3 years as a history and English teacher. Her passions are her husband, two children, history, reading, nature, and her Savior, Jesus Christ.
  • Good thing you checked! I always read my receipts, like you said, mainly out of curiosity, but I've never found an error like that!