Adyen

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

menu-pricing-nested-modifiers

UPHELD, now cited, and settled on the schema rather than on a keyword count. Adyen holds no menu record of any kind. The Terminal API's 163 published schemas contain no item, basket, category or modifier object: a PaymentRequest carries SaleData (OperatorID, OperatorLanguage, ShiftNumber, SaleTransactionID, SaleReferenceID, SaleTerminalData, TokenRequestedType, CustomerOrderID, CustomerOrderReq, SaleToPOIData, SaleToAcquirerData, SaleToIssuerData) and PaymentTransaction.AmountsReq, whose whole field set is Currency, RequestedAmount, CashBackAmount, TipAmount, PaidAmount, MinimumAmountToDeliver, MaximumCashBackAmount and MinimumSplitAmount. Amounts, never items. The one place item detail reaches an Adyen terminal is a rendering payload, not a data model: to show a virtual receipt you 'gather all content in an XML file, convert this file to a Base64 string, and pass that string in a display request', where '<lines>: contains line items that represent the goods that the shopper is purchasing. Each line item can have a count, description, and amount.' The vendor's own instruction is to 'populate an XML input file with line items and total amounts from your POS app'. Nothing is stored, nothing is identified, nothing is reportable -- Adyen receives a picture of the check, and receiving is not authoring. Adyen's only structured line-item object is Checkout API LineItem, and it is closed -- additionalProperties: false over amountExcludingTax, amountIncludingTax, brand, color, description, id, imageUrl, itemCategory, manufacturer, marketplaceSellerId, productUrl, quantity, receiverEmail, returnShippingCompany, returnTrackingNumber, returnTrackingUri, shippingCompany, shippingMethod, size, sku, taxAmount, taxPercentage, trackingNumber, trackingUri, upc. It is a flat retail line with no parent reference, no child collection and no group construct, so nesting to three levels is not merely undocumented but excluded by the published schema. The word 'modifier' occurs 190 times across 50 documents and all 190 were read: every one is the Android Jetpack Compose UI sense inside a payment-method component page, never a menu modifier. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/api-explorer/terminal-api/latest/post/payment · retrieved 2026-09-08

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

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

UPHELD, now cited. There is no modifier to price and no parent to price it against. Adyen holds no menu record of any kind. The Terminal API's 163 published schemas contain no item, basket, category or modifier object: a PaymentRequest carries SaleData (OperatorID, OperatorLanguage, ShiftNumber, SaleTransactionID, SaleReferenceID, SaleTerminalData, TokenRequestedType, CustomerOrderID, CustomerOrderReq, SaleToPOIData, SaleToAcquirerData, SaleToIssuerData) and PaymentTransaction.AmountsReq, whose whole field set is Currency, RequestedAmount, CashBackAmount, TipAmount, PaidAmount, MinimumAmountToDeliver, MaximumCashBackAmount and MinimumSplitAmount. Amounts, never items. The nearest thing Adyen publishes to a size dimension is Checkout LineItem.size, documented in full as 'Size of the item.' -- a free-text retail attribute added in v70 that carries no price of its own and no relationship to any other line. With additionalProperties: false on LineItem there is no matrix construct anywhere in the schema, and with no modifier object there is nothing for a matrix to key. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/api-explorer/terminal-api/latest/post/payment · retrieved 2026-09-08

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

menu-pricing-fractional-placement

Not scored by this record.

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

menu-pricing-half-and-half-rule

Not scored by this record.

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

menu-pricing-topping-quantity-tiers

