Xenial

Provides a graphical floor-plan editor where an operator can draw sections, place tables of varying shape/capacity, save multiple floor-plan layouts per location, and assign sections to servers.

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

Supports splitting a check by item, by seat, by even N-way, and by arbitrary dollar/percentage amount, and merging checks or tables back together, including after partial payment.

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

Ships a first-party handheld ordering app running natively on the handheld device (not a remote/mirrored desktop session) that can send to kitchen and take a card payment tableside.

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

With the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen, and tender cash, and the vendor publishes what does and does not work offline.

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

Offers a first-party self-order kiosk that renders the same menu and modifier tree as the POS with no separate menu build, and the vendor documents ADA/accessibility conformance for it. differentiator

order-capture-kiosk-first-party

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

Supports drive-thru-specific order flow: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment.

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

Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.

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

Vendor ships a first-party AI voice ordering agent for phone and/or drive-thru that injects orders directly as POS orders, or publishes a documented API partner program for third-party voice AI. differentiator

order-capture-voice-ai

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

Supports order throttling: per-channel capacity limits per time slot with automatic quote-time extension when kitchen load exceeds a configured threshold. differentiator

order-capture-throttling

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

Accepts future-dated/scheduled orders with a per-channel lead time and automatically injects them into the make queue at a computed fire time rather than on receipt.

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

Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.

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

Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator

order-capture-order-ready-signal

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

Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.

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

Supports modifier groups nested at least three levels deep, each level with independent min/max selection counts and a forced-selection (required) flag.

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

A single modifier can carry different prices depending on the parent item and the selected size, configured as a matrix rather than by duplicating the modifier.

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

Supports modifier quantity tiers (light / regular / extra / double) with a configurable price multiplier per tier, distinct from adding the modifier twice.

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

Item base price can be defined as a grid across two variant axes (e.g. size x crust/preparation) with a per-cell price override. differentiator

menu-pricing-size-style-matrix

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

Items can define an included-modifier allowance (e.g. three toppings included) that automatically charges only for overage and credits or forbids substitutions per configuration. differentiator

menu-pricing-included-allowance

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

Supports combo/meal construction where components can be swapped with a price delta, and the system can automatically detect and convert eligible a-la-carte items in the cart into the combo price.

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

Upsell/suggestive-sell prompts can be configured per item and per channel (POS, kiosk, online), and the vendor reports attach-rate on those prompts. differentiator

menu-pricing-upsell-prompts

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

A single 86 action propagates automatically to POS, KDS, the vendor's own online ordering, kiosk, and connected third-party marketplaces, with a documented propagation latency.

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

Supports per-item countdown/par counts that decrement on sale and automatically 86 the item at zero, with a scheduled auto-restore. differentiator

menu-pricing-countdown-auto-86

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO NO. The Availability page publishes the complete item-availability state model and it is two booleans, not a count. Its Product Statuses table is a closed 2x2 of Active x Available - Live, 86’d, Inactive, Inactive 86’d - and the page states 'When a product is "86'd", it cannot be added to an order at the POS.' Availability is set by a toggle ('Toggle On if the product is currently "Live" at the site') plus 'Allow POS to Control Availability', and the 2026 March Feature Highlight re-publishes the same model as current, adding only a multi-site edit grid, two permissions and an Unavailable Products Report. There is no quantity field anywhere in it. Controls over the whole 11,269-section corpus: `countdown` 15 docs, every one a kitchen-cell timer, a Suite Catering event clock or a DMB promo timer; `par count` 0; `quantity available` 0; `auto 86` 0; `auto restore` 0; `count down` 0; `stock count` 0; `decrement` 3, all fractional-modifier or bug-fix text. `par level` (18 docs) is Back Office Par Level Units Setup and Chef Build To, both prep-projection floors for cook lists, and `deplete` (2 docs) is recipe depletion reporting. ONE SENTENCE HERE WAS WRONG AND THE ADVERSARIAL PASS CORRECTED IT: a per-item count DOES decrement on sale, but only in Venue Inventory (the stadium/venue product) - Sale Depletion Orders debit Quantity On Hand and a 2026-09-01 note records that a refund or void “should be credited back to original seller/session/site”. Nothing 86s at zero anywhere, which is the limb the claim turns on: `reaches zero` 0, `automatically unavailable` 0, `restore availability` 0 and `auto restore` 0 across 11,269 sections and across the 1,274 re-fetched pages, and the vendor’s own availability vocabulary, which the first pass never ran, resolves the same way - `sold out` (12 docs) is Digital Menu Board Swap Text When Sold Out driven by the boolean, `out of stock` (32) carries no threshold, `availability threshold` (1) is a 2022 Omni menu-publishing setting, and `remaining quantity` (2) is a Suite Catering par-stock column of which the docs say ‘venue staff need to calculate it and manually fill it in’. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/data-management/ordering-settings/product-list/create-product/availability.html · retrieved 2026-09-12 adversarially verified

Menus, individual items, and prices can be scheduled to activate and deactivate automatically by day and time in the location's own timezone.

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

Supports distinct price books per channel (dine-in, pickup, delivery, kiosk, each third-party marketplace) including percentage-markup rules applied to a base price rather than manual per-item entry.

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

Supports dual pricing / cash-discount at the item level with the card price displayed as the base price, applied consistently across POS, kiosk, and online ordering, and printed on the receipt. differentiator

menu-pricing-dual-pricing

CLAIM: item-level dual pricing / cash discount with the card price as base, applied across POS, kiosk and online ordering and printed on the receipt. VERDICT no. THE CONSTRAINT THE STANDING NOTE NAMED IS NOW LIFTED: it upheld unknown because the 1,197-file Wayback corpus 'stops in 2023, so absence here cannot exclude a feature shipped into Genius in 2024-2026'. The live 2026 Genius app is now held in full. NEW SURFACE: dm.xenial.com, 'DataManagement UI' - the entry named `dm_ui` in Xenial's own anonymous service registry at https://ssr.xenial.com (see the delivery notes) - is the current Genius menu/pricing/site configuration app (webpack namespace `webpackChunk_geniuspos_pos_datamanagement_ui`, class `theme-genius`). CENSUS BY SCRIPT-LOADER FIXPOINT: the runtime https://dm.xenial.com/runtime-es2021.44ce99f3ae07daa03f5d.js carries the chunk-hash table `r.u` with 1,292 entries; all 1,292 were fetched (1 required the runtime's special case, chunk 68592 -> common-es2021.be3a0e9e49fbc5511764.js) plus main-es2021 (14.9 MB) and the runtime - 36.6 MB, 1,294 files, and a second round over every fetched chunk produced 0 new chunk references. SOFT-200 CONTROL PASSED: https://dm.xenial.com/main-es2021.ZZZ.js returns 404 (548 B), so the 14.9 MB body is real. EVIDENCE: the price model is a closed four-member enumeration - STANDARD, PRICE_POINT, CONDITIONAL, CHILD_PRICES (chunk 59586, `selectedPriceType` switch and `isPricePointPriceType` / `isConditionalOrChildPriceType` helpers), with PRICE_POINT entities, site-specific prices and pricing-rule modals whose adjustment operations are replace / adjust-amount / percent. No member is tender-conditioned and no item carries a second price. CONTROLS over all 1,294 files, tokenised and case-insensitive: 'dual pricing' 0, 'dualPricing' 0, 'cash discount' 0, 'cashDiscount' 0, 'CashDiscount|DualPrice' 0, 'non-cash' 0, 'cash price|card price' 0, 'surcharge' 0, 'convenience fee' 0, 'service fee' 0. POSITIVE CONTROLS in the same corpus: 'pricePoint' 81, 'receipt' 120, 'PCI' 304, 'order_source' 225, 'tender' 34. POISON NAMED: the app ships an obfuscated i18n dictionary whose KEYS are base64-like, and one of them is literally "ByOd":"HTML" - a naive grep for BYOD hits it. Retrieved 2026-09-17. GRADE SET AT MERGE (324th): production JS bundle / script-loader census = grade B, not A, per the 321st precedent that downgraded sapaad override-audit A->B for source-map evidence. An anonymous OpenAPI spec can be A; first-party application code that the vendor does not publish as documentation cannot. https://dm.xenial.com/main-es2021.e76128ec72dc650e576a.js · retrieved 2026-09-17 adversarially verified

Menu changes can be staged as an effective-dated version, previewed before publish, and rolled back to a prior version after publish. differentiator

menu-pricing-versioning-effective-dates

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

Supports a central corporate menu template pushed to locations with field-level governance controlling which attributes a location may override. differentiator

menu-pricing-franchise-hierarchy

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

Stores allergen flags and nutrition values per item and publishes them to online ordering and third-party menus, and can derive nutrition from linked recipe components rather than manual entry.

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 items and modifiers can be linked to recipes/bills of materials so that a sale depletes theoretical inventory and yields item-level theoretical food cost. differentiator

menu-pricing-recipe-linkage

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

Pushes menus to third-party marketplaces through a certified direct integration (not scraping or a menu-management middleman) and surfaces per-item sync status and rejection errors to the operator.

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

Supports rule-based dynamic pricing where item price varies automatically by time, demand, or channel, with configurable floor/ceiling guardrails.

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

The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator

payments-processor-choice

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

Vendor publishes card-processing pricing publicly (a specific flat rate or interchange-plus markup) rather than quote-only. differentiator

payments-published-rates

Upheld and now cited. No card-processing rate for Xenial or for Genius for Enterprise appears on any vendor property: across a 175-document corpus read 2026-09-09: an href fixpoint over www.xenial.com that closed at 181 URLs, the 86 sitemap entries that still resolve, and the four legal PDFs, including the Xenial Consolidated System Terms (3/2025) in English, Spanish and French-Canadian -- three renderings of ONE document, not three instruments, `interchange`, `basis points`, `bps`, `flat rate`, `discount rate`, `processing rate`, `per transaction fee`, `surcharge`, `cash discount`, `dual pricing`, `merchant of record` and `acquirer` occur zero times, tokenised and as bare substrings alike -- and that zero includes the full 181,483-character English text of the Consolidated System Terms, which is where a rate structure would have to be defined if one were published at all. The terms instead route all fees to the bilateral Sales Agreement (Section 5.1), and where they touch card processing directly they disclaim it: for mobile ordering, 'all payment processing is the responsibility of the App Provider and its payment processors'. A word on the instrument, because the obvious one is a fossil: www.xenial.com/sitemap.xml lists 500 URLs, EVERY ONE stamped lastmod 2020-12-11, and 414 of them now 404 -- including 361 of the 364 product-documentation entries, which are .stml files from a site since rebuilt. A sitemap can be complete-looking and almost entirely dead, so this corpus rests on a live href fixpoint instead. docs.xenial.com, developer.xenial.com, wiki.xenial.com and status.xenial.com all fail DNS resolution. https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/ · retrieved 2026-09-09

Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator

payments-dual-pricing

CLAIM: native dual-pricing / cash-discount mode storing two prices per item and printing both cash and card totals on the guest check and receipt. VERDICT no, on the same 1,294-file closed script-loader fixpoint census of dm.xenial.com (Genius DataManagement UI) set out under menu-pricing-dual-pricing - which lifts the standing note's stated limit that the 2023 Wayback capture 'cannot exclude a feature shipped into Genius in 2024-2026'. The receipt and tender side is inside this corpus: the terminal/site settings schema (chunk 40911) enumerates `receipt_printing_method` with the closed option list none / inherit_site_settings / 'Print on Tender' / 'Print on Total Save', plus display_print_option, display_email_option, display_sms_option, `prompt_donation_on_tender`, `pay_type_scheme_entity_id` (Payment Type Scheme) and a live receipt preview component (`xux-receipt-preview`); chunk 20356 is Create New Payment Type and 47187 Create New Payment Type Scheme. Nothing in any of it formats or stores a second total, and no payment type or price carries a cash-versus-card price pair. CONTROLS over all 1,294 files: 'cash price|card price' 0, 'non-cash' 0, 'dual pricing' 0, 'cash discount' 0, 'surcharge' 0. Positive control 'receipt' 120, 'tender' 34. Retrieved 2026-09-17. GRADE SET AT MERGE (324th): production JS bundle / script-loader census = grade B, not A, per the 321st precedent that downgraded sapaad override-audit A->B for source-map evidence. An anonymous OpenAPI spec can be A; first-party application code that the vendor does not publish as documentation cannot. https://dm.xenial.com/runtime-es2021.44ce99f3ae07daa03f5d.js · retrieved 2026-09-17 adversarially verified

Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator

payments-surcharge-guardrails

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

All first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay.

payments-emv-nfc

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

Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. differentiator

payments-softpos-tap-to-pay

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO NO. `Tap to Pay` 0 occurrences, `softPOS` 0, `tap-to-phone` 0 across all 11,269 sections including every 2026 release note. The Genius Hardware publication is the vendor’s own device catalogue and enumerates eleven devices, each with its own specifications page: Aava 10 Tablet, Active Tab5, All In One Handheld with Moby5500, All in One Handheld iRoc Max with Moby 5500, GC26, GC26 Merchant-Facing Display, Kitchen N Series Nano, Moby 5500M, TD22, Verifone P400, XC23. Every card-accepting entry is a dedicated reader or a handheld with an integrated Moby5500 SRED module; none is a commodity phone running a software-only reader. The 2026 January Feature Highlight confirms the architecture from the other direction - payment data reaches the POS over USB serial from the separate Genius/GPI Payment System device. A phone-only acceptance path would have to appear in this catalogue and does not. https://www.xenial.com/product-documentation/en/genius-hardware.html · retrieved 2026-09-12 adversarially verified

Guest can scan a QR code on the printed check or table tent to view and pay the check from their own phone, with the payment closing the check in the POS automatically. differentiator

payments-qr-guest-pay

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

Configurable tip pooling and distribution rules (by hours worked, sales, role percentage, or points) that produce a per-employee tip allocation exportable to payroll. differentiator

payments-tip-pooling

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

Card payments can be captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. differentiator

payments-offline-store-and-forward

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

Vendor publicly documents who bears the loss when a stored offline transaction declines on reconnect, and surfaces a post-reconnect report of failed offline payments. differentiator

payments-offline-decline-liability

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

First-party gift cards with real-time balance tracking, redeemable across every location in the group and through the online-ordering channel.

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

House/on-account tabs with per-account credit limits, running balance, and periodic statement or invoice generation.

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

A single check can be settled with multiple tenders and split by seat, by item, by even shares, or by arbitrary amount, with no hard cap below eight ways.

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

Voids, refunds, discounts, and no-sales require role-based authorization (manager PIN or approval) and write to an immutable audit log identifying the approver.

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

In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator

payments-chargeback-tooling

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO NO. `chargeback` 0 occurrences across all 11,269 sections; `dispute` 1, and it is not a payments surface. The Genius Cloud Reporting publication documents the report catalogue report-by-report, each with its own Parameters and Column Descriptions pages - 57 named reports across the five categories the Reporting Overview names ('The report categories include:' Audit, Inventory, Money, Payroll, Sales) plus Order Explorer and the Dashboard. No dispute, chargeback, retrieval-request or representment report or screen exists in it, and no evidence-submission workflow appears anywhere in the corpus. Bound honestly: the Overview says 'include', so the five categories are a floor rather than a ceiling, but the zero for the word itself is over the vendor’s complete published corpus, release notes included. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/reporting/reporting-overview.html · retrieved 2026-09-12 adversarially verified

Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator

payments-card-on-file

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

Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator

payments-payout-timing

CLAIM: vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. VERDICT: partial/C. 332nd NEW SURFACE: Global Payments' own Genius Enterprise product pages under www.globalpayments.com/point-of-sale/enterprise/ (enterprise-pos, back-office, kitchen-management, kiosk, digital-menu-board, drive-thru, food-service-management) plus the umbrella /genius page. Live host is a Cloudflare 403 to curl with full browser + Sec-Fetch headers and to WebFetch (a refusal, not an absence), so read via Wayback id_ captures 2025-09-09..2026-05-27 (never cited by any prior pass). EVIDENCE: the Genius umbrella page (www.globalpayments.com/genius, Wayback 20251103213301, 433 KB; the page carries an 'Enterprise businesses - Handle the demands of even the most complex environments. Genius manages high-volume drive thrus, streamlines kitchen workflows for global franchises and powers events for large venues' tile linking /point-of-sale/enterprise) FAQ: 'How quickly will I receive funds from customer transactions? In most cases, funding is deposited the following business day† (after settlement) to the financial account you provide at time of boarding. Your Global Payments representative will be happy to confirm this for you.' Footnote: '†Merchants on certain processing programs are not eligible for next-day funding; funding may be delayed by Global Payments’ Credit or Risk departments at any time.' The footnote is still on the page in the 20260527164420 capture. WHY NOT yes: (1) marketing page = grade C and this is a differentiator; (2) the statement is Genius-brand-wide and not tied to a Genius for Enterprise (ex-Xenial) processing programme - the footnote carves out 'certain processing programs', which could be exactly the enterprise ones; (3) no same-day/instant option and no weekend schedule is stated. It is the first Global Payments sentence tying a deposit schedule to the Genius brand; the earlier UCP payfac payout menu ('xenial' = 0) stays unattributable. Retrieved 2026-09-18. https://web.archive.org/web/20251103213301/https://www.globalpayments.com/genius · retrieved 2026-09-18 adversarially verified

A single account can route settlement funds to different bank accounts per location or legal entity (separate MIDs or split settlement) under unified reporting. differentiator

payments-multi-entity-routing

Re-checked 2026-09-05 against the 2023 Xenial Cloud Portal corpus and against the record's own 2026-08-08 live reading. The Portal does carry per-site payment identity: the Xenial Payment Router service is site-only ('This service is only available at the site-level. It is not available at the company-level') and carries Merchant Name, Merchant Site ID, Merchant Key, Web Checkout Key and Apple/Google Pay Merchant IDs; the live pass separately found a Moneris device 'Merchant ID' and a FreedomPay Terminal ID scoped per site. But nothing published configures where money lands. No page in either corpus exposes a bank account, settlement account, remittance destination or legal entity, the words MID and split settlement do not appear, and settlement is described only as batches sent to the clearing house. The claim asks whether a single account routes settlement funds to different bank accounts per location or legal entity under unified reporting; per-site gateway credentials are a plausible precondition for that, not evidence of it, and whether distinct site credentials translate into distinct deposits is a Global Payments merchant-agreement arrangement not documented on any Xenial property. Unresolved rather than partial, because a partial would assert a funds-routing capability that no page states. || 324th: NEW SURFACE, corroborating but not settling: Xenial's anonymous production service registry at https://ssr.xenial.com/ (112 services; nonsense control passes with 404 'Unknown Service') lists {"key":"xpr","name":"Xenial Payment Router","url":"https://xpr.xenial.com"}, and https://xpr.xenial.com/info answers 200 with {"appname":"Xenial Payment Router","appversion":"BUILD-3.10.34","statusmessage":"healthy"} - so the Payment Router the 2023 Portal documented as a site-only service is a LIVE PRODUCTION service in 2026, not a retired one, which removes the staleness objection to the record's existing per-site merchant-identity finding. What is still missing is unchanged: no public surface states whether one deployment can settle to two legal entities' MIDs simultaneously, nor how an order is routed between them. /swagger, /swagger/v1/swagger.json, /v3/api-docs, /openapi.json all 404 on xpr and on 14 other registry hosts probed; only /info is exposed. Retrieved 2026-09-17. || 325th: NEW SURFACE, cell still unknown. The Payment Router now has a documented book in the Genius developer portal (payment-router.html, payment-router-api---getting-started.html, authorize-and-capture-transaction-flow.html, sale-transaction-flow.html, operation-definitions-756297.html) and it is transaction plumbing only: authorize/capture and sale flows. Controls over the 100%-fetched 293-topic portal: 'bank account|remittance|split settlement|MID' = 0. The per-site merchant identity already in the record is therefore still unaccompanied by any published statement of where funds land. Retrieved 2026-09-17. || 328th: 328th: NEW SURFACE, no move, and the same publisher caveat as payments-payout-timing. The 100%-fetched 145-document developer.globalpayments.com corpus (its own /llms.txt manifest; nonsense control /docs/zzz-nonsense-control.md = 404 at 9 B) does document multi-account fund movement on Global Payments' Unified Commerce Platform - /api/transfers.md: 'Transfers represent the movement of funds from one Global Merchant Account to another', /api/accounts.md exposes per-account payout bank/card settings (bank_transfer_monthly_limit_amount, disable_payout_bank_transfer_limit_percentage, 'The account balance available for transfer or payout'), and /api/links.md enumerates UPDATE_PRIMARY_ACCOUNT and the micro-deposit validation pages for 'the primary payout bank information on an account'. That is a real multi-account settlement model, but it belongs to the UCP payfac programme and 'xenial' = 0 across all 145 documents, so it cannot be attributed to the Xenial POS. Also re-grepped for this cell, first time, the Xenial APK web-asset corpus described on hardware-byod (1,781 files / 9,489,331 chars): 'split settlement' 0, 'bank account' 0, 'merchant id' 0, payout 0, funding 0, and MID scores 1 in the Genius Shell main.js as a substring of unrelated minified code. Held unknown. Retrieved 2026-09-18. || 332nd: 332nd NEW SURFACE: Global Payments' own Genius Enterprise product pages under www.globalpayments.com/point-of-sale/enterprise/ (enterprise-pos, back-office, kitchen-management, kiosk, digital-menu-board, drive-thru, food-service-management) plus the umbrella /genius page. Live host is a Cloudflare 403 to curl with full browser + Sec-Fetch headers and to WebFetch (a refusal, not an absence), so read via Wayback id_ captures 2025-09-09..2026-05-27 (never cited by any prior pass). The only funding sentence on it is singular: 'funding is deposited the following business day (after settlement) to the financial account you provide at time of boarding' (/genius FAQ, Wayback 20251103213301). No per-location/per-entity bank routing appears on any of the 8 pages ('bank account(s)' 0, 'settlement' 1 = that FAQ, 'entity|entities' 0; 'funding' scores 19, almost all the nav link 'Business funding' - POISON). Not a `no`: a marketing FAQ is not a census of boarding options. Retrieved 2026-09-18. adversarially verified

Vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance / P2PE listing available to merchants on request.

payments-p2pe-pci4

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO PARTIAL. The first limb is now met by a first-party statement rather than marketing prose: the 2026 January Feature Highlight, describing the Genius USB Connection Type integration, states that the 'USB ecosystem system is PCI validated P2PE to so data coming from the GPI Payment System is not considered PCI data' (typography as published). That is the vendor asserting a validated P2PE solution in front of the POS, not merely E2EE in a brochure, and it is corroborated on the device side by the Moby5500 SRED / TR39 / PCI PIN 2.0 specifications in the Genius Hardware catalogue. SHORTFALL: the second limb is still unmet. `PCI DSS` 0, `Attestation` 0, `AOC` 0, `on request` in a compliance sense 0 across all 11,269 sections; no PCI SSC P2PE listing is referenced; and no trust centre exists to hold one (trust.globalpayments.com NXDOMAIN). Nothing states that a current PCI DSS 4.x Attestation of Compliance or the P2PE listing entry is available to merchants on request. https://www.xenial.com/release-notes/en/feature-highlights/previous-feature-highlights/2026-january---feature-highlights.html · retrieved 2026-09-12 adversarially verified

Items route to specific KDS stations by item, category, order type, or revenue center, with routing rules configurable per location without vendor involvement.

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

An expo screen consolidates items from multiple prep stations into a single order view and only marks the order complete when every contributing station has bumped its items.

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

Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator

kitchen-course-firing

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

Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator

kitchen-prep-time-pacing

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 load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator

kitchen-order-throttling

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

Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator

kitchen-channel-pause-propagation

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

Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator

kitchen-order-ready-callback

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

KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.

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

An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.

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

Configurable target cook times per station or order type, with visual color escalation and/or audible alert when a ticket exceeds target.

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

If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator

kitchen-printer-fallback

"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

KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator

kitchen-offline-operation

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

Station screens can display item-level build/assembly detail (recipe steps, portioning, or full modifier breakout) rather than only the ticket line text. differentiator

kitchen-item-build-screens

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

A bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order.

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

Edits made in the POS to an order already displayed in the kitchen visually flag the added, changed, or removed items on the live ticket. differentiator

kitchen-order-modification-alerts

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

Bumping an order ready triggers a guest-facing notification — SMS/text, app push, or an order-status display board — without a separate product purchase. differentiator

kitchen-guest-ready-notification

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

Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.

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

Reports actual ticket and per-station times (average and percentile) sliced by daypart, station, and order channel, exportable to CSV or an API.

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

Generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list.

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

Product includes a native in-house driver module: drivers are first-class entities with clock-in/out, assignment state (in-store / on-run / returning), and per-driver run history reportable from the POS itself (not via a third-party add-on).

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

Provides a dedicated dispatch/expo screen showing undispatched orders, driver availability, and elapsed time per order, with multi-order run batching (assigning 2+ orders to one driver as a single run).

delivery-dispatch-board

CLAIM: a dedicated dispatch/expo screen showing undispatched orders, driver availability and elapsed time per order, with multi-order run batching. VERDICT: MOVED unknown -> partial (B). The standing note treated the permission rows as evidence that 'a dispatch screen exists ... contents unpublished' and held unknown; re-reading the claim conjunct by conjunct, TWO of its four elements are affirmatively published by the vendor, which is part of the claim itself rather than an adjacent feature. EVIDENCE, re-fetched live 2026-09-18 at HTTP 200 / 1,219,398 B (raw bytes read, <!-- --> stripped first, so no tag-welding): the Genius Point of Sale > Foodservice Management POS > Employees permission enumeration publishes 'Delivery Dashboard' / 'Access the order delivery dashboard.' and, as a SEPARATE higher permission, 'Delivery Dashboard Manager (view all drivers)' / 'Access the order delivery dashboard and view all drivers.' A dedicated delivery dashboard therefore exists as a named, separately-permissioned screen, and driver visibility across the whole roster is a named capability of it. The same page carries the roster inputs ('Driver Cash Drop', 'Driver Settlement - Delivery driver cash settlement', and the Positions flag 'Delivery Driver? - If selected, the position involves delivering orders to customers in a vehicle.'), which is why delivery-driver-roster already stands at partial on this very URL. SHORTFALL (why not yes): an undispatched-order queue, an elapsed-time-per-order column and multi-order run batching are published nowhere - 0 hits over the 100%-fetched 293-topic Genius developer portal, 0 over the 1,197-file documentation corpus, and 0 over the 327th's new 1,524-file front-end corpus described below. Retrieved 2026-09-18. https://www.xenial.com/product-documentation/en/genius-point-of-sale/foodservice-management-pos/employees.html · retrieved 2026-09-18 adversarially verified

