Qu

order-capture-floor-plan-editor

Qu's POS page affirmatively states the product is not designed for table-service concepts; no floor plan or section objects exist. https://www.qubeyond.com/ordering/pos · retrieved 2026-08-01

order-capture-seat-level

No table-service model; seat numbering not applicable per vendor's own scope statement. https://www.qubeyond.com/ordering/pos · retrieved 2026-08-01

order-capture-coursing-hold-fire

KDS supports fire on tender, fire on next, fire on fly, and manual fire/suspend. Course assignment from a handheld is not documented. https://www.qubeyond.com/kitchen-solutions/kitchen-display-system · retrieved 2026-08-01

order-capture-split-merge

Seat/table splitting and table merging presuppose table service, which Qu states it does not support. Item-level splitting is undocumented. https://www.qubeyond.com/ordering/pos · retrieved 2026-08-01

order-capture-bar-tab-preauth differentiator

No Qu source addresses card pre-authorization or bar tabs. 'bar tab', 'pre-auth', 'preauth' and 'open tab' return zero matches across all 199 uncited www.qubeyond.com pages, and the check-handling features Qu does describe (Combine Checks merging into a parent check, Check Search filters) carry no tab or open-authorization concept. Qu's /multi-unit-pos-guide comparison table states 'Built exclusively for QSR and Fast Casual' under an 'Industry Focus' row, but that is a market-segment positioning statement in a competitive sales guide, not a feature enumeration or a statement of non-support. Product documentation is behind support.qubeyond.com, which redirects to a login on every path, so the capability is undetermined. adversarially verified

order-capture-transfer-audit

Qu First Gen 2.0 Admin Guide Chapter 8, Section 4 (updated April 2020; Wayback capture 2020-08-06): 'Check Sharing Groups share checks and clock ins/outs among all of the terminals that have been added to that group.' The Enterprise Configuration reference adds 'Allow Peer Refresh: If "true", terminal will refresh display immediately whenever a check is received from another terminal', and the v140 release note records that 'a check can be suspended on one terminal after items have been added' and resumed elsewhere. Checks can also be table-assigned ('Fixed Check Label: The category label on the POS terminal for checks that are assigned to a table'). SHORTFALL: only device-level check sharing is documented; there is no documented server-to-server or table-to-table transfer action, and no audit entry naming both the transferring and receiving employee - Chapter 12: Audit Trail covers configuration changes, not check ownership. Vintage: First Gen 2.0 / Next Gen 3.5 archive, 2020. https://web.archive.org/web/20200806003551/https://support.qubeyond.com/hc/en-us/articles/360001252212-Chapter-8-Printing-First-Gen-2-0- · retrieved 2026-09-03

order-capture-native-handheld

Drive-thru page cites mobile/tablet order-taking beyond fixed terminals; no purpose-built handheld with integrated tableside card capture is documented. https://www.qubeyond.com/ordering/drive-thru · retrieved 2026-08-01

order-capture-offline-order-entry

Qube edge: ordering, payments and kitchen routing continue during outages. Vendor publishes no list of what does not work offline. https://www.qubeyond.com/ordering/pos · retrieved 2026-08-01

order-capture-qr-same-check differentiator

Re-fetched the Online Ordering page: "tableside" is listed as a fulfillment/hand-off mode alongside in-store, curbside and white-label delivery. Shortfall: the page never describes a guest QR scan writing items onto an existing server-opened check rather than creating a new order/ticket, and Qu's own POS page states the product is "not designed for... table-service concepts", which is the model this claim presupposes (an open check with server-entered items already on it). https://www.qubeyond.com/ordering/online-ordering · retrieved 2026-08-04

order-capture-kiosk-first-party differentiator

First-party kiosk (Qu Flex) uses the same single menu as POS; ADA is addressed as feature claims (audio output, adjustable interaction), not a published conformance report. https://www.qubeyond.com/ordering/kiosk · retrieved 2026-08-01

order-capture-drive-thru

Dedicated drive-thru product with 5+ concurrent orders on screen and flexible order injection; order-point/window separation, tandem lanes and pull-forward are not documented. https://www.qubeyond.com/ordering/drive-thru · retrieved 2026-08-01

order-capture-drive-thru-timers

Re-fetched the drive-thru page: "Operators get real-time speed-of-service data through Qu Notify and a real-time Kitchen Intelligence Score so managers can act on bottlenecks before they impact guests," plus a claimed "up to 50% faster service times." Shortfall: this is a rolled-up operational score, not the segmented order/total/window timers tied to individual orders that the claim names — no per-segment timer breakdown or per-order timer report is documented. https://www.qubeyond.com/ordering/drive-thru · retrieved 2026-08-04

order-capture-voice-ai differentiator

The drive-thru page says verbatim: 'Qu's open Intelligent Commerce Platform integrates with AI voice-ordering partners — including ConverseNow and Presto.' That is an explicit third-party integration, not a Qu capability. The researcher's own note concedes 'third-party, not first-party' and then scored it yes anyway. https://www.qubeyond.com/ordering/drive-thru · retrieved 2026-08-01 adversarially verified

order-capture-throttling differentiator

Qu versioned release notes 'December 16th (v140)' (Wayback capture 2021-01-25) enumerate store/group-level platform settings that can be scoped to an order channel: 'Future Order Acceptance Days, Min Max Order Limits, Bucket Scheduling, Kitchen Buffer Lead Time, Print Kitchen Ticket', and state that 'all platform settings use the catering channel as well, allowing the customer to change order limits and timings to be specific to catering'. That establishes per-channel order limits and time-bucket scheduling. SHORTFALL: 'Bucket Scheduling' and 'Min Max Order Limits' appear only as setting names with no documented mechanics, and nothing in the corpus describes automatic quote-time extension when kitchen load crosses a configured threshold. Vintage: Next Gen 3.5-era v140, December 2020; live site silent. https://web.archive.org/web/20210125175255/https://support.qubeyond.com/hc/en-us/articles/360054441371-December-16th-v140- · retrieved 2026-09-03 adversarially verified

order-capture-scheduled-orders

Qu versioned release notes 'December 16th (v140)' (Wayback capture 2021-01-25) document the future-order setting: 'Future Order Acceptance Days... Minimum days - lowest number of days in advance an order can be placed. 0 = same day, 1 = tomorrow... Maximum days - highest number of days in advance an order can be placed', and 'This setting can be set with a context specific to web and/or catering to allow for differing order limits', i.e. per-channel. The same note lists 'Kitchen Buffer Lead Time' and 'Print Kitchen Ticket' among the store/group-level settings that take a per-channel context. SHORTFALL: the release note names 'Kitchen Buffer Lead Time' as a setting without describing the mechanism, so automatic injection of a future-dated order into the make queue at a computed fire time (rather than on receipt) is not documented. Vintage: Next Gen 3.5-era v140, December 2020; not verified against the current Intelligent Commerce Platform. https://web.archive.org/web/20210125175255/https://support.qubeyond.com/hc/en-us/articles/360054441371-December-16th-v140- · retrieved 2026-09-03

order-capture-catering

EZCater is a named direct integration; no native catering quote/deposit/balance flow is documented. https://www.qubeyond.com/ordering/third-party-ordering · retrieved 2026-08-01

order-capture-order-ready-signal differentiator

Re-evidenced 2026-08-12. DoorDash's 18 May 2026 Preferred Integrations Program announcement names Qu in the 2026 cohort ('Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, and UrbanPiper', generated on performance and feature sets as of 8 May 2026), so Preferred status was retained a year after the inaugural 2025 cohort, which named the same ten plus ChowNow. DoorDash's provider-facing DPIP page makes 'Order Ready Signal' one of eight mandatory high-quality features and defines the bar: supporting a feature 'means that you've built and launched the feature and that it has been used by at least one DoorDash store'. Membership therefore asserts Qu shipped an order-ready signal on its DoorDash integration, not merely that DoorDash asks for one. Shortfall: the mechanism is undocumented -- no Qu-published page shows the signal is emitted automatically from POS or KDS state rather than a manual tap. Qu's own pages stop short: /kitchen-solutions/order-status is guest-facing ('shows guests the real-time progress of their order -- placed, in-prep, and ready'; 'pulls state changes directly from Qu KDS'), and /ordering/third-party-ordering says only 'bi-directional integrations sync with third-party providers in real time' and 'syncs automatically to Qu's KDS and Order Status to keep guests and drivers informed'. DoorDash's per-partner comparison tool renders no provider names in HTML, and no coverage beyond DoorDash (Uber Eats, Olo) is documented. Qu's API hosts are offline and its knowledge base is behind SSO. Prior note's quotation from the merchant criteria page ('Notify Dashers as soon as an order is ready for pick-up directly through your integration') was dropped: merchants.doordash.com/en-us/preferred-integrations has been redesigned and now carries only the bare bullet 'Order ready signals'. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-12 adversarially verified

order-capture-void-comp-controls

Qu First Gen 2.0 Admin Guide Chapter 6: Configuration (updated April 2020; Wayback capture 2020-08-08) documents operator-defined reason codes under System Lookups - 'add your own reasons for voiding a check or discounting an item... Void Reasons, Time Entry Reasons, Return Reasons, Paid In/Out Reasons, Discount Reasons'. Reason capture is enforced per-discount ('Require to Enter Reason for Discount?' in the discount definition) and per-void at the POS ('If required, you will be prompted for a void reason. Select the reason, and Tap Void/Remove Item', Next Gen 2020). Manager gating: 'Some discounts may be configured to require manager approval' (First Gen), and a 2020 Next Gen article gates restricted actions by job title so 'the POS will present a manager prompt to the cashier when performing restricted actions'. Exception reporting: the Qu Reports Quick Guide (Next Gen, Sept 2020) lists 'Voided Items - Displays all voided items by an employee', 'Refunds - Lists all refunded checks by an employee', a 'Discounts' report, and 'Labor Red Flag - ...useful for analyzing whether the store or employee uses specific actions (e.d voids) too often'. Vintage: documented for First Gen 2.0 and Next Gen 3.5 in 2020, not verified against today's Intelligent Commerce Platform; these are basic POS controls unlikely to have been removed. https://web.archive.org/web/20200808111044/https://support.qubeyond.com/hc/en-us/articles/360001267211-Chapter-6-Configuration-First-Gen-2-0- · retrieved 2026-09-03 adversarially verified

menu-pricing-nested-modifiers

"Unlimited modifiers and layered options" claimed; nesting depth and min/max/forced-selection semantics not documented. https://www.qubeyond.com/ordering/online-ordering · retrieved 2026-08-01

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

Qu First Gen 2.0 menu-build article (Wayback capture 2020-08-13): ingredient groups and their ingredients are attached to the item and priced there - 'Add the ingredients by clicking "Add Ingredient", and add the title and the associated price (if needed)' - and 'existing ingredient group, ingredients, and modifiers can be associated with an item', so one shared modifier can carry a different price on a different parent item without being duplicated. Pricing is also multi-dimensional by price tier: 'At least one price tier is needed for pricing of modifiers, ingredients, and prep instructions.' SHORTFALL: the second axis is the price tier (meal period / location / daypart), not the parent item's selected size - item sizes are 'Portions' ('Portions allow the addition of item sizes and prices... large fries at $2.00 and small fries for $1.00'), and no per-portion modifier price or modifier-by-size matrix is documented. Vintage: First Gen 2.0, 2018-2020. https://web.archive.org/web/20200813234817/https://support.qubeyond.com/hc/en-us/articles/360001492972-How-do-I-add-a-Menu-Menu-Items-Ingredients-and-Prep-Instructions-First-Gen-2-0- · retrieved 2026-09-03

menu-pricing-fractional-placement differentiator

Read all 199 uncited www.qubeyond.com pages, the Winter 2026 release highlights (fetched live today), the Blaze Pizza CTO piece and the Blaze partnership announcement. 'fractional', 'half and half' and 'half-and-half' are absent from the corpus; 'topping' appears three times, all in customer-brand descriptions. The nearest item is Winter 2026's 'Portion Updates (Portion Propagation & Hidden Defaults): Parent items can dynamically update child item portions' — a combo/child-item portion inheritance feature, not sectioned placement with per-section pricing. Qu runs Blaze Pizza, a build-your-own pizza chain, which is affirmative reason to doubt absence. Sectioned modifier placement is menu-configuration behaviour documented in an admin guide, and Qu's operator documentation is unreachable. Undocumented, not absent.

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

Same corpus and same negative searches as menu-pricing-fractional-placement: no half-pricing rule language of any kind on any Qu page, including the Winter 2026 release which is the most granular pricing-feature enumeration Qu publishes ($0 price detection, penny rounding, portion propagation, bulk item assignment). A choice among higher-half/average/fractional-topping pricing is a per-item configuration option that lives in a menu-admin guide, never on a marketing site, so the silence carries no weight for this cell. Qu's reference pizza customer (Blaze) further argues against hardening this into an absence.

menu-pricing-topping-quantity-tiers

Qu First Gen 2.0 menu-build article (updated April 2020; Wayback capture 2020-08-13) documents modifiers ON an ingredient, which is exactly the quantity/intensity tier mechanic: 'To add ingredient modifiers such as Extra cheese, 4 sugars, light mayo, etc: After the ingredient is added click "Add Modifier." Add a title, and price (if needed) for the modifier.' Chapter 1 gives the same pattern ('Espresso shot is an ingredient but multiple shots can be added. 1 shot, 2 shot, etc.'; 'Ingredients may be modified for example 1 slice, 2 slices, 3 slices'), so a tier is a distinct priced object rather than the ingredient added twice. SHORTFALL: each tier carries its own absolute price entered per price tier; no configurable price MULTIPLIER per tier is documented anywhere in the corpus. Vintage: First Gen 2.0, 2018-2020 documentation; live site silent. https://web.archive.org/web/20200813234817/https://support.qubeyond.com/hc/en-us/articles/360001492972-How-do-I-add-a-Menu-Menu-Items-Ingredients-and-Prep-Instructions-First-Gen-2-0- · retrieved 2026-09-03

menu-pricing-size-style-matrix differentiator

Qu First Gen 2.0 menu-build article (Wayback capture 2020-08-13) documents one priced variant axis on the item - 'Portions allow the addition of item sizes and prices. For example, large fries at $2.00 and small fries for $1.00. Click on "Add Portion", create the title for the specific portion and set the Price' - and a second, separately priced axis for preparation style: 'Prep instructions, or modifiers, describe an item. For example, temperature of beef - well-done, medium, rare... Now add the Prep instruction by clicking "Add Prep Instruction", Add the title and the associated price (if needed).' SHORTFALL: the two axes compose additively (portion price plus prep-instruction price); no size x style grid with a per-cell base-price override is documented, and 'Portions are currently linked and will be changed for every item where the portion has been used'. Vintage: First Gen 2.0, 2018-2020; live site silent. https://web.archive.org/web/20200813234817/https://support.qubeyond.com/hc/en-us/articles/360001492972-How-do-I-add-a-Menu-Menu-Items-Ingredients-and-Prep-Instructions-First-Gen-2-0- · retrieved 2026-09-03

menu-pricing-included-allowance differentiator

No included-modifier allowance, free-topping count, or overage-charging language anywhere in the 199-page corpus. The closest first-party text is Winter 2026's portion-propagation entry, whose stated benefit is that it 'ensures accurate upcharges, and simplifies complex combo logic' — upcharge machinery exists, but nothing establishes an included-count-then-charge-overage rule or substitution credit policy, which is exactly the kind of per-item configuration Qu's unreachable admin documentation would define. The marketing surface would not carry it either way.

menu-pricing-combos

Kiosk upsell prompts suggest add-ons and combos; combo construction with swap deltas and auto-conversion is not documented. https://www.qubeyond.com/ordering/kiosk · retrieved 2026-08-01

menu-pricing-upsell-prompts differentiator

AI-driven upsell prompts at kiosk checkout and channel-specific upsells claimed, with ~22% AOV lift cited; per-prompt attach-rate reporting not documented. https://www.qubeyond.com/ordering/kiosk · retrieved 2026-08-01

menu-pricing-86-propagation

Real-time item 86ing and item availability checks are mandatory DPIP capabilities and Qu is a 2026 partner; no propagation latency is published. https://developer.doordash.com/en-US/docs/marketplace/overview/getting_started/preferred_integrations_new/ · retrieved 2026-08-01

menu-pricing-countdown-auto-86 differentiator

Fall 2025 release: "Notify Item Availability: Manage in and out of stock items anywhere. Mark items in/out of stock from your phone and set a 'Revive Date' to auto-restock later." The POS page adds that "Price changes, modifiers, and 86'd items update everywhere simultaneously with no manual sync required." Shortfall: the 86 is operator-initiated. The scheduled auto-restore half of the claim is evidenced (Revive Date); the automatic half is not — no per-item countdown or par count that decrements on sale and 86s the item at zero appears anywhere on qubeyond.com (no hit for 'countdown', 'par level' or 'depletion'). https://www.qubeyond.com/resource-center/qus-fall-2025-product-release-highlights · retrieved 2026-09-03

menu-pricing-dayparting

Menu page cites AI-powered demand and daypart analysis and instant propagation of LTO/price changes; explicit scheduled activate/deactivate by local timezone is not documented. https://www.qubeyond.com/management/unified-menu-management · retrieved 2026-08-01

menu-pricing-channel-price-books

The strongest verbatim on the cited page is 'Delivery orders may carry a fee surcharge, while kiosk may feature upsell-only items.' A delivery fee surcharge and channel item visibility are not an item-level price book per channel. Directionally right, but a 'yes' on marketing illustration rather than a documented pricing model overstates it. https://www.qubeyond.com/management/channel-management · retrieved 2026-08-01 adversarially verified

menu-pricing-dual-pricing differentiator

Same corpus-wide silence as payments-dual-pricing, and this cell's object is further from the contract: item-level two-price storage applied consistently across POS, kiosk and online ordering with receipt printing is a menu-engine behaviour that neither a payments contract nor a marketing site would document. The /modules page, which might have enumerated pricing capabilities, is an unpublished Webflow template consisting of 'Placeholder Name / Job Title' rows and one boilerplate paragraph.

menu-pricing-versioning-effective-dates differentiator

Fall 2025 release, POS item 1: "A new set of icons shows each menu's status, version, and update schedule—all available through the POS... you can instantly see what's live, what's pending, and what needs attention." So menus are versioned and changes are scheduled ahead of going live. Shortfall: no evidence of a preview-before-publish step, and none of rollback to a prior published version — 'preview', 'rollback' and 'roll back' return zero hits across the whole site. https://www.qubeyond.com/resource-center/qus-fall-2025-product-release-highlights · retrieved 2026-09-03

menu-pricing-franchise-hierarchy differentiator

Corporate standards enforced centrally with "local overrides within approved parameters"; field-level lock governance is not documented. https://www.qubeyond.com/management/brand-franchise-management · retrieved 2026-08-01

menu-pricing-allergen-nutrition

Qu's store-group inheritance model lists the configurable menu attributes as "Menus — Dynamic items, prices, dietary needs, allergens", so allergen data is held per item in the menu database; the Fall 2025 release adds kiosk-side surfacing — "Guests can filter menu items by Vegan, Vegetarian, or Gluten-Free options, depending on what the brand sets up." Shortfall: allergen/dietary tags only. No evidence of stored per-item nutrition values, and none at all of deriving nutrition from linked recipe components; publication of allergen data to third-party marketplace menus is likewise not stated. https://www.qubeyond.com/resource-center/dynamic-stores-transforming-menu-management-to-serve-a-new-decade · retrieved 2026-09-03

menu-pricing-recipe-linkage differentiator

Re-evidenced 2026-08-08 after the cited /products/ page began redirecting to the homepage. Qu's product line-up is enumerated in full on the live site (the Platform Solutions nav carried on /platform and every section index, matching the sitemap's product URL tree exactly): Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Qu Pay, and Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify Mobile Insights, Unified Data & Reporting). No inventory or recipe module exists. The menu module's own Features list is 'Cross-channel menu management / Single operations and menu database / Dynamic store groupings and brand administration / Deep item, pricing, and promotional customization / AI-connected demand and daypart intelligence / Single API structure for clean, consistent data', and it describes its database as 'Every item, price, and modifier lives in a single menu database' - items, prices and modifiers, with no bill of materials, no depletion and no theoretical cost. Recipe costing is partner-delivered: the integrations directory's 'Back of House + Labor' category lists MarketMan, Restaurant365, Crunchtime, SynergySuite, COGS-Well and Decision Logic. https://www.qubeyond.com/management/unified-menu-management · retrieved 2026-08-08 adversarially verified

menu-pricing-3p-menu-push

Direct certified marketplace integrations with real-time menu sync; real-time menu syncing and detailed order error reporting are DPIP requirements Qu meets. https://www.qubeyond.com/ordering/third-party-ordering/ · retrieved 2026-08-01

menu-pricing-dynamic-pricing

Qu claims "dynamic pricing across all delivery platforms"; rule engine and floor/ceiling guardrails are not documented. https://www.qubeyond.com/resource-center/qu-named-first-excellent-pos-in-doordashs-new-preferred-integrations-program · retrieved 2026-08-01

payments-processor-choice differentiator

Status page lists FreedomPay and WorldPay as integrated payment providers; Aurus is a listed payments partner; online ordering supports "Qu Pay or third-party providers." https://status.qubeyond.com/ · retrieved 2026-08-01

payments-published-rates differentiator

No card-processing rates published anywhere on qubeyond.com; Qu Pay page is entirely qualitative. https://www.qubeyond.com/payments/qu-pay · retrieved 2026-08-01

payments-dual-pricing differentiator

Read all three legal documents end to end and grepped the full 199-page uncited corpus: zero occurrences of 'dual pricing', 'cash discount' or any two-price language. The Adyen-for-Platforms contract is the payments contract behind Qu Pay but its subject is Adyen's acquiring, settlement, reserve and liability terms; a POS feature that stores two prices per item and prints both on the guest check is a menu/pricing-engine behaviour that this contract would not document even if it existed. Qu's operator documentation (support.qubeyond.com) is walled and the archived copy was already mined without answering. Silence here is not load-bearing.

payments-surcharge-guardrails differentiator

