Chowly

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

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

menu-pricing-fractional-placement differentiator

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). On this claim the widened corpus changes the evidence but not the verdict. Chowly's own menu object model is now documented end to end - Chowly Printer: Menu Management Overview (Dejeuner: item = name, price, tax rate, image, description; modifier group = min/max; modifier = name, price) and the closed propagated-field lists in Toast: Item Settings with Chowly and Clover with Chowly Overview - and none of it carries a section, half, quarter or placement attribute. Against that sits real counter-signal: Koala: Web Ordering Feature Set lists a "Pizza Topping Customization template" under Templates & Styling, and chowly.statuspage.io/api/v2/components.json lists a distinct "Koala" component alongside "Dejeuner" and "Chowly Online Ordering", so the Koala ordering front end is a separate surface whose product detail page is not described by the sync-path field lists. No Koala-* article in the 195 retrieved bodies documents that template's behaviour, and the feature set explicitly says modifiers render "as set in the menu provider" (Olo/Square). A differentiator-weight verdict on placement and per-section pricing semantics needs A/B documentation that does not exist on either surface. Unresolved.

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

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.

menu-pricing-topping-quantity-tiers

2026-08-08 enumeration audit, downgraded from no. Every leg of the enumeration fails the bar on re-reading. Chowly Printer: Menu Management Overview 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 the Printer segment only. Brink with Chowly Overview and Toast: Modifier Settings with Chowly are integration how-tos that assert no completeness. The single explicit first-party non-support sentence, in Square: Setting Modifier Limits (Min / Max Settings), is "Allow multiple quantities of a single modifier is not currently supported on the Chowly Integration" - but that forecloses ordering the same modifier N times, which is precisely the mechanism this claim says a tier must be DISTINCT from, and it is scoped to Square. Nothing retrieved enumerates the modifier pricing fields available on the Toast or Chowly POS API paths, where the record already concedes richer modifier handling. Not established either way. adversarially verified

menu-pricing-size-style-matrix differentiator

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

menu-pricing-included-allowance differentiator

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. adversarially verified

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. adversarially verified

menu-pricing-upsell-prompts differentiator

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

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

menu-pricing-countdown-auto-86 differentiator

Chowly maintains no per-item quantity state: it mirrors the menu out of the operator's POS and holds no stock or counts (the record's inventory scope exclusion rests on exactly this). 86 state travels the other direction — the vendor's own page says '86 it in your POS and it disappears from every delivery app instantly', and the help-centre FAQ slugs (FAQ-How-do-I-86-an-item, Square-Mark-Items-as-Sold-Out) route the action to the POS. A countdown/par count that decrements on sale, auto-86s at zero and auto-restores on schedule would require Chowly-side counts the architecture does not have; propagation of POS-originated 86s is already scored at menu-pricing-86-propagation. Checked 2026-08-04.

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

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

menu-pricing-dual-pricing differentiator

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). Chowly's complete documented price-setting surface is now mapped and every element of it is a channel markup rather than a tender-based price: the RCC upcharge percentage set per location or per ordering platform (FAQ - How do I set upcharges to my menu items), Smart Pricing (named as an RCC reporting page in Sales Reporting Page on the Restaurant Control Center and as a statuspage component, but with a dead help article at /s/article/Smart-Pricing-Overview and a 404 at chowly.com/smart-pricing/), and the marketing-only Pricing Agent at chowly.com/agents/pricing/ whose examples are "+8% surcharge on 3PD only" and "Sunday-only +6% markup across all delivery platforms" - grade D and still channel markup. Product Mix Reporting on the Restaurant Control Center confirms the mechanism by reporting "Min and Max Price: The minimum and maximum price paid for the menu item and/or modifier (differs when varying upcharges are used)". Nothing states whether an item-level cash-versus-card price can be configured, and Chowly is not the acquirer on any path (first-party checkout settles through the restaurant's own Stripe or Square account), so the question may not even arise. Neither direction is documented. Unresolved.

menu-pricing-versioning-effective-dates differentiator

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

menu-pricing-franchise-hierarchy differentiator

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.

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

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

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

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

payments-processor-choice differentiator

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

payments-published-rates differentiator

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

payments-dual-pricing differentiator

The claim requires printing both cash and card totals on the guest check and receipt, and Chowly owns neither surface: it prints nothing (no printer, terminal or KDS product — settled across the reliability and payments cells), has no card-present acceptance of any kind, and the guest check lives in the underlying POS. Card payments in its own ordering channels settle through the operator's existing processor. Whether its online checkout could store a second cash-price per item is separately unresolved (see menu-pricing-dual-pricing), but a native dual-pricing mode that prints dual totals on checks cannot exist in a product with no checks or receipts. Checked 2026-08-04.

payments-surcharge-guardrails differentiator

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.

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

payments-softpos-tap-to-pay differentiator

No card-present acceptance product of any kind.

payments-pay-at-table

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

payments-qr-guest-pay differentiator

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

payments-tip-adjust

Card-present tip flows belong to the underlying POS and processor.

payments-tip-pooling differentiator

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

payments-offline-store-and-forward differentiator

Chowly does not capture card payments.

payments-offline-decline-liability differentiator

No offline card path exists, so no liability position is published.

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

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.

payments-split-tender

Tender handling belongs to the underlying POS.

payments-refund-void-controls

No POS authorization model; Chowly's own user roles are undocumented.

payments-chargeback-tooling differentiator

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

payments-card-on-file differentiator

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

payments-payout-timing differentiator

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

payments-multi-entity-routing differentiator

Chowly never holds or routes merchant settlement funds — 'payments settle through your existing processor' plus this record's settled payout finding (payments-payout-timing, grade B) establish that settlement banking is configured at each operator's own processor, so there is no Chowly settlement layer in which per-location or per-legal-entity bank routing could be configured. The single exception, Google Ordering, routes payment to Chowly's payment processing partner per the Terms, and no per-entity routing is documented for that channel either. Checked 2026-08-04.

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. adversarially verified

delivery-driver-roster

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.help/s/article/FAQ-How-will-delivering-my-own-orders-affect-my-integration and the adversarial pass returned it to unknown: Quote verified verbatim in chowly/FAQ-How-will-delivering-my-own-orders-affect-my-integration.txt, URL matches. The FAQ is a how-does-self-delivery-affect-my-integration article, not a closed enumeration of the self-delivery offer: it says 'has the same capabilities as one using a food ordering platform' and 'set a minimum order total or charge a delivery fee upon request', then invites the reader to 'contact Chowly Support' for the rest, and moves on to future-order printing. Nothing in it says drivers are unsupported. Terms 2(d) is permissive ('Restaurant may elect to utilize a courier service'), not exclusive. The vendor's own product copy contradicts the 'no driver entity' premise: chowly-com/agents__delivery.txt says the agent watches 'Driver Availability - Real-time pool across DoorDash, UberEats, Grubhub, in-house', lists 'AI-driven driver selection per order' and logs 'Switched 3 orders from 3PD driver to in-house', and the automation blog says 'Orders automatically dispatch to the best available driver from your delivery network'. That is grade C/D marketing and does not establish clock-in/out, assignment state or per-driver run history, but it does establish that the current platform has some notion of in-house driver availability, so the older FAQ cannot be read as the whole of the offer. Corpus grep for driver/dispatch/courier/clock-in found no roster, clock-in/out or per-driver report anywhere - which is absence, not positive evidence. Falls to unknown per the proposer's own fallback. 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). The self-delivery documentation is now read in full and it describes an integration posture, not a driver module: FAQ - How will delivering my own orders affect my integration says a self-delivering restaurant "has the same capabilities as one using a food ordering platform", that "Chowly's software allows restaurants to set a minimum order total or charge a delivery fee upon request", and then discusses future-order print buffer times. Koala Checkout Configurations (Olo Users Only): Self-Delivery, retrieved for the first time here, shows the Koala side is only a handoff mode: "Koala currently supports Olo's Self-Delivery handoff mode, which allows orders to be put in on a Koala Responsive Website and route to Olo with delivery set as fulfillment. This allows a brand to manage their own delivery program" - the driver program is the brand's, run outside Chowly. chowly.statuspage.io/api/v2/components.json lists 45 operational components (Orders API, Menus API, Dejeuner, Restaurant Control Center, Koala, Chowly Printers, per-POS and per-marketplace entries) and none is a driver, dispatch or delivery service. Against that, chowly.com/agents/delivery/ markets a "Real-time pool across DoorDash, UberEats, Grubhub, in-house" with "AI-driven driver selection" - grade D, and it describes routing, not a driver record with clock-in/out and run history. Neither presence nor absence established. Unresolved. adversarially verified

