Toast

Provides a graphical floor-plan editor where an operator can draw sections, place tables of varying shape/capacity, save multiple floor-plan layouts per location, and assign sections to servers.

order-capture-floor-plan-editor

Table service floor plan with sections and server assignment is core Toast FSR functionality; specific doc page not retrieved this pass.

Order lines can be tagged to a seat number at entry, and the check can be split by seat afterward without re-keying items.

order-capture-seat-level

Seat-numbered ordering and split-by-seat are standard Toast table service behavior; not verified against a doc page.

Items can be assigned to courses and held, with a fire-next-course action available from a handheld or terminal that releases only that course to the kitchen.

order-capture-coursing-hold-fire

Coursing with hold and fire-next-course from terminal or handheld; KDS docs confirm the firing half. https://doc.toasttab.com/doc/platformguide/platformKDSOverview.html · retrieved 2026-08-01

Supports splitting a check by item, by seat, by even N-way, and by arbitrary dollar/percentage amount, and merging checks or tables back together, including after partial payment.

order-capture-split-merge

Split by item, seat, even N-way and amount supported. Merge after partial payment not verified.

Opens a bar tab against a card pre-authorization with a configurable auth amount, supports incremental re-auth as the tab grows, and auto-closes stale tabs at end of day. differentiator

order-capture-bar-tab-preauth

Card pre-authorization is a documented Toast feature (called out as unavailable offline). Incremental re-auth and automatic stale-tab close not documented. https://doc.toasttab.com/doc/platformguide/adminOfflineCCPayments.html · retrieved 2026-08-01

An open check can be transferred between servers, tables, and devices, and the transfer is recorded in an audit log naming both employees.

order-capture-transfer-audit

Check transfer between servers and tables is standard; audit-log naming both employees not verified.

Ships a first-party handheld ordering app running natively on the handheld device (not a remote/mirrored desktop session) that can send to kitchen and take a card payment tableside.

order-capture-native-handheld

Toast Go 3 is a first-party native handheld with integrated reader that fires to kitchen and takes payment tableside. https://pos.toasttab.com/hardware/toast-go · retrieved 2026-08-01

With the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen, and tender cash, and the vendor publishes what does and does not work offline.

order-capture-offline-order-entry

Offline order entry, cash tender, printing and (with local sync) KDS routing all documented, with an explicit unavailable-features list. https://doc.toasttab.com/doc/platformguide/adminOfflineModeOverview.html · retrieved 2026-08-01

Guest QR at-table ordering writes items onto the same open check as server-entered items, rather than creating a separate order ticket. differentiator

order-capture-qr-same-check

Toast Order & Pay supports scan-to-order and scan-to-pay at table; that guest items land on the same server-opened check was not verified in docs.

Offers a first-party self-order kiosk that renders the same menu and modifier tree as the POS with no separate menu build, and the vendor documents ADA/accessibility conformance for it. differentiator

order-capture-kiosk-first-party

First-party Toast Kiosk runs the same POS menu and modifier tree. No ADA/WCAG conformance report or VPAT located. https://pos.toasttab.com/hardware · retrieved 2026-08-01

Supports drive-thru-specific order flow: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment.

order-capture-drive-thru

Toast Drive-Thru launched April 14, 2026 as a unified hardware + POS-native software solution. Order-point/pay-window separation and tandem-lane assignment not enumerated publicly. https://pos.toasttab.com/news/toast-drive-thru-launch-2026 · retrieved 2026-08-01

Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.

order-capture-drive-thru-timers

Speed of Service (SoS) reporting ships with Toast Drive-Thru to identify lane bottlenecks. Per-segment timers tied to individual orders not documented. https://pos.toasttab.com/news/toast-drive-thru-launch-2026 · retrieved 2026-08-01

Vendor ships a first-party AI voice ordering agent for phone and/or drive-thru that injects orders directly as POS orders, or publishes a documented API partner program for third-party voice AI. differentiator

order-capture-voice-ai

Not first-party. Incept AI is a named certified integration for phone and drive-thru order taking; Toast says more voice partners follow in 2026. https://support.toasttab.com/en/article/Get-Started-With-InceptAI-Integration · retrieved 2026-08-01

Supports order throttling: per-channel capacity limits per time slot with automatic quote-time extension when kitchen load exceeds a configured threshold. differentiator

order-capture-throttling

Manual delay/snooze in 5-minute increments up to 120 minutes plus per-slot order caps. Automatic quote extension triggered by measured kitchen load not documented. https://support.toasttab.com/en/article/Managing-Online-Order-Volume-Throttling-Orders-1492627940253 · retrieved 2026-08-01

Accepts future-dated/scheduled orders with a per-channel lead time and automatically injects them into the make queue at a computed fire time rather than on receipt.

order-capture-scheduled-orders

Scheduled/pre-orders with per-channel lead times; Toast documents how online orders are fired into the make queue rather than on receipt. https://doc.toasttab.com/doc/platformguide/adminFiringToastOnlineOrders.html · retrieved 2026-08-01

Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.

order-capture-catering

Toast Catering & Events runs lead form to BEO to kitchen sheet to paid invoice, with catering-specific hours, lead times, minimums and capacity. https://support.toasttab.com/en/article/Getting-Started-Catering-and-Events · retrieved 2026-08-01

Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator

order-capture-order-ready-signal

The inference chain does check out on DoorDash's side - the 2026 DPIP standards require order-ready notifications and Toast is in the 2026 cohort - but that establishes the capability only for the DoorDash channel, via a third party's program requirements, with no Toast documentation of an order-ready signal for Uber Eats, Grubhub, or first-party pickup. Partial, not yes. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-01 adversarially verified

Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.

order-capture-void-comp-controls

Void reasons are a shared MLM configuration object; manager approval and exception reporting are standard Toast behavior but not verified page-by-page.

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

Nested modifier groups with min/max and required flags. Caveat: nested subgroups do not render on third-party marketplace menus. https://support.toasttab.com/en/article/Creating-Modifier-Groups-and-Modifiers-1492803987509 · retrieved 2026-08-01

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

Re-pointed off the dead adminPortionsAndPricing.html to the live pricing-strategies set. Size price "Applies to: Menu items, modifier groups, modifier item references": on a modifier group's details page you set "How are modifiers in this group priced" to "All modifiers share the same price", select Size Price, and fill a grid whose rows are size/price pairs, so "all of the toppings in a Toppings modifier group cost $0.50 for a small pizza, $1 for a medium pizza, and $1.50 for a large pizza" with one modifier, not duplicates. Set "Each modifier has a unique price" instead and each modifier's item reference carries its own Size Prices grid ("pepperoni costs $1 on a small pizza and $2 on a large"). Size/Sequence Price adds the second axis (size by 1st option / 2nd option / all additional options). Parent-item variation comes from the same underlying item reference being priced separately per modifier group, or per modifier via the "Override item reference price" setting. Caveat: for modifier groups and modifiers these strategies are not supported on the Toast Takeout (Local by Toast) app or Toast Order and Pay. https://doc.toasttab.com/doc/platformguide/adminSizePrice.html · retrieved 2026-08-08 adversarially verified

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

menu-pricing-fractional-placement

Verified myself against Toast platform docs: "Modifiers can be applied to menu items in portions, for example, a one-half portion of a topping can be applied to either the first or second half of a pizza." This is a real native per-section portion model, not a duplicated-modifier workaround. https://doc.toasttab.com/doc/platformguide/adminPortionsOverview.html · retrieved 2026-08-01 adversarially verified

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

The cited page returns HTTP 403 to retrieval, so I could not confirm it directly. However the Price Multiplier field (0-100, max 2 decimals, set on the portion) is corroborated from doc.toasttab.com/doc/platformguide/adminConfiguringPortions.html. Still only one pricing lever - no average-the-halves or charge-higher-half rule found. Partial stands; note the researcher's cited URL is not publicly retrievable. https://doc.toasttab.com/doc/platformguide/adminConfiguringPortions.html · retrieved 2026-08-01 adversarially verified

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

Toast pre-modifiers (NO, SUB, ADD, EXTRA, ON SIDE) are prefix/suffix tiers applied to a modifier, and each pre-modifier option carries either a Multiply Price? factor - "If the Multiply Price? setting is set to two (2), it would double the price of a modifier", set it to 0 for NO - or a mutually exclusive fixed price such as $0.50. This is a per-tier multiplier on one modifier, distinct from adding the modifier twice: repeating a modifier is a separate mechanism requiring modifier-level multi-select and duplicate modifiers to be enabled. https://support.toasttab.com/en/article/Pre-Modifiers-1493068611745 · retrieved 2026-08-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

Size-axis pricing is documented; a two-axis size x crust grid with per-cell override is not. Operators typically model crust as a separate item or modifier.

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

Toast's Sequence modifier pricing strategy prices modifiers "by the sequence in which they are added to a menu item. For example, on a pizza menu item with a Toppings modifier group, the first topping is free, the second topping costs $1.00, the third topping costs $1.50, and all additional toppings cost $2.00" - overage-only charging. Shortfalls: it is expressed as a per-position price ladder, not a declared 'N included' allowance with a substitution credit-or-forbid rule, and Toast states the Sequence, Size and Size/Sequence strategies "are not supported on the Toast Takeout (Local by Toast) app, Toast Order and Pay, and Toast Kiosk." https://doc.toasttab.com/doc/platformguide/adminPricingModifierOptions.html · retrieved 2026-08-08

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

Combo is a Toast discount type configured against "one or more eligible combinations of items" (adminDiscountsConfigureCombo.html), and Combo discounts are explicitly listed as eligible for auto-apply: "An auto-apply discount is applied if the items on the check match the selection criteria of the discount, without any action from a restaurant employee" - the automatic a-la-carte-to-combo conversion the claim describes. Shortfalls: no component-swap-with-price-delta mechanism is documented (a Toast combo is a discount over an item combination, not a built meal with swap deltas); "Discounts can only be applied automatically to checks that are created or updated on the Toast POS app", so not online ordering; and "If you apply a combo discount to a check that includes more than one of the same menu item... the discount applies to only one of the items." https://doc.toasttab.com/doc/platformguide/adminAutoApplyDiscounts.html · retrieved 2026-08-08

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

Digital upsell prompts exist in Toast Online Ordering; per-channel configuration and vendor-reported attach-rate not verified.

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

86 propagates within Toast (POS, KDS, Toast Online Ordering). For marketplaces Toast states the ordering partner controls whether 86'd items are respected. No published propagation latency. https://support.toasttab.com/en/article/Uber-Eats-DoorDash-and-Grubhub-Integration-Configuration-Limitations · retrieved 2026-08-01

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

"After you manually set the Quantity status for a menu item, the quantity amount is automatically decreased by the Toast platform each time you order that menu item", and "When the quantity amount reaches 0 (zero), the Toast platform automatically changes the inventory status to Out of Stock for the menu item." Scheduled restore is documented separately: "You can create stock refresh schedules that automatically refresh a menu item or modifier's stock status and quantity (count) on a defined schedule" (plartformAutomaticallyRefreshingInventory.html). https://doc.toasttab.com/doc/platformguide/adminMenuItemInventoryOverview.html · retrieved 2026-08-08

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

Time-specific pricing and scheduled menu/item availability documented. Note it does not sync to third-party marketplaces. https://support.toasttab.com/en/article/Get-Help-with-Third-Party-Ordering-Price-Incompatibilities · retrieved 2026-08-01

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

Distinct prices per third-party channel are configurable, and menu versions cover dine-in vs off-premise. https://support.toasttab.com/en/article/Get-Help-With-Third-Party-Ordering-Integration-Pricing · retrieved 2026-08-01

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

Toast Cash Discounting shows one advertised price with a cash discount at tender, rather than storing two item-level prices. Digital wallets are treated as cards and excluded. https://support.toasttab.com/en/article/Toast-Cash-Discount-Overview · retrieved 2026-08-01

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

Toast stores structured per-item allergens: "select the applicable allergens for the menu item from the drop-down list of pre-defined options. Note: This is a pre-defined list of allergens and is not customizable." They publish to "Online Ordering, Toast Mobile Order & Pay, Catering Online Ordering, Kiosk, Tables, Local by Toast, and Branded Apps." Shortfalls: no per-item nutrition or calorie field is documented - the 465-page doc.toasttab.com platform guide inventory I crawled contains no Nutrition, Calorie or Recipe page at all; no derivation of nutrition from linked recipe components; and third-party marketplace menus (DoorDash, Uber Eats) are not among the listed allergen destinations. https://support.toasttab.com/en/article/Add-Allergen-Information-to-Online-Ordering-Menu-Items · retrieved 2026-08-08

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

xtraCHEF links recipes to Toast POS items, giving real-time plate costing, inventory depletion and theoretical food cost. https://support.toasttab.com/en/article/xtraCHEF-Get-Started-With-Actual-vs-Theoretical-Analysis-Reports · retrieved 2026-08-01

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

Direct certified push to DoorDash, Grubhub, Uber Eats, Deliveroo and Skip. Toast documents which menu features silently fail to sync, but a per-item sync-status/rejection view for operators was not found. https://support.toasttab.com/en/article/Get-Help-with-Third-Party-Ordering-Price-Incompatibilities · retrieved 2026-08-01

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

menu-pricing-dynamic-pricing

Toast supports Time Specific Price on menu groups and items - "you define the price of a menu group or item during specific times of the day. For example, a menu item that costs $10 between noon and 2pm and $12 during the rest of the day" - with a Base Price used outside the defined windows, alongside Menu Specific Price and Location Specific Price levels, so price does vary automatically by time and by menu/channel. Shortfalls: pricing is calendar-scheduled, not demand-responsive; the platform guide's complete price-strategy set (Base, Fixed, Open, Sequence, Size, Size/Sequence, Time Specific, Menu Specific, Location Specific) takes no demand or utilisation input and exposes no floor/ceiling guardrail fields; and overlap safety is left to the operator ("Be careful to avoid overlapping time-specific prices"). https://doc.toasttab.com/doc/platformguide/adminTimeSpecificPrice.html · retrieved 2026-08-08

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

Upgrade the evidence, not the score. This should never have rested on review sites: Toast's own Payment Processing Terms state the merchant "agrees to utilize Toast as its exclusive provider of Payment processing services," and support docs tell switchers to have their prior processor disabled. Vendor-affirmed absence, so 'no' is legitimate rather than 'not documented'. https://pos.toasttab.com/payment-processing-terms · retrieved 2026-08-01 adversarially verified

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

payments-published-rates

NOTE ONLY, no change of value -- the 403 on this URL is a CLIENT fingerprint, not a refusal, and the page still says what the cell records. Re-probed 2026-09-17: curl with a browser UA plus Accept/Accept-Language ALONE still returns 403 (3,366 bytes, a Cloudflare 'Just a moment... Enable JavaScript and cookies to continue' interstitial), and a nonsense sibling path returns the same 403 interstitial at 3,320 bytes, so the naive re-probe proves nothing either way. Adding the Chrome fetch-metadata headers (sec-fetch-mode: navigate, sec-fetch-dest: document, sec-fetch-site: none, upgrade-insecure-requests: 1, sec-ch-ua) on the SAME url flips it to 200 at 105,438 bytes (10,163 chars stripped, page footer 'This page was last updated on: July 16, 2026'). Content confirms the verdict verbatim: 'Custom pricing. Zero confusion. Our goal at Toast is to provide our customers with a clear and transparent payment processing rate - no hidden fees, no bait and switch, no unexplained rate hikes; what you see in your quote is exactly what you'll get. We'll work with you to build a custom rate specific to the characteristics of your restaurant.' The page explains interchange, network fees, issuing bank, card network, PCI compliance and merchant bank as fee COMPONENTS and distinguishes card-present from card-not-present pricing, but publishes no rate, no markup and no per-transaction figure. For future sessions: pos.toasttab.com needs sec-fetch-* headers, not just a UA. Retrieved 2026-09-17. https://pos.toasttab.com/payments/payment-processing-fees · retrieved 2026-09-17 adversarially verified

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

Cash Discounting is single-advertised-price with a discount at cash tender, not two stored prices printed side by side. https://support.toasttab.com/en/article/Toast-Cash-Discount-Overview · retrieved 2026-08-01

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

Debit and prepaid identified by BIN and automatically excluded; 3% card-brand cap enforced; enabled per location and only in eligible US states; tips and taxes not surcharged. https://support.toasttab.com/en/article/Credit-Card-Surcharging-FAQ · retrieved 2026-08-01

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

payments-emv-nfc

Toast terminals accept EMV chip and NFC; Apple Pay, Google Pay and Samsung Pay are explicitly treated as card transactions. https://support.toasttab.com/en/article/Toast-Cash-Discount-Overview · retrieved 2026-08-01

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

payments-softpos-tap-to-pay

No phone-as-reader acceptance. Toast's merchant-side acceptance devices are enumerated twice, and every entry is Toast-supplied hardware with a physical reader. The cited article 'Accept Apple Pay, Google Pay, or Samsung Pay With Toast' (support.toasttab.com, stamped Aug 28 2026, 1,993 chars stripped, re-retrieved 2026-09-15 HTTP 200) answers 'Which Toast devices support Apple Pay, Google Pay, and Samsung Pay?' with Toast Tap (On-Counter and Direct Attach) and Toast Go 2, and closes 'Apple Pay, Google Pay, and Samsung Pay are not accepted on Magtek eDynamo devices such as Toast Go 1 and directly on the Toast tablet (POS).' CORRECTION: that list is NOT closed - it omits the Toast Go 3, which Toast ships (two Go 3 articles in the help sitemap) and which the fresher, explicitly matched-pair enumeration in 'Take Payments on the POS' (support.toasttab.com/en/article/Taking-Payments, Aug 20 2026, retrieved 2026-09-15 HTTP 200) lists as wallet-capable: 'Devices that accept mobile wallet payments: Toast Go 2 / Toast Go 3 / Toast Tap (on-counter or direct-attach)' against 'Devices that do not accept mobile wallet payments: Toast Go 1 / The Toast tablet'. That article is what the no now rests on, and it states the mechanism: 'Ask the guest to tap their phone or watch on the card reader's NFC zone' - the phone is always the GUEST's payment instrument presented to a Toast reader, never the merchant's acceptance device. It applies itself to 'Toast Flex terminal, Toast Go 2, Toast Go 3, and Toast Tap (on-counter or direct-attach)'. Corroborated by 'Identify Your Toast Hardware' (Sep 9 2026), a self-described glossary of every Toast hardware class - terminals, guest displays, KDS, handhelds, printers, card readers, accessories, network - with no commodity-phone acceptance option, and by the approved-hardware clause on pos.toasttab.com/pricing ('may only be used on approved Toast hardware'). https://support.toasttab.com/en/article/Which-Toast-devices-support-Apple-Pay-Google-Pay-and-Samsung-Pay · retrieved 2026-09-15 adversarially verified

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

Toast Go 3 handheld takes EMV/NFC at the table with tip prompt and splitting. https://pos.toasttab.com/hardware/toast-go · retrieved 2026-08-01

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

Toast documents a "receipt QR code payment experience" alongside Don't Wait to Pay, and confirms automatic settlement: "the guest's table changes from yellow to white once the guest's payment has been completed". Mobile Order & Pay separately documents scanning a QR at the table to order and pay. https://support.toasttab.com/en/article/Don-t-Wait-to-Pay-Overview · retrieved 2026-08-02 adversarially verified

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

Unsourced. The pre-auth-then-adjust flow, batch window, and unadjusted-tips manager screen are all non-obvious and unverified. adversarially verified

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

Toast Tips Manager computes pooled tips from POS data and syncs allocations directly into Toast Payroll, replacing spreadsheets. https://support.toasttab.com/en/article/Toast-Payroll-Tips-Manager-Setup · retrieved 2026-08-01

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

