Clover Go

Supports splitting a check by item, by seat, by even N-way, and by arbitrary dollar/percentage amount, and merging checks or tables back together, including after partial payment.

order-capture-split-merge

CLAIM: split a check by item, by seat, by even N-way and by arbitrary amount, and merge checks/tables back together, including after partial payment. VERDICT: no for Clover Go. NEW SURFACE (327th) that the prior passes did not have: the Clover Go SDK's own published CONTENTS enumeration at docs.clover.com/dev - 'Card present payments | Manual entry payments | Capture and tip adjust | Payment reversal | Closeout | Receipts' (clover-go-sdk-contents), the complete list of what the Go SDK does; there is no split, seat or merge operation in it, and the SDK page adds that it does not ship 'Pre-built user interface (UI) screens' or a 'Clover-built app that handles payment on the customer's device' (clover-go-sdk). This is an ENUMERATION, not a procedure gap. It is corroborated by the Go app's own complete top-level menu - 'Employees | Inventory | Reporting | Closeout | Cash Log | Card reader | Help | Settings' (explore-the-ui-go-g2) - and by the two complete Go checkout procedures, which end at one tender: quick sale ('Enter the full sale amount, including taxes and other fees, and tap Checkout ... Tap Complete Transaction ... enter a tip amount; then tap Approve payment ... Select a receipt option') and itemized sale ('select items from your inventory, add custom, variable, and per-unit priced items, and apply discounts to a single item or an entire order'), with no split step anywhere (take-payments-with-go). The only multi-device order behaviour Clover publishes for Go is a hand-off, not a split: 'Open transactions are saved transactions that have not been paid. This feature allows you to create an order on another Clover device and process the payment using the Clover Go app or vice versa' (work-with-orders-on-clover-go); the same article's only order operations are view, rename and delete. BOUND: 29 Clover-Go-specific help articles with full bodies, 57,048 chars, plus the 905/905 docs.clover.com/dev census (llms.txt manifest, 0 shells, 25.6 MB, nonsense-path control passed). CONTROLS over the 29 Go bodies: 'split' 0 hits. POSITIVE CONTROLS on the same bodies: 'tip' 5 docs, 'customer' 11 docs, 'employee' 8 docs. Cross-check: split IS documented by Clover, for the Android Register app only ('Tap Split by Items', 'Tap Split Custom Amount'), which is a different product and is the poison this cell has to avoid. Retrieved 2026-09-18. https://www.clover.com/en-US/help/take-payments-with-go · retrieved 2026-09-18 adversarially verified

With the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen, and tender cash, and the vendor publishes what does and does not work offline.

order-capture-offline-order-entry

330th: MOVED to partial on an app-level census. NEW SURFACE (330th) — THE CLOVER GO ANDROID APP ITSELF, unpacked: clover.companion.app v5.13 (the Play/App Store product 'Clover Go - Dashboard & POS', iOS bundle com.clover.clover-companion-app v5.13.1, 2026-08-27). 111.7 MB XAPK pulled anonymously from an apkpure mirror of the vendor's Play listing; it is Clover's own signed build (META-INF carries BUILD_INFO.clover-android-sdk, .clover-android-loyalty-kit, .clover-remote-*, .core-payments-kernel; package and version match the store listings). I parsed resources.arsc myself (.cache/q330/clover-go/arsc2.mjs) to the DEFAULT-locale string table: 4,484 string resources with their resource KEYS, i.e. the app's complete shipped UI vocabulary, plus 336,692 printable strings from the 8 classes*.dex (strings.mjs). This is an app-level census of the STORE-LEVEL product, which no prior pass on this vendor had (they used the help centre, its Contentful route census, the cloverstatic.com dashboard source maps and docs.clover.com). Grade B: vendor-shipped code, not published documentation. WHAT THE APP PUBLISHES ABOUT OFFLINE ORDER CAPTURE (all from the shipped string table): orders ARE created and tendered offline — `offline_payments_optin_settings_description` = 'Offline payments allow you to accept cash, card, and check payments without a network connection' (so CASH TENDER offline is explicit, which the help centre never said for Go); `pending_order_tab_info` = 'Orders processed offline will appear as pending. Processing will complete as soon as the system comes back online.'; `offline_payments_optin_settings_note` = 'Note: Offline transactions are automatically submitted when the system is back online and you log into the app.'; `network_back_online_from_offline_msg` = 'Any transactions taken offline will now be processed.' The app also ships the full modifier surface used to build those orders (`item_modifier_group_n_required` '%d required', `item_modifier_custom_add_title` 'Add custom modifier', `item_error_modifiers_required_message` 'Modifiers are required', `acc_line_item_modifiers` 'Modifiers: %s'), though no string scopes modifiers to the offline path. AND THE APP PUBLISHES THE SHORTFALLS, which is the claim's last conjunct: `open_order_tab_offline_subtitle`/`closed_order_tab_offline_subtitle` = 'You must be online to view your open/closed orders'; `network_offline_home_msg` = 'You must be online to view your home screen'; `offline_mode_invoice_unavailable_title` = 'Invoicing is unavailable while your device is offline'; `void_not_allowed_offline_message` = 'Void not allowed while offline.'; `order_offline_refund_dialog_message` = 'Any transactions refunded in offline mode will not be sent for payment when the system comes back online.'; `offline_surcharge_payment_disabled_msg` = 'While surcharging is enabled, you cannot take card payments offline'; `pay_failure_reason_offline_not_allowed` = 'Offline is not allowed for this card type'; limits are enumerated (`offline_payments_optin_offline_payment_limit`, `..._offline_cumulative_max_days` 'Cumulative offline amount allowed over 7 days', `offline_max_days_violation_msg`). Merchant-facing prose says the same: 'You can continue to take payments when you're not connected to the internet ... When enabled, devices can take offline payments for up to 7 days ... When a connection becomes available, your device automatically submits offline payments for authorization' (accept-offline-payments). NOT YES: no kitchen/ticket-send module exists in Go at all (no kitchen routing string in the 4,484-resource table beyond the `more_menu_reporting_kds_reports` 'Kitchen operations' REPORT), and nothing states that modifier selection survives a dropped connection. Retrieved 2026-09-18. https://www.clover.com/en-US/help/accept-offline-payments · retrieved 2026-09-18 adversarially verified

Offers a first-party self-order kiosk that renders the same menu and modifier tree as the POS with no separate menu build, and the vendor documents ADA/accessibility conformance for it. differentiator

order-capture-kiosk-first-party

Not scored by this record.

Supports drive-thru-specific order flow: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment.

order-capture-drive-thru

Not scored by this record.

Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.

order-capture-drive-thru-timers

Not scored by this record.

Vendor ships a first-party AI voice ordering agent for phone and/or drive-thru that injects orders directly as POS orders, or publishes a documented API partner program for third-party voice AI. differentiator

order-capture-voice-ai

Not scored by this record.

Supports order throttling: per-channel capacity limits per time slot with automatic quote-time extension when kitchen load exceeds a configured threshold. differentiator

order-capture-throttling

Not scored by this record.

Accepts future-dated/scheduled orders with a per-channel lead time and automatically injects them into the make queue at a computed fire time rather than on receipt.

order-capture-scheduled-orders

Scheduling exists at Clover and is explicitly out of reach at the Go tier. Clover Online Ordering does the customer-facing half - its own product page at clover.com/pos-systems/online-ordering offers scheduled orders, letting a customer order now and pick a later pickup time, with a configurable how-far-in-advance window - but Clover's own food-truck FAQ, which is the page written for exactly this buyer, says that to let customers order ahead or to integrate DoorDash 'you will need the Restaurant Growth plan, which includes these advanced online ordering features'. Clover Go sells Starter and Essentials only. Even one tier up the second half of the claim is unevidenced: nothing in the 1,066-document corpus describes injecting a future-dated order into a make queue at a computed fire time - `fire time`, `future order` and `scheduled order` as a make-queue concept occur zero times - and order firing is named in the developer plan table only as a Table Service Restaurant tool. https://www.clover.com/pos-solutions/food-truck · retrieved 2026-09-09 adversarially verified

Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator

order-capture-order-ready-signal

Not scored by this record.

Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.

order-capture-void-comp-controls

Not scored by this record.

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

menu-pricing-nested-modifiers

Clover Go's plans cannot use modifiers at all, so nesting them three levels deep is not possible either. Clover's help article 'Supporting different software plans for multi-location' makes a plan-level statement: 'Each Clover software service plan supports a specific set of features, and availability can vary by plan.' It then says 'The following features are supported only on the Register plan and above: Item attributes such as variants, per-unit pricing, and cost tracking Modifier groups and modifiers Printer labels'. Under the heading 'Impact on Essentials plan and below' it adds 'Locations on the Essentials plan or below don’t support modifier groups, modifiers, or printer labels', and that such items 'don’t appear on POS devices at those locations.' Clover Go currently sells exactly two plans. Its plan matrix at clover.com/pricing/go (Wayback capture of 2026-06-11; the live page is a 7,820-byte shell) has only a Starter and an Essentials column, and no modifier or variant row. This is a closed statement mapping plans to features, not a silence. Named limits on scope: (1) the article sits in the multi-location section, is US/CA and is behind a feature flag, but the plan-to-feature statement it makes is general; (2) this cell scores the plans sold today. Clover Go help articles (explore-the-ui-go-g2, run-reports-on-the-clover-go-app) still name the legacy Go plans 'Register Lite', 'Register' and 'Payments Plus', and a grandfathered Go merchant on the legacy Register plan is, by this same article, on a plan that supports modifier groups. How deep that would nest is not documented for Go. None of the 28 Go-tagged help articles mentions modifiers in English. https://www.clover.com/en-US/help/different-software-plans-multi-location · retrieved 2026-09-15 adversarially verified

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

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