The Adyen contract is the only document in the set that touches surcharging, and it does so once, for one country, as a merchant obligation rather than a platform control: 'Users in Australia will not impose a surcharge or any other fee on the relevant Payment Methods that exceeds the amount said User pays for that Payment Method as a percentage of the total price' (15.5.2). That places cap compliance on the operator and describes no BIN/product-code detection, no debit or prepaid exclusion, and no per-location toggle — but it is Adyen's clause about Australian regulation, not a statement about whether Qu's POS ships a surcharging engine for the US. Wrong object to settle the cell; no US surcharge language exists anywhere in the corpus.

payments-emv-nfc

Qu's Third Party Terms (the Adyen payment terms incorporated into Qu's Master SaaS Agreement) price "EMV-compliant payment terminal devices" as a one-time cost (17.4) and define a Payment Device as equipment that reads the card, registers the Shopper's approval and encrypts the Payment Details (18). Qu's Fall 2025 release also adds "Real-time payment connectivity visibility across EMV devices" for Aurus, FreedomPay, TriPOS and Verifone terminals. Shortfall: EMV chip acceptance is established, but nothing Qu publishes states that its terminals accept NFC contactless, Apple Pay or Google Pay — the only contactless/Apple Pay/Google Pay text on the site describes FreedomPay's own platform in a partnership press release, not Qu's terminal fleet. https://www.qubeyond.com/third-party-terms · retrieved 2026-09-03

payments-softpos-tap-to-pay differentiator

Zero hits for 'tap to pay', 'softpos' or phone-as-terminal across the legal set and all 199 pages. The Adyen contract is deliberately payment-method-agnostic — it says supported Payment Methods 'may change from time to time' and are set between Adyen, Qu and the schemes — so acceptance hardware is outside its subject. The Qu Pay launch release names the channels served ('point-of-sale, kiosks, drive-thru, web, and mobile') but that is a marketing selection, not an enumeration of acceptance methods.

payments-pay-at-table

Vendor states the platform is not designed for table-service concepts; no pay-at-table handheld product is offered. https://www.qubeyond.com/ordering/pos · retrieved 2026-08-01

payments-qr-guest-pay differentiator

Qu's only documented guest-phone QR flow is an ordering entry point, not scan-to-pay on an existing check: 'Tableside ordering allows guests to place and pay for their orders directly from their mobile devices while seated at the table, using a unique QR code to access the menu. The order is sent directly to the kitchen with the table number' — a feature of Qu's Online Ordering system, with curbside built the same way ('scanning a QR code displayed at the curb'). The guest authors and pays for their own order; no source describes a server-fired POS check being surfaced by a scan, viewed, paid and auto-closed. Whether Qu supports pay-the-check QR is undetermined on the open surface. adversarially verified

payments-tip-adjust

Qu 'Next Gen 3.5' help article (updated April 2020; Wayback capture 2020-08-09) documents post-close tip adjust: check search, 'Select Payment to Adjust Tip (There could be more than one credit card on the check...)', enter the tip. It states the adjust window: 'Generally tips may only be adjusted on the same date.' The First Gen 2.0 Enterprise Configuration reference documents the pre-auth half - 'Require Credit Card Authorization: If set to "true", the terminal prints an authorization slip with tip line for credit card transactions... In Table Service mode, authorization slips are always printed for credit cards' - and a 2020 article gates tip adjust by job title so it 'will require manager approval to apply'. SHORTFALL: no on-device/customer-facing tip prompt on the EMV terminal is described in either generation's EMV payment article, and no manager screen listing unadjusted tips is documented (only a Labor 'Tip' report of tips collected by employee). Vintage: First Gen 2.0 / Next Gen 3.5 archive, 2020; live marketing site silent. https://web.archive.org/web/20200809112540/https://support.qubeyond.com/hc/en-us/articles/360042453371-How-Do-I-Adjust-a-Credit-Card-Tip-Next-Gen- · retrieved 2026-09-03

payments-tip-pooling differentiator

7shifts' "Tip Pooling for Qu POS" doc (updated 2026-06-24) states "Qu automatically transfers sales, payment, and tip information to 7shifts" and requires per-employee order/sale assignment in Qu POS, establishing per-employee tip capture in Qu. Shortfall: the pooling/distribution rule engine (by hours worked, sales, role percentage, or points) lives in 7shifts' separately licensed Tip Pooling module — "within 7shifts, the distribution of tips and gratuities among employees is automated" — not in Qu itself, which has no published tip-pool ledger. Same source/finding as labor-tip-pooling-rules and labor-tip-distribution-audit-trail. https://kb.7shifts.com/hc/en-us/articles/35540967177875-Tip-Pooling-for-Qu-POS · retrieved 2026-08-04

payments-offline-store-and-forward differentiator

POS page FAQ: "Does Qu POS work if the internet goes down? Yes. Qu POS processes transactions on Qu Business Edge (Qube), the on-site intelligence hub in every restaurant. Ordering, payments, and kitchen routing continue uninterrupted during connectivity outages, and data syncs to the smart cloud automatically when the connection is restored." Shortfall: offline card capture is asserted only as marketing on a feature page (grade C, below the grade-A/B floor a differentiator yes requires); no published documentation names a store-and-forward mechanism or any configurable per-transaction or cumulative offline limit. https://www.qubeyond.com/ordering/pos · retrieved 2026-09-03 adversarially verified

payments-offline-decline-liability differentiator

The claim is that the vendor PUBLICLY documents offline-decline loss allocation and a post-reconnect failure report. Qu's public offline-payments material — the Qu Business Edge page ('Full transaction processing continues... Sync resumes automatically with no manual intervention', 'No data loss during outages') and the 'Solving for In-Store Stability with Edge Computing' post ('offline payment acceptance') — promotes offline card acceptance without a word on who bears a decline on reconnect or any failed-offline-payments report. The help centre is login-gated (support.qubeyond.com 302s to Document360) and no public MSA/ToS exists, so the public documentation this claim requires verifiably does not exist. https://www.qubeyond.com/qu-business-edge · retrieved 2026-08-04

payments-gift-cards

Gift card is partner-delivered: Paytronix gift + loyalty integration across in-store, drive-thru, kiosk, mobile and web; Valutec/Worldpay gift processing appears on the status page. https://www.globenewswire.com/news-release/2026/06/23/3316041/0/en/paytronix-and-qu-further-integration-enabling-advanced-omnichannel-ordering-and-menu-management.html · retrieved 2026-08-01

payments-house-accounts

Qu Next Gen 3.5 article (October/November 2020; Wayback capture 2020-11-28): 'Customers often use offline credit payment types to tender third-party DSP (DoorDash, Uber Eats, etc.), House Account, and other types of orders. However, managers would like to restrict their cashiers from using these without manager approval because they are not tied to a real tender type (cash, credit, or gift).' So a house account exists as an operator-created tender. SHORTFALL: it is only a payment type. The First Gen 2.0 Enterprise Configuration reference enumerates the payment-type categories available - 'Cash, Offline Credit, Check, Hotel Room Charge, Credit, Gift Card, GEM Room Charge, Marriott Room Charge, EmployeeMeal, Electronic Payment, Opera, StayNTouch' - with no house-account ledger among them, and no per-account credit limit, running balance, or statement/invoice generation is documented anywhere in the corpus. Vintage: First Gen 2.0 / Next Gen 3.5 archive, 2020. https://web.archive.org/web/20201128162138/https://support.qubeyond.com/hc/en-us/articles/360051880331-How-do-I-Prevent-Cashiers-from-Applying-Offline-Credit-Payment-Types- · retrieved 2026-09-03

payments-split-tender

Qu 'Next Gen 3.5' help article (updated April 2020; Wayback capture 2020-08-09): 'From the Payments screen, press the + number widget until you reach the number of desired payments... The amount due for each payment will automatically divide equally by the number of payments selected. To change the amount of a payment, touch the "Due" box and enter the desired amount. The other payments will automatically adjust. There is no limit to the number of payments or the combination of payment types.' Even shares, arbitrary amount and no cap are all explicit; the First Gen 2.0 Payments guide adds the same ('You may split check payments by any number of increments and by multiple methods') and a separate First Gen article documents splitting items between seats ('Seating allows you to split the items on a check between the customers on the check'). Vintage caveat: this is the archived 2019-2021 support site for First Gen 2.0 / Next Gen 3.5, not the current Intelligent Commerce Platform, and the live site is silent; multi-tender splitting is a basic POS mechanic unlikely to have been removed. https://web.archive.org/web/20200809111311/https://support.qubeyond.com/hc/en-us/articles/360041247211-How-do-I-add-an-Additional-Tender-Next-Gen- · retrieved 2026-09-03

payments-refund-void-controls

Qu Next Gen 3.5 article (October/November 2020; Wayback capture 2020-11-28): job-title switches in Enterprise Intelligence disable 'Perform Paid in and Paid Out', 'No Sale', 'Claim Till', and 'Once this change takes effect, the POS will present a manager prompt to the cashier when performing restricted actions'; sibling 2020 articles do the same for offline credit payment types and for Tip Adjust, and manager approval can be given by swiping a manager mag card. Discounts likewise: 'Some discounts may be configured to require manager approval.' SHORTFALL: the corpus documents role gating explicitly for no-sale, paid in/out, till claim/close, offline tenders and tip adjust - not for refunds or voids - and no immutable log identifying the APPROVING manager is documented. Chapter 12: Audit Trail covers admin-side configuration changes ('a detailed activity history of changes occurring within Qu... tracked based on Date, Employee, Module, Location'), while the Voided Items and Refunds reports name the acting employee only. Vintage: 2020 Next Gen 3.5 archive; live site silent. https://web.archive.org/web/20201128163422/https://support.qubeyond.com/hc/en-us/articles/360051880871-How-do-I-Prevent-a-Cashier-from-Performing-Manager-Related-Till-Functions-No-Sale-Paid-In-Out-and-Claim-Close-Till- · retrieved 2026-09-03 adversarially verified

payments-chargeback-tooling differentiator

The contract walks chargebacks at length (15 occurrences, a dedicated Clause 7, plus rolling-reserve and set-off machinery) and establishes that the chargeback counterparty is Adyen and the schemes, not Qu: the merchant must cooperate with 'inquiries by Processor, Acquirers, and/or Scheme Owners with respect to Chargebacks', and scheme requests about a specific Transaction are 'forwarded by Processor to Platform in electronic form' (3.4), with Clause 5 routing all first-line communication through Qu. That establishes a correspondence channel through the platform, which is consistent with either an in-product dispute dashboard or an email chase, and distinguishes neither. A liability-allocation contract would not describe merchant UI, so its silence on an open-dispute list and evidence submission is not load-bearing; the subject of any such tooling may in any case be Adyen rather than Qu.

payments-card-on-file differentiator

No occurrence of 'tokeniz', 'vault', 'card on file' or 'recurring' anywhere in the legal set or the 199 pages. The contract does settle the claim's tail clause — 4.3 contractually forbids the merchant from holding PANs: 'User will not copy, capture, or intercept Payment Details such as credit card numbers, card verification or CVM codes, or PIN codes' — but the head clause, a tokenized card-on-file guest profile reusable across online, phone and in-store, is unaddressed, and if it exists the token vault would be Adyen's rather than Qu's. Head clause unmeasured, so the cell does not resolve.

payments-payout-timing differentiator

Qu Pay claims "on-demand settlements replace standard payout schedules" and unified payout reporting; no deposit schedule is published. https://www.qubeyond.com/payments/qu-pay · retrieved 2026-08-01

payments-multi-entity-routing differentiator

Third Party Terms 7: "Adyen will Settle Customer Funds directly to each Customer on a gross basis ... meaning 100% of Transaction proceeds will be Settled daily", and "The Settlement of the Customer Funds will be exclusively made pursuant to Customer's binding Settlement instructions"; each legal entity is separately KYC'd and onboarded (3). The Qu Pay page markets "unified payout reporting across every location". Shortfall: the published terms achieve per-entity settlement by onboarding each legal entity as its own merchant of record rather than by routing one account's funds to multiple bank accounts, and no published source shows per-location bank-account routing configured inside a single merchant account. https://www.qubeyond.com/third-party-terms · retrieved 2026-09-03

payments-p2pe-pci4

Qu publishes a PCI DSS v4.0.1 compliance guide covering its payment stack. On in-person payments it states the terminals are "all validated and listed P2PE-approved solutions" with cardholder data "encrypted from the point of interaction until it reaches Adyen's secure decryption environment", that the processor is "a PCI DSS Level 1 Service Provider, with PCI DSS compliance assessed by an independent Qualified Security Assessor (QSA) annually", and instructs merchants to obtain the Service Provider's Attestation of Compliance. Shortfall: the guide describes the processor's (Adyen's) attestation, not a Qu-issued AoC or P2PE listing, and P2PE is one of two options — the default in-person integration is E2EE, not validated P2PE. https://www.qubeyond.com/pci-dss-compliance-guide · retrieved 2026-09-03

kitchen-station-routing

KDS offers load balancing with "flexible order routing, manual or intelligent rules-based" across production and fulfillment stations. https://www.qubeyond.com/kitchen-solutions/kitchen-display-system · retrieved 2026-08-01

kitchen-expo-consolidation

Item state syncs across production and fulfillment KDS stations in real time; a distinct expo screen with all-stations-bumped completion gating is not explicitly documented. https://www.qubeyond.com/kitchen-solutions/kitchen-display-system · retrieved 2026-08-01

kitchen-course-firing differentiator

KDS feature page lists 'Mulitple Firing Modes: Fire on tender, fire on next, fire on fly, and manual fire/suspend to fit any ordering or kitchen workflow.' A 2021 Qu post expands the same four modes (fire on fly / on next / on tender / manual fire). Shortfall: the mechanism is a per-item release rule plus a manual fire/suspend; nothing on qubeyond.com describes assigning items to named courses, nor firing a held course on demand from a server terminal, handheld or expo screen. https://www.qubeyond.com/kitchen-solutions/kitchen-display-system · retrieved 2026-09-03 adversarially verified

kitchen-prep-time-pacing differentiator

Read Qu's Smart Kitchen Vision enumeration ('Reimagined KDS', 'Order Ready Board', 'AI-generated promised ready times', 'Production Optimization Board', 'Smart Expo', 'Smart Edge'), the Intelligent Commerce Platform launch release ('production forecasting and dynamic kitchen load balancing to improve makeline speeds and throughput'), and the Fall 2024 / Winter 2025 / Fall 2025 / Winter 2026 release highlights. Qu's promised-ready-time feature factors in 'prep needs' at the order level and Winter 2026 adds 'Expanded item-level production states', but nothing describes operator-configurable per-item cook times or staggering item start/display so an order's items finish together. These six-bullet 'what's inside' lists are marketing selections, not exhaustive KDS feature enumerations, so their silence on coursing does not settle the cell.

kitchen-order-throttling differentiator

No Qu source describes kitchen load throttling. The only adjacent material is a marketing bullet on the Oct 9 2024 'Qu's Smart Kitchen Vision' announcement — 'AI-generated promised ready times — improves delivery time accuracy by factoring in all channels, labor, and prep needs' — whose stated purpose is delivery-ETA accuracy, with no operator-configurable order-volume or ticket-time threshold, no gating condition and no pacing or delayed release of incoming digital orders. 'throttl' appears zero times across all 199 uncited www.qubeyond.com pages, and the ICP launch release mentions only 'production forecasting and dynamic kitchen load balancing to improve makeline speeds'. A predictive ready-time estimator is a different capability from a load-triggered throttle; undetermined on the open surface. adversarially verified

kitchen-channel-pause-propagation differentiator

Channel Management pauses third-party integrations and re-syncs menus from one dashboard; item 86ing to DoorDash is a DPIP requirement Qu meets. https://www.qubeyond.com/management/channel-management · retrieved 2026-08-01

kitchen-order-ready-callback differentiator

Order ready signal is a required DPIP capability; Qu KDS syncs automatically to Qu Order Status and third-party channels. https://developer.doordash.com/en-US/docs/marketplace/overview/getting_started/preferred_integrations_new/ · retrieved 2026-08-01

kitchen-bump-bar-hardware

Qu blog on its KDS: 'Qu KDS also supports order navigation and bump bar functionality, allowing staff to move through orders, make check-level edits, and undo previous actions.' Shortfall: bump-bar support is asserted in a marketing post only; no supported bump-bar or programmable-keypad models are named anywhere on qubeyond.com, and support.qubeyond.com is login-walled. https://www.qubeyond.com/resource-center/qus-kds-delivering-a-holistic-view-of-your-ordering-production-capabilities · retrieved 2026-09-03

kitchen-all-day-counts

Fall 2025 release highlights, item 10: 'KDS Item Count View: Real-Time Kitchen Insights — Kitchen teams can now see, at a glance, how many of each item or ingredient needs to be prepped... a clear view of exactly how many items need to hit the grill or fryer.' The companion Fall 2025 overview repeats 'Real-time kitchen item counts'. Per-modifier aggregation is not stated. https://www.qubeyond.com/resource-center/qus-fall-2025-product-release-highlights · retrieved 2026-09-03

kitchen-sla-alerts

Qu Notify raises configurable alerts on service-time thresholds and a Kitchen Intelligence Score; per-station color escalation on the KDS is not documented. https://www.qubeyond.com/management/notify-mobile-insights · retrieved 2026-08-01

kitchen-printer-fallback differentiator

The string 'printer' does not occur once in the entire 1.85 MB uncited corpus, nor in the Winter 2026 release, nor in the two unlinked legal documents. That is a striking silence but it is not load-bearing here: Qu's published resilience story is scoped to connectivity (Business Edge keeps ordering, payments and kitchen routing running when the WAN drops), and device-level ticket failover to a backup screen or printer is a station-configuration behaviour that would be documented in an operator guide, not on a marketing site or in release notes. Qu's operator documentation is walled and the archived copy is exhausted, so the behaviour can be neither confirmed nor ruled out.

kitchen-offline-operation differentiator

Re-fetched 2026-08-02. The page states core services execute on-site - "POS, payments, order routing, and kitchen workflows" - with "uninterrupted operations with offline mode", "system state is preserved locally" and "sync resumes automatically with no manual intervention". Shortfall: this is contingent on deploying the Qu Business Edge (Qube) on-premise appliance, which Qu markets as a distinct offering with unpublished packaging and price; it is not established as a property of the base cloud platform. Nothing documents KDS ticket queueing, bump-state retention, or reconciliation on reconnect. Qu publishes no publicly retrievable product documentation: support.qubeyond.com (the 'Qu Campus' Document360 portal) redirects to a login, and both qu-api.qubeyond.com and qu-pos-api.qubeyond.com return HTTP 403 behind a mismatched TLS certificate. No grade A/B evidence is obtainable, so a differentiator 'yes' cannot stand. https://www.qubeyond.com/qu-business-edge · retrieved 2026-08-02 adversarially verified

kitchen-item-build-screens differentiator

"Dynamic order cells" with detailed order info; recipe-step or portioning build screens are not documented. https://www.qubeyond.com/kitchen-solutions/kitchen-display-system · retrieved 2026-08-01

kitchen-pizza-fractional-display differentiator

Qu's KDS is described as 'color-coded, fully configurable, displaying every order detail including modifiers across every channel in real time' (Smart Kitchen Vision), and Winter 2026 adds collapsible KDS cells and menu/modifier images at POS — but nothing addresses how a sectioned or fractional topping is rendered on the make-line. Make-line rendering of halves and quarters is a screen-behaviour detail that only operator documentation would show, and Qu ships a build-your-own pizza brand (Blaze), so an absence verdict here would be manufacturing.

kitchen-recall-refire

Qu's KDS post says bump-bar navigation lets staff 'move through orders, make check-level edits, and undo previous actions', and that KDS cells use 'different colors for new, modified, voided, and resurrected orders' — a resurrected (recalled) order state. Shortfall: the described undo/resurrect is at check level; no per-item refire or ticket reprint without re-entering the order is documented. https://www.qubeyond.com/resource-center/qus-kds-delivering-a-holistic-view-of-your-ordering-production-capabilities · retrieved 2026-09-03

kitchen-order-modification-alerts differentiator

Staff can update submitted orders directly on the KDS with item state syncing in real time; explicit visual flagging of added/changed/removed items is not documented. https://www.qubeyond.com/kitchen-solutions/kitchen-display-system · retrieved 2026-08-01

kitchen-guest-ready-notification differentiator

Re-fetched 2026-08-02. Qu Order Status shows guests the "real-time progress of their order - placed, in-prep, and ready", pulling "state changes directly from Qu KDS", with layout, co-branding, orientation and multilingual header options. Shortfall: this is an in-store display only - the page contains no SMS, text, push, or pager notification to the guest's own device, so the guest must be present and watching a screen. Qu publishes no publicly retrievable product documentation: support.qubeyond.com (the 'Qu Campus' Document360 portal) redirects to a login, and both qu-api.qubeyond.com and qu-pos-api.qubeyond.com return HTTP 403 behind a mismatched TLS certificate. No grade A/B evidence is obtainable, so a differentiator 'yes' cannot stand. https://www.qubeyond.com/kitchen-solutions/order-status · retrieved 2026-08-02 adversarially verified

kitchen-waste-logging

Re-evidenced 2026-08-08 after the previously cited /products/ page went dead. The live Smart Kitchen Solutions index enumerates exactly three kitchen products - KDS ("brings clarity and control to high-volume kitchens"), Order Status, and Energy & Equipment Intelligence - and names no waste, spoilage, remake or reason-code function. The /platform Platform Solutions navigation lists the complete catalog (Ordering: POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering; Kitchen: KDS, Order Status, Energy & Equipment Intelligence; Payments: Qu Pay; Management: Unified Menu Management, Channel Management, Brand & Franchise Management, Notify, Unified Data & Reporting; plus Qube, Qu Equip, Qu Business Edge) with no inventory module. The /integrations directory (all 120 partners enumerated) files inventory and food cost under "Back of House + Labor" - MarketMan, Restaurant365, Crunchtime, Compeat, COGS-Well, Decision Logic, SynergySuite, Altametrics, Rosnet. With no native inventory ledger, a KDS waste entry that depletes inventory cannot exist. https://www.qubeyond.com/kitchen · retrieved 2026-08-08

kitchen-speed-of-service-reporting

Real-time prep tracking and service-speed metrics surfaced in Notify and reporting; percentile slicing and CSV/API export of station times are not documented. https://www.qubeyond.com/management/notify-mobile-insights · retrieved 2026-08-01

kitchen-prep-forecasting

The menu page claims "AI-connected demand and daypart intelligence," the same evidence already used for reporting-sales-forecast ("a daypart-granular forecast surface consumable by scheduling is not documented"). Shortfall: this is demand/daypart intelligence for menu and pricing decisions — nothing establishes it produces a prep list or predicted prep quantity surfaced to kitchen staff as a daily task list, which is what this claim specifically requires. https://www.qubeyond.com/management/unified-menu-management · retrieved 2026-08-04

delivery-driver-roster

Re-evidenced 2026-08-08 after the cited /products/ page began redirecting to the homepage; the reasoning is unchanged and both legs re-verified on live pages. Absence: the /ordering section index enumerates the complete ordering line-up - Point of Sale, Kiosk, Drive-thru, Third-party Ordering, Online Ordering - and the site-wide Platform Solutions nav enumerates the whole 14-product platform, with no delivery, driver or dispatch module anywhere. Affirmative alternative: the Online Ordering page enumerates fulfillment as 'Multiple Hand-Off Modes: Flexible fulfillment options including in-store, curbside, tableside, and white-label delivery', and the integrations directory carries a 'Delivery' category (Cartwheel, Checkmate, DoorDash, GrubHub, UberEats, ezCater). Drivers are not first-class entities in Qu; the vendor enumerates the third-party route instead. Same reasoning carries the sibling delivery-dispatch-board / route-map / driver-tracking / driver-comp / cash-reconcile 'no' scores, which cite the same dead URL and need the same re-pointing. https://www.qubeyond.com/ordering/online-ordering · retrieved 2026-08-08 adversarially verified

delivery-dispatch-board

Re-evidenced 2026-08-08 after the cited /products/ page went dead. The live Omnichannel Ordering index enumerates five products - POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering - and its only delivery statement is marketplace-facing: "Connect every major delivery marketplace directly to your POS - eliminating tablet chaos, manual entry, and costly middleware." No dispatch or expo-for-delivery screen appears in the /platform Platform Solutions nav either. The /integrations directory's "Delivery" category is six marketplaces and aggregators (DoorDash, UberEats, GrubHub, Checkmate, ezCATER, Bites) plus Cartwheel, a third-party delivery dispatch and driver-management platform - i.e. Qu routes the dispatch function to a partner. https://www.qubeyond.com/ordering · retrieved 2026-08-08

delivery-route-map differentiator

Re-evidenced 2026-08-08 after the cited /products/ page went dead. The Platform Solutions navigation enumerates the entire product line - Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Smart Payment Solutions (Qu Pay), Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify, Unified Data & Reporting), Qube, Qu Equip, Qu Business Edge - with no dispatch, mapping or routing product. The /ordering index describes delivery only as "Connect every major delivery marketplace directly to your POS". Route sequencing is a partner function: the /integrations "Delivery" category lists Cartwheel, a third-party dispatch and routing platform. https://www.qubeyond.com/platform · retrieved 2026-08-08