Cards are encrypted and stored on device, then submitted on reconnect. An optional per-transaction offline limit can be set, above which a manager override is required. Devices enter offline mode ~40s after losing connectivity. https://support.toasttab.com/en/article/Prepare-to-Operate-in-Offline-Mode-During-Service-Disruptions-or-Outages · retrieved 2026-08-01

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

Liability is stated plainly: 'You are responsible for any declined, expired, or disputed payments taken in Offline Mode,' and authorizations may expire within 24 hours. A dedicated post-reconnect failed-payment report is not documented. https://support.toasttab.com/en/article/Prepare-to-Operate-in-Offline-Mode-During-Service-Disruptions-or-Outages · retrieved 2026-08-01

First-party gift cards with real-time balance tracking, redeemable across every location in the group and through the online-ordering channel.

payments-gift-cards

First-party Toast gift cards clearly exist (they are named in the offline-unavailable list), but group-wide and online redemption - the parts that matter - are explicitly unverified by the researcher. https://doc.toasttab.com/doc/platformguide/platformOfflinePaymentsOverview.html · retrieved 2026-08-01 adversarially verified

House/on-account tabs with per-account credit limits, running balance, and periodic statement or invoice generation.

payments-house-accounts

House accounts exist as a Toast tender type (documented as unavailable offline). Per-account credit limits and statement/invoice generation not verified. https://doc.toasttab.com/doc/platformguide/platformOfflineModeLocalSync.html · retrieved 2026-08-01

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

Multi-tender settlement with split by seat, item, even shares and amount; no evidence of a cap below eight.

Voids, refunds, discounts, and no-sales require role-based authorization (manager PIN or approval) and write to an immutable audit log identifying the approver.

payments-refund-void-controls

Role-gated voids, refunds and discounts with reason codes; immutability of the audit log not verified.

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

payments-chargeback-tooling

Toast Web Reports > Payments > Chargebacks lists chargebacks with status (including New), amount, reason, check date and response deadline, plus a Win Likelihood estimate. Disputes are filed inside the product: the flow provides an explanation field and a "Supporting documents" upload, then a Confirm step, with the warning that "disputes cannot be edited or amended after submission." A Chargebacks Report also appears in Toast's finance report catalog. https://support.toasttab.com/en/article/Disputing-Chargebacks-in-Toast-s-Back-End · retrieved 2026-08-08

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

