(LB 2.0) Order Aggregation Onboarding & Transition Walkthrough
Introduction
Navigating the transition from one aggregator to another can be challenging due to the varying POS limitations and setups. The following is a list of helpful suggestions to help guide you in your upcoming transition to Lunchbox Order Aggregation.
Note: For Brand New Clients, two weeks' advance notice for all Marketplaces is required.
Warning: When the time comes to transition over from a previous aggregation integration, it is very important that you alert the previous integration to remove their integration from the marketplace. If prior integrations are accidentally left on, these will overwrite the settings put in place by Lunchbox and cause order failures.
Limitations
We do not have the ability to automatically void or cancel orders that are voided or canceled on the Third Party Marketplace. Voids and Cancellations have to happen on the Marketplace, on Lunchbox, and on the POS.
We do not currently support self-delivered Marketplace Ordering.
We do not currently automatically overwrite the Takeout Pricing (A dev escalation would be required to achieve this for DoorDash. Ubereats would need to be manually adjusted.)
If you have menus overridden to close on certain days on the online menu we cannot override these settings you would need to uncheck and remove any daily closure overrides.
We do not have the ability to remove other integration menus from the ordering platform. You would need to get in touch with Marketplace Support to remove old menus. This can be done on the day of launch.
We do not have the ability to remove the previous aggregator's connection to the marketplace. It is important to remember to reach out to both the previous aggregator and the marketplace to remove the previous integration. Failure to do this could lead to order failures.
We do not have the ability to send more than one menu to each 3PD Marketplace by location.
We do not have the ability to create brand-new Merchant Accounts on the 3PD Marketplaces. If you have not connected with Doordash, Grubhub & Ubereats it is important that you sign up for an account for all locations that you are opting into using order aggregation. (Note: Lunchbox requires restaurants to pull all locations under one parent umbrella for Doordash Marketplace Onboarding. For all other Marketplaces, this is highly recommended)
Doordash/Caviar- https://get.doordash.com/en-us/semc-signup?&utm_ad_group_id=138863901320&utm_keyword=[…]SsIzrcZFTKvX3pOEE0rFPTlCuwiAKsvSEhoCr1kQAvD_BwE&gclsrc=aw.ds
Grubhub/Seamless - https://get.grubhub.com/products/merchant-portal/#bottomForm
UberEats/Postmates - https://merchants.ubereats.com/us/en/s/promo-30-days/?utm_source=AdWords_NonBrand&utm_ca[%E2%80%A6]ment=&tar=&utm_medium=cpc-brand&gclsrc=aw.ds&gad_source=1
IMPORTANT NOTE: When new marketplaces are being onboarded, we highly recommend that you check that your restaurant is visible on each primary Marketplace and the Marketplace they acquired.
Doordash acquired Caviar
Grubhub acquired Seamless
UberEats acquired Postmates
If you don't see your store listed, contact the Marketplace Support to request this action be taken.
Doordash/Caviar Support - 855 973-1040
Grubhub/Seamless Support - 877 866-4482
UberEats/Postmates Support - 833 275-3287
Order Aggregation Transition Walkthrough
Step 1: Connect to Lunchbox
Connect Lunchbox to the Point of Sale System before the transition.
Note: It is important to provide our team with plenty of time to help ensure that the required location information and menu structures are compatible and that there aren’t any additional adjustments that need to be made to ensure a successful rollout. Reference any available POS-specific setup documentation to ensure your restaurant is ready to go. Articles can be found in our Help Center please click this link. http://support.lunchbox.io
Please be sure to add [email protected] as a user to the admin dashboard of each Marketplace that you are launching. This will help provide visibility to the lunchbox support team should we need to troubleshoot during the onboarding process.
Step 2: Gather the goods
Collect all the information needed by location and ensure it has been included in your shared Configuration Workbook.
Very important: check to make sure you fill out all the columns inside the "Location Details Tab" and "Order Agg Details Tab" inside the workbook).
Note: It is important to be very specific by location. Restaurant partners that are using POS but are not on Multi-Location Management require different IDs per store.
Examples include but are not limited to:
Service Type POS ID’s
Payment Type POS ID’s
Menu POS ID’s
Location POS ID’s
Surcharge POS ID’s - Pricing Uplifts (Toast Customers will achieve this with Menu Specific Pricing or the employment of an Open$ Tax Inclusive Menu item)
Service Fee POS ID’s & Amounts (Lunchbox 2.0 is unable to self-deliver 3rd Party Marketplace Orders)
Throttling Rules (Maximum # of Orders, Max Sale $ and Interval)
Service Type Hours Overrides
3PD Marketplace Ordering URL’s - These can be found by navigating to the ordering URL for each restaurant location and copying the web URL.
3PD Marketplace Facilitator State Setup - Yes or No (Depending on if the DSP is responsible for paying the sales tax determines how this is configured.
Note: Variable Marketplace Facilitator Setup - % Rates are needed to know which party is responsible for paying the portion of sales tax that is mandated by the state where you are operating.
Marketplace Facilitator Doc for reference
3PD Marketplace Credentials
How to Find the Location Specific Ubereats UUID’s
NOTE about Ubereats UUID's: There are 4 ways to find this value, and you will need a unique UUID per restaurant.
You can request store-specific UUIDs from your Uber Eats account manager. If you have multiple locations, provide details to avoid receiving the UUID of another location. 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:
4. Or you can find the ID yourself by looking into the page's source code to find the UUID.
Step 1. Go to your Uber Eats store, right-click, and select View Page Source.
Step 2. On the source page, command+find \u0022uuid\u0022:\u0022. This will tell you how to get UUID from the code.
Step 3. The UUID directly follows the first result of the search phrase \u0022uuid\u0022:\u0022 and ends at \. In the example below, the UUID is 5c8c0826-02f5-4d10-a0f2-cc77e8c3223d.
Paste this value on the Order Aggregation tab of your Configuration Workbook for each location.
How to Find the Location-Specific Grubhub Merchant IDs
Note: This ID can be retrieved from the URL of your store's specific location. You can also retrieve these IDs from your GrubHub merchant portal.
Paste this value on the Order Aggregation tab of your configuration Workbook for each location.
How to Generate the Location-Specific Doordash Merchant IDs
Note: These IDs are created in the Lunchbox using the LB admin URL Chain Name/Tenant from the Old Admin Dashboard @ the store number.
For example: if the following brand’s URL is marcellespizza.lunchbox.io and the store number is 1995 then the Doordash ID would be 1995@marcellespizza:
Add this value to the Order Aggregation tab of your Configuration Workbook for each location.
Step 3: Schedule and Communicate with the 3PD Marketplace (ie Ubereats, Doordash, Grubhub, EZCater)
It is advisable to plan a staggered implementable rollout schedule. Start with a single location to get a feel for the integration and allow for adequate testing. Then, proceed as you see fit to roll out your additional locations.
Communicate with your 3PD Marketplace Reps, alerting them that you want your restaurant to be on POS Protocol and that the POS provider will be...
Doordash currently refers to Lunchbox internally as Novadine.
Grubhub refers to Lunchbox internally as Lunchbox v2
Uber Eats refers to Lunchbox internally as Novadine POS.
along with the rollout schedule. The more in the know your reps are the easier the transition will be.
Note: Validate the launch dates that the 3PD Marketplace allows for these types of transitions. Typically, Thursdays are the sweet spot based on limitations that exist on the 3PD Marketplace side for when new integration onboarding can occur. Typically marketplaces prefer Tues-Thurs
Doordash (Onboarding is now done using SSIO) link to support center doc here
3 business days for photo ingestion
Photo Approval can be bypassed by contacting your rep and requesting that they manually approve the photos.
Ubereats
24-48 hrs' notice.
Grubhub
1-2 Weeks notice.
Step 4: Train the team
It is advised to train your staff 1 to 2 weeks before the transition so that they know what to expect for the upcoming rollout and any adjustments that may be required with this new integration. Be sure to plan your manager training with the Lunchbox Team.
Step 5: Remind and repeat
When preparing to launch, a notification email should be sent to the Aggregator that you are moving away from. CC the 3PD Marketplace rep who is making the adjustment to notify them of the date and time of the integration removal and when the new one will be added. A reminder email should be sent the day before as well.
Note: This step can be skipped if you have never worked with an Order Aggregator before.
It is important that the connection from the previous aggregator be removed both on the aggregator side and the marketplace side so that Lunchbox can establish the new connection and avoid having old menus overwrite the new menus.
Step 6: Test the integration
Test orders should be placed through the Lunchbox Admin Login page (clientname).novadine.com. This step is critical to ensure that service type, tender, tips, tax, and menu items are being sent to the POS Correctly. Also, check hours, photos, and menu setup to ensure information is being communicated properly to the 3PD Marketplace and that the menu looks great and appetizing. This will also allow restaurants to ensure tickets are working through downstream workflows correctly (i.e., sales reporting, printer routing, etc.).
Step 7: Let’s Launch
Once the integration has been activated via the 3PD Marketplace Teams, the Lunchbox Team will need to Push the Menu. The team member will achieve this by clicking the Menu Tab>Edit Menu For a Location>Publish Menu.
On the day of launch, we recommend placing test orders using the 3PD Marketplace Ordering URL's.
Use these checklists to help test once the menu has been pushed.
Doordash currently refers to Lunchbox internally as Novadine.
Grubhub refers to Lunchbox internally as Lunchbox v2
Uber Eats refers to Lunchbox internally as Novadine POS.
Note: Make sure to cancel any orders that have been placed to avoid drivers arriving for test orders.
Pro Tip: Contact each 3PD Marketplace Rep or Support Staff and double check your restaurant category tags and information (ie Fried Chicken, Organic, Serves Alcohol etc) are up to date. 3PD Marketplaces are very busy onboarding many clients, and these steps have been known to be missed. Call support, and they can assist in getting these set up accordingly. Improperly tagged restaurants lead to decreased visibility when guests are searching the 3PD Marketplace for something to eat.
Super Pro Tip: Follow the steps outlined here to remove unwanted Marketplaces from your Google My Business Profile.
”To remove a specific provider with whom your business has a business relationship:
Contact the provider's support team.
Ask the provider's support team to be excluded from being listed on your Business Profile.
To remove a specific unauthorized provider from your Business Profile, use the .”opt out form