TouchBistro

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-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

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

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

order-capture-bar-tab-preauth differentiator

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

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

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

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

order-capture-qr-same-check differentiator

Checked the complete help.touchbistro.com corpus - all 844 URLs in /s/sitemap-topicarticle-1.xml and -weekly.xml, 765 unique articles, retrieved with a Googlebot user agent because the Salesforce Experience Cloud site serves a shell otherwise. Every documented guest ordering path is a separate order object: TouchBistro Online Ordering and DoorDash orders arrive in Orders | Online Ordering as pending/ASAP takeout or delivery tickets (DoorDash-Understanding-the-Server-Experience, touchbistro-online-ordering-diner-experience), and the Order screen articles describe only server-entered items. Every QR reference in the corpus is for something else: loyalty scanning, digital/physical gift-card scanning, satellite-iPad pairing and manager-approval QR. The "QR Code Menu" named in the touchbistro.com navigation is a marketing menu-hosting tool, not an ordering surface, and www.touchbistro.com/page-sitemap.xml and feature-sitemap.xml contain no QR ordering page. That is absence of any at-table QR ordering documentation rather than an exhaustive enumeration ruling one out, so the same-check question is unresolved.

order-capture-kiosk-first-party differentiator

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

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

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

order-capture-voice-ai differentiator

Checked all 765 unique help.touchbistro.com articles (sitemap-enumerated, Googlebot UA): no voice, telephony or AI-ordering article exists, and the App Marketplace integration list (chapter-11-integrations) has categories for Reservations, Loyalty/Marketing, Gift Cards, Scheduling, Accounting, Inventory, Online Ordering, Bar Management, Analytics and Insurance - none for voice. On www.touchbistro.com, feature-sitemap.xml lists nine feature pages (integrations, support, payment-processing, staff-management-scheduling, floor-plan-table-management, tableside-order-management, reporting-analytics, ipad-menu-management) with no voice page, and page-sitemap.xml (99 pages) contains no developer, API or partner-program page; /partner-program/ returns 404 and only /iso-partnerships/ and /partner-offer/ (reseller/affiliate pages) exist. No public API reference or webhook documentation was found on either host. The App Marketplace is an integration directory and the feature sitemap is a marketing roundup, neither of which qualifies as an exhaustive enumeration under the evidence rules, so this stays unknown rather than no.

order-capture-throttling differentiator

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

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

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

order-capture-order-ready-signal differentiator

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

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

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

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

menu-pricing-fractional-placement differentiator

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

menu-pricing-half-and-half-rule differentiator

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

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

menu-pricing-size-style-matrix differentiator

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

menu-pricing-included-allowance differentiator

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

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

menu-pricing-upsell-prompts differentiator

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

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

menu-pricing-countdown-auto-86 differentiator

"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

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

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

menu-pricing-dual-pricing differentiator

"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

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-pricing-recipe-linkage differentiator

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

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

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

payments-processor-choice differentiator

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

payments-published-rates differentiator

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

payments-dual-pricing differentiator

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

payments-surcharge-guardrails differentiator

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

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

payments-softpos-tap-to-pay differentiator

"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

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

payments-qr-guest-pay differentiator

Read the payment documentation across the Googlebot-UA mirror of all 765 help.touchbistro.com articles. The v12 Checkout guide (help.touchbistro.com/s/article/checkout) walks the whole checkout surface - split by seating, split evenly, Discount/Comp All Items, Promo Code, Service Charges, Tax Exclusions, Add Note, quick-pay tender buttons, Cash, integrated payment options, Pay on Account, receipt options and penny rounding - and never mentions a QR on the guest check or a guest-device payment page; it introduces payment options by example ("Tap a payment option. For example Cash or an integrated payment option") rather than exhaustively, so it does not settle the question. Every QR reference in the corpus is for a different purpose: loyalty Customer Web App scanning, digital and physical gift-card redemption, satellite-iPad pairing, staff login and manager approval. The bill/guest-check customization article (Admin Settings | Bill & Order Tickets) shows no QR element. Guest-initiated payment from a phone is documented only through TouchBistro Online Ordering, which creates its own order rather than paying an open POS check. No pay-at-table QR product page exists in www.touchbistro.com/page-sitemap.xml or feature-sitemap.xml.

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

payments-tip-pooling differentiator

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

payments-offline-store-and-forward differentiator

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

payments-offline-decline-liability differentiator

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

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

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

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

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

payments-chargeback-tooling differentiator

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

payments-card-on-file differentiator

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

payments-payout-timing differentiator

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

payments-p2pe-pci4