delivery-dispatch-board

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). Read every operator-facing screen Chowly documents and none is a dispatch board. The Restaurant Control Center's surface is now enumerated for the first time from Sales Reporting Page on the Restaurant Control Center: "There are seven different reporting pages: Locations, Sales, Orders, Product Mix, Week over Week, Delivery Buydown, and Smart Pricing", plus the operational articles Pausing Platforms, Suspending Items, Setting Hours, Holiday Hours, Checking Platform Statuses and Resyncing Your Menu. That is an analytics-and-controls console, not an expo screen - no undispatched-order queue, driver availability panel, elapsed-time-per-order display or multi-order run batching appears in any of them. "Dispatch" occurs in the corpus only as Olo's courier network (Koala Checkout Configurations (Olo Users Only): Dispatch & Delivery - "most of the UI keys off of the response from Olo to determine whether Dispatch or Delivery are supported") and in Koala Olo Menu Partners: Dispatch Tracking Webhooks. The seven-page list is an enumeration of RCC reporting, not of the whole RCC, so it cannot carry a no. Unresolved.

delivery-route-map differentiator

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.

delivery-driver-tracking differentiator

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 full app portfolio is now visible across the deployment series and it is entirely guest- or store-facing: Koala Web Ordering, Koala iOS Mobile, Koala Android and the Koala iOS Kiosk, each with its own App Deployment and Release articles, plus the Chowly Printer. No driver-facing application appears in any of them, and none of the 45 components at chowly.statuspage.io/api/v2/components.json is a driver app. Searched every body for GPS, latitude, longitude, geofence and "driver app": zero hits. The only delivery telemetry documented is inbound and third-party - Koala Olo Menu Partners: Dispatch Tracking Webhooks subscribes Koala to Olo's DispatchStatusUpdate webhook for "near real-time status updates for dispatch orders, including updated estimated delivery times", which is order status and ETA from Olo rather than coordinates from a Chowly-operated driver device. A missing app in a deployment library is not an enumeration of the product. Unresolved.

delivery-zones-polygon differentiator

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). No operator-facing delivery-zone editor is documented on any Chowly surface, and the zone geometry consistently lives elsewhere. New evidence retrieved this pass: Revel Sync instructs operators to "set your delivery radius to a minimum of 15 miles" and to set the maximum distance in the Revel POS, i.e. the radius is a POS-side setting Chowly asks you to widen, not one it defines; Koala Location Configurations: Delivery Search describes "the store validation algorithm" returning no result when there is "no location that is within range of the user's provided address and delivers to the user's provided address", but never says how that range is expressed, and Koala Checkout Configurations (Olo Users Only): Dispatch & Delivery makes it Olo's answer - "most of the UI keys off of the response from Olo to determine whether Dispatch or Delivery are supported". FAQ - How will delivering my own orders affect my integration offers only an order minimum and a delivery fee "upon request". "Polygon", "isochrone" and "drive time" occur nowhere in the 195 bodies. Whether any Chowly-side zone object exists, and with what geometry, is undetermined. Unresolved.

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

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

delivery-driver-comp differentiator

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 mileage, reimbursement, payroll, wage, driver tip and settlement: no occurrences. Chowly holds no driver record to attach compensation to (see delivery-driver-roster) and publishes no labour module - none of the 45 components at chowly.statuspage.io/api/v2/components.json is a labour, payroll or driver service, and the seven RCC reporting pages named in Sales Reporting Page on the Restaurant Control Center (Locations, Sales, Orders, Product Mix, Week over Week, Delivery Buydown, Smart Pricing) are all order- and revenue-side. Tipping appears twice and both are guest-side capture with no allocation statement: Koala Checkout Configurations: Tipping (three configurable percentage tiers of the basket subtotal plus an optional custom field, configurable separately for Pickup and Delivery) and the Brink tender setting "Allow Tips" (Brink with Chowly Overview). No source states where tip funds go or whether any reimbursement line exists. Unresolved.

delivery-cash-reconcile

A driver settle-up reconciling cash collected requires cash tender records Chowly structurally lacks: 'Chowly holds no tender, cash, tax or drawer data - those live in the POS' is a settled grade-B finding of this record (reporting-eod-closeout), and its own channels are card/wallet checkouts settling through the operator's processor. It also ships no driver module with shift state (delivery-driver-roster remains undocumented beyond the Delivery Agent's routing awareness of 'in-house' drivers). With neither cash data nor a driver cash-bank surface, a per-driver over/short settlement flow has nothing to run on. Checked 2026-08-04.

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

delivery-daas-fallback differentiator

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

delivery-3p-direct-integration differentiator

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

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

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

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

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

delivery-3p-reconciliation differentiator

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

delivery-injection-error-visibility differentiator

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

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

delivery-promise-time differentiator

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). Chowly's only documented timing controls are manual and coarse, and the dynamic ones belong to partners. FAQ - How will delivering my own orders affect my integration has Chowly staff set print buffer times for future orders and warns they "need to be set as the exact time it takes to prepare an order" - a fixed per-store constant, applied to ticket printing rather than to a guest quote. Koala Olo Menu Partners: Dispatch Tracking Webhooks receives "near real-time status updates for dispatch orders, including updated estimated delivery times" from Olo, so the dynamic ETA is computed by Olo Dispatch and passed through post-order. Nothing documents how the promise time shown to a guest at checkout is derived, and kitchen load, driver availability and zone drive time appear as inputs nowhere in the 195 bodies - although chowly.com/agents/delivery/ markets "Prep Times + Order Volume" and "Customer Distance + ETA" as agent inputs, which is grade D. Unresolved.

delivery-offline-behavior

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). Read the four articles that touch degraded operation and none answers the question. Koala Incident Response Protocol is about Koala's own outages (Datadog and OpsGenie monitoring, four SLA failure levels with response and resolution targets, post-mortems). Order Failures: Causes and Next Steps covers order-injection failures between marketplace, Chowly and POS. FAQ - How do I stop orders from coming in and FAQ - How can I check if my third party platforms are online cover deliberate pausing and platform status, and Checking Platform Statuses on the Restaurant Control Center is the RCC view of the same. The nearest thing to a degraded-mode statement is FAQ - Why is "Chowly Open Item" printing on tickets?, which says the open item "can be used as a fail safe to help push through orders in certain situations" - a fallback inside order injection, not an internet-outage policy. "Offline" occurs once in 195 bodies, in Koala Olo Menu Partners: Olo Location Webhooks, meaning a location taken offline. Chowly holds no driver records, so part of the claim may be inapplicable, but no offline behaviour is documented in either direction. Unresolved.

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

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

digital-native-app differentiator

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

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

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

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

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

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

digital-kiosk differentiator

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

digital-group-ordering

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 group order, shared cart, spend cap, split payment and participant: no occurrences. The basket behaviour Chowly documents is single-guest throughout - Koala: Web Ordering Feature Set lists under View Basket & Checkout only cross-sell, Machine Learning Cross Sell, basket editing including "migrations to a new store location", guest checkout and order confirmation emails, and the closest multi-person feature is "Allow guests to assign item recipients" (Koala Menu Configurations (Olo Users Only): Assigning Item Recipients), which labels items within one guest's order rather than opening a cart to other people. That article set is scoped to Koala Enterprise web ordering and does not cover Chowly Online Ordering (named as a distinct ordering platform in Toast: Nested Modifier Settings with Chowly and as its own statuspage component) or the kiosk. Nothing rules a group-ordering flow in or out. Unresolved.