Dispatch includes a live map view with geocoded stops and system-generated route sequencing (turn order optimization) for a multi-stop run, not just a static address list. differentiator

delivery-route-map

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO NO. `geocode` 0, `turn-by-turn` 0, `stop sequence` 0, `optimize route` 0, `route map` 0, `courier` 1 - and that one is the Courier typeface in the DMB font requirements, a control’s own false friend. Latitude and longitude occur twice in 11,269 sections: automatic site geocoding in Portal Site Setup, and an EasyPost parcel-shipment response in Partner Relay. Nothing in the corpus dispatches to a map. The only delivery-dispatch surface Xenial publishes at all is a permission row in the Foodservice Management POS security-role list, a single row of the security-role table whose name cell reads ‘Delivery Dashboard Manager (view all drivers)’ and whose description cell reads ‘Access the order delivery dashboard and view all drivers.’ - TWO TABLE CELLS, not the one contiguous span this note first quoted - with no screen documentation behind it and certainly no geocoded stops or route sequencing. https://www.xenial.com/product-documentation/en/genius-point-of-sale/foodservice-management-pos/employees.html · retrieved 2026-09-12 adversarially verified

Captures live driver GPS position from a driver-facing mobile app and surfaces it back to the dispatch screen. differentiator

delivery-driver-tracking

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO NO. There is no driver-facing app to capture a position from. `GPS` matches 3 documents and all three are hardware radio specifications in the Genius Hardware device catalogue (iRoc Max, Aava 10, Galaxy Tab Active5); `location tracking` 0, `live location` 0, `driver app` 0. The documented mobile applications are enumerated and none is for a driver: Genius Mobile Manager, SuiteSpot, and the Nextep guest app. Every driver surface in the corpus is money or roster, not position - Driver Cash Drop, Driver Settlement, a Delivery Driver? position flag ('If selected, the position involves delivering orders to customers in a vehicle'), and the Delivery Dashboard Manager permission row. https://www.xenial.com/product-documentation/en/genius-point-of-sale/foodservice-management-pos/employees.html · retrieved 2026-09-12 adversarially verified

Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.

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

Tracks per-delivery driver compensation inputs — mileage or distance driven per run, per-delivery flat reimbursement, and driver-retained tips — and exports them to payroll as separate reimbursement vs. wage lines. differentiator

delivery-driver-comp

Upheld. The Wayback corpus reproduces exactly the money functions the 2026-08-08 pass found and they all concern cash the driver COLLECTS, not what the driver is PAID: Nextep > Employees (captured 2023-01-30) lists 'Driver Cash Drop - Delivery driver cash drop' and 'Driver Settlement - Delivery driver cash settlement'. Mileage, distance driven, per-delivery reimbursement and driver-retained tips return zero hits across all 1,197 files, and the Xenial/RTI Back Office Payroll export pages document wage and time-punch export with no reimbursement-versus-wage split. Held unknown because drivers are plainly a first-class Position ('Delivery Driver?' flag on the Positions editor) so the pay inputs exist somewhere unpublished. Resolved by: a Genius payroll-export or driver-settlement report showing per-run mileage or flat reimbursement lines. || 325th: NEW SURFACE, cell still unknown. Over the 100%-fetched 293-topic Genius developer portal 'mileage|reimburse' = 0, and no payroll topic splits reimbursement from wages (the Staff API and the Data Stream Time Punches feed carry punches and employee records only). The portal does confirm driver assignment exists as order state ('131 Order Is Assigned a Driver' in the Omni Order Injection and POSRequest error tables), so the pay inputs remain somewhere unpublished, exactly as the standing note reasoned. Retrieved 2026-09-17. || 327th: 327th, A POISON FINDING THAT RETIRES A FALSE LEAD FOR THIS CELL. 327th NEW COMBINED FIRST-PARTY FRONT-END CORPUS (nobody had run this cell against it): the 229 complete public source maps of FOUR Xenial SPAs already on disk (analytics.xenial.com, reports.xenial.com, xea.xenial.com, xvi.xenial.com; 118.9 MB) UNIONED with the 724 readable files of the closed 1,294-file script-loader fixpoint census of dm.xenial.com (Genius DataManagement, 49.5 MB) = 1,524 files / 168.3 MB of the vendor's own shipped code and i18n dictionaries. Denominator stated; these are BACK-OFFICE/analytics apps and by merge policy do not bound the store-level POS. Over it 'driver' scores 447 hits in the map set and 28 in dm - but every one is library code, not a delivery driver: reports.xenial.com's main.4672b942d3cda827.js.map carries localForage, whose API is literally DefinedDrivers/DefaultDrivers/driverName/defineDriver/setDriver/getDriver ('A driver name should be defined and not overlap with the library-defined, default drivers'), and dm's are DB/OPOS device drivers. Tokenising does NOT remove this poison; it has to be read. Tightened controls over the same 1,524 files: 'delivery driver|driver (name|assign|pay|comp|dispatch|list|manage)' = 63, all localForage driverName; 'driver tip' 0, 'mileage' 0, 'per-delivery' 0. So no driver-pay input exists anywhere in four Xenial SPAs plus the Genius configuration app either. Still unknown, not no: these are back-office/analytics apps and do not bound the store-level POS where Driver Settlement runs. Retrieved 2026-09-18. || 331st: 331st: NEW CORPUS, same answer, with a closed enumeration found. 331st CORPUS, run against this cell for the first time: the three Paligo publications' own search manifests on www.xenial.com (product-documentation/en/js/fuzzydata.min.js 3,988 sections / 790 pages; release-notes/en/js/fuzzydata.min.js 3,956 sections / 192 pages; developer-resources/en/js/fuzzydata.min.js 3,337 sections / 293 pages; all fetched 200 on 2026-09-18 with version=20260915 builds; 1,275 pages, 14.2 M chars). Controls are tokenised, word-boundary, case-insensitive. 'mileage' 0, 'reimburs*' 0, 'per-delivery' 0 across all 1,275 pages. Genius Portal publishes the Payroll report category as a closed list with full column descriptions (payroll-reports.html: 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, Tips Allocation Summary; columns are hours, rates, Reg $/OT $, Total Tips, Total $), the Business Rules > Payroll group is enumerated (no reimbursement rule), and Back Office 'Export Payroll' writes an hours file (e.g. 'Hours.csv'). None carries mileage or a reimbursement-vs-wage split. NOT proposed as `no`: the in-house delivery module that would hold per-run inputs is the Foodservice Management (Nextep) Delivery Dashboard, which the docs cover only as permissions ('Delivery Dashboard Manager (view all drivers)', 'Driver Settlement'), and its own Reports page says only 'Reports provides reports in various categories' - a manual that does not document the module bounds nothing about it. Retrieved 2026-09-18. adversarially verified

Can hand a first-party order to an on-demand courier marketplace (DoorDash Drive, Uber Direct, Nash, Relay or equivalent) natively from the POS, with the courier quote and status returning into the order record.

delivery-daas-dispatch

