TouchBistro

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

"Add and remove tables, walls, sections, and dining rooms with just a few clicks"; changes sync automatically. Multiple dining rooms implied; per-server section assignment listed in POS tier. https://www.touchbistro.com/features/floor-plan-table-management/ · retrieved 2026-08-01

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

Items are assigned to seats on the Order Input screen (Seat Options menu; "Order a Menu Item to a Seat"; "Split a Menu Item Between Seats"; "Move a Menu Item to Another Seat"). At checkout the existing seat tags drive the split with no re-entry: "Tap Split By Seating (allows guests to pay for the items they ordered at their seat as well as any items shared with the table)." Shared items are handled explicitly, and "if you split items between two or more seats, TouchBistro will force a split by seats on Checkout". Not available on Cash Register or takeout/delivery/bar tab orders. https://help.touchbistro.com/s/article/checkout?language=en_US · retrieved 2026-08-08 adversarially verified

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

"How to Course Your Items": from the Order Screen tap the Course icon, then "To send just drinks, tap Send Drinks. To send all items for a single course, tap Send" and "Tap a course (e.g., Course 1)" - so only that course is released. Under "Fire/Hold Orders": "Tap Fire to tell the kitchen to fire a selected course. Or tap an individual menu item to fire it. Alternatively, tap Hold if you need to tell the kitchen to hold preparing a certain item." Course assignment is a Menu Group setting inherited by items, overridable per item via Default Course (Menu Management: Menu Items). TouchBistro POS runs on iPad terminals and tableside iPads, so the action is available from both. https://help.touchbistro.com/s/article/sending-drinks-and-courses-at-separate-times · retrieved 2026-08-06

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

Two split modes are offered at checkout: "Tap Split By Seating" and "Tap Split Evenly By #"; items can be divided across seats from the Order screen via Split Item Among Seats, and seats can be recombined (Combine Multiple Seats to Create Combined Guest Checks; Split Seats That Are Currently Combined). Shortfall, and the guide states it as a limit rather than leaving it unfound: there is no arbitrary dollar or percentage split, and "you cannot split... a bill that has a partial payment". After a partial payment on a split bill you also "cannot remove the split" or "return to the Order screen and perform any function found there (add discounts, void items, add seats, and so on)", and you cannot "merge a bar tab into a bar tab with a split" or transfer a split bar tab to a table. https://help.touchbistro.com/s/article/checkout?language=en_US · retrieved 2026-08-08 adversarially 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

Bar tabs are opened against a card via Admin Settings | Payment Gateways | "Create/Open Bar Tabs by Swiping Card" plus a per-gateway "Save card for payment when opening bar tabs" option; the tab captures the cardholder name and last four digits and the auth follows the tab if it is transferred to a table. Shortfalls, all stated by the vendor: the auth amount is not configurable - it is a zero auth, and "to ensure the card is valid, Zero Auth will run a temporary $1 pre-auth transaction"; "a zero auth does not check if the cardholder has enough remaining credit limit to pay for the accrued tab. The charge may still be rejected at checkout"; no incremental re-authorization as the tab grows is documented anywhere in the help centre; no end-of-day stale-tab auto-close is documented; and the feature cannot be used with American Express, cannot be started from the cash register or a table, and cannot be used with store-and-forward. https://help.touchbistro.com/s/article/How-to-Perform-Zero-Auth-Bar-Tab-Transactions-with-TSYS · retrieved 2026-08-06

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

Table transfer documented ("Diners can switch tables without... losing their bill information") and "Manager activity tracking" exists; an audit entry naming both employees is not documented. https://www.touchbistro.com/features/floor-plan-table-management/ · retrieved 2026-08-01

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

"Download and install TouchBistro POS to each satellite iPad to connect them to your system" - each handheld runs the app locally and connects to the Main Device over the venue's own network (default port 1337, or manual IP entry), which is a first-party native app rather than a mirrored or remote session. Items ordered on it route to kitchen Prep Stations selected per menu item. Card payment is taken at the table on the same device with a paired reader: on the Checkout screen "tap Credit/Debit Card... TouchBistro will prompt the diner to tap, dip, or swipe the card", then "you will be prompted to pass the iPad to the diner" for tip and on-screen signature. https://help.touchbistro.com/s/article/Part-2-How-to-Connect-iPads-to-your-Main-Device?language=en_US · retrieved 2026-08-08 adversarially verified

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

Built-in offline mode: devices keep communicating over LAN so orders and payments continue; vendor states reports become unavailable until reconnect. Full degradation matrix not verified. https://www.touchbistro.com/blog/what-is-a-hybrid-pos/ · 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

No guest-facing QR ordering exists, so nothing can write onto an open check. The word is present and was measured: QR occurs in 51 product documents, and in the current 861-article KB every occurrence is device linking, staff passcode login by QR, or a payment-terminal setting — on the Moneris Go terminals the receipt option "Print QR Code" is documented as "This is currently not supported. Leave as Disable ." The only guest ordering product in the suite is Online Ordering, whose 2026 Product Guide feature list is takeout and delivery through the restaurant website, social channels and TouchBistro Dine; there is no at-table or scan-to-order entry in it. In-venue order capture is server-entered on the POS: the takeout-type article shows a "Drive Thru" style label is a free-text Takeout Type a manager creates, not a guest channel. `scan to order` occurs zero times. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. https://help.touchbistro.com/s/article/takeout-types?language=en_US · retrieved 2026-09-10

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

Upheld, and now affirmatively evidenced rather than inferred: /self-ordering-kiosk/ returns 404 and the features catalog enumerates 18 products with no kiosk. Discovered a wrinkle the dossier missed — a first-party "TouchBistro Kiosk" iPad app is still listed on the App Store under TouchBistro Inc., last updated version 1.5.0 on 11 Sept 2019 with no Apple privacy disclosures. That is an abandoned legacy SKU, not a shipping product, so "no" holds. https://apps.apple.com/us/app/touchbistro-kiosk/id1076400071 · retrieved 2026-08-01 adversarially verified

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

Positive evidence of absence from vendor documentation, not from the marketing catalogue. The KDS guide, listing the order types a ticket can be re-typed to, says: "Options include order types TouchBistro doesn't itself generate like Drive Thru or Curb Side." The only drive-thru construct TouchBistro documents is a user-created Takeout Type: "Enter a Name (e.g., Drive Thru)" used to "categorize sales and voids" in reports and to print a header on kitchen tickets, and the server guide states a custom takeout type "is functionally the same as a Takeout order, except the custom takeout order name is printed on the kitchen ticket." No order-point/pay-window/pickup-window separation, no lane assignment or order sequencing, and no pull-forward or parking-spot assignment exists anywhere in the help centre. https://help.touchbistro.com/s/article/Using-TouchBistro-KDS-Powered-by-Fresh?language=en_US · retrieved 2026-08-06 adversarially verified

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

order-capture-drive-thru-timers

"Drive Thru" is documented only as an example of a custom Takeout Type - a free-text label created under Admin Settings | Menu | Takeout Types that "will be used in reports to categorize sales and voids" and can be printed as a kitchen-ticket header (takeout-types). The KDS article likewise treats Drive Thru as a ticket Order Type label for "order types TouchBistro doesn't itself generate". The Index of Cloud Reports enumerates every data cell in every Cloud report; the only timing fields it lists are Sent Time and Paid Time (Sales | Detailed Sales), Avg. Table Turn Time (mins) by Server (Labor | Staff Performance) and Service Time (Labor | Hourly Labor Cost). There is no order/total/window timer, no speed-of-service segment, and no drive-thru report. The Takeout Types Report carries only orders, sales, tax and total per type. https://help.touchbistro.com/s/article/Index-of-Cloud-Reports · retrieved 2026-08-06

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

Neither disjunct holds. No first-party voice ordering agent appears in the 2026 Product Guide's suite enumeration, and `voice AI` and `AI voice` occur zero times corpus-wide (the `voice ordering` hits are TouchBistro's own survey of what restaurants generally deploy). Nor is there a documented API partner program for third-party voice AI: developer.touchbistro.com, developers.touchbistro.com, api.touchbistro.com and docs.touchbistro.com all answer NXDOMAIN to a DNS query (measured, not inferred from a connection failure), and no API reference exists anywhere in the corpus. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Controls as measured over the cited PDF by all three instruments: voice AI 0 tokenised in -layout, 0 tokenised in no-flags, 0 squashed; AI voice 0/0/0; voice ordering 0/0/0. POISON PUBLISHED so this is not re-audited: the bare control voice reads 0 tokenised but 6 squashed, and all 6 are the word invoice or invoices inside the Profit Management invoice-processing copy. The bare control AI reads 0 tokenised but 70 squashed, every one a substring of an ordinary word such as available, email, detail and main. A squashed figure for either term alone would be pure noise. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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

Throttling exists for TouchBistro Online Ordering: "If the potential ASAP order exceeds your maximum in the 15 minute window ... the diner will be immediately warned your venue is at capacity and offered a chance to schedule the order at the first available time", and for scheduled orders "the throttled time will not be shown" in the slot picker. Slots are fixed 15 minutes apart and bounded by Pickup Wait / Delivery Wait and Schedule Days in Advance settings. Shortfalls: the cap is a venue-wide order maximum per 15-minute window, not a per-channel capacity limit - DoorDash Marketplace orders are governed separately by DoorDash's own Pause Orders control and the Order Manager's manual 5-minute pickup-time adjustment (DoorDash-Understanding-the-Server-Experience), not by this maximum; and the response to exceeding capacity is to hide or block the slot and offer the next available one, not to automatically extend the quoted prep time; no kitchen-load threshold input is documented. https://help.touchbistro.com/s/article/touchbistro-online-ordering-diner-experience · retrieved 2026-08-06

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

Guests can "schedule pick up for a time that is convenient for them." Per-channel lead times and computed fire-time injection into the make queue are not documented. https://www.touchbistro.com/online-ordering/ · 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

Deposits: "Tap Options | Customer Account List. Tap the account. Tap Add Deposit and select the payment method", and "TouchBistro will not report the deposit as a sale, it will report as a deposit on the account reports". Balance due: on the day of pickup the order is closed with Pay on Account and "the $100 deposit is applied and the Account History screen reports the outstanding balance"; Accounts Report and Detailed Account Report can be added to the End of Day template. Shortfalls: there is no catering order type or catering module - the quote step is an explicit workaround ("create a quote ... From your floor plan tap Orders. Tap the Delivery or Takeout tab ... Under Receipt Options, tap Print and give a copy to the customer. Tap Back ... Tap More | Delete Order", with the note "We don't recommend keeping the order open or you will have to ignore it every time you perform an end of day"); on the pickup day the order must be re-keyed from scratch; and there is no delivery/event schedule separate from the standard Takeout/Delivery queue. Accounts also do not support integrated payments on TouchBistro Payments - Ingenico (Moby 8500). https://help.touchbistro.com/s/article/creating-closing-account · retrieved 2026-08-06

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