digital-catering-portal differentiator

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/partnerships/ and the adversarial pass returned it to unknown: Quote confirmed at chowly-com/partnerships.txt:41-42 ('ezCater / Catering order integration for high-value business orders'), URL matches. The claim is a distinct first-party catering ordering flow with catering menu/minimums, lead-time rules, quotes, deposits and invoice/house-account/ACH terms. An ezCater marketplace-order injection is a channel; every catering rule (minimums, lead time, invoicing) on that path belongs to ezCater. Corpus grep for 'catering' finds only that listing, the Koala 'Delivery Order URL ... unique URL for delivery or catering' slot (Koala-General-Configurations-Managing-Locations.txt:31, which points guests at an external system), a Mr. B's case-study phrase 'online catering' with no product named, BentoBox mentions on alternatives pages, and a catering blog post whose body did not render. No limb of the claim is present on a Chowly surface; the present half is a partner listing at grade D. Unknown. 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). Catering occurs exactly once in the 195 bodies and it is a URL slot, not a flow: Koala General Configurations: Managing Locations says "Delivery Order URL is used to create a secondary CTA on a location card. The standard use case is to provide a unique URL for delivery or catering" - i.e. brands point the second CTA at some other catering system. No separate catering menu, order minimum, lead-time rule, quote, deposit or invoice/ACH term is documented on any Chowly surface, and none of the 45 components at chowly.statuspage.io/api/v2/components.json is a catering service. Catering reaches Chowly today through the marketplace path via the ezCater integration reported by third parties, which is a channel connection rather than a first-party portal. The Koala feature set is scoped to Koala Enterprise web ordering and its checkout inventory sits under "For Olo Users Only: Add-On Features", so it cannot exhaust the vendor. Unresolved. adversarially verified

digital-voice-ai-phone differentiator

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

digital-drivethru-ai

No drive-thru product at all.

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

digital-google-order differentiator

"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

digital-apple-business-connect

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). Confirmed against the wider corpus rather than the sitemap subset. Apple occurs only as Apple Pay (Koala Square Menu Partners: Adding Digital Wallets), Apple SSO (Koala Punchh Loyalty Partners: Apple SSO), and Apple Business Manager / App Store Connect across the iOS kiosk and mobile deployment series - never Apple Business Connect and never a Maps place-card action. The one documented search-and-maps ordering placement is Google: Google Direct Order with Chowly Overview and Google Direct Order: Enabling Online Ordering / Setting a Preferred Provider cover Google Search, Maps and Voice, and "Google Food Ordering" is a live component at chowly.statuspage.io/api/v2/components.json. No article purports to enumerate the full set of placement channels - the Google articles describe one channel, not the closed set - so absence of an Apple Business Connect article is not positive evidence of absence. Unresolved.

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

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

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

digital-guest-data-ownership differentiator

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

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-read every fee- and tax-bearing article in the widened corpus. Chowly's own fee levers are embedded markups with no guest-facing line item: the RCC upcharge percentage "on all of your third party platforms at the same time or on a platform-by-platform basis" (FAQ - How do I set upcharges to my menu items), confirmed by Product Mix Reporting on the Restaurant Control Center reporting "Min and Max Price ... (differs when varying upcharges are used)". Tax Settings for Ordering Channels states "Chowly's software and Support Team are unable to alter taxes in anyway" and pushes every jurisdictional question to the marketplace, walking through Marketplace Facilitator coverage per platform. Google Direct Order with Chowly Overview discloses a 5% Google processing fee plus Stripe's $0.30 + 2.9%, which are merchant-side costs. The Koala checkout inventory has tipping, promo codes and gift cards but no service-fee or surcharge configuration. Nothing states behaviour in jurisdictions or card-brand programmes where surcharging is prohibited, and none of these is an exhaustive statement of the fee-configuration surface. Unresolved.

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

guest-loyalty-thirdparty-identity-attach differentiator

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

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

guest-loyalty-tiers differentiator

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

guest-loyalty-offline-behavior differentiator

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-read the failure-behaviour set. Koala Incident Response Protocol classifies a Level 2 major failure as explicitly including "issues with loyalty provider" and gives response and resolution targets, but its only statement about guest-visible consequences is that "it is ultimately the responsibility of our customers to be aware of the health of those systems" - it never says what a guest sees, or what happens to accrual, when Punchh, Paytronix or Spendgo is unreachable. Order Failures: Causes and Next Steps covers order-injection failures with no loyalty content. Koala Punchh Loyalty Partners: Advanced Loyalty Dashboard describes earn and redeem in store ("Enter barcode to earn points on a purchase") without a degraded path. "Offline" occurs once in 195 bodies, in Koala Olo Menu Partners: Olo Location Webhooks, meaning a location taken offline. There is no queue-and-reconcile versus blocked statement to score and no document purports to enumerate degraded-mode behaviour. Unresolved.

guest-loyalty-offer-stacking-rules differentiator

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). Chowly's documented offer surface remains two basket actions defined elsewhere: "Apply a promotion code to the basket" (listed under "For Olo Users Only: Add-On Features > Checkout") and "Apply a loyalty reward to the basket" under SSO + Loyalty, where "Features may vary by integration partner (Punchh, Paytronix, Spendgo, etc.)" - both in Koala: Web Ordering Feature Set. Promotion and reward definition therefore lives in Olo and in the loyalty partner, not in the Brand CMS. The only ordering/precedence mechanism Chowly configures anywhere is for cross-sell, not discounts: Koala Cross-Sell Configurations: Machine Learning Cross Sell says rules "can be sorted via drag and drop functionality to determine the sequence in which the rules should apply". No exclusive-versus-combinable flag, discount precedence or order-of-application setting appears in the 195 bodies. Because the offer engine belongs to a partner, Chowly's documentation cannot enumerate its configuration and absence here proves nothing. Unresolved.

guest-loyalty-targeted-offers differentiator

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

guest-loyalty-rfm-segmentation differentiator

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

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

guest-loyalty-native-email-sms differentiator

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

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

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

guest-loyalty-campaign-attribution differentiator

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

guest-loyalty-data-export-portability differentiator

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

guest-loyalty-cdp-event-api differentiator

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

guest-loyalty-review-capture-routing differentiator

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

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

guest-loyalty-wallet-pass differentiator

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 wallet article remains Koala Square Menu Partners: Adding Digital Wallets, and it is about payment rather than loyalty: "Available Digital Wallet Platforms: Google Pay, Apple Pay", enabled through Square as the payment provider with brand-supplied application IDs. The documented in-store loyalty carrier is a scannable barcode inside the branded app - "Scan Your Barcode functionality (Punchh only)" in Koala: Web Ordering Feature Set and "Enter barcode to earn points on a purchase" in Koala Punchh Loyalty Partners: Advanced Loyalty Dashboard. No Apple Wallet or Google Wallet loyalty pass, .pkpass, push-updatable balance or PassKit/Wallet API reference occurs in the 195 bodies. This is not scored no because in this architecture the pass would be issued by the loyalty provider (Punchh, Paytronix, Spendgo), whose feature set Chowly's Koala Enterprise web-ordering enumeration expressly does not purport to cover ("Features may vary by integration partner"). Unresolved.

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

guest-loyalty-redemption-fraud-controls

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 all 195 bodies for fraud, velocity, approval, manual adjustment, audit log and self-redemption: no occurrences. The only anti-abuse control documented anywhere is Koala General Configurations: Enabling reCAPTCHA, which protects sign-in/sign-up against bot traffic ("reCAPTCHA primarily activates when it suspects malicious activity") and is unrelated to redemption. Redemption is executed by the loyalty partner - Koala Punchh Loyalty Partners: Advanced Loyalty Dashboard covers earn and redeem in store - and manual point adjustments would be made in the Punchh, Paytronix or Spendgo back office, whose controls Chowly does not publish. Chowly's own back-office access model is itself undocumented beyond provisioning: Creating a Restaurant Control Center Account describes only support-issued email invitations, so there is no permission surface against which a manager-approval requirement could even be expressed. Unresolved.

