Not official integrations with providers like DoorDash or UberEats refer to the use of third-party solutions, APIs, or other means that are not officially sanctioned by these platforms to connect restaurants or services with their delivery systems.
Two popular ways to run an integration like that are email parsing and tablet emulation.
The first automatically extracts order details from confirmation emails sent by platforms like DoorDash. Software analyzes the email content, pulls out key data (like customer info, order items, and delivery details), and then inputs this data into the restaurant's system for processing
The second mimics the operation of a physical tablet used for receiving orders from the chosen platforms. Software runs on a server that "pretends" to be the tablet, capturing orders directly from the delivery platform and feeding them into the restaurant's system as if they were manually entered.
When we say that something is not entirely official, there's already a certain vibe of deception, isn’t it?
On the other hand, if providers are aware of these integrations (they are), then it's not such a dishonest method.
Let's set aside the moral question and answer that: why to choose non-official integrations?
Well, because they can offer advantages.
Here are some of the main motivations behind this decision:
Customization and Flexibility
Non-official integrations can offer more customization options. That allows companies to tailor the integration to their specific needs (order routing, custom notifications, regional promotion and offers), which might not be possible with the official APIs.
Sometimes, official integrations might not provide all the features a business needs, or those features might be rolled out too slowly.
Non-official solutions can fill these gaps by offering additional functionalities or faster access to new capabilities.
Cost Savings
Official integrations often come with fees or commissions that can be substantial, especially for small businesses. Non-official ones may help to avoid these costs, making them a more attractive option for companies looking to save money.
Avoiding Lock-ins
By using non-official integrations, companies might avoid being locked into a specific platform's ecosystem, potentially reducing costs associated with switching or integrating with multiple platforms.
Faster Implementation
“Gray” integrations can often be set up more quickly, allowing businesses to start using new features or functionalities without waiting for official support or lengthy approval processes. Because this is how it works –
Waiting lists to partner up with DoorDash and others are very long, you can wait for a year and even more to get in.
Overcoming Official Limitations
You might find official integrations too restrictive, especially in terms of data access, customization, or operational control. Non-official solutions might allow you to bypass these limitations.
“Grey” integrations can sometimes connect with other systems, tools, or platforms that official ones do not support, providing more comprehensive solutions.
It doesn't sound bad at all, but the most crucial thing is that non-official integrations also and ALWAYS come with a range of problems:
Compliance and Legal Risks
Non-official integrations often violate the terms of service of platforms like DoorDash and UberEats. This can lead to penalties, account suspension, or even permanent bans.
Unauthorized access to customer data through non-official channels could result in breaches of privacy laws, leading to legal liabilities and fines (you don’t want that for sure).
Security Issues
Non-official integrations might not adhere to the same security standards as official ones, making them more vulnerable to hacking or data breaches.
This can compromise sensitive customer and business information!
Lack of Innovation and Updates
Non-official integrations might not keep up with the latest features, updates, or innovations offered by the platforms. This can put businesses at a disadvantage compared to those using official integrations that benefit from continuous improvements.
Unreliable Performance
Since these integrations are not officially supported, they may not be reliable.
It’s like one day you have access to all the features, but then the provider changes protocols or codes, and you are empty handed – the lack of full accession to the platform's features or APIs leads to order mismanagement, incorrect pricing, failure to update menu items and more.
What does lack of access to the official platform functionalities look like?
Imagine the situation:
Mark has 10 restaurants in California with a $10,000 revenue per day.
Total daily earnings from all restaurants: $10,000 x 10 = $100,000.
He uses “gray integration” of DoorDash, by the way.
One sunny – or rainy – Monday the provider changes something in their system, and all 10 restaurants lose something like $30,000.
Why so much? Typically, restaurants might receive 20% to 40% of their orders from delivery platforms, depending on the business model and location…
On average, non-official integrations fail once every 5-6 months. It takes 3-10 days to fix, so total restaurant losses per year might vary from $90K up to 300K.
Add negative reviews and clients disappointment, and congrats – you’ve just destroyed your business.
Being aware of all of this, we at KitchenHub provide official integrations only.
So we thought it would be helpful to guide you in avoiding mistakes when choosing between short-term benefits and custom solutions, especially if you're considering working with providers on your own.
.png)
.png)