delivery-driver-tracking differentiator

Re-evidenced 2026-08-08 after the cited /products/ page went dead. The Platform Solutions navigation enumerates every Qu product and the only mobile app in it is Qu Notify Mobile Insights, a manager reporting app - there is no driver-facing application, and therefore no source of driver GPS. The /ordering index describes delivery solely as "Connect every major delivery marketplace directly to your POS". Live driver location is a partner capability in Qu's own directory: the /integrations "Delivery" category lists Cartwheel, a third-party dispatch and driver-tracking platform. https://www.qubeyond.com/platform · retrieved 2026-08-08

delivery-zones-polygon differentiator

Qu Next Gen 3.5 release notes for v139 (17 Nov 2020; Wayback capture 2021-01-25) introduce a store-level Delivery Setting: 'New Delivery Setting at Store level that allows to set a Custom Area or a Delivery Radius.' The walkthrough is explicit: 'Besides being able to define delivery settings via a Maximum Delivery Radius, users will have the flexibility to configure their own custom delivery area... go to any Store, Delivery Settings tab and select: Custom Area. The system will request a KML file to be uploaded and once uploaded will show a map to preview the area.' The operator draws the shape in Google MyMaps ('Add lines or draw a shape. Draw the shape on the map to create your custom delivery zone'), exports KML, and sets Calculation Mode to Custom Area; the store must have a valid address 'so that the system can automatically generate coordinates.' That is an arbitrary map polygon, not a radius or ZIP list. VINTAGE: this is the 2020 Next Gen 3.5 generation, not the current Intelligent Commerce Platform; the live site (qubeyond.com/ordering/online-ordering, grade C) still advertises 'white-label delivery' as a hand-off mode but does not describe zone geometry, so persistence of the KML custom-area mechanism into the current product is not independently confirmed. Note also the article records that a drawable in-product map was then only 'in the roadmap'. https://web.archive.org/web/20210125165411/https://support.qubeyond.com/hc/en-us/articles/360052896691-November-17th-v139- · retrieved 2026-09-03

delivery-zone-pricing

SHORTFALL: the documented model is one delivery area per store, not priced zones. Qu Next Gen 3.5 v139 (17 Nov 2020) documents a single store-level Delivery Settings tab whose Calculation Mode is either a 'Maximum Delivery Radius' or one uploaded KML 'Custom Area'; nothing in that configuration carries a fee, an order minimum or a quoted promise time. The delivery fee lives elsewhere entirely, as a service charge: Chapter 6 Configuration (First Gen 2.0) says 'Service charges such as gratuities or delivery fees may be added to Qu' with a Service Charge Category of 'Service Charge / Delivery Fee / Other Charge / Gratuity / Automatic Service Charge', configured at enterprise/store level against items, not against a geographic zone. So a fee and a validated delivery area both exist and are applied per store from the validated address, but per-zone fee/minimum/promise-time tiering is not documented anywhere in the archived corpus. VINTAGE: First Gen 2.0 (2018) settings reference plus Next Gen 3.5 v139 (2020); current product not covered. https://web.archive.org/web/20210125165411/https://support.qubeyond.com/hc/en-us/articles/360052896691-November-17th-v139- · retrieved 2026-09-03

delivery-address-validation

Qu Next Gen 3.5 help article 'Changing Order Types from the Online Menu' (updated 19 Oct 2020; Wayback capture 2020-11-25): 'Guest will be prompted by the website to enter the delivery address to validate that delivery is available from this location. An actual physical address is required (i.e. 123 Main Street). If the store can deliver to the provided address, the user will get a success message... If the location cannot deliver to the provided address, the user will be prompted to either order pickup or search for other sites.' Out-of-zone addresses are therefore flagged and blocked before the order proceeds: 'Since a valid address is required to ensure the location can deliver, users will be required to enter and submit one before they can exit the prompt.' Geocoding against a mapping service is corroborated by the v139 delivery-area notes, which require a valid store address 'so that the system can automatically generate coordinates for the location' and use Google MyMaps/KML geometry for the area. VINTAGE: Next Gen 3.5, 2020 documentation; the live marketing site still lists delivery as a hand-off mode (grade C) but does not describe address validation, so the current implementation is not separately confirmed. https://web.archive.org/web/20201125102417/https://support.qubeyond.com/hc/en-us/articles/360048239071-Changing-Order-Types-from-the-Online-Menu-Next-Gen- · retrieved 2026-09-03

delivery-driver-comp differentiator

Re-evidenced 2026-08-08 after the cited /products/ page went dead. The Platform Solutions navigation enumerates the whole catalog and contains no driver, delivery-dispatch or payroll product, so there is no place to record mileage, per-delivery reimbursement or driver-retained tips, and no first-party payroll target to export wage-versus-reimbursement lines to. The /integrations directory confirms both halves are bought in: "Delivery" carries Cartwheel (dispatch/driver management) and "Back of House + Labor" carries Proliant (payroll) alongside 7shifts, HotSchedules, Harri and Workstream. https://www.qubeyond.com/platform · retrieved 2026-08-08

delivery-cash-reconcile

Re-evidenced 2026-08-08 after the cited /products/ page went dead. The Platform Solutions navigation enumerates every Qu product and includes no driver or delivery-dispatch module, so there is no driver to bank, no run assignment to reconcile against and no per-driver over/short report. The /ordering index treats delivery only as "Connect every major delivery marketplace directly to your POS", and the /integrations "Delivery" category assigns driver management to the partner Cartwheel. https://www.qubeyond.com/platform · retrieved 2026-08-08

delivery-daas-dispatch

Verified verbatim 'Flexible fulfillment options including in-store, curbside, tableside, and white-label delivery.' No courier network is named, no quote/assign/status contract is documented. Partial is the ceiling; do not let anyone read this as native dispatch. https://www.qubeyond.com/ordering/online-ordering · retrieved 2026-08-01 adversarially verified

delivery-daas-fallback differentiator

'courier' and 'dispatch' occur zero times; every 'driver' hit is either metaphorical ('revenue driver') or generic industry commentary. Also fetched /integrations live: it is a filterable directory of 150 certified partners with a 'Delivery' category, which shows Qu integrates delivery providers but says nothing about overflow rules. Hybrid-dispatch logic — auto-escalating to a DaaS courier when no in-house driver is free, out of zone, or past a wait threshold — is rules configuration described only in operator documentation. Nothing on the open surface bears on it.

delivery-3p-direct-integration differentiator

Direct bi-directional integrations with Uber Eats, DoorDash, Grubhub, EZCater and Monkey, "no middleware required"; corroborated by DPIP 2026 membership. https://www.qubeyond.com/ordering/third-party-ordering/ · retrieved 2026-08-01

delivery-3p-injection

Orders inject straight into the POS and KDS with no tablet re-keying; Qu cites a 0.2% error rate vs 0.7% industry average and 99.8% order success. https://www.qubeyond.com/ordering/third-party-ordering/ · retrieved 2026-08-01

delivery-menu-push

Single menu pushes to third parties with channel-specific pricing; real-time menu syncing is a DPIP requirement Qu meets. https://www.qubeyond.com/management/channel-management · retrieved 2026-08-01

delivery-86-sync

I verified the program requirements page independently: Preferred partners 'must support all of the following features' including real-time menu syncing, real-time 86ing, order ready signal, item polling, and detailed error reporting, with 'supporting' defined as built, launched, and used by at least one live store. Membership therefore is real evidence. Scope caveat: it evidences these capabilities on the DoorDash channel only, not platform-wide. https://developer.doordash.com/en-US/docs/marketplace/overview/getting_started/preferred_integrations_new/ · retrieved 2026-08-01 adversarially verified

delivery-store-pause

Operators can pause third-party integrations from the Channel Management dashboard; timed auto-reactivation is not documented. https://www.qubeyond.com/management/channel-management · retrieved 2026-08-01

delivery-3p-reconciliation differentiator