guest-loyalty-ai-offer-recommendation differentiator

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

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

labor-clock-in-at-pos

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

labor-photo-punch-verification differentiator

No labor product.

labor-geofenced-mobile-punch

No labor product.

labor-offline-time-punch differentiator

No labor product.

labor-granular-rbac

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). Read the full Restaurant Control Center article set - Creating a Restaurant Control Center Account, Logging Into the Restaurant Control Center, FAQ - How do I get into Chowly's Restaurant Control Center, Setting Hours, Holiday Hours, Pausing Platforms, Suspending Items, Checking Platform Statuses, Resyncing Your Menu, Sales Reporting and Product Mix Reporting - which is every RCC document Chowly publishes. Access is provisioned only by support: "A Support Team member will ask you for the email address(es) of whoever would like access ... You can give more than one email address access ... If you have multiple locations, you will need to have the names of them ready", followed by a "Confirm invitation" email from support@chowlyinc.com. There is no user-management screen, no role, no permission and no access-level article anywhere in the 195 bodies, and the analytics side is enumerated as seven reporting pages with no admin page among them. Location names are collected at provisioning, which hints at location scoping, but the article does not say access is restricted to them. Chowly is also not a POS, so void, comp, drawer open and price change have no counterpart in its product - but its own docs never state that boundary, and a provisioning walkthrough is not an enumeration of a permission model. Unresolved.

labor-manager-override-audit

No POS override surface.

labor-native-scheduling differentiator

No labor product.

labor-demand-labor-forecast differentiator

Delivery Agent references staffing to adjust marketplace hours, but Chowly produces no labor forecast.

labor-realtime-labor-percent differentiator

No labor cost data in the platform.

labor-overtime-prevention differentiator

No labor product.

labor-break-compliance-by-state differentiator

No labor product.

labor-fair-workweek-support

No labor product.

labor-minor-labor-rules

No labor product.

labor-tip-pooling-rules

No labor product.

labor-tip-distribution-audit-trail

No labor product.

labor-qualified-tips-w2-reporting differentiator

No labor or payroll product.

labor-native-payroll differentiator

No payroll product.

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

labor-shift-swap-workflow differentiator

No labor product.

labor-digital-onboarding-i9

No HR product.

labor-server-performance-metrics differentiator

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

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

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

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

reporting-comps-voids-audit

Comps and voids are POS-side events Chowly does not own.

reporting-cash-over-short

No drawer or cash data.

reporting-labor-productivity

No labor data in the platform.

reporting-server-scorecards differentiator

No employee dimension in Chowly reporting.

reporting-channel-profitability differentiator

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

reporting-multiloc-drilldown differentiator

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

reporting-custom-report-builder differentiator

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

reporting-scheduled-delivery

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/ and the adversarial pass returned it to unknown: Quote confirmed at chowly-com/home.txt:123-126, URL matches. Context (lines 100-126) shows it is the 'From Demo to More Profit in 90 Days' sales timeline, sitting after 'Dedicated CSM assigned to your account' - 'Monthly health reports show the full picture' reads as an account-management deliverable, not a product feature, and it says nothing about the operator choosing a report, cadence or recipients. Corpus grep for 'weekly report|monthly report|health report|digest|scheduled report|subscribe|report.*email' finds no other hit; the only documented data-out control is the per-tile Download (Navigating-the-Restaurant-Control-Center.txt:41). A homepage narrative line is not a present half for 'schedule any report ... on a defined cadence and recipient list'. The analyst's own note concedes 'Honest alternative is unknown'. 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. All seven reporting pages are now retrieved in full and each repeats the same enumeration verbatim - "There are seven different reporting pages: Locations, Sales, Orders, Product Mix, Week over Week, Delivery Buydown, and Smart Pricing" - with every tile on every page described individually. Navigating-the-Restaurant-Control-Center documents the control set that appears on every RCC tile: "The Filters, Expand, and Three Dots icons function more-or-less the same in every tile", where Filters changes "the range of dates/time used in the tile, and the locations used in the tile" and "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." So the RCC's data-out control is a manual per-tile Download; there is no schedule, subscription, recipient list, recurring email, SFTP or destination-delivery control on any tile, and Date Range Settings offers only Quick Select presets and fixed or relative custom ranges. Across all 204 article bodies no scheduled-report, subscription or report-delivery feature appears, and chowly.statuspage.io/api/v2/components.json (plain UA, HTTP 200) lists 45 components - Orders API, Menus API, Menu API, SDK API, V2 TOOS Partner API, Acknowledge Order API, Aperitif (Reporting Portal), Aboyeur, Dejeuner, Garcon, Restaurant Control Center, Managed Emails and so on - with no report-delivery or scheduler service. The one article that enumerates the tile action menu describes itself as "an overview of the basic structures" of the RCC, which the evidence bar excludes as an enumeration, and the RCC's Store Settings page - "allows you to update a large number of settings" - has no published reference article at all. A scheduled delivery would sit in that undocumented settings area rather than on a reporting page, so the seven-page enumeration does not reach it. Unresolved. adversarially verified

reporting-raw-warehouse-export differentiator

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. The floor this claim contrasts against is now documented rather than merely absent: Navigating-the-Restaurant-Control-Center documents the control set that appears on every RCC tile: "The Filters, Expand, and Three Dots icons function more-or-less the same in every tile", where Filters changes "the range of dates/time used in the tile, and the locations used in the tile" and "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." and the Orders reporting page's Order Detail tile is transaction-level (LOCATION NAME, CUSTOMER NAME, SALES DATE, SUBTOTAL, TIP, SALES TAX, TOTAL, PLATFORM, ERROR OR CANCELLATION REASON, SERVICE TYPE, ORDER STATUS), so a manual per-order download exists. Above that floor there is nothing: "S3", "SFTP", "Snowflake", "BigQuery", "Redshift", "warehouse", "data feed" and "scheduled export" occur zero times across the 204 article bodies; chowly.statuspage.io/api/v2/components.json lists 45 components with no ETL, export or warehouse service; https://chowly.com/sitemap.xml (re-fetched today, 167 URLs) contains no developer, docs or data page; and api./docs./developer./developers.chowly.com all fail DNS. The one article that enumerates the tile action menu describes itself as "an overview of the basic structures" of the RCC, which the evidence bar excludes as an enumeration, and the RCC's Store Settings page - "allows you to update a large number of settings" - has no published reference article at all. Because no document enumerates Chowly's data-egress surface, this is assessed and unresolved rather than a documented absence.

reporting-public-api differentiator

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

reporting-webhooks differentiator

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. "Webhook" occurs 48 times across the 204 bodies and every occurrence is Chowly or Koala SUBSCRIBING to a partner: Koala-Olo-Menu-Partners-Olo-Menu-Webhooks ("The MenuItemAvailabilityChanged webhook notifies us when an item on a location's menu has been 86'ed or 68'ed"), Koala-Olo-Menu-Partners-Olo-Location-Webhooks (VendorAvailabilityChanged, VendorTemporarilyDisabled; "Koala has integrated with the following Olo webhooks"), Koala-Olo-Menu-Partners-Dispatch-Tracking-Webhooks (DispatchStatusUpdate), Koala-Olo-Menu-Partners-Syncing-Locations-with-Olo and Koala-Square-Menu-Partners-Inventory-Webhooks ("Koala supports the ability to integrate with Square's Webhooks for Inventory"). Not one describes Chowly emitting events to a customer-supplied endpoint, and "HMAC", "signature", "signing secret" and "replay" appear nowhere. chowly.statuspage.io/api/v2/components.json lists 45 components with no webhook, event or delivery service; the closest is "Acknowledge Order API", which is an inbound acknowledgement path. No published document enumerates Chowly's outbound integration surface, so this is unresolved rather than absent.