The inventory data model enumerates the whole modifier object — id, name, price and a reference to its parent modifierGroup — and carries exactly one price field per modifier, with no per-parent-item or per-variant override. Sizes are modelled as separate items inside an item group (docs.clover.com/dev/docs/managing-items-item-groups), and a modifier group is attached to each item, so the same modifier resolves to the same price on Small and Large; charging more for a topping on a large means duplicating the modifier group per size. No price matrix exists. https://docs.clover.com/dev/docs/managing-modifier-groups-modifiers · retrieved 2026-08-04

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

menu-pricing-topping-quantity-tiers

The apply-modification request schema is id, name, alternateName, amount, a nested modifier object (id, name, alternateName, available, price, modifierGroup) and quantitySold — which the reference states is "only used in reports". There is no quantity, tier or multiplier field on an applied modification. The modifier-management guide describes extra quantities as repeated additions — a Caesar Salad with "two Tofu modifier and three Avocado modifier additions" — i.e. price x N by adding the modifier twice, which is precisely the mechanism this claim excludes. No configurable per-tier multiplier. https://docs.clover.com/dev/reference/orderapplymodification · retrieved 2026-08-04

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

menu-pricing-size-style-matrix

Not scored by this record.

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

menu-pricing-included-allowance

Not scored by this record.

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

menu-pricing-combos

Not scored by this record.

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

menu-pricing-upsell-prompts

Not scored by this record.

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

menu-pricing-86-propagation

Not scored by this record.

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

menu-pricing-countdown-auto-86

Not scored by this record.

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

menu-pricing-dayparting

Not scored by this record.

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

menu-pricing-channel-price-books

Not scored by this record.

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

menu-pricing-dual-pricing

Not scored by this record.

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

menu-pricing-allergen-nutrition

Not scored by this record.

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

menu-pricing-3p-menu-push

Not scored by this record.

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

menu-pricing-dynamic-pricing

Not scored by this record.

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

payments-processor-choice

Not scored by this record.

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

payments-published-rates

Not scored by this record.

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

payments-dual-pricing

Not scored by this record.

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

payments-surcharge-guardrails

Not scored by this record.

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

payments-emv-nfc

Clover Go is marketed as a chip-and-contactless reader; the page is client-rendered so the exact wallet list could not be extracted. https://www.clover.com/pos-systems/clover-go · retrieved 2026-08-01

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

payments-softpos-tap-to-pay

Not scored by this record.

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

payments-qr-guest-pay

Not scored by this record.

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

payments-offline-store-and-forward

Not scored by this record.

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

payments-offline-decline-liability

Not scored by this record.

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

payments-gift-cards

330th: THE 327th's PROPOSED `no` IS FALSIFIED — the Clover Go app ships the gift-card tender itself. NEW SURFACE (330th) — THE CLOVER GO ANDROID APP ITSELF, unpacked: clover.companion.app v5.13 (the Play/App Store product 'Clover Go - Dashboard & POS', iOS bundle com.clover.clover-companion-app v5.13.1, 2026-08-27). 111.7 MB XAPK pulled anonymously from an apkpure mirror of the vendor's Play listing; it is Clover's own signed build (META-INF carries BUILD_INFO.clover-android-sdk, .clover-android-loyalty-kit, .clover-remote-*, .core-payments-kernel; package and version match the store listings). I parsed resources.arsc myself (.cache/q330/clover-go/arsc2.mjs) to the DEFAULT-locale string table: 4,484 string resources with their resource KEYS, i.e. the app's complete shipped UI vocabulary, plus 336,692 printable strings from the 8 classes*.dex (strings.mjs). This is an app-level census of the STORE-LEVEL product, which no prior pass on this vendor had (they used the help centre, its Contentful route census, the cloverstatic.com dashboard source maps and docs.clover.com). Grade B: vendor-shipped code, not published documentation. GIFT-CARD EVIDENCE INSIDE THE GO APP: the string table carries the tender ids and the exact redemption labels of Clover's own gift-card procedure — `com.clover.tender.external_gift_card` = 'External Gift Card', `system_tender_external_giftcard` = 'External Gift Card', `card_type_gift_card` = 'Gift Card', `gyft_manual_entry` = 'Gift/Card manual', `scan_gyft_qr_code` = 'Gift/Scan QR code', `print_gift_button` = 'Print Gift Receipt', `more_menu_reporting_gift_cards` = 'Gift Cards', `generic_gift_card_activations` = 'Gift Card Activations', `account_giftcard` = 'Gift Card'. Those two entry labels are verbatim the steps of https://www.clover.com/en-US/help/redeem-digital-gift-cards ('Manual Entry: Tap Gift/Card Manual ... QR code: Tap Gift/Scan QR code and scan the gift card QR code on the customer's phone'). The app's own dex confirms the live calls, not just labels: `/v2/merchant/%s/giftcards/balance_inquiry`, `/v2/merchant/%s/giftcards/redeem`, `/auth/giftcards/balance_inquiry`, `/auth/giftcards/redeem`, `COS_URI_GIFTCARDS_BALANCE_INQUIRY`, com/clover/sdk/v3/payments/GiftCard, GiftCardTransaction, GiftCardResponse, GiftCardState, com/clover/core/api/payments/GiftCardPaymentType, IGIftCardPaymentListener, com/clover/sdk/v1/printer/job/GiftCardPrintJob, plus card transaction types GETBALANCE and BALANCE_LOCK. So the 327th's 'gift card 0 hits across 29 Go help articles' was a help-centre hole, not an absence. CLAIM CONJUNCTS: first-party gift cards — YES, Clover Gift Cards is Clover's own app/rail (Gyft is Clover's delivery wallet): 'With the Gift Cards app, you can issue, redeem, and manage gift cards directly from your device' (offer-clover-gift-cards). Real-time balance — YES: 'Transactions are tracked in real time, and you can view balances through the Gift Card app on your Clover device or the Gift Cards dashboard' (manage-gift-cards), and the Go app calls balance_inquiry directly. Online-ordering channel — PARTLY: 'Clover offers a free setup to help you start selling digital gift cards online ... They can redeem the card in person, online, or over the phone' (sell-digital-gift-cards), but that is the gift-card storefront, not the OLO checkout. Redeemable across EVERY location in the group — NOT PUBLISHED: no gift-card article in the 1,119-doc help corpus states group-wide redemption (tokenised scan of every gift-card doc for 'multi-location|all your locations|every location|across locations' returned only the multi-location SALES report and the customizable-reports page). Hence partial, not yes. Retrieved 2026-09-18. https://www.clover.com/en-US/help/manage-gift-cards · retrieved 2026-09-18 adversarially verified

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

payments-split-tender

Not scored by this record.

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

payments-refund-void-controls

Clover Go's own help article on refunds, tagged to the Go devices and the Go app for the US and Canada, puts refunds behind a role permission: 'Refunds can only be issued by employees whose roles include the Access Register > Refund payments permission', which the owner assigns per role on the dashboard under Employee Permissions. The in-app refund flow asks for a 'Refund reason', and the article notes 'You must configure refund reasons on the dashboard prior to selecting them.' Voids exist in the Go app, where the transaction search filters by 'Voids'. The Go-tagged articles never document void reasons. A separate article that carries no device or app tags says reason tracking, once enabled, prompts an employee on the dashboard or 'on a Clover device' and that the records 'automatically appear in the details of each order or transaction ... also available in the Transactions report'. It does not name Go. Named shortfalls: (1) the control checks the permission of the employee doing the refund. No manager PIN or approval step for an employee without that permission is documented. (2) No audit log is described as immutable or tamper-evident, and no void or refund record names an approver. The only documented approver field is on line-item discounts; see labor-manager-override-audit. (3) Discount permission is documented only for the legacy Go G1 app ('manage the discounts permission for employees from the Web Dashboard'). The current G2 settings list no such permission. (4) No-sale is not documented for Go either way. Across all 28 Go-tagged help articles, 'approver', 'approval', 'audit', 'immutable' and 'override' each occur zero times (whole-word counts). https://www.clover.com/en-US/help/issue-refund-go · retrieved 2026-09-15 adversarially verified

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

payments-chargeback-tooling

Not scored by this record.

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

payments-card-on-file

Not scored by this record.

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

payments-payout-timing

Not scored by this record.

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

payments-p2pe-pci4

Not scored by this record.

Items route to specific KDS stations by item, category, order type, or revenue center, with routing rules configurable per location without vendor involvement.

kitchen-station-routing

Item-level routing is real at Clover and is a KDS software feature, listed on the KDS page beside multi-level fulfillment, expo mode, prep time reporting and runner ticket printing. It therefore inherits the KDS plan gate: 'Merchants must be on a Register, Table Service Restaurant, or Counter Service Restaurant plan to purchase and use the Clover Kitchen Display System.' Clover Go sells exactly two software plans: the comparison page at clover.com/pricing/go has only a Starter and an Essentials column. Clover's developer documentation on merchant service plans maps every plan to the devices it supports, and it puts those two at the bottom of the ladder - cloud-based payments with employee and customer management, then a cash-register replacement with simple inventory and order management - each supporting only Mini, Flex, a tethered Mini-to-Mini, or no device at all. A kitchen printer and weight scales appear in the supported-device list of the Register, Counter Service Restaurant and Table Service Restaurant plans only, and order firing is named only as a Table Service Restaurant tool. Clover does also route without a KDS, one tier up: its casual-dining solutions page describes using item labels to send appetizers and entrees to the kitchen printer and drinks to the bar printer. That mechanism needs a kitchen printer, which appears in the supported-device list of the Register, Counter Service Restaurant and Table Service Restaurant plans and in neither of Clover Go's two. So with no KDS station to route to and no printer to route at, there is nothing at this tier for a routing rule to address. `station routing` occurs zero times across the 1,066-document corpus and `prep station` occurs once, in that casual-dining page - never in the 905-page developer corpus. https://www.clover.com/kitchen-display-system · retrieved 2026-09-09 adversarially verified

