Navigating the transition from one aggregator to another can be a bit of a challenge due to the varying POS limitations and setups. The following are a list of helpful suggestions to help guide you in your upcoming transition to Lunchbox Aggregation.
NOTE: For Brand New Clients: 2 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 the integration by marketplace. If there are accidentally left on these will overwrite the settings that have been put in place by Lunchbox.
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's 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.
Step 1: Connect to Lunchbox - Connect Lunchbox to the Point of Sale System before the transition.
NOTE: It is important to provide our team plenty of time to help ensure that the required location information and menu structure is compatible and that there aren’t any additional adjustments that need to 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 firstname.lastname@example.org as a user to the admin dashboard of each Marketplace that you are launching across all marketplaces. 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 of the necessary information that will be needed for a successful transition by location and make sure that it has been included in your shared Configuration Workbook.
NOTE: It is important to be very specific by location. Restaurant Partners using POS that are not on some sort of Multi Location Management typically require different IDs per store.
Examples include but are not limited to:
Service Type POS ID’s
Payment Type POS ID’s
Service Fee POS ID’s & Amounts (Only if you are delivering your own 3rd Party Marketplace Orders)
Menu POS ID’s
Location POS ID’s
Surcharge - Pricing Uplifts (Toast Customers will achieve this with Menu Specific Pricing or the employment of an Open$ Tax Inclusive Menu item)
Throttling Rules (Maximum # of Orders, Max Sale $ and Interval)
Service Type Hours Overrides
3P Marketplace Credentials
Note: There are three 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.
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, find \u0022uuid\u0022:\u0022
Step 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.
Grubhub ID Merchant ID’s
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.
3P Marketplace URL’s
3P Marketplace Facilitator State Setup - Yes or No (Depending on if the DSP is responsible for paying the sales tax determines on 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
Step 3: Schedule and Communicate with the 3P 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 for testing and then proceed as you see fit for rolling out your additional locations.
Communicate with your 3P Marketplace Reps alerting them that you want your restaurant to be on POS Protocol and that the POS provider will be NovaDine along with the rollout schedule,
the more in the know your reps are the easier the transition will be. Two weeks notice should do the trick!
NOTE: Validate the launch dates that the 3P Marketplace allows for these types of transitions. Typically Thursdays are the sweet spot based on limitations that exist on the 3P Marketplace side for when new integration onboarding can occur. (Tues-Thurs)
24-48 hrs notice for Ubereats
Doordash 6 business days for integration 3 business days for photo ingestion Photo Approval can be bypassed by reaching out to your rep and requesting that they manually approve the photos.
Grubhub Needs 1-2 Weeks Notice
Step 4: Train the team - It is advised to be sure to train your staff within 1 to 2 weeks ahead of 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 3P 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: If you have never worked with an Order aggregator before this step can be skipped.
NOTE: 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 - It is advised to place test orders 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 3P Marketplace and the menu looks great and appetizing. This will also allow restaurants to ensure tickets are working through downstream workflows correctly. (ie sales reporting, printer routing etc.)
Step 7: Let’s Launch - Once the integration have 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 3P Marketplace Dashboard.
Use these checklists to help test once the menu has been pushed.https://docs.google.com/document/d/1yUmn36xXOrt3x8uK0ZuRJFv-ktPEBD2Hlz4f5CgBeT4/edit#
NOTE: Make sure to cancel any orders that have been placed to avoid drivers arriving for test orders.
PRO TIP: Contact each 3P 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. 3P Marketplaces are very busy onboarding lots of clients and these steps have been known to be missed. Call into support they can assist in getting these setup accordingly. Improperly tagged restaurants leads to decreased visibility when guests are searching the 3P Marketplace for something to eat.