Agilysys

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-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

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

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

order-capture-bar-tab-preauth differentiator

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

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

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

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

order-capture-qr-same-check differentiator

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

order-capture-kiosk-first-party differentiator

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

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

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

order-capture-voice-ai differentiator

Walked the whole InfoGenesis help system TOC on 2026-08-08 (ig.onagilysys.com/help/POS/<PRODUCT>/Data/Tocs/MasterTOC*.js, 5,336 topics across IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB and IGCM): zero topics match voice, speech recognition, conversational or drive-thru. The only speech-related topics are IG Kiosk ADA text-to-speech (/IG_Kiosk/UserGuide/ADA%20Mode%20Text%20to%20Speech%20Support.htm), which is output, not ordering. A POS API does exist (IG_12UX/ConfigGuide/POS%20API%20Configuration.htm, API%20Registration.htm, IG_Fly/ConfigGuide/API%20Client.htm, and the agys-dev.developer.azure-api.net portal), but nothing in it is presented as a voice-AI partner program. Left unknown rather than no because a help system for shipped features is not an enumeration of partner programs, and www.agilysys.com marketing does reference AI Guest Intelligence.

order-capture-throttling differentiator

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

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

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

order-capture-order-ready-signal differentiator

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

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

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

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

menu-pricing-fractional-placement differentiator

Searched all 5,336 help topics on ig.onagilysys.com plus the 1,448-topic eatec-userguide.onagilysys.com TOC on 2026-08-08 for half, portion, fraction, side and placement: the only hit is IG_KDS/UserGuide/Prepare%20Portions%20of%20Item%20Across%20Multiple.htm, which is prep routing, not pricing. Read the item pricing surface directly - IG_12UX/ConfigGuide/Price%20Information.htm (Price Levels, Store Price Levels, Quantity Category, Default), Quantity%20Category.htm and Modifier%20Price%20Tier%20Level.htm: the only portion-like construct is a quantity category with a Price Multiple, which scales a whole item by size and is limited to one per item ("A quantity-based modifier is already applied towards the item. Only one can be applied at a time"). No sectioned placement with independent per-section pricing appears. Not scored no because the ConfigGuide Modifier and Choice Group topics are stubs that do not publish their field lists, so the modifier form's full configurable surface is unread.

menu-pricing-half-and-half-rule differentiator

This is downstream of fractional placement, which is itself undocumented (see menu-pricing-fractional-placement). Checked IG_12UX/ConfigGuide/Price%20Information.htm, Item%20Price%20Tier%20Level.htm, Modifier%20Price%20Tier%20Level.htm, Quantity%20Category.htm and Schedule%20Price%20Change.htm on 2026-08-08: item pricing is base price by price level and price tier, plus a single quantity-category multiplier; there is no rule selector for how a shared item is priced (higher half, average, fraction per topping). A TOC sweep of all 5,336 InfoGenesis topics returns no topic containing half. Left unknown rather than no because no published screen enumerates the pricing-rule options as a closed set.

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

menu-pricing-size-style-matrix differentiator

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

menu-pricing-included-allowance differentiator

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

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

menu-pricing-upsell-prompts differentiator

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

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

menu-pricing-countdown-auto-86 differentiator

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

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

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

menu-pricing-dual-pricing differentiator

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-pricing-versioning-effective-dates differentiator

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

menu-pricing-franchise-hierarchy differentiator

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

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-pricing-recipe-linkage differentiator

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

menu-pricing-3p-menu-push

Swept the entire InfoGenesis help TOC (5,336 topics, all seven products) on 2026-08-08 for DoorDash, Uber, Grubhub, marketplace, third party and delivery partner: no marketplace name appears anywhere, and the only delivery topics are IG OnDemand's own Delivery Fulfillment Type and IG Fly's delivery-detail capture. Read IG_12UX/12.3.15_RN/Additional%20Integrations%20Enabled.htm, which lists the integrations moved onto Integration Application Services (Eatec, IGT, Light & Wonder Envoy CMP, Light & Wonder Envoy ACSC) - a partial migration list, not a catalogue. Menu management is entirely IGCM-side (Item, Screen, Price Tier menus) with no channel sync-status or rejection-error screen. Left unknown rather than no because that IAS list is explicitly incremental ("with each release, more integrations are being transitioned") and so is not an exhaustive enumeration of Agilysys integrations.

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

payments-processor-choice differentiator

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

payments-published-rates differentiator

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

payments-dual-pricing differentiator

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

payments-surcharge-guardrails differentiator

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

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

payments-softpos-tap-to-pay differentiator

"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

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

payments-qr-guest-pay differentiator

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

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

payments-tip-pooling differentiator

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

payments-offline-store-and-forward differentiator

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

payments-offline-decline-liability differentiator

No public Agilysys document addresses who bears loss on a post-reconnect decline, nor any failed-offline-payment report.

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

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

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

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

payments-chargeback-tooling differentiator

Swept all 5,336 InfoGenesis help topics on 2026-08-08 for chargeback, dispute, representment, retrieval request and reversal: zero hits. Read the two nearest surfaces directly - IG_12UX/ConfigGuide/Settlements.htm (a settlement-status utility listing ID, Tendered Time, Check Number, Amount, Status, Account Number, Tip, Tax, Tender Id, Terminal ID, Profit Center, Meal Period ID, Cashier ID, Merchant ID) and the ReportsGuide books (~490 topics across four products), whose card-related reports are Credit Card Exception, Refund Return Void Detail/Summary and PMS Settlement Status - none of them a dispute queue or evidence-submission workflow. Left unknown rather than no because Agilysys Pay runs on Adyen, Tyro and FreedomPay gateways whose own merchant back offices are outside this help system and were not reachable.

payments-card-on-file differentiator