An expo screen consolidates items from multiple prep stations into a single order view and only marks the order complete when every contributing station has bumped its items.

kitchen-expo-consolidation

Expo mode is a named Clover KDS software feature and is gated with the rest of the KDS: 'Merchants must be on a Register, Table Service Restaurant, or Counter Service Restaurant plan to purchase and use the Clover Kitchen Display System.' Clover Go sells exactly two software plans: the comparison page at clover.com/pricing/go has only a Starter and an Essentials column. Clover's developer documentation on merchant service plans maps every plan to the devices it supports, and it puts those two at the bottom of the ladder - cloud-based payments with employee and customer management, then a cash-register replacement with simple inventory and order management - each supporting only Mini, Flex, a tethered Mini-to-Mini, or no device at all. A kitchen printer and weight scales appear in the supported-device list of the Register, Counter Service Restaurant and Table Service Restaurant plans only, and order firing is named only as a Table Service Restaurant tool. Consolidation across prep stations presupposes both a screen and multiple stations, and the Go tier has neither. `expo` occurs exactly once across the 1,066-document corpus, on the KDS page itself, and `expediter` occurs zero times. https://www.clover.com/kitchen-display-system · retrieved 2026-09-09 adversarially verified

Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator

kitchen-prep-time-pacing

Not scored by this record.

Kitchen load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator

kitchen-order-throttling

Not scored by this record.

Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator

kitchen-channel-pause-propagation

Not scored by this record.

Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator

kitchen-order-ready-callback

Not scored by this record.

KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.

kitchen-bump-bar-hardware

Clover documents exactly one bump bar and it is a KDS accessory: 'The KB9000 is a fully programmable kitchen display bump bar with touch operations.', offered with both the 14-inch and 24-inch KDS. It is unreachable from the Go tier for the same reason the KDS is - 'Merchants must be on a Register, Table Service Restaurant, or Counter Service Restaurant plan to purchase and use the Clover Kitchen Display System.' Clover Go sells exactly two software plans: the comparison page at clover.com/pricing/go has only a Starter and an Essentials column. Clover's developer documentation on merchant service plans maps every plan to the devices it supports, and it puts those two at the bottom of the ladder - cloud-based payments with employee and customer management, then a cash-register replacement with simple inventory and order management - each supporting only Mini, Flex, a tethered Mini-to-Mini, or no device at all. A kitchen printer and weight scales appear in the supported-device list of the Register, Counter Service Restaurant and Table Service Restaurant plans only, and order firing is named only as a Table Service Restaurant tool. A bump bar needs a kitchen display to bump, and the Clover Go product is a phone app paired with a Bluetooth card reader. https://www.clover.com/kitchen-display-system · retrieved 2026-09-09 adversarially verified

An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.

kitchen-all-day-counts

Not scored by this record.

Configurable target cook times per station or order type, with visual color escalation and/or audible alert when a ticket exceeds target.

kitchen-sla-alerts

Not scored by this record.

If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator

kitchen-printer-fallback

Not scored by this record.

KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator

kitchen-offline-operation

Not scored by this record.

Station screens can display item-level build/assembly detail (recipe steps, portioning, or full modifier breakout) rather than only the ticket line text. differentiator

kitchen-item-build-screens

Not scored by this record.

A bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order.

kitchen-recall-refire

Not scored by this record.

Edits made in the POS to an order already displayed in the kitchen visually flag the added, changed, or removed items on the live ticket. differentiator

kitchen-order-modification-alerts

Not scored by this record.

Bumping an order ready triggers a guest-facing notification — SMS/text, app push, or an order-status display board — without a separate product purchase. differentiator

kitchen-guest-ready-notification

Not scored by this record.

Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.

kitchen-waste-logging

Not scored by this record.

Reports actual ticket and per-station times (average and percentile) sliced by daypart, station, and order channel, exportable to CSV or an API.

kitchen-speed-of-service-reporting

Not scored by this record.

Generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list.

kitchen-prep-forecasting

Not scored by this record.

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

delivery-dispatch-board

Clover does not dispatch deliveries itself at any tier; it hands them to a third party. Its delivery page describes the flow as one where 'Everything is processed in your Clover POS and then dispatched to DoorDash for delivery to your customers.', with aggregators such as Grubhub as the alternative. There is consequently no undispatched-order queue, no driver availability view, no elapsed-time-per-order board and no multi-order run batching to build one from: `dispatch board`, `driver assignment`, `expo screen` and `run batching` occur zero times across the 1,066-document corpus, and the single occurrence of `dispatch` in the 905-page developer documentation is in a 3-D Secure SDK topic, unrelated to delivery. The Clover Go plan matrix carries no delivery row at all. https://www.clover.com/delivery · retrieved 2026-09-09 adversarially verified

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

delivery-address-validation

Not scored by this record.

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

delivery-daas-dispatch

Not scored by this record.

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

delivery-3p-direct-integration

Not scored by this record.

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

delivery-3p-injection

Not scored by this record.

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

delivery-menu-push

Not scored by this record.

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

delivery-86-sync

Not scored by this record.

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

delivery-store-pause

Not scored by this record.

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

delivery-3p-reconciliation

Not scored by this record.

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

delivery-injection-error-visibility

Not scored by this record.

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

delivery-tracking-page

Not scored by this record.

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

delivery-promise-time

Not scored by this record.

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

digital-first-party-web

330th: MOVED to partial; the 327th's 'online ordering 0 hits' was measured on a 29-article Go help subset and the app itself contradicts it. NEW SURFACE (330th) — THE CLOVER GO ANDROID APP ITSELF, unpacked: clover.companion.app v5.13 (the Play/App Store product 'Clover Go - Dashboard & POS', iOS bundle com.clover.clover-companion-app v5.13.1, 2026-08-27). 111.7 MB XAPK pulled anonymously from an apkpure mirror of the vendor's Play listing; it is Clover's own signed build (META-INF carries BUILD_INFO.clover-android-sdk, .clover-android-loyalty-kit, .clover-remote-*, .core-payments-kernel; package and version match the store listings). I parsed resources.arsc myself (.cache/q330/clover-go/arsc2.mjs) to the DEFAULT-locale string table: 4,484 string resources with their resource KEYS, i.e. the app's complete shipped UI vocabulary, plus 336,692 printable strings from the 8 classes*.dex (strings.mjs). This is an app-level census of the STORE-LEVEL product, which no prior pass on this vendor had (they used the help centre, its Contentful route census, the cloverstatic.com dashboard source maps and docs.clover.com). Grade B: vendor-shipped code, not published documentation. THE GO APP SURFACES THE FIRST-PARTY ORDERING CHANNEL: `settings_online_ordering` = 'Online ordering' (a Settings row, alongside `settings_online_booking`, `settings_online_shopping`, `settings_order_types`) and `online_orders` = 'Online Orders'. VENDOR STATEMENT ON THE CHANNEL ITSELF: 'Online ordering (OLO) is fully integrated with your POS, making it easy for customers to find and order from your restaurant. We create a branded online ordering page for you at no additional cost, giving customers a seamless way to place takeout, delivery, or curbside pickup orders ... Customers can immediately start ordering through your dedicated web page or the Clover consumer app. Service plan availability: Available on the Restaurant Growth plan' (set-up-online-ordering), and 'Online ordering (OLO) lets your customers place orders through a branded online website that seamlessly integrates with your POS menu' (online-ordering-faqs). So it is first-party, commission-free (no additional cost, no per-order marketplace fee) and writes into the POS menu/orders. WHY PARTIAL AND NOT YES: the URL is Clover-generated, not the restaurant's own domain — 'Clover automatically generates a URL based on your business name and location, which you can edit during setup' (online-ordering-faqs); the channel is gated to the Restaurant Growth plan, which a Go-only merchant need not hold; and setup runs through the Setup app on a Clover device rather than the Go app. Retrieved 2026-09-18. https://www.clover.com/en-US/help/set-up-online-ordering · retrieved 2026-09-18 adversarially verified

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

digital-menu-single-source

The developer inventory FAQ states an item's "Online Status" and "Description" fields "are part of the Clover Online Ordering (OLO) system and are not included in the standard Inventory API response" — the online-ordering attributes live on the same inventory item record the register sells from — and Clover's own blog (blog.clover.com/clovers-new-inventory-can-help-your-business-run-smoother) describes Clover Online Ordering merchants managing menu items, categories, modifiers and modifier groups in the Inventory interface, with per-item online visibility flags rather than a separate menu build. Named shortfall: Clover Online Ordering is a plan-dependent add-on, and nothing readable documents whether a Go-tier merchant has the channel at all — the record's digital-first-party-web cell is unresolved for the same reason, and the COO setup articles on the help centre (US and EU hosts) are client-rendered and returned no readable text. Single-source is established for the platform's COO channel, not for this product tier. https://docs.clover.com/dev/docs/inventory-faqs · retrieved 2026-08-04

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

digital-native-app

Not scored by this record.

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

digital-account-saved-payment

