--- title: "Revel POS Integration" slug: "revel-pos-integration" description: "R365 and Revel POS integration: connection requirements, data flow, and configuration details." updated: 2026-06-03T22:28:30Z published: 2026-06-03T23:16:58Z canonical: "docs.restaurant365.com/revel-pos-integration" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.restaurant365.com/llms.txt > Use this file to discover all available pages before exploring further. # Revel POS Integration Restaurant365 integrates with Revel 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](/doc/docs/pos-integration-overview). ## Data Transfer from Revel to R365 R365 connects directly to Revel POS's cloud service through an API. Once authorized, data flows automatically into R365. Learn more about [connecting](/doc/docs/vendor-pos-integration-4#connect-a-revel-pos-to-r365) Revel 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 Revel data from the previous business day and creates corresponding records in R365 for financial and operational reporting, including the [Daily Sales Summary (DSS)](/doc/docs/daily-sales-summary). > [!NOTE] > API Limit > > Revel enforces per-location API call limits which may limit the ability to repoll or bulk-import historical data. ### 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**](/doc/docs/pos-sales-integrations). *Click to expand for additional information.* ****Sales ticket** records generated from Revel data include:** - Receipt number (Order ID in Revel) - Date - Server - Service type/revenue center (Order dining option in Revel) - Guest count - Menu items, including modifiers - Tax - Charge tips - Payments - Discounts - Voids - Comment Learn about [alternative polling configurations](/docs/revel-pos-integration#vendor-pos-integration-configurations) which change the way sales data is imported below. - **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**](/doc/docs/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 Revel employee needs to be imported immediately, repoll the latest DSS. ****Employee records** created from Revel include:** - First and last name - Phone number - Email address - Hire date - Payroll ID (External ID in Revel) ****Job records** created from Revel include:** - Job code (Role ID in Revel) - Pay rate (Role wage in Revel) ****Labor details** created from Revel time punches are polled with a **14 day labor lookback** window to capture updates made in the POS after the initial import.** This means that changes made in Revel to labor data from the last 14 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 Revel on Tuesday, the shift in R365 will automatically update on Wednesday when the DSS imports, or by repolling the Monday DSS. - **Declared tips** are imported to R365 ### Repolling Data Revel enforces per-location API call limits which limit the ability to repoll data. Please [contact R356 Support](https://help.restaurant365.net/en/support/home#contact) to assist with repolling the data. --- ## Customization ### Revel POS Integration Configurations R365 Support uses the default polling configuration when setting up a new location. If other Revel 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** Revel configuration **does not** import **Paid outs** which include **"tip"** in the name.** [Contact R356 Support](https://help.restaurant365.net/en/support/home#contact) to import paid outs that have "tip" in the name. **The **default** Revel configuration **does not** import **open, unpaid** or **irregular ticket**.** [Contact R356 Support](https://help.restaurant365.net/en/support/home#contact) to import open, unpaid, and irregular tickets. **The **default** Revel configuration **does not** split **tax rates** by category.** [Contact R356 Support](https://help.restaurant365.net/en/support/home#contact) to import **split taxes** (e.g. liquor tax vs. food tax). **The **default** Revel configuration imports **voids** with the generic name "void."** [Contact R356 Support](https://help.restaurant365.net/en/support/home#contact) to replace the generic void name with the corresponding **EVRC type** in Revel. **The following **alternative** polling configurations are available for **all** POS:** | Name | Description | | --- | --- | | Specify business day start time | Imports data from a specific time forward for the previous business day. | | Trim service type name | Removes double spaces from service type category names. | | Split sales detail | Splits a sales detail into two entries: the original and a new one with a specified name and optional category. | | Use revenue centers | Specifies a list of Revenue Center names to import. For hospitality locations such as hotels and casinos that manage separate facility areas as distinct locations. | | Menu item category override | Maps menu items to a specified category, overriding the POS category mapping. | | Disable deposits import | Disables deposits polling. | | Number of lookback days | Sets the number of days to look back when matching deposits by creation date to the import date. | | Custom payroll ID field | Substitutes a custom field into the Payroll ID polling. | | VSD for actual enabled | Splits shifts that span the start-of-day time and assigns them to their respective dates. | | Allow 24 hour punches | Allows 24-hour shifts to bypass the import filter so the Labor Rules Engine can process them, and enables managers to correct punches for shifts with no clock-out recorded. | | Observes daylight savings time | By default, locations are assumed to observe Daylight Saving Time. Set to `false` for locations that do not observe it, such as those in Arizona. | | Offset time zone | Adds a time zone offset to correct for an inaccurate time zone on the location record. | | Use consolidate API | Sends sales and labor data through two consolidated API endpoints as zipped and encrypted files. | **The following **alternative** polling configurations are available for Revel POS:** | Name | Description | | --- | --- | | Import based on day of payment | Imports Revel transactions based on the day of payment instead of the created day. | | Ignore Revel pickup date | Imports orders on the closed business date and bypasses the Revel pickup date blocking logic. | | VSD prior day | Uses the VSD setting or BusinessDateStartTime for Revel API calls instead of the default 4:00 a.m. start time. | | Block alternate date items | Blocks items that have already been reported on previous business dates when checks span multiple days due to third-party payment updates. | | Import barcode as PLU | Imports the barcode value as the PLU. | | Use Revel subcategory | Includes the category of the product along with its class by using the Revel subcategory. | | Category to use | Uses a numeric value to determine which Revel category level to use, where Class is 1, Category is 2, SubClass is 3, and SubCategory is 4. | | Apply item quantity to modifiers | Calculates each modifier quantity as the base modifier quantity multiplied by the item quantity. | | Use initial price for size modifier | Uses the "initial_price" amount for an item instead of "price" for size modifiers. | | Topping count enabled | Includes topping count values for create-your-own pizza items. | | Categories for toppings modifier | Identifies which topping modifier categories count toward the topping count. | | Modifier item prefix | Adds a prefix to the modifier item name based on the modifier.mod_type value. | | Tax exempt to category | Prepends "TaxExempt" to the Revel sales category for qualifying sales. | | Ignore Revel single-item tax void | Applies the tax amount on partially voided checks and prevents balancing adjustments caused by rounding errors. | | Discount prefix | Transforms each discount payment type to the format "Discount - {discountName}". | | Sales discounts applied to sales tickets | Imports sales discounts applied to sales tickets from Revel into Restaurant365. | | Import house account invoices | Imports house account invoices from Revel into Restaurant365. | | House account payments | Processes house account payments from past Revel orders. | | Extend API timeout | Specifies the number of seconds before the Revel API call stops waiting. | ### Add On Integrations The Revel POS integration supports the following add on integrations: - **[Intraday Polling](/doc/docs/intraday-polling)** 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](https://docs.restaurant365.com/doc/docs/smart-ops-release-operations-dashboard) and [R365 Intelligence Dashboards](https://docs.restaurant365.com/doc/docs/r365-intelligence-creating-a-dashboard) to display real-time performance alongside forecasted values > [!NOTE] > 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](/doc/docs/scheduling-schedule-writeback)** 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. > [!NOTE] > - The scheduling feature in Revel must be enabled to use R365 Schedule Writeback. Contact your POS representative to confirm scheduling is enabled. > - Schedule enforcement settings are managed in Revel. - **[Till Management](/doc/docs/tills)** Till Management provides a complete workflow from till monitoring to deposit verification, ensuring cash is properly tracked, balanced, and recorded each day. - **[Revenue Center Splits](/doc/docs/revenue-center-split)** 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. ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-AZ2U4603.png?sv=2026-02-06&spr=https&st=2026-11-01T01%3A42%3A27Z&se=2026-11-01T02%3A42%3A27Z&sr=c&sp=r&sig=uTLB0ldSPsTEtaZNUBS5u%2Bn7nUcObo2CpRowkyp7tNM%3D) - **[Menu Item Modifier Management](/doc/docs/pos-menu-item-modifier-management) *(beta)*** 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. > [!NOTE] > **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 Revel POS to R365 Follow these steps to connect a Revel POS to R365: *Click steps to expand for additional information and images.* ****1)** Email [partnerconnectsetup@revelsystems.com](mailto:partnerconnectsetup@revelsystems.com) and request the R365 integration to be activated.** In the email, request that Revel send R365 the Revel URL, API Key, API Secret and the Revel Establishment Number for each location. ****2)** Follow the instructions to [**Connect a Cloud POS**](/doc/docs/connect-a-cloud-pos).** If location names are different in R365 and Revel, please provide a list of matching names when filling out the Location Add-On form.