ChowNow

menu-pricing-nested-modifiers

Modifier groups hang off menu items only. The group add/edit form is enumerated as Name, Description, Minimum/Maximum values, Main Items and Modifiers; the modifier form as Name, Description, Price, Modifier Groups and Classification, with no child-group field. The Copy dialogs confirm the depth of the tree: Copy Category targets Location/Merchant/Menu, Copy Item targets Merchant/Menu/Category, Copy Mod targets Merchant/Menu/Category/Main Item/Modifier Group - the modifier is the leaf. Min/max is real and a minimum of 1 forces a selection ('Minimum: 1, Maximum: 1 means they can only choose one modifier in the group'), but only one nesting level exists, so the three-level bar is not met. https://get.chownow.com/restaurant-support/modifier-groups/ · retrieved 2026-08-06

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

The modifier record's fields are Name, Description, Price, Modifier Groups and Classification - one Price - and ChowNow explicitly promotes sharing that one record: 'You can have a single modifier linked to multiple modifier groups. This way, you only need to create it once!' The modifier group form (Name, Description, Minimum/Maximum, Main Items, Modifiers) and the item form (Name, Description, Category, Price, Modifier Groups, Image, Classifications) contain no per-parent or per-size price override, so varying a modifier's price by parent item or size requires duplicating the modifier. https://get.chownow.com/restaurant-support/modifiers/ · retrieved 2026-08-06

menu-pricing-fractional-placement differentiator

Modifier fields are Name, Description, Price, Modifier Groups and Classification; modifier-group fields are Name, Description, Minimum/Maximum, Main Items and Modifiers; item fields are Name, Description, Category, Price, Modifier Groups, Image and Classifications. None carries a placement, section or fraction attribute, and the Menu Editor Overview's full capability list (Create a New Menu, POS Refresh, Categories, Modifier Groups, Modifiers, Bulk Price Updates, Menu Mapping, Publish, Preview) has no sectioned-placement construct. A modifier is either selected or not; halves and quarters cannot be expressed except by naming separate modifiers. https://get.chownow.com/restaurant-support/modifiers/ · retrieved 2026-08-06

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

The Menu Editor Overview enumerates every function of both the Advanced editor (Introduction, Publish Menus, Create a New Menu, Add New Items using POS Refresh, Create Categories, Create Modifier Groups, Create Modifiers, Bulk Price Updates, Menu Mapping) and the Legacy editor (create/edit item, edit modifier, photos, rearrange categories, hide out-of-stock items). No pricing-rule setting exists, and no half/quarter placement exists to apply one to - modifier pricing is a flat Price per modifier, summed. https://get.chownow.com/restaurant-support/menu-editor-overview/ · retrieved 2026-08-06

menu-pricing-topping-quantity-tiers

Adding a modifier takes Name, Description, Price and Classification; editing adds only Modifier Groups. There is no quantity stepper, tier or price multiplier anywhere in the modifier or modifier-group forms - the group exposes only Minimum/Maximum counts of how many modifiers may be chosen. Light/regular/extra/double with a per-tier multiplier is not expressible; it can only be imitated by creating separate modifiers at separate flat prices. https://get.chownow.com/restaurant-support/modifiers/ · retrieved 2026-08-06

menu-pricing-size-style-matrix differentiator

The item add/edit form is enumerated as Name, Description, Category, Price, Modifier Groups, Image and Classifications - one Price field and no variant dimension. ChowNow's own structural description is 'Inside a menu item, you'll often have modifier groups and modifiers', and the modifier record carries a single flat Price. A size x crust grid with a price per cell has no representation; each combination would need its own item or its own flatly-priced modifier. https://get.chownow.com/restaurant-support/menu-items/ · retrieved 2026-08-06

menu-pricing-included-allowance differentiator

The only count mechanism is the group's Minimum/Maximum, documented as 'minimum/maximum rules tell your customer how many modifiers they can choose in that group' - 'Minimum: 0, Maximum: 3 means they can choose up to 3 modifiers, or none at all.' Exceeding the maximum is blocked, not charged. There is no included-count field, no overage price and no substitution credit/forbid setting in the item (Name, Description, Category, Price, Modifier Groups, Image, Classifications), group or modifier (Name, Description, Price, Modifier Groups, Classification) forms. Three-toppings-included with paid overage can only be built as free modifiers plus separately-priced ones. https://get.chownow.com/restaurant-support/modifier-groups/ · retrieved 2026-08-06

menu-pricing-combos

Combo-style construction is possible through modifier groups: ChowNow describes modifiers as a way of 'adding extra cheese, substituting for non-dairy milk, or bundling in a dessert', groups constrain choices via Minimum/Maximum, and each modifier carries its own Price so a swap produces a price delta. Shortfall: there is no combo/meal entity in the menu model and none appears in the Menu Editor Overview's complete feature list, so nothing detects eligible a-la-carte items already in the cart and converts them to a combo price - the diner must pick the combo item up front. https://get.chownow.com/restaurant-support/modifiers/ · retrieved 2026-08-06

menu-pricing-upsell-prompts differentiator

QR Code Ordering is claimed to include 'digital upsell prompts' and direct ordering copy references optimizing the menu for upsells. No per-channel configuration model and no attach-rate reporting documented; a support search for 'upsell' returns zero articles. https://get.chownow.com/products/q2-feature-release/ · retrieved 2026-08-01

menu-pricing-86-propagation

Automated Inventory Sync propagates out-of-stock items AND modifiers from Revel, Omnivore, Genius, Clover, and Square out to ChowNow, DoorDash, Uber Eats and Grubhub. POS-driven only, limited POS list, no published propagation latency, no kiosk/KDS surface. https://get.chownow.com/restaurant-support/?s=inventory · retrieved 2026-08-01

menu-pricing-countdown-auto-86 differentiator

ChowNow's 'automated inventory sync and 86ing feature' delivers the decrement-and-86 outcome but not natively: 'Square tracks your inventory levels for each item. When an item's stock reaches 0, it is automatically marked as sold out across all connected platforms. When you add more stock in Square, the item is automatically re-enabled.' Shortfalls: the par/count lives in the connected POS, never in ChowNow, and only for the named integrated POS systems (Square, Clover, Revel, Omnivore, Genius); it works 'only if you are using your POS Menu as your source of truth, or if you're mapping directly through the Menu Editor'; ChowNow's own availability surface is a binary hide toggle ('Tap on Item Availability... Select Items or Modifiers, then tap on the toggle switch'); and restore is triggered by restocking in the POS, not by a schedule, so the claim's scheduled auto-restore is absent. https://get.chownow.com/restaurant-support/automatically-sync-square-inventory-updates/ · retrieved 2026-08-06 adversarially verified

menu-pricing-dayparting

Menus and their availability are schedulable; items and prices are not. 'The menu hours set in Menu Editor will affect the availability of this menu on all the online platforms connected to it.' Menu Editor > Edit Menu > Menu Info > MENU HOURS has a Standard Hours tab (per day, with closed-all-day and open-24-hours options) and a Holiday Hours tab scoped to selected integrations; future Holiday Hours publish automatically at 1am the day before. Withdrawing the earlier 'timezone basis is never stated' leg - the ChowNow Partner API spec states it: the menu `at` parameter is 'ISO-8601 local date-time with NO timezone; it is read as the restaurant's local wall-clock time', a value carrying a trailing Z or offset is rejected with 400 because 'a zoned value would silently resolve against the wrong instant upstream', and the upstream resolves 'to the ONE menu scheduled at the requested time'. Shortfall, now on a stated limitation rather than on silence: per-item and per-price scheduling does not exist - 'If you have menu items that change price depending on the time of day, or the day of the week, ChowNow is unable to display the alternate price at those times. ChowNow will always display the base price at all times of the day.' https://get.chownow.com/restaurant-support/updating-your-standard-menu-hours-and-holiday-menu-hours/ · retrieved 2026-08-06

menu-pricing-channel-price-books

Withdrawing the grade-D marketing-only leg: the mechanism is documented in ChowNow's own OpenAPI 3.1 spec. The gateway note on GET /v1/restaurants/{id}/menu says the upstream call is made with 'NO cn_channel query param -> base, no-markup pricing (CN-48933)', which establishes that ChowNow's menu service resolves prices against a channel identifier and applies a markup per channel over one base price. The vendor's own description of it is 'a baked-in tool that automatically adjusts menu prices to offset standard fees', managed from one dashboard. Shortfall: this is a single ChowNow-managed fee-offset markup toggled per discovery/marketplace channel, not operator-authored price books - no price-book object, no per-channel percentage-markup rule the operator can set, and no separate dine-in/pickup/delivery/kiosk price sets appear in the spec or in the Menu Editor documentation. https://developer.chownow.com/docs/openapi.json · retrieved 2026-08-06 · not refetchable · site policy · graded A when read

menu-pricing-dual-pricing differentiator

'We do not accept cash so that all ChowNow orders are prepaid by credit card', and the diner-facing tender list is exhaustive: 'All major credit/debit cards (Visa, Mastercard, Discover, AMEX) are accepted. Apple Pay is also accepted if you are using the restaurant's iOS application. All other payment options (Cash, PayPal, Android Pay, etc) are not accepted at this time.' The item record holds one Price. The only per-item-independent fee is a per-location service fee by dollar amount or percentage applied to every order, which is not a cash discount. There is also no POS or kiosk surface and no printed guest check for a dual price to appear on. https://get.chownow.com/restaurant-support/accepting-cash/ · retrieved 2026-08-06

menu-pricing-versioning-effective-dates differentiator

Changes are staged and previewed: unpublished menus show an orange 'modified' status per integration, Menu Editor > pencil > Preview Menu renders the menu 'with your hours and items' and lets you click into an item to see its modifiers, and publishing runs a VALIDATE step then reports per-integration green/blue/red results. Shortfall: there is no named or effective-dated menu version and no rollback to a prior published version - the only undo is in Bulk Edit ('You can undo the last 5 previous updates'), which covers bulk price increases/decreases only, and the only date-effective publish is Holiday Menu Hours auto-publishing at 1am the prior day. https://get.chownow.com/restaurant-support/how-to-preview-your-menu/ · retrieved 2026-08-06

menu-pricing-franchise-hierarchy differentiator

Central propagation exists as an explicit copy: Copy Category asks for 'Target Location, Target Merchant and Target Menu'; Copy Item takes Target Merchant/Menu/Category; Copy Group and Copy Mod take Target Merchant plus the destination path. All locations are reached from the Headquarters sidebar in one dashboard and admin users can be scoped to one location or all. Shortfall: the copy is a detached duplicate - no parent template, no push of subsequent changes, and no field-level governance controlling which attributes a location may override. Adding a location is not self-serve either ('Contact your Restaurant Success Manager'). https://get.chownow.com/restaurant-support/menu-categories/ · retrieved 2026-08-06

menu-pricing-allergen-nutrition

Re-checked the cited menu-items article in full: it is a task walkthrough whose add-step field list ('item name, description, and price') is shorter than its own edit-step list, so it is not an exhaustive field reference. It documents a Classifications field but only illustrates one use ('If your item contains alcohol, make sure to tag it using the Classifications field'); ChowNow never publishes the permitted classification values, and a restaurant-support search for 'classifications' returns only this article, so whether the vocabulary carries allergen or dietary flags cannot be determined. Toast's ChowNow integration chart is silent on allergen or nutrition fields. The recipe-derivation arm of the claim IS separately established as absent (see menu-pricing-recipe-linkage and inventory-native-not-partner: no recipe module, MarketMan is the named inventory partner), but the storage-and-publication arm is unresolved, so the honest value is unknown. adversarially verified

menu-pricing-recipe-linkage differentiator

No inventory or recipe module; ChowNow lists MarketMan as its inventory partner instead. https://get.chownow.com/partners/ · retrieved 2026-08-01

menu-pricing-3p-menu-push

Centralized menu management pushes items, pricing, and availability to DoorDash, Uber Eats and Grubhub 'with one click' via ChowNow's own (Cuboh) integrations, not a third-party middleman. Menu-mapping troubleshooting articles exist but no per-item sync-status/rejection dashboard is documented. https://get.chownow.com/products/order-aggregation/ · retrieved 2026-08-01

menu-pricing-dynamic-pricing

'A free-to-use automated feature within the Order Better Network that lets restaurants offset menu prices to protect profit margins... Once your restaurant starts taking Order Better Network orders, Profit Protector can automatically adjust the menu pricing to effectively offset the cost of Order Better Network fees.' Shortfall: the rule is a single channel-scoped fee offset - no time-of-day, day-part or demand trigger, no rule builder, and no floor or ceiling guardrail is published; the markup formula is not disclosed and enabling it requires emailing ChowNow or a Restaurant Success Manager rather than a dashboard setting. https://get.chownow.com/restaurant-support/what-s-profit-protector/ · retrieved 2026-08-06

payments-processor-choice differentiator

Verified verbatim: 'ChowNow requires all of our clients to use our current payment processor.' Stripe confirmed independently by the billing article 'How do I submit required information to Stripe?'. Reinforced by 'We do not accept cash so that all ChowNow orders are prepaid by credit card' — which also independently supports every card-present, offline-payment, split-tender and cash-drawer 'no'. https://get.chownow.com/support-category/order-and-payments-processing/ · retrieved 2026-08-01 adversarially verified

payments-published-rates differentiator

Help centre: 'For Visa, Mastercard, Discover, and American Express - the transaction fees are 2.95% + $0.29 per order.' A single flat rate across all four brands with no tiering. The public Restaurant Agreement repeats it per subscription (US and Canada $0.29 + 2.95%; third-party POS integration $0.30 + 2.9%). Merchants cannot substitute a processor - support states 'At this time ChowNow requires all of our clients to use our current payment processor.' https://get.chownow.com/restaurant-support/credit-card-transaction-fees/ · retrieved 2026-08-06

payments-dual-pricing differentiator

'We do not accept cash so that all ChowNow orders are prepaid by credit card' (cash tips to a driver excepted), and the diner tender enumeration adds that 'All other payment options (Cash, PayPal, Android Pay, etc) are not accepted at this time.' Items carry a single Price field, so no second price can be stored. Diner-facing totals are an online Order Summary and an emailed confirmation; the only additional line ChowNow can add is a per-location service fee (dollar or percentage) or the optional $0.99 service charge, neither of which is a cash/card price pair. https://get.chownow.com/restaurant-support/accepting-cash/ · retrieved 2026-08-06

payments-surcharge-guardrails differentiator

Two articles enumerate the whole fee-configuration surface: 'You can add a service fee either by amount or percentage of the order, through the ChowNow Dashboard under the Location Info section', and the service charge is a per-location checkbox - Settings > Location Details > Ordering > Edit > 'Enable Service Charge' - adding a fixed $0.99 to website and branded-app orders, split 50/50 with ChowNow and shown in the Order Summary. Per-location enable/disable is therefore satisfied, but nothing else in the claim is: the fee is charged on every order irrespective of card product, there is no BIN or card-product lookup, no debit/prepaid exclusion and no network percentage cap enforcement - and every ChowNow order is a card transaction, so a card surcharge is indistinguishable from a flat fee. https://get.chownow.com/restaurant-support/service-charge-frequently-asked-questions/ · retrieved 2026-08-06

payments-emv-nfc

ChowNow ships no payment terminals; all payments are card-not-present through the digital ordering flow.

payments-softpos-tap-to-pay differentiator

No in-person acceptance product.

payments-pay-at-table

No handheld payment device. QR ordering shifts payment to the guest's own phone instead.

payments-qr-guest-pay differentiator

QR Code Ordering lets guests 'browse menus, place orders, and pay' from their phone at the table, but this creates a ChowNow order routed to the POS — it does not open and close an existing POS check. https://get.chownow.com/products/qr-code-ordering/ · retrieved 2026-08-01

payments-tip-adjust

