Restaurant365 integrates with Aloha POS, enabling seamless data flow between a location’s POS and the R365 platform. This allows daily sales, labor, and payment information to automatically drive reporting and accounting processes in R365. Learn more about POS integrations.
Data Transfer from Aloha to R365
R365 uses an application installed on a local Aloha POS computer or back-office server to poll and transmit data. This requires the local device to remain powered and connected to the internet for polling. Learn more about connecting Aloha below.
The POS system is the source of record for all daily sales and labor activity. R365 reports on, but does not alter, the information recorded in the POS.
The daily polling cycle imports Aloha data from the previous business day and creates corresponding records in R365 for financial and operational reporting, including the Daily Sales Summary (DSS).
Sales Data
When sales data is imported, R365 creates detailed records based on the information received from the POS. Learn more about POS Sales integrations.
Click to expand for additional information.
Sales ticket records generated from Aloha data include:
Receipt number
Date
Server
Service type/revenue center
Guest count
Menu items, including modifiers
Charge tips
Auto gratuities
Payments
Discounts
Credit card fees
Voids
Paid outs and paid ins are imported to R365.
Deposits entered in the POS are imported to R365.
Labor Data
When labor data is imported, R365 creates employee-related records derived from POS data. Learn more about Labor integrations.
Click to expand for additional information.
POS employee records are created in the next polling cycle after an employee is added to the POS whether or not they have clocked in.
If a new Aloha employee needs to be imported immediately, repoll the latest DSS.
Employee records created from Aloha include:
First, middle, and last name
Mailing address
Phone number
Employee ID number
Hire date
Active/terminated status
Job records created from Aloha include:
Job title (short name)
Job code (ID number)
Pay rate
Labor details created from Aloha time punches are polled with a 16 day labor lookback window to capture updates made in the POS after the initial import.
This means that changes made in Aloha to labor data from the last 16 days will automatically import with the next regular polling cycle, or by repolling a DSS within the lookback period for a date after the adjusted business day.
For example, if a shift from Monday is edited in Aloha on Tuesday, the shift in R365 will automatically update on Wednesday when the DSS imports, or by repolling the Monday DSS.
Labor polling includes tip reduction data by default.
An alternative polling configuration can be applied when data is not importing as expected. Learn more about alternative polling configurations below.
Declared tips are not imported with Aloha labor data by default.
An alternative polling configuration can be applied to import declared tips. Learn more about alternative polling configurations below.
Repolling Data
When changes are made within the POS to correct missing or inaccurate data, the DSS must be repolled in order to transfer the updated data to R365.
If the affected DSS is less than 30 days old, the fastest way to trigger a repoll is to delete the DSS record from the Daily Sales Summary (Classic) page. R365 regularly checks for missing DSS dates, and a deleted DSS will automatically repoll with the most current POS data within about 30 minutes.
For DSS older than 30 days, please contact R365 Support to assist with repolling the data.
Customization
Aloha POS Integration Configurations
R365 Support uses the default polling configuration when setting up a new location. If other integrations exist in the system, R365 will use the same configuration in use at the existing locations.
Click to expand for additional information and images.
The default Aloha configuration imports taxes with the generic name TAX.
The integration can alternatively be configured to import taxes by category.
The default Aloha configuration imports comps and discounts as they are named in the POS.
The integration can be alternatively configured to import comps and discounts by category, or by reason and category.
The following alternative polling configurations are available for Aloha POS:
Name | Description |
|---|---|
Use Mexico Date Format | Enables yyyy/mm/dd format, regardless of the POS server system clock. |
Use Menu Item ID | By default, Item Code is used as the key field when importing menu items. Enabling this setting changes the key field to Menu ID. |
Use PluId With MenuItem Name | Uses the PLU ID as the MenuItemID. |
PLU for Menu ID Value | Enables switching the Aloha-polled PLU used for the POS Menu ID value. The AlohaPlu value determines which column in the Aloha data files is used as the PLU (for example, setting "AlohaPlu": "SKU" uses the SKU column). |
SKU | Specifies the SKU value listed in the config file for data lookups. The AlohaSku value determines which column in the Aloha data files is used as the SKU (for example, setting "AlohaSku": "ID" uses the ID column). |
Modifier Codes | Concatenates modifiers with the reason they were fired, such as Add, Sub, Extra, or No. |
Get Service Type for Check-level | Obtains the service type for the check from GNDSALE data instead of GNDITEM, which is item-level. |
Use Check Count and Guest Count | Counts one check as one guest and ignores the guest count value. |
Include inclusive tax item as line item | Includes inclusive tax as a separate line when the value is set to True. |
Include Void Detail | Includes the void reason in the payment type name (for example, Void – Cashier Error). |
Gift Certificate Sales Tickets | Corrects imports when gift certificate sales appear as balancing adjustments. |
Accept Surcharge and Order Mode Charge | Allows Service Charge and Order Mode Charge to be imported. |
Break Out Order Mode Charge | Creates new sales details for Order Mode Charges and sets the menu item name to the service type. |
Categories for Toppings Modifier | Specifies which topping modifier is used for the topping count. |
Is Topping Count Enabled | Includes topping count. |
Adjust Null Clock Out | Sets null clock-out times to the clock-in time. |
Adjust Time Offset | Negates the time offset that R365 applies by default. |
Security Number as Payroll ID | Sets the Aloha employee Security Number as the R365 Payroll ID. |
Custom Payroll ID Field | Substitutes a custom field into the Payroll ID polling process. |
Use Tip Employee | Sets the employee on the sales ticket to the tip employee. |
Add On Integrations
The Aloha POS integration supports the following add on integrations:
Intraday Polling is an add-on feature that collects current sales and labor data from compatible POS systems every 15, 30, or 60 minutes, depending on the POS system’s capabilities, allowing the Operations Dashboard and R365 Intelligence Dashboards to display real-time performance alongside forecasted values
Data imported through Intraday Polling does not produce a DSS, or update other reports that pull data from the DSS. The DSS will continue to be created as scheduled with the previous day’s complete data to populate these reports.
Schedule Writeback sends schedules that are created in R365 to the POS when published, providing a time frame for employees to clock in for their Scheduled start time. This allows locations to use the schedule enforcement features in their POS system to prevent employees from clocking in early.
The scheduling feature in Aloha must be enabled to use R365 Schedule Writeback. Contact your POS representative to confirm scheduling is enabled.
Schedule enforcement settings are managed in Aloha.
Till Management provides a complete workflow from till monitoring to deposit verification, ensuring cash is properly tracked, balanced, and recorded each day.
Revenue Center Split enables businesses with distinct service areas — such as bars, dining rooms, or patios— to treat each area as a separate location in R365. This allows for more accurate reporting and improved sales tracking by isolating data by service area.
The POS Menu Item Modifier Management POS integration configuration allows for menu items to be created in R365 based on the combination of parent menu items and their associated modifiers.
In Beta
Menu Item Modifier Management is currently in beta and is only available for select POS systems and customers. It is not fully supported across all environments. Contact your CSM for more information.
Connect a Aloha POS to R365
Follow the instructions to Connect a Local Install POS.