320th (no move): WIDENED the 319th's Go scope. The 319th counted only the 27 Task routes with 'go' in the SLUG; this pass scanned the union of the Contentful route census (.cache/q319/clover/ctf-docs.json, 906 Task routes) and the App Search corpus (1,197 unique docs) for every doc whose title or body names 'Clover Go', 'Go app' or 'Go G2': 71 docs, 47 of them WITHOUT 'go' in the slug (e.g. take-payment-for-appointments, view-appointments, manage-payment-settings, rewards-program-faqs, work-with-open-orders, start-a-manual-batch-closeout). Tokenised word-boundary controls over those 71: split* 0 docs; clock* 0; gift 1 (manage-payment-settings, a generic tender list 'Cash Credit Card Check Gift Cards EBT', not Go-scoped); offline 2 (manage-payment-settings: 'Clover Go: Set offline payment limits and preferences for specific devices, including transaction limits and cumulative thresholds'; search-filter-find-go2: payments filter), both PAYMENTS only; shift(s) 1 (explore-the-ui-go-g2 'add and manage employees and shifts', scheduling, not a punch); 'online ordering|online store' 3 (status page list; add-services/add-items 'Show online', services-business booking, not a Go order channel). Poison: 'shifts' is scheduling, 'offline' is card store-and-forward. Not a no: the Go app is closed-source and the help centre is not a feature enumeration. Retrieved 2026-09-16. Also: over the full 1,197-doc corpus, 'card on file|stored card|tokenized|order history' hit only Virtual Terminal, appointments payment, and merchant customer-record pages; 'reorder' hits only gift-card stock and Order with Google ('find, order, and reorder' - a Google channel, not first-party). No doc describes a guest account with saved cards/addresses on Clover's own ordering site. The 2026-08-04 note's 'help centre unreadable' is superseded. || 330th: 330th: TWO NEW SURFACES, STILL A HOLD. (1) Clover publishes the COMPLETE consumer-side checkout procedure for its own first-party channel, and it is a guest checkout with no account: 'Fill out your information for the order, including name, phone number, and email. Tap Add card to add your payment card information. (Optional) Add special instructions ... Tap Place Order' (place-online-orders-with-clover-app) — every step enumerated, no sign-up, no saved address, no stored card and no reorder step. (2) NEW SURFACE (330th) — THE CLOVER GO ANDROID APP ITSELF, unpacked: clover.companion.app v5.13 (the Play/App Store product 'Clover Go - Dashboard & POS', iOS bundle com.clover.clover-companion-app v5.13.1, 2026-08-27). 111.7 MB XAPK pulled anonymously from an apkpure mirror of the vendor's Play listing; it is Clover's own signed build (META-INF carries BUILD_INFO.clover-android-sdk, .clover-android-loyalty-kit, .clover-remote-*, .core-payments-kernel; package and version match the store listings). I parsed resources.arsc myself (.cache/q330/clover-go/arsc2.mjs) to the DEFAULT-locale string table: 4,484 string resources with their resource KEYS, i.e. the app's complete shipped UI vocabulary, plus 336,692 printable strings from the 8 classes*.dex (strings.mjs). This is an app-level census of the STORE-LEVEL product, which no prior pass on this vendor had (they used the help centre, its Contentful route census, the cloverstatic.com dashboard source maps and docs.clover.com). Grade B: vendor-shipped code, not published documentation. The Go app DOES hold vaulted cards (`card_on_file_button` = 'Pay with Card on File', `card_entry_type_vaulted` = 'VAULTED', pref `enableVaultedCard`, and customer records with addresses/emails/phones), but every published use is MERCHANT-initiated — Virtual Terminal ('To save the customer's card information, select Save Card on File. You must have the customer's permission', take-a-payment) and appointment no-show fees ('the customer's card on file is charged the cancellation fee', view-appointments). That is a merchant-held token, not a guest account on a first-party channel, i.e. adjacent to the claim rather than part of it. Not scored no: the consumer procedure is one article, not a census of the OLO/consumer-app surface. Retrieved 2026-09-18. adversarially verified

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

digital-upsell-engine

Not scored by this record.

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

digital-scheduled-pacing

Not scored by this record.

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

digital-fulfillment-modes

Not scored by this record.

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

digital-qr-table

Not scored by this record.

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

digital-kiosk

Not scored by this record.

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

digital-voice-ai-phone

Not scored by this record.

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

digital-drivethru-ai

Not scored by this record.

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

digital-sms-ordering

Not scored by this record.

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

digital-google-order

Not scored by this record.

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

digital-apple-business-connect

Not scored by this record.

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

digital-loyalty-attach

Not scored by this record.

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

digital-subscriptions

Not scored by this record.

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

digital-promo-parity

Not scored by this record.

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

digital-guest-data-ownership

Not scored by this record.

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

digital-checkout-pci-sca

Not scored by this record.

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

digital-surcharge-transparency

Not scored by this record.

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

guest-loyalty-unified-profile

320th (no move): WIDENED the 319th's Go scope. The 319th counted only the 27 Task routes with 'go' in the SLUG; this pass scanned the union of the Contentful route census (.cache/q319/clover/ctf-docs.json, 906 Task routes) and the App Search corpus (1,197 unique docs) for every doc whose title or body names 'Clover Go', 'Go app' or 'Go G2': 71 docs, 47 of them WITHOUT 'go' in the slug (e.g. take-payment-for-appointments, view-appointments, manage-payment-settings, rewards-program-faqs, work-with-open-orders, start-a-manual-batch-closeout). Tokenised word-boundary controls over those 71: split* 0 docs; clock* 0; gift 1 (manage-payment-settings, a generic tender list 'Cash Credit Card Check Gift Cards EBT', not Go-scoped); offline 2 (manage-payment-settings: 'Clover Go: Set offline payment limits and preferences for specific devices, including transaction limits and cumulative thresholds'; search-filter-find-go2: payments filter), both PAYMENTS only; shift(s) 1 (explore-the-ui-go-g2 'add and manage employees and shifts', scheduling, not a punch); 'online ordering|online store' 3 (status page list; add-services/add-items 'Show online', services-business booking, not a Go order channel). Poison: 'shifts' is scheduling, 'offline' is card store-and-forward. Not a no: the Go app is closed-source and the help centre is not a feature enumeration. Retrieved 2026-09-16. Also: 0 docs in the full 1,197-doc corpus describe customer dedup/merge ('merge' hits only multi-location ITEM merge and Dining guest lists). rewards-program-faqs (identifier = 'phone number or email address'; 'synced across all connected Clover devices and eligible business locations') was already judged adjacent in q310 and is not re-proposed. The 2026-08-04 note's 'help centre is client-rendered / unreadable' is superseded: the corpus is readable and silent. || 327th: NEW MEASUREMENT (327th) on a Clover-Go-scoped corpus nobody had built for this cell: 29 Clover Go help articles with full bodies (57,048 chars) plus the 905/905 docs.clover.com/dev census. 'loyalty' 0 hits and 'online ordering' 0 hits across all 29 Go bodies; 'customer' 11 docs / 34 hits, every one of them a receipt recipient, an appointment attendee or a card-present counterparty, never a stored guest profile. The Go app's complete top-level menu ('Employees | Inventory | Reporting | Closeout | Cash Log | Card reader | Help | Settings', explore-the-ui-go-g2) and its complete settings list (go-preferences) contain no Customers module. Held unknown, not scored: this claim is about the Clover PLATFORM guest record (Clover Customers, which does exist and is documented for the dashboard), and a Go-app-scoped silence cannot settle whether the platform profile unifies Go transactions with web and kiosk. Retrieved 2026-09-18. || 330th: 330th: CORRECTION TO THE 327th PLUS A NEW SURFACE, STILL A HOLD. NEW SURFACE (330th) — THE CLOVER GO ANDROID APP ITSELF, unpacked: clover.companion.app v5.13 (the Play/App Store product 'Clover Go - Dashboard & POS', iOS bundle com.clover.clover-companion-app v5.13.1, 2026-08-27). 111.7 MB XAPK pulled anonymously from an apkpure mirror of the vendor's Play listing; it is Clover's own signed build (META-INF carries BUILD_INFO.clover-android-sdk, .clover-android-loyalty-kit, .clover-remote-*, .core-payments-kernel; package and version match the store listings). I parsed resources.arsc myself (.cache/q330/clover-go/arsc2.mjs) to the DEFAULT-locale string table: 4,484 string resources with their resource KEYS, i.e. the app's complete shipped UI vocabulary, plus 336,692 printable strings from the 8 classes*.dex (strings.mjs). This is an app-level census of the STORE-LEVEL product, which no prior pass on this vendor had (they used the help centre, its Contentful route census, the cloverstatic.com dashboard source maps and docs.clover.com). Grade B: vendor-shipped code, not published documentation. THE 327th's STATEMENT THAT THE GO APP HAS NO CUSTOMERS MODULE IS WRONG for the shipped 5.13 build: `more_menu_customers` = 'Customers', `more_menu_customers_list` = 'Customers List', `more_menu_customer_rewards` = 'Rewards', a full guest record (`customer_add_title` 'Add customer', `customer_birthday_label`, `customerAddressAddTitle`, `customer_email_picker_description` 'Email addresses on file') whose deletion warning states the record holds purchase history — `customer_delete_confirmation` = 'This customer profile, including contact information, and order history will be permanently removed.' The app also embeds Clover's loyalty stack (META-INF BUILD_INFO.clover-android-loyalty-kit; dex: com/clover/sdk/loyalty/LoyaltyContract, ILoyaltyServiceV3, CustomerProvidedDataResponse, CloverCFPLoyaltyHelper) and calls /v1/merchants/{merchantId}/customers and /customers/cos/{customerId}. WHY IT STILL DOES NOT SETTLE THE CLAIM: nothing published describes DEDUP/MERGE behaviour — a tokenised scan of the 4,484-resource table for 'merge|duplicate|dedup' returns only duplicate-PAYMENT guards (`duplicate_transaction_alert_title` 'Duplicate Payment?', pref `bypassDuplicateCheck`), and 'merge' has 0 customer hits in the 1,119-doc help corpus. The only identity statement remains the rewards FAQ (phone or email identifier, 'Rewards are synced across all connected Clover devices and eligible business locations'), which a prior pass already judged adjacent, and kiosk/web unification is unstated in both corpora. Retrieved 2026-09-18. adversarially verified

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

guest-loyalty-thirdparty-identity-attach

Not scored by this record.

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

guest-loyalty-accrual-models

Clover Rewards is Clover's own loyalty program (not a bolt-on vendor) and a merchant can turn it on from the Go app: 'You can sign up through your Clover device, Go app, or Clover dashboard to go through a straightforward 2-step setup' (help article rewards-program-faqs, read via Clover's public help search engine 2026-09-15). The Go pricing table, in a Wayback capture of clover.com/pricing/go dated 2026-06-11 (the live page is an empty shell), has one row covering 'Create customer database / Offer promotions and loyalty program / Get private feedback / Offer gift cards': Not Included on Starter, Included on Essentials. That row lumps four features together, and the capture is three months old. The one way customers earn is points per dollar, at a fixed rate: 'For every dollar your customer spends, 1 reward point is granted', and 'Reward points are based on pre-tax customer spend'. Merchants set how many points each reward costs ('You can make any discount or item available for as many points as you want'), not how many points a dollar earns. SHORTFALL: the claim needs at least two ways to earn, and only one is documented, with a fixed rate. Visit counts show up only as bonuses in a paid add-on: 'With a bonus plus rewards subscription ... Regulars Bonus: ... A loyalty rewards member reaches Regular status after a set number of visits'; 'VIP Bonus: Use this to help your best customers earn points faster' (create-custom-bonus-plus-rewards-new, a dashboard procedure). That is a visit threshold that unlocks a bonus, not earning by punch or visit count, and no spend-tier earning is described. 'punch', 'visit-based', 'spend tier' and 'tiered' have zero hits across the 1,119 en-US help bodies. Those zeros are only an absence, which is why this is partial and not no. Starter-plan Go merchants do not get the loyalty row at all. https://www.clover.com/en-US/help/rewards-program-faqs · retrieved 2026-09-15 adversarially verified

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