Toast Online Ordering: "Guests can create an account before or during checkout and save a credit card for future use. At checkout, guests choose between Express checkout with Toast (uses saved information) or Checkout as guest." Separately, for Catering & Events, "Guests must opt in to saving their card during the deposit payment process" and staff later see a "Charge saved card ending in XXXX" button on the POS. Merchant PAN storage is ruled out: Toast states the platform stores only "the last four digits of a credit card number" and that cardholder data must only be entered into the Toast payment field. Shortfalls: no documentation describes one guest-profile token reusable across online ordering, phone orders and in-store - the two saved-card paths are channel-specific - and the public articles never use the word tokenization (the developer guide's PARTNER_VAULT cardNumberOrigin covers partner-held credentials, not a Toast guest vault). doc.toasttab.com/doc/platformguide/adminSavedCreditCards.html still returns HTTP 403. https://support.toasttab.com/en/article/Online-Ordering-FAQ · retrieved 2026-08-08

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

payments-payout-timing

Toast publishes the schedule with a named cutoff: batches closed before 9:30 p.m. ET produce a deposit that "arrives next business day"; after 9:30 p.m. ET, or via the 4 a.m. auto-batch, the "deposit arrives two business days later". Toast adds that "Most restaurants' service hours extend past 9:30 p.m. ET, which means deposits typically take two business days instead of one", and excludes federal banking holidays. Faster funding exists as a separate product, Instant Deposit, whose transactions and fees are reported in Toast Web (Instant Deposit Reporting Overview) and which appears alongside standard payouts in the Reconciliation report. https://support.toasttab.com/en/article/When-are-deposits-made-to-my-bank-account · retrieved 2026-08-08

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

Toast states it is a PCI-DSS-compliant Level 1 Service Provider assessed by a QSA and provides PCI Responsibility Guides on request. No published validated P2PE listing or v4.x AOC located. https://support.toasttab.com/en/article/What-is-PCI-Compliance · retrieved 2026-08-01

Items route to specific KDS stations by item, category, order type, or revenue center, with routing rules configurable per location without vendor involvement.

kitchen-station-routing

Prep stations (Grill, Salad, Bar, Pizza) with routing by item, dining option and service area, configurable by the operator. https://doc.toasttab.com/doc/platformguide/adminRoutingOrdersKitchen.html · retrieved 2026-08-01

An expo screen consolidates items from multiple prep stations into a single order view and only marks the order complete when every contributing station has bumped its items.

kitchen-expo-consolidation

Expediter screen shows the whole order across stations; the ticket turns green only when every prep station has fulfilled its items. https://doc.toasttab.com/doc/platformguide/adminUsingExpo.html · retrieved 2026-08-01

Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator

kitchen-course-firing

Items assigned to courses, held, then fired; fired items route to expo and the relevant prep stations. https://doc.toasttab.com/doc/platformguide/platformKDSOverview.html · retrieved 2026-08-01

Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator

kitchen-prep-time-pacing

KDS ships 'automated firing by prep time' so items are staggered to finish together. https://support.toasttab.com/en/article/Get-Started-With-the-Kitchen-Display-System · retrieved 2026-08-01

Kitchen load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator

kitchen-order-throttling

Order caps and manual delay/snooze extend quote times, but throttling is operator-triggered or capacity-configured, not automatically driven by measured KDS ticket times. https://support.toasttab.com/en/article/Managing-Online-Order-Volume-Throttling-Orders-1492627940253 · retrieved 2026-08-01

Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator

kitchen-channel-pause-propagation

Toast pushes availability to marketplaces, but explicitly states the ordering partner decides whether menu visibility and availability settings are respected. https://support.toasttab.com/en/article/Uber-Eats-DoorDash-and-Grubhub-Integration-Configuration-Limitations · retrieved 2026-08-01

Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator

kitchen-order-ready-callback

Same single-channel inference. No Toast doc shows a KDS bump firing an order-ready callback to marketplaces generally. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-01 adversarially verified

KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.

kitchen-bump-bar-hardware

Marketing hardware page only, with the researcher conceding no supported-model list. A hardware-compatibility 'yes' on marketing copy is exactly the failure mode to avoid. https://pos.toasttab.com/hardware/kitchen-display-system · retrieved 2026-08-01 adversarially verified

An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.

kitchen-all-day-counts

All Day View with production item counts is a listed KDS feature. https://support.toasttab.com/en/article/Get-Started-With-the-Kitchen-Display-System · retrieved 2026-08-01

Configurable target cook times per station or order type, with visual color escalation and/or audible alert when a ticket exceeds target.

kitchen-sla-alerts

Color-coded ticket escalation plus SMS and in-app alerts are listed KDS features. https://support.toasttab.com/en/article/Get-Started-With-the-Kitchen-Display-System · retrieved 2026-08-01

If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator

kitchen-printer-fallback

Adding a kitchen printer in Toast exposes a "Backup" printer selection among its configurable fields, and the guide states: "If printing fails at this printer, the system redirects tickets to the backup printer." Caveat recorded rather than scored: platformKitchenPrintersOffline.html describes a local-network outage in which "The Toast POS device cannot send tickets to the kitchen printers", with the only named recovery being autofiring of queued online orders once connectivity returns - so the designated-backup failover covers printer/device failure, not a whole-network outage. https://doc.toasttab.com/doc/platformguide/adminAddKitchenPrinter.html · retrieved 2026-08-08

KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator

kitchen-offline-operation

Under offline mode with local sync, KDS devices receive orders from every POS device on the LAN via a local hub device while the internet or Toast cloud is unreachable. https://doc.toasttab.com/doc/platformguide/platformOfflineModeLocalSync.html · retrieved 2026-08-01

Station screens can display item-level build/assembly detail (recipe steps, portioning, or full modifier breakout) rather than only the ticket line text. differentiator

kitchen-item-build-screens

Color-coded modifiers give full modifier breakout on station screens. Recipe steps or portioning instructions on the KDS not documented. https://support.toasttab.com/en/article/Get-Started-With-the-Kitchen-Display-System · retrieved 2026-08-01

Sectioned/fractional topping placement (halves, quarters, specific sections) is rendered visually and unambiguously on the make-line screen or ticket. differentiator

kitchen-pizza-fractional-display

Portions carry through from POS entry to tickets, but Toast does not document a visual pie/section rendering on the make-line screen. https://doc.toasttab.com/doc/platformguide/adminUsingPortionsInTheToastPosApp.html · retrieved 2026-08-01

A bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order.

kitchen-recall-refire

Recall/unbump and item refire are standard Toast KDS actions; not verified against a specific doc page.

Edits made in the POS to an order already displayed in the kitchen visually flag the added, changed, or removed items on the live ticket. differentiator

kitchen-order-modification-alerts

Toast documents a Flash Changes setting that "defines whether the KDS device alerts employees to new and changed tickets by intermittently changing the color of the ticket headers. To acknowledge the ticket and stop the flashing, you select the ticket." The KDS configuration quick reference adds an audible option to "Play a sound when a new ticket appears, a ticket is ready for fulfillment at an expediter KDS device, an item is changed, and an item is marked as void." Item-level marking is documented for re-fired checks: "refunded items appear crossed out and are labeled as REFUNDED... The remaining quantity is labeled as CHANGED." Shortfall: on a live displayed ticket the alert is a header-colour flash for the whole ticket, and the per-item crossed-out/REFUNDED/CHANGED labelling is documented only for refunds on re-fired checks - Toast does not document per-item visual flagging of items added or removed on an already-displayed ticket. https://doc.toasttab.com/doc/platformguide/adminKitchenDiningRoomReference.html · retrieved 2026-08-08

Bumping an order ready triggers a guest-facing notification — SMS/text, app push, or an order-status display board — without a separate product purchase. differentiator

kitchen-guest-ready-notification

Order status SMS exists for delivery and online orders. A general bump-driven ready notification or status board included at no extra cost was not confirmed. https://support.toasttab.com/en/article/Toast-Delivery-Services-Order-Status-SMS-Texts · retrieved 2026-08-01

Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.

kitchen-waste-logging

Waste is a first-class, reason-coded POS workflow that depletes inventory, but it is not at the kitchen/KDS screen. 'Get Started With Food Waste Reduction' (Last updated: Jun 23, 2026, 11:41 AM) documents configurable reasons -- 'In Toast Web, navigate to Menus > Food waste management > Food waste tracker. Select + Add Discount Reason. Add a Name and Description ... Ensure both the Active and Waste columns are toggled to the on position', with suggested reasons 'Expired Drop Misfire Burnt Donation Compost' -- and depletion: 'When you add a menu item to waste tracking, the item will be deducted automatically from your restaurant's inventory count. However, in order for that to occur, your restaurant must not be in test mode.' A Food Waste Breakdown report (Reports > Menus > Food waste breakdown) 'aggregates every action your staff has taken on the POS Waste Tracker', viewable 'by day, waste reason' or top items. SHORTFALL: the entry surface is a POS mode -- 'On your POS main menu, select Waste Tracking in the Mode section' -- restricted by permission '1.19 Record Excess Food Menu Items' and 'compatible with Toast Go's and scanners'; entries accumulate on one check per day and 'You cannot change the items on a previous day's food waste check.' The Toast KDS platform guide (doc.toasttab.com/doc/platformguide/platformKDSOverview.html, 32,961 chars of stripped text, which is the full KDS nav tree) has ZERO occurrences of 'waste', 'spoil', 'remake' or 'discount' -- the KDS action surface is bump/recall/unfulfill/filter/all-day, with no waste capture. Second shortfall: the mechanism is a discount (reasons are created as discount reasons under the 6.1 Discounts Setup permission), and the article's depletion sentence is about the menu item's 'inventory count', i.e. item-level quantity, not ingredient-level stock. Ingredient-level depletion is documented on a DIFFERENT surface, Toast IQ Inventory -- 'Waste tracking reduces your inventory. Waste logged against an ingredient or a prep item is deducted from stock and appears in the item's recent activity, labeled by where it was logged, so it sits alongside sales depletion' (support.toasttab.com/en/article/Toast-IQ-Inventory-FAQ) -- so the two should not be read as one flow. https://support.toasttab.com/en/article/Get-Started-with-Food-Waste-Reduction · retrieved 2026-09-15 adversarially verified

Reports actual ticket and per-station times (average and percentile) sliced by daypart, station, and order channel, exportable to CSV or an API.

kitchen-speed-of-service-reporting

Kitchen productivity reporting in KDS plus Speed of Service reporting in Toast Drive-Thru. Percentile slicing and CSV/API export not explicitly documented. https://support.toasttab.com/en/article/Get-Started-With-the-Kitchen-Display-System · retrieved 2026-08-01

Generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list.

kitchen-prep-forecasting

Forecast-driven prep reaches Toast only through a partner: "The PreciTaste team analyzes sales data and POS items daily to create a location-based prep forecast", with a Prep Assistant that "automates daily ingredient preparation using AI-driven forecasts." Named shortfall: this is not first-party - "This integration requires access to Toast Partner Integrations", it is requested by adding a tile in Toast Partner Connect, and the PreciTaste customer success team contacts the restaurant separately, so it is a separately contracted vendor. Toast's own prep output, Production Items feeding Prep Tools (Prep Sheets, Pack Sheets, BEOs), derives quantities from actual booked Catering & Events orders - "if one menu item requires 1 bread roll per guest and the guest orders for 25 people, the prep sheet will show 25 bread rolls" - not from historical sales or forecast demand. https://support.toasttab.com/en/article/Get-Started-With-the-PreciTaste-Integration · retrieved 2026-08-08

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

Toast supports delivery with your own drivers, with Delivery Mode as the native in-POS module for managing and dispatching them. https://support.toasttab.com/en/article/How-do-I-set-up-my-take-out-and-delivery-options-1492745822028 · retrieved 2026-08-01

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

delivery-dispatch-board

Checked the cited article. Delivery Mode does have Unassigned / En Route / Delivered phases, dispatches to clocked-in employees with a Driver job type, and explicitly supports dispatching multiple orders to one driver (weak batching). Per-order elapsed timers and route sequencing are still absent, so partial is right - but the note's claim that multi-order dispatch is undocumented is wrong. https://support.toasttab.com/en/article/Delivery-Mode-1493048871021 · retrieved 2026-08-01 adversarially verified

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

Delivery 2.0 Live Map provides a map view of delivery activity. System-generated multi-stop route sequencing not documented. https://support.toasttab.com/en/article/Delivery-2-0-Live-Map · retrieved 2026-08-01

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

delivery-driver-tracking

Guests can see driver location on a map for Toast Delivery Services orders. Live GPS from an in-house driver app back to dispatch not documented. https://support.toasttab.com/en/article/Toast-Delivery-Services-Order-Status-SMS-Texts · retrieved 2026-08-01

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

Researcher missed this. Toast documents an actual Polygon tool on the delivery-area map: "Select the Polygon tool (square icon) at the top right of the map. The tool allows you to draw and designate your delivery area." Arbitrary polygon geometry is documented; drive-time isochrones are not. https://doc.toasttab.com/doc/platformguide/adminConfigureDeliveryArea.html · retrieved 2026-08-01 adversarially verified

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

Now sourced rather than inferred: Toast documents multiple mileage-based service charges and delivery zones, a Waive Fee Threshold, a Delivery Distance Threshold, and a Delivery Minimum set to Reject. Quote times are configured on the Delivery & Takeout page. https://support.toasttab.com/en/article/Configuring-Delivery-Fees-1493053499602 · retrieved 2026-08-01 adversarially verified

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

Confirmed: Toast compares the configured delivery area to the customer's address on on-site and online delivery orders to automatically allow or deny the order. The delivery-area doc page itself does not describe the geocoding mechanism, so 'geocoding' specifically remains unverified. https://support.toasttab.com/en/article/Configuring-Delivery-Fees-1493053499602 · retrieved 2026-08-01 adversarially verified

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

Toast Web > Takeout & delivery > Availability > Takeout/delivery has a Driver Reimbursement section, defaulting to "No, do not reimburse drivers" and switchable to "Yes, reimburse drivers for each delivery order completed" with a reimbursement amount, described as reimbursing drivers "for the wear and tear of their personal vehicle". Shortfalls: the reimbursement is a flat per-completed-delivery amount - no mileage or distance per run is captured anywhere in the delivery section of the platform guide; driver-retained tips are not addressed on this page; and no payroll export separating a non-taxable reimbursement line from wage lines is documented. Toast also restricts the feature: "Driver reimbursement is only available for first-party delivery." https://doc.toasttab.com/doc/platformguide/adminReimburseDriversAndCashBanks.html · retrieved 2026-08-08

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

"You can also choose to configure a starting cash balance for a delivery driver. At the end of the driver's shift, their cash bank is returned to the restaurant and counted as cash in hand." It is enabled in Toast Web > Takeout & delivery > Availability > Takeout/delivery under Driver Cash Management by selecting "Yes, assign driver bank for reporting" and entering a starting amount, and orders are tied to drivers - "An Order Ready order must be assigned to a driver before it can be marked as complete" (platformManagingDeliveryOrders.html). Shortfall: Toast documents issuing and returning the bank but no settle-up flow reconciling cash collected against orders assigned and tips owed, and no per-driver over/short figure; the platform guide's cash pages produce drawer-level and deposit-level variance only. https://doc.toasttab.com/doc/platformguide/adminReimburseDriversAndCashBanks.html · retrieved 2026-08-08

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

Toast Delivery Services dispatches on-demand couriers powered by Uber Direct or DoorDash Drive from Toast's own online ordering channels, keeping the guest data. https://support.toasttab.com/en/article/Toast-Delivery-Services · retrieved 2026-08-01

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

Vendor-affirmed absence, not merely unfound. Toast's delivery overview enumerates the model completely - "Toast offers two options for delivery: First-party delivery: You use your own drivers to make deliveries. Toast Delivery Services (TDS): You can choose between DoorDash or Uber Direct to deliver orders from Toast Online Ordering and the Local by Toast app" - and then states in an Important callout: "First-party delivery and TDS cannot be used at the same time or interchangeably." With the two modes mutually exclusive there is no per-order overflow from an in-house driver to a DaaS courier, and no wait-threshold or out-of-zone dispatch rule appears in the delivery section or in the TDS setup article. https://doc.toasttab.com/doc/platformguide/adminDeliveryOverview.html · retrieved 2026-08-08

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

Toast-owned direct integrations with DoorDash, Grubhub, Uber Eats and Caviar; no middleware required. https://pos.toasttab.com/third-party-delivery-integrations · retrieved 2026-08-01

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

Orders flow from the marketplaces directly into the Toast POS, eliminating tablets and manual double-entry. https://pos.toasttab.com/third-party-delivery-integrations · retrieved 2026-08-01

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

One Toast master menu publishes to marketplaces with channel-specific prices. Real caveats: time-specific pricing and nested subgroups do not sync. https://support.toasttab.com/en/article/Adjusting-Sync-ing-Hours-on-DoorDash-UberEats-GrubHub-Menus · retrieved 2026-08-01

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

Toast pushes availability but states the ordering partner controls whether 86'd items are hidden — so item-level 86 is not uniformly guaranteed across channels. https://support.toasttab.com/en/article/Uber-Eats-DoorDash-and-Grubhub-Integration-Configuration-Limitations · retrieved 2026-08-01

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

From inside Toast you can "turn on, off, or snooze (pause) third-party online ordering channels" individually or in bulk, and the snooze is timed with automatic resumption: it pauses ordering for 20 or 40 minutes, or until the start of online ordering hours the next day. Shortfalls: the documented effect is on whether Toast accepts orders from that channel - Toast does not state that the store is deactivated or shown as closed on the marketplace's own storefront; the timers are fixed presets rather than an arbitrary duration; and marketplace account management stays outside Toast. https://doc.toasttab.com/doc/platformguide/platformManagingThirdPartyOnlineOrderingChannels.html · retrieved 2026-08-08

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

Positive scope statement, not absence of mention. Toast's Reconciliation report "gives you a single list of every payout Toast has sent to your bank account", and Payout Details breaks one payout into "card payments, refunds, fees, withholdings (Toast Capital and Easy Pay loan repayments, Toast Delivery Services fees, instant deposit fees, and others)" - no marketplace commission, marketing-fee or 3P adjustment line anywhere in that breakdown, and the report is itself "in limited release with select customers". Marketplace money never enters that surface: "Sales from third-party delivery integrations (DoorDash, Uber Eats, Grubhub) are paid out by those providers directly to the restaurant on the provider's own schedule and do not appear in your Toast credit card deposit", and Toast tells operators these platforms "issue payouts directly to you, not through Toast", sending them to each marketplace's own knowledge base for payout questions. What Toast provides is sales-side tracking only - the DoorDash integration "consolidate[s] DoorDash accounting and reporting in Toast, with a unique payment type and dining option for tracking". Toast Delivery Services, Toast's own dispatch product, does get a TDS billing breakdown, but that is Toast's own fee withheld from a Toast payout, not a marketplace payout being reconciled. https://support.toasttab.com/en/article/Reconciliation-Report-and-Payout-Details-Overview · retrieved 2026-08-08 adversarially verified

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

Toast publishes troubleshooting for missing third-party orders and setup checklists, but a live per-channel integration health dashboard with failure alerts was not found. https://support.toasttab.com/en/article/My-restaurant-isn-t-receiving-third-party-orders · retrieved 2026-08-01

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

Toast Delivery Services provides guest order status SMS and a confirmation page with a live driver map. https://support.toasttab.com/en/article/Toast-Delivery-Services-Order-Status-SMS-Texts · retrieved 2026-08-01

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

Toast documents order wait time calculation and throttling that adds to the quote. Automatic adjustment from driver availability and zone drive time not documented. https://doc.toasttab.com/doc/devguide/calculatingOrderWaitTime.html · retrieved 2026-08-01

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

delivery-offline-behavior

Toast has a dedicated offline-delivery page: "You can place takeout and delivery orders when the device is in offline mode", with the stated limitation that "you cannot look up guest information to link the order to an existing guest account", which can create duplicate guest accounts on reconnection. Shortfall: of the three behaviours the claim asks to see documented, only order entry is covered. Neither adminOfflineDelivery.html nor the other fourteen offline pages in the platform guide (adminOfflineModeOverview, platformOfflineMode, adminOfflineCCPayments, platformOfflinePaymentsOverview, platformOfflineKDSDevices, adminCompletingShiftReviewOffline, adminPendingTipsWhenOffline and the rest) states whether driver assignment/dispatch or driver cash-bank settlement continues during an internet outage. https://doc.toasttab.com/doc/platformguide/adminOfflineDelivery.html · retrieved 2026-08-08

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

Toast Online Ordering is first-party and commission-free, writing orders straight into the POS, with its own operator dashboard. https://doc.toasttab.com/doc/platformguide/adminOnlineOrderingDashboard.html · retrieved 2026-08-01

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

digital-menu-single-source

Online ordering renders the same Toast POS menu record; no separate digital menu build. https://doc.toasttab.com/doc/platformguide/adminFiringToastOnlineOrders.html · retrieved 2026-08-01

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

digital-native-app

Toast's Branded Mobile App: "Launch your own mobile app (on iOS or Android) - build your brand with your logo and choice of fonts, colors, and imagery." It is published under the restaurant's own store identity: setup requires the restaurant to create its own developer accounts with each store ($99 annually with Apple, $25 one-time with Google), and "It can take up to two weeks for your newly created app to be completed" plus app-store review. This is distinct from the shared multi-restaurant Local by Toast (Toast Takeout) marketplace app, which Toast also operates. https://support.toasttab.com/en/article/Get-Started-With-the-Branded-Mobile-App · retrieved 2026-08-08

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

Guest accounts with saved addresses, tokenized cards and reorder in Toast Online Ordering; not verified against a doc page.

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

Checkout upsells exist; configurable-vs-algorithmic behavior and attach-rate reporting not documented.

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

Scheduled/pre-orders plus per-slot order caps and throttling that close or delay slots when the kitchen saturates. https://support.toasttab.com/en/article/Managing-Online-Order-Volume-Throttling-Orders-1492627940253 · retrieved 2026-08-01

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

Pickup, curbside, dine-in/QR and delivery in one flow with mode-specific fees and prep timing; curbside arrival check-in not separately verified.

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

Toast Order & Pay supports QR scan-to-order and scan-to-pay with splitting and tipping.

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

First-party kiosk on the same menu and modifier engine with unattended EMV. No published accessibility conformance documentation. https://pos.toasttab.com/hardware · retrieved 2026-08-01

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

Toast documents group ordering on Toast Mobile Order & Pay: it lets "multiple guests at one table scan a QR code and begin ordering items on a single check", displaying guest names "so servers know who each item is for", and it works with the Tabs option so guests can "order multiple rounds and pay at the end". Shortfalls: no per-person or total spend cap is documented, and the join mechanism is an in-venue table QR code for on-premise Mobile Order & Pay rather than a remotely shareable group-order link for an off-premise order. https://support.toasttab.com/en/article/Group-Ordering-on-Toast-Mobile-Order-PayTM-INTERNAL · retrieved 2026-08-08

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

Catering Online Ordering has its own hours, customized lead times, order minimums and capacity settings, feeding Catering & Events invoicing. https://support.toasttab.com/en/article/Getting-Started-with-Catering-Online-Ordering · retrieved 2026-08-01

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

Incept AI is a named certified partner taking guest orders over the phone and injecting them into Toast. https://support.toasttab.com/en/article/Get-Started-With-InceptAI-Integration · retrieved 2026-08-01

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

digital-drivethru-ai

Toast Drive-Thru ships with Incept AI voice ordering integrated to the POS menu; escalation-to-human handoff not documented. https://pos.toasttab.com/news/toast-drive-thru-launch-2026 · retrieved 2026-08-01

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

digital-sms-ordering

Toast SMS Marketing campaigns may carry an ordering link - the "Accepted SMS marketing URLs" are the Toast Online Ordering page and the restaurant's own website - so a text-a-link path into a Toast order exists, and orders placed via that link arrive in the POS as ordinary online orders. Shortfalls: messaging is one-way broadcast, and the only inbound keyword documented is texting JOIN to the restaurant's dedicated toll-free number to subscribe, not to order. Toast's other SMS product, Text to Pay, is explicitly payment-only - "The guest will receive a link via text message with their check" - and places no orders. No conversational or agentic text-ordering flow is documented. https://support.toasttab.com/en/article/Get-Started-With-SMS-Marketing · retrieved 2026-08-08

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

Order with Google is "automatically enabled in your Toast account when Online Ordering is turned on", provisioning the Toast direct ordering link as an ordering option on the restaurant's Google listing. Toast also documents the preferred placement the claim describes: "By adding a preferred business badge to your listing, you can elevate your Toast link's position in the Google UI and shift third-party orders to Toast to save on commission", with the badge requiring the operator to connect with Google. Recorded rather than scored as a shortfall: the badge is an operator action, not an automatic default - the claim treats preferred status as the ideal, not the requirement. https://support.toasttab.com/en/article/Using-Order-with-Google · retrieved 2026-08-08

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

CLAIM: Apple Business Connect 'Order Food' action to first-party ordering. VERDICT: stays unknown. NEW SURFACES (found via crt.sh listing of %.toasttab.com, 346 unique hostnames): (a) guesthelp.toasttab.com, the Toast Local guest Intercom help centre - sitemap 93 URLs, all 72 /en/ articles plus collection pages fetched (80 docs, census of that sitemap); (b) updates.toasttab.com, Toast product updates on LaunchNotes - sitemap 423 announcements, all 423 fetched at 200, publishedAt 2023-09-02 to 2026-09-14 (census of that sitemap); (c) trustcenter.toasttab.com, the Toast Trust Center (anonymous site-data JSON the page itself loads: dvqneza7fx.us-west-2.awsapprunner.com/api/v1/tc/trustcenter.toasttab.com/site-data/), which enumerates 8 security_certificates + 1 security_report. Controls: "apple business|apple maps" 0 in guesthelp (80) and 0 in updates (423); apple 0 in updates. KNOWN-POSITIVE CONTROL FAILS: "Order with Google|google business|google maps" is also 0 in both, although support.toasttab.com/en/article/Using-Order-with-Google exists - so neither new corpus covers listing channels and neither can carry a no. Also: the support.toasttab.com sitemap (805 URLs on 2026-09-16) omits live 200 articles (e.g. Set-Up-the-STORM-Accessibility-Device-for-Toast-Kiosk), so the prior 828-URL sitemap bound was never a census; its search runs on Coveo behind robots-disallowed /api/ and was not used. Retrieved 2026-09-16. || 322nd: VERDICT: stays unknown. NEW SURFACE (322nd): every support.toasttab.com page (Next.js "support-public-app", incl. its 404 page, e.g. https://support.toasttab.com/en/article/Zz-Nonsense-Article-Qq, HTTP 404, 578,781 bytes, anonymous) server-renders a LaunchDarkly allFlagsState object ("$flagsState") into the RSC payload: 4,148 flag keys spanning all Toast product lines (oo- online ordering, ksk- kiosk, loy-/ca- loyalty and consumer app, stp- Toast Local, lgc- gift cards, whsl- wholesale, ord-oapi- orders API ...), each with its evaluated value for an anonymous visitor. A flag list is NOT a feature census (flags are created and retired, and a value is per-context), so it can inform a note but cannot carry a yes or no. Controls: "apple-business|business-connect|apple-maps" 0 of 4,148 keys; apple flags are only Apple Pay ("oo-v3-apple-pay", "oo-v4-apple-pay", "opt-apple-pay-shipping"), app smart banners ("ca-toast-local-web-apple-banner", "nv1-tables-lbt-apple-smart-banner"), "oo-branded-app-apple-license-email" and gift-card wallet. The Google counterpart IS flagged ("stp-google-business-profile":true, "stp-google-reviews"), so the flag set does see listing-channel work, and Apple Business Connect is absent from it - lean no, but a flag list is not a census of shipped integrations. Slug probes Apple-Business-Connect, Using-Apple-Business-Connect, Order-with-Apple-Maps, Apple-Maps-Ordering all 404 (same size as nonsense slug). Retrieved 2026-09-17. || 324th: NEW 2026-09-17 -- marketing corpus bounded and empty, which is a floor and not a verdict. The pos.toasttab.com sitemap index was expanded in full: https://pos.toasttab.com/sitemap.xml redirects to /sitemaps-1-sitemap.xml, which lists 22 section sitemaps plus custom.xml; fetching all of them yields 4,146 unique URLs. Tokenised, case-insensitive search over that URL set for `apple`, `business-connect`, `wallet` returns exactly one hit, and it is a press release about Applebee's ('applebees-selects-toast-technology-as-new-point-of-sale'). So Toast does not market an Apple Business Connect 'Order Food' action anywhere on its own marketing host. WHY THIS IS NOT A `no`: a URL-slug census is not a body census, the Apple Maps place-card action is configured by the merchant in Apple Business Connect rather than documented by a POS vendor, and Toast's two documentation hosts are not bounded (support.toasttab.com's 787-URL sitemap is known to omit live articles; doc.toasttab.com/sitemap.xml returns S3 AccessDenied). Stays unknown. Retrieved 2026-09-17. || 329th: MERGE HOLD (proposed no/B, held unknown): An Apple Business Connect 'Order Food' action is a merchant-configured URL into Toast Online Ordering, so an order placed through it arrives as ordinary online ordering: a closed orderSource enum lacking APPLE does not bound the placement. The surface where Toast would document it (support.toasttab.com) is uncensusable (Coveo client-side search, sitemap omits live articles); the developer-doc census is the wrong publisher surface for an operator how-to. PROPOSAL AS WRITTEN: NEW 2026-09-18 -- the surface that was called unbounded is now censused, and it carries a CLOSED ORDER-SOURCE ENUMERATION in which the Google analogue is present and Apple is absent. VERDICT: unknown -> no / B. THE SURFACE: doc.toasttab.com/sitemap.xml 403s (S3 AccessDenied) and so does /robots.txt and /llms.txt, which is why three prior passes recorded the developer host as unbounded -- but the API reference is a separate Gatsby app with its OWN sitemap at https://doc.toasttab.com/openapi/sitemap.xml (3,593 bytes, 518 <loc> entries), and the five DocBook guide books (devguide, platformguide, cookbook, relnotes, main) crawl to a same-book href FIXPOINT. Fetched: 495/495 unique API-reference pages (2,054,648 chars stripped, 0 non-200) and 710 guide topics (5,107,559 chars stripped; rounds to fixpoint: devguide 4 rounds/216 topics, platformguide 4/470, cookbook 4/19, relnotes 4/4, main 2/1; 0 misses, 0 non-200; nonsense control https://doc.toasttab.com/doc/platformguide/zzNonsenseQq.html = 403 AccessDenied 111 bytes, so a 200 is a real page). EVIDENCE: the Analytics API's MetricsReportingData.orderSource field publishes a closed list -- 'Valid values: API BRANDED_ONLINE_ORDERING CALLER_ID CATERING CATERING_ONLINE_ORDERING GOOGLE GRUBHUB (deprecated) IN_STORE INVOICE KIOSK ONLINE ORDER_AND_PAY_AT_TABLE TOAST_LOCAL TOAST_PICKUP_APP TOAST_TABLES' (15 values) -- and the Kitchen API repeats it in prose at https://doc.toasttab.com/openapi/kitchen/tag/Data-definitions/schema/ItemFulfillment/ : 'orderSource string The way the order was placed. Valid values: In Store Online Order-and-Pay-at-Table API Kiosk Caller Id Google Invoice Toast Pickup App Toast Local Branded Online Ordering Catering Catering Online Ordering Toast Tables eCommerce Online ordering Branded Mobile App Grubhub (deprecated)' (18 values). Google's listing channel gets its own first-party order source in both; Apple gets none. BOUND/CONTROLS over the 1,205-document census, tokenised and case-insensitive: 'business connect' 0, 'apple maps' 0, 'google business' 0; 'apple' 11 in the guides and 7 in the API reference and EVERY hit is poison -- Apple Pay as a payment method ('toggle on or off the following payment methods: Apple Pay, Google Pay, and Keyed-in cards'), the APPLE_PAY_CNP payment-type enum, and a discount example named 'Buy one, get one apple!'. KNOWN-POSITIVE CONTROL PASSES (this is what the 316th/322nd passes could not achieve): 'order with google' returns 2 hits in the same corpus, at https://doc.toasttab.com/doc/platformguide/adminQuoteTimeStrategyOverview.html -- 'Order source (in-store, Toast kiosk, Toast Online Ordering, Local by Toast app, Order with Google, or third-party online ordering channels)' and 'The SmartQuote quote time strategy only applies to orders placed via the Toast Online Ordering website, Local by Toast app, and Order with Google' -- so this corpus DOES document listing-channel ordering integrations, and it documents Google's and not Apple's. RESIDUAL RISK, stated so the owner can hold the row: an Apple Business Connect 'Order Food' action is a merchant-configured URL in Apple's own portal, so a restaurant could point it at its Toast online-ordering page unaided and those orders would simply land as ONLINE; what is positively absent is any Toast-side support, documentation or order source for the channel, which is what the prior three passes' marketing-sitemap (4,146 URLs, zero apple), guesthelp (80 docs), updates (423 announcements) and flag-set evidence ('stp-google-business-profile':true present, no apple-business-connect key among 4,148) already pointed at. Retrieved 2026-09-18. adversarially verified

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

Guests are prompted to join Toast Loyalty during online ordering and accrue/redeem on the same guest identity as in-store. https://support.toasttab.com/en/article/Getting-Started-Toast-Loyalty · retrieved 2026-08-01

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

Toast Subscription Plans are a native guest-facing recurring-billing product - mug clubs, wine clubs, seasonal access passes - where the restaurant sets a plan price and billing frequency and Toast charges subscribers automatically, either on their signup anniversary or on a synchronized date shared by all members (a quarterly plan billing 1 Jan / 1 Apr / 1 Jul / 1 Oct). Named shortfall: entitlement delivery is manual - "Benefits are redeemed manually" through a 100% discount applied at checkout - and the platform does not natively support automatic discounts, stored value or a plan-linked delivery-fee waiver; benefits needing credits or deferred payment must be paired with house accounts. https://support.toasttab.com/en/article/Get-Started-With-Subscription-Plans · retrieved 2026-08-08

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

Promos and loyalty rewards are defined centrally and honored across POS and digital; explicit per-channel eligibility controls not verified.

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

Toast publishes a Merchant Data Processing Addendum and documents loyalty data import. Bulk self-serve export of guest PII and consent status without fee or approval is not documented, and API export requires an RMS Essentials+ subscription per location. https://pos.toasttab.com/privacy/merchantdpa · retrieved 2026-08-01

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

Checkout is Toast-hosted and Toast is a PCI Level 1 Service Provider, so card data never touches the restaurant's page. 3DS support and Req 6.4.3/11.6.1 script-integrity posture not published. https://support.toasttab.com/en/article/What-is-PCI-Compliance · retrieved 2026-08-01

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

Surcharging is state-gated with card-brand-compliant signage requirements and BIN-based debit exclusion. Whether the identical configuration applies to online and kiosk channels is not stated explicitly. https://support.toasttab.com/en/article/Credit-Card-Surcharging-FAQ · retrieved 2026-08-01

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

No source, and the researcher concedes dedup/merge behavior is undocumented. Cross-surface identity unification is a differentiator claim that needs product docs. adversarially verified

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

guest-loyalty-thirdparty-identity-attach

Get Started With Toast Loyalty: "Guests cannot earn or redeem Toast Loyalty points on orders placed through online ordering integrations such as DoorDash, Grubhub, or Uber Eats." A separate article gives the same answer for ChowNow. Guestbook's "Which guests get added to Guestbook" list enumerates every profile-creating event (Toast Online Ordering, Local by Toast, mobile payments, Mobile Order & Pay email receipt, Branded Mobile App, emailed or texted in-store receipt, Toast Go feedback, Toast Tables booking) and no third-party marketplace is among them; the Guestbook Order Source filter likewise enumerates In-store, Toast Online Ordering, Toast Branded Online Ordering, Toast Local (web), Toast Local (app), Toast Mobile Order & Pay, Toast Self-Ordering Kiosk, phone and invoice, with no DoorDash, Uber Eats or Grubhub option. https://support.toasttab.com/en/article/Getting-Started-Toast-Loyalty · retrieved 2026-08-08

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

Operator chooses points per dollar spent or per visit, sets value per point, minimum spend and reward type (free item or cash back). https://support.toasttab.com/en/article/Getting-Started-Toast-Loyalty · retrieved 2026-08-01

Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator

guest-loyalty-tiers

Configure and Redeem Tiered Rewards: "With tiered item rewards, you can expand your restaurant's reward offerings through Toast Loyalty. You can set up three free item rewards, each tied to different points or visit balance tiers." These are reward thresholds, not guest status tiers - there is no promotion, no demotion and no rolling window. Get Started With Toast Loyalty enumerates the full configuration surface (signup method, visit-based or amount-based earning, discount rewards with a value-per-point, free-item rewards with points-to-unlock) and contains no status-tier concept. https://support.toasttab.com/en/article/Configure-and-Redeem-Tiered-Rewards-in-Toast-Loyalty · retrieved 2026-08-08

Documents explicitly what loyalty lookup, accrual, and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). differentiator

guest-loyalty-offline-behavior

Documented clearly: loyalty rewards cannot be redeemed as a payment method offline, alongside gift cards, customer credits, comp cards and house accounts. https://doc.toasttab.com/doc/platformguide/platformOfflinePaymentsOverview.html · retrieved 2026-08-01

Offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. differentiator

guest-loyalty-offer-stacking-rules

The discount Advanced Properties include an "Allow with other discounts" setting, which is the explicit exclusive-vs-combinable control. Shortfall: Toast documents no order-of-application or precedence configuration, and the setting "is only available when the discount type is fixed check, open check, or BOGO. Item discounts cannot be combined." Promo codes are further limited - "Only one promo code or discount can be applied to a single check." https://support.toasttab.com/en/article/Basic-Discount-Configuration · retrieved 2026-08-08

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

Automated campaigns target behavioral audiences such as lapsed guests, but a general rules-builder over recency/frequency/spend/items is not documented. https://support.toasttab.com/en/article/Building-an-Automated-Email-Campaign · retrieved 2026-08-01

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

Prebuilt lifecycle segments (new, repeat, lapsed) drive Toast's automated campaigns, but a full RFM/VIP/at-risk model surfaced as analytics is not documented. https://support.toasttab.com/en/article/Building-an-Automated-Email-Campaign · retrieved 2026-08-01

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

'Set it and forget it' ongoing campaigns including welcome, repeat-visit and lapsed win-back, plus automated loyalty notifications. https://support.toasttab.com/en/article/Building-an-Automated-Email-Campaign · retrieved 2026-08-01

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

Both channels are native: Toast Email Marketing and Toast SMS Marketing with one-time and automated campaigns. https://support.toasttab.com/en/article/Get-Started-With-SMS-Marketing · retrieved 2026-08-01

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

Consent is captured at online-ordering checkout and Toast Loyalty signup. Per-channel consent timestamp/source records and non-STOP revocation handling not documented. https://support.toasttab.com/en/article/Get-Started-With-SMS-Marketing · retrieved 2026-08-01

Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.

guest-loyalty-10dlc-registration

Toast documents operator SMS registration: the restaurant completes business information under Marketing > SMS marketing and "your restaurant or business group will receive a unique, verified toll-free number for SMS marketing"; as of February 2026 the flow "includes new required fields to comply with updated toll-free number (TFN) carrier registration requirements", and "it can take up to 14 business days to receive your dedicated toll-free phone number." Shortfall as worded: the documented path is toll-free number verification, not A2P 10DLC brand and campaign registration, which appears in neither Get Started With SMS Marketing nor the SMS Marketing FAQ; a live website with no coming-soon banner is a prerequisite, and rejected registrations must go back through Customer Care. https://support.toasttab.com/en/article/Get-Started-With-SMS-Marketing · retrieved 2026-08-08

Reports redemption and incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. differentiator

guest-loyalty-campaign-attribution

Toast markets campaign-driven revenue reporting; tying redeemed offers to actual check totals was not verified in documentation.

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

Guestbook offers self-serve export: "Select Download list at the top of the Guestbook table", "Toast emails the logged-in user a link to a unique download URL", and the file is a CSV including contact information (primary email address or phone number) plus a guestGuid key. No fee and no support ticket. Shortfalls: the export is the Guestbook table (contact info, order date, number of orders, average spend per check, order source), not per-transaction history - full order history is viewable only in the per-guest profile UI; "If your restaurant management group has more than 250,000 guests, the export is limited to guests who have ordered within the past six months"; the download link expires after 72 hours; and a listed known limitation is that you cannot send Guestbook data automatically to an SFTP site or external destination. https://support.toasttab.com/en/article/Access-Your-Guest-Data-with-the-Guest-Report · retrieved 2026-08-08

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

Toast captures post-transaction star-rated feedback on Toast Go handhelds and on digital receipts, and the Guest Feedback Inbox lets managers reply privately where the guest left an email, set a status, add notes, or use an AI-drafted response; Toast frames the purpose as "Address negative experiences before disgruntled guests air their frustrations on Yelp." Shortfall: there is no score-based routing - Toast documents no mechanism that sends high scorers toward Google, Yelp or TripAdvisor, and no threshold that decides which of the two paths a response takes. Ratings are reported by theme (Atmosphere, Service, Food Quality, Wait Time). https://support.toasttab.com/en/article/Guest-Feedback · retrieved 2026-08-08

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

CLAIM: native guest referral with per-guest codes, first-order attribution, two-sided rewards. VERDICT: stays unknown. NEW SURFACES (found via crt.sh listing of %.toasttab.com, 346 unique hostnames): (a) guesthelp.toasttab.com, the Toast Local guest Intercom help centre - sitemap 93 URLs, all 72 /en/ articles plus collection pages fetched (80 docs, census of that sitemap); (b) updates.toasttab.com, Toast product updates on LaunchNotes - sitemap 423 announcements, all 423 fetched at 200, publishedAt 2023-09-02 to 2026-09-14 (census of that sitemap); (c) trustcenter.toasttab.com, the Toast Trust Center (anonymous site-data JSON the page itself loads: dvqneza7fx.us-west-2.awsapprunner.com/api/v1/tc/trustcenter.toasttab.com/site-data/), which enumerates 8 security_certificates + 1 security_report. Tokenised controls (word-boundary, case-insensitive): referral 0/80 guesthelp, 0/423 updates; "refer a friend|invite a friend|share your code" 0/0; refer* 1 guesthelp ("please refer to our guest terms") and 5 updates (all "reference"/"referred to as Focused View"/"reference the Salesloft Drift Breach Disclosure") - poison, none a referral mechanic. The 16 loyalty-titled announcements (tiers, kiosk redemption, GFD sign-up, third-party loyalty rewards) contain no referral. WHY NOT NO: neither corpus enumerates loyalty mechanics (updates covers POS release notes from 2023-09 only; guesthelp is a guest FAQ). Retrieved 2026-09-16. || 322nd: VERDICT: stays unknown. NEW SURFACE (322nd): every support.toasttab.com page (Next.js "support-public-app", incl. its 404 page, e.g. https://support.toasttab.com/en/article/Zz-Nonsense-Article-Qq, HTTP 404, 578,781 bytes, anonymous) server-renders a LaunchDarkly allFlagsState object ("$flagsState") into the RSC payload: 4,148 flag keys spanning all Toast product lines (oo- online ordering, ksk- kiosk, loy-/ca- loyalty and consumer app, stp- Toast Local, lgc- gift cards, whsl- wholesale, ord-oapi- orders API ...), each with its evaluated value for an anonymous visitor. A flag list is NOT a feature census (flags are created and retired, and a value is per-context), so it can inform a note but cannot carry a yes or no. Tokenised controls over the 4,148 keys: referr* 0, refer 0, invite* 3 (POISON: "lpx-invited-user-pos-auth", "po-use-bulk-invite-controls", "whsl-buyer-portal-invite-superadmin" - staff/buyer user invites), ambassador 0; 53 loyalty flags (accrual notification, signup CTA, kiosk loyalty, redemption, 3p loyalty, linked cards) and none names referral. Not a no: a flag list is not a feature census. Slug probes Toast-Loyalty-Referral-Program, Loyalty-Referrals, Refer-a-Friend-Loyalty, Setting-Up-Loyalty-Referrals all 404 (guesses). Retrieved 2026-09-17. || 324th: NEW 2026-09-17 -- a HOMONYM is now ruled out by name, so nobody re-mines it. Toast's support sitemap (https://support.toasttab.com/sitemap.xml, 787 URLs) contains exactly one referral article, 'Toast Referral Program Overview' (last updated Sep 17 2026; fetched 200, 134,576 raw bytes, 2,942 chars stripped). It is a MERCHANT-acquisition programme, not a guest mechanic: 'How can I refer new businesses to Toast?... Advocates can earn up to $2,000 for submitting a successful referral to Toast... As of March 2026, the Toast Referral program has transitioned to Toast Advocates. Advocates can use this new portal to submit referrals, track their progress, and earn referral bonuses when the referred location goes live with Toast' (portal advocates.toasttab.com). The same thing appears twice more as chrome and must not be mistaken for a guest feature: the pos.toasttab.com nav item 'Toast Advocates - Grow the community and get rewarded for every referral' and the site-footer link 'Refer a Restaurant'. Nothing here gives a guest a per-guest code or link, attributes a referred guest's first order, or pays a two-sided reward. Separately, the pos.toasttab.com sitemap tree was expanded in full (22 section sitemaps, 4,146 unique URLs) and the only referral page in it is a BLOG post about employee referral programmes. That marketing corpus is a census of pos.toasttab.com but NOT of Toast's KB, and support.toasttab.com's sitemap is known to omit live articles, so no `no` may rest on either. Stays unknown. Retrieved 2026-09-17. || 329th: NEW 2026-09-18 -- the Toast Loyalty product page's BODY (not just its slug) and the guest app's own listing were finally read, plus a 1,205-document developer census; all negative, still not a bound. STAYS UNKNOWN. (a) BODY GREP OF THE MARKETING PRODUCT PAGES: https://pos.toasttab.com/products/loyalty (108,611 bytes, 11,281 chars stripped), /products/toast-marketing (12,106) and /products/gift-card (11,404), all fetched with the Sec-Fetch-* header set; chrome measured with a nonsense sibling (https://pos.toasttab.com/zzNonsenseQq329 = 404, 6,213 chars stripped, i.e. roughly 5 K chars of real body per page). Controls: `wallet` 0, `apple` 0, `invite` 0, `friend` 0, `share` 0, `pass` 0 on all three; `referr*` hits only the site-wide nav and footer chrome, 'Toast Advocates Grow the community and get rewarded for every referral', which the 324th already identified as the MERCHANT-acquisition programme. So Toast's own Loyalty product page markets no guest referral mechanic. (b) THE GUEST APP'S VENDOR-AUTHORED FEATURE LIST: Toast - Local Restaurants (App Store id 1362180579, v3.27.1, 2026-09-14; the Toast, Inc. publisher roster via itunes.apple.com/lookup?id=543556374 is 5 apps and this is the only guest-facing one) enumerates 18 feature bullets including 'Rewards & loyalty', 'Deals & offers' and 'Order history', and names no referral, invite or share-a-code mechanic; the Google Play listing for com.toasttab.consumer (195,537 bytes) scores `referral` 0 and `invite` 0 with loyalty/rewards present as a passing known-positive. Its full-resolution 'Rewards & Offers' screenshot (mzstatic /1000x0w.png, read as an image) shows only a Rewards/Offers tab pair, a birthday-reward banner and per-restaurant point cards -- no Invite-friends tile. (c) doc.toasttab.com census (495 API-reference pages + 710 guide topics to a link fixpoint, 7.2 M chars): `\breferral\b` 0 and `\breferrals\b` 0. POISON WORTH RECORDING: an unanchored `referr` control scores 31 hits on that corpus and every one is the substring inside PREFERRED ('the menus API is the preferred method', 'the menus webhook is the preferred method') or 'referred to as a waste order' / 'also often referred to as a PIN code'; tokenise or this cell reads as populated. WHY STILL NOT A `no`: none of these is an enumeration of Toast Loyalty's own program configuration -- the developer corpus documents only the THIRD-PARTY loyalty integration interface (apiLoyaltyIntegrationOverview, apiLoyaltyPosWorkflow, apiLoyaltyKioskWorkflow, and the /openapi/loyalty spec's 37 schemas: AccountInfo, Offer, Redemption, RedemptionLimit, ResponseSignup, ResponseTransfer, ItemRedemptionInfo, ExpirationData and the rest), which is the surface a partner implements rather than the settings screen of Toast's first-party programme, and the platform guide has no Toast Loyalty configuration reference at all; and support.toasttab.com is still uncensusable (sitemap omits live articles, /en/search is client-side Coveo with no SSR results, homepage RSC payload holds zero /en/article/ links). Retrieved 2026-09-18. adversarially verified

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

CLAIM: Apple/Google Wallet loyalty pass with push-updatable balance. VERDICT: stays unknown. NEW SURFACES (found via crt.sh listing of %.toasttab.com, 346 unique hostnames): (a) guesthelp.toasttab.com, the Toast Local guest Intercom help centre - sitemap 93 URLs, all 72 /en/ articles plus collection pages fetched (80 docs, census of that sitemap); (b) updates.toasttab.com, Toast product updates on LaunchNotes - sitemap 423 announcements, all 423 fetched at 200, publishedAt 2023-09-02 to 2026-09-14 (census of that sitemap); (c) trustcenter.toasttab.com, the Toast Trust Center (anonymous site-data JSON the page itself loads: dvqneza7fx.us-west-2.awsapprunner.com/api/v1/tc/trustcenter.toasttab.com/site-data/), which enumerates 8 security_certificates + 1 security_report. What the guest KB says about the loyalty card: "If a restaurant requests your loyalty account QR code, you can view it by selecting "Show digital loyalty card" which is beneath the "Ways to redeem" header" - inside the Toast Local app. The Loyalty and Rewards collection (25 articles) has no wallet-pass article; "Wallet" in this KB (12 docs) is the Toast Local app's own Wallet tab (Toast Cash, saved cards), and the only "Apple Wallet|Google Wallet" hit is the Apple Pay device-card-number article. Updates: wallet 0, pass 1 (irrelevant) across 423 announcements. WHY NOT NO: known-positive control fails - Toast ships Add to Apple Wallet for gift cards (support.toasttab.com/en/article/Apple-Wallet-for-Toast-Gift-Cards-Troubleshooting), yet neither guesthelp's gift-card collection nor the 423 updates mention it, so neither corpus is a census of wallet features. Retrieved 2026-09-16. || 322nd: VERDICT: stays unknown. NEW SURFACE (322nd): every support.toasttab.com page (Next.js "support-public-app", incl. its 404 page, e.g. https://support.toasttab.com/en/article/Zz-Nonsense-Article-Qq, HTTP 404, 578,781 bytes, anonymous) server-renders a LaunchDarkly allFlagsState object ("$flagsState") into the RSC payload: 4,148 flag keys spanning all Toast product lines (oo- online ordering, ksk- kiosk, loy-/ca- loyalty and consumer app, stp- Toast Local, lgc- gift cards, whsl- wholesale, ord-oapi- orders API ...), each with its evaluated value for an anonymous visitor. A flag list is NOT a feature census (flags are created and retired, and a value is per-context), so it can inform a note but cannot carry a yes or no. It holds "ca-loyalty-wallet-add":false ({"variation":1,"version":15}) beside "lgc-gift-cards-apple-wallet":true ({"variation":0,"version":25}) - i.e. an add-loyalty-to-wallet capability exists as a gated consumer-app flag, OFF for the anonymous context, while the gift-card Apple Wallet flag (the shipped, documented feature) is ON. That is consistent with a loyalty wallet pass being in development or limited rollout, not documented as shipped. Also probed support.toasttab.com slugs Toast-Loyalty-Apple-Wallet, Add-Loyalty-Card-to-Apple-Wallet, Loyalty-Digital-Wallet: all 404 at the same size as a nonsense slug (guesses, not a bound). Retrieved 2026-09-17. || 324th: NEW 2026-09-17 -- the nearest Toast surface is found and is the WRONG instrument. Toast does ship an Apple Wallet integration, but for GIFT CARDS, not for a loyalty pass: 'Troubleshoot Apple Wallet for Toast Gift Cards' (last updated Sep 16 2026; fetched 200, 132,307 raw bytes, 915 chars stripped) exists as a support article, and its whole body is an outage notice -- 'Question: Why are my Toast gift cards not working with Apple Pay? Answer: The Toast team is aware of an issue with this feature, and we are working on a resolution.' A stored-value gift card in Apple Wallet is not a loyalty pass with a push-updatable POINTS balance, and the claim's stated purpose (an alternative to a branded app download for the LOYALTY programme) is untouched; Toast separately sells a Branded mobile app. Bounding checked and insufficient: support.toasttab.com's sitemap (787 URLs) has exactly two Apple Wallet or Apple Pay articles besides that one ('Which Toast devices support Apple Pay, Google Pay and Samsung Pay', 'How can a customer disable the Apple Pay ad on the bottom of a receipt') and the sitemap is not a census of the KB; pos.toasttab.com's full sitemap tree (22 section sitemaps, 4,146 unique URLs) has zero `wallet` matches; doc.toasttab.com's sitemap.xml returns S3 AccessDenied so the developer corpus is unbounded. No `no` is publishable. Stays unknown. Retrieved 2026-09-17. || 329th: NEW 2026-09-18 -- two new vendor-authored surfaces and a full-resolution screenshot of the actual loyalty screen, all negative, and still not a publishable bound. STAYS UNKNOWN. (a) THE PUBLISHER APP CENSUS: https://itunes.apple.com/lookup?id=543556374&entity=software&country=us returns Toast, Inc.'s complete iOS roster, 5 apps -- Toast - Local Restaurants (id 1362180579, v3.27.1, 2026-09-14), MyToast (1509268882), Toast Now (6444586410), Toast Tables (1588284147), Events Manager by Toast (6746572646). The guest-facing one is Toast Local, and its store listing is a vendor-authored feature enumeration of 18 bullets across 'EVERYTHING YOU NEED TO EAT LOCAL' and 'KEY FEATURES'; loyalty is named twice ('Rewards & loyalty: Earn points and unlock perks at participating restaurants', 'Restaurant loyalty and rewards programs at participating locations') and neither a wallet pass nor an Add-to-Wallet action appears anywhere in it. The Google Play listing https://play.google.com/store/apps/details?id=com.toasttab.consumer (195,537 bytes) scores 'wallet' 0, 'add to wallet' 0, 'google wallet' 0 while the known-positive control passes on the same bytes (loyalty 7, rewards 24, pickup 12, reserve 5). (b) THE SCREENSHOT READ AT FULL RESOLUTION: the App Store screenshot URLs were rewritten from /320x480bb.jpg to /1000x0w.png and read as images. Screenshot 4 is captioned 'Order local. Get rewarded.' and shows the app's 'Rewards & Offers' screen -- a Rewards/Offers tab pair, a 'Happy Birthday! You've got rewards waiting' banner, and a stack of per-restaurant loyalty cards rendered INSIDE the app ('Toast n' crumbs 50 pts to next reward', 'Toasties 10 pts to next reward', 'A Toast tale 30 pts to next reward', '120 total points'), with the footnote 'Loyalty programs are offered by participating restaurants in the app. Participation and program terms vary.' There is no Add to Apple Wallet or Save to Google Wallet affordance on that screen; screenshot 3 shows the post-order 'Points earned! See details' card, again in-app. That matches the guest KB's 'Show digital loyalty card' QR code and is consistent with the LaunchDarkly pair recorded in the 322nd ('ca-loyalty-wallet-add':false beside 'lgc-gift-cards-apple-wallet':true). (c) The doc.toasttab.com census built this session (495 API-reference pages + 710 guide topics, 7.2 M chars stripped, fixpoint reached with 0 misses) scores `wallet` 0 of 1,205 documents. WHY STILL NOT A `no`: the known-positive control FAILS on both new corpora for this axis -- Toast's shipped, documented Apple Wallet gift-card feature (support.toasttab.com/en/article/Apple-Wallet-for-Toast-Gift-Cards-Troubleshooting) is absent from the developer docs and from both store listings, so neither corpus is a census of Toast's wallet features; a store listing is marketing prose and a screenshot is one screen, not a settings enumeration; and support.toasttab.com remains uncensusable (its sitemap omits live 200 articles, its search is client-side Coveo with no SSR results in /en/search HTML, and its homepage RSC payload contains zero /en/article/ links). Retrieved 2026-09-18. adversarially verified

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

Toast publishes guidance for managing privacy compliance obligations and a Merchant DPA. In-app locate/export/delete tooling with propagation to loyalty and marketing records is not explicitly documented. https://support.toasttab.com/en/article/Managing-Your-Privacy-Compliance-Obligations · retrieved 2026-08-01

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

Toast documents a velocity control and an employee-level misuse report: Loyalty Program Alerts "notify you if a rewards account has accrued points more than three times in 24 hours", enabled at Marketing > Loyalty > Settings with an email address and delivered "every Monday at 11:00 am ET"; the Loyalty Misuse Report (Reports > Cash and loss management > Loyalty Misuse) gives "a breakdown of total points accrued and redeemed on transactions per employee" and tags employee accounts with an EMP tag. Shortfalls: manager approval is explicitly unavailable - "At this time it is not possible to set up manager approval for loyalty redemption" - manual point adjustment is gated only by the 3.2 Transfer / Rewards Adjustment permission, and no audit log of adjustments is documented. https://support.toasttab.com/en/article/Taking-Action-Against-Suspicious-Rewards-Activity · retrieved 2026-08-08

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

Toast IQ was expanded in 2026 from smart features into an AI assistant. Marketing-level claim; specific shipped offer-content/audience/send-time recommendation not confirmed as generally available. https://pos.toasttab.com/news/toast-expands-toast-iq-smart-ai-assistant · retrieved 2026-08-01

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

Native stored-value gift cards tied to the guest record and redeemable across the brand's locations; explicitly unavailable offline.

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

Employees punch at the Toast terminal; time entries flow to Toast Payroll with no separate time clock hardware. https://support.toasttab.com/en/article/Time-Entry-Management-Overview · retrieved 2026-08-01

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

labor-photo-punch-verification

Customize Time Clock Options enumerates the entire Toast time clock configuration surface: Print clock slips, Enforce scheduling (manager approval for non-scheduled clock-in or clock-out), Show time?, and Time entry rounding scheme. No camera, photo or biometric option exists. The Sling by Toast time clock settings are likewise enumerated (early clock-in, clock-in without scheduled shift, auto clock-out, early clock-out, shift classification, automated breaks) with no photo capture. Clocking in is authenticated by POS access code only. Toast does document biometrics, but for multi-factor login to Toast Web, not for punch. https://support.toasttab.com/en/article/Setting-Up-Time-Clock-Options · retrieved 2026-08-08

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

Toast's platform guide documents the offline punch behavior directly: "During offline mode, employees can clock in on Toast POS devices", and the support article adds that "each employee should clock in and out on the same Toast device for the duration of the outage so their time entries stay together." Named shortfall: the other half of the punch fails - "During offline mode, employees cannot clock out of their shifts because shift reviews are not supported in offline mode" when Shift Review is set to Required - and Toast publishes a manual repair procedure "for an employee who could not clock out during offline mode." Reconciliation is therefore partly manual rather than automatic, and Toast documents no duplicate-entry handling for punches taken across more than one device. https://doc.toasttab.com/doc/platformguide/adminOfflineEmployees.html · retrieved 2026-08-08

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

Per-action permission sets by role and location (voids, comps, discounts, refunds, reports); granularity not enumerated in a retrieved doc.

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

Overrides attributed to the approving manager; immutability and post-hoc queryability not verified.

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

Sling by Toast / Toast Scheduling builds and publishes schedules in the same platform as timekeeping, surfaced to staff in the MyToast app. https://support.toasttab.com/en/article/The-MyToast-App-Shifts · retrieved 2026-08-01

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

Toast markets sales-history-driven labor planning; a documented recommended-hours-by-daypart engine was not located.

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

Labor % is documented as "labor cost divided by net sales or gross sales". SHORTFALL: the documentation says only that "the report updates automatically for pre-set date filters" and never states that the figure is available live during service, which is the discriminating half of this claim. Refresh frequency and in-service availability are undocumented. https://support.toasttab.com/en/article/Labor-Cost-Breakdown-Report-Overview · retrieved 2026-08-02 adversarially verified

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

Toast Payroll tracks and calculates overtime across locations, FEINs and job types. A clock-in-time warning or block before OT is incurred is not documented. https://support.toasttab.com/en/article/Toast-Payroll-Overtime · retrieved 2026-08-01

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

Break clock-in/out is tracked and Toast documents failure modes, but per-state meal/rest rule configuration, attestation prompts and missed-break premium flagging were not confirmed. https://support.toasttab.com/en/article/Time-Entry-Management-Overview · retrieved 2026-08-01

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

labor-minor-labor-rules

Toast enforces no age-conditional labour rule at either scheduling or clock-in. The clock-in gate is a closed configuration surface with two settings and an explicit statement that it cannot be conditioned on the employee: 'On this page, you can configure early and late clock-in and clock-out limits. The maximum grace period is 90 minutes', and the FAQ 'Can I apply schedule enforcement to only some employees?' answers 'Schedule enforcement cannot be applied to only some employees. It applies to every employee at your location, so anyone who clocks in outside their scheduled shift needs manager approval, regardless of their role or department', the only remedy being to 'disable schedule enforcement for everyone' (Sling by Toast: Set Up Schedule Enforcement, last updated Sep 11 2026). The partner-integration variant offers only Minutes grace periods with a manager passcode override. A whole-surface census over the help centre bounds the scheduling half: across the 790 en-language article slugs in support.toasttab.com/sitemap.xml, the tokens 'minor', 'age', 'child', 'school', 'teen', 'youth' and 'permit' are ALL ZERO; and across 120 retrieved labour and payroll article BODIES (1,261,451 chars, all 60 Toast Payroll slugs included, footer stripped), tokenised counts are minor 1, age 1, teen/youth/underage/juvenile/minors/permit/certificate 0. Toast Payroll DOES hold an employee date of birth, but solely for a filing obligation -- 'Toast Payroll also requires each new hire's date of birth to complete New Hire Reporting, even in states where date of birth isn't one of the federally mandated elements' -- and that DOB drives no hour cap, time window or school-day rule anywhere in the corpus. Break configuration is likewise age-agnostic (Building Breaks in Toast, 16,043 chars, zero age tokens), which is the adjacent capability scored separately at labor-break-compliance-by-state. https://support.toasttab.com/en/article/Schedule-Enforcement · retrieved 2026-09-15 adversarially verified

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

Toast Tips Manager automates calculation and distribution of pooled tips from POS data by configurable rules, feeding payroll directly. https://support.toasttab.com/en/article/Toast-Payroll-Tips-Manager-Setup · retrieved 2026-08-01

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

Per-shift, per-employee tip contribution and distribution records are retained and flow into payroll reporting. https://support.toasttab.com/en/article/Toast-Payroll-Tips-Manager-Setup · retrieved 2026-08-01

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

Toast Payroll addresses the One Big Beautiful Bill Act tip provisions and commits to the occupation code: "TTOC are not required for 2025 reporting and are not on the 2025 Form W-2. Reporting will being [sic] on the 2026 Form W-2. Toast Payroll will add TTOC to employee profiles in 2026." For 2025 it surfaces the tip figure at My Profile > Taxes & Documents > Year End Documents from January 19, 2026, covering "both tips employees reported and any tips an employer was required to report on an employee's behalf." Shortfalls: the article does not separate cash from charged tips (it describes a single discretionary-tips figure and places tips in Box 7), TTOC support is stated as a future 2026 addition rather than as shipped, and Toast documents neither W-2 Box 12 code TP nor Box 14b. This is Toast Payroll, a separately licensed product, not Toast POS. https://support.toasttab.com/en/article/Toast-Payroll-No-Tax-on-Tips-and-or-Overtime · retrieved 2026-08-08

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

Toast help centre documents Toast Payroll as the filing agent, not an export: the Tax Center is 'Toast Payroll's central hub for managing payroll taxes and employer tax filings', employers must list Toast Payroll as third-party administrator on every state tax account 'so Toast Payroll can file and communicate with the state agency on your behalf', and federal filings are authorized by IRS Form 8655. Employee direct deposit accounts are configured inside Toast Payroll (Plaid link or manual routing/account entry) and paid from the company bank account. https://support.toasttab.com/en/article/Toast-Payroll-Manage-Payroll-Taxes · retrieved 2026-08-06

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

Toast Web publishes a Payroll Export at Reports > Labor > Labor summary > Employee Summary, downloaded as "a .csv file" containing Regular worked, Overtime hours, Pay rates, Net sales, Tips and Gratuity - so timecards, wages and tips do leave the platform in a documented format, and operators are told they can "filter the report after it's downloaded" for their own payroll system. Automated Nightly Data Export additionally delivers a Time Entries file over SFTP nightly, retained seven days. Shortfall: no provider-specific format and no direct payroll integration is documented for any third party - the article names only Toast Payroll ("If you use Toast Payroll, this data is imported automatically"), and the only third-party providers Toast names (ADP Run, QuickBooks, Square Payroll, Gusto) appear in a migration article describing data flowing INTO Toast Payroll from a prior provider, not out of Toast to them. https://support.toasttab.com/en/article/How-do-I-export-the-Payroll-Labor-Summary-report · retrieved 2026-08-08

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

Shift visibility and self-service actions exist in the MyToast app and Sling; manager-approval workflow enforcing overtime and role eligibility not verified. https://support.toasttab.com/en/article/The-MyToast-App-Shifts · retrieved 2026-08-01

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

Per-server item sales are documented, and Toast references an Employee Productivity report covering sales, tips, guests served and turn times. SHORTFALL: void and comp rate BY EMPLOYEE — named explicitly in this claim — is not documented in the sales reporting overview retrieved this pass. https://support.toasttab.com/en/article/Sales-Reports-Overview · retrieved 2026-08-02 adversarially verified

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

xtraCHEF does real-time plate costing with variance updates, recalculating as invoice-derived ingredient costs move. Sub-recipe nesting depth not explicitly documented. https://support.toasttab.com/en/article/xtraCHEF-Recipe-Reporting · retrieved 2026-08-01

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

inventory-unit-conversion-yields

Purchase/recipe/count unit conversion is implicit in xtraCHEF plate costing; explicit yield/waste percentage on raw-to-usable conversion not documented.

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

Actual vs Theoretical analysis compares product actually used against what Toast POS sales imply, reporting variance for waste, portioning, theft and unrecorded sales. https://support.toasttab.com/en/article/xtraCHEF-Get-Started-With-Actual-vs-Theoretical-Analysis-Reports · retrieved 2026-08-01

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

Toast POS sales data fuels inventory depletion in xtraCHEF, but the cadence (near-real-time vs daily batch) and modifier-driven depletion are not specified. https://xtrachef.com/integration/toast/ · retrieved 2026-08-01

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

Item counts do auto-86 and do propagate: Toast "will automatically mark this item as 'out of stock' when the last unit is sold" for limited-stock items, and "Stock changes that you make are immediately applied to your Toast Online Ordering site, and there is no need to publish them." Shortfall on the trigger the claim names: the mechanism is per menu item, not component-ingredient driven - "Item counts only apply to an individual item. For instance, if you use lobster in a lobster roll and also in lobster mac and cheese, these counts will need to be set individually and will not update based on each other's item count." Propagation to connected DoorDash, Uber Eats or Grubhub menus is not addressed in this article. https://support.toasttab.com/en/article/Setting-the-Stock-Status-and-Count-for-Menu-Items · retrieved 2026-08-08

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

Physical inventory and inventory analytics with count history are documented; explicit ad-hoc spot counts and scheduled cycle counts as distinct modes were not confirmed. https://support.toasttab.com/en/article/xtraCHEF-Inventory-Analytics · retrieved 2026-08-01

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

inventory-mobile-count-offline

xtraCHEF by Toast ships a mobile inventory app on iOS (App Store) and Android (Google Play) for taking counts, with product selection, quantity entry and an Out of stock control that "automatically appl[ies] zero to your stock level." Shortfalls: the article documents neither barcode nor QR scanning, and says nothing about operating with no network connectivity or syncing on reconnect - no offline behavior is described in xtraCHEF-Mobile-Inventory, xtraCHEF-Inventory-Counts or xtraCHEF-Inventory-Getting-Started. Note this is xtraCHEF, a separately licensed Toast module, not the POS app. https://support.toasttab.com/en/article/xtraCHEF-Mobile-Inventory · retrieved 2026-08-08

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

xtraCHEF ships vendor management, ordering and product catalogs, but named EDI order-transmission integrations with Sysco / US Foods / PFG are not documented publicly. https://pos.toasttab.com/products/xtrachef · retrieved 2026-08-01

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

Toast help centre: 'xtraCHEF's artificial intelligence and machine learning capture your purchases from invoices', and 'line items extracted from your supplier invoices' are then usable 'as products in advanced food-cost reporting, recipe creation, and inventory management'. Documented intake routes are mobile-camera photo capture of an invoice, a per-account 'xcinvoice' email address, and desktop file upload; uploaded documents sit in Processing (typically 6 to 8 hours) before Completed, and illegible or incomplete uploads are Rejected. Extracted items are then mapped/assigned to products per the Map Invoice Items article. https://support.toasttab.com/en/article/xtraCHEF-101 · retrieved 2026-08-06

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

Per-item purchase price history and fluctuating-cost drilldown are documented; a configurable threshold alert on received price is not. https://pos.toasttab.com/products/xtrachef · retrieved 2026-08-01

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

xtraCHEF supports per-item par levels that feed ordering: on the Count List you "input a par level amount (par level UOM's are based on the item's purchase unit)" describing "how much of your inventory item to have on hand at all times", and during a count "If you created par levels when creating your Count List, these amounts will automatically populate", with the shortfall against on-hand surfaced in a "Need to Order" column the user can adjust. Shortfall: every documented par is a static operator-set figure - no sales-forecast-driven par mode appears in xtraCHEF-Inventory-Counts, xtraCHEF-Inventory-Getting-Started or xtraCHEF-Advanced-Inventory-Training - and the workflow stops at a suggested order quantity rather than a generated purchase order. https://support.toasttab.com/en/article/xtraCHEF-Inventory-Counts · retrieved 2026-08-08

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

inventory-waste-logging

xtraCHEF's Manage Waste feature (Inventory > Manage Waste > + Add Waste) is a structured workflow with a date, an inventory item or ingredient, a Reason selector "to indicate the type of waste being logged", a quantity, and optional notes or an image. Waste cost is reported separately from usage variance: "xtraCHEF's Manage Waste feature gives you the actual dollar impact of these events" and it "ensures your Actual vs Theoretical Analysis reflects a true variance" by accounting for wastage independently. Shortfalls: the article does not enumerate the available reason codes, does not state that logging waste debits on-hand inventory quantity, and the capability lives in xtraCHEF, a separately licensed module, not in the base POS. https://support.toasttab.com/en/article/xtraCHEF-Inventory-Waste · retrieved 2026-08-08

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

Checked the xtraCHEF by Toast inventory doc set on support.toasttab.com: xtraCHEF-Inventory-Getting-Started (inventory area and count list setup, where the documented item attributes are purchase unit or UOM and par level), xtraCHEF-Inventory-Counts (count entry fields are UOM quantity and Need to Order, with a four-digit limit per item), xtraCHEF-Inventory-Waste, xtraCHEF-Advanced-Inventory-Training and xtraCHEF-Get-Started-With-Inventory-Reports. No expiration date, use-by date, lot date or shelf-life field appears on the item record, and no expiring-soon report or alert appears in the report catalogue. Also checked the POS-side Setting-the-Stock-Status-and-Count-for-Menu-Items, which carries only In stock, Out of stock or Limited stock plus a unit count. Because none of these pages claims to enumerate the complete item schema, this remains absence of evidence rather than a documented no. || 319th: CLAIM: tracks expiry/use-by dates and surfaces an expiring-soon alert. VERDICT: stays unknown. NEW SURFACE: updates.toasttab.com (LaunchNotes, 423 announcements 2023-09-02..2026-09-14, all fetched; found via crt.sh). inventory appears in 6 announcements, xtrachef in 0; expir* in 2, both poison ("Expired IDs now trigger a specific failure message in WeScan" - age-verification ID scanning; "expired loyalty rewards were shown to guests"); shelf 0; "use-by|use by date" 0. WHY NOT NO: the updates feed is a release-note stream, not an item-schema enumeration, and xtraCHEF/Toast IQ Inventory changes do not appear in it at all (xtrachef 0), so it cannot bound the inventory module. Retrieved 2026-09-16. || 322nd: VERDICT: stays unknown. NEW SURFACE (322nd): every support.toasttab.com page (Next.js "support-public-app", incl. its 404 page, e.g. https://support.toasttab.com/en/article/Zz-Nonsense-Article-Qq, HTTP 404, 578,781 bytes, anonymous) server-renders a LaunchDarkly allFlagsState object ("$flagsState") into the RSC payload: 4,148 flag keys spanning all Toast product lines (oo- online ordering, ksk- kiosk, loy-/ca- loyalty and consumer app, stp- Toast Local, lgc- gift cards, whsl- wholesale, ord-oapi- orders API ...), each with its evaluated value for an anonymous visitor. A flag list is NOT a feature census (flags are created and retired, and a value is per-context), so it can inform a note but cannot carry a yes or no. Controls over the keys: expir* 3, all POISON ("cp-disable-amex-expiry-validation", "pmts-ccsecure-validate-expiration-date" - card expiry; "ec-team-web-session-expiration-tracking" - login sessions); shelf 0, spoil 0, "use-by" 0, lot 0; batch 26, all engineering batching. xtraCHEF app.sa.toasttab.com redirects anonymously to /XtraChefAccount/Account/LogOn, which itself 302s (361 bytes) with no script bundle to read. Retrieved 2026-09-17. || 329th: MERGE HOLD (proposed no/C, held unknown): The enumeration is a 2022-01-20 xtraCHEF feature matrix and the module has since been rebuilt as Toast Inventory: a retired-generation document may not carry a `no` (320th policy). The current product page zero is a marketing page, grade C, and not an item-schema enumeration. PROPOSAL AS WRITTEN: NEW 2026-09-18 -- the gap named in the existing note ('none of these pages claims to enumerate the complete item schema') is closed by a vendor-published FEATURE MATRIX, on a domain no prior pass swept. VERDICT: unknown -> no / C. NEW SURFACE: xtrachef.com is still live and is a WordPress site (robots.txt 99 bytes, generic '*', Sitemap: /sitemap_index.xml). /wp-json/wp/v2/types lists no custom types; /wp-json/wp/v2/pages?per_page=100 returns 80 pages (1 page of results, page 2 = HTTP 400) and 0 posts. WARNING for the next pass: this is a PAGE-BUILDER HOLE -- content.rendered across all 80 pages totals only 6,015 chars, so the REST bodies are empty and a control run over them manufactures zeros; the prose only exists in the rendered HTML, which must be fetched per slug (nonsense control https://xtrachef.com/zzNonsenseQq329/ = HTTP 404, 2,351 chars stripped; real pages 4.2-6.6 K chars). EVIDENCE: https://xtrachef.com/featurematrix/ (18,693 bytes, 4,512 chars stripped) publishes a per-tier matrix ('= Available for opt-in = Not available') across On the House / Starter / Chef's Choice for eight named modules, and its Inventory Management section enumerates exactly seven features -- 'Drag and drop, shelf-to-sheet area and count list configuration', 'Take physical accounts on any device (off-line mode support)', 'Automatic inventory value updates based on the last 3, 6, or 9 purchase prices', 'Intuitive, easy-to-use interface on both desktop or mobile (offline mode capability)', 'Waste Reporting', 'Actual vs. Theoretical Variance Reporting', 'Depleting Inventory & Par Reporting' -- with no date, lot, use-by, expiry or shelf-life feature, and its Recipe Management section enumerates seven more ('Real-time, automated plate cost and variance updates...', 'Configurable unit-of-measure (UOM) calculations and conversions', 'Model the prime costs (including labor) and gross margins of prep recipes and recipes', 'PMIX Margin Variance Reports (available to Toast customers)', 'Upload images to menus and menu items', 'Multi-language support for preparation & procedures', 'Indicate potential allergens') with no prep-date or use-by-date field. CORROBORATION ON THE CURRENT PRODUCT: https://pos.toasttab.com/products/inventory-management fetched 2026-09-18 (106,709 bytes, 9,999 chars stripped) scores expir* 0, shelf* 0, spoil* 0, FIFO 0, rotat* 0, 'use by' 0, lot 0, while 'waste' 3 and 'par' 1 ('Schedule recurring orders to ensure you're maintaining par levels') -- the current page sells waste, variance and par, not dates. POISON NAMED: a bare `shelf` control is worthless on this vendor -- 'shelf-to-sheet' is xtraCHEF's name for its count-sheet layout and is 1 of 1 `shelf` hits in the matrix; `expir*` on Toast corpora is card expiry, session expiry and loyalty-reward expiry (3 of 3 flag hits, 2 of 2 LaunchNotes hits, 5 of 5 doc.toasttab.com 'expiration date' hits are all 'the two-digit month of the expiration date for the card'). BOUND HONESTLY STATED: the 1,205-document doc.toasttab.com census built this session (495 API-reference pages + 710 guide topics to a link fixpoint) CANNOT bound this cell -- `xtrachef` returns 0 hits in it and its only inventory pages are POS menu-item 86ing (adminMenuItemInventoryOverview, adminSettingInventoryStatusForMenuItems, adminMenuInventory86Report, apiUpdatingInventoryInformation), so the ingredient-level module is outside it. WEAKNESS: the feature matrix is dated 2022-01-20 in WP metadata and Toast has since rebuilt the module as 'Toast Inventory' / 'Retail inventory management'; the matrix is therefore an enumeration of the predecessor, corroborated but not replaced by the 2026 product page. If the owner treats a 2022 matrix as stale evidence, hold the row at unknown rather than downgrading the rest of the note. Retrieved 2026-09-18. adversarially verified

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

inventory-bar-partial-bottle

Bottle-fraction holding is documented and the weight/scale disjunct is documented as absent, but the capability binds only to a limited-release module. BINDS TO: Toast IQ Inventory, which its own FAQ states three times is not generally available -- 'Toast IQ Inventory is currently in limited release with select customers', 'available to select customers in a limited release', and 'Toast IQ Inventory is not generally available. It is in a limited release with select customers and is rolling out in phases, with capabilities arriving over time.' (Toast-IQ-Inventory-FAQ, re-retrieved 2026-09-15, 200, 710,638 raw / 25,779 chars stripped.) BOTTLE-FRACTION DISJUNCT MET: 'How do unit conversions work? Unit conversions are stored on the ingredient itself and applied everywhere that ingredient is used ... A spirit bought by the bottle and poured in fluid ounces is held in one unit and consumed in another. Conversions within the same family, such as volume-to-volume, are handled automatically. A conversion between families, such as weight to volume, asks you to confirm a density conversion the first time, then reuses it.' The same Q&A carries the operator-side symptom verbatim as an 'Also asked as' alias -- 'Why do some of my spirit bottles show as milliliters instead of bottles?' -- so an open bottle is held and reported in millilitres, not as a whole unit, which is exactly what this claim's why_it_matters asks for. Depletion is real-time at fire across every channel, counts are entered per item in the item's own unit from the stock counts area, and waste logged against an ingredient is 'deducted from stock'. WEIGHT/SCALE DISJUNCT DOCUMENTED ABSENT: the FAQ answers the question directly -- 'Will there be integrations with scales or draft systems? Scale and draft system integrations are an active area of research rather than an available capability. Barcode scanning is included, as is barcode label generation and printing.' Corroborated by the Overview's closed peripheral enumeration under Requirements and Permissions: 'No additional hardware is required, though a barcode scanner and a label printer are supported if you want to scan items during a count or print your own labels' (Toast-IQ-Inventory-Overview, 200, 7,403 chars stripped). Weight therefore enters only as a unit-conversion family, never as a captured measurement. SHORTFALLS NAMED: (1) limited release, select customers, not GA; (2) no scale or draft-system capture, per the FAQ sentence above; (3) bottle-versus-glass pooling is not built -- Known Limitations, 'Linking inventory of similar items - eventually, you will be able to link the inventory of multiple sellable items that deplete the same pool of inventory, like a bottle of wine and a glass of wine', restated in the FAQ as 'There is no default size multiplier, and that is deliberate. Two capabilities replace it: size modifiers ... and shared inventory, which links items that draw from a common stock using a ratio. Neither is available yet'; (4) bar-area granularity is absent -- 'Can I track inventory by sub-location? Tracking inventory by sub-location within a single site - separate bar, kitchen, and retail areas - is not available in the current release'; (5) 'Modifier selections impacting inventory calculations' is a Known Limitation, so a modifier-driven extra pour does not decrement. XTRACHEF, THE GENERALLY-AVAILABLE INVENTORY PRODUCT, DOES NOT CARRY THIS: 'bottle', 'scale', 'weigh', 'conversion', 'fluid ounce' and 'milliliter' are ALL ZERO across xtraCHEF-Inventory-Counts (5,596 chars), xtraCHEF-Inventory-Getting-Started (8,950) and xtraCHEF-Advanced-Inventory-Training (2,918), all re-fetched at 200 on 2026-09-15; counting there is by the item's purchase UOM with a par level. CONTROLS/POISON: 'partial' is ZERO in the FAQ, so the vendor never uses this claim's own word -- the finding rests on the spirits/millilitres passage, not on a keyword. MY OWN CONTROL CARRIED THE TRAP: 'weigh' returns 2 hits and one is 'There are feature gaps to weigh first', an ordinary verb; tokenised to the unit sense there is exactly one weight hit in 25,779 chars, the density sentence. 'bottle' returns 2 lines and both are the spirit passage; the single Overview 'bottle' hit is the wine limitation. Separately, Toast's bar-hardware route is third-party and after-the-fact: BarTrack 'compar[es] what's poured with what's sold through Toast', which measures pour variance rather than holding a partial bottle. https://support.toasttab.com/en/article/Toast-IQ-Inventory-FAQ · retrieved 2026-09-15 adversarially verified

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

xtraCHEF automatically syncs accurately coded invoice data to accounting systems with GL coding. Specific named target formats and per-category mapping detail not enumerated publicly. https://pos.toasttab.com/products/xtrachef · retrieved 2026-08-01

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

Toast help centre documents Recipes as a feature of 'Toast's Inventory Management': the recipe is tied to a 'Menu item from your POS', ingredients are added with quantity and unit of measure, and 'Toast automatically calculates the cost contribution of each item and the total recipe cost from its ingredients', recalculating 'instantly whenever an ingredient's price changes' so COGS stays current. Purchase data feeds it from Toast-owned xtraCHEF invoice capture. No MarginEdge/MarketMan/R365 contract is required, though inventory is a paid Toast module rather than base-POS functionality. https://support.toasttab.com/en/article/Get-Started-With-Recipes · retrieved 2026-08-06

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

Variance Analysis and Product Mix reports join recipe cost to Toast sales mix to spotlight where menu changes lift profitability. A configurable below-threshold margin flag is not documented. https://support.toasttab.com/en/article/xtraCHEF-Recipe-Reporting · retrieved 2026-08-01

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

Toast Web plus a manager mobile app give near-live sales off-premise; specific latency not published.

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

Same defect - the note reasons from the Cash Management API rather than from any documented close-out report. adversarially verified

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

reporting-pmix-modifier-level

Product mix at item and modifier level, filterable by daypart and revenue center; not verified against a specific report doc.

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

Comps/voids/discounts attributed to employee and approver with reason codes; immutability not verified.

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

Justified by the existence of a Cash Management API, which is not the same as a drawer/shift/employee over-short report in the reporting UI. Inference from an API surface to a report is over-generous. adversarially verified

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

Sales per labor hour and labor percent by hour and employee, sourced from POS time clock data.

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

Per-server reporting is documented only as item sales: "you can also view individual server's item sales by selecting Server from the first drop-down and Item name in the second", and only for date ranges of seven days or less. SHORTFALL: average check per server, items per check, attachment rate for named categories and tips as a percentage of sales are not present in this documentation. https://support.toasttab.com/en/article/Sales-Reports-Overview · retrieved 2026-08-02 adversarially verified

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

Revenue centers can isolate each third-party channel for revenue reporting, but margin net of marketplace commission is not documented as a built-in report. https://support.toasttab.com/en/article/Revenue-Centers-for-3rd-Party-Online-Ordering-Integrations · retrieved 2026-08-01

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

Recurring emailed report delivery is standard in Toast Web; cadence and recipient-list configuration not verified against a doc.

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

Docs are fully public and self-serve Standard API credentials exist — but they are GET-only and require an RMS Essentials+ subscription per location. Write access needs a partner agreement. https://doc.toasttab.com/doc/devguide/devApiAccessFAQs.html · retrieved 2026-08-01

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

Webhooks exist but are provisioned by contacting the Toast integrations team with your endpoint; retry behavior and payload signature verification are not published. https://doc.toasttab.com/doc/devguide/apiOverview.html · retrieved 2026-08-01

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

Verified verbatim in Toast's own dev FAQ: "Standard API access only supports GET requests" and every location requires "a subscription to Toast Restaurant Management Suite Essentials or higher." Vendor-affirmed plan gating - a legitimate 'no'. https://doc.toasttab.com/doc/devguide/devApiAccessFAQs.html · retrieved 2026-08-01 adversarially verified

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

Core sales/labor/PMIX reporting is included with the POS plan, but multi-location comparison and API/analytics access sit behind higher Restaurant Management Suite tiers.

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

Toast documents the window: "You can access data for the last 48 months, and you can filter a report for six months at a time." That exceeds the 24 months the claim asks for. Shortfalls: retention is not uniform across the reporting UI - "The Sales Summary can show data from the past 15 months. For data older than 15 months, contact Customer Care" - so there is per-report truncation well ahead of the 48-month figure and an archive-retrieval step through support, though no fee is stated for it. Toast also notes "At this time, there is no single export of your Toast data", that "data backup/retention availability may differ by market" with some international markets as short as 30 days, and that after account closure "your data will be accessible for 60 days." https://support.toasttab.com/en/article/Can-I-download-a-back-up-of-all-of-my-Toast-data · retrieved 2026-08-08

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

Toast IQ is the pattern-deviation half: it "proactively surface[s] key insights about your business and the local market" and identifies "changes in item sales or local events that may impact your business", delivered into a "For You feed". Shortfalls: the article documents no push or email delivery for those insights and no configuration at all, and the rest of Toast's notification surface is enumerated and event-driven rather than threshold-driven - the Toast app sends exactly three notifications (new online order, KDS-fulfilled ticket, offline payment retry failed), and Text Alerts are manual, with Toast stating "At this time, these text alerts are not automatic - the user on the POS will need to manually send a text alert." There is no operator-configured metric threshold on sales, voids, discounts or labor percentage anywhere in these screens. https://support.toasttab.com/en/article/Toast-IQ-Overview · retrieved 2026-08-08

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

Toast IQ expanded in 2026 from smart features into an AI assistant positioned to answer questions against operator data. Marketing announcement, not product documentation. https://pos.toasttab.com/news/toast-expands-toast-iq-smart-ai-assistant · retrieved 2026-08-01

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

New-vs-returning and lapsed cohorts drive Toast Marketing automations; a dedicated guest cohort analytics report with lifetime spend was not verified.

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

Toast markets forecasting feeding labor planning; a daypart/hourly forecast exposed in the reporting UI was not confirmed in documentation.

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

Tips Manager plus Toast Payroll produce declared vs charged tip detail, pool distribution records and payroll-ready tip reporting. https://support.toasttab.com/en/article/Toast-Payroll-Tips-Manager-Setup · retrieved 2026-08-01

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

Restaurant management groups are a first-class Enterprise-module object that shared configuration, menus and reporting scope to. https://doc.toasttab.com/doc/platformguide/sharingMenusAndOtherInformationAmongRestaurants.html · retrieved 2026-08-01

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

multi-location-central-menu-publish

Menus (or portions of menus), void reasons, employees and job descriptions are authored once and shared to selected locations. A publish/version history log of what was pushed, when and by whom is not documented. https://support.toasttab.com/en/article/Copying-Menus-to-Other-Locations-Using-Multi-Location-Management · retrieved 2026-08-01

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

Menu versions let one shared item carry different prices/offerings per location without duplicating the item record and without polluting above-store reporting. https://doc.toasttab.com/doc/platformguide/platformMenuManagerMenuAndMultiLocationRestaurants.html · retrieved 2026-08-01

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

Above-store reporting aggregates across selected locations from one place. Store-vs-store ranking and automatic variance flags not explicitly documented. https://pos.toasttab.com/products/multi-location-management · retrieved 2026-08-01

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

Locations added to a shared Gift Card/Loyalty group redeem interchangeably: "your customers can purchase or redeem gift cards or loyalty points at any location within the group", configured under Location groups > Loyalty. Outstanding liability is reported - setting the Gift Card Liabilities report's start and end dates to the same day gives an Ending Liability value that "is your total outstanding gift card liability as of that date" (liability = Total Sales minus Total Redemptions). Inter-store settlement is explicit: the report "tracks each transaction in relation to the store that owns the card's liability (the original purchase store) versus the store that redeemed the value", "The redemption store is always owed the amount for accepting the original store's gift card and honoring that liability", with Debit and Credit columns, and it "allows you to periodically audit how much each store owes the others based on liability amount vs. redeemed amount." https://support.toasttab.com/en/article/Using-Gift-Cards-at-Multiple-Locations · retrieved 2026-08-08

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

A single Toast Loyalty profile and balance spans the brand's locations; not verified against a doc page.

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

Toast implements a second brand as a second location with its own back end, not as a mode on one terminal: "Since your virtual restaurant is a separate location and thus has an individual back-end, it's important to be able to compare sales across all locations." The hardware condition in the claim is documented as impossible - "There must be a separate device for each virtual restaurant, even if you are operating multiple ghost kitchens out of the same location" - plus "At least one hard-wired terminal in order to run a virtual restaurant." Separate menus, ticket differentiation via dining options and prep stations, and separately reportable revenue are all supported; running them on the same terminal and drawer is not. Toast also notes the setup "will not work with Kitchen Display System (KDS)" - virtual brand orders print but do not appear on KDS screens. https://support.toasttab.com/en/article/Setting-Up-a-Virtual-Restaurant · retrieved 2026-08-08

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

Per-location tax configuration with multiple simultaneous rates and inclusive/exclusive handling; jurisdiction-specific prepared-food rules and per-location exemptions not verified.

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

Overtime rules are configurable per restaurant at Employees > Employee management > Overtime rules, with Rule Type (weekly hours, daily hours, or consecutive days worked), a threshold value, and an overtime rate factor. Shortfalls against the claim: they are reporting constructs, not terminal enforcement - configured rules "impact your Labor Summary and payroll reports" and surface under Labor reporting, with no clock-in block or terminal warning documented. The one rule that is enforced at the terminal, the clock-in and clock-out window around a scheduled shift (manager passcode or swipe card to override), "requires a scheduling integration that works with schedule enforcement" rather than being native. Toast documents configuration at the individual restaurant level only - no per-location-group scoping of labor rules appears - and no predictive-scheduling compliance rule exists at all. https://support.toasttab.com/en/article/Creating-New-Overtime-Rules · retrieved 2026-08-08

The POS software runs on commodity off-the-shelf hardware (standard iPads, Android tablets, or PCs) that the operator can buy from a third party, rather than only on vendor-supplied proprietary terminals. differentiator

hardware-commodity-devices

Toast's own app-installation article supplies the direct prohibition: "You should not use an Android mobile device/phone (or any other non-Toast hardware) to operate your business, take payments, or use Toast POS." Sideloading the APK is sanctioned only so a device can act as an emulator for viewing menus and features, and "The Toast app is not available for iOS" at all, which rules out the standard-iPad route. This sits alongside the Non-Supported Hardware Devices article, which retires the generic tablets Toast once ran on (Samsung 7, 8 and 10 inch, Acer, Azpen, OnePlus, Elo V1) and states they will require a new device to be purchased, and the Toast Hardware Hub, which enumerates the vendor-supplied terminals (Flex 3, Flex 14, Flex for Guest and Kitchen, Go 2 and 3, Kiosk, Elo V2, V3 and V4). https://support.toasttab.com/en/article/Installing-an-APK-Link-1492745822838 · retrieved 2026-08-08

Vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs.

hardware-os-platforms

Toast documents and identifies its own device lineup (Flex, Go 3, KDS) and Toast Web runs in a browser, but there is no supported-third-party-OS matrix because third-party clients are not supported. https://support.toasttab.com/en/article/What-Kind-of-Hardware-Do-I-Have · retrieved 2026-08-01

Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.

hardware-handheld-purpose-built

Toast Go 3 is a purpose-built handheld with an integrated card reader. Published drop and IP ingress ratings were not verified in this pass. https://pos.toasttab.com/hardware/toast-go · retrieved 2026-08-01

The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator

hardware-handheld-battery-swap

Toast publishes a step-by-step operator procedure for replacing the Toast Go 2 battery in the field and sells the part as the "Toast Go 2 Battery Replacement Kit" - the article carries a stock notice reading "The Toast Go 2 Battery Replacement Kit is temporarily out of stock starting the week of August 10, and we expect it back in stock in mid-October." The battery is therefore field-replaceable by the operator rather than a depot repair, which is the branch of the disjunctive claim that is satisfied. Narrower reading: Toast does not describe the swap as hot (the procedure powers the device down), and no published rated battery life in hours or per shift was found for Toast Go 2 or Toast Go 3 on support.toasttab.com or pos.toasttab.com/hardware. https://support.toasttab.com/en/article/Replacing-the-Battery-and-Card-Reader-in-Your-Toast-Go-2 · retrieved 2026-08-08

Handhelds support cellular/LTE connectivity as a documented fallback when store Wi-Fi drops, either built into the device or via a vendor-supplied failover.

hardware-handheld-lte

Toast explicitly sells a 'Wi-Fi Only Handheld' starter kit, which implies an LTE-equipped variant exists, but the LTE failover behavior is not documented in what was retrieved. https://pos.toasttab.com/shop/starter-kits/handheld-starter-kit · retrieved 2026-08-01

Terminals continue to take orders, print to kitchen, and record cash sales with the internet down, and the vendor documents explicitly which functions degrade (card auth, loyalty lookup, refunds).

hardware-offline-mode

Confirmed including the sharp caveat - EMV chip mode is listed as unavailable, swipe only. https://doc.toasttab.com/doc/platformguide/platformOfflineModeLocalSync.html · retrieved 2026-08-01 adversarially verified

Sells or supports a dedicated kitchen display system with bump-bar or touch input, station routing, and course/fire timing, as a first-party product rather than an integration-only dependency.

hardware-kds

First-party KDS hardware and software with station routing, expo, prep-time firing and all-day counts. https://pos.toasttab.com/hardware/kitchen-display-system · retrieved 2026-08-01

Offers a self-order kiosk running the same menu and modifier engine as the POS, in both countertop and freestanding form factors, with integrated payment and accessibility (ADA) compliance documented. differentiator

hardware-kiosk

First-party kiosk on the same menu engine with integrated payment. Countertop vs freestanding SKUs and ADA conformance documentation were not verified. https://pos.toasttab.com/hardware · retrieved 2026-08-01

Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, and speaker/headset integration, with a documented timer/speed-of-service measurement.

hardware-drive-thru

Toast Drive-Thru (April 2026) is a unified hardware + software solution with Speed of Service measurement and Drive-Thru KDS. Outdoor menu boards, confirmation displays and headset integration are not itemized publicly. https://pos.toasttab.com/news/toast-drive-thru-launch-2026 · retrieved 2026-08-01

Works with standard ESC/POS thermal receipt and kitchen printers from more than one manufacturer (e.g. Epson and Star), including LAN/Ethernet printers, rather than only vendor-branded printers.

hardware-printer-compatibility

Toast supports LAN kitchen printers and historically Epson/Star ESC/POS models, but Toast sells and provisions its own printers and no public multi-manufacturer compatibility list was located.

Supports the standard peripheral set — cash drawers (including multi-drawer per terminal), barcode scanners, scales for by-weight items, and customer-facing displays — with a published compatibility list.

hardware-peripherals

Cash drawers, barcode scanners, scales and customer-facing displays are supported through Toast Shop; a published third-party compatibility list was not found.

Card entry happens on a PCI-listed PTS device using validated point-to-point encryption, so the POS application and tablet stay out of PCI scope; the vendor states the merchant's SAQ type.

hardware-p2pe-terminal

Toast confirms all payment devices meet or exceed PCI requirements and takes on most PCI obligations, but does not publish a validated P2PE listing or name the merchant's SAQ type — it instead says most customers need not submit an SAQ/AOC at all. https://support.toasttab.com/en/article/What-is-PCI-Compliance · retrieved 2026-08-01

Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. differentiator

hardware-tap-to-phone

Toast enumerates its contactless acceptance surface and it is entirely vendor hardware. Take Payments on the POS lists mobile wallet support on "Toast Go 2, Toast Go 3, and Toast Tap (on-counter or direct-attach)", and the dedicated article states that Apple Pay, Google Pay and Samsung Pay are not accepted directly on the Toast tablet (POS) - acceptance requires the Toast Tap reader or a Go handheld with a built-in NFC reader. There is no Tap to Pay on iPhone or Tap to Pay on Android offering: the Toast app is not available for iOS at all, and Toast instructs operators not to use a non-Toast Android phone to take payments. https://support.toasttab.com/en/article/Which-Toast-devices-support-Apple-Pay-Google-Pay-and-Samsung-Pay · retrieved 2026-08-08

Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator

hardware-pricing-transparency

Starter kits are publicly priced (from $0 upfront for the first device) and Toast Shop is public, but per-SKU list prices for Toast Flex and Toast Go 3 are not visible without an account. https://pos.toasttab.com/shop/starter-kits · retrieved 2026-08-01

Hardware can be purchased outright (owned) as an alternative to a mandatory lease or subscription-bundled rental, and the vendor states which. differentiator

hardware-ownership-vs-lease

Toast documents multiple payment routes for starter kits including outright purchase, a no-upfront-cost option and a pay-as-you-go all-in-one platform rate, plus third-party financing at fixed monthly or percentage-of-sales. Which SKUs can be owned outright at what price is not fully published. https://support.toasttab.com/en/article/How-customers-can-pay-for-Toast-Starter-Kits-Internal · retrieved 2026-08-01

Vendor documentation confirms whether hardware purchased from the vendor remains usable with other software after cancellation, i.e. it is not software-locked or remotely bricked. differentiator

hardware-usable-after-churn

Toast now documents the lock directly: "each hardware device running Toast software needs a matching software subscription to stay active"; when a device is unlicensed the operator has 14 days, and "if no action is taken within the 14-day grace period, the unlicensed device will lock, and you'll see a message on-screen prompting you to purchase a subscription before continuing use." Reuse is documented only within the Toast ecosystem — Reusing Approved Hardware Devices at a New Location requires a factory reset and says access-point reuse is allowed "provided that the hardware was originally purchased from Toast." So the vendor's own docs confirm the device is software-locked to an active Toast subscription; nothing documents usability with other software after cancellation. https://support.toasttab.com/en/article/Device-Licensing-FAQ · retrieved 2026-08-02 adversarially verified

Publishes a hardware warranty term and a replacement/advance-exchange SLA with a stated turnaround (e.g. next-business-day depot swap). differentiator

hardware-rma-sla

Toast's US Limited Hardware Warranty publishes both halves. Term: Toast Products "will not have substantial defects in materials and workmanship, for 12 months from the date of shipment for all handheld devices, and 24 months from the date of shipment (the 'Warranty Period') for all other Toast Products", and "Any replacement hardware will be warranted for the remaining duration of the original Warranty Period, or 30 days, whichever is longer." Advance-exchange SLA: "If a Toast Customer Care representative has issued you an RMA number, we will make reasonable efforts to ship an advance replacement product to you by next day air saver service by the next business day", with the faulty unit due back within 30 days of the advance replacement shipment or the operator is charged for the part. The support-side RMA article adds standard shipping of three to five business days and expedited of one to two. https://pos.toasttab.com/limited-warranty · retrieved 2026-08-08

Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.

hardware-byod

Toast prohibits the staff-BYOD pattern the claim describes: "You should not use an Android mobile device/phone (or any other non-Toast hardware) to operate your business, take payments, or use Toast POS", and it warns specifically against using such a device to send orders to the kitchen. Sideloading the app onto a personal Android device is sanctioned only as an emulator for previewing menus and features, and "The Toast app is not available for iOS." The Toast apps that are documented for personal devices are not ordering or payment apps: MyToast is an employee payroll and shift app, Toast Now is a manager reporting app, and Toast Tables is a host and reservation app with its own documented device list. There is therefore no documented permission and security model for staff taking orders or payments on their own phone. https://support.toasttab.com/en/article/Installing-an-APK-Link-1492745822838 · retrieved 2026-08-08

Provides a remote device-management console showing each terminal, printer, and KDS as online/offline, with remote reboot, software-version visibility, and staged rollout of updates. differentiator

hardware-remote-device-management

Toast exposes a Device Details API and device visibility in Toast Web. Remote reboot, software-version visibility and staged rollout controls for operators were not documented. https://doc.toasttab.com/doc/devguide/apiOverview.html · retrieved 2026-08-01

Integrates with specialty beverage hardware — self-pour tap walls, flow meters, or liquor pour spouts — such that pours post to a POS tab automatically.

hardware-selfpour-scales

Self-pour dispensing hardware is an integrated, first-party-documented partner; automatic pour-to-tab is not documented. Refetched 2026-09-15 via curl (HTTP 200, 627,787 bytes); every quote confirmed verbatim against raw bytes. Toast help centre, last updated Aug 28 2026: "The Napa integration enhances the guest experience for self-pouring beverages and helps customers extend their inventory’s shelf life with special technology", naming "Napa Technology’s flagship product, the TapStation and WineStation, along with their AI-integrated Bacchus system", enabled at Integrations > Integrations management > Browse & purchase integrations with onboarding by a Napa representative. Napa’s own site independently establishes the hardware class and the Toast link at grade D (napatechnology.com robots.txt disallows only /wp-admin/; FAQ retrieved 2026-09-15): WineStation is "an automated, temperature-controlled wine dispensing and preservation system that allows guests to pour their own wine", with "built-in access controls that allow venues to authorize guests through RFID cards, room keys, wristbands, credit cards, or custom access codes", and "Integrates with leading point-of-sale and property management systems, including Toast, GoTab, Clover, Focus, Opera, and MICROS Symphony". SHORTFALL, on the claim’s operative "such that pours post to a POS tab automatically": no sentence on either side says a dispensed pour opens or posts to a Toast check. Toast’s stated benefits are operational and analytical only ("easier for customers to manage orders, track inventory, and process transactions efficiently"; "insights into sales trends, inventory levels, and customer preferences"). Napa documents automatic charge posting only on the hotel PMS path -- "Room Key integration to allow guests to enjoy the WineStation and insure accurate billing with the room key billing system" -- and on the POS path says nothing beyond "integration with all major Point of Sale systems including Toast". SECOND SHORTFALL: this is a paid partner integration behind the Toast Partner Integrations entitlement, not native Toast capability. POISON: "PourThat" is the top "pour" hit in Toast’s support slugs and is a drink-ordering and payment app, not pour hardware; "shelf life" on toasttab.com is Napa’s wine preservation, not date tracking. SCOPE/DOUBLE-COUNT: BarTrack (https://support.toasttab.com/en/article/BarTrack-Integration-Inventory-Analytics, refetched 2026-09-15, HTTP 200) is deliberately NOT load-bearing here -- it is explicitly after-the-fact reconciliation, "By comparing what’s poured with what’s sold through Toast" -- so this cell and inventory-bar-partial-bottle do not rest on the same sentence. https://support.toasttab.com/en/article/Get-Started-With-the-Napa-Technology-Integration · retrieved 2026-09-15 adversarially verified

Supports inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call.

hardware-callerid-integration

Toast documents a first-party Caller ID module with named hardware: "Toast supports two types of Caller ID boxes: Vertex (VoIP) and Whozz Calling (Analog)", with compatible models listed as Whozz Calling? Basic 2 Line version 2.8, Basic 4 Line version 12, and Vertex VoIP Unit 2 Line version 85-19. The record pop is real - "a pop-up will appear during an incoming call that allows the server to start the order, put the order on hold, or ignore the order", and "When a returning customer calls, their name, number, and address will automatically be populated in the delivery information screen." Shortfalls: the pop surfaces contact details only, not the guest's order history as the claim requires; the pop-up "will only appear when a server is in Quick Order Mode" and in other modes such as Table Service the call is only a corner notification; the module must be enabled by Toast Customer Care and the software module purchased; and "At this time, Caller ID is only available for restaurants located in the U.S." https://support.toasttab.com/en/article/Caller-ID-1492794310341 · retrieved 2026-08-08

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

extensibility-public-api-docs

doc.toasttab.com is fully public — API overview, authentication, scopes, rate limits and example requests all readable with no NDA or sales call. https://doc.toasttab.com/doc/devguide/apiOverview.html · retrieved 2026-08-01

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

extensibility-api-access-cost

Confirmed. Note the FAQ states the subscription requirement but no dollar figure, so the magnitude of the upcharge is unknown. https://doc.toasttab.com/doc/devguide/devApiAccessFAQs.html · retrieved 2026-08-01 adversarially verified

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

extensibility-free-sandbox

Sandbox credentials and hostname are issued by the Toast integrations team when you begin building an integration — there is no self-serve free sandbox for developers without that relationship. https://doc.toasttab.com/doc/devguide/apiClientAccounts.html · retrieved 2026-08-01

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

OAuth 2 client-credentials grant with bearer tokens and documented scopes — machine-to-machine, not an operator-facing authorization-code consent flow. Restaurant access is granted through Toast's partner connection process rather than a per-app consent screen the operator can individually revoke. https://doc.toasttab.com/doc/devguide/authentication.html · retrieved 2026-08-01

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

extensibility-webhooks-push

Real-time webhooks exist for integration and order lifecycle events, but they are partner-provisioned — you supply your endpoint to the Toast integrations team rather than self-configuring. https://doc.toasttab.com/doc/devguide/apiOverview.html · retrieved 2026-08-01

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

extensibility-webhook-reliability

Two of three legs are documented. Signing: the message-signing page states the body and timestamp are concatenated, hashed and signed with HMAC-SHA256 using the subscription's secret key and published in the Toast-Signature header. Retry: on timeout, 404, 429 or 5xx the platform 'will wait five minutes and then resend the update', then waits 10 minutes and resends a second time, and 'if the second resend attempt fails, the Toast platform does not send the update again' (restaurant availability updates alone 'retry five times in a minute with exponential back-off'). Missing leg: no replay endpoint, redelivery request or stored event log for missed deliveries appears anywhere in the webhooks section of doc.toasttab.com/doc/devguide - after two failures the event is lost and the integrator must backfill from the Orders API. https://doc.toasttab.com/doc/devguide/apiRetrySupport.html · retrieved 2026-08-08

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

The Orders API accepts externally originated orders as first-class Toast tickets that route to KDS/printers and land in reporting; a Tender API also exists for external payment. Partner-gated. https://doc.toasttab.com/doc/devguide/apiOverview.html · retrieved 2026-08-01

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

extensibility-menu-write-api

The developer guide states flatly: 'Menus API supports data retrieval only', and that 'Menus API supersedes configuration API and menu data export for menu data retrieval'. The Menus V3 OpenAPI reference exposes exactly two operations, 'Get menus' and 'Get menu last modified timestamp', both GET. The Configuration API 'returns information about the configuration of a restaurant and its menus, such as menu items' with no create/update operations. The complete OpenAPI index at doc.toasttab.com/openapi lists Analytics, Authentication, Cash Management, Configuration, Credit cards, Device details, Kitchen, Labor, Menus V2, Menus V3, Order management configuration, Orders, Packaging configuration, Partners, Restaurant availability, Restaurants and Stock - no menu, modifier or price write API among them. Stock allows updating item availability, not item, modifier or price definitions; the Orders API's plu field is explicitly 'a read-only value and your integration cannot set or modify this value in a POST request'. Menu authoring is a Toast Web operation, not an API operation. https://doc.toasttab.com/doc/devguide/apiGettingMenuInformationFromTheMenusAPI.html · retrieved 2026-08-08

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

extensibility-doordash-preferred

DoorDash publishes its own complete provider registry at https://merchants.doordash.com/api/partner-integrations — 64 providers, each carrying a `qualityStatus` of PREFERRED (12), CERTIFIED (47) or AT_RISK_OF_SUSPENSION (5), plus a features-completed count against the eight high-quality features the program requires. It is served anonymously and merchants.doordash.com/robots.txt permits it (Allow: / with only /cdn-cgi/ and /monitoring barred). This is the instrument the program page points to when it says the roster is tracked in real time, and it supersedes the 2026 announcement post most of this corpus cited — that post introduces its ten names with the word `include`, which makes it a floor, not a ceiling. In that registry this vendor is the entry `toast`, rendered as 'Toast', with qualityStatus PREFERRED and 8 of the 8 high-quality features built. GRADE HARMONISED TO B, 2026-09-11: this URL was first written at grade A. The adversarial pass ruled E on the principle that the rubric grades by the publisher's relationship to the SCORED vendor, and DoorDash is not that vendor. B is the settlement, for two reasons that are not preference: 39 rows already graded a DoorDash-published document B on this claim before today, and one URL on one claim cannot carry two grades; and E is unworkable, because nine of the 47 rows are `yes` on a differentiator-weight claim, which the grade floor refuses below B. B reads as the product documentation of the programme's own publisher, which is what this registry is. The dissent is recorded in verification.jsonl. https://merchants.doordash.com/api/partner-integrations · retrieved 2026-09-11

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

Toast-owned direct integrations with DoorDash, Grubhub, Uber Eats and Caviar — no paid middleware layer required. https://pos.toasttab.com/third-party-delivery-integrations · retrieved 2026-08-01

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

extensibility-middleware-compatibility

Not verified against any middleware vendor's own documentation by the researcher, and not by me. Deliverect/Chowly/Otter/Checkmate support for Toast is plausible but unsourced here. adversarially verified

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

xtraCHEF syncs GL-coded invoice and COGS data into accounting systems as mapped entries rather than raw CSV. The full list of named target systems was not enumerated publicly. https://pos.toasttab.com/products/xtrachef · retrieved 2026-08-01

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

extensibility-payroll-export

Labor hours do leave the system without re-keying: Toast Web has a 'Payroll Export' under Reports > Labor > Labor summary, downloaded as an Excel file from the Employee Summary section (requires the 3.12 Shift Review permission). The Automated Nightly Data Export additionally delivers a Labor/Employee 'Time Entries' data set to an S3 bucket over SFTP. Shortfall against the claim as worded: no named third-party payroll provider. Neither the payroll export article, the Toast Payroll Export Employee Data article, the nightly data export article, nor the 137 partners in the pos.toasttab.com integrations sitemap name Gusto, ADP, Paychex, Paylocity or any equivalent, and no provider-specific export format is documented. The only named payroll destination is Toast's own Toast Payroll (Toast Payroll and Toast POS Integration Guide). The export is a generic spreadsheet, not a provider-formatted feed. https://support.toasttab.com/en/article/I-can-t-download-the-payroll-export · retrieved 2026-08-08

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

extensibility-app-marketplace

Toast operates a public partner directory of named third-party integrations that operators can browse. https://pos.toasttab.com/partners/directory/stream · retrieved 2026-08-01

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

The Orders and Tender APIs let a third-party UI drive Toast transactions (this is how partner kiosks and ordering front-ends work), but Toast does not market or document a formal headless mode. https://doc.toasttab.com/doc/devguide/apiOverview.html · retrieved 2026-08-01

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

Machine-readable and broad in scope: the export covers Sales/Finance (Order Details, Payment Details, Item Selection Details, Modifier Selection Details, Kitchen Details, Cash Management, Product Mix), Labor/Employee (Time Entries), Accounting, and Configuration (Menu), delivered to an S3 bucket reached over SFTP with credentials and SSH keys. Shortfalls against 'complete historical export on demand at contract end': it is a rolling nightly feed generated 'within one hour after each restaurant's configured closeout hour' containing 'the previous business day' only; 'data is stored for seven days before being cycled out'; no historical backfill mechanism is documented; and access is not self-serve - 'you must contact Toast Customer Care to receive data export access' plus the 8.3 Data Export Config permission. Guest/customer records are not among the listed data sets and must be pulled separately from the Guestbook CSV. At contract end the Merchant Agreement section 8.5 gives 30 days of access to retrieve a copy rather than a delivered export package. https://support.toasttab.com/en/article/Automated-Nightly-Data-Export-1492723819691 · retrieved 2026-08-08

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

reliability-offline-order-entry

Order entry continues on-terminal; printer connections remain functional during internet outages since the LAN is unaffected. Devices enter offline mode roughly 40 seconds after losing connectivity. https://doc.toasttab.com/doc/platformguide/adminOfflineModeOverview.html · retrieved 2026-08-01

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

reliability-offline-card-auth

No authorization happens offline. Toast's own doc: card data is encrypted and stored, then "sends the stored card information to the card networks for authorization" only on reconnect - no floor-limit or offline approval. It must be pre-enabled, and under the new local-sync architecture "EMV credit card mode (credit cards must be swiped)" is explicitly unavailable, so chip acceptance dies during the outage. That is degraded store-and-forward, not offline card authorization. https://doc.toasttab.com/doc/platformguide/adminOfflineCCPayments.html · retrieved 2026-08-01 adversarially verified

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

Toast states the merchant is responsible for declined, expired or disputed offline payments and warns authorizations may expire within 24 hours. An optional per-transaction cap with manager override is configurable; no cumulative cap is documented. https://support.toasttab.com/en/article/Prepare-to-Operate-in-Offline-Mode-During-Service-Disruptions-or-Outages · retrieved 2026-08-01

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

Verified verbatim: "Orders sent from one POS device cannot be seen on another device unless it is a KDS device." Toast even advises each employee stay on a single device while offline. Kiosks also stop entirely offline. https://doc.toasttab.com/doc/platformguide/platformOfflineModeLocalSync.html · retrieved 2026-08-01 adversarially verified

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

There is a local hub device — an ordinary Toast terminal, typically a hardwired stationary one, auto-designated as relay — but it is not a dedicated on-premise transaction engine or edge server. Toast is migrating all customers onto this local-sync model and deprecating the older offline method. https://doc.toasttab.com/doc/platformguide/platformOfflineModeLocalSync.html · retrieved 2026-08-01

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

reliability-offline-kds-printing

KDS devices receive all orders from every POS on the LAN via the local hub during an internet or cloud outage, and printers keep working. During a local network failure, however, there are no printer connections. https://doc.toasttab.com/doc/platformguide/platformOfflineModeLocalSync.html · retrieved 2026-08-01

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

Failover is documented and configurable. The Add-a-kitchen-printer page describes a Backup Printer field: 'If printing fails at this printer, the system redirects tickets to the backup printer.' The platform guide further advises that in a KDS-primary restaurant you add a kitchen printer to act as the backup when the system is offline, that a single backup printer should be assigned to every prep station, and that with a backup printer configured and a local network connection an Autofire-assigned device still fires and prints tickets. Shortfall: the alerting half of the claim is undocumented. Neither adminAddKitchenPrinter.html, the Kitchen Printer Troubleshooting FAQs nor Get Help With Printers Going Offline describes any banner, on-screen alert or notification telling staff that a printer was unreachable or that a ticket was rerouted - the failover is silent as documented. https://doc.toasttab.com/doc/platformguide/adminAddKitchenPrinter.html · retrieved 2026-08-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

What is documented is the avoidance design, not a resolution algorithm. The local-sync page states 'orders sent from one POS device cannot be seen on another device unless it is a KDS device' and recommends 'each employee choose a single device to place and update orders'; the support guidance to operators is 'Stick to one device per employee so order and payment information stays together.' Toast also documents the failure mode when that is not observed: 'If you found duplicate or additional items on checks after using your Toast device in Offline Mode, you must void (remove) the extra or duplicate item(s) to close the check.' Shortfall: no stated conflict-resolution behaviour. Neither platformOfflineModeLocalSync.html, adminOfflineModeOverview.html nor the offline-mode support articles name a rule (last-write-wins, merge, operator prompt), describe reconciliation on reconnect, or say what happens if the local hub device itself fails. The documented remedy is manual voiding after the fact. https://doc.toasttab.com/doc/platformguide/platformOfflineModeLocalSync.html · retrieved 2026-08-08

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

Best-in-class here. Toast explicitly enumerates what is unavailable offline: gift cards (sale and redemption), loyalty redemption, Tender API payments, text to pay, customer credits, comp cards, house accounts and card pre-authorization. Under local sync, EMV chip readers are also disabled and kiosks stop entirely. https://doc.toasttab.com/doc/platformguide/platformOfflinePaymentsOverview.html · retrieved 2026-08-01

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

reliability-public-status-page

status.toasttab.com is public with per-component status (Order Processing/KDS, Card Processing, POS app) and incident history. No published uptime percentage. https://status.toasttab.com · retrieved 2026-08-01

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

Sole source is the pricing page, which could not be retrieved (403). This is an unverified marketing claim contradicted by the dossier's own complaint section. Marketing copy is not capability. https://pos.toasttab.com/pricing · retrieved 2026-08-01 adversarially verified

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

Enterprise marketing page only; no product documentation of an on-site installation offering, coverage area, or what it costs. Claim-level at best. https://pos.toasttab.com/restaurant-pos/enterprise · retrieved 2026-08-01 adversarially verified

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

reliability-menu-build-service

The Remote/Onsite Onboarding Guide states 'Toast configures your menu from customizable templates that you then edit', and the engagement includes an assigned Onboarding Consultant and a scheduled menu review session. Shortfall: this is not a turnkey menu build. The same guide makes the operator responsible for the input - customers must 'Complete the Get Started With Toast Menus course and finalize your menu template' as preparation for the review appointment - so Toast supplies and configures the template structure while item-level entry and finalization sit with the restaurant. No documented full menu-entry-as-a-service, and the scope is not stated to vary by package on any retrievable page. https://support.toasttab.com/en/article/Remote-Onsite-Onboarding-Guide · retrieved 2026-08-08

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

reliability-hardware-replacement-sla

The Return Merchandise Authorization article documents an advance-exchange flow with a published turnaround: standard shipping 'three to five business days', expedited 'one to two business days but may incur additional fees'. Replacement is free for in-warranty devices covering 'hardware or software functionality failure, unresolved errors, card reader issues, power issues, and port issues'; physical damage and out-of-warranty devices are replaced at full price. The replacement ships first and the faulty unit is returned 'within 30 days' using a prepaid shipping label included in the replacement box. Note this is a shipping turnaround, not a contractual uptime SLA with remedies. https://support.toasttab.com/en/article/Replacing-Faulty-Hardware-RMA · retrieved 2026-08-08

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

Toast states it is a PCI-DSS-compliant Level 1 Service Provider assessed by a QSA and provides PCI Responsibility Guides through Customer Care. A published v4.0/4.0.1 AOC covering post-March-2025 future-dated requirements was not located. https://support.toasttab.com/en/article/What-is-PCI-Compliance · retrieved 2026-08-01

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

reliability-mfa-role-based-access

Role-based permissions are core to Toast Web and the POS. Enforceable MFA on back-office and POS administrative logins was not verified in documentation.

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

reliability-self-serve-training

Toast Central and support.toasttab.com are free, public, extensive training libraries; Toast also provides a POS training mode for staff onboarding. https://support.toasttab.com/en · retrieved 2026-08-01

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

reliability-failover-terminal-role

Toast automatically designates an eligible device — typically a hardwired stationary terminal — as the local hub, so hub election is automatic. But because terminals cannot share check state offline, this is relay failover, not full master-role failover. https://doc.toasttab.com/doc/platformguide/platformOfflineModeLocalSync.html · retrieved 2026-08-01

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

reliability-cellular-backup

Toast sells LTE-capable handhelds (a 'Wi-Fi Only' variant is explicitly distinguished) and supplies networking gear, but automatic cellular failover for terminals is not documented. https://pos.toasttab.com/shop/starter-kits/handheld-starter-kit · retrieved 2026-08-01

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

The $0 Starter Kit is marketed with no monthly subscription and no upfront cost. Paid tiers are consistently reported by operators as 1–3 year terms; Toast does not publish a month-to-month option for its core paid POS tier. https://pos.toasttab.com/pricing · retrieved 2026-08-01

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

Merchant Agreement section 8.4: Merchant 'may terminate this Agreement at any time following the Effective Date' but 'shall incur and pay (a) an early termination fee equal to either (i) the remaining Fees for Software Subscription Fees that would have otherwise been due for the remainder of the then-current Term, or ii) for a Pay-as-you-go subscription, one-hundred and fifty dollars ($150.00) multiplied by the number of months remaining in the then-current Term, as applicable ("Early Termination Fee"), and (b) any applicable processing fee related to Software financing.' Section 6.1 adds that 'All Fees are non-cancelable and non-refundable'. There is exactly one carve-out: under section 6.2 a merchant terminating because Toast raised card processing rates or the core POS tablet subscription fee is exempt from the Early Termination Fee, other than the software-financing processing fee. https://pos.toasttab.com/merchant-agreement · retrieved 2026-08-08

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

Merchant Agreement section 8.1: after the Initial Term 'the term of this Agreement with respect to such applicable Order(s) shall automatically renew for successive one (1) year periods (each a "Renewal Term")', and 'either party may terminate an Order, and this Agreement with respect to such Order, by providing at least thirty (30) days' written notice of its intent not to renew prior to the end of the then-current Term.' Section 8.1 also warns that each Renewal Term is governed by the then-current version of the Merchant Agreement and that promotional terms lapse at renewal. The one figure that remains order-form-only is the length of the Initial Term itself, which section 8.1 defers to 'the initial term outlined in the Order' - but the claim asks for the auto-renewal term and the notice window, and both are published. https://pos.toasttab.com/merchant-agreement · retrieved 2026-08-08

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

Same correction: now vendor-documented exclusivity, not operator inference. https://pos.toasttab.com/payment-processing-terms · retrieved 2026-08-01 adversarially verified

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

Upheld, and both halves of the prior rationale are corrected. FIRST, THE PAGE IS READABLE AGAIN: a prior pass recorded pos.toasttab.com/pricing as HTTP 403 on 2026-08-08 and treated Toast's pricing as unreachable; it answered 200 at 656,369 bytes on 2026-09-09, which is the standing rule that a refusal is not a deletion. SECOND, "Toast publishes blended flat rates only" is FALSE as of that read -- the live page publishes NO card rate whatsoever. Across its 9,852 stripped characters `interchange` occurs zero times, `per transaction` zero, `processing rate` zero, and the only percentage is "0% interest financing"; the 33 decimal percentages in the raw HTML are every one of them a CSS gradient stop, which is exactly the trap a stripped-text count avoids. The page instead says "Toast is not a payment card processor, but it is a payment facilitator that partners with processors to offer card processing services" and sends everything else to a quote ("The upfront costs for Toast are hardware and implementation, which vary depending on your specific hardware packages and installation needs"). AND INTERCHANGE-PLUS DEMONSTRABLY EXISTS AS A TOAST PRODUCT -- support.toasttab.com/en/article/Toast-Interchange-Plus-Reporting redirects into idm.toasttab.com rather than 404ing, while a fabricated article slug on the same host hard-404s at 575,106 bytes, so the article is real and login-gated. What is unpublished is the markup, not the option. Grade C: a vendor pricing page. https://pos.toasttab.com/pricing · retrieved 2026-09-09

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

No cap, but a real exit right. Section 6.2: software fees 'will remain unchanged during the Initial Term', while 'Toast reserves the right to change (i) Card processing rates and other non-Software Fees at any time during the Term upon thirty (30) days' prior written notice' and '(ii) any Fees at the beginning of, or at any time during, a Renewal Term upon thirty (30) days' prior written notice'. Nothing limits increases to pass-through interchange or network changes. The merchant's remedy is split: for 'a change in Card processing rates or in the Fee for Toast's monthly POS core tablet subscription' the merchant may 'elect to terminate this Agreement', and 'the Early Termination Fee under Section 8.4 shall not apply (other than the processing fee for Software financing)'; for a non-software fee increase or an increase on any other software subscription module the remedy is only to remove that product or module. Shortfalls: the penalty-free exit does not extend to every increase, silence is deemed acceptance, and 'any amounts prepaid by Merchant as of the date of such removal or termination shall be non-refundable.' https://pos.toasttab.com/merchant-agreement · retrieved 2026-08-08

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

Partial is right for the wrong reason. Toast does name plans and a $0 entry point publicly, but the pricing page is not machine-retrievable, per-terminal pricing is quote-based, and processing rate is custom-quoted per merchant. Do not let this read as 'Toast publishes its rates'. https://pos.toasttab.com/pricing · retrieved 2026-08-01 adversarially verified

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

Modules are sold per-Order and can be dropped, but not cleanly. Section 6.2 grants an unconditional removal right in one situation only: where Toast raises the fee on 'any Software subscription module (other than Toast's monthly POS core tablet subscription)', the merchant may give written notice that it 'has elected to remove such applicable non-Software product or service or the Software subscription module that is subject to the Fee change' - and Toast's repricing right is carved out for that case. Otherwise: 'in the event that Toast permits Merchant to modify an Order to remove a product, service or module at any time during the Term (other than in connection with a price increase by Toast as set forth in the immediately foregoing paragraph), Toast shall have the right to update pricing across the Merchant's remaining products, services or modules.' So mid-term removal is discretionary on Toast's side and does trigger repricing of the rest, and section 6.1 makes all fees 'non-cancelable and non-refundable' with prepaid amounts non-refundable on removal. The pricing page (retrieved 2026-08-08, last updated 8 July 2026) markets packages plus add-ons but publishes no per-module cancellation terms. https://pos.toasttab.com/merchant-agreement · retrieved 2026-08-08

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

Outright purchase is offered alongside no-upfront-cost and pay-as-you-go platform-rate options, so no lease is mandatory. But published per-SKU prices are limited to starter kits. https://support.toasttab.com/en/article/How-customers-can-pay-for-Toast-Starter-Kits-Internal · retrieved 2026-08-01

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

Toast's own Compatible Printers article lists non-proprietary Epson models alongside Toast-branded units: Epson TM-T20 II, TM-U220B, TM-M30, TM-T88V, TM-L90 and L100. The Hardware Hub additionally names Elo terminals and guest/kitchen displays, Zebra (DS2208, DS9308, DS2278) and Honeywell (MK7580, 1472G) scanners, a Brecknell 6710U scale and Meraki routers, and links out with "Don't have a Toast printer? See what other printers are compatible with Toast." The claim asks only whether at least one non-proprietary hardware option is documented; it plainly is. Separately note the terminal itself is a different question, scored under hardware-commodity-devices. https://support.toasttab.com/en/article/Toast-Compatible-Printers · retrieved 2026-08-02 adversarially verified

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

CSV report export exists in Toast Web, and programmatic export exists via Standard/Analytics API access — but the API route is GET-only and requires an RMS Essentials+ subscription for every location, so full self-serve export is plan-conditional. https://doc.toasttab.com/doc/devguide/devApiAccessFAQs.html · retrieved 2026-08-01

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

Two of three ledgers export cleanly. Guests: 'To export the current view of Guestbook (after any filters and segments you have applied), select Download list'; Toast emails a unique download URL and the file is a CSV carrying contact information, order date, number of orders, average spend per check, order source, dining option, loyalty status, house account status, marketing preference, guest tags, booking counts and guest feedback. Gift cards: the Gift Card Balances report 'lists every active gift card account and its current balance' with a download icon producing a .csv, and the Gift Card Liabilities report is delivered by 'Email Export' as an Excel attachment where 'the Ending Liability value displayed is your total outstanding gift card liability as of that date'. Shortfall: loyalty. Guestbook exports 'Loyalty status' but not the balance - loyalty balance and rewards are visible only inside the guest profile via the Loyalty Module, which directs 'To add or adjust points or rewards, use the Loyalty platform', and no documented CSV/report exports a per-guest loyalty point balance or point ledger. https://support.toasttab.com/en/article/Access-Your-Guest-Data-with-the-Guest-Report · retrieved 2026-08-08

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

Merchant Agreement section 8.5: 'at Merchant's request if received within thirty (30) days of termination of the Order or Agreement for any reason other than termination by Toast for Merchant's uncured material breach, to the extent Merchant is otherwise unable to access the information itself, Toast will permit Merchant to access the Services solely and exclusively to the extent necessary for Merchant to retrieve a copy of Merchant Data, Customer Data, and any other data, materials, and information collected by the Merchant as part of the Services and contained in Merchant's Toast Account.' The same section fixes the outer bound: 'Toast has no obligation to retain Merchant Data and ... will have the right to irretrievably delete and destroy Merchant Data after thirty (30) days following the termination of this Agreement.' Two conditions worth recording: the window is void if Toast terminated for the merchant's uncured material breach, and it is request-based rather than automatic. Section 5.2 separately confirms 'Merchant owns all Merchant Data.' https://pos.toasttab.com/merchant-agreement · retrieved 2026-08-08

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

Toast publishes a Merchant Data Processing Addendum, which is more than most competitors offer publicly. Whether it affirmatively states merchant ownership and constrains Toast's own product/marketing use of that data beyond aggregated de-identified use was not verified. https://pos.toasttab.com/privacy/merchantdpa · retrieved 2026-08-01

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

Toast says it assumes most PCI requirements, all payment devices meet or exceed PCI requirements, and most customers need not submit an SAQ or AOC at all — but it does not name the applicable merchant SAQ type or cite a validated P2PE listing. https://support.toasttab.com/en/article/What-is-PCI-Compliance · retrieved 2026-08-01

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

MFA exists but does not reach the coverage the claim describes. The support article: 'Multi-factor authentication (MFA) ... adds an extra layer of security to your Toast Web login', by authenticator app or SMS one-time code; 'MFA is required for users with 8.1 Financial Accounts or 8.7 Instant Deposits permissions, and for HR+ Toast Payroll users'; and decisively, 'MFA does not apply when you log in on a Toast POS device.' The platform guide adds that other users may enrol voluntarily - 'ideally, anyone with access to critical systems or operations should enrol' - and documents no admin switch to require MFA org-wide. On the standard itself, Toast's PCI Compliance Overview says only that Toast 'obtained independent validation of its payment software' and 'completed independent third-party assessments of our payments ecosystem'; it names no PCI DSS version, does not mention the 31 March 2025 future-dated requirements, and says nothing about payment-page script inventory or integrity monitoring under Req 6.4.3 / 11.6.1. Note the merchant-facing framing: Merchant Agreement section 4.1(f) and the Definitions section push PCI-DSS compliance onto the merchant and point to pcisecuritystandards.org rather than stating Toast's own control posture. https://support.toasttab.com/en/article/Setting-Up-Multi-Factor-Authentication · retrieved 2026-08-08

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

Toast publishes privacy-compliance guidance for operators and an executable Merchant DPA. Dedicated in-app DSAR tooling to locate, export and delete an individual guest's records across loyalty and marketing is not documented. https://support.toasttab.com/en/article/Managing-Your-Privacy-Compliance-Obligations · retrieved 2026-08-01

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

CLAIM: vendor publishes a VPAT/ACR claiming WCAG 2.1 AA for kiosk and web ordering, including a documented tactile/audio non-visual access mode on kiosks. VERDICT: unknown -> partial/B. The non-visual kiosk conjunct is now documented first-party; the conformance-report conjunct is not met. EVIDENCE (met): support.toasttab.com/en/article/Set-Up-the-STORM-Accessibility-Device-for-Toast-Kiosk (Last updated Jun 25, 2026; HTTP 200): "The STORM Audio-Nav device is an accessible keypad with a headphone jack that enables blind and low vision guests to navigate the Toast Kiosk screen while listening to the JAWS screen reader." "Toast pre-installs JAWS on your device, so no separate installation is required." "Kiosk Accessibility features only work in Kiosk mode." It also concedes "Some elements, such as unlabeled graphics, may not be read or interacted with effectively." Release note updates.toasttab.com/announcements/toast-kiosk-supports-accessibility-features-including-a-screen-reader-and-external-keypad-integration (July 22, 2026, POS v2.112, CPPL-116): "Guests can use JAWS screen reader support or connect the STORM Audio Nav, a third-party external device with a headphone jack and directional keypad". EVIDENCE (not met): the Toast Trust Center - the vendor's on-request document portal, exactly where an ACR would sit - enumerates its whole document list in the anonymous site-data JSON: PCI DSS AOC for Service Providers, Capital SOC 2 Type II, Core & POS SOC 2 Type II, Capital SOC 1 Type II, Payroll SOC 1 Type II, Core & POS SOC 1 Type II, PCI Responsibility Matrix, QSA Guide for Merchants, Information Security Policy Overview. No VPAT/ACR/accessibility item. Tokenised controls vpat / wcag / acr / "accessibility conformance": 0 in the trust-center JSON, 0 in 423 updates announcements, 0 in 80 guesthelp docs, 0 in the STORM article. pos.toasttab.com/accessibility 404 (the /accessibility-statement and /legal/accessibility probes returned a Cloudflare 403 refusal, not an absence). Consistent with the atlas precedent that a documented tactile/audio kiosk mode without an ACR is partial (otter, square). NOTE: the support.toasttab.com sitemap (805 URLs today) does NOT list the STORM article although it serves 200 - that sitemap is not a census, so any older zero bound to it is weak. NEW SURFACES (found via crt.sh listing of %.toasttab.com, 346 unique hostnames): (a) guesthelp.toasttab.com, the Toast Local guest Intercom help centre - sitemap 93 URLs, all 72 /en/ articles plus collection pages fetched (80 docs, census of that sitemap); (b) updates.toasttab.com, Toast product updates on LaunchNotes - sitemap 423 announcements, all 423 fetched at 200, publishedAt 2023-09-02 to 2026-09-14 (census of that sitemap); (c) trustcenter.toasttab.com, the Toast Trust Center (anonymous site-data JSON the page itself loads: dvqneza7fx.us-west-2.awsapprunner.com/api/v1/tc/trustcenter.toasttab.com/site-data/), which enumerates 8 security_certificates + 1 security_report. Retrieved 2026-09-16. https://support.toasttab.com/en/article/Set-Up-the-STORM-Accessibility-Device-for-Toast-Kiosk · retrieved 2026-09-16 adversarially verified

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

Toast Credit Card Surcharging identifies debit and prepaid by BIN and excludes them automatically, caps at the 3% card-brand maximum, excludes tips and taxes, is gated to eligible US states with state-specific guidance (e.g. New York), and documents the required point-of-entry and point-of-sale disclosure wording. https://support.toasttab.com/en/article/Credit-Card-Surcharging-FAQ · retrieved 2026-08-01