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 following needs to be configured in your Aloha Lab before beginning the integration.
Time sync set up on BOH (Recommendation is Google for time sync)
Aloha Takeout Order Manager on BOH is required at minimum and must be setup for Web Ordering
Labs and Restaurants should have Aloha Take Out on front of house and back of house installed (this is preferred)
UnitPriceOverride should be enabled
EnablePriceOverride should be enabled
UseTakeoutPrice should be enabled
Setting environment variables for BSL ordering
The Aloha system is sometimes configured with a .bat file that sets specific environment variables prior to launching the Front-of-House. With this method, the Front-of-House (Iberqs.exe or Iber.exe) launches with the ‘Radiant Takeout and Delivery’ service and runs under a service context. You must set the following system environment variables:
Iberdir=C:\AlohaQS for Quick Service installations or IberDir=C:\Aloha for Table Service installations.
IberRoot=AlohaQS for Quick Service installations or IberRoot=Aloha for Table Service installations.
LocalDir=C:\AlohaQS for Quick Service installations or LocalDir=C:\Aloha for Table Service installations. *
MasterCapable=False *
NumTerms=n, where n is the total number of physical terminals.
Server=n, where n is the computer name.
ServerCapable=False *
Term=n, where n is the terminal ID number of the interface server used at the site. *
TermStr=n, where n is the TermStr on all terminals used at the site.
NoFatalMsgBox=True
* Indicates variables that are not typically set up for a common Aloha Takeout installation. All other variables may already be in place.
Configuring Front-of-House to start
If ATG (Aloha Transaction Gateway) or a third-party software launches the Front-of-House (Iber.exe or Iberqs.exe) from the BOH, then the ATO application needs to also. To do this, configure the Takeout System Parameters function.
To configure Iber to start on the BOH:
With Takeout selected in the product panel, select Maintenance > Takeout Configuration > Takeout System Parameters.
Figure 8 Takeout System Parameters
Under the ‘Service’ group bar, type the IP address the Aloha BOH site controller uses to connect to the Aloha network in ‘Service Host.’ The Aloha Takeout service broadcasts and accepts messages across this IP. If the IP address is incorrect or the network adapter is not at the top of the Connections frame, the terminals will not be able to connect to the service.
Select Start POS Interface to automatically start and restart a UI-less instance of Iber.exe or Iberqs.exe on the BOH computer to accept orders from a web order.
Leave all remaining options as their default unless otherwise instructed.
Click Save and exit the Takeout System Parameters function.
Creating void reasons for future and canceled orders
In a typical Aloha Takeout installation, you create two void reasons in the Aloha POS for future orders and canceled orders, and associate these in the Takeout Settings function. You can use these existing void reasons; however, you most likely will create new void reasons specifically for online orders.
To create the ATO void reasons:
With Takeout, Quick Service, or Table Service selected in the product panel, select Maintenance > System Settings > Void Reasons.
Click New to create a new void reason.
Under the ‘Settings’ group bar, type a name for the void reason in ‘Description.’
Select or clear Return voided items back to inventory based on the following criteria:
For a Future Order void reason, clear Return voided items back to inventory, as these items are not ordered.
For the Canceled Order void reason, select Return voided items back to inventory, if you can prevent the items from being prepared or you can reuse the items. Clear Return voided items back to inventory, if you typically prepare and waste the items as a result of a canceled order.
Select Do Not Report for the future order void reason.
Clear Do Not Report for the canceled order void reason.
Click Save.
Repeat this procedure to configure either the future order or canceled order void reason.
Click Save and exit the Void Reasons function.
Configuring future orders for BSL ordering
By nature, an online order is a future order and you must configure Aloha Takeout for future ordering. Here you also associate the void reasons you created in “Creating void reasons for future and canceled orders” on page 17.
If you implement Aloha Takeout Order Manager where you manage orders from the BOH, instead of the full Aloha Takeout product, you must ensure you select ‘Activate future orders via server.’ If you are using the full Aloha Takeout product, clear ‘Activate future orders via server.’
To configure future order for BSL ordering:
With Takeout selected in the product panel, select Maintenance > Takeout Configuration > Takeout Settings.
Select the Options > Settings tab.
Figure 9 Takeout Settings - Options - Settings Tab
Under the ‘Settings’ group bar, select Auto fulfill orders to enable Aloha Takeout to automatically close the check in Aloha Takeout when the check is closed in the Aloha POS. Note: This option does not affect delivery orders.
Select Close checks on apply payment to enable Aloha Takeout to automatically close the check in the Aloha POS once full payment is applied.
Note: This option is a global setting and applies to all order modes aligned in Aloha Takeout. You can opt to override and configure this for specific order modes in Mainte- nance > Takeout Configuration > Takeout Settings > Order Modes.
Select the void reason created for cancelled orders from the ‘Order cancel void reason’ drop-down list.
Select the Options > Future Orders tab.
Figure 10 Takeout Settings - Options - Future Orders Tab
Under the ‘Future orders’ group bar, select Enable future day orders.
Select Auto-release future orders, if applicable.
Select the void reason to use for future orders from the ‘Future order void reason’ drop-down list.
Select Activate future orders via server, if using ATO Order Manager instead of the full Aloha Takeout product.
Leave all remaining options as their default unless otherwise instructed.
Click Save and exit the Takeout Settings function.
Provisioning Aloha Takeout for use with BSL
You must provision Aloha Takeout to identify the site and communicate with NCR BSL. During the interim when these options are in the Aloha Configuration Center interface, you must add custom values using the Takeout Settings > Custom Settings tab.
To enter values into the Custom Settings tab:
With Takeout selected in the product panel, select Maintenance > Takeout Configuration > Takeout Settings > Custom Settings tab.
Figure 11 Takeout Settings - Custom Tab
Click Add and type the XPath, Element name, and Element value for each line. Leave Attribute cleared for each line.
Click Save and exit the Takeout Settings function.
Use the following lines to enter in the Custom tab. For your convenience, you can copy the ‘xpath’ and ‘element name’ from this document and paste it directly into the application:
EnableExternalCommunication - Set to True for NCR BSL to work. XPath: /Config/Options/ExternalCommunicationConfiguration Element Name: EnableExternalCommunication
EnableOmniChannelCommunications - Set to True for NCR BSL to work. XPath: /Config/Options/ExternalCommunicationConfiguration
Element Name: EnableOmniChannelCommunications
EnterpriseUnit - An alphanumeric value that identifies a specific site XPath: /Config/Options/ExternalCommunicationConfiguration Element Name: EnterpriseUnit
OcpSharedKey - An alphanumeric value used to validate the site to NCR BSL for ordering.
XPath: /Config/Options/ExternalCommunicationConfiguration Element Name: OcpSharedKey
OcpSecretKey - An alphanumeric value used to validate the site for NCR BSL for
ordering.
XPath: /Config/Options/ExternalCommunicationConfiguration Element Name: OcpSecretKey
OcpApplicationKey - Identifies the application connected. In this case, the value
represents ATO and is always set to 8a8088e05d9c6da0016051c508c5000c. XPath: /Config/Options/ExternalCommunicationConfiguration
Element Name: OcpApplicationKey
OcpOrganization - Identifies the company and is created by NCR BSL based on the name of the company.
XPath: /Config/Options/ExternalCommunicationConfiguration Element Name: OcpOrganization
In addition, you can use the following optional setting:
EnableOnlineOrderAlert - Set to True. XPath: /Config/Options
Element Name: EnableOnlineOrderAlert
Versioning Aloha Takeout
After you configure all before-mentioned procedures in this document, you need to version the Takeout Settings record to support additional sites for BSL ordering. This allows you to copy your configuration to other sites without having to repeat your configuration. The main reason to version is because the ‘EnterpriseUnit’ used in the provisioning process is unique to the site.
To version the Takeout Settings record:
With Takeout selected in the product panel, select Maintenance > Takeout Configuration > Takeout Settings.
With the function open, click Version from the command panel. The Version Assignment dialog box appears.
Figure 12 Version Assignment Dialog Box
3. Click OK.
Net New Locations: Set your locations to Emergency Close until it is time to begin testing
Pro Tip! Setting your net new locations to emergency close until your launch date will allow us to set up order aggregation without running the risk of accidentally setting your store live early.
Do so by navigating to AOO and go to edit the site and check off the Emergency Closed checkbox. When you are ready to begin testing and or go live the setting will need to be unchecked.