guest-loyalty-offline-behavior

Not scored by this record.

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

guest-loyalty-offer-stacking-rules

Not scored by this record.

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

guest-loyalty-targeted-offers

Not scored by this record.

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

guest-loyalty-rfm-segmentation

Not scored by this record.

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

guest-loyalty-lifecycle-automation

Clover Rewards ships two of the three lifecycle triggers as set-once bonuses, reachable from the Go app; there is no win-back automation. Retrieved 2026-09-15 from Clover's help-centre search engine, which returns the full article text. Rewards is reachable from Go: rewards-program-faqs says 'You can sign up through your Clover device, Go app, or Clover dashboard' and 'You can easily activate a sign-up bonus to encourage new customers to enroll in your loyalty program'. The Go plan matrix (Wayback capture 20260611042802 of clover.com/pricing/go, the latest 200 capture; the live page is a script-only page with no content) lists 'Offer promotions and loyalty program' as Not included on Starter and Included on Essentials. BIRTHDAY (met): enable-birthday-and-signup-bonuses: 'Set an automatic bonus: Offer a one-time Sign-up bonus for signing up. Add a Birthday bonus.' These bonuses 'automatically display in the customer's Clover consumer app and the Customer app'. create-custom-bonus-plus-rewards-new: 'Birthday Bonus: Use this to reward your customers on their birthday. After receiving it, they have 30 days to redeem the bonus.' FIRST VISIT (loosely met): the Welcome/Sign-up bonus is an enrollment incentive, not a thank-you sent after a first visit. The article says it is 'only visible for customers who have not yet checked in to your program using the Clover consumer app' and 'They can redeem it on their first visit'. SHORTFALLS: (1) No lapsed-customer or win-back automation is documented. Searching 1,119 en-US help articles for win-back, winback, lapsed, haven't visited, inactive customers and last visit finds no loyalty page. The only 'lapsed' hits are inside 'collapsed' on table-order pages, and the only 'automatic offer' page (stop-or-cancel-real-time-promotions) gives no trigger. That is an absence, so it counts as a shortfall and not a no. (2) The bonuses are a fixed set (welcome, regulars, VIP, birthday), not a configurable trigger library. (3) They show up inside the consumer app when a customer is eligible; no outbound campaign send is documented. (4) Custom bonuses need 'a bonus plus rewards subscription' (that article is tagged US-only). At the Go tier, loyalty needs the Essentials plan. Scope caveat: none of the three loyalty articles is tagged with a Go device or the Go app. Go access rests on the FAQ's 'Go app' line plus the Go pricing matrix. https://www.clover.com/en-US/help/rewards-program-faqs · retrieved 2026-09-15 adversarially verified

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

guest-loyalty-native-email-sms

Not scored by this record.

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

guest-loyalty-consent-management

Not scored by this record.

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

guest-loyalty-10dlc-registration

Not scored by this record.

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

guest-loyalty-campaign-attribution

Not scored by this record.

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

guest-loyalty-data-export-portability

Not scored by this record.

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

guest-loyalty-review-capture-routing

Not scored by this record.

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

guest-loyalty-referral-program

Not scored by this record.

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

guest-loyalty-wallet-pass

Not scored by this record.

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

guest-loyalty-privacy-rights-tooling

Not scored by this record.

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

guest-loyalty-redemption-fraud-controls

Not scored by this record.

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

guest-loyalty-ai-offer-recommendation

Not scored by this record.

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

guest-loyalty-stored-value-gift

Not scored by this record.

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

labor-clock-in-at-pos

CLAIM: employees clock in and out at the POS terminal using a PIN, badge or card, with no separate time-clock hardware. VERDICT: no, on THREE independent Clover enumerations of the Clover Go app itself (not a sibling product, not the Station/Flex line). NEW SURFACE (327th): (1) the Clover Go app's own UI census - 'The More menu contains options to manage your business, pair your card reader (U.S. only), get help, set app preferences, and log out. Employees | Inventory | Reporting | Closeout | Cash Log | Card reader (U.S. only) | Help ... | Settings' (explore-the-ui-go-g2). That is the complete top-level menu and there is no Shifts, Timeclock or Time Clock entry. (2) The complete Go report list: 'Sales Overview, Sales Report, Tender and Card Types, Item Sales (Register Lite and Register plans only), Removed Items, Requested Reports, Order types ..., Employees, Discounts, Taxes ..., Deposit' (run-reports-on-the-clover-go-app) - an Employees report exists and it is a SALES report ('Top employees by amount collected'), with no labour or timecard report. (3) The complete Go settings enumeration - Transactions (Key/Scan card permission, Invoice number, Payment note, Quick sale, Carbon copy receipts), Inventory (Item images, Custom item), About your business (Change service plan), Security (Face ID, Inactivity timeout), Privacy (App analytics), Log Out (go-preferences) - no clock-in, break or punch setting. (4) NEW on the developer side: the 905/905 census of https://docs.clover.com/dev/llms.txt (309-page /dev/reference API reference included for the first time) publishes the Shifts object (employeecreateshift, employeegetemployeeshift(s), employeeupdateshift, employeedeleteshift, merchantgetshift, merchantgetallshifts) and 'clock in' occurs in exactly those 6 pages - but the Clover Go SDK's own published contents page enumerates the SDK surface as card-present payments, manual-entry payments, capture and tip adjust, payment reversal, closeout and receipts (clover-go-sdk-contents), with no shift/timeclock capability. BOUND: the 29 Clover-Go-specific help articles held with full bodies (57,048 chars: take-payments-with-go, take-payments-clover-go, explore-the-ui-go-g2, go-preferences, run-reports-on-the-clover-go-app, work-with-orders-on-clover-go, manage-inventory-go, view-closeout-history-go, search-filter-find-go2, set-up-clover-go, before-you-use-clover-go(-), download-and-log-in-to-the-go-app, issue-refund-go, send-invoice-go, tap-to-pay-on-iphone, troubleshoot-clover-go-setup-us-only/-canada-only, log-in-issues-and-fixes, issues-and-fixes-go-app, common-issues-fixes-go, connect-charge-go-reader, pair-a-card-reader-with-go-app, power-down/store-clover-go-reader, go-3, use-clover-go and the appointment articles that name Clover Go). TOKENISED CONTROLS over those 29 bodies: 'clock in' 0, 'shift' 0, 'time clock' 0, 'timeclock' 0. POSITIVE CONTROLS on the same 29 bodies: 'employee' 8 docs / 13 hits, 'customer' 11 docs / 34 hits, 'tip' 5 docs / 10 hits - so the staff vocabulary is present and punches simply are not. The employee concept in the Go app is login and permissions only ('Log in different users (different email addresses), single account ... enter their passcode or use Touch ID'). Retrieved 2026-09-18. https://www.clover.com/en-US/help/explore-the-ui-go-g2 · retrieved 2026-09-18 adversarially verified

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

labor-photo-punch-verification

Not scored by this record.

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

labor-geofenced-mobile-punch

Not scored by this record.

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

labor-offline-time-punch

Not scored by this record.

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

labor-granular-rbac

