Resy

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

Resy has one level of selection group and it hangs off an event ticket, not a menu item. The documented builder is: create an event ticket, open its "Items" tab, "Start From Scratch", then set "Pricing" ("Items are individually priced and added to the final cost") and "Booking Rules" ("Require selection(s) for booking", "1 selection per guest"). That yields a forced-selection flag and a per-guest selection count — one level — and the members are flat entries drawn from the Item Library, which carries no child group of its own: an item's documented fields are name, cost, Item Type (a tax code), Total Stock, Daily Limit, category and the shifts it is applied to (https://helpdesk.resy.com/en_us/how-can-i-manage-add-on-items-S1vobw7UO). Nothing nests below that, and no second or third level, no independent min/max pair per level, and no sub-group object appears anywhere. The strings 'modifier group' and 'modifier' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance). https://helpdesk.resy.com/en_us/using-add-ons-to-offer-different-priced-event-tickets-ryEZ6SEc · 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

Resy's own documented answer to variant pricing is duplication — precisely what the claim excludes. To sell two prices for one thing the help centre instructs: "You'll first need to create the add-on item for each ticket in the Item Library. (For example, if you want to sell Adult and Children's tickets for an event, you'll need to create an 'Adult Ticket' and 'Children's Ticket' item, which can be priced appropriately.)" Each Item Library entry carries a single cost (https://helpdesk.resy.com/en_us/how-can-i-manage-add-on-items-S1vobw7UO); there is no price matrix, no parent-item dimension and no size dimension, and an item's price does not vary with what it is attached to. Resy holds no menu item and no size attribute at all, so the parent-by-size matrix the claim describes has no operands here. https://helpdesk.resy.com/en_us/using-add-ons-to-offer-different-priced-event-tickets-ryEZ6SEc · 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

The Item Library is Resy's only priced-object surface, and its documented fields are name and cost, Item Type (a tax code drawn from a fixed list — Alcoholic Beverage, Book, Candy, Chocolate, Clothing, Donation, Food, Grocery/Pantry, Gum, Merchandise, Non-Alcoholic Beverage, On-Premise Event, Online Event, Single-Use Items), Applied To (shifts), Total Stock, Daily Limit and Date Created. No quantity tier, price multiplier or per-tier pricing appears. The only quantity controls documented anywhere are stock depletion ("Total Stock Quantity = 50. Daily Sales Limit = 10.") and the booking-rule selection count ("1 selection per guest", https://helpdesk.resy.com/en_us/using-add-ons-to-offer-different-priced-event-tickets-ryEZ6SEc), neither of which prices a tier. No light/regular/extra/double tier vocabulary occurs in any of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance). https://helpdesk.resy.com/en_us/how-can-i-manage-add-on-items-S1vobw7UO · 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

Resy ships no first-party payment terminal, so there is nothing to accept EMV or terminal NFC. The hardware article enumerates the entire required kit — iPad Pro 12.9" or iPad 9.7"+ on iOS 15 or higher, cases, keyboards, security stands, a Lightning-to-USB3 and USB-to-Ethernet adapter pair for hardwiring, a wifi extender, and Star Micronics TSP143IIIBi / MCP31LB / TSP650II BTi / TSP654IIBi2 / TSP100 chit printers — and no card reader, PIN pad or terminal appears in it. Card acceptance is online or keyed through Stripe, or guest-phone: Resy Pay puts a QR code on the check so diners "can pay their checks on their phone via QR code, and even choose to pay with Google Pay™, Apple Pay®, and eligible American Express Membership Rewards® points towards their meal" (https://helpdesk.resy.com/en_us/resy-pay-BJUK2y65) — wallet acceptance in the guest's own handset, not contactless at a Resy terminal. Resy's own text places card hardware outside the product: the Resy Credit excludes transactions "Processed using a third-party system (e.g., mobile card readers or payment platforms)" (https://helpdesk.resy.com/en_us/resy-credit-faq-HJSEckqixl). 'EMV' and 'card present' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance). https://helpdesk.resy.com/en_us/resyos-recommended-hardware-and-accessories-SyvVbP78_ · 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

The Transactions FAQ enumerates every money-movement function Resy performs — event ticket sales, prepaid reservations, cancellation/no-show fees and third-party prepay — and states 'Resy does not add any additional fees for payment processing. You will see a transaction fee from our third-party payment processor of 2.9% + $0.30 per transaction', with refunds issued 'via your Stripe Dashboard'. No stored-value or gift-card instrument appears. The plans-pricing comparison table across all four plans (Platform, Platform 360, Essential, Premium) lists no gift-card row, and re-tested 2026-09-08 over the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance) — the earlier bound of "57 articles" was the curated llms.txt slice, not the manifest — 'gift' occurs in just two, neither of them an instrument: a marketing suggestion to "target VIPs to encourage them to purchase gift cards", and the Resy Credit exclusion list, which names "Resy-branded American Express® Gift Cards; and gift cards purchased at restaurants" among the transactions Resy does NOT process. The larger corpus strengthens this verdict rather than disturbing it. The 'Resy branded American Express Gift Card' that does exist is an Amex consumer prepaid card usable at any Amex-accepting merchant — not a merchant-issued gift-card program with balance tracking across a restaurant group. https://helpdesk.resy.com/en_us/transactions-faq-ByVZQWk8Y · 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

Resolved from `unknown`. Attribution and a record do exist for the one money action Resy performs in-app: cancelling a prepaid reservation past the cancellation window offers a "Refund payment" toggle, after which the operator must "Select your name from the accountability screen and tap 'Confirm Cancellation'", and "A record of the refund will be listed in the guest's reservation history"; charging a cancellation or no-show fee runs through the same accountability screen (https://helpdesk.resy.com/en_us/how-do-i-charge-a-cancellation-or-no-show-fee-HJQXfP7Lu). NAMED SHORTFALLS: the accountability screen is an unauthenticated name picker, not an authorization — "Tap the name or initials for the person completing the reservation. If not listed, tap 'Add Name'" — so any user may attribute an action to any name, and no PIN or manager approval is required. The permission model's nine password-protected actions are all reservation and floor-plan actions and include no refund, void, comp or discount (https://helpdesk.resy.com/en_us/user-permissions-r1zCWDmU_). The trail is the guest's reservation history rather than an immutable append-only log: 'activity log' occurs in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance), and the single 'audit' hit is "PrePay audit prior to service", a manual weekly review of a report. Voids, discounts and no-sales have no controls because they do not exist — Resy runs no register. And refunds outside the in-app path leave Resy entirely: "To approve and issue a refund for a guest" the operator is sent to the Stripe Dashboard, where Resy's controls do not reach. https://helpdesk.resy.com/en_us/how-to-cancel-and-refund-a-prepaid-reservation-SJRfzDXIu · retrieved 2026-09-08

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

payments-chargeback-tooling

Not scored by this record.

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

payments-card-on-file

Not scored by this record.

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

payments-payout-timing

Not scored by this record.

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

payments-multi-entity-routing

Not scored by this record.

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

payments-p2pe-pci4

Not scored by this record.

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

delivery-driver-roster

Resy operates no delivery at all, so a native in-house driver module with drivers as first-class entities, clock-in/out, assignment state and per-driver run history has nothing to attach to. 'dispatch' and 'delivery zone' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance) and in none of the 71 pages of Resy's merchant site; 'driver' and 'delivery fee' occur once each on the merchant site and both sit in /resources/ editorial about restaurants generally, not about Resy. The merchant site's 20 product pages are reservations, experiences, guest data, analytics, get-discovered, Amex guest demand, business perks, platform security, industry commitment, integrations, pricing, hospitality groups, restaurants, hotels, wineries, get-started and the two terms pages — there is no delivery, dispatch or logistics page, and the four-plan comparison table on the pricing page carries no delivery row. Resy's own explainer marks the category boundary: it is a reservation platform that integrates with POS and delivery systems rather than being one (https://resy.com/join/resources/what-is-a-pos-system-in-a-restaurant/). https://resy.com/join/plans-pricing/ · 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

Resy operates no delivery at all, so a dispatch/expo screen with undispatched orders, driver availability, elapsed time per order and multi-order run batching has nothing to attach to. 'dispatch' and 'delivery zone' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance) and in none of the 71 pages of Resy's merchant site; 'driver' and 'delivery fee' occur once each on the merchant site and both sit in /resources/ editorial about restaurants generally, not about Resy. The merchant site's 20 product pages are reservations, experiences, guest data, analytics, get-discovered, Amex guest demand, business perks, platform security, industry commitment, integrations, pricing, hospitality groups, restaurants, hotels, wineries, get-started and the two terms pages — there is no delivery, dispatch or logistics page, and the four-plan comparison table on the pricing page carries no delivery row. Resy's own explainer marks the category boundary: it is a reservation platform that integrates with POS and delivery systems rather than being one (https://resy.com/join/resources/what-is-a-pos-system-in-a-restaurant/). https://resy.com/join/plans-pricing/ · 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