Searched the complete Googlebot-UA mirror of help.touchbistro.com (all 844 sitemap URLs, 765 unique articles) for PCI, P2PE, point-to-point, DSS, attestation and encryption: the only hits are the Moneris iPP320 terminal setup guide, where "On the Mode screen, press F1 to scroll and select PCI" is a device mode selection, not a compliance statement. No trust, security or compliance article exists in the help centre. On www.touchbistro.com, page-sitemap.xml lists 99 pages with no security, trust, PCI or compliance page - /security/ and /pci-compliance/ both 404; /security-hall-of-fame/ and /vulnerability-disclosure/ are a researcher-credit page and a vulnerability-reporting policy (PGP key, report to a security mailbox) and say nothing about PCI DSS or P2PE. The Privacy Notice's only security statement remains "TouchBistro Services use Secure Sockets Layer (SSL) encryption and/or other features where personal information is collected." The Terms of Service and Dine terms and conditions contain no PCI or P2PE clause. Merchants transact through third-party processors and their terminals (PAX, Ingenico, Moneris, Chase, TSYS), whose own listings were not treated as evidence for TouchBistro. Absence of a published attestation is not evidence that one is unavailable on request, so this stays unknown.

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

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

kitchen-course-firing differentiator

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

kitchen-prep-time-pacing differentiator

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-order-throttling differentiator

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

kitchen-channel-pause-propagation differentiator

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

kitchen-order-ready-callback differentiator

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

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

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

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

kitchen-printer-fallback differentiator

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

kitchen-offline-operation differentiator

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

kitchen-item-build-screens differentiator

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

kitchen-pizza-fractional-display differentiator

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

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

kitchen-order-modification-alerts differentiator

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

kitchen-guest-ready-notification differentiator

Re-examined on 2026-08-06 against the full help.touchbistro.com corpus (765 unique articles, Googlebot UA) and downgraded from no. The evidence genuinely available is: the Online Ordering alerts article documents an acceptance email/SMS and a cancel-or-decline email/SMS and mentions no completion alert; the Fresh KDS bump is documented as "You can close a ticket by tapping on its X button" with closed tickets moved under Recall and no outbound event named; the POS completion step is "Tap the order and then tap Complete when the order is ready for pick-up or delivery", after which the order moves to Closed Bills with no alert described; and the Customer Facing Display's configurable surface is enumerated as Logo, Message of the Day, Welcome Screen, Payment Screen, Font Color, Font Size, Brand Color and Show Takeout, which makes it a per-terminal order/payment mirror rather than a status board. That last item is a real settings-screen enumeration and does dispose of the display-board leg. But the alerts article is a prose FAQ that never asserts it lists every alert, and the app-push leg is unaddressed by any enumeration -- TouchBistro publishes a Customer Web App that diners install to an iPhone or Android home screen, and nothing documents whether it can notify. Absence of a documented order-ready notification across the corpus is a failed search, not positive evidence of absence, so this is unresolved rather than no.

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

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

kitchen-prep-forecasting

Checked, unresolved -- not unexamined. I mirrored the full help.touchbistro.com/s/ sitemap (sitemap-topicarticle-1.xml plus the weekly file, 844 English article URLs) via a Googlebot user agent and searched every article body for 'prep list', 'par level' and 'forecast': zero hits. The closest documented artefact is the Low Stock Ingredients Report in the legacy Ingredient-Based Inventory System (/s/article/setting-using-touchbistro-ingredient-based-inventory-system), which "estimates how many menu items you can still make and serve based on existing ingredient inventory" -- a stock-runway figure, not a predicted prep quantity, and not surfaced to kitchen staff as a task list. Neither KDS product exposes a prep-list view: the enumerated Fresh KDS options (/s/article/Using-TouchBistro-KDS-Powered-by-Fresh) are Order Type, Prioritize, Order Type Colors, Split/Merge, Add Note, Fulfillment Times, Modifier Styles, Summaries and All Day Counts. TouchBistro's separately sold Inventory Management add-on is marketed on touchbistro.com/inventory-management/ as forecasting usage, but that is a marketing page (grade D at best) and no product documentation for it is publicly retrievable -- it has no presence in the help centre. The doc set is silent rather than negative, and a help-centre search returning nothing does not meet the bar for `no`.

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

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

delivery-route-map differentiator

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

delivery-driver-tracking differentiator

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-zones-polygon differentiator

"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

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

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

delivery-driver-comp differentiator

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

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

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

delivery-daas-fallback differentiator

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

delivery-3p-direct-integration differentiator

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

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

delivery-menu-push

Menu publishing to marketplaces is a function of the middleware layer (Deliverect/UrbanPiper), not of a TouchBistro master-menu push. Channel-specific markups not documented. https://www.touchbistro.com/features/integrations/ · retrieved 2026-08-01

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

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

delivery-3p-reconciliation differentiator

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

delivery-injection-error-visibility differentiator

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

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

delivery-promise-time differentiator

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

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

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

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

digital-native-app differentiator

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

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-upsell-engine differentiator

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

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

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

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

digital-kiosk differentiator

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

digital-group-ordering

Checked help.touchbistro.com (Googlebot-rendered Salesforce site): the 844-article sitemap contains no article on group, shared-cart or party ordering; the four-step Online Ordering setup series (Hours of Operation, Pickup, Delivery, Advanced Settings, Page Activation) and the end-to-end diner walkthrough describe a single-cart, single-payer flow with no shareable participant link, no per-person or total spend cap and no multi-payer split. Page Activation offers only two distribution artifacts, an HTML button snippet and a direct order.tbdine.com URL. Absent any vendor doc asserting its own completeness over the ordering feature set, this is unresolved rather than a finding of absence.

