Vendors / Enterprise & chain restaurant POS
Infor
Infor (Hospitality / POS)
Enterprise hospitality suite vendor whose "Infor POS" is positioned as a terminal/kiosk/tableside/poolside component alongside Infor HMS and Sales & Catering — a quote-only enterprise sale with no published pricing, but with a full public documentation library at docs.infor.com/pos covering the POS, both Enterprise Manager generations, Kiosk and OrderNow.
scored unknown legacy rubric
- Claims in scope
- 314
- Scored
- 45
- Assessed
- 43
- Unknown
- 271
- Not applicable
- 0
- Values challenged
- 4
unknown, never as no.Identity
- Owner
- Infor (a Koch Industries company)
- Parent
- Koch Industries
- Who it is for
- Hotels, resorts and large hospitality operators already buying Infor HMS and Sales & Catering; POS is sold as one module of a suite, not as a standalone restaurant product
- Site
- https://www.infor.com/industries/hospitality
Pricing
transparency: quote-only · unit: unknown (quote-only, enterprise licensing) · processor lock-in: unknown
- Software
- Not published. Enterprise quote-only; the hospitality industry page carries no figures.
Capabilities
Every claim is binary and checkable. Grades: A primary documentation · B product documentation · C pricing or feature page · D marketing claim · E third-party reporting · F inference with no source. A yes on a differentiator claim requires A or B.
Order capture & FOH workflow
Provides a graphical floor-plan editor where an operator can draw sections, place tables of varying shape/capacity, save multiple floor-plan layouts per location, and assign sections to servers.
order-capture-floor-plan-editor
Not scored by this record.
Order lines can be tagged to a seat number at entry, and the check can be split by seat afterward without re-keying items.
order-capture-seat-level
Not scored by this record.
Items can be assigned to courses and held, with a fire-next-course action available from a handheld or terminal that releases only that course to the kitchen.
order-capture-coursing-hold-fire
Not scored by this record.
Supports splitting a check by item, by seat, by even N-way, and by arbitrary dollar/percentage amount, and merging checks or tables back together, including after partial payment.
order-capture-split-merge
User Guide 3.0.27 ch.2 documents 'Separating a check per guest' (tap New Check per guest, or Separate Checks to auto-create a check for every guest), 'Combining checks of guests in a single table number' (Check To), 'Moving a check to an existing table'/'to a new table' (Move Check), and 'Merging checks' with two named merge styles — Merge Seats ('combine the menu items of guests from different table numbers to a single table number') and Append Seats. By-item splitting is 'Moving a menu item to another guest'/'Sharing a menu item' (cost 'split equally between the guests'); even N-way is Split Evenly ('print the receipt with the amount due divided among guests'); arbitrary amounts come via 'Processing a split tender transaction' — 'splitting a single check transaction into two or more transactions with any combination of payment options', keying a cash or credit amount and leaving a remaining balance. Merge is documented for a 'sent check'; behaviour after a partial payment is not addressed. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/user/pos_3.0.27_user__en-us.pdf · retrieved 2026-08-03
Opens a bar tab against a card pre-authorization with a configurable auth amount, supports incremental re-auth as the tab grows, and auto-closes stale tabs at end of day. differentiator
order-capture-bar-tab-preauth
Not scored by this record.
An open check can be transferred between servers, tables, and devices, and the transfer is recorded in an audit log naming both employees.
order-capture-transfer-audit
Not scored by this record.
Ships a first-party handheld ordering app running natively on the handheld device (not a remote/mirrored desktop session) that can send to kitchen and take a card payment tableside.
order-capture-native-handheld
Not scored by this record.
With the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen, and tender cash, and the vendor publishes what does and does not work offline.
order-capture-offline-order-entry
An offline mode demonstrably exists and the terminal is local-first, but its scope is never published. Evidence for: the Connectivity indicator is a three-state light on the sign-in screen — green 'connected to the Internet and the Infor POS cloud', yellow 'connected to the Internet, but not to the Infor POS cloud', red 'not connected to the Internet' — so the application runs and signs staff in while disconnected. Architecture is local-first: 'A revenue center is either a primary terminal or a combination of primary and client Infor POS terminals in a store. Client terminals send data gathered from using Infor POS to a master terminal. The primary terminal then consolidates the data and uploads it to an Infor POS database', and a Backup RVC function assigns primary/backup roles between revenue centers. Offline tender is documented twice: the report glossary defines Offline credit as 'The total amount of credit card authorization requests entered in offline mode and waiting for authorization' (it is also a line on the Employee Summary Report), and 'Processing offline transactions for a stored-value card' states 'If the internet connection is down, you can process a stored-value card payment as an offline transaction and close the check. The transaction through the card payment processor queues up for automatic processing when the Internet is re-established', with a Payment online function that forces a processor offline. Named shortfall: the second half of the claim is unmet — no guide in the 3.0.27 library contains an offline-operation section enumerating what does and does not work while disconnected. Nothing states whether kitchen chits still print or route, whether menu and configuration changes remain available, whether cash tender is unaffected, or how long the offline credit queue may grow; the only 'internet is down' instruction in 56 pages concerns stored-value cards, and even there offline behaviour is disclaimed to the provider ('Offline capabilities of stored-value cards depend on its provider'). https://docs.infor.com/pos/3.0.27/en-us/useradminlib/user/pos_3.0.27_user__en-us.pdf · retrieved 2026-08-04
Guest QR at-table ordering writes items onto the same open check as server-entered items, rather than creating a separate order ticket. differentiator
order-capture-qr-same-check
Not scored by this record.
Offers a first-party self-order kiosk that renders the same menu and modifier tree as the POS with no separate menu build, and the vendor documents ADA/accessibility conformance for it. differentiator
order-capture-kiosk-first-party
Not scored by this record.
Supports drive-thru-specific order flow: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment.
order-capture-drive-thru
Not scored by this record.
Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.
order-capture-drive-thru-timers
Not scored by this record.
Vendor ships a first-party AI voice ordering agent for phone and/or drive-thru that injects orders directly as POS orders, or publishes a documented API partner program for third-party voice AI. differentiator
order-capture-voice-ai
Not scored by this record.
Supports order throttling: per-channel capacity limits per time slot with automatic quote-time extension when kitchen load exceeds a configured threshold. differentiator
order-capture-throttling
Not scored by this record.
Accepts future-dated/scheduled orders with a per-channel lead time and automatically injects them into the make queue at a computed fire time rather than on receipt.
order-capture-scheduled-orders
User Guide 3.0.27, 'Scheduling an order': Schedule Order takes a date and a time, items are then added and sent, and 'The check is automatically sent to the kitchen on the specified date and time. You can configure the time when the check is sent to the kitchen minutes before the specified time' — i.e. a configurable lead time and a fire-time injection rather than print-on-receipt. A schedule limit (e.g. seven days out) is configurable, scheduled orders are shown on a dashboard, and 'You can modify the menu items, date, and time of both unpaid and paid scheduled orders prior to the specified schedule'. The digital channel has its own switch: OrderNow Admin Portal 'Configuring scheduled orders' = Order > Future Orders check box plus optional kitchen service start/end times. Lead-time changes are made via an Infor POS representative, not self-serve. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/user/pos_3.0.27_user__en-us.pdf · retrieved 2026-08-03
Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.
order-capture-catering
Not scored by this record.
Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator
order-capture-order-ready-signal
Not scored by this record.
Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.
order-capture-void-comp-controls
Not scored by this record.
Menu, modifiers & pricing engine
Payments & money movement
The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator
payments-processor-choice
Not scored by this record.
Vendor publishes card-processing pricing publicly (a specific flat rate or interchange-plus markup) rather than quote-only. differentiator
payments-published-rates
Not scored by this record.
Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator
payments-dual-pricing
Not scored by this record.
Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator
payments-surcharge-guardrails
Not scored by this record.
All first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay.
payments-emv-nfc
Infor's own storefront sells exactly four payment devices, all PAX Android units — A35 PIN pad, A30 multilane, A920Pro mobile, Elys A3700 customer-facing tablet — and the collection description states the lineup comprises 'Android-based smart PIN pads, mobile payment terminals, and customer-facing payment tablets that support EMV and contactless transactions'. The A35 product page specifies 'tap, chip, and swipe card payments with PIN entry' on PayDroid (Android 10), and unlike the POS terminals these SKUs carry list prices ($364-$644). So EMV chip plus NFC contactless is established for every payment device Infor sells. Named shortfall: Apple Pay and Google Pay are named nowhere on the store or in the five-guide 3.0.27 documentation library — the only EMV trace in the docs is the EM tender check box 'EMV Manual... enable manual entry of card number with EMV' — and the A35 page states the device 'arrives unconfigured and requires setup with your payment processor before accepting payments', so wallet acceptance rests with processor configuration rather than being a documented product property. https://pos.infor.com/collections/payment-devices · retrieved 2026-08-04
Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. differentiator
payments-softpos-tap-to-pay
Not scored by this record.
Vendor ships a handheld that takes EMV/NFC payment at the table, including tip prompt and check splitting, without carrying the card away.
payments-pay-at-table
Not scored by this record.
Guest can scan a QR code on the printed check or table tent to view and pay the check from their own phone, with the payment closing the check in the POS automatically. differentiator
payments-qr-guest-pay
Not scored by this record.
Supports both pre-auth-then-tip-adjust and on-device tip prompt flows, with a documented batch/adjust window and a manager screen for unadjusted tips.
payments-tip-adjust
Not scored by this record.
Configurable tip pooling and distribution rules (by hours worked, sales, role percentage, or points) that produce a per-employee tip allocation exportable to payroll. differentiator
payments-tip-pooling
Not scored by this record.
Card payments can be captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. differentiator
payments-offline-store-and-forward
Not scored by this record.
Vendor publicly documents who bears the loss when a stored offline transaction declines on reconnect, and surfaces a post-reconnect report of failed offline payments. differentiator
payments-offline-decline-liability
Not scored by this record.
First-party gift cards with real-time balance tracking, redeemable across every location in the group and through the online-ordering channel.
payments-gift-cards
User Guide 3.0.27 ch.5 'Stored-value cards' covers gift cards: tender against 'the tender button of the stored-value card provider', 'Loading a stored-value card' (Add to Gift Card), 'Performing a balance inquiry' (real-time balance shown and printable), offline stored-value transactions, and a Gift Card Daily Report in EM giving 'the balances that were loaded to each gift card provider for the day'. Shortfall: the cards are not first-party — every function is routed through an external stored-value card provider, Infor POS can be configured to one or several providers, and 'Offline capabilities of stored-value cards depend on its provider. For details, contact your stored-value card provider.' Redemption scope across all locations in a group and through the OrderNow ordering channel is nowhere documented. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/user/pos_3.0.27_user__en-us.pdf · retrieved 2026-08-03
House/on-account tabs with per-account credit limits, running balance, and periodic statement or invoice generation.
payments-house-accounts
Not scored by this record.
A single check can be settled with multiple tenders and split by seat, by item, by even shares, or by arbitrary amount, with no hard cap below eight ways.
payments-split-tender
Not scored by this record.
Voids, refunds, discounts, and no-sales require role-based authorization (manager PIN or approval) and write to an immutable audit log identifying the approver.
payments-refund-void-controls
EM Administration Guide 3.0.27 'Configuring Infor POS features for a job code' sets an access level per individual POS function — NONE ('If this function is used with a NONE access level, an on-screen numeric keypad is displayed... you must specify the user ID of an employee with a FULL access level'), NORMAL, FULL — and the same per revenue center via Store Settings; discounts and service charges are separately gated by 'Adding a job code to a discount or service charge'. Exception reporting distinguishes 'Manager voids — the count and value of voids that require authorization' from 'Server voids — voids... that do not require authorization', and 'Voided Down to $0' records 'the tab ID, the total amount, and the manager who authorized the checks that are voided to $0'. Infor does not use the word immutable for these records. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/em3admin/pos_3.0.27_em3admin__en-us.pdf · retrieved 2026-08-03
In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator
payments-chargeback-tooling
Not scored by this record.
Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator
payments-card-on-file
Not scored by this record.
Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator
payments-payout-timing
Not scored by this record.
A single account can route settlement funds to different bank accounts per location or legal entity (separate MIDs or split settlement) under unified reporting. differentiator
payments-multi-entity-routing
Not scored by this record.
Vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance / P2PE listing available to merchants on request.
payments-p2pe-pci4
Not scored by this record.
Kitchen & production
Items route to specific KDS stations by item, category, order type, or revenue center, with routing rules configurable per location without vendor involvement.
kitchen-station-routing
Enterprise Manager Administration Guide 3.0.27 ch.7 'Printing management' documents the routing model end to end. A logical printer 'represents a physical printer in your revenue center... Use a logical printer to connect with multiple routing groups to print receipts of specific menu items to different locations, such as multiple kitchens. For example, you can route printing of receipts with egg menu items to your first kitchen printer, while you can route printing of receipts with hash menu items to your second kitchen printer' (Configuration > Printing > Printers > Logical Printers; separate tasks add a routing group and assign it to a logical printer). Routing is set at two levels of the item hierarchy: per menu item (Details > Printing > Routing Group — 'Configuring the routing group on a menu item level overrides the routing group set on a family group level') and per family group, i.e. category (Routing Group field, with an Output/Edit Output printer picker shown instead when routing groups are disabled). Per-location override is explicit: 'Optionally, to assign a routing group to a specific revenue center, click Store Settings.' The targets are KDS devices, not only printers — Printer Parameters carry KDS-specific fields (Consolidate: 'have menu item modifiers displayed as one line in a kitchen display system (KDS)'; Print Summary: 'For a KDS, select one of these options: No / On Top / On Bottom'), items carry a Kitchen Name that 'takes precedence over the local name in being displayed in the kitchen printer or display' plus Priority ('Menu items with the same priority level are displayed together in the kitchen display') and Cook Time, and the report catalogue includes a Speed Of Service Report that 'Describes bump times from the KDS'. All of this is customer-administered in Enterprise Manager with no vendor ticket. Not evidenced: routing by order type (dine-in vs takeaway) is nowhere in either EM guide — the documented axes are item, family group and revenue center. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/em3admin/pos_3.0.27_em3admin__en-us.pdf · retrieved 2026-08-04
An expo screen consolidates items from multiple prep stations into a single order view and only marks the order complete when every contributing station has bumped its items.
kitchen-expo-consolidation
CLAIM UNDER TEST: an expediter or expo view consolidates the items of one order across the kitchen stations it was routed to, and gates completion on every contributing station. VERDICT unknown: Infor ships a KDS but publishes no anonymous description of its screen behaviour. This note replaces one that was bound to the superseded 3.0.27 library and that asserted the library 'contains only five guides'; 2026.08 publishes FOUR guides in 374 topics, the EMv1 guide having been removed, and every element below was re-derived from the current HTML rather than inherited. WHAT IS MET AND WHAT IS ABSENT. Met: a KDS demonstrably exists. It is bumped from the POS, Functions menu (user/gog1555619772856.html): 'Bump Order - Bumps the order off Infor KDS'. It has a report metric, 'Types of Infor POS reports' (user/gnu1562573286176.html): 'Speed of Service - Lists all kitchen times during the specified period. Kitchen Time is the sum of Prep time and Expo bump', and the EM guide describes the same report (em3admin/teb1570776984357.html). It has certified hardware: pos.infor.com/products.json?limit=250 returns all 117 SKUs, among them monitors 'Certified for Infor Kitchen Display System', bump bars, a bump bar controller, A/B switches and a fan filter, which are hardware descriptions with no expo semantics and grade C in any case. Absent: any KDS guide at all. The publisher's sitemap lists four POS libraries in total and the useradminlib manifest resolves to the four guides named below, none of them a KDS document. THE ONLY KDS CONFIGURATION INFOR PUBLISHES IS PRINTER PARAMETERS, in 'Adding printer parameters for a logical printer' (em3admin/izw1570607551347.html): 'Consolidate - Select this check box to have menu item modifiers displayed as one line in a kitchen display system (KDS).' and 'Print Summary - For a KDS, select one of these options: No ... On Top ... On Bottom'. THAT 'Consolidate' IS A HOMONYM AND IS THE TRAP IN THIS CELL: it consolidates MODIFIER LINES on one ticket, not items across stations, and must never be read as cross-station expo consolidation. WHY IT CANNOT BE SCORED EITHER WAY. Infor's kitchen distribution model is print routing and the docs enumerate it in full: 'A routing group contains family groups to route orders of specific menu items to a printer. The routing group is then assigned to a logical printer, which is a representative of a physical printer in a revenue center' (em3admin/res1570676037826.html), overridable per item (em3admin/qlk1568358256119.html). A KDS is addressed as one of those logical printers. Nothing published states whether an expo screen aggregates the items a ticket sent to several such devices, or withholds completion until every contributing device bumps. CONTROLS OVER ALL 374 TOPICS, 4,472,753 BYTES, WORD-BOUNDARY, RE-RUN BY THE VERIFIER: station 0, workstation 0, expeditor 0, expediter 0, expediting 0, destination 0, video 0; expo 1, that one hit being the report metric above; bump 3 across three topics; KDS 13 across five topics, every hit read; routing 55, all of it printer routing. Corpus controls pass: Infor 3,827, menu 2,267, check 1,274, print 1,212, kiosk 503, so these are real zeros about a real corpus. POISON IN THE DOC CORPUS, tokenised and reproduced by the verifier: key 1,135 hits and URL 1,164 and XML 744 are all Oxygen WebHelp chrome across all 374 topics and carry no product meaning; favorite 16 is the WebHelp Favorite button, four hits in each of the four default.html shells and nowhere else, not a guest favourites feature; REST 1 is the sentence 'The rest of the reports must be exported in a new tab'; merge 9 is seven hits of 'Merging checks' in user/ueu1576570123604.html plus two incidental, never a profile merge; prep 1 is 'Prep time' in a report definition; 'stored value' resolves to stored-value cards, not a payment vault. MANIFEST AND GATE. docs.infor.com/sitemap.xml (234,123 bytes, 1,771 loc elements, re-fetched whole 2026-09-15 by the verifier) lists exactly four Infor POS libraries: /pos/2026.08/en-us/useradminlib/, /pos/2026.08/en-us/technical/, and the same pair for 2026.05. The 2026.08 useradminlib sitemap.html (28,297 bytes) resolves to 375 hrefs, which is 374 topic files in four folders (user 148, em3admin 146, kadmin 65, posonapag 15, four of which are the per-guide default.html tables of contents) plus one top-level shell, so 2026.08 publishes FOUR guides and not five; the EMv1 guide of the retired 3.0.27 library is gone. All 374 were fetched at 200 and searched as RAW HTML with only HTML comments stripped and every control word matched on word boundaries; tag stripping was not used, because it welds table cells into false quotes. Doc corpus 4,472,753 bytes; corpus controls pass, Infor 3,827 menu 2,267 check 1,274 print 1,212 kiosk 503. The second per-version /technical/ library is a login wall, not an absence: https://docs.infor.com/pos/2026.08/en-us/technical/sitemap.html answers HTTP 302 to /docs/sso?contentUri=%2Fpos%2F2026.08%2Fen-us%2Ftechnical%2Fsitemap.html and a SAML auto-submit form; it was not evaded and it caps every absence recorded here. The superseded 3.0.27 library still answers 200 (25,937 bytes, re-probed 2026-09-15) and is an archived generation, not a dead link. A second rendering instrument does exist and was checked. The 2026.08 PDFs are UNLINKED - no topic references one and sitemap.xml has no PDF entry - but they are served at the same path pattern the 3.0.27 generation used, and all four return 200 (user 1,618,213 B; em3admin 2,125,483 B; kadmin 730,794 B; posonapag 302,954 B). pdftotext extracts them cleanly, 299,267 characters with a positive control of Infor=671, and the API-vocabulary zeros reproduce in them. An earlier note's claim that Infor's PDFs are unreadable because of a custom-encoded font is FALSE: that artefact came from one broken cached extraction, not from the files. CAVEAT. A KDS product demonstrably exists but Infor publishes no anonymous documentation of its screen behaviour anywhere in the current library, and the second per-version /technical/ library is behind the SAML wall described above. Absence of a document is unknown, not no. || 320th: 320th NEW SURFACES, nothing on expo. (1) The Infor Partner API developer portal https://developer.vivonet.com/ (production, census of five Swagger specs via /api_docs/services.json): kds 0, kitchen 0, expo 0, bump 0 in every spec. (2) The Infor POS Enterprise Manager web app https://emweb.hpo.inforcloudsuite.com/entMgr/index.html (production; found via crt.sh %.hpo.inforcloudsuite.com; robots.txt is a generic 'User-agent: * Disallow: /', not naming our bot): its anonymous static bundle (43 scripts; entMgr.min.7d13b21d.js 2,365,509 B) and 157 of its 197 referenced AngularJS templates (40 report-app templates 404) were read. KDS 0 and expedit 0 across all of it; 'expo' 19 in the bundle is POISON - every hit is 'export'. The only kitchen configuration screens are printerParameters, printers, routingGroups and familyGroups editOutput, i.e. the same printer-routing model the docs already describe. No KDS editor exists in the Enterprise Manager front end, so KDS screen behaviour is configured elsewhere and remains undocumented anonymously. Retrieved 2026-09-16. || 323rd: 323rd, NEW PRODUCTION HOST, NOT NAMED BY ANY PRIOR NOTE. crt.sh on inforcloudsuite.com (1,215 names) and vivonet.com (56) and halopos.com (6) was re-run; the only previously unrecorded live surface is the OrderNow ADMIN console, https://admin-ordernow.hpo.inforcloudsuite.com/ (HTTP 200, 1,531 bytes, <title>OrderNowAdmin</title>; it is NOT a soft-200 catch-all - /zzz-nonsense-path returns an honest 404 of 352 bytes). It is bounded by the publisher's own Angular service-worker manifest /ngsw.json (200, 26,686 bytes, 172 assets of which 119 are .js), and the application closure is 7 files - runtime/polyfills/main/scripts in es2015 and es5 twins; the other 112 .js are the ids-enterprise LOCALE CULTURE files, which are the classic false-hit source and were excluded. The four es2015/neutral files were read as raw bytes: 2,921,020 bytes. NO SOURCE MAP IS PUBLISHED and this was controlled: main-es2015.2e23f4fc6920945296f0.js.map returns 404/374 bytes and the fabricated sibling main-es2015.ZZZZZZZZ.js.map returns 404/362 bytes, i.e. the same shape, so there is no map to parse and no SPA-shell soft 200 was mistaken for one. halopos.com and www.halopos.com are a PARKED 'Reserved for halopos.com' placeholder page, not a product. ecs/go/reports/legacy/page.vivonet.com and stage/hpo.inforcloudsuite.com do not answer (connection failure, not a refusal); ssee.vivonet.com returns 403 to curl with a browser UA and the Accept/Accept-Language pair, which is a refusal and not an absence. WHAT IT HELD FOR THIS CELL: no kitchen surface at all. Over the whole 2,921,020-byte closure, tokenised, word-boundary, case-insensitive: kds 0, kitchen 0, expo 0, expedit 0, bump 0, station 0, printer 0, routing 0, consolidat 0, with positives menu 448, store 22, order 14, print 10, route 46 (Angular router). This is the second Infor first-party web application after the Enterprise Manager front end to contain NO KDS configuration or display surface whatsoever, which narrows where the undocumented KDS behaviour can live but does not describe it. 323rd, THE WAYBACK ROUTE IS NOW CLOSED FOR THIS VENDOR. Every note on this record is capped by the SAML-gated https://docs.infor.com/pos/2026.08/en-us/technical/ library, and the 320th recorded that Wayback was offline on 2026-09-16 so the walled-docs-may-have-been-public check could not be run. It was run today and the archive is up: http://web.archive.org/cdx/search/cdx?url=docs.infor.com%2Fpos%2F*&output=json&collapse=urlkey returns 52,316 bytes of captures of the OPEN useradminlib topics (2026.02 em3admin/user/kadmin/posonapag .html files, 200s), while the same query narrowed to docs.infor.com/pos/2026.08/en-us/technical/* and to docs.infor.com/pos/*/technical/* returns ZERO rows on both. The gated technical library has never been archived, so it was never public and cannot be recovered. docs.vivonet.com has no captures either; developer.vivonet.com has 22 (2017-2019, all portal chrome: /docs, /login, /signup, /robots.txt, bootstrap css/js) and api.vivonet.com has 3. So the only route that could have recovered a KDS guide - an archived copy of the gated technical library - is now positively excluded, and the cell rests where it was: Infor ships a KDS and publishes no anonymous description of its screen behaviour. Retrieved 2026-09-17. || 329th: 329th: A NEW HOST AND THE FIRST INFOR SENTENCE EVER FOUND ABOUT KDS SCREEN BEHAVIOUR - AND IT STILL DOES NOT REACH THE CLAIM. https://archive.docs.infor.com/ is named by no prior note; it was found in docs.infor.com's own client config (window.env.ARCHIVEDOMAIN in https://docs.infor.com/static-867db65b/js/env.js). It serves eight archived Infor POS useradminlib generations that docs.infor.com/sitemap.xml no longer lists - 3.0.21 through 3.0.28 - each with its own publisher manifest sitemap.html, and both extremes were fetched to 100% with zero misses (3.0.27: 469/469; union of the other seven: 600/600 more), i.e. 1,069 topic files, 17,245,444 raw bytes, including three folder families the 2026.08 library lacks entirely: em1admin (the removed EMv1 guide, 90 topics), admin (15) and release_notes_2020/2021/2022/2023 (~130 topics). WHAT IT HELD. The release notes contain the only published description of Infor KDS behaviour in the atlas's record of this vendor: 'Infor KDS integration - You can now integrate Infor POS with Infor KDS software and hardware. When integrated with Infor KDS, you can now send and view the status of menu items to multiple KDS screens in real time using Infor POS. You can also select order types and modifiers in line with Infor KDS.' (release_notes_2021/vnp1603782159413.html, published in the 3.0.23 generation), and 'Infor KDS - You can now generate the Speed of Service report... If the bump bar is not available, then you can now tap the KDS Bump button in Infor POS to bump orders off the KDS screens.' (release_notes_2022/gpm1635312407349.html). So MULTIPLE KDS SCREENS and real-time per-item status are now established, and bumping is possible from the POS across those screens. WHY THIS IS STILL NOT A PARTIAL. The claim needs an EXPO SCREEN that consolidates items from several prep stations into a single order view AND withholds completion until every contributing station has bumped. Infor's sentence describes the opposite direction - items being SENT OUT to multiple screens, with their status readable back at the POS terminal - and it names no expo view, no order-level consolidation across screens and no completion gate. A partial built on it would shortfall every conjunct of the claim, which the merge rejects, and a no may not rest on a retired generation while the /technical/ library stays gated. Also new and read: 'Kitchen chit information - You can now add and configure this information in the kitchen chit: Item count summary / Payment status / Scheduled order time / Sequence of menu items and modifiers by priority' (release_notes_2021/iyg1621835880680.html), which is chit layout, not an expo screen. CONTROLS OVER THE WHOLE NEW 1,069-FILE, 17,245,444-BYTE CORPUS, tokenised word-boundary case-insensitive: expediter 0, expeditor 0, expedite 0, station 0, video 2 (both an unrelated em3admin topic); expo 3 and every one is the Speed-of-Service report metric 'Kitchen Time is the sum of Prep time and Expo bump' (release_notes_2023/eoc1654587512728.html, release_notes_2023/rcr1635312715016.html, user/gnu1562573286176.html) - THE SAME HOMONYM TRAP the existing note records, now reproduced twice more in the archive; bump 13, of which release_notes_2022/gpm1635312407349.html holds 6 and is the only operational one; 'bump bar' 2, both in that topic; KDS 88 and 'kitchen display' 17, spread over the EMv1 twin em1admin/byg1619573712194.html (which is the printer-parameter topic izw again, with the same 'Consolidate - menu item modifiers displayed as one line in a KDS' MODIFIER-LINE homonym and the same Print Summary No/On Top/On Bottom options), kadmin/sty, user/jrg, user/gog and the posemag/poskag/posug reprints of the same files under the 3.0.21 folder names; consolidate 7, no new sense. Corpus positives pass: Infor 10,580, menu 7,521, print 3,411, check 2,968, kitchen 209. ROUTES CLOSED TODAY. The publisher's own topic manifest is fetched to 100% on both the current and every archived generation, so there is no unlisted-topic route left; the Oxygen WebHelp static search index of the 2026.08 library is a DISABLED STUB (oxygen-webhelp/app/search/index/index-1.js is 148 bytes and returns {"test":...}, index-2.js and index-3.js are 74 bytes each, and htmlFileList.js / htmlFileInfoList.js / keywords.js 404 with docs.infor.com's 6,877-byte error page), so no hidden topic list exists there; docs.infor.com's content API (/api/v2/products, /contents, /search) answers 401 'No authorization (bearer)' to anonymous GET and no token was obtained; archive.docs.infor.com gates /technical/ exactly as docs.infor.com does (3.0.26 and 3.0.27 both 302 to /docs/sso?contentUri=...). APP-STORE CENSUS, ALSO NEW AND ALSO EMPTY FOR THIS CELL: the iTunes publisher census of Infor (US), LLC (artistId 493525183) returns 59 apps and exactly ONE is a POS product, 'Infor POS Mobile Insights' (id 6475422870, com.infor.mobileinsights2, 3.0.1, last updated 2024-09-24), a multi-location sales/discount/void reporting app whose own listing says 'only available to current Infor POS customers'; there is no Infor KDS, expo, kitchen or store-level POS app on the store, so no screenshot route to a KDS screen exists. Retrieved 2026-09-18. adversarially verified
Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator
kitchen-course-firing
Not scored by this record.
Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator
kitchen-prep-time-pacing
Not scored by this record.
Kitchen load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator
kitchen-order-throttling
Not scored by this record.
Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator
kitchen-channel-pause-propagation
Not scored by this record.
Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator
kitchen-order-ready-callback
Not scored by this record.
KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.
kitchen-bump-bar-hardware
CLAIM: KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models. MET: Infor's own first-party hardware storefront sells two current Infor-branded bump bar models by part number and price. The 'Infor Next GEN Bump Bar (USB Version) with Bracket' (variants FP-900580-104 4ft $230 / FP-900580-112 12ft $245; vendor Infor, product_type Hardware, published 2025-12-19) is 'an advanced keypad solution designed for seamless integration with Infor SmartSeries and Infor POS systems, as well as select compatible Kitchen Display Systems (KDS)', with 'USB interface for quick, plug-and-play connectivity', 'Optimized key layout for efficient kitchen workflow' and 'High-durability key switches' (https://pos.infor.com/products/infor-bump-bar, re-fetched 200, 424,610 bytes, 2026-09-15). The 'Infor Next GEN Bump Bar (SERIAL Version) with Bracket', SKU FP-700580-009, $245, is 'an advanced keypad assembly designed for seamless compatibility with Infor SmartSeries, Infor POS systems, and other supported Kitchen Display Systems (KDS)' with 'optimized key mapping for common kitchen ticket functions' (https://pos.infor.com/products/infor-next-gen-bump-bar-serial-version-with-mounting-kit, re-fetched 200, 2026-09-15). The surrounding estate corroborates a real bump-input product line: Infor Bump Bar Power Supply FP-700581-002, Infor Bump Bar Controller FP-900500-000 (named on the 'Infor KDS GEN 4 Power Adapter' 59-105501-000 listing), Infor Bump Bar Mounting Plate Kit AS-700576-000 and Replacement Bump Bar Hardware Kit AS-100575-000. That the POS drives a KDS with a bump action is separately documented at grade B: the Infor POS User Guide 2026.08 'Functions menu' button table defines 'Bump Order Bumps the order off Infor KDS' (https://docs.infor.com/pos/2026.08/en-us/useradminlib/user/gog1555619772856.html, re-fetched 200, 2026-09-15), and 'Types of Infor POS reports' defines Speed of Service as 'Lists all kitchen times during the specified period. Kitchen Time is the sum of Prep time and Expo bump.' SHORTFALLS, which are why this is partial and not yes: (1) the second conjunct, documented supported models, is satisfied only in the hardware direction. The bump bar models are named, priced and part-numbered, but no source states which KDS supports them: both bodies hedge to 'select compatible Kitchen Display Systems (KDS)' and 'other supported Kitchen Display Systems (KDS)' without enumerating one, and neither says the 'Infor KDS' named in the Functions menu is among them. (2) No configuration, key-mapping, pairing, driver or port procedure is published anywhere. The current Infor POS 2026.08 documentation library - all 374 topics across the user, em3admin, kadmin and posonapag guides - never uses the phrase 'bump bar'. The only KDS configuration Infor publishes is two printer-parameter fields, Consolidate and Print Summary, in 'Adding printer parameters for a logical printer'; neither concerns physical input. (3) The compatibility statement is joint across two separately marketed Infor restaurant POS lines, 'Infor SmartSeries and Infor POS systems', so the models are shared rather than established as Infor POS KDS peripherals, and the mounting-plate kit names the legacy 'Mk6/Ps600/Ultra-Touch/SmartSeries Bump Bar', which are not current Infor POS terminals. (4) The library's own KDS language is substantially third-party: the Kiosk Administration Guide says the order-ready text 'is sent by an integrated third party QSR kitchen display system (KDS)', and 'Specifying the mobile phone number of the guest' says 'The contents of the order notification is determined by your KDS. For details, contact your Infor POS representative.' Which KDS a site runs, and therefore whether it takes an Infor bump bar, is not settled by the published documentation. CONTROLS: tokenised word-boundary controls were run over all 374 topics of the 2026.08 library, with HTML comments stripped before tags and tags replaced by a separator so no table cells or inline spans were welded into false contiguity. 'bump bar' and 'bump-bar': 0 hits in 0 topics. Word-boundary bump-stem: 4 hits in 3 topics, every one of them ticket-bump semantics ('Bump Order', 'Expo bump', 'Describes bump times from the KDS'), none about hardware. Word-boundary KDS: 11 hits in 5 topics. 'kitchen display': 5 hits in 5 topics. CONTROL POISON, published because it nearly produced the opposite verdict: 'keypad' is NOT a usable control over this corpus. It returns 71 hits across 43 topics and every one of them is an ON-SCREEN NUMERIC KEYPAD - Enter User ID, Guests, Enter Table, Cash, Declare Tips, Shutdown Code, Pay Tips - that is, touchscreen UI, the exact opposite of the physical keypad this claim asks about. A 'keypad is present in the docs' reading would have been a false yes. The mirror control bounds the zero: 'touchscreen' returns 96 hits in 17 topics, so this library discusses input surfaces constantly, and the bump-bar silence is a genuine absence rather than a vocabulary gap. CORPUS BOUNDING: the storefront was read as a census, not a sample - pos.infor.com/products.json?limit=250 returned all 117 SKUs and the bump-bar and KDS entries above are the complete set. pos.infor.com/robots.txt (3,620 bytes, read whole) is a stock Shopify file allowing /products/ and /collections/ and barring only cart, checkout, orders, account and AJAX surfaces; nothing names ClaudeBot and no checkout surface was touched. Both product URLs and both documentation URLs were independently re-fetched at 200 with full-size bodies on 2026-09-15, not interstitials. No PDF-derived evidence is used in this cell in either direction: Infor's PDFs embed custom-encoded fonts whose control words extract as zero, so no absence recorded here rests on one. Grade C: the proposition rests on a first-party product-catalogue page written to sell. The corroborating 'Bump Order' function is grade B but does not itself mention a bump bar. https://pos.infor.com/products/infor-bump-bar · retrieved 2026-09-15 adversarially verified
An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.
kitchen-all-day-counts
Not scored by this record.
Configurable target cook times per station or order type, with visual color escalation and/or audible alert when a ticket exceeds target.
kitchen-sla-alerts
Not scored by this record.
If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator
kitchen-printer-fallback
Not scored by this record.
KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator
kitchen-offline-operation
Not scored by this record.
Station screens can display item-level build/assembly detail (recipe steps, portioning, or full modifier breakout) rather than only the ticket line text. differentiator
kitchen-item-build-screens
Not scored by this record.
Sectioned/fractional topping placement (halves, quarters, specific sections) is rendered visually and unambiguously on the make-line screen or ticket. differentiator
kitchen-pizza-fractional-display
Not scored by this record.
A bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order.
kitchen-recall-refire
Not scored by this record.
Edits made in the POS to an order already displayed in the kitchen visually flag the added, changed, or removed items on the live ticket. differentiator
kitchen-order-modification-alerts
Not scored by this record.
Bumping an order ready triggers a guest-facing notification — SMS/text, app push, or an order-status display board — without a separate product purchase. differentiator
kitchen-guest-ready-notification
Not scored by this record.
Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.
kitchen-waste-logging
Not scored by this record.
Reports actual ticket and per-station times (average and percentile) sliced by daypart, station, and order channel, exportable to CSV or an API.
kitchen-speed-of-service-reporting
Not scored by this record.
Generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list.
kitchen-prep-forecasting
Not scored by this record.
Delivery, dispatch & third-party channels
Product includes a native in-house driver module: drivers are first-class entities with clock-in/out, assignment state (in-store / on-run / returning), and per-driver run history reportable from the POS itself (not via a third-party add-on).
delivery-driver-roster
No driver entity exists anywhere in the product's published surface. The EM Administration Guide 3.0.27 is a complete field-by-field configuration reference, and its Employee management chapter enumerates every people object in the product — employee accounts, job codes with per-function POS privileges, job assignments, payment information, clock time records, edit history, employee classes — with no driver role, no assignment state (in-store/on-run/returning) and no run object. The word 'driver' occurs in the guide only as the tender 'Driver Param' COM-port field for payment-device integration; 'delivery' occurs exactly once, as the per-order-type field 'Mobile Delivery Method — Select the delivery method among pickup, delivery, or none'. The 56pp User Guide contains no occurrence of 'deliver' or 'driver' at all, and neither the EM nor the POS report catalogue lists a driver or run report. Consistent with the record's settled delivery-dispatch-board 'no': the only other delivery construct Infor documents is the Kiosk 'Deliver to Customer' completion message, meaning a runner brings the order to the guest. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/em3admin/pos_3.0.27_em3admin__en-us.pdf · retrieved 2026-08-04
Provides a dedicated dispatch/expo screen showing undispatched orders, driver availability, and elapsed time per order, with multi-order run batching (assigning 2+ orders to one driver as a single run).
delivery-dispatch-board
The EM Administration Guide 3.0.27 is a complete configuration reference (menu items, touchscreen, groups, tenders and discounts, employees and job codes, printing, reports) and contains no driver, dispatch, run or route object of any kind. The only delivery construct in the product is a per-order-type field, 'Mobile Delivery Method — Select the delivery method among pickup, delivery, or none', and in the Kiosk guide a 'Deliver to Customer' completion message meaning a runner brings food to the guest. The POS User Guide has no dispatch screen among its documented screens (command bar, functions menu, notification toolbar, main panel, navigation panel, check control toolbar, check view panel, right-hand menu). https://docs.infor.com/pos/3.0.27/en-us/useradminlib/em3admin/pos_3.0.27_em3admin__en-us.pdf · retrieved 2026-08-03
Dispatch includes a live map view with geocoded stops and system-generated route sequencing (turn order optimization) for a multi-stop run, not just a static address list. differentiator
delivery-route-map
Not scored by this record.
Captures live driver GPS position from a driver-facing mobile app and surfaces it back to the dispatch screen. differentiator
delivery-driver-tracking
Not scored by this record.
Delivery areas can be defined as arbitrary map polygons or by drive-time isochrones, not solely as a radius or a ZIP/postcode list. differentiator
delivery-zones-polygon
Not scored by this record.
Each delivery zone carries its own independently configurable delivery fee, order minimum, and quoted promise time, applied automatically from the validated customer address.
delivery-zone-pricing
No delivery zone object exists to price. The EM Administration Guide 3.0.27 enumerates the fee mechanisms available — discounts and service charges (assignable to family groups, menu items, job codes and order types) and tenders — none of which take a delivery area, an order minimum or a promise time, and there is no address-capture or geocoding step anywhere in the guide. The OrderNow Admin Portal Administration Guide's configuration task list is complete in eight items (store URL, QR code signage, scheduled orders, special instructions, payment-method logo, tips, Stripe connection, Kiosk translations) and contains no delivery fee or zone setting. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/em3admin/pos_3.0.27_em3admin__en-us.pdf · retrieved 2026-08-03
Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.
delivery-address-validation
Not scored by this record.
Tracks per-delivery driver compensation inputs — mileage or distance driven per run, per-delivery flat reimbursement, and driver-retained tips — and exports them to payroll as separate reimbursement vs. wage lines. differentiator
delivery-driver-comp
Not scored by this record.
Provides a driver cash bank / settle-up flow that reconciles cash collected, orders assigned, and tips owed at end of shift, producing a per-driver over/short figure.
delivery-cash-reconcile
Not scored by this record.
Can hand a first-party order to an on-demand courier marketplace (DoorDash Drive, Uber Direct, Nash, Relay or equivalent) natively from the POS, with the courier quote and status returning into the order record.
delivery-daas-dispatch
Not scored by this record.
Supports hybrid dispatch: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. differentiator
delivery-daas-fallback
Not scored by this record.
Offers direct, first-party certified API integrations with DoorDash, Uber Eats, and Grubhub marketplaces (vendor-owned, not solely resold through Otter/Deliverect/Chowly/ItsaCheckmate middleware). differentiator
delivery-3p-direct-integration
Not scored by this record.
Third-party marketplace orders inject automatically into the POS as normal tickets that fire to KDS/printers without tablet re-keying or manual accept.
delivery-3p-injection
Not scored by this record.
Marking an item or modifier 86'd in the POS pushes item-level out-of-stock status to connected third-party channels in near real time, and restores it on availability (DoorDash requires item and item-option 86ing of new POS partners).
delivery-86-sync
Not scored by this record.
Store can be paused/deactivated on each connected third-party marketplace from inside the POS with a timed auto-reactivation, rather than only from each marketplace's own tablet or portal.
delivery-store-pause
Not scored by this record.
Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. differentiator
delivery-3p-reconciliation
Not scored by this record.
Vendor exposes integration health to the operator — failed/rejected order injections, connection status per channel, and alerts on failure — rather than failing silently. differentiator
delivery-injection-error-visibility
Not scored by this record.
Guests receive a branded order status / driver tracking page or SMS link on the restaurant's own domain for first-party delivery orders, driven by real order and driver state.
delivery-tracking-page
Not scored by this record.
Quoted delivery promise times adjust dynamically from current kitchen load, driver availability, and zone drive time, rather than a fixed per-store constant. differentiator
delivery-promise-time
Not scored by this record.
Vendor documents explicit offline behavior for delivery: whether cash delivery orders, driver assignment, and driver settlement continue during an internet outage.
delivery-offline-behavior
Not scored by this record.
Digital ordering & guest-facing channels
Vendor ships a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission.
digital-first-party-web
CLAIM TESTED: a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission. VALUE partial, grade B, verified adversarially 2026-09-15. WHAT IS MET. The channel is first-party and is configured from the same back office as the POS: https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/imu1555619456690.html - "Infor POS Enterprise Manager is a hospitality technology solution which you can use to configure the user interface of these Infor products: Infor POS / Infor POS Kiosk / Infor POS OrderNow", and "you can select Self Serve Platforms to access Infor POS Kiosk configuration and Infor POS OrderNow Admin Portal". It is a web link a guest opens, not an app download: https://docs.infor.com/pos/2026.08/en-us/useradminlib/posonapag/yph1594970463711.html "Configuring the store URL" - "Create a branded and short link with a link shortener service. Click Mobile App Link. In the Unbranded Link section, click Copy Link. You can copy this link to a link shortener service. In the Branded Link field, paste the shortened link of the unbranded link." - and https://docs.infor.com/pos/2026.08/en-us/useradminlib/posonapag/fto1640838680879.html "Configuring the QR code signage" - "In the Branded Link field, specify the URL of the store", with a Display Branded Link signage check box, a Primary Branding Color drop-down and a store-logo upload. THE MENU AND THE ORDERS ARE THE POS's OWN, which is the conjunct that matters most and is met at grade B: the menu-item attribute "Mobile Name Specify the name of the menu item that is displayed in the mobile ordering app" sits beside Local Name and Kitchen Name on the same POS menu record (https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/bhx1568339621480.html); a modifier carries per-channel checkboxes, "POS To enable the modifier in Infor POS, select this check box. Mobile To enable the modifier in mobile ordering app, select this check box. Kiosk To enable the modifier in Infor POS Kiosk, select this check box" (https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/dqf1568788052662.html); images are uploaded per channel, "For Infor POS OrderNow, click Add image in the Mobile section" (https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/fpn1568362512734.html); serving periods carry a channel menu, "If the serving period is for Infor POS Kiosk and Infor POS OrderNow, then specify a menu" (https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/xav1568961249748.html). The terminal can switch the channel on and off - the Functions menu table gives it "Mobile Enables or disables mobile ordering" and "Online Ordering Enables or disables online ordering" (https://docs.infor.com/pos/2026.08/en-us/useradminlib/user/gog1555619772856.html) - and guest orders land on the kitchen's service clock: https://docs.infor.com/pos/2026.08/en-us/useradminlib/posonapag/bmm1640842899470.html "You can enable guests to submit advance orders. The allowable lead time is configured within the POS Control Options", with Kitchen Service Start/End relative to store open and close and "The schedule in the Online Ordering and Pickup Times table is updated." SHORTFALL 1, THE ADDRESS IS NOT THE RESTAURANT'S OWN DOMAIN. The OrderNow Admin Portal guide is a CLOSED list of 15 topics, re-derived from the library manifest rather than inherited: About this guide, overview, Accessing the portal, Configuration tasks, store URL, QR code signage, future orders and special instructions, custom logo for payment methods and card integration branding, tips, Stripe, Elavon, FreedomPay, Shift4, Kiosk menu-name translations, and the guide cover. There is no custom-domain, DNS, CNAME, white-label or site-theme topic in it. The only documented branding levers are pointing a third-party link shortener at an Infor-issued unbranded link, a Primary Branding Color and a logo on the QR SIGNAGE artwork, and payment-method icons ("Adding a custom logo to payment methods and card integration branding"). An Infor-issued URL wearing a shortener alias is materially short of the restaurant's own domain. SHORTFALL 2, THE COMMERCIAL MODEL IS NOT STATED BY ANY FIRST-PARTY SOURCE, so commission-free is unevidenced in either direction and is NOT scored as met. What the documentation does establish, as a grade-B fact rather than an inference, is where the money lands: the operator connects their OWN merchant accounts - Elavon, FreedomPay, Shift4 ("specify the public key and secret key", gated by a job-code permission named "Online Ordering Payment Admin") and Stripe ("Click Connect with Stripe. This action redirects to the Stripe website, where you must login and proceed with necessary actions"). Infor is therefore not the merchant of record and funds do not settle through it, which is consistent with a licensed module rather than a marketplace; it is not a statement that no per-order fee is charged, and no such statement exists. CONTROLS, tokenised, ZERO IN BOTH INSTRUMENTS: commission 0, commissions 0, fee 0, fees 0, per-order 0, rake 0, marketplace 0, "merchant of record" 0, "custom domain" 0, DNS 0, CNAME 0, subdomain 0, "white label" 0, "white-label" 0. Non-zero: OrderNow 21 topics / 48 hits, "online ordering" 3 topics, branding 7, branded 2 (both the Branded Link field), URL 9, Stripe 9, Elavon 2, FreedomPay 2, Shift4 2. TWO INSTRUMENTS. Every control below was re-run by the verifier, tokenised on word boundaries (hyphen and whitespace treated as equivalent, phrases matched across line wraps), over two independent renderings of the same library: (i) the 374 raw HTML topics, comments stripped with <!-- --> removed BEFORE tags and every tag replaced by a SPACE so no <dt>/<dd> or table cell can be welded into a false quote; and (ii) a fresh pdftotext extraction of the four published 2026.08 PDFs (em3admin, kadmin, posonapag, user; 299,267 characters). The earlier claim that Infor PDFs are a poisoned corpus is FALSE for these four and was retired: pdftotext reads them cleanly (positive control Infor = 671 occurrences across the four). A previously cached extraction of the same PDFs in .cache/q310-infor-hospitality/txt-*.txt IS cid-mangled garbage ("Infor" renders as ") ! * -"); it was produced by a different extractor and must not be used. HTML positive controls on tag-stripped text: Infor 242 topics / 661 hits, menu 186 / 925, report 40 / 179, employee 42 / 195, discount 39 / 130, tax 23 / 144, printer 16 / 63. PDF positive controls: Infor 671, menu 767, report 148, employee 165, discount 114, tax 111, printer 55. Both instruments agree on every figure quoted below. MANIFEST BOUND: https://docs.infor.com/pos/2026.08/en-us/useradminlib/sitemap.html, re-derived by me on 2026-09-15, carries 375 .html anchors = 1 library root + 374 topics, distributed user 148 / em3admin 146 / kadmin 65 / posonapag 15. All 374 are on disk and were read as RAW bytes; the on-disk distribution matches the sitemap exactly, so the zero is bound to the publisher's own manifest with no gap. GATE: the companion library /pos/2026.08/en-us/technical/ returns HTTP 200 carrying an identical 1,840-byte SAML auto-submit form to mingle-sso.us2.prd3.inforcloudsuite.com ("Access rights validated") for both its default.html and its sitemap.html. That is a login wall, not an absence; it caps every absence here at grade B and grade A is not available on this vendor. POISON FOUND, recorded so it is not re-derived. (1) "domain" reads 374 of 374 HTML topics and 760 hits, and 0 in all four PDFs. The 374 are the Oxygen WebHelp template's own JavaScript, isKnownServer(domain); a naive HTML-only control would have manufactured a positive for custom-domain support out of page chrome. The PDF instrument is what discriminates it. (2) "current" likewise reads 374 of 374 HTML topics but only 2 PDF documents - template chrome again; it is worthless as a control and was discarded. (3) "count" is the trap of the inventory cells: 14 HTML topics, 56 hits, and not one is a stock count - the senses are the sales COUNTDOWN (Set Count, Count List, Remove Countdown, Daily Default, Carryover Remainder), the GUEST COUNT / COVER COUNT / CHECK COUNT / TABLE COUNT / VOID QUANTITY report columns, "Covers - Counts covers in a check", and "calorie count". A substring search would have read this as inventory counting. (4) "stock" reads 5 topics and every hit is "stock keeping unit" (the free-text Vendor SKU field), "Out of Stock" in the countdown colour legend, or the Kiosk "Hide Out-of-Stock Items" toggle. (5) "inventory" reads exactly 1 topic and 1 hit, inside the countdown topic: "Color indicators are integrated into the names of menu items to visually represent inventory status." (6) "components" reads 13 topics but resolves to Infor POS Kiosk hardware components and to the Data Distribution Service "communication between various components, such as terminals, kitchen displays, and reporting systems" - never a recipe component. (7) "batch" is Batch Export of bookmarked reports. (8) "86" reads 0 in HTML and 2 in PDF, and both PDF hits are the page number 86 - not the 86ing sense. (9) "real time" reads exactly 1 topic in both instruments and it is the Terminal Health dashboard, DEVICE TELEMETRY, a homonym of a sales dashboard that must never be cited as one. (10) "physical" is physical printers and physical user cards; "prep" is "Prep time" in the Speed of Service report; "portion" is "the tendered portion of the check"; "vendor" is "vendor stock keeping unit". THE DOMAIN TRAP IS THE ONE THAT WOULD HAVE FLIPPED THIS CELL: "domain" reads 374 of 374 HTML topics and 760 hits, and 0 across all four PDFs, because every WebHelp page ships an isKnownServer(domain) script. An HTML-only control would have manufactured evidence of custom-domain support out of page chrome; the second instrument is what proves the prose figure is zero. ADVERSE EVIDENCE WEIGHED AND NOT LEANED ON: the 2020 press release www.infor.com/news/infor-contactless-ordering-hospitality calls OrderNow "a responsive web application" that "is easily embeddable in a customer's own web environment", which would strengthen the own-branding conjunct - it is grade D, six years old, and no current first-party page or doc topic repeats the embeddability claim. The grade-D resource page www.infor.com/resources/infor-pos-ordernow says "OrderNow is an integral part of the Infor POS restaurant point of sale platform" and corroborates the channel only. The SSO-gated /technical/ library could document a domain-mapping step; that is a login wall, not an absence, and it caps this at grade B. https://docs.infor.com/pos/2026.08/en-us/useradminlib/posonapag/yph1594970463711.html · retrieved 2026-09-15 adversarially verified
Vendor offers a branded native iOS and Android ordering app (published under the restaurant's own brand in the App Store/Play Store), not only a mobile web page or a shared multi-restaurant marketplace app. differentiator
digital-native-app
Not scored by this record.
Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels.
digital-account-saved-payment
CLAIM UNDER TEST: guests can create an account with saved addresses, saved tokenized payment methods, and one-tap reorder of a previous order across first-party channels. VERDICT no: Infor's first-party guest ordering channel ships no guest account at all, offers no path to save or re-present a payment method, and has no reorder surface; what it remembers is one browser's autofill strings. WHAT IS MET AND WHAT IS ABSENT. Met, in a degenerate form only: a remembered address, one string, in one browser, with no account behind it. Absent: account creation, an address book, a second address, any saved or re-presentable card, and any reorder or order-history surface. A partial was considered and rejected because it would shortfall the account, the saved card and the reorder, which is self-refuting. THE CLIENT CORPUS AND HOW IT WAS BOUNDED. The verifier rebuilt the corpus independently rather than inheriting it. index.html at https://ordernow.hpo.inforcloudsuite.com/ names main-LVLHA3PY.js, polyfills-Z6E3LSDP.js and three modulepreloaded chunks; every fetched file was then re-grepped for further chunk/main/polyfills/runtime/styles/vendor script names and the new ones fetched, repeating until the set stopped growing. It closed after three rounds at 28 files and 1,991,970 bytes, every one HTTP 200. The closure was then bound to the PUBLISHER'S OWN MANIFEST rather than to the fact that it stopped growing: the Angular service worker manifest at /ngsw.json (200, 34,169 bytes) hash-tables 270 assets of which exactly 28 are .js, and that set is identical to the closure, with nothing in the manifest unfetched and nothing fetched that the manifest does not list. The remaining 242 assets are images, fonts, a stylesheet, /index.html, /manifest.webmanifest and five /assets/i18n/*.json files; those i18n files were fetched too and are ngx-translate scaffolding stubs of 200 to 387 bytes ('Hello Angular with ngx-translate!'), so they are not a translation dictionary hiding UI labels. No source map is published: main, polyfills and two chunks all 404 on .js.map, a fabricated sibling chunk-ZZZZZZZZ.js.map 404s identically, and no file contains a sourceMappingURL, so this is minified source read as raw bytes. The host has no robots.txt (404) and returns an honest 404 on a nonsense path, so it is not a soft-200 catch-all and nothing bars it. THE HOST IS INFOR'S OWN MULTI-STORE CHANNEL, NOT ONE CUSTOMER'S TENANT. The bundle carries the production environment literal {production:!0, environmentName:'', hostName:'ordernow.hpo.inforcloudsuite.com', apiUrl:'https://api.vivonet.com', gaTrackingCode:'UA-170266735-1', stripeApiKey:'pk_live_...'}, the application constant App={name:'Infor OrderNow'}, and /manifest.webmanifest reads {name:'Infor OrderNow', short_name:'OrderNow', description:"Infor's Contactless Ordering Application"}. It is not a single property's deployment: the Angular route table is rooted on a parameter, path ':store_id' and ':store_id/start', and every API call is built as /v1.1/stores/${storeId}/..., /mobile/stores/${storeId}/manifests, /admin/stores/${storeId}/configuration and /shift4/keys/${storeId}, so one build serves arbitrary stores. The channel enumeration is also closed at the vendor's own word: Infor's OrderNow brochure states the product is a responsive web application and that 'an app download is not required', and a search of the App Store catalogue of Infor (US), LLC returns 27 published apps, none of them a guest ordering app. OrderNow web is therefore the first-party digital ordering channel, not one of several. WHAT THE CODE SHOWS. The guest record is a browser key-value bag and it is a CLOSED enumeration: App={name:'Infor OrderNow'}, LocalStorageKeys={currentOrderNumber, currentOrder, currentMenuId, lastEmail, lastFirstName, lastLastName, lastPhone, lastAddress, lastCategory, atriumCard, lastTenderId, lastTenderName, usePaymentRequest, lastPickupTime, lastSearchTerm, lastSelectedDietaryPreferences, guestSession, guestPortal, lastPosVersion, lastPartnerApiVersion, lastInternalApiVersion, ssoLastPath}. Twenty-two keys, not one of them a card, a card token, a customer id, an address book or an order list. They are filled on blur and re-read on re-entry, e.g. 'addressFocusOut(r){this.localStorage.setItem(x.LocalStorageKeys.lastAddress,this.guestAddress),...}' and 'let r=this.localStorage.getItem(x.LocalStorageKeys.lastPhone);this.phoneForm.get("phone")?.setValue(r)'. WHY THE VERDICT DOES NOT REST ON THAT localStorage FINDING. Browser-local autofill does not by itself refute a saved payment method on an account: a card could in principle be vaulted server side at api.vivonet.com and simply not be exercised by this flow. That objection was tested directly against the code and fails. There is no client-side vocabulary for a stored instrument anywhere in the 1,991,970 bytes: customerId 0, stripeCustomer 0, ephemeralKey 0, setupIntent 0, savePaymentMethod 0, maskedPan 0, lastFour 0, expiry 0. The only last4/expMonth/paymentMethodId occurrences are inside the Shift4 flow that tokenises the card the guest has just typed, for that one transaction (it assembles l.paymentMethod.cardNumber from f.first6, six literal asterisks and f.last4, then sends it with that order), and paymentMethodId is a POS tender-method integer initialised to 0. The payment step always mounts a fresh processor element, Stripe .create('card'), Shift4 createComponent('card').mount('#shift4-card'), and the name field is a plain input marked autocomplete='cc-name', i.e. it delegates recall to the browser, which is what a form does when there is nothing on file. The per-order field list is itself a closed enumeration of require* flags: requireGuestFirstName, requireGuestLastName, requireGuestEmail, requirePhoneNumber, requireGuestRoomNumber, requireGuestCount, requireGuestCreditCard, requireCustomCardNumber, requireNameOnCard, every one a 'require this field on this order' toggle; and the complete show*/allow*/enable* config surface (allowMultiplePayments, allowTipping, showAppleGooglePayButtons, showBalanceOnReceipt, showBalanceOnTender, showCustomPaymentUi, showStoreHours and twelve more) contains no saved-card, account or reorder flag. A server feature flag cannot conjure UI that is absent from the shipped code, and a vault no client can reach is not a guest capability. The email field's own helper text is 'We will email your paperless receipt. No spam from us.', a receipt destination rather than an account. THE ONLY THING CALLED AN ACCOUNT IS SOMEONE ELSE'S BALANCE. The header avatar renders with aria-label 'Account balance' and binds to this.atrium.profile, an Atrium campus-card SSO identity federated through a Cognito hosted UI to a per-store identity_provider, yielding only firstName, a photo and tender balances. Separately guestSession/guestPortal are a hotel PMS deep link read off the query string and exchanged at /mobile/hotelOperation/guestPortalReservationInfo?bearerToken=. Both are borrowed identities from a stored-value system or a property management system; neither is an OrderNow account the guest creates and neither carries a saved card. Whether a declining-balance campus tender counts as a saved payment method was considered and rejected: it is a third party's account resolved at login, and the reorder conjunct is absent regardless. CONTROLS OVER THE 1,991,970-BYTE, 28-FILE CLOSURE, ALL WORD-BOUNDARY, ALL RE-RUN BY THE VERIFIER AND ALL ZERO: savedCard 0, saveCard 0, cardOnFile 0, storedCard 0, setupIntent 0, savePaymentMethod 0, tokenize 0, tokenized 0, vault 0, rememberMe 0, remember 0, save 0, saved 0, reorder 0, orderHistory 0, pastOrder 0, pastOrders 0, previousOrder 0, favorites 0, favourite 0, createAccount 0, myAccount 0, addressBook 0, loyalty 0, points 0, rewards 0, member 0, membership 0. Positive controls over the same bytes, which prove the script and the corpus: stripe 67, freedompay 39, shift4 33, elavon 9, atrium 49, address 43, email 35, phone 22, guest 25, oauth 30, cognito 53. No positive control read zero. SECOND, INDEPENDENT CORPUS: THE PUBLISHED ADMIN GUIDE. The Infor POS OrderNow Admin Portal Administration Guide 2026.08 is a CLOSED 15-topic manifest, and the verifier re-derived its titles from the 15 files rather than from the note: About this guide, OrderNow overview, Accessing the Admin Portal, Configuration tasks, Configuring the store URL, Configuring the QR code signage, Configuring future orders and special instructions, Adding a custom logo to payment methods and card integration branding, Configuring tips, Configuring Elavon as payment solution, Configuring FreedomPay as payment solution, Configuring Shift4 as payment solution, Connecting with Stripe, Configuring translations for menu item names in Infor Kiosk. No guest account, no card on file, no reorder setting. This generation adds three payment-provider topics the retired 3.0.27 library did not carry, so the guide is actively maintained and its silence is current. Across all 374 topics, word boundary: reorder 0, tokenization 0, vault 0, PCI 0. POISON IN THE CLIENT BUNDLE, all of it reproduced by the verifier on word boundaries over the full 1,991,970 bytes. A naive reader gets oauth 30, cognito 53, token 156, history 73, profile 63, card 93, account 14, signup 3, wallet 5 and would publish a false cell from any of them. oauth and cognito are AWS Amplify internals plus the one real guest SSO endpoint described below; signup 3 is Amplify's own enumeration and error strings ('password is required to signUp'), not a sign-up screen; token is Amplify and JWT plumbing plus Shift4's single-transaction tokenPaymentMethodType; history is the browser History API and Angular router state such as 'history.state?.editIndex'; profile is the Atrium avatar component and its CSS class names; card is overwhelmingly the Bootstrap .card layout class, appearing in the const arrays of at least eight unrelated components; account is mostly Amplify's connectedAccounts and error text. The four flags requireLowercase, requireUppercase, requireNumbers and requireSpecialCharacters look like an account signup password policy and are Amplify's Cognito password-policy parser, not an Infor surface. Finally '_lastOrder' is a tax-calculation memo cache that JSON.stringify-compares an order to skip a repeat /orders/data call, and is NOT an order-history store. POISON IN THE DOC CORPUS, tokenised and reproduced by the verifier: key 1,135 hits and URL 1,164 and XML 744 are all Oxygen WebHelp chrome across all 374 topics and carry no product meaning; favorite 16 is the WebHelp Favorite button, four hits in each of the four default.html shells and nowhere else, not a guest favourites feature; REST 1 is the sentence 'The rest of the reports must be exported in a new tab'; merge 9 is seven hits of 'Merging checks' in user/ueu1576570123604.html plus two incidental, never a profile merge; prep 1 is 'Prep time' in a report definition; 'stored value' resolves to stored-value cards, not a payment vault. MANIFEST AND GATE. docs.infor.com/sitemap.xml (234,123 bytes, 1,771 loc elements, re-fetched whole 2026-09-15 by the verifier) lists exactly four Infor POS libraries: /pos/2026.08/en-us/useradminlib/, /pos/2026.08/en-us/technical/, and the same pair for 2026.05. The 2026.08 useradminlib sitemap.html (28,297 bytes) resolves to 375 hrefs, which is 374 topic files in four folders (user 148, em3admin 146, kadmin 65, posonapag 15, four of which are the per-guide default.html tables of contents) plus one top-level shell, so 2026.08 publishes FOUR guides and not five; the EMv1 guide of the retired 3.0.27 library is gone. All 374 were fetched at 200 and searched as RAW HTML with only HTML comments stripped and every control word matched on word boundaries; tag stripping was not used, because it welds table cells into false quotes. Doc corpus 4,472,753 bytes; corpus controls pass, Infor 3,827 menu 2,267 check 1,274 print 1,212 kiosk 503. The second per-version /technical/ library is a login wall, not an absence: https://docs.infor.com/pos/2026.08/en-us/technical/sitemap.html answers HTTP 302 to /docs/sso?contentUri=%2Fpos%2F2026.08%2Fen-us%2Ftechnical%2Fsitemap.html and a SAML auto-submit form; it was not evaded and it caps every absence recorded here. The superseded 3.0.27 library still answers 200 (25,937 bytes, re-probed 2026-09-15) and is an archived generation, not a dead link. A second rendering instrument does exist and was checked. The 2026.08 PDFs are UNLINKED - no topic references one and sitemap.xml has no PDF entry - but they are served at the same path pattern the 3.0.27 generation used, and all four return 200 (user 1,618,213 B; em3admin 2,125,483 B; kadmin 730,794 B; posonapag 302,954 B). pdftotext extracts them cleanly, 299,267 characters with a positive control of Infor=671, and the API-vocabulary zeros reproduce in them. An earlier note's claim that Infor's PDFs are unreadable because of a custom-encoded font is FALSE: that artefact came from one broken cached extraction, not from the files. CAVEATS AND WHY THE GRADE IS A. (1) Grade A was challenged explicitly and sustained. The cited source is the vendor's own production client code, which the atlas already grades A in 150 cells across other vendors including absence verdicts, and the file set is bound here to the publisher's own ngsw.json manifest rather than to a crawl that merely stopped growing, which is a stronger bound than a closure alone. (2) An Infor-hosted API at api.vivonet.com is live and unread: /status answers anonymously {"appVersion":"2.9.0.127","appName":"vvnapi"} while /swagger.json, /openapi.json, /v3/api-docs, /robots.txt and a nonsense control path all return honest JSON 404s, so it is not a soft-200 host but it publishes no contract. (3) The SAML-gated /technical/ library could document an account API. Neither of those can put an account, a card selector or a reorder button into a shipped bundle that contains none of the three, which is why the absence is positive rather than merely unfound. (4) The bound is Infor's own hosted OrderNow deployment plus the published admin guide; an operator could of course put a different ordering front end in front of Infor POS, and the POS and kiosk channels were assessed only from the documentation. https://ordernow.hpo.inforcloudsuite.com/main-LVLHA3PY.js · retrieved 2026-09-15 adversarially verified
Digital checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator
digital-upsell-engine
Not scored by this record.
Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.
digital-scheduled-pacing
Not scored by this record.
Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.
digital-fulfillment-modes
Not scored by this record.
Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.
digital-qr-table
Not scored by this record.
Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator
digital-kiosk
Not scored by this record.
Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.
digital-group-ordering
Not scored by this record.
Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator
digital-catering-portal
Not scored by this record.
Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator
digital-voice-ai-phone
Not scored by this record.
Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.
digital-drivethru-ai
Not scored by this record.
Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.
digital-sms-ordering
Not scored by this record.
Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator
digital-google-order
Not scored by this record.
Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.
digital-apple-business-connect
Not scored by this record.
Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.
digital-loyalty-attach
Not scored by this record.
Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.
digital-subscriptions
Not scored by this record.
Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.
digital-promo-parity
Not scored by this record.
Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator
digital-guest-data-ownership
Not scored by this record.
Digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.
digital-checkout-pci-sca
Not scored by this record.
Digital channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator
digital-surcharge-transparency
Not scored by this record.
Guest data, loyalty & marketing
Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.
guest-loyalty-unified-profile
CLAIM UNDER TEST: maintains a single guest profile that automatically merges transactions from in-store POS, first-party web or app ordering and kiosk under one identity matched on phone or email, with documented dedup or merge behaviour. VERDICT no: Infor POS holds no guest record of any kind; the only guest identity in the product belongs to a third-party loyalty or stored-value provider, and the first-party web channel carries no loyalty identity at all. WHAT IS MET AND WHAT IS ABSENT. Met: nothing of the claim. The POS and the kiosk can both resolve a guest by loyalty card number or mobile number, which is the nearest thing to an identity match, but they resolve it to the PROVIDER's profile. Absent: any Infor-side guest, customer, member or profile entity for those channels to merge into; any web-channel loyalty identity; and any documented dedup or merge rule. A partial was considered on the strength of the card-number and mobile-number lookup and rejected, because with no Infor-held record, no web channel and no merge rule it would shortfall every conjunct and be self-refuting. THE ENTERPRISE MASTER-DATA SURFACE IS ENUMERATED AND HAS NO CUSTOMER IN IT. The Infor POS Enterprise Manager Administration Guide 2026.08, 146 topics, publishes its complete table of contents, and its domains are Revenue center, Menu item management, Touchscreen menu management, Groups management, Itemizers, HMS transaction code mapping, Tender and discount management, Employee management, Store management, Printing management, Table management, Reports management, Dynamic reports and Terminal health dashboard. EM is where every record in Infor POS is created, menu items, taxes, tenders, stores, revenue centres, tables, employees, job codes and employee classes, and there is no guest, customer, member or profile entity anywhere in it. The only person record is the employee: 'Adding an employee account', 'Modifying the personal information of an employee', 'Viewing the edit history of an employee'. That is an enumerated absence in the system of record, not a failure to find a page. GUEST IDENTITY IS THE LOYALTY PROVIDER'S, AND INFOR SAYS SO. Infor POS User Guide 2026.08, 'Viewing and printing the points balance of a loyalty card' (user/baf1558937756127.html, breadcrumb Stored-value cards > Loyalty card interactions): 'From the functions menu, tap the function button of the loyalty card provider.' / 'In the on-screen keypad, specify the loyalty card number. Optionally, specify the phone number of the guest.' / 'In the Loyalty Points window, tap Print to print the points balance and available discounts or rewards.' / 'The Loyalty Points window opens the profile of the loyalty card user.' The profile is opened, not maintained, and the window belongs to the provider. The Kiosk repeats the pattern from the other side, 'Applying a discount or reward using loyalty points' (kadmin/cej1575976360770.html): 'In the Order Summary pane, tap LOGIN. Swipe your loyalty card through the magnetic stripe reader (MSR). Optionally, specify your mobile number and tap Login.' The kiosk's 'Payment and loyalty' topic (kadmin/voc1706242421151.html) configures only whether the provider's logo appears on the home screen. THE FIRST-PARTY WEB CHANNEL HAS NO LOYALTY IDENTITY AT ALL. THE CLIENT CORPUS AND HOW IT WAS BOUNDED. The verifier rebuilt the corpus independently rather than inheriting it. index.html at https://ordernow.hpo.inforcloudsuite.com/ names main-LVLHA3PY.js, polyfills-Z6E3LSDP.js and three modulepreloaded chunks; every fetched file was then re-grepped for further chunk/main/polyfills/runtime/styles/vendor script names and the new ones fetched, repeating until the set stopped growing. It closed after three rounds at 28 files and 1,991,970 bytes, every one HTTP 200. The closure was then bound to the PUBLISHER'S OWN MANIFEST rather than to the fact that it stopped growing: the Angular service worker manifest at /ngsw.json (200, 34,169 bytes) hash-tables 270 assets of which exactly 28 are .js, and that set is identical to the closure, with nothing in the manifest unfetched and nothing fetched that the manifest does not list. The remaining 242 assets are images, fonts, a stylesheet, /index.html, /manifest.webmanifest and five /assets/i18n/*.json files; those i18n files were fetched too and are ngx-translate scaffolding stubs of 200 to 387 bytes ('Hello Angular with ngx-translate!'), so they are not a translation dictionary hiding UI labels. No source map is published: main, polyfills and two chunks all 404 on .js.map, a fabricated sibling chunk-ZZZZZZZZ.js.map 404s identically, and no file contains a sourceMappingURL, so this is minified source read as raw bytes. The host has no robots.txt (404) and returns an honest 404 on a nonsense path, so it is not a soft-200 catch-all and nothing bars it. Over that corpus, word boundary: loyalty 0, points 0, rewards 0, member 0, membership 0, favorites 0, createAccount 0, myAccount 0, orderHistory 0, reorder 0. Positive controls over the same bytes: stripe 67, freedompay 39, shift4 33, elavon 9, atrium 49, guest 25, address 43, email 35, cognito 53; none read zero. The guest in OrderNow is a per-order field list, requireGuestFirstName, requireGuestLastName, requireGuestEmail, requirePhoneNumber, requireGuestRoomNumber, requireGuestCount, cached in that browser's localStorage under co-last-first-name, co-last-email, co-last-phone and co-address. The one thing the client calls a profile is the Atrium campus-card SSO identity behind an avatar whose aria-label is literally 'Account balance', yielding firstName, a photo and tender balances from an external stored-value system. THE HOST IS INFOR'S OWN MULTI-STORE CHANNEL, NOT ONE CUSTOMER'S TENANT. The bundle carries the production environment literal {production:!0, environmentName:'', hostName:'ordernow.hpo.inforcloudsuite.com', apiUrl:'https://api.vivonet.com', gaTrackingCode:'UA-170266735-1', stripeApiKey:'pk_live_...'}, the application constant App={name:'Infor OrderNow'}, and /manifest.webmanifest reads {name:'Infor OrderNow', short_name:'OrderNow', description:"Infor's Contactless Ordering Application"}. It is not a single property's deployment: the Angular route table is rooted on a parameter, path ':store_id' and ':store_id/start', and every API call is built as /v1.1/stores/${storeId}/..., /mobile/stores/${storeId}/manifests, /admin/stores/${storeId}/configuration and /shift4/keys/${storeId}, so one build serves arbitrary stores. The channel enumeration is also closed at the vendor's own word: Infor's OrderNow brochure states the product is a responsive web application and that 'an app download is not required', and a search of the App Store catalogue of Infor (US), LLC returns 27 published apps, none of them a guest ordering app. OrderNow web is therefore the first-party digital ordering channel, not one of several. The claim's three-channel merge therefore fails outright on the web channel. CONTROLS OVER THE 374-TOPIC, 4,472,753-BYTE 2026.08 MANIFEST, WORD-BOUNDARY, ALL RE-RUN BY THE VERIFIER: dedup 0, unified 0, profile 1 and that single hit is the loyalty PROVIDER's profile quoted above, customer 16 across 7 topics and none is a customer record but phrases such as 'customers can provide special instructions', loyalty 87 across 15 topics and every one of those topics was listed and the substantive ones read, all of them the provider's card, the densest being 'Applying a discount or reward with loyalty points' 16, 'Viewing and printing the points balance of a loyalty card' 16 and the kiosk equivalent 13, with the rest under Stored-value cards, tender-ID balance inquiry and integrated tenders. Corpus controls pass: Infor 3,827, menu 2,267, check 1,274, print 1,212, kiosk 503. THE TRAPS. merge scores 9 and reads like profile merging; seven of the nine are in user/ueu1576570123604.html, whose title is 'Merging checks', combining two open checks at a table. account scores 94 across 20 topics and every one is a GL or accounting object ('Adding an account itemizer', 'Adding an account' under Groups management, 'Account' as a tender field) or an employee account; the POS Functions-menu button 'Account Inquiry - Shows the API-based accounts' is a house-account or stored-value lookup, not a guest CRM record. POISON IN THE DOC CORPUS, tokenised and reproduced by the verifier: key 1,135 hits and URL 1,164 and XML 744 are all Oxygen WebHelp chrome across all 374 topics and carry no product meaning; favorite 16 is the WebHelp Favorite button, four hits in each of the four default.html shells and nowhere else, not a guest favourites feature; REST 1 is the sentence 'The rest of the reports must be exported in a new tab'; merge 9 is seven hits of 'Merging checks' in user/ueu1576570123604.html plus two incidental, never a profile merge; prep 1 is 'Prep time' in a report definition; 'stored value' resolves to stored-value cards, not a payment vault. MANIFEST AND GATE. docs.infor.com/sitemap.xml (234,123 bytes, 1,771 loc elements, re-fetched whole 2026-09-15 by the verifier) lists exactly four Infor POS libraries: /pos/2026.08/en-us/useradminlib/, /pos/2026.08/en-us/technical/, and the same pair for 2026.05. The 2026.08 useradminlib sitemap.html (28,297 bytes) resolves to 375 hrefs, which is 374 topic files in four folders (user 148, em3admin 146, kadmin 65, posonapag 15, four of which are the per-guide default.html tables of contents) plus one top-level shell, so 2026.08 publishes FOUR guides and not five; the EMv1 guide of the retired 3.0.27 library is gone. All 374 were fetched at 200 and searched as RAW HTML with only HTML comments stripped and every control word matched on word boundaries; tag stripping was not used, because it welds table cells into false quotes. Doc corpus 4,472,753 bytes; corpus controls pass, Infor 3,827 menu 2,267 check 1,274 print 1,212 kiosk 503. The second per-version /technical/ library is a login wall, not an absence: https://docs.infor.com/pos/2026.08/en-us/technical/sitemap.html answers HTTP 302 to /docs/sso?contentUri=%2Fpos%2F2026.08%2Fen-us%2Ftechnical%2Fsitemap.html and a SAML auto-submit form; it was not evaded and it caps every absence recorded here. The superseded 3.0.27 library still answers 200 (25,937 bytes, re-probed 2026-09-15) and is an archived generation, not a dead link. A second rendering instrument does exist and was checked. The 2026.08 PDFs are UNLINKED - no topic references one and sitemap.xml has no PDF entry - but they are served at the same path pattern the 3.0.27 generation used, and all four return 200 (user 1,618,213 B; em3admin 2,125,483 B; kadmin 730,794 B; posonapag 302,954 B). pdftotext extracts them cleanly, 299,267 characters with a positive control of Infor=671, and the API-vocabulary zeros reproduce in them. An earlier note's claim that Infor's PDFs are unreadable because of a custom-encoded font is FALSE: that artefact came from one broken cached extraction, not from the files. CAVEATS. (1) The absence is of a NATIVE Infor guest profile. An operator who buys an external loyalty platform may well get a unified profile from that vendor; the claim asks what the POS maintains, and the answer is nothing. (2) Infor markets 'It integrates with loyalty programs and third-party platforms', which is consistent with, not contrary to, this verdict, since integration is exactly the delegation described above. (3) The SAML-gated /technical/ library could describe a guest API, but it could not add a customer entity to an EM configuration tree that the admin guide enumerates in full, nor loyalty code to an OrderNow bundle that contains none. Grade B rather than A because the load-bearing instrument here is the administration guide, with the client code as corroboration. (4) The Kiosk guide's disclaimer that 'some features described in this guide may not apply to your Infor POS Kiosk' warns that the guides may over-describe a given subscription, not that they under-describe the product. https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/default.html · retrieved 2026-09-15 adversarially verified
Orders arriving from third-party marketplaces (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. differentiator
guest-loyalty-thirdparty-identity-attach
Not scored by this record.
Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.
guest-loyalty-accrual-models
Accrual is not configurable in the product because loyalty itself is delegated to an external provider — precisely the bolt-on the claim excludes. User Guide 3.0.27 ch.5 classes loyalty cards as stored-value cards whose 'value is contained in the card and not with a financial institution', and every documented loyalty interaction routes through 'the tender button of the stored-value card provider' or 'the function button of the loyalty card provider': the POS can look up a card by number or guest phone number, apply a provider-issued discount or reward, and view or print the points balance — nothing else. The EM Administration Guide, the product's only administrative surface, is complete in eight chapters (overview, menu items, touchscreen menus, groups, tenders/discounts, employees, printing, reports) and contains no loyalty configuration of any kind — no points-per-dollar rate, no visit/punch counter, no spend tier. The only 'points' objects in EM are campus meal-plan fields (CashEQ Meal Periods with Meal Point Value and Max Points Per Period), which are cafeteria board plans, not loyalty accrual. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/user/pos_3.0.27_user__en-us.pdf · retrieved 2026-08-04
Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator
guest-loyalty-tiers
Not scored by this record.
Documents explicitly what loyalty lookup, accrual, and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). differentiator
guest-loyalty-offline-behavior
Not scored by this record.
Offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. differentiator
guest-loyalty-offer-stacking-rules
Not scored by this record.
Offers can be issued to a dynamically defined audience (rules over recency, frequency, spend, or items purchased) rather than only broadcast to the whole list. differentiator
guest-loyalty-targeted-offers
Not scored by this record.
Automatically computes recency/frequency/monetary or equivalent lifecycle segments (new, regular, at-risk, lapsed, VIP) without the operator building the queries. differentiator
guest-loyalty-rfm-segmentation
Not scored by this record.
Ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns rather than one-off manual sends.
guest-loyalty-lifecycle-automation
Enterprise Manager is the only administrative surface Infor publishes for this product and its chapter list is complete — menu item management, touchscreen menu management, groups management, tender and discount management, employee management, printing management, reports management. There is no campaign, marketing, email or SMS module in it, and no trigger, audience or send-schedule object anywhere in the guide. The loyalty functions Infor documents in the POS are limited to looking up a card, printing a points balance and applying a provider-issued discount or reward at the register; birthday, first-visit and win-back automations are not part of the product. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/em3admin/pos_3.0.27_em3admin__en-us.pdf · retrieved 2026-08-03
Sends both email and SMS campaigns natively from the platform, not solely by handing the list to a third-party ESP. differentiator
guest-loyalty-native-email-sms
Not scored by this record.
Captures per-channel marketing consent with timestamp and source of consent, and honors revocation received by any reasonable means (not just the STOP keyword) across all channels.
guest-loyalty-consent-management
Not scored by this record.
Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.
guest-loyalty-10dlc-registration
Not scored by this record.
Reports redemption and incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. differentiator
guest-loyalty-campaign-attribution
Not scored by this record.
Provides self-serve export of the full guest list and transaction history, including contact PII, via CSV or API, without a vendor fee or support ticket. differentiator
guest-loyalty-data-export-portability
Not scored by this record.
Exposes a documented outbound guest and order event API or webhook stream that a CDP or marketing platform can subscribe to (e.g. Olo, Punchh, Bridg, Klaviyo). differentiator
guest-loyalty-cdp-event-api
Not scored by this record.
Triggers post-transaction feedback requests and routes responses by score, sending low scores to private service recovery and high scores toward public review sites. differentiator
guest-loyalty-review-capture-routing
Not scored by this record.
Includes a native referral mechanic with per-guest codes or links, attribution of the referred guest's first order, and two-sided rewards.
guest-loyalty-referral-program
Not scored by this record.
Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance, as an alternative to requiring a branded app download. differentiator
guest-loyalty-wallet-pass
Not scored by this record.
Provides admin tooling to fulfill guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records.
guest-loyalty-privacy-rights-tooling
Not scored by this record.
Enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log.
guest-loyalty-redemption-fraud-controls
Not scored by this record.
Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing (claim-level; verify it is a shipped product feature, not a roadmap statement). differentiator
guest-loyalty-ai-offer-recommendation
Not scored by this record.
Offers native stored-value/gift card balances tied to the same guest profile and redeemable across all locations of the brand.
guest-loyalty-stored-value-gift
Not scored by this record.
Labor & workforce
Employees clock in and out at the POS terminal using a PIN, badge, or card, with no separate time-clock hardware required.
labor-clock-in-at-pos
User Guide 3.0.27 ch.1: the sign-in screen carries a dedicated 'Clock In / Out' button described as 'for tracking labor hours', and 'Clocking in and clocking out' is a documented task — tap Clock In / Out on the sign-in screen, specify your user ID in the Clock In / Out on-screen numeric keypad, Enter, confirm. Identification is a keyed user ID or a card: 'To sign in, swipe your user card through the magnetic stripe reader (MSR). Optionally, specify your user ID in the Enter User ID on-screen numeric keypad' (Infor's storefront sells the swipe cards). No separate time-clock hardware appears anywhere in the guide. The punches flow into labor reporting: Close Day 'clocks out and cashes out all listed employees', the POS report glossary defines Clock times as containing 'the employee name, date and time of clock in, job code, and total time clocked in for the shift', a Clock in Status report 'Lists all employees clocked in during the reporting period', and EM ch.6 gives managers Clock time records with search, modify and add tasks for correcting an employee's punches. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/user/pos_3.0.27_user__en-us.pdf · retrieved 2026-08-04
Captures a photo at punch (or performs facial verification) attached to the timecard entry, with a photo-only mode available that stores no biometric template. differentiator
labor-photo-punch-verification
Not scored by this record.
Supports mobile clock-in restricted by geofence or location validation for staff who do not punch at a fixed terminal.
labor-geofenced-mobile-punch
Not scored by this record.
Records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, with the behavior documented. differentiator
labor-offline-time-punch
Not scored by this record.
Permissions are grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers.
labor-granular-rbac
EM Administration Guide 3.0.27, ch.6: 'Job codes define the features and reports accessible by employees in Infor POS Enterprise Manager and in Infor POS.' Four separate grant surfaces hang off a job code — POS Privileges (an access level of NONE, NORMAL or FULL 'in the row of the Infor POS feature', i.e. per discrete function), Enterprise Rights (an Allow Access check box per EM feature), EM Reports (Allow View per report) and POS Reports (NONE/NORMAL/FULL per report). Each of the four is additionally overridable per location: 'In the row of the Infor POS feature, click Store Settings... In the row of the revenue center, click the Access Level list.' Job codes are operator-created and duplicable, so this is not a fixed cashier/manager/admin tier set. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/em3admin/pos_3.0.27_em3admin__en-us.pdf · retrieved 2026-08-03
Manager overrides and approvals are attributed to the individual approver and written to an immutable audit trail queryable after the fact.
labor-manager-override-audit
Override is attributed at the point of authorisation — a function set to NONE for a job code prompts for 'the user ID of an employee with a FULL access level' — and the POS 'Voided Down to $0' figure records 'the tab ID, the total amount, and the manager who authorized the checks'. Shortfall: there is no general override audit trail documented. EM lists an 'Event Log Report — Describes event information of a revenue center' without saying what events it holds or whether overrides are among them; the per-record 'Record Details' edit history for menu items, taxes and employees is documented only as a click path with no stated contents; and the on-terminal POS reports are explicitly bounded — 'The information gathered from activities since the last close day are tracked by Infor POS' — so after-the-fact query depends on the undescribed EM report. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/em3admin/pos_3.0.27_em3admin__en-us.pdf · retrieved 2026-08-03
Builds and publishes employee shift schedules inside the same platform that holds the timekeeping data, rather than requiring a third-party scheduling app. differentiator
labor-native-scheduling
Not scored by this record.
Generates recommended staffing levels or labor hours by daypart from the operator's own POS sales history, not just a static template. differentiator
labor-demand-labor-forecast
Not scored by this record.
Displays labor cost as a percentage of sales in real time during service on a manager view or POS, not only in end-of-day or next-morning reports. differentiator
labor-realtime-labor-percent
Not scored by this record.
Warns or blocks at clock-in when an employee is approaching or would cross a configured overtime threshold, before the overtime is incurred. differentiator
labor-overtime-prevention
Not scored by this record.
Configures meal and rest break rules per state or jurisdiction, prompts required break attestation, and flags missed breaks for premium pay. differentiator
labor-break-compliance-by-state
Not scored by this record.
Supports predictive-scheduling ordinances by tracking advance-notice deadlines for published schedules and calculating predictability pay owed for employer-initiated changes.
labor-fair-workweek-support
Not scored by this record.
Enforces minor-labor restrictions (age-based maximum hours, prohibited time windows, school-day limits) at both scheduling and clock-in.
labor-minor-labor-rules
Not scored by this record.
Computes tip pooling and tip-outs automatically per shift from configurable rules (percentage of sales, hours worked, points, or role), rather than requiring a manual spreadsheet.
labor-tip-pooling-rules
Not scored by this record.
Retains a per-shift, per-employee record of tips received, amounts contributed to the pool, and amounts distributed from the pool, exportable for audit.
labor-tip-distribution-audit-trail
Not scored by this record.
Payroll export separates cash from charged qualified tips and carries a Treasury tipped-occupation code, supporting the W-2 Box 12 code TP and Box 14b reporting required for tax year 2026. differentiator
labor-qualified-tips-w2-reporting
Not scored by this record.
Vendor processes payroll itself as a first-party product (tax filing and direct deposit), as opposed to exporting to a third-party payroll provider only. differentiator
labor-native-payroll
Not scored by this record.
Exports timecards, wages, and tips in documented formats or via direct integration for at least two major payroll providers (e.g. Gusto, ADP, Paychex, QuickBooks).
labor-payroll-export-formats
Not scored by this record.
Employees can request shift swaps or claim open shifts in a self-service app, subject to a manager approval workflow that enforces overtime and role eligibility. differentiator
labor-shift-swap-workflow
Not scored by this record.
Provides digital new-hire onboarding that collects W-4 and I-9 documentation and supports E-Verify submission.
labor-digital-onboarding-i9
Not scored by this record.
Reports per-employee sales performance metrics (average check, items or category attachment rate, void and comp rate) by server or cashier. differentiator
labor-server-performance-metrics
Not scored by this record.
Inventory, purchasing & cost control
Supports multi-level recipe/BOM costing where a recipe can contain sub-recipes (prep items) and plate cost recalculates automatically when any component ingredient's cost changes.
inventory-recipe-bom-costing
CLAIM TESTED: multi-level recipe/BOM costing, a recipe able to contain sub-recipes (prep items), and plate cost recalculating automatically when any component ingredient's cost changes. VALUE no, grade B, verified adversarially 2026-09-15. NOTHING IN THIS CLAIM IS MET. WHAT EXISTS INSTEAD: one flat, hand-typed number on the sold menu item. https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/ivk1568094351637.html "Adding a menu item" enumerates the menu-item record as SIXTEEN fields - Menu Item, SKU, Price, Cost, Family Group, Type, Local Name, Priority, Cook Time (min), Condiment, Roll up Price, Restricted, Combo Parent, Header Item, Cover, Active - and the only costing field among them names its own consumer: "Cost Specify the cost of the menu item. This information is used in the Theoretical Cost Report." SHORTFALL 1, no components: there is no ingredient, component, quantity-per, sub-item or stock-item field of any kind on the record, and no stock-item entity exists anywhere in the library - the only item entity Infor POS has is the sold menu item. SHORTFALL 2, no nesting: the nearest structure is "Combo Parent Select this check box to enable the menu item as part of a flex combo. You can add flex combo menu items in any order in a check and have scalable modifier options", which nests SOLD items inside a promotional bundle for pricing, not prep items inside a recipe for costing. SHORTFALL 3, no recalculation: because the Cost input is a number an administrator types, plate cost cannot recalculate when an ingredient price moves - there are no ingredient prices. SHORTFALL 4, no back office to hold one: the EM Administration Guide contents (https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/default.html, read whole) enumerates the entire configuration surface - About this guide, Enterprise Manager overview, Revenue center, Menu item management, Touchscreen menu management, Groups management, Tender and discount management, Employee management, Store management, Printing management, Table management, Reports management - with no inventory, stock, recipe, purchasing, receiving or costing area. The downstream reports are menu-ITEM level and consistent with the flat field: https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/teb1570776984357.html "Theoretical Costs Report Describes costs incurred by menu items." and "Waste Tracking Report Describes information on wasted menu items." The only purchasing-shaped string on the record is free text: https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/tyd1568361567786.html "Vendor SKU Specify the stock keeping unit of the menu item according to its vendor." This closes, rather than inherits, the 2026-08-03 pass, which saw a Theoretical Costs Report in the catalogue and reasoned that recipe costing must exist upstream of it. It does not. RAW-BYTE CHECK: the Cost quote is a genuine definition-list pairing in the served bytes - <dt>Cost</dt> followed by <dd>Specify the cost of the menu item. This information is used in the <span>Theoretical Cost Report</span>.</dd> - the only markup inside the sentence being the span that bolds the report name. Comments were stripped before tags and no quoted text came from a comment, so no <dt>/<dd> or table cell was welded into a false quote. CONTROLS, all tokenised on word boundaries, all read in BOTH instruments and zero in both: recipe 0, recipes 0, ingredient 0, ingredients 0, "bill of material" 0, "bill of materials" 0, sub-recipe 0, sub-item 0, "plate cost" 0, yield 0, yields 0, "cost of goods" 0, COGS 0, portions 0. Non-zero neighbours resolved by reading every hit: portion 1 ("the tendered portion of the check"), prep 1 ("Kitchen Time is the sum of Prep time and Expo bump"), component 1 (a configuration entity), components 13 (Kiosk hardware and DDS "communication between various components, such as terminals, kitchen displays, and reporting systems"), batch 1 (Batch Export of bookmarked reports). TWO INSTRUMENTS. Every control below was re-run by the verifier, tokenised on word boundaries (hyphen and whitespace treated as equivalent, phrases matched across line wraps), over two independent renderings of the same library: (i) the 374 raw HTML topics, comments stripped with <!-- --> removed BEFORE tags and every tag replaced by a SPACE so no <dt>/<dd> or table cell can be welded into a false quote; and (ii) a fresh pdftotext extraction of the four published 2026.08 PDFs (em3admin, kadmin, posonapag, user; 299,267 characters). The earlier claim that Infor PDFs are a poisoned corpus is FALSE for these four and was retired: pdftotext reads them cleanly (positive control Infor = 671 occurrences across the four). A previously cached extraction of the same PDFs in .cache/q310-infor-hospitality/txt-*.txt IS cid-mangled garbage ("Infor" renders as ") ! * -"); it was produced by a different extractor and must not be used. HTML positive controls on tag-stripped text: Infor 242 topics / 661 hits, menu 186 / 925, report 40 / 179, employee 42 / 195, discount 39 / 130, tax 23 / 144, printer 16 / 63. PDF positive controls: Infor 671, menu 767, report 148, employee 165, discount 114, tax 111, printer 55. Both instruments agree on every figure quoted below. MANIFEST BOUND: https://docs.infor.com/pos/2026.08/en-us/useradminlib/sitemap.html, re-derived by me on 2026-09-15, carries 375 .html anchors = 1 library root + 374 topics, distributed user 148 / em3admin 146 / kadmin 65 / posonapag 15. All 374 are on disk and were read as RAW bytes; the on-disk distribution matches the sitemap exactly, so the zero is bound to the publisher's own manifest with no gap. GATE: the companion library /pos/2026.08/en-us/technical/ returns HTTP 200 carrying an identical 1,840-byte SAML auto-submit form to mingle-sso.us2.prd3.inforcloudsuite.com ("Access rights validated") for both its default.html and its sitemap.html. That is a login wall, not an absence; it caps every absence here at grade B and grade A is not available on this vendor. POISON FOUND, recorded so it is not re-derived. (1) "domain" reads 374 of 374 HTML topics and 760 hits, and 0 in all four PDFs. The 374 are the Oxygen WebHelp template's own JavaScript, isKnownServer(domain); a naive HTML-only control would have manufactured a positive for custom-domain support out of page chrome. The PDF instrument is what discriminates it. (2) "current" likewise reads 374 of 374 HTML topics but only 2 PDF documents - template chrome again; it is worthless as a control and was discarded. (3) "count" is the trap of the inventory cells: 14 HTML topics, 56 hits, and not one is a stock count - the senses are the sales COUNTDOWN (Set Count, Count List, Remove Countdown, Daily Default, Carryover Remainder), the GUEST COUNT / COVER COUNT / CHECK COUNT / TABLE COUNT / VOID QUANTITY report columns, "Covers - Counts covers in a check", and "calorie count". A substring search would have read this as inventory counting. (4) "stock" reads 5 topics and every hit is "stock keeping unit" (the free-text Vendor SKU field), "Out of Stock" in the countdown colour legend, or the Kiosk "Hide Out-of-Stock Items" toggle. (5) "inventory" reads exactly 1 topic and 1 hit, inside the countdown topic: "Color indicators are integrated into the names of menu items to visually represent inventory status." (6) "components" reads 13 topics but resolves to Infor POS Kiosk hardware components and to the Data Distribution Service "communication between various components, such as terminals, kitchen displays, and reporting systems" - never a recipe component. (7) "batch" is Batch Export of bookmarked reports. (8) "86" reads 0 in HTML and 2 in PDF, and both PDF hits are the page number 86 - not the 86ing sense. (9) "real time" reads exactly 1 topic in both instruments and it is the Terminal Health dashboard, DEVICE TELEMETRY, a homonym of a sales dashboard that must never be cited as one. (10) "physical" is physical printers and physical user cards; "prep" is "Prep time" in the Speed of Service report; "portion" is "the tendered portion of the check"; "vendor" is "vendor stock keeping unit". ADVERSE EVIDENCE WEIGHED AND REJECTED: www.infor.com/products/point-of-sale (grade D) markets "Monitor sales, track inventory, and gain insight into customer behavior"; its only documented referent in the product is the per-item sales countdown, and it asserts nothing about recipes, sub-recipes or component costing. Infor separately sells CloudSuite Food & Beverage, a process ERP with formula management, and Infor Hospitality Analytics; those are different products with their own libraries and this verdict is about what Infor POS itself ships. https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/ivk1568094351637.html · retrieved 2026-09-15 adversarially verified
Stores purchase unit, recipe unit, and count unit per item with explicit conversion factors, plus a yield/waste percentage applied to raw-to-usable conversion.
inventory-unit-conversion-yields
CLAIM TESTED: purchase unit, recipe unit and count unit stored per item with explicit conversion factors, plus a yield/waste percentage applied to the raw-to-usable conversion. VALUE no, grade B, verified adversarially 2026-09-15. NOTHING IN THIS CLAIM IS MET. WHAT EXISTS INSTEAD: two free-text strings and one sale-side scale setting. SHORTFALL 1, no units on the item record: https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/tyd1568361567786.html "Specifying the item size or vendor stock keeping unit" is the whole unit vocabulary of the menu-item record and it is "Item Size Specify the item size of the menu item." plus "Vendor SKU Specify the stock keeping unit of the menu item according to its vendor." - free text, no enumerated unit list, no second unit, no factor. SHORTFALL 2, no conversion factors: the sixteen-field menu-item record at https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/ivk1568094351637.html (Menu Item, SKU, Price, Cost, Family Group, Type, Local Name, Priority, Cook Time, Condiment, Roll up Price, Restricted, Combo Parent, Header Item, Cover, Active) carries no unit-of-measure field at all; the only quantity concept on it is the sales countdown. SHORTFALL 3, no yield or waste percentage anywhere, and no raw-to-usable conversion to apply one to. SHORTFALL 4, no place for such a table to live: the EM Administration Guide contents (https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/default.html, read whole) has no inventory, stock or purchasing area, and there is no stock-item entity in the library - the only item entity is the sold menu item. THE ONE UNIT-OF-MEASURE SURFACE IN THE PRODUCT, named here because a note that omits it is incomplete: https://docs.infor.com/pos/2026.08/en-us/useradminlib/kadmin/wjm1579077106811.html "Configuring the weight unit of an integrated scale for weighing menu items" - "Tap Scale Weight Unit and tap a weight unit option. This enables the menu items with the selected weight unit option to be added to an order." That is one unit, chosen so an integrated scale can PRICE a weighed item at the point of sale; there is no second unit and no factor between them. The User Guide pair "Calculating the price of a menu item using a scale" and "Adding a tare weight button" is the same sale-side surface. Weight-to-price is not purchase-to-recipe-to-count. CONTROLS, tokenised, ZERO IN BOTH INSTRUMENTS: "unit of measure" 0, UOM 0, conversion 0, convert 0, yield 0, yields 0, variance 0, "on hand" 0, "par level" 0, par 0, reorder 0, requisition 0, supplier 0, suppliers 0, "order guide" 0, shrinkage 0, invoice 0, ounce 0, pound 0, gram 0, litre 0, liter 0. Non-zero neighbours resolved by reading every hit: unit 5 topics (the Vendor SKU topic and its ToC entry, the Kiosk Scale Weight Unit topic, "Look Up Searches items by stock keeping unit (SKU) or barcode (UPC)"); units 2 (a modifier display field, and "Count List Opens number of remaining units of a menu item available for an order"); converted 2 (smart-combo price conversion); receiving 2 ("Receiving a transferred check"); purchase 3 and purchasing 1 (payment-side language); vendor 2 (the Vendor SKU field); weight 5, tare 3, scale 7 (the sale-side weighing surface above); quantity 12 (report columns and "Specifying the quantity of a menu item ordered in a check"); case 1. TWO INSTRUMENTS. Every control below was re-run by the verifier, tokenised on word boundaries (hyphen and whitespace treated as equivalent, phrases matched across line wraps), over two independent renderings of the same library: (i) the 374 raw HTML topics, comments stripped with <!-- --> removed BEFORE tags and every tag replaced by a SPACE so no <dt>/<dd> or table cell can be welded into a false quote; and (ii) a fresh pdftotext extraction of the four published 2026.08 PDFs (em3admin, kadmin, posonapag, user; 299,267 characters). The earlier claim that Infor PDFs are a poisoned corpus is FALSE for these four and was retired: pdftotext reads them cleanly (positive control Infor = 671 occurrences across the four). A previously cached extraction of the same PDFs in .cache/q310-infor-hospitality/txt-*.txt IS cid-mangled garbage ("Infor" renders as ") ! * -"); it was produced by a different extractor and must not be used. HTML positive controls on tag-stripped text: Infor 242 topics / 661 hits, menu 186 / 925, report 40 / 179, employee 42 / 195, discount 39 / 130, tax 23 / 144, printer 16 / 63. PDF positive controls: Infor 671, menu 767, report 148, employee 165, discount 114, tax 111, printer 55. Both instruments agree on every figure quoted below. MANIFEST BOUND: https://docs.infor.com/pos/2026.08/en-us/useradminlib/sitemap.html, re-derived by me on 2026-09-15, carries 375 .html anchors = 1 library root + 374 topics, distributed user 148 / em3admin 146 / kadmin 65 / posonapag 15. All 374 are on disk and were read as RAW bytes; the on-disk distribution matches the sitemap exactly, so the zero is bound to the publisher's own manifest with no gap. GATE: the companion library /pos/2026.08/en-us/technical/ returns HTTP 200 carrying an identical 1,840-byte SAML auto-submit form to mingle-sso.us2.prd3.inforcloudsuite.com ("Access rights validated") for both its default.html and its sitemap.html. That is a login wall, not an absence; it caps every absence here at grade B and grade A is not available on this vendor. POISON FOUND, recorded so it is not re-derived. (1) "domain" reads 374 of 374 HTML topics and 760 hits, and 0 in all four PDFs. The 374 are the Oxygen WebHelp template's own JavaScript, isKnownServer(domain); a naive HTML-only control would have manufactured a positive for custom-domain support out of page chrome. The PDF instrument is what discriminates it. (2) "current" likewise reads 374 of 374 HTML topics but only 2 PDF documents - template chrome again; it is worthless as a control and was discarded. (3) "count" is the trap of the inventory cells: 14 HTML topics, 56 hits, and not one is a stock count - the senses are the sales COUNTDOWN (Set Count, Count List, Remove Countdown, Daily Default, Carryover Remainder), the GUEST COUNT / COVER COUNT / CHECK COUNT / TABLE COUNT / VOID QUANTITY report columns, "Covers - Counts covers in a check", and "calorie count". A substring search would have read this as inventory counting. (4) "stock" reads 5 topics and every hit is "stock keeping unit" (the free-text Vendor SKU field), "Out of Stock" in the countdown colour legend, or the Kiosk "Hide Out-of-Stock Items" toggle. (5) "inventory" reads exactly 1 topic and 1 hit, inside the countdown topic: "Color indicators are integrated into the names of menu items to visually represent inventory status." (6) "components" reads 13 topics but resolves to Infor POS Kiosk hardware components and to the Data Distribution Service "communication between various components, such as terminals, kitchen displays, and reporting systems" - never a recipe component. (7) "batch" is Batch Export of bookmarked reports. (8) "86" reads 0 in HTML and 2 in PDF, and both PDF hits are the page number 86 - not the 86ing sense. (9) "real time" reads exactly 1 topic in both instruments and it is the Terminal Health dashboard, DEVICE TELEMETRY, a homonym of a sales dashboard that must never be cited as one. (10) "physical" is physical printers and physical user cards; "prep" is "Prep time" in the Speed of Service report; "portion" is "the tendered portion of the check"; "vendor" is "vendor stock keeping unit". CORPUS CORRECTION: the prior note for this cell was cited to https://docs.infor.com/pos/3.0.27/en-us/useradminlib/em3admin/pos_3.0.27_em3admin__en-us.pdf. That URL still returns 200 but 3.0.27 is the superseded generation, so the note was bound to the wrong corpus and has been re-derived against 2026.08. The prior note also asserted that Infor PDFs use embedded subset fonts from which control words extract as zero regardless of presence; that assertion is FALSE for the 2026.08 PDFs and has been withdrawn - pdftotext reads all four cleanly and they are used here as the second instrument. https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/tyd1568361567786.html · retrieved 2026-09-15 adversarially verified
Produces a theoretical-vs-actual usage variance report per item for a defined count period, showing theoretical usage from POS sales times recipe, actual usage from counts plus receipts, and the variance in both units and currency. differentiator
inventory-theoretical-vs-actual
Not scored by this record.
Depletes ingredient on-hand quantities in near real time as orders are fired at the POS, including depletion driven by modifier selections, not only in an end-of-day batch. differentiator
inventory-realtime-depletion
Not scored by this record.
Automatically 86s (marks unavailable) menu items on the POS, online ordering, and connected third-party delivery menus when a component ingredient hits zero or a configured threshold. differentiator
inventory-86-auto-sync
Not scored by this record.
Supports full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts.
inventory-count-modes
CLAIM TESTED: full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts. VALUE no, grade B, verified adversarially 2026-09-15. NOT ONE OF THE THREE COUNT MODES EXISTS, AND NEITHER DOES VARIANCE OR HISTORY. WHAT EXISTS INSTEAD: a sell-down counter that resets each business day. https://docs.infor.com/pos/2026.08/en-us/useradminlib/user/owb1561967667029.html "Setting a count for a menu item" is the only thing Infor POS calls a count: "A countdown set to an item is automatically applied to all configured revenue centers in a single primary terminal. This applies to items sold, voided or returned, or when the item is removed from a revenue center in a primary terminal." Its display is a traffic light, not a ledger: "Color indicators are integrated into the names of menu items to visually represent inventory status. These colors reflect the current stock level: Light Gray: Count is greater than 5 / Orange: Count is between 5 to 1 / Red: Count is 0 or Out of Stock." Its option list is closed and is three items: "Remove Countdown: Remove the count of a menu item", "Daily Default: Specify the default daily count of a menu item", "Carryover Remainder: Specify the remaining count of a menu item from the previous business day". SHORTFALL 1, no count session: the operator types a number of items left; there is no counted-versus-expected pair, so no variance can be computed. SHORTFALL 2, no history: https://docs.infor.com/pos/2026.08/en-us/useradminlib/user/mya1561968421985.html "Viewing the count of a menu item" is the entire reporting surface - "From the right-hand menu, tap Count List to view a summary of menu items with a count." A live list of current numbers, and Daily Default overwrites it each business day. SHORTFALL 3, no modes: there is no full-count, spot-count or cycle-count task, no count sheet, no scheduling of counts and no subset selection. THE VENDOR WORKAROUND, the classic shape of a documented absence: https://docs.infor.com/pos/2026.08/en-us/useradminlib/user/xuj1555619811594.html "Tagging a menu item as waste" - "The wasted menu item is now excluded from check payment. Note: A wasted item is not tracked in gross sales reports. We recommend creating a new check named Waste and moving wasted items there for record purposes." Infor advises opening a dummy check to keep a record of shrink. BINDING ENUMERATIONS: the User Guide contents (https://docs.infor.com/pos/2026.08/en-us/useradminlib/user/default.html) and the EM Administration Guide contents (https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/default.html) were both read whole; between them they enumerate every operator task and every back-office configuration area in the product, and neither contains a physical inventory, spot count, cycle count, count sheet or stock adjustment task. The POS Functions menu table (https://docs.infor.com/pos/2026.08/en-us/useradminlib/user/gog1555619772856.html) enumerates every function button and the only relevant ones are "Set Count Specifies the quantity available for a menu item", Count List and Waste. CONTROLS, tokenised, ZERO IN BOTH INSTRUMENTS: counting 0, cycle 0, "cycle count" 0, "spot count" 0, "physical inventory" 0, stocktake 0, "stock take" 0, "count sheet" 0, recount 0, audit 0, variance 0, shrinkage 0, "on hand" 0, usage 0, depletion 0, "par level" 0, requisition 0. Non-zero neighbours resolved: adjustment 1 (a tender adjustment), waste 5 / wasted 4 (the workaround above), inventory 1 (the colour-legend sentence quoted above), countdown 1 (the same topic). RAW-BYTE CHECK: all four quotes are real element-level prose in the served bytes - a <p> for the countdown sentence, a genuine <ul> of <li> elements for the colour legend (not a welded table), three <li> elements for the option list, a <p> for the Count List sentence and a <note> for the waste workaround. Comments were stripped before tags; nothing was welded. TWO INSTRUMENTS. Every control below was re-run by the verifier, tokenised on word boundaries (hyphen and whitespace treated as equivalent, phrases matched across line wraps), over two independent renderings of the same library: (i) the 374 raw HTML topics, comments stripped with <!-- --> removed BEFORE tags and every tag replaced by a SPACE so no <dt>/<dd> or table cell can be welded into a false quote; and (ii) a fresh pdftotext extraction of the four published 2026.08 PDFs (em3admin, kadmin, posonapag, user; 299,267 characters). The earlier claim that Infor PDFs are a poisoned corpus is FALSE for these four and was retired: pdftotext reads them cleanly (positive control Infor = 671 occurrences across the four). A previously cached extraction of the same PDFs in .cache/q310-infor-hospitality/txt-*.txt IS cid-mangled garbage ("Infor" renders as ") ! * -"); it was produced by a different extractor and must not be used. HTML positive controls on tag-stripped text: Infor 242 topics / 661 hits, menu 186 / 925, report 40 / 179, employee 42 / 195, discount 39 / 130, tax 23 / 144, printer 16 / 63. PDF positive controls: Infor 671, menu 767, report 148, employee 165, discount 114, tax 111, printer 55. Both instruments agree on every figure quoted below. MANIFEST BOUND: https://docs.infor.com/pos/2026.08/en-us/useradminlib/sitemap.html, re-derived by me on 2026-09-15, carries 375 .html anchors = 1 library root + 374 topics, distributed user 148 / em3admin 146 / kadmin 65 / posonapag 15. All 374 are on disk and were read as RAW bytes; the on-disk distribution matches the sitemap exactly, so the zero is bound to the publisher's own manifest with no gap. GATE: the companion library /pos/2026.08/en-us/technical/ returns HTTP 200 carrying an identical 1,840-byte SAML auto-submit form to mingle-sso.us2.prd3.inforcloudsuite.com ("Access rights validated") for both its default.html and its sitemap.html. That is a login wall, not an absence; it caps every absence here at grade B and grade A is not available on this vendor. POISON FOUND, recorded so it is not re-derived. (1) "domain" reads 374 of 374 HTML topics and 760 hits, and 0 in all four PDFs. The 374 are the Oxygen WebHelp template's own JavaScript, isKnownServer(domain); a naive HTML-only control would have manufactured a positive for custom-domain support out of page chrome. The PDF instrument is what discriminates it. (2) "current" likewise reads 374 of 374 HTML topics but only 2 PDF documents - template chrome again; it is worthless as a control and was discarded. (3) "count" is the trap of the inventory cells: 14 HTML topics, 56 hits, and not one is a stock count - the senses are the sales COUNTDOWN (Set Count, Count List, Remove Countdown, Daily Default, Carryover Remainder), the GUEST COUNT / COVER COUNT / CHECK COUNT / TABLE COUNT / VOID QUANTITY report columns, "Covers - Counts covers in a check", and "calorie count". A substring search would have read this as inventory counting. (4) "stock" reads 5 topics and every hit is "stock keeping unit" (the free-text Vendor SKU field), "Out of Stock" in the countdown colour legend, or the Kiosk "Hide Out-of-Stock Items" toggle. (5) "inventory" reads exactly 1 topic and 1 hit, inside the countdown topic: "Color indicators are integrated into the names of menu items to visually represent inventory status." (6) "components" reads 13 topics but resolves to Infor POS Kiosk hardware components and to the Data Distribution Service "communication between various components, such as terminals, kitchen displays, and reporting systems" - never a recipe component. (7) "batch" is Batch Export of bookmarked reports. (8) "86" reads 0 in HTML and 2 in PDF, and both PDF hits are the page number 86 - not the 86ing sense. (9) "real time" reads exactly 1 topic in both instruments and it is the Terminal Health dashboard, DEVICE TELEMETRY, a homonym of a sales dashboard that must never be cited as one. (10) "physical" is physical printers and physical user cards; "prep" is "Prep time" in the Speed of Service report; "portion" is "the tendered portion of the check"; "vendor" is "vendor stock keeping unit". ADVERSE EVIDENCE WEIGHED: www.infor.com/products/point-of-sale (grade D) says "Monitor sales, track inventory". Its only documented referent in the product is this countdown, which is why the cell is scored on the doc enumeration and not on the brochure. CORPUS CORRECTION: the prior note was cited to a 3.0.27 PDF and was therefore bound to the superseded generation; this verdict is re-derived against 2026.08 in both HTML and PDF. https://docs.infor.com/pos/2026.08/en-us/useradminlib/user/owb1561967667029.html · retrieved 2026-09-15 adversarially verified
Provides a mobile/tablet counting app supporting barcode or QR scanning that continues to accept counts with no network connectivity and syncs on reconnect.
inventory-mobile-count-offline
Not scored by this record.
Ships pre-built electronic vendor catalog and order-transmission integrations with named broadline distributors (e.g. Sysco, US Foods, Performance Food Group) that send purchase orders and receive invoices electronically rather than by emailed PDF. differentiator
inventory-vendor-catalogs-edi
Not scored by this record.
Ingests supplier invoices from photo, PDF, or email and extracts line-item detail (item, quantity, unit, price) into the inventory ledger without manual line entry. differentiator
inventory-invoice-ocr
Not scored by this record.
Tracks per-item purchase price history across invoices and alerts when a received price exceeds the prior or contracted price by a configurable threshold. differentiator
inventory-price-change-alerts
Not scored by this record.
Maintains par levels per item per location and generates suggested purchase order quantities from on-hand versus par, with at least one mode driven by a sales forecast rather than a static par. differentiator
inventory-par-auto-suggest
Not scored by this record.
Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.
inventory-waste-logging
Not scored by this record.
Supports inter-location inventory transfers as a two-sided transaction crediting the sending location and debiting the receiving location, with an in-transit or approval state.
inventory-transfers
Not scored by this record.
Supports a commissary/central kitchen model where one location produces prep items and issues or sells them to other locations at a computed transfer cost.
inventory-commissary
Not scored by this record.
Captures lot/batch numbers at receiving and links them through production to sales or transfers, enabling a backward and forward recall trace.
inventory-lot-traceability
Not scored by this record.
Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.
inventory-shelf-life-expiry
Not scored by this record.
Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting.
inventory-bar-partial-bottle
Not scored by this record.
Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.
inventory-cogs-gl-export
Not scored by this record.
Inventory and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator
inventory-native-not-partner
Not scored by this record.
Reporting, BI & data access
Provides a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise.
reporting-realtime-dashboard
CLAIM TESTED: a live sales dashboard reflecting transactions within minutes of the sale, accessible from BOTH a browser AND a mobile app off-premise. VALUE no, grade B, verified adversarially 2026-09-15; a proposed partial was rejected on this pass. WHAT IS MET: only the browser half of the access conjunct, which is a delivery medium rather than the capability. Infor POS Enterprise Manager is a cloud back office reached off-premise in a browser - https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/qsz1555619456862.html "You can access Infor POS Enterprise Manager by specifying the URL that is provided by your Infor POS Enterprise Manager representative in a web browser" - and it carries real sales reporting. Enterprise Manager X (https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/zwu1569834267652.html "In Infor POS Enterprise Manager X, you can access dynamic reports, perform bulk update, and manage videos") serves Dynamic reports (https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/iyl1725418163764.html): "Dynamic reports are customizable reports that you can filter, save as bookmark, and schedule", filterable by Date / Stores / Column / Group By / Filter, with Time groupings Serving Period, Hour, 30 Minutes and 15 Minutes, and a Sales column catalogue including Gross Sales, Net Sales, Guest Count, Check Count, Cover Count, Items Sold, Discounts, Returns, Average Sale Per Check and Sales by Interval; https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/ceu1725418722296.html adds Run Report, Run Report in a New Tab, Export to Excel/PDF, report history, Save as New Bookmark, Schedule and Batch Export. The standard-report catalogue also carries a summary row named "Executive Desktop Describes gross sales and the number of closed checks and guests" (https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/teb1570776984357.html). Intraday sales at a 15-minute grain in a browser is a real operator surface and is recorded here so no reader concludes Infor publishes nothing. SHORTFALL 1, THERE IS NO SALES DASHBOARD. The EM Reports management table of contents was read whole (18 entries: Standard reports, Viewing a standard report, Exporting standard reports, six named exports, Scheduling and emailing a standard report, Dynamic reports, Accessing EMX, Viewing and exporting a dynamic report, Bulk update editor, Terminal health dashboard, Viewing the terminal health status) and the standard-report catalogue was read whole (35 rows). Tokenised, "dashboard" occurs in exactly 6 topics and 10 hits across 374 topics, and the referents are exhaustively: the Terminal Health dashboard, a "Schedule Dashboard" listing report schedules, a dashboard of SCHEDULED ORDERS on the terminal (user/euv1610700055405 "the information about all scheduled orders are displayed in a dashboard"), and the Stripe merchant Dashboard in the OrderNow guide. Sales reach the operator as reports, not as a dashboard. SHORTFALL 2, NO STATED FRESHNESS, AND THE ARCHITECTURE POINTS THE OTHER WAY. latency 0, "live" 0 in tag-stripped prose, realtime 0, immediately 0, instantly 0, today 0, "up to date" 0, poll 0, polling 0. Meanwhile the standard-report catalogue's first row is a report type called Data sync: "Data Sync Status Describes the time and date when the revenue center was last synced with Infor POS Enterprise Manager data", with its own export topic (https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/wvt1571899913395.html), and revenue centers carry an "Enable DDS Select this check box to enable data sync through Data Distribution Service (DDS) to facilitate communication between various components, such as terminals, kitchen displays, and reporting systems." EM is fed by a sync whose cadence is nowhere published and for which Infor ships a last-synced status report. That is adverse to "within minutes", not merely silent. SHORTFALL 3, THERE IS NO MOBILE APP OF ANY KIND FOR MANAGERS. "manager app" 0, iOS 0, Android 0; "mobile app" occurs once in 374 topics and it is the OrderNow guest link button; "app" occurs 4 times and all four are the guest OrderNow app; all 30 "mobile" hits are guest-facing (Mobile Name on the menu item, "Mobile Enables or disables mobile ordering", mobile wallets, the guest's mobile phone number for SMS, Mobile Delivery Method) or WebHelp feedback chrome ("This page is difficult to use on my mobile device"). Across a complete four-guide library covering the terminal, the back office, the Kiosk and OrderNow, no manager or reporting application exists. That is positive evidence of absence, and it falsifies the claim's "and a mobile app" outright. HOMONYM TRAP, recorded so it is never re-mined: https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/oqt1577419383109.html "Terminal health dashboard" - "You can monitor the operational status of a revenue center in real time by accessing the Terminal Health dashboard. This dashboard contains detailed insights into terminal performance, connectivity, and potential issues." This is the ONLY tokenised "real time" string in all 374 topics and in all four PDFs, and it is DEVICE TELEMETRY; its companion topic tzc1577426882218 shows the tabs Offline / In use / Tree View. It must never be cited as a sales dashboard. TWO INSTRUMENTS. Every control below was re-run by the verifier, tokenised on word boundaries (hyphen and whitespace treated as equivalent, phrases matched across line wraps), over two independent renderings of the same library: (i) the 374 raw HTML topics, comments stripped with <!-- --> removed BEFORE tags and every tag replaced by a SPACE so no <dt>/<dd> or table cell can be welded into a false quote; and (ii) a fresh pdftotext extraction of the four published 2026.08 PDFs (em3admin, kadmin, posonapag, user; 299,267 characters). The earlier claim that Infor PDFs are a poisoned corpus is FALSE for these four and was retired: pdftotext reads them cleanly (positive control Infor = 671 occurrences across the four). A previously cached extraction of the same PDFs in .cache/q310-infor-hospitality/txt-*.txt IS cid-mangled garbage ("Infor" renders as ") ! * -"); it was produced by a different extractor and must not be used. HTML positive controls on tag-stripped text: Infor 242 topics / 661 hits, menu 186 / 925, report 40 / 179, employee 42 / 195, discount 39 / 130, tax 23 / 144, printer 16 / 63. PDF positive controls: Infor 671, menu 767, report 148, employee 165, discount 114, tax 111, printer 55. Both instruments agree on every figure quoted below. MANIFEST BOUND: https://docs.infor.com/pos/2026.08/en-us/useradminlib/sitemap.html, re-derived by me on 2026-09-15, carries 375 .html anchors = 1 library root + 374 topics, distributed user 148 / em3admin 146 / kadmin 65 / posonapag 15. All 374 are on disk and were read as RAW bytes; the on-disk distribution matches the sitemap exactly, so the zero is bound to the publisher's own manifest with no gap. GATE: the companion library /pos/2026.08/en-us/technical/ returns HTTP 200 carrying an identical 1,840-byte SAML auto-submit form to mingle-sso.us2.prd3.inforcloudsuite.com ("Access rights validated") for both its default.html and its sitemap.html. That is a login wall, not an absence; it caps every absence here at grade B and grade A is not available on this vendor. POISON FOUND, recorded so it is not re-derived. (1) "domain" reads 374 of 374 HTML topics and 760 hits, and 0 in all four PDFs. The 374 are the Oxygen WebHelp template's own JavaScript, isKnownServer(domain); a naive HTML-only control would have manufactured a positive for custom-domain support out of page chrome. The PDF instrument is what discriminates it. (2) "current" likewise reads 374 of 374 HTML topics but only 2 PDF documents - template chrome again; it is worthless as a control and was discarded. (3) "count" is the trap of the inventory cells: 14 HTML topics, 56 hits, and not one is a stock count - the senses are the sales COUNTDOWN (Set Count, Count List, Remove Countdown, Daily Default, Carryover Remainder), the GUEST COUNT / COVER COUNT / CHECK COUNT / TABLE COUNT / VOID QUANTITY report columns, "Covers - Counts covers in a check", and "calorie count". A substring search would have read this as inventory counting. (4) "stock" reads 5 topics and every hit is "stock keeping unit" (the free-text Vendor SKU field), "Out of Stock" in the countdown colour legend, or the Kiosk "Hide Out-of-Stock Items" toggle. (5) "inventory" reads exactly 1 topic and 1 hit, inside the countdown topic: "Color indicators are integrated into the names of menu items to visually represent inventory status." (6) "components" reads 13 topics but resolves to Infor POS Kiosk hardware components and to the Data Distribution Service "communication between various components, such as terminals, kitchen displays, and reporting systems" - never a recipe component. (7) "batch" is Batch Export of bookmarked reports. (8) "86" reads 0 in HTML and 2 in PDF, and both PDF hits are the page number 86 - not the 86ing sense. (9) "real time" reads exactly 1 topic in both instruments and it is the Terminal Health dashboard, DEVICE TELEMETRY, a homonym of a sales dashboard that must never be cited as one. (10) "physical" is physical printers and physical user cards; "prep" is "Prep time" in the Speed of Service report; "portion" is "the tendered portion of the check"; "vendor" is "vendor stock keeping unit". ADVERSE EVIDENCE WEIGHED AND REJECTED: www.infor.com/products/point-of-sale (grade D) markets "Gain insight with real-time analytics" and "real-time reporting". Vendor marketing establishes a claim, not a capability, and the documentation neither states nor supports a latency; a grade-D line cannot carry a conjunct that the grade-B corpus enumerates away. Infor Hospitality Analytics (www.infor.com/products/hospitality-business-intelligence) is a SEPARATE product - a data lake "centralizing hospitality data from property management, POS, sales, catering, and other systems" with a Report Builder - and is not the dashboard of the POS; that page itself tokenises dashboard 0 and mobile 0. An operator could of course buy a BI product or a third-party dashboard; this cell scores what Infor POS ships. https://docs.infor.com/pos/2026.08/en-us/useradminlib/em3admin/teb1570776984357.html · retrieved 2026-09-15 adversarially verified
Generates a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types, and expected cash deposit in one document.
reporting-eod-closeout
EM publishes a 'Daily Close Day Report — Describes sales and operational information of a business day' plus a Cashout Report and a 'Consolidated CashOut Report EM' per employee or revenue center; the POS has Close Day on the sign-in screen ('close the business day and reboot Infor POS... clock out all signed-in users') and 'Printing a cash-out report' via Print Close against a selected cash drawer. The User Guide's report glossary enumerates the reconciling lines in one document: gross receipts, net revenue, total revenue, tax collected and tax summary, discounts and discount summary, void summary, manager vs server voids, tender and cash summary, charged and declared tips, tips due and tips paid, media loan and media pickup, rounding total and change in grand total (which includes returns). https://docs.infor.com/pos/3.0.27/en-us/useradminlib/user/pos_3.0.27_user__en-us.pdf · retrieved 2026-08-03
Provides a product mix (PMIX) report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center.
reporting-pmix-modifier-level
Product mix exists and slices the two ways the claim asks for: EM publishes a 'Product Sales Mix Export — Describes product sales of menu items', a 'Menu Item Report — Describes the menu items sold per revenue center' and a 'Day Parts Report — Describes the menu items sold during the different parts of a day', and every report is run against a Dates range and a Store Group selection. Shortfall: Infor publishes report names and one-line descriptions only. Neither guide states that modifiers are broken out as their own lines (they are stored as menu items — 'Modifiers are created as menu items in Infor POS Enterprise Manager' — so this is inference, not documentation), nor that the report carries both gross and net sales per item; the POS-side equivalent is described purely as a count, 'Specifies how many of each menu item were sold'. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/em3admin/pos_3.0.27_em3admin__en-us.pdf · retrieved 2026-08-03
Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.
reporting-comps-voids-audit
Not scored by this record.
Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.
reporting-cash-over-short
Not scored by this record.
Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.
reporting-labor-productivity
Not scored by this record.
Reports per-server metrics including average check, items per check, attachment rate for named categories, and tips as a percentage of sales. differentiator
reporting-server-scorecards
Not scored by this record.
Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator
reporting-channel-profitability
Not scored by this record.
Provides a consolidated multi-location report with side-by-side location comparison and drill-down from group total to a single location and then to an individual transaction. differentiator
reporting-multiloc-drilldown
Not scored by this record.
Includes a self-service report builder letting a non-developer choose dimensions, measures, and filters and save the result, rather than only fixed canned reports. differentiator
reporting-custom-report-builder
Not scored by this record.
Supports scheduling any report for automatic recurring delivery by email or to a shared destination on a defined cadence and recipient list.
reporting-scheduled-delivery
Not scored by this record.
Offers automated recurring bulk export of transaction-level raw data to a customer-controlled destination (S3, SFTP, Snowflake, BigQuery, or equivalent), not just manual CSV download. differentiator
reporting-raw-warehouse-export
Not scored by this record.
Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator
reporting-public-api
Not scored by this record.
Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator
reporting-webhooks
Not scored by this record.
API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator
reporting-api-not-upcharged
Not scored by this record.
Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator
reporting-tier-paywall
Not scored by this record.
Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator
reporting-history-retention
Not scored by this record.
Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator
reporting-anomaly-alerts
Not scored by this record.
Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.
reporting-nl-query
Not scored by this record.
Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator
reporting-guest-cohorts
Not scored by this record.
Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator
reporting-sales-forecast
Not scored by this record.
Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.
reporting-tip-tax-compliance
Not scored by this record.
Multi-location, franchise & enterprise governance
Supports a named organizational hierarchy of at least three levels (e.g. enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations.
multi-location-org-hierarchy
EM Administration Guide 3.0.27 names a four-level hierarchy above the terminal: 'You can select all revenue centers by revenue center, region, or company', and the Store Selection window offers 'a site, market, or company' where 'Selecting the check box of a market or company selects all revenue centers affiliated to the selected market or company'. Selections are first-class and reusable — 'Save as a New Custom Selection' creates a named group that can be reselected. Permissions scope to the same objects (job code access levels, Enterprise Rights and report visibility each carry a per-revenue-center Store Settings override) and reports are run against a Store Group selection. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/em3admin/pos_3.0.27_em3admin__en-us.pdf · retrieved 2026-08-03
Corporate menu items expose per-field override rules so a location can change some attributes (e.g. price, availability) while corporate locks others (e.g. name, image, recipe), and locked fields are not editable at store level. differentiator
multi-location-local-override-policy
Not scored by this record.
Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.
multi-location-price-zones
Location-group and daypart variation are both supported off one item record: EM configuration applies to whichever revenue centers, site, market or company is selected, item detail pages carry a Store Settings override per revenue center, Event Prices give 'a change in the default price of a menu item during a limited period' with an Active flag 'in the selected revenue center' and a priority order for overlapping events, and Price Schedules change a price at a set date and time. Shortfall: no channel price book. The EM guides expose per-channel enablement flags (POS, Mobile, Kiosk) but no per-channel price, so an item cannot carry a different price on Kiosk or OrderNow than at the register without duplicating it. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/em3admin/pos_3.0.27_em3admin__en-us.pdf · retrieved 2026-08-03
Menu, price, and promo changes can be scheduled to activate at a future date/time interpreted in each target location's own timezone, and can be rolled back after activation. differentiator
multi-location-scheduled-publish
Not scored by this record.
A new location can be provisioned by cloning a documented configuration template (menu, taxes, roles, printers, modifiers, tenders) rather than being configured from scratch, and the vendor publishes the expected time-to-open. differentiator
multi-location-new-store-template
Not scored by this record.
The permission model distinguishes a franchisor/corporate tenant from an independently-owned franchisee tenant, so corporate can see franchisee sales and enforce config while the franchisee owns its own employees, banking, and labor data. differentiator
multi-location-corp-vs-franchisee-roles
Not scored by this record.
Calculates franchise royalty, ad-fund, and marketing-fee amounts automatically from POS net sales on a defined schedule, with a configurable royalty basis (gross vs net of discounts/comps/third-party). differentiator
multi-location-royalty-calculation
Not scored by this record.
Supports automated ACH/debit collection of calculated royalties and fees from franchisee accounts, with a franchisee-visible statement of what was charged.
multi-location-royalty-collection
Not scored by this record.
Provides above-store reporting that aggregates sales, labor, discounts, voids, and item mix across any selected set of locations in one view, with store-vs-store ranking and variance flags.
multi-location-consolidated-reporting
Not scored by this record.
Item-level sales roll up across locations under a shared corporate item ID even when stores have renamed or locally priced the item. differentiator
multi-location-normalized-item-rollup
Not scored by this record.
Gift cards issued at one location are redeemable at any other location in the brand, with a reported outstanding-liability balance and inter-store settlement/redemption reconciliation between owners.
multi-location-cross-location-giftcard
Not scored by this record.
A single customer loyalty profile, balance, and stored order history is shared across all locations in the brand rather than being per-location.
multi-location-cross-location-loyalty
Not scored by this record.
A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. differentiator
multi-location-multi-brand
Not scored by this record.
Tax configuration is per-location with support for multiple simultaneous tax rates, jurisdiction-specific rules (e.g. prepared-food vs grocery, inclusive vs exclusive tax), and per-location tax exemptions.
multi-location-multi-tax-jurisdiction
Not scored by this record.
Supports locations operating in different currencies and languages within one enterprise account, with consolidated reporting converted to a reporting currency.
multi-location-multi-currency-locale
Not scored by this record.
Produces an immutable audit log of who changed which configuration object (price, tax, permission, discount) at which location and when, exportable or queryable by corporate. differentiator
multi-location-config-audit-log
Not scored by this record.
Supports SSO via SAML or OIDC against the customer's identity provider for back-office/above-store users, with SCIM or equivalent for automated deprovisioning. differentiator
multi-location-enterprise-sso
Not scored by this record.
Publishes a documented multi-location API (or data warehouse/BI export) that returns transaction-level data across all locations in one authenticated call, without per-location credentials. differentiator
multi-location-enterprise-api
Not scored by this record.
Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.
multi-location-central-labor-policy
Not scored by this record.
Hardware & physical footprint
The POS software runs on commodity off-the-shelf hardware (standard iPads, Android tablets, or PCs) that the operator can buy from a third party, rather than only on vendor-supplied proprietary terminals. differentiator
hardware-commodity-devices
Not scored by this record.
Vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs.
hardware-os-platforms
Device specs are published; the client operating system is not. Infor's storefront gives full hardware specs for the current first-party terminal, the T3 (Intel Alder Lake N97/i3-N305, 1x DDR4 up to 8GB, 128GB M.2 SSD, 15.1in 1024x768 true-flat PCAP multi-touch), and for the end-of-life T2 (Bay Trail Celeron, 4GB, 60GB SSD, resistive touch), and names an OS on adjacent SKUs — the POP Server back-office box runs 'Windows 10 IoT 2021' and the PAX payment devices run PayDroid/Android 10 (A35) and Android 11 (Elys A3700). Named shortfall: the OS the Infor POS client itself runs on is stated nowhere — not on the T3 or T2 pages and not in any of the five guides of the 3.0.27 documentation library, which never name Windows, Android, iOS or Linux for any client; no minimum OS versions and no supported-device matrix exist; and the User Guide's Hardware topic explicitly declines to enumerate: 'The available hardware for your Infor POS terminal are based on your subscription agreement with your Infor POS representative.' Whether existing devices or MDM tooling carry over cannot be assessed from what Infor publishes. https://pos.infor.com/products/t3-pos-infor-terminal · retrieved 2026-08-04
Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.
hardware-handheld-purpose-built
Not scored by this record.
The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator
hardware-handheld-battery-swap
Not scored by this record.
Handhelds support cellular/LTE connectivity as a documented fallback when store Wi-Fi drops, either built into the device or via a vendor-supplied failover.
hardware-handheld-lte
Not scored by this record.
Terminals continue to take orders, print to kitchen, and record cash sales with the internet down, and the vendor documents explicitly which functions degrade (card auth, loyalty lookup, refunds).
hardware-offline-mode
The architecture is on-premise-first and Infor distinguishes the two failure modes explicitly: Infor POS is opened 'from your desktop or the local folder', 'Client terminals send data gathered from using Infor POS to a master terminal. The primary terminal then consolidates the data and uploads it to an Infor POS database', and the connectivity indicator has three states — green (Internet and Infor POS cloud), yellow ('connected to the Internet, but not to the Infor POS cloud'), red (no Internet). Card capture during an outage is documented: 'Offline credit — the total amount of credit card authorization requests entered in offline mode and waiting for authorization', plus a PickUp/Drop button that 'sets a payment option offline or online'. Shortfall: Infor publishes no scoped statement of which functions continue or degrade offline; order entry, kitchen routing and loyalty lookup are never addressed for the red-light case, and stored-value behaviour is explicitly handed off — 'Offline capabilities of stored-value cards depend on its provider.' https://docs.infor.com/pos/3.0.27/en-us/useradminlib/user/pos_3.0.27_user__en-us.pdf · retrieved 2026-08-03
Sells or supports a dedicated kitchen display system with bump-bar or touch input, station routing, and course/fire timing, as a first-party product rather than an integration-only dependency.
hardware-kds
First-party, named and sold by Infor. The User Guide's button glossary names the product — the Bump Order button 'Bumps the order off Infor KDS' — and Infor's own storefront (pos.infor.com) carries a Kitchen Display System (KDS) catalogue section with a separate Bump Bars collection and Infor-branded KDS parts (Infor Bump Bar power supply, kitchen display controller components). Station routing is documented in EM ch.7: logical printers connect 'with multiple routing groups to print receipts of specific menu items to different locations, such as multiple kitchens', routing groups attach per menu item and per family group with per-revenue-center Store Settings, printer parameters carry KDS-specific options (Consolidate modifiers to one line; Print Summary No/On Top/On Bottom), and items carry Kitchen Name, Cook Time (min) and Priority ('Menu items with the same priority level are displayed together in the kitchen display'). Course and fire timing is a documented POS workflow — the Coursing chapter's Fire Course 'notify the kitchen staff to start preparing the next course', plus Next Course, Select Course and moving an item between courses — and the EM Speed Of Service Report 'Describes bump times from the KDS' to measure the kitchen. Residual that does not defeat the claim: the 3.0.27 library publishes no dedicated KDS administration guide, so on-screen KDS configuration beyond the printer parameters, and supported bump-bar models, are undocumented — those gaps are scored separately in kitchen-bump-bar-hardware and kitchen-expo-consolidation. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/user/pos_3.0.27_user__en-us.pdf · retrieved 2026-08-04
Offers a self-order kiosk running the same menu and modifier engine as the POS, in both countertop and freestanding form factors, with integrated payment and accessibility (ADA) compliance documented. differentiator
hardware-kiosk
Not scored by this record.
Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, and speaker/headset integration, with a documented timer/speed-of-service measurement.
hardware-drive-thru
Not scored by this record.
Works with standard ESC/POS thermal receipt and kitchen printers from more than one manufacturer (e.g. Epson and Star), including LAN/Ethernet printers, rather than only vendor-branded printers.
hardware-printer-compatibility
Not scored by this record.
Supports the standard peripheral set — cash drawers (including multi-drawer per terminal), barcode scanners, scales for by-weight items, and customer-facing displays — with a published compatibility list.
hardware-peripherals
Not scored by this record.
Card entry happens on a PCI-listed PTS device using validated point-to-point encryption, so the POS application and tablet stay out of PCI scope; the vendor states the merchant's SAQ type.
hardware-p2pe-terminal
Not scored by this record.
Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. differentiator
hardware-tap-to-phone
Not scored by this record.
Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator
hardware-pricing-transparency
Not scored by this record.
Hardware can be purchased outright (owned) as an alternative to a mandatory lease or subscription-bundled rental, and the vendor states which. differentiator
hardware-ownership-vs-lease
Not scored by this record.
Vendor documentation confirms whether hardware purchased from the vendor remains usable with other software after cancellation, i.e. it is not software-locked or remotely bricked. differentiator
hardware-usable-after-churn
Not scored by this record.
Publishes a hardware warranty term and a replacement/advance-exchange SLA with a stated turnaround (e.g. next-business-day depot swap). differentiator
hardware-rma-sla
Not scored by this record.
Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.
hardware-byod
Not scored by this record.
Provides a remote device-management console showing each terminal, printer, and KDS as online/offline, with remote reboot, software-version visibility, and staged rollout of updates. differentiator
hardware-remote-device-management
Not scored by this record.
Integrates with specialty beverage hardware — self-pour tap walls, flow meters, or liquor pour spouts — such that pours post to a POS tab automatically.
hardware-selfpour-scales
Not scored by this record.
Supports inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call.
hardware-callerid-integration
Not scored by this record.
Integrations, API & extensibility
Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.
extensibility-public-api-docs
CLAIM: public, self-serve API reference documentation readable without a signed partner agreement, NDA or sales call. VERDICT: no -> yes. The published no ('the POS technical library is behind a customer login') is FALSIFIED by a surface no prior pass saw. NEW SURFACE (320th, found by crt.sh on vivonet.com, the POS platform Infor acquired; no prior pass or atlas file names it): https://developer.vivonet.com/ is a PRODUCTION 3scale developer portal titled 'Infor Partner API' ('Infor Partner API Portal ... Place orders direct to Halo POS systems, processing through the Infor Cloud', '© Copyright 2026. Infor'; plan 'Partner Developer Access ... 5000 hits per minute, 800000 hits per month'). robots.txt is fully commented out (no bar). /docs loads Swagger UI anonymously. Its registry is a CENSUS: https://developer.vivonet.com/swagger/spec/ (Swagger 1.2 resource listing) and https://developer.vivonet.com/api_docs/services.json both list exactly FIVE specs - apispecs, API_1_1, API_1_1_1, QA_API_1_1_1, QA_API_1_1 - and all five were fetched at 200 (apispecs.json 34,318 B, host api.vivonet.com, 15 operations; API_1_1.json 115,489 B, 76 ops; API_1_1_1.json 92,428 B, 56 ops; the two QA_ copies 118,294 B and 95,236 B), soft-404 control /swagger/spec/zzq.json -> 404. PRODUCTION STATUS: apispecs.json declares host api.vivonet.com (production, answers /status anonymously); API_1_1 and API_1_1_1 are the production-named registry entries that /docs loads by default but their host field reads vvnapi-staging.qa.vivonet.com; the QA_ entries are pre-release and were used for nothing below. The link to Infor POS is established: the Infor OrderNow client already cited in this cell is configured with apiUrl https://api.vivonet.com and logs 'Partner API version', and the spec's /v1.1/companies/{companyId}/terminalHealthStatus matches the Infor POS Terminal Health feature. EVIDENCE: https://developer.vivonet.com/docs renders Swagger UI with no sign-in ('Sign in to your account for quick access to useful values' is optional), loading /swagger/spec/API_1_1_1.json; the landing page says 'Register for your Partner Developer account today to gain access to the Infor API, allowing your applications to interact with services in the Infor cloud and with Point of Sale and Mobile devices in stores today', and https://developer.vivonet.com/signup?plan_ids[]=2357355819573 is an open self-serve form ('You are signing up to plan Partner Developer Access.': Organization Name, username, name, phone, email) at 200. The reference is complete and field-level: 76 operations in API_1_1 with full request/response schemas (Product, menu categories, menuItems, discounts, tenders, orders place/get/add items/pay/close, receipts, employees, terminalHealthStatus, data/orders time-range export). Every conjunct: public (anonymous 200), API reference (Swagger 2.0), no agreement/NDA/sales call to read it. The docs.infor.com /technical/ SAML gate is real but no longer decides this cell. Retrieved 2026-09-16. https://developer.vivonet.com/docs · retrieved 2026-09-16 adversarially verified
API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator
extensibility-api-access-cost
Not scored by this record.
A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator
extensibility-free-sandbox
Not scored by this record.
Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).
extensibility-oauth-partner-apps
329th: THE 320th MERGE HOLD IS ANSWERED BY A NEW INFOR-PUBLISHED SURFACE, NOT BY MORE OF THE SAME. The hold was that developer.vivonet.com is a census of THAT partner API only and not of Infor POS integration surfaces. NEW HOST, named by no prior note and in no atlas file: https://archive.docs.infor.com/ (Infor's own documentation archive, discovered in the docs.infor.com client config as window.env.ARCHIVEDOMAIN inside https://docs.infor.com/static-867db65b/js/env.js). It serves EIGHT archived Infor POS useradminlib generations that docs.infor.com no longer lists - 3.0.21, 3.0.22, 3.0.23, 3.0.24, 3.0.25, 3.0.26, 3.0.27, 3.0.28 - each with its own publisher manifest sitemap.html (3.0.27 = 35,749 B/469 hrefs, 3.0.23 = 40,467 B/522 hrefs). Both manifests were fetched to 100%: 469/469 and then the union of the other seven, 600/600 further files, ZERO misses, total 1,069 topic files and 17,245,444 raw bytes searched with HTML comments stripped and no tag stripping. Those generations publish THREE folders the current 2026.08 library does not have at all: em1admin (the removed Enterprise Manager v1 guide, 90 topics), admin (15) and, decisively, release_notes_2020 / release_notes_2021 / release_notes_2022 / release_notes_2023 (~130 topics, 'INF.Map.Publication.PubTitle = Infor POS Release Notes for 2021'). WHAT THE RELEASE NOTES ESTABLISH ABOUT THE HOLD. Infor's own release notes carry a recurring chapter titled 'Infor POS Partner API' (release_notes_2020/hib1564730804314.html, imk1594620363100.html, tnc1585552354038.html; release_notes_2021/bkh1599120447213.html, ond1615186326447.html; release_notes_2022/muw1634798499801.html - all six are chapter headers with empty bodies), and the nine leaf topics under it are Infor's complete published change history of its third-party API: 'A new endpoint is now available in Infor POS Partner API for allowing the update of table status' (release_notes_2020/vni1574750391230.html), 'A new endpoint is now available for Infor POS Partner API to enable a phone number field' (huo1585206200240.html), 'The notificationPhoneNumber API field is now available' (int1598499841863.html), 'A new API endpoint is now available to support Infor POS when retrieving order ready SMS notifications' (release_notes_2021/pta1607680744564.html), 'To support terminal health status, API endpoints now return terminal status information' (ihi1611121346789.html), 'The API endpoints are extended to support Sodexo requirements' (release_notes_2022/ymk1635313580391.html), 'The Open Discount All function is now supported for API third-party partners. API partners can now send a discount amount of any value' (jri1635313529373.html), and two 'Third-party applications certification' topics: 'These third-party applications are now certified: Yellowdog: Menu Insert API / Hangry mobile ordering: Closed check API' (release_notes_2021/zwx1623309282169.html) and 'Birchstreet: Menu Insert API / Nutrislice mobile ordering: Closed check API / UEAT mobile ordering: Closed check API' (release_notes_2022/yyt1640311239556.html). So Infor itself names 'Infor POS Partner API' as THE surface third-party applications integrate through, its terms of art are 'API third-party partners' and 'API partners', and the two APIs it names in the certification list (Menu Insert, Closed check) are the menuItems and orders/{tabId} operations of the anonymously published portal. The portal is therefore not one API among Infor's POS integration surfaces; it is the one Infor documents. THE AUTHORISATION MODEL, RE-VERIFIED LIVE TODAY, NOT INHERITED. https://developer.vivonet.com/api_docs/services.json still returns 200/600 B and still lists exactly five specs (apispecs, API_1_1, API_1_1_1 and the two QA_ copies); soft-404 control /swagger/spec/zzq-nonsense.json returns 404/22 B; https://api.vivonet.com/status still answers {"appVersion":"2.9.0.127","appName":"vvnapi"}. The production spec (apispecs.json, 34,328 B, host api.vivonet.com) was re-parsed today: it has NO securityDefinitions and no security block anywhere (its top-level keys are swagger, info, host, basePath, tags, schemes, paths, definitions, parameters), and 15 of 15 operations require the static header parameter xApiKeyParam {"name":"x-api-key","in":"header","description":"Your API access key","required":true}. The operation list is closed: GET products, categories, menuItems/{menuItemId}, discounts, storeDetails, tenders, orders/receipt/{correlationId}, orders/{tabId}, apiKeys/stores, employees; PUT orders/data; POST orders, receipts/email, orders/{tabId}/items; PATCH orders/{tabId}. Scoping is Infor-side entitlement, not an operator grant: 'GET /v1/apiKeys/stores - returns a list of the Stores that the API Key entitles a partner to access.' Grant is by INFOR CERTIFICATION of the partner (the two certification topics above), not by the merchant authorising an app, and there is no consent, no scope and no revocation resource. CONTROLS, tokenised word-boundary case-insensitive, over the fresh production spec: oauth 0, bearer 0, token 0, scope 0, revok 0, notif 0. CONTROLS OVER THE ENTIRE NEW 1,069-FILE, 17,245,444-BYTE ARCHIVE CORPUS: OAuth 0, token 0, bearer 0, secret 0, revoke 0, web service 0, SOAP 0, middleware 0, marketplace 0, integrator 0, endpoint 38 (ALL 38 in release_notes_2020/2021/2022 and every one the request/response endpoints quoted above - this is a real count where the current library scores 0, so a later pass must not treat endpoint-0 as a property of Infor), API 333, api key 2, credentials 40, REST 2, JSON 8. Corpus positives pass: Infor 10,580, menu 7,521, print 3,411, check 2,968. POISON NAMED: XML 1,614 is Oxygen WebHelp chrome in every file and carries no product meaning; 'scope' 2 is 'scope of this document' in em1admin/dvo1618374896651.html; 'third-party' 103 is overwhelmingly the kiosk guide's third-party payment and loyalty providers. BOUND AND RESIDUAL DOUBT. The SAML gate on docs.infor.com/pos/<ver>/en-us/technical/ is unchanged and archive.docs.infor.com gates its /technical/ copies identically (3.0.26 and 3.0.27 both 302 to /docs/sso?contentUri=...), so the gate was not evaded and cannot be recovered there either; docs.infor.com's own content API (https://docs.infor.com/api/v2/products, /contents, /search) answers 401 {"success":false,"message":"No authorization (bearer)."} to every anonymous GET and no token was obtained. What is no longer in doubt is that Infor publishes a third-party API contract anonymously and that contract is a static per-partner key on every operation with Infor-side, not operator-side, entitlement. Retrieved 2026-09-18. https://developer.vivonet.com/swagger/spec/apispecs.json · retrieved 2026-09-18 adversarially verified
The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.
extensibility-webhooks-push
329th: NEW INFOR-PUBLISHED SURFACE THAT ANSWERS THE 320th HOLD. https://archive.docs.infor.com/ is a host no prior note names; it was found in docs.infor.com's own client config (window.env.ARCHIVEDOMAIN in https://docs.infor.com/static-867db65b/js/env.js) and it serves eight archived Infor POS useradminlib generations (3.0.21-3.0.28) that docs.infor.com/sitemap.xml no longer lists. Each generation ships the publisher's own manifest, sitemap.html, and both extremes were fetched to 100% with zero misses (3.0.27: 469/469 hrefs; union of the other seven: 600/600 further files), giving 1,069 topic files and 17,245,444 raw bytes. It contains folders the 2026.08 library does not have: em1admin (the removed EMv1 guide), admin, and ~130 topics of release_notes_2020 / 2021 / 2022 / 2023. THE ENUMERATION THAT SETTLES THIS CELL. Those release notes carry a recurring 'Infor POS Partner API' chapter (six header topics: release_notes_2020/hib1564730804314.html, imk1594620363100.html, tnc1585552354038.html; release_notes_2021/bkh1599120447213.html, ond1615186326447.html; release_notes_2022/muw1634798499801.html) whose nine leaf topics are Infor's own complete published change history of its third-party API across three years. EVERY ONE IS A REQUEST/RESPONSE ENDPOINT OR A REQUEST FIELD, AND THE PULL DIRECTION IS EXPLICIT IN INFOR'S OWN WORDING: 'A new API endpoint is now available to support Infor POS when RETRIEVING order ready SMS notifications' (release_notes_2021/pta1607680744564.html); 'To support terminal health status, API endpoints now RETURN terminal status information' (ihi1611121346789.html); 'A new endpoint is now available in Infor POS Partner API for allowing the update of table status depending on the progress of the service' (release_notes_2020/vni1574750391230.html); 'The notificationPhoneNumber API field is now available' (int1598499841863.html); 'The Open Discount All function is now supported for API third-party partners. API partners can now SEND a discount amount' (release_notes_2022/jri1635313529373.html); plus 'Support for DAAS' (ymk1635313580391.html) and two 'Third-party applications certification' topics naming 'Menu Insert API' and 'Closed check API' as the integration routes for Yellowdog, Hangry, Birchstreet, Nutrislice and UEAT (release_notes_2021/zwx1623309282169.html, release_notes_2022/yyt1640311239556.html). In three years of Infor's own API release notes there is not one subscription, registration, callback, event-delivery or push topic. That is the Infor-side enumeration the 320th hold said was missing: the developer.vivonet.com portal is not one partner API among Infor's POS integration surfaces, it is the API Infor documents and certifies partners against. LIVE RE-VERIFICATION TODAY, NOT INHERITED. api_docs/services.json 200/600 B, still exactly five specs; soft-404 control /swagger/spec/zzq-nonsense.json 404/22 B; api.vivonet.com/status 200 {"appVersion":"2.9.0.127","appName":"vvnapi"}. The production spec apispecs.json (34,328 B, host api.vivonet.com) re-parsed today has a CLOSED operation list of 15 - GET products, categories, menuItems/{menuItemId}, discounts, storeDetails, tenders, orders/receipt/{correlationId}, orders/{tabId} ('Get order from POS'), apiKeys/stores, employees; PUT orders/data; POST orders, receipts/email, orders/{tabId}/items; PATCH orders/{tabId} ('Closes order on POS') - with no subscription, registration or callback resource, and API_1_1's time-windowed 'GET /v1/companies/{companyId}/stores/{storeId}/data/orders - Returns orders (closed checks) for a single store in a given company and time range (max 24 hours)' is the polling shape the claim contrasts itself with. CONTROLS over the fresh production spec, tokenised and word-boundary: webhook 0, callback 0, subscri 0, notif 0, push 0, poll 0, socket 0. CONTROLS OVER THE ENTIRE NEW 1,069-FILE, 17,245,444-BYTE ARCHIVE CORPUS: webhook 0, callback 0, poll 0, polling 0, queue 0, queued 0, web service 0, SOAP 0, store-and-forward 0; endpoint 38, ALL of them the release-note endpoints quoted above (a real count where the current 374-topic library scores 0). POISON NAMED AND READ: 'push' 4 splits into em3admin/auh1653547580332.html (2, the incidental hits a prior note already recorded) and release_notes_2023/yqt1653523108793.html (2) - the latter is 'POS messages: You can add POS messages to PUSH NOTIFICATIONS to terminals that have general service updates for cashiers', which is Infor pushing a text message to its OWN cashier terminals and is NOT an event delivered to an integrator's endpoint; a counter would publish a false yes from it. 'subscription' 17 is the commercial sense ('your subscription agreement with your Infor POS Kiosk representative'). 'notification' 23 and the whole SMS-alert family are messages to GUESTS' phones, not to registered endpoints. 'event' 186 is the Enterprise Manager calendar/pricing event object in both EM generations. Corpus positives pass: Infor 10,580, menu 7,521, print 3,411, check 2,968. BOUND AND RESIDUAL DOUBT. docs.infor.com/pos/<ver>/en-us/technical/ remains SAML-gated and archive.docs.infor.com gates its /technical/ copies identically (3.0.26 and 3.0.27 both 302 to /docs/sso?contentUri=...), so the gate stands unevaded; docs.infor.com's content API (/api/v2/products, /contents, /search) returns 401 'No authorization (bearer)' to anonymous GET and no token was obtained. The no rests on the anonymously published production spec plus Infor's own three-year enumeration of that API's changes, both of which are pull-only. Retrieved 2026-09-18. https://developer.vivonet.com/swagger/spec/apispecs.json · retrieved 2026-09-18 adversarially verified
Webhooks are cryptographically signed (e.g. HMAC) AND documented to retry with backoff, with a replayable event log for missed deliveries. differentiator
extensibility-webhook-reliability
Not scored by this record.
A public write API accepts externally originated orders into the POS as first-class tickets that fire to KDS/printers and land in reporting.
extensibility-order-injection-api
Not scored by this record.
Every core object the API can read (orders, menu, customers, employees, inventory) can also be written or updated via the same API. differentiator
extensibility-data-symmetry
Not scored by this record.
API rate limits are published as specific numeric quotas with documented throttling behavior and headers.
extensibility-published-rate-limits
Not scored by this record.
The vendor is a named DoorDash Preferred Integration Partner (DPIP) under the 2026 program requirements. differentiator
extensibility-doordash-preferred
Not scored by this record.
Direct, first-party certified integrations exist with DoorDash, Uber Eats, and Grubhub without requiring a paid middleware layer (Otter/Chowly/Deliverect/Checkmate). differentiator
extensibility-first-party-delivery-integrations
Not scored by this record.
The POS is a supported endpoint for at least two major aggregation middleware platforms (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate).
extensibility-middleware-compatibility
Not scored by this record.
Native, vendor-maintained connectors exist for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export.
extensibility-accounting-connectors
Not scored by this record.
Labor hours export natively to at least two named payroll providers (e.g. Gusto, ADP, Paychex, Paylocity) without manual re-keying.
extensibility-payroll-export
Not scored by this record.
Raw transaction-level data can be exported on a schedule to a customer-controlled destination (S3/SFTP/warehouse/Snowflake share), not only viewed in the vendor's reporting UI. differentiator
extensibility-bi-data-warehouse
Not scored by this record.
The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.
extensibility-app-marketplace
Not scored by this record.
Operators can define custom fields or run vendor-hosted custom logic/scripts against POS objects without a vendor engineering engagement.
extensibility-custom-fields-scripting
Not scored by this record.
The vendor supports a headless/embedded mode where a third-party UI (kiosk, web ordering, drive-thru) drives the POS transaction engine via API.
extensibility-headless-embedded
Not scored by this record.
The vendor publishes an API changelog and a stated deprecation/notice policy for breaking changes.
extensibility-api-versioning-deprecation
Not scored by this record.
A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator
extensibility-data-portability-exit
Not scored by this record.
Reliability, offline & operations
Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.
reliability-offline-order-entry
Local-first operation is evidenced but not stated as a guarantee. The application runs from the local machine, client terminals post to an in-store primary terminal that consolidates and then uploads to the cloud, a revenue center can be given a backup terminal role in a primary terminal (Backup RVC), and the connectivity indicator treats 'connected to the Internet, but not to the Infor POS cloud' as a distinct working state. Cards can be taken while disconnected via offline authorization entry. Shortfall: Infor nowhere states that order entry, ticket routing to the kitchen and check printing continue when the Internet connection is lost — the red-light state is defined but its operational consequences are never described, and the guide gives no offline scope or limits. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/user/pos_3.0.27_user__en-us.pdf · retrieved 2026-08-03
Card payments can be accepted while offline via store-and-forward, not just cash-only fallback. differentiator
reliability-offline-card-auth
Not scored by this record.
The vendor publicly documents who bears the loss when a store-and-forward transaction declines after connectivity returns, and states any per-transaction or cumulative offline cap. differentiator
reliability-offline-decline-liability
Not scored by this record.
Multiple terminals continue to share a single check/table state over the local network while the internet is down (LAN-only degraded operation, not per-terminal islands). differentiator
reliability-lan-degraded-multi-terminal
Not scored by this record.
The vendor documents a local/on-premise transaction engine or edge server (not purely cloud-hosted request/response) for the ordering path. differentiator
reliability-local-transaction-engine
Not scored by this record.
Kitchen display and/or kitchen printer routing continues to function while offline.
reliability-offline-kds-printing
CLAIM: kitchen display and/or kitchen printer routing continues to function while offline. NOT ESTABLISHED for any offline condition in the Infor POS 2026.08 library; the cell stays unknown. WHAT IS MET: only an adjacent capability, peer-terminal redundancy. 'Configuring backup revenue centers' (https://docs.infor.com/pos/2026.08/en-us/useradminlib/user/erx1576721787745.html, a topic new in this generation and absent from 3.0.27) says: 'If your restaurant uses several POS terminals and the primary terminal goes offline, a designated backup terminal can take over... For example, during a busy dinner service, the primary terminal loses power... After approval, the backup terminal becomes the new primary terminal. Staff can continue accessing open checks, processing payments, printing receipts, and sending orders to the kitchen without interruption.' Infor's own worked example fixes the meaning of 'goes offline' here as loss of ONE TERMINAL (power), not loss of connectivity: the in-store architecture is described at https://docs.infor.com/pos/2026.08/en-us/useradminlib/user/nak1561442755105.html as 'Client terminals send data gathered from using Infor POS to a master terminal. The primary terminal then consolidates the data and uploads it to an Infor POS database', so Backup RVC is redundancy of the in-store master role and is silent about the WAN. SHORTFALLS: (1) No published topic states that kitchen chits or a KDS keep working during an internet or LAN outage. (2) The 'Connectivity indicator' topic (https://docs.infor.com/pos/2026.08/en-us/useradminlib/user/ytw1555619776257.html) is a bare three-row table - 'Green light: Infor POS is connected to the Internet and the Infor POS cloud. Yellow light: Infor POS is connected to the Internet, but not to the Infor POS cloud. Red light: Infor POS is not connected to the Internet.' - and attaches NO operational consequence to the yellow or red state; it names states, it does not say orders still reach the kitchen. (3) The documented offline paths are payment paths only: 'Processing offline transactions for a stored-value card' ('If the internet connection is down, you can process a stored-value card payment as an offline transaction and close the check... queues up for automatic processing when the Internet is re-established', user/ble1560242911282.html), an 'Offline credit' report line ('The total amount of credit card authorization requests entered in offline mode and waiting for authorization', user/eqz1555619808989.html) and an 'Offline' tender checkbox ('disable card-based tenders when in offline mode', em3admin/itv1643605702763.html). Infor therefore knows how to document offline behaviour and does so for tenders, while saying nothing of the kind for the kitchen path. (4) The 2026.08 library still publishes no KDS guide; KDS appears only as a printer-parameter target ('Consolidate... displayed as one line in a kitchen display system (KDS)', 'Print Summary: For a KDS', em3admin/izw1570607551347.html), as a bump function ('Bump Order: Bumps the order off Infor KDS') and as an integrated third-party notifier, so the display side is undocumented in every respect. (5) Printer recovery is manual, not automatic ('Redirect Printer', 'Auto-Redirect Printers: Redirects the printing of a receipt of all printers to another printer', user/okv1562227265437.html), invoked by a person from the functions menu. WHY NOT PARTIAL: the one thing the cited topic establishes - continuity across a dead peer terminal - is not the claim, and the proposal's own shortfall concedes the claim's only conjunct is unmet, so a 'partial' would shortfall every conjunct. CONTROLS (tokenised, word-boundary, over the 374-topic 2026.08 corpus - user, em3admin, kadmin, posonapag): positives Infor 661/242 files, menu 925, check 614, printer 63, kitchen 46, print 71, so the corpus reads. offline 19 hits in 9 files (all read; payments, the Terminal Health 'Offline' tab, and the Backup RVC topic - none about kitchen behaviour in an outage), KDS 11, 'kitchen display' 4, internet 8, cloud 7, 'local mode' 2 (a kiosk MENU SCHEDULE mode, not a degraded-operation mode - a near-miss trap), 'primary terminal' 15, unavailable 6. Genuine zeros: outage, failover, queue/queued, spool, store-and-forward, degraded, reconnect, redundant, 'backup printer', unreachable, buffer, resume, network, LAN, Wi-Fi. Both cited URLs were re-fetched live with a browser UA: 200, 12159 and 11429 bytes, byte-identical to the cached topics, real topic content, no interstitial. No PDF-derived zero was used (Infor PDFs extract control words as 0). || 320th: 320th NEW SURFACES, no kitchen offline behaviour. (1) Infor Partner API portal https://developer.vivonet.com/ (five-spec census): offline 0, kitchen 0, kds 0. (2) Enterprise Manager front end https://emweb.hpo.inforcloudsuite.com/entMgr/ (production bundle 2,365,509 B + 157 templates): 'offline' 14 in the bundle and 20 in app/reports/templates/terminal.content.html are all the Terminal Health report ('$scope.labels=["Offline","In Use"]', 'Offline Since:') plus 2 in the integrated-tender editor ('enableOffline' / offLineEnable, the offline card-tender checkbox already cited); none concerns printers or KDS during an outage. crt.sh also lists ddsync.vivonet.com, sso.vivonet.com, audit.vivonet.com (connect timeout) and dev/qa/sandbox/stage/staging.hpo.inforcloudsuite.com (NXDOMAIN); mobile-insights.hpo.inforcloudsuite.com is an S3-backed app whose non-root paths 403 (refusal, not absence). Wayback CDX was offline 2026-09-16. Retrieved 2026-09-16. || 323rd: 323rd, NEW PRODUCTION HOST, NOT NAMED BY ANY PRIOR NOTE. crt.sh on inforcloudsuite.com (1,215 names) and vivonet.com (56) and halopos.com (6) was re-run; the only previously unrecorded live surface is the OrderNow ADMIN console, https://admin-ordernow.hpo.inforcloudsuite.com/ (HTTP 200, 1,531 bytes, <title>OrderNowAdmin</title>; it is NOT a soft-200 catch-all - /zzz-nonsense-path returns an honest 404 of 352 bytes). It is bounded by the publisher's own Angular service-worker manifest /ngsw.json (200, 26,686 bytes, 172 assets of which 119 are .js), and the application closure is 7 files - runtime/polyfills/main/scripts in es2015 and es5 twins; the other 112 .js are the ids-enterprise LOCALE CULTURE files, which are the classic false-hit source and were excluded. The four es2015/neutral files were read as raw bytes: 2,921,020 bytes. NO SOURCE MAP IS PUBLISHED and this was controlled: main-es2015.2e23f4fc6920945296f0.js.map returns 404/374 bytes and the fabricated sibling main-es2015.ZZZZZZZZ.js.map returns 404/362 bytes, i.e. the same shape, so there is no map to parse and no SPA-shell soft 200 was mistaken for one. halopos.com and www.halopos.com are a PARKED 'Reserved for halopos.com' placeholder page, not a product. ecs/go/reports/legacy/page.vivonet.com and stage/hpo.inforcloudsuite.com do not answer (connection failure, not a refusal); ssee.vivonet.com returns 403 to curl with a browser UA and the Accept/Accept-Language pair, which is a refusal and not an absence. WHAT IT HELD FOR THIS CELL: nothing about degraded operation. Over the whole 2,921,020-byte closure, tokenised, word-boundary, case-insensitive: offline 0 (it does not even carry the Terminal Health 'Offline' label that the Enterprise Manager front end does), printer 0, kds 0, kitchen 0, outage 0, failover 0, queue 0, spool 0, reconnect 0; positives menu 448, store 22, order 14. 323rd, THE WAYBACK ROUTE IS NOW CLOSED FOR THIS VENDOR. Every note on this record is capped by the SAML-gated https://docs.infor.com/pos/2026.08/en-us/technical/ library, and the 320th recorded that Wayback was offline on 2026-09-16 so the walled-docs-may-have-been-public check could not be run. It was run today and the archive is up: http://web.archive.org/cdx/search/cdx?url=docs.infor.com%2Fpos%2F*&output=json&collapse=urlkey returns 52,316 bytes of captures of the OPEN useradminlib topics (2026.02 em3admin/user/kadmin/posonapag .html files, 200s), while the same query narrowed to docs.infor.com/pos/2026.08/en-us/technical/* and to docs.infor.com/pos/*/technical/* returns ZERO rows on both. The gated technical library has never been archived, so it was never public and cannot be recovered. docs.vivonet.com has no captures either; developer.vivonet.com has 22 (2017-2019, all portal chrome: /docs, /login, /signup, /robots.txt, bootstrap css/js) and api.vivonet.com has 3. That closes the last untried retrieval route named in this note's history: the kitchen-path offline behaviour was never published anonymously and no archived copy of the gated library exists to recover it from. Retrieved 2026-09-17. || 329th: 329th: THE CORPUS TRIPLED AND THE KITCHEN-OFFLINE ZEROS HELD. New host, named by no prior note: https://archive.docs.infor.com/ (found in docs.infor.com's own client config, window.env.ARCHIVEDOMAIN in https://docs.infor.com/static-867db65b/js/env.js). It serves eight archived Infor POS useradminlib generations docs.infor.com/sitemap.xml no longer lists (3.0.21-3.0.28), each with its own publisher manifest sitemap.html; 3.0.27 was fetched 469/469 and the union of the other seven 600/600, zero misses, 1,069 topic files and 17,245,444 raw bytes, adding em1admin (the removed EMv1 guide), admin and ~130 release-note topics for 2020-2023 that no prior pass held. WHAT IT HELD FOR THIS CELL. Nothing that gives the kitchen path continuity, and one new near-miss in the OPPOSITE direction: 'Error messages for customers - If the POS terminal is offline or not available, a message is now displayed to inform the customers.' (release_notes_2022/djl1635313302645.html), which is the OrderNow/kiosk guest being told ordering is unavailable, i.e. Infor documenting a STOP rather than a degraded-operation path - it is about the guest-ordering front end, not about chits or a KDS, and it is not evidence either way for the claim. The Backup RVC feature the existing note already cites is confirmed to be terminal redundancy and nothing more by its own release note: 'Backup primary terminal - You can now set up a backup primary terminal that can run when the primary terminal fails or goes offline' (release_notes_2023/aml1635313601910.html). CONTROLS OVER THE WHOLE NEW 1,069-FILE, 17,245,444-BYTE CORPUS, tokenised word-boundary case-insensitive: outage 0, failover 0, queue 0, queued 0, spool 0, reconnect 0, degraded 0, resume 0, buffer 0, store-and-forward 0, LAN 0, expediter 0, station 0. offline 69 across both EM generations, the kiosk guide, the user guide and the release notes, every file listed and the new ones read: em3admin/hte1577427374099.html (2) is 'Viewing the status of a revenue center' and its hits are the Terminal Health Dashboard's Offline tab, not kitchen behaviour. internet 24, network 16, kitchen 209, KDS 88, 'kitchen display' 17 - all read, none attaching an operational consequence to a connectivity state for the kitchen path. Corpus positives pass: Infor 10,580, menu 7,521, print 3,411, check 2,968. So across three additional years of Infor POS release notes and a whole removed administration guide, Infor never states that kitchen chits or a KDS keep working during an outage, and never states that they stop; the documented offline paths remain payment paths. ROUTES CLOSED TODAY: the publisher's topic manifest is now at 100% on the current AND all eight archived generations; the 2026.08 Oxygen WebHelp static search index is a disabled stub (index-1.js 148 bytes returning {"test":...}, index-2/3.js 74 bytes, htmlFileList.js and keywords.js 404 with the 6,877-byte error page), so no unlisted topic list exists; docs.infor.com's content API (/api/v2/products, /contents, /search) answers 401 'No authorization (bearer)' anonymously and no token was obtained; archive.docs.infor.com gates /technical/ identically to docs.infor.com (302 to /docs/sso). The iTunes publisher census of Infor (US), LLC (artistId 493525183, 59 apps) contains exactly one POS app, Infor POS Mobile Insights (6475422870), a reporting app, so there is no store-level or KDS app whose screenshots could show degraded-mode behaviour. This stays unknown: absence of an offline statement is not a capability no. Retrieved 2026-09-18. adversarially verified
The system automatically fails over to a backup printer or KDS station when a configured kitchen printer is unreachable, and alerts staff.
reliability-printer-fallback
The EM printing chapter is a complete enumeration of the printing model — logical printers ('a logical printer represents a physical printer in your revenue center'), printer parameters, routing groups, assignment of routing groups to logical printers, receipt and report properties, headers and trailers — and no logical printer or routing group carries a backup, failover or alert setting. Infor's documented remedy for an unavailable printer is manual and after the fact: the POS Redirect Printer function offers Restore Printer, Redirect Printer, 'Auto-Redirect Printers — redirects the printing of a receipt of all printers to another printer' and Assign Printer, all invoked by a user from the functions menu. Automatic failover on an unreachable printer, and staff alerting, are not part of the product. https://docs.infor.com/pos/3.0.27/en-us/useradminlib/em3admin/pos_3.0.27_em3admin__en-us.pdf · retrieved 2026-08-03
The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).
reliability-sync-conflict-handling
Not scored by this record.
The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).
reliability-offline-feature-matrix
Not scored by this record.
A public, per-component status page exists showing current and historical incident state without a login.
reliability-public-status-page
Not scored by this record.
A contractual uptime SLA with a stated percentage AND a service credit remedy is published or available in the standard agreement. differentiator
reliability-contractual-uptime-sla
Not scored by this record.
The vendor publishes written post-incident reports or root-cause summaries for major outages.
reliability-incident-postmortems
Not scored by this record.
24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.
reliability-247-live-support
Not scored by this record.
The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator
reliability-onsite-install
Not scored by this record.
A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.
reliability-hardware-replacement-sla
Not scored by this record.
Operators can trigger and retrieve their own data backup/restore, or the vendor publishes RPO/RTO figures for data recovery.
reliability-backup-restore
Not scored by this record.
The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.
reliability-pci-dss-4-attestation
Not scored by this record.
Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.
reliability-mfa-role-based-access
Not scored by this record.
A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.
reliability-self-serve-training
Not scored by this record.
Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. differentiator
reliability-failover-terminal-role
Not scored by this record.
Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.
reliability-cellular-backup
Not scored by this record.
Commercial, compliance & data ownership
Vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core POS software tier. differentiator
commercial-month-to-month-contract
Not scored by this record.
Vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. differentiator
commercial-no-early-termination-fee
Not scored by this record.
The auto-renewal term and the required cancellation notice window (e.g. 30/60/90 days) are stated in publicly accessible contract terms rather than only in a signed quote.
commercial-autorenew-terms-published
Both halves of the claim — the renewal term and the notice window — are stated in Infor's own standard contract text, publicly downloadable without login. Infor's 'On-Premises Software Terms and Conditions' (dated November 2023, hosted on Infor's own DAM) §4b: the term 'shall (i) begin on the Order Form Date and end on the last day of the twelve-month period beginning on the Order Form Date, unless a longer time period is agreed upon in the Order Form, and (ii) renew for successive twelve month renewal periods, unless either party provides written notice to the other party of non-renewal at least 90 days prior to the commencement of such renewal period (Infor will notify Customer at least 30 days prior to the notice period of the renewal period and the next Support fee)'. Infor POS is sold as a subscription, and that document states 'Infor does not provide Cloud Services with respect to On Premises Software' — the matching subscription instrument is Infor's 'Subscription License and Services Agreement (US March 2019)', between 'Infor (US), Inc.' and the Licensee, §10a: 'the Initial Subscription Term shall be as set forth on the applicable Order Form. After the Initial Subscription Term, the Subscription Term shall renew for successive one-year Renewal Terms, unless either party provides written notice of non-renewal to the other party at least ninety (90) days prior to expiration of the Initial Subscription Term or then current Renewal Term.' Same 90-day window on both paper trails, so the diligence question the claim asks is answerable before signing. Two caveats that do not defeat the claim: only the initial term length is quote-specific (it sits on the Order Form), and the subscription agreement is published via Infor reseller and public-procurement channels (dlt.com/sites/default/files/documents/2021-03/Infor-SaaS-EULA.pdf) rather than on infor.com — infor.com/about/legal links only a privacy policy, terms of use and modern-slavery statement, with no contract library. https://dam.infor.com/api/public/content/a43a38c17c5f4338986840a9f870af00?v=4fab71ce · retrieved 2026-08-04
The POS software can be purchased and operated with a third-party payment processor of the operator's choice (no mandatory in-house processing lock). differentiator
commercial-processing-not-bundled
Not scored by this record.
Vendor publishes an interchange-plus (cost-plus) processing rate option with the markup stated as a specific bps + per-transaction figure, rather than only blended/flat card-present rates. differentiator
commercial-interchange-plus-published
Not scored by this record.
The processing agreement caps or prohibits unilateral vendor-initiated rate increases outside of pass-through interchange/network changes, or grants penalty-free exit on any increase. differentiator
commercial-rate-increase-clause
Not scored by this record.
Per-location and per-additional-terminal software pricing is published as specific dollar figures on the vendor's public site (not 'contact sales' only).
commercial-pricing-published
No pricing on Infor's hospitality industry page; enterprise contact-sales motion. https://www.infor.com/industries/hospitality · retrieved 2026-08-01
Individual modules (online ordering, KDS, loyalty, inventory, payroll, marketing) can be purchased à la carte and cancelled independently without repricing the base POS subscription. differentiator
commercial-module-unbundling
Not scored by this record.
All required terminals, KDS screens, and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental.
commercial-hardware-purchase-outright
Infor runs its own hardware storefront at pos.infor.com carrying the full required kit as purchasable goods — POS Terminals, Kitchen Display System (KDS) with bump bars, Thermal and Impact Receipt Printers, label printers, Cash Drawers, Payment Devices, Monitors, Cables, Power Supplies and Swipe Cards — and no lease, rental or financing programme is offered or referenced anywhere on the store, so nothing indicates a mandatory multi-year hardware lease. Named shortfall: not one published price. The current flagship, the Infor POS T3 Terminal (modular 15.1in all-in-one), shows no numeric price and reads 'Coming soon!' with 'Current clients please contact your sales representative for pricing and availability. New customers please call our sales department for assistance 603-889-5152'; the superseded T2 Terminal page carries the same contact-sales instruction plus an end-of-life notice, and no product page exposes an add-to-cart or checkout flow. The User Guide reinforces that hardware is bundled into the negotiated deal rather than sold off a price list: 'The available hardware for your Infor POS terminal are based on your subscription agreement with your Infor POS representative.' So outright purchase is the evident model and no lease is imposed, but the 'at a published price' half of the claim fails outright — every SKU is quote-only, and hardware TCO cannot be diligenced without contacting sales. https://pos.infor.com/products/t3-pos-infor-terminal · retrieved 2026-08-04
Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator
commercial-hardware-not-locked
Not scored by this record.
One-time implementation, menu-build, onboarding, and training fees are published as specific amounts or explicitly stated as $0.
commercial-implementation-fee-published
Not scored by this record.
Operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee.
commercial-data-export-self-serve
Not scored by this record.
Guest/customer records, loyalty balances or point ledgers, and gift-card liability balances are exportable in machine-readable form by the operator. differentiator
commercial-export-customer-and-loyalty
Not scored by this record.
Contract or documentation specifies a post-termination data retrieval window (a defined number of days during which the operator can still export their data) rather than immediate cutoff. differentiator
commercial-post-termination-export-window
Not scored by this record.
Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator
commercial-data-ownership-clause
Not scored by this record.
The POS is source-available or open source with a documented self-hosting option (source published under an OSI or source-available license, not merely an open API).
commercial-source-available-selfhost
Not scored by this record.
Vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A / SAQ P2PE-HW, and names the applicable SAQ.
commercial-pci-p2pe-tokenization
Not scored by this record.
Vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — notably MFA for all access to the cardholder data environment including POS and back-office logins, and (for hosted ordering pages) payment-page script integrity monitoring per Req 6.4.3/11.6.1.
commercial-pci-dss-4-controls
Not scored by this record.
Vendor states it holds a current SOC 2 Type II (or ISO 27001) attestation and will provide the report under NDA via a trust center or on request.
commercial-soc2-attestation
Not scored by this record.
Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.
commercial-privacy-dsar-tooling
Not scored by this record.
Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator
commercial-wcag-kiosk-accessibility
Not scored by this record.
POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator
commercial-dual-pricing-compliant
Not scored by this record.
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 4 values — 0 upheld, 4 downgraded, 0 upgraded. It separately resolved 40 previously unknown values. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| order-capture-split-merge | unknown (F) — "No public documentation located during the 2026-08-01 research pass." | resolve-to-yes | The placeholder was a marker for an unexamined cell, not a finding. Infor does publish a POS documentation library at docs.infor.com/pos. The User Guide 3.0.27 documents Separate Checks per guest, Check To combining, Move Check to an existing or new table, and Merge Check with Merge Seats and Append Seats styles; by-item splitting via moving or sharing an item between guests; Split Evenly at print; and split tender in 'any combination of payment options'. Merge behaviour after a partial payment is not addressed. source |
| order-capture-scheduled-orders | unknown (F) — placeholder rationale | resolve-to-yes | User Guide 'Scheduling an order': the check is sent automatically to the kitchen at the scheduled date and time, with a configurable number of minutes ahead of it, a configurable horizon limit, and a scheduled-orders dashboard. OrderNow adds a Future Orders switch with kitchen service window. Fire-time injection rather than print-on-receipt is explicit. source |
| menu-pricing-nested-modifiers | unknown (F) — placeholder rationale | resolve-to-partial | EM documents forced and non-forced modifiers and sequenced modifier windows, so the capability is present, but the touchscreen forced-modifier field list is exhaustive and offers only Repeat Times plus Allow Close — one count, not an independent min and max — and nothing in either EM guide establishes three-level nesting. source |
| menu-pricing-modifier-price-by-parent-size | unknown (F) — placeholder rationale | resolve-to-no | Both EM admin guides are field-by-field menu item references and between them enumerate every pricing mechanism: Price, Event Prices, Price Schedules, smart-combo discount, scale pricing, per-revenue-center Store Settings, and Roll up Price for summing forced modifiers. Modifiers are menu items with a single price. Item Size is a free-text Custom Field beside Vendor SKU, not a price axis. No matrix exists. source |
| menu-pricing-topping-quantity-tiers | unknown (F) — placeholder rationale | resolve-to-no | The documented quantity mechanisms are keying a quantity before tapping the item, and Repeat, which 'adds another order of the menu item' — precisely the duplication the claim distinguishes tiers from. No light/regular/extra/double tier and no per-tier multiplier appears in the EMv3 or EMv1 field references. source |
| payments-gift-cards | unknown (F) — placeholder rationale | resolve-to-partial | Gift cards exist as stored-value cards with load, real-time balance inquiry, offline transactions and a daily EM report, but every function routes through an external stored-value card provider tender — Infor even defers offline behaviour to that provider — so these are not first-party cards, and cross-location and OrderNow redemption scope is undocumented. source |
| payments-refund-void-controls | unknown (F) — placeholder rationale | resolve-to-yes | Per-function access levels NONE/NORMAL/FULL per job code, with a NONE-level function prompting for the user ID of a FULL-access employee, plus job-code gating on discounts and service charges. Exception reporting separates manager voids (requiring authorisation) from server voids, and Voided Down to $0 names the authorising manager. Immutability is not claimed by Infor and is not asserted here. source |
| delivery-dispatch-board | unknown (F) — placeholder rationale | resolve-to-no | The EM configuration reference contains no driver, dispatch, run or route object; the entire delivery surface is a per-order-type 'Mobile Delivery Method' of pickup, delivery or none, plus a Kiosk 'Deliver to Customer' completion message. The User Guide enumerates the POS screens and none is a dispatch board. source |
| delivery-zone-pricing | unknown (F) — placeholder rationale | resolve-to-no | There is no delivery zone object to price. EM enumerates the fee mechanisms — discounts and service charges assignable to family groups, items, job codes and order types, and tenders — none of which take an area, minimum or promise time, and no address capture or geocoding step exists. The OrderNow admin guide's eight configuration tasks include no delivery fee. source |
| digital-menu-single-source | unknown (F) — placeholder rationale | resolve-to-yes | EM states it configures the user interface of Infor POS, Infor POS Kiosk and Infor POS OrderNow, menu items for POS and Kiosk are added and configured in EM, kiosk images attach to the same item record, and channel reach is a set of check boxes (POS, Mobile, Kiosk) on the one record rather than a separate build. source |
| guest-loyalty-lifecycle-automation | unknown (F) — placeholder rationale | resolve-to-no | Enterprise Manager is the only administrative surface Infor publishes and its chapter list is complete — menu items, touchscreen, groups, tenders and discounts, employees, printing, reports. No campaign, marketing, email or SMS module and no trigger or audience object exists. POS loyalty is limited to card lookup, balance print and applying a provider-issued reward. source |
| labor-granular-rbac | unknown (F) — placeholder rationale | resolve-to-yes | Job codes are operator-created and carry four separate grant surfaces — POS Privileges per individual POS function, Enterprise Rights per EM feature, EM Reports per report, POS Reports per report — each with a per-revenue-center Store Settings override. This is per-action, per-role and per-location, not a fixed tier set. source |
| labor-manager-override-audit | unknown (F) — placeholder rationale | resolve-to-partial | Attribution at the moment of override is documented (a NONE-level function requires a FULL-access employee's user ID) and the Voided Down to $0 figure names the authorising manager, but there is no documented general override audit trail: the EM Event Log Report's contents are unstated, the per-record Record Details history is a click path with no described contents, and on-terminal POS reports cover only activity since the last close day. source |
| reporting-eod-closeout | unknown (F) — placeholder rationale | resolve-to-yes | EM publishes a Daily Close Day Report, a Cashout Report and a Consolidated CashOut Report EM; the POS has a Close Day action and a Print Close cash-out report per cash drawer. The User Guide's report glossary lists gross receipts, net and total revenue, tax collected and summary, discounts, void summary, tender and cash summary, tips declared/due/paid, and media loan and pickup in one document. source |
| reporting-pmix-modifier-level | unknown (F) — placeholder rationale | resolve-to-partial | Product mix exists (Product Sales Mix Export, Menu Item Report per revenue center, Day Parts Report) and reports run against a date range and a store group, so both required slices are present. But Infor publishes only report names and one-line descriptions: modifier-level breakout is inference from modifiers being stored as menu items, and neither gross nor net sales per item is stated — the POS-side description is a count only. source |
| multi-location-org-hierarchy | unknown (F) — placeholder rationale | resolve-to-yes | EM names company, market, site and revenue center as selectable levels, selecting a market or company selects all revenue centers beneath it, and a selection can be saved as a reusable named custom selection. Permissions carry per-revenue-center overrides and reports run against a Store Group. source |
| multi-location-central-menu-publish | unknown (F) — placeholder rationale | resolve-to-partial | Authoring once to a chosen set is the tool's default behaviour — all EM configuration applies to the selected revenue centers, chosen by revenue center, site, market, company or a saved selection. But no publish or version history is documented: Record Details is an undescribed click path and Data Sync Status gives only a last-sync timestamp, so what was pushed, by whom, and any rollback are absent. source |
| multi-location-price-zones | unknown (F) — placeholder rationale | resolve-to-partial | Per-location-group and per-daypart pricing both work off one item record (selection-scoped configuration, per-revenue-center Store Settings, Event Prices with priority ordering, Price Schedules by date and time). The channel axis is missing: EM exposes POS, Mobile and Kiosk enablement flags but no per-channel price. source |
| hardware-offline-mode | unknown (F) — placeholder rationale | resolve-to-partial | Infor documents a locally installed application, an in-store primary terminal that consolidates client-terminal data before uploading to the cloud, a three-state connectivity indicator that treats loss of cloud as distinct from loss of Internet, and offline credit-card authorization entry. It does not publish which functions degrade during an outage, and hands stored-value offline behaviour to the card provider — the second half of the claim is unmet. source |
| reliability-offline-order-entry | unknown (F) — placeholder rationale | resolve-to-partial | The primary/client on-premise architecture, the Backup RVC terminal role, the distinct yellow connectivity state and offline card authorization all evidence local-first operation, but Infor never states that order entry, kitchen routing and check printing continue when the Internet is lost; the red-light state is defined and its consequences left undescribed. source |
| reliability-printer-fallback | unknown (F) — placeholder rationale | resolve-to-no | The EM printing chapter is a complete enumeration of the printing model — logical printers, printer parameters, routing groups, routing-group-to-printer assignment, receipt properties, headers and trailers — and no object carries a backup, failover or alert setting. Infor's documented remedy is the manual, user-invoked Redirect Printer function (Restore, Redirect, Auto-Redirect all printers, Assign). source |
| order-capture-offline-order-entry | unknown (F) — "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | The placeholder marked an unexamined cell. An offline mode is documented but its scope is not. For: the Connectivity indicator is a three-state light (green = Internet and Infor POS cloud, yellow = Internet but not cloud, red = 'not connected to the Internet') shown on the sign-in screen, so the terminal runs disconnected; the architecture is local-first, with client terminals feeding a primary terminal that 'consolidates the data and uploads it to an Infor POS database'; the report glossary defines Offline credit as 'The total amount of credit card authorization requests entered in offline mode and waiting for authorization'; and 'Processing offline transactions for a stored-value card' states 'If the internet connection is down, you can process a stored-value card payment as an offline transaction and close the check.' Shortfall that caps it at partial: no guide in the 3.0.27 library publishes an offline scope — nothing states whether kitchen chits still route, whether configuration remains available, or how the queue is bounded, which is the explicit second half of the claim. source |
| kitchen-station-routing | unknown (F) — "No public documentation located during the 2026-08-01 research pass." | resolve-to-yes | The placeholder marked an unexamined cell; EMv3 ch.7 documents the routing model in full. A logical printer 'connect[s] with multiple routing groups to print receipts of specific menu items to different locations, such as multiple kitchens', with a worked two-kitchen example. Routing groups attach per menu item (Details > Printing > Routing Group, which 'overrides the routing group set on a family group level') and per family group, and 'Optionally, to assign a routing group to a specific revenue center, click Store Settings' gives the per-location override. Targets include KDS, not just printers: Printer Parameters carry Consolidate ('displayed as one line in a kitchen display system (KDS)') and Print Summary ('For a KDS... No / On Top / On Bottom'), items carry Kitchen Name, Priority ('Menu items with the same priority level are displayed together in the kitchen display') and Cook Time, and the Speed Of Service Report 'Describes bump times from the KDS'. All administered in Enterprise Manager without vendor involvement. Order-type routing is not documented; the claim is disjunctive and item/category/revenue-center are all satisfied, so this does not reduce the value. source |
| commercial-autorenew-terms-published | unknown (F) — "No public documentation located during the 2026-08-01 research pass." | resolve-to-yes | The placeholder marked an unexamined cell. Infor publishes the renewal term and the notice window in standard contract text that needs no login. On-Premises Software Terms and Conditions (November 2023, Infor's own DAM) §4b: twelve-month term that will 'renew for successive twelve month renewal periods, unless either party provides written notice... of non-renewal at least 90 days prior to the commencement of such renewal period', with a 30-day pre-notice obligation on Infor. The subscription equivalent, Infor's Subscription License and Services Agreement (US March 2019) §10a, sets 'successive one-year Renewal Terms' with the same 'at least ninety (90) days' non-renewal notice. Read in full, not from snippets. Caveats recorded in the claim note: initial term length lives on the Order Form, and the subscription agreement is published through reseller/procurement channels because infor.com/about/legal carries no contract library and every candidate terms index on infor.com 404s. source |
| commercial-hardware-purchase-outright | unknown (F) — "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | The placeholder marked an unexamined cell. Infor operates its own hardware storefront at pos.infor.com listing terminals, KDS screens and bump bars, thermal and impact printers, cash drawers, payment devices and monitors as purchasable goods, with no lease, rental or financing programme anywhere on the site — so the 'no mandatory multi-year lease' half holds. Named shortfall capping this at partial: no SKU carries a price. The current T3 terminal shows 'Coming soon!' and 'Current clients please contact your sales representative for pricing and availability', the end-of-life T2 repeats the contact-sales instruction, and no page has an add-to-cart. The User Guide adds that 'The available hardware for your Infor POS terminal are based on your subscription agreement with your Infor POS representative.' The 'published price' half of the claim therefore fails. source |
| payments-emv-nfc | unknown (F) — "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | The placeholder marked an unexamined cell. Infor's storefront payment-device collection is four PAX Android units described collectively as supporting 'EMV and contactless transactions', and the A35 page specifies 'tap, chip, and swipe card payments with PIN entry', so EMV chip plus NFC contactless holds for the whole first-party lineup at grade C. Capped at partial because the claim's wallet clause is unestablished: Apple Pay and Google Pay are named nowhere on the store or in the five-guide documentation library, whose only EMV trace is the 'EMV Manual' tender check box, and the devices ship unconfigured pending payment-processor setup. source |
| delivery-driver-roster | unknown (F) — "No public documentation located during the 2026-08-01 research pass." | resolve-to-no | The placeholder marked an unexamined cell. The EM guide's Employee management chapter enumerates every people object — employees, job codes, job assignments, payment information, clock time records, edit history, employee classes — and no driver role, assignment state or run object exists among them. 'Driver' appears only as the tender COM-port Driver Param, 'delivery' only in the Mobile Delivery Method pickup/delivery/none field, the User Guide contains neither word, and no driver or run report is in either report catalogue. Same complete-enumeration basis as the settled delivery-dispatch-board no. source |
| guest-loyalty-accrual-models | unknown (F) — "No public documentation located during the 2026-08-01 research pass." | resolve-to-no | The placeholder marked an unexamined cell. The docs establish that loyalty is a third-party stored-value provider integration — every interaction goes through 'the function button of the loyalty card provider' and the balance lives with the provider — which is exactly the bolt-on the claim excludes, and the complete eight-chapter EM configuration reference contains no accrual configuration at all: no points-per-dollar, no visit/punch counter, no spend tier. The only points fields in EM are campus CashEQ meal-plan settings. source |
| labor-clock-in-at-pos | unknown (F) — "No public documentation located during the 2026-08-01 research pass." | resolve-to-yes | The placeholder marked an unexamined cell. The User Guide documents a Clock In / Out button on the sign-in screen 'for tracking labor hours' with a keyed user ID and confirmation, sign-in by MSR user card swipe as the alternative, Close Day clocking out all employees, and Clock times / Clock in Status reporting; EM ch.6 adds manager-side clock time record search, modify and add. No separate time-clock hardware is required or mentioned. source |
| hardware-os-platforms | unknown (F) — "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | The placeholder marked an unexamined cell. The storefront publishes full device specs for the T3 and T2 terminals and names an OS for the POP Server (Windows 10 IoT 2021) and the PAX payment devices (Android 10/11), satisfying the device-spec limb at grade C. Capped at partial because the client OS of Infor POS itself is never named anywhere — no guide in the five-guide library names any operating system, no minimum versions or supported-device matrix exist, and the User Guide's Hardware topic defers hardware scope to 'your subscription agreement with your Infor POS representative'. source |
| hardware-kds | unknown (F) — "No public documentation located during the 2026-08-01 research pass." | resolve-to-yes | The placeholder marked an unexamined cell. All four limbs of the claim are evidenced: 'Infor KDS' is named in the User Guide (Bump Order 'Bumps the order off Infor KDS') and Infor sells KDS hardware and bump bars on its own storefront (first-party, not integration-only); bump-bar input via the storefront's Bump Bars collection and the Speed Of Service Report's 'bump times from the KDS'; station routing via EM routing groups with KDS printer parameters, Kitchen Name, Cook Time and Priority; course/fire timing via the Coursing chapter's Fire Course / Next Course / Select Course workflow. The absence of a dedicated KDS admin guide is recorded but scored in the neighbouring KDS cells, not this one. source |
| kitchen-bump-bar-hardware | unknown — bound to the retired Infor POS 3.0.27 library | resolve-to-partial | Re-fetched all four cited URLs myself with a browser UA and confirmed every quoted byte is in the served body - real 424,610 and 414,577 byte Shopify pages and 43,439 and 16,859 byte Oxygen WebHelp topics, not challenge interstitials - and pulled both products.json objects, which gave part numbers and prices the rendered HTML buries (USB FP-900580-104/-112 at $230/$245; serial FP-700580-009 at $245). The proposal is honest and its own caveats are accurate, but it asks for yes on a two-conjunct claim where only the first conjunct is clean. Infor demonstrably sells Infor-branded bump bars that name Infor POS, so this must not be downgraded to unknown - that would assert we do not know something we do know. What is missing is the support relation the claim actually turns on: both bodies hedge to 'select compatible' / 'other supported' KDS without naming one, and the entire current 2026.08 library - 374 topics, re-verified by my own tokenised controls, not inherited - contains zero occurrences of 'bump bar' and publishes no key mapping, pairing or configuration. A buyer can buy the hardware but cannot find from any Infor source that the KDS accepts it, or which KDS models do. Present but materially limited is partial by the state definitions. The most useful thing I found is adverse and is now in the note: 'keypad' is not a safe absence control here, because it returns 71 hits in 43 topics and all 71 are on-screen numeric keypads, the opposite of the claim, so a control-driven yes on that word would have been fabricated; the mirror control 'touchscreen' at 96 hits in 17 topics bounds the bump-bar zero as a real absence in a corpus that talks about input constantly. Grade stays C rather than D: a Shopify listing carrying SKU, price, interface spec and included contents is a first-party product-catalogue page in the same family as a pricing page, not a press release or landing page, and D would understate it. Verdict label is resolve-to-partial because the prior value was unknown and was never asserted; final_value is partial. |
| reliability-offline-kds-printing | unknown — bound to the retired Infor POS 3.0.27 library | downgrade-to-unknown | Proposal rejected. The cited 'Configuring backup revenue centers' topic is real and its quotes are in the served bytes (live re-fetch 200, 12159 bytes, identical to the corpus copy), but it documents PEER-TERMINAL FAILOVER, not offline operation: Infor's own example is 'the primary terminal loses power', and the overview topic shows the primary terminal is the in-store master that clients post to and that uploads to the cloud, so its failure is a LAN-local hardware event. The 'Connectivity indicator' topic enumerates three states and attaches no behaviour to the yellow (cloud down) or red (no internet) state, so it cannot carry the claim. The proposal's own shortfall paragraph concedes no topic says kitchen chits or the KDS survive an internet or LAN outage, which makes its 'partial' shortfall every conjunct of a single-conjunct claim and therefore self-refuting. Tokenised controls over the 374-topic 2026.08 corpus found 19 'offline' hits, all payments or terminal health; 'outage', 'failover', 'queue', 'spool', 'store-and-forward', 'degraded', 'reconnect', 'redundant', 'unreachable' are zero on a corpus whose positive controls pass (Infor 661, menu 925, printer 63, kitchen 46). Cell stays unknown; the url is refreshed from the superseded 3.0.27 library to the live 2026.08 library default (200, 34533 bytes) so the note is bound to the corpus actually read. |
| extensibility-public-api-docs | unknown — bound to the retired Infor POS 3.0.27 library | resolve-to-no | Resolution upheld in value, downgraded in grade, and two of the proposal's supporting statements are false. WHAT I CONFIRMED MYSELF: the sitemap really does bound the POS to four locs across two versions and two libraries; /technical/ really is a Concierge SAML wall at both versions, and I added the fabricated-path control the proposal lacked (a fabricated library path returns the 661-byte soft-404 redirect, a fabricated topic returns 404, only /technical/ returns the 1,840-byte 'Access rights validated' form, so the gate is discriminated from the catch-all); Wayback CDX over docs.infor.com/pos/ by PREFIX match (239 URLs, nine library slugs, 2019-2026) holds no technical, api or developer capture. WHAT THE PROPOSAL GOT WRONG, TWICE. (a) 'developer.infor.com is a Theneo-hosted shell... any path under it resolves to /no-project-found... No public Infor POS project exists there' is a dead-signpost inference from one probe of /asset-manifest.json. developer.infor.com publishes 2,868 anonymously readable API reference projects: the catalogue page's own inline script names the registry api.theneo.io/project/641da466da19fdcb138d4fd2/published, and Infor's own Developer Portal Overview Guide says the catalogue exists precisely so people can read API docs 'outside of a paywall or login'. The conclusion survives, and is now much better bounded, because that catalogue's 37-product tag taxonomy contains no hospitality or POS entry and searches return zero for point of sale, hospitality, restaurant, smartseries, ordernow, kitchen, menu, tender and revenue center against live positive controls (ion 304, m3 69, order 23). But the proposal's fourth numbered point, on which its grade A partly rested, was not measured. (b) 'the 2026.08 PDFs are a poisoned corpus - a custom-encoded font makes Infor extract as ) ! * - and EVERY control word returned ZERO' is an artefact of the proposal's own PDF reader, not of the files. pdftotext extracts the same four PDFs cleanly (299,267 characters, Infor 671, POS 243, menu 329), and the devportal PDF extracts cleanly too. Rerun over the PDFs, the API-vocabulary zeros are identical to the HTML ones, so the record gains a genuine second instrument that the proposal discarded. I also re-ran the corpus controls tokenised in three modes and found poison the proposal did not report: 'pos' in Infor's public API catalogue is 52 M3 ERP programs (POS350MI is 'Project invoice interface'); 'integration' in the POS library is 4 hits all reading 'card integration branding'; 'JSON' is Json.NET in a licence list; stem 'rest' reads 18 documents against 1 whole-word; XML, HTTP and URL match all 374 documents in raw bytes because of Oxygen WebHelp furniture. GRADE: A is not available. The atlas grades an API reference, spec, filing or source as A; the cited artefact is a product-documentation library index plus an HTTP gate response, which is B, and the argument's second leg is an absence bounded to a library nobody outside Infor can read. B with the manifest, the gate and the controls all published. |
| inventory-recipe-bom-costing | unknown — bound to the retired Infor POS 3.0.27 library | resolve-to-no | Upheld, with the proposer's enumeration corrected. I verified the key quote in the raw served bytes myself: at lines 136-140 of em3admin__ivk1568094351637.html the Cost quote is a genuine <dt>Cost</dt> / <dd>Specify the cost of the menu item. This information is used in the <span>Theoretical Cost Report</span>.</dd> pairing, one definition-list item, with only a bolding span inside the sentence - it is not manufactured contiguity, and no quoted text came from an HTML comment. But the proposer called its field list "the complete field enumeration" and listed 11 fields when the topic has SIXTEEN <dt> elements: it silently dropped Restricted, Combo Parent, Header Item, Cover and Active. I read all five and none is a component or ingredient field (Combo Parent is a flex-combo sales bundle, "You can add flex combo menu items in any order in a check and have scalable modifier options" - a bundle of SOLD items priced as a promotion, not a costed bill of materials), so the verdict survives, but the note has been rewritten to enumerate all sixteen. I re-ran every control tokenised in both HTML and PDF: recipe, recipes, ingredient, ingredients, bill of material(s), sub-recipe, sub-item, plate cost, yield, cost of goods, COGS and portions all read 0 in BOTH instruments, against positive controls that read 242/661 and 671. The proposer's positive-control figures (Infor 374, menu 374) were taken over raw HTML including markup and chrome; mine are over tag-stripped prose and are the honest ones. Grade B is correct and grade A is unavailable: the /technical/ library is a SAML wall. |
| inventory-unit-conversion-yields | unknown — bound to the retired Infor POS 3.0.27 library | resolve-to-no | Upheld, with one surface the proposer missed added and dismissed on its merits. Quotes verified in raw bytes. Controls re-run tokenised in both instruments: unit of measure 0, UOM 0, conversion 0, convert 0, yield 0, yields 0, variance 0, on hand 0, par level 0, par 0, reorder 0, requisition 0, supplier(s) 0, order guide 0, shrinkage 0, invoice 0, ounce 0, pound 0, gram 0, litre 0, liter 0 - all zero in HTML AND in the four PDFs. The proposer missed kadmin/wjm1579077106811 "Configuring the weight unit of an integrated scale for weighing menu items" ("Tap Scale Weight Unit and tap a weight unit option. This enables the menu items with the selected weight unit option to be added to an order"), which is the only place the product names a unit of measure at all. I read it: it selects the unit an integrated scale reports at the point of sale so a weighed item can be PRICED, and it is a single unit with no second unit and no factor. That is a sale-side weighing feature, not a purchase-to-recipe-to-count conversion table, so it does not disturb the verdict - but a note that does not name it is incomplete and it has been added. I also read the two remaining "unit(s)" hits (a modifier display field, and "Count List opens number of remaining units of a menu item available for an order") and the CPG checkbox on the same Custom Fields page; none carries a conversion factor. The prior note was bound to a retired 3.0.27 PDF and additionally asserted that Infor PDFs extract as zero regardless of presence; that assertion is FALSE and has been removed - the 2026.08 PDFs extract cleanly and now serve as the cross-check. |
| inventory-count-modes | unknown — bound to the retired Infor POS 3.0.27 library | resolve-to-no | Upheld, and this is the strongest of the three zeros. I verified every quote in the raw bytes: the countdown prose is a real <p> at line 113 of user__owb1561967667029.html, the colour legend is a real <ul> of <li> elements (not a welded table), the Remove Countdown / Daily Default / Carryover Remainder options are three real <li> elements at lines 129-131, the Count List sentence is a real <p> at line 113 of user__mya1561968421985.html, and the vendor workaround is a real <note> at line 118 of user__xuj1555619811594.html. Controls re-run tokenised in both instruments: counting 0, cycle 0, cycle count 0, spot count 0, physical inventory 0, stocktake 0, stock take 0, count sheet 0, recount 0, audit 0, variance 0, shrinkage 0, on hand 0, usage 0, depletion 0, par level 0, requisition 0 - zero in HTML and zero in all four PDFs. "adjustment" reads 1 and is a tender adjustment. The decisive evidence is not the zeros but the documented workaround, which is the classic shape of a positive absence: on wasting an item Infor tells the operator "A wasted item is not tracked in gross sales reports. We recommend creating a new check named Waste and moving wasted items there for record purposes." A vendor that advises opening a dummy check to keep a record of shrink does not ship count sessions with variance history. |
| reporting-realtime-dashboard | unknown — bound to the retired Infor POS 3.0.27 library | resolve-to-no | PROPOSAL REJECTED. The proposer overrode a prior unknown with partial while conceding, in its own text, that there is no sales dashboard object in the product and that no document states a latency. Asked whether off-premise browser sales reporting satisfies a conjunct of the claim, my answer is that it satisfies only the browser half of the ACCESS conjunct - a delivery medium - and nothing of the capability the claim names. Working through the claim: (a) "live sales dashboard" - I read the EM Reports management table of contents whole (18 entries, em3admin/default.html) and the standard-report catalogue whole (35 rows, teb1570776984357.html) and tokenised "dashboard" across both instruments: 6 HTML topics, 10 hits, and the referents are exhaustively Terminal Health (device telemetry), Schedule Dashboard (a list of report schedules), a dashboard of scheduled ORDERS on the terminal, and the Stripe merchant Dashboard. There is no sales dashboard object; sales reach the operator as reports. That is an enumerated absence, not an unexamined one. (b) "within minutes of the sale" - "live" reads 0 in tag-stripped prose (the proposer's "live 4" was raw-HTML markup, not text), latency 0, realtime 0, immediately 0, instantly 0, today 0, and the only "real time" string in 374 topics is the Terminal Health telemetry homonym. Worse, and the proposer missed this: the standard-report catalogue opens with a report type "Data sync" whose entry is "Data Sync Status - Describes the time and date when the revenue center was last synced with Infor POS Enterprise Manager data", with its own export topic. EM is fed from the revenue centers by a sync whose cadence is nowhere published and which needs a status report to tell an operator when it last ran. That moves this conjunct from unevidenced to adverse-leaning. (c) "and a mobile app off-premise" - I read all 30 "mobile" hits: every one is guest-facing (Mobile Name on the menu item, mobile ordering enable/disable, mobile wallets, the guest's mobile phone number for SMS, the OrderNow Mobile App Link) or WebHelp feedback chrome ("This page is difficult to use on my mobile device"). manager app 0, iOS 0, Android 0, app 4 and all four are the guest OrderNow app. Across a complete four-guide library there is no manager or reporting application. That is positive evidence of absence. So one conjunct is positively false, one is unevidenced and leaning adverse, and the third is half-met. I also found, and record, the one piece of adverse evidence the proposer did not: the catalogue does carry a standard report named "Executive Desktop - Describes gross sales and the number of closed checks and guests", and EMX dynamic reports do reach a 15-minute grouping. Those are real and are named in the note so the reader is not misled - but a named report in a browser console is not a live dashboard on a phone, and scoring this partial would publish the opposite of what the documentation supports. |
| digital-first-party-web | unknown — bound to the retired Infor POS 3.0.27 library | resolve-to-partial | Partial upheld, but the reasoning is repaired. The proposer conceded that "commission" tokenises to zero and then inferred from the operator's own processor accounts that there is probably no rake; I agree that is inference and it is not scored. It does not, however, sink the cell to unknown, because the commission-free conjunct is not the head of the claim - it is a qualifier on a channel, and the channel itself is documented at grade B in both instruments. What I verified myself in raw bytes: the store URL topic is a real task list (line 112-117 of posonapag__yph1594970463711.html), the QR signage Branded Link / Display Branded Link signage / Primary Branding Color steps are real <li> elements, and the Stripe redirect sentence is a real <li>. I re-derived the OrderNow Admin Portal guide from titles.txt rather than inheriting the proposer's count: it is a CLOSED list of 15 topics (About, overview, Accessing, Configuration tasks, store URL, QR code signage, future orders and special instructions, custom logo for payment methods and card integration branding, tips, Stripe, Elavon, FreedomPay, Shift4, Kiosk translations, cover) and it contains no custom-domain, DNS, CNAME, white-label or site-theme topic. Controls tokenised in BOTH instruments: custom domain 0, DNS 0, CNAME 0, subdomain 0, white label 0, white-label 0, marketplace 0, rake 0, commission 0, commissions 0, fee 0, fees 0, per-order 0, merchant of record 0. The "domain" trap is the one that would have flipped this: it reads 374 of 374 in HTML and 0 in all four PDFs, because it is the WebHelp template's isKnownServer(domain) script - the PDF instrument is what proves the prose figure is zero. One correction against the proposer in the OTHER direction: the operator connecting their own Elavon, FreedomPay, Shift4 and Stripe merchant accounts is not merely an inference, it is a documented grade-B fact about where the money lands, and it is worth recording as such even though no first-party source states the commercial model. Partial with two named shortfalls is the honest value; unknown would discard a documented ordering channel. |
| digital-account-saved-payment | unknown — bound to the retired Infor POS 3.0.27 library | resolve-to-no | Rebuilt the corpus from scratch and reproduced the proposer's closure exactly: 28 .js files, 1,991,970 bytes, closed after three rounds, and additionally bound to the publisher's own /ngsw.json hash table, whose 28 .js entries are the identical set. Probed .js.map on main, polyfills and two chunks plus a fabricated sibling control: all 404, no sourceMappingURL anywhere, so no better corpus was missed. Found and closed one hole the proposer left open, the five /assets/i18n/*.json files in ngsw.json, which turn out to be ngx-translate scaffolding stubs and carry no UI labels. Re-ran every control tokenised and reproduced every figure; all positive controls non-zero. Confirmed first-party multi-store status from the :store_id route root, the production environment literal, the webmanifest and the pk_live Stripe key, so this is not one customer's tenant. Grade A challenged and SUSTAINED: the source type is vendor production code, which the atlas grades A in 150 existing cells including no verdicts; the channel enumeration is closed by Infor's own brochure ('an app download is not required') and by the absence of any guest ordering app among the 27 App Store titles published by Infor (US), LLC, which removes the across-first-party-channels scope objection; and the file set is manifest-bound. Substantive challenge also answered: the localStorage autofill finding alone would NOT refute a server-side card on file, so the note was rewritten to rest the verdict on the absence of any save-or-reuse path in the shipped client instead, with customerId/setupIntent/ephemeralKey/maskedPan/lastFour all zero and a fresh processor element mounted every order. Added new poison the proposer missed: Bootstrap's .card layout class inflating card to 93, and Amplify's requireLowercase/requireUppercase/requireNumbers/requireSpecialCharacters password-policy flags which read like an account signup surface. Removed the false assertion that Infor PDFs are unreadable due to custom fonts; there is in fact no PDF rendition of this generation at all. |
| guest-loyalty-unified-profile | unknown — bound to the retired Infor POS 3.0.27 library | resolve-to-no | Sustained. Re-derived the doc manifest from docs.infor.com/sitemap.xml and the useradminlib sitemap and reproduced 374 topics in four folders. Independently rebuilt the OrderNow closure and reproduced every client control including loyalty 0, points 0, rewards 0, member 0 with all positive controls non-zero. One figure the proposal omitted and the verifier ran: loyalty scores 87 in the doc corpus, not 0; the 15 topics carrying it were enumerated by title and the substantive ones read, and every one is the third-party provider's card, which strengthens rather than weakens the verdict, so it is now published in the note instead of being left out. Confirmed profile 1, dedup 0, unified 0, customer 16 across 7 topics, merge 9 with 7 in 'Merging checks'. Grade B is correct and was not raised: the load-bearing instrument is a vendor administration guide. Removed the false custom-font PDF assertion. |
| kitchen-expo-consolidation | unknown — bound to the retired Infor POS 3.0.27 library | downgrade-to-unknown | Correction accepted. Verified the load-bearing corrected fact independently: docs.infor.com/sitemap.xml lists exactly four POS libraries and the 2026.08 useradminlib sitemap resolves to 375 hrefs, being 374 topic files across user 148, em3admin 146, kadmin 65 and posonapag 15 plus one shell, so FOUR guides and 374 topics is correct and the old note's 'five guides' was false of the current library. Re-ran the controls over the 374 topics and reproduced expo 1 in user/gnu1562573286176.html, bump 3, KDS 13 across five topics, station 0, expeditor 0, and the corpus controls. Re-probed the 3.0.27 default.html at 200, 25,937 bytes, so the old citation is archived rather than dead. Value unchanged at unknown. Removed the false custom-font PDF assertion and replaced it with what is actually true, that this generation publishes no PDF rendition at all. |
| extensibility-oauth-partner-apps | unknown — bound to the retired Infor POS 3.0.27 library | downgrade-to-unknown | Correction accepted. Verified both corrected facts independently. API does occur exactly 3 times on word boundaries across the 374 topics, two hits in kadmin/psf1575018874987.html and one in user/gog1555619772856.html, and OAuth 0 and token 0 reproduce. The OrderNow client does carry the amazoncognito /oauth2/authorize URL: grepped the rebuilt 28-file closure and found ssoBaseLoginUrl and ssoBaseLogoutUrl pointing at ordernow-hpo-inforcloudsuite.auth.us-west-2.amazoncognito.com with client_id 1tv4r7h57qctv0jli4ed2bo5na, used with identity_provider federation, which is guest SSO and not partner-app authorisation. Re-probed api.vivonet.com: /status 200 with the stated JSON body, and /swagger.json, /openapi.json, /v3/api-docs, /robots.txt and a nonsense path all honest JSON 404s, so the not-a-soft-200 finding holds. Re-confirmed the /technical/ 302 to the SAML form. Value unchanged at unknown. Added the Amplify password-policy flags to the published poison, since requireLowercase and its siblings read like an account signup surface. Removed the false custom-font PDF assertion. |
| extensibility-webhooks-push | unknown — bound to the retired Infor POS 3.0.27 library | downgrade-to-unknown | Correction accepted. Verified the corrected count of four guides and 374 topics against the publisher's own sitemaps, and re-ran the doc controls, reproducing webhook 0, callback 0, endpoint 0, token 0, OAuth 0, event 52 across 7 topics, subscription 13, push 2 in em3admin/auh1653547580332.html, with all corpus controls passing. Rebuilt the OrderNow closure independently and reproduced webhook 0 alongside the WebSocket 1 and setInterval 11 poison. Re-probed api.vivonet.com and confirmed the 200 on /status and honest JSON 404s elsewhere. Value unchanged at unknown, which is the right call: the readable library is a user-and-administration library and its silence about an integration contract is not positive evidence of absence. Removed the false custom-font PDF assertion. |
Sources
Every URL this record cites. 23 in total.
- https://www.infor.com/industries/hospitality
- https://docs.infor.com/pos/3.0.27/en-us/useradminlib/default.html
- https://docs.infor.com/pos/3.0.27/en-us/useradminlib/user/pos_3.0.27_user__en-us.pdf
- https://docs.infor.com/pos/3.0.27/en-us/useradminlib/em3admin/pos_3.0.27_em3admin__en-us.pdf
- https://docs.infor.com/pos/3.0.27/en-us/useradminlib/em1admin/pos_3.0.27_em1admin__en-us.pdf
- https://docs.infor.com/pos/3.0.27/en-us/useradminlib/posonapag/pos_3.0.27_posonapag__en-us.pdf
- https://docs.infor.com/pos/3.0.27/en-us/useradminlib/kadmin/pos_3.0.27_kadmin__en-us.pdf
- https://www.infor.com/products/smartseries
- https://dam.infor.com/api/public/content/a43a38c17c5f4338986840a9f870af00?v=4fab71ce
- https://www.dlt.com/sites/default/files/documents/2021-03/Infor-SaaS-EULA.pdf
- https://www.infor.com/about/legal
- https://pos.infor.com/
- https://pos.infor.com/products/t3-pos-infor-terminal
- https://pos.infor.com/products/infor-pos-t2-terminal
- https://www.infor.com/products/point-of-sale
- https://pos.infor.com/collections/payment-devices
- https://pos.infor.com/products/pax-a35-credit-card-pin-pad-android-touchscreen-payment-terminal
- https://pos.infor.com/products/point-of-purchase-pop-server
- https://pos.infor.com/collections/kitchen-display-system
- https://docs.infor.com/sitemap.xml
- https://docs.infor.com/pos/2026.08/en-us/useradminlib/sitemap.html
- https://docs.infor.com/pos/2026.05/en-us/useradminlib/sitemap.html
- https://docs.infor.com/pos/2026.08/en-us/technical/default.html