Resy operates no delivery at all, so per-zone delivery fees, order minimums and quoted promise times applied from a validated customer address has nothing to attach to. 'dispatch' and 'delivery zone' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance) and in none of the 71 pages of Resy's merchant site; 'driver' and 'delivery fee' occur once each on the merchant site and both sit in /resources/ editorial about restaurants generally, not about Resy. The merchant site's 20 product pages are reservations, experiences, guest data, analytics, get-discovered, Amex guest demand, business perks, platform security, industry commitment, integrations, pricing, hospitality groups, restaurants, hotels, wineries, get-started and the two terms pages — there is no delivery, dispatch or logistics page, and the four-plan comparison table on the pricing page carries no delivery row. Resy's own explainer marks the category boundary: it is a reservation platform that integrates with POS and delivery systems rather than being one (https://resy.com/join/resources/what-is-a-pos-system-in-a-restaurant/). https://resy.com/join/plans-pricing/ · 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

What Resy embeds on the restaurant's own domain is a BOOKING widget, not an ordering site: the article is "Resy Widget Installation", the code comes from Venue > Basic Info > Widget in the Resy Dashboard, and the install targets are BentoBox, Squarespace, WordPress, Wix and GoDaddy — the thing installed takes reservations. No commission-free web ordering menu exists to write orders into a POS, and Resy has no POS to write them into. 'food ordering', 'commission-free' and 'order directly' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance) and none of the 71 merchant pages; the four 'online ordering' hits on the merchant site are all /resources/ editorial advising operators to "Link your online ordering platforms" — that is, someone else's. Resy At Home, a 2020 prepaid-pickup programme for "large format meals, grocery boxes, or meal kits" built on the Events ticketing tool, appears only in blog posts dated 2020 and in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance). Resy's own positioning corroborates the absence: for takeout and delivery revenue it refers operators to a partner, announcing that "Resy has teamed up with ChowNow, a platform for commission-free online ordering, marketing automation, and delivery tools for restaurants" (https://blog.resy.com/for-restaurants/four-tips-to-help-boost-takeout-revenue-through-the-end-of-winter/, 2024-03-06) — a vendor that shipped this capability would not source it. https://helpdesk.resy.com/en_us/booking-button-installation-Skx_7ueNo · retrieved 2026-09-08

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