Re-checked on 2026-08-08 against the help system rather than the Pay marketing page an earlier verifier read. A TOC sweep of all 5,336 topics for card on file, stored credential, saved card, wallet and recurring returns: IG_OnDemand/ConfigGuide/Wallet%20Payment.htm (a menu for configuring wallet payment methods, no stored-PAN semantics), IG_OnDemand/12.3.15_RN/Display%20Saved%20Account%20Details.htm (a card-VIEW layout toggle for saved discount/GA account lookups, not a stored payment credential), and Octopus stored-value card integration. IG OnDemand guest accounts are documented with OTP verification and saved preferences but never with a reusable payment token shared across online, phone and in-store. Unknown, not no: the P2PE/tokenization the Pay page describes could underpin a stored credential that simply is not written up in the POS help system.

payments-payout-timing differentiator

Found the nearest first-party statement and it is about capture, not funding: IG_12UX/ReleaseNotes_12.3.13/Agilysys%20Pay%20Adyen%20Authorization.htm (Scheduled Captures, Settlement Delay) says Adyen.ImmediateSettlement defaults true so pay-at-counter and pay-at-table sales "are settled immediately upon completion" and authorizations settle shortly after the closed check uploads; set false, "the customer must contact Adyen to schedule the daily batch settlement time". That is the merchant-to-gateway capture schedule. Nothing in the 5,336-topic help system, the Settlements utility or the ReportsGuide books states a deposit/funding schedule to the merchant's bank account, and no next-day or instant-funding option is offered; www.agilysys.com/en/products/pay/ describes P2PE, EMV and scope reduction only. Unknown because funding terms for a quote-only enterprise processor are normally contractual and unpublished, which is not evidence they do not exist.

payments-multi-entity-routing differentiator

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

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

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

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

kitchen-course-firing differentiator

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

kitchen-prep-time-pacing differentiator

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-order-throttling differentiator

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

kitchen-channel-pause-propagation differentiator

Re-walked ig.onagilysys.com/help/POS on 2026-08-08 against the cached master TOCs for all seven products (IG_12UX 1,688 topics, IG_Kiosk 1,213, IG_OnDemand 902, IG_Fly 802, IG_KDS 582, IG_DMB 59, IGCM 90). A regex sweep of every topic path and title for DoorDash, Uber, Grubhub, Olo, marketplace, third-party and 3rd returns zero marketplace topics. IG KDS /UserGuide/Highlight and Display Order Source in Expo Chit.htm enumerates the order sources the kitchen can show as 'InfoGenesis POS Terminal 12UX, IG Kiosk, IG OnDemand, and IG Fly' - all first-party. 86/un-86 propagation IS documented, but only inward across Agilysys surfaces (IG_OnDemand /UserGuide/Sync 86 Un86 Status from Item Countdown Menu in IGCM.htm; terminal options 290/293/530/1314). The only acknowledgement of external channels anywhere is a report field in IG_KDS /ReportsGuide/Kitchen Reports.htm that defines Source as 'Cloud orders - OnDemand and third-party orders', which names no channel and describes no outbound pause. Absence of any documented marketplace connection, not documented absence.

kitchen-order-ready-callback differentiator

IG KDS /UserGuide/Update Kitchen Order Status in IG OnDemand.htm (retrieved 2026-08-08) shows a real order-ready callback exists: on 'Order bumped', 'Order delivered', 'Order confirmed by the kitchen' and ten other Master Expo transitions the status is sent out of KDS - but the documented recipient is IG OnDemand, Agilysys's own ordering front end, and the topic says the feature 'is applicable to the whole order and not for specific items'. Nothing in the 5,336-topic help system (checked across all seven product TOCs for DoorDash/Uber/Grubhub/Olo/marketplace/third-party) documents a courier-dispatch callback to a third-party marketplace, and the Agilysys developer portal at agys-dev.developer.azure-api.net exposes no API catalogue anonymously (its own management endpoint /apis?api-version=2022-04-01-preview returns {"value":[],"count":0}), so a webhook could exist behind the sign-in wall. Unresolved rather than absent.

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

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

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

kitchen-printer-fallback differentiator

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

kitchen-offline-operation differentiator

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

kitchen-item-build-screens differentiator

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

kitchen-pizza-fractional-display differentiator

Regex-swept all 5,336 topic paths and titles across IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB and IGCM on 2026-08-08 for pizza|half|fraction|portion|section. Two candidates, both read in full and neither on point: IG_KDS /UserGuide/Prepare Portions of Item Across Multiple Stations.htm is prep routing ('An item can be split into multiple portions. Each portion can be routed to different kitchen departments and stations'), with no notion of a spatial section of the item; IG_12UX /UserGuide/Quantity Based Modifiers.htm uses pizza only as a SIZE example ('if Pizza is added to the check and the guest wants to modify the portion size from Standard to Large'), alters quantity and price, and permits only one such modifier per item. The 12UX modifier configuration surface (ConfigGuide Modifier, Modifiers, Modifier Price Tier Level, Show Modifiers, Printing Modifiers, Assign Sizeable Modifiers to Choice Group) was listed but its field tables were not read exhaustively, so a half/section attribute cannot be positively excluded. Agilysys sells into hotels, casinos, cruise and campus rather than pizza QSR, which makes silence unsurprising but is not evidence.

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

kitchen-order-modification-alerts differentiator

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

kitchen-guest-ready-notification differentiator

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

kitchen-waste-logging

Two systems checked on 2026-08-08. (1) Eatec (eatec-userguide.onagilysys.com, 1,448 topics walked via Data/Tocs/MasterTOC_Chunk0-6.js) does have the workflow the claim's second half needs: /UserGuide/Creating Spoilages and Loss.htm is reached at Inventory Management > Spoilage and Loss and carries a Reason drop-down ('The cause of spoilage'), Location, Post Date, Department, item list and Post Spoilage, with /NewFeatures/Inventory Depletion by Spoilage for Configured Location.htm and reports Spoilage/Loss Detail [INV61], Spoilage/Loss Summary [INV61S] and Usage Detail by Item/Sort by Waste [INV03D]. (2) But the claim requires entry 'directly at the kitchen/KDS screen'. A regex sweep of all 582 IG KDS topic paths and titles for waste|spoil|remake|reason returns nothing, and the documented KDS operator action set (bump-bar keys Expand, Cook, Bump, Recall, Priority, Print; chit and item bump/reopen) contains no waste function. The Eatec Mobile app exists but is documented for receiving, transfers and physical counts, not KDS-side waste. So the mechanism exists in the back office and is undocumented at the kitchen screen - not positively excluded there.

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

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

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

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

