Skip to main content
All CollectionsPOS ConfigurationToast Configuration (LB 2.0)
1a Part 1 - Adding the Lunchbox Integration (Loyalty & Tender) (Toast)
1a Part 1 - Adding the Lunchbox Integration (Loyalty & Tender) (Toast)
Updated over a week ago

Disclaimer: This article is for Lunchbox 2.0 customers only. If your dashboard header looks the same as below, you are in the right place:


The Restaurant Partner must activate the Toast Integration using the Toast Integrations portal on their Toast Dashboard. Without API access Lunchbox cannot begin the onboarding process for the partner.

BEFORE PROCEEDING READ THE FOLLOWING CAREFULLY

Restaurant partners onboarding with Lunchbox that are operating multiple brands and only some of those brands with Lunchbox need to ensure that Toast has configured your restaurant groupings properly before adding the API integration.

Example: Restaurant Partner 1 has a Burrito Concept (Using Lunchbox Loyalty Tender and Gift Card) and a Salad concept (Using Toast Loyalty and Toast Gift Cards) and only the burrito concept is onboarding with Lunchbox.

In this scenario each concept will require its own restaurant group to ensure that activated global integration settings only affect the concept onboarding onto Lunchbox.

In order to have your restaurant groupings reach out to Toast Support to have them adjusted before adding the integration.

Note: This is for new brands onboarding onto Lunchbox 2.0. For Lunchbox 1.0 onboarding, we are maintaining the process found Here until everyone is migrated to Lunchbox 2.0.

WARNING: It is very important that all new restaurants that are added to a restaurant group are built out with the Lunchbox & ECard Integrations (When purchasing Lunchbox Gift Cards as soon as the establishment is created and a location code should be added to all new stores before publishing. THIS MUST BE DONE TO AVOID HAVING SETTINGS CONFLICT WHEN PUBLISHING CHANGES ON GLOBAL CHAIN CONFIGURATIONS.

When requesting new locations with Toast make sure the Rep has added your requested location code to the establishment and they the location be built out with the Lunchbox v2 integration Loyalty (Only if using Lunchbox Loyalty) and Tender API (Only if using Scan to Pay) and Ecard Integration (Only if ECard is purchased)

RECOMMENDED: Do not grant API access until a location code has been added to each location in Toast POS. If this occurs it is ok Lunchbox will need to manually update the location Code to match what was added in Toast.


Adding the Lunchbox Integration

Step 1: Begin by logging into the Toast Dashboard. Then Scroll down to and click the My Integrations link in the Toast dashboard.

Step 2: Click the Add More Integrations button

Note: Restaurant Partners who are moving from Lunchbox 1.0 to Lunchbox 2.0 will see the v1 integration already listed. The initial integration should stay in place during the transition.

Additional Note: Before adding in the Lunchbox Integration it is important to note that restaurant partners must subscribe to Toast's Partner Connect. Follow this Toast article for instructions on setting this up. https://central.toasttab.com/s/article/Toast-Partner-Connect-Setting-Up-Integrations-with-Toast Enabling Toast Partner Connect does incur an additional charge of $25 a month per restaurant.

Step 3: Search Lunchbox and click Add Now

Note: This is the Lunchbox V2 integration once added it will display as Lunchbox. (This is technically the Lunchbox V2 integration.)

Step 4: Next using the Select Locations dropdown check off the Locations that you would like to add and click Apply.

Step 5: The screen will now show the list of selected locations. Click Confirm to get set up!

Note: Once the integration has been added it will appear in the list on the My Integrations screen.

Step 6: Once the Restaurant’s request has been granted, an email will be sent from Toast to [email protected]. The email will look like this and contains the location’s GUID.

The following API Email request will be done by your Implementation Project Manager
https://support.lunchbox.io/en/articles/9974663-1a-part-2-enabling-the-loyalty-and-tender-api

Did this answer your question?