Xenial Cloud supports product-level flags that indicate items ineligible for discounts.
Affected Components:
Data Management (XDM)
Cloud POS (XPOS)
Online Ordering (XOO)
Enterprise Integration and Onboarding (EIO)
Administrators have the ability to configure products and modifiers to enable/disable discounts. Default configuration toggles Discounts On.
Products: → → → → → → →
Modifiers: → → → → → → →
![]() |
When configured in Data Management, Cloud POS does not apply discounts to flagged products or modifiers.
When configured in Data Management, the integrator discount calculator does not apply discounts to flagged products or modifiers.
Updates to product-level and modifier-level properties consumed from Enterprise Data Manager.
The Product Returns feature enables customers to return a previously purchased retail product for a refund or exchange it with another product.
Configure this feature to allow customers to return/exchange products purchased from a different location, or restrict returns exclusively to purchases made at the original location.
Reason codes optionally captured help to determine if the returned product is eligible to add back to inventory.
Perform product returns with or without a customer receipt.
|
|
Affected Components:
Data Management (XDM)
Ordering (POS)
Pipeline (PPL)
Portal/Onboarding (XOP)
Reporting (RPT)
Xenial XUX (XUX)
Enhanced Suite Catering Advanced Day (ADO) and Event Day (EDO) orders for Price Points and Menu Pricing. Xenial Online Ordering automatically populates transaction types, and Improved validation for quantity-based fields.
Affected Components:
Xenial Online Ordering (XOO)
Xenial Cloud Portal (XOP)
Xenial Data Management (XDM)
Xenial User Experience (XUX)
The Xenial Online Ordering API identifies orders originating from Mobile Order Integrators or Kiosk and automatically populates the Transaction Types with the EventID:
PRE_AUTH
SALE
REFUND
Improved the Suite Catering Price Point list:
From the Price Point list, use the Actions dropdown to access Delete option
The Deleted Items view displays deleted Price Points history
A warning appears when attempting to delete a Price Point from Active Events or Accounts
It is possible to restore deleted Price Points
Advanced Day Order (ADO) Price Point field is only visible with an active Suite Catering subscription.
Xenial Data Management improvements for Suite Catering include:
Price Point Name field accepts multiple language characters
Improved Price Point verification workflow of Sites and Events
Advanced Day Order (ADO) fields such as Source and Price Point are only visible with an active Suite Catering subscription.
Events list automatically displays all Active Sites along with their respective Price Point and Advance Day Order (ADO) Price Point fields—removed the Active toggle in the Events editor
Improved quantity-based field validation for Child Item Product Pricing:
Quantity-Based Ranges and Range Sets must contain at least one value
All Range fields must contain a Start value
The End field must contain a value greater than the Start value
Price Rule field accepts overlapping ranges
The Price field requires a value
Improved customer transaction process by enabling consumption of Fortress Loyalty Provider data. Added ability to post a request to void an order from Point of Sale in order to void Loyalty orders. Added functionality to register till in Fortress Loyalty Provider with first gift or loyalty transaction through RegisterUpdateTill request.
Affected Components:
Xenial Gift and Loyalty (XGL)
Xenial Point of Sale (XPOS)
Ensured XGL responds appropriately to POS for locationconfiguration request when using Fortress.
Xenial Point of Sale sends a generic command to identify customer IDs and for available Loyalty rewards attributed to the customer ID to the Fortress Loyalty Provider. Void order requests can also be sent to void a Loyalty order.
Printed content from POS and XKM are translated into the preferred, local language of the site, which is in compliance with local laws.
Affected Components:
Xenial Cloud POS (XPOS)
Xenial Kitchen Management (XKM)
Printers
Print requests sent by POS are translated to the preferred language of the site. Translations include user-defined strings—such as order item names and destination names—and system strings, which include printer and transaction types. The language used in the POS app does not affect the language on the printed receipt.
When POS is required to print two receipts, the merchant copy always prints in the site-preferred language; while the customer copy prints using either the cardholder language—received from the payment processor—or the merchant site-preferred language. Either way, the customers will fully understand the content of their receipt.
Printed content from XKM—such as bump chits and item label—appears in the preferred language of the site.
Optimizations for the Retail ordering experience:
Optimize Order Ticket header for Retail transactions
On-screen receipt displays Retail item descriptions
Product Lookup specifically for Retail Items
Optimize display details of Product Detail screen
Order History optimizations for retail (columns, filters, search criteria)
Keyboard use permitted for all keypad inputs
Affected Components:
Xenial CLoud POS (XPOS)
The following XPOS UI changes support Retail Services.
Change Quantity button appears on the Item Action Bar:
![]() |
Item Detail screen:
![]() |
Useful Retail information displayed on Order Ticket:

