Kiosk <> Toast Setup

Created by Satyam Sharma, Modified on Tue, 11 Jun at 4:43 PM by Zuppler Level 2 Support

This article guides you through the steps to setup a Toast integrated account with the Zuppler Kiosk. The Toast<>Kiosk integration is managed via POSaaS today but will shift to Chef soon.


TABLE OF CONTENTS


Create account in BOB CRM

We need to start with configuring a store in BOB CRM, this will provide us with a Store ID which we need to use to connect the Toast account with the Kiosk. We need to follow the same steps we do while creating an account for a Tablet+Printer.

  1. Login to BOB CRM and click on 'Add Store'
  2. Enter the store name, phone and email address
  3. The phone number and email address provided while creating this account will be used to login to the Kiosk, so we need to make sure the phone number and email is possessed by the restaurant staff who can provide the OTP/Code while logging in
  4. Once the account is created, navigate to the 'Country' tab and confirm if the region set up there falls in the time-zone which the restaurant is in
  5. Navigate to the 'Payment & Tax' tab and make sure the sales tax percentage set up there matches the tax rate defined in the restaurant's Toast backend
  6. Lastly, click the ham burger icon on the top left of the page and navigate to Settings > Business Hours. Set up the hours of operation there as configured in our system


Copy the Store ID shown on the top left of the page beside the store name. 


Connect Toast with the Kiosk in POSaaS

We need to follow the same step as we do while setting up a Toast account in POSaaS. The only difference would be:

  1. Click on 'Foodhub' in the "Publish Menu (External System)" section of the create new POSaaS account page
  2. Enter the Store ID copied from BOB CRM in the 'External partner' field of the restaurant update page in POSaaS
  3. Please make sure to complete the POS mappings too, as its done with a usual Toast integrated account



Final Configurations

  • Lastly, assign the channel to the FoodHub External Orders channel. The remote ID of the integration should be the Store ID from BOB CRM
  • Enable the Pickup service type in control panel, this will be needed when orders from the Kiosk are created in our system
  • Assign the 'External Order' order workflow to the store. This OW has marketing automation flow for website and app orders, so if some restaurant does not want it, contact the config team to have a new OW without marketing automation configured


Pushing menu to Kiosk

Here are some points to remember about menu push to the Kiosk:

  • We are importing the menu from Toast and then pushing it to the Kiosk via POSaaS in this case. 
  • The 'Sync' and 'Publish to 3PS' job in POSaaS pushes the menu to the Kiosk. Export job does not help in pushing the menu to the Kiosk, it only sends the menu updates to the website and app.
  • The 'Debug' checkbox in the POSaaS restaurant settings provides you visibility into the menu data being passed over to the Kiosk in the 'Publish to 3PS' and 'Sync' job
  • Toast supports nested modifiers but the Kiosk does not support it yet. So, we need to make sure the restaurant does not have any items containing nested modifiers in the menu. We can uncheck the 'Import Nested Modifiers' checkbox in POSaaS to not import and push the nested modifiers to the Kiosk but it can still cause order injection failures to Toast. It's better to inform the restaurant about it and have the nested structure removed for now. We'll be having this support once the integration is migrated to Chef which should be soon :)
  • It is possible to add overrides to the menu and then push those changes to the Kiosk. You just need to add the overrides, save the changes and push the menu to the Kiosk using the 'Sync' or the 'Publish to 3PS' job



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article