OpenTable

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

OVERTURNED from an uncited `no`. OpenTable has a real modifier engine, and it reaches different depths on its two menu paths. In the NATIVE editor the depth is one: the operator creates a modifier group, adds each 'Modifier name, price, and tax percentage', can 'Check the box if guests are required to select from this modifier group' and 'Add a minimum and maximum number of modifiers that a customer can select', then assigns the group to a menu item — so the forced-selection flag and independent min/max the claim asks for are both present, but a modifier group can only be attached to an ITEM. The Access Menus response confirms the stored native shape: modifier objects carry only id, name, ordinal and price. The PARTNER-PUBLISHED path is deeper — in the Menus webhook schema a Modifier itself carries `modifierGroups`, 'a List of ModifierGroup Ids and their respective positions eligible for the modifier', and every ModifierGroup at every level carries its own minChoices/maxChoices, which satisfies the three-levels test structurally. Partial rather than yes because that depth is reachable only by importing a menu OpenTable cannot then edit ('You can only edit menu items created in OpenTable for Restaurants, changes can't be made to imported items') and because no OpenTable channel fires an order against these menus at all — they render on the restaurant's profile page. https://docs.opentable.com/ · retrieved 2026-09-08

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

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

UPHELD, now cited, and settled on the schema's shape rather than on a keyword count. Item sizes do exist on the partner-publishing path: an Item may carry `sizes` when `priceMetadata.priceType == SIZE_PRICE`, and each ItemSize has its own priceMetadata. But price never crosses from that axis to the modifier. A Modifier carries exactly one `priceMetadata`, with no reference to the parent item, no reference to an ItemSize, and no matrix construct anywhere in the schema; the only per-context multiplier, `multiplicationFactor`, applies to PreModifiers and is not keyed to size. OpenTable's native menu is flatter still — its items have no size dimension at all and its modifiers carry a single `price.amount`. Pricing one topping differently per parent size therefore requires duplicating the modifier, which is what the claim excludes. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://docs.opentable.com/ · retrieved 2026-09-08

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

menu-pricing-fractional-placement

Not scored by this record.

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

menu-pricing-half-and-half-rule

Not scored by this record.

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

menu-pricing-topping-quantity-tiers

OVERTURNED from an uncited `no`. The Menus webhook schema documents PreModifierGroup and PreModifier objects, attached to a modifier group through its `preModifierGroup` field. A PreModifier carries `displayMode`, 'Used to determine how the premodifier should be displayed along with the modifier. Should be - PREFIX or SUFFIX', and its priceMetadata carries `multiplicationFactor`, 'Applicable for PreModifiers. This will be used if minPrice/maxPrice is not set for premodifiers.' A named intensity token rendered as a prefix or suffix on the modifier, priced by a multiplier rather than by a second line, is exactly the light/regular/extra tiering the claim describes, and it is distinct from adding the modifier twice. Partial, not yes: the mechanism exists only in the partner-menu ingestion schema — `preModifier`, `multiplicationFactor` and `SIZE_PRICE` occur in that one document and nowhere else in the corpus — the native menu editor offers no tier control, and the tiers are display-only because no OpenTable channel takes an order. https://docs.opentable.com/ · retrieved 2026-09-08

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

menu-pricing-size-style-matrix

Not scored by this record.

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

menu-pricing-included-allowance

Not scored by this record.

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

menu-pricing-combos

Not scored by this record.

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

menu-pricing-upsell-prompts

Not scored by this record.

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

menu-pricing-86-propagation

Not scored by this record.

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

menu-pricing-countdown-auto-86

Not scored by this record.

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

menu-pricing-dayparting

Not scored by this record.

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

menu-pricing-channel-price-books

Not scored by this record.

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

menu-pricing-dual-pricing

Not scored by this record.

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

menu-pricing-versioning-effective-dates

Not scored by this record.

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

menu-pricing-franchise-hierarchy

Not scored by this record.

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

menu-pricing-allergen-nutrition

Not scored by this record.

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

menu-pricing-recipe-linkage

Not scored by this record.

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

menu-pricing-3p-menu-push

Not scored by this record.

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

menu-pricing-dynamic-pricing

Not scored by this record.

The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator

payments-processor-choice

Not scored by this record.

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

payments-published-rates

Not scored by this record.

Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator

payments-dual-pricing

Not scored by this record.

Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator

payments-surcharge-guardrails

Not scored by this record.

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

payments-emv-nfc

UPHELD, now cited. OpenTable ships no payment terminal of its own, so there is no first-party terminal to accept EMV or NFC on. Payments run through the operator's own gateway account, and OpenTable takes the e-commerce side of it only: to connect FreedomPay the restaurant must 'work directly with FreedomPay' to 'Set up any required hardware and terminals' and to 'Receive your MID for e-commerce credentials, Store ID, Terminal ID', and the article states 'To integrate FreedomPay with OpenTable, your FreedomPay account must be set up for e-commerce' and 'OpenTable does not use FreedomPay's hosted payment controls (HPC).' Card-present work stays on the processor's side: 'Refunds for FreedomPay transactions are managed in the FreedomPay Enterprise Portal or your payment terminal, depending on your FreedomPay setup.' The terminal is the merchant's and the processor's, never OpenTable's. `EMV`, `contactless`, `tap to pay` and `card reader` each occur zero times. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://support.opentable.com/s/article/Manage-FreedomPay-and-OpenTable?language=en_US · retrieved 2026-09-08

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

Positive evidence of absence, from OpenTable's own help centre. 'Gifts: Choose Your Gift Card Management Service' (updated 2025-12-17) opens 'To start selling gift cards on OpenTable, you'll need to choose a gift card processor' and states 'For restaurants, OpenTable Gifts will be processor agnostic', then enumerates the alternatives operators must buy instead — GiftRocker, Paytronix, Swipeit, Synergy and Vantiv/Worldpay, with each vendor's monthly fee. The companion article 'Welcome to the New OpenTable Gifts' confirms the product is a marketing listing only: 'When a customer selects your restaurant, they click on Buy Gift Card which takes them to your gift card sales page. Don't have a gift card sales page? Find out more about gift card vendors to pick the right one for you.' OpenTable issues no card, holds no balance and performs no redemption; there is no first-party gift card to track a balance on. https://support.opentable.com/s/article/Changes-to-OpenTable-Gifts-Those-who-use-us-for-processing-and-gift-card-management-services?language=en_US · 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

CLAIM: voids, refunds, discounts and no-sales require role-based authorization (manager PIN or approval) and write to an immutable audit log naming the approver. VERDICT: unknown -> partial/B. OpenTable is not a POS, so voids and no-sales do not exist in its product; the only money movement it controls is reservation deposits, prepaid experiences and no-show charges. For those, the authorization half exists as an opt-in gate. SURFACE: support.opentable.com Aura KB (186 live English articles; not a census - 52 hrefs have no public version). EVIDENCE: 'Passcode protection for key features' (last published 2026-02-20): 'Set up a restaurant passcode and restrict specific actions to employees who have the passcode.' 'Enter a four-digit passcode'; selectable actions include 'Waive payment for prepaid experiences or deposits: choosing not to require an in-house guest the fee for experiences or reservation deposits.' and 'Refund deposit payments: refunding deposits placed for reservations in OpenTable for Restaurants.' Refund path it gates ('Manage your Stripe integration'): 'Select the reservation with the deposit to refund. Select the three dots in the top right. Select Issue refund.' - FreedomPay/CardConnect refunds happen in the processor's own dashboard. Attribution: 'Set up and manage staff action logging': 'This requires staff to select their name in a pop-up window before completing actions that you designate.' and 'Select the clock icon in the reservation navigation to view the reservation history. View a record of the reservation changes and the staff members who made them.' SHORTFALLS: the passcode is ONE shared four-digit restaurant code, not a per-manager PIN or role, so it cannot identify an approver; staff action logging identifies the actor by self-selected name, not the approver, and is not stated to cover refunds; the log is never called immutable; discounts are not gated (the 'Custom roles and user permissions' article's payment-adjacent permission is 'Policies', which creates booking policies incl. deposits); voids and no-sales are not applicable. Retrieved 2026-09-16. https://support.opentable.com/s/article/passcode-protection?language=en_US · retrieved 2026-09-16 adversarially verified

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