UPHELD, now cited. Adyen holds no menu record of any kind. The Terminal API's 163 published schemas contain no item, basket, category or modifier object: a PaymentRequest carries SaleData (OperatorID, OperatorLanguage, ShiftNumber, SaleTransactionID, SaleReferenceID, SaleTerminalData, TokenRequestedType, CustomerOrderID, CustomerOrderReq, SaleToPOIData, SaleToAcquirerData, SaleToIssuerData) and PaymentTransaction.AmountsReq, whose whole field set is Currency, RequestedAmount, CashBackAmount, TipAmount, PaidAmount, MinimumAmountToDeliver, MaximumCashBackAmount and MinimumSplitAmount. Amounts, never items. The only quantity Adyen models is Checkout LineItem.quantity, documented as 'Number of items.' and typed as a plain int64, with no multiplier, tier or step field beside it on a schema that is closed by additionalProperties: false. The virtual-receipt XML line has a 'count' for the same purpose. A light/regular/extra tier with a price multiplier has no representation in any published Adyen object. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/api-explorer/terminal-api/latest/post/payment · retrieved 2026-09-08

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

menu-pricing-size-style-matrix

Not scored by this record.

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

menu-pricing-included-allowance

Not scored by this record.

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

menu-pricing-combos

Not scored by this record.

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

menu-pricing-upsell-prompts

Not scored by this record.

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

menu-pricing-86-propagation

Not scored by this record.

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

menu-pricing-countdown-auto-86

Not scored by this record.

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

menu-pricing-dayparting

Not scored by this record.

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

menu-pricing-channel-price-books

Not scored by this record.

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

menu-pricing-dual-pricing

Not scored by this record.

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

menu-pricing-versioning-effective-dates

Not scored by this record.

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

menu-pricing-franchise-hierarchy

Not scored by this record.

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

menu-pricing-allergen-nutrition

Not scored by this record.

Menu items and modifiers can be linked to recipes/bills of materials so that a sale depletes theoretical inventory and yields item-level theoretical food cost. differentiator

menu-pricing-recipe-linkage

Not scored by this record.

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

menu-pricing-3p-menu-push

Not scored by this record.

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

menu-pricing-dynamic-pricing

Not scored by this record.

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

Certified PCI-compliant first-party terminals across hospitality and food service supporting EMV chip and NFC contactless including Apple Pay and Google Pay. https://docs.adyen.com/point-of-sale/ · retrieved 2026-08-01

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

payments-softpos-tap-to-pay

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

Terminal API supports gift card activate, payment, balance check, load funds, refund and deactivate; issuance and cross-location program management typically ride on a gift-card partner. https://docs.adyen.com/point-of-sale/ · retrieved 2026-08-01

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

Both halves of the control exist and neither is joined to an identity, so this is a partial rather than the unknown it was. Authorization is real on both sides. In the Customer Area the actions are separately grantable roles, not a manager tier: a Refund payments role whose whole permission is 'The user can refund a payment.', a Cancel payments role reading 'The user can cancel a payment.', and a Capture payments role reading 'The user can capture a payment.', with Merchant manage payments and Merchant Fix POS Payments as the combined variants. At the terminal, Management API's terminal settings carry a dedicated refund passcode -- refundPin, 'The passcode for referenced and unreferenced refunds on standalone terminals', maximum length 6 -- alongside adminMenuPin ('The passcode for the Admin menu and the Settings menu') and txMenuPin ('The passcode for the Transactions menu'). What is missing is the approver. A six-digit terminal passcode is a per-terminal shared secret that attributes nothing to a person, and Adyen publishes no immutable audit log of payment modifications: 'audit log' occurs in 3 of 2,535 documents and all three are the Balance Platform account-holder page, while the two audit-trail roles it does define are scoped to capabilities and to transfer schedules, not to refunds. The register-side actions the claim also names -- comps, discounts and no-sales -- have no representation at all, because Adyen holds no check to discount. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters, plus 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. https://docs.adyen.com/account/user-roles · retrieved 2026-09-08

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.

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