Qu markets third-party economics heavily (0.2% vs 0.7% order failure rate, direct injection ROI math, Bill Miller BBQ's '25% decrease in check reconciliations & lost online transactions'), and Winter 2026 adds 'Major Improvements to Digital Order Attribution: Enhanced flexibility in mapping and splitting digital order revenue across channels and providers'. All of that concerns attributing recorded order revenue to channels, not matching marketplace payout deposits against POS-recorded 3P sales with commission, marketing fees, refunds and unpaid-order detection itemized. The Bill Miller figure describes fewer reconciliations being needed, not a reconciliation report. Since none of these establishes the payout-matching object the claim names, and a report inventory would only appear in operator documentation, the cell is unresolved rather than absent.

delivery-injection-error-visibility differentiator

Channel Management provides error visibility and validation reporting; detailed order error reporting is a DPIP requirement Qu meets. https://www.qubeyond.com/management/channel-management · retrieved 2026-08-01

delivery-tracking-page

Qu Order Status keeps guests and drivers informed via brandable status surfaces; a branded tracking page on the restaurant's own domain with driver state is not documented (no in-house drivers). https://www.qubeyond.com/kitchen-solutions/order-status · retrieved 2026-08-01

delivery-promise-time differentiator

Qu post: 'you can dynamically adjust ready times, turning a static promise into a responsive solution that adapts to real-time conditions' with 'estimates for order readiness by considering factors like historical and current order volume, labor availability, and preparation time'; Qu's Smart Kitchen page lists 'AI-generated promised ready times — improves delivery time accuracy by factoring in all channels, labor, and prep needs.' Shortfall: marketing/roadmap material describing a kitchen ready-time estimate; no evidence the quote factors driver availability or per-zone drive time, and no configuration documentation exists (support site login-walled). https://www.qubeyond.com/resource-center/5-reasons-why-your-kitchen-needs-a-smart-upgrade-now · retrieved 2026-09-03

delivery-offline-behavior

Re-fetched the Qu Business Edge resilience page directly for delivery-specific offline language: it states only that "ordering, payments, and kitchen routing continue uninterrupted during connectivity outages" — a generic continuity claim with no mention of cash delivery orders, driver assignment, or driver settlement. Qu also ships no native driver/dispatch module at all (delivery-driver-roster, -dispatch-board, -driver-tracking, -driver-comp, -cash-reconcile are all documented "no" elsewhere in this record), so there is no native driver-assignment or driver-settlement process to have offline behavior for. Same "claims continuity, publishes no feature-level detail" pattern as reliability-offline-feature-matrix (also "no"). https://www.qubeyond.com/qu-business-edge · retrieved 2026-08-04

digital-first-party-web

First-party branded online ordering with custom subdomains, positioned explicitly against marketplace commissions ($60K–$180K+ annual savings claimed). https://www.qubeyond.com/ordering/online-ordering · retrieved 2026-08-01

digital-menu-single-source

Every item, price and modifier lives in a single menu database driving all channels. https://www.qubeyond.com/management/unified-menu-management · retrieved 2026-08-01

digital-native-app differentiator

Qu's first-party ordering channel is described as web, not a native app: qubeyond.com/ordering/online-ordering offers 'Multi & Virtual Brand Support -- Manage multiple brands under one parent with custom subdomains and branding' and its FAQ says orders are placed 'through a branded web or mobile experience.' Branded native apps come from certified partners instead: the integrations directory lists Lunchbox (lunchbox.io), Olo, Onosys and Paytronix under 'Digital Ordering'/'Payments', and Qu's own release 'Paytronix & Qu Further Integration' (2026-06-23) describes Paytronix as providing 'loyalty programs, online ordering, gift cards, branded mobile applications' with 'orders placed through Paytronix's online ordering platform flow automatically into Qu.' Shortfall: no first-party Qu-published iOS/Android app; a branded native app depends on a third-party ordering partner, and neither source states that such an app is published under the restaurant's own brand in the App Store and Play Store. https://www.qubeyond.com/integrations · retrieved 2026-09-03

digital-account-saved-payment

SHORTFALL: saved payment is documented; saved addresses and one-tap reorder are not. Qu Web Ordering v139 (17 Nov 2020, Next Gen 3.5) documents guest accounts with stored cards under 'Store Saved Payment Information: (Same as Express) Saved payment is also supported with Aurus. Logged in users can save a card by clicking the checkbox. User can save multiple cards and can make payment using any single card at a time.' Card entry is through a hosted Aurus/Express iframe, i.e. the PAN is held by the processor. Logged-in accounts are further evidenced by the Punchh web-ordering flow ('Logged in users earn points by placing orders'). The archived corpus nowhere documents a saved-address book or one-tap reorder of a previous order, both of which the claim requires. VINTAGE: Next Gen 3.5 / Web Ordering 3.0, 2020-21; the current Intelligent Commerce Platform online-ordering page does not restate these mechanics. https://web.archive.org/web/20210125165411/https://support.qubeyond.com/hc/en-us/articles/360052896691-November-17th-v139- · retrieved 2026-09-03

digital-upsell-engine differentiator

AI-driven upsell/cross-sell prompts documented for kiosk and referenced for digital channels; attach-rate reporting not documented. https://www.qubeyond.com/ordering/kiosk · retrieved 2026-08-01

digital-scheduled-pacing

SHORTFALL: scheduled/future ordering is documented; per-daypart capacity throttling is not. Qu Web Ordering v140 (16 Dec 2020, Next Gen 3.5) documents the platform setting 'Future Order Acceptance Days' with two parameters, 'Minimum days - lowest number of days in advance an order can be placed (0 = same day, 1 = tomorrow...)' and 'Maximum days - highest number of days in advance an order can be placed', settable per order channel (web vs catering); v140/v141 also reference a 'Future Order Calendar prompt' and v141 a checkout 'time slot' that updates on expiry, so time-slotted future ordering exists. The store/group settings checklist names 'Bucket Scheduling' and 'Min Max Order Limits' and 'Kitchen Buffer Lead Time' but never defines them, and no article describes slot capacity limits or automatic closing of saturated slots. VINTAGE: Next Gen 3.5, Dec 2020 / Jan 2021 release notes; not confirmed for the current platform. https://web.archive.org/web/20210125175255/https://support.qubeyond.com/hc/en-us/articles/360054441371-December-16th-v140- · retrieved 2026-09-03 adversarially verified

digital-fulfillment-modes

Online ordering supports in-store, curbside, tableside and white-label delivery handoff modes. https://www.qubeyond.com/ordering/online-ordering · retrieved 2026-08-01

digital-qr-table

"Tableside" is a listed fulfillment mode; QR scan-to-order attaching to an existing POS check with split/tip is not documented and Qu disclaims table service. https://www.qubeyond.com/ordering/online-ordering · retrieved 2026-08-01

digital-kiosk differentiator

Kiosk Marketplace, 2025-08-21, independently reports Qu shipping kiosk upgrades that let "Qu's Flex POS terminals switch between cashier and guest-facing modes", with "ADA screen reader support and multiple language options", naming Taco John's and WOWorks as early adopters. Shortfall: kiosk is a guest-facing mode of the Qu Flex POS terminal rather than a documented standalone kiosk product, so a terminal running as a kiosk is not simultaneously a cashier station; the vendor page claims only "software accessibility features" for ADA, with no tactile keypad, audio jack or physical accessibility hardware documented. Qu publishes no publicly retrievable product documentation: support.qubeyond.com (the 'Qu Campus' Document360 portal) redirects to a login, and both qu-api.qubeyond.com and qu-pos-api.qubeyond.com return HTTP 403 behind a mismatched TLS certificate. No grade A/B evidence is obtainable, so a differentiator 'yes' cannot stand. https://www.kioskmarketplace.com/news/qu-unveils-kiosk-upgrades-to-boost-revenue-ease-staffing-for-restaurants/ · retrieved 2026-08-02 adversarially verified

digital-group-ordering

'group order' and 'shared cart' return nothing. The nearest first-party feature is Winter 2025's 'Combine Checks', whose own worked example is 'a coach paying for individual orders placed by a sports team' — but that is a staff-side POS merge of checks already rung, not a shareable link where remote participants build one cart under a per-person spend cap. Different object, so it does not part-satisfy the claim. Catering appears in the corpus only as survey data about operator priorities and as an integration category, suggesting group/catering ordering may be partner-delivered, which would make the partner the subject rather than Qu.

digital-catering-portal differentiator

Same evidence as order-capture-catering: EZCater is named as a direct integration partner. Shortfall: no distinct native catering flow — separate catering menu/minimums, lead-time rules, quotes/proposals, deposits, or invoice/house-account/ACH terms — is documented; catering is delegated to the EZCater integration. https://www.qubeyond.com/ordering/third-party-ordering/ · retrieved 2026-08-04

digital-voice-ai-phone differentiator

Named voice AI partners (ConverseNow, Presto) inject orders into POS/KDS; documented for drive-thru, not explicitly for inbound phone. https://www.qubeyond.com/ordering/drive-thru · retrieved 2026-08-01

digital-drivethru-ai

AI voice ordering integration at the drive-thru lane flowing into POS and KDS; escalation-to-human handoff is not documented. https://www.qubeyond.com/ordering/drive-thru · retrieved 2026-08-01

digital-sms-ordering

All four 'SMS' occurrences are unrelated: Adyen's terms listing SMS/IVR payment methods, Qu Equip's 'Multi-channel alerts via SMS, Email, and Notify' for equipment faults, and two marketing-cadence discussions in guest-engagement thought leadership. Qu's own guest-facing ordering entry points are enumerated as POS, kiosk, drive-thru, online ordering, third-party, plus QR-based tableside and curbside; conversational text-to-order is not among them. That list is a marketing selection rather than an exhaustive channel enumeration, so it will not be converted into an absence.

digital-google-order differentiator

No occurrence of 'Order with Google' or 'Google Business Profile' anywhere; the sole related line is advice in a 2020-era ghost-kitchen listicle — '6. Own your Google My Business page… You can direct customers to order directly from you' — which counsels the operator to do this themselves and claims nothing about Qu provisioning the link. This is a genuinely marketing-shaped feature and Qu's 177-piece resource centre argues relentlessly for shifting demand from marketplaces to first-party channels, so the silence is suggestive; but editorial silence across thought-leadership is not an enumeration, and whether Qu's white-label ordering URLs are provisioned to GBP is an onboarding step recorded only in operator documentation.

digital-apple-business-connect

'Apple Business' and 'Apple Maps' occur zero times; the only Apple references in the corpus are 'Apple Pay', an 'Apple iOS and Android applications' aside about app development, and two idiomatic 'apples-to-apples' phrases. As with the Google cell, an Apple Maps 'Order Food' custom action is a per-brand provisioning task rather than a platform feature page, and Qu publishes no onboarding documentation publicly. Nothing read settles it.

digital-loyalty-attach

Loyalty accrual/redemption in digital ordering is delivered by the Paytronix integration across in-store, drive-thru, kiosk, mobile and web — partner, not native. https://www.globenewswire.com/news-release/2026/06/23/3316041/0/en/paytronix-and-qu-further-integration-enabling-advanced-omnichannel-ordering-and-menu-management.html · retrieved 2026-08-01

digital-subscriptions

'membership' returns nothing and both 'subscription' hits are about software vendor contracts ('five vendors costs five subscriptions', 'not just another software subscription'), not guest programs. Winter 2026 ships 'Loyalty Profiles at Kiosk' — guests log in, view and redeem rewards in the kiosk flow — which confirms a loyalty surface but says nothing about recurring billing, fee-waiver tiers or per-period entitlements; /integrations carries a separate 'Loyalty' partner category, so paid tiers may sit with a partner, in which case the partner would be the subject.

digital-promo-parity

Single menu/promotion database with channel-level rule configuration and eligibility; stacking/precedence semantics not documented. https://www.qubeyond.com/management/channel-management · retrieved 2026-08-01

digital-guest-data-ownership differentiator

Unified Data & Reporting FAQ: 'Qu's unified data layer supports API-based integrations with external BI platforms, enabling operators to pipe Qu data into the analytics environment of their choice'; the Online Ordering page pitches 'Retain Your Guest Data — Easily access and analyze data to foster repeat visits.' Shortfall: this is access to a data layer, not a documented bulk export of first-party guest records (email, phone, consent status, order history), and Qu makes no statement about export being free of fee or vendor approval. https://www.qubeyond.com/management/unified-data-reporting · retrieved 2026-09-03

digital-checkout-pci-sca

Fetched the Qu Pay, Online Ordering, and platform pages directly for PCI language: none of the three — including Qu Pay, the page whose entire subject is payments — mentions hosted payment fields, a hosted payment page, or publishes any PCI DSS 4.0 compliance statement (including the March-2025 script-integrity requirement). Complete silence on the vendor's own payments product page, on the exact topic that page exists to cover, supports a documented absence rather than mere non-discovery. https://www.qubeyond.com/payments/qu-pay · retrieved 2026-08-04

digital-surcharge-transparency differentiator

This cell asks about channel parity for a fee configuration whose existence is itself unmeasured. Since no surcharge, dual-pricing or service-fee configuration is documented for the POS anywhere in the legal set or the 199 pages, there is nothing to compare digital channels against, and no guest-facing disclosure or prohibited-jurisdiction handling is described. The Adyen contract's only surcharge clause is the Australian merchant cap and does not address disclosure at all.

guest-loyalty-unified-profile

Qu claims a "single source of truth for guest data" normalizing guest records across POS, kiosk, drive-thru and online; dedup/merge behavior is not documented. https://www.qubeyond.com/management/unified-data-reporting · retrieved 2026-08-01

guest-loyalty-thirdparty-identity-attach differentiator

Fully traversed Qu's certified-partner directory (https://www.qubeyond.com/integrations, 14 pages, 121 named partners, 11 category facets). Delivery marketplaces appear as their own facet (DoorDash, UberEats, GrubHub, ezCATER, Checkmate, Cartwheel, Bites) and loyalty/guest identity appears as a separate Loyalty facet (Incentivio, Paytronix, Punchh, SPARKFLY, SpendGo, Thanx, hang, tapmango). Qu publishes nothing about whether a marketplace order joins to a guest profile, and because the guest profile lives in a partner system the subject of this claim is the partner, not Qu. Grepped all 199 uncited pages: no page connects third-party order ingestion to guest identity. Note the directory is not exhaustive by Qu's own reckoning — its counter reads '150 integrations' while 121 are served.

guest-loyalty-accrual-models

Strengthened: beyond the Paytronix releases, Qu's own online-ordering page says 'third party loyalty', and loyalty is absent from the enumerated product catalog. Documented absence, not merely undocumented. https://www.qubeyond.com/ordering/online-ordering · retrieved 2026-08-01 adversarially verified

guest-loyalty-tiers differentiator

Qu's own certified-partner directory carries a dedicated Loyalty category (Incentivio, Paytronix, Punchh, SPARKFLY, SpendGo, Thanx, hang, tapmango) and the /become-a-partner form lists 'Loyalty' as a partner Solution Type, so loyalty is partner-delivered and the tier engine's subject is the partner, not Qu. 'tier' occurs 6 times in the 199-page corpus and never as a loyalty status tier (price tiers, premium tier, tiers of support). Qu makes no claim to own this capability, so a Qu `no` would score the wrong object; the partners' tier behaviour is undocumented on any Qu surface.

guest-loyalty-offline-behavior differentiator

Re-fetched the Qu Business Edge offline-resilience page directly: its only offline statement is generic ("full transaction processing continues... system state preserved locally... sync resumes automatically"), with no mention of loyalty lookup, accrual, or redemption at all. The Qu Pay page is likewise silent. Loyalty itself is partner-delivered (Paytronix/Thanx), so the page that would need to document this behavior — and doesn't — is the one page describing Qu's own offline model. Same "claims continuity, silent on the named sub-behavior" pattern as reliability-offline-feature-matrix (also "no"). https://www.qubeyond.com/qu-business-edge · retrieved 2026-08-04

guest-loyalty-offer-stacking-rules differentiator

Same evidence and finding as digital-promo-parity: a single menu/promotion database with channel-level rule configuration and eligibility is documented, but explicit stacking/precedence semantics (exclusive vs combinable, order of application) are not — for the promotion engine generally, which is the mechanism a loyalty offer-stacking rule would run on. https://www.qubeyond.com/management/channel-management · retrieved 2026-08-04

guest-loyalty-targeted-offers differentiator

Same partner-subject finding: the integrations directory's Loyalty facet holds eight certified partners and Qu ships no loyalty or marketing module. The corpus's only segmentation/one-to-one-offer passage is a Church's Chicken executive interview describing his own marketing practice, not a Qu product capability. 'segment' (14) and 'offer' (96) hits are thought-leadership prose. Audience-rule targeting belongs to the partner platform and Qu documents none of it.

guest-loyalty-rfm-segmentation differentiator

Qu's own loyalty post describes lifecycle segmentation only inside a certified partner's product: "Incentivio's Guest Journey Dashboard leverages machine learning to automatically segment based on guest's visit frequency and spending habits" and "identifies guests at risk of churning." Shortfall: the capability is the third-party loyalty partner's (Incentivio), reached through the Qu integration; Qu describes its own role as the "foundational platform" / data layer and no source shows Qu computing recency-frequency-monetary or lifecycle segments natively. https://www.qubeyond.com/resource-center/loyalty-3-0-elevating-guest-engagement-through-deeper-insights · retrieved 2026-09-03

guest-loyalty-lifecycle-automation

'lifecycle' returns zero hits across all 199 uncited pages and the Adyen contract. Triggered birthday / first-visit / win-back campaigns would live in the loyalty-marketing engine, which the certified-partner directory shows is supplied by partners (Loyalty facet: Incentivio, Paytronix, Punchh, SPARKFLY, SpendGo, Thanx, hang, tapmango). The subject is the partner; Qu neither claims nor is enumerated to own lifecycle automation, and partner feature depth is not published on any Qu host.

guest-loyalty-native-email-sms differentiator

Same page and finding underlying guest-loyalty-accrual-models: Qu's own Online Ordering page states "third party loyalty," and guest email/SMS messaging is consistently presented across Qu's resource-center posts as delivered through named partners (Thanx, Paytronix), never as a native Qu send capability. The claim specifically requires NOT solely handing the list to a third-party ESP — that is exactly what Qu's own language describes. https://www.qubeyond.com/ordering/online-ordering · retrieved 2026-08-04

guest-loyalty-consent-management

The only consent machinery documented anywhere is OneTrust cookie consent on qubeyond.com itself ('Set by OneTrust to store the user's cookie consent preferences') plus GPC honouring for Qu's own site visitors — that is Qu's marketing site, not an operator's guest-messaging consent ledger. Per-channel marketing consent with timestamp and source, and non-keyword revocation handling, are product behaviours the privacy policy explicitly scopes itself out of and that no other document touches.

guest-loyalty-10dlc-registration

'10DLC' and 'A2P' return zero hits in the 199-page corpus and in the 69 KB Adyen contract. The four SMS hits are a payment-method clause, a Qu Notify alert-channel mention ('Multi-channel alerts via SMS, Email, and Notify'), and two customer interview quotes — none is guest marketing SMS. Since guest messaging is partner-delivered per the directory's Loyalty facet, carrier registration would be the partner's obligation and Qu's silence is not a denial. A marketing site would not necessarily document 10DLC even if handled.

guest-loyalty-campaign-attribution differentiator

Spring 2025 release: "Qu tracks acceptance rates for both kiosk and POS, as well as the revenue impact and net sales lift for each cross-sell campaign" with "comprehensive, real-time metrics that show exactly which promotions are working." Shortfall: attribution is documented only for kiosk/POS cross-sell upsell campaigns; nothing in the corpus reports redemption or incremental sales for an issued loyalty offer or marketing campaign, which live in partner systems (Thanx, Paytronix, Spendgo). https://www.qubeyond.com/resource-center/qus-spring-2025-product-release-highlights · retrieved 2026-09-03

guest-loyalty-data-export-portability differentiator

Feature page lists "Normalized guest and operational data" in the unified data layer and states: "Qu's unified data layer supports API-based integrations with external BI platforms, enabling operators to pipe Qu data into the analytics environment of their choice." Shortfall: the page never states that the guest list with contact PII is exportable, never mentions CSV or a self-serve export, and says nothing about whether a fee or a support request is required; only BI piping of Qu data generally is established. https://www.qubeyond.com/management/unified-data-reporting · retrieved 2026-09-03

guest-loyalty-cdp-event-api differentiator

A DataExport API component exists and Qu integrates named CDP/analytics partners (Bikky, Paytronix); no public event/webhook contract is documented. https://status.qubeyond.com/ · retrieved 2026-08-01

guest-loyalty-review-capture-routing differentiator

New evidence but not settling: the certified-partner directory includes feedback/reputation partners — Ovation and momos under Analytics, Marqii under Digital Ordering — so a review-capture route plainly exists via partner, but Qu describes none of their behaviour, and score-based routing (low to private recovery, high to public sites) is a property of the partner product that no Qu page states. Corpus 'review'/'rating' hits are all 'read the report' and star-rating prose. Partner is the subject; depth undocumented.

guest-loyalty-referral-program

Re-evidenced 2026-08-08 after the cited /products/ page began redirecting to the homepage. The Platform Solutions nav (carried on /integrations and every product page, and matching the sitemap product tree exactly) still enumerates the full module line-up - Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Qu Pay, Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify Mobile Insights, Unified Data & Reporting) - and no loyalty product appears in it. Qu's own Online Ordering page frames loyalty as external: 'Whether you use Qu Pay or an integrated provider, third party loyalty or Qu's built-in discounts, Qu Online Ordering fits the way you operate' - built-in discounts, third-party loyalty. The integrations directory carries a 'Loyalty' category whose members are Thanx, Paytronix, Punchh, Incentivio, SpendGo, Sparkfly, tapmango and hang. (The earlier note also named LevelUp; it is not in the current 150-entry directory and has been dropped.) With no native loyalty program there is no native referral mechanic, per-guest code or two-sided reward. https://www.qubeyond.com/integrations · retrieved 2026-08-08 adversarially verified

guest-loyalty-wallet-pass differentiator

All four 'wallet' hits in the corpus are payment wallets or the 'share of guest wallet' metaphor (Adyen/Olo Pay mobile wallets); none is a loyalty pass. A wallet loyalty pass is a loyalty-engine feature and the integrations directory establishes loyalty is delivered by eight certified partners, several of which issue passes in their own right — so the subject is the partner. Qu claims no loyalty module and therefore cannot be scored `no` for a pass it never offered.

guest-loyalty-privacy-rights-tooling

The privacy policy is a controller-side website policy that expressly excludes the product data plane ('Information processed on behalf of our customers through Qu products and services, where separate contractual terms may apply') and handles its own DSARs by email. It therefore cannot speak to operator-facing admin tooling over guest records, and deletion propagation to loyalty is further out of reach because Qu's loyalty is partner-supplied. Distinct from commercial-privacy-dsar-tooling, which is scored no on its published-DPA conjunct — this cell has no publication conjunct to fail.

guest-loyalty-redemption-fraud-controls

'velocity' occurs once and means drive-thru order velocity; the 17 'fraud' hits in the corpus and 17 in the Adyen contract are payment/chargeback fraud, never loyalty redemption. Redemption velocity limits, manual point-adjustment approval and self-redemption flagging sit inside the loyalty engine, which the certified-partner directory shows is partner-supplied. Subject is the partner; neither Qu nor its partner announcements address redemption fraud controls.

guest-loyalty-ai-offer-recommendation differentiator

Platform page, Enterprise AI Agents: "Performance data across locations is analyzed to highlight what's working and what's not. Enterprise Management enables teams to fine-tune promotions, reduce unnecessary discounting." The April 2026 ICP announcement repeats "Enterprise AI agents to optimize decisions like promotions and discounts." Shortfall: the AI agents are described as optimising network-level promotion and discount decisions; no source shows AI/ML recommendations for offer content, a target audience, or send timing to guests, and Qu ships no send channel of its own. https://www.qubeyond.com/platform · retrieved 2026-09-03

guest-loyalty-stored-value-gift

Stored value/gift is partner-delivered via Paytronix across all channels and locations; not a native Qu ledger. https://www.globenewswire.com/news-release/2026/06/23/3316041/0/en/paytronix-and-qu-further-integration-enabling-advanced-omnichannel-ordering-and-menu-management.html · retrieved 2026-08-01

labor-clock-in-at-pos

Qu holds punch and hours data natively: Notify can alert on "Number of Employees Clocked in ... in one or all of your stores", and the Winter 2025 release describes tip pooling "within the enterprise management solution" that distributes tips "based on hours worked" and is "closed at the end of each payroll week". Shortfall: no source in the 239-page corpus describes the punch mechanism itself - there is not a single mention of clock-in, time clock, punch or timecard at the terminal, so PIN/badge/card clock-in at the POS is not established (the word "punch" and "time clock" return zero hits site-wide). https://www.qubeyond.com/resource-center/finally-an-app-that-saves-your-store-managers-time-money · retrieved 2026-09-03 adversarially verified

labor-photo-punch-verification differentiator

'punch', 'time clock', 'clock-in' and 'timekeeping' return zero hits, but the corpus contains affirmative evidence of a native labor-hours surface that makes an absence verdict unsafe: Winter 2025 shipped tip pooling that 'collects and distributes tips among eligible employees based on hours worked… simplifying tracking, adjustments, and payroll through automatic calculations and detailed reports', which presupposes hours captured in Qu. Whether the punch mechanism captures a photo or performs facial verification, and whether a non-biometric mode exists, is a time-clock configuration detail confined to the walled operator documentation.

labor-geofenced-mobile-punch

'geofenc' occurs zero times. Same footing as the photo-punch cell: Qu's tip-pooling feature implies hours-worked capture, /integrations carries a 'Back of House + Labor' partner category (7shifts, Altametrics among them) suggesting scheduling and labor may often be partner-delivered, and neither fact establishes whether Qu itself offers a location-validated mobile punch. A marketing corpus would not document a geofence radius or its enforcement behaviour.

labor-offline-time-punch differentiator

Qu's offline claims are consistently scoped to commerce, not labor — the Business Edge story is that ordering, payments and kitchen routing continue and 'Sync resumes automatically' — and no page extends that to time punches or describes duplicate-free reconciliation on reconnect. The claim explicitly requires the behaviour be documented, and Qu documents its offline scope only at the level of order flow; but this surface would never enumerate which subsystems are excluded from local execution, so the omission cannot be converted into a no.

labor-granular-rbac

Granular permissioning, user administration and role-based permission management are claimed across brands and locations; per-action grant lists are not published. https://www.qubeyond.com/management/brand-franchise-management · retrieved 2026-08-01

labor-manager-override-audit

Chapter 12: Audit Trail (First Gen 2.0, updated 2020-04-20): 'The Qu audit trail provides a detailed activity history of changes occurring within Qu. Changes can be tracked based on Date, Employee, Module, Location and any combination of the above. The report can also be exported as a csv document. Audit Trail can only be accessed from the Enterprise Level of Qu Enterprise Intelligence.' Approver attribution exists at the POS: restricting till functions means 'the POS will present a manager prompt to the cashier when performing restricted actions', and per 'Assigning an Employee Mag Card to a User' (Jan 2021) the manager clears it by swiping their own card. EI time-entry edits are attributed (a 'Last Edit By' field and an 'Edited shifts' filter in Labor Summary, v141-v143 release notes) and 'you are required to enter a comment to indicate the reason for manually updating the entries'. Shortfall: the docs never state that POS manager overrides themselves land in the audit trail, and immutability or tamper-evidence is nowhere asserted. Vintage: First Gen 2.0 (2018-2020) and Next Gen 3.5 (2020-21). https://web.archive.org/web/20200809112957/https://support.qubeyond.com/hc/en-us/articles/360001271931-Chapter-12-Audit-Trail-First-Gen-2-0- · retrieved 2026-09-03

labor-native-scheduling differentiator

Re-evidenced 2026-08-08: /about/qu-technology-partners/ now 301s to /integrations, which carries the same evidence. Qu ships no scheduling product - the site-wide Platform Solutions enumeration (five ordering products, three kitchen products, Qu Pay, five management products), corroborated item for item by the sitemap's product URL tree, contains no workforce, scheduling or time-and-attendance module. Scheduling is partner-delivered: the integrations directory's 'Back of House + Labor' category lists 7shifts, Altametrics, HotSchedules, Harri, Workstream and Proliant among its 150 certified integrations. Schedule building and publishing therefore happen in a third-party app, not in the platform holding the sales data. https://www.qubeyond.com/integrations · retrieved 2026-08-08 adversarially verified

labor-demand-labor-forecast differentiator

"The machine learning models and AI function within Notify provide sales and labor forecasting based on previous store performance. These predictive analytics help you adjust staffing levels in advance." The Notify product page repeats "predictive analytics help you forecast trends and optimize staffing". Shortfall: the forecast is advisory output in the Notify mobile app built on the operator's own store history; the corpus never shows recommended staffing levels or labor hours broken out by daypart, and Qu ships no scheduling surface (7shifts and Altametrics sit in Qu's "Back of House + Labor" partner category). https://www.qubeyond.com/resource-center/finally-an-app-that-saves-your-store-managers-time-money · retrieved 2026-09-03

labor-realtime-labor-percent differentiator

Notify is described as "Qu's voice-activated and AI-enabled real-time reporting app" where a manager can "check on store sales, top selling items, labor to net sales percentage", with configurable alerts on "Labor to net sales percentage". Shortfall: the only evidence is a 2022 vendor blog post; the current Notify product page reduces this to "sales, labor, and operational metrics", and no product documentation states the refresh interval or that the figure is available on the POS itself during service. https://www.qubeyond.com/resource-center/finally-an-app-that-saves-your-store-managers-time-money · retrieved 2026-09-03 adversarially verified

labor-overtime-prevention differentiator

Notify alerts can be configured on KPI thresholds "including staff overtime", and the listed example is "get alerted any time of the day about: Employees who are close to overtime". Shortfall: this is a threshold alert pushed to a manager's phone, not a warning or block presented at clock-in on the terminal; nothing in the corpus prevents or interrupts the punch, and the overtime threshold is described only as a configurable Notify KPI. https://www.qubeyond.com/resource-center/finally-an-app-that-saves-your-store-managers-time-money · retrieved 2026-09-03

labor-break-compliance-by-state differentiator