delivery-route-map differentiator

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

delivery-driver-tracking differentiator

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-zones-polygon differentiator

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

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

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

delivery-driver-comp differentiator

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

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

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

delivery-daas-fallback differentiator

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

delivery-3p-direct-integration differentiator

No first-party DoorDash/Uber Eats/Grubhub certified integration is published. The listed ordering partners are Olo, Crave and Tapingo — third-party ordering middleware. https://www.agilysys.com/en/solution-partners/ · retrieved 2026-08-01

delivery-3p-injection

Checked on 2026-08-08 across all seven POS help sets (5,336 topics) plus the developer portal. Evidence pulls both ways and settles nothing. FOR: IG_KDS /ReportsGuide/Kitchen Reports.htm defines the Source field of KDS Estimated vs Actual Order Detail as 'OnPrem orders - Kiosks and IG terminals' and 'Cloud orders - OnDemand and third-party orders', so third-party orders are a recognised order class reaching the kitchen. AGAINST: IG_KDS /UserGuide/Highlight and Display Order Source in Expo Chit.htm enumerates the sources the expo can display as 'InfoGenesis POS Terminal 12UX, IG Kiosk, IG OnDemand, and IG Fly' - no marketplace; a regex sweep of every topic path and title for DoorDash|Uber|Grubhub|Olo|marketplace|third-party returns zero topics; and /IG_12UX/12.3.15_RN/Additional Integrations Enabled Through IAS.htm lists the integrations moving onto the Integration Application Services bus as Eatec, IGT, Light & Wonder Envoy CMP and Light & Wonder Envoy ACSC - casino and inventory, no delivery aggregator. The API surface that would carry an injection endpoint (agys-dev.developer.azure-api.net) publishes nothing anonymously: its portal management endpoint /apis?api-version=2022-04-01-preview returns {"value":[],"count":0} and the catalogue sits behind sign-in. Neither auto-injection nor a manual-accept requirement can be established.

delivery-menu-push

Re-evidenced 2026-08-08, withdrawing the earlier unverified aside about Olo/Crave APIs. The 747-topic IGCM Configuration Guide holds the master menu (items, modifiers, price tiers, day-part and screen schedules) but contains no channel, marketplace or menu-publishing target, and no channel-specific price markup construct. Agilysys' Solution Partners directory places Online Mobile Ordering with third parties (OLO, Ssnapp, Tapingo), so any marketplace menu is maintained in the partner's portal. https://ig.onagilysys.com/help/POS/IG_12UX/Sitemap.xml · retrieved 2026-08-08 adversarially verified

delivery-86-sync

Re-evidenced 2026-08-08. InfoGenesis does document 86ing - 'Manage 86' in the ConfigGuide, '86 Un86 Item', '86 Un 86 Modifier' and 'Indicate Local 86 or Un86' in the UserGuide, and 'Display Details of 86d Items' in the release notes - so item and modifier out-of-stock exists. What is absent is any push: no third-party channel, marketplace or partner-availability topic appears in the 1,691-topic set, and the availability state is described as local/enterprise only. https://ig.onagilysys.com/help/POS/IG_12UX/Sitemap.xml · retrieved 2026-08-08 adversarially verified

delivery-store-pause

Re-evidenced 2026-08-08. No topic in the 1,691-topic InfoGenesis help set concerns pausing, deactivating or reactivating a store on an external ordering channel; the documented store-level controls are profit centre, day-part and terminal configuration. With Online Mobile Ordering delegated to partners (OLO, Ssnapp, Tapingo) per Agilysys' Solution Partners directory, marketplace availability is managed in the partner's portal, not the POS. https://ig.onagilysys.com/help/POS/IG_12UX/Sitemap.xml · retrieved 2026-08-08 adversarially verified

delivery-3p-reconciliation differentiator

Re-evidenced 2026-08-08. 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; there are no marketplace channels in the documentation to reconcile. https://ig.onagilysys.com/help/POS/IG_12UX/Sitemap.xml · retrieved 2026-08-08 adversarially verified

delivery-injection-error-visibility differentiator

Re-evidenced 2026-08-08 with a correction: Agilysys does publish integration-health reporting - the ConfigGuide has Interfaces, Interface Server and Interface Resources, and the ReportsGuide has an Interfaces report, Posting Status Report, Posting Detail Report and a Posting Error Report for Opera. All of it covers PMS/casino/payment interfaces. There is no third-party order channel in the 1,691-topic documentation set, so no failed or rejected order injection, per-channel connection status, or channel failure alert is exposed. https://ig.onagilysys.com/help/POS/IG_12UX/Sitemap.xml · retrieved 2026-08-08 adversarially verified

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

delivery-promise-time differentiator

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

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

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

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

digital-native-app differentiator

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

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-upsell-engine differentiator

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

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

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

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

digital-kiosk differentiator

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

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

digital-catering-portal differentiator

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

digital-voice-ai-phone differentiator

