The Major Problem with Delivery Codes on Grubhub | Delivery Code Glitch

One of the major conversation points around Grubhub is in regards to their delivery code system, and while some are satisfied with the system, or more like unbothered, there is a major problem with the execution of this system. 

While it can be argued that the system is actually much better and easier than most platforms, there is an overall security issue with it and I think it will lead to more harm than good if it isn’t properly addressed. 

So in this video, We are talking about:

• The Major Problem with Delivery Codes on Grubhub

• What they tell you vs How it ACTUALLY is

• Everything in between!

Disclaimer: The content of this video does not contain and is never intended to be legal, business, financial, tax, or health advice of any kind. This video is for entertainment, educational, and informational purposes only. It is advised that you conduct your own research and consult with qualified professionals before applying anything you find online.

I also want to be clear that everything we are going to go over is very market dependent, and what applies to me and my market may not apply to you.

DrivenWyld/YouTube

What are Grubhub Delivery Codes?

Delivery codes on Grubhub are given to customers when a customer is required to provide a number upon delivery to receive the order, otherwise the driver cannot continue with delivering for the night, and customers have to prove they are the proper recipient.

This is a way for platforms to increase the security between stealing drivers and scamming customers.

What Makes Grubhub Delivery Codes Different?

This is not an unheard of method on platforms, and is something being adopted on every platform to an extent. However, Grubhub codes are different in a few different ways. 

Two Random Digits

Each time a Grubhub order assigns a code to an order, the numbers are completely random, higher security, mildly more annoying and only made worse when a school teacher orders and gets “67” as their number, I am not joking, that actually happened. 

Available for Contactless Delivery

This is the most nonsense thing in my opinion, why even have a delivery code system if you are going to make it available for someone who wants contactless delivery? If they have a code, they either set it themselves or you don’t trust them yet so why make contactless available?

It just makes no sense for a security feature that only works if you have contact with the customer to be available or imposed on a feature upon a customer with a feature that supports contactless service.

The Work Around

In the event that the customer cannot find the code or you cannot get in touch with your customer, you can just hit there’s a problem and proceed to conduct a contactless delivery sequence from there. 

Which is great if a customer doesn’t understand the app or isn’t answering the phone. But if you can bypass the code that easily, what’s the point of the security feature? Why have a security feature with an easy to unlock fail safe?

Then I started experiencing something firsthand with my customers… then I understood. 

The Delivery Code Glitch

Recently, I have been noticing that some of my customers have been imposed a delivery code but it just isn’t available in the app, and while I was able to help some customers in the past find theirs, I can also confirm that they were just not receiving them. 

Which thank god that the work around exists, because it just means that the work that I have been required to do can still happen without needing to contact support and the less they are required the better, but still. 

I am concerned that this is going to lead to some other problems where some opportunistic people can claim “they never got their order”, meanwhile they just never got the code, and that leads to a violation on the driver.

It hasn’t happened to me yet, and Grubhub seems to be a bit better at regulating some stuff, but then again they are also the least active app in my market in terms of the big 3 apps. So I wonder how this would be regulated in a busier market. 

The Catch 22

Honestly, I was thinking for a while on how I would fix this. Obviously I would love to see the code come through 100% of the time, but then again how do you compensate in the meantime and what if it happens again?

If you remove this work around you risk more friction, but if you don’t remove it you aren’t adding friction to the scammers either. 

You could add more support agents to compensate for the loss, but then that is going to cost more as well. 

So the question becomes which will cost you more? The cost of the thefts or the people you hire to compensate for the technological difference? Let me know what you guys think.

Final Thoughts

Honestly, this is not that big of a deal. Sure there are some customers who are generally annoyed at the prospect of having a code at all, but it isn’t something worth being too uppity about to be honest. 

I understand that when an app has been bought out, they are prioritizing other things rather than tech overhauls but I guess they added a decent work around in the meantime.

If anything it kind of represents what a difference in management can do for a company. 

If you would like to add some other perspective to the Delivery Code Glitch on Grubhub, feel free to email me: drivenwyld@gmail.com and who knows? Maybe your email or perspective and be featured in a post as well!