UPHELD, now cited, and the zero-hit is about the word's sense rather than its count. Every one of the 65 occurrences of 'driver' across the 2,535-document corpus was read and classified: 47 are a driver's licence in identity verification, 6 a motorist in Adyen's parking-garage card-acquisition example, 5 a software or hardware device driver (the Adyen POS Library 'acts as a hardware driver'; a Verifone NFC driver; a Wi-Fi driver; two Cegid plugin drivers), 5 figurative ('four key drivers', 'a strong driver for brand loyalty'), and 2 the food-delivery sense -- both in one Adyen for Platforms worked example, where Adyen is describing its own customer rather than its own product: 'you have a large food delivery company called Food delivery, where your users are delivery drivers and restaurants', for which Adyen supplies business accounts and payouts. Paying a courier is not rostering one: there is no driver entity, no clock-in or assignment state, and no per-driver run history in any published Adyen API or report. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/business-accounts/account-structure-resources/platform-account-structure · retrieved 2026-09-08

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

delivery-dispatch-board

UPHELD, now cited. 'dispatch board' occurs zero times, and 'dispatch' occurs exactly 3 times in 2,535 documents -- one sentence about JavaScript events, 'you must listen to the events they dispatch', repeated on the hosted-onboarding components page across Issuing, Marketplaces and Platforms. Adyen ships no operator screen of any kind beyond the Customer Area, whose documented point-of-sale surface is terminal and transaction management -- 'View transactions for a terminal, store, or region' -- and there is no order object to leave undispatched, no driver entity to show availability for, and no run to batch. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/point-of-sale · retrieved 2026-09-08

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

UPHELD, now cited. 'delivery zone' occurs zero times in 53,523,717 characters. 'delivery' occurs 35 times across 14 of the 327 point-of-sale pages, and all 35 were read: they are shipping a terminal to a merchant and tracking that shipment ('order terminals and accessories for delivery to a location of your choice'), Android Play Feature Delivery, USB Power Delivery adapters, the guaranteed payment-response delivery feature, one pre-authorisation example mentioning a web shop's delivery time, and one naming of delivery as a vertical Adyen's terminals are built for ('designed for hospitality, retail, food, events, lifestyle, delivery, and more'). That last one is the strongest thing in the vendor's favour and it is a hardware statement, not a fulfilment feature. Adyen holds no customer address for order fulfilment, no order minimum and no promise time; the only per-location money rules it does publish are surcharge configuration and payment-method availability, neither of which is a delivery fee. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/point-of-sale · retrieved 2026-09-08

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.

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

delivery-menu-push

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.

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

UPHELD, now cited, and the vendor rules itself out in its own words. Adyen's hosted consumer surface is Pay by Link, which it describes as 'Accept payments using an Adyen payment page' and whose use cases it lists as 'Adding a payment option to an invoice', 'Asking a shopper to pay after they visit your product showroom', and 'Letting a shopper pay after interacting with them through chat, email, or social media.' The page then states plainly: 'Do not use Pay by Link as the only way to accept payments for your online shop.' A link 'takes your customer to a secure Adyen payment page' -- there is no catalogue, no cart and no order. The 250 occurrences of 'storefront' are all in the plugins book, where Adyen is the payment method installed into someone else's Adobe Commerce or Salesforce Composable Storefront. Adyen ships checkout, and a restaurant ordering site is not checkout. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/unified-commerce/pay-by-link · retrieved 2026-09-08

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

digital-menu-single-source

UPHELD, now cited. The claim asks whether one menu record feeds both the register and the digital channels; Adyen has no menu record at either end. Adyen holds no menu record of any kind. The Terminal API's 163 published schemas contain no item, basket, category or modifier object: a PaymentRequest carries SaleData (OperatorID, OperatorLanguage, ShiftNumber, SaleTransactionID, SaleReferenceID, SaleTerminalData, TokenRequestedType, CustomerOrderID, CustomerOrderReq, SaleToPOIData, SaleToAcquirerData, SaleToIssuerData) and PaymentTransaction.AmountsReq, whose whole field set is Currency, RequestedAmount, CashBackAmount, TipAmount, PaidAmount, MinimumAmountToDeliver, MaximumCashBackAmount and MinimumSplitAmount. Amounts, never items. Nothing propagates because nothing is authored: the in-person path receives an amount over Terminal API and the online path receives a closed, flat Checkout LineItem, and neither is stored as a catalogue Adyen could publish from. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/api-explorer/terminal-api/latest/post/payment · retrieved 2026-09-08

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