Re-evidenced 2026-08-08: /about/qu-technology-partners/ now 301s to /integrations, which carries the same evidence. Qu ships no labor module: the site-wide Platform Solutions enumeration (ordering, kitchen, payments, and menu/channel/brand/notify/data management), corroborated by the sitemap's product URL tree, has no workforce, scheduling or time-and-attendance product, and Qu's own directory delegates the category - 'Back of House + Labor' lists 7shifts, Altametrics, HotSchedules, Harri, Workstream and Proliant. Per-state break-rule configuration, break-attestation prompts and missed-break premium flagging are workforce-module features that live in those partner products, not in Qu. (7shifts' Qu integration article remains unreadable: kb.7shifts.com returns HTTP 403 to both direct fetch and the Zendesk help-center API, re-probed 2026-08-08.) https://www.qubeyond.com/integrations · retrieved 2026-08-08 adversarially verified

labor-fair-workweek-support

Re-evidenced 2026-08-08: /about/qu-technology-partners/ now 301s to /integrations. The chain established for labor-native-scheduling and labor-shift-swap-workflow (both 'no') re-verified on live pages: Qu's enumerated platform - five ordering products, three kitchen products, Qu Pay, five management products, matching the sitemap product tree exactly - contains no workforce module, and the integrations directory routes 'Back of House + Labor' to 7shifts, Altametrics, HotSchedules and Harri. Predictive-scheduling ordinance support requires a native scheduling system to measure schedule publication and employer-initiated changes against; Qu has none, so advance-notice tracking and predictability-pay calculation are properties of the partner product. https://www.qubeyond.com/integrations · retrieved 2026-08-08 adversarially verified

labor-minor-labor-rules

Re-evidenced 2026-08-08: /about/qu-technology-partners/ now 301s to /integrations. The claim requires enforcement at both scheduling and clock-in. Qu has no native scheduling surface at all - the site-wide Platform Solutions enumeration and the sitemap's product URL tree agree on fourteen products (ordering, kitchen, payments, management) with no workforce module - and the vendor's own directory routes the category to 'Back of House + Labor' partners 7shifts, Altametrics, HotSchedules and Harri. Age-based hour caps, prohibited time windows and school-day limits therefore cannot be enforced natively at scheduling; any such enforcement is a property of the partner product. The nearest thing Qu ships is reporting, not enforcement: Qu Notify Mobile Insights offers 'real-time reporting across stores, labor, and items'. https://www.qubeyond.com/integrations · retrieved 2026-08-08 adversarially verified

labor-tip-pooling-rules

Same source as labor-tip-distribution-audit-trail and payments-tip-pooling: Qu "automatically transfers sales, payment, and tip information to 7shifts," giving Qu per-employee tip capture. Shortfall: the automatic per-shift pooling computation from configurable rules (hours worked, sales percentage, role, points) happens inside 7shifts' separately licensed Tip Pooling module, not in Qu, which publishes no native pooling rule engine. https://kb.7shifts.com/hc/en-us/articles/35540967177875-Tip-Pooling-for-Qu-POS · retrieved 2026-08-04

labor-tip-distribution-audit-trail

7shifts' 'Tip Pooling for Qu POS' doc (updated 2026-06-24) states 'Qu automatically transfers sales, payment, and tip information to 7shifts' and requires 'user assignments to orders/sales in Qu POS', establishing per-employee tip capture in Qu. Shortfall: pool contribution rules, distribution calculation, reports and payroll export all live in 7shifts' separately licensed Tip Pooling module, not in Qu — Qu publishes no first-party tip-pool ledger or export (its help centre is login-gated). Article HTML is bot-gated; body read via the site's public Zendesk article API for the same article id. https://kb.7shifts.com/hc/en-us/articles/35540967177875-Tip-Pooling-for-Qu-POS · retrieved 2026-08-03

labor-qualified-tips-w2-reporting differentiator

Report Calculations (First Gen 2.0, updated 2020-04-20, archived 2020-12-01) shows the Tip Track report separating the two tip populations explicitly: 'Total Receipts = Gross Sales + Charged Tips + Cash Tips' and 'Total Direct Tips = Charged Tips + Cash Tips'; the Next Gen Labor reports add a Tip report that 'Displays all tips collected by each employee' and a Payroll Summary of regular/overtime hours and earnings per employee. Shortfall: cash-versus-charged separation is present but nothing in the corpus carries a Treasury tipped-occupation code, a W-2 Box 12 code TP field or Box 14b output, and no payroll-export format is documented at all. Vintage: First Gen 2.0 / Next Gen 3.5, 2017-2020 - this documentation predates the TY2026 requirement entirely, so the missing conjunct is untested rather than refuted. https://web.archive.org/web/20201201062202/https://support.qubeyond.com/hc/en-us/articles/115006316228 · retrieved 2026-09-03

labor-native-payroll differentiator

Re-evidenced 2026-08-08 after the cited /products/ page went dead. The /platform Platform Solutions navigation enumerates the complete catalog - ordering, kitchen, payments and platform management - with no payroll or HR product, and /management's five products (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify, Unified Data & Reporting) name no labor function at all. Positively, Qu's own integrations directory (all 120 partners enumerated) files payroll under "Back of House + Labor" as a partner category: Proliant (payroll processing), alongside 7shifts, HotSchedules, Harri and Workstream. Qu does not file tax or run direct deposit itself. https://www.qubeyond.com/integrations · retrieved 2026-08-08

labor-payroll-export-formats

Qu's certified-partner directory (Webflow CMS, walked ?12898331_page=1..14, 121 items served against a page label reading 'Showing 1 to 9 of 150') lists under category 'Back of House + Labor': Proliant (proliant.com), Fourth/HotSchedules (fourth.com/product/hotschedules), Altametrics, 7shifts, Harri and Workstream. Qu's own post 'What Qu's Doubled Integration Network Means For You' (qubeyond.com/resource-center/what-qus-doubled-integration-network-means-for-you, grade D) groups them explicitly: 'Labor Management: Optimize your workforce with sophisticated tools from HotSchedules, Proliant, and Rippling.' So direct certified integration with at least two payroll/HCM providers exists. Shortfall: payroll reaches the operator only through those third-party partners -- Qu publishes no export file format or field list, neither the directory nor the post states that timecards, wages or tips are the data exchanged, and none of Gusto, ADP, Paychex or QuickBooks appears anywhere in the 121-partner directory or the 239-page qubeyond.com corpus (Rippling is named in the post but is absent from the directory, so the directory is not exhaustive). https://www.qubeyond.com/integrations · retrieved 2026-09-03

labor-shift-swap-workflow differentiator

Re-evidenced 2026-08-08: /about/qu-technology-partners/ now 301s to /integrations. Qu ships no native scheduling product - the enumerated platform (Omnichannel Ordering, Smart Kitchen Solutions, Qu Pay, Unified Platform Management; fourteen products, matching the sitemap product tree) has no workforce module, and the integrations directory's 'Back of House + Labor' category lists 7shifts, Altametrics, HotSchedules, Harri and Workstream. With no schedule to swap against and no employee self-service app in the line-up, there is no shift-swap or open-shift-claim workflow with manager approval in Qu itself; those are properties of the partner scheduling product. https://www.qubeyond.com/integrations · retrieved 2026-08-08 adversarially verified

labor-digital-onboarding-i9

Re-evidenced 2026-08-08 after the cited /products/ page went dead. The /platform Platform Solutions navigation enumerates the entire product line with no HR, hiring or onboarding module, and /management's five products name no employee function. Qu's own integrations directory (all 120 partners enumerated) places hiring and onboarding in the "Back of House + Labor" partner category - Workstream and Harri are both hiring/onboarding platforms, with 7shifts and HotSchedules for scheduling and Proliant for payroll. No Qu-published page mentions W-4, I-9 or E-Verify. https://www.qubeyond.com/integrations · retrieved 2026-08-08

labor-server-performance-metrics differentiator

Qu Reports Quick Guide (Next Gen 3.5, Oct 2020) documents per-employee exception metrics - 'Voided Items - Displays all voided items by an employee', 'Refunds - Lists all refunded checks by an employee', 'Labor Red Flag - Displays the total activity for several KPIs. This report is useful for analyzing whether the store or employee uses specific actions (e.d voids) too often' - plus an employee filter on every report so sales can be sliced per cashier. Shortfall: void and refund activity by employee is documented but average check per server, items-per-check and category attachment rate are not; comps are folded into discounts ('Discounts generally include manager comps and coupons', Report Calculations) with no per-employee comp rate. Vintage: Next Gen 3.5, 2020 archived help centre. https://web.archive.org/web/20201128174707/https://support.qubeyond.com/hc/en-us/articles/360049022511-Qu-Reports-Quick-Guide-Next-Gen- · retrieved 2026-09-03

inventory-recipe-bom-costing

Re-evidenced 2026-08-08 after the cited /products/ page went dead. The /platform Platform Solutions navigation enumerates the complete catalog - Omnichannel Ordering, Smart Kitchen Solutions, Smart Payment Solutions, Unified Platform Management, Qube, Qu Equip, Qu Business Edge - with no inventory module, and neither /management nor /kitchen names inventory, recipes or food cost. Qu's own integrations directory (all 120 partners enumerated) carries nine inventory and recipe-costing vendors under "Back of House + Labor": MarketMan, Restaurant365, Crunchtime, Compeat, COGS-Well, Decision Logic, SynergySuite, Altametrics and Rosnet. Multi-level recipe/BOM costing is bought from one of those, not built into Qu. https://www.qubeyond.com/integrations · retrieved 2026-08-08

inventory-unit-conversion-yields

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. purchase/recipe/count units with conversion factors and a yield percentage are attributes of an inventory item master. The /platform Platform Solutions catalog enumerates every product family Qu sells - Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Smart Payment Solutions (Qu Pay), Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify, Unified Data & Reporting), Qube, Qu Equip and Qu Business Edge - and there is no inventory, purchasing or food-cost product among them. I re-fetched the whole 233-URL sitemap on 2026-08-08 and searched the rendered text: "par level", "purchase order", "spoilage", "depletion" and "commissary" return zero occurrences anywhere on qubeyond.com, and "invoice" appears only in a blog post about POS billing. Qu's own /integrations directory, walked page by page through all 17 pages (121 named partners), files nineteen vendors under "Back of House + Labor" including MarketMan, Restaurant365, Crunchtime, Compeat, COGS-Well, Decision Logic, SynergySuite, Altametrics, Rosnet, Ctuit and Buyers Edge Platform. Unit conversion and yield are configured in whichever of those the operator buys, not in Qu. https://www.qubeyond.com/platform · retrieved 2026-08-08

inventory-theoretical-vs-actual differentiator

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. a theoretical-vs-actual variance report needs both recipe-driven theoretical usage and counted actual usage, and Qu ships neither. The /platform Platform Solutions catalog enumerates every product family Qu sells - Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Smart Payment Solutions (Qu Pay), Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify, Unified Data & Reporting), Qube, Qu Equip and Qu Business Edge - and there is no inventory, purchasing or food-cost product among them. The word "theoretical" occurs exactly once on qubeyond.com, in an unrelated sentence about connectivity risk. Qu's own /integrations directory, walked page by page through all 17 pages (121 named partners), files nineteen vendors under "Back of House + Labor" including MarketMan, Restaurant365, Crunchtime, Compeat, COGS-Well, Decision Logic, SynergySuite, Altametrics, Rosnet, Ctuit and Buyers Edge Platform. Variance reporting is what those partners sell. https://www.qubeyond.com/platform · retrieved 2026-08-08

inventory-realtime-depletion differentiator

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. Qu's actual item-availability mechanism is manual, not ingredient-driven. The Fall 2025 release highlights describe it plainly: "Notify Item Availability: Manage in and out of stock items anywhere - Mark items in/out of stock from your phone and set a 'Revive Date' to auto-restock later." A product that ships a manual in/out-of-stock toggle with a timed revive is not depleting ingredient on-hand quantities as orders fire. "Depletion" returns zero occurrences across the whole site, and the /platform Platform Solutions catalog enumerates every product family Qu sells - Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Smart Payment Solutions (Qu Pay), Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify, Unified Data & Reporting), Qube, Qu Equip and Qu Business Edge - and there is no inventory, purchasing or food-cost product among them. https://www.qubeyond.com/resource-center/qus-fall-2025-product-release-highlights · retrieved 2026-08-08

inventory-86-auto-sync differentiator

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. the propagation half is real and the trigger half is not. /ordering/pos states "Price changes, modifiers, and 86'd items update everywhere simultaneously with no manual sync required", and the Fall 2025 release highlights give the mechanism: "Notify Item Availability ... Mark items in/out of stock from your phone and set a 'Revive Date' to auto-restock later." The 86 is entered by a human and revived on a clock. Threshold-driven auto-86 needs ingredient on-hand levels, and the /platform Platform Solutions catalog enumerates every product family Qu sells - Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Smart Payment Solutions (Qu Pay), Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify, Unified Data & Reporting), Qube, Qu Equip and Qu Business Edge - and there is no inventory, purchasing or food-cost product among them. https://www.qubeyond.com/resource-center/qus-fall-2025-product-release-highlights · retrieved 2026-08-08

inventory-count-modes

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. full physicals, spot counts and recurring cycle counts with retained per-count variance history all presuppose a count ledger. The /platform Platform Solutions catalog enumerates every product family Qu sells - Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Smart Payment Solutions (Qu Pay), Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify, Unified Data & Reporting), Qube, Qu Equip and Qu Business Edge - and there is no inventory, purchasing or food-cost product among them. I re-fetched the whole 233-URL sitemap on 2026-08-08 and searched the rendered text: "par level", "purchase order", "spoilage", "depletion" and "commissary" return zero occurrences anywhere on qubeyond.com, and "invoice" appears only in a blog post about POS billing. Qu's own /integrations directory, walked page by page through all 17 pages (121 named partners), files nineteen vendors under "Back of House + Labor" including MarketMan, Restaurant365, Crunchtime, Compeat, COGS-Well, Decision Logic, SynergySuite, Altametrics, Rosnet, Ctuit and Buyers Edge Platform. https://www.qubeyond.com/platform · retrieved 2026-08-08

inventory-mobile-count-offline

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. Qu's mobile app is Qu Notify, and its own page enumerates its key features: "Customizable Real-Time Alerts", "Intelligent Data Access" (voice commands and an AI chatbot), "Visual Analytics & Forecasting" and "Performance Reporting". Its FAQ describes it as "a mobile insights app ... that delivers real-time operational alerts, AI-driven insights, end-of-day summaries, and a real-time Kitchen Intelligence Score". No counting workflow, no barcode or QR scanning, no offline count buffer. The /platform Platform Solutions catalog enumerates every product family Qu sells - Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Smart Payment Solutions (Qu Pay), Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify, Unified Data & Reporting), Qube, Qu Equip and Qu Business Edge - and there is no inventory, purchasing or food-cost product among them. https://www.qubeyond.com/management/notify-mobile-insights · retrieved 2026-08-08

inventory-vendor-catalogs-edi differentiator

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. there is no purchasing surface to hang EDI on. The phrase "purchase order" returns zero occurrences across all 233 pages of qubeyond.com, no broadline distributor (Sysco, US Foods, PFG) appears anywhere on the site, and the /platform Platform Solutions catalog enumerates every product family Qu sells - Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Smart Payment Solutions (Qu Pay), Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify, Unified Data & Reporting), Qube, Qu Equip and Qu Business Edge - and there is no inventory, purchasing or food-cost product among them. Qu's own /integrations directory, walked page by page through all 17 pages (121 named partners), files nineteen vendors under "Back of House + Labor" including MarketMan, Restaurant365, Crunchtime, Compeat, COGS-Well, Decision Logic, SynergySuite, Altametrics, Rosnet, Ctuit and Buyers Edge Platform. Buyers Edge Platform, the one procurement name in the directory, is a partner rather than a Qu module. https://www.qubeyond.com/integrations · retrieved 2026-08-08

inventory-invoice-ocr differentiator

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. the word "invoice" appears on exactly one page of qubeyond.com, a blog post about POS billing practices, and never as a product capability. The /platform Platform Solutions catalog enumerates every product family Qu sells - Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Smart Payment Solutions (Qu Pay), Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify, Unified Data & Reporting), Qube, Qu Equip and Qu Business Edge - and there is no inventory, purchasing or food-cost product among them. Invoice capture is supplied by partners in the enumerated /integrations directory - marginedge under Analytics, and Restaurant365, Compeat and Crunchtime under "Back of House + Labor". https://www.qubeyond.com/integrations · retrieved 2026-08-08

inventory-price-change-alerts differentiator

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. per-item purchase price history is a purchasing-ledger feature and Qu has no purchasing ledger: "purchase order" and "invoice" as a capability return zero hits site-wide. Qu Notify's alerting is enumerated on its own page as "sales anomalies, service-time thresholds, equipment issues, the real-time Kitchen Intelligence Score, and other configurable operational exceptions" - no received-price threshold among them. Qu's own /integrations directory, walked page by page through all 17 pages (121 named partners), files nineteen vendors under "Back of House + Labor" including MarketMan, Restaurant365, Crunchtime, Compeat, COGS-Well, Decision Logic, SynergySuite, Altametrics, Rosnet, Ctuit and Buyers Edge Platform. https://www.qubeyond.com/integrations · retrieved 2026-08-08

inventory-par-auto-suggest differentiator

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. "par level" returns zero occurrences across all 233 pages of qubeyond.com. The nearest thing Qu ships is Smart Kitchen production forecasting - /platform: "Smart Kitchen uses production forecasting and kitchen load balancing to help teams stay ahead of demand and prepare the right amount of food at the right time" - which forecasts prep quantities for the line, not order quantities against a stocked par, and produces no purchase order. Qu's own /integrations directory, walked page by page through all 17 pages (121 named partners), files nineteen vendors under "Back of House + Labor" including MarketMan, Restaurant365, Crunchtime, Compeat, COGS-Well, Decision Logic, SynergySuite, Altametrics, Rosnet, Ctuit and Buyers Edge Platform. https://www.qubeyond.com/platform · retrieved 2026-08-08

inventory-waste-logging

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. "spoilage" returns zero occurrences site-wide, and every use of "waste" on qubeyond.com is an outcome claim, not a logging feature - /platform: production planning means "less waste, better throughput"; /kitchen-solutions/energy-equipment-intelligence flags "energy waste". Reason-coded waste entries that debit stock and report waste cost apart from usage variance require an inventory ledger, and the /platform Platform Solutions catalog enumerates every product family Qu sells - Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Smart Payment Solutions (Qu Pay), Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify, Unified Data & Reporting), Qube, Qu Equip and Qu Business Edge - and there is no inventory, purchasing or food-cost product among them. Qu's own /integrations directory, walked page by page through all 17 pages (121 named partners), files nineteen vendors under "Back of House + Labor" including MarketMan, Restaurant365, Crunchtime, Compeat, COGS-Well, Decision Logic, SynergySuite, Altametrics, Rosnet, Ctuit and Buyers Edge Platform. https://www.qubeyond.com/platform · retrieved 2026-08-08

inventory-transfers

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. a two-sided transfer with an in-transit state requires per-location stock balances to credit and debit. The /platform Platform Solutions catalog enumerates every product family Qu sells - Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Smart Payment Solutions (Qu Pay), Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify, Unified Data & Reporting), Qube, Qu Equip and Qu Business Edge - and there is no inventory, purchasing or food-cost product among them. I re-fetched the whole 233-URL sitemap on 2026-08-08 and searched the rendered text: "par level", "purchase order", "spoilage", "depletion" and "commissary" return zero occurrences anywhere on qubeyond.com, and "invoice" appears only in a blog post about POS billing. Multi-location functionality on /management is menu, channel and brand configuration plus cross-brand reporting - no stock movement between stores. Qu's own /integrations directory, walked page by page through all 17 pages (121 named partners), files nineteen vendors under "Back of House + Labor" including MarketMan, Restaurant365, Crunchtime, Compeat, COGS-Well, Decision Logic, SynergySuite, Altametrics, Rosnet, Ctuit and Buyers Edge Platform. https://www.qubeyond.com/platform · retrieved 2026-08-08

inventory-commissary

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. "commissary" and "central kitchen" return zero occurrences across all 233 pages of qubeyond.com. The /platform Platform Solutions catalog enumerates every product family Qu sells - Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Smart Payment Solutions (Qu Pay), Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify, Unified Data & Reporting), Qube, Qu Equip and Qu Business Edge - and there is no inventory, purchasing or food-cost product among them. Smart Kitchen Solutions covers KDS, Order Status and equipment monitoring for a single restaurant's line; nothing issues prep items to other locations at a computed transfer cost. Qu's own /integrations directory, walked page by page through all 17 pages (121 named partners), files nineteen vendors under "Back of House + Labor" including MarketMan, Restaurant365, Crunchtime, Compeat, COGS-Well, Decision Logic, SynergySuite, Altametrics, Rosnet, Ctuit and Buyers Edge Platform. https://www.qubeyond.com/platform · retrieved 2026-08-08

inventory-lot-traceability

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. lot capture at receiving presupposes a receiving function, and Qu has none: "purchase order" and "invoice" as capabilities return zero hits site-wide, and the /platform Platform Solutions catalog enumerates every product family Qu sells - Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Smart Payment Solutions (Qu Pay), Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify, Unified Data & Reporting), Qube, Qu Equip and Qu Business Edge - and there is no inventory, purchasing or food-cost product among them. No recall, traceability or lot/batch language appears anywhere in the re-fetched corpus. Qu's own /integrations directory, walked page by page through all 17 pages (121 named partners), files nineteen vendors under "Back of House + Labor" including MarketMan, Restaurant365, Crunchtime, Compeat, COGS-Well, Decision Logic, SynergySuite, Altametrics, Rosnet, Ctuit and Buyers Edge Platform. https://www.qubeyond.com/platform · retrieved 2026-08-08

inventory-shelf-life-expiry

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. expiry tracking needs dated received or prepped stock records. The /platform Platform Solutions catalog enumerates every product family Qu sells - Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Smart Payment Solutions (Qu Pay), Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify, Unified Data & Reporting), Qube, Qu Equip and Qu Business Edge - and there is no inventory, purchasing or food-cost product among them. I re-fetched the whole 233-URL sitemap on 2026-08-08 and searched the rendered text: "par level", "purchase order", "spoilage", "depletion" and "commissary" return zero occurrences anywhere on qubeyond.com, and "invoice" appears only in a blog post about POS billing. The only date-driven availability feature Qu documents is the Fall 2025 "Revive Date" on a manually 86'd menu item, which restores an item on a schedule rather than warning that stock is about to expire. Qu's own /integrations directory, walked page by page through all 17 pages (121 named partners), files nineteen vendors under "Back of House + Labor" including MarketMan, Restaurant365, Crunchtime, Compeat, COGS-Well, Decision Logic, SynergySuite, Altametrics, Rosnet, Ctuit and Buyers Edge Platform. https://www.qubeyond.com/platform · retrieved 2026-08-08

inventory-bar-partial-bottle

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. Qu is a multi-unit QSR and fast-casual platform (/payments/qu-pay: "Qu Pay is built for multi-unit QSR") with no inventory ledger at all, let alone weight-based or fractional bottle counting; no scale integration appears among the 121 enumerated partners. Beverage-level monitoring in Qu's ecosystem is a partner concern - DigitalPour is listed under "Back of House + Labor" in /integrations. https://www.qubeyond.com/integrations · retrieved 2026-08-08

inventory-cogs-gl-export

Accounting is a listed partner category and Restaurant365 publishes a Qu POS connector; Qu ships no first-party GL export with mapping. https://www.restaurant365.com/partners/qu-pos/ · retrieved 2026-08-01

inventory-native-not-partner differentiator

Inventory and recipe costing are explicitly partner-delivered (MarketMan, Restaurant365) and absent from Qu's enumerated product catalog. https://www.marketman.com/partner/qu · retrieved 2026-08-01

inventory-menu-margin-linkage differentiator

Re-evidenced 2026-08-08: the cited https://qubeyond.com/products/ now 301s to the homepage, so the original "no native inventory module" leg is withdrawn and replaced. contribution margin per item requires recipe cost, which Qu does not compute - "recipe" never appears on qubeyond.com as a capability, and the /platform Platform Solutions catalog enumerates every product family Qu sells - Omnichannel Ordering (POS, Kiosk, Drive-Thru, Online Ordering, Third-Party Ordering), Smart Kitchen Solutions (KDS, Order Status, Energy & Equipment Intelligence), Smart Payment Solutions (Qu Pay), Unified Platform Management (Unified Menu Management, Channel Management, Brand & Franchise Management, Qu Notify, Unified Data & Reporting), Qube, Qu Equip and Qu Business Edge - and there is no inventory, purchasing or food-cost product among them. Qu's analytics surface, Unified Data & Reporting plus Qu Notify, is enumerated as sales, labor, channel, service-time and equipment metrics with no cost-of-goods input. Qu's own /integrations directory, walked page by page through all 17 pages (121 named partners), files nineteen vendors under "Back of House + Labor" including MarketMan, Restaurant365, Crunchtime, Compeat, COGS-Well, Decision Logic, SynergySuite, Altametrics, Rosnet, Ctuit and Buyers Edge Platform. marginedge is additionally listed under Analytics. https://www.qubeyond.com/integrations · retrieved 2026-08-08

reporting-realtime-dashboard

Unified Data & Reporting plus the Qu Notify mobile app; Qu claims live system-wide data access in under two seconds. https://www.qubeyond.com/management/unified-data-reporting · retrieved 2026-08-01

reporting-eod-closeout

