Xenial

order-capture-floor-plan-editor

Shortfall: Table Service documentation covers table mapping, table status, enable/disable table and host mode, and a "Floor Plan" resource appears in the POS Data Management API operation definitions — so floor plans are a first-class object. But no graphical multi-layout editor and no server-section assignment is documented. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/modifier-groups.html · retrieved 2026-08-02

order-capture-split-merge

Docs cover order split/suspend, Split Payment, and Move Party to Another Table. Even N-way, arbitrary-amount split and post-partial-payment merge not documented. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

order-capture-native-handheld

A native POS app installs on Android and iOS handhelds from the public app stores, with per-terminal configuration download — a documented install procedure, not a marketing claim. Separately, an AI-first Genius handheld was unveiled in mid-2026; that is an announcement rather than shipping evidence and is scored at hardware-handheld-purpose-built. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-pos-app/install-pos.html · retrieved 2026-08-02

order-capture-offline-order-entry

Shortfall: the only concrete statement is App Store marketing for the Xenial Shell / Cloud POS SKU — "If the internet goes down, your local Xenial apps keep running the store and sharing order information for up to 30 days." That is the SMB packaging, not Genius for Enterprise. The enterprise POS Online/Offline Data Flow chapter exists and separates "Loss of Internet" from "Loss of LAN", but its body text is not publicly retrievable, so no documented offline order-entry behaviour exists for the enterprise product. Downgraded from yes for consistency with the other offline cells, which the 2026-08-01 verification pass had already reduced on this same source. https://apps.apple.com/us/app/xenial-shell/id1463045984 · retrieved 2026-08-02

order-capture-kiosk-first-party differentiator

First-party kiosk hardware+software is a named product line (Nextep Systems, now Global Payments). ADA/accessibility conformance not published. https://geniusforenterprise.com/home · retrieved 2026-08-02

order-capture-drive-thru

Order-point / pay-window / pickup-window separation is documented as the product's data model, not as a slogan: the Virtual Drive Thru shows "Menu Board (single or double-lane) Pay Window Pickup Window Vehicles waiting in line", and Vehicle Indicator Bubbles carry Greet Time, Pay Window Time and Pickup Window Time per segment. Separation extends to the POS itself: "Some Drive Thru terminal scheme configurations require an order be paid at one terminal and served at another terminal", enabled by the terminal-scheme setting Show Unfulfilled Paid orders, with Pay and Serve buttons on the Drive Thru screen. Dual-lane is supported ("single and dual-lane drive thrus"; GPIO channels 0 Menu board 1 and 3 Menu board 2). Pull-forward or parking-spot assignment is still not documented anywhere in the tree. RE-CITED 2026-08-08: path moved from /en/drive-thru-director/the-main-screen-overview.html. CORRECTION WITHDRAWN: the 2026-08-02 pass removed a "Vision system that automates order start, maintains order sequence, and improves throughput with minimal staff input" quote as uncorroborated; it is in fact verbatim first-party text on genius-drive-thru.html ("Genius Drive Thru integrated Vision system automates order start, maintains order sequence, and improves throughput with minimal staff input"). It is module-overview prose with no configuration or behaviour documented behind it, so it is recorded but not relied on. https://www.xenial.com/product-documentation/en/genius-drive-thru/the-main-screen-ui-overview.html · retrieved 2026-08-08

order-capture-drive-thru-timers

Drive Thru Director models the lane as measured segments and publishes its own arithmetic. Goals and Metrics: "Each segment of the drive thru has a specific speed of service goal typically set by the parent brand"; "The average speed of service is determined by adding vehicle wait-times, then dividing by the number of completed drive thru events", reported per segment per daypart and for the whole day. The Main Screen UI Overview names the segments "Menu Board, Pay Window, Pickup Window" (plus optional Greet Time, defined as "the length of time between vehicle detection at the menu board and the activation of the drive thru team headset"). Tied to individual orders by the Transaction Report, which "analyzes individual transactions for the selected date" with columns Menu Time, Line Time, Pickup Time and Total Time, and by the matched-pair rule that "A completed drive thru event must have a menu board event and a pickup window event". RE-CITED 2026-08-08: the previously cited /en/drive-thru-director/ path is gone; this tree is now /en/genius-drive-thru/ and fetches 200 with body text in the raw HTML, so the old 'indexed but 404' caveat no longer applies. The earlier note's quote "typically set by the Parent Company" was not verbatim and has been corrected. https://www.xenial.com/product-documentation/en/genius-drive-thru/goals-and-metrics.html · retrieved 2026-08-08

order-capture-voice-ai differentiator

Shortfall: the only evidence is two sentences of marketing copy — "Patent-pending voice assistant technology gives better results, faster, because it uses three leading natural language processors" and "Speech-to-text can be injected into the POS to automate ordering". Conditional phrasing, patent-pending, no GA statement, no named brand deployment, and no voice-ordering topic anywhere in the product-documentation or developer-resources trees. Regraded B to D: a product marketing page is grade D, not documentation. https://www.xenial.com/products/drive-thru-controller/ · retrieved 2026-08-02

order-capture-throttling differentiator

Online Ordering Settings has a Kitchen Capacity Management section: "Enable Kitchen Capacity Management - Toggle On to define a maximum number of online orders a store accepts within a 15-minute time period" plus a "Number of Orders per 15 Minutes" field, so a per-time-slot capacity cap is real and configurable. Shortfalls: the cap is a single setting scoped to the Online Ordering subscription (company web site and mobile app) with no per-channel/per-order-source limits, and no automatic quote-time or pick-up-time extension is documented when the threshold is crossed. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/online-ordering-settings.html · retrieved 2026-08-08

order-capture-scheduled-orders

Shortfall: one company/site-wide lead time, and the delayed fire applies to kitchen PRINTING only. Future-dated ordering is native to the core POS, not just the catering add-on: orders carry a Pickup Date/Time, the POS Open & Suspended screen has an "Online Orders lane" whose orders "are sorted by Pickup Date/Time in ascending order", and Company Preferences | Kitchen Settings exposes "Kitchen Lead Time for Future Orders (seconds) - Type the number of seconds before the defined Pickup Date/Time to send a future order to the kitchen. Set to 0 to send the order when the Pickup Date/Time is reached", paired with "Delay Sending Future Orders to Kitchen" (Yes/No, also settable per printer with Inherit Site Settings). That is a computed fire time. But the lead time is a single value defined for the company or site, not per channel or per order source - order sources get only a send Timeout, not a lead time. And the vendor states the limitation itself: "Currently, the point of sale (POS) forwards future orders to the Kitchen Video Screen immediately upon receipt, so items in such orders have a submitted fulfillment_status prior to when they display in the kitchen" - so the delay governs the printed chit, not the KDS make queue. RE-EVIDENCED 2026-08-08: the previous citation (Suite Catering getting-started) is a dead URL and was the wrong module for this claim. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/preferences/company-preferences.html · retrieved 2026-08-08

order-capture-catering

Shortfall: the catering flow is venue/suite catering, not restaurant catering, and it is a separate add-on product. Suite Catering "is a venue-focused cloud service accessed through the Portal. It allows venue staff to manage suites, accounts, advanced day order and event day order workflows, and their associated business processes", and the module overview adds that it lets venues "display a calendar of events, accept orders for food and beverage prior to an event, add additional items to orders during an event, and to settle payment for consumed food and beverage after an event". The documented tree does cover much of what the claim asks for: an event schedule separate from the order queue (Events, Event-Attendant Suite Assignment, Event-Suite Reassignment), balance and settlement handling (Invoice, Add/Edit/Refund Payment, Pre-Auth History, House Account / Genius House Account invoice payment types), and production planning (Production Report, Par Stock Report). What is absent for a restaurant brand is the quoting half: no catering quote, deposit percentage, lead-time or delivery-window, and no catering minimum is documented; ordering is bounded by advanced-day vs event-day windows against a venue event. RE-CITED 2026-08-08: tree moved from /en/xenial-suite-catering/ to /en/genius-add-on-products/suite-catering/. The prior note's quote ("a venue-focused Xenial Cloud service that allows venue staff to ...") was not verbatim and is corrected above. https://www.xenial.com/product-documentation/en/genius-add-on-products/suite-catering/suite-catering---getting-started.html · retrieved 2026-08-08

order-capture-order-ready-signal differentiator

Shortfall: no named marketplace consumer. The Notification service's Order Notification format "provides customers and integrators the ability to subscribe to order updates that indicate when the order status changes"; "The subscription is enabled using Amazon Simple Queue Service (SQS), and the type of the subscription can be defined by the integrator, such as Short Message Service (SMS), email, or push notifications", against a per-company topic "arn:aws:sns:{region}:{source_owner}:proda-pos-notifier-{company_id}". The enumerated notification types include Order Ready and Order Fulfilled; Sample 12 carries "notification_status": "order-ready" with "fulfillment_status": "order_ready", and Sample 14 shows the live envelope with "subject": "XENIAL Notification:order-ready" and an "order_source_ext" block containing "is_marketplace": false alongside "is_ado" and "is_tax_liable" - so the event pipeline is marketplace-aware at the order-source level. But no page states that this event reaches DoorDash, Uber Eats or Grubhub, or any third-party marketplace by name; those appear only in the Genius Integration Partners list as delivery/online-ordering integrators. It is a generic integrator pub/sub contract, not a documented marketplace callback. RE-CITED 2026-08-08: the previous URL had a duplicated path segment and 404s; this is the live location and the body text is in the raw HTML. https://www.xenial.com/developer-resources/en/genius-point-of-sale/enterprise-pos/notification/message-formats.html · retrieved 2026-08-08

order-capture-void-comp-controls

Manager Procedures cover refunds, discounts, employee admin and POS reporting. Mandatory reason codes and a dedicated exception report not documented. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

menu-pricing-nested-modifiers

Modifier Groups, Modifier Builds, Default Builds, Quick/All Builds documented. Three-level nesting depth and per-level min/max/forced flags not confirmed. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/modifier-groups.html · retrieved 2026-08-01

menu-pricing-modifier-price-by-parent-size

The Modifier List Pricing page documents Child-Item Pricing Rules — 'Specify modifier price when ordered as child item'. A single modifier record carries a priority-ordered rule list; each rule names Parent Items (Products) or Parent Items (Tags) ('when the product is ordered as a child of any of the selected products, the child item pricing rule is applied') with a Replace / Amount / Percentage price adjustment, plus optional order-source, price-point, destination and quantity-range conditions. Sizes are separate product variation records ('define variations for a product to allow each of its sizes, associated meals and other variant types to be sold and tracked' — Variations/Conversion pages), so a per-size modifier price is a rule keyed to that size's product: one modifier, no duplication. It is a rule list, not a literal grid UI. RETRIEVAL CORRECTION: this page's body text IS served in the raw HTML inside the #topic-content div — the record's earlier 'body text is client-rendered, direct fetch returns navigation only' caveat is an artifact of fetch converters drowning in the 1.2MB navigation tree, not a property of the site. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/modifiers/pricing.html · retrieved 2026-08-04

menu-pricing-topping-quantity-tiers

Shortfall: fractional modifier quantities are genuinely documented — an "Allow Modifier Quantities to Change" toggle enables a +/- rocker that increments "by the specified increment value", with a long-press popup offering fractional options, and the fractions print "on kitchen tickets and in the preparation instructions". Split Modify covers cases like "half the standard serving of relish, or one third the amount of mayonnaise". But this is SERVING quantity, not a priced tier: no per-tier price multiplier and no per-section (half-and-half) placement pricing is documented. Direct fetch of xenial.com/product-documentation returns the navigation tree only (body text is client-rendered); the quoted text is from the public search index of this page. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/modifier-groups.html · retrieved 2026-08-02

menu-pricing-size-style-matrix differentiator

Product Variants and Variant Builds documented — a variant build mixes product variants with different modifications and quantities. Two-axis grid with per-cell price override not confirmed. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/product-variants.html · retrieved 2026-08-01

menu-pricing-included-allowance differentiator

Two documented mechanisms. (a) Quantity-Based Pricing on the Child-Item Pricing Rule (Modifiers > Pricing, and the Pricing Rules section of Product List > Price): "Pricing by Quantity - Select Add Range... Start Lowest product quantity in range, End Highest product quantity in range, Price Adjustment: Replace / Amount / Percentage", with an "Include Build Items" toggle deciding whether default build modifiers count toward the quantity - i.e. the first N modifiers can be priced at zero and only overage charged, automatically. (b) Menu Genie 'Select Many of NE Check' templates carry an explicit included quantity and maximum quantity: "The normal modifier of each button is added to the order until the included quantity is reached. The extra modifier or the chargeable modifier is added to the order for each button selected after the included quantity is reached", and buttons grey out once the maximum is met. Substitution handling is configurable on Modifier Builds: "Subtract Price on Modifier Removal" and "Subtract Price on Modifier Replacement" toggles decide whether removing or swapping an included modifier credits the build price. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/modifiers/pricing.html · retrieved 2026-08-08

menu-pricing-combos

Combo Meals, Add Combo Meal to Order, Change Combo Meal Size, and Convert Item to Combo Meal — the last is exactly the a-la-carte-to-combo conversion required. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

menu-pricing-upsell-prompts differentiator

AI upsell recommendations rendered on drive-thru menu board/OCU with claimed 2% LTO and combo lift. Per-item/per-channel configuration and attach-rate reporting not documented. https://www.xenial.com/products/drive-thru-controller/ · retrieved 2026-08-01

menu-pricing-86-propagation

Item Availability is a documented Manager Function. Cross-channel propagation scope and latency not published. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

menu-pricing-countdown-auto-86 differentiator

Re-checked 2026-08-08 against the full two-portal dump of xenial.com (product-documentation 786 pages and developer-resources 293 pages). Item 86ing is documented and manual only: Enterprise POS App > Manager Procedures > Item Availability enumerates the three ways to flag an item (Functions > Item Availability, long-press at Order Entry, Product Details Available toggle) and Genius Mobile Manager > Items has an on/off availability toggle - none carries a count, a decrement-on-sale behaviour or a restore schedule. The Menu Engine out_of_stock flag is explicitly set by staff, not by depletion ("Integrators do not set the value of out_of_stock directly; instead, the employees at the point of sale change the availability status"). Quantity On Hand exists only in the Venue Inventory add-on (stand worksheets, inventory counts) and in Classic Chef's Minimum On-Hand Quantity for cook-list targets; neither is documented as driving POS auto-86 at zero. 'par count', 'auto-restore', 'sold out' as a state and 'auto-86' return nothing. No page enumerates the item-availability mechanisms as exhaustive, so this stays unknown rather than no.

menu-pricing-dayparting

Shortfall: menus and prices are schedulable, individual items are not - a product's own Availability page offers site, order-source, age and fulfillment-method controls but no time period, so an item can only be dayparted by moving the whole menu it sits on. What does exist is first-class: a Time Period record takes "Days of the week when the time period is active", "Start time", "End time", "Start date" and "End date", with an overnight rule ("if the Start time for Tuesday is 10:00 PM and the End time is 3:00 AM, the parameter is recognized as spanning Tuesday and Wednesday"). The Menu editor's Availability page then defines "availability restrictions by time period" (Allow Time Periods Restriction), and Pricing Rules take Time Period conditions - "Only apply pricing rule during specific time periods", with a stated tie-break: "If an order is entered during one time period and tendered in another, the product pricing for the time period when the order was entered is used." On timezone: each site is created with its own "Time Zone" field (Enterprise Portal | Sites | Create Site), but no page states explicitly that time periods are evaluated in site-local time. RE-EVIDENCED 2026-08-08: the previous citation (Digital Menu Board Schedules) is a dead URL and scheduled signage content, not menu or price activation; the note's claim that per-item price windows are undocumented was wrong. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/time-period.html · retrieved 2026-08-08

menu-pricing-channel-price-books

The Pricing Updates editor's 'Edit Pricing Rules' function documents Order Source Conditions as a first-class rule dimension: 'Only the Following - Only apply pricing rule to specific order sources', combined with a Price Adjustment of Replace / Amount / Percentage against the standard price. Order Source is itself a configurable object (Mobile App, Website, POS Terminal, DMB, per order-source.html) with a documented 'Injected Order Options' page for orders arriving through third-party injection. This is a rule-based percentage-markup pricing engine keyed to channel, matching the claim; it is a conditional rule list rather than a literal 'book' UI, and whether each individual third-party marketplace is separately selectable as an order source (versus one generic 'injected' bucket) is not confirmed. Retrieved from the product-documentation full-text search index. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/pricing-updates.html · retrieved 2026-08-04

menu-pricing-dual-pricing differentiator

Re-checked 2026-08-08 across the whole published surface of both xenial.com portals (product-documentation and developer-resources, 1,079 pages / 7,250 sections). 'dual pricing', 'cash discount', 'point of sale', 'P2PE'-style tender-priced menus: 'dual pricing' and 'cash discount' occur zero times. The three surfaces where it would live were read field by field: Fees > Automatic Fee (General / Availability / Qualify Criteria / Apply Criteria pages - conditions are order source, destination, event type, product tags and item sources, with no tender or card-type condition), Product List > Price (Pricing, Price Points, Pricing Rules whose conditions are order source, destination and price point, and Child-Item Pricing Rules), and the Discount List editors (availability by POS screen, automatic application, loyalty). The one tender-aware construct anywhere is a developer-side Omni Order Discounts filter, tender_tags with a condition scope of "tender" - a building block for a cash discount, not a documented dual-price model with the card price as base across POS, kiosk and online and both totals on the receipt. Unresolved: the pricing-mode surface is not enumerated as exhaustive, so this is absence of evidence.

menu-pricing-versioning-effective-dates differentiator

Data Management > Packages is the staging mechanism: "The Packages feature enables administrators to deploy a collection of Data Management updates together in a package. Sites are updated immediately upon deployment of the package -OR- on a scheduled date." Create Package exposes "Toggle Schedule Changes to On. In the Effective Date field, type the deployment date"; changes are attached from any Data Management editor via Add to Package (an orange package icon marks every changed field and record), reviewed with View Package Details before deploy, and a scheduled deployment can be cancelled with Stop Package / Force Stop Package. The Menu Engine API takes the same parameter (PUT /menu?effective_date=...). Shortfall: no rollback to a prior version after publish. Settings and Tools > Change History gives version history and a side-by-side new-vs-historical JSON compare, but its actions are View Version and Compare only - there is no restore; the only revert documented anywhere is Sites > Revert Copy, available for 24 hours after a site-to-site configuration copy. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/packages.html · retrieved 2026-08-08

menu-pricing-franchise-hierarchy differentiator

Central records with per-site override at field level. Data Management | Ordering Settings | Pricing Updates is the corporate menu-price editor: it can "Edit Price" for a product across the estate, "Set Site-Specific Pricing - Define product price that is specific to one or more sites" (a View and Edit Price form with a row per site and an All Sites row), "Edit Pricing Rules - Define product pricing rules when certain conditions are met" and "Edit Child-Item Pricing Rules", with a Select Sites filter at the top and changes stageable via "Add Changes to Package". Pricing rules carry Replace / Amount / Percentage adjustment plus roll-up handling, conditioned on Order Sources, Time Periods, Price Points and Destinations. The field-level governance is the globe control that recurs throughout the Data Management and Portal editors - "Multi-site users: To the right of the field, select the globe icon to define values for each site" (seen on menu availability, product availability, kitchen screen settings, bump bars, currency scheme, labor matrix, event price points), i.e. any single field on a company-level record can be given per-site values. Sites are organised by Enterprise Portal | Settings and Tools | Site Hierarchies: "define a hierarchical relationship between sites in the company", where "User permissions to view reports and edit site settings are based on the respective level of the site in the hierarchy", and hierarchies feed the Site Selector used by the Data Management editors. RE-CITED 2026-08-08: path moved from /en/xenial-data-management/ordering-settings/pricing-updates.html; the destination now fetches 200 with body text in the raw HTML, so the earlier 404 caveat is withdrawn. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/pricing-updates.html · retrieved 2026-08-08

menu-pricing-allergen-nutrition

