*this is more or less a consumer tip. No wrongdoing is being implied here*
A lady whose store I frequent and I got in a conversation about Wal-Mart, and she talked about how she would always get charged the wrong price when she went to the Wal-Mart in The Colony, especially when it had to do with items with recent price cuts, or just put on clearance.
I frequent the one in Carrollton, and have almost never had such problems. I do have experience in a retail chain store, and from that have a theory: Every night (at least in theory), the store's computers connect to the central computers in order to transmit data on sales (giving corporate an idea on what to replenish), and recieve pricing database updates when a new product arrives, or the price changes on an existing SKU.
In a well-managed store, with nothing to hide, the connection and updates go smoothly, and the scanners at the checkouts pull up the correct prices, at least most of the time. If the updates are spotty due to "technical difficulties", pricing information may not be up-to-date, and there may be many instances where items will not scan with the correct price. If that happens, forego the item, don't make a fuss, hop in your car, and try to buy the same thing at the same brand of store down the street.
If the scanner at the other store prices it correctly, now is the time to call the corporate office. They may have a bug (which they also would like to know about), or they may have a manager or shift leader who ensures that "technical difficulties" arise at transmission time in order to give him/herself time to falsify the necessary documents to cover up their doing something they shouldn't (in the meantime missing patches that update prices).
If Corporate is suspicious of a store, they may need customer complaints from folks like you to override a District Manager who may not be doing anything about the problem. If it scans wrong at both stores, it's a bug. Corporate might want to know about it&but in any case, please do not take it out on the poor clerk.
0 comments