reporting-api-not-upcharged differentiator

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

reporting-tier-paywall differentiator

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

reporting-history-retention differentiator

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. "Retention", "archive", "historical data", "months of history" and "purge" occur zero times across the 204 bodies. The two nearest facts are both new this pass and neither is a retention commitment. Navigating-the-Restaurant-Control-Center documents the date control: "Quick Select allows you to choose from a set of predefined and commonly-used date ranges. Custom Ranges can be fixed or relative and then set for any number of minutes, hours, days, months, quarters, etc." - no cap is stated, but no floor is guaranteed either. The longest window any tile actually shows is the Week-over-Week page's "Last 12 Weeks Sales" tile (that page is also the only one defaulting to 21 days rather than 7); 12 weeks is far short of 24 months but is a tile default, not a data-availability limit. Koala-Cross-Sell-Configurations-Machine-Learning-Cross-Sell's "rolling 90 days worth of orders OR 400k orders whichever comes first" bounds a training window, and Koala-IOS-Mobile-Configurations-Account-Deletion covers guest-record deletion, not transaction retention. https://chowly.com/terms-and-conditions/ (re-read today) contains no retention or archive clause. Unresolved.

reporting-anomaly-alerts differentiator

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/ads/ and the adversarial pass returned it to unknown: Quotes confirmed at chowly-com/agents__ads.txt:86,50, agents__delivery.txt:67, agents__review.txt:58, agents__campaign.txt:32, automation blog line 126; URL matches. But the claim is a proactive push/email alert to the operator when an operator-configured reporting metric (void spike, sales vs forecast, discount rate) breaches or deviates. What the marketing describes is automatic action on agent metrics - pausing an ad campaign below an ROI threshold, pausing a platform on prep time, sending a win-back email - and the one 'alerted operations' line is a simulated activity-log entry on the Review Agent page. No page claims threshold alerts on sales/void/discount metrics, and grep of every RCC article and Checking-Platform-Statuses for 'alert|notif' finds only the 15-minute publish-lock notification. The present half is a different feature (ad-spend guardrail) with marketing sentences attached; the rule that C/D marketing yields partial applies only when the marketing claims THE capability, which it does not. 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. All seven reporting pages are now retrieved in full and each repeats the same enumeration verbatim - "There are seven different reporting pages: Locations, Sales, Orders, Product Mix, Week over Week, Delivery Buydown, and Smart Pricing" - with every tile on every page described individually. Navigating-the-Restaurant-Control-Center documents the control set that appears on every RCC tile: "The Filters, Expand, and Three Dots icons function more-or-less the same in every tile", where Filters changes "the range of dates/time used in the tile, and the locations used in the tile" and "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." Nothing in that control set is an alert, threshold or subscription. Checking-Platform-Statuses-on-the-Restaurant-Control-Center remains pull-based - Location Status, Menu Publish Status, Availability Status and per-platform statuses the operator goes and looks at, with the remedy "please reach out to Chowly's Support Team". Koala-Incident-Response-Protocol's alerting is Chowly-internal: "Koala has automated Datadog monitoring alerts set for API failures. If these alerts are triggered, members of the Koala team are notified via OpsGenie immediately", with customers told only about Level 1 and Level 2 incidents that cannot be resolved quickly. The only operator-facing notification documented anywhere is an in-app rate-limit warning in Suspending-Items-Restaurant-Control-Center ("86ing items and publishing menu changes can only be done in 15 minute increments"). No operator-configured metric threshold, deviation-from-history rule, or push/email alert over sales, voids or discount rate appears in any of the 204 bodies, and chowly.statuspage.io's 45 components include "Managed Emails" (a marketing service) but no alerting service. The one article that enumerates the tile action menu describes itself as "an overview of the basic structures" of the RCC, which the evidence bar excludes as an enumeration, and the RCC's Store Settings page - "allows you to update a large number of settings" - has no published reference article at all. Unresolved. adversarially verified

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

reporting-guest-cohorts differentiator

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

reporting-sales-forecast differentiator

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

reporting-tip-tax-compliance

No tip or payroll data in the platform.

multi-location-org-hierarchy

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.help/s/article/Locations-Reporting-Page-on-the-Restaurant-Control-Center and the adversarial pass returned it to unknown: Quotes confirmed at chowly/Locations-Reporting-Page-on-the-Restaurant-Control-Center.txt:19,39,41,47, Creating-a-Restaurant-Control-Center-Account.txt:21 and restaurant-types__multi-concept-groups.txt:30; URLs match. What the B-grade evidence establishes is a two-level model - one account, named locations, ad-hoc 'location sets' as a report filter. The claim text explicitly excludes that model: 'at least three levels ... as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations'. A flat list is what the claim says does not count, so it cannot serve as the present half of a partial. Grep for 'region|district|franchisee|parent account|group.*location|hierarch' across the help centre finds only Olo's Brand Menu Admins and an Aloha regional email. No enumeration closes the question (Store Settings and RCC user management are undocumented), so this is unknown rather than no; the flat two-level finding belongs in the rationale, not the verdict. 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. All seven reporting pages are now retrieved in full and each repeats the same enumeration verbatim - "There are seven different reporting pages: Locations, Sales, Orders, Product Mix, Week over Week, Delivery Buydown, and Smart Pricing" - with every tile on every page described individually. The scoping construct is now visible and it is a set, not a tree: every reporting article says "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 Navigating-the-Restaurant-Control-Center says the per-tile Filters icon "allows you to change two things: the range of dates/time used in the tile, and the locations used in the tile", with a top-right "Search Bar [that] allows you to quickly access your desired location by name". Locations-Reporting-Page-on-the-Restaurant-Control-Center enumerates its entire Platforms Enabled per Location table - STATUS, NAME, ORDER PLATFORM, ORDER PLATFORM STATUS - with no region, group, district, brand or concept column, and its tiles count only "Locations Online" and "Enabled Platforms". On the Koala side, Koala-General-Configurations-Managing-Locations enumerates the whole per-location settings screen (Username/Olo location ID, Payment Location ID, Delivery Order URL, Loyalty Reference ID, Alcohol Verification PIN, three Location Status options, ASAP Ordering) with no parent or group field. So the documented model is account -> location, two levels, with ad-hoc location sets. What blocks a verdict: no article defines what a location set is or whether it persists as a named object that permissions or reporting can be scoped to, Overview-of-the-Manage-Locations-Page (already cited in this record's sources) returns no article version id when probed again today, and chowly.com/restaurant-types/multi-concept-groups/ says only that "each brand gets its own tailored strategy, while the group sees everything from one dashboard" - grade-D marketing. Unresolved. adversarially verified

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

multi-location-local-override-policy differentiator

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

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

multi-location-scheduled-publish differentiator

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

multi-location-new-store-template differentiator

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

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

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. The whole documented identity lifecycle is now in hand and contains no tenancy concept. Creating-a-Restaurant-Control-Center-Account: "A Support Team member will ask you for the email address(es) of whoever would like access to your Restaurant Control Center. You can give more than one email address access if you'd like to have multiple accounts able to use your control center. (2) If you have multiple locations, you will need to have the names of them ready. Our Support Team will need to know this information to give you access to all that the Restaurant Control Center has to offer. (3) You will receive an email from support@chowlyinc.com ... Click the 'Confirm invitation' link." FAQ-How-do-I-get-into-Chowly-s-Restaurant-Control-Center and Logging-Into-the-Restaurant-Control-Center then document sign-in at chowly.app / dashboard.chowly.app with email and password. No corporate vs franchisee tenant, no scoping of one operator's access to a subset of another's locations, and the word "franchise" appears in none of the 204 article bodies. Chowly also holds no employee, banking or labor data, so the claim's second limb has no object in this product. Left unresolved rather than absent because franchisor/franchisee separation is a commercial and contractual arrangement that would be configured by Chowly Support for an enterprise account (the Terms at chowly.com/terms-and-conditions/ restrict access only as a licence limit - "Restaurant shall not allow persons other than its employees or contractors to access or use the Services") and would not necessarily appear in a self-serve how-to; the only franchise evidence remains the Golden Krust marketing case study.

