A LinkedIn user claimed to have received a fake order in his name. He said that he did not place the order, and since it was marked as cash-on-delivery, his family ended up paying for it.
The post read,”Hello Blinkit , started delivering fake orders? yesterday my family received a order of my name which i did not ordered! , it was COD, my family paid for it assuming it’s a genuine order, they didn’t called me to confirm as they did not wanted to distract me at work.”
He asked Blinkit to verify his previous order details and asked the company to check who made this fake order.
“If a person orders any, so doesn’t it appears in their order history? check my account in your system and see if theirs any order I placed for 2 bottles of nutella and a ketchup, as I have shared my personal details with you, you willl find nothing for yesterday, so who ordered that in my name? at my address?” the user said.
He further questioned Blinkit about its data protection policies.
“Check for those persons who placed fake orders by using my data like name, contact no. and address. Do you ensure your systems are secure for customer data? or doesn’t care? don’t let it be(sic),” the user added.
Blinkit reacts
The quick delivery platform expressed regret over the incident and asked the user to contact customer support service.
Blinkit commented under the post, “Hi Avesh, we’re really sorry to hear about what happened, and we completely understand how concerning this must be for you. We take such matters very seriously. Would request you to kindly share your registered contact number/order id via socialsupport@blinkit.com we’ll get this checked.”
Netizen suggests
On of the LinkedIn user suggested Blinkit to introduce OTP system before delivering an order to avoid such incidents in future.
The user wrote, “Getting order without placing one !! I think blinkit needs to work on verification before placing an order like if someone is placing the order it must be verified via OTP then maybe these things wont happen in future !! just opinion(sic).”