digital-catering-portal differentiator

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

digital-voice-ai-phone differentiator

Checked the App Marketplace integration list on help.touchbistro.com (chapter-11-integrations), which enumerates the partner categories Reservations, Loyalty/Marketing, Gift Cards, Scheduling (7shifts, Push Operations), Accounting (TouchBistro Profit Management, Shogo, DAVO), Inventory (MarketMan, Optimum Control, Restaurant365), Online Ordering, Bar Management (Craftable, Wisk, Bevcheck, Freepour), Analytics (Avero) and Insurance (Coverdash) - no voice or telephony category - plus touchbistro.com/online-ordering/ and /features/payment-processing/, neither of which mentions AI phone ordering. Third-party voice vendors (Loman, Goodcall) advertise TouchBistro integrations on their own marketing sites, which is their claim, not a TouchBistro-named certified partner, and I did not retrieve any TouchBistro page naming them. App directories are near-universally incomplete, so this stays unresolved.

digital-drivethru-ai

Checked the full 844-article help.touchbistro.com sitemap: the only 'drive' matches are DoorDash Drive (third-party delivery dispatch), and no article - order screen, hardware, KDS or menu guide - describes a drive-thru lane, lane timer, lane display or lane-side ordering. touchbistro.com/online-ordering/ describes pickup, delivery, kiosk and tableside touchpoints only. No TouchBistro document enumerates supported service modes or venue types, so the absence of a drive-thru product is strongly suggested but not positively established, and an AI lane assistant cannot be scored either way.

digital-sms-ordering

Checked the Online Ordering customer-alerts article on help.touchbistro.com, which scopes SMS to transactional order status: "All diners will receive email alerts. They can also choose to receive SMS alerts... The diner will have to authorize SMS communication every time they order", covering acceptance and cancel/decline alerts only. TouchBistro Marketing's documented send channels are Email through the operator's SendGrid account and In-App Messaging to the Customer Web App. No text-to-order, text-a-link or conversational chat ordering article exists in the 844-article sitemap. Unresolved rather than absence, because no doc enumerates the vendor's ordering channels.

digital-google-order differentiator

Checked the Page Activation section of the Online Ordering setup guide and the dedicated 'Linking Your Online Ordering Page to Your Restaurant Website and Social Media' article on help.touchbistro.com. Both describe only two distribution resources - a copyable HTML button snippet in several sizes and the direct order.tbdine.com URL - and instruct the operator to paste that URL by hand into a profile's Website field: "You can, for example, post this in your restaurant's Facebook page or your Google business page." That is manual link placement, not Order with Google provisioning of the ordering link into the Google Business Profile as an ordering option, and nothing addresses the 'Preferred by Business' setting. No article in the sitemap mentions Order with Google. The linking guide scopes itself to websites and social media rather than enumerating every placement, so this is unresolved.

digital-apple-business-connect

Checked the same Page Activation and 'Linking Your Online Ordering Page' documentation on help.touchbistro.com (HTML button snippet plus direct order.tbdine.com URL, manually placed) and searched the 844-article sitemap: no article mentions Apple Business Connect, Apple Maps place cards or an 'Order Food' custom action - Apple-named articles all concern Apple ID setup for the iPad. Because the linking guide addresses only websites and social media and does not claim to enumerate ordering-link placements, this is unresolved rather than a finding of absence.

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

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

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

digital-guest-data-ownership differentiator

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-pci-sca

Checked touchbistro.com/touchbistro-payments/ and touchbistro.com/features/payment-processing/ - neither mentions PCI DSS, tokenization, hosted fields, encryption or 3DS - and the help.touchbistro.com article set, including security-settings (which is POS passcode and warning configuration, not payment security) and supported-payment-processor-integrations. Structurally the first-party ordering checkout is a vendor-hosted page on order.tbdine.com that merchants link to with a button snippet or URL rather than embed, so card data does not touch the restaurant's own page; card entry, tip control and the accepted brands (Visa/Mastercard/American Express/Visa Debit/Discover) are described in the diner-experience guide. But TouchBistro publishes no retrievable PCI DSS 4.0 statement, no position on the March 2025 client-side script-integrity requirements and no 3DS support statement, so the claim as worded is unresolved.

digital-surcharge-transparency differentiator

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

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

guest-loyalty-thirdparty-identity-attach differentiator

Checked the DoorDash Marketplace server-experience and diner-experience guides and the DoorDash integration guide on help.touchbistro.com. Marketplace orders land on the POS under Orders | Online Ordering identified by "the DoorDash logo and the DoorDash order ID number associated with it... on the order tile on the left side of their screen, as well as the bill preview" with a DELIVERY or PICKUP icon, are pre-paid "via the App or web page", and are closed by tapping Complete; no guest name, email or phone capture into the Guest Engagement CRM is described anywhere in the flow. The CRM guide defines its Guest List as "all guests who have redeemed a reward or checked in", which a marketplace order does neither - suggestive, but no TouchBistro document states that marketplace orders cannot attach to a native guest profile, so this stays unresolved.

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