Shortfall: nutrition values are manually entered, not recipe-derived, and publication to online ordering/third-party menus is not documented. What IS documented: a per-product Allergens page ('define the allergen content of the product' with Contains / May Contain / Does Not Contain per allergen, plus a separate Allergens object with a POS-display icon) and a per-product Nutrition page ('specify the required nutrition details about the product', entered 'as Values' or 'as a Range', e.g. '12 milligrams of Calcium'). Both exist at the modifier level too (modifiers/allergens.html, modifiers/nutrition.html). No page states these fields flow through to Online Ordering or to Deliverect-connected third-party menus, and no recipe-component linkage for auto-derived nutrition is documented (the record's recipe-linkage cell is itself only partial). Retrieved from the product-documentation full-text search index. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/product-list/create-product/nutrition.html · retrieved 2026-08-04

menu-pricing-recipe-linkage differentiator

Downgraded from yes on 2026-08-02 verification. Shortfall: no documented recipe module. The Back Office Food navigation enumerates Inventory Counts, Orders, Purchases, Product Mix and Sales/Misc with no Recipes entry, and /en/genius-back-office/food/recipes.html returns HTTP 404. What exists is a "Recipe Venue" resource in the POS Data Management API operation list plus grade-C marketing ("Powerful food cost and inventory tools slash cost and waste; food cost variance accurate to the ounce"). Ingredient quantities and yields bound to a sellable menu item are not documented anywhere retrievable. The prior note quoted a phrase, "standardized recipes with precise ingredient measurements", that could not be located on any Xenial page. https://www.xenial.com/product-documentation/en/genius-back-office/food.html · retrieved 2026-08-02 adversarially verified

menu-pricing-3p-menu-push

Enterprise Portal > Settings and Tools > Company Settings configures "Food Delivery Services (DoorDash, GrubHub, Uber Eats)" as first-party services: "Toggle on the delivery services used at the company", with a Delivery Service URL, an optional Callback URL described as "The Menu Engine link for Web site validation", and an Order Source to associate with the provider. DoorDash is a direct certified path - "DoorDash Self-Service Integration: Genius manages integration (tokens, subscriptions, test stores) and monitors integration health in real-time via the new self-service DoorDash Developer Portal", with site activation from the DoorDash Onboarding section. Menus reach the marketplaces through Xenial's own Menu Engine API (PUT /menu with effective_date, order_source_ids and a callback url), not a middleman, although Deliverect and Checkmate are also listed partners. Shortfall: nothing documents per-item sync status or item-level rejection errors surfaced to the operator - the only monitoring named is integration-level health in the DoorDash developer portal, and Menu Engine error handling is documented for the integrator, not in the Portal UI. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-portal/settings-and-tools/company-settings.html · retrieved 2026-08-08

menu-pricing-dynamic-pricing

Product List > Price documents rule-based automatic pricing: "Pricing Rules - Define rules for how a product is priced when certain conditions are met. For example, define a rule to charge a different price based on time period or order source." Rule conditions are Order Sources, Destinations and Price Points, with Replace/Amount/Percentage adjustments and a drag-ordered priority list; Time Periods are a first-class entity whose period_type array includes "pricing", so dayparted prices apply automatically. Price Points add event-driven pricing ("charge a different price... during special events, such as a football game"), assigned via the Events and Event Type editors. Shortfalls: nothing varies price by real-time demand - 'demand pricing', 'surge pricing' and 'dynamic price' occur nowhere in either portal - and the rule form has no floor or ceiling guardrail (the only cap in the pricing surface is the Maximum Amount field on a percentage-based fee, and Price Cap is a legacy Classic Portal price-group feature). https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/product-list/create-product/price.html · retrieved 2026-08-08

payments-processor-choice differentiator

Data Management > Ordering Settings > Peripherals opens "Use the Peripherals editor to create the following peripheral types" and then tables them exhaustively. The payment schemas are: Payment General Device (Bluetooth/LAN/OPOS), Custom Payment Device (Bluetooth/LAN/OPOS), BAMS (FirstData) (LAN/OPOS), FreedomPay (FreedomPay SDK), Genius, Global Payments Payment App (GP Pay App), Moneris (LAN), TranSend (LAN/OPOS) and Verifone (Bluetooth/LAN). Each carries its own processor credentials - the FreedomPay device takes a FreedomPay Terminal ID and requires the FreedomPay company service, the Moneris device takes a Merchant ID "used with the Portal Moneris service" - and each peripheral has a Payment Platform dropdown to "select the processing application used by the device". Company Settings separately provisions Citcon and FreedomPay as services. So the POS is documented as running on named third-party processors and gateways, not only on the parent company's in-house rails; a Custom Payment Device schema exists as well. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/peripherals.html · retrieved 2026-08-08

payments-published-rates differentiator

No card-processing rate published for Xenial or Genius for Enterprise on any vendor property.

payments-dual-pricing differentiator

Re-checked 2026-08-08 against both xenial.com portals in full. 'dual pricing' and 'cash discount' occur zero times in 1,079 pages. The surfaces that would carry a second stored price were read in full: Product List > Price (Pricing, Price Points, Pricing Rules, Child-Item Pricing Rules) has exactly one Price field per price point and no tender dimension; Fees > Automatic Fee's four configuration pages condition a surcharge on order source, destination, event type, product tags and item sources, never on tender or card type; the Discount List editors expose availability by POS screen and automatic application, not tender. Receipt configuration (Site/Company Preferences printing settings, header/footer templates) has no dual-total option. The nearest construct is the developer-side Omni Order Discounts specification, which has a tender_tags filter and a condition scope of "tender" - enough to build a cash discount, but not a documented dual-price mode printing both totals. Unresolved rather than absent: no page enumerates the tender-pricing surface as complete.

payments-surcharge-guardrails differentiator

The Fees editor is the surcharging engine ("apply an automatic 5% surcharge on all product transactions") and the Automatic Fee page enumerates its entire configuration surface page by page - General, Availability, Qualify Criteria, Apply Criteria. Per-location control is documented: Availability > Active Status toggles the fee per site ("select the globe icon to define values for each site"), and amount/percentage values are themselves site-overridable. Shortfalls: no card-type dimension exists anywhere in that surface - conditions are order source, destination, event type, product tags, required/disqualifying items, item sources and an Apply to Liability Items toggle - so debit and prepaid cannot be excluded by BIN or product code; and no network percentage cap is enforced (the only ceiling is a free-text "Maximum Amount" currency cap on a Fixed Percentage fee, with "If a value is not defined for this field, then a limit is not set on the fee amount"). 'BIN' appears in the corpus only as a URL used to validate a BIN range for gift/payment service providers, not as a fee condition. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/fees/automatic-fee.html · retrieved 2026-08-08

payments-emv-nfc

Touchless Payments is a named product line; Global Payments supplies the terminals. https://www.xenial.com/ · retrieved 2026-08-01

payments-softpos-tap-to-pay differentiator

Re-checked 2026-08-08 across both xenial.com portals: 'tap to pay', 'tap-to-pay', 'softpos' and 'soft pos' return zero occurrences in 1,079 pages. The place the capability would have to be configured is Data Management > Ordering Settings > Peripherals, whose opening table enumerates every peripheral type the editor can create; every payment schema there is an external terminal (Payment General/Custom Device over Bluetooth, LAN or OPOS; BAMS (FirstData); FreedomPay; Genius; Moneris; TranSend; Verifone), and each has a device page describing a physical reader. The one entry that could be a phone-as-terminal product, "Global Payments Payment App - GP Pay App", is the single line in the corpus that mentions it: it has no configuration page in either portal and 'GP Pay' occurs exactly once. Contactless is documented only as an EMV/NFC card_acquisition value and as terminal hardware specs. Left unknown because the undocumented GP Pay App entry blocks an absence finding.

payments-qr-guest-pay differentiator

QR code contactless payment marketed in the drive-thru context; automatic check closure in POS not documented. https://www.xenial.com/solutions/drive-thru/ · retrieved 2026-08-01

payments-tip-pooling differentiator

Shortfall: no configurable distribution formula. Back Office Staff preferences document a binary 'Tips Allocation Method' setting of 'Individual' or 'Tip Pooling', plus 'Automatic Charge Tips Calculation' ('automatically calculate employee tip amounts based on the respective orders during their shift'), and job codes carry a tip category (Yes/Indirect/No, per reporting-tip-tax-compliance). A Tips Allocation Summary payroll report shows per-employee allocated tips with clock in/out times. But no page documents a configurable allocation rule by hours worked, sales percentage, role percentage or points -- 'tip pool percentage', 'pool distribution' and 'by hours worked' return zero hits -- so pooling is a mode toggle, not the rules engine the claim describes. Retrieved from the product-documentation full-text search index. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/preferences/site-preferences.html · retrieved 2026-08-04

payments-offline-store-and-forward differentiator

Store and forward is a named, configurable facility with both limit types the claim asks for. Ordering Settings > Preferences > Company Preferences, Payments section: "Max SAF Amount - Type the maximum currency amount allowed for Store and Forward (SAF) offline transaction processing" and "Max SAF Transactions - Type the maximum number of pending Store and Forward (SAF) offline transactions to allow at a time"; the same Payments settings are overridable per site in Site Preferences. Per-device controls exist too: the FreedomPay peripheral takes a "POS Floor Limit - the maximum currency amount the merchant agrees to accept in offline mode... Setting the amount to 0 disables Store and Forward (SAF)" and a "Max Days Allowed Offline" (default 5), and the Moneris and other payment device pages carry an "Enable SAF" toggle and SAF Port. Offline transactions are forwarded and approved or declined at batch settlement. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/preferences/company-preferences.html · retrieved 2026-08-08

payments-offline-decline-liability differentiator

Shortfall: the loss-allocation half of the claim is not published. What IS documented, in the FreedomPay payment-device configuration: 'POS Floor Limit — Type the maximum currency amount the merchant agrees to accept in offline mode — the parent brand may set a predetermined default amount. Setting the amount to 0 disables Store and Forward (SAF)'; 'Max Days Allowed Offline' (default 5); Retry Count (default 100); 'Days to Keep Failed Transactions' before deletion (default 30); and 'Decline Replay Timer — the interval (in minutes) to retry a declined replay attempt — default set to 1440'. Company/site Payments preferences add Max SAF Amount and Max SAF Transactions caps, and the Order Payments sales report carries Payment Status and SAF columns (SAF: '"Store and Forward" transactions (i.e. transactions occurred while the PIN pad was offline)'), giving a post-reconnect view of offline transactions and their status. But no page states who bears the loss when a stored transaction ultimately declines — 'merchant agrees to accept' is floor-limit acceptance phrasing, not a liability statement — and no dedicated failed-offline-payments report is documented. CORRECTION to the 2026-08-02 verification note on payments-offline-store-and-forward that 'store and forward appears nowhere on any Xenial property': SAF is documented in detail on the payment-peripheral and preferences pages; that pass predates the raw-HTML retrieval path. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/peripherals/freedompay-payment-device.html · retrieved 2026-08-04

payments-gift-cards

Gift certificates and gift card management documented in Tender Operations; Como and Punchh named as gift and loyalty integration partners. https://www.xenial.com/product-documentation/en/genius-integration-partners.html · retrieved 2026-08-01

payments-house-accounts

House accounts are a first-class platform object: listed as a tender type in POS Tender Operations, and published as "House Account" and "House Account Status" resources in the POS Data Management API operation definitions. Credit limits and statement generation are still not detailed. https://www.xenial.com/developer-resources/en/pos-api---getting-started.html · retrieved 2026-08-02

payments-split-tender

Split Payment and Different Pay Type documented; multiple tenders per check supported. No stated cap found, so the eight-way floor is unverified. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

payments-refund-void-controls

Manager Procedures gate refunds and order history; role/permission model exists in the Portal. An immutable audit log naming the approver is not documented. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

payments-chargeback-tooling differentiator

Re-checked 2026-08-08 across the complete two-portal dump (product-documentation 786 pages, developer-resources 293 pages). 'chargeback' returns zero occurrences and 'dispute' zero genuine ones. The reporting surface was walked directly: Genius Back Office report-manager and kpis, and Enterprise POS > Reporting (Sales Reports, Detailed Settlement Report, Inventory Reports, Employee/Drawer Audit Reports) - none is a dispute queue and none mentions evidence submission. Payments are settled to the processor in batches (Settle Batch, Detailed Settlement Report), which is consistent with disputes being handled in the Global Payments/FreedomPay merchant portal rather than in Genius, but no Xenial page says so. developers., docs., api., help. and support.xenial.com do not resolve, and the Genius API reference is customer-gated behind a per-user 'API Documentation Access' permission, so an in-product dispute dashboard cannot be ruled out from public material.

payments-card-on-file differentiator

Shortfall: documented only inside Suite Catering's guest-facing SuiteSpot portal (stadium/venue account ordering), not confirmed for QSR online ordering, phone orders or in-store reuse. The SuiteSpot Pay Invoice flow documents 'Select Pay by a Saved Card or Pay by a New Card' and an optional 'Save This Card to save the card to the account'. No PAN-storage statement is made (a Gift Card payment method separately routes through the Givex provider, suggesting tokenized processing, but this is not stated for credit cards). No card-on-file capability is documented in the core Enterprise POS, Online Ordering or Back Office trees. Retrieved from the product-documentation full-text search index. https://www.xenial.com/product-documentation/en/genius-add-on-products/suite-catering/suitespot.html · retrieved 2026-08-04

payments-payout-timing differentiator

Re-checked 2026-08-08. Xenial's documentation covers card settlement only up to the batch: the POS Functions list has "Settle Batch - Send credit card batches to the clearing house for settlement", payment peripherals carry a "Batch Timeout Seconds", and the POS reports include a "Detailed Settlement Report - Credit card batch settlement details". Nothing states when funds arrive. 'deposit' throughout Genius Back Office and Cash Management means a counted cash deposit (drawers, skim envelopes, Validate Multiple Deposits), not a card funding event; 'payout' appears once, as a POS cash-payout function; 'funding' never appears in a settlement sense. Deposit timing is a Global Payments merchant-agreement term and no xenial.com page publishes a schedule or a next-day/instant funding option. The previously recorded counter-signal was a single reviewer report, which is not evidence for a capability either way.

payments-multi-entity-routing differentiator

Re-checked 2026-08-08 across both portals. There is per-site payment identity: payment peripherals are scoped to chosen sites ("select the globe to choose specific sites for which this peripheral is active") and each carries its own processor credentials - the Moneris device has a "Merchant ID... used with the Portal Moneris service", the FreedomPay device a FreedomPay Terminal ID - and Company Settings notes that service credentials defined at company level are defaults that a site may override. But nothing in the Portal configures where money lands: 'split settlement', 'settlement account', 'bank account', 'legal entity' and 'remittance' return nothing, the Sites editor covers hierarchy, tags and configuration copy rather than banking, and settlement itself is described only as batches sent to the clearing house. Whether separate MIDs per site translate into per-entity funding is a processor-side arrangement that the documentation does not address, so this stays unknown rather than partial.

payments-p2pe-pci4

Re-checked 2026-08-08 across both portals and the wider xenial.com site. 'P2PE', 'point-to-point', 'PCI DSS', 'PA-DSS' and 'Attestation' return zero occurrences in 1,079 documentation pages; 'tokenization' likewise, though the developer payment-flow pages describe the Genius Payment Interface issuing "a single-use token for PCI compliance" for both authorize/capture and sale flows. The hardware pages under genius-hardware give device-level security only - Verifone terminals "PCI PTS 5.x Approved", Ingenico readers with "AES, TDES-DUKPT, RSA or On-Guard DATA key (SRED), TR39 / PCI PIN 2.0 DATA and PIN certified key management" - which is a PTS-approved reader with SRED, not a PCI-listed P2PE solution. There is no trust centre: no compliance or security page under www.xenial.com/product-documentation, and trust., security., help. and support.xenial.com do not resolve. An AoC supplied to merchants on request would not be published anyway, so absence here cannot settle the claim.

kitchen-station-routing

Kitchen Stations and routing schemes define which stations receive what content while Kitchen runs in that scheme; configurable in Data Management. Packaging caveat: on the smaller Xenial Cloud POS SKU this module is a paid add-on rather than part of the base subscription (per the App Store listing); it is scored here as a documented module of the enterprise Genius platform, where the commercial packaging is not published. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

kitchen-expo-consolidation

"Bump Upstream Screens" is a documented kitchen setting, implying multi-station consolidation. Completion-gating on all contributing stations not documented. https://www.xenial.com/product-documentation/en/genius-kitchen.html · retrieved 2026-08-01

kitchen-course-firing differentiator

Shortfall: no documented hold-then-fire-on-demand action. Courses are a first-class object -- 'assign items to a meal course at the POS to group items by their respective course on kitchen displays and printers' (examples: Appetizer, Entree, Dessert) -- and an order destination's 'Allow Coursing' setting routes each course to a separate kitchen ticket sharing the same order number, with ticket headers optionally color-coded per course (Order Courses, genius-kitchen/kitchen-management-interface/kitchen-tickets.html). But no page describes holding a course and releasing/firing it on demand from a server terminal, handheld or expo screen -- the documented behavior is automatic per-course ticket separation, not a manual fire action. Retrieved from the product-documentation full-text search index. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/courses.html · retrieved 2026-08-04

kitchen-prep-time-pacing differentiator

Predictive cooking adjusts prep from AI camera data and historical sales — production forecasting rather than documented per-item start staggering to a common finish. https://www.xenial.com/solutions/drive-thru/ · retrieved 2026-08-01

kitchen-order-throttling differentiator

The volume-threshold half is documented and is named for the kitchen: Data Management > Online Ordering Settings has a Kitchen Capacity Management section - "Enable Kitchen Capacity Management - Toggle On to define a maximum number of online orders a store accepts within a 15-minute time period", with a "Number of Orders per 15 Minutes" maximum, so incoming digital orders are paced into 15-minute slots once the configured volume is reached. Shortfalls: the trigger is a fixed order count per slot, not a ticket-time threshold, and the kitchen's own timing settings (Kitchen Cell Settings > Timing: Overdue After in Seconds, Warning After in Seconds, and the Hold Timer thresholds) only raise visual and audio alerts - no documented feedback from kitchen load into order release or into quoted prep times. Every 'throttl' hit in both portals remains infrastructure-level API metering. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/online-ordering-settings.html · retrieved 2026-08-08

kitchen-channel-pause-propagation differentiator

Item 86ing does propagate automatically. Menu Engine's Item Availability page: "the employees at the point of sale change the availability status of each item dynamically", setting out_of_stock true, and "The Menu Engine API then sends a notification back to the integrator at a specified URL, informing the integrator whenever one of their sites runs out of a particular item" - a PUT to the integrator's Stockout URL carrying company_id, site_id, order_source_ids, product_id and is_available false, with the reverse notification sent on restock. The integrator must enable enable_stockout_notifications and register a Stockout URL in Portal API. Marketplaces are configured as first-party delivery services in Company Settings (DoorDash, GrubHub, Uber Eats). Shortfalls: this is item availability only - the same page states out_of_stock "has no bearing on the overall availability of the menu, which is determined by the menu's store hours for that site", and no store-pause action from POS or KDS is documented; and there is no documented KDS-initiated 86, the availability change being made in the POS. https://www.xenial.com/developer-resources/en/genius-point-of-sale/enterprise-pos/menu-engine/item-availability.html · retrieved 2026-08-08

kitchen-order-ready-callback differentiator

Shortfall: no named marketplace consumer - the ready event is published to a generic integrator topic, not to a documented DoorDash/Uber Eats/Grubhub callback. The bump-drives-ready half of the chain is documented and is no longer in doubt: fulfillment_status Ready means "The item preparation is complete" and is reached by "Items that are completed at all Kitchen Video Screens to which they are sent, either by the individual item being marked as Ready or by it being bumped from all screens (manual or auto-bump)", and the order/item state table maps "Complete an item - An action performed on the kitchen screen" to order fulfillment status Ready, "applied to the order when all its items are marked as completed". That order-level Ready is exactly what the Notification service publishes as "notification_status": "order-ready" / "fulfillment_status": "order_ready" (Message Formats Sample 12), on a per-company SNS topic any integrator may subscribe to. What is missing is only the far end: no page states that a third-party marketplace consumes it. WITHDRAWN 2026-08-08: the prior note said "no page states that bumping the KDS drives the order-ready event" - the fulfillment-status reference states exactly that, and that leg of the shortfall is removed. https://www.xenial.com/developer-resources/en/genius-point-of-sale/enterprise-pos/notification/fulfillment-statues-for-orders-and-order-items.html · retrieved 2026-08-08

kitchen-bump-bar-hardware

Dedicated Bump Bars configuration page; bump bar definitions assign to stations or to the active Kitchen Screen. Supported models list not published. Packaging caveat: on the smaller Xenial Cloud POS SKU this module is a paid add-on rather than part of the base subscription (per the App Store listing); it is scored here as a documented module of the enterprise Genius platform, where the commercial packaging is not published. https://www.xenial.com/product-documentation/en/genius-kitchen.html · retrieved 2026-08-01

kitchen-all-day-counts

Documented verbatim: 'The Order Item Summary Pane displays the \"All Day Count\" for a kitchen display. The \"All Day Count\" is the total order item quantity for all active orders on the display... automatically updated as orders are bumped and new orders are added.' Opens via bump bar or touchscreen. Per-modifier aggregation specifically is not separately called out, only per-item. Retrieved from the product-documentation full-text search index. https://www.xenial.com/product-documentation/en/genius-kitchen/kitchen-management-interface/kitchen-displays.html · retrieved 2026-08-04

kitchen-sla-alerts

The Kitchen Screen Settings Cells Timing page documents both halves of the claim: 'Overdue After in Seconds' -- 'the number of seconds that must pass after an order arrives in the kitchen before it is considered overdue. When an order is overdue, the animation and/or audio alert plays' -- and 'Warning After in Seconds' -- 'when the countdown timer for an order changes color (yellow background and red text) to alert the kitchen staff that the order is nearly overdue.' Configurable per kitchen cell/station. Retrieved from the product-documentation full-text search index. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/kitchen-settings/kitchen-screen-settings/kitchen-cell-settings.html · retrieved 2026-08-04

kitchen-printer-fallback differentiator

"Chef Recovery" is a documented kitchen-management topic implying failure recovery; automatic backup-printer failover with no ticket loss is not spelled out. https://www.xenial.com/product-documentation/en/classic-products/chef-kitchen-management/chef-recovery.html · retrieved 2026-08-01

kitchen-offline-operation differentiator

Sourced entirely to the Xenial Shell App Store blurb — marketing copy, not product documentation, and confidence was mislabeled 'documented'. Worse, the same listing I verified says kitchen management is a PAID ADD-ON, not part of the base subscription ('basic plan includes ordering, menus, sales tax, reporting, time clock, and payment integration'; kitchen management, scheduling, inventory, loyalty, gift cards, email campaigns cost extra). So offline KDS is add-on-gated on the SMB product and undocumented for the enterprise product this dossier otherwise describes. https://apps.apple.com/us/app/xenial-shell/id1463045984 · retrieved 2026-08-02 adversarially verified

kitchen-item-build-screens differentiator

Modifier builds and fractional modifier quantities render on kitchen tickets and preparation instructions. Full recipe-step/portioning build screens not documented. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

kitchen-recall-refire

Shortfall: no distinct per-item refire/reprint action is documented, only whole-order mechanisms. Recall is documented: 'If an order is bumped from a kitchen display by mistake, recall the bumped order to the open orders display... a ***RECALLED*** label appears in the kitchen ticket header', with an 'Upstream Recall' setting controlling whether recall propagates to upstream monitors (recall-settings.html). Separately, 'Resend Order to Kitchen' is a documented POS order-level procedure. But no page describes refiring or reprinting a single item within an order without re-entering it -- the granularity documented is the whole order. Retrieved from the product-documentation full-text search index. https://www.xenial.com/product-documentation/en/genius-kitchen/using-kitchen-management.html · retrieved 2026-08-04

kitchen-order-modification-alerts differentiator

Kitchen Screen Settings > Cells > Cell Body has the setting outright: "Display Changes In Order - Toggle Yes to display indicators for order updates in the kitchen. If the order is updated at the POS after the order is sent to the kitchen, the order updates are indicated in the kitchen in real-time." The Animation section on the same page gives separate animations for Order Arrival, "Item Arrival - Select the animation to play when an item is added to an order", Order Update and Order Bump, and Enable Super Headers displays "a visual indicator that notifies the kitchen staff when an order does not require preparation, such as a Cleared, Deleted, or Voided order". The developer-side POS/kitchen state table confirms the removal case: on Void order item, "The item is shown as Voided on the kitchen display", and newly added items enter as Pending while previously added items remain Submitted. Configured per kitchen screen, so it is on by choice rather than always. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/kitchen-settings/kitchen-screen-settings/kitchen-cell-settings.html · retrieved 2026-08-08

kitchen-guest-ready-notification differentiator

An Order Ready Display is a documented first-party guest-facing screen: 'a customer-facing display that enables the customer to see the status of their order. While their order is prepared, the customer's name appears in the In Progress section... When the order is ready, the customer's name appears in the Ready section' (or the order number if no name is captured). This is a Data Management > Kitchen Settings object, not a separately sold product line, and satisfies the order-status-display-board branch of the claim (SMS/push branch not separately confirmed, though the developer-resources Order Notification service supports SMS/email/push subscription types generically). Retrieved from the product-documentation full-text search index. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/kitchen-settings/order-ready-display.html · retrieved 2026-08-04

kitchen-waste-logging

Waste is a first-class POS transaction with reason codes and inventory depletion: Enterprise POS App > Order Entry Procedures > Order-Level Procedures documents Create Waste Order - "this action enables you to identify selected order items as 'waste'. The ingredients are removed from inventory" - and the flow is Functions > Create Waste Order, select items, select Waste, "When prompted, select the reason code for the transaction (if applicable)". Create Waste Order is a grantable terminal-scheme function, order_type on the order API carries the value Waste, and Genius Back Office adds Menu Waste/Promo and Raw Waste/Promo entry forms with timestamped, summable waste records. Shortfall: none of this is at the kitchen/KDS screen. The Genius Kitchen and Kitchen Screen Settings surfaces (bump, recall, item lifecycle Claim/Complete, ingredient filters) contain no waste, spoilage or remake logging action, so the entry point is the POS terminal or Back Office rather than the KDS. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-pos-app/order-entry-procedures/order-level-procedures.html · retrieved 2026-08-08

kitchen-speed-of-service-reporting

Remote Performance Monitoring in kitchen management plus camera-based lane timers and Back Office KPIs. Percentile slicing and CSV/API export not confirmed. https://www.xenial.com/product-documentation/en/classic-products/chef-kitchen-management/remote-performance-monitoring.html · retrieved 2026-08-01

kitchen-prep-forecasting

Predictive cooking from historical sales plus Back Office Projections (four-week trend, daily and daypart) driving production and ordering. Packaging caveat: on the smaller Xenial Cloud POS SKU this module is a paid add-on rather than part of the base subscription (per the App Store listing); it is scored here as a documented module of the enterprise Genius platform, where the commercial packaging is not published. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

delivery-driver-roster

Drivers are a modelled role, not just an ad-hoc employee. The Foodservice Management POS security-role Capability list (an exhaustive POS Functions table) includes "Delivery Dashboard - Access the order delivery dashboard", "Delivery Dashboard Manager (view all drivers) - Access the order delivery dashboard and view all drivers", "Driver Cash Drop - Delivery driver cash drop" and "Driver Settlement - Delivery driver cash settlement"; the Add Position form carries "Delivery Driver? If selected, the position involves delivering orders to customers in a vehicle"; and the Omni Order Injection API rejects an edit with error 131 "Order is assigned a driver", so driver-to-order assignment exists in the order model. Clock in/out is a general POS function (Clock In Self / Clock In/Out Employee). Shortfall: no page documents the contents of the delivery dashboard, no in-store / on-run / returning assignment states are defined, and no per-driver run-history report is documented anywhere in Back Office Report Manager or the FSM Reports page. This is also the Foodservice Management POS line (the Nextep-derived campus/foodservice product), not Enterprise POS -- the QSR Enterprise POS tree documents no driver functions at all. https://www.xenial.com/product-documentation/en/genius-point-of-sale/foodservice-management-pos/employees.html · retrieved 2026-08-08

delivery-dispatch-board

Re-examined 2026-08-08 against a full dump of BOTH Paligo portals on www.xenial.com (product-documentation, 786 pages / 3,917 sections, and developer-resources, 293 pages / 3,333 sections). The screen exists: the Foodservice Management POS security-role capability table lists "Delivery Dashboard - Access the order delivery dashboard" and "Delivery Dashboard Manager (view all drivers)" (/product-documentation/en/genius-point-of-sale/foodservice-management-pos/employees.html). But those two permission rows are the only occurrences of "delivery dashboard" in 1,079 pages -- neither the Foodservice Management POS User Guide nor the Order Management System (OMS) chapter, which are where a dispatch screen would be described, mentions drivers, undispatched queues, driver availability or multi-order run batching. The OMS chapter documents Open / Closed / Future tabs with elapsed time per ticket, which is kitchen expo rather than delivery dispatch. Enterprise POS has no equivalent screen. Unresolved because the dashboard's contents are undocumented, not because dispatch is absent.

delivery-route-map differentiator

Re-examined 2026-08-08 across both www.xenial.com Paligo portals (product-documentation and developer-resources, 1,079 pages / 7,250 sections dumped in full). Searches for map, route, geocode, stop sequencing and turn order return nothing relevant: the only "geocod" hit in the entire corpus is a geo/coordinates/geocodingStatus block describing the STORE's own location inside a Customer Loyalty Service sample payload (/developer-resources/en/genius-add-on-products/gift-and-loyalty/customer-loyalty-service/operation-definitions/sample-code.html), and every "zone" hit is a time zone or a Vision Zone drive-thru vehicle detector. The Online Ordering API Order Object field-category index (/developer-resources/en/genius-point-of-sale/enterprise-pos/online-ordering/order-object.html) enumerates ~30 field groups and contains no driver, route, stop or geolocation object. Held unknown rather than no because the Foodservice Management Delivery Dashboard exists as a permission but its contents are never documented, so its map behaviour is unexamined rather than excluded.

delivery-driver-tracking differentiator

Re-examined 2026-08-08 across both www.xenial.com Paligo portals in full. There is no driver-facing mobile app in the documented app set -- Genius Mobile Manager (/product-documentation/en/genius-mobile-manager/, 27 pages) is a manager dashboard/alerts app, and the installable POS apps are Genius Shell and Enterprise POS. The Online Ordering Order Object field-category index and the Enterprise Kitchen SendOrderRequestBody schema (/developer-resources/en/genius-kitchen/operation-definitions.html) carry vehicle fields for drive-thru (vehicleidentifier, vehicleuniqueid, parkstatus, currentfulfillmentpoint) but no driver, latitude/longitude or location object. Searches for driver GPS, driver location and live driver return nothing. Unknown rather than no because the Foodservice Management Delivery Dashboard's contents are undocumented and Xenial's full API reference is gated behind a per-user Genius Portal permission ("API Documentation Access"), so absence in the public set is not absence in the product.

delivery-address-validation

The Online Ordering API's CustomerRequestBody is the schema every first-party online order carries, and its address handling is free text with no validation semantics: "address1 string No The address of the customer / address2 string No The secondary address of the customer / city string No The city of the customer / state string No The state of residence of the customer / zip_code string No The zip code of residence of the customer", plus pickup_date_time and delivery_date_time. Every field is optional and none is geocoded, normalised or checked; there is no zone, service-area, distance or validation-status field, and the Order Object field-category index (order-object.html) lists no geolocation object at all. Independently, the Online Ordering Settings editor -- which enumerates the module's entire configurable surface (Color Schema, Company Logo, Ordering Flow Settings, Products Displaying Settings, Order Source, Kitchen Capacity Management, Payment Fulfillment Options, Destinations, Digital Notifications) -- contains no delivery-zone, radius or address-validation setting. "Delivery zone", "geocode" and "address validation" occur zero times across all 1,079 pages of both portals. Address vetting is therefore left to the marketplace or the integrator's own storefront, not performed by Xenial. https://www.xenial.com/developer-resources/en/genius-point-of-sale/enterprise-pos/online-ordering/operation-definitions.html · retrieved 2026-08-08

delivery-driver-comp differentiator

Re-examined 2026-08-08 across both www.xenial.com portals. Contrary to the previous rationale, driver-specific money functions do exist -- the Foodservice Management POS Functions table (/product-documentation/en/genius-point-of-sale/foodservice-management-pos/employees.html) lists "Driver Cash Drop" and "Driver Settlement - Delivery driver cash settlement", and the FSM POS User Guide's Drawer Management table defines "Driver Drop: used when a delivery service is used, and the money collected by the employee needs to be entered into the FSM POS system... the employee returned from delivering a pizza order and needs to submit the money collected from the guest." All three concern cash the driver COLLECTS, not what the driver is PAID. Searched both portals for mileage, distance driven, per-delivery reimbursement and driver tip retention: zero hits. The Back Office Payroll export and payroll-reports pages document wage and time-punch export with no reimbursement-vs-wage line split. Unresolved because driver pay is plainly handled somewhere (drivers are a first-class Position) but no published page describes the inputs.

delivery-daas-dispatch

Re-examined 2026-08-08 across both portals. The Order Source editor (/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/order-source.html) ends its General page with "Preferred Delivery Provider - Select the Preferred Delivery Provider for this Order Source", and Company Settings has a "Food Delivery Services (DoorDash, GrubHub, Uber Eats)" service block with a Delivery Service URL and Callback URL per provider -- so the platform does hold a per-source delivery-provider assignment. But that single sentence is the only documentation of the setting: no page describes requesting a courier, receiving a quote, or a courier status coming back onto the order record, and the Online Ordering Order Object field-category index contains no courier, quote or fulfilment-partner object. "DoorDash Drive", "Uber Direct", "Nash" and "Relay" (as a courier) occur zero times in 1,079 pages; the only Relay hit is "Partner Relay", a stock-lookup service. Unresolved: the hook exists, its behaviour is not published, and Xenial's full API reference is customer-gated behind a Genius Portal per-user permission.

delivery-daas-fallback differentiator

Re-examined 2026-08-08 across both www.xenial.com portals in full. The only courier-selection mechanism published is a static one-line setting, "Preferred Delivery Provider - Select the Preferred Delivery Provider for this Order Source" on the Order Source editor: one provider per source, with no conditions, thresholds or fallback ordering. The Genius rule surfaces that do exist and are fully enumerated -- the Fees editor's Availability/Qualify/Apply Criteria pages and the Order Source editor's own field list -- expose conditions on order source, destination, event type and order total only, nothing on driver availability, wait time or zone. Searches for hybrid dispatch, overflow, fallback courier and auto-assign return nothing. Held unknown rather than no because the in-house driver side (Delivery Dashboard, driver Positions) is documented only as permissions, so there is no published description of the dispatch behaviour this rule would sit on top of.

delivery-3p-direct-integration differentiator

Vendor-owned, not resold middleware. (1) Self-Service Integration Onboarding: "Self-Service Integration Onboarding (SSIO) allows merchants to manage Delivery Service subscriptions through the Portal. Enabling self-service onboarding for single or multiple sites activates features such as menu generation and publishing for the subscribed delivery service." The operator selects Connect to <service>, signs into the delivery service with Google/Facebook/Apple/email credentials, maps sites in Onboarding Site Mapping, selects Onboard Site within a 60-minute session window, then Refresh Status and Refresh Menu -- single-site and multi-site procedures both documented, with instructional videos. (2) Company Settings > Services carries a "Food Delivery Services (DoorDash, GrubHub, Uber Eats)" block with a per-provider Delivery Service URL, Callback URL (Menu Engine) and Order Source mapping, and a named "DoorDash Self-Service Integration" where "Genius manages integration (tokens, subscriptions, test stores) and monitors integration health in real-time via the new self-service DoorDash Developer Portal" and sites are activated for DoorDash from the DoorDash Onboarding section. (3) The Order Source editor publishes per-DSP menu-image specifications for DoorDash, Grubhub and Uber Eats (exact file size, format and aspect-ratio requirements) -- an integration you resell does not require you to hold each marketplace's asset spec. (4) The Omni Channel Ordering developer set publishes native per-marketplace order payloads for Uber Eats, Grubhub and DoorDash, including each marketplace's own JSON order shape and the matching Xenial POSResponse. Deliverect and Checkmate are also listed as partners, but they are alternatives to, not the route for, the direct integrations. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-portal/self-service-integration-onboarding--ssio-.html · retrieved 2026-08-08

delivery-3p-injection

Deliverect aggregates online-order and delivery channels directly into Xenial Cloud, giving one view of all orders — but this is paid middleware, not native injection. https://www.deliverect.com/en-us/integrations/xenial-cloud · retrieved 2026-08-02

delivery-menu-push

Achievable through the Deliverect integration rather than a documented first-party push from the POS master menu. https://www.deliverect.com/en-us/integrations/xenial-cloud · retrieved 2026-08-02

delivery-86-sync

Documented end to end. "Integrators do not set the value of out_of_stock directly; instead, the employees at the point of sale change the availability status of each item dynamically to reflect the stock of items at their site. The Menu Engine API then sends a notification back to the integrator at a specified URL, informing the integrator whenever one of their sites runs out of a particular item." Setup is two subscription fields -- "enable_stockout_notifications" and "stockout_url - The webhook/callback URL that receives PUT messages for stockout notifications" -- enabled "for their delivery services subscription in Portal API". The payload is a PUT carrying company_id, site_id and an availability array of {order_source_ids, product_id, entity_id, is_available}, so status is scoped per order source (i.e. per marketplace channel). Restore is explicit: "When the site in question is able to restock the item, the employees set the item to available in POS, and the item's out_of_stock value returns to 'false'... The Menu Engine API sends another notification to the integrator's Stockout URL informing them that the item is now available at that site." Newly generated menus also carry the flag so a channel can reconcile state. The POS-side action is the documented Item Availability manager function (item-availability.html: grays out and crosses off the item). Caveat on wording: the notification is keyed on product_id, so item-level 86 is evidenced; a separate modifier/item-option availability push is not separately documented. https://www.xenial.com/developer-resources/en/genius-point-of-sale/enterprise-pos/menu-engine/item-availability.html · retrieved 2026-08-08

delivery-store-pause

Pausing is a first-class, per-channel POS function. The Order Source editor's General page carries "Allow Pausing this Order Source - Toggle On to enable permissioned POS users to pause receiving orders from this order source to prevent order overload", and the Open Order Screens editor carries "Display Order Source Management Button - Toggle Yes to enable permissioned POS users to pause receiving orders from specific Order Sources". Because each delivery marketplace is configured as its own Order Source (Company Settings maps DoorDash, GrubHub and Uber Eats each to an Order Source), that is per-marketplace pausing initiated from inside the POS. It propagates: the Site Status Notification service "detects changes in the accepting_online_orders flag and sends notifications to the integrator when this flag is changed from the store", and the Online Ordering FAQ adds "our system can send an https request to an applicable API to pause/unpause online ordering operation for a store". Shortfall: what is documented is Xenial refusing intake and telling the channel, not deactivating the storefront on each marketplace's own system; and no timed auto-reactivation exists anywhere -- there is no duration, expiry or resume-at field on the pause, so a paused source must be un-paused by hand. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/order-source.html · retrieved 2026-08-08

delivery-3p-reconciliation differentiator

Re-examined 2026-08-08 across both www.xenial.com portals. What Xenial does publish for third-party channels is tax, not settlement: order sources carry Is Marketplace / Is Tax Liable toggles, tax definitions carry a marketplace_liable flag, the Order Object exposes total_marketplace_liable, and integrators may inject marketplace_remitted_tax and collected_exclusive_tax (Marketplace Facilitator Field Injection). Nothing addresses payout deposits, commission, marketing fees, adjustments or missing orders. The Back Office Export utility enumerates the exportable modules -- "Cash Sheet, Employees, Inventory, Menu Analysis, Menu Items, Payroll, Product Mix, Purchases, Security Users, Time Punches, Transaction Level Detail (TDL)" -- with no third-party or settlement module, and every 'reconcil' hit in the corpus is till reconciliation or Reconcile Inventory. Held unknown rather than no because Report Manager (/product-documentation/en/genius-back-office/report-manager.html) never enumerates its report catalogue -- reports are chosen from a Report Type dropdown whose contents are not published -- so the report inventory is not an exhaustive list I can argue from.

delivery-injection-error-visibility differentiator

Orders do not fail silently, and the alerting is operator-configurable in Data Management. Company Preferences > Notification Service: "Notification Channel - From the dropdown, select the preferred notification delivery channel: None (do not send notifications), Email, Pus[h] (push notification on mobile device), SMS (text message on mobile device)"; "Events to notify ... select a notification template OR select None (Don't Notify)"; and "Delayed Delivery Wait - Number of minutes the service waits before it sends notification to the integrator of delayed order delivery. Default is 10. For example, online order delivery is delayed if the POS unit is offline. The notification enables the integrator to decide how to handle the delay (e.g. cancel orders in the queue). All orders in the queue that are not canceled are delivered once the unit is back online." Alongside it, the Site Status Notification Service lets "customers and integrators" subscribe to a company SNS topic for site online/offline events and exposes GET /site/status, GET /terminal/status, GET /kitchen/status and GET /events, with a POS heartbeat and a configurable six-minute offline threshold. Shortfall: everything published is event-push aimed primarily at the integrator, not an operator-facing console -- there is no per-channel connection-status dashboard in the Genius Portal, no queue or list of failed or rejected order injections, and the only rejection documentation is the developer-side Integration Error Handling page of retry advice for 4XX/5XX responses. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/preferences/company-preferences.html · retrieved 2026-08-08

delivery-tracking-page

Re-examined 2026-08-08 across both www.xenial.com portals. The relevant surface is the Digital Notifications editor (/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/digital-notifications.html), which builds HTML templates per Event Type with a Usage Type and per-site activation; Online Ordering Settings points at it for "email notification templates for receipts and order cancellation events", and the only Event Types the page names are Order Confirmation, Receipt and Refund. Nothing describes a guest-facing status page, a tracking link, or SMS to the guest for a first-party delivery order -- the Twilio service's enumerated uses in Company Settings are SMS Receipt, Waitlist and Transfer Request, and Suite Catering's SMS notification is EDO event messaging to venue staff. Held unknown rather than no because the Digital Notifications page never enumerates its Event Type dropdown (it says only "This setting is not available for all Event Types"), so the notification catalogue is not an exhaustive list, and no driver state exists to drive such a page in the first place.

delivery-promise-time differentiator

Re-examined 2026-08-08 across both www.xenial.com portals. Two adjacent mechanisms exist and both are static. Foodservice Management POS > System > Hours of Operation exposes an Advanced Orders section for future orders whose only timing fields are "Prep Time - Number of minutes required to prepare future orders" and "Number of Days - Number of days notice required for future orders" -- a per-store constant. Online Ordering Settings exposes "Kitchen Capacity Management ... Number of Orders per 15 Minutes", which throttles intake but does not alter a quoted time. The Enterprise Kitchen order schema carries futuresendtime and pickupdate but no computed promise or ready estimate, and 'promise time', 'quote time' and 'lead time' occur zero times in 1,079 pages. Held unknown rather than no because neither of those pages is a delivery promise-time editor -- one is FSM hours of operation, the other online-ordering intake -- so there is no settings screen whose options are the promise-time surface, and the load-aware quoting could sit in the ordering front end rather than in configuration.

delivery-offline-behavior

Delivery is named, not left to inference. Under Loss of Internet the Cloud Message Queue row reads: "POS cannot consume messages from the cloud queue. Messages accrue until connectivity is restored, at which point POS automatically consumes them in the background with no user intervention required. Impacted functionality includes: Mobile and Delivery Service Provider (DSP) orders cannot be consumed." The chapter's Things to Know adds "When a unit comes back online, will it receive all orders that have queued while the unit was offline? Yes... When a unit is offline, the integrator who submitted the order receives a notification and determines how to handle the delay", which ties to the configurable Delayed Delivery Wait in Company Preferences. Loss of LAN separately documents that "Product Availability Updates (86) are not synchronized between terminals until LAN connectivity is restored" and that payment processing fails on networked devices while Bluetooth/USB/serial pinpads keep working. Shortfall: the chapter covers channel intake only. None of the three specifics this claim names is addressed -- whether a cash delivery order can be rung and closed offline, whether a driver can be assigned while offline, and whether Driver Settlement / Driver Cash Drop function during an outage are all unstated, and those functions live in the Foodservice Management POS line whose offline documentation is limited to Offline Credit Card Transactions and a 'Run POS in Offline Mode' permission. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-pos-app/pos-online-offline-data-flow.html · retrieved 2026-08-08

digital-first-party-web

Shortfall: integration language throughout — Xenial "integrates online and mobile ordering with delivery capabilities", and the line item reads "Online, Mobile Ordering & Delivery Integration". Re-checked 2026-08-02: the one "open API and software architecture" boast on that page attaches to Xenial Encounter, a Classic product, not to the Genius platform. There is no first-party online-ordering module in the product-documentation tree, and the documented digital-channel path is Deliverect middleware. https://www.xenial.com/products/pos-software/ · retrieved 2026-08-02 adversarially verified

digital-menu-single-source

Pure vendor positioning ('one connected platform'). It is also in tension with the dossier's own delivery cells, which show marketplace menus flowing through Deliverect middleware rather than one propagated menu record. No documentation of single-record propagation with per-channel sync status. https://www.xenial.com/products/pos-software/ · retrieved 2026-08-02 adversarially verified

digital-native-app differentiator

Sole source is the geniusforenterprise.com home page module list. No branded consumer app product documentation, no named brand app built on it, no App Store evidence of a Xenial-built guest ordering app (the only Xenial iOS listing is the operator-facing Shell app). Marketing-page 'yes'. https://geniusforenterprise.com/home · retrieved 2026-08-02 adversarially verified

digital-account-saved-payment

All three elements exist, but only in the venue-catering product. SuiteSpot is described as "the fan-facing site" that authorized users access "to place orders and manage account settings"; adding an authorized user captures Basic Information, Phone Numbers and an Address, sends a SuiteSpot registration email, and the user then has: saved cards ("Pay by a Saved Card or Pay by a New Card", an Add/Edit Cards on File permission, a Card On File Expiration Email reminder, and 3DS OTP on card add), FAVORITES ("A favorite is an order saved as a template", maximum 12, saved from the ORDERS tab) and MY ACCOUNT > ORDERS & BILLING > ORDER HISTORY. Separately, Enterprise POS Company Preferences > Loyalty exposes "Favorite Items - display a customer's 'favorited' loyalty items on their profile for quick access" and "Recent Items - display a customer's recently ordered items on their profile for quick access (Group by Order; Last <period>; Max Allowed 0-50)", which is reorder off a guest's loyalty profile. Shortfall: the general Online Ordering module has none of it. Its complete settings editor has no account, login, saved-card or reorder section; its API customer object is a per-order record with free-text address fields and no account or stored-token concept ("How do we create a customer? Send a request with all customer information, typically collected from customer login information from a merchant's website" -- i.e. the identity lives in the integrator's storefront, not in Xenial); and no first-party channel is documented with saved addresses plus saved payment plus one-tap reorder together. https://www.xenial.com/product-documentation/en/genius-add-on-products/suite-catering/suitespot.html · retrieved 2026-08-08

digital-upsell-engine differentiator

AI upsell is documented for drive-thru surfaces; digital-checkout suggestion configuration and attach-rate reporting are not. https://www.xenial.com/products/drive-thru-controller/ · retrieved 2026-08-01

digital-scheduled-pacing

Both halves are documented as configuration, not marketing. Throttling: the Online Ordering Settings editor carries "Kitchen Capacity Management - Enable Kitchen Capacity Management: Toggle On to define a maximum number of online orders a store accepts within a 15-minute time period" and "Number of Orders per 15 Minutes - Maximum number of online orders a store accepts within a 15-minute time period" -- a per-time-slot capacity cap on acceptance. Future orders: the same editor's Ordering Flow Settings offer "Display Pick Up Time Step at the Start of the Ordering Flow ... Enable this option if menu item availability and pricing is dependent upon business hours" (otherwise the Pick Up Time is chosen on the Order Review page); the Online Ordering API carries pickup_date_time and delivery_date_time on the customer object, with the FAQ noting "How this value is queued depends on whether the pickup time exceeds the current business day"; Hours of Operation has an Advanced Orders section with Prep Time and days of notice; and the Order Management System has a dedicated Future tab where "orders placed through Mobile/Online Ordering appear", showing order due date and time and auto-promoting to Open a configurable interval (e.g. 15 minutes) before the due time. Two limits worth recording though they do not defeat the claim: the cap is a single orders-per-15-minutes value rather than a per-daypart schedule, and item-level (as opposed to order-level) slot caps are not offered. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/online-ordering-settings.html · retrieved 2026-08-08

digital-fulfillment-modes

Verified verbatim ('Counter, drive-thru, line-busting, curbside, delivery, and more: your choice of channels in one connected platform') but it is a marketing enumeration with no documentation for curbside arrival/check-in, and delivery here means marketplace integration, not fulfillment. Claim-level at best. https://www.xenial.com/products/pos-software/ · retrieved 2026-08-02 adversarially verified

digital-qr-table

QR contactless payment marketed; scan-to-order attaching to an existing POS check with split and tip is not documented. https://www.xenial.com/solutions/drive-thru/ · retrieved 2026-08-01

digital-kiosk differentiator

Shortfall: self-order kiosk is a genuine first-party line (Nextep Systems heritage, now Global Payments) and trade press reports enhanced 2026 kiosk configurations integrated with POS and kitchen management — but there is NO kiosk module in the public product-documentation tree (which covers Integration Partners, Point of Sale, Back Office, Kitchen, Drive Thru, Digital Menu Board, Mobile Manager, Add-on Products, Classic Products and Hardware), and no ADA/WCAG conformance is published. Downgraded from yes: trade press is grade E, below the floor for a differentiator. https://restauranttechnologynews.com/2026/06/global-payments-strengthens-restaurant-operations-with-connected-pos-payments-and-commerce-technology/ · retrieved 2026-08-02

digital-group-ordering

Re-examined 2026-08-08 across both www.xenial.com portals (1,079 pages / 7,250 sections). The three group-adjacent mechanics found are all something else: (1) kitchen cell settings carry a "Group Indicator - Display the associated Group Order when the order is added as part of a large group order", an in-store large-party display flag; (2) the Enterprise POS terminal-scheme 'group order' order option added in the 2026 Data Management release notes is a cashier-side option modal; (3) Suite Catering accounts have multiple Authorized Users who can each place orders against one suite account, with per-user permissions -- but that is a standing venue account, not a shareable one-time cart, and its permission list carries no per-person or total spend cap. Searched both portals for shareable link, share link, spend cap, per-person limit and split payment in an ordering context: no consumer-facing group cart appears. Unresolved rather than no because Xenial's guest-facing ordering front ends (the embeddable Online Ordering module and integrator storefronts) are documented only by their settings editor, which does not enumerate cart features.

digital-catering-portal differentiator

Shortfall: this is stadium/suite catering, not restaurant catering, so lead-time rules, minimums and quote workflows for a restaurant brand are not documented. Suite Catering is a distinct documented Genius add-on with its own guest portal (SuiteSpot) -- 'advanced day order and event day order workflows', per-event ADO/EDO ordering windows, account-based ordering with tax exemptions and special pricing, and a documented invoice-payment flow ('Pay Invoice', with saved-card support). That satisfies the structural shape of the claim (separate ordering flow, accounts, deposits/invoice payment) but for the venue/suite segment specifically, which this dossier's ICP notes is 'not restaurant catering'. Retrieved from the product-documentation full-text search index; same underlying source already used for order-capture-catering. https://www.xenial.com/product-documentation/en/genius-add-on-products/suite-catering/suite-catering---getting-started.html · retrieved 2026-08-04

digital-voice-ai-phone differentiator

Re-examined 2026-08-08 across both www.xenial.com portals. Voice ordering is genuinely supported at the data layer: Menu Engine can emit voice command data per item on request ("include_voice_commands boolean - When set to true, voice commands and its synonyms are added to the Menu Engine menu output"), with voice_name ("The primary product name for use with voice ordering"), voice_synonyms ("The typical pronunciations of the product name or alternate names") and voice_description as first-class product fields configured in Data Management. Genius Integration Partners lists a Voice AI category naming Audivi, ConverseNow, Hi Auto, OpenCity and Presto. What is missing is the channel: no page says inbound phone, call answering, telephone or IVR, none of the five Voice AI partners has its own documentation page (only Como and Punchh do), and the drive-thru tree describes headset and lane audio rather than telephony. Unresolved because an integration directory cannot establish which channel a named partner serves, and the partner-specific detail is not published.

digital-drivethru-ai

Shortfall: camera-driven lane AI is documented — the Genius Drive Thru Vision system "automates order start, maintains order sequence, and improves throughput with minimal staff input" — but conversational AI order-taking is not. Voice ordering appears only as patent-pending marketing copy, with no documented accuracy, escalation or human-handoff behaviour. Direct fetch of xenial.com/product-documentation returns the navigation tree only (body text is client-rendered); the quoted text is from the public search index of this page. https://www.xenial.com/product-documentation/en/genius-drive-thru.html · retrieved 2026-08-02

digital-sms-ordering

Re-examined 2026-08-08 across both www.xenial.com portals. SMS exists as an integration, not as a channel: Company Settings > Service Settings defines Twilio as "A Short Message Service (SMS) used for printing receipts and sending transfer request notifications", and its configuration pages are exactly three -- SMS Receipt, Waitlist and Transfer Request, each with an Enabled toggle and default-or-custom credentials. SMS also appears as a Notification Channel option in Company Preferences > Notification Service and as EDO messaging to suite attendants in Suite Catering. Nothing anywhere describes an inbound text-to-order, text-a-link or conversational chat ordering flow landing in the POS; text-to-order, SMS order and chat order return zero hits in 1,079 pages. Held unknown rather than no because the Twilio service page enumerates one partner's feature set, not Xenial's ordering channels, and the ordering-channel inventory is never published as a closed list.

digital-google-order differentiator

Re-examined 2026-08-08 across both www.xenial.com portals in full. Every occurrence of Google is one of four unrelated things: the Google Play Store as an install route for Genius Shell and Enterprise POS; "Google Pay Merchant ID" / googlepay_merchant_id as a Payment Router wallet credential; Chrome as the recommended browser for the Genius Portal; and "Google credentials" as one sign-in option in the Self-Service Integration Onboarding OAuth window. There is no Google Business Profile, no Order with Google, no food-ordering-link provisioning and no 'Preferred by Business' setting anywhere, and the Online Ordering Settings editor's website integration section offers only a copy-paste script and button for the operator's own site. Genius Integration Partners' Delivery and Online Ordering category lists Checkmate, Deliverect, DoorDash, Grubhub, Olo, Paytronix, SkipTheDishes and Uber Eats -- Olo does provision Order with Google for its customers, so the path may exist commercially -- but an integration directory is not an exhaustive statement of capability, so this stays unresolved.

digital-apple-business-connect

Re-examined 2026-08-08 across both www.xenial.com portals in full. The only Apple references are "Apple Pay Merchant ID" / applepay_merchant_id in the Payment Router site configuration, the Apple App Store as an install route for Genius Shell, "Apple credentials" as a sign-in option in the Self-Service Integration Onboarding OAuth window, and an AppleWebKit user-agent string in a sample payload. Apple Business Connect, Apple Maps, place card and Order Food custom action return zero hits across 1,079 pages / 7,250 sections. Unresolved rather than no for the same reason as the Google surface: place-card provisioning is normally delivered by the online-ordering partner (Olo and Checkmate are both listed Xenial partners) rather than by the POS, and no Xenial page enumerates which listing surfaces its ordering links are published to.

digital-loyalty-attach

POS documents loyalty transaction processing and integrates Punchh and Como. Shared guest identity across in-store and digital not documented. https://www.xenial.com/product-documentation/en/genius-integration-partners.html · retrieved 2026-08-01

digital-subscriptions

Re-examined 2026-08-08 across both www.xenial.com portals. 'Subscription' occurs constantly and always in the operator sense -- a company or site subscribing to Suite Catering, Online Ordering, a delivery service, a Menu Engine menu subscription with stockout_url, or Portal service subscriptions managed under Manage Service Subscriptions. 'Membership' occurs only as security-group membership for Portal users and as a loyalty prompt ("Enable Loyalty Prompts - prompt user to ask customer about loyalty membership"). The recurring guest-side constructs that do exist are Suite Catering's Advanced Day Ordering / Event Day Ordering windows and Par Stock (standing stock per suite per event), neither of which is billed recurringly to a guest. No delivery-fee waiver, per-period entitlement or paid loyalty tier is documented; the loyalty surface is entirely partner-delivered (Como, Fortress, Givex, Mirego, Paytronix, Punchh, Sparkfly, SVS, Beanstalk). Unresolved because a paid tier would be configured in the loyalty partner's own product, which is outside Xenial's published documentation.

digital-promo-parity

Discounts and employee benefits are centrally configured tender operations on a single platform, implying parity, but channel eligibility controls are not documented. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

digital-guest-data-ownership differentiator

Re-examined 2026-08-08 across both www.xenial.com portals. On the mechanics: the Back Office Export utility enumerates the modules it can extract -- "Cash Sheet, Employees, Inventory, Menu Analysis, Menu Items, Payroll, Product Mix, Purchases, Security Users, Time Punches, Transaction Level Detail (TDL)" -- with no customer or guest module; the only bulk guest-record export found anywhere is Suite Catering's Account List, which offers Import/Export Accounts with a downloadable template and an 'Export Selected Accounts' action, plus a Guest Account Import that creates or updates registered guests who "can login to mobile ordering sites". On the substance of the claim -- a documented statement that the operator OWNS the records and can export them in bulk without fee or vendor approval -- nothing in either portal addresses ownership, licensing or export fees at all, and searches for data ownership, own the data and guest data return zero hits. Unresolved rather than no because that commitment is a contractual term that would sit in the Global Payments/Xenial master services agreement or DPA rather than in product documentation, and Xenial sells to enterprise QSR chains under negotiated contracts that are not published.

digital-checkout-pci-sca

Card data is kept off the restaurant's page: "When the processor hosted payment controls (HPC) configuration is complete, selecting Credit payment in the website initiates a request to the processor in order to retrieve the control that hosts the credit payment user interface (UI). This UI is an iframe tag that is provided by the processor. All credit card inputs on this credit UI are routed to the processor's services", and "Credit card sales are processed through the existing online ordering flow, with the addition of the new hosted payment iframe being displayed seamlessly... Users fill in the hosted credit form normally and confirm by selecting the Pay button displayed within the iframe." The Payment Router API corroborates the pattern with a session_key field described as "The Hosted Payment Controls (HPC) bearer token received during in the request", alongside board_card ("If the value is true, save the card details for future payments") so the PAN is exchanged for a stored credential at the processor. 3DS is documented on the guest-facing side: in SuiteSpot, "If 3DS authentication is required when adding a credit card, a pop-up appears requesting the one-time passcode (OTP) sent to the registered mobile number", with Add Credit Card and Pay by a New Card suppressed when the Genius integration is disabled while 3DS is enabled. Shortfall: no PCI DSS compliance statement of any kind is published in either portal -- 'PCI DSS' and 'PCI DSS 4' occur zero times across 1,079 pages -- so there is no attestation, no service-provider AOC reference and nothing addressing the client-side script-integrity requirements effective March 2025; and hosted-field/iframe checkout is documented for the Foodservice Management online-ordering flow while 3DS is documented only for SuiteSpot, so neither is shown to cover the whole digital estate. https://www.xenial.com/product-documentation/en/genius-point-of-sale/foodservice-management-pos/snap-ebt-guide.html · retrieved 2026-08-08

digital-surcharge-transparency differentiator

Channel parity is real. There is a single Fees editor in Data Management > Ordering Settings > Discounts & Fees with four pages -- General, Availability, Qualify Criteria, Apply Criteria -- and no separate digital fee configuration exists. Its Availability page scopes a fee by "the order source, order destination, and/or event type", with Order Sources conditions of All / Only the Following / Excluding the Following; because each digital and marketplace channel is its own Order Source, the same fee object with the same Fee Method (Fixed Amount, Fixed Percentage with pre/post-discount consideration and a Maximum Amount, or Range with order-total range sets) applies to a digital order exactly as to a POS order, per-site overridable via the globe icon. The fee_type "surcharge" appears in the order payload as an item of item_type "fee". Shortfall: the compliance half is absent. The Fee editor's complete field list contains no tender type, card brand or payment-method condition, so a card-brand-scoped surcharge (and the brand exclusions surcharging rules require) cannot be expressed; there is no jurisdiction or state condition, only per-site values an operator must set by hand; and no guest-facing disclosure text, receipt-legend or checkout-notice field is documented for digital checkout. 'Dual pricing' and 'cash discount' occur zero times across both portals, so a cash/card dual-price display is not offered either. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/fees/automatic-fee.html · retrieved 2026-08-08

guest-loyalty-unified-profile

Re-checked 2026-08-08 across both www.xenial.com Paligo portals, /product-documentation/en/ (786 pages) and /developer-resources/en/ (293 pages), which the earlier pass had not reached. The Customer Loyalty Service API surface is fully enumerated at /developer-resources/en/genius-add-on-products/gift-and-loyalty/customer-loyalty-service/operation-definitions/client-integration-endpoints.html and provider-integration-endpoints.html and consists of identifyCustomers, simulateAccrual, redeemReward, submitOrder, voidOrder, addCustomer, updateCustomer, redeemBalance and reverseBalance -- there is no merge, link or dedup operation, and identifyCustomers takes one of phone_number / email / code / loyalty_card_number and returns whatever the configured provider (Paytronix, Punchh, Como, Givex, Fortress, SVS) holds. The only first-party guest-record UI found is Foodservice Management POS ('Search by Phone', 'Search by Email', 'Creating Customer Profile' on /product-documentation/en/genius-point-of-sale/foodservice-management-pos/foodservice-management---pos-user-guide.html), which is the K-12/foodservice line and documents no cross-channel matching. Whether a single profile spans POS, first-party web/app and kiosk -- and with what dedup rule -- is therefore undetermined: it would be decided by the external loyalty provider, whose reference Xenial gates behind a per-user 'API Documentation Access' permission in the Genius Portal.

guest-loyalty-thirdparty-identity-attach differentiator

DoorDash, Grubhub and Uber Eats are named direct integration partners under 'Delivery and Online Ordering' on genius-integration-partners.html, and the Omni Channel Ordering discount specification prints the live DoorDash and Uber Eats order payloads, each with a consumer object -- '"consumer": { "id": 46527657, "first_name": "Name", "last_name": "L", "email": ... }' -- alongside applied_discounts carrying promo_id, promo_code and external_campaign_id. The Genius Online Ordering API's CustomerObject likewise carries id ('the user defined unique identifier for the customer record'), names, phone_home/phone_work/phone_cell and email. So usable guest identity does arrive with the order. Shortfall: nothing documents that identity being matched against, or written into, a persistent guest profile. The loyalty account is reached only by an explicit POS Identify Customer call into an external provider, the Customer Loyalty Service exposes no lookup-by-marketplace-order or attach operation, and this discount specification is on the CLASSIC (legacy) Omni Channel product rather than a Genius page. https://www.xenial.com/developer-resources/en/classic-products/omni-channel-ordering/omni-order-discounts-specifications.html · retrieved 2026-08-08

guest-loyalty-accrual-models

Loyalty is delivered largely through named partners Punchh and Como; a CRM/loyalty add-on exists on the smaller Cloud POS packaging. Native accrual models not enumerated. https://www.xenial.com/product-documentation/en/genius-integration-partners.html · retrieved 2026-08-01

guest-loyalty-tiers differentiator

Re-checked 2026-08-08 over both www.xenial.com Paligo portals (product-documentation 786 pages / 3,917 sections and developer-resources 293 pages / 3,333 sections). 'Tier' appears nowhere in a loyalty sense; the only hits are 'VIP area' as a venue product type on ordering-settings/product-list.html and in SuiteSpot marketing. The Customer Loyalty Service customer schema (developer-resources/en/genius-add-on-products/gift-and-loyalty/customer-loyalty-service/operation-definitions/client-integration-endpoints.html) carries balances, rewards, promotions, cards, preferred_tips, referral_code and opt-in flags -- no tier, status or lifetime-spend field -- and the reward object carries id, name, balance, program_id, apply_automatically, calculated_by, associated_points and promotion_type but no tier gating. Consistent with the architecture: 'Provider Integrations - Loyalty rewards rules and calculations are owned by the loyalty provider.' Any rolling-window promotion/demotion would live with Paytronix, Punchh, Como, Givex, Fortress or SVS, whose behaviour Xenial does not publish. Undetermined rather than absent.

guest-loyalty-offline-behavior differentiator

A dedicated developer page enumerates the offline behaviour call by call. Lookup: if the default lookup criterion is code or card number the POS accepts the number, saves it to the order, 'does not prompt the Cashier with a customer profile', 'does not apply loyalty rewards', closes the order and 'sends the Submit Order request using the saved customer identification number for points accrual' -- accrual is deferred, not lost. If code/card are unavailable, 'the POS prompts the Customer or Cashier with the Loyalty Unavailable screen. Loyalty Customer lookups are not allowed if the Rewards System is offline' -- lookup is blocked. Validation: if Rewards Validation times out the POS 'does not convert the offers to rewards', shows an error and asks whether to proceed without the applied offers. Redemption and submission: 'If the Redeem Reward request times out or the POS goes offline, the POS queues the request to retry later... The POS keeps the applied rewards in the order', and the same queue-and-retry applies to Submit Order, which 'keeps the applied rewards and assigned loyalty customer number in the order'. That is an explicit blocked-vs-queue-and-reconcile specification. https://www.xenial.com/developer-resources/en/genius-add-on-products/gift-and-loyalty/customer-loyalty-service/things-to-know--offline-loyalty-rewards-processing.html · retrieved 2026-08-08

guest-loyalty-offer-stacking-rules differentiator

The Rules page of the Discount List editor is the stacking configuration. Precedence: 'Priority -- Type the priority to assign to the discount in relation to other active discounts. If multiple discounts are available, the priority value determines which discount to apply first. A discount with a priority of 1 is applied before a discount with a priority of 2.' Combinability: 'Exclusive Options -- Exclusive Before: Do not apply the discount if another discount is already applied. Exclusive After: Do not allow other discounts (including customer loyalty) once the discount is applied.' Alongside these the same page configures Max Discount Amount, Minimum Order Subtotal, Apply Post Tax, Applies to Modifiers, Applies to Child Items, and a Qualify Criteria page with inclusive item sets (Purchase All in List / Purchase Any in List) and tag-based Exclusive Criteria that disqualify an order. The loyalty engine rides this same surface: redeemReward payloads apply rewards as discounts with discount codes defaultLoyaltyOrderLevelDiscount / defaultLoyaltyItemLevelDiscount, and the Client Integration doc states 'The client defines the rules for whether multiple rewards can be applied to the order or if they are mutually exclusive based on the discount configuration.' https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/discount-list/order-level-discount.html · retrieved 2026-08-08

guest-loyalty-targeted-offers differentiator

Re-checked 2026-08-08 by reading the offer configuration surface itself rather than searching for the phrase. The Discount List editor (product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/discount-list/order-level-discount.html and item-level-discount.html) exposes Availability by site, Order Sources, Time Periods and Destinations, a Schedule with start/end date and time, Qualify Criteria over required item sets and product tags, Roles, Priority and Exclusive Before/After -- every axis is a property of the order or the store, not of the guest. The only guest-side field is a free-text 'Customer Info' prompt ('e.g. military personnel, students, police officers') that reminds the cashier to check ID. There is no audience, list, segment or campaign object anywhere in Data Management, and the Customer Loyalty Service API (developer-resources .../customer-loyalty-service/operation-definitions/) has no segment or audience endpoint. But offer issuance in Xenial's architecture is provider-owned -- 'Provider Integrations - Loyalty rewards rules and calculations are owned by the loyalty provider' -- so a recency/frequency/spend audience would be built in Punchh or Paytronix and arrive as a reward on identifyCustomers. Undetermined for the stack as sold, not shown absent.

guest-loyalty-rfm-segmentation differentiator

Re-checked 2026-08-08 against the enumerated Genius Portal report catalogue -- Sales Reports (85 sections), Inventory Reports (40), Payroll Reports (28), Money Reports and Audit Reports, each of which opens 'The following introduces the reports in the <X> category' and lists every report -- plus Genius Back Office (report-manager.html, kpis.html) and the Venue Inventory dashboard. Not one report in any category is guest- or loyalty-scoped; the closest is Discount Summary, which groups by discount code. The Customer Loyalty Service operation list (developer-resources/en/genius-add-on-products/gift-and-loyalty/customer-loyalty-service/operation-definitions/client-integration-endpoints.html) is complete -- identifyCustomers, redeemReward, submitOrder, voidOrder, addCustomer, updateCustomer, redeemBalance, reverseBalance -- with no segment, cohort or audience operation. I am leaving this unknown rather than no because lifecycle segmentation sits on the provider side of Xenial's split ('Loyalty rewards rules and calculations are owned by the loyalty provider'), so absence from Xenial's own reporting does not establish that the operator lacks it; and Xenial gates the provider-facing reference behind a per-user 'API Documentation Access' permission in the Genius Portal, so the surface is not fully public.

guest-loyalty-lifecycle-automation

Re-checked 2026-08-08 across both portals. The raw material for lifecycle triggers is captured: AddCustomerRequestBody on the Customer Loyalty Service (developer-resources/en/genius-add-on-products/gift-and-loyalty/customer-loyalty-service/operation-definitions/client-integration-endpoints.html) carries customer_details.birth_date, email_opt_in, sms_opt_in and terms_and_conditions_confirmed, and reward objects carry a promotion_type such as 'Welcome Reward'. What is missing is any sending or scheduling surface: Data Management's editors cover discounts, surveys, menus, peripherals and staff, with no campaign, journey, trigger or message-template object; the loyalty API has no campaign or send operation; and no Genius Portal module composes or dispatches guest email or SMS. That is consistent with the documented split in which reward and offer logic is owned by the external provider (Punchh, Paytronix, Como, Givex, Fortress, SVS), so a birthday or win-back automation would be configured and sent there. Undetermined for the deployed stack rather than shown absent.

guest-loyalty-native-email-sms differentiator

Email campaigns are listed as a premium add-on on the Xenial Shell packaging. Native SMS campaigning not documented. https://apps.apple.com/us/app/xenial-shell/id1463045984 · retrieved 2026-08-02

guest-loyalty-consent-management

Consent is captured per channel on the loyalty customer record. AddCustomerRequestBody defines 'customer_details.email_opt_in boolean -- A flag that indicates whether the customer agreed to receive emails', 'customer_details.sms_opt_in boolean -- A flag that indicates whether a customer agreed to receive marketing messages' and 'customer_details.terms_and_conditions_confirmed boolean -- A flag that indicates whether a customer has agreed to the terms and conditions'; UpdateCustomerRequestBody repeats all three as updated_customer_details fields, so consent can be changed after enrolment. Shortfall: the schema records only a boolean state. There is no consent timestamp field, no source-of-consent field, no per-channel revocation record, and no STOP-keyword or revocation handling documented anywhere on either portal -- the only 'opt-out' page in product-documentation is the unrelated Digital Menu Board 'Opt-In/Out of Promotional Content' display setting. Downstream honouring of a revocation would fall to the external loyalty/messaging provider, which Xenial does not document. https://www.xenial.com/developer-resources/en/genius-add-on-products/gift-and-loyalty/customer-loyalty-service/operation-definitions/client-integration-endpoints.html · retrieved 2026-08-08

guest-loyalty-10dlc-registration

Re-checked 2026-08-08 over both www.xenial.com Paligo portals (product-documentation and developer-resources, 1,079 pages / 7,250 sections in total). '10DLC', 'A2P', 'short code' and 'brand registration' occur zero times. There is also no messaging or campaign module to register for: the only SMS-adjacent artefact is the sms_opt_in consent flag on the Customer Loyalty Service customer schema, and guest messaging is owned by the external loyalty provider under the documented split ('Loyalty rewards rules and calculations are owned by the loyalty provider'). Team Portal sends employee email, not guest SMS. So the question is probably not Xenial's to answer, but nothing on either portal says who does carry the registration burden, and the provider-facing reference is gated behind the Genius Portal's per-user 'API Documentation Access' permission. Undetermined.

guest-loyalty-campaign-attribution differentiator

The Discount Summary report ('summarized information about discount totals for selected sites for the specified time range, so that an operator can audit discounted orders') has these columns: Discount Code, Discount Name, Discounts Applied (quantity of discounts applied), Discount Item Quantity, Discount Amount, Net Sales, '% of Net Sales -- Percentage of Net Sales that is attributable to the Discount Amount', Gross Sales, % of Gross Sales, and Completely Discounted Products, grouped by any of business date, site or event. Since a redeemed loyalty reward is applied as a discount carrying its own code (redeemReward payloads use defaultLoyaltyOrderLevelDiscount and defaultLoyaltyItemLevelDiscount, with loyalty_info.offer_id and reward_id attached), redemption counts and redeemed value are reported against real check totals. Shortfall: attribution stops at the discount code. There is no campaign object above the offer, no control or holdout group, and nothing computes incremental sales -- '% of Net Sales attributable to the Discount Amount' is a share of the discounted sales, not lift. Genuine incremental measurement would sit with the external loyalty provider. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/reporting/inventory-reports.html · retrieved 2026-08-08

guest-loyalty-data-export-portability differentiator

Back Office ships an Export Data module; whether guest PII and loyalty ledgers are included, and at what cost, is not documented. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

guest-loyalty-cdp-event-api differentiator

Enterprise Portal documents configurable "Data Stream Endpoints," implying an outbound event stream. No public payload, protocol or subscription documentation. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

guest-loyalty-review-capture-routing differentiator

Post-transaction feedback is triggered natively: 'Use the Customer Surveys editor to manage the survey codes that are automatically generated at the POS for qualifying orders, including the variables used to generate a survey code, and the message to print on the receipt. The customer survey codes enable sites to invite guests to take a survey and provide feedback about their visit and the quality of the service.' The editor has four pages -- General (name, ID, External ID 'used by third-party services to reference the survey', Priority), Availability (active per site, plus conditions on order source, destination, time period and event type), Qualify Criteria (including eligible discounts) and Message & Code. Shortfall: the trigger is all Xenial owns. The survey itself is run by a third-party service referenced through External ID; no response, score or NPS value is captured, stored or reported anywhere in the Genius Portal (no guest-feedback report appears in the enumerated Sales, Inventory, Payroll, Money or Audit report catalogues), and there is no score-based routing to private service recovery or to public review sites. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/customer-surveys.html · retrieved 2026-08-08

guest-loyalty-referral-program

Re-checked 2026-08-08 directly against the Customer Loyalty Service reference on the developer-resources portal, which the earlier pass had not walked. The endpoint list is exhaustive for both integration styles -- identifyCustomers, simulateAccrual, redeemReward, submitOrder, voidOrder, addCustomer, updateCustomer, redeemBalance, reverseBalance -- and the only referral artefact in any of their schemas is 'customer_details.referral_code string No -- The customer's referral code' on AddCustomerRequestBody (it is not even present on UpdateCustomerRequestBody). Product-documentation adds only a 'referral code' entry in the Gift and Loyalty customer update-field list in a release note. A stored field is not a mechanic: nothing generates a per-guest code or link, nothing attributes the referred guest's first order, and no reward is issued to either side. I am not recording this as a no because referral programmes sit on the provider side of the documented split ('Loyalty rewards rules and calculations are owned by the loyalty provider'), so the presence of an inbound referral_code field is more consistent with Punchh or Paytronix running the programme than with nobody running one. Undetermined.

guest-loyalty-wallet-pass differentiator

Re-checked 2026-08-08 across both www.xenial.com Paligo portals (1,079 pages / 7,250 sections). 'Apple Wallet', 'Google Wallet', 'wallet pass' and 'PassKit' occur zero times. The documented identification methods are the full set on the POS Loyalty Transactions page and the Customer Loyalty Service identifyCustomers schema -- phone number, email, first/last name, loyalty card number, code, or a barcode scanned with the barcode scanner or the device camera -- and the customer response object returns balances and rewards for on-screen display, with no pass-issuance or push-update field. Pass issuance would be a function of the external loyalty provider (Punchh, Paytronix, Como, Givex, Fortress, SVS) rather than the POS, and Xenial publishes nothing about provider-side wallet support. Undetermined.

guest-loyalty-privacy-rights-tooling

Re-checked 2026-08-08 on both portals. The Customer Loyalty Service exposes addCustomer and updateCustomer but no delete, erase, anonymise or export operation -- the endpoint list at developer-resources/en/genius-add-on-products/gift-and-loyalty/customer-loyalty-service/operation-definitions/client-integration-endpoints.html is complete (identifyCustomers, redeemReward, submitOrder, voidOrder, addCustomer, updateCustomer, redeemBalance, reverseBalance) and provider-integration-endpoints.html adds only simulateAccrual. On the admin side, Genius Back Office Export Data enumerates its export modules as Cash Sheet, Employees, Inventory, Menu Analysis, Menu Items, Payroll, Product Mix, Purchases, Users and Time Punches -- no guest or customer export -- and no Portal module covers subject access or deletion requests. What stops this being a no is that the guest record itself lives with the external loyalty provider, so deletion would be executed there and propagated by them; Xenial documents neither its own tooling nor the provider hand-off, and gates the provider-facing reference behind a per-user 'API Documentation Access' permission. Undetermined.

guest-loyalty-redemption-fraud-controls

Redeemed loyalty rewards are applied to the check as discounts (the redeemReward payload writes discount codes defaultLoyaltyOrderLevelDiscount and defaultLoyaltyItemLevelDiscount with a loyalty_info block), so the Discount List controls govern redemption: 'Restrict By Roles' with an Authorized Roles list, 'Require Re-Authentication -- Require users to re-authenticate their user credentials in order to apply this discount... provides an additional security check and tracks the employee who applied the discount at the time of payment', Max Discount Amount, Minimum Order Subtotal, and a Comment setting that can be made Required. Velocity monitoring exists in Genius Mobile Manager, whose alert categories include Fraud Detection and Discount: 'Daily discount count exceeds', 'Single employee daily discount count exceeds', 'Single discount exceeds' and 'Discount happens after specific time', each with a configurable threshold. Data Management carries an Audit Trail and Back Office a Store Audit Log. Shortfall: none of this is loyalty-point-aware. There is no redemption-velocity limit expressed in points or rewards, no manager-approval workflow on manual point adjustments (point balances are held by the external provider and the Customer Loyalty Service exposes no adjust operation), and nothing flags an employee redeeming against their own loyalty account. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/discount-list/order-level-discount.html · retrieved 2026-08-08

guest-loyalty-ai-offer-recommendation differentiator

AI-driven upsell recommendation is a shipped drive-thru feature. AI generation of offer content, audience or send timing is not documented. https://www.xenial.com/products/drive-thru-controller/ · retrieved 2026-08-01

guest-loyalty-stored-value-gift

Gift certificate and gift card management in Tender Operations, on an enterprise platform with brand-wide site hierarchy. Packaging caveat: on the smaller Xenial Cloud POS SKU this module is a paid add-on rather than part of the base subscription (per the App Store listing); it is scored here as a documented module of the enterprise Genius platform, where the commercial packaging is not published. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

labor-clock-in-at-pos

Clock procedures documented in the POS app; time clock included in the base app feature set with no separate hardware. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

labor-photo-punch-verification differentiator

Re-checked 2026-08-08 by reading the punch surface itself rather than searching phrases. Clock Procedures (product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-pos-app/clock-procedures.html) documents Sign On, Sign Out, Change PIN, Confirm Drawer Assignment, Clock In, Clock Out and Start/End Break in full, and every step is User ID plus PIN with a job selection -- no image capture, no verification prompt. The only biometric on either portal is a fingerprint reader: the Peripherals editor lists 'Fingerprint Reader (USB)' among its creatable device types and company/site Preferences carry 'Use Biometrics -- Select this option if a biometric fingerprint reader device is used at the site to grant users access to the POS application', with a configurable Biometrics License Agreement the user must accept. That is template-based fingerprint access control for sign-on, which is the opposite of the claim's photo-only, no-template mode. The Peripherals table does include a 'Camera (LAN)' type, but nothing ties it to timekeeping. I am leaving this unknown rather than no because the Peripherals table enumerates devices rather than timecard features, and Genius Back Office Time Card Entries does not publish its full field list, so a photo attachment on the timecard record cannot be ruled out from what is published.

labor-geofenced-mobile-punch

Re-checked 2026-08-08 across both portals. 'Geofence', 'geo-fence' and 'location validation' occur zero times in a timekeeping context (the sole geolocation hit is an LG ConnectedCare firewall hostname on a digital-menu-board installation page). Team Portal (product-documentation/en/genius-back-office/team-portal.html, 26 sections) is the only employee-facing mobile surface and its enumerated team-member functions are Schedules, Shift Bar Colors, Shift Indicators, View Shift Details, Offer Shift, Available Shifts, Pick Up Shift, Hours Worked, View Work Details, Time Off and Logout -- viewing hours worked, never recording them. Clock Procedures puts every punch at a terminal ('Employees can clock in/out from a terminal without requiring the user currently signed on to the terminal to sign out'), and Genius Mobile Manager is a manager analytics app (Key Stats, Alerts, Reports, Order Search, Purchase Orders, Transfers) with no clock function. So mobile punch itself appears not to exist, which would make the geofence question moot -- but a menu listing is not a statement of completeness, so this stays unknown rather than no.

labor-offline-time-punch differentiator

Time clock is part of the local app set that keeps running offline up to 30 days, so punches should persist — but reconciliation and duplicate handling are not documented. https://apps.apple.com/us/app/xenial-shell/id1463045984 · retrieved 2026-08-02

labor-granular-rbac

Enterprise Portal User Management provides roles, permissions and user groups, scoped by site hierarchy. Per-discrete-action granularity not fully enumerated. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

labor-manager-override-audit

Manager Procedures and employee functions are documented; immutable, queryable override audit trail is not. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

labor-native-scheduling differentiator

Re-cited on 2026-08-02 verification, replacing an inference from the Projections module with the scheduling module itself. The Team Portal documentation states team members "view and manage their respective shifts for a Back Office labor schedule" and receive email notification "when managers publish a new schedule" — an authored, published, employee-visible labour schedule. Projections separately determine how many employees to schedule per Job per day. Packaging caveat: on the smaller Xenial Cloud POS SKU scheduling is a paid add-on rather than part of the base subscription; scored here as a documented module of the enterprise Genius platform. https://www.xenial.com/product-documentation/en/genius-back-office/team-portal.html · retrieved 2026-08-02 adversarially verified

labor-demand-labor-forecast differentiator

Projections "enable Back Office to determine the number of employees to schedule for each Job for each day based on the sales or counts the store is projected to generate", off a four-week trend with daily, daypart and 30-minute detail levels. Direct fetch of xenial.com/product-documentation returns the navigation tree only (body text is client-rendered); the quoted text is from the public search index of this page. https://www.xenial.com/product-documentation/en/genius-back-office/projections.html · retrieved 2026-08-02 adversarially verified

labor-realtime-labor-percent differentiator

Back Office KPIs and Mobile Manager surface labor metrics off-premise; true in-service real-time labor percentage on a manager view is not documented. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

labor-overtime-prevention differentiator

Shortfall: the warning fires at shift-request/schedule-approval time, not at clock-in. The Pending Shift Changes page documents warning icons next to a shift-pickup request: a red 'OT' label appears when 'the total number of scheduled hours for the employee exceeds the defined Overtime Warning Limit', alongside a purple 'M' (minor) and orange 'H' (ACA-eligibility-threshold) icon. This is a scheduling-time warning to the manager approving a shift-pickup request, not a block or warning presented to the employee at the POS clock-in screen before overtime is incurred. Retrieved from the product-documentation full-text search index. https://www.xenial.com/product-documentation/en/genius-back-office/labor/pending-shift-changes.html · retrieved 2026-08-04

labor-break-compliance-by-state differentiator

Shortfall: no per-state rule library and no break attestation. What IS documented: the Back Office Break Time editor defines break types with eligibility thresholds ('the total number of minutes the employee must work before they are eligible for the break'), paid/unpaid status and minor-specific return-early enforcement, warning 'It may be necessary to disable this setting to ensure local labor laws are enforced'; a Missed Breaks payroll report lists 'exceptions in regards to employee breaks associated with assigned shifts'; and Mobile Manager labor alerts include 'Employee is owed missed breaks penalty — when employee is owed "premium pay" due to missed break', with the page quoting California Labor Code section 226.7's one-additional-hour-of-pay rule verbatim. So missed-break premium flagging is shipped and CA premium pay is contemplated by name. But break rules are values the operator configures per company/site — no state or jurisdiction preset library is documented — and 'attest' occurs nowhere in any corpus, so required break-attestation prompts are not documented. https://www.xenial.com/product-documentation/en/genius-mobile-manager/enterprise-mobile-manager/settings/preferences.html · retrieved 2026-08-04

labor-fair-workweek-support

Shortfall: only the clopening/rest-hours rule is documented; advance-notice deadline tracking and predictability-pay calculation are not. The Business Rules Schedule group documents 'Restrict Clopenings' explicitly as ordinance compliance: 'Enforce local and state ordinances around Fair/Predictive Scheduling practices. \"Clopenings\" refers to the practice of scheduling the same employee for a closing shift and a subsequent opening shift on a consecutive day. Employees must have at least X number of hours bet[ween]...' (with a separate business rule elsewhere noting 'In most states, this number is 11'). No page documents tracking of advance-schedule-publish deadlines or calculating predictability pay owed for employer-initiated changes. Retrieved from the product-documentation full-text search index. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/staff-settings/business-rules.html · retrieved 2026-08-04

labor-minor-labor-rules

Shortfall: clock-in enforcement is not documented. What IS documented: a Labor Law business-rule group with minor-labor limits — Max Hours School Day / School Week / Non-School Day / Non-School Week, and Start/End Time for School and Non-School Days ('the time of day when an employee must end work on a scheduled school day'); Back Office Labor ships a School Districts editor with per-district school-year calendars and school-day start/end times; schedule views filter Minors / No Minors; and the Break Time editor enforces break-return rules specifically for minors at the POS ('Toggle Off to NOT allow minors to return early from breaks... It may be necessary to disable this setting to ensure local labor laws are enforced'). The scheduling side and minor break enforcement are solid, but no page states that clock-in is blocked when a minor is outside permitted time windows or over hour caps, and how employees are flagged as minors (age-derived from birth date, or manual) is not described. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/staff-settings/business-rules.html · retrieved 2026-08-04

labor-tip-pooling-rules

Shortfall: same as payments-tip-pooling -- a binary 'Tips Allocation Method: Individual / Tip Pooling' toggle and 'Automatic Charge Tips Calculation' per shift are documented, plus a Tips Allocation Summary payroll report, but no configurable computation rule by percentage of sales, hours worked, points or role is documented anywhere in the corpus. Retrieved from the product-documentation full-text search index. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/preferences/site-preferences.html · retrieved 2026-08-04

labor-tip-distribution-audit-trail

Shortfall: no explicit contributed-to-pool vs distributed-from-pool breakdown. The Payroll Reports documentation names a 'Tips Allocation Summary' report showing per-employee allocated tips together with clock in/out times, and a 'Total Tips' column on the Payroll Hours and Wage Detail report. This is a per-employee, exportable tip record, but no page distinguishes amounts an employee contributed to a pool from amounts distributed to them from it -- the report shows allocated (i.e. distributed) totals only. Retrieved from the product-documentation full-text search index. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/reporting/payroll-reports.html · retrieved 2026-08-04

labor-qualified-tips-w2-reporting differentiator

Re-checked 2026-08-08 against the payroll surface on both portals. The Payroll report catalogue (product-documentation/en/genius-point-of-sale/enterprise-pos/reporting/payroll-reports.html) opens 'The following introduces the reports in the Payroll category' and lists all nine: Employee On The Clock, Employee Time Punch Sign-Off, Labor Performance Summary, Missed Breaks, Payroll Hours Detail, Payroll Hours and Wage Detail, Payroll Summary, Timecard Audit and Tips Allocation Summary. None mentions W-2 boxes, a tipped-occupation code, or a qualified-tip split. Genius Back Office Export Data offers a single 'Export Payroll' producing a named flat file (example 'Hours.csv') with no documented column list, so the export's tip columns cannot be inspected from published material. The only place cash and charged tips are separated in the documentation is the LEGACY Classic line: the IRIS POS clock-record form has distinct 'Cash Tips' and 'Charge Tips' fields (product-documentation/en/classic-products/iris-pos/clock-in-out-adjustments.html). '10DLC'-style specificity is simply absent here: 'W-2', 'Box 12', 'tipped occupation' and 'qualified tip' occur zero times in 7,250 sections, and the Genius release notes carry nothing on the 2026 tip provisions. Undetermined: the export column list is unpublished, so I cannot say the split is missing.

labor-native-payroll differentiator

Payroll in Xenial's own products is an export, not a payroll run. Genius Back Office Export Data enumerates its export types -- Cash Sheet, Employees, Inventory, Menu Analysis, Menu Items, Payroll, Product Mix, Purchases, Users and Time Punches -- and the Payroll path is a file handoff: 'From the Export dropdown, select Payroll. In the Payroll Export File field, type a file name for the data export file, including the file extension (e.g.: Hours.csv)', with an Export Payroll button and a stored default file name. Staff Settings business rules speak the same way ('Salary Employees Included in Payroll Export'). The Payroll report category is enumerated in full at reporting/payroll-reports.html and comprises nine hours/wage/audit reports with no pay run, no tax filing, no direct deposit and no payment register. Neither portal (786 + 293 pages) documents Xenial disbursing wages, filing employment taxes or originating direct deposits; the one direct-deposit artefact anywhere is a bank-account field on the LEGACY IRIS POS employee record, which feeds an outside payroll system. Scope note: this is about Xenial's documented product line, not about other Global Payments brands sold separately. https://www.xenial.com/product-documentation/en/genius-back-office/export-data.html · retrieved 2026-08-08

labor-payroll-export-formats

Payroll connections referenced and Back Office has an Export Data module; no two named payroll providers documented. https://apps.apple.com/us/app/xenial-shell/id1463045984 · retrieved 2026-08-02

labor-shift-swap-workflow differentiator

Shortfall narrowed on 2026-08-02 verification. Open-shift pickup with manager approval IS documented, contrary to the prior note: the Pending Shift Changes page describes store managers viewing "pending employee shift pickup requests for a selected store and period" and approving or declining them. Still partial because two components remain unevidenced — employee-to-employee shift trades as distinct from claiming an unassigned shift, and any overtime guardrail applied at approval time. https://www.xenial.com/product-documentation/en/genius-back-office/labor/pending-shift-changes.html · retrieved 2026-08-02 adversarially verified

labor-digital-onboarding-i9

Shortfall: these are classification/reference fields, not a document-collection or E-Verify submission workflow. Employee Records documents 'I-9 Document Classes' ('employee identification documents... available for selection when adding employee records'), 'I-9 Statuses' ('used to identify the status of an employee's legal authorization to work in the United States') and 'W-4 Filing Statuses' as configurable reference-list objects attached to an employee record. No page describes collecting or uploading I-9/W-4 documents, a self-service new-hire onboarding flow, or E-Verify submission -- the documented mechanism is status tracking, presumably populated after paperwork is completed elsewhere. Retrieved from the product-documentation full-text search index. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/staff-settings/employee-records.html · retrieved 2026-08-04

labor-server-performance-metrics differentiator

POS Reporting and Back Office KPIs exist across hundreds of data points; a per-server scorecard with void/comp rate is not specifically documented. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

inventory-recipe-bom-costing

Standardized recipes with precise ingredient measurements drive usage and food cost. Multi-level sub-recipes and automatic plate-cost recalculation on ingredient cost change not documented. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

inventory-unit-conversion-yields

Shortfall: unit-of-measure conversion is documented — "for each inventory location, inventory items can be counted by Cases, Inners, or UOMs", and items that "come in varying case counts ... should always be added in UOMs". But recipe YIELD percentages and waste-adjusted yields are not documented, so only half the claim is evidenced. Citation corrected: the previously cited resources.xenial.com URL returns HTTP 404; the live path is on www.xenial.com. Direct fetch of xenial.com/product-documentation returns the navigation tree only (body text is client-rendered); the quoted text is from the public search index of this page. https://www.xenial.com/product-documentation/en/genius-back-office/food/inventory-counts.html · retrieved 2026-08-02

inventory-theoretical-vs-actual differentiator

Re-cited on 2026-08-02 verification because the previously cited module root returns navigation only. Back Office Report Manager lists a "Weekly Food Variance Report", and the Back Office reporting documentation describes diagnosing "the root causes of large variances in actual and ideal food usage, excessive waste, high food-cost percentages, lapses between actual and target yields". Actual-versus-ideal usage variance is a named shipped report. Packaging caveat: on the smaller Xenial Cloud POS SKU this module is a paid add-on rather than part of the base subscription (per the app-store listings); scored here as a documented module of the enterprise Genius platform, whose commercial packaging is not published. https://www.xenial.com/product-documentation/en/genius-back-office/report-manager.html · retrieved 2026-08-02 adversarially verified

inventory-realtime-depletion differentiator

Sales-driven depletion is documented in the Venue Inventory add-on. Venue Inventory 'automatically syncs with Data Management and our other cloud services to display the most up-to-date information such as Item Inventory and Unit Costs', an inventory item added mid-event 'appears on the stand worksheet Entry Form for the site after the transfer is completed or a sales order for the item is tendered', and 'if a site is not added to an active event, but a site terminal processes orders during the sales times for the event, a stand worksheet is initialized and reflects the inventory items consumed by those sales orders'. Depletion is recipe-driven: the Recipe module links ingredients (with quantity, measure and yield) and recipes-as-ingredients to products, the chargeable item is 'the inventory item that is counted during stand worksheet operations', a Sale Depletion Order API carries per-order sale information into Venue Inventory, and a Recipe Depletion report 'provides details about inventory item depletion/usage amounts in recipes'. Modifiers are in scope: the Modifier editor has a Venue Inventory page displaying 'linked recipes and chargeable items -- sub-recipes are detailed by their individual ingredients'. Shortfall: this is the stadium/venue add-on and its unit of work is the event, with post-closure order handling (is_post_closure) explicitly supported. The mainstream restaurant path, Genius Back Office Food, is periodic instead -- inventory counts are taken Daily, Weekly or Period and 'determine the actual usage of each raw item, which is then used to report raw item variance', with only one count kept per day -- and no documentation states a per-order depletion latency for it. https://www.xenial.com/product-documentation/en/genius-add-on-products/venue-inventory/venue-inventory-overview.html · retrieved 2026-08-08

inventory-86-auto-sync differentiator

Cross-channel propagation is documented and automatic. 'Menu Engine can track the availability of individual menu items at each site using the out_of_stock flag... Sites typically use the out_of_stock flag to signal when they have run out of the ingredients required to stock an item.' When an employee marks an item unavailable at the POS, 'the Menu Engine API sends a stockout notification to the Stockout URL specified by the integrator' -- a PUT carrying company_id, site_id, order_source_ids, product_id and is_available:false -- and 'when new menus are generated, the items on the menu are also marked as out_of_stock', with a reverse notification on restock. Integrators enable this with enable_stockout_notifications and stockout_url on their menu subscription. On the POS side, Item Availability can be toggled from Functions, from a long press at Order Entry, or from Product Details, and an unavailable item 'cannot be added to an order'. Shortfall: the trigger is human. 'Integrators do not set the value of out_of_stock directly; instead, the employees at the point of sale change the availability status of each item dynamically to reflect the stock of items at their site.' No documentation ties out_of_stock to a component ingredient reaching zero or a configured threshold -- Venue Inventory's Min/PAR/Max thresholds drive replenishment and ordering, not menu 86ing. https://www.xenial.com/developer-resources/en/genius-point-of-sale/enterprise-pos/menu-engine/item-availability.html · retrieved 2026-08-08

inventory-count-modes

Shortfall: variance validation is documented — "The Validate button on the Inventory Count screen compares counted items to what is expected to be in stock, and helps to pinpoint amounts that fall outside an expected variance" — and counts can be taken by Cases, Inners or UOMs per inventory location. But distinct spot-count and cycle-count modes are not documented. Citation corrected from the resources.xenial.com path, which returns HTTP 404. Direct fetch of xenial.com/product-documentation returns the navigation tree only (body text is client-rendered); the quoted text is from the public search index of this page. https://www.xenial.com/product-documentation/en/genius-back-office/food/inventory-counts.html · retrieved 2026-08-02

inventory-mobile-count-offline

Re-checked 2026-08-08 by walking both counting surfaces and the mobile app. Genius Back Office Food Inventory Counts is a web form: select site, business date and a Daily/Weekly/Period view, pick a Location (Stock Room, Cooler, Freezer) and type a Count per packaging unit, with a Validate button that flags counts outside an expected variance -- no scanning step and no offline statement. Venue Inventory Inventory Counts and the Stand Worksheet are Genius Portal screens with the same shape; the Inventory Item record does carry a UPC Code Mapping field populated by scanning, but that is item setup in the Portal, not a count workflow. Genius Mobile Manager (27 pages) enumerates its modules as Home, Alerts, Flexible Chart, Key Stats, Order Search, Purchase Orders, Reports, Transfers and Settings -- no inventory counting, no scanner. Nothing on either portal describes count entry continuing without connectivity or syncing on reconnect; the only store-and-forward documented anywhere is FreedomPay payment SAF. I am leaving this unknown rather than no because a page tree is not a completeness assertion and a tablet browser reaching the Back Office form is not ruled out -- but no counting app with barcode scanning and offline capture is published.

inventory-vendor-catalogs-edi differentiator

Electronic ordering and invoicing both exist. On the Order form: 'Send Order -- Transmit the order online. To use eOrdering, the vendor must be a Back Office Supply Chain Partner', with order Status moving to Placed and then through vendor-set values Pending, Process, Invoiced, Shipped, Out for Delivery, Not Delivered and Delivered. Orders can be system-calculated (Quantity On-Hand + Projected Usage until next order date - Quantity Ordered in transit, honouring each item's Order Based On setting). On the receiving side, Food Purchases is 'used to receive electronic invoices and add manual invoices': a Receive Delivery function 'receive[s] invoices from vendors that are set up for electronic invoicing', an eInvoice? column marks electronically ordered purchases, an Unlinked? column flags inventory items not yet mapped to the vendor's equivalent item, and adjustments to an eInvoice append '-ADJ' to the invoice number. Each vendor carries Standard Inventory Items that load as a default order guide, and inventory items map to vendor items with a preferred-vendor indicator. Shortfall: no distributor is named. Neither portal (786 + 293 pages) mentions Sysco, US Foods, Performance Food Group or any other broadline supplier, and the eligible set is described only as 'Back Office Supply Chain Partners' with no published list, so the pre-built-catalog half of the claim cannot be confirmed for any named vendor. https://www.xenial.com/product-documentation/en/genius-back-office/food/orders.html · retrieved 2026-08-08

inventory-invoice-ocr differentiator

The Purchases utility declares its own complete scope: 'Use the Purchases utility to receive electronic invoices and add manual invoices.' Both paths are then given in full. Electronic: 'Receive Delivery -- Receive invoices from vendors that are set up for electronic invoicing', an EDI-style feed from a Back Office Supply Chain Partner whose only failure notes are 'Unlinked Items' and 'There is no electronic invoice for this order'. Manual: the Add Purchase form's field table is Store, Vendor, Invoice Date, Invoice Number ('the invoice number from the vendor's paper invoice'), Date Entered, Balance Amount, Approved, Comment and Load Default Items, then per line Item, Qty, Cost ('the last unit cost recorded for this item appears; if there has been a price change... type the new unit cost here'), Total Cost and UOM/Case. There is no file upload, no attachment, no photo capture, no PDF or email ingestion, and no extraction or review queue in the utility, on the Receive Delivery form, or anywhere in the enumerated Genius Portal inventory tooling -- the paper invoice is retyped. Genius Mobile Manager's modules include Purchase Orders but no invoice capture. https://www.xenial.com/product-documentation/en/genius-back-office/food/purchases.html · retrieved 2026-08-08

inventory-price-change-alerts differentiator

The alerting surface is enumerated exhaustively and contains no price alert. Mobile Manager Preferences states 'The following identifies the Mobile Manager alert categories: Application, Check, Discount, Fraud Detection, Inventory, Labor, Sales, Tip, Void', and gives each category's full table of alert, trigger and configurable value. Inventory Alerts consists of exactly two: 'If new pending transfer is awaiting approval' and 'If new Purchase Order is created' -- neither price-related, and neither threshold-valued. The reporting surface says the same: the Inventory report catalogue ('The following introduces the reports in the Inventory category') lists all seventeen reports -- Discount Summary, Inventory Cost of Goods Sold, Inventory Count, Inventory Item Listing, Inventory on Hand, Inventory Purchase Summary, Order Summary, Physical/Terminal Sales, Physical Sales Accounting, Product Listing, Recipe Depletion, Sales Detailed, Sales Over Short, Stand Worksheet Closing, Transfer Summary, Transfers by Item, Transfer Pick Sheet -- with no per-item purchase-price-history or price-variance report. What price memory exists is single-valued and passive: on Add Purchase the Cost field shows 'the last unit cost recorded for this item... if there has been a price change for this item, type the new unit cost here', and Transfers cost items by LIFO from the most recent purchase or transfer. No contracted price is stored to compare against and no threshold can be configured. https://www.xenial.com/product-documentation/en/genius-mobile-manager/enterprise-mobile-manager/settings/preferences.html · retrieved 2026-08-08

inventory-par-auto-suggest differentiator

Projections are described as critical to calculating accurate inventory orders for vendors — a forecast-driven suggestion path. Static par levels per item per location not documented. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

inventory-waste-logging

Waste cost is reported and diagnosable in Back Office. A structured reason-coded waste entry workflow is not documented. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

inventory-transfers

Inventory application supports transfers in and out alongside physical counts and invoice receiving. Two-sided in-transit/approval state not detailed. Packaging caveat: on the smaller Xenial Cloud POS SKU this module is a paid add-on rather than part of the base subscription (per the App Store listing); it is scored here as a documented module of the enterprise Genius platform, where the commercial packaging is not published. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

inventory-commissary

Site-to-site issue at a computed cost is documented. 'Transfers -- inventory items moved from one site to another -- must be added to a site's inventory to allow for an accurate account of food costs, actual usage, and waste', with statuses Pending, Accepted and Rejected, single and multi-item entry, and a receiving-site accept/reject step for In Company transfers ('Only Accepted transfers appear on reports'; Out of Company transfers are auto-Accepted). Cost is computed, not typed: 'Back Office references the item cost from the most recent purchase/transfer record. If the item was transferred multiple times, the Last-In-First-Out accounting method is used', surfaced as a Calculated Cost field with an optional, permission-gated Override. Venue Inventory has a parallel Transfer module with warehouse-to-stand transfers, transfer groups and templates and replenish-to-par. Shortfall: the production half is missing. Neither engine documents a central kitchen producing prep items -- there is no production order, batch/build, assembly or yield-on-production function anywhere in Genius Back Office Food or Venue Inventory; recipes exist only in Venue Inventory and are consumed by sales, not manufactured into stock. The one 'commissary' term on either portal is Venue Inventory's 'Commissary Assignment', a Hawker Manager staffing assignment for a stadium event, not a production kitchen. https://www.xenial.com/product-documentation/en/genius-back-office/food/transfers.html · retrieved 2026-08-08

inventory-lot-traceability

No lot or batch identity exists anywhere in the data model. The Venue Inventory Inventory Item editor enumerates the item's entire configurable surface as six pages -- Availability, General (name, description, ID, GL account, Show on Stand Worksheet, UPC Code Mapping, tags), Measures, Recipe Information, Reporting, Vendors -- with no lot, batch or serial field, and the list view's columns are ID, Name, Major Category, Chargeable, Show on Stand Worksheet, UPC Code Mapping, Modified Date and Entity ID. Genius Back Office's Store-Level Inventory Item Settings likewise enumerates every item setting -- Minimum to Order, Fixed Usage per Week, Order Available Delay, Usage per Customer, Safety Factor, PAR, Order Basis, Per $1000 Sales -- with nothing lot-related. Capture at receiving is equally closed: the Add Purchase line fields are Item, Qty, Cost, Total Cost and UOM/Case, and Receive Delivery's only per-invoice notes concern unlinked items and missing eInvoices. Costing runs on LIFO by transaction date rather than by identified lot, and the enumerated seventeen-report Inventory catalogue contains no traceability or recall report. 'Lot number', 'batch number' and 'traceability' occur nowhere in the 7,250 sections of either portal. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/venue-inventory-settings/inventory-item.html · retrieved 2026-08-08

inventory-shelf-life-expiry

Neither the capture nor the surfacing side exists. Dates on a received purchase are commercial only -- the Add Purchase field table is Store, Vendor, Invoice Date, Invoice Number, Date Entered, Balance Amount, Approved, Comment, Load Default Items, and per line Item, Qty, Cost, Total Cost, UOM/Case -- with no expiration or use-by field; the Order form's three dates are Order Date, Delivery Date and Available Date, the last defined as when the product can begin to be used, not when it expires. The inventory item's whole configurable surface carries no shelf-life attribute in either engine (Venue Inventory: Availability, General, Measures, Recipe Information, Reporting, Vendors; Back Office store-level: Minimum to Order, Fixed Usage per Week, Order Available Delay, Usage per Customer, Safety Factor, PAR, Order Basis, Per $1000 Sales). On the output side the Inventory report catalogue is enumerated in full ('The following introduces the reports in the Inventory category') across seventeen reports with no expiring-soon or spoilage report, and Mobile Manager's complete alert-category list gives Inventory exactly two alerts, both about transfers and purchase orders. Waste is recorded after the fact through Raw Waste/Promo and Menu Waste/Promo rather than predicted. Every genuine 'expiration' hit in 7,250 sections concerns WEB-SRM digital certificates for Quebec fiscal compliance. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/reporting/inventory-reports.html · retrieved 2026-08-08

inventory-cogs-gl-export

Back Office has a dedicated Export Data module; no named accounting-system format or configurable GL account mapping is documented. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

inventory-native-not-partner differentiator

Inventory, recipes and food cost are native Back Office modules from Xenial, not a separately contracted third party. Packaging caveat: on the smaller Xenial Cloud POS SKU this module is a paid add-on rather than part of the base subscription (per the App Store listing); it is scored here as a documented module of the enterprise Genius platform, where the commercial packaging is not published. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

inventory-menu-margin-linkage differentiator

Food-cost percentage and usage variance are reported against sales. Per-item contribution margin with a configurable threshold flag is not documented. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

reporting-realtime-dashboard

Back Office is browser-based and accessible from anywhere including mobile devices; a Genius Mobile Manager app and Portal Dashboard exist. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

reporting-eod-closeout

End of Day procedures plus drawer assignment, reconciliation and closing, and a Back Office Cash module. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

reporting-pmix-modifier-level

Reporting suite spans hundreds of data points with daypart as a first-class dimension; modifier-level PMIX is not specifically documented. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

reporting-comps-voids-audit

POS Reporting and Manager Procedures cover refunds and discounts; a dedicated attribution report naming applier and approver with reason codes is not documented. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

reporting-cash-over-short

Back Office Cash module plus POS drawer functions (assignment, reconciliation, closing) and drive-thru drawer assignments. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-pos-app/manager-procedures/drawer-functions.html · retrieved 2026-08-01

reporting-labor-productivity

Back Office Labor module and KPIs, with a labor matrix determining ideal labor cost, computed against POS time-clock hours. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

reporting-channel-profitability differentiator

Shortfall: no commission netting and no margin. Order Source is a first-class reporting dimension - the Order Source editor carries an Is Marketplace toggle ("The third party remits tax when sales are made via a Marketplace facilitator source (order source associated with facilitator (eg. Uber Eats/Doordash))"), an Is Tax Liable sub-toggle, and an Order Source selector on each delivery service "to filter out orders from the provider on reports and designate specific menus for the provider"; Sales reports additionally break out Net/Gross Sales per order destination (Category Sales per Site, Employee Audit "Destination Sales", Labor Performance: Destination). So revenue IS separable by dine-in / online / each marketplace. But nothing in the enumerated Reports categories (Audit, Inventory, Money, Payroll, Sales) reports margin, and no marketplace commission or fee field exists anywhere in the order object or the reporting columns - the only "Commission Rates" module in the corpus is stadium hawker commission under Venue Inventory Settings. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/order-source.html · retrieved 2026-08-08

reporting-multiloc-drilldown differentiator

Reporting explicitly spans a single site or an entire franchise, over a site hierarchy with tags. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

reporting-custom-report-builder differentiator

Back Office ships a "Report Manager" module; whether it is a true dimension/measure self-service builder or a canned-report organizer is not documented. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

reporting-scheduled-delivery

Report Manager exists and Back Office has Tasklists; recurring scheduled email delivery with recipient lists is not explicitly documented. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

reporting-raw-warehouse-export differentiator

Portal "Data Stream Endpoints" plus a Back Office Export Data module suggest automated outbound feeds; destinations (S3/SFTP/Snowflake) and scheduling are not documented. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

reporting-public-api differentiator

CORRECTION: the 2026-08-01 record scored this "no". The developer-resources site publishes a Genius Back Office API section — "Back Office API Getting Started", "Things to Know", "Connect to Back Office API" and "Back Office APIs" — over the product that owns sales, inventory and labour reporting. Shortfall: the endpoint list, available report entities, fields, granularity and history depth were not retrievable, so programmatic reporting access is demonstrably published but unspecified. https://www.xenial.com/developer-resources/?lang=en · retrieved 2026-08-02

reporting-webhooks differentiator

Shortfall: no payload signature and no documented retry policy. The Data Stream API is a fully documented outbound webhook service - it "publishes JSON formatted objects to a configurable webhook URL", the endpoint is customer-supplied in Genius Portal > Settings and Tools > Data Stream Endpoints (Type HTTP or SQS, Target endpoint, Validate Connection), and Order objects covering payment detail are pushed on state transition. But authentication is a static optional bearer string the customer types in, and the docs state plainly: "the service does not support an Authentication step, nor is there a process to refresh the token periodically" - there is no HMAC or any payload signature to verify. No retry, backoff or delivery-guarantee behaviour is documented; the only recovery documented is a manual Resend Data action in the Portal, and an ordering guard ("relevance_key": "_id,time.last_modified") that suppresses stale copies. https://www.xenial.com/developer-resources/en/genius-point-of-sale/enterprise-pos/data-stream/data-stream/setup.html · retrieved 2026-08-08

reporting-api-not-upcharged differentiator

Checked 2026-08-08 against both Paligo portals dumped in full (1,079 pages / 7,250 sections). The developer-resources portal documents how API access is GRANTED but never what it costs: getting-started-with-apis.html lists the prerequisites (completed NDA and Developer Licensing Agreement, account-manager confirmation, an integrator token generated by Xenial), and Portal Company Settings gates each data service as a per-company subscription/service toggle - but no page states whether API or raw-data access carries a fee, a per-location charge, or a plan tier. Separately, Genius API documentation itself is a per-user Portal permission ("API Documentation Access"), so the commercial terms sit behind the customer relationship. Nothing on www.xenial.com outside /product-documentation/ and /developer-resources/ publishes pricing of any kind for this enterprise-quote vendor. Unresolved because absence of a published price is not evidence that access is included.

reporting-tier-paywall differentiator

On the Cloud POS packaging, reporting sits in the base subscription while inventory, scheduling, CRM and loyalty are paid add-ons — so basic reporting is not paywalled but adjacent analytics are modular. https://apps.apple.com/us/app/xenial-shell/id1463045984 · retrieved 2026-08-02

reporting-history-retention differentiator

Re-checked 2026-08-08 across the full two-portal dump for retention, retain, purge, archive and month/year-of-history phrasing. The only retention statements in the corpus are unrelated to this claim: Revenu Quebec WEB-SRM fiscal-data archiving for Quebec compliance; a Kitchen Settings "Days To Keep Logs" field for application logs; and Suite Catering's Archived Order List rule ("an order is classified as archived if its associated event occurred 60 days ago and the order itself was closed 60 days ago"), which is a catering-module archive, not the reporting UI. Genius Portal Reports (Audit, Inventory, Money, Payroll, Sales, Order Explorer) and Back Office Report Manager / KPIs all take a free date or date-range selector with no stated bound, and Back Office export-data and Report Designer say nothing about a horizon. No transaction-level retention window - and no statement that there is none - is published either way.

reporting-anomaly-alerts differentiator

Checked 2026-08-08 every alerting surface in both portals. Genius Back Office KPIs has a Notifications section on the Store KPIs page, but the docs describe only viewing "store notifications ... with their respective date" - no page documents defining the condition that raises one. Data Management > Ordering Settings > Digital Notifications is the only template-driven notification engine and its Event Types are guest-facing (Order Confirmation, Receipt, Refund), delivered by email/SMS to the customer. Back Office Tasklists are checklist workflows. The Reports Dashboard is configurable to eight Key Stats but is a view, not a trigger. Nothing found lets an operator set a metric threshold or a deviation-from-history rule and receive a push or email; equally, no page rules it out, and Xenial's Report Designer custom-report utility was not exhaustively enumerated. Unresolved.

reporting-nl-query

Re-checked 2026-08-08 across the full two-portal dump of xenial.com (1,079 pages / 7,250 sections): "natural language", "AI assistant", "chatbot", "artificial intelligence" and "copilot" return zero genuine hits, and every documented reporting entry point is a parameterised canned report, a Report Designer template, Order Explorer order search or the fixed Sales Dashboard. That is absence of evidence rather than evidence of absence: the Reporting Overview page previously relied on is a walkthrough of the Reports homepage whose category list is introduced with "The report categories include:", which claims no completeness, and a conversational analytics product would not necessarily be documented inside the Enterprise POS reporting manual. No launch, release note or dated announcement of a Xenial natural-language or AI query capability was found on the web either. Unresolved.

reporting-guest-cohorts differentiator

Re-checked 2026-08-08 against the enumerated Reports catalogue in both portals rather than by keyword alone. The Sales category (30 reports), Audit (6), plus Money, Payroll, Inventory, Order Explorer and Back Office Report Manager / KPIs contain guest COUNTS and per-guest averages (Guest Count, GCA, Guests Per Labor Hour, Average Net Sales per guest) but no report keyed to an identifiable guest record. Portal > Accounts > Guests and Accounts holds guest account records and rewards registration, and Suite Catering has its own guest user lists, but no page ties those records to new-versus-returning counts, visit frequency or lifetime spend. Loyalty is delivered by third-party providers (Punchh, Paytronix, Como, Givex, Sparkfly, SVS, Fortress, Mirego) whose own platforms would hold that analysis. Left unknown rather than no because Back Office Report Designer builds custom reports whose available fields are not enumerated.

reporting-sales-forecast differentiator

Back Office "automatically calculates the sales trend for each date in the projection based on the previous four (4) weeks' sales figures", exposed on a Trend Dates tab. Daily Projections, Day Part Projections and Detail Projections (30-minute intervals) build on it, and feed both labour scheduling and vendor inventory orders. Direct fetch of xenial.com/product-documentation returns the navigation tree only (body text is client-rendered); the quoted text is from the public search index of this page. https://www.xenial.com/product-documentation/en/genius-back-office/projections.html · retrieved 2026-08-02 adversarially verified

reporting-tip-tax-compliance

Shortfall: no declared-vs-charged comparison and no tip tax liability summary by jurisdiction. What IS documented: Back Office Staff preferences include 'Automatic Charge Tips Calculation — automatically calculate employee tip amounts based on the respective orders during their shift' and a Tips Allocation Method of Individual or Tip Pooling; job codes carry a tip category (Yes = direct, Indirect = 'through either tip pooling or tip splitting', No); the Payroll Hours and Wage Detail report carries Total Tips per employee; the Tips Allocation Summary report shows per-employee allocated tips with clock in/out times; Money Reports include a Paid Out Tips Detail; and a GL Account for Tips is configurable. But no cash-tip declaration workflow is documented for the current Enterprise POS ('declared' appears only in a legacy Encounter POS release note — 'shift close report contain declared cash values'), so declared-versus-charged reporting is absent, as is any tip tax liability rollup by jurisdiction. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/reporting/payroll-reports.html · retrieved 2026-08-04

multi-location-org-hierarchy

Enterprise Portal provides Site Hierarchies and Tags as first-class objects, with site management, roles and permissions scoped to them. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

multi-location-central-menu-publish

Central Data Management authors ordering settings across the hierarchy, with a documented Sync Changes mechanism to push to sites. Publish/version history detail not confirmed. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

multi-location-local-override-policy differentiator

Shortfall: no explicit statement that corporate-controlled fields become non-editable at store level. Corporate Items (Foodservice Management POS, the campus/school/healthcare product line) documents 'local override values for individual menu items', and the Advanced item editor carries a distinct 'Corporate' tab ('Override values for the parent corporate item') alongside a separate 'Overrides' tab ('Local override values for the item'). This is a corporate-vs-local override structure matching the claim's shape, but no page states which specific fields (price, availability, name, image, recipe) are lockable versus editable, or confirms locked fields are enforced as non-editable at the store terminal. Documented in the Foodservice Management POS product line rather than the Genius Enterprise POS branded product this dossier centers on. Retrieved from the product-documentation full-text search index. https://www.xenial.com/product-documentation/en/genius-point-of-sale/foodservice-management-pos/corporate-items.html · retrieved 2026-08-04

multi-location-price-zones

Menu maintenance supports managing product prices across the hierarchy; per-location-group, per-channel and per-daypart price tiers on one item record are not documented. https://www.xenial.com/product-documentation/en/classic-products/classic-portal/menu-maintenance--mm-/manage-product-prices/change-price-s-.html · retrieved 2026-08-01

multi-location-scheduled-publish differentiator

Shortfall: no per-location timezone semantics and no post-activation rollback. Data Management Packages bundle menu, product, price, discount and tax changes and deploy them together: "Sites are updated immediately upon deployment of the package -OR- on a scheduled date", and creating a package offers "Toggle Schedule Changes to On. In the Effective Date field, type the deployment date", with the Package List showing a Scheduled column holding "the date and time when the package is scheduled for deployment" and statuses Ready / Ready to Deploy / Scheduled / In Progress. Pricing Updates and each Data Management editor feed a package via Add Changes to Package, and Set Site-Specific Pricing scopes values per site. But the docs never say the effective date is interpreted in each target site's local timezone, and the only reversal documented is Stop Package / Force Stop Package, which halts a deployment that has not finished - after a package deploys there is no documented rollback (only Restore Deleted Records, and manual re-editing). https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/packages.html · retrieved 2026-08-08

multi-location-new-store-template differentiator

Portal documents Site Creation, site configuration and service enablement — a provisioning workflow. Configuration cloning from a template and published time-to-open are not documented. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

multi-location-corp-vs-franchisee-roles differentiator

Roles, user groups and hierarchy-scoped permissions exist, and Xenial serves franchisees directly. A formal franchisor-vs-franchisee tenancy boundary is not documented. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

multi-location-royalty-calculation differentiator

Re-checked 2026-08-08 against both Paligo portals dumped in full, including the developer-resources portal the earlier pass never reached. Grepping royalty / franchise / ad fund / advertising fee across 7,250 sections returns three things, none of them a calculation engine: Back Office Utilities > Store Fields Setup, whose customisable numeric store fields are illustrated "e.g.: Rent and Royalty" - a manually keyed value, not a computed one; the Drive Thru Rack-n-Stack Leaderboard, which compares speed of service "with others in the same district and/or franchise"; and Classic Portal user administration referring to a franchise's primary contact. No royalty, ad-fund or fee module appears in Back Office (Cash, Food, Labor, Projections, Report Manager, KPIs, Tasklists, Team Portal, Export Data, Utilities) or in the Portal navigation, and no royalty resource appears in the Portal, Data Management, Back Office or Staff API operation definitions. Still unknown, not no: the Store Fields Setup finding hints the royalty basis is entered rather than derived, but that is inference and the nav lists are overviews, not completeness assertions.

multi-location-royalty-collection

Re-checked 2026-08-08 over both portals. No ACH, direct-debit, sweep or franchisee-billing surface exists anywhere: Back Office Cash covers drawer, deposit and cashier reconciliation only, Money reports cover pay types and settlement, and the Data Stream Deposit object describes bank deposits of store cash ("declare how much currency to send to the bank"), not inter-company collection. No franchisee-facing statement of charges appears in the Team Portal, the Genius Portal or SuiteSpot. This follows the same finding as multi-location-royalty-calculation - there is no royalty amount being calculated to collect - but as there is no enumeration asserting the absence, it stays unknown.

multi-location-consolidated-reporting

Back Office aggregates sales, labor and food across a single site or an entire franchise. Store-vs-store ranking and variance flags not explicitly documented. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

multi-location-normalized-item-rollup differentiator

Shortfall: local RENAME under the corporate id is not documented. Data Management holds one corporate product record per item, identified by a Formal Name plus an ID (PLU) and assigned to Major/Minor reporting categories on the General page. Price is overridden per location without forking the record - Pricing Updates > Set Site-Specific Pricing: "From the View and Edit Price form, type the price for each listed site", and the Product List Price page repeats "Multi-site users: To the right of the field, select the globe icon to define values for each site". Enterprise reporting then aggregates on that shared record: Category Sales per Site offers grouping levels "By Hierarchy" and "By Hierarchy and Site", and Enterprise Sales Summary is a "high-level breakdown of sales data across all company sites". What is NOT documented is a per-site name override - Formal Name and Alternate Name are single corporate values with no globe icon described - so the claim's "even when stores have renamed" half is unevidenced. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/pricing-updates.html · retrieved 2026-08-08

multi-location-cross-location-giftcard

Gift card management is centrally configured on an enterprise platform; brand-wide redemption, outstanding liability reporting and inter-store settlement are not documented. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

multi-location-cross-location-loyalty

Enterprise loyalty is delivered via Punchh or Como, which are brand-wide platforms; native cross-location profile sharing is not documented by Xenial. https://www.xenial.com/product-documentation/en/genius-integration-partners.html · retrieved 2026-08-01

multi-location-multi-brand differentiator

Re-checked 2026-08-08 across both portals, including the developer-resources portal the earlier pass did not have. Searching virtual brand / multi-brand / dual brand / second brand still returns nothing, and the structural check agrees: the Portal object model is Company > Site > Terminal, a Site carries one set of Data Management records, and separation within a site is expressed through Revenue Centers, Order Sources, Destinations, Price Points and Terminal Schemes rather than through a brand entity. Menus can be scoped per order source and receipts are templated per site, so the pieces of a second concept exist, but no page documents two separately branded, separately reported concepts sharing one terminal and drawer. Unresolved rather than absent - none of those configuration pages claims to be the complete set of concepts a site may run.

multi-location-multi-tax-jurisdiction

Localized sales tax per site, tax exemptions in Tender Operations, and a documented Quebec WEB-SRM fiscal reporting integration with per-site and per-terminal configuration. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-portal/web-srm---service/web-srm-site-integration/configure-sites-and-pos-terminals-in-data-management.html · retrieved 2026-08-01

multi-location-multi-currency-locale

Shortfall: multi-LOCALE is evidenced — product documentation is published in English, Spanish and French (the doc site serves /en/, /es/ and /fr/ path variants), the Portal has Language Configuration, and the vendor claims deployment in 62 countries. Multi-CURRENCY is not: no currency configuration, FX handling or consolidated reporting-currency conversion is documented. The 62-countries figure is a marketing claim, hence grade D. https://geniusforenterprise.com/home · retrieved 2026-08-02

multi-location-config-audit-log differentiator

Genius Portal > Settings and Tools > Change History is a corporate-level configuration change log. Its columns are Date ("change timestamp"), User ("user name who made the change"), Source ("application used to make the change"), Change Type ("such as UPDATE or CREATE"), Type ("entity type from the Genius ecosystem"), Name and ID ("entity unique identifier") - so who, what object, what kind of change and when. It is filterable by any column, by date range, and by location via the Site Selector, and each row opens the changed entity as JSON with a Compare view diffing new against historical and a Select Change / View Version picker for prior versions. Because prices, taxes, discounts and permissions are all Data Management / Portal entities, they fall inside it, and Data Management records additionally carry a per-record Audit Trail ("view an audit trail of updates to a Data Management record including site mappings", searchable with a From/To datepicker). The docs do not assert immutability or describe an export, but corporate-queryable is satisfied outright. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-portal/settings-and-tools/change-history.html · retrieved 2026-08-08

multi-location-enterprise-sso differentiator

Shortfall: OIDC only (no SAML) and no SCIM or automated deprovisioning. Portal SSO against a customer IdP is documented end to end in developer-resources: "Portal API accepts sign-on credentials from SSO/Identity Providers through a Federated URL"; "The client may use any IDP/SSO platform that supports the OpenID Connect (OIDC) protocol"; the client registers an app integration, returns client_id, client_secret and the .well-known URL, Xenial creates a client-specific IDP and issues a Federated URL. The worked example is Okta with redirect URI https://mfa.sso.xenial.com/oauth2/v1/authorize/callback, and Portal admins then add the provider under Company Settings > Identity Providers (ID, Name, Type, Domains). But SAML appears nowhere in either portal, SCIM appears nowhere, no user-provisioning or deprovisioning sync is documented (Portal user lifecycle is manual - Add person, Resend Email Invitation, deactivate), and MFA is still enforced after federation ("the user is still required to authenticate (for MFA purposes)"). Setup is also vendor-mediated, not self-service: "A representative from our company works with the SSO admin/team of the client." https://www.xenial.com/developer-resources/en/genius-point-of-sale/enterprise-pos/enterprise-portal/sso-configuration-for-companies/sso-process-overview.html · retrieved 2026-08-08

multi-location-enterprise-api differentiator

Above-store access is issued at company scope, not per location: the published operation index carries "Getting an Integrator Token — POST /integrator/token" and "Getting a Company Integrator Token — POST /v1/company-integrator/access-token", a company-scoped credential distinct from the narrower integrator token. One credential spans the brand rather than requiring per-location provisioning. CORRECTION from 2026-08-02 verification: the request-body object names previously quoted (IntegratorCredentials, PostCompanyIntegratorTokenRequestBody) are NOT retrievable — the developer site renders as an operation index and the individual operation pages could not be fetched. Endpoint paths are evidenced; payload schemas are not. https://www.xenial.com/developer-resources/en/pos-api---getting-started.html · retrieved 2026-08-02 adversarially verified

multi-location-central-labor-policy

Back Office Settings include a per-site labor matrix for ideal labor cost. Jurisdictional break/OT/predictive-scheduling rules enforced at the terminal are not documented. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

hardware-commodity-devices differentiator

Re-evidenced on 2026-08-02 verification because the previously cited install-pos.html returns navigation only and the quoted install sentences were not retrievable. What holds: the install chapter enumerates System Requirements, Android, iOS, Windows and Silent Install as documented install paths, and the POS is publicly listed on Google Play as "Genius Enterprise POS" (com.xenial.shell.app), installable on a standard Android device. No proprietary terminal is required. https://play.google.com/store/apps/details?id=com.xenial.shell.app · retrieved 2026-08-02 adversarially verified

hardware-os-platforms

Verified verbatim: "Hardware and OS agnostic: Windows, iOS, Android." The Enterprise POS install chapter independently carries Android, iOS and Windows sections. Linux is named on no page retrieved and has been removed from this claim. Grading note from 2026-08-02 verification: the OS string itself comes from a vendor feature page (grade C); the grade-B support is the install chapter per-OS structure. https://www.xenial.com/products/pos-software/ · retrieved 2026-08-02 adversarially verified

hardware-handheld-purpose-built

Tablets plus a new AI-first Genius handheld announced May 2026 with voice-driven order entry. No published drop rating or IP ingress rating. https://restauranttechnologynews.com/2026/06/global-payments-strengthens-restaurant-operations-with-connected-pos-payments-and-commerce-technology/ · retrieved 2026-08-02

hardware-handheld-battery-swap differentiator

The current Genius handheld publishes a hot-swap battery design in its spec table. All in One Handheld iRoc Max with Moby 5500 (SF Model 2600-iMin-iRocP), Battery capacity: "Capacity: 3.89V / 8000mAh / 31.1Wh Swappable Smart Battery; Backup Battery: 3.8V / 205mAh / 0.8Wh, for hot swap" - an internal backup cell exists specifically so the main pack can be exchanged without powering down, and a 5-slot charger dock is listed as an accessory. The Aava 10 Tablet spec table likewise lists "Exchangeable battery" with a microSD slot in the battery compartment. Note the older All In One Handheld with Moby5500 (2600-AIOHand-M5500) publishes only a capacity (7.6V / 2500mAh / 19Wh) and no swap language, and no device publishes a rated shift life in hours except the Galaxy Tab Active5 (16-hour video playback). https://www.xenial.com/product-documentation/en/genius-hardware/all-in-one-handheld-iroc-max-with-moby-5500.html · retrieved 2026-08-08

hardware-offline-mode

Confidence label is wrong: the sole source is an App Store product description for Xenial Shell (the smaller Xenial Cloud POS packaging), which the dossier itself elsewhere concedes is NOT the enterprise Genius for Enterprise product. The '30 days' figure appears nowhere in Xenial product documentation — I searched the offline data-flow chapter and found no duration statement. Treat 30 days as a vendor marketing claim about the SMB SKU, not a documented enterprise capability. https://apps.apple.com/us/app/xenial-shell/id1463045984 · retrieved 2026-08-02 adversarially verified

hardware-kds

Genius Kitchen (and legacy Chef) is a first-party KDS with kitchen stations, routing schemes and bump bar support. Packaging caveat: on the smaller Xenial Cloud POS SKU this module is a paid add-on rather than part of the base subscription (per the App Store listing); it is scored here as a documented module of the enterprise Genius platform, where the commercial packaging is not published. https://www.xenial.com/product-documentation/en/genius-kitchen.html · retrieved 2026-08-01

hardware-kiosk differentiator

First-party kiosk hardware and software with integrated payment and loyalty, including new 2026 configurations. Countertop-vs-freestanding range and ADA documentation not published. https://investors.globalpayments.com/news-events/press-releases/detail/486/global-payments-announces-the-launch-of-its-genius-for · retrieved 2026-08-02

hardware-drive-thru

First-party lane hardware documented at installation level. Drive Thru Director "consists of the following hardware: Media Player (Controller) GPIO Board Vehicle Detection System", and the GPIO board "communicates electronic signals from vehicle sensors in the drive thru to the Drive Thru Director software" over a published wiring standard whose channels are 0 Menu board 1, 1 Pickup window, 2 Payment window, 3 Menu board 2, 6 Greet time (menu board 1), 7 Greet time (menu board 2) - the greet-time channels being the headset tie-in, since Greet Time is "the length of time between vehicle detection at the menu board and the activation of the drive thru team headset". The buried detector is specified to installation tolerance: cabling laid "in the shape of a rectangle with 45 degree corners", "60" (152.4 cm) by 18" (45 cm)", placed "approximately 12-18' (30-48 cm) from the edge of the curbing", "Use a continuous piece of un-spliced cabling" "looped around the rectangle a total of six times", with a stated pass/fail test ("If the DC resistance is greater than 3 ohms, or the insulation resistance to ground is less than 100 megohms, the cabling is damaged and the entire installation must be replaced"). Outdoor menu boards and confirmation displays are the Genius Drive Thru "loop detectors, camera systems, and intelligent order confirmation units", and the timer requirement is met by the segment speed-of-service model in Goals and Metrics. RE-CITED 2026-08-08: page renamed to /en/genius-drive-thru/buried-vehicle-detectors.html and now fetches 200 with body text in the raw HTML, so the earlier 404-and-search-index caveat is withdrawn. https://www.xenial.com/product-documentation/en/genius-drive-thru/buried-vehicle-detectors.html · retrieved 2026-08-08

hardware-printer-compatibility

Printers are generic, multi-vendor peripherals configured in Data Management > Ordering Settings > Hardware > Peripherals, with four separate connection paths documented as their own chapters: Printer (LAN), Printer (USB), Printer (Serial) and Printer (Serial Device Bridge), plus Printer (OPOS). The LAN chapter's Peripheral Configuration is Peripheral Name, Printer Type ("Receipt Printer or Kitchen Printer"), Vendor ("From the dropdown, select the vendor for the device"), Model ("select the device model") and Cutting Option (Full Cut / Partial Cut / Tear Bar), and its Connection Configuration is simply "IP - type the IP address of the device" and "Port" - i.e. any network printer, addressed by IP. The developer-resources Device Bridge chapter names the Vendor field's contents concretely: "Vendor - The brand of the device such as Epson or Logic Controls", over OPOS logical device names. Epson is also listed as an Operational integration partner, and the TD22 kiosk ships an optional integrated "Epson TM-M30 - interfaces include: USB, Serial, Ethernet, WiFi". Kitchen printers get their own routing filters, backup printer sets and print templates. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/peripherals/printer--lan-.html · retrieved 2026-08-08

hardware-peripherals

Cash drawer operations documented (assignment, reconciliation, closing, drive-thru drawer assignments). No published peripheral compatibility list for scanners, scales or CFDs. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-pos-app/manager-procedures/drawer-functions.html · retrieved 2026-08-01

hardware-p2pe-terminal

Shortfall: PTS listing yes, validated P2PE and SAQ type no. Card entry runs on PCI-approved PIN-entry devices whose spec sheets state the approval: Moby 5500 (SF 2600-MP-P / 2600-MP-T) - "Encryption AES, TDES-DUKPT, RSA or On-Guard DATA key (SRED) TR39 / PCI PIN 2.0 DATA and PIN certified key management; Remote key update service (Ingenico-hosted service)" and "Certifications and security ... EMV L1 and L2 Contact, EMV L1 Contactless ... PCI PTS 6.x"; Verifone P400 - "Security PCI PTS 5.x Approved", Verifone Secure OS. SRED plus remote key injection is the encrypting-reader model this claim describes, and the POS itself talks to the reader as a Payment Device peripheral (LAN, Bluetooth or OPOS) rather than handling the PAN. What Xenial does NOT publish is a PCI-listed validated P2PE solution reference, and no page anywhere in either portal states the merchant's SAQ type - SAQ, P2PE and point-to-point encryption occur zero times in the 7,250-section dump. https://www.xenial.com/product-documentation/en/genius-hardware/moby-5500m.html · retrieved 2026-08-08

hardware-tap-to-phone differentiator

Checked 2026-08-08 across both portals: tap to pay and tap to phone occur zero times, and no Apple or Google softPOS programme is named. The positive evidence points the other way without settling it. Every documented payment path is a discrete reader - the Peripherals catalogue enumerates Payment Device (Bluetooth / LAN / OPOS), Payment Genius, Payment Genius (USB), Payment Verifone (Bluetooth / LAN), Payment Moneris (LAN), Payment TranSend (LAN / OPOS), Payment BAMS FirstData (LAN / OPOS), FreedomPay Payment Device and Custom Payment Device - and the iRoc Max handheld's spec line reads "Payment: Requires Moby 5500, Portico". Cutting against a clean absence, the Aava 10 Tablet spec sheet lists "Payment NFC: Front facing NFC antenna behind Display; Optimized for payment processing; Supporting EMV and other payment cards", i.e. a Xenial-supplied tablet that reads cards with no separate reader - but that is vendor hardware, not the commodity phone this claim asks about, and no page says the Genius app can take contactless on an unmanaged personal device. Unresolved.

hardware-pricing-transparency differentiator

No per-SKU hardware prices published anywhere; hardware page directs to sales.

hardware-ownership-vs-lease differentiator

Shortfall: the vendor hardware page states "Flexible purchase options: buy outright or pay a low monthly as-a-service fee", so purchase is offered rather than a lease being forced — but there is no price, no SKU list, no lease term and no ownership or title language anywhere. A vendor feature page is grade C, below the floor for a yes on a differentiator. https://www.xenial.com/products/pos-hardware/ · retrieved 2026-08-02

hardware-usable-after-churn differentiator

Checked 2026-08-08 across both Paligo portals. bricked, software-locked, decommission and after-cancellation return nothing, and nothing in Genius Hardware, Hardware Installation or the Contact Support page addresses post-cancellation use. The nearest artefacts cut both ways and settle nothing: Genius Hardware publishes ordinary commodity spec sheets (Samsung Galaxy Tab Active5, Aava 10 Android tablet, LG UL3J displays, Verifone P400, Epson TM-M30 in the TD22 kiosk), which suggests general-purpose devices; but the Portal binds each unit as a Terminal with a downloaded configuration, LG displays are enrolled in LG ConnectedCare device management, and Genius POS on Android/iOS requires a Portal login at first launch. Whether a purchased unit is released, wiped or left enrolled at contract end is a commercial-terms question Xenial does not publish on www.xenial.com. Unresolved.

hardware-rma-sla differentiator

Shortfall: warranty terms are published per device, an exchange SLA is not. The Genius Hardware spec sheets carry warranty lines - Aava 10 Tablet: "Warranty 1-year standard warranty; Optional: 3-year warranty contract"; Galaxy Tab Active5: "Service and Support 3-year limited warranty". So a warranty term is stated for the devices that publish one (the Moby 5500, GC26, XC23, TD22 and Verifone P400 sheets carry none, giving only a Moby lifetime rating of "100k transactions on magstripe reader and smart card reader"). No replacement or advance-exchange turnaround exists anywhere: the Contact Support page publishes only channels and numbers (SMS 1-844-957-4434, phone 1-800-547-4266, WebChat, Web-to-Case, sos@globalpay.com) with no response or swap target, and the words RMA, depot and advance exchange occur zero times in either portal. https://www.xenial.com/product-documentation/en/genius-hardware/aava-10-tablet.html · retrieved 2026-08-08

hardware-byod

Checked 2026-08-08 across both portals: BYOD, personal device and own phone occur zero times. What is documented is neutral on the question. Install POS publishes an ordinary consumer install path - "From a Web browser, go to Google Play ... search for Genius ... select Install", the same for the iTunes App Store, then "type the login credentials that were registered with the Portal" - with minimum requirements of Android 11+, iOS 15.8.6+ or Windows 10+, 8GB RAM and 32GB disk. So the app is publicly downloadable and gated by Portal credentials rather than by device enrolment, which is consistent with BYOD but is not a documented BYOD posture. Against it, the terminal model registers each unit in Data Management > Ordering Settings > Hardware > Terminals with a downloaded per-terminal configuration and peripheral assignment, and Xenial sells its own managed handhelds. No permission or security model for staff-owned devices is published. Unresolved.

hardware-remote-device-management differentiator

POS Terminal Management in Manager Procedures, kitchen Remote Performance Monitoring, and a remote support portal. A unified online/offline device console with staged rollout is not documented. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

extensibility-public-api-docs

Re-verified independently on 2026-08-02, overturning the 2026-08-01 verification pass which had upheld a value of "no". The developer-resources root and the POS API getting-started page both return HTTP 200 and publish a first-party operation index: token endpoints, the Connect API order endpoint, and Data Management operation definitions across roughly thirty resources (Product, Product Price, Bundle Component Price, Variant, Discount Definition, Fee Definition, Tax Definition, Floor Plan, House Account, Recipe Venue, Store Hours Config, Reporting Category and more). Caveat retained rather than ignored: the section carries a "Privileged and Confidential" heading, Portal Requirements are a stated prerequisite, and no sandbox, rate limits or self-serve credential signup appear anywhere — so this is published-but-partner-gated documentation, not an open self-serve API. Individual operation pages did not render to direct fetch. https://www.xenial.com/developer-resources/en/pos-api---getting-started.html · retrieved 2026-08-02 adversarially verified

extensibility-api-access-cost differentiator

Re-checked 2026-08-08 with the developer-resources portal fully dumped (293 pages / 3,333 sections) rather than browsed by navigation. Getting Started with APIs > API Prerequisites states the gate as legal and relational, not priced: "Return a completed NDA and Developer Licensing Agreement; Receive confirmation from an account manager to begin integration and development; Receive an integrator token for a test developer account: Generated by our developers." Portal Company Settings expresses each data service (Data Stream, Altametrics, Yellow Dog, Loyalty, the delivery services) as a per-company service that must be enabled, and Portal API is described as administering "companies and their allowed products and subscriptions" - but no page attaches a fee, a per-location charge or a plan tier to API or raw-data access. Xenial publishes no pricing of any kind, and Genius API documentation is itself a per-user Portal permission ("API Documentation Access"), so the commercial terms sit inside the customer contract. Unresolved.

extensibility-partner-revshare

Re-checked 2026-08-08 across both portals in full. revenue share, referral fee and partner fee occur zero times. genius-integration-partners.html enumerates the partner roster by category (Back Office and Reporting, Delivery and Online Ordering, Digital Menu Boards, Gift and Loyalty, Kiosk, Operational, Payments, Voice AI) and each partner has a configuration page, but those pages describe Portal service setup - credentials, URLs, tokens, enablement toggles - and never commercial terms. The developer-resources side documents the onboarding path (NDA and Developer Licensing Agreement, account-manager confirmation, integrator token) with no pricing attached, and the agreements themselves are not public. No partner or marketplace commercial terms are published; unresolved rather than absent, since a private partner agreement is the norm for an enterprise vendor and non-publication is not evidence that no fee exists.

extensibility-free-sandbox differentiator

Shortfall: a test account exists but it is neither free nor self-service, and no seeded data is described. Non-production environments are documented and addressable - Menu Engine publishes "Testing (UAT) https://uat-xme.xenial.com/" alongside production; Back Office states "The Back Office API environment consists of two stacks: QA/UAT and Production" with QA URLs (qa-xconnect.xenial.com/auth, /swagger); Menu Update Monitor lists QA, UAT and PROD endpoints; Omni Order Injection publishes a staging URL; the Data Stream setup chapter lists separate UAT and PROD publishing IP ranges; and Digital Menu Board publishes a UAT environment on xenialstg.net. Access, however, is gated: API Prerequisites reads "Before starting the integration development process, developers must: Return a completed NDA and Developer Licensing Agreement; Receive confirmation from an account manager to begin integration and development; Receive an integrator token for a test developer account: Generated by our developers." There is no signup, the token is issued by Xenial staff after an executed agreement, and no page describes seeded or demo data. https://www.xenial.com/developer-resources/en/getting-started-with-apis.html · retrieved 2026-08-08

extensibility-oauth-partner-apps

Shortfall: token issuance is documented — "POST /integrator/token" taking an IntegratorCredentials object, and a company-scoped "POST /v1/company-integrator/access-token" — and Xenial and Global Payments use OKTA for authentication. But this is an integrator credential exchange, not a per-merchant OAuth authorisation-code grant with scoped consent, and Portal Requirements gate credential issuance, so a third-party developer cannot self-provision. https://www.xenial.com/developer-resources/en/pos-api---getting-started.html · retrieved 2026-08-02

extensibility-webhooks-push

The Data Stream API is push, and the docs frame it explicitly against polling: "Data Stream API publishes JSON formatted objects to a configurable webhook URL ... Rather than the user calling the API to request data, the API reaches out to the user to notify them that something happened. This is a much more efficient model in contrast to Polling a RESTful API on a set interval." Six object types are documented with full payloads - Orders, Drawers, Deposits, Time Punches, End of Day Notifications and Workflows. Order coverage spans the lifecycle: the Order Status table lists Pending ("the initial order state"), Open, Saved, Suspended, Checked In, Committed, Closed ("the payment has been applied to the order with an amount that satisfies the order total"), Voided, Post Payment Voided, Overringed, Deleted, Purged and Split, marking which are final, and states "If necessary, users can add states to the list of allowed states" - with an Order States filter in the endpoint configuration to choose exactly which are delivered. The payload carries payments, discounts, refund-bearing totals and a contributors array of per-action employee and terminal edits. https://www.xenial.com/developer-resources/en/genius-point-of-sale/enterprise-pos/data-stream/data-stream.html · retrieved 2026-08-08

extensibility-webhook-reliability differentiator

Shortfall: no cryptographic signing and no documented retry with backoff. Replay is the half that is met - Genius Portal > Settings and Tools > Data Stream Endpoints documents Resend Data, choosing Entity (Orders, Drawers, Deposits), Site, Business Date and an entity-specific filter (specific order numbers, drawer event types, deposit statuses), and the Staff API publishes a parallel operation that "resends all shifts for a specific company, site, and business date ... and can be used when the shift data has failed to be sent to the integrator's target endpoint". Signing is explicitly not offered: the only authentication is an optional static string the customer supplies, sent as an AUTHORIZATION header, and the docs state "DSS supports an optional authorization layer, whereby the user may opt to configure a token string ... the service does not support an Authentication step, nor is there a process to refresh the token periodically", adding "If your API does not require specific authorization, then the AUTHORIZATION header is still present but with a value of null". Integrity is addressed instead by source-IP whitelisting (published UAT and PROD address lists) and by an ordering guard, the configurable Relevance Key (default "_id,time.last_modified") that suppresses out-of-order copies. No retry count, interval, backoff or dead-letter behaviour appears anywhere in the Data Stream chapter. https://www.xenial.com/developer-resources/en/genius-point-of-sale/enterprise-pos/data-stream/data-stream/setup.html · retrieved 2026-08-08

extensibility-order-injection-api

The Connect API is published as a documented inbound order-write contract: "Connect API | Getting Started", "Sending Orders" and "Order Conflict Resolution", against the endpoint "POST /api/ds/pipeline/pos.order". Explicit conflict-resolution semantics on an inbound order endpoint is more than most quote-only enterprise vendors publish. CORRECTION from 2026-08-02 verification: the POSOrderMessage/POSOrder field list previously quoted (contributors, creator, customer, deleted_items, destination, owner, payment_info) is not retrievable — only the operation titles render. Treat the data-model detail as unverified. https://www.xenial.com/developer-resources/en/pos-api---getting-started.html · retrieved 2026-08-02 adversarially verified

extensibility-menu-write-api differentiator

Shortfall: the POS Data Management section publishes operation definitions across the full menu object graph — Product, Product Category, Product Price, Bundle Component, Bundle Component Price, Variant, Variant Type, Discount Definition, Fee Definition, Tax Definition, Tax Group, Recipe Venue, Store Hours Config, Store Hours Config Group, Time Period, Tag, Measure, Named Calculations, Order Destination, Order Source, Floor Plan, General Ledger Account, House Account, Inventory Item Venue, Cart, Reporting Category — but the HTTP verbs exposed per resource were not retrievable, so documented WRITE access to menu records is not confirmed. Read access is clearly documented; write is inferred, so this is not scored yes. https://www.xenial.com/developer-resources/en/pos-api---getting-started.html · retrieved 2026-08-02

extensibility-data-symmetry differentiator

Shortfall: both an inbound order pipeline (Connect API) and a broad Data Management resource surface are published, so the API is not read-only — but no statement exists that everything configurable in the Enterprise Portal is reachable through the API, and per-resource verbs were not retrievable. https://www.xenial.com/developer-resources/en/pos-api---getting-started.html · retrieved 2026-08-02

extensibility-published-rate-limits

Re-checked 2026-08-08 over the full two-portal dump. rate limit, quota, throttle, burst, 429 and requests-per-second/minute return nothing that is a policy - the single near-hit is rhetorical, in the Data Stream overview arguing that polling "often results in a rate-limited API resource that serves up far more data than what is actually required". Getting Started with APIs > Operation Definitions Overview defines the documentation shape as Endpoint, Data Model and Sample Code, and the Headers section enumerates exactly four required headers (CONTENT-TYPE, AUTHORIZATION, X-COMPANY-ID, X-SITE-IDs) with no rate-limit or retry-after header among them; individual operation definitions list response codes (200, 401 and per-endpoint errors) without 429. Token validity is published (21 days, with a rotation mechanism required) but that is a credential lifetime, not a quota. No numeric limit or throttling behaviour is published; whether limits exist and are communicated privately is undetermined.

extensibility-doordash-preferred differentiator

Positive evidence of absence: DoorDash's 2026 Preferred Integrations cohort (performance snapshot as of 2026-05-08) is Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast and UrbanPiper. Xenial is not among them. Regraded B to E — this is third-party reporting, not vendor documentation. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-02 adversarially verified

extensibility-first-party-delivery-integrations differentiator

DoorDash, Grubhub and Uber Eats are first-party Genius services configured directly in the Portal, not through middleware. Company Settings > Services documents them as one native service group: "Food Delivery Services (DoorDash, GrubHub, Uber Eats) - Toggle on the delivery services used at the company and define the following settings: Delivery Service URL ... Callback URL - (Optional) The Menu Engine link for Web site validation. Order Source - From the dropdown, select the order source to associate with the delivery provider." DoorDash goes further: "DoorDash Self-Service Integration - Genius manages integration (tokens, subscriptions, test stores) and monitors integration health in real-time via the new self-service DoorDash Developer Portal. From the DoorDash Onboarding section of the service form, directly activate sites for the DoorDash delivery platform." Supporting evidence across the corpus: Order Source carries per-provider marketplace-facilitator tax handling; the Order Source Images chapter publishes each provider's own image spec (DoorDash 16:9 1400x800, Grubhub 4:3 1600x1200, Uber Eats 320-6000px); and the Omni Order Discounts API specification carries per-partner request formats and dedicated discount PLUs (29330110 DOORDASH OMNI, 29330115 UBER OMNI, 29330120 GRUBHUB OMNI). Middleware (Checkmate, Deliverect, Olo) is separately available but is not the documented path. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-portal/settings-and-tools/company-settings.html · retrieved 2026-08-08

extensibility-middleware-compatibility

Deliverect publishes a Xenial Cloud integration connecting Uber Eats, SkipTheDishes and more. Only one major middleware platform confirmed; a second was not. https://www.deliverect.com/en-us/integrations/xenial-cloud · retrieved 2026-08-02

extensibility-accounting-connectors

Shortfall: exactly one named accounting connector exists. Restaurant365's own documentation states "R365 connects directly to Xenial Cloud POS's cloud service through an API", importing sales (receipts, menu items, payments, discounts, voids) and labour (employee records, jobs, declared tips). But it is documented by the partner rather than by Xenial, it targets Xenial Cloud POS rather than Genius for Enterprise, and setup requires a Client ID, Client Secret, Company ID and Location ID "obtained from Xenial Cloud Support". One support-brokered connector is not a connector ecosystem, so partial rather than yes. https://docs.restaurant365.com/docs/xenial-cloud-pos-integration · retrieved 2026-08-02 adversarially verified

extensibility-payroll-export

Payroll connections referenced and Back Office exports data; two named payroll providers are not documented. https://apps.apple.com/us/app/xenial-shell/id1463045984 · retrieved 2026-08-02

extensibility-bi-data-warehouse differentiator

Data Stream Endpoints plus the Export Data module imply scheduled outbound feeds; customer-controlled destinations are not documented. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

extensibility-app-marketplace

Positive evidence of absence: the Genius Integration Partners page names only Como and Punchh, both under "Gift and Loyalty", enabled via Company/Site Settings | Enable Service. There is no browsable marketplace, no self-install and no partner directory. Important qualification: the Restaurant365 connector proves partners exist outside that page, so the correct reading is that the ecosystem is undisclosed and support-brokered, not provably tiny. https://www.xenial.com/product-documentation/en/genius-integration-partners.html · retrieved 2026-08-02

extensibility-custom-fields-scripting

Enterprise Portal Settings and Tools document Custom Fields and Custom Services as operator-configurable objects. Vendor-hosted custom scripting is not documented. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-08-01

extensibility-headless-embedded

Shortfall: the POS engine is documented as driving external surfaces over a published contract — a Customer Facing Display (CFD/OCU) XML interface with POS Output objects (Order, ItemBuild, MainOrder, ProductDetail, ValueMeal, Qualifier, Discount, Total, OrderDiscount) and sample order states — and orders can be injected via the Connect API. But no headless or embedded POS deployment mode is documented, and there is no UI-less runtime or embeddable SDK. https://www.xenial.com/developer-resources/en/pos-api---getting-started.html · retrieved 2026-08-02

extensibility-api-versioning-deprecation

Shortfall: path versioning is visible in the published auth endpoint ("POST /v1/company-integrator/access-token") and Xenial publishes a public per-product release-notes site including previous releases. No deprecation policy, breaking-change notice period or sunset schedule is published anywhere in developer-resources. https://www.xenial.com/developer-resources/en/pos-api---getting-started.html · retrieved 2026-08-02

extensibility-data-portability-exit differentiator

Shortfall: no post-termination-specific statement, and guest/customer records are not among the listed exportable modules. The Back Office Export utility documents exportable modules: Cash Sheet, Employees, Inventory, Menu Analysis, Menu Items, Payroll, Product Mix, Purchases, Security Users, Time Punches, and 'Transaction Level Detail (TDL)' -- a broad in-life export covering orders, menu and payroll, but no page states this remains available on demand after contract termination, specifies a machine-readable format guarantee, or confirms customer/guest records and payments metadata are included. Retrieved from the product-documentation full-text search index; consistent with the record's existing commercial-data-export-self-serve finding on the same module. https://www.xenial.com/product-documentation/en/genius-back-office/export-data.html · retrieved 2026-08-04

reliability-offline-order-entry

Shortfall: same single App Store marketing sentence as order-capture-offline-order-entry, describing the Xenial Shell / Cloud POS SKU rather than Genius for Enterprise. The prior note claimed "per vendor docs" — that is not supported; the enterprise offline data-flow chapter yields only navigation headings. https://apps.apple.com/us/app/xenial-shell/id1463045984 · retrieved 2026-08-02

reliability-offline-card-auth differentiator

Store-and-forward is a first-class, configurable part of the Genius payment peripheral surface, not an inferred capability. The FreedomPay Payment Device settings page defines 'POS Floor Limit - Type the maximum currency amount the merchant agrees to accept in offline mode... Setting the amount to 0 disables Store and Forward (SAF)', 'Max Days Allowed Offline - Type the maximum number of consecutive days the merchant agrees to process transactions in offline mode - default set to 5. This setting implies that at least one (1) online transaction was successfully completed before Store and Forward (SAF) executes', 'Enable SAF - Toggle Yes if the device supports and the merchant allows Store and Forward (SAF) offline transaction processing', 'SAF Port' and a SAF Retry Count. Company Preferences > Payments adds platform-level caps: 'Max SAF Amount' and 'Max SAF Transactions - Type the maximum number of pending Store and Forward (SAF) offline transactions to allow at a time' (ordering-settings/preferences/company-preferences.html). The POS Online/Offline Data Flow chapter states for Loss of Internet that 'Payments (other than gift cards) are processed in accordance with configured offline rules' - gift card processing is the named exception, card payment is not. The developer portal corroborates at the API level: the Custom Payment Adapter exposes safReport(), and the POS API Transaction object carries safObject: SAFUploadObject | SAFReportObject. Xenial's own FreedomPay certification summary lists 'Store-and-Forward (SAF) Supports offline authorizations and maintains SAF status, including: Update of that status as offline Transactions are forwarded, and either approved or declined'. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/peripherals/freedompay-payment-device.html · retrieved 2026-08-08

reliability-offline-decline-liability differentiator

Shortfall: no statement of who bears the loss when a stored transaction ultimately declines. Same underlying evidence as payments-offline-decline-liability (which this cell duplicates from the reliability angle): the FreedomPay payment-device configuration documents a 'POS Floor Limit' ('the maximum currency amount the merchant agrees to accept in offline mode'), 'Max Days Allowed Offline' (default 5), Retry Count (default 100), 'Days to Keep Failed Transactions' (default 30) and a 'Decline Replay Timer' (default 1440 minutes), plus company-level Max SAF Amount/Transactions caps and a Payment Status/SAF column on the Order Payments sales report. This documents the offline-acceptance cap and retry mechanics in detail but 'merchant agrees to accept' is floor-limit acceptance language, not a stated loss-allocation rule for the case where a stored transaction is later declined. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/peripherals/freedompay-payment-device.html · retrieved 2026-08-04

reliability-lan-degraded-multi-terminal differentiator

Regraded D to B and re-cited on 2026-08-02 verification. LAN loss is named explicitly in the documentation, not just as a heading: "in the event internet or LAN connectivity is lost... users can continue to place orders and perform all mission-critical operations to service guests." Shortfall narrowed: nothing states that multiple terminals continue to SHARE order data with each other across a LAN partition, as opposed to each terminal independently continuing to ring. The prior App Store citation described internet loss and has been dropped. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-pos-app/pos-online-offline-data-flow.html · retrieved 2026-08-02 adversarially verified

reliability-local-transaction-engine differentiator

Upgraded from partial on 2026-08-02 verification. The POS Online/Offline Data Flow chapter states: "The vast majority of system functions are unaffected in the event internet or LAN connectivity is lost, and users can continue to place orders and perform all mission-critical operations to service guests." First-party product documentation that the terminal keeps transacting without the cloud, which clears the differentiator grade floor and supersedes the grade-C vendor feature page previously cited. Body text is client-rendered and was read from the chapter public search index; the chapter URL itself returns HTTP 200. This does NOT extend to card authorisation — see reliability-offline-card-auth. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-pos-app/pos-online-offline-data-flow.html · retrieved 2026-08-02 adversarially verified

reliability-offline-kds-printing

Identical sourcing defect: one App Store marketing sentence, kitchen management is a paid add-on per that same listing, and nothing addresses offline PRINTING at all. Print fallback while offline is unaddressed in every public source I reached. https://apps.apple.com/us/app/xenial-shell/id1463045984 · retrieved 2026-08-02 adversarially verified

reliability-printer-fallback

Chef Recovery is a documented kitchen-management recovery topic; automatic backup-printer/KDS failover with staff alerting is not spelled out. https://www.xenial.com/product-documentation/en/classic-products/chef-kitchen-management/chef-recovery.html · retrieved 2026-08-01

reliability-sync-conflict-handling

Xenial publishes the algorithm. DataSync Process Flow lists as step 6 'Performs conflict resolution to determine whether received data should overwrite the local data version'. DataSync Data Comparison gives the rule: every terminal broadcasts, per feed, 'the name of the feed, the amount of the feed resources and the time of the last update'; on receiving a peer's UDP message 'a check is started to compare the data of the two terminals: local and remote. If the data is not equal, then the remote terminal has more recent data and the process of finding the difference is started... the local terminal requests the entire list of resources at the remote terminal and checks for a mismatch of each resource by the time of the last change or the lack of a resource', then fetches and saves the remote entity. DataSync Database names the audit fields the comparison runs on ('updated_at - The time of the last update of the entity') and states 'DataSync works with audit fields only'. That is last-write-wins by per-resource timestamp, applied when terminals rejoin after a LAN partition. The cloud ingestion layer documents the same discipline separately: Connect API's Order Conflict Resolution says 'The default conflict resolution flow compares the combination of the order elements: _id and time.last_modified. If the time.last_modified field is more recent for the same identifier (_id), an update is made in the database. Otherwise, the order payload is considered to be out of date and is not updated.' Time punches are the one place a different authority is named: 'The Staff module receives offline time punches and determines if any conflicting clock in/out records should overwrite existing data.' https://www.xenial.com/developer-resources/en/genius-point-of-sale/enterprise-pos/datasync/datasync-data-comparison.html · retrieved 2026-08-08

reliability-offline-feature-matrix

Shortfall: the chapter describes the online data flow and states that it identifies the system components impacted when connectivity is lost, separating "Loss of Internet" from "Loss of LAN" — more structure than most of this market publishes. But only the chapter preamble is publicly readable; the per-component impact list itself is not, so no component-by-component degradation matrix can be cited. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-pos-app/pos-online-offline-data-flow.html · retrieved 2026-08-02 adversarially verified

reliability-public-status-page

There is no Xenial status page. status.xenial.com resolves (CNAME lxysgbxdz2kw.stspg-customer.com, Atlassian Statuspage) but the custom-domain certificate is not provisioned - https fails with SEC_E_WRONG_PRINCIPAL - and the host answers http with a 302 to https://www.statuspage.io/, i.e. a dangling Statuspage tenant that serves the vendor's own marketing site rather than any Xenial component list. The previous pass recorded the certificate mismatch and stopped there; following it through resolves it. The Support page itself publishes only support@xenial.com, a support-communities link, a WIKI link, a request form and a remote-access link - no status URL, no uptime page. Neither Paligo portal (786 + 293 pages) contains a status-page reference. trust.xenial.com does not resolve at all (NXDOMAIN) and /trust/, /security/ and /legal/ return 404. https://www.xenial.com/support/ · retrieved 2026-08-08

reliability-contractual-uptime-sla differentiator

Xenial publishes its standard agreement - the Consolidated System Terms and Conditions (3/2025), linked from the xenial.com footer - and it contains no uptime percentage and no service-credit remedy. The availability covenant is Section 2.1: 'We will use commercially reasonable efforts to make available any Software Service that we provide to you on a subscription basis (Subscription Software) for remote electronic authorized Use', carved out for '(i) scheduled downtime (of which we shall give advance electronic notice); (ii) service downtime or degradation due to a Force Majeure Event; (iii) any other circumstances beyond our reasonable control, including your use of Third Party Materials; (iv) Use of the Software Service other than in accordance with these System Terms; or (v) any suspension or termination'. The words uptime, availability percentage and service credit appear nowhere in the document; the only credit mentioned is a billing-error adjustment under Section 5.1 ('you must contact us no later than sixty (60) days after the closing date on the first billing statement in which the error... appeared in order to receive an adjustment or credit'). Support Services (Section 6) commits to a 24x7x365 hotline for technical issues and 8am-5pm local for general questions, which is a response channel, not an availability SLA. https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/index.pdf · retrieved 2026-08-08

reliability-incident-postmortems

Re-checked 2026-08-08 against a wider surface than the 2026-08-04 pass. The venue question is now settled: status.xenial.com is a dangling Atlassian Statuspage CNAME whose http endpoint 302s to https://www.statuspage.io/ and whose https endpoint fails certificate validation, so no incident history is published there; trust.xenial.com is NXDOMAIN and www.xenial.com/trust/, /security/ and /legal/ are 404. Searched the full text of both Paligo portals (product-documentation 786 pages / 3,917 sections and developer-resources 293 pages / 3,333 sections, dumped locally) for postmortem, post-incident, root cause, outage and incident report: the genius-back-office release-notes subtree carries feature and defect notes only, never an outage RCA. The published Consolidated System Terms contain no incident-reporting or RCA commitment (the only notification duty is the EU/UK data-processor clause 3.10.1(vi), 'notify Customer as soon as practicable on becoming aware of... any data security incident'). Left unknown rather than no because the one plausible venue that could carry customer RCAs - the gated Xenial Support Communities at www.xenial.com/support/communities/ - requires a login, so absence on public surfaces does not establish that no written post-incident reports are issued to customers.

reliability-247-live-support

Multiple support phone lines, SMS lines and email queues published, plus a Jira-based Solution Manager portal and community forum. 24/7/365 coverage is not stated and no response SLA is published. https://www.xenial.com/support/ · retrieved 2026-08-01

reliability-onsite-install differentiator

Xenial describes itself as developing, installing and supporting hardware and software for its segments, and operates a remote support portal. On-site go-live terms are not published. https://www.linkedin.com/company/xenialcloud · retrieved 2026-08-01 · not refetchable · site policy · graded D when read

reliability-menu-build-service differentiator

Xenial does contract to do menu data work for the operator, but as an ongoing paid maintenance service rather than as an onboarding menu build. Schedule 7.2 of the published System Terms defines Menu Maintenance Services: 'Subject to Customer's payment of all applicable Fees... Global is responsible for and agrees to (during the Support Term unless a different time period is specified): (i) remotely update, align, and configure Customer's Systems at the Authorized Restaurant Location(s) to reflect menu changes, including the addition of new products, deletion of discontinued products, and changes in options and pricing; and (ii) make available a Menu Maintenance portal to enable Customer to update its pricing for individual menu items and to make selections from offered options'. The operator must designate 'no more than two Customer contact personnel' authorised to request and approve changes, must 'review all menu changes, and correct errors resulting from erroneous selections and data entry by Customer personnel', and 'assumes all risk and responsibility as to menu changes made directly by Customer personnel'. Shortfall: the service is scoped to the Support Term and to changes, is conditioned on payment of applicable Fees, and is separate from the Implementation Services definition (Section 1.2: 'installation, implementation, training, and other services related to the initiation of the System'), which nowhere mentions menu construction. No Xenial document states that the initial menu build is performed by Xenial as part of onboarding. https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/index.pdf · retrieved 2026-08-08

reliability-hardware-replacement-sla

A replacement programme exists and is contractual, but no turnaround time is stated. Section 6 of the published System Terms commits Global to '(v) Replace or substantially correct (in our sole discretion) materially nonconforming Equipment and Installed Software that is under valid warranty during the applicable Warranty Period, at no charge to you (other than shipping, handling, and taxes)' and '(vi)... replace or substantially correct malfunctioning Equipment and Installed Software after the applicable Warranty Period, at the rates and prices set forth in our then-current Support Services Price List' - so it is both included (in warranty) and purchasable (out of warranty). The structure is an advance exchange: Section 5.4 charges 'the list price of any replacement items if any Equipment is not returned to us... within forty-five (45) calendar days after shipment of the replacement items to you', i.e. the replacement ships before the defective unit comes back. Shortfall: no turnaround commitment of any kind - no next-business-day, no shipping window, no on-site option - is stated; 'Replacement items may be new, used, refurbished, or reconditioned in our sole discretion'; and the Support Services Price List that sets the out-of-warranty rates and exclusions is 'provided to you separately' and is not published. The 24x7x365 hotline in Section 6(iii) is the only stated time commitment and it covers phone support, not hardware dispatch. https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/index.pdf · retrieved 2026-08-08

reliability-backup-restore

Operators can self-serve a retrieval of their own data, but not a backup/restore, and no recovery objectives are published. Genius Back Office ships an Export utility: 'Use the Export utility to extract data from an Back Office module and export the data into a file in accordance with specified settings. The Back Office modules from which data can be exported include: Cash Sheet, Employees, Inventory, Menu Analysis, Menu Items, Payroll, Product Mix, Purchases, Security Users, Time Punches, Transaction Level Detail (TDL)', each to a named file the operator specifies (for example Cash.csv) across selected stores and a date range. On the recovery side, DataSync 'allows each terminal to operate as an independent unit. In the event of data loss, DataSync uses the local network to restore the terminal(s)', and a 'Cloud Restore' is listed among the remotely initiated commands a site consumes from the cloud. Shortfall: none of that is an operator-triggered point-in-time backup or restore of the account's data, the Cloud Restore command is documented only as a name in a list with no procedure, and no RPO or RTO figure appears anywhere in the 7,250 documented sections or in the published System Terms - which instead make it the operator's job, requiring the Customer to 'protect its own data and programs, including performing nightly and weekly backups' (Schedule 7.2). https://www.xenial.com/product-documentation/en/genius-back-office/export-data.html · retrieved 2026-08-08

reliability-pci-dss-4-attestation

Re-checked 2026-08-08. No Attestation of Compliance, no validated P2PE listing and no trust center were located on any Xenial property: trust.xenial.com is NXDOMAIN, www.xenial.com/trust/, /security/ and /legal/ all return 404 (the footer's only legal links are /privacypolicy/, /Terms-of-use/, a Canadian privacy statement and the service-terms PDFs). The published Consolidated System Terms and Conditions (3/2025) at /legal/service-terms/Xenial-Consolidated-System-Terms/index.pdf contain zero occurrences of PCI, P2PE, SAQ or cardholder data. Full-text search of both Paligo portals (product-documentation 786 pages / 3,917 sections; developer-resources 293 pages / 3,333 sections) returns PCI only as device-level certifications in hardware specification tables - 'TR39 / PCI PIN 2.0 DATA and PIN certified key management' and 'PCI PTS 6.x' on the Moby5500 - never a company or platform attestation. A web search for a Xenial SOC 2 / PCI attestation returned no first-party page. Left unknown, not no: enterprise QSAs and AoCs are routinely shared under NDA with chain customers rather than published, and Xenial's own API reference is customer-gated (Genius Portal carries a per-user 'API Documentation Access' permission), so a customer-facing compliance package could exist behind the same wall.

reliability-mfa-role-based-access

Multi-factor authentication is mandatory, not optional: asked "Can companies or individual users opt out of multi-factor authentication (MFA)?", the vendor answers "No." Users "authenticate by entering their username and password, plus a unique code", delivered by email for most products and additionally by SMS for back office. "Xenial and Global Payments are using OKTA authentication." One documented exception: "MFA is not required for POS or XKM install. Portal users performing installs will NOT be challenged." Combined with Enterprise Portal roles, permissions and user groups scoped to the site hierarchy. https://www.xenial.com/what-is-mfa/ · retrieved 2026-08-02

reliability-self-serve-training

Extensive first-party self-serve material is publicly published: a product-documentation site spanning Point of Sale, Back Office, Kitchen, Drive Thru, Digital Menu Board, Mobile Manager, Add-on Products, Classic Products and Hardware, in three languages, plus per-product release notes, a developer-resources site, and a Genius Academy LMS with a published course schedule on the support page. In-terminal training mode is not documented. https://www.xenial.com/product-documentation/ · retrieved 2026-08-02

reliability-failover-terminal-role differentiator

Genius POS has no master/server role to fail over, which is the stronger form of what this claim tests. The DataSync chapter of the developer portal states it plainly: 'DataSync allows each terminal to operate as an independent unit. In the event of data loss, DataSync uses the local network to restore the terminal(s). Terminals do not have a single master server, which results in a need to replicate the single state of all generated data between the terminals within a single site.' The replication is peer-to-peer and continuous - every 500ms each terminal broadcasts per-feed state over UDP, peers diff it and pull missing resources over TCP terminal-to-terminal by IP - and the cloud path is per-terminal too: 'Transactional data is enqueued on the POS terminal where the transactions were performed' and sent to Genius Cloud independently. The POS Online/Offline Data Flow chapter confirms the operational consequence: on loss of LAN a terminal keeps taking orders and 'Terminals with Bluetooth or wired connections (USB, Serial) are not impacted' for payment, with only cross-terminal functions (order sharing, store-wide reporting, 86 synchronisation) degraded. The one place the phrase 'master terminal' occurs is unrelated - Expo Number Configuration's Shared mode picks one as the numbering focal point. https://www.xenial.com/developer-resources/en/genius-point-of-sale/enterprise-pos/datasync.html · retrieved 2026-08-08

reliability-cellular-backup

Cellular-capable terminals are documented; automatic failover to them is not. The All in One Handheld iRoc Max with Moby 5500 specification lists 'Connectivity Wi-Fi 6E, 802.11 a/b/g/n/ac/ax (2.4GHz/5GHz/6GHz); Bluetooth 5.2, 2G/3G/4G LTE, GPS, NFC' with 'Nano SIM x 1, eSIM (optional)' among its peripheral ports, and the Aava 10 Tablet lists 'Communication WLAN IEEE 802.11ax+r/k/v; WiFi6E, WiDi, WWAN, BT5.3, BLE'. Shortfall: no page in either portal describes automatic or manual failover from Wi-Fi/LAN to the cellular radio, no carrier or data plan is offered, and the chapter that would say so - POS Online/Offline Data Flow, which enumerates component by component what happens on Loss of Internet and Loss of LAN - never mentions cellular as a fallback path; its answer to losing internet is queue-and-forward, not a second WAN. The countertop and kiosk SKUs (GC26, XC23, N Series Nano) list only Ethernet and Wi-Fi. https://www.xenial.com/product-documentation/en/genius-hardware/all-in-one-handheld-iroc-max-with-moby-5500.html · retrieved 2026-08-08

commercial-month-to-month-contract differentiator

The published standard agreement sets a five-year default. Consolidated System Terms and Conditions (3/2025) Section 4.1.2: 'Unless otherwise expressly set forth in a Sales Agreement, (i) the initial period for the provision of the Software Service shall be five (5) years from execution of the applicable Sales Agreement (the Initial Subscription Term); and (ii) following the Initial Subscription Term, subscriptions to the Software Service will automatically renew for additional successive periods of one (1) year'. Support runs on its own term, one year by default if the Sales Agreement is silent (Section 4.1.3). The thirty-day termination right in Section 4.1.1 applies only to the System Terms themselves 'when there are no active Sales Agreements' - it is not a way out of a live subscription. No month-to-month, no-minimum-term or trial-to-monthly offer appears in the terms, on the pricing pages, or anywhere in the two documentation portals. https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/index.pdf · retrieved 2026-08-08

commercial-no-early-termination-fee differentiator

The published terms say the opposite of the claim. Section 4.4 (Fees Upon Termination): 'All Fees are non-cancellable and all amounts paid are non-refundable; provided, however, that if this Agreement is terminated by you in accordance with Section 4.2 (Termination), we will refund to you any prepaid Fees under the Sales Agreement on a pro-rated basis... If this Agreement is terminated by us in accordance with Section 4.2 (Termination), you will pay to us any unpaid Fees covering the remainder of all Sales Agreements.' Acceleration of the unpaid balance of the remaining term is exactly the liquidated-damages exposure the claim asks to be disclaimed. Section 4.2 gives the operator a for-cause exit only (thirty days' notice on an uncured material breach, or insolvency); there is no convenience termination of a live Sales Agreement, and Section 4.1.2 sets a five-year default term. Section 4.4 also permits Global to 'require you to make payments for all lapsed periods as a condition of resuming Support Services'. https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/index.pdf · retrieved 2026-08-08

commercial-autorenew-terms-published

Both the renewal term and the notice window are in publicly accessible contract terms rather than only in a signed quote. Consolidated System Terms (3/2025) Section 4.1.2: subscriptions 'will automatically renew for additional successive periods of one (1) year (each a Renewal Subscription Term), unless either party gives the other party written notice of non-renewal at least sixty (60) days before the end of the relevant Initial Subscription Term or any Renewal Subscription Term, as applicable.' Support renewal is stated on the same pattern in Section 4.1.3: the Support Term renews for one year and 'Customer must notify Global in writing at least sixty (60) days prior to the expiration of the then-current Support Term or Renewal Support Term of its election to terminate Support', with Global invoicing 'approximately thirty (30) days prior to expiration... at our then-current Fees'. Notices must follow Section 13.10. The document is linked from the xenial.com footer as a PDF and needs no login. https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/index.pdf · retrieved 2026-08-08

commercial-processing-not-bundled differentiator

The POS is documented to run on payment platforms other than its parent's. Data Management > Ordering Settings > Peripherals ships a Peripheral Schema dropdown for payment devices whose documented schemas are Payment (generic, LAN/OPOS/Bluetooth), Payment BAMS (FirstData) (LAN and OPOS), FreedomPay (SDK), Payment Genius (LAN and USB), Payment Moneris (LAN), Payment TransEnd (LAN and OPOS), Payment Verifone (LAN and Bluetooth), and Custom Payment (LAN/OPOS/Bluetooth). Each generic and branded schema carries a 'Payment Platform - From the dropdown, select the processing application used by the device' field. Beyond the shipped list, the developer portal publishes a Custom Payment Adapter - 'a plugin that extends our POS functionality' - with a documented interface (Constructor(config: PaymentDeviceConfig), setAdapter, getAvailableFeatures, batchReport, safReport, and the Connection Adapter methods), configured by pointing the peripheral at an 'Adapter URL' with JSON options. The published System Terms contain no processing-exclusivity clause and never mention card acquiring at all. Caveats worth recording rather than treating as a shortfall: a custom adapter requires Xenial's sign-off ('clients and/or integrators are required to submit their code to us for review and approval'), FreedomPay sites are limited to one payment service per company at a time, and commercial pricing is not published, so a specific chain's Sales Agreement could still bundle processing - the 2026 CKE award was announced as exclusive U.S. POS and in-store payments. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/peripherals/payment-device--lan-.html · retrieved 2026-08-08

commercial-interchange-plus-published differentiator

No processing rate of any structure is published.

commercial-rate-increase-clause differentiator

Re-checked 2026-08-08. The only agreement Xenial publishes is the Consolidated System Terms and Conditions (3/2025), the software and equipment terms linked from the site footer, and its full text contains no card-processing provisions: zero occurrences of "interchange", "payment services" or "Card Brand", and the single "merchant" hit is inside "MERCHANTABILITY". Those terms do reserve unilateral repricing on the SOFTWARE side without any cap -- Support renews "at our then-current Fees" (4.1.3), out-of-warranty work is billed per the "then-current Support Services Price List, as it may be revised by us from time to time in our discretion" (6(vi)), late fees are "subject to change in our discretion" (5.4), and Global "may modify these System Terms, in whole or in part, at any time" -- but that is not the processing agreement this claim asks about. The Global Payments card-processing agreement governing rates, interchange pass-through and exit-on-increase is not published on any Xenial property, so its terms cannot be read and no positive finding either way is available. Unresolved.

commercial-pricing-published

Quote-only. No per-location or per-terminal dollar figures on any vendor property; all paths route to Book a Demo.

commercial-module-unbundling differentiator

Cloud POS packaging shows a base subscription plus separately purchasable add-ons (kitchen management, inventory, scheduling, CRM, loyalty, email). Independent cancellation terms are not published. https://apps.apple.com/us/app/xenial-shell/id1463045984 · retrieved 2026-08-02

commercial-hardware-purchase-outright

Outright purchase is explicitly offered as an alternative to the as-a-service fee, satisfying the no-mandatory-lease half — but no published price, so the criterion is only half met. https://www.xenial.com/products/pos-hardware/ · retrieved 2026-08-02

commercial-hardware-not-locked differentiator

A documented Android/iOS/Windows install path plus a publicly downloadable Google Play build ("Genius Enterprise POS", com.xenial.shell.app) establishes that the software is not bound to vendor-supplied hardware. Scope note added on 2026-08-02 verification: this is an architectural statement, not a commercial one — Xenial sells its own hardware line and publishes no prices for it, and no contract language on hardware sourcing is public. https://play.google.com/store/apps/details?id=com.xenial.shell.app · retrieved 2026-08-02 adversarially verified

commercial-implementation-fee-published

No implementation, menu-build, onboarding or training fees published, and none stated as $0.

commercial-data-export-self-serve

Back Office ships a dedicated Export Data module, so operator-driven export exists. Whether it covers full transaction-level history without support involvement is not documented. https://www.xenial.com/product-documentation/en/genius-back-office.html · retrieved 2026-08-01

commercial-export-customer-and-loyalty differentiator

Operator-run exports exist but none of the three datasets in this claim is among them. The Back Office Export utility enumerates its own scope: 'The Back Office modules from which data can be exported include: Cash Sheet, Employees, Inventory, Menu Analysis, Menu Items, Payroll, Product Mix, Purchases, Security Users, Time Punches, Transaction Level Detail (TDL)' - transaction-level detail is exportable to a named file per store and date range, so tender-level history leaves the system in machine-readable form. Shortfall: there is no guest/customer module, no loyalty module and no gift-card module in that list. The nearest report-level substitutes are partial at best - Reports > Sales carries 'Liability Detail - Detailed information about gift certificate sales' and 'Liability Summary', which are sales of liability items rather than outstanding liability balances, and a 'Shipping Report' that 'contains details about orders flagged for shipping including the respective customer name and address'. Loyalty is provider-side: the offline chapter names 'Loyalty (Beanstalk)' and states 'Loyalty requests received by Gift and Loyalty (GL) are sent to the Loyalty provider where responses are processed and returned to POS', so point ledgers sit with the loyalty partner, and Gift Provider Profiles similarly point at an external gift processor's BIN-validation URL. No documented path exports a guest record set, a point ledger or a gift-card liability balance. https://www.xenial.com/product-documentation/en/genius-back-office/export-data.html · retrieved 2026-08-08

commercial-post-termination-export-window differentiator

A defined window exists but it is a request-and-return, not continued self-serve export. Consolidated System Terms (3/2025), Schedule A Section 4.3.3 (Customer Data Portability and Deletion): "Prior to or within thirty (30) days after the effective date of termination or expiration of these System Terms, Customer may request in writing that Global return all Customer Data to Customer. Within forty-five (45) days of its receipt of Customer's written request, Global will provide Customer with an estimate of the cost of such return of Customer Data if Customer is requesting that the Customer Data be returned in a specific format not normally provided by Global; otherwise, Global shall deliver the Customer Data to Customer free of additional charge." Shortfalls, all in the same or an adjacent clause: (i) the operator cannot export for itself during the window -- Section 4.3.1 disables "all Authorized User access to the Software Service, including any portal, reporting or other functionality" on termination, so retrieval depends on Global performing the return; (ii) the returned set is capped -- "Global's obligation to return Customer Data is limited to the following: (a) general information regarding how the Customer Data is structured; (b) ninety (90) days of detailed transaction data for transactions processed by the Services; and (c) all summary transaction data collected by Global not to exceed the prior seven (7) years"; (iii) a non-standard format is chargeable and delivery waits on payment of Global's estimate; and (iv) if no written request is made within the thirty days, "Global will have no obligation to maintain or provide any Customer Data, and will thereafter delete or destroy all copies of Customer Data in its systems". https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/index.pdf · retrieved 2026-08-08

commercial-data-ownership-clause differentiator

Half of this claim is met explicitly and the other half is contradicted. Ownership: Section 3.1 ends 'Ownership and title to your data shall remain with you', and Section 3.2 defines Customer Data as 'any data, content or other materials of any type that you upload, submit or otherwise transmit to or through the System, including but not limited to menu pricing and data concerning or relating to your customers'. Shortfall: the terms do not constrain Global's use of that data to aggregated or de-identified purposes - they do the reverse. Section 3.4 (Our Use of Data): 'you unconditionally accept and acknowledge that Global may collect, use, sell, transfer and disclose non-identifying data and other information relating to the provision, Use and performance of the System and related systems and technologies, Customer Data, and information about your and your customers' use of the System', with 'transfer' defined to include transmission to a third party 'including, but not limited to, your Brand'. Global separately owns all Aggregated Data outright and may disclose or transfer it in a corporate transaction. Section 3.3 also takes 'a worldwide, perpetual (but revocable hereunder) royalty-free license to host, copy, transmit and display the Customer Data', and Schedule Brand Rights permits routing daily menu sales, ticket count and product mix to the franchisor. So the merchant holds title while the vendor holds an express right to use, sell and disclose the same data beyond de-identified use. https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/index.pdf · retrieved 2026-08-08

commercial-source-available-selfhost

Proprietary commercial SaaS from a Fortune 500 subsidiary; no source availability or self-hosting option.

commercial-pci-p2pe-tokenization

Hardware-encrypted card entry and tokenization are both documented; the scope-reduction claim and the SAQ are not. Encryption at the reader is specified per SKU - the Genius All In One Handheld with Moby5500 lists 'Encryption AES, TDES-DUKPT, RSA or On-Guard DATA key (SRED) TR39 / PCI PIN 2.0 DATA and PIN certified key management', 'Remote key update service (Ingenico-hosted service)' and 'Certifications and security... EMV L1 and L2 Contact, EMV L1 Contactless... SCR Class; PCI PTS 6.x'. Tokenization appears as a configurable behaviour in Company Preferences > Payments: 'Allow Recording Card Token - Toggle Yes to record the card token provided with the payment card transaction in the order data. The card token can be used for customer intelligence (CI) and reporting purposes. Due to limitations of the particular payment provider, the card token may not be provided to the POS in the transaction.' Shortfall: nothing states the solution is a PCI-listed validated P2PE solution, no SAQ is named anywhere (SAQ, SAQ A and SAQ P2PE-HW return zero hits across 7,250 documented sections and across the published System Terms), no P2PE Instruction Manual is published, and the tokenization setting is explicitly provider-dependent rather than guaranteed. SRED-capable hardware is not the same as a validated P2PE listing, and the claim asks for the SAQ to be named. https://www.xenial.com/product-documentation/en/genius-hardware/all-in-one-handheld-with-moby5500.html · retrieved 2026-08-08

commercial-pci-dss-4-controls

One of the two named controls is documented as a product behaviour; the PCI framing and the other control are not. MFA on the back-office console is documented and non-optional: 'The following describes the process for Multi-Factor Authentication (MFA) of users on the Portal', a new user logging in 'is sent a One-time verification code email', an existing user logging in likewise receives 'A One-time verification code email... to the provided email address', lockout follows 'five (5) failed login attempts', and administrators have a 'Clear MFA for User' action in User Management. Shortfall: the documentation never frames any of this as a PCI DSS v4.0.1 control - PCI DSS 4, 6.4.3, 11.6.1 and 'script integrity' return zero hits across both Paligo portals (786 + 293 pages) and across the published Consolidated System Terms; no payment-page script-integrity or change-and-tamper-detection mechanism is described for the hosted-ordering surfaces; and nothing states that MFA extends to POS terminal sign-on, which is a PIN-and-role model in the documented Enterprise POS app rather than a second factor. There is no Xenial trust center (trust.xenial.com NXDOMAIN, /trust/ and /security/ 404) where such a mapping would normally be published. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-portal/login-to-portal.html · retrieved 2026-08-08

commercial-soc2-attestation

Re-checked 2026-08-08 across every first-party surface now known to exist. There is no Xenial trust center: trust.xenial.com is NXDOMAIN and www.xenial.com/trust/, /security/ and /legal/ return 404; the footer's legal links are only /privacypolicy/, /Terms-of-use/, /legal/canadian-privacy-statement.stml and the service-terms PDFs. SOC, SOC 2, ISO 27001 and 'attestation' return zero occurrences in the published Consolidated System Terms and Conditions (3/2025) - the security clause there is Section 3.5, 'Global implements security procedures to help protect Customer Data from security attacks. However... we cannot guarantee that our security procedures will be error-free' - and zero occurrences across the full-text dump of both Paligo portals (product-documentation 786 pages / 3,917 sections and developer-resources 293 pages / 3,333 sections). The only audit right in the terms runs the other way (Section 13.6, Global auditing the customer's use), except in the EU/UK/Switzerland data-processing clause 3.10.1(ix), which does 'allow Customer the right to audit Global's processing operations, systems and/or facilities'. A web search for a Xenial SOC 2 Type II statement surfaced no first-party page. Left unknown rather than no because this claim is satisfied by a statement made under NDA or on request, which is exactly what an enterprise vendor selling to QSR chains would keep off the public web, and Xenial demonstrably gates other reference material this way - Genius API documentation is a per-user permission inside the Genius Portal.

commercial-privacy-dsar-tooling

The DPA half is met and the in-app tooling half is not. Xenial publishes data-processing terms inside the standard agreement rather than as a separate signable DPA: for EU, Iceland, Liechtenstein, Norway, UK and Switzerland locations, Section 3.10.1 is replaced by a processor clause under which 'Global will act as a data processor', may not engage sub-processors 'without the prior specific or general written authorization of Customer', must notify the customer of breaches, allows a customer audit right, and must 'provide reasonable assistance, upon the reasonable request of Customer and subject to all applicable charges or fees at our then-current rates, to enable Customer to comply with its obligations of providing access to Personal Data, and the restriction, anonymization, deletion and/or rectification of Personal Data under the Data Protection Laws and, if required by Customer, to return or delete all copies of the Personal Data'. The Canadian variant instead incorporates the privacy policy at xenial.com/privacypolicy/ by reference. Shortfall: DSAR fulfilment is a manual, chargeable assistance obligation on Xenial rather than operator self-service, and no in-app tooling for locating, exporting or deleting an individual guest's records is documented anywhere in the 7,250 sections of the two portals - the only deletion control found is Mobile Manager's Accounts > Privacy area, which offers 'Delete my personal information' for the signed-in staff user's own account, not for guests. There is also no CCPA/CPRA-specific operator clause; the US terms carry only the general Data Protection Laws warranty in Section 7.2 putting consent and notice duties on the operator. https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/index.pdf · retrieved 2026-08-08

commercial-wcag-kiosk-accessibility differentiator

Re-checked 2026-08-08. No VPAT or Accessibility Conformance Report exists on any reachable Xenial surface: www.xenial.com/accessibility/ returns 404, as do /legal/, /trust/ and /security/, and the site footer links only the privacy policy, terms of use, the Canadian privacy statement and the service-terms PDFs. 'accessibility', 'WCAG', 'Section 508', 'screen reader', 'tactile' and 'audio jack' return no substantive hits across the full-text dump of both Paligo portals (product-documentation 786 pages / 3,917 sections and developer-resources 293 pages / 3,333 sections) - the only matches are the ordinary sense of the word ('easily accessible', 'accessible through several areas in Data Management'). Notably the kiosk product is not documented in either portal at all: kiosks appear only as a consumer of menu data in the POS Online/Offline Data Flow chapter ('Kiosks consume menu data from Genius Cloud and send orders via Online Ordering') and in the integration-partner directory's Kiosk category, so there is no kiosk UI documentation in which a non-visual access mode could be described either way. A web search for a Xenial kiosk VPAT returned nothing first-party. Left unknown rather than no because a VPAT is routinely supplied to enterprise and public-sector buyers on request without being posted, and the absence of any kiosk documentation at all means this is an unlit surface rather than a surveyed empty one.

commercial-dual-pricing-compliant differentiator

Automatic surcharging exists and is receipt-disclosed; the card-network compliance controls are absent from the configuration surface. The Fees editor is the mechanism: 'Use the Fees editor to define fees to add to qualifying orders either manually or automatically as dictated by business rules. For example, apply an automatic 5% surcharge on all product transactions. Applied fees are printed on the guest receipt and optionally the POS reports.' Its Automatic Fee editor is a closed set of pages - General (Fee Method: Fixed Amount, Fixed Percentage with a Maximum Amount cap and pre/post-discount basis, or Range), Availability (order source, destination, event type, each All / Only the Following / Excluding the Following), Qualify Criteria (required items, exclusive product tags) and Apply Criteria (item sources and items feeding a percentage calculation). Shortfall: no criterion anywhere in that surface references tender, card brand, card type or funding source, so a surcharge cannot be automatically suppressed for debit and prepaid cards as the networks require - the fee is resolved against the order before a tender is selected. There is no cash-discount or dual-pricing construct ('dual pricing' and 'cash discount' return zero hits across both portals), no surcharge cap tied to the network 3% ceiling, no state-exclusion logic, and no menu-board or point-of-entry disclosure requirement is described in the fee configuration or in the digital-menu-board documentation. Receipt disclosure is the one compliance element that is met. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/fees/automatic-fee.html · retrieved 2026-08-08