Network tokenization and stored payment details for returning shoppers are core Adyen capability, but the guest account, saved addresses and reorder belong to the ordering platform. https://docs.adyen.com/point-of-sale/ · retrieved 2026-08-01

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.

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

POS docs describe shopper recognition and loyalty program integration, i.e. identifying a shopper by card token; not a merchant-facing guest CRM. https://docs.adyen.com/point-of-sale/ · retrieved 2026-08-01

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

guest-loyalty-thirdparty-identity-attach

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

No accrual engine; integrates with loyalty providers. https://docs.adyen.com/point-of-sale/ · retrieved 2026-08-01

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

UPHELD, now cited, and Adyen states the division of labour itself. Its loyalty product is recognition, not a programme: 'To engage shoppers in loyalty use cases, you must have a back-end system to store customer profiles of your shoppers', and on the point-of-sale side, 'To use this method, you need to create customer profiles in your back-end system.' What Adyen supplies is the identifier -- the card alias and shopper reference returned in card-acquisition responses -- so that 'you look up the shopper in your loyalty program and decide on the discount or loyalty reward to offer.' Terminal API's loyalty objects are a pass-through to a loyalty acquirer, not a ledger: LoyaltyData carries only CardAcquisitionReference and LoyaltyAccountID, LoyaltyAccount only LoyaltyAccountID and LoyaltyBrand, and LoyaltyHandling is the enum Forbidden / Processed / Allowed / Proposed / Required. There is no campaign, segment, trigger or send. 'win-back' occurs zero times; 'birthday' occurs once, in an unrelated gift-card refund example. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/unified-commerce/loyalty-program · retrieved 2026-09-08

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.

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

UPHELD, now cited, and the near-miss is disposed of explicitly by the vendor. 'clock in' and 'time clock' each occur zero times in 53,523,717 characters. The one construct that resembles a clock-in is the Terminal API login, and its own page says what it is not: 'Log out of your terminal when changing operator, or at the end of a shift... This login request can additionally mark events like a change of operator or the start of a new shift, so that you can get the totals by operator or shift', followed immediately by 'The login request does not authenticate the operator.' Both OperatorID and ShiftNumber are optional and documented as 'Your identification of the operator' and 'Your identification of the shift' -- labels the merchant's own POS supplies to group reconciliation totals. No PIN, badge or card identifies a person, no hours are accumulated, and there is no clock-out event distinct from a terminal logout. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/point-of-sale/reconciling-totals/log-in-and-log-out · retrieved 2026-09-08

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

Resolved to partial: the permission model is genuinely per-action and not tiered, but it only covers the actions Adyen owns. 'User roles are sets of permissions that determine what the user can do in the Customer Area... Each user can have one or more roles', assignable individually or bundled into role groups, across thirteen documented categories (Account, Developer, Donation campaigns, Finance, Financial products, General, In-person payments, Online payments, Partners, Platforms, Risk, Transactions, Classic platforms). Discrete actions really are separable -- Refund payments, Cancel payments and Capture payments are three distinct roles, and viewing is split into 'View Payments' (more than 50 data fields) versus 'View key payments data' (more than 10, 'No access to shopper details, risk data, or more technical metadata'). Location scoping comes from account access rather than from the role: roles are granted together with access to specific accounts, and 'you can only assign roles or give access to accounts that your own user already has'. It falls short of yes because four of the seven actions the claim enumerates -- void, comp, discount and drawer open -- and price change have no permission to grant, Adyen having no register. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters, plus 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. https://docs.adyen.com/account/user-roles · retrieved 2026-09-08

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