Qu Notify delivers end-of-day summaries; a full reconciling close-out document (tax, tips, tenders, expected deposit) is not documented. https://www.qubeyond.com/management/notify-mobile-insights · retrieved 2026-08-01

reporting-pmix-modifier-level

Product page FAQ: "Qu lets operators compare performance across locations, dayparts, and channels in one view, surfacing top performers, operational gaps, and revenue opportunities without exporting data to spreadsheets." Item-level sales are evidenced on the Notify blog, whose dashboard list includes "Net Sales, Check Counts, Payments, Average Check Size, Gross Sales, Discounts, Cash, Voids, Service Charges, Taxes, Item Sales & Gift Card Sales" (qubeyond.com/resource-center/finally-an-app-that-saves-your-store-managers-time-money). SHORTFALL: nothing on any of the 239 reachable qubeyond.com pages describes a product-mix report at MODIFIER level, nor an item-level gross-vs-net sales split, nor a revenue-center filter. No grade-A/B documentation exists to check: qu-api.qubeyond.com and qu-pos-api.qubeyond.com both answer with a Microsoft *.azurewebsites.net certificate (TLS altname mismatch) and support.qubeyond.com 302s every path to /login. https://www.qubeyond.com/management/unified-data-reporting · retrieved 2026-09-03

reporting-comps-voids-audit

Notify's dashboard metric list includes "Discounts, Cash, Voids, Service Charges" and alerts can be configured on "staff overtime, cash, voids, and more". The Winter 2025 release post adds Notify Check Search, which "allows staff to filter transaction data based on a wide range of criteria, including Date, Employee, and Order Type". SHORTFALL: voids and discounts appear only as aggregate dashboard metrics plus a generic transaction filter; no reachable Qu page describes a comps/voids/override audit report carrying reason codes, timestamps, the applying employee AND the approving manager. Qu publishes no help centre or admin guide (support.qubeyond.com login-walled; both qu-api hosts fail TLS identity), so no grade-A/B source exists to settle it. https://www.qubeyond.com/resource-center/finally-an-app-that-saves-your-store-managers-time-money · retrieved 2026-09-03

reporting-cash-over-short

Fall 2025 release: "We've added a single 'Reports' button on the POS that consolidates End of Day, End of Shift, and Tills reports in one spot." Notify separately alerts on "Cash" as a monitored metric. SHORTFALL: a Tills report at the terminal is evidenced, but no reachable Qu surface states that it computes an over/short variance (counted cash vs expected cash from tenders and paid-outs) or attributes that variance per drawer and per employee. No vendor documentation is reachable to confirm the report's contents (support portal login-walled; both API hosts fail TLS identity). https://www.qubeyond.com/resource-center/qus-fall-2025-product-release-highlights · retrieved 2026-09-03

reporting-labor-productivity

Labor metrics alongside sales are surfaced in Notify; sales-per-labor-hour by hour/department/employee is not documented. https://www.qubeyond.com/management/notify-mobile-insights · retrieved 2026-08-01

reporting-server-scorecards differentiator

Qu Reports Quick Guide (Next Gen 3.5, Oct 2020): every report carries an 'Employee Filter - Each report shows data for all employees, and the user can filter them to display data for a specific employee'; the Labor group includes a Tip report ('Displays all tips collected by each employee') and a Labor Red Flag report ('Displays the total activity for several KPIs... useful for analyzing whether the store or employee uses specific actions (e.d voids) too often'); Voided Items 'Displays all voided items by an employee' and Refunds 'Lists all refunded checks by an employee'. Shortfall: there is no per-server scorecard object - average check appears only on Hourly Sales (by hour, not by server), and items per check, category attachment rate and tips as a percentage of sales are not documented anywhere in the catalogue. Vintage: Next Gen 3.5, 2020. https://web.archive.org/web/20201128174707/https://support.qubeyond.com/hc/en-us/articles/360049022511-Qu-Reports-Quick-Guide-Next-Gen- · retrieved 2026-09-03

reporting-channel-profitability differentiator

Reporting is channel-aware and Qu argues "different channels have different economics"; margin net of marketplace commission is not documented. https://www.qubeyond.com/management/channel-management · retrieved 2026-08-01

reporting-multiloc-drilldown differentiator

Product page FAQ: "Qu lets operators compare performance across locations, dayparts, and channels in one view, surfacing top performers, operational gaps, and revenue opportunities." Notify adds "Monitor one store, a group of stores, or your full enterprise from one screen" and Check Search, which displays individual checks chronologically filtered by Date/Employee/Order Type. SHORTFALL: side-by-side location comparison and transaction-level lookup exist as SEPARATE features; no reachable page documents a continuous drill path from group total to one location to one transaction - and Qu markets Notify as delivering "Real-time insights in feed format - no drill-downs required!". Differentiator weight and the best available source is a grade-C feature page, so `yes` is not available. https://www.qubeyond.com/management/unified-data-reporting · retrieved 2026-09-03 adversarially verified

reporting-custom-report-builder differentiator

"Data-rich reporting and insights with deep customization options" claimed; a named self-service dimension/measure builder is not documented. https://www.qubeyond.com/management/unified-data-reporting · retrieved 2026-08-01

reporting-scheduled-delivery

Qu Reports Quick Guide (Next Gen 3.5, updated 2020-10-19, archived 2020-11-28): 'the user can save each report as a custom report (with the filters and customizations that you have selected), scheduled (to be emailed regularly), exported (downloaded or emailed as either an Excel file, CSV, or PDF), and printed' - i.e. any report in the catalogue, not a fixed subset. The companion article 'How do I schedule reports to auto-send? (Next Gen)' gives the mechanics: select the report, Click Schedule, then set Send Time, Time Zone, Frequency and Employees (recipients must have an email on their profile). The First Gen 2.0 admin guide documents the same Email Reports feature from 2017. Vintage: Qu Next Gen 3.5, 2020 archive; not re-verified against today's Intelligent Commerce Platform, but recurring emailed reports are a basic mechanic and the live Brand & Franchise Management page still lists 'Native reporting and notification capabilities'. https://web.archive.org/web/20201128174707/https://support.qubeyond.com/hc/en-us/articles/360049022511-Qu-Reports-Quick-Guide-Next-Gen- · retrieved 2026-09-03

reporting-raw-warehouse-export differentiator

A DataExport API component exists and Qu supports API connections to external BI tools; scheduled push to a customer-controlled S3/SFTP/warehouse is not documented. https://status.qubeyond.com/ · retrieved 2026-08-01

reporting-public-api differentiator

A REST Data Access API exists and is documented: 'All Data Access API calls prefixed with api/v3', with basket/order endpoints under customers/{customerId}/locations/{locationId}/baskets. But the documentation is no longer served -- qu-pos-api.qubeyond.com and qu-api.qubeyond.com both return Azure's 'Error 403 - This web app is stopped' (HTTP 403 Site Disabled, 1148 bytes) on 2026-08-09, and Wayback shows that same stopped-app page from 2023-12-30 onward; the quoted text is from the last good capture (2022-07-24). Documented scope is ordering/baskets only, not payments, menu or labor. No self-serve credentials: support.qubeyond.com redirects every path to a Document360 OIDC login, and integrations are onboarded by partner certification. https://web.archive.org/web/20220724113646/https://qu-pos-api.qubeyond.com/ · retrieved 2026-08-09

reporting-webhooks differentiator

Publication/capability split applied strictly: the claim's head verb is 'Emits', a capability. 'webhook' returns zero hits in the 199-page corpus and zero in the Adyen contract, and Qu publishes no API documentation anywhere (docs./api./developer./developers.qubeyond.com are ENOTFOUND, support.qubeyond.com 302s every path, no llms.txt), so an unpublished partner webhook contract remains a live possibility. Marketing 'open API' / 'bi-directional' copy is grade-C brochure language that enumerates no event or retry semantics. May not be scored `no`.

reporting-api-not-upcharged differentiator

Commercial claim, not a publication claim. Qu publishes no pricing of any kind; the /become-a-partner page is a HubSpot lead form with no fee, revenue-share or certification-cost statement, and the integrations page's only programme prose is 'Our robust certification process ensures that integrations are tested and reliable.' The Adyen contract governs payments economics only and never mentions API or data-access fees. Nothing public establishes whether raw-data access is included or gated.

reporting-tier-paywall differentiator

Commercial claim. Qu publishes no plan structure, tier names, or feature-by-tier matrix on any of the 239 sitemap URLs, and /integrations and /become-a-partner add nothing about packaging. The Adyen contract addresses payments economics and is silent on subscription tiers. Which reporting features sit on an entry-level plan cannot be determined.

reporting-history-retention differentiator

Non-publication, measured across two product generations rather than inferred from the marketing site. Qu's help centre was public on Zendesk 2019-2021 and 210 articles survive in the Wayback CDX index; 'retention'/'retain' occurs in none of them, including every document that would carry a window -- the Reporting Guide (which enumerates each report and its calculations), Report Calculations, the Enterprise Intelligence Guide, 'How do I Set the Reporting Periods for My Store', 'Qu 3.5 Reporting Documentation', Chapter 5: Reporting, and Chapter 12: Audit Trail, which states only that 'Audit Trail can only be accessed from the Enterprise Level of Qu Enterprise Intelligence' and names no window. Live side, management/unified-data-reporting says only 'historical data' with no figure, and the privacy policy's retention clause is scoped to website visitors. The claim's verb is 'Documents', so non-publication is the finding. Caveat: the current help centre is login-gated, so a gated admin guide could state a window we cannot see; this rests on the enumerated public and archived reporting documentation. https://web.archive.org/web/20210125165411/https://support.qubeyond.com/hc/en-us/articles/360049022511 · retrieved 2026-09-03

reporting-anomaly-alerts differentiator

Re-fetched 2026-08-02. Qu Notify "pushes AI-powered alerts on sales anomalies, service-time thresholds, equipment issues, the real-time Kitchen Intelligence Score, and other configurable operational exceptions, delivered straight to mobile devices". Shortfall: no threshold-configuration mechanism is shown, no definition of what constitutes an anomaly (baseline, sensitivity, comparison window), and the page does not say whether Qu Notify is included with the platform or separately licensed; its quantified benefit claim ("30-50% faster issue resolution") is unsourced. Qu publishes no publicly retrievable product documentation: support.qubeyond.com (the 'Qu Campus' Document360 portal) redirects to a login, and both qu-api.qubeyond.com and qu-pos-api.qubeyond.com return HTTP 403 behind a mismatched TLS certificate. No grade A/B evidence is obtainable, so a differentiator 'yes' cannot stand. https://www.qubeyond.com/management/notify-mobile-insights · retrieved 2026-08-02 adversarially verified

reporting-nl-query

Verified verbatim is a single marketing line: 'Operate hands-free with simple voice commands and surface insights through an AI chatbot.' No product documentation, no examples of queries, no scope of data addressable. Marketing copy for an AI feature is the single most inflated category in this space; a 'yes' needs docs. https://www.qubeyond.com/management/notify-mobile-insights · retrieved 2026-08-01 adversarially verified

reporting-guest-cohorts differentiator

Qu Reports Quick Guide (Next Gen 3.5, Oct 2020) enumerates a Customers report: 'Included all customers and their information entered on the POS or the web ordering site. The collected information includes first name, last name, phone number, email address, last order date, total orders, the total dollar amount spent, and registration status.' That is guest-level lifetime spend and visit count tied to identifiable records from POS and online ordering. Shortfall: the report is a flat customer list - the guide documents no new-versus-returning guest counts, no visit-frequency cohorting and no loyalty-linked segmentation (loyalty in this vintage is the third-party Punchh integration). Vintage: Next Gen 3.5, 2020; the live site markets 'normalized guest and operational data' but publishes no cohort report. https://web.archive.org/web/20201128174707/https://support.qubeyond.com/hc/en-us/articles/360049022511-Qu-Reports-Quick-Guide-Next-Gen- · retrieved 2026-09-03

reporting-sales-forecast differentiator

Notify claims predictive analytics for trend forecasting and the menu module claims AI demand/daypart analysis; a daypart-granular forecast surface consumable by scheduling is not documented. https://www.qubeyond.com/management/notify-mobile-insights · retrieved 2026-08-01

reporting-tip-tax-compliance

7shifts' 'Tip Pooling for Qu POS' doc (updated 2026-06-24) states 'Qu automatically transfers sales, payment, and tip information to 7shifts', so per-employee tip capture exists in Qu. Shortfall: the payroll- and tax-ready outputs this claim names are not Qu's — 'within 7shifts, the distribution of tips and gratuities among employees is automated' in a Tip Pooling module operators 'trial or purchase' separately, and neither declared-vs-charged tip breakdowns nor a jurisdictional tax liability summary is documented anywhere public for Qu itself (help centre login-gated). Article HTML is bot-gated; body read via the site's public Zendesk article API for the same article id. https://kb.7shifts.com/hc/en-us/articles/35540967177875-Tip-Pooling-for-Qu-POS · retrieved 2026-08-04

multi-location-org-hierarchy

Brand administration with dynamic store groupings and location-based customization inside one enterprise tenant. https://www.qubeyond.com/management/brand-franchise-management · retrieved 2026-08-01

multi-location-central-menu-publish

Single menu database publishes to all locations and channels in one action; a publish/version history showing what was pushed, when, and by whom is not documented. https://www.qubeyond.com/management/unified-menu-management · retrieved 2026-08-01

multi-location-local-override-policy differentiator

"Standardize where it matters and customize where it counts" with local overrides within approved parameters; per-field lock enforcement is not documented. https://www.qubeyond.com/management/brand-franchise-management · retrieved 2026-08-01

multi-location-price-zones

This is the researcher's own two-step inference ('dynamic store groupings' + 'channel-specific pricing' therefore price zones). Neither cited page documents assigning a price to a location group. Inference stacking is not documentation. https://www.qubeyond.com/management/channel-management · retrieved 2026-08-01 adversarially verified

multi-location-scheduled-publish differentiator

Fall 2025 release: "A new set of icons shows each menu's status, version, and update schedule - all available through the POS", distinguishing "what's live, what's pending, and what needs attention"; the Fall 2025 recap calls these "traffic light menu status indicators so your team always knows what's live, updating, or needs attention". SHORTFALL: a pending/scheduled menu update is evidenced, but no reachable Qu page states that the activation time is interpreted in each target location's own timezone, nor that an activated change can be rolled back. Differentiator weight with only grade-D evidence, so `yes` is unavailable regardless. https://www.qubeyond.com/resource-center/qus-fall-2025-product-release-highlights · retrieved 2026-09-03

multi-location-new-store-template differentiator

Winter 2026 release, under "Enterprise Agility & Rollout Speed": "Consistent Store Creation with Templates - Pre-built configuration templates standardize new store setup across formats", with the stated advantage "Reduce human error, accelerate openings, and ensure operational consistency from day one". SHORTFALL: the claim's second half is unmet - Qu publishes no expected time-to-open for a templated new location, and the template's contents (menu, taxes, roles, printers, modifiers, tenders) are not enumerated anywhere reachable; the customer portal that would carry a setup guide is login-walled. https://www.qubeyond.com/resource-center/qus-winter-2026-product-release-highlights · retrieved 2026-09-03

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

Franchisor enforces brand standards centrally while franchisees operate locally on Qube, with granular permissioning; a distinct franchisee tenant owning its own banking/labor data is not documented. https://www.qubeyond.com/management/brand-franchise-management · retrieved 2026-08-01

multi-location-royalty-calculation differentiator

Corroborates rather than upgrades the prior finding. Across the complete legal set and all 199 uncited pages the string 'royalt' occurs exactly once, in the website T&Cs' IP licence ('a non-exclusive, royalty-free, perpetual, and worldwide license'). No royalty, ad-fund or marketing-fee calculation appears anywhere, and no royalty basis is discussed. The prior sweep already read Brand & Franchise Management in full and found the same; the newly enumerated surface adds nothing, and the payments contract is silent because franchise fee administration is not its subject.

multi-location-royalty-collection

Same corpus-wide silence as royalty calculation. The Adyen contract is the one document in the set that could plausibly carry a fee-sweep mechanism, and it does describe money movement in detail — settlement, set-off, rolling reserve — but every one of those flows is between Adyen and the merchant for transaction proceeds; there is no franchisor sweep, no ACH/debit collection of fees from franchisee accounts and no franchisee-visible fee statement. Qu Pay's launch release mentions franchisee 'on-demand settlements' of their own funds, which is the opposite direction of flow.

multi-location-consolidated-reporting

Every transaction from every channel and location flows into one reporting layer with cross-location and cross-daypart comparison and real-time exception alerts. https://www.qubeyond.com/management/unified-data-reporting · retrieved 2026-08-01

multi-location-normalized-item-rollup differentiator

A single central menu database implies shared corporate item identity across locations, but Qu does not document rollup behavior for locally renamed items. https://www.qubeyond.com/management/unified-menu-management · retrieved 2026-08-01

multi-location-cross-location-giftcard

Cross-channel/cross-location gift is delivered through the Paytronix integration rather than a native Qu liability ledger. https://www.globenewswire.com/news-release/2026/06/23/3316041/0/en/paytronix-and-qu-further-integration-enabling-advanced-omnichannel-ordering-and-menu-management.html · retrieved 2026-08-01

multi-location-cross-location-loyalty

Brand-wide loyalty profile is Paytronix-delivered across in-store, drive-thru, kiosk, mobile and web. https://www.globenewswire.com/news-release/2025/10/07/3162505/0/en/paytronix-and-qu-partner-to-deliver-smarter-more-personalized-guest-experiences.html · retrieved 2026-08-01

multi-location-multi-brand differentiator

Re-fetched 2026-08-02. The brand & franchise page states "Operate every brand and location from a single system" and "Qu gives corporate teams a master control layer to enforce brand standards while franchisees can manage local overrides within approved parameters"; the online-ordering page adds "Manage multiple brands under one parent with custom subdomains and branding". Shortfall: the original note's "separately reportable revenue" per brand appears on neither page, virtual brands are not mentioned on either, and the brand/location hierarchy model is nowhere described. Multi-brand is attested at marketing level only. Qu publishes no publicly retrievable product documentation: support.qubeyond.com (the 'Qu Campus' Document360 portal) redirects to a login, and both qu-api.qubeyond.com and qu-pos-api.qubeyond.com return HTTP 403 behind a mismatched TLS certificate. No grade A/B evidence is obtainable, so a differentiator 'yes' cannot stand. https://www.qubeyond.com/management/brand-franchise-management · retrieved 2026-08-02 adversarially verified

multi-location-multi-tax-jurisdiction

Tax, pricing and discount configuration across brands and locations is claimed; jurisdiction-specific rules and per-location exemptions are not documented. https://www.qubeyond.com/management/brand-franchise-management · retrieved 2026-08-01

multi-location-multi-currency-locale

Verified verbatim on the POS page: 'Accept US Dollars, Canadian Dollars and Mexican pesos, with seamless conversion and unified reporting.' Specific and on point. https://www.qubeyond.com/ordering/pos · retrieved 2026-08-01 adversarially verified

multi-location-config-audit-log differentiator

Chapter 12: Audit Trail (First Gen 2.0, updated 2020-04-20) documents a corporate-level change log: 'a detailed activity history of changes occurring within Qu. Changes can be tracked based on Date, Employee, Module, Location and any combination of the above. The report can also be exported as a csv document. Audit Trail can only be accessed from the Enterprise Level of Qu Enterprise Intelligence.' Who / when / where / which module, queryable and CSV-exportable by corporate, is therefore established. Shortfall: the article does not enumerate which configuration objects the 'Module' axis covers - price, tax, permission and discount are each configurable per Chapter 6 but none is named as audited - and immutability is not claimed. Vintage: First Gen 2.0, article dated 2018-02-27 and updated 2020; the live site markets 'Centralized Data Governance' and 'Granular permissioning and user administration' but publishes no audit-log page. https://web.archive.org/web/20200809112957/https://support.qubeyond.com/hc/en-us/articles/360001271931-Chapter-12-Audit-Trail-First-Gen-2-0- · retrieved 2026-09-03

multi-location-enterprise-sso differentiator

Zero occurrences of SAML, SCIM, 'single sign' or SSO as a word in the legal set or the 199 pages (apparent 'OIDC' and 'SSO' hits are substrings — 'signin-oidc' in the Document360 login URL in every page footer, and 'Processor' in the Adyen contract). Qu publishes no security or trust page and no developer host exists, so staff federation for above-store users has no surface that would necessarily document it; a payments contract and a website privacy policy would not. No guest-identity feature was mistaken for staff federation here.

multi-location-enterprise-api differentiator

Reporting and DataExport APIs are enterprise-scoped and Qu markets API access to external BI; no public multi-location API reference or auth model is available. https://status.qubeyond.com/ · retrieved 2026-08-01

multi-location-central-labor-policy

What is a Payroll Profile? (Next Gen 3.5, April 2020): payroll profiles are created under Employee Groups and configure 'Weekly Overtime Starts After' plus an overtime multiplier, a daily overtime threshold, a double-overtime threshold and multiplier, and break rules (Paid or Unpaid, maximum paid time on break, minimum time on break before paid, minimum work time for paid-break eligibility). Terminal-level enforcement is documented separately in Chapter 6: Configuration, whose Labor setting reads 'Clock in Tolerance Minutes - When labor management is in use, this value limits an employee clockin to the scheduled shift time +/- the specified tolerance in minutes. Default 5' - and Chapter 6 settings are set at Enterprise level and overridden per store or revenue centre. Shortfall: the overtime and break rules attach to employee groups rather than location groups and are pay calculations applied after the fact; only clock-in tolerance is enforced at the terminal, and predictive-scheduling compliance appears nowhere in the corpus. Vintage: Next Gen 3.5 and First Gen 2.0, 2018-2020. https://web.archive.org/web/20200806012955/https://support.qubeyond.com/hc/en-us/articles/360042408211-What-is-a-Payroll-Profile-Next-Gen- · retrieved 2026-09-03

hardware-commodity-devices differentiator

