Chowly

Supports modifier groups nested at least three levels deep, each level with independent min/max selection counts and a forced-selection (required) flag.

menu-pricing-nested-modifiers

Three chained modifier-group levels do publish, but only on two of Chowly's integration paths. Toast: Nested Modifier Settings with Chowly, rule (1): "Chowly only supports two layers of nested modifier sets", where the layers counted are those BELOW the item-level group - its own example runs Taco Dinner > Meat (beef) > ground beef / steak > rare / well done, and only the fourth link in that chain ("marinated" or "unseasoned") is "not supported by Chowly". Rule (2): "Unlimited number of modifier groups and nested modifier groups supported" within the permitted levels. Each level carries the independent controls the claim asks for: Toast: Modifier Settings with Chowly says Chowly reads Required / Optional / Optional-Force Show ("If a modifier group is set as 'Required,' Chowly will not let your customers place an order until the min/max number of require modifiers is met") and "Chowly does read" the "Min # Selections" and "Max # Selections" columns. SHORTFALLS: nesting works only "for restaurants using a Toast POS or Chowly's POS API" (FAQ - Can I use nested modifiers?), and every other POS requires the documented "flattening" workaround; a fourth group level is silently dropped - "Menu items with more than two layers of nested modifiers sets will be skipped in the menu publish, and an alert will be sent to the #nested-modifier-alerts Slack channel"; default (pre-selected) nested modifiers are unsupported; and only DoorDash, Grubhub, Uber Eats and Chowly Online Ordering accept nesting downstream. Retrieved from the server-rendered Knowledge view at https://chowly.help/articles/en_US/Knowledge/Toast-Nested-Modifier-Settings-with-Chowly; the /s/article/ URL is the site's inert SPA shell. https://chowly.help/s/article/Toast-Nested-Modifier-Settings-with-Chowly · retrieved 2026-08-08 adversarially verified

A single modifier can carry different prices depending on the parent item and the selected size, configured as a matrix rather than by duplicating the modifier.

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

Quote: "Pricing Strategies Limitations: Chowly can integrate "Base Price," "Size Price," "Upcharge Price," as well as Time, Location, and Menu Specific Price pricing strategies. However, this "Open Price" strategy is incompatible This can lead to empty or $0 priced items or groups on your platforms." Chowly states it consumes Toast's Size Price strategy (the Toast construct that prices by the parent item's size) rather than requiring duplicated modifiers, and the March 2022 changelog shows Chowly reading Revel size pricing ('We added the size pricing onto Revel items when the price is zero and modifiers are present'). Shortfall: the sentence sits under Item Settings and never says whether modifier-level Size Price (price-per-parent-size on a modifier group) propagates; it is scoped to the Toast sync path; on Square the overview says 'Pricing Overrides are not currently a supported feature, however you can get around this by ensuring Price (Required) matches the price override'; and Chowly's own Dejeuner modifier record holds a single price (Chowly Printer Menu Management Overview: 'you can change the modifier's name and price'). No matrix configuration exists on any Chowly-owned surface. https://chowly.help/s/article/Toast-with-Chowly-Overview · retrieved 2026-09-03 adversarially verified

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

menu-pricing-fractional-placement

CLAIM: fractional/sectioned modifier placement (at minimum halves) with independent pricing per section. VERDICT: partial (merge downgrade from yes: Koala only RENDERS section options and prices that are configured in the connected menu provider, and per-section pricing is evidenced by one release-note bug line) for Chowly Online Ordering (Koala), the vendor's own first-party ordering product. EVIDENCE: the current Koala Web Ordering feature set (chowly.help kA01K000000oZjiSAE, modified 2023-11-07) lists under Koala Customizations > Templates & Styling a 'Pizza Topping Customization template'. The release notes define it: 'Pizza Menu Template - We now have the capacity to support pizza topping option groups, creating a cleaner and more usable experience for brands that allow a guest to customize their pizza toppings based on weight of topping and quadrant of pizza to which they want the topping applied.' (https://chowly.help/s/article/Koala-Web-Release-November-13-2019). The section axis is named and enumerated: 'Hide option groups if their names are "Amount" or "Left/Right/Whole" so as to not duplicate pizza topping groups'; 'Pizza Template to account for pizza toppings that only have one nested option group (amount OR position)'; 'Bug where app would crash if pizza topping amountGroup or positionGroup was missing' (https://chowly.help/s/article/Koala-Web-Release-May-20-2020). Independent pricing per section is explicit: 'Bug where pizza topping amount and position calories and costs were not being surfaced to the user' - i.e. each amount/position option carries its own cost, which Koala prices and displays. CAVEAT: the section prices originate in the connected menu provider (Olo/Square); Koala renders, prices and submits them. Retrieved 2026-09-18. https://chowly.help/s/article/Koala-Web-Ordering-Feature-Set · retrieved 2026-09-18 adversarially verified

The half-and-half pricing rule is operator-configurable among at least two of: charge the higher-priced half, average the halves, or charge each topping at a fraction of full price. differentiator

menu-pricing-half-and-half-rule

2026-08-08 re-sweep. Rebuilt the chowly.help corpus independently rather than trusting the sitemap: POST /s/sfsites/aura with RecordServiceComponentController.getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c, seeded from /s/sitemap-topicarticle-1.xml (114 slugs) and crawled to fixpoint over every chowly.help/s/article/ href inside the retrieved bodies - 204 slugs reached, 195 with live bodies, 9 dead (getArticleVersionId returns null and the URL 404s, including Smart-Pricing-Overview and Delivery-Search, both linked from live articles). Searched every retrieved body for half, split, section, portion and topping rule: the only "half" hits are unrelated (half-hour increments in the Aloha and Toast hours articles, CA AB1276 utensil compliance, Square tax rounding). Chowly's own price levers are now fully mapped and none of them is a topping-pricing rule: the Restaurant Control Center upcharge field, described in FAQ - How do I set upcharges to my menu items as a percentage applied "on all of your third party platforms at the same time or on a platform-by-platform basis", and Smart Pricing, which the RCC reporting articles (Sales Reporting Page on the Restaurant Control Center) name as one of the seven analytics pages and which the upcharge FAQ says "will impact the ways you can set your upcharges in the RCC" - but its own help article, chowly.help/s/article/Smart-Pricing-Overview, is a dead link (getArticleVersionId returns null, URL 404s) and chowly.com/smart-pricing/ also 404s, so Smart Pricing's rule surface is undocumented. The only pizza-specific artefact anywhere is the "Pizza Topping Customization template" named in Koala: Web Ordering Feature Set, for which no configuration article exists. No operator-selectable higher-half / average / fraction-of-full rule is documented or ruled out. Unresolved. || 328th: NEW SURFACE: Chowly Online Ordering (Koala) does render a Left/Right/Whole position group per pizza topping with per-option costs (https://chowly.help/s/article/Koala-Web-Release-May-20-2020), but nothing in Chowly's own corpora exposes the PRICING RULE for a half-and-half build as an operator choice: 'half and half' 0/583 chowly.help articles, 0/958 chowly.app RCC sources, 0/910 cms.koala.io sources; 'average' as a pricing rule 0. The rule is resolved upstream by the menu provider/POS, so Chowly neither configures nor documents it. Held unknown rather than no. Retrieved 2026-09-18. || 333rd: 333rd NEW (notes only): the Koala/COO guest client (closed Next.js bundle, 875 first-party sources on <slug>.onlineorder.site) has a pizza layout (theme keys pizza_option_group_layout, pizza_position_option_group_layout, pizza_weight_option_group_layout in @koala/sdk) but computes no price: placement is rendered from the menu provider's option groups and the basket total is returned by the server (/v1/ordering/store-locations/:id/baskets/:id). The 20 archived api.koala.io menus in Wayback are all 'olo-full-xml-*' syncs of Olo menus, so any half-and-half pricing rule is the menu provider's. /\bhalf\b|halves|left.?half|right.?half/ = no pricing hit in 875 (the hits are CSS widths and error-envelope comments - POISON). Held unknown: no pricing module of Chowly's own. Retrieved 2026-09-18. || 334th: 334th NEW (notes only): the published menu schema carries no placement (left/right/whole) or half-pricing field: an option has only title, price, external_id, customization_option_id, suspend_until and nested customizations; /half|placement|portion/ = 0 in the spec. Chowly's partner-facing menu model can express a half build only as flat POS modifiers; held unknown (the pricing rule, if any, is the POS's), notes only. Source: https://api-docs.chowlyinc.com/toos/v2/ (Chowly's own OpenAPI 3.0.2 TOOS v2 spec, served anonymously; new this session) and/or chowly.help KB images. Retrieved 2026-09-18. adversarially verified

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

menu-pricing-topping-quantity-tiers

CLAIM: modifier quantity tiers (light/regular/extra/double) with a CONFIGURABLE PRICE MULTIPLIER per tier, distinct from adding the modifier twice. VERDICT: partial. EVIDENCE: Chowly Online Ordering (Koala) ships a dedicated nested 'Amount' option group per pizza topping - 'brands that allow a guest to customize their pizza toppings based on WEIGHT of topping' (https://chowly.help/s/article/Koala-Web-Release-November-13-2019) - handled as its own group ('amountGroup'), so a tier is a distinct selection rather than a repeat add, and each amount option carries its own cost and calories ('Bug where pizza topping amount and position calories and costs were not being surfaced to the user', https://chowly.help/s/article/Koala-Web-Release-May-20-2020). SHORTFALL: no configurable price MULTIPLIER is exposed anywhere in Chowly's own surfaces - the tier prices are absolute option prices that arrive from the connected menu provider, and 'multiplier' is 0/583 chowly.help articles, 0/958 chowly.app RCC source-map sources, 0/910 cms.koala.io source-map sources. Retrieved 2026-09-18. https://chowly.help/s/article/Koala-Web-Release-May-20-2020 · retrieved 2026-09-18 adversarially verified

Item base price can be defined as a grid across two variant axes (e.g. size x crust/preparation) with a per-cell price override. differentiator

menu-pricing-size-style-matrix

Toast: Item Settings with Chowly asserts its own completeness: "Which Item Settings Appear in Online Menus? The following item settings do go online: Name, Price, Modifiers, Inventory, Description, Image, and Visible To. All other settings groups within an item are not used by Chowly." One Price field per item, and the exclusion is stated explicitly. Clover with Chowly Overview says the same for that path - on an item you "make edits to price, item name, photos, and descriptions. Any other item-related settings will not effect your third party menus" - and Chowly's own Dejeuner editor exposes exactly "the item's name, price, tax rate, image, description" (Chowly Printer: Menu Management Overview). There is no two-axis variant grid and no per-cell price override on any documented path; a size or crust choice can only be expressed as an additive modifier price under the item's single base price. read via POST https://chowly.help/s/sfsites/aura (RecordServiceComponentController.getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c); the HTML at this URL is the site's inert CSS-error SPA shell. https://chowly.help/s/article/Toast-Item-Settings-with-Chowly · retrieved 2026-08-08

Items can define an included-modifier allowance (e.g. three toppings included) that automatically charges only for overage and credits or forbids substitutions per configuration. differentiator

menu-pricing-included-allowance

2026-08-08 enumeration audit, downgraded from no. Both legs miss the claim as worded. Brink with Chowly Overview self-describes as "the different features and required settings for Brink's integration with Chowly" and its "Disclaimer!" is a caution that "Chowly and your POS system may face integration issues if you are utilizing Included (default) Modifiers", advising that the Hamburger example be set to "minimum quantity ... 1 and the maximum quantity ... 6". That is troubleshooting advice on one POS path, not an enumeration of the item pricing rules available. FAQ - How do I make Default Modifiers? does carry a first-party non-support sentence - "modifiers are unable to appear on a third party menus as pre-selected" - but pre-selection is not the construct this claim names (an included count with automatic overage-only charging and a substitution credit/forbid setting), and the same article ends "For Toast and Revel Clients Only ... Toast and Revel clients are given the option to create them", which contradicts any universal reading. No retrieved page enumerates Chowly's item pricing rule surface. || 326th: SURFACE (new this pass, never censused before): https://cms.koala.io is the live production "Koala Brand CMS" - Koala is the digital-ordering company Chowly merged with, and this is the brand-config product the Koala-* articles in chowly.help describe. It is a Create-React-App SPA with a CLOSED /asset-manifest.json (58 .js.map entries) and a webpack runtime chunk-hash table of 57 lazy chunks that the manifest exactly covers; all 57 maps fetched 2026-09-18 and every one is REAL (begins {"version":3, and carries sourcesContent), 15 MB in total, 910 unique mapped sources of which 575 are Koala's own TypeScript/TSX (2.4 MB). SOFT-200 CONTROL PASSED: /static/js/zzz.NONSENSE.chunk.js.map returns a 79-byte "The page could not be found / NOT_FOUND" 404, not an SPA shell. 1 round, 0 misses. Grade B (production code the vendor does not publish as documentation). It bounds the Koala Brand CMS ONLY - not the Chowly Restaurant Control Center (chowly.app), not the POS, and not the ordering/kiosk runtimes it configures. allowance 0/910, "free topping" 0, overage 0, and both "substitut" (1) and "included" (3) occur only in bundled library sources - POISON, 0 in Koala's own 575 files. With no price field on either global products or global modifiers (closed field enumeration recorded on menu-pricing-topping-quantity-tiers), an included-count-then-charge-the-overage rule cannot be expressed in Koala's own menu layer at all. Retrieved 2026-09-18. || 328th: NEW SURFACE: the Koala Web Ordering feature enumeration (chowly.help kA01K000000oZjiSAE, 2023-11-07) and the pizza-template release notes were re-read for this cell. Chowly Online Ordering renders option groups exactly as the connected menu provider defines them ('modifiers as set in the menu provider'), so an included-modifier allowance with overage pricing would be a provider-side construct that Koala passes through; allowance 0/583 chowly.help, 0/958 chowly.app sources, 0/910 cms.koala.io sources, overage 0 in all three, and 'included' hits are unrelated (utensils, special instructions, API `included` JSON:API side-loads). Not scorable either way: the corpus bounds what Chowly DOCUMENTS, not what the upstream menu carries. Retrieved 2026-09-18. || 333rd: 333rd NEW (notes only): the Koala/COO guest client (closed bundle, 875 first-party sources) reads only min_selections, max_selections, min/max_aggregate_quantity, choice_quantity_increment and quantity_applied from the menu (src/features/product-customizer/product-options/*, src/utils/menu.ts); /free.?(modifier|topping|choice|quantity)|allowance/ = 0/875 and every 'included' hit is UI copy (cutlery preference, password rules) - POISON. Any overage price arrives priced from the menu provider (the archived api.koala.io menus are all 'olo-full-xml-*' Olo syncs). Held unknown: the module is the menu provider's. Retrieved 2026-09-18. || 334th: 334th NEW (notes only): the published menu schema's only quantity controls are min_permitted, max_permitted and supports_quantity_modifiers ('min_permitted/max_permitted are the total number of modifier units for the group'); no included/free-count field, every option carries its own flat price; /free|included|allowance/ = 0 in the spec. Held unknown (overage pricing, if any, is the POS's), notes only. Source: https://api-docs.chowlyinc.com/toos/v2/ (Chowly's own OpenAPI 3.0.2 TOOS v2 spec, served anonymously; new this session) and/or chowly.help KB images. Retrieved 2026-09-18. adversarially verified

Supports combo/meal construction where components can be swapped with a price delta, and the system can automatically detect and convert eligible a-la-carte items in the cart into the combo price.

menu-pricing-combos

2026-09-03 re-sweep (195th): the full chowly.help corpus (204 slugs via Aura) and 86 chowly.com pages were re-read; an analyst proposed partial from https://chowly.com/agents/upsell/ and the adversarial pass returned it to unknown: Quote confirmed (chowly-com/agents__upsell.txt:38,52,68) but it does not answer the claim. The claim is an operator-built combo/meal object with swappable components at a price delta plus automatic a-la-carte-to-combo conversion in the cart. The Upsell Agent's 'Bundle Built on the Fly' is an AI-generated add-on suggestion at checkout on 'online ordering and 1st-party app' (line 79); nothing describes a combo object, component swapping, a delta, or cart detection/conversion. Corpus grep for 'combo|meal deal|bundle' outside the upsell page hits only iOS bundle IDs, 'Popmenu bundles', and the same 'Cart-aware AI upsells & bundles' comparison line. Chowly mirrors menus from the POS (FAQ-Chowly-s-POS-API-Integration:36-37 'Chowly cannot: make changes to menus. make changes to menu items.'), so whether a POS combo propagates is simply undocumented. The present half is a different feature with a marketing sentence attached - that is unknown, not partial. No enumeration supports a no. Prior rationale: 2026-08-08 enumeration audit, downgraded from no. Re-read at https://chowly.help/articles/en_US/Knowledge/Chowly-Printer-Menu-Management-Overview. The article opens "This article proves an overview of how to manage (edit, revise) third party menus and hours for restaurants using Chowly's Printer Solution" - an overview, and scoped to one customer segment - and it is a task walkthrough (create/edit/delete/reorder categories, items, modifier groups, modifiers) rather than a declared-complete object model. The absence of a combo object from a how-to that never claims to enumerate Dejeuner's schema is silence. The Toast item-settings enumeration is genuinely closed but is about which ITEM settings propagate, and a combo/meal is a separate menu object rather than a setting on an item, so it does not reach this claim. The record's own corpus-wide zero-hit search for "combo", "meal deal" and "bundle" is a null search, which the evidence rules do not accept as positive evidence of absence. || 326th: SURFACE (new this pass, never censused before): https://cms.koala.io is the live production "Koala Brand CMS" - Koala is the digital-ordering company Chowly merged with, and this is the brand-config product the Koala-* articles in chowly.help describe. It is a Create-React-App SPA with a CLOSED /asset-manifest.json (58 .js.map entries) and a webpack runtime chunk-hash table of 57 lazy chunks that the manifest exactly covers; all 57 maps fetched 2026-09-18 and every one is REAL (begins {"version":3, and carries sourcesContent), 15 MB in total, 910 unique mapped sources of which 575 are Koala's own TypeScript/TSX (2.4 MB). SOFT-200 CONTROL PASSED: /static/js/zzz.NONSENSE.chunk.js.map returns a 79-byte "The page could not be found / NOT_FOUND" 404, not an SPA shell. 1 round, 0 misses. Grade B (production code the vendor does not publish as documentation). It bounds the Koala Brand CMS ONLY - not the Chowly Restaurant Control Center (chowly.app), not the POS, and not the ordering/kiosk runtimes it configures. combo 0/910, bundle 0/910, "meal deal" 0/910. What the CMS does ship in this area is CROSS-SELL, a first-class module (route /cross-sell, 22 source files, rule config with triggers, product and location search, and an upsell_weight field on every global product) - suggestive selling attached to a cart, not a combo object with swappable components and a price delta. That distinction is now sourced rather than inferred, but the cell still turns on a POS-side menu object that no Chowly surface enumerates. Retrieved 2026-09-18. || 328th: MERGE HOLD (proposed no/B, held unknown): Koala renders the connected POS/Olo menu, so a POS-built combo can pass through as an item; a zero over Koala's own feature enumeration does not bound what the rendered menu carries. The agent named this as its weakest row. PROPOSAL AS WRITTEN: CLAIM: combo/meal construction with component swap price deltas AND automatic detection/conversion of eligible a-la-carte cart items into the combo price. VERDICT: no for Chowly Online Ordering (Koala). BOUND: the vendor's own published Web Ordering feature enumeration (https://chowly.help/s/article/Koala-Web-Ordering-Feature-Set, modified 2023-11-07) lists every menu and basket feature under Core Experience > Navigate the Menu and View Basket & Checkout, plus Koala Customizations and the Olo add-on menu/checkout lists; the only basket-building mechanism enumerated is 'Cross-sell products to guests and increase check size' and 'Enable Machine Learning Cross Sell', which is an adjacent upsell, not combo construction. CONTROLS (tokenised, word-boundary, case-insensitive) over chowly.help (583 articles, full Salesforce Knowledge REST census), chowly.app RCC source maps (958 sources), cms.koala.io source maps (910 sources): combo 0/583, 0/958, 0/910; 'meal deal' 0 in all three; bundle 0 in all three; allowance 0 in all three. Positive controls in the same corpora: modifier 76/583, 'cross-sell'/'cross sell' present, pizza 10/583, so the corpora do carry menu-construction vocabulary. Retrieved 2026-09-18. || 333rd: 333rd NEW (notes only), bearing on the 327th hold ('Koala renders the connected POS/Olo menu'): CONFIRMED from the payloads themselves. Wayback holds 20 archived api.koala.io /v1/ordering/store-locations/<id>/menu responses (2022-06 .. 2026-08; e.g. store 8090 captured 2026-08-22, 1.70 MB) and EVERY one carries a data.id of the form 'olo-full-xml-<n>-<m>' with a synced_at stamp - the Koala menu is a sync of the Olo menu export, so combo objects and their pricing are Olo's, not Chowly's. The COO/Koala guest client (875 first-party sources, closed Next.js bundle on <slug>.onlineorder.site) prices nothing itself: option cards read min/max_selections, min/max_aggregate_quantity and choice_quantity from the menu and totals come back from /baskets/:id; /\bcombos?\b|\bmeals?\b|\bbundles?\b/ = 3/875, all POISON (a Salsarita's loyalty blurb 'Free Combo Upgrades', the 'Complete Your Meal' cross-sell string, a Sentry 'bundle size' comment). Held: the module belongs to the menu provider. Retrieved 2026-09-18. || 334th: 334th NEW (notes only): the menu Chowly publishes to ordering partners is a CLOSED nested schema - Menu > sections > subsections > items (title, price, tax_rate, external_id, suspend_until, customizations) > customizations (min_permitted, max_permitted, supports_quantity_modifiers) > customization_options (title, price), nested up to 2 levels (guide: 'Modifiers/Customizations can be nested up to 2 levels'; 'Sizes are most commonly displayed as modifiers'). No combo/meal/bundle object and no component-swap or price-delta field; /combo|meal|bundle/ = 0 in the spec. Consistent with the 327th hold (menu mirrored from the POS; 'Item and modifier prices may be 0 or null based on the POS that generated the menu'), so held unknown, notes only. Source: https://api-docs.chowlyinc.com/toos/v2/ (Chowly's own OpenAPI 3.0.2 TOOS v2 spec, served anonymously; new this session) and/or chowly.help KB images. Retrieved 2026-09-18. adversarially verified

Upsell/suggestive-sell prompts can be configured per item and per channel (POS, kiosk, online), and the vendor reports attach-rate on those prompts. differentiator

menu-pricing-upsell-prompts

Upsell Agent surfaces AI suggestions at digital checkout "without restaurant configuration", so not per-item/per-channel configurable, and no attach-rate report documented. https://chowly.com/solutions/branded-online-ordering/ · retrieved 2026-08-01

A single 86 action propagates automatically to POS, KDS, the vendor's own online ordering, kiosk, and connected third-party marketplaces, with a documented propagation latency.

menu-pricing-86-propagation

"86 it in your POS and it disappears from every delivery app instantly." Covers POS to 3P and first-party. No kiosk; no numeric propagation latency published. https://chowly.com/solutions/3rd-party-marketplace-integration/ · retrieved 2026-08-01

Supports per-item countdown/par counts that decrement on sale and automatically 86 the item at zero, with a scheduled auto-restore. differentiator

menu-pricing-countdown-auto-86

Auto-86 at zero does exist inside a Chowly-owned product. On the Koala plus Square path, Koala monitors Square inventory and an item at 0 or below is removed from the guest-facing menu automatically, and the RCC 86 screen adds a timed auto-restore: unless the operator changes it, "all items and mods will default to come back in stock at the start of your next business day" (kb:Suspending-Items-Restaurant-Control-Center), with custom date/time and indefinite options. Partial rather than yes: Chowly holds no quantity of its own — the count lives in Square, the behaviour is Koala Enterprise-scoped, and on the ordinary POS-sync path kb:Square-Mark-Items-as-Sold-Out says Chowly "cannot automatically detect an item’s inventory quantity", so items can still show as available at stock zero. (chowly.help serves an inert SPA shell; bodies are the Aura mirror.) https://chowly.help/s/article/Koala-Square-Menu-Partners-Inventory-Function · retrieved 2026-09-06 adversarially verified

Menus, individual items, and prices can be scheduled to activate and deactivate automatically by day and time in the location's own timezone.

menu-pricing-dayparting

Restaurant Control Center > Menu Management > Hours carries a Holiday Hours editor: pick a date in the calendar picker, take the default "Closed All Day" or choose "Open during a custom time" with a start and end time, and save "to apply this Holiday Hour across all of your Online Ordering platforms integrated within the Restaurant Control Center"; the article states "Holiday Hour settings are relative to the location's time zone." Shortfall: this is store-hours scheduling only - one single future date at a time, no same-day create or delete, and no item-level or price-level activation windows anywhere in Chowly. Regular hours are read out of the POS ("Chowly simply takes whatever hours settings you have in your POS and/or ordering channels and puts them out to your customers"), and product/modifier availability scheduling by date and time is performed in Olo's dashboard, for Koala Enterprise customers using Olo (Koala-Olo-Menu-Partners-Scheduling-Product-Availability), not in Chowly. read via the site's Salesforce Aura record endpoint (RecordServiceComponentController.getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c); the HTML at this URL is the site's CSS-error SPA shell. https://chowly.help/s/article/FAQ-How-Do-I-Set-Up-Holiday-Hours · retrieved 2026-08-08

Supports distinct price books per channel (dine-in, pickup, delivery, kiosk, each third-party marketplace) including percentage-markup rules applied to a base price rather than manual per-item entry.

menu-pricing-channel-price-books

The verbatim marketing text is only "Set up-charge percentages by location or by individual ordering platform." A percentage markup is not a price book: no per-item channel price override, no independent channel menu price list, no documentation of what happens to items that need a different absolute price rather than a uniform uplift. Also a marketing page, not product documentation. https://chowly.com/solutions/restaurant-control-center/ · retrieved 2026-08-01 adversarially verified

Supports dual pricing / cash-discount at the item level with the card price displayed as the base price, applied consistently across POS, kiosk, and online ordering, and printed on the receipt. differentiator

menu-pricing-dual-pricing

Chowly's one documented price-setting lever is a channel markup sitting downstream of the operator's POS, so the tender axis this claim requires has nowhere to live. "Some restaurants choose to make their online menus a little more expensive than their in house menu." "In the Upcharge field, you can add a number that then gets translated into a percentage. For example, 5.0 is a 5% upcharge, 7.5 is a 7.5% upcharge", and "This upcharge is then applied to whatever price you have set for your menu items in your POS system." - "a 5% upcharge will make this item appear as $10.50 to customers ordering online". The percentage is chosen per location ("Click the location that you would like to add or edit upcharges for") and optionally per platform ("Scroll down to the Platform List Table near the bottom of the page, and click the name of whichever platform you would like to add or edit upcharges"), and it is baked into the menu published to an ordering channel before any card is presented, so it cannot vary by tender. The base price is the operator's POS price, which Chowly reads and does not write, and Chowly prints no receipt. The one occurrence of the claim's own phrase is this article's closing line and it means something else: "Note: Up-charges are not supported for pickup menus on Doordash, as Chowly implemented dual pricing support specifically to meet DoorDash's requirements." - a marketplace pickup-versus-delivery menu rule, not cash versus card. No card-price-as-base, no cash discount, no item-level tender price, no receipt disclosure. This is not a corpus zero-hit: the verdict rests on what this article says the mechanism is. Currency: LastPublishedDate 2026-02-24, one of only nine 2026-published articles in the 203-article corpus, so it documents the current product. https://chowly.help/s/article/Upcharge-Settings-on-the-Restaurant-Control-Center · retrieved 2026-09-05 adversarially verified

Menu changes can be staged as an effective-dated version, previewed before publish, and rolled back to a prior version after publish. differentiator

menu-pricing-versioning-effective-dates

Two of the three legs exist, for one customer segment only. Chowly Printer: Menu Management Overview documents a genuine stage-then-publish split in Dejeuner: "The 'Save' button will ensure that all changes made on Dejeuner are set and updated. The 'Publish' button then sends the most updated version of Dejeuner to connected third party platforms", and a preview - "Click the 'View Menu' button to see how your third party menus will appear for customers when ordering on a computer's web browser. Click the 'View QR Code' button ... to see how your third party menus will appear ... on a cell phone." SHORTFALLS: (1) the staged change carries no effective date - there is no future-dated activation anywhere in the article; (2) no rollback to a prior published version is documented, and no version history is exposed; (3) the surface is Printer-only. Sync customers get no staging at all: FAQ - How do I change my menu and Resyncing Your Menu on the Restaurant Control Center route every structural edit to the POS followed by a single "Resync Menu" button, and the effective-dating that does appear on the Revel path ("Edit Effective Date/Time ... There needs to be an effective date and time range for the menu to be continually synced", Revel Sync) belongs to Revel's Custom Menus, not to Chowly. read via POST https://chowly.help/s/sfsites/aura (RecordServiceComponentController.getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c); the HTML at this URL is the site's inert CSS-error SPA shell. https://chowly.help/s/article/Chowly-Printer-Menu-Management-Overview · retrieved 2026-08-08

Supports a central corporate menu template pushed to locations with field-level governance controlling which attributes a location may override. differentiator

menu-pricing-franchise-hierarchy

2026-08-08 re-sweep. Rebuilt the chowly.help corpus independently rather than trusting the sitemap: POST /s/sfsites/aura with RecordServiceComponentController.getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c, seeded from /s/sitemap-topicarticle-1.xml (114 slugs) and crawled to fixpoint over every chowly.help/s/article/ href inside the retrieved bodies - 204 slugs reached, 195 with live bodies, 9 dead (getArticleVersionId returns null and the URL 404s, including Smart-Pricing-Overview and Delivery-Search, both linked from live articles). Re-checked the multi-location surface across all three of Chowly's own admin tools and the Koala Brand CMS. Chowly's Restaurant Control Center is documented as location-aware but not template-aware: Creating a Restaurant Control Center Account provisions accounts against named locations, FAQ - How do I set upcharges to my menu items sets upcharges per location, and the seven RCC analytics pages named in Sales Reporting Page on the Restaurant Control Center (Locations, Sales, Orders, Product Mix, Week over Week, Delivery Buydown, Smart Pricing) are reporting only. In Koala, a master-menu shape exists but belongs to the menu provider: Koala Olo Menu Partners: Olo Menu Setup instructs brands to "set up your master menu with descriptions, calories, and pricing" then "enable location-based menus for each of your locations", and Koala Location Configurations: Delivery-Only Locations shows the one documented override mechanism - "a brand must override the global settings in the CMS. (Locations > Select location > Location Attributes > select a CTA > Edit)" - which governs CTAs on a location card, not menu attributes, and says nothing about which fields a location may or may not override. No field-level governance model is published anywhere. Unresolved. || 326th: SURFACE (new this pass, never censused before): https://cms.koala.io is the live production "Koala Brand CMS" - Koala is the digital-ordering company Chowly merged with, and this is the brand-config product the Koala-* articles in chowly.help describe. It is a Create-React-App SPA with a CLOSED /asset-manifest.json (58 .js.map entries) and a webpack runtime chunk-hash table of 57 lazy chunks that the manifest exactly covers; all 57 maps fetched 2026-09-18 and every one is REAL (begins {"version":3, and carries sourcesContent), 15 MB in total, 910 unique mapped sources of which 575 are Koala's own TypeScript/TSX (2.4 MB). SOFT-200 CONTROL PASSED: /static/js/zzz.NONSENSE.chunk.js.map returns a 79-byte "The page could not be found / NOT_FOUND" 404, not an SPA shell. 1 round, 0 misses. Grade B (production code the vendor does not publish as documentation). It bounds the Koala Brand CMS ONLY - not the Chowly Restaurant Control Center (chowly.app), not the POS, and not the ordering/kiosk runtimes it configures. This is the first surface that shows Chowly/Koala's actual multi-location menu model, and it lands between the claim's two conjuncts. CENTRAL TEMPLATE - yes, in a strong sense: the CMS's menu is literally a GLOBAL menu, organization-scoped (services/globalMenu.service.ts GETs /global_products with include[]=verifications&include[]=allergens&include[]=tags&include[]=global_product_options and PUTs by id), edited once per brand at /global-menu/products, /global-menu/product-modifiers and /global-menu/tags, and applied to every location of that organization. FIELD-LEVEL GOVERNANCE - absent: there is no location-level menu at all. The per-location surface (routes /locations/:id/attributes, /locations/:id/info, /locations/:id/kiosks/:kioskId) governs location attributes, CTAs, kiosk config and status (Active / Hidden from search / Inactive, constants/koala/config.ts), never menu attributes, and the 910 sources contain no override, inheritance or lock construct on a menu field (franchise 0). A location cannot override brand menu fields at all, which is not the same as being governed in which ones it may. Held unknown rather than partial for that reason; the OWNER may reasonably read a menu that is global by construction as satisfying the template conjunct. Retrieved 2026-09-18. || 328th: NEW SURFACE: chowly.help 'Aloha: Pricing Management' (kA01K000000oZcXSAU) is the one article that addresses corporate-vs-location menu pricing, and it directs the operator to do all of it INSIDE the POS ('restaurants using Chowly with the Aloha POS system can change and update prices on their third party menus ... uniform across all store locations, different across store locations'); Chowly holds no central menu template of its own. The Koala Brand CMS does carry a config inheritance model ('component-level configs are left undefined, allowing for a "define globally and only override when necessary" paradigm', chowly.help kA01K000000oa1ISAQ) but it governs SITE/UI configuration, not menu attributes, and no field-level governance list exists in the 910 cms.koala.io source-map sources. Held unknown: the module is the POS's, not Chowly's. Retrieved 2026-09-18. adversarially verified

Stores allergen flags and nutrition values per item and publishes them to online ordering and third-party menus, and can derive nutrition from linked recipe components rather than manual entry.

menu-pricing-allergen-nutrition

Chowly does store an ingredient/allergen-style flag of its own. Koala Menu Configurations: Dietary Preferences - 'Dietary Preferences allow you to set "ingredient" tags on certain items that can help guide guests in choosing the right meal for them' - has the operator build a global tag list in the Brand CMS (Global Menu > Tags) and apply tags at product level ('always present in the meal') and at modifier level ('the customization of a meal may remove a certain dietary tag'), with a guest-selectable filter and a 'rollup of dietary preferences based on the final construct and customization of their meal', on Web, iOS Mobile and Kiosk. Nutrition is thinner: Koala-Menu-Configurations-Nutrition-URL-PDF provides one 'global URL ... linked from all menu item PDPs', not per-item values; calories come through 'as set in the menu provider' (Koala-Web-Ordering-Feature-Set); and Koala-Olo-Users-Only-Compliance-Labels surfaces Olo's High Sodium and Prop 65 labels only. Shortfalls: nutrition values are not stored per item and are the menu provider's; the nutrition document is one brand-wide PDF/URL; dietary tags sync only every 24 hours; all of this is Koala Enterprise web/iOS/kiosk, not the third-party marketplace path, and nothing is published out to third-party marketplace menus; and there is no recipe model to derive nutrition from (settled at menu-pricing-recipe-linkage). Read via the Salesforce Aura record endpoint; the HTML at this URL is the site's CSS-error SPA shell. https://chowly.help/s/article/Koala-Menu-Configurations-Dietary-Preferences · retrieved 2026-08-08 adversarially verified

Menu items and modifiers can be linked to recipes/bills of materials so that a sale depletes theoretical inventory and yields item-level theoretical food cost. differentiator

menu-pricing-recipe-linkage

Ships no inventory or recipe product. https://chowly.com/chowly-platform/ · retrieved 2026-08-01

Pushes menus to third-party marketplaces through a certified direct integration (not scraping or a menu-management middleman) and surfaces per-item sync status and rejection errors to the operator.

menu-pricing-3p-menu-push

Bi-directional POS-to-marketplace menu sync since 2021 across 150+ channels via direct certified integrations; DPIP status requires real-time menu syncing and detailed order error reporting. https://chowly.com/solutions/3rd-party-marketplace-integration/ · retrieved 2026-08-01

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

menu-pricing-dynamic-pricing

Pricing Agent adjusts per-item, per-platform, per-time-slot on demand and elasticity. No configurable floor/ceiling guardrails documented. https://chowly.com/solutions/dynamic-pricing/ · retrieved 2026-08-01

The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator

payments-processor-choice

No open processor choice is documented. The Stripe setup guide states: 'If your Chowly subscription includes Google Direct Order and/or Chowly Online Ordering, you will need to create a Stripe account. Chowly has partnered with Stripe to provide payment processing services.' Stripe is mandatory for Chowly's first-party ordering; Koala ordering uses the merchant's own Square account; delivery-marketplace orders settle through the merchant's existing setup. Chowly has no in-house acquiring, but processing is channel-locked with no selectable list of gateways, so partial not yes. https://chowly.help/s/article/creating-a-stripe-account-for-chowly · retrieved 2026-08-06

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

payments-published-rates

Not a processor; publishes no card rates. Only published transactional rate is Google Ordering at $0.30 + 2.9% + up to 10% of Base Order Value. https://chowly.com/terms-and-conditions/ · retrieved 2026-08-01

Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator

payments-dual-pricing

Chowly’s own vocabulary uses "dual pricing" for a different thing: kb:Upcharge-Settings-on-the-Restaurant-Control-Center says up-charges are unsupported for DoorDash pickup menus because "Chowly implemented dual pricing support specifically to meet DoorDash’s requirements" — channel-level pickup-versus-delivery pricing, not a cash-versus-card differential at tender. The Diner Terms sentence routing payments to the merchant’s processor says who settles a payment, not whether two prices are presented by tender type, so it does not carry the cell in either direction. A Chowly document describing a cash discount or card surcharge presented to a guest would settle it; the corpus contains none, and absence is not measurable on chowly.help. || 324th: NEW SURFACE AND A HOMONYM TRAP, recorded so the next pass does not score it backwards. The full chowly.help census (583 articles, Salesforce guest knowledge API https://chowly.help/services/data/v59.0/support/knowledgeArticles?pageSize=100 - 5.1x the 114-slug sitemap corpus prior passes used) contains exactly ONE occurrence of the phrase 'dual pricing', and it is NOT the card-network cash-discount/surcharge sense this cell scores. 'Upcharge Settings on the Restaurant Control Center' (https://chowly.help/s/article/Upcharge-Settings-on-the-Restaurant-Control-Center, modified 2026-02-24) closes with: 'Note: Up-charges are not supported for pickup menus on Doordash, as Chowly implemented dual pricing support specifically to meet DoorDash's requirements.' That is DoorDash's delivery-vs-pickup menu-price differential - the same homonym the 260th recorded for DoorDash's MENU_CONTAINS_ITEM_LEVEL_BASE_PRICE flag. The article otherwise describes only a percentage menu markup applied to POS prices ('5.0 is a 5% upcharge... a 5% upcharge will make this item appear as $10.50'), settable per-location or per-platform, and negative ('downcharges'). Controls over the 583 bodies: /\bcash\s+discount/ 0/583, /\bsurcharg\w*/ 1/583 (a 2020 Koala release note, not a card surcharge programme). No card-brand-compliant dual pricing, no debit/prepaid exclusion rule and no receipt-disclosure requirement is documented anywhere in the census. Stays unknown - Chowly is not the processor (payments settle through Square, Toast or Stripe per https://chowly.help/s/article/COO-and-Chowly-Platform-FAQ), so the capability would belong to those processors. Retrieved 2026-09-17. || 327th: 327th: NEW SURFACE, homonym now confirmed from the vendor's own rebuilt site; still unknown. chowly.com was rebuilt as a Next.js site since the last pass and all 167 sitemap URLs were fetched today. https://chowly.com/solutions/dynamic-pricing/ names the two-price construct explicitly and it is a CHANNEL split, not a tender split: '1P vs 3P Price Differentiation - Maintain lower prices on your commission-free direct ordering while 3rd party menus reflect the true cost of marketplace commissions', and the Pricing Agent 'adjusts your third-party menu prices automatically based on demand, recovering the 15-30% commission marketplaces take'. The 2026-01-13 Terms names the subprocessor behind it: 'Sauce Technologies, Inc. (dynamic pricing services)'. So Chowly does store two prices per item, keyed to ORDERING CHANNEL, never to cash-vs-card, and it prints no guest check. CONTROLS over 583 chowly.help articles, 958 chowly.app RCC sources, 910 cms.koala.io sources and 167 site pages: /cash discount|cash price|card price/i = 0, 0, 0, 0; /dual pric/i = 1/583 (the 'Upcharge Settings on the Restaurant Control Center' homonym already recorded), 0, 0, 0. Held unknown rather than scored no: a cash-discount tender mode is a card-present POS module Chowly's product does not contain at all. Retrieved 2026-09-18. || 332nd: MERGE HOLD (proposed no/B, held unknown): One SpotOn-integration sentence (Chowly cannot read the POS 'Cash Price' setting) is an integration limitation, not a bound on dual pricing across Chowly's own ordering/kiosk surfaces. PROPOSAL AS WRITTEN: 332nd: PROPOSED unknown -> no (B) on a NEW VENDOR SENTENCE, not on a census zero. CLAIM: a native dual-pricing / cash-discount mode that stores two prices per item and prints both cash and card prices. NEW EVIDENCE (per-cell re-grep of the 583-article census with the VENDOR'S term 'Non-Cash Price', which the 324th-327th controls /cash discount|cash price|card price|dual pric/ did not tokenise): where the POS itself runs dual pricing, Chowly states it carries only ONE of the two prices. SpotOn: Menu Item Settings with Chowly (https://chowly.help/s/article/SpotOn-Menu-Item-Settings-with-Chowly, published 2024-02-23): 'Set its price in the "Non-Cash Price" section (Chowly is unable to read the "Cash Price" setting).' SpotOn: Modifier Settings with Chowly (https://chowly.help/s/article/SpotOn-Modifier-Settings-with-Chowly, 2024-02-23): 'Use the "Non-Cash Price" column to make certain Modifier Group options cost additional money'. So Chowly's menu model ingests a single price per item even from a dual-pricing POS; its only two-price construct is the channel split already recorded (1P vs 3P pricing; DoorDash pickup-vs-delivery 'dual pricing' homonym). BOUND - four censuses on disk, each 100% of its publisher's own manifest, re-verified CURRENT by the 332nd today: (a) chowly.help Salesforce Knowledge, 583/583 articles (.cache/q324/chowly/ch/arts); the listing https://chowly.help/services/data/v59.0/support/knowledgeArticles?pageSize=100 was re-paged 2026-09-18 (6 pages) and still returns 583 ids, ZERO not already held, newest lastPublishedDate 2026-06-16, so the census has not gone stale; (b) the Restaurant Control Center chowly.app, 958 sources from the complete /asset-manifest.json source-map set (.cache/q325/chowly/src; today's manifest still names main.54b02cd0.js, the censused build); (c) cms.koala.io Koala Brand CMS, 910 mapped sources (.cache/q326/chowly/cmssrc; today's manifest still names main.12caeb2d.chunk.js, the censused build); (d) all 167 chowly.com sitemap pages (.cache/q327/chowly/sitetxt). KNOWN-POSITIVE CONTROLS (tokenised, word-boundary, case-insensitive; KB/RCC/Koala/site docs hit): /\btoast\b/ 48/114/0/113, /\bmenus?\b/ 273/110/35/125 - the regexes fire. Script: .cache/q332/chowly/a/ctl.mjs, output ctl-out.json. CONTROLS: /cash discount\w*|dual pric\w*|cash price|card price/ = 3/583 (the DoorDash homonym + the two SpotOn sentences above), 0/958, 0/910, 0/167; /surcharg\w*/ 1/583 (a 2020 Koala release note), 0/958, 0/910, 1/167. WEAKEST PART: the non-support sentence is scoped to the SpotOn integration path, and earlier merges held this cell as a card-present module the product lacks entirely; if that hold governs, keep the SpotOn sentence as a note. Retrieved 2026-09-18. adversarially verified

Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator

payments-surcharge-guardrails

2026-08-08 re-sweep. Rebuilt the chowly.help corpus independently rather than trusting the sitemap: POST /s/sfsites/aura with RecordServiceComponentController.getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c, seeded from /s/sitemap-topicarticle-1.xml (114 slugs) and crawled to fixpoint over every chowly.help/s/article/ href inside the retrieved bodies - 204 slugs reached, 195 with live bodies, 9 dead (getArticleVersionId returns null and the URL 404s, including Smart-Pricing-Overview and Delivery-Search, both linked from live articles). Searched every body for surcharge, BIN, debit, prepaid, interchange and card brand: zero occurrences of the first five, and the only card-type mention is a location-card display of "accepted credit cards" in Koala: Web Ordering Feature Set. What the widened corpus does establish is architectural: Chowly is never the acquirer. First-party checkout settles into the restaurant's own Stripe account (creating a Stripe account for Chowly - "Chowly will not have access to your Stripe account"), Koala web and kiosk settle through the brand's own Square account using brand-supplied application IDs and access tokens (Koala Square Menu Partners: Square Application ID and Access Tokens; Koala iOS Kiosk App Deployment: Kiosk Kickoff Requirements names Square and PCI Proxy as the payment partners), and refunds are performed in the Square dashboard, not in a Chowly screen (Koala Square Menu Partners: Issuing a Refund). A BIN/product-code guardrail engine is therefore unlikely to be Chowly's to operate, but no source says so and no source rules it in. Unresolved. || 327th: 327th: NEW SURFACE - the fee engine Chowly DOES ship is now enumerated, and it carries no card-brand logic. The chowly.app Restaurant Control Center source-map census (958 first-party sources from the complete /asset-manifest.json map set; grade B, production code not published as documentation) holds the whole fee surface: components/ServiceFee/ServiceFee.tsx writes {service_fee_rate, service_fee_type: 'percentage'|'fixed'} per platform per location via updateOrderPlatform, validating only 'Please enter a percentage between 0 and 100'; components/PosServiceFeeId/PosServiceFeeId.tsx maps it to a POS fee id; components/LocationUpcharge/LocationUpcharge.tsx applies a -100..100% markup where 'Upcharge percentage will apply to all baskets prior to tax'. That is a per-location, per-ordering-platform basket fee. CONTROLS for the claim's guardrails across 583 chowly.help articles, the 958 RCC sources, 910 cms.koala.io sources and all 167 pages of the rebuilt chowly.com: /\bBIN\b|debit card|prepaid card|surcharge cap|interchange|network cap/i = 1/583, 0/958, 0/910, 2/167. The single KB hit is 'Toast Pay Chargebacks on Chowly Online Ordering' discussing a chargeback, not card-product detection. POISON NAMED in the two site hits: chowly.com/diner-terms-and-conditions/ says 'If the charge to your credit or debit card incorrectly differs from the total amount displayed to you at checkout', which is a diner re-charge clause and not a surcharging rule, and best-restaurant-management-software matches /interchange/ only inside the word INTERCHANGEABLY ('used interchangeably'). No BIN/product-code detection and no network percentage cap exists anywhere. Held unknown, not no: card acceptance itself is not Chowly's - the merchant's own Stripe or Toast Pay account takes the card - so a surcharging ENGINE is a module the product does not contain. Retrieved 2026-09-18. adversarially verified

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

payments-emv-nfc

No first-party terminals. Apple Pay/Google Pay are supported in the online checkout only. https://chowly.com/solutions/branded-online-ordering/ · retrieved 2026-08-01

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

payments-softpos-tap-to-pay

Chowly does have a card-present surface — the Koala iOS Kiosk, whose kickoff article states "We partner closely with Square to power payment on our kiosks" — and its documented acceptance mechanism is the opposite of softPOS: a separate Square Reader is paired to the iPad, and when that reader fails the operator is told they may need to purchase a new one. Contactless taken on the device itself with no separate reader is excluded by the deployment architecture of the only card-present product Chowly documents. (chowly.help serves an inert SPA shell; body is the Aura mirror.) https://chowly.help/s/article/Koala-iOS-Kiosk-App-Deployment-Pairing-the-the-Square-Reader-App · retrieved 2026-09-06 adversarially verified

Vendor ships a handheld that takes EMV/NFC payment at the table, including tip prompt and check splitting, without carrying the card away.

payments-pay-at-table

No handheld hardware. https://chowly.com/chowly-platform/ · retrieved 2026-08-01

Guest can scan a QR code on the printed check or table tent to view and pay the check from their own phone, with the payment closing the check in the POS automatically. differentiator

payments-qr-guest-pay

Lunchbox's partner documentation for its Chowly integration states verbatim: 'Chowly integration does not support Scan-to-Pay, Subscriptions, or Catering.' Structurally the claim also has no surface on Chowly's side: it prints no guest checks or table tents, ships no dine-in product, and its documented POS direction is order injection — nothing anywhere describes reading or closing an open POS check. No QR pay-the-check flow appears in Chowly's own materials (ordering feature pages, the 193-URL sitemap, or the help-centre article slugs). Grade E because the explicit limitation statement is a partner's support page (Dec 2023) describing the Chowly pipeline rather than Chowly's own documentation. https://support.lunchbox.io/en/articles/8684645-chowly-overview · retrieved 2026-08-04

Supports both pre-auth-then-tip-adjust and on-device tip prompt flows, with a documented batch/adjust window and a manager screen for unadjusted tips.

payments-tip-adjust

The vendor’s tipping configuration document for its own ordering surfaces describes the whole mechanism: the guest selects one of three configurable percentage tiers or a custom amount at checkout, before the card is charged, so the tip is fixed at authorisation. No adjust window, batch close or unadjusted-tip screen appears in that configuration or anywhere else in the corpus. Bounded: card-present tip adjustment on an operator’s own terminal, and on the Square reader paired to a Koala kiosk, belongs to that POS or to Square rather than to Chowly. https://chowly.help/s/article/Koala-Checkout-Configurations-Tipping · retrieved 2026-09-06 adversarially verified

Configurable tip pooling and distribution rules (by hours worked, sales, role percentage, or points) that produce a per-employee tip allocation exportable to payroll. differentiator

payments-tip-pooling

No labor product. https://chowly.com/chowly-platform/ · retrieved 2026-08-01

Card payments can be captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. differentiator

payments-offline-store-and-forward

Nothing in the 375-document corpus addresses capturing card payments while the connection is down. "Offline" occurs only in blog copy about taking review disputes offline and in an Olo webhook for a vendor going offline; the kiosk best-practices article merely instructs operators to ensure the devices have a reliable internet connection. A Koala kiosk or Chowly checkout document describing behaviour during a network outage, with per-transaction or cumulative offline limits, would settle it. The corpus holds no such document, and absence is not measurable on chowly.help. || 331st: 331st NEW (notes only): the only card-PRESENT path Chowly ships is the Koala iOS Kiosk, and its card capture is Square's, not Chowly's: 'To pair your Square card reader, select Connect a Reader and follow the on-screen instructions provided by Square' and 'Grant the App permissions to use the Microphone* *this is for the Mag swipe reader' (https://chowly.help/s/article/Koala-iOS-Kiosk-App-Deployment-Application-Initialization); kiosk payments land in the brand's own Square account (Koala-iOS-Kiosk-App-Deployment-Verifying-Square-Payment-with-Koala). Per-cell re-grep for offline|store-and-forward|SAF|internet|network outage|connectivity over the 583-article chowly.help census, 958 chowly.app RCC sources, 910 cms.koala.io sources, 167 chowly.com pages and the 2026-01-13 Terms: the one functional 'offline' hit is an Olo webhook ('VendorAvailabilityChanged A vendor has gone offline or online'); the kiosk best-practices article says only 'Ensure the devices have a reliable internet connection'. Offline capture on this path would be a Square Reader SDK behaviour Chowly neither documents nor controls; the web/app channels are card-not-present and cannot store-and-forward. Also checked: koalalabs.zendesk.com (the retired Koala help centre that 33 chowly.help bodies still link to) now 404s every article id and its /api/v2/help_center, and Wayback holds 1 article of it. Retrieved 2026-09-18. adversarially verified

Vendor publicly documents who bears the loss when a stored offline transaction declines on reconnect, and surfaces a post-reconnect report of failed offline payments. differentiator

payments-offline-decline-liability

332nd: MOVED unknown -> no (B). CLAIM: the vendor PUBLICLY DOCUMENTS who bears the loss when a stored offline transaction declines on reconnect, AND surfaces a post-reconnect report of failed offline payments - publication-shaped. This is the exact twin of reliability-offline-decline-liability, which LANDED no/B in 331st batch 1 on the same four censuses; the two cells should not disagree. The claim applies: Chowly runs one card-present path of its own (Koala iOS Kiosk + paired Square reader; 'any payments your guests make on a kiosk will appear in your dashboard', https://chowly.help/s/article/Koala-iOS-Kiosk-App-Deployment-Verifying-Square-Payment-with-Koala). BOUND - four censuses on disk, each 100% of its publisher's own manifest, re-verified CURRENT by the 332nd today: (a) chowly.help Salesforce Knowledge, 583/583 articles (.cache/q324/chowly/ch/arts); the listing https://chowly.help/services/data/v59.0/support/knowledgeArticles?pageSize=100 was re-paged 2026-09-18 (6 pages) and still returns 583 ids, ZERO not already held, newest lastPublishedDate 2026-06-16, so the census has not gone stale; (b) the Restaurant Control Center chowly.app, 958 sources from the complete /asset-manifest.json source-map set (.cache/q325/chowly/src; today's manifest still names main.54b02cd0.js, the censused build); (c) cms.koala.io Koala Brand CMS, 910 mapped sources (.cache/q326/chowly/cmssrc; today's manifest still names main.12caeb2d.chunk.js, the censused build); (d) all 167 chowly.com sitemap pages (.cache/q327/chowly/sitetxt). KNOWN-POSITIVE CONTROLS (tokenised, word-boundary, case-insensitive; KB/RCC/Koala/site docs hit): /\btoast\b/ 48/114/0/113, /\bmenus?\b/ 273/110/35/125 - the regexes fire. Script: .cache/q332/chowly/a/ctl.mjs, output ctl-out.json. CELL CONTROLS: /store[- ]and[- ]forward|\bSAF\b|deferred authori[sz]ation|offline (payment|transaction|card|mode)s?/ = 0/583, 1/958, 0/910, 0/167 and /offline (limit|cap)s?|per[- ]transaction limit/ = 0/583, 1/958, 0/910, 0/167 - the single RCC hit for both is CRA serviceWorker.js boilerplate ('gives it offline capabilities'), POISON. The 2026-01-13 restaurant Terms carry no chargeback, offline or decline allocation (liability provisions are only the general cap and the as-is disclaimer); the diner terms say only 'All payments will be processed by the Merchants' payment processor'. SECOND CONJUNCT: the RCC's shipped reporting index (10 pages incl. Disputes and Reconciliation, which are marketplace/online disputes) and its 16 sigmaPages embeds carry no failed-offline-payment report. WEAKEST PART: the kiosk's card engine is Square's, and Square publishes its own offline rules - Square's publication, not Chowly's. Retrieved 2026-09-18. https://chowly.com/terms-and-conditions/ · retrieved 2026-09-18 adversarially verified

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

payments-gift-cards

"Gift Card Support" is enumerated under Checkout in Koala: Web Ordering Feature Set, so gift cards can be tendered through the first-party ordering channel. Shortfall: it appears only inside the "For Olo Users Only: Add-On Features" block, i.e. acceptance of gift cards issued by the Olo stack, not a Chowly-issued stored-value product; nothing equivalent is listed for the Square menu/payment path or for third-party marketplace orders; and no article in the 115-article help centre documents card issuance, activation or reload, real-time balance tracking, or cross-location redemption within a group. The corpus contains no occurrence of "stored value" and no gift-card article of any kind. read via the site's Salesforce Aura record endpoint (RecordServiceComponentController.getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c); the HTML at this URL is the site's CSS-error SPA shell. https://chowly.help/s/article/Koala-Web-Ordering-Feature-Set · retrieved 2026-08-08

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

payments-house-accounts

2026-08-08 re-sweep. Rebuilt the chowly.help corpus independently rather than trusting the sitemap: POST /s/sfsites/aura with RecordServiceComponentController.getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c, seeded from /s/sitemap-topicarticle-1.xml (114 slugs) and crawled to fixpoint over every chowly.help/s/article/ href inside the retrieved bodies - 204 slugs reached, 195 with live bodies, 9 dead (getArticleVersionId returns null and the URL 404s, including Smart-Pricing-Overview and Delivery-Search, both linked from live articles). Searched every body for house account, on account, invoice, credit limit, statement, net terms and ACH: no occurrences bearing on a tender. The complete documented payment surface is third-party settlement plus two first-party processors - marketplace tenders arriving through the integration (Brink with Chowly Overview shows the operator configuring a Tender per platform with "Tender Type ... External"), Stripe for Google Direct Order and Chowly Online Ordering, and Square for Koala web and kiosk. Guest-side stored value is limited to "Save and delete credit cards" and "Gift Card Support" in Koala: Web Ordering Feature Set, both Olo-only add-ons. None of these articles enumerates a tender list for the product, and Chowly is not a POS with a back office where running balances and statements would live, so absence here carries little information either way. Unresolved. || 333rd: 333rd NEW (notes only): NEW SURFACE (333rd, never censused): the CHOWLY ONLINE ORDERING guest client that every Chowly white-label tenant runs (<slug>.onlineorder.site; the App Store publisher census's 51 apps carry bundle ids site.onlineorder.<slug>). It is the Koala web-ordering Next.js app (theme CSS from koala-web-ordering-themes.s3.amazonaws.com), one multi-tenant build (buildId 94f531751c59ff7df44392c822336a31a4d8642d served on stuftpizzabarandgrill.onlineorder.site and muldoonpizza.onlineorder.site alike). CLOSED BUNDLE: _buildManifest.js names 21 pages (/, /account/*, /checkout, /store/[...id], /stores, /order-confirmation, /arrival-confirmation ...) and the initial chunk set; the webpack runtime defines NO chunk-URL / lazy-load function (no .u/.e/.l), so the initial set is the whole app; 45 of 45 app chunks serve a real .map with sourcesContent (only the polyfills chunk has none), 2,148 mapped sources, 875 first-party incl. the vendored @koala/sdk (packages/sdk/dist/index.mjs + v4). Soft-404 control: /_next/static/chunks/zzz-nonsense333.js.map -> 404. Scratch: .cache/q333/chowly/a/coo/js (maps), .cache/q333/chowly/a/ctl.mjs (five-corpus control runner). The guest client's payment model is a CLOSED enum in @koala/sdk: PAYMENT_TYPES = credit_card, credit_card_token, cash, stored_value, billing_account, digital_wallet (plus a zod PAYMENT_METHODS enum adding 'prepaid'). POISON NAMED: 'billing_account' is NOT a house account - src/utils/payment.ts renders it as 'Account #<saved_account_id>' and the SDK's only account-payment route is /v1/ordering/me/stored-cards, i.e. an Olo-style saved card; stored_value renders 'Gift card'. /house.?account|charge.?account|corporate.?account/ = 0/875; /credit.?limit|invoice/ = 0/875 (the 'on account' hits are sign-in UI strings). So no house/on-account tender exists on Chowly's own ordering surface. Held unknown rather than no: Chowly is middleware with no store-level tender module (the 331st/332nd no-module merge rule), and catering on Olo-backed Koala tenants settles through Olo. Retrieved 2026-09-18. || 334th: 334th NEW (notes only): the partner order-injection API accepts a CLOSED tender enum: info.payment_type ENUM ['cash','credit'] (tip_payment_type likewise); no account/on-account/invoice tender exists on the path that injects third-party orders into the POS. Held unknown under the no-module rule (house accounts would be a POS tender), notes only. Source: https://api-docs.chowlyinc.com/toos/v2/ (Chowly's own OpenAPI 3.0.2 TOOS v2 spec, served anonymously; new this session) and/or chowly.help KB images. Retrieved 2026-09-18. adversarially verified

A single check can be settled with multiple tenders and split by seat, by item, by even shares, or by arbitrary amount, with no hard cap below eight ways.

payments-split-tender

A Chowly-owned product does settle one order with more than one tender: where the brand’s Olo configuration supports Split Tender, a Koala checkout guest pays part with a gift card and the balance with another form of payment. That falsifies a flat claim that tender handling belongs entirely to the underlying POS. Partial rather than yes: the documented case is two tenders only, it is Olo-gated and Enterprise-only, and nothing in the corpus describes splitting a check by seat, by item, by even shares or by arbitrary amount. https://chowly.help/s/article/Koala-Checkout-Configurations-Olo-Users-Only-Gift-Cards-Support · retrieved 2026-09-06 adversarially verified

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

payments-refund-void-controls

Chowly documents its refund control model positively and it is the opposite of role-based authorisation: a refund is issued by whoever holds the order-confirmation email, by clicking a link inside it — no login, no manager PIN, no recorded approver — and cancellation is gated the same way. The only stated limits are business rules rather than permissions: one refund per order, and only within 48 hours, after which the operator works in Stripe. Bounded: this is the only refund mechanism the corpus documents for a Chowly-operated ordering channel. https://chowly.help/s/article/Google-Direct-Order-Orders-Refunds · retrieved 2026-09-06 adversarially verified

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

payments-chargeback-tooling

Automated dispute management with a claimed 70-80% win rate, but these are third-party marketplace order disputes and refund claims, not card-network chargebacks. https://chowly.com/ · retrieved 2026-08-01

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

payments-card-on-file

Koala: Web Ordering Feature Set lists "Save and delete credit cards" under SSO + Loyalty, so a signed-in guest profile can retain a card for reuse in web and mobile ordering. Shortfall: the item sits inside the "For Olo Users Only: Add-On Features" block and the section is prefaced "Features may vary by integration partner (Punchh, Paytronix, Spendgo, etc.)", so availability is neither universal nor Chowly-owned; scope is the ordering account only, with no documented reuse for phone orders or at an in-store register (Chowly runs no POS); and no article in the corpus states that the vault is tokenized or addresses PAN storage - the string "tokeniz" does not occur anywhere in the 115 articles. Digital wallets are a separate, Square-provided surface (Koala-Square-Menu-Partners-Adding-Digital-Wallets: Google Pay and Apple Pay, both requiring Square as the payment provider). read via the site's Salesforce Aura record endpoint (RecordServiceComponentController.getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c); the HTML at this URL is the site's CSS-error SPA shell. https://chowly.help/s/article/Koala-Web-Ordering-Feature-Set · retrieved 2026-08-08

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

payments-payout-timing

Chowly never holds merchant funds; settlement is via the operator's own processor. https://chowly.com/solutions/branded-online-ordering/ · retrieved 2026-08-01

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

payments-multi-entity-routing

331st: MOVED unknown -> partial (B). CLAIM: one account routes settlement to different bank accounts per location or legal entity (separate MIDs or split settlement) under unified reporting. VERDICT: partial, for Chowly's own first-party payment channels only (Chowly Online Ordering 'COO' and Google Direct Order 'GFO'). EVIDENCE (the full 583-article chowly.help Salesforce knowledge census on disk from the 324th, re-grepped per cell; three KB screenshots read at full resolution): (1) Settlement is a per-LOCATION connected-account model, not a pooled one. 'December 2021: Chowly Changes' (https://chowly.help/s/article/December-2021-Chowly-Changes, still published): '[Google - Stripe] Refunds Issue: By collecting payments on the Direct Order Stripe account and using transfers to move the funds to the connected accounts caused refunds to not work as expected. Solution: Chowly has switched to using Direct Charges when the location has onboarded their Stripe account.' (2) The payment provider is a per-location record with its own account id. 'Using Square for Payments' (https://chowly.help/s/article/Using-Square-for-Payments, published 2025-03-07): 'If the location does not pass the readiness check in Plaunch...'; 'Deleting a Payment Provider will disable the COO Order Platform'; its screenshot (rtaImage refid 0EMPq000006HQc9, read as an image) shows a 'Payment Provider Settings' panel with 'Payment Provider: Stripe', an 'Account ID' field and 'Provider Onboarding: Onboarding Completed'; refid 0EMPq000006HQlp shows the same panel creating a 'Square' provider. Each location onboards through its own link: 'You can only follow these steps after a Chowly employee has provided you with a unique, one-time URL' and 'Input Bank Account Information - This account is where money from transactions will be received' (https://chowly.help/s/article/creating-a-stripe-account-for-chowly); 'You can have multiple Stripe accounts under the same email address. Each account will have its own dashboard' (FAQ-Stripe-Account-and-Payments). (3) Unified reporting across locations: the chowly.app Restaurant Control Center source maps (958 sources, 325th census) render features/order-managment/OrderManagement.tsx with a MultiLocationDropdown whose selected ids are sent as 'partnerIds', and OrderDetailsDrawer.tsx exposes a Stripe refund for 'PlatformName.COO && paymentProvider === PaymentProvider.stripe' orders (PaymentProvider enum: square | stripe | valutec). SHORTFALL (why not yes): only COO/GFO money moves through Chowly; marketplace (DoorDash, Uber Eats, Grubhub) payouts settle through each marketplace, and Toast/Square-POS merchants settle through their own POS processor. The per-location routing is shown by architecture (Stripe Connect connected accounts, per-location provider records set in Chowly's internal Plaunch tool), not by an operator-facing setting to assign bank accounts to locations or entities; and the Stripe setup article advises 'For restaurant owners with multiple locations, it is best practice to choose a primary/headquarter address to use for this account', so a shared account across locations is also a documented path. The per-location routing sentence is from a 2021 release note. Retrieved 2026-09-18. https://chowly.help/s/article/Using-Square-for-Payments · retrieved 2026-09-18 adversarially verified

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

payments-p2pe-pci4

2026-09-03 re-sweep (195th): the full chowly.help corpus (204 slugs via Aura) and 86 chowly.com pages were re-read; an analyst proposed partial from https://chowly.com/diner-privacy-policy/ and the adversarial pass returned it to unknown: Quote confirmed verbatim at chowly-com/diner-privacy-policy.txt:54, URL matches. But the claim asks for point-to-point encryption and a current PCI DSS 4.x AoC / P2PE listing available on request. The sentence is a generic transmission-security statement ('TLS 1.2 ... consistent and up-to-date with PCI Data Security Standards'); it names no attestation, SAQ, version, P2PE validation or request route. Corpus grep for 'PCI|P2PE|attestation|AoC|SOC 2|point-to-point' returns only this line and Koala-iOS-Kiosk-App-Deployment-Kiosk-Kickoff-Requirements.txt:17 naming 'PCI Proxy' as a partner account manager - a third-party broker on the Square-powered kiosk path, not Chowly's artefact. Neither limb of the claim is present; a privacy-policy boilerplate line is not a present half. Unknown, not partial (and not no: Chowly may hold an AoC as a service provider and simply not publish it). Prior rationale: 2026-08-08 re-sweep. Rebuilt the chowly.help corpus independently rather than trusting the sitemap: POST /s/sfsites/aura with RecordServiceComponentController.getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c, seeded from /s/sitemap-topicarticle-1.xml (114 slugs) and crawled to fixpoint over every chowly.help/s/article/ href inside the retrieved bodies - 204 slugs reached, 195 with live bodies, 9 dead (getArticleVersionId returns null and the URL 404s, including Smart-Pricing-Overview and Delivery-Search, both linked from live articles). Searched every body for PCI, P2PE, AoC, attestation, SOC 2, tokeniz and encryption. There is exactly one PCI hit and it is a new one for this record: Koala iOS Kiosk App Deployment: Kiosk Kickoff Requirements lists the partner reps a brand must supply access to as "your account managers at Olo, Square, Punchh, and PCI Proxy" - naming PCI Proxy as a payment-data partner on the kiosk path - and "We partner closely with Square to power payment on our kiosks." That establishes a third-party card-data broker in the architecture, not an attestation. No compliance posture is published: the only availability document is Koala Incident Response Protocol (Datadog/OpsGenie, four SLA failure levels, post-mortems), and trust., security., docs. and status.chowly.com are all NXDOMAIN. Chowly sells no card-present terminal of its own, so a P2PE validation may be inapplicable rather than withheld. Nothing enumerates the vendor's compliance artefacts, so this is unresolved rather than absent. || 328th: NEW SURFACE: Chowly is not the processor and not the merchant of record on any tender. chowly.help states 'All other POS systems will use Stripe payment processing and should cancel/refund from the Restaurant Control Center (RCC)' (kA01K000000oa7BSAQ), 'Apple Pay ... seamlessly integrated through Stripe', 'Koala supports Olo Pay on Web and iOS. The Olo Pay UI leverages a Stripe iframe', and for Toast 'Toast is the merchant of record for payment processing. This means all chargeback notifications, dispute tools, and resolution proce[sses]' (kA0Pq0000003uQfKAI). Card entry is a hosted iframe ('PCI Proxy iFrame' on the Koala Checkout page, 8 release-note articles). Chowly sells no card-present terminal, so P2PE does not apply; P2PE 0/583 chowly.help, 0/958 chowly.app sources, 0/910 cms.koala.io sources, 0/167 chowly.com pages, and 'SOC 2' 0 in all four. The only PCI statement is a privacy-policy sentence about TLS 1.2 'consistent and up-to-date with PCI Data Security Standards' (https://chowly.com/diner-privacy-policy/) - not an AOC. Held unknown: the product lacks the module entirely. Retrieved 2026-09-18. || 332nd: 332nd NEW (notes only): Visa Global Registry of Service Providers queried through its own public lookup endpoint (https://www.visa.com/splisting/api/company?companyName=<name>, found in the registry SPA's main.js as fetchCompanyName): 'chowly' -> {"data":[]}, 'koala' -> {"data":[]}; known-positive control 'stripe' -> 8 Stripe entities incl. 'Stripe, LLC', so the lookup works. Chowly/Koala are not Visa-registered PCI DSS validated service providers; a registry is a floor, not a census (a merchant-level SAQ or a privately held AoC would not appear), so this does not carry a no. Retrieved 2026-09-18. adversarially verified

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

delivery-driver-roster

Positive evidence of absence via an affirmative equivalence statement, not a zero-hit. This is the only article in the 203-article help centre written about operators who run their own drivers, and it states that such an operator gets nothing extra from Chowly: a restaurant that "has its own delivery drivers has the same capabilities as one using a food ordering platform (such as DoorDash, Grubhub, or UberEats)". The entire self-delivery feature set it names is two settings - Chowly's "software allows restaurants to set a minimum order total or charge a delivery fee upon request" - and even that is not self-serve: "If you are a Chowly customer and interested in using your own delivery drivers, contact Chowly Support". The operator-facing surface is thin enough that future-order print timing is adjusted for you, since "Chowly employees can adjust buffer times for future orders". There is no driver entity, no clock-in/out, no assignment state and no per-driver run history; and the claim asks for these to be reportable from the POS itself, which Chowly is not - it injects tickets into someone else's POS. C2: LastPublishedDate 2023-08-18, the stale stratum, so weighed against the current product. Counter-evidence, disclosed and not quoted from this url: chowly.com/agents/delivery/ (2026) lists in-house among the Delivery Agent's driver pool alongside DoorDash, UberEats and Grubhub, and its activity log shows orders switched from a third-party courier to in-house. That is a per-order fulfilment choice, not a driver roster Chowly holds, and none of that page's six stated autopilot capabilities is driver management. Note also that the support-routing article When-to-contact-Chowly-vs-POS/3rd-Party Support was rejected as evidence for this cell: it routes general reporting and menu/hour updates to POS Support, both of which Chowly demonstrably ships in the Restaurant Control Center, so it is a triage list and its omissions prove nothing. https://chowly.help/s/article/FAQ-How-will-delivering-my-own-orders-affect-my-integration · retrieved 2026-09-05 adversarially verified

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

delivery-dispatch-board

A closed enumeration of the operator console's analytics surface plus an exhaustive column list for its order-level screen, which is the nearest thing Chowly ships to a dispatch board. The article names the console's reporting pages: "There are seven different reporting pages: Locations, Sales, Orders, Product Mix, Week over Week, Delivery Buydown, and Smart Pricing." The Orders page's Order Detail tile - "This tile shows specific data about each individual order received" - is enumerated column by column: LOCATION NAME, CUSTOMER NAME, SALES DATE, SUBTOTAL, TIP, SALES TAX, TOTAL, PLATFORM, ERROR OR CANCELLATION REASON, SERVICE TYPE and ORDER STATUS. There is no driver column, no assignment state, no elapsed-time clock and no run object to batch two orders onto. The two fulfilment-adjacent columns are shallow by the vendor's own definition: SERVICE TYPE "Indicates whether the order was picked-up or delivered" and ORDER STATUS "Indicates if an order was processed successfully", where the states are POS-injection states (finalized / posted), not dispatch states. Scope limit stated honestly: this enumeration closes the analytics surface, not the whole console; the console's other documented surfaces per Navigating the Restaurant Control Center are the Home page and Store Settings, whose documented content is hours, menu resync, item suspension and platform pausing. Corroborating, not quoted from this url: chowly.com/agents/delivery/ (2026) answers whether the operator has to manage anything with No, choosing a courier per single order with no human dispatcher and no multi-order run. LastPublishedDate 2024-02-23. https://chowly.help/s/article/Orders-Reporting-Page-on-the-Restaurant-Control-Center · retrieved 2026-09-05 adversarially verified

Dispatch includes a live map view with geocoded stops and system-generated route sequencing (turn order optimization) for a multi-stop run, not just a static address list. differentiator

delivery-route-map

2026-08-08 re-sweep. Rebuilt the chowly.help corpus independently rather than trusting the sitemap: POST /s/sfsites/aura with RecordServiceComponentController.getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c, seeded from /s/sitemap-topicarticle-1.xml (114 slugs) and crawled to fixpoint over every chowly.help/s/article/ href inside the retrieved bodies - 204 slugs reached, 195 with live bodies, 9 dead (getArticleVersionId returns null and the URL 404s, including Smart-Pricing-Overview and Delivery-Search, both linked from live articles). The only map surfaces documented anywhere are guest-facing store locators, both now read in full: Koala Location Configurations: Standard Search ("Our default search radius is 10 miles", geolocation then IP then View All Locations, guest may "search using the view frame of the map") and Koala Location Configurations: Delivery Search (a delivery tab with an address field and "Google Autocomplete", requiring "the Places API ... enabled for the Google Maps API key associated with your Koala account"). Both find a store for a guest; neither plots delivery stops. No article in the 195 bodies describes a dispatch map, geocoded stop list, turn-order optimization or multi-stop run sequencing, and no delivery or dispatch component exists among the 45 in chowly.statuspage.io/api/v2/components.json. The vendor's Delivery Agent page (chowly.com/agents/delivery/, "Knows which driver, which platform, which route saves you the most") is grade D and cannot carry a differentiator verdict. Because Chowly documents no dispatch back office at all there is no enumeration to argue absence from. Unresolved. || 328th: NEW SURFACE: Chowly's delivery is courier AGGREGATION, not own-driver dispatch. The Restaurant Control Center ships a Nash integration ('DEFAULT_NAME: "Nash Dispatch Service"' in DispatchSettings.tsx, and NashDeliverySettings.tsx 'Chowly will add a request to the driver in the pickup instructions for this Partner. This is a request only and may not be enforced by all providers'), matching the Terms' vendor list 'Nash Technologies Inc. (delivery courier service)' (https://chowly.com/terms-and-conditions/, updated 2026-01-13); the partner alternative is VROMO, which 'aggregates drivers from multiple companies, finding the closest and most cost-efficient driver'. There is no dispatch board: 'optimiz' 0/583 chowly.help, 0/958 chowly.app RCC source-map sources, 0/910 cms.koala.io sources, 0/167 chowly.com pages; 'turn-by-turn' 0 in all four; 'multi-stop' 0 in all four. Positive control: 'dispatch' 18/583 and 17/958, all courier-handoff or React `Dispatch<SetStateAction>`. Held unknown - the module does not exist in the product. Retrieved 2026-09-18. || 334th: 334th NEW (notes only): KB screenshots read at full resolution (chowly.help Using-Nash-with-Chowly refid 0EMPq00000JRNaH and Chowly-Platform-Operator-Guide refid 0EMPq00000Ow1M5): the RCC order drawer's 'DELIVERY ACTIVITY' panel is a timestamped status TIMELINE fed by the courier (Created (Sent To Provider), Not Assigned Driver, Assigned Driver, Driver Updated <name>, Pickup Enroute/Arrived/Complete, Dropoff Enroute/Arrived/Complete) - no map, no stop list, no sequencing. Consistent with the 328th finding (courier aggregation via Nash, not own-driver dispatch). Held, notes only. Source: https://api-docs.chowlyinc.com/toos/v2/ (Chowly's own OpenAPI 3.0.2 TOOS v2 spec, served anonymously; new this session) and/or chowly.help KB images. Retrieved 2026-09-18. adversarially verified

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

delivery-driver-tracking

The vendor states affirmatively what its dispatch tracking is, and it is an inbound event stream rather than GPS: "Koala has integrated with the DispatchStatusUpdate Olo self-service webhook to support dispatch order tracking.This webhook allows Koala to subscribe to near real-time status updates for dispatch orders, including updated estimated delivery times." The enablement procedure is entirely on the upstream platform's side - find the Koala webhook in Olo's self-service webhook dashboard and enable DispatchStatusUpdate for the brand - so Chowly is a consumer of someone else's courier telemetry, not a producer of it. Scope limit, which the prior draft did not state: this article is written for Koala Enterprise customers on Olo, so on its own it closes only that path. What carries the claim beyond it is that both objects the claim requires are absent from the product: there is no driver-facing mobile application to emit a position - Chowly's app product is the branded consumer ordering and loyalty app documented at chowly.com/solutions/mobile-app/ - and no dispatch screen to surface one to (see delivery-dispatch-board). C2: LastPublishedDate 2023-11-15, the Koala stratum where the staleness discount bites hardest; checked against the 2026 delivery page, which still describes courier supply as a pool across DoorDash, UberEats, Grubhub and in-house and documents no driver app. https://chowly.help/s/article/Koala-Olo-Menu-Partners-Dispatch-Tracking-Webhooks · retrieved 2026-09-05 adversarially verified

Delivery areas can be defined as arbitrary map polygons or by drive-time isochrones, not solely as a radius or a ZIP/postcode list. differentiator

delivery-zones-polygon

325th: MOVED unknown -> yes (B). NEW SURFACE: chowly.app, the Restaurant Control Center, ships PUBLIC source maps. /asset-manifest.json lists exactly three JS files and all three .map files; /static/js/main.54b02cd0.js.map is 6,180,398 bytes and begins {"version":3, while the nonsense control /static/js/main.54b02cd0.js.NONSENSE.map 404s and /zzz-nope.js.map returns the 867-byte SPA shell, so the map is real. Extracted 1,050 first-party sources (4.75 MB; 830 .ts/.tsx) from all three maps - a complete map set with no unmapped chunk. CLAIM: delivery areas definable as arbitrary map polygons or drive-time isochrones, not solely a radius or ZIP list. VERDICT: yes for Chowly Online Ordering. EVIDENCE: features/manage-locations/DeliveryArea/DeliveryArea.tsx renders two tabs, 'Circular Area' and 'Polygon Area'; the polygon instructions read 'Start drawing - Click anywhere in the map and keep clicking until all the desired points have been added to the polygon.', 'Save drawing - Press the C key to close the polygon.', 'Cancel drawing - Press Escape key.'; save is gated on `isPolygonClosed && polygonPoints.length >= 3` and the vertices are clicked freely on a Google Map (handleMapClick pushes each e.latLng). The area persists through POST/PATCH /api/v3/delivery_areas with a GeoJSON body built by utils.ts buildGeoJSON: {type:'FeatureCollection', features:[{geometry:{type:'Polygon',coordinates:[...]}, properties:{deliveryType}}]}; the same file states 'The backend stores all shapes as polygons in GeoJSON format, so circles must be converted to a many-sided polygon' (64-point ring), and parseGeoJSON round-trips deliveryType 'polygon' vs 'circle'. It is wired to the live product, not dead code: ManagePlatform.tsx line 738 renders `{isCOO && locationIdFromPartner && (<DeliveryArea partnerId={...} partnerCity={...} partnerLatitude={...} />)}` (isCOO = Chowly Online Ordering), and the shipped bundle main.54b02cd0.js contains the strings 'Polygon Area' and 'Set Delivery Area'. A radius circle is the ALTERNATIVE tab, so the product is not radius-only; no drive-time isochrone exists, which the claim does not require (disjunction). Grade B: the vendor's own shipped production code, not published documentation. Retrieved 2026-09-17. https://chowly.app/static/js/main.54b02cd0.js.map · retrieved 2026-09-17 adversarially verified

Each delivery zone carries its own independently configurable delivery fee, order minimum, and quoted promise time, applied automatically from the validated customer address.

delivery-zone-pricing

FAQ - How will delivering my own orders affect my integration?: "Chowly's software allows restaurants to set a minimum order total or charge a delivery fee upon request" for restaurants running their own drivers - so two of the claim's three attributes exist somewhere in the product. Shortfall: both are set "upon request" by contacting Chowly Support rather than by the operator, the article ties neither to a zone, and no article in the 115-article help centre describes multiple zones each carrying its own independently configurable fee and minimum. The third attribute, a per-zone quoted promise time, is not configurable at all: the only time control documented for delivery is a Chowly-set ticket print buffer for future orders. Zone setup itself remains a Chowly onboarding task per Thrive POS's integration guide, with no published zone editor and no automatic application from a validated address. read via the site's Salesforce Aura record endpoint (RecordServiceComponentController.getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c); the HTML at this URL is the site's CSS-error SPA shell. https://chowly.help/s/article/FAQ-How-will-delivering-my-own-orders-affect-my-integration · retrieved 2026-08-08

Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.

delivery-address-validation

Koala Location Configurations: Delivery Search documents both halves of the claim. Geocoding against a mapping service: 'Delivery Search also includes Google Autocomplete functionality, which assists the user in entering a valid and complete address', and 'Prior to configuring delivery search, please ensure the Places API is enabled for the Google Maps API key associated with your Koala account'. Out-of-zone rejection before acceptance: the feature 'prevents a user who intends to order delivery from finding a store that (1) doesn't offer delivery or (2) doesn't include the guest's address in its delivery range', and the configurable strings include a 'Delivery Search No Results Text' - 'surfaced when the store validation algorithm does not return an eligible store. This means there is no location that is within range of the user's provided address and delivers to the user's provided address' - with an 'Address Out Of Range Toast Title' on iOS. Configured in Brand CMS at Ordering Config > Web Config > Locations ('Delivery Search' toggle) and Mobile iOS > Config > Flows > Location > Features ('Supports Delivery'). Caveats short of a downgrade: the toggle is disabled by default, the Google Maps key is the brand's own, the underlying delivery range comes from the menu provider (Olo), and on the third-party marketplace path the address arrives already validated by the marketplace. Read via the Salesforce Aura record endpoint; the HTML at this URL is the site's CSS-error SPA shell. https://chowly.help/s/article/Koala-Location-Configurations-Delivery-Search · retrieved 2026-08-08 adversarially verified

Tracks per-delivery driver compensation inputs — mileage or distance driven per run, per-delivery flat reimbursement, and driver-retained tips — and exports them to payroll as separate reimbursement vs. wage lines. differentiator

delivery-driver-comp

The one article addressing self-delivery operators enumerates what Chowly gives them and it contains no compensation object: Chowly's "software allows restaurants to set a minimum order total or charge a delivery fee upon request", and the operator with "its own delivery drivers has the same capabilities as one using a food ordering platform (such as DoorDash, Grubhub, or UberEats)" - i.e. an order injected into the POS. A delivery fee is money the diner pays the restaurant, not a mileage rate, a per-run reimbursement or a driver-retained tip allocation, and there is no payroll export because there is no payroll product: Chowly's 2026 platform line is marketing site, online ordering, Google Business Profile, Google Ads, third-party integration, email marketing, mobile app, dynamic pricing, surveys and loyalty. The operator does not even hold the timing controls - "Chowly employees can adjust buffer times for future orders". Corroborating, not quoted from this url: the support-routing article assigns tip distribution to the POS vendor, which is a positive instruction rather than an omission; that single line is the only part of that article this cell relies on, because its omissions are unreliable (it also routes reporting and menu/hour updates away from Chowly, both of which the Restaurant Control Center ships). C2: LastPublishedDate 2023-08-18; nothing in the 2026 Delivery Agent material introduces a driver-compensation object. https://chowly.help/s/article/FAQ-How-will-delivering-my-own-orders-affect-my-integration · retrieved 2026-09-05 adversarially verified

Provides a driver cash bank / settle-up flow that reconciles cash collected, orders assigned, and tips owed at end of shift, producing a per-driver over/short figure.

delivery-cash-reconcile

The Restaurant Terms, updated January 2026, allocate the entire delivery function away from Chowly to the Delivery Partner, and the Diner Terms repeat the allocation to the guest. A driver cash bank, an end-of-shift settle-up and a per-driver over/short figure are delivery-fulfilment functions this contract assigns to a third party. Consistent with that, Chowly’s own channels carry no cash tender: the Diner Terms route all payments to the merchant’s payment processor against a designated payment method. https://chowly.com/terms-and-conditions/ · retrieved 2026-09-06 adversarially verified

Can hand a first-party order to an on-demand courier marketplace (DoorDash Drive, Uber Direct, Nash, Relay or equivalent) natively from the POS, with the courier quote and status returning into the order record.

delivery-daas-dispatch

Kept at partial, not upgraded and not zeroed. Verified verbatim on the Delivery Agent page: "AI-driven driver selection per order", "Best Driver Selected — Cheapest + fastest option chosen for every single order", "Typically $1-4 per delivery". Shipped-product framing with a live log, but zero courier APIs named and no operator-configurable dispatch logic documented. Claim-level. https://chowly.com/agents/delivery/ · retrieved 2026-08-01 adversarially verified

Supports hybrid dispatch: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. differentiator

delivery-daas-fallback

Quote: "Driver Availability Real-time pool across DoorDash, UberEats, Grubhub, in-house | → Best Driver Selected Cheapest + fastest option chosen for every single order | ✓ AI-driven driver selection per order" Differentiator with C-grade presence evidence, so partial per the brief. Chowly does operate a courier option: the T&C (grade B) says 'Restaurant may elect to utilize a courier service that deliver orders through a network of delivery partners' and lists 'Nash Technologies Inc. (delivery courier service)' as a subprocessor. The Delivery Agent page markets per-order automatic selection between in-house and third-party drivers on cost and speed, and the automation blog (D) says 'Orders automatically dispatch to the best available driver from your delivery network. Fastest, cheapest option chosen automatically based on real-time availability and routing.' Shortfall: no help-centre article documents the routing, no operator-configurable overflow rules (no-driver-available, out-of-zone, wait threshold) are described anywhere, the T&C frames the courier as an election rather than an automatic fallback, and the only documented delivery handoffs in the Koala docs are Olo-mediated. Marketing describes hybrid dispatch; nothing documents its configuration. https://chowly.com/agents/delivery/ · retrieved 2026-09-03 adversarially verified

Offers direct, first-party certified API integrations with DoorDash, Uber Eats, and Grubhub marketplaces (vendor-owned, not solely resold through Otter/Deliverect/Chowly/ItsaCheckmate middleware). differentiator

delivery-3p-direct-integration

Chowly is itself the certified integrator - direct connections to DoorDash, Uber Eats, Grubhub, Postmates, ezCater, and a named DoorDash Preferred Integration Partner for 2026. Scored on substance: direct certified integrations with no middleware beneath it. Note Chowly IS the middleware in other vendors' stacks. https://chowly.com/partnerships/ · retrieved 2026-08-01

Third-party marketplace orders inject automatically into the POS as normal tickets that fire to KDS/printers without tablet re-keying or manual accept.

delivery-3p-injection

Strongest cell in the dossier and it survives adversarial review on third-party evidence, not marketing: DoorDash's own developer docs require and verify order injection quality (sub-1% failure/cancel on rolling 28-day data, 250+ live stores) and DoorDash's newsroom names Chowly in the 2026 cohort. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-01 adversarially verified

Menu, pricing, modifiers, and photos publish from the POS master menu out to connected third-party marketplaces, including channel-specific price markups, without maintaining a separate menu in each portal.

delivery-menu-push

One POS menu edit propagates to all 150+ channels; per-channel and per-location up-charge percentages are configurable in the Control Center. https://chowly.com/solutions/restaurant-control-center/ · retrieved 2026-08-01

Marking an item or modifier 86'd in the POS pushes item-level out-of-stock status to connected third-party channels in near real time, and restores it on availability (DoorDash requires item and item-option 86ing of new POS partners).

delivery-86-sync

Re-evidenced 2026-08-09 after the original citation (merchants.doordash.com/en-us/preferred-integrations) was retired; the successor page renders its partner roster client-side, so the named-partner enumeration is no longer server-retrievable there and that leg is withdrawn. Two live sources carry the cell instead. DoorDash's DPIP developer page enumerates the required high-quality-integration features - "Self-serve integration onboarding (SSIO)", "Activation within SSIO", "Menu pull", "86 items", "Order Ready Signal", "Item Polling", "Integrated Promotions", "Detailed Error Reporting" - plus the gates "Order failure rate below 1%", "Merchant cancel rate below 1%" and "Support at least 250 DoorDash stores"; the 86ing reference requires partners to "Call the respective endpoints in real time when a user marks item(s) and/or item option(s) out of stock via your UI (e.g. POS or tablet)", with is_active false for unavailability and true for restocking - i.e. the restore half is part of the certified behaviour. DoorDash's own newsroom still names the 2026 cohort and Chowly is in it (Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper). Chowly's own page corroborates the operator-facing behaviour - "86 it in your POS and it disappears from every delivery app instantly" and "86'd ingredients sync across all 150+ channels in real time" - but that is marketing and is not what the cell rests on. Known limit, from Chowly's help centre: 86ing and menu publishing from the Restaurant Control Center are throttled to 15-minute increments; that is a repeat-action rate limit, not the propagation latency of a single 86. https://developer.doordash.com/en-US/docs/marketplace/overview/getting_started/preferred_integrations_new/ · retrieved 2026-08-09 adversarially verified

Store can be paused/deactivated on each connected third-party marketplace from inside the POS with a timed auto-reactivation, rather than only from each marketplace's own tablet or portal.

delivery-store-pause

Control Center pauses delivery platforms by location; Delivery Agent additionally auto-pauses on prep-time thresholds and adjusts marketplace hours. Explicit timed auto-reactivation is not separately documented. https://chowly.com/solutions/restaurant-control-center/ · retrieved 2026-08-01

Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. differentiator

delivery-3p-reconciliation

Control Center reports sales by delivery platform and location plus automated marketplace dispute management. Matching payout deposits to POS-recorded 3P sales with commission and marketing-fee itemization and missing-order detection is not documented. https://chowly.com/solutions/restaurant-control-center/ · retrieved 2026-08-01

Vendor exposes integration health to the operator — failed/rejected order injections, connection status per channel, and alerts on failure — rather than failing silently. differentiator

delivery-injection-error-visibility

The only supporting text is "Cancellation and error tracking surfaces errors and roadblocks early" — marketing prose with no documented failed-order queue, retry/replay mechanism, per-order error detail, or alerting. The dossier's own review evidence (errors unnoticed for weeks) argues against a full yes. https://chowly.com/solutions/restaurant-control-center/ · retrieved 2026-08-01 adversarially verified

Guests receive a branded order status / driver tracking page or SMS link on the restaurant's own domain for first-party delivery orders, driven by real order and driver state.

delivery-tracking-page

Koala Olo Menu Partners: Dispatch Tracking Webhooks: Koala "has integrated with the DispatchStatusUpdate Olo self-service webhook to support dispatch order tracking. This webhook allows Koala to subscribe to near real-time status updates for dispatch orders, including updated estimated delivery times." That state drives the brand's own Koala-built web and mobile ordering experience, which is deployed on the brand's domain and app-store identity (Koala-Web-Ordering-App-Deployment-Redirecting-and-Launching-Your-App). Shortfall: it is an Olo-only add-on that the brand must enable itself in Olo's self-service webhook dashboard and then flag to its Koala CSM; it covers Olo Dispatch courier orders rather than the restaurant's own drivers; the state carried is order status and ETA, not driver position; and no SMS tracking link is documented anywhere in the 115-article help centre. read via the site's Salesforce Aura record endpoint (RecordServiceComponentController.getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c); the HTML at this URL is the site's CSS-error SPA shell. https://chowly.help/s/article/Koala-Olo-Menu-Partners-Dispatch-Tracking-Webhooks · retrieved 2026-08-08

Quoted delivery promise times adjust dynamically from current kitchen load, driver availability, and zone drive time, rather than a fixed per-store constant. differentiator

delivery-promise-time

327th: MOVED unknown -> partial (B). NEW EVIDENCE from two surfaces the 2026-08-08 note predates. (1) The 583-article chowly.help census (Salesforce Knowledge REST, 100% of the publisher's manifest) holds 'Order Throttling in Chowly Online Ordering' (modified 2025-01-30), which the 204-body corpus did not: 'Chowly Online Ordering offers a dynamic order throttling system... This system allows restaurants to manage order flow during peak hours... setting thresholds that adjust preparation times based on the order subtotal... In the Order Throttling section, you can add different tiers by setting a range of order subtotals and assigning corresponding prep times... If the subtotal reaches a threshold set in one of the RCC-configured tiers, the system automatically adjusts the preparation time. The diner receives a notification directly in their cart or at checkout, informing them of the new expected preparation time.' The chowly.app RCC source-map census corroborates the shipped screen: components/OrderThrottling/OrderThrottleEditor.tsx and OrderThrottleToggle.tsx, and PrepTimeShortcut.tsx. (2) chowly.com was rebuilt as a Next.js site since the last pass; all 167 URLs in its sitemap were fetched today (none a soft-404: the 404 shell is 7,758 bytes, every page >10 KB). https://chowly.com/agents/delivery/ states the Delivery Agent 'watches four data sources continuously': 'Driver Availability - Real-time pool across DoorDash, UberEats, Grubhub, in-house', 'Prep Times + Order Volume - Your kitchen pace vs. inbound order load', 'Customer Distance + ETA', 'Delivery Cost per Order'. WHY PARTIAL, NOT YES: the quoted time does move dynamically rather than being a fixed per-store constant, which is the claim's contrast, and kitchen load is an input. But the RCC mechanism keys the adjustment to CART SUBTOTAL via an operator-authored tier table, not to live kitchen state; the Delivery Agent's three other inputs drive driver selection and platform auto-pause ('Paused UberEats - prep time hit 28 minutes'), not the quoted promise; and the base Prep Times screen is an operator-set constant in 15-minute increments per platform, which 'Prep Times Settings in the Restaurant Control Center' says DoorDash, GrubHub and Uber Eats ignore in favour of their own algorithms. No document ties the quote to zone drive time. Retrieved 2026-09-18. https://chowly.help/s/article/Order-Throttling-in-Chowly-Online-Ordering · retrieved 2026-09-18 adversarially verified

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

delivery-offline-behavior

327th: MOVED unknown -> no (B). A publication claim, settled against four censuses (583 chowly.help articles = 100% of the Salesforce Knowledge manifest; 958 chowly.app RCC sources from the complete /asset-manifest.json map set; 910 cms.koala.io sources; all 167 pages of the rebuilt chowly.com sitemap, none a soft-404). CONTROL /\boffline\b/i = 1/583, 3/958, 0/910, 6/167 and none concerns delivery - the KB hit is an Olo vendor going offline, the RCC hits are browser online/offline events, and all six site hits are SEO-blog 'offline marketing' poison. Nothing states what happens to cash delivery orders, driver assignment or driver settlement during an outage. POSITIVELY, the vendor has published why: Chowly runs no fleet and no driver settlement of its own. 'Using Nash with Chowly' (modified 2026-05-05, in the 583 but not in the older 204-body corpus) says 'Nash is a Delivery Aggregator (Not Delivery Fleet)... They provide these services programmatically through the Nash API' and 'While Nash delivery settings cannot be controlled or changed via the RCC, this offers a view of the delivery status and settings'; 'What is Delivery as a Service?' names the three providers (Relay, Nash, Vromo). The 2026-01-13 Terms and Conditions makes it contractual: 'Restaurant may elect to utilize a courier service that deliver orders through a network of delivery partners (the "Delivery Partners"). Restaurant understands and agrees that Delivery Partner, not Chowly, is responsible for all order fulfillment, delivery and related support matters', and its subprocessor list names 'Nash Technologies Inc. (delivery courier service)'. Retrieved 2026-09-18. https://chowly.com/terms-and-conditions/ · retrieved 2026-09-18 adversarially verified

Vendor ships a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission.

digital-first-party-web

Branded commission-free ordering on the restaurant's own domain - "0% commission vs 15-30% on the delivery apps" - with orders firing into the POS and payment settling through the operator's own processor. https://chowly.com/solutions/branded-online-ordering/ · retrieved 2026-08-01

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

digital-menu-single-source

Same POS menu record drives first-party ordering, mobile app, and all connected marketplaces; one edit propagates everywhere. https://chowly.com/solutions/3rd-party-marketplace-integration/ · retrieved 2026-08-01

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

digital-native-app

Deployment guide: 'Each brand will need to own their own Apple Developer Account to ensure that Apple T&Cs are adhered to... because of the whitelabel nature of the Koala iOS application' and 'we will upload ipa's and publish off of the client's Apple Developer Account.' The Android Brand Assets guide specifies a per-brand app icon (48x48 to 1024x1024) and splash screen with 'Play Store Assets... to be uploaded by customer.' Confirms a restaurant-branded native iOS and Android app in the brand's own App Store Connect / Play Store accounts, not a shared Chowly marketplace app. https://chowly.help/s/article/Koala-iOS-Mobile-App-Deployment-Setting-Up-Your-First-Koala-iOS-Mobile-Application · retrieved 2026-08-06

Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels.

digital-account-saved-payment

Order history saved with one-click rapid reorder; Apple Pay and Google Pay wallet checkout. Saved addresses and tokenized saved cards are not explicitly documented. https://chowly.com/solutions/branded-online-ordering/ · retrieved 2026-08-01

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

digital-upsell-engine

Upsell Agent surfaces AI suggestions from order patterns at checkout. No attach-rate reporting documented, and it is explicitly non-configurable ("without restaurant configuration"). https://chowly.com/agents/upsell/ · retrieved 2026-08-01

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

digital-scheduled-pacing

Koala Web Ordering Feature Set enumerates 'Future ordering' under 'For Olo Users Only: Add-On Features > Checkout', alongside a time selector where 'If selected, ASAP will be an available option in the time selector at checkout'; the 3rd-party side documents future orders too ('Future Ordering is available for Google Food Ordering users'). Shortfalls: scheduled ordering on the first-party channel is an Olo-only add-on rather than a native capability; nothing in the 196-article chowly.help knowledge base documents per-daypart or per-slot capacity limits, order/item caps or automatic slot closure when the kitchen saturates; and on the 3P side 'Chowly's integration software cannot print future ordering details on ordering tickets', with buffer times adjustable only by Chowly staff. https://chowly.help/s/article/Koala-Web-Ordering-Feature-Set · retrieved 2026-08-08

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

digital-fulfillment-modes

Koala Web Ordering Feature Set, Checkout section: 'Choose fulfillment method (Dispatch Delivery, Self-Delivery, Curbside, Dine In, Pickup, Table Tents)'. Curbside has its own configuration article (Olo must expose Make, Model and Color custom fields; Koala surfaces In Store CTA / Curbside CTA / Curbside Helper Text / Pickup Instructions strings) and Dine In has one (Olo custom field named exactly 'Table Number'). Shortfalls: the entire fulfillment-method set sits under 'For Olo Users Only: Add-On Features', so it is unavailable to Square-menu or non-Olo brands; curbside captures vehicle make/model/colour at checkout but no guest arrival check-in is documented; and the only mode-specific setting in the Brand CMS is tipping ('Brands may configure different tipping options for Pickup vs Delivery') - no mode-specific fees and no per-mode prep timing. https://chowly.help/s/article/Koala-Web-Ordering-Feature-Set · retrieved 2026-08-08

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

digital-qr-table

Koala Checkout Configurations (Olo Users Only): Dine In Handoff Mode documents an at-table ordering mode - 'Ensure Dine In is enabled on all relevant locations in Olo... If you are using Table Numbers, you will need to have Olo add a custom field called "Table Number"... the Koala field supports alphanumeric values' - and the Web Ordering Feature Set lists 'Table Tents' among the fulfillment methods; tipping is configurable per handoff mode. Shortfalls: nothing in the 196 retrieved chowly.help articles describes a guest-facing QR scan, a scan-to-pay flow, or attaching to an existing open POS check - a dine-in order is injected as a new order; and check splitting is not supported (the only split documented is split tender across a gift card and one other tender, and only when Olo enables it). Feature availability is also Olo-add-on-only. https://chowly.help/s/article/Koala-Checkout-Configurations-Olo-Users-Only-Dine-In-Handoff-Mode · retrieved 2026-08-08

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

digital-kiosk

No kiosk appears in the ten published solutions, the agents list, or the sitemap. https://chowly.com/chowly-platform/ · retrieved 2026-08-01

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

digital-group-ordering

A closed enumeration carrying an explicit closure clause, the form C1 permits: "If there's a feature not on the list that you're interested in, reach out to your customer success manager to find out when it might become available!" - what is not listed is not available. The index runs Core Experience (Find a Location, Sign In/Sign Up, Navigate the Menu, View Basket & Checkout), Koala Customizations (Templates & Styling, Menu Category Navigation Types, Features, Tracking) and a section headed "For Olo Users Only: Add-On Features" covering Menu, Checkout and SSO + Loyalty. Nowhere in it is there a shareable participant link, a per-person or total spend cap, or split payment; checkout offers "Support guest checkout", "Choose fulfillment method" and tipping. The nearest listed feature is the menu-section item "assign item recipients", which labels items inside one guest's single basket - not a multi-participant link, and it carries neither cap nor split tender. Correction to the prior draft: the checkout enumeration sits under the Olo-only add-on section, not under the core checkout, so it closes less than was claimed. C2: LastPublishedDate 2023-11-07, the stale Koala stratum; checked against the current product, and chowly.com/solutions/branded-online-ordering/ (2026) lists six key features - own domain, commission-free ordering, Apple Pay and Google Pay, rapid reorder, native POS integration, loyalty and email capture - with no group-order link either. https://chowly.help/s/article/Koala-Web-Ordering-Feature-Set · retrieved 2026-09-05 adversarially verified

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

digital-catering-portal

A stated alternative rather than an absence, which is why this cell is cited here rather than to a feature list. This article "explains the different location settings" in Koala's CMS and documents the one field in the product that mentions catering at all - a Delivery Order URL that creates a secondary call-to-action on a location card, where "The standard use case is to provide a unique URL for delivery or catering". Chowly's documented handling of catering is therefore a link that sends the guest out of the product; there is no catering flow inside it. Corroborating, not quoted from this url: the Koala Web Ordering Feature Set, whose closure clause tells the reader that anything not listed is unavailable, lists no catering menu or order minimum, no lead-time rule, no quote or proposal, no deposit and no invoice, house-account or ACH term - its checkout is retail card-and-wallet only, with future ordering being scheduling rather than a catering flow. The ezCater tie named on chowly.com/partnerships/ is an inbound marketplace order feed into the POS, the same shape as DoorDash or Grubhub, and is not a Chowly-owned catering portal, which is why the prior adversarial pass rejected it as a partial. C2: LastPublishedDate 2023-11-14; the 2026 branded-ordering page adds no catering flow. https://chowly.help/s/article/Koala-General-Configurations-Managing-Locations · retrieved 2026-09-05 adversarially verified

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

digital-voice-ai-phone

Not among the eight published AI agents, and no certified voice partner is named. https://chowly.com/agents/ · retrieved 2026-08-01

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

digital-drivethru-ai

Chowly’s AI product line is a counted roster — the agents index says "Eight agents. One restaurant." and names all eight, none of which takes an order by voice — and the only drive-thru in a Chowly product is a Koala handoff-mode label on the cart and checkout screens. But a count of the branded agent line closes that line, not the category. Chowly ships whole products its marketing site never mentions, most clearly the Koala iOS Kiosk, which has roughly thirty knowledge-base articles and no marketing page at all, so the 167-page marketing census cannot bound what Chowly sells. A voice-ordering product page or article would settle the cell. || 327th: MERGE HOLD (proposed no/B, held unknown): Merge policy: an ordering-middleware product with no drive-thru lane product at all = the claim does not apply; hold unknown (same as conversenow kiosk x2 in the 326th). The Terms' service enumeration is kept as the bound. PROPOSAL AS WRITTEN: 327th: MOVED unknown -> no (B). The 'counted roster' bound in the existing note is now backed by a CONTRACTUAL enumeration and a rebuilt product site, not just an index page. (1) The 2026-01-13 Terms and Conditions (https://chowly.com/terms-and-conditions/, new since the last pass) enumerates every service a Restaurant may elect, clause by clause: first-party web/mobile ordering (2b), private-label Google Ordering (2c), a courier service through Delivery Partners (2d), digital marketing and advertising (2e), and 'dynamic pricing, revenue reconciliation and recovery, Google business profile management, or customer surveys' (2f), plus the four named subprocessors (Nash Technologies, Sauce Technologies, Cookdash d/b/a Superorder, Ovation Up). No voice, telephone or drive-thru ordering service is among them. (2) The rebuilt chowly.com ships eight dedicated agent pages - /agents/{seo,gbp,ads,campaign,pricing,review,delivery,upsell}/ - each with its own closed 'Capabilities' list; none is a voice agent. (3) CONTROLS over 583 chowly.help articles (100% of the Knowledge manifest), 958 RCC sources, 910 cms.koala.io sources and all 167 site pages: /voice AI|voice agent|voice ordering|AI phone|phone agent/i = 0/583, 0/958, 0/910 and 3/167, and ALL THREE site hits are POISON of a specific kind - Chowly's own comparison blogs describing a COMPETITOR's feature ('AI phone answering on upper tiers', 'AI phone answering service for 24/7 call handling') in best-restaurant-management-software, best-restaurant-online-ordering-systems and top-6-restaurant-website-providers-for-2026; the subject of every sentence is another vendor, never Chowly. MORE POISON NAMED: /drive.thru|drive.through/i returns 7/583, 1/910 and 5/167, and every one is a HANDOFF MODE or a competitor round-up, not AI voice - 'Koala Checkout Configurations (Olo Users Only): Drive Thru/Drive In' is a conveyance option in the checkout config alongside Dine In, cms.koala.io's hit is containers/KioskConfig/Conveyance/form.tsx (the same conveyance enum), and the five site hits are all blog posts comparing other vendors' products. Chowly's kiosk/ordering stack offers a drive-thru CONVEYANCE; it offers no AI voice ordering in the lane and no escalation-to-human handoff. Retrieved 2026-09-18. || 333rd: 333rd NEW (notes only): Wayback of the pre-merger koala.io marketing site (46 HTML captures, 2013-2025) shows the only drive-thru product Koala sold: 'Mobile POS - Allow your team members to take orders anywhere ... Line Busting / Drive-Thru / Table-Side' (koala.io/products/mobile-pos, captured 2021-08-09) - a STAFF-held order-taking device, not AI voice; Koala's 'Machine Learning' pages (products/machine-learning, platform/machine-learning, 2022-11 / 2023-01) are cross-sell recommendation. The live COO/Koala guest client carries drive_thru_instructions only as a handoff-mode string. Retired-generation marketing may not carry a no (owner ruling 2), and the 327th hold stands. Retrieved 2026-09-18. adversarially verified

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

digital-sms-ordering

SMS is used for post-order surveys only; no text-to-order path is documented. https://chowly.com/solutions/customer-surveys/ · retrieved 2026-08-01

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

digital-google-order

"Google Ordering" is a priced line item in the Terms ($0.30/order + 2.9% + up to 10% of Base Order Value) and the GBP Agent manages the Google Business Profile. Note it carries a per-order fee rather than being included. https://chowly.com/terms-and-conditions/ · retrieved 2026-08-01

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

digital-apple-business-connect

CLAIM: supports Apple Business Connect ordering placement - an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow. VERDICT: no. BOUND: the 100% chowly.help census (583/583 articles, https://chowly.help/services/data/v59.0/support/knowledgeArticles?pageSize=100; 44/44 already-cited article URLs present). ENUMERATION: Chowly documents each surface it will place a COO ordering link on with its own article - 'Chowly Online Ordering on Google Business Pages', 'Chowly Online Ordering on Facebook', 'Chowly Online Ordering on Instagram', 'Chowly Online Ordering on TikTok', 'Chowly Online Ordering on X (Twitter)', plus the deeper 'Google Direct Order with Chowly Overview', 'Google - Direct Order: Enabling Online Ordering & Setting a Preferred Provider' and 'Finalize your Google Food Ordering Set-Up', and the site-builder set (Wix, Squarespace, WordPress, Weebly, GoDaddy). Apple is absent from that placement set. The Chowly Platform FAQ's own listing of the discovery surfaces Chowly manages names only Google: 'An integrated Google Business Profile ensures diners find the restaurant while searching in Google and on Google maps' (https://chowly.help/s/article/COO-and-Chowly-Platform-FAQ, modified 2026-04-23). CONTROLS over all 583 bodies: /\bApple\s+Business\s+Connect/ 0/583 and /\bApple\s+Maps/ 0/583. POISON checked: /\bApple/ does hit, but the hits are Apple SSO (diner login), Apple iPad/App Store kiosk deployment and Apple Configurator - none is a Maps place-card action. Grade B. Retrieved 2026-09-17. https://chowly.help/s/article/COO-and-Chowly-Platform-FAQ · retrieved 2026-09-17 adversarially verified

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

digital-loyalty-attach

Verified the verbatim claim ("The POS knows their balance and applies the reward in real time"), but the page names zero POS systems and Chowly claims 50+ POS integrations. In-store accrual/redemption necessarily depends on the specific POS's loyalty hooks; no compatibility matrix exists. Scoring a universal yes off an unqualified marketing sentence is exactly the over-read this pass is meant to catch. https://chowly.com/solutions/loyalty-program/ · retrieved 2026-08-01 adversarially verified

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

digital-subscriptions

Lunchbox's partner documentation states verbatim: 'Chowly integration does not support Scan-to-Pay, Subscriptions, or Catering.' On Chowly's own side no subscription or membership product exists anywhere in the enumerated platform: ten solutions, eight agents, the ordering Key Features list and the loyalty page's mechanics (points earn, in-store redemption, sign-on bonuses) contain no recurring-billing, membership or paid-tier feature across the full 193-URL sitemap. Grade E because the explicit limitation statement is a partner's support page (Dec 2023) describing the Chowly pipeline rather than Chowly's own documentation. https://support.lunchbox.io/en/articles/8684645-chowly-overview · retrieved 2026-08-04

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

digital-promo-parity

The claim is that the Campaign Agent "creates unique promo codes and syncs them to POS automatically" — first-party + POS. Nothing documents promo parity onto the third-party marketplaces, which is the hard half of this capability (marketplace promos are funded and configured platform-side). Partial at best. https://chowly.com/solutions/email-marketing/ · retrieved 2026-08-01 adversarially verified

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

digital-guest-data-ownership

Marketing asserts "This is YOUR data - not the delivery apps'", but the Terms document no bulk export right and bar the restaurant from reidentifying End User personal information. Claim and contract disagree. https://chowly.com/terms-and-conditions/ · retrieved 2026-08-01

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

digital-checkout-pci-sca

Card capture is delegated to a payment provider rather than handled on the brand's own page: Koala-Square-Menu-Partners-Adding-Digital-Wallets documents Square as 'the menu & payment provider' with the Square payment form supplying the credit card entry fields (Apple Pay requires 'Using Square V2 as the payment provider' and domain registration with Apple); Koala-iOS-Kiosk-App-Deployment-Kiosk-Kickoff-Requirements names PCI Proxy alongside Olo, Square and Punchh as the partner reps Koala works with; and Chowly's Google Direct Order channel runs payments through Stripe (FAQ-Stripe-Account-and-Payments, creating-a-stripe-account-for-chowly). Shortfalls: none of the 196 chowly.help articles contains a PCI DSS 4.0 compliance statement, any reference to the March-2025 client-side script-integrity requirements (6.4.3 / 11.6.1), an AOC or SAQ type, or any mention of 3DS / 3-D Secure / SCA; the only security controls documented for the ordering front end are reCAPTCHA (Koala-General-Configurations-Enabling-reCAPTCHA) and 'user data collected by your app encrypted in transit - YES' in the Google Play data-safety article. https://chowly.help/s/article/Koala-iOS-Kiosk-App-Deployment-Kiosk-Kickoff-Requirements · retrieved 2026-08-08

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

digital-surcharge-transparency

SHORTFALL NAMED: Chowly ships online price differentiation, not a mirrored surcharge configuration with disclosure. PRESENT: "Some restaurants choose to make their online menus a little more expensive than their in house menu." "In the Upcharge field, you can add a number that then gets translated into a percentage. For example, 5.0 is a 5% upcharge, 7.5 is a 7.5% upcharge", applied "to whatever price you have set for your menu items in your POS system." It is set per location and either for all platforms at once or per individual platform, and negatives are supported: "You can even do negative upcharges (or downcharges) if you'd like to run a promo or a discount". MISSING, and why this is not a yes: the uplift is embedded in the displayed item price - "a 5% upcharge will make this item appear as $10.50 to customers ordering online" - so there is no separate service-fee or card-surcharge line and consequently no guest-facing disclosure string at all; and it is Chowly's own markup applied over the POS's prices, not the POS's service-fee / dual-pricing / card-surcharge configuration mirrored online. No jurisdiction logic and no card-brand logic appear in the article; its single enumerated restriction is a marketplace policy - "Note: Up-charges are not supported for pickup menus on Doordash, as Chowly implemented dual pricing support specifically to meet DoorDash's requirements." - not a US state surcharging prohibition or a card-network rule. Also stated: "If you are using our Smart Pricing product, please note that this feature will not be accessible within the Restaurant Control Center", because "upcharges are automatically configured using our AI algorithm". LastPublishedDate 2026-02-24 - current documentation, not the 2023 stratum. https://chowly.help/s/article/Upcharge-Settings-on-the-Restaurant-Control-Center · retrieved 2026-09-05 adversarially verified

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

guest-loyalty-unified-profile

Same evidence, same gap: single profile across web/app/register is asserted on a marketing page with no POS list, no dedup/merge semantics, and no statement of whether the profile spans all locations of a brand. Claim-level, POS-dependent. https://chowly.com/solutions/loyalty-program/ · retrieved 2026-08-01 adversarially verified

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

guest-loyalty-thirdparty-identity-attach

Terms confirm Chowly collects Order Data including End User name, address, phone and email across channels, so marketplace identity is captured - but whether it merges into a native loyalty profile is undocumented, and Chowly bars reidentification by the restaurant. https://chowly.com/terms-and-conditions/ · retrieved 2026-08-01

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

guest-loyalty-accrual-models

Points accrual with welcome rewards is documented. A second accrual model (punch/visit or spend tier) is not. https://chowly.com/solutions/loyalty-program/ · retrieved 2026-08-01

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

guest-loyalty-tiers

Koala Punchh Loyalty Partners: Advanced Loyalty Dashboard - 'Koala offers an Advanced Loyalty Dashboard for brands using Punchh or Spendgo for Loyalty', surfacing 'visual representation of guest's earnings and progress towards rewards', 'available points, earning status and other user-specific loyalty components', available rewards and offers, earn and redeem in store, points history and barcode entry. The Web Ordering Feature Set's SSO + LOYALTY section is prefaced 'Features may vary by integration partner (Punchh, Paytronix, Spendgo, etc.)'. Shortfall: the loyalty engine is the partner's, not Chowly's - status tiers, and any rolling-window spend or visit rule that promotes or demotes between them, are configured in Punchh/Paytronix/Spendgo and are nowhere described as a Chowly-side capability; the dashboard's own enumerated components are points, earning status and progress to next reward, with no tier construct. Chowly's separately marketed points programme (chowly.com/loyalty-program) has no product documentation at all. https://chowly.help/s/article/Koala-Punchh-Loyalty-Partners-Advanced-Loyalty-Dashboard · retrieved 2026-08-08

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

guest-loyalty-offline-behavior

327th: MOVED unknown -> no (B). A publication claim, and the module it is about definitely exists at Chowly now, so the claim applies: chowly.com/solutions/loyalty-program/ is a first-party product page on the rebuilt site, and the chowly.app RCC source-map census carries a shipped loyalty feature area - features/digital-marketing/Loyalty/Loyalty.tsx, LoyaltyDiners/, LoyaltyRewards/, LoyaltyAdapterIndicator.tsx, and the API modules api/loyaltyDiners, api/loyaltyLedgerEntries, api/loyaltyRedeemables (a diner ledger, i.e. accrual and redemption are Chowly's own objects, not only Punchh's). BOUND: 583 chowly.help articles (100% of the Salesforce Knowledge manifest), 958 RCC sources, 910 cms.koala.io sources, all 167 chowly.com sitemap pages (none a soft-404). CONTROLS: /loyalty.{0,120}offline|offline.{0,120}loyalty/i = 0/583, 0/958, 0/910, 0/167; /\boffline\b/i = 1/583 (an Olo vendor going offline), 3/958 (browser online/offline events and a chat widget), 0/910, 6/167 (all SEO-blog 'offline marketing' poison); /queue.and.reconcile|reconcile.{0,40}(?:points|rewards)/i = 0 everywhere. Nothing documents whether loyalty lookup, accrual or redemption queues, blocks or silently drops when connectivity is lost. Retrieved 2026-09-18. https://chowly.com/solutions/loyalty-program/ · retrieved 2026-09-18 adversarially verified

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

guest-loyalty-offer-stacking-rules

CLAIM: offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. VERDICT: partial. EVIDENCE, from the 583-article chowly.help census (Salesforce guest knowledge API, see the commercial-wcag row for the route): 'Standalone Promotions in the RCC' (https://chowly.help/s/article/Standalone-Promotions-in-the-RCC, modified 2026-03-11) states an explicit, published exclusivity rule in its FAQ - 'Can the diner use the BOGO Promo Code with another Promo Code? No, we do not currently have this functionality.' and 'Do BOGO Promo Codes "stack" within the basket?... No. BOGO Promo Codes only work once within the diner's basket... This works inline with our overarching philosophy that only one promo code can be applied to a single order.' So the engine's combinability behaviour IS documented, and it is exclusive-only. NAMED SHORTFALL: exclusivity is a fixed product philosophy, not CONFIGURATION - the article enumerates the complete condition set an operator can set on a promo ('Conditions: Options to make it single use and add a minimum purchase amount. Active Dates') and there is no exclusive-vs-combinable toggle, no priority/order-of-application field and no maximum-discount cap. Promo types are closed at three: 'Fixed Discount, Percentage Off, or BOGO'. The interaction between a Standalone Loyalty redemption and a promo code is not documented in 'Loyalty and Promotions on the Restaurant Control Center (RCC)' (https://chowly.help/s/article/Digital-Marketing-on-the-Restaurant-Control-Center-RCC, modified 2026-03-13) either. SCOPE BOUND: this covers Chowly's own standalone engine only; that article also says 'if your restaurant uses Square or Toast POS, Promo Codes must be created directly from the POS System', so stacking for those operators is the POS vendor's behaviour, not Chowly's. Grade B. Retrieved 2026-09-17. https://chowly.help/s/article/Standalone-Promotions-in-the-RCC · retrieved 2026-09-17 adversarially verified

Offers can be issued to a dynamically defined audience (rules over recency, frequency, spend, or items purchased) rather than only broadcast to the whole list. differentiator

guest-loyalty-targeted-offers

Shortfall named: evidence is a marketing landing page only, and a differentiator yes needs grade A or B. The page does state "Audience segmentation by RFM (recency, frequency, monetary value)" and "Promo codes created and synced to your POS automatically", with win-back and welcome sequences. But the channel is email only - no SMS or push offer targeting is described on either the Campaign Agent or email-marketing page - and the email-marketing page conditions the loop on Chowly owning the channel: "Because Chowly owns the ordering platform, you see the full picture from send to sale." No product documentation could be retrieved to confirm the segmentation is operator-configurable: chowly.help is a Salesforce Experience Cloud site that renders only "Sorry to interrupt / CSS Error" to retrieval, and its indexed article URLs either 404 or return the same shell. https://chowly.com/agents/campaign/ · retrieved 2026-08-02 adversarially verified

Automatically computes recency/frequency/monetary or equivalent lifecycle segments (new, regular, at-risk, lapsed, VIP) without the operator building the queries. differentiator

guest-loyalty-rfm-segmentation

Monitors behavior and order history to identify at-risk or lapsing customers automatically. A full named lifecycle segmentation (new / regular / at-risk / lapsed / VIP) is not documented. https://chowly.com/solutions/email-marketing/ · retrieved 2026-08-01

Ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns rather than one-off manual sends.

guest-loyalty-lifecycle-automation

Always-on welcome sequences for new customers and "escalating win-back emails to customers who haven't ordered recently". Birthday triggers are not documented. https://chowly.com/solutions/email-marketing/ · retrieved 2026-08-01

Sends both email and SMS campaigns natively from the platform, not solely by handing the list to a third-party ESP. differentiator

guest-loyalty-native-email-sms

Email campaigns are native. SMS is native but documented only for post-order surveys, not marketing campaigns. https://chowly.com/solutions/customer-surveys/ · retrieved 2026-08-01

Captures per-channel marketing consent with timestamp and source of consent, and honors revocation received by any reasonable means (not just the STOP keyword) across all channels.

guest-loyalty-consent-management

Koala Account Configurations: Opt-In documents marketing consent capture at sign-up: 'Brands may surface an opt-in message during account creation. This is an optional configuration available for select loyalty integrations. If enabled, an opt-in string and checkbox will be surfaced. Selecting the opt-in is optional...' The string is authored in Brand CMS at Web Ordering > Strings > Signup and supports HTML for linking privacy policy and terms; a companion article covers a required Terms & Conditions acceptance checkbox. Shortfalls: consent is a single undifferentiated marketing opt-in, not per-channel (no separate email/SMS/push consent); no timestamp or source-of-consent capture is documented; no revocation or unsubscribe handling appears anywhere in the 196-article corpus (the words consent, revoke, unsubscribe and STOP do not occur outside this article); the feature is only 'available for select loyalty integrations', so the consent record lives in Punchh/Paytronix/Spendgo; and the CMS offers 'Opt-In Auto-Select', which pre-ticks the consent box by default at Web Ordering > Config > Accounts. https://chowly.help/s/article/Koala-Account-Configurations-Opt-In · retrieved 2026-08-08

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

guest-loyalty-10dlc-registration

Quote: "In particular, Chowly will not share your mobile information or text messaging originator opt-in data and consent information with any third party. You may opt-out of receiving further messages sent on Chowly's behalf by replying STOP or ask for more information by replying HELP. Message frequency may vary. Message and data rates may apply." Chowly is the SMS sender, not the operator: the privacy policy (vendor legal page, grade B) carries the CTIA/10DLC-campaign-required consent, STOP/HELP, frequency and rates disclosures for 'messages sent on Chowly's behalf', and the Diner Terms (B) obtain consent to 'receive communications from Chowly, Merchants ... including via email, text message'. The only SMS product is the post-order text survey (chowly.com/solutions/customer-surveys, C: 'Chowly sends an automatic text survey after every completed order'); operator campaigns are email only (Campaign Agent). So the operator sends no SMS through the platform and bears no registration. Shortfall: A2P 10DLC brand/campaign registration is never named or documented anywhere (searched 10DLC, A2P, TCPA, short code, Twilio, campaign registration across 161 help bodies and 81 site pages: zero), and there is no operator-facing SMS marketing channel at all. Answering the claim as written: registration is not 'explicitly documented'; it is implicitly Chowly's because the vendor is the originator. https://chowly.com/privacy-policy/ · retrieved 2026-09-03 adversarially verified

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

guest-loyalty-campaign-attribution

Supported only by the bullet "Track email-to-order revenue, not just opens and clicks." No documented attribution window, model, multi-touch handling, or report artifact. Marketing page, single sentence, weighted differentiator — does not clear the bar for yes. https://chowly.com/solutions/email-marketing/ · retrieved 2026-08-01 adversarially verified

Provides self-serve export of the full guest list and transaction history, including contact PII, via CSV or API, without a vendor fee or support ticket. differentiator

guest-loyalty-data-export-portability

Quote: "(3) The Three Dots icon shows a drop-down list of other actions you can do with your data: Sort, Download, Refresh data, Copy to clipboard, and Format." Self-serve download exists on every Restaurant Control Center tile (grade B), and the Delivery Buydown page shows order-level tiles carrying 'CUSTOMER NAME', subtotal, tax, total, status and 'CREATED AT' per order, so an operator can download order history with customer name without a ticket or fee. chowly.com/solutions/loyalty-program (C) claims 'Every loyalty sign-up captures name, email, phone, and order history. This is YOUR data'. Shortfall: no documented export of the full guest list with contact PII (email, phone) - the RCC tiles are order/sales analytics, the loyalty guest record lives in the POS loyalty program or the Koala loyalty partner, no API is documented, and the automation blog's 'Instead of ... exporting six different spreadsheets, you see everything in one place' (D) positions the product against exports rather than for them. https://chowly.help/s/article/Navigating-the-Restaurant-Control-Center · retrieved 2026-09-03 adversarially verified

Exposes a documented outbound guest and order event API or webhook stream that a CDP or marketing platform can subscribe to (e.g. Olo, Punchh, Bridg, Klaviyo). differentiator

guest-loyalty-cdp-event-api

Koala-Web-Ordering-App-Deployment-Responsive-Web-Launch-Requirements instructs brands to 'have the responsible party review Koala's Commerce Events Data Layer to ensure any necessary modifications to the current tagging implementation will work properly'; Koala-Web-Ordering-App-Deployment-Kickoff-Requirements documents GA4 support and states 'Koala currently supports pixels via Google Tag Manager, which allows you to add, modify and manage your pixels without reliance on our dev team', with a dedicated article for Enhanced Ecommerce. Shortfalls: this is a browser-side data layer and tag container, not a subscribable event stream - a CDP can only collect what the guest's browser fires, and server-side or offline events (loyalty accrual, POS-side order state, refunds) are not included; no outbound webhook product, no event catalogue, no signature verification and no retry semantics are documented; the webhooks Chowly documents run the other way, as Koala subscribing to Olo's MenuItemAvailabilityChanged, VendorAvailabilityChanged and dispatch-tracking webhooks. A Koala API does exist (Koala-IOS-Mobile-Configurations-Account-Deletion: deletion 'via a call by the Koala API') but no reference for it is published. https://chowly.help/s/article/Koala-Web-Ordering-App-Deployment-Kickoff-Requirements · retrieved 2026-08-08

Triggers post-transaction feedback requests and routes responses by score, sending low scores to private service recovery and high scores toward public review sites. differentiator

guest-loyalty-review-capture-routing

Quote: "Chowly sends an automatic text survey after every completed order . Happy customers are guided straight to your Google Business Profile to leave a review, while unhappy customers are routed to a private channel — so you can fix problems before they become public 1-star reviews." The claim is described end to end on the vendor's feature page (C) and the Review Agent page (C: 'Positives Routed to Google', 'Negatives Intercepted ... routed to private channel before they post', 'Sentiment Analysis Reads the response, sorts praise from problems', log line 'Negative feedback intercepted — routed to manager for direct outreach'), and chowly.com/agents/ reports '84,000+ post-order surveys sent · this month', i.e. shipped. Differentiator weight with no A/B source: no help-centre article documents the survey, the score threshold, the private-channel destination or any configuration, and the routing is by AI sentiment rather than a documented score cut-off. Partial: marketing establishes the mechanism; documentation of configuration is absent. https://chowly.com/solutions/customer-surveys/ · retrieved 2026-09-03 adversarially verified

Includes a native referral mechanic with per-guest codes or links, attribution of the referred guest's first order, and two-sided rewards.

guest-loyalty-referral-program

Koala Punchh Loyalty Partners: Referral Code - 'Koala supports an optional field on Sign Up allowing a guest to enter a Referral Code from a friend who has referred them. Users may also pull their personal referral code from their account.' Enabled by any Brand CMS user at Web Ordering Config > Web Config > Accounts > Punchh Referral Code Field [True], and on iOS at Flows > Account > Features > Referral Code Enabled. So per-guest codes and referred-guest attribution at sign-up are real and self-serve to switch on. Shortfalls: the feature is explicitly Punchh-only (unavailable to Paytronix, Spendgo or non-loyalty brands); Koala supplies only the code entry field and the personal-code display, while the referral reward rules are defined in Punchh; attribution is captured at account creation rather than against the referred guest's first order; and no two-sided reward (referrer and referee) is documented on Chowly's side. The referral programme on chowly.com is a separate B2B refer-a-restaurant bounty, not this feature. https://chowly.help/s/article/Koala-Punchh-Loyalty-Partners-Referral-Code · retrieved 2026-08-08

Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance, as an alternative to requiring a branded app download. differentiator

guest-loyalty-wallet-pass

Chowly's 2026 loyalty carrier is affirmatively stated to be its branded app, and the page answers the exact problem this claim names - enrolment without an app install - with a different remedy. It names the carrier: "Point balances, available rewards, and redemption are front and center. The app IS the loyalty experience", the app being "Built around the loyalty program, not bolted on as an afterthought". And its stated answer to install friction is an incentive to install rather than a no-download pass: "Sign-On Bonuses", "Drive app adoption with welcome bonuses for new account creation", "Download the app, get 50 points free", "reducing the friction of the hardest step: the first install". None of the page's six key features - iOS & Android, Loyalty-First Design, Sign-On Bonuses, Push Notifications, Integrated Ordering, Rapid Reorder - is an Apple or Google Wallet pass. Corroborating, not quoted from this url: chowly.com/solutions/loyalty-program/ (2026) names the earn-and-redeem surfaces as the website, the mobile app and the register, with six key features and no wallet pass; and the help centre's only wallet article, Koala Square Menu Partners: Adding Digital Wallets, is Apple Pay and Google Pay as a payment method, with the in-store loyalty carrier being a barcode scanned inside the app. Grade C, not B: this is a first-party feature page written to sell, and Chowly publishes no product documentation for its own 2026 loyalty program. Caveat recorded for re-verification: Koala's SSO + Loyalty section says features may vary by integration partner (Punchh, Paytronix, Spendgo), and those partners do issue wallet passes - that is the partner's capability, not Chowly's, and this cell should be reopened if Chowly ever documents pass issuance itself. https://chowly.com/solutions/mobile-app/ · retrieved 2026-09-05 adversarially verified

Provides admin tooling to fulfill guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records.

guest-loyalty-privacy-rights-tooling

Chowly runs a CCPA request process (access, portability twice per 12 months, deletion) with a 45-day response window, but it is an email workflow to Chowly, not in-app operator tooling. https://chowly.com/ccpa/ · retrieved 2026-08-01

Enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log.

guest-loyalty-redemption-fraud-controls

325th: MOVED unknown -> no (B) for Chowly's own loyalty adapter. NEW SURFACE: the RCC's complete public source-map set now exposes the whole loyalty admin surface (nonsense controls as on delivery-zones-polygon). CLAIM: enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log. VERDICT: no - the product enforces none of them. EVIDENCE: the loyalty surface is features/digital-marketing/Loyalty (LoyaltyRewards + UpsertRewardModal + UploadCsvModal, BonusIncentives + UpsertBonusIncentiveModal, LoyaltyDiners + LoyaltyDinersDrawer, ImportLogTable, ToastCoupons) over five endpoints (loyaltyRedeemables, loyaltyRedeemable, loyaltyRedeemableCsv, loyaltyDiners/:id, loyaltyLedgerEntries). Manual point adjustment is unguarded: api/loyaltyLedgerEntries/index.ts exposes `createLoyaltyLedgerEntry(loyaltyAccountId, amount, reason)` POSTing { amount, reason } with the only validation being a non-empty account id and a finite non-zero amount, and LoyaltyDinersDrawer.tsx drives it from a credit/debit toggle plus a free-text box that defaults to the literal `'Manual adjustment'` when blank - no second approver, no manager PIN, no approval state machine (contrast the email-campaign path, which does ship an approve/reject/block flow with an audit timeline). There is no velocity or per-guest cap: `velocity` 0 hits in the 830 shipped files and 0/583 in the chowly.help census, and the reward payload carries no per-guest or per-period redemption limit. Employee self-redemption cannot be flagged because there is no employee dimension at all (`employee|employees|staff` 1/830, the role name; the reporting order record has no employee field). The nearest related artefact is the per-account ledger itself (GET /api/v3/loyalty_accounts/:id/ledger_entries, rendered as dated credit/debit cards with the reason), which is a transaction list, not an enforced control - a partial resting on it would shortfall every conjunct of the claim. SHORTFALL/SCOPE: this bounds Chowly's NATIVE loyalty adapter; Organization.loyalty_adapter also takes 'Toast' and 'Square', where Loyalty.tsx says 'Loyalty setup happens in your Square dashboard' and the controls are the POS's, not Chowly's. Retrieved 2026-09-17. https://chowly.app/static/js/main.54b02cd0.js.map · retrieved 2026-09-17 adversarially verified

Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing (claim-level; verify it is a shipped product feature, not a roadmap statement). differentiator

guest-loyalty-ai-offer-recommendation

Quote: "How does it know what offers to make? + It watches your POS data. Customers who haven't ordered in 14 days get a different offer than first-time customers or VIPs. The agent segments in real time — no marketing degree required." Shipped, not roadmap: chowly.com/agents/ reports '1.8M emails sent + tracked · this month' and the email-marketing page (C) adds '✓ Optimizes send times based on when your customers engage'. The Campaign Agent generates offer content (subject, body, promo code), picks the audience (RFM segments, 14-day churn flags, first-timers vs VIPs) and the schedule - all three legs of the claim. Differentiator weight with C-grade evidence only: no help-centre article documents the Campaign Agent, its models, approvals or configuration (the only documented ML feature, per the record's prior rationale, is item cross-sell - Koala Cross-Sell Configurations: Machine Learning Cross Sell - which is the wrong feature and is not in today's corpus). Partial until an A/B source describes it. https://chowly.com/agents/campaign/ · retrieved 2026-09-03 adversarially verified

Offers native stored-value/gift card balances tied to the same guest profile and redeemable across all locations of the brand.

guest-loyalty-stored-value-gift

Koala Checkout Configurations (Olo Users Only): Gift Cards Support - 'Koala offers gift card support for Olo brands, keying off of configurations in Olo. There is not a setup required on the Koala side and all setup is automated based off Olo configurations... (1) Koala keys off of Olo to determine whether or not Gift Cards are supported. (2) Koala keys off of Olo to determine whether or not Split Tender is supported. If Supported - A guest will be able to split payment across a gift card and another form of payment. If Not Supported - A guest will only be able to use a gift card if the value of the gift card covers the entire cost of the order.' Shortfalls: this is acceptance of a third party's stored value, not a native product - the card, the balance and the multi-location redemption rules all live in Olo (and the feature sits under 'For Olo Users Only: Add-On Features', so Square-menu and non-Olo brands have none); balances are not tied to the Chowly/Koala guest profile, which carries loyalty points from Punchh/Paytronix/Spendgo instead; and even split tender is contingent on the Olo configuration. No gift-card issuance, reload or balance-check surface is documented on Chowly's side, and gift cards do not appear at all in the third-party-marketplace or Restaurant Control Center documentation. https://chowly.help/s/article/Koala-Checkout-Configurations-Olo-Users-Only-Gift-Cards-Support · retrieved 2026-08-08

Employees clock in and out at the POS terminal using a PIN, badge, or card, with no separate time-clock hardware required.

labor-clock-in-at-pos

Ships no labor or timekeeping product. https://chowly.com/chowly-platform/ · retrieved 2026-08-01

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

labor-photo-punch-verification

331st LABOUR CENSUS -> no/B. MERGE CALL: landed `no`, not held at unknown, because this record already carries five labour `no`s on the same basis (clock-in-at-pos, granular-rbac, payroll-export-formats at B; manager-override-audit, server-performance-metrics at C), and the chowly/olo scope precedent requires a category to be SETTLED `no` before it is excluded. The claim is bounded by three censused Chowly product surfaces plus the publisher app census below, not by marketing silence. FOUR CORPORA ALREADY ON DISK, EACH A CENSUS OF ONE CHOWLY SURFACE, plus one new publisher census: (1) chowly.help Salesforce Knowledge, 583/583 articles (100% of the Knowledge listing, 1.34 M chars stripped, HTML comments removed first); (2) the Restaurant Control Center chowly.app, closed /asset-manifest.json source-map set, 958 extracted sources; (3) cms.koala.io Koala Brand CMS, 910 mapped sources (580 Koala-own); (4) the rebuilt chowly.com, 167/167 sitemap pages; (5) NEW: the App Store publisher census for Chowly Inc (iTunes lookup id=1726094961&entity=software, 51 apps): every one is a white-label DINER ordering/loyalty app for a named restaurant (Muldoon Pizza, Two Eggs, Liv's Juice Bar ...); zero employee-, manager-, time-clock- or scheduling-facing apps. TOKENISED word-boundary controls, case-insensitive, KB / RCC / Koala / site (docs hit): known-positive menu 273/110/35/125 and order(s) 294/105/39/167 (regexes work); time[-]clock 0/0/0/2; clock(ed)-in/out 0/0/0/1; timesheet|timecard 0/0/0/0; payroll 0/0/0/9; W-2|I-9 0/0/0/0; wage|hourly rate 0/0/0/2; tip pool|tip-out|tip share 0/0/0/2; fair workweek|predictive scheduling 0/0/0/1; meal|rest break 0/0/0/1; labor|labour 1/0/0/24; punch 1/0/0/10; shift(s) 3/9/8/45; overtime|over time 0/7/3/22; schedul* 29/63/3/24; employee(s) 17/1/0/8; 7shifts|Homebase|HotSchedules|Sling|Deputy|Harri|Gusto|ADP|Paychex 0/0/0/3. EVERY NON-ZERO HIT WAS READ AND CLASSIFIED, AND NONE IS A CHOWLY LABOUR SURFACE. POISON NAMED: KB `labor` = 'Labor Day' (holiday hours); KB `punch` = 'Olo, Punch or SSMA' (a data-deletion partner); site `punch` = loyalty PUNCH CARDS; KB `shift` = a UI element that 'would shift from left to right' and chargeback 'Chip Liability Shift'; RCC/Koala `shift` = floating-ui shift(), Array.prototype.shift(), shiftKey and 'shift+left' hotkeys (and `shifted`/`shifting` excluded by the token boundary); RCC/Koala `overtime` = 'over time' in chart captions and slate-editor comments; `break` = CSS/text LINE BREAKS, 'breaks of availability' in hours, and the JS `break` statement; KB `schedul*` 29 docs = scheduled (future) ORDERS, store/online-ordering hour schedules, Olo product-availability schedules, 'Schedule a Meeting with Our Team', the Stripe payout schedule and the Koala release schedule - zero employee schedules; KB `employee` 17 docs = Chowly's own support staff ('Chowly employees have no way of getting into your POS'), a POS employee ACCOUNT used to install the Chowly App on Clover, and the POS employee Chowly stamps onto an injected ticket ('orders integrating with the incorrect dining option, tender, revenue center, or employee'); RCC `employee` 1 = the RCC LOGIN ROLE `RESTAURANT_EMPLOYEE`, whose src/config.ts permittedFeaturesByRole grant is exactly five features (Manage Locations view/search/select, Resync Menus, Select Platform) - an app-user role, not an employee record; site hits are all SEO blog prose about OTHER vendors (7shifts 'time clock with break compliance, tip pooling and payouts, and payroll', resources/blogs/best-restaurant-management-software). THE APP'S OWN ENUMERATIONS CLOSE IT FOR THE RCC: src/config.ts `enum AppFeatureName` lists 23 features (Health Dashboard, 5 Analytics reports, 16 Manage Location/Platform actions, View COO Brand & Config Info) and the router's path table is Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing - no labour route. VENDOR-VOICE POSITIONING (grade C, blog 2026-06-09, https://chowly.com/resources/blogs/best-restaurant-management-software/): all-in-one platforms like Chowly 'consolidate the guest-facing side of the business - website, ordering, marketing, loyalty - into one system', while 'Most restaurants run a POS ..., an online ordering system, a scheduling tool like 7shifts, and inventory or invoice software'; and https://chowly.com/resources/blogs/restaurant-tech-stack-pays-for-itself-90-days/ tabulates the stack as 'POS | Toast/Square | Existing operational backbone' and 'Everything else | Chowly Platform | Online ordering, delivery integration, marketing, loyalty, website, analytics, AI pricing'. The site's own product menu (index) enumerates Marketing Website, Online Ordering, Google Business Profile, Google Ads, 3rd Party Integration, Email Marketing, Mobile App, Dynamic Pricing, Customer Surveys, Loyalty Program and eight AI Agents - no labour product. The only staffing-aware line is the Delivery Agent's 'Dynamic hours adjustment based on real-time staffing' (agents/delivery), which CONSUMES staffing to set marketplace hours. CONCLUSION: the labour claims do not apply to Chowly - there is no employee record, time punch, schedule, wage or tip-distribution object in any Chowly product surface we hold. CELL: no time punch exists to photograph; camera|photo hits concern menu/brand images only (not re-counted). Retrieved 2026-09-18. https://chowly.com/chowly-platform/ · retrieved 2026-09-18 adversarially verified

Supports mobile clock-in restricted by geofence or location validation for staff who do not punch at a fixed terminal.

labor-geofenced-mobile-punch

331st LABOUR CENSUS -> no/B. MERGE CALL: landed `no`, not held at unknown, because this record already carries five labour `no`s on the same basis (clock-in-at-pos, granular-rbac, payroll-export-formats at B; manager-override-audit, server-performance-metrics at C), and the chowly/olo scope precedent requires a category to be SETTLED `no` before it is excluded. The claim is bounded by three censused Chowly product surfaces plus the publisher app census below, not by marketing silence. FOUR CORPORA ALREADY ON DISK, EACH A CENSUS OF ONE CHOWLY SURFACE, plus one new publisher census: (1) chowly.help Salesforce Knowledge, 583/583 articles (100% of the Knowledge listing, 1.34 M chars stripped, HTML comments removed first); (2) the Restaurant Control Center chowly.app, closed /asset-manifest.json source-map set, 958 extracted sources; (3) cms.koala.io Koala Brand CMS, 910 mapped sources (580 Koala-own); (4) the rebuilt chowly.com, 167/167 sitemap pages; (5) NEW: the App Store publisher census for Chowly Inc (iTunes lookup id=1726094961&entity=software, 51 apps): every one is a white-label DINER ordering/loyalty app for a named restaurant (Muldoon Pizza, Two Eggs, Liv's Juice Bar ...); zero employee-, manager-, time-clock- or scheduling-facing apps. TOKENISED word-boundary controls, case-insensitive, KB / RCC / Koala / site (docs hit): known-positive menu 273/110/35/125 and order(s) 294/105/39/167 (regexes work); time[-]clock 0/0/0/2; clock(ed)-in/out 0/0/0/1; timesheet|timecard 0/0/0/0; payroll 0/0/0/9; W-2|I-9 0/0/0/0; wage|hourly rate 0/0/0/2; tip pool|tip-out|tip share 0/0/0/2; fair workweek|predictive scheduling 0/0/0/1; meal|rest break 0/0/0/1; labor|labour 1/0/0/24; punch 1/0/0/10; shift(s) 3/9/8/45; overtime|over time 0/7/3/22; schedul* 29/63/3/24; employee(s) 17/1/0/8; 7shifts|Homebase|HotSchedules|Sling|Deputy|Harri|Gusto|ADP|Paychex 0/0/0/3. EVERY NON-ZERO HIT WAS READ AND CLASSIFIED, AND NONE IS A CHOWLY LABOUR SURFACE. POISON NAMED: KB `labor` = 'Labor Day' (holiday hours); KB `punch` = 'Olo, Punch or SSMA' (a data-deletion partner); site `punch` = loyalty PUNCH CARDS; KB `shift` = a UI element that 'would shift from left to right' and chargeback 'Chip Liability Shift'; RCC/Koala `shift` = floating-ui shift(), Array.prototype.shift(), shiftKey and 'shift+left' hotkeys (and `shifted`/`shifting` excluded by the token boundary); RCC/Koala `overtime` = 'over time' in chart captions and slate-editor comments; `break` = CSS/text LINE BREAKS, 'breaks of availability' in hours, and the JS `break` statement; KB `schedul*` 29 docs = scheduled (future) ORDERS, store/online-ordering hour schedules, Olo product-availability schedules, 'Schedule a Meeting with Our Team', the Stripe payout schedule and the Koala release schedule - zero employee schedules; KB `employee` 17 docs = Chowly's own support staff ('Chowly employees have no way of getting into your POS'), a POS employee ACCOUNT used to install the Chowly App on Clover, and the POS employee Chowly stamps onto an injected ticket ('orders integrating with the incorrect dining option, tender, revenue center, or employee'); RCC `employee` 1 = the RCC LOGIN ROLE `RESTAURANT_EMPLOYEE`, whose src/config.ts permittedFeaturesByRole grant is exactly five features (Manage Locations view/search/select, Resync Menus, Select Platform) - an app-user role, not an employee record; site hits are all SEO blog prose about OTHER vendors (7shifts 'time clock with break compliance, tip pooling and payouts, and payroll', resources/blogs/best-restaurant-management-software). THE APP'S OWN ENUMERATIONS CLOSE IT FOR THE RCC: src/config.ts `enum AppFeatureName` lists 23 features (Health Dashboard, 5 Analytics reports, 16 Manage Location/Platform actions, View COO Brand & Config Info) and the router's path table is Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing - no labour route. VENDOR-VOICE POSITIONING (grade C, blog 2026-06-09, https://chowly.com/resources/blogs/best-restaurant-management-software/): all-in-one platforms like Chowly 'consolidate the guest-facing side of the business - website, ordering, marketing, loyalty - into one system', while 'Most restaurants run a POS ..., an online ordering system, a scheduling tool like 7shifts, and inventory or invoice software'; and https://chowly.com/resources/blogs/restaurant-tech-stack-pays-for-itself-90-days/ tabulates the stack as 'POS | Toast/Square | Existing operational backbone' and 'Everything else | Chowly Platform | Online ordering, delivery integration, marketing, loyalty, website, analytics, AI pricing'. The site's own product menu (index) enumerates Marketing Website, Online Ordering, Google Business Profile, Google Ads, 3rd Party Integration, Email Marketing, Mobile App, Dynamic Pricing, Customer Surveys, Loyalty Program and eight AI Agents - no labour product. The only staffing-aware line is the Delivery Agent's 'Dynamic hours adjustment based on real-time staffing' (agents/delivery), which CONSUMES staffing to set marketplace hours. CONCLUSION: the labour claims do not apply to Chowly - there is no employee record, time punch, schedule, wage or tip-distribution object in any Chowly product surface we hold. CELL: no employee mobile app exists - the Chowly Inc App Store publisher list is 51 diner ordering apps; geofenc* = 0 in KB/RCC/Koala. Retrieved 2026-09-18. https://chowly.com/chowly-platform/ · retrieved 2026-09-18 adversarially verified

Records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, with the behavior documented. differentiator

labor-offline-time-punch

331st LABOUR CENSUS -> no/B. MERGE CALL: landed `no`, not held at unknown, because this record already carries five labour `no`s on the same basis (clock-in-at-pos, granular-rbac, payroll-export-formats at B; manager-override-audit, server-performance-metrics at C), and the chowly/olo scope precedent requires a category to be SETTLED `no` before it is excluded. The claim is bounded by three censused Chowly product surfaces plus the publisher app census below, not by marketing silence. FOUR CORPORA ALREADY ON DISK, EACH A CENSUS OF ONE CHOWLY SURFACE, plus one new publisher census: (1) chowly.help Salesforce Knowledge, 583/583 articles (100% of the Knowledge listing, 1.34 M chars stripped, HTML comments removed first); (2) the Restaurant Control Center chowly.app, closed /asset-manifest.json source-map set, 958 extracted sources; (3) cms.koala.io Koala Brand CMS, 910 mapped sources (580 Koala-own); (4) the rebuilt chowly.com, 167/167 sitemap pages; (5) NEW: the App Store publisher census for Chowly Inc (iTunes lookup id=1726094961&entity=software, 51 apps): every one is a white-label DINER ordering/loyalty app for a named restaurant (Muldoon Pizza, Two Eggs, Liv's Juice Bar ...); zero employee-, manager-, time-clock- or scheduling-facing apps. TOKENISED word-boundary controls, case-insensitive, KB / RCC / Koala / site (docs hit): known-positive menu 273/110/35/125 and order(s) 294/105/39/167 (regexes work); time[-]clock 0/0/0/2; clock(ed)-in/out 0/0/0/1; timesheet|timecard 0/0/0/0; payroll 0/0/0/9; W-2|I-9 0/0/0/0; wage|hourly rate 0/0/0/2; tip pool|tip-out|tip share 0/0/0/2; fair workweek|predictive scheduling 0/0/0/1; meal|rest break 0/0/0/1; labor|labour 1/0/0/24; punch 1/0/0/10; shift(s) 3/9/8/45; overtime|over time 0/7/3/22; schedul* 29/63/3/24; employee(s) 17/1/0/8; 7shifts|Homebase|HotSchedules|Sling|Deputy|Harri|Gusto|ADP|Paychex 0/0/0/3. EVERY NON-ZERO HIT WAS READ AND CLASSIFIED, AND NONE IS A CHOWLY LABOUR SURFACE. POISON NAMED: KB `labor` = 'Labor Day' (holiday hours); KB `punch` = 'Olo, Punch or SSMA' (a data-deletion partner); site `punch` = loyalty PUNCH CARDS; KB `shift` = a UI element that 'would shift from left to right' and chargeback 'Chip Liability Shift'; RCC/Koala `shift` = floating-ui shift(), Array.prototype.shift(), shiftKey and 'shift+left' hotkeys (and `shifted`/`shifting` excluded by the token boundary); RCC/Koala `overtime` = 'over time' in chart captions and slate-editor comments; `break` = CSS/text LINE BREAKS, 'breaks of availability' in hours, and the JS `break` statement; KB `schedul*` 29 docs = scheduled (future) ORDERS, store/online-ordering hour schedules, Olo product-availability schedules, 'Schedule a Meeting with Our Team', the Stripe payout schedule and the Koala release schedule - zero employee schedules; KB `employee` 17 docs = Chowly's own support staff ('Chowly employees have no way of getting into your POS'), a POS employee ACCOUNT used to install the Chowly App on Clover, and the POS employee Chowly stamps onto an injected ticket ('orders integrating with the incorrect dining option, tender, revenue center, or employee'); RCC `employee` 1 = the RCC LOGIN ROLE `RESTAURANT_EMPLOYEE`, whose src/config.ts permittedFeaturesByRole grant is exactly five features (Manage Locations view/search/select, Resync Menus, Select Platform) - an app-user role, not an employee record; site hits are all SEO blog prose about OTHER vendors (7shifts 'time clock with break compliance, tip pooling and payouts, and payroll', resources/blogs/best-restaurant-management-software). THE APP'S OWN ENUMERATIONS CLOSE IT FOR THE RCC: src/config.ts `enum AppFeatureName` lists 23 features (Health Dashboard, 5 Analytics reports, 16 Manage Location/Platform actions, View COO Brand & Config Info) and the router's path table is Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing - no labour route. VENDOR-VOICE POSITIONING (grade C, blog 2026-06-09, https://chowly.com/resources/blogs/best-restaurant-management-software/): all-in-one platforms like Chowly 'consolidate the guest-facing side of the business - website, ordering, marketing, loyalty - into one system', while 'Most restaurants run a POS ..., an online ordering system, a scheduling tool like 7shifts, and inventory or invoice software'; and https://chowly.com/resources/blogs/restaurant-tech-stack-pays-for-itself-90-days/ tabulates the stack as 'POS | Toast/Square | Existing operational backbone' and 'Everything else | Chowly Platform | Online ordering, delivery integration, marketing, loyalty, website, analytics, AI pricing'. The site's own product menu (index) enumerates Marketing Website, Online Ordering, Google Business Profile, Google Ads, 3rd Party Integration, Email Marketing, Mobile App, Dynamic Pricing, Customer Surveys, Loyalty Program and eight AI Agents - no labour product. The only staffing-aware line is the Delivery Agent's 'Dynamic hours adjustment based on real-time staffing' (agents/delivery), which CONSUMES staffing to set marketplace hours. CONCLUSION: the labour claims do not apply to Chowly - there is no employee record, time punch, schedule, wage or tip-distribution object in any Chowly product surface we hold. CELL: no punch surface to go offline; offline behaviour documented only for order routing/printing. Retrieved 2026-09-18. https://chowly.com/chowly-platform/ · retrieved 2026-09-18 adversarially verified

Permissions are grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers.

labor-granular-rbac

325th: MOVED unknown -> no (B). NEW SURFACE: the Restaurant Control Center's complete public source-map set (chowly.app /asset-manifest.json lists 3 JS files and all 3 maps; main.54b02cd0.js.map 6,180,398 bytes, starts {"version":3; the nonsense siblings .NONSENSE.map 404 and /zzz-nope.js.map returns the 867-byte shell; 1,050 sources / 830 .ts/.tsx extracted). CLAIM: permissions grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers. VERDICT: no - the shipped model is exactly four fixed tiers. EVIDENCE: src/config.ts ships `export enum UserRole { CHOWLY_ADMIN = 'Chowly Admin', CHOWLY_SUPPORT = 'Chowly Support', RESTAURANT_MANAGER = 'Restaurant Manager', RESTAURANT_EMPLOYEE = 'Restaurant Employee' }` and a hard-coded map `export const permittedFeaturesByRole: Record<UserRole, Array<AppFeatureName>>` built with lodash `difference(Object.values(AppFeatureName), [...])`, over a closed 22-member `enum AppFeatureName` ('Health Dashboard', 'Analytics: Locations', 'Analytics: Sales', 'Analytics: Orders', 'Analytics: Product Mix', 'Analytics: Week over Week', 'Manage Locations', 'Manage Locations: Search', 'Manage Locations: Add Location', 'Manage Locations: Select Location', 'Manage Location: Location Upcharge', 'Manage Location: Resync Menus', 'Manage Location: Pause All Platforms', 'Manage Location: Pause Single Platform', 'Manage Location: Add Platform', 'Manage Location: Select Platform', 'Manage Location: Add Menu', 'Manage Location: Edit Menu', 'Manage Location: Preview Menu', 'Manage Location: Delete Menu', 'Manage Platform: Platform Upcharge', 'Access to all locations on Manage Locations page', 'View COO Brand & Config Info'). Restaurant Employee receives exactly five of them; the only location-scoping lever in the whole enum is the single boolean-like MANAGE_LOCATIONS_ACCESS_ALL, so there is no per-location grant. Report access is likewise a role test, not a grant: `hasPermissionToReporting` returns true only for CHOWLY_ADMIN, CHOWLY_SUPPORT or RESTAURANT_MANAGER. features/account-management/AccountManagement.tsx is a READ-ONLY 'User List' (columns Email, Status, Role, Organizations/Logos, Locations, Last Access) over GET /api/v3/account_management/users - no role editor, no permission grid, no create/update call in api/accountManagement. BOUND/CONTROLS: corpus = the complete RCC map set (830 .ts/.tsx files, 3/3 chunks mapped) plus the 583-article chowly.help Salesforce Knowledge census from the 324th. Tokenised word-boundary controls over the 830 files: `permission|permissions` 4 files / 5 hits, every one a `hasPermission` boolean prop passed into a settings panel; `employee|employees|staff` 1 hit, the role name in config.ts; `labor|labour` 0. POISON FOUND AND PUBLISHED: `void|voids|voided` returns 553 hits in 231 files and EVERY one is the TypeScript `void` return type (Promise<void>) - a count published from that term would be pure artefact; `comp|comps|comped` 4 hits, all in the SEO Keywords RankingsTable; `role|roles` 75 hits, mostly ARIA `role="region"`. Retrieved 2026-09-17. https://chowly.app/static/js/main.54b02cd0.js.map · retrieved 2026-09-17 adversarially verified

Manager overrides and approvals are attributed to the individual approver and written to an immutable audit trail queryable after the fact.

labor-manager-override-audit

A manager override audit trail is definitionally a register surface — a void, comp or discount approved at the point of sale — and Chowly states in its own voice that it is not a POS and does not replace one, but is the ordering and marketing layer running on top of whichever system the operator picks. Its knowledge base reinforces the boundary: the Chowly app and Chowly employees "have no way of getting into your POS merchant portal" (kb:FAQ-Chowly-s-POS-API-Integration), and the only override concept Chowly owns is a menu-sync artefact, not an approval event. Grade C: the sentence sits on a marketing blog page, though its grammatical subject is Chowly. https://chowly.com/resources/blogs/best-pizza-pos-systems/ · retrieved 2026-09-06 adversarially verified

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

labor-native-scheduling

331st LABOUR CENSUS -> no/B. MERGE CALL: landed `no`, not held at unknown, because this record already carries five labour `no`s on the same basis (clock-in-at-pos, granular-rbac, payroll-export-formats at B; manager-override-audit, server-performance-metrics at C), and the chowly/olo scope precedent requires a category to be SETTLED `no` before it is excluded. The claim is bounded by three censused Chowly product surfaces plus the publisher app census below, not by marketing silence. FOUR CORPORA ALREADY ON DISK, EACH A CENSUS OF ONE CHOWLY SURFACE, plus one new publisher census: (1) chowly.help Salesforce Knowledge, 583/583 articles (100% of the Knowledge listing, 1.34 M chars stripped, HTML comments removed first); (2) the Restaurant Control Center chowly.app, closed /asset-manifest.json source-map set, 958 extracted sources; (3) cms.koala.io Koala Brand CMS, 910 mapped sources (580 Koala-own); (4) the rebuilt chowly.com, 167/167 sitemap pages; (5) NEW: the App Store publisher census for Chowly Inc (iTunes lookup id=1726094961&entity=software, 51 apps): every one is a white-label DINER ordering/loyalty app for a named restaurant (Muldoon Pizza, Two Eggs, Liv's Juice Bar ...); zero employee-, manager-, time-clock- or scheduling-facing apps. TOKENISED word-boundary controls, case-insensitive, KB / RCC / Koala / site (docs hit): known-positive menu 273/110/35/125 and order(s) 294/105/39/167 (regexes work); time[-]clock 0/0/0/2; clock(ed)-in/out 0/0/0/1; timesheet|timecard 0/0/0/0; payroll 0/0/0/9; W-2|I-9 0/0/0/0; wage|hourly rate 0/0/0/2; tip pool|tip-out|tip share 0/0/0/2; fair workweek|predictive scheduling 0/0/0/1; meal|rest break 0/0/0/1; labor|labour 1/0/0/24; punch 1/0/0/10; shift(s) 3/9/8/45; overtime|over time 0/7/3/22; schedul* 29/63/3/24; employee(s) 17/1/0/8; 7shifts|Homebase|HotSchedules|Sling|Deputy|Harri|Gusto|ADP|Paychex 0/0/0/3. EVERY NON-ZERO HIT WAS READ AND CLASSIFIED, AND NONE IS A CHOWLY LABOUR SURFACE. POISON NAMED: KB `labor` = 'Labor Day' (holiday hours); KB `punch` = 'Olo, Punch or SSMA' (a data-deletion partner); site `punch` = loyalty PUNCH CARDS; KB `shift` = a UI element that 'would shift from left to right' and chargeback 'Chip Liability Shift'; RCC/Koala `shift` = floating-ui shift(), Array.prototype.shift(), shiftKey and 'shift+left' hotkeys (and `shifted`/`shifting` excluded by the token boundary); RCC/Koala `overtime` = 'over time' in chart captions and slate-editor comments; `break` = CSS/text LINE BREAKS, 'breaks of availability' in hours, and the JS `break` statement; KB `schedul*` 29 docs = scheduled (future) ORDERS, store/online-ordering hour schedules, Olo product-availability schedules, 'Schedule a Meeting with Our Team', the Stripe payout schedule and the Koala release schedule - zero employee schedules; KB `employee` 17 docs = Chowly's own support staff ('Chowly employees have no way of getting into your POS'), a POS employee ACCOUNT used to install the Chowly App on Clover, and the POS employee Chowly stamps onto an injected ticket ('orders integrating with the incorrect dining option, tender, revenue center, or employee'); RCC `employee` 1 = the RCC LOGIN ROLE `RESTAURANT_EMPLOYEE`, whose src/config.ts permittedFeaturesByRole grant is exactly five features (Manage Locations view/search/select, Resync Menus, Select Platform) - an app-user role, not an employee record; site hits are all SEO blog prose about OTHER vendors (7shifts 'time clock with break compliance, tip pooling and payouts, and payroll', resources/blogs/best-restaurant-management-software). THE APP'S OWN ENUMERATIONS CLOSE IT FOR THE RCC: src/config.ts `enum AppFeatureName` lists 23 features (Health Dashboard, 5 Analytics reports, 16 Manage Location/Platform actions, View COO Brand & Config Info) and the router's path table is Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing - no labour route. VENDOR-VOICE POSITIONING (grade C, blog 2026-06-09, https://chowly.com/resources/blogs/best-restaurant-management-software/): all-in-one platforms like Chowly 'consolidate the guest-facing side of the business - website, ordering, marketing, loyalty - into one system', while 'Most restaurants run a POS ..., an online ordering system, a scheduling tool like 7shifts, and inventory or invoice software'; and https://chowly.com/resources/blogs/restaurant-tech-stack-pays-for-itself-90-days/ tabulates the stack as 'POS | Toast/Square | Existing operational backbone' and 'Everything else | Chowly Platform | Online ordering, delivery integration, marketing, loyalty, website, analytics, AI pricing'. The site's own product menu (index) enumerates Marketing Website, Online Ordering, Google Business Profile, Google Ads, 3rd Party Integration, Email Marketing, Mobile App, Dynamic Pricing, Customer Surveys, Loyalty Program and eight AI Agents - no labour product. The only staffing-aware line is the Delivery Agent's 'Dynamic hours adjustment based on real-time staffing' (agents/delivery), which CONSUMES staffing to set marketplace hours. CONCLUSION: the labour claims do not apply to Chowly - there is no employee record, time punch, schedule, wage or tip-distribution object in any Chowly product surface we hold. CELL: the only schedule objects are order, hours, product-availability and email-campaign schedules (RCC ScheduleBuilder.tsx is the Dynamic Pricing time grid; RescheduleCampaignModal is email marketing). Retrieved 2026-09-18. https://chowly.com/chowly-platform/ · retrieved 2026-09-18 adversarially verified

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

labor-demand-labor-forecast

331st LABOUR CENSUS -> no/B. MERGE CALL: landed `no`, not held at unknown, because this record already carries five labour `no`s on the same basis (clock-in-at-pos, granular-rbac, payroll-export-formats at B; manager-override-audit, server-performance-metrics at C), and the chowly/olo scope precedent requires a category to be SETTLED `no` before it is excluded. The claim is bounded by three censused Chowly product surfaces plus the publisher app census below, not by marketing silence. FOUR CORPORA ALREADY ON DISK, EACH A CENSUS OF ONE CHOWLY SURFACE, plus one new publisher census: (1) chowly.help Salesforce Knowledge, 583/583 articles (100% of the Knowledge listing, 1.34 M chars stripped, HTML comments removed first); (2) the Restaurant Control Center chowly.app, closed /asset-manifest.json source-map set, 958 extracted sources; (3) cms.koala.io Koala Brand CMS, 910 mapped sources (580 Koala-own); (4) the rebuilt chowly.com, 167/167 sitemap pages; (5) NEW: the App Store publisher census for Chowly Inc (iTunes lookup id=1726094961&entity=software, 51 apps): every one is a white-label DINER ordering/loyalty app for a named restaurant (Muldoon Pizza, Two Eggs, Liv's Juice Bar ...); zero employee-, manager-, time-clock- or scheduling-facing apps. TOKENISED word-boundary controls, case-insensitive, KB / RCC / Koala / site (docs hit): known-positive menu 273/110/35/125 and order(s) 294/105/39/167 (regexes work); time[-]clock 0/0/0/2; clock(ed)-in/out 0/0/0/1; timesheet|timecard 0/0/0/0; payroll 0/0/0/9; W-2|I-9 0/0/0/0; wage|hourly rate 0/0/0/2; tip pool|tip-out|tip share 0/0/0/2; fair workweek|predictive scheduling 0/0/0/1; meal|rest break 0/0/0/1; labor|labour 1/0/0/24; punch 1/0/0/10; shift(s) 3/9/8/45; overtime|over time 0/7/3/22; schedul* 29/63/3/24; employee(s) 17/1/0/8; 7shifts|Homebase|HotSchedules|Sling|Deputy|Harri|Gusto|ADP|Paychex 0/0/0/3. EVERY NON-ZERO HIT WAS READ AND CLASSIFIED, AND NONE IS A CHOWLY LABOUR SURFACE. POISON NAMED: KB `labor` = 'Labor Day' (holiday hours); KB `punch` = 'Olo, Punch or SSMA' (a data-deletion partner); site `punch` = loyalty PUNCH CARDS; KB `shift` = a UI element that 'would shift from left to right' and chargeback 'Chip Liability Shift'; RCC/Koala `shift` = floating-ui shift(), Array.prototype.shift(), shiftKey and 'shift+left' hotkeys (and `shifted`/`shifting` excluded by the token boundary); RCC/Koala `overtime` = 'over time' in chart captions and slate-editor comments; `break` = CSS/text LINE BREAKS, 'breaks of availability' in hours, and the JS `break` statement; KB `schedul*` 29 docs = scheduled (future) ORDERS, store/online-ordering hour schedules, Olo product-availability schedules, 'Schedule a Meeting with Our Team', the Stripe payout schedule and the Koala release schedule - zero employee schedules; KB `employee` 17 docs = Chowly's own support staff ('Chowly employees have no way of getting into your POS'), a POS employee ACCOUNT used to install the Chowly App on Clover, and the POS employee Chowly stamps onto an injected ticket ('orders integrating with the incorrect dining option, tender, revenue center, or employee'); RCC `employee` 1 = the RCC LOGIN ROLE `RESTAURANT_EMPLOYEE`, whose src/config.ts permittedFeaturesByRole grant is exactly five features (Manage Locations view/search/select, Resync Menus, Select Platform) - an app-user role, not an employee record; site hits are all SEO blog prose about OTHER vendors (7shifts 'time clock with break compliance, tip pooling and payouts, and payroll', resources/blogs/best-restaurant-management-software). THE APP'S OWN ENUMERATIONS CLOSE IT FOR THE RCC: src/config.ts `enum AppFeatureName` lists 23 features (Health Dashboard, 5 Analytics reports, 16 Manage Location/Platform actions, View COO Brand & Config Info) and the router's path table is Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing - no labour route. VENDOR-VOICE POSITIONING (grade C, blog 2026-06-09, https://chowly.com/resources/blogs/best-restaurant-management-software/): all-in-one platforms like Chowly 'consolidate the guest-facing side of the business - website, ordering, marketing, loyalty - into one system', while 'Most restaurants run a POS ..., an online ordering system, a scheduling tool like 7shifts, and inventory or invoice software'; and https://chowly.com/resources/blogs/restaurant-tech-stack-pays-for-itself-90-days/ tabulates the stack as 'POS | Toast/Square | Existing operational backbone' and 'Everything else | Chowly Platform | Online ordering, delivery integration, marketing, loyalty, website, analytics, AI pricing'. The site's own product menu (index) enumerates Marketing Website, Online Ordering, Google Business Profile, Google Ads, 3rd Party Integration, Email Marketing, Mobile App, Dynamic Pricing, Customer Surveys, Loyalty Program and eight AI Agents - no labour product. The only staffing-aware line is the Delivery Agent's 'Dynamic hours adjustment based on real-time staffing' (agents/delivery), which CONSUMES staffing to set marketplace hours. CONCLUSION: the labour claims do not apply to Chowly - there is no employee record, time punch, schedule, wage or tip-distribution object in any Chowly product surface we hold. CELL: forecast = 0 docs in KB/RCC/Koala; the Delivery Agent reads staffing, it does not forecast labour. Retrieved 2026-09-18. https://chowly.com/chowly-platform/ · retrieved 2026-09-18 adversarially verified

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

labor-realtime-labor-percent

331st LABOUR CENSUS -> no/B. MERGE CALL: landed `no`, not held at unknown, because this record already carries five labour `no`s on the same basis (clock-in-at-pos, granular-rbac, payroll-export-formats at B; manager-override-audit, server-performance-metrics at C), and the chowly/olo scope precedent requires a category to be SETTLED `no` before it is excluded. The claim is bounded by three censused Chowly product surfaces plus the publisher app census below, not by marketing silence. FOUR CORPORA ALREADY ON DISK, EACH A CENSUS OF ONE CHOWLY SURFACE, plus one new publisher census: (1) chowly.help Salesforce Knowledge, 583/583 articles (100% of the Knowledge listing, 1.34 M chars stripped, HTML comments removed first); (2) the Restaurant Control Center chowly.app, closed /asset-manifest.json source-map set, 958 extracted sources; (3) cms.koala.io Koala Brand CMS, 910 mapped sources (580 Koala-own); (4) the rebuilt chowly.com, 167/167 sitemap pages; (5) NEW: the App Store publisher census for Chowly Inc (iTunes lookup id=1726094961&entity=software, 51 apps): every one is a white-label DINER ordering/loyalty app for a named restaurant (Muldoon Pizza, Two Eggs, Liv's Juice Bar ...); zero employee-, manager-, time-clock- or scheduling-facing apps. TOKENISED word-boundary controls, case-insensitive, KB / RCC / Koala / site (docs hit): known-positive menu 273/110/35/125 and order(s) 294/105/39/167 (regexes work); time[-]clock 0/0/0/2; clock(ed)-in/out 0/0/0/1; timesheet|timecard 0/0/0/0; payroll 0/0/0/9; W-2|I-9 0/0/0/0; wage|hourly rate 0/0/0/2; tip pool|tip-out|tip share 0/0/0/2; fair workweek|predictive scheduling 0/0/0/1; meal|rest break 0/0/0/1; labor|labour 1/0/0/24; punch 1/0/0/10; shift(s) 3/9/8/45; overtime|over time 0/7/3/22; schedul* 29/63/3/24; employee(s) 17/1/0/8; 7shifts|Homebase|HotSchedules|Sling|Deputy|Harri|Gusto|ADP|Paychex 0/0/0/3. EVERY NON-ZERO HIT WAS READ AND CLASSIFIED, AND NONE IS A CHOWLY LABOUR SURFACE. POISON NAMED: KB `labor` = 'Labor Day' (holiday hours); KB `punch` = 'Olo, Punch or SSMA' (a data-deletion partner); site `punch` = loyalty PUNCH CARDS; KB `shift` = a UI element that 'would shift from left to right' and chargeback 'Chip Liability Shift'; RCC/Koala `shift` = floating-ui shift(), Array.prototype.shift(), shiftKey and 'shift+left' hotkeys (and `shifted`/`shifting` excluded by the token boundary); RCC/Koala `overtime` = 'over time' in chart captions and slate-editor comments; `break` = CSS/text LINE BREAKS, 'breaks of availability' in hours, and the JS `break` statement; KB `schedul*` 29 docs = scheduled (future) ORDERS, store/online-ordering hour schedules, Olo product-availability schedules, 'Schedule a Meeting with Our Team', the Stripe payout schedule and the Koala release schedule - zero employee schedules; KB `employee` 17 docs = Chowly's own support staff ('Chowly employees have no way of getting into your POS'), a POS employee ACCOUNT used to install the Chowly App on Clover, and the POS employee Chowly stamps onto an injected ticket ('orders integrating with the incorrect dining option, tender, revenue center, or employee'); RCC `employee` 1 = the RCC LOGIN ROLE `RESTAURANT_EMPLOYEE`, whose src/config.ts permittedFeaturesByRole grant is exactly five features (Manage Locations view/search/select, Resync Menus, Select Platform) - an app-user role, not an employee record; site hits are all SEO blog prose about OTHER vendors (7shifts 'time clock with break compliance, tip pooling and payouts, and payroll', resources/blogs/best-restaurant-management-software). THE APP'S OWN ENUMERATIONS CLOSE IT FOR THE RCC: src/config.ts `enum AppFeatureName` lists 23 features (Health Dashboard, 5 Analytics reports, 16 Manage Location/Platform actions, View COO Brand & Config Info) and the router's path table is Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing - no labour route. VENDOR-VOICE POSITIONING (grade C, blog 2026-06-09, https://chowly.com/resources/blogs/best-restaurant-management-software/): all-in-one platforms like Chowly 'consolidate the guest-facing side of the business - website, ordering, marketing, loyalty - into one system', while 'Most restaurants run a POS ..., an online ordering system, a scheduling tool like 7shifts, and inventory or invoice software'; and https://chowly.com/resources/blogs/restaurant-tech-stack-pays-for-itself-90-days/ tabulates the stack as 'POS | Toast/Square | Existing operational backbone' and 'Everything else | Chowly Platform | Online ordering, delivery integration, marketing, loyalty, website, analytics, AI pricing'. The site's own product menu (index) enumerates Marketing Website, Online Ordering, Google Business Profile, Google Ads, 3rd Party Integration, Email Marketing, Mobile App, Dynamic Pricing, Customer Surveys, Loyalty Program and eight AI Agents - no labour product. The only staffing-aware line is the Delivery Agent's 'Dynamic hours adjustment based on real-time staffing' (agents/delivery), which CONSUMES staffing to set marketplace hours. CONCLUSION: the labour claims do not apply to Chowly - there is no employee record, time punch, schedule, wage or tip-distribution object in any Chowly product surface we hold. CELL: the RCC reporting index (ten pages, sixteen Sigma embeds, recorded in the 325th) carries no labour page; no wage or hours field exists to divide by sales. Retrieved 2026-09-18. https://chowly.com/chowly-platform/ · retrieved 2026-09-18 adversarially verified

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

labor-overtime-prevention

331st LABOUR CENSUS -> no/B. MERGE CALL: landed `no`, not held at unknown, because this record already carries five labour `no`s on the same basis (clock-in-at-pos, granular-rbac, payroll-export-formats at B; manager-override-audit, server-performance-metrics at C), and the chowly/olo scope precedent requires a category to be SETTLED `no` before it is excluded. The claim is bounded by three censused Chowly product surfaces plus the publisher app census below, not by marketing silence. FOUR CORPORA ALREADY ON DISK, EACH A CENSUS OF ONE CHOWLY SURFACE, plus one new publisher census: (1) chowly.help Salesforce Knowledge, 583/583 articles (100% of the Knowledge listing, 1.34 M chars stripped, HTML comments removed first); (2) the Restaurant Control Center chowly.app, closed /asset-manifest.json source-map set, 958 extracted sources; (3) cms.koala.io Koala Brand CMS, 910 mapped sources (580 Koala-own); (4) the rebuilt chowly.com, 167/167 sitemap pages; (5) NEW: the App Store publisher census for Chowly Inc (iTunes lookup id=1726094961&entity=software, 51 apps): every one is a white-label DINER ordering/loyalty app for a named restaurant (Muldoon Pizza, Two Eggs, Liv's Juice Bar ...); zero employee-, manager-, time-clock- or scheduling-facing apps. TOKENISED word-boundary controls, case-insensitive, KB / RCC / Koala / site (docs hit): known-positive menu 273/110/35/125 and order(s) 294/105/39/167 (regexes work); time[-]clock 0/0/0/2; clock(ed)-in/out 0/0/0/1; timesheet|timecard 0/0/0/0; payroll 0/0/0/9; W-2|I-9 0/0/0/0; wage|hourly rate 0/0/0/2; tip pool|tip-out|tip share 0/0/0/2; fair workweek|predictive scheduling 0/0/0/1; meal|rest break 0/0/0/1; labor|labour 1/0/0/24; punch 1/0/0/10; shift(s) 3/9/8/45; overtime|over time 0/7/3/22; schedul* 29/63/3/24; employee(s) 17/1/0/8; 7shifts|Homebase|HotSchedules|Sling|Deputy|Harri|Gusto|ADP|Paychex 0/0/0/3. EVERY NON-ZERO HIT WAS READ AND CLASSIFIED, AND NONE IS A CHOWLY LABOUR SURFACE. POISON NAMED: KB `labor` = 'Labor Day' (holiday hours); KB `punch` = 'Olo, Punch or SSMA' (a data-deletion partner); site `punch` = loyalty PUNCH CARDS; KB `shift` = a UI element that 'would shift from left to right' and chargeback 'Chip Liability Shift'; RCC/Koala `shift` = floating-ui shift(), Array.prototype.shift(), shiftKey and 'shift+left' hotkeys (and `shifted`/`shifting` excluded by the token boundary); RCC/Koala `overtime` = 'over time' in chart captions and slate-editor comments; `break` = CSS/text LINE BREAKS, 'breaks of availability' in hours, and the JS `break` statement; KB `schedul*` 29 docs = scheduled (future) ORDERS, store/online-ordering hour schedules, Olo product-availability schedules, 'Schedule a Meeting with Our Team', the Stripe payout schedule and the Koala release schedule - zero employee schedules; KB `employee` 17 docs = Chowly's own support staff ('Chowly employees have no way of getting into your POS'), a POS employee ACCOUNT used to install the Chowly App on Clover, and the POS employee Chowly stamps onto an injected ticket ('orders integrating with the incorrect dining option, tender, revenue center, or employee'); RCC `employee` 1 = the RCC LOGIN ROLE `RESTAURANT_EMPLOYEE`, whose src/config.ts permittedFeaturesByRole grant is exactly five features (Manage Locations view/search/select, Resync Menus, Select Platform) - an app-user role, not an employee record; site hits are all SEO blog prose about OTHER vendors (7shifts 'time clock with break compliance, tip pooling and payouts, and payroll', resources/blogs/best-restaurant-management-software). THE APP'S OWN ENUMERATIONS CLOSE IT FOR THE RCC: src/config.ts `enum AppFeatureName` lists 23 features (Health Dashboard, 5 Analytics reports, 16 Manage Location/Platform actions, View COO Brand & Config Info) and the router's path table is Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing - no labour route. VENDOR-VOICE POSITIONING (grade C, blog 2026-06-09, https://chowly.com/resources/blogs/best-restaurant-management-software/): all-in-one platforms like Chowly 'consolidate the guest-facing side of the business - website, ordering, marketing, loyalty - into one system', while 'Most restaurants run a POS ..., an online ordering system, a scheduling tool like 7shifts, and inventory or invoice software'; and https://chowly.com/resources/blogs/restaurant-tech-stack-pays-for-itself-90-days/ tabulates the stack as 'POS | Toast/Square | Existing operational backbone' and 'Everything else | Chowly Platform | Online ordering, delivery integration, marketing, loyalty, website, analytics, AI pricing'. The site's own product menu (index) enumerates Marketing Website, Online Ordering, Google Business Profile, Google Ads, 3rd Party Integration, Email Marketing, Mobile App, Dynamic Pricing, Customer Surveys, Loyalty Program and eight AI Agents - no labour product. The only staffing-aware line is the Delivery Agent's 'Dynamic hours adjustment based on real-time staffing' (agents/delivery), which CONSUMES staffing to set marketplace hours. CONCLUSION: the labour claims do not apply to Chowly - there is no employee record, time punch, schedule, wage or tip-distribution object in any Chowly product surface we hold. CELL: every overtime-token hit is the phrase over time (poison above). Retrieved 2026-09-18. https://chowly.com/chowly-platform/ · retrieved 2026-09-18 adversarially verified

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

labor-break-compliance-by-state

331st LABOUR CENSUS -> no/B. MERGE CALL: landed `no`, not held at unknown, because this record already carries five labour `no`s on the same basis (clock-in-at-pos, granular-rbac, payroll-export-formats at B; manager-override-audit, server-performance-metrics at C), and the chowly/olo scope precedent requires a category to be SETTLED `no` before it is excluded. The claim is bounded by three censused Chowly product surfaces plus the publisher app census below, not by marketing silence. FOUR CORPORA ALREADY ON DISK, EACH A CENSUS OF ONE CHOWLY SURFACE, plus one new publisher census: (1) chowly.help Salesforce Knowledge, 583/583 articles (100% of the Knowledge listing, 1.34 M chars stripped, HTML comments removed first); (2) the Restaurant Control Center chowly.app, closed /asset-manifest.json source-map set, 958 extracted sources; (3) cms.koala.io Koala Brand CMS, 910 mapped sources (580 Koala-own); (4) the rebuilt chowly.com, 167/167 sitemap pages; (5) NEW: the App Store publisher census for Chowly Inc (iTunes lookup id=1726094961&entity=software, 51 apps): every one is a white-label DINER ordering/loyalty app for a named restaurant (Muldoon Pizza, Two Eggs, Liv's Juice Bar ...); zero employee-, manager-, time-clock- or scheduling-facing apps. TOKENISED word-boundary controls, case-insensitive, KB / RCC / Koala / site (docs hit): known-positive menu 273/110/35/125 and order(s) 294/105/39/167 (regexes work); time[-]clock 0/0/0/2; clock(ed)-in/out 0/0/0/1; timesheet|timecard 0/0/0/0; payroll 0/0/0/9; W-2|I-9 0/0/0/0; wage|hourly rate 0/0/0/2; tip pool|tip-out|tip share 0/0/0/2; fair workweek|predictive scheduling 0/0/0/1; meal|rest break 0/0/0/1; labor|labour 1/0/0/24; punch 1/0/0/10; shift(s) 3/9/8/45; overtime|over time 0/7/3/22; schedul* 29/63/3/24; employee(s) 17/1/0/8; 7shifts|Homebase|HotSchedules|Sling|Deputy|Harri|Gusto|ADP|Paychex 0/0/0/3. EVERY NON-ZERO HIT WAS READ AND CLASSIFIED, AND NONE IS A CHOWLY LABOUR SURFACE. POISON NAMED: KB `labor` = 'Labor Day' (holiday hours); KB `punch` = 'Olo, Punch or SSMA' (a data-deletion partner); site `punch` = loyalty PUNCH CARDS; KB `shift` = a UI element that 'would shift from left to right' and chargeback 'Chip Liability Shift'; RCC/Koala `shift` = floating-ui shift(), Array.prototype.shift(), shiftKey and 'shift+left' hotkeys (and `shifted`/`shifting` excluded by the token boundary); RCC/Koala `overtime` = 'over time' in chart captions and slate-editor comments; `break` = CSS/text LINE BREAKS, 'breaks of availability' in hours, and the JS `break` statement; KB `schedul*` 29 docs = scheduled (future) ORDERS, store/online-ordering hour schedules, Olo product-availability schedules, 'Schedule a Meeting with Our Team', the Stripe payout schedule and the Koala release schedule - zero employee schedules; KB `employee` 17 docs = Chowly's own support staff ('Chowly employees have no way of getting into your POS'), a POS employee ACCOUNT used to install the Chowly App on Clover, and the POS employee Chowly stamps onto an injected ticket ('orders integrating with the incorrect dining option, tender, revenue center, or employee'); RCC `employee` 1 = the RCC LOGIN ROLE `RESTAURANT_EMPLOYEE`, whose src/config.ts permittedFeaturesByRole grant is exactly five features (Manage Locations view/search/select, Resync Menus, Select Platform) - an app-user role, not an employee record; site hits are all SEO blog prose about OTHER vendors (7shifts 'time clock with break compliance, tip pooling and payouts, and payroll', resources/blogs/best-restaurant-management-software). THE APP'S OWN ENUMERATIONS CLOSE IT FOR THE RCC: src/config.ts `enum AppFeatureName` lists 23 features (Health Dashboard, 5 Analytics reports, 16 Manage Location/Platform actions, View COO Brand & Config Info) and the router's path table is Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing - no labour route. VENDOR-VOICE POSITIONING (grade C, blog 2026-06-09, https://chowly.com/resources/blogs/best-restaurant-management-software/): all-in-one platforms like Chowly 'consolidate the guest-facing side of the business - website, ordering, marketing, loyalty - into one system', while 'Most restaurants run a POS ..., an online ordering system, a scheduling tool like 7shifts, and inventory or invoice software'; and https://chowly.com/resources/blogs/restaurant-tech-stack-pays-for-itself-90-days/ tabulates the stack as 'POS | Toast/Square | Existing operational backbone' and 'Everything else | Chowly Platform | Online ordering, delivery integration, marketing, loyalty, website, analytics, AI pricing'. The site's own product menu (index) enumerates Marketing Website, Online Ordering, Google Business Profile, Google Ads, 3rd Party Integration, Email Marketing, Mobile App, Dynamic Pricing, Customer Surveys, Loyalty Program and eight AI Agents - no labour product. The only staffing-aware line is the Delivery Agent's 'Dynamic hours adjustment based on real-time staffing' (agents/delivery), which CONSUMES staffing to set marketplace hours. CONCLUSION: the labour claims do not apply to Chowly - there is no employee record, time punch, schedule, wage or tip-distribution object in any Chowly product surface we hold. CELL: meal|rest break = 0 in KB/RCC/Koala; the one site hit is 7shifts. Retrieved 2026-09-18. https://chowly.com/chowly-platform/ · retrieved 2026-09-18 adversarially verified

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

labor-fair-workweek-support

331st LABOUR CENSUS -> no/B. MERGE CALL: landed `no`, not held at unknown, because this record already carries five labour `no`s on the same basis (clock-in-at-pos, granular-rbac, payroll-export-formats at B; manager-override-audit, server-performance-metrics at C), and the chowly/olo scope precedent requires a category to be SETTLED `no` before it is excluded. The claim is bounded by three censused Chowly product surfaces plus the publisher app census below, not by marketing silence. FOUR CORPORA ALREADY ON DISK, EACH A CENSUS OF ONE CHOWLY SURFACE, plus one new publisher census: (1) chowly.help Salesforce Knowledge, 583/583 articles (100% of the Knowledge listing, 1.34 M chars stripped, HTML comments removed first); (2) the Restaurant Control Center chowly.app, closed /asset-manifest.json source-map set, 958 extracted sources; (3) cms.koala.io Koala Brand CMS, 910 mapped sources (580 Koala-own); (4) the rebuilt chowly.com, 167/167 sitemap pages; (5) NEW: the App Store publisher census for Chowly Inc (iTunes lookup id=1726094961&entity=software, 51 apps): every one is a white-label DINER ordering/loyalty app for a named restaurant (Muldoon Pizza, Two Eggs, Liv's Juice Bar ...); zero employee-, manager-, time-clock- or scheduling-facing apps. TOKENISED word-boundary controls, case-insensitive, KB / RCC / Koala / site (docs hit): known-positive menu 273/110/35/125 and order(s) 294/105/39/167 (regexes work); time[-]clock 0/0/0/2; clock(ed)-in/out 0/0/0/1; timesheet|timecard 0/0/0/0; payroll 0/0/0/9; W-2|I-9 0/0/0/0; wage|hourly rate 0/0/0/2; tip pool|tip-out|tip share 0/0/0/2; fair workweek|predictive scheduling 0/0/0/1; meal|rest break 0/0/0/1; labor|labour 1/0/0/24; punch 1/0/0/10; shift(s) 3/9/8/45; overtime|over time 0/7/3/22; schedul* 29/63/3/24; employee(s) 17/1/0/8; 7shifts|Homebase|HotSchedules|Sling|Deputy|Harri|Gusto|ADP|Paychex 0/0/0/3. EVERY NON-ZERO HIT WAS READ AND CLASSIFIED, AND NONE IS A CHOWLY LABOUR SURFACE. POISON NAMED: KB `labor` = 'Labor Day' (holiday hours); KB `punch` = 'Olo, Punch or SSMA' (a data-deletion partner); site `punch` = loyalty PUNCH CARDS; KB `shift` = a UI element that 'would shift from left to right' and chargeback 'Chip Liability Shift'; RCC/Koala `shift` = floating-ui shift(), Array.prototype.shift(), shiftKey and 'shift+left' hotkeys (and `shifted`/`shifting` excluded by the token boundary); RCC/Koala `overtime` = 'over time' in chart captions and slate-editor comments; `break` = CSS/text LINE BREAKS, 'breaks of availability' in hours, and the JS `break` statement; KB `schedul*` 29 docs = scheduled (future) ORDERS, store/online-ordering hour schedules, Olo product-availability schedules, 'Schedule a Meeting with Our Team', the Stripe payout schedule and the Koala release schedule - zero employee schedules; KB `employee` 17 docs = Chowly's own support staff ('Chowly employees have no way of getting into your POS'), a POS employee ACCOUNT used to install the Chowly App on Clover, and the POS employee Chowly stamps onto an injected ticket ('orders integrating with the incorrect dining option, tender, revenue center, or employee'); RCC `employee` 1 = the RCC LOGIN ROLE `RESTAURANT_EMPLOYEE`, whose src/config.ts permittedFeaturesByRole grant is exactly five features (Manage Locations view/search/select, Resync Menus, Select Platform) - an app-user role, not an employee record; site hits are all SEO blog prose about OTHER vendors (7shifts 'time clock with break compliance, tip pooling and payouts, and payroll', resources/blogs/best-restaurant-management-software). THE APP'S OWN ENUMERATIONS CLOSE IT FOR THE RCC: src/config.ts `enum AppFeatureName` lists 23 features (Health Dashboard, 5 Analytics reports, 16 Manage Location/Platform actions, View COO Brand & Config Info) and the router's path table is Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing - no labour route. VENDOR-VOICE POSITIONING (grade C, blog 2026-06-09, https://chowly.com/resources/blogs/best-restaurant-management-software/): all-in-one platforms like Chowly 'consolidate the guest-facing side of the business - website, ordering, marketing, loyalty - into one system', while 'Most restaurants run a POS ..., an online ordering system, a scheduling tool like 7shifts, and inventory or invoice software'; and https://chowly.com/resources/blogs/restaurant-tech-stack-pays-for-itself-90-days/ tabulates the stack as 'POS | Toast/Square | Existing operational backbone' and 'Everything else | Chowly Platform | Online ordering, delivery integration, marketing, loyalty, website, analytics, AI pricing'. The site's own product menu (index) enumerates Marketing Website, Online Ordering, Google Business Profile, Google Ads, 3rd Party Integration, Email Marketing, Mobile App, Dynamic Pricing, Customer Surveys, Loyalty Program and eight AI Agents - no labour product. The only staffing-aware line is the Delivery Agent's 'Dynamic hours adjustment based on real-time staffing' (agents/delivery), which CONSUMES staffing to set marketplace hours. CONCLUSION: the labour claims do not apply to Chowly - there is no employee record, time punch, schedule, wage or tip-distribution object in any Chowly product surface we hold. CELL: fair workweek|predictive scheduling = 0 in KB/RCC/Koala; the one site hit is generic blog prose. Retrieved 2026-09-18. https://chowly.com/chowly-platform/ · retrieved 2026-09-18 adversarially verified

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

labor-minor-labor-rules

331st LABOUR CENSUS -> no/B. MERGE CALL: landed `no`, not held at unknown, because this record already carries five labour `no`s on the same basis (clock-in-at-pos, granular-rbac, payroll-export-formats at B; manager-override-audit, server-performance-metrics at C), and the chowly/olo scope precedent requires a category to be SETTLED `no` before it is excluded. The claim is bounded by three censused Chowly product surfaces plus the publisher app census below, not by marketing silence. FOUR CORPORA ALREADY ON DISK, EACH A CENSUS OF ONE CHOWLY SURFACE, plus one new publisher census: (1) chowly.help Salesforce Knowledge, 583/583 articles (100% of the Knowledge listing, 1.34 M chars stripped, HTML comments removed first); (2) the Restaurant Control Center chowly.app, closed /asset-manifest.json source-map set, 958 extracted sources; (3) cms.koala.io Koala Brand CMS, 910 mapped sources (580 Koala-own); (4) the rebuilt chowly.com, 167/167 sitemap pages; (5) NEW: the App Store publisher census for Chowly Inc (iTunes lookup id=1726094961&entity=software, 51 apps): every one is a white-label DINER ordering/loyalty app for a named restaurant (Muldoon Pizza, Two Eggs, Liv's Juice Bar ...); zero employee-, manager-, time-clock- or scheduling-facing apps. TOKENISED word-boundary controls, case-insensitive, KB / RCC / Koala / site (docs hit): known-positive menu 273/110/35/125 and order(s) 294/105/39/167 (regexes work); time[-]clock 0/0/0/2; clock(ed)-in/out 0/0/0/1; timesheet|timecard 0/0/0/0; payroll 0/0/0/9; W-2|I-9 0/0/0/0; wage|hourly rate 0/0/0/2; tip pool|tip-out|tip share 0/0/0/2; fair workweek|predictive scheduling 0/0/0/1; meal|rest break 0/0/0/1; labor|labour 1/0/0/24; punch 1/0/0/10; shift(s) 3/9/8/45; overtime|over time 0/7/3/22; schedul* 29/63/3/24; employee(s) 17/1/0/8; 7shifts|Homebase|HotSchedules|Sling|Deputy|Harri|Gusto|ADP|Paychex 0/0/0/3. EVERY NON-ZERO HIT WAS READ AND CLASSIFIED, AND NONE IS A CHOWLY LABOUR SURFACE. POISON NAMED: KB `labor` = 'Labor Day' (holiday hours); KB `punch` = 'Olo, Punch or SSMA' (a data-deletion partner); site `punch` = loyalty PUNCH CARDS; KB `shift` = a UI element that 'would shift from left to right' and chargeback 'Chip Liability Shift'; RCC/Koala `shift` = floating-ui shift(), Array.prototype.shift(), shiftKey and 'shift+left' hotkeys (and `shifted`/`shifting` excluded by the token boundary); RCC/Koala `overtime` = 'over time' in chart captions and slate-editor comments; `break` = CSS/text LINE BREAKS, 'breaks of availability' in hours, and the JS `break` statement; KB `schedul*` 29 docs = scheduled (future) ORDERS, store/online-ordering hour schedules, Olo product-availability schedules, 'Schedule a Meeting with Our Team', the Stripe payout schedule and the Koala release schedule - zero employee schedules; KB `employee` 17 docs = Chowly's own support staff ('Chowly employees have no way of getting into your POS'), a POS employee ACCOUNT used to install the Chowly App on Clover, and the POS employee Chowly stamps onto an injected ticket ('orders integrating with the incorrect dining option, tender, revenue center, or employee'); RCC `employee` 1 = the RCC LOGIN ROLE `RESTAURANT_EMPLOYEE`, whose src/config.ts permittedFeaturesByRole grant is exactly five features (Manage Locations view/search/select, Resync Menus, Select Platform) - an app-user role, not an employee record; site hits are all SEO blog prose about OTHER vendors (7shifts 'time clock with break compliance, tip pooling and payouts, and payroll', resources/blogs/best-restaurant-management-software). THE APP'S OWN ENUMERATIONS CLOSE IT FOR THE RCC: src/config.ts `enum AppFeatureName` lists 23 features (Health Dashboard, 5 Analytics reports, 16 Manage Location/Platform actions, View COO Brand & Config Info) and the router's path table is Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing - no labour route. VENDOR-VOICE POSITIONING (grade C, blog 2026-06-09, https://chowly.com/resources/blogs/best-restaurant-management-software/): all-in-one platforms like Chowly 'consolidate the guest-facing side of the business - website, ordering, marketing, loyalty - into one system', while 'Most restaurants run a POS ..., an online ordering system, a scheduling tool like 7shifts, and inventory or invoice software'; and https://chowly.com/resources/blogs/restaurant-tech-stack-pays-for-itself-90-days/ tabulates the stack as 'POS | Toast/Square | Existing operational backbone' and 'Everything else | Chowly Platform | Online ordering, delivery integration, marketing, loyalty, website, analytics, AI pricing'. The site's own product menu (index) enumerates Marketing Website, Online Ordering, Google Business Profile, Google Ads, 3rd Party Integration, Email Marketing, Mobile App, Dynamic Pricing, Customer Surveys, Loyalty Program and eight AI Agents - no labour product. The only staffing-aware line is the Delivery Agent's 'Dynamic hours adjustment based on real-time staffing' (agents/delivery), which CONSUMES staffing to set marketplace hours. CONCLUSION: the labour claims do not apply to Chowly - there is no employee record, time punch, schedule, wage or tip-distribution object in any Chowly product surface we hold. CELL: no employee record with a date of birth exists in any corpus; the kiosk age check is an alcohol ID check of a guest. Retrieved 2026-09-18. https://chowly.com/chowly-platform/ · retrieved 2026-09-18 adversarially verified

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

labor-tip-pooling-rules

331st LABOUR CENSUS -> no/B. MERGE CALL: landed `no`, not held at unknown, because this record already carries five labour `no`s on the same basis (clock-in-at-pos, granular-rbac, payroll-export-formats at B; manager-override-audit, server-performance-metrics at C), and the chowly/olo scope precedent requires a category to be SETTLED `no` before it is excluded. The claim is bounded by three censused Chowly product surfaces plus the publisher app census below, not by marketing silence. FOUR CORPORA ALREADY ON DISK, EACH A CENSUS OF ONE CHOWLY SURFACE, plus one new publisher census: (1) chowly.help Salesforce Knowledge, 583/583 articles (100% of the Knowledge listing, 1.34 M chars stripped, HTML comments removed first); (2) the Restaurant Control Center chowly.app, closed /asset-manifest.json source-map set, 958 extracted sources; (3) cms.koala.io Koala Brand CMS, 910 mapped sources (580 Koala-own); (4) the rebuilt chowly.com, 167/167 sitemap pages; (5) NEW: the App Store publisher census for Chowly Inc (iTunes lookup id=1726094961&entity=software, 51 apps): every one is a white-label DINER ordering/loyalty app for a named restaurant (Muldoon Pizza, Two Eggs, Liv's Juice Bar ...); zero employee-, manager-, time-clock- or scheduling-facing apps. TOKENISED word-boundary controls, case-insensitive, KB / RCC / Koala / site (docs hit): known-positive menu 273/110/35/125 and order(s) 294/105/39/167 (regexes work); time[-]clock 0/0/0/2; clock(ed)-in/out 0/0/0/1; timesheet|timecard 0/0/0/0; payroll 0/0/0/9; W-2|I-9 0/0/0/0; wage|hourly rate 0/0/0/2; tip pool|tip-out|tip share 0/0/0/2; fair workweek|predictive scheduling 0/0/0/1; meal|rest break 0/0/0/1; labor|labour 1/0/0/24; punch 1/0/0/10; shift(s) 3/9/8/45; overtime|over time 0/7/3/22; schedul* 29/63/3/24; employee(s) 17/1/0/8; 7shifts|Homebase|HotSchedules|Sling|Deputy|Harri|Gusto|ADP|Paychex 0/0/0/3. EVERY NON-ZERO HIT WAS READ AND CLASSIFIED, AND NONE IS A CHOWLY LABOUR SURFACE. POISON NAMED: KB `labor` = 'Labor Day' (holiday hours); KB `punch` = 'Olo, Punch or SSMA' (a data-deletion partner); site `punch` = loyalty PUNCH CARDS; KB `shift` = a UI element that 'would shift from left to right' and chargeback 'Chip Liability Shift'; RCC/Koala `shift` = floating-ui shift(), Array.prototype.shift(), shiftKey and 'shift+left' hotkeys (and `shifted`/`shifting` excluded by the token boundary); RCC/Koala `overtime` = 'over time' in chart captions and slate-editor comments; `break` = CSS/text LINE BREAKS, 'breaks of availability' in hours, and the JS `break` statement; KB `schedul*` 29 docs = scheduled (future) ORDERS, store/online-ordering hour schedules, Olo product-availability schedules, 'Schedule a Meeting with Our Team', the Stripe payout schedule and the Koala release schedule - zero employee schedules; KB `employee` 17 docs = Chowly's own support staff ('Chowly employees have no way of getting into your POS'), a POS employee ACCOUNT used to install the Chowly App on Clover, and the POS employee Chowly stamps onto an injected ticket ('orders integrating with the incorrect dining option, tender, revenue center, or employee'); RCC `employee` 1 = the RCC LOGIN ROLE `RESTAURANT_EMPLOYEE`, whose src/config.ts permittedFeaturesByRole grant is exactly five features (Manage Locations view/search/select, Resync Menus, Select Platform) - an app-user role, not an employee record; site hits are all SEO blog prose about OTHER vendors (7shifts 'time clock with break compliance, tip pooling and payouts, and payroll', resources/blogs/best-restaurant-management-software). THE APP'S OWN ENUMERATIONS CLOSE IT FOR THE RCC: src/config.ts `enum AppFeatureName` lists 23 features (Health Dashboard, 5 Analytics reports, 16 Manage Location/Platform actions, View COO Brand & Config Info) and the router's path table is Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing - no labour route. VENDOR-VOICE POSITIONING (grade C, blog 2026-06-09, https://chowly.com/resources/blogs/best-restaurant-management-software/): all-in-one platforms like Chowly 'consolidate the guest-facing side of the business - website, ordering, marketing, loyalty - into one system', while 'Most restaurants run a POS ..., an online ordering system, a scheduling tool like 7shifts, and inventory or invoice software'; and https://chowly.com/resources/blogs/restaurant-tech-stack-pays-for-itself-90-days/ tabulates the stack as 'POS | Toast/Square | Existing operational backbone' and 'Everything else | Chowly Platform | Online ordering, delivery integration, marketing, loyalty, website, analytics, AI pricing'. The site's own product menu (index) enumerates Marketing Website, Online Ordering, Google Business Profile, Google Ads, 3rd Party Integration, Email Marketing, Mobile App, Dynamic Pricing, Customer Surveys, Loyalty Program and eight AI Agents - no labour product. The only staffing-aware line is the Delivery Agent's 'Dynamic hours adjustment based on real-time staffing' (agents/delivery), which CONSUMES staffing to set marketplace hours. CONCLUSION: the labour claims do not apply to Chowly - there is no employee record, time punch, schedule, wage or tip-distribution object in any Chowly product surface we hold. CELL: tip is a diner-entered gratuity forwarded to the POS ticket; tip-pool tokens = 0 in KB/RCC/Koala; RCC tip hits are an order-level money field (api/orderManagement/types.ts `tip`, summed with delivery_fee in RefundModal and OrderOverflowPopover) plus a map-pin "tip". Retrieved 2026-09-18. https://chowly.com/chowly-platform/ · retrieved 2026-09-18 adversarially verified

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

labor-tip-distribution-audit-trail

331st LABOUR CENSUS -> no/B. MERGE CALL: landed `no`, not held at unknown, because this record already carries five labour `no`s on the same basis (clock-in-at-pos, granular-rbac, payroll-export-formats at B; manager-override-audit, server-performance-metrics at C), and the chowly/olo scope precedent requires a category to be SETTLED `no` before it is excluded. The claim is bounded by three censused Chowly product surfaces plus the publisher app census below, not by marketing silence. FOUR CORPORA ALREADY ON DISK, EACH A CENSUS OF ONE CHOWLY SURFACE, plus one new publisher census: (1) chowly.help Salesforce Knowledge, 583/583 articles (100% of the Knowledge listing, 1.34 M chars stripped, HTML comments removed first); (2) the Restaurant Control Center chowly.app, closed /asset-manifest.json source-map set, 958 extracted sources; (3) cms.koala.io Koala Brand CMS, 910 mapped sources (580 Koala-own); (4) the rebuilt chowly.com, 167/167 sitemap pages; (5) NEW: the App Store publisher census for Chowly Inc (iTunes lookup id=1726094961&entity=software, 51 apps): every one is a white-label DINER ordering/loyalty app for a named restaurant (Muldoon Pizza, Two Eggs, Liv's Juice Bar ...); zero employee-, manager-, time-clock- or scheduling-facing apps. TOKENISED word-boundary controls, case-insensitive, KB / RCC / Koala / site (docs hit): known-positive menu 273/110/35/125 and order(s) 294/105/39/167 (regexes work); time[-]clock 0/0/0/2; clock(ed)-in/out 0/0/0/1; timesheet|timecard 0/0/0/0; payroll 0/0/0/9; W-2|I-9 0/0/0/0; wage|hourly rate 0/0/0/2; tip pool|tip-out|tip share 0/0/0/2; fair workweek|predictive scheduling 0/0/0/1; meal|rest break 0/0/0/1; labor|labour 1/0/0/24; punch 1/0/0/10; shift(s) 3/9/8/45; overtime|over time 0/7/3/22; schedul* 29/63/3/24; employee(s) 17/1/0/8; 7shifts|Homebase|HotSchedules|Sling|Deputy|Harri|Gusto|ADP|Paychex 0/0/0/3. EVERY NON-ZERO HIT WAS READ AND CLASSIFIED, AND NONE IS A CHOWLY LABOUR SURFACE. POISON NAMED: KB `labor` = 'Labor Day' (holiday hours); KB `punch` = 'Olo, Punch or SSMA' (a data-deletion partner); site `punch` = loyalty PUNCH CARDS; KB `shift` = a UI element that 'would shift from left to right' and chargeback 'Chip Liability Shift'; RCC/Koala `shift` = floating-ui shift(), Array.prototype.shift(), shiftKey and 'shift+left' hotkeys (and `shifted`/`shifting` excluded by the token boundary); RCC/Koala `overtime` = 'over time' in chart captions and slate-editor comments; `break` = CSS/text LINE BREAKS, 'breaks of availability' in hours, and the JS `break` statement; KB `schedul*` 29 docs = scheduled (future) ORDERS, store/online-ordering hour schedules, Olo product-availability schedules, 'Schedule a Meeting with Our Team', the Stripe payout schedule and the Koala release schedule - zero employee schedules; KB `employee` 17 docs = Chowly's own support staff ('Chowly employees have no way of getting into your POS'), a POS employee ACCOUNT used to install the Chowly App on Clover, and the POS employee Chowly stamps onto an injected ticket ('orders integrating with the incorrect dining option, tender, revenue center, or employee'); RCC `employee` 1 = the RCC LOGIN ROLE `RESTAURANT_EMPLOYEE`, whose src/config.ts permittedFeaturesByRole grant is exactly five features (Manage Locations view/search/select, Resync Menus, Select Platform) - an app-user role, not an employee record; site hits are all SEO blog prose about OTHER vendors (7shifts 'time clock with break compliance, tip pooling and payouts, and payroll', resources/blogs/best-restaurant-management-software). THE APP'S OWN ENUMERATIONS CLOSE IT FOR THE RCC: src/config.ts `enum AppFeatureName` lists 23 features (Health Dashboard, 5 Analytics reports, 16 Manage Location/Platform actions, View COO Brand & Config Info) and the router's path table is Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing - no labour route. VENDOR-VOICE POSITIONING (grade C, blog 2026-06-09, https://chowly.com/resources/blogs/best-restaurant-management-software/): all-in-one platforms like Chowly 'consolidate the guest-facing side of the business - website, ordering, marketing, loyalty - into one system', while 'Most restaurants run a POS ..., an online ordering system, a scheduling tool like 7shifts, and inventory or invoice software'; and https://chowly.com/resources/blogs/restaurant-tech-stack-pays-for-itself-90-days/ tabulates the stack as 'POS | Toast/Square | Existing operational backbone' and 'Everything else | Chowly Platform | Online ordering, delivery integration, marketing, loyalty, website, analytics, AI pricing'. The site's own product menu (index) enumerates Marketing Website, Online Ordering, Google Business Profile, Google Ads, 3rd Party Integration, Email Marketing, Mobile App, Dynamic Pricing, Customer Surveys, Loyalty Program and eight AI Agents - no labour product. The only staffing-aware line is the Delivery Agent's 'Dynamic hours adjustment based on real-time staffing' (agents/delivery), which CONSUMES staffing to set marketplace hours. CONCLUSION: the labour claims do not apply to Chowly - there is no employee record, time punch, schedule, wage or tip-distribution object in any Chowly product surface we hold. CELL: no tip is distributed to any employee inside Chowly; tip-pool tokens = 0 in KB/RCC/Koala. Retrieved 2026-09-18. https://chowly.com/chowly-platform/ · retrieved 2026-09-18 adversarially verified

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

labor-qualified-tips-w2-reporting

331st LABOUR CENSUS -> no/B. MERGE CALL: landed `no`, not held at unknown, because this record already carries five labour `no`s on the same basis (clock-in-at-pos, granular-rbac, payroll-export-formats at B; manager-override-audit, server-performance-metrics at C), and the chowly/olo scope precedent requires a category to be SETTLED `no` before it is excluded. The claim is bounded by three censused Chowly product surfaces plus the publisher app census below, not by marketing silence. FOUR CORPORA ALREADY ON DISK, EACH A CENSUS OF ONE CHOWLY SURFACE, plus one new publisher census: (1) chowly.help Salesforce Knowledge, 583/583 articles (100% of the Knowledge listing, 1.34 M chars stripped, HTML comments removed first); (2) the Restaurant Control Center chowly.app, closed /asset-manifest.json source-map set, 958 extracted sources; (3) cms.koala.io Koala Brand CMS, 910 mapped sources (580 Koala-own); (4) the rebuilt chowly.com, 167/167 sitemap pages; (5) NEW: the App Store publisher census for Chowly Inc (iTunes lookup id=1726094961&entity=software, 51 apps): every one is a white-label DINER ordering/loyalty app for a named restaurant (Muldoon Pizza, Two Eggs, Liv's Juice Bar ...); zero employee-, manager-, time-clock- or scheduling-facing apps. TOKENISED word-boundary controls, case-insensitive, KB / RCC / Koala / site (docs hit): known-positive menu 273/110/35/125 and order(s) 294/105/39/167 (regexes work); time[-]clock 0/0/0/2; clock(ed)-in/out 0/0/0/1; timesheet|timecard 0/0/0/0; payroll 0/0/0/9; W-2|I-9 0/0/0/0; wage|hourly rate 0/0/0/2; tip pool|tip-out|tip share 0/0/0/2; fair workweek|predictive scheduling 0/0/0/1; meal|rest break 0/0/0/1; labor|labour 1/0/0/24; punch 1/0/0/10; shift(s) 3/9/8/45; overtime|over time 0/7/3/22; schedul* 29/63/3/24; employee(s) 17/1/0/8; 7shifts|Homebase|HotSchedules|Sling|Deputy|Harri|Gusto|ADP|Paychex 0/0/0/3. EVERY NON-ZERO HIT WAS READ AND CLASSIFIED, AND NONE IS A CHOWLY LABOUR SURFACE. POISON NAMED: KB `labor` = 'Labor Day' (holiday hours); KB `punch` = 'Olo, Punch or SSMA' (a data-deletion partner); site `punch` = loyalty PUNCH CARDS; KB `shift` = a UI element that 'would shift from left to right' and chargeback 'Chip Liability Shift'; RCC/Koala `shift` = floating-ui shift(), Array.prototype.shift(), shiftKey and 'shift+left' hotkeys (and `shifted`/`shifting` excluded by the token boundary); RCC/Koala `overtime` = 'over time' in chart captions and slate-editor comments; `break` = CSS/text LINE BREAKS, 'breaks of availability' in hours, and the JS `break` statement; KB `schedul*` 29 docs = scheduled (future) ORDERS, store/online-ordering hour schedules, Olo product-availability schedules, 'Schedule a Meeting with Our Team', the Stripe payout schedule and the Koala release schedule - zero employee schedules; KB `employee` 17 docs = Chowly's own support staff ('Chowly employees have no way of getting into your POS'), a POS employee ACCOUNT used to install the Chowly App on Clover, and the POS employee Chowly stamps onto an injected ticket ('orders integrating with the incorrect dining option, tender, revenue center, or employee'); RCC `employee` 1 = the RCC LOGIN ROLE `RESTAURANT_EMPLOYEE`, whose src/config.ts permittedFeaturesByRole grant is exactly five features (Manage Locations view/search/select, Resync Menus, Select Platform) - an app-user role, not an employee record; site hits are all SEO blog prose about OTHER vendors (7shifts 'time clock with break compliance, tip pooling and payouts, and payroll', resources/blogs/best-restaurant-management-software). THE APP'S OWN ENUMERATIONS CLOSE IT FOR THE RCC: src/config.ts `enum AppFeatureName` lists 23 features (Health Dashboard, 5 Analytics reports, 16 Manage Location/Platform actions, View COO Brand & Config Info) and the router's path table is Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing - no labour route. VENDOR-VOICE POSITIONING (grade C, blog 2026-06-09, https://chowly.com/resources/blogs/best-restaurant-management-software/): all-in-one platforms like Chowly 'consolidate the guest-facing side of the business - website, ordering, marketing, loyalty - into one system', while 'Most restaurants run a POS ..., an online ordering system, a scheduling tool like 7shifts, and inventory or invoice software'; and https://chowly.com/resources/blogs/restaurant-tech-stack-pays-for-itself-90-days/ tabulates the stack as 'POS | Toast/Square | Existing operational backbone' and 'Everything else | Chowly Platform | Online ordering, delivery integration, marketing, loyalty, website, analytics, AI pricing'. The site's own product menu (index) enumerates Marketing Website, Online Ordering, Google Business Profile, Google Ads, 3rd Party Integration, Email Marketing, Mobile App, Dynamic Pricing, Customer Surveys, Loyalty Program and eight AI Agents - no labour product. The only staffing-aware line is the Delivery Agent's 'Dynamic hours adjustment based on real-time staffing' (agents/delivery), which CONSUMES staffing to set marketplace hours. CONCLUSION: the labour claims do not apply to Chowly - there is no employee record, time punch, schedule, wage or tip-distribution object in any Chowly product surface we hold. CELL: W-2 = 0 in all four corpora; Chowly is never an employer-of-record or wage filer. Retrieved 2026-09-18. https://chowly.com/chowly-platform/ · retrieved 2026-09-18 adversarially verified

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

labor-native-payroll

331st LABOUR CENSUS -> no/B. MERGE CALL: landed `no`, not held at unknown, because this record already carries five labour `no`s on the same basis (clock-in-at-pos, granular-rbac, payroll-export-formats at B; manager-override-audit, server-performance-metrics at C), and the chowly/olo scope precedent requires a category to be SETTLED `no` before it is excluded. The claim is bounded by three censused Chowly product surfaces plus the publisher app census below, not by marketing silence. FOUR CORPORA ALREADY ON DISK, EACH A CENSUS OF ONE CHOWLY SURFACE, plus one new publisher census: (1) chowly.help Salesforce Knowledge, 583/583 articles (100% of the Knowledge listing, 1.34 M chars stripped, HTML comments removed first); (2) the Restaurant Control Center chowly.app, closed /asset-manifest.json source-map set, 958 extracted sources; (3) cms.koala.io Koala Brand CMS, 910 mapped sources (580 Koala-own); (4) the rebuilt chowly.com, 167/167 sitemap pages; (5) NEW: the App Store publisher census for Chowly Inc (iTunes lookup id=1726094961&entity=software, 51 apps): every one is a white-label DINER ordering/loyalty app for a named restaurant (Muldoon Pizza, Two Eggs, Liv's Juice Bar ...); zero employee-, manager-, time-clock- or scheduling-facing apps. TOKENISED word-boundary controls, case-insensitive, KB / RCC / Koala / site (docs hit): known-positive menu 273/110/35/125 and order(s) 294/105/39/167 (regexes work); time[-]clock 0/0/0/2; clock(ed)-in/out 0/0/0/1; timesheet|timecard 0/0/0/0; payroll 0/0/0/9; W-2|I-9 0/0/0/0; wage|hourly rate 0/0/0/2; tip pool|tip-out|tip share 0/0/0/2; fair workweek|predictive scheduling 0/0/0/1; meal|rest break 0/0/0/1; labor|labour 1/0/0/24; punch 1/0/0/10; shift(s) 3/9/8/45; overtime|over time 0/7/3/22; schedul* 29/63/3/24; employee(s) 17/1/0/8; 7shifts|Homebase|HotSchedules|Sling|Deputy|Harri|Gusto|ADP|Paychex 0/0/0/3. EVERY NON-ZERO HIT WAS READ AND CLASSIFIED, AND NONE IS A CHOWLY LABOUR SURFACE. POISON NAMED: KB `labor` = 'Labor Day' (holiday hours); KB `punch` = 'Olo, Punch or SSMA' (a data-deletion partner); site `punch` = loyalty PUNCH CARDS; KB `shift` = a UI element that 'would shift from left to right' and chargeback 'Chip Liability Shift'; RCC/Koala `shift` = floating-ui shift(), Array.prototype.shift(), shiftKey and 'shift+left' hotkeys (and `shifted`/`shifting` excluded by the token boundary); RCC/Koala `overtime` = 'over time' in chart captions and slate-editor comments; `break` = CSS/text LINE BREAKS, 'breaks of availability' in hours, and the JS `break` statement; KB `schedul*` 29 docs = scheduled (future) ORDERS, store/online-ordering hour schedules, Olo product-availability schedules, 'Schedule a Meeting with Our Team', the Stripe payout schedule and the Koala release schedule - zero employee schedules; KB `employee` 17 docs = Chowly's own support staff ('Chowly employees have no way of getting into your POS'), a POS employee ACCOUNT used to install the Chowly App on Clover, and the POS employee Chowly stamps onto an injected ticket ('orders integrating with the incorrect dining option, tender, revenue center, or employee'); RCC `employee` 1 = the RCC LOGIN ROLE `RESTAURANT_EMPLOYEE`, whose src/config.ts permittedFeaturesByRole grant is exactly five features (Manage Locations view/search/select, Resync Menus, Select Platform) - an app-user role, not an employee record; site hits are all SEO blog prose about OTHER vendors (7shifts 'time clock with break compliance, tip pooling and payouts, and payroll', resources/blogs/best-restaurant-management-software). THE APP'S OWN ENUMERATIONS CLOSE IT FOR THE RCC: src/config.ts `enum AppFeatureName` lists 23 features (Health Dashboard, 5 Analytics reports, 16 Manage Location/Platform actions, View COO Brand & Config Info) and the router's path table is Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing - no labour route. VENDOR-VOICE POSITIONING (grade C, blog 2026-06-09, https://chowly.com/resources/blogs/best-restaurant-management-software/): all-in-one platforms like Chowly 'consolidate the guest-facing side of the business - website, ordering, marketing, loyalty - into one system', while 'Most restaurants run a POS ..., an online ordering system, a scheduling tool like 7shifts, and inventory or invoice software'; and https://chowly.com/resources/blogs/restaurant-tech-stack-pays-for-itself-90-days/ tabulates the stack as 'POS | Toast/Square | Existing operational backbone' and 'Everything else | Chowly Platform | Online ordering, delivery integration, marketing, loyalty, website, analytics, AI pricing'. The site's own product menu (index) enumerates Marketing Website, Online Ordering, Google Business Profile, Google Ads, 3rd Party Integration, Email Marketing, Mobile App, Dynamic Pricing, Customer Surveys, Loyalty Program and eight AI Agents - no labour product. The only staffing-aware line is the Delivery Agent's 'Dynamic hours adjustment based on real-time staffing' (agents/delivery), which CONSUMES staffing to set marketplace hours. CONCLUSION: the labour claims do not apply to Chowly - there is no employee record, time punch, schedule, wage or tip-distribution object in any Chowly product surface we hold. CELL: payroll = 0 in KB/RCC/Koala; the 9 site hits are blog prose about other vendors. Retrieved 2026-09-18. https://chowly.com/chowly-platform/ · retrieved 2026-09-18 adversarially verified

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

labor-payroll-export-formats

No payroll integrations listed on the partnerships page and no labor data to export. https://chowly.com/partnerships/ · retrieved 2026-08-01

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

labor-shift-swap-workflow

331st LABOUR CENSUS -> no/B. MERGE CALL: landed `no`, not held at unknown, because this record already carries five labour `no`s on the same basis (clock-in-at-pos, granular-rbac, payroll-export-formats at B; manager-override-audit, server-performance-metrics at C), and the chowly/olo scope precedent requires a category to be SETTLED `no` before it is excluded. The claim is bounded by three censused Chowly product surfaces plus the publisher app census below, not by marketing silence. FOUR CORPORA ALREADY ON DISK, EACH A CENSUS OF ONE CHOWLY SURFACE, plus one new publisher census: (1) chowly.help Salesforce Knowledge, 583/583 articles (100% of the Knowledge listing, 1.34 M chars stripped, HTML comments removed first); (2) the Restaurant Control Center chowly.app, closed /asset-manifest.json source-map set, 958 extracted sources; (3) cms.koala.io Koala Brand CMS, 910 mapped sources (580 Koala-own); (4) the rebuilt chowly.com, 167/167 sitemap pages; (5) NEW: the App Store publisher census for Chowly Inc (iTunes lookup id=1726094961&entity=software, 51 apps): every one is a white-label DINER ordering/loyalty app for a named restaurant (Muldoon Pizza, Two Eggs, Liv's Juice Bar ...); zero employee-, manager-, time-clock- or scheduling-facing apps. TOKENISED word-boundary controls, case-insensitive, KB / RCC / Koala / site (docs hit): known-positive menu 273/110/35/125 and order(s) 294/105/39/167 (regexes work); time[-]clock 0/0/0/2; clock(ed)-in/out 0/0/0/1; timesheet|timecard 0/0/0/0; payroll 0/0/0/9; W-2|I-9 0/0/0/0; wage|hourly rate 0/0/0/2; tip pool|tip-out|tip share 0/0/0/2; fair workweek|predictive scheduling 0/0/0/1; meal|rest break 0/0/0/1; labor|labour 1/0/0/24; punch 1/0/0/10; shift(s) 3/9/8/45; overtime|over time 0/7/3/22; schedul* 29/63/3/24; employee(s) 17/1/0/8; 7shifts|Homebase|HotSchedules|Sling|Deputy|Harri|Gusto|ADP|Paychex 0/0/0/3. EVERY NON-ZERO HIT WAS READ AND CLASSIFIED, AND NONE IS A CHOWLY LABOUR SURFACE. POISON NAMED: KB `labor` = 'Labor Day' (holiday hours); KB `punch` = 'Olo, Punch or SSMA' (a data-deletion partner); site `punch` = loyalty PUNCH CARDS; KB `shift` = a UI element that 'would shift from left to right' and chargeback 'Chip Liability Shift'; RCC/Koala `shift` = floating-ui shift(), Array.prototype.shift(), shiftKey and 'shift+left' hotkeys (and `shifted`/`shifting` excluded by the token boundary); RCC/Koala `overtime` = 'over time' in chart captions and slate-editor comments; `break` = CSS/text LINE BREAKS, 'breaks of availability' in hours, and the JS `break` statement; KB `schedul*` 29 docs = scheduled (future) ORDERS, store/online-ordering hour schedules, Olo product-availability schedules, 'Schedule a Meeting with Our Team', the Stripe payout schedule and the Koala release schedule - zero employee schedules; KB `employee` 17 docs = Chowly's own support staff ('Chowly employees have no way of getting into your POS'), a POS employee ACCOUNT used to install the Chowly App on Clover, and the POS employee Chowly stamps onto an injected ticket ('orders integrating with the incorrect dining option, tender, revenue center, or employee'); RCC `employee` 1 = the RCC LOGIN ROLE `RESTAURANT_EMPLOYEE`, whose src/config.ts permittedFeaturesByRole grant is exactly five features (Manage Locations view/search/select, Resync Menus, Select Platform) - an app-user role, not an employee record; site hits are all SEO blog prose about OTHER vendors (7shifts 'time clock with break compliance, tip pooling and payouts, and payroll', resources/blogs/best-restaurant-management-software). THE APP'S OWN ENUMERATIONS CLOSE IT FOR THE RCC: src/config.ts `enum AppFeatureName` lists 23 features (Health Dashboard, 5 Analytics reports, 16 Manage Location/Platform actions, View COO Brand & Config Info) and the router's path table is Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing - no labour route. VENDOR-VOICE POSITIONING (grade C, blog 2026-06-09, https://chowly.com/resources/blogs/best-restaurant-management-software/): all-in-one platforms like Chowly 'consolidate the guest-facing side of the business - website, ordering, marketing, loyalty - into one system', while 'Most restaurants run a POS ..., an online ordering system, a scheduling tool like 7shifts, and inventory or invoice software'; and https://chowly.com/resources/blogs/restaurant-tech-stack-pays-for-itself-90-days/ tabulates the stack as 'POS | Toast/Square | Existing operational backbone' and 'Everything else | Chowly Platform | Online ordering, delivery integration, marketing, loyalty, website, analytics, AI pricing'. The site's own product menu (index) enumerates Marketing Website, Online Ordering, Google Business Profile, Google Ads, 3rd Party Integration, Email Marketing, Mobile App, Dynamic Pricing, Customer Surveys, Loyalty Program and eight AI Agents - no labour product. The only staffing-aware line is the Delivery Agent's 'Dynamic hours adjustment based on real-time staffing' (agents/delivery), which CONSUMES staffing to set marketplace hours. CONCLUSION: the labour claims do not apply to Chowly - there is no employee record, time punch, schedule, wage or tip-distribution object in any Chowly product surface we hold. CELL: no shift object exists; every shift hit is poison (above). Retrieved 2026-09-18. https://chowly.com/chowly-platform/ · retrieved 2026-09-18 adversarially verified

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

labor-digital-onboarding-i9

331st LABOUR CENSUS -> no/B. MERGE CALL: landed `no`, not held at unknown, because this record already carries five labour `no`s on the same basis (clock-in-at-pos, granular-rbac, payroll-export-formats at B; manager-override-audit, server-performance-metrics at C), and the chowly/olo scope precedent requires a category to be SETTLED `no` before it is excluded. The claim is bounded by three censused Chowly product surfaces plus the publisher app census below, not by marketing silence. FOUR CORPORA ALREADY ON DISK, EACH A CENSUS OF ONE CHOWLY SURFACE, plus one new publisher census: (1) chowly.help Salesforce Knowledge, 583/583 articles (100% of the Knowledge listing, 1.34 M chars stripped, HTML comments removed first); (2) the Restaurant Control Center chowly.app, closed /asset-manifest.json source-map set, 958 extracted sources; (3) cms.koala.io Koala Brand CMS, 910 mapped sources (580 Koala-own); (4) the rebuilt chowly.com, 167/167 sitemap pages; (5) NEW: the App Store publisher census for Chowly Inc (iTunes lookup id=1726094961&entity=software, 51 apps): every one is a white-label DINER ordering/loyalty app for a named restaurant (Muldoon Pizza, Two Eggs, Liv's Juice Bar ...); zero employee-, manager-, time-clock- or scheduling-facing apps. TOKENISED word-boundary controls, case-insensitive, KB / RCC / Koala / site (docs hit): known-positive menu 273/110/35/125 and order(s) 294/105/39/167 (regexes work); time[-]clock 0/0/0/2; clock(ed)-in/out 0/0/0/1; timesheet|timecard 0/0/0/0; payroll 0/0/0/9; W-2|I-9 0/0/0/0; wage|hourly rate 0/0/0/2; tip pool|tip-out|tip share 0/0/0/2; fair workweek|predictive scheduling 0/0/0/1; meal|rest break 0/0/0/1; labor|labour 1/0/0/24; punch 1/0/0/10; shift(s) 3/9/8/45; overtime|over time 0/7/3/22; schedul* 29/63/3/24; employee(s) 17/1/0/8; 7shifts|Homebase|HotSchedules|Sling|Deputy|Harri|Gusto|ADP|Paychex 0/0/0/3. EVERY NON-ZERO HIT WAS READ AND CLASSIFIED, AND NONE IS A CHOWLY LABOUR SURFACE. POISON NAMED: KB `labor` = 'Labor Day' (holiday hours); KB `punch` = 'Olo, Punch or SSMA' (a data-deletion partner); site `punch` = loyalty PUNCH CARDS; KB `shift` = a UI element that 'would shift from left to right' and chargeback 'Chip Liability Shift'; RCC/Koala `shift` = floating-ui shift(), Array.prototype.shift(), shiftKey and 'shift+left' hotkeys (and `shifted`/`shifting` excluded by the token boundary); RCC/Koala `overtime` = 'over time' in chart captions and slate-editor comments; `break` = CSS/text LINE BREAKS, 'breaks of availability' in hours, and the JS `break` statement; KB `schedul*` 29 docs = scheduled (future) ORDERS, store/online-ordering hour schedules, Olo product-availability schedules, 'Schedule a Meeting with Our Team', the Stripe payout schedule and the Koala release schedule - zero employee schedules; KB `employee` 17 docs = Chowly's own support staff ('Chowly employees have no way of getting into your POS'), a POS employee ACCOUNT used to install the Chowly App on Clover, and the POS employee Chowly stamps onto an injected ticket ('orders integrating with the incorrect dining option, tender, revenue center, or employee'); RCC `employee` 1 = the RCC LOGIN ROLE `RESTAURANT_EMPLOYEE`, whose src/config.ts permittedFeaturesByRole grant is exactly five features (Manage Locations view/search/select, Resync Menus, Select Platform) - an app-user role, not an employee record; site hits are all SEO blog prose about OTHER vendors (7shifts 'time clock with break compliance, tip pooling and payouts, and payroll', resources/blogs/best-restaurant-management-software). THE APP'S OWN ENUMERATIONS CLOSE IT FOR THE RCC: src/config.ts `enum AppFeatureName` lists 23 features (Health Dashboard, 5 Analytics reports, 16 Manage Location/Platform actions, View COO Brand & Config Info) and the router's path table is Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing - no labour route. VENDOR-VOICE POSITIONING (grade C, blog 2026-06-09, https://chowly.com/resources/blogs/best-restaurant-management-software/): all-in-one platforms like Chowly 'consolidate the guest-facing side of the business - website, ordering, marketing, loyalty - into one system', while 'Most restaurants run a POS ..., an online ordering system, a scheduling tool like 7shifts, and inventory or invoice software'; and https://chowly.com/resources/blogs/restaurant-tech-stack-pays-for-itself-90-days/ tabulates the stack as 'POS | Toast/Square | Existing operational backbone' and 'Everything else | Chowly Platform | Online ordering, delivery integration, marketing, loyalty, website, analytics, AI pricing'. The site's own product menu (index) enumerates Marketing Website, Online Ordering, Google Business Profile, Google Ads, 3rd Party Integration, Email Marketing, Mobile App, Dynamic Pricing, Customer Surveys, Loyalty Program and eight AI Agents - no labour product. The only staffing-aware line is the Delivery Agent's 'Dynamic hours adjustment based on real-time staffing' (agents/delivery), which CONSUMES staffing to set marketplace hours. CONCLUSION: the labour claims do not apply to Chowly - there is no employee record, time punch, schedule, wage or tip-distribution object in any Chowly product surface we hold. CELL: I-9 = 0 in all four corpora; every onboarding hit is restaurant/location onboarding (site onboarding_employee hits are careers-page and blog prose). Retrieved 2026-09-18. https://chowly.com/chowly-platform/ · retrieved 2026-09-18 adversarially verified

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

labor-server-performance-metrics

Reporting is channel- and location-level, not employee-level. https://chowly.com/solutions/restaurant-control-center/ · retrieved 2026-08-01

Provides a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise.

reporting-realtime-dashboard

Restaurant Control Center gives real-time total sales at a glance with drill-down by location and delivery platform, in the browser. No operator-facing mobile reporting app is documented. https://chowly.com/solutions/restaurant-control-center/ · retrieved 2026-08-01

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

reporting-eod-closeout

Chowly holds no tender, cash, tax or drawer data - those live in the POS. https://chowly.com/pos/ · retrieved 2026-08-01

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

reporting-pmix-modifier-level

Top-selling items and average basket size by location are reported. Modifier-level PMIX with gross and net sales sliced by daypart and revenue center is not documented. https://chowly.com/solutions/restaurant-control-center/ · retrieved 2026-08-01

Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.

reporting-comps-voids-audit

The Restaurant Control Center’s reporting surface is described by one sentence — "There are seven different reporting pages: Locations, Sales, Orders, Product Mix, Week over Week, Delivery Buydown, and Smart Pricing" — repeated verbatim as a navigation preamble in seven articles all last modified inside a single five-day window in February 2024. That is one editorial act copy-pasted, not seven agreeing witnesses, and a knowledge-base mirror can never prove there is no eighth page. It is also two and a half years old while the rest of that book was revised into 2026, and Chowly’s 2026 marketing describes the Control Center consolidating "orders, discounts, and revenue" — a dimension the 2024 articles do not carry. A current description of the reporting surface would settle it. || 325th: MERGE HOLD (proposed no/B, held unknown): Chowly takes no comps or voids; not applicable is held unknown, not scored no. PROPOSAL AS WRITTEN: 325th: MOVED unknown -> no (B). THE 'SEVEN REPORTING PAGES' FLOOR IS RETIRED: the stale February-2024 help-centre sentence is superseded by the shipped index. features/reporting/Reporting.tsx ships `const reportingPageCardLinks = [...]` naming TEN pages - Locations /locations, Sales /sales, Orders /orders, Product Mix /product-mix, Week over Week /wow, Delivery Buy Down /delivery-buy-down, Dynamic Pricing /smart-pricing, Disputes /disputes (Experiments.RRR_REPORT), Reconciliation /reconciliation (RRR_REPORT), Platform Stats /platform-stats (adminOnly) - and src/config.ts `sigmaPages` enumerates the sixteen Sigma Computing embeds behind them (healthDashboard, locationsReport, ordersReport, productMix, salesReport, smartPricingReport, wowReport, deliveryBuyDown, salesOrderByPlatform, advancedOrders, disputes, reconciliation, ordersComeFromReport, repeatCustomersReport, topCustomersListReport, platformStats). CLAIM: an audit report of comps, voids, discounts and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps. VERDICT: no. EVIDENCE: the platform holds no employee dimension to attribute anything to. api/orderManagement/types.ts ships the reporting row as a closed attribute list - order_platform_order_id, outcome_classification, customer_email/first/last/phone, loyalty_member, customer_platform_customer_id, delivery_city/fee/state/status/street/street2/zip, internal_order_id, order_status, order_type, platform_name, pos_order_id, submission_time, subtotal, tax, tip, payment_provider, partner_id, ready_at, aasm_state, timing_preference, expected_ready_at, conveyance_time, catering, total, partner_name, gift_card_used - with no employee, server, approver, void, comp or override field, and the sortable-column union (OrderSortField, 13 members, declared 'MUST stay a subset of the BE whitelist Orders::Reporting::Sort::SORTABLE_COLUMNS') adds none. The only reason codes in the product are cancellation/refund reasons on an order (features/order-managment/giftCardRefund/refundableReasonCopy.ts, RefundModal) and campaign block reasons, neither attributed to an approving manager. BOUND/CONTROLS: complete RCC map set (830 .ts/.tsx, 3/3 chunks) + the 583-article chowly.help census. App controls: `employee|employees|staff` 1 hit (a role name), `comp|comps|comped` 4 hits all in the SEO RankingsTable, `reason` 150 hits across campaign-block and refund copy only. POISON: `void|voids|voided` 553 hits in 231 files are ALL the TypeScript `void` type. Census control: `void|voids|comp|comps` 1/583 docs, the single hit being Chowly-Online-Ordering-Refund-Request. Retrieved 2026-09-17. || 333rd: 333rd NEW (notes only; the 325th hold 'Chowly takes no comps or voids' is NOT re-proposed): the RCC order record is a closed TypeScript type (src/api/orderManagement/types.ts ReportingOrder: customer_*, delivery_*, order_status, platform_name, pos_order_id, subtotal, tax, tip, payment_provider, total, gift_card_used ...) with NO employee/actor/approver field and no discount or reason-code field; RCC refunds carry refund_reason = the refund TYPE ('e.g. void post-refund') and refundable_reason = ineligibility codes (already_refunded, manager_tid_missing, window_expired ...), never who refunded. The RCC's only two audit logs are adjacent: marketing-campaign blocks ('Provide a reason - this will be recorded in the audit log') and Support-Assistant actions ('All actions are logged and auditable below'). The guest client (875 sources) has no void/comp surface ('void' hits are the TS keyword - POISON). Retrieved 2026-09-18. || 334th: 334th NEW (notes only): the partner API's order record (order_details: id, payload, external_id, created_at, completed_at, error_at, error_string, ticket_payload) has no employee, approver, reason-code or void field, and orders cannot be voided through the API. KB screenshots of RCC Order Management read at full resolution (chowly.help Order-Management-on-the-Restaurant-Control-Center refid 0EMPq00000OSse2, Using-Nash-with-Chowly refid 0EMPq00000JRKpJ, Refunding-and-Canceling-Chowly-Online-Ordering-Orders refid 0EMPq00000AJxcw) show columns Ticket ID, Status, Timing, AASM State, Platform, Location, Submission/Scheduled Time, Customer, Delivery Address, Order Type and an order drawer with only Cancel Order / Refund Order - no actor or reason column. Adds to the 325th hold; notes only. Source: https://api-docs.chowlyinc.com/toos/v2/ (Chowly's own OpenAPI 3.0.2 TOOS v2 spec, served anonymously; new this session) and/or chowly.help KB images. Retrieved 2026-09-18. adversarially verified

Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.

reporting-cash-over-short

Cash over/short is a drawer count at a register, and Chowly operates no register: it states in its own voice that it is not a POS but the ordering layer on top of one, and every order it handles is prepaid — the Diner Terms route all payments in its first-party channels to a card processor against a designated payment method, and marketplace orders are settled by the marketplace. With no cash tender anywhere in a Chowly-controlled flow there is no drawer to count and no variance to report. Bounded to Chowly: cash taken at the operator’s own register is reconciled in that POS. https://chowly.com/diner-terms-and-conditions/ · retrieved 2026-09-06 adversarially verified

Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.

reporting-labor-productivity

332nd: MOVED unknown -> no (B). CLAIM: sales per labor hour and labor cost % of sales by hour, department and employee, from actual clocked hours in the POS time clock. VERDICT: no - Chowly has no time clock (labor-clock-in-at-pos is no/B on this record) and no labour-hours input, so no SPLH or labour-% report can exist. PRECEDENT ON THIS RECORD: the 331st labour census (same four corpora + the App Store publisher census, Chowly Inc developer id 1726094961, 51 apps, all white-label diner ordering apps) LANDED 16 labour cells no/B in 331st batch 1 (fba9c0f) - incl. labor-clock-in-at-pos, labor-native-scheduling, labor-overtime-prevention, labor-break-compliance-by-state, labor-fair-workweek-support, labor-native-payroll, labor-payroll-export-formats - on the finding that no Chowly product surface holds an employee record, time punch, schedule, wage or tip-distribution object. This cell consumes exactly that absent data, so it follows the landed category rather than the older no-module hold; the 331st proposed it unknown only because the category was then undecided. BOUND - four censuses on disk, each 100% of its publisher's own manifest, re-verified CURRENT by the 332nd today: (a) chowly.help Salesforce Knowledge, 583/583 articles (.cache/q324/chowly/ch/arts); the listing https://chowly.help/services/data/v59.0/support/knowledgeArticles?pageSize=100 was re-paged 2026-09-18 (6 pages) and still returns 583 ids, ZERO not already held, newest lastPublishedDate 2026-06-16, so the census has not gone stale; (b) the Restaurant Control Center chowly.app, 958 sources from the complete /asset-manifest.json source-map set (.cache/q325/chowly/src; today's manifest still names main.54b02cd0.js, the censused build); (c) cms.koala.io Koala Brand CMS, 910 mapped sources (.cache/q326/chowly/cmssrc; today's manifest still names main.12caeb2d.chunk.js, the censused build); (d) all 167 chowly.com sitemap pages (.cache/q327/chowly/sitetxt). KNOWN-POSITIVE CONTROLS (tokenised, word-boundary, case-insensitive; KB/RCC/Koala/site docs hit): /\btoast\b/ 48/114/0/113, /\bmenus?\b/ 273/110/35/125 - the regexes fire. Script: .cache/q332/chowly/a/ctl.mjs, output ctl-out.json. CELL CONTROLS: /sales per labou?r hours?|SPLH|labou?r (cost|hours?|percent(age)?|%)/ = 0/583, 0/958, 0/910, 5/167; ALL 5 SITE HITS ARE POISON - blog prose: 'Real-Time Labor Cost Visibility' in a research round-up of other tools (resources/blogs/how-the-right-restaurant-software-saves-100-hours-a-year...), ROI arithmetic 'At $25/hour labor cost, that's $14,300-24,700/year in saved time' (restaurant-automation-save-20-hours-weekly), 'before you count the labor hours spent keeping all of it running' (restaurant-tech-stack-pays-for-itself-90-days) and a testimonial 'saving countless labor hours' (restaurant-types/multi-concept-groups). /\blabou?rs?\b/ = 1/583 ('Labor Day' holiday hours - POISON), 0/958, 0/910. The RCC's shipped reporting index (features/reporting/Reporting.tsx reportingPageCardLinks: Locations, Sales, Orders, Product Mix, Week over Week, Delivery Buy Down, Dynamic Pricing, Disputes, Reconciliation, Platform Stats) and src/config.ts sigmaPages (16 Sigma embeds) contain no labour report, and the ReportingOrder row (closed 33-field list) has no hours or wage field. Retrieved 2026-09-18. https://chowly.app/static/js/main.54b02cd0.js.map · retrieved 2026-09-18 adversarially verified

Reports per-server metrics including average check, items per check, attachment rate for named categories, and tips as a percentage of sales. differentiator

reporting-server-scorecards

332nd: MOVED unknown -> no (B). CLAIM: per-server metrics - average check, items per check, attachment rate for named categories, tips as % of sales. VERDICT: no - Chowly has no server/employee dimension in any product surface (labor-server-performance-metrics is already no/C on this record), so no per-server report can exist. PRECEDENT ON THIS RECORD: the 331st labour census (same four corpora + the App Store publisher census, Chowly Inc developer id 1726094961, 51 apps, all white-label diner ordering apps) LANDED 16 labour cells no/B in 331st batch 1 (fba9c0f) - incl. labor-clock-in-at-pos, labor-native-scheduling, labor-overtime-prevention, labor-break-compliance-by-state, labor-fair-workweek-support, labor-native-payroll, labor-payroll-export-formats - on the finding that no Chowly product surface holds an employee record, time punch, schedule, wage or tip-distribution object. This cell consumes exactly that absent data, so it follows the landed category rather than the older no-module hold; the 331st proposed it unknown only because the category was then undecided. BOUND - four censuses on disk, each 100% of its publisher's own manifest, re-verified CURRENT by the 332nd today: (a) chowly.help Salesforce Knowledge, 583/583 articles (.cache/q324/chowly/ch/arts); the listing https://chowly.help/services/data/v59.0/support/knowledgeArticles?pageSize=100 was re-paged 2026-09-18 (6 pages) and still returns 583 ids, ZERO not already held, newest lastPublishedDate 2026-06-16, so the census has not gone stale; (b) the Restaurant Control Center chowly.app, 958 sources from the complete /asset-manifest.json source-map set (.cache/q325/chowly/src; today's manifest still names main.54b02cd0.js, the censused build); (c) cms.koala.io Koala Brand CMS, 910 mapped sources (.cache/q326/chowly/cmssrc; today's manifest still names main.12caeb2d.chunk.js, the censused build); (d) all 167 chowly.com sitemap pages (.cache/q327/chowly/sitetxt). KNOWN-POSITIVE CONTROLS (tokenised, word-boundary, case-insensitive; KB/RCC/Koala/site docs hit): /\btoast\b/ 48/114/0/113, /\bmenus?\b/ 273/110/35/125 - the regexes fire. Script: .cache/q332/chowly/a/ctl.mjs, output ctl-out.json. CELL CONTROLS: /(average|avg) (check|ticket)|items per (check|ticket|order)|attach(ment)? rate|per[- ](server|employee)|(server|employee) (report|performance|sales|scorecard)s?/ = 0/583, 0/958, 0/910, 11/167; ALL 11 SITE HITS ARE POISON - 'average ticket' as a restaurant-level figure in blog prose ('At a $30 average ticket, a restaurant processing under roughly $19,000...' in resources/blogs/clover-vs-square-for-restaurants; 'Pizza Pirate ... saw their average ticket jump 40%' in essential-restaurant-website-features...), never per server. /employee_?id|server_?(id|name)|employeeId|serverName/ = 0 in all four. The RCC ReportingOrder row is a closed 33-field list with no employee/server field and OrderSortField's 13 columns add none; RCC /\bservers?\b/ hits are all 'server-side'/'doordash_server_error' (POISON). Tip exists only as an order field, never aggregated per person. Retrieved 2026-09-18. https://chowly.app/static/js/main.54b02cd0.js.map · retrieved 2026-09-18 adversarially verified

Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator

reporting-channel-profitability

Reports sales by individual delivery platform and by location, and 1P vs 3P economics is the core pitch. Margin net of marketplace commission, marketing fees and refunds is not documented as a report. https://chowly.com/solutions/restaurant-control-center/ · retrieved 2026-08-01

Provides a consolidated multi-location report with side-by-side location comparison and drill-down from group total to a single location and then to an individual transaction. differentiator

reporting-multiloc-drilldown

Consolidated multi-location hub with drill-down by location or delivery platform - Golden Krust consolidated 125+ locations. Side-by-side store ranking and drill-through to an individual transaction are not documented. https://chowly.com/solutions/restaurant-control-center/ · retrieved 2026-08-01

Includes a self-service report builder letting a non-developer choose dimensions, measures, and filters and save the result, rather than only fixed canned reports. differentiator

reporting-custom-report-builder

Sales-Reporting-Page-on-the-Restaurant-Control-Center and Product-Mix-Reporting-on-the-Restaurant-Control-Center both open with the same enumeration of the entire analytics surface: 'There are seven different reporting pages: Locations, Sales, Orders, Product Mix, Week over Week, Delivery Buydown, and Smart Pricing. Each one provides you with a more specific and deeper dive into your restaurants' data points. All of the Reports Pages initially shows data for every single location over the last 7 days. Location sets and time ranges can be adjusted.' Each page is then described tile by tile as fixed content - Total Sales, Sales by Platform, Sales by Location; Number of Items Ordered, Average Item Price, Number of Modifiers Ordered, Top 10 Items, Top 10 Modifiers, Items Detail, Modifiers Detail. The only user controls documented are prebuilt dropdowns (Menu Item, Platform Name, Service Type) plus location set and date range - filters over a fixed report, not a choice of dimensions and measures, and there is no save, no custom report object and no builder anywhere in the 196-article corpus. The enumeration is current: it already contains the recent Smart Pricing and Delivery Buydown pages. https://chowly.help/s/article/Sales-Reporting-Page-on-the-Restaurant-Control-Center · retrieved 2026-08-08

Supports scheduling any report for automatic recurring delivery by email or to a shared destination on a defined cadence and recipient list.

reporting-scheduled-delivery

CLAIM: any report can be scheduled for automatic recurring delivery by email or to a shared destination, with a cadence and a recipient list. VERDICT: no. BOUND: the whole chowly.help knowledge base, fetched to 100% of the publisher's own manifest - https://chowly.help/services/data/v59.0/support/knowledgeArticles?pageSize=100, 6 pages, 583 articles, every body retrieved via the article's own url (denominator 583; 44 of 44 chowly.help article URLs already cited in this record are inside it, so it is a census and not a floor). ENUMERATION 1, the reporting surface: 'Sales Reporting Page on the Restaurant Control Center' (https://chowly.help/s/article/Sales-Reporting-Page-on-the-Restaurant-Control-Center) opens 'There are seven different reporting pages: Locations, Sales, Orders, Product Mix, Week over Week, Delivery Buydown, and Smart Pricing.' ENUMERATION 2, what an operator can DO with a report tile: 'Navigating the Restaurant Control Center' (https://chowly.help/s/article/Navigating-the-Restaurant-Control-Center, modified 2026-02-11) enumerates the complete tile action set - 'The Three Dots icon shows a drop-down list of other actions you can do with your data: Sort, Download, Refresh data, Copy to clipboard, and Format', alongside a Filters icon (date range + locations) and an Expand icon. There is no schedule, subscribe, email or deliver action. CONTROLS, tokenised and case-insensitive over all 583 stripped bodies: /\bschedul\w*\s+report/ 0/583; /\breport\w*\s+schedul/ 0/583; /\bemail\w*\s+(me|you|the)?\s*report/ 0/583; /\bsubscri\w*/ 5/583 and POISON - every one is a commercial subscription ('add a new location to your current Chowly subscription', Stripe account setup, an Olo webhook subscription), none a report subscription. Corroborating vendor statement: the Chowly Platform FAQ (https://chowly.help/s/article/COO-and-Chowly-Platform-FAQ, modified 2026-04-23) answers 'Can I email my customers through Chowly?' for COO with 'Not currently, However, customer data reports are accessible via the Restaurant Control Center... which allows restaurants to export insights' - manual export is the documented route. Grade B. Retrieved 2026-09-17. https://chowly.help/s/article/Sales-Reporting-Page-on-the-Restaurant-Control-Center · retrieved 2026-09-17 adversarially verified

Offers automated recurring bulk export of transaction-level raw data to a customer-controlled destination (S3, SFTP, Snowflake, BigQuery, or equivalent), not just manual CSV download. differentiator

reporting-raw-warehouse-export

CLAIM: automated recurring bulk export of transaction-level raw data to a customer-controlled destination (S3, SFTP, Snowflake, BigQuery or equivalent), not just manual CSV download. VERDICT: no. BOUND: the same 100% chowly.help census as reporting-scheduled-delivery (583/583 articles from https://chowly.help/services/data/v59.0/support/knowledgeArticles?pageSize=100, all bodies held, 44/44 already-cited article URLs present). EVIDENCE: the RCC's documented data-egress mechanism is a manual per-tile action - 'Navigating the Restaurant Control Center' enumerates the tile menu as 'Sort, Download, Refresh data, Copy to clipboard, and Format', and the Chowly Platform FAQ frames export as an operator action ('customer data reports are accessible via the Restaurant Control Center... which allows restaurants to export insights and fuel their own marketing efforts', https://chowly.help/s/article/COO-and-Chowly-Platform-FAQ). CONTROLS over all 583 bodies, tokenised and case-insensitive: /\bdata\s+warehouse\b/ 0/583, /\bsnowflake\b/ 0/583, /\bBigQuery\b/ 0/583, /\bS3\b/ 0/583, /\bSFTP\b/ 0/583. /\bexport\b/ hits only 6/583 and POISON - the hits are menu/image export between POS and marketplaces and one 'export insights' line, not a warehouse feed. Grade B. Retrieved 2026-09-17. https://chowly.help/s/article/Navigating-the-Restaurant-Control-Center · retrieved 2026-09-17 adversarially verified

Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator

reporting-public-api

Quote: "Chowly has it's own API specifically so other POS systems can connect to our services. We call this API the "Chowly POS API."" Positive evidence of absence on the claim's two load-bearing prongs. Chowly's own help centre defines its API as partner-facing and restricted: 'Chowly has it's own API specifically so other POS systems can connect to our services. We call this API the "Chowly POS API."' (FAQ-Chowly-s-POS-API-Integration) and access is 'only available to POS systems who have built to them' - not self-service credentials obtainable by an operator or developer without a partnership. No public reference, schema or credential flow exists anywhere on chowly.help or the 167-URL chowly.com sitemap (no /developers, /docs, /api page). The claim also requires labor data, which Chowly, an integration layer rather than a POS, does not hold. The V2 TOOS Partner API known from the goparrot client is likewise a partner (online-ordering-provider) surface. Caveat for the audit: this is a 'no' on 'public + self-service', not a claim that no API exists; the prior pass left it unknown because a partner API's surface cannot be seen from outside. https://chowly.help/s/article/FAQ-Chowly-s-POS-API-Integration · retrieved 2026-09-03 adversarially verified

Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator

reporting-webhooks

333rd: PROPOSED unknown -> no (B) on the DOCUMENTATION conjunct only - the exact shape that LANDED no/B for extensibility-webhook-reliability on this record in the 331st (batch 1). CLAIM: emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, WITH DOCUMENTED retry behaviour AND payload signature verification - a conjunction, so one failed conjunct fails it. Whether Chowly emits outbound webhooks at all is left to extensibility-webhooks-push (held under the unpublished-partner-API rule); this row does not depend on it, because either way no retry or signature behaviour is documented anywhere Chowly publishes. NEW SURFACE (333rd, never censused): the CHOWLY ONLINE ORDERING guest client that every Chowly white-label tenant runs (<slug>.onlineorder.site; the App Store publisher census's 51 apps carry bundle ids site.onlineorder.<slug>). It is the Koala web-ordering Next.js app (theme CSS from koala-web-ordering-themes.s3.amazonaws.com), one multi-tenant build (buildId 94f531751c59ff7df44392c822336a31a4d8642d served on stuftpizzabarandgrill.onlineorder.site and muldoonpizza.onlineorder.site alike). CLOSED BUNDLE: _buildManifest.js names 21 pages (/, /account/*, /checkout, /store/[...id], /stores, /order-confirmation, /arrival-confirmation ...) and the initial chunk set; the webpack runtime defines NO chunk-URL / lazy-load function (no .u/.e/.l), so the initial set is the whole app; 45 of 45 app chunks serve a real .map with sourcesContent (only the polyfills chunk has none), 2,148 mapped sources, 875 first-party incl. the vendored @koala/sdk (packages/sdk/dist/index.mjs + v4). Soft-404 control: /_next/static/chunks/zzz-nonsense333.js.map -> 404. Scratch: .cache/q333/chowly/a/coo/js (maps), .cache/q333/chowly/a/ctl.mjs (five-corpus control runner). BOUND: FIVE product-surface censuses, re-grepped per cell with tokenised case-insensitive regexes (.cache/q333/chowly/a/ctl.mjs): (a) chowly.help 583/583 Salesforce Knowledge articles; (b) chowly.app Restaurant Control Center 958 sources (closed asset-manifest map set); (c) cms.koala.io Koala Brand CMS 910 sources; (d) chowly.com 167/167 sitemap pages; (e) NEW the COO/Koala guest ordering client, 875 first-party sources. Known-positive control /\btoast\b/ = 48/583, 114/958, 0/910, 113/167, 56/875 (the regexes fire). CONTROLS: /\bwebhooks?\b/ = 14/583, 0/958, 1/910, 0/167, 0/875 - every KB hit is a webhook Chowly/Koala CONSUMES (Olo location/menu/dispatch-tracking webhooks, Square inventory webhooks, 'The RCC will continue to accept 86ing updates from the POS via webhooks', SpotOn onboarding 'Enter Webhook URL' = the SpotOn-side URL pointing at Chowly); the CMS hit is a Vercel deploy hook (POISON). /retr(y|ies|ied) within 80 chars of webhook|event|deliver|notification/ = 0/583, 1/958 (onboarding-wizard save retry - POISON), 0/910, 0/167, 3/875 (basket-menu refetch 'with 3 automatic retries', arrival-notification error retry, a 'Retry Delivery' CTA - client UI, POISON). /\bHMAC\b|signing (secret|key)|signature (verification|header)|x-*-signature/ = 0 in all five. /endpoint url|callback url|webhook url|subscribe ... events/ = 2/583 (Olo webhooks Koala subscribes to; the SpotOn URL), 1/958 (Google consent-screen callback), 1/910 (urql client option) - POISON, none a customer endpoint. ROUTE MANIFESTS (owner ruling 6, 2026-09-18): the RCC router (App.js + utils/urls.ts) lists every operator page - analytics (locations, sales, orders, product-mix, platform-stats, reconciliation, disputes, smart-pricing, wow, delivery-buy-down, dm-reporting), billing, account-management, support, digital-marketing, promo-codes, loyalty, media-library, keywords, customer-surveys, marketing-website, mobile-app, order-management, connections, menu-management, dynamic-pricing - and no webhook or endpoint-registration page; the @koala/sdk bundled in the COO client names 58 API routes (/v1/ordering/store-locations/:id/baskets/*, /v1/ordering/me/*, /v1/ordering/loyalty/*, /v1/ordering/orders/*, /configurations/*, /v1/tags ...) and none is a webhook subscription. WEAKEST PART: webhooks.chowlyinc.com (certspotter, 331st) is a login-gated Rails/Devise app named for webhooks and was not read; it may host a partner-facing outbound service documented privately. That bears on the capability conjunct (held on extensibility-webhooks-push), not on whether retry/signature behaviour is DOCUMENTED, which is what this row scores and what the twin row already landed on. Retrieved 2026-09-18. || 334th CORRECTION: Chowly publishes an anonymous OpenAPI 3.0.2 spec for its partner API (https://api-docs.chowlyinc.com/toos/v2/, Redoc, v2.0.0) whose 4 outbound webhooks (order confirmation, order error, menu updated, location paused/unpaused) carry an HMAC-SHA256 X-Signature header, so the SIGNATURE conjunct IS documented and any wording above that says otherwise is superseded. The no stands on the other conjunct(s): the spec documents no retry/backoff behaviour and no replayable event log. Retrieved 2026-09-18. https://chowly.help/s/article/FAQ-Chowly-s-POS-API-Integration · retrieved 2026-09-18 adversarially verified

API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator

reporting-api-not-upcharged

Quote: "The Three Dots icon shows a drop-down list of other actions you can do with your data: Sort, Download, Refresh data, Copy to clipboard, and Format." Quote verified in chowly/SDK-Provider-Support-Contacts.txt. The claim conjoins 'API and raw-data access'. The API half is genuinely absent for subscribers by the vendor's own restriction ('only available to POS systems who have built to them'), but the claim's named failure modes are a per-location fee, revenue share or enterprise-only contract, and no Chowly text prices or tiers an API - there is simply no subscriber API. The raw-data half, however, is real and un-gated: chowly/Navigating-the-Restaurant-Control-Center.txt documents on every report tile 'The Three Dots icon shows a drop-down list of other actions you can do with your data: Sort, Download, Refresh data, Copy to clipboard, and Format', inside the standard Restaurant Control Center, with no tier or fee mentioned anywhere (Terms 6(a) publishes only a set-up fee plus per-location monthly fee with a $35 minimum). A flat no would erase the data-access half the claim asks about; the honest value is partial: report data export is included in the standard dashboard, but there is no subscriber API at any price, and export is per-tile download rather than raw data. Grade B (help-centre). Analyst note: API access is not part of any Chowly restaurant subscription at any price: the vendor states the API is available only to POS systems that have built to it, i.e. gated behind a partner build, which is the claim's named failure mode (partner/enterprise-only gate) rather than inclusion in the standard subscription. Raw-data access for subscribers is the manual per-tile Download (Navigating-the-RCC). Pricing corroboration: Terms 6(a) publishes only 'a one-time set up fee per location, and a monthly fee per location ... $35 per month minimum fee per location' and defers the schedule to a private Onboarding Form; Google-Direct-Order-with-Chowly-Overview says 'All of Chowly's core products are included at no additional cost' but also 'you will not be bumped up to the next pricing tier', confirming tiers exist without listing them; chowly.com comparison pages say pricing is 'Custom-quoted per restaurant based on location count and the products you choose'. None mentions API or data access as a subscribed product. Audit caveat: the prior pass called this unresolved because there is no operator API product to price; this proposal reads the partner-only restriction as the positive absence. https://chowly.help/s/article/Navigating-the-Restaurant-Control-Center · retrieved 2026-09-03 adversarially verified

Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator

reporting-tier-paywall

Quote: "All of Chowly's core products are included at no additional cost. ... Ordering with Google is free for all Chowly partners. Meaning that you will not be bumped up to the next pricing tier, and there are no setup costs." Present: the Restaurant Control Center's seven reporting pages include Product Mix (PMIX: 'Number of Items Ordered, Average Item Price, and Number of Modifiers Ordered' with Menu Item/Platform/Service Type filters), Locations and Sales-by-Location multi-location comparison, and an Orders page with 'Error Rate' and 'ERROR OR CANCELLATION REASON' per order; RCC access is granted to any Chowly customer by asking Support ('To sign up for access to Chowly's Restaurant Control Center, you must reach out to our Support Team') with no plan qualifier, and the help centre says core products carry no additional cost. Named shortfalls: (1) the same article confirms 'the next pricing tier' exists and no document states which tier includes the RCC - Terms 6(a) publishes only a per-location monthly fee with a $35 minimum and defers the schedule to a private Onboarding Form, and chowly.com says pricing is 'Custom-quoted ... based on ... the products you choose'; (2) Chowly holds no labor data, so labor-vs-sales cannot exist; (3) comps/voids audit is only third-party cancellation/error reasons; (4) the Smart Pricing and Delivery Buydown pages depend on separately elected products (Terms 2(f)). Grade B because the carrying sentences are help-centre. https://chowly.help/s/article/Google-Direct-Order-with-Chowly-Overview · retrieved 2026-09-03 adversarially verified

Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator

reporting-history-retention

325th: MOVED unknown -> no (B). CLAIM: the vendor DOCUMENTS a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. VERDICT: no - nothing in any Chowly surface documents a retention window, so the documentation the claim requires does not exist. NEW SURFACE: the RCC's complete public source-map set (1,050 sources, 830 .ts/.tsx, 3/3 chunks mapped; nonsense controls as on delivery-zones-polygon). `retention|retain` = 0 hits across all 830 files; the date controls in the app are open-ended (CustomDatePicker/CalendarPicker with no min date, `OrderReportFilter.start_date/end_date` unbounded), and the reporting pages hand the range to a Sigma embed whose backing window is set outside the app. BOUND/CONTROLS: the 583-article chowly.help Salesforce Knowledge census (100% of the publisher's manifest, taken in the 324th) returns `retention|archive|purge` = 1/583 docs / 1 hit and it is POISON - 'enhance customer retention' in COO-and-Chowly-Platform-FAQ, marketing prose about repeat guests, not data retention; `months\s+of\s+history|historical\s+data` 0/583 docs; `truncat` 3/583 docs and all POISON (UI text-truncation fixes in three release-note articles). https://chowly.com/terms-and-conditions/ carries no retention or archive clause (section 4(e) requires only that the Restaurant 'uninstall and destroy all copies of the Software' on termination). Retrieved 2026-09-17. https://chowly.app/static/js/main.54b02cd0.js.map · retrieved 2026-09-17 adversarially verified

Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator

reporting-anomaly-alerts

325th: MOVED unknown -> no (B). NEW SURFACE: the RCC's complete public source-map set (asset-manifest lists 3 JS and 3 maps; main map 6,180,398 bytes starting {"version":3; .NONSENSE.map 404s; 1,050 sources / 830 .ts/.tsx). CLAIM: operator-configurable threshold or deviation alerts pushed to the operator on reporting metrics. VERDICT: no - the shipped app has no alert configuration of any kind. EVIDENCE: the complete reporting surface is ten pull-only pages (features/reporting/Reporting.tsx reportingPageCardLinks) rendering sixteen Sigma Computing embeds (config.ts sigmaPages) through a signed embed URL (api/dashboard/sigmaUrl.ts GET /api/v3/dashboard/sigma_url/reports); a Sigma embed exposes no subscription UI in this app. features/health/Health.tsx and its Shortcuts (MenuImportShortcut, PlatformShortcut, PrepTimeShortcut) are a pull dashboard, and the only push channels in the code are transient in-session toasts (react-toastify), the NotificationBanner component and Pusher order events (hooks/usePusherMessages, useBulkOrderActionListener) - none of them operator-configured, none threshold-based. BOUND/CONTROLS over the 830 shipped files: `alert|alerts` 11 files / 12 hits, all POISON (the MUI-based AlertModal/AlertContainer components, one browser `alert()` in AddLocation, styled 'alert' colours); `threshold` 5 files / 8 hits, all POISON (ScrollIndicator and useIntersectionVisibility scroll thresholds, a midnight-merge threshold); `notify|notification|notifications` 36 hits, all the banner/toast components; `subscribe|subscription` 20 hits, all RxJS/websocket subscriptions. Over the 583-article census `threshold|alert|alerts` = 19 docs / 27 hits and every one is Koala-internal Datadog/OpsGenie monitoring, a store banner, a curbside arrival notification or CCPA/ADA text - no operator-configured metric alert. Retrieved 2026-09-17. https://chowly.app/static/js/main.54b02cd0.js.map · retrieved 2026-09-17 adversarially verified

Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.

reporting-nl-query

Quote: "What analytics does it include? + Week-over-week trends, custom date-range reports, top-selling items, the locations driving the most order volume, cancellation rates, and average basket size by location." Positive vendor statement that its AI layer is not a prompt-driven assistant: every one of the eight /agents/ pages repeats 'Most AI hands you a report to go fix. Or a chatbot. This agent works 24/7 ... based on data and intelligence', and the platform's AI is defined as autonomous actions ('Data -> Intelligence -> Action'), not question answering. The analytics surface is separately enumerated on solutions/restaurant-control-center: 'What analytics does it include? + Week-over-week trends, custom date-range reports, top-selling items, the locations driving the most order volume, cancellation rates, and average basket size by location' - fixed reports, no query box - and the seven help-centre reporting pages describe only dropdown/filter-driven tiles. The only chat in the product is the RCC's support chat ('Clicking it will open up Chowly's chat feature and allow you to speak directly with a member of Chowly's Support Team', Navigating-the-RCC), and the owner.com comparison stresses 'Not a chatbot. Not a help center.' Chowly also holds no labor data. Audit caveat: 'not prompts' is positioning copy, so this is a grade-C no; the fallback is unknown. https://chowly.com/solutions/restaurant-control-center/ · retrieved 2026-09-03 adversarially verified

Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator

reporting-guest-cohorts

Guest-level cohorting exists, but in the Campaign Agent rather than in reporting. The Campaign Agent page documents "Audience segmentation by RFM (recency, frequency, monetary value)" with segments built on "Frequency, recency, last-order item - segments built in real time", plus "Welcome sequences for new customers", "Win-back automation for lapsed customers before they fully churn", "Churn Signals" for "Customers showing pre-churn behavior - silent-too-long alerts", and targeting of "first-time customers or VIPs". That covers new-versus-returning, visit frequency and monetary-value cohorts tied to identifiable guest records. Named shortfalls: (1) this is a chowly.com product page, grade C, not documentation - no admin guide describes the segment definitions or their reporting output; (2) the segments are campaign-targeting audiences, not a report of guest counts, and no new-vs-returning count, visit-frequency distribution or lifetime-spend cohort report is documented; (3) it is a separate paid AI-agent product, not part of the Restaurant Control Center's analytics, whose surface is a closed seven-page list (Locations, Sales, Orders, Product Mix, Week over Week, Delivery Buydown, Smart Pricing) with no guest dimension beyond a CUSTOMER NAME column in the Orders page Order Detail tile; (4) third-party marketplace orders arrive without guest identity, so cohorts can only cover first-party and loyalty guests. https://chowly.com/agents/campaign/ · retrieved 2026-08-08

Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator

reporting-sales-forecast

The RCC's reporting surface is enumerated identically in all seven of its reporting articles - "There are seven different reporting pages: Locations, Sales, Orders, Product Mix, Week over Week, Delivery Buydown, and Smart Pricing" - and each article then describes every tile on its page. Not one tile is forward-looking. The page the first pass could not read, and named as the one place a forecast could plausibly hide, is Smart Pricing, and it is wholly retrospective: Total Sales, Total Markups ("the dollar amount of additional sales made by your selected locations due to Smart Pricing"), Average Basket Size, a Smart Pricing Order Details table, and a Sales and Markups bar chart where "The X-axis represents each day of the week". Week over Week is likewise historical (Previous Week Sales for days 8-14, Last Week Sales for days 1-7, Percentage Change, Last 12 Weeks Sales). Smart Pricing does run a demand model internally - Upcharge-Settings-on-the-Restaurant-Control-Center: "upcharges are automatically configured using our AI algorithm, which is designed to maximize revenue during busy periods" - but its output is a price, not a published forecast, and nothing at daypart or hourly granularity is exposed in the reporting UI or consumable by any scheduling or ordering workflow. Chowly holds no labor data, so there is no scheduling workflow to consume one. read via the chowly.help Salesforce Aura record endpoint (getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c); the HTML at this URL is the site's CSS-error SPA shell. https://chowly.help/s/article/Smart-Pricing-Reporting-Page-on-the-Restaurant-Control-Center · retrieved 2026-08-08

Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.

reporting-tip-tax-compliance

Chowly does hold tip and tax data — the Control Center’s Order Detail tile carries a TIP column and a SALES TAX column — so the cell cannot be dismissed for want of data. What Chowly allocates away by name is the compliance function: its support-routing article puts tip distribution on the POS support desk, alongside printer and KDS routing. Nothing in the corpus describes a tip-allocation, tip-credit or 8027-style report on any Chowly surface. Bounded: this settles where tip compliance is handled, not whether the operator’s POS provides it. https://chowly.help/s/article/When-to-contact-Chowly-vs--POS-3rd-Party-Support · retrieved 2026-09-06 adversarially verified

Supports a named organizational hierarchy of at least three levels (e.g. enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations.

multi-location-org-hierarchy

325th: MOVED unknown -> no (B). NEW SURFACE: the RCC's complete public source-map set (see delivery-zones-polygon for the nonsense controls; 1,050 sources / 830 .ts/.tsx). CLAIM: a named organizational hierarchy of at least three levels as a first-class object reporting and permissions can be scoped to. VERDICT: no - the shipped object model is two levels, organization -> location. EVIDENCE: api/models.ts ships the whole Organization type as a closed 22-field record - `export type Organization = { id, name, coo_slug, ovation_company_id, ovation_default_user_id, chowly_platform, ovation_onboarding_started, ovation_phone_verified, ovation_phone, approval_email_list?, email_approval_users?, sms_approval_users?, dynamic_pricing_provider?, meta_fields_data?, surveys_active?, coo_dynamic_pricing_enabled?, loyalty_adapter?, website_accessibility?, loyalty_signup_bonus?, google_place_id?, google_feature_id?, promo_ceiling_enabled?, promo_ceiling_max_percentage?, promo_ceiling_max_dollar? }` - with no parent, region, group, brand or concept field; the location (partner) side carries only `organization_id` / `organization_name`. Scoping is therefore a flat set: components/PageOrganizationSelector + PageLocationSelector + MultiLocationDropdown pick an organization and then a list of locations, and features/account-management/AccountManagement.tsx renders each user's access as two flat chip lists, 'Organizations/Logos' and 'Locations'. The permission enum has exactly one location-scoping member, 'Access to all locations on Manage Locations page'. BOUND/CONTROLS: over the 830 shipped source files, `parent_organization|parent_id|region|district|group_id|brand_id|concept` = 0 real hits; POISON: `region` matches only ARIA `role="region"` and aria-live comments, `concept` only two TODO comments ('menu override concept', 'a DISPLAY concept, not a status'). Over the 583-article chowly.help census: `region|district` 3/583 docs, all poison (an Aloha regional email address; two Koala Android/iOS app-region deployment notes), `franchise|franchisee|franchisor` 0/583. Retrieved 2026-09-17. https://chowly.app/static/js/main.54b02cd0.js.map · retrieved 2026-09-17 adversarially verified

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

multi-location-central-menu-publish

"Update your POS menu once and push the changes to every delivery channel on demand" - the push axis is channel, not location set. No publish or version history showing what was pushed, when and by whom. https://chowly.com/solutions/restaurant-control-center/ · retrieved 2026-08-01

Corporate menu items expose per-field override rules so a location can change some attributes (e.g. price, availability) while corporate locks others (e.g. name, image, recipe), and locked fields are not editable at store level. differentiator

multi-location-local-override-policy

Quote: "This upcharge is then applied to whatever price you have set for your menu items in your POS system. For example, if you have an item that costs $10.00 in your POS system, a 5% upcharge will make this item appear as $10.50 to customers ordering online." The one per-location override Chowly exposes is price: a per-location upcharge percentage (all platforms at once, or per platform) layered on the POS price. Every other item attribute is mirrored read-only from the POS and cannot be edited at store level in Chowly at all (FAQ-Chowly-s-POS-API-Integration: 'Chowly cannot: make changes to menus. make changes to menu items. ... change photos or descriptions. change tax rates'; Product-Mix reporting: 'The name of the items and modifiers as they exist in the POS system'). SHORTFALL: this is a fixed product design, not a configurable per-field override policy; there is no corporate-vs-store role, no lock/unlock rule per field, and the price lever is a blanket percentage rather than an item price. On the Koala/Olo enterprise path menu authority sits in Olo ('Brand Menu Admins'), which is Olo's feature. Square-with-Chowly-Overview separately says '(3) Pricing Overrides are not currently a supported feature' (Square item-level price overrides do not survive sync). https://chowly.help/s/article/Upcharge-Settings-on-the-Restaurant-Control-Center · retrieved 2026-09-03 adversarially verified

Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.

multi-location-price-zones

Same single sentence is doing double duty. "Up-charge percentages by location" is per-location markup on the marketplace menu, not price zones — no zone/group object, no distinct item prices per zone, and it does not touch in-store POS pricing at all (the POS remains the price master). Marketing-page evidence only. https://chowly.com/solutions/restaurant-control-center/ · retrieved 2026-08-01 adversarially verified

Menu, price, and promo changes can be scheduled to activate at a future date/time interpreted in each target location's own timezone, and can be rolled back after activation. differentiator

multi-location-scheduled-publish

Quote: "(8) Change Time Limit on 86ed Item or Mod: Clicking on the green clock icon will allow you to change settings on when the 86ed item or mod is set to come back in stock. You will have the following three (3) choices for when the item or mod comes back in stock: At the start of the next open day (This is the default option unless changed) At a custom date and time 86'd Indefinitely" Future-dated activation is documented natively for three availability objects, each per location: (a) 86'd items/modifiers return 'At a custom date and time' or 'At the start of the next open day'; (b) paused platforms reopen at a chosen date/time (Home-Page-on-the-RCC: 'A pop will appear, allowing you to select a date and time to reopen'); (c) Holiday Hours are set for 'a single date in the future' and 'Holiday Hour settings are relative to the location's time zone' (FAQ-How-Do-I-Set-Up-Holiday-Hours) - which answers the claim's timezone limb for hours. SHORTFALL: no scheduling exists for menu content, price (the Upcharge field has no schedule) or promos - those publish immediately on Save/Publish or on the POS resync - and no rollback after activation is documented anywhere. Olo's 'Availability Schedule' recommended in Koala-Olo-Menu-Partners-Olo-Menu-Webhooks is Olo's feature, not Chowly's. https://chowly.help/s/article/Suspending-Items-Restaurant-Control-Center · retrieved 2026-09-03 adversarially verified

A new location can be provisioned by cloning a documented configuration template (menu, taxes, roles, printers, modifiers, tenders) rather than being configured from scratch, and the vendor publishes the expected time-to-open. differentiator

multi-location-new-store-template

Half the claim is met. Time-to-open IS published: the article 'explains the process for adding a new Kiosk location. which generally be completed within 1-2 weeks'. But the documented process is not a template clone - it is 'Step 1: Reach out to Support' ('reach out to support@koala.io including the new location store number and ID so we can unlock the location') then 'Step 2: Configure Location Assets' (upload a Welcome Screen image, ensure location-specific items have images, update the payment location ID). Koala-Square-Menu-Partners-Creating-Locations similarly walks the operator through creating each location by hand in Square, and Koala-General-Configurations-Managing-Locations shows the per-location fields are filled in individually (Payment Location ID, Loyalty Reference ID, Delivery Order URL, Alcohol Verification PIN) with no copy-from-existing-store control. Shortfall: no cloneable configuration template; nothing covering taxes, roles, printers, modifiers or tenders, which live in the POS rather than in Chowly; and provisioning cannot complete without Chowly/Koala support unlocking the location. https://chowly.help/s/article/Koala-iOS-Kiosk-App-Deployment-Adding-a-New-Kiosk-Location · retrieved 2026-08-08

The permission model distinguishes a franchisor/corporate tenant from an independently-owned franchisee tenant, so corporate can see franchisee sales and enforce config while the franchisee owns its own employees, banking, and labor data. differentiator

multi-location-corp-vs-franchisee-roles

325th: MOVED unknown -> no (B). NEW SURFACE: the RCC's complete public source-map set (nonsense controls as on delivery-zones-polygon; 830 .ts/.tsx files). CLAIM: the permission model distinguishes a franchisor/corporate tenant from an independently-owned franchisee tenant, so corporate can see franchisee sales and enforce config while the franchisee owns its own employees, banking and labor data. VERDICT: no. EVIDENCE: the shipped role enum is `UserRole { CHOWLY_ADMIN = 'Chowly Admin', CHOWLY_SUPPORT = 'Chowly Support', RESTAURANT_MANAGER = 'Restaurant Manager', RESTAURANT_EMPLOYEE = 'Restaurant Employee' }` (src/config.ts) - the only tenancy distinction it encodes is vendor staff versus restaurant staff, and `permittedFeaturesByRole` gives Restaurant Manager every feature except 'Access to all locations on Manage Locations page'. There is no corporate-versus-franchisee axis anywhere in the model: the Organization record (api/models.ts, 22 fields, quoted in full on multi-location-org-hierarchy) has no parent or franchisee field, and a user's access is a flat chip list of organizations and locations in the read-only Account Management user list. The claim's second limb has no object in the product either: Chowly holds no employee, banking or labor record - `labor|labour` 0/830 files, `employee|employees|staff` 1/830 (the role name itself), and the reporting order record (api/orderManagement/types.ts ReportingOrder, a closed 33-field attribute list) carries customer, delivery address, platform, subtotal, tax, tip, total, payment_provider and states, with no employee, server, wage or bank field. BOUND/CONTROLS: complete RCC map set plus the 583-article chowly.help census, where `franchise|franchisee|franchisor` = 0/583 docs / 0 hits (tokenised, word-boundary, case-insensitive). Retrieved 2026-09-17. https://chowly.app/static/js/main.54b02cd0.js.map · retrieved 2026-09-17 adversarially verified

Calculates franchise royalty, ad-fund, and marketing-fee amounts automatically from POS net sales on a defined schedule, with a configurable royalty basis (gross vs net of discounts/comps/third-party). differentiator

multi-location-royalty-calculation

No franchise financial management in the product line. https://chowly.com/chowly-platform/ · retrieved 2026-08-01

Supports automated ACH/debit collection of calculated royalties and fees from franchisee accounts, with a franchisee-visible statement of what was charged.

multi-location-royalty-collection

The premise that Chowly has no franchise financial product is stated nowhere in the corpus, and Chowly demonstrably serves franchise systems: the Mr. Jims.Pizza case study describes 45-plus locations and repeatedly names franchisees, and the multi-concept-groups page sells central reporting to hospitality groups. The word "royalty" appears in no form, which on this vendor is not evidence of absence, and the Terms’ fee section describes only Chowly’s own setup, monthly and Google Ordering fees while deferring the rest to a non-public Onboarding Form. A document describing franchisor-side billing would settle it. || 327th: 327th: the scope premise the old note called unsourced is now CITED to vendor legal, though it still does not license a no. The 2026-01-13 Terms and Conditions enumerates every fee that flows between the parties - 'a one-time set up fee per location, and a monthly fee per location in advance of each month', a '$35 per month minimum fee per location', and Google Ordering fees of '$0.30 per order, plus 2.9% of the order amount, and Chowly up to 10% of the Base Order Value' - all of them Chowly-to-Restaurant, with no franchisor, franchisee or royalty party anywhere in the agreement. CONTROL /franchis|royalt/i = 0/583 chowly.help articles (100% of the Knowledge manifest), 0/958 chowly.app RCC sources, 0/910 cms.koala.io sources; the rebuilt chowly.com returns 9/167, and every one is SEO blog prose about franchise chains as a comparison class (POISON: the blog corpus discusses other vendors' customers, never a Chowly franchise product). Held unknown, not no: royalty collection is a franchise-finance module Chowly's product does not contain at all. Retrieved 2026-09-18. adversarially verified

Provides above-store reporting that aggregates sales, labor, discounts, voids, and item mix across any selected set of locations in one view, with store-vs-store ranking and variance flags.

multi-location-consolidated-reporting

Restaurant Control Center consolidates multi-location data into one hub with drill-down by location and platform; Golden Krust consolidated 125+ locations, cutting order errors 15%. Scope is sales, channel, cancellations, errors and basket size - not labor, voids or discounts. https://chowly.com/solutions/restaurant-control-center/ · retrieved 2026-08-01

Item-level sales roll up across locations under a shared corporate item ID even when stores have renamed or locally priced the item. differentiator

multi-location-normalized-item-rollup

Item-level sales do roll up across locations, and across differing local prices, but by NAME rather than by a corporate item ID. The Product Mix page reports over the whole selected location set ("All of the Reports Pages initially shows data for every single location over the last 7 days. Location sets and time ranges can be adjusted") and its Items Detail and Modifiers Detail tables are keyed on "Menu Item and Modifier: The name of the items and modifiers as they exist in the POS system and on third party platforms", with columns Ordered, Sales, Avg Price and "Min and Max Price: The minimum and maximum price paid for the menu item and/or modifier (differs when varying upcharges are used)" - i.e. one row aggregates the same-named item even where the price differs by location or platform, which is exactly the locally-priced half of the claim. NAMED SHORTFALL: there is no shared corporate item identifier anywhere in Chowly's documented data model. The join key is the POS item name, so a store that renamed the item would produce a separate row; Koala-General-Configurations-Managing-Locations shows the only cross-system identifiers stored per location are the Olo location ID, a Square payment location ID and a Punchh loyalty reference, none of them item-level, and no article in the corpus documents any item-mapping or normalisation step. read via the chowly.help Salesforce Aura record endpoint (getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c); the HTML at this URL is the site's CSS-error SPA shell. https://chowly.help/s/article/Product-Mix-Reporting-on-the-Restaurant-Control-Center · retrieved 2026-08-08

Gift cards issued at one location are redeemable at any other location in the brand, with a reported outstanding-liability balance and inter-store settlement/redemption reconciliation between owners.

multi-location-cross-location-giftcard

Gift cards can be redeemed, but nothing else in the claim is present. 'Koala offers gift card support for Olo brands, keying off of configurations in Olo. There is not a setup required on the Koala side and all setup is automated based off Olo configurations... (1) Koala keys off of Olo to determine whether or not Gift Cards are supported. (2) Koala keys off of Olo to determine whether or not Split Tender is supported. If Supported - A guest will be able to split payment across a gift card and another form of payment. If Not Supported - A guest will only be able to use a gift card if the value of the gift card covers the entire cost of the order.' Shortfalls: Chowly/Koala issues no gift card and holds no balance, so brand-wide redeemability is Olo's property and is nowhere stated; the feature is listed in Koala-Web-Ordering-Feature-Set only under 'For Olo Users Only: Add-On Features > Checkout', so Square-menu and non-Olo brands do not get it; and no outstanding-liability report and no inter-store settlement or redemption reconciliation appears in any of the 160 articles, on the 169-URL chowly.com sitemap, or among the 41 services on Chowly's status page. https://chowly.help/s/article/Koala-Checkout-Configurations-Olo-Users-Only-Gift-Cards-Support · retrieved 2026-08-08

A single customer loyalty profile, balance, and stored order history is shared across all locations in the brand rather than being per-location.

multi-location-cross-location-loyalty

The profile is brand-scoped, the balance is not Chowly's. Koala-Web-Ordering-Feature-Set lists under 'SSO + LOYALTY': 'Create a new account', 'Sign in to an existing account', 'View order history and quickly reorder past orders', 'Favorite an order or location', 'Apply a loyalty reward to the basket', 'Save and delete credit cards', 'Earn and redeem loyalty points' - one account per brand app covering all its locations, and Koala-Account-Configurations-Favorite-Locations confirms the account carries a chosen location ('Koala migrated its Favorite Location logic to sync with a brand's CRM provider... Required / Optional / Disabled'). Shortfalls: the block is headed 'For Olo Users Only: Add-On Features' and 'Features may vary by integration partner (Punchh, Paytronix, Spendgo, etc.)', so this is not native and not universal; the points ledger is held by that partner, and Koala-General-Configurations-Managing-Locations shows Koala only stores a per-location 'Loyalty Reference ID... used to associate a given location with a Punchh location', which is a mapping, not a shared balance; and neither Chowly nor Koala states anywhere that a balance earned at one location is redeemable at another. chowly.com/solutions/loyalty-program/ (grade D) frames the same capability by channel, not by location: 'customers earn points on the website, in the mobile app, or at the register'. https://chowly.help/s/article/Koala-Web-Ordering-Feature-Set · retrieved 2026-08-08

A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. differentiator

multi-location-multi-brand

Multi-concept operation is documented, but not the separation the claim asks for. 'Koala offers a Responsive Web template to support Cross-Concept Food Halls. This template allows a brand with multiple "themes" or "concepts" to group items from a master menu under an individual concept so a user can navigate via concept but order items from across the menu in one transaction. Using a tagging system in the Brand CMS, we allow restaurants to add each concept to the system using either plain text, images or icons.' An optional splash page lets a guest pick a concept after choosing a location, and Koala-Web-Ordering-Feature-Set lists 'Cross-concept Food Hall Template (e.g., ghost kitchen)' and a 'Food Hall' menu navigation type. Shortfalls: the article states outright that 'Purchases across items aggregate in a single basket', so there are no separate per-brand receipts or tenders; concepts are tags on one master menu rather than distinct menus; no separately reportable per-concept revenue is documented anywhere (the RCC reports slice by platform and date only); and Chowly owns no terminal or drawer at all - its only hardware, per its own status page, is 4G LTE, 2G WiFi and Ethernet printers. FAQ-Virtual-Restaurant is published but its body is empty, so the vendor's own virtual-brand answer is a stub. https://chowly.help/s/article/Koala-Menu-Configurations-Food-Hall-Template · retrieved 2026-08-08

Tax configuration is per-location with support for multiple simultaneous tax rates, jurisdiction-specific rules (e.g. prepared-food vs grocery, inclusive vs exclusive tax), and per-location tax exemptions.

multi-location-multi-tax-jurisdiction

Tax configuration lives entirely in the underlying POS. https://chowly.com/pos/ · retrieved 2026-08-01

Supports locations operating in different currencies and languages within one enterprise account, with consolidated reporting converted to a reporting currency.

multi-location-multi-currency-locale

Chowly's own deployment documentation states the product does not operate outside one country, which forecloses locations in different currencies. Koala-iOS-Mobile-App-Deployment-App-Creation, step 8: "Navigate to 'Pricing & Availability' and set availability to 'United States'. Koala's application does not currently support usage outside of the United States." Koala-Android-App-Deployment-Testing-Releasing, step 5: "Ensure you add a Country/Region - Koala recommends only selecting United States as our Android App will not work outside of these areas." Consistent with that boundary and with no contrary evidence anywhere: Koala-General-Configurations-Managing-Locations enumerates the entire per-location settings screen (Username/Olo location ID, Payment Location ID, Delivery Order URL, Loyalty Reference ID, Alcohol Verification PIN, three location statuses, ASAP Ordering) with no currency, locale or timezone field; "currency" occurs twice in 204 article bodies and both are Punchh banked-currency rewards; "language" occurs only in iPad setup steps; every amount in https://chowly.com/terms-and-conditions/ is USD ("$35 per month minimum fee per location"; "$0.30 per order, plus 2.9%"); creating-a-stripe-account-for-chowly requires a US EIN or SSN and an IRS Letter 147C/SS-4; the only compliance article is US state law (Koala-California-Stores-Only-Compliance-CA-AB1276); and chowly.statuspage.io runs America/Chicago. SCOPE NOTE for anyone contesting this: the two quoted statements are about Koala's mobile and Android ordering apps specifically, and no article states a supported-country list for the Restaurant Control Center or the third-party marketplace path; no consolidated reporting-currency feature is described anywhere either way. read via the chowly.help Salesforce Aura record endpoint (getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c); the HTML at this URL is the site's CSS-error SPA shell. https://chowly.help/s/article/Koala-iOS-Mobile-App-Deployment-App-Creation · retrieved 2026-08-08

Produces an immutable audit log of who changed which configuration object (price, tax, permission, discount) at which location and when, exportable or queryable by corporate. differentiator

multi-location-config-audit-log

325th: MOVED unknown -> no (B). NEW SURFACE: the RCC's complete public source-map set (nonsense controls as on delivery-zones-polygon). CLAIM: an immutable audit log of who changed which configuration object (price, tax, permission, discount) at which location and when, exportable or queryable by corporate. VERDICT: no. EVIDENCE: the shipped app contains exactly ONE audit surface and it is scoped to email-marketing campaigns, not configuration. api/campaignAuditLogs/index.ts calls GET /api/v3/organizations/:organizationId/campaigns/:campaignId/audit_logs and its own comment says 'chowly-api proxies marketing-app''s Rails Event Store stream. Returns { events: [{ event_id, event_type, data, metadata }], meta: { total_count, limit, offset } }'; every event_type is prefixed 'CampaignAudit::', and components/AuditLogTimeline/AuditLogTimeline.tsx renders it as a per-campaign status timeline (actor email or 'System', timestamp, fromStatus -> toStatus, an optional feedback reason). Nothing writes or reads a history for the objects the claim names: the configuration screens (LocationUpcharge, ServiceFee, PlatformUpcharges, dynamic-pricing ScheduleBuilder, HoursModal/HolidayHours/MenuHours, DeliveryArea, DeliveryFeeSettings, OrderAmountRestrictions, PromoCodes, SchedulingSettings, CheckoutPageSettings, MenuSyncSettings) all end in a PUT/PATCH with a success toast and no history call, and the nearest thing to a change history, MenuImportHistoryDrawer, reads api/reporting/sync_lifecycles/:id - machine sync stages and durations with no actor. There is no export of any audit; the only export endpoints in the whole API table (src/config.ts chowlyApi, ~140 named endpoints) are `orderManagementExport: '/api/v3/reporting/orders/export_csv'` and `loyaltyDinersExport`. BOUND/CONTROLS: complete RCC map set (830 .ts/.tsx) + the 583-article chowly.help census. Controls over the app: `audit` 5 files / 14 hits - the campaign audit log (3), the campaign Block/BulkBlock modals (2) and 7 in features/support/Support.tsx; `immutable` 0; `retention|retain` 0. Over the 583 articles: `audit|audit\s+log|change\s+history` 2 docs / 3 hits, both POISON - 'Audit Background' inside Koala: ADA Compliance (an accessibility audit) and one marketing ownership guide. Retrieved 2026-09-17. https://chowly.app/static/js/main.54b02cd0.js.map · retrieved 2026-09-17 adversarially verified

Supports SSO via SAML or OIDC against the customer's identity provider for back-office/above-store users, with SCIM or equivalent for automated deprovisioning. differentiator

multi-location-enterprise-sso

CLAIM: SSO via SAML or OIDC against the customer's identity provider for back-office/above-store users, with SCIM or equivalent for automated deprovisioning. VERDICT: no. BOUND: the 100% chowly.help census (583/583 articles, Salesforce guest knowledge API, all bodies; 44/44 already-cited article URLs inside it). CONTROLS, tokenised case-insensitive over the 583 stripped bodies: /\bSAML\b/ 0/583; /\bOkta\b|\bAzure\s+AD|\bEntra\b|\bOneLogin\b|\bsingle\s+sign/ 0/583; /\bSCIM\b/ 0/583. THE POISON, and it is the decisive part of this verdict: /\bSSO\b/ returns 19/583 and EVERY occurrence is CONSUMER/DINER social login inside the Koala guest ordering app, never an admin identity provider - 'Added front-end support for Olo SSO. Added option to sign in with Apple SSO'; 'Added support for configuring Apple and/or Facebook SSO in the CMS (Punchh only)'; 'Koala Punchh Loyalty Partners: Apple SSO'; 'Resolved issue in which a brand without SSO/loyalty would fail to load store locations'. A grep-level reading of that 19 would have produced a false yes. The back-office identity model documented for the Restaurant Control Center is username/password: 'Creating a Restaurant Control Center Account', 'Logging Into the Restaurant Control Center' and 'Forgotten Password for the Restaurant Control Center' are the complete set of RCC access articles and none mentions an IdP. Grade B. Retrieved 2026-09-17. https://chowly.help/s/article/Navigating-the-Restaurant-Control-Center · retrieved 2026-09-17 adversarially verified

Publishes a documented multi-location API (or data warehouse/BI export) that returns transaction-level data across all locations in one authenticated call, without per-location credentials. differentiator

multi-location-enterprise-api

Quote: "Order Detail This tile shows specific data about each individual order received. The default is to show order details for all selected locations over the last 7 days." Transaction-level data across all locations from one login is documented: the RCC Order Detail tile lists each individual order for 'all selected locations' with location, customer, timestamp, subtotal, tip, tax, total, platform, status, and every tile carries a Three Dots menu with 'Sort, Download, Refresh data, Copy to clipboard, and Format' (Navigating-the-Restaurant-Control-Center), so a corporate user can pull a cross-location order-level extract with one set of credentials. SHORTFALL: this is a manual dashboard download, not a documented API, data warehouse or BI export; Chowly publishes no operator-facing API reference (its status page names Orders/Menus/Acknowledge Order/SDK/V2 TOOS Partner APIs, all partner-facing and undocumented publicly; SDK-Provider-Support-Contacts: 'these features are only available to POS systems who have built to them'). Custom date ranges are supported ('Custom Ranges can be fixed or relative'). https://chowly.help/s/article/Orders-Reporting-Page-on-the-Restaurant-Control-Center · retrieved 2026-09-03 adversarially verified

Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.

multi-location-central-labor-policy

332nd: MOVED unknown -> no (B). CLAIM: labour rules (overtime, break enforcement, predictive-scheduling compliance) configurable per location/group and enforced at the terminal. VERDICT: no - no labour rule is configurable at any level of any Chowly surface; the per-location rules this claim centralises are themselves no/B on this record (labor-overtime-prevention, labor-break-compliance-by-state, labor-fair-workweek-support, 331st). PRECEDENT ON THIS RECORD: the 331st labour census (same four corpora + the App Store publisher census, Chowly Inc developer id 1726094961, 51 apps, all white-label diner ordering apps) LANDED 16 labour cells no/B in 331st batch 1 (fba9c0f) - incl. labor-clock-in-at-pos, labor-native-scheduling, labor-overtime-prevention, labor-break-compliance-by-state, labor-fair-workweek-support, labor-native-payroll, labor-payroll-export-formats - on the finding that no Chowly product surface holds an employee record, time punch, schedule, wage or tip-distribution object. This cell consumes exactly that absent data, so it follows the landed category rather than the older no-module hold; the 331st proposed it unknown only because the category was then undecided. BOUND - four censuses on disk, each 100% of its publisher's own manifest, re-verified CURRENT by the 332nd today: (a) chowly.help Salesforce Knowledge, 583/583 articles (.cache/q324/chowly/ch/arts); the listing https://chowly.help/services/data/v59.0/support/knowledgeArticles?pageSize=100 was re-paged 2026-09-18 (6 pages) and still returns 583 ids, ZERO not already held, newest lastPublishedDate 2026-06-16, so the census has not gone stale; (b) the Restaurant Control Center chowly.app, 958 sources from the complete /asset-manifest.json source-map set (.cache/q325/chowly/src; today's manifest still names main.54b02cd0.js, the censused build); (c) cms.koala.io Koala Brand CMS, 910 mapped sources (.cache/q326/chowly/cmssrc; today's manifest still names main.12caeb2d.chunk.js, the censused build); (d) all 167 chowly.com sitemap pages (.cache/q327/chowly/sitetxt). KNOWN-POSITIVE CONTROLS (tokenised, word-boundary, case-insensitive; KB/RCC/Koala/site docs hit): /\btoast\b/ 48/114/0/113, /\bmenus?\b/ 273/110/35/125 - the regexes fire. Script: .cache/q332/chowly/a/ctl.mjs, output ctl-out.json. CELL CONTROLS: /over[- ]?time (rule|threshold|polic(y|ies)|alert)s?|(meal|rest) breaks?|break (rule|enforcement|compliance)|predictive scheduling|fair workweek/ = 0/583, 0/958, 0/910, 2/167; BOTH SITE HITS ARE POISON - blog prose about other vendors ('a time clock with break compliance, tip pooling and payouts, and payroll' describing 7shifts in resources/blogs/best-restaurant-management-software; 'Labor data flows directly from clock-in to paycheck, with break enforcement' in a research round-up). POISON NOT COUNTED: untokenised 'break' hits the JS break keyword and CSS breakpoints (153 in the Koala CMS alone). ENUMERATIONS: the RCC's src/config.ts enum AppFeatureName (23 features) and its router path table (Home, Analytics, Billing, Digital Marketing, Manage Platform, Menu Management, Order Management, Logs, Manage Locations, Dynamic Pricing), and the Koala CMS closed ROUTES table (constants/routes.ts: global menu/tags/colours/modules, web-marketing, web-ordering, mobile-iOS, kiosk config/strings, cross-sell, locations, users, settings) - no labour setting in either back office. Retrieved 2026-09-18. https://chowly.app/static/js/main.54b02cd0.js.map · retrieved 2026-09-18 adversarially verified

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

extensibility-public-api-docs

I could not locate any public API reference, auth spec, sandbox, rate limits, or changelog. The chowly.help SDK/POS API articles are indexed but did not render content, and no endpoint documentation surfaced. "No public API docs" survives — but the note should be corrected: a partner API does exist, it is just undocumented publicly. https://chowly.com/partnerships/ · retrieved 2026-08-01 adversarially verified

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

extensibility-api-access-cost

Quote: "Note: Chowly's POS API has many integration-related features, but these features are only available to POS systems who have built to them. Chowly cannot control how other POS providers choose to build to our POS API." Same evidence as reporting-api-not-upcharged: Chowly's API is not a subscriber entitlement at any tier - it is available only to POS vendors (and, per the status page and the TOOS v2 client, ordering-provider partners) that have built to it, so 'included in the base subscription' is false by the vendor's own restriction rather than by silence. Supporting: FAQ-Chowly-s-POS-API-Integration ('Chowly has it's own API specifically so other POS systems can connect to our services'); Terms 6(a) fee shape (set-up fee + per-location monthly fee, $35 minimum, rest in a private Onboarding Form) and the Google overview's 'next pricing tier' show tiers exist but list no API line item; the integration blog's 'The Chowly Platform replaces that entire stack with one platform fee, every product included, every integration built in' describes Chowly's own products, not third-party API access. Audit caveat as on the reporting twin: the prior pass held this unknown because no operator API product exists to price. https://chowly.help/s/article/SDK-Provider-Support-Contacts · retrieved 2026-09-03 adversarially verified

The vendor publishes its partner/marketplace commercial terms (referral fee, revenue share percentage, or per-location partner fee) in public documentation.

extensibility-partner-revshare

The partnerships page enumerates POS, delivery and technology partner categories and invites contact, but publishes no referral fee, revenue share, or per-location partner fee. https://chowly.com/partnerships/ · retrieved 2026-08-01

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

extensibility-free-sandbox

A sandbox exists and is named. The Apple SSO setup instructs the operator to register both a 'Production URL - Example: order.brand.com' and a 'Sandbox URL - Example: brand.sandbox.order.koala.io', and warns 'We can only support Apple SSO on one environment at a time, so if you would like to test on Sandbox before integrating on Production our team will need to know as such.' The Facebook SSO article carries the same pair, and Koala-Olo-Menu-Partners-Demo-Vendor-Locations and Koala-Square-Menu-Partners-Creating-Locations cover 'demo vendors (labs)' for testing. Shortfalls: every one of these articles is scoped 'for Koala's Enterprise customers'; the sandbox is a per-brand environment on the customer's own subdomain, provisioned during a paid implementation and gated on the Koala team; there is no self-serve signup, no seeded public dataset, and no developer portal at all (chowly.com has no /developers page and api.chowlyinc.com/api-docs returns 404). For some integrations only one environment can be active at a time. https://chowly.help/s/article/Koala-Punchh-Loyalty-Partners-Apple-SSO · retrieved 2026-08-08

Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).

extensibility-oauth-partner-apps

Shortfalls, carried verbatim from the rationale: (1) scopes are unproven — no scope parameter or scope error could be elicited without a registered client and no scope vocabulary is published anywhere, so 'scoped' is not established; (2) client_credentials is enabled alongside authorization_code and carries no operator consent step, so not every grant on this server is operator-granted, and for the authorization_code path 'operator-granted' is inferred from a sign-in gate rather than from a consent screen actually reached; (3) refresh_token is not an enabled grant; (4) the surface is partner-only and undocumented — an operator cannot discover from any published surface what a grant permits or how to revoke it. adversarially verified

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

extensibility-webhooks-push

334th: PROPOSED unknown -> partial (A). NEW SURFACE (334th, never censused or cited by any prior pass): Chowly's OWN partner API reference is served ANONYMOUSLY at https://api-docs.chowlyinc.com/toos/v2/ - a Redoc page titled 'Chowly Third Party Online Ordering Service API' with the whole OpenAPI 3.0.2 document embedded in __redoc_state (info.version 2.0.0, contact 'Chowly Engineering Team <engineering@chowly.com>', server https://api.chowlyinc.com/api/toos/v2). The 331st probed only the host root of api-docs.chowlyinc.com (empty 404); the spec lives one path down. Soft-200 control: /toos/zzz/ -> 404, /toos/v2/swagger.json -> 404, robots.txt -> 404 (no bar). The spec is CURRENT (it documents supports_quantity_modifiers and Chowly's 2030-01-01 standard suspend value). Found via a 2023 forum.bubble.io thread linking Chowly's partner guide 'Chowly TOOS API (v2)' (V 7.1, a public Google Doc, https://docs.google.com/document/d/1RNgPWLJnUReBjBZK7B6zybHGFJUaHnatJJCQYmSSXbM, which links the Redoc URL and apipartners@chowlyinc.com). The spec is CLOSED: 3 paths (GET /menus, POST /orders, GET /orders/{id}), 4 x-webhooks, 12 component schemas. Scratch: .cache/q334/chowly/a/toosv2.html, toosv2.spec.json, toos.txt. CLAIM: pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling. EVIDENCE (the spec's x-webhooks block, verbatim): 'orderConfirmation' - 'This webhook is triggered when an order is integrated into the POS.'; 'orderError' - 'This webhook is triggered when there is an error integrating an order to the POS.' (event 'order_issue'); 'menuUpdated' ('menu_updated'); 'locationStatusUpdated' - 'triggered when a location is paused or unpaused' ('location_status_updated'); each POSTed to the partner's endpoint and signed (securitySchemes.XSignature: 'a cryptographic signature derived from the the body of the request, and the location's API key'; the guide: 'HMAC SHA256 Hex Digest that uses the location's specific API key as the secret'). Webhooks tag: 'The webhook must be set up to receive post requests from the Chowly system. This webhook must handle both order and menu events.' So order status is PUSHED, not polled. SHORTFALL (why not yes): the order events are only 'integrated into the POS' and 'error integrating' - no modified, paid, voided or refunded event exists in the closed x-webhooks set, and the guide states 'It is not possible to cancel or void an order through the API once it has been sent to Chowly'; it is 'A single universal/static webhook for all locations' per integration partner, registered through Chowly staff ('Please confirm with the CS team the webhook'), behind a partnership agreement ('In order to utilize the Chowly API, a partnership agreement must be signed'), not an operator-subscribable event feed. Bounds the TOOS partner API only; the POS-side Chowly POS API remains unpublished. Retrieved 2026-09-18. https://api-docs.chowlyinc.com/toos/v2/ · retrieved 2026-09-18 adversarially verified

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

extensibility-webhook-reliability

331st: MOVED unknown -> no (B), on the DOCUMENTATION conjunct only. CLAIM: webhooks are HMAC-signed AND DOCUMENTED to retry with backoff, with a replayable event log - a conjunction, so one failed conjunct fails it. Whether Chowly emits webhooks at all is left to extensibility-webhooks-push (held); this row does not depend on it, because either way nothing is documented. BOUND - four censuses, each 100% of its publisher's own manifest, all re-grepped per cell in the 331st: (a) 583 chowly.help articles (Salesforce Knowledge REST, .cache/q324/chowly/ch/arts); (b) 958 chowly.app Restaurant Control Center sources (complete /asset-manifest.json map set, .cache/q325/chowly/src); (c) 910 cms.koala.io sources (closed manifest, .cache/q326/chowly/cmssrc); (d) all 167 pages of the rebuilt chowly.com sitemap incl. the 2026-01-13 Online Terms for Restaurants, diner terms, both privacy policies and the CCPA notice (.cache/q327/chowly/sitetxt). KNOWN-POSITIVE CONTROL: /\btoast\b/i = 48/583, 114/958, 0/910, 113/167 and /\bwebhooks?\b/i = 14/583, so the tokenised regexes fire. CONTROLS: /\bretr(y|ies|ied)\b.{0,80}(webhook|event|deliver|notification)|(webhook|event|deliver|notification).{0,80}\bretr(y|ies|ied)\b/i = 0/583, 1/958, 0/910, 0/167 (the RCC hit is a Sidekiq bulk-order-action comment on Chowly's own backend jobs, client-facing, not a delivery guarantee); /\bHMAC\b|signing (secret|key)/i = 0 in all four; /event log|replay|redeliver/i = 1/583 ('Redeliver missing items' - food, POISON), RCC 'replays' = React Query page refetch, CMS urql 'replays' map (POISON). NEW SURFACES (331st, certspotter after crt.sh; certspotter found hosts crt.sh never listed): chowlyinc.com -> api-docs.chowlyinc.com (in CT logs; serves an empty 404 to /, /swagger, /openapi.json, /api-docs, /docs and a nonsense path alike - no spec behind it), webhooks.chowlyinc.com (a Rails/Devise app titled 'Chowly' that 302s to /users/sign_in - login-gated, not read); chowly.io -> coo-api.chowly.io (production Chowly Online Ordering API; JSON 404s, and /swagger/openapi.yaml returns a 15-byte file whose entire content is 'openapi: 3.0.0' - an EMPTY spec; api.koala.io/swagger/openapi.yaml returns the same 15-byte stub; host has a generic `User-agent: * Disallow: /`, read like a browser per the standing order, not cited); chowly.help -> pos-api-emulator, validator, product, training, onboarding, operations, csm (all behind Cloudflare Access login, not read). partners.chowly.com re-probed with curl + browser UA: Cloudflare 530 'Origin DNS error' on /, /robots.txt and a nonsense path alike - the host is dead, not refusing. WEAKEST PART: webhooks.chowlyinc.com (login-gated) suggests an outbound webhook service exists; its semantics may be documented privately to partners. If the merge treats this as a webhooks capability `no` under the unpublished-partner-API rule, hold it. Retrieved 2026-09-18. || 334th CORRECTION: Chowly publishes an anonymous OpenAPI 3.0.2 spec for its partner API (https://api-docs.chowlyinc.com/toos/v2/, Redoc, v2.0.0) whose 4 outbound webhooks (order confirmation, order error, menu updated, location paused/unpaused) carry an HMAC-SHA256 X-Signature header, so the SIGNATURE conjunct IS documented and any wording above that says otherwise is superseded. The no stands on the other conjunct(s): the spec documents no retry/backoff behaviour and no replayable event log. Retrieved 2026-09-18. https://chowly.help/s/article/FAQ-Chowly-s-POS-API-Integration · retrieved 2026-09-18 adversarially verified

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

extensibility-order-injection-api

An inbound order-injection API exists but is partner-gated and undocumented. First-party evidence, replacing the third-party client the prior note leaned on: Chowly's own status page enumerates, under the 'V2 TOOS Partner API' group described as 'API used by Third Party Online Ordering Service (TooS) who have built to the Chowly API', an 'Orders API' component described as 'Third Party Online Ordering Service (TooS) Inbound Orders API', alongside a separate 'Orders API - SDK POS Orders API' and an 'Acknowledge Order API' on the POS side; api.chowlyinc.com/api/toos/v2/menus answers 401 Invalid Credentials today, so the host is live. Shortfalls: access is partner-gated with no self-serve credentials or sandbox; no request schema, field list or reference is published (api.chowlyinc.com/api-docs and /swagger.json both 404); and Chowly is middleware - the injected order fires to KDS/printers and lands in reporting via the operator's own POS, not Chowly's. The prior citation, github.com/goparrot/chowly-api-client, is withdrawn as primary evidence: it is a wrapper by GoParrot Inc. (acquired by Square) last committed 2021-07-20. https://chowly.statuspage.io/api/v2/components.json · retrieved 2026-08-08 · not refetchable · site policy · graded B when read adversarially verified

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

extensibility-menu-write-api

Menus are written into Chowly programmatically, but not by anyone the operator can direct. FAQ-Chowly-s-POS-API-Integration: 'Chowly has it's own API specifically so other POS systems can connect to our services. We call this API the "Chowly POS API"... Chowly is unable to know of any changes you make in your POS system unless your POS system "contacts" Chowly to let us know', and the POS does so either automatically on a schedule, via a manual 'Publish' button, or through its own support team. Chowly's status page names that surface explicitly: under the 'SDK API' group, a 'Menu API' component described as 'SDK Menu Update'. Shortfalls: this write path belongs to the POS vendor's SDK integration, not to operators or third-party developers - the same article states Chowly itself 'cannot make changes to menus' or 'menu items'; the only partner API a caller can reach, V2 TOOS, exposes menus read-only (GET /api/toos/v2/menus, and the status page describes its Menus API as a 'Menu Feed'), with no menu write method in the public client; and no request schema, field list or reference is published anywhere (api.chowlyinc.com/api-docs returns 404). Modifiers and prices are edited in the operator's POS, never through a Chowly API. https://chowly.help/s/article/FAQ-Chowly-s-POS-API-Integration · retrieved 2026-08-08

Every core object the API can read (orders, menu, customers, employees, inventory) can also be written or updated via the same API. differentiator

extensibility-data-symmetry

334th: PROPOSED unknown -> partial (A). NEW SURFACE (334th, never censused or cited by any prior pass): Chowly's OWN partner API reference is served ANONYMOUSLY at https://api-docs.chowlyinc.com/toos/v2/ - a Redoc page titled 'Chowly Third Party Online Ordering Service API' with the whole OpenAPI 3.0.2 document embedded in __redoc_state (info.version 2.0.0, contact 'Chowly Engineering Team <engineering@chowly.com>', server https://api.chowlyinc.com/api/toos/v2). The 331st probed only the host root of api-docs.chowlyinc.com (empty 404); the spec lives one path down. Soft-200 control: /toos/zzz/ -> 404, /toos/v2/swagger.json -> 404, robots.txt -> 404 (no bar). The spec is CURRENT (it documents supports_quantity_modifiers and Chowly's 2030-01-01 standard suspend value). Found via a 2023 forum.bubble.io thread linking Chowly's partner guide 'Chowly TOOS API (v2)' (V 7.1, a public Google Doc, https://docs.google.com/document/d/1RNgPWLJnUReBjBZK7B6zybHGFJUaHnatJJCQYmSSXbM, which links the Redoc URL and apipartners@chowlyinc.com). The spec is CLOSED: 3 paths (GET /menus, POST /orders, GET /orders/{id}), 4 x-webhooks, 12 component schemas. Scratch: .cache/q334/chowly/a/toosv2.html, toosv2.spec.json, toos.txt. CLAIM: every core object the API can read (orders, menu, customers, employees, inventory) can also be written via the same API. EVIDENCE: the closed path set is GET /menus ('Pull a feed of the standard 3rd party menu'), POST /orders ('Creates a new order') and GET /orders/{id} ('Retrieve details about a specific order'). ORDERS are symmetric (create + read back; order_details carries payload, created_at, completed_at, error_at, ticket_payload). MENU is read-only: no write path exists, and the partner guide instructs 'Prevent the customer from modifying the menu directly in your system, as this would cause their data to become inconsistent with Chowly data'; orders cannot be amended after submission ('It is not possible to cancel or void an order through the API once it has been sent to Chowly'). Customers exist only as fields embedded in an order (customer: id, name, phone, email, address...), and no employee or inventory object is exposed. SHORTFALL: one object (orders) is read/write; the menu is read-only on this API, and customers/employees/inventory are not API objects. Scoped to the published TOOS v2 partner API; the POS-side Chowly POS API (through which POS systems publish menus in) is unpublished and is not claimed here. Retrieved 2026-09-18. https://api-docs.chowlyinc.com/toos/v2/ · retrieved 2026-09-18 adversarially verified

API rate limits are published as specific numeric quotas with documented throttling behavior and headers.

extensibility-published-rate-limits

331st: MOVED unknown -> no (B). CLAIM: API rate limits are PUBLISHED as specific numeric quotas with documented throttling behaviour and headers. This is publication-shaped, so a publication census settles it (the 327th rule), and the atlas already scores extensibility-public-api-docs `no`/B for the same vendor. BOUND - four censuses, each 100% of its publisher's own manifest, all re-grepped per cell in the 331st: (a) 583 chowly.help articles (Salesforce Knowledge REST, .cache/q324/chowly/ch/arts); (b) 958 chowly.app Restaurant Control Center sources (complete /asset-manifest.json map set, .cache/q325/chowly/src); (c) 910 cms.koala.io sources (closed manifest, .cache/q326/chowly/cmssrc); (d) all 167 pages of the rebuilt chowly.com sitemap incl. the 2026-01-13 Online Terms for Restaurants, diner terms, both privacy policies and the CCPA notice (.cache/q327/chowly/sitetxt). KNOWN-POSITIVE CONTROL: /\btoast\b/i = 48/583, 114/958, 0/910, 113/167 and /\bwebhooks?\b/i = 14/583, so the tokenised regexes fire. CONTROLS: /rate[- ]?limit(s|ed|ing)?|\bquotas?\b|\bthrottl(e|ed|ing)\b|requests per (second|minute|hour)|X-RateLimit|Retry-After/i = 6/583, 4/958, 2/910, 1/167, and /\d+\s*(requests|calls|req)\s*(per|\/)\s*(second|sec|minute|min|hour|day)/i = 0 in all four. POISON, every hit named: the 6 KB hits and 1 site hit are ORDER THROTTLING (kitchen pacing - 'Order Throttling Visibility for Non-Admins', 'throttling string on Checkout'); the RCC hits are DoorDash rate-limiting CHOWLY ('DoorDash is currently rate limiting our requests.'), the OrderThrottling components and a localStorage 'quota is exceeded' comment; the CMS hits are lodash throttle and a debounce hook. Not one is a quota Chowly publishes. NEW SURFACES (331st, certspotter after crt.sh; certspotter found hosts crt.sh never listed): chowlyinc.com -> api-docs.chowlyinc.com (in CT logs; serves an empty 404 to /, /swagger, /openapi.json, /api-docs, /docs and a nonsense path alike - no spec behind it), webhooks.chowlyinc.com (a Rails/Devise app titled 'Chowly' that 302s to /users/sign_in - login-gated, not read); chowly.io -> coo-api.chowly.io (production Chowly Online Ordering API; JSON 404s, and /swagger/openapi.yaml returns a 15-byte file whose entire content is 'openapi: 3.0.0' - an EMPTY spec; api.koala.io/swagger/openapi.yaml returns the same 15-byte stub; host has a generic `User-agent: * Disallow: /`, read like a browser per the standing order, not cited); chowly.help -> pos-api-emulator, validator, product, training, onboarding, operations, csm (all behind Cloudflare Access login, not read). partners.chowly.com re-probed with curl + browser UA: Cloudflare 530 'Origin DNS error' on /, /robots.txt and a nonsense path alike - the host is dead, not refusing. So the only anonymous spec slot Chowly serves on its production API hosts is an empty OpenAPI stub, the api-docs host serves nothing, and the partner host is dead. WEAKEST PART: the 'Chowly POS API' partner guide circulates privately; if the merge reads 'published' to include private partner docs, hold it. Retrieved 2026-09-18. https://chowly.help/s/article/FAQ-Chowly-s-POS-API-Integration · retrieved 2026-09-18 adversarially verified

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

extensibility-doordash-preferred

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

Direct, first-party certified integrations exist with DoorDash, Uber Eats, and Grubhub without requiring a paid middleware layer (Otter/Chowly/Deliverect/Checkmate). differentiator

extensibility-first-party-delivery-integrations

Direct certified connections to DoorDash, Uber Eats, Grubhub, Postmates and ezCater held by Chowly itself with no middleware beneath it. Chowly IS the middleware layer other stacks pay for. https://chowly.com/partnerships/ · retrieved 2026-08-01

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

extensibility-middleware-compatibility

Chowly is a peer and competitor to Deliverect, Otter and Checkmate, not an endpoint they aggregate. The criterion does not apply to a middleware vendor. https://chowly.com/partnerships/ · retrieved 2026-08-01

Native, vendor-maintained connectors exist for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export.

extensibility-accounting-connectors

2026-09-03 re-sweep (195th): the full chowly.help corpus (204 slugs via Aura) and 86 chowly.com pages were re-read; an analyst proposed no from https://chowly.com/chowly-platform/ and the adversarial pass returned it to unknown: Quote verified in chowly-com/chowly-platform.txt (line 21 '10 Tools. One Dashboard.' followed by the ten headings). But the list does not survive the enumeration bar: it is a marketing inventory of products, not a statement of integrations, and the same site calls itself a '21-product platform' twice in resources__blogs__restaurant-automation-save-20-hours-weekly.txt, so the ten-tool list is demonstrably not complete. The automation blog's 'Here's what we automate' list is a blog (D) and claims 'a complete platform approach' as a slogan, not a closed integration catalogue. chowly.com/partnerships lists six POS partners while claiming '50+ native POS integrations' elsewhere, so the partner page is not a complete enumeration either. Grep across 185 help files and 86 chowly.com files for quickbooks/xero/netsuite/restaurant365/ledger/journal/bookkeep found zero hits, and the only 'accounting' mention is the integration blog's 'rarely line up with your POS or accounting without manual reconciliation' - a problem statement, not a non-support statement. Nothing in Chowly's text says an accounting connector is unsupported or recommends a workaround for GL posting. That is absence of evidence, so the cell stays unknown. Prior rationale: 2026-08-08 SECOND PASS. I rebuilt the chowly.help corpus myself rather than reusing the first pass's: 114 slugs from /s/sitemap-topicarticle-1.xml, then href closure inside article bodies (196 articles), then targeted slug probing, which found 8 live articles that neither the sitemap nor any in-article link reaches - Navigating-the-Restaurant-Control-Center, Home-Page-on-the-Restaurant-Control-Center, Upcharge-Settings-on-the-Restaurant-Control-Center and the Orders, Locations, Week-over-Week, Delivery-Buydown and Smart-Pricing reporting pages - for 204 bodies in total. Retrieval was POST https://chowly.help/s/sfsites/aura (RecordServiceComponentController.getArticleVersionId with urlName + en_US, then aura://RecordUiController/ACTION$getRecordWithFields on Knowledge__kav.Content__c); the HTML at every /s/article/ URL is still the site's ~466KB CSS-error SPA shell. "QuickBooks", "Xero", "Sage", "NetSuite", "journal entry" and "general ledger" occur zero times across the 204 article bodies, among the 45 components on chowly.statuspage.io/api/v2/components.json, and on the 167 URLs of https://chowly.com/sitemap.xml re-fetched today - whose non-blog set is fully enumerable and consists of eleven /solutions/ pages (branded-online-ordering, 3rd-party-marketplace-integration, dynamic-pricing, marketing-website, paid-ads, email-marketing, google-business-profile, loyalty-program, customer-surveys, mobile-app, restaurant-control-center) and eight /agents/ pages (seo, gbp, ads, campaign, pricing, review, delivery, upsell), none of them accounting. Section 2(h) of https://chowly.com/terms-and-conditions/ names the vendors Chowly subcontracts to - Nash Technologies (delivery courier), Sauce Technologies (dynamic pricing), Cookdash d/b/a Superorder (revenue reconciliation and recovery) and Ovation Up (customer surveys) - with no accounting or GL partner among them; Superorder is marketplace revenue recovery, not a ledger connector. But that clause lists vendors for elected services rather than declaring a complete integration catalogue, a sitemap is a list of published pages rather than a supported-integrations table, and chowly.com/partnerships/ (Toast, SpotOn, Square) is a directory, which the evidence rules exclude. Unresolved rather than a positive absence. || 326th: MERGE HOLD (proposed no/B, held unknown): Chowly is order middleware and keeps no sales journal of its own; the 325th rule holds a module the product lacks entirely at unknown rather than no. The three-corpus zero is kept as the bound. PROPOSAL AS WRITTEN: CLAIM: native vendor-maintained connectors for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export. VERDICT: no. BOUND - three complete corpora, none of which existed in full when the current note was written: (1) the 583-article chowly.help census (Salesforce Knowledge REST, 100% of the publisher's own manifest; bodies at .cache/q324/chowly/ch/txt); (2) the chowly.app Restaurant Control Center source-map census, 958 first-party sources; (3) SURFACE (new this pass, never censused before): https://cms.koala.io is the live production "Koala Brand CMS" - Koala is the digital-ordering company Chowly merged with, and this is the brand-config product the Koala-* articles in chowly.help describe. It is a Create-React-App SPA with a CLOSED /asset-manifest.json (58 .js.map entries) and a webpack runtime chunk-hash table of 57 lazy chunks that the manifest exactly covers; all 57 maps fetched 2026-09-18 and every one is REAL (begins {"version":3, and carries sourcesContent), 15 MB in total, 910 unique mapped sources of which 575 are Koala's own TypeScript/TSX (2.4 MB). SOFT-200 CONTROL PASSED: /static/js/zzz.NONSENSE.chunk.js.map returns a 79-byte "The page could not be found / NOT_FOUND" 404, not an SPA shell. 1 round, 0 misses. Grade B (production code the vendor does not publish as documentation). It bounds the Koala Brand CMS ONLY - not the Chowly Restaurant Control Center (chowly.app), not the POS, and not the ordering/kiosk runtimes it configures. CONTROLS, tokenised, word-boundary, case-insensitive, run over ALL THREE corpora: quickbooks 0/583, 0/958, 0/910; xero 0/0/0; netsuite 0/0/0; sage 0/0/0; "ledger" 0 and "general ledger" 0; journal 0/0/0; restaurant365 0; marginedge 0; bookkeep 0; accounting 0/583. No tokenisation poison arises because none of the control words occurs at all, in any substring. The integration catalogues Chowly does publish name POS systems and marketplaces only (Toast, SpotOn, Square, Clover, Olo, DoorDash, Grubhub, Uber Eats, and for loyalty Punchh/Paytronix); no GL or accounting destination appears on any of the three surfaces. WEAKNESS THE OWNER SHOULD WEIGH: Chowly is middleware and keeps no sales journal of its own, so this could be read as a module the product lacks entirely (hold) rather than a scored no. I score it no because an accounting connector is an integration claim rather than a POS module, and three complete corpora are silent. Retrieved 2026-09-18. || 327th: 327th: a FOURTH corpus and a contractual subprocessor list, same zero. The rebuilt Next.js chowly.com was censused in full today (all 167 sitemap URLs, none a soft-404) and /quickbooks|\bxero\b|netsuite|restaurant365|general ledger/i returns 3/167 - all three inside SEO blog posts naming other vendors' accounting tools, never a Chowly connector (POISON: the blog corpus is a software round-up genre). The same control is 0/583 chowly.help articles, 0/958 chowly.app RCC sources and 0/910 cms.koala.io sources. The 2026-01-13 Terms names the only four subprocessors Chowly uses to deliver Services - Nash Technologies (courier), Sauce Technologies (dynamic pricing), Cookdash d/b/a Superorder (revenue reconciliation and recovery), Ovation Up (customer surveys) - and none is an accounting system. Notably the closest adjacent service Chowly does sell is 'revenue reconciliation and recovery', which reconciles marketplace payouts, not a sales journal. The 325th merge hold stands. Retrieved 2026-09-18. adversarially verified

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

extensibility-payroll-export

332nd: MOVED unknown -> no (B). CLAIM: labour hours export natively to at least two named payroll providers without re-keying. VERDICT: no - Chowly records no labour hours and ships no payroll connector; the twin cells labor-payroll-export-formats and labor-native-payroll are already no/B on this record. PRECEDENT ON THIS RECORD: the 331st labour census (same four corpora + the App Store publisher census, Chowly Inc developer id 1726094961, 51 apps, all white-label diner ordering apps) LANDED 16 labour cells no/B in 331st batch 1 (fba9c0f) - incl. labor-clock-in-at-pos, labor-native-scheduling, labor-overtime-prevention, labor-break-compliance-by-state, labor-fair-workweek-support, labor-native-payroll, labor-payroll-export-formats - on the finding that no Chowly product surface holds an employee record, time punch, schedule, wage or tip-distribution object. This cell consumes exactly that absent data, so it follows the landed category rather than the older no-module hold; the 331st proposed it unknown only because the category was then undecided. BOUND - four censuses on disk, each 100% of its publisher's own manifest, re-verified CURRENT by the 332nd today: (a) chowly.help Salesforce Knowledge, 583/583 articles (.cache/q324/chowly/ch/arts); the listing https://chowly.help/services/data/v59.0/support/knowledgeArticles?pageSize=100 was re-paged 2026-09-18 (6 pages) and still returns 583 ids, ZERO not already held, newest lastPublishedDate 2026-06-16, so the census has not gone stale; (b) the Restaurant Control Center chowly.app, 958 sources from the complete /asset-manifest.json source-map set (.cache/q325/chowly/src; today's manifest still names main.54b02cd0.js, the censused build); (c) cms.koala.io Koala Brand CMS, 910 mapped sources (.cache/q326/chowly/cmssrc; today's manifest still names main.12caeb2d.chunk.js, the censused build); (d) all 167 chowly.com sitemap pages (.cache/q327/chowly/sitetxt). KNOWN-POSITIVE CONTROLS (tokenised, word-boundary, case-insensitive; KB/RCC/Koala/site docs hit): /\btoast\b/ 48/114/0/113, /\bmenus?\b/ 273/110/35/125 - the regexes fire. Script: .cache/q332/chowly/a/ctl.mjs, output ctl-out.json. CELL CONTROLS: /\bpayroll\b|\bgusto\b|\bpaychex\b|\bADP\b|\bpaylocity\b|\bpaycom\b/ = 0/583, 0/958, 0/910, 9/167; ALL 9 SITE HITS ARE POISON - SEO blog prose naming OTHER vendors' payroll features (7shifts 'payroll if you want it all in one'; 'Labor data flows directly from clock-in to paycheck'), never a Chowly connector. CONTRACTUAL ENUMERATION: the 2026-01-13 Online Terms for Restaurants (https://chowly.com/terms-and-conditions/) enumerate the whole Service at s.2 (first-party web/mobile ordering, private-label Google Ordering, courier delivery, digital marketing and ads, dynamic pricing, revenue reconciliation and recovery, Google Business Profile management, customer surveys) and name every subcontracted vendor at s.2(h) - 'Nash Technologies Inc. (delivery courier service) Sauce Technologies, Inc. (dynamic pricing services) Cookdash Inc. d/b/a Superorder (revenue reconciliation and recovery) Ovation Up, Inc. (customer surveys)' - no labour, time-clock or payroll service and no payroll vendor. Retrieved 2026-09-18. https://chowly.com/terms-and-conditions/ · retrieved 2026-09-18 adversarially verified

Raw transaction-level data can be exported on a schedule to a customer-controlled destination (S3/SFTP/warehouse/Snowflake share), not only viewed in the vendor's reporting UI. differentiator

extensibility-bi-data-warehouse

325th: MOVED unknown -> no (B). NEW SURFACE: the RCC's complete public source-map set (asset-manifest lists 3 JS files and all 3 maps; main map 6,180,398 bytes starting {"version":3; .NONSENSE.map 404s and /zzz-nope.js.map returns the 867-byte shell; 1,050 sources extracted, 830 .ts/.tsx). CLAIM: raw transaction-level data exported ON A SCHEDULE to a customer-controlled destination (warehouse/BI/object store). VERDICT: no. The complete shipped endpoint table (src/config.ts `chowlyApi`, ~140 named endpoints - the whole API the customer-facing app can call) contains exactly two export routes, both manual, on-demand, browser-download: `orderManagementExport: '/api/v3/reporting/orders/export_csv'` and `loyaltyDinersExport: '/api/v3/loyalty_accounts/export_loyalty_accounts'`. There is no destination field, no schedule, no credential store and no connector anywhere in the app; analytics is delivered the other way round, as Chowly-hosted Sigma Computing embeds fetched through a signed URL (api/dashboard/sigmaUrl.ts, config.ts sigmaPages, 16 embeds), which is a UI ceiling rather than a data feed. A partial was considered and rejected: manual CSV download satisfies none of the claim's conjuncts (scheduled, customer-controlled destination). BOUND/CONTROLS over the 830 shipped files: `sftp|s3|snowflake|redshift|bigquery|warehouse` 5 files / 7 hits, and every one is CHOWLY'S OWN internal Snowflake, never a customer destination - 'the backend only sends them once the Snowflake columns exist' (api/ovation/helpers/surveyAnalytics.ts), '`search_date` is part of the Snowflake merge key and history accumulates rather than overwriting' (api/reporting/keywordRankings.ts), 'a stale Snowflake sync leaves the split briefly out of step' (TotalSurveysCard), 'the Snowflake table casts with `_DATA:search_date::TIMESTAMP::DATE`' (Keywords/rankingsUtils.ts, useKeywordRankings.ts). So a warehouse exists behind Chowly's analytics and the customer is given no route into it; `sftp` 0, `s3` 0, `redshift|bigquery` 0; `schedule|scheduled` 272 hits are campaign send-times, menu availability schedules and dynamic-pricing schedules, never a data export. Over the 583-article chowly.help census `sftp|snowflake|redshift|bigquery|warehouse|data\s+export` = 0/583 docs. Retrieved 2026-09-17. https://chowly.app/static/js/main.54b02cd0.js.map · retrieved 2026-09-17 adversarially verified

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

extensibility-app-marketplace

Named integrations are browsable across /pos/ and /partnerships/ (Toast, Square, SpotOn, Clover, Revel, Lightspeed, Aloha, Menufy) but there is no self-install marketplace - connection is a sales and implementation process. https://chowly.com/partnerships/ · retrieved 2026-08-01

Operators can define custom fields or run vendor-hosted custom logic/scripts against POS objects without a vendor engineering engagement.

extensibility-custom-fields-scripting

Some self-serve extension exists, none of it against POS objects. Koala-General-Configurations-Pixel states the case explicitly: 'Koala currently supports pixels via Google Tag Manager, which allows you to add, modify and manage your pixels without reliance on our dev team. In order to implement GTM, just share your brand's GTM ID with your implementation manager!' Koala-Menu-Configurations-Marketing-Tags lets an operator define a global vocabulary and attach it to menu objects ('Navigate to Global Menu > Tags... select "Add New Tag"... Enter a label (required), text color (required), background color (optional) and icon (optional)', then 'Navigate to Global Menu > Products... Under Marketing Tags section, select the relevant tag'), and Koala-Menu-Configurations-Using-Filter-Tags-to-Create-Master-Categories and Koala-General-Configurations-Dynamic-String-Parameters extend the same pattern. Shortfalls: 'Custom Fields on Checkout' is listed in Koala-Web-Ordering-Feature-Set only under 'For Olo Users Only: Add-On Features', and creating one is not self-serve - Koala-Checkout-Configurations-Olo-Users-Only-Dine-In-Handoff-Mode says 'you will need to have Olo add a custom field called "Table Number"... It's critical that the custom field follows this exact naming convention'. Marketing tags 'cannot be applied to modifiers'. And there is no vendor-hosted server-side scripting, webhook handler or custom logic against orders, menus or any POS object anywhere in the 160 articles - the GTM route runs third-party JavaScript in the guest's browser, not logic against Chowly's data. https://chowly.help/s/article/Koala-General-Configurations-Pixel · retrieved 2026-08-08

The vendor supports a headless/embedded mode where a third-party UI (kiosk, web ordering, drive-thru) drives the POS transaction engine via API.

extensibility-headless-embedded

A headless ordering path exists and is described by Chowly itself. chowly.statuspage.io groups a 'Menus API' ('Third Party Online Ordering Service (TooS) Menu Feed') and an 'Orders API' ('TooS Inbound Orders API') under 'V2 TOOS Partner API - API used by Third Party Online Ordering Service (TooS) who have built to the Chowly API': a third-party UI reads the menu and injects the order through Chowly into the operator's POS. api.chowlyinc.com/api/toos/v2/menus returns 401 Invalid Credentials, so the surface is live. Shortfalls: partner-gated with no public docs, sandbox or self-serve credentials (api-docs and swagger.json 404; the partner guide circulates as a private Google Doc); and the surface is menu-read plus order-injection only - payment and the fiscal transaction stay in the underlying POS, so this is headless ordering, not a headless POS transaction engine. The prior citation github.com/goparrot/chowly-api-client is withdrawn: it is a third-party wrapper by a Square-acquired company, last committed 2021-07-20. https://chowly.statuspage.io/api/v2/components.json · retrieved 2026-08-08 · not refetchable · site policy · graded B when read adversarially verified

The vendor publishes an API changelog and a stated deprecation/notice policy for breaking changes.

extensibility-api-versioning-deprecation

CLAIM: the vendor publishes an API changelog AND a stated deprecation/notice policy for breaking changes. VERDICT: partial - the changelog conjunct is now established from the vendor's own knowledge base; the policy conjunct is not. THE EXISTING NOTE'S CONTROL IS FALSIFIED BY A LARGER CORPUS: it states the corpus holds no instance of "deprecat", but that was measured on the 195/375-body corpus. Over the COMPLETE 583-article chowly.help census (Salesforce Knowledge REST listing, 100% of the publisher's manifest; bodies cached at .cache/q324/chowly/ch/txt) /deprecat/i returns 6/583. EVIDENCE: 215 of the 583 articles are dated release notes ("Release Notes 3/12/2025", "Koala Web Release April 6, 2022", "Koala iOS Mobile Release v. 2.18", "May & June 2021 Release Notes"), and several carry an explicit API section - the Koala Web releases have a "B - ORDERING API" block. kb:May-June-2021-Release-Notes announces a breaking change to Chowly's own POS API with a sunset date: "V1 Menu API Deprecation - The V1 Menu endpoint was turned off in early June and all partners have transitioned to the V2 API. The V1 Order endpoint will be turned off August 1, 2021." kb:Release-Notes-2-6-2024 records another API break: "The total field used within our POS API for GrubHub integration has been updated to use merchant_total instead of the deprecated grand_total." SHORTFALL (why not yes): a dated changelog that announces individual sunsets is not a STATED policy - no notice period, supported-version window or sunset commitment appears in any of the 583 bodies, and there is still no public developer portal. Retrieved 2026-09-18. https://chowly.help/s/article/May-June-2021-Release-Notes · retrieved 2026-09-18 adversarially verified

A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator

extensibility-data-portability-exit

The Terms specify a post-termination obligation on the restaurant ("must uninstall and destroy all copies of the Software") and grant no data-retrieval right, format, or window. No export mechanism documented anywhere. https://chowly.com/terms-and-conditions/ · retrieved 2026-08-01

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

reliability-offline-order-entry

Pure cloud with no on-premise component; order entry is the POS's job and Chowly's channels stop when connectivity does. https://chowly.com/pos/ · retrieved 2026-08-01

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

reliability-offline-card-auth

Chowly does operate payment paths of its own: a Chowly-provisioned Stripe account carries Google Direct Order, and a Square reader paired to a Koala kiosk takes card-present payment, so the premise that Chowly never authorises a card is wrong. Nothing in the corpus describes what any of those paths do when connectivity is lost — no store-and-forward behaviour, no offline limit, no reconnect flow. The Diner Terms sentence about the merchant’s payment processor speaks to who settles a payment, not to offline authorisation. A payments or kiosk article describing behaviour during an outage would settle it. || 331st: 331st: per-cell re-grep of the four censuses: /store[- ]and[- ]forward|\bSAF\b|offline (payment|transaction|card|mode)/i = 0/583, 0/910, 0/167, and 1/958 (CRA serviceWorker boilerplate - POISON). The Koala card-present path was read in full: Koala-iOS-Kiosk-Feature-Set (a feature list that says features 'not on the list' are not yet available) itemises NO payment behaviour at all - not even card acceptance - so its silence on offline cards bounds nothing; Koala-iOS-Kiosk-App-Deployment-In-store-Operations-Best-Practices says 'Ensure the devices have a reliable internet connection' and to run a test transaction to confirm the Square reader pairing. The Koala kiosk app is not in the public App Store (iTunes search + the Chowly Inc developer census, 51 apps, are all white-label consumer ordering apps site.onlineorder.*), so no store listing or release history is available. Held: 'never affirmed' is not a capability `no`. Retrieved 2026-09-18. adversarially verified

The vendor publicly documents who bears the loss when a store-and-forward transaction declines after connectivity returns, and states any per-transaction or cumulative offline cap. differentiator

reliability-offline-decline-liability

331st: MOVED unknown -> no (B). CLAIM: the vendor PUBLICLY DOCUMENTS who bears the loss when a store-and-forward transaction declines after connectivity returns, and states any offline cap - publication-shaped, the same shape as reliability-offline-feature-matrix, which landed `no`/B in the 327th on the same four censuses. The claim applies: Chowly runs a card-present path of its own (Koala iOS Kiosk + paired Square reader, 'any payments your guests make on a kiosk will appear in your dashboard', Koala-iOS-Kiosk-App-Deployment-Verifying-Square-Payment-with-Koala). BOUND - four censuses, each 100% of its publisher's own manifest, all re-grepped per cell in the 331st: (a) 583 chowly.help articles (Salesforce Knowledge REST, .cache/q324/chowly/ch/arts); (b) 958 chowly.app Restaurant Control Center sources (complete /asset-manifest.json map set, .cache/q325/chowly/src); (c) 910 cms.koala.io sources (closed manifest, .cache/q326/chowly/cmssrc); (d) all 167 pages of the rebuilt chowly.com sitemap incl. the 2026-01-13 Online Terms for Restaurants, diner terms, both privacy policies and the CCPA notice (.cache/q327/chowly/sitetxt). KNOWN-POSITIVE CONTROL: /\btoast\b/i = 48/583, 114/958, 0/910, 113/167 and /\bwebhooks?\b/i = 14/583, so the tokenised regexes fire. CONTROLS: /store[- ]and[- ]forward|\bSAF\b|deferred authori[sz]ation|offline (payment|transaction|card|mode)/i = 0/583, 1/958, 0/910, 0/167 (the RCC hit is CRA serviceWorker.js boilerplate 'App is running in offline mode' - POISON); /offline (limit|cap)|per[- ]transaction limit/i = 0 in all four; /\boffline\b/i = 1/583 (an Olo vendor going offline), 3/958 (browser online/offline events), 0/910, 6/167 (marketing 'offline' - POISON). /\bchargebacks?\b|\bdisputes?\b/i DOES hit (5/583, 17/167): Toast-Pay-Chargebacks-on-Chowly-Online-Ordering, Square-Payment-Disputes-on-COO, a Stripe support-details field and Chowly's dispute-management product - all card-not-present online-ordering or marketplace disputes, none an offline-authorised decline. The 2026-01-13 restaurant Terms (48,804 chars) have 0 hits for chargeback, payment processor, Stripe, offline or decline; the diner terms say only 'All payments will be processed by the Merchants' payment processor'. The Koala iOS Kiosk Feature Set, 11 kiosk release notes (v1.5.0-v1.14.0) and the In-store Operations article ('Ensure the devices have a reliable internet connection') say nothing of offline acceptance or its risk. WEAKEST PART: the kiosk's payment engine is Square's; Square documents its own offline rules, but that is Square's publication, not Chowly's. Retrieved 2026-09-18. https://chowly.com/terms-and-conditions/ · retrieved 2026-09-18 adversarially verified

Multiple terminals continue to share a single check/table state over the local network while the internet is down (LAN-only degraded operation, not per-terminal islands). differentiator

reliability-lan-degraded-multi-terminal

The premise of no terminals and no LAN component is falsified: the Koala iOS Kiosk deployment articles describe multiple in-store iPads on a store network, including power-over-ethernet adapters, adapter whitelisting and per-port power budgets, so a multi-device on-premise deployment does exist. What is missing is any statement of what happens when that network degrades — no peer election, no primary or secondary role, no local queueing. A device-behaviour-on-network-loss article would settle it. || 331st: 331st: per-cell re-grep: /\bLAN\b|same (wifi|network)|local network/i = 0/583, 0/958, 0/910, 0/167; /internet (is )?(down|outage|goes down)|loses? (internet|connection|connectivity)|no internet|without internet/i = 0/583, 0/910, 0/167 and 2/958 (a chat widget toast and CRA serviceWorker - POISON). The Koala iOS Kiosk Feature Set enumerates no check or table object shared between devices (dine-in is only a 'Table Tents' fulfillment choice); each kiosk pairs its own Square reader. Chowly has no multi-terminal check state for the claim to act on: held as not-applicable rather than `no`. Retrieved 2026-09-18. adversarially verified

The vendor documents a local/on-premise transaction engine or edge server (not purely cloud-hosted request/response) for the ordering path. differentiator

reliability-local-transaction-engine

331st: MOVED unknown -> no (B). CLAIM: the vendor DOCUMENTS a local/on-premise transaction engine or edge server for the ordering path - publication-shaped, the 327th rule. BOUND - four censuses, each 100% of its publisher's own manifest, all re-grepped per cell in the 331st: (a) 583 chowly.help articles (Salesforce Knowledge REST, .cache/q324/chowly/ch/arts); (b) 958 chowly.app Restaurant Control Center sources (complete /asset-manifest.json map set, .cache/q325/chowly/src); (c) 910 cms.koala.io sources (closed manifest, .cache/q326/chowly/cmssrc); (d) all 167 pages of the rebuilt chowly.com sitemap incl. the 2026-01-13 Online Terms for Restaurants, diner terms, both privacy policies and the CCPA notice (.cache/q327/chowly/sitetxt). KNOWN-POSITIVE CONTROL: /\btoast\b/i = 48/583, 114/958, 0/910, 113/167 and /\bwebhooks?\b/i = 14/583, so the tokenised regexes fire. CONTROLS: /\blocal (server|network|queue|database|db|cache|storage|mode)\b|\bedge (server|device|computing)\b|\bon[- ]site server\b|\bBOH server\b/i = 2/583, 0/958, 0/910, 0/167 - both KB hits are POISON: Aloha-Restarting-ATO tells the operator to log in to Configuration Center 'on the Aloha BOH server' (NCR's server, not Chowly's), and Release-Notes-01-07-2025 moved COO cart data 'from local storage to session storage' (browser storage). /\bon[- ]prem(ise|ises)?\b/i = 6/583 and 3/167, all POISON: Koala's 'on-premise ordering flow' is a DINE-IN handoff mode (Koala-Olo-Users-Only-On-Premise-Ordering; 'Table Number field ... in the on-premise ordering flow'), and the site hits are blog prose ('The on-premise server era is over'). /\bqueue(d|s)?\b within 80 chars of offline|outage|internet|connection|reconnect/ = 0/583, 0/958, 1/910 (a browser task-queue comment in a bundled polyfill), 0/167. The only on-premise Chowly software the corpus names is an integration adapter: /\bchowly agent\b/i = 1/583, the single sentence 'If we installed a Chowly App or Chowly Agent on your POS for the integration, that may need to be reinstalled' in an article that treats every order failure as remote; and the Clover 'Chowly App' is documented only as a ticket-printing/toggle app now labelled 'Legacy: Using the Chowly App' (Clover-Sync). Neither is described as capturing, persisting or queueing orders. WEAKEST PART: that adapter does sit on the POS in the ordering path; a reader who counts an integration agent as an 'edge server' could argue partial - but the vendor documents no processing role for it. Retrieved 2026-09-18. https://chowly.help/s/article/Order-Failures-Causes-and-Next-Steps · retrieved 2026-09-18 adversarially verified

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

reliability-offline-kds-printing

The Chowly Printer is a cloud-fed device: its connection options are a Wi-Fi network or an Ethernet cable, it signals a red light while searching for its internet source, and the only remedy the vendor documents for a connectivity problem is operator troubleshooting or a call to Chowly Support. No local spool, queue or degraded-mode print path appears anywhere in the corpus, and Chowly’s support-routing article assigns printer and KDS routing to the operator’s POS support desk. Kitchen output therefore stops when the site loses connectivity. (chowly.help serves an inert SPA shell; body is the Aura mirror.) https://chowly.help/s/article/Common-Printer-Support · retrieved 2026-09-06 adversarially verified

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

reliability-printer-fallback

When a Chowly printer goes offline the documented remedy is human: support walks the operator through resetting the hardware to bring it back. kb:Common-Printer-Support reinforces this with an operator troubleshooting flowchart — power, connection, jams, paper, error light, hard reset — and an Aboyeur screen showing the last order sent to the printer, with no re-route, no secondary device and no backup destination anywhere in the failure handling. Chowly’s support-routing article separately assigns printer and KDS routing to POS support. https://chowly.help/s/article/Order-Failures-Causes-and-Next-Steps · retrieved 2026-09-06 adversarially verified

The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).

reliability-sync-conflict-handling

Quote: "Toast, Square and POS API: POS Menu Imports Overwrite 86ing in the RCC and Chowly Support: Importing menus from these systems will override any 86ed items in the Restaurant Control Center (RCC). Recommendation: Use the POS system itself to manage 86ed items. Aloha and Revel: Menu Imports Don't Overwrite 86ing: 86ing events in the RCC remain unaffected by menu imports from the POS." Chowly does document a conflict-resolution rule for the one case where two writers can edit the same state (an item's availability edited in the RCC and in the POS): per POS family it is either POS-import-wins (Toast, Square, POS API - the RCC edit is overwritten) or independent-with-divergence (Aloha, Revel - 'menus may not always be in sync if the RCC is used first'), and Square-Mark-Items-as-Sold-Out repeats the rule ('syncing the menu overwrite manually 86'd items, making them available again'). The 15-minute publish lock ('86ing items and publishing menu changes can only be done in 15 minute increments ... menus on third party platforms will not be updated') is a throttle whose failure mode is a dropped update. SHORTFALL: the claim asks about two devices editing during a network partition; Chowly is a cloud service with no device-local state, so the documented behavior is source-of-truth precedence between the POS feed and the RCC, not a last-write-wins/merge/prompt policy for partitioned devices. https://chowly.help/s/article/Suspending-Items-Restaurant-Control-Center · retrieved 2026-09-03 adversarially verified

The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).

reliability-offline-feature-matrix

327th: MOVED unknown -> no (B). This is a claim about PUBLICATION, which a census can settle. BOUND: 583 chowly.help articles (100% of the Salesforce Knowledge manifest), 958 chowly.app RCC mapped sources, 910 cms.koala.io sources, and all 167 pages of the rebuilt chowly.com sitemap fetched today (none a soft-404). CONTROL /\boffline\b/i = 1/583, 3/958, 0/910, 6/167, and not one is a feature-availability statement. The single KB hit is 'Koala Olo Menu Partners: Olo Location Webhooks' (a vendor location going offline in Olo). The three RCC hits are the browser online/offline events in serviceWorker.js and a chat widget's connection state. All six site hits are SEO blog prose about offline marketing and offline word-of-mouth (POISON: 'offline' in the marketing sense dominates the rebuilt site). /store.and.forward/i = 0 across all four. The claim applies - Chowly ships in-store devices (the Chowly Printer, the Koala iOS Kiosk and mPOS fleet) whose behaviour during an outage is exactly what an operator would need - and the vendor publishes a per-component status page with 46 components and a four-level incident SLA, so it is not a vendor that publishes no reliability material. It publishes no list of what stops working offline. WEAKEST PART: the RCC is a back-office/middleware app, so this bound is about what Chowly publishes, not about a POS terminal's offline engine. Retrieved 2026-09-18. https://chowly.com/terms-and-conditions/ · retrieved 2026-09-18 adversarially verified

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

reliability-public-status-page

Chowly publishes a public status page at chowly.statuspage.io. It returns 200, its API at /api/v2/summary.json names the page "Chowly" with indicator "none" and the description "All Systems Operational", and it enumerates 46 components in nine groups: Third Party Ordering Solutions, Point Of Sale, SDK API, V2 TOOS Partner API, Chowly User Tools, Chowly Printers, Customer Care, Chowly Features and Chowly Digital Marketing. The prior verdict checked only the vanity host status.chowly.com and inferred absence from its NXDOMAIN, which is not a sound test for a vendor hosted on a status-page SaaS. Grade B: a first-party vendor-operated surface. https://chowly.statuspage.io/ · retrieved 2026-09-06 adversarially verified

A contractual uptime SLA with a stated percentage AND a service credit remedy is published or available in the standard agreement. differentiator

reliability-contractual-uptime-sla

Confirmed: no service level, uptime commitment, or credit remedy in the Terms, and the liability cap is verbatim "the lesser of (a) $500 and (b) the fees that Restaurant paid to Chowly in the three months preceding". This is the single most damaging verified fact in the dossier and it is correctly stated. https://chowly.com/terms-and-conditions/ · retrieved 2026-08-01 adversarially verified

The vendor publishes written post-incident reports or root-cause summaries for major outages.

reliability-incident-postmortems

A written post-incident commitment is documented: 'What Happens After an Incident is Resolved? The Koala team always runs a post mortem for incidents that impact our customer base. We will identify any code or process changes that need to go into affect, and will provide customers with a post-mortem report within 2 weeks of incident resolution.' The same article publishes a four-level failure classification with response and target resolution times (Level 1 critical failure: 30-minute response, 4-hour target; Level 2 major: 1 hour / 1 day; Level 3 minor: 1 business day / next release; Level 4 misuse: 1 business day / next release), Datadog monitoring with OpsGenie paging, and 9am-5pm Mon-Fri business hours with on-call outside them. Shortfalls: the reports go to affected customers, not to the public. Chowly's own status page, https://chowly.statuspage.io (50 incidents in the feed, 2021 through 2026-08-07), closes every one with a bare line - 'This incident has been resolved.' - and carries no root-cause summary for any of them, including the major 2026-08-07 'Service Disruption Impacting Order Flow and COO Functionality'. The commitment is also Koala-side; nothing extends it to Chowly's marketplace-integration incidents. https://chowly.help/s/article/Koala-Incident-Response-Protocol · retrieved 2026-08-08

24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.

reliability-247-live-support

Shortfall named: live human support exists but is not round-the-clock. Chowly's own contact page publishes phone "(888) 628-0823 ext. 2" and text "(866) 674-0469" with the hours "Daily, 9 AM - 12 AM CST" - a 15-hour daily window, seven days a week, leaving roughly 12 AM-9 AM CST uncovered by a published live channel. Ticket submission via chowly.help/s/contactsupport is always available but is asynchronous, and no response-time commitment is published for it; chat availability is not stated. Note the conflict: a 2023 Chowly blog post is titled "Introducing 24/7 Support", but its body was not retrievable and the current contact page contradicts a 24/7 live reading. Consistent with the record's separate finding that the Terms carry no uptime or service-level commitment. https://chowly.com/company/contact/ · retrieved 2026-08-02 adversarially verified

The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator

reliability-onsite-install

Both of Chowly’s in-store hardware paths are documented as customer-performed with remote support only. On the kiosk path the brand buys the iPads, enrols them in Apple Business Manager and a mobile device management system itself, and buys enclosures from a third-party hardware partner, while the in-store operations article tells the brand to train its own team and run a daily device sweep. On the printer path kb:Common-Printer-Support gives the operator a troubleshooting flowchart and a support phone number. No dispatch, technician visit or dealer network appears anywhere in the corpus. https://chowly.help/s/article/Koala-iOS-Kiosk-App-Deployment-Kiosk-Kickoff-Requirements · retrieved 2026-09-06 adversarially verified

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

reliability-menu-build-service

A one-time per-location setup fee is contractually disclosed and Chowly performs menu mapping between POS and marketplaces. Reviewers report the mapping is a recurring failure point - deleted photos, mismapped modifiers, implementation waits of six months to over a year. https://chowly.com/terms-and-conditions/ · retrieved 2026-08-01

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

reliability-hardware-replacement-sla

327th: MOVED unknown -> no (B). BOUND - four censuses, each 100% of its own publisher manifest: (a) 583 chowly.help articles via the Salesforce Knowledge REST API; (b) 958 first-party sources from chowly.app's complete /asset-manifest.json source-map set (the Restaurant Control Center); (c) 910 cms.koala.io mapped sources; (d) ALL 167 URLs of the rebuilt Next.js chowly.com sitemap, fetched today, none a soft-404 (the 404 shell is 7,758 bytes; every page exceeded 10 KB). CONTROLS, tokenised and case-insensitive: /advance exchange|replacement (?:printer|device|unit|terminal)|next.business.day|\bRMA\b|hardware warranty/i = 1/583, 0/958, 0/910, 0/167, and the single KB hit is inside '86 (Suspend) Items Restaurant Control Center' about replacement of menu data, not a device. /\bRMA\b/i alone = 0 everywhere. EVIDENCE: Chowly does ship first-party hardware (the Chowly Printer, three connectivity SKUs monitored on its status page), so the claim applies, and the vendor DOES publish a support SLA for software - 'Koala: Incident Response Protocol' sets out four failure levels with response and target-resolution times ('A - LEVEL 1 CRITICAL FAILURE... Response time: 30 minutes, Target Resolution: 4 hours'), 'per the standard Koala SLA' - so this is not a vendor that publishes nothing. That published SLA covers platform failures only and names no device, no turnaround and no exchange. The 2026-01-13 Terms and Conditions has no hardware clause and disclaims the opposite: 'Restaurant accepts the Services "as is", with no implied warranty of any kind, including implied warranties of merchantability', with aggregate liability capped at 'the lesser of (a) $500 and (b) the fees that Restaurant paid to Chowly in the three months preceding'. No replacement or advance-exchange programme is included or offered for purchase. Retrieved 2026-09-18. https://chowly.com/terms-and-conditions/ · retrieved 2026-09-18 adversarially verified

Operators can trigger and retrieve their own data backup/restore, or the vendor publishes RPO/RTO figures for data recovery.

reliability-backup-restore

327th: MOVED unknown -> no (B). The 2026-08-08 note was written against a 204-body corpus; this rests on four censuses taken since - 583 chowly.help articles (100% of the Salesforce Knowledge manifest), 958 chowly.app RCC sources (complete /asset-manifest.json map set), 910 cms.koala.io sources, and all 167 pages of the rebuilt chowly.com sitemap (none a soft-404). CONTROLS: /\bRPO\b|\bRTO\b|recovery point objective|recovery time objective|data backup|back up your data/i = 0/583, 0/958, 0/910, 0/167. POISON FOUND AND EXCLUDED: a bare /\bbackup\b/i returns 5 KB files, and every hit is a homonym - 'Creating a Stripe Account for Chowly' six times about a Stripe two-factor BACKUP CODE ('Chowly does not need your backup code nor should it ever be shared with Chowly'), and 'Koala Cross-Sell Configurations: Machine Learning Cross-Sell' twice about ML rules used 'as backup rules' behind manual ones. Neither is data backup. /disaster recovery/i = 0 across all four. No operator-triggerable export/restore exists in the RCC: the 958-source RCC tree has no backup, export-all or restore route, and its only 'restore' tokens are React DOM helpers in the CMS tree. The 2026-01-13 Terms and Conditions publishes no RPO, RTO or recovery commitment; on termination it requires the Restaurant to 'uninstall and destroy all copies of the Software' and says nothing about retrieving data. Retrieved 2026-09-18. https://chowly.com/terms-and-conditions/ · retrieved 2026-09-18 adversarially verified

The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.

reliability-pci-dss-4-attestation

The claim asks whether the vendor PUBLISHES a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent, and the answer is no. This privacy policy is the entirety of Chowly's published security disclosure. Its overview undertakes to tell the reader "The kinds of security measures in place to protect against loss or misuse of your personal information", and the section discharging that undertaking, "How secure is your personal information?", reads in full: "The security of our user data is very important to us. We store your information securely, using industry-standard encryption technology. When you enter sensitive information (such as a credit card number) on our web forms, we encrypt the transmission of that information using secure socket layer technology (SSL)." Transport encryption and nothing else - no AoC, no SAQ, no QSA, no ROC, no P2PE listing, no compliance-page reference. This paragraph is cited as the whole of what Chowly publishes on security, NOT as an enumeration of its certifications; a privacy policy makes no completeness claim about compliance posture. What closes the publication question is the venue census, measured 2026-09-05: chowly.com/trust/, /compliance/, /security-policy/ and /data-processing-addendum/ each returned 404 at exactly 50,608 bytes, byte-identical to the fabricated control /zzz-control-205d/ and to the same control length recorded for /msa/, /sla/, /dpa/, /acceptable-use-policy/, /security/, /legal/ and /terms-of-service/; trust.chowly.com is NXDOMAIN; chowly.com's 167-URL sitemap holds no security, trust, compliance or certification page; and the footer legal index links exactly five documents - Privacy, Terms, CCPA, Diner Privacy and Diner Terms. The P2PE limb is inapplicable rather than unresolved: such a listing attaches to a solution encrypting at a card-reading device and Chowly ships none, card capture in its stack running through Square, Stripe and PCI Proxy. BOUND: this establishes that Chowly publishes no attestation. It does NOT establish that Chowly lacks PCI DSS validation and must not be read that way. https://chowly.com/privacy-policy/ · retrieved 2026-09-05 adversarially verified

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

reliability-mfa-role-based-access

Role-based access is met, but only for Chowly's Koala online-ordering Brand CMS (acquired 2023; now Chowly's branded ordering layer), not for the Restaurant Control Center. The served main.3855e1a8.chunk.js defines two groups, ADMIN:"group:organization_admin",USER:"group:organization_user", plus separate permission scopes (MANAGE_PERMISSIONS:"permissions:manage",PUBLISH_PAGES:"pages:publish", device_configurations:manage), each with a label shown to admins (label:"Manage Users"; "Allows user to publish or unpublish pages."). The user-list chunks check groupScopes.includes("group:organization_admin") before showing admin controls. Shortfall, MFA: the Koala SDK constants in 11.5db6a73c.chunk.js set staff sign-in to a single password grant, t.USER={GRANT_TYPE:"password",SCOPES:["group:organization_admin"]}. The only other grant is a Paytronix guest loyalty login. The sign-in form asks only for a username and password ("Sign in below to access the Koala CMS."), and the only protection on it is rate limiting ("Too many attempts, try again later"). None of mfa/otp/totp/2fa/two-factor/multi-factor/authenticator/sso/saml/oidc/okta appear as whole words in any of the 58 chunks listed in asset-manifest.json. That shows MFA is missing from this one client. Chowly has published nothing saying MFA is unavailable, so this cannot support a `no` for the RCC. https://prod-coo-brand-cms.chowly.io/static/js/main.3855e1a8.chunk.js · retrieved 2026-09-15 adversarially verified

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

reliability-self-serve-training

A public knowledge base exists at chowly.help (linked from site navigation as Support) but it did not render for automated fetch, so depth is unverified. No terminal training mode exists because there is no terminal. https://chowly.com/ · retrieved 2026-08-01

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

reliability-failover-terminal-role

"No terminals" is false — the Koala kiosk fleet is a set of in-store devices, added and removed per location through the content management system. But no document assigns any of them a failover, primary or backup role, and none describes what a store does when one kiosk is down beyond restarting it and re-pairing its reader. A kiosk or printer article describing a designated standby device or an automatic role takeover would settle it. || 331st: 331st: per-cell re-grep: /\bfail[- ]?over\b|\bbackup (device|kiosk|terminal|printer)\b|\bprimary (device|kiosk|terminal)\b|\bmaster (device|terminal|kiosk)\b/i = 0/583, 0/958, 0/910, 0/167. The 50 Koala kiosk articles in the census (deployment, configuration, 11 release notes) describe independent iPads, each in ASAM with its own reader, and no master/server role for any device to take over. No module = held, not `no`. Retrieved 2026-09-18. || 332nd: MERGE HOLD (proposed no/B, held unknown): Owner ruling Q5 covers a cloud POS with no in-store master terminal; Chowly is middleware whose only in-store devices are kiosks, and a middleware product with no terminal module at all is held unknown, not no. PROPOSAL AS WRITTEN: 332nd: MOVED unknown -> no (B) under OWNER RULING 2026-09-18 (Q5): a cloud-hosted product with no in-store master/primary terminal role scores no on reliability-failover-terminal-role rather than unknown (landed for spoton, slice, gotab). The architecture is established on this record: (1) the only in-store device fleet Chowly ships is the Koala iOS Kiosk, a set of independent iPads each running in Autonomous Single App Mode with its own paired Square reader, provisioned per location from the cloud CMS (cms.koala.io routes /locations/:id/kiosks/:kioskId; chowly.help Koala-iOS-Kiosk-App-Deployment-Adding-a-New-Kiosk-Location, -Pairing-the-the-Square-Reader-App, Koala-IOS-Kiosk-Configurations-Enabling-Disabling-Autonomous-Single-App-Mode-ASAM); the In-store Operations article's instruction is 'Ensure the devices have a reliable internet connection', and recovery from a failed device is restart/re-pair of that device alone; (2) there is no local server for any device to take over from - reliability-local-transaction-engine LANDED no/B on this record in the 331st (no on-premise/edge transaction engine documented; the only on-POS software is an integration adapter, the 'Chowly Agent'). BOUND - four censuses on disk, each 100% of its publisher's own manifest, re-verified CURRENT by the 332nd today: (a) chowly.help Salesforce Knowledge, 583/583 articles (.cache/q324/chowly/ch/arts); the listing https://chowly.help/services/data/v59.0/support/knowledgeArticles?pageSize=100 was re-paged 2026-09-18 (6 pages) and still returns 583 ids, ZERO not already held, newest lastPublishedDate 2026-06-16, so the census has not gone stale; (b) the Restaurant Control Center chowly.app, 958 sources from the complete /asset-manifest.json source-map set (.cache/q325/chowly/src; today's manifest still names main.54b02cd0.js, the censused build); (c) cms.koala.io Koala Brand CMS, 910 mapped sources (.cache/q326/chowly/cmssrc; today's manifest still names main.12caeb2d.chunk.js, the censused build); (d) all 167 chowly.com sitemap pages (.cache/q327/chowly/sitetxt). KNOWN-POSITIVE CONTROLS (tokenised, word-boundary, case-insensitive; KB/RCC/Koala/site docs hit): /\btoast\b/ 48/114/0/113, /\bmenus?\b/ 273/110/35/125 - the regexes fire. Script: .cache/q332/chowly/a/ctl.mjs, output ctl-out.json. CELL CONTROLS: /fail[- ]?over|(primary|master|backup|standby) (device|kiosk|terminal|ipad|server|station)s?/ = 0/583, 0/958, 0/910, 0/167. WEAKEST PART: Q5 was worded for a cloud POS; Chowly is ordering middleware whose in-store devices are self-service kiosks, not POS terminals. If the merge reads Q5 as POS-only, hold. Retrieved 2026-09-18. adversarially verified

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

reliability-cellular-backup

327th: MOVED unknown -> partial (B). The vendor's own device article, in the 583-article census, documents the cellular option first-party and also shows it is not a failover. 'Chowly Printer Guide': 'Your Chowly Printer comes pre-configured to connect to an internet source' with three lettered alternatives - 'A. WIFI CONNECTION', 'B. ETHERNET CABLE', 'C. FOR LTE PRINTER CLIENTS: Majority of Chowly's Enterprise size restaurant groups use LTE printers. These printers receive orders through a cellular signal, similar to a mobile phone. If you experience frequent drops in the cellular signal on your LTE printer, we recommend moving the printer to an area within the restaurant that has the strongest connection.' chowly.statuspage.io/api/v2/summary.json (46 components, re-fetched today) monitors '4G LTE Printers', '2G Wifi Printers' and 'Ethernet Printers' as three SEPARATE components, i.e. three distinct device populations. WHY PARTIAL: the claim's substance - first-party documented cellular connectivity for the in-store device - is satisfied, and the LTE unit is the majority deployment for enterprise groups. The claim's other half is not: LTE is that printer's PRIMARY and only path, chosen per client at provisioning, and no document describes any automatic switch to cellular when the WAN link drops. The remedy the vendor publishes for a cellular drop is to physically move the printer. Retrieved 2026-09-18. https://chowly.help/s/article/Chowly-Printer-Guide · retrieved 2026-09-18 adversarially verified

Vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core POS software tier. differentiator

commercial-month-to-month-contract

Confirmed verbatim in the Terms. Genuinely unusual for this category and correctly scored. https://chowly.com/terms-and-conditions/ · retrieved 2026-08-01 adversarially verified

Vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. differentiator

commercial-no-early-termination-fee

No ETF or liquidated-damages clause appears in the published Terms - but that is silence rather than an affirmative waiver, and the annual plan's 60-day pre-renewal notice functions as a soft trap. Reviewers report being billed after cancelling: "Does not refund even when you follow their 30 day." https://chowly.com/terms-and-conditions/ · retrieved 2026-08-01

The auto-renewal term and the required cancellation notice window (e.g. 30/60/90 days) are stated in publicly accessible contract terms rather than only in a signed quote.

commercial-autorenew-terms-published

Renewal cadence and notice windows are publicly stated: monthly auto-renew with 30 days' written notice; annual auto-renew for successive one-year periods with notice at least 60 days before term end. Also published: 30-day cure for material breach, 10 business days for non-payment, 1.5% monthly interest on invoices 30+ days late. https://chowly.com/terms-and-conditions/ · retrieved 2026-08-01

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

commercial-processing-not-bundled

Chowly imposes no in-house acquiring on POS-native or delivery-marketplace orders, but its own ordering channels are processor-locked: 'If your Chowly subscription includes Google Direct Order and/or Chowly Online Ordering, you will need to create a Stripe account. Chowly has partnered with Stripe to provide payment processing services.' The Terms bill this channel to Chowly's payment partner at $0.30 + 2.9% per order. Mandatory Stripe on the direct-order channel is the named bundling shortfall, so partial not yes. https://chowly.help/s/article/creating-a-stripe-account-for-chowly · retrieved 2026-08-06

Vendor publishes an interchange-plus (cost-plus) processing rate option with the markup stated as a specific bps + per-transaction figure, rather than only blended/flat card-present rates. differentiator

commercial-interchange-plus-published

Not an acquirer; publishes no card processing rate of any structure. https://chowly.com/solutions/branded-online-ordering/ · retrieved 2026-08-01

The processing agreement caps or prohibits unilateral vendor-initiated rate increases outside of pass-through interchange/network changes, or grants penalty-free exit on any increase. differentiator

commercial-rate-increase-clause

Terms sec.6(f), verbatim: "Fee Increases. Chowly may change fees by providing 30 days' written notice prior to the end of a monthly invoicing period." That is an unrestricted unilateral right - no percentage or index cap, no carve-out limiting increases to pass-through costs, and no clause granting exit on an increase. Termination is governed separately and unconditionally by sec.4(b) (monthly plan, 30 days' notice) and sec.4(c) (annual plan, 60 days before the end of the Initial or Renewal Term) and is nowhere linked to a price change, so an annual-plan operator hit mid-term has no increase-triggered exit. Sec.11 additionally lets Chowly "amend this agreement by posting a revised version online" with continued use as acceptance. No interchange pass-through arises on Chowly's own fees: Chowly is not the card processor - Stripe takes first-party/Google Direct Order payments and Square takes Koala kiosk payments, in each case on the merchant's own processor account. https://chowly.com/terms-and-conditions/ · retrieved 2026-08-08

Per-location and per-additional-terminal software pricing is published as specific dollar figures on the vendor's public site (not 'contact sales' only).

commercial-pricing-published

No pricing page - /pricing/ returns 404 and is absent from the sitemap. The only public dollar figures are in the Terms: a $35/month per-location minimum, an unquantified one-time per-location setup fee, and Google Ordering at $0.30/order + 2.9% + up to 10% of Base Order Value. Actual plan pricing is quote-only; SoftwareAdvice lists "Custom quote". https://chowly.com/terms-and-conditions/ · retrieved 2026-08-01

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

commercial-module-unbundling

Terms sec.2 is written as an elective menu: the Restaurant "may elect to utilize first party ordering software (web or mobile)" (b), "may elect to utilize a courier service" (d), "may elect to utilize digital marketing and advertising (including email marketing and paid ads)" (e), and "may elect to receive, as part of the Services, dynamic pricing, revenue reconciliation and recovery, Google business profile management, or customer surveys" (f); Google Ordering carries a named independent opt-out - "Restaurant may opt out of the Google Ordering by emailing Chowly" (c). Named shortfalls: (1) sec.2(g) hard-bundles two modules - "Restaurants that elect to use Chowly's proprietary platform are required to use Chowly's first party ordering software and its website builder and management services"; (2) no a la carte price is published anywhere - sec.6(a) puts all fees in a per-location Onboarding Form and imposes a "$35 per month minimum fee per location", a floor that dropping modules cannot go below, and chowly.com/pricing does not exist; (3) apart from the Google Ordering email opt-out, no per-module cancellation mechanism is documented - sec.4(b)/(c) terminate the whole agreement on 30- or 60-day notice, and chowly.help routes cancellation to a support form at /s/cancellation-request. Chowly sells no POS, so there is no base POS subscription to reprice; the tested unit is the per-location platform fee. https://chowly.com/terms-and-conditions/ · retrieved 2026-08-08

All required terminals, KDS screens, and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental.

commercial-hardware-purchase-outright

327th: MOVED unknown -> partial (B). NEW EVIDENCE. The 583-article census holds 'Koala iOS Kiosk App Deployment: Purchasing Devices and Enrolling in ABM & MDM': 'Koala's Kiosk and mPOS applications are distributed as free Custom Applications on ABM. In order to use the Koala Kiosk or mPOS applications, you will need to purchase Apple devices and enroll them in ABM (Apple Business Manager)... Your organization will need to acquire licenses via ABM in the Custom App Section.' So for the entire in-store device fleet the operator buys standard Apple hardware outright, direct from Apple at Apple's published price, and the Koala software licence on it is free; there is no Chowly-mediated lease, rental or hardware contract of any kind. Tokenised control across all four censuses - 583 KB articles, 958 chowly.app RCC mapped sources, 910 cms.koala.io sources, 167 chowly.com pages - /\blease\b|\brental\b|\brent\b|monthly hardware/i returns 0/583, 0/958, 0/910 and 5/167, and all five site hits are SEO blog prose about other operators' costs, not a Chowly hardware offer. The 2026-01-13 Terms and Conditions (https://chowly.com/terms-and-conditions/) has no hardware section at all: its only fee terms are 'a one-time set up fee per location, and a monthly fee per location', '$35 per month minimum fee per location', and Google Ordering per-order fees. WHY PARTIAL, NOT YES: the claim requires a PUBLISHED PRICE for all required devices, and the Chowly Printer - a first-party thermal unit Chowly ships and monitors on its own status page in three connectivity SKUs - has no published price anywhere. 'Chowly Printer Guide' and 'Common Printer Support' describe contents, paper and reset only; a price/cost/fee proximity control over the 583 articles returns 2 files and 4 hits, all of them the word 'Feed' button in the hard-reset instructions (POISON: /fee/ matches 'Feed'). Retrieved 2026-09-18. https://chowly.help/s/article/Koala-iOS-Kiosk-App-Deployment-Purchasing-Devices-and-Enrolling-in-ABM-MDM · retrieved 2026-09-18 adversarially verified

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

commercial-hardware-not-locked

Requires zero vendor hardware and is explicitly hardware-agnostic: runs on top of Toast, Square, SpotOn, Clover, Revel, Lightspeed and Aloha and their existing peripherals. "Keep Toast POS" is marketed positioning. https://chowly.com/pos/ · retrieved 2026-08-01

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

commercial-implementation-fee-published

The Terms confirm "a one-time set up fee per location" exists but never state the amount, and it is not $0. Reviewers specifically flag setup fees discovered after signature. https://chowly.com/terms-and-conditions/ · retrieved 2026-08-01

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

commercial-data-export-self-serve

A self-serve download exists and is documented, but not for the full scope the claim names. Navigating-the-Restaurant-Control-Center: "The Filters, Expand, and Three Dots icons function more-or-less the same in every tile ... The Three Dots icon shows a drop-down list of other actions you can do with your data: Sort, Download, Refresh data, Copy to clipboard, and Format." Applied to the Orders reporting page that reaches transaction level - its Order Detail tile lists one row per order with LOCATION NAME, CUSTOMER NAME, SALES DATE, SUBTOTAL, TIP, SALES TAX, TOTAL, PLATFORM, ERROR OR CANCELLATION REASON, SERVICE TYPE and ORDER STATUS - and the Smart Pricing page adds UPCHARGE, BASE PRICE, ID, MARKUP and TIMESTAMP. NAMED SHORTFALLS. (1) Getting an account is not self-serve: "To sign up for access to Chowly's Restaurant Control Center, you must reach out to our Support Team" (Creating-a-Restaurant-Control-Center-Account), so the claim's "without contacting support" limb fails at the first step. (2) No line-item detail is downloadable per order - Product Mix reports items aggregated over the selected location set, not the lines of an individual order. (3) No labor data exists in the product at all. (4) No file format is stated anywhere; "CSV" appears in the 204-article corpus only in an AWS CNAME validation article and an Aloha hours spreadsheet, so the download's format is undocumented. (5) There is no documented API alternative - Chowly's five API surfaces are partner-facing and unpublished. read via the chowly.help Salesforce Aura record endpoint (getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c); the HTML at this URL is the site's CSS-error SPA shell. https://chowly.help/s/article/Navigating-the-Restaurant-Control-Center · retrieved 2026-08-08

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

commercial-export-customer-and-loyalty

One of the three data sets the claim names is machine-readable to the operator; the other two are not Chowly's to hold. WHAT IS EXPORTABLE: the Orders reporting page's Order Detail tile carries "CUSTOMER NAME: Indicates the name of the customer that placed the order" alongside sales date, subtotal, tip, tax, total, platform and service type, and the Delivery Buydown page's COO Delivery Orders table repeats CUSTOMER NAME with per-order fee splits; every RCC tile exposes a Download action ("The Three Dots icon shows a drop-down list of other actions you can do with your data: Sort, Download, Refresh data, Copy to clipboard, and Format" - Navigating-the-Restaurant-Control-Center). NAMED SHORTFALLS. (1) That is order-level guest data, not a customer-record set - no email, phone, address or profile field appears in any documented tile, and no customer object or list exists anywhere in the RCC's documented surface. (2) Loyalty balances and point ledgers are not Chowly's: Koala-Punchh-Loyalty-Partners-Advanced-Loyalty-Dashboard describes a guest-facing dashboard (points available, earning status, rewards, points history, barcode earn) for brands running Punchh or Spendgo and routes configuration to a Koala Account Manager, so the ledger sits with the loyalty vendor and no operator-side extract is documented on either side. (3) Gift-card liability has no representation at all - Koala-Checkout-Configurations-Olo-Users-Only-Gift-Cards-Support covers accepting a gift card at checkout via Olo, not balances or liability. Chowly's marketing asserts ownership rather than portability (chowly.com/solutions/loyalty-program/: "This is YOUR data - not the delivery apps'"; "Who owns the loyalty customer data? You do."), which is grade D and not an export mechanism. read via the chowly.help Salesforce Aura record endpoint (getArticleVersionId then RecordUiController.getRecordWithFields on Knowledge__kav.Content__c); the HTML at this URL is the site's CSS-error SPA shell. https://chowly.help/s/article/Orders-Reporting-Page-on-the-Restaurant-Control-Center · retrieved 2026-08-08

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

commercial-post-termination-export-window

Confirmed verbatim: "Restaurant must uninstall and destroy all copies of the Software and discontinue use of the Services", with no retrieval right, window, or format granted. Affirmative asymmetry, not merely silence, so "no" is justified here. https://chowly.com/terms-and-conditions/ · retrieved 2026-08-01 adversarially verified

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

commercial-data-ownership-clause

The Terms assert Chowly's IP ownership of the Software and Services, state Chowly collects End User Order Data (name, address, phone, email, items, preferences), and prohibit the restaurant from reidentifying End User personal information. No clause states the merchant owns its transaction or guest data, and no constraint on Chowly's use of it is published - directly at odds with the marketing line "This is YOUR data". https://chowly.com/terms-and-conditions/ · retrieved 2026-08-01

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

commercial-source-available-selfhost

Proprietary closed-source SaaS; Terms require destroying all copies of the Software at termination. https://chowly.com/terms-and-conditions/ · retrieved 2026-08-01

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

commercial-pci-p2pe-tokenization

Card acceptance is documented as fully delegated to the merchant's own processor account. Online: "If your Chowly subscription includes Google Direct Order and/or Chowly Online Ordering, you will need to create a Stripe account. Chowly has partnered with Stripe to provide payment processing services", and the same article states "Chowly will never have access to any of the information described above because Chowly will not have access to your Stripe account." Card-present: on the Koala kiosk the card is dipped/tapped on a paired Square Reader (Koala-iOS-Kiosk-App-Deployment-Pairing-the-the-Square-Reader-App) and funds settle into the brand's own Square account, which the brand authorises via OAuth in the Koala CMS - "any payments your guests make on a kiosk will appear in your dashboard, and be debited into your bank account" (Koala-iOS-Kiosk-App-Deployment-Verifying-Square-Payment-with-Koala); refunds are issued inside Square, not inside Koala. Web checkout runs on Square's payment form with Google Pay/Apple Pay wallet buttons (Koala-Square-Menu-Partners-Adding-Digital-Wallets). Named shortfall: Chowly documents none of what the claim requires about PCI itself - "PCI", "SAQ", "P2PE" and "tokeniz" return zero hits across all 114 published chowly.help articles, and the only security statement Chowly publishes (privacy policy sec.4) says merely "industry-standard encryption technology" and SSL on web forms. The scope reduction is architectural and inferable from the delegation, but it is neither asserted nor mapped to an SAQ type by the vendor. https://chowly.help/s/article/creating-a-stripe-account-for-chowly · retrieved 2026-08-08

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

commercial-pci-dss-4-controls

The claim scores DOCUMENTATION of the PCI DSS v4.0.1 future-dated controls in force since 31 Mar 2025 - MFA for all access to the cardholder data environment including POS and back-office logins, and payment-page script integrity monitoring per Req 6.4.3/11.6.1. Chowly documents neither, anywhere it publishes. This privacy policy is its only public security disclosure: the overview undertakes to describe "The kinds of security measures in place to protect against loss or misuse of your personal information", and the section discharging it, "How secure is your personal information?", is three sentences - "The security of our user data is very important to us. We store your information securely, using industry-standard encryption technology. When you enter sensitive information (such as a credit card number) on our web forms, we encrypt the transmission of that information using secure socket layer technology (SSL)." SSL in transit is the whole documented control set: no MFA statement, no cardholder-data-environment scope statement, no script-integrity or payment-page tamper-monitoring statement. Venue absence measured, not assumed: on 2026-09-05 chowly.com/trust/, /compliance/, /security-policy/ and /data-processing-addendum/ all returned 404 at exactly 50,608 bytes, identical to the fabricated control /zzz-control-205d/; trust.chowly.com is NXDOMAIN; the 167-URL sitemap carries no compliance page; and the footer legal index is five documents - Privacy, Terms, CCPA, Diner Privacy, Diner Terms. Corroborating, from other documents and therefore not quoted here: the RCC sign-in is documented end to end as email and password with no second factor (Logging-Into-the-Restaurant-Control-Center), and card capture in Chowly's stack runs through Square, Stripe and PCI Proxy rather than through Chowly. BOUND: much of the cardholder data environment is likely those processors', so this is a finding about what Chowly documents, not a finding that the controls are absent from the payment chain. https://chowly.com/privacy-policy/ · retrieved 2026-09-05 adversarially verified

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

commercial-soc2-attestation

The claim asks whether the vendor STATES it holds a current SOC 2 Type II or ISO 27001 attestation and will provide the report under NDA via a trust center or on request. Chowly makes no such statement. This Terms and Conditions is a complete restaurant-facing services contract - eleven numbered sections from Definitions through General - and it closes itself: "This agreement constitutes the entire agreement between the parties with respect to its subject matter." Within it there is no audit, attestation, certification, SOC, ISO or report-on-request clause of any kind; the strings SOC, ISO 27, audit and attestation occur zero times in it. Section 7 is a plain mutual NDA - "During the Term and for five years thereafter, neither party shall disclose Confidential Information disclosed to it by the other party" - with no audit-report delivery obligation attached, and section 10 disclaims the rest, the Services being accepted as is "with no implied warranty of any kind, including implied warranties of merchantability, noninfringement of intellectual property rights, course of performance, course of dealing and usage of trade." One qualification, because the entire-agreement clause is not absolute: the opening paragraph provides that "The Onboarding Form governs in the event of any inconsistency or conflict with these terms." A private order form therefore does sit above these terms - but it is not published, and this claim asks what the vendor states, so it cannot supply the missing statement. Venue measured absent on 2026-09-05: chowly.com/trust/, /compliance/, /security-policy/ and /data-processing-addendum/ all returned 404 at exactly 50,608 bytes, byte-identical to the fabricated control /zzz-control-205d/; trust.chowly.com is NXDOMAIN; and this document's own footer links exactly five legal documents - Privacy, Terms, CCPA, Diner Privacy and Diner Terms - which are the whole published legal corpus. BOUND: this establishes that Chowly makes no such statement and offers no trust centre. It does NOT establish that Chowly lacks SOC 2. https://chowly.com/terms-and-conditions/ · retrieved 2026-09-05 adversarially verified

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

commercial-privacy-dsar-tooling

Chowly runs a CCPA request process for consumers - category and specific-piece disclosure, portability twice per 12 months, deletion with transaction and legal carve-outs, 45-day response extendable to 90 - via email to Chowly. No in-app operator DSAR tooling and no published DPA the operator can execute. https://chowly.com/ccpa/ · retrieved 2026-08-01

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

commercial-wcag-kiosk-accessibility

NEW SURFACE (retires the 114-article bound every prior chowly pass used): chowly.help serves its WHOLE knowledge base anonymously at the Salesforce guest knowledge API, https://chowly.help/services/data/v59.0/support/knowledgeArticles?pageSize=100 (6 pages, 583 articles, full bodies via each article's own url, 2.89 MB of stripped text). Prior passes bounded chowly at 114 slugs from /s/sitemap-topicarticle-1.xml; this is 5.1x larger. Census check: 44 of 44 chowly.help /s/article/ URLs already cited in this record are inside it. CLAIM: vendor publishes a VPAT/ACR claiming WCAG 2.1 AA for kiosk + consumer web ordering, including a documented tactile/audio non-visual access mode on kiosks. VERDICT: partial. EVIDENCE for the met half: 'Koala: ADA Compliance' (https://chowly.help/s/article/Koala-ADA-Compliance, modified 2023-10-20) publishes a first-party accessibility AUDIT of the Koala web-ordering app: 'When determining whether a page is accessible there are two main questions... Can I navigate the page using alternative input devices (such as a keyboard) and an alternative output device (such as a screen reader)?'; scan methods 'Lighthouse... For pages that could not be accessed through Lighthouse, an accessibility plugin called WAVE was used' plus 'manual testing was done using Apple's built in screen reader'; per-route results order.brand.com 92, /store 100, /store/checkout 92, /sign-up 98, /login 95, with named defects ('Form inputs are missing labels: Payment info card expiration and zip code... This is an iframe from PCI proxy... Backlogged'). The kiosk non-visual mode IS documented: 'Koala IOS Kiosk Configurations: Enabling Kiosk Accessibility' (https://chowly.help/s/article/Koala-IOS-Kiosk-Configurations-Enabling-Kiosk-Accessibility, modified 2023-11-14) - 'Koala's Kiosk platform offers complete support for visually impaired guests, however to enable Voice Over functionality, your operations team will need to be aware of the steps to take', then Settings > General > Accessibility > VoiceOver and 'tap 3 times anywhere in the screen to activate VoiceOver'. NAMED SHORTFALL: no VPAT and no ACR is published; the words WCAG, VPAT and Section 508 return 0/583 over the full census, so no conformance LEVEL (2.1 AA or any other) is claimed anywhere; the published audit is Lighthouse-score-based rather than a criterion-by-criterion conformance report; and it covers the web-ordering routes only - the kiosk article documents a VoiceOver toggle but no kiosk audit or tactile mode. Grade B (vendor help-centre documentation). Retrieved 2026-09-17. https://chowly.help/s/article/Koala-ADA-Compliance · retrieved 2026-09-17 adversarially verified

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

commercial-dual-pricing-compliant

The trap in this cell is a naming collision and the document resolves it. The one article in Chowly's corpus containing the phrase dual pricing is this one, and its subject is CHANNEL pricing: "Some restaurants choose to make their online menus a little more expensive than their in house menu." "In the Upcharge field, you can add a number that then gets translated into a percentage. For example, 5.0 is a 5% upcharge, 7.5 is a 7.5% upcharge", and "This upcharge is then applied to whatever price you have set for your menu items in your POS system." - "a 5% upcharge will make this item appear as $10.50 to customers ordering online". The variables are location and ordering platform ("Scroll down to the Platform List Table near the bottom of the page, and click the name of whichever platform you would like to add or edit upcharges"), never the card the guest presents. The sentence that invites misreading is the closing note: "Note: Up-charges are not supported for pickup menus on Doordash, as Chowly implemented dual pricing support specifically to meet DoorDash's requirements." - separate pickup and delivery menu prices to satisfy a marketplace policy, not a card-network cash-discount or surcharging program. The claim's limbs fail on what this document positively establishes rather than on silence: the percentage is applied to prices already set in a POS Chowly does not own and is baked into the published menu before authorization, so there is no point at which a BIN or card product could be inspected to exclude debit and prepaid, and Chowly prints no receipt and drives no menu board on which the required fee disclosure could appear. Currency: LastPublishedDate 2026-02-24, one of nine 2026-published articles, so it documents the current product. https://chowly.help/s/article/Upcharge-Settings-on-the-Restaurant-Control-Center · retrieved 2026-09-05 adversarially verified