digital-menu-single-source

There is no single menu record to propagate from, because Resy holds no menu. Its only item store is the Item Library of prepaid add-on items, and its scope object is the SHIFT, not the channel: "Applied To: Shows which shifts you have applied these items", and "When you make an edit to an existing add-on item, this will affect all shifts that the item is being used and all transactions going forward." That propagation runs across shifts within one venue's booking flow — Resy.com, the Resy app and the booking widget render the same booking record — and there is no in-store channel to keep in step, Resy running no register. The restaurant's actual food menu lives outside Resy entirely; Resy's own guidance to operators is to "upload a sample menu" to their Google profile (https://resy.com/join/resources/digital-marketing-for-restaurants/). https://helpdesk.resy.com/en_us/how-can-i-manage-add-on-items-S1vobw7UO · 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

Resolved from `unknown`. Saved, tokenized payment against a guest account is real and documented: with Resy Pay a diner pays the check from their phone by QR code and can "use Apple Pay, Google Pay, or a card saved on their Resy account", split the check with friends, and — for eligible Amex Card Members — apply Membership Rewards points; guests also store a card against prepaid reservations and cancellation-fee policies. NAMED SHORTFALLS: the other two elements of the claim do not exist and cannot, because Resy has no ordering channel — there is no previous order to re-place, so one-tap reorder is absent, and no delivery or fulfilment address is stored because nothing is fulfilled. The account is also the consumer Resy network account rather than a restaurant-branded first-party channel, and Resy Pay itself rides the operator's existing POS (its compatible list is Micros RES 3700, Micros Simphony FE, Micros Simphony, NCR Aloha, Toast and Upserve/Breadcrumb), so the stored instrument pays a check the POS owns. https://helpdesk.resy.com/en_us/resy-pay-BJUK2y65 · retrieved 2026-09-08

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

digital-upsell-engine

Not scored by this record.

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

digital-scheduled-pacing

Not scored by this record.

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

digital-fulfillment-modes

Not scored by this record.

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

digital-qr-table

Not scored by this record.

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

digital-kiosk

Not scored by this record.

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

digital-group-ordering

Not scored by this record.

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

digital-catering-portal

Not scored by this record.

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

digital-voice-ai-phone

Not scored by this record.

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

digital-drivethru-ai

Not scored by this record.

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

digital-sms-ordering

Not scored by this record.

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

digital-google-order

Not scored by this record.

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

digital-apple-business-connect

Not scored by this record.

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

digital-loyalty-attach

Not scored by this record.

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

digital-subscriptions

Not scored by this record.

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

digital-promo-parity

Not scored by this record.

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

digital-guest-data-ownership

Not scored by this record.

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

digital-checkout-pci-sca

Not scored by this record.

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

digital-surcharge-transparency

Not scored by this record.

Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.

guest-loyalty-unified-profile

A single guest profile per venue account is real and its dedup/merge behavior is documented — but the merge is manual, not automatic. The help centre: 'You will need to merge guest profiles if a guest has multiple profiles within Resy. Merging the profiles will keep all guest visit information in one place.' Duplicate detection surfaces as a blue exclamation point next to the phone/email that opens a 'Duplicate Phone Number' pop-up, after which staff confirm 'Merge Guests', pick the surviving name/number/email and tap 'Merge Guest' — a staff-initiated flow, with a second manual path via the profile's three-dot menu. Hard limit in the same article: 'App User profiles cannot be merged. When a guest creates their profile through Resy.com or the Resy App, their information is protected and can only be edited by the guest or Resy Support.' Channel coverage also falls short of the claim: what lands on the profile is reservation/visit data plus POS check data via the check-matching integration (POS Integrations article) — Resy has no first-party ordering or kiosk channel to merge. The enterprise marketing page asserts 'Unlock a unified guest profile — a single view of each guest across every concept' (https://resy.com/join/hospitality-groups/), but no automatic phone/email-match merge is documented anywhere. https://helpdesk.resy.com/how-to-merge-guest-profiles-H1Qq89cbt · retrieved 2026-08-04

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

guest-loyalty-thirdparty-identity-attach

Not scored by this record.

Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.

guest-loyalty-accrual-models