Adyen's only native override gate is a terminal passcode, and it is shared, not personal: the Admin & Settings, Transactions and Refunds passcodes are "managed at the company, merchant, store, or terminal level" and "propagate to all terminals at and under that level", with no per-employee credential documented anywhere in the standalone terminal docs. Standalone refunds require "your 6-digit Refunds passcode", so the approval is gated but the approver is not identified. Attribution does exist on the back-office side — the Customer Area audit trail and the terminal Audit Log record "who performed the action, what was changed, and when it happened" — but that covers account settings and terminal configuration changes, not transaction-level overrides. In integrated mode the cashier identity is SaleData.OperatorID, an OPTIONAL Terminal API field, "Identification of the Cashier or Operator", supplied by the connecting sale system and not authenticated by Adyen. Named shortfall: override approvals are authorised by an org-level shared passcode with no individual approver attribution, and the audit trails that do name a user cover configuration, not overrides. https://docs.adyen.com/point-of-sale/menu-access/ · retrieved 2026-08-04

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.

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

UPHELD, now cited, with the homonym ruled out. 'recipe' and 'ingredient' each occur zero times in 53,523,717 characters. 'inventory' does occur, and in Adyen's vocabulary it means the terminal fleet, not stock: the Management API defines the reassignment status 'inventory: the terminal is in inventory and cannot process transactions', and of a closed store, 'The terminals under the store are reassigned to the merchant inventory.' The only stock-keeping Adyen mentions is the merchant's own software running on Adyen hardware -- 'For example, a POS app and an inventory maintenance app... This enables your staff to use a single device not only for taking payments, but also for other tasks like checking the inventory'. Adyen holds no product record to cost, so a multi-level recipe with sub-recipes has nothing to be built from. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/point-of-sale/android-terminals/deploy-apps · retrieved 2026-09-08

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

UPHELD, now cited. There is no stock item to carry a purchase, recipe or count unit. 'recipe' and 'ingredient' are zero across the corpus, and Adyen's 'inventory' is its own published term for the terminal fleet ('inventory: the terminal is in inventory and cannot process transactions'). The only unit Adyen models anywhere is money: amounts in minor units of a processing currency. Yield and waste percentages have no field in any of the 129 published specs. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/point-of-sale/android-terminals/deploy-apps · retrieved 2026-09-08

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

UPHELD, now cited. 'stock count' occurs zero times, as do 'recipe' and 'ingredient'; the corpus's 'inventory' is the terminal fleet, per the Management API's own status definition 'inventory: the terminal is in inventory and cannot process transactions.' With no stock record there is no physical count, no spot count, no cycle count and no variance history to keep. Adyen's own framing is that counting stock is the merchant's job on the merchant's app: 'you can install and use Android apps. For example, a POS app and an inventory maintenance app.' The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/point-of-sale/android-terminals/deploy-apps · retrieved 2026-09-08

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.

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

inventory-menu-margin-linkage

Not scored by this record.

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

Customer Area gives transaction visibility by terminal, store or region with automated settlement reporting; payments data only, not restaurant sales. https://docs.adyen.com/point-of-sale/ · retrieved 2026-08-01

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

reporting-eod-closeout

Settlement reconciliation reporting is documented, but it covers tender and payouts only — no net sales, tax, discounts or expected cash deposit. https://docs.adyen.com/point-of-sale/ · retrieved 2026-08-01

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

reporting-pmix-modifier-level