guest-loyalty-tiers differentiator

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

guest-loyalty-offline-behavior differentiator

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

guest-loyalty-offer-stacking-rules differentiator

Checked the Rewards, Promotions, Menu Management Discounts and Menu Management Promotions guides on help.touchbistro.com. What exists is eligibility scoping, not stacking configuration: rewards carry Prohibited Groups/Items (check discounts) or Applicable Groups/Items (item discounts), day/time availability windows and per-venue scope; promotions carry # Days Until Expiration and Quantity Per User (or Unlimited); POS discounts carry menu-group scope and staff-type restrictions. Behaviourally discounts do co-apply - the diner Checkout screen "will display any automatic menu item discounts (1), any automatic bill discounts (2), and any Promo Code discount (3) entered by the diner" - and Buy X Get Y rewards resolve internally ("TouchBistro Loyalty automatically determines the most expensive qualifying item"). But no exclusive-vs-combinable flag and no order-of-application setting is exposed on any documented screen. None of these guides claims to enumerate the discount engine's rule set, so this is unresolved rather than a finding of absence.

guest-loyalty-targeted-offers differentiator

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

guest-loyalty-rfm-segmentation differentiator

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

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

guest-loyalty-native-email-sms differentiator

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

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

guest-loyalty-10dlc-registration

Searched the full 844-article help.touchbistro.com sitemap and read the Guest Engagement series: no article mentions A2P 10DLC, brand registration or campaign registration. Operator-sent marketing runs over two documented channels only - Email through the operator's own SendGrid account ("Ensure you're already set up with SendGrid", templates built in the SendGrid dashboard) and In-App Messaging to the Customer Web App - so there is no operator SMS campaign channel in the product that would require the operator to register. TouchBistro does originate transactional SMS (Online Ordering order-status alerts the diner re-authorises each order; the MoonClerk sign-up password link; reservation reminders), but no document states who holds the brand/campaign registration for those. Because the marketing guides do not purport to enumerate compliance obligations, this is unresolved rather than a finding of absence.

guest-loyalty-campaign-attribution differentiator

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

guest-loyalty-data-export-portability differentiator

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

guest-loyalty-review-capture-routing differentiator

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

guest-loyalty-referral-program

Searched the full 844-article help.touchbistro.com sitemap for referral mechanics and read the Rewards, Promotions, Automated Marketing and Customer Web App guides. The closest documented constructs are a Promotion Guest Page - "a direct link that allows the diner to claim the promotion", described as optional and shared by the operator rather than minted per guest - and a Customer Web App Custom button holding an operator-supplied outbound URL. Neither is a per-guest code or link, neither attributes a referred guest's first order, and no two-sided reward is described anywhere. The help centre's top navigation also carries a 'Referrals' link, but that is TouchBistro's own merchant-referral program, not a guest referral mechanic in the product. No document enumerates the marketing feature set, so this is unresolved.

guest-loyalty-wallet-pass differentiator

Checked the Guest Engagement | Customer Web App configuration guide, which enumerates the app's Home Screen Buttons (Locations, Rewards, Custom, Gift Cards, Feedback), its branding assets and its App Details tab, and the companion guide on how diners add the web app to their phone's home screen. The documented card-free mechanism is a branded PWA in which the Rewards button "allows diners to check in to your loyalty program using a QR code" - not an Apple Wallet or Google Wallet pass with a push-updatable balance. No article in the 844-article sitemap mentions Apple Wallet, Google Wallet or a pass file. Because the Customer Web App guide configures that app only and does not enumerate loyalty credential formats, this is unresolved rather than a finding of absence.

guest-loyalty-privacy-rights-tooling

Checked the Guest Engagement CRM guide, the Customer Web App guide and the loyalty program guides on help.touchbistro.com for merchant-side data-subject tooling. Documented: staff can look a guest up by first name, last name, email or phone, open that guest's detail, export the filtered list to CSV, apply and manage tags, adjust points and claimed items, and opt the diner out of email on their behalf. Not documented anywhere: a delete, erase, anonymise or data-access-request action on a guest record, or any statement about propagating a deletion into loyalty balances, redemption history and marketing lists - and adjacent objects are explicitly non-deletable ("Rewards cannot be deleted, only made inactive"; "Program cannot be deleted, only made inactive"). TouchBistro operates a corporate privacy portal for individuals, which is not merchant admin tooling. No doc enumerates the available actions on a guest record, so this is unresolved.

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

guest-loyalty-ai-offer-recommendation differentiator

Checked the TouchBistro Marketing introduction, the Automated Marketing guide, the Promotions guide and the CRM guide on help.touchbistro.com, plus touchbistro.com/online-ordering/. Every documented mechanism is rule- or calendar-based: audience is operator-built saved filters plus vendor-authored canned filters (rule templates, explicitly "create by TouchBistro", not models); offer content is manually authored Rewards and SendGrid email templates the operator builds; send timing is a scheduler with Weekly, Monthly, Yearly and Once intervals plus two expiring-offer reminder buffers the operator sets in days. No AI, ML, predictive or recommendation language appears in any Guest Engagement article, and the product pages make no AI claim either. Since neither the help centre nor the product site takes a position on AI recommendations, the claim as worded ('Vendor documents...') is unresolved rather than refuted.

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

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