Resolved from `unknown`: Resy exposes no operator-configurable accrual of any kind. 'accrual' and 'punch card' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance), and no points-per-dollar, visit-count or spend-tier earn rule is configurable anywhere in the product. The nearest constructs are read-only labels rather than earn rules: "New regulars are guests who have completed their third all-time visit to your restaurant" is an analytics definition whose documented follow-up is manual — "Make sure to note their status on their profile so you can acknowledge them and/or their loyalty the next time they dine!" — and auto-tagging that "Automatically identify VIPs, regulars, and special-occasion guests" (https://resy.com/join/guest-data/) produces a tag, not a balance, with no reward attached and nothing to redeem. The points that do appear in the corpus are American Express Membership Rewards, spent by Card Members through Resy Pay (https://helpdesk.resy.com/en_us/resy-pay-BJUK2y65), and the Resy Credit is an Amex cardholder benefit whose own FAQ excludes merchant instruments from it (https://helpdesk.resy.com/en_us/resy-credit-faq-HJSEckqixl) — both are Amex issuer programmes that the restaurant neither configures nor funds. https://helpdesk.resy.com/en_us/advanced-analytics-faq-S1zUFF61C · retrieved 2026-09-08

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's own marketing-email pathway is a manual export to a third-party ESP: 'You can create and set up effective marketing emails for your guests through Mailchimp', via a three-step flow — download the Guestbook from Resy OS as CSV, import it into Mailchimp, then build and send a one-off 'Email Blast' (with a Constant Contact discount offered through the Amex Business Savings Suite as the alternative). The Marketing and Promotion category enumerates the whole marketing surface — the Mailchimp article, Promote on Social Media, Facebook/Google/Instagram listing integrations, and manual 2-Way Texting — and contains no triggered campaign feature. The only automated guest emails Resy itself sends are transactional: 'Guests booking or making reservation changes online will receive an automated email from Resy with the reservation details every time they book, change, or cancel a reservation' (booked/change/cancel/waitlist, body-customizable on Platform 360 only). Birthday, first-visit and lapsed win-back automations appear nowhere; the vendor's documented answer to lifecycle marketing is the Mailchimp hand-off. https://helpdesk.resy.com/en_us/how-to-send-an-email-blast-BJGSDmUd · 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

Resy OS has no time clock. 'time clock', 'timeclock', 'clock in', 'clock-in', 'payroll' and 'shift schedul' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance) — 'punch' appears twice and both are "a punchy description" in event-content guidance. Resy OS's only person object is a user login with per-action booking and settings permissions (https://helpdesk.resy.com/en_us/user-permissions-r1zCWDmU_), and its only per-transaction staff marker is the accountability screen, an unauthenticated name picker — "Tap the name or initials for the person completing the reservation. If not listed, tap 'Add Name'" (https://helpdesk.resy.com/en_us/how-to-book-a-reservation-in-resyos-app-rJxfGvXIu). That records who says they did something; it does not start or stop a shift, and no hours, breaks or labour totals are produced anywhere. https://helpdesk.resy.com/en_us/resyos-troubleshooting-steps-ByjDtVwBK · 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

Resy OS grants permissions as individual per-action toggles, not fixed tiers: Booking Permissions ('Book without payment', 'Charge cancel fee') and Update Settings Permissions ('Update venue details and transactions settings', 'Create exclusive groups', 'Create and edit floor plans on the web dashboard', 'Update shifts', 'Single-day changes', 'Guest communications', 'Manage users', 'Set and update tax rates'), plus a separate 'Reports' tab controlling report/distribution-list access. Shortfall: the grantable actions are reservation and settings actions only — there is no void, comp, discount, refund, drawer-open or price-change permission, because Resy runs no register; permissions are assigned per individual user with no reusable role object to apply across staff; and two of the toggles (Create exclusive groups, Guest communications) are documented as 'available for Platform 360 and Full Stack restaurant partners' only. Per-location scoping is not addressed in the article. https://helpdesk.resy.com/user-permissions-r1zCWDmU_ · 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

An override gate exists and its scope is enumerated: 'Password Protections' can be applied to creating unassigned reservations, booking/assigning to in-house inventory, closing and opening days and shifts, adding and removing table blocks, editing floor plans and tables in the ResyOS app, disabling online reservations for a shift, single-day availability changes, adding or removing VIP tags, and unassigning Global Dining Access slots. Shortfall: the gate is a single venue-level secret — 'When performing an action that is password protected, users will be prompted to enter the password. If entered incorrectly, the action will fail' — and the per-user control is only a binary 'Enforce password protection' bypass flag, so an approval cannot be attributed to the individual approver; this is exactly the shared-PIN pattern the claim is written against. No override log, activity trail or after-the-fact query surface is described in this article or anywhere in the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance) — re-tested 2026-09-08, the earlier bound of "57 articles" having been the curated llms.txt slice rather than the manifest: 'activity log' occurs zero times, and the single 'audit' hit is "PrePay audit prior to service", a manual weekly review of the PrePay report rather than a log. https://helpdesk.resy.com/user-permissions-r1zCWDmU_ · retrieved 2026-08-04

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

labor-native-scheduling

Not scored by this record.

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

labor-demand-labor-forecast

Not scored by this record.

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

labor-realtime-labor-percent

Not scored by this record.

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

labor-overtime-prevention

Not scored by this record.

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

labor-break-compliance-by-state

Not scored by this record.

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

labor-fair-workweek-support

Not scored by this record.

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

labor-minor-labor-rules

Not scored by this record.

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

labor-tip-pooling-rules

Not scored by this record.

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

labor-tip-distribution-audit-trail

Not scored by this record.

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

labor-qualified-tips-w2-reporting

Not scored by this record.

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

labor-native-payroll

Not scored by this record.

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

labor-payroll-export-formats

Not scored by this record.

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

labor-shift-swap-workflow

Not scored by this record.

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

labor-digital-onboarding-i9

Not scored by this record.

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

labor-server-performance-metrics

Not scored by this record.

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

inventory-recipe-bom-costing