UPHELD, now cited, and this is the sharpest form of the scope line: Adyen cannot report on items because it is never sent any. Adyen holds no menu record of any kind. The Terminal API's 163 published schemas contain no item, basket, category or modifier object: a PaymentRequest carries SaleData (OperatorID, OperatorLanguage, ShiftNumber, SaleTransactionID, SaleReferenceID, SaleTerminalData, TokenRequestedType, CustomerOrderID, CustomerOrderReq, SaleToPOIData, SaleToAcquirerData, SaleToIssuerData) and PaymentTransaction.AmountsReq, whose whole field set is Currency, RequestedAmount, CashBackAmount, TipAmount, PaidAmount, MinimumAmountToDeliver, MaximumCashBackAmount and MinimumSplitAmount. Amounts, never items. The one place item detail reaches an Adyen terminal is a rendering payload, not a data model: to show a virtual receipt you 'gather all content in an XML file, convert this file to a Base64 string, and pass that string in a display request', where '<lines>: contains line items that represent the goods that the shopper is purchasing. Each line item can have a count, description, and amount.' The vendor's own instruction is to 'populate an XML input file with line items and total amounts from your POS app'. Nothing is stored, nothing is identified, nothing is reportable -- Adyen receives a picture of the check, and receiving is not authoring. The published reporting book is 36 pages and every one of them is a payments or settlement report -- settlement reconciliation at batch and transaction level, invoice reconciliation, payment accounting, disputed transactions, 3D Secure, balance transfers, sales-to-payouts, fiscal-period close. The word 'product' occurs exactly once across all 36 pages, in the advancements detail report. There is no product-mix report at item level, let alone at modifier level, and no daypart or revenue-centre dimension exists to filter one by: 'daypart' occurs zero times in the corpus. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/reporting · retrieved 2026-09-08

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.

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

Company account > merchant account > store > terminal is a real hierarchy that reporting and terminal management scope to; described in POS docs as by terminal, store or region. https://docs.adyen.com/point-of-sale/ · retrieved 2026-08-01

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

multi-location-central-menu-publish

UPHELD, now cited, and the interesting part is that the publishing machinery genuinely exists but carries the wrong payload. Adyen operates a real four-level configuration hierarchy -- company, merchant account, store, terminal -- in which 'settings defined at a certain level propagate to all terminals at and under that level. But settings defined at a lower level replace values inherited from a higher level.' What propagates is payment features and device settings: floor limits, store-and-forward limits, receipt logos, tender options. It is not a menu, because there is no menu; and the Store object itself is closed by additionalProperties: false over address, businessLineIds, description, externalReferenceId, id, localizedInformation, merchantId, phoneNumber, reference, shopperStatement, splitConfiguration, status and subMerchantData -- no catalogue, no price, no version. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/point-of-sale/design-your-integration/determine-account-structure/configure-features · retrieved 2026-09-08

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

UPHELD, now cited. 'price tier' and 'daypart' each occur zero times in 53,523,717 characters. Adyen holds no item record to carry a price at any level, and the Store object that would scope one is closed by additionalProperties: false with no price, price-list or menu field among its thirteen properties. The per-location money rules Adyen does publish -- surcharge configuration, payment-method availability, dynamic currency conversion -- act on the transaction amount the POS has already computed, never on an item price, and none of them is keyed by order channel or daypart. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/point-of-sale/design-your-integration/determine-account-structure/configure-features · retrieved 2026-09-08

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.

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

extensibility-public-api-docs

docs.adyen.com is fully public and self-serve, including the complete Terminal API and in-person payments reference. https://docs.adyen.com/point-of-sale/ · retrieved 2026-08-01

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

extensibility-api-access-cost

Not scored by this record.

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

extensibility-partner-revshare

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

Resolved to partial, one documented limitation short of yes. Adyen runs a real OAuth 2.0 authorization-code flow with PKCE for third-party applications: 'When your customer authorizes your access request, you get a token that you can use to authorize API requests on their behalf', and 'If the authorization code is intercepted, it cannot be used without the PKCE secret.' Access is scoped, with eight named scopes each carrying an identifier and an enumerated list of the Management API operations it unlocks -- psp.webhook:read, psp.webhook:write, psp.onlinepayment:write, psp.onlinepayment.tokenization:write, psp.rawcarddata:write, psp:paybylink:write, psp.accountsettings:write, psp.clouddeviceapi:write. Grants are individually revocable by the operator, immediately: revoking an installed app in Developers > OAuth authorizations means 'we immediately: Revoke the app's access to your account. Invalidate all active access', and the audit trail names the app as 'oauth_[Authorization_ID]@Company.[YourCompanyAccount]'. This is not shared static API keys. The shortfall is that the operator cannot shape the grant: 'At the moment it is not possible to extend the scopes after the OAuth app has been created. Your customer can also not select or deselect requested scopes. The authorization can only be granted with all requested scopes', and 'Currently, you cannot change the scope of an existing OAuth client.' Scoped by the developer, take-it-or-leave-it for the operator. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters, plus 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. https://docs.adyen.com/partners/oauth/scopes · retrieved 2026-09-08

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

