Logging in to the Tablet App

Modified on Tue, 18 Jun at 4:49 PM

Article: How to Log in to the Tablet App

(Detailed Instructions)

How to Log in to the Tablet App:

(Quick Start)

  1. Go to retail.buddi.io or click on the app icon from your home screen.

    NOTE: Downloading the app onto your tablet is simple. Refer to Step #3 in this article for instructions. An app icon will be added to your home screen after you are done.

  2. Refer to the login credentials found in your Buddi Onboarding ticket. Enter the Email Address (Username) and Password found under Retail Store Sign in. You will stay signed in.

    NOTE: You will see the Tablet App's home screen as soon as you are logged in. This is the main interface that customers will see when using the tablet.

Shown: Buddi Tablet App Sign-in Page (https://retail.buddi.io). This is the default appearance of the user interface. Please send us your logo and/or branding assets so that we can help you with custom branding this interface. You can also DIY by accessing the Buddi Admin Portal (app.buddi.io) > Custom Branding > Kiosk.

Click on 'Browse Menu' to see the menu and begin shopping right away!

Staff Portal

Optional: If your staff is using floater tablets to serve customers on the floor, they can use the Staff Portal to access other areas, such as the Customer Queue or Menu List View.

1. Click on 'Staff' at the top-right
2. Use to the General Staff login credentials 
to sign in. This was provided to you in your Buddi Onboarding ticket.

General Staff can come in here to manage incoming orders (Customer Queue), BUT we highly recommend using the Admin Portal (app.buddi.io) > Order Queue.

  • The same General Staff login credentials can be used to sign in. We do not recommend signing into the Tablet App queue if your devices are customer-facing.

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