Upheld. Everything delivery-partner-shaped in this corpus is MARKETPLACE plumbing, not courier hire. Company Settings' 'Food Delivery Service' block (captured 2023-03-25) holds a Delivery Service URL, a Callback URL and an Order Source per provider - menu publishing and order attribution - and the freshest relevant page, Portal > Self-Service Integration Onboarding > Things to Know (captured 2025-06-08), is an OAuth 'Connect to the delivery partner' and site-mapping flow for storefront onboarding. Xenial Online Ordering's release notes name a 'Delivery Adapter' component that makes 'delivery service calls', but no page describes requesting a courier, receiving a quote, or a courier status returning onto the order. 'DoorDash Drive', 'Uber Direct', 'Nash' and courier-Relay occur zero times. Note the 2021 Order Source editor in this corpus has no 'Preferred Delivery Provider' field at all - that setting is a later, Genius-era addition, which is direct evidence that this capture set post-dates nothing and cannot bound the current product. Resolved by: a Genius courier-quote or on-demand-delivery configuration topic. || 324th: NEW SURFACE, not settling: Xenial's anonymous production service registry https://ssr.xenial.com/ (112 services, nonsense control 404 'Unknown Service') names {"key":"xad","name":"Xenial Delivery Adapter","url":"https://xad.xenial.com"} and that service is live - https://xad.xenial.com/info returns {"appname":"Xenial Delivery Adapter","appversion":"BUILD-3.10.165","appdateUTC":"2026-08-26","statusmessage":"healthy"}, built last month. So a first-party delivery integration component exists in production and is actively maintained, which the 2021-2023 corpus could only show as marketplace plumbing. It does not settle the claim: an 'adapter' names no courier network, exposes no spec (/swagger, /swagger/v1/swagger.json, /v3/api-docs, /openapi.json all 404; only /info is public), and a courier-hire flow cannot be inferred from a service name. POISON for future passes on this record: in the 1,294-file dm.xenial.com census 'delivery' returns 55 hits and every one is a NOTIFICATION or RECEIPT delivery method (`receipt_printing_method` titled 'Receipt Delivery Method', `alert_delivery_method` text_message / guest_waiting / e_mail / none, `delayed_delivery_wait`) - not one concerns food delivery; 'courier' and 'driver' are 0 in that corpus because the config app has no delivery module at all. Retrieved 2026-09-17. || 325th: NEW SURFACE, cell still unknown. Xenial now publishes a closed partner enumeration by product category, and its delivery category is marketplace/aggregator only: 'Delivery and Online Ordering: Checkmate, Deliverect, DoorDash, Grubhub, Olo, Paytronix, SkipTheDishes, Uber Eats'. The only shipping-style service the portal documents end to end is parcel, not courier: Partner Relay's next steps are 'Configure EasyPost as a Custom Service' and 'Create Shipping Service in Service Builder', and EasyPost is also the one delivery-adjacent name in the 'Operational' partner category. Controls over the 100%-fetched 293-topic portal: 'courier' 0, 'DoorDash Drive|Uber Direct|Nash' 0, against 'delivery' 216 hits in 28 topics. Held unknown rather than `no` because the enumeration names DoorDash and Uber Eats without saying which of their products is integrated (marketplace vs Drive/Direct), so it does not by itself exclude a courier-hire flow. SURFACE (new this pass, 100% of the publisher's own manifest): the LIVE Genius developer portal https://www.xenial.com/developer-resources/en/index-en.html publishes a TOC of 293 topic permalinks; all 293 were fetched at HTTP 200 on 2026-09-17 (3.10 MB of nav-stripped topic text). SOFT-200/CATCH-ALL CONTROL PASSED: /developer-resources/en/zzz-nonsense-topic.html returns 404 with a 0-byte body. www.xenial.com still 403s on /robots.txt to every client but serves /sitemap.xml (500 locs) and every topic page to curl with a browser UA. Positive controls in the stripped corpus: 'order' 3,314 hits/159 topics, 'loyalty' 571/26, 'delivery' 216/28, 'webhook' 50/14. Retrieved 2026-09-17. || 331st: 331st: NEW CORPUS, same answer. 331st CORPUS, run against this cell for the first time: the three Paligo publications' own search manifests on www.xenial.com (product-documentation/en/js/fuzzydata.min.js 3,988 sections / 790 pages; release-notes/en/js/fuzzydata.min.js 3,956 sections / 192 pages; developer-resources/en/js/fuzzydata.min.js 3,337 sections / 293 pages; all fetched 200 on 2026-09-18 with version=20260915 builds; 1,275 pages, 14.2 M chars). Controls are tokenised, word-boundary, case-insensitive. 'courier' 1 hit (the font name Courier - poison), 'DoorDash Drive|Uber Direct|Nash' 0, 'dispatch(ed) (a|the) driver|courier' 0, 'delivery quote|estimate' 0. The newest delivery work is marketplace-inbound: 2026 March highlights 'Online Ordering | UberEats Delivery Integration' (Connect to Uber Eats, store mapping, pause/unpause, order-ready and cancel notifications routed to the delivery provider); the Order Source 'Preferred Delivery Provider' enum is 'None; Uber Eats; DoorDash; Grubhub' (XDM-42398). Kiosk poison: genius-kiosk---getting-started.html sets 'Type Delivery Provider' for the Nextep kiosk service - a service-type label, not a courier. Held unknown (no courier module at all = hold, per merge rules). Retrieved 2026-09-18. || 334th: 334th NEW SURFACE: 218 Global Payments press releases (investors.globalpayments.com/news-events/press-releases, ?page=1..22 until empty, every detail page fetched 200 on 2026-09-18, 2.15 M chars of release text; 23 of them name Genius or Xenial, incl. 122 Xenial launch 2017, 473 Genius platform 2025-05-16, 486 Genius for Enterprise 2025-09-10, 490 higher education, 495 Uber Eats partnership 2025-11-18, 509 AI-first handheld 2026-05-12, 515 Genius World 2026-08-24). Tokenised 'DoorDash Drive|Uber Direct|Nash|courier' = 0 across all 218. The one delivery release (495, 2025-11-18) makes Uber Eats Genius' 'preferred delivery partner' with 'self-serve' onboarding and 'orders, updates and cancellations sync instantly between Genius and Uber Eats' - MARKETPLACE inbound, not a first-party order handed to a courier; POISON for this cell: 'Uber' here is Uber Eats, not Uber Direct. Consistent with the standing marketplace-only enumeration; still unknown. Retrieved 2026-09-18. adversarially verified

Supports hybrid dispatch: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. differentiator

delivery-daas-fallback

Upheld. No conditional courier-selection surface exists in the corpus: the rule engines that ARE fully enumerated here (the Fees editor's Availability/Qualify/Apply criteria and the Order Source editor's option list, captured 2021-2023) condition only on order source, destination, event type, product tags and order total - never on driver availability, wait time or zone - and 'hybrid dispatch', 'overflow' and 'fallback' return nothing. Held unknown rather than no because the in-house dispatch side it would sit on (the Nextep/FSM Delivery Dashboard) is documented only as a permission, and because this Wayback set stops in 2023 while the base DaaS hook itself is a later addition. Resolved by: a Genius dispatch-rules topic showing an automatic hand-off threshold. || 324th: NEW SURFACE, not settling: the live production 'Xenial Delivery Adapter' (XAD, BUILD-3.10.165, built 2026-08-26, healthy) discovered in Xenial's anonymous service registry https://ssr.xenial.com/ establishes that first-party delivery integration code is current rather than the 2021-2023 artefact the standing note had to work from. No conditional courier-selection surface is reachable anonymously: XAD publishes /info only (/swagger, /swagger/v1/swagger.json, /v3/api-docs, /openapi.json all 404), and the complete 1,294-file script-loader fixpoint census of the current Genius configuration app dm.xenial.com contains no delivery module whatsoever - 'courier' 0, 'driver' 0, 'geofenc' 0, and its 55 'delivery' hits are all receipt/notification delivery methods (poison). Overflow-to-DaaS rules remain undetermined. Retrieved 2026-09-17. || 325th: NEW SURFACE, cell still unknown: over the 100%-fetched 293-topic Genius developer portal there is no conditional courier-selection surface - 'courier' 0, 'DoorDash Drive|Uber Direct|Nash' 0, 'overflow' 0 - and the published partner enumeration (genius-integration-partners.html) lists delivery partners as marketplaces (Checkmate, Deliverect, DoorDash, Grubhub, Olo, Paytronix, SkipTheDishes, Uber Eats) with no dispatch-rules topic attached to any of them. Retrieved 2026-09-17. adversarially verified

Offers direct, first-party certified API integrations with DoorDash, Uber Eats, and Grubhub marketplaces (vendor-owned, not solely resold through Otter/Deliverect/Chowly/ItsaCheckmate middleware). differentiator

delivery-3p-direct-integration

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

Third-party marketplace orders inject automatically into the POS as normal tickets that fire to KDS/printers without tablet re-keying or manual accept.

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

Menu, pricing, modifiers, and photos publish from the POS master menu out to connected third-party marketplaces, including channel-specific price markups, without maintaining a separate menu in each portal.

delivery-menu-push

DoorDash publishes a machine-readable registry of its integration partners at https://merchants.doordash.com/api/partner-integrations — 64 providers, each tiered PREFERRED (12), CERTIFIED (47) or AT_RISK_OF_SUSPENSION (5), and each carrying an explicit true/false flag for 23 named integration features across four collections. It is served anonymously and merchants.doordash.com/robots.txt permits it. The programme is described, and its eight high-quality features defined in prose, at https://merchants.doordash.com/en-us/learning-center/doordash-preferred-integrations-program; the merchant-facing label for each flag comes from the label dictionary embedded in DoorDash's integrations comparison page. SCOPE: this attests the vendor's DOORDASH integration specifically — not Uber Eats, not Grubhub, and not the POS in general. DIRECTION: a true flag is a positive attestation; a false flag is NOT a reliable negative on its own, because Lavu's help centre documents a DoorDash temporary-closure control with scheduled auto-reopen while Lavu's `STORE_AVAILABILITY_WEBHOOKS` flag reads false, and Xenial's developer docs enumerate an order-ready notification while its `SUPPORT_ORDER_READY_SIGNAL` flag reads false. The flag `MENU_PULL_SUPPORTED` ('Real-time menu syncing') is TRUE for `xenial`, and the registry classes that entry PROVIDER_AGGREGATION_TYPE_POS rather than MIDDLEWARE_AGGREGATOR. THIS CORRECTS THE PRIOR REASONING: the cell was scored on the premise that menu push is achievable through the Deliverect integration rather than a first-party push from the POS master menu, and DoorDash records Xenial as holding its own first-party menu integration. `partial` is retained because no flag covers modifiers or channel-specific price markups for this provider — `CHANNEL_BASED_MENU` reads false but sits inside the ENABLING_DDOO collection, which carries `active: false` for `xenial`, so it is not-applicable rather than a measured absence. https://merchants.doordash.com/api/partner-integrations · retrieved 2026-09-12

Marking an item or modifier 86'd in the POS pushes item-level out-of-stock status to connected third-party channels in near real time, and restores it on availability (DoorDash requires item and item-option 86ing of new POS partners).

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

Store can be paused/deactivated on each connected third-party marketplace from inside the POS with a timed auto-reactivation, rather than only from each marketplace's own tablet or portal.

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

Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. differentiator

delivery-3p-reconciliation

CLAIM: a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemising commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. VERDICT unknown (proposed partial/B rejected: no conjunct is met by Xenial). Verifier re-fetched live 2026-09-16. FOUND: https://reports.xenial.com/4745.aa0aa304ff2cccfe.js (200, 95,483 B) en dictionary block UBER_EATS {File Name, Size, Status, Refresh, Report Type, Last Updated, 'Payment Details Report', 'Finance Summary Report', 'Order History Report', 'Order Errors Transaction Report', 'Order Errors Menu Item Report', 'Downtime Report', 'Customer and Delivery Feedback Report', 'Menu Item Feedback Report', 'Orders and Items Report', Regenerate, Download} and 'Only sites with active Uber Eats subscription are shown'; https://reports.xenial.com/1398.2b3b5b6a2c692dcd.js (200, 176,805 B) generateReport()/regenerateReport() POST /uber-eats/{generateReport|regenerateReport} with {date_from, date_to, store_uuids, report_type, workflow_id}, rows with DOWNLOAD / REGENERATE actions by status. WHY IT MEETS NOTHING: these are Uber Eats' own marketplace report types requested per store and date range and handed back as downloadable files. Xenial performs no matching of payouts against POS-recorded 3P sales; any commission/fee itemisation is inside Uber's file and is not evidenced in Xenial's bytes; no missing/unpaid-order identification exists. Passing a marketplace's report through is file retrieval, not reconciliation, and it is Uber-only (tokenised \b(DOOR_?DASH|GRUBHUB)\b = 0 in both chunks, though dm.xenial.com's preferred_delivery_provider enum lists none/ubereats/doordash/grubhub). CONTROLS: tokenised \b(reconcil\w*|payout\w*|commission\w*|deposit\w*)\b in 1398 = 0; in 4745 = 36, all POS till fields ('Deposit Variance: Actual/Expected/Variance', Paid In/Out) - POISON: 'deposit' there is the cash-drawer deposit, not a marketplace payout; across the analyst's 776-file corpus \bcommission hits only stadium-hawker 'Commission Rates' (dm/xprt/xvi) and reconcil only a GL-account tooltip 'displayed in reports for financial reconciliation'. Not no: the reporting UI is not an exhaustive census of Xenial/Genius reporting (Genius Back Office xbo.xenial.com and analytics are separate surfaces). Resolved by: a report that joins marketplace payouts to POS 3P orders. Supersedes nothing in the prior rationale; adds the Uber Eats report pass-through as a known non-qualifying feature. || 323rd: NEW SURFACE, cell still unknown, corroborating the standing verdict. The Reporting UI ships a closed 65-member enum ReportType (report-identificators.ts, readable in that app's source map): no reconciliation, payout, commission or marketplace-settlement report appears in it, and reconcil is 0 across the 175 first-party sources. The only third-party surface in the app remains the Uber Eats pass-through report downloader already recorded. SURFACE (new this pass): the anonymous Simple Service Registry https://ssr.xenial.com/?env=prod (200, 14,651 B, 112 prod service rows) names every Xenial production host; four of them serve PUBLIC SOURCE MAPS anonymously (retrieved 2026-09-17, each verified against a nonsense sibling path): xvi.xenial.com main-es2021.29e36e9d5f3e7723e50e.js.map (30.3 MB, 1,959 sources / 835 first-party), reports.xenial.com main.4672b942d3cda827.js.map (19.1 MB, 631 sources / 175 first-party), analytics.xenial.com main.fa2f8777.js.map (9.4 MB, 395 first-party) plus 213 of its 220 lazy chunk maps enumerated from the chunk table inside main.js (1,474 further first-party source entries), and xea.xenial.com main.5a404f0740583be4.js.map (9.8 MB, 261 first-party). A source map carries sourcesContent, i.e. the original TypeScript. Hosts whose .map answers were SPA-shell soft 200s and were discarded: xbo, team, record-and-play, mbs-xspot, braves-xspot, demo-xspot, tablesideordering-uat (that last one is an Amazon CloudFront placeholder). crt.sh for xenial.com returned 393 names, almost all qa-/dev-/devlab- copies that merge policy bars; the production extras (ordering.xenial.com, giftcardreorder, analytics-crm-demo, demo-global-bites) do not answer and orders.omni-eu 403s. Retrieved 2026-09-17. || 325th: NEW SURFACE, cell still unknown. Over the 100%-fetched 293-topic Genius developer portal 'reconcil|commission' returns 19 hits in 9 topics and none is a marketplace payout match: they are the Chef API's 'This data is reconcilable with the configuration data returned in the Report.getStaticData method', a GL-account tooltip, and stadium-hawker 'Commission Rates'. POISON to record: 'de-duplication' in this corpus is the Pipeline republish flag '"ignore_deduplication": true', not identity or payout matching. The published partner enumeration also puts the reconciliation-capable names in a different category from delivery - 'Back Office and Reporting: Altametrics, Bikky, CLEARVIEW, Crunchtime, Deputy, Fourth / Macromatix / HotSchedules, Harri, Restaurant365, Shogo' - i.e. any matching happens in a third-party back-office product, not in Genius. Retrieved 2026-09-17. || 327th: 327th, POISON MEASURED ON THE RECONCILIATION VOCABULARY ITSELF. 327th NEW COMBINED FIRST-PARTY FRONT-END CORPUS (nobody had run this cell against it): the 229 complete public source maps of FOUR Xenial SPAs already on disk (analytics.xenial.com, reports.xenial.com, xea.xenial.com, xvi.xenial.com; 118.9 MB) UNIONED with the 724 readable files of the closed 1,294-file script-loader fixpoint census of dm.xenial.com (Genius DataManagement, 49.5 MB) = 1,524 files / 168.3 MB of the vendor's own shipped code and i18n dictionaries. Denominator stated; these are BACK-OFFICE/analytics apps and by merge policy do not bound the store-level POS. 'reconcil*' scores 62 hits and NOT ONE is a payout match: 8415.map is React's own reconciler ('ReactReconcileTransaction', 'React's rendering and reconciliation algorithm'), 9223.map is exceljs's XML model reconcile()/reconcilePicture(), and main.fa2f8777.js.map is a React useLayoutEffect comment. A future pass that reports a non-zero 'reconcile' count over a Xenial front-end corpus is reporting library code. Tightened: 'payout' = 0, 'commission' and 'split settlement' produce nothing in the reports SPA that renders the UBER_EATS file dictionary already in the record. Retrieved 2026-09-18. || 331st: 331st: NEW TEXT, not settling. 331st CORPUS, run against this cell for the first time: the three Paligo publications' own search manifests on www.xenial.com (product-documentation/en/js/fuzzydata.min.js 3,988 sections / 790 pages; release-notes/en/js/fuzzydata.min.js 3,956 sections / 192 pages; developer-resources/en/js/fuzzydata.min.js 3,337 sections / 293 pages; all fetched 200 on 2026-09-18 with version=20260915 builds; 1,275 pages, 14.2 M chars). Controls are tokenised, word-boundary, case-insensitive. Two current statements nobody had set against this cell: (1) 2026 May Feature Highlights, 'Reporting | UberEats Reports - PRMA-6507 Added the ability to export UberEats Reports using data from UberEats platform to analyse and reconcile information', with permission 'Uber Eats Report (Reporting.Uber.Eats)'; release note XOO-12078 'generate and download Uber Eats reports as ZIP archive'. The vendor's own word is 'reconcile', but the mechanism is still the Uber-file pass-through already rejected as file retrieval: no join of payouts to POS 3P orders is described. (2) 2026 February/March highlights: 'Add columns Discount Funding-Uber Eats and Discount Funding-Merchant to Discount Summary and Discount Detail reports' (from discount_funding_splits). That is promo-funding attribution, one fee-adjacent line, not commission/marketing-fee/payout matching. Controls: 'reconcil*' 97 hits / 33 pages, none a marketplace payout match; 'commission*' 131 hits / 10 pages, all stadium hawker Commission Rates (venue-inventory) plus Omni discount specs; 'payout' 3 hits, all register cash payouts. Retrieved 2026-09-18. adversarially verified

Vendor exposes integration health to the operator — failed/rejected order injections, connection status per channel, and alerts on failure — rather than failing silently. differentiator

delivery-injection-error-visibility

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

Guests receive a branded order status / driver tracking page or SMS link on the restaurant's own domain for first-party delivery orders, driven by real order and driver state.

delivery-tracking-page

CLAIM: guests receive a branded order-status / driver-tracking page or SMS link for first-party delivery orders, driven by real order and driver state. VERDICT: partial/B. EVIDENCE (vendor release notes, Genius Foodservice Management POS = Nextep, live page 200 / 245,190 B; nonsense sibling /zzz-nonsense.html = 404): 2024-11-14 | Nextep: 'Add Order Status Tracking - Online Desktop Ordering: Customers can now configure custom statuses and notifications so that their guests can track their order status and allow order status notifications via SMS or email.' 2024-08-01 | Nextep: 'Mobile App (OSM): Order Tracking: Customers can now configure custom order statuses & text notifications so guests can track their order status on the app or receive SMS/push notifications.' The same product runs in-house delivery (product-documentation foodservice-management-pos/employees.html: 'Delivery Dashboard Manager (view all drivers)', 'Driver Settlement - Delivery driver cash settlement', Position flag 'Delivery Driver?'). SO the order-status half is met: guest-facing status tracking in the operator's first-party web and app ordering, with SMS notification, driven by operator-configured order statuses. SHORTFALL (named): no driver state (no en-route/driver-location event anywhere - 'driver' in the three manifests is OPOS device drivers, the FSM driver permissions, and the Omni error '131 Order Is Assigned a Driver'); the notes do not say the page is on the restaurant's own domain or that it covers delivery orders specifically; and it is the Foodservice Management (Nextep) line, not Enterprise POS, whose notification catalogue (developer portal) stays kitchen-only. 331st CORPUS, run against this cell for the first time: the three Paligo publications' own search manifests on www.xenial.com (product-documentation/en/js/fuzzydata.min.js 3,988 sections / 790 pages; release-notes/en/js/fuzzydata.min.js 3,956 sections / 192 pages; developer-resources/en/js/fuzzydata.min.js 3,337 sections / 293 pages; all fetched 200 on 2026-09-18 with version=20260915 builds; 1,275 pages, 14.2 M chars). Controls are tokenised, word-boundary, case-insensitive. Retrieved 2026-09-18. https://www.xenial.com/release-notes/en/genius-point-of-sale/foodservice-management-pos/previous-releases.html · retrieved 2026-09-18 adversarially verified

Quoted delivery promise times adjust dynamically from current kitchen load, driver availability, and zone drive time, rather than a fixed per-store constant. differentiator

delivery-promise-time

Upheld. Both timing mechanisms visible in this corpus are static constants, not load-aware quotes: Nextep > System > Hours of Operation (captured 2023-01-30) exposes, for Advanced Orders, only 'Prep Time - Number of minutes required to prepare future orders' and 'Number of Days - Number of days notice required for future orders', and the Nextep item record carries a per-item 'Prep Time - Amount of time the kitchen staff needs to prepare the item'. 'promise time', 'quote time' and 'wait time' occur zero times in the corpus. Held unknown rather than no because neither page is a delivery promise-time editor, and dynamic quoting could live in the online-ordering front end rather than in captured configuration. Resolved by: an online-ordering or Genius topic showing a quoted time derived from current kitchen load or driver availability. || 325th: NEW SURFACE, cell still unknown, with one lead named for the next pass. Over the 100%-fetched 293-topic developer portal 'promise time|quote(d) time|estimated (ready|delivery) time|ETA' = 0, so no load-aware quote is documented anywhere in Xenial's integrator documentation. The lead: the published partner enumeration lists 'Operational: Curbit, EasyPost, Epson, Instant Financial, Perfect Company, PopID' - Curbit is an order-timing/throttling vendor and is named as a Genius integration partner, but it has no topic of its own in the portal, so what it drives (prep-time prediction, promise quoting, or curbside arrival) is unstated. Retrieved 2026-09-17. || 326th: NEW SURFACE (326th), and it does NOT bound the restaurant POS - stated plainly. The 61 `*-xspot.xenial.com` hosts in the crt.sh listing are live production instances of Xenial's guest-facing SuiteSpot ordering app (Angular; braves-xspot.xenial.com serves <title>SuiteSpot</title> with body data-company-code="BRAVES" and loads FreedomPay's hpc_min.js). I took it to a CENSUS: the webpack runtime (runtime.bce2fd5f94dece6a.js) carries a complete chunk-hash table of 76 entries; all 75 lazy chunks plus main.ab83504f760b9d4a.js fetched at 200, 7.61 MB of production JS, 0 misses, no unmapped loader entries. SOFT-200 CONTROL PASSED: /main.ZZZZZZZZ.js returns the 1,119-byte index.html shell and every fetched chunk is larger and begins with webpack chunk syntax, so none of the 75 is a shell. This is the VENUES/stadium suite-catering guest app, not the restaurant POS or the Genius back office, so under the standing merge rule it bounds only itself. WHAT IT HELD for this cell: `quote time` = 0, `wait time` = 0, `lead time` = 0, `prep time` = 0, `ETA` = 0 and `estimated` = 0 over the whole 7.61 MB census; `promise` = 128 and every hit is the JavaScript Promise type - the single worst control in this vocabulary, and it is named here so no later pass mistakes it for a promise-time feature. `scheduled` = 1. The guest app therefore quotes nothing dynamic, but it is the stadium suite-catering front end, so it cannot settle whether the restaurant online-ordering front end computes a load-aware promise time. Retrieved 2026-09-18. || 327th: 327th, A HOMONYM TRAP FOR THIS CELL, now measured and disarmed. 327th NEW COMBINED FIRST-PARTY FRONT-END CORPUS (nobody had run this cell against it): the 229 complete public source maps of FOUR Xenial SPAs already on disk (analytics.xenial.com, reports.xenial.com, xea.xenial.com, xvi.xenial.com; 118.9 MB) UNIONED with the 724 readable files of the closed 1,294-file script-loader fixpoint census of dm.xenial.com (Genius DataManagement, 49.5 MB) = 1,524 files / 168.3 MB of the vendor's own shipped code and i18n dictionaries. Denominator stated; these are BACK-OFFICE/analytics apps and by merge policy do not bound the store-level POS. 'promise time' = 0 across all 1,524 files, but 'quoted time' scores 9 in dm.xenial.com's main.js and every one is the WAITLIST, not delivery: the hits sit in generateQuotedTimeOptions / party-details form, next to PartySize, PartySeated, ReseatParty, PreSelectedTables and alert methods ('Coaster Pager', 'Email', 'Guest Waiting'), and the enumeration itself is a closed seating-wait table - quotedTimes = [{'2-7 minutes',2},{'5-10 minutes',5},{'10-15 minutes',10},{'15-20 minutes',15},{'20-25 minutes',20}...]. A future pass grepping for a quoted/promised time in a Xenial corpus will hit this and must not read it as an order promise. No prep-time, lead-time or quote-to-guest construct exists in the corpus. Retrieved 2026-09-18. || 331st: 331st: NEW CORPUS, same answer. 331st CORPUS, run against this cell for the first time: the three Paligo publications' own search manifests on www.xenial.com (product-documentation/en/js/fuzzydata.min.js 3,988 sections / 790 pages; release-notes/en/js/fuzzydata.min.js 3,956 sections / 192 pages; developer-resources/en/js/fuzzydata.min.js 3,337 sections / 293 pages; all fetched 200 on 2026-09-18 with version=20260915 builds; 1,275 pages, 14.2 M chars). Controls are tokenised, word-boundary, case-insensitive. Every timing control found is a static constant: Enterprise POS 'Kitchen Lead Time for Future Orders (seconds)' (company/site preferences, printer chit delay), FSM 'Prep Time - Number of minutes required to prepare future orders' and per-item 'Prep Time'. POISON: host-mode.html 'Quoted Time (Estimated) - Estimated time until table is available' is the WAITLIST quote, not a delivery promise; 'Ready Timer' is the order-ready board; 'throttl*' is API gatekeeper metering. 'promise time' 0, 'estimated (delivery|pickup) time' 0, 'ETA' 0. Retrieved 2026-09-18. adversarially verified

Vendor documents explicit offline behavior for delivery: whether cash delivery orders, driver assignment, and driver settlement continue during an internet outage.

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

Vendor ships a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission.

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

The web/app ordering menu is generated from the same POS menu record as in-store — one item edit propagates to all first-party digital channels without a separate digital menu build.

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

Vendor offers a branded native iOS and Android ordering app (published under the restaurant's own brand in the App Store/Play Store), not only a mobile web page or a shared multi-restaurant marketplace app. differentiator

digital-native-app

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

Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels.

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 checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator

digital-upsell-engine

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

Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.

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

Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.

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

Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.

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

Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator

digital-kiosk

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

Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.

digital-group-ordering

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO NO. Xenial does have a feature called Group Order and it is a different mechanism from the claim. The 2026-08-12 Data Management release note 'Enhanced support for large-party group ordering' adds a Group Order Order Option at Terminal Scheme level; the 2026-03-17 note adds a Split Order Into Sessions By Segment toggle in Kitchen Settings; kitchen cell settings display a Group Indicator 'when the order is added as part of a large group order'; and IRIS was changed to flag orders as a Group Order for Genius Kitchen. That is in-store large-party ordering keyed to seats/segments on a terminal. The claim’s mechanism is absent: `shareable link` 0, `spend cap` 0, `per-person cap` 0, `group ordering link` 0, `invite` in an ordering context 0, across all 11,269 sections. No guest-facing link where participants add their own items under a cap exists. https://www.xenial.com/release-notes/en/genius-point-of-sale/enterprise-pos/data-management/release-notes---production-environment/previous-releases.html · retrieved 2026-09-12 adversarially verified

Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator

digital-catering-portal

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

Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator

digital-voice-ai-phone

MERGE DOWNGRADE yes -> partial (325th): the developer portal documents voice-command menu data built for an artificial voice controller to operate the POS, and a closed partner list names five Voice AI partners, which is a real part of the claim. But no single document says AI answers the PHONE channel; the phone half is joined in from separate app strings, and the agent flagged that join itself. CLAIM: AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. VERDICT: yes, grade B - the one conjunct the 2026-09-16 verifier rejected the `yes` on (order injection into the POS) is now documented by Xenial itself, and the partner leg is satisfied by a published enumeration. EVIDENCE (1) NAMED CERTIFIED PARTNERS: the developer portal's 'Genius Integration Partners' page - 'Genius partners with the following integrators for these products' - is a closed, category-by-category list whose last category is verbatim 'Voice AI: Audivi, ConverseNow, Hi Auto, OpenCity, Presto' (the other categories being Back Office and Reporting; Delivery and Online Ordering; Digital Menu Boards; Gift and Loyalty; Kiosk; Operational; Payments). Footer '(c) 2026 Global Payments'. (2) ORDER INJECTION / NO STAFF TRANSCRIPTION: https://www.xenial.com/developer-resources/en/menu-structure.html - 'Voice Commands. The Menu Engine can include voice command data for individual menu items. This information provides the parameters necessary for an artificial voice controller system to operate the point of sale for the menu in question.' The menu is handed to that system by the Menu Engine create-menu request with '"include_voice_commands": true' (PUT https://xme.xenial.com/v1/menu), each item carrying a voice_commands object {name, synonyms, description}; the same three fields (voice_name, voice_synonyms, voice_description) are documented as configured in Data Management in create-a-menu-using-data-management-menu-features.html ('The primary product name for use with voice ordering' / 'The typical pronunciations of the product name or alternate names for the product'). digital-menu-board-order-data-api.html adds that 'the POS sends data every time the order taker or customer presses a key or speaks, if voice controlled'. (3) INBOUND PHONE + OPERATOR FALLBACK is already in the record from the live xprt.xenial.com bundle ('Number to call the store voice ordering platform', 'Number to route the calls to the store operator', subscription row {name: Voice Ordering, product: VoiceOrdering}); what was missing was never the phone leg but the injection leg. SURFACE (new this pass, 100% of the publisher's own manifest): the LIVE Genius developer portal https://www.xenial.com/developer-resources/en/index-en.html publishes a TOC of 293 topic permalinks; all 293 were fetched at HTTP 200 on 2026-09-17 (3.10 MB of nav-stripped topic text). SOFT-200/CATCH-ALL CONTROL PASSED: /developer-resources/en/zzz-nonsense-topic.html returns 404 with a 0-byte body. www.xenial.com still 403s on /robots.txt to every client but serves /sitemap.xml (500 locs) and every topic page to curl with a browser UA. Positive controls in the stripped corpus: 'order' 3,314 hits/159 topics, 'loyalty' 571/26, 'delivery' 216/28, 'webhook' 50/14. Retrieved 2026-09-17. https://www.xenial.com/developer-resources/en/genius-integration-partners.html · retrieved 2026-09-17 adversarially verified

Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.

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

Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.

digital-sms-ordering

Upheld. Nothing in the recovered corpus describes inbound text-to-order or text-a-link ordering landing in the POS. The SMS artefacts the corpus does add are outbound and marketing-side: the archived Xenial Messaging product page (captured 2021-04-21, Customer Engagement Cloud line) offers 'email, text, push notiffcations or alerts within your app' as outbound channels, and the Xenial Cloud documentation's Twilio service is receipts, waitlist and transfer notifications. Outbound guest messaging is not conversational ordering. A 'no' is unavailable on this corpus for the reasons measured above (a floor, and blind to 2024-2026), and the ordering-channel inventory is never published as a closed list. Resolved by: a Genius Online Ordering channel list, or a post-2024 release note naming an SMS ordering channel. || 325th: NEW SURFACE, cell still unknown, and SMS remains outbound-only on the current documentation: over the 100%-fetched 293-topic Genius developer portal 'sms order|text-to-order|order by text' = 0, and every SMS reference is an outbound notification channel the INTEGRATOR builds - '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' - or the SMS receipt link described in sms-data-retention.html ('For SMS receipts, an HTML version of the receipt is stored and accessible through a URL included in the SMS message'). The order origins published in the notification samples are 'mobile' and numeric store codes, with no SMS channel. Retrieved 2026-09-17. || 327th: 327th, NEW CORPUS, same answer. 327th NEW COMBINED FIRST-PARTY FRONT-END CORPUS (nobody had run this cell against it): the 229 complete public source maps of FOUR Xenial SPAs already on disk (analytics.xenial.com, reports.xenial.com, xea.xenial.com, xvi.xenial.com; 118.9 MB) UNIONED with the 724 readable files of the closed 1,294-file script-loader fixpoint census of dm.xenial.com (Genius DataManagement, 49.5 MB) = 1,524 files / 168.3 MB of the vendor's own shipped code and i18n dictionaries. Denominator stated; these are BACK-OFFICE/analytics apps and by merge policy do not bound the store-level POS. Tokenised, case-insensitive, word-boundary controls: '\bsms\b' = 0 and 'twilio' = 0 across all 1,524 files / 168.3 MB. So neither the Genius configuration app nor the analytics/reporting SPAs contain any SMS channel at all - not even the outbound receipt/waitlist Twilio surface the documentation describes, which means this corpus is silent rather than contradictory. It does not bound Xenial Online Ordering (xooapi.xenial.com), which is where a text-to-order channel would live and which remains uncensused. Retrieved 2026-09-18. || 328th: 328th: NEW CORPUS, same answer. Over the Xenial APK web-asset corpus (1,781 files / 9,489,331 chars; see hardware-byod): Twilio 0, 'text to order' 0, and `SMS` scores only 2 - one in the Privacy Notice shipped as assets/www/assets/EULA.txt and one in xbo's main bundle - with no inbound SMS channel and no order origin of 'sms' anywhere in the three shipped Android apps. Retrieved 2026-09-18. || 331st: 331st: NEW CORPUS, same answer, and a POISON named. 331st CORPUS, run against this cell for the first time: the three Paligo publications' own search manifests on www.xenial.com (product-documentation/en/js/fuzzydata.min.js 3,988 sections / 790 pages; release-notes/en/js/fuzzydata.min.js 3,956 sections / 192 pages; developer-resources/en/js/fuzzydata.min.js 3,337 sections / 293 pages; all fetched 200 on 2026-09-18 with version=20260915 builds; 1,275 pages, 14.2 M chars). Controls are tokenised, word-boundary, case-insensitive. 'text-to-order|order by text/SMS|chatbot order' 0. 'conversational ordering' occurs in enterprise-pos.html ('Genius Enterprise POS features real-time data sync, conversational ordering, offline capabilities') and IRIS/FSM pages - it means the CASHIER's entry flow follows the sequence a guest speaks ('designed to follow how a guest typically requests an order, also known as conversational ordering'), NOT chat/SMS ordering; do not read it as this claim. Every SMS hit is outbound: FSM order-status notifications 'via SMS or email' (2024-11-14 Nextep release), alert levels 'Email or SMS text', MFA codes. Retrieved 2026-09-18. || 334th: 334th NEW SURFACE: 218 Global Payments press releases (investors.globalpayments.com/news-events/press-releases, ?page=1..22 until empty, every detail page fetched 200 on 2026-09-18, 2.15 M chars of release text; 23 of them name Genius or Xenial, incl. 122 Xenial launch 2017, 473 Genius platform 2025-05-16, 486 Genius for Enterprise 2025-09-10, 490 higher education, 495 Uber Eats partnership 2025-11-18, 509 AI-first handheld 2026-05-12, 515 Genius World 2026-08-24). 'text-to-order' 0, 'SMS' 0. POISON NAMED: release 486 (Genius for Enterprise, 2025-09-10) lists 'conversational ordering' as POS functionality, and 509 describes it as 'AI-powered voice ordering technology, which will allow servers to have real conversations with customers while the POS quietly builds the ticket' - staff-side VOICE capture, not guest SMS/chat ordering. Still unknown. Retrieved 2026-09-18. adversarially verified

Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator

digital-google-order

OWNER RULING 2026-09-18 (Q4): xenial digital-google-order -> no. Bound: the only Google Business Profile object in 168.3 MB of Xenial shipped code is one program-tile title, with Order with Google / ordering link / actionLink / menuLink all 0; the 331st added the 1,275-page xenial.com documentation search-index census (product-documentation 790, release-notes 192, developer-resources 293, builds 2026-09-15) with Google Business, Maps and Order with Google all 0. Retrieved 2026-09-18. PRIOR EVIDENCE: Upheld, deliberately. Zero hits for 'Order with Google', 'Google Business Profile' and 'Preferred by Business' across all 1,197 recovered files; every Google occurrence is Google Play as an install route, Google Pay / Google Wallet as a TENDER on the payments and touchless-payments pages ('Pay using Apple Pay, Google Wallet, gift card, or by entering card number'), Chrome as the recommended browser, or Google credentials as an OAuth sign-in option. Order with Google is a third-party listing programme normally provisioned by the online-ordering partner (Olo and Checkmate are both listed Xenial partners), so a POS vendor's silence is not evidence in either direction; a 'no' here needs Xenial to state it does not support it. This is the exact defect that killed two apple-business-connect 'no' verdicts on audit last session. Resolved by: a Xenial or Genius online-ordering page enumerating which listing surfaces its ordering links are published to, or a Google-side merchant listing naming Xenial as an order-with-Google provider. || 325th: NEW SURFACE, cell still unknown (deliberately). Xenial now publishes a closed integrator enumeration by product category (genius-integration-partners.html, 8 categories) and no listing/search surface appears in it: the ordering-adjacent category is 'Delivery and Online Ordering: Checkmate, Deliverect, DoorDash, Grubhub, Olo, Paytronix, SkipTheDishes, Uber Eats', and over the whole 293-topic portal 'Order with Google|Google Business Profile' = 0, every Google reference being Google Pay as a tender. Still not a `no` for the reason the standing note gives - Order with Google is provisioned by the ordering partner, and Olo and Checkmate are both listed here - so a POS vendor's partner list is not the enumeration that settles it. Retrieved 2026-09-17. || 327th: 327th, THE FIRST GOOGLE-LISTING SURFACE XENIAL ACTUALLY SHIPS, and it still does not carry the claim. 327th NEW COMBINED FIRST-PARTY FRONT-END CORPUS (nobody had run this cell against it): the 229 complete public source maps of FOUR Xenial SPAs already on disk (analytics.xenial.com, reports.xenial.com, xea.xenial.com, xvi.xenial.com; 118.9 MB) UNIONED with the 724 readable files of the closed 1,294-file script-loader fixpoint census of dm.xenial.com (Genius DataManagement, 49.5 MB) = 1,524 files / 168.3 MB of the vendor's own shipped code and i18n dictionaries. Denominator stated; these are BACK-OFFICE/analytics apps and by merge policy do not bound the store-level POS. analytics.xenial.com's complete main.fa2f8777.js.map (a real map: begins {"version":3, with sourcesContent) holds the app's English dictionary, and inside a block of PROGRAM TILES it publishes: "adsProgramTitle: 'Google Ads'", "gmbProgramTitle: 'Google Business Profile'", "workspaceProgramTitle: 'Workspace Admin'", "googleDriveTitle: 'Drive'", "googleGmailTitle: 'Gmail'", alongside "advancedAnalyticsTitle: 'Payment Analytics Plus'". Xenial therefore does surface a Google Business Profile program to its operators - the exact object the claim's ordering link must be provisioned to - and that is a materially better place to look than the POS docs. Yet over the whole map set 'Order with Google' = 0, 'Preferred by' = 0, 'food ordering' = 0, 'ordering link' = 0, 'orderOnline' = 0, 'actionLink' = 0, 'menuLink' = 0 and 'Reserve with Google' = 0; the only 'Google Business Profile' occurrence in 168.3 MB is that one menu title. Held unknown, not no: a single i18n tile proves the module is named, not what the module does, and the GMB program screen's own chunk was not separately identified. Resolved by: the analytics GMB program's own route chunk, or a Google-side listing naming Xenial as an order-with-Google provider. Retrieved 2026-09-18. https://www.xenial.com/product-documentation/en/genius-point-of-sale.html · retrieved 2026-09-18 adversarially verified

Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.

digital-apple-business-connect

Upheld, deliberately. 'Apple Business Connect', 'Apple Maps', 'place card' and 'Order Food' return zero hits across all 1,197 recovered files; every Apple occurrence is Apple Pay as a tender, the App Store as an install route, or Apple credentials as an OAuth sign-in option. Apple Business Connect place-card provisioning is a third-party listing programme delivered by the ordering partner, not the POS, and the corpus is both a measured floor and blind to 2024-2026 (Apple Business Connect's Order Food custom action postdates most of these captures). Absence here is absence of evidence. Resolved by: Xenial/Genius documentation enumerating listing-surface publication, or an Apple-side partner directory entry. || 325th: NEW SURFACE, cell still unknown (deliberately). Over the 100%-fetched 293-topic Genius developer portal 'Apple Business Connect|Apple Maps' = 0, and the newly published closed integrator enumeration (genius-integration-partners.html, 8 product categories) contains no listing or place-card partner; every Apple reference in the portal is Apple Pay as a tender or the App Store as an install route. Absence here remains absence of evidence, per the audit that killed two apple-business-connect `no` verdicts. Retrieved 2026-09-17. || 327th: 327th, ASYMMETRY WORTH RECORDING. 327th NEW COMBINED FIRST-PARTY FRONT-END CORPUS (nobody had run this cell against it): the 229 complete public source maps of FOUR Xenial SPAs already on disk (analytics.xenial.com, reports.xenial.com, xea.xenial.com, xvi.xenial.com; 118.9 MB) UNIONED with the 724 readable files of the closed 1,294-file script-loader fixpoint census of dm.xenial.com (Genius DataManagement, 49.5 MB) = 1,524 files / 168.3 MB of the vendor's own shipped code and i18n dictionaries. Denominator stated; these are BACK-OFFICE/analytics apps and by merge policy do not bound the store-level POS. Xenial ships a named 'Google Business Profile' program tile in analytics.xenial.com's dictionary (see digital-google-order), but there is no Apple counterpart anywhere: 'Apple Business Connect' = 0, 'Apple Maps' = 0, 'place card' = 0, 'Order Food' = 0 across all 1,524 files / 168.3 MB. Every Apple string in the corpus is Apple Pay as a tender or the App Store as an install route, reproducing the documentation corpus exactly. Still absence of evidence per the audit that killed two `no`s on this cell; recorded so a later pass does not re-run it. Retrieved 2026-09-18. || 328th: 328th: NEW CORPUS, reproduces the asymmetry, no move. Over the Xenial APK web-asset corpus (1,781 files / 9,489,331 chars; Genius Shell assets/www, xbo assets/public, mobilemanager assets/public - see hardware-byod for the bound): 'Apple Business Connect' 0, 'Apple Maps' 0, 'place card' 0, AND 'Google Business Profile' 0 as well - so the one Google-listings tile found in analytics.xenial.com's dictionary in the 327th does not appear in any of the three shipped Android apps either. Absence of evidence, per the audit that killed two `no`s on this cell. Retrieved 2026-09-18. || 331st: 331st: NEW CORPUS, same answer. 331st CORPUS, run against this cell for the first time: the three Paligo publications' own search manifests on www.xenial.com (product-documentation/en/js/fuzzydata.min.js 3,988 sections / 790 pages; release-notes/en/js/fuzzydata.min.js 3,956 sections / 192 pages; developer-resources/en/js/fuzzydata.min.js 3,337 sections / 293 pages; all fetched 200 on 2026-09-18 with version=20260915 builds; 1,275 pages, 14.2 M chars). Controls are tokenised, word-boundary, case-insensitive. 'Apple Business|Apple Maps|place card' 0, and the Google counterpart 'Order with Google|Google Business|Google Maps|Reserve with Google|GMB' is also 0 across all 1,275 pages. Retrieved 2026-09-18. adversarially verified

Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.

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

Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.

digital-subscriptions

Upheld. Searched the recovered corpus for a recurring guest-side entitlement: 'subscription' remains operator-side throughout (a company subscribing to Suite Catering, Online Ordering, a Menu Engine menu subscription, Portal service subscriptions), and 'membership program', 'recurring billing', 'delivery fee waiver' and 'paid tier' return zero hits. The Customer Engagement Cloud marketing tree (captured 2021-04-21) sells Gift and Stored Value as the recurring-value construct - 'Stored Value lets customers load value, spend and repeat' - which is a prepaid wallet, not a recurring charge for a per-period entitlement. Not a 'no': the corpus is a floor, has no 2024-2026 coverage, and a paid loyalty tier would be configured in the loyalty partner's product. Resolved by: a Genius Gift and Loyalty or online-ordering doc describing recurring guest billing. || 325th: NEW SURFACE, cell still unknown: over the 100%-fetched 293-topic Genius developer portal 'recurring (billing|charge|payment)|membership program|subscription plan' = 0. 'Subscription' in this corpus is operator-side throughout - a company subscribing to a Genius service (Loyalty, Online Ordering, Voice Ordering) in Portal Company Settings, or an integrator subscribing to the Notification service's SQS/SNS topic - never a guest paying per period. Retrieved 2026-09-17. || 326th: NEW SURFACE (326th), and it does NOT bound the restaurant POS - stated plainly. The 61 `*-xspot.xenial.com` hosts in the crt.sh listing are live production instances of Xenial's guest-facing SuiteSpot ordering app (Angular; braves-xspot.xenial.com serves <title>SuiteSpot</title> with body data-company-code="BRAVES" and loads FreedomPay's hpc_min.js). I took it to a CENSUS: the webpack runtime (runtime.bce2fd5f94dece6a.js) carries a complete chunk-hash table of 76 entries; all 75 lazy chunks plus main.ab83504f760b9d4a.js fetched at 200, 7.61 MB of production JS, 0 misses, no unmapped loader entries. SOFT-200 CONTROL PASSED: /main.ZZZZZZZZ.js returns the 1,119-byte index.html shell and every fetched chunk is larger and begins with webpack chunk syntax, so none of the 75 is a shell. This is the VENUES/stadium suite-catering guest app, not the restaurant POS or the Genius back office, so under the standing merge rule it bounds only itself. WHAT IT HELD for this cell: tokenised, case-insensitive, word-boundary over the whole 7.61 MB census, `membership` = 0, `recurring` = 0, `loyalty` = 0, `reward` = 0. `subscription` = 15 and every one is the RxJS Subscription class or a .subscribe() teardown, i.e. the control's own poison - the framework word, not a guest entitlement. So Xenial's live guest-ordering front end carries no recurring-billing or paid-tier construct. This cannot convert the cell: the app is stadium suite catering, where a per-period entitlement would not be expected, and it is silent about the restaurant products the claim is scored against. Retrieved 2026-09-18. || 331st: 331st: NEW CORPUS, same answer. 331st CORPUS, run against this cell for the first time: the three Paligo publications' own search manifests on www.xenial.com (product-documentation/en/js/fuzzydata.min.js 3,988 sections / 790 pages; release-notes/en/js/fuzzydata.min.js 3,956 sections / 192 pages; developer-resources/en/js/fuzzydata.min.js 3,337 sections / 293 pages; all fetched 200 on 2026-09-18 with version=20260915 builds; 1,275 pages, 14.2 M chars). Controls are tokenised, word-boundary, case-insensitive. 'recurring (billing|charge|payment)' 0, 'paid (tier|membership)' 0, 'subscription (plan|program|billing)' 0; 'membership' 29 hits / 10 pages, all loyalty-lookup prompts ('ask customer about their loyalty membership') or Back Office security-group membership (poison). Retrieved 2026-09-18. adversarially verified

Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.

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

Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator

digital-guest-data-ownership

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO PARTIAL, and it is half-met in a way the two surfaces now show precisely. Ownership is published: the Consolidated System Terms section 3.1 ends 'Ownership and title to your data shall remain with you' (already recorded in api_posture.data_export_on_exit). SHORTFALL: there is no bulk guest-record export. The Back Office Export utility publishes its module list - '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 - and there is no customer or guest module among the twelve; the word 'include' makes that a floor rather than a ceiling, but `export guest` 0, `customer export` 0 and `export customer` 0 across all 11,269 sections leave nothing else to find. Consented marketing status is captured per guest (Sms Opt In, Email Opt in registration fields) and is not exportable by any documented route, and no fee or approval terms are published either way. https://www.xenial.com/product-documentation/en/genius-back-office/export-data.html · retrieved 2026-09-12 adversarially verified

Digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.

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 channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator

digital-surcharge-transparency

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

Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.

guest-loyalty-unified-profile

CLAIM: a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering and kiosk under one identity (phone or email match), with documented dedup/merge behaviour. VERDICT: no. Xenial's own loyalty documentation states that the guest record belongs to a THIRD-PARTY PROVIDER, and enumerates every loyalty function it exposes - none is a merge, dedup or identity-resolution function. Verbatim: 'Customer Loyalty Service, accessed through the Gift and Loyalty services API, allows users to track customer purchases and accrue and apply rewards to transactions at the point of sale using an existing loyalty service provider. Gift and Loyalty API supports the following loyalty service providers: SVS / Paytronix / Punchh / BK Loyalty / Givex / Fortress / Heartland/Gift and Loyalty.' The closed function lists are 'Identify Customers, Simulate Accrual, Redeem Reward, Submit Order, Void Order, Add Customer, Update Customer, Redeem Balance, Reverse Balance' (Provider Integrations) and the same minus Simulate Accrual (Client Integrations); 'After the service associates a customer with the order, our system manages accruing awards and applying awards to customer accounts as part of the existing transaction flow on the point of sale (POS) system.' Setup is per company and per site with the PROVIDER's credentials and base path (customer-loyalty-service---getting-started.html: 'Select the correct loyalty provider from the drop down menu. Enter the details of the loyalty account'), so identity is resolved inside Paytronix/Punchh/SVS, not in Xenial, and no match key or merge rule is published. BOUND/CONTROLS over the 100%-fetched 293-topic portal: 'de-?dup|merge (customer|guest|profile)|golden record|identity resolution' = 20 hits in ONE topic and all 20 are POISON - the Pipeline republish flag '"ignore_deduplication": true' in operation-definitions-987302.html (Data Stream order re-publication), not guest identity. Positive control 'loyalty' = 571 hits in 26 topics, so the vocabulary is present and the absence is specific. This is the venue the standing note asked for ('a Customer Engagement Cloud or Genius admin guide stating the match key and merge behaviour') and it documents the opposite. SURFACE (new this pass, 100% of the publisher's own manifest): the LIVE Genius developer portal https://www.xenial.com/developer-resources/en/index-en.html publishes a TOC of 293 topic permalinks; all 293 were fetched at HTTP 200 on 2026-09-17 (3.10 MB of nav-stripped topic text). SOFT-200/CATCH-ALL CONTROL PASSED: /developer-resources/en/zzz-nonsense-topic.html returns 404 with a 0-byte body. www.xenial.com still 403s on /robots.txt to every client but serves /sitemap.xml (500 locs) and every topic page to curl with a browser UA. Positive controls in the stripped corpus: 'order' 3,314 hits/159 topics, 'loyalty' 571/26, 'delivery' 216/28, 'webhook' 50/14. Retrieved 2026-09-17. https://www.xenial.com/developer-resources/en/customer-loyalty-service.html · retrieved 2026-09-17 adversarially verified

Orders arriving from third-party marketplaces (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. differentiator

guest-loyalty-thirdparty-identity-attach

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

Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.

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

Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator

guest-loyalty-tiers

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO NO. The decisive artefact is Xenial’s own Customer Loyalty Service reference, which was unreadable to the prior pass. It describes the product as tracking purchases and accruing rewards 'using an existing loyalty service provider', names the supported providers (SVS, Paytronix, Punchh, BK Loyalty, Givex, Fortress, Heartland/Gift and Loyalty), and closes the operation set: 'The Gift and Loyalty API supports the following loyalty functions for Provider Integrations' - Identify Customers, Simulate Accrual, Redeem Reward, Submit Order, Void Order, Add Customer, Update Customer, Redeem Balance, Reverse Balance. Nine functions, none of them a tier, and 'the following' is a closed list rather than an 'includes'. Controls: `loyalty tier` 0, `demotion` 0, `rolling window` 0 across 11,269 sections; the 10 documents matching `tier` are all Tier Pricing (menu price tiers) or a DMB permission, a false friend worth recording. Where a status tier exists it is the third-party provider’s - in Provider Integrations 'all reward logic is owned by a loyalty provider' - not a Xenial capability. https://www.xenial.com/developer-resources/en/customer-loyalty-service.html · retrieved 2026-09-12 adversarially verified

Documents explicitly what loyalty lookup, accrual, and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). differentiator

guest-loyalty-offline-behavior

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

Offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. differentiator

guest-loyalty-offer-stacking-rules

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

Offers can be issued to a dynamically defined audience (rules over recency, frequency, spend, or items purchased) rather than only broadcast to the whole list. differentiator

guest-loyalty-targeted-offers

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO PARTIAL. The prior pass declined to move this on a 2021 marketing page at grade D; this is different evidence at grade B. The 2025 June Feature Highlight states the loyalty service can 'Personalize upsell suggestions, like add-ons, based on a user’s past behavior or preferences at checkout' and can send notifications 'based on user behavior or events' - so issuance is conditioned on the individual guest’s history rather than broadcast to the whole list. SHORTFALL: there is no audience-definition surface. `audience` matches 1 document (a Speed of Service note), `target list` 0, `segment builder` 0, and no rule editor over recency, frequency, spend or items purchased is documented; in Provider Integrations 'all reward logic is owned by a loyalty provider', so which guests qualify is generally the third party’s decision, not the operator’s in Xenial. https://www.xenial.com/release-notes/en/feature-highlights/previous-feature-highlights/2025-june---feature-highlights.html · retrieved 2026-09-12 adversarially verified

Automatically computes recency/frequency/monetary or equivalent lifecycle segments (new, regular, at-risk, lapsed, VIP) without the operator building the queries. differentiator

guest-loyalty-rfm-segmentation

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO NO. `RFM` 0, `cohort` 0, `lifetime spend` 0, `visit frequency` 0, `returning guest` 0, `at-risk` 0 across all 11,269 sections. The `segment` matches (138 docs) are drive-thru lane segments and kitchen seat/tray segments, a false friend. The closed nine-function list in the Customer Loyalty Service reference (Identify Customers, Simulate Accrual, Redeem Reward, Submit Order, Void Order, Add Customer, Update Customer, Redeem Balance, Reverse Balance) contains no segmentation or scoring operation, and the guest-analytics feature Xenial actually shipped - 2025 June Baseline Loyalty Metrics - is aggregate, not per-guest: 'The Loyalty section displays the performance metrics between loyalty and non-loyalty customers'. Nothing computes lifecycle segments. https://www.xenial.com/developer-resources/en/customer-loyalty-service.html · retrieved 2026-09-12 adversarially verified

Ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns rather than one-off manual sends.

guest-loyalty-lifecycle-automation

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO PARTIAL on evidence dated after everything the prior pass could reach. The 2025 June Feature Highlight, under support added to the loyalty service, states 'System can now send push or SMS notifications based on user behavior or events, such as reminders for discounts, birthday offers, or featured restaurant promotions' - event-triggered messaging with birthday named, not a manual blast - and it names the endpoints added to carry it (addCustomer, updateCustomer, reverseBalance). SHORTFALL: only the birthday trigger of the three the claim names is evidenced. `win-back` 0, `lapsed` 0, `first visit` 0, `re-engagement` 0 across all 11,269 sections, and no campaign-configuration surface is documented anywhere - `campaign` matches 12 documents and the substantive ones are Campaign Coupon permissions in the Portal, not lifecycle automations. There is also no documented always-on/off control for these sends. https://www.xenial.com/release-notes/en/feature-highlights/previous-feature-highlights/2025-june---feature-highlights.html · retrieved 2026-09-12 adversarially verified

Sends both email and SMS campaigns natively from the platform, not solely by handing the list to a third-party ESP. differentiator

guest-loyalty-native-email-sms

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

Captures per-channel marketing consent with timestamp and source of consent, and honors revocation received by any reasonable means (not just the STOP keyword) across all channels.

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

Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.

guest-loyalty-10dlc-registration

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO NO. This claim is satisfied by documentation, so a zero over the publisher’s complete published corpus settles it. `10DLC` 0, `A2P` 0, `brand registration` 0 and `campaign registration` 0 across all 11,269 sections; `short code` matches 5 documents and not one is an SMS originator - a Nextep kiosk loyalty sign-in code 'provided by third-party loyalty systems', an Omni-Channel loyalty ETL, and the delivery_short_code field in the DoorDash and Uber Eats order formats. The platform does send SMS on the operator’s behalf - the 2025 June Feature Highlight states 'System can now send push or SMS notifications based on user behavior or events, such as reminders for discounts, birthday offers, or featured restaurant promotions' - so the obligation is live and is nowhere addressed. Nothing handles or documents A2P 10DLC brand or campaign registration. https://www.xenial.com/release-notes/en/feature-highlights/previous-feature-highlights/2025-june---feature-highlights.html · retrieved 2026-09-12 adversarially verified

Reports redemption and incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. differentiator

guest-loyalty-campaign-attribution

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

Provides self-serve export of the full guest list and transaction history, including contact PII, via CSV or API, without a vendor fee or support ticket. differentiator

guest-loyalty-data-export-portability

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

Exposes a documented outbound guest and order event API or webhook stream that a CDP or marketing platform can subscribe to (e.g. Olo, Punchh, Bridg, Klaviyo). differentiator

guest-loyalty-cdp-event-api

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

Triggers post-transaction feedback requests and routes responses by score, sending low scores to private service recovery and high scores toward public review sites. differentiator

guest-loyalty-review-capture-routing

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

Includes a native referral mechanic with per-guest codes or links, attribution of the referred guest's first order, and two-sided rewards.

guest-loyalty-referral-program

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO PARTIAL. A per-guest referral code is a documented first-class field, which the prior pass could not see: AddCustomerRequestBody carries a data-model row for the field ‘customer_details.referral_code’, typed ‘string’, required ‘No’, described ‘The customer’s referral code’ - FOUR TABLE CELLS, not the one contiguous span this note first quoted, and the field is namespaced, not bare - in BOTH the Provider Integration and Client Integration data models, it appears in the published Add Customer sample body, and the Portal’s loyalty registration configuration offers Referral Code as one of the selectable registration-field checkboxes (First Name, Middle Name, Last Name, Email, Phone Number, Code, Loyalty Card Number, Birthday, Address, Referral Code, Sms Opt In, Email Opt in). SHORTFALL: capture only. Nothing generates or issues a code or link, nothing attributes the referred guest’s first order, and no two-sided reward is documented - `referral link` 0, `refer a friend` 0, `two-sided` 0 across all 11,269 sections, and the closed nine-function loyalty operation list contains no referral operation. https://www.xenial.com/developer-resources/en/provider-integration-endpoints.html · retrieved 2026-09-12 adversarially verified

Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance, as an alternative to requiring a branded app download. differentiator

guest-loyalty-wallet-pass

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO PARTIAL. The prior pass had only a 2020 marketing blog post at grade D; the live release notes carry the product behaviour. Xenial Online Ordering issues value and loyalty passes into Apple Wallet: 2023-04-02 records 'Value and loyalty tickets added to Apple Wallet display as expected' and 2023-05-08 records 'Ticket number value displays as expected for Givex tickets in Apple Wallet'. SHORTFALL: the update mechanism and the second wallet are unevidenced. `push-updatable` 0, `pass update` 0, `Google Wallet` 1 document - and that one is a Nextep report note about Apple/Google PAY tender identifiers, not a loyalty pass - across all 11,269 sections. Nothing documents a balance that updates on the pass after issue, and the Givex framing suggests the pass is the gift/loyalty provider’s rather than Xenial’s. https://www.xenial.com/release-notes/en/genius-point-of-sale/enterprise-pos/online-ordering/release-notes---production-environment/previous-releases.html · retrieved 2026-09-12 adversarially verified

Provides admin tooling to fulfill guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records.

guest-loyalty-privacy-rights-tooling

CLAIM: admin tooling to fulfil guest data access AND deletion requests, including deletion propagation to loyalty and marketing records. VERDICT: unknown -> partial/B on newly readable first-party source. MET (the marketing half, operator-run, no vendor ticket): services/apiGateway/index.ts of the Xenial Analytics / Customer Intelligence app proxies '/contacts/delete' (deleteList) and '/contacts/delete/progress' (checkDeletionJobStatus(jobId), posting { deletionJobId: jobId }); store/emailMarketing/contacts/active/sagas.ts runs it as an async job and reports contacts_MultipleDeletionJobSuccessBody = '{0} contacts were deleted successfully.' The same admin holds '/contacts/list/unsubscribed' and builds a guest-facing '/opt-out/loyalty' link into every campaign footer (EmailTemplateEditor/EmailTable.tsx, mailTableOptOutFromTheLoyaltyProgram). NOT MET: (a) no ACCESS/export - there is no per-guest data export anywhere in the contacts or member modules, only getPdfForPage and campaign stats; (b) no LOYALTY deletion - the loyalty member API in the same gateway is exactly searchMembers, fetchMemberDetails, fetchMemberActivity, lockMember, unlockMember, so a member can be LOCKED but not deleted or anonymised, and nothing propagates a contact deletion to the member record; (c) gdpr|ccpa|anonymi[sz]|data subject|right to be forgotten are 0 across the 395 main + 1,474 chunk first-party sources (the one gdpr hit is a branding URL map to evopayments.eu/en/gpa-gdpr). SURFACE (new this pass): the anonymous Simple Service Registry https://ssr.xenial.com/?env=prod (200, 14,651 B, 112 prod service rows) names every Xenial production host; four of them serve PUBLIC SOURCE MAPS anonymously (retrieved 2026-09-17, each verified against a nonsense sibling path): xvi.xenial.com main-es2021.29e36e9d5f3e7723e50e.js.map (30.3 MB, 1,959 sources / 835 first-party), reports.xenial.com main.4672b942d3cda827.js.map (19.1 MB, 631 sources / 175 first-party), analytics.xenial.com main.fa2f8777.js.map (9.4 MB, 395 first-party) plus 213 of its 220 lazy chunk maps enumerated from the chunk table inside main.js (1,474 further first-party source entries), and xea.xenial.com main.5a404f0740583be4.js.map (9.8 MB, 261 first-party). A source map carries sourcesContent, i.e. the original TypeScript. Hosts whose .map answers were SPA-shell soft 200s and were discarded: xbo, team, record-and-play, mbs-xspot, braves-xspot, demo-xspot, tablesideordering-uat (that last one is an Amazon CloudFront placeholder). crt.sh for xenial.com returned 393 names, almost all qa-/dev-/devlab- copies that merge policy bars; the production extras (ordering.xenial.com, giftcardreorder, analytics-crm-demo, demo-global-bites) do not answer and orders.omni-eu 403s. Retrieved 2026-09-17. https://analytics.xenial.com/static/js/main.fa2f8777.js.map · retrieved 2026-09-17 adversarially verified

Enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log.

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

Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing (claim-level; verify it is a shipped product feature, not a roadmap statement). differentiator

guest-loyalty-ai-offer-recommendation

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

Offers native stored-value/gift card balances tied to the same guest profile and redeemable across all locations of the brand.

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

Employees clock in and out at the POS terminal using a PIN, badge, or card, with no separate time-clock hardware required.

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

Captures a photo at punch (or performs facial verification) attached to the timecard entry, with a photo-only mode available that stores no biometric template. differentiator

labor-photo-punch-verification

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO NO, and the control that nearly published a false zero belongs in the note: `biometric` is NOT absent - it matches 71 documents, because Xenial ships fingerprint biometrics for POS and clock-in authentication. That mechanism is the wrong one twice over. It is a fingerprint, not a photo or a face - the Peripherals editor defines a Fingerprint Reader, Company and Site Preferences carry a setting whose label cell reads ‘Use Biometrics’ and whose description cell reads ‘Select this option if a biometric fingerprint reader device is used at the site to grant users access to the POS application.’ - TWO TABLE CELLS, not the one contiguous span this note first quoted - alongside a Biometrics License Agreement field, Staff carries Skip Biometrics per employee, the GC26 and XC23 device pages each list a side-attached Biometric fingerprint scanner, and the Foodservice Management POS Clock In / Clock Out topic states 'Genius supports Biometrics fingerprint recognition within the POS system' - and it enrols a template, so the photo-only, no-template mode the claim asks for is the opposite of what is offered. The photo limb itself is absent: `photo punch` 0, `selfie` 0, `facial recognition` 0, `face match` 0 across all 11,269 sections. The Peripherals editor does define Camera and Camera (LAN) types, and Mobile Manager login 'does support mobile device biometric recognition' by Face ID, but no documented timekeeping flow attaches an image to a timecard entry; Clock Procedures is credential-only, ending 'Employees can clock in/out from a terminal without requiring the user currently signed on to the terminal to sign out.' https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-pos-app/clock-procedures.html · retrieved 2026-09-12 adversarially verified

Supports mobile clock-in restricted by geofence or location validation for staff who do not punch at a fixed terminal.

labor-geofenced-mobile-punch

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO NO. `geofence` 0, `mobile punch` 0, `remote punch` 0, `location validation` 0 across all 11,269 sections. Punching is documented only 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 the mobile products Xenial documents are enumerated and none of them punches: Genius Mobile Manager (Dashboard, Items, Orders, Control Panel, Change Revenue Center), the SuiteSpot venue app, and the Nextep guest app. Latitude and longitude occur twice in the whole corpus, once as automatic site geocoding in Portal Site Setup and once in an EasyPost parcel response, never as a staff position. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/enterprise-pos-app/clock-procedures.html · retrieved 2026-09-12 adversarially verified

Records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, with the behavior documented. differentiator

labor-offline-time-punch

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

Permissions are grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers.

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

Manager overrides and approvals are attributed to the individual approver and written to an immutable audit trail queryable after the fact.

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

Builds and publishes employee shift schedules inside the same platform that holds the timekeeping data, rather than requiring a third-party scheduling app. differentiator

labor-native-scheduling

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

Generates recommended staffing levels or labor hours by daypart from the operator's own POS sales history, not just a static template. differentiator

labor-demand-labor-forecast

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

Displays labor cost as a percentage of sales in real time during service on a manager view or POS, not only in end-of-day or next-morning reports. differentiator

labor-realtime-labor-percent

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

Warns or blocks at clock-in when an employee is approaching or would cross a configured overtime threshold, before the overtime is incurred. differentiator

labor-overtime-prevention

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

Configures meal and rest break rules per state or jurisdiction, prompts required break attestation, and flags missed breaks for premium pay. differentiator

labor-break-compliance-by-state

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

Supports predictive-scheduling ordinances by tracking advance-notice deadlines for published schedules and calculating predictability pay owed for employer-initiated changes.

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

Enforces minor-labor restrictions (age-based maximum hours, prohibited time windows, school-day limits) at both scheduling and clock-in.

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

Computes tip pooling and tip-outs automatically per shift from configurable rules (percentage of sales, hours worked, points, or role), rather than requiring a manual spreadsheet.

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

Retains a per-shift, per-employee record of tips received, amounts contributed to the pool, and amounts distributed from the pool, exportable for audit.

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

Payroll export separates cash from charged qualified tips and carries a Treasury tipped-occupation code, supporting the W-2 Box 12 code TP and Box 14b reporting required for tax year 2026. differentiator

labor-qualified-tips-w2-reporting

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO NO. `W-2` 0, `Box 12` 0, `tipped occupation` 0, `qualified tip` 0, `code TP` 0 across all 11,269 sections - a corpus whose release notes run to 2026-09 and which tracks payroll-law change in detail (multiple RTIconnect service packs for Nevada overtime, Saskatchewan and Alberta rules, Canada Premium formats), so a 2026 tax-year field would be visible here if it existed. The payroll export surface is published and is hours-and-wage shaped: the Back Office Export utility ('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) plus the named export formats and the Tips Allocation Summary and Paid Out Tips Detail reports. Cash and charged tips are distinguished for allocation, but no Treasury tipped-occupation code and no Box 12 code TP carrier exists. https://www.xenial.com/product-documentation/en/genius-back-office/export-data.html · retrieved 2026-09-12 adversarially verified

Vendor processes payroll itself as a first-party product (tax filing and direct deposit), as opposed to exporting to a third-party payroll provider only. differentiator

labor-native-payroll

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

Exports timecards, wages, and tips in documented formats or via direct integration for at least two major payroll providers (e.g. Gusto, ADP, Paychex, QuickBooks).

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

Employees can request shift swaps or claim open shifts in a self-service app, subject to a manager approval workflow that enforces overtime and role eligibility. differentiator

labor-shift-swap-workflow

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

Provides digital new-hire onboarding that collects W-4 and I-9 documentation and supports E-Verify submission.

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

Reports per-employee sales performance metrics (average check, items or category attachment rate, void and comp rate) by server or cashier. differentiator

labor-server-performance-metrics

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

Supports multi-level recipe/BOM costing where a recipe can contain sub-recipes (prep items) and plate cost recalculates automatically when any component ingredient's cost changes.

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

Stores purchase unit, recipe unit, and count unit per item with explicit conversion factors, plus a yield/waste percentage applied to raw-to-usable conversion.

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

Produces a theoretical-vs-actual usage variance report per item for a defined count period, showing theoretical usage from POS sales times recipe, actual usage from counts plus receipts, and the variance in both units and currency. differentiator

inventory-theoretical-vs-actual

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

Depletes ingredient on-hand quantities in near real time as orders are fired at the POS, including depletion driven by modifier selections, not only in an end-of-day batch. differentiator

inventory-realtime-depletion

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

Automatically 86s (marks unavailable) menu items on the POS, online ordering, and connected third-party delivery menus when a component ingredient hits zero or a configured threshold. differentiator

inventory-86-auto-sync

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

Supports full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts.

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

Provides a mobile/tablet counting app supporting barcode or QR scanning that continues to accept counts with no network connectivity and syncs on reconnect.

inventory-mobile-count-offline

CLAIM: a mobile/tablet counting app with barcode or QR scanning that keeps accepting counts with no network and syncs on reconnect. VERDICT: unknown -> partial/B. The published source of Xenial Venues Inventory (xvi.xenial.com) settles the scanning half and refutes the offline half for that app. MET: src/app/shared/services/scanning/scanning.service.ts is a first-class ScanningService - it buffers document keydown events (rx.buffer with a DEFAULT_ARTIFICIAL_INPUT_THRESHOLD debounce and a DEFAULT_VALID_SCANNING_LENGTH minimum) to tell a scanner from typing, then `public findItemIndex(upcCode: string, scanOptions: IScanResultOption)` locates the item in the grid; the error dictionary carries `ScannedCodeCanNotLocated`. It is injected into src/app/shared/services/inventory-count/inventory-count.form.service.ts (which also defines the cell class `scanning-highlight`), into the order and transfer containers, and into every numeric grid cell renderer (integer-renderer, float-input-renderer, price-input-renderer, each marked [attr.customScanning]=true); edit.orders.container.ts reads `upc_codes` off the Data Management item. The app is responsive (xux-side-nav-mobile hidden-desktop, mobile-show nav), so counting with a scanner on a tablet is shipped. NOT MET (offline): across the 835 first-party sources there is no service worker, no navigator.onLine, no offline queue and no ngsw - the only client persistence is draft recovery (xux-form-list.container.ts: `Method is used for asking a user about saving changed data in IndexedDB`) and expiring-storage.service.ts (`Uses localForage library to store in indexedDB when available`), neither of which is a count queue; the failure path is the i18n key `CheckInternetAndTryAgain`. CONTROLS/POISON: case-insensitive `sync` matched 357 files purely through `async`; `scan` matched `rx.scan` and `nested-scan`; tokenised offline = 0 and ngsw|serviceWorker|navigator.onLine = 0 over the 835 first-party sources. BOUND: this is the Venues Inventory web app only; the back office (xbo.xenial.com) ships no readable map, so this cannot exclude an offline counting app elsewhere in the Xenial line. SURFACE (new this pass): the anonymous Simple Service Registry https://ssr.xenial.com/?env=prod (200, 14,651 B, 112 prod service rows) names every Xenial production host; four of them serve PUBLIC SOURCE MAPS anonymously (retrieved 2026-09-17, each verified against a nonsense sibling path): xvi.xenial.com main-es2021.29e36e9d5f3e7723e50e.js.map (30.3 MB, 1,959 sources / 835 first-party), reports.xenial.com main.4672b942d3cda827.js.map (19.1 MB, 631 sources / 175 first-party), analytics.xenial.com main.fa2f8777.js.map (9.4 MB, 395 first-party) plus 213 of its 220 lazy chunk maps enumerated from the chunk table inside main.js (1,474 further first-party source entries), and xea.xenial.com main.5a404f0740583be4.js.map (9.8 MB, 261 first-party). A source map carries sourcesContent, i.e. the original TypeScript. Hosts whose .map answers were SPA-shell soft 200s and were discarded: xbo, team, record-and-play, mbs-xspot, braves-xspot, demo-xspot, tablesideordering-uat (that last one is an Amazon CloudFront placeholder). crt.sh for xenial.com returned 393 names, almost all qa-/dev-/devlab- copies that merge policy bars; the production extras (ordering.xenial.com, giftcardreorder, analytics-crm-demo, demo-global-bites) do not answer and orders.omni-eu 403s. Retrieved 2026-09-17. https://xvi.xenial.com/main-es2021.29e36e9d5f3e7723e50e.js.map · retrieved 2026-09-17 adversarially verified

Ships pre-built electronic vendor catalog and order-transmission integrations with named broadline distributors (e.g. Sysco, US Foods, Performance Food Group) that send purchase orders and receive invoices electronically rather than by emailed PDF. differentiator

inventory-vendor-catalogs-edi

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

Ingests supplier invoices from photo, PDF, or email and extracts line-item detail (item, quantity, unit, price) into the inventory ledger without manual line entry. differentiator

inventory-invoice-ocr

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

Tracks per-item purchase price history across invoices and alerts when a received price exceeds the prior or contracted price by a configurable threshold. differentiator

inventory-price-change-alerts

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

Maintains par levels per item per location and generates suggested purchase order quantities from on-hand versus par, with at least one mode driven by a sales forecast rather than a static par. differentiator

inventory-par-auto-suggest

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

Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.

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

Supports inter-location inventory transfers as a two-sided transaction crediting the sending location and debiting the receiving location, with an in-transit or approval state.

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

Supports a commissary/central kitchen model where one location produces prep items and issues or sells them to other locations at a computed transfer cost.

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

Captures lot/batch numbers at receiving and links them through production to sales or transfers, enabling a backward and forward recall trace.

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

Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.

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

Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.

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 and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator

inventory-native-not-partner

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

Joins recipe cost to actual item sales mix to report contribution margin per menu item, and flags items whose margin fell below a configured threshold after ingredient cost changes. differentiator

inventory-menu-margin-linkage

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

Provides a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise.

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

Generates a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types, and expected cash deposit in one document.

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

Provides a product mix (PMIX) report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center.

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

Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.

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

Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.

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

Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.

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

Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator

reporting-channel-profitability

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

Provides a consolidated multi-location report with side-by-side location comparison and drill-down from group total to a single location and then to an individual transaction. differentiator

reporting-multiloc-drilldown

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

Includes a self-service report builder letting a non-developer choose dimensions, measures, and filters and save the result, rather than only fixed canned reports. differentiator

reporting-custom-report-builder

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

Supports scheduling any report for automatic recurring delivery by email or to a shared destination on a defined cadence and recipient list.

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

Offers automated recurring bulk export of transaction-level raw data to a customer-controlled destination (S3, SFTP, Snowflake, BigQuery, or equivalent), not just manual CSV download. differentiator

reporting-raw-warehouse-export

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

Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator

reporting-public-api

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

Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator

reporting-webhooks

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

API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator

reporting-api-not-upcharged

Upheld. The decisive constraint is that the earlier pass had /developer-resources/en/ LIVE (293 pages / 3,333 sections, dumped 2026-08-08) and left this unknown; my corpus is the 2021-2023 pre-Genius Wayback tree under a different URL scheme and contains NONE of those paths, so it is an older, smaller, strict subset on exactly this question and cannot reopen what a richer surface closed. Re-reading the published Consolidated System Terms (2023 revision, captured 2024-03-29) confirms why no contract can settle it either: Section 5.1 delegates every Fee to 'the Sales Agreement', an order form we do not hold, and the contract's own Schedules/Exhibits index names two further documents marked 'Provided Separately' that are not public - the Support Services Price List and the Site Readiness Specifications. APIs appear in the contract only as Xenial property (Section 3.1 sweeps 'application program interfaces ( APIs )' into Xenial Materials) and as third-party dependencies (Section 3.9). Schedule A's enumerated Services are Point of Sale System, Menu Maintenance, Content Management, Loyalty Module, Mobile Ordering Module and SaaS - no data or API service among them. Contract silence that is expressly delegated elsewhere is not evidence of inclusion. Resolvable only by the Support Services Price List, an executed Sales Agreement, or a Genius developer-portal pricing page - and the developer surface is now unreachable, because www.xenial.com returns 403 on /robots.txt to POSAtlasBot, curl and Chrome alike and the repo's scope proof fails. || 325th: NEW MEASUREMENT, cell still unknown, and the standing note's 'the developer surface is now unreachable' is STALE: www.xenial.com 403s only on /robots.txt, while /sitemap.xml (500 locs) and all 293 developer-portal topics answer 200 to curl with a browser UA (a nonsense topic 404s at 0 bytes). Re-read for this cell: the gate is still stated legally, never priced. Reporting API | Getting Started publishes a three-step onboarding - '1 Getting Started with APIs... 2 Confidentiality Statement: Information about our non-disclosure agreement (NDA) terms and conditions regarding endpoints. 3 API Prerequisites' - and the identical three steps head every other API book (Partner Relay, Pipeline, Payment Router, Portal, Staff, Back Office). Controls over the whole 293-topic corpus: the 38 word-boundary 'fee' hits are all the Data Management 'Fee Definition' object (GET /fee-definition/current, GET /fee-definition/list), the 19 'pricing' hits are 'Pricing Menu' and the 'Digital Menu Board Pricing API', and the 11 'cost' hits are 'Inventory Item Cost' - the portal's money vocabulary is menu data, not commercial terms. No price list, tier or per-location API fee is published on it. Retrieved 2026-09-17. || 332nd: 332nd NEW SURFACE: Global Payments' own Genius Enterprise product pages under www.globalpayments.com/point-of-sale/enterprise/ (enterprise-pos, back-office, kitchen-management, kiosk, digital-menu-board, drive-thru, food-service-management) plus the umbrella /genius page. Live host is a Cloudflare 403 to curl with full browser + Sec-Fetch headers and to WebFetch (a refusal, not an absence), so read via Wayback id_ captures 2025-09-09..2026-05-27 (never cited by any prior pass). NEW: Global Payments' Genius Back Office page (Wayback 20250909011610) sells raw-data access as an ADD-ON: 'API-driven data streams (via our Data Stream add-on) to power third party BI dashboards' and 'Our restaurant back office system integrates with Data Stream, enabling exports to third-party BI and analytics platforms'. The developer portal's data-stream---getting-started.html step 4 'Set up Subscription Configuration' is SQS/token/IP-whitelist plumbing, not a price. 'add-on' is a packaging noun with no stated fee, per-location charge or plan gate, so per the 329th merge rule it cannot carry a `no`; but it is the first vendor sentence indicating raw-data export is NOT in the base package, so a `yes` is now contradicted as well. Held unknown. Retrieved 2026-09-18. || 334th: 334th NEW SURFACE: the App Store PUBLISHER census for Xenial (itunes lookup?id=1455368071&entity=software = 4 apps: Xenial Shell com.xenial.shell.app, Genius Mobile Manager, Genius Back Office Mobile, and Genius Team Portal Mobile io.genius.tp.mobile.app, the last NEW since the 328th: released 2025-11-04, an employee schedule/time-off/shift-swap app). The Xenial Shell listing's closed plan enumeration (base: Ordering, Dynamic menus, Localized sales tax engine, Reporting, Time clock, Payment connection, Payroll connection; paid add-ons: Kitchen management, Scheduling, Inventory, Instant data & alerts, Manager log & tasks, B2C CRM, Stored value, Loyalty, Customer engagement, Email campaigns, Single-use coupons) puts 'Reporting' in the base plan but names no API or raw-data export in either list; legacy Xenial SMB text, not the Genius Enterprise contract, and silent on the claim. Weighs nothing against the 332nd's 'Data Stream add-on' reading. Held unknown. Retrieved 2026-09-18. adversarially verified

Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator

reporting-tier-paywall

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

Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator

reporting-history-retention

CLAIM: documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. VERDICT: no. The vendor's DESIGNATED data-retention publication has now been found and it documents no such window. notification-service---getting-started.html points to it explicitly ('For information on data retention policies, see SMS Data Retention'), and that page states, verbatim: 'Under the Genius data retention policy, phone numbers captured within the order object are managed as Personally Identifiable Information (PII) data collected in the order... Local orders are retained on in-store devices, such as tablets and point of sale (POS) terminals, for one business day post-finalization. After one business day, the order data is purged. The order data is transmitted to the Genius cloud and stored within an encrypted database for an extended period until archiving, and is excluded from external interfaces, such as Data Stream.' The only quantified figures on the page are Twilio's 13-month SMS log retention and a one-year life for the HTML SMS receipt URL. BOUND/CONTROLS: over the 100%-fetched 293-topic portal 'retention|purge|archiv' returns 35 hits in 10 topics and every one is either this page, the order-state value 'purged', the Company Preferences 'Order Purge pane' (hours an abandoned order persists), the Enterprise Kitchen Purge event, or the Data Stream 'Purged Order at EOD' notification - none is a reporting horizon. The only quantified historical horizon Xenial publishes runs the other way: report-gethistorical.html states 'The Chef API offers up to two weeks of historical transactional data.' With the already recorded zeros (1,274-page Paligo census; reports.xenial.com's 175 first-party sources, where the client publishes no cap and reads a server-side per-company min_date), the vendor documents retention and documents no >=24-month queryable window - the claim's first conjunct failing on the vendor's own retention page, with archiving named and unquantified, which is the silent truncation the claim guards against. SURFACE (new this pass, 100% of the publisher's own manifest): the LIVE Genius developer portal https://www.xenial.com/developer-resources/en/index-en.html publishes a TOC of 293 topic permalinks; all 293 were fetched at HTTP 200 on 2026-09-17 (3.10 MB of nav-stripped topic text). SOFT-200/CATCH-ALL CONTROL PASSED: /developer-resources/en/zzz-nonsense-topic.html returns 404 with a 0-byte body. www.xenial.com still 403s on /robots.txt to every client but serves /sitemap.xml (500 locs) and every topic page to curl with a browser UA. Positive controls in the stripped corpus: 'order' 3,314 hits/159 topics, 'loyalty' 571/26, 'delivery' 216/28, 'webhook' 50/14. Retrieved 2026-09-17. https://www.xenial.com/developer-resources/en/sms-data-retention.html · retrieved 2026-09-17 adversarially verified

Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator

reporting-anomaly-alerts

Product line: Xenial/Genius MOBILE MANAGER, the multi-site manager phone app over Xenial Cloud - not the Back Office KPIs or Portal Reports surfaces the 2026-08-08 pass enumerated, which is why it went unfound. Wayback captures 2023-03-29 (alerts.html) and 2023-03-25 (define-application-preferences.html); the live host is walled (robots.txt 403 to POSAtlasBot, curl and Chrome alike), so this is an Internet Archive citation. Account > Preferences > Alerts is an operator-configured threshold engine in six categories - Checks, Discount, Fraud Detection, Labor, Tips, Void - in which the operator toggles each alert on and types the triggering value ('Toggle on/off the desired alerts to enable/disable push notifications ... Type or select the desired values for each alert'), and a breach raises a push notification to the phone. Named operator-set thresholds include 'Any check is above', 'Send push notification if discount is equal or greater than' (per-transaction and per-day), 'Number of discounts is equal or greater than' (per employee and across all employees), 'Send alert if labor cost exceeds' (labor cost percentage against sales total and time of day), 'If tip on check is highest than' (order-total percentage) and 'Send push notification if void is over'. Delivery is scoped per site (Appearance & Behavior > Enable Notifications > Select Sites) with a quiet-hours window. The claim is a DISJUNCTION - threshold breach OR deviation from historical pattern - and the first limb is met outright, natively, with push delivery. SHORTFALL RECORDED FOR HONESTY: every trigger is a fixed operator-set threshold or a fraud event; no deviation-from-history or sales-below-forecast rule is documented anywhere in the corpus. CURRENCY: the module is documented in a 2023 capture, but Mobile Manager is a live product book in the current Genius tree - product.yaml lists 'Genius Mobile Manager' among the shipping Genius product names and this record's own commercial-privacy-dsar-tooling row cites Mobile Manager's Accounts > Privacy area from the live portal at retrieved 2026-08-08 - so the module survived the Sept-2025 rebrand. What the 2023 capture cannot establish is that the Alerts page itself is unchanged. https://web.archive.org/web/20230329171255id_/https://www.xenial.com/product-documentation/en/xenial-mobile-manager/alerts.html · retrieved 2026-09-05 adversarially verified

Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.

reporting-nl-query

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO NO. `natural language` 0, `AI assistant` 0, `copilot` 0, `generative` 0, `LLM` 0, `ask a question` 0, `artificial intelligence` 0, `machine learning` 0 across all 11,269 sections - a corpus running to 2026-09 release notes, so a shipped assistant could not be invisible in it. The 11 documents matching `conversational` are Conversational Ordering, a POS menu-flow mode, and the 6 `AI` matches are the Voice AI partner category and the .AI artwork file format; both false friends. The reporting product as published is a fixed catalogue reached by picking a category and a report and setting Parameters - 'Open a report category to access the list of reports that are available' - with the only free-text affordance being 'In the Search Reports field, type criteria to search for a specific report name', i.e. a report-name search, not a query over the operator’s data. https://www.xenial.com/product-documentation/en/genius-point-of-sale/enterprise-pos/reporting/reporting-overview.html · retrieved 2026-09-12 adversarially verified

Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator

reporting-guest-cohorts

CLAIM: guest-level analytics including new vs returning guest counts, visit frequency and lifetime-spend cohorts tied to identifiable guest records from loyalty or online ordering. VERDICT partial, grade B (anonymously served first-party production UI bundle of Xenial's Analytics XP, registry row analytics-xp -> https://analytics.xenial.com in https://ssr.xenial.com/?env=prod; B not A because a minified UI bundle is the product surface, not published source). Verifier re-fetched live 2026-09-16; lazy chunk URLs resolved from the served main.js chunk map. MET: (1) new vs returning counts - https://analytics.xenial.com/static/js/9431.7257cf5a.chunk.js title 'NEW VS RETURNING CUSTOMERS', hint 'The percentage of new and returning customers at your location and that of your competitors'; https://analytics.xenial.com/static/js/8518.0223cb03.chunk.js '<b>New Customer:</b> A customer who made their first transaction with your business in the last 12 months.' / '<b>Returning Customer:</b> A customer who has made more than one transaction with your business in the last 12 months.'; dictionary labels 'New Visits', 'Return Visits'. (2) visit frequency - https://analytics.xenial.com/static/js/4020.db8c3a08.chunk.js RFM 'Frequency', legend 'Avg. Number of Visits in a Month', hint 'Frequency is a view of how often customers visit within {0} Days' (30); 'Avg. Days Between Visits'. (3) lifetime-value cohorts - https://analytics.xenial.com/static/js/7577.5bf5d472.chunk.js renders monetaryLifeTimeValue per RFM tier. SHORT (named): the cohort identity is the payment-card transaction, not an identifiable loyalty or online-ordering guest record. main.js defines the data-provider enum {transactions:'transactions', mastercard:'mastercard'} and the 8518 and 7577 widgets pass dataProvider transactions; competitor comparison comes from a Mastercard data fetcher (MastercardCompareDataFetcher). The product's loyalty module is separate: https://analytics.xenial.com/static/js/3412.19b330a6.chunk.js member detail shows Email Address, Phone Number, Date Enrolled, Linked Cards ('the number of cards (payment methods) linked with the loyalty member's account'), Points Total ('total amount of points ever earned') and activity history - no visit count, spend or cohort per member; chunk_7809 member search is by phone/email with columns Loyalty ID, Date Enrolled, Last Activity, Status. Nothing binds the new/returning or RFM cohorts to those member records, and the claim's qualifier ('tied to identifiable guest records from loyalty or online ordering') is not met by card-derived identity; this matches the 2021 Xenial Analytics marketing wording 'Based on credit card sales'. The analysis is real and three of four conjuncts are met, so partial not unknown. CONTROLS: tokenised \b(new|returning|repeat|first-time) (customers?|guests?|visitors?)\b = 0 across the 223-file reports/staff/xprt/dm/xvi/xcat/xea corpus, 13 files once the 220 analytics chunks were added - the capability lives only in analytics.xenial.com. POISON: main.js mock data tier1..tier5 lifetimeValue (1e4..1e5) is a demo/mock generator, not evidence of a report - the live widget evidence is chunk 7577; 'Google Business Profile' is a listing-management programme; the bundle carries evopayments.eu legal URLs and TSYS/GPI teaser keys (a Global Payments shared analytics product, likely dependent on Global Payments card processing - not established). https://analytics.xenial.com/static/js/main.fa2f8777.js · retrieved 2026-09-16 adversarially verified

Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator

reporting-sales-forecast

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

Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.

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

Supports a named organizational hierarchy of at least three levels (e.g. enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations.

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

A corporate-level menu can be authored once and published to a chosen set of locations in a single action, with a publish/version history showing what was pushed, when, and by whom.

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

Corporate menu items expose per-field override rules so a location can change some attributes (e.g. price, availability) while corporate locks others (e.g. name, image, recipe), and locked fields are not editable at store level. differentiator

multi-location-local-override-policy

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

Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.

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

Menu, price, and promo changes can be scheduled to activate at a future date/time interpreted in each target location's own timezone, and can be rolled back after activation. differentiator

multi-location-scheduled-publish

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

A new location can be provisioned by cloning a documented configuration template (menu, taxes, roles, printers, modifiers, tenders) rather than being configured from scratch, and the vendor publishes the expected time-to-open. differentiator

multi-location-new-store-template

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

The permission model distinguishes a franchisor/corporate tenant from an independently-owned franchisee tenant, so corporate can see franchisee sales and enforce config while the franchisee owns its own employees, banking, and labor data. differentiator

multi-location-corp-vs-franchisee-roles

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

Calculates franchise royalty, ad-fund, and marketing-fee amounts automatically from POS net sales on a defined schedule, with a configurable royalty basis (gross vs net of discounts/comps/third-party). differentiator

multi-location-royalty-calculation

Upheld, now tested against the contract as well as the docs. Royalty, ad fund and franchise fee return ZERO hits across all 1,197 recovered files except one blog quotation about McDonald's franchisee relief. In the Consolidated System Terms (2023 revision, captured 2024-03-29) 'royalty' appears only inside the IP licence grants ('royalty-free license to host, copy, transmit and display the Customer Data') - never as a franchise fee. The nearest structural finding is Schedule A's Brand Rights clause, which contemplates the franchisor data flow a royalty engine would consume but not the engine itself: the System 'may be designed or configured to transmit or facilitate the transmission of Customer data through Xenial to the Brand (including daily menu sales, ticket count and menu item product mix and other data identifiable by Authorized Restaurant Location)'. Combined with the earlier pass's Back Office 'Store Fields Setup' finding (customisable numeric store fields illustrated 'e.g.: Rent and Royalty' - a manually keyed value, not a computed one), the evidence leans toward absence, but it is entirely a zero-hit over a corpus that is a measured floor, so a no is not available. Resolvable by a Genius Back Office franchise-fee module page. || 323rd: NEW SURFACE, cell still unknown. The Reporting UI publishes a CLOSED report catalogue in first-party source: src/app/containers/reports/report/ag-grid-reports/helpers/report-identificators.ts enumerates enum ReportType with 65 members (employeeScorecardReport, enterpriseSalesSummaryReport, orderExplorerReport, orderPaymentsReport, inventoryCountReport, depositSummary, salesOverShort, LiabilityDetail, payrollSummaryReport, weeklySalesAndLaborHistory, irisPayrollSummary, webSRM, taxExemptSalesReport, timecardAuditReport and so on) plus parallel ReportName, ReportTitle and ReportID enums; no royalty, franchise-fee or ad-fund report is among them, and tokenised royalt(y|ies)|franchise fee|ad fund is 0 across all four first-party source-map corpora (835 + 175 + 395 + 261 sources). This does NOT license a no: the enum bounds the Reporting UI alone, and the Back Office (xbo.xenial.com), where a franchise-fee module would live, ships no readable source. SURFACE (new this pass): the anonymous Simple Service Registry https://ssr.xenial.com/?env=prod (200, 14,651 B, 112 prod service rows) names every Xenial production host; four of them serve PUBLIC SOURCE MAPS anonymously (retrieved 2026-09-17, each verified against a nonsense sibling path): xvi.xenial.com main-es2021.29e36e9d5f3e7723e50e.js.map (30.3 MB, 1,959 sources / 835 first-party), reports.xenial.com main.4672b942d3cda827.js.map (19.1 MB, 631 sources / 175 first-party), analytics.xenial.com main.fa2f8777.js.map (9.4 MB, 395 first-party) plus 213 of its 220 lazy chunk maps enumerated from the chunk table inside main.js (1,474 further first-party source entries), and xea.xenial.com main.5a404f0740583be4.js.map (9.8 MB, 261 first-party). A source map carries sourcesContent, i.e. the original TypeScript. Hosts whose .map answers were SPA-shell soft 200s and were discarded: xbo, team, record-and-play, mbs-xspot, braves-xspot, demo-xspot, tablesideordering-uat (that last one is an Amazon CloudFront placeholder). crt.sh for xenial.com returned 393 names, almost all qa-/dev-/devlab- copies that merge policy bars; the production extras (ordering.xenial.com, giftcardreorder, analytics-crm-demo, demo-global-bites) do not answer and orders.omni-eu 403s. Retrieved 2026-09-17. || 324th: NEW INSTRUMENT, same answer: the standing note's zeros were measured on a 2021-2023 Wayback tree. They now also hold on the LIVE 2026 product's configuration app. dm.xenial.com (Genius DataManagement UI) was censused to a closed script-loader fixpoint - 1,292 chunk hashes in runtime-es2021.44ce99f3ae07daa03f5d.js, all fetched plus main and runtime, 1,294 files / 36.6 MB, 0 new chunk references on round 2, soft-200 control passed (main-es2021.ZZZ.js -> 404). Over that corpus 'royalt' 0, 'franchise fee' 0, 'ad fund' 0, 'virtual brand|multi-brand|multiBrand' 0, while positive controls hold ('pricePoint' 81, 'order_source' 225, 'receipt' 120). Still unknown rather than `no` because a royalty calculation is a REPORTING function and this is the configuration app; the reporting app reports.xenial.com is a separate bundle set and its backend (reportsbackend.xenial.com, per the ssr.xenial.com registry) exposes only /info anonymously. Retrieved 2026-09-17. || 325th: NEW INSTRUMENT, same answer, plus a dead end future passes should not re-walk. (1) Over the 100%-fetched 293-topic Genius developer portal - which includes the 'Genius Back Office' book (Back Office API | Getting Started, Things to Know, Connect to Back Office API, Back Office APIs) - 'royalt' 0, 'franchise fee' 0, 'ad fund' 0, while 'order' scores 3,314 hits in 159 topics. (2) THE BACK OFFICE UI ITSELF STILL SHIPS NO READABLE SOURCE, and the reason is now measured: https://xbo.xenial.com/ serves only a login app - index.html is titled 'Genius Back Office' but loads runtime.3f1529c52ac43df0.js whose webpack namespace is `webpackChunkxconnect_login` and whose chunk-hash table r.u holds just 7 entries {76:common, 492, 597, 622, 680, 786, 924}; main.d2b4071db69d00c7.js is 876,628 B and contains 'royalt' 0, 'franchise' 0, 'deposit' 0, 'retention' 0, 'brand' 0 (its 'driver'/'dispatch' hits are Angular internals). A nonsense sibling (main.ZZZNONSENSE.js) returns the 3,185-byte index shell with HTTP 200, so every xbo .js answer must be length-checked before it is believed. (3) Also probed and empty: 93 xenial.com / genius.io service-registry hosts x 7 spec paths (/openapi.json, /swagger/v1/swagger.json, /v3/api-docs, /swagger.json, /api-docs, /q/openapi, /swagger-ui/index.html) = 651 requests, zero anonymous specs; every 200 was an SPA shell or 'Hello from the load balancer!'. Retrieved 2026-09-17. || 328th: 328th: NEW CORPUS, same answer. Re-grepped for this cell against the Xenial APK web-asset corpus described on hardware-byod (Genius Shell assets/www + xbo assets/public + mobilemanager assets/public = 1,781 files / 9,489,331 chars, first time any pass grepped the web assets inside the packages): 'franchise fee' 0, 'ad fund' 0, and `royalty` scores 11 with every single hit the Apache-2.0 licence phrase 'no-charge, royalty-free' inside mobilemanager's 3rdpartylicenses.txt - POISON, and severe, because a substring grep of any Xenial bundle will report a non-zero royalty count from its third-party licence file alone. Retrieved 2026-09-18. adversarially verified

Supports automated ACH/debit collection of calculated royalties and fees from franchisee accounts, with a franchisee-visible statement of what was charged.

multi-location-royalty-collection

Upheld. The only ACH surface in the entire recovered legal set runs the opposite way: Schedule C (ACH - US) and Schedule C-1 (ACH - Canada) of the Consolidated System Terms are each an 'Authorization for Direct Payment via ACH (ACH Debit)' by which the CUSTOMER authorises Xenial to debit the customer for Xenial's own invoices - 'Customer agrees to execute one of the two attached Direct Debit Authorizations ... to allow Xenial' - not a franchisor sweeping royalties from franchisees. No franchisee-facing statement of charges exists anywhere in the corpus. This follows multi-location-royalty-calculation: there is no computed royalty amount to collect. Still unknown rather than no, because the finding rests on a zero-hit over a floor corpus and on contract silence, and the contract expressly delegates commercial mechanics to a Sales Agreement and a Support Services Price List that we do not hold. || 325th: NEW INSTRUMENT, same answer: over the 100%-fetched 293-topic Genius developer portal (including the Genius Back Office book) 'royalt' 0, 'franchise fee' 0, 'ad fund' 0, and no franchisee statement-of-charges or ACH-sweep surface appears. The only money-movement topic is Data Stream 'Deposits', which is the POS Cash Management declaration of cash - 'Deposit Transactions are performed as a part of Cash Management at POS API, which allows users to declare how much currency to send to the bank' - with Deposit Status Open/Finalized/Deleted and itemised denomination counts. Retrieved 2026-09-17. adversarially verified

Provides above-store reporting that aggregates sales, labor, discounts, voids, and item mix across any selected set of locations in one view, with store-vs-store ranking and variance flags.

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

Item-level sales roll up across locations under a shared corporate item ID even when stores have renamed or locally priced the item. differentiator

multi-location-normalized-item-rollup

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

Gift cards issued at one location are redeemable at any other location in the brand, with a reported outstanding-liability balance and inter-store settlement/redemption reconciliation between owners.

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

A single customer loyalty profile, balance, and stored order history is shared across all locations in the brand rather than being per-location.

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

A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. differentiator

multi-location-multi-brand

Upheld. Virtual brand, multi-brand, dual brand and second brand return zero substantive hits across all 1,197 files (the only 'co-brand' matches are boilerplate in the US and Canadian privacy policies about marketing partners). The earlier pass's structural reading survives and the contract reinforces it: the unit of licensing is the 'Authorized Restaurant Location', Schedule A caps the POS Software Service at 'a maximum of five (5) Xenial point-of-sale terminals', and 'Brand' throughout the contract denotes the FRANCHISOR entity above the customer, never a switchable identity inside a store. Separation within a site is expressed through Revenue Centers, Order Sources, Destinations, Price Points and Terminal Schemes. But no page claims to enumerate every concept a site may run, so this remains a zero-hit over a floor. Resolvable by a Genius Portal page documenting two separately branded, separately reported concepts on one terminal and drawer. || 324th: NEW INSTRUMENT, same answer, now measured on the live product rather than a 2023 capture: over the closed 1,294-file script-loader fixpoint census of dm.xenial.com (Genius DataManagement UI; 1,292 loader-table chunks + main + runtime, 36.6 MB, round-2 new references 0, soft-200 control passed) the word 'brand' returns exactly 1 hit and 'concept' returns 0, while the configuration unit remains the SITE throughout (site selector, site-specific prices, `Merchant Site ID`, per-site payment identity, 'This service is only available at the site-level'). Positive controls hold in the same corpus ('pricePoint' 81, 'order_source' 225). Held unknown rather than `no` for the reason the standing note gives: menu/brand segregation could be expressed through the Menu Engine (xme.xenial.com) or Suite Catering, neither of which serves an anonymous surface. Retrieved 2026-09-17. || 325th: NEW INSTRUMENT, same answer: over the 100%-fetched 293-topic Genius developer portal 'virtual brand|multi-brand|dual brand|second brand|concept' returns 4 hits in 3 topics, none a switchable in-store identity, while the documented separation axes remain Order Source, Order Destination (consumption_type), Revenue Center, Price Point and Terminal Scheme. The Menu Engine - named in the standing note as the unmeasured place brand segregation might live - is now documented here (menu-structure.html, pricing-menu.html, item-availability.html, menu-engine-api---getting-started.html) and segregates by SITE, tag and exclusion list, not by brand. Retrieved 2026-09-17. || 326th: NEW SURFACE (326th), and it does NOT bound the restaurant POS - stated plainly. The 61 `*-xspot.xenial.com` hosts in the crt.sh listing are live production instances of Xenial's guest-facing SuiteSpot ordering app (Angular; braves-xspot.xenial.com serves <title>SuiteSpot</title> with body data-company-code="BRAVES" and loads FreedomPay's hpc_min.js). I took it to a CENSUS: the webpack runtime (runtime.bce2fd5f94dece6a.js) carries a complete chunk-hash table of 76 entries; all 75 lazy chunks plus main.ab83504f760b9d4a.js fetched at 200, 7.61 MB of production JS, 0 misses, no unmapped loader entries. SOFT-200 CONTROL PASSED: /main.ZZZZZZZZ.js returns the 1,119-byte index.html shell and every fetched chunk is larger and begins with webpack chunk syntax, so none of the 75 is a shell. This is the VENUES/stadium suite-catering guest app, not the restaurant POS or the Genius back office, so under the standing merge rule it bounds only itself. WHAT IT HELD for this cell: `virtual brand` = 0, `multi-brand` / `multibrand` = 0, `brand` = 1 over the 7.61 MB census, against 458 hits for `suite` - the app's entire identity model is one company code baked into the served HTML (body data-company-code="BRAVES"), i.e. one instance per venue rather than switchable brands inside one instance. That is consistent with the standing note's structural reading (the licensed unit is the location, separation inside a site runs through Revenue Centers / Order Sources / Destinations) but adds no new conjunct, and a per-venue guest app is the wrong publisher for a POS terminal-level claim. Retrieved 2026-09-18. || 327th: 327th, A CONTROL WHOSE FIGURE IS ENTIRELY POISON. 327th NEW COMBINED FIRST-PARTY FRONT-END CORPUS (nobody had run this cell against it): the 229 complete public source maps of FOUR Xenial SPAs already on disk (analytics.xenial.com, reports.xenial.com, xea.xenial.com, xvi.xenial.com; 118.9 MB) UNIONED with the 724 readable files of the closed 1,294-file script-loader fixpoint census of dm.xenial.com (Genius DataManagement, 49.5 MB) = 1,524 files / 168.3 MB of the vendor's own shipped code and i18n dictionaries. Denominator stated; these are BACK-OFFICE/analytics apps and by merge policy do not bound the store-level POS. 'concept' scores 22 hits over the 229-map set and every single one is library prose, not a restaurant concept: React's ReactMultiChild comment ('React itself does not directly have this concept of the union of prevChildren and nextChildren'), parse5's link to dom.spec.whatwg.org/#concept-document-limited-quirks, jQuery's html.spec.whatwg.org/#concept-fe-disabled, redux-saga's 'we model this using the concept of Parent task', a webpack.js.org/concepts/mode/ warning, and an Argentine CUIT validator citing a Spanish page titled 'Conceptos basicos'. Tokenising does not help - the word is genuine, the referent is not. 'virtual|multi-|dual-|second brand' = 0 and 'brand' remains a franchisor label. Publishing the invariance rather than the figure: across four analytics/reporting SPAs plus the Genius configuration app there is no switchable in-store identity. Still unknown: back-office apps do not bound the store-level POS. Retrieved 2026-09-18. || 332nd: 332nd NEW SURFACE: Global Payments' own Genius Enterprise product pages under www.globalpayments.com/point-of-sale/enterprise/ (enterprise-pos, back-office, kitchen-management, kiosk, digital-menu-board, drive-thru, food-service-management) plus the umbrella /genius page. Live host is a Cloudflare 403 to curl with full browser + Sec-Fetch headers and to WebFetch (a refusal, not an absence), so read via Wayback id_ captures 2025-09-09..2026-05-27 (never cited by any prior pass). 'brand' on them is an above-store dimension: Enterprise POS 'Use role-based access control by brand, region or store' and 'Built to support a wide range of restaurant configurations, from flagship venues to satellite concepts'; Back Office 'Customize dashboards to see trends by region, brand or user type'. That confirms brand is a hierarchy level for RBAC and reporting across a franchisor portfolio, but says nothing of two brands on one terminal/drawer with separate receipts ('virtual brand' 0, 'multi-brand' 0, 'co-brand' 0). Held unknown. Retrieved 2026-09-18. || 333rd: 333rd VIDEO CENSUS (new surface type for this record): Global Payments' YouTube channel 'Genius by Global Payments' (@GeniusPOS, 143 uploads listed by yt-dlp --flat-playlist; POISON: @Xenial is an unrelated gaming channel) and Nextep's legacy channel (@NextepSystems, 19 uploads), plus the Global Payments Vidyard hub videos.globalpayments.com (Cloudflare 403 live; its 6 Wayback-known player ids read via play.vidyard.com/player/<id>.json, 5 with English VTT captions: 'Stadium Capabilities', 'Meet Genius', 'Introducing Genius for Retail', 'Commerce Made Easy', 'Brand Launch'). YouTube caption tracks returned 429 to both youtube-transcript-api and timedtext, so only titles, descriptions and 1080p frames were read. For THIS cell the one candidate is 'How SE Co-Brand manages digital menus across every location' (14ZnzH7Xzkk, 88 s). Its vendor-written description: 'SE Co-Brand Ventures franchises iconic snack brands like Auntie Anne's, Cinnabon and Jamba ... With Genius digital menu boards, SE Co-Brand replaced a patchwork of disconnected systems with a single, cloud-based platform. Now they can make updates across every location in seconds.' The product is Genius DIGITAL MENU BOARDS, not the POS, and 35 frames at 2.5 s intervals (1080p) are a talking-head testimonial (Dustin King, COO) with no POS or brand-switch screen. A multi-brand franchisee using menu boards does not show one terminal ringing two brands. Retrieved 2026-09-18. adversarially verified

Tax configuration is per-location with support for multiple simultaneous tax rates, jurisdiction-specific rules (e.g. prepared-food vs grocery, inclusive vs exclusive tax), and per-location tax exemptions.

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

Supports locations operating in different currencies and languages within one enterprise account, with consolidated reporting converted to a reporting currency.

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

Produces an immutable audit log of who changed which configuration object (price, tax, permission, discount) at which location and when, exportable or queryable by corporate. differentiator

multi-location-config-audit-log

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

Supports SSO via SAML or OIDC against the customer's identity provider for back-office/above-store users, with SCIM or equivalent for automated deprovisioning. differentiator

multi-location-enterprise-sso

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

Publishes a documented multi-location API (or data warehouse/BI export) that returns transaction-level data across all locations in one authenticated call, without per-location credentials. differentiator

multi-location-enterprise-api

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

Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.

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

The POS software runs on commodity off-the-shelf hardware (standard iPads, Android tablets, or PCs) that the operator can buy from a third party, rather than only on vendor-supplied proprietary terminals. differentiator

hardware-commodity-devices

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

Vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs.

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

Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.

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

The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator

hardware-handheld-battery-swap

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

Terminals continue to take orders, print to kitchen, and record cash sales with the internet down, and the vendor documents explicitly which functions degrade (card auth, loyalty lookup, refunds).

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

Sells or supports a dedicated kitchen display system with bump-bar or touch input, station routing, and course/fire timing, as a first-party product rather than an integration-only dependency.

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

Offers a self-order kiosk running the same menu and modifier engine as the POS, in both countertop and freestanding form factors, with integrated payment and accessibility (ADA) compliance documented. differentiator

hardware-kiosk

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

Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, and speaker/headset integration, with a documented timer/speed-of-service measurement.

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

Works with standard ESC/POS thermal receipt and kitchen printers from more than one manufacturer (e.g. Epson and Star), including LAN/Ethernet printers, rather than only vendor-branded printers.

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

Supports the standard peripheral set — cash drawers (including multi-drawer per terminal), barcode scanners, scales for by-weight items, and customer-facing displays — with a published compatibility list.

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

Card entry happens on a PCI-listed PTS device using validated point-to-point encryption, so the POS application and tablet stay out of PCI scope; the vendor states the merchant's SAQ type.

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

Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. differentiator

hardware-tap-to-phone

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO NO, same instrument as payments-softpos-tap-to-pay. `Tap to Pay`, `softPOS` and `tap-to-phone` are each 0 across 11,269 sections. The eleven-device Genius Hardware catalogue (Aava 10 Tablet, Active Tab5, All In One Handheld with Moby5500, All in One Handheld iRoc Max with Moby 5500, GC26, GC26 Merchant-Facing Display, Kitchen N Series Nano, Moby 5500M, TD22, Verifone P400, XC23) carries no commodity-phone acceptance SKU, and the tablets in it (Aava 10, Galaxy Tab Active5) are documented with NFC as a hardware radio specification, never as a card-acceptance path. Contactless acceptance in every documented flow runs through a Moby5500 / Verifone P400 / GC26 reader. https://www.xenial.com/product-documentation/en/genius-hardware.html · retrieved 2026-09-12 adversarially verified

Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator

hardware-pricing-transparency

Upheld. No per-SKU hardware price is published on any Xenial property: `hardware price`, `starting at`, `msrp`, `buy now` and `add to cart` occur zero times across a 175-document corpus read 2026-09-09: an href fixpoint over www.xenial.com that closed at 181 URLs, the 86 sitemap entries that still resolve, and the four legal PDFs, including the Xenial Consolidated System Terms (3/2025) in English, Spanish and French-Canadian -- three renderings of ONE document, not three instruments, tokenised and as bare substrings alike, and the two live hardware pages (POS hardware, kiosk hardware and software) carry a Schedule a Demo call to action and no figure. The contract confirms the posture is deliberate rather than an omission: equipment is bought, leased or subscribed under the Sales Agreement per Section 5.1, and the only price the terms mention is a penalty reference -- Xenial may charge 'applicable late fees plus the list price of any replacement items' when equipment is not returned within forty-five days. So a list price for hardware exists inside the commercial relationship and is not published outside it. A word on the instrument, because the obvious one is a fossil: www.xenial.com/sitemap.xml lists 500 URLs, EVERY ONE stamped lastmod 2020-12-11, and 414 of them now 404 -- including 361 of the 364 product-documentation entries, which are .stml files from a site since rebuilt. A sitemap can be complete-looking and almost entirely dead, so this corpus rests on a live href fixpoint instead. docs.xenial.com, developer.xenial.com, wiki.xenial.com and status.xenial.com all fail DNS resolution. https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/ · retrieved 2026-09-09

Hardware can be purchased outright (owned) as an alternative to a mandatory lease or subscription-bundled rental, and the vendor states which. differentiator

hardware-ownership-vs-lease

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

Vendor documentation confirms whether hardware purchased from the vendor remains usable with other software after cancellation, i.e. it is not software-locked or remotely bricked. differentiator

hardware-usable-after-churn

The prior rationale said this was 'a commercial-terms question Xenial does not publish on www.xenial.com'. That is wrong: the published standard agreement allocates hardware ownership expressly, and the clauses below are cited nowhere in this record. REVISION CAUTION: the text read here is the 2023 revision of the Consolidated System Terms, recovered from a Wayback capture dated 2024-03-29; a later 3/2025 revision governs and is cited elsewhere in this record, but it holds no reading of these two clauses and www.xenial.com now returns 403 on /robots.txt to every client, so it cannot be re-fetched. Section numbering is known to drift between the two revisions, so the LANGUAGE below is the evidence and the section numbers are locators only. Product line: the Equipment terms are cross-product - Genius/Xenial Cloud POS terminals, kiosks and digital-menu-board media players all ship under them. PURCHASED equipment: Section 5.5 (Title; Risk of Loss) vests ownership in the customer at shipment - 'the title, risk and responsibility for all Equipment purchased by you under this Agreement shall transfer from Xenial to you upon shipment of the Equipment (i.e. FOB at the point of shipment)' - and no clause anywhere reserves Xenial a right to remotely disable or brick Equipment. LEASED equipment: Section 14.8 (End of Lease Term Buyout) gives a one-dollar buyout at the end of a sixty-month Lease Term. SHORTFALLS, which are why this is partial and not yes. (1) The contract settles TITLE, not CAPABILITY. No Xenial hardware page documents unlocked boot, OS reimaging or any third-party-software posture, and the live Genius Hardware book is closed to us. (2) On the lease-then-buyout path only, Section 14.8 reserves Xenial a right of access to strip FIRMWARE, not merely software, from a unit the customer now owns - 'Customer must allow Xenial the right to access such Equipment to remove any software, firmware, or other Xenial proprietary data or information from the relevant Equipment' - and the contract nowhere states the unit remains functional afterwards. This right is not stated for equipment purchased outright under Section 5.5. (3) Whether either clause survives into the 3/2025 revision is unverified. https://web.archive.org/web/20240329061233id_/https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/ · retrieved 2026-09-05 adversarially verified

Publishes a hardware warranty term and a replacement/advance-exchange SLA with a stated turnaround (e.g. next-business-day depot swap). differentiator

hardware-rma-sla

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

Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.

hardware-byod

Upheld. 'BYOD', 'personal device' and 'own phone' occur zero times in the corpus, and the two things it does document point opposite ways. For: Install Xenial Ordering (captured 2022-07-04) publishes an ordinary consumer install path - Google Play or the iTunes App Store, then login with credentials registered with the Xenial Portal - with no device-enrolment step, and the 2026-02-14 Genius Mobile Manager page says that app installs on iOS and Android devices; but Mobile Manager is reporting, not the ordering or payment app the claim names. Against: the same install topic ends by requiring the device to be selected from a site's terminal list and to 'Download Configuration Data', with Replace and Remove Terminal flows - a registered-terminal model, not a staff-owned-phone model - and no permission or security posture for staff-owned devices is published anywhere. Resolved by: a Genius topic stating whether staff may run the ordering or payment app on an unenrolled personal device, and under what role restrictions. || 324th: NEW SURFACE plus A POISON WARNING THAT MATTERS FOR THIS CELL. The complete 1,294-file script-loader fixpoint census of the live Genius configuration app dm.xenial.com adds no device-enrolment, personal-device or MDM surface. CRITICAL: a raw grep for 'BYOD' over that corpus returns 2 hits and BOTH ARE FALSE - the app ships an obfuscated i18n dictionary whose keys are base64-like tokens, and one key is literally "ByOd", whose VALUE is "HTML" (it labels the HTML receipt-template type). Any future pass that records a BYOD hit on a Xenial Angular bundle must tokenise and check the key/value orientation. Real controls: 'personal device' 0, 'own device' 0, 'enrol|enroll' 0 in a device sense. The cell stays unknown for the reason already recorded - the ordinary consumer install path is documented but a staff BYOD permission/security model is not published anywhere. Retrieved 2026-09-17. || 325th: NEW SURFACE, cell still unknown: over the 100%-fetched 293-topic Genius developer portal 'BYOD|personal device|own device' = 0, and the device model the portal does document is the opposite - the XPOS plugin and Device Bridge books require per-device setup on registered terminals ('set up OPUS on each device. Each peripheral device needs to be configured and working with the OPOS driver and utility individually. Make note of the logical device names (LDN) for each device'), and the Notification service reports 'the online/offline status of specific sites and terminals'. No staff-owned-device permission or security posture is published. Retrieved 2026-09-17. || 327th: 327th, THE 'byod' CONTROL IS ITSELF POISONED IN THIS CORPUS - a trap worth publishing. A case-insensitive '\bbyod\b' over 327th NEW COMBINED FIRST-PARTY FRONT-END CORPUS (nobody had run this cell against it): the 229 complete public source maps of FOUR Xenial SPAs already on disk (analytics.xenial.com, reports.xenial.com, xea.xenial.com, xvi.xenial.com; 118.9 MB) UNIONED with the 724 readable files of the closed 1,294-file script-loader fixpoint census of dm.xenial.com (Genius DataManagement, 49.5 MB) = 1,524 files / 168.3 MB of the vendor's own shipped code and i18n dictionaries. Denominator stated; these are BACK-OFFICE/analytics apps and by merge policy do not bound the store-level POS. returns 2 hits, both in dm.xenial.com's main.js, and both are an i18n HASH KEY, not the acronym: the enum reads e.HTML="ByOd" and the dictionary block confirms "ByOd":"HTML" (beside "I/sa":"Order Cancellation", "C9YJ":"Order Confirmation", "5fS1":"Use Default Template"). Xenial's i18n keys are random 4-5 character strings, so ANY short acronym control run over a Xenial bundle can collide with one; case-sensitivity is the only discriminator and 'BYOD' upper-case = 0. 'personal device' and 'own device' = 0 over all 1,524 files. Separately: the store-level Genius Android shell (com.xenial.shell.app 3.0.22, unpacked on disk) still enforces the registered-terminal model in its own strings - 'Select the Site for your location', 'Terminal Scheme:', 'Connected Devices:', 'Download Configuration Data for your location', 'Refresh Terminal' - with no personal-device path. Retrieved 2026-09-18. || 328th: 328th: NEW CORPUS - THE WEB ASSETS SHIPPED INSIDE XENIAL'S THREE ANDROID PACKAGES, which no prior pass had grepped (q312 read only the native strings and the Play listings). The packages have been on disk since q312: com.xenial.shell.app (the store-level device shell, assets/www is a self-contained 8.5 MB Angular app titled 'Genius Shell', 321 files, no network chunk loading - everything it runs is on disk), com.xenial.xbo (assets/public, Capacitor, the Back Office mobile app) and com.xenial.mobilemanager (assets/public, Capacitor). Unioned readable text = 1,781 files / 9,489,331 chars. Positive controls live: Xenial 128, terminal 153, order 391, payment 51. WHAT IT HOLDS FOR THIS CELL: case-sensitive 'BYOD' 0, tokenised 'byod' 0, 'personal device' 0, 'own device' 0, 'bring your own' 0 across all 1,781 files, which reproduces the registered-terminal model already recorded from the native strings, now over the shipped UI as well. Still unknown, not `no`: the shell is the device provisioning/launcher layer and the POS UI itself is downloaded to the terminal at runtime, so this corpus does not bound the POS application. POISON PUBLISHED for anyone re-testing acronyms against a Xenial corpus: `AOC` scores 2 and both are a DISPLAY-MANUFACTURER pattern table in Genius Shell main.js - {pattern:'^AOC.+', manufacturer:'AOC Monitors'} beside Sony/Acer/HP - and `royalty` scores 11, all of them the Apache-2.0 phrase 'no-charge, royalty-free' in mobilemanager's 3rdpartylicenses.txt. Retrieved 2026-09-18. || 332nd: 332nd NEW SURFACE: Global Payments' own Genius Enterprise product pages under www.globalpayments.com/point-of-sale/enterprise/ (enterprise-pos, back-office, kitchen-management, kiosk, digital-menu-board, drive-thru, food-service-management) plus the umbrella /genius page. Live host is a Cloudflare 403 to curl with full browser + Sec-Fetch headers and to WebFetch (a refusal, not an absence), so read via Wayback id_ captures 2025-09-09..2026-05-27 (never cited by any prior pass). Genius Enterprise POS page (Wayback 20250909011533): 'Run Genius Enterprise POS on virtually any device or operating system ... Any operating system Works on iOS, Android, Windows and Linux Your hardware or ours* Compatible with rugged terminals and lightweight tablets' with footnote '*Minimum standards apply for devices.' That is OPERATOR-owned hardware eligibility, not staff personal phones, and no enrolment/permission/security model for a personal device is stated ('BYOD' 0 and 'own device(s)' 0 across the 8 pages; 'personal' scores 8 and ALL 8 are the footer link 'Do not sell and share my personal information' - POISON). Adjacent, not a partial. Retrieved 2026-09-18. || 333rd: 333rd VIDEO CENSUS (new surface type for this record): Global Payments' YouTube channel 'Genius by Global Payments' (@GeniusPOS, 143 uploads listed by yt-dlp --flat-playlist; POISON: @Xenial is an unrelated gaming channel) and Nextep's legacy channel (@NextepSystems, 19 uploads), plus the Global Payments Vidyard hub videos.globalpayments.com (Cloudflare 403 live; its 6 Wayback-known player ids read via play.vidyard.com/player/<id>.json, 5 with English VTT captions: 'Stadium Capabilities', 'Meet Genius', 'Introducing Genius for Retail', 'Commerce Made Easy', 'Brand Launch'). YouTube caption tracks returned 429 to both youtube-transcript-api and timedtext, so only titles, descriptions and 1080p frames were read. Also NEW: Global Payments' own Genius hardware catalogue www.globalpayments.com/point-of-sale/hardware (Wayback id_ 20260527, gzip body, 13,497 chars stripped; live host Cloudflare 403) enumerates vendor-supplied devices only: Countertop (15.6-inch modular), Handheld ('Compact, rugged ... 8+ hours of battery'), Kitchen management (KDS monitor, screen connector, bump bar), Kiosk (27-inch, 22-inch, grab-and-go), Displays, Drive thru. 'personal device|own phone|BYOD|bring your own' = 0 on it. POISON for this cell: www.globalpayments.com/point-of-sale/mobile (Wayback 20250524) says 'You can accept card payments ... on your personal device (Android and iOS)', but it is the generic small-business mobile-payments page ('businesses that don't have a complex offering or inventory'), not Genius Enterprise POS, and it describes payment acceptance, not the staff ordering app. The 'Power your enterprise business with Genius' video (7D-2FNrb9Nk, 65 s, 26 frames read at 1080p) shows only vendor countertop, KDS and kiosk hardware. A hardware catalogue does not bound whether the app runs on a staff phone, so still unknown. Retrieved 2026-09-18. || 334th: 334th NEW SURFACE: the App Store PUBLISHER census for Xenial (itunes lookup?id=1455368071&entity=software = 4 apps: Xenial Shell com.xenial.shell.app, Genius Mobile Manager, Genius Back Office Mobile, and Genius Team Portal Mobile io.genius.tp.mobile.app, the last NEW since the 328th: released 2025-11-04, an employee schedule/time-off/shift-swap app); all four list 48 iPhone models as supported. Xenial Shell: 'enterprise power made smartphone easy ... You also get to load Xenial on as many devices to run your store for that single price' - OPERATOR devices without per-terminal fees, no staff-owned-device permission or security model. Genius Team Portal Mobile is the one app meant for an employee's own phone, and it is scheduling/time-off, not ordering or payment. Press release 509 (2026-05-12) introduces a vendor-supplied 'AI-first Genius handheld'. Tokenised 'BYOD|own phone|own device|personal device' = 0 over the 4 listings and the 218 press releases. Adjacent, still unknown. Retrieved 2026-09-18. adversarially verified

Provides a remote device-management console showing each terminal, printer, and KDS as online/offline, with remote reboot, software-version visibility, and staged rollout of updates. differentiator

hardware-remote-device-management

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

Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.

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

API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator

extensibility-api-access-cost

Upheld, and deliberately not filled from this corpus. The earlier pass read /developer-resources/en/ LIVE (293 pages / 3,333 sections, 2026-08-08) and found the API gate stated in legal and relational terms rather than priced - completed NDA and Developer Licensing Agreement, account-manager confirmation, an integrator-issued token. My Wayback corpus is the 2021-2023 pre-Genius tree and contains none of those paths, so on this cell it is a strict subset and cannot improve on that. Re-reading the contract explains why it cannot help either: Section 5.1 defines Fees wholly by reference to an unpublished order form ('you shall pay to us the fees and other amounts set forth in the Sales Agreement'), and the Schedules/Exhibits index names the Support Services Price List and the Site Readiness Specifications as 'Provided Separately'. Schedule A makes every Service conditional on appearing in that Sales Agreement, and two of its enumerated Services - the Loyalty Module and the Mobile Ordering Module - are third-party integration GATEWAYS sold as separate line items 'Subject to Customers payment of all applicable Fees', which leans toward integration surfaces being priced rather than bundled; but those are pre-built partner connectors, not the developer API, so this is inference, not the positive statement a no requires. Resolvable by the Support Services Price List, an executed Sales Agreement, or a Genius developer-portal pricing page - all now unreachable, since www.xenial.com answers 403 on /robots.txt to every client and the repo's scope proof fails. || 325th: NEW MEASUREMENT, cell still unknown; the note's claim that this surface is unreachable is STALE (all 293 developer-portal topics fetched at 200 on 2026-09-17; only /robots.txt 403s). The access gate is documented and relational, not priced: every API book opens with the same steps - 'Getting Started with APIs. Steps to obtain an integrator token', 'Confidentiality Statement. Information about our non-disclosure agreement (NDA) terms and conditions regarding endpoints', 'API Prerequisites' - integrator tokens are issued per company (getting-an-integrator-token.html, getting-a-company-integrator-token.html), and voice-command and Menu Engine configuration explicitly require 'the help of a your account manager'. Over the whole 293-topic corpus no fee, surcharge, tier or per-location charge for API access appears (the 'fee'/'pricing'/'cost' hits are the Fee Definition object, Pricing Menu and Inventory Item Cost). Contract silence delegated to an unpublished Sales Agreement plus documentation silence is still not the positive statement a `no` needs. Retrieved 2026-09-17. || 326th: NEW MEASUREMENT (326th), cell still unknown, recorded so the route is not re-run a fourth time. The ssr.xenial.com Simple Service Registry route is now EXHAUSTED: the 325th probed 71 production hosts drawn from the registry against 7 spec paths each (/swagger/index.html, /swagger/v1/swagger.json, /swagger.json, /openapi.json, /v3/api-docs, /api-docs, /q/openapi) - 498 responses, and re-reading every one of them by size shows that not a single body is a specification. The largest four (142,163 B, log-readerbackend.xenial.com) are one identical Next.js HTML shell returned for all four paths; reports.xenial.com returns the same 26,912-byte 'Xenial Reporting' shell for all four; record-and-play.xenial.com the same 16,503-byte Angular shell. Every one is a soft-200 catch-all, so there is no anonymous Xenial OpenAPI document to price access against, and the gate remains what the developer portal states in legal rather than priced terms (NDA + Developer Licensing Agreement + account-manager confirmation). Retrieved 2026-09-18. || 327th: 327th, TWO CANDIDATE DEVELOPER-PORTAL HOSTS FOUND AND BOTH ELIMINATED. Certificate transparency on xenial.cloud and heartlandcommerce.com (185 names, first time either domain was enumerated) surfaced developer.xenial.cloud and portal.xenial.cloud. Both are dead at DNS (NXDOMAIN); the single archived 200 of developer.xenial.cloud (2024-09-04) is 'Aether Developer Docs', an MSP analytics initiative, not Xenial's restaurant API - so it cannot carry a price or a free-access statement either way. help.xenial.com, support.xenial.com and docs.xenial.com are all NXDOMAIN; www.xenial.com/developer-resources/en/index-en.html remains the only developer surface and is unchanged (200, 169,658 B), so the NDA + Developer Licensing Agreement + account-manager gate already in the record is still the whole published story and is stated in legal, not priced, terms. Retrieved 2026-09-18. || 332nd: 332nd NEW SURFACE: Global Payments' own Genius Enterprise product pages under www.globalpayments.com/point-of-sale/enterprise/ (enterprise-pos, back-office, kitchen-management, kiosk, digital-menu-board, drive-thru, food-service-management) plus the umbrella /genius page. Live host is a Cloudflare 403 to curl with full browser + Sec-Fetch headers and to WebFetch (a refusal, not an absence), so read via Wayback id_ captures 2025-09-09..2026-05-27 (never cited by any prior pass). NEW: Genius Back Office page (Wayback 20250909011610): 'API-driven data streams (via our Data Stream add-on) to power third party BI dashboards' - the vendor packages its outbound data API (Data Stream webhooks, developer-resources data-stream-429470.html) as an add-on. The Enterprise POS page speaks only of 'robust APIs to connect with kitchen automation, loyalty programs and enterprise IT systems' and 'custom APIs' (kitchen-management), with no price. No fee, per-location surcharge or tier is stated anywhere on the 8 pages (the 4 word-boundary 'fee(s)' hits are card-processing/surcharge FAQ text on /genius), so an add-on noun cannot carry `no` (329th rule), but it weighs against `yes`. Held unknown. Retrieved 2026-09-18. || 334th: 334th NEW SURFACE: the App Store PUBLISHER census for Xenial (itunes lookup?id=1455368071&entity=software = 4 apps: Xenial Shell com.xenial.shell.app, Genius Mobile Manager, Genius Back Office Mobile, and Genius Team Portal Mobile io.genius.tp.mobile.app, the last NEW since the 328th: released 2025-11-04, an employee schedule/time-off/shift-swap app). The Xenial Shell listing (vendor-written, current version 2.2.150 of 2025-09-10, 'Xenial (now Genius)') is the only first-party text found that ENUMERATES plan contents: 'monthly subscription ... per store location. With the basic subscription plan you get: Ordering, Dynamic menus, Localized sales tax engine, Reporting, Time clock, Payment connection, Payroll connection. For a little more each, monthly - you can add: Kitchen management, Scheduling, Inventory, Instant data & alerts, Manager log & tasks, B2C CRM, Stored value, Loyalty, Customer engagement, Email campaigns, Single-use coupons.' API / integration access appears in NEITHER list ('API' 0 in the listing), so the enumeration is silent on this claim; it is also the 2017 Xenial SMB pricing text carried forward, not the Genius Enterprise commercial model. Press-release census (218 Global Payments press releases (investors.globalpayments.com/news-events/press-releases, ?page=1..22 until empty, every detail page fetched 200 on 2026-09-18, 2.15 M chars of release text; 23 of them name Genius or Xenial, incl. 122 Xenial launch 2017, 473 Genius platform 2025-05-16, 486 Genius for Enterprise 2025-09-10, 490 higher education, 495 Uber Eats partnership 2025-11-18, 509 AI-first handheld 2026-05-12, 515 Genius World 2026-08-24)): 'API' 4 hits, none about Genius/Xenial API pricing (EdgeExpress, Google, Heartland terminal). Held unknown. Retrieved 2026-09-18. adversarially verified

The vendor publishes its partner/marketplace commercial terms (referral fee, revenue share percentage, or per-location partner fee) in public documentation.

extensibility-partner-revshare

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO NO. This is a publication claim, so a zero over the publisher’s own complete corpus settles it. The Integration Partners List - published identically in Product Documentation and Developer Resources - opens 'Genius partners with the following integrators for these products' and then names about fifty partners across eleven product categories with no commercial term attached to any of them. Across the whole 11,269-section corpus, including the 3,337-section Developer Resources publication: `revenue share` 0, `referral fee` 0, `partner program` 0, `certification fee` 0, `per-location fee` 0. The prior pass had already read the Consolidated System Terms end to end and found none there either. Xenial publishes who it integrates with and does not publish what that costs. https://www.xenial.com/product-documentation/en/genius-integration-partners.html · retrieved 2026-09-12 adversarially verified

A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator

extensibility-free-sandbox

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

Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).

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

The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.

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

Webhooks are cryptographically signed (e.g. HMAC) AND documented to retry with backoff, with a replayable event log for missed deliveries. differentiator

extensibility-webhook-reliability

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

A public write API accepts externally originated orders into the POS as first-class tickets that fire to KDS/printers and land in reporting.

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

Menu items, modifiers, and prices can be written and updated via API, not just read. differentiator

extensibility-menu-write-api

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

Every core object the API can read (orders, menu, customers, employees, inventory) can also be written or updated via the same API. differentiator

extensibility-data-symmetry

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

API rate limits are published as specific numeric quotas with documented throttling behavior and headers.

extensibility-published-rate-limits

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO PARTIAL, and it corrects a premise the standing rationale asserted. That rationale said the API reference enumerates 'response codes enumerated per endpoint without 429'. That is now false: Genius Kitchen GET /settings publishes a 429 row reading 'Error happened when the current terminal received too many requests from the same IP. The response contains the next header with information of the next new open window for requests', and names the header as Retry-After in milliseconds. So throttling behaviour and the header ARE documented, and the 2025 March Feature Highlight confirms the mechanism exists - 'Implemented a metering and throttling threshold' on Cloud Portal servers, with a gatekeeper_header environment variable. SHORTFALL, which is why this is partial and not yes: no numeric quota is published anywhere. `quota` 0, `requests per second` 0, `requests per minute` 0 across all 11,269 sections; `rate limit` matches 2 documents, both Portal release notes with no figure; and the 429 + Retry-After documentation covers exactly ONE endpoint out of the 3,337-section Developer Resources publication - `Too Many Requests` occurs in 1 document only. A reader cannot learn what the limits are, only that they exist. https://www.xenial.com/developer-resources/en/operation-definitions-763028.html · retrieved 2026-09-12 adversarially verified

The vendor is a named DoorDash Preferred Integration Partner (DPIP) under the 2026 program requirements. differentiator

extensibility-doordash-preferred

DoorDash publishes its own complete provider registry at https://merchants.doordash.com/api/partner-integrations — 64 providers, each carrying a `qualityStatus` of PREFERRED (12), CERTIFIED (47) or AT_RISK_OF_SUSPENSION (5), plus a features-completed count against the eight high-quality features the program requires. It is served anonymously and merchants.doordash.com/robots.txt permits it (Allow: / with only /cdn-cgi/ and /monitoring barred). This is the instrument the program page points to when it says the roster is tracked in real time, and it supersedes the 2026 announcement post most of this corpus cited — that post introduces its ten names with the word `include`, which makes it a floor, not a ceiling. In that registry this vendor is the entry `xenial`, rendered as 'Xenial', with qualityStatus CERTIFIED and 4 of the 8 high-quality features built. CERTIFIED and AT_RISK are the program's other two tiers, so this is positive evidence of non-membership rather than a failure to find the vendor: it is present in the registry and carries a status that is not PREFERRED. GRADE HARMONISED TO B, 2026-09-11: this URL was first written at grade A. The adversarial pass ruled E on the principle that the rubric grades by the publisher's relationship to the SCORED vendor, and DoorDash is not that vendor. B is the settlement, for two reasons that are not preference: 39 rows already graded a DoorDash-published document B on this claim before today, and one URL on one claim cannot carry two grades; and E is unworkable, because nine of the 47 rows are `yes` on a differentiator-weight claim, which the grade floor refuses below B. B reads as the product documentation of the programme's own publisher, which is what this registry is. The dissent is recorded in verification.jsonl. https://merchants.doordash.com/api/partner-integrations · retrieved 2026-09-11

Direct, first-party certified integrations exist with DoorDash, Uber Eats, and Grubhub without requiring a paid middleware layer (Otter/Chowly/Deliverect/Checkmate). differentiator

extensibility-first-party-delivery-integrations

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

The POS is a supported endpoint for at least two major aggregation middleware platforms (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate).

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

Native, vendor-maintained connectors exist for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export.

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

Labor hours export natively to at least two named payroll providers (e.g. Gusto, ADP, Paychex, Paylocity) without manual re-keying.

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

Raw transaction-level data can be exported on a schedule to a customer-controlled destination (S3/SFTP/warehouse/Snowflake share), not only viewed in the vendor's reporting UI. differentiator

extensibility-bi-data-warehouse

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

The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.

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

Operators can define custom fields or run vendor-hosted custom logic/scripts against POS objects without a vendor engineering engagement.

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

The vendor supports a headless/embedded mode where a third-party UI (kiosk, web ordering, drive-thru) drives the POS transaction engine via API.

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

The vendor publishes an API changelog and a stated deprecation/notice policy for breaking changes.

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

A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator

extensibility-data-portability-exit

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

Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.

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

Card payments can be accepted while offline via store-and-forward, not just cash-only fallback. differentiator

reliability-offline-card-auth

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

The vendor publicly documents who bears the loss when a store-and-forward transaction declines after connectivity returns, and states any per-transaction or cumulative offline cap. differentiator

reliability-offline-decline-liability

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

Multiple terminals continue to share a single check/table state over the local network while the internet is down (LAN-only degraded operation, not per-terminal islands). differentiator

reliability-lan-degraded-multi-terminal

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

The vendor documents a local/on-premise transaction engine or edge server (not purely cloud-hosted request/response) for the ordering path. differentiator

reliability-local-transaction-engine

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

Kitchen display and/or kitchen printer routing continues to function while offline.

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

The system automatically fails over to a backup printer or KDS station when a configured kitchen printer is unreachable, and alerts staff.

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

The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).

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

The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).

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

A public, per-component status page exists showing current and historical incident state without a login.

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

A contractual uptime SLA with a stated percentage AND a service credit remedy is published or available in the standard agreement. differentiator

reliability-contractual-uptime-sla

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

The vendor publishes written post-incident reports or root-cause summaries for major outages.

reliability-incident-postmortems

DOWNGRADED FROM `no` BY THE ADVERSARIAL PASS, 2026-09-12. The instrument is sound and I reproduced it: the three Paligo fuzzydata.min.js search indexes are a page-level CENSUS of xenial.com’s three documentation portals (11,269 sections over 1,274 pages, a strict superset of the portals’ own index-en.html contents at 1,267, diffed both ways), and I re-fetched all 1,274 pages at HTTP 200 and confirmed every asserted zero on that second instrument. But the sentence the `no` rested on - “There is no published venue in which a post-incident report could appear” - is FALSE. xenial.statuspage.io is a live Statuspage titled “Xenial Status”: every path on it, including /api/v2/status.json, /api/v2/incidents.json and /history.atom, returns HTTP 200 after redirecting to https://xenial.statuspage.io/access/login, i.e. it is an audience-restricted status page, not an absent one (its robots.txt is three lines and bars only /api/ and /embed/). globalpayments.statuspage.io likewise redirects into a Global Payments SSO login. The venue therefore exists and its contents are unmeasurable to us, so whether Xenial publishes written post-incident reports or root-cause summaries inside it cannot be settled from outside. The prior pass probed status.xenial.com (TLS name mismatch), status.globalpay.com and trust.globalpayments.com (both NXDOMAIN) but never probed statuspage.io. Everything else in the resolved note survives: `postmortem`, `post-incident`, `root cause analysis`, `SLA` and `service level` are each 0 across 11,269 sections and across the 1,274 re-fetched pages, and the Contact Support publication names five channels (SMS, WebChat, Web-to-Case, Phone, Email) and no status page. Unknown, not no - a login wall is not an absence. || 324th: NEW SURFACE, and it is a DEAD one - which is the point the standing note could not test. The sentence the withdrawn `no` rested on was that there is no published venue for a post-incident report; the Paligo doc census could not see outside xenial.com. Certificate transparency (https://crt.sh/?q=%25.xenial.com&output=json, 393 distinct names) shows Xenial did provision `status.xenial.com`, and it still resolves (104.192.142.21). It no longer serves a status page: https:// fails TLS with SEC_E_WRONG_PRINCIPAL (the Statuspage certificate no longer covers the name) and http://status.xenial.com/ 302s to https://www.statuspage.io, which 301s to Atlassian's own marketing page - i.e. the Statuspage tenant is deprovisioned and the CNAME is dangling. Its API (/api/v2/summary.json) is unreachable for the same reason. So Xenial's only ever status/incident venue is retired rather than merely absent. Held unknown, not `no`: a retired venue does not prove customers receive no RCA through the account channel, and enterprise post-mortems are routinely delivered under NDA. Also re-probed from the service registry: `XSSM Site Status Monitor` (xssm.xenial.com) and `XSSN Xenial Site Status Notifier` are STORE-level monitoring services, not a public trust page. Retrieved 2026-09-17. || 325th: NEW SURFACE, cell still unknown. The current Contact Support publication in the developer portal enumerates the support channels and still names no status page or incident venue (Web-to-Case / support-request; 'Phone. Emergency issues or complex items where mobility is required and dialogue is best suited for voice-to-voice contact. Example: Issues with network cables, credit card processing, or offline equipment. 1-800-547-4266'; Email; WebChat). Over the 100%-fetched 293-topic corpus 'post-mortem|post-incident|root cause' returns 1 hit and it is not an RCA publication. Xenial's site-status services (XSSM Site Status Monitor, XSSN Site Status Notifier) and the Notification API's Site Online / Site Offline events are per-store monitoring delivered to integrators, not a public incident record. Retrieved 2026-09-17. || 326th: NEW MEASUREMENT (326th), cell still unknown, and it CORRECTS the 324th's reading. The 324th concluded from status.xenial.com (TLS SEC_E_WRONG_PRINCIPAL, http 302 to www.statuspage.io) that 'the Statuspage tenant is deprovisioned and the CNAME is dangling'. That is true of the custom domain only. The tenant ITSELF is alive and private: curl with a browser UA gets 302 -> https://xenial.statuspage.io/access/login on the root and on every API path (/api/v2/summary.json, /api/v2/incidents.json, /api/v2/status.json, /api/v2/components.json, /history.atom, /history.json all 302 to the same login), and the login page returns 200 with <title>Xenial Status - Login</title>. NONSENSE CONTROL: /zzz-nonsense-path returns a bare 404 with 0 bytes, so the 302 is a real audience restriction and not a catch-all. So the venue exists, is Xenial's, and publishes nothing publicly - a login wall, still not an absence, so the cell stays unknown rather than moving to `no`. POISON FOUND AND NAMED: https://genius.statuspage.io/api/v2/summary.json answers 200 anonymously and would be an easy false positive for the Genius brand, but its page.name is 'Genius Inc', its time_zone is 'Asia/Tokyo' and its components are 'Standalone Games for Android' - a different publisher entirely, with 0 incidents. Do not cite it. Retrieved 2026-09-18. || 332nd: 332nd NEW SURFACE: Global Payments' own Genius Enterprise product pages under www.globalpayments.com/point-of-sale/enterprise/ (enterprise-pos, back-office, kitchen-management, kiosk, digital-menu-board, drive-thru, food-service-management) plus the umbrella /genius page. Live host is a Cloudflare 403 to curl with full browser + Sec-Fetch headers and to WebFetch (a refusal, not an absence), so read via Wayback id_ captures 2025-09-09..2026-05-27 (never cited by any prior pass). 'postmortem|post-incident|root cause|incident report' 0 and 'status page' 0 across the 8 pages; the only reliability language is Back Office 'ensures uptime, reliability and flexibility' and FSM 'Real-time device health monitoring'. The reseller site's 'Proactive Monitoring Real-time alerts and uptime transparency' (geniusforenterprise.com/support-7402) is third-party marketing and names no venue. Global Payments 2024/2025 Global Responsibility Reports: 'post-incident' 0, 'root cause' 0; the board 'is also apprised directly of incidents as appropriate, pursuant to our incident response plan' (internal, not published). 332nd: POISON NAMED for the whole record - geniusforenterprise.com (cited in product.yaml as a vendor domain) is NOT Global Payments': every page footer reads 'An Authorized Reseller of Global Payments ... JCR Systems is an independent authorized reseller. Powered by CT.Marketing' (LeadConnector/GoHighLevel funnel, 10 pages, nonsense path = soft-200 homepage). Anything on it is third-party grade D. Retrieved 2026-09-18. || 334th: 334th NEW SURFACE: 218 Global Payments press releases (investors.globalpayments.com/news-events/press-releases, ?page=1..22 until empty, every detail page fetched 200 on 2026-09-18, 2.15 M chars of release text; 23 of them name Genius or Xenial, incl. 122 Xenial launch 2017, 473 Genius platform 2025-05-16, 486 Genius for Enterprise 2025-09-10, 490 higher education, 495 Uber Eats partnership 2025-11-18, 509 AI-first handheld 2026-05-12, 515 Genius World 2026-08-24). 'post-incident|postmortem|root cause|outage' = 0 across all 218. The status venue remains the login-restricted xenial.statuspage.io, so held unknown. Retrieved 2026-09-18. adversarially verified

24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.

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

The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator

reliability-onsite-install

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

The vendor performs the initial menu build as part of onboarding rather than leaving it entirely to the operator. differentiator

reliability-menu-build-service

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

A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.

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

Operators can trigger and retrieve their own data backup/restore, or the vendor publishes RPO/RTO figures for data recovery.

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

The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.

reliability-pci-dss-4-attestation

331st: NEW SURFACE, and it supplies the listing the adversarial pass said was missing. CLAIM: the vendor publishes a current PCI DSS v4.0/4.0.1 AoC OR EQUIVALENT (the claim's own example: 'validated P2PE listing'). VERDICT: partial/B. EVIDENCE: (1) First-party, Xenial's 2026 January Feature Highlight (cited URL, re-fetched today, 225,437 B), PRMA-6397 Genius USB Connection Type Integration - Phase 2: 'Enabled USB serial communication to the Genius/GPI Payment System' followed, as the next list item, by 'USB ecosystem system is PCI validated P2PE to so data coming from the GPI Payment System is not considered PCI data' (two separate list items; typography as published). (2) The listing that sentence refers to EXISTS and is CURRENT on the PCI SSC's own register (https://www.pcisecuritystandards.org/assessors_and_solutions/point_to_point_encryption_solutions/ ; the register loads by the page's public listing call, admin-ajax action get_p2pe_solutions_data, status=Valid: 136 valid solutions, status=Expired: 59, saved as p2pe-sol-Valid.json / p2pe-sol-Expired.json): solution 804 'Genius Smart P2PE', company 'Global Payments Direct, Inc.' (Xenial's parent), reference 2024-00056.012, standard 'P2PE v3.1', assessor 'Coalfire Systems, Inc', annual revalidation 2027-07-25, reassessment 2027-07-25, status valid; its P2PE application is 'Genius' 6.5.*.* (ref 2025-00056.010, revalidation 2027-04-23), its components include 'Global Payments US KIF' (2024-00056.006) and Verifone VRK, and its current POI devices are Verifone P400/P400 Plus/P400 DMSR (4-10239), M400, V400m and e285 - the P400 being a device Xenial's own Genius Hardware catalogue sells (see hardware-p2pe-terminal). So the 'Genius/GPI Payment System' Xenial names is a PCI-listed, currently validated P2PE v3.1 solution of its parent, which is the equivalent the claim names. SHORTFALL (why not yes): Xenial itself publishes no AoC and no listing reference number - the link from its sentence to solution 804 is by product name (Genius) and owner (GPI = Global Payments Inc.); the listing covers only the Genius payment path and its listed Verifone devices - the Moby/5500 that Xenial's hardware catalogue also sells appears on NO Global Payments P2PE listing (it is listed only under Bluefin, FreedomPay, First Data TransArmor, IXOPAY/TokenEx, Worldline Ingenico One and Worldpay); and nothing covers the Xenial POS/cloud's own PCI DSS 4.0.1 scope. The listing also carries display flag 'dependency_min_anniversary_date_expired' (older Mx915/Mx925/WSX POIs expired 2021/2024 remain attached). CONTROLS: Visa Global Registry of Service Providers company search (GET https://www.visa.com/splisting/api/company?companyName=Xenial) returns data [] for 'Xenial' and 'Genius'; Heartland and 'Global Payments Direct, Inc.' ARE registered there, so Xenial is not a separately registered PCI DSS service provider. Retrieved 2026-09-18. https://www.xenial.com/release-notes/en/feature-highlights/previous-feature-highlights/2026-january---feature-highlights.html · retrieved 2026-09-18 adversarially verified

Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.

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

A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.

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

Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. differentiator

reliability-failover-terminal-role

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

Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.

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

Vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core POS software tier. differentiator

commercial-month-to-month-contract

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

Vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. differentiator

commercial-no-early-termination-fee

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

The auto-renewal term and the required cancellation notice window (e.g. 30/60/90 days) are stated in publicly accessible contract terms rather than only in a signed quote.

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

The POS software can be purchased and operated with a third-party payment processor of the operator's choice (no mandatory in-house processing lock). differentiator

commercial-processing-not-bundled

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

Vendor publishes an interchange-plus (cost-plus) processing rate option with the markup stated as a specific bps + per-transaction figure, rather than only blended/flat card-present rates. differentiator

commercial-interchange-plus-published

Upheld. The claim requires an interchange-plus option with the markup stated as a specific bps plus per-transaction figure, and Xenial publishes no rate of any structure at all -- not interchange-plus, not blended, not a flat card rate. `interchange`, `interchange plus`, `basis points`, `bps`, `discount rate` and `processing rate` occur zero times across a 175-document corpus read 2026-09-09: an href fixpoint over www.xenial.com that closed at 181 URLs, the 86 sitemap entries that still resolve, and the four legal PDFs, including the Xenial Consolidated System Terms (3/2025) in English, Spanish and French-Canadian -- three renderings of ONE document, not three instruments, tokenised and as bare substrings alike, including across the whole English text of the Consolidated System Terms. Nothing in the corpus even establishes Xenial as the acquirer for card-present transactions; the terms disclaim payment processing for the mobile-ordering path entirely. A claim about the SHAPE of a published markup cannot be met by a vendor that publishes no markup. A word on the instrument, because the obvious one is a fossil: www.xenial.com/sitemap.xml lists 500 URLs, EVERY ONE stamped lastmod 2020-12-11, and 414 of them now 404 -- including 361 of the 364 product-documentation entries, which are .stml files from a site since rebuilt. A sitemap can be complete-looking and almost entirely dead, so this corpus rests on a live href fixpoint instead. docs.xenial.com, developer.xenial.com, wiki.xenial.com and status.xenial.com all fail DNS resolution. https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/ · retrieved 2026-09-09

The processing agreement caps or prohibits unilateral vendor-initiated rate increases outside of pass-through interchange/network changes, or grants penalty-free exit on any increase. differentiator

commercial-rate-increase-clause

CITATION RE-HOMED ONTO THE GOVERNING REVISION. Xenial's published standard agreement - Consolidated System Terms and Conditions (3/2025), linked from the site footer and already cited nine times in this record at retrieved 2026-08-08 - reserves unilateral repricing without cap and grants no exit on an increase. From the 3/2025 text: subscriptions and Support renew at Global's 'then-current Fees' (4.1.2, 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'. Nothing caps an increase, indexes it, or limits it to pass-through cost. NOR IS THERE PENALTY-FREE EXIT: Section 4.2 gives the operator a for-cause exit only (thirty days on an uncured material breach, or insolvency); the only other escape is ordinary non-renewal on sixty days' notice before term end against a five-year default Initial Subscription Term (4.1.2); and Section 4.4 makes all Fees non-cancellable and all amounts non-refundable, with acceleration of the remaining balance if Global terminates. No clause anywhere makes a price change a termination trigger. CORROBORATION FROM AN EARLIER REVISION, cited as colour and not as load: the 2023 revision of the same document, recovered at https://web.archive.org/web/20240329061233id_/https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/ , states the same right in one sentence at Section 5.1 (Fees) - 'We reserve the right to change the Fees and to institute new charges and Fees at the end of the initial Subscription Term or Support Term or then-current renewal Term, as applicable, upon thirty (30) days prior written notice to you (which may be sent by email)'. Section 5.1 of the 3/2025 revision was read on 2026-08-08 and carries the same billing-error sentence that immediately follows this one in the 2023 text, so 5.1 is the Fees clause in both revisions. ANALYST INFERENCE, LABELLED AS SUCH: because notice of a renewal-term increase need arrive only thirty days out while non-renewal notice is due sixty days out, the opt-out window can close before the new price is disclosed. That is a reading of two clauses, not a quoted statement, and the verdict does not rest on it. SCOPE, STATED PLAINLY: this is the Equipment and Software agreement. The Global Payments card-processing agreement governing discount rates and interchange pass-through is not published on any Xenial property - the contract has zero occurrences of 'interchange' or 'Card Brand' - so this no is established for software, support and hardware fees and is untested for card-processing rates. https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/index.pdf · retrieved 2026-08-08 adversarially verified

Per-location and per-additional-terminal software pricing is published as specific dollar figures on the vendor's public site (not 'contact sales' only).

commercial-pricing-published

Upheld, and the vendor's own contract now says why rather than us inferring it from an empty pricing page. Section 5.1 of the Consolidated System Terms makes every number bilateral: 'you shall pay to us the fees and other amounts set forth in the Sales Agreement ("Fees") in the manner specified in the Sales Agreement.' Xenial goes further and confirms that a price list EXISTS and is deliberately withheld -- late fees 'are set forth in the Support Services Price List provided to you separately'. Across a 175-document corpus read 2026-09-09: an href fixpoint over www.xenial.com that closed at 181 URLs, the 86 sitemap entries that still resolve, and the four legal PDFs, including the Xenial Consolidated System Terms (3/2025) in English, Spanish and French-Canadian -- three renderings of ONE document, not three instruments, `per location`, `per seat`, `subscription fee` and `msrp` occur zero times, tokenised and as bare substrings alike, and no dollar figure for software appears anywhere. One correction to the old rationale: it said all paths route to Book a Demo. That exact phrase, `book a demo`, reads ZERO in the corpus -- the vendor's wording is Schedule a Demo, which reads 228 times across 151 documents, with Contact Us at 209 and Request a Demo at 11. The conclusion is unchanged but a control has to match the vendor's spelling. A word on the instrument, because the obvious one is a fossil: www.xenial.com/sitemap.xml lists 500 URLs, EVERY ONE stamped lastmod 2020-12-11, and 414 of them now 404 -- including 361 of the 364 product-documentation entries, which are .stml files from a site since rebuilt. A sitemap can be complete-looking and almost entirely dead, so this corpus rests on a live href fixpoint instead. docs.xenial.com, developer.xenial.com, wiki.xenial.com and status.xenial.com all fail DNS resolution. https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/ · retrieved 2026-09-09

Individual modules (online ordering, KDS, loyalty, inventory, payroll, marketing) can be purchased à la carte and cancelled independently without repricing the base POS subscription. differentiator

commercial-module-unbundling

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

All required terminals, KDS screens, and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental.

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

Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator

commercial-hardware-not-locked

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

One-time implementation, menu-build, onboarding, and training fees are published as specific amounts or explicitly stated as $0.

commercial-implementation-fee-published

Upheld, and the contract shows these fees are a named, chargeable category rather than something Xenial simply never mentions. The Consolidated System Terms define Implementation Services as 'your purchase or lease of installation, implementation, training, and other services related to the initiation of the System', and place them, like everything else, in the bilateral document: 'in each case as applicable as specified in the Sales Agreement'. So installation, implementation and training are all billable and all quote-only. Across a 175-document corpus read 2026-09-09: an href fixpoint over www.xenial.com that closed at 181 URLs, the 86 sitemap entries that still resolve, and the four legal PDFs, including the Xenial Consolidated System Terms (3/2025) in English, Spanish and French-Canadian -- three renderings of ONE document, not three instruments, `implementation fee`, `installation fee`, `setup fee`, `onboarding fee`, `training fee`, `no setup`, `one-time fee` and `activation fee` occur zero times, tokenised and as bare substrings alike -- no amount is published and none is stated as $0. `menu build` reads once, in the product-documentation index, as a task name and not a price. A word on the instrument, because the obvious one is a fossil: www.xenial.com/sitemap.xml lists 500 URLs, EVERY ONE stamped lastmod 2020-12-11, and 414 of them now 404 -- including 361 of the 364 product-documentation entries, which are .stml files from a site since rebuilt. A sitemap can be complete-looking and almost entirely dead, so this corpus rests on a live href fixpoint instead. docs.xenial.com, developer.xenial.com, wiki.xenial.com and status.xenial.com all fail DNS resolution. https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/ · retrieved 2026-09-09

Operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee.

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

Guest/customer records, loyalty balances or point ledgers, and gift-card liability balances are exportable in machine-readable form by the operator. differentiator

commercial-export-customer-and-loyalty

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

Contract or documentation specifies a post-termination data retrieval window (a defined number of days during which the operator can still export their data) rather than immediate cutoff. differentiator

commercial-post-termination-export-window

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

Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator

commercial-data-ownership-clause

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

The POS is source-available or open source with a documented self-hosting option (source published under an OSI or source-available license, not merely an open API).

commercial-source-available-selfhost

Upheld, and this is the strongest form of the verdict: the contract does not merely fail to grant source, it forbids the whole category. Customers must not 'Use, modify, integrate or distribute the Global Materials or the System (or any Related Applications) in any manner that does or is reasonably likely to subject the foregoing to any open source license terms', and a country-specific clause confirms what is withheld by carving out anything that would 'involve any access to, or use or modification of, any of Global's source code by Customer'. What the licence does grant is explicitly binary-only: 'a perpetual license, to access, use and, as applicable, install and run' -- but of 'the object code versions of the Software'. That is worth stating precisely, because it means Xenial DOES have an on-premises install path (Installed Software on Equipment at Authorized Restaurant Locations) and it still fails this claim, which asks for source published under an OSI or source-available licence. `self-host`, `self hosted`, `gpl` and `mit license` are zero across a 175-document corpus read 2026-09-09: an href fixpoint over www.xenial.com that closed at 181 URLs, the 86 sitemap entries that still resolve, and the four legal PDFs, including the Xenial Consolidated System Terms (3/2025) in English, Spanish and French-Canadian -- three renderings of ONE document, not three instruments, tokenised and as bare substrings alike, while proprietary reads 8 times in the terms. A word on the instrument, because the obvious one is a fossil: www.xenial.com/sitemap.xml lists 500 URLs, EVERY ONE stamped lastmod 2020-12-11, and 414 of them now 404 -- including 361 of the 364 product-documentation entries, which are .stml files from a site since rebuilt. A sitemap can be complete-looking and almost entirely dead, so this corpus rests on a live href fixpoint instead. docs.xenial.com, developer.xenial.com, wiki.xenial.com and status.xenial.com all fail DNS resolution. https://www.xenial.com/legal/service-terms/Xenial-Consolidated-System-Terms/ · retrieved 2026-09-09

Vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A / SAQ P2PE-HW, and names the applicable SAQ.

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

Vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — notably MFA for all access to the cardholder data environment including POS and back-office logins, and (for hosted ordering pages) payment-page script integrity monitoring per Req 6.4.3/11.6.1.

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

Vendor states it holds a current SOC 2 Type II (or ISO 27001) attestation and will provide the report under NDA via a trust center or on request.

commercial-soc2-attestation

DOWNGRADED FROM `no` BY THE ADVERSARIAL PASS, 2026-09-12. The instrument is sound and I reproduced it: the three Paligo fuzzydata.min.js search indexes are a page-level CENSUS of xenial.com’s three documentation portals (11,269 sections over 1,274 pages, a strict superset of the portals’ own index-en.html contents at 1,267, diffed both ways), and I re-fetched all 1,274 pages at HTTP 200 and confirmed every asserted zero on that second instrument. The measurements hold - `SOC 2`, `ISO 27001`, `attestation`, `conformance` and `under NDA` are each 0 across 11,269 sections AND across the 1,274 re-fetched pages, and the 41 bare `SOC` matches are all “system on a chip (SOC) environments” in the Digital Menu Board content topic. But the corpus is THE WRONG PUBLISHER for this proposition. A SOC 2 / ISO 27001 statement lives on a corporate trust or security page, not in a POS product manual, and that surface is UNMEASURED rather than absent: Xenial itself has none (/security and /trust 404, and its own 500-loc sitemap names no security, compliance or trust page), and www.globalpayments.com - the parent, and the natural publisher for a subsidiary’s attestations - serves a Cloudflare “Just a moment...” interstitial with HTTP 403 on every path including /security, which its own 260-byte robots.txt expressly permits. Archived Global Payments merchant security pages carry no SOC 2 or ISO 27001 statement either, but those are marketing pages, not the corporate trust surface. An absence bounded to product documentation cannot settle a compliance-attestation claim about a Global Payments company, so the honest value is unknown. Resolvable by the Global Payments corporate security/compliance pages if the Cloudflare interstitial can be passed in policy, or by a Global Payments 10-K. || 325th: NEW INSTRUMENTS, cell still unknown, and two of the standing note's blockers are now measured. (1) THE PARENT'S SEC FILINGS ARE A BOUNDED CORPUS AND THEY ARE SILENT: EDGAR full-text search over every filing of Global Payments Inc (CIK 0001123360) returns 'SOC 2' = 0 hits and 'ISO 27001' = 0 hits (efts.sec.gov/LATEST/search-index; 'Xenial' itself appears 13 times, all in EX-21.1 subsidiary lists, including the 2026-02-20 filing). www.sec.gov/Archives needs Sec-Fetch-Dest/Mode/Site headers plus a browser UA or it 403s. (2) www.globalpayments.com is no longer uniformly 403 - the Cloudflare challenge is intermittent and the site answered 200 once in this session - but there is still no corporate trust or compliance page to read: a Wayback CDX enumeration of every globalpayments.com HTML capture whose urlkey matches security|compliance|trust|certif returns 50 URLs, every one a marketing or 'insights' article (e.g. /accept-payments/online/security, /insights/security-questions-for-your-payment-provider), with no trust centre, SOC 2 or ISO 27001 page among them; trust.globalpayments.com and status.globalpayments.com are NXDOMAIN. (3) Over the 100%-fetched 293-topic Genius developer portal 'SOC 2|ISO 27001|attestation|AOC' = 0. Held unknown, not `no`: the claim is satisfiable 'on request', which no public corpus can exclude, and a Whistic/Vanta-style vault behind a sales contact would appear in none of these instruments. Retrieved 2026-09-17. || 327th: 327th, THE PUBLISHER SEARCH IS NOW EXHAUSTED ON THE DNS SIDE. The standing note's blocker is that the right publisher (a corporate trust/security page) is unmeasured. This pass ran certificate-transparency enumeration on the two Xenial-owned domains never enumerated before - heartlandcommerce.com and xenial.cloud - yielding 185 distinct names. NO trust, security, compliance or vault host exists among them (no trust.*, no security.*, no *.safebase/whistic/vanta CNAME target); the only externally-interesting names are developer.xenial.cloud and portal.xenial.cloud, and BOTH are dead at DNS today (curl status 0, NXDOMAIN), as are trust.globalpayments.com and security.globalpayments.com. The Wayback CDX for developer.xenial.cloud holds exactly one 200 capture (2024-09-04) and it is A DIFFERENT PRODUCT: 'Aether Developer Docs ... a new initiative to bring advanced insights, analytics and AI to Managed Service Providers' - do not re-mine it as a Xenial developer portal. www.globalpayments.com remains 403 to browser-UA curl WITH Sec-Fetch headers on /legal, /en-us/legal, /en-us/security, /en-us/why-global-payments/security and /sitemap.xml (its robots.txt serves 200 at 243 B, so the refusal is Cloudflare, not policy); www.heartland.us/legal 403s likewise. A refusal is not an absence, so this stays unknown. Retrieved 2026-09-18. || 328th: 328th: TWO NEW SURFACES, both bounded, neither publishes an attestation. (1) developer.globalpayments.com (reached via developer.globalpay.com, which 301s there), the parent's own developer portal, censused to 100% of its published /llms.txt manifest: 145 documents, all 200, 6.8 MB, nonsense control /docs/zzz-nonsense-control.md = 404 at 9 B. Over it 'SOC 2' 0, 'ISO 27001' 0, attestation 0, 'Attestation of Compliance' 0, AOC 0; its 38 PCI DSS mentions are all merchant SCOPE REDUCTION prose ('Simplest level of PCI DSS compliance: SAQ A', 'PCI DSS scope reduction via Hosted Fields'), i.e. what the integrator's SAQ becomes, never a report Global Payments will hand over. This is a publication census of the parent's developer portal, so it retires 'the parent publishes nothing reachable' as a guess and replaces it with a measurement - but it is not the corporate trust/security page the claim needs, and it cannot carry a `no` for Xenial. (2) The Xenial APK web-asset corpus (1,781 files / 9,489,331 chars; see hardware-byod): 'SOC 2' 0, 'ISO 27001' 0, attestation 0. Its one legal document is assets/www/assets/EULA.txt, which despite the filename is the Xenial Privacy Notice of 25 Jan 2022 (Xenial, Inc., 'its subsidiaries and affiliates ... include but are not limited to RTI and SICOM', contact privacy@globalpay.com) - a privacy notice, with no certification or audit-report clause. Held unknown: www.globalpayments.com/en-us/security and www.heartland.us/legal still return Cloudflare 403 to browser-UA curl with Sec-Fetch headers, and a refusal is not an absence. Retrieved 2026-09-18. || 331st: 331st: TWO NEW REGISTRIES MEASURED, neither carries SOC 2 / ISO 27001, cell held. (1) Visa Global Registry of Service Providers, public company-name lookup (GET https://www.visa.com/splisting/api/company?companyName=<name>, the SPA's own call): 'Xenial' -> [] and 'Genius' -> []; 'Heartland' -> 'Heartland Payment Systems LLC, a division of Global Payments Direct Inc.'; 'Global Payments' -> six entities incl. 'Global Payments Direct, Inc.'. The registry's program list (fetchCriteria) is PCI DSS / TPA / ACS / AVP only - it has no SOC 2 or ISO 27001 field, so it cannot answer this claim either way. (2) The PCI SSC P2PE register (136 valid solutions) lists Global Payments Direct's 'Genius Smart P2PE' (see reliability-pci-dss-4-attestation) - a PCI artefact, not a SOC 2 / ISO 27001 statement. A web search for a Xenial or Global Payments SOC 2 / ISO 27001 statement returned only unrelated vendors (e.g. 'Helios Global Payments Solutions', a different company - POISON, do not cite). xenial.com's current sitemap (500 locs) names no security/trust/compliance page. Retrieved 2026-09-18. || 332nd: 332nd: TWO NEW PARENT DOCUMENTS, neither names SOC 2 or ISO 27001. Global Payments' 2024 and 2025 Global Responsibility Reports (investors.globalpayments.com/sustainability -> d1io3yog0oux5.cloudfront.net ... 2024_GP_GRR.pdf 23.5 MB / 300,897 chars text; 2025+Global+Responsibility+Report.pdf 4.97 MB / 185,522 chars; both name Xenial/Genius in their business sections, so they are the right publisher). Their security sections state the frameworks the parent uses: 2024 p.69-70 'The structure of the information security program is informed by the NIST Cybersecurity Framework, and the program includes controls designed to facilitate the compliance of our cardholder data environments with Payment Card Industry (PCI) Data Security Standard (DSS)' and 'aligns its program with the NIST Cybersecurity Framework as well as leveraging the Payment Card Industry's (PCI) Payment Data Security Standards and their certifications'; 2025 repeats 'aligns to the NIST Cybersecurity Framework'. Tokenised controls over both: 'SOC 1|SOC 2|SOC2' 0, 'ISO 27001|ISO/IEC' 0, 'attest*' 0; known-positive controls 'NIST' 2/2 and 'PCI' 8/8 hits (word-boundary, 2024/2025). Also 0 across the 8 Genius Enterprise pages on www.globalpayments.com (Wayback, see payments-payout-timing) - the back-office page says only 'Powered by AWS and Microsoft Azure Cloud ... enterprise-grade platform ensures uptime'. Not a `no`: a governance report is not a trust-centre census, and help.globalpay.com/account/compliance-and-security (a Global Payments 'Compliance & Security' help page) is a Cloudflare 403 to curl - a refusal, unread. 332nd: POISON NAMED for the whole record - geniusforenterprise.com (cited in product.yaml as a vendor domain) is NOT Global Payments': every page footer reads 'An Authorized Reseller of Global Payments ... JCR Systems is an independent authorized reseller. Powered by CT.Marketing' (LeadConnector/GoHighLevel funnel, 10 pages, nonsense path = soft-200 homepage). Anything on it is third-party grade D. Retrieved 2026-09-18. || 334th: 334th NEW SURFACE: 218 Global Payments press releases (investors.globalpayments.com/news-events/press-releases, ?page=1..22 until empty, every detail page fetched 200 on 2026-09-18, 2.15 M chars of release text; 23 of them name Genius or Xenial, incl. 122 Xenial launch 2017, 473 Genius platform 2025-05-16, 486 Genius for Enterprise 2025-09-10, 490 higher education, 495 Uber Eats partnership 2025-11-18, 509 AI-first handheld 2026-05-12, 515 Genius World 2026-08-24). 'SOC 1|SOC 2|ISO 27001|SSAE' = 0 across all 218 (known-positive controls live: 'Genius|Xenial' in 23 releases, 'PCI' 2 hits in 2 releases). Also the App Store PUBLISHER census for Xenial (itunes lookup?id=1455368071&entity=software = 4 apps: Xenial Shell com.xenial.shell.app, Genius Mobile Manager, Genius Back Office Mobile, and Genius Team Portal Mobile io.genius.tp.mobile.app, the last NEW since the 328th: released 2025-11-04, an employee schedule/time-off/shift-swap app): none of the four listings names SOC 2 / ISO 27001. A press-release archive is not a trust-centre census, so held unknown. Retrieved 2026-09-18. adversarially verified

Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.

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

Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator

commercial-wcag-kiosk-accessibility

Re-tested 2026-09-12 against the LIVE Paligo full-text search index served by all three xenial.com documentation publications (product-documentation, release-notes and developer-resources each serve en/js/fuzzydata.min.js, 5.5 + 7.8 + 4.9 MB), parsed to 11,269 indexed sections carrying 11.18 M chars of body text - 3,988 Product Documentation, 3,944 Release Notes, 3,337 Developer Resources. TWO PREMISES THIS NOTE WAS FIRST WRITTEN WITH WERE FALSE AND THE ADVERSARIAL PASS STRUCK THEM on 2026-09-12: the index is NOT “a surface no prior pass read” (this record’s own sources.jsonl cites all three fuzzydata.min.js files at HTTP 200 on 2026-08-04, with their sizes), and only 10 of these 26 standing rationales rested on the 1,197 Internet Archive files. What IS new is that the index runs to 2026-09-15 and that the pages themselves render body text server-side. The corpus is a PAGE-LEVEL CENSUS of these three portals rather than a floor: it is a strict superset of the portals’ own index-en.html tables of contents (1,274 pages against 1,267, diffed both ways), the 328 empty-body sections are container topics whose text is filed under their children (63 of 64 “Endpoints” containers are empty while each per-endpoint child carries its own body), and www.xenial.com/sitemap.xml is the weaker and stale instrument - 386 of its 392 documentation locs now 404. The adversarial pass re-fetched all 1,274 distinct pages at HTTP 200 and re-ran every asserted zero below over that second instrument; all held. Every term was matched tokenised, plural-tolerant on the last word, with the matcher proved in the same run on `drive thru` (334 docs) and `split check` (7 docs, matching the plural `Split Check Restrictions`). Every quotation below was checked verbatim-present in the fetched bytes of the page named for it (the cited URL unless the sentence names another topic). RESOLVED TO PARTIAL, on a tree the prior pass could not read - the Foodservice Management POS (Nextep) release notes, which are the kiosk line. A documented non-visual access mode exists: 2023-11-16 records that on the Low Visibility menu 'screen reader announces details for the selected item', that the 'Screen reader displays clearer item descriptions when pressing ? (question mark) on the KVI Bar' and that it 'prompts customers to Select Dining Option'; 2024-05-30 adds System Text Editor fields to 'control the text and audio dialog for scroll buttons'; 2024-04-18 records a Low Vis Mode contrast-ratio fix; and 2025-03-06 states that 'the items being delivered include those needed to meet WCAG 2.2 compliance'. Genius Kiosk configuration also carries an accessibility setting, though not under the name this note first gave it: the Genius Kiosk | Getting Started settings table pairs a label cell ‘Accessibility’ with a value cell ‘Reach Mode = ON’, so the contiguous span ‘Accessibility Reach Mode’ does not exist in the source. SHORTFALL: no accessibility conformance report is published. `VPAT` 0, `ACR` 0, `conformance` 0, `Section 508` 0 across all 11,269 sections; the WCAG references are three release-note lines, two of them SuiteSpot colour work, and none claims a conformance level for the consumer web-ordering surface. A release note asserting compliance work is not a VPAT/ACR. https://www.xenial.com/release-notes/en/genius-point-of-sale/foodservice-management-pos/previous-releases.html · retrieved 2026-09-12 adversarially verified

POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator

commercial-dual-pricing-compliant

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