payments-chargeback-tooling

Not scored by this record.

Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator

payments-card-on-file

Not scored by this record.

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

payments-payout-timing

Not scored by this record.

A single account can route settlement funds to different bank accounts per location or legal entity (separate MIDs or split settlement) under unified reporting. differentiator

payments-multi-entity-routing

Not scored by this record.

Vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance / P2PE listing available to merchants on request.

payments-p2pe-pci4

Not scored by this record.

Product includes a native in-house driver module: drivers are first-class entities with clock-in/out, assignment state (in-store / on-run / returning), and per-driver run history reportable from the POS itself (not via a third-party add-on).

delivery-driver-roster

UPHELD, now cited, and not a vacuous pass — OpenTable did run delivery and takeout surfaces and has withdrawn both. The help centre states 'OpenTable's delivery partner integration options will be discontinued beginning March 18, 2025' and 'Delivery partner integrations on OpenTable restaurant profiles will be discontinued on March 18, 2025, and diners will no longer be able to view delivery partner integrations.' Even before withdrawal the feature was a link-out to a third-party delivery partner's page, never an in-house driver module: no driver entity, assignment state or run history appears anywhere. `driver` and `dispatch` are absent from the operator corpus. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://support.opentable.com/s/article/OpenTable-Delivery-FAQ-s-for-Restaurants?language=en_US · retrieved 2026-09-08

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

delivery-dispatch-board

UPHELD, now cited. There is no dispatch surface because there is no delivery operation to dispatch: OpenTable's only delivery function was displaying third-party partner links on the restaurant profile, and 'Delivery partner integrations on OpenTable restaurant profiles will be discontinued on March 18, 2025, and diners will no longer be able to view delivery partner integrations.' Its own ordering channel is gone too — 'Restaurant Takeout management was deprecated on July 1, 2024; the last day diners were able to order takeout through OpenTable was on June 1, 2024.' With no orders in the system there is nothing undispatched to show, no driver availability to track and no run batching. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://support.opentable.com/s/article/OpenTable-Delivery-FAQ-s-for-Restaurants?language=en_US · retrieved 2026-09-08

Dispatch includes a live map view with geocoded stops and system-generated route sequencing (turn order optimization) for a multi-stop run, not just a static address list. differentiator

delivery-route-map

Not scored by this record.

Captures live driver GPS position from a driver-facing mobile app and surfaces it back to the dispatch screen. differentiator

delivery-driver-tracking

Not scored by this record.

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

delivery-zones-polygon

Not scored by this record.

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

delivery-zone-pricing

UPHELD, now cited. Delivery zones, fees, order minimums and promise times require the vendor to own the delivery order, and OpenTable does not: takeout ordering was withdrawn — 'Restaurant Takeout management was deprecated on July 1, 2024; the last day diners were able to order takeout through OpenTable was on June 1, 2024' — and the delivery partner integration that replaced nothing was itself discontinued on 2025-03-18. No zone, fee, minimum or quoted-time configuration exists in the operator product. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://support.opentable.com/s/article/Offering-Pickup-Ordering-through-OpenTable?language=en_US · retrieved 2026-09-08

Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.

delivery-address-validation

Not scored by this record.

Tracks per-delivery driver compensation inputs — mileage or distance driven per run, per-delivery flat reimbursement, and driver-retained tips — and exports them to payroll as separate reimbursement vs. wage lines. differentiator

delivery-driver-comp

Not scored by this record.

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

delivery-cash-reconcile

Not scored by this record.

Can hand a first-party order to an on-demand courier marketplace (DoorDash Drive, Uber Direct, Nash, Relay or equivalent) natively from the POS, with the courier quote and status returning into the order record.

delivery-daas-dispatch

Not scored by this record.

Supports hybrid dispatch: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. differentiator

delivery-daas-fallback

Not scored by this record.

Offers direct, first-party certified API integrations with DoorDash, Uber Eats, and Grubhub marketplaces (vendor-owned, not solely resold through Otter/Deliverect/Chowly/ItsaCheckmate middleware). differentiator

delivery-3p-direct-integration

Not scored by this record.

Third-party marketplace orders inject automatically into the POS as normal tickets that fire to KDS/printers without tablet re-keying or manual accept.

delivery-3p-injection

Not scored by this record.

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

delivery-menu-push

Not scored by this record.

Marking an item or modifier 86'd in the POS pushes item-level out-of-stock status to connected third-party channels in near real time, and restores it on availability (DoorDash requires item and item-option 86ing of new POS partners).

delivery-86-sync

Not scored by this record.

Store can be paused/deactivated on each connected third-party marketplace from inside the POS with a timed auto-reactivation, rather than only from each marketplace's own tablet or portal.

delivery-store-pause

Not scored by this record.

Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. differentiator

delivery-3p-reconciliation

Not scored by this record.

Vendor exposes integration health to the operator — failed/rejected order injections, connection status per channel, and alerts on failure — rather than failing silently. differentiator

delivery-injection-error-visibility

Not scored by this record.

Guests receive a branded order status / driver tracking page or SMS link on the restaurant's own domain for first-party delivery orders, driven by real order and driver state.

delivery-tracking-page

Not scored by this record.

Quoted delivery promise times adjust dynamically from current kitchen load, driver availability, and zone drive time, rather than a fixed per-store constant. differentiator

delivery-promise-time

Not scored by this record.

Vendor documents explicit offline behavior for delivery: whether cash delivery orders, driver assignment, and driver settlement continue during an internet outage.

delivery-offline-behavior

Not scored by this record.

Vendor ships a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission.

digital-first-party-web