Clover's help centre (bodies read through its public App Search engine; the www.clover.com/en-US/help pages are JS shells) documents per-action permissions, custom roles and per-location role scoping, and names Clover Go among the surfaces they cover. Per action and per role: manage-roles-and-access-permissions says 'you can add permissions to existing roles and create custom roles with unique permissions', with 'Select Edit next to a feature to modify its permissions'; the three default roles (Admin, Manager, Employee) cannot be removed, but custom roles are additive, so this is not a fixed-tier model. Enforcement inside the Go app appears in two Go-tagged articles. issue-refund-go: 'Refunds can only be issued by employees whose roles include the Access Register > Refund payments permission'. go-preferences: key/scan card entry is controlled from 'Access Sale ... Access Manual Transaction', and you 'manage the discounts permission for employees from the Web Dashboard by selecting Employees > Permissions > Access Register'. Per location: add-role-multiple-locations says 'If you create or change permissions at the individual location level, they remain local to that location and do not roll up to the group level', and a role's customisable scope includes 'Individual location dashboard and POS permissions, including device and Clover Go'. different-software-plans-multi-location refers to 'Locations on the Essentials plan or below' inside a multi-location business, so per-location scoping is not confined to higher plans. SHORTFALL: (1) the role-editing and custom-role articles are platform-wide, not Go-tagged, and describe editing on the dashboard or in the Employees app on a Clover device; no Go article shows creating or editing a role in the Go app, and the Go pricing matrix (Wayback 20260611) lists only 'Manage employee profiles and shifts', with no permissions row; (2) of the claim's named actions, Go articles show only refund, manual/keyed entry and discount permissions, while void, comp, drawer open, price change and report access are not shown for Go; (3) per-location scoping works only inside a Clover multi-location business structure, and on Starter 'The Starter plan supports up to three employees, including the owner or admin'. https://www.clover.com/en-US/help/add-role-multiple-locations · retrieved 2026-09-15 adversarially verified

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

labor-manager-override-audit

Attribution exists for one override type: the line-item discount object carries an approver field, "The person that authorized a discount", alongside the order's own "Information about the employee who took the order", and both are readable after the fact through the Orders API. Named shortfall: that is the only documented approver attribution. The voids-and-refunds guide (docs.clover.com/dev/docs/voids-and-refunds) documents no authorizing-manager field, the orders guide documents no change history or log endpoint recording who edited, voided or price-overrode an order, and Clover publishes no immutability or tamper-evidence property for any of it. Clover's own help-centre articles on employee roles and manager passcodes are client-rendered and returned no readable text, so the till-side approval flow could not be read. https://docs.clover.com/dev/reference/ordercreatelineitemdiscount · retrieved 2026-08-04

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

labor-native-scheduling

Not scored by this record.

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

labor-demand-labor-forecast

Not scored by this record.

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

labor-realtime-labor-percent

Not scored by this record.

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

labor-overtime-prevention

Not scored by this record.

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

labor-minor-labor-rules

Not scored by this record.

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

labor-qualified-tips-w2-reporting

Not scored by this record.

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

labor-native-payroll

Not scored by this record.

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

labor-payroll-export-formats

Not scored by this record.

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

labor-shift-swap-workflow

Not scored by this record.

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

labor-server-performance-metrics

Not scored by this record.

Supports multi-level recipe/BOM costing where a recipe can contain sub-recipes (prep items) and plate cost recalculates automatically when any component ingredient's cost changes.

inventory-recipe-bom-costing

Clover names this gap itself. Its developer documentation carries a table headed 'Apps for Quick Service Restaurants' listing app types it invites third parties to build, and one of them is 'Recipe-based inventory' - tracking inventory based on the components that make up a menu item. A vendor advertising a capability as an opportunity for its App Market is stating that its own product does not have it. Clover's enhanced inventory page corroborates the shape: an operator manages items, categories, modifier groups and modifiers with stock levels, bulk editing and filters, with no ingredient, component, sub-recipe or plate cost anywhere beneath them. `bill of materials` occurs zero times across the 1,066-document corpus. `recipe` occurs in four developer documents and the sense is split, which matters: three use it for a code recipe, an API worked example under a `recipes/` documentation path. The fourth is the strongest evidence on this cell and points the same way - a table headed 'Apps for Quick Service Restaurants' lists app types Clover invites third-party developers to build, and among them is 'Recipe-based inventory' described as tracking inventory based on the components that make up a menu item. Clover is naming this as an unmet merchant need for its App Market to fill, which is a first-party absence stated by the vendor. Clover Go additionally sits on the two lowest plans, which Clover's developer plan documentation scopes as a cash-register replacement with simple inventory and order management - the entry rung of its own inventory ladder. https://docs.clover.com/dev/docs/merchant-needs · retrieved 2026-09-09 adversarially verified

Stores purchase unit, recipe unit, and count unit per item with explicit conversion factors, plus a yield/waste percentage applied to raw-to-usable conversion.

inventory-unit-conversion-yields

There is no unit system in Clover inventory to convert between. The enhanced inventory page describes managing 'your items, categories, modifier groups, and modifiers' with stock levels tracked per item, and nothing in it stores a purchase unit, a recipe unit, a count unit or a conversion factor, let alone a raw-to-usable yield percentage. `unit conversion`, `par level` and `bill of materials` occur zero times across the 1,066-document corpus, and the single occurrence of `yield` is in a developer topic on currency rounding, not a food yield. Clover Go's own plans reach only the simple-inventory rung of the developer plan table, not the enhanced inventory this page describes. https://www.clover.com/pos-systems/online-ordering-inventory · retrieved 2026-09-09 adversarially verified

Produces a theoretical-vs-actual usage variance report per item for a defined count period, showing theoretical usage from POS sales times recipe, actual usage from counts plus receipts, and the variance in both units and currency. differentiator

inventory-theoretical-vs-actual

Not scored by this record.

Depletes ingredient on-hand quantities in near real time as orders are fired at the POS, including depletion driven by modifier selections, not only in an end-of-day batch. differentiator

inventory-realtime-depletion

Not scored by this record.

Automatically 86s (marks unavailable) menu items on the POS, online ordering, and connected third-party delivery menus when a component ingredient hits zero or a configured threshold. differentiator

inventory-86-auto-sync

Not scored by this record.

Supports full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts.

inventory-count-modes

Stock is a single mutable value per item: the item_stocks update schema is quantity ("Current count of this item in stock"), the deprecated stockCount ("Deprecated, use quantity instead"), stockAlertThreshold, an item reference and modifiedTime — nothing else. No count-session, count-history or variance object exists anywhere in the Inventory API, and the inventory overview (docs.clover.com/dev/docs/working-with-inventory) enumerates the manageable set as item stock, modifiers, discounts and taxes with no counting workflow. Any full, spot or cycle count on Clover is therefore an in-place overwrite of quantity with no variance recorded as history — the mechanism the claim requires does not exist first-party; App Market third parties (e.g. Thrive) sell exactly this. https://docs.clover.com/dev/reference/inventoryupdateitemstock · retrieved 2026-08-04

Provides a mobile/tablet counting app supporting barcode or QR scanning that continues to accept counts with no network connectivity and syncs on reconnect.

inventory-mobile-count-offline

Not scored by this record.

Ships pre-built electronic vendor catalog and order-transmission integrations with named broadline distributors (e.g. Sysco, US Foods, Performance Food Group) that send purchase orders and receive invoices electronically rather than by emailed PDF. differentiator

inventory-vendor-catalogs-edi

Not scored by this record.

Ingests supplier invoices from photo, PDF, or email and extracts line-item detail (item, quantity, unit, price) into the inventory ledger without manual line entry. differentiator

inventory-invoice-ocr

Not scored by this record.

Tracks per-item purchase price history across invoices and alerts when a received price exceeds the prior or contracted price by a configurable threshold. differentiator

inventory-price-change-alerts

Not scored by this record.

Maintains par levels per item per location and generates suggested purchase order quantities from on-hand versus par, with at least one mode driven by a sales forecast rather than a static par. differentiator

inventory-par-auto-suggest

Not scored by this record.

Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.

inventory-waste-logging

Not scored by this record.

Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.

inventory-cogs-gl-export

Not scored by this record.

Inventory and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator

inventory-native-not-partner

Not scored by this record.

Joins recipe cost to actual item sales mix to report contribution margin per menu item, and flags items whose margin fell below a configured threshold after ingredient cost changes. differentiator

inventory-menu-margin-linkage

Not scored by this record.

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

reporting-realtime-dashboard

Clover Dashboard is available in browser and mobile app; refresh latency and Go-tier report scope not verified in this check. https://www.clover.com/pos-systems/clover-go · retrieved 2026-08-01

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

reporting-eod-closeout