'Tips are paid out at the end of each business day, along with the rest of your daily disbursements... ChowNow will provide a report breaking out the tips earned each day', and dine-in tips are reconciled by filtering the Accounting Data Report to Dine-In orders. All orders are prepaid by card at online checkout on the diner's own device, so there is no pre-authorization held for later adjustment, no batch/adjust window and no manager screen for unadjusted tips - the only documented post-order money movement is a dashboard refund (full or by item) or a Cuboh-tablet Upcharge, each an arbitrary amount entered with a reason, not a tip adjustment. https://get.chownow.com/restaurant-support/tips/ · retrieved 2026-08-06

payments-tip-pooling differentiator

No labor module; 7shifts is the named team-management partner. https://get.chownow.com/partners/ · retrieved 2026-08-01

payments-offline-store-and-forward differentiator

Cloud-only platform; no offline payment capture documented.

payments-offline-decline-liability differentiator

No offline payment path exists to document liability for.

payments-gift-cards

Enumerated all three get.chownow.com Yoast sitemaps - 166 marketing pages, 278 restaurant-support articles, 38 diner-support articles - and found no gift-card page; the restaurant-support search for 'gift card' returned only the standing popular-articles block (zero real hits). The two nearest constructs are not merchant stored value: ChowNow Bucks is ChowNow-issued diner goodwill credit added by support agents and reimbursed to the restaurant in weekly deposits, and 'promotional cards' are printed onboarding collateral reordered from ChowNowStore.com. The customer membership program is a prepaid annual discount, not a redeemable balance. No page asserts that gift cards are unsupported and no settings screen enumerates the payment/credit types a diner may apply, so a `no` is not earned. There is no separate help centre to check: support.chownow.com and help.chownow.com do not resolve and chownow.zendesk.com 404s.

payments-house-accounts

'Can I bill my customers later?' is answered 'ChowNow is a prepaid ordering system, therefore all the orders must be process at the time of checkout. This way, you are never in a position where you have made the food but no one comes to pick it up and pay for it.' Reinforced by 'We do not accept cash so that all ChowNow orders are prepaid by credit card.' No account balance, credit limit, running tab or statement/invoice run exists; ChowNow's own workaround for tax-exempt business customers is a promo code, not an account. https://get.chownow.com/restaurant-support/billing-customers-later/ · retrieved 2026-08-06

payments-split-tender

Single-tender digital checkout; no split-tender or split-by-seat documented.

payments-refund-void-controls

At portal.chownow.com an operator picks the location and order, then chooses Full Refund or Refund By Item - the latter expands each line item's add-ons and modifiers with per-line checkboxes - and in both paths must 'Type in your name under Approved By' and give a reason before confirming; the diner is emailed on full and partial refunds. Shortfall: 'Approved By' is a typed free-text string, not an authenticated manager PIN or role check; the only access control documented is which locations a dashboard user may view; no immutable audit log or approver report is published; and the alternative Cuboh-tablet path takes an arbitrary refund or Upcharge amount plus a reason with no approval step at all. Discounts, voids and no-sales are not distinct authorised actions in this platform. https://get.chownow.com/restaurant-support/order-refunds/ · retrieved 2026-08-06

payments-chargeback-tooling differentiator

ChowNow assumes the cost of fraudulent disputes internally and markets '100% Fraud & Chargeback Protection ... without any limits' — a liability shift rather than an operator-facing dispute dashboard with evidence submission. https://get.chownow.com/support-category/order-and-payments-processing/ · retrieved 2026-08-01

payments-card-on-file differentiator

Cards persist on a diner profile - ChowNow tells diners 'If you ever feel uncomfortable having your credit card information stored on the ChowNow platform you can go here to learn how you can remove them' - and the merchant is walled off: 'we never give a restaurant access to your credit card information or the ability to add additional charges to your order once it's been placed'; on the restaurant side ChowNow states card data is 'encrypted and hidden in our admin and merchant processor', with Stripe as processor. Shortfall: ChowNow never describes a token, vault or reuse mechanism explicitly, and the documented ordering channels are the restaurant's website, its branded mobile app, a Facebook plugin and eat.chownow.com only - there is no phone-order or in-store channel for the stored card to be reused in. https://get.chownow.com/diner-support/credit-card-security/ · retrieved 2026-08-06

payments-payout-timing differentiator

Verified in the support index verbatim: 'disbursed daily after closing, Monday through Friday. This can take 1-2 business days.' Tips ride the same disbursement. https://get.chownow.com/support-category/order-and-payments-processing/ · retrieved 2026-08-01 adversarially verified

payments-multi-entity-routing differentiator

Payment processing is per location, not per account: 'Click on Headquarters, then select a location... view the Payment Processing status for this location by navigating to Settings, then Payment Processing', where each location has its own Stripe account with its own 'Business Details' and 'Management and ownership' sections, and the instruction closes 'Repeat these steps for each location until the Payment Processing status is Your Stripe account is active for each location.' Disbursements land daily in 'the bank account you have on file' and reporting is unified under Headquarters. Shortfall: no article states that different locations may point at different bank accounts or legal entities, no split-settlement of a single order is described, and adding a location is handled by a Restaurant Success Manager rather than self-serve. https://get.chownow.com/restaurant-support/how-do-i-submit-required-information-to-stripe/ · retrieved 2026-08-06

payments-p2pe-pci4

'ChowNow is a PCI compliant company with proper certification to acquire, maintain, and protect credit card information submitted on our platform. Credit card information is encrypted and hidden in our admin and merchant processor', and the diner-facing counterpart confirms the restaurant is never given access to card data. Shortfall: no PCI DSS version is named (nothing ties the statement to 4.x), no Attestation of Compliance is published or offered on request anywhere in the 278-article support corpus or the 166 marketing pages, and no P2PE listing exists or could - every order is a prepaid online card transaction processed by Stripe with no ChowNow-supplied payment terminal, so there is no point-to-point encryption instance to validate. https://get.chownow.com/restaurant-support/customer-credit-card-security/ · retrieved 2026-08-06

delivery-driver-roster

In-house delivery can be configured (zones, fees) but drivers are not first-class entities — no clock-in, assignment state, or per-driver run history. Flex Delivery outsources the driver entirely. https://get.chownow.com/products/flex-delivery/ · retrieved 2026-08-01

delivery-dispatch-board

No dispatch/expo screen; Flex Delivery dispatch is automatic to Uber Direct / DoorDash Drive. https://get.chownow.com/products/flex-delivery/ · retrieved 2026-08-01

delivery-route-map differentiator

No in-house routing; couriers are third-party.

delivery-driver-tracking differentiator

No first-party driver app.

delivery-zones-polygon differentiator

'Delivery zones can be set up on the ChowNow dashboard by zip code, mile radius and custom polygon. You can set up multiple zones and use any combination of the zone types.' The configuration walkthrough matches: Settings > Location Info > Delivery > Edit > '+ Add Area', where 'Polygon allows you to drop pins on the map for customized zones', Circle gives a mile radius around the restaurant and Zip Code takes a comma-separated list; each area carries its own minimum (and optional maximum) subtotal and a delivery fee by dollar amount or percentage. Drive-time isochrones are not offered, but the claim's bar is arbitrary polygons rather than radius/ZIP alone, and that is met. Separately, dispatch via a partner such as DoorDash Drive is distance-capped at 8 miles. https://get.chownow.com/restaurant-support/delivery-zone-types/ · retrieved 2026-08-06

delivery-zone-pricing

Zone GEOMETRY is configurable but zone PRICING is not. 'Delivery zones can be set up on the ChowNow dashboard by zip code, mile radius and custom polygon. You can set up multiple zones and use any combination of the zone types.' Pricing is documented as a single flat rate, not per zone: 'orders will be priced at a flat $7.98 with a maximum range of 8 miles. You can choose how much of this fee is paid by you or your customer' (recommended diner share $3.99). No per-zone delivery fee, no per-zone order minimum and no per-zone promise time appear in the support corpus. Verified: true https://get.chownow.com/restaurant-support/delivery-zone-types/ · retrieved 2026-08-09 adversarially verified

delivery-address-validation

Delivery eligibility is geographic and evaluated in-product: zones are defined by custom polygon, mile radius or zip list with per-area minimum subtotals, and ChowNow's diner Terms of Use state 'ChowNow uses Google Maps and the Google Maps API as part of our online ordering system', so entered addresses are geocoded and matched to a zone before a delivery order can be placed. Shortfall: ChowNow publishes no address verification, normalisation or correction step and no description of what a diner sees when an address falls outside every zone; its own diner article on a mistyped delivery address offers no in-product flag or fix, telling the diner to text ChowNow support instead. https://get.chownow.com/restaurant-support/delivery-zone-types/ · retrieved 2026-08-06

delivery-driver-comp differentiator

No in-house driver module and no payroll export.

delivery-cash-reconcile

No driver bank/settle-up flow.

delivery-daas-dispatch

Flex Delivery dispatches first-party orders to Uber Direct and DoorDash Drive natively at a flat $3.99/order with no commission or distance surcharge; ChowNow recommends a 50/50 split with the diner. https://get.chownow.com/products/flex-delivery/ · retrieved 2026-08-01

delivery-daas-fallback differentiator

Automatic failover BETWEEN courier networks based on real-time driver availability and response time. Rule-based overflow from in-house drivers to DaaS is not documented, though Flex can run alongside in-house drivers. https://get.chownow.com/products/flex-delivery/ · retrieved 2026-08-01

delivery-3p-direct-integration differentiator

Direct integrations with DoorDash, Uber Eats and Grubhub, owned by ChowNow via its 2024 acquisition of Cuboh — no third-party middleware layer purchased separately. https://get.chownow.com/integrations/all/ · retrieved 2026-08-01

delivery-3p-injection

Sole source is a product marketing page and the researcher labelled it 'claimed' yet still scored 'yes'. The 0.1s and 99.9% figures are unaudited vendor metrics with no methodology. Countervailing evidence: ChowNow/Cuboh is absent from DoorDash's 2026 Preferred Integration Partner roster (Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper) — a program explicitly built around injection reliability and cancellation rates — and reviewers report added manual steps post-Cuboh. A marketing-only 'yes' on a weighted differentiator does not clear the bar. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-01 adversarially verified

delivery-menu-push

The quoted 'one click' language is from the Order Aggregation marketing page, not product documentation. ChowNow's actual support library documents per-POS menu setup and mapping work ('How to Set Up Your Square POS Menu for Import', Cuboh menu-mapping troubleshooting), and the dossier's own top complaint is items and modifier options silently disappearing from the live menu. No sync-status or rejection surface is documented. Partial, not yes. https://get.chownow.com/restaurant-support/how-to-set-up-your-square-pos-menu/ · retrieved 2026-08-01 adversarially verified

delivery-86-sync

Upheld and strengthened. The dossier cited a search-results URL; real per-POS support articles exist and confirm the behavior: 'How to Automatically sync Square/Clover/Revel/Omnivore/Genius POS Inventory Updates' — out-of-stock items and modifiers propagate across ChowNow, DoorDash, UberEats, Grubhub (Clover/Square articles additionally name SkipTheDishes and Ritual). POS-driven only, as scored. https://get.chownow.com/restaurant-support/how-to-automatically-sync-clover-pos-inventory-updates/ · retrieved 2026-08-01 adversarially verified

delivery-store-pause

'The Cuboh Tablet allows you to manage all of your online storefronts from the Integrations Tab.' Under Navigation > Integrations an operator can 'Open or close all of the online storefronts associated with a specific restaurant merchant' or 'Open or close individual online storefronts for all merchants at once'; Toggle by Concept disables one merchant 'across all of its integrated app platforms' and Toggle by Integration disables all merchants on one app. Shortfall: there is no timer - ChowNow describes it as 'best used for temporary situations, say if you close down early for the night' and says normal hours resume when the Integration Status is active again, with a warning to 'wait 30 seconds between turning stores on / off'. No scheduled or duration-based auto-reactivation is documented. https://get.chownow.com/restaurant-support/managing-your-3rd-party-apps-from-the-cuboh-tablet/ · retrieved 2026-08-06

delivery-3p-reconciliation differentiator

Disbursement Reports 'reconcile payouts with line-item clarity' and comparative analytics benchmark channels. Itemized marketplace commission/marketing fees, refunds/adjustments and missing-order detection are not documented. https://get.chownow.com/products/advanced-reporting/ · retrieved 2026-08-01

delivery-injection-error-visibility differentiator

The support portal includes an 'error message lookup' section and menu-mapping troubleshooting articles, implying surfaced errors; no per-channel connection-health dashboard or failure alerting is documented. https://get.chownow.com/restaurant-support/ · retrieved 2026-08-01

delivery-tracking-page

'How can I track my order?' is answered: 'At this time, ChowNow does not have any tracking software capabilities to give you real time updates on your delivery order. However, once the restaurant accepts your order, you will get an order confirmation with the approximate time for pickup or delivery.' The other documented diner messages are confirmation emails and cancellation/partial-refund emails, plus marketing campaigns. No branded status page, driver map or SMS tracking link on the restaurant's own domain is described anywhere, and ChowNow states it never dispatches its own drivers - 'the restaurant's couriers or their delivery company' do. https://get.chownow.com/diner-support/order-issue-delivery-tracking/ · retrieved 2026-08-06

delivery-promise-time differentiator

Order Throttling limits orders 'based on 15 minute time slots'; when the current slot fills, 'customers will be automatically presented with the next available time' and full future slots are hidden, so the quoted time does move with accepted volume. Per-order override exists too: with the Custom Preparation Times toggle on, an 'Add Custom Prep Time' button appears for 3 minutes and the resulting fulfilment time (current time + custom prep) is printed and pushed to ChowNow, UberEats, DoorDash, GrubHub and Ritual; otherwise the default prep time is sent. Shortfall: the slot cap and the default prep time are operator constants set from order history, not computed from live kitchen state, there is no driver-availability input, and ChowNow states 'It is not possible to control the delivery preparation time' - the third-party app adds its own driver/delivery time, so no zone drive-time component is modelled. https://get.chownow.com/restaurant-support/how-do-i-manage-order-volume-with-order-throttling-settings/ · retrieved 2026-08-06

delivery-offline-behavior