CLAIM: vendor ships a first-party, commission-free web ordering site on the restaurant's brand/domain that writes orders into the POS. VERDICT: unknown -> no/B. This `no` does NOT rest on an absence count; it rests on the vendor's own withdrawal notices plus the identity of the only ordering product it still points to. EVIDENCE: article titled 'Takeout ordering through OpenTable: Discontinued July 1, 2024' (ArticleNumber for slug Offering-Pickup-Ordering-through-OpenTable, last published 2024-08-19): 'Restaurant Takeout management was deprecated on July 1, 2024; the last day diners were able to order takeout through OpenTable was on June 1, 2024.' and 'July 31, 2024: Takeout will be removed from OpenTable for Restaurants.' Companion article 'Link delivery partners and add takeout details to your OpenTable profile - Discontinued March 18, 2025': 'Delivery partner integrations on OpenTable restaurant profiles will be discontinued on March 18, 2025'. What remains is a partner: 'OpenTable and Bbot' (last published 2026-06-17): 'Bbot is a digital ordering platform', set up via 'Integrations. Select Digital Ordering in the panel on the left. Select the Bbot tile.', with support at 'support@bbot.menu' and 'Emailing Bbot's Support team won't connect you to the OpenTable Support Team.' COUNTER-QUOTE a reviewer should weigh: the same article says 'If you decide to proceed with digital ordering offered by OpenTable, you can easily sign up through OpenTable for Restaurants' - OpenTable resells/refers it, but it is operated and supported by Bbot. Bbot is not OpenTable's: the article's 'Bbot Setup Knowledge Base' link, central.bbot.menu, now 301s to https://tableside-help.doordash.com/ (DoorDash). Menu partners listed for online ordering are likewise third parties ('Deliverect ... streamline your online ordering process'; 'Popmenu ... online ordering'). CONTROLS over the 186 live KB articles (tokenised, word-boundary, case-insensitive): 'order online' 0, 'order ahead' 0, 'commission-free' 0, 'pick-up' 0; 'pickup' 2 (both the discontinuation articles); 'online ordering' 1 (Deliverect, menu-partner article); 'digital ordering' 1 (Bbot); 'online order(s)' 3 (Deliverect; a Toast deposit-import quirk 'The system thinks this is an online order'; Maple voice AI). POISON: 'order(s)' matches 53 articles, dominated by 'in order to' and 'sort order' (not tallied individually). The anonymous docs.opentable.com Postman collection (1.49 MB, Booking/CRM/Directory/Menus/POS/Reviews/Sync APIs) has 0 'takeout' and 0 'online order'. BOUND: the KB is not a census (52 hrefs without a public version); the verdict is carried by the positive discontinuation statements, which absence in the remainder cannot contradict. www.opentable.com robots.txt names Claude-User and Claude-SearchBot, so the marketing /restaurant-solutions/products/features/digital-ordering/ page was NOT fetched. Retrieved 2026-09-16. https://support.opentable.com/s/article/Offering-Pickup-Ordering-through-OpenTable?language=en_US · retrieved 2026-09-16 adversarially verified

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

digital-menu-single-source

UPHELD, now cited, and the reason is sharper than the record’s old "not a POS" framing. OpenTable does hold a real menu record — a native builder with an Item Library, categories, modifier groups and per-item price and tax — but that record feeds exactly one destination, the restaurant's OpenTable profile page: 'Toggle the option in the Display column to make the menu visible on your OpenTable profile page.' There is no first-party ordering channel for it to propagate to, because takeout was withdrawn on 2024-07-01. It is not the POS record either: menus are typed into OpenTable, imported by AI from a PDF, or pulled from Popmenu, Storekit, SinglePlatform, Yext or Toast, and imported items are frozen — 'You can only edit menu items created in OpenTable for Restaurants, changes can't be made to imported items.' Menu maintenance is therefore duplicated by construction, which is the condition the claim exists to detect. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://support.opentable.com/s/article/How-To-Update-Your-Menus-in-GuestCenter?language=en_US · retrieved 2026-09-08

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

digital-native-app

Not scored by this record.

Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels.

digital-account-saved-payment

CLAIM: guests can create an account with saved addresses, tokenized saved payment methods and one-tap reorder across FIRST-PARTY ordering channels. VERDICT: unknown -> no/B, dependent on digital-first-party-web: OpenTable has had no ordering channel of its own since takeout was withdrawn ('Restaurant Takeout management was deprecated on July 1, 2024; the last day diners were able to order takeout through OpenTable was on June 1, 2024.' / 'July 31, 2024: Takeout will be removed from OpenTable for Restaurants.'), so there is no order to reorder and no first-party ordering checkout to save a card to. The digital ordering product it refers restaurants to, Bbot, is a partner whose help centre now redirects to DoorDash (central.bbot.menu -> tableside-help.doordash.com). What does exist is adjacent and does not satisfy the claim: the restaurant membership programme has a guest sign-up link ('Copy sign up link') but carries no saved payment or reorder; card storage is on OpenTable's consumer network for reservation holds and deposits ('Manage your Stripe integration'), not a restaurant-branded ordering account. CONTROLS over 186 live KB articles: 'reorder' 3 (all UI verbs: 'Reorder categories', 'Reorder the display', survey questions - plus one menu-QR line 'review and reorder' that is a sentence about viewing a menu, not an ordering function), 're-order' 0, 'saved card' 0, 'saved address' 0; 'card on file' 1 (Stripe reservation holds). BOUND as for digital-first-party-web: the KB is not a census; the `no` rests on the vendor's withdrawal statement, not on absence. Retrieved 2026-09-16. https://support.opentable.com/s/article/Offering-Pickup-Ordering-through-OpenTable?language=en_US · retrieved 2026-09-16 adversarially verified

Digital checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator

digital-upsell-engine

Not scored by this record.

Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.

digital-scheduled-pacing

Not scored by this record.

Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.

digital-fulfillment-modes

Not scored by this record.

Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.

digital-qr-table

Not scored by this record.

Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator

digital-kiosk

Not scored by this record.

Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.

digital-group-ordering

Not scored by this record.

Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator

digital-catering-portal

Not scored by this record.

Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator

digital-voice-ai-phone

Not scored by this record.

Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.

digital-drivethru-ai

Not scored by this record.

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

digital-sms-ordering

Not scored by this record.

Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator

digital-google-order

Not scored by this record.

Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.

digital-apple-business-connect

Not scored by this record.

Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.

digital-loyalty-attach

Not scored by this record.

Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.

digital-subscriptions

Not scored by this record.

Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.

digital-promo-parity

Not scored by this record.

Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator

digital-guest-data-ownership

Not scored by this record.

Digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.

digital-checkout-pci-sca

Not scored by this record.

Digital channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator

digital-surcharge-transparency

Not scored by this record.

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