extensibility-webhooks-push

Adyen pushes webhooks for payment, dispute and payout lifecycle events; there is no restaurant order lifecycle (created/modified/voided) to subscribe to. https://docs.adyen.com/development-resources/webhooks/ · retrieved 2026-08-01

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.

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

extensibility-menu-write-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.

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

reliability-offline-order-entry

UPHELD, now cited, and deliberately not overstated: Adyen has a real and well-documented offline mode, but it is an offline PAYMENT mode. Two mechanisms are published -- offline EMV, where 'the payment terminal verifies that the PIN entered by the shopper matches the PIN on the EMV chip... and then asks the card to approve the payment', and store and forward, where 'the payment terminal or Mobile SDK approves payments without any verification' up to a configured maximum amount and maximum number of transactions, later forwarding them: 'Later, when the terminal or Mobile SDK is able to connect to the internet again, it sends the stored payments to the Adyen payments platform for further processing.' Receipt printing survives the outage on a standalone terminal ('If you are using a standalone terminal, it will print the receipt'). None of that is what the claim asks. Adyen has no order and no ticket to enter or route while online, so there is nothing to continue while offline; a scheme-compliant card receipt is not a guest check. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/point-of-sale/offline-payment · retrieved 2026-09-08

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

UPHELD, now cited. 'kitchen display', 'kitchen printer' and 'KDS' each occur zero times in 53,523,717 characters. The only printing Adyen documents is the terminal's own built-in receipt printer, and its output is enumerated and closed: Terminal API's DocumentQualifier admits exactly SaleReceipt, CashierReceipt, CustomerReceipt, Document, Voucher and Journal -- no order ticket, no station, no prep chit. There is no kitchen routing to keep working offline, online or otherwise. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/point-of-sale/offline-payment · retrieved 2026-09-08

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

UPHELD, now cited. Fallback needs a second target, and Adyen publishes exactly one printer per terminal, built into the device: 'Some payment terminals, like the V400m or V400c, have a built-in printer. Such terminals automatically print the receipt using the Terminal API receipt data.' The documented behaviour when a merchant does not want that printer used is a manual opt-out, not an automatic failover -- 'If you do not want to print the receipt on the terminal, specify the tender option ReceiptHandler in your payment requests... You can then let your POS app send the receipt data to your receipt printer, or email the receipt to the shopper.' The routing decision and any recovery from it sit in the merchant's POS app. Terminal API does report printer health -- PrinterStatus is the closed enum OK, PaperLow, NoPaper, PaperJam, OutOfOrder -- so the terminal can tell the POS the paper has jammed, but Adyen configures no backup station to reroute to and raises no staff alert of its own. The scope sentence is Adyen's own: on Android terminals, 'You create your Android app' and Adyen signs and deploys it, 'For example, a POS app and an inventory maintenance app.' Adyen supplies the device, the acquiring and the terminal management; the merchant supplies the point-of-sale software. Measured over the Adyen corpus frozen 2026-09-08: 2,535 docs.adyen.com pages, 53,523,717 characters -- the 2,523 pages of the publisher's own llms-full.txt plus 12 of the 43 sitemap URLs it omits -- together with 12 of the 129 OpenAPI specs Adyen publishes at github.com/Adyen/adyen-openapi. Absence is measurable on this host: a fabricated path under any doc tree 404s at exactly 245,687 bytes / 16 stripped characters, against 10,493 for the live /point-of-sale page. The sitemap is a stale index rather than a manifest -- 29 of its 2,565 locs answer that same 404 -- so llms.txt is the current census and the union is the corpus. https://docs.adyen.com/point-of-sale/basic-tapi-integration/generate-receipts · retrieved 2026-09-08

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.

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