Re-walked ig.onagilysys.com/help/POS on 2026-08-08 using the cached master TOCs for all seven products (5,336 topics). The only AI-assistant topic in the corpus is /IGCM/12.3.15_RN/AI Chat Assistant for IGCM (Mobile View).htm, which is an administrator aid inside the configuration manager, not a guest ordering channel. The documented order sources are enumerated by IG_KDS /UserGuide/Highlight and Display Order Source in Expo Chit.htm as 'InfoGenesis POS Terminal 12UX, IG Kiosk, IG OnDemand, and IG Fly' - no telephone channel. No named voice-AI partner appears in the IAS integration list (/IG_12UX/12.3.15_RN/Additional Integrations Enabled Through IAS.htm: Eatec, IGT, Light & Wonder Envoy CMP, Light & Wonder Envoy ACSC). www.agilysys.com marketing was not re-read because a marketing mention could not carry a yes on a differentiator anyway. Since the order-source list is a display enumeration rather than a statement of supported channels, this is undocumented rather than excluded.

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

digital-sms-ordering

Read /IG_12UX/ConfigGuide/SMS Configuration.htm in full on 2026-08-08. The configured surface is strictly outbound: a Country Code, an SMS Body of up to 918 characters, and a fixed Legends token set - [SN] Store Name, [PC] Profit Center Name, [D] Check Closed Date Time, [CN] Check Name, [GT] Grand Total, [RT] Receipt Text - with providers set up 'in the following two ways': the customer's own Twilio account, or Agilysys-brokered Twilio sub-account / Open Market / Vonage. There is no inbound keyword, reply-handling or session construct on that screen. The other SMS topics in the corpus are all one-way as well: Send Receipt PDF as Link in Order Confirmation Email and SMS, Email and SMS Receipts, Send Item and Modifier Details Only in SMS and Email Receipts, IG_KDS Configure SMS Notification Failed/Cancelled Orders and Email/SMS Notification when Order Moves to Open Order Tab, and IG_OnDemand Guest Consent for Receiving SMS. Ordering is reached by QR code and link into the OnDemand browser flow instead. A text-a-link flow could be assembled from these parts by an operator, but no conversational or text-to-order capability is documented, so this is unresolved rather than excluded.

digital-google-order differentiator

Re-walked ig.onagilysys.com/help/POS on 2026-08-08 (the site was restructured to /help/POS/<PRODUCT>/ since the earlier pass) and re-swept all 5,336 topic paths and titles across IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS, IG_DMB and IGCM for google|business profile|local listing. The only Google reference remains OnDemand social sign-in (Google, Facebook, LinkedIn); there is no Google Business Profile, local-listing or ordering-link provisioning topic. IG OnDemand ordering is provisioned instead by QR code and URL (/IG_OnDemand/UserGuide/Generate QR Code for Site Entity in Pickup and Delivery Logistics.htm), and an operator can paste such a link into their own Business Profile without any vendor feature. Absence of documentation, not documented absence - the prior rationale reached the right conclusion and is preserved.

digital-apple-business-connect

Re-swept all 5,336 topic paths and titles across the seven product TOCs at ig.onagilysys.com/help/POS on 2026-08-08 for apple|maps|business connect|order food: the hits are payment-only - /IG_12UX/12.3.15_RN/Apple Tap to Pay on iPhone.htm, /IG_12UX/UserGuide/Apple Tap to Pay on iPhone.htm, and the Wallet Payment configuration topics in 12UX/Kiosk/OnDemand. The iTunes lookup API for Agilysys NV, LLC (queried the same day, 22 apps) shows the vendor's Apple-ecosystem presence is staff apps, payment utilities and the brandable Guest App - nothing referencing Apple Business Connect or a Maps place-card action. As with Order with Google, an operator can register an Apple Business Connect 'Order Food' action pointing at an OnDemand link entirely outside the product, so vendor silence is not evidence either way.

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

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

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

digital-guest-data-ownership differentiator

Located and read the governing topic on 2026-08-08: IG_OnDemand /UserGuide/Data Privacy and Consent Management.htm, which 'outlines how IG OnDemand manages guest data and communication preferences ... how guest information is collected and managed, and how guests can give or withdraw their consent'. It states 'All transactional data used in IG OnDemand will always be saved. To remove any saved guest details, properties must contact Agilysys', and enumerates only two supported features: Guest Consent for Receiving SMS, and Remove Saved Preferences. The sibling ConfigGuide topic /Customer PII Data Deletion for Privacy Compliance.htm covers automatic retention-period purging of PII from the check JSON under a CCPA or GDPR setting. Neither says anything about the operator OWNING guest records or being able to bulk-export them, and the only bulk export documented anywhere in the corpus is IGCM enterprise configuration export (/IG_12UX/12.3.15_RN/Scrub Personal Information during Enterprise Export and Import.htm), which covers EMPLOYEE PII fields (emp_name, emp_SSN, emp_tel...) and not guest records. The Loyalty & Promotions and Digital Marketing SKUs, which hold the guest database, publish no documentation at all. Directionally unfavourable but not a positive statement about export, so unknown.

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-surcharge-transparency differentiator

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

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

guest-loyalty-thirdparty-identity-attach differentiator

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

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

guest-loyalty-tiers differentiator

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

guest-loyalty-offline-behavior differentiator

Swept all 5,336 topics for offline|standalone|store-and-forward on 2026-08-08 and read the substantive ones. /IG_12UX/UserGuide/Go Offline.htm: the terminal can be taken offline manually or drops offline on a network error; 'When the terminal is offline, none of the reports are generated. The user cannot clock out or clock in ... Most of the terminal functions cannot be performed' - suggestive, but it does not name loyalty. /IG_12UX/UserGuide/Global Application Service (GAS) Offline Scenarios.htm specifies offline behaviour for 86/un-86 only (local 86 icon, manual re-86 required after reconnect). /IG_12UX/ConfigGuide/Offline Configurations.htm exposes just two fields, 'Offline user max limit' and 'Offline check limit'. The rest are payment- or kitchen-scoped: Offline Support for Atrium Tenders, Configure Offline Tender Limit for Atrium Campus Cards, Offline Kitchen Printing, Offline Kitchen Video, IG_KDS Support for Kitchen Printer when Terminal is Offline, IG_Fly Build Offline Orders during Connectivity Disruption, and four IG Kiosk offline topics including Support Offline Payments (Credit Cards). Agilysys Loyalty & Promotions is a server-side service reached over the network (its POS-side topics are all live member lookups and tender authorisations) so degradation is likely, but no topic states what lookup, accrual or redemption do while disconnected, and the Loyalty & Promotions SKU publishes no documentation of its own.