Re-read the cited POS_OFFLINE article in full; it covers only the ChowNow-to-POS connection ('Your POS may go offline if it's unable to connect to your restaurant internet') and prescribes manual re-entry, saying nothing about delivery operation during an outage. The `no` rested on enumerating the three Yoast sitemaps, which lists article URLs and titles rather than bodies, so it cannot show that no published article addresses driver assignment or driver settlement while offline. Two supporting facts are solid and worth keeping in view - cash delivery orders cannot arise because ChowNow accepts no cash, and ordering is entirely server-side - but ChowNow never states its offline delivery behaviour and I could not establish that it nowhere does, so this is unknown rather than a documented absence. adversarially verified

digital-first-party-web

Direct online ordering plus an SEO-optimized website on the restaurant's own branding, included in all three tiers, with 'no per-order cut' — flat subscription + card processing only. https://get.chownow.com/products/direct-online-ordering/ · retrieved 2026-08-01

digital-menu-single-source

Menus can be sourced/imported from the POS and mapped (Square import, Cuboh menu mapping), and centralized menu management pushes one edit to all channels. But the ChowNow menu is a separate record requiring mapping, and operators report items and modifier options silently disappearing. https://get.chownow.com/restaurant-support/?s=modifier · retrieved 2026-08-01

digital-native-app differentiator

Help centre: 'Branded mobile apps (both Android and iOS) are included with our Pro and Premier subscriptions' and 'Apple requires a $99/year fee as part of the Developer Program Membership. Restaurants will need to pay this fee.' A companion article covers design updates (logo, loading screen image, name, colour scheme) at no extra cost, and a further article covers removal of the restaurant's app from the App Store and Play Store on cancellation - i.e. an app listed under the restaurant's own brand, not only the multi-restaurant ChowNow Marketplace app. Tier naming in the help centre is the legacy Pro/Premier pair; current published tiers are Launch/Grow/Elevate. https://get.chownow.com/restaurant-support/does-chownow-publish-restaurant-mobile-apps/ · retrieved 2026-08-06

digital-account-saved-payment

Diners hold a ChowNow account that tracks rewards progress and order history across the website, branded app, Marketplace and Discovery Network, and can reorder favorites. Saved addresses and tokenized saved payment are not explicitly documented. https://get.chownow.com/products/rewards-program/ · retrieved 2026-08-01

digital-upsell-engine differentiator

'Digital upsell prompts' claimed for QR Code Ordering (with a claimed 9% check-size lift). No configuration model and no attach-rate reporting documented. https://get.chownow.com/products/q2-feature-release/ · retrieved 2026-08-01

digital-scheduled-pacing

Scheduled/future orders with adjustable prep and lead times and large-order thresholds. No per-daypart capacity limits or automatic slot closure documented. https://get.chownow.com/restaurant-support/?s=scheduled · retrieved 2026-08-01

digital-fulfillment-modes

Pickup, delivery (in-house zones or Flex), dine-in via QR, and catering all run from one ordering flow with mode-specific fees and prep timing. Curbside with arrival check-in is not documented. https://get.chownow.com/pricing/ · retrieved 2026-08-01

digital-qr-table

QR Code Ordering ships on all tiers — guests scan, order and pay from their phone. It does not attach to an open POS check, and splitting/tipping behavior is undocumented. https://get.chownow.com/products/qr-code-ordering/ · retrieved 2026-08-01

digital-kiosk differentiator

No kiosk product in the product line or pricing table. https://get.chownow.com/pricing/ · retrieved 2026-08-01

digital-group-ordering

Enumerated all three get.chownow.com Yoast sitemaps (166 marketing pages, 278 restaurant-support articles, 38 diner-support articles) and searched restaurant-support for 'group order', which returned only menu-structure articles and the standing popular-articles block. The diner article 'What are the different ways I can order?' lists the ordering paths as the restaurant's website, its downloadable mobile app, its Facebook page (select restaurants) and eat.chownow.com - no shareable cart link - and checkout is described throughout as one diner account paying with one stored card, with per-order spend limits set only as catering min/max order amounts. But ChowNow never publishes a checkout settings screen or states that group ordering is unsupported, and the catering flow (inquiry forms, order-ahead windows up to 30 days) is the closest documented large-party path, so absence here is unproven. No help centre exists beyond get.chownow.com: support.chownow.com and help.chownow.com do not resolve and chownow.zendesk.com 404s.

digital-catering-portal differentiator

5% commission and 'Set lead times, order minimums, and prep windows ... up to 30 days ahead' are confirmed verbatim. However 'inquiry forms for event details' does not appear anywhere on the catering page and should be struck from the note as unsourced. Score stays partial for the right reasons. https://get.chownow.com/products/catering/ · retrieved 2026-08-01 adversarially verified

digital-voice-ai-phone differentiator

Checked get.chownow.com/partners/, get.chownow.com/integrations/all/ and the individual /integrations/* pages in the page sitemap (POS, marketplace, printer and discovery partners only - Auphan, Brink, Clover, Givex, Lavu, Lightspeed, Linga, Micros, PixelPoint, Positouch, Revel, Silverware, Square, Toast, Universal, Verona, Volante, DoorDash, Grubhub, Uber Eats, Yelp, Google, Apple Maps, Epson, Star Micronics), plus the 278-article restaurant-support corpus, where a search for 'phone' returns only support-contact, Cuboh and error-code articles. Nothing first-party offers inbound AI call answering, and the diner article 'What are the different ways I can order?' enumerates the ordering paths as restaurant website, branded mobile app, Facebook page and eat.chownow.com, which argues against a native product. Unresolved because the claim is satisfied by a named certified partner as well, and an integrations directory is not an exhaustive list - no ChowNow page asserts that voice ordering is unavailable.

digital-drivethru-ai

No drive-thru product.

digital-sms-ordering

ChowNow issues every U.S. client a Text-To-Order code: 'Customers can simply text your custom code to the number 33733 and they will be sent directly to place an order on the proper web or mobile device', and ChowNow tells operators to print it 'on your POS receipts, in-store signage, 4x6 cards, takeout menus, business cards, and stickers'. Orders placed through the resulting flow reach the POS via ChowNow's POS integrations. Shortfall: this is text-a-link only - a one-shot keyword autoresponder on a shared 33733 short code that hands off to web or app. Nothing conversational exists: no in-thread item selection, no text reordering of a previous order, and no inbound-reply handling. ChowNow's own SMS product is otherwise one-way marketing ('SMS marketing lets you reach customers directly on their phones with promotions, updates, and announcements'), enabled as a 10DLC registration under Marketing > Campaign Settings. https://get.chownow.com/restaurant-support/text-to-download-code/ · retrieved 2026-08-06 adversarially verified

digital-google-order differentiator

ChowNow's own blog states Google discontinued end-to-end ordering in July 2024; diners are now 'redirected to either your restaurant's website or a third-party site.' ChowNow also publishes a support article titled 'Disabling End-to-End Google Ordering with ChowNow.' What remains is an 'Order Online' link on the Google Business Profile plus the Preferred-Provider designation — a link placement any ordering vendor can obtain, not a provisioned Google ordering channel. The dossier's parenthetical ('Food Ordering with Google, not legacy Place Actions') describes a mechanism Google has retired. https://get.chownow.com/blog/googles-ordering-changes-what-your-restaurant-needs-to-know/ · retrieved 2026-08-01 adversarially verified

digital-apple-business-connect

Apple Maps is a named Discovery Network channel — 'Connect your menu to Apple Maps ... find, browse, and order' — but Apple Business Connect and the 'Order Food' custom action are not named and the provisioning mechanism is not documented. https://get.chownow.com/integrations/apple-maps/ · retrieved 2026-08-01

digital-loyalty-attach

Rewards accrue and redeem automatically at checkout across the ordering page, branded app, Marketplace and Discovery Network under the diner's ChowNow account. There is no in-store POS identity to unify with — in-store diners enter only via CSV upload to marketing. https://get.chownow.com/products/rewards-program/ · retrieved 2026-08-01

digital-subscriptions

'Does my online ordering have a membership program?' answers: 'ChowNow offers a membership program... Customers can prepay a membership fee to join - 100% of which goes directly to you - and in return they get a discount on orders for the coming year when they order from your restaurant's website, branded mobile app, or from the ChowNow website, iOS app, or Android app.' ChowNow's Membership Products Terms of Service define the entitlement formally: 'Members are Registered Users who sign up for ChowNow's annual customer membership program... The Customer Membership Program allows Members to pay an annual fee on a per-Restaurant, per-location basis, to earn discounts at such Restaurant locations for orders placed.' That is a paid membership tier billed on a period, entitling the diner to ongoing discounts, administered by the platform across all of the restaurant's ChowNow channels. Enrolment is set up with ChowNow's support/marketing team rather than self-serve, and the separate Restaurant Rewards Program (sticker-card loyalty, per location) is free rather than paid. https://get.chownow.com/restaurant-support/loyalty-program-alternatives/ · retrieved 2026-08-06

digital-promo-parity

Rewards and campaign offers apply consistently across all ChowNow first-party channels. There is no POS or kiosk channel to reach parity with, and reviewers report promos display weakly on the ordering page. https://get.chownow.com/products/rewards-program/ · retrieved 2026-08-01

digital-guest-data-ownership differentiator

The quote is marketing copy on a product page. No contract clause vests ownership in the merchant, and the dossier itself records that ChowNow's privacy policy reserves rights to use the same diner base for its own Marketplace, mParticle analytics, and third-party advertisers/remarketers — while operating a consumer marketplace competing for that diner. Self-serve CSV export of the Customer Spending report is real and verified; ownership is not. That is partial. (The researcher already scored commercial-data-ownership-clause 'partial' — this cell is inconsistent with it.) https://get.chownow.com/legal/privacy-policy/ · retrieved 2026-08-01 adversarially verified

digital-checkout-pci-sca

Checkout is vendor-hosted and processed by Stripe, and ChowNow's terms assert PCI-DSS compliance. No PCI DSS 4.0 statement, no script-integrity (6.4.3/11.6.1) disclosure, and no 3DS documentation. https://get.chownow.com/legal/terms-of-service/ · retrieved 2026-08-01

digital-surcharge-transparency differentiator

Operators can add a service fee by dollar amount or percentage per location, and can choose how the Flex Delivery fee splits with the diner. No dual pricing, no card-brand surcharge engine, no jurisdiction handling documented. https://get.chownow.com/support-category/order-and-payments-processing/ · retrieved 2026-08-01

guest-loyalty-unified-profile

One diner identity spans ChowNow's website, branded app, Marketplace and Discovery Network. In-store guests are brought in only by CSV upload; no automatic POS transaction merge, and no documented dedup/merge rules. https://get.chownow.com/pricing/ · retrieved 2026-08-01

guest-loyalty-thirdparty-identity-attach differentiator

Checked get.chownow.com/products/order-aggregation/ (aggregation is described at the order level - orders from Grubhub, DoorDash, UberEats, SkipTheDishes and Ritual land on one Hub tablet - and the 'your diners, your data' language on that page refers to direct ChowNow channels), the eight articles under get.chownow.com/support-category/order-aggregation/ (per-marketplace connection guides, none of which mention diner records), and get.chownow.com/restaurant-support/customer-data-dashboard/ (lists total spend, order count and average purchase per diner but never says which order sources feed it). No ChowNow page states either that marketplace guest identity attaches to a native profile or that it does not. No help centre exists to search further: support.chownow.com and help.chownow.com do not resolve and chownow.zendesk.com 404s; the support content lives under get.chownow.com/restaurant-support/.

guest-loyalty-accrual-models

One model only: a 'sticker' punch/visit count with an operator-set qualifying minimum order value and an operator-set sticker threshold, redeeming a % or $ reward. No points-per-dollar and no spend-tier accrual. https://get.chownow.com/products/rewards-program/ · retrieved 2026-08-01

guest-loyalty-tiers differentiator

Marketing auto-segments include a behavior-derived VIP segment that diners move in and out of, but this drives campaigns — it is not a loyalty status tier with earn-rate or benefit differentiation. https://get.chownow.com/products/email-sms-marketing/ · retrieved 2026-08-01

guest-loyalty-offline-behavior differentiator

Cloud-only, digital-only; there is no offline path and no offline behavior documented.

guest-loyalty-offer-stacking-rules differentiator

ChowNow resolves discount collisions itself rather than exposing stacking rules: 'When a diner unlocks their reward discount, it will get automatically applied to their next order. If at that time they have another discount for your restaurant associated with their ChowNow account, the system will pick the better of the two.' The configurable surface of the Rewards Settings page is enumerated in this article and in the best-practices guide as three fields only - stickers required per reward, minimum order value to earn a sticker, and reward value (percent-off or dollar-off). There is no exclusive-vs-combinable flag, no precedence/order-of-application setting, and no stacking configuration in the campaign tooling (get.chownow.com/restaurant-support/getting-started-with-custom-on-demand-email-campaigns/, .../getting-started-with-automated-email-sms-campaigns/), where automated campaign content and offers 'cannot be edited at this time'. https://get.chownow.com/restaurant-support/get-started-with-our-restaurant-rewards-program/ · retrieved 2026-08-06

guest-loyalty-targeted-offers differentiator

Help centre campaign builder: 'Select your audience from the library of pre-built, lifecycle-based segments, or target your entire marketing list', then 'make sure the promo code is set up in your dashboard (Marketing > Promotions)' and 'Select the promotion you want to use from the dropdown. The offer details will automatically populate within the email.' The SMS equivalent is the same flow with the promo code pasted into the text. Limit worth recording: the documentation describes choosing from ChowNow's pre-built lifecycle segments or the full list - it does not document an operator-authored rule builder over arbitrary spend or item-purchased criteria. https://get.chownow.com/restaurant-support/getting-started-with-custom-on-demand-email-campaigns/ · retrieved 2026-08-06

guest-loyalty-rfm-segmentation differentiator

Help centre: automated campaigns run against 'lifecycle moments like Welcome, Win Back, and VIP, plus monthly and seasonal promotional sends', and the campaign builder lets the operator 'Select your audience from the library of pre-built, lifecycle-based segments' - i.e. the segments are computed by ChowNow from order activity, with no query-building by the operator. The documentation does not publish the thresholds (what order count makes a VIP, how many days make a diner lapsed); those figures appear only in ChowNow's marketing blog. Also note automated campaign content and promotions 'cannot be edited at this time', and marketing is unusable on Launch (no contacts or send credits). https://get.chownow.com/restaurant-support/getting-started-with-automated-email-sms-campaigns/ · retrieved 2026-08-06

guest-loyalty-lifecycle-automation

Pre-built always-on automations for Welcome, Win Back, VIP and Seasonal moments across email and SMS. Birthday is not among the named triggers. https://get.chownow.com/products/email-sms-marketing/ · retrieved 2026-08-01

guest-loyalty-native-email-sms differentiator

Help centre: SMS is sent from ChowNow itself - the operator submits 10DLC registration (legal name, EIN, business type) via 'Dashboard under Marketing > Campaign Settings' and waits roughly 5 business days for carrier approval; '10DLC registration is required for any business sending SMS marketing messages, regardless of audience size'. Email campaigns are composed in the same Marketing section (Getting Started with Custom On-Demand Email Campaigns), and campaign reporting for both channels lives under Marketing > One-Time Campaigns > Reports. Shortfall to record: 'SMS marketing is included with ChowNow Grow and Elevate plans' - not Launch. https://get.chownow.com/restaurant-support/how-do-i-enable-sms-marketing/ · retrieved 2026-08-06

guest-loyalty-consent-management

Revocation is honoured and is not STOP-keyword-only: diners 'are automatically removed from your active count when they: Unsubscribe from your email or SMS marketing' or hard-bounce, and thereafter 'stay in your database for reporting and history... and won't receive future campaigns'. On-demand SMS templates are 'preloaded with your restaurant's name, and opt-out directions'. Named shortfalls: (1) consent is not captured, it is inferred - the same article enumerates exactly two ways a diner joins the marketing list, 'Automatically, when they place an order' and 'Via a one-time list upload during onboarding', with no opt-in checkbox or consent record described at checkout; (2) consent is not per-channel - 'Each unique diner counts as one contact, whether you reach them by email, SMS, or both', and no separate email/SMS consent state is documented; (3) no consent timestamp or source is stored - get.chownow.com/restaurant-support/how-do-i-add-in-store-diners-to-my-chownow-marketing-list/ puts the burden on the operator to 'confirm these contacts opted in to marketing communications' and to drop anyone who has not received marketing email in 12 months or marketing texts in 6 months, which is an attestation rule rather than a recorded consent artefact. https://get.chownow.com/restaurant-support/understanding-marketing-contact-limits/ · retrieved 2026-08-06

guest-loyalty-10dlc-registration

ChowNow explicitly documents the A2P 10DLC step as part of turning SMS marketing on: '10DLC (10-Digit Long Code) is the carrier-approved framework that allows businesses to legally send SMS marketing messages in the U.S.', and 'Registration is required by mobile carriers to verify your business.' The operator submits legal business name, EIN and business type through ChowNow, which files the registration; approval is stated as roughly five business days, after which SMS campaigns can send. SMS sending itself is metered in credits (get.chownow.com/restaurant-support/understanding-sms-credits/: '1 credit = 1 text message sent to 1 diner', 2 credits over 160 characters or with emoji) and is a Grow/Elevate-tier feature. https://get.chownow.com/restaurant-support/how-do-i-enable-sms-marketing/ · retrieved 2026-08-06

guest-loyalty-campaign-attribution differentiator

Verified that the marketing page says 'Track attributed orders and revenue, not just opens and clicks' — but that is the entire evidentiary basis. No product documentation, no attribution model, no attribution window, no report name, and no support article describing where an operator sees it. Under the marketing-is-claim-level rule this is claim-level on a weighted differentiator. https://get.chownow.com/products/email-sms-marketing/ · retrieved 2026-08-01 adversarially verified

guest-loyalty-data-export-portability differentiator

Support article 'How can I reach the customers I have collected in my database?' documents exporting the Customer Spending report with contact data for external marketing; report exports are self-serve from the dashboard. https://get.chownow.com/restaurant-support/?s=export · retrieved 2026-08-01

guest-loyalty-cdp-event-api differentiator

Withdrawing 'there is no ChowNow developer portal'. There is one, and it rules this out explicitly. The ChowNow Partner API spec has no `webhooks` and no `callbacks` object anywhere in the document - order state is read by polling GET /v1/orders/{order_id}/status - and there is no guest or customer resource among its ten operations. The portal's own status list confirms it: 'These endpoints are not yet implemented and return 501 Not Implemented: Customer creation, lookup, and detail'. So there is no outbound guest-or-order event stream a CDP could subscribe to. The one webhook stream in the ChowNow group, Cuboh Direct's orders.* and merchant.* events, is a channel-partner integration surface - subscription requires Cuboh QA certification and a piloted live merchant, it carries no loyalty or guest-profile events, and it cannot be pointed at an operator's Klaviyo, Punchh or Bridg instance. https://developer.chownow.com/docs/openapi.json · retrieved 2026-08-06 · not refetchable · site policy · graded A when read

guest-loyalty-review-capture-routing differentiator

Re-verified 2026-08-06. The 'What Automated Emails & Texts Are Sent to My Diners?' article is a marketing-automations catalogue (Lifecycle Campaigns: Welcome Series, Win Back 30/60 Days, VIP Special Offer; Promotional Campaigns: Monthly Promos, 2026 Seasonal Promos), not an exhaustive list of all automated diner messaging - it omits transactional mail entirely, so it cannot support an absence finding for post-transaction feedback requests. The counter-evidence hunt found nothing either way: help-centre searches for 'review' and 'feedback' return no rating-capture article, and ChowNow's own blog on getting Google reviews recommends third-party tools (Marqii, Statusbrew) rather than a ChowNow feature. Whether ChowNow sends any post-order rating prompt, and whether responses could be routed by score, is undetermined. adversarially verified

guest-loyalty-referral-program

get.chownow.com/restaurant-support/referral-program/ ('Is there a referral program to recommend other restaurants to ChowNow?') is restaurant-to-restaurant only - it directs the operator to get.chownow.com/refer-a-restaurant/ and pays '$500 USD for any restaurant that purchases the ChowNow Pro Subscription'. That article answers a different question from this claim. The support search for 'rewards' at get.chownow.com/restaurant-support/?s=rewards returns exactly three articles (the two Restaurant Rewards Program articles and that B2B referral page), and the two rewards articles describe only sticker accrual and redemption, with no per-guest referral code, link, first-order attribution or two-sided reward. No ChowNow page states that a guest-to-guest referral mechanic does not exist, and a help-centre search returning nothing is not evidence of absence, so this stays unknown.

guest-loyalty-wallet-pass differentiator

Checked get.chownow.com/restaurant-support/get-started-with-our-restaurant-rewards-program/ and .../restaurant-rewards-program-set-up-best-practices-guide/ - the program is described as diners earning digital 'stickers' per takeout order, tracked against the diner's ChowNow account and redeemed automatically on the next order, with progress and enrolment stats visible to the operator on the Rewards Settings page. Neither article, nor the Rewards Program entry in the product index at get.chownow.com/products/, nor the Marketing Suite rows of the plan table at get.chownow.com/pricing/ (which lists 'Loyalty & Rewards Program') mentions Apple Wallet, Google Wallet, a .pkpass, or any pass with a push-updatable balance. Absence from these pages is not a vendor statement that no wallet pass is issued, so unknown.

guest-loyalty-privacy-rights-tooling

ChowNow operates a vendor-side OneTrust Data Privacy Rights Request webform and a CPRA notice, and diners can access/delete their own contact data in account settings. No operator-facing in-app DSAR tooling and no deletion-propagation documentation. https://get.chownow.com/legal/privacy-policy/ · retrieved 2026-08-01

guest-loyalty-redemption-fraud-controls

The Rewards Settings surface is enumerated the same way in both ChowNow rewards articles and consists of three configurable fields: the number of stickers required to unlock a reward, the minimum order dollar amount that earns a sticker, and the reward value (percent-off or dollar-off). The get-started article additionally states that manually adding stickers to a diner is not available, and that changes to a program apply only 'for new diners going forward'. Redemption is automatic - 'When a diner unlocks their reward discount, it will get automatically applied to their next order' - with no operator step to approve. There is consequently no redemption velocity limit, no manager-approval workflow on point adjustments (there are no manual adjustments), no employee self-redemption flag, and no audit log; the only reporting exposed is aggregate program stats (diners enrolled, rewards unlocked) on the Rewards Settings page. A support search for 'audit' at get.chownow.com/restaurant-support/?s=audit returns 0 results. https://get.chownow.com/restaurant-support/get-started-with-our-restaurant-rewards-program/ · retrieved 2026-08-06

guest-loyalty-ai-offer-recommendation differentiator

Checked get.chownow.com/products/email-sms-marketing/ (segments are 'auto-generated' from 'real behavior such as New, Repeat, VIP, and Lapsed' - a rules description, with no AI or ML wording), get.chownow.com/products/q2-feature-release/ (the Spring 2026 release covers Email & SMS Marketing, Catering and QR Code Ordering, and makes no AI claim), get.chownow.com/restaurant-support/getting-started-with-automated-email-sms-campaigns/ (content and promotions in automated campaigns 'cannot be edited at this time'; campaigns are on by default), and .../getting-started-with-custom-on-demand-sms-campaigns/ (send time is operator-chosen from a date/time picker, with static best-practice guidance to send 10-11am or 4-6pm rather than a computed recommendation). None of the thirteen entries in the product index at get.chownow.com/products/ advertises an AI feature. That is a wide but not exhaustive read of the vendor's own claims, and no page states ChowNow does not offer AI recommendations, so this stays unknown rather than becoming a negative assertion.

guest-loyalty-stored-value-gift

Checked get.chownow.com/products/ - the full product index lists thirteen products across Ordering (Online Ordering, Branded Mobile Apps, Website Builder, Marketplace, Discovery Network, Catering, QR Code Ordering), Marketing (Email & SMS Marketing, Rewards Program) and Operations (Flex Delivery, Order Aggregation, Advanced Reporting) and includes no gift-card or stored-value product. The 'Compare Plans Included Features' table at get.chownow.com/pricing/ lists the Marketing Suite as Automated Email Marketing, Automated SMS Marketing, On-Demand Campaigns, CSV Upload, Loyalty & Rewards Program and Print Marketing, with no gift card on any of Launch/Grow/Elevate. A support search at get.chownow.com/restaurant-support/?s=gift+card returns 'Found 0 results'. Under the evidence rule these are a product roundup, a pricing page and a null help-centre search - none is an exhaustive enumeration or a vendor statement of non-support - so this remains unknown despite the consistent signal.

labor-clock-in-at-pos

No labor module of any kind; 7shifts is ChowNow's named team-management partner. https://get.chownow.com/partners/ · retrieved 2026-08-01

labor-photo-punch-verification differentiator

No labor module.

labor-geofenced-mobile-punch

No labor module.

labor-offline-time-punch differentiator

No labor module.

labor-granular-rbac

Re-verified 2026-08-06. The only surface ChowNow publishes on dashboard permissions is the FAQ 'Can I add more users to my dashboard?', which shows the create-user form offering 'Company admin (can change settings for all locations)' or 'Regional admin (they are only associated with a specific location)'. That is a creation-flow how-to, not a permissions reference, and it asserts nothing about what can be configured on a user after creation. Help-centre searches for roles, permissions, users and 'regional admin' surface no permissions article. The two named options are location scope rather than per-action grants, which makes granular RBAC unlikely, but no documented settings surface establishes its absence. adversarially verified

labor-manager-override-audit

No labor module and no POS override construct.

labor-native-scheduling differentiator

No labor module; 7shifts partner. https://get.chownow.com/partners/ · retrieved 2026-08-01

labor-demand-labor-forecast differentiator

No labor module.

labor-realtime-labor-percent differentiator

No labor data in the platform.

labor-overtime-prevention differentiator

No labor module.

labor-break-compliance-by-state differentiator

No labor module.

labor-fair-workweek-support

No labor module.

labor-minor-labor-rules

No labor module.

labor-tip-pooling-rules

Tips are passed through in disbursements; no pooling engine. https://get.chownow.com/support-category/order-and-payments-processing/ · retrieved 2026-08-01

labor-tip-distribution-audit-trail

No per-employee tip ledger.

labor-qualified-tips-w2-reporting differentiator

ChowNow issues 1099s to restaurants earning $20,000+; it has no employee-level payroll or W-2 reporting. https://get.chownow.com/support-category/billing-my-account/ · retrieved 2026-08-01

labor-native-payroll differentiator

No payroll product.

labor-payroll-export-formats

No labor hours to export; no named payroll integrations on the integrations page. https://get.chownow.com/integrations/all/ · retrieved 2026-08-01

labor-shift-swap-workflow differentiator

No labor module.

labor-digital-onboarding-i9

No HR module.

labor-server-performance-metrics differentiator

No employee dimension in reporting. https://get.chownow.com/products/advanced-reporting/ · retrieved 2026-08-01

inventory-recipe-bom-costing

No inventory module; MarketMan is the named inventory partner. https://get.chownow.com/partners/ · retrieved 2026-08-01

inventory-unit-conversion-yields

No inventory module.

inventory-theoretical-vs-actual differentiator

No inventory module.

inventory-realtime-depletion differentiator

No inventory module.

inventory-86-auto-sync differentiator

Item and modifier 86 syncs automatically from the connected POS's own stock status out to ChowNow and the marketplaces — but it is POS-driven availability, not ingredient-level depletion or threshold logic owned by ChowNow. https://get.chownow.com/restaurant-support/?s=inventory · retrieved 2026-08-01

inventory-count-modes

No inventory module.

inventory-mobile-count-offline

No inventory module.

inventory-vendor-catalogs-edi differentiator

US Foods appears on the partners page as a distributor discount relationship, not an EDI catalog/PO integration. https://get.chownow.com/partners/ · retrieved 2026-08-01

inventory-invoice-ocr differentiator

Ottimate is listed as an AP-automation partner, not a ChowNow feature. https://get.chownow.com/partners/ · retrieved 2026-08-01

inventory-price-change-alerts differentiator

No purchasing module.

inventory-par-auto-suggest differentiator

No purchasing module.

inventory-waste-logging

No inventory module.

inventory-transfers

No inventory module.

inventory-commissary

No inventory module.

inventory-lot-traceability

No inventory module.

inventory-shelf-life-expiry

No inventory module.

inventory-bar-partial-bottle

No inventory module.

inventory-cogs-gl-export

No COGS data and no accounting connectors in the integrations directory. https://get.chownow.com/integrations/all/ · retrieved 2026-08-01

inventory-native-not-partner differentiator

Explicitly partner-delivered: MarketMan is listed as ChowNow's inventory partner. https://get.chownow.com/partners/ · retrieved 2026-08-01

inventory-menu-margin-linkage differentiator

Item & Modifier reports are marketed as identifying 'top sellers and margin drivers', but there is no recipe cost input, so no true contribution margin per item. https://get.chownow.com/products/advanced-reporting/ · retrieved 2026-08-01

reporting-realtime-dashboard

Centralized performance dashboard with on-demand, real-time data across first- and third-party channels and multi-location visibility. Browser-based; no operator mobile app documented. https://get.chownow.com/products/advanced-reporting/ · retrieved 2026-08-01

reporting-eod-closeout

Disbursement Reports reconcile payouts line-by-line, available ~1 hour after closing each business day. No tender-type/cash/tax EOD reconciliation — there is no POS drawer. https://get.chownow.com/support-category/order-and-payments-processing/ · retrieved 2026-08-01

reporting-pmix-modifier-level

Item & Modifier Reports are one of the four named report families, covering top sellers and margin drivers. https://get.chownow.com/products/advanced-reporting/ · retrieved 2026-08-01

reporting-comps-voids-audit

No comp/void/override constructs exist in a digital-ordering-only platform, and no such report is listed. https://get.chownow.com/products/advanced-reporting/ · retrieved 2026-08-01

reporting-cash-over-short

No cash drawer.

reporting-labor-productivity

No labor data in the platform.

reporting-server-scorecards differentiator

No employee dimension.

reporting-channel-profitability differentiator

Comparative Analytics benchmarks performance across channels, locations and time periods, with claimed 'margin reporting across every platform' and commission tracking. Explicit net-of-commission P&L by marketplace is not documented. https://get.chownow.com/products/advanced-reporting/ · retrieved 2026-08-01

reporting-multiloc-drilldown differentiator

Multi-location visibility plus a dashboard location switcher and comparative analytics across locations; a formal group-to-location-to-transaction drilldown path is not documented. https://get.chownow.com/products/advanced-reporting/ · retrieved 2026-08-01

reporting-custom-report-builder differentiator

Re-verified 2026-08-06. The cited article's purpose is exporting to Excel; its report list is introduced as 'Below are the types of reports you can run', but the article is scoped to the retired ChowNow Pro / Hub / Premier product lines, so it is not authoritative for the current Launch/Grow/Elevate dashboard and a builder living elsewhere would not appear in it. The Advanced Reporting product page (retrieved with a Googlebot UA; a normal UA gets a Cloudflare 403) advertises four fixed report families plus a centralized dashboard and no builder, but it is grade-C marketing. Help-centre searches for 'custom report' and 'report builder' return no relevant article. No self-service dimension/measure builder was found, and none was ruled out. adversarially verified

reporting-scheduled-delivery

Recurring emailed reporting exists: from the Dashboard, select the location under 'Headquarters', then Settings > Email Notifications, enter email addresses and choose 'daily, weekly, and/or monthly order reports'; the article states you can 'sign up as many people as you'd like to receive' them, so cadence and recipient list are both configurable. Named shortfall: this is a notification setting for order summaries, not a scheduler for reports - the claim's 'any report' is not met. The Reports section itself (get.chownow.com/restaurant-support/how-to-run-reports/) offers Analytics, Accounting Data, Customer Data, Promo Data, Order Source, Order History, Order Edit Data, Cancellation Data, Order Control Data, POS Errors, Item Report and Modifier Report only as manual runs finished by clicking Export to Excel, with no scheduling option and no shared destination (SFTP, drive, webhook). https://get.chownow.com/restaurant-support/daily-order-summaries-dashboard/ · retrieved 2026-08-06

reporting-raw-warehouse-export differentiator

Withdrawing the 'no API' leg. The ChowNow Partner API spec declares exactly ten operations - GET /v1/restaurants, GET /v1/restaurants/{id}, GET /v1/restaurants/{id}/menu, GET /v1/restaurants/{id}/availability, POST /v1/quotes, POST /v1/orders, GET /v1/orders/{id}, POST /v1/orders/{id}/cancel, GET /v1/orders/{id}/status, POST /v1/orders/{id}/refunds - and that enumeration is exhaustive for the product. None is a bulk or recurring export; there is no destination configuration of any kind (the strings S3, SFTP, warehouse, Snowflake, BigQuery and export do not occur in the document), and orders are addressable only one at a time by order_id, with no list-orders endpoint, so transaction-level data cannot even be swept programmatically. Operator-side, the dashboard offers manual CSV download only. Automated recurring bulk export to a customer-controlled destination does not exist. https://developer.chownow.com/docs/openapi.json · retrieved 2026-08-06 · not refetchable · site policy · graded A when read

reporting-public-api differentiator

A public API exists and is documented: 'ChowNow Developer API', OpenAPI 3.1, version 0.1.0-draft, server https://openapi.chownow.com/v1, security scheme workos_m2m (OAuth2 client-credentials via WorkOS), with exactly ten operations - GET /v1/restaurants, GET /v1/restaurants/{id}, GET /v1/restaurants/{id}/menu, GET /v1/restaurants/{id}/availability, POST /v1/quotes, POST /v1/orders, GET /v1/orders/{id}, POST /v1/orders/{id}/cancel, GET /v1/orders/{id}/status, POST /v1/orders/{id}/refunds. Coverage against the claim: orders yes (place, read, status, cancel, refund), payments partly (a Totals breakdown of item_total, discount, subtotal, sales_tax, delivery_fee, service_fee, tip, total, total_due on quotes and orders - no settlement, payout or tender reporting), menu read-only. Shortfalls: no labor data of any kind; there is no list-orders or reporting endpoint, so this is a transactional partner-ordering API rather than a reporting API; and credentials are not self-service - 'Ask ChowNow for Partner API access. Your request is reviewed by our team; it can be approved for sandbox, or declined', with production access granted only after sandbox approval and governed by an integration agreement. https://developer.chownow.com/docs/openapi.json · retrieved 2026-08-06 · not refetchable · site policy · graded A when read

reporting-webhooks differentiator

Outbound webhooks exist on one of ChowNow's two published APIs. The Cuboh Direct spec (Cuboh is ChowNow's subsidiary, the engine behind the Hub product) carries an OpenAPI 3.1 'webhooks:' block with orders.new, orders.update, orders.accept, orders.adjust, orders.cancel, orders.complete, merchant.new, merchant.update, merchant.open, merchant.close, delivered to a subscriber-defined HTTPS URL, signed with an 'X-Cuboh-Signature' HMAC-SHA256 of the body, and retried on 500/502/503/504/429 'based on an exponential backoff algorithm. Ex. 1 second after the initial attempt, then 2 seconds, then 4 seconds until 5 total events were sent'. Shortfalls: ChowNow's own Partner API (developer.chownow.com/docs/openapi.json, verified 2026-08-06) declares no webhooks and no callbacks at all - order state is polled via GET /v1/orders/{id}/status; there are no payment lifecycle events (no paid, voided or refunded webhook - Cuboh exposes refund only as an inbound POST); and the endpoint owner must be a QA-certified Cuboh channel partner, not an operator supplying their own URL. https://docs.cuboh.com/static/media/direct.cc50b46f10923bea774a.yml · retrieved 2026-08-06

reporting-api-not-upcharged differentiator

Withdrawing 'no API to include' - an API exists. It is nonetheless not a subscription entitlement. The Getting Access page enumerates the complete lifecycle in four stages: 'Partner API access is granted in two stages: sandbox first, then production. Production access is only reachable after sandbox approval - the ordering is enforced by the platform, not by convention'; 'Ask ChowNow for Partner API access. Your request is reviewed by our team; it can be approved for sandbox, or declined'; and 'Approved access can later be revoked under the terms of your integration agreement.' No path from a ChowNow restaurant subscription to API or raw-data access appears anywhere on the portal, and the API's own description scopes it to 'ChowNow marketplace partners' rather than to subscribing restaurants. Access is therefore gated behind a separately negotiated partner agreement, which is exactly what this claim asks about; the commercial terms of that agreement are not published. https://developer.chownow.com/docs/getting-access · retrieved 2026-08-06 · not refetchable · site policy · graded A when read

reporting-tier-paywall differentiator

'Reporting' is checked on all three tiers including Launch, so core reporting is not paywalled — but tier differences are marketing contacts/SMS credits, and whether the full 'Advanced Reporting' set sits on Launch is not stated. https://get.chownow.com/pricing/ · retrieved 2026-08-01

reporting-history-retention differentiator

The Analytics view carries no history limit: 'You are able to view sales data starting from your first day on ChowNow', over an operator-selected date range, exportable to CSV. Named shortfall: that is aggregate sales analytics (gross vs net sales, order source, average order amount, hourly peaks), not the transaction-level detail the claim requires. On the transaction-level reports, get.chownow.com/restaurant-support/how-to-run-reports/ documents the Accounting Data report as showing individual orders 'up to 90 days' and Order Source as covering 'a time range no greater than 30 days'. ChowNow publishes no retention window for order-level data, states nothing about truncation, and names no archive-retrieval fee, so a 24-month transaction-level look-back is neither documented as available nor priced. https://get.chownow.com/restaurant-support/how-to-view-sales-analytics-on-the-dashboard/ · retrieved 2026-08-06

reporting-anomaly-alerts differentiator

Checked the only documented notification surface, Settings > Email Notifications (get.chownow.com/restaurant-support/daily-order-summaries-dashboard/), which describes choosing daily, weekly and/or monthly order reports for a list of recipients - a fixed-cadence digest, not a metric threshold. Also checked get.chownow.com/restaurant-support/how-to-view-sales-analytics-on-the-dashboard/ and .../how-do-i-view-sales-trends-on-the-dashboard/ (date-range comparison of gross/net sales, order source, hourly peaks, CSV export - no alert configuration), the twelve canned reports at .../how-to-run-reports/, and get.chownow.com/products/advanced-reporting/ (dashboard plus four report families, no alerting claim). The Email Notifications article does not enumerate every notification type the screen offers, so I cannot treat it as the complete configurable surface, and no ChowNow page states that threshold or anomaly alerts are unavailable.

reporting-nl-query

Checked get.chownow.com/restaurant-support/how-to-run-reports/ (select a named report, set parameters, Run Report, Export to Excel), .../how-to-view-sales-analytics-on-the-dashboard/ and .../how-do-i-view-sales-trends-on-the-dashboard/ (date-range and multi-location selectors over gross/net sales, order source, average order amount and hourly peaks, with CSV export), get.chownow.com/products/advanced-reporting/ (Centralized Performance Dashboard plus Order, Item & Modifier, Comparative Analytics and Disbursement report families) and get.chownow.com/products/q2-feature-release/ (Spring 2026 release: Email & SMS Marketing, Catering, QR Code Ordering - no assistant). No natural-language or chat query surface appears in any of them, but none of these pages asserts that ChowNow lacks one, so this stays unknown.

reporting-guest-cohorts differentiator

Guest-level raw data yes, cohort reporting no. The Customer Data report 'will show you your customer's email addresses, when they ordered last, the total number of orders they've placed at your restaurant and much more', and the dashboard article adds 'each diner's total spend, amount of orders, their average purchase' - so lifetime spend and order frequency are available per identifiable diner and exportable. Named shortfall: no documented report of new-versus-returning guest counts, retention or frequency cohorts; Order Source gives only 'the amount of customers you had, their average order amount, your largest order' for a window of at most 30 days, and the New/Repeat/VIP/Lapsed lifecycle segments are selectable as campaign audiences, not reported as cohort sizes. Campaign reports are aggregate only (sent, opens, clicks, sales within 14 days, unsubscribes). https://get.chownow.com/restaurant-support/how-to-run-reports/ · retrieved 2026-08-06

reporting-sales-forecast differentiator

Checked get.chownow.com/restaurant-support/how-to-view-sales-analytics-on-the-dashboard/ (compare gross vs net sales over a chosen date range, identify peak order times by hour, export CSV - all retrospective), .../how-do-i-view-sales-trends-on-the-dashboard/ (single or multiple locations, comparison of gross sales across selected time periods, average order amount, peak times), the twelve canned reports at .../how-to-run-reports/ (none named as a forecast or projection), and get.chownow.com/products/advanced-reporting/ (Order Reports, Item & Modifier Reports, Comparative Analytics, Disbursement Reports - 'benchmark performance across channels, locations, and time periods', i.e. historical). No forward projection at daypart or hourly granularity is described, and no page states one does not exist, so unknown.

reporting-tip-tax-compliance

ChowNow issues restaurant-level 1099s only; there is no employee-level declared-vs-charged tip reporting or pool distribution detail. https://get.chownow.com/support-category/billing-my-account/ · retrieved 2026-08-01

multi-location-org-hierarchy

An above-store tier exists and is a real object rather than a flat list: the dashboard shows a 'Headquarters' label in the left sidebar and the operator switches context by clicking it and then searching for or selecting a location. Reporting can span it - the Analytics view lets the operator 'select either a single location or multiple locations to view their sales data' (get.chownow.com/restaurant-support/how-do-i-view-sales-trends-on-the-dashboard/) - and permissions are scoped to it: Settings > Users > Create offers Company admin, who 'can change settings for all locations', or Regional admin, who is 'only associated with a specific location'. Named shortfall: the hierarchy is two levels (Headquarters > location), not the three the claim requires. Despite its name the Regional admin role is scoped to named locations, not to a region; no region, group, market or brand object is documented anywhere as something reporting or permissions can target, and multi-location reporting is done by multi-selecting individual locations. https://get.chownow.com/restaurant-support/how-can-i-switch-which-location-i-am-viewing-in-the-dashboard/ · retrieved 2026-08-06

multi-location-central-menu-publish

Centralized menu management publishes one edit across channels from a single dashboard. Publishing to a selected set of LOCATIONS with version history showing what/when/who is not documented. https://get.chownow.com/products/order-aggregation/ · retrieved 2026-08-01

multi-location-local-override-policy differentiator

Checked get.chownow.com/restaurant-support/what-is-the-menu-editor/ (import a menu, add or edit menu names, hours, categories, descriptions and prices, manage modifiers, then publish 'straight to your delivery partners in real-time'), .../how-to-update-menu-prices-using-menu-editor/ (edit individually or in bulk; 'Any menu changes need to be published in order to show on the delivery apps connected to the menu'), .../menu-items/, .../modifiers/ and .../how-do-i-adjust-the-prices-on-all-my-menu-items-at-once/. None of these describes a corporate master menu, an inheritance relationship between a parent and a location menu, per-field override permissions, or fields locked at store level. The dashboard's only permission distinction is Company admin vs Regional admin at the whole-location level (.../adding-users-dashboard/), which is coarser than the per-field model the claim asks about. No ChowNow page states that per-field override rules do not exist, so unknown.

multi-location-price-zones

One of the claim's three dimensions is real and now primary-sourced. The ChowNow Partner API spec (OpenAPI 3.1, developer.chownow.com/docs/openapi.json) documents the menu fetch as issued 'with a neutral User-Agent (partner-gateway/1.0) and NO cn_channel query param -> base, no-markup pricing (CN-48933)' - so ChowNow's menu service carries a channel-keyed markup over a single base price, the same mechanism the vendor markets as 'a baked-in tool that automatically adjusts menu prices to offset standard fees'. One item record, different prices by channel, no duplication. Shortfalls: the markup is ChowNow's automatic fee-offset keyed to a channel identifier, not an operator-defined price tier or zone object - no zone/tier entity appears in the spec or in the Menu Editor articles; there is no location-group price dimension (menus resolve per restaurant_id, and bulk edit is documented only as one uniform dollar or percentage change across 'All Items' or 'All Modifiers'); and per-daypart pricing is positively excluded - 'ChowNow will always display the base price at all times of the day'. https://developer.chownow.com/docs/openapi.json · retrieved 2026-08-06 · not refetchable · site policy · graded A when read

multi-location-scheduled-publish differentiator

Checked get.chownow.com/restaurant-support/what-is-the-menu-editor/ ('publish... straight to your delivery partners in real-time'), .../how-to-update-menu-prices-using-menu-editor/ ('Any menu changes need to be published in order to show on the delivery apps connected to the menu' - an immediate manual publish, with no effective-date field), and .../how-do-i-adjust-the-prices-on-all-my-menu-items-at-once/ (immediate bulk change, reversed only by editing back). A support search at get.chownow.com/restaurant-support/?s=schedule returns 19 results, all about scheduled ORDERS on the Hub tablet, campaign send scheduling, catering and snooze intervals - none about scheduling a menu, price or promo change. Menu hours are editable (a recurring availability window), which is not the same as a future-dated change activation. No version history or rollback control is documented, and no page states future-dated publishing is unavailable, so unknown.

multi-location-new-store-template differentiator

Checked get.chownow.com/restaurant-support/how-to-add-another-restaurant-chownow/, ChowNow's own answer to adding a location, which reads in full as an instruction to 'Contact your Restaurant Success Manager or email support@chownow.com. We'll provide you with the proper documentation to get started with onboarding for your new location and we'll put you in contact with a sales rep if you have any questions.' It says nothing about whether menu, tax, role, printer, modifier or tender configuration is copied from an existing location, and gives no time-to-open. The Onboarding support category (get.chownow.com/support-category/onboarding/) and the pricing page (which carries a one-time setup fee) likewise publish no expected launch timeline. Because the article is a hand-off instruction rather than an enumeration of the provisioning surface, the absence of a clone-from-template feature is not established, so unknown.

multi-location-corp-vs-franchisee-roles differentiator

Checked get.chownow.com/restaurant-support/adding-users-dashboard/ - the entire user model is one account with Company admin ('can change settings for all locations') and Regional admin ('only associated with a specific location'), i.e. scope within a single tenant, with no notion of a separately-owned sub-tenant, no cross-tenant visibility grant, and no separation of banking or employee data. A support search at get.chownow.com/restaurant-support/?s=franchise returns 'Found 0 results', and get.chownow.com/pricing/ prices per location with no franchise or enterprise tier. ChowNow also operates no labor module, so 'the franchisee owns its own employees and labor data' has no counterpart in the product. That said, the user-creation screen speaks to roles rather than to account/billing tenancy, and a null help-centre search is not evidence of absence, so the claim as worded is unresolved.

multi-location-royalty-calculation differentiator

Checked get.chownow.com/restaurant-support/?s=franchise ('Found 0 results'), the twelve canned reports enumerated at .../how-to-run-reports/ (Analytics, Accounting Data, Customer Data, Promo Data, Order Source, Order History, Order Edit Data, Cancellation Data, Order Control Data, POS Errors, Item Report, Modifier Report - no royalty or fee-calculation report), the four report families on get.chownow.com/products/advanced-reporting/ (Order, Item & Modifier, Comparative Analytics, Disbursement - Disbursement Reports 'reconcile payouts with line-item clarity', i.e. ChowNow's own payouts to the restaurant, not franchisor fee capture), and the plan comparison at get.chownow.com/pricing/, whose Operations Suite is Fraud & Chargeback Protection, Order Aggregation, Menu Management, POS Integrations, Delivery Management, Reporting and 24/7 Support. Nothing configures a royalty basis or schedule. As the earlier verifier noted, no ChowNow source affirmatively states royalty tooling is absent and none of these surfaces is an exhaustive franchise-feature enumeration, so the honest value stays unknown. Same reasoning applies to multi-location-royalty-collection. adversarially verified

multi-location-royalty-collection

No franchise financial tooling.

multi-location-consolidated-reporting

Dashboard tracks sales and ordering trends 'across first- and third-party channels with multi-location visibility' and benchmarks across locations. Store-vs-store ranking and variance flags are not documented. https://get.chownow.com/products/advanced-reporting/ · retrieved 2026-08-01

multi-location-normalized-item-rollup differentiator

Checked get.chownow.com/restaurant-support/how-to-run-reports/, which lists an Item Report and a Modifier Report under the ChowNow Hub and Premier report set but does not describe their grouping key or whether they can span locations; .../how-do-i-view-sales-trends-on-the-dashboard/, where the operator can 'select either a single location or multiple locations to view their sales data' but the metrics shown are gross sales, average order amount and peak order times with no item-level breakdown; and get.chownow.com/products/advanced-reporting/, which claims 'Item & Modifier Reports identify top sellers and biggest margin drivers' and separately that 'Comparative Analytics benchmark performance across channels, locations, and time periods' - marketing copy that never says items are matched across locations by a shared identifier. Menus are documented as per-location objects built by import or by hand (.../what-is-the-menu-editor/) with no corporate item ID construct described. Whether renamed or locally-priced items normalise into one rollup row is therefore unresolved.

multi-location-cross-location-giftcard

Checked get.chownow.com/products/ (full product index: Online Ordering, Branded Mobile Apps, Website Builder, Marketplace, Discovery Network, Catering, QR Code Ordering, Email & SMS Marketing, Rewards Program, Flex Delivery, Order Aggregation, Advanced Reporting - no gift or stored-value product), the 'Compare Plans Included Features' table at get.chownow.com/pricing/ (Ordering, Marketing and Operations suites across Launch/Grow/Elevate, no gift card line), and get.chownow.com/restaurant-support/?s=gift+card ('Found 0 results'). There is consequently nothing documented to redeem across locations, no outstanding-liability report among the twelve canned reports at .../how-to-run-reports/, and no inter-store settlement mechanism described. Because a product roundup, a pricing page and a null help-centre search are none of them an exhaustive enumeration or a vendor statement of non-support, this remains unknown. Note also that the one balance ChowNow does hold per diner - Rewards stickers - is documented as per-location only.

multi-location-cross-location-loyalty

ChowNow states the limitation directly: 'Today the Rewards Program works on a per-location basis only.' A diner's sticker accrual and unlocked reward therefore belong to the individual location that ran the program, and are not shared across the other locations of the brand; each location configures its own sticker goal, minimum order value and reward value, and changes 'go into effect for new diners going forward' at that location. The claim's requirement of a single loyalty profile and balance shared brand-wide is not met by design. (The diner does hold one ChowNow account with order history, but the loyalty balance the claim turns on is explicitly per location.) https://get.chownow.com/restaurant-support/get-started-with-our-restaurant-rewards-program/ · retrieved 2026-08-06

multi-location-multi-brand differentiator

Checked get.chownow.com/restaurant-support/cuboh-tablet-overview/ and .../chownow-hub-overview/ (the Hub aggregates orders from Grubhub, DoorDash, UberEats, SkipTheDishes, Ritual and ChowNow onto one tablet and dashboard; the tablet references filtering 'by specific merchant' but no article explains what a merchant is in a multi-brand sense), .../managing-your-settings-on-the-cuboh-app/ (settings are auto-print, printer connections, ticket formatting, item/modifier 86-ing, prep times, snooze defaults - nothing brand-scoped), and a support search at get.chownow.com/restaurant-support/?s=virtual+brand ('Found 0 results'). ChowNow is an ordering layer with no cash drawer or terminal of its own, so the claim's 'same hardware and drawer' has no direct counterpart, and the vendor publishes nothing stating that a second brand cannot run alongside the first. Unresolved.

multi-location-multi-tax-jurisdiction

Tax is handled per location and ChowNow publishes a Marketplace Facilitator Laws FAQ covering marketplace-collected tax; subscription sales tax is applied by state/local rules. Multiple simultaneous rates and prepared-food vs grocery rules are not documented. https://get.chownow.com/support-category/order-and-payments-processing/ · retrieved 2026-08-01

multi-location-multi-currency-locale

ChowNow operates in the US and Canada — the support portal has a Canada-specific section — but consolidated multi-currency reporting is not documented. https://get.chownow.com/restaurant-support/ · retrieved 2026-08-01

multi-location-config-audit-log differentiator

Checked get.chownow.com/restaurant-support/?s=audit ('Found 0 results'), the eleven articles in the 'Using the ChowNow Dashboard' category at get.chownow.com/support-category/using-admin/ (sales analytics, password reset, demo orders, login, Toast alternate steps, sales trends, running/exporting reports, adding users, customer data, alternate contact, daily order summaries - no change-history or activity-log article), the twelve canned reports at .../how-to-run-reports/ (the closest is Order Edit Data and Order Control Data, both order-level rather than configuration-level), and .../adding-users-dashboard/ (creating a user records contact details and a permission level; no audit surface is mentioned). Menu edits are described as immediate with no version history (.../how-to-update-menu-prices-using-menu-editor/). None of this is an enumeration that would exclude an audit log, and a null support search is not evidence of absence, so unknown.

multi-location-enterprise-sso differentiator

Checked get.chownow.com/restaurant-support/adding-users-dashboard/ (Settings > Users > Create, enter the new user's contact information and choose Company admin or Regional admin - a ChowNow-local account, with no identity-provider, domain or federation step), .../how-can-i-reset-my-cuboh-password/ and .../how-do-i-log-into-the-web-dashboard/ (ChowNow-hosted credentials and password reset), and a support search at get.chownow.com/restaurant-support/?s=single+sign-on ('Found 0 results'). No SAML, OIDC, SCIM or directory-sync language appears on the support site or in the plan comparison at get.chownow.com/pricing/, which has no enterprise tier above Elevate. ChowNow publishes no developer or admin API documentation portal that would carry an SSO configuration reference. Because that is silence rather than a stated boundary, and enterprise SSO is commonly arranged off-catalogue, this stays unknown.

multi-location-enterprise-api differentiator

Withdrawing 'no public API of any kind'. A public API exists and one credential does span locations - a single organization-level OAuth2 client-credentials token authorizes GET /v1/restaurants across the whole ChowNow network, so per-location credentials are not required. But the claim's substance, transaction-level data across all locations in one authenticated call, is absent: of the ten declared operations the only order reads are GET /v1/orders/{order_id} and GET /v1/orders/{order_id}/status, both single-order and both requiring an order_id the caller already holds. There is no list-orders, no date-range query, no per-location transaction feed and no BI or warehouse export operation in the document, and the spec's operation list is exhaustive. https://developer.chownow.com/docs/openapi.json · retrieved 2026-08-06 · not refetchable · site policy · graded A when read

multi-location-central-labor-policy

No labor module.

extensibility-public-api-docs

Withdrawing the earlier shortfall that ChowNow publishes no API reference of its own. developer.chownow.com serves /docs/openapi.json (OpenAPI 3.1, 55KB, HTTP 200, no credentials) plus /docs/getting-started, /docs/getting-access and /docs/authentication as full prose - all four retrieved anonymously on 2026-08-06. The reference is complete on its face: base URL, the ten operations, request and response schemas, error shapes, the workos_m2m OAuth2 client-credentials scheme with its five scopes, the token endpoints, a worked curl token exchange, the rate limit, a troubleshooting table and the live-vs-501 endpoint status list. Nothing is behind a sign-in, an NDA or a sales call - the 'Sign in' and 'Request access' links govern credential issuance, not readability. Cuboh's Direct and Connect specs (docs.cuboh.com) are separately readable in full and corroborate the same posture for the Hub product. The API is versioned 0.1.0-draft, which bears on maturity but not on whether the documentation is public. https://developer.chownow.com/docs/openapi.json · retrieved 2026-08-06 · not refetchable · site policy · graded A when read

extensibility-api-access-cost differentiator

Withdrawing 'no ChowNow operator API exists to be priced'. The Partner API exists, and the portal enumerates its access path completely, with no subscription route among the stages: 'Partner API access is granted in two stages: sandbox first, then production. Production access is only reachable after sandbox approval - the ordering is enforced by the platform, not by convention'; 'Ask ChowNow for Partner API access. Your request is reviewed by our team; it can be approved for sandbox, or declined'; 'Approved access can later be revoked under the terms of your integration agreement'; and 'your integration agreement determines which scopes and endpoints are available to you'. The API is scoped to 'ChowNow marketplace partners' - buying a ChowNow restaurant subscription (Launch, Grow or Elevate on get.chownow.com/pricing/) grants no API access at all, and the public Restaurant Agreement's fee definitions (Subscription Fee, Marketing Fee, Add-On Fees, Set up Fee, Direct Service Charge, Credit Card Processing Charges) contain no API entitlement. So access is conditioned on a separate negotiated agreement rather than included; what that agreement costs is not published. https://developer.chownow.com/docs/getting-access · retrieved 2026-08-06 · not refetchable · site policy · graded A when read

extensibility-partner-revshare

'If a restaurant uses your link to purchase a ChowNow Subscription, you'll earn a $500 reward after they've been live with ChowNow for 30 days. You'll get an email from PartnerStack to create an account and get paid via PayPal or Stripe.' The page is public and ungated, states no referral cap ('There's no limit to how many restaurants you can refer'), does not require the referrer to be a customer, and enumerates qualifying and excluded business types plus the conditions under which a referral is marked unqualified. A specific referral fee is therefore published; a percentage rev-share for integration partners is not, but the claim is satisfied by any one of the three named forms. https://get.chownow.com/refer-a-restaurant/ · retrieved 2026-08-06

extensibility-free-sandbox differentiator

Re-scored against ChowNow's own portal rather than the Cuboh spec. A first-party sandbox exists and precedes any paid relationship: base URLs are 'Production https://openapi.chownow.com/v1' and 'Sandbox https://partner.openapi.chownow.com/v1 (being provisioned)', with a separate sandbox token issuer, and the access lifecycle grants sandbox first - 'Production access is only reachable after sandbox approval'. No fee is attached to it and no production account is required to reach it. Shortfalls, all stated by ChowNow: it is not open self-serve - 'Ask ChowNow for Partner API access. Your request is reviewed by our team; it can be approved for sandbox, or declined'; it is still 'being provisioned'; and there is no seeded test data because it is not an isolated environment at all - 'Sandbox and production credentials call the same API with the same data - the only difference is which set of credentials you were issued. There is no order or data isolation between the two today.' Cuboh's core-staging.cuboh.net development server exists on the Hub side under the same manual-credential model. https://developer.chownow.com/docs/getting-started · retrieved 2026-08-06 · not refetchable · site policy · graded A when read

extensibility-oauth-partner-apps

The ChowNow Developer API (OpenAPI title 'ChowNow Developer API', version 0.1.0-draft, server https://openapi.chownow.com/v1) declares exactly one security scheme, 'workos_m2m: type: oauth2', with a clientCredentials flow (production token endpoint https://auth.developer.chownow.com/oauth2/token, sandbox https://diverse-touch-59-partner.authkit.app/oauth2/token) and five scopes - restaurants:read, catalog:read, orders:read, orders:write, orders:refund - applied per operation (GET /v1/restaurants requires restaurants:read; POST /v1/orders/{order_id}/refunds requires orders:refund). The Authentication guide adds that the token is an RS256 JWT whose 'scope' claim the gateway enforces, rejecting a request that lacks the scope with 403 Forbidden; that the client secret is shown once and is rotatable, and 'the old one keeps working until you revoke it'; and the portal's own API exposes POST /api/v1/apps/{public_id}/secrets/revoke. Shortfalls against the claim: the permissions are ChowNow-granted at partnership level, not operator-granted - 'Your application is granted the API scopes for the current endpoint surface... You do not choose scopes per application yet', 'per-application scope selection is planned', and orders:refund is 'granted selectively' - so there is no restaurant-operator consent step and no per-app scope grant; access is also gated behind a manual request/approval lifecycle (sandbox approval, then production approval). The separate Cuboh/Hub specs at docs.cuboh.com remain static bearer tokens 'valid for 10 years', unique per partner and unscoped. https://developer.chownow.com/docs/openapi.json · retrieved 2026-08-06 · not refetchable · site policy · graded A when read adversarially verified

extensibility-webhooks-push

Split verdict across ChowNow's two published APIs. ChowNow's own Partner API spec (developer.chownow.com/docs/openapi.json, OpenAPI 3.1) contains no `webhooks` and no `callbacks` object anywhere; order lifecycle is read by polling GET /v1/orders/{order_id}/status, which is precisely what this claim asks a platform not to require. Real push does exist on the Cuboh Direct API behind the Hub product: an OpenAPI 3.1 'webhooks:' block covering orders.new, orders.update, orders.accept, orders.adjust, orders.cancel, orders.complete, merchant.new, merchant.update, merchant.open, merchant.close, delivered over HTTPS to one subscriber URL per event family with a <300ms response-time standard - 'You must define only one Webhook URL for each of the Order(s), Merchant(s) and Menu(s) events'. Shortfalls: no paid, voided or refunded event in the enumerated set (Cuboh exposes refund only as an inbound POST /cuboh-connect-order/<order_id>/refund/), and the subscriber must be a QA-certified channel partner rather than an operator registering their own endpoint. https://developer.chownow.com/docs/openapi.json · retrieved 2026-08-06 · not refetchable · site policy · graded A when read

extensibility-webhook-reliability differentiator

Signing: 'Each webhook event includes an X-Cuboh-Signature request header... a hexadecimal HMAC signature of the HTTP request body, using a secret as a key and SHA256 as the hash function' (for GETs the signature covers external_integration_merchant_uuid). Retry: 'If Cuboh receives any of the following server errors: 500, 502, 503, 504, or 429 - the webhook event will be resent based on an exponential backoff algorithm. Ex. 1 second after the initial attempt, then 2 seconds, then 4 seconds until 5 total events were sent without a response', with a handling table (500/503 retry with backoff; 400 do not retry; 401 update token; 403 contact Cuboh). Shortfalls: no replayable event log or redelivery endpoint is documented anywhere in either spec, so after five failed attempts the event is lost; and the signing 'secret can be found in the QA documentation provided', which is not public. https://docs.cuboh.com/static/media/direct.cc50b46f10923bea774a.yml · retrieved 2026-08-06

extensibility-order-injection-api

Re-scored onto ChowNow's own spec. POST /v1/orders ('Place an order', scope orders:write) accepts a fully formed externally originated order with restaurant_id in the body and returns an Order carrying the restaurant_id for later lookups; POST /v1/quotes prices the cart first and the returned total is re-sent as validated_total 'so the price can't drift between quote and order'; the lifecycle afterwards is GET /v1/orders/{id}, GET /v1/orders/{id}/status and POST /v1/orders/{id}/cancel. The portal states the purpose plainly: 'The ChowNow Partner API lets your platform place food orders at thousands of restaurants on behalf of your users.' Cuboh's POST /api/v2/external-integration/order does the same for the Hub product. Shortfalls: ChowNow is an ordering layer, not a POS, so the destination is ChowNow's order flow (and, for Hub, the Cuboh tablet) rather than a POS ticket; neither spec documents KDS or printer firing for an injected order or states that injected orders land in the operator's reporting; and cancellation and refund are listed among the endpoints that 'are not yet implemented and return 501 Not Implemented'. https://developer.chownow.com/docs/openapi.json · retrieved 2026-08-06 · not refetchable · site policy · graded A when read

extensibility-menu-write-api differentiator

Neither of ChowNow's published APIs can write a menu. The ChowNow Partner API declares exactly ten operations and the only catalog access among them is read-only - GET /v1/restaurants/{id}/menu, described as 'a single, schedule-resolved menu ... already stripped of unavailable (86'd) items and base-priced' - with no POST, PUT or PATCH on any menu, item, modifier or price path; that enumeration is exhaustive for the API. On the Cuboh side, POST 'New Menu' and PATCH 'Update Menu' under /api/v2/external-integration/merchant/<uuid>/menus both carry the tag 'Menu Ingestion (coming soon)' and descriptions beginning '[coming soon, open a get GET to ingest menu]', so they are specified but not live. The only unqualified menu write anywhere is POST item/status-update, which toggles item availability (86ing) and writes no item, modifier or price. Menu authoring remains a Menu Editor / POS-sync operation. https://developer.chownow.com/docs/openapi.json · retrieved 2026-08-06 · not refetchable · site policy · graded A when read

extensibility-data-symmetry differentiator

Complete path inventory of both specs. Direct: POST/GET /api/v2/external-integration/order, GET order/{id}, POST order/{id}/cancel, POST order-group/{id}/cancel, POST merchant/<uuid>/status. Connect: POST cancel/refund/upcharge/complete/accept on /cuboh-connect-order/<order_id>/, GET /cuboh-connect-order/<order_id>/details/, POST+GET+PATCH menus, GET menus/<external_menu_id>, POST+GET validate/<id>, POST item/status-update, POST merchant status, GET merchant orders. Menus are readable now while both write verbs (POST New Menu, PATCH Update Menu) are tagged 'Menu Ingestion (coming soon)', so a core readable object is not writable. Customers, employees and inventory have no path and no schema in either document. Read/write symmetry across core objects is positively absent from the schema, not merely unfound. https://docs.cuboh.com/static/media/connect.7bc86b76a95006107da4.yml · retrieved 2026-08-06

extensibility-published-rate-limits

All three elements the claim asks for are published. Numeric quota: 'Every client organization is limited to 600 requests per 60 seconds. This limit is the same for sandbox and production credentials - there is no per-tier rate differentiation today.' Throttling behaviour: the OpenAPI document defines a shared RateLimited response, referenced from every one of the ten operations, described as 'Per-partner rate limit exceeded' with the body '{ "code": "RATE_LIMITED", "title": "Rate limit exceeded." }' when enforced at the Cloudflare API Shield edge, and the security scheme states the gateway 'derives the partner identity from the JWT org_id claim and uses it for ... partner-scoped rate limits'. Headers: Retry-After ('Seconds to wait before retrying'), X-RateLimit-Limit ('Request budget for the surfaced window') and X-RateLimit-Window ('Length in seconds of the surfaced budget window'), all typed in the response definition. Caveat, not a shortfall against this claim: the API is versioned 0.1.0-draft, and the edge-enforced 429 body omits request_id, so callers correlate via the cf-ray header instead. https://developer.chownow.com/docs/getting-started · retrieved 2026-08-06 · not refetchable · site policy · graded A when read

extensibility-doordash-preferred differentiator

Verified against DoorDash's own newsroom post announcing the 2026 roster. Cohort is Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper. Neither ChowNow nor Cuboh appears. 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, Uber Eats and Grubhub integrations are ChowNow-owned (via the 2024 Cuboh acquisition) and included in the base subscription — no separate middleware contract required. https://get.chownow.com/integrations/all/ · retrieved 2026-08-01

extensibility-middleware-compatibility

Inverted: ChowNow is not a POS and therefore not an endpoint for Deliverect/Chowly/Otter/Checkmate — after acquiring Cuboh it competes with them.

extensibility-accounting-connectors

Confirmed by full enumeration of the integrations directory: 24 POS systems, 4 delivery apps (DoorDash, Grubhub, Skip, Uber Eats), 5 discovery channels (Apple Maps, Google, Snap, Tripadvisor, Yelp), 2 printer vendors. Zero accounting, zero payroll, zero reservations, zero third-party loyalty. Same enumeration independently supports labor-payroll-export-formats and extensibility-payroll-export. https://get.chownow.com/integrations/all/ · retrieved 2026-08-01 adversarially verified

extensibility-payroll-export

No payroll integrations listed; ChowNow holds no labor hours to export. https://get.chownow.com/integrations/all/ · retrieved 2026-08-01

extensibility-bi-data-warehouse differentiator

Manual dashboard CSV export only. https://get.chownow.com/restaurant-support/?s=export · retrieved 2026-08-01

extensibility-app-marketplace

A public integrations directory lists named POS, delivery and discovery integrations, and a partners page lists named service partners with discounts. Self-install by the operator is not documented — POS connections are set up by an Onboarding Specialist. https://get.chownow.com/integrations/all/ · retrieved 2026-08-01

extensibility-custom-fields-scripting

Checked both Cuboh OpenAPI specs in full (no custom-field, metadata, attribute or script object appears in any schema), the ChowNow Dashboard help articles under get.chownow.com/support-category/ (Using the ChowNow Dashboard, Onboarding, How to Use Tablet), the Settings surfaces those articles describe (Settings > Users, Location Info, Global Printer Settings), and the collection list at support.cuboh.com/en/ (Product Tutorials, Cuboh Web Dashboard, Menu Management, POS Integrations, POS Errors, Delivery App Integrations, Menu Mapping, Storefront, Common Support Issues, New Dashboard). Nothing addresses operator-defined custom fields or vendor-hosted custom logic either affirmatively or by exclusion. The partner API specs are not the operator's configuration surface, so their silence does not enumerate what the Dashboard can do. Unresolved.

extensibility-headless-embedded

Checked the Cuboh Direct spec (POST /api/v2/external-integration/order lets a third-party ordering platform submit orders, including multi-brand group orders, but the spec describes them surfacing on the Cuboh tablet, not a third-party UI driving a transaction engine - there are no cart, tender, tax-calculation or payment-authorization endpoints in either spec), the Connect spec, and the ChowNow product pages for QR Code Ordering, Website Builder and Branded Mobile Apps at get.chownow.com/products/, which are all first-party front ends. ChowNow publishes no statement that a third-party kiosk, web-ordering or drive-thru UI may drive its ordering engine, and no statement that it may not. Unresolved: the partner API is an order-submission channel, which is a weaker thing than the claim asks about, and no doc marks the boundary.

extensibility-api-versioning-deprecation

Scored against ChowNow's own Partner API, not Cuboh's. The OpenAPI 3.1 document (info.version '0.1.0-draft', server https://openapi.chownow.com/v1, ten operations) contains no changelog, no x-changelog, no sunset or deprecation policy, no notice period for breaking changes, and not one deprecated flag on any path, operation or property - the strings 'changelog', 'deprecat', 'sunset' and 'breaking' occur zero times in the 55KB spec. Versioning is stated only as a URL convention: 'Versioning - Endpoints are versioned in the URL path (e.g. /v1/...)'. The only stability language anywhere is on the RFC 9457 error schema, and it runs the other way - 'title/detail are human-facing and may be reworded without notice'. The developer portal's own sidebar enumerates the complete published documentation set - Introduction, Getting Access, Authentication, Place an order, API Reference - with no changelog or release-notes entry, and /docs/changelog returns 404. Getting Started instead labels endpoints 'not yet implemented' returning 501 and says per-application scope selection is 'planned', which is a roadmap note, not a deprecation policy. https://developer.chownow.com/docs/openapi.json · retrieved 2026-08-06 · not refetchable · site policy · graded A when read adversarially verified

extensibility-data-portability-exit differentiator

While active, orders, items/modifiers, analytics, disbursements and the diner contact database are self-serve exportable to CSV. No documented complete historical export at contract end and no machine-readable format specification. https://get.chownow.com/restaurant-support/?s=export · retrieved 2026-08-01

reliability-offline-order-entry

Cloud-only; no on-terminal order entry exists at all.

reliability-offline-card-auth differentiator

No offline payment path.

reliability-offline-decline-liability differentiator

No store-and-forward to document.

reliability-lan-degraded-multi-terminal differentiator

No multi-terminal LAN architecture.

reliability-local-transaction-engine differentiator

No on-premise transaction engine documented; the Hub tablet is a cloud client.

reliability-offline-kds-printing

Tickets originate from the cloud; no offline print path documented.

reliability-printer-fallback

The Hub/Cuboh tablet's printer configuration is exhaustively described by two articles. Global Printer Settings ('These settings affect all printers connected directly to the Cuboh tablet') lists every toggle: Ticket Font Size (Medium/Large/Extra Large), Show Menu Item Prices, Show Menu Modifier Prices, Show Discounts, Print Cancelled Orders, Print Delivery Fee. The per-printer screen (Printer Connections) lets you toggle a discovered Star Micronics TSP100/SP700 or Epson TM printer on, Save, then 'tap Configure to configure which merchants and also the number of copies to use for the connected printer'. There is no backup or failover printer assignment, no reroute-on-unreachable behaviour and no staff alert setting in either screen; a support search for printer returns no failover article. The entire configurable printer surface is enumerated and automatic failover is not in it. https://get.chownow.com/restaurant-support/global-printer-settings/ · retrieved 2026-08-06

reliability-sync-conflict-handling

Checked both Cuboh OpenAPI specs (no idempotency key, ETag, If-Match, version or revision field on any request or response; the only conflict semantics documented anywhere is a 409 the PARTNER returns when an external_location_id is already assigned to another merchant during merchant onboarding), the ChowNow help centre categories at get.chownow.com/support-category/ covering How to Use Tablet and Using the ChowNow Dashboard, and support.cuboh.com/en/ (collections: Product Tutorials, Cuboh Web Dashboard, Menu Management, POS Integrations, POS Errors, Delivery App Integrations, Menu Mapping, Storefront, Common Support Issues, New Dashboard). No document states last-write-wins, merge, or an operator prompt for edits made on two devices during a partition. Unresolved - the vendor is cloud-only with no documented offline edit mode, but nothing published defines the behaviour either way.

reliability-offline-feature-matrix

No offline feature matrix exists; a support search for offline returns only 'POS Offline Error'. https://get.chownow.com/restaurant-support/?s=tablet · retrieved 2026-08-01

reliability-public-status-page

Documented by enumeration of the vendor's own published URL index rather than by absence of mention: get.chownow.com/sitemap_index.xml lists six sitemaps (page 166, post 189, restaurant_support 278, diner_support 38, category 37, support_category 26) totalling 734 URLs, and none matches status, uptime, incident or trust. Independently, status.chownow.com and trust.chownow.com both return DNS NXDOMAIN (8.8.8.8), and chownow.statuspage.io is not a provisioned tenant - it redirects to atlassian.com's Statuspage marketing page. No status link appears in the site footer. https://get.chownow.com/sitemap_index.xml · retrieved 2026-08-09 adversarially verified

reliability-contractual-uptime-sla differentiator

The restaurant-side Restaurant Agreement (General Terms, public, effective 2026-04-08) is the operative contract and states the opposite of an SLA. Section 7.3 Disclaimer: 'CHOWNOW CANNOT GUARANTEE THAT THE PLATFORM, ORDER BETTER NETWORK, OR ANY OF THE SERVICES WILL BE AVAILABLE AT ALL TIMES, OR THAT EVERY ERROR IN THE PLATFORM OR PROBLEM RAISED BY RESTAURANT WILL BE RESOLVED', the services are 'provided AS IS and AS AVAILABLE', and ChowNow 'hereby disclaims any and all express, implied, or statutory warranties, including, without limitation, any warranties of... AVAILABILITY, ERROR-FREE OR UNINTERRUPTED OPERATION'. No uptime percentage and no service credit appears in the Agreement; the only remedy provisions are Section 8's liability caps (12 months of fees, or $100 for Core-only subscribers). Section 5.4 lists the surviving sections and no service-level exhibit is among the incorporated terms. https://get.chownow.com/legal/registermyresto/ · retrieved 2026-08-06

reliability-incident-postmortems

The Cuboh status page (Atlassian Statuspage, components include Cuboh Dashboard, Cuboh Cloud Infrastructure, Cuboh Reporting Service and 'ChowNow Orders') publishes an incident history whose RSS feed returns 19 entries with written cause statements. Examples: 'On January 22nd a database value was unintentionally modified during a release, causing a service outage that lasted approximately 8 minutes. Everything was quickly rolled back' (3 Feb 2025); 'There was a package upgrade in our latest release which has caused a system outage. This outage lasted for 32 min (From 10:56AM PST to 11:28AM PST)' (22 Oct 2024); 'DoorDash excess of menu serve requests overwhelmed our systems and brought down our servers from ~8:30PM to 8:45PM PST' (20 Nov 2024). Shortfalls: these are one-to-three-sentence cause-and-duration notes, not post-incident reports with remediation or prevention actions; the most recent entry is Feb 2025; status.chownow.com does not resolve (DNS NXDOMAIN), so ChowNow's own ordering platform, Dashboard and branded apps have no equivalent surface. https://status.cuboh.com/history.rss · retrieved 2026-08-06

reliability-247-live-support

'24/7 Support (Phone & Chat)' is checked on all three tiers including Launch; support line 888-707-2469 accepts call or text. Reviewers note peak-time wait times. https://get.chownow.com/pricing/ · retrieved 2026-08-01

reliability-onsite-install differentiator

Checked get.chownow.com/support-category/onboarding/ (article list includes Document Needed List, How to integrate with Fresh KDS, How to find your DoorDash Store ID, Introduction to the ChowNow Dashboard, plus a government-accounts set; the category is paginated and not self-declaring as complete), the How to Use Tablet articles (Downloading the Cuboh App, connecting a ChowNow printer to the tablet, printer setup), a support search for 'on-site' and 'install' which returns only self-service integration guides, the pricing page's '$119 - $499 setup fee', and Section 1.42 of the Restaurant Agreement ('Set up Fee: $499'). Every documented step is remote or operator-performed and the Agreement contains no on-site services clause except Section 2.1(c) Photography Services, which does put ChowNow staff or contractors in the restaurant but for photography, not installation. Unresolved: no page states whether in-person go-live support is offered, and the onboarding article list is not an exhaustive enumeration.

reliability-menu-build-service differentiator

A $119-$499 setup fee and Onboarding Specialists who coordinate POS menu retrieval/mapping are documented; menu mapping articles also describe operator-performed mapping for some POS systems, so responsibility is split. https://get.chownow.com/restaurant-support/?s=modifier · retrieved 2026-08-01

reliability-hardware-replacement-sla

ChowNow's public Refund Policy documents a hardware return and replacement program: call 1-888-707-CHOW for a Return Material Authorization; a product is DOA 'if it shows symptoms of a hardware failure, preventing basic operability, when you first use it after opening the box', reportable 'within 30 calendar days of the invoice date', after which Technical Support offers Replacement ('ChowNow, at its expense, will ship another of the same product') or Service (repair, after which replacement may not be requested). Returns must reach the warehouse within 14 calendar days of RMA issuance, and a $150 handling fee applies if a returned product is found not to be DOA. Shortfalls against the claim: no turnaround time is stated for either replacement or repair; there is no advance-exchange (the replacement is arranged after the DOA determination); the program is scoped to out-of-box failures inside 30 days, with later failures referred to 'ChowNow's standard product warranty', which is not published - the incorporated Tablet and Wireless Printer Terms at get.chownow.com/legal/registermyresto/tablet-and-wireless-printer-terms/ returns 404. https://get.chownow.com/legal/refund/ · retrieved 2026-08-06

reliability-backup-restore

Checked get.chownow.com/legal/registermyresto/ in full (Section 7.3 disclaims availability and uninterrupted operation; Sections 5.3 and 6 cover termination and data rights; no recovery, backup, RPO or RTO obligation appears anywhere), get.chownow.com/legal/ which enumerates the six published policy documents (Refund, Terms, Privacy, CA Privacy Notice, Do Not Sell, Google Disclosure) and contains no security or resilience document, support searches for 'backup' and 'restore' on get.chownow.com/restaurant-support/ which return zero relevant articles, and trust.chownow.com / security.chownow.com which do not resolve. The self-serve CSV exports already recorded on this record (orders, items and modifiers, analytics, disbursements, Customer Spending) are a data-export facility, not an operator-triggered backup with a restore path. Unresolved: no RPO/RTO figure is published and no restore mechanism is described either way.

reliability-pci-dss-4-attestation

ChowNow publishes no attestation of any kind. Its own sitemap index enumerates the merchant site exhaustively - page-sitemap.xml lists all 166 pages (including a 21-page /legal/ subtree: registermyresto, eight registermyresto-outdated term sets, referral-program-agreement, referral-terms, refund, survey-sweepstakes-rules, membership-products-terms-of-service, restaurant-rewards, cookie-notice, california-privacy-rights-act, california-consumer-privacy-act, commissions, rewards-beta-survey, terms-of-service, privacy-policy) and restaurant_support-sitemap.xml lists all 278 support articles; no page in either is a security, trust, compliance or attestation document, and /security/ and /trust/ both 404 while trust.chownow.com and security.chownow.com do not resolve. The developer portal's docs nav likewise enumerates five documents with no security or compliance page. What ChowNow does publish is two generic statements: Restaurant Agreement s4.7, 'To the extent that ChowNow stores, processes, or transmits cardholder data, ChowNow complies with the most current version of the Payment Card Industry Data Security Standard (PCI-DSS)', and a support FAQ, 'ChowNow is a PCI compliant company with proper certification to acquire, maintain, and protect credit card information.' Neither names a DSS version, a QSA, an assessment date, an AoC, an SAQ or a P2PE listing - the strings 'Attestation', 'P2PE' and 'SAQ' occur nowhere in the agreement. Whether an AoC is furnished to merchants privately on request is a separate question this claim does not ask. https://get.chownow.com/legal/registermyresto/ · retrieved 2026-08-06 adversarially verified

reliability-mfa-role-based-access

Role-based permissions exist but are coarse and MFA is absent. The user-creation flow is the whole of the access-control surface: 'Navigate to dashboard.chownow.com, Click Settings on the left side, then Users, Click the green Create button, Fill in the contact info for the new admin user, and then choose if they should be a Company admin (can change settings for all locations), or a Regional admin (they are only associated with a specific location).' Two roles, both admin, with scope as the only distinction - no server, manager or read-only role and no per-permission grants. No MFA step appears in that flow, the related article 'How to reset your Password' describes password reset only, and a help-centre search for 'two-factor' on get.chownow.com/restaurant-support/ returns zero articles. Section 6.3 of the Restaurant Agreement commits only to 'commercially reasonable administrative, technical, and physical safeguards' and names no authentication control. https://get.chownow.com/restaurant-support/adding-users-dashboard/ · retrieved 2026-08-06

reliability-self-serve-training

A free, public, login-free restaurant support article library covers getting started, tablet use, menu management, POS integration, delivery, marketing and billing. No video LMS or terminal training mode documented. https://get.chownow.com/restaurant-support/ · retrieved 2026-08-01

reliability-failover-terminal-role differentiator

No terminal/master architecture.

reliability-cellular-backup

Checked the Hub tablet and printer articles at get.chownow.com/restaurant-support/ - 'How to manage your Printer Settings and Connections from the Cuboh Tablet' (Star Micronics TSP100/SP700 over LAN, Wi-Fi and Bluetooth; Epson TM discovered by 'scanning your local network'), 'How to set up a TP-Link with your Printer', 'Downloading the Cuboh App', and 'I am unable to log into my Cuboh tablet' - plus a support search for 'cellular' which returns zero articles, and the pricing page, which prices a printer ($250-$420) and no data plan or LTE accessory. Every documented connectivity path is Wi-Fi, LAN or Bluetooth and the tablets named on this record (Lenovo M8, Vankyo MatrixPad S20) are Wi-Fi-class Android devices. Unresolved: no page presents itself as a complete list of supported connectivity, and ChowNow neither offers nor rules out LTE failover in print.

commercial-month-to-month-contract differentiator

Help centre cancellation policy: ChowNow offers month-to-month as well as prepaid (annual or two-year) plans; for month-to-month, 'ChowNow has a 30 day cancellation policy, meaning you will be responsible for paying for the last 30 days of your service', and service can be switched off immediately within that window. Prepaid plans can be cancelled any time but carry no prorated refund. Friction to note: cancelling requires a form plus a consultation call with a Restaurant Success Manager, the Restaurant Agreement auto-renews 'for the same plan term agreed upon', and leased hardware must be returned within 30 days. Published monthly pricing ($249/$349/$449) sits above the annual prepaid rate ($229/$319/$409). https://get.chownow.com/restaurant-support/cancellation-policy/ · retrieved 2026-08-06

commercial-no-early-termination-fee differentiator

The public Restaurant Agreement contains an early-termination charge rather than a disclaimer of one. Section 5.3 Effect of Termination: 'For Restaurants who are on annual plans but have monthly billing terms, any unpaid balance of the annual plan payment at the time of termination shall be immediately due to ChowNow', and ChowNow 'shall charge Restaurant's credit card, bank account, or other approved facility for any outstanding Fees and Taxes'. Section 4.2 Refunds; Cancellation Fee: 'Restaurant may be subject to a cancellation fee (Cancellation Fee) with respect to certain Services as may be specified in the applicable Service Terms' - and those Service Terms are not retrievable (the Premier, Pro, Core, Additional and Tablet and Wireless Printer Terms pages under get.chownow.com/legal/registermyresto/ all return 404). The Refund Policy's 'you may cancel your ChowNow service at any time. You will be billed for the remaining amount in your monthly cycle' describes monthly plans only and is expressly incorporated subject to Section 4.2. Section 5.2 additionally requires Elevate/Grow/Launch/Premier/Pro/Hub subscribers to file a cancellation request or take a consultation call, after which termination takes a further 30 days. https://get.chownow.com/legal/registermyresto/ · retrieved 2026-08-06

commercial-autorenew-terms-published

The public help center documents a 30-day cancellation policy and the cancellation procedure, and billing timing (charged within 1-3 business days of signup). The auto-renewal term itself is not stated, and the public ToS is the diner agreement, not the restaurant agreement. https://get.chownow.com/support-category/billing-my-account/ · retrieved 2026-08-01

commercial-processing-not-bundled differentiator

Support article 'Can I use my own payment processor?' — ChowNow requires all clients to use its processor. Payments are hard-bundled at 2.95% + $0.29. https://get.chownow.com/support-category/order-and-payments-processing/ · retrieved 2026-08-01

commercial-interchange-plus-published differentiator

Only a blended flat rate is published (2.95% + $0.29); no interchange-plus option appears anywhere. https://get.chownow.com/pricing/ · retrieved 2026-08-01

commercial-rate-increase-clause differentiator

The restaurant-side Restaurant Agreement (General Terms, effective 2026-04-08) is public after all. S4.1: 'ChowNow may modify any of the foregoing fees at any time on written notice to Restaurant (including via Restaurant's individual account in its admin.chownow.com dashboard), and any such modification shall go into effect thirty (30) days after such notice.' 'Fees' as defined includes Subscription Fees, Marketing Fee, Add-On Fees and Credit Card Processing Charges (defined at $0.29 + 2.95% US, $0.30 + 2.9% via Third Party POS Integration), so the processing rate itself is unilaterally modifiable. No cap, no index, no carve-out limiting increases to pass-through interchange/network changes, and no clause granting the Restaurant a termination right triggered by an increase. S5.1 auto-renews for the same plan term; S5.2 gives ChowNow termination for convenience on 30 days' notice 'without penalty or liability' but gives that right to the Restaurant only for Core-only subscribers - Elevate/Grow/Launch/Premier/Pro/Hub must file a cancellation request or take a cancellation consultation call, after which termination takes a further 30 days, and S4.2 preserves a possible Cancellation Fee. Positive evidence of absence, not merely silence. https://get.chownow.com/legal/registermyresto/ · retrieved 2026-08-02

commercial-pricing-published

Three tiers with specific monthly and annual dollar figures, plus setup fee range, processing rate, printer cost, Apple developer fee, and Flex Delivery per-order fee — all on a public page with no sales gate. https://get.chownow.com/pricing/ · retrieved 2026-08-01

commercial-module-unbundling differentiator

The three suites (Ordering, Marketing, Operations) are bundled into every tier and cannot be bought à la carte; tiering is by marketing contact/SMS volume. Flex Delivery ($3.99/order) and catering (5%) are usage-priced and optional. https://get.chownow.com/pricing/ · retrieved 2026-08-01

commercial-hardware-purchase-outright

Printer published at $250-$420. Tablet acquisition terms (purchase, rental, or included) are not published, and no mandatory hardware lease is disclosed either way. https://get.chownow.com/pricing/ · retrieved 2026-08-01

commercial-hardware-not-locked differentiator

Third-party ESC/POS printers from two manufacturers are explicitly supported — Star Micronics TSP100/SP700 and Epson TM (all models) over LAN, Wi-Fi and Bluetooth — and the Hub app runs on standard Android tablets (Lenovo M8, Vankyo MatrixPad S20). https://get.chownow.com/restaurant-support/?s=tablet · retrieved 2026-08-01

commercial-implementation-fee-published

Published as a range — '$119 - $499 setup fee' — not a specific amount, with no explanation of what determines the position in the range. https://get.chownow.com/pricing/ · retrieved 2026-08-01

commercial-data-export-self-serve

Order reports, item & modifier reports, sales analytics, disbursement reports and the Customer Spending diner database are all exportable from the ChowNow Dashboard without contacting support. https://get.chownow.com/restaurant-support/?s=export · retrieved 2026-08-01

commercial-export-customer-and-loyalty differentiator

Diner contact and spending data is exportable and ChowNow markets 'your diners, your data.' Loyalty sticker balances and gift-card liability exports are not documented (and no gift card product was found). https://get.chownow.com/products/direct-online-ordering/ · retrieved 2026-08-01

commercial-post-termination-export-window differentiator

Section 5.3 of the public Restaurant Agreement: on termination 'all rights and licenses granted hereunder will immediately cease, and Restaurant will immediately cease all access to, and use of, the Platform and must return any leased hardware as set forth in the Tablet and Wireless Printer Terms'. No grace period, export window or data-delivery obligation is attached. Section 6.2 grants the Restaurant a licence to use Third-Party Order Data only 'during the Term' (while Order Data is jointly owned and usable by either party 'during the Term and indefinitely thereafter', which is a use right, not an access or export right once the Dashboard is closed). Section 5.4 lists the surviving provisions and none of them preserves access. The only post-termination obligation running to the Restaurant is payment of amounts due under Section 4.5 and removal of the ordering widget from its website within 30 days. Immediate cutoff is the published contractual position. https://get.chownow.com/legal/registermyresto/ · retrieved 2026-08-06

commercial-data-ownership-clause differentiator

Marketing states operators get 'full access to diner ordering data and contact information' and can export at will, but no published contract clause vests ownership in the merchant or constrains ChowNow's use. The privacy policy affirmatively reserves broad rights: aggregate analysis, sharing authenticated users' email and phone with mParticle, and sharing with 'third-party advertisers and remarketers' — while ChowNow simultaneously runs a competing consumer Marketplace on that same diner base. https://get.chownow.com/legal/privacy-policy/ · retrieved 2026-08-01

commercial-source-available-selfhost

Proprietary SaaS; no source availability or self-hosting.

commercial-pci-p2pe-tokenization

Re-verified 2026-08-06. The strings 'tokeniz', 'P2PE' and 'SAQ' appear nowhere in the public Restaurant Agreement, whose entire PCI content is the generic Section 4.7, and ChowNow sells no card-present device (its hardware is a tablet and a wireless printer), so a validated P2PE listing would have no product to cover. But the enumeration the note relies on is not one: get.chownow.com/legal/ renders no body and its six links are the footer present on every page, and trust.chownow.com and security.chownow.com do not resolve. Whether ChowNow documents tokenization and a merchant SAQ scope in onboarding or merchant-facing material is undetermined. adversarially verified

commercial-pci-dss-4-controls

Neither future-dated control is documented anywhere ChowNow publishes, and the published surface is now enumerable rather than merely unsearched: page-sitemap.xml (166 pages), restaurant_support-sitemap.xml (278 support articles), the developer portal's five-document docs nav, and the Restaurant Agreement. MFA - the agreement's security clause is s6.3, 'commercially reasonable administrative, technical, and physical safeguards designed to prevent a Security Incident', and 'MFA', 'multi-factor' and 'two-factor' occur zero times in its 69KB; no support article in the 278 covers MFA or 2FA; the documented dashboard identity flows are a password reset by emailed verification code and a Settings > Users > Create form whose fields are contact info plus Company-admin or Regional-admin scope, with no second-factor step described; the developer portal documents OAuth2 client-credentials machine-to-machine auth for partners, which is not user MFA and does not cover the merchant dashboard. Script integrity - no ChowNow page documents Req 6.4.3 authorised-script management or 11.6.1 payment-page change detection; the nearest published statement is the FAQ 'ChowNow ordering is SSL secure - which means our widgets have the proper certifcation [sic]', which is a TLS assertion about an embedded ordering widget, not script-integrity monitoring. The dashboard itself is behind a login and cannot be inspected, so this records the documentation, not the implementation. https://get.chownow.com/legal/registermyresto/ · retrieved 2026-08-06 adversarially verified

commercial-soc2-attestation

ChowNow makes no SOC 2 or ISO 27001 statement anywhere it publishes. I re-read the whole Restaurant Agreement (69KB): 'ISO 27' occurs zero times and 'SOC' only inside other words (associated, social, announce); the security undertaking is s6.3, which binds each party to 'commercially reasonable administrative, technical, and physical safeguards designed to prevent a Security Incident', with the 72-hour breach-notification duty running from Restaurant to ChowNow. Beyond the contract, the published surface is enumerable and empty on this point: page-sitemap.xml lists all 166 pages of get.chownow.com and restaurant_support-sitemap.xml all 278 support articles, and none is a trust centre, security page or attestation summary; /security/ and /trust/ 404, trust.chownow.com and security.chownow.com do not resolve, www.chownow.com publishes only brand and location sitemaps, and the developer portal's docs nav lists five documents with no security section. The claim requires the vendor to state it holds the attestation and will provide it under NDA - no such statement is published. Whether an unpublished report exists and is furnished under NDA to enterprise prospects is not something this claim asks or that any crawl could establish. https://get.chownow.com/legal/registermyresto/ · retrieved 2026-08-06 adversarially verified

commercial-privacy-dsar-tooling

ChowNow operates a vendor-side OneTrust Data Privacy Rights Request webform plus a CPRA notice and a Do Not Sell request flow, and diners can edit/delete contact data in account settings. No operator-facing in-app DSAR tooling and no publicly available DPA for restaurants. https://get.chownow.com/legal/privacy-policy/ · retrieved 2026-08-01

commercial-wcag-kiosk-accessibility differentiator

Re-verified 2026-08-06. get.chownow.com/accessibility/, get.chownow.com/legal/accessibility/, get.chownow.com/trust/ and www.chownow.com/accessibility all 404, and the Restaurant Agreement contains no accessibility representation ('WCAG' does not occur; 'accessib' occurs twice, both in links to third-party policies). It is also true that ChowNow's product line contains no self-order kiosk. But the enumeration relied on does not exist - the cited legal page is an empty shell whose six links are the site footer - and no conformance-report surface was positively excluded, so whether ChowNow publishes an ACR for its consumer web-ordering surfaces is unknown. adversarially verified

commercial-dual-pricing-compliant differentiator

The operator's entire customer-fee surface is one control: 'You can add a service fee either by amount or percentage of the order, through the ChowNow Dashboard under the Location Info section.' There is no card-type dimension to it - no debit or prepaid exclusion, no BIN-based logic, no separate cash and card price, and no receipt or menu-board disclosure handling. The eleven-article Order and Payments Processing help category contains no surcharging, cash-discount or dual-pricing article, and a support search for 'surcharge' returns zero results. Two structural facts close it: 'Do you accept cash? We do not accept cash so that we can ensure your restaurant gets paid' - there is no cash tender for a cash discount to be priced against - and Section 7.2(i) of the Restaurant Agreement requires that 'the prices it charges Customers through the Platform or Order Better Network shall be the same prices (or lower)' as offline prices, with ChowNow automatically deducting the difference if the restaurant prices higher, which forecloses a card-price/cash-price split. https://get.chownow.com/restaurant-support/charging-customers-service-fees/ · retrieved 2026-08-06