The archived Hardware Videos section documents Qu running on a general-purpose Windows PC terminal built by a third-party OEM rather than a Qu-proprietary device: 'Swap SSD Hard Drive on Touch Dynamic Acrobat Terminal', 'Replace Terminal MSR (Magnetic Stripe Reader)' on a Touch Dynamic terminal, 'Removing terminal cable and port covers', and a troubleshooting step reading 'Tap the windows icon in the bottom left of the screen'. The MSR driver article names the part as a 'Magtek MagneSafe Magnetic Stripe Reader Device' reinstalled from Windows Device Manager. Shortfall: nothing documents an operator buying or supplying their own terminal - Chapter 7: POS Terminals states flatly 'Activating a new terminal must be completed by Qu' - and no iPad or Android tablet POS client appears anywhere in the 210 archived articles. Vintage: First Gen 2.0 / Next Gen 3.5, 2020 captures; today's product is the Qu Business Edge (Qube) edge appliance, which this archive predates. https://web.archive.org/web/20200920081822/https://support.qubeyond.com/hc/en-us/articles/360038050532-Swap-SSD-Hard-Drive-on-Touch-Dynamic-Acrobat-Terminal · retrieved 2026-09-03

hardware-os-platforms

No public spec sheet: the POS page names no client OS, minimum versions, or device specs, and Qu Campus documentation is login-gated. https://www.qubeyond.com/ordering/pos · retrieved 2026-08-01

hardware-handheld-purpose-built

Same evidence as order-capture-native-handheld: the drive-thru page cites mobile/tablet order-taking beyond fixed terminals. Shortfall: no purpose-built handheld with an integrated card reader is documented, and no drop rating or IP ingress rating is published anywhere on qubeyond.com. https://www.qubeyond.com/ordering/drive-thru · retrieved 2026-08-04

hardware-handheld-battery-swap differentiator

'battery' occurs zero times in 1.85 MB. Qu publishes no hardware catalogue at all — its own solutions navigation lists ordering, kitchen, payments and enterprise-management pages and nothing device-related, and /modules turned out to be an unpublished Webflow template full of lorem ipsum. The only handheld-adjacent first-party facts are Golden Chick's 'outside line-busting tablets' and an architecture line about 'store-level APIs uniformly communicate with in-store POS, kiosk, drive-through, and handheld devices'. With no hardware spec page in existence, neither the hot-swap capability nor a published shift battery rating can be assessed.

hardware-handheld-lte

No cellular or LTE reference exists anywhere on Qu's open surface ('cellular' zero hits; all 'LTE' matches are substrings). Golden Chick's case study describes tablets used outdoors for drive-thru line busting, which is precisely the deployment where an LTE fallback would matter, yet the study names no connectivity mechanism. Because Qu publishes no device specifications of any kind, the absence of an LTE mention is uninformative about whether handhelds carry or can fail over to cellular.

hardware-offline-mode

Qube edge keeps ordering, payments and kitchen routing running offline with auto-sync on reconnect; Qu publishes no list of which functions degrade. https://www.qubeyond.com/qu-business-edge · retrieved 2026-08-01

hardware-kds

QuKitchen KDS is a first-party product with its own status-page component and product page. https://www.qubeyond.com/kitchen-solutions/kitchen-display-system · retrieved 2026-08-01

hardware-kiosk differentiator

Qu Flex switches between POS and guest-facing kiosk on one device; freestanding form factor and an ADA/VPAT conformance report are not published. https://www.qubeyond.com/ordering/kiosk · retrieved 2026-08-01

hardware-drive-thru

Dedicated drive-thru software channel with voice AI partners; menu boards, confirmation displays and headsets appear only as a partner category (Hardware + Digital Signage), and no timer spec is published. https://www.qubeyond.com/ordering/drive-thru · retrieved 2026-08-01

hardware-printer-compatibility

Chapter 8: Printing (First Gen 2.0, updated 2020-04-20): 'Qu supports two types of printers: Receipt printers and kitchen printers'; receipt printers are configured per terminal by 'Scroll to Printer, select POS Printer Model... Select the desired printer model', and kitchen printers by 'Select the printer model' plus a path and routing into kitchen print groups and terminal print groups. Network attachment is documented in troubleshooting: 'Ensure the Ethernet cord is securely fastened at the printer port and the wall/switch', and disconnecting the POS 'will affect the communication between POS and any network printers'. Shortfall: a selectable model list implies more than one supported device, but the archive never names a printer manufacturer, never says ESC/POS, and publishes no compatibility list - so multi-manufacturer support is implied, not established. Vintage: First Gen 2.0, 2018-2020. https://web.archive.org/web/20200806003551/https://support.qubeyond.com/hc/en-us/articles/360001252212-Chapter-8-Printing-First-Gen-2-0- · retrieved 2026-09-03

hardware-peripherals

Chapter 6: Configuration (First Gen 2.0) enumerates a Barcode Scanner settings block ('Number of sentinel characters at end of string provided by symbol/barcode scanner (if any). These characters are removed from the scan output. Default 3', plus a start-sentinel length) and a Tills block whose 'Require Till Assignment' setting governs whether 'users must claim till in order to accept cash transactions or open, or pop, the cash drawer'. Scales are supported for by-weight items - 'Why is the Scale Not Weighing? (Next Gen)' instructs 'Remove all items from the scale, Power down the scale for thirty seconds... ensure that the scale is showing a 0.00 weight'. Customer-facing displays are a first-class output surface in the v139 release notes: modifiers 'now display with their portion amount on the same line on the Detail screen, KDS, Printers, and Customer Facing Displays.' Shortfall: no published compatibility list of any kind, and multi-drawer-per-terminal is nowhere documented. Vintage: First Gen 2.0 / Next Gen 3.5, 2018-2021. https://web.archive.org/web/20200808111044/https://support.qubeyond.com/hc/en-us/articles/360001267211-Chapter-6-Configuration-First-Gen-2-0- · retrieved 2026-09-03

hardware-p2pe-terminal

Fetched the Qu Pay page directly, the one page whose entire subject is card acceptance: it contains no PCI-listed PTS device claim, no P2PE validation statement, and no merchant SAQ type. The claim specifically requires the vendor to state the SAQ type, and nowhere on qubeyond.com does it. https://www.qubeyond.com/payments/qu-pay · retrieved 2026-08-04

hardware-tap-to-phone differentiator

'tap to pay' returns nothing and the Adyen for Platforms terms — Qu's payments contract, and the densest new document in this record — is a generic processor agreement defining Authorisation, Capture and Capture Period without enumerating acceptance form factors, so it cannot settle whether softPOS acceptance is offered. Qu routes payments through Adyen, which does offer Tap to Pay on iPhone and Android, meaning the capability could be present without appearing in any Qu-authored text. Unresolved rather than absent.

hardware-pricing-transparency differentiator

No hardware SKU prices anywhere on qubeyond.com; the only commercial path is a demo request. https://www.qubeyond.com/get-a-demo · retrieved 2026-08-01

hardware-ownership-vs-lease differentiator

Same finding as the already-scored commercial-hardware-purchase-outright: fetched the POS page directly and it names no hardware price, purchase term, or lease term at all — the only hardware reference is the Qube edge appliance with no commercial terms attached, and every commercial path funnels to the get-a-demo quote form. The vendor does not state which model applies, which is what this claim requires. https://www.qubeyond.com/ordering/pos · retrieved 2026-08-04

hardware-usable-after-churn differentiator

The claim asks whether vendor documentation confirms that vendor-purchased hardware stays usable with other software after cancellation. Qu's complete published legal set (site terms of use, privacy policy, Adyen-for-Platforms T&Cs) contains no hardware terms, no title or ownership clause for terminals or the Smart Edge device, and no post-termination hardware provision; /hardware-terms and /warranty 404 (probed 2026-09-04). Qu publishes thought-leadership arguing the lock-in risk exists at other vendors — 'Proprietary hardware means your repair options are limited' — while making no commitment about its own. No documentation confirms the position in either direction, and the contract that would is not public. adversarially verified

hardware-rma-sla differentiator