guest-loyalty-offer-stacking-rules differentiator

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

guest-loyalty-targeted-offers differentiator

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

guest-loyalty-rfm-segmentation differentiator

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

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

guest-loyalty-native-email-sms differentiator

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

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

guest-loyalty-10dlc-registration

Read /IG_12UX/ConfigGuide/SMS Configuration.htm end to end on 2026-08-08 (the same topic exists in the Fly, Kiosk and OnDemand ConfigGuides). It states 'SMS communication can be set up in the following two ways': integrate the customer's existing Twilio account directly within InfoGenesis, or use Agilysys, which 'requires customers to contact Agilysys for setup' via a Twilio sub-account created for the customer, Open Market (customer shares username, password and sending mobile number) or Vonage/Nexmo (API key, API secret, sending number). The configurable fields are Country Code, SMS Body, Legends tokens, SMS_Provider and SMS_Provider_Configuration, with billing settable per store or per enterprise. Nowhere in that workflow, nor anywhere else in the 5,336-topic corpus (swept for 10DLC|A2P|campaign registration|brand registration|carrier), is A2P 10DLC brand or campaign registration mentioned. The bring-your-own-carrier-account model implies the operator registers at the carrier, but that is inference about an undocumented step rather than a documented vendor position, so the claim's 'handles or explicitly documents' test is unresolved, not failed.

guest-loyalty-campaign-attribution differentiator

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

guest-loyalty-data-export-portability differentiator

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

guest-loyalty-cdp-event-api differentiator

Probed the Agilysys API surface directly on 2026-08-08. agys-dev.developer.azure-api.net is a live Azure API Management developer portal (/internal-status-0123456789abcdef returns PortalVersion 20250219080853, CodeVersion 20260603194926) whose landing page says only 'Agilysys has a broad collection of partners and APIs to help you assemble the perfect solution for you. Sign in to learn more.' Its /config.json exposes the backing management endpoint, and querying that catalogue anonymously - agys-dev.management.azure-api.net/.../apis?api-version=2022-04-01-preview - returns {"value":[],"count":0}: the entire API catalogue is behind authentication, so neither the presence nor the absence of a guest/order event stream can be read from it. developer., docs., support. and help.agilysys.com do not resolve. Inside the product, the only API construct documented is inbound configuration: /IG_12UX/ConfigGuide/POS API Configuration.htm has just two fields, 'POS API Reload Config URL' and 'POS API Subscription Key' (an APIM subscription key), plus /ConfigGuide/API Registration.htm. The one documented outbound status stream, IG_KDS /UserGuide/Update Kitchen Order Status in IG OnDemand.htm, is a fixed internal feed to Agilysys's own ordering app with no subscriber model. No webhook, no event schema, no CDP partner named.

guest-loyalty-review-capture-routing differentiator

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

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

guest-loyalty-wallet-pass differentiator

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.

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

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).

guest-loyalty-ai-offer-recommendation differentiator

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

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

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

labor-photo-punch-verification differentiator

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

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

labor-offline-time-punch differentiator

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

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

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

labor-native-scheduling differentiator

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

labor-demand-labor-forecast differentiator

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

labor-realtime-labor-percent differentiator

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

labor-overtime-prevention differentiator

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

labor-break-compliance-by-state differentiator

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

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

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

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

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

labor-qualified-tips-w2-reporting differentiator

Enumerated the entire IG_12UX Reports Guide book (the delivered back-office report set, 122 topics) on 2026-08-08 rather than relying on search vocabulary. The tip-related reports are IRS Tips Report, IRS Tips and Gratuity, Server Shift Sales Tips and Gratuities Report, Tip Transfer Detail Report and Gratuity and Service Charge Summary; the labor reports are Labor Summary Report, Clock Activity Report, Clock Detail Report, Current Clock-In Report and Temporary Employee Card Assignment Report. None is a payroll export format, and the audit finding of 2026-08-05 stands: the IRS Tips Report does separate Charged Tips from Declared Cash Tips per employee with Charged Tips/Grats Sales and Ratio columns. But no report or configuration topic in any of the seven help sets mentions a Treasury tipped-occupation code, W-2, Box 12, Box 14 or code TP, and /IG_12UX/ReportsGuide/Report Generation Overview.htm describes output as Acrobat, Excel or 'exported to other programs' - a generic report export, not a structured payroll interchange. Payroll itself is handled by integration (/IG_12UX/ReleaseNotes/InfoGenesis POS Integration with 7shifts.htm), whose field mapping is not published. TY2026 Box 12 code TP / Box 14b support can therefore be neither affirmed nor positively excluded; it could sit in the 7shifts interface spec or in release notes issued after 12.3.15.

labor-native-payroll differentiator

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

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

labor-shift-swap-workflow differentiator

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

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

labor-server-performance-metrics differentiator

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

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

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

inventory-theoretical-vs-actual differentiator

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

inventory-realtime-depletion differentiator

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

inventory-86-auto-sync differentiator

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

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

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

inventory-vendor-catalogs-edi differentiator

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

inventory-invoice-ocr differentiator

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

inventory-price-change-alerts differentiator

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

inventory-par-auto-suggest differentiator

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

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

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

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

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

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

inventory-bar-partial-bottle