Product Lookup for Retail Items:
![]() |
Added permissions in the Xenial Data Management settings to view, manage, and delete dm-document-external-reference. documents. Improved the workflow for Xenial Data Management, Xenial Point of Sale, Xenial Point of Sale Shell, and Xenial Online Ordering for receiving large payloads.
Affected Components:
Xenial Data Management (XDM)
Xenial Point of Sale (XPOS)
Reports
Xenial Online Ordering (XOO)
Added permissions in the Xenial Data Management settings to view, manage, and delete dm-document-external-reference. documents and improved the workflow for XDM when receiving and filtering large payloads.
Improved the workflow for XPOS and XPOS Shell when receiving and filtering large payloads.
Improved the workflow for Xenial Reports when receiving large payloads.
Improved the workflow for XOO when receiving large payloads.
→ → →
The purpose of the Yellow Dog integration is to utilize and integrate the Yellow Dog API to update the Xenial Data Management product list retail items. Item orders and returns processed through Xenial Point of Sale are sent to the Yellow Dog service to update stock levels. Xenial Data Management syncs with Yellow Dog hourly. Credentials utilized in the Yellow Dog Integration Service are encrypted per Yellow Dog requirements.
Added permissions sub-groups for retail service with options to enable/disable a User Role to Add, View, Manage, and Delete.
Affected Components:
Xenial Cloud Portal (XOP)
Xenial Data Management (XDM)
Xenial Pipeline (PPL)
Xenial Operations XOPS)
Administrators have the ability to configure permissions for retail items. The following permissions sub-groups were added in the Data Management Admin page. Permissions include the ability for users to Add, View, Manage, and Delete.
→ → → → → → → →
Product -
![]() |
Retail Item
![]() |
Gift Card
![]() |
Gift Certificate
![]() |
Allergens
![]() |
Note
The Retail, Gift Card, Gift Certificate, and Allergens sub-groups inherit the status of the Product sub-category.
Added the following permissions to the Pipeline and Portal groups. These permissions are Global Level and Allowed for admin roles by default.
→ →
Pipeline Group Permissions
Name | Description | System Name |
---|---|---|
Data Import Start | Process for importing data from external systems to the Pipeline group. | DataImport.Start |
Data Import Status View | Permission to receive the status of the data import job in the Pipeline group. | DataImportStatus.View |
Portal Permissions
Name | Description | System Name |
---|---|---|
Decrypt YellowDog Credentials | Permission to view encrypted user credentials from Yellow Dog. | Subscription.YellowDog.Decrypt |
Xenial Data Management syncs with Yellow Dog hourly.
The Minor Reporting Category field in Product Configuration displays an error and disables the Done button when the Minor Reporting Category field is empty.
Xenial Data Management syncs with Yellow Dog hourly. Tags that are imported from Yellow Dog external carts are imported to the Xenial Data Management Tag section with the Tag ID, External ID, and Description fields filled out if applicable.
Exporting and Importing - Added Retail Item to the Product Type column. Exporting the Price List notates Retail Items in the Item Type column. The Import Summary pop-up displays the count of Retail Items.
Bundle Components - Updated the Bundle Component filter to include retail items and show, sort, and filter the Product Type column.
External Bulk Payloads - Updated the workflow in Data Management to process external bulk cart payloads.
Product Prices - Updated the default value for the Open Price field under the Price section of a product to Off. This field is not marked as required.
Conversions - Updated the Conversion section of Retail items to allow users to manipulate the conversions.
Product Variations - Improved the cart implementation in Product Variations to allow users to modify complex fields.
Portal - Updated Portal workflow to prevent the deletion of the Tax Group, Major Reporting Category, Minor Reporting Category, and Image Set entities when utilized in the Yellow Dog Integration service.
Product and Pricing Updates - Added Retail Item to the Item Type field for Products and Product Type columns in the Product and Pricing Updates tables. Exporting the Price List notates Retail Items in the Item Type column. The Import Summary pop-up displays the count of retail Items.
Improvements to Xenial Pipeline to integrate with the Yellow Dog service.
Syncing - Activating Yellow Dog Integration triggers a data sync. Xenial Data Management syncs with Yellow Dog hourly.
Data Management - Improved workflow sends a status notification upon cart deployment as either a success or a failure. Upon receiving the notification, the Mango status document is updated to reflect the status.
Imports - Verified Yellow Dog Integration workflow imports an item with the name Not Specified along with the Product ID number when the item does not have a name.
Data Management Returns - Updated Data Management Returns fields to adhere to requirements for the Yellow Dog integration. Updated the Yellow Dog url expands on images.
Mange Status Messages - Improved Mango status messages display the details of the error. The following errors have been defined:
Extract failed due to an authentication or extract data issue.
Transformation failed or a cart has errors.
Create Carts with Data Mana failed or a cart has errors.
Cart Deployment failed or a cart has errors.
The update is stuck at XWS level.
The update is stuck at Data Management level.
Created necessary permissions and environments for Yellow Dog integration.
New Retail configuration allows clients to designate and identify products eligible for shipping or pick-up at an alternate location.
Affected Components:
Xenial Portal (XOP)
Data Management (XDM)
Cloud POS (XPOS)
→ → →
Permission required to mark a product as eligible for shipping.
![]() |
→ → → → → →
Access the Fulfillment Method configuration through Xenial Data Management:
From Data Management, navigate to Ordering Settings then select Product List.
From the Product List, select a product.
To the left, from the Product menu, select Availability.
From the Availability options, scroll to Fulfillment Methods.
Select a Fulfilment Method of Shipping, Pick Up Later, or In-Store Purchase.
From the upper-right, select Save.
![]() |
When configured, the Cloud POS Actions Bar displays a Shipping/Pick Up option.
![]() |
Manager approval required to proceed to customer identification and address verification.
Access configurations through
→ →New sort option available for Condition column, labeled Error
Use filters to view discrepancies in shift/work time
Delete or edit times with detailed notes
Available permissions for
Staff.PunchEdits
are Edit and DeleteUpdated reporting process flow to ensure accurate business date
Affected Components:
Xenial Cloud Portal (XPOS)
User Interface/Experience (XNU)
Reports (RPT)
Use filter to view discrepancies in shift/work time and ability to delete or edit entries with a note. New sort condition, labeled Error.
![]() |
Reporting process flow includes data tests to ensure accurate business date.
Timekeeping enhancements in the following areas: improved clock-in/out focusing on processes where connectivity is lost and then restored, improved messaging in cases where XPOS is unable to communicate with XBO, XPOS respects Employee Job Code which enables the Payroll engine to process employee records, and streamlined data consumption for Reporting so that Payroll Details are available within 10 minutes of generation.
![]() |
Affected Components:
Xenial Point of Sale (XPOS)
Xenial Cloud Staff
Xenial Back Office (XBO)
XPOS verifies employee job status with Xenial Back Office upon login to XPOS, shift clock-in, and upon use of manager credentials for Manager Override prompts. The clock event warning message relates instructions unique to the specific event (ClockIn/Out or Break Start/End). Manual acknowledgement of the message is required before proceeding.
Designed warning message modal for XPOS to display in the event of intermittent connectivity during clock events.
Adjusted Timeclock logic to recognize if an unregistered clock event exists—due to connectivity issues at the site—and to create a clock event in its place. Note that at this time functionality is limited to only the most recent unregistered clock event. If extended connectivity issues persist, site managers must manually input other clock events.