Resolved from `unknown`; the prior rationale’s assertion that merge and dedup behaviour was undocumented is falsified. OpenTable documents merge behaviour precisely: the operator selects profiles in the Guestbook, designates a primary by Bookmark icon, and 'Once merged, the guestbook entry will keep primary profile data and use details from the other profiles as secondary data.' Profile provenance is modelled too — no icon for an in-house booking, an OpenTable icon for a diner-network booking, a Guest Share icon for a profile created at a sister restaurant — and POS checks attach to the guest through reservation matching by table number and a booking-time window. Partial rather than yes on two counts the claim names: the merge is operator-initiated from a checkbox list, not automatic on phone or email match, and the channels it can unify are reservation channels — there is no first-party web or app ordering and no kiosk to merge transactions from, takeout having been withdrawn in 2024. https://support.opentable.com/s/article/Guest-Merge?language=en_US · retrieved 2026-09-08

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: at least two of points-per-dollar, visit/punch-count and spend-tier accrual as configuration, without a bolt-on loyalty vendor. VERDICT: unknown -> partial/B. The prior rationale looked only at the diner-side Dining Points programme; OpenTable ships a first-party, restaurant-configured loyalty product. SURFACE: support.opentable.com Salesforce Aura KB (Knowledge__kav, body field Details__c), census of 2026-09-16: sitemap-topicarticle-1 + weekly = 194 unique slugs, 185 live; href fixpoint added 44 more, 1 live (186 live total); 52 slugs return no public version (archived or non-public; not discriminable), so the KB is NOT a census. Article 'Build and run a restaurant membership loyalty program on the OpenTable platform' (ArticleNumber 000002580, first published 2025-02-28, last 2025-06-30): 'Available for Pro customers.' Setup path: 'Open the menu and select Loyalty. Select Membership programs in the left panel. Select the Start program button.' Visit-count accrual is configuration: 'Set the Criteria to unlock including, the number of visits required to unlock the reward, and the amount of time the visits should occur.'; frequency options 'Immediately after sign up', 'Once', 'Recurring' ('After a Member redeems a recurring reward, their progress will reset, and they can unlock it again after completing the required number of visits') and 'Once, then recurring' ('a complimentary bottle of fine wine might initially require 10 visits in 5 months'). Reward types: 'Exact amount off of the bill', 'Percentage off of the bill', 'Complimentary item', 'Special availability with an access rule'; 'Add up to 15 rewards.' Release note (New on OpenTable, released April 23, 2025): 'Create a loyalty program to help identify more guests and increase guest visit frequency. Available for restaurants on OpenTable Pro.' SHORTFALL (why partial): only ONE of the three accrual models is documented. Nothing in the membership article accrues points per dollar or promotes by spend tier - 'Minimum check size' is a per-reward redemption gate, not accrual. Points balances and tiers appear only for THIRD-PARTY programmes: the docs.opentable.com Postman collection (anonymous, 1.49 MB) 'CRM V3 Loyalties' endpoint carries loyaltyTier ('e.g., Diamond, Gem') and pointsBalance ('Current points balance of the guest in the program') pushed in by partners, and the KB's 'Loyalty & PMS integrations with OpenTable' names Paytronix, Blackbird and Bilt - bolt-ons the claim excludes. A `no` on the second model is not publishable (KB is not a census). Retrieved 2026-09-16. https://support.opentable.com/s/article/restaurantmemberships?language=en_US · retrieved 2026-09-16 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