Positive evidence of a competing mechanism plus a stated messaging limitation. Courier timing is set by DoorDash, never by POS or KDS state. Drive: "This is the estimated amount of time it will take for the order to be prepared. DoorDash Drive won't dispatch a Dasher until the food prep time has elapsed" -- a static configured constant -- and "An alert for a driver will not go out until you accept the order", i.e. keyed to acceptance, not readiness (https://help.touchbistro.com/s/article/Getting-Started-With-DoorDash-Drive). Marketplace: "DoorDash has an algorithm that calculates prep time and delivery time and will fire the scheduled order the day of pickup based on its own calculated lead time" (https://help.touchbistro.com/s/article/DoorDash-Marketplace-Understanding-the-Server-Experience). TouchBistro states outright that it cannot push order state to the courier side: "TouchBistro will not issue a cancel message to the driver's DoorDash app" (https://help.touchbistro.com/s/article/How-to-Use-DoorDash-Drive) -- a cancel being a more basic event than a ready. The integration guide enumerates everything TouchBistro pushes up to the DoorDash store and it is menu data only: "Out of Stock / Back in Stock (86'ing); Adding, Updating or Deleting a Menu, Menu Group or Menu Item; Adding, Updating or Deleting Menu Images; Adding the status of Alcohol to an Item". The only readiness lever documented anywhere is manual and lives inside DoorDash's own webview -- Order Manager's "four key features" are enumerated a-d (adjust pickup time in 5-minute intervals, order summary, call the diner, track/call the dasher) -- and the POS lifecycle ends with a tablet tap after the fact: "Tap the order and then tap Complete when the order is picked up by the driver or diner" (https://help.touchbistro.com/s/article/DoorDash-Understanding-the-Server-Experience). For marketplaces reached through the aggregator route, TouchBistro says the third-party tablet must be kept to manage order state: "You still need to keep and use your third-party online ordering platform tablets ... You will need the third-party tablet to manage issues (e.g., order cancelation)" (https://help.touchbistro.com/s/article/what-is-an-online-ordering-aggregator). https://help.touchbistro.com/s/article/doordash-Integrating · retrieved 2026-08-06 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

Admin | Admin Settings | Menu | Void Reasons builds a named reason list (each with Is Taxable and Returns Inventory flags). Security settings gate the actions: Manager Passcode Settings offers Void Items ("a manager confirmation screen will appear if a server tries to void a sent menu item"), Delete Items and Discount Items. The exception reports exist and name the approver: Sales | Void Detail Reports carries Void Reason, Void Amount, Void Quantity, Server name and Authorized By; Sales | Discount Details Report carries Discount Reason and Authorized By; Void Summary adds Void % of Sales. https://help.touchbistro.com/s/article/void-reasons?language=en_US · retrieved 2026-08-08 adversarially verified

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

Min/max and forced selection are per group and independent: "Minimum Modifiers - If left blank or set to 0, this is an optional modifier. If set to 1 or higher, TouchBistro POS will automatically prompt the server ... On Online Ordering it will require the diner to select the minimum number of items before the diner can add it to his/her cart"; "Maximum Modifiers - ... it will prevent the server or diner from adding more items than permissible"; and each modifier carries a Mandatory flag that auto-adds it and does not count against the maximum. The POS-side article (setting-item-modification) publishes the full min/max behaviour matrix. Shortfalls: nesting is not a native depth setting - it is an emergent effect of using menu items as modifiers, "If you used some menu items as a modifier and those menu items have modifiers, TouchBistro will nest them on the POS", and the only documented example is two levels deep (Burger combo -> Caesar Salad side -> chicken/no chicken); three-level depth is nowhere documented. The vendor also warns "If you plan to use online ordering, we do not recommend creating these kinds of nested modifiers as online ordering systems (DoorDash and TouchBistro Online Ordering) cannot work with nested modifiers." https://help.touchbistro.com/s/article/Menu-Management-Modifier-Groups · retrieved 2026-08-06

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

TouchBistro documents the entire modifier configuration surface twice. In Cloud (Menu Management: Modifier Groups) a Modifier Group has exactly these fields - Modifier Group Name, Minimum Modifiers, Maximum Modifiers, Icon, Available For, Assign to - and each modifier added to it carries a single upcharge Price plus a Mandatory flag and a sort position. In the POS (How Do I Set Up Item Modifiers in the POS-based Platform?) the same surface is Name, Minimum/Maximum Modifier Selection, Icon, then per modifier a Name, one Price and Mandatory. There is no parent-item dimension and no size dimension on a modifier price. The group is applied to many parents at once via "Assign to" / "Assign to Menu Items", which necessarily shares one price across every parent, and the documented way to get a different price is to build or duplicate another Modifier Group ("If you would like to use an existing Modifier Group as the basis for a new one ... click Duplicate"). No price matrix exists. https://help.touchbistro.com/s/article/Menu-Management-Modifier-Groups · retrieved 2026-08-06

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

menu-pricing-fractional-placement

The complete modifier configuration surface is published for both platforms - POS (Admin Settings | Menu | Item Modifications: group Name, Minimum/Maximum Modifier Selection, Icon; per modifier Name, Price, Mandatory, sort order) and Cloud (Menu Management | Modifier Groups: Name, Minimum Modifiers, Maximum Modifiers, Icon, Available For, Assign to; per modifier one upcharge Price, Mandatory, sort). Neither has any placement, section, half or quarter attribute, and no price-per-section concept exists. The nearest documented feature is unrelated: "How Do I Handle Half and Split Orders?" covers half portions of a whole dish, implemented by setting the order item Quantity to .5 and adding a separately created "Half Portion Up Charge" menu item, or by a "Half portion" text modifier whose upcharge is split across seats. Searching all 765 help articles returns no half-and-half, left/right or quarter topping placement of any kind. https://help.touchbistro.com/s/article/setting-item-modification · retrieved 2026-08-06

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

An operator-configurable half-and-half pricing rule requires a half/section construct to price, and TouchBistro has none - the complete modifier group configuration (Cloud: Name, Minimum Modifiers, Maximum Modifiers, Icon, Available For, Assign to; per modifier a single Price and Mandatory) and the complete Add Menu Item form (Menu Management: Menu Items) contain no placement attribute and no pricing-rule selector such as higher-half, average-the-halves or fractional-topping. Menu item pricing is a single before-tax Price field plus an Open Price checkbox. Nothing in the 765-article help centre describes pizza-style half pricing; the only documented halving is a half-portion quantity of a whole dish with a manually created upcharge item. https://help.touchbistro.com/s/article/Menu-Management-Modifier-Groups · retrieved 2026-08-06

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

menu-pricing-topping-quantity-tiers

The POS modifier configuration screen is enumerated in full: "Tap Add Text Modifier. Enter a Name. Enter a Price if the modification comes with an additional cost ... Turn-on Mandatory If the modifier is required", and identically for Add Menu Modifier. The Cloud equivalent (Menu Management: Modifier Groups) adds only Create from Existing Menu Item / Create a Kitchen Instruction, an upcharge Price and Mandatory. Neither carries a quantity tier (light/regular/extra/double) or a per-tier price multiplier. The documented way to express intensity is a separate text modifier per level (the vendor's own examples are "rare, medium, and well done", "Well Done", "No ice"), each with its own flat Price - not a multiplier on the modifier's base price. Order-item Quantity exists on the Order screen (used for .5 half portions) but is documented against the order item, not against a modifier. https://help.touchbistro.com/s/article/setting-item-modification · retrieved 2026-08-06

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

Menu Management: Menu Items enumerates the entire Add Menu Item form - Name, Short Name, Description, gift-card flag, contains-alcohol flag, Requires manager approval, This item can be returned, Background Color, Default Course, Available For, Menu Item Images, Price, Open Price, Taxes, Total cost of ingredients, Item out of stock, UPC Code, Menu Group, Sales Category, Modifier Group, Prep Stations, plus Custom Hours scheduling. Pricing is one field: "Price - Enter the Menu Item before-tax price", with "Open Price - Check this if you want the price to be entered at the time it is ordered." There is no size axis, no preparation/crust axis, no variant table and no per-cell override; bulk price editing is a one-off dollar or percentage change across selected items, not a grid. Sizes and styles must be modelled either as separate menu items or as modifiers carrying flat upcharges. https://help.touchbistro.com/s/article/Menu-Management-How-to-Add-Menu-Items · retrieved 2026-08-06

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

The Modifier Group form is enumerated in full - Modifier Group Name, Minimum Modifiers, Maximum Modifiers, Icon, Available For, Assign to - with no included-allowance, free-count or overage field, and the POS equivalent (Item Modifications) is the same. Maximum Modifiers is a hard cap, not an overage trigger: "If set to 1 or greater, it will prevent the server or diner from adding more items than permissible", and on the Order screen "Further selections will grey out upon reaching the maximum." The vendor's documented way to model included options is manual per-modifier zero pricing: "If the Menu Item has a price ... the displayed price will be added as an upcharge. You can set it to zero if the original menu item already has the selection built into the price ... Premium modifiers can then be set for an upcharge price." There is no substitution credit and no configurable forbid-substitution behaviour. https://help.touchbistro.com/s/article/Menu-Management-Modifier-Groups · retrieved 2026-08-06

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 construction with swap deltas is documented: create the combo as a menu item where "For Price, put the FULL end price of the combo with all additions", then attach a Modifier Group of menu-item modifiers as the component choices. Swap price deltas are the modifier upcharges - "a burger combo comes with a free side for $18 but if the diner wants a premium side like sweet potato fries you can set an upcharge like $1. Setting a new price here will not change the menu item's price when ordered a la carte" (Menu Management: Modifier Groups). Shortfalls: there is no combo object in TouchBistro - a combo is a hand-built menu item plus modifier group, so every combo and every price must be maintained by hand; and nothing in the help centre describes automatic detection or conversion of eligible a-la-carte items already in the cart into the combo price. The server must select the combo item explicitly. https://help.touchbistro.com/s/article/calculating-ontario-tax-reduction-combo-meals · retrieved 2026-08-06

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

The prompt is configured on the Modifier Group and assigned to specific menu items: "Minimum Modifiers - if set to 1 or higher, TouchBistro POS will automatically prompt the server to ask the diner for the minimum number of preferred modifier item or items. On Online Ordering it will require the diner to select the minimum number of items before the diner can add it to his/her cart." Channel is selectable per group ("Available For - set if this Modifier Group available at the POS and/or for Online Ordering"), and premium modifiers carry upcharges. Promotions add a second, weaker prompt: a qualifying item shows "a % icon associated with it, giving the server a heads up... Alert staff to look for these icons so they can help upsell". Shortfall: there is no upsell-prompt field on the menu item itself (the Menu Items field list is exhaustive and has none), kiosk is not a selectable channel, and reporting is modifier preference (Menu | Modifier Preference by Menu Item: Modifier, Modifier Type, Quantity Sold, Menu Item (Parent)) rather than an attach rate on prompts. https://help.touchbistro.com/s/article/Menu-Management-Modifier-Groups?language=en_US · retrieved 2026-08-08 adversarially 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

A single availability change propagates without a publish step: "changes to stock counts and availability do not have to be published. They are pushed to the venue immediately." Downstream: the POS Order screen shows out-of-stock and low-stock items; "TouchBistro Online Ordering will mark menu items that are out of stock as unavailable"; "DoorDash Online Ordering will hide menu items that are out of stock". Shortfall: no propagation latency is published beyond "immediately"; KDS is not addressed; enforcement on the third-party channel is incomplete - "DoorDash Online Ordering will not block a diner from ordering more items than are in inventory", and an item going out of stock while an order sits in Pending forces the server to decline the whole order or accept it with a manager override, since "there is no way for the server or manager to edit the order and remove the out-of-stock item". Other marketplaces reach TouchBistro through Deliverect or UrbanPiper rather than natively. https://help.touchbistro.com/s/article/Menu-Management-Stock-Availability?language=en_US · retrieved 2026-08-08 adversarially verified

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

"Stock Availability is a simplified inventory system for countable menu items ... As orders with the items are fulfilled, the stock count decreases" (POS 11.47.0+). Counts are per menu item and per menu-item modifier, with an optional "Low Stock Indicator" threshold that surfaces the remaining count on the Order screen. Decrement rule is documented: "Adding an item to the order screen does not decrease the stock count. Sending the item to the kitchen does decrease the stock count", and voids restore the count if set to return to inventory. Auto-86 at zero is explicit: "The Out of Stock control is automatically enabled if stock count reaches zero", and the POS Order screen blocks the item pending a manager Override; the Advanced settings screen carries the equivalent POS-side toggle "Automatically Mark Items Out Of Stock". Shortfall: there is no scheduled auto-restore - stock must be replenished by hand via Manage Stock ("There is no bulk updating"), counts must be set per location, and there is no inventory report or CSV export of the stock page. https://help.touchbistro.com/s/article/Menu-Management-Stock-Availability · retrieved 2026-08-06

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

Menu level: "if you would like to only offer this menu some of the time, click Custom hours and set which days and times the menu is available... a breakfast menu is available Monday to Friday from 9 am to 11 am but 10 am to 1 pm on Saturday and Sunday", with multiple schedules per menu. Item level: the same Custom Hours control exists on the individual menu item - "available Monday to Saturday opening to closing hours; available Sunday 1 pm to closing hours" is the worked example. Price level: Menu Management | Promotional Pricing schedules a percentage/dollar discount or a fixed price against selected menu groups or items over chosen days and times ("a Happy Hour between 4 pm and 6 pm Monday to Thursday", with optional grace minutes either side). Schedules are configured per venue or per restaurant group against that location's opening hours; no timezone field is exposed, and scheduled promotions apply at the POS only - "they will not be applied if a diner is using your TouchBistro Online Ordering site". https://help.touchbistro.com/s/article/Menu-Management-Menus?language=en_US · retrieved 2026-08-08 adversarially verified

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

One markup rule exists and it is percentage-based: during DoorDash Marketplace setup "set up a price for the menu items for delivery through your DoorDash store ... after selecting a dollar or percentage increase", and "Orders placed for pickup through DoorDash will be priced based on what you've already set for your Online Ordering menu(s). You can increase the menu item's price by a dollar or a percentage. You can also leave it as 0 to keep the delivery and pick up the same." It is editable later from the DoorDash App page. Shortfalls: that is the only price book. A Menu Item has a single before-tax Price field (Menu Management: Menu Items) and a Menu's only channel control is "Available for - Select if this menu should be available for use on the POS and/or on your online ordering site" (Menu Management: Menus) - availability, not price. Dine-in, pickup and TouchBistro Online Ordering all share the one item price; there is no kiosk price book; the DoorDash uplift is a single venue-wide increase rather than per-item; and per-item divergence is only achievable by hand or by the one-off bulk price increase/decrease tool. https://help.touchbistro.com/s/article/doordash-Integrating · retrieved 2026-08-06

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

"How Do I Set Up a Cash discount?" documents the supported approach on both platforms: create a percentage Discount (POS: Admin Settings | Menu | Discounts; Cloud: Menu Management | Discounts) scoped to chosen Menu Groups/Items, on the premise that "your prices have a credit card fee built into them" so the card price is the base price. The Order and Checkout screens then display a Cash Total line alongside the Total, and "Tap Cash and the tender modal will display the Cash Total (and any penny rounding)". Shortfalls: it is not item-level dual pricing - the item carries one Price and the discount is applied to the bill; the vendor explicitly instructs "Do not apply the discount to individual items. Tap Checkout. Tap Discount/Comp All Items"; the discount is lost on a partial cash payment and is not restored by a second cash payment; and neither article states that the cash price is surfaced on the kiosk or on TouchBistro Online Ordering / DoorDash menus, which price from the same single item Price. https://help.touchbistro.com/s/article/cash-discounting · retrieved 2026-08-06

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

Inventory module provides "Automatic generation of allergen tags and nutritional information" derived from recipe data — which satisfies the derive-from-recipe half. Publication to online ordering and third-party menus is not documented, and this requires the paid Inventory add-on. https://www.touchbistro.com/inventory-management/ · retrieved 2026-08-01

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

Documented recipe-to-item linkage exists only in the legacy Ingredient-Based Inventory System: on a menu item you "Slide Recipe Cost to green to cost this menu item", then "tap Manage Recipe", "Select the appropriate inventory ingredient and Recipe Measure" and enter a quantity, with ingredient Purchase Measure, Cost Per Unit ($) and a Conversion Ratio to the Recipe Measure. Shortfall, stated by TouchBistro's own guide: it is "(POS-based platform users only)", "this functionality is no longer being actively developed, it is not available for all accounts", and for customers on the current Menu Management tool "TouchBistro does not support this inventory for such customers." In current Menu Management a menu item's food cost is a single manually keyed field — "Total cost of ingredients: Enter the item's food cost" (https://help.touchbistro.com/s/article/Menu-Management-How-to-Add-Menu-Items) — with no recipe or ingredient linkage. The separately-sold Inventory Management add-on is marketed as doing recipe-to-item costing, but no product documentation for it is publicly retrievable. https://help.touchbistro.com/s/article/setting-using-touchbistro-ingredient-based-inventory-system · retrieved 2026-08-02 adversarially verified

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

Reached through aggregator middleware (UrbanPiper, Deliverect) rather than vendor-owned certified direct connections, except DoorDash. Per-item sync status and rejection surfacing not documented. https://www.touchbistro.com/features/integrations/ · 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

Rule-based time-of-day pricing exists: Admin Settings | Menu | Promotional Pricing, where a promotion has a Price Adjust of Fixed Price, Discount by Percent or Discount by Amount, a Schedule setting "the days of the week and times of day the promotion will be active", and a Choose Items selection of Menu Groups/Items; a Hide Item mode can also suppress items on a schedule. Shortfalls: the axis is time only - no demand-driven or channel-driven rule is documented; there are no floor/ceiling guardrails, and the vendor warns of the failure mode instead, "If the discount exceeds the cost of the items, they will be priced at $0"; "Price promotions are not applied to menu items ordered via TouchBistro's Online Ordering"; and the feature is being retired - "as this functionality is no longer being actively developed, it is not available for all accounts." https://help.touchbistro.com/s/article/promotional-pricing · retrieved 2026-08-06

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

Help-centre article "What Payment Processor Integrations Does TouchBistro Support?" (updated 2026-03-03) enumerates integrated processors and their supported devices: USA - TB Payments (A800, A920Pro, Lane/3000, Link/2500), Chase USA (A800, A920Pro, Moby8500), TSYS (A800, A920Pro); Canada - Chase Merchant Services (DESK/5000, MOVE/5000), TD (DESK/5000, MOVE/5000), Moneris (DX 8000, A35). Worldpay triPOS is documented separately as a configurable gateway. The admin guide (payment-gateways) says to tap "the Payment Gateway you contracted with", then Setup, then enter the ID, password, keys or tokens provided by that gateway company - so the merchant brings their own processor contract. Capability varies by processor: offline payment, bar tabs and pre-auth tipping are marked NO for several of them. https://help.touchbistro.com/s/article/supported-payment-processor-integrations?language=en_US · retrieved 2026-08-06 adversarially verified

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

payments-published-rates

Re-retrieved live 2026-08-06. The vendor's own FAQ answers the question directly: "What payment processing rates will I be charged? It varies, as our payment partners will need to assess many factors before they give you a custom rate. This includes understanding your credit history, sales volume, and more." That is an affirmative statement that pricing is quote-only; no flat rate and no interchange-plus markup appears on this page or on /pricing/, whose payments entry reads only "Get a Quote". Graded C: this is the vendor's own pricing disclosure on a product page, which is exactly the surface a publication claim must be judged on, but it is not product documentation. https://www.touchbistro.com/features/payment-processing/ · retrieved 2026-08-06 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

Both totals are shown to the server and guest: "The bill preview on the checkout screen will display the Total (Sub Total + Sales Tax). It will also display the Cash Total which is all qualifying menu items discounted by the cash discount percentage plus sales tax as applied to the cash discounted sub total"; the Order screen shows the same Cash Total line and the quick-pay buttons prompt from it; "The closed bill will show the actual pre-tax discount amount" and penny rounding "will appear on the receipt". Shortfalls: this is not a native dual-pricing mode and does not store two prices per item - the Menu Item form carries a single before-tax Price, and the cash figure is computed by a percentage Discount object created under Menu | Discounts (cash-discounting); the discount is void if the diner pays only part in cash and is not restored by a second cash payment; and interaction with service charges is asymmetric - "the cash discount only applies to qualifying menu items, it does get applied in full to any service charges". https://help.touchbistro.com/s/article/checkout · retrieved 2026-08-06

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

The only bill-add-on engine is Service Charges (Cloud | Venue Info | Service Charges, POS 12.0.0+), whose configuration is enumerated in full: a name; charge type of Fixed Percentage, Fixed Amount or Open Amount; pre/post-discount application; recipient Venue or Employee; manual-versus-automatic with a per-order-type checklist; a Dine-In minimum party size; and an optional Apply Tax with tax selection. There is no card-type, BIN, product-code or network-cap input anywhere in it, and it carries the explicit instruction "Do not use service charges to handle charging credit card fees." The POS Advanced settings screen is likewise enumerated in full and its Payments section contains only Open Cash Drawer When Accepting Credit Payments, Open Cash Drawer When Accepting Cash Payments, Show Non-Integrated Payment Options and Require Auth # - no surcharge control and no per-location enable. The vendor's documented route to recovering card costs is the reverse construction: build the fee into menu prices and apply a percentage cash discount (cash-discounting). https://help.touchbistro.com/s/article/Service-Charges · retrieved 2026-08-06

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

payments-emv-nfc

Payments page: credit, debit and digital wallets including Apple Pay, Google Pay and Samsung Pay via tap-to-pay on first-party terminals. https://www.touchbistro.com/features/payment-processing/ · 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

"What Payment Processor Integrations Does TouchBistro Support?" is a supported/unsupported feature matrix covering every processor (TB Payments, Chase, TSYS in the USA; Chase Merchant Services, TD, Moneris in Canada), and every column is a physical terminal - PAX A800, PAX A920Pro, Ingenico Lane/3000, Link/2500, Moby 8500, Moneris Go / Desk 5000 / Move 5000 / V400. Rows include Credit Card Swipe, Credit Card EMV (Chip/Pin), Card Not Present, Pre-Auth Tipping, Start Bar Tabs, Offline Payment, Table-Side and "Tap and Pay" - so tap acceptance is a property of the paired terminal, not of the iPad or a phone. There is no Tap to Pay on iPhone entry, no Android tap-to-phone entry, and no reader-less acceptance row. TouchBistro POS itself runs only on iPad (hardware-payment-third-party-app-sup2 lists Compatible iPads, Printers, Routers, Cash Drawers, Barcode Scanners and Supported Payment Processor Integrations), and the vendor's payment-processing page describes "tap to pay, and digital wallet payments from Apple Pay, Google Pay, and Samsung Pay" as things the merchant's terminal accepts. https://help.touchbistro.com/s/article/supported-payment-processor-integrations · retrieved 2026-08-06

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

Upheld but on a different source than cited — I could not find the quoted sentence on /features/payment-processing/. The verifiable claim is on the TouchBistro Payments page: "Tableside contactless payments save your staff time and make it more convenient – and safer – for guests to pay." Marketing-page claim level, not product documentation, and gated to US-only TouchBistro Payments. https://www.touchbistro.com/touchbistro-payments/ · retrieved 2026-08-01 adversarially verified

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

Pay-at-table is a server-carried terminal flow, not a guest QR scan. The Moneris Go Plus Pay-at-Table article documents the terminal receipt options, where the guest-phone option is an SMS receipt link ("enter their phone number and have a link to the receipt sent to their phone's SMS app") and the QR option is explicitly "This is currently not supported. Leave as Disable ." The 2026 Product Guide's Payments page enumerates where a guest may pay as the counter, the table or online, with no guest-scan option (paraphrased, not quoted: that span sits across two columns of the PDF and is not contiguous in the extracted text). QR occurs in 51 product documents and not once as a guest payment channel; `scan to pay` occurs zero times corpus-wide. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. https://help.touchbistro.com/s/article/Setting-Up-Moneris-Go-Plus-Pay-at-Table?language=en_US · retrieved 2026-09-10

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

Pre-auth-then-adjust: bills print as a sign-on slip, then "From the Floorplan, tap Orders | Closed Bills. Locate bills with 'Tip Required' highlighted ... Enter the tip written on the receipt in the Tip field and tap Process Payment." On-device prompting: the same setting selects the alternative flow - "tap Admin | Admin Settings | Payments. Scroll down and locate Default Swipe Action. If it says 'Sign on Slip' tap it and select Sign on Screen" - after which "the diner will be prompted with tipping options"; PAX and Moneris Go terminals prompt on the terminal itself ("The diner will be prompted to leave a tip. If the diner prefers to leave no tip, they can tap No Tip"). Batch/adjust window: "as long as the batch has not been submitted, you can correct the tip. Check your batch close times. For example, TB Payments - Igenico automatically submits the batch at 11:30 PM EST", corrected via More | View/Edit Payments | Adjust Amount. Manager screen for unadjusted tips: the Closed Bills list highlights "Tip Required" with a "Only show if tip required" filter, searchable by authorization number or last four digits, and "Access to this feature is only available to the Admin account and, typically, a Manager staff type with Can Manage Orders enabled." Note the pre-auth path is terminal-dependent - the supported-integrations matrix marks Pre-Auth Tipping and Pre-Auth Tip Correction YES for Lane/3000 and Link/2500 but NO for PAX A800 and A920Pro, which use on-device prompting instead. https://help.touchbistro.com/s/article/How-Do-I-Reconcile-Tips-Written-On-Receipts · retrieved 2026-08-06

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

Tip-out exists as one flat rule: Admin Settings | Menu | Gratuity Settings, "Enable Calculate Credit Card Tip Out. Enter a custom Tip Out Display Name for the End of Day Report. Enter a Tip Out Amount (%)." It produces a per-employee figure - the server's shift report shows Cash Owed To House or Cash Owed to [name] with the arithmetic done - and Cloud reports carry CC Tip Out to House, CC Tips Owed to Server and Total Tips by Server under Labor | Staff Performance and Labor | Tips by Payment Method (Index-of-Cloud-Reports). Service Charges add a second, coarser lever: an autograt can be directed to "Venue" (house revenue) or "Employee" ("whoever opens the bill will receive the charge ... rolled into their earned tips"). Shortfalls: there is no rule engine - the only configurable input is a single percentage of credit card tips, with no allocation by hours worked, sales, role percentage or points; the withholding does not apply to cash tips; and nothing distributes the collected pool back out to support staff, so the per-employee allocation is a withholding figure rather than a pool share. https://help.touchbistro.com/s/article/gratuity-settings · retrieved 2026-08-06

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

Setup guide (updated 2026-07-21) documents an "Enable Store and Forward" setting with two configurable caps: "The system will decline any single charge that exceeds the Per Transaction Limit. Similarly, the system will decline transactions once all transactions exceed Total Limit during the offline period." TouchBistro ships defaults and advises tuning them against your chargeback history. Documented constraints: Tip on Terminal is required (offline is unavailable with tip-on-receipt), store and forward cannot start bar tabs, and offline authorization verifies only card number and expiry - it cannot check lost/stolen status or credit limit, so the merchant carries the decline risk. The POS retries upload every 30 minutes; unforwarded items show Pending and rejected ones Declined on the Store and Forward Summary report, and declined transactions expire after 7 days. Availability is processor- and device-specific: the support matrix marks Offline Payment YES only for TB Payments Lane/3000 and Link/2500 and for Moneris DX 8000/A35, and NO for TB Payments A800/A920Pro, Chase USA, TSYS, Chase Canada and TD. https://help.touchbistro.com/s/article/Setting-Up-the-TouchBistro-Payrix-Lane-3000?language=en_US · retrieved 2026-08-06 adversarially verified

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

The post-reconnect report is present and specified: "TouchBistro will attempt to automatically upload offline payments every 30 minutes. You should review the Store and Forward Summary report to see if any transactions have been declined", reached via Admin | Payment Gateways Options | Store and Forward Summary. Outcomes are enumerated - not-yet-forwarded payments are marked Pending, accepted ones are removed, "Payments forwarded which then get rejected will be flagged as Declined. You can tap Print Receipt to print a copy of the declined transaction", declined transactions can be re-forwarded but "will expire after 7 days" - and offline payments are flagged in Closed Bills with a generic CARD PAYMENT label until they settle. Shortfall: no liability statement. The vendor discloses only the risk - "the system can only verify the expiry date and card number. It cannot check if the card is lost/stolen or has sufficient credit limit" - and neither this article, the parallel store-and-forward guides, the Terms of Service nor the Dine terms and conditions on www.touchbistro.com state who absorbs the loss on a declined stored transaction. https://help.touchbistro.com/s/article/Enabling-and-Using-Store-and-Forward-with-TouchBistro-Payments-Payrix · retrieved 2026-08-06

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

Physical and digital first-party gift cards with "Multi-Location Support" and redemption on the online ordering page; POS integration gives "reporting and end-of-year reconciliation support." Paid add-on. https://www.touchbistro.com/gift-cards/ · retrieved 2026-08-01

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

payments-house-accounts

"Customer Accounts are a way to extend temporary credit to diners. For example, you cater your local city hall's weekly council meeting. Instead of charging the city each time for the order, you agree to settle up at the end of the month and bill it, instead, to a Customer Account." Orders close via Checkout | Pay on Account; the Account History screen carries the running balance and "For partial payments, the account's outstanding balance will be shown after the payment"; deposits can be pre-collected and are reported as non-sale deposits; accounts can be favourited, archived, reactivated and deleted (only if never used). Reporting: Accounts Report and Detailed Account Report can be added to the End of Day template, and the Payment and Refund Totals Report carries amount charged to accounts, with Cloud fields Account Name, Charged to Account, Deposits, Subtotal, Tips and Total under Audit | Accounts Report. Shortfalls: account creation is documented only as "Enter the details about the account" with no credit limit field anywhere in the article or in the Cloud Accounts Report field list, and no periodic statement or invoice generation is documented - settlement is a manual Apply Payment against the balance, with the caveat "You cannot refund or delete a payment made to an account." Accounts also do not support integrated payments with TouchBistro Payments - Ingenico (Moby 8500). https://help.touchbistro.com/s/article/customer-account-list · retrieved 2026-08-06

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

Multiple tenders on one check are documented: partial payments are supported ("if the diner partially pays with cash, the cash discount is no longer applied and the bill's remaining balance is calculated based on the pre-discount total... if a second payment is made in cash, the discount will not be restored"), and a payment can be undone mid-settlement via Edit/Undo Payments. Splits offered are Split By Seating and Split Evenly By # (no stated ceiling on the number of ways), plus item-level allocation across seats. Shortfall: there is no arbitrary dollar or percentage split mode, and the split and multi-tender paths interact badly - "you cannot split... a bill that has a partial payment", and once a split bill is partially paid you cannot remove the split or return to the Order screen. https://help.touchbistro.com/s/article/checkout?language=en_US · retrieved 2026-08-08 adversarially verified

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-based authorization is documented per action - Manager Passcode Settings cover Void Items, Delete Items, Discount Items and Open Cash Drawer, and the role matrix carries Can Authorize and Perform Voids without Approval, Can Authorize and Perform Discounts without Approval, Can Open Cash Drawer and Can Refund Closed Bills. Approver attribution exists for voids and discounts (Authorized By on Void Detail and Discount Details Reports), for deletes (Deleted Items Report Detailed view: "Manager - Name of the manager who approved") and for no-sales (No Sale Report: Server Name plus Manager). Shortfall: refunds are not covered the same way - the Audit | Bills with Outstanding Balances report "will not show full or partial refunds, or refunds using the Refund Sale option" and no report exposes an Authorized By for a refund; and the trail is not immutable, since the Reopened Bills note warns that "using the reopen feature will delete the bill from your system and any integrated payment information associated with it". https://help.touchbistro.com/s/article/security-settings?language=en_US · retrieved 2026-08-08 adversarially verified

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

payments-chargeback-tooling

Shortfall: available only to merchants on TouchBistro Payments (Payrix), it lives in the separate payments portal rather than the POS, and evidence is manually uploaded documents rather than assembled from the POS transaction record. TouchBistro documents a Disputes page in the TouchBistro Payrix Portal (payrix.touchbistro.com / ca.payrix.touchbistro.com) that "alerts you to chargebacks arising from customer disputes", lets the merchant "accept the charge back by clicking Accept Liability or challenge it by clicking Respond", warns that "If you do not respond by the Response Due Date, the dispute will be automatically flagged as lost", and takes a representment with supporting documents (signed credit card receipt, authorization form, invoice, signed proof of delivery, correspondence logs, screenshots of your Terms of Service, photos, incident summary; 2 MB per document, 10 MB total). Dispute Details, Disputes and Dispute Ratios standard reports are also documented. Merchants on TouchBistro's other processors get nothing: the payment-processing FAQ says of "chargebacks" - "Please reach out to your payment processor." https://help.touchbistro.com/s/article/Using-Your-TouchBistro-Payrix-Portal?language=en_US · retrieved 2026-08-06 adversarially verified

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

The guest profile is enumerated and contains no card: "When a diner is signed in, the diner can click on their name and then click Profile. The diner can edit their name, email, password, and phone number", plus saved delivery addresses which can be added, edited or deleted - the only reusable stored data. The same diner account is the one shared with Loyalty and Marketing and with accounts created at the point of sale, so it is the guest profile across channels. Online Ordering re-collects the card each time: "If you have enabled Online Payments, you will see a tip control and fields to enter credit card details", and scheduled orders "can only select to pay by card online" through those same fields. Phone orders are taken as a card-not-present transaction keyed at the terminal for that order (How Do I Take a Payment Over the Phone ...). The one stored-card feature is single-tab scoped - the gateway option "Save card for payment when opening bar tabs" retains the swipe for that bar tab only and the auth is consumed at checkout. No tokenized card-on-file reusable across online ordering, phone and in-store is offered. https://help.touchbistro.com/s/article/How-to-Create-a-Diner-Account-Via-Online-Ordering · retrieved 2026-08-06

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

payments-payout-timing

Published: Chase accounts typically next business day; other institutions 1-4 additional business days. No same-day or instant funding option is offered. https://www.touchbistro.com/features/payment-processing/ · retrieved 2026-08-01

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

Neither conjunct is published. The 2026 Product Guide's TouchBistro Payments "What features are included?" list names Security and Fraud Protection and describes it as "Enjoy the peace of mind and security of end-to-end data encryption" — E2EE, which is not the PCI-validated P2PE program. `P2PE` and `point-to-point encryption` occur zero times on every product surface (their single corpus-wide hit is an industry blog post about card processing generally), and `PCI DSS`, `Attestation of Compliance` and `AOC` occur zero times anywhere in the corpus. PCI is present 36 times and was read: in the Product Guides it is always attributed to the processors ("our trusted, PCI-compliant payment processors"), and in the current KB it is a PCIe SSD requirement, a TSYS Genius Mini terminal note and a Moneris pin-pad Mode setting. There is no security page (/security/ 404s at exactly 60 bytes, byte-identical to a fabricated control) and trust.touchbistro.com is NXDOMAIN. Subject is therefore the processors, not TouchBistro. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Controls as measured over the cited PDF by all three instruments: P2PE 0/0/0, point-to-point encryption 0/0/0, PCI DSS 0/0/0, Attestation of Compliance 0/0/0, AOC 0/0/0, tokenization 0/0/0. The bare string PCI is likewise 0 under all three instruments in this file, so the 36 corpus-wide PCI hits the note reads are in OTHER documents. CITATION SCOPE NOTED: the quoted phrase PCI-compliant payment processors is not in this 2026 US guide under any instrument; it is in a sibling Product Guide, and the conclusion drawn from it is unaffected. The distinguishing E2EE quote IS in this file under all three instruments. POISON PUBLISHED: SCA reads 0 tokenised but 13 squashed, every one a fragment of scan or of diners can, orders can and s can. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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

"Send the Right Order to the Right Station Every Time" — routes to grill, fryer etc; menu management routes "orders to specific kitchen stations by menu item type." Per-location self-service configurability not explicitly stated. https://www.touchbistro.com/kitchen-display-system/ · 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

All POS and online orders appear "in one place as different order types on single or individual screens" and multiple screens sync bumps/strikethroughs. Gating order completion on every contributing station bumping is not documented. https://www.touchbistro.com/kitchen-display-system/ · 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

Menu items carry a Default Course field in Menu Management ("Set it if the Menu Item needs to always be a specific course... flag it as a Drinks course"). On the POS Order Screen, "tap on the Course icon... Tap Fire to tell the kitchen to fire a selected course. Or tap an individual menu item to fire it. Alternatively, tap Hold if you need to tell the kitchen to hold preparing a certain item," plus Send Drinks and send-by-course. The KDS side mirrors this: on TouchBistro KDS Powered by Fresh "If you send a fire order for a course, Fresh KDS will move the course to the top of the ticket. Each item will be stamped with its fired time," held items collect under a Holds button and "Tap Release it will return the held items to the main screen." The expo screen can also originate the fire: the Order Behavior setting Manual Item Fire means "items sent from the POS will initially be in a Hold status. You can then fire individual items from the KDS versus firing items via TouchBistro's coursing" (https://help.touchbistro.com/s/article/Using-TouchBistro-KDS-Powered-by-Fresh). https://help.touchbistro.com/s/article/sending-drinks-and-courses-at-separate-times · retrieved 2026-08-06

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

Enumeration of the configurable surface, not absence of evidence. The Menu Item guide tabulates every field on a menu item -- Name, Short Name, contains alcohol, requires manager approval, can be returned, Background Color, Default Course, Available For, Images, Price, Open Price, Taxes, Total cost of ingredients, Item out of stock, UPC Code, Menu Group, Sales Category, Modifier Group, Prep Stations, Custom Hours -- and there is no cook time or prep duration field. The Fresh KDS guide likewise tabulates the whole of Settings | Appearance (Show Employee Name, Item Display Option, Show Seat Number, Order Type Colors, Modifier Styles, All Day Count) and Settings | Order Behavior (Manual Item Fire, Tap to Start, Strike Through Individual Modifiers, Move Completed Items to Bottom of Order Card); none stagger item start or display. The only timing behaviour documented is measurement after the fact -- "Prep time stats and transition times calculate as soon as the order comes into the KDS" -- and, on the legacy iPad KDS, colour-change thresholds (Turn Order Yellow After / Turn Order Red After) plus an Enable Cooking Time Indicator timer that tracks "the time to prepare each order item" (https://help.touchbistro.com/s/article/using-the-kds). Timers and colour ageing are not pacing. https://help.touchbistro.com/s/article/Menu-Management-How-to-Add-Menu-Items · retrieved 2026-08-06

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

Online Ordering | Advanced Settings, Order Throttling: "Enable if you wish to prevent diners from submitting new orders that would exceed a maximum count every 15 minutes. If enabled, enter the maximum number of orders that can be submitted per 15-minute window. For example, if set to 10, if the 11th diner tries to place an order, the diner will be required to schedule their order for later (if scheduled orders are enabled), or can place their order when the next 15 minute window opens." That is a configurable order-volume threshold that automatically paces release of incoming digital orders. Worth recording: the threshold is a fixed count per window rather than a ticket-time measure, and a separate manual timed pause (Manage Online Ordering, three durations) handles ad hoc rushes. https://help.touchbistro.com/s/article/touchbistro-online-ordering-merchant-settings · retrieved 2026-08-06

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

Documented for DoorDash only. Pause: from Orders | Online Ordering the staff member taps Manage Online Ordering, picks one of three pause durations and taps Pause Orders; "When paused, the diner will not be able to place a non scheduled pickup order," and DoorDash itself computes the next available slot (https://help.touchbistro.com/s/article/DoorDash-Understanding-the-Server-Experience). 86: "If you mark a menu item out of stock via Menu Management, this will get pushed to DoorDash and the menu item will be hidden on the DoorDash order page," and Out of Stock / Back in Stock (86'ing) is listed among the changes TouchBistro pushes to the DoorDash store. Shortfalls: (a) Uber Eats, Grubhub and the rest reach TouchBistro only through the UrbanPiper or Deliverect aggregators, and for those TouchBistro instructs operators "You still need to keep and use your third-party online ordering platform tablets. Do not disconnect the tablets - the platform may think your restaurant is not open" -- pause and availability are handled on each platform's own tablet, and the aggregator menu upload carries only "Menu Item Name, Menu Item Price, Menu Item Description, Menu item Modifiers" with no stock field (https://help.touchbistro.com/s/article/what-is-an-online-ordering-aggregator, https://help.touchbistro.com/s/article/getting-touchbistro-set-up-for-your-online-ordering-aggregator); (b) neither pause nor 86 originates at the KDS -- pause is a POS/Cloud action and 86 is set in Cloud Menu Management; (c) Item Availability is a "sticky" field: once edited in the DoorDash Merchant portal it "will no longer accept updates if changed in TouchBistro Menu Management." https://help.touchbistro.com/s/article/doordash-Integrating · retrieved 2026-08-06

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

Positive evidence of a different mechanism. DoorDash Drive setup field Food Prep Time: "This is the estimated amount of time it will take for the order to be prepared. DoorDash Drive won't dispatch a Dasher until the food prep time has elapsed." Dispatch is therefore driven by a static configured constant, not by a bump. Reinforcing this, TouchBistro states it cannot send order-state messages to DoorDash's driver side at all: "If you've accepted the order and used the cancel option under More, you will need to immediately call DoorDash support and cancel. TouchBistro will not issue a cancel message to the driver's DoorDash app" (https://help.touchbistro.com/s/article/How-to-Use-DoorDash-Drive). On the Marketplace side the only readiness lever documented is manual and lives in DoorDash's own webview, not on the KDS: in the DoorDash Order Manager "You can adjust the pickup time using the controls at the top. You can increase or decrease the time in 5 minute intervals" (https://help.touchbistro.com/s/article/DoorDash-Understanding-the-Server-Experience). The Fresh KDS bump action is documented in full -- "You can close a ticket by tapping on its X button or tapping anywhere in the ticket's header area" -- with no outbound event. https://help.touchbistro.com/s/article/Getting-Started-With-DoorDash-Drive · retrieved 2026-08-06

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

kitchen-bump-bar-hardware

"Optional bump bar and sticky label printers available" alongside MicroTouch 15.6" and 21.5" touchscreens. Specific bump-bar models are not enumerated. https://www.touchbistro.com/kitchen-display-system/ · retrieved 2026-08-01

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

kitchen-all-day-counts

Present but tier-limited. TouchBistro KDS Powered by Fresh: "If you tap the option bar at the bottom and then tap Summaries, you will see a list of your mains ordered." The legacy iPad KDS is more explicit at item level -- "Tap Show Summary in the menu bar to see a list of menu items on order and how many have been ordered" (https://help.touchbistro.com/s/article/using-the-kds). Shortfalls on the current product: (a) the modifier dimension is a paid upsell -- the section is headed "All Day Counts (Premium/Unlimited Subscribers)"; (b) it counts operator-defined ingredients rather than modifiers as such -- you "Manage Ingredients", then create a New Counting Rule bound to "the parent menu item or the menu item modifier" or a Combo, e.g. one tomato per Garden Salad ordered as a modifier; (c) it is "an either/or setting (you see ingredients or menu items in the summary but not both)", so item and modifier counts cannot be on screen together; and (d) TouchBistro warns "No records are kept of ingredients used. It does not interact with our inventory management system. You cannot set up different kinds of measures." https://help.touchbistro.com/s/article/Using-TouchBistro-KDS-Powered-by-Fresh · retrieved 2026-08-06

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

Orders display instantly with "optional audible alerts" and the dashboard reports bump times. Configurable per-station target cook times with colour escalation are not documented. https://www.touchbistro.com/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

The vendor documents the failure path and it ends in manual recovery. Advanced | Printing, Enable Safe Printing: "TouchBistro will ensure the printer you are sending a ticket or receipt to is online (connected, turned on, and loaded with paper) before attempting to print... If TouchBistro does not find the designated online printer, it will make a few attempts to connect before allowing you to dismiss the dialog box." No reroute to another station is described. Auto Accept documents the same manual recovery: "If a print job (either a kitchen ticket or guest check) fails for some reason (e.g., the printer can't be found or it's out of paper), the device configured for Auto Accept will display the print error as usual... After fixing the printer issue, tap the order, tap More, and then tap Reprint Order Ticket" (https://help.touchbistro.com/s/article/How-to-Enable-Auto-Accept-for-Online-Ordering). Redundancy in TouchBistro is manual duplicate routing configured in advance, not failover: a Prep Station is "representations of one or more physical printers" and a menu item may be assigned to several Prep Stations (https://help.touchbistro.com/s/article/Menu-Management-Prep-Stations), and the vendor's stated remedy for KDS fragility is to run a printer permanently alongside it -- "we recommend that you use a LAN-based kitchen impact printer in conjunction with the KDS... if a ticket is closed accidentally on the KDS, a physical copy of the ticket is immediately available from the printer" (https://help.touchbistro.com/s/article/kdssettingup). https://help.touchbistro.com/s/article/advanced-settings · retrieved 2026-08-06

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

kitchen-offline-operation

Verified verbatim: "Our offline mode ensures your KDS will continue working even when your internet is temporarily unavailable." Note the exact quote the dossier attributes ("Built-in redundancy ensures...") is not the current page wording — same substance, sloppy quoting. https://www.touchbistro.com/kitchen-display-system/ · retrieved 2026-08-01 adversarially verified

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

Staff can "strikethrough individual items and modifiers," so full modifier breakout is displayed. Recipe steps or portioning detail on the station screen is not documented. https://www.touchbistro.com/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

Enumeration of the whole modifier model. A Modifier Group has exactly these settings -- Modifier Group Name, Minimum Modifiers, Maximum Modifiers, Icon, Available For, Assign to -- and its members are either an existing Menu Item (with an upcharge price, a Mandatory flag and a sort position) or a free-text Kitchen Instruction. There is no section, half, quarter, placement or portion attribute and no price multiplier. TouchBistro's own worked example is a flat pizza toppings list: "For a pizza toppings modifier group, the cheese option might be set to mandatory." Because placement is never captured, nothing sectioned can be rendered downstream; the ticket rendering rule confirms the model is ordinal rather than spatial -- "Modifiers will appear on the ticket in the order they are selected" (https://help.touchbistro.com/s/article/Menu-Management-How-to-Add-Menu-Items) -- and modifier handling on tickets and screens is by prep station only (https://help.touchbistro.com/s/article/Understanding-Modifier-Routing). Fresh KDS's only modifier presentation feature is keyword highlighting: Modifier Styles "work by a simple pattern matching on some key terms in a modifier." https://help.touchbistro.com/s/article/Menu-Management-Modifier-Groups · retrieved 2026-08-06

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

kitchen-recall-refire

"View and recall past orders at any time" to identify and correct errors. Item-level refire or reprint without re-entry is not documented. https://www.touchbistro.com/kitchen-display-system/ · retrieved 2026-08-01

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

On TouchBistro KDS Powered by Fresh, edits to a displayed ticket are flagged at both levels: "If you send a second course, the ticket will add the course items with the appropriate banner to the full ticket. Note the pencil icon in the ticket header. This indicates the ticket has been updated," and at item level "the pencil icons next to the items that have been fired. The pencil icon indicates the menu item has been updated in some way." Fired, held, picked-up and resent states each carry their own banner or icon, and resends are time-stamped in place ("Resent items are merely time stamped 'Resent at'"). Removals are covered on the legacy iPad KDS -- "Voided tickets will turn red and voided items will appear on a ticket next to them" (https://help.touchbistro.com/s/article/using-the-kds) -- and voids follow the same station routing as the original item, so they reach the screen that showed it: "Voids use the same routing path. If you void a burger with a salad side, the void will go to the burger's printer and the salad's printer" (https://help.touchbistro.com/s/article/Understanding-Modifier-Routing). https://help.touchbistro.com/s/article/Using-TouchBistro-KDS-Powered-by-Fresh · retrieved 2026-08-06

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

The KDS module's own included-feature enumeration has no guest-facing output. The 2026 Product Guide's "TouchBistro's Kitchen Display System Powered by Fresh" page answers "What features are included?" with nine items — POS Integration, Customizable Display and Touchscreen Interface, Order View, Ticket History View, Routing Capabilities, Online Order Fulfillment, Bump Bar Compatible, Reporting and Analytics, Offline Mode — and none is a guest notification or status board. The only guest SMS channel in the suite is Reservations ("communicate with guests via SMS and email"), which is booking communication and a separately priced product, and TouchBistro Marketing is email and in-app only. No bump-to-notify behaviour is documented in the current 861-article KB. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Not an absence-based verdict: it rests on the KDS module answering What features are included? with a closed nine-item list. Both enumeration anchors, Bump Bar Compatible and Ticket History View, are present under all three instruments, so the enumeration this verdict rests on was read intact. Supporting controls over the cited PDF: guest notification 0/0/0, order ready 0/0/0, status board 0/0/0. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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

kitchen-waste-logging

Present, but in the wrong place and on the legacy platform. The Ingredient-Based Inventory System reports Waste Quantity as "The ingredients used for voided items without a return to stock" alongside a Waste Cost figure, so a void carrying a reason code that is not set to return to stock depletes ingredient inventory and lands in a waste report; reason codes come from Menu Management | Void Reasons, and "If you void an item, stock count does return to its previous count if the void has been set up to return to inventory" (https://help.touchbistro.com/s/article/Menu-Management-Stock-Availability). Shortfalls: (a) the entry point is the POS order screen void, not the kitchen -- neither KDS product exposes a waste, spoilage or remake action; the Fresh KDS ticket options are enumerated as Order Type, Prioritize, Order Type Colors, Split/Merge, Add Note and Fulfillment Times (https://help.touchbistro.com/s/article/Using-TouchBistro-KDS-Powered-by-Fresh); (b) there is no distinct spoilage or remake category, only voids; and (c) the ingredient depletion path lives in the legacy POS-based Ingredient-Based Inventory System, which TouchBistro says "is no longer being actively developed, it is not available for all accounts." https://help.touchbistro.com/s/article/setting-using-touchbistro-ingredient-based-inventory-system · retrieved 2026-08-06

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

KDS dashboard reports "average tickets, detailed order information, bump times, and BOH performance metrics." Percentile times, per-station and per-channel slicing, and CSV/API export are not documented. https://www.touchbistro.com/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

Predicted prep quantities from POS data are shipped, but not a prep task list surfaced to kitchen staff. The Inventory Management product page: "Never Run Out of Key Ingredients Again Thanks to Food Prep Forecasting Ensure you always have sufficient inventory on hand and prepped for service with data-driven forecasting that takes your actual and ideal usage into account." The 2026 Product Guide's Inventory Management "What features are included?" list names both "Food Prep Forecasting" and "Task & Waste Manager" as included features. SHORTFALL: nothing published describes the output as a daily prep task list surfaced to the kitchen. The current 861-article KB holds only 4 inventory articles, all about the POS's built-in ingredient inventory rather than the Inventory Management module, so the module has no operator documentation on this host; `prep forecast` occurs zero times corpus-wide and every `prep` hit in the current KB is Prep Stations (kitchen ticket routing). Whether the forecast reaches cooks as a task list is undetermined. https://www.touchbistro.com/inventory-management-offer/ · retrieved 2026-09-10

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

Positive enumeration from vendor documentation, replacing the marketing product catalog the first pass cited. (a) The delivery-order screen is documented field by field and the driver is a free-text string carried on the order, not an entity: "Add important notes to help the driver (e.g., ring buzzer 1217). Enter the name of the driver assigned." The Delivery Order Options table then enumerates every action available on a delivery order -- Change Staff, Transfer to Table, Merge Delivery, Edit Info, Delete Order -- with no dispatch, no assign-to-driver and no in-store/on-run/returning state. (b) Staff Types are an enumerated permission model (https://help.touchbistro.com/s/article/edit-staff-types): every General, Payments, Staff and Manager option is listed and the only delivery-related permission is "Can Access Takeout/Delivery" -- there is no driver role and no run state. (c) Index of Cloud Reports, which "lists all data cells generated by Cloud and its associated report" (https://help.touchbistro.com/s/article/Index-of-Cloud-Reports), contains no driver data cell at all: delivery appears only as Sales | Sales by Order Type and Audit | Delivery Fee, and per-person reporting is by Server Name, so there is no per-driver run history. (d) The word "dispatch" appears in exactly one of the 765 help-centre articles, and there in reference to DoorDash dispatching a Dasher. Own-fleet delivery is supported and drivers can be carried as staff and settled up individually at clock-out (see delivery-cash-reconcile), but that is the generic server flow, not a driver module. https://help.touchbistro.com/s/article/How-To-Take-Delivery-Orders · retrieved 2026-08-06 adversarially verified

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

Vendor documentation exhaustively describes the in-house delivery flow and it is an order list, not a dispatch board. Orders are created and worked from the Delivery/Takeout tab: "Enter the name of the driver assigned" is a free-text field on the order form alongside address and notes, and the complete enumerated set of Delivery Order Options is Change Staff, Transfer to Table, Merge Delivery, Edit Info, Delete Order. There is no driver-availability view, no elapsed-time-per-order display, and no multi-order run batching - Merge Delivery merges one order into another order, not several orders into a driver run. The article's stated end state is that the order sits "in the ASAP or Scheduled Orders section until the customer comes to pick it up or the driver has returned with payment." https://help.touchbistro.com/s/article/How-To-Take-Delivery-Orders?language=en_US · retrieved 2026-08-06 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

A map exists but not a routed multi-stop run. Creating an in-house delivery order: "Fill out customer details on the Delivery screen. Enter the address. When you enter the address, TouchBistro will display the delivery route on the map. If your iPad is not generating a delivery route, ensure TouchBistro has permission to access your location services." That is one geocoded stop, routed from the venue, inside a single order record. Shortfalls: the Delivery/Takeout tab is a flat list of orders, the enumerated per-order options are Change Staff, Transfer to Table, Merge Delivery, Edit Info and Delete Order, and nothing groups several orders into a run, sequences stops or optimises turn order. The only other map is DoorDash's, embedded in the DoorDash Order Manager webview: "You can see when a dasher is assigned, their in-bound location via the map, and the status of the delivery (in transit, delivered, etc.)" -- one courier, one order, and "Once the dasher picks up the order, you cannot track by the map" (https://help.touchbistro.com/s/article/DoorDash-Understanding-the-Server-Experience). https://help.touchbistro.com/s/article/How-To-Take-Delivery-Orders · retrieved 2026-08-06

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

delivery-driver-tracking

Third-party only, and partial even there. In the DoorDash Order Manager, opened as a webview from the POS after acceptance (role permission: Can Manage and Pause Online Ordering (DoorDash)): "You can see when a dasher is assigned, their in-bound location via the map, and the status of the delivery (in transit, delivered, etc.). Once the dasher picks up the order, you cannot track by the map. This ensures the diner's location remains confidential." Shortfalls: (a) the position comes from DoorDash's Dasher app, not a TouchBistro driver-facing app -- TouchBistro publishes no driver app, and on an in-house delivery order the driver is a free-text field ("Enter the name of the driver assigned", https://help.touchbistro.com/s/article/How-To-Take-Delivery-Orders) with no device, login or location capture; (b) tracking covers only the inbound leg to the restaurant and is cut off at pickup, so the drop leg is invisible to the operator; (c) it is per-order in a webview, not a dispatch board over a fleet; and (d) TouchBistro explicitly cannot push state the other way -- "TouchBistro will not issue a cancel message to the driver's DoorDash app" (https://help.touchbistro.com/s/article/How-to-Use-DoorDash-Drive). https://help.touchbistro.com/s/article/DoorDash-Understanding-the-Server-Experience · retrieved 2026-08-06

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

"A boundary is an area you define that is valid for delivery services provided by your venue. Diners ordering outside of a valid boundary won't be able to place a delivery order." Drawing is free-form on a map centred on the venue pin: "Click and drag a vector. Click again to start a new vector. Repeat until you've enclosed an area. A boundary requires a minimum of four vectors. Click Save when done." Multiple boundaries per venue are supported, with dedicated Working with Multiple Boundaries and Overlapping Boundaries sections, and boundary names must be unique. This is arbitrary polygon geometry, not a radius or a postcode list. Drive-time isochrones are not offered, but the claim requires polygons or isochrones, not both. Caveat worth recording: if the venue switches to DoorDash Drive fulfilment the polygons are discarded -- "If you have previously set up the Delivery screen for your own fleet (delivery times, delivery boundaries, etc.), they will not be used by DoorDash. DoorDash Drive employs a flat 5-mile (8 km) radius" (https://help.touchbistro.com/s/article/Getting-Started-With-DoorDash-Drive). https://help.touchbistro.com/s/article/Creating-Delivery-Boundaries · retrieved 2026-08-06

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

Per-boundary, all three components. On saving a boundary "you will be prompted to define the name for this boundary and input approximate wait times for preparation and delivery. You can also set a minimum spend amount for delivery. If an online order's subtotal is below this amount (before taxes, tips, and delivery fees but post discounts), Online Ordering will prevent the diner from completing a delivery order and prompts the diner to switch to the pickup method" (limits: wait time up to 360 minutes, minimum spend up to $1,000). Fees are separate objects bound to a boundary: "use the Assign to an Existing Delivery Boundary drop-down box to indicate which boundary this fee is applicable to"; a fee may be a fixed dollar amount or "Switch to Percentage" of the pre/post-discount subtotal, may be flagged taxable against a chosen tax, and may be waived above a spend threshold. Application is automatic from the entered address: "The diner will see the boundary's delivery fee in the cart. The diner will also see details on minimum spend, delivery fee, and the free delivery amount" (https://help.touchbistro.com/s/article/Diner-POV-Delivery-Boundaries-for-Online-Ordering). https://help.touchbistro.com/s/article/Creating-Delivery-Boundaries · retrieved 2026-08-06

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

Out-of-zone rejection is documented and enforced before acceptance: "When the diner visits your site, the diner will be prompted to enter the delivery address... If the address is completely out of any of your boundaries, the diner will be given an alert that warns 'Looks like you're too far for delivery.' The diner should then switch to pickup." Under DoorDash Drive the equivalent radius test applies -- "If the address is outside of the DoorDash Drive's 5 mile/8 km delivery radius, the diner will get a warning that delivery is unavailable due to being outside of the delivery boundaries" (https://help.touchbistro.com/s/article/How-to-Use-DoorDash-Drive). Geocoding is implicit in the point-in-polygon boundary test and in the POS drawing a route from a typed address. Shortfalls: (a) no address validation, normalisation or autocomplete against a mapping service is documented -- only the in/out-of-boundary test, and TouchBistro's own advice is manual verification ("test your boundaries with addresses that are just inside the boundary line to make sure desired diners are not excluded"); (b) phone orders keyed on the POS Delivery screen get no boundary check whatsoever -- the address merely "display[s] the delivery route on the map" and the order proceeds regardless (https://help.touchbistro.com/s/article/How-To-Take-Delivery-Orders). https://help.touchbistro.com/s/article/Diner-POV-Delivery-Boundaries-for-Online-Ordering · retrieved 2026-08-06

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

Enumeration of the delivery order surface plus a contrary documented tip rule. The complete set of fields on an in-house delivery order is customer details, address, notes for the driver, "Enter the name of the driver assigned", the date, and an optional reminder; the per-order options are Change Staff, Transfer to Table, Merge Delivery, Edit Info and Delete Order. There is no distance, mileage, run or per-delivery reimbursement field anywhere on it, and 'mileage' occurs in none of the 844 English help-centre articles. Tips are documented as going elsewhere: for online orders "Any credit/debit tips paid by the diner, either online or during pickup, will be credited to the Staff account logged into the iPad that closes the online order", and under DoorDash Drive "Any tip the diner leaves here will be earmarked for the DoorDash driver. It cannot be set to be split with the driver and the venue", with the venue then remitting it -- "Any figure under Tips to Venue for TouchBistro DoorDash Drive will be tips that you will need to remit to DoorDash" (https://help.touchbistro.com/s/article/How-to-Use-DoorDash-Drive). With no driver entity there is nothing to export to payroll as a reimbursement line. https://help.touchbistro.com/s/article/How-To-Take-Delivery-Orders · retrieved 2026-08-06

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

A generic per-staff settle-up exists and can be pointed at a driver, but there is no driver bank and no over/short. On clock-out TouchBistro generates a Shift Report: "When you clock out, TouchBistro generates your final shift report. Scroll to down to the Payment Totals header", which breaks out cash collected and tips charged to cards, and its closing section nets them -- "You'll see exactly who owes whom and how much ... The Cash Owed to House item indicates she owes house $36.41 out of the $56.85 currently on her person. If Jill took in more credit card tips than cash, then Cash Owed to House would be zero and Cash Owed to Jill would be a positive number." The report is printed and handed to the house to settle up. A delivery order can be routed to that person: the Delivery Order Options table offers "Change Staff - Tap Change Staff to assign the order to another server" (https://help.touchbistro.com/s/article/How-To-Take-Delivery-Orders). Shortfalls: (a) no float or bank is issued to the driver and no counted-cash figure is entered against an expected one, so the output is an amount-owed, not an over/short -- expected-versus-actual exists only at drawer level for the venue's business day in the End of Day Cash Deposit (https://help.touchbistro.com/s/article/How-to-Complete-Your-End-of-Day-Cash-Deposit); (b) the driver on a delivery order is a free-text name ("Enter the name of the driver assigned"), not a staff entity, so per-driver attribution only works if the operator makes each driver a staff member and reassigns every delivery order via Change Staff; (c) tips owed covers card tips only -- "TouchBistro does not keep track of cash tips you've accrued"; (d) nothing about the flow is delivery-specific, and TouchBistro separately notes it "does not support a mobile payment method a driver can take to the door". https://help.touchbistro.com/s/article/How-Do-I-Read-My-Shift-Report-on-the-POS · retrieved 2026-08-06 adversarially verified

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

Verified verbatim: "Pay one flat fee per order and $0 in commission" for DoorDash Drive, with the hard constraint the dossier correctly flagged — "all payments must be processed online. DoorDash Drive couriers cannot accept payment when delivering orders." Fee amount unpublished. Note the same page confirms the absence of any in-house dispatch: for own-fleet delivery the documented workflow is "you can call your customer at the phone number they provided with their order and take payment over the phone." https://www.touchbistro.com/online-ordering/ · retrieved 2026-08-01 adversarially verified

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

Positive evidence of a binary, manually thrown switch rather than hybrid dispatch. "If you already have your own fleet set up with Online Ordering delivery, you will need to continue using your own fleet until your account is approved by DoorDash. Once approved, you will see the option to Switch To DoorDash Drive on your Delivery setup page. Click Switch To DoorDash Drive and then confirm... If you wish to return to using your own delivery fleet, click Switch To My Own Fleet." The two modes cannot coexist even in configuration: "If you have previously set up the Delivery screen for your own fleet (delivery times, delivery boundaries, etc.), they will not be used by DoorDash. DoorDash Drive employs a flat 5-mile (8 km) radius from your venue and charges you a flat fee per delivery." There is no rule engine, no driver-availability input and no wait-time or out-of-zone trigger; out-of-zone under either mode simply pushes the diner to pickup. The one automation adjacent to dispatch is a timer, not a fallback: "DoorDash Drive won't dispatch a Dasher until the food prep time has elapsed." https://help.touchbistro.com/s/article/Getting-Started-With-DoorDash-Drive · retrieved 2026-08-06

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

DoorDash appears as a direct first-party integration (Online Ordering + Drive). Uber Eats, Grubhub and SkipTheDishes are reached through UrbanPiper and Deliverect middleware, not vendor-owned certified connections. https://www.touchbistro.com/features/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

Aggregator partners "pull orders from third-party apps into POS", so injection works — but for most marketplaces it depends on a separately-paid middleware layer. https://www.touchbistro.com/features/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

DoorDash publishes a machine-readable registry of its integration partners at https://merchants.doordash.com/api/partner-integrations — 64 providers, each tiered PREFERRED (12), CERTIFIED (47) or AT_RISK_OF_SUSPENSION (5), and each carrying an explicit true/false flag for 23 named integration features across four collections. It is served anonymously and merchants.doordash.com/robots.txt permits it. The programme is described, and its eight high-quality features defined in prose, at https://merchants.doordash.com/en-us/learning-center/doordash-preferred-integrations-program; the merchant-facing label for each flag comes from the label dictionary embedded in DoorDash's integrations comparison page. SCOPE: this attests the vendor's DOORDASH integration specifically — not Uber Eats, not Grubhub, and not the POS in general. DIRECTION: a true flag is a positive attestation; a false flag is NOT a reliable negative on its own, because Lavu's help centre documents a DoorDash temporary-closure control with scheduled auto-reopen while Lavu's `STORE_AVAILABILITY_WEBHOOKS` flag reads false, and Xenial's developer docs enumerate an order-ready notification while its `SUPPORT_ORDER_READY_SIGNAL` flag reads false. The flag `MENU_PULL_SUPPORTED` ('Real-time menu syncing') is TRUE for `touchbistro_production`, and the registry classes that entry PROVIDER_AGGREGATION_TYPE_POS rather than MIDDLEWARE_AGGREGATOR. THIS CORRECTS THE PRIOR REASONING: the cell was scored on the premise that menu publishing is a function of the middleware layer (Deliverect/UrbanPiper) and not of a TouchBistro master-menu push. `partial` is retained because `CHANNEL_BASED_MENU` is FALSE for `touchbistro_production` inside an ACTIVE ENABLING_DDOO collection, so the channel-specific price markups the claim requires are a measured absence on this channel. https://merchants.doordash.com/api/partner-integrations · retrieved 2026-09-12

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

The push is explicit: "Out of Stock / Back in Stock (86'ing)" is listed among the changes TouchBistro sends to the DoorDash store, and "If you mark a menu item out of stock via Menu Management, this will get pushed to DoorDash and the menu item will be hidden on the DoorDash order page." Latency is near real time -- "Changes to stock counts and availability do not have to be published. They are pushed to the venue immediately" -- and modifiers are in scope because "stock availability can be entered for menu items (e.g., bagels) sold via the order screen and menu items used as modifiers (e.g., packets of dipping sauce)", with automatic 86 at zero ("The Out of Stock control is automatically enabled if stock count reaches zero") and restoration on restock (https://help.touchbistro.com/s/article/Menu-Management-Stock-Availability). Shortfalls: (a) it is not a POS-side action -- "You can no longer edit a menu item and mark it out of stock or use the bulk edit option. If you want to mark any menu item out of stock... use the Out of Stock option on the Stock Availability dashboard" in Cloud; (b) DoorDash is the only marketplace wired to receive it -- Uber Eats and the rest arrive via UrbanPiper/Deliverect, whose menu upload carries only "Menu Item Name, Menu Item Price, Menu Item Description, Menu item Modifiers" with no availability field, and operators are told to keep the third-party tablets running (https://help.touchbistro.com/s/article/getting-touchbistro-set-up-for-your-online-ordering-aggregator); (c) Item Availability is a sticky field -- once edited in the DoorDash Merchant portal it "will no longer accept updates if changed in TouchBistro Menu Management"; and (d) depletion does not block DoorDash diners -- "DoorDash Online Ordering will not block a diner from ordering more items than are in inventory", and under Auto Accept "If a menu item is at zero inventory, it will still be accepted." https://help.touchbistro.com/s/article/doordash-Integrating · retrieved 2026-08-06

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

In-POS and timed: "If you are finding orders are coming in too quickly, the Manage Online Ordering button on the Online Ordering tab... lets a staff member temporarily pause orders. After tapping this button, the POS will open a web view page where you have three pause options. After selecting one, you can then tap Pause Orders to put it into effect... The POS will show a pause banner indicating what time ordering will recommence." Reactivation is automatic at the chosen duration and the effect reaches DoorDash's diner surface: "When paused, the diner will not be able to place a non scheduled pickup order. If the pause is 20 or 40 minutes, the diner will be able to schedule a pickup in the next available window that is the pause value + a prep time as determined by a DoorDash metric." It is also available from Cloud (Online Ordering | Manage Online Ordering) and gated by the Can Manage and Pause Online Ordering (DoorDash) role permission. Shortfalls: (a) DoorDash Marketplace and TouchBistro's own ordering site are the only surfaces this controls -- Uber Eats, Foodora, ChowNow and Skip the Dishes arrive through UrbanPiper/Deliverect, and for those TouchBistro instructs "You still need to keep and use your third-party online ordering platform tablets. Do not disconnect the tablets - the platform may think your restaurant is not open. You will need the third-party tablet to manage issues" (https://help.touchbistro.com/s/article/what-is-an-online-ordering-aggregator); (b) DoorDash-initiated pauses cannot be cleared from TouchBistro -- "These pauses forced by DoorDash cannot be manually unpaused" (https://help.touchbistro.com/s/article/doordash-Integrating). https://help.touchbistro.com/s/article/DoorDash-Understanding-the-Server-Experience · retrieved 2026-08-06

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

What exists: "Online Ordering | Sales By Online Order Provider will break out orders fulfilled by DoorDash Drive"; "To see each fee collected and the tax collected on the fee, see Audit | Delivery Fee", which "lists each time a fee is collected" and shows refunded fees as negatives (https://help.touchbistro.com/s/article/How-Does-the-Server-Manage-Online-Delivery-Orders-and-Fee-Reporting); and DoorDash orders "will be reported under the Online Ordering section where you can see the sales, cancellations and fulfillment status of the orders" (https://help.touchbistro.com/s/article/doordash-Integrating). What is missing, stated by TouchBistro itself: there is no payout-to-sales match and the commission side is reconciled manually off DoorDash's invoice -- "Service Fee will be treated as sales. Your account[ant] should be informed to deduct fees invoiced by DoorDash Drive from your actual sales figures" -- and tips owed to DoorDash are handled the same way ("DoorDash will include this in their monthly service invoice"). No report itemises commission or marketing fees, none ingests a deposit or payout file, and none identifies missing or unpaid orders; DoorDash billing disputes are routed to DoorDash support. https://help.touchbistro.com/s/article/How-to-Use-DoorDash-Drive · retrieved 2026-08-06

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

Surfaced: named onboarding error codes with remediation -- STORE_HOURS_NOT_POPULATED_FAILURE, MENU_BLANK_FAILURE, MENU_JOB_FAILURE, MENU_PULLING_REQUEST_FAILURE -- plus a Reconnect Store action; a per-integration status on the Cloud App Marketplace settings page, including a yellow banner when store activation fails; and forced-pause notices ("There can be reasons DoorDash itself pauses diner orders. A similar banner will display on this page"). Print-path failures surface on the POS: "the device configured for Auto Accept will display the print error as usual... After fixing the printer issue, tap the order, tap More, and then tap Reprint Order Ticket" (https://help.touchbistro.com/s/article/How-to-Enable-Auto-Accept-for-Online-Ordering). Shortfalls: (a) there is no log, dashboard or alert for a failed or rejected order injection -- an order not accepted in time is simply cancelled by DoorDash ("Orders in Pending must be accepted within 3-8 minutes or they will time out and be canceled", https://help.touchbistro.com/s/article/DoorDash-Understanding-the-Server-Experience) with no notification documented; (b) the vendor's answer to a lost order is a phone call, not a screen -- "DoorDash doesn't have a record of an online order" is listed as an issue to raise with TouchBistro support on 1-855-363-5252; (c) the only order-arrival health check offered to staff is manual polling: "You can immediately ping DoorDash Online Ordering by pulling down on the left pane and releasing it." https://help.touchbistro.com/s/article/doordash-Integrating · retrieved 2026-08-06

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

Present for the courier case: "When the order is accepted, the diner will get a confirmation email and/or ta[e]xt with a tracking link. If the diner clicks on it, the diner can follow the progress of the pickup and delivery. The tracking link opens in a browser tab. The progress is refreshed automatically. The diner can call the driver directly at the provided number." SMS is opt-in per order ("The diner will have to authorize SMS communication every time they order") and email always goes out (https://help.touchbistro.com/s/article/touchbistro-online-ordering-customer-alerts). Shortfalls: (a) it is tied to DoorDash Drive fulfilment -- for own-fleet delivery the documented diner alerts are acceptance and cancel/decline only, with no status or driver page, and the in-house driver has no tracked state beyond a name typed on the order; (b) it is not on the restaurant's domain -- "the diner will still need to find/access your Online Ordering site via order.tbdine.com or using the button widget on your own website"; (c) driver state is DoorDash's, and the number the diner must use is the venue's contact number given at checkout, not the driver's own. https://help.touchbistro.com/s/article/How-to-Use-DoorDash-Drive · retrieved 2026-08-06

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

The dynamic component exists but is DoorDash's and covers only the courier leg: "In the top left corner of the online ordering screen, they will be given a wait time. This is calculated based on the food prep time that you set up within your delivery settings and a DoorDash Drive delivery time estimate", and "Example: If 'Food Prep Time' is 15 minutes and it will take the Dasher 30 minutes to arrive, the diner will see a wait time of approximately 45-60 minutes (TouchBistro adds a 15 minute buffer)" (https://help.touchbistro.com/s/article/Getting-Started-With-DoorDash-Drive). On the DoorDash Marketplace side a pause causes DoorDash -- not TouchBistro -- to push the next available slot out "by the pause value + a prep time as determined by a DoorDash metric". Shortfalls: (a) the kitchen leg is a fixed operator constant in every mode -- Food Prep Time is "the estimated amount of time it will take for the order to be prepared", and for own-fleet delivery each boundary stores static "approximate wait times for preparation and delivery" (max 360 minutes) with no load input (https://help.touchbistro.com/s/article/Creating-Delivery-Boundaries); (b) nothing reads current ticket count, KDS load or in-house driver availability -- the only volume mechanisms are the manual timed pause and a fixed Order Throttling cap per 15-minute window; (c) for own-fleet delivery the entire quote is static. https://help.touchbistro.com/s/article/How-to-Use-DoorDash-Drive · retrieved 2026-08-06

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

delivery-offline-behavior

The vendor does publish an explicit, itemised offline table -- Take/close orders: Yes; Take cash payments: Yes; Take offline payments: Yes (TouchBistro Payments US or Moneris Canada); Print kitchen tickets: Yes; Send orders to the Kitchen Display System (TouchBistro KDS or Fresh KDS): Yes; Access iPad reports: No; Access real-time cloud reports: No ("TouchBistro will sync all sales/labor data when the Internet is restored"); Change/edit menu remotely on Cloud: No; Access online orders: No; Edit floor plan: No; loyalty and gift cards: No. Delivery is covered only by inference from two rows: online orders -- the channel most delivery orders arrive on -- are inaccessible, while a delivery order keyed on the POS is an ordinary order and so remains takeable and closeable for cash. Shortfalls against the claim: the table never names delivery; and it says nothing about whether a driver can be assigned during an outage, whether the delivery route map (which depends on iPad location services and a map service) still renders, or whether driver settlement and the Cash Deposits Expected/Over-Short calculation behave normally offline. No other help-centre article addresses delivery during an outage. https://help.touchbistro.com/s/article/What-can-you-do-with-TouchBistro-POS-if-your-Internet-goes-down · retrieved 2026-08-06

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

"100% commission-free" online ordering with a direct URL for the restaurant; card processing fees still apply. Pricing page repeats: "TouchBistro does not charge any commission fees on online orders." Sold as a paid add-on. https://www.touchbistro.com/online-ordering/ · 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

One menu record drives both channels, with a checkbox rather than a second build: on a Menu, "Available for - select if this menu should be available for use on the POS and/or on your online ordering site"; on a Menu Item, "Available For - if this Menu Item is part of a Menu Group that is included in a Menu available at the POS or for Online ordering and you would like to make it not available, remove the appropriate checkmark". The same item record carries the description and image used online ("if your restaurant is also connected to your TouchBistro Online Ordering site, the uploaded image will be used on your customer-facing menu. You cannot upload multiple images... you cannot have different images for Online Ordering and the POS"). One qualification: menu edits are not live until published - "anytime you add a menu item or edit a menu item, it will not automatically appear on your menu. You need to publish the changes" - though stock and availability changes bypass that step. https://help.touchbistro.com/s/article/Menu-Management-Menus?language=en_US · retrieved 2026-08-08 adversarially verified

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

TouchBistro's own documented answer to how a diner gets its ordering app onto a phone is a browser bookmark, not an app store: "Visit the Customer Web App URL in a browser. Tap the Share icon. Tap Add to Home Screen" for iPhone, and "Tap the Menu icon. Tap Install App | Install" for Android. The ordering surface itself is a hosted page the operator links from their own site ("Linking Your Online Ordering Page to Your Restaurant Website and Social Media"), and diner-facing discovery runs through TouchBistro's shared tbdine.com site. No per-restaurant branded iOS or Android binary appears in the App Marketplace integration list or among the priced add-ons on /pricing/. https://help.touchbistro.com/s/article/how-your-diners-can-add-the-customer-web-app-to-their-phones-home-screen?language=en_US · retrieved 2026-08-06 adversarially verified

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

Help centre: "Before diners can complete their order, they need to set up a diner account. TouchBistro Online Ordering does not allow an order with a guest account" (the guest-checkout path instead collects name/email/phone). Signed-in diners edit name, email, password and phone under Profile and hold multiple saved delivery addresses - "Diners can save multiple addresses", each addable, editable and deletable, and offered back for selection on a return visit. SHORTFALL: no saved or tokenized card is documented - the diner-experience guide has the diner "pick a method of payment" and enter credit card details on the checkout screen each time - and no one-tap reorder of a previous order appears anywhere in the documented diner flow, which builds the cart item by item from the menu screen. https://help.touchbistro.com/s/article/How-to-Create-a-Diner-Account-Via-Online-Ordering?language=en_US · retrieved 2026-08-06

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

The Online Ordering Advanced Settings screen is enumerated in full in the vendor setup guide - Offer Cutlery, Offer Tip, Allow Scheduled Orders/Days in Advance, Calorie Contextual Statement, Order Throttling, Checkout as Guest - with no suggestion, add-on or recommendation control, and the complete Online Ordering nav is Hours of Operation & Holiday Closures, Pickup, Delivery, Advanced Settings and Page Activation. The companion end-to-end diner walkthrough (menu screen with menu groups, item popup with mandatory/optional modifiers and special instructions, cart, checkout, Place Order) contains no suggested-items or add-on step at any point. TouchBistro's own upsell language is about staff at the POS, not digital checkout: "Any item qualifying for a promotion will have a % icon associated with it, giving the server a heads up... Alert staff to look for these icons so they can help upsell." No attach-rate or suggestion-conversion metric appears in the enumerated Cloud report set. https://help.touchbistro.com/s/article/touchbistro-online-ordering-merchant-settings?language=en_US · retrieved 2026-08-06

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 pickup is supported. Per-daypart throttling, capacity limits, and automatic slot closure when the kitchen saturates are not documented. https://www.touchbistro.com/online-ordering/ · 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 and delivery (DoorDash Drive or own fleet) are documented in one flow. Curbside arrival check-in and dine-in QR ordering within the same flow are not. https://www.touchbistro.com/online-ordering/ · retrieved 2026-08-01

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

A separate QR Code Menu tool exists, but nothing documents scan-to-order or scan-to-pay attaching to an existing POS check with splitting and tipping. https://www.touchbistro.com/online-ordering/ · retrieved 2026-08-01

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

The CFD is documented as a passive mirror of the server's order screen and is explicitly incapable of taking guest input: "Your empty Order screen will be paired with your CFD's Welcome Screen", it "will continue to display the customer-facing order screen through the entire payment process", and - decisively - "You cannot display any kind of sign-on-screen payment dialog on the CFD or display any kind of QR code scanning screen." No self-order kiosk appears in the App Marketplace integration list, among the priced add-ons on /pricing/, or in the Hardware, Payment, and Third Party App Support article, whose complete category list is Compatible iPads, Compatible Printers, Mac Computer Purchasing Guide, Compatible Routers, Supported Payment Processor Integrations, Compatible Cash Drawers, Compatible Barcode Scanners. Counter-evidence noted and weighed: TouchBistro's AODA accessibility policy contains the boilerplate line "TouchBistro will consider accessibility features when designing software updates in our iPad POS system and self-ordering kiosks" - a forward-looking legal-template commitment, with no kiosk product, SKU, price or setup article anywhere behind it. https://help.touchbistro.com/s/article/Using-the-CFD?language=en_US · retrieved 2026-08-06 adversarially verified

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

The 2026 Product Guide's Online Ordering page answers "What features are included?" with POS Integration, Multi-Touchpoint Ordering, Scheduled and Immediate Orders, Integrated Online Payments, Discovery Platform, On-Demand Delivery, Cloud Management, Marketing Integration, Loyalty Integration and Gift Cards Integration. No shareable multi-participant cart, per-person cap or group-payment split appears in it. `group ordering` occurs zero times across the whole corpus; the single `group order` hit is a 2021 article about ordering Modifier Groups on a menu. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Not an absence-based verdict: it rests on the Online Ordering closed feature enumeration, whose anchors Multi-Touchpoint Ordering and Discovery Platform are present under all three instruments. Supporting controls over the cited PDF: group ordering 0/0/0, group order 0/0/0, shareable cart 0/0/0, split the bill 0/0/0. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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

Two components of the claim are documented, the central one is not. Customer Accounts on the POS "are a way to extend temporary credit to diners. For example, you cater your local city hall's weekly council meeting. Instead of charging the city each time for the order, you agree to settle up at the end of the month and bill it, instead, to a Customer Account. You can also use accounts to log a deposit against a future order (a catering job) or event at your venue (a wedding)", closed to via Pay on Account at checkout, with an Accounts Report and Detailed Account Report covering charges, payments and deposits. Lead time and minimums exist on the digital side: Pickup Wait / Delivery Wait, Allow Scheduled Orders with a Schedule Days in Advance limit, and a per-delivery-boundary minimum spend (maximum $1,000). SHORTFALL: there is no distinct catering ordering flow. No separate catering menu, no catering-specific minimums or lead-time rules, no quote or proposal step, no online deposit capture and no ACH terms are documented; the house account, its deposits and its monthly invoicing are manual POS-side operations, not a guest-facing catering portal. https://help.touchbistro.com/s/article/customer-account-list?language=en_US · retrieved 2026-08-06

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

No native voice product and no named voice partner. The 2026 Product Guide's table of contents enumerates the whole suite — POS, TouchBistro One, Payments, Customer Facing Display, Inventory Management, Labor Management, Kitchen Display System, Profit Management, Online Ordering, Loyalty, Marketing, Gift Cards, Reservations, Integration Partners, Hardware — and contains no voice or telephony product. `voice AI` and `AI voice` occur zero times corpus-wide. The three `voice ordering` hits are TouchBistro's own industry survey reporting what restaurants in general deploy, not its product. FLOOR NOTED: the integrations catalogue is framed "TouchBistro integrates with a variety of best-in-class software and payment partners" and its App Marketplace is behind a customer sign-in, so an unlisted partner cannot be excluded; the verdict rests on the product-suite enumeration and on the absence of any published integration path. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Not an absence-based verdict: it rests on the table of contents enumerating the whole product suite with no voice or telephony product, and that table of contents extracts intact under all three instruments. Supporting controls over the cited PDF: voice AI 0/0/0, AI voice 0/0/0, voice ordering 0/0/0. POISON PUBLISHED: the bare control voice reads 0 tokenised but 6 squashed, all 6 being invoice or invoices, and the bare control AI reads 0 tokenised but 70 squashed, all substrings of ordinary words. The published FLOOR about the customer-signin App Marketplace is unchanged. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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

digital-drivethru-ai

There is no drive-thru order type at all, so no AI voice lane can be integrated with it. The current KDS article states the boundary affirmatively: the ticket Order Type list "Options include order types TouchBistro doesn't itself generate like Drive Thru or Curb Side." Drive Thru is present nine times and was read: in the KB it is only ever an example of a free-text Takeout Type a manager types in so kitchen staff treat a ticket differently, and the rest are industry blog posts. `voice AI` and `AI voice` occur zero times corpus-wide, and the 2026 Product Guide's suite enumeration contains no drive-thru or voice product. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. https://help.touchbistro.com/s/article/Using-TouchBistro-KDS-Powered-by-Fresh?language=en_US · retrieved 2026-09-10

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

digital-sms-ordering

No conversational SMS or chat ordering channel exists. The 2026 Product Guide's Online Ordering feature list is website, social channels and the TouchBistro Dine page; its Marketing page describes the campaign channels as email and in-app only ("automate your email and in-app campaigns"). `text-to-order`, `SMS ordering` and `text message ordering` occur zero times corpus-wide. SMS is present 114 times on product surfaces and was read: it is Reservations booking confirmations and payment-terminal SMS receipt links, never an inbound ordering channel. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Not an absence-based verdict: it rests on the positive statement that the Marketing channels are email and in-app, and on the Online Ordering channel enumeration; both extract intact under all three instruments. Supporting controls over the cited PDF: text-to-order 0/0/0, SMS ordering 0/0/0, text message ordering 0/0/0. SMS itself is present 3 times under all three instruments and was read: all three are TouchBistro Reservations Two-Way SMS and Email Communication, booking communication, never an inbound ordering channel. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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

Ordering through the Google Business Profile is documented; the preferred-placement half is asserted only on a feature page. The 2026 Product Guide describes Online Ordering as letting diners "order directly through your restaurant's website, Google My Business profile, social media channels, and TouchBistro Dine", so the direct ordering link IS provisioned to the Google profile as an ordering option rather than leaving marketplace links as the only choice. SHORTFALL: the stronger half of the claim rests on a single product/feature page, where the DoorDash Online Ordering product lists "Order with Google" and glosses it "Set Online Ordering as your preferred ordering method on Google to maximize commission-free* online orders." — a vendor assertion with no operator documentation behind it: the current 861-article KB contains no article on provisioning the Google profile, so the preferred-placement mechanics cannot be confirmed. Downgraded from a drafted yes for that reason. (Preferred by Business is the claim wording, not the vendor page wording.) https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-10

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

`Apple Business Connect` occurs zero times across the whole 3,321-document corpus, as does `Apple Maps` on every product surface (its single hit is an industry blog post). The 2026 Product Guide enumerates the Online Ordering channels as the restaurant website, the Google My Business profile, social media channels and TouchBistro Dine; Apple Maps is not among them, and the complementary Google placement IS published by name (see digital-google-order), which is why the omission reads as a real gap rather than an unmentioned capability. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Controls as measured over the cited PDF by all three instruments: Apple Business Connect 0/0/0, Apple Maps 0/0/0. The contrast that carries the verdict survives the same instruments: Google My Business is present once in all three, so the complementary Google placement is published by name while the Apple one is not. The bare word Apple is present 7 times in all three and was read: Apple iPad hardware and Apple Pay acceptance, never a Maps or Business Connect listing. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 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

"Customers can earn and redeem rewards when placing orders in venue or online", with Loyalty integrating directly into Online Ordering under one guest identity. Requires both paid add-ons. https://www.touchbistro.com/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

TouchBistro Cloud has a Guest Engagement | Promotions | Subscriptions screen that takes a MoonClerk API key. Recurring payment forms are built in MoonClerk (Frequency = Recurring, with Recurring Period, Recurring Day and Duration, and an optional upfront one-time sign-up amount; "For multiple subscription levels, create a separate form for each level"). On sign-up "an account will be created automatically in TouchBistro Marketing using the Name, Email, and Phone Number that was entered in the MoonClerk Form", and five subscriber lifecycle tags - Pending, Active, Past Due, Unpaid, Canceled - are written into the CRM and are filterable, so operators "can then set up a filter to market promotions to customers with an Active tag". MoonClerk's Payer Portal can be configured to let diners pause, resume and cancel. SHORTFALL: billing, plan definition, the payment form and the subscriber portal all live in a separate third-party MoonClerk account the operator signs up for and funds; TouchBistro holds only the API key and the status tags, tag sync lags roughly 24 hours, and there is no entitlement engine - no automatic delivery-fee waiver, per-period item grant or paid loyalty tier - so the member benefit must be delivered manually by sending promotions to the Active tag. https://help.touchbistro.com/s/article/moonclerk-integration?language=en_US · retrieved 2026-08-06

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

Parity is explicitly broken for one promotion type and holds for the others. Menu Management Promotional Pricing (scheduled percentage/dollar-discount promotions and fixed-price promotions - happy hour, $5 lunch apps): "Promotions are only applied at the point of sale. They will not be applied if a diner is using your TouchBistro Online Ordering site." What does carry across channels: Menu Management Discounts render online - the diner Order screen "will display any automatic menu item discounts (1) as well as any automatic bill discounts (2)" and the Checkout screen shows both plus "any Promo Code discount (3) entered by the diner" - and Loyalty rewards defined once under Guest Engagement | Rewards are redeemable at the POS and on the ordering site ("If you see Loyalty Rewards, this means your Online Ordering page is linked to your Loyalty account and diners can claim rewards"). Channel eligibility control exists at menu-object level: when picking reward-applicable groups/items, "Menu groups or items found will indicate if they have been made available for online ordering. If you see In-Venue Only, the category or menu item will not be offered as part of a reward to diners ordering online." https://help.touchbistro.com/s/article/Menu-Management-Promotions?language=en_US · retrieved 2026-08-06

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

Operators can import guest CSVs into the CRM and export reports, but no documented bulk guest-record export. The Merchant Terms grant TouchBistro a perpetual irrevocable licence over Merchant Content and outright ownership of aggregated deidentified data. https://www.touchbistro.com/terms-of-service/ · 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

The published-compliance conjunct fails. `PCI DSS`, `Attestation of Compliance`, `3-D Secure`, `3DS` and `strong customer authentication` all occur zero times across the whole corpus, so no PCI DSS 4.0 position — and specifically no client-side script-integrity statement — is published anywhere. What is published attributes compliance to the processors ("our trusted, PCI-compliant payment processors") and describes the security feature only as end-to-end data encryption. The checkout mechanics are partly favourable — a 2021 online-ordering article has the diner entering card details on the TouchBistro-hosted ordering page and states "Payment details are never saved between orders" — but the claim is a conjunction and its compliance half is unpublished. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Controls as measured over the cited PDF by all three instruments: PCI DSS 0/0/0, Attestation of Compliance 0/0/0, 3-D Secure 0/0/0, 3DS 0/0/0, strong customer authentication 0/0/0, tokenization 0/0/0. POISON PUBLISHED: SCA reads 0 tokenised but 13 squashed, every one a fragment of scan or of diners can and orders can; and a proximity probe for 3-D Secure returns a single hit that is the page number 3 followed by the unrelated word securely. Neither is a compliance statement. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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

Digital channels get one configurable fee, not the POS fee set. Online Ordering | Delivery supports a per-boundary delivery fee that is "a fixed dollar fee or click Switch to Percentage to charge a delivery fee based on the bills subtotal (before tax/tips)", with a pre/post-discount basis selector and an "Is this fee taxable?" control that assigns a specific tax; guest-facing disclosure is fixed - the internal name is hidden and "All fees will be identified as 'Delivery Fee'" to the diner. SHORTFALL: the POS-side mechanisms have no documented online counterpart. Service Charges are created and applied on the POS Checkout screen (12.0.0+), and both documented cash-discounting/dual-pricing methods are POS discounts applied by tapping Discount/Comp All Items or by a Menu Management discount surfaced on the POS tender screen, while the Online Ordering Advanced Settings screen exposes only Offer Cutlery, Offer Tip, Allow Scheduled Orders, Calorie Contextual Statement, Order Throttling and Checkout as Guest. No card-surcharge configuration, no jurisdiction restriction handling and no card-brand exclusion logic is documented for any channel. https://help.touchbistro.com/s/article/touchbistro-online-ordering-merchant-settings?language=en_US · retrieved 2026-08-06

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

CRM "tracks data across both in-venue and online channels" capturing visit frequency, average spend, order history and birthdays. Dedup/merge behaviour on phone or email match is not documented, and there is no kiosk channel. https://www.touchbistro.com/loyalty/ · retrieved 2026-08-01

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

guest-loyalty-thirdparty-identity-attach

CLAIM: marketplace orders (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. VERDICT: partial. Marketplace orders are NOT anonymous tickets - TouchBistro carries the diner's name and phone onto the order - but nothing attaches them to a Guest Engagement CRM profile. EVIDENCE (identity carried): 'DoorDash Online Ordering - Understanding the Server Experience' (https://help.touchbistro.com/s/article/DoorDash-Understanding-the-Server-Experience?language=en_US) tells the server to review 'Pickup or Delivery / Need to pack cutlery/condiments. Name of the intended diner.' and its Receipt and Kitchen Ticket table (Item | Location, read from raw HTML cells, not a contiguous quote) maps 'Intended Diner Name' -> 'Ticket, Receipt' and 'Diner Phone Number' -> 'Receipt'. That this is the MARKETPLACE integration: 'Integrating with DoorDash' (https://help.touchbistro.com/s/article/doordash-Integrating?language=en_US) says 'This integration requires an existing DoorDash Merchant account with Marketplace enabled' and names the App Marketplace product 'DoorDash Online Ordering'. The prior note read only the sibling 'DoorDash Marketplace - Understanding the Server Experience' article, which describes the order tile (logo + DoorDash order ID) and omits the ticket table. Aggregated channels corroborate (grade D, third party): Deliverect's 'TouchBistro: Accept online orders on your POS' (https://help.deliverect.com/en/articles/7979285-touchbistro-accept-online-orders-on-your-pos-manual-and-auto-accept) lists 'Information TouchBistro displays from orders' incl. 'Customer's name' and 'Customer's phone number and delivery address' for Uber Eats/DoorDash orders, and its TouchBistro settings page offers 'Anonymize customer data (GDPR) ... Update the customer's name to "Anonymized" once the order is finalized by TouchBistro'. SHORTFALL (no profile attach): the CRM guide (https://help.touchbistro.com/s/article/touchbistro-loyalty-guest-reporting?language=en_US) defines the Guest List tab as 'Here you will see all guests who have redeemed a reward or checked in' - a marketplace order does neither; across the 783 en_US articles of the live 861-loc KB (sitemap-topicarticle-1.xml, bodies via Aura Knowledge__kav.Process_Steps__c, 783/783 retrieved) no DoorDash article mentions loyalty, CRM, Guest Engagement, reward or guest profile, and no regex hit ties online/third-party/marketplace/DoorDash/Deliverect/UrbanPiper/Uber orders to CRM or the guest list (the only online-to-loyalty path is TouchBistro's OWN Online Ordering Loyalty integration). The shortfall is stated from a definition plus absence, so it is partial not no. Retrieved 2026-09-16. https://help.touchbistro.com/s/article/DoorDash-Understanding-the-Server-Experience?language=en_US · retrieved 2026-09-16 adversarially verified

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

Points tied to guest spend and items purchased is documented, with customizable rewards including BOGO. A second distinct model (visit/punch count or spend tier) is not documented. https://www.touchbistro.com/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

Guest Engagement | Loyalty Programs | Create New offers exactly two program types. The Spend-Based dialog's complete field set is Name, Status, Points Per Dollar, Description, Venues and Schedule. The Item-Based dialog's complete field set is Name, Status, Number of Times Each Individual Item Can Be Claimed, Claim Limit Per Day for ALL Items, Description, Reward Milestone (an existing Reward unlocked at a set claimed-item count), Number of Claimed Item(s), Venues, Applicable Groups/Items and Schedule. Neither exposes a status level, a rolling-window spend or visit threshold, or any promotion/demotion mechanic; rewards are redeemed by spending a fixed Reward Points amount set per reward. The only tier-shaped constructs are manual operator work in the CRM - saved filters, the canned 'We Love You' filter, and operator-applied Tags (the vendor suggests tagging diners "as VIP") - none of which moves an account between statuses automatically. https://help.touchbistro.com/s/article/touchbistro-loyalty-managing-spend-based-loyalty?language=en_US · retrieved 2026-08-06

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

guest-loyalty-offline-behavior

TouchBistro publishes a Feature/Access table for internet loss, and redemption is documented as blocked: "Let customers claim loyalty rewards - No", alongside "Can use/purchase gift cards - No" and "Access online orders - No", while "Take/close orders on your TouchBistro POS - Yes", "Take cash payments - Yes" and "Take offline payments... Yes If you're using TouchBistro Payments (US) or Moneris (Canada)"; against the cloud-reporting row the table adds "TouchBistro will sync all sales/labor data when the Internet is restored". SHORTFALL: the table addresses reward claiming only. It states nothing about whether a guest's loyalty account can be looked up offline, and nothing about whether point accrual on bills closed offline is queued and applied on reconnect or simply lost - and the CRM's stated refresh cadence ("the data (spend, visits, etc.) on the CRM page updates every six hours") does not answer it. https://help.touchbistro.com/s/article/What-can-you-do-with-TouchBistro-POS-if-your-Internet-goes-down?language=en_US · retrieved 2026-08-06

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

guest-loyalty-offer-stacking-rules

The artefact that would carry the setting was opened and enumerated. The current Menu Management: Discounts reference (POS 12.0.0+) documents every field on a Discount: the three immutable Discount Types (Item, Bill, Cash), permissible items on an Item Discount, exclusions on a Bill Discount, a Min Spend restriction with non-qualifying groups, POS/Online Ordering availability, promo codes with start and expiry, and the three Apply Discount modes — "Automatically", "Manually" and "Promo Code". Nothing in it configures whether two discounts may both apply, which wins, or an order of application; `stacking` occurs zero times on any product surface. Precedence behaviour does exist and is not configurable: a loyalty article notes that where a guest qualifies both ways "the promotional offer supersedes it" — stated as fixed behaviour, not a rule the operator sets. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. https://help.touchbistro.com/s/article/Menu-Management-Discounts?language=en_US · retrieved 2026-09-10

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

Birthday targeting is built in; spend- and frequency-based segmentation is explicitly gated behind also purchasing the Loyalty and/or Online Ordering modules. Rules over items purchased are not documented. https://www.touchbistro.com/marketing/ · 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

Guest Engagement | CRM ships a Suggested Filters tab of "a number of 'canned' filters create by TouchBistro" that the operator runs without building any query. The documented set maps directly onto lifecycle segments: We Miss You - "Identify guests who have historically been big spenders, but haven't visited your restaurants recently" (lapsed/at-risk high value); We Love You - "Identify guests who visit frequently and/or have spent a lot recently" (VIP); New Guests - "Identify guests who recently visited your restaurant for the first time"; Birthdays - "Identify guests with a recent or upcoming birthday"; and Loyalty Club - "Identify guests who have made a certain amount of progress in your loyalty program". They run on recency/frequency/monetary data the platform maintains itself (Total Visits, Average Spent and Date Range columns on the Guest List, refreshed every six hours), and the resulting cohorts feed Promotions & Communications and Automated Marketing directly. https://help.touchbistro.com/s/article/touchbistro-loyalty-guest-reporting?language=en_US · retrieved 2026-08-06

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

Automated campaigns can be scheduled "once, weekly, monthly, or yearly" and birthday promotions are explicit. First-visit thank-you and lapsed win-back as shipped always-on automations are not documented. https://www.touchbistro.com/marketing/ · 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

Marketing sends drag-and-drop branded email and in-app messages natively. SMS marketing is not documented as a Marketing capability — SMS appears only for reservation reminders and two-way reservation messaging. https://www.touchbistro.com/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 and revocable, but it is a single flag. "The CRM has an Email opt-in column that indicates the diner's consent status"; diners opt in at the Online Ordering checkout screen and on login to the Customer Web App ("The diner can click Skip to not opt-in but will be prompted again next time the diner logs into the Customer Web App"); and "Only diners who have opted in can receive email marketing offers you generate via the Marketing features", which is enforced at send time - a filter returning 10 diners shows "Send to 3 Guests" when only 3 have opted in. Revocation is honoured by two means, not just a keyword: the SendGrid-generated email carries an unsubscribe link and "Their CRM opt-in status should be then updated within 24 hours", and staff can opt a diner out on their behalf from the CRM - "You cannot use this to opt-in a diner. However, if you click on the checkmark, you can help a diner opt-out." SHORTFALL: it is one email opt-in boolean. There is no per-channel consent (the MoonClerk sign-up form's marketing checkbox writes the same email_marketing_consent key, and in-app messaging has no separate consent), and no consent timestamp and no source-of-consent field appear in any documented CRM column. https://help.touchbistro.com/s/article/touchbistro-loyalty-guest-reporting?language=en_US · retrieved 2026-08-06

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

guest-loyalty-10dlc-registration

`10DLC`, `10-DLC` and `A2P` occur zero times across the whole 3,321-document corpus, so no brand or campaign registration is handled or documented. The precondition mostly does not arise: the 2026 Product Guide's Marketing page describes the channels as email and in-app only, listing Email Marketing, Campaign Automation and a Customer Web App and no SMS feature. TouchBistro does publish an SMS Terms of Service naming a short code, but it is TouchBistro's own prospect marketing list, not an operator guest channel: "When you text JOIN to 31929, TouchBistro will send you a message to confirm your signup." (A short code is also not the long-code A2P route 10DLC governs.) The one operator-facing SMS in the suite is Reservations booking communication. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Controls as measured over the cited PDF by all three instruments: 10DLC 0/0/0, 10-DLC 0/0/0, A2P 0/0/0, short code 0/0/0. The precondition evidence survives the same instruments: the Marketing enumeration anchor Campaign Automation is present in all three and the module lists no SMS feature, and the only SMS in this file is the Reservations Two-Way SMS and Email Communication entry, present 3 times in all three. The short-code quote cited in the note is from the separate SMS Terms of Service, not this PDF, and is correctly attributed there. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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

guest-loyalty-campaign-attribution

Open and click-through rates are monitored and promotion redemption is tracked "to figure out what works." Tying redemptions to actual check totals or incremental sales is not documented. https://www.touchbistro.com/marketing/ · retrieved 2026-08-01

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

Self-serve export exists and carries PII. In Guest Engagement | CRM, after any search or filter, "Click Export if you want to export this search as a CSV file" - no support ticket, no fee - over a guest list carrying name, email, phone, Total Visits and Average Spent, with an adjustable Date Range. Reports | Guest Engagement adds three further downloads ("These reports are download only as CSV files") open to Admin or Analyst: Reward Redemption (Redemption ID, Timestamp, Redemption Type, Points, Reward Name, Diner Name/Email/Phone, Venue ID, Restaurant Name/Address), Point Earnings (Earned ID, Guest Name/Email/Phone, Points Earned, New Point Balance, Date and Time, Venue) and Claimed Items (guest identity, program name, menu item, venue, time and date). SHORTFALL: what is exportable is the guest list plus loyalty point, redemption and claimed-item events. No export of each guest's underlying order or spend transaction history is documented - the CRM holds only aggregates (Total Visits, Average Spent) and the Point Earnings rows carry points and balances, not bill totals or line items - and TouchBistro publishes no guest or CRM API. https://help.touchbistro.com/s/article/touchbistro-loyalty-guest-reporting?language=en_US · retrieved 2026-08-06

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

Post-dining surveys and customer feedback collection are documented (Marketing and Reservations). Score-based routing to private recovery vs public review sites is not. https://www.touchbistro.com/marketing/ · retrieved 2026-08-01

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

No guest referral mechanic. The 2026 Product Guide's Loyalty page answers "What features are included?" with POS Integration, a CRM platform, Custom Loyalty Programs, Customer Web App, Cloud Reporting, Marketing Integration, Online Ordering Integration and Multi-Location Functionality — no referral codes, no attribution of a referred guest's first order, no two-sided reward. THE WORD IS A TRAP AND WAS MEASURED: referral occurs in 44 product documents and every one is TouchBistro's own merchant-acquisition bounty for referring a restaurant to TouchBistro, stated in the same Product Guide as "you'll earn $1,000 USD for each referral who becomes a TouchBistro customer", plus a set of ISO/reseller referral landing pages. The published terms of that programme settle whose programme it is: /referrals-tnc/ makes ineligible "Restaurant owners, operators, franchisors and business decision makers referring restaurants which they own, operate or are responsible for making POS purchasing decisions" and requires participants be 18 or over and resident in Canada or the U.S. That is a channel programme, not a guest feature. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Not an absence-based verdict: the control word is present and was read, and the verdict rests on the published terms establishing whose programme it is. Measured over the cited PDF by all three instruments: referral 2 tokenised in both extractions and 3 squashed, referrals 1 in all three, and every hit is the merchant-acquisition bounty quoted in the note. The Loyalty enumeration anchor Custom Loyalty Programs is present under all three instruments, so the closed feature list was read intact. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 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

`Apple Wallet`, `wallet pass` and `PassKit` occur zero times across the whole corpus, and `Google Wallet` occurs zero times on every product surface (its three hits are industry blog posts and a 2014 press release about NFC payment acceptance, not a loyalty pass). The vendor ships a different answer to the same problem and names it in the Loyalty feature list: a Customer Web App, described as "Create a custom-branded web app for your guests that allows them to earn, redeem, and track their rewards from their own devices." A branded web app is not a wallet pass and carries no push-updatable balance. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Controls as measured over the cited PDF by all three instruments: Apple Wallet 0/0/0, wallet pass 0/0/0, PassKit 0/0/0, Google Wallet 0/0/0. The bare word wallet is present 2 times tokenised and 3 squashed and was read: it is digital wallet payment acceptance at the terminal, not a loyalty pass. The positive alternative that carries the verdict survives the same instruments: the Customer Web App quote about guests earning, redeeming and tracking rewards from their own devices is present in all three. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 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

No operator-side tooling. The Privacy Notice routes rights requests to TouchBistro rather than to an operator console — "If you would like us to remove you from our contact list or exercise your rights related to your personal information, you can make a request to us using the contact details as provided in the" How to Contact Us section — and its Right to Delete text has TouchBistro reviewing the request and directing "our service providers to take similar action", with Merchants described as "independent third parties that maintain their own business practices". On the operator surface the current KB's Guest Engagement articles document only Add/Remove Points and Add/Remove Claimed items against a guest looked up by email or phone; no delete-a-guest or export-a-guest operation is documented, and `DSAR` and `access request` occur zero times corpus-wide. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. https://www.touchbistro.com/privacy-notice/ · retrieved 2026-09-10

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

An audit trail and several caps exist; approval and self-redemption flagging do not. Audit trail: the Reward Redemption CSV records Redemption ID, Timestamp, Redemption Type, Points spent, Reward Name, Diner Name/Email/Phone and venue for every redemption, and Point Earnings records Earned ID, Points Earned, New Point Balance and Date/Time per accruing transaction. Caps: item-based programs configure "Number of Times Each Individual Item Can Be Claimed" and "Claim Limit Per Day for ALL Items", promotions configure Quantity Per User (or Unlimited) and # Days Until Expiration, and rewards carry day/time availability windows and prohibited menu groups. Access to manual adjustment is role-gated - "Guest Engagement can only be accessed by a person with an Admin account or a person given a Guest Engagement account." SHORTFALL: the manual Add/Remove Points and Add/Remove Claimed adjustments carry no documented approval step and no documented audit record of who adjusted what and when; there is no per-guest redemption velocity limit; and there is no employee self-redemption flag - TouchBistro's documented substitute is manual inspection, "The Discount Details report does record which server processed the reward, which can give you some insight into odd redemption activity centered around a particular server." https://help.touchbistro.com/s/article/How-to-View-Guest-Engagement-Reports?language=en_US · retrieved 2026-08-06

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

Neither guest-engagement module offers a recommendation engine. The 2026 Product Guide's Marketing feature list is POS Integration, Custom Promotions, Email Marketing, Campaign Automation, Customer Web App, Cloud Reporting, Loyalty Integration and Online Ordering Integration; the Loyalty list adds a CRM and Cloud Reporting. Automation there is scheduling and segmentation, not model-suggested offers. `suggested offer` occurs zero times corpus-wide. VERIFIED AGAINST MYSELF: machine learning is NOT absent from the product surface — it appears on two vendor-published partner-offer pages — but in both it is the 7shifts package feature "Machine learning auto-scheduler", a labour-scheduling capability of a partner product, not offer selection in Loyalty or Marketing. The four product-surface AI hits likewise carry no offer-selection function. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Controls as measured over the cited PDF by all three instruments: suggested offer 0/0/0, machine learning 0/0/0, artificial intelligence 0/0/0. POISON PUBLISHED, AND A NEAR-MISS THAT MUST NOT BE RE-AUDITED AS A FINDING: a word-boundary control on the singular recommendation reads 0, but the plural IS present once under all three instruments, in the Reservations module, not in Loyalty or Marketing - "Direct integration with the TouchBistro POS allows you to track your guests order history so staff can offer personalized recommendations and upsell with ease." That is a human server reading order history at the table, with no model, no offer object and no automated selection, so it does not meet the claim; it is recorded here because a singular word-boundary control scatters it and a future pass would otherwise rediscover it as new. Separately the bare control AI reads 0 tokenised but 70 squashed, every one a substring of an ordinary word such as available, email and detail. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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

Gift cards are first-party, physical and digital, and redeemable at any location of the brand. Whether balances are tied to the same guest/loyalty profile is not documented. https://www.touchbistro.com/gift-cards/ · retrieved 2026-08-01

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

"Enter the passcode. Tap the green checkmark or Clock In | Clock Out." Passcodes are four digits, generated per staff member and unique to the venue; a QR-code login is offered as an alternative ("tap the QR code icon at the top right and image your assigned code"). Clock-in also works from the floor plan screen. No separate time-clock hardware appears anywhere in the flow, and a Clock In/Clock Out Only permission exists for staff who should do nothing else on the POS. https://help.touchbistro.com/s/article/How-Do-I-Clock-In?language=en_US · retrieved 2026-08-08 adversarially verified

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

No photo or biometric capture at punch. `facial verification` occurs zero times corpus-wide and `facial recognition` occurs zero times on every product surface (all six hits are industry blog posts). The 2026 Product Guide's Labor Management "What features are included?" list is POS Integration, Scheduling, Employee Management, Forecasting, Team Communication, In-Depth Reporting and Multi-Location Staff Management — no time-clock verification entry. Clock-in itself is a POS action and the current KB article documents its methods exhaustively as a manager-issued passcode, the floor plan, or a staff QR code ("If your venue uses a QR code login, tap the QR code icon at the top right and image your assigned code") — an identity token, not a photo or a face. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Not an absence-based verdict: it rests on the current KB documenting the clock-in methods exhaustively as passcode, floor plan or staff QR code, which is a closed enumeration on a different document, plus the Labor Management closed feature list here whose anchor Team Communication is present under all three instruments. Supporting controls over the cited PDF: facial verification 0/0/0, facial recognition 0/0/0, biometric 0/0/0, fingerprint 0/0/0. The word photo is present 1 time tokenised and 2 squashed and was read: it is displaying photos of menu items on the Customer Facing Display and photographing an invoice for Profit Management, never a punch-in capture. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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

TouchBistro's internet-outage Feature/Access table states, against the cloud-reporting row, "TouchBistro will sync all sales/labor data when the Internet is restored", while taking and closing orders, cash payments, offline card payments, kitchen tickets and KDS all remain Yes - consistent with the POS running on the local iPad or Mac main device where clock-in is a passcode action. SHORTFALL: clock-in/clock-out is not itself a row in the table, so punch capture during an outage is inferred from the labor-data sync statement rather than stated; the same table sets "Manage staff - No... This feature is available if you are using the legacy POS-based platform", meaning manager-side staff and shift administration is unavailable during an outage on the cloud-based platform; and no document anywhere describes duplicate suppression, conflict resolution or loss handling when punches reconcile on reconnect. https://help.touchbistro.com/s/article/What-can-you-do-with-TouchBistro-POS-if-your-Internet-goes-down?language=en_US · retrieved 2026-08-06

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

Cloud-based platform: "You can, if you wish, create and name additional roles by clicking Add Role", and when editing a role you "define the role's name, default pay, and, if you are multi-location, specify which venues this role is valid at". Permissions are grouped by POS, Cash Deposit, Staff, Devices, Menu, Reports, Floor Plan, Manage Settings & Venue Details, App Marketplace and Reservations, each an individually toggled line - Can Authorize and Perform Voids without Approval, Can Authorize and Perform Discounts without Approval, Can Open Cash Drawer, Can Refund Closed Bills, Can Perform Pay-Ins/Pay-Outs, POS Administrative Access, and so on. The POS-based platform equivalent (Staff Types) is likewise per-action across General, Payments, Staff and Manager sections, including Can Manage Menu, Can Manage Shifts, Can Access All Reports and a Pay In/Out Max Value ceiling. Canned roles exist but are not the limit. https://help.touchbistro.com/s/article/Staff-Permissions?language=en_US · retrieved 2026-08-08 adversarially verified

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 are attributed to the individual approver and are queryable after the fact from Cloud over a chosen date range: Sales | Void Detail Reports and Sales | Discount Details Report both carry an Authorized By column alongside Server name, Bill Number and Date | Time; Labor | Deleted Items Report's detailed view pairs "Server - Name of the server" with "Manager - Name of the manager who approved"; Labor | No Sale Report pairs Server Name with Manager and a Date/Timestamp. Shortfall: nothing documents the trail as immutable, and the Audit | Reopened Bills report shows the opposite is possible - "using the reopen feature will delete the bill from your system and any integrated payment information associated with it", with the report noting the reopened bill "will no longer exist in the system". https://help.touchbistro.com/s/article/Index-of-Cloud-Reports?language=en_US · retrieved 2026-08-08 adversarially 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

Native scheduling in the Labor Management add-on is asserted only on the vendor feature page: "Quickly and easily build staff schedules based on forecasted demand and instantly share those schedules back with your team", plus "a centralized solution for managing availability, schedule changes, time off requests, and blocked dates." Shortfalls: it is a separately-quoted add-on, not part of the $69 POS tier; "TouchBistro Labor Management is currently available to restaurants in Canada (excluding Quebec) and the continental United States" only; and the one piece of actual product documentation, the knowledge-base article "TouchBistro Labor Management: Basics of Labor Scheduling", is behind a customer login (help.touchbistro.com returns the Salesforce login form, not the article body), so shift-level scheduler behaviour cannot be independently confirmed. No evidence found that a third party powers it. https://www.touchbistro.com/labor-management/ · retrieved 2026-08-02 adversarially verified

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

Verified: "Accurately predict your staffing needs" driven by labor percentage, hours, costs or employee count against net sales or guest count, with POS data flowing "every 15 minutes." Native, not partner-powered. Marketing-page claim level; paid add-on; "Canada (excluding Quebec) and the continental United States" only. https://www.touchbistro.com/labor-management/ · retrieved 2026-08-01 adversarially verified

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

"Real-time labor cost reporting and overtime tracking" is claimed, but Labor Management ingests POS data only every 15 minutes, so it is near-real-time at best. https://www.touchbistro.com/labor-management/ · retrieved 2026-08-01

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

Staff | Staff Settings | Overtime Rules enumerates the entire overtime feature - Weekly Overtime (Payout Period), Daily Overtime (Shift Part 1), Doubletime (Shift Part 2) and Spread of Hours - and states their purpose outright: rules are set up "for calculating overtime pay for the Timesheet Details and the Timesheet Summary report". Every rule is a pay multiplier applied after the fact; none produces an alert. The clock-in guide enumerates the POS clock-in flow and documents exactly one interruption, and it is scheduling rather than overtime: "If you receive an error like the one below, you are not scheduled to clock in at that day or time... You will be prompted to seek a manager confirmation." So the machinery to stop a clock-in exists and is wired to the schedule, not to an overtime threshold. Caveat: the separately sold TouchBistro Labor Management scheduling guides are now behind a login and could not be read. https://help.touchbistro.com/s/article/Staff-Overtime-Rules?language=en_US · retrieved 2026-08-08 adversarially verified

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

Vendor statement of absence in the Breaks guide: "TouchBistro does not restrict breaks based on time worked. For example, if a staff member is eligible for a meal break after 6 hours of work and the staff member has only worked 5 hours, TouchBistro will still make any and all configured break options available to the staff member." The whole Break Type configuration surface (Admin | Admin Settings | Staff | Break Types | Add) is Name, Duration and a Paid Break toggle - no jurisdiction selector, no eligibility threshold, no waiver and no attestation prompt; the guide opens "The information here is not to be taken as legal advice. Refer to your local employment labour laws before you proceed." Break output is descriptive only: a Break Details report listing breaks taken and by whom, plus Unpaid Break (Reg./OT1/OT2 Hrs) columns on Timesheet Details and Timesheet Summary. No missed-break or premium-pay flag exists in the enumerated eleven-report Cloud Labor Reports set. The only per-jurisdiction pay rules TouchBistro implements are on Staff | Staff Settings | Overtime Rules - weekly overtime, daily overtime (Shift Part 1), doubletime (Shift Part 2) and New York Spread of Hours - none of which is a meal or rest break rule. For scheduling-side breaks the vendor defers to a third party: "7shifts will then apply preprogrammed breaks to Susan's full time between clock-in and clock-out." https://help.touchbistro.com/s/article/breaks?language=en_US · retrieved 2026-08-06

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

labor-minor-labor-rules

No minor-labor enforcement at scheduling or clock-in. `child labor` and `minor labor` occur zero times corpus-wide. THE WORD IS A TRAP AND WAS MEASURED: minor occurs in 11 product documents and every current-KB hit is the TouchBistro Reservations seating flag, not a labor rule — "Enable this if you want to prompt diners to indicate if a particular guest is a minor. If enabled and the diner indicates one or more guests are a minor, TouchBistro Reservations will not offer tables marked" as Adult Only to that party. The 2026 Product Guide's Labor Management feature list carries no compliance or age-rule entry, and its Scheduling description is availability, schedule changes, time-off requests and blocked dates. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Controls as measured over the cited PDF by all three instruments: child labor 0/0/0, minor labor 0/0/0, labor law 0/0/0, compliance 0/0/0, and the bare trap word minor is 0 under all three instruments in this file, so the 11 documents carrying it are elsewhere in the corpus and the Reservations seating-flag reading quoted in the note is unaffected. The Labor Management closed feature enumeration was read intact, its anchor Team Communication being present under all three instruments, and it carries no compliance or age-rule entry. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · 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

One rule-based tip-out is computed automatically; there is no pool distribution engine. Admin | Admin Settings | Menu | Gratuity Settings exposes Calculate Credit Card Tip Out, a custom Tip Out Display Name for the End of Day report, and a single Tip Out Amount (%) applied to credit card tips - "The Tip Out Amount (%) can also be used to represent the Credit Card merchant fee for jurisdictions that allow this fee to be withheld from tips." The withholding accrues per server without manual work and rolls up automatically: "When you close your day, as a manager or Admin, you will see the total tip out amount accrued from all servers in your End of Day report", with per-staff CC Tip Out to House columns on the Staff Performance and Tips by Payment Method reports. The same screen configures Auto Gratuity (Minimum Party Size, Default %, Gratuity Name, Gratuity Mode, pre/post-discount calculation). SHORTFALL: the only configurable basis is a flat percentage of credit card tips withheld to the house - "The tip out withholding does not calculate on cash tips" - with no allocation of that pool onward to other employees by hours worked, points, role or percentage of sales, and the vendor treats redistribution as the operator's problem outside the system: "You should consult your accountant about any tax implications that may arise in your jurisdiction when the house manages a tip pool." https://help.touchbistro.com/s/article/gratuity-settings?language=en_US · retrieved 2026-08-06

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

The receipt and contribution sides are retained per employee per shift and are exportable; the distribution side does not exist. Staff Performance carries, per staff member, Credit Card Tips, Cash Tips ("If the server's staff type is set to require cash tip reporting, the cash tips the server reports at his/her shift end are reported here"), Total Tips, Gratuity, Tip %, CC Tips Owed to Server and CC Tip Out to House ("If you set up a tip 'claw back', the amount of server tips clawed back by the house"). Tips by Payment Method breaks the same figures down by tender. Shift Details and Timesheet Details tie every row to a named staff member, staff type, date and clock-in/clock-out time. iPad reports export by CSV or email or print, and "If 'Tip Out to House (% of Credit Card Tips)' is enabled, the amount owed to the house will be shown on the report"; a per-staff shift report is reprintable from the Staff List (View Shift Report, Print or Email). SHORTFALL: because there is no pool distribution engine, no report records amounts distributed out of a pool to individual employees - the audit trail ends at what each employee received and what was clawed back to the house. https://help.touchbistro.com/s/article/labor-reports?language=en_US · retrieved 2026-08-06

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

Cash and charged tips are separated per employee; the tax-year-2026 statutory fields are absent. Staff Performance reports Credit Card Tips and Cash Tips as distinct columns - cash tips being what the server declares at shift end where the staff type requires cash tip reporting - plus Total Tips and a separate Gratuity column used where auto-grats are configured to be treated differently from tips; Tips by Payment Method splits tips by tender; Timesheet Details and Timesheet Summary carry the wage side (regular, OT1, OT2, payout-period OT, Spread of Hours, Gross Pay). SHORTFALL: no Treasury tipped-occupation code exists in any documented staff profile, staff type or report column, and neither W-2 Box 12 code TP nor Box 14b appears in any of the eleven enumerated Cloud labor reports or in the iPad CSV/email exports. Payroll is not a TouchBistro product - the App Marketplace routes scheduling and payroll to 7shifts and Push Operations - and TouchBistro publishes no payroll export schema. https://help.touchbistro.com/s/article/labor-reports?language=en_US · retrieved 2026-08-06

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

The App Marketplace article is the vendor's own complete list of what can be attached to TouchBistro, organised by category, and it names each first-party product explicitly (TouchBistro Reservations, TouchBistro Loyalty, TouchBistro Marketing, TouchBistro Digital Gift Cards, TouchBistro Profit Management). There is no Payroll category; the nearest is "Scheduling", whose only entries are 7shifts and Push Operations, and "Accounting", whose entries are TouchBistro Profit Management, Shogo and DAVO. TouchBistro's own labor surface stops at timesheets and gross pay: the Labor reports enumerate Break Details, Hourly Labor Cost, Hours Summary, Labor Cost Analysis, Shift Details, Timesheet Details and Timesheet Summary, ending at Gross Pay with no tax withholding, filing or direct deposit. No first-party payroll product, tax filing or direct deposit is documented anywhere in the help centre. https://help.touchbistro.com/s/article/chapter-11-integrations?language=en_US · retrieved 2026-08-06 adversarially verified

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

Two named partners exist (Push Operations, 7shifts) plus "payroll export functionality integrated with third-party systems." Direct Gusto, ADP, Paychex or Paylocity connectors are not named. https://www.touchbistro.com/features/integrations/ · retrieved 2026-08-01

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 trading and time-off request handling are documented in the employee mobile app. A manager approval workflow that enforces overtime and role eligibility is not documented. https://www.touchbistro.com/labor-management/ · 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

Labor | Staff Performance "helps you gauge staff performance using several different metrics" and reports per server: Net Sales, Bill Count, Order Count, Average Check, Guest Count, Guest Average, Avg. Table Turn Time (mins), Credit Card Tips, Cash Tips, Total Tips, Tip %, Void Amount ("the amount the server voided for the time period. A high void amount may indicate the server is making a lot of mistakes") and Discount Amount ("the dollar value of discounts issued by the server"). Void and comp exposure is also available as a rate at venue level via Sales | Void Summary Reports (Void % of Sales). Category attachment rate is the one metric family not offered per server. https://help.touchbistro.com/s/article/labor-reports?language=en_US · retrieved 2026-08-08 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

Recipe costing with per-dish profit margins is documented. Multi-level sub-recipes and automatic plate-cost recalculation on ingredient price change are not. https://www.touchbistro.com/inventory-management/ · 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

Each ingredient carries a Purchase Measure, a Cost Per Unit for that measure, and one or more Recipe Measures each with a Conversion Ratio ("the Recipe Measure contained in one unit of the Purchase Measure"); stock is counted in a selectable Measurement. Shortfall: there is no yield or waste percentage applied to raw-to-usable conversion - the Ingredient Consumption Report's Waste Quantity/Waste Cost are only voided items not returned to stock, not a yield factor. TouchBistro also flags this system as legacy: "as this functionality is no longer being actively developed, it is not available for all accounts", and it is unsupported for customers on the Menu Management menu tool. https://help.touchbistro.com/s/article/setting-using-touchbistro-ingredient-based-inventory-system?language=en_US · retrieved 2026-08-06

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

"Data-driven forecasting that takes your actual and ideal usage into account" implies a theoretical-vs-actual comparison exists, but a per-item variance report in units and currency for a defined count period is not documented. https://www.touchbistro.com/inventory-management/ · 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

Sales and menu data sync from TouchBistro POS every 15 minutes — better than an end-of-day batch, but not true real-time. Whether modifier selections drive depletion is not documented. https://www.touchbistro.com/inventory-management/ · 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

Automatic 86 at zero is documented: "the Out of Stock control is automatically enabled if stock count reaches zero", counts decrease when the item is sent to the kitchen (or when the bill closes, if nothing is sent to a printer), and a void returns stock "if the void has been set up to return to inventory". It propagates without publishing ("pushed to the venue immediately") to the POS Order screen, to TouchBistro Online Ordering ("will mark menu items that are out of stock as unavailable") and to DoorDash ("will hide menu items that are out of stock"), and it covers menu items used as modifiers. Shortfall, and it is the substance of the claim: Stock Availability is "a simplified inventory system for countable menu items (cans of pop, bottles of beer, number of bagels)" - depletion is per sellable item, not per component ingredient, and the guide warns against using it for anything sold by weight. A configured threshold does not 86: the Low Stock Indicator only warns ("the count will appear next to the menu item"; "the diner-facing online ordering pages will not show low status counts"). There is also no inventory report. https://help.touchbistro.com/s/article/Menu-Management-Stock-Availability?language=en_US · retrieved 2026-08-08 adversarially verified

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

Re-read verbatim 2026-08-11. The page says counts may be taken "by physical location in your venue" and "let multiple managers count at the same time", and its FAQ that "counts can be done by multiple people at the same time and across different areas within your venue" — so the concurrency is WITHIN one venue, across areas. The wording previously recorded here ("across different venue locations") was a paraphrase in quotation marks and read as cross-LOCATION counting, which TouchBistro does not claim; withdrawn. Counts are maintained as a digital database. Distinct full / spot / scheduled cycle count modes with separate variance history are still not documented, so the value is unchanged. https://www.touchbistro.com/inventory-management/ · 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

iOS and Android mobile apps are available for counting. Barcode/QR scanning and offline count capture with sync-on-reconnect are not documented. https://www.touchbistro.com/inventory-management/ · retrieved 2026-08-01

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

"Direct ordering from select vendors and purchase order creation" is documented, but no broadline distributors are named and no EDI invoice receipt is described. https://www.touchbistro.com/inventory-management/ · 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

TouchBistro's own Profit Management page: "Simply scan, email, or take a photo of your invoices and handwritten adjustments, and all the details will be captured and digitized in less than 48 hours." Shortfalls: this is a separately-subscribed add-on (an App Marketplace chicklet under Back of House; "Most integrations require you to register and arrange payment"), not part of the POS subscription; capture is not real time (stated turnaround under 48 hours, implying assisted transcription rather than inline OCR); and neither the core POS ingredient inventory nor TouchBistro Inventory Management documents any invoice ingestion. Evidence is a vendor feature page (grade C), not documentation of the extraction behaviour. https://www.touchbistro.com/profit-management/ · 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

The module has no invoice ingestion, so there is no per-item purchase price history to alert against. The 2026 Product Guide's Inventory Management "What features are included?" list has Suggested Ordering ("automated order suggestions for each vendor based on your restaurant's needs") and Recipe Costing, but no invoice capture, no received-price comparison and no threshold alert; `price alert` occurs zero times corpus-wide and the single `price change` hit is unrelated. Invoice processing and price alerts are a partner capability on this platform, not TouchBistro's: the integrations catalogue describes MarginEdge as supplying "automated invoice processing, food costing, digital recipe builder, price alerts, online ordering and bill pay", which is why the subject of any such alert is MarginEdge and not the POS. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Controls as measured over the cited PDF by all three instruments: price alert 0/0/0, threshold 0/0/0. POISON PUBLISHED, AND IT IS AN INSTRUMENT ARTEFACT THAT WOULD OTHERWISE LOOK LIKE A REFUTATION: the phrase price change reads 0 tokenised in both extractions and 0 squashed in no-flags, but 1 squashed in -layout. That single hit is manufactured by -layout welding three adjacent columns of the Customer Facing Display page - the middle column ends "and at the price" and the right-hand column begins "changes by displaying all menu items", whose real sentence is "Avoid costly errors and last-minute changes by displaying all menu items and modifiers to guests in real-time." There is no price-change phrase in the document; the no-flags instrument returns 0 and settles it. The word invoice is present 3 times tokenised and 6 squashed and was read: it is Profit Management scanning invoices for cost capture, with no received-price comparison and no alert, consistent with the MarginEdge attribution in the note. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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

TouchBistro Inventory Management page: "Take the guesswork out of your purchase orders with automated order suggestions for each vendor based on your restaurant's needs", "create purchase orders in minutes, and email your inventory orders directly to your vendors", and "data-driven forecasting that takes your actual and ideal usage into account". Shortfalls: no par level per item per location is documented as the input to those suggestions (the only per-location concept named is assigning an item to a physical counting location); the forecasting described is prep forecasting, not a forecast-driven PO quantity mode; the module is a separately-priced add-on; and the evidence is a vendor feature page (C), below the A/B floor a differentiator yes requires. https://www.touchbistro.com/inventory-management/ · retrieved 2026-08-06

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

inventory-waste-logging

"Digital logging of waste, theft, spoilage, and overproduction." Whether waste cost is reported separately from usage variance is not stated. https://www.touchbistro.com/inventory-management/ · retrieved 2026-08-01

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

No date tracking and no expiring-soon surface. The 2026 Product Guide's Inventory Management "What features are included?" list is POS Integration, Inventory Tracking, Flexible Counting Options, Recipe Costing & Management, Suggested Ordering, Food Prep Forecasting, Task & Waste Manager, Nutritional Information & Allergen Mapping, Data-Driven Reporting and Multi-Location Inventory Management. The nearest feature tracks spoilage as an event, not a date: its description is "Digitally track all important inventory details, like food temperatures, spoilage, waste, maintenance needs, and more." `expiring soon` occurs zero times corpus-wide, and `shelf life` and `use-by` occur zero times on every product surface (all their hits are industry blog posts). THE WORD IS A TRAP AND WAS MEASURED: expiry occurs 51 times and every product-surface hit is a credit card expiry date at payment entry, not an ingredient date. Hedge noted: that feature description ends "and more", so the enumeration is not airtight. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Controls as measured over the cited PDF by all three instruments: expiring soon 0/0/0, shelf life 0/0/0, use-by 0/0/0, expiry 0/0/0, expiration 0/0/0, so the 51 corpus-wide expiry hits the note reads as credit-card expiry dates are all in other documents. The nearest positive evidence survives the same instruments: the spoilage-as-an-event quote about food temperatures, spoilage, waste, maintenance needs, and more is present once in all three. The existing hedge stands - that description ends with and more, so the enumeration is not airtight. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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

inventory-bar-partial-bottle

The dedicated bar setup guide has operators stock spirits in Liters and pour in Fluid Ounces via a conversion ratio ("1 liter equals 33.81 (rounding) fluid ounces"), and on-hand is entered as a free-form volume figure ("four 1.75 liter bottles. That's 7 liters... enter 7"), so partial-bottle quantities can be recorded. Shortfalls: no scale or weight integration exists anywhere in the documented hardware set, there is no tenths-of-a-bottle or bottle-fraction counting UI, and this is the deprecated POS-based ingredient system. The App Marketplace bar-management partners Freepour and Bevcheck are separately-subscribed third parties, and TouchBistro's Freepour article states "If you've created recipes and ingredients in TouchBistro's inventory system, TouchBistro does not export this data to this integration." https://help.touchbistro.com/s/article/setting-up-the-ingredient-inventory-system-for-a-bar?language=en_US · retrieved 2026-08-06

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

Accounting connectors exist for QuickBooks, Xero, Sage Intacct, Shogo, Restaurant365 and DAVO. Whether TouchBistro itself exports period COGS and AP invoice detail with per-category GL mapping, versus the partner doing it, is not documented. https://www.touchbistro.com/features/integrations/ · 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

TouchBistro now ships first-party Inventory Management (marked NEW), so it is native — but it is a separately-priced add-on with unpublished pricing, and TouchBistro simultaneously lists eight third-party inventory partners (R365, MarginEdge, WISK, MarketMan, Craftable, Optimum Control, Freepour, Bevchek), which is how most of its base actually solves this. https://www.touchbistro.com/features/integrations/ · retrieved 2026-08-01

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

"See the profit margins of every dish" and optimize recipes for profitability. Joining recipe cost to actual sales mix for contribution margin, and threshold-based flagging after ingredient cost changes, are not documented. https://www.touchbistro.com/inventory-management/ · 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

Withdrawing the previously recorded marketing quote, which the live page does not contain. TouchBistro's Cloud Reporting guide ("How to Navigate Cloud Reporting") documents the freshness contract directly: "Some reports update in real time. That is to say as new data comes into the POS, the report will immediately reflect the updated information. These reports are denoted by a Real Time label," while the rest are batched - "It usually takes about 8 minutes for data on the POS (e.g., sales, payments refunds, bills) to be reflected in the reports and dashboards." The dashboards themselves are documented in How to Use Your Cloud Dashboards: a Sales Dashboard (Net Sales, Average Spend, Parties/Bills/Seats, top Sales Categories, staff shifts, Menu Groups and Items) and a Weekly Targets Dashboard. Within-minutes freshness is therefore met. The off-premise half is only partly met: Cloud Reporting is a browser product accessed by signing in with email and password, and its own instructions assume a desktop browser ("Printing from Safari is not supported"; print "to a printer you have configured with your PC/Mac computer"). No dedicated mobile reporting app is documented anywhere in the 844-URL help-centre sitemap - the only TouchBistro apps documented are the POS iPad app, the Reservations iPad app and the diner-facing Customer Web App. The on-POS live view is the Snapshot Report (Admin | Snapshot Report: running sales total, open tabs and tables, active-shift labor cost, labor/sales ratio), which is on-premise only. https://help.touchbistro.com/s/article/Set-Up-Your-TouchBistro-Dashboard?language=en_US · retrieved 2026-08-08

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

reporting-eod-closeout

The End of Day report is a single dated document made up of named sub-reports: Sales, Tax and Tip Summary (Net Sales with "Gross Sales (before discounts) and Discounts... broken out below", Total Sales Taxes with individual taxes broken out, Total Tips, Total Refund Amount, Total Voids, Total Bill Count, Gross Margin); Payments Summary (Total Cash, Total Non-Cash, Total Payments); Payments by Payment Type (Type, Count, Refunds, Tips, Total per tender); Tip Summary and Tips by Employee; Tip Outs; Payouts/Payins; and Cash Deposits (Expected Deposit = "the system's calculation of what should be in the cash drawer or drawers less the pay-ins/payouts", Actual Deposit, Over/Short, Created by). It downloads as CSV or XLSX, prints or emails, and filters by Day Part. https://help.touchbistro.com/s/article/How-to-View-Your-End-of-Day-Reports?language=en_US · retrieved 2026-08-06

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

Sales | Sales by Menu Item reports Menu Item Name, Menu Item Quantity, Gross Sales, Net Sales, Discount, Voids and Sales Percentage; Advanced Reports has a dedicated Product Mix report type that "fully encompasses all available data from a collection of related static reports", can be restricted to a configured Day Part via the Time Frame control, and takes section as a dimension. Shortfall: at modifier level the only reports are Menu | Modifier Preference by Menu Item (Menu Item (Parent), Modifier, Modifier Type, Quantity Sold) and Menu | Text Modifier - quantity, with no net sales measure for modifiers. The Index of Cloud Reports, which states it "lists all data cells generated by Cloud", contains no modifier-level net sales cell. https://help.touchbistro.com/s/article/Index-of-Cloud-Reports?language=en_US · retrieved 2026-08-06

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

Sales | Void Detail Reports carries Void Reason, Void Quantity, Void Amount, Server name, Authorized By, Bill Number, Menu item and Date | Time; Sales | Discount Details Report carries Discount Reason, Discount Quantity, Discount Amount, Server Name, Authorized By, Bill Number and Date Time; Labor | Deleted Items Report adds Server Name, Manager, Item Ordered Date and Item Deleted Date; Labor | No Sale Report carries Server Name, Manager and Date/Timestamp. Void and discount reasons are operator-defined lists (Menu Management: Void Reasons, Discounts). Shortfall: price overrides are not covered - the Index of Cloud Reports, which "lists all data cells generated by Cloud", contains no price-override or open-price-entry cell and no override approver field, so an item rung in at a manually altered price is not attributable in reporting. https://help.touchbistro.com/s/article/Index-of-Cloud-Reports?language=en_US · retrieved 2026-08-06

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

The Cash Deposits step of the End of Day checklist computes an Expected Deposit ("all cash payments made on bills (including tax and any auto grats), any cash pay-ins minus cash payouts"), takes an Actual Deposit and reports the difference in an Over/Short column, with a blind-count permission (Can Create/Edit Blind Cash Deposits hides the Expected and Over/Short columns) and a View History audit showing "what changes were made, when, and by whom". Shortfalls: the calculation is per business day and aggregates drawers - TouchBistro describes it as "what should be in the cash drawer or drawers" - so there is no per-drawer figure; there is no per-shift or per-employee over/short (the Shift Summary reports Cash Owed to House and Cash Owed to Server, a tip-out balance rather than a variance against a counted drawer); and TouchBistro states plainly "The Cash Deposits report does not provide an audit utility." https://help.touchbistro.com/s/article/How-to-Complete-Your-End-of-Day-Cash-Deposit?language=en_US · retrieved 2026-08-06

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

Labor | Hourly Labor Cost "shows total gross sales for each hour over the given time range, your total labor costs (BOH and FOH) for each hour... as well as the labor cost expressed as a percentage of gross sales", and its Labor Cost column is "calculated based on the clock in/clock out times of all staff members and their set rate of pay plus over time (if configured)" - so the POS time clock is the source. Labor | Labor Cost Analysis gives Labor Cost % by department, splitting FOH from BOH ("front of the house and back of the house staff are differentiated on the Staff Type page") and by Staff Type. Shortfall: there is no sales-per-labor-hour column anywhere, and labor cost as a percentage of sales is not produced per employee - the per-employee reports (Hours Summary, Shift Details, Timesheet Details/Summary) give hours and gross pay only. https://help.touchbistro.com/s/article/labor-reports?language=en_US · retrieved 2026-08-08 adversarially verified

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

Labor | Staff Performance reports per server: Average Check ("the server's average check size"), Guest Average ("the average spend per guest"), Tip % ("average percentage tip the staff member is earning"), Total Tips, Bill Count, Order Count, Guest Count, Avg. Table Turn Time, Void Amount and Discount Amount. Shortfall: the report has no items-per-check metric - Bill Count and Order Count count checks, not lines - and no attachment rate for a named category. Category-level analysis exists only at venue level (Sales | Sales by Sales Category, Menu | Modifier Preference by Menu Item), not per server. https://help.touchbistro.com/s/article/labor-reports?language=en_US · retrieved 2026-08-08 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

Sales | Sales by Order Type breaks out Dine-In, Take Out, Delivery, Bar Tab and Order Online; the Takeout Types Report splits operator-defined custom takeout types (the docs use Uber Eats as the worked example); and Sales by Online Order Provider reports per-provider Bill Count, Gross Sales, Discounts, Net Sales, Tax, Tips to Venue, Provider Commission ("used if you have a third party aggregator") and Total Payment, naming DoorDash and TouchBistro Dine as providers. Shortfalls: no margin or cost measure is available by channel - Menu Item Costs and Gross Margin appear only on Gross Margins by Day, Sales by Menu Group and Sales by Sales Category, none of which take channel as a dimension - and TouchBistro warns that with a third-party aggregator "TouchBistro will not reflect any discounts or promotions being offered by the third party ordering platform", so channel net revenue is incomplete. https://help.touchbistro.com/s/article/touchbistro-online-ordering-ipad-and-cloud-reporting?language=en_US · retrieved 2026-08-06

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

Cloud has a first-class scheduled-report builder, not just the daily sales email the marketing page advertises. "Log into Cloud and click Reports | Scheduled Reports"; "To create a new scheduled report, click Schedule Report at the top right." Step 1 takes a name, a Rolling Date Range, a format ("either CSV (a generic comma-separated values format) or XLSX") and a recipient list - "Enter one or more emails. Click the comma on your keyboard to enter additional emails." Step 2 sets the cadence: "select the frequency: Daily, Weekly, Every 2 Weeks, or Monthly." Step 3: "expand report types and select reports", with a venue toggle for multi-location operators (multi-venue selections restrict to the "multi" reports). A Next Report Date column shows the next send, and reports are editable and deletable. Daily sends fire two hours after the close of the configured service day. Separately, the TouchBistro Payrix Portal has its own Schedule Reports tab for payment Standard Reports - "You can use this tab to schedule one or more Standard Reports to be emailed to you on a recurring (daily, weekky, monthly) basis" (vendor typo preserved) - but that covers only payment-processing reports and only sends to the logged-in user; the Cloud builder is what carries this claim. https://help.touchbistro.com/s/article/custom-reports?language=en_US · retrieved 2026-08-08 adversarially verified

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

Re-attacked on evidence rather than on the marketing page. The App Marketplace article is TouchBistro's own complete enumeration of every integration route available to a merchant, category by category; no developer, API or sandbox entry appears, and it states "Most integrations require you to register and arrange payment with either TouchBistro or a third-party integration partner" - i.e. every route is commercially gated. Probed 2026-08-06: developers.touchbistro.com, developer.touchbistro.com, api.touchbistro.com and docs.touchbistro.com do not resolve, and touchbistro.com/developers/ and /api/ both 404. Across the whole mirrored help centre every occurrence of "API" is a third party's API that TouchBistro consumes or that the merchant pastes in (MoonClerk API key, Enlace Fiscal CFDI API, Moneris terminal setup) - there is no TouchBistro-issued API key, endpoint, or reference. The only documented route for a third party remains emailing integratedpartners@touchbistro.com with commercial terms negotiated privately. https://help.touchbistro.com/s/article/chapter-11-integrations?language=en_US · retrieved 2026-08-06 adversarially verified

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

NEW SURFACE 1 (certificate transparency, 319th): crt.sh for touchbistro.com (2,680 cert rows), touchbistro.io (652) and touchbistro.net (385) gave 330 distinct non-wildcard hostnames; each was DNS-resolved and probed at / plus /swagger, /swagger/index.html, /swagger-ui.html, /swagger/v1/swagger.json, /api-docs, /v2/api-docs, /v3/api-docs, /openapi.json, /openapi.yaml, /docs, /redoc, /graphql, /robots.txt, /sitemap.xml and a nonsense-path control. A partner API tier EXISTS in CT (partners.api.touchbistro.io, staging./develop./integration.partners.api.touchbistro.io, partners.api.int.touchbistro.net, production.partners.api.int.touchbistro.net) but every one is NXDOMAIN today; the live API hosts (venue.api, ordering.api, payments.api, loyalty.api, legacy.api .touchbistro.io; api.touchbistro.io; api.touchbistro.net) return a 16-58 byte 404 on every doc path; no Swagger/OpenAPI/Redoc/GraphQL answered anywhere; schemas.touchbistro.com is S3 AccessDenied (not listable); marketingstaging/marketingdev.touchbistro.com WP REST is the same census as production (help-article 1012, integration 26, post 838; zero extra ids); Wayback CDX offline. The TouchBistro Cloud portal bundle (admin.touchbistro.com, Next.js buildId 334e477b7176c8f4b8c631216b16afe954c49a11, all 535 _buildManifest files, 19.1 MB, anonymous CloudFront) holds 0 'webhook' tokens and its 156 API path templates are the internal venue config API (server header 'TouchBistro venue:config:api'); the only integration calls are /v1/venues/{venueXRefID}/integrations/{integrationXRefID}/actions/enable|disable. That bundle is an internal client, not a partner contract, so it bounds nothing about the partner API. NEW SURFACE 3: payrix.touchbistro.com (TouchBistro Payments, powered by Payrix; anonymous Angular bundle, 1,258 chunks, 29.4 MB) has a 'webhooks' route (WebalertsModule), the string 'Webhooks that have triggered within the last 7 days are shown here.', and alert-trigger editing gated by the permission check be("update","alertTriggers",...). The Cloud portal i18n says 'Create your Payrix Portal login to access transaction reporting, dispute management, and monthly statements.' This is generic Payrix white-label portal code for PAYMENT-processor events only: it covers no order events, TouchBistro documents no retry or signature, and the bundle does not show that a merchant login holds the alertTriggers permission. Not enough for partial. NEW SURFACE 2 (retired vendor API docs): 'Sous Chef' (https://raw.githubusercontent.com/sam-shore/sous-chef/fe5e5f90b13044908df4287b118ada1721f54e52/REST-API.md, read via api.github.com tree + raw, no clone) is a copy of TouchBistro's own repo: its commits (2016-10-21 to 2017-08-04) are by @touchbistro.com addresses, the README signs off 'Your friendly neighbourhood ... TouchBistro engineering and product team' and links github.com/TouchBistro/sous-chef, which api.github.com now returns 404 for. REST-API.md lists 19 endpoints, every one 'GET' and described 'Retrieve ...' (Menu, Bills, Bill, Bills (Extended), Summary, Drilldown, Sales by Day ... Shifts, Tax Summary) on cloud.touchbistro.com; auth is '<api_token>: The unique API Token associated with your TouchBistro Dev account. This will be provided to you by TouchBistro.' menus-to-go.md: 'Menus To Go is our private API for polling menu information for a particular venue' and 'That app can then poll the server directly via the above end-point' (GET http://<ip>:1337/getmenuformenuapp, 'no encryption and no authentication'). That API is RETIRED: cloud.touchbistro.com/api/v1/bills 301 -> admin.touchbistro.com -> 404 today. The README calls itself 'deliberately vague ... this isn't formal documentation', so it describes a 2016-17 read-only API, not today's partner API. VERDICT: still unknown. Retrieved 2026-09-16. || 322nd: CLAIM: see taxonomy. NEW SURFACE (322nd, PUBLIC SOURCE MAPS): the TouchBistro Cloud portal admin.touchbistro.com (production; Next.js buildId 334e477b7176c8f4b8c631216b16afe954c49a11) serves a .js.map for every one of its 535 _buildManifest chunks anonymously (535/535 HTTP 200; nonsense-map control 404), 9,529 sources, 1,597 own (non-node_modules) files with sourcesContent, 10.8 MB (e.g. https://admin.touchbistro.com/_next/static/chunks/10029-f0511988be735f8c.js.map). Grade B for the portal only; it is an internal client of the venue config API and is not a census of TouchBistro's partner API. Tokenised, case-insensitive controls over the 1,597 own sources: webhook/webhooks 0, hmac 0, 'partner api' 0, 'open api' 0; 'callback' 29 (React/OAuth callbacks, POISON), 'retry' 28 (shared/helpers/withRetries.ts client retries, POISON), 'signature' 1 (payment-application form). The only third-party API-key UI is SendGrid (crm/guest-engagement). VERDICT: still unknown (the portal bundle does not bound the partner API). Retrieved 2026-09-17. || 327th: MERGE HOLD (proposed no/B, held unknown): Same as extensibility-webhooks-push: the partner API is unpublished, so webhook emission is unmeasured, not absent. PROPOSAL AS WRITTEN: 327th: same census and same controls as the extensibility-webhooks-push cell - the WordPress corpus completed today to 100% of the publisher's own /wp-json/wp/v2/types manifest (23 types; page 100 -> 254/254; 28,730,675 chars over ~2,600 items, help-articles included) plus the 535-file admin bundle and the retired Sous Chef docs. CLAIM: emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint. VERDICT: no. 'webhook' 0/28.7 M, 'callback URL' 0, 'endpoint' appears only inside the retired Sous Chef material, where every one of the 19 endpoints is a GET the integrator must poll. Poison as named in the webhooks-push cell (poll = Harris Poll; white label = a barcode sticker on an iPP320). Retrieved 2026-09-18. adversarially verified

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

330th, NEW: the RAW-DATA half of this claim is settled from TouchBistro's own help articles (grade B), which no prior pass had read against this cell. CLAIM: '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.' VERDICT: partial - raw-data access is included and unpriced; the API half does not exist to be priced. EVIDENCE: https://www.touchbistro.com/help-articles/generating-menu-reports/ - 'The Menu Item List Report lets you view (and export as CSV) a list of all your current menu items (grouped by Menu Category), their current menu prices, and their costs... this report can be useful if you need to export your menu and prices. For example, you want to use the raw export text as the basis for a printed menu or for posting online.' https://www.touchbistro.com/help-articles/whats-new-in-touchbistro-7-2-2/ - 'Download Reports as CSV Files ... Most reports now allow you to export the report data as a CSV file (which you can open in your spreadsheet software). The following reports support CSV export:' followed by an enumerated report list (Sales by Day, Sales by Category, Menu Item Sales, Payments, Sales by Section, ...). https://www.touchbistro.com/help-articles/user-management/ - the Cloud Portal role table gives a standard 'Analyst' role that 'can: 1. Access Reports. 2, Download reports. 3. Set up scheduled reports.' No fee, add-on SKU, tier or per-location charge attaches to CSV export or the Analyst role anywhere in the 60.9 MB WordPress census (100% of /wp-json/wp/v2/types, 23 types, held on disk from the 327th). BOUND for the unpriced half: the only commercial contract TouchBistro publishes is https://www.touchbistro.com/terms-of-service/ - measured today, https://www.touchbistro.com/legal/ (489,588 B) and https://www.touchbistro.com/master-services-agreement/ (489,612 B) are SOFT-404 shells, byte-for-byte the size of the live nonsense control https://www.touchbistro.com/zzz-nonsense-330/ (404, 489,601 B) and of /api/ (404, 489,585 B) and /become-a-partner/ (404, 489,601 B), so there is no separate MSA/order form/SLA to read. The ToS's only API sentence is about THIRD-PARTY fees, not TouchBistro's: 'Any such access shall be governed by any applicable end user or API agreements or terms applicable to such third party and may be subject to fees charged by such third party.' NOT a no: no TouchBistro API fee is stated anywhere, and the API conjunct fails because no merchant-facing API is offered at all (see the api-access-cost cell), not because it is priced. Retrieved 2026-09-18. https://www.touchbistro.com/help-articles/generating-menu-reports/ · retrieved 2026-09-18 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

"Reporting & Analytics" (50+ reports) is included in the $69 base POS tier. But labor-vs-sales, inventory/COGS and margin reporting require the paid Labor and Inventory add-ons, and multi-location capability is undocumented. https://www.touchbistro.com/pricing/ · retrieved 2026-08-01

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

No retention window is documented anywhere, which is what this claim asks for. `years of data` occurs zero times corpus-wide. The only published retention statement is open-ended and is about personal information rather than transaction detail: "We will retain your personal information for the period necessary to fulfill the purposes outlined in this Privacy Notice unless a longer retention period is required". THE WORD IS A TRAP AND WAS MEASURED: retention occurs 85 times and every product-surface hit is customer retention in a marketing sense. The 2026 Product Guide sells the reporting tier as breadth, not depth — "Equipped with more than 50 cloud-based reports, TouchBistro gives you instant access to the insights you need" — and states no history window and no archive-retrieval position. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. https://www.touchbistro.com/privacy-notice/ · retrieved 2026-09-10

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

Operator-configured thresholds exist and one of them alerts: the POS ingredient Low-Stock Warning is a per-ingredient value that will "send you an alert when stocks are low", and Menu Management Stock Availability has a Low Stock Indicator surfaced on the order screen. Shortfalls: nothing comparable exists for sales, labor, void or discount metrics. The Weekly Targets dashboard takes operator-entered weekly sales and cover targets but only displays progress - "the Key Targets section will show you how close you are to hitting sales and customer numbers you specify" - with no breach notification documented. Scheduled reports are time-triggered emails, not threshold-triggered, and cannot include End of Day or Cash Deposits. No historical-deviation or anomaly detection of any kind is documented. https://help.touchbistro.com/s/article/How-to-User-Your-Cloud-Dashboards?language=en_US · retrieved 2026-08-06

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

Reporting is a fixed report library, not a query interface. The 2026 Product Guide: "Equipped with more than 50 cloud-based reports, TouchBistro gives you instant access to the insights you need." `natural language query` occurs zero times corpus-wide; `copilot` occurs zero times on every product surface; the single corpus `natural language` hit is an industry blog post about a Subway smart fridge. The current 861-article KB documents named reports (Sales Reports and the rest) with no ad-hoc question surface, and the Inventory module's reporting description offers "custom or ad-hoc reports on demand" — report building, not a natural-language answer. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Not an absence-based verdict: it rests on the positive statement that reporting is a fixed library, and the quote about more than 50 cloud-based reports is present under all three instruments, as is the Inventory ad-hoc reports phrasing. Supporting controls over the cited PDF: natural language query 0/0/0, natural language 0/0/0, copilot 0/0/0, ask a question 0/0/0. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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

Loyalty CRM captures visit frequency, average spend and order history per guest, and reports on rewards/loyalty programs. New-vs-returning counts and lifetime-spend cohort reporting are not specifically documented. https://www.touchbistro.com/loyalty/ · retrieved 2026-08-01

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

Labor Management forecasts demand from POS history with net sales or guest count as drivers, consumed by scheduling. A forward sales forecast exposed at daypart/hourly granularity in the reporting UI is not documented, and it requires the paid Labor add-on. https://www.touchbistro.com/labor-management/ · retrieved 2026-08-01

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

Declared versus charged tips per employee is documented: the End of Day Tips by Employee sub-report and the Shift Summary Report both split Total Cash Tips ("cash tips the server reports at his/her shift end") from Total Non Cash Tips (credit card); Labor | Tips by Payment Method reports Tips, Applied to Bill and CC Tip Out to House per server; Labor | Staff Performance adds Cash Tips by Server, Credit Card Tips by Server, CC Tips Owed to Server and Tip % by Server; and Labor | Timesheet Details/Summary carry Reg/OT1/OT2 hours and pay for payroll. Shortfalls: there is no tip pool distribution detail - TouchBistro's only pooling mechanism is a flat Tip Out Amount (%) withheld from credit card tips to the house, surfaced as a single accrued total on the End of Day, with no per-recipient allocation - and the tax side is Audit | Tax Summary by Tax Name over a maximum of three operator-created taxes, which is not a liability summary by jurisdiction. https://help.touchbistro.com/s/article/Index-of-Cloud-Reports?language=en_US · retrieved 2026-08-06

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

"In TouchBistro, we can organize your venues via three levels: Corporate Level... Restaurant Group Level... Venue Level", with Restaurant Groups used to organize guest engagement products, staff, menus and taxes, and branding. It is a first-class object for both permissions and reporting: staff are added at corporate, group or venue level (a corporate-level manager "has the power to clock in as manager at any corporate venue") and Multi reports "can be generated at the Corporate level, at one or more Restaurant Group levels, as well as specific venues within groups", with report scheduling offering the same mix-and-match. Venues can be moved between groups on request to TouchBistro. https://help.touchbistro.com/s/article/How-to-Navigate-the-Cloud-Site-for-Multi-Location-Restaurants?language=en_US · retrieved 2026-08-06

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

multi-location-central-menu-publish

Central authoring exists at one tier: "Menus can be set at the Restaurant Group level for all venues under the group but you cannot have one universal corporate-wide menu." Shortfalls: (1) no corporate-level menu; (2) the target set is not choosable - "These are radio buttons hence if you have two or more venues under a particular group, you can't select a subset of venues. You must either set your menu on a venue-by-venue basis for the group or in bulk at the Restaurant Group level"; (3) publishing is not a single action across the estate - "you need to select each group to see what needs to be published... the system will not then toggle to the next group with waiting changes"; (4) no publish or version history of what was pushed, when and by whom is documented; and (5) a venue-level edit permanently breaks inheritance - "you forever sever its connection at its parent Restaurant Group level." https://help.touchbistro.com/s/article/How-to-Navigate-the-Cloud-Site-for-Multi-Location-Restaurants?language=en_US · retrieved 2026-08-06

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

Two of the three axes are documented without duplicating the item record: per location group, since menu items and their prices are set at the Restaurant Group level with per-venue overrides ("if you set a price for Steak at the Vancouver venue level..."); and per daypart, via Menu Management | Promotional Pricing, which applies a Fixed Price or a percentage/dollar Discount on a day-and-time schedule ("Select appetizers are offered at a fixed price of $5 during weekday lunch hours") and fires automatically on the order screen. Shortfalls: there is no per-order-channel price - TouchBistro states "Promotions are only applied at the point of sale. They will not be applied if a diner is using your TouchBistro Online Ordering site" - and group pricing cannot target a subset of venues, because the location selector offers radio buttons at group or venue level only. https://help.touchbistro.com/s/article/Menu-Management-Promotions?language=en_US · retrieved 2026-08-06

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

Labor Management offers "multi-location management from single platform" and Loyalty works across locations. Above-store aggregation of sales, labor, discounts, voids and item mix with store-vs-store ranking is not documented; reviewers cite this as a weakness. https://www.touchbistro.com/labor-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

"Multi-Location Support" — customers "use gift cards to pay for meals at their most convenient locations"; POS integration provides reporting and end-of-year reconciliation. Inter-store settlement between separate owners is not documented. https://www.touchbistro.com/gift-cards/ · retrieved 2026-08-01

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

Verified verbatim: "Your TouchBistro customer loyalty programs can be used across your restaurant's locations." Add the geo limit the dossier omitted from this cell: "TouchBistro Loyalty is currently available to restaurants in Canada (excluding Québec) and the United States." Marketing-page claim, paid add-on. https://www.touchbistro.com/loyalty/ · retrieved 2026-08-01 adversarially verified

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

Multi-location is modelled as separate venues, not two brands on one terminal. `multi-brand` occurs zero times across the whole corpus and `virtual brand` occurs zero times on every product surface (both hits are industry blog posts). Where the 2026 Product Guide addresses scale it is always per-venue — Loyalty "Multi-Location Functionality", Labor "Multi-Location Staff Management" ("Simplify multi-venue team management and allow employees to work at different locations"), Inventory "Multi-Location Inventory Management". The current KB matches: menu configuration offers "Select a location" and a restaurant-group selector, and multi-venue articles switch between venues rather than running two brands concurrently on one device and drawer. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Controls as measured over the cited PDF by all three instruments: multi-brand 0/0/0, virtual brand 0/0/0, multiple brands 0/0/0, ghost kitchen 0/0/0. INSTRUMENT CAUTION PUBLISHED: a proximity probe for multi brand returns one -layout-only hit that is the table-of-contents entry Multi-Location Functionality colliding with the phrase custom-branded web app through column interleaving; the no-flags instrument returns 0 and it is not a phrase in the document. The per-venue modelling that carries the verdict survives the instruments: Multi-Location Staff Management is present in the no-flags extraction, though notably ABSENT from -layout, which is exactly the column-interleaving fault recorded above. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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 is documented: "If you have multiple locations, you can only create taxes at the corporate level. All venues will inherit the tax names and tax rates. However, you can, at the venue level, specify a unique rate based on each venue's location and specific rates." Multiple simultaneous rates are supported (Detailed Sales reports Tax Rate Applied and Estimated Tax Amount for Tax 1, 2 and 3 per line); jurisdiction-specific rules exist (an Ontario threshold rule - "When the total amount for all items is under or the same as" $4.00, taxed at the GST rate - plus published guides for BC PST on soda, Ohio tax-free takeout, occupation tax, UK settings and tax holidays); inclusive pricing is configurable per menu item; and "Exclude this tax from" removes a tax for a chosen order type. Shortfalls: "You can create up to three taxes" is a hard cap; the tax set itself is corporate-only, so a venue in a jurisdiction needing an additional or differently-structured tax cannot add one and can only re-rate an inherited tax; and there is no per-location customer tax-exemption object (the Tax Exclusion audit report records manual per-bill exclusions after the fact). https://help.touchbistro.com/s/article/Tax-Settings?language=en_US · retrieved 2026-08-06

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

Labor rules are configurable and jurisdiction-shaped: Staff | Staff Settings | Overtime Rules takes a weekly base and multiplier, a daily overtime threshold (Shift Part 1), a doubletime threshold (Shift Part 2) and a Spread of Hours dollar amount, and "If you have more than one location, you must set overtime rules for each location." Shortfalls: (1) scope is per venue only - the multi-location guide lists Overtime Rules among the settings that "always need to be set at the venue level and can't be generalized at the Corporate or Restaurant Group level", so there is no group-level policy; (2) the rules are for reporting, not enforcement - they exist "for calculating overtime pay for the Timesheet Details and the Timesheet Summary report", with no documented clock-in block, approaching-overtime warning or break prompt at the POS, and TouchBistro warns the shift rules silently fail to trigger when a staff member clocks in twice in a day; (3) no predictive-scheduling compliance feature is documented anywhere. https://help.touchbistro.com/s/article/Staff-Overtime-Rules?language=en_US · retrieved 2026-08-06

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

TouchBistro is an iPad-native POS running on standard Apple hardware the operator can buy anywhere; the Customer Facing Display page names iPad Air, iPad Mini 2 and iPad Pro 2015+ explicitly. Not a proprietary-terminal-only platform. https://www.touchbistro.com/customer-facing-display/ · retrieved 2026-08-01

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

iPadOS/iOS is named with specific models and a minimum version for the CFD (iOS 6+). KDS requires MicroTouch 15.6" or 21.5" touchscreens; inventory/labor apps are iOS and Android. A consolidated minimum-spec matrix for the POS itself was not found publicly. https://www.touchbistro.com/customer-facing-display/ · 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

The vendor's supported-device list is an explicit, exhaustive enumeration - "The following iPads are supported by TouchBistro" - and every entry in it is an Apple iPad, listed by Apple model number across the iPad, iPad Mini, iPad Air and iPad Pro families, with an explicit unsupported list. The tableside recommendation is a commodity Mini: "venues that offer tableside ordering might consider the iPad Mini for use by servers." The parent Hardware, Payment, and Third Party App Support article enumerates the complete supported-hardware surface as Compatible iPads, Compatible Printers, Mac Computer Purchasing Guide, Compatible Routers, Supported Payment Processor Integrations, Compatible Cash Drawers and Compatible Barcode Scanners - card readers are a separate, separately-paired category, and no purpose-built handheld with an integrated reader appears. No drop rating or IP ingress rating is published for any device TouchBistro sells or supports. https://help.touchbistro.com/s/article/ipads?language=en_US · retrieved 2026-08-06 adversarially verified

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

The batteries on the PAX A800 and A920Pro handheld payment terminals are user-accessible and field-replaceable - TouchBistro's setup guide instructs "flip the terminal over, remove the case, and then gently remove the battery and the sticker. Replace the battery and case." Shortfalls: no hot-swap is documented (the terminal must be powered down and partly disassembled, and TouchBistro's payment guides warn that below 10% charge "you will not be able to process the transaction"); no rated battery life or shift endurance figure is published for the A800, A920Pro, Moby 8500 or RP457c; and the ordering handheld itself is a consumer iPad or iPad Mini from the supported-model list, with a sealed non-replaceable battery and no vendor-published runtime. https://help.touchbistro.com/s/article/Setting-Up-the-PAX-A800-A920Pro-for-TouchBistro-Payments?language=en_US · retrieved 2026-08-06

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

Cellular hardware is supported: the supported-iPad article lists a WiFi+cellular variant for every recommended and supported family, including the iPad Mini 7 (model A2996) used as a satellite handheld. Shortfalls: TouchBistro frames cellular as a niche rather than a failover - "we only recommend iPads with cellular support for simple food truck setups that lack a cellular router" - and no Wi-Fi-drop failover behaviour is documented anywhere; satellite iPads communicate with a Main Device or Mac Pro Server over the venue LAN, which a cellular link does not replace; and on the cellular-capable PAX A800 payment terminal TouchBistro's setup procedure requires the opposite, instructing operators to "Disable eSIM card" in the terminal's network settings. No vendor-supplied cellular failover product exists in the documented hardware set. https://help.touchbistro.com/s/article/ipads?language=en_US · retrieved 2026-08-06

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

Terminals keep taking orders and payments and keep talking to each other with the internet down; vendor states some features such as report access are unavailable until reconnect. A complete degradation list was not retrievable (help centre is JS-rendered). https://www.touchbistro.com/blog/what-is-a-hybrid-pos/ · retrieved 2026-08-01

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 product with station routing, optional bump bar, audible alerts, multi-screen sync, recall and offline redundancy. Separately priced add-on; US and Canada (ex-Quebec) only. https://www.touchbistro.com/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

The Hardware, Payment, and Third Party App Support article is the vendor's complete supported-hardware index and its category list is exactly: Compatible iPads, Compatible Printers, Mac Computer Purchasing Guide for TouchBistro Multi, Compatible Routers, Supported Payment Processor Integrations, Compatible Cash Drawers, Compatible Barcode Scanners. No kiosk category, countertop or freestanding, exists. The customer-facing display is documented as display-only and cannot take guest input at all: "You cannot display any kind of sign-on-screen payment dialog on the CFD or display any kind of QR code scanning screen." No kiosk appears among the priced add-ons on /pricing/ or in the App Marketplace list, and no ADA or accessibility conformance documentation exists for any kiosk. Counter-evidence weighed: the AODA accessibility policy's boilerplate refers to "our iPad POS system and self-ordering kiosks", but no such product is sold, priced or documented. https://help.touchbistro.com/s/article/hardware-payment-third-party-app-sup2?language=en_US · retrieved 2026-08-06 adversarially verified

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

TouchBistro's KDS guide lists drive-thru among the ticket types it does not produce: reassigning a ticket offers "order types TouchBistro doesn't itself generate like Drive Thru or Curb Side." The only drive-thru facility in the POS is a cosmetic label - a custom Takeout Type named e.g. "Drive Thru", which is "functionally the same as a Takeout order, except the custom takeout order name is printed on the kitchen ticket." TouchBistro's hardware compatibility index (Hardware, Payment, and Third Party App Support) enumerates the supported peripheral classes as iPads, printers, Mac Pro Server computers, routers, payment processor terminals, cash drawers and barcode scanners; no outdoor menu board, order confirmation display, speaker or headset appears there or anywhere in the 764 help-centre articles, and no speed-of-service or drive-thru timer measure appears in the Index of Cloud Reports, which "lists all data cells generated by Cloud." https://help.touchbistro.com/s/article/Using-TouchBistro-KDS-Powered-by-Fresh?language=en_US · retrieved 2026-08-06

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

LAN/Ethernet ESC/POS receipt and kitchen printers are supported and are not vendor-branded - the supported list is Star Micronics TSP100III (143IIILAN), TSP100IV (143IV-UE), TSP143IIIU (Lightning/USB), mC-Print3 (MCP31LB) and the SP742ML/ME impact kitchen printer, all Cat5e Ethernet except the Lightning model, and "All Ethernet-based printers in this document can be used as Kitchen printers." Epson TM-m30 and TM-T88VI have full TouchBistro Ethernet setup guides, so more than one manufacturer has been supported. Shortfall: the current list is single-manufacturer. TouchBistro states "TouchBistro only supports the Ethernet-based printers (receipt and Kitchen printers) listed on this page" and that list contains no Epson, while both Epson guides carry "This printer has been retired from our product lineup. Support resources remain available for existing customers who continue to use this legacy hardware." Serial and parallel printers are unsupported, Ethernet adapters explicitly do not work, the Star ECO line is unsupported, and SP700s in Epson mode "have limited support." https://help.touchbistro.com/s/article/right-printer?language=en_US · retrieved 2026-08-06

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, bump bars, sticky label printers and a customer-facing display are referenced across product pages. No published peripheral compatibility list, and no documentation of scales for by-weight items or multi-drawer per terminal. https://www.touchbistro.com/kitchen-display-system/ · retrieved 2026-08-01

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

Card entry never happens on the iPad. TouchBistro's supported payment matrix enumerates, per processor, every device it integrates with and the features each supports: TouchBistro Payments A800, A920Pro, Lane/3000, Link/2500 and Moby 8500; Chase USA and Chase Canada A800/A920Pro and DESK/5000, MOVE/5000; TSYS PAX; TD DESK/5000 and MOVE/5000; Moneris DX 8000 and A35. All are standalone PIN-entry terminals handling swipe, EMV chip and PIN and contactless. Shortfalls: TouchBistro publishes no validated point-to-point encryption listing and names no P2PE solution provider, and it makes no statement anywhere about the merchant's SAQ type or resulting PCI scope - a search of all 764 help-centre articles returns no occurrence of P2PE, PCI scope or SAQ. Whether the tablet is genuinely out of scope therefore rests on the processor's own attestation, not on anything TouchBistro publishes. https://help.touchbistro.com/s/article/supported-payment-processor-integrations?language=en_US · retrieved 2026-08-06

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

TouchBistro's supported payment matrix lists, processor by processor, every device it accepts payment on - A800, A920Pro, Lane/3000, Link/2500, Moby 8500, DESK/5000, MOVE/5000, DX 8000, A35 - with a feature row per device (swipe, EMV chip and PIN, Tap and Pay, pre-auth tipping, bar tabs); every entry is a separate PCI PIN-entry terminal and there is no softPOS or reader-free row. Independently, the supported-device article for the POS application itself ("The following iPads are supported by TouchBistro") lists only iPad, iPad Mini, iPad Air and iPad Pro models by Apple part number - no iPhone or Android phone is a supported device at all, so Tap to Pay on iPhone or Tap to Pay on Android has no host device in the documented product. The "tap to pay" wording that does appear in TouchBistro's docs is the contactless-reader enable toggle on a Moneris iPP320 PIN pad, not phone-based acceptance. https://help.touchbistro.com/s/article/supported-payment-processor-integrations?language=en_US · retrieved 2026-08-06

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

hardware-pricing-transparency

Re-retrieved live 2026-08-06. The pricing page is the vendor's complete published price list and it publishes no hardware SKU or price. Software starts "at $69/month" with the flag "! Hardware required" and the footnote "*Hardware, payment processing, and additional fees apply"; the Essentials Bundle at "$119/month" bundles "Restaurant-grade hardware" with the footnote "**Payment processing and additional fees apply"; the Custom bundle is priced "Custom - Get a Quote". Every entry in the Add-ons grid, including Payments and Customer Facing Display, carries a "Get a Quote" button and no figure. The FAQ confirms hardware is sold, not published: "TouchBistro offers hardware financing for venues with two or more terminals ... paying for your hardware in monthly installments." https://www.touchbistro.com/pricing/ · retrieved 2026-08-06 adversarially verified

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

Hardware can be bought (with financing offered "for venues with two or more terminals") or taken bundled inside the Essentials subscription. The vendor states both routes exist but publishes neither price nor lease terms. https://www.touchbistro.com/pricing/ · 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

The question is answered in the Merchant Terms, but not favourably. Hardware means "the iPads and other related hardware technology required by Merchant to utilize TouchBistro Services and acquired by Merchant from TouchBistro, as detailed in the Sales Quote", and where a Hardware Payment Plan applies, "throughout the term of the HPP Agreement, TouchBistro shall maintain the right to remotely disable any iPads which form part of the subject matter of the HPP Agreement"; the same right attaches on default during the Initial Term where the merchant "was provided an Incentive for hardware". Shortfalls: financed or incentivised iPads are therefore expressly software-lockable and not guaranteed usable after cancellation; and for hardware bought outright the terms say nothing at all - no clause confirms it is free of lock, and none addresses the card readers, which are supplied under the payment processor's arrangement rather than TouchBistro's. https://www.touchbistro.com/terms-of-service/ · retrieved 2026-08-06

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

Nothing is published, and this is a publication claim. `RMA`, `return merchandise authorization` and `advance exchange` occur zero times across the whole corpus. The 2026 Product Guide has a Hardware section and a Hardware FAQs page that do enumerate supported iPads, the routers it names (Cisco Meraki Z4C and Unifi access points bought with it — framed "including", so a floor), supported printer and cash-drawer brands — and state no warranty term and no replacement turnaround. The current KB points merchants at somebody else's warranty instead: "The device manufacturer has advised that the use of third-party accessories may void the manufacturer's warranty. Please refer to the manufacturer's warranty documentation for full details." warranty is present 19 times and was read: contest and beta disclaimers, manufacturer pointers, and the Merchant Terms disclaiming warranties on payment processing. `next business day` on the vendor site is Chase deposit funding, not hardware. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Controls as measured over the cited PDF by all three instruments: RMA 0/0 tokenised, return merchandise authorization 0/0/0, advance exchange 0/0/0, next business day 0/0/0, replacement 0/0/0, and the bare word warranty is 0 under all three instruments in this file, which is the positive point the note makes - the Hardware section and Hardware FAQs state no warranty term. The 19 warranty hits and the manufacturer-warranty quote the note reads are in the KB and other documents and are correctly attributed there. POISON PUBLISHED: RMA reads 0 tokenised but 28 squashed in -layout and 29 in no-flags, and every single hit is a fragment of an ordinary word - labor management, information, thermal, performance, for maximum, for managing. Nothing in that figure is a return authorisation. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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

hardware-byod

TouchBistro's supported-device article is an exhaustive statement for the POS application - "The following iPads are supported by TouchBistro", with recommended and supported models enumerated by Apple model number across the iPad, iPad Mini, iPad Air and iPad Pro families, plus a Mac Pro Server for estates above five iPads. No iPhone or Android phone appears, and the hardware compatibility index (iPads, printers, Mac, routers, payment terminals, cash drawers, barcode scanners) has no phone class either. There is therefore no ordering or payment app that staff could run on a personal phone, and consequently no BYOD permission or security model to document. Cloud web access for managers and the diner-facing Customer Web App are the only phone-reachable surfaces documented, and neither takes orders or payments at the point of sale. https://help.touchbistro.com/s/article/ipads?language=en_US · retrieved 2026-08-06

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

A device console exists: POS Connectivity | Manage Devices lists each connected iPad and lets an admin Log Off an iPad or Remove iPad from Restaurant behind an admin passcode, and the multi-location guide treats Devices as a per-venue managed object. Printer state is surfaced live with per-condition messages (Disconnected, Paper Low, Paper Empty, Power Disconnected, Cover Open, Cutter Error, Buffer Overflow), and tickets can be redirected from a failed printer to another. Shortfalls: the console lives on the POS itself rather than in a remote cloud portal; there is no remote reboot; no software-version column or per-device version visibility is documented; and there is no staged rollout - TouchBistro updates are ordinary App Store app updates applied iPad by iPad, with the vendor's own guidance being to switch automatic updates off entirely and "Repeat these steps for all iPads." https://help.touchbistro.com/s/article/managing-connected-devices?language=en_US · retrieved 2026-08-06

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

Specialty beverage hardware partners are integrated and documented under Bar Management in the App Marketplace - Freepour, Bevcheck, Craftable and Wisk - each enabled from TouchBistro Cloud by pasting a Restaurant ID or partner GUID. Shortfall: the documented purpose is one-directional inventory reconciliation (TouchBistro describes enabling Freepour "to help with inventory data"), and nothing documents a pour measured by a flow meter or spout posting itself onto an open POS tab or bill. TouchBistro further states of that integration "If you've created recipes and ingredients in TouchBistro's inventory system, TouchBistro does not export this data to this integration", indicating a loosely coupled feed rather than live order injection. No scale, flow meter or self-pour tap wall appears in TouchBistro's hardware compatibility index. https://help.touchbistro.com/s/article/freepour?language=en_US · retrieved 2026-08-06

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

`caller ID` and `callerid` occur zero times across the whole 3,321-document corpus. The integration catalogue is 26 entries in eight categories — Accounting, Business Insights & Analytics, Business Insurance, Inventory Management, Online Ordering Aggregators, Online Ordering Integrations, Payment Processing, Staff Scheduling & Payroll — with no telephony category and no telephony partner, and the 2026 Product Guide's Hardware FAQs enumerate supported iPads, routers, printers and cash drawers with no telephony device. FLOOR NOTED: the catalogue is framed "TouchBistro integrates with a variety of best-in-class software and payment partners" and directs customers to an App Marketplace behind sign-in, so an unlisted partner cannot be excluded; the verdict rests on the corpus-wide zero plus the absence of any telephony surface in the hardware enumeration. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. https://www.touchbistro.com/features/integrations · retrieved 2026-09-10

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

extensibility-public-api-docs

The App Marketplace article enumerates every integration a merchant can enable and states that "Most integrations require you to register and arrange payment with either TouchBistro or a third-party integration partner" - there is no self-serve developer entry among them. Probed 2026-08-06: developers.touchbistro.com, developer.touchbistro.com, api.touchbistro.com and docs.touchbistro.com do not resolve at all, and https://www.touchbistro.com/developers/ and /api/ both return 404. No reference documentation, sandbox, or key-provisioning flow is published on any TouchBistro host. Across the mirrored help centre, every "API" occurrence is a third party's API key pasted into TouchBistro (MoonClerk, Enlace Fiscal, Moneris), never a TouchBistro-issued credential. The documented route for a third party is emailing integratedpartners@touchbistro.com and negotiating commercial terms first. https://help.touchbistro.com/s/article/chapter-11-integrations?language=en_US · retrieved 2026-08-06 adversarially verified

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

extensibility-api-access-cost

NEW SURFACE 2 (retired vendor API docs): 'Sous Chef' (https://raw.githubusercontent.com/sam-shore/sous-chef/fe5e5f90b13044908df4287b118ada1721f54e52/REST-API.md, read via api.github.com tree + raw, no clone) is a copy of TouchBistro's own repo: its commits (2016-10-21 to 2017-08-04) are by @touchbistro.com addresses, the README signs off 'Your friendly neighbourhood ... TouchBistro engineering and product team' and links github.com/TouchBistro/sous-chef, which api.github.com now returns 404 for. REST-API.md lists 19 endpoints, every one 'GET' and described 'Retrieve ...' (Menu, Bills, Bill, Bills (Extended), Summary, Drilldown, Sales by Day ... Shifts, Tax Summary) on cloud.touchbistro.com; auth is '<api_token>: The unique API Token associated with your TouchBistro Dev account. This will be provided to you by TouchBistro.' menus-to-go.md: 'Menus To Go is our private API for polling menu information for a particular venue' and 'That app can then poll the server directly via the above end-point' (GET http://<ip>:1337/getmenuformenuapp, 'no encryption and no authentication'). That API is RETIRED: cloud.touchbistro.com/api/v1/bills 301 -> admin.touchbistro.com -> 404 today. The README calls itself 'deliberately vague ... this isn't formal documentation', so it describes a 2016-17 read-only API, not today's partner API. On price it says only that the API token 'will be provided to you by TouchBistro'. It names no fee, tier or plan. NEW SURFACE 1 (certificate transparency, 319th): crt.sh for touchbistro.com (2,680 cert rows), touchbistro.io (652) and touchbistro.net (385) gave 330 distinct non-wildcard hostnames; each was DNS-resolved and probed at / plus /swagger, /swagger/index.html, /swagger-ui.html, /swagger/v1/swagger.json, /api-docs, /v2/api-docs, /v3/api-docs, /openapi.json, /openapi.yaml, /docs, /redoc, /graphql, /robots.txt, /sitemap.xml and a nonsense-path control. A partner API tier EXISTS in CT (partners.api.touchbistro.io, staging./develop./integration.partners.api.touchbistro.io, partners.api.int.touchbistro.net, production.partners.api.int.touchbistro.net) but every one is NXDOMAIN today; the live API hosts (venue.api, ordering.api, payments.api, loyalty.api, legacy.api .touchbistro.io; api.touchbistro.io; api.touchbistro.net) return a 16-58 byte 404 on every doc path; no Swagger/OpenAPI/Redoc/GraphQL answered anywhere; schemas.touchbistro.com is S3 AccessDenied (not listable); marketingstaging/marketingdev.touchbistro.com WP REST is the same census as production (help-article 1012, integration 26, post 838; zero extra ids); Wayback CDX offline. The TouchBistro Cloud portal bundle (admin.touchbistro.com, Next.js buildId 334e477b7176c8f4b8c631216b16afe954c49a11, all 535 _buildManifest files, 19.1 MB, anonymous CloudFront) holds 0 'webhook' tokens and its 156 API path templates are the internal venue config API (server header 'TouchBistro venue:config:api'); the only integration calls are /v1/venues/{venueXRefID}/integrations/{integrationXRefID}/actions/enable|disable. That bundle is an internal client, not a partner contract, so it bounds nothing about the partner API. The Cloud portal i18n (4,102 keys) and the WP 'integration' post type (26) hold no API pricing. VERDICT: still unknown. Retrieved 2026-09-16. || 322nd: CLAIM: see taxonomy. NEW SURFACE (322nd, PUBLIC SOURCE MAPS): the TouchBistro Cloud portal admin.touchbistro.com (production; Next.js buildId 334e477b7176c8f4b8c631216b16afe954c49a11) serves a .js.map for every one of its 535 _buildManifest chunks anonymously (535/535 HTTP 200; nonsense-map control 404), 9,529 sources, 1,597 own (non-node_modules) files with sourcesContent, 10.8 MB (e.g. https://admin.touchbistro.com/_next/static/chunks/10029-f0511988be735f8c.js.map). Grade B for the portal only; it is an internal client of the venue config API and is not a census of TouchBistro's partner API. The Marketplace enumeration (src/domains/marketplace/utils/partnerInfoMapper.tsx) lists a partner tile partnerName 'Api Access' (slug api_access, no website, no referralInfo); src/shared/locales/en.ts: partner_description_long_api_access "With a direct integration into TouchBistro's Cloud API, your POS transaction data will flow directly into your proprietary data management and reporting systems. Simplify your reporting, save time and reduce errors from double-entry." and partner_description_short_api_access "Direct API access delivers your transaction data directly into your proprietary data and reporting systems." So a merchant-facing, READ-ONLY transaction-data Cloud API is sold/listed as a Marketplace item; no price, fee, plan or 'included' wording appears in the listing or anywhere in the 1,597 files. No cost is stated for the 'Api Access' listing. VERDICT: still unknown. Retrieved 2026-09-17. || 327th: 327th, NEW SURFACE: TouchBistro's merchant Terms of Service at https://www.touchbistro.com/terms-of-service/ (200, 75,866 chars of stripped text; nonsense-path control https://www.touchbistro.com/zzz-nonsense-control/ returns a 404 template, so the page is real). It is a genuine merchant agreement - subscription terms, termination, incentive repayment, Beta Terms - and it PRICES NOTHING about API access. Its only API sentence concerns third parties, not TouchBistro's own fee: 'Any such access shall be governed by any applicable end user or API agreements or terms applicable to such third party and may be subject to fees charged by such third party.' It does confirm that developer credentials exist as a concept: merchants may not 'use the developer credentials licensed to a different individual or entity'. Also checked: the public /pricing/ page and, at 100% of the /wp-json/wp/v2/types manifest, the whole WordPress corpus (28.7 M chars) - 'integration fee' 2 hits, both POISON (a blog comparing SILVERWARE's '$25 per month integration fee', and TouchBistro Reservations copy about the ~$100/month a reservations-POS integration usually costs elsewhere); one real per-location fee is disclosed but for a different product ('Do TouchBistro Digital Gift Cards support multi-location? Yes. There is a per-location fee, however.'), which shows the vendor WOULD state such a fee when one exists, yet it states none for API access. Still unknown: silence is not inclusion. Retrieved 2026-09-18. || 328th: 328th, NEW SURFACE for this cell: a per-cell re-grep of the admin.touchbistro.com source-map corpus already on disk from the 322nd (535 maps, 301 recovered original TypeScript sources, 14 MB of `sourcesContent`; this is TouchBistro Cloud, the back-office app, NOT the iPad POS). There is NO merchant-facing API-key, developer, credentials or integration-billing screen anywhere in it. Tokenised over all 301 sources, `api_key`/`API Key`/`api-key` scores 41 occurrences in 10 files and EVERY ONE IS POISON - a field where the merchant pastes a THIRD PARTY's key: 'Change SendGrid API Key and/or "From" email address:' and `ge.moonclerk_api_key_saved` (guest-engagement promotions/subscriptions dialogs, crm EmailTab), plus `NEXT_PUBLIC_GOOGLE_MAPS_API_KEY` in shared/config/browser.ts. `webhook` 0, `graphql` 0. A back-office bundle cannot price anything, so this is a bound on the SELLING surface only, not a verdict. Also probed today for a public developer surface to census: developer.touchbistro.com, docs.touchbistro.com, api.touchbistro.com and partners.touchbistro.com are all NXDOMAIN (nslookup 'Non-existent domain'; curl exit 000, not a refusal), confirming the 327th's finding that the live partner tier publishes nothing. Retrieved 2026-09-18. || 330th: 330th, NEW SURFACES, cell still unknown. (1) TouchBistro's ONLY published 'Partner Program' is an affiliate/referral scheme, not a technology or developer tier: the site header and footer link 'Partner Program' to https://www.touchbistro.com/affiliates/ (200, 517,879 B), titled "TouchBistro's Partner Program" - 'When you join our affiliate partner program, you can earn cash for introducing restaurateurs to TouchBistro... up to $100 Per Demo, up to $1000 Per Sale' and the eligibility list is resellers and consultants (Restaurant/Hospitality Consultants, Merchant Service Providers & Agents, Solution Providers, IT & Managed Service Providers, Restaurant Equipment Suppliers, Food Service Suppliers, Restaurant Marketing Companies). There is no API/developer tier, price list or access fee on it. (2) Measured today with curl + browser UA: developer.touchbistro.com and developers.touchbistro.com are NXDOMAIN; https://www.touchbistro.com/api/ and /become-a-partner/ are soft-404 shells (489,585 / 489,601 B) identical in size to the nonsense control /zzz-nonsense-330/ (489,601 B); /integrations/ 301s to the homepage and /partners/ 301s to /features/integrations/, whose only outbound integration links are the partners' OWN pages (deliverect, 7shifts, pushoperations, marketman, shogo, avero, craftable, bevchek, tracrite, davosalestax, coverdash) - no TouchBistro developer portal. (3) The same soft-404 test retires https://www.touchbistro.com/legal/ and /master-services-agreement/ as corpora: both are 489.5 KB shells, so the Terms of Service is the whole published commercial contract and its single API sentence prices only THIRD-PARTY APIs ('may be subject to fees charged by such third party'). WHY STILL UNKNOWN: no TouchBistro API fee, plan gate or enterprise-only clause is stated on any of these surfaces, and the 329th rule requires a STATED fee for a cost `no`; and a `yes` is impossible because TouchBistro names the absence of open API access as its own weakness (see extensibility-menu-write-api). The claim has nothing to price. Retrieved 2026-09-18. 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

There is no developer-facing surface to host a sandbox. Probed 2026-08-06: developer.touchbistro.com, api.touchbistro.com and docs.touchbistro.com all fail to resolve (curl exit, no HTTP response); the complete touchbistro.com nav and footer, read on /terms-of-service/, /iso-partnerships/ and /contact-us/, offer Products, Restaurant Types, Pricing, Resources, Compare, Customer Hub, Help Articles, Customer Support, About, Careers, News, Contact, Referrals, Partner Program and ISO & Agents - no developer or API destination. All 773 help.touchbistro.com articles (mirrored from /s/sitemap-topicarticle-1.xml) contain zero occurrences of 'sandbox'. Reforming Retail (23 Jan 2019) records the only documented access route: a third party approaches TouchBistro, 'commercial terms must be established', and TouchBistro issues an API key. A free test environment obtainable without a paid production account does not exist because no unsolicited developer can obtain access at all. https://reformingretail.com/index.php/2019/01/23/why-do-some-cloud-pos-companies-still-lack-apis/ · retrieved 2026-08-06

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

TouchBistro's operator-facing authorization surface is the Cloud App Marketplace, and its per-app setup screens are documented individually. Every one is an enable/disable toggle plus a partner-side identifier the operator copies in or out - MarketMan: 'Select Enabled. Get your MarketMan Buyer GUID ... and enter it here'; Push Operations: 'Select Enabled. Copy your Restaurant ID. You will need to enter this into your Push integration'; Avero: 'Select Enable from the drop-down box ... Enter your business key in the Avero Business ID field'. None presents a scope list, a consent screen, or an operator-issued credential. The single authorization dialog in the set (7shifts) runs the other way: the operator logs into 7shifts and is 'prompted to authorize the integration on the 7shifts' side', with TouchBistro receiving only a Location ID. 'OAuth' appears zero times across all 773 mirrored help.touchbistro.com articles. Corroborating the key model on the partner side, Reforming Retail (23 Jan 2019) quotes TouchBistro's CEO: 'it's up to the third party software provider to get an API key from us' and 'If an approved provider is doing something fishy we kill the key' - keys issued to and revoked by TouchBistro, not scoped grants issued by the operator. https://help.touchbistro.com/s/article/chapter-11-integrations · retrieved 2026-08-06

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

extensibility-webhooks-push

NEW SURFACE 2 (retired vendor API docs): 'Sous Chef' (https://raw.githubusercontent.com/sam-shore/sous-chef/fe5e5f90b13044908df4287b118ada1721f54e52/REST-API.md, read via api.github.com tree + raw, no clone) is a copy of TouchBistro's own repo: its commits (2016-10-21 to 2017-08-04) are by @touchbistro.com addresses, the README signs off 'Your friendly neighbourhood ... TouchBistro engineering and product team' and links github.com/TouchBistro/sous-chef, which api.github.com now returns 404 for. REST-API.md lists 19 endpoints, every one 'GET' and described 'Retrieve ...' (Menu, Bills, Bill, Bills (Extended), Summary, Drilldown, Sales by Day ... Shifts, Tax Summary) on cloud.touchbistro.com; auth is '<api_token>: The unique API Token associated with your TouchBistro Dev account. This will be provided to you by TouchBistro.' menus-to-go.md: 'Menus To Go is our private API for polling menu information for a particular venue' and 'That app can then poll the server directly via the above end-point' (GET http://<ip>:1337/getmenuformenuapp, 'no encryption and no authentication'). That API is RETIRED: cloud.touchbistro.com/api/v1/bills 301 -> admin.touchbistro.com -> 404 today. The README calls itself 'deliberately vague ... this isn't formal documentation', so it describes a 2016-17 read-only API, not today's partner API. It shows the 2016-17 API was pull-only (no webhook, no callback, and 'polling' named as the menu path), but the platform was rebuilt afterwards (the CT partner-API hosts above), so it cannot carry a current 'no'. NEW SURFACE 1 (certificate transparency, 319th): crt.sh for touchbistro.com (2,680 cert rows), touchbistro.io (652) and touchbistro.net (385) gave 330 distinct non-wildcard hostnames; each was DNS-resolved and probed at / plus /swagger, /swagger/index.html, /swagger-ui.html, /swagger/v1/swagger.json, /api-docs, /v2/api-docs, /v3/api-docs, /openapi.json, /openapi.yaml, /docs, /redoc, /graphql, /robots.txt, /sitemap.xml and a nonsense-path control. A partner API tier EXISTS in CT (partners.api.touchbistro.io, staging./develop./integration.partners.api.touchbistro.io, partners.api.int.touchbistro.net, production.partners.api.int.touchbistro.net) but every one is NXDOMAIN today; the live API hosts (venue.api, ordering.api, payments.api, loyalty.api, legacy.api .touchbistro.io; api.touchbistro.io; api.touchbistro.net) return a 16-58 byte 404 on every doc path; no Swagger/OpenAPI/Redoc/GraphQL answered anywhere; schemas.touchbistro.com is S3 AccessDenied (not listable); marketingstaging/marketingdev.touchbistro.com WP REST is the same census as production (help-article 1012, integration 26, post 838; zero extra ids); Wayback CDX offline. The TouchBistro Cloud portal bundle (admin.touchbistro.com, Next.js buildId 334e477b7176c8f4b8c631216b16afe954c49a11, all 535 _buildManifest files, 19.1 MB, anonymous CloudFront) holds 0 'webhook' tokens and its 156 API path templates are the internal venue config API (server header 'TouchBistro venue:config:api'); the only integration calls are /v1/venues/{venueXRefID}/integrations/{integrationXRefID}/actions/enable|disable. That bundle is an internal client, not a partner contract, so it bounds nothing about the partner API. VERDICT: still unknown. Retrieved 2026-09-16. || 322nd: CLAIM: see taxonomy. NEW SURFACE (322nd, PUBLIC SOURCE MAPS): the TouchBistro Cloud portal admin.touchbistro.com (production; Next.js buildId 334e477b7176c8f4b8c631216b16afe954c49a11) serves a .js.map for every one of its 535 _buildManifest chunks anonymously (535/535 HTTP 200; nonsense-map control 404), 9,529 sources, 1,597 own (non-node_modules) files with sourcesContent, 10.8 MB (e.g. https://admin.touchbistro.com/_next/static/chunks/10029-f0511988be735f8c.js.map). Grade B for the portal only; it is an internal client of the venue config API and is not a census of TouchBistro's partner API. Controls over the 1,597 own sources: webhook(s) 0; the only integration writes are Marketplace partner connects (7shifts, DoorDash Marketplace, Coverdash, Avero). VERDICT: still unknown. Retrieved 2026-09-17. || 327th: MERGE HOLD (proposed no/B, held unknown): A CAPABILITY claim, and TouchBistro runs a partner API it does not publish (retired Sous Chef doc, live partner integrations). A complete census of the PUBLIC site and help centre bounds what is published, not what the unpublished partner API emits; same hold as qu, conversenow and digital-dining this session. PROPOSAL AS WRITTEN: 327th - the corpus that earlier passes left SHORT is now a census, and it carries the verdict. CLAIM: real-time webhooks pushed for order lifecycle events. VERDICT: no. BOUND: TouchBistro's site is WordPress and its own manifest, https://www.touchbistro.com/wp-json/wp/v2/types, declares 23 types. Counts re-derived today from X-WP-Total, not inherited: post 841, page 254, help-article 1012, integration 26, content-module 117, press-release 217, employee-story 8, banner 1, personalization 0, testing 0. The 317th's corpus held only 100 of the 254 PAGES; all 254 were fetched today (3 requests, 15.8 MB) together with the newest posts, giving 28,730,675 chars of body text across every type - the help-article type IS the store-level POS's own documentation, so this bounds the product and not just a back office. CONTROLS, tokenised, word-boundary, case-insensitive, denominator 28.7 M chars / ~2,600 items: webhook 0, 'REST API' 0, 'developer portal' 0, 'callback URL' 0, 'subscribe to events' 0, 'push notification to' 0, SDK 0. POISON NAMED AND EXCLUDED: 'open API' 3 and 'API access' 3 - every one is TouchBistro's competitor-comparison copy crediting SOMEONE ELSE ('Toast also offers ... an open API', 'Lightspeed ... raw API access'), i.e. this vendor writes the phrase only about rivals; 'poll'/'polling' 21 hits, all Harris Poll and Instagram/Facebook polls; 'embed' 64 and 'iframe' 6, all Calconic calculator widgets and an eCardSystems balance iframe; 'white label' 1 - a physical white LABEL with a barcode on the back of an iPP320 terminal. CORROBORATION: the only TouchBistro API documentation ever published, the retired Sous Chef REST-API.md, is 19 endpoints all GET, and its menus-to-go doc tells the integrator 'That app can then poll the server directly via the above end-point' - polling, explicitly, not push; and the admin.touchbistro.com Next.js bundle censused in the 319th (535 _buildManifest files, 19.1 MB) holds 0 'webhook' tokens. Retrieved 2026-09-18. adversarially verified

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

extensibility-webhook-reliability

No webhook contract found on any new surface. NEW SURFACE 1 (certificate transparency, 319th): crt.sh for touchbistro.com (2,680 cert rows), touchbistro.io (652) and touchbistro.net (385) gave 330 distinct non-wildcard hostnames; each was DNS-resolved and probed at / plus /swagger, /swagger/index.html, /swagger-ui.html, /swagger/v1/swagger.json, /api-docs, /v2/api-docs, /v3/api-docs, /openapi.json, /openapi.yaml, /docs, /redoc, /graphql, /robots.txt, /sitemap.xml and a nonsense-path control. A partner API tier EXISTS in CT (partners.api.touchbistro.io, staging./develop./integration.partners.api.touchbistro.io, partners.api.int.touchbistro.net, production.partners.api.int.touchbistro.net) but every one is NXDOMAIN today; the live API hosts (venue.api, ordering.api, payments.api, loyalty.api, legacy.api .touchbistro.io; api.touchbistro.io; api.touchbistro.net) return a 16-58 byte 404 on every doc path; no Swagger/OpenAPI/Redoc/GraphQL answered anywhere; schemas.touchbistro.com is S3 AccessDenied (not listable); marketingstaging/marketingdev.touchbistro.com WP REST is the same census as production (help-article 1012, integration 26, post 838; zero extra ids); Wayback CDX offline. The TouchBistro Cloud portal bundle (admin.touchbistro.com, Next.js buildId 334e477b7176c8f4b8c631216b16afe954c49a11, all 535 _buildManifest files, 19.1 MB, anonymous CloudFront) holds 0 'webhook' tokens and its 156 API path templates are the internal venue config API (server header 'TouchBistro venue:config:api'); the only integration calls are /v1/venues/{venueXRefID}/integrations/{integrationXRefID}/actions/enable|disable. That bundle is an internal client, not a partner contract, so it bounds nothing about the partner API. The legacy 'Sous Chef' REST docs (https://raw.githubusercontent.com/sam-shore/sous-chef/fe5e5f90b13044908df4287b118ada1721f54e52/REST-API.md, TouchBistro-authored 2016-17, now retired) are GET-only and have no webhook, signature or retry section. VERDICT: still unknown. Retrieved 2026-09-16. || 322nd: CLAIM: see taxonomy. NEW SURFACE (322nd, PUBLIC SOURCE MAPS): the TouchBistro Cloud portal admin.touchbistro.com (production; Next.js buildId 334e477b7176c8f4b8c631216b16afe954c49a11) serves a .js.map for every one of its 535 _buildManifest chunks anonymously (535/535 HTTP 200; nonsense-map control 404), 9,529 sources, 1,597 own (non-node_modules) files with sourcesContent, 10.8 MB (e.g. https://admin.touchbistro.com/_next/static/chunks/10029-f0511988be735f8c.js.map). Grade B for the portal only; it is an internal client of the venue config API and is not a census of TouchBistro's partner API. Controls over the 1,597 own sources: webhook(s) 0, hmac 0; 'retry' hits are client-side withRetries.ts (POISON), 'signature' 1 is a payment-application field. VERDICT: still unknown. Retrieved 2026-09-17. || 327th: MERGE HOLD (proposed no/B, held unknown): Same as extensibility-webhooks-push. PROPOSAL AS WRITTEN: 327th: this cell falls out of the webhooks-push finding - there is no webhook surface at all for a signature or a retry policy to attach to. BOUND as in that cell (WordPress manifest census completed today: 23 types, 254/254 pages, 28.7 M chars; plus the 535-file admin.touchbistro.com bundle and the retired Sous Chef REST-API.md). CONTROLS, tokenised: webhook 0, HMAC 0, 'signed' 0 in any integration sense, 'retry' 0, 'backoff' 0, 'dead letter' 0, 'replay' 0. Retrieved 2026-09-18. adversarially verified

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

Orders demonstrably inject from Deliverect, UrbanPiper, Flipdish and DoorDash and fire to KDS/printers — so the capability exists — but it is available only to approved partners under private commercial terms, not as a public write API. https://www.touchbistro.com/features/integrations/ · retrieved 2026-08-01

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

extensibility-menu-write-api

330th, NEW: a VENDOR DENIAL, not an absence - prior passes held this cell because an unpublished partner API could not be bounded, but TouchBistro states in its own voice that it does not offer developer API access. CLAIM: 'Menu items, modifiers, and prices can be written and updated via API, not just read.' VERDICT: no. EVIDENCE (all TouchBistro-authored pages on www.touchbistro.com, grade C): https://www.touchbistro.com/blog/best-restaurant-pos-systems/ under the heading 'What are TouchBistro's weaknesses?' - 'Unlike some POS providers that offer integrations with dozens of different partners and custom Application Programming Interface (API) access, TouchBistro supports integrations for a much more curated list of best-in-class partners.' https://www.touchbistro.com/blog/touchbistro-vs-clover/ - after noting 'the Clover API is available to developers so there is the option to design your own app', TouchBistro writes 'TouchBistro does not support the same kind of app ecosystem as Clover, meaning you have a more limited list of third-party partners to choose from. Part of the reason for this is that TouchBistro offers more of its own native solutions.' https://www.touchbistro.com/blog/touchbistro-vs-toast/ - 'Toast also has an open API, which means you can develop your own integrations if you choose to - a plus for enterprise restaurant brands. While TouchBistro does not offer as many integrations...'. CORROBORATION (vendor help, grade B): the menu master is the iPad, and even TouchBistro's OWN cloud menu editor cannot write to it without a manual device-side pull - https://www.touchbistro.com/help-articles/remote-menu-management/ 'Remote Menu Management allows you to edit your menu and various menu-related options via TouchBistro cloud page' and then 'On your iPad, open TouchBistro. Access Admin | Admin Settings | Menu. Tap Import Menu Changes... Tap Import Menu Changes to signal TouchBistro to return menu editing on the iPad.' BOUND/CONTROLS: no developer surface exists to contradict this - developer(s).touchbistro.com NXDOMAIN and /api/ a soft-404 (measured today, curl + browser UA); the only 'Partner Program' is the affiliate scheme at /affiliates/; the 60.9 MB WordPress census (100% of /wp-json/wp/v2/types, 23 types, 254 pages, 1,012 help-articles) contains no menu-write endpoint, and every tokenised case-insensitive `\bAPI\b` hit in it is one of four things: a THIRD-PARTY key the merchant pastes in (Moneris API token, SendGrid API Key, TouchBistro Loyalty enablement key, enlacefiscal.com CFDI API), TouchBistro's own payment callback URLs (api.touchbistro.net/moneris/hppapprove|hppdecline), a COMPETITOR's API in a comparison post (Lightspeed 'raw API access', Toast 'open API', Clover, MICROS, Revel, Epos Now, Silverware), or the WordPress/vendor script chrome (api.w.org, omappapi.com, calconic.com/api/embed) - poison named because an untokenised `api` search is dominated by that chrome; and the admin.touchbistro.com source-map corpus (535 maps, 301 original sources, held from the 322nd) has no menu domain at all, its 156 path templates being the venue-config API. WEAKNESS: the strongest statements are vendor blog prose (grade C), and they deny 'custom API access' generally rather than menu write specifically. Retrieved 2026-09-18. https://www.touchbistro.com/blog/best-restaurant-pos-systems/ · retrieved 2026-09-18 adversarially verified

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 `touchbistro_production`, rendered as 'TouchBistro', with qualityStatus CERTIFIED and 4 of the 8 high-quality features built. CERTIFIED and AT_RISK are the program's other two tiers, so this is positive evidence of non-membership rather than a failure to find the vendor: it is present in the registry and carries a status that is not PREFERRED. 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

DoorDash is a direct integration (Online Ordering and Drive). Uber Eats, Grubhub and SkipTheDishes require UrbanPiper or Deliverect middleware, which is separately paid. https://www.touchbistro.com/features/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

Both Deliverect and UrbanPiper are named as supported "Online Ordering Aggregator" endpoints on the vendor's own integrations page. https://www.touchbistro.com/features/integrations/ · retrieved 2026-08-01

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

Named vendor-listed accounting connectors: QuickBooks, Xero, Sage Intacct, Shogo, Restaurant365 and DAVO by Avalara. Depth of journal-entry mapping versus CSV is not stated for each. https://www.touchbistro.com/features/integrations/ · 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

Two named partners in the Staff Scheduling & Payroll category — Push Operations and 7shifts. Neither is a top-tier payroll bureau in the Gusto/ADP/Paychex/Paylocity sense, and none of those four is named. https://www.touchbistro.com/features/integrations/ · retrieved 2026-08-01

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

extensibility-app-marketplace

A public integrations directory exists with eight categories and ~25 named partners, browsable without login. But it is a marketing directory — there is no self-install flow, no listing terms, and no developer onboarding. https://www.touchbistro.com/features/integrations/ · 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

NEW SURFACE 2 (retired vendor API docs): 'Sous Chef' (https://raw.githubusercontent.com/sam-shore/sous-chef/fe5e5f90b13044908df4287b118ada1721f54e52/REST-API.md, read via api.github.com tree + raw, no clone) is a copy of TouchBistro's own repo: its commits (2016-10-21 to 2017-08-04) are by @touchbistro.com addresses, the README signs off 'Your friendly neighbourhood ... TouchBistro engineering and product team' and links github.com/TouchBistro/sous-chef, which api.github.com now returns 404 for. REST-API.md lists 19 endpoints, every one 'GET' and described 'Retrieve ...' (Menu, Bills, Bill, Bills (Extended), Summary, Drilldown, Sales by Day ... Shifts, Tax Summary) on cloud.touchbistro.com; auth is '<api_token>: The unique API Token associated with your TouchBistro Dev account. This will be provided to you by TouchBistro.' menus-to-go.md: 'Menus To Go is our private API for polling menu information for a particular venue' and 'That app can then poll the server directly via the above end-point' (GET http://<ip>:1337/getmenuformenuapp, 'no encryption and no authentication'). That API is RETIRED: cloud.touchbistro.com/api/v1/bills 301 -> admin.touchbistro.com -> 404 today. The README calls itself 'deliberately vague ... this isn't formal documentation', so it describes a 2016-17 read-only API, not today's partner API. The local server endpoint in menus-to-go.md served 'our self-serve app' (TouchBistro's own client) and was read-only, with no order-submit endpoint, so it is not a third-party headless mode. That API is retired. NEW SURFACE 1 (certificate transparency, 319th): crt.sh for touchbistro.com (2,680 cert rows), touchbistro.io (652) and touchbistro.net (385) gave 330 distinct non-wildcard hostnames; each was DNS-resolved and probed at / plus /swagger, /swagger/index.html, /swagger-ui.html, /swagger/v1/swagger.json, /api-docs, /v2/api-docs, /v3/api-docs, /openapi.json, /openapi.yaml, /docs, /redoc, /graphql, /robots.txt, /sitemap.xml and a nonsense-path control. A partner API tier EXISTS in CT (partners.api.touchbistro.io, staging./develop./integration.partners.api.touchbistro.io, partners.api.int.touchbistro.net, production.partners.api.int.touchbistro.net) but every one is NXDOMAIN today; the live API hosts (venue.api, ordering.api, payments.api, loyalty.api, legacy.api .touchbistro.io; api.touchbistro.io; api.touchbistro.net) return a 16-58 byte 404 on every doc path; no Swagger/OpenAPI/Redoc/GraphQL answered anywhere; schemas.touchbistro.com is S3 AccessDenied (not listable); marketingstaging/marketingdev.touchbistro.com WP REST is the same census as production (help-article 1012, integration 26, post 838; zero extra ids); Wayback CDX offline. The TouchBistro Cloud portal bundle (admin.touchbistro.com, Next.js buildId 334e477b7176c8f4b8c631216b16afe954c49a11, all 535 _buildManifest files, 19.1 MB, anonymous CloudFront) holds 0 'webhook' tokens and its 156 API path templates are the internal venue config API (server header 'TouchBistro venue:config:api'); the only integration calls are /v1/venues/{venueXRefID}/integrations/{integrationXRefID}/actions/enable|disable. That bundle is an internal client, not a partner contract, so it bounds nothing about the partner API. VERDICT: still unknown. Retrieved 2026-09-16. || 322nd: CLAIM: see taxonomy. NEW SURFACE (322nd, PUBLIC SOURCE MAPS): the TouchBistro Cloud portal admin.touchbistro.com (production; Next.js buildId 334e477b7176c8f4b8c631216b16afe954c49a11) serves a .js.map for every one of its 535 _buildManifest chunks anonymously (535/535 HTTP 200; nonsense-map control 404), 9,529 sources, 1,597 own (non-node_modules) files with sourcesContent, 10.8 MB (e.g. https://admin.touchbistro.com/_next/static/chunks/10029-f0511988be735f8c.js.map). Grade B for the portal only; it is an internal client of the venue config API and is not a census of TouchBistro's partner API. Controls over the 1,597 own sources: headless 0, 'embedded' 0 in any API sense, 'partner api' 0. VERDICT: still unknown. Retrieved 2026-09-17. || 327th: MERGE HOLD (proposed no/B, held unknown): Same unpublished-partner-API shape, and the agent flagged it as resting on synonym controls rather than a denial. PROPOSAL AS WRITTEN: 327th. CLAIM: a headless/embedded mode where a third-party UI drives the POS. VERDICT: no. BOUND: the WordPress census completed today to 100% of the publisher's /wp-json/wp/v2/types manifest (23 types, 254/254 pages, 28,730,675 chars, ~2,600 items incl. all 1,012 help-articles and all 26 integration records - the integration type is TouchBistro's own enumeration of what may connect to it, and every one of the 26 is a finished third-party product, not an embedding toolkit). CONTROLS with the vendor's own synonyms, tokenised: headless 0, 'white-label' 0, SDK 0, 'embedded POS' 0, 'developer portal' 0. POISON NAMED: 'white label' 1 hit is a barcode sticker on an iPP320 card terminal; 'embed' 64 and 'iframe' 6 are all marketing widgets (Calconic profit-margin calculators, an eCardSystems gift-balance iframe, a reservation widget), none of them a POS surface. CORROBORATION: the retired TouchBistro Sous Chef API was 19 read-only GETs, and its own README calls itself 'deliberately vague ... this isn't formal documentation'. Retrieved 2026-09-18. adversarially verified

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

Merchant Terms state that on termination "Merchant Content will, shortly thereafter, cease to appear on TouchBistro Services", with TouchBistro retaining archival copies for internal use. No documented machine-readable full historical export at contract end. https://www.touchbistro.com/terms-of-service/ · retrieved 2026-08-01

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

reliability-offline-order-entry

Verified on the vendor's own page with an explicit enumerated list: "Take and close orders," "Take offline payments and cash payments," "Send orders to your Kitchen Display System," print kitchen tickets and receipts; while offline you cannot "access reports and data or change your floor plan, menu, or staff permissions." This is the strongest offline evidence TouchBistro publishes, and it is a blog page, not product documentation. https://www.touchbistro.com/blog/what-is-a-hybrid-pos/ · retrieved 2026-08-01 adversarially verified

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

reliability-offline-card-auth

No offline AUTHORIZATION occurs. TouchBistro's own payments page describes pure store-and-forward: "This feature allows you to continue taking payments, storing the guest's credit card information offline. Once your Internet is back up and running, the stored payments will process." The blog adds "the transaction is stored on the payment device." No approval code is obtained at the table, no per-transaction or cumulative cap is published, and no liability statement exists. The dossier's supporting quote ("all of TouchBistro's payment partners have an offline payments mode") and the iPP320-v11/ https://www.touchbistro.com/touchbistro-payments/ · 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

Half the claim is met. Caps and windows are published: 'You can store up to 100 offline payments per Ingenico payment device. There is no dollar limit on what can be charged offline', and 'You should upload your stored transactions within 5 days.' The Payrix guide adds the decline lifecycle - 'Payments forwarded which then get rejected will be flagged as Declined', 'Declined transactions can be re-forwarded, although they will expire after 7 days', and TouchBistro 'will attempt to automatically upload offline payments every 30 minutes'. It also discloses the risk plainly: 'the system can only verify the expiry date and card number. It cannot check if the card is lost/stolen or has sufficient credit limit.' Shortfall: nowhere does TouchBistro state who bears the loss when a stored transaction declines after reconnect. The docs put the operational burden on the merchant ('You cannot currently remove failed or decline transactions from the summary screen'; print the slip and retry, since 'A card declined for insufficient credit may go through the next day'), and the Merchant Terms of Use (eff. 31 Mar 2026) sec. 11 disclaims all payment-processing liability to the processor, but no loss-allocation statement for offline declines exists in either document. https://help.touchbistro.com/s/article/touchbistro-payments-store-and-forward · retrieved 2026-08-06

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

The architecture is genuinely LAN-local, which the prior verification did not establish. Satellite iPads reach the Main Device directly on the restaurant network: 'Make sure your satellite iPads are connected to your TouchBistro network (the same network your main device iPad is connecting to)', and if discovery fails, 'Type the IP address and Port Number into the Connect Manually dialog box ... The default Port Number is 1337.' No cloud service sits in that path. TouchBistro's outage table ('What Can You Do with TouchBistro POS If Your Internet Goes down?') confirms LAN device-to-device traffic survives an outage - 'Take/close orders on your TouchBistro POS: Yes', 'Print kitchen tickets: Yes', 'Send orders to the Kitchen Display System (TouchBistro KDS or Fresh KDS): Yes' - while listing cloud-dependent functions (remote menu edits, online orders, real-time cloud reports, loyalty redemption, gift cards) as unavailable. Shortfall: TouchBistro nowhere states in terms that satellite iPads retain the shared check/table state through an internet outage; the outage table is phrased per-device ('your POS device'), and the vendor documents at least one condition that drops the whole mesh - on the TSYS Genius Mini setup page, 'you should not use this device with the iPad designated as the Main Device as the Mini invokes the TSYS payment app. If invoked on the Main Device iPad, all satellite iPads will be disconnected.' Shared multi-terminal state during degraded operation is strongly implied by the architecture but not affirmed by the vendor. https://help.touchbistro.com/s/article/Part-2-How-to-Connect-iPads-to-your-Main-Device · retrieved 2026-08-06

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

TouchBistro self-describes as a hybrid POS with local device-to-device operation, which implies a local transaction path. The specific architecture — designated master iPad versus edge server — is not formally documented in retrievable public material. https://www.touchbistro.com/blog/what-is-a-hybrid-pos/ · retrieved 2026-08-01

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

reliability-offline-kds-printing

Verified verbatim on the live page (re-read 2026-08-11): "Our offline mode ensures your KDS will continue working even when your internet is temporarily unavailable", and "Built-in redundancy features ensure that your devices can continue to talk to one another and orders can still be taken, even without internet." The claim is satisfied on its kitchen-display half; the page does not separately address kitchen PRINTER routing during an outage, which the claim admits via "and/or". The wording previously recorded here ("Built-in redundancy ensures the KDS continues functioning without internet connectivity") is not the page text and was already flagged as such by kitchen-offline-operation on this same page. Corrected, not withdrawn: the substance is published. https://www.touchbistro.com/kitchen-display-system/ · retrieved 2026-08-11

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

reliability-printer-fallback

The printer setup guide documents the remedy for an unreachable kitchen printer, and it is entirely manual: under 'How to Re-direct Order Tickets' - 'Tap the out-of-service printer. Tap Redirect All Menu Items to Printer. Select the printer you wish to use. Note: Tap Disable Printer Redirection once the printer starts working again.' No automatic fallback target is configurable: the same article enumerates the complete set of printer assignments (Global Receipt Printer, Global Reports Printer, Global Bartender Printer, Local Receipt Printer, Local Drink Printer) and none is a backup or failover role. Nor is there alerting. The article lists the complete set of messages - 'TouchBistro provides the following error messages: Cover Open, Disconnected, Paper Low, Paper Empty, Power Disconnected, Paper Feed In-Progress, Cutter Error, Drawer Open, Mechanical Error, Buffer Overflow, Unknown Error' - and the companion article says the operator must go and look: 'Tap Admin | Admin Settings. Tap Printers & Kitchen Displays ... With your cursor tap and swipe down with your finger to update the printer status(es)', with the advice to 'Make it a daily practice to check for printer errors before service.' Automatic failover with staff alerting is not present; the vendor's documented alternative is manual redirection after manual inspection. https://help.touchbistro.com/s/article/printers · retrieved 2026-08-06

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

The vendor publishes a declared-complete offline behaviour matrix and conflict resolution is not in it. The 2026 Product Guide introduces it as a ceiling — "Below is a full list of the features that are available or unavailable if you temporarily lose internet connectivity at your restaurant" — and the table's thirteen rows are per-feature Yes/No availability plus one sync note, "No (TouchBistro will sync all sales/labor data when the internet is restored)". Nothing states a last-write-wins, merge or operator-prompt rule for the same object edited on two devices during a partition. The matrix in fact removes most of the conflict surface by disabling configuration offline, answering "No" to "Change/edit menu", "Manage staff permissions" and "Edit floor plan" — but suppressing the edits is not documenting the resolution the claim asks for. `conflict` appears 10 times on product surfaces, none of it about sync. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Not an absence-based verdict: it rests on a self-declared-complete offline matrix, and both anchors are present under all three instruments - the introduction "Below is a full list of the features that are available or unavailable" and the sync row "will sync all sales/labor data when the internet is restored". Supporting controls over the cited PDF: conflict 0/0/0, last write wins 0/0/0, merge 0/0/0, sync conflict 0/0/0 including a proximity probe. The word sync is present 3 times in all three instruments and is the restore-on-reconnect note, not a resolution rule. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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

A dedicated help article "What Can You Do with TouchBistro POS If Your Internet Goes Down" exists and the vendor states report access is unavailable offline, but the full enumerated matrix could not be retrieved (the help centre is a JS-rendered Salesforce site) and is not published on the marketing site. https://help.touchbistro.com/s/article/What-can-you-do-with-TouchBistro-POS-if-your-Internet-goes-down · retrieved 2026-08-01

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

reliability-public-status-page

Upheld, and no longer resting on a failed DNS lookup. TouchBistro's own Support feature page describes the whole of what it offers when something breaks and it is people, not a page: "Our world-class support specialists, based out of North America, are available 24/7/365 to help with your TouchBistro products", with `status`, `outage`, `downtime` and `incident` each absent from it. A full census of the WordPress sitemap index on 2026-09-09 -- 2,232 URLs across post, page and help-article sitemaps -- contains no status, uptime, incident or trust page; the only near-miss is /feature-removal-status/, a deprecations page. AND THE ABSENCE IS OF A PUBLIC PAGE, NOT OF THE FACILITY: touchbistro.statuspage.io answers 200 and redirects to touchbistro.okta.com SAML, whereas two fabricated statuspage.io subdomains redirect byte-identically to atlassian.com/software/statuspage (127,605 b). TouchBistro therefore HAS a Statuspage tenant and has put it behind its own SSO, which is a different and sharper finding than "no status page exists" -- it is gated, and the claim asks for a public one. Grade C: a vendor feature page. https://www.touchbistro.com/features/support/ · retrieved 2026-09-09

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

Vendor claims 24/7/365 phone and email support included at no extra cost, and the pricing page states "free customer support is included." Heavily contradicted in practice: Capterra and BBB record persistent unresponsiveness, and BBB shows 43 of 51 complaints unanswered. https://www.touchbistro.com/pricing/ · retrieved 2026-08-01

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

An installation program exists and is contractual, not merely a marketing gesture. The Merchant Terms of Use (effective 31 Mar 2026), sec. 7 'Hardware and Professional Services': 'If Merchant orders any professional services under a Sales Quote, then, upon request from TouchBistro or its authorized service provider (collectively, the "Service Provider"), Merchant will promptly provide the Service Provider with any information, resources and assistance required by the Service Provider to enable the implementation of the TouchBistro Services and, if applicable, to provide training to Merchant.' Sec. 6 confirms these are billable line items - 'All pre-paid license, subscription, or other fees (including professional services such as installation and training) are non-refundable' - and the Terms define a 'Go-Live Date'. TouchBistro's ISO partner page states it performs the work first-party: 'Focus on maximizing your residuals while we handle the TouchBistro POS sale, installation, and merchant training - no revenue share, no hidden fees.' Shortfall: neither source says the installation is delivered in person on site rather than remotely, and TouchBistro publishes no certified dealer or installer network - the only reseller-facing programs are the ISO referral network (payments residuals, referral only) and the affiliate Partner Program, which states it 'is not intended for product integrations' and pays per demo and per sale. The in-person element of the claim is therefore unestablished. https://www.touchbistro.com/terms-of-service/ · retrieved 2026-08-06

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 KDS page states "Customized onboarding with professional services experts included" for that module. Whether initial POS menu build is performed by TouchBistro as part of standard onboarding is not documented — and reviewers cite poor onboarding and incorrect initial setup. https://www.touchbistro.com/kitchen-display-system/ · retrieved 2026-08-01

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

reliability-hardware-replacement-sla

No replacement or advance-exchange programme is offered or sold. `advance exchange` and `RMA` occur zero times corpus-wide. The vendor's hardware commercial surface is fully enumerated in the 2026 Product Guide FAQs — upfront hardware and implementation costs, the Essentials bundle with "hardware for $0 upfront", hardware financing "for venues with two or more terminals", no charge for support, no charge for software updates — and no replacement programme appears among the purchasable items. The Hardware FAQs cover supported models only, and the KB defers to the manufacturer's warranty. Residual: support terms in the signed Sales Quote are not public, so this is an absence on the published record rather than a contractual one. Measured over a 3,321-document corpus re-derived this pass and de-duplicated by URL: the 861-article current Salesforce KB, the 2026 Product Guide plus 13 sibling PDFs, 198 WordPress pages, 22 sitemap-only product pages, 1,012 archived 2021 help-articles, 117 content modules, 217 press releases, 840 industry blog posts, the 26-entry integration catalogue and a 14-document legal set. PDF INSTRUMENT AUDIT (311th pass, prompted by a pdftotext intra-word-space fault found on another corpus): the cited Product Guide PDF was re-fetched at HTTP 200 with %PDF-1.5 magic bytes, 11,746,919 bytes, Last-Modified 2026-08-11, and re-extracted three ways - pdftotext -layout, pdftotext with no flags, and a whitespace-squashed substring probe run over both. Positive controls pass in all three instruments, so the extraction is sound: TouchBistro 153, order 31 tokenised and 105 squashed, restaurant 40, payments 32. This document does NOT carry the intra-word-space fault: word-boundary counts are identical between -layout and no-flags for all 91 terms tested, and the only one-and-two-letter fragments -layout emits are apostrophe artefacts such as restaurant s website. The -layout instrument does however carry a DIFFERENT fault that was measured and is recorded here for every cell citing this file: it interleaves adjacent columns, so the strings Nutritional Information & Allergen Mapping, automated order suggestions for each vendor, and Multi-Location Staff Management are each present in the no-flags extraction but ABSENT from -layout. A phrase control run only over -layout can therefore read a false zero on this PDF. Every control below was re-run over all three instruments. Controls as measured over the cited PDF by all three instruments: advance exchange 0/0/0, return merchandise authorization 0/0/0, replacement 0/0/0, warranty 0/0/0. The enumerated commercial surface that carries the verdict survives the same instruments: hardware for $0 upfront and hardware financing are both present in all three, and no replacement programme appears among the purchasable items. POISON PUBLISHED: RMA reads 0 tokenised but 28 squashed in -layout and 29 in no-flags, every hit a fragment of labor management, information, thermal or performance. The existing residual about the non-public Sales Quote stands. The verdict stands. https://www.touchbistro.com/wp-content/uploads/2024/09/US-TouchBistro-Product-Guide-2026.pdf · retrieved 2026-09-15 adversarially verified

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

TouchBistro publishes no AoC, no trust centre and no P2PE listing of its own. Its only public security statement is in the Privacy Notice: 'TouchBistro takes precautions - including administrative, technical, and physical measures - to safeguard your personal information ... TouchBistro Services use Secure Sockets Layer (SSL) encryption and/or other features where personal information is collected', followed by 'we cannot guarantee the security of your personal information transmitted to our Websites.' No certification, standard, assessor or attestation is named anywhere in it; the strings 'PCI', 'SOC 2', 'certification' and 'attestation' do not occur. Probed 2026-08-06: touchbistro.com/security/, /trust/, /compliance/, /security-and-compliance/ and /responsible-disclosure/ all return 404; the site footer offers only Privacy Notice, Terms of Use, SMS Terms, Accessibility, Responsible Disclosure and Code of Conduct. The Merchant Terms of Use (eff. 31 Mar 2026) contain zero occurrences of 'PCI'. Across all 773 mirrored help.touchbistro.com articles the only PCI reference is about a third party's hardware - 'Both versions are PCI compliant', of the TSYS Genius Mini reader - which is a PTS device statement, not a TouchBistro attestation covering the post-March-2025 future-dated requirements. https://www.touchbistro.com/privacy-notice/ · retrieved 2026-08-06

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 fully documented on both platforms (Staff | Roles with per-permission toggles and per-venue scoping; POS Staff Types). Cloud authentication is not: setting up a POS+Cloud account enumerates the whole credential set - "enter a valid email address the staff member can access. This is used as the staff member's Cloud login Username. The staff member will need to access this email to complete their set up (including choosing a password for login to Cloud)" - and the profile guide's only security control is Update Password, with "you can view your four-digit passcode but you cannot modify it". POS access is a four-digit passcode. No second factor, step-up or SSO option appears in either guide or anywhere in the 844-article help centre index. https://help.touchbistro.com/s/article/How-To-Set-Up-User-Accounts-for-Staff-for-Cloud-and-POS-Login?language=en_US · retrieved 2026-08-08 adversarially verified

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

reliability-self-serve-training

A public Customer Hub and help centre provide "helpful guides, videos, step-by-step tutorials, and live workshops" free of charge. A practice/training mode on the terminal itself is not documented, and reviewers criticise training material quality. https://www.touchbistro.com/customer-hub/ · 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

TouchBistro's architecture has a single designated Main Device (an iPad or a Mac running Pro Server) that satellite iPads connect to on the LAN, and reassigning that role is an explicitly manual, human-authorised operation: 'This process moves all your restaurant data to a different iPad already on your network. Tap Admin | Admin Settings on the iPad you wish to make your Main Device. Tap POS Connectivity | Manage Connected Devices. Tap Set iPad as Main Device. In the Manager Confirmation window type your Admin Passcode. Tap Continue.' The Manage Connected Devices screen is the complete role-management surface and its documented options are Log Off iPad, Log Out All Other iPads, Disconnect iPad From Restaurant, Transfer Main Device Data to Mac and Set iPad as Main Device - no automatic election or standby role among them. Because the procedure moves the restaurant data set from the current Main Device, it presupposes the primary is reachable rather than failed. The published recovery path for a lost primary is a restore instead: 'Tap Restore from Your Account ... Confirm this is the restaurant you want to download and tap Restore' (starting-your-restaurant-if-you-do-not-have-device-linking), or on Pro Server, Support | Restore Backup with the caveat 'You will lose any data acquired since the backup you are restoring.' No terminal assumes the master role automatically. https://help.touchbistro.com/s/article/making-a-different-ipad-your-main-device · retrieved 2026-08-06

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

reliability-cellular-backup

Cellular connectivity is documented, but as a primary link and never as an automatic failover. In every food-truck reference build TouchBistro specifies 'a standard TouchBistro-supported Z3 Wi-Fi router wired to cellular LTE router to supply Internet connectivity. The LTE router is sourced by you', with suggested hardware 'ZTE MF275R Turbo Hub in Canada, Nighthawk LTE Mobile Hotspot Router in the USA'. The supported-iPad guide is explicit that iPad cellular is a substitute for that router, not a backup behind it: 'we only recommend iPads with cellular support for simple food truck setups that lack a cellular router.' Shortfalls: the LTE hardware is sourced by the operator, not supplied or supported by TouchBistro; it is positioned as the sole WAN rather than a standby; and TouchBistro documents no cutover behaviour, no failover configuration and no detection or fallback logic anywhere - the supported-router page states 'TouchBistro will only support the Cisco Meraki Z3/Z4/Z4C line of routers' and describes only monthly data usage, with no failover configuration. Automatic terminal-level LTE failover is not a documented TouchBistro capability. https://help.touchbistro.com/s/article/food-truck-setup · retrieved 2026-08-06

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

Pricing is presented as "$69/month" and "$119/month" but no term is stated on the pricing page. The Merchant Terms define an Initial Term set in the private Sales Quote. Merchant Maverick reports month-to-month is standard while discounted custom rates come with one-year commitments; BBB complainants describe multi-year terms. Not a publicly guaranteed month-to-month offer. https://www.touchbistro.com/terms-of-service/ · 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

Verified in the Merchant Terms: on default TouchBistro recovers the full incentive amount, all outstanding fees, and "the entire amount of any software license fees, hardware fees or payments... which would have been payable... during the balance of the then current term." Liquidated damages, as scored. Auto-renewal for a period equal to the Initial Term with 30 days' notice also verified. https://www.touchbistro.com/terms-of-service/ · retrieved 2026-08-01 adversarially verified

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

Publicly stated: auto-renews "for a period equivalent to the period of the Initial Term" absent written notice "at least thirty (30) days prior to the end of the then current term." The renewal length itself is defined by reference to the private quote. https://www.touchbistro.com/terms-of-service/ · retrieved 2026-08-01

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

commercial-processing-not-bundled

Admin guide "Using Your Payments Screen" (updated 2026-03-20): "You have to register with a Payment Gateway (e.g., TouchBistro Payments) before you begin" - the operator taps "the Payment Gateway you contracted with", taps Setup and enters "the information provided by the Payment Gateway company (e.g., ID, password, keys, tokens)". The same guide documents Non-Integrated Card Types for merchants using "a credit card payment solution external to TouchBistro", added by card type for reporting and surfaced by enabling Show Non-Integrated Payment Options. The processor support matrix names TB Payments, Chase USA and TSYS in the USA and Chase Merchant Services, TD and Moneris in Canada, with Worldpay triPOS documented separately. No documented requirement to use in-house processing; note that feature parity is not equal across gateways (offline payments, bar tabs and pre-auth tipping are unsupported on several). https://help.touchbistro.com/s/article/payment-gateways?language=en_US · retrieved 2026-08-06 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

Re-retrieved live 2026-08-06. The vendor claims the structure and withholds every number. The TouchBistro Payments FAQ answers "What payment processing rates will I be charged?" with "TouchBistro Payments leads the marketplace with an innovative cost plus pricing model. This is the most transparent and equitable pricing model available, with easy-to-understand terms and fees", and the page markets "transparent pricing" twice. No basis-point markup, no per-transaction figure and no flat rate appears here, on /features/payment-processing/ (whose FAQ says rates "vary" and are set as "a custom rate" by payment partners), or on /pricing/, where Payments is priced "Get a Quote". Claiming cost-plus is not publishing the markup, which is what this claim requires. https://www.touchbistro.com/touchbistro-payments/ · retrieved 2026-08-06 adversarially verified

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

The published agreement does the opposite of capping increases, and the exit it grants is not on the increase. Merchant Terms of Use §2 (Fees; Charges; Taxes): "Except as expressly provided in the applicable Sales Quote, TouchBistro reserves the right to change the fees for TouchBistro Services upon thirty (30) days’ prior written notice to Merchant." No cap, no ceiling, and no interchange-only carve-out. The objection route runs to the end of the term rather than out of it: a dissenting merchant "may cancel its Merchant account with TouchBistro effective upon the expiration of the then current term of the Merchant’s TouchBistro Services Agreement", with the old fees held in the interim ("the fees in effect prior to the fee change notice will remain in force"), so the merchant must serve out the committed term. `increase` occurs zero times in the 68,847-character Terms. Residual: card processing rates sit in the unpublished HPP Agreement and the Sales Quote, so no cap can be examined there either. Nine other legal paths — including /sla/, /dpa/ and /api-terms/ — 404 at exactly 60 bytes, byte-identical to a fabricated control. https://www.touchbistro.com/terms-of-service/ · retrieved 2026-09-10

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

Per-location software is published ($69/mo POS, $119/mo Essentials with hardware) and Reservations is published at $229/mo. But per-additional-terminal pricing is not published, the third tier is quote-only, and ten of eleven add-ons show "Get a Quote" with no dollar figure. https://www.touchbistro.com/pricing/ · retrieved 2026-08-01

Individual modules (online ordering, KDS, loyalty, inventory, payroll, marketing) can be purchased à la carte and cancelled independently without repricing the base POS subscription. differentiator

commercial-module-unbundling

Modules are explicitly sold as separate add-ons on top of the base POS, so à la carte purchase exists. Whether one can be cancelled independently without repricing the base subscription is not documented — and BBB/Capterra complaints centre on the difficulty of cancelling anything. https://www.touchbistro.com/pricing/ · retrieved 2026-08-01

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

Hardware can be purchased (financing offered for 2+ terminals) rather than only leased, but no published price for any terminal, KDS screen or printer, so the "published price" half of the criterion fails. https://www.touchbistro.com/pricing/ · 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

The iPad half is true, but the KDS page states flatly: "TouchBistro KDS requires MicroTouch Touchscreens (15.6\" or 21.5\") that must be purchased through TouchBistro, installation fees will apply." That is explicit hardware lock-in with a mandatory vendor purchase channel on a core module, plus a fee the pricing page never mentions. The researcher's blanket "non-proprietary, third-party sourceable" is wrong for anything beyond the POS tablet, and card readers are processor-bound. https://www.touchbistro.com/kitchen-display-system/ · retrieved 2026-08-01 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

Self-serve export is real and documented, but not as a full-history dump. Cloud Reporting: "On most reports, you will see a Get this report drop-down box... If you select Download you have the option to download the report in a CSV or XLS format," and Scheduled Reports lets an operator pick "CSV (a generic comma-separated values format) or XLSX" on a Daily/Weekly/Every 2 Weeks/Monthly cadence to arbitrary email recipients - no support ticket, no stated fee. Coverage of the four data classes is documented in the Index of Cloud Reports: line items in Sales | Detailed Sales (Order ID, Order Item ID, Bill Number, Menu Item ID, Quantity, Base Price, Pre-tax Amount, Total Amount, Discount Amount, Is Voided, Sent Time, Paid Time, Server, Table name), payments in Payments | Payments (Bill Number, Order Number, Bill Date, Payment Method, Transaction Total, Tip, Cash Tips), and labor in Labor | Timesheet Details (Clock-In, Clock-Out, Reg./OT hours, Gross Pay). The named shortfalls: the line-item export is capped at a single day - "The Detailed Sales CSV has a large amount of sales data. You can only generate this data for one selected sales day" - so extracting a year of line items means 365 manual exports; the custom date range on other reports goes back "as far as 3 years"; and there is no public API to automate any of it (developer/api/docs.touchbistro.com do not resolve and no developer portal is linked from either host), so the documented-API alternative in the claim is unavailable. https://help.touchbistro.com/s/article/sales-reports?language=en_US · retrieved 2026-08-08

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

All three components are documented as operator-run CSV exports. Guest records: in Guest Engagement | CRM, after filtering the guest list, 'Click Export if you want to export this search as a CSV file.' Loyalty point ledger: the Guest Engagement reports are 'download only as CSV files', and the Point Earnings report's columns are Earned ID, 'Guest Name/Email/Phone', 'Points Earned', 'New Point Balance' ('The account's balance after the transaction'), date/time and venue - a per-transaction ledger with running balance, alongside a Reward Redemption report carrying points spent per redemption. Gift-card balances: the Digital Gift Card Usage report reports 'funds added and funds used' with columns Gift Card Reference Id, Credit Amount, Debit Amount, 'Previous Balance', 'New Balance', Type (purchase, redeem, or refund), Origin, Bill Number and purchaser/recipient contact details. Caveat on scope, not on capability: these reports require a Loyalty, Marketing or Digital Gift Cards subscription and are visible only to Admin or Analyst roles, and the gift-card export covers TouchBistro Digital Gift Cards - physical gift-card programs run on the processor (TSYS, Worldpay, Moneris) report through that processor's tooling. https://help.touchbistro.com/s/article/How-to-View-Guest-Engagement-Reports · retrieved 2026-08-06

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

Verified: merchant content "will, shortly thereafter, cease to appear" on termination, TouchBistro retains archival copies "for our internal business purposes," holds an "irrevocable, perpetual, worldwide, transferable, non-exclusive, royalty-free, and sublicensable" licence to merchant content, and owns all aggregated disidentified data. No retrieval window anywhere. https://www.touchbistro.com/terms-of-service/ · retrieved 2026-08-01 adversarially verified

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

Merchants retain ownership of Merchant Content — but grant TouchBistro a perpetual, irrevocable licence to use it, and TouchBistro outright owns "Aggregated Deidentified Data" derived from User Content and may use it for any lawful purpose indefinitely. Ownership is nominal; use is not meaningfully constrained. https://www.touchbistro.com/terms-of-service/ · 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

Tokenization is documented first-party. The TouchBistro Payrix portal guide lists an Account Updater standard report that 'Checks for and provides a list of all updates to stored, tokenized credit cards on merchant account(s)' - so cards handled through TouchBistro Payments are vaulted as tokens rather than stored as PANs. Hardware-encrypted entry is implied by the reader estate: card entry happens on processor-supplied PIN pads and readers (Payrix Lane/3000 and Link/2500, Moneris Go A35 / Move 5000 / V400, Ingenico iPP320, TSYS Genius Mini, Verifone MX 915/925), and of the Genius Mini TouchBistro says 'Both models support EMV (chip) and tap (contactless) payment types, as well as traditional card swipes. Both versions are PCI compliant.' Shortfalls: (1) TouchBistro publishes no validated P2PE solution listing of its own and does not identify any listed P2PE solution used by its processors - the phrase 'P2PE' occurs zero times across all 773 mirrored help.touchbistro.com articles and zero times in the Merchant Terms of Use (eff. 31 Mar 2026); (2) TouchBistro nowhere names the merchant's applicable SAQ type, so the claimed scope reduction to SAQ A or SAQ P2PE-HW is not asserted by the vendor; (3) touchbistro.com/security/ and /trust/ return 404 and the Privacy Notice's security section names only SSL, so there is no architecture statement to read. https://help.touchbistro.com/s/article/Using-Your-TouchBistro-Payrix-Portal · retrieved 2026-08-06

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

The staff account guide is the entire credential-configuration surface and it enumerates every option on the Add screen. For a POS-only account the credential is 'Passcode: This is automatically generated although you can manually customize it to a preferred 4-digit passcode. The code must be unique for the venue.' For a POS+Cloud account the Cloud credential is the staff member's email address as 'Cloud login Username' plus a password they choose from a setup email, and 'the passcode cannot be used to log into the Cloud and the email cannot be used to clock into the POS'. No second-factor option appears among the enumerated fields or role settings, and there is no separate authentication-settings article: the strings 'MFA', '2FA', 'multi-factor', 'two-factor' and 'authenticator' occur zero times across all 773 mirrored help.touchbistro.com articles. A shared 4-digit venue-unique passcode is definitionally single-factor, so MFA for all access to the cardholder data environment including POS logins is not in effect. The payment-page half is likewise unaddressed: no statement of script-integrity monitoring or change-detection for the TouchBistro Online Ordering / Customer Web App payment pages per Req 6.4.3 or 11.6.1 exists in the help centre, in the Merchant Terms of Use (eff. 31 Mar 2026, zero occurrences of 'PCI'), or on any security page - touchbistro.com/security/, /trust/ and /compliance/ all return 404. https://help.touchbistro.com/s/article/How-To-Set-Up-User-Accounts-for-Staff-for-Cloud-and-POS-Login · retrieved 2026-08-06

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

Re-verified on the current privacy notice. TouchBistro operates a privacy rights portal (a Privacy Request Form for California residents, at /privacy-rights-form/) and names a Privacy Officer with email, phone and postal address; it grants access, deletion, correction and portability rights under CPRA and, for EEA/UK residents, access, rectification, erasure, restriction, portability and objection, with further named rights for Nebraska, Texas and Nevada residents. That is TouchBistro acting as controller of its own data. Merchant-facing shortfall unchanged and re-confirmed against the new text: no in-app DSAR tooling for an operator to locate, export or delete an individual guest's records is described, no executable DPA is published or referenced anywhere in the notice, and the notice pushes merchant data practices away - "our Merchants are independent third parties that maintain their own business practices and policies that are separate from their relationship with us". https://www.touchbistro.com/privacy-notice/ · retrieved 2026-08-08 adversarially verified

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

TouchBistro publishes an accessibility document set - the /accessibility/ hub linked from the site footer, plus its Accessibility Policy and Multi-Year Accessibility Plan - and it is entirely an AODA compliance programme, not a product conformance report. It contains no VPAT, no ACR, and no conformance claim at WCAG 2.1 AA or later. The highest commitment made is for the corporate website and to an older standard: "We will work towards meeting internationally recognized Web Content Accessibility Guidelines (WCAG) 2.0 Level AA website requirements in accordance with Ontario's accessibility laws by Jan 1, 2021", with the policy and plan themselves posted "in an accessible format that conforms with, at minimum, WCAG 2.0 Level A." On kiosks the policy commits only to intent: "TouchBistro will consider accessibility features when designing software updates in our iPad POS system and self-ordering kiosks." No tactile or audio non-visual access mode is documented, and no conformance claim covers the consumer web-ordering surface. https://www.touchbistro.com/accessibility/policy/ · retrieved 2026-08-06 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

Cash discounting is supported and documented, and in the Menu Management path it behaves like dual pricing at the point of sale: 'If your prices have a credit card fee built into them, you can offer customers automatic discounts if they pay with cash ... On the Order screen you will see the cash total with the discount applied. Likewise on the Checkout screen you will see the cash amount.' The legacy path is a manually applied discount - 'Tap Checkout. Tap Discount/Comp All Items. Tap Cash Discount' - and TouchBistro describes the surcharge direction as a workaround rather than a feature: 'posting prices as cash prices and then using an auto-grat to charge a "bump up" for customers who want to pay with a credit card.' Shortfalls: (1) the mechanism is a percentage discount scoped by Menu Group and Staff Type, with no awareness of card type, so there is no automatic exclusion of debit or prepaid cards from any surcharge - an auto-gratuity cannot see the BIN; (2) no receipt or menu-board disclosure handling is provided or documented; (3) TouchBistro contractually disclaims the entire compliance surface. Merchant Terms of Use (eff. 31 Mar 2026) sec. 12 Surcharges: TouchBistro 'does not determine whether Merchant may impose a surcharge, processing fee, or similar fee ... does not set the amount of any Surcharge, and does not provide legal advice regarding Surcharges', and the Merchant 'is solely responsible ... for ensuring that any Surcharge complies with all applicable law, regulations, and payment network rules and instructions (including any required notices, registrations, disclosures, signage, receipt requirements, prohibitions, and any caps or limitations on the amount of a Surcharge)'. https://help.touchbistro.com/s/article/cash-discounting · retrieved 2026-08-06