Clover's dashboard Sales Overview report (Reports > Sales Overview) is a single end-of-day reconciliation document, but its availability on Clover Go is limited by plan. Help articles read from the help-centre search engine and confirmed live on 2026-09-15. First, 'Read a Sales Overview Full report' (read-sales-overview-full-reports) says: 'Start with the gross sales amount. Subtract amounts for discounts, refunds, and exchanges to get the net sales amount. Add amounts for non-revenue items, gift card activations, taxes and fees, tips, and service charges. Review the amount collected.' It adds a Tender Types section ('The total amount collected for all tenders should match the Amount Collected on the sales summary'), plus Cash Deposit and Cash Adjustments sections. Second, the Trends view of the same report (read-sales-overview-trends-reports) says 'Use this report during your closeout process to reconcile totals' and calculates the expected deposit: 'start with the cash sales amount. Subtract cash refunds. Add any cash added. Subtract any cash removed. Subtract any cash back ... subtract the tips payout to get the expected deposit'. It also says to 'Balance the till / Settle the cash drawer'. Scope for Go: neither article is tagged for Go (both carry the reporting app facet and no device facet). The Go-tagged article 'run-reports-on-the-clover-go-app' lists 'Sales Overview' among the reports in the Go app's More menu and defers to the dashboard reports documentation. SHORTFALL (plan tier): on the Go plan matrix (clover.com/pricing/go, Wayback capture 20260611; the live page is a soft-200 shell), 'Basic sales reports' is Starter-only and 'Detailed sales reports and tax reporting' is Essentials-only. In the Go app, 'Taxes', 'Item Sales' and 'Order types' are marked '(Register Lite and Register plans only)'. So a Go merchant is not documented as getting the full tax and discount reconciliation on every plan. Go's own 'Closeout' is card-batch settlement ('Batches on Clover Go are set to close automatically', view-closeout-history-go; 'Understand closeout' defines closeout as sending card transactions for clearing), not a reconciliation packet. Also, the expected-deposit arithmetic appears only in the Trends view; the Full view shows total cash sales and adjustments. https://www.clover.com/en-US/help/read-sales-overview-full-reports · retrieved 2026-09-15 adversarially verified

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

reporting-pmix-modifier-level

Item-level product mix is documented: the dashboard's "Item and Service sales report" shows "how many times a specific item was purchased within a selected timeframe", and applied modifications carry a quantitySold count described as "only used in reports". Named shortfall: Clover publishes no modifier-level PMIX report presenting modifier quantity with gross and net sales, and no daypart or revenue-centre filter — the same FAQ concedes "the default reports may not show daily breakdowns by item" and points merchants at exporting sales data to a spreadsheet. Clover Go has no revenue-centre concept at all. https://docs.clover.com/dev/docs/merchant-dashboard-and-reports-faqs · retrieved 2026-08-04

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

reporting-comps-voids-audit

Not scored by this record.

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

reporting-cash-over-short

Not scored by this record.

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

reporting-labor-productivity

Not scored by this record.

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

reporting-channel-profitability

Not scored by this record.

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

reporting-scheduled-delivery

Not scored by this record.

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

reporting-public-api

Not scored by this record.

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

reporting-webhooks

Not scored by this record.

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

reporting-api-not-upcharged

Not scored by this record.

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

reporting-tier-paywall

Not scored by this record.

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

reporting-history-retention

Not scored by this record.

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

reporting-anomaly-alerts

Not scored by this record.

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

reporting-nl-query

Not scored by this record.

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

reporting-guest-cohorts

Not scored by this record.

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

reporting-sales-forecast

Not scored by this record.

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

reporting-tip-tax-compliance

Not scored by this record.

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

multi-location-multi-brand

Not scored by this record.

The POS software runs on commodity off-the-shelf hardware (standard iPads, Android tablets, or PCs) that the operator can buy from a third party, rather than only on vendor-supplied proprietary terminals. differentiator

hardware-commodity-devices

Not scored by this record.

Vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs.

hardware-os-platforms