The help-centre article 'Turn guests into regulars with automated email marketing campaigns' documents exactly the three automations the claim names, plus two more: 'Re-engage lapsed guests: Remind past guests to visit again', 'Welcome new guests: Thank first-time guests and encourage them to return', 'Happy birthday: Bring guests in to celebrate their birthday', alongside Thank repeat guests and Happy anniversary. They are triggered, not manual blasts - campaigns 'use diner profile and visit history data', Send to targets by tags or visit counts, and Send frequency is per-trigger (birthday emails 'as early as 30 days before a guest's birthday, or as late as a day before'). Always-on is explicit: 'The campaign will run perpetually until stopped.' Group-level launch and stats exist for multi-location operators. SHORTFALL: the entire feature is tier-gated - 'Available for restaurants on OpenTable Pro' is stamped on every section - so subscribers below the top Pro plan do not get lifecycle automation at all, and sending requires Marketing/All-Access permission plus a verified device and (for reply-capable sender addresses) an authenticated custom domain. https://support.opentable.com/s/article/Turn-guests-into-regulars-with-automated-email-campaigns?language=en_US · 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

UPHELD, now cited, and bounded. OpenTable's staff-management neighbourhood is documented in detail — named custom roles, feature-area permissions, per-login role assignment, a shared restaurant passcode for sensitive actions, and login-activity monitoring — and time and attendance appears nowhere in it. `time clock`, `timeclock`, `clock-in`, `timesheet`, `payroll` and `punch` each occur zero times across the corpus, on a matcher proven in the same run against terms known present (`chit` 54, `modifier` 67, `reservation` 2,138). The single `clock in` string in the corpus is inside an availability article and is not a timekeeping feature. There is no employee time record to clock into, and no terminal that would host one. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://support.opentable.com/s/article/Custom-roles-and-user-permissions?language=en_US · retrieved 2026-09-08

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

labor-photo-punch-verification

Not scored by this record.

Supports mobile clock-in restricted by geofence or location validation for staff who do not punch at a fixed terminal.

labor-geofenced-mobile-punch

Not scored by this record.

Records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, with the behavior documented. differentiator

labor-offline-time-punch

Not scored by this record.

Permissions are grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers.

labor-granular-rbac

Not fixed tiers: 'Create a custom role with a specific name, and select the feature permissions', 'Create up to ten roles that align with your business needs', users may hold multiple roles, and the seven preset roles (Front of House, Reporting, Marketing, Relationship Management, Direct Messaging, Security Admin, All Access) are themselves editable — only All Access 'can't be customized'. Per location is satisfied: the group-account article documents both group-level roles and restaurant-level custom roles created for one or all restaurants in a group. SHORTFALL: the grantable permissions are feature-area gates (Availability Planning, Marketing, Policies, Reporting: View / Reporting: Export data, Reviews, Direct Messaging, Security Admin, Sign Agreements), not the per-action grants the claim enumerates. The nearest transactional actions — waive payment for prepaid experiences or deposits, refund deposit payments, overbook, underbook, block a table — are not role-assignable at all; they are gated by a single restaurant-wide four-digit passcode in Restaurant Settings > Restaurant Passcode, which every holder shares. https://support.opentable.com/s/article/Custom-roles-and-user-permissions?language=en_US · 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

Two mechanisms exist and neither closes the claim. Override gating ('Passcode protection for key features', re-read 2026-08-09 at its current URL): 'Set up a restaurant passcode and restrict specific actions to employees who have the passcode', where the operator will 'Enter a four-digit passcode' and then 'Select the actions that you want to require the user to enter the passcode to complete' from an enumerated list - Block or unblock a table, Block new online reservations during specific timeframes, Overbook the restaurant when adding in-house reservations, Underbook the restaurant, Change OpenTable iPad application settings, Waive payment for prepaid experiences or deposits, Refund deposit payments. SHORTFALL, and it is the exact antipattern the claim targets: the passcode is a single four-digit code set once for the whole restaurant and shared by everyone who may override, so an approval carries no approver identity. Attribution is a separate feature, 'Set up and manage staff action logging' (https://support.opentable.com/s/article/Logging-User-Actions-1505260692723?language=en_US, retrieved 2026-08-09), which 'tracks changes staff make to reservations on OpenTable, helping you identify who made updates and when' but works by self-assertion - it 'requires staff to select their name in a pop-up window before completing actions that you designate', from an unauthenticated list, and the two features are joined only by a cross-reference tip, not by shared identity. The resulting trail is browsed one booking at a time - 'Select the clock icon in the reservation navigation to view the reservation history. View a record of the reservation changes and the staff members who made them' - rather than exposed as a queryable audit report, and neither article publishes any immutability, tamper-evidence, retention or export statement. https://support.opentable.com/s/article/passcode-protection?language=en_US · retrieved 2026-08-09

Builds and publishes employee shift schedules inside the same platform that holds the timekeeping data, rather than requiring a third-party scheduling app. differentiator

labor-native-scheduling

Not scored by this record.

Generates recommended staffing levels or labor hours by daypart from the operator's own POS sales history, not just a static template. differentiator

labor-demand-labor-forecast

Not scored by this record.

Displays labor cost as a percentage of sales in real time during service on a manager view or POS, not only in end-of-day or next-morning reports. differentiator

labor-realtime-labor-percent

Not scored by this record.

Warns or blocks at clock-in when an employee is approaching or would cross a configured overtime threshold, before the overtime is incurred. differentiator

labor-overtime-prevention

Not scored by this record.

Configures meal and rest break rules per state or jurisdiction, prompts required break attestation, and flags missed breaks for premium pay. differentiator

labor-break-compliance-by-state

Not scored by this record.

Supports predictive-scheduling ordinances by tracking advance-notice deadlines for published schedules and calculating predictability pay owed for employer-initiated changes.

labor-fair-workweek-support

Not scored by this record.

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

labor-minor-labor-rules

Not scored by this record.

Computes tip pooling and tip-outs automatically per shift from configurable rules (percentage of sales, hours worked, points, or role), rather than requiring a manual spreadsheet.

labor-tip-pooling-rules

Not scored by this record.

Retains a per-shift, per-employee record of tips received, amounts contributed to the pool, and amounts distributed from the pool, exportable for audit.

labor-tip-distribution-audit-trail

Not scored by this record.

Payroll export separates cash from charged qualified tips and carries a Treasury tipped-occupation code, supporting the W-2 Box 12 code TP and Box 14b reporting required for tax year 2026. differentiator

labor-qualified-tips-w2-reporting

Not scored by this record.

Vendor processes payroll itself as a first-party product (tax filing and direct deposit), as opposed to exporting to a third-party payroll provider only. differentiator

labor-native-payroll

Not scored by this record.

Exports timecards, wages, and tips in documented formats or via direct integration for at least two major payroll providers (e.g. Gusto, ADP, Paychex, QuickBooks).

labor-payroll-export-formats

Not scored by this record.

Employees can request shift swaps or claim open shifts in a self-service app, subject to a manager approval workflow that enforces overtime and role eligibility. differentiator

labor-shift-swap-workflow

Not scored by this record.

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

labor-digital-onboarding-i9

Not scored by this record.

Reports per-employee sales performance metrics (average check, items or category attachment rate, void and comp rate) by server or cashier. differentiator

labor-server-performance-metrics

Not scored by this record.

Supports multi-level recipe/BOM costing where a recipe can contain sub-recipes (prep items) and plate cost recalculates automatically when any component ingredient's cost changes.

inventory-recipe-bom-costing

UPHELD, now cited, with the homonym disarmed. `inventory` is frequent in this corpus and never means food stock: OpenTable's Reporting Suite files Turn Times and Experiences performance under 'Use inventory and Experiences reports', where the inventory being managed is seats and availability. Food-cost vocabulary is absent outright — `recipe`, `ingredient` (5 hits, all menu-description prose), `food cost`, `purchase order` and `stock level` — and OpenTable holds no ingredient entity to cost against: its menu record stops at item, modifier and price. No plate cost, no sub-recipe, no component roll-up. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://support.opentable.com/s/article/How-to-Access-GuestCenter-Reporting?language=en_US · retrieved 2026-09-08

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

inventory-unit-conversion-yields

UPHELD, now cited. Purchase, recipe and count units presuppose a stocked-item record, and OpenTable has none — the only 'inventory' it manages is seating and availability ('Use inventory and Experiences reports' introduces Turn Times and Experiences performance). There is no unit, conversion factor, yield or waste percentage anywhere in the corpus; `waste` occurs once and not in this sense. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://support.opentable.com/s/article/How-to-Access-GuestCenter-Reporting?language=en_US · retrieved 2026-09-08

Produces a theoretical-vs-actual usage variance report per item for a defined count period, showing theoretical usage from POS sales times recipe, actual usage from counts plus receipts, and the variance in both units and currency. differentiator

inventory-theoretical-vs-actual

Not scored by this record.

Depletes ingredient on-hand quantities in near real time as orders are fired at the POS, including depletion driven by modifier selections, not only in an end-of-day batch. differentiator

inventory-realtime-depletion

Not scored by this record.

Automatically 86s (marks unavailable) menu items on the POS, online ordering, and connected third-party delivery menus when a component ingredient hits zero or a configured threshold. differentiator

inventory-86-auto-sync

Not scored by this record.

Supports full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts.

inventory-count-modes

UPHELD, now cited. Physical counts, spot counts and cycle counts all require a stocked-item record OpenTable does not keep; its 'inventory' reports cover seats and Experiences, not goods. No count workflow, count history or variance record of any kind appears in the 186 help articles or the published API collection. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://support.opentable.com/s/article/How-to-Access-GuestCenter-Reporting?language=en_US · retrieved 2026-09-08

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

inventory-mobile-count-offline

Not scored by this record.

Ships pre-built electronic vendor catalog and order-transmission integrations with named broadline distributors (e.g. Sysco, US Foods, Performance Food Group) that send purchase orders and receive invoices electronically rather than by emailed PDF. differentiator

inventory-vendor-catalogs-edi

Not scored by this record.

Ingests supplier invoices from photo, PDF, or email and extracts line-item detail (item, quantity, unit, price) into the inventory ledger without manual line entry. differentiator

inventory-invoice-ocr

Not scored by this record.

Tracks per-item purchase price history across invoices and alerts when a received price exceeds the prior or contracted price by a configurable threshold. differentiator

inventory-price-change-alerts

Not scored by this record.

Maintains par levels per item per location and generates suggested purchase order quantities from on-hand versus par, with at least one mode driven by a sales forecast rather than a static par. differentiator

inventory-par-auto-suggest

Not scored by this record.

Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.

inventory-waste-logging

Not scored by this record.

Supports inter-location inventory transfers as a two-sided transaction crediting the sending location and debiting the receiving location, with an in-transit or approval state.

inventory-transfers

Not scored by this record.

Supports a commissary/central kitchen model where one location produces prep items and issues or sells them to other locations at a computed transfer cost.

inventory-commissary

Not scored by this record.

Captures lot/batch numbers at receiving and links them through production to sales or transfers, enabling a backward and forward recall trace.

inventory-lot-traceability

Not scored by this record.

Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.

inventory-shelf-life-expiry

Not scored by this record.

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

inventory-bar-partial-bottle

Not scored by this record.

Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.

inventory-cogs-gl-export

Not scored by this record.

Inventory and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator

inventory-native-not-partner

Not scored by this record.

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

inventory-menu-margin-linkage

Not scored by this record.

Provides a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise.

reporting-realtime-dashboard

Resolved from `unknown`. The mobile half of the claim is met and cited: 'Access key business metrics on the go, including real-time shift stats and total revenue from your POS compared to the last four-week average.', under the heading 'Find metrics in the Owner's App' The latency is real rather than nominal, because the POS API requires that 'All ticket updates should be received by OT no later than 30 seconds after the event occurs in the restaurant's POS system.' Partial, not yes, on two shortfalls: the browser side is a report-building surface, not a live dashboard — every entry in the Reporting Suite catalogue is a report you filter, run and export, and its own troubleshooting section is about pages that fail to load and emailed links that expire — and the revenue shown is not OpenTable's own, it is a third-party POS feed that exists only where a POS integration is enabled, which the reporting articles flag repeatedly ('lifetime spend or covers when POS integration is enabled'). https://support.opentable.com/s/article/How-to-Access-GuestCenter-Reporting?language=en_US · retrieved 2026-09-08

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

UPHELD, now cited against the vendor's own catalogue of its Reporting Suite. The hub article enumerates the whole set — Shift Occupancy, Cover Trends, Reservations, Referral Tracking, Turn Times, Experiences performance, First Time Visits, Guest Frequency, Guestbook Export, the three OpenTable for Groups reports, monthly emailed cover reports and scheduled Reviews reports — and every one of them is reservation-, cover- or guest-shaped. None reconciles a service. The money OpenTable can show is the money a POS hands it: the Reservations report's POS columns are 'POS Revenue, POS gratuity, and total gratuity', which is neither gross nor net sales, and carries no tax, discount, refund, tender-type or cash-deposit line. There is no single end-of-day document. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://support.opentable.com/s/article/How-to-Access-GuestCenter-Reporting?language=en_US · retrieved 2026-09-08

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

reporting-pmix-modifier-level

UPHELD, now cited — and checked against the near miss, because OpenTable does receive modifier-level data. The POS Tickets API takes every ticket's `order_items`, each with an `item` (name, price, categories, course) and a `modifiers` array carrying id, name, price and quantity, and the POS API overview says the restaurant can 'view checks on the reservation card via the iPad app' including 'Ordered Menu items'. That is per-check display, not a product mix. On the reporting side the aggregation stops at the reservation: the Reservations report's POS column set is exactly 'POS Revenue, POS gratuity, and total gratuity', and no report in the Reporting Suite catalogue aggregates by item or modifier at all. `product mix` and `PMIX` occur zero times. Quantity, gross and net sales by item and modifier, filterable by daypart and revenue center, is not produced. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://support.opentable.com/s/article/Reservations-Report-in-GuestCenter?language=en_US · retrieved 2026-09-08

Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.

reporting-comps-voids-audit

Not scored by this record.

Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.

reporting-cash-over-short

Not scored by this record.

Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.

reporting-labor-productivity

Not scored by this record.

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

reporting-server-scorecards

Not scored by this record.

Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator

reporting-channel-profitability

Not scored by this record.

Provides a consolidated multi-location report with side-by-side location comparison and drill-down from group total to a single location and then to an individual transaction. differentiator

reporting-multiloc-drilldown

Not scored by this record.

Includes a self-service report builder letting a non-developer choose dimensions, measures, and filters and save the result, rather than only fixed canned reports. differentiator

reporting-custom-report-builder

Not scored by this record.

Supports scheduling any report for automatic recurring delivery by email or to a shared destination on a defined cadence and recipient list.

reporting-scheduled-delivery

Not scored by this record.

Offers automated recurring bulk export of transaction-level raw data to a customer-controlled destination (S3, SFTP, Snowflake, BigQuery, or equivalent), not just manual CSV download. differentiator

reporting-raw-warehouse-export

Not scored by this record.

Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator

reporting-public-api

Not scored by this record.

Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator

reporting-webhooks

Not scored by this record.

API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator

reporting-api-not-upcharged

Not scored by this record.

Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator

reporting-tier-paywall

Not scored by this record.

Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator

reporting-history-retention

Not scored by this record.

Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator

reporting-anomaly-alerts

Not scored by this record.

Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.

reporting-nl-query

Not scored by this record.

Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator

reporting-guest-cohorts

Not scored by this record.

Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator

reporting-sales-forecast

Not scored by this record.

Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.

reporting-tip-tax-compliance

Not scored by this record.

Supports a named organizational hierarchy of at least three levels (e.g. enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations.

multi-location-org-hierarchy

'Manage group permissions and data with Subgroups' documents a named three-level hierarchy as a first-class object: group > subgroup > restaurant, with nesting deeper ('Create a subgroup within the subgroup by selecting Add new subgroup while in the subgroup'). Subgroups are created, named ('Add a name for the subgroup of restaurants'), edited and deleted under Management > Subgroups, with restaurants assigned by RID. Permissions scope to each level: 'Subgroup administrators have All-Access permissions to all restaurants within the subgroup'; 'Users with subgroup-level access can only edit or delete members of the same subgroup, not group-level users'; the companion group-directory article distinguishes group-level access ('across all restaurants in the group or subgroup') from restaurant-level access in the group account. Reporting scopes too: 'The subgroup experience looks the same as the OpenTable for Groups experience but is restricted to that of the restaurants included in the subgroup', which carries group features such as group reporting, and per-subgroup Guest share controls whether diner-profile data crosses the parent group. Requires the OpenTable for Groups product, which is the multi-location offering this claim is about. https://support.opentable.com/s/article/Subgroups?language=en_US · retrieved 2026-08-04

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

multi-location-central-menu-publish

UPHELD, now cited against the group product's own scope statement. OpenTable for Groups lists what it does: 'Use Accounts tools to manage users and access at the group and restaurant level', 'Monitor performance across locations with group-level reporting and exports', 'Find availability across the group when one location is full', optional Guest Share, affiliate availability widgets and group-branded email campaigns. Menus are not in that list, and the menu product is single-restaurant throughout — every step in the menu article begins by logging in to one restaurant's OpenTable for Restaurants website, and publishing means toggling a Display column on that restaurant's own profile. `group menu` occurs zero times. There is no corporate menu, no target-location selection and no publish history. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://support.opentable.com/s/article/GuestCenter-for-groups?language=en_US · retrieved 2026-09-08

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

multi-location-local-override-policy

Not scored by this record.

Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.

multi-location-price-zones

UPHELD, now cited. An OpenTable item carries a single price: '(Name, price, and tax are required)', and the Access Menus response serialises it as one `price.amount`. There is no location group, order channel or daypart dimension on price — `price tier` and `daypart` occur zero times — and the vendor's own workaround for wanting two prices is to duplicate the record: 'If you need to change items for a specific menu, such as it's price, you may want to create a new menu item.' That is precisely the item duplication the claim exists to rule out, and menus are per-restaurant in any case. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://support.opentable.com/s/article/How-To-Update-Your-Menus-in-GuestCenter?language=en_US · retrieved 2026-09-08

Menu, price, and promo changes can be scheduled to activate at a future date/time interpreted in each target location's own timezone, and can be rolled back after activation. differentiator

multi-location-scheduled-publish

Not scored by this record.

A new location can be provisioned by cloning a documented configuration template (menu, taxes, roles, printers, modifiers, tenders) rather than being configured from scratch, and the vendor publishes the expected time-to-open. differentiator

multi-location-new-store-template

Not scored by this record.

The permission model distinguishes a franchisor/corporate tenant from an independently-owned franchisee tenant, so corporate can see franchisee sales and enforce config while the franchisee owns its own employees, banking, and labor data. differentiator

multi-location-corp-vs-franchisee-roles

Not scored by this record.

Calculates franchise royalty, ad-fund, and marketing-fee amounts automatically from POS net sales on a defined schedule, with a configurable royalty basis (gross vs net of discounts/comps/third-party). differentiator

multi-location-royalty-calculation

Not scored by this record.

Supports automated ACH/debit collection of calculated royalties and fees from franchisee accounts, with a franchisee-visible statement of what was charged.

multi-location-royalty-collection

Not scored by this record.

Provides above-store reporting that aggregates sales, labor, discounts, voids, and item mix across any selected set of locations in one view, with store-vs-store ranking and variance flags.

multi-location-consolidated-reporting

Not scored by this record.

Item-level sales roll up across locations under a shared corporate item ID even when stores have renamed or locally priced the item. differentiator

multi-location-normalized-item-rollup

Not scored by this record.

Gift cards issued at one location are redeemable at any other location in the brand, with a reported outstanding-liability balance and inter-store settlement/redemption reconciliation between owners.

multi-location-cross-location-giftcard

Not scored by this record.

A single customer loyalty profile, balance, and stored order history is shared across all locations in the brand rather than being per-location.

multi-location-cross-location-loyalty

Not scored by this record.

A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. differentiator

multi-location-multi-brand

Not scored by this record.

Tax configuration is per-location with support for multiple simultaneous tax rates, jurisdiction-specific rules (e.g. prepared-food vs grocery, inclusive vs exclusive tax), and per-location tax exemptions.

multi-location-multi-tax-jurisdiction

Not scored by this record.

Supports locations operating in different currencies and languages within one enterprise account, with consolidated reporting converted to a reporting currency.

multi-location-multi-currency-locale

Not scored by this record.

Produces an immutable audit log of who changed which configuration object (price, tax, permission, discount) at which location and when, exportable or queryable by corporate. differentiator

multi-location-config-audit-log

Not scored by this record.

Supports SSO via SAML or OIDC against the customer's identity provider for back-office/above-store users, with SCIM or equivalent for automated deprovisioning. differentiator

multi-location-enterprise-sso

Not scored by this record.

Publishes a documented multi-location API (or data warehouse/BI export) that returns transaction-level data across all locations in one authenticated call, without per-location credentials. differentiator

multi-location-enterprise-api

Not scored by this record.

Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.

multi-location-central-labor-policy

Not scored by this record.

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

extensibility-public-api-docs

dev.opentable.com exists but resolves to a Partner Portal; no reference docs rendered without partner access at check time. https://dev.opentable.com/partner-portal · retrieved 2026-08-01

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

extensibility-api-access-cost

Not scored by this record.

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

extensibility-partner-revshare

Not scored by this record.

A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator

extensibility-free-sandbox

Not scored by this record.

Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).

extensibility-oauth-partner-apps

OpenTable's partner API reference (read as the Postman collection docs.opentable.com serves at /api/collections/38767429/2sAXxTcWRy) carries an Authorization section: 'OpenTable utilizes OAuth 2.0 for authorizing access to protected resources' via GET {base}/api/v2/oauth/token?grant_type=client_credentials on oauth.opentable.com, credentials base64'd into an Authorization: Basic header, bearer token thereafter. Operator consent and revocation are real but live elsewhere — the Integrations Marketplace inside the restaurant's own portal, where 'restaurants will be able to learn about partnership opportunities, onboard an integration or offboard an integration' per RID. SHORTFALL: this is the client-credentials grant, so the token is the partner's own long-lived machine credential rather than a per-operator grant, and no scope model is documented on OpenTable's token endpoint — the only 'scope' parameter in the docs is one OpenTable may pass to the PARTNER's authorization server during marketplace onboarding, where OpenTable is the OAuth client and the parameter is marked '(Optional)'. Revocation is therefore all-or-nothing per restaurant tile, not per individually granted permission. https://docs.opentable.com/ · 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

Real push exists, but not for the event class this claim names. The Reservation Webhook v3 (Feb 2025), published for Copper, Gold, Platinum and POS partners, states 'Webhooks are triggered on any change in reservation status. A POST request is sent to the specified endpoint with the payload data', over HTTPS:443 only, with 'exponential backoff strategy. After three failed attempts, the webhook is marked as undeliverable'; the payload's state enum runs NotConfirmed through Seated, CheckDropped, Paid, Done, NoShow, Cancelled. A menu webhook is also documented. SHORTFALL: the order/check lifecycle is not pushed by OpenTable. Ticket data flows the other way — the POS partner POSTs tickets to OpenTable's POS Tickets API with operation 'add' or 'update' — and a consumer wanting order events must poll: the Platinum Orders API is 'GET {base}/sync/v2/pos-data' filtered by updated_after with limit/offset paging, rate-limited to 1,500 requests per rolling 30 seconds. There is no created/modified/paid/voided/refunded order webhook. https://docs.opentable.com/ · retrieved 2026-08-04

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

extensibility-webhook-reliability

Not scored by this record.

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

extensibility-order-injection-api

Not scored by this record.

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

extensibility-menu-write-api

Not scored by this record.

Every core object the API can read (orders, menu, customers, employees, inventory) can also be written or updated via the same API. differentiator

extensibility-data-symmetry

Not scored by this record.

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

extensibility-published-rate-limits

Not scored by this record.

The vendor is a named DoorDash Preferred Integration Partner (DPIP) under the 2026 program requirements. differentiator

extensibility-doordash-preferred

Not scored by this record.

Direct, first-party certified integrations exist with DoorDash, Uber Eats, and Grubhub without requiring a paid middleware layer (Otter/Chowly/Deliverect/Checkmate). differentiator

extensibility-first-party-delivery-integrations

Not scored by this record.

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

extensibility-middleware-compatibility

Not scored by this record.

Native, vendor-maintained connectors exist for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export.

extensibility-accounting-connectors

Not scored by this record.

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

extensibility-payroll-export

Not scored by this record.

Raw transaction-level data can be exported on a schedule to a customer-controlled destination (S3/SFTP/warehouse/Snowflake share), not only viewed in the vendor's reporting UI. differentiator

extensibility-bi-data-warehouse

Not scored by this record.

The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.

extensibility-app-marketplace

Not scored by this record.

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

extensibility-custom-fields-scripting

Not scored by this record.

The vendor supports a headless/embedded mode where a third-party UI (kiosk, web ordering, drive-thru) drives the POS transaction engine via API.

extensibility-headless-embedded

Not scored by this record.

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

extensibility-api-versioning-deprecation

Not scored by this record.

A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator

extensibility-data-portability-exit

Not scored by this record.

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

reliability-offline-order-entry

UPHELD, now cited, and not vacuous — OpenTable ships a genuine named offline mode, so the question is what survives in it. The article is explicit that it is degraded and read-mostly: 'While offline mode allows you to operate without internet, it is not intended to be a fully functional and operational experience'; you 'will be able to see your floor plan and look up information about reservations and guests, but information may become outdated'; 'any changes you make won't get published to OpenTable.com or other devices until you are back online'; reservation history is unavailable and reservations older than two days 'can be out of date or unavailable'. What it protects is the book and the floor plan. Order entry, ticket routing and check printing are not among the things that continue offline because OpenTable performs none of them online either — check data flows into OpenTable from the restaurant's POS, never the reverse. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://support.opentable.com/s/article/Offline-mode-in-GuestCenter?language=en_US · retrieved 2026-09-08

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

reliability-offline-card-auth

Not scored by this record.

The vendor publicly documents who bears the loss when a store-and-forward transaction declines after connectivity returns, and states any per-transaction or cumulative offline cap. differentiator

reliability-offline-decline-liability

Not scored by this record.

Multiple terminals continue to share a single check/table state over the local network while the internet is down (LAN-only degraded operation, not per-terminal islands). differentiator

reliability-lan-degraded-multi-terminal

Not scored by this record.

The vendor documents a local/on-premise transaction engine or edge server (not purely cloud-hosted request/response) for the ordering path. differentiator

reliability-local-transaction-engine

Not scored by this record.

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

reliability-offline-kds-printing

UPHELD, now cited, and deliberately checked against what OpenTable does print — it is not a free pass. The iPad app drives a real chit-printing stack over Ethernet, Bluetooth, Wi-Fi and USB, and one documented configuration puts a printer on the line: '1 Ethernet Printer in the kitchen for the Chef to review guest allergies in notes.' But what prints is a guest chit — group notes, visit stats, guest spend, rewards — not a kitchen ticket, and there is no order routing to continue: no station, no prep area, no course firing, no KDS. Nothing in the offline-mode article's list of what still works mentions printing, and the article's own framing is that offline 'is not intended to be a fully functional and operational experience'. Kitchen display and kitchen printer routing do not exist here, offline or online. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://support.opentable.com/s/article/Chit-Printer-Setup?language=en_US · retrieved 2026-09-08

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

reliability-printer-fallback

UPHELD, now cited against a fully enumerated settings screen. Chit Printing is configured by selecting printers from a discovered list — 'You can select to print to multiple printers at one time' — then setting 'the default number of chits, decide if they print automatically, and select which details are included on the chit', with toggles for group notes, visit stats, guest spend and rewards. Multiple printers here print SIMULTANEOUSLY, which is broadcast, not failover: no backup-printer designation, no reroute on unreachable, and no alert to staff appears in the article or anywhere else in the corpus. The only recovery documented is manual — reset the printer, forget and re-pair it. Measured over the corpus frozen 2026-09-08: 186 OpenTable help-centre articles (185 of the 194 urlNames in support.opentable.com/s/sitemap-topicarticle-1.xml, fetched as prose through the Salesforce Aura record endpoint, plus one article found by an href fixpoint and absent from the sitemap) and all 159 documented nodes of the published Postman collection at docs.opentable.com (collection 38767429/2sAXxTcWRy), 2,317,152 characters. That is a FLOOR, not a census: the fixpoint referenced 44 slugs the sitemap omits, of which 8 are live. https://support.opentable.com/s/article/Chit-Printer-Setup?language=en_US · retrieved 2026-09-08

The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).

reliability-sync-conflict-handling

Not scored by this record.

The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).

