Agilysys

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

IGCM has a Floor Plan menu (POS Configuration > Business > Floor Plan) with a graphical Layout designer: add named floor-plan records, then place Tables, Floor Plans and Screen Tools onto a canvas with Snap to grid, Grid size (0-9), Button padding and Allow button overlap. Tables are configured separately with Table No, Table Name, Max Seats and Booth/Private/Outside/Smoking/View/VIP attributes, and the terminal reproduces "the shapes, sizes, and colors of the tables" from IGCM. Multiple floor plans exist per profit center (one is primary; the rest are selectable, and Terminal Option 300 prompts for the default table layout to use during a shift). Shortfall: there is no server-section construct - areas exist only as labelled Terrain tools, and servers are attached to individual checks (Transfer Server) rather than to a section of the floor plan. https://ig.onagilysys.com/help/POS/IG_Fly/ConfigGuide/Create%20Floor%20Plan.htm · retrieved 2026-08-08

Order lines can be tagged to a seat number at entry, and the check can be split by seat afterward without re-keying items.

order-capture-seat-level

"Every menu item in a check can be assigned to a seat. This helps with the food service and also while splitting checks." First item defaults to Seat 1; Advance Seat moves subsequent items to the next seat (1-25), Modify Seat reassigns an existing line, VIP Seat flags one. The Advanced Split Check screen then offers Split by Seat with Move ("move items across seats") and an Assign to Seat step inside it, so the check is split from the seat tags already on the lines rather than re-keyed. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Ordering%20Items%20by%20Seat.htm · retrieved 2026-08-08

Items can be assigned to courses and held, with a fire-next-course action available from a handheld or terminal that releases only that course to the kitchen.

order-capture-coursing-hold-fire