Clover names the client operating systems for the Clover Go app, iOS and Android, but its published minimum versions contradict each other, and the only device requirements it states are Bluetooth LE and a device that is not jailbroken or rooted. The Go-tagged help article 'Download and log in to the Clover Go app' (read in full through Clover's public help-centre search engine and re-queried 2026-09-15) says: 'To use the Clover Go app you need: iOS 11 or higher Android 6 or higher'. The Go-tagged help article 'Take payments with Tap to Pay on iPhone' gives a different minimum: 'Although the Clover Go app requires iOS 13 or higher, Apple requires iOS 16 or higher for Tap to Pay on iPhone', and it requires an 'iPhone XS or later'. The clover.com/go product page (Wayback id_ capture 2026-08-10; the live URL returns a JS shell) gives a third minimum: 'iOS version 15 and higher Android version 9.0 and higher. Please note: Clover Go will not function on a jailbroken or rooted device', and its reader specs read 'Compatibility: iOS 15 (Bluetooth LE required) and Android 9.0 (and higher)'. Shortfall: no single authoritative minimum OS version exists, because three first-party merchant surfaces give three different iOS floors (11, 13, 15) and two Android floors (6, 9). Also, no device hardware spec (supported models, RAM, screen) is published beyond Bluetooth LE, the non-rooted requirement and the iPhone XS floor for Tap to Pay. The Clover Go developer SDK's own minimums cover third-party developer apps, not the merchant Go app, and are not counted here. https://www.clover.com/en-US/help/download-and-log-in-to-the-go-app · retrieved 2026-09-15 adversarially verified

Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.

hardware-handheld-purpose-built

Not scored by this record.

The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator

hardware-handheld-battery-swap

Not scored by this record.

Handhelds support cellular/LTE connectivity as a documented fallback when store Wi-Fi drops, either built into the device or via a vendor-supplied failover.

hardware-handheld-lte

Not scored by this record.

Terminals continue to take orders, print to kitchen, and record cash sales with the internet down, and the vendor documents explicitly which functions degrade (card auth, loyalty lookup, refunds).

hardware-offline-mode

Clover Go keeps one thing going with the internet down: card payments. The Clover Go product page FAQ says: "If you're in an area with bad service or without Wi-Fi, you can take payments offline and the transactions will be authorized once you're connected again." The Go-tagged merchant help article 'Set up a Go card reader' (clover.com/en-US/help/go-3, read through the help centre's public search engine) agrees: "The Clover Go card reader (available in the U.S.) lets you take chip and contactless payments with or without a network connection." That is the merchant Go app. It is not the developer Go SDK, whose documentation says the SDK "does not support offline payments (Store-and-Forward)". SHORTFALL: the claim's other limbs are not met at this tier. Kitchen printing cannot happen, because a kitchen printer appears only in the supported-device lists of the Register, Counter Service and Table Service Restaurant plans, while Go sells only Starter and Essentials. Neither offline order entry nor offline cash recording is described in any Go-tagged help article. And no Go-scoped page documents which functions degrade, beyond the deferred authorization. Clover's general offline-payments articles ('Set up offline payments', 'Accept offline payments') do list degradations: a 7-day offline window, per-payment and total limits, a merchant-approval threshold, declined-payment risk, no EBT or gift cards, and 'Do not uninstall the app while offline'. But neither article names Go. One lists default-on devices as 'Clover Station, Station 2, Clover Mini, Flex, Mobile'. The other carries a Register-app facet and gives device Setup-app steps. So those limits are not attributed to Clover Go here. https://www.clover.com/go · retrieved 2026-09-15 adversarially verified

Sells or supports a dedicated kitchen display system with bump-bar or touch input, station routing, and course/fire timing, as a first-party product rather than an integration-only dependency.

hardware-kds

Clover the platform does sell a genuine first-party KDS - a 14-inch or 24-inch purpose-built kitchen unit at $799 or $899 plus $25 per device per month, with expo mode, item-level routing and a programmable bump bar. Clover Go merchants cannot buy it. The KDS page's own FAQ states the gate outright: 'Merchants must be on a Register, Table Service Restaurant, or Counter Service Restaurant plan to purchase and use the Clover Kitchen Display System.' Clover Go sells exactly two software plans: the comparison page at clover.com/pricing/go has only a Starter and an Essentials column. Clover's developer documentation on merchant service plans maps every plan to the devices it supports, and it puts those two at the bottom of the ladder - cloud-based payments with employee and customer management, then a cash-register replacement with simple inventory and order management - each supporting only Mini, Flex, a tethered Mini-to-Mini, or no device at all. A kitchen printer and weight scales appear in the supported-device list of the Register, Counter Service Restaurant and Table Service Restaurant plans only, and order firing is named only as a Table Service Restaurant tool. So this is a first-party product that exists one tier up and is excluded by plan from the tier this record scores, which is a documented exclusion rather than an absence of evidence. https://www.clover.com/kitchen-display-system · retrieved 2026-09-09 adversarially verified

Offers a self-order kiosk running the same menu and modifier engine as the POS, in both countertop and freestanding form factors, with integrated payment and accessibility (ADA) compliance documented. differentiator

hardware-kiosk

Not scored by this record.

Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, and speaker/headset integration, with a documented timer/speed-of-service measurement.

hardware-drive-thru

Not scored by this record.

Works with standard ESC/POS thermal receipt and kitchen printers from more than one manufacturer (e.g. Epson and Star), including LAN/Ethernet printers, rather than only vendor-branded printers.

hardware-printer-compatibility

Not scored by this record.

Supports the standard peripheral set — cash drawers (including multi-drawer per terminal), barcode scanners, scales for by-weight items, and customer-facing displays — with a published compatibility list.

hardware-peripherals

Not scored by this record.

Card entry happens on a PCI-listed PTS device using validated point-to-point encryption, so the POS application and tablet stay out of PCI scope; the vendor states the merchant's SAQ type.

hardware-p2pe-terminal

Not scored by this record.

Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. differentiator

hardware-tap-to-phone

Not scored by this record.

Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator

hardware-pricing-transparency

Not scored by this record.

Hardware can be purchased outright (owned) as an alternative to a mandatory lease or subscription-bundled rental, and the vendor states which. differentiator

hardware-ownership-vs-lease

Not scored by this record.

Vendor documentation confirms whether hardware purchased from the vendor remains usable with other software after cancellation, i.e. it is not software-locked or remotely bricked. differentiator

hardware-usable-after-churn

Not scored by this record.

Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.

hardware-byod

Not scored by this record.

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

extensibility-public-api-docs

docs.clover.com is fully public and self-serve, covering the Clover REST API and Android SDK; no NDA or sales call required. https://docs.clover.com/dev/docs/home · retrieved 2026-08-01

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

extensibility-api-access-cost

Not scored by this record.

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

extensibility-free-sandbox

Not scored by this record.

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

extensibility-oauth-partner-apps

OAuth 2.0 v2 flow with expiring access/refresh token pairs and scoped permissions granted when a merchant installs from the App Market; revocation not detailed. https://docs.clover.com/dev/docs/use-oauth · retrieved 2026-08-01

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

extensibility-webhooks-push

Order webhooks fire on CREATE, UPDATE and DELETE only — no distinct paid, voided or refunded event types, so state must be re-read. https://docs.clover.com/dev/docs/webhooks · retrieved 2026-08-01

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

extensibility-webhook-reliability

Not scored by this record.

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

extensibility-order-injection-api

Not scored by this record.

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

extensibility-doordash-preferred

Not scored by this record.

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

extensibility-first-party-delivery-integrations

Not scored by this record.

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

extensibility-middleware-compatibility

Not scored by this record.

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

extensibility-accounting-connectors

Not scored by this record.

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

extensibility-payroll-export

Not scored by this record.

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

extensibility-app-marketplace

Not scored by this record.

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

extensibility-headless-embedded

Not scored by this record.

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

extensibility-data-portability-exit

Not scored by this record.

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

reliability-offline-order-entry

330th: MOVED to partial. NEW SURFACE (330th) — THE CLOVER GO ANDROID APP ITSELF, unpacked: clover.companion.app v5.13 (the Play/App Store product 'Clover Go - Dashboard & POS', iOS bundle com.clover.clover-companion-app v5.13.1, 2026-08-27). 111.7 MB XAPK pulled anonymously from an apkpure mirror of the vendor's Play listing; it is Clover's own signed build (META-INF carries BUILD_INFO.clover-android-sdk, .clover-android-loyalty-kit, .clover-remote-*, .core-payments-kernel; package and version match the store listings). I parsed resources.arsc myself (.cache/q330/clover-go/arsc2.mjs) to the DEFAULT-locale string table: 4,484 string resources with their resource KEYS, i.e. the app's complete shipped UI vocabulary, plus 336,692 printable strings from the 8 classes*.dex (strings.mjs). This is an app-level census of the STORE-LEVEL product, which no prior pass on this vendor had (they used the help centre, its Contentful route census, the cloverstatic.com dashboard source maps and docs.clover.com). Grade B: vendor-shipped code, not published documentation. CONJUNCT 1, ORDER ENTRY CONTINUES OFFLINE: yes, and the app says so in its own words — 'Orders processed offline will appear as pending. Processing will complete as soon as the system comes back online.' (`pending_order_tab_info`), 'Offline payments allow you to accept cash, card, and check payments without a network connection' (`offline_payments_optin_settings_description`), with a store-and-forward banner (`store_forward_offline` = 'OFFLINE PAYMENTS STORE & FORWARD MODE') and an on-reconnect upload path including its failure case (`err_msg_failed_upload_detail` = 'Payments taken offline did not upload when the system reconnected. Please resubmit payments to try again.'). CONJUNCT 2, TICKET ROUTING: the product has no routing module — the 4,484-resource table has no kitchen/ticket/expo destination string; the only kitchen token is a REPORT (`more_menu_reporting_kds_reports` = 'Kitchen operations'). CONJUNCT 3, CHECK PRINTING: Go prints receipts to a paired Bluetooth printer and the app models the printer being unreachable (`send_receipt_printer_offline` = 'Unable to connect', `print_status_offline` = 'Offline'); nothing states check/ticket printing during a WAN outage, and receipts are deferred instead (`send_receipt_sent_offline` = 'A receipt will be sent to %s once you're online.'). One conjunct met and published, two not — partial, not the previous hold and not a no. Retrieved 2026-09-18. https://www.clover.com/en-US/help/accept-offline-payments · retrieved 2026-09-18 adversarially verified

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

reliability-offline-card-auth

Not scored by this record.

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

reliability-offline-decline-liability

Not scored by this record.

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

reliability-offline-kds-printing

The claim cannot be satisfied at this tier because neither of its two limbs exists here. There is no kitchen display - the Clover KDS is gated behind Register, Table Service Restaurant or Counter Service Restaurant plans, and Clover Go sells only Starter and Essentials - and there is no kitchen printer, which appears in the supported-device list of those same higher plans and in neither Go plan's. Clover Go sells exactly two software plans: the comparison page at clover.com/pricing/go has only a Starter and an Essentials column. Clover's developer documentation on merchant service plans maps every plan to the devices it supports, and it puts those two at the bottom of the ladder - cloud-based payments with employee and customer management, then a cash-register replacement with simple inventory and order management - each supporting only Mini, Flex, a tethered Mini-to-Mini, or no device at all. A kitchen printer and weight scales appear in the supported-device list of the Register, Counter Service Restaurant and Table Service Restaurant plans only, and order firing is named only as a Table Service Restaurant tool. Clover Go does have an offline capability, but it is a payments one: the Clover Go product page at clover.com/go says that in an area with bad service or without Wi-Fi the merchant can take payments offline and the transactions are authorized once connectivity returns. Payments, not tickets. https://www.clover.com/kitchen-display-system · retrieved 2026-09-09 adversarially verified

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

reliability-printer-fallback

The device specifications enumerate internal and compatible external printers per device — Station Duo and Station (2018) with a 3 1/8" internal printer plus the Star Micronics SP742ML, Mini 3/Mini 2/Compact/Flex 4/Flex 3 with an internal thermal receipt printer, Flex Pocket with none — and Clover Go appears in none of them. Clover Go is defined there as "a bring-your-own-device (BYOD) offering, designed for processing EMV payments through mobile devices" on a customer-supplied phone or tablet, so there is no configured kitchen printer to fail over from. The REST printing guide adds only that "the request is routed to the firing device's order printer or, if none is available, to its onboard printer" — a static route, not unreachable-printer failover — and describes no retry, no backup-printer or KDS redirect and no staff alert beyond a FAILED print-event state. https://docs.clover.com/dev/docs/clover-devices-tech-specs · retrieved 2026-08-04

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

reliability-offline-feature-matrix

Not scored by this record.

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

reliability-public-status-page

Not scored by this record.

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

reliability-247-live-support

Not scored by this record.

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

reliability-menu-build-service

Not scored by this record.

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

reliability-hardware-replacement-sla

Not scored by this record.

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

reliability-pci-dss-4-attestation

Not scored by this record.

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

reliability-mfa-role-based-access

Not scored by this record.

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

reliability-self-serve-training

Not scored by this record.

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

reliability-cellular-backup

Not scored by this record.

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

commercial-month-to-month-contract

Not scored by this record.

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

commercial-no-early-termination-fee

Not scored by this record.

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

commercial-autorenew-terms-published

CLAIM: the auto-renewal term and the cancellation notice window are stated in publicly accessible contract terms. VERDICT: partial/B. NEW SURFACE: the US Clover Terms of Service (www.clover.com/terms, 'Last updated: April 17, 2025'; live URL is a 7,820-byte JS shell to a browser UA, full 55,653-byte body served to a Googlebot UA; robots.txt bars only /v1-/v3, /setup etc., names no Anthropic agent). SCOPE IS CLOVER GO: the Terms 'govern your access to and use of Clover's products and services (including, but not limited to, any version of the Clover Go application and Clover Online Services)'. MET (notice window, public): 'Your obligations under these Terms continue for the longer of your use of the Clover Services, until you or we terminate your Clover Account by giving the other 30 days' notice'; 'Clover may add or change fees for Clover Services at any time and, if it does, it will provide you with 30 days' notice'. So the software terms are evergreen with a public 30-day notice, no fixed renewal term. SHORTFALL: the Terms defer to a separate 'payment processing agreement', and the Clover Go pricing page footer (Wayback id_ 20260611042802 of clover.com/pricing/go, and the 20260810 capture of clover.com/go) says of the hardware promotion 'Requires a 3-year contract. All other terms and conditions apply.' The term, renewal and early-termination terms of that processing contract are not linked from clover.com/terms (href census of the page: no program guide or merchant agreement PDF) and were not found publicly. Consistent with the sibling clover record (UK acquiring T&Cs, partial/B). Retrieved 2026-09-16. https://www.clover.com/terms · retrieved 2026-09-16 adversarially verified

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

commercial-processing-not-bundled

Not scored by this record.

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

commercial-interchange-plus-published

Not scored by this record.

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

commercial-rate-increase-clause

Not scored by this record.

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

commercial-pricing-published

Clover does publish plan and device pricing publicly, but the pages are client-rendered and no figures could be read or cited in this check. https://www.clover.com/pos-systems/compare · retrieved 2026-08-01

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

commercial-module-unbundling

Not scored by this record.

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

commercial-hardware-purchase-outright

Devices are sold outright direct from Clover, but bank/ISO channels also lease, and no figures were verifiable here. https://www.clover.com/pos-systems/clover-go · retrieved 2026-08-01

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

commercial-hardware-not-locked

Not scored by this record.

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

commercial-data-export-self-serve

Not scored by this record.

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

commercial-export-customer-and-loyalty

Not scored by this record.

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

commercial-post-termination-export-window

Not scored by this record.

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

commercial-data-ownership-clause

Not scored by this record.

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

commercial-pci-p2pe-tokenization

Not scored by this record.

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

commercial-pci-dss-4-controls

Not scored by this record.

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

commercial-privacy-dsar-tooling

Not scored by this record.

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

commercial-wcag-kiosk-accessibility

Not scored by this record.

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

commercial-dual-pricing-compliant

Not scored by this record.