reliability-offline-feature-matrix

Not scored by this record.

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

reliability-public-status-page

Not scored by this record.

A contractual uptime SLA with a stated percentage AND a service credit remedy is published or available in the standard agreement. differentiator

reliability-contractual-uptime-sla

Not scored by this record.

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

reliability-incident-postmortems

Not scored by this record.

24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.

reliability-247-live-support

Not scored by this record.

The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator

reliability-onsite-install

Not scored by this record.

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

reliability-menu-build-service

Not scored by this record.

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

reliability-hardware-replacement-sla

Not scored by this record.

Operators can trigger and retrieve their own data backup/restore, or the vendor publishes RPO/RTO figures for data recovery.

reliability-backup-restore

Not scored by this record.

The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.

reliability-pci-dss-4-attestation

Not scored by this record.

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

reliability-mfa-role-based-access

Not scored by this record.

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

reliability-self-serve-training

Not scored by this record.

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

reliability-failover-terminal-role

Not scored by this record.

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

reliability-cellular-backup

Not scored by this record.

Vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core POS software tier. differentiator

commercial-month-to-month-contract

Not scored by this record.

Vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. differentiator

commercial-no-early-termination-fee

Not scored by this record.

The auto-renewal term and the required cancellation notice window (e.g. 30/60/90 days) are stated in publicly accessible contract terms rather than only in a signed quote.