Resy holds no ingredient, so there is no bill of materials to cost. 'ingredient', 'sub-recipe', 'plate cost', 'food cost' and 'recipe' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance); the merchant-site hits for those words are all /resources/ editorial carrying restaurant operating advice, not descriptions of Resy. The only costed object in the product is an Item Library entry, whose cost is its single SALE price with no component structure beneath it and no cost roll-up (https://helpdesk.resy.com/en_us/how-can-i-manage-add-on-items-S1vobw7UO). "Inventory" in Resy's own vocabulary means bookable seats — table, slot, prepaid and Global Dining Access inventory — with the single exception of an add-on item's Total Stock and Daily Limit, which count units of a finished item offered for sale, not stock of an ingredient. https://helpdesk.resy.com/en_us/how-can-i-manage-add-on-items-S1vobw7UO · 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

No unit model exists to convert between. 'unit of measure', 'par level', 'yield' and 'shrinkage' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance). An Item Library entry has one quantity dimension — Total Stock and Daily Limit, both counts of the sellable item ("Total Stock Quantity = 50. Daily Sales Limit = 10.") — and no purchase unit, recipe unit, count unit, conversion factor or waste percentage. There is no purchasing surface at all: 'purchase order' and 'vendor order' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance), and raw-to-usable conversion has no raw side because Resy stores no ingredient. https://helpdesk.resy.com/en_us/how-can-i-manage-add-on-items-S1vobw7UO · 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

Resy tracks stock by depletion, never by counting it. The Item Library's documented quantity surface is Total Stock and Daily Limit, decremented as items sell ("Total Stock Quantity = 50. Daily Sales Limit = 10. Sales will continue daily, max 10 items daily, until 50 items have been sold overall"), and the listed uses of the library are "Creating, updating, or deleting items", "Checking the quantities left on your items" and "Visibility on where your active items are currently being offered". No count session of any kind exists: 'physical count', 'cycle count', 'count sheet' and 'stocktake' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance), so neither full physical inventory, ad-hoc spot counts nor scheduled recurring cycle counts are available — and with no count there is no counted-versus-expected variance to record as history. The corpus's two 'variance' hits are month-over-month cover mix and waitlist quote-time accuracy, not stock variance. https://helpdesk.resy.com/en_us/how-can-i-manage-add-on-items-S1vobw7UO · 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

The browser dashboard has a live-ish operational view: the Analytics Home page 'is where you can see today's cover stats at a glance and compare them to yesterday's performance', and with a POS integration the reservation profile carries a 'Check' tab with 'Real-time check level data' plus automatic 'Check Dropped' and course-status updates. Shortfall: the live surface is covers and per-reservation checks, not an aggregated live sales dashboard — the check tab is documented as refreshing only when 'the check tab is closed and reopened', and every sales roll-up is a scheduled email rather than a screen: Daily Forecast 'sent daily and only for dinner shifts', POS Trends Dashboard 'sent weekly', POS Overview 'sent weekly', Service Snapshot 'sent to your inbox at 6:00 am local time'. Sales data at all requires the POS integration, which is 'available for Platform and Platform 360 restaurant partners'. Off-premise mobile access is asserted on the marketing site ('Mobile access — Check in on performance anytime, anywhere', https://resy.com/join/analytics/) but the help centre documents the ResyOS iPad app only for table management, so the mobile half of the claim is unevidenced in documentation. https://helpdesk.resy.com/en_us/resy-analytics-BJdQMvX8_ · retrieved 2026-08-04

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

Resy produces no daily close-out. Its POS reporting article enumerates the whole scheduled set — "Daily Forecast - sent daily and only for dinner shifts", "POS Trends Dashboard - sent weekly", "POS Overview - sent weekly" — and the daily one is a forward projection ("a projection of your expected sales and covers based on the previous five weeks of data along with anticipated no-shows, VIPs expected to dine, your spread of covers and confirmation status"), not a reconciliation of the day that closed. None of the components the claim names is reported against a business day: 'net sales', 'gross sales', 'close-out', 'end of day' and 'close of business' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance). Structurally there is nothing to reconcile — Resy runs no register, so there are no tender types, no drawer and no expected cash deposit; the money it does move (prepayments, deposits, cancellation and no-show fees) settles through Stripe on a payout schedule set in the Stripe Dashboard, outside any Resy document. https://helpdesk.resy.com/en_us/resyos-and-pos-reporting-SJRv9oy2O · 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