"Ordering by course permits more control over the timing of food delivery to the guest." Advance Course groups lines into up to 25 courses, Modify Course reassigns a line, and "if a check with course is fired, the course numbers are also sent to the kitchen printer or kitchen video". IG Fly (handheld) documents Fire by Course (#1921), which fires items by course number on an open check, alongside Advance Course (#316) and Modify Course Number (#315), with Terminal Option 1153 (Default to 'Hold Item') holding all lines until fired. IG KDS receives the course number and can Split Chits based on Course. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Ordering%20Items%20By%20Course.htm · retrieved 2026-08-08

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

Advanced Split Check (#3) offers Split by Seat, Split by Course and Split by Item on one screen, plus Split Here ("split the item to the required number of portions, and the amount of the item is divided based on the number of portions") and Merge ("merge two or more splits into a single check"; the old Combine Check button was renamed Merge). Separately, Even Split divides a check 2-32 ways, Split All Items spreads items across up to 25 checks, and Split Payment supports uneven "split by amount and split by percentage". Tables/checks recombine via Merge and Transfer Table. Note: the docs do not state whether a merge is permitted after a partial tender, and Modify Seat is explicitly blocked on a partially tendered check. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Advanced%20Split%20Check%20Functionality.htm · retrieved 2026-08-08

Opens a bar tab against a card pre-authorization with a configurable auth amount, supports incremental re-auth as the tab grows, and auto-closes stale tabs at end of day. differentiator

order-capture-bar-tab-preauth

The Authorize function opens a card authorization on an open check and lets the user "complete the payment later while closing the check or adding a tip"; multiple authorizations per check are allowed, Modify Auth increases or decreases an existing authorization, Terminal Option 39 permits authorizing more than the check total, and zero-dollar authorizations are supported (Terminal Option 1419 auto-increases them to the check balance). The Adyen release note confirms incremental behaviour by describing when it breaks: with delayed settlement "this prevents the authorization on the open check from being increased, even if it is to add a tip". Shortfall: no automatic end-of-day close of stale tabs - Open Checks Purge (#2090) is an operator-driven selection with a 30-day retention window, not an EOD sweep. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Authorization.htm · retrieved 2026-08-08

An open check can be transferred between servers, tables, and devices, and the transfer is recorded in an audit log naming both employees.

order-capture-transfer-audit

Transfer Check moves an open check to another Server (by Server ID and optional password, or from a list of clocked-in employees with Terminal Option 130), another Profit Center, or another Table; the Server Name shown in Check View changes on transfer, and Transfer Pull lets a server pull a check from another server. Checks are held centrally, so any terminal can recall them (Break Lock releases a check locked by another terminal). Shortfall: no documented transfer audit record naming both employees - the Electronic Journal utility filters logged events by a single Employee, Terminal, Source, Event Name and Logging Severity, and no sample transfer entry or field list is published; IGCM Audit Logging covers back-office form edits, not terminal check transfers. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Transfer%20Check.htm · retrieved 2026-08-08

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

IG Fly and IG Flex are first-party handheld apps with their own configuration and user guides; native iOS and Android POS Terminal apps ship in both app stores. https://www.agilysys.com/en/products/ig-fly/ · retrieved 2026-08-01

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

Claims enterprise-grade offline resiliency with kitchen jobs and check data reconciling on reconnect, but publishes no what-works/what-fails matrix. https://www.agilysys.com/en/products/infogenesis-pos/ · retrieved 2026-08-01

Guest QR at-table ordering writes items onto the same open check as server-entered items, rather than creating a separate order ticket. differentiator

order-capture-qr-same-check

IG Quick Pay attaches to an existing POS check via QR; whether IG OnDemand guest items write onto a server-opened check is not documented. https://www.agilysys.com/en/products/ig-quick-pay/ · retrieved 2026-08-01

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

IG Kiosk documents real-time menu sync from InfoGenesis POS with no separate build; no ADA/WCAG conformance statement anywhere on the page. https://www.agilysys.com/en/products/ig-kiosk/ · retrieved 2026-08-01

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

Re-evidenced 2026-08-08 after the cited /en/products/ index 301'd to the homepage. The complete InfoGenesis 12UX help set (1,691 topic pages: ConfigGuide 747, UserGuide 449, ReportsGuide 122, plus release notes) contains no topic matching 'drive' - no drive-thru mode, order point, pay window, pickup window, tandem lane or pull-forward/parking-spot function. The IGCM Configuration Guide states it 'contains information about all the modules in the IGCM' and lists them as POS Configuration, Utilities, User Management and Reports. Agilysys' current product catalogue is 37 /en/products/ pages and none is a drive-thru product; ICP is hotels, resorts, casinos, cruise and stadiums. https://ig.onagilysys.com/help/POS/IG_12UX/Sitemap.xml · retrieved 2026-08-08 adversarially verified

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

order-capture-drive-thru-timers

Re-evidenced 2026-08-08 after the cited index went dead. The InfoGenesis ReportsGuide enumerates 122 reports (Cashier Performance, Hourly Revenue, Product Mix, Labor Summary, Clock Activity/Detail, Enterprise Revenue Summary and so on); none reports order, total or window segment times, and no topic in the 1,691-topic help set matches 'drive'. There is no drive-thru order flow to time. https://ig.onagilysys.com/help/POS/IG_12UX/Sitemap.xml · retrieved 2026-08-08 adversarially verified

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

Both disjuncts fail. No first-party voice ordering agent: `drive-thru`, `drive through`, `IVR`, `phone order`, `caller`, `telephony` and `inbound call` occur ZERO times across all 7,051 help-topic bodies, and the 12.3.16 Classify and Store Transaction table - introduced by 'Refer to the following table for information on the classification and supported values captured whenever a check is opened or closed' - enumerates Terminal Mode, 'the ordering channel or the product associated with the source', as POS Terminal, IG OnDemand, IG Fly, IG Kiosk, Teams Ordering, DoorDash, Uber Eats and Grubhub, with no voice or telephone channel. And no documented API partner program for third-party voice AI: the Azure API Management developer portal at agys-dev.developer.azure-api.net publishes nothing anonymously (re-probed 2026-09-12 - /robots.txt and a fabricated path return the same 404 shell), api/developer/docs/help/partners.agilysys.com are NXDOMAIN and support.agilysys.com resolves to 65.210.128.41 but drops every TCP connect, i.e. unmeasured rather than absent - so there is no published API reference on which to found a voice partner program. CORRECTED 2026-09-12: an earlier draft of this note said every `voice`/`speech` hit was IG Kiosk ADA text-to-speech and that the only AI assistant was the IGCM chat helper. Both are false. Of 74 `voice` hits, most are credit-card VOICE AUTHORIZATION (a manual phone authorisation of a card) and 13 are an Eatec 26.2.5 'AI Requisition Voice Assistant' for back-office inventory requisitions - a second AI assistant, and a voice one. Neither is a guest ordering channel, so the verdict is unchanged. The 102-name Solution Partners roster is NOT load-bearing here and is visibly mis-categorised (Olo is filed under Hardware, the sole PBX member is a wristband vendor, and Percipia - hotel telephony - is filed under Payment Processing). ALSO CORRECTED: `drive-thru` was published as a zero over 7,156 documents; over the full 8,068 it is 2 hits, both in one blog post ('With up to 70% of quick service sales coming through drive-thru windows'), generic industry commentary about Chick-fil-A rather than an Agilysys product, so the verdict is unchanged but the figure was wrong. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IG_12UX/12.3.16_RN/Classify%20and%20Store%20Transaction.htm · retrieved 2026-09-12 adversarially verified

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

IG KDS ships 'Smart Order Throttling' balancing demand against kitchen capacity; per-channel time-slot caps and automatic quote extension are not documented. https://www.agilysys.com/en/products/ig-kds/ · retrieved 2026-08-01

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

IG OnDemand accepts scheduled orders 1-365 days out, configured per site entity ('Scheduled in Future' checkbox with From Day/To Day lead-time bounds) plus an Order Scheduling Time Interval and per-slot Web Order Throttling capacity; IG Fly enforces a 15-minute minimum lead. IG KDS holds them in a Scheduled Orders tab and 'the scheduled orders move into the Open tab as per the schedule set while ordering', with a manual Push to Open promote for priority firing - fire-at-schedule, not print-on-receipt. https://ig.onagilysys.com/help/POS/IG_OnDemand/UserGuide/Support%20Scheduled%20Orders.htm · retrieved 2026-08-03

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

Sales & Catering handles BEOs and syncs InfoGenesis charges to group accounts — event catering, not a restaurant catering queue with documented quotes, deposits and balance-due tracking. https://www.agilysys.com/en/products/sales-and-catering/ · retrieved 2026-08-01

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

IG KDS pushes order state changes to IG OnDemand for a documented list of transitions - order bumped, delivered, received in the kitchen, confirmed, rejected, moved from Queue/Schedule to Open, moved from Open to Closed - which OnDemand uses to accept, delay or reject guest orders. InfoGenesis also emits generic Order Events (placed, refunded, voided) and Kitchen Events ("triggered when an order is bumped in the kitchen") to external systems as JSON, but "Contact Agilysys to initiate this integration at your property" and "development efforts may be required on both sides". Shortfall: the receiving channel is Agilysys's own IG OnDemand or a bespoke integration - no third-party marketplace (DoorDash, Uber Eats, Grubhub) appears anywhere in the 5,336-topic help system, so no marketplace order-ready callback is documented. https://ig.onagilysys.com/help/POS/IG_KDS/UserGuide/Update%20Kitchen%20Order%20Status.htm · 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

Partial upgrade, not a full yes — record it as partial if the schema allows. The first-party POS Terminal app listing documents 'Void items from the check', 'Void Checks' and 'Provide access permissions based on job code', which is void + permission control. Comps and manager-override audit trails remain entirely undocumented, so do not read this as full void/comp governance. https://apps.apple.com/us/app/infogenesis-pos-terminal/id1534574604 · retrieved 2026-08-01 adversarially verified

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

Choice Groups carry Minimum and Maximum fields in the Main submenu of the IGCM Choice Group menu (the kiosk auto-advances "when the minimum number of modifiers is selected"), a minimum of 0 is explicitly the not-required case, and Terminal Option 1428 (Show message when choice Group conditions are not met) enforces the rule at the terminal; Terminal Option 71 exists solely to ignore min/max. Nesting is real - IGCM shows "all levels of nested modifiers" for an employee-facing menu and only one level for a guest-facing menu, and the kiosk speaks of "multi-level modifiers". Shortfall: no topic states a supported nesting depth, and the only concrete statement of structure is IG KDS's "a modifier is shown one level below the item, and a nested modifier is shown one level below the modifier" - two levels, not the three the claim asks for. https://ig.onagilysys.com/help/POS/IG_Kiosk/UserGuide/Auto%20Advance%20to%20Next%20Page.htm · retrieved 2026-08-08

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

Modifier Price Tier Level is a matrix of modifier prices per price level x price tier, and 'the price of the modifier is considered according to the tier of the added item' - parent-item-dependent modifier pricing exists without duplicating the modifier. Shortfall: no documented pricing of a modifier by the parent item's selected size; sizes are implemented as quantity-category multipliers on the item's own price, and a modifier's Base Price field is disabled once a quantity category is assigned to it. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Modifier%20Price%20Tier%20Level.htm · retrieved 2026-08-03

Supports fractional/sectioned modifier placement (at minimum halves, ideally quarters) with independent pricing per section. differentiator

menu-pricing-fractional-placement

CLAIM: fractional/sectioned modifier placement (halves, ideally quarters) with independent per-section pricing. VERDICT: no. The prior pass withheld a no because 'the ConfigGuide Modifier and Choice Group topics are stubs that do not publish their field lists'. They are not stubs: they are TOC parents, and the MasterTOC tree lists their submenus. EVIDENCE (closed enumeration of the modifier form): https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Modifier.htm has exactly 11 child topics - Basic Details (ID, Modifier Name, Base Price, Kitchen Printer Text, Kitchen Video Text, Print modifier on customer check), Classification (Nested Choice Group, Discounts, Item (Product Mix), Item Group), Show Choice Groups, Kitchen Printer Settings (Kitchen Printer (Logical), Primary, Print with Item on Kitchen Printer), Kitchen Video (Category, Department, Cook Time), Price Levels (Price Level, Current Price), Image Configurations, Kiosk Configuration (Calories Base/Max, Description, Display Name), Show Layouts, Tags (Tag, Type, Sequence), Translation. Choice Group.htm has 6 (Basic Details: ID, Name, Display Name, Description, Minimum, Maximum; Modifiers: Modifier, Sequence; Translation; Show Items; Show Layouts; Additional Image). No placement, side, section or fraction attribute exists on either form. The ordering-time model in https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Modifiers.htm is min/max per choice group, a quantity per modifier ('Select the right half of the modifier button to add a quantity of the modifier'), nested choice groups and one sizeable modifier - and its own pizza example has no placement: 'when the user orders a pizza, the Toppings prompt appears. Select the required pizza toppings (i.e., cheese, olives, garlic), then select Done'. BOUND: raw-HTML census of ig.onagilysys.com/help/POS, 2026-09-16 (HelpSystem.xml BuildTime 9/16/2026 3:19:59 PM): 7 MadCap help systems (IG_12UX 1,724, IG_Kiosk 1,238, IG_OnDemand 923, IG_Fly 918, IG_KDS 595, IG_DMB 59, IGCM 99 TOC entries = 5,556 topics), all 200; href fixpoint over 55,577 in-body .htm links added ZERO topics outside the TOC; a nonsense path returns a real 404 (WebContentNotFound), so no soft-200. Plus 71 superseded 12.3.16_RN topics that are still served but no longer in the TOC (replaced by 12.3.16.1_RN), read from the q310 cache: CORPUS 5,627 bodies, comments/scripts stripped, tokenised word-boundary case-insensitive controls (.cache/q316/agilysys/controls.mjs). CONTROLS over 5,627 bodies: half|halves 2 hits, both POISON ('Half Tone' printer logo setting; 'right half of the modifier button' = touch target); quarter 4 = 'First Quarter' report period (POISON); fraction/fractional 2 = 'fractions of an hour' time sync; sectioned 0 (1 'Price Levels section' UI hit); placement 18 = QR code/banner/container placement; 'on the side'|side A/B|first/second side 0 ('left side'/'right side' 78 = screen layout); modifier prefix|pre-modifier 0; build your own 0; portion 134 = KDS 'Prepare Portions of Item Across Multiple Stations' (prep routing to stations), split-check portions and quantity-category 'portion size from Standard to Large' (POISON, none spatial); pizza 195 in 35 files = report arithmetic, cross-sell and size examples; topping 15 = the multi-select example above. Retrieved 2026-09-16. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Modifier.htm · retrieved 2026-09-16 adversarially verified

The half-and-half pricing rule is operator-configurable among at least two of: charge the higher-priced half, average the halves, or charge each topping at a fraction of full price. differentiator

menu-pricing-half-and-half-rule

CLAIM: operator-configurable half-and-half pricing rule (higher half / average / fraction per topping). VERDICT: no. There is no sectioned placement to price (see menu-pricing-fractional-placement), and the modifier price surface is a closed enumeration with no rule selector. EVIDENCE: https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Basic%20Details_65.htm (Modifier > Basic Details): 'Base Price | Enter an appropriate price for the modifier. Even though the price is configured here, the price of the modifier displayed in POS Terminal is determined by the price level configured in the Price Levels sub-menu. If price level is configured for the meal period schedule or tender group or check type, it overrides the price entered in this field.' https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Price%20Levels.htm (Modifier > Price Levels) holds only 'Price Level' and 'Current Price'. The remaining price constructs are whole-item: price tiers, and a quantity category with a price multiple limited to one per item. These are the only 11 submenus of the Modifier form per the MasterTOC tree (Basic Details, Classification, Show Choice Groups, Kitchen Printer Settings, Kitchen Video, Price Levels, Image Configurations, Kiosk Configuration, Show Layouts, Tags, Translation). BOUND: raw-HTML census of ig.onagilysys.com/help/POS, 2026-09-16 (HelpSystem.xml BuildTime 9/16/2026 3:19:59 PM): 7 MadCap help systems (IG_12UX 1,724, IG_Kiosk 1,238, IG_OnDemand 923, IG_Fly 918, IG_KDS 595, IG_DMB 59, IGCM 99 TOC entries = 5,556 topics), all 200; href fixpoint over 55,577 in-body .htm links added ZERO topics outside the TOC; a nonsense path returns a real 404 (WebContentNotFound), so no soft-200. Plus 71 superseded 12.3.16_RN topics that are still served but no longer in the TOC (replaced by 12.3.16.1_RN), read from the q310 cache: CORPUS 5,627 bodies, comments/scripts stripped, tokenised word-boundary case-insensitive controls (.cache/q316/agilysys/controls.mjs). CONTROLS: 'half and half'|half-and-half 0; half 2 (both POISON: Half Tone, right half of a button); fraction 2 (time sync interval). Retrieved 2026-09-16. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Basic%20Details_65.htm · retrieved 2026-09-16 adversarially verified

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

Quantity categories carry a configurable Price Multiple applied through modifiers ('enter an appropriate value based on which the price of the item will be modified'), with per-item quantity/price override flags. Shortfall: the documented mechanism scales the parent item's price for size selection - 'only one quantity category modifier should be applied to an item at a time' - and no light/regular/extra/double tiering of an individual topping modifier with per-tier multipliers is documented. https://ig.onagilysys.com/help/POS/IG_Fly/ReleaseNotes/Sizeable%20Items%20and%20Quantity.htm · retrieved 2026-08-03

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

One variant axis is fully supported: an item is flagged Sizeable Item in Price Information, mapped to a Quantity Category whose Price Multiple scales the price (Coffee Small $3 / Medium $4 / Large $5), with per-item Is Quantity Override and Is Price Override checkboxes to override the category values, a Default size, and Prompt For Sizes at the terminal. A grid does exist in Item Price Tier Level - "users can configure different prices for the item against each price level and price tier" - but its axes are commercial (price level x price tier), not variant axes. Shortfall: no second variant axis and no per-cell override across two axes; only one quantity-based (size) modifier may be applied to an item at a time, so a size x crust/preparation price grid cannot be expressed - a second axis is an ordinary priced modifier added to the base. https://ig.onagilysys.com/help/POS/IG_Fly/ReleaseNotes/Sizeable%20Items%20and%20Quantity.htm · retrieved 2026-08-08

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

The substitution half of the claim is configurable and documented: in Item Level Configurations, "if only selecting specific items that cannot be substituted, a package is created... if selecting one or more selection groups, a selection group is created that permits substitutions", each component carrying its own Price, Quantity and Amount that roll into Package Price. Shortfall: no included-modifier allowance. Choice Groups expose only Minimum and Maximum selection counts (IGCM Choice Group Main submenu); nothing in Price Information, Modifier Price Tier Level or the Choice Group topics defines an included count with overage-only charging or a substitution credit, and a TOC sweep of all 5,336 topics finds no included/free/allowance/overage topic. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Item%20Level%20Configurations.htm · 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

Packages are "a group of items sold for a set price"; in Item Level Configurations each component carries its own Price and Quantity and the Package Price is "the total price of the package from the combined price of the item amounts entered", so a swapped component changes the price by its own delta. Selection Groups are the swap mechanism - "a package contains a set group of items that cannot permit substitutions while a selection group can have substitutions inserted when required" - and Package Update lets a selection be made later in a coursed meal. Automatic Package Recognition supplies the cart detection: "the POS terminal supports recognizing items automatically as packages when items belonging to a package are added as individual items to a check. Individual items are replaced with packages", and the terminal shows the guest's saving. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Packages.htm · retrieved 2026-08-08

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

Built-in upsell prompts documented on IG Kiosk and IG OnDemand plus AI 'embedded upselling' on POS; per-channel configuration and attach-rate reporting are not documented. https://www.agilysys.com/en/products/ig-kiosk/ · 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

Claims a single synchronized source of truth for menus, pricing and availability across terminals, mobile, kiosk and QR; no third-party marketplace propagation, no published latency. https://www.agilysys.com/en/products/infogenesis-pos/ · 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

Item Countdown assigns per-item Quantity on Hand, Warning and 86 Cut-Off per profit-center countdown group; counts decrement on save/tender, increment on void, and 'when the item quantity goes below the threshold limit, it is 86ed automatically', with security-level-5+ override to sell past the 86. Shortfall: no scheduled auto-restore is documented - un-86 is manual via the Manage 86 utility or terminal functions. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Item%20Countdown.htm · retrieved 2026-08-03

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

The Daypart Schedule menu gained a Date Based Schedule submenu: pick a Date (up to 90 days out), a Pickup Method of All Day or Time Range with Start Time and End Time, a Platform, and then the Screen (the menu layout of items), Price Level and Check Type that apply. Week-wise schedules remain and "when both date-wise and week-wise schedules are configured, the date-wise schedule takes precedence"; overlapping windows resolve by start time. Dayparts are mapped to a terminal group or profit center (IG_Fly/ConfigGuide/Map%20Daypart%20to%20Terminal%20Group.htm), so each outlet runs its own schedule on its own terminals' clock; the docs never discuss timezone conversion explicitly. https://ig.onagilysys.com/help/POS/IG_12UX/ReleaseNotes/Date%20Wise%20Menu%20in%20Schedule.htm · 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

Distinct price books exist as Price Levels, Store Price Levels (per-store price that "takes precedence" over a scheduled price) and Price Tiers, with Item/Modifier Price Tier Level letting every item and modifier hold a different price against each price level and tier, and Price Tier Mapping binding tiers to product class and revenue category per schedule; a Daypart Date Based Schedule selects the Price Level and Check Type in force. Percentage markup is also real: Schedule Price Change applies Amount or Percentage to a Displayed Price Level or All Price Levels with Up/Nearest/Down rounding over a start/end date range. Shortfall: the axes are price level, tier, store and check type - there is no per-third-party-marketplace price book (no marketplace integration appears anywhere in the help system), and the percentage rule is a scheduled bulk utility that writes prices rather than a standing per-channel markup rule. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Schedule%20Price%20Change.htm · retrieved 2026-08-08

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

The documented card-cost-recovery model is the opposite of dual pricing: a credit-card surcharge added on top of the base price at tender - configured in the Adyen portal, 'POS terminal calculates the surcharge and displays the confirmation screen with the total transaction amount (purchase amount, tip, and surcharge)', with DataCap surcharge-percentage support and a Configure Tax for Surcharge checkbox under Default Taxes. The pricing and discount constructs the manual enumerates (price tiers and schedules, discounts, discount rules, PMS/member/tier discounts, coupons) contain no cash-discount-by-tender and no card-price-displayed-as-base mode; 'dual pricing' and 'cash discount' return zero topics across the indexed help sets for POS Terminal, OnDemand, Kiosk, Fly and KDS. https://ig.onagilysys.com/help/POS/IG_12UX/ReleaseNotes/Adyen%20Surcharge%20Support.htm · retrieved 2026-08-04

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

Effective dating is documented: Schedule Price Change takes a unique named record with Start Date and End Date ("the start date must not be lesser than the current date") and the terminal automatically reverts when the window ends - "the price of the item, Duck Hush is scheduled as $27.00 (previously $25.00). During the scheduled period POS terminal shows the new price and after the schedule ends, POS terminal reverts to the old price" - and a Swap to Previous Price checkbox swaps current and previous prices. Daypart Date Based Schedules stage menu screens up to 90 days ahead. Shortfall: this is scheduled staging of prices and screens, not menu versioning - no version history, no draft/preview of a pending menu before publish, and no rollback to a prior published version. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Price%20Change%20Utility%20vs%20Scheduled.htm · 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

Cloud portal deploys menu/price/promo updates globally across multiple properties simultaneously; field-level override governance is not documented. https://www.agilysys.com/en/products/infogenesis-pos/ · retrieved 2026-08-01

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

Eatec offers nutrition tracking as a named optional add-on; publishing allergen/nutrition to online ordering or third-party menus is not documented. https://www.agilysys.com/en/products/eatec/ · retrieved 2026-08-01

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

The Eatec page lists Recipe Costing under 'optional add-on modules' (alongside Catering Management, Nutrition Tracking, Commissary/Manufacturing, Buffet Management). So it is a paid add-on to Eatec, which is itself a separately licensed SKU from InfoGenesis POS — two purchases away from the POS. Not a native POS capability. https://www.agilysys.com/en/products/eatec/ · retrieved 2026-08-01 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

DOWNGRADED from partial 2026-09-12: both conjuncts fail, and one fails by the claim's own definition. The claim requires a certified DIRECT integration and expressly excludes 'a menu-management middleman'. The only marketplace menu route Agilysys documents is exactly that: IGCM 12.3.14 integrates InfoGenesis with UrbanPiper, 'a middleware platform that connects POS systems to multiple online food delivery aggregators, such as DoorDash, Grubhub, and Uber Eats', and certification is with the middleware, not the marketplaces - 'The supported functionality is certified through the UrbanPiper Atlas portal. Validations with delivery aggregators are not included'. The menu bullets are real ('Add or update menu - Add or update menu in UrbanPiper through InfoGenesis.', 'Category timing groups (daypart schedule) - Send schedules to UrbanPiper to associate them with the categories in the menu.') but they are middleware-mediated and 'This integration is supported for SaaS customers only.'. The second conjunct fails absolutely: no per-item sync-status or rejection-error surface is published (`publish status` occurs ZERO times across the entire 8,068-document estate and `sync status` zero times across all 5,595 InfoGenesis topic bodies - its single help-corpus hit is an Eatec purchase-order draft-save note), which is exactly the silent-failure mode an IG OnDemand 12.3.15.8 bug fix describes - 'Menu publish failed to sync to the UrbanPiper portal when more than three sites were configured.' A partial requires a named shortfall the evidence supports; here neither half of the claim is met, so the honest value is `no`. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IGCM/12.3.14_RN/Contents.htm · retrieved 2026-09-12 adversarially verified

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

menu-pricing-dynamic-pricing

Rule-based automatic variation by time and channel is documented: Price Tier Schedule holds dated schedules ( "no two price tier schedules can have the same starting date"), Price Tier Mapping assigns tiers by product class and revenue category within a schedule, Daypart Date Based Schedule switches Price Level and Check Type by date and time range, and Schedule Price Change applies a percentage or amount over a date range with rounding and auto-revert. Shortfall: nothing varies price by demand, inventory or sell-through - every rule is calendar or channel driven - and there are no floor/ceiling guardrails on the computed price (Schedule Price Change offers only Up/Nearest/Down rounding). https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Price%20Tier%20Mapping.htm · 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

Independently verified against the Solution Partners directory: Adyen, Elavon, Freedom Pay, Global Pay, Shift4, Verifone, Tyro, Windcave, Ingenico and POST are all named. Nine competing processors/gateways certified is genuine evidence that Agilysys Pay is elective. Same evidence upholds commercial-processing-not-bundled. https://www.agilysys.com/en/solution-partners/ · retrieved 2026-08-01 adversarially verified

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

payments-published-rates

The Agilysys Pay page describes the platform in detail and publishes no rate, markup, or per-transaction figure. https://www.agilysys.com/en/products/pay/ · retrieved 2026-08-01

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

The storage half exists: items carry multiple price levels, and Terminal Option 60 'Set price levels based on tender type' re-prices 'all items at the time of tender', which is the cash-price switching mechanism. Shortfall: no dual-pricing or cash-discount mode is documented as such - nothing prints both cash and card totals on the guest check or receipt, and no cash-discount program appears in the help centre or on agilysys.com. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Auto%20Price%20Level.htm · retrieved 2026-08-03

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

Surcharging is gateway-delegated rather than a POS engine: Adyen surcharge support is documented for credit cards only, Australia region only, configured in the Adyen portal ('Properties must work with Adyen to configure the surcharge percentage') and 'cannot be removed in POS terminal'; IG OnDemand adds a configurable Surcharge Percentage for DataCap tenders at enterprise/store/tender level with optional tax-on-surcharge. Shortfall: no BIN/product-code debit or prepaid exclusion performed by the POS and no network-percentage-cap enforcement is documented; per-location control exists only as the store-level percentage field. https://ig.onagilysys.com/help/POS/IG_12UX/ReleaseNotes/Adyen%20Surcharge%20Support.htm · retrieved 2026-08-03

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

payments-emv-nfc

Agilysys Pay supports EMV chip, NFC tap-to-pay and mobile wallets including Apple Pay and Google Pay across first-party terminals and handhelds. https://www.agilysys.com/en/products/pay/ · 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

"InfoGenesis POS supports Apple Tap to Pay functionality on iPhone, enabling contactless card payments directly on supported iPhone devices." Two function buttons ship for it - Tap to Pay on iPhone (#2095) and How to Tap & Pay (#2120) - and the documented envelope is Adyen or Tyro gateway, United States, iPhone 14 and above, Wi-Fi, NFC only, Visa/Mastercard/Amex/Discover, with the IG POS app and the Agilysys Pay Adyen iOS app on the same iPhone and Terminal Option 1465 enabled. Shipped in 12.3.15 (Using InfoGenesis POS 12.3.15). Android tap-to-pay is not documented; the claim allows either. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Apple%20Tap%20to%20Pay%20on%20iPhone.htm · retrieved 2026-08-08

Vendor ships a handheld that takes EMV/NFC payment at the table, including tip prompt and check splitting, without carrying the card away.

payments-pay-at-table

IG Fly is a rugged all-in-one handheld with P2PE, EMV, NFC and mobile wallets for tableside payment; Agilysys Pay documents pay-at-table via handheld terminals. https://www.agilysys.com/en/products/ig-fly/ · retrieved 2026-08-01

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

IG OnDemand Full Service user guide: staff create a check at the POS terminal (with or without a table number) and print it; 'This check has a QR code, which guests can scan' to order and to pay at the table from their own mobile device. Supported tenders are Cash, Credit Card, Room/Member Charge, Loyalty, Stripe Wallet and GA; partial payments are supported and the tender is applied to the POS check itself. Separately documented: Terminal Option 1522 prints a PayQR on split-check receipts so each guest pays their own split, and IG Fly function Save + Payment QR (#544) prints a receipt whose QR opens a payment URL. https://ig.onagilysys.com/help/POS/IG_OnDemand/UserGuide/IG%20OnDemand%20Full%20Service.htm · retrieved 2026-08-06

Supports both pre-auth-then-tip-adjust and on-device tip prompt flows, with a documented batch/adjust window and a manager screen for unadjusted tips.

payments-tip-adjust

Both flows are documented. Pre-auth-then-adjust: Authorize holds the card on an open check and the user completes payment "later while closing the check or adding a tip", with Modify Auth to increase the hold. On-device prompt: Terminal Option 522 prompts for the tip on the external payment device (with 82 and 524), or 528 keeps tip and signature on the terminal. The adjust window is documented on the Adyen side - with Adyen.ImmediateSettlement true, sales settle immediately and PAC authorizations "shortly after the closed check is uploaded"; set false, everything settles at a daily batch time the customer schedules with Adyen, after which "this prevents the authorization on the open check from being increased, even if it is to add a tip" (error: No time left for over authorisation). Shortfall: no manager screen listing unadjusted tips - the closest surfaces are the Universal Desktop Credit Card Settlements form and the Tip Transfer Detail / IRS Tips reports, none of which is described as an unadjusted-tip worklist. https://ig.onagilysys.com/help/POS/IG_12UX/ReleaseNotes_12.3.13/Agilysys%20Pay%20Adyen%20Authorization.htm · retrieved 2026-08-08

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

Per-employee allocation and movement exist: Tip Transfer moves any portion of one employee's tip balance to another named employee (with Terminal Option 131 to pick from a list, self-transfer blocked, and an Additional Tip Transfer prompt for the remainder), Tip Payout withdraws tips, gratuities and service charges to an employee with a signed chit and cash-drawer release, and the IRS Tips Report computes per-employee "Tips, Grats and Transfer = Charged Tips + Declared Cash Tips + Gratuities + Tips Transferred In - Tips Transferred Out" with Employee ID and Secondary ID, printable and exportable (Tip Transfer Detail Report likewise). Shortfall: no tip-pool construct - there is no rule that distributes a pool by hours worked, sales, role percentage or points; distribution is a manual employee-to-employee transfer keyed in at the terminal, and no topic in any of the five Reports books describes a pool allocation. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Tip%20Payout.htm · retrieved 2026-08-08

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

IG Flex documents an 'offline transaction mode' continuing to accept orders AND payments during connectivity loss, syncing on restore; per-transaction and cumulative caps are not published. https://www.agilysys.com/en/products/ig-flex/ · retrieved 2026-08-01

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

OVERTURNED from `no`. The prior rationale asserted no "failed-offline-payment report" exists; the InfoGenesis Reports Guide documents exactly one. The Credit Card Exception Report "provides details of all credit card transactions that are not fully processed or that are pending", is populated from the Payment_Card_Settlement table, and its field list carries the offline discriminator directly: an `Offline` field, "Flag indicating if terminal was offline when transaction was done", which is also one of the report's filters; a `Status` field whose "Possible values are: Successful, Pending, Retry, Partial, Failed, and Real-Time", with Pending, Failed and Partial selected by default; a `Repost Count` -- "The number of times transaction was reposted (When a transaction fails, it is possible to Repost it and try it again.)"; and `Error Code` / `Error Message`. So the post-reconnect view of failed stored transactions is published, per book (the same report appears in IG_Kiosk, IG_OnDemand and IG_Fly). `partial` because the other half of the claim is still unmet: no Agilysys document allocates the LOSS on a post-reconnect decline. The nearest published sentence is a risk statement about a different control -- the Credit Card Bypass Agency limit is "the credit card dollar amount that the customer is willing to risk" -- which places pre-authorisation risk on the operator but says nothing about who eats a stored offline transaction that declines. Grade B: the vendor's own product documentation. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/Credit%20Card%20Exception%20Report.htm · retrieved 2026-09-09

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

Closed-loop Agilysys Gift Card with real-time activation and balance tracking, redemption across lodging, dining, spa, golf, retail and online channels, and centralized liability/breakage reporting. https://www.agilysys.com/en/products/gift-card/ · retrieved 2026-08-01

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

payments-house-accounts

Room-charge posting to the PMS folio and InfoGenesis charge sync to catering group accounts are documented; per-account credit limits and periodic statements are not. https://www.agilysys.com/en/products/sales-and-catering/ · retrieved 2026-08-01

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

Missed evidence. The IG Quick Pay page states the solution 'supports split payments and multiple payment methods including credit cards, digital wallets, room charges, and casino accounts', and the POS Terminal app listing documents payment 'with multiple payment methods such as cash, credit cards, generic authorization, gift cards or coupons'. Scope note: split is documented for the QR guest-pay channel; server-driven split tender at the terminal is inferred, not stated. https://www.agilysys.com/en/products/ig-quick-pay/ · retrieved 2026-08-01 adversarially verified

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

Void reasons carry a 0-9 security level - 'setting a security level greater than the signed-on server/cashier forces the terminal to prompt for a manager override when selecting the void reason' - and void/refund rights hang off job-code functions (5 Void Check, 46 Void Item) plus refund terminal options (28, 477, 1268, 1477). The approver is recorded and queryable: the Voided Checks and Refund Return Void Detail reports carry Auth Employee / Auth Employee ID as grouping, sorting and filter dimensions. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Reason%20For%20Void.htm · retrieved 2026-08-03

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

payments-chargeback-tooling

Positive absence by bounded enumeration over the publisher's own corpus. `chargeback`, `dispute`, `disputed`, `representment`, `retrieval request` and `evidence submission` occur ZERO times across all 7,051 help-topic bodies; the 124 `dispute` hits in the wider 8,068-document estate (35 documents) are legal dispute-resolution clauses in the regional Terms or 10-K risk language, and the 9 `chargeback` hits (8 documents) are marketing ('minimizes chargebacks' on the Agilysys Authorize page) or 10-K risk text. The two in-product surfaces where a dispute queue would live carry none: the Settlements utility's complete field table is Settlement Type, Task Status, Start/End Date, Search, Refresh, Select All, ID, Tendered Time, Name, Check Number, Amount, Status, Account Number, Tip, Tax, Tender Id, Terminal ID, Profit Center, Meal Period ID, Cashier ID and Merchant ID, and the card-related ReportsGuide reports are Credit Card Exception, Refund Return Void Detail/Summary and PMS Settlement Status. A gateway's own merchant back office (Adyen, Tyro, FreedomPay) is not an in-product dashboard, so it cannot satisfy the claim. The POS help system is the right publisher for an in-product dashboard, which is what makes this a `no` rather than an `unknown`. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Settlements.htm · 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

Overturns a title-only zero. The 12.3.14 PeopleVine integration creates four dedicated tenders - House Credits, House Accounts, Card on File and Auto - and defines the third: 'Card On File tender refers to the member’s card stored information to facilitate faster future payments.' The same tender is documented for 12UX POS Terminal, IG Fly, IG Kiosk and IG OnDemand, so one stored credential is reusable across in-store, handheld and online/kiosk ordering, and the credential is held in the PeopleVine portal rather than in the POS. SHORTFALL: it is not first-party - it exists only through the third-party PeopleVine membership platform and 'must be enabled for the member’s account in the PeopleVine portal'; it is scoped to club/loyalty MEMBERS rather than any guest profile; no phone-order channel is documented; and the topic never states that the stored credential is tokenized. `card on file` appears in 4 of 7,051 topic bodies and all four are this integration. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IG_12UX/12.3.14_RN/PeopleVine%20Integration.htm · retrieved 2026-09-12 adversarially verified

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

payments-payout-timing

This claim is a publication test and the publication is affirmatively absent. `deposit schedule`, `funding schedule`, `next-day`, `same-day` and `instant funding` occur ZERO times across the entire 8,068-document estate, and the single words resolve to unrelated senses on inspection (all 152 help-corpus `payout` hits, in 45 topics, are TIP payout - POS function #12 - and the 88 `deposit` hits are hotel room deposits and eCash account funding; `funding` in the PDFs is board-committee and pension language). The only first-party statement on timing is about merchant-to-gateway CAPTURE and it hands the schedule to the processor: the 12.3.13 Agilysys Pay Adyen Authorization note says Adyen.ImmediateSettlement defaults true so pay-at-counter and pay-at-table sales settle on completion, and that when it is set false: 'The customer must contact Adyen to schedule the daily batch settlement time.' So Agilysys neither publishes a deposit schedule nor offers a funding option of its own; funding is a gateway matter set outside the product. Agilysys is not the acquirer, which is why the absence is a property of what it publishes rather than a gap in our reading. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://www.agilysys.com/en/terms-and-conditions/ · retrieved 2026-09-12 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

The Settlements utility "displays the status of various types of payment transactions" filtered by Settlement Type, Task Status and date range, and each row carries both a Profit Center and a Merchant ID (the topic states the Merchant ID column shows the profit-center-associated identifier) alongside Terminal ID and Cashier ID - so distinct MIDs per outlet settle under one queryable view, and IGCM supports either a Centralized Configuration Management hierarchy or multiple independent enterprises per concept (Example 3: Multiple Independent Enterprises, which warns that in the independent model "it is not possible to roll up reporting to see an overview of the entire enterprise"). Shortfall: no destination bank account is configured or shown anywhere in the POS - fund routing lives with the Adyen/Tyro/FreedomPay merchant account, and no topic documents split settlement or per-entity disbursement rules. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Settlements.htm · retrieved 2026-08-08

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

PCI-validated P2PE and tokenization are stated on Pay, Kiosk and Flex pages; no PCI DSS 4.x AoC or P2PE listing reference is published and no trust center exists. https://www.agilysys.com/en/products/pay/ · retrieved 2026-08-01

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

IG KDS 'Real-Time Routing' sends orders to named prep stations (Fry, Grill, Pantry). Whether routing rules are operator-editable without vendor involvement is not stated, and reviews suggest configuration work is billable. https://www.agilysys.com/en/products/ig-kds/ · 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

'Master & Prep Views' give expeditors a complete order overview while prep teams get focused task lists with real-time bump updates. https://www.agilysys.com/en/products/ig-kds/ · 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

InfoGenesis POS Terminal 12UX User Guide, Ordering Items By Course: 'Advance Course' groups check items into numbered courses (max 25 per check, course number shown on the check); 'Modify Course' reassigns an item to another course from a prompt listing the check's courses; 'Fire by Course' fires all items in a nominated course and states 'The items in the course can be on hold and fired later.' 'If a check with course is fired, the course numbers are also sent to the kitchen printer or kitchen video.' The same Fire by Course and Ordering by Course functions are documented for IG Fly (handheld), and IG KDS renders Course Number on Chit, Course Timers on Expo and Expand/Collapse Courses in the Expo chit. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Ordering%20Items%20By%20Course.htm · retrieved 2026-08-08

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

Routing is described as timed 'so every dish is ready at the same time', implying pacing; per-item cook times and staggered start logic are not documented. https://www.agilysys.com/en/products/ig-kds/ · 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 entire evidence base is one IG KDS marketing bullet — 'Smart order throttling automatically balances demand with kitchen capacity'. No capacity units, no per-channel caps, no configuration surface, no doc. The same sentence was scored 'partial' at order-capture-throttling, so the dossier grades one claim two ways; the conservative grade should win. https://www.agilysys.com/en/products/ig-kds/ · retrieved 2026-08-01 adversarially verified

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

The UrbanPiper integration note (IGCM 12.3.14) publishes outbound availability propagation the earlier title sweep missed: 'Store toggle - Manage store availability in real time' and 'Menu toggle (items and modifiers) - Manage item and modifiers availability in real time', pushed from InfoGenesis into UrbanPiper, 'which in turn manages all aggregator-specific interactions' for DoorDash, Grubhub and Uber Eats. SHORTFALL: it runs through third-party middleware rather than a direct marketplace connection, it is 'supported for SaaS customers only', and the note describes availability toggles without stating that a POS- or KDS-side 86 automatically triggers the push - the documented 86/un-86 propagation (IG_OnDemand Sync 86 Un86 Status, terminal options 290/293/530/1314) still moves only between Agilysys surfaces. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IGCM/12.3.14_RN/Contents.htm · retrieved 2026-09-12 adversarially verified

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

IGCM 12.3.14 lists, under Order Management, 'Order status update - Send order status updates to UrbanPiper' - an outbound status path from InfoGenesis to the aggregator middleware, which the 2026-08-08 pass could not see because it swept titles only. SHORTFALL: the note neither enumerates the statuses nor names the trigger, so a KDS bump is not documented as the event that fires it; the only KDS-bump callback that IS specified (IG KDS Update Kitchen Order Status in IG OnDemand) terminates at Agilysys’s own ordering app and is 'applicable to the whole order and not for specific items'; and no courier-dispatch semantics appear anywhere. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IGCM/12.3.14_RN/Contents.htm · retrieved 2026-09-12 adversarially verified

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

kitchen-bump-bar-hardware

IG KDS User Guide, Bump Bar: a manufacturer/model/connectivity table naming TG3 Electronics KBA-A4473-BB20-TE-TU-HOR 1829 (USB), QSR Automations KP-9000 (Bluetooth) and QSR Automations KP-7500 (USB). The companion topic /UserGuide/Bump Bar Support.htm describes it as 'a hardware peripheral used in IG KDS Prep Expo and Kitchen Master Expo operations without a touch screen ... a 20-key bar with a USB connector', usable vertically or horizontally, and enumerates the keys: Tab Left, Tab Right, Search, Reset, Left, Right, First, Last, Up, Down, and 1/Expand, 2-5, 6/Cook, 7/Bump, 8/Recall, 9/Priority, 0/Print. /UserGuide/Configuring Actions for Bumpbar Keys.htm documents programmable top-row (1-0) and bottom-row (a-j) key assignment. Shipped in the separately licensed IG KDS module rather than base InfoGenesis POS. https://ig.onagilysys.com/help/POS/IG_KDS/UserGuide/Bump%20Bar.htm · retrieved 2026-08-08

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

kitchen-all-day-counts

IG KDS 12.3.15 release note, Group Items by Modifiers in Item Summary: 'items with multiple modifiers are grouped under the item in Item Summary, with counts displayed at both item and modifier level. When an item is bumped, the count is reduced from both the item and modifier summary.' Worked example: Lamb Chops with Medium Rare/Feta x2 and Well Done x2 shows total count 5 with per-modifier counts. It is enabled by an 'Advanced Item Summary' checkbox at POS Configuration > Kitchen > Display Settings > Summary Table; supported on both prep and master expo; 'Hold and void items are not displayed in the item summary'; an item routed to multiple stations 'is included in the item summary of each station where the item is visible', i.e. the aggregate is per station. Opened from the bottom bar of the expo (/IG_KDS/UserGuide/Display Item Summary in Expo.htm). Documented shortfalls: special instructions unsupported, bump-bar operation of the summary unsupported. https://ig.onagilysys.com/help/POS/IG_KDS/12.3.15_RN/Group%20Items%20by%20Modifiers%20in.htm · retrieved 2026-08-08

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

IG KDS release note / User Guide, Long Wait Alert in Expo Chit: 'the color of the chit in the expo can be changed to indicate that an order is in progress for a long duration. Users can configure the preferred color and duration after which the color must be changed. This setting takes precedence over all other chit color configurations.' Configuration is at POS Configuration > Kitchen > Display System > Orders, checkbox 'Late order color', which reveals a 'Later Order Color Control' submenu whose rows take Time (mm:ss) - 'the time in mm:ss after which the color of the chit must change to the color configured' - and Color (picker or hex). 'A maximum of three records can be configured', i.e. three-stage visual escalation. Because the Display System record is per kitchen display, targets are set per station; /IG_KDS/UserGuide/Assign Chit Color for Fulfillment Types.htm additionally colours chits by order type, and /12.3.15_RN/Display Chit Timer Until Order is Delivered.htm runs a live chit timer. Shipped in the separately licensed IG KDS module. Audible alerting is not documented - the claim's 'and/or' is met by the colour escalation. https://ig.onagilysys.com/help/POS/IG_KDS/ReleaseNotes/Long%20Wait%20Alert%20in%20Expo%20Chit.htm · retrieved 2026-08-08

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

Automatic fallback exists on both paths, but neither is a designated backup with a no-ticket-loss guarantee. Printer path: with Terminal Option 150 'the receipt printer prints the kitchen chits when the kitchen printer fails to print chits', and Terminal Option 1464 raises cause-specific error prompts (unreachable, out of paper, door open, service stopped) with a Print Locally button - the safety net is the terminal's own receipt printer, and the config guide states outright that 'alternate kitchen printers are not backup or fail-over printers'. KDS path: unroutable items 'will be sent to the expo handling most items in the order' automatically and are color-flagged, but if no station can take the order 'the entire order will be rejected, and failed order email notification will be sent' - ticket loss is possible. https://ig.onagilysys.com/help/POS/IG_KDS/UserGuide/Send%20Unroutable%20Items%20to%20Available.htm · retrieved 2026-08-04

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

kitchen-offline-operation

InfoGenesis states kitchen jobs and check data automatically reconcile when the network restores, implying local queueing; not stated as an explicit offline KDS guarantee. https://www.agilysys.com/en/products/infogenesis-pos/ · retrieved 2026-08-01

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

IG KDS User Guide, Displaying Modifiers and Nested Modifiers: 'The modifiers and nested modifiers for an item are shown below the item in the station display. A modifier is shown one level below the item, and a nested modifier is shown one level below the modifier' - a full indented modifier breakout, not just ticket line text. /IG_KDS/UserGuide/Prepare Portions of Item Across Multiple Stations.htm adds item-level build detail of a sort: 'An item can be split into multiple portions. Each portion can be routed to different kitchen departments and stations. Each station prepares and bumps its portion independently. The item is completed only after all portions are bumped' (worked example: Station A prepares the chicken, Station B the salad of a Chicken Salad), and the master expo shows each station's status. Related: Promote Modifier to Item, Display Package Names next to Items and Modifiers in Expos, Print Separate Chit for Guests with Dietary Instructions. SHORTFALL: nothing in the 582-topic IG KDS set documents recipe steps, ingredient quantities, portion weights or cooking instructions on the station screen - a regex sweep of every IG KDS topic path and title for recipe/build/assembly/instruction returns only the dietary-instruction chit and the portion-routing topic. Recipes live in the separately licensed Eatec module and are not documented as surfacing on a KDS station. https://ig.onagilysys.com/help/POS/IG_KDS/UserGuide/Displaying%20Modifiers%20and%20Nested.htm · retrieved 2026-08-08

Sectioned/fractional topping placement (halves, quarters, specific sections) is rendered visually and unambiguously on the make-line screen or ticket. differentiator

kitchen-pizza-fractional-display

CLAIM: sectioned/fractional topping placement rendered on the make-line screen or ticket. VERDICT: no. The POS has no placement attribute to render (the Modifier form's 11 submenus carry none - see menu-pricing-fractional-placement), and the KDS modifier rendering is purely hierarchical. EVIDENCE: https://ig.onagilysys.com/help/POS/IG_KDS/UserGuide/Displaying%20Modifiers%20and%20Nested.htm: 'The modifiers and nested modifiers for an item are shown below the item in the station display. A modifier is shown one level below the item, and a nested modifier is shown one level below the modifier.' IG_KDS/UserGuide/Station Displays.htm: 'modifiers are displayed one level below the item'. The modifier's kitchen-facing fields are Kitchen Printer Text, Kitchen Video Text, Kitchen Video Category/Department and Cook Time (ConfigGuide Basic Details_65 and Kitchen Video) - no side or section. POISON: IG_KDS/UserGuide/Prepare Portions of Item Across.htm ('An item can be split into multiple portions. Each portion can be routed to different kitchen departments and stations') is prep routing of whole components to stations, not spatial sections; 'Modifiers are displayed only under the portion routed to the modifier's department' confirms portions are department routes. BOUND: raw-HTML census of ig.onagilysys.com/help/POS, 2026-09-16 (HelpSystem.xml BuildTime 9/16/2026 3:19:59 PM): 7 MadCap help systems (IG_12UX 1,724, IG_Kiosk 1,238, IG_OnDemand 923, IG_Fly 918, IG_KDS 595, IG_DMB 59, IGCM 99 TOC entries = 5,556 topics), all 200; href fixpoint over 55,577 in-body .htm links added ZERO topics outside the TOC; a nonsense path returns a real 404 (WebContentNotFound), so no soft-200. Plus 71 superseded 12.3.16_RN topics that are still served but no longer in the TOC (replaced by 12.3.16.1_RN), read from the q310 cache: CORPUS 5,627 bodies, comments/scripts stripped, tokenised word-boundary case-insensitive controls (.cache/q316/agilysys/controls.mjs). CONTROLS as for fractional placement: half 2 / quarter 4 / fraction 2 / sectioned 0 / 'on the side' 0 / placement 18 - all poison, none a topping section. Retrieved 2026-09-16. https://ig.onagilysys.com/help/POS/IG_KDS/UserGuide/Displaying%20Modifiers%20and%20Nested.htm · retrieved 2026-09-16 adversarially verified

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

kitchen-recall-refire

IG KDS 12.3.15 release note / User Guide, Reopen Delivered Chits and Items: 'IG KDS has been enhanced to allow users to reopen delivered chits and individual items directly from the Closed tab.' The behaviour table states that on reopening a chit it 'moves it to the Open tab with Start status. All items are reset to Yet to Start', and that 'When a single item is reopened, only that item is reset. Others remain bumped' - item-level refire without re-entering the order. It also documents the pre-existing recall path: 'If the chit is not marked as delivered, only recall will be available within the configured time.' Gated by 'Enable Reopen for Delivered chits' plus 'Enable Item wise Bumping' and 'Enable Item Level Actions on Chit' at POS Configuration > Kitchen > Display System > Orders. Recall is also a dedicated hardware key - key 8 / Recall on the 20-key bump bar (/IG_KDS/UserGuide/Bump Bar Support.htm) - and 'Order recalled' / 'Order reopened' are among the Master Expo transitions pushed back to IG OnDemand. Reprint is available as bump-bar key 0 / Print. Shipped in the separately licensed IG KDS module. https://ig.onagilysys.com/help/POS/IG_KDS/12.3.15_RN/Reopen%20Delivered%20Chits%20and.htm · retrieved 2026-08-08

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

IG KDS User Guide, Highlight Order Changes on Expo chit: 'Order changes on expo chits can be highlighted in real-time. A bell icon is displayed on the chit header and next to the specific item or course and is displayed until the update is acknowledged by tapping the header' - the flag is item-level, on the live ticket, and requires acknowledgement. The companion topic /ReleaseNotes/Display Check Modifications on Expo.htm enumerates the POS-side changes propagated to a displayed chit (Seat, Course, Check Label, Check Type, delivery details, Table number, Server name, Profit center, Room number, Cover count), notes 'Previously, modifications done will reflect only when a new item is added to the recalled check. With this enhancement, modifications will reflect even if a new item is not added', and requires Terminal Option 156 (Use real-time kitchen video interface). Documented caveats: for Kiosk and OnDemand orders modifications reach the expo only when Pay at Cashier is the payment method; only fields ticked in Display Preferences (POS Configuration > Kitchen > Kitchen Operation) are shown; after a split check no add/void should be made to parent or child chit. Shipped in the separately licensed IG KDS module. https://ig.onagilysys.com/help/POS/IG_KDS/UserGuide/Highlight%20Order%20Changes%20on.htm · 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

IG KDS's Notification Info settings page documents Enable SMS Notification, Enable Email Notification and Enable App Notification when Order is Bumped, selectable item-wise, station-wise or order-wise, with editable templates defaulting to 'Your order number {{N}} is ready to pick up at Counter {{Counter}}', plus separate Dine In / Take Away templates and a distinct Order Arrival notification. Shortfall: the capability lives in IG KDS, a separately licensed companion SKU, not in base InfoGenesis POS, so the claim's 'without a separate product purchase' condition is not met. https://ig.onagilysys.com/help/POS/IG_KDS/UserGuide/Notification%20Info.htm · retrieved 2026-08-02 adversarially verified

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

kitchen-waste-logging

The back-office half is fully documented: Eatec Inventory Management > Spoilage and Loss takes Location, Post Date, a Reason drop-down ('The cause of spoilage'), Reference, Remark, Approved By, Department and an item list, with Inventory Depletion by Spoilage for Configured Location and the Spoilage/Loss Detail [INV61] and Summary [INV61S] reports. SHORTFALL: the claim requires entry at the kitchen/KDS screen and there is none. Across all 5,595 InfoGenesis topic BODIES (IG KDS’s 595 and the 92 Server 12.x topics included) `spoil`, `remake` and `reason code` occur ZERO times and `waste` occurs twice, both the IG OnDemand cutlery prompt default 'Help us reduce plastic waste - only request cutlery when needed'; the documented KDS operator action set is Expand, Cook, Bump, Recall, Priority and Print with chit and item bump/reopen, and no waste function. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://eatec-userguide.onagilysys.com/UserGuide/Creating%20Spoilages%20and%20Loss.htm · retrieved 2026-09-12 adversarially verified

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

IG KDS Reports Guide, Speed of Service: 'This report calculates the average bump time for orders along with the total orders count', with fields Station ('the name of the prep or the master expo'), Average Bump ('the total time taken to bump all the orders in the station divided by the total count'), Average Delivery Time (mm:ss), Total Count and Average ('average delivery time across departments and meal periods'); grouping by Department / Meal Period / Station and filters Meal Period, Stores, Level - so per-station and per-daypart slicing are both native. /IG_KDS/ReportsGuide/Kitchen Reports.htm adds KDS Estimated vs Actual Order Detail at order level with Actual Queue Time, Actual Attending Time, Actual Prep Time, Actual Delivery Time, Actual Fulfilment Time and Estimated vs Actual variance, sliced by Fulfilment Type and by Source, whose values are 'OnPrem orders - Kiosks and IG terminals' and 'Cloud orders - OnDemand and third-party orders' - i.e. order channel. Export: /IG_12UX/ReportsGuide/Report Generation Overview.htm states reports are 'printed or viewed on-screen, published with Adobe Acrobat, analyzed with Microsoft Excel, or exported to other programs'. SHORTFALLS: every documented time metric is a mean - no percentile (p50/p90) statistic appears in either report's field table; no CSV or reporting-API export format is named, only Acrobat/Excel/'other programs'; and the reports are in the separately licensed IG KDS module. https://ig.onagilysys.com/help/POS/IG_KDS/ReportsGuide/Speed%20of%20Service.htm · retrieved 2026-08-08

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

Eatec (separately licensed Inventory & Procurement module) User Guide, Production Plan: 'Eatec provides solutions to plan production of finished goods and inventory items. Users can post production from planning ... Production plans use finished goods, inventory items, existing production plans, or item history based on: Production, Requisitions, Transfers, Usage', with functions Create/Modify/Duplicate production plan, Production plan analysis, View production plan summary, Print production plan, Print production plan worksheet, Viewing production plan history and Posting production from production plan. /UserGuide/Sales Forecasting.htm: 'used to forecast the product sales in a defined location within a defined date range ... can be segmented by user provided period length and periods ... the sale forecast ... can be exported to other verticals of Eatec such as shopping list and worksheet.' /NewFeatures/Consolidated Quick Orders Report Enhancement - Recipe-Level Quantities for Production Planning.htm supplies recipe-level quantities. SHORTFALLS: the deliverable is a printed back-office production-plan worksheet, not a daily prep task list surfaced to kitchen staff on a screen - no IG KDS topic (582 walked) mentions prep lists or forecasts; the forecast basis documented is item usage/transfer/requisition history and a user-defined sales plan rather than an automatic demand model; and all of it requires the separately purchased Eatec module, not InfoGenesis POS. https://eatec-userguide.onagilysys.com/UserGuide/Production%20Plan.htm · retrieved 2026-08-08

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

Re-evidenced 2026-08-08. InfoGenesis does carry a Delivery order type, but the whole of it is the Add Delivery Details function, which 'is used to input the following delivery information while sending an order to the KDS and get the same printed on kitchen printer chits as well: Customer name, Delivery type, Phone number of the customer, Address for the delivery, Pick up time of the order, Postal Code..., Cutlery'. Drivers are not entities anywhere in the 1,691-topic help set - no driver clock-in state, no in-store/on-run/returning status, no per-driver run history report among the 122 documented reports. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Add%20Delivery%20Details.htm · retrieved 2026-08-08 adversarially verified

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

Re-evidenced 2026-08-08. The delivery order type ends at the Add Delivery Details prompt, whose output is 'displayed in the KP chits based on the configuration in the Universal Desktop and the IGCM'. Nothing in the 1,691-topic help set is a dispatch or expo screen: no undispatched-order queue, no driver availability pane, no elapsed-time-per-order view and no multi-order run batching. The IG KDS guide covers kitchen routing only. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Add%20Delivery%20Details.htm · retrieved 2026-08-08 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-evidenced 2026-08-08. The delivery record is 'Enter Address' plus 'Enter Postal Code' typed at the terminal and printed on the kitchen chit; the documented field table lists no map, geocode, latitude/longitude or stop-order field. No topic in the 1,691-topic InfoGenesis help set concerns routing, map view or multi-stop sequencing. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Add%20Delivery%20Details.htm · retrieved 2026-08-08 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-evidenced 2026-08-08. The InfoGenesis Help Center publishes exactly six help sets - POS Terminal, IG Kiosk, IG OnDemand, IG Fly, IG KDS, IG Digital Menu Board - i.e. the only first-party mobile apps are the IG Fly/IG Flex staff handhelds and the IG OnDemand guest ordering app. No driver application exists, and no topic in the 1,691-topic set concerns GPS position, live location or driver tracking. https://ig.onagilysys.com/help/POS/IG_12UX/Sitemap.xml · retrieved 2026-08-08 adversarially verified

Delivery areas can be defined as arbitrary map polygons or by drive-time isochrones, not solely as a radius or a ZIP/postcode list. differentiator

delivery-zones-polygon

Re-evidenced 2026-08-08. The Add Delivery Details topic tables every field captured for a Delivery-type check: Customer Name, Delivery Type, Mobile Number, Email Address, Address, Postal Code, Pickup Date and Time, Cutlery. There is no zone, area, radius, isochrone or postcode-list construct in that table or anywhere in the 747-topic IGCM Configuration Guide. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Add%20Delivery%20Details.htm · retrieved 2026-08-08 adversarially verified

Each delivery zone carries its own independently configurable delivery fee, order minimum, and quoted promise time, applied automatically from the validated customer address.

delivery-zone-pricing

The delivery configuration is enumerated in the site entity Logistics submenu - button/kitchen/confirmation text, check type, cutlery choice, and delivery to pre-configured on-property locations chosen from an assigned-location drop-down with per-location QR codes; the guest types a free-text address at checkout. No delivery zone, zone fee, order minimum, promise time or address-validation construct appears anywhere in the delivery documentation. This is hospitality room-service-style delivery, not zoned street delivery with per-zone economics. https://ig.onagilysys.com/help/POS/IG_OnDemand/UserGuide/Delivery%20Fulfillment%20Type.htm · retrieved 2026-08-03

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

Re-evidenced 2026-08-08, correcting the earlier reasoning: address entry DOES exist. For the Delivery type, Address and Postal Code are Mandatory (Dine-in and Pick-up make them Optional). But the documented behaviour is plain entry - 'Enter Address: Enter the address of delivery' - and the topic's complete field table shows no lookup, geocode, mapping-service call, or out-of-zone check. The only enforcement documented is mandatory-field presence and, for Pick Up or Delivery, that the user 'must provide input for either Mobile Number or Email Address to proceed further'. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Add%20Delivery%20Details.htm · retrieved 2026-08-08 adversarially verified

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

Re-evidenced 2026-08-08. Withdrawing the earlier claim that Agilysys has no labor module - InfoGenesis does record time punches and publishes Clock Activity, Clock Detail, Current Clock In and Labor Summary reports. What does not exist is any driver: no driver entity, no mileage or distance field, no per-delivery reimbursement construct and no reimbursement-vs-wage export in the 1,691-topic help set or the 122 documented reports. The delivery order type captures only customer contact details for the kitchen chit. https://ig.onagilysys.com/help/POS/IG_12UX/Sitemap.xml · retrieved 2026-08-08 adversarially verified

Provides a driver cash bank / settle-up flow that reconciles cash collected, orders assigned, and tips owed at end of shift, producing a per-driver over/short figure.

delivery-cash-reconcile

Re-evidenced 2026-08-08. The 122 documented InfoGenesis reports include Cashier Tender Shift, Terminal Tender Shift, Cashier Performance, Server Sales, Server Shift Sales Tips and Gratuity and Tip Transfer Detail - settlement is modelled per cashier, terminal and server. No driver bank, driver settle-up or per-driver over/short report exists, and no driver entity exists in the 1,691-topic help set to attach one to. https://ig.onagilysys.com/help/POS/IG_12UX/Sitemap.xml · retrieved 2026-08-08 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

Re-evidenced 2026-08-08. No topic in the 1,691-topic InfoGenesis help set mentions DoorDash, Uber, Nash, Relay, courier or delivery dispatch of any kind; the ConfigGuide's Interfaces section covers PMS, casino and payment interfaces. Agilysys' own Solution Partners directory carries 31 categories with no courier or delivery category, and delegates Online Mobile Ordering to third parties (OLO, Ssnapp, Tapingo). There is no native courier handoff and no quote/status return into the check. https://ig.onagilysys.com/help/POS/IG_12UX/Sitemap.xml · retrieved 2026-08-08 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

Re-evidenced 2026-08-08. Hybrid overflow needs both halves and InfoGenesis documents neither: no driver entity or assignment state anywhere in the 1,691-topic help set, and no courier/marketplace integration topic. There is likewise no rules engine keyed on wait threshold or zone - the delivery order type is a set of chit fields. https://ig.onagilysys.com/help/POS/IG_12UX/Sitemap.xml · retrieved 2026-08-08 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

Re-evidenced 2026-09-12 on first-party documentation rather than the partner roster. The claim excludes marketplace connectivity 'solely resold through ... middleware', and middleware is exactly what Agilysys documents: IGCM 12.3.14 integrates InfoGenesis with UrbanPiper, 'a middleware platform that connects POS systems to multiple online food delivery aggregators, such as DoorDash, Grubhub, and Uber Eats. Instead of integrating separately with each aggregator, InfoGenesis communicates directly with UrbanPiper, which in turn manages all aggregator-specific interactions.' Certification is with the middleware - 'The supported functionality is certified through the UrbanPiper Atlas portal. Validations with delivery aggregators are not included' - so no vendor-owned certified DoorDash/Uber Eats/Grubhub integration exists. DoorDash, Uber Eats and Grubhub occur in only 6 of the 7,051 help-topic bodies, all of them this release note (in IGCM and Server 12.x) plus the 12.3.16 transaction-classification table. The withdrawn Olo/Crave/Tapingo reasoning came from the Solution Partners roster, which is visibly mis-categorised and is not an enumeration. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IGCM/12.3.14_RN/Contents.htm · retrieved 2026-09-12 adversarially verified

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

Resolved off a release note a title-only sweep could not see. IGCM 12.3.14 documents an InfoGenesis integration with UrbanPiper, 'a middleware platform that connects POS systems to multiple online food delivery aggregators, such as DoorDash, Grubhub, and Uber Eats', and enumerates 'Order relay - Relay orders placed in aggregators to InfoGenesis.' SHORTFALL: injection is middleware-mediated rather than a first-party aggregator connector (no direct DoorDash/Uber/Grubhub integration is documented anywhere); it is gated - 'This integration is supported for SaaS customers only' - and 'Validations with delivery aggregators are not included'; and the note never states that relayed orders fire to KDS/printers without a manual accept. DoorDash, Uber Eats and Grubhub occur in exactly 6 of the 7,051 topic bodies - this note, its Server 12.x duplicate, and the 12.3.16 transaction-classification table account for all six. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IGCM/12.3.14_RN/Contents.htm · retrieved 2026-09-12 adversarially verified

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

UPGRADED from `no` 2026-09-12. The 2026-08-08 basis - 'the 747-topic IGCM Configuration Guide ... contains no channel, marketplace or menu-publishing target' - was a title-only sweep artefact and is false at body level. IGCM 12.3.14 documents an InfoGenesis integration with UrbanPiper, 'a middleware platform that connects POS systems to multiple online food delivery aggregators, such as DoorDash, Grubhub, and Uber Eats', enumerating 'Add or update menu - Add or update menu in UrbanPiper through InfoGenesis.' and 'Category timing groups (daypart schedule) - Send schedules to UrbanPiper to associate them with the categories in the menu.' One master menu therefore publishes outward without maintaining a separate menu in each marketplace portal. SHORTFALL: it is middleware-mediated rather than a direct marketplace connection; no channel-specific price markup construct is documented anywhere in the 7,051 help-topic bodies; it is 'supported for SaaS customers only'; and photos are not mentioned. The withdrawn note's Olo/Ssnapp/Tapingo reasoning came from the Solution Partners roster, which is visibly mis-categorised (Olo is filed under Hardware) and should not be used as an enumeration. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IGCM/12.3.14_RN/Contents.htm · retrieved 2026-09-12 adversarially verified

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

UPGRADED from `no` 2026-09-12. The 2026-08-08 basis - 'What is absent is any push: no third-party channel, marketplace or partner-availability topic appears in the 1,691-topic set' - was a title-only sweep artefact and is false at body level. IGCM 12.3.14 lists, under Menu, 'Menu toggle (items and modifiers) - Manage item and modifiers availability in real time.', pushed from InfoGenesis into UrbanPiper, which 'manages all aggregator-specific interactions' for DoorDash, Grubhub and Uber Eats - item AND modifier level, which is what DoorDash requires. The local 86 machinery is documented separately (Manage 86, 86 Un86 Item, 86 Un 86 Modifier, IG OnDemand Sync 86 Un86 Status, terminal options 290/293/530/1314). SHORTFALL: the push is middleware-mediated, it is 'supported for SaaS customers only.', and the release note never states that a POS- or KDS-side 86 automatically triggers the outbound toggle, so the two documented mechanisms are not joined up in writing. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IGCM/12.3.14_RN/Contents.htm · retrieved 2026-09-12 adversarially verified

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

UPGRADED from `no` 2026-09-12. The 2026-08-08 basis - 'No topic in the 1,691-topic InfoGenesis help set concerns pausing, deactivating or reactivating a store on an external ordering channel' - was a title-only sweep artefact and is false at body level. IGCM 12.3.14 lists, under Stores, 'Store toggle - Manage store availability in real time.', pushed from InfoGenesis into UrbanPiper, 'which in turn manages all aggregator-specific interactions' for DoorDash, Grubhub and Uber Eats. SHORTFALL: it runs through third-party middleware rather than per-marketplace control; it is 'supported for SaaS customers only.'; and no timed auto-reactivation is documented - the bullet describes a toggle, with no duration or scheduled re-open. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IGCM/12.3.14_RN/Contents.htm · retrieved 2026-09-12 adversarially verified

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

Re-evidenced 2026-09-12 with a correction: marketplace channels DO now appear in the documentation (the IGCM 12.3.14 UrbanPiper integration), so the 2026-08-08 closing clause - 'there are no marketplace channels in the documentation to reconcile' - is withdrawn. The verdict survives on the reconciliation test. The ReportsGuide enumerates 122 reports, including Tender, Liability Tender, Credit Card Summary/Transaction Detail/Exception, Posting Detail/Status/Summary and PMS Settlement Status - reconciliation is modelled against tenders and PMS postings. None reconciles a third-party marketplace deposit, and none itemises commission, marketing fees or marketplace adjustments; across the 7,051 help-topic bodies the 152 `payout` hits are all TIP payout (POS function #12) and there is no marketplace remittance, commission or adjustment construct anywhere. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IG_12UX/Sitemap.xml · retrieved 2026-09-12 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

Re-evidenced 2026-09-12 with a correction: a third-party order channel DOES exist in the documentation (the IGCM 12.3.14 UrbanPiper integration, with order relay and order-status update), so the 2026-08-08 reason - 'There is no third-party order channel in the 1,691-topic documentation set' - is withdrawn. The verdict survives on the visibility test itself. `sync status` and `publish status` occur ZERO times across all 7,051 help-topic bodies, no per-channel connection status or failure alert is published, and the failure mode is documented only in retrospect, as a fixed defect: IG OnDemand 12.3.15.8 Bug Fixes records that 'Menu publish failed to sync to the UrbanPiper portal when more than three sites were configured.' The integration-health reporting Agilysys does publish - ConfigGuide Interfaces, Interface Server and Interface Resources, and the ReportsGuide Interfaces report, Posting Status Report, Posting Detail Report and Posting Error Report for Opera - all covers PMS, casino and payment interfaces, not order channels. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IG_OnDemand/12.3.15.8_RN/Bug%20Fixes.htm · retrieved 2026-09-12 adversarially verified

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

Overturned from no on audit: first-party order-status tracking for delivery orders exists. IG OnDemand's Track Order Status shows a nine-stage progress bar (0-100%, ending 'Order delivered') on the Order Confirmation and 'I am Here' screens for all To Go fulfillment types including delivery, gated by the Enable Track Order Status checkbox; IG Fly captures delivery details (name, mobile, e-mail, address, postal code) and IG KDS sends SMS/e-mail order-status alerts to them. Shortfalls: no driver state anywhere - no driver construct exists in any help set (delivery is on-property), the status view lives inside the OnDemand ordering flow rather than a documented operator-domain page, and the stages reflect kitchen/fulfillment state only. https://ig.onagilysys.com/help/POS/IG_OnDemand/UserGuide/Track%20Order%20Status.htm · retrieved 2026-08-05 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

Re-evidenced 2026-08-08. InfoGenesis does capture a promise time, but as manual entry: 'Pick up time of the order' is one of the Add Delivery Details fields (Mandatory for Pick-up, Optional for Delivery), typed by the user. The documented field table contains no computed quote, and there is no kitchen-load, driver-availability or drive-time input in the 1,691-topic help set to compute one from. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Add%20Delivery%20Details.htm · retrieved 2026-08-08 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

Re-evidenced 2026-08-08. Agilysys does document offline behaviour explicitly - Go Offline, Offline Configurations, Configure Offline Tender Limit, Offline Kitchen Printing, Offline Kitchen Video, Notification Service Offline - and the Go Offline topic states 'When the terminal is offline, none of the reports are generated. The user cannot clock out or clock in when the terminal goes offline. Most of the terminal functions cannot be performed when the terminal goes offline.' None of these topics addresses delivery: no statement about cash delivery orders, driver assignment or driver settlement during an outage. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Go%20Offline.htm · retrieved 2026-08-08 adversarially verified

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

IG OnDemand is a first-party mobile-first web ordering channel writing into InfoGenesis with no marketplace commission; it is not documented as running on the operator's own branded domain. https://www.agilysys.com/en/products/ig-ondemand/ · retrieved 2026-08-01

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

InfoGenesis is marketed as a single synchronized source of truth for menus, pricing and availability across terminals, mobile, kiosks and QR; IG OnDemand documents unified configuration across ordering channels. https://www.agilysys.com/en/products/infogenesis-pos/ · retrieved 2026-08-01

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

App Store listing for Agilysys Guest App (Agilysys NV, LLC; v26.1.2, updated 2026-07-09), retrieved via the iTunes lookup API 2026-08-08: 'Rather than having to create their own guest app from the ground up, hospitality organizations can use the Guest App from Agilysys ... The Agilysys Guest App is fully brandable to reflect the hospitality organization's preferences for look and style. After applying a name and brand style, hospitality organizations tailor the app experience ... Depending on which capabilities an organization makes available through the brandable Guest App, corresponding Agilysys solutions must be in place.' A live white-labelled instance is published under the property's own name by the same seller: 'Pinehurst Country Club, NC' (id6463205901, v1.2.10, 2026-05-30), described as 'This custom mobile application will allow you to book a tee time, make dining and fitness reservations, view Member charges'. SHORTFALLS: neither listing documents menu ordering - the functions named are itineraries, service requests, tee times, dining/fitness reservations and member charges; food ordering is IG OnDemand, whose 902-topic help set is a browser product (e.g. /IG_OnDemand/UserGuide/Display Browser Tab Title based on the Screen.htm) reached by QR code and link; and only the iOS side was verified - a Play Store developer listing for Agilysys NV LLC could not be retrieved and guessed package ids (com.agilysys.guestapp, com.agilysys.pinehurst) both 404, so Android publication is unconfirmed. https://apps.apple.com/us/app/agilysys-guest-app/id6449189252 · retrieved 2026-08-08

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

IG OnDemand has signed-in guest accounts (sign-up verified by activation link or e-mail OTP) and guests can save GA member/charge account numbers 'to their signed-in profile', with saved account details surfaced in discount popups. Shortfall: saved tokenized card-on-file, saved delivery addresses and one-tap reorder of a previous order are not documented for the guest-facing channels - the checkout flow captures name, e-mail and phone each time. https://ig.onagilysys.com/help/POS/IG_OnDemand/12.3.15_RN/Save%20GA%20Account%20Number%20Entered.htm · retrieved 2026-08-03

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

IG OnDemand surfaces built-in upsell prompts and personalized recommendations at purchase moments; attach-rate reporting on those suggestions is not documented. https://www.agilysys.com/en/products/ig-ondemand/ · 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

Kitchen-side Smart Order Throttling exists in IG KDS; per-daypart slot capacity that automatically closes digital time slots is not documented. https://www.agilysys.com/en/products/ig-kds/ · retrieved 2026-08-01

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

Documented modes: multi-venue pickup, poolside, room service with room identifier, and QR at-table. Curbside arrival check-in and delivery are not documented. https://www.agilysys.com/en/products/ig-ondemand/ · retrieved 2026-08-01

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

IG OnDemand uses QR-code location routing for at-table/at-location ordering; IG Quick Pay adds QR scan-to-pay with tipping against the existing POS check. https://www.agilysys.com/en/products/ig-quick-pay/ · 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

IG Kiosk (plus IG PanOptic grab-and-go kiosk) shares the POS menu in real time with Agilysys Pay P2PE unattended payment; no accessibility conformance is claimed. https://www.agilysys.com/en/products/ig-kiosk/ · retrieved 2026-08-01

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

IG OnDemand is the guest self-service ordering product, and its public manual documents a single-guest flow end to end: browse menu, build a personal cart, tender, with scheduled orders, delivery fulfillment types and guest-account charging. No shareable-link, join-a-cart, per-person or total spend cap, or multi-participant construct appears anywhere - 'group order'/'group ordering' return zero hits across the 902 indexed OnDemand topics (user guide, config guide and every release-note series) and across the POS Terminal, Kiosk, Fly and KDS help sets. https://ig.onagilysys.com/help/POS/IG_OnDemand/UserGuide/Contents.htm · retrieved 2026-08-04

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

Sales & Catering covers BEO automation and group-account charge sync — an event-sales workflow, not a guest-facing catering ordering portal with lead-time rules, deposits and ACH terms. https://www.agilysys.com/en/products/sales-and-catering/ · retrieved 2026-08-01

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

No telephone ordering channel exists and no partner is named. The 12.3.16 Classify and Store Transaction table enumerates Terminal Mode - 'the ordering channel or the product associated with the source' - as POS Terminal, IG OnDemand, IG Fly, IG Kiosk, Teams Ordering, DoorDash, Uber Eats and Grubhub, with no voice or telephone channel; `caller`, `caller ID`, `telephony`, `IVR` and `inbound call` occur ZERO times across the entire 8,068-document estate, and `phone order` and `drive-thru` occur ZERO times across all 7,051 help-topic bodies - their only hits anywhere are 1 and 2 respectively, in two blog posts, as generic industry commentary ('A few years ago, dine-in and phone orders dominated the restaurant landscape'), not as an Agilysys channel. CORRECTED 2026-09-12: both terms were published as zeros over a 7,156-document corpus that excluded the vendor's own 820 posts. Agilysys documents its certified integrations in that corpus (PeopleVine, UrbanPiper, 7shifts, Shopify, Adyen, Shift4, FreedomPay, AssaAbloy, Berg) and none is a voice or telephony order-taking vendor, which is what carries the 'named certified partner' half - not the partner roster, which is visibly mis-categorised and does contain a telephony vendor (Percipia, filed under Payment Processing). CORRECTED 2026-09-12: an earlier draft said every `voice`/`speech` hit was IG Kiosk ADA text-to-speech output and that the only AI assistant was 'an AI-based chat assistant in mobile, enabling users to perform operational tasks through conversational inputs'. The chat-assistant quotation is accurate but the enumeration was not: most of the 74 `voice` hits are credit-card voice authorisation and 13 are Eatec 26.2.5's 'AI Requisition Voice Assistant' for inventory requisitions. Neither answers a guest call, so the verdict stands. The guestsense.ai page markets 'engage easily using voice or chat' with no ordering injection and no named partner, which is marketing rather than a certified integration. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IG_12UX/12.3.16_RN/Classify%20and%20Store%20Transaction.htm · retrieved 2026-09-12 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

Re-evidenced 2026-08-08. The IGCM Configuration Guide overview does disclose AI - 'This product includes features powered by Generative Artificial Intelligence (GenAI)... they will be clearly identified wherever they appear in the system' - but the modules it says it covers in full are POS Configuration, Utilities, User Management and Reports. No topic in the 1,691-topic help set matches 'drive', and there is no voice ordering, speech recognition or escalation-to-human topic. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Contents.htm · retrieved 2026-08-08 adversarially verified

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

digital-sms-ordering

CLAIM: conversational SMS or chat ordering/reordering that lands in the POS. VERDICT: partial. NEW SURFACE the prior full-body pass missed (its 'inbound/two-way 0' control did not include 'chatbot'): IG OnDemand release 12.3.15.7 ships conversational ordering through a Microsoft Teams chatbot, and 12.3.16.1 records 'Teams Ordering' as an ordering channel on the POS check. EVIDENCE: https://ig.onagilysys.com/help/POS/IG_OnDemand/12.3.15.8_RN/12%203%2015%207.htm - 'Place Orders through Microsoft Teams Chatbot | IG OnDemand has been enhanced to allow users to place orders through a chatbot in Microsoft Teams. With this enhancement, users can: Place orders from available profit centers; Manage profile information; View order history, order status, and receipts; View item recommendations filtered based on dietary preferences and allergen selections; Complete payments using GA and Credit Card payment methods'; configured per site under External Integration ('Microsoft Teams | When enabled, orders can be placed through Microsoft Teams', 'Azure Bot Id'). Lands in the POS: https://ig.onagilysys.com/help/POS/IG_OnDemand/12.3.16.1_RN/Store%20Check%20Source%20Details.htm and IG_12UX/12.3.16.1_RN/Classify and Store Transaction.htm list the check 'Mode' values 'IG OnDemand | IGPOSTerminal | Teams Ordering | DoorDash | Uber Eats | Grubhub', stored 'whenever a check is opened or closed'. SHORTFALLS (named): chat only in Microsoft Teams, not SMS/WhatsApp/web chat ('whatsapp|messenger|imessage|rcs' 0 in 5,627 bodies; every SMS topic is outbound receipts/notifications per SMS Configuration.htm); 'This is a pilot feature is supported only for SaaS customers. Contact Agilysys to enable this feature'; 'applicable only to ASAP orders with the pick-up fulfillment type in the To Go profile'; 'Reordering a completed order is not supported'; 'Scheduled orders are not supported'; the bot is 'available only to users who have been granted access by the property's Microsoft Teams or Microsoft 365 administrators' (an employee/workplace audience, not the public). BOUND: raw-HTML census of ig.onagilysys.com/help/POS, 2026-09-16 (HelpSystem.xml BuildTime 9/16/2026 3:19:59 PM): 7 MadCap help systems (IG_12UX 1,724, IG_Kiosk 1,238, IG_OnDemand 923, IG_Fly 918, IG_KDS 595, IG_DMB 59, IGCM 99 TOC entries = 5,556 topics), all 200; href fixpoint over 55,577 in-body .htm links added ZERO topics outside the TOC; a nonsense path returns a real 404 (WebContentNotFound), so no soft-200. Plus 71 superseded 12.3.16_RN topics that are still served but no longer in the TOC (replaced by 12.3.16.1_RN), read from the q310 cache: CORPUS 5,627 bodies, comments/scripts stripped, tokenised word-boundary case-insensitive controls (.cache/q316/agilysys/controls.mjs). Retrieved 2026-09-16. https://ig.onagilysys.com/help/POS/IG_OnDemand/12.3.15.8_RN/12%203%2015%207.htm · retrieved 2026-09-16 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

CLAIM: Order with Google - the direct ordering link provisioned to the Google Business Profile. VERDICT: no (weaker than the pizza trio; the orchestrator may prefer to hold it at unknown, see below). EVIDENCE: the IG OnDemand ordering site's settings are a closed enumeration - https://ig.onagilysys.com/help/POS/IG_OnDemand/ConfigGuide/Site%20Settings.htm (30 KB) lists every site-level integration: Login Authentication (Facebook, Google, LinkedIn, Agilysys login, External login, SSO), Sign Up/Sign In modals, OTP verification, Engage member lookup and Engage Loyalty, Stored Payments, Recent Order and Favorites, logistics (Delivery, Pickup, Apex), scheduled-order timeslots, 'Google Analytics Configuration | Analytics | Enabled - Google Tag Manager is supported for the site' with GTag manager ID, ADA, cookie consent, Table Number LookUp, Import/Export, Generate QR / Generate Bulk QR, closed-store menu and a toggle list. Google appears only as social sign-in and GTM; there is no Business Profile, ordering-action or listing field. The ordering-channel enumeration on the check (Store Check Source Details 12.3.16.1: 'IG OnDemand | IGPOSTerminal | Teams Ordering | DoorDash | Uber Eats | Grubhub') names no Google channel. BOUND: raw-HTML census of ig.onagilysys.com/help/POS, 2026-09-16 (HelpSystem.xml BuildTime 9/16/2026 3:19:59 PM): 7 MadCap help systems (IG_12UX 1,724, IG_Kiosk 1,238, IG_OnDemand 923, IG_Fly 918, IG_KDS 595, IG_DMB 59, IGCM 99 TOC entries = 5,556 topics), all 200; href fixpoint over 55,577 in-body .htm links added ZERO topics outside the TOC; a nonsense path returns a real 404 (WebContentNotFound), so no soft-200. Plus 71 superseded 12.3.16_RN topics that are still served but no longer in the TOC (replaced by 12.3.16.1_RN), read from the q310 cache: CORPUS 5,627 bodies, comments/scripts stripped, tokenised word-boundary case-insensitive controls (.cache/q316/agilysys/controls.mjs). CONTROLS: google 47 hits in 19 files = Google Pay/Google Wallet payment tokens, Google Chrome browser paths, Google social login, Google Tag Manager, Google Play Store (POISON, all); 'google business profile|google my business|business profile|order with google|google maps|reserve with google' 0. CAVEAT: a Google ordering action can be registered by the operator (or by Google's own partner feed) pointing at an OnDemand URL with no vendor feature; this no says the product does not provision it, which is what the claim asks. Retrieved 2026-09-16. https://ig.onagilysys.com/help/POS/IG_OnDemand/ConfigGuide/Site%20Settings.htm · retrieved 2026-09-16 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

CLAIM: Apple Business Connect 'Order Food' action on the Apple Maps place card pointing at the vendor's first-party ordering flow. VERDICT: no (same strength and caveat as digital-google-order). EVIDENCE: https://ig.onagilysys.com/help/POS/IG_OnDemand/ConfigGuide/Site%20Settings.htm is the closed enumeration of the ordering site's integrations (social logins, Engage loyalty, stored payments, logistics, GTM analytics, cookie consent, QR generation, toggles) and carries no Apple Business Connect, Maps or place-card field; the check ordering-channel enumeration (IG_OnDemand/12.3.16.1_RN/Store Check Source Details.htm: 'IG OnDemand | IGPOSTerminal | Teams Ordering | DoorDash | Uber Eats | Grubhub') has no Apple channel. BOUND: raw-HTML census of ig.onagilysys.com/help/POS, 2026-09-16 (HelpSystem.xml BuildTime 9/16/2026 3:19:59 PM): 7 MadCap help systems (IG_12UX 1,724, IG_Kiosk 1,238, IG_OnDemand 923, IG_Fly 918, IG_KDS 595, IG_DMB 59, IGCM 99 TOC entries = 5,556 topics), all 200; href fixpoint over 55,577 in-body .htm links added ZERO topics outside the TOC; a nonsense path returns a real 404 (WebContentNotFound), so no soft-200. Plus 71 superseded 12.3.16_RN topics that are still served but no longer in the TOC (replaced by 12.3.16.1_RN), read from the q310 cache: CORPUS 5,627 bodies, comments/scripts stripped, tokenised word-boundary case-insensitive controls (.cache/q316/agilysys/controls.mjs). CONTROLS: apple 26 hits in 11 files = Apple Pay / Apple Wallet payment, Apple Tap to Pay on iPhone, Apple Safari browser, App Store (POISON, all); 'business connect|apple maps|place card' 0; 'order food' 8 = POISON, the IG OnDemand landing-page button ('Button text | Default : ORDER FOOD', Site Design.htm) and the IG Smart Menu link, not an Apple Maps action. Retrieved 2026-09-16. https://ig.onagilysys.com/help/POS/IG_OnDemand/ConfigGuide/Site%20Settings.htm · retrieved 2026-09-16 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

Loyalty & Promotions unifies guest identity across PMS and POS and references digital touchpoints; in-flow accrual/redemption inside IG OnDemand checkout is not explicitly documented. https://www.agilysys.com/en/products/loyalty-and-promotions/ · 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

Re-evidenced 2026-08-08 against the product's own page rather than the dead index. Agilysys Membership does recurring billing: 'Automate recurring billing, renewals, upgrades, downgrades, and expirations with rules-based controls', with 'dues management, invoicing, and usage tracking'. Named shortfall, unchanged: it is a clubs/residences membership product tied to PMS and InfoGenesis, and nothing on the page attaches it to digital or online F&B ordering as a guest subscription tier (a delivery-fee waiver, per-period item entitlement or paid loyalty tier). https://www.agilysys.com/en/products/membership/ · retrieved 2026-08-08 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

Loyalty & Promotions centrally defines item-specific, outlet-specific and post-type promotions with precision controls; explicit channel-eligibility parity across POS/kiosk/digital is not documented. https://www.agilysys.com/en/products/loyalty-and-promotions/ · 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

The claim turns on whether export needs 'a fee or vendor approval', which makes the published contract the right instrument, and it answers against the claim. DPA (04-02-25) section 12.1: 'You are advised to take appropriate action to back up or otherwise store separately any Personal Data prior to the termination of the Subscription Services. You may make a written request to Agilysys for the retrieval of, or access to, your Personal Data up to ten (10) days prior to the termination of Subscription Services.' Retrieval therefore requires a written request to the vendor inside a ten-day window - vendor approval, which the claim excludes. There is no self-serve route either: `bulk export` and `guest export` occur ZERO times across all 7,051 help-topic bodies, and the IG OnDemand Data Privacy and Consent Management topic says 'To remove any saved guest details, properties must contact Agilysys'. CORRECTED 2026-09-12: the documented export family is larger than an earlier draft allowed - the ReportsGuide Scheduling and Report Category menus carry Employee Export ('Exports file with employee data records'), Clock Data Export, Order Table Export (Vintage), Product mix Export, Summary Export, Banquet Export, Choice Group Export, WinRetails Export and DataWorks Export (Vintage), alongside IGCM enterprise configuration export - but none of them carries a guest record, so the conclusion is unchanged. The nearest guest-data feed is Agilysys Analyze Data-as-a-Service, a paid analytics SKU, which the claim also excludes. Sibling check: commercial-post-termination-export-window rests on the same clause and is also `no`, so this is not a conjunction of two unknowns. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://www.agilysys.com/en/wp-content/uploads/Agilysys-Data-Processing-Agreement-04-02-25-Final.pdf · 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

IG OnDemand and IG Kiosk route payment through Agilysys Pay with PCI-validated P2PE and tokenization; PCI DSS 4.0 script-integrity (Req 6.4.3/11.6.1) and 3DS support are not addressed publicly. https://www.agilysys.com/en/products/pay/ · retrieved 2026-08-01

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

IG OnDemand calculates a configurable card surcharge in the digital flow (enterprise/store/tender-level percentage with priority order, optional tax on surcharge via Terminal Option 1396) - but 'applicable only for DataCap credit card transactions'. Shortfall: no guest-facing disclosure requirement is documented for the digital checkout, nothing covers jurisdictions or card brands where surcharging is prohibited, and dual pricing is not documented for digital channels at all. https://ig.onagilysys.com/help/POS/IG_OnDemand/12.3.15.4_RN/Surcharge%20Calculation%20Enhancements.htm · retrieved 2026-08-03

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

PMS+POS integration creates a consolidated guest view and Analyze markets 'Guest 360'; dedup/merge behavior on phone or email match is not documented. https://www.agilysys.com/en/products/loyalty-and-promotions/ · retrieved 2026-08-01

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

There is no documented path for marketplace orders to reach InfoGenesis at all, let alone attach to a native guest profile: the Solution Partners directory's filterable categories (Online Mobile Ordering, Payment Processing, PMS, Casino Player Tracking, etc.) include no third-party delivery marketplace category and name no DoorDash, Uber Eats or Grubhub partner; Agilysys is absent from DoorDash's 2026 Preferred Integration Partner list; and DoorDash/Uber/Grubhub/marketplace return zero topics across every indexed help set, including the Loyalty Configuration guide. With no marketplace order ingestion documented anywhere, marketplace-order identity attach is absent a fortiori. https://www.agilysys.com/en/solution-partners/ · retrieved 2026-08-04

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

Supports tier-based, points-based or hybrid loyalty structures with customizable earning rules, expiration schedules and redemption logic as configuration. https://www.agilysys.com/en/products/loyalty-and-promotions/ · retrieved 2026-08-01

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

guest-loyalty-tiers

Tier-based structures are documented; automatic promotion/demotion driven by a rolling-window spend or visit count is not. https://www.agilysys.com/en/products/loyalty-and-promotions/ · retrieved 2026-08-01

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

guest-loyalty-offline-behavior

Overturns the prior finding that no topic states what loyalty does offline. The 12.3.13 Meal Swipe Entitlements note carries a dedicated 'Offline Scenario' heading and specifies queue-and-reconcile: if the third-party system is offline the Loyalty & Promotions system checks for downloaded entitlement data and applies the meal swipe tender if it is present; failing that the tender is applied and 'recorded as manual adjustment required in the Loyalty & Promotions system', and at the terminal 'the meal period is denoted with an asterisk symbol to indicate an offline redemption.' The opposite case is documented too - Authorize Member Charge Tenders states 'This enhancement is not supported for offline transactions' - and the IGCM IAS Postings log carries an Offline field whose two list items read '0' - 'The terminal is offline.' and '1' - 'The terminal is online.' per posting. (QUOTATION CORRECTED 2026-09-12: an earlier draft ran those two separate list items together as a single quoted span, which only looks contiguous once the HTML is tag-stripped.) SHORTFALL: only entitlement redemption and member-charge authorisation are placed. Point ACCRUAL offline, and general points lookup and redemption offline, are still unstated, so the claim's lookup/accrual/redemption triple is not fully documented. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IG_12UX/ReleaseNotes_12.3.13/Meal%20Swipe%20Entitlements%20for.htm · retrieved 2026-09-12 adversarially verified

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

guest-loyalty-offer-stacking-rules

Documented as 'precision controls to prevent margin erosion while supporting combined incentives'; explicit exclusive-vs-combinable precedence configuration is not shown. https://www.agilysys.com/en/products/loyalty-and-promotions/ · retrieved 2026-08-01

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

Documented targeting is tier-level and basket-level, not guest-level: the IGCM Tier Discount config page offers 'Use this discount for Tiers only' with a Tier Level selector and a Discount Code matching a type configured in the Agilysys Loyalty admin portal, and the Buy Rules / Spend Rules release note gates promotions behind Terminal Option 1427 and builds every rule from Product Class, Revenue Category, Item Group, Item or Check Level. Shortfall: no guest attribute (recency, frequency, spend, items purchased) is an addressable audience in the documented POS surface; the marketing page's AI-driven segmentation is authored in the separately licensed Loyalty Suite admin portal, whose documentation is not public and could not be verified. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Tier%20Discount.htm · retrieved 2026-08-02 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

Digital Marketing does intelligent audience segmentation on behavior and spend patterns; automatically computed named lifecycle segments (new/regular/at-risk/lapsed/VIP) are not documented. https://www.agilysys.com/en/products/digital-marketing/ · retrieved 2026-08-01

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

Automated lifecycle workflows triggered by booking events and stay milestones, plus post-stay survey automation with response-triggered follow-ups. Note these are hotel-stay lifecycles, not restaurant visit lifecycles. https://www.agilysys.com/en/products/digital-marketing/ · retrieved 2026-08-01

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

Shortfall: campaign send is not an InfoGenesis POS capability. It requires Agilysys Digital Marketing, a separately licensed product aimed at the PMS/stay guest journey, and Agilysys publishes no admin guide, help centre or manual for it - only the product page and a brochure PDF. The InfoGenesis help centre documents email and SMS only as transactional receipt and order-notification delivery (SMS Configuration, Email and SMS Receipts, Send Receipt PDF as Link in Order Confirmation Email and SMS, Guest Consent for Receiving SMS); no campaign authoring, segmentation or scheduling is documented anywhere. https://www.agilysys.com/en/products/digital-marketing/ · retrieved 2026-08-06

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

OnDemand and Kiosk capture explicit opt-in consent for SMS and e-mail notifications with configurable compliance text ('guests must explicitly opt in to receive order status and order receipts through SMS'), and a Data Privacy and Consent Management section documents Remove Saved Preferences. Shortfall: no timestamp/source-of-consent ledger is documented, the consent flows cover order notifications rather than marketing channels, and 'to remove any saved guest details, properties must contact Agilysys' - cross-channel revocation handling is undocumented. https://ig.onagilysys.com/help/POS/IG_OnDemand/UserGuide/Guest%20Consent%20for%20Receiving.htm · retrieved 2026-08-03

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

guest-loyalty-10dlc-registration

The terms are absent from the publisher's whole manifest and the vendor also publishes a closed enumeration of its SMS provisioning routes in which A2P registration does not appear. `10DLC`, `A2P`, `A2P 10DLC`, `campaign registration`, `brand registration` and `toll-free verification` occur ZERO times across the entire 8,068-document estate, and `carrier` zero times across all 7,051 help-topic bodies (its 24 hits elsewhere are blog and 10-K prose). The enumeration corroborates: SMS Configuration states 'SMS communication can be set up in the following two ways, depending on the customer's preference' - integrate the customer's own Twilio account directly, or use Agilysys, which 'Supports SMS communication through one of the following methods, which requires customers to contact Agilysys for setup' via a Twilio sub-account, Open Market (username, password, sending mobile number) or Vonage (API Key, API Secret, sending number). Both framings state a count ('two ways', 'one of the following'), neither is hedged with 'for example' or 'includes', and every required credential is itemised - none is a brand or campaign registration. So Agilysys neither handles nor documents A2P 10DLC registration; the bring-your-own-provider model leaves it with the operator and says so nowhere. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/SMS%20Configuration.htm · 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

Performance analytics connect engagement to booking revenue and 'measure marketing ROI by linking activity directly to revenue outcomes'; offer-redemption-to-check-total attribution is not documented. https://www.agilysys.com/en/products/digital-marketing/ · retrieved 2026-08-01

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

Analyze offers Data-as-a-Service clean data feeds into a customer's own BI platform, but that is a paid analytics SKU; no free self-serve guest-PII export is documented. https://www.agilysys.com/en/products/analyze/ · 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

A documented outbound order and guest event stream does exist, which the API-portal-only probe of 2026-08-08 could not establish. IG_12UX ConfigGuide Event Notification turns on Order Event - 'The order event details are sent to the external system when guests place orders or refund/void orders.' - and Kitchen Event, fired 'when the order is bumped in the kitchen', and the IG Fly release note Send Order and Kitchen Events prints the full JSON for place, refund/void and kitchen-bump events with a field-by-field description table, including guest identifiers in del_info (room, ph, email) and per-item detail. It is also authenticable: Server 12.x release 12.3.15.4 adds an Others (HMAC) adapter mode with HMACSecretKey, HMACHeaderKey and HMACAlgorithm (SHA-256 or SHA-512). SHORTFALL: there is still no subscriber model. Delivery is to one IAS adapter and configuration group selected per enterprise, not a stream a CDP can subscribe to; onboarding is bespoke - the topic says 'Contact Agilysys to initiate this integration at your property.' and then, in a separate note callout, 'Note that development efforts may be required on both sides' (QUOTATION CORRECTED 2026-09-12: an earlier draft quoted those two paragraphs as one continuous span); the Employee Event slot is 'For future use'; the Agilysys InfoGenesis Event Notifications Reference Guide it points to is not public; and no CDP or marketing platform is named as a consumer. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Event%20Notification.htm · retrieved 2026-09-12 adversarially verified

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-stay survey automation with response-triggered follow-ups is documented; score-based routing to private recovery vs public review sites is not. https://www.agilysys.com/en/products/digital-marketing/ · retrieved 2026-08-01

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

The Loyalty & Promotions page enumerates the program mechanics the product offers - points, tier and hybrid structures, real-time earn/redeem, targeted item- and outlet-specific promotions, BOGO, conditional discounts, timed incentives, experiential rewards, limited-time offers, upsell incentives - and no referral mechanic is among them; the page's framing is rewarding on-property spend (rooms, F&B, spa, golf), not guest acquisition. 'Referral' returns zero topics across all indexed InfoGenesis help sets. No per-guest codes or links, referred-first-order attribution or two-sided reward appears in any Agilysys material located. https://www.agilysys.com/en/products/loyalty-and-promotions/ · retrieved 2026-08-04

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

Swept all 5,336 topic paths and titles on 2026-08-08 for wallet|apple|google|pass|membership card. Every wallet hit is a payment instrument: /IG_12UX/ConfigGuide/Wallet Payment.htm, /IG_Kiosk/ConfigGuide/Wallet Payment.htm, /IG_OnDemand/ConfigGuide/Wallet Payment.htm, /IG_12UX/12.3.15_RN/Partial Refund for Credit Card and Wallet Payments.htm, and Apple Tap to Pay on iPhone. The loyalty credential documented on the POS side is a physical scan - /IG_12UX/ReleaseNotes/Display Additional Information on Scanning Patron Card - Loyalty & Promotions.htm - together with member charge tenders, discount codes, meal-swipe entitlements and multi-guest lookup, none of which involve a provisioned pass. IG OnDemand's guest identity is a login (social sign-in with Google, Facebook, LinkedIn) rather than a wallet object. Pass issuance would live in the Agilysys Loyalty & Promotions or Digital Marketing SKU, and neither publishes any documentation on ig.onagilysys.com or elsewhere, so this cannot be resolved from vendor material. || 325th: 325th: NEW SURFACE, and it CORRECTS this record - the Agilysys Loyalty & Promotions SKU is no longer undocumented. agilysys.com's WordPress media library is not listable through the REST API (www.agilysys.com/wp-json/ returns a 1,244-byte bot-challenge shell carrying an accessKey, and the working /en/wp-json/ index exposes 68 routes of which NONE is wp/v2 - the core namespace is declared but its routes are withheld, so /en/wp-json/wp/v2/media 404s), and wp-sitemap.xml lists pages only. Enumerated it instead from the Wayback CDX index of agilysys.com PDFs (488 rows; 263 under /en/wp-content/), which names ~260 documents including a 2026-copyright sell sheet for this SKU that nothing in the record had read. Fetched live at 200, 562,719 bytes, application/pdf; the nonsense control /en/wp-content/uploads/Agilysys-Zzz-Nope-Control.pdf 404s. It enumerates six 'Product Features': Flexible Loyalty Programs ('Design tier-based, points-based, or hybrid loyalty programs with customizable earning, redemption, and expiration rules'), Enterprise-Wide Program Management, Targeted Promotions & Offers, Real-Time Earn & Redeem, Built-In Tracking & Performance Insights, Integrated Guest Profile & Transaction Data. No Apple Wallet, Google Wallet, pass, PassKit or push-updatable balance appears anywhere in it. POISON, named so it is not re-mined: the sheet's phone mock-up shows in-app tabs labelled 'My Wallet' and 'eCash' over a 'Platinum Tier Member' / 'Expiring Point Summary' screen - that is Agilysys's own app wallet (see the separate Agilysys-eCash sell sheet), not a provisioned OS wallet pass; and the 2026 Agilysys-IG-Fly.pdf 'PCI-validated P2PE with EMV, NFC, and mobile wallet support' is a PAYMENT wallet, the same trap the 319th recorded. Still unknown, not no: a six-bullet marketing sheet that also carries un-replaced lorem-ipsum placeholder text ('Sumquidi dolut explaut lam, simus, offici que platisc iisciiscil et') and the self-disclaiming 'The information contained in this promotional material is for illustration purposes only' is not an enumeration that can exclude a feature, and the SKU still publishes no configuration documentation. Retrieved 2026-09-17. || 327th: 327th: NEW SURFACE - the Loyalty & Promotions PRODUCT PAGE (43,079 characters of stripped text, far fuller than the sell sheet read in the 325th: seven feature panels plus an eight-question FAQ block). It describes the credential surface as tier/points/hybrid programmes with 'custom earning rules, redemption thresholds, expiration policies and tier benefits', real-time earn and redeem 'across PMS and POS transactions', and segment-of-one targeting. No Apple Wallet, Google Wallet, pass, PassKit, .pkpass or push-updatable balance appears. POISON NAMED, because it is the whole reason a grep looks positive here: 'wallet' scores 5 on this page and 10 across the whole 117-page site, and EVERY occurrence is the phrase 'wallet share' (grow/capture/increase total wallet share) - a spend-capture metric, not a pass; the only 'Apple' and 'Google' tokens on the entire site (2 each) are the Agilysys Pay and Authorize pages' mobile payment wallets, the same payment-instrument trap recorded in the 319th. Corpus: the FIRST body-level census of www.agilysys.com's HTML pages (prior passes read only ~9 legal pages plus the 117-document PDF library): the publisher's own page manifest https://www.agilysys.com/en/wp-sitemap-posts-page-1.xml lists 117 pages and all 117 were fetched at HTTP 200 (1,846,153 characters of stripped text); the nonsense control https://www.agilysys.com/en/zzz-nope-control-qq/ returns 404. (The WP REST API still withholds wp/v2 - /en/wp-json/ lists 68 routes in 10 namespaces, and wp/v2/types, wp/v2/media and wp/v2/solution_partner all 404 with rest_no_route, re-confirmed today.) Still unknown, not no: a product page is grade C and the SKU still publishes no configuration documentation. Retrieved 2026-09-18. || 328th: 328th: the last unchecked Agilysys corpus is now checked at BODY level and agrees. Prior notes on this cell swept topic PATHS AND TITLES ('all 5,336 topic paths and titles'); the 5,627-topic body corpus on disk (.cache/q316/agilysys/corpus.json, 10,620,922 characters) was tokenised today: 'Apple Wallet|Google Wallet|pkpass|PassKit' scores 3 hits in 2 topics and both are PAYMENT instruments - /IG_OnDemand/ReleaseNotes/12 3 11.htm 'guests to use their saved credit or debit cards in the Apple Wallet to make payments through Apply Pay. Google Pay is not supported' and /IG_Fly/12.3.15.11_RN 'Tokens created using Apple Pay/Google Wallet (NFC/contactless) cannot be reused for follow-on transactions' - and 'add to wallet' scores 0. No provisioned loyalty pass exists in the POS product's own documentation at body level. Still unknown, not no, for the standing reason: pass issuance would sit in the Agilysys Loyalty & Promotions SKU, which publishes a product page and a sell sheet but no configuration documentation, so no loyalty-product census exists to bound. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE - the App Store PUBLISHER census (itunes.apple.com/lookup?id=712501910&entity=software, Agilysys NV, LLC) = 22 apps: InfoGenesis POS Terminal, Agilysys Guest App, Agilysys Member App, Agilysys Member Access Control, a white-label club app (Pinehurst Country Club), Agilysys Service, Reserve, Caddie, Stock, Eatec Mobile x2, My Hotel Key, and 10 Agilysys Pay processor builds. Tokenised over all 22 descriptions: 'wallet' 0, 'pass' 0 (the only credential language is My Hotel Key's digital room key). The loyalty-facing app is the Agilysys Member App (id 6748003419, 2026-09-07): 'Access the member directory and digital membership card with QR code', 'Personalized itinerary, entitlements, offers'. Its 4 screenshots, read at full resolution (1000x0w), show an in-app 'PLATINUM since 2025' tier card with a 'View' button, points with 'Expiring - 710 Pts', All Offers / Eligible Offers, member transactions, buddy lists and a member directory - no 'Add to Apple Wallet' control anywhere. So the loyalty credential Agilysys ships is IN-APP (a QR membership card), which is the branded-app model this claim is the alternative to; but a store listing (grade C) is not a census of the Loyalty & Promotions SKU's configuration, so this stays unknown rather than no. Retrieved 2026-09-18. || 334th: 334th: two NEW SURFACES, neither shows a provisioned OS wallet pass. (1) The Android build of the Agilysys Member App itself (com.agilysys.memberapp 26.1.4, version code 673; 164,582,683-byte XAPK from the apkcombo mirror, unpacked, never executed). It is a Flutter app whose whole Dart code is one AOT libapp.so (package root agilysys_mobile_app, 33 modules incl. membership, promotions, casino, digital_key, dining, ondemand). Its wallet vocabulary is an IN-APP wallet: 'My Wallet', MyWalletWidget, WalletTransactionsBloc / GetWalletTransactionsEvent, txtMembershipMyWallet, membershipCards / txtMembershipCardNumber. None of the ~190 bundled Dart packages is a wallet-pass plugin, and 'pkpass', 'PassKit', 'savePasses', 'gms.pay' / PayClient score 0 in libapp.so. POISON named so it is not re-mined: 'wallet_membership' / 'wallet_giftcard' are Material ICON names; 'vnd.apple.pkpass' in classes2.dex is one row of a MIME-type table (between vnd.adobe.photoshop and vnd.google-earth.kml+xml); and the dex's 'Credential is available for Google Wallet' / getAddToWalletProvisioningDeepLink strings are the Zaplox/dormakaba/LEGIC digital ROOM KEY SDK (hotel door key in Google Wallet), not a loyalty pass. (2) The Agilysys Digital Marketing training course on the Knowledge Center (40 Supademo walkthroughs, 2,943 text fields, all fetched at 200): its template menu is Communication (Email, SMS), Print (PDF File), Attachments and Survey Result Response; 'wallet' 0, 'pass' 0, 'loyalty' 0, 'points' 0 (control: 'template' 291, 'campaign' 278). So neither the member app nor the marketing module issues a wallet pass; still unknown rather than no because pass issuance would be server-side in the Loyalty & Promotions SKU, which has no published configuration docs or course. Retrieved 2026-09-18. 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

IG OnDemand / IG Kiosk / IG 12UX Configuration Guide, Customer PII Data Deletion for Privacy Compliance: 'Users can automatically delete customer personally identifiable information (PII) to comply with privacy regulations. Customer PII data is captured during order creation through sources such as loyalty programs, memberships, credit card processing, and delivery inputs. Properties can enable privacy compliance laws at the enterprise level and select the applicable regulation CCPA or GDPR. Only one regulation can be selected at a time ... customer PII data is retained in the check JSON file only for the configured retention period after the check reaches Completed status. After the retention period expires, the PII data is automatically deleted from the check JSON file. This applies only to checks that are completed after it is enabled.' Consent tooling exists alongside it: /IG_OnDemand/UserGuide/Guest Consent for Receiving SMS.htm and /IG_Kiosk/12.3.15.7_RN/Guest Consent for SMS and Email Notifications.htm, with Remove Saved Preferences for withdrawal. SHORTFALLS: this is a blanket time-based purge, not admin tooling to fulfil an individual guest's access or deletion request - there is no DSAR queue, no per-guest lookup-and-erase, and no data-access/export report; it only ever reaches PII inside the check JSON, so propagation to loyalty and marketing records is not shown (and the Loyalty & Promotions and Digital Marketing SKUs publish no documentation); it is not retroactive ('applies only to checks that are completed after it is enabled'); and /IG_OnDemand/UserGuide/Data Privacy and Consent Management.htm states 'All transactional data used in IG OnDemand will always be saved. To remove any saved guest details, properties must contact Agilysys' - i.e. ad-hoc erasure is a vendor service request, not operator tooling. https://ig.onagilysys.com/help/POS/IG_OnDemand/ConfigGuide/Customer%20PII%20Data%20Deletion.htm · retrieved 2026-08-08

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

Re-checked on 2026-08-08 against the re-walked help system. /IG_12UX/ReportsGuide/Anti-Fraud Controls.htm is the corpus's dedicated fraud topic and it is void-and-override scoped: it documents Authorize Emp ID capture on Void Checks / Void Item by Authorizing Employee / Void Item Detail, Electronic Journal message 5013 (Manager Override) logging manager ID plus void reason, and Item Reorder Control against happy-hour price-arbitrage schemes. It says nothing about loyalty points, redemption velocity or employee self-redemption. The POS-side loyalty configuration surface remains thin - /IG_12UX/ConfigGuide/Loyalty Configuration.htm exposes exactly two fields, 'Promotion frequency (n)' and 'Maximum spend on check' - and the only related control found elsewhere is /IG_12UX/ReleaseNotes/Maximum Discount Limit on Promotions - Agilysys Loyalty & Promotions.htm. The reporting side offers /IG_12UX/ReportsGuide/Loyalty Earned Transaction Detail.htm, an earn ledger rather than a fraud control. Velocity limits, manager approval on manual point adjustment and employee self-redemption flagging would sit in the Agilysys Loyalty & Promotions SKU, which publishes no documentation on ig.onagilysys.com and no separate help system (only ig.onagilysys.com and eatec-userguide.onagilysys.com resolve; developer./docs./support./help.agilysys.com do not). || 325th: 325th: NEW SURFACE - the Agilysys Loyalty & Promotions SKU does now publish a sell sheet (found by enumerating the WordPress media library through the Wayback CDX index, since /en/wp-json exposes no wp/v2 routes and wp-sitemap.xml lists no media; live 200, 562,719 bytes, nonsense-path control 404). It is the first first-party description of the SKU this record has held, and it names the loyalty rule surface as 'customizable earning, redemption, and expiration rules' plus 'Targeted Promotions & Offers ... based on guest segments, behaviors, visit frequency, or spend thresholds' and 'Built-In Tracking & Performance Insights ... Monitor program performance, guest engagement, and redemption activity'. Nothing in it is a fraud control: no velocity or per-period redemption limit, no manager approval on manual point adjustment, no employee self-redemption flag, no audit log. That is a marketing sheet (grade D at best, and it disclaims itself - 'for illustration purposes only' - and still carries lorem-ipsum placeholders), so it cannot carry a no; the SKU's configuration documentation remains unpublished. Unknown (unchanged). Retrieved 2026-09-17. || 326th: 326th: the full published-collateral census confirms the gap without closing it. Across 117 documents / 3,079,354 characters (the closed 28-datasheet product-resource manifest plus 84 live flat-path wp-content PDFs), tokenised word-boundary case-insensitive: 'velocity' 2 (both the FY23/FY24 10-K business phrase, POISON), 'self-redemption' 0, 'manager approval' 0, 'audit log' 0. 'fraud' scores 63 across 18 documents and every one is PAYMENT fraud - Agilysys Pay, Agilysys Authorize ('reduce fraud exposure with PCI-Compliant processing, tokenization, and secure authorization workflows'), IG Quick Pay and the Audit Committee Charter - not loyalty-redemption fraud. The Loyalty & Promotions sell sheet read in the 325th remains the SKU's only public document. Unknown stands. Retrieved 2026-09-18. || 327th: 327th: NEW SURFACE, same answer. The Loyalty & Promotions product page (43,079 characters, seven feature panels and an eight-question FAQ) is the fullest public description of the SKU and its only control language is margin protection, not fraud: 'Rule-based controls protect margins', 'Precision Promotion Engine - create item-specific, outlet-specific, or post-type promotions to influence behavior without eroding margin', and reporting that tracks 'redemption rates, guest engagement, and revenue impact'. Tokenised over the FIRST body-level census of www.agilysys.com's HTML pages (prior passes read only ~9 legal pages plus the 117-document PDF library): the publisher's own page manifest https://www.agilysys.com/en/wp-sitemap-posts-page-1.xml lists 117 pages and all 117 were fetched at HTTP 200 (1,846,153 characters of stripped text); the nonsense control https://www.agilysys.com/en/zzz-nope-control-qq/ returns 404. (The WP REST API still withholds wp/v2 - /en/wp-json/ lists 68 routes in 10 namespaces, and wp/v2/types, wp/v2/media and wp/v2/solution_partner all 404 with rest_no_route, re-confirmed today.) : 'audit log' 0, 'velocity' 3 - all three POISON (Eatec inventory velocity, gift-card and kiosk throughput marketing) - 'self-redemption' 0, 'manager approval' 0. Retrieved 2026-09-18. || 331st: 331st: body-level control over the InfoGenesis help corpus on disk (.cache/q316/agilysys/corpus.json: 5,627 topic bodies, 10,620,922 characters; built from the MadCap MasterTOC manifests of all 7 IG help systems (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM), 5,540/5,540 TOC topics at HTTP 200, plus an href fixpoint): 'redemption|redeem' within 60 chars of limit/approval/velocity/maximum/security level = 7 hits in 4 topics, none a loyalty fraud control. POISON named: https://ig.onagilysys.com/help/POS/IG_Kiosk/ConfigGuide/Add%20Payment.htm 'Maximum Redemption | Enter the maximum redemption' sits in the Kiosk PROMO-CODE block (next to 'Allow Multiple Promocode', 'Allow 100% Discount') - a promo-code cap, not a points-redemption velocity limit; IG Fly 'Apply Promotions at Fly Loyalty' 'maximum value on discount prizes when redeeming promotions' is a discount-size cap configured in the Loyalty & Promotions SKU; the rest is the 19-character promotion-code length limit. 'point(s) adjust*' 0, 'self-redemption' 0. Retrieved 2026-09-18. || 334th: NEW SURFACE (334th): the Agilysys Knowledge Center's InfoGenesis training courses are Supademo interactive walkthroughs of the live product, never opened by a prior pass (prior passes read only the course TITLES on /en/knowledge-center/). The three InfoGenesis course pages (https://www.agilysys.com/en/knowledge-center-videos/?course=<base64 title>: Back of House for Menu, Inventory and Admin Setup; Front of House for Ordering, Payments and Guest Service; Reporting) link 318 distinct demos, and all 318 were fetched anonymously at HTTP 200 from app.supademo.com/demo/<id>; each page embeds its full step list (narration 'audioText', on-screen callouts, screenshots) in the Next.js flight payload: 17,548 text fields, 780,574 characters, 7,219 screenshots. Vendor-authored tutorials walking the actual IGCM / POS terminal UI (grade B as documentation of what they show; a training set, not a census of the product). Over all 318, tokenised: 'loyalty' 0, 'redeem/redemption' 0, 'points' 0 (every 'point' is 'point of sale'). 'fraud' scores 2, both in 'Increasing Zero-Dollar Authorization to Check Total Automatically' ('Enable Authorization Fraud Prevention Feature' terminal option) - a card pre-authorisation control, POISON for this cell. The 40-demo Digital Marketing course also scores 'loyalty' 0. No loyalty fraud control is taught. Retrieved 2026-09-18. adversarially verified

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

InfoGenesis markets 'AI Guest Intelligence' with predictive insights and embedded upselling, and Analyze offers AI insights — marketing claims, not a documented offer-content/audience/send-time recommender. https://www.agilysys.com/en/products/infogenesis-pos/ · 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

Closed-loop stored value with real-time balance, multi-outlet and cross-property redemption, guest self-service reload portal, integrated with PMS and InfoGenesis POS. https://www.agilysys.com/en/products/gift-card/ · 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

Source citation is wrong — I fetched Default.htm and it is only a landing page linking to six product guides; it documents no clock-in. The capability is nonetheless verifiable from a first-party source: the Agilysys-published App Store listing states 'Allow Employees' to clock-in and clock-out - Provide access permissions based on job code'. Upheld on substituted evidence, not on the cited one. https://apps.apple.com/us/app/infogenesis-pos-terminal/id1534574604 · retrieved 2026-08-01 adversarially verified

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-evidenced 2026-08-08, withdrawing the false 'no labor module' premise - InfoGenesis does have timekeeping. The Clocking In and Out topic enumerates the punch method exhaustively: 'Swipe, scan or tap the employee ID card or enter employee credentials at the Sign On screen' followed by 'Select the appropriate role.' No camera, photo capture, facial verification or biometric step appears there or anywhere in the 1,691-topic help set; the supported terminal options for clock-in/out are 37, 38 and 215, which govern slip printing and manager override only. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Clocking%20In%20and%20Out.htm · retrieved 2026-08-08 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-evidenced 2026-08-08, withdrawing the false 'no labor or scheduling product' premise. Clocking in is documented as a terminal action - card swipe/scan/tap or credentials at the Sign On screen, then role selection - and clock-out is via Jump Bar to Function or the User screen. The first-party mobile apps documented by the Help Center are IG Fly/IG Flex (server handhelds), IG Kiosk and IG OnDemand (guest ordering); none offers a punch clock, and no geofence, GPS or location-validation topic exists in the 1,691-topic set. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Clocking%20In%20and%20Out.htm · retrieved 2026-08-08 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

Re-evidenced 2026-08-08 with direct documentation, withdrawing the false 'no labor module' premise. The Go Offline topic states: 'When the terminal is offline, none of the reports are generated. The user cannot clock out or clock in when the terminal goes offline. Most of the terminal functions cannot be performed when the terminal goes offline.' Time punches are therefore not recorded offline at all, so there is nothing to reconcile on reconnect. Agilysys does document offline tender limits, offline kitchen printing and offline kitchen video, so the exclusion of timekeeping is deliberate and stated. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Go%20Offline.htm · retrieved 2026-08-08 adversarially verified

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

Back-office IGCM permissions are genuinely granular: permission groups per form, listing, executable and report with separate view/add/edit/delete rights, roles per enterprise and tenant-level roles (Centralized User Role Management). Shortfall: terminal-side authorization rides a fixed ladder - 'security levels are inclusive and ascending, with the higher security levels possessing all the rights and properties of a security level below them' (0-9, applied to items, void reasons and meal periods) plus per-job-code function activation; discrete per-action grants per role are not the terminal model. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Security%20Level.htm · retrieved 2026-08-03

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

Overrides are attributed to the individual approver: a manager override requires a specific employee's credentials at security level 5-9 and is rejected with 'the employee does not have sufficient security to perform the manager override' otherwise; the Voided Checks and Refund Return Void Detail reports expose Auth Employee and Auth Employee ID as grouping, sorting and filter dimensions queryable after the fact. IGCM configuration changes are separately captured by the Audit Logging utility with user, operation and date filters plus export. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/Voided%20Checks%20Report.htm · retrieved 2026-08-03

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-evidenced 2026-08-08. InfoGenesis does hold the timekeeping data (Clock Data, Clock Activity/Detail reports, Labor Summary), and the IGCM does have a module named Scheduling - but it is not staff scheduling: 'Task Scheduling provides a way to schedule and launch tasks on one or more servers... Examples of user-defined tasks are: scheduling an executable, scheduling a report group to run on demand or at an exact time, an employee export, or SQL database maintenance.' The other 'schedule' topics are Meal Period, DayPart, Price Tier, Screen and Schedule Price Change. No shift roster is built or published in the platform. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Scheduling.htm · retrieved 2026-08-08 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

Analyze provides AI-driven demand forecasting and seasonality projections explicitly to help teams plan staffing; it does not output recommended labor hours into a scheduling tool, because none exists. https://www.agilysys.com/en/products/analyze/ · retrieved 2026-08-01

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

Overturned from no on audit: the prior premise ('no live labor-hour data') is false - punches are native and the terminal report list includes 'Hourly Sales and Labor' for the CURRENT calendar day (by check open or close time) plus a 'Productivity Flash Report (current calendar day / current Productivity Period)' that 'provides the management with a summary of customer volume, gross revenue, discounts, net revenue, and labor costs' - intraday sales-versus-labor pulled at the POS during service. Shortfalls: no labor-as-percentage-of-sales metric is documented anywhere, and this is an on-demand terminal report, not a persistent real-time manager view. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/POS%20Terminal%20Reports.htm · retrieved 2026-08-05 adversarially verified

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

Re-evidenced 2026-08-08, withdrawing the false 'no labor/scheduling module' premise. The clock-in topic enumerates the terminal options that govern punching - 37 (disable clock-in slip printing), 38 (disable clock-out slip printing), 215 (clock-out manager override with open checks) - and no overtime threshold, approaching-overtime warning or clock-in block appears among them. No topic in the 1,691-topic help set matches 'overtime', and there is no hours projection to test a threshold against because no shift schedule exists. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Clocking%20In%20and%20Out.htm · retrieved 2026-08-08 adversarially verified

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

Native timekeeping is clock-centric only: Clocking In and Out, Auto Clock-Out and the clock reports document no break configuration of any kind. Breaks appear solely in the 7shifts Restaurant Team Management integration release note - 'Perform Scheduled Login, Perform Unscheduled Login, Capture Time Punch, Calculate Breaks' - whose only stated rule is that 'break time is only considered valid if there is a minimum of 1 minute interval between sign-in and sign-off period'. No per-state or per-jurisdiction break rules, no break-attestation prompt and no missed-break premium-pay flag exist anywhere in the documentation; break handling is delegated to the third-party labor platform. https://ig.onagilysys.com/help/POS/IG_12UX/ReleaseNotes/InfoGenesis%20POS%20Integration_1.htm · 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

Re-evidenced 2026-08-08. Predictive-scheduling compliance needs a published shift schedule, and the IGCM's Scheduling module schedules server tasks and report groups, not staff: 'Task Scheduling provides a way to schedule and launch tasks on one or more servers.' No topic in the 1,691-topic set concerns advance notice, schedule publication, predictability pay or employer-initiated change tracking, and none of Agilysys' 37 product pages is a workforce-management product. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Scheduling.htm · retrieved 2026-08-08 adversarially verified

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

labor-minor-labor-rules

Neither half of the claim exists natively. Scheduling: InfoGenesis has no employee-scheduling module - schedule-aware login exists only through the 7shifts integration ('Perform Scheduled Login'). Clock-in: the documented procedure is swipe/scan/enter credentials and select a role, with job-code configuration, clock-in/out slips and manager override for clocking out with open checks - no age-based hour caps, prohibited time windows or school-day limits. 'Minor' (in the labor sense) returns zero topics across every indexed help set. Enforcement 'at both scheduling and clock-in' is not possible in a product that documents neither construct. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Clocking%20In%20and%20Out.htm · 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

Re-evidenced 2026-08-08, withdrawing the claim that Agilysys publishes no tipping module. InfoGenesis documents tipping in depth, and the whole of it is enumerable: Tip Configuration (No limit / Warn when exceeded / Manager override when exceeded / Do not allow when exceeded, with a Max. Percent field per profit centre), Suggested Tip Tables, Tip Amount, Tip Limit, Tip Payout, Tip Percentage, Tip Transfer, Transfer Check Tips, Self Check Tip Transfer, plus Gratuities, Gratuity Category and VAT Gratuities; reporting is IRS Tips, IRS Tips and Gratuity, Gratuity and Service Charge, Server Shift Sales Tips and Gratuity, and Tip Transfer Detail. Nothing in the 1,691-topic set is a tip pool, tip-out or distribution rule - tips move employee to employee by manual transfer, and no percentage-of-sales, hours, points or role allocation basis is configurable. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Tip%20Configuration.htm · retrieved 2026-08-08 adversarially verified

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

Per-shift, per-employee tip records exist and reconcile across reports: Server Shift Sales Tips and Gratuities (per shift reset), IRS Tips Report (charged tips, declared cash tips, gratuities and transfers in/out per employee) and the Tip Transfer Detail Report showing every transfer with date/time, from-employee, to-employee and amount, reconciling to terminal reports 190/191. Shortfall: there is no tip-pool construct - pooling must be executed as manual employee-to-employee Tip Transfer functions, so pool contributions and distributions appear only as transfers in/out. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/Tip%20Transfer%20Detail%20Report.htm · retrieved 2026-08-03

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

Half the claim is documented and half is absent from the whole published corpus. Agilysys addresses the qualified-tips distinction head-on: release 12.3.14.7 'Segregate Tips and Gratuity in Reports' separately tracks discretionary tips from non-discretionary gratuities and service charges, states that only discretionary tips 'will be considered as qualified tips' while an automatic or non-modifiable gratuity 'is not considered as qualified tips even when distributed to employees through pooling or tip payout', and says the point is 'making reports tax-compliant, audit-defensible, and aligned with regulatory requirements preventing any non-discretionary amounts from being treated as deductible amounts during tax reporting'; it adds Terminal Options 1514/1517, a Track Tips & Gratuities Separately store checkbox and Grats Transfer columns on the IRS Tips and Tip Transfer Detail reports. The delivered IRS Tips Report separates Charged Tips from Declared Cash Tips per employee with Charged Tips/Grats Sales and Ratio columns. SHORTFALL: there is no payroll interchange and no tax-code carriage. `W-2`, `Box 12`, `tipped occupation` and `payroll export` occur ZERO times across the entire 8,068-document estate; report output is Acrobat, Excel or 'exported to other programs'; and the 7shifts integration, the documented payroll-adjacent path, publishes only employee and job-code entity mapping ('One 7Shifts job code can be mapped with only one POS job code') with no tip or earnings fields. So the qualified/non-qualified split exists in REPORTS, but TY2026 Box 12 code TP and Box 14b cannot be emitted by anything Agilysys documents. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/IRS%20Tips%20Report.htm · 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

Re-evidenced 2026-08-08, withdrawing the false statement that payroll appears as a partner category - Agilysys' Solution Partners directory has 31 categories and payroll is not among them. The vendor's own page inventory lists 37 /en/products/ pages (PMS, SWS, InfoGenesis POS, Eatec, Book, Book4Time, Reserve, Sales & Catering, Golf, Spa, Membership, Central Reservation, Express Kiosk, Express Mobile, Residence Management, Retail, Service, IG Flex, IG Fly, IG OnDemand, IG Kiosk, IG PanOptic Kiosk, IG KDS, IG Digital Menu Boards, Pay, Authorize, IG Quick Pay, Gift Card, Digital Marketing, Loyalty & Promotions, DataMagine, Analyze and Book4Time sub-pages); none is payroll. InfoGenesis produces Clock Activity, Clock Detail, Current Clock In and Labor Summary reports and an employee export task - i.e. payroll inputs for a third party, not tax filing or direct deposit. https://www.agilysys.com/en/wp-sitemap-posts-page-1.xml · retrieved 2026-08-08 adversarially verified

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

Solution Partners lists a payroll/accounting category naming PayDayPortal and GoCardless; two major named payroll providers with documented export formats are not confirmed. https://www.agilysys.com/en/solution-partners/ · retrieved 2026-08-01

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

Re-evidenced 2026-08-08. The IGCM Scheduling module schedules server tasks and report groups ('scheduling an executable, scheduling a report group to run on demand or at an exact time, an employee export, or SQL database maintenance'), not staff shifts, so there are no open shifts to claim and nothing to swap. No self-service employee app is documented - the Help Center's six help sets are POS Terminal, IG Kiosk, IG OnDemand, IG Fly, IG KDS and IG Digital Menu Board - and no approval-workflow topic exists in the 1,691-topic set. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Scheduling.htm · retrieved 2026-08-08 adversarially verified

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

labor-digital-onboarding-i9

Re-evidenced 2026-08-08. The IGCM Configuration Guide states it 'contains information about all the modules in the IGCM' - POS Configuration, Utilities, User Management and Reports - and its employee topics are Employees, Employee Group, Assign Employees, Clock Data and employee card assignment, with job codes mapped per employee. No W-4, I-9, E-Verify, tax-withholding or onboarding-document topic exists in the 1,691-topic help set, and none of Agilysys' 37 product pages is an HR product. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Contents.htm · retrieved 2026-08-08 adversarially verified

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

InfoGenesis POS Reports Guide, Cashier Performance: 'shows data for a single store only ... a broad range of summary-level performance indicators for each cashier'. Documented fields include Net Checks, Net Revenue, Avg Check ('the Average Net Revenue per Net Check', Total Net Revenue / Total Net Checks), Disc Qty ('the quantity of all discounts applied by the cashier, either at the item or check-level'), Discount Amount, Disc % ('the percent of gross revenue given as a discount'), Refund + Return Amt, Void Amount, No Sale Quantity and Over/Short; it can be grouped and sorted by Discount %, Discount Amount, Void Amount, Void Quantity, Refund Amount, Refund Quantity and No Sale Quantity, filtered by Business Period, Meal Period, Cashier, Profit Center and Store. The companion /ReportsGuide/Server Sales Report.htm reports per server ID/name: Net Revenue, Discount, Gratuity, Tip, Service Charge, # of Checks, # of Covers, Avg Check ('Net Revenue divided by the number of checks') and Avg Cover, grouped by profit center and primary job code. /ReportsGuide/Server Sales by Items Added Report.htm covers the item-attachment dimension, and Enterprise Cashier Performance Report rolls it up across stores. That is per-employee average check, comp/discount rate and void rate as the claim asks. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/Cashier%20Performance.htm · retrieved 2026-08-08

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

Eatec provides dynamic recipe costing tied to ingredient pricing with standardized recipes across locations; multi-level sub-recipe (prep item) nesting is not explicitly documented publicly. https://www.agilysys.com/en/products/eatec/ · 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

The full unit model exists, but in Eatec - the separately licensed Inventory & Procurement suite - not in InfoGenesis POS itself. Eatec's public user guide documents units for 'the purchased or ordered items, packages, and recipes' (Setup > Global > Unit), a Unit Conversions page with explicit From Unit / To Unit / Conversion factor records, recipe-unit (RU) linkage per item, purchase-unit reporting (Inventory Activity by Item in Purchase Units, Current QOH & Value in Purchase Unit) and differentiated UOM for physical inventory counts. Yield/waste: default ingredient conversions 'may be altered within the recipe to account for shrinkage/yield and waste', a Refuse percentage reduces raw-to-usable weight (e.g. 10% for an apple core), and butchery yield-% reporting exists. Shortfall: requires the Eatec SKU on top of the POS. https://eatec-userguide.onagilysys.com/UserGuide/Managing%20Recipe.htm · retrieved 2026-08-04

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

Eatec markets COGS accuracy tracking, perpetual inventory and margin performance monitoring; an explicit theoretical-vs-actual variance report in units and currency is not documented publicly. https://www.agilysys.com/en/products/eatec/ · retrieved 2026-08-01

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

Real-time stock tracking and perpetual inventory for foodservice and retail are documented; modifier-driven depletion at fire time is not. https://www.agilysys.com/en/products/eatec/ · retrieved 2026-08-01

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

IG_12UX ConfigGuide, Item Countdown: items and modifiers are assigned to countdown groups (one per profit center) with per-item Quantity on Hand, Warning and Cut Off values - 'Quantity on Hand ... depletes as each unit of the item is added to a check, and the check is saved or tendered ... When the item is voided, the quantity increments'; 'Warning ... the quantity at which the POS terminal must warn the user that the item quantity is almost reaching the 86 level'; 'Cut Off ... the quantity at which the item would be 86'd'. Automatic firing is Terminal Option 293 (Automatically 86 items), with 290 (Enable item countdown), 291, 530 (Send 86/un86 to terminals in all profit centers) and 1314. Propagation to digital channels is documented in IG_OnDemand /UserGuide/Sync 86/Un86 Status from Item Countdown Menu in IGCM.htm: 'Users can sync the 86/Un86 status of items in the OnDemand application from the Item Countdown menu in IGCM or through the POS terminal ... OnDemand verifies if the item is 86'ed/un86'ed from the InfoGenesis database' (To Go and Full Service profiles), and in IG Kiosk (/UserGuide/86 Un86 Items.htm, /UserGuide/Display 86ed Items and Modifiers.htm). SHORTFALLS: (1) the countdown is a finished-menu-item quantity, not a component-ingredient balance - depletion of an Eatec ingredient to zero is nowhere documented as driving a POS 86; the Eatec/InfoGenesis link documented is product, modifier, allergen, price-level and quick-order export plus sales import, not stock-to-86; (2) no third-party marketplace menu is touched - no DoorDash/Uber/Grubhub topic exists in the 5,336-topic corpus; (3) /IG_12UX/UserGuide/Global Application Service (GAS) Offline Scenarios.htm warns that items 86ed while GAS is down stay local and 'must be manually re-86ed after GAS connectivity is restored'. https://ig.onagilysys.com/help/POS/IG_OnDemand/UserGuide/Sync%2086%20Un86%20Status%20from%20Item.htm · 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

Mobile inventory tools for counts and transfers are documented; full/spot/cycle count modes and per-count variance history are not enumerated. https://www.agilysys.com/en/products/eatec/ · retrieved 2026-08-01

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

Mobile counting tools plus UPC/SKU support for retail merchandise are documented; offline counting with sync-on-reconnect is not stated. https://www.agilysys.com/en/products/eatec/ · retrieved 2026-08-01

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

Eatec New Features, Vendor Punchout - Sysco Foods Supplier Integration: 'Eatec has been enhanced to support the Vendor Punchout integration between Sysco Foods with the latest updates as part of this release', applicable to the Suppliers, Purchase Request and Purchase Order modules, with the workflow described as 'The buyer exits (punches out) Eatec and enters the supplier's web-based catalogue ... the shopping cart with the selected items is brought back to Eatec ... An order is not submitted to the supplier until the buyer has added the line items to a purchase request and the purchase order is approved and sent to the supplier.' The same topic names the electronic transport it feeds: 'Purchase Order EDI', 'EDI Invoice Import' and 'MA Invoice Import (file based)'. The corpus carries a full EDI stack, not a mention: Enhancements in EDI850 PO Export File; Addition of DTM Segment in PO Confirmation EDI 855 File; Enhancements in EDI 855 Confirmation Import File; EDI 855 PO Enhancement: Handle Special Order Remarks; EDI 810 Import Enhancement - Read Misc. Charges from SAC Segment; EDI 810 Invoice Import Enhancement - Update Linked Purchase Order; Import Supplier Item Number for PO Invoice Import in EDI 810 File; Custom Lookup for Customer Account Number in EDI 810; Enhancements in EDI Credit Invoice; /UserGuide/Saved EDI Invoices.htm; and 26.2.5_RN Enhanced EDI Invoice Management with Duplicate Validation and Deletion Controls. A second named punchout supplier is Amazon (/NewFeatures/Vendor Punchout - Amazon Integration.htm). SHORTFALL: Sysco is the only broadline distributor named - US Foods, PFG, Gordon and Sysco's regional peers appear nowhere - and all of this is in Eatec, a separately licensed Inventory & Procurement product, not InfoGenesis POS. https://eatec-userguide.onagilysys.com/NewFeatures/Vendor%20Punchout%20Sysco%20Foods.htm · 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

Eatec documents automated invoice processing and reconciliation; extraction from photo/PDF/email via OCR is not specified. Agilysys separately ships DataMagine for document imaging. https://www.agilysys.com/en/products/eatec/ · retrieved 2026-08-01

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

Eatec New Features, Receiving Tolerance Percentage for Inventory Type, Inventory, and Suppliers: 'This feature allows users to define receiving tolerance for each inventory item that overrides to the tolerance percentage defined in the Setup > Inventory Type. Based on the system preference to display a warning message, Eatec validates the cost change for an item based on this tolerance percentage.' At receiving (MA): 'All cost change validations are processed with respect to the basic cost/unit loaded ... The percentage of cost changes is reported at each item level on a real-time basis ... The % cost change is highlighted only when the % cost change values are greater or less than the defined tolerance percentage', with % Cost Change and Tolerance % columns on the line. The threshold ladder is configurable at Setup > Inventory Types via a 'Price Change Allowed %' drop-down offering Warn if modified, Warn if over 10%, 20%, 30%, 40%, 50%, overridable per item under Masters > Inventory List > Settings; the system preference at Setup > System Preference > Purchasing Options selects 'No Warning for Cost Changes' or 'Warn if Cost is Over Predefined % in Item (or) Type'. The prior/contracted price is carried by Supplier Bids (Request for Bids, Link Bids, Bid Region, Items without active Bids) and history by /ReportsGuide/Item Cost Changes/Detail [PUR19].htm and Item Cost Changes/Summary [PUR19b], which report 'inventory item purchases performed between a given date range' with invoice details. SHORTFALLS: the alert is an in-transaction warning at receiving, not a push notification or exception queue, and the documentation notes that on Purchase Orders 'There are no validations/cost change alerts that are notified to the user'; and it requires the separately licensed Eatec module. https://eatec-userguide.onagilysys.com/NewFeatures/Receiving%20Tolerance%20Percentage.htm · 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

Automated replenishment logic plus demand-forecasting integration is documented; explicit per-item per-location par levels driving suggested PO quantities are not spelled out. https://www.agilysys.com/en/products/eatec/ · 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

Eatec User Guide, Creating Spoilages and Loss: reached at Inventory Management > Spoilage and Loss > New Spoilages & Loss, the header fields are Location, Post Date, Reason ('The cause of spoilage. Select the cause of spoilage from the drop-down list'), Reference, Remark, Approved By, Department and Override Account Number; items are added from Items/Packages/Class/Type with Unit, Pack Size, Quantity and Remarks, and the transaction is committed with Post Spoilage ('activated only upon entering the quantity of the item/s'). Depletion is explicit in /NewFeatures/Inventory Depletion by Spoilage for Configured Location.htm, reversal in /UserGuide/Reversing Spoilage and Loss.htm, and approval routing in /UserGuide/Document Approval - Process Documents for Req/PR/PO/Spoilage & Loss.htm with e-mail approval notifications. Waste cost is reported separately from usage variance by a dedicated report family: Spoilage/Loss Detail [INV61], Spoilage/Loss Summary [INV61S] and Spoilage & Loss Form [SLFRM01], distinct from the Variance Report (Single Day) [INV42] / by Location [INV42L] usage-variance family, with Usage Detail by Item/Sort by Waste [INV03D] bridging the two. SHORTFALL: the entire workflow lives in Eatec, a separately licensed Inventory & Procurement product, not in InfoGenesis POS - no waste or spoilage topic exists in any of the seven POS help sets. https://eatec-userguide.onagilysys.com/UserGuide/Creating%20Spoilages%20and%20Loss.htm · retrieved 2026-08-08

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

Eatec provides mobile inventory tools for counts and transfers with centralized multi-property controls retaining location-level visibility. https://www.agilysys.com/en/products/eatec/ · 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

Eatec offers commissary operations as a named optional add-on module alongside catering management and nutrition tracking. https://www.agilysys.com/en/products/eatec/ · retrieved 2026-08-01

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

Eatec New Features, Selecting Lots for Production Recipe of FG Item: with the 'Choose Ingredient Lots' checkbox enabled the user is 'provided with all lots available for the linked items of the selected production recipe and sub-recipes linked for an FG item for Production and Butchery' and specifies, per ingredient, 'the quantity of the item ... that must be depleted'; the finished good itself takes Lot ID, Manufactured Date and Expiry Date, and on posting Eatec will 'Deplete inventory item Lot QOH as per user selection' and 'Record inventory usage activity'. That is the production link between raw lot and finished lot. Both directions are reported: Production Lot Activity by FG Item [INV54] and Production Lot Activity by Raw Item [INV55]. Lot capture and maintenance are documented in /NewFeatures/Modifying Lot ID Value under Lots in Inventory List.htm ('The modified Lot ID is referred in all areas like lot lookup and lot reports ... The changes to Lot ID is tracked under the Lot History for audit purpose'), /NewFeatures/Filter Option in Lots for F&B Inventory Item.htm (filters Locations, Source, Posted On, Expiry Date, Last Physical Date), /UserGuide/Reset Inventory Lots.htm and /NewFeatures/Modify Lot QOH from Inventory Reset.htm; movement retains lots via /NewFeatures/Transfer Edit Enhancements with Batch, Lot, and Bin Retention.htm and /NewFeatures/System Preference to Disable Appending Transfer ID to Lot ID.htm; picking is served by Order LOT Picklist [QOOR01_Lots] and configuration by Item Lot Setup [ItemLotSetup]. SHORTFALLS: the forward trace runs to transfers, sales orders and quick orders inside Eatec, and no topic links a lot through to an InfoGenesis POS check line, so trace-to-sale at the guest-check level is not shown; and the whole capability requires the separately licensed Eatec module. https://eatec-userguide.onagilysys.com/NewFeatures/Selecting%20Lots%20for%20Production.htm · 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

Eatec New Features, Filter Option in Lots for F&B Inventory Item: on Masters > Inventory List > (F&B item) > Edit > Lots the Column Filter offers Locations, Source, Posted On, Expiry Date and Last Physical Date - so an expiry date is held per lot and can be filtered on. /NewFeatures/Selecting Lots for Production Recipe of FG Item.htm shows it being set automatically on output: the finished-good line carries 'Manufactured Date - the manufacturing date of the FG item' and 'Expiry Date - the expiry date of the FG item gets auto updated', for both Production and Butchery, alongside 'Deplete inventory item Lot QOH as per user selection. If there is no user selection for an ingredient lot, then the required quantity is depleted under the default lot depletion logic.' SHORTFALLS: no expiring-soon report exists in the 254-topic Eatec Reports Guide - a sweep of all 1,448 Eatec topic paths and titles for expir|shelf|use-by|FIFO|freshness returns only this lot filter and a supplier-bid effective/expiry bulk edit; no alert, notification or dashboard warns before spoilage, so surfacing depends on a user opening the Lots tab and sorting; the default lot depletion logic is not documented as FIFO or expiry-ordered; and the capability requires the separately licensed Eatec module. https://eatec-userguide.onagilysys.com/NewFeatures/Filter%20Option%20in%20Lots%20for.htm · retrieved 2026-08-08

Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting.

inventory-bar-partial-bottle

A partial container can be counted, by a generic multi-unit mechanism. Eatec’s Differentiating UOM for Physical Inventory lets a counter 'add / (front slash) in between the quantity count in the Quantity field to differentiate the units of measure (UOM) such as TU/BU/PU/RU while posting or modifying the counts/cycle counts', e.g. '5/6/8/3', and 'The system calculates the quantity and converts the values based on the actual unit'; Units supplies the convertible basis - 'Convertible units are standard weight or liquid volume units, such as quarts, gallons, ounces, and pounds' - and Units 'include metric, standard volume, weight units, and bottle units'. SHORTFALL: there is no scale or weighing-device integration for inventory counting anywhere (the only documented scale is the POS checkout scale for sold-by-weight items), no bottle-fraction or tenths field, and no per-ounce pour-cost report; the remainder must be keyed by hand in a smaller unit. `self-pour`, `flow meter`, `tap wall` and `keg` occur ZERO times across the entire 8,068-document estate. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://eatec-userguide.onagilysys.com/NewFeatures/Differentiating%20UOM%20for%20Physical.htm · retrieved 2026-09-12 adversarially verified

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

Eatec documents GL export capabilities and accelerated month-end close; no named accounting import format or per-category GL mapping is published. https://www.agilysys.com/en/products/eatec/ · 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

Agilysys publishes its own Eatec user guide. Setup > Interface > POS Mappings is Eatec's first-party POS integration module - 'Users use the POS Mappings module to post sales in Eatec through a POS system', configured with POS System, POS Text, Store ID, connection/service manager URL, Enterprise ID, POS Site ID and POS Location (used in calculating QOH). Recipe costing is likewise Agilysys's own: Recipe Extended Costs supports real-time cost updates, general ledger accounting and role-based access across Production, Butchery and Finished Goods Transfers. Caveat: Eatec is a separately licensed SKU from InfoGenesis POS, and Recipe Costing is an optional Eatec module - but both are Agilysys products, so the vendor-native test is met. https://eatec-userguide.onagilysys.com/UserGuide/Interface.htm · retrieved 2026-08-06

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

Analyze provides menu engineering analytics covering item performance, contribution margins and sales trends; automatic flagging of items below a configured margin threshold is not documented. https://www.agilysys.com/en/products/analyze/ · 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

Analyze ships role-specific dashboards for F&B, rooms, spa, golf, retail and events with mobile-ready real-time access and instant alerts. https://www.agilysys.com/en/products/analyze/ · 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

InfoGenesis ReportsGuide, Sales Balance Report: 'a consolidated report that provides information on multiple areas of the POS system such as employees, tenders, checks, meal period, and sales transactions.' One document carries Gross Revenue, (-) Discounts, (=) Net Revenue, (+) Tax Collected, (+) Gratuity, (+) Service Charge, (+) Tips Collected, (+) Refund Amt, Void Amt, a Tender sub-report breaking every configured tender out by quantity and amount, then Cash Tender, Total Cash Drop, (-) Accountable Cash and (=) Over/Short, where Accountable Cash = (Total Tenders - Change) + Loans - Withdrawals - Tips Paid - Non-cash Tenders is the expected cash deposit. The Daily Sales Report gives the same close-out per cashier and terminal after a shift reset. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/Sales%20Balance%20Report.htm · retrieved 2026-08-08

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

Item-level performance and contribution margin reporting is documented via Analyze menu engineering; modifier-level PMIX and daypart/revenue-center filtering are not confirmed. https://www.agilysys.com/en/products/analyze/ · 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

ReportsGuide 'Anti-Fraud Controls': 'Voids are tracked by the POS terminal application according to the authorizing employee and reported in the Electronic Journal, and the Void back-office reports... The following back-office reports record the ID of any manager performing a Void override in the Authorize Emp ID field: Void Checks, Void Item by Authorizing Employee, Void Item Detail', and 'EJ message 5013 (Manager Override) logs all manager overrides performed for voids at the POS Terminal. The Additional Data field in the EJ log shows the Manager ID as well as the void reason.' The Voided Checks Report filters and groups on Auth Employee, Server, Reason ID, Reason Description and Closed Date; the Discount Detail Report (check- and item-level discounts, and comp tenders per Tax Configuration 'Comp (Ent. Tax)') groups and filters on both Cashier and Auth Employee with Closed Date/Time. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/Anti%20Fraud%20Controls.htm · retrieved 2026-08-08

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

ReportsGuide, Cashier Tender Shift Report: 'provides information to balance the cash drawer... breaks down the information by business period and shift', with Total Tenders, +Loans, -Withdrawals, -Tips Paid Out, -Non-cash Tenders, '= Accountable Cash' (the expected physical cash the cashier or server-banker is responsible for), Cash Dropped and 'Over/Short = Cash Drop Amount - Accountable Cash'. The parallel Terminal Tender Shift report gives the terminal/drawer view ('profit centers that perform cashier shift resets rather than terminal shift resets... support employee accountability rather than terminal accountability'), and the Cashier Performance Report repeats Account. Cash, Cash Dropped and Over/Short per cashier. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/Cashier%20Tender%20Shift.htm · retrieved 2026-08-08

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

Shortfall: no sales-per-labor-hour figure, and labor % is not broken out per employee. The 'Hourly Revenue with Labor Data' report (introduced in IGCM 12.3.15, 'InfoGenesis POS has been enhanced to allow users to generate a combined report of sales and labor data') reports, per selected time interval and per profit center, Checks, Covers, Gross Revenue, 'Labor Amount = Sum of individual labor rates of clocked in employees' and 'Labor % = [LaborRate * 100 / Gross Revenue]', using POS clock-in data ('Labor data is displayed only when employee clock-in data is available'). Fixed-period runs are capped at 7 days. The Labor Summary Report gives per-employee reported hours, labor rate and estimated wages by job code, but no revenue, so labor cost per employee cannot be expressed as a percentage of that employee's sales in a delivered report, and sales per labor hour is not computed anywhere in the 122-topic report set. https://ig.onagilysys.com/help/POS/IG_OnDemand/ReportsGuide/Hourly%20Revenue%20with%20Labor.htm · retrieved 2026-08-08

Reports per-server metrics including average check, items per check, attachment rate for named categories, and tips as a percentage of sales. differentiator

reporting-server-scorecards

Shortfall: no items-per-check, no category attachment rate, and tips are reported as amounts rather than as a percentage of sales. The Server Sales Report reports per server: Server ID, Server Name, Net Revenue, Discount, Gratuity, Tip, Tip + Grat, Service Charge, # of Checks, # of Covers, 'Avg Check' (net revenue / checks) and 'Avg Cover', grouped and filtered by profit center, store and primary job code. Server Sales by Items Added attributes item revenue to the user who added the item rather than the check owner, and Server Shift Sales Tips and Gratuities covers tips by shift. None of the 122 delivered reports computes items per check or an attachment rate for a named category. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/Server%20Sales%20Report.htm · retrieved 2026-08-08

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 fulfillment-channel dimension for third-party marketplaces and no netting of marketplace commission. Product Mix - Margin Report reports item margin ('Margin is the revenue left over after an item's cost is subtracted from its sales price') with Items Sold, Gross Revenue, Discounts and Net Revenue, grouped by item, product class, profit center, meal period, check type, report category or profit center group; Product Mix - Revenue by Originating Profit Center attributes revenue to 'the profit center in which an item is ordered', which separates a kiosk, IG OnDemand or QR outlet configured as its own profit center from the dining room. The Licensing Activity Report is the only report carrying an order-origin field (CheckOriginationType: POS Terminal Application, Tpg, Atpg, OrderWebApi, TenderCheckWebApi) and it reports transaction counts, not revenue. Nothing in the delivered report set records a marketplace commission or a first-party vs marketplace delivery split. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/Product%20Mix%20Margin%20Report.htm · 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

Analyze consolidates PMS, POS, spa, golf, retail and F&B across single or multi-property portfolios; side-by-side store ranking and drill-through to an individual transaction are not documented. https://www.agilysys.com/en/products/analyze/ · 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

The InfoGenesis back-office portal is described as having flexible reporting and configuration; Analyze's plain-language query is positioned as replacing 'manual report building', implying no conventional drag-and-drop builder. https://www.agilysys.com/en/products/analyze/ · 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

ReportsGuide, Scheduling (Reports > Scheduling > POS Schedule in IGCM): 'Task Scheduling provides a way to schedule and launch tasks on one or more servers... scheduling a report group to run on demand or at an exact time.' A schedule row carries Type (Task or Report Group), Name, Pause, Time Zone, Frequency, Scheduled Time, Customer/Enterprise/Division/Store context, Scheduled By, and a Destination button: 'A different destination is possible by selecting one of the E-mail, Printer, or File Path options', with 'A single report group can be scheduled multiple times to output at different destinations'. The Recurrence prompt sets Hourly / Expires After / No Expiration and a Start Date Time; Task Setup adds SFTP delivery with password, SSH-key or two-factor authentication. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/Scheduling.htm · retrieved 2026-08-08

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

Analyze Data-as-a-Service exports clean data feeds into existing BI platforms; scheduling cadence, destination types (S3/SFTP/Snowflake) and transaction-level granularity are unspecified. https://www.agilysys.com/en/products/analyze/ · 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

The Agilysys API Management developer portal requires sign-in ('Sign in to learn more') and exposes no API list. No self-service developer credentials are obtainable. https://agys-dev.developer.azure-api.net/ · retrieved 2026-08-01

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: delivery is through an Agilysys-provisioned IAS adapter rather than a customer-entered endpoint URL, and no retry behaviour or payload signature verification is documented. Outbound events do exist and their payloads are published: 'IG Fly has been enhanced to... sending the following events to external systems - Order Event... triggered when an order is placed, refunded, or voided. Kitchen Event... triggered when an order is bumped in the kitchen', with a full sample JSON body (type, ctxt.t_id/ent_id/sm_id/term_id, crtdTime, chkInfo, del_info, orders[]) and a field-by-field description table. Event Notification is enabled per enterprise (POS Configuration > Administration > Enterprise > Event Notification) with Order Event and Kitchen Event checkboxes, each bound to an 'IAS Adapter Configuration' and Configuration Group; Employee Event is marked 'For future use'. The release note adds 'Contact Agilysys to initiate this integration at your property. Note that development efforts may be required on both sides.' There is no payment-lifecycle event. https://ig.onagilysys.com/help/POS/IG_Fly/ReleaseNotes/Send%20Order%20and%20Kitchen%20Events.htm · 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

Shortfall: API access is licensed separately per store and API-originated transactions are metered against the customer's contract. ReportsGuide, Licensing Activity Report: 'captures key data for auditing transaction origins that are used for customer contracts/payment plans', reporting total transaction count by Terminal, Profit Center, Store and Enterprise together with the transaction source (CheckOriginationType - POS Terminal Application = 1, Tpg = 2, Atpg = 3, OrderWebApi = 4, TenderCheckWebApi = 5). The IGCM release note 'Move POS API Client License Key from API Registration to API Client' states the change 'allow[s] customers to assign unique license keys to individual store instances, enabling flexible license control across different stores. This feature is targeted only for customers using IG POS APIs.' API Registration is a per-enterprise checkbox with per-client license keys and a POS API Subscription Key. No price is published anywhere: agilysys.com has no pricing page and the Azure APIM developer portal at agys-dev.developer.azure-api.net returns an empty list from /developer/apis?api-version=2022-04-01-preview and /developer/products, so no product or plan is visible anonymously. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/Licensing%20Activity%20Report.htm · retrieved 2026-08-08

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

Upgraded 2026-08-08 on the product's own reporting documentation. 'InfoGenesis POS offers comprehensive back-office reporting based on its transactional databases... POS reports provide detailed views of a profit center's daily activities - sales, labor, and item movement.' The documented catalogue is 122 reports and covers every family the claim names: Labor Summary Report and Clock Activity/Clock Detail (labor vs sales); Product Mix Revenue/Margin/Weight/with Cost/Modifiers (PMIX); Refund Return Void Detail and Summary, Voided Checks, Reopened Checks, Discount Detail/Summary and Anti Fraud Controls (comps/voids audit); Enterprise Revenue Summary, Enterprise Sales Balance, Enterprise Cashier Performance, Enterprise Discount Summary and Enterprise Tender (multi-location comparison). Caveat: Agilysys publishes no plan tiers or pricing at all, so 'entry-level paid plan' cannot be tested literally; what is positively established is that core reporting is not held behind the separate Analyze analytics SKU, which is a cross-product BI platform layered on PMS, POS, spa, golf, retail and events. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/Report%20Generation%20Overview.htm · retrieved 2026-08-08 adversarially verified

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

Shortfall: Agilysys publishes no retention window at all - retention is whatever the operator sets on the purge tasks. The ReportsGuide Scheduling topic enumerates the delivered system tasks, which include 'Purge Business Detail Transactions - Purges transactions from the ig_business database detail tables based on the specified retention period', 'Purge Business Summary Transactions', 'Purge Business Day Tables (Vintage)', 'Purge Calendar Day Tables (vintage)' and 'Purge Audit Logging Track Tables... A value can be specified for the number of days of data to keep'. Transaction-level detail therefore persists until a customer-scheduled purge removes it - no silent truncation and no archive-retrieval fee is documented - but no minimum or default window, and certainly not a stated 24 months, appears in the 122-topic ReportsGuide or anywhere on agilysys.com. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/Scheduling.htm · retrieved 2026-08-08

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

Analyze provides real-time dashboards with instant alerts so managers can respond to performance shifts; operator-configurable thresholds and historical-pattern deviation detection are not documented. https://www.agilysys.com/en/products/analyze/ · retrieved 2026-08-01

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

Analyze lets users 'ask operational questions in plain language and receive instant contextual answers', explicitly eliminating SQL and manual report building. https://www.agilysys.com/en/products/analyze/ · retrieved 2026-08-01

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

Analyze 'Guest 360' combines PMS, POS and loyalty data into unified profiles to understand behavior patterns and lifetime value; new-vs-returning counts and frequency cohorts are not named. https://www.agilysys.com/en/products/analyze/ · retrieved 2026-08-01

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

Analyze provides AI-driven demand forecasting and seasonality projections; daypart/hourly granularity and consumption by scheduling or ordering workflows are not documented. https://www.agilysys.com/en/products/analyze/ · retrieved 2026-08-01

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

Per-employee declared-versus-charged exists: the IRS Tips Report lists Charged Tips/Grats Sales, Declared Cash Tips, Gratuities, Tips Transferred In/Out with the formula 'Tips, Grats and Transfer = Charged Tips + Declared Cash Tips + Gratuities + Tips Transferred In - Tips Transferred Out', plus an IRS Tips/Grats ratio against allocable sales; the IRS Tips and Gratuity report tracks gratuity amounts flowing to the employee's payroll account. Two shortfalls: (1) no tip-pool construct exists, so there is no pool-distribution detail - pooling can only be run as manual employee-to-employee Tip Transfers; (2) the Daily Tax Summary Report shows only aggregate Taxable Sales / Non-taxable Sales / Tax grouped by profit center or terminal, not a tax-liability breakdown by tax type or jurisdiction. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/IRS%20Tips%20Report.htm · 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-wide management across single or multi-property portfolios with centralized governance is documented; a named three-level hierarchy object scoping reporting and permissions is not. https://www.agilysys.com/en/products/loyalty-and-promotions/ · 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

Cloud-hosted portal manages menus, pricing and promotions and deploys updates globally across multiple properties simultaneously; publish/version history showing what was pushed, when and by whom is not documented. https://www.agilysys.com/en/products/infogenesis-pos/ · 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

ConfigGuide, 'Configure Permissions for the Child Enterprise' (POS Configuration > Administration > Enterprise > CCM2 Configuration): the parent enterprise sets, per entity, 'Allow Inherit' ('the child enterprise is allowed to inherit the records configured in the menus mapped to the entity'), 'Allow Override' ('the child enterprise is allowed to override the records inherited from the parent enterprise') and 'Allow New'. Individual records can be locked regardless: 'If an individual record has the View only in Child Enterprise option enabled, it cannot be overridden in the child enterprise even if Allow Override is enabled for an entity', and 'Exclude for Child Enterprise' hides a record entirely. Price is separately controlled in Price Tier Management, where the parent toggles 'Change Price Tier Mapping in Child Enterprise', 'Create New Price Tier Mapping', 'Create New Price Tier' and 'Allow Price Override for Price Tier' ('the child enterprise is allowed to modify the price configured for each price level within a price tier in the Item Price Tier Level and Modifier Price Tier Level menus'), each disabled by default. Corporate can therefore let a location reprice an inherited item while the item record itself stays view-only. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Configure%20Permissions%20for.htm · retrieved 2026-08-08

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

One item record carries a price matrix: the Item Price Tier Level and Modifier Price Tier Level menus price each record against every price level x price tier; Auto Price Level sets the active level by check type, meal period (daypart), GA class, terminal group and tender; Price Tier Schedule switches tiers by date; and CCM2 parent/child enterprise inheritance with the Price Tier Management controls decides which tier mappings each child property uses and whether it may override prices - per location group without duplicating the item. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Auto%20Price%20Level.htm · retrieved 2026-08-03

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: scheduling granularity is a start/end DATE, not a date-and-time, and the docs never state that activation is interpreted in each store's own time zone. ConfigGuide, Schedule Price Change: 'allows the user to schedule a price change for a future date unlike the Price Change utility and optionally to schedule that change to last for a specified date range', with Start Date ('must not be lesser than the current date'), End Date, price level selection, amount or percentage change and rounding. Rollback exists in two forms: an item's 'Previous Price' is retained and a 'Swap to Previous Price' checkbox swaps current and previous prices, and the schedule's End Date returns the price. Menu scheduling exists separately (IGCM 'Date and Week Wise Menu Schedule', DayPart Schedule, Screen Schedule, Price Tier Schedule). Store time zone is configured per store in IGCM (UserGuide 'Store Configured Time Zone': 'The time zone must be configured in the Store menu in IGCM'), and the report/task scheduler carries a Time Zone column, but the price and menu schedules do not document time-zone handling. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Schedule%20Price%20Change.htm · 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

Shortfall: the documented cloning covers menus only, not a whole-store template of taxes, roles, printers, modifiers and tenders, and no time-to-open is published. IGCM 12.3.14 release note 'Copy Global Menu Across Stores': 'IGCM has been enhanced to allow users to copy the global menu created in one store to other stores within the same division. Only division-level items and modifiers from the menu can be copied... This operation is executed as a task, and its status can be viewed in the Task Manager utility.' Beyond that, the Enterprise/Division model means a new store inherits by construction - taxes, tenders, check types, discounts and job codes are defined at enterprise level and items, modifiers and order screens at division level, so 'each level inherits the configuration from the levels above it' - and a CCM2 child enterprise inherits parent records per entity. What is not documented is a store-provisioning template or clone-a-store action, and Agilysys publishes no expected time-to-open anywhere on agilysys.com. https://ig.onagilysys.com/help/POS/IGCM/12.3.14_RN/Copy%20Global%20Menu%20Across%20Stores.htm · retrieved 2026-08-08

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

Shortfall: the docs never model a franchisor/franchisee boundary - there is no ownership, banking or franchise-fee concept, and the child enterprise's separateness is a configuration hierarchy, not a tenancy with its own contract. What is documented: IGCM supports a tenant containing multiple enterprises, and 'Centralized User Role Management with Tenant-Level Permissions' introduces Tenant Permission Group, Tenant Permission Level, Tenant User Role and Tenant Role so 'a role can be created at the tenant level and assigned to the user in all three enterprises', while enterprises created without 'Use Tenant Permissions' keep their own enterprise-level roles ('permanent and cannot be changed after the enterprise is created'). A CCM2 parent enterprise pushes and locks configuration into child enterprises which may be granted 'Allow New' to own records that 'are not centrally available and can be accessed only from the child enterprise', and employees, profit centers, terminals and table layouts are store-level objects. Reporting: 'The reports in the IGCM only display data for a selected store. If an employee has permissions to access stores in several enterprises, they can access different stores in different enterprises. If the user is a member of the System Administration Group... a user can access all stores in all enterprises on this system.' https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Centralized%20User%20Role%20Management.htm · retrieved 2026-08-08

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

Re-evidenced 2026-08-08. Zero of the 1,691 InfoGenesis 12UX documentation topics match 'royalty' or 'franchise'. The enterprise hierarchy that does exist is Customer, Enterprise, Division and Store - used for task scoping and Enterprise-level reports (Enterprise Revenue Summary, Enterprise Sales Balance, Enterprise Tender) - with no fee schedule, royalty basis, or gross-vs-net-of-discounts election. None of Agilysys' 37 product pages is a franchise-management product; the ICP is owned and managed hospitality properties. https://ig.onagilysys.com/help/POS/IG_12UX/Sitemap.xml · retrieved 2026-08-08 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

Re-evidenced 2026-08-08. There is no royalty calculation to collect - zero 'royalty' or 'franchise' topics in the 1,691-topic help set - and no ACH, direct-debit or franchisee-statement topic either. The documented account constructs are guest accounts (GA Account Activity/Balances), gift cards and PMS folio posting, all guest-facing rather than franchisee-facing. https://ig.onagilysys.com/help/POS/IG_12UX/Sitemap.xml · retrieved 2026-08-08 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

Analyze aggregates revenue across properties and revenue centers in one platform; labor, discount and void roll-ups plus store-vs-store ranking and variance flags are not documented. https://www.agilysys.com/en/products/analyze/ · 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: roll-up holds only for division-level items, and the enterprise-level report set contains no item-level report. ConfigGuide, Enterprise/Division Model: items, product classes and modifiers are configured at the division level and shared by every store beneath it, and 'All numeric identifiers for configuration elements (such as item ID, product class ID...) must be unique within the enterprise', so one corporate item ID survives across stores while stores price it differently through price tiers (Item Price Tier Level, store-level price tier). But 'it is possible to create store level items and modifiers that are only accessible to an individual store' - those are separate records with their own IDs and do not roll up - and the six delivered enterprise reports (Enterprise Revenue Summary, Enterprise Sales Balance, Enterprise Tender, Enterprise Discount Summary, Enterprise Refund Return Void Detail, Enterprise Cashier Performance) are all money/tender summaries; every Product Mix report runs at store or division scope. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Enterprise%20Division%20Model.htm · 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

The Gift Card page documents redemption 'across dining, spa, golf, retail, lodging, and online channels' and a guest self-service balance/reload portal — that is cross-OUTLET, not cross-PROPERTY. The only property-level language is 'on or off property' marketing copy. Cross-property redemption across separate legal entities/properties is not affirmatively documented. https://www.agilysys.com/en/products/gift-card/ · retrieved 2026-08-01 adversarially verified

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

Supports enterprise-wide loyalty and promotional program management across single or multi-property portfolios, recognizing spend across rooms, F&B, spa, golf and digital touchpoints. https://www.agilysys.com/en/products/loyalty-and-promotions/ · 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

IG KDS supports 'multiple venues or food court concepts from a single, centralized system' and InfoGenesis runs many outlets per property; separate branding/receipts and separately reportable virtual brands on one drawer are not documented. https://www.agilysys.com/en/products/ig-kds/ · retrieved 2026-08-01

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

Shortfall: taxes are defined at the ENTERPRISE level, not per location, so genuinely different jurisdictional rates require a CCM2 child enterprise override or a separate enterprise rather than a per-store tax setting. ConfigGuide, Tax: 'Taxes are types of taxes used at any time in the system, such as state and local sales taxes, entertainment taxes, value-added taxes (VAT), or general and provincial sales taxes (GST and PST)... The taxes applied to an item are based on the tax group assigned to the item [and] the check type (regular, comp, room service)... For every check type, define which taxes are applied to each tax group', and 'Items are priced with or without tax included' (a full VAT mode with its own report set exists). Tax Category supports simultaneous dual taxes ('Canada has both a GST... and a PST... Tax Categories break out dual taxes on the check'). Exemption is handled by tender and check type: 'Checking Auto Remove Tax automatically removes tax for the value of the tender applied to the check. This is often used for comps and coupons. Tax is also automatically removed by selecting a check type override with a check type that has no tax.' Store Information carries a per-store Tax Identification Number, and country-specific fiscal reporting (Philippines BIR, Thailand, VAT, Quebec) is delivered. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Tax.htm · retrieved 2026-08-08

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: currency is an enterprise-level setting, not a per-location one, and no consolidated reporting-currency conversion is documented. Release note 'Currency based on Enterprise Setting': Terminal Option 1415 makes the terminal 'follow the currency, date, and time format configured in the Currency Customization and Date/Time Customization in the Administrator > Enterprise'; when disabled the terminal follows the OS Language & Region settings. Multi-language is real and per-enterprise: primary and secondary languages are configured for the enterprise with per-menu Translations, receipts print in multiple languages by terminal option, static data prints in the profit center language, and Arabic right-to-left receipt support ships. Foreign currency is handled at tender level only - a Foreign Currency tender (verification code 41-49) converts at a manually configured Currency Rate and 'does not support partial or multiple payments' - and Dynamic Currency Conversion components print on receipts. No report converts multiple stores' takings into a single reporting currency. https://ig.onagilysys.com/help/POS/IG_12UX/ReleaseNotes/Currency%20based%20on%20Enterprise.htm · retrieved 2026-08-08

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

Shortfall: the log is explicitly NOT immutable - the delivered system task 'Purge Audit Logging Track Tables' 'purges data in all databases containing track tables. Track tables are used by the Audit Logging Viewer. A value can be specified for the number of days of data to keep' - and the documented filter set has no location column. ConfigGuide, Audit Logging: 'The Audit Logging utility captures all the inventory, tender and general activities occurring in various forms of IGCM including accessing of the logged activities and the user's sign in or sign off from the IGCM', filterable by Application (IGCM, Generic Authorization), Start Date, End Date, User, Operation ('success, failure or edit') and Type ('the activities based on form'), with Print and 'Exports the generated entries in an excel file format'. Scope follows the IGCM context selection (enterprise/division/store) rather than appearing as a queryable per-location field, and newer functions state audit coverage explicitly (for example 'Audit logging is supported for this functionality' on Copy Global Menu Across Stores). https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Audit%20Logging.htm · 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: no SCIM or any automated deprovisioning, and federation is not self-service - the property exchanges metadata with Agilysys to set it up. ConfigGuide, Single Sign-On (SSO): 'InfoGenesis POS can integrate with any identity provider supported by Microsoft Azure AD B2C... The following integrations are supported: SAML-based Identity Providers - Any provider that supports SAML protocol for authentication; OAuth-based Identity Providers - Any provider that supports OAuth protocol for authentication; Local Account...; Social Media Account'. The OAuth setup lists OIDC Discovery Endpoint, Client ID and Client Secret supplied by the property and Protocol (OpenID Connect), Resource Scopes (Email, profile, openid), Response Type (Code), Response Mode (form_post), Grant Types and Claims Mapping (sub, email, family_name, given_name) supplied by Agilysys; the SAML setup lists Entity ID, secret value/ID, App Federation Metadata URL and givenname/surname/emailaddress/name claims. MFA, reCAPTCHA, password complexity and web session timeout are configurable. Nothing in the topic mentions SCIM, directory sync or automated user deprovisioning. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Single%20Sign%20On%20SSO.htm · 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

Shortfall: no API reference is published and the documented cross-location data is summary-level file output, not transaction-level in one call. The POS API exists but is configured, not documented: ConfigGuide API Registration enables per-enterprise API Clients (Name, Client Type, Terminal, Profile, Employee, Job Code, Device, Duration, Active) and POS API Configuration takes a 'POS API Reload Config URL' and 'POS API Subscription Key'; IGCM now assigns 'unique license keys to individual store instances'. The Azure APIM developer portal at agys-dev.developer.azure-api.net returns an empty value array from both /developer/apis?api-version=2022-04-01-preview and /developer/products, so no operation, schema or authentication scope is visible anonymously. What is documented for cross-location data: the Enterprise Sales Balance Report is 'a consolidated report... for the different stores mapped to an enterprise' and the Enterprise Revenue Summary lists revenue by property, and both can be scheduled to e-mail, file path or SFTP, alongside bulk export tasks (Product Mix Export, Revenue Summary Export, Tender Summary Export, DataWorks Export) - all summary-level, and the export tasks select by time period and profit center rather than returning transaction rows. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/API%20Registration.htm · retrieved 2026-08-08

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

Re-evidenced 2026-08-08, withdrawing the false premise that no labor product exists - InfoGenesis holds employees, job codes, clock data and labor reporting, and scopes configuration by Customer, Enterprise, Division and Store. What is missing is the rules: none of the 747 IGCM Configuration Guide topics defines an overtime threshold, a mandatory break rule, or predictive-scheduling compliance settings, and 'overtime' does not occur anywhere in the 1,691-topic set. The terminal enforces only the clock-in/out options 37, 38 and 215 (slip printing and manager override on open checks). Labor appears after the fact, in the Labor Summary and Clock Detail reports. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Contents.htm · retrieved 2026-08-08 adversarially verified

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

12UX user guide Supported Devices table: iOS - iPad Mini 6th/7th gen; Windows - Touch Dynamic Razor P100. The config guide's Supported Devices table adds the mobile/IG Fly list: iPhone 10X and iPhone XR (iOS), Samsung Note10 Lite, Samsung Xcover Pro, Zebra TC22 (Android). Supported Devices and Mode gives the platform matrix as iOS/iPadOS 26, Android 13/14/15 and Windows, and Supported Devices Information tunes check counts for Samsung tab, iPad mini, Laptop (1280x720) and Desktop (1920x1080). Constraint worth naming: support is a named certified-device list, not any arbitrary tablet. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Supported%20Devices.htm · retrieved 2026-08-06

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

Windows, iOS and Android are named as supported client platforms; minimum OS versions and device specs are not published. https://www.agilysys.com/en/products/infogenesis-pos/ · retrieved 2026-08-01

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

IG Fly is a rugged all-in-one handheld consolidating ordering, payment, check management, printing and scanning; IG Flex is a rugged tablet. No drop rating or IP ingress rating is published for either. https://www.agilysys.com/en/products/ig-fly/ · retrieved 2026-08-01

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

326th: NEW SURFACE - the vendor's own product-resource manifest and the full live PDF library. www.agilysys.com/en/product-resource/ is a closed vendor-published enumeration of 28 current datasheets (identical on /page/2/ and /page/3/: the pager is a client-side filter, so 28 is the whole catalogue; the nonsense path /en/zzz-nonsense-qq/ returns the site 404 at 39,018 B, a different body). All 28 fetched at 200 as application/pdf. Separately the 259 wp-content PDF URLs from the Wayback CDX index were re-fetched WITH redirects: 113 of the dated /uploads/<year>/<month>/ paths 301 to the product-resource landing page (a corpus hole the 325th's no-redirect fetch could not see), 84 are real PDFs at the flat /uploads/<name>.pdf path. Corpus finally held: 117 text-extracted documents, 3,079,354 characters, including the FY23 and FY24 10-Ks, every current product sell sheet, the POS Device Disinfecting and Cleaning Guide, and 20+ customer spotlights. VERDICT: no - both disjuncts fail on a corpus that now includes every handheld sell sheet the vendor publishes (IG Fly, IG Flex, Express Mobile, IG Quick Pay) plus the POS Device Disinfecting and Cleaning Guide, the only hardware-care document Agilysys publishes. Tokenised word-boundary case-insensitive over 3,079,354 characters: 'hot-swap'/'hot swap' 0, 'swappable' 0, 'replaceable' 0, 'mAh' 0, 'charging' 1 (a 10-Q financial phrase). 'batter*' scores 4 across 2 distinct documents: the IG Fly sell sheet's 'engineered to withstand demanding environments with drop resistance and long battery life' - an unquantified adjective, already recorded in the 325th - and, POISON, the Cleaning Guide's 'Remove batteries from items like wireless keyboards', a peripheral-cleaning instruction. This agrees with the prior pass's control over the 5,627-topic help corpus (hot-swap|spare battery|battery life|replaceable battery = 0). No rated shift battery life and no field-replaceable or hot-swap battery is published for any supported handheld. Retrieved 2026-09-18. https://www.agilysys.com/en/product-resource/ · retrieved 2026-09-18 adversarially verified

Handhelds support cellular/LTE connectivity as a documented fallback when store Wi-Fi drops, either built into the device or via a vendor-supplied failover.

hardware-handheld-lte

IG Fly includes cellular backup connectivity so transactions continue when Wi-Fi drops. https://www.agilysys.com/en/products/ig-fly/ · retrieved 2026-08-01

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

Offline transaction mode is documented for IG Flex and enterprise-grade offline resiliency for InfoGenesis, but the vendor publishes no explicit list of which functions degrade offline. https://www.agilysys.com/en/products/ig-flex/ · retrieved 2026-08-01

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

IG KDS is a first-party kitchen display product with station routing, master/prep views and bump updates, fully integrated with InfoGenesis POS. https://www.agilysys.com/en/products/ig-kds/ · 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

Two first-party kiosk SKUs (IG Kiosk and IG PanOptic grab-and-go AI kiosk) share the POS menu engine and take payment via Agilysys Pay P2PE; countertop-vs-freestanding form factors and ADA compliance are not documented. https://www.agilysys.com/en/products/ig-kiosk/ · retrieved 2026-08-01

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

Re-evidenced 2026-08-08. IG Digital Menu Boards is real and documented - it has its own user guide and release notes in the InfoGenesis Help Center - but it is an in-venue display product. Zero of the 1,691 documentation topics match 'drive', and none concerns an outdoor lane display, order confirmation display, speaker or headset integration, or a speed-of-service timer. The hardware partners named in Agilysys' Solution Partners directory are PAR, Aures, Epson, Toshiba and Touch Dynamic - terminal and peripheral makers, no drive-thru lane vendor. https://ig.onagilysys.com/help/POS/IG_12UX/Sitemap.xml · retrieved 2026-08-08 adversarially verified

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

Same bad citation — the help landing page says nothing about printers. USB/Wi-Fi/Bluetooth receipt printing is stated verbatim in the Agilysys NV, LLC App Store listing ('Print sales receipts by connecting your device to a receipt printer via USB, Wi-Fi or Bluetooth'). Still no ESC/POS model compatibility list, so partial is right. https://apps.apple.com/us/app/infogenesis-pos-terminal/id1534574604 · retrieved 2026-08-01 adversarially verified

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

IG Flex documents convertibility with cash drawers, scales, scanners, stands and charging docks; Eatec supports UPC/SKU scanning. No published compatibility list of specific models. https://www.agilysys.com/en/products/ig-flex/ · 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

Card entry occurs on PCI-validated P2PE devices including secure Bluetooth payment devices on IG Flex, but Agilysys never states the resulting merchant SAQ type. https://www.agilysys.com/en/products/pay/ · retrieved 2026-08-01

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

InfoGenesis UserGuide, 'Apple Tap to Pay on iPhone' (also a 12.3.15 release note): 'InfoGenesis POS supports Apple Tap to Pay functionality on iPhone, enabling contactless card payments directly on supported iPhone devices.' Parameters table: Supported Gateways Adyen and Tyro; Supported Region United States; Supported iPhone Model iPhone 14 and above; Connectivity Wi-Fi; Card Types 'NFC mode only: Visa, Mastercard, American Express, Discover'. No external reader is involved - 'IG POS application and Agilysys Pay Adyen iOS app must be installed on the same iPhone' - and Terminal Option 1465 (Use Pay Centralized Configuration) must be enabled. Documented limits: five consecutive tap attempts per transaction, a 40-second timeout prompt, and Terminal Options 1268 and 477 unsupported. No Tap to Pay on Android equivalent is documented. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Apple%20Tap%20to%20Pay%20on%20iPhone.htm · retrieved 2026-08-08

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

hardware-pricing-transparency

No hardware SKU prices are published anywhere on agilysys.com; every hardware page routes to a sales contact. https://www.agilysys.com/en/products/ig-flex/ · retrieved 2026-08-01

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

Agilysys US Sales Terms and Conditions, section 4.2: 'Title to Equipment (excluding third party software) will pass to Customer at the time of delivery.' Section 6.1 confirms the sale model: 'Agilysys warrants that, at the time the Equipment... is shipped, Agilysys will be the lawful owner of the Equipment... free and clear of any liens and encumbrances... and will have full right, power and authority to sell the same to Customer.' Equipment is sold outright, not leased or rented; Agilysys takes only a purchase-money security interest in the Equipment until paid, and section 4.6 has the customer accept third-party manufacturer EULAs for 'Equipment resold by Agilysys to Customer'. No lease or subscription-bundled rental option appears in the terms. https://www.agilysys.com/en/terms-and-conditions/ · retrieved 2026-08-08

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

Shortfall: the terms confirm hardware ownership but say nothing about running other software on it, and they document a software kill switch. Title passes to the customer at delivery (section 4.2), so the device is the customer's property after cancellation. But the licence is tied: section 2.1 grants a licence 'to use the Software specified in the Agreement with the Equipment specified in the Agreement or other equipment which Agilysys has certified as compatible with the Software', 'Upon termination of any Software license granted under the Agreement, Customer's rights to use the Software cease', and 'Software licensed under the Agreement may incorporate an electronic repossession device which Agilysys can, and will, activate in the event that Customer does not pay, in full... Customer understands that the electronic repossession device will prevent the Software from operating.' The repossession device is documented as disabling the Software, not the Equipment, and no Agilysys page addresses whether a purchased terminal can be re-imaged for another vendor's POS. https://www.agilysys.com/en/terms-and-conditions/ · retrieved 2026-08-08

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

Agilysys' own published sales terms are the enumeration and they decline both halves of this claim. Section 6.1 Equipment Warranty: 'Equipment is subject to any warranties provided by the manufacturers/licensors of such Equipment to end users thereof... Agilysys makes no other warranty of any kind with regard to the Equipment' - so no Agilysys warranty term is published, only a pass-through to the manufacturer. Section 4.5 Returns is the entire return procedure and contains no exchange or turnaround commitment: 'Customer may return Equipment only with Agilysys' prior consent... Customer shall return Equipment freight prepaid, in accordance with Agilysys' instructions in original packaging and in good condition, without alteration. Customer assumes risk of loss for returned Equipment until receipt by Agilysys... Customer agrees to accept a credit memo in the amount of the value of the returned Equipment', usable against future purchases for one year. The customer-support page publishes software support channels (MyAgilysys case portal, e-mail, regional phone, 24x7 for critical and standard issues) and no hardware RMA or depot-swap SLA. https://www.agilysys.com/en/terms-and-conditions/ · 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

Checked the supported-device statements in both relevant help systems: IG_12UX UserGuide 'Supported Devices' lists iPad Mini 6th/7th gen (iOS), Touch Dynamic Razor and P100 (Windows), and 'Supported Devices and Mode' lists iOS/iPadOS 26, Android 13-15 and Windows; IG Fly's 'Supported Devices and Gateways' gives a gateway-to-device matrix that is entirely gateway-supplied payment terminals (PAX A800/M8/A920 Pro/A77, Castles S1F2/S1F4 Pro, ELO M60) with the app installed 'from the gateway app store or portal'. Device activation is licence-bound - UserGuide 'Manage Devices': 'manage devices associated with the registered license at the POS terminal... view and deactivate a device from another terminal... to utilize the license in a new device', visible only at security level 7 or higher - and each store carries an Authentication Code that must be entered when a terminal is installed. No topic in 5,336 InfoGenesis topics addresses personally-owned devices, and no BYOD permission or security model (MDM enrolment, containerisation, personal-device policy) is published. The device lists are framed per gateway and per enhancement rather than as a closed statement of what may not be used, so this is unresolved rather than a documented prohibition. || 319th: VERDICT: unknown (unchanged). NEW SURFACE 2026-09-16: compassintakeform.onagilysys.com (Compass Group implementation form) lists 'iPad (Hardware not supplied by Agilysys)' and 'IG Fly (Hardware Not Supplied by Agilysys)' as terminal options - customer-sourced OPERATOR hardware, not staff-owned phones, and no permission/security model. Help-corpus control over 5,627 topics: own device|personal phone/device|bring your own|employee-owned = 5 topics, all POISON (employee-owned CHECKS; OnDemand Communal Cart guests' 'own devices'; Fly handles payment 'on its own device'). Unknown (unchanged). Retrieved 2026-09-16. || 326th: 326th: the vendor's complete published collateral is now censused and does not address device ownership either. Over the 117-document / 3,079,354-character live PDF library (the 28-sheet /en/product-resource/ manifest plus 84 flat-path wp-content PDFs) and the FY2026 10-K: 'BYOD' 0 and 'personal device' 0 in every product document. POISON worth recording because it reads like a hit: 'own device' scores 11 across 8 documents and EVERY occurrence is a GUEST device - Agilysys Authorize ('Guests easily complete authorizations on their own devices'), IG OnDemand, IG Quick Pay, and the Kewadin spotlight ('IG OnDemand allows guests to place and pay for orders using their own device - phone, tablet, laptop'); the FY23/FY24 10-Ks add 'a personal mobile device such as a smart phone or tablet' for Express Mobile guest check-in. No staff-BYOD permission or security model exists in any Agilysys document. Retrieved 2026-09-18. || 327th: 327th: the vendor's own website is now censused too and is silent on device ownership. Over the FIRST body-level census of www.agilysys.com's HTML pages (prior passes read only ~9 legal pages plus the 117-document PDF library): the publisher's own page manifest https://www.agilysys.com/en/wp-sitemap-posts-page-1.xml lists 117 pages and all 117 were fetched at HTTP 200 (1,846,153 characters of stripped text); the nonsense control https://www.agilysys.com/en/zzz-nope-control-qq/ returns 404. (The WP REST API still withholds wp/v2 - /en/wp-json/ lists 68 routes in 10 namespaces, and wp/v2/types, wp/v2/media and wp/v2/solution_partner all 404 with rest_no_route, re-confirmed today.) tokenised: 'BYOD' 0, 'personal device' 0, 'personally owned' 0, 'own phone' 0. That closes the last first-party surface (help system, PDF library, 10-K and now the site) without an ownership statement. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE - the App Store listing of the staff app itself. 'InfoGenesis POS Terminal' (id 1534574604, com.agilysys.igpos, version 12.3.16, 2026-09-09) is distributed publicly on the US App Store with supportedDevices covering iPhone as well as iPad (minimum iOS 13.0), and its description names a permission model: 'Allow Employees' to clock-in and clock-out - Provide access permissions based on job code'. That makes installation on a phone technically possible, but nothing in the listing (or across all 22 apps of publisher 712501910: 'BYOD' 0, 'own device' 0, 'personal device' 1 and it is My Hotel Key ('unlock your hotel room door using your own personal device'), a GUEST room-key app - POISON) says staff may use their OWN phones or states a personal-device security model; the help corpus binds each device to a registered licence and lists iPad Mini as the supported iOS device. Unknown. Retrieved 2026-09-18. || 334th: NEW SURFACE (334th): the Agilysys Knowledge Center's InfoGenesis training courses are Supademo interactive walkthroughs of the live product, never opened by a prior pass (prior passes read only the course TITLES on /en/knowledge-center/). The three InfoGenesis course pages (https://www.agilysys.com/en/knowledge-center-videos/?course=<base64 title>: Back of House for Menu, Inventory and Admin Setup; Front of House for Ordering, Payments and Guest Service; Reporting) link 318 distinct demos, and all 318 were fetched anonymously at HTTP 200 from app.supademo.com/demo/<id>; each page embeds its full step list (narration 'audioText', on-screen callouts, screenshots) in the Next.js flight payload: 17,548 text fields, 780,574 characters, 7,219 screenshots. Vendor-authored tutorials walking the actual IGCM / POS terminal UI (grade B as documentation of what they show; a training set, not a census of the product). Tokenised over all 318: 'BYOD' 0, 'own/personal device|phone' 0; 'mobile' hits are the guest's mobile number on delivery details and receipt notifications, and a 'mobile' screen-layout preview. The Android Agilysys Member App (com.agilysys.memberapp 26.1.4, unpacked) is a GUEST/member app, not a staff ordering app. 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

Shortfall: no staged or phased rollout control, and updates land only when someone restarts the app at the device. UserGuide, System Management Utility (SMU): 'allows the user to send commands from the back office to terminals and kitchen printers' - Go Online, Go Offline ('the terminal status indicator turns to amber and not red'), Reload Config ('Loads terminals with new or updated configuration changes made in IGCM'), Clear Dispatcher Connection, 86/Un86, and 'Reboot/Launch Application'. All of these are also schedulable as SMU tasks (SMU Reboot Terminal, SMU Lock/Unlock Terminal, SMU Go Online/Offline, SMU Reload Terminal Config, SMU Reload Kitchen Printer Service, SMU Reset X and Z Terminal Reports) against a store. Version visibility shipped in IGCM 12.3.11: 'A new column, Version, has been added to the Terminal submenu under System Management Utility menu (Utilities > System Management Utility > Terminals). The base version is displayed under the Version column. Users can view the detailed package information by selecting the Info icon next to the release profile', covering terminals and kiosks. Updates: the PAX Pay@Table app 'checks for updates every 15 minutes and downloads the updates automatically', then prompts 'Updates are downloaded Restart application to apply updates', deferrable by the user and blocked while a check is open. Kitchen printers and KDS appear as Device records but no online/offline dashboard for them is documented, and there is no ring/cohort rollout mechanism. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/System%20Management%20Utility.htm · retrieved 2026-08-08

Integrates with specialty beverage hardware — self-pour tap walls, flow meters, or liquor pour spouts — such that pours post to a POS tab automatically.

hardware-selfpour-scales

Overturns a title-only zero: the IG_12UX and IG Fly ConfigGuide Peripherals form documents a BAR GUN peripheral alongside receipt printer, customer display, cash drawer, coin dispenser, scale, scanner and the AssaAbloy RFID key-card interface. Its fields are Bar Gun Port, Baud Rate, a Timeout ('The maximum time allowed in milliseconds for the POS terminal to get a response from the bar gun', default 3000) and a Data Format whose options are '1Byte', 'Berg Basic (formerly 5Byte)' and 'Samsung 650' - Berg being a liquor-dispensing control system. Pour state is tracked against the order: the Item Display System is 'a system where multiple orders appear on the Item Display screen, and the bar gun is used to pour any displayed drink items and bump off the orders as they are completed', with a 'Only allow bump after all bar gun items are poured' option and undispensed drinks shown in green - 'The order is not completed until all such items are red, indicating they are fully poured.' SHORTFALL: this is an order-first dispensing-gun interface - the check is rung and the gun then reports completion - not the pour-first posting the claim describes, and no self-pour tap wall, flow meter or pour-spout vendor is named anywhere in the entire 8,068-document estate. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Peripherals.htm · retrieved 2026-09-12 adversarially verified

Supports inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call.

hardware-callerid-integration

326th: NEW SURFACE - the vendor's own product-resource manifest and the full live PDF library. www.agilysys.com/en/product-resource/ is a closed vendor-published enumeration of 28 current datasheets (identical on /page/2/ and /page/3/: the pager is a client-side filter, so 28 is the whole catalogue; the nonsense path /en/zzz-nonsense-qq/ returns the site 404 at 39,018 B, a different body). All 28 fetched at 200 as application/pdf. Separately the 259 wp-content PDF URLs from the Wayback CDX index were re-fetched WITH redirects: 113 of the dated /uploads/<year>/<month>/ paths 301 to the product-resource landing page (a corpus hole the 325th's no-redirect fetch could not see), 84 are real PDFs at the flat /uploads/<name>.pdf path. Corpus finally held: 117 text-extracted documents, 3,079,354 characters, including the FY23 and FY24 10-Ks, every current product sell sheet, the POS Device Disinfecting and Cleaning Guide, and 20+ customer spotlights. VERDICT: no. Over this 117-document corpus, tokenised word-boundary case-insensitive: 'caller id' 0, 'PBX' 0, 'CTI' 0, 'screen pop' 0, 'phone order' 0, 'incoming call' 0, 'inbound call' 0, 'dial' 0. That is the collateral half of the denominator; the documentation half was measured in a prior pass - all 5,336 InfoGenesis topic titles and paths across IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB and IGCM plus the 1,448-topic Eatec help system - and returned no caller ID, telephony, phone-order, PBX, call or screen-pop topic. Two independent bounded corpora, neither containing the feature. POISON, named so it is not re-mined: (1) 'telephone' scores 38 and 'telephon*' 44 and EVERY hit is SEC boilerplate (Registrant's telephone number, including area code) or an Agilysys sales number in a document footer; (2) 'phone' scores 35 and every product-context hit is a GUEST's own smartphone running IG OnDemand / IG Smart Menu / Express Mobile, or a contact number; (3) 'call center' scores 1, and it matters - the Q1 FY25 investor deck's Hospitality Experience Cloud appendix lists 'Call Center' as an experience enhancer of the LODGING (PMS) ecosystem, beside Service Task Optimization and Digital Authorizations, while the F&B/POS ecosystem column does not contain it. That is a reservations call-centre module on the PMS side, not a POS caller-ID screen pop. Retrieved 2026-09-18. https://www.agilysys.com/en/product-resource/ · retrieved 2026-09-18 adversarially verified

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

extensibility-public-api-docs

The Agilysys developer portal is a sign-in wall; no API reference is readable without credentials. End-user product docs at ig.onagilysys.com are public, but those are not API documentation. https://agys-dev.developer.azure-api.net/ · retrieved 2026-08-01

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

extensibility-api-access-cost

VERDICT: unknown (unchanged). NEW SURFACE 2026-09-16: certificate-transparency census (crt.sh %.agilysys.com, %.onagilysys.com, %.rguest.com; certspotter rate-limited) = 1,972 distinct hostnames. Probed 211 IG/POS/API/loyalty/docs-named hosts at /, /swagger, /swagger/index.html, /swagger/v1/swagger.json, /api-docs, /openapi.json, /docs, /robots.txt plus a nonsense-path control, and the root of the other 1,761 (1,451 NXDOMAIN/unreachable). Result: no anonymous IG POS API spec. ig-integrationapi-prod-01/-sales, ig-posv3extint-prod-01-*, ig-usdef-integrationapi-*, igsaas, ig-config/cook/realtime/reports-prod-* all 403 'Web App - Unavailable' (a refusal, not an absence); ig-posv3-sales.onagilysys.com, ig-pos-qa.rguest.com, ig-auth-sales and ig-api-devopstraining serve /swagger/index.html as a 1,817-byte 'Authentication Gateway' ('Unauthorised Access!!' / Retry Login) - login-gated, not read further; /swagger/v1/swagger.json 404 on all. core-loyalty-*, v1-documentation-*, pay-swaggerui-*, integrationapiprod, igpos, igposweb: NXDOMAIN. The only anonymous Swagger found is pay-gateway-sales.onagilysys.com/help ('My Swagger UI', RGuest Pay payment gateway, not the POS API). No product tier or pricing surfaced. Unknown (unchanged). Retrieved 2026-09-16. || 323rd: 323rd: NEW SURFACE - Agilysys does run an Azure API Management developer portal, and it publishes nothing to an anonymous visitor. The Wayback lead recorded last pass ('agys-dev.developer.azure-api.net has one capture (301, 2024-05-24)') is LIVE today, not retired: / returns 200 with 5,822 B of real portal HTML, /apis 200/4,904 B and /products 200/4,824 B, against a nonsense path that returns the portal's own 404 page at 200/4,374 B - three distinct bodies, so this is not a catch-all. Its data API answers anonymously and is a live listing rather than a document: GET /developer/apis?api-version=2022-04-01-preview (the only api-version the host accepts; all others are rejected with MissingOrIncorrectVersionParameter, which is how the supported version was learned) returns exactly {"value":[],"nextLink":null}, and /developer/products the same. Zero APIs and zero products are published to the unauthenticated developer role. agys-prod.developer.azure-api.net answers 200 with the 514-byte unconfigured APIM default page ('This is a home page of the Developer portal - an automatically generated, fully customizable website for publishing your API documentation'). An empty anonymous listing is a gate, not an enumeration of Agilysys's APIs, so it cannot carry a no on fees; it does show that no price, tier or free-access statement is reachable through the vendor's own developer portal. Still unknown. Retrieved 2026-09-17. || 326th: 326th: a measurement that bears on all six extensibility cells at once. The vendor's complete published product collateral - 117 documents, 3,079,354 characters, being the closed 28-datasheet manifest at www.agilysys.com/en/product-resource/ plus the 84 live flat-path /en/wp-content/uploads/*.pdf documents - contains the token 'API' ZERO times (word-boundary, case-insensitive), with 'webhook' 0, 'sandbox' 0, 'free trial' 0, 'changelog' 0, 'deprecat*' 0 and 'developer' 7 (all in the FY23/FY24 10-K workforce discussion, the Book4Time SLA and a 2018 trade magazine: POISON). The FY2026 10-K scores 'API' 0 and 'APIs' 2, both positioning lines with no access, fee or tier statement. So Agilysys publishes no API price, tier, fee or free-access statement in any of its own collateral - a second bounded corpus agreeing with the empty anonymous APIM developer-portal listing recorded in the 323rd. Still unknown: silence about a fee is not a statement that access is included. Retrieved 2026-09-18. || 327th: 327th: NEW SURFACE - Agilysys DOES publish API commercial terms, for exactly one product, and it is not the POS. The Book4Time API Terms of Use (www.agilysys.com/en/book4time-api-terms-of-use/, an Agilysys-hosted legal page, 21,622 characters) is a 15-section agreement whose section 07 API Call Limitations reads verbatim: 'The API call limitations are as follows: 1000 per day per Customer property location / 5000 per initial Customer property location ... In no event will unused API calls roll over to the next day or month, as applicable. API call overages will be billed quarterly in arrears for each additional 1000 daily API calls required.' That is a metered, per-location, billable API - the shape this claim asks about - but it governs Book4Time, the acquired spa product, so per the standing merge rule (a sibling product does not bound the POS) it cannot score InfoGenesis. It does sharpen the gap: Agilysys knows how to publish API terms and publishes none for InfoGenesis POS. BOUND: over the FIRST body-level census of www.agilysys.com's HTML pages (prior passes read only ~9 legal pages plus the 117-document PDF library): the publisher's own page manifest https://www.agilysys.com/en/wp-sitemap-posts-page-1.xml lists 117 pages and all 117 were fetched at HTTP 200 (1,846,153 characters of stripped text); the nonsense control https://www.agilysys.com/en/zzz-nope-control-qq/ returns 404. (The WP REST API still withholds wp/v2 - /en/wp-json/ lists 68 routes in 10 namespaces, and wp/v2/types, wp/v2/media and wp/v2/solution_partner all 404 with rest_no_route, re-confirmed today.) the token 'API' scores 99 hits in 8 of 117 pages and 78 of those are this one Book4Time page; the rest are Book4Time service agreement 8, Book4Time integrations 6, PMS 3, and ONE passing mention each on infogenesis-pos, who-we-serve/restaurants and our-locations. 'webhook' 0, 'sandbox' 0, 'free trial' 0, 'REST' 2 (careers boilerplate + privacy policy: POISON). No fee, tier or included-access statement exists for the InfoGenesis API anywhere on the vendor's own site. Retrieved 2026-09-18. || 328th: MERGE HOLD (proposed no/B, held unknown): The release note documents a per-store POS API licence KEY, not a fee or plan tier; a licence key can be issued at no charge. No published price or order-form line shows API access costs extra. The agent named this its weakest move. PROPOSAL AS WRITTEN: 328th: MOVED unknown -> no on a body-level re-grep of the InfoGenesis help corpus (.cache/q316/agilysys/corpus.json, 5,627 topic bodies, 10,620,922 characters) that no prior pass on this cell had run - every prior note searched hosts, PDFs and the marketing site, never the help bodies. The IG POS API is a SEPARATELY LICENSED entitlement, keyed per store instance. IGCM release note 'Move POS API Client License Key from API Registration to API Client', verbatim: 'InfoGenesis has been enhanced to allow customers to assign unique license keys to individual store instances, enabling flexible license control across different stores. This feature is targeted only for customers using IG POS APIs... The License Key field has been relocated from the API Registration submenu to the API Client submenu in the Enterprise menu... Additionally, this update eliminates the need for a separate POS API license configuration for Nexus, IG Fly and IG OnDemand 12.x.' Corroborating topics: /IG_12UX/ConfigGuide/API Registration.htm ('Enable the API Registration checkbox to configure the API Registration and API Client sub-menus'), /IG_Fly/ConfigGuide/API Client.htm (per-client Token, Duration, and a 'Full Service' switch - 'If this option is enabled, it means that the instance is allowed to access the Full Service APIs'), /IG_12UX/ConfigGuide/Virtual Device Registration.htm ('used to create a device for the IGPOS API client. A separate device must be created for each client'), and /IG_12UX/ConfigGuide/CCM2 Features.htm (API Registration is not inherited by a cloned child enterprise). So API access is an enterprise-level entitlement that must be enabled, is licensed with keys obtained from Agilysys, and is licensed PER STORE INSTANCE - the per-location upgraded-entitlement shape this claim asks about - not something included by default with the base subscription. WEAKNESS STATED HONESTLY: Agilysys publishes no price for that licence (the vendor's whole published corpus - 117 PDFs/3,079,354 chars and 117 site pages/1,846,153 chars - scores 'API' in only 8 pages, 78 of those hits in the Book4Time spa-product API Terms of Use), so the verdict rests on a documented per-instance licence gate rather than on a published fee. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE (332nd): SwaggerHub, never checked for this vendor. Agilysys's own SwaggerHub organisations list anonymously: https://api.swaggerhub.com/apis/Agilysys-Inc = 13 APIs (PMS - Reservations and Profiles, PMS - Account Look-up and Charge Posting, PMS - Condo & Residence Management, StayConnect ARI / Config / Groups / Reservations & Profiles (published, modified 2026-08-28..09-03), PMS - Express Check-In and Check-Out, PMS - Booking Engine, PMS - Additional Inbound / Outbound APIs, PMS - Availability, Rates and Inventory) and https://api.swaggerhub.com/apis/Agilysys_STAY = 3 (Rbook, Stay OpenAPI Inbound/Outbound snapshots); a public-registry search for 'infogenesis' returns 4 unrelated specs (0 Agilysys). So Agilysys publishes 16 API definitions and ALL are the Stay PMS family (the 'Charge Posting' spec is the PMS side a POS posts to); ZERO InfoGenesis POS APIs are published there. That is a census of what Agilysys chose to publish on SwaggerHub, not of the IG POS API (which exists: Import Services, ConfigurationMetadata export, IG POS API clients, per the help corpus), and a sibling product's specs cannot score the POS. Also new (third party, grade D): Avero's KB article 'Infogenesis API' (averoinc.zendesk.com, read via /api/v2/help_center/en-us/articles/15669431063827.json, updated 2026-07-17): 'InfoGenesis API is supported for Sales data only ... Agilisys provides Avero access to your businesses API to collect your sales data'; cloud IG needs only the store's TWS credentials and a base URL ('Base URL for v12 will be https://{{URL}}/bridge/1/ias-api/v2/{{siteId}}/{{adapterName}}'), while on-premise IG 'requires your team to work with Agilysys to setup API access'. No fee, licence price or tier is stated. Neither surface states a fee or an inclusion for InfoGenesis API access; the 328th hold (a licence key is not a fee) still governs. Retrieved 2026-09-18. || 334th: 334th: NEW SURFACE - the HTNG API Registry entry 'Agilysys API' (https://apiregistry.htng.org/api/agilysys~agilysys-api; live host 502 today, read from its Wayback capture 2021-12-06, 200). Its only substantive text: 'Agilysys integration partners share a commitment to customer service and a focus on interoperability. Integration partners self-certify products against Agilysys APIs or HTNG standards. A certification logo will be issued upon successful completion of testing.' Documentation URL, endpoint and architecture are all 'Not Provided'. No fee, tier or inclusion statement - a partner-certification framing, not a price. Also: 'API' 0 across the 318 InfoGenesis Knowledge Center Supademo walkthroughs (operator training does not touch API licensing). 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

The SCORE survives — nothing about referral fees, revenue share or per-location partner fees appears on the Solution Partners page. But the supporting note is not on that page: I found no self-certification language, no HTNG reference, no certification-logo program, and could not confirm the 80+/24-category counts. Treat the note as unsourced narrative even though the verdict stands. https://www.agilysys.com/en/solution-partners/ · retrieved 2026-08-01 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

VERDICT: unknown (unchanged). NEW SURFACE 2026-09-16: certificate-transparency census (crt.sh %.agilysys.com, %.onagilysys.com, %.rguest.com; certspotter rate-limited) = 1,972 distinct hostnames. Probed 211 IG/POS/API/loyalty/docs-named hosts at /, /swagger, /swagger/index.html, /swagger/v1/swagger.json, /api-docs, /openapi.json, /docs, /robots.txt plus a nonsense-path control, and the root of the other 1,761 (1,451 NXDOMAIN/unreachable). Result: no anonymous IG POS API spec. ig-integrationapi-prod-01/-sales, ig-posv3extint-prod-01-*, ig-usdef-integrationapi-*, igsaas, ig-config/cook/realtime/reports-prod-* all 403 'Web App - Unavailable' (a refusal, not an absence); ig-posv3-sales.onagilysys.com, ig-pos-qa.rguest.com, ig-auth-sales and ig-api-devopstraining serve /swagger/index.html as a 1,817-byte 'Authentication Gateway' ('Unauthorised Access!!' / Retry Login) - login-gated, not read further; /swagger/v1/swagger.json 404 on all. core-loyalty-*, v1-documentation-*, pay-swaggerui-*, integrationapiprod, igpos, igposweb: NXDOMAIN. The only anonymous Swagger found is pay-gateway-sales.onagilysys.com/help ('My Swagger UI', RGuest Pay payment gateway, not the POS API). '-sales' and '-devopstraining' IG environments exist (ig-posv3-sales, ig-auth-sales, ig-config-sales, ig-api-devopstraining) but every one is Azure AD / auth-gateway gated or 403; nothing offers developer self-signup. Unknown (unchanged). Retrieved 2026-09-16. || 323rd: 323rd: NEW SURFACE - the Agilysys customer community, agilysys.my.site.com, is a Salesforce Experience Cloud site that serves no anonymous knowledge and no self-service signup. / redirects to /s/login (a 1,332-byte redirect shell with no Aura context); the LOGIN shell does carry a usable context (410,892 B; fwuid+loaded extracted with scripts/lib/aura.mjs), and the guest Aura POST to /s/sfsites/aura works (HTTP 200, real action envelopes), but getObjectInfo comes back state ERROR 'You don't have access to this record. Ask your administrator for help or to request access.' for Knowledge__kav, How_To__kav AND FAQ__kav alike - all three tenant shapes seen on other vendors. support./community./help.agilysys.com are NXDOMAIN. So the route works and the data does not: login-gated, a refusal rather than an absence. Read with the empty anonymous APIM developer-portal listing recorded at extensibility-api-access-cost, there is no reachable free sandbox or trial credential without a contract. Still unknown. Retrieved 2026-09-17. || 326th: 326th: new corpus, same answer. 'sandbox' = 0 and 'free trial' = 0 across the vendor's complete published collateral (117 documents, 3,079,354 characters: the closed 28-datasheet /en/product-resource/ manifest plus the 84 live flat-path wp-content PDFs), and 'trial' = 3, all three in a 10-Q litigation paragraph (POISON). No self-signup or developer-trial offer appears in any Agilysys document. That is an absence in collateral, not an enumeration of developer programs, so it cannot carry a no on top of the login-gated community and the empty APIM developer portal already recorded. Retrieved 2026-09-18. || 327th: 327th: NEW SURFACE, and the nearest thing Agilysys publishes to a developer programme still offers no sandbox. The Book4Time API Terms of Use (the vendor's only public API agreement; spa product, not the POS) grants 'a revocable, limited, non-exclusive, non-sublicensable, non-transferable license to access and use the API solely for the purpose of developing, testing, displaying, and distributing your Application' - a licence to test against the live service, with no test environment, no seeded data and no self-signup named anywhere in its 15 sections; access is issued as credentials to an existing 'Customer' or 'Authorized Third Party'. BOUND: 'sandbox' 0 and 'free trial' 0 across the FIRST body-level census of www.agilysys.com's HTML pages (prior passes read only ~9 legal pages plus the 117-document PDF library): the publisher's own page manifest https://www.agilysys.com/en/wp-sitemap-posts-page-1.xml lists 117 pages and all 117 were fetched at HTTP 200 (1,846,153 characters of stripped text); the nonsense control https://www.agilysys.com/en/zzz-nope-control-qq/ returns 404. (The WP REST API still withholds wp/v2 - /en/wp-json/ lists 68 routes in 10 namespaces, and wp/v2/types, wp/v2/media and wp/v2/solution_partner all 404 with rest_no_route, re-confirmed today.) Retrieved 2026-09-18. || 331st: 331st: the one APIM host the help corpus itself names (IG_Fly/ConfigGuide/SaaS.htm: 'https://ig-api-management-devint.azure-api.net/casv2') has a developer portal, https://ig-api-management-devint.developer.azure-api.net/ ('Home - Agilysys API Management - Developer Portal', 200, 5,823 B; nonsense path returns the portal 404 page at 404/4,374 B). Its anonymous listing /developer/apis?api-version=2022-04-01-preview returns ONE api, 'Echo API' (path 'echo'), and /developer/products returns 'Starter' ('5 calls/minute up to a maximum of 100 calls/week') and 'Unlimited' ('Administrator approval is required'). POISON, named so it is not read as a free tier: all three are Azure API Management's out-of-the-box sample content created with every new APIM instance, not Agilysys products, and 'devint' is a development-integration environment, not a developer programme; the gateway root serves only an 'IG' app-selector SPA. No seeded test environment or self-serve developer access for the IG POS API is offered on it. Also: 'sandbox' 0 and 'test environment' 0 over the 5,627 help-topic bodies (Training Mode exists, a terminal feature for staff, not a developer sandbox). Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE (332nd): SwaggerHub, never checked for this vendor. Agilysys's own SwaggerHub organisations list anonymously: https://api.swaggerhub.com/apis/Agilysys-Inc = 13 APIs (PMS - Reservations and Profiles, PMS - Account Look-up and Charge Posting, PMS - Condo & Residence Management, StayConnect ARI / Config / Groups / Reservations & Profiles (published, modified 2026-08-28..09-03), PMS - Express Check-In and Check-Out, PMS - Booking Engine, PMS - Additional Inbound / Outbound APIs, PMS - Availability, Rates and Inventory) and https://api.swaggerhub.com/apis/Agilysys_STAY = 3 (Rbook, Stay OpenAPI Inbound/Outbound snapshots); a public-registry search for 'infogenesis' returns 4 unrelated specs (0 Agilysys). So Agilysys publishes 16 API definitions and ALL are the Stay PMS family (the 'Charge Posting' spec is the PMS side a POS posts to); ZERO InfoGenesis POS APIs are published there. That is a census of what Agilysys chose to publish on SwaggerHub, not of the IG POS API (which exists: Import Services, ConfigurationMetadata export, IG POS API clients, per the help corpus), and a sibling product's specs cannot score the POS. None of the 16 is an InfoGenesis spec, so no IG sandbox or seeded test environment is offered there (SwaggerHub's own virtserver auto-mock is a platform feature, not an Agilysys sandbox). Also new (third party, grade D): Avero's KB article 'Infogenesis API' (averoinc.zendesk.com, read via /api/v2/help_center/en-us/articles/15669431063827.json, updated 2026-07-17): 'InfoGenesis API is supported for Sales data only ... Agilisys provides Avero access to your businesses API to collect your sales data'; cloud IG needs only the store's TWS credentials and a base URL ('Base URL for v12 will be https://{{URL}}/bridge/1/ias-api/v2/{{siteId}}/{{adapterName}}'), while on-premise IG 'requires your team to work with Agilysys to setup API access'. No fee, licence price or tier is stated. The Avero integration uses the customer's production TWS credentials; no developer test tenant is mentioned. Retrieved 2026-09-18. || 334th: 334th: NEW SURFACE - the HTNG API Registry entry 'Agilysys API' (Wayback capture 2021-12-06; the live registry answers 502) says partners 'self-certify products against Agilysys APIs or HTNG standards. A certification logo will be issued upon successful completion of testing', with documentation URL and endpoint 'Not Provided': testing is mentioned, but no sandbox, test tenant or seeded data is offered or linked. 'sandbox' 0 over the 318 InfoGenesis Supademo walkthroughs on the Knowledge Center. Unknown. Retrieved 2026-09-18. adversarially verified

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

IG Fly ConfigGuide 'API Client' documents the mechanism: the operator adds a client with Client Type 'External' ('Internal is for future use'), a Duration 'after which the session would expire in the hh:mm format', and a Token that 'is auto generated when the form is saved'; the Active checkbox 'indicates the state of the client certificate. Enable or disable it to activate or deactivate a client respectively', and a Full Service flag decides whether 'the instance is allowed to access the Full Service APIs'. So grants are operator-created, individually revocable and coarsely scoped (Full Service on/off, plus binding to one terminal, profile, employee and job code) - but the credential is a generated bearer token, paired with a 'POS API Subscription Key' in POS API Configuration, not an OAuth 2.0 authorization grant with scopes. https://ig.onagilysys.com/help/POS/IG_Fly/ConfigGuide/API%20Client.htm · retrieved 2026-08-08

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

extensibility-webhooks-push

IG_12UX ConfigGuide 'Event Notification' (POS Configuration > Administration > Enterprise) enumerates the whole event surface: Enable Event Notification, Order Event - 'the order event details are sent to the external system when guests place orders or refund/void orders' - Kitchen Event - 'sent to the external system when the order is bumped in the kitchen' - and Employee Event, marked 'For future use'. Delivery is routed through a named IAS Adapter Configuration and Configuration Group. The IG Fly release note 'Send Order and Kitchen Events' publishes the push payload (type, ctxt.t_id/ent_id/sm_id/term_id, chkInfo with chkNum/GUID/ordId/status closed|refund, del_info, orders[] with item id, qty, splInst, chldEntts). This is push, not polling. Shortfall: only place, refund/void and kitchen-bump are covered - no modify or payment event, employee events are 'for future use' - and the same note says 'Contact Agilysys to initiate this integration at your property. Note that development efforts may be required on both sides', so it is a provisioned adapter rather than a self-serve webhook subscription. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Event%20Notification.htm · 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

The conjunction fails, but on the retry/replay half rather than the signing half. CORRECTED 2026-09-12: a first pass published `HMAC` as a corpus zero and rested the verdict on 'no secret, no signing key'. That zero was FALSE - it was bounded to a corpus missing the InfoGenesis POS Server 12.x help project, where release 12.3.15.4 'HMAC Authentication for Sending Event Notifications' states 'A signature generated using a configured key allows the receiving system to verify the authenticity of the request' and adds an Others (HMAC) adapter mode to IGCM with the fields UserName, Password, HeaderInfo, Url, HMACSecretKey ('the key used to generate signature for the external system request authentication'), HMACHeaderKey ('The header key name that carries the HMAC signature') and HMACAlgorithm ('Enter the hash function SHA-256 or SHA-512', default SHA-256). Signing is therefore DOCUMENTED and a shared secret IS configurable. What defeats the claim is the same release note's own statement of delivery semantics: 'Events for orders placed and orders prepared when IAS service is stopped will not be triggered again when IAS service restarts.' That is positive evidence of no retry and no replayable event log, not an absence of evidence. Corroborating: `backoff` and `signing key` occur ZERO times across the entire 8,068-document estate and `replay` zero times across all 7,051 help-topic bodies; the only `retry` inside any event-notification topic is an EPI settlement retry dialog; the Event Notification field table exposes no retry count or timeout; and the Send Order and Kitchen Events payload tables label their JSON a 'Sample' and show no signature field. The claim requires signing AND documented retry-with-backoff AND a replayable log, so it fails. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/Server12/12.3.15.4_RN/Contents.htm · retrieved 2026-09-12 adversarially verified

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

Olo, Crave and Tapingo are listed ordering partners, implying an order-injection path into InfoGenesis exists; the write API itself is not publicly documented. https://www.agilysys.com/en/solution-partners/ · retrieved 2026-08-01

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

extensibility-menu-write-api

331st: MOVED unknown -> partial on a BODY-level re-grep of the InfoGenesis help corpus on disk (.cache/q316/agilysys/corpus.json: 5,627 topic bodies, 10,620,922 characters; built from the MadCap MasterTOC manifests of all 7 IG help systems (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM), 5,540/5,540 TOC topics at HTTP 200, plus an href fixpoint). Every prior note on this cell searched hosts, PDFs and the marketing site for an operation list; none read the help bodies for the vendor's own term, which is 'Import Services'. CLAIM: menu items, modifiers and prices can be written and updated via API. EVIDENCE (vendor help, grade B, re-fetched live today at HTTP 200 with curl; nonsense control /IG_12UX/ReleaseNotes/zzz-nope-qq.htm 404): (1) https://ig.onagilysys.com/help/POS/IG_12UX/ReleaseNotes/12%203%2011%2012%20x%20Server%20Only.htm - '12.3.11 (12.x Server Only) | Import Services: New API to Delete SKU | The Update Import Services API has been enhanced to include a provision to delete the SKU code and description for a menu item ID. | Relative URL: {{casurll}}/ImportServices/Items/{ItemID}/SKUs/{SKU Number} ... Updated Documentation: InfoGenesis POS Import Services API Specification'. (2) https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Important%20Points.htm (identical in IG_Kiosk, IG_OnDemand, IG_Fly) - 'The following import service APIs are supported in CCM2: Item Import | Modifier Import. The following export service APIs are supported in CCM2: Order Table Export | Product mix Export | WinRetails Export | Summary Export | Clock Data Export' and 'Updating and deleting of base and group records is allowed in the Item, Modifier, Choice Group, Layout, Special Instructions menus.' (3) https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/Scheduling.htm - 'Item Import | Imports item data from a file. When the Enable Import via Web Service in the Parameters tab is selected, the items are imported with the translation text' (same sentence for Modifier Import). (4) The record format those imports carry, https://ig.onagilysys.com/help/POS/IG_12UX/ReleaseNotes/New%20Import%20and%20Export%20Tasks.htm: Item Import field 1 'Action | U or D ... U - To add a new item or update fields in an existing item', field 4 'Price Levels ... {action,price level ID,current price,store ID} Example: {U,3,10.5,1}'; Modifier Import field 1 'U - To add a new modifier or update fields in an existing modifier ... D - To delete a modifier', field 4 'Price Levels ... {action,price level ID,current price}'. So items, modifiers and their prices are written and updated through a vendor-named import service API, not just read (the read side is the 'ConfigurationMetadata export service APIs' listed in IGCM bug 558534: Items, Modifiers, PriceLevels among 25 objects). SHORTFALLS, why partial and not yes: the 'InfoGenesis POS Import Services API Specification' itself is not public (no anonymous spec on any of the 1,972 CT-listed hosts, the APIM developer portals list no Agilysys API), so the only REST operation published verbatim is SKU delete; the price and modifier write paths are documented through the import TASK's record format with a web-service switch, i.e. a batch import service rather than a published per-object CRUD API. Retrieved 2026-09-18. https://ig.onagilysys.com/help/POS/IG_12UX/ReleaseNotes/12%203%2011%2012%20x%20Server%20Only.htm · retrieved 2026-09-18 adversarially verified

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

VERDICT: unknown (unchanged). NEW SURFACE 2026-09-16: certificate-transparency census (crt.sh %.agilysys.com, %.onagilysys.com, %.rguest.com; certspotter rate-limited) = 1,972 distinct hostnames. Probed 211 IG/POS/API/loyalty/docs-named hosts at /, /swagger, /swagger/index.html, /swagger/v1/swagger.json, /api-docs, /openapi.json, /docs, /robots.txt plus a nonsense-path control, and the root of the other 1,761 (1,451 NXDOMAIN/unreachable). Result: no anonymous IG POS API spec. ig-integrationapi-prod-01/-sales, ig-posv3extint-prod-01-*, ig-usdef-integrationapi-*, igsaas, ig-config/cook/realtime/reports-prod-* all 403 'Web App - Unavailable' (a refusal, not an absence); ig-posv3-sales.onagilysys.com, ig-pos-qa.rguest.com, ig-auth-sales and ig-api-devopstraining serve /swagger/index.html as a 1,817-byte 'Authentication Gateway' ('Unauthorised Access!!' / Retry Login) - login-gated, not read further; /swagger/v1/swagger.json 404 on all. core-loyalty-*, v1-documentation-*, pay-swaggerui-*, integrationapiprod, igpos, igposweb: NXDOMAIN. The only anonymous Swagger found is pay-gateway-sales.onagilysys.com/help ('My Swagger UI', RGuest Pay payment gateway, not the POS API). No operation list is anonymously readable, so read/write symmetry is still undeterminable. Unknown (unchanged). Retrieved 2026-09-16. || 323rd: 323rd: the public-source-map route was run over Agilysys and it lands OUTSIDE this product. 100 production-named SPA hosts from the CT census (rguest.com / onagilysys.com; *-prod-* plus portal/admin/ui/web/console names, with dev/qa/demo/sales/uat/test/staging excluded) were fetched at / and their script bundles probed for <bundle>.js.map plus /asset-manifest.json, /manifest.json, /.vite/manifest.json and /packs/manifest.json, each against a /zzq-nonsense-81237.js.map control on the same host - necessary, because the control is a soft 200 on several (130,268 B on the tenant host), so byte length and the leading bytes were compared and only bodies starting {"version":3 were kept. Only 4 of 100 serve an HTML SPA at all, and only one serves a full map set: v1-tenantmanagementui-prod-westus.rguest.com, title 'Enterprise Management' (runtime.js.map 17,516 B, polyfills 2,120,261 B, scripts 211,013 B, main 14,573,515 B; main carries 518 sources with sourcesContent, 117 of them under ./src). It is NOT an InfoGenesis/POS app and cannot bound any POS cell: its own product enumeration ./src/app/shared/global.constant.ts reads 'export const enum Product { SPA = 1, RETAIL = 2, GOLF = 3, Common = 4, SalesAndCatering = 5, PMS = 6, Tenant = 7, EnhancedInventory = 8, HouseKeeping = 9, Accounting = 10, Folio = 11 }' - no POS member - and ./src/app/shared/constants/app-constants.ts sets TENANT_PRODUCT_ID = 7 (Tenant). SCOPE REJECTION, recorded so it is not re-mined: this is the rGuest Stay/Spa/Golf tenant console, a different product family from InfoGenesis. The only other map found is a vendored bootstrap.bundle.min.js.map on activities-adminportal-prod-ctrus.onagilysys.com ('Financial Admin Login'). Still unknown. Retrieved 2026-09-17. || 327th: 327th: bounded against a corpus this cell had never been checked against, with the same result: no Agilysys operation list is public for InfoGenesis. Over the first body-level census of www.agilysys.com's HTML pages (117 of 117 pages from the publisher's own page manifest https://www.agilysys.com/en/wp-sitemap-posts-page-1.xml, all HTTP 200, 1,846,153 characters; nonsense control /en/zzz-nope-control-qq/ 404; the WP REST API still withholds wp/v2 - types, media and solution_partner all 404 rest_no_route today), the only document that describes an Agilysys API as a contract is the Book4Time API Terms of Use, which is a spa-product agreement and enumerates no objects at all - it speaks of an 'Application that you develop using the Book4Time API to use, search, display, upload, and/or modify Book4Time content', which is a read/write framing for a DIFFERENT product and cannot be read onto the POS. 'webhook' 0. Retrieved 2026-09-18. || 331st: 331st: the help BODIES (never grepped for this cell; the InfoGenesis help corpus on disk (.cache/q316/agilysys/corpus.json: 5,627 topic bodies, 10,620,922 characters; built from the MadCap MasterTOC manifests of all 7 IG help systems (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM), 5,540/5,540 TOC topics at HTTP 200, plus an href fixpoint)) publish both halves of an InfoGenesis API object list for the first time, and they are asymmetric as far as they go, but the list is not a census. READ side: IGCM bug 558534, https://ig.onagilysys.com/help/POS/IGCM/ReleaseNotes/Bug%20Fix_1.htm: 'The following ConfigurationMetadata export service APIs ... BusinessPeriodRollTime | CardTypes | CheckTypes | Coupons | Discounts | EmployeeJobCodes | Employees | Gratuities | GratuityCategories | Items | JobCodes | MealPeriodSchedules | MealPeriods | Modifiers | PriceLevels | ProductClasses | ProfitCenters | RevenueClasses | Taxes | TaxCategories | Tenders | VoidReasons | TenderClasses | RevenueCategories | Terminals' (25 objects), plus export service APIs 'Order Table Export | Product mix Export | WinRetails Export | Summary Export | Clock Data Export'. WRITE side: https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Important%20Points.htm 'The following import service APIs are supported in CCM2: Item Import | Modifier Import', and the 12.3.11 Import Services SKU-delete endpoint. So menu objects are symmetric (read via ConfigurationMetadata, write via Import Services), and Employees/Tenders/Discounts/Taxes are readable with no import service API named. Not a no: the import list is scoped 'supported in CCM2' (the scheduler also has an Employee Import task), orders are written through the separate IG POS API (IG OnDemand 'Unable to create order in POS API'), and neither API's specification is public, so the write surface is not enumerated. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE (332nd): SwaggerHub, never checked for this vendor. Agilysys's own SwaggerHub organisations list anonymously: https://api.swaggerhub.com/apis/Agilysys-Inc = 13 APIs (PMS - Reservations and Profiles, PMS - Account Look-up and Charge Posting, PMS - Condo & Residence Management, StayConnect ARI / Config / Groups / Reservations & Profiles (published, modified 2026-08-28..09-03), PMS - Express Check-In and Check-Out, PMS - Booking Engine, PMS - Additional Inbound / Outbound APIs, PMS - Availability, Rates and Inventory) and https://api.swaggerhub.com/apis/Agilysys_STAY = 3 (Rbook, Stay OpenAPI Inbound/Outbound snapshots); a public-registry search for 'infogenesis' returns 4 unrelated specs (0 Agilysys). So Agilysys publishes 16 API definitions and ALL are the Stay PMS family (the 'Charge Posting' spec is the PMS side a POS posts to); ZERO InfoGenesis POS APIs are published there. That is a census of what Agilysys chose to publish on SwaggerHub, not of the IG POS API (which exists: Import Services, ConfigurationMetadata export, IG POS API clients, per the help corpus), and a sibling product's specs cannot score the POS. So no InfoGenesis operation list became readable this pass; the 331st's partial object lists (ConfigurationMetadata export vs Import Services) remain the only evidence, and they are not a census. Also new (third party, grade D): Avero's KB article 'Infogenesis API' (averoinc.zendesk.com, read via /api/v2/help_center/en-us/articles/15669431063827.json, updated 2026-07-17): 'InfoGenesis API is supported for Sales data only ... Agilisys provides Avero access to your businesses API to collect your sales data'; cloud IG needs only the store's TWS credentials and a base URL ('Base URL for v12 will be https://{{URL}}/bridge/1/ias-api/v2/{{siteId}}/{{adapterName}}'), while on-premise IG 'requires your team to work with Agilysys to setup API access'. No fee, licence price or tier is stated. Retrieved 2026-09-18. || 334th: NEW SURFACE (334th): the Agilysys Knowledge Center's InfoGenesis training courses are Supademo interactive walkthroughs of the live product, never opened by a prior pass (prior passes read only the course TITLES on /en/knowledge-center/). The three InfoGenesis course pages (https://www.agilysys.com/en/knowledge-center-videos/?course=<base64 title>: Back of House for Menu, Inventory and Admin Setup; Front of House for Ordering, Payments and Guest Service; Reporting) link 318 distinct demos, and all 318 were fetched anonymously at HTTP 200 from app.supademo.com/demo/<id>; each page embeds its full step list (narration 'audioText', on-screen callouts, screenshots) in the Next.js flight payload: 17,548 text fields, 780,574 characters, 7,219 screenshots. Vendor-authored tutorials walking the actual IGCM / POS terminal UI (grade B as documentation of what they show; a training set, not a census of the product). 'API' 0 and 'import' 0 over all 318 (exports are only report output: 'Adobe Acrobat (.pdf)', 'MS Excel (.xlsx)', and terminal diagnostic logs). The training set does not reach the API surface, so it does not enumerate either half of read/write. Unknown. Retrieved 2026-09-18. adversarially verified

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

extensibility-published-rate-limits

No rate limits are published; the entire API reference sits behind the developer-portal login. https://agys-dev.developer.azure-api.net/ · retrieved 2026-08-01

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 count of how many of the eight high-quality features the provider has built. It is served anonymously and merchants.doordash.com/robots.txt permits it (Allow: / with only /cdn-cgi/ and /monitoring barred). This is what the program page means when it says the roster is tracked in real time, and it is a CENSUS rather than a floor: every provider integrated with DoorDash appears in it with a tier, so a vendor that is absent altogether is not in the programme at any tier. This vendor appears nowhere in the 64 entries, under any provider id or friendly name — checked mechanically against both fields, with the only near-misses being substring coincidences (Speedline against Lightspeed, vroom_restaurant against Restaurant365) that were read and rejected. 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 and never a ceiling, and reading it as a ceiling is what produced this cell's prior grade. 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

No first-party DoorDash/Uber Eats/Grubhub integration is published; third-party ordering routes through partners such as Olo. https://www.agilysys.com/en/solution-partners/ · retrieved 2026-08-01

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

extensibility-middleware-compatibility

Score stands, partner list is wrong. The directory names OLO, Tapingo, LevelUp and Ssnapp under ordering; 'Crave' does not appear. Deliverect/Chowly/Otter/Checkmate are indeed absent, so the partial holds — but two of the three cited names were only two-thirds right. https://www.agilysys.com/en/solution-partners/ · retrieved 2026-08-01 adversarially verified

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

Eatec documents GL export and automated invoice reconciliation, and 'accounting reconciliation' is a named partner category; no named QuickBooks Online connector with mapped journal entries is confirmed. https://www.agilysys.com/en/solution-partners/ · retrieved 2026-08-01

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

extensibility-payroll-export

PayDayPortal and GoCardless appear in the partner directory under payroll/payments; two named major payroll providers with documented native export are not confirmed. https://www.agilysys.com/en/solution-partners/ · retrieved 2026-08-01

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

Analyze Data-as-a-Service exports clean data feeds into a customer's existing BI platform; destination types, scheduling and transaction-level granularity are unspecified and it is a paid SKU. https://www.agilysys.com/en/products/analyze/ · 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

A public, browsable Solution Partners directory lists 80+ named partners across 24 filterable categories, but there is no self-install mechanism — engagement is via 'contact us'. https://www.agilysys.com/en/solution-partners/ · retrieved 2026-08-01

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

extensibility-custom-fields-scripting

333rd: MOVED unknown -> partial/B on the FIELD half of this claim, from a vendor-vocabulary body grep of the InfoGenesis help corpus on disk (.cache/q316/agilysys/corpus.json, 5,627 topic bodies from the MadCap MasterTOC manifests of all 7 IG help systems) that the 328th ran only for the atlas's own words ('custom field|user-defined field|UDF', 1 poison hit). InfoGenesis does not call these 'custom fields'; it calls them special-instruction categories, tags and field labels, and all three are operator-configured in IGCM with no vendor step. EVIDENCE (vendor help centre, grade B, each page re-fetched live at 200 today): (1) OPERATOR-DEFINED INPUT FIELDS ON ORDER LINES. https://ig.onagilysys.com/help/POS/IG_Kiosk/UserGuide/Multiple%20Special%20Instructions.htm: "Users can configure multiple special instruction fields with specific categories, such as Allergies , Add Items , Avoid Items , and others. This allows the kiosk to display a maximum of 5 special instruction categories while ordering. Guests can enter the appropriate text in each special instruction field when adding items to the cart"; configured per profit-center card, https://ig.onagilysys.com/help/POS/IG_OnDemand/ConfigGuide/Display%20Multiple%20Special%20Instruction.htm: "Header Text | Allow Multiple Special Instruction ... Users can add up to 5 special instructions | Instruction Text | Kitchen Text" (same topic in IG_Kiosk/ConfigGuide and IG_OnDemand/UserGuide/Allergens.htm, where the limit is 20 characters). The operator names each field, the guest fills it per item, and the value travels with the item to the kitchen. (2) OPERATOR-DEFINED ITEM/MODIFIER ATTRIBUTES. https://ig.onagilysys.com/help/POS/IG_Kiosk/ConfigGuide/Tags_5.htm: "A tag an attribute associated with the item ... Tags can be associated with items and modifiers ... The following tags are available by default in the IGCM: Spicy ... Soy. Perform the following steps to configure Tags: Navigate to Kiosk/On Demand Configuration > Items > Tags . Select Add"; tags then attach to items, modifiers, packages, store items and store modifiers (IG_OnDemand/ConfigGuide/Tags.htm, Tags_1..Tags_4). (3) An operator-labelled response field on the Kiosk feedback form (IG_Kiosk/ConfigGuide/Feedback Question.htm: "Field Label | Enter the preferred field label. For example, Help us improve"). WHY PARTIAL AND NOT YES: all three are on the guest-facing Kiosk/OnDemand surfaces. The core POS objects (check, employee, customer, menu item at the 12UX terminal) have no operator-defined field of any type in the corpus. The terminal's 'Additional Info' prompt (IG_12UX/UserGuide/Additional Customer Information.htm) has mandatory and optional fields, but no topic says who defines them. The field types are free text and boolean tag only, capped at 5 categories and 15-20 characters. The SCRIPT half is still unmet as the 331st recorded: the one named script package is switched on by Agilysys ('Contact Agilysys to enable the RCCL-Scripts flag'). The closest operator-run logic is on-premise, not vendor-hosted: IG_12UX/ReportsGuide/Scheduling.htm, "This scheduling applies to both InfoGenesis tasks as well as user-defined tasks. Examples of user-defined tasks are: scheduling an executable ... or SQL database maintenance". POISON: 'User Defined 1/2' in Servers.htm are UDP server IP slots (lsr_udp), 'user-defined cards' in Basic Details_25 are card-prefix ranges, 'CPFAdd ... user-defined text' is receipt footer text; none is a field on a POS object. Retrieved 2026-09-18. https://ig.onagilysys.com/help/POS/IG_Kiosk/UserGuide/Multiple%20Special%20Instructions.htm · retrieved 2026-09-18 adversarially verified

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

IG Fly ConfigGuide 'API Client' documents an external system driving the POS transaction engine as a terminal: Client Type 'External'; Terminal - 'Only the terminals for which the Default for Virtual Terminal option is enabled appear here'; Profile, Employee and Job Code the client transacts as; Full Service - 'the instance is allowed to access the Full Service APIs'; and 'Supress LRD/LAS - checks are posted to GAS directly for non Full Service clients'. So a virtual-terminal headless mode is a documented, configurable product feature. Shortfall: no third party can build against it unaided - the API reference is partner-gated (the developer portal returns zero APIs to anonymous callers) and the parallel IG Fly event-integration note says 'Contact Agilysys to initiate this integration at your property. Note that development efforts may be required on both sides.' https://ig.onagilysys.com/help/POS/IG_Fly/ConfigGuide/API%20Client.htm · retrieved 2026-08-08

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

extensibility-api-versioning-deprecation

331st: MOVED unknown -> no on the conjunctive reading this atlas applied to qu (release notes carrying API changes, deprecation half fails). CLAIM: the vendor publishes an API changelog AND a stated deprecation/notice policy for breaking changes. CHANGELOG HALF (partly met, and this corrects earlier notes that said Agilysys publishes no API change record): the public InfoGenesis release notes do announce API changes - https://ig.onagilysys.com/help/POS/IG_12UX/ReleaseNotes/12%203%2011%2012%20x%20Server%20Only.htm 'Import Services: New API to Delete SKU ... Relative URL: {{casurll}}/ImportServices/Items/{ItemID}/SKUs/{SKU Number} ... Updated Documentation: InfoGenesis POS Import Services API Specification'; https://ig.onagilysys.com/help/POS/IGCM/ReleaseNotes/Move%20POS%20API%20Client%20License.htm (per-store POS API licence keys); IGCM bug 558534 (ConfigurationMetadata export service APIs); IG Fly 12.3.16 bug 1206246 (POS API event table); IG Fly Prerequisites 'POS API version 3.0.14.2'. 10 release-note topics in all touch an API, scattered through product notes; there is no dedicated API changelog. DEPRECATION HALF (absent, bounded): the InfoGenesis help corpus on disk (.cache/q316/agilysys/corpus.json: 5,627 topic bodies, 10,620,922 characters; built from the MadCap MasterTOC manifests of all 7 IG help systems (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM), 5,540/5,540 TOC topics at HTTP 200, plus an href fixpoint), tokenised word-boundary case-insensitive: 'deprecat*' 2 hits in 1 topic, both POISON (ReportsGuide/Scheduling 'SMU 86 Item ... Deprecated, see 86/Un-86 Management' - a scheduler command, not an API); 'sunset' 0; 'end of life' 0; 'breaking change' 0; 'notice period' 0; 'advance notice' 0; 'versioning' 0; 'backward(s) compatib*' 2, both POISON (a DMP installer key kept 'to support backwards compatibility'; terminal/interface-server upgrade parity). The same terms score 0 over the vendor's other published corpora recorded on this cell: 117 live PDFs / 3,079,354 chars ('changelog' 0, 'deprecat*' 0) and the 117/117-page www.agilysys.com body census ('changelog' 0, 'deprecation' 0). The only API-version statement Agilysys publishes anywhere is the Book4Time (spa product) API Terms s.04, which reserves the right to force upgrades with no notice window. SCOPE: the Import Services API Specification and the APIM developer portals are not public (agys-dev lists 0 APIs anonymously), so a policy could exist inside a licensed spec; the claim is about what the vendor PUBLISHES, and nothing published states one. Retrieved 2026-09-18. https://ig.onagilysys.com/help/POS/IG_12UX/ReleaseNotes/12%203%2011%2012%20x%20Server%20Only.htm · retrieved 2026-09-18 adversarially verified

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

In-product export exists but is report-shaped, and contract-end retrieval is a manual request. IGCM's Electronic Journal utility exports filtered check-event data (Utilities > Utilities > Electronic Journal, with an 'Export Electronic Journal with Header and Applied Filters' option; CSV by email, PDF and Excel), and the ReportsGuide states InfoGenesis reports are 'printed or viewed on-screen, published with Adobe Acrobat, analyzed with Microsoft Excel, or exported to other programs'. At contract end, however, the published Data Processing Agreement (04-02-25, incorporated into the Terms by section 11.13) says only: 'You may make a written request to Agilysys for the retrieval of, or access to, your Personal Data up to ten (10) days prior to the termination of Subscription Services' (12.1), with no format specified and no coverage of orders, menu or payment metadata; 12.2 then requires prompt deletion. There is no documented complete machine-readable historical export available on demand. https://www.agilysys.com/en/wp-content/uploads/Agilysys-Data-Processing-Agreement-04-02-25-Final.pdf · retrieved 2026-08-08

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

reliability-offline-order-entry

Enterprise-grade offline resiliency is claimed with check data reconciling on restore; no documented guarantee of on-terminal ticket routing and check printing during outage. https://www.agilysys.com/en/products/infogenesis-pos/ · retrieved 2026-08-01

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

reliability-offline-card-auth

Verified verbatim on the IG Flex page: 'Continue accepting orders and payments during connectivity disruptions. Transactions automatically synchronize once network access is restored.' Upheld ONLY at that scope — it is a marketing bullet on ONE hardware SKU. The IG Fly page makes no offline claim at all, and no floor limit, cumulative cap, or auth mechanism is published anywhere. A buyer should treat this as unverified for anything other than IG Flex. https://www.agilysys.com/en/products/ig-flex/ · retrieved 2026-08-01 adversarially verified

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

OVERTURNED from `no`. The prior rationale claimed no document "addresses store-and-forward decline liability or offline transaction caps"; the caps half is false. InfoGenesis publishes at least four configurable offline caps: "Credit Card Offline - Limit ... This is the credit card dollar amount beyond which offline credit card transaction will not be allowed" (Credit Card Bypass Limits); "Offline user max limit" and "Offline check limit" (Offline Configurations); and a per-account and per-terminal count cap for campus-card tenders whose exceeded-prompt is published verbatim -- "You've reached the maximum number of offline tenders. Please reconnect to the network or contact the system administrator" -- reset "once a transaction is made when both the service manager and terminal are back online". `partial`, not `yes`, because the claim is a conjunction and the liability half remains unpublished: no document says who bears the loss when a stored transaction declines after reconnect, and the one risk sentence in the corpus attaches to the pre-authorisation bypass limit, not to store-and-forward. Grade B: the vendor's own configuration documentation. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Credit%20Card%20Bypass%20Limits.htm · retrieved 2026-09-09

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

IG_12UX UserGuide 'Local Shift Services (LSS)': 'The Local Shift Service (LSS) is a windows service running locally at the customer site on an interface server or terminal box. The LSS allows terminal operations to continue during a loss of connectivity to the back office.' Terminal Option 279 routes transaction data to the LSS server 'and not in the POS server. When the terminal is back online, the transaction data in this server is uploaded to the POS server', and the terminal status indicator turns amber to show LSS is acting as backup server. The supported set is shared, not per-terminal: 'Check services: save, recall, tender, void, refund, and recall check list', 'Sequential order number (store level and profit center specific)', employee sign-on/clock-in, tip transfer and payout, loans and withdrawals, shift resets and reports. Store-level sequential numbering and a recallable check list held on one LAN service is shared check state across terminals, not islands. (Without LSS the fallback is much thinner - UserGuide 'Go Offline': 'Most of the terminal functions cannot be performed when the terminal goes offline.') https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Local%20Shift%20Services%20LSS.htm · retrieved 2026-08-08

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

Local Application Service (LAS) is a documented on-premise component, not an inference from marketing copy. The installer topic lists 'Local Application Service (LAS)' as an install-time checkbox next to IG App Central and IIS Proxy Server. The KDS guide describes its runtime behaviour: kitchen orders are filtered per LAS device; 'Scheduled Sync LAS - LAS sends closed orders to the server at configured intervals; open and scheduled orders are excluded'; 'Sync Failure / Multi-LAS - if sync is disabled, orders are stored on LAS and are synced once connectivity is restored'; and offline is reported as 'Unable to connect with GAS / LAS to retrieve order status', distinguishing the local service from the cloud Global Application Service. The terminal itself also holds state: 'If for any reason a terminal is disconnected from the system, employees can continue to ring sales with no system downtime. All data is captured offline at the POS terminal and automatically uploaded to the server upon reconnection.' https://ig.onagilysys.com/help/POS/IG_KDS/UserGuide/View%20and%20Filter%20Kitchen%20Order.htm · retrieved 2026-08-06

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

reliability-offline-kds-printing

InfoGenesis states kitchen jobs automatically reconcile when the network restores, implying local queueing of kitchen routing during outage; not stated as a guarantee. https://www.agilysys.com/en/products/infogenesis-pos/ · retrieved 2026-08-01

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

On kitchen-printer failure the terminal alerts staff with cause-specific prompts (Terminal Option 1464: unreachable, out of paper, door open, service stopped) and 'the receipt printer prints the kitchen chits when the kitchen printer fails to print chits' (Terminal Option 150), plus a Print Locally button. Shortfall: the fallback lands on the terminal's own receipt printer, not a designated backup kitchen device - the config guide states outright that 'alternate kitchen printers are not backup or fail-over printers' (they are scheduled rerouting), and no automatic failover to a backup kitchen printer or KDS station is documented. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Display%20Kitchen%20Printer%20Error.htm · retrieved 2026-08-03

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

Conflict behavior is documented for two narrow cases. GAS outage: items 86ed while the service is unreachable keep a local-86 icon and 'must be manually re-86ed after GAS connectivity is restored', while items un86ed offline 'revert to their previous global status' on re-login - server-wins for un86, manual reconciliation for 86. Two-terminal contention: a check recalled on a second terminal opens view-only, an operator-prompted Break Lock can seize it, a Break Lock Failure prompt fires if the check was tendered elsewhere, and the manual warns the function 'can lead to discrepancies owing to the checks from different terminals getting mixed up'. Shortfall: no documented policy (last-write-wins, merge or prompt) for check edits made on two devices during a network partition - Go Offline mode disables most terminal functions, and the documentation stops at the caution note. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Global%20Application%20Service.htm · retrieved 2026-08-04

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

OVERTURNED from `no`. The prior rationale said Agilysys "publishes no explicit list of what is unavailable offline"; the Go Offline topic publishes one, in three sentences: "When the terminal is offline, none of the reports are generated. The user cannot clock out or clock in when the terminal goes offline. Most of the terminal functions cannot be performed when the terminal goes offline." The paired Go Online topic states what survives -- "When the terminal goes offline the transaction data is saved in the local database" and is uploaded on reconnect. `partial` rather than `yes` because the third sentence is a catch-all, not an enumeration: "most of the terminal functions" names nothing, and none of the functions the claim asks about -- gift cards, loyalty lookup, refunds, manual card entry -- is placed on either side. What IS individually enumerated is reporting and time clock (unavailable) plus check capture (available), together with the separately documented offline caps. Grade B: the vendor's own user documentation. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Go%20Offline.htm · retrieved 2026-09-09

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

reliability-public-status-page

Upheld and strengthened. status.onagilysys.com renders empty to a fetcher, but the component roster is independently confirmed at 20 components including 'IG 12 NA' (i.e. InfoGenesis 12), Eatec NA, Pay NA, PanOptic Kiosk NA, Digital Marketing NA — so the POS itself is in scope, which the dossier did not establish. Still no rolling uptime percentage. https://statusgator.com/services/agilysys-saas-north-america · retrieved 2026-08-01 adversarially verified

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

327th: MOVED unknown -> partial. The 326th merge held a proposed partial with the reason 'no percentage or credit schedule is published anywhere, so no conjunct of the claim is affirmatively met'. A PERCENTAGE IS PUBLISHED, on a page no prior pass had read. EVIDENCE: www.agilysys.com/en/about/ carries a statistics band whose fourth tile is, in raw HTML (checked as bytes, not as tag-stripped text, so this is not a welded artefact): <img alt="Uptime Guarantee"> ... <h3 class="text-slider-heading...">99.5%</h3> <p class="text-p-base mb-3">Uptime Guarantee</p> <p class="text-xs...">24/7 Support</p>. So Agilysys publicly states a 99.5% uptime guarantee. Read with the FY2026 10-K's Item 1A statement recorded in the 326th ('We may have contractual service level agreements (SLAs) requiring specified uptime and performance standards ... could result in service credits'), each conjunct now has some first-party support. WHY PARTIAL AND NOT YES: the percentage is a marketing stat tile (grade C) attached to no agreement, the standard published Terms still make the sole remedy correct / circumvent / refund rather than a credit, and the incorporated 'service level policy' is still unpublished. BOUND/CONTROLS: over the FIRST body-level census of www.agilysys.com's HTML pages (prior passes read only ~9 legal pages plus the 117-document PDF library): the publisher's own page manifest https://www.agilysys.com/en/wp-sitemap-posts-page-1.xml lists 117 pages and all 117 were fetched at HTTP 200 (1,846,153 characters of stripped text); the nonsense control https://www.agilysys.com/en/zzz-nope-control-qq/ returns 404. (The WP REST API still withholds wp/v2 - /en/wp-json/ lists 68 routes in 10 namespaces, and wp/v2/types, wp/v2/media and wp/v2/solution_partner all 404 with rest_no_route, re-confirmed today.) tokenised word-boundary case-insensitive: 'service credit' 0, '99.5' 1 (this tile), 'guarantee' 2 (this tile and a privacy-policy sentence), 'uptime' 8 - POISON NAMED: the other 7 uptime hits are unquantified marketing prose on the IG Fly, IG KDS, IG Kiosk, InfoGenesis POS, Pay and PMS product pages ('built for uptime and resiliency', 'continuous uptime'). 'SLA' scores 2 and both are Book4Time documents (the acquired spa product). Retrieved 2026-09-18. https://www.agilysys.com/en/about/ · retrieved 2026-09-18 adversarially verified

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

reliability-incident-postmortems

The status page publishes its own configuration and it forecloses this. status.onagilysys.com is Site24x7 StatusIQ ('Agilysys SaaS North America Status'; DNS CNAMEs to site24x7sp.com, assets on site24x7static.com) and ships a statuspages.globals.preferences object in the page source containing '"show_incident_history":false', '"show_incident_history_last_n_days" : 2', '"status_history_last_n_days":2', '"show_component_details_page":false', '"allow_rss_feed":false' and '"allow_calendar_feed":false' - all six verified verbatim in the bytes retrieved 2026-09-12. Probed live the same day: /rss answers HTTP 200 with 'RSS feed disabled for this page.', /ical answers 'Calender feed disabled for this page.' and /history 404s, so there is no incident archive to carry a root-cause summary even in principle. This is NOT a Statuspage tenant, so the Atlassian Atom-feed route does not apply: agilysys.statuspage.io 301s to atlassian.com/software/statuspage, byte-identical to a fabricated control subdomain, i.e. no such tenant exists. `postmortem` and `root-cause summary` occur ZERO times across the entire 8,068-document estate; the only root-cause commitment Agilysys makes anywhere is private and contractual - DPA 11.4, 'Agilysys will take reasonable measures designed to identify the root cause(s) of the Personal Data Breach', reported to the affected customer, not published. GRADE: an embedded page-configuration object is neither primary technical documentation nor a spec nor a filing, so this is graded B (a first-party vendor-operated surface, measured directly) rather than the A a first pass assigned. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://status.onagilysys.com/ · retrieved 2026-09-12 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

Re-verified 2026-08-08 at the live URL (/en/support/ now 301s to /en/customer-support/). The support page states availability as 24 hours a day, 7 days a week for Critical/Emergency issues, for Standard support and for email, with the MyAgilysys portal, SupportDesk@agilysys.com and regional phone lines - North America 800-327-7088 and Las Vegas 702-875-4900, EMEA +44-203-868-3138, and APAC lines for Australia, China and Singapore among others. No premium support tier is distinguished on the page. The dossier's earlier caveat that no Level 2 engineer is available after 5pm or at weekends remains unsourced and is withdrawn. https://www.agilysys.com/en/customer-support/ · retrieved 2026-08-08 adversarially verified

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

Agilysys's published Terms and Conditions define Professional Services as 'the installation, integration, training and other professional or technical services specified in the Agreement' (1.6), performed 'by Agilysys' professional services organization (which may include third parties under contract with Agilysys)' (3.1) - i.e. first-party or contracted-dealer delivery, with the customer reimbursing 'reasonable out-of-pocket expenses' (5.5). Self-install is actively discouraged: 'If Customer elects to either (a) perform its own installation of Software, or (b) have a third party which has not been approved in writing by Agilysys perform installation of Software, Agilysys may refuse to provide Support Services for any or all of such Software' (3.5). Shortfall: nothing published states the work is performed in person on site rather than remotely, installation is a separately quoted chargeable service billed at hourly rates (5.2) rather than included, and no go-live support window or lead time is stated anywhere. https://www.agilysys.com/en/terms-and-conditions/ · retrieved 2026-08-08

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

reliability-menu-build-service

DOWNGRADED from partial/C 2026-09-12. The asserted partial rested on one line of the Agilysys Professional Services sell sheet, under Software Installation: 'Whether you're deploying a Property Management System (PMS) or Point of Sale (POS), this service includes discovery, configuration and database build.' Re-read the whole sheet: the word 'menu' occurs in it ZERO times. 'Database build' is a different proposition from an initial MENU or item-database build, and the sheet disclaims itself in terms - 'The information contained in this promotional material is for illustration purposes only.' - which is the document's own framing sentence falsifying any ceiling or floor read off it. Nothing else in the measured corpus states that a menu build is performed by Agilysys, or that it is included: the Terms define Professional Services as 'the installation, integration, training and other professional or technical services specified in the Agreement' (1.6) and bill them at hourly rates as good-faith estimates (5.2), with the scope of any engagement sitting in the non-public Agreement. Reading a marketing sell sheet that never mentions menus as evidence of a menu-build service is the marketing-as-capability error this pass exists to catch. Assessed, unresolved. || 319th: VERDICT: unknown (unchanged). NEW SURFACE 2026-09-16 (found via crt.sh): compassintakeform.onagilysys.com, an anonymous 'Compass Group / Agilysys Implementation Form' (251 KB single page). Fields: 'Type of Project: Add-On Unit | Hardware Remediation | New Construction | New Install/Product - Existing Site | Remediation | Version Upgrade', 'Tech Resource: Agilysys On-Site | Agilysys Remote | Compass Digital', 'Functionality Add: Rotating Menus / GA Auth / Table Layout / SMS Functionality'. No field for menu or item-database build, nor for who performs it; it is also a single-customer (Compass) intake form, not a general onboarding statement. Unknown (unchanged). Retrieved 2026-09-16. || 325th: 325th: NEW SURFACE - there is a SECOND services sell sheet, Agilysys Technical Services (https://www.agilysys.com/en/wp-content/uploads/Agilysys-Technical-Services.pdf, live 200, 525,358 bytes, 01/25 revision), distinct from the Professional Services sheet on which the 2026-09-12 downgrade rested. Found by enumerating the WordPress media library from the Wayback CDX index (263 /en/wp-content/ documents) because /en/wp-json exposes no wp/v2 routes and wp-sitemap.xml lists no media. Read in full: the word 'menu' occurs ZERO times in it as well. Its engagement list is 'Consultation and Gap Analysis', 'Development Planning' ('Our specialists help you plan for the specific needs of your business, discover new capabilities, build and configure your technology, validate your data, train staff and monitor deployment'), 'Seamless Integrations' and 'Implementation, Training and Monitoring' - 'build and configure your technology' and 'validate your data' are the same generic build language the downgrade already rejected, on a sheet that carries the same self-disclaiming sentence ('The information contained in this promotional material is for illustration purposes only'). Two of two published services sheets are now read and neither states that Agilysys performs the initial menu or item-database build. Unknown (unchanged). Retrieved 2026-09-17. || 326th: 326th: the services catalogue is now CLOSED and the answer does not change. www.agilysys.com/en/product-resource/ is a vendor-published enumeration of 28 current datasheets (identical on /page/2/ and /page/3/ - the pager is a client-side filter), and exactly three of the 28 are services sheets: Agilysys Professional Services and Agilysys Technical Services (both read in prior passes) and Agilysys Service - which turns out NOT to be an onboarding sheet at all but a housekeeping/engineering task-automation product ('Agilysys Service brings housekeeping, engineering, guest requests, and food runner assignments into one mobile-first platform'), recorded so a later reader does not mistake it for a services offer. Across all 117 documents and 3,079,354 characters, 'menu build' = 0 and 'menu configuration' = 0; the 46 'menu' hits are menu-engineering, digital-menu and menu-item product features. Three of three published services documents are now read and none states that Agilysys performs the initial menu or item-database build. Still unknown rather than no: the scope of any engagement sits in the non-public Agreement, which the Terms bill at hourly rates as a good-faith estimate. Retrieved 2026-09-18. || 327th: 327th: NEW SURFACE - the Agilysys Knowledge Center (www.agilysys.com/en/knowledge-center/), a public catalogue of the vendor's 'how-to' training curricula that no prior pass has cited. Its InfoGenesis entry is 'InfoGenesis POS Back of House Training for Menu, Inventory, and Admin Setup - Step-by-step InfoGenesis POS back of house video training for inventory, menu setup, and administrative workflows', i.e. Agilysys trains the OPERATOR to do menu setup. That is suggestive, not dispositive (training a customer to maintain a menu does not establish who performs the initial build), so the cell stays unknown. BOUND: 'menu build' 0 and 'menu configuration' 0 over the FIRST body-level census of www.agilysys.com's HTML pages (prior passes read only ~9 legal pages plus the 117-document PDF library): the publisher's own page manifest https://www.agilysys.com/en/wp-sitemap-posts-page-1.xml lists 117 pages and all 117 were fetched at HTTP 200 (1,846,153 characters of stripped text); the nonsense control https://www.agilysys.com/en/zzz-nope-control-qq/ returns 404. (The WP REST API still withholds wp/v2 - /en/wp-json/ lists 68 routes in 10 namespaces, and wp/v2/types, wp/v2/media and wp/v2/solution_partner all 404 with rest_no_route, re-confirmed today.) ; 'onboarding' scores 10 across 9 pages and none of them attaches a menu or item-database build to Agilysys. Retrieved 2026-09-18. || 331st: 331st: the help BODIES, never checked for this cell (prior notes read collateral and the site), are silent on who builds the menu. the InfoGenesis help corpus on disk (.cache/q316/agilysys/corpus.json: 5,627 topic bodies, 10,620,922 characters; built from the MadCap MasterTOC manifests of all 7 IG help systems (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM), 5,540/5,540 TOC topics at HTTP 200, plus an href fixpoint), tokenised: 'menu build' 0, 'build (the|your) menu' 0, 'data/database build|conversion' 0, 'implementation (team|engineer|consultant|specialist)' 0. 'Agilysys installer' scores 4 hits in 3 topics, all Opera OHIP interface mapping ('collaborate with the Agilysys installer to finalize the setup'), not menu work. What the docs do show is operator-side menu tooling: https://ig.onagilysys.com/help/POS/IG_12UX/ReleaseNotes/New%20Import%20and%20Export%20Tasks.htm Item/Modifier Import from .csv, 'It is recommended to first export the .csv file and then perform import by modifying the exported file'. Consistent with the Knowledge Center's operator menu-setup training; no statement either way on an Agilysys-performed initial build. Retrieved 2026-09-18. || 334th: NEW SURFACE (334th): the Agilysys Knowledge Center's InfoGenesis training courses are Supademo interactive walkthroughs of the live product, never opened by a prior pass (prior passes read only the course TITLES on /en/knowledge-center/). The three InfoGenesis course pages (https://www.agilysys.com/en/knowledge-center-videos/?course=<base64 title>: Back of House for Menu, Inventory and Admin Setup; Front of House for Ordering, Payments and Guest Service; Reporting) link 318 distinct demos, and all 318 were fetched anonymously at HTTP 200 from app.supademo.com/demo/<id>; each page embeds its full step list (narration 'audioText', on-screen callouts, screenshots) in the Next.js flight payload: 17,548 text fields, 780,574 characters, 7,219 screenshots. Vendor-authored tutorials walking the actual IGCM / POS terminal UI (grade B as documentation of what they show; a training set, not a census of the product). The Back of House course (123 demos) has a whole 'Item & Menu Management' section taught to the OPERATOR: Creating an Item, Creating an Item Group, Creating a Modifier, Creating a Choice Group, Adding Modifiers to a Choice Group - Manager, Creating a Product Class, Updating Item Price, Creating an Item with an Existing Item's Data, 86ing Items & Modifiers, Creating a Meal Period / Screen Schedule / Price Level, plus CCM2 parent-to-child item assignment. 'Agilysys' scores 330 hits and every one is product branding; no demo says Agilysys builds or loads the initial menu. Also new: local transcripts (faster-whisper, audio via yt-dlp; captions are IP-blocked) of the Agilysys YouTube testimonials Crazy Pita (QOuNILfNeps), Blue Lake Casino (P8K7_kmc7vM) and Grande Colonial (g1x3lz53ER4): 'professional services or support ... like a unified team whether or not they're on site or on the phone' (Blue Lake) - no menu build named. Consistent with operator-built menus; still not a statement either way, so unknown. Retrieved 2026-09-18. adversarially verified

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

reliability-hardware-replacement-sla

Agilysys publishes a self-serve RMA request tool (agilysys.com/en/rmarequest/) whose stated guidelines are: 'Return requests on this tool is only for material that shipped within the last 30 days'; categories include 'DOA Failure: If the product fails within 30 days of shipping to you' and a 'Warranty Return' reason code; and 'Product failure outside of 30 days from shipping date must be routed through the support team for a SalesForce Ticket. Please contact support for this at 800-327-7088.' The published Terms also contemplate paid equipment cover - 'Agilysys shall have no support obligations of any kind regarding Equipment except as specifically provided in any separate maintenance service contract with respect to Equipment' (3.5) - so a hardware maintenance contract is purchasable. Shortfall: this is a returns process, not an advance-exchange programme; no replacement turnaround time (next-business-day, 4-hour, or any figure) is published, and section 6.1 disclaims all Agilysys equipment warranty beyond the manufacturer's. https://www.agilysys.com/en/rmarequest/ · 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

The second disjunct is a publication test and it fails outright; the first is a bounded enumeration over a complete help census. No recovery figure is published: `RTO`, `recovery point` and `recovery time` occur ZERO times across the entire 8,068-document estate and `disaster recovery` zero times across all 7,051 help-topic bodies (5 hits elsewhere, none with a figure), while the 73 apparent `RPO` hits in that corpus are a poison control - all 73, in 12 documents, are the InfoGenesis 'PMS RPOS Protocol' name, not a Recovery Point Objective. And no operator-triggered backup or restore is documented: across the 7,051 bodies the 99 `backup` hits are kitchen and digital-menu-board backup STATIONS, the LSS backup server and printer backup, the 42 `restore` hits are Remove/Restore Tax, Gratuity and Service Charge functions, and the System Management Utility terminal command set is Go Online, Go Offline, Reload Config and Clear Dispatcher Connection. The Server 12.x help project, added to the corpus by the adversarial pass, contains `backup`, `restore` and `recovery` zero times. CORRECTED 2026-09-12 on two points: the figure was published as 110 `backup` hits, which was the wider-corpus count, not the help-corpus count it was attributed to; and the contract must not be read as settling the FEATURE. Terms 2.1 ('to make one (1) copy of the Software if reasonably necessary for internal back-up purposes'), DPA 12.1 ('back up or otherwise store separately any Personal Data') and DPA Exhibit 2 item 13 ('Business resiliency/ continuity and disaster recovery procedures', with no RPO or RTO attached) settle what the customer is ENTITLED to do and confirm no figure is published; they corroborate, they do not establish the absence of a product function. Residual limit on the first disjunct: Agilysys publishes no server installation or administration guide, so an on-premise DBA-level backup path would not appear in this corpus either way. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Files%201.htm · retrieved 2026-09-12 adversarially verified

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

PCI-validated P2PE is claimed across Pay, Kiosk and Flex; no PCI DSS 4.0/4.0.1 AoC, no P2PE listing reference and no trust center are published. https://www.agilysys.com/en/products/pay/ · retrieved 2026-08-01

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

reliability-mfa-role-based-access

IG_12UX ConfigGuide 'Single Sign-On (SSO)': 'InfoGenesis POS can integrate with any identity provider supported by Microsoft Azure AD B2C... A user flow is a predefined sequence of steps that guide the authentication process... It allows properties to customize how their users must interact with our products when signing in (for example, MFA).' For the Local Account option the customisable preferences explicitly include 'Is multifactor authentication required (Available options include Email, SMS and/or Phone call, Authenticator App)', plus reCAPTCHA, password complexity and web session timeout; SAML and OAuth/OIDC providers are both supported. RBAC is fully documented: ConfigGuide 'Permission Group' - 'Permissions are set for each POS form, listing, executable, or report. For each form, permissions are set to view the form, add a record, edit information, and delete a record' - with Roles, Permission Levels and tenant-level roles. Shortfall: MFA is documented on the IGCM back-office/identity layer only; POS terminal sign-on is employee ID, job code and MSR card swipe, and ConfigGuide 'Password Security' enumerates the terminal-side controls as complexity, 90-day expiry, four-password history and lockout after six failures with no second factor. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Single%20Sign%20On%20SSO.htm · retrieved 2026-08-08

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

reliability-self-serve-training

A genuinely public, login-free InfoGenesis Help Center provides configuration guides, user guides and release notes for POS Terminal, IG Kiosk, IG OnDemand, IG Fly, IG KDS and Digital Menu Board. But operators report Agilysys charges for all instructor training with no online training video library, and no terminal training mode is documented. https://ig.onagilysys.com/help/Default.htm · retrieved 2026-08-01

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

reliability-failover-terminal-role

IG_12UX UserGuide 'Local Shift Services (LSS)' documents automatic role takeover when the host server is lost: LSS is 'a windows service running locally at the customer site on an interface server or terminal box' and 'allows terminal operations to continue during a loss of connectivity to the back office'; with Terminal Option 279 enabled 'the transaction data is saved in the server where LSS is active and not in the POS server', the status indicator turns amber automatically, and LSS carries 'the full suite of InfoGenesis POS shift services' - check save/recall/tender/void/refund, sign-on and clock-in, tip transfer and payout, shift resets and reports. Shortfall: the backup host is pre-designated in IGCM ('any other configuration related to setting up the LSS must also be done in IGCM'), not elected at failure time; no topic in the help system describes any terminal automatically assuming the master role, and no election, quorum or promotion behaviour is documented. https://ig.onagilysys.com/help/POS/IG_12UX/UserGuide/Local%20Shift%20Services%20LSS.htm · retrieved 2026-08-08

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

reliability-cellular-backup

IG Fly ships cellular backup connectivity as a documented Wi-Fi failover. https://www.agilysys.com/en/products/ig-fly/ · retrieved 2026-08-01

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

No month-to-month subscription is publicly offered, on the same standard applied to the other quote-only enterprise records. The published Terms set an annual default and defer the initial term to a non-public order form - 5.4: 'Unless otherwise stated in the Agreement, the term of each Subscription Service will automatically renew thereafter for additional one year periods unless either party provides written notice of termination at least 30 days prior to the end of the current term' - and 10.1 runs open-ended. Enumerated the publisher's own page manifest: the WordPress sitemap index at /en/wp-sitemap.xml declares exactly five sub-sitemaps (posts, pages and three taxonomies), the two content ones list 117 pages and 820 posts, and there is no pricing page, no plan or tier page and no self-serve sign-up. `month-to-month` and `month to month` occur ZERO times across the entire 8,068-document estate, the 820 posts included. The FY2026 10-K corroborates a committed book rather than a monthly one: approximately $152 million of remaining performance obligations sits in 'contracts greater than one year', with 42%, 30% and 17% expected within the 12, 24 and 36 months following March 31, 2026 and 'the rest thereafter'. As with the NCR Voyix row, this establishes only that no month-to-month offer exists in public terms - the length of the commitment a given customer signs is set in the unpublished order form. Corpus, re-derived adversarially on 2026-09-12: every help-topic BODY at HTTP 200 - 5,503 InfoGenesis topics (IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB, IGCM) plus 92 InfoGenesis POS Server 12.x topics = 5,595, plus 1,456 Eatec topics = 7,051 of 7,051 - then the whole content set the WordPress sitemap index declares, 117 /en/ pages and 820 /en/ posts, and the 80 PDFs those pages link: 8,068 documents. The Server 12.x help project and the 820 posts were BOTH absent from the first pass's 7,156, and each product's MasterTOC is a strict SUPERSET of every content topic in that product's own Sitemap.xml (the sitemaps add only Default.htm, Search.htm and image assets), so 7,051 is a census of the help systems and 117+820 a census of the site, while the 80 PDFs are a FLOOR - the sitemap index declares no attachment sitemap. https://www.agilysys.com/en/terms-and-conditions/ · retrieved 2026-09-12 adversarially verified

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

Agilysys's published Terms and Conditions do not state what the claim requires and state close to its opposite. Section 5.4: 'Except as set forth herein, all fees for Subscription Services will be non-refundable once paid.' Termination rights are limited: 10.2 permits termination only for an uncured material breach after 30 days' written notice, and 10.3's termination-at-convenience right is expressly scoped to Software licences ('Customer may terminate Software license(s) at its convenience upon written notice to Agilysys'), not to Subscription Services. There is thus no published right to cancel a subscription mid-term, and prepaid fees are forfeited if the customer stops using it - the published terms contain no no-ETF/no-liquidated-damages statement. https://www.agilysys.com/en/terms-and-conditions/ · 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

OVERTURNED from `no`. The prior rationale -- "No publicly accessible contract terms on agilysys.com state auto-renewal length or cancellation notice window; terms live only in signed quotes" -- was false, and the record's OWN standing notes already cited this document twice for other cells. The US Sales Terms & Conditions state both halves of the claim in one sentence: "the term of each Subscription Service will automatically renew thereafter for additional one year periods unless either party provides written notice of termination at least 30 days prior to the end of the current term." Support Services carry their own identical clause: "Support Services shall automatically renew from year to year unless Customer provides written notice of termination at least 30 days prior to the end of the current annual Support Services term." Eleven further jurisdictional editions are published on the same host (UK, Australia, UAE, Canada, Hong Kong, Malaysia, Philippines, Singapore, plus the Book4Time set) and the UK edition repeats it verbatim with a hyphen -- "additional one-year periods". Term one year, notice 30 days, public, bilateral. Grade B: the vendor's own contract page. https://www.agilysys.com/en/terms-and-conditions/ · retrieved 2026-09-09

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

Agilysys certifies multiple third-party processors and gateways — Adyen, Elavon, FreedomPay, Shift4, Global Payments, Verifone, Tyro, Windcave — so Agilysys Pay is elective. A genuine differentiator versus Toast/Square. https://www.agilysys.com/en/solution-partners/ · retrieved 2026-08-01

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

No processing rate of any structure is published; the Agilysys Pay page carries no pricing. https://www.agilysys.com/en/products/pay/ · retrieved 2026-08-01

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

The prior line said this was never scored. Agilysys's published Terms and Conditions, section 5.4: 'Agilysys may change any portion of the fees for Subscription Services upon any renewal of the Subscription Services term by providing notice of such changes at least 30 days prior to the end of the current term' - so mid-term unilateral increases on the subscription are foreclosed, and because either party may decline renewal on 30 days' notice under the same clause, the customer can exit at the increase without a termination charge. Shortfall: no cap on the size of any renewal increase is stated; the notice and the customer's own opt-out deadline are both '30 days prior to the end of the current term', leaving no consideration period; Software Support is weaker still - 'Agilysys reserves the right to make changes to its support policy and prospectively change its fees at any time' (3.2); and no card-processing agreement for Agilysys Pay is published anywhere on agilysys.com, so processing rates and interchange pass-through are entirely unaddressed by any public document. https://www.agilysys.com/en/terms-and-conditions/ · retrieved 2026-08-08

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

Rebuilt off the vendor's own site index after the original Capterra basis was voided as a denylisted host. agilysys.com/robots.txt declares two sitemaps; the page sitemap enumerates 117 published pages, 35 of them under /en/products/, covering every SKU. Grepping the full set for pric|cost|plan|quote returns exactly one hit, /en/stock-quotes/, the investor stock-price page. A complete first-party page index containing no pricing page is positive evidence of absence. https://www.agilysys.com/en/wp-sitemap-posts-page-1.xml · retrieved 2026-08-02 adversarially verified

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

Re-evidenced 2026-08-08 from the vendor's live page inventory after the cited index 301'd to the homepage. The catalogue is explicitly modular: 37 separately marketed product pages, including Eatec, Analyze, Loyalty & Promotions, Pay, Authorize, Gift Card, IG Quick Pay, IG Kiosk, IG PanOptic Kiosk, IG KDS, IG OnDemand, IG Flex, IG Fly, IG Digital Menu Boards, Digital Marketing and DataMagine, each with its own page and collateral. Named shortfall, unchanged: Agilysys publishes no pricing or plan structure whatsoever, and independent cancellation of a module without repricing the base InfoGenesis subscription is documented nowhere. https://www.agilysys.com/en/wp-sitemap-posts-page-1.xml · retrieved 2026-08-08 adversarially verified

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

No published price exists for any hardware. The vendor's own page sitemap enumerates 117 published pages - re-verified 2026-08-04, the only pric/cost/plan/quote/hardware/buy/purchase match is the investor page /en/stock-quotes/ - and contains no hardware store, price list or purchase page; every product page terminates in 'Connect with a Hospitality Expert'. The claim's condition, purchase outright at a published price, is therefore unmet: all InfoGenesis hardware (terminals, IG KDS screens, printers) is sold quote-only. Whether a lease is mandatory is not published either way; the failing leg is the published price. https://www.agilysys.com/en/wp-sitemap-posts-page-1.xml · retrieved 2026-08-04

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

Config guide Peripherals topic names third-party devices by model. Printer Type with Use OPOS selected: Epson TM-L90, Epson TM-T70, Epson TM-T88IV, Epson TM-T88V, Epson TM-T88VI, HP A794, IBM 4610. With Share Printer selected: Epson TM-P60/P-20, Zebra Cameo, Zebra MZ-220, Zebra QL-220, Zebra RW 220. 'Use 3rd party interface' exposes com1-com32 'to be used for serial receipt printers, Bluetooth printers, or third-party interfaces such as Smart Receipt (com20)'. Cash Drawer Port, Coin Dispenser Port, Scale Port, Scanner Port and Bar Gun Port are generic com/OPOS settings, and Printer Types documents any serial or IP printer as configurable as a kitchen printer. https://ig.onagilysys.com/help/POS/IG_12UX/ConfigGuide/Peripherals.htm · retrieved 2026-08-06

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

commercial-implementation-fee-published

Enumerated Agilysys's own complete page sitemap for agilysys.com/en - all 117 pages. There is no pricing, plans, packages, implementation, onboarding or training page; the only cost-adjacent URL is /en/stock-quotes/ (investor relations). /en/pricing/, /en/plans/ and /en/cost/ each return 404. Every product page terminates in Request a Demo. No implementation, menu-build, onboarding or training fee is published as an amount, and none is stated as $0. https://www.agilysys.com/en/wp-sitemap-posts-page-1.xml · retrieved 2026-08-06

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

IG_12UX ReportsGuide 'Report Generation Overview': 'InfoGenesis POS offers comprehensive back-office reporting based on its transactional databases... InfoGenesis POS reports are printed or viewed on-screen, published with Adobe Acrobat, analyzed with Microsoft Excel, or exported to other programs for access on any personal computer.' The delivered set covers the claim's data classes - Closed Check, Check Tender Detail, Server Sales by Items Added, Clock Activity, Clock Detail, Labor Summary - and IGCM's Electronic Journal utility exports filtered check-event data (filters for check number, date range, profit center, terminal, employee, source, event name, severity) with CSV by email and PDF/Excel with headers. Report Groups can be scheduled to a destination and file type. Shortfall: every path is report- and filter-scoped - there is no documented single full-transaction-history extract, and no documented API for bulk retrieval (the developer portal returns zero APIs to anonymous callers), so 'full transactional history' is assembled report by report rather than exported. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/Report%20Generation%20Overview.htm · retrieved 2026-08-08

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

IG_12UX ReportsGuide 'Gift Card Transaction Detail Report' 'lists information for transactions by gift card... the check number, invoice number, and gift card number', with fields Check #, Invoice #, Card No, Tender Amount, Closed Date, Cashier ID, groupable and filterable and exportable to Excel/PDF like all InfoGenesis reports. Shortfall, from the same ReportsGuide book (the delivered report set for the product): there is no gift-card liability or outstanding-balance report, only transaction activity; the only loyalty ledger report, 'Loyalty Earned Transaction Detail', states 'These reports work with the Hyatt loyalty interface only and are not to be used with any other player tracking/loyalty program'; and the only guest-identified report, 'Closed Check with Guest ID', exists to carry India's PAN/FORM60 number for large cash payments, not to export a guest database. No customer/guest record export is documented. https://ig.onagilysys.com/help/POS/IG_12UX/ReportsGuide/Gift%20Card%20Transaction%20Detail.htm · 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

Agilysys's published Data Processing Agreement (dated 04-02-25, incorporated into the Terms by section 11.13), section 12 'Return and Deletion of Personal Data upon Termination of Subscription Services': '12.1 You are advised to take appropriate action to back up or otherwise store separately any Personal Data prior to the termination of the Subscription Services. You may make a written request to Agilysys for the retrieval of, or access to, your Personal Data up to ten (10) days prior to the termination of Subscription Services. 12.2 Upon termination of the Subscription Services, Agilysys will promptly delete all copies of Personal Data from the Subscription Services environment by rendering such Personal Data unrecoverable, except as may be required by law.' The only window runs backwards from termination, and the published commitment after termination is prompt deletion. https://www.agilysys.com/en/wp-content/uploads/Agilysys-Data-Processing-Agreement-04-02-25-Final.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

The published DPA (04-02-25, incorporated by Terms section 11.13) constrains use: '3.1 You are the Controller of the Personal Data provided by You to Agilysys for Processing'; '3.2 Agilysys is a Processor of the Personal Data'; Agilysys processes only on the customer's documented instructions (5.1-5.2), passes government disclosure requests back to the customer rather than answering them (13.1), and will not migrate the environment to another data-centre region 'without Your prior written authorization' (7.1). Shortfall: the DPA reaches 'Personal Data' only, not the operator's order, item and payment records; no clause in either the DPA or the Terms says the merchant owns its transaction or customer data (the Terms' Ownership clause, 2.4, assigns Agilysys ownership of the Software and Documentation and is silent on customer data); and no aggregated/de-identified-use carve-out is published in either direction. https://www.agilysys.com/en/wp-content/uploads/Agilysys-Data-Processing-Agreement-04-02-25-Final.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

Proprietary commercial software. An on-premise deployment option exists, but that is self-hosting of a closed binary, not source-available licensing. https://www.agilysys.com/en/products/infogenesis-pos/ · retrieved 2026-08-01

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

PCI-validated P2PE plus tokenization is documented and Agilysys states it reduces audit scope, but the vendor never names the resulting merchant SAQ type (SAQ A vs SAQ P2PE-HW). https://www.agilysys.com/en/products/pay/ · retrieved 2026-08-01

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

The closest first-party reference is the published DPA (04-02-25), section 10.4, which contemplates 'a SSAE 16/ISAE 3402 Type 2, ISO, NIST, PCI DSS, HIPAA or similar audit report issued by a qualified third party auditor within the prior twelve months' being supplied in lieu of a customer audit - a naming of report types, not documentation of any control. Nothing addresses PCI DSS v4.0.1 specifically: a title search of all 5,336 InfoGenesis help topics returns no PCI topic (only 'Reinit Sigcap/P2PE Function', 'Token Validation before Reopening Check' and PII-encryption release notes), agilysys.com has no security or trust page (/en/security/, /en/trust-center/ and /en/security-and-compliance/ all 404) and its WordPress search API returns nothing for PCI, SOC 2 or certification. MFA into the environment is separately documented for IGCM back-office logins via Azure AD B2C, but not framed as a Req 8.4.2/CDE control, and no payment-page script-integrity monitoring (Req 6.4.3/11.6.1) is documented for IG OnDemand's hosted checkout. Unresolved. || 323rd: 323rd: the one remaining place a PCI DSS 4.0.1 control statement could sit - the Agilysys customer community at agilysys.my.site.com - is closed to anonymous readers. / redirects to /s/login, and a guest Aura getObjectInfo (context extracted successfully from the login shell, HTTP 200, real action envelopes) returns state ERROR 'You don't have access to this record. Ask your administrator for help or to request access.' for Knowledge__kav, How_To__kav and FAQ__kav alike: the route worked and the data did not. support./community./help.agilysys.com are NXDOMAIN, and no trust or compliance surface was found on any Agilysys-owned host this pass. Retrieved 2026-09-17. || 325th: 325th: NEW SURFACE, two documents, neither a v4.0.1 control statement. Enumerating agilysys.com's WordPress media library from the Wayback CDX index (263 /en/wp-content/ documents; the REST API exposes no wp/v2 routes and wp-sitemap.xml lists no media) surfaced (1) the 2026 IG Fly sell sheet, whose only security line is 'Secure Payments - PCI-validated P2PE with EMV, NFC, and mobile wallet support ensures safe, contactless transactions while protecting cardholder data' - a P2PE validation claim on a marketing sheet that disclaims itself ('for illustration purposes only'), which speaks to cardholder-data scope reduction and says nothing about PCI DSS v4.0.1 requirements such as MFA into the CDE (8.4.2) or payment-page script integrity (6.4.3 / 11.6.1); and (2) a current third-party processor disclosure, Third-Party-Processor-List-10-2-2025.pdf, which is a privacy-law sub-processor list rather than a control description. The library contains no security white paper, no AOC, no SAQ and no trust page; the only prior-era security document in it is a 2019 magazine column (HotelOwner_Hospitality_Security_3_Tips_Dec2019.pdf). Unknown (unchanged). Retrieved 2026-09-17. || 326th: 326th: NEW SURFACE - the FY2026 Form 10-K on SEC EDGAR (filed 2026-05-21, agys-20260331.htm, 315,092 characters extracted), the first attested first-party security statement this record has held. Item 1C Cybersecurity, verbatim: 'the external auditor additionally conducts an annual payment card industry (PCI) data security standard review of our security controls that protect payment information' and 'The results of our SOC 2 and PCI assessments are annually reported to the Cybersecurity Risk Subcommittee.' That asserts a PCI DSS assessment happens; it documents no v4.0.1 future-dated control. Tokenised word-boundary case-insensitive over the 10-K: 'MFA' 0, 'multi-factor'/'multifactor' 0, '4.0.1' 0, 'script integrity' 0. Over the 117-document / 3,079,354-character live PDF library (28-sheet product-resource manifest plus 84 flat-path wp-content PDFs, including the FY23/FY24 10-Ks): 'MFA' 0, 'multi-factor' 0, 'script integrity' 0, '8.4.2' 0, '6.4.3' 0, '4.0.1' 0, 'PCI DSS' 0 - all 43 'PCI' hits across 25 documents are PCI-validated P2PE, PCI scope reduction or 'PCI-compliant tokenization' marketing on the Agilysys Pay, Authorize, IG Fly, IG Flex, IG Kiosk and IG OnDemand sheets, i.e. cardholder-data scope reduction rather than a requirement-level control. Unknown stands. Retrieved 2026-09-18. || 327th: 327th: NEW SURFACE and one new hit, which does not reach the claim. Across the FIRST body-level census of www.agilysys.com's HTML pages (prior passes read only ~9 legal pages plus the 117-document PDF library): the publisher's own page manifest https://www.agilysys.com/en/wp-sitemap-posts-page-1.xml lists 117 pages and all 117 were fetched at HTTP 200 (1,846,153 characters of stripped text); the nonsense control https://www.agilysys.com/en/zzz-nope-control-qq/ returns 404. (The WP REST API still withholds wp/v2 - /en/wp-json/ lists 68 routes in 10 namespaces, and wp/v2/types, wp/v2/media and wp/v2/solution_partner all 404 with rest_no_route, re-confirmed today.) tokenised: 'MFA' 0, 'script integrity' 0, '4.0.1' 0, '8.4.2' 0, '6.4.3' 0; 'multi-factor' scores exactly 1, on the IG Quick Pay product page - 'IT Teams: Configure customizable workflows, multi-factor authentication, and integrations with InfoGenesis POS for scalable, secure operations across properties' - a marketing bullet (grade C) that names MFA as configurable in one payment SKU but says nothing about coverage of all access to the cardholder data environment, and nothing about payment-page script integrity. 'PCI' scores 71 across 27 pages and, exactly as in the PDF library, every one is PCI-validated P2PE / PCI-compliant tokenization / PCI scope-reduction marketing. The about page's stat band adds an unsourced '100% Security Audits - SOC 2 compliant' tile, which names a report type, not a control. Unknown stands. Retrieved 2026-09-18. || 328th: MERGE HOLD (proposed partial/B, held unknown): A partial that shortfalls every conjunct is self-refuting (324th rule): the MFA found is an OPTIONAL per-customer Azure AD B2C SSO setting, never stated as covering all CDE access, with `4.0.1` 0 and script-integrity 0. The SSO topic is kept as evidence. PROPOSAL AS WRITTEN: 328th: MOVED unknown -> partial on a BODY-LEVEL re-grep of the InfoGenesis help corpus that no prior pass ran. Every previous note on this cell searched TOPIC TITLES ('a title search of all 5,336 InfoGenesis help topics returns no PCI topic'); the 5,627-topic body corpus held on disk (.cache/q316/agilysys/corpus.json, 10,620,922 characters of stripped topic text, the same union corpus the 319th used for its BYOD control) does document MFA on InfoGenesis sign-in. /IG_12UX/ConfigGuide/Single Sign On SSO.htm, verbatim: 'InfoGenesis POS can integrate with any identity provider supported by Microsoft Azure AD B2C... It allows properties to customize how their users must interact with our products when signing in (for example, MFA). Customers can also opt to enforce signed requests based on public keys', and for the Local Account method the customisable preferences are 'Is multifactor authentication required (Available options include Email, SMS and/or Phone call, Authenticator App)', 'Is reCAPTCHA required', 'Password complexity (Simple, Strong, Custom)', 'Web session timeout'. The identical topic ships in the IG_12UX, IG_Kiosk, IG_OnDemand and IG_Fly config guides. That is a vendor-documented (grade B) MFA capability covering POS and back-office sign-in, which is the first conjunct of this claim. SHORTFALLS, why this is partial and not yes: MFA is presented as a per-customer OPTION ('if customers opt for a Local Account', 'properties to customize'), never as enforced for all access to the cardholder data environment; and the second conjunct is absent - 'script integrity' 0, 'Content-Security' 0, '4.0.1' 0 across all 5,627 topic bodies, and the same three controls score 0 across the 117-document/3,079,354-character PDF library and the 117-page www.agilysys.com body census read in the 326th/327th. Agilysys nowhere cites PCI DSS v4.0.1 or its requirement numbers; the only 'PCI DSS' hit in the whole help corpus is a 12.3.13.5 release note, 'Agilysys Pay Global Payments is certified by the Payment Card Industry Data Security Standard (PCI DSS)'. Retrieved 2026-09-18. || 334th: NEW SURFACE (334th): the Agilysys Knowledge Center's InfoGenesis training courses are Supademo interactive walkthroughs of the live product, never opened by a prior pass (prior passes read only the course TITLES on /en/knowledge-center/). The three InfoGenesis course pages (https://www.agilysys.com/en/knowledge-center-videos/?course=<base64 title>: Back of House for Menu, Inventory and Admin Setup; Front of House for Ordering, Payments and Guest Service; Reporting) link 318 distinct demos, and all 318 were fetched anonymously at HTTP 200 from app.supademo.com/demo/<id>; each page embeds its full step list (narration 'audioText', on-screen callouts, screenshots) in the Next.js flight payload: 17,548 text fields, 780,574 characters, 7,219 screenshots. Vendor-authored tutorials walking the actual IGCM / POS terminal UI (grade B as documentation of what they show; a training set, not a census of the product). The login walkthrough itself, 'Logging on to IGCM' (https://app.supademo.com/demo/cm98lg4mo0sj1pxcbcrmxk0pu, updated 2026-09-09), is organisation name -> 'Proceed' -> email -> password -> 'Sign in' -> 'You have now successfully logged in to IGCM' with no second factor, and 'Creating a User' (cmipoyszc2801gxad3fpani0j) sets email, name, password and roles with no MFA enrolment. MFA vocabulary ('MFA|multi-factor|two-factor|2FA|OTP|verification code|authenticator') scores 4 hits in 2 demos, all POISON: GA/tender 'verification code' on donations and foreign-currency tenders. 'PCI' 0. This agrees with the 328th hold (MFA is an optional per-customer Azure AD B2C setting) and adds that the vendor's own current training shows back-office login without MFA; still no v4.0.1 statement, so unknown (a login demo is not a published control statement, and the vendor's community KB is login-gated). Retrieved 2026-09-18. adversarially verified

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

Agilysys's published DPA (04-02-25, incorporated into the Terms by section 11.13) commits to supplying third-party audit reports in lieu of a customer audit: '10.4 If the requested audit scope is addressed in a SSAE 16/ISAE 3402 Type 2, ISO, NIST, PCI DSS, HIPAA or similar audit report issued by a qualified third party auditor within the prior twelve months and Agilysys provides such report to You confirming there are no known material changes in the controls audited, You agree to accept the findings presented in the third party audit report in lieu of requesting an audit of the same controls covered by the report.' The report is supplied under the Agreement's confidentiality regime (Terms section 8), and section 10 also grants a customer audit right on 30 days' notice. Shortfall: the clause is conditional and names report families generically - Agilysys nowhere states affirmatively that it currently holds a SOC 2 Type II or ISO 27001 attestation, there is no trust centre or security page (agilysys.com/en/security/ and /en/trust-center/ both 404), and SSAE 16/ISAE 3402 is the superseded predecessor of SSAE 18 SOC 2. https://www.agilysys.com/en/wp-content/uploads/Agilysys-Data-Processing-Agreement-04-02-25-Final.pdf · retrieved 2026-08-08

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 of the claim is fully met: a Data Processing Agreement dated 04-02-25 is published at agilysys.com/en/dpa/ and incorporated into the standard Terms by section 11.13. Product-side, IG_12UX ConfigGuide 'Customer PII Data Deletion for Privacy Compliance' lets properties 'enable privacy compliance laws at the enterprise level and select the applicable regulation CCPA or GDPR', after which 'customer PII data is retained in the check JSON file only for the configured retention period after the check reaches Completed status' and is then deleted automatically. Shortfall: that is retention-based bulk purge, not per-individual DSAR tooling. The DPA's own wording is conditional - '6.1 If possible, Agilysys will grant You electronic access to Your Subscription Services environment that holds Personal Data to enable You to respond to requests from Data Subjects' - and 6.2 falls back to 'submit a service request via MyAgilysys Support Portal... the parties will negotiate in good faith with respect to any charges or fees'. IG OnDemand's UserGuide is blunter still: 'All transactional data used in IG OnDemand will always be saved. To remove any saved guest details, properties must contact Agilysys.' No consent ledger export or in-app locate/export of one guest's records is documented. https://www.agilysys.com/en/wp-content/uploads/Agilysys-Data-Processing-Agreement-04-02-25-Final.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

No VPAT or accessibility conformance report is published, and the IG Kiosk and IG PanOptic Kiosk pages are entirely silent on ADA/WCAG and on any tactile/audio non-visual access mode — a notable gap for a vendor selling unattended kiosks into US hotels, stadiums and airports. https://www.agilysys.com/en/products/ig-kiosk/ · retrieved 2026-08-01

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

Surcharging is documented, twice. IG_12UX release note 'Adyen Surcharge Support': 'the surcharge is configured in the Adyen portal and based on the card type that the guest presents, POS terminal calculates the surcharge and displays the confirmation screen with the total transaction amount (purchase amount, tip, and surcharge)', with an explicit Supported Parameters table - Devices Verifone P400 Plus/V400C Plus/e285; Industry Types Food and Beverage, Retail; Card Entry Modes Tap, Chip, Swipe; Card Types 'Credit'; Region 'Australia'; Transaction Type 'Pay at counter'. IG OnDemand's 'Surcharge Calculation Enhancements' adds a configurable Surcharge Percentage at enterprise/store/tender level with Blended Tax handling and Terminal Option 1396, but 'is applicable only for DataCap credit card transactions'. Shortfall: the supported-parameters table restricts the Adyen path to credit cards in Australia at the counter; debit and prepaid exclusion is a consequence of that scoping rather than an automatic documented rule; no cash-discount or dual-price mode is documented; and no receipt or menu-board fee-disclosure behaviour is described in either topic ('the surcharge added to a transaction cannot be removed in POS terminal'). https://ig.onagilysys.com/help/POS/IG_12UX/ReleaseNotes/Adyen%20Surcharge%20Support.htm · retrieved 2026-08-08