Walked eatec-userguide.onagilysys.com for the first time on 2026-08-08 (1,448 topics recovered from Data/Tocs/MasterTOC_Chunk0-6.js: NewFeatures 608, UserGuide 542, ReportsGuide 254, plus three release-note books) and swept every path and title for scale|weigh|bottle|liquor|bar|beverage|wine|keg|pour|ounce|tenth|partial. The hits are all adjacent, none on point: /UserGuide/Unit Conversions.htm is a generic Setup > Global > Unit > Unit Conversions table (Conversion value, From Unit, To Unit, Source, Is Active) with no beverage semantics; Enabling Catch Weight for F&B Inventory Items, for Supplier Bids and in Eatec Mobile handles variable-weight receiving of items such as butchery cuts, not depletion of an opened bottle; /NewFeatures/Scale Quantity and Units to Chef Friendly Quantity and Units.htm is recipe display scaling; Differentiating UOM for Physical Inventory addresses count units generally; and Reverse Transfer Quantities (Partial Transfer Reversal) is unrelated. No topic anywhere documents a bench-scale or weight-device integration, a tenths/fraction-of-bottle count unit, or per-ounce pour costing. Physical-inventory count screens were listed but their field tables were not read exhaustively, so a fractional count unit cannot be positively excluded - and Agilysys sells heavily into casino and resort bars, which makes a wholly absent capability less likely than an undocumented one.

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-native-not-partner differentiator

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

inventory-menu-margin-linkage differentiator

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

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

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

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

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

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

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

reporting-server-scorecards differentiator

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

reporting-channel-profitability differentiator

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

reporting-multiloc-drilldown differentiator

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

reporting-custom-report-builder differentiator

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

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

reporting-raw-warehouse-export differentiator

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

reporting-public-api differentiator

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

reporting-webhooks differentiator

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

reporting-api-not-upcharged differentiator

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

reporting-tier-paywall differentiator

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

reporting-history-retention differentiator

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

reporting-anomaly-alerts differentiator

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

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

reporting-guest-cohorts differentiator

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

reporting-sales-forecast differentiator

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

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

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

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

multi-location-local-override-policy differentiator

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

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

multi-location-scheduled-publish differentiator

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

multi-location-new-store-template differentiator

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

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

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

multi-location-royalty-calculation differentiator

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

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

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

multi-location-normalized-item-rollup differentiator

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

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

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

multi-location-multi-brand differentiator

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

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

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

multi-location-config-audit-log differentiator

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

multi-location-enterprise-sso differentiator

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

multi-location-enterprise-api differentiator

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

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

hardware-commodity-devices differentiator

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

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

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

hardware-handheld-battery-swap differentiator

