Uber Eats Order Aggregation Onboarding & Configuration
In this article, we’ll detail the process for Onboarding and Configuring a brand or location for Uber Eats Order Aggregation.
Note: For general Order Aggregation Onboarding, please refer to: Order Aggregation Onboarding & Transition Walkthrough
Table of Contents
To get started with onboarding your Uber Eats Marketplace for Order Aggregation, refer to the following steps.
If you have an Uber Eats Account Manager, introduce them to your Lunchbox POC (Point of Contact) so they can assist with providing any specific Uber Eats information like the UUIDs for the stores being onboarded.
If you are comfortable with sharing, provide your Lunchbox POC with access to your Uber Eats Merchant Portal by creating a login for them. This will help will testing and troubleshooting.
Retrieve all Store UUIDs:
There are 4 ways to find this value and you will need a unique UUID per restaurant.
You can request the UUIDs of your stores from your Uber Eats account manager. Provide details to avoid receiving the UUID of another location if you have multiple. Adding the URL of the store(s) in the request always helps.
If your location doesn’t have a rep this can be found by connecting with the support team.
You can also find the UUID from the Uber Merchant Portal (https://merchants.ubereats.com/) at the end of the Store URL:
Or you can find the ID yourself by looking into the page's source code to find the UUID.
Go to your Uber Eats store, right-click, and select View Page Source.
On the source page, find \u0022uuid\u0022:\u0022
3. The UUID directly follows the first result of the search phrase and ends at \. In the example below, the UUID is 5c8c0826-02f5-4d10-a0f2-cc77e8c3223d.
Once you have gathered your location’s UUIDs, provide them to your Lunchbox POC.
Provide the following information to your Lunchbox POC for each of your locations:
POS External Location ID
Location Lead & Prep Times
Uber Eats URL
Uber Eats POS External Service Type ID
Alternatively, you can use 1 “3PD” External Service Type ID for all Order Aggregation Marketplaces.
Uber Eats POS External Payment ID
Alternatively, you can use 1 “3PD” External Payment Type ID for all Order Aggregation Marketplaces.
Determine if you would like to use an Uber Eats (or 3PD Marketplace) specific menu or if you are going to use a menu that will require an Uplift % for the entire menu being sent to Uber Eats.
Provide the POS External Menu ID or Name to your Lunchbox POC.
Once this initial information is provided, your Lunchbox POC will have Uber Eats added as an integration to your Lunchbox Dashboard.
Meet with your Lunchbox POC and confirm a launch date and time for the Uber Eats Order Aggregation transition.
Your Lunchbox POC will then submit the Uber Integration: Tech Support Request Form filling out the following information:
Email = Lunchbox POC email
Are you the Integration owner = Yes
Integration Name = Novadine POS
Client ID = (please refer to internal docs)
Product = Uber Eats
Eats > Category = Stores
Eats > Store request = Store onboarding/offboarding
Action = Onboarding
Staging Profile Name = Brand Name
Store UUIDs = One per line - DO NOT specify store URLS
Date & Time to schedule on - If specified, action will be taken on the date specified, and not ASAP. Action will be taken within a 1 hour window from the time specified.
Note: Scheduling can only be 24+ hours from now.
Additional context = Anything that may be helpful for UberEats (Example: Launch or staging date)
Timezone = Specify timezone name, if this needs to be scheduled
Note: Please schedule at least 3 days in advance for the integration to be completed by Uber Eats.
Once your Lunchbox POC receives a confirmation email from Uber Eats, they will reach out to you with the next steps for the date and time of the launch.
You’ll be able to start testing and taking orders when the integration is complete.
Once the integration is complete, Lunchbox will schedule time to test orders and make sure they are flowing properly from Uber Eats to Lunchbox to your POS and follow up with any additional information or requirements.
When you are live, please utilize email@example.com and Uber Eats support for any assistance.
Note: Uber Eats refers to Lunchbox internally as Novadine POS.
The Lunchbox Onboarding and Configurations Team will perform the following in your Admin Dashboard to prepare, test and launch Uber Eats for Order Aggregation (the following instructions are for the older version of the Lunchbox 2.0 Dashboard:
Gather Location & Menu information provided by the RP (Restaurant Partner) as mentioned above.
Request Uber Eats to be added to the Integrations page of the RP’s Admin Dashboard by submitting an Engineering Change Request ticket.
Populate Location information from the POS on the Locations page (if it is not auto-populating from the POS)
Navigate to Menus > Admin Links > Service Types and create an Uber Eats Service Type
Add the Global External Service Type ID (if applicable) that will used when sending orders to the POS. If there is a Local External Service Type ID, populate that in Service Types.
Mark as Visible and Internal Use so it is not displayed to customers on the 1st party order site.
Select Pick-up as the Service Group ID.
Alternatively, you can use 1 “3PD” Service Type for all Order Aggregation Marketplaces
Navigate to Menus > Admin Links > Edit Provider and select Uber Eats
Enter the Global Service Type ID and select the Take Out Service Type.
Navigate to Menus > Admin Links > Payment Types and create a Uber Eats Payment Type.
Add the Global External Payment Type ID (if applicable) that will used when closing orders out in the POS (as an “Other Payment option”). If there is a Local External Service Type ID, populate that in Payments.
Alternatively, you can use 1 “3PD” Payment Type for all Order Aggregation Marketplaces
Navigate Menus > Admin Links > Edit Order Provider and select Uber Eats
Enter the Global Menu ID that will be used for All locations. If there is a Local Menu ID, populate that in Integrations > Order Providers > Uber Eats for each location.
Navigate to Integrations > Order Providers > Uber Eats and populate the following:
Uber Eats ID = location code @ tenant (for example 0003@gdsalads):
Service Type Ext ID = Only populate Uber Eats (or 3PD) Local External ID if the RP is not using a Global External ID for all locations
Menu ID = Only populate the Local Menu ID if the RP is not using a Global Menu ID for all locations
(Optional) Open Offset Minutes = Negative time that you would like to allow orders to start being placed from Uber Eats (for example if your business hours open at 11 AM and you want to start taking Uber Eats orders at 11:15, set this to -15.
(Optional) Close Offset Minutes = Negative time that you would like to stop orders from being placed from Uber Eats (for example if your business hours close at 10 PM and you want to stop taking Uber Eats orders at 9:45, set this to -15.
Item Upcharge % = Local Menu Upcharge percentage that you would like to add to your menu items if not using a Global Menu Upcharge.
Enable Menu Integration = Set the date for when the menu should be sent to Uber Eats
Enable Order Integration = Set the date for when the integration with Uber Eats should begin.
Navigate to Menus and click on the Menu you are using to send to Uber Eats. Ensure that the new Uber Eats (or 3PD) Service Type is checked off
Navigate back to Menus, select Edit Menu for a Location, and add the Menu that you are using to send to Uber Eats.
Navigate to Business Hours, select the Location, select the Menu being sent to Uber Eats, and update the Custom Hours.
If you have the same hours for all locations, leave the location unselected and set up Default Hours to be used across your brand. Custom (local) will always override Default (global) hours.
Navigate to Payments, select a location and add the Uber Eats (or 3PD) Payment Type. Enter the Local External Payment ID if it is specific to the location (this will override the Global External Payment ID)
You will need to add the Uber Eats (or 3PD) Payment Type individually for all locations.
Navigate to Service Types, select a location, Approve the Uber Eats (or 3PD) Service Type and Save.
Once Approved, configure the following and Save:
Status = Enabled
Payment Processing = Uber Eats (or 3PD)
Order Fulfillment = Enter Lead Minutes, Prep Minutes and Minimum Order Amount
Order Handling = Auto Send to the POS & (optional Hold Same Day & Future Orders if you want send scheduled orders to the POS based on Prep time).
Tax Rules = Will populate with the Menu
External ID = Enter Local External Payment ID if it is specific to the location (this will override the Global External Service Type ID)
You will configure the Uber Eats (or 3PD) Service Type individually for all locations.
(Optional) Configure Order Throttling Rules for Uber Eats by navigating to Order Processing > Order Throttling Rules, selecting the Uber Eats (or 3PD) Service Type and configuring the rules.
Once the above has been completed and Uber Eats has alerted Lunchbox and the client that they are ready for Lunchbox to send the menus, navigate to Menus > Edit Menu for a Location. Select the location and click Publish Menu. This will send the menu and integration information to Uber Eats.
Do this individually for all locations.
Navigate to Event Logging, select the location and make sure there are no errors when sending the integration to Uber Eats. This is what a successful integration looks like:
Navigate to the Uber Eats Location URL and ensure that all of the settings that you’ve configured along with the menu structure are correct.
Do this for all locations.
Communicate with the RP and place a test order to ensure that the order is flowing into Lunchbox and being sent to the POS without error. Provide the Restaurant Partner with the Testing Checklist: https://drive.google.com/file/d/1lwbR0OBEFqriBxOY7p1HosbO3OEopPOH/view?usp=sharing