commercial-autorenew-terms-published

Half the claim is met. OpenTable's help centre article on the 2026 Client Agreement (2026-03-25) publishes the renewal term under the heading 'Auto Renewal': 'New agreements now default to a 12-month auto-renewal term, where previously the default was month-to-month. This change also includes clear language around fees associated with early termination. If you're an existing restaurant, this does not affect you - your current Order Form terms continue to take precedence.' SHORTFALL: the cancellation notice window is nowhere in that public text, nor is the early-termination fee it alludes to; the article closes 'Reach out to your account manager. They can walk you through any part of the agreement.' The Client Agreement itself has no public URL I could find, and the one contract OpenTable does publish, the Terms of Use at opentable.com/c/legal/terms-and-conditions, is diner-facing — I read it in full and it governs use of the OpenTable sites and reservation services, with no restaurant subscription term, renewal or notice provisions. https://support.opentable.com/s/article/Updates-to-the-restaurant-client-agreement?language=en_US · retrieved 2026-08-04

The POS software can be purchased and operated with a third-party payment processor of the operator's choice (no mandatory in-house processing lock). differentiator

commercial-processing-not-bundled

Not scored by this record.

Vendor publishes an interchange-plus (cost-plus) processing rate option with the markup stated as a specific bps + per-transaction figure, rather than only blended/flat card-present rates. differentiator