Checked the IG Fly help system (802 topics) - Supported Devices and Gateways gives the complete handheld matrix (Shift4: PAX A800, PAX M8; Planet: PAX A920 Pro, PAX A77; Adyen: Castles S1F2; FreedomPay and Elavon: Castles S1F4 Pro; plus ELO M60) and every one is a third-party payment terminal whose battery is specified by its manufacturer, not by Agilysys. The only battery topic in all 5,336 InfoGenesis topics is UserGuide 'CC Battery %' (function #2083), which 'displays battery percentage for Moby 5500 payment device and indicates its low battery status', iOS/Bluetooth only. No Agilysys page states a rated shift battery life or a hot-swap/field-replaceable battery for any supported handheld, and agilysys.com/en/products/ now 301s to the homepage so the old IG Fly marketing wording could not be re-read at its cited URL.

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

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

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

hardware-kiosk differentiator

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

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

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

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

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

hardware-tap-to-phone differentiator

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-pricing-transparency differentiator

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-ownership-vs-lease differentiator

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

hardware-usable-after-churn differentiator

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

hardware-rma-sla differentiator

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

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.

hardware-remote-device-management differentiator

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

hardware-selfpour-scales

Checked the whole hardware surface of the InfoGenesis help system. ConfigGuide 'Device' defines the device entity narrowly - 'Devices are either a physical kitchen printer (such as in IP printer), a Kitchen Display System (KDS), or an IP receipt printer' - and the peripheral topics that exist are weighing scales for sold-by-weight items (Zebra MP7201 scale support, Dual Lane Scale Support for POS Terminals, Scale, Reinitialize Scale, Printing Item Weights, Product Mix - Weight Report), a coin dispenser, secondary/guest-facing displays, barcode and QR scanning, and payment devices. Searched all 5,336 InfoGenesis topic titles and paths and the 1,448-topic Eatec inventory help system for tap wall, flow meter, pour spout, dispenser (beverage), keg or self-pour: nothing. Because the Device menu covers only kitchen and receipt devices and scales are documented as checkout weighing hardware, the absence of a beverage-dispense integration is not backed by an enumeration that claims to list every peripheral, so this stays unresolved.

hardware-callerid-integration

Searched all 5,336 InfoGenesis topic titles and paths (IG_12UX 1,688, IG_Kiosk 1,213, IG_OnDemand 902, IG_Fly 802, IG_KDS 582, IG_DMB 59, IGCM 90) and the 1,448-topic Eatec help system for caller ID, telephony, phone-order, PBX, call or screen-pop: no topic exists. The guest-lookup mechanisms that are documented are all non-telephony - Generic Authorization account lookup, PMS room/folio lookup, loyalty card and guest ID search, and IG OnDemand guest accounts with OTP verification. The ConfigGuide Device entity covers only kitchen printers, KDS and IP receipt printers, and the delivered peripheral topics are scales, coin dispenser, secondary displays, scanners and payment devices, so no supported-peripheral enumeration exists that would positively exclude telephony hardware. agilysys.com's product index (agilysys.com/en/products/) now 301s to the homepage, so the marketing side could not be re-walked at its indexed URL.

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

extensibility-api-access-cost differentiator

The Azure API Management developer portal at agys-dev.developer.azure-api.net serves an empty shell: /config.json names managementApiUrl agys-dev.management.azure-api.net/.../service/AGYS-Dev, and that host's own widget endpoints /apis?api-version=2022-04-01-preview and /products?api-version=2022-04-01-preview both return {"value":[],"count":0} to an anonymous caller, so no API, product, operation or schema is exposed publicly at all. No product tier is therefore visible to price. The published standard Terms and Conditions (www.agilysys.com/en/terms-and-conditions, read 2026-08-08) itemise fees only for Equipment, Software licences, Software Support, Professional Services and Subscription Services (sections 5.1-5.4) and name no API or developer fee either way. The InfoGenesis help system (ig.onagilysys.com/help/POS/IG_12UX/) documents the API Registration, API Client and POS API Configuration setup screens but no commercial terms. Whether the POS API is bundled or licensed separately is not publicly determinable.

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

extensibility-free-sandbox differentiator

The Azure API Management developer portal at agys-dev.developer.azure-api.net serves an empty shell: /config.json names managementApiUrl agys-dev.management.azure-api.net/.../service/AGYS-Dev, and that host's own widget endpoints /apis?api-version=2022-04-01-preview and /products?api-version=2022-04-01-preview both return {"value":[],"count":0} to an anonymous caller, so no API, product, operation or schema is exposed publicly at all. A sandbox would normally surface as an APIM product; none does. I also searched the titles of all 5,336 topics in the seven InfoGenesis help systems (ig.onagilysys.com/help/POS/<PRODUCT>/Data/Tocs/) for sandbox, test key, trial and developer topics and found none; the ConfigGuide 'API Client' topic issues a token only against a live enterprise, terminal, profile, employee and job code. No public statement either way.

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

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

extensibility-webhook-reliability differentiator

Now examined against the real event mechanism rather than a missing one. IG_12UX ConfigGuide 'Event Notification' exposes only Enable/Order/Kitchen/Employee toggles plus an IAS adapter and configuration group - no secret, no signing key, no retry or timeout field. The IG Fly release note 'Send Order and Kitchen Events' prints the complete order-event and kitchen-event JSON and no signature, HMAC, nonce or delivery-id field appears in it. 'IAS Adapter Configuration' (POS Configuration > Interfaces) only assigns an adapter to an interface type. No topic in the seven help systems describes retry with backoff or a replayable log for missed deliveries, and the Azure API Management developer portal at agys-dev.developer.azure-api.net serves an empty shell: /config.json names managementApiUrl agys-dev.management.azure-api.net/.../service/AGYS-Dev, and that host's own widget endpoints /apis?api-version=2022-04-01-preview and /products?api-version=2022-04-01-preview both return {"value":[],"count":0} to an anonymous caller, so no API, product, operation or schema is exposed publicly at all. Signing and retry behaviour may be specified in the partner-only integration guides; unresolved.

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

extensibility-menu-write-api differentiator

IG_12UX ConfigGuide 'POS API Configuration' contains exactly two fields - 'POS API Reload Config URL' and 'POS API Subscription Key' - so the setup screen tells us an API exists but nothing about its resources. The only documented way to bulk-change the menu is the IGCM release note 'New Import and Export Tasks for Items and Modifiers', which is a scheduled file task inside the back office, not an external write API. The Azure API Management developer portal at agys-dev.developer.azure-api.net serves an empty shell: /config.json names managementApiUrl agys-dev.management.azure-api.net/.../service/AGYS-Dev, and that host's own widget endpoints /apis?api-version=2022-04-01-preview and /products?api-version=2022-04-01-preview both return {"value":[],"count":0} to an anonymous caller, so no API, product, operation or schema is exposed publicly at all. With no operation list or schema published, whether menu items, modifiers and prices are writable over the API cannot be determined.

extensibility-data-symmetry differentiator

The Azure API Management developer portal at agys-dev.developer.azure-api.net serves an empty shell: /config.json names managementApiUrl agys-dev.management.azure-api.net/.../service/AGYS-Dev, and that host's own widget endpoints /apis?api-version=2022-04-01-preview and /products?api-version=2022-04-01-preview both return {"value":[],"count":0} to an anonymous caller, so no API, product, operation or schema is exposed publicly at all. Read/write symmetry is a property of the operation list, and no operation list is published: the help system's only API topics are the IGCM setup screens (API Registration, API Client, POS API Configuration), which name a client, a token, a subscription key and a Full Service flag but no resources. developer.agilysys.com, docs.agilysys.com and support.agilysys.com do not resolve. Unresolved.

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

extensibility-doordash-preferred differentiator

Cited URL 404s (redirects to merchants.doordash.com, also 404). The underlying fact is correct and verifiable elsewhere: the 2026 cohort is Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper — no Agilysys. Use the DoorDash newsroom URL instead. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-01 adversarially verified

extensibility-first-party-delivery-integrations differentiator

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

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

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

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

extensibility-bi-data-warehouse differentiator

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

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

extensibility-custom-fields-scripting

The prior basis (one anonymous Info-Tech reviewer) is not documentation and is set aside. I searched the titles of all 5,336 topics across the seven InfoGenesis help systems (ig.onagilysys.com/help/POS/<PRODUCT>/Data/Tocs/MasterTOC_Chunk*.js) for custom field, user-defined, UDF, script, extension and plugin: the only hits are unrelated ('Improved Description Visibility for Terminal Options', 'Time Extension to Place ASAP Orders'). Configuration in IGCM is fixed-form - Permission Group, Role, Terminal Option numbers - with no documented user-defined field or scripting hook. A title index is not an exhaustive statement about the product, and the Azure API Management developer portal at agys-dev.developer.azure-api.net serves an empty shell: /config.json names managementApiUrl agys-dev.management.azure-api.net/.../service/AGYS-Dev, and that host's own widget endpoints /apis?api-version=2022-04-01-preview and /products?api-version=2022-04-01-preview both return {"value":[],"count":0} to an anonymous caller, so no API, product, operation or schema is exposed publicly at all. so a vendor-hosted extension model cannot be ruled out.

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

extensibility-api-versioning-deprecation

The Azure API Management developer portal at agys-dev.developer.azure-api.net serves an empty shell: /config.json names managementApiUrl agys-dev.management.azure-api.net/.../service/AGYS-Dev, and that host's own widget endpoints /apis?api-version=2022-04-01-preview and /products?api-version=2022-04-01-preview both return {"value":[],"count":0} to an anonymous caller, so no API, product, operation or schema is exposed publicly at all. so there is no portal changelog or deprecation notice. The public release-notes books (ReleaseNotes across IG_12UX, IG_Kiosk, IG_OnDemand, IG_Fly, IG_KDS and IGCM, versioned 12.3.9 through 12.3.15.7) are product release notes, not an API changelog: the nearest entries are IGCM's 'Move POS API Client License Key from API Registration to API Client' and 'Restrict Permission Group Creation...', which describe back-office screens rather than API versions. No deprecation or breaking-change notice policy is published on agilysys.com (/en/terms-and-conditions makes no reference to one). Unresolved.

extensibility-data-portability-exit differentiator

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

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

reliability-offline-card-auth differentiator

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

reliability-offline-decline-liability differentiator

No public Agilysys document addresses store-and-forward decline liability or offline transaction caps.

reliability-lan-degraded-multi-terminal differentiator

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

reliability-local-transaction-engine differentiator

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

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

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

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

reliability-offline-feature-matrix

Agilysys markets offline resiliency repeatedly but publishes no explicit list of what is unavailable offline (gift cards, loyalty lookup, refunds, manual card entry).

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

reliability-contractual-uptime-sla differentiator

Agilysys does publish a standard master agreement - www.agilysys.com/en/terms-and-conditions (read 2026-08-08) - which the prior rationale assumed did not exist. Section 3.3: 'All Subscription Services will be subject to and performed in accordance with applicable service level policies in effect at the time. Agilysys reserves the right to make changes to its service level policies at any time.' The service level policies themselves are not published (/en/sla/ and /en/legal/ both 404), so no percentage is readable. Section 6.3 makes correction, circumvention or a fee refund the 'sole remedy' for non-conforming Subscription Services, which points away from service credits without excluding them from the unpublished policy. status.onagilysys.com is a Site24x7 StatusIQ page ('Agilysys SaaS North America Status') that renders client-side and shows no SLA figure. Unresolved because the incorporated policy is not public.

reliability-incident-postmortems

status.onagilysys.com is a Site24x7 StatusIQ status page ('Agilysys SaaS North America Status - View active incident progress, historical component status, and subscribe to email and RSS notifications'), rendered entirely client-side from js-wc.site24x7static.com. It is not Atlassian Statuspage, so /api/v2/summary.json, /api/v2/incidents.json and /history.json all return 404, and /sp/api/public/statuspages/incidents 404s as well; I could not enumerate past incidents or inspect whether any entry carries a root-cause summary. agilysys.com/en/customer-support/ links MyAgilysys, email and regional phone support with no incident-report archive, and no post-incident report is published anywhere I could reach on agilysys.com. Unresolved: the incident history exists behind the client-rendered page but its contents were not readable.

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

reliability-onsite-install differentiator

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

reliability-menu-build-service differentiator

The published Terms and Conditions (www.agilysys.com/en/terms-and-conditions) enumerate 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) - initial menu or database build is not named either way, and the scope of any given engagement lives in the customer's Agreement, which is not public. The IG_12UX ConfigGuide addresses the operator throughout when building Items, Modifiers, Screens, Price Tiers and Profit Centers in IGCM, but a configuration guide is written for the operator whether or not Agilysys does the first build. No agilysys.com page (/en/customer-support/, product pages) states that the initial menu build is included in onboarding. Unresolved; the prior 'reviewers report' basis is set aside as not documentation.

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