Searched the complete open surface on 2026-09-04: no hardware provision exists in any of the three published legal documents (the only 'warranty' occurrences are Adyen boilerplate on the merchant's own goods), and 'advance exchange', 'next-business-day', 'depot', 'RMA' and 'return merchandise' return zero word-boundary matches across all 199 uncited www.qubeyond.com pages; /warranty and /hardware-terms 404. The only published SLA in the set is Adyen's payment-interface uptime commitment (§6.1), which is neither Qu's nor about hardware. This is not positive evidence of absence: Qu does supply hardware (the Smart Edge in-store device), and warranty and RMA terms customarily sit in the customer contract and in support.qubeyond.com, which redirects to a Document360 login on every path. Undetermined in either direction. adversarially verified

hardware-byod

'BYOD' occurs zero times. The only personal-device workflows Qu describes are guest-facing — tableside and curbside ordering where the guest scans a QR code and orders 'directly from their mobile devices' — not staff running the ordering or payment app on their own phone. A BYOD permission and security model is precisely the kind of admin-and-security documentation Qu publishes nowhere publicly (no docs, developer, help or university host exists; support.qubeyond.com 302s on every path), so the marketing silence carries no weight for this cell.

hardware-remote-device-management differentiator

The note claims 'Qu Pay cites remote device management and nightly updates' — I fetched the Qu Pay page and it contains no device-management or nightly-update language whatsoever. The only real evidence is a status-page component literally named 'Esper KDS Device Management', i.e. a third-party MDM (Esper) scoped to KDS devices, not a Qu first-party fleet-management product covering POS/kiosk/drive-thru. https://www.qubeyond.com/payments/qu-pay · retrieved 2026-08-01 adversarially verified

hardware-selfpour-scales

Enumerated all 121 partners in Qu's certified directory across 11 facets: there is no self-pour, flow-meter or pour-spout partner (DigitalPour is filed under Back of House + Labor and is draft-beverage menu/inventory management, not pour-to-tab metering) and no beverage-hardware facet. But the directory is NOT exhaustive by Qu's own reckoning — its counter reads '150 integrations' while only 121 are served across all 14 pages — so absence from it is not load-bearing. 'self-pour' and 'tap wall' return zero corpus hits. Consistent with Qu's QSR/fast-casual ICP but not positively established.

hardware-callerid-integration

No telephony or caller-ID facet exists among the directory's 11 categories and no caller-ID partner appears among the 121 enumerated; the eight voice partners (ConverseNow, SoundHound Ai, VOICEplug, Presto, Deepgram, Incept AI, Audivi.Ai, Monkey) are all AI order-taking under Digital Ordering, which is a different capability from popping a customer record on an inbound call. 'caller' returns zero corpus hits. Absence is not decisive because the directory publishes 121 of a self-declared 150.

extensibility-public-api-docs

No publicly readable API reference exists. Qu's two published API doc hosts, qu-api.qubeyond.com and qu-pos-api.qubeyond.com, both return Azure's 'Error 403 - This web app is stopped. The web app you have attempted to reach is currently stopped and does not accept any requests' (HTTP 403 Site Disabled) to HTTPS, HTTPS-without-verification and plain HTTP alike, and Wayback shows that page from 2023-12-30 onward -- the docs were public until roughly 2023 and were taken down. No developer/developers/docs/api/apidocs subdomain of qubeyond.com resolves. The vendor's only remaining documentation surface, support.qubeyond.com (Document360), 302s /, /hc/en-us and /sitemap.xml alike to identity.document360.io/Account/Login, and does so despite serving 'User-agent: * Disallow:' -- the gate is authentication, not crawler policy. API access is by partner certification. https://support.qubeyond.com/hc/en-us · retrieved 2026-08-09 adversarially verified

extensibility-api-access-cost differentiator

Commercial claim. The /become-a-partner page and the /integrations 'Become a Partner' block are the only surfaces that could price integration and neither states a fee, per-location charge, revenue share, or plan requirement — the only text is 'We believe responsible partnerships benefit everyone in the ecosystem. Our robust certification process ensures that integrations are tested and reliable.' A silence on a lead-capture form is not an assertion that access is free. Qu is quote-only with no published pricing.

extensibility-partner-revshare

Resolved 2026-08-08. The claim asks whether Qu publishes partner commercial terms, so the test is exhausting the surfaces where they would appear. The partner program page /become-a-partner carries no figures at all - only an inquiry form and the invitation "If you're a technology company aiming to help restaurants improve operations, increase revenue, and wow their guests, contact us to explore opportunities for working together." The integrations directory is now fully enumerable via the Webflow pagination parameter (/integrations?12898331_page=N, 14 pages, 120 partners across 11 categories); no entry carries any fee, referral or revenue-share figure, and the page's only commercial language is "Our robust certification process ensures that integrations are tested and reliable" beside a Become a Partner call to action. The 233-URL sitemap contains no partner-terms, pricing or developer-program page, and the API portals are unauthenticated-403. Commercial terms are handled by inquiry, not published. https://www.qubeyond.com/become-a-partner · retrieved 2026-08-08

extensibility-free-sandbox differentiator

Positive evidence of the opposite, from Qu's own archived API reference rather than from the marketing site. The Data Access API documents an account-issued credential model: 'If an endpoint requires an API Key, the header APIKey =[string] should be present in the Request', with the worked example framed as 'All examples assume that company integrating with Data Access API is called "GoodEatsOrdering"' -- a named, onboarded partner, not self-serve signup. 'sandbox' occurs in none of the 210 archived help-centre articles. Measured 2026-09-03: sandbox.qubeyond.com does resolve (A 3.220.47.246, 100.31.229.247) but 502s on /, /robots.txt and /swagger/index.html and has never been captured by Wayback, so it is an internal environment hostname and not an offer to developers; the archived example base URL dev-data-access-api.azurewebsites.net resolves to 23.96.112.53, the same stopped Azure app as qu-api.qubeyond.com. https://web.archive.org/web/20220724113646/https://qu-pos-api.qubeyond.com/ · retrieved 2026-09-03

extensibility-oauth-partner-apps

Qu's own Data Access API documentation states the authentication mechanism outright: 'Important: If an endpoint requires an API Key, the header APIKey =[string] should be present in the Request.' A static shared-secret header, with no authorization endpoint, no token exchange, no scopes and no per-operator grant or revocation. The doc page is no longer served -- qu-pos-api.qubeyond.com returns Azure 'Error 403 - This web app is stopped' on 2026-08-09 -- so this is quoted from the last good capture (2022-07-24, doc header 'API v 20190222.1'); the identical sentence appears in the qu-api.qubeyond.com capture of 2022-06-30 ('API v 3.0.93.12'). No OAuth, scope or consent language appears anywhere on qubeyond.com or in its partner material. https://web.archive.org/web/20220724113646/https://qu-pos-api.qubeyond.com/ · retrieved 2026-08-09 adversarially verified

extensibility-webhooks-push

Capability verb ('pushes'), so the exhausted host set cannot convert this to `no`. 'webhook' is absent from all 199 uncited pages. The corpus's strongest architecture statements are marketing — 'Built on REST APIs... an open, bi-directional infrastructure' and 'The APIs leverage bi-directional data syncs' — which describe direction of data flow, not push-vs-poll transport, and are grade C. With no developer host in existence, an unpublished push contract remains possible.

extensibility-webhook-reliability differentiator

Capability claim, compounded (signing AND retry AND replay log). Zero 'webhook' and zero 'rate limit' hits in the 199-page corpus and the Adyen contract. No Qu host publishes an API reference, so HMAC signing, backoff policy and replay semantics are unmeasurable rather than absent. May not be scored `no` under the publication/capability split.

extensibility-order-injection-api

Qu's API documentation: 'Qu provides REST API for 3rd party ordering applications to place orders in Qu POS systems. With current implementation 3rd party vendors can send online orders to Qu Data Access API, orders will be saved in the database and POS systems in stores pull online orders and print them.' The reference documents the full write path -- basket create, add/delete items and discounts, Calculate Totals, then POST Order -- under api/v3/customers/{id}/locations/{id}/baskets. Note the shortfall in the mechanism: it is a PULL model, the store polls the cloud, not a push into the terminal. The doc host is no longer served (Azure 'web app is stopped', 403, on 2026-08-09), so this is quoted from the 2022-07-24 capture; that the path is live today is corroborated by Qu's own 2026-01-13 release announcing Onosys 'certification and production-ready integration' with 'deep, bi-directional integration', and by live Zuppler and 7shifts connectors. https://web.archive.org/web/20220724113646/https://qu-pos-api.qubeyond.com/ · retrieved 2026-08-09 adversarially verified

extensibility-menu-write-api differentiator

Capability verb ('can be written'). The corpus adds only marketing: menu changes are managed centrally in Qu and syndicated to channels ('manage all menu and item changes in one place'; 'No more worrying about menu mapping and order rejection'). That is Qu pushing its own menu outward, not a customer-facing menu write endpoint, and a 'Key Features' style passage is a selection rather than an enumeration. No API reference is published on any Qu host, so this stays unknown.

extensibility-data-symmetry differentiator

Capability claim over five object families. The only new material is repeated marketing use of 'bi-directional' ('an open, bi-directional infrastructure'; 'bi-directional integration with leading delivery service providers'; 'The APIs leverage bi-directional data syncs'), all of it grade-C brochure copy scoped to delivery-channel order and menu flow — it never enumerates customers, employees or inventory, and cannot establish read/write parity. With no published API reference on any Qu host, symmetry is unmeasurable.

extensibility-published-rate-limits

The archived Data Access API reference's conventions section is complete and omits any quota. It reads in full: 'Message Format: All requests and responses bodies are in JSON format. API URLs: All Data Access API calls prefixed with api/v3... Important: If an endpoint requires an API Key, the header APIKey =[string] should be present in the Request.' No numeric quota, no throttling behaviour, no headers. 'rate limit', 'throttl' and 'quota' occur in none of the 210 archived help-centre articles. Re-measured 2026-09-03: docs./developer./developers./help./api./university.qubeyond.com are all ENOTFOUND; qu-api and qu-pos-api answer 403 Azure 'Web App - Unavailable' over plain HTTP and fail TLS identity; support.qubeyond.com/hc/en-us is a Document360 login page; the 239-URL live sitemap contains no developer or API-reference page. https://web.archive.org/web/20220724113646/https://qu-pos-api.qubeyond.com/ · retrieved 2026-09-03

extensibility-doordash-preferred differentiator

Verified at DoorDash's own newsroom: 'The 2026 cohort DoorDash Preferred Integration Partners include Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, and UrbanPiper.' Caveat the dossier does not: DoorDash's page names NO rating tiers, so Qu's 'first POS rated Excellent' remains a vendor claim, and the dossier repeats it as fact in best_at and in two score notes. 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 bi-directional DoorDash, Uber Eats, Grubhub (plus EZCater, Monkey) integrations, explicitly "no middleware required." https://www.qubeyond.com/ordering/third-party-ordering/ · retrieved 2026-08-01

extensibility-middleware-compatibility

Qu blog (dated June 19, 2019): "Qu offers the flexibility of third party integration for customers that wish to continue to use smaller third party players and when direct integration is not yet an option. Qu's customer-first and API-first approach allows customers to integrate familiar platforms like Chowly and ItsaCheckMate into their existing ecosystem." That names two of the listed aggregation middleware platforms. SHORTFALL: the statement is seven years old and current Qu marketing positions the opposite - "Cut out middleware" and "no middleware required" (ordering/third-party-ordering, ordering/pos) - and it could not be confirmed against the live partner directory, which reports "Showing 1 to 9 of 150 integrations" and does not render the remaining pages to a plain fetch. Deliverect and Otter appear nowhere on the site. https://www.qubeyond.com/resource-center/third-party-delivery-blessing-or-technology-curse-for-operators · retrieved 2026-09-03

extensibility-accounting-connectors

Accounting is a listed partner category and Restaurant365 maintains a Qu POS connector; a vendor-maintained QuickBooks Online connector with mapped journal entries is not documented. https://www.restaurant365.com/partners/qu-pos/ · retrieved 2026-08-01

extensibility-payroll-export

Qu blog announcing 2024 certifications: "Labor Management Optimize your workforce with sophisticated tools from HotSchedules, Proliant, and Rippling", within "100+ industry-leading integration partners" whose "robust certification process ensures that integrations are tested and reliable". Proliant and Rippling are both payroll processors, so two named payroll providers are certified partners. SHORTFALL: no reachable Qu page states that LABOR HOURS flow to them, in which direction, or that manual re-keying is eliminated; the partner directory's Back of House + Labor category could not be enumerated past its first 9 of 150 rows; and Gusto, ADP, Paychex and Paylocity appear nowhere as Qu integrations. https://www.qubeyond.com/resource-center/what-qus-doubled-integration-network-means-for-you · retrieved 2026-09-03

extensibility-bi-data-warehouse differentiator

DataExport API exists and Qu markets API connections into external BI; scheduled delivery to a customer-controlled destination is not documented. https://www.qubeyond.com/management/unified-data-reporting · retrieved 2026-08-01

extensibility-app-marketplace

Re-evidenced 2026-08-08: /about/qu-technology-partners/ now 301s to /integrations, a live public directory that states 'Showing 1 to 9 of 150 integrations' and is browsable and filterable by eleven categories - Accounting, Analytics, Back of House + Labor, Delivery, Digital Ordering, Hardware + Digital Signage, Kitchen / KDS, Loss Prevention, Loyalty, Other, Payments. Named entries include 7shifts, Altametrics, MarketMan, Restaurant365, Crunchtime, Olo, Paytronix, Thanx, DoorDash, UberEats, GrubHub, FreedomPay and Fiserv. Shortfall (the reason this is partial, not yes): there is no self-install. Every entry's only action is 'View Site', linking out to the partner; enablement runs through Qu's certification process - 'Our robust certification process ensures that integrations are tested and reliable' - with a 'Become a Partner' form rather than an operator-facing install button. Grade C rather than B: this is a first-party marketing/feature page, not product documentation. https://www.qubeyond.com/integrations · retrieved 2026-08-08 adversarially verified

extensibility-custom-fields-scripting

Chapter 6: Configuration (First Gen 2.0) documents two operator-defined extension surfaces inside Enterprise/Store Configuration. The Client settings block carries 'Prompt for Check Extension Data - Specify JSON Format Extension Data', i.e. operator-specified JSON fields prompted for and carried on a check. System Lookups let the operator 'Add custom values using System Lookups. For example, add your own reasons for voiding a check or discounting an item', covering Void Reasons, Time Entry Reasons, Return Reasons, Paid In/Out Reasons, Discount Reasons, Order Types and Inventory Units. Shortfall: these are configuration-driven custom values plus a custom JSON payload on one object, not user-defined fields across POS objects, and no vendor-hosted scripting or custom-logic runtime appears anywhere in the 210 archived articles or the v139-v143 release notes. Vintage: First Gen 2.0, 2018-2020. https://web.archive.org/web/20200808111044/https://support.qubeyond.com/hc/en-us/articles/360001267211-Chapter-6-Configuration-First-Gen-2-0- · retrieved 2026-09-03

extensibility-headless-embedded

Third-party ordering front ends (e.g. Zuppler, Bite) drive Qu through its ordering API, and Qu markets an "API forward" stack, but no formal headless/embedded mode is documented. https://www.zuppler.com/qu-beyond-pos · retrieved 2026-08-01

extensibility-api-versioning-deprecation

The claim is conjunctive and the deprecation half fails. Qu does publish release notes, so a 'no hits for changelog' reading would be wrong: seasonal recaps run publicly in the resource centre (Fall 2024 through Winter 2026) and dated versioned notes ran in the then-public help centre, some carrying real API changes -- 'Labor API - A store's locationId is now available with each labor schedule'; 'as of v139, Data Export API will offer a new export structure that converts Items with Portions into individual Items'. But the public recaps are feature marketing with no API section, and the only deprecation found anywhere is ad-hoc and about platform settings, not the API: 'Please review the soon to be deprecated Platform Settings (QuickSuspend, SuspendOrderAllowed, PrintOnSuspendByDefault, SendOrderOnSuspendByDefault)... they have been marked deprecated and will be deleted in the future when there are no POS running versions prior v142.' No stated deprecation or breaking-change notice policy appears on any enumerated surface: the 239-URL sitemap, the status page, the resource centre, the archived API reference, or six NXDOMAIN developer subdomains. https://web.archive.org/web/20210125165411/https://support.qubeyond.com/hc/en-us/articles/360052896691-November-17th-v139 · retrieved 2026-09-03

extensibility-data-portability-exit differentiator

Product page FAQ: "Yes. Qu's unified data layer supports API-based integrations with external BI platforms, enabling operators to pipe Qu data into the analytics environment of their choice", alongside "Access up-to-date performance data across locations through Qu or your existing reporting tools"; the multi-unit guide claims "100% First-party guest data, owned". SHORTFALL: this is an ongoing BI pipe, not an exit right - no reachable Qu page commits to a COMPLETE historical export of orders, customers, menu and payment metadata AT CONTRACT END, names a machine-readable format, or states whether a fee applies. The only Qu-authored terms published are website terms of use, with no MSA and no data-return clause; no format or endpoint can be checked because both API hosts fail TLS identity and the customer portal is login-walled. https://www.qubeyond.com/management/unified-data-reporting · retrieved 2026-09-03

reliability-offline-order-entry

Qube executes POS, payments, order routing and kitchen workflows locally; ordering continues uninterrupted during outages. https://www.qubeyond.com/qu-business-edge · retrieved 2026-08-01

reliability-offline-card-auth differentiator

Qu Business Edge (Qube) product page asserts "Local Execution of Critical Services: POS, payments, order routing, and kitchen workflows execute on-site. There is no reliance on remote service calls for core operations", plus a "Write-Local, Sync-Global Data Model" where "All transactions are written locally at the edge and propagated to the cloud in real time... No data loss during outages" and "Resilience Without Degraded Modes... Full transaction processing continues". The Qu POS page FAQ repeats it: "Ordering, payments, and kitchen routing continue uninterrupted during connectivity outages, and data syncs to the smart cloud automatically when the connection is restored" (https://www.qubeyond.com/ordering/pos). SHORTFALL: this is asserted on grade-C vendor feature pages only. No store-and-forward mechanism, floor/ceiling limits, per-transaction or aggregate offline caps, maximum offline duration, or decline-on-reconnect handling is published anywhere on qubeyond.com; support.qubeyond.com is login-walled and there is no grade-A/B documentation. Whether card authorization is genuinely deferred and forwarded, or merely captured locally, is not documented. https://www.qubeyond.com/qu-business-edge · retrieved 2026-09-03 adversarially verified

reliability-offline-decline-liability differentiator

Duplicate claim of the already-resolved payments-offline-decline-liability ("no", same source): Qu's public offline-payments material — the Qu Business Edge page ("Full transaction processing continues... Sync resumes automatically with no manual intervention," "No data loss during outages") — promotes offline card acceptance continuity without a word on who bears a decline on reconnect, or any per-transaction/cumulative offline cap. No public MSA/ToS exists (privacy-policy page confirms the only legal document published is the privacy policy, which excludes customer/product terms) and the help centre is login-gated, so the public documentation this claim requires verifiably does not exist. https://www.qubeyond.com/qu-business-edge · retrieved 2026-08-04

reliability-lan-degraded-multi-terminal differentiator

Qube is a single on-premise hub serving the location's POS, kiosk, drive-thru and KDS, implying shared local state across terminals, but Qu does not document multi-terminal check sharing during a partition. https://www.qubeyond.com/qu-business-edge · retrieved 2026-08-01

reliability-local-transaction-engine differentiator

Qu Business Edge (Qube) is an explicitly documented on-premise edge hub running critical services locally without remote service calls; A / E / IQu hardware series. https://www.qubeyond.com/qu-business-edge · retrieved 2026-08-01

reliability-offline-kds-printing

Offline kitchen ROUTING is affirmatively claimed and I verified the wording. Offline kitchen PRINTING is nowhere stated — Qu publishes no printer-fallback or impact-printer behavior at all (the dossier itself scores kitchen-printer-fallback and reliability-printer-fallback unknown, which contradicts a 'yes' here). https://www.qubeyond.com/qu-business-edge · retrieved 2026-08-01 adversarially verified

reliability-printer-fallback

Same evidence base as kitchen-printer-fallback: zero occurrences of 'printer' across the full corpus and the Winter 2026 release, and Qu's reliability marketing is uniformly about uptime percentages ('99.99% platform and product uptime', 'triple redundant commerce cloud', 'Keeps processing orders when the internet drops. Always.') rather than peripheral failure handling. Automatic re-routing to a backup printer plus a staff alert is table-stakes plumbing that a vendor documents in a station-setup article, not in an uptime pitch, so this surface would not carry it even if it existed.

reliability-sync-conflict-handling

Qu Business Edge documents a 'Write-Local, Sync-Global' model: 'All transactions are written locally at the edge and propagated to the cloud in real time', 'System state is preserved locally', and — the operative line — 'Automatic conflict resolution and state reconciliation on reconnect'. The vendor publicly commits to conflict resolution existing. Shortfall: the resolution behaviour itself is never specified — nothing states last-write-wins, merge or operator prompt, which is precisely what this claim asks for — and the help centre where it might be specified is login-gated. https://www.qubeyond.com/qu-business-edge · retrieved 2026-08-04

reliability-offline-feature-matrix

Qu claims full offline continuity but publishes no list of degraded features; the Qube page does not detail what requires connectivity. https://www.qubeyond.com/qu-business-edge · retrieved 2026-08-01

reliability-public-status-page

status.qubeyond.com is public with per-component status (Qu Core APIs, QuKitchen KDS, Web Ordering, Reporting/Notify/DataExport APIs, QuBox, FreedomPay, WorldPay, DoorDash, UberEats, Olo, Esper, CrowdStrike, AWS) and incident history. No rolling uptime percentages published. https://status.qubeyond.com/ · retrieved 2026-08-01

reliability-contractual-uptime-sla differentiator

Qu markets 99.99%/99.997% as architecture design claims for Qube, but no customer-facing SLA with a service-credit remedy is published. https://www.qubeyond.com/platform · retrieved 2026-08-01

reliability-incident-postmortems

The status page carries incident history with narrative updates (e.g. real-time reporting delay, Valutec gift card processing via WorldPay); formal RCA postmortems are not published. https://status.qubeyond.com/ · retrieved 2026-08-01

reliability-247-live-support

"Qu offers 24x7x365 support to keep your restaurant cooking along," with a published phone line (844.464.8786). Whether it is included in base pricing is not stated. https://www.qubeyond.com/support · retrieved 2026-08-01

reliability-onsite-install differentiator

Two case studies lean against the claim but do not settle it. Dave's Hot Chicken lists as a benefit 'Reduced on-site IT intervention from four days to near zero, transitioning to a reliable remote support model', against a pain point that 'Previous technology required four (4) full days of on-site IT support per new location'; a companion video page says Qu is 'fast and easy to implement, requiring minimal intervention from IT teams'; GoTo Foods 'Completed in-store implementation in 90 minutes'. All of these measure the operator's own IT burden and post-launch support model, not whether Qu fields first-party or dealer installers — and Qu deployed 2,100 Jack in the Box restaurants in 15 months, which no page describes the mechanics of. Scoring no here would convert a support-burden statistic into a services-model verdict.

reliability-menu-build-service differentiator

Zero hits for 'menu build', 'build your menu' or 'configure your menu' across the legal set and 199 pages. Onboarding-speed claims exist — the Qu Pay release says merchants 'go live in days instead of weeks, reducing onboarding timelines by up to 75%' — but that sentence is about payments merchant onboarding, not menu construction, and names no party as the builder. Who performs the initial menu build is a professional-services term that would live in an unpublished SOW or in the walled operator documentation.

reliability-hardware-replacement-sla

Deliberately scored differently from hardware-rma-sla. That cell asks whether Qu publishes a warranty term and turnaround, which the exhausted surface settles as no; this one asks whether a replacement/advance-exchange program is 'included or purchasable', which is a capability that a quote-only enterprise vendor would negotiate in an unpublished MSA. Qu publishes no MSA — the only T&Cs govern website use — so the existence of such a program is unmeasurable rather than absent.

reliability-backup-restore

Searched the corpus, the Adyen for Platforms terms (69.5 KB) and the unlinked website terms for 'backup', 'restore', 'retention', 'business continuity', 'disaster', 'RPO' and 'RTO'. The only 'backup' hit is an edge-architecture boast — 'By eliminating the need for complex backup systems, Qu's fault-tolerant approach minimizes downtime' — which is about redundant infrastructure, not operator-retrievable data backups. No RPO/RTO figure appears anywhere. Qu does not PUBLISH recovery objectives on its open surface, but that is only one disjunct of the claim; whether an operator can trigger and retrieve their own configuration backup is an admin-console capability behind the walled documentation. Both disjuncts must fail for a no.

reliability-pci-dss-4-attestation

Fetched the platform page directly, the page whose subject is Qu's architecture and enterprise capabilities: it describes unified commerce, kitchen orchestration, payments, and enterprise management but contains no PCI DSS v4.0/4.0.1 Attestation of Compliance, validated P2PE listing, or any compliance-attestation language at all. The Qu Pay page (fetched separately) is equally silent. No trust-center or security page exists on qubeyond.com to check instead. https://www.qubeyond.com/platform · retrieved 2026-08-04

reliability-mfa-role-based-access

Role-based permissions and granular user administration are documented; MFA enforcement on back-office or POS admin logins is not. https://www.qubeyond.com/management/channel-management · retrieved 2026-08-01

reliability-self-serve-training

"Qu Campus" provides documentation and training but requires customer login; there is no free public training library, and a terminal training mode is not documented. https://www.qubeyond.com/support · retrieved 2026-08-01

reliability-failover-terminal-role differentiator

Qube is marketed with "triple redundancy"; automatic promotion of a terminal to master on primary failure is not documented. https://www.qubeyond.com/qu-business-edge · retrieved 2026-08-01

reliability-cellular-backup

'cellular' occurs zero times in the corpus and every apparent 'LTE' hit is a substring of ordinary words ('alternative', 'ultimate'). Qu's connectivity story is that the store keeps running locally when the internet drops ('System state is preserved locally,' 'Sync resumes automatically'), which describes surviving the outage rather than an alternate WAN path. A vendor-documented LTE failover would normally appear in a network-requirements or store-install document, a class of document Qu publishes nowhere publicly, so the marketing silence does not settle whether such failover is offered.

commercial-month-to-month-contract differentiator

Qu's complete published legal set is three documents — /terms-and-conditions (website terms of use only; 'These terms and conditions constitute the entire agreement between you and our company regarding the use of our website'), /privacy-policy, and /adyen-for-platforms-terms-and-conditions. None contains a subscription, term, renewal, notice or fee provision, and no pricing page exists in the 239-URL sitemap; /msa, /master-subscription-agreement, /subscription-agreement, /terms-of-service, /legal and /customer-agreement all 404 (probed 2026-09-04). Qu is quote-only: the commercial term is negotiated in a contract that is not published, so whether a month-to-month option is available cannot be determined in either direction. Scored consistently with olo and speedline, the same no-published-pricing pattern. adversarially verified

commercial-no-early-termination-fee differentiator

Same underlying fact as the already-scored commercial-autorenew-terms-published: re-fetched the privacy policy directly, the only legal document Qu publishes, and it explicitly states "This Privacy Policy does not apply to: Information processed on behalf of our customers through Qu products and services, where separate contractual terms may apply" — confirming no MSA, ToS, or order-form terms are publicly posted anywhere on qubeyond.com. A published term stating no early-termination fee cannot exist because no published contract terms exist at all. https://www.qubeyond.com/privacy-policy/ · retrieved 2026-08-04

commercial-autorenew-terms-published

No publicly accessible MSA, terms of service, or order-form terms exist on qubeyond.com; the website privacy policy explicitly excludes platform/customer data terms. https://www.qubeyond.com/privacy-policy/ · retrieved 2026-08-01

commercial-processing-not-bundled differentiator

Verified verbatim on the online-ordering page: 'Whether you use Qu Pay or an integrated provider, third party loyalty or Qu's built-in discounts...' — vendor-stated processor optionality, corroborated by FreedomPay and WorldPay appearing as live status-page components. https://www.qubeyond.com/ordering/online-ordering · retrieved 2026-08-01 adversarially verified

commercial-interchange-plus-published differentiator

No processing rate of any structure is published. https://www.qubeyond.com/payments/qu-pay · retrieved 2026-08-01

commercial-rate-increase-clause differentiator

Same fact as commercial-no-early-termination-fee: no processing agreement or any commercial terms are publicly posted (privacy policy re-fetched and confirms the scope exclusion for customer/product terms), so no published clause capping or prohibiting unilateral rate increases, or granting penalty-free exit on an increase, can exist. https://www.qubeyond.com/privacy-policy/ · retrieved 2026-08-04

commercial-pricing-published

Quote-only. No pricing page exists; the site routes all commercial inquiries to a demo request form. https://www.qubeyond.com/get-a-demo · retrieved 2026-08-01

commercial-module-unbundling differentiator

There is no published pricing, no module SKU list and no subscription agreement — the site T&Cs govern website use only and the Adyen document covers payments. The one page that would carry an enumeration, /modules, is an unfinished template: its body is repeated 'Placeholder Name / Placeholder Job Title' blocks around a single generic paragraph, with no module list at all. Whether modules can be bought and cancelled independently without repricing the base subscription is unmeasurable from Qu's public surface.

commercial-hardware-purchase-outright

The claim requires purchase 'at a published price'. Qu publishes no prices at all: the POS page describes hardware only via 'Qu Business Edge (Qube)... the on-site intelligence hub in every restaurant' with no price, purchase, lease or rental term, qubeyond.com has no pricing page anywhere, and every path funnels to the get-a-demo quote form. Whether outright purchase is negotiable in a quote is unknowable, but the published-price condition is verifiably unmet, which fails the claim as worded. https://www.qubeyond.com/ordering/pos · retrieved 2026-08-04

commercial-hardware-not-locked differentiator

Qu's own help centre documents the product operating on third-party, non-proprietary hardware throughout: a 'Manual Transaction Guide for Ingenico IPP320' PIN pad (First Gen 2.0, March 2020); a 'Magtek MagneSafe Magnetic Stripe Reader Device' as the terminal MSR, whose driver the operator uninstalls and reinstalls from Windows Device Manager (Nov 2020); Touch Dynamic Acrobat Windows terminals with operator-serviceable SSD and MSR swaps; and ChefTab as the KDS, configured by the operator through 'Cheftab Settings/Preferences' ('How do I Prevent Bumping a Chit on the KDS?', Oct 2020). No Qu-branded terminal, printer or reader appears anywhere in the 210 archived articles. Corroborated live: ChefTab and Logic Controls both appear in Qu's certified-partner directory today, under Kitchen/KDS and Hardware + Digital Signage respectively. Vintage: First Gen 2.0 / Next Gen 3.5, 2020, with live partner-directory corroboration. https://web.archive.org/web/20200809113433/https://support.qubeyond.com/hc/en-us/articles/360040852811-Manual-Transaction-Guide-for-Ingenico-IPP320-First-Gen-2-0- · retrieved 2026-09-03

commercial-implementation-fee-published

No implementation, menu-build, or training fees published; Qu Pay claims onboarding timelines reduced up to 75% but states no cost. https://www.qubeyond.com/payments/qu-pay · retrieved 2026-08-01

commercial-data-export-self-serve

A DataExport API exists as a platform component; self-serve export of full transactional history without a support ticket is not documented. https://status.qubeyond.com/ · retrieved 2026-08-01

commercial-export-customer-and-loyalty differentiator

Qu Reports Quick Guide (Next Gen 3.5, Oct 2020): the Customers report covers 'all customers and their information entered on the POS or the web ordering site... first name, last name, phone number, email address, last order date, total orders, the total dollar amount spent, and registration status', and every report can be 'exported (downloaded or emailed as either an Excel file, CSV, or PDF)' - so guest records are operator-exportable in machine-readable form. Shortfall: no loyalty point ledger or balance is exportable from Qu itself (loyalty in this generation is the third-party Punchh integration, whose 'LifetimePoints and totalActivePoints' live on Punchh's side per the v142 release notes), and while First Gen listed a Gift Cards report, no gift-card liability balance export is documented. Vintage: Next Gen 3.5, 2020. https://web.archive.org/web/20201128174707/https://support.qubeyond.com/hc/en-us/articles/360049022511-Qu-Reports-Quick-Guide-Next-Gen- · retrieved 2026-09-03

commercial-post-termination-export-window differentiator

Same underlying fact as commercial-no-early-termination-fee and commercial-rate-increase-clause: no contract or MSA is publicly posted anywhere on qubeyond.com (privacy policy confirms the scope exclusion and that separate, non-public contractual terms apply), so no publicly available document specifies a post-termination data-retrieval window versus an immediate cutoff. https://www.qubeyond.com/privacy-policy/ · retrieved 2026-08-04

commercial-data-ownership-clause differentiator

Third Party Terms 12.1: "Qu and Adyen may use de-identified and/or aggregated Transaction data solely for the purposes of creating, optimizing payment performance, and improving Adyen and Qu's products and services... In no event shall Adyen or Qu provide, sell, or otherwise disclose any de-identified and/or aggregated Transaction data to any third party (except as required by Applicable Law or the Scheme Rules)." The companion Adyen for Platforms Terms Qu publishes state at 9.1 "Each party remains the owner of all data made available to the other party." Shortfall: both clauses are scoped to payment-services transaction data only; the Master SaaS Agreement that would govern ownership of POS order, menu and guest records is not published, so no published Qu term states the merchant owns its full transaction and customer data. https://www.qubeyond.com/third-party-terms · retrieved 2026-09-03

commercial-source-available-selfhost

Proprietary, closed-source, vendor-hosted cloud plus vendor-supplied Qube edge appliance. No source or self-host option. https://www.qubeyond.com/platform · retrieved 2026-08-01

commercial-pci-p2pe-tokenization

Fetched the Qu Pay page directly: no validated P2PE or hardware-encrypted card-entry-plus-tokenization claim is made, and no SAQ type (A / P2PE-HW) is named anywhere on qubeyond.com. Same finding as hardware-p2pe-terminal. https://www.qubeyond.com/payments/qu-pay · retrieved 2026-08-04

commercial-pci-dss-4-controls

Fetched the Qu Pay, platform, and Qu Business Edge pages directly: none documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — no MFA-for-cardholder-data-environment statement covering POS/back-office logins, and no payment-page script-integrity monitoring statement. https://www.qubeyond.com/qu-business-edge · retrieved 2026-08-04

commercial-soc2-attestation

Fetched the platform page directly: it describes unified commerce, kitchen orchestration and enterprise management with no SOC 2 Type II or ISO 27001 attestation claim, and no trust-center link exists anywhere on qubeyond.com to request a report under NDA. https://www.qubeyond.com/platform · retrieved 2026-08-04

commercial-privacy-dsar-tooling

Conjunctive claim requiring in-app DSAR tooling PLUS 'a published DPA the operator can execute'. No DPA is published: the complete legal set is three documents (site terms of use, privacy policy, Adyen-for-Platforms T&Cs) and /dpa, /data-processing-agreement, /data-processing-addendum, /legal/dpa, /gdpr and /ccpa all 404 (probed 2026-09-04); the Adyen document's only privacy clause (9.2) allocates roles between Adyen and the merchant and cites Adyen's Privacy Statement. The privacy policy expressly excludes the product data plane from its own scope — 'Information processed on behalf of our customers through Qu products and services, where separate contractual terms may apply' — i.e. Qu locates guest-data processing terms in an unpublished contract. Request handling is email-only: 'To exercise any applicable privacy rights, please contact us using the information in Section 16.' The published-DPA conjunct fails, so the compound claim is not met; the in-app-tooling conjunct is separately unmeasured behind the gated customer portal. https://www.qubeyond.com/privacy-policy · retrieved 2026-09-04 adversarially verified

commercial-wcag-kiosk-accessibility differentiator

Kiosk page claims software accessibility features (audio output, adjustable screen interaction) "to support ADA compliance requirements"; no VPAT/ACR or WCAG 2.1 AA conformance claim is published. https://www.qubeyond.com/ordering/kiosk · retrieved 2026-08-01

commercial-dual-pricing-compliant differentiator

Compound claim requiring a card-network-compliant fee-offset program with automatic debit/prepaid exclusion plus receipt and menu-board disclosure. No component appears in the legal set or the 199 pages. The Adyen contract does impose general scheme-rule compliance on the merchant and lists fineable violations, but surcharge compliance appears only in the Australia clause and only as the merchant's own duty; that neither establishes nor excludes a compliant US program in Qu's POS.