labor-photo-punch-verification differentiator

Checked the clock-in guides on help.touchbistro.com, which document two punch methods - passcode entry then Clock In/Out, or "If your venue uses a QR code login, tap the QR code icon at the top right and image your assigned code" - and the manager-side Staff List guide, whose editable shift record consists of Staff Type, Rate of Pay, Cash Tip, Clock-In Time and Clock-Out Time. The Cloud Shift Details and Timesheet Details report columns are enumerated in the Labor Reports guide and contain no image, verification or attestation field. No photo, camera, facial-verification or biometric term appears in any labor, staff, security or hardware article in the 844-article sitemap. None of these is a document asserting its own completeness over punch verification options, so this stays unresolved.

labor-offline-time-punch differentiator

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

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

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

labor-native-scheduling differentiator

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

labor-demand-labor-forecast differentiator

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

labor-realtime-labor-percent differentiator

"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

labor-overtime-prevention differentiator

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

labor-break-compliance-by-state differentiator

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

labor-minor-labor-rules

Checked Staff | Staff Settings | Overtime Rules on help.touchbistro.com - the only per-jurisdiction labor rule surface TouchBistro documents, comprising weekly overtime (payout period), daily overtime (Shift Part 1), doubletime (Shift Part 2) and New York Spread of Hours - plus the Break Types configuration (Name, Duration, Paid only, with the explicit note that "TouchBistro does not restrict breaks based on time worked"), the Staff List and staff-type guides (no date-of-birth or age field appears in any documented staff field set), and the Staff Permissions guide. The only clock-in gate documented is schedule-based rather than age-based: "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", overridable by a manager passcode. No age-based hour cap, prohibited time window or school-day rule is documented anywhere, but no vendor doc enumerates minor-labor handling, so this remains unresolved rather than a finding of absence.

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

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

labor-qualified-tips-w2-reporting differentiator

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

labor-native-payroll differentiator

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

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

labor-shift-swap-workflow differentiator

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

labor-server-performance-metrics differentiator

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

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

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

inventory-theoretical-vs-actual differentiator

"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

inventory-realtime-depletion differentiator

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

inventory-86-auto-sync differentiator

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

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

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

inventory-vendor-catalogs-edi differentiator

"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

inventory-invoice-ocr differentiator

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

inventory-price-change-alerts differentiator

Checked the full help.touchbistro.com article set (764 articles crawled from /s/sitemap-topicarticle-1.xml). The only price field in the POS ingredient system is a single editable Cost Per Unit, and TouchBistro's own article averaging-per-unit-costs-add-new-stock tells operators to recompute a blended cost by hand in an unsupported spreadsheet, which argues against stored purchase-price history but is not a statement about the paid inventory products. touchbistro.com/profit-management/ says only "prices are updated daily" and touchbistro.com/inventory-management/ names no price-variance alert. TouchBistro Profit Management and TouchBistro Inventory Management have no help-centre documentation of their own beyond the enable/configure chicklet articles, and no public admin guide for either was locatable, so per-item invoice price history and configurable threshold alerting remain undetermined rather than absent.

inventory-par-auto-suggest differentiator

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

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

inventory-shelf-life-expiry

Checked the POS ingredient inventory screens as documented on help.touchbistro.com (Manage Ingredients: name, menu group, Purchase Measure, Cost Per Unit, Low-Stock Warning, Recipe Measures; Ingredient Inventory: Purchase/Adjust action, Measurement, Quantity) and the Menu Management Stock Availability screen (count, Low Stock Indicator, Out of Stock). No date field appears in either, and the ingredient reporting set (Ingredient Consumption, Low Stock Ingredients, Menu Item Cost) contains no expiring-soon view. Neither page asserts it shows the complete field set, however, and the paid TouchBistro Inventory Management and Profit Management modules have no published field-level documentation - their touchbistro.com pages name a Task and Waste Manager tracking "waste, theft, spoilage, and overproduction" after the fact, not dated lots. Undetermined rather than absent.

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

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-native-not-partner differentiator

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

inventory-menu-margin-linkage differentiator

"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

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

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

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

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

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

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

reporting-server-scorecards differentiator

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

reporting-channel-profitability differentiator

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

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

reporting-public-api differentiator

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

reporting-webhooks differentiator

Searched the whole crawled help.touchbistro.com corpus (764 articles) for webhook, endpoint, payload, signature, retry and HMAC: zero hits in English content. The integration articles (App Marketplace chicklets for DoorDash, MarketMan, Freepour, Shogo, 7shifts, Profit Management) are all configure-by-venue-ID flows with no developer-facing detail. touchbistro.com/features/integrations/ names partners and an App Marketplace sign-in but describes no API, webhook or developer program. cdn.touchbistro.com/help/ - a second help host that surfaced in search results - returned HTTP 403 (Cloudflare error 526) to every request. No public developer portal was locatable, so outbound event delivery is undetermined rather than absent: TouchBistro is reported to run a private partner API, and a private API's webhook behaviour cannot be ruled out from public sources.