reliability-backup-restore

A title search of all 5,336 InfoGenesis help topics for backup and restore returns only unrelated hits ('Remove/Restore Gratuity', 'Remove/Restore Tax', 'Remove/Restore Service Charge', and IG KDS 'Backup Station Enhancements', which is a kitchen-display station role) - there is no operator-triggered backup or restore utility topic in IGCM. The published Terms grant a backup copy of the Software only ('to make one (1) copy of the Software if reasonably necessary for internal back-up purposes', 2.1), not of data. The published DPA puts the onus on the customer without providing a tool: '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' (12.1). No RPO or RTO figure appears in the Terms, the DPA, or on status.onagilysys.com. Unresolved - SaaS backup posture is likely in the unpublished service level policy.

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

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

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

reliability-failover-terminal-role differentiator

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

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

commercial-month-to-month-contract differentiator

Re-read Agilysys's published Terms and Conditions end to end on 2026-08-08. The document never states an initial subscription term. Section 5.4 Subscription Fees governs renewal only and expressly defers to the signed order form: '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.' Section 10.1 Term is equally open-ended ('The Agreement will begin on the Effective Date and will remain in effect until terminated accordance with these Terms'). So the published default renewal cycle is annual, but the length of the term a customer first commits to is set in a non-public agreement, and Agilysys publishes no pricing page, plan tier or self-serve sign-up - www.agilysys.com/en/products/ now 301s to the homepage. Neither a month-to-month option nor a multi-year minimum is publicly established either way. Left unknown rather than no because a renewal clause that yields to the order form is not an enumeration of the terms on offer.

commercial-no-early-termination-fee differentiator

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

commercial-autorenew-terms-published

No publicly accessible contract terms on agilysys.com state auto-renewal length or cancellation notice window; terms live only in signed quotes.

commercial-processing-not-bundled differentiator

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

commercial-interchange-plus-published differentiator

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

commercial-rate-increase-clause differentiator

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

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

commercial-module-unbundling differentiator

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

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

commercial-hardware-not-locked differentiator

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

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

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

commercial-export-customer-and-loyalty differentiator

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

commercial-post-termination-export-window differentiator

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

commercial-data-ownership-clause differentiator

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

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

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

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.

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

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

commercial-wcag-kiosk-accessibility differentiator

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

commercial-dual-pricing-compliant differentiator

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