Corrected from an uncited `no`: an item-level product-mix report does exist. "POS: Product Mix" is a named Advanced Analytics report that "shows your most frequently ordered food items for First Time Diners, your Top Food Spenders, and Item Category Sales by Reservation Source", with a date-range filter and a filter "for unique POS Item categories"; the POS Trends Dashboard likewise "shows sales category trends and top selling items", and the help centre tells operators to "Check out the product mix and spend by sales category to inform menu planning, ordering, pricing and upselling" (https://helpdesk.resy.com/en_us/resyos-and-pos-reporting-SJRv9oy2O). NAMED SHORTFALLS, each of them required by the claim: there is no modifier dimension — Resy holds no modifier object at all, so modifier-level PMIX is not merely undocumented but unrepresentable; the item view is a "First Time Diners Top 10" segment ranking plus a category-by-source breakdown rather than a full item list carrying quantity, gross and net sales columns; and the only documented filters are date range and POS Item category, with no daypart and no revenue centre. The report is also gated to Platform 360 and depends on the POS integration, so the item and check data it reads are the connected POS's, not Resy's. https://helpdesk.resy.com/en_us/pos-product-mix-BkRm18xn6 · 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

Resy's documented multi-venue model is exactly the flat list the claim excludes. The Dashboard Booking article (Platform 360 only) describes the entire cross-venue surface as a switcher: 'The venue selector is in the top right corner to quickly toggle between different restaurants', 'toggle between different venues more efficiently'. No group, region or brand tier exists anywhere in the public help centre: the Reporting and Analytics article and the Resy OS FAQ contain zero occurrences of 'group', 'location' or 'multi', every documented report is per-venue, and the user-permissions article assigns per-action toggles to individual users with no venue- or group-scoping mechanism. Even the enterprise sales page (https://resy.com/join/hospitality-groups/) claims only two levels — 'manage reservations, guest data, reporting, and performance across all locations within a single system' and 'enterprise reporting' — and never names a middle tier or an org-hierarchy object. A named three-level hierarchy that reporting and permissions scope to is absent from both the documentation and the vendor's own enterprise pitch. https://helpdesk.resy.com/en_us/desktop-reservation-flow-SJEDlJNn2 · 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

There is no menu to author centrally and no publish action of any kind. Add-on items are created per venue in that venue's Item Library and scoped to that venue's shifts ("Applied To: Shows which shifts you have applied these items", https://helpdesk.resy.com/en_us/how-can-i-manage-add-on-items-S1vobw7UO); no corporate tier owns them, and no roll-out or push-to-locations action occurs in any of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance). Resy's own enterprise pitch marks the ceiling: hospitality groups get to "manage reservations, guest data, reporting, and performance across all locations within a single system", with "Multi-location reporting: Compare and manage performance across venues" and "Multi-location visibility: Easily access guest profiles across multiple venues" — visibility and reporting across venues, never authoring a record and pushing it down to a chosen set of them, and never a version history of what was pushed, when and by whom. The multi-venue affordance that is documented is the Platform 360 dashboard's venue selector, a flat toggle between restaurants. https://resy.com/join/hospitality-groups/ · 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

An Item Library entry carries exactly one price — the Item column "Shows the name of each item and their cost" — and no tier, zone, channel or daypart dimension hangs off it. 'price zone' and 'price tier' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance) and none of the 71 merchant pages; 'daypart' appears once on the merchant site, in /resources/ editorial. The documented way to charge two prices is to create two items ("you'll need to create an 'Adult Ticket' and 'Children's Ticket' item, which can be priced appropriately", https://helpdesk.resy.com/en_us/using-add-ons-to-offer-different-priced-event-tickets-ryEZ6SEc) — duplicating the record, which is what the claim excludes. Items are per-venue objects in the first place, so there is no location-group tier for a price to vary across, and Resy sells through one channel, its own booking flow, with no in-store or third-party channel to price differently. https://helpdesk.resy.com/en_us/how-can-i-manage-add-on-items-S1vobw7UO · 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

Resy confirms an API exists but publishes no reference for it, and the only offered path to integration is a sales conversation. The integrations page shows partner logos with 'Book a demo' / 'Schedule a demo today' CTAs and links no documentation; the hospitality-groups page asserts 'With an open API, webhooks, and integrations, Resy serves up your data' with nothing to read behind it; the plans-pricing table's 'Booking API' row (Platform 360 and Premium) likewise links no reference. Checked 2026-08-04: resy.com/developers and api.resy.com both serve or redirect to the consumer Angular shell at resy.com; developers.resy.com and dev.resy.com fail DNS resolution, consistent with the 2026-08-04 pass recorded on the OAuth cell (developers/developer/docs/partners subdomains all NXDOMAIN, api.resy.com/docs 302s to the consumer site); re-tested 2026-09-08 over the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance) — the earlier bound of "57 articles" was the curated llms.txt slice — 'API' occurs in three, none of them a reference: a static "Venue ID & API Key" that an operator pastes into BentoBox, and two passing mentions. No endpoint, parameter, schema or authentication contract is published anywhere. There is no public, self-serve API reference readable without a sales call — the widely used api.resy.com endpoints are community reverse-engineering, not vendor documentation. https://resy.com/join/integrations/ · retrieved 2026-08-04

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

OVERTURNED FROM `unknown`, on evidence the 2026-08-04 pass could not see: it searched 57 articles — the curated llms.txt slice — and concluded "zero contain 'OAuth', 'API key' or 'API'". Across the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance) both strings do appear, and what they show settles the claim against it. The one documented case of a third party authenticating TO Resy uses a shared static credential: BentoBox "is integrated with Resy and does not require the full widget code. You only need the Venue ID & API Key", which the operator copies out of the Resy Dashboard's widget page and pastes into BentoBox. That is a bearer key scoped to a venue, not an operator-granted OAuth grant, and nothing describes scopes, per-app consent, expiry or individual revocation. The corpus's only OAuth flow runs the other way and is Square's, not Resy's — enabling the Square integration sends the operator to an americanexpress.com partner-gateway /oauth link and then into Square's App Marketplace to "Follow the prompts to authorize" (https://helpdesk.resy.com/en_us/pos-integrations-square-Bk6NliyHJg), which is Resy authenticating as a client to Square. No OAuth authorization server, scope list or app-management surface is published on any Resy property, and developers.resy.com, developer.resy.com, docs.resy.com and partners.resy.com remain NXDOMAIN. https://helpdesk.resy.com/en_us/booking-button-installation-Skx_7ueNo · retrieved 2026-09-08

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

extensibility-webhooks-push

NEW SURFACE (2026-09-17, crt.sh on resy.com, 217 names): an anonymous OpenAPI 3.1 spec "Demand API" ("API for external partners", version 0.1.0) is served at https://partner-api.sandbox.resy.com/openapi.json with /docs and /redoc (49,254 bytes, 11 paths). It is a SANDBOX, pre-release copy: production partner-api.resy.com returns 404 on /openapi.json, /docs and /redoc, and the demo/staging hosts 403. Its paths are auth (B2B authenticate, account-link), availability search/calendar, venues/all, and three TEST endpoints that show Resy runs an outbound reservations webhook: POST /v1/test/webhook/receiver "Test Reservations Webhook ... :param payload: The reservation webhook payload (JSON)", POST /v1/test/webhook/validate "Validate stored webhook credentials and return an access token + headers" (body: webhook_id), and POST /v1/test/webhook/oauth/token "Local OAuth token endpoint for testing webhook credentials. Accepts JSON body matching Toast's authentication API format". No OpenAPI `webhooks` object, no event names and no payload schema are published. Why this stays unknown: (1) merge policy - a sandbox/pre-release spec may not carry the value, notes only; (2) the events are RESERVATION events, whereas the claim enumerates order lifecycle events (created, modified, paid, voided, refunded) that Resy, running no register, does not own - an adjacent feature, not part of the claim. Also found: webhook.demo/dev/staging.resy.com exist (Incapsula 503, no production webhook host in CT logs). Wayback CDX offline 2026-09-17. Retrieved 2026-09-17. || 330th: NEW SURFACES (330th), still unknown. (1) THE OPERATOR SITE HAS BEEN REBUILT AND MOVED: os.resy.com now 301s to www.resyos.com, which 301s to a new Next.js property at resy.com/join/ (204 KB, buildId pntstZbUt..., 20 routes incl. /join/integrations/, /join/platform-security/, /join/plans-pricing/). Its assets are served from tock-public.imgix.net and the header banner reads "Tock is now part of the Resy network"; the footer now carries TWO products and TWO help desks -- "Help desk: Resy: Resources for Platform & Platform 360 plans" (helpdesk.resy.com) and "Help desk: Resy powered by Tock: Resources for Essential & Premium plans" (dashboard.exploretock.com) -- plus separate "Resy Merchant Terms of Service" and "Tock Merchant Terms of Service". Nothing in the atlas record covers the Tock-side platform. (2) /join/integrations/ is the first published statement of what Resy's POS integration actually does, and it is INBOUND, not an outbound order-event push: "POS & Event Systems: Sync reservation and check data in real time to understand guest spend, optimize table turns, and improve accuracy across service. Send down payment information, including prepayment and deposits ... Turn tables more efficiently with real-time course statuses." The page's own FAQ JSON-LD: "Does Resy integrate with POS systems? Yes, Resy's guest management platform integrates with POS systems, CRM, reporting, and analytics tools". Partner logos include aloha, heartland, commerce-7, fishbowl. This is a marketing page (grade C) and, per merge policy, a partner registry bounds partners, not features. (3) THE PRODUCTION PARTNER API WAS RE-PROBED WITH CURL (not node fetch) today: partner-api.resy.com/openapi.json, /docs and /redoc all return 404 (22-byte body), so the prior note's finding stands and is not a node-fetch artefact; partner-api.sandbox.resy.com/openapi.json still serves the same byte-identical 49,254-byte Demand API 0.1.0 spec. pos.resy.com, transaction.resy.com, item.resy.com and inventory.resy.com (production CT names) all 302 to resy.com/ and serve no spec; rgs.resy.com no longer resolves. WHY IT STAYS UNKNOWN: unchanged from the prior pass -- Resy runs no register, so the order-lifecycle events the claim enumerates (created, modified, paid, voided, refunded) are events it consumes from the operator's POS rather than emits, and the only webhook surface it publishes is reservation-shaped and sandbox-only. The new integrations page strengthens that reading rather than settling the cell. Retrieved 2026-09-18. adversarially verified

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

extensibility-webhook-reliability

Not scored by this record.

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

extensibility-order-injection-api

Not scored by this record.

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

Resy OS's documented answer to lost connectivity is to restore connectivity, not to keep working without it. The troubleshooting article's remedies are "Try connecting to a different WiFi network or Mobile HotSpot", "Check your internet speed. Perform an internet speed test", "Clear your cache in the app by tapping Venue Name > Settings > About > Clear Cache", and force-restarting the iPad; the browser-side article says "Make sure you are connected to the internet. Try a different network and/or hotspot" (https://helpdesk.resy.com/en_us/troubleshooting-common-issues-S10dQb2rbg). No offline, degraded, cached or store-and-forward mode is described anywhere, and 'cached', 'outage' and 'failover' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance). NOTE ON THE WORD: 'offline' occurs six times in the corpus and every instance is Resy's term for availability that is not bookable online — taking a shift, a table or Global Dining Access inventory "offline" — never a network state. Structurally there is also no order entry to continue: Resy takes reservations, not orders, and holds no check of its own. https://helpdesk.resy.com/en_us/resyos-troubleshooting-steps-ByjDtVwBK · 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

Resy does print, but not to the kitchen and not offline by design. The only printing it documents is a reservation chit from the host stand: "You can print a chit from the guests reservation profile in ResyOS", carrying "Guest name", "Reservation details such as date and time, party size and table type and number", "Guest and Visit Tags", "Guest and Visit Notes" and "Add On Item Name and Quantity (not price)" — a seating slip, with the money explicitly stripped out of it. There is no kitchen routing to continue: 'KDS' and 'kitchen display' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance) (the merchant site's four hits are /resources/ editorial about POS systems generally), no station, prep-area or route object exists, and Resy holds no order to route. The printer itself is a Bluetooth Star Micronics paired to one iPad, and its documented failure handling is manual reconnection rather than offline queueing (https://helpdesk.resy.com/en_us/resyos-recommended-hardware-and-accessories-SyvVbP78_). https://helpdesk.resy.com/en_us/troubleshooting-for-bluetooth-chit-printers-rycyGwXId · 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

The vendor's own article on an unreachable printer is the decisive evidence, and it prescribes people rather than failover. "Chit Printing in the ResyOS App" enumerates why the printer drops — "Bluetooth printers may lose connection for any of the following reasons: 1. Paper is low or out. 2. The iPad is too far from the printer. (Maximum of 15 feet away) 3. Bluetooth has been disabled on the iPad. 4. The printer is not set to automatically reconnect to the iPad." — and answers with a manual checklist ("Check the printer for any error lights. Make sure the paper isn't low and the paper port is comp[letely closed]"). No backup printer is nominated, nothing reroutes, and no alert is raised to staff: 'backup printer', 'failover', 'fails over' and 'reprint' occur in none of the 204 public help-centre articles (the helpdesk sitemap’s 199 en_us articles plus 5 more referenced only from article bodies, all fetched 2026-09-08 as Markdown via the published `<url>.md` affordance). There is also no second destination to fail over TO — Resy documents one chit printer paired per iPad, and no KDS station exists in the product. https://helpdesk.resy.com/en_us/troubleshooting-for-bluetooth-chit-printers-rycyGwXId · 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

The Resy Merchant Terms of Service are public and linked from the pricing page footer. Section 6.1: 'After the expiration of the Initial Term, this Agreement shall automatically renew for additional successive Renewal Terms as specified on the Order Form ... unless either party notifies the other party of non-renewal at least 30 days prior to the expiration of the Term as specified on the Order Form.' Shortfall: the cancellation notice window is published (30 days) but the renewal term length is not — both the Initial Term and each Renewal Term are deferred to the signed Order Form, as are any termination fees ('any termination fees charged pursuant to the Order Form'). The help centre reinforces this, routing 'Upgrade contract terms (i.e., monthly to yearly)' and 'Contract Changes' to a Restaurant Success Manager rather than to published terms. https://cloud.send.resy.com/terms · 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

OVERTURNED FROM `unknown`. The prior pass recorded "resy.com/for-restaurants returned no readable content at check time", but resy.com is a soft-200 catch-all — every path on that host, including invented ones, returns the same 237-character Angular shell — so that was a dead path, not an absent page. The merchant site lives at resy.com/join/, with its own robots.txt and sitemap, and its pricing page publishes four named plans at specific dollar figures: Platform "$289 /month", Essential "$289 /month" (Powered by Tock), Platform 360 "$459 /month" and Premium "$459 /month", with prepayment fees stated per plan ("3% fee on prepayments", "2% fee on prepayments") under the footnote "Standard payment processing fees will apply". Each plan carries a self-serve "Get Platform" / "Get Essential" / "Get Platform 360" / "Get Premium" button rather than contact-sales only, and the page's FAQ states "Resy pricing is transparent with no per-cover fees. We do not charge any fees on a per reservation basis" and "Each month, you pay one monthly fee". Per-additional-terminal pricing is not published because Resy sells no terminal — operators buy iPads and chit printers at retail. Grade C: this is the vendor's own marketing and pricing page. https://resy.com/join/plans-pricing/ · retrieved 2026-09-08

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

Resy sells no hardware and leases none. The hardware article specifies commodity kit the operator buys at retail: iPad Pro 12.9" or iPad 9.7"-or-larger on iOS 15+, named cases/keyboards/stands, a Lightning-to-USB3 plus USB-to-Ethernet adapter for hardwiring, and Star Micronics chit printers (TSP143IIIBi, MCP31LB, TSP650II BTi, TSP654IIBi2, TSP100 series). It explicitly directs purchase to third-party retail — 'We encourage you to buy a Certified Refurbished iPad for cost savings directly from the Apple Store, or obtain one from another retailer like Walmart or Target' — so all required devices are outright purchases at publicly listed retail prices with no Resy hardware lease or rental. No KDS or terminal is required because Resy is a reservations and table-management product, not a register. https://helpdesk.resy.com/en_us/resyos-recommended-hardware-and-accessories-SyvVbP78_ · retrieved 2026-08-04

Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator

commercial-hardware-not-locked

Not scored by this record.

One-time implementation, menu-build, onboarding, and training fees are published as specific amounts or explicitly stated as $0.

commercial-implementation-fee-published

Not scored by this record.

Operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee.

commercial-data-export-self-serve

Not scored by this record.

Guest/customer records, loyalty balances or point ledgers, and gift-card liability balances are exportable in machine-readable form by the operator. differentiator

commercial-export-customer-and-loyalty

Not scored by this record.

Contract or documentation specifies a post-termination data retrieval window (a defined number of days during which the operator can still export their data) rather than immediate cutoff. differentiator

commercial-post-termination-export-window

Not scored by this record.

Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator

commercial-data-ownership-clause

Not scored by this record.

The POS is source-available or open source with a documented self-hosting option (source published under an OSI or source-available license, not merely an open API).

commercial-source-available-selfhost

Not scored by this record.

Vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A / SAQ P2PE-HW, and names the applicable SAQ.

commercial-pci-p2pe-tokenization

Not scored by this record.

Vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — notably MFA for all access to the cardholder data environment including POS and back-office logins, and (for hosted ordering pages) payment-page script integrity monitoring per Req 6.4.3/11.6.1.

commercial-pci-dss-4-controls

Not scored by this record.

Vendor states it holds a current SOC 2 Type II (or ISO 27001) attestation and will provide the report under NDA via a trust center or on request.

commercial-soc2-attestation

Not scored by this record.

Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.

commercial-privacy-dsar-tooling

Not scored by this record.

Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator

commercial-wcag-kiosk-accessibility

Not scored by this record.

POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator

commercial-dual-pricing-compliant

Not scored by this record.