ItsaCheckmate

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

CLAIM: supports modifier groups nested at least three levels deep, each level with independent min/max selection counts and a forced-selection (required) flag. THE PROPOSED 'no' IS REJECTED BECAUSE IT WAS BOUNDED TO THE WRONG CORPUS. ItsaCheckmate publishes an anonymous, robots-allowed developer hub at openapi-itsacheckmate.readme.io, linked from www.itsacheckmate.com/onboarding/marketplace-developer-onboarding as 'Checkmate OpenAPI Documentation'; its llms.txt lists 15 pages and I fetched all of them (199,443 bytes). That corpus states the opposite of the help centre. MIDDLEWARE SCOPE RULING, made explicitly: the taxonomy asks whether the product MODELS the structure, not whether bytes traverse it, and Checkmate DOES model it - the objects below are Checkmate's own Get Menu and Submit Order schemas, not a connected POS's and not a marketplace's. MET (1) NESTING IS IN CHECKMATE'S OWN MENU SCHEMA. In the Get Menu response schema at this url, a menu item carries modifier_groups[], each group carries modifiers[], and each MODIFIER carries its own 'modifier_groups' array - the structure is recursive in Checkmate's published contract. Checkmate says so in prose too: 'modifiers (array, optional) - we allow for nested modifiers, but this is not a commonly used feature' (https://openapi-itsacheckmate.readme.io/page/order-receivers), and the Submit Order schema declares 'modifiers: { type: object, description: "Nested or second level modifiers. May require additional work with you to get this working." }' (https://openapi-itsacheckmate.readme.io/reference/submit-an-order). MET (2) INDEPENDENT MIN/MAX PER GROUP: every modifier_groups item declares maximum_amount, minimum_amount and allow_modifier_multiple_quantity (21 occurrences each of minimum_amount and maximum_amount across the Get Menu page). The portal side matches - Checkmate's Direct Sync capability matrices carry the rows 'Set Min/Max on Modifier Groups', 'Add New Modifier Group', 'Add new Modifier' and 'Change/Edit Modifier Price', and the Toast Direct Sync manual lets an operator edit 'Modifier Group Name, Required? Status, Multi-select, and Min-Max directly from this view' (https://support.itsacheckmate.com/hc/en-us/articles/8166742779419-Toast-POS-Direct-Sync-Manual). MET (3) FORCED SELECTION: the Direct Sync matrices carry the row 'Enable Required Modifiers', the portal exposes a 'Required? Status' field, and the order-error taxonomy has a 'Min Max Errors - Violations of minimum/maximum constraints' category (https://support.itsacheckmate.com/hc/en-us/articles/27696575802651-Types-of-Order-Errors). SHORTFALLS, numbered, and they are the reason this is not a yes. (1) THREE LEVELS IS NEVER DOCUMENTED: Checkmate's own words are 'second level modifiers', and the nested modifier_groups array at modifier level is declared as a bare {type: array} with NO items schema, so nothing in the published contract says a level-2 group carries its own minimum_amount/maximum_amount - 'each level with independent min/max' is unproven below level 1. (2) IT IS NOT TURNKEY: 'May require additional work with you to get this working', and 'not a commonly used feature'. (3) FIVE POS INTEGRATION PATHS REQUIRE FLATTENING BEFORE ONBOARDING, each checklist carrying an identical worked example (Item Burger / Modifier Group Cheese / Modifier Swiss, American, Cheddar / Nested Modifier ...): Brink 'Remove all nested modifiers (modifiers with modifier groups)' (https://support.itsacheckmate.com/hc/en-us/articles/8185480110235), SpotOn (.../8185709515291), Revel (.../8192970358811), Clover (.../8194853288475), Square (.../8196938850971); and Brink is refused outright - 'Note: Checkmate's system does not support nested modifiers for Brink POS' (.../8185581258907). (4) BOTH PUBLISHED DIRECT SYNC MATRICES MARK THE ROW: SpotOn Direct Sync Matrix 'Nested Modifiers X' (.../38870336101915) and Genius (formerly Heartland) Direct Sync Matrix 'Nested Modifiers X' (.../28454063126683). (5) The cross-POS standard says 'Avoid nested modifiers - which are modifier groups that are assigned to modifiers within another modifier group' (.../8126546949147, POS Integrations / General POS Integrations Info), and ezCater rejects them downstream (.../41076077506331). THE POISON THAT WOULD HAVE INVERTED THE VERDICT IN THE OTHER DIRECTION, and I confirmed it by reading both table headers: 'Genius (formerly Heartland) - Integration Partner Matrix' (.../28455137521435) shows 'Nested Modifiers [check][check][check]', but its own header reads 'The table below indicates if a feature is supported for an Integration Partner for the Genius POS' - three columns of MARKETPLACES. The near-identically titled Direct Sync Matrix header reads 'indicates if a feature is supported and where it needs to be updated (Genius POS or in Checkmate UI)' and marks the same row X. Two tables, same section, almost the same title, only one scoped to the vendor being scored. CONTROLS, tokenised word-boundary AND left-boundary stem, comments stripped before tags, scripts written to disk: over all 383 help-centre articles nested|nesting|sub-?modifier = 19 hits in 12 articles, every one a removal or non-support instruction except the marketplace-scoped row; over the 15-page developer hub the same control = 2 hits in 2 pages and BOTH are permissive. Positive controls: help centre Checkmate 799 hits / 201 docs, order 1,546 / 190, the 9,534 / 377; developer hub Checkmate 15 / 3, order 130 / 14. BOUND CORPORA AND THEIR HOLES. Help centre: href fixpoint re-derived - 172 distinct /hc/{locale}/articles/<id> references inside raw bodies, 14 not held, probed at support.itsacheckmate.com/api/v2/help_center/en-us/articles/<id>.json giving 0 unlisted published 200s, 0 gated 401/403s and 14 stale 404s, with three fabricated 14-digit control ids also 404. Attachments: 2,521 over 383 articles, only 6 non-image (two 435-byte text/plain, four mp4 on the Store Groups article), NO PDFs. VIDEO HOLE, NAMED: 257 iframes across 161 of 383 articles (42%) - 139 scribehow, 55 loom, 1 drive.google and 62 whose src I could not parse - and several portal how-tos are a stub sentence plus an embed, so no text-only census of this KB is complete. Developer hub hole: llms.txt is a STRICT SUBSET of the site - reference/webhook-details-and-authentication-overview is referenced from a listed page and is not itself listed, so the hub is a floor, not a census. https://openapi-itsacheckmate.readme.io/reference/getting-started-with-your-api-1 · retrieved 2026-09-15 adversarially verified

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

Checkmate is a sync layer, so what its menu schema can represent is the capability. The Modifier Disambiguation IDs page states: 'In some cases - a Modifier Items will have a different price when it's attached to a different Menu Item. In such cases we may use a Special Format for the Modifier Item id that allows us to easily determine the context - with CM_USE_ID in the middle', with the id form <uuid>##CM_USE_ID##MenuItem:<item-id>##ModifierItem:<mod-id>. Per-parent-item modifier pricing therefore survives the sync out to the marketplaces. Shortfall: it is carried as a separate context-qualified modifier instance per parent item - duplication with a disambiguation key, not a matrix - and there is no size dimension anywhere in the Get Menu schema; modifier objects expose a single scalar price and sizes appear as ordinary modifier items or separate menu items each with their own price. Checkmate cannot configure any of it either: 'Prices are established directly at the Point Of Sale (POS) systems rather than through the Checkmate Portal. We do not support individual pricing adjustments for items or modifiers on online menus', the only portal price control being a uniform Price Elevation percentage across all items and modifiers (support.itsacheckmate.com article 8127887582619). https://openapi-itsacheckmate.readme.io/reference/modifier-disambiguation-ids · retrieved 2026-08-04

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

The Get Menu reference gives modifier groups minimum_amount, maximum_amount and allow_modifier_multiple_quantity, and the menu meta object carries allows_mod_quantitieas [sic] - so modifier quantity is supported, but only as a repeat count of the same modifier, which is exactly the mechanism this claim distinguishes tiers from. Shortfall: no tier construct and no price-multiplier field exists in the schema - searching the full Get Menu reference payload returns zero occurrences of 'multiplier', and a modifier object exposes only id, name, price, description, suspend_until, is_alcohol, nutritional_info and a nested modifier_groups array. Light/regular/extra can therefore only travel as separate modifier items each with a flat price, and Checkmate cannot set those prices: 'We do not support individual pricing adjustments for items or modifiers on online menus; all prices must originate from the POS' (support.itsacheckmate.com article 8127887582619). https://openapi-itsacheckmate.readme.io/reference/getting-started-with-your-api-1 · retrieved 2026-08-04

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

No first-party payment terminals; card acceptance sits with the marketplace or the integrated POS. https://itsacheckmate.com/ · retrieved 2026-08-01

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

payments-softpos-tap-to-pay

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

First-party gift cards do exist, on Checkmate Direct Ordering: 'Direct Ordering supports digital gift cards that can be created, activated, and loaded with credit for customers to use at checkout' (support article 41206446643483). Balances are live at the point of redemption - the guest presents a QR code or the card number, 'The gift card balance is applied to the total', and 'Gift card balances can be used for full or partial payment'. Shortfall: digital-only and effectively single-POS. 'Only Direct Ordering Digital Gift Cards can be used with this process. Physical gift cards and other gift card systems are not supported', and the only documented in-store, phone and drive-thru redemption path requires 'Toast POS with the Direct Ordering Digital Gift Card integration enabled'. No documentation was found for in-store redemption on any other integrated POS, so redemption across every location in a mixed-POS group is not established. https://support.itsacheckmate.com/hc/en-us/articles/38072866230299-Using-Digital-Gift-Cards-with-Toast-POS · retrieved 2026-08-04

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

Role-gated refunds and voids are documented for Direct Ordering. Adding Users and Managing Permissions defines five ranked roles (Admin, Catering Manager, Manager, Cashier, Employee) and per-function minimum-role settings including 'Refund Orders', 'Cancel Orders', 'Edit Orders - Quick Edit' and 'Edit Orders - Full Edit': 'If the role of Admin is assigned, only users with the Admin role can cancel orders.' Processing and Calculating Refunds (article 37713905696411) confirms the gate - 'A refund can be requested from Checkmate Support or, depending on account permissions, processed directly from the Direct Ordering Admin Panel' - and defines voids: uncharged Pending/Open orders 'are canceled (voided) instead, in full only, with no partial voids', while 'a refund cannot be reversed once it is processed.' Shortfall: the audit half of the claim is not documented - no article describes an audit log, immutable or otherwise, identifying who processed a refund or void - and the discount and no-sale halves have no analogue because Checkmate has no register or cash drawer; authorization is a role threshold at login, not a manager-PIN-at-terminal approval. https://support.itsacheckmate.com/hc/en-us/articles/26312240204827-Adding-Users-and-Managing-Permissions · retrieved 2026-08-04

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

Product is marketplace channel management; no in-house driver entity, clock-in, or run history is documented. https://itsacheckmate.com/ · retrieved 2026-08-01

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

delivery-dispatch-board

The Admin Panel orientation enumerates the order screens - 'Orders Overview: Provides an overview of all orders, including today's orders, upcoming orders, and held orders' and 'Order Management: Manages open and upcoming orders at the store level' - and neither is a dispatch board. Delivery is fulfilled by third-party last-mile providers, not own drivers: store settings carry 'Delivery Integration, Delivery Service Provider Setup', the integrations list names DoorDash Drive, Relay and Uber Direct, and the Delivery report 'reviews delivery order data for orders fulfilled through a delivery provider'. No driver entity exists anywhere in the product (see delivery-driver-roster), so a screen showing driver availability or batching 2+ orders onto one driver's run has nothing to operate on. The only driver artefact in the documentation is the Driver Wait Time Report (article 29732578925851) on marketplace couriers' waits, 'currently available only for DoorDash and Uber Eats' with data 'at least two days old' - a retrospective report, not dispatch. Re-pointed 2026-08-12: the article was renamed from "Introduction to the Direct Ordering Admin Panel" to "Navigating the Direct Ordering Admin Panel". Same Zendesk article id (26107840524187), same document; both quoted passages were re-verified as still present. On this host the slug is decorative and self-correcting, so the old URL still resolves. https://support.itsacheckmate.com/hc/en-us/articles/26107840524187-Navigating-the-Direct-Ordering-Admin-Panel · retrieved 2026-08-12

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

The address-validation half is documented: each store's revenue center has a delivery zone (circular radius or a custom shape drawn on the map), the customer enters a delivery address and 'Direct Ordering automatically checks which store locations deliver to that address', with numbered zone priorities resolving overlaps between nearby stores. Shortfall: zones gate eligibility only. Each revenue center has exactly one zone, and nothing in the article attaches a delivery fee, an order minimum, or a quoted promise time to a zone, so there is no construct for near/far pricing tiers. The only documented fee path is flat and out-of-band: 'Sending Delivery Fees through your POS' (article 8126991461147) says to add the fee in the POS and email support@itsacheckmate.com to have it applied per ordering platform. An 'Advanced Delivery' entry and a Surcharges page appear in the Admin Panel settings list, but no public article documents per-zone fee, minimum, or promise-time configuration. https://support.itsacheckmate.com/hc/en-us/articles/26310661867035-Setting-up-Delivery-Zones · retrieved 2026-08-04

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

Site markets first-party web and app ordering plus kiosk alongside marketplace channels; commission structure and domain branding are not specified. https://itsacheckmate.com/ · retrieved 2026-08-01

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

digital-menu-single-source

Core product: EveryWare unified channel and menu management, centrally managing menus across marketplaces and syncing to POS. Reinforced by DoorDash 2026 Preferred Integration Partner status, which requires real-time menu syncing. https://itsacheckmate.com/ · retrieved 2026-08-01

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

digital-native-app

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

All three elements are in the Direct Ordering admin documentation. Saved cards: 'By default, logged-in guests can save credit cards to their profile for faster checkout on future orders', configurable brand-wide across 'both the Web App and the Mobile App' with Prevent / Hide / Guest Choice options; cards live with the payment processor (NMI or Stripe, per How Credit Card Payments Work, article 26312726330779). Saved addresses: the Customer Details page lists 'Address: the customer's saved address or addresses' with unit number and last-used date (article 37713575428635). Reorder: 'For a customer with a registered Direct Ordering account, signed in with a verified email address, reordering a past order and paying with a saved credit card takes only a few clicks' - from the homepage for the most recent order or from Order History for older ones - plus a Favorites tile for one-tap access to favorited items (article 22212398288923). https://support.itsacheckmate.com/hc/en-us/articles/39186287279131-Managing-Saved-Credit-Cards-for-Logged-In-Guests · retrieved 2026-08-04

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

A single Direct Ordering profile per guest is documented - the Customer Details page carries contact details, loyalty program, tier, points and credit, full order history and saved addresses (article 37713575428635) - and in-store POS transactions can land on that same loyalty account: staff look the guest up by QR code, phone or email at the register, and a missed transaction 'can be added manually to the guest's loyalty account by entering the purchase details into the system within 24 hours'. Shortfall: the in-store leg is documented only for Toast POS, and attachment is staff-initiated identification at checkout rather than an automatic match - 'Linking a payment card in the app does not automatically earn points for in-store purchases. Guests must still identify themselves at the Toast POS by scanning their QR code or providing their phone number or email at checkout.' Kiosk orders are nowhere documented as attaching to the profile, and no dedup/merge behavior is documented anywhere - the closest article, Updating Customer Email Addresses (26331485594907), covers changing a login email, not merging duplicate profiles. https://support.itsacheckmate.com/hc/en-us/articles/29361529216923-Earning-and-Redeeming-Loyalty-with-Toast-In-Store · retrieved 2026-08-04

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

CLAIM: 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. Checkmate supports all three, in its own first-party product. MIDDLEWARE SCOPE RULING, made explicitly because this is the only positive claim on a middleware record: Checkmate Direct Ordering is ItsaCheckmate's OWN web/app ordering product, which the atlas record already scopes in ('plus first-party web/app ordering, kiosk, AI voice ordering, catering and reconciliation'), and the article's own title says 'Supported by Direct Ordering'. The decisive sentence naming the owner is in a companion article: 'The Checkmate Direct Ordering loyalty program enhances guest satisfaction...' (https://support.itsacheckmate.com/hc/en-us/articles/29361529216923-Earning-and-Redeeming-Loyalty-with-Toast-In-Store). This is not a connected POS's loyalty and not a marketplace's. MET (1) POINTS PER DOLLAR: 'Bankable points let customers earn points for each dollar spent. The restaurant chooses how many points are earned per dollar and what the points are called, such as "stars" or any custom term. Points are awarded on the order subtotal before taxes, tips, and fees... if a customer spends $2.95 and the earning rate is 2 points per dollar, the calculated value is 5.90, so the customer receives 5 points'; plus 'Assign point values only to selected items'. MET (2) SPEND-TIER: 'Direct Ordering also supports traditional spend-based programs, which reward customers with credit as they cross a spending threshold, for example "Spend $50, get a $5 reward." ... Separate programs can run for different order types, each with its own thresholds and status tiers.' MET (3) VISIT/PUNCH: 'Punchcard Loyalty. Punchcard loyalty rewards customers based on the number of visits or orders. For example, after five visits a customer receives a free meal valued at $15.' IT IS CONFIGURATION, NOT DEVELOPMENT: 'each configurable to match a restaurant's business model', and the reward object is a named field set in the Direct Ordering Admin Panel - Name, Discount Type (Percentage / Dollar Amount), Minimum and Maximum Discount Amount, Minimum and Maximum Order Size, Points Shop Cost, Order Type (All/OLO/Catering/Merch), Service Type (Dine-In/Pick-Up/Delivery), Channel Type (Kiosk/Online/App/Phone), Days Valid, start and end date and time, Title, Short Description (https://support.itsacheckmate.com/hc/en-us/articles/33406785422875-Rewards), with Reward Events (.../33406731592347) and Bonus Periods applying an earning multiplier ('if the earning rate is 2 points per dollar and a customer spends $10, they normally earn 20 points; with a 2x Bonus Period, they earn 40', .../39545479208091). NOT A BOLT-ON: Checkmate documents a third-party loyalty service as the ALTERNATIVE, not the mechanism - 'This feature becomes available once the third-party loyalty service is turned on. It applies to the scenario where a restaurant launches first-party ordering first and adds an integrated third-party loyalty solution at a later time' (.../22979770595611). WHICH CATEGORY: Checkmate Direct Ordering (1st Party) / Loyalty & Marketing, 15 articles. FRESHNESS - THE BRIEF NAMED TWO BULK RE-SAVE MINUTES AND THERE ARE AT LEAST SIX. I bucketed every updated_at by exact second: 2026-06-29T20:19:50Z carries 15 articles (all of Loyalty & Marketing, including this one), 2026-06-26T19:57:57Z carries 12, 2026-06-26T15:40:13Z carries 10, 2026-06-29T20:46:07Z carries 9, 2026-06-26T14:40:32Z carries 9 and 2026-06-11T17:37:50Z carries 9 (all of Direct Ordering Menu Setup), on top of the 42 sharing 2026-06-02T17:30 and 20 sharing 2026-04-20T21:05. updated_at is therefore NOT cited as currency for any article in this cell; the verdict rests on the prose, which is detailed, internally consistent and cross-referenced. CONTROLS, tokenised, scripts written to disk: punchcard|punch card|bankable = 6 hits in 2 articles, 'points per dollar' = 2 in 2, loyalty = 91 in 21. Positive controls Checkmate 799 / 201, order 1,546 / 190, the 9,534 / 377. BOUND CORPUS AND HOLES: href fixpoint re-derived - 172 referenced ids, 14 absent, 0 unlisted published 200s, 0 gated, 14 stale 404s, three fabricated 14-digit controls all 404. 2,521 attachments over 383 articles, 6 non-image, none loyalty-related. VIDEO HOLE, NAMED: 257 iframes in 161 of 383 articles (42%); this particular article is an exception - I checked its raw bytes and it carries ZERO iframes and 3,410 characters of prose - but nine of the fifteen Loyalty & Marketing articles do carry embeds, so the step-by-step configuration screens are partly unreadable to me. That limits the configuration detail I can attest to, not the existence of the three accrual models, which is stated in text. https://support.itsacheckmate.com/hc/en-us/articles/26309755876379-Types-of-Loyalty-Programs-Supported-by-Direct-Ordering · retrieved 2026-09-15 adversarially verified

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

Trigger-based always-on campaigns are a documented Direct Ordering feature, distinct from one-off sends. Setting Up Automated Email Campaigns: 'An automated email campaign sends emails to guests based on one of the following trigger points' - Birthday (a set number of days before, on, or after the birthday), Last Order Date (on, or a set number of days after, the last order date: the lapsed win-back case), and Order Placed (on, or a set number of days after, an order: the post-purchase thank-you case). Reward Events (article 33406731592347) repeats the pattern on the rewards side: 'Automated Reward Event: a recurring reward triggered by events such as birthdays, last orders, or registrations', the registration trigger covering the first-visit welcome. Tier attainment also delivers 'Automated Rewards: rewards are added to customer accounts automatically and sent by email, SMS, and push notification' (Types of Loyalty Programs, article 26309755876379). https://support.itsacheckmate.com/hc/en-us/articles/29659156081563-Setting-Up-Automated-Email-Campaigns · retrieved 2026-08-04

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

No labor or time-and-attendance product in the catalog. https://itsacheckmate.com/ · retrieved 2026-08-01

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

labor-photo-punch-verification

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

Permissions are granted per discrete action, not by fixed tier. The admin guide enumerates individually assignable permissions in six sections: Menu (Add Items or Modifiers, Edit Item or Modifier Names, Edit Tax Rate, Edit Modifier Group Min/Max, Edit Price Elevation Percent, Sort Menu Items, Delete Menu Items or Modifiers, Toggle Menu Item Availability, 'Push, Pull, and Revert Menu'), Location (Create/Update/Manage Location, Toggle Store Status, Update Holiday Hours, Update Kitchen Prep Time, Access and Configure Integration Settings), User (Create, Update, Delete, Archive, Manage Users), Partner, Insightful Analytics - where every report is separately grantable (View Order Summary Reports, View Top Selling Items Report, View Sold Out Frequency Report, View Promo Analysis Report, View System Health Report, Customize Alerts) - and Other (View Credentials, Edit Credentials, Refunds Dispute Access, View Account Reconciliation, View Order Errors). 'The master user can assign these permissions to control what other users can view, modify, or manage.' Per-location scoping is explicit and separate: the Manage User Access interface lets an admin 'view the assigned locations' and assign or unassign locations or brands per user, and archived users retain 'permissions, preferences, and location assignments' (article 8132791104411). The register-side actions in the claim's parenthetical (void, comp, drawer open) have no analogue because Checkmate has no terminal. https://support.itsacheckmate.com/hc/en-us/articles/8132477413915-Manage-User-Access-Permissions-Explained · retrieved 2026-08-04

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

Individual attribution exists for the privileged actions Checkmate does have, and it is queryable after the fact through the Reporting API. Sold Out Items Details exposes sold_out_action_started_at and sold_out_action_started_by ('Email or identifier of the person who marked the item as sold out'), sold_out_action_ended_at, sold_out_action_ended_by, reason, offline_hours and times_went_offline; Item Sold Out Events adds user_id plus a superseded flag and next_pushed_event_id; Order Details records asker_id, assignee_id, assigned_to, resolved_by, reviewer_id, submitter_id and canceled_by against each order error. Shortfall: Checkmate has no register and documents no manager-override or approval-at-the-terminal flow, so the specific artefact the claim describes does not exist here; no in-portal audit-log view is documented anywhere in the Account Management or Portal sections; and nothing in the documentation asserts the log is immutable. https://support.itsacheckmate.com/hc/en-us/articles/30504461783963-Reporting-API-Internal-Data-Tables · 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

No inventory or recipe costing product; the catalog is ordering, channels, kiosk, voice, loyalty and reconciliation. https://itsacheckmate.com/ · retrieved 2026-08-01

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

inventory-unit-conversion-yields

No inventory module exists in the published product catalog. https://itsacheckmate.com/ · retrieved 2026-08-01

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

No inventory counting product is offered. https://itsacheckmate.com/ · retrieved 2026-08-01

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

inventory-mobile-count-offline

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

Markets financial reconciliation and cross-channel reporting; refresh latency, browser plus mobile access are not specified. https://itsacheckmate.com/ · 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

CLAIM: 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. MIDDLEWARE SCOPE RULING: ItsaCheckmate IS the publisher who would document this if it were true, because Checkmate Direct Ordering is its own first-party ordering and payments product with its own reporting menu - so this absence is bounded to the right publisher, not inferred from a middleware's silence about someone else's POS. POSITIVE EVIDENCE OF ABSENCE, three ways. (1) THE FIRST-PARTY REPORT CATALOGUE IS ENUMERATED AND CLOSED, at this url: 'Checkmate Direct Ordering offers an extensive catalog of reports that provide insights into online orders... The available reports are: Receipts, Tenders Summary, Tenders, Product Mix, Credit Cards, Order Ratings, CSV Downloads.' Each is a filterable transaction list, not a close-out packet - 'The Tenders Summary report provides a summary of the payment tenders collected across orders... Filter by Dates, Store location, Sale Type (Sale, Refund), and Order Source' (.../33647513854491). (2) THE OTHER CATALOGUE IS ENUMERATED TWICE AND IS ABOUT SOMETHING ELSE: Reconcile's full report list appears in 'What is Reconcile?' (.../26108047066139) and 'Types of Reconcile Reports' (.../26109471700635) - Unified Statement, Refunds and Adjustments, Sales Reconciliation, Deposit Reconciliation, Dashboard, POS to Statement Bridge, Fully Reconciled Transactions, Unreconciled Transactions, Tax Rate by Location. Every one reconciles ORDERING-PLATFORM STATEMENTS TO BANK DEPOSITS - 'bridges the sales per your Ordering Platform statement to the deposit in your bank account'. That is marketplace payout reconciliation, a different artefact from a nightly manager close-out. (3) THE CASH LEG CANNOT EXIST. CONTROLS, tokenised word-boundary AND left-boundary stem, comments stripped before tags, scripts written to disk, over all 383 articles and 879,505 characters of stripped body text: cash = 0 both-boundary. PRECISION CORRECTION TO THE PRIOR PASS, which had written 'Checkmate never mentions cash at all': the STEM run returns 2, and both are 'cashier' - the Direct Ordering role list 'Admin, Catering Manager, Manager, Cashier, Employee' (.../26312240204827) and 'QR ordering reduces the need for a dedicated front-of-house cashier' (.../26312298800411). Neither is a drawer. I also ran the control over Checkmate's public developer hub (15 pages, 199,443 bytes, openapi-itsacheckmate.readme.io) and cash = 1 there: the boolean 'cash_payment: Attribute to identify a cash order' in the Submit Order schema - a flag on a relayed marketplace order, not a cash reconciliation. Supporting zeros, all tokenised over the help centre: EOD = 0, 'end of day' = 0, close out / close-out = 0, 'daily close' = 0, 'cash drawer' = 0, drawer = 0, 'z report' = 0, 'shift report' = 0, and EOD = 0 over the developer hub too. PUBLISH THE POISON: till = 2 hits and BOTH are the preposition - 'if you wish to receive orders till 9:00 pm' (.../26106561220251) - which a substring reader would have called a cash till. deposit = 79 hits in 17 articles and every one is a BANK deposit of a marketplace or processor payout inside Reconcile, never a cash deposit; that is the exact homonym that could have faked the claim's decisive conjunct. Positive controls: Checkmate 799 / 201, order 1,546 / 190, the 9,534 / 377. WHY NOT PARTIAL: the claim is for ONE document reconciling eight named lines. Checkmate's tender, refund and discount data is spread across separate filterable exports with no close-out artefact, and one of the eight lines cannot exist in a product that never holds a drawer, so a partial would shortfall the defining conjunct. BOUND CORPORA AND THEIR HOLES. Help centre: href fixpoint re-derived from scratch - 172 distinct referenced ids, 14 absent, probed at the Help Center API giving 0 unlisted published 200s, 0 gated 401/403s, 14 stale 404s, three fabricated 14-digit control ids also 404. ZERO GATED ARTICLES ANYWHERE IN THIS CORPUS is what licenses a zero at all. Attachments: 2,521 over 383 articles, 6 non-image, NO PDFs, nothing report-bearing. Second corpus: Checkmate's public developer hub, all 15 pages listed in its llms.txt, fetched and searched - no reporting surface at all. I also probed developers./docs./developer./documentation.itsacheckmate.com (all DNS-dead) and api.itsacheckmate.com (a sign-in wall, not a doc host). VIDEO HOLE, NAMED AS THE LIMIT OF THIS ZERO: 257 iframes across 161 of 383 articles (42%) - 139 scribehow, 55 loom, 1 drive.google, 62 unparsed - whose on-screen steps no text census can read. What bounds the zero despite that hole is that both report catalogues are written out as CLOSED ENUMERATIONS in prose, and a report's NAME would appear in the catalogue even if its steps lived in a video. FRESHNESS: the Direct Ordering reporting articles all share the bulk second 2026-06-29T20:46:07Z (9 articles), one of six bulk re-save seconds I measured, so updated_at is not cited as currency; 'Types of Reconcile Reports' is 2025-06-11. https://support.itsacheckmate.com/hc/en-us/articles/33646351597851-Accessing-Direct-Ordering-Reporting · retrieved 2026-09-15 adversarially verified

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

Modifier-level product mix is real. The Top Selling Items report has three tabs - Overview, 'Item Details: Provides detailed sales data for each item' and 'Modifier Details: Shows detailed sales data for modifiers' - with filters at the top of the page and the ability to 'Add or remove columns, fields, and specific items'. The underlying Sold Items Details API confirms the grain and the measures: item_name, item_type ('Type of the item (e.g., modifier_item)'), quantity, subtotal ('Subtotal amount for the sold item, excluding taxes'), location_id, order_source, created_date. Shortfall: the only sales measure documented is a tax-exclusive subtotal, with no separate net-of-discount or net-of-refund figure alongside it, and the documented slicing dimensions are location, ordering platform and date - neither the Using Filters guide (article 22530557028251) nor any Reporting API field list mentions a daypart or a revenue-center filter, which follows from Checkmate seeing only digital-channel orders rather than the whole restaurant. https://support.itsacheckmate.com/hc/en-us/articles/22540386187291-Insights-Top-Selling-Items · retrieved 2026-08-04

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

CLAIM: a named organizational hierarchy of at least three levels (enterprise > region/group > location) as a first-class object that REPORTING AND PERMISSIONS can be scoped to, not just a flat list of locations. MIDDLEWARE SCOPE RULING: every object below is Checkmate's own - the Direct Ordering Admin Panel and the Checkmate Portal - not a connected POS's establishment tree. (I checked the one contaminating hit: 'hierarchy' returns 4 in 3 articles and one of them is Revel's own Management Console tree at .../8192460420251, which is NOT Checkmate's and is excluded.) MET (1) THREE NAMED LEVELS AS FIRST-CLASS OBJECTS, at this url: 'Stores: View all stores, filtered by open or closed status or by store group. Store Groups: Group stores by shared attributes such as city, state, owner, or franchisee to manage configurations and reporting more efficiently. Regions: Manage pricing across multiple stores or groups of revenue centers for consistent menu and payment settings.' That is brand > store group > store. MET (2) STORE GROUPS HAVE THEIR OWN CRUD AND ASSIGNMENT SURFACE: 'Grouping locations into Store Groups provides a convenient way to organize and oversee multiple locations. Stores can be categorized by criteria such as market, city, or franchise... Log in to the Direct Ordering Admin Panel. Go to Stores. Select Store Groups. Select Add... A store can be assigned to a specific store group on the store's Settings page' (https://support.itsacheckmate.com/hc/en-us/articles/23709638962971-Organizing-Locations-with-Store-Groups). MET (3) REPORTING IS EXPLICITLY ONE OF THEIR PURPOSES - 'to manage configurations and reporting more efficiently' - which is half of the claim's scoping conjunct. MET (4) THE PORTAL SIDE IS GENUINELY TWO DEEP ABOVE THE LOCATION: Location Tags group 'locations and brands based on various criteria, such as city, region, type' (.../22538023996059) and Tag Collections sit above them - 'Tag Collections... allow[] you to categorize multiple Location Tags into broader groups based on specific criteria such as country, state, or custom-defined attributes', with Create/View/Copy/Edit/Delete/Search and predefined collections auto-generated by country, state/province and POS system (.../23777317088283). SHORTFALLS, numbered. (1) PERMISSIONS SCOPE TO INDIVIDUAL STORES, NOT TO THE GROUPING OBJECTS: 'By default, creating a new user grants access to every store within the brand. The following video shows how to restrict a user's access to specific stores' (https://support.itsacheckmate.com/hc/en-us/articles/26312240204827-Adding-Users-and-Managing-Permissions). Nothing documents granting a user a Store Group, a Region or a Tag Collection. Tags touch permissions only at the edge - 'Creating shared location tags is reserved for users with Admin roles by default' is permission TO MANAGE tags, not permission SCOPED BY tag. (2) THE GROUPING OBJECTS ARE SIBLINGS, NOT ONE NESTED TREE: Store Groups and Regions sit alongside each other under Stores and no article states that a Region contains Store Groups. (3) THE ROLE MODEL IS NOT AN ORG MODEL: five ranked roles (Admin, Catering Manager, Manager, Cashier, Employee) over a named function list (View Catering Summary, Refund Orders, Add Locations, Edit Orders Quick/Full, Cancel Orders, Resend Email to Customer, Confirm Orders without Sending, Show Wait Times Page, Turn Off Location Temporarily). (4) THE EVIDENCE ITSELF IS PARTLY UNREADABLE - see the holes. CONTROLS, tokenised, scripts written to disk: 'location group' = 0, and that zero is about MY vocabulary, not Checkmate's, which is 'store group' (18 hits in 4 articles with 'location tag' and 'tag collection') - running only my words would have manufactured an absence. PUBLISH THE POISON: region|regions|regional = 5 hits in 4 articles and only ONE is a Regions OBJECT (the admin-panel nav line); two are ordinary English ('regional or market conditions', 'same country or region') and two are Location Tag criteria. hierarch(y|ies|ical) = 4 in 3 and only one is organizational (the ROLE ranking); the others are a menu-element parent column and Revel's own tree. 'sub-brand' = 0. Positive controls: Checkmate 799 / 201, order 1,546 / 190, the 9,534 / 377. BOUND CORPUS AND ITS HOLES: href fixpoint re-derived - 172 referenced ids, 14 absent, 0 unlisted published 200s, 0 gated, 14 stale 404s, three fabricated 14-digit controls all 404. Attachment census: 2,521 over 383 articles, 6 non-image - and FOUR OF THE SIX ARE mp4 CLIPS ATTACHED TO THE STORE GROUPS ARTICLE ITSELF, so part of this cell's own evidence is video I cannot read. VIDEO HOLE, NAMED AND DIRECTLY ON THIS CELL: 257 iframes across 161 of 383 articles (42%); the Store Groups article is 493 characters of prose plus one embed, and the permissions article carries FIVE embeds including the very demonstration of restricting a user to specific stores. Shortfall (1) therefore rests on what the prose says the video shows, not on a complete reading, and is recorded as a shortfall of a partial rather than as a zero. FRESHNESS: cited articles are 2026-06-30, 2026-06-10 and 2026-06-09, none in the six bulk re-save seconds I measured across this corpus. https://support.itsacheckmate.com/hc/en-us/articles/26107840524187-Navigating-the-Direct-Ordering-Admin-Panel · retrieved 2026-09-15 adversarially verified

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

multi-location-central-menu-publish

Central menu management pushes to selected channels and locations; a publish/version history showing what, when and by whom is not documented. https://itsacheckmate.com/ · retrieved 2026-08-01

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

multi-location-local-override-policy

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

CLAIM: price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record. SHORTFALLS, numbered. (1) THERE IS NO PER-ITEM PRICE TIER AT ALL, in Checkmate's own words at this url: 'Prices are established directly at the Point Of Sale (POS) systems rather than through the Checkmate Portal. We do not support individual pricing adjustments for items or modifiers on online menus; all prices must originate from the POS. However, the Price Elevation feature allows you to apply a uniform percentage increase to all menu items and modifiers.' The lever is a blanket percentage over the whole menu, plus rounding. (2) THE DAYPART CONJUNCT FAILS, AND IT IS A MIDDLEWARE SCOPE TRAP: the only daypart-varying pricing in the corpus sits inside Destination-Based Pricing - 'Prices vary by menu based on seasons, celebrations, or peak business hours (e.g., standard 10% elevation during regular hours and 15% during peak hours)' - and that method's own definition is that the prices ARE SET IN THE POS and merely pulled in, on ONE POS: 'Destination-Based Pricing: Customized prices for ordering platforms are set in the POS and pulled into the Checkmate system (available on Brink POS only)' (https://support.itsacheckmate.com/hc/en-us/articles/29390712942491-Pricing-Methods). That is the connected POS's capability, not Checkmate's, and counting it would be exactly the middleware error this cell is prone to. (3) LOCATION-GROUP PRICING IS ONE SENTENCE: Direct Ordering's admin nav names a 'Regions: Manage pricing across multiple stores or groups of revenue centers for consistent menu and payment settings' object (.../26107840524187) with no configuration article behind it. (4) DYNAMIC PRICING IS A BOLT-ON, via a third-party integration (Juicer) added to a Checkmate account, which the atlas's native-capability standard excludes from a yes. (5) GRADE-A CORROBORATION OF THE LIMIT, from a corpus the prior pass did not open - Checkmate's public OpenAPI FAQ says of per-fulfilment pricing: 'what I have just described above is part of a custom integration that we have with a single, large platform. This is not inherently available in our OpenAPI integration, and there is no out-of-the-box way to support different menus or pricing' (https://openapi-itsacheckmate.readme.io/page/faq). MET, and it is why this is not a zero: THE ORDER-CHANNEL CONJUNCT IS GENUINELY SATISFIED WITHOUT DUPLICATING THE ITEM RECORD. 'Pricing Methods' enumerates three named methods, of which 'Variable Pricing: POS prices can be elevated by customizing/applying variable price elevation percentages individually for each live ordering platform based on the restaurant's requirements', worked as 'Different elevations applied across different platforms (e.g., 0% on DoorDash and 15% on UberEats)'. The mechanism is documented in detail with rounding rules - 'if an item's menu price is $10 and you wish to elevate this price by 20% on the ordering platform, the item price will be adjusted to appear as $12', with Traditional Rounding or Round-Up, to the whole dollar or to $0.99, and an opt-out for items under $1.00 (.../25529046754459-Menu-Price-Elevation-and-Rounding). The structural corroboration is in Checkmate's own API: the menu is fetched per channel - GET /api/v2/menu/{order_source}, where order_source is 'Name of the ordering platform' (https://openapi-itsacheckmate.readme.io/reference/getting-started-with-your-api-1). CONTROLS, tokenised, scripts written to disk: 'price zone' = 0, 'price tier|pricing tier' = 0, daypart = 0 - and that trio of zeros is about MY vocabulary; Checkmate's own words are 'price elevation' and 'destination-based pricing', which return 65 hits in 22 articles. CORRECTION TO THE PRIOR PASS'S POISON NOTE: it said the token 'zone' is unusable because it matches 'timezone'. Tokenised with word boundaries it does not - zone returns 13 hits in exactly 2 articles, and the real poison is different: the hits are 'local time zone' (spaced, in the Sold Out Frequency Report) and DELIVERY ZONE, a delivery-radius object with a Circular Radius or Custom Shape (https://support.itsacheckmate.com/hc/en-us/articles/26310661867035-Setting-Up-Delivery-Zones). A reader who saw 'Delivery Zone' and thought 'price zone' would have faked this cell. Positive controls: Checkmate 799 / 201, order 1,546 / 190, the 9,534 / 377. BOUND CORPORA AND HOLES: help-centre href fixpoint re-derived - 172 referenced ids, 14 absent, 0 unlisted published 200s, 0 gated, 14 stale 404s, three fabricated 14-digit controls all 404; 2,521 attachments, 6 non-image, none pricing-related. VIDEO HOLE, NAMED: 257 iframes in 161 of 383 articles (42%), and 'Updating Menu Prices' itself carries an embed, so the configuration surface may be richer than the prose shows - another reason this is a partial rather than a stronger negative. Second corpus: all 15 pages of Checkmate's public developer hub, where 'price zone|price tier|pricing tier|daypart' = 0. FRESHNESS: Updating Menu Prices 2025-06-06, Pricing Methods 2025-06-11, Price Elevation and Rounding 2025-06-11, all outside the six bulk re-save seconds I measured. https://support.itsacheckmate.com/hc/en-us/articles/8127887582619-Updating-Menu-Prices · retrieved 2026-09-15 adversarially verified

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

REPLACES an undated first-pass placeholder that said 'Site references a Developer Marketplace but routes to a Partner With Us contact flow; no publicly readable API reference was found' -- while three cells in this same record cite openapi-itsacheckmate.readme.io/reference/ pages at grade A, retrieved 2026-08-04, including extensibility-oauth-partner-apps quoting the portal's own OAuth statement. Re-fetched 2026-09-01: HTTP 200 anonymously; robots.txt (231 b) allows / and bars only readme.io internals (/cdn-cgi/ carried as a must-refuse control and correctly refused). The reference renders its content server-side without a session -- the 'Get Menu' page shows its method and URL in the open ('get https://sandbox-api.itsacheckmate.com/api/v2/menu/{order_source}', 'Returns the latest menu for your location') and its navigation enumerates the whole v2.2 surface: Onboarding & OAuth 2.0 Flow (Introduction, Scopes, App Registration, Authorisation Request, Bulk Special Case, Activating your Location), Open API v2.2 APIs (Get Token / Refresh Token, Get Token Details, Get Location, Activate Location, Get Menu, Submit Order / Group Order), an Error Library, a Webhooks section, and a Postman collection. SHORTFALL, recorded not scored: 'Log In' appears in the site chrome and the Recent Requests panel says 'Log in to see full request history' -- that gates request logging, not the reference. https://openapi-itsacheckmate.readme.io/reference/getting-started-with-your-api-1 · retrieved 2026-09-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

The Marketplace for Developers portal states 'ItsaCheckmate uses the OAuth 2.0 protocol for authentication and authorization'. The grant is operator-initiated inside the merchant's own portal: the restaurant user opens the Market Place page, sees the third-party application listed with state 'Authorization Required', clicks Authorize and is shown a consent popup saying the app will have access to the location provided in the request, its menus, and the ability to place orders on that location; the app then receives a single-use verification code at its redirect URI and exchanges it for an access token plus refresh token. Grants are per location - 'For every location you want access for, you need to generate seprate [sic] pair of tokens' - and individually revocable: 'At any point of time after the authorization state has been moved to In progress, you can click Disconnect to destroy your current access tokens and start over'. Resource scopes are enforced, not merely described: the Get Menu endpoint states 'You can only access this API if you have an access token issued with the scope menus' and Submit Order 'with the scope orders'. No shared static API key path appears anywhere in the v2.2 reference. https://openapi-itsacheckmate.readme.io/reference/authorisation-request · retrieved 2026-08-04

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

extensibility-webhooks-push

CLAIM: the platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling. THE PROPOSED 'no' IS REJECTED: it rested on the premise that 'Checkmate publishes exactly one customer-facing programmatic interface, the Reporting API', and that premise is false. ItsaCheckmate runs a public developer programme with an anonymous, robots-allowed OpenAPI hub at openapi-itsacheckmate.readme.io, linked from www.itsacheckmate.com/onboarding/marketplace-developer-onboarding as 'Checkmate OpenAPI Documentation'; I fetched all 15 pages in its llms.txt (199,443 bytes). Checkmate pushes, and documents how. MET (1) CHECKMATE POSTS LIVE ORDERS TO A PARTNER-CONFIGURED ENDPOINT. Its Order Receivers programme exists so that 'companies that do not neatly fall into either of those categories' can 'receive copies of orders sent to locations' POS systems... for last-mile delivery, loyalty, or other use cases that involve receiving live order data'. The contract is a webhook in all but name: 'The URL endpoint Target for Relayed Orders on the OR Server should be configured for POST requests and require an Authorization Token in the Header as such: Authorization: Basic <token>'; a conforming call 'should return a 200 Success response. If the Authorization Token check fails a 401 Unauthorized Error should get returned. All other issues with the payload structure, content, etc, should cause the return of a 400 Bad Request Error.' The Target URL and Authorization Token are set by the partner at platform.itsacheckmate.com/order_receivers#config, and a full order packet schema is published (order_id, order_created_at, order_source enum uber/postmates/doordash, location, customer, items, modifiers, payment). MET (2) A SECOND REAL WEBHOOK EXISTS: the Update Notice Webhook - 'We will communicate to Ordering Platforms that a Menu needs to be updated via an Update Notice Webhook packet... Our developer partners will need to set-up and maintain an Update Notice Webhook Target URL on their server' (https://openapi-itsacheckmate.readme.io/reference/update-notice), with an HTTPS POST contract, JSON payload {location_id}, expected 200, and optional HTTP Basic auth via a partner-chosen API Key and Secret (.../reference/webhook-details-and-authentication-overview). Neither interface is polling. SHORTFALLS, numbered, and they are why this is not a yes - every one is Checkmate refusing the claim in its own voice. (1) ONLY 'CREATED' IS PUSHED. Asked directly, 'Also I see webhook is applicable only for menu updates. Will you send the webhook pushes for order updates also?', Checkmate answers: 'We have a webhook for menu updates... For submitting orders to ItsaCheckmate, there is a separate endpoint... We respond with a success (2xx) for the above order submission, confirming success. NO FURTHER ORDER UPDATES ARE DELIVERED BACK TO THE ORDERING PLATFORM' (https://openapi-itsacheckmate.readme.io/page/faq). Modified, paid, voided and refunded are not pushed. (2) CANCELLATION IS EXPLICITLY REFUSED: 'We currently do not do this for any ordering platforms (send a cancellation update or pass a canceled status back to the POS). Once we deposit the order into the POS we do not (nor do we necessarily have the ability to) change the status of that order in the POS.' (3) ORDER-ERROR PUSH IS REFUSED: 'Will we be notified of an order error, with detail, via a webhook message? A: Any errors will be manually handled by our Error Handling team and you won't be notified about it in developer environment.' (4) IT IS ROADMAP, NOT PRODUCT: 'Q: Any specific reasons why you don't have order update webhooks?... A: ... We hope to have more options around this in the future... We do have plans in the future but it is limited by POS.' (5) THE RETURN LEG IS INBOUND ONLY AND THE RELAY IS UNBUILT: order status transitions (accepted, driver_assigned, order_picked_up, order_delivered, order_cancelled) are POSTed BY the partner TO Checkmate at app.itsacheckmate.com/or_status_transition, and Checkmate says only that it 'intend[s] to eventually implement a relay of that information back to the Ordering Platforms. This should happen soon.' (6) THE PUSH IS GATED BEHIND AN APPROVED PARTNERSHIP, not self-serve: an Order Receiver must submit an onboarding form and be approved, and in production 'our team will set this up for you'. (7) THE CUSTOMER-FACING INTERFACE REMAINS PULL-ONLY ON A BATCH CADENCE: the Reporting API is 'a secure, brand-specific API link from where you can access the data as required', with 'Internal data updates every hour' and 'Operational performance data is updated every 48 hours' (https://support.itsacheckmate.com/hc/en-us/articles/30504470828187-Reporting-API). CONTROLS, tokenised, scripts written to disk. Over the help centre: webhook(s) = 6 hits in 3 articles and NOT ONE is Checkmate pushing order events - four are the Statuspage incident-subscription control ('Webhook - Enter your website and email address to receive updates via Webhooks', .../25996726444059 and .../26102758591003) and two are the TOAST 86 WEBHOOK, which is Toast's webhook that Checkmate CONSUMES ('The Toast 86 Webhook detects when an item is marked Out of Stock and automatically syncs the update to all connected ordering platforms', .../8166742779419) - a capability of the connected POS, not of Checkmate. callback = 0, HMAC = 0, signature = 0. 'push notification' = 15 hits in 5 articles, all guest-facing campaign pushes - a homonym sitting inside this cell's own id. Over the developer hub: webhook = 27 hits in 4 of 15 pages, poll/polling = 0, callback = 1 (an OAuth redirect). Positive controls: help centre Checkmate 799 / 201, order 1,546 / 190, the 9,534 / 377; hub Checkmate 15 / 3, order 130 / 14. BOUND CORPORA AND HOLES. Help centre fixpoint re-derived: 172 referenced ids, 14 absent, 0 unlisted 200s, 0 gated, 14 stale 404s, three fabricated 14-digit controls all 404; 2,521 attachments, 6 non-image, no PDFs. VIDEO HOLE, NAMED: 257 iframes in 161 of 383 articles (42%). Developer hub hole, NAMED: its llms.txt is a STRICT SUBSET - the webhook authentication page is referenced from a listed page but is not itself listed, so the hub is a floor and other unlisted pages may exist. I also probed developers./docs./developer./documentation.itsacheckmate.com (all DNS-dead) and api.itsacheckmate.com (a sign-in wall). https://openapi-itsacheckmate.readme.io/page/order-receivers · retrieved 2026-09-15 adversarially verified

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

extensibility-webhook-reliability

Not scored by this record.

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

extensibility-order-injection-api

Not scored by this record.

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

No on-terminal software; order entry continuity is the integrated POS vendor's responsibility. https://itsacheckmate.com/integrations/ · retrieved 2026-08-01

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

reliability-offline-card-auth

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

Checkmate does drive kitchen printers and KDS screens — the Portal FAQ heading is 'Do tickets print or show up on KDS screens instantly?' — but it drives them through the integrated POS from its own cloud, with no local component to keep routing while offline. The documented failure path is human, not device: 'If an order cannot be sent through our integration, our team will contact you via pre-established channels to ensure you are aware of the order and can complete it before the driver arrives.' The Clover printing path is likewise triggered only 'once the order is injected into the POS system', and a print that does not land within two minutes produces an email plus a web receipt, with the ticket reprinting only 'when the printer is back online' (article 8194923674139). Supersedes an earlier rationale that wrongly asserted Checkmate has no kitchen printing or KDS product at all; see reliability-printer-fallback. https://support.itsacheckmate.com/hc/en-us/articles/26977712762907 · retrieved 2026-08-04

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

reliability-printer-fallback

The alerting half is documented; the automatic failover half is not. Clover Native Printing 'triggers a print to the order printer once the order is injected into the POS system', 'sends a failed printing email to the user if the job is not printed within two minutes of the request', and 'informs the user about the unavailability of the printer to print the order receipt via email. Also, it provides basic order details and a link to view the HTML version of the order receipt by selecting the Web Receipt... When the printer is back online, the order receipt prints as requested.' Shortfall: the recovery path is an email alert plus a web receipt and a deferred reprint, not an automatic re-route to a backup printer or KDS station; it is documented only for the Clover integration; and for other POS the ticket-routing guidance sends the operator into the POS back end instead ('Ensure that all items in your integrated menu(s) have the correct Prep Station assigned to them', article 8159680010267). Orders that cannot be injected at all fall back to human outreach rather than a device: 'If an order cannot be sent through our integration, our team will contact you via pre-established channels' (Portal FAQs, article 26977712762907). https://support.itsacheckmate.com/hc/en-us/articles/8194923674139-Clover-Native-Printing · retrieved 2026-08-04

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

Site claims 'flexible contracts' but publishes no contract terms, no auto-renewal term, and no cancellation notice window. https://itsacheckmate.com/ · retrieved 2026-08-01

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

Site claims 'transparent fees' but publishes no dollar figures anywhere; engagement is via contact sales only. https://itsacheckmate.com/ · 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. SHORTFALLS, numbered. (1) NO HARDWARE PRICE IS PUBLISHED ANYWHERE. I refetched www.itsacheckmate.com/pricing (HTTP 200): both tiers carry only a 'Request Pricing' button under 'No setup fee, easy to get started / Simple pricing that scales with you', with no dollar figure for hardware or software; the record's pricing.transparency is quote-only. (2) THE ONLY DOCUMENT STATING PURCHASE TERMS IS AN EXPIRED PROMOTIONAL FLYER WHOSE SUBJECT IS A RESELLER, NOT THE RESTAURANT. The Kiosk Referral Program page's Terms & Conditions read 'Hardware Purchase: The reseller will purchase the kiosk hardware at the specified "buy price" from Checkmate. However, the reseller retains discretion in setting and selling the hardware to restaurant brands at an appropriate price point', alongside '25% off Checkmate kiosk hardware - resell at market value' and 'Flat 25% revenue share of the monthly $150 software fee in perpetuity' - but the same page states 'Promo Duration: This offer is valid for a limited time only and will expire on November 30, 2024', and the only published number on it ($150/month) is for SOFTWARE (https://www.itsacheckmate.com/kiosk-reseller-promotion). By the flyer's own logic the restaurant's price is set by the reseller and is therefore definitionally unpublished. (3) THE HELP CENTRE NEVER DISCUSSES HARDWARE COMMERCE AT ALL, so the purchase evidence had to come from marketing - see the controls. (4) NO WARRANTY OR TERMS-OF-SALE DOCUMENT IS PUBLISHED, unlike Bite: warrant(y|ies) = 0 across all 383 articles and there are no PDFs in the entire attachment corpus. MET, and it is why this is not a zero or an unknown: HARDWARE IS SOLD OR BROUGHT BY THE OPERATOR, NOT LEASED, and Checkmate says so on a live page - 'Secure and hardware agnostic... Use our hardware offerings, or bring your own, you decide!' and 'Works with multiple form factors and hardware types' (this url). The parts are named commodity third-party devices an operator can source: 'Modular Configuration Options: Wall Mounted and Countertop Kiosk, Free Standing; Spec - Kiosk Furniture; Spec - 21.5" Android All-in-One Touchscreen; Spec - Ingenico Lane 3000; Spec - Bezel Mounted Scanner; Spec - Epson TMT88VII' (https://support.itsacheckmate.com/hc/en-us/articles/29143769712027, Digital Menu Boards & Kiosk), with per-device maintenance articles for the Microtouch screen, the Ingenico Lane 3000 and the Epson TMT88vii. A separate first-party statement bounds the hardware surface honestly: for the third-party ordering product Checkmate ships nothing at all - 'We do not provide any tablets or any other hardware to the restaurant' (https://openapi-itsacheckmate.readme.io/page/faq). CONTROLS, tokenised word-boundary AND left-boundary stem, comments stripped before tags, scripts written to disk, over all 383 article bodies: leas(e|ed|ing) = 0, rent(al|ed|s)? = 0, warrant(y|ies) = 0, 'price list' = 0, purchas(e|ed|ing)|buy = 18 hits in 13 articles (all guest-side purchases, none hardware). Same controls over all 15 pages of Checkmate's public developer hub: lease = 0, rent = 0. THE READER ARTEFACT THE PRIOR PASS CAUGHT AND I CONFIRM: 'hardware' returns 0 across 2,052,897 raw bytes of article BODIES while the article TITLED 'Hardware Technical Specs' sits in the index - the corrected statement is that the word appears zero times in bodies and once in the title index, and my own count reproduces that. Positive controls: Checkmate 799 hits / 201 docs, order 1,546 / 190, the 9,534 / 377. GRADE: C, because every load-bearing document is a marketing or promotional page rather than a customer master agreement; there is no grade-B commercial source to cite. BOUND CORPORA AND HOLES: help-centre href fixpoint re-derived - 172 referenced ids, 14 absent, 0 unlisted published 200s, 0 gated, 14 stale 404s, three fabricated 14-digit controls all 404. Attachment census: 2,521 attachments over all 383 articles, only 6 non-image (two 435-byte text/plain, four mp4), NO PDFs - so unlike Bite there is no attached terms-of-sale or spec sheet to read, and the 'Spec -' lines resolve to images, not documents. VIDEO HOLE, NAMED: 257 iframes across 161 of 383 articles (42%). Marketing corpus bound to the 350 URLs in www.itsacheckmate.com/sitemap.xml, of which I read /pricing, /solutions/kiosk, /onboarding/kiosk-onboarding and /kiosk-reseller-promotion; the kiosk onboarding page is a lead form with no commercial terms. https://www.itsacheckmate.com/solutions/kiosk · retrieved 2026-09-15 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.