Skip to main content
All CollectionsPOS ConfigurationAloha BSL Configuration (LB 2.0)
1a - Request Data Access (NCR Aloha BSL- LB 2.0)
1a - Request Data Access (NCR Aloha BSL- LB 2.0)
M
Written by Mark Robert Turner
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:


About Aloha Takeout and BSL

In order for Lunchbox to be able to integrate with your Aloha BSL POS we will need to ensure that a Data Release form has been submitted and that your POS follows the required software and Hardware specifications needed for integration.

NCR Aloha Takeout and BSL at a Glance

Core Product

Aloha® Takeout (ATO)

Complementary Products

Business Services Layer (NCR BSL)

Separate License Required?

No

Other References

Aloha Takeout v17.1 Implementation Guide, Aloha Takeout Reference Guide, Aloha Takeout Using Configuration Utility Quick Reference Guide

What is NCR BSL

This document provides instructions for configuring NCR® Aloha® Takeout (ATO) to use the NCR Business Services Layer (NCR BSL), formerly known as Business Services Layer (NCR BSL), for sites using third-party delivery services.

The NCR Business Services Layer is cloud-based technology that provides a truly seamless guest experience for on-demand consumers, allowing them to access and interact with an authorized NCR partner using their mobile phone, a tablet, a desktop computer, a laptop, and more.

When you leverage NCR BSL with Aloha Takeout, several services come into play:

  • Order - Used by Aloha Takeout to receive orders from the third-party marketplace and send new order information and order status updates as the order progresses through the fulfilment process in the restaurant.

  • Notification - Used by Aloha Takeout to receive notifications for orders, delivery, and updates from the Order service.

  • Authentication - Used by Aloha Takeout to authenticate itself with the platform.

  • Item Availability - Used by Aloha Takeout to publish changes made to item availability in the Aloha POS to Aloha Online Ordering, eliminating the possibility of a guest adding an item that is temporarily not available to their online order.

  • Fulfillment Time - Used by Aloha Takeout to calculate a timeline for the fulfillment process of an order.

  • Delivery - Used by Aloha Takeout to connect third-party and in-store delivery services.

Software & Hardware Requirements

Verify Site Meets Requirements

  • CFC 20.29 or higher

  • ATO 19.10.21 or Higher (should be latest version available)

  • POS 12.3 or Higher (15.1+ recommended)

  • POS 15.1. needs latest RAL version

Business Services Layer (BSL)

  • Catalog (Optional Menu Source)

  • Menu (Preferred Menu Source) - if using Menu – then a menu will need to exist (or be created) in Menu Configurator (Aloha Online)

  • Order

  • Item Availability (Optional – requires ATO installed on terminals)

  • CMC / HASP Key # from the Client's Lab

  • NCR Account Exec Name (or reseller contact name)

What you need to know before you begin

This document assumes you already have a working version of Aloha Takeout on your system. If you do not, refer to he Aloha Takeout Implementation Guide or the Aloha Takeout Order Manager Implementation Guide for more information.

Complete the Data Release Form

In order for Lunchbox to begin integration we need the restaurant partner to print and sign and send this form.

Once filled out please send a signed copy to your NCR Aloha BSL Rep and cc your Implementation project manager.

Email template:

To: NCR Reseller or NCR Rep

CC: {your CSM / Implementation Project Manager}

--

Subject: "Lunchbox Data Release Consent"

--

Body:

Hello,

NCR we are partnering with Lunchbox for our online ordering solution. I have attached the required data release form for reference. Please feel free to reach out with any additional questions.

(Attach Signed Form)

Sincerely,

(Preferred Contact Credentials)

Once this has been completed Lunchbox will submit a ticket to the engineering team to begin enabling the integration.

Did this answer your question?