reporting-api-not-upcharged differentiator

Checked touchbistro.com/features/integrations/ (partner logos and an App Marketplace sign-in, no API or developer terms), touchbistro.com/features/reporting-analytics/ ("more than 50 reports that update in real time", no data-access terms), the TouchBistro Merchant Terms of Service (defines Services, Hardware and Hardware Payment Plan agreements; contains no API, developer or data-access clause and no fee schedule), and the full help.touchbistro.com corpus, where the only integration documentation is per-partner enablement carrying the standing note "Most integrations require you to register and arrange payment with either TouchBistro or a third-party integration partner." That note establishes integrations are chargeable but not whether direct API or raw-data access is separately priced. Pricing is quote-based and the API is not publicly documented, so the commercial terms cannot be determined from public sources.

reporting-tier-paywall differentiator

"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

reporting-history-retention differentiator

Checked every Cloud reporting guide on help.touchbistro.com (how-to-generate-reports, the sales/labor/menu/payment/audit report guides, Advanced Reports, Multi-Venue Roll Up Reports, Customizing Report Templates, Index of Cloud Reports) plus touchbistro.com/features/reporting-analytics/. Reports take an arbitrary custom date range with no stated floor, and the only lookback limit published anywhere is specific to one report - Sales Trends, where "Available weeks will only go back to the start of the calendar year." Two other documented limits are not retention (cash deposits cannot be edited after 7 days; End of Day and Cash Deposits cannot be included in scheduled reports). No transaction-level retention window, truncation policy or archive-retrieval fee is published on either host, so the 24-month test cannot be evaluated.

reporting-anomaly-alerts differentiator

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

reporting-nl-query

Searched the crawled help.touchbistro.com corpus for AI, assistant, natural language, ask and chat: the only hits are the offline live-chat support widget and diner-facing messaging, nothing analytical. The Cloud reporting surface as documented is fixed reports plus Advanced Reports, whose querying model is explicitly manual - drag Dimensions to Rows or Columns, drag Measures to Values, add Filters with operators - with no query box anywhere in the guide. touchbistro.com/features/reporting-analytics/ markets "more than 50 reports that update in real time" and mentions no AI or natural-language capability. Because neither source is an exhaustive statement of the product surface and TouchBistro shipped platform changes as recently as June 2026, absence of an assistant is not established; recorded as unresolved.

reporting-guest-cohorts differentiator

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

reporting-sales-forecast differentiator

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

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

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

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

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

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

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

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

multi-location-multi-brand differentiator

Searched the crawled help.touchbistro.com corpus for virtual brand, ghost kitchen, multi-brand, second brand and concept: zero hits. Branding is documented only as a venue-or-group-level setting (How to Brand Your Venue; the multi-location guide lists Branding and Tax Settings as the two Venue Info options settable at Restaurant Group level), which implies one identity per venue rather than two on one terminal, and receipt customisation is per venue. The nearest documented mechanisms are custom Takeout Types, which only print a label on the kitchen ticket and are "functionally the same as a Takeout order", and Sales Categories for revenue segmentation - neither yields separate menus plus separate receipt branding on shared hardware. Because no page enumerates the complete set of venue-level configuration objects, recorded as unresolved rather than absent.

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

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

hardware-commodity-devices differentiator

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

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

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

hardware-handheld-battery-swap differentiator

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

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

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

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

hardware-kiosk differentiator

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

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

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

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

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

hardware-tap-to-phone differentiator

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-pricing-transparency differentiator

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-ownership-vs-lease differentiator

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

hardware-usable-after-churn differentiator

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

hardware-rma-sla differentiator

Read the TouchBistro Merchant Terms of Service end to end: it defines Hardware and Hardware Payment Plan agreements and reserves a remote-disable right, but states no warranty period, no return or RMA procedure and no advance-exchange turnaround. Searched the crawled help.touchbistro.com corpus for warranty, RMA, advance exchange, depot, replacement and next business day: the only warranty hits are third-party monitor and PAX terminal manufacturer notes, not a TouchBistro service commitment, and the hardware compatibility hub covers compatibility only. Warranty and replacement terms appear to sit in the private Sales Quote, which is not public, so no turnaround can be stated either way.

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

hardware-remote-device-management differentiator

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

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

hardware-callerid-integration

Searched all 764 crawled help.touchbistro.com articles for caller ID, CID, telephony, phone integration, VoIP and screen pop: no hits other than diner SMS receipts and reservation phone fields. TouchBistro's hardware compatibility index enumerates iPads, printers, Mac Pro Server computers, routers, payment terminals, cash drawers and barcode scanners, with no telephony device class. The App Marketplace integration list (reservations, loyalty and marketing, gift cards, scheduling, accounting, inventory, online ordering, bar management, analytics, insurance) contains no telephony partner - but an app directory is not an exhaustive statement of what can integrate, and phone-order workflow is documented only as manual entry of a Takeout or Delivery order with the customer keyed in by hand. Recorded as unresolved: the absence of a documented telephony integration is not itself proof that none exists.

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