reliability-menu-build-service

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.

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

CLAIM: 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. VERDICT: yes/B (was unknown/F; the old rationale read only the pricing page). EVIDENCE: Adyen Terms and Conditions (www.adyen.com/legal/adyen-terms-and-conditions; 'Unless otherwise agreed, the following terms apply to Agreements entered into on or after 1 November 2023'; 'Last update 1 November 2023'; anonymous 200; robots.txt is `User-agent: *` with no Disallow): '11. Duration and Termination 11.1 Duration and Termination for Convenience Except where explicitly agreed otherwise in the Agreement, the Agreement is entered into for an indefinite period, until it is terminated by either party by providing at least two (2) months' written notice to the other party.' So the term structure is public (indefinite/evergreen - there is no renewal cycle to roll into) and the notice window is public (two months). The pre-November-2023 terms (www.adyen.com/legal/terms-and-conditions, 'Effective from: March 7th, 2023') carry the same rule at 10.1: 'the Merchant Agreement is entered into for an indefinite period until it is terminated by either party by giving at least two (2) months' written notice'. Also public, 4.2: price increases need 'three (3) months' prior notice' and the merchant 'may terminate its Agreement' during that window. CAVEAT: 'Except where explicitly agreed otherwise in the Agreement' - a signed Merchant Agreement can set a fixed term; the default is nonetheless published, which is what the claim tests. Retrieved 2026-09-16. https://www.adyen.com/legal/adyen-terms-and-conditions · retrieved 2026-09-16 adversarially verified

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

Transaction pricing is published in specific figures — unusual and creditable — but there is no published per-location or per-terminal software price. https://www.adyen.com/pricing · 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

CLAIM: all required terminals, KDS screens and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental. VERDICT: partial/B (was unknown/F). SATISFIED, outright purchase and no lease: Adyen Payment Device Terms of Service (www.adyen.com/legal/payment-device-terms-of-service, 'Last update 1 November 2023') 1.1 'The sales price for each Payment Device includes the following: Payment Device hardware equipped with the relevant Software, Adyen key, ...'; 1.2 'Orders for Payment Devices are invoiced to Merchant on a monthly basis, based on the shipping date of the relevant Payment Device(s).'; 2.6 'Payment Devices and accessories purchased by Merchant'; 3.4 'each Payment Device sold by Adyen to Merchant'. The optional Replacement Service is a monthly fee with an 'indefinite term' that 'Merchant may terminate ... per the end of any calendar month by giving at least one week prior notice' - no multi-year commitment. Tokenised controls over that page: rent*|leas*|financ* -> 0 hardware hits (the matches are 'Replacement' and 'least cost routing'). SHORTFALL, price not published: 1.1 'Pricing for Payment Devices and accessories will be as agreed in the Agreement or as set out in Adyen's latest pricing list ... The latest pricing list for Payment Devices and accessories can be provided upon request.' www.adyen.com/pricing carries no terminal/hardware price. Prices exist only behind authentication: Management API v3 (Adyen/adyen-openapi json/ManagementService-v3.json, read via raw.githubusercontent.com) GET /merchants/{merchantId}/terminalProducts 'Returns a country-specific list of payment terminal packages' with TerminalProduct.price {currency, value}, requiring an API credential with the Management role. Adyen supplies payment terminals only (no KDS screens or kitchen printers). Retrieved 2026-09-16. https://www.adyen.com/legal/payment-device-terms-of-service · retrieved 2026-09-16 adversarially verified

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.