multi-location-royalty-calculation differentiator

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

multi-location-royalty-collection

No franchise financial management product.

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

multi-location-normalized-item-rollup differentiator

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

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

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

multi-location-multi-brand differentiator

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

multi-location-multi-tax-jurisdiction

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

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

multi-location-config-audit-log differentiator

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. "Audit log", "change history", "version history" and "revision" occur zero times across the 204 bodies. Every configuration flow now documented ends at a save or publish with no record: Upcharge-Settings-on-the-Restaurant-Control-Center ("Select the upcharge percentage ... Click the blue 'Save' button"), Setting-Hours-in-the-Restaurant-Control-Center and Holiday-Hours-on-the-Restaurant-Control-Center ("Store Tools > Store Settings ... Hover over Menu Hours and click the pencil icon"), Pausing-Platforms-on-the-Restaurant-Control-Center, Suspending-Items-Restaurant-Control-Center ("click 'Publish'") and, on the Koala side, Managing Locations, Managing Strings and Marketing Tags ("To edit a tag, select the pencil icon next to the tag. To delete a tag, select the trash icon"). Menu propagation is described as overwriting the third-party menu from the POS with no publish record. chowly.statuspage.io/api/v2/components.json lists 45 components - including Chowly's five named user tools, Aperitif (Reporting Portal), Aboyeur (Printer and Menu Status Page), Dejeuner (Chowly Menu Manager), Garcon and the Restaurant Control Center - and none is an audit or history service. Much configuration is also performed by Chowly Support on the operator's behalf (adding platforms, category selection, 86'ing on Revel), which is exactly where a trail would matter and where nothing states whether actions are logged. The one article that enumerates the tile action menu describes itself as "an overview of the basic structures" of the RCC, which the evidence bar excludes as an enumeration, and the RCC's Store Settings page - "allows you to update a large number of settings" - has no published reference article at all. Unresolved.

multi-location-enterprise-sso differentiator

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. "SAML", "SCIM", "OIDC" and "single sign-on" occur zero times across the 204 bodies. The SSO articles that do exist are DINER identity for brand ordering apps, not workforce identity: Koala-Punchh-Loyalty-Partners-Apple-SSO ("Koala offers the ability for users to authenticate via Apple SSO for brands using Punchh", configured with a Services Identifier client_id and OAuth redirect URLs under Web Ordering > Config > Integrations), the matching Facebook-SSO article, and the "SSO + LOYALTY" block of Koala-Web-Ordering-Feature-Set - and that feature list is scoped to Koala Enterprise web ordering only, so it cannot enumerate the vendor. The back-office side is now fully documented and is password-only: Creating-a-Restaurant-Control-Center-Account (Support collects the email addresses that should have access, the user clicks "Confirm invitation") and Logging-Into-the-Restaurant-Control-Center ("enter the email address and password you used to create your account"), with recovery by an emailed reset link. Those are getting-access how-tos rather than an enumeration of supported authentication methods, and an IdP integration for an enterprise account is routinely arranged through an account manager without a public article, so this stays unresolved rather than a positive absence. No deprovisioning or SCIM statement exists anywhere.

multi-location-enterprise-api differentiator

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

multi-location-central-labor-policy

No labor product.

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

extensibility-api-access-cost differentiator

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

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

extensibility-free-sandbox differentiator

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

extensibility-oauth-partner-apps

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. The prior no at grade A rested on goparrot/chowly-api-client's static api-key header: last push 2021-07-20, 0 stars, no description, owner GoParrot, Inc., a third party since acquired by Square. A third-party wrapper's choice of auth header is not an enumeration of the authentication mechanisms a vendor offers, and a 2021 artifact cannot establish what is absent in 2026; grade A is not available for it. The live 401 on https://api.chowlyinc.com/api/toos/v2/menus (re-probed today) confirms the endpoint exists and nothing about its authorization surface. What is established, and short of the claim: every operator-facing authorization procedure documented in the help centre is credential handover, not scoped revocable consent granted by the operator to a third party - Koala-Square-Menu-Partners-Square-Application-ID-and-Access-Tokens, Koala-iOS-Kiosk-App-Deployment-Grant-Admin-Access-to-Square ("Admin is the only permission group which gives access to your Application ID and Access Tokens. Creating a custom permission group (even with all permissions granted) will not allow the user to access this required information"), and the Koala kickoff articles that ask brands to hand over "Sandbox and Production API Keys" and "Client ID and Secret ID". Where OAuth does appear it is Koala acting as a client against someone else's IdP (Koala-Punchh-Loyalty-Partners-Apple-SSO redirect URLs; Koala-iOS-Kiosk-App-Deployment-Verifying-Square-Payment-with-Koala: "log into your Square account and give permission to the Koala Application"), not Chowly issuing scoped tokens. Chowly's own five API surfaces (per chowly.statuspage.io) publish no auth model anywhere reachable. Whether Chowly offers OAuth to partner apps is undetermined.

extensibility-webhooks-push

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. All five webhook articles were re-read and every one has Chowly or Koala SUBSCRIBING to a partner's webhooks, never emitting: Koala-Square-Menu-Partners-Inventory-Webhooks ("Koala supports the ability to integrate with Square's Webhooks for Inventory"), Koala-Olo-Menu-Partners-Olo-Location-Webhooks (VendorAvailabilityChanged, VendorTemporarilyDisabled), -Olo-Menu-Webhooks (MenuItemAvailabilityChanged), -Dispatch-Tracking-Webhooks (DispatchStatusUpdate), -Syncing-Locations-with-Olo. The only publicly visible partner API shape is polling-shaped (GET /api/toos/v2/menus, POST /api/toos/v2/orders, GET /api/toos/v2/orders/{id}; the menus path returns 401 on re-probe today) with no subscription or callback registration, but that wrapper is a third-party 2021 artifact and cannot bound the surface. Against it, chowly.statuspage.io/api/v2/components.json names an "Acknowledge Order API" and an "SDK API", and FAQ-Chowly-s-POS-API-Integration confirms an inbound Chowly POS API that roughly twenty POS vendors build SDKs against - and nothing published states how a new order reaches the POS side, which is exactly where an outbound push would live. Chowly publishes no API reference (/api-docs and /swagger.json 404) and its partner guide circulates privately. Unresolved.

extensibility-webhook-reliability differentiator

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. This depends on extensibility-webhooks-push, still unresolved. "HMAC", "signature", "signing secret", "replay" and "event log" occur zero times across the 204 bodies. The retry behaviour visible in goparrot/chowly-api-client is the CALLER's, not Chowly's - src/utils/common.ts configures axios-retry with "retries: config.maxRetries || 6" and exponentialDelay and a retryCondition that retries POSTs only on HTTP 500-599 - and says nothing about Chowly's delivery guarantees; the repository is a third-party 2021 artifact in any case. Chowly publishes no API reference (api.chowlyinc.com/api-docs and /swagger.json both 404 today) and chowly.statuspage.io/api/v2/components.json lists 45 components with no event, webhook or delivery service among them. The Olo and Square webhook articles describe the PARTNERS' self-service subscription dashboards ("Olo recently released Self-Service Webhook functionality that allows brands to seamlessly manage their webhooks"), not Chowly's outbound semantics. Unresolved.

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

extensibility-menu-write-api differentiator

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

extensibility-data-symmetry differentiator

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. The prior no at grade A rested on goparrot/chowly-api-client as an enumeration of "the whole surface". That repository belongs to GoParrot, Inc. (a third party since acquired by Square), was last pushed 2021-07-20, has 0 stars and no description - a partial implementation of one API as it stood five years ago, and not eligible for grade A. Its claim to completeness is now positively refuted from Chowly's own surfaces: chowly.statuspage.io/api/v2/components.json names five distinct API components (Orders API, Menus API / Menu API, Acknowledge Order API, SDK API, V2 TOOS Partner API) where the wrapper covers only the TOOS v2 partner API, and SDK-Provider-Support-Contacts states "Chowly's POS API has many integration-related features, but these features are only available to POS systems who have built to them", listing roughly twenty POS vendors. No schema, OpenAPI document or reference for any of those APIs is published (/api-docs and /swagger.json both 404 on re-probe today; docs./developer./developers./api.chowly.com fail DNS), so which objects are readable and which writable is not determinable from outside. Note also that customers, employees and inventory are largely not Chowly's objects at all - the menu is mirrored from the POS and loyalty ledgers sit with Punchh/Spendgo - but no document draws that boundary as an API statement. Unresolved.

extensibility-published-rate-limits

2026-08-08 propagation audit. The prior rationale rested partly on github.com/goparrot/chowly-api-client documenting no quotas; that leg is withdrawn, because the repo is a GoParrot (Square-acquired) wrapper last committed 2021-07-20 and an absent method in it proves nothing. It also stated that chowly.help renders no article text, which is no longer true. What carries the cell instead: the claim asserts PUBLICATION, and numeric quotas with throttling headers can only be published in an API reference. Chowly has none - api.chowlyinc.com/api-docs and api.chowlyinc.com/swagger.json both return 404 today, developers.chowly.com and docs.chowly.com do not resolve, chowly.statuspage.io enumerates 45 components with no developer-documentation surface among them, and this record's verified extensibility-public-api-docs finding is that no public API reference, auth spec, sandbox or changelog exists (the partner guide circulates as a private Google Doc; SDK-Provider-Support-Contacts likewise points partners at Google Docs). I additionally full-text searched 310 live chowly.help articles - the 114 sitemap-listed ones plus 196 reachable only from in-article hrefs - for 'rate limit', 'throttl' and 'quota': zero hits. Unlike the attestation claims, this one has no off-surface venue: an API reference is either public or it is not. Published numeric rate limits are affirmatively absent. adversarially verified

extensibility-doordash-preferred differentiator

Upheld on a much stronger source than the one cited. The DoorDash newsroom names the 2026 cohort — Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper — and DoorDash developer docs confirm the gates: 250+ live DoorDash stores, sub-1% order failure and merchant-avoidable cancel rate on rolling 28-day data, plus required SSIO, activation, menu pull with 86 items, and Order Ready Signal. Replace get.doordash.com with about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 and developer.doordash.com. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-01 adversarially verified

extensibility-first-party-delivery-integrations differentiator

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

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

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. adversarially verified

extensibility-payroll-export

No labor data exists in the platform to export.

extensibility-bi-data-warehouse differentiator

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. The comparison point is now documented rather than merely absent: Navigating-the-Restaurant-Control-Center documents the control set that appears on every RCC tile: "The Filters, Expand, and Three Dots icons function more-or-less the same in every tile", where Filters changes "the range of dates/time used in the tile, and the locations used in the tile" and "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." That Download applies to transaction-level tiles - the Orders page's Order Detail table (LOCATION NAME, CUSTOMER NAME, SALES DATE, SUBTOTAL, TIP, SALES TAX, TOTAL, PLATFORM, ERROR OR CANCELLATION REASON, SERVICE TYPE, ORDER STATUS) and the Smart Pricing page's Order Details table - so operators can pull raw rows by hand. Beyond it there is nothing: "S3", "SFTP", "Snowflake", "warehouse", "data export" and "scheduled export" occur zero times in the 204 bodies; chowly.statuspage.io/api/v2/components.json lists 45 components with no warehouse, ETL or export service; https://chowly.com/terms-and-conditions/ has no data-export or portability clause - section 4(e) requires only that on termination the Restaurant "uninstall and destroy all copies of the Software". No file format is even stated for the Download. The one article that enumerates the tile action menu describes itself as "an overview of the basic structures" of the RCC, which the evidence bar excludes as an enumeration, and the RCC's Store Settings page - "allows you to update a large number of settings" - has no published reference article at all. Unresolved.

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

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

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

extensibility-api-versioning-deprecation

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. That crawl is itself the finding here: eight live articles are reachable by neither the sitemap nor any in-article href, and chowly.help/s/sitemap-view-1.xml lists non-public sections including /s/rcc-internal-articles, /s/chowly-pos-api-internal and /s/v2-partners-internal - so an absence argument built on the public help centre is under-powered by construction. Chowly does publish release notes, but for products rather than APIs: /s/product-release-notes, /s/chowly-product-release-notes and the Koala release-note views, whose articles (Koala-iOS-Mobile-Release-v-2-18, Koala-Web-Release-August-9th-2023) are app changelogs with no API surface, version or deprecation content. Re-probed today: https://api.chowlyinc.com/api-docs and /swagger.json both return HTTP 404 while /api/toos/v2/menus returns 401; https://chowly.com/sitemap.xml (167 URLs) contains no developer, docs, changelog or API reference page; trust., security., docs., developer., developers. and api.chowly.com all fail DNS. Partner-facing documentation for a key-gated API is normally distributed directly - SDK-Provider-Support-Contacts shows roughly twenty POS vendors have built to the POS API, so such material demonstrably exists out of public view, and chowly.help carries a /s/chowly-pos-api-internal section for it. Whether a changelog and deprecation policy are published to those partners is undetermined; what is established is only that none is publicly reachable.

extensibility-data-portability-exit differentiator

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

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

reliability-offline-card-auth differentiator

Chowly does not capture card payments.

reliability-offline-decline-liability differentiator

No offline card path, so no liability position published.

reliability-lan-degraded-multi-terminal differentiator

No terminals and no LAN component.

reliability-local-transaction-engine differentiator

No edge server or on-premise engine documented; the architecture is cloud middleware between POS APIs and marketplace APIs.

reliability-offline-kds-printing

No KDS; printing belongs to the POS.

reliability-printer-fallback

No printer routing product.

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

reliability-offline-feature-matrix

Chowly publishes no offline feature matrix of any kind.

reliability-public-status-page

status.chowly.com does not resolve (DNS NXDOMAIN) and no status page is linked from site navigation, footer, or the support entry point. Notable given operators depend on Chowly for live order flow.

reliability-contractual-uptime-sla differentiator

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

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

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

reliability-onsite-install differentiator

Remote SaaS onboarding only; no on-site install or dealer network documented, and no hardware to install.

reliability-menu-build-service differentiator

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

reliability-hardware-replacement-sla

No hardware.

reliability-backup-restore

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. "RPO", "RTO", "disaster recovery" and "restore" occur nowhere in the 204 bodies as Chowly controls; the single "backup" hit is Stripe's two-step-verification backup code in creating-a-stripe-account-for-chowly, which protects the operator's Stripe account. New this pass, and short of the claim: Navigating-the-Restaurant-Control-Center documents the control set that appears on every RCC tile: "The Filters, Expand, and Three Dots icons function more-or-less the same in every tile", where Filters changes "the range of dates/time used in the tile, and the locations used in the tile" and "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." That gives an operator a manual copy of whatever a tile is showing, but a per-tile download of reporting data is not an operator-triggered backup and there is no restore path of any kind. https://chowly.com/terms-and-conditions/ (re-read today) declares itself the entire agreement, disclaims all warranties ("Restaurant accepts the Services \"as is\", with no implied warranty of any kind"), caps liability at the lesser of $500 and three months of fees, contains no data-recovery, retention or restore obligation, and on termination requires only that the Restaurant "uninstall and destroy all copies of the Software"; the privacy policy addresses retention of personal data only. chowly.statuspage.io/api/v2/components.json lists 45 components with no backup or recovery service, and Koala-Incident-Response-Protocol publishes response and resolution targets but no recovery-point or recovery-time objective. The RCC's Store Settings page remains undocumented, so an in-product export or restore control there cannot be ruled out. Unresolved.

reliability-pci-dss-4-attestation

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. No chowly.help article contains "PCI" as a compliance statement; the single "PCI" hit in 204 bodies is a partner name - Koala-iOS-Kiosk-App-Deployment-Kiosk-Kickoff-Requirements: "We work closely with your account managers at Olo, Square, Punchh, and PCI Proxy" - which indicates card data in the kiosk stack is tokenised by PCI Proxy and captured by Square rather than handled by Chowly, and Google Direct Order checkout runs on Stripe. That explains why Chowly might hold no attestation of its own but is not evidence either way about publication. Re-probed today: chowly.com/security/ and /trust/ 404, https://chowly.com/sitemap.xml (167 URLs, re-fetched) has no security, trust, compliance or certifications page, trust.chowly.com and security.chowly.com fail DNS. The prior no cited chowly.com/privacy-policy, whose security section is a generic sentence about industry-standard encryption and SSL - a legal document making no completeness claim about compliance posture, so not an enumeration. AoCs are routinely furnished under NDA and trust centres are commonly hosted on third-party domains a sitemap would never list. On the claim's alternative limb, I attempted the PCI SSC register directly this pass: https://listings.pcisecuritystandards.org/assessors_and_solutions/p2pe_solutions and its API paths all return the PCI Security Standards Council's WordPress marketing shell rather than the listing application, and www.pcisecuritystandards.org/assessors_and_solutions/point_to_point_encryption_solutions 301s, so the register remains unreadable to me and that limb is still untested. Undetermined.

reliability-mfa-role-based-access

2026-08-08 enumeration audit, downgraded from no. Retrieved both cited articles in full. Creating a Restaurant Control Center Account is a three-step support-mediated provisioning procedure and Logging Into the Restaurant Control Center is a three-step sign-in plus password reset; both self-describe as how-tos and neither purports to enumerate the RCC's security configuration. The claim asserts that MFA is ENFORCEABLE - an org-level administrator setting - and a walkthrough of the default sign-in path cannot show whether such a toggle exists; equally, provisioning being handled by a support agent who is given email addresses and location names says nothing about what role or scope that agent sets on the back end, since the operator never sees the admin console. The record's own multi-location-corp-vs-franchisee-roles and multi-location-enterprise-sso are left unknown off these same two articles, and the asymmetry cannot be defended. Chowly publishes no security, trust or compliance page (trust./security. subdomains do not resolve), so there is no venue where the answer would appear. Not established in either direction. adversarially verified

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

reliability-failover-terminal-role differentiator

No terminals.

reliability-cellular-backup

No hardware or connectivity product.

commercial-month-to-month-contract differentiator

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

commercial-no-early-termination-fee differentiator

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

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

commercial-processing-not-bundled differentiator

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

commercial-interchange-plus-published differentiator

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

commercial-rate-increase-clause differentiator

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

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

commercial-module-unbundling differentiator

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

commercial-hardware-purchase-outright

Not applicable - Chowly sells no terminals, KDS screens, or printers. There is also no mandatory lease, which is the merchant-favorable read of the same fact.

commercial-hardware-not-locked differentiator

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

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

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

commercial-export-customer-and-loyalty differentiator

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

commercial-post-termination-export-window differentiator

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

commercial-data-ownership-clause differentiator

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

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

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

commercial-pci-dss-4-controls

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. "PCI", "DSS", "v4.0.1", "SAQ", "MFA", "multi-factor" and "script integrity" produce no compliance content across the 204 article bodies or on https://chowly.com/privacy-policy/, /terms-and-conditions/ and /ccpa/. Privacy policy section 4 remains the only security statement Chowly publishes: data stored "securely, using industry-standard encryption technology" with SSL on web forms. Two first-party facts are new this pass. First, the cardholder data environment is demonstrably other people's: Koala-iOS-Kiosk-App-Deployment-Kiosk-Kickoff-Requirements names PCI Proxy as a partner rep alongside Olo, Square and Punchh ("We work closely with your account managers at Olo, Square, Punchh, and PCI Proxy"), kiosk and web checkout capture through Square (Koala-iOS-Kiosk-App-Deployment-Verifying-Square-Payment-with-Koala), and Google Direct Order settles through Stripe (creating-a-stripe-account-for-chowly) - so Req 6.4.3/11.6.1 payment-page script integrity attaches to those parties' pages, and Chowly documenting nothing does not tell you the controls are absent. Second, on the MFA limb, the RCC's sign-in is now documented end to end and is single-factor (Logging-Into-the-Restaurant-Control-Center: email and password, then the home page), which shows no second factor on a Chowly back-office login but does not establish whether that login is in any cardholder data environment's scope. There is no trust centre: trust.chowly.com and security.chowly.com fail DNS and https://chowly.com/sitemap.xml (167 URLs, re-fetched today) enumerates no security, compliance or trust page. Unresolved.

commercial-soc2-attestation

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. Re-checked today across every public surface: "SOC 2", "ISO 27001" and "trust center" occur zero times in the 204 article bodies; https://chowly.com/sitemap.xml (167 URLs, re-fetched) contains no security, compliance, trust or certifications page and its non-blog set is fully enumerable (eleven /solutions/ pages, eight /agents/ pages, six /pos/ pages, partnerships, legal and company pages); chowly.com/security/ and /trust/ 404; trust.chowly.com and security.chowly.com fail DNS; https://chowly.com/privacy-policy/ section 4 "How secure is your personal information?" names only "industry-standard encryption technology" and "secure socket layer technology (SSL)". That is not enough to assert absence. A privacy policy's security paragraph is the wrong instrument - SSL boilerplate is published by attested and unattested firms alike and the policy never claims to enumerate certifications - and the claim's "or on request" limb cannot be refuted by public silence, since a report can be furnished under NDA to a procurement contact without ever being published. Trust centres are also commonly hosted on third-party domains (Vanta, Drata, SafeBase, Sprinto) that no sitemap would list; I probed one such pattern and got a 403 shell rather than a Chowly page, which establishes nothing. Independent search returns nothing about Chowly and SOC 2 or ISO 27001 in either direction. Unresolved. adversarially verified

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

commercial-wcag-kiosk-accessibility differentiator

No kiosk exists, and no VPAT/ACR or WCAG 2.1 AA conformance claim is published for the branded web ordering or mobile app surfaces.

commercial-dual-pricing-compliant differentiator

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. IMPORTANT TRAP, recorded so it is not mis-scored again: Upcharge-Settings-on-the-Restaurant-Control-Center - a live article reachable by neither chowly.help's sitemap nor any in-article href, retrieved today by slug probe - ends 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 "dual pricing" in the MARKETPLACE sense, a different menu price for delivery than for pickup, and has nothing to do with card-network dual pricing, cash discounting or surcharging. Chowly's documented price levers are (a) the RCC Upcharge field, a percentage applied to "whatever price you have set for your menu items in your POS system", settable for all platforms at once or per individual platform and allowing negatives as discounts, and (b) Smart Pricing, which sets those upcharges automatically ("upcharges are automatically configured using our AI algorithm, which is designed to maximize revenue during busy periods"). Both move the MENU price; neither adds a fee at tender, and across the 204 article bodies "surcharge", "cash discount", "debit", "prepaid" and "BIN" produce no surcharging content, no debit or prepaid exclusion logic, no network cap enforcement and no receipt or menu-board fee disclosure. That is absence, not positive absence. The prior no rested on FAQ-Chowly-s-POS-API-Integration, which bounds what Chowly can do inside the operator's own POS merchant portal and therefore does not enumerate the checkout surfaces Chowly itself runs - Koala web ordering and kiosk on Square, and Google Direct Order on Stripe - which is exactly where a compliant surcharge would be configured. Chowly publishes no checkout fee-configuration reference for either. Unresolved. adversarially verified