extensibility-api-access-cost differentiator

TouchBistro publishes nothing about API commercial terms. Re-probed 2026-08-06: developer.touchbistro.com, api.touchbistro.com, docs.touchbistro.com and partners.touchbistro.com all fail to resolve (curl exit 000, no HTTP response); www.touchbistro.com/features/integrations/, titled 'POS Integrations & APIs', lists only pre-built partner integrations and says nothing about API access, fees, plan tiers, a developer portal or an application route; and no API reference exists in any of the 765 help.touchbistro.com articles. The only statement ever located on the question is Reforming Retail's 23 Jan 2019 interview with founder/CEO Alex Barrotti ('it's up to the third party software provider to get an API key from us'; 'Commercial terms must be established'), which predates TouchBistro's Cloud platform and App Marketplace by years and describes partner terms rather than what a merchant's own subscription includes. Whether API access is bundled, surcharged or tier-gated in 2026 is therefore undetermined rather than positively absent. adversarially verified

extensibility-free-sandbox differentiator

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

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

extensibility-webhooks-push

Unresolved because TouchBistro publishes no API documentation of any kind. Checked 2026-08-06: developer.touchbistro.com, api.touchbistro.com and docs.touchbistro.com do not resolve; the full touchbistro.com navigation and footer (read on /terms-of-service/, /iso-partnerships/, /contact-us/) contain no developer or API destination; and I mirrored all 773 articles on help.touchbistro.com via /s/sitemap-topicarticle-1.xml (Salesforce Experience Cloud, prerendered to a Googlebot user agent) and 'webhook' occurs zero times in the corpus. The 15 API mentions in that corpus are all third-party credentials pasted into TouchBistro (Moneris API token, SendGrid API key, MoonClerk API key, Mexican CFDI). Reforming Retail (23 Jan 2019) confirms an API exists but is deliberately unpromoted and partner-gated, so whether it pushes order-lifecycle events or requires polling is not observable from any public source. This is an evidence gap, not evidence of absence.

extensibility-webhook-reliability differentiator

Unresolved for the same reason as extensibility-webhooks-push: no webhook delivery contract is published, so signing, retry/backoff and replay cannot be assessed. Checked 2026-08-06: no developer host resolves (developer/api/docs.touchbistro.com); no developer or API entry anywhere in the touchbistro.com nav or footer; and across all 773 mirrored help.touchbistro.com articles the strings 'webhook', 'HMAC' and 'signature' do not appear in any integration context. The App Marketplace setup articles (chapter-11-integrations, enabling-push-operations, marketman, avero, scheduling-integrations-7shifts) describe only enable toggles and pasted partner identifiers and say nothing about event delivery mechanics. Cannot be scored without partner-level documentation TouchBistro does not publish.

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

extensibility-menu-write-api differentiator

Every menu data path TouchBistro documents runs outward or stays internal, but the private API's schema is not observable. Checked 2026-08-06 across all 773 mirrored help.touchbistro.com articles: 'How Do I Set up a Third Party Aggregator If I Am Using the POS-Based Platform?' (getting-touchbistro-set-up-for-your-online-ordering-aggregator) describes 'Configuring and Uploading Your Menu' and 'Uploading and Your Online Ordering Aggregator Portal' - the operator prepares the TouchBistro menu and it is imported by UrbanPiper or Deliverect, with TouchBistro noting what the aggregator 'will not import' (nested modifiers, the Common modifier group). Menu Management articles (Menu-Management-How-to-Add-Menu-Items, Menu-Management-How-to-Publish-Your-Menu) describe authoring in the Cloud portal and publishing down to the POS, an internal sync, not an API. No inbound menu write endpoint is documented, but no API reference is published at all (developer/api/docs.touchbistro.com do not resolve; no developer entry in the site nav), so absence of documentation here is not evidence the private partner API lacks menu writes.

extensibility-doordash-preferred differentiator

Conclusion confirmed — the 2026 cohort is Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper (list generated on performance as of 8 May 2026); TouchBistro is absent. But the cited URL (get.doordash.com/en-us/blog/preferred-integration-partners-2026) 301s to a merchants.doordash.com path that returns 404. Repoint to the DoorDash newsroom item. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-01 adversarially verified

extensibility-first-party-delivery-integrations differentiator

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

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

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

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

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

extensibility-headless-embedded

Checked 2026-08-06 across all 773 mirrored help.touchbistro.com articles and the touchbistro.com product pages: every documented order-entry surface is TouchBistro's own client - the POS iPad app, the Customer Facing Display, TouchBistro Kiosk, TouchBistro Online Ordering, and the Customer Web App - and each is configured from Admin Settings or the Cloud portal rather than driven by a third party. The App Marketplace list (chapter-11-integrations) contains no headless or embedded-commerce category. But TouchBistro publishes no API reference (developer.touchbistro.com, api.touchbistro.com and docs.touchbistro.com do not resolve; no developer destination in the site nav or footer), and Reforming Retail (23 Jan 2019) records that a partner-gated API does exist, so whether an approved partner can drive the transaction engine headlessly cannot be determined from public sources.