commercial-interchange-plus-published

Not scored by this record.

The processing agreement caps or prohibits unilateral vendor-initiated rate increases outside of pass-through interchange/network changes, or grants penalty-free exit on any increase. differentiator

commercial-rate-increase-clause

Not scored by this record.

Per-location and per-additional-terminal software pricing is published as specific dollar figures on the vendor's public site (not 'contact sales' only).

commercial-pricing-published

One of three tiers carries a public figure. The Basic plan page states 'Free* to try for 30 days then $149 per month, cancel anytime' and, in the footnote, 'After your 30-day free trial, OpenTable Basic is $149 per month plus a per cover fee. Credit card required.' SHORTFALL: the per-cover fee that the same sentence says is charged on top is never quantified on any OpenTable page, and the Core and Pro plan pages (https://www.opentable.com/restaurant-solutions/plans/core/ and /pro/, both retrieved 2026-08-09) carry no dollar figure whatsoever - their pricing FAQ answers only the contract term, 'The standard contract is one year with auto-renewal annually', and route the reader to 'Speak to sales'. Nothing on the site publishes a per-additional-terminal or per-device price. Note also that the previously cited /restaurant-solutions/pricing/ no longer exists: it 404s to /blog_404 at exactly the byte size a fabricated path under the same directory returns, while /restaurant-solutions/ itself returns 200. https://www.opentable.com/restaurant-solutions/plans/basic/ · retrieved 2026-08-09 · not refetchable · site policy · graded C when read

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

Resolved from `unknown`. The lease half of the claim is cleanly met and now cited: OpenTable rents and leases nothing — `lease`, `leasing` and `rental` occur zero times across the corpus on a word-boundary matcher proven live in the same run — and the one piece of hardware it specifies is bought outright from a third party at that vendor's own published price: 'OpenTable doesn't sell, distribute, or service printers; however, you can find the printers we support available for purchase on the StarMicronics site', with the supported models named (Star Micronics TSP143IV, TSP143IIIB, TSP143IIIU, TSP134IV, mC-Print3). Partial rather than yes because the claim asks about all required hardware and the set is incomplete: OpenTable ships no terminals and no KDS screens at all, and the iPad that runs OpenTable for Restaurants is never given a purchase price or supply term anywhere in the corpus. https://support.opentable.com/s/article/Chit-Printer-Setup?language=en_US · retrieved 2026-09-08

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.