extensibility-data-portability-exit differentiator

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

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

reliability-offline-card-auth differentiator

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

reliability-offline-decline-liability differentiator

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

reliability-lan-degraded-multi-terminal differentiator

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

reliability-local-transaction-engine differentiator

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

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

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

reliability-sync-conflict-handling

Checked 2026-08-06 against all 773 mirrored help.touchbistro.com articles, including the connectivity and multi-device set (Part-2-How-to-Connect-iPads-to-your-Main-Device, managing-connected-devices, you-are-mac-pro-server, making-a-different-ipad-your-main-device, adding-ipads-to-an-existing-restaurant-using-a-mac-pro-server) and the outage article What-can-you-do-with-TouchBistro-POS-if-your-Internet-goes-down. None states a conflict-resolution policy - no last-write-wins, merge, or operator-prompt behaviour is described for edits made on two devices while the network is partitioned. The closest documented behaviour is narrower and is an acknowledgement-propagation limitation rather than a conflict policy: in the aggregator setup guide, 'If an order is acknowledged via one iPad, TouchBistro will not communicate order acknowledgment to the other iPads. Hence, to avoid confusion and preparing the same order multiple times, designate one iPad for online ordering.' The Mac Pro Server guide exposes a 'Repair Restaurant Data' support tool 'to find and repair any issues in your restaurant's SQL data' but does not say what it resolves or how. Unresolved: the vendor has not published the behaviour, and I found no primary source that would let me assert either a policy or its absence.

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

reliability-public-status-page

status.touchbistro.com does not resolve (DNS NXDOMAIN) and no per-component status page is linked from the site, support pages, or customer hub. Absence is inferred from a failed lookup, not from a vendor statement.

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

reliability-onsite-install differentiator

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

reliability-menu-build-service differentiator

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

reliability-hardware-replacement-sla

Checked 2026-08-06. The Merchant Terms of Use at touchbistro.com/terms-of-service/ (effective 31 Mar 2026) is TouchBistro's complete published commercial agreement; its sec. 7 'Hardware and Professional Services' covers only which hardware is approved ('TouchBistro may alter which hardware is approved as compatible ... in its discretion') and professional services, sec. 22 covers the Hardware Payment Plan and TouchBistro's 'right to remotely disable any iPads', and nowhere in the document do the words 'advance exchange', 'RMA', 'replacement', 'service level', 'uptime' or 'SLA' appear in a hardware-support sense. All 773 mirrored help.touchbistro.com articles likewise contain no advance-exchange or turnaround content - the hardware articles (hardware-payment-third-party-app-sup2, ipads, printers, supported-routers, where-can-i-get-supplies-for-my-printer) cover compatibility, setup, firmware and factory resets only. This is not sufficient for a 'no': the Terms repeatedly defer commercial specifics to the 'Sales Quote', a per-merchant ordering document that is not published, so a replacement program could exist there. touchbistro.com/support/, /security/ and /pos-hardware/ all return 404.

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

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

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

reliability-failover-terminal-role differentiator

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

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

commercial-month-to-month-contract differentiator

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

commercial-no-early-termination-fee differentiator

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

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

commercial-processing-not-bundled differentiator

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

commercial-interchange-plus-published differentiator

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

commercial-rate-increase-clause differentiator

Read the full TouchBistro Merchant Terms of Use at touchbistro.com/terms-of-service/ (effective 31 Mar 2026) on 2026-08-06. It contains zero occurrences of 'increase' or 'price', and its sec. 11 Payment Processing places the processing agreement outside TouchBistro's document altogether: 'The Payment Processing Services are provided by TouchBistro's bank partners and/or payment processing provider partners ... Merchant agrees that it will execute any and all agreements with the Payment Processing Provider as the Payment Processing Provider may require', and 'TouchBistro is not a party to the Merchant's agreement with its payment processor'. Fees under the TouchBistro agreement are set by the 'Sales Quote', a per-merchant ordering document that is not published ('Merchant shall pay TouchBistro any fees specified in its Sales Quote'). The counterpart processor agreements - Payrix (payrix.touchbistro.com / ca.payrix.touchbistro.com), Moneris, TSYS and Worldpay - are not linked or reproduced anywhere on touchbistro.com, and none of the 773 mirrored help.touchbistro.com articles reproduces processing rate terms. Unresolved because the governing document is private, not because TouchBistro's own terms are silent.

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

commercial-module-unbundling differentiator

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

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

commercial-hardware-not-locked differentiator

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

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

commercial-export-customer-and-loyalty differentiator

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

commercial-post-termination-export-window differentiator

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

commercial-data-ownership-clause differentiator

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

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

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

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

commercial-wcag-kiosk-accessibility differentiator

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

commercial-dual-pricing-compliant differentiator

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