Clover

order-capture-floor-plan-editor

A first-party floor plan exists: the developer docs state Clover Dining "uses a private data schema for features such as table mapping and guest seating". Shortfall — no fetchable documentation of multiple saved layouts, server-section assignment or table-state colouring; clover.com/help/dining-manage-table-orders returned only the page title "Clover Help" to a non-JS fetch on 2026-08-02. https://docs.clover.com/dev/docs/orders-faqs · retrieved 2026-08-02

order-capture-seat-level

"Guest seating" is named as a Clover Dining feature. Shortfall — seat-level item assignment, split-by-seat and per-seat coursing are documented nowhere fetchable, and the Dining schema is private, so orders created through the REST API cannot carry seat data at all. https://docs.clover.com/dev/docs/orders-faqs · retrieved 2026-08-02

order-capture-coursing-hold-fire

Clover Dining coursing: 'Manual coursing: server fires courses manually. Enabled by default' and 'Auto-coursing: courses are fired on schedule', with a per-table Auto-coursing screen on Station and Flex where firing times are adjusted in +/- 5 minute steps; 'Fire items in an order one at a time' documents More > Refire to Kitchen > select items > Print. Auto-coursing 'is available for all Table Service Restaurant plans'. https://www.clover.com/en-US/help/auto-coursing · retrieved 2026-09-03 adversarially verified

order-capture-split-merge

Split by item/amount/guest count is standard Clover behavior; merge and post-partial-payment split not documented publicly.

order-capture-bar-tab-preauth differentiator

Pre-auth is affirmatively a Clover payment method: the region table lists "Auth and pre-auth" as "Not supported" for Ireland and the United Kingdom and "Pre-auth" as "Not supported" for Austria, Germany and the Netherlands, which establishes it is supported in North America. Shortfall — nothing documents bar-tab behaviour specifically: pre-auth amount configuration, incremental re-authorisation, or automatic close of stale tabs. https://docs.clover.com/dev/docs/region-specific-features · retrieved 2026-08-02 adversarially verified

order-capture-transfer-audit

Transfers are native: 'You can transfer orders between servers without affecting the existing order... the order is saved in its current state so the new server can continue' — Clover Dining > table > More > Transfer Server > pick server > Transfer; the Work-with-orders suite also covers 'move orders across tables'. Shortfall — no audit trail: nothing documents that the transfer is logged naming both employees, and the item-availability FAQ pattern ('We do not currently have a log or report') recurs across Dining features. Full help-centre text read via the help centre's own search API; the HTML page is a client-rendered shell. https://www.clover.com/en-US/help/transfer-an-order-to-a-different-server · retrieved 2026-08-05

order-capture-native-handheld

Clover Flex 4 runs Clover POS natively on Android 13 and is documented as "ideal for restaurant table-side orders, at the counter, in line, or on the go", accepting "credit and debit cards, chip cards with PIN entry and signature, NFC-enabled cards from all major brands, and mobile payment services, including Apple Pay, Google Pay, and Samsung Pay". Firing to the kitchen: the developer FAQ states "You can configure the following as a default firing device: Clover Mini and Flex", and "you can set up a KDS as the order printer for a default firing device" (https://docs.clover.com/dev/docs/faqs). MIXED GRADE — the tableside fire flow itself belongs to the Clover Dining app, documented only on a vendor feature page: "This table mapping tool lets you send orders straight to the kitchen" (https://uk.clover.com/apps/clover-dining/, grade C). No Clover developer document describes Dining running on Flex. https://docs.clover.com/dev/docs/clover-devices-tech-specs · retrieved 2026-08-02 adversarially verified

order-capture-offline-order-entry

Orders can be rung and recorded on-device without a network connection — "Clover Mini and Flex are set to take offline payments for up to 7 days". Shortfall — the region table states "Canadian merchants cannot use their Clover devices to process any payments in offline mode" and that UK/Ireland "Payments are not processed if the Clover device is offline", and no complete offline feature matrix is published. https://docs.clover.com/dev/docs/handling-offline-payments · retrieved 2026-08-02

order-capture-qr-same-check differentiator

Scan to Order with Running Tabs puts guest QR orders onto the table's open tab in Clover Dining, not a separate paid ticket: guests 'can open your website again to add more items to the order' throughout the meal, the order 'appears under the assigned table number in Clover Dining' and 'servers can manage the order like they would a regular order' (tables show orange until paid, then green). Shortfall — nothing states guest items merge onto the same check as server-entered items (tables can hold multiple orders; combining orders is a separate manual action), Running Tabs works only at defined tables, and the mode is all-or-nothing: 'you must offer it at all tables in your restaurant' (running-tabs-faqs). https://www.clover.com/en-US/help/use-the-qr-code-for-scan-to-order · retrieved 2026-08-05

order-capture-kiosk-first-party differentiator

Clover sells a first-party Kiosk sharing the Clover inventory; ADA/accessibility conformance documentation not found.

order-capture-drive-thru

Downgraded from no on the enumeration audit of 2026-08-06. Neither leg of the original argument meets the bar for positive evidence of absence. (1) The cited help article enumerates online-ordering fulfillment methods only - 'You can fulfill online orders in the following ways: In-store pickup... Curbside pickup... Delivery through DoorDash drive (U.S. only)... Dine-in' - which is silent on a POS drive-thru order flow. (2) The 'complete device catalogue' leg is false: the tech-specs page says only 'Learn about the various models of Clover devices suited for various business needs' and its section nav lists Clover Station, Clover Mini, Clover Flex, Clover Compact and Clover Go - it does not list the Kiosk or KDS the note credits to it, so it is neither complete nor self-declaring. (3) Clover order types are freeform merchant-created labels ('Select Create custom order type. Enter a name for the order type'), so there is no closed list of order flows to argue from either. I also found no affirmative evidence Clover has drive-thru: a search result attributing 'drive thru order queues, including split-lane functionality' to Clover proved, on retrieval of payrocpos.com/clover-hospitality/, to describe Aloha on the same page. Assessed and unresolved. adversarially verified

order-capture-drive-thru-timers

Downgraded from no on the enumeration audit of 2026-08-06. This cell was derived entirely from order-capture-drive-thru, whose enumeration argument does not survive audit (the cited page enumerates online-ordering fulfillment methods, and the 'complete device catalogue' leg misdescribes a tech-specs page that asserts no completeness and omits Kiosk and KDS). The only independent basis left is the researcher's own note that a help-centre full-text search for drive-thru timers returned nothing - a negative search result, which is absence of evidence. The KDS Kitchen operations report and KDS delay thresholds are real but are not segment timers, so nothing here establishes presence either. Assessed and unresolved. adversarially verified

order-capture-voice-ai differentiator

No first-party voice agent found; Clover does publish a general partner API program, but no voice-specific program was retrievable.

order-capture-throttling differentiator

Overturned from no on the 2026-08-06 enumeration audit. Clover Hospitality by BentoBox online ordering has per-time-slot capacity limits with automatic quote extension: Order Pacing is set at 'Online Ordering > Location > Edit Location > Hours > Order Pacing' as a recurring day-of-week/time-of-day maximum of up to 50 orders every 15 minutes; 'Clover Hospitality by BentoBox tracks the prepare-by time for incoming orders and monitors those times for your pacing cap', and once a slot is full an incoming order is pushed to the beginning of the next 15-minute increment, the diner being quoted Prep Time plus the pacing threshold while still able to order. Full future slots grey out like a sold-out item. Shortfall - the cap is not per channel: 'your pacing maximums will apply to both of these order types' (pickup and delivery share one cap), third-party marketplace volume is outside it, the trigger is an order count rather than measured kitchen load, and the control exists only in the Clover Hospitality (BentoBox) ordering product - the Clover POS's own online ordering still enumerates just hours, a single static Food preparation time, a printer, a scheduled-order window and 3-D Secure. https://help.getbento.com/en/articles/419841 · retrieved 2026-08-06 adversarially verified

order-capture-scheduled-orders

Scheduling is affirmatively offered on first-party channels: “Clover also offers customers the convenience they desire with scheduled orders, allowing diners to order now and schedule a more convenient pickup time or delivery time later.” Shortfall — the claim’s mechanics are undocumented: no retrievable page describes a per-channel lead time or whether a future-dated order is injected into the make queue at a computed fire time rather than firing on receipt. The help centre is client-rendered (help slugs return only the title “Clover Help”) and community.clover.com does not resolve from this environment (DNS ENOTFOUND, 2026-08-03). https://blog.clover.com/reasons-you-need-to-try-the-new-clover-online-ordering-with-delivery-now/ · retrieved 2026-08-03

order-capture-catering

A quote workflow exists: Estimates (Sales activity > Estimates, Essentials plan and above, dashboard and Clover Go) with line items, 'payment terms, and even attachments', customer accept / decline by email or SMS, templates, and manual or automatic conversion to an invoice ('the final step in a quote-to-cash workflow'). Shortfalls: not catering-specific - no deposit or balance-due step on the estimate, no delivery / event schedule, and no link to the restaurant order queue or kitchen. https://www.clover.com/en-US/help/create-and-send-estimates · retrieved 2026-09-03 adversarially verified

order-capture-order-ready-signal differentiator

2026-08-05 sweep with full help-centre text. Read the Uber Eats FAQ, DoorDash FAQ/marketplace articles and the KDS suite: marketplace integrations document inbound order injection, menu sync and 86 sync, but no outbound order-ready event; the documented order-ready signals are guest-facing only (KDS 'Complete order' or Orders-app 'Mark as ready' fires an SMS to the customer — kiosk-order-notifications). Whether bumping an order notifies DoorDash/Uber Eats courier dispatch is stated nowhere. Unknown stands.

order-capture-void-comp-controls

Role-based employee permissions gate voids/discounts; mandatory reason codes and a dedicated exception report not documented publicly.

menu-pricing-nested-modifiers

Re-read 2026-08-02. A modifier carries id, name, price and a single parent modifierGroup reference; minRequired/maxAllowed live on the group. Nothing associates a modifier group to a modifier, and the docs enumerate item groups with variants as the alternative construct for deeper structure. https://docs.clover.com/dev/docs/managing-modifier-groups-modifiers · retrieved 2026-08-02 adversarially verified

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

Modifier price is a single scalar field on the modifier object ("name":"Tofu" "price":100). The documented model has no per-parent-item or per-size price table for a modifier. https://docs.clover.com/dev/docs/managing-modifier-groups-modifiers · retrieved 2026-08-02 adversarially verified

menu-pricing-fractional-placement differentiator

Re-read 2026-08-02 and it stands. The documented inventory model is item to modifier group to modifier, where a modifier carries only name and price. There is no placement, section, side or fraction attribute anywhere in the model and no pizza-specific construct. Fractional placement on Clover is App Market territory, not native. https://docs.clover.com/dev/docs/managing-modifier-groups-modifiers · retrieved 2026-08-02 adversarially verified

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

No pricing-rule object exists in the documented model capable of expressing a half-and-half rule (max vs average vs sum of halves), and modifiers carry no half/whole quantity concept. https://docs.clover.com/dev/docs/managing-modifier-groups-modifiers · retrieved 2026-08-02 adversarially verified

menu-pricing-topping-quantity-tiers

Positive absence by enumeration of the modifier model. A modifier carries only a name and a flat price (“Enter required information — mId, modifier name and price”; example body {"price":100,"name":"Tofu"}); a modifier group carries only minRequired/maxAllowed count limits. The order model is the closing half: an applied modifier on a line item is documented as “id — Unique identifier for the modifier applied to a line item. price — Additional cost, if any, for the modifier” (docs.clover.com/dev/docs/working-with-orders, read 2026-08-03) — no quantity, tier or multiplier field exists, so light/regular/extra/double at a per-tier multiplier can neither be configured nor represented on an order. The only expressible route is separate flat-priced modifiers, which is exactly what the claim excludes. https://docs.clover.com/dev/docs/managing-modifier-groups-modifiers · retrieved 2026-08-03

menu-pricing-size-style-matrix differentiator

Item groups model multi-attribute variants — create the group, add attributes such as Size, add options per attribute, associate items with the group; each generated combination is a distinct item. Shortfall — the docs show items with a single price field and never state that each generated variant carries its own price, there is no two-axis grid editor, and modifier prices do not vary per cell. The 2026-08-01 adversarial pass reached the same conclusion and explicitly said the correct value is partial, not yes. https://docs.clover.com/dev/docs/managing-items-item-groups · retrieved 2026-08-02 adversarially verified

menu-pricing-included-allowance differentiator

Positive absence by enumeration. The complete documented modifier model prices every modifier flat and unconditionally — a modifier is name + price, and group-level minRequired/maxAllowed are selection-count limits, not pricing logic. No allowance, included-count, overage-charge or substitution-credit construct appears anywhere in the enumerated inventory objects (items, categories, subcategories, item stock, modifiers, item groups, tags — docs.clover.com/dev/docs/working-with-inventory) or in the order representation of applied modifiers (id + price only). Three-toppings-included with charge-only-for-overage cannot be configured natively. https://docs.clover.com/dev/docs/managing-modifier-groups-modifiers · retrieved 2026-08-03

menu-pricing-combos

No native combo/meal engine with cart auto-detection found in fetchable docs.

menu-pricing-upsell-prompts differentiator

2026-08-05 sweep with full help-centre text (searched upsell, cross-sell, suggestions, recommended items across Register, Kiosk setup, and online-ordering menu articles). No configurable upsell/suggestive-sell prompt exists in any documented surface, and no attach-rate reporting; the Insights product recommends actions to the merchant, not add-ons to the guest. Absence not closed by enumeration of checkout behaviour, so unknown stands.

menu-pricing-86-propagation

Item stock is a first-class object — "Quantity of a specific item available in the inventory" — and inventory changes emit webhooks (event keys I, IC, IG, IM). Shortfall — no documented automatic 86 action at a threshold, and no documented propagation of an 86 to kiosk, online-ordering or third-party marketplace menus. https://docs.clover.com/dev/docs/working-with-inventory · retrieved 2026-08-02

menu-pricing-countdown-auto-86 differentiator

Item stock quantity is tracked per item. Shortfall — no documented countdown display at the point of order entry, no configurable auto-86 threshold, and no documented behaviour when stock reaches zero. https://docs.clover.com/dev/docs/working-with-inventory · retrieved 2026-08-02

menu-pricing-dayparting

Menu Management FAQs: 'Can I display different menus at different times of day? Yes. You can configure dayparts—such as breakfast, lunch, and dinner—and assign them to menus so that the appropriate menu displays automatically at the right time', with device menus also schedulable ('assign specific menus to point of sale (POS) devices and schedule them to appear at designated times'). Per-menu items and prices differ ('Each menu can display different categories, items, and prices'). OLO daypart assignment is per-channel (Items > Menus > Menu availability > Edit — assign-daypart-olo-menu), and the location timezone is set/verified under Settings > Business hours > Timezone (set-up-operational-information). Available 'to merchants with supported service plans at no additional cost'. https://www.clover.com/en-US/help/organize-offerings-with-menu-management · retrieved 2026-08-05

menu-pricing-channel-price-books

Per-channel price books exist as multiple menus: 'Can I have different pricing or items for different online ordering platforms? Yes. You can create unique menus for each platform, giving you full control over which items appear and at what prices for each service' — across Clover Online Ordering, BentoBox, Uber Eats, Grubhub, Order with Google and DoorDash, one active menu per channel (work-with-multiple-menus). Shortfall — prices are entered per menu; no percentage-markup rule applied to a base price is documented anywhere in the menu-management suite. https://www.clover.com/en-US/help/organize-offerings-with-menu-management · retrieved 2026-08-05

menu-pricing-dual-pricing differentiator

Cash-discount/dual-pricing is commonly enabled by Clover resellers and App Market apps; native item-level dual pricing across POS, kiosk and online not documented.

menu-pricing-allergen-nutrition

Allergen handling is order-time flagging, not menu data: in the Dining or Register app an operator taps Add Allergy on an item (predefined checkboxes plus up to 15 custom allergies, savable to the predefined list) or flags allergies per guest, and the allergen prints in the order summary. Shortfall — no allergen or nutrition attribute is stored on the menu item itself (the complete item object field set has none — docs.clover.com/dev/reference/inventoryupdateitem), nothing publishes allergen/nutrition data to online ordering or third-party menus, and recipe-derived nutrition is impossible (no recipe object exists). https://www.clover.com/en-US/help/manage-allergy-information · retrieved 2026-08-05

menu-pricing-recipe-linkage differentiator

The inventory model is enumerated as items, categories, subcategories, item stock, modifiers, item groups and tags. No recipe, bill-of-materials or ingredient object exists, so a menu item cannot be linked to a recipe natively. https://docs.clover.com/dev/docs/working-with-inventory · retrieved 2026-08-02

menu-pricing-3p-menu-push

First-party direct menu publish exists for both major marketplaces: DoorDash — 'You can create, pre-validate, preview, and publish a DoorDash menu—all from your Clover dashboard', with validation errors surfaced ('DoorDash will encounter errors while validating your menu. You will be prompted to... retry menu sync', up to 3 retries, then a failure message); Uber Eats — 'Your Clover menu will be used on Uber Eats... Menu refreshes take place hourly. Out-of-stock updates are immediate' (uber-eats-faq). Shortfall — error surfacing is menu-level at validation/onboarding; no per-item sync status or per-item rejection report is documented. https://www.clover.com/en-US/help/doordash-frequent-questions · retrieved 2026-08-05

menu-pricing-dynamic-pricing

Rule-based price variation by time and channel is native: daypart-assigned menus switch automatically ('the appropriate menu displays automatically at the right time') and each menu carries its own prices per channel and per device. Shortfall — no demand-based pricing exists, and no floor/ceiling guardrail construct is documented; price variation is achieved only by authoring separate menus. https://www.clover.com/en-US/help/organize-offerings-with-menu-management · retrieved 2026-08-05

payments-processor-choice differentiator

Processing is assigned by Clover, not chosen by the merchant: the region table states Brazil and Mexico "Payment transactions" are "processed through SiTef", and gift cards are "managed through the Fiserv payment gateway". No third-party processor option is documented anywhere in the payments documentation. https://docs.clover.com/dev/docs/region-specific-features · retrieved 2026-08-02

payments-published-rates differentiator

Flat rates are published for the direct channel on clover.com, but that page is JS-rendered and unfetchable; bank/ISO-sold accounts are quote-only.

payments-dual-pricing differentiator

Available via reseller programs and App Market apps; native two-price storage with both totals on the check not documented.

payments-surcharge-guardrails differentiator

Debit exclusion is BIN-based and documented: “Surcharges are only applied when the customer pays with an eligible credit BIN credit card; they are not added to debit, cash, or other forms of payment.” Jurisdiction guardrails are at onboarding: “Clover onboards merchants for credit card surcharging in the following countries: Canada, excluding Quebec [and] United States, excluding states with legal restrictions or prohibitions.” The rate is Clover-controlled, not merchant-editable (“Merchant editable? No, Clover configures the surcharge rate when the merchant is onboarded”; Canada flat 2.40%, “most US merchants having a surcharge of 3.00%”). Shortfall — prepaid-card exclusion is not stated in any retrievable page, no per-location enable/disable toggle is documented (configuration happens at merchant onboarding), and network-cap enforcement is implied by Clover setting the rate rather than stated as a check. https://docs.clover.com/dev/docs/transaction-data · retrieved 2026-08-03

payments-emv-nfc

Current devices ship EMV contact, contactless and magstripe: Flex 4 and Flex Pocket "EMV Contact (chip), EMV Contactless (tap), and Magstripe Reader"; Flex 3, Mini 2/3 and Station Duo "EMV chip card reader, NFC reader, and MSR reader". Wallets are named explicitly — Flex 4 accepts "NFC-enabled cards from all major brands, and mobile payment services, including Apple Pay, Google Pay, and Samsung Pay"; the Clover Go reader "accepts chip, dip, and contactless payments, including Tap-to-Pay on iPhone, Apple Pay, Google Pay, and Samsung Pay". Exception on legacy hardware: Clover Station (2018) lists only "EMV chip card and MSR readers", with NFC arriving via the optional printer carrying a "4.3 inch customer-facing display and NFC reader". https://docs.clover.com/dev/docs/clover-devices-tech-specs · retrieved 2026-08-02 adversarially verified

payments-softpos-tap-to-pay differentiator

Re-sourced from a Fiserv press release to Clover developer documentation, clearing the differentiator grade floor. The Android SDK FAQ states "While Tap to Pay on iPhone allows contactless payments without additional hardware, this feature is not available for Android devices", and the device spec page records that Clover Go "accepts chip, dip, and contactless payments, including Tap-to-Pay on iPhone". The claim admits either platform ("and/or"), and the iPhone half is documented. Documented limit rather than an absence of evidence: "For Android, a physical Clover card reader, such as the Clover Go, or a dedicated Clover device, such as the Flex or Mini, is still required to process contactless payments." https://docs.clover.com/dev/docs/android-sdk-faqs · retrieved 2026-08-02 adversarially verified

payments-pay-at-table

The hardware exists: Flex 4 and Flex Pocket are handheld terminals with EMV contact/contactless/magstripe and 4G LTE. Shortfall — the pay-at-table workflow itself (fire from the table, split at the table, tip on the handheld) belongs to Clover Dining, whose help pages are client-rendered and return no content. https://docs.clover.com/dev/docs/clover-devices-tech-specs · retrieved 2026-08-02

payments-qr-guest-pay differentiator

Scan to Pay is native and on by default: 'a unique QR code is printed at the bottom of each table-level printed bill', guests scan with their phone camera, pay via Apple Pay (iOS), Google Pay (Android) or manual entry on 'a secure Clover-hosted page', choose a tip, and the transaction (method, time, tip, bill details) is viewable on the dashboard/device; merchants can disable it under Settings > Transactions > Payments > Scan to Pay Settings. Shortfall — 'Scan to Pay QR codes do not appear on bills for individual guests or split bills', and automatic closure of the check on payment is not explicitly documented. https://www.clover.com/en-US/help/take-a-payment-with-scan-to-pay · retrieved 2026-08-05

payments-tip-adjust

On-device tip prompt and tip adjust are standard; the documented batch/adjust window and an unadjusted-tips manager screen were not retrievable.

payments-tip-pooling differentiator

Positive absence by enumeration. The complete Tips documentation suite covers tip suggestions (up to 4, percentage or smart flat tipping), tip entry location (screen vs paper receipt), tip adjustment on paper receipts, and Autofill $0.00 — no pooling or distribution rule exists anywhere in it; the platform Shift object carries only cashTipsCollected with no pool fields (grade-A prior finding), and Clover's own apps catalogue positions tip/time tooling in the paid third-party Time Clock by Homebase app. A lone blog marketing sentence claims Clover can 'Pool tips'; no configuration, report or API object supports it anywhere in vendor documentation. https://www.clover.com/en-US/help/set-tip-amounts · retrieved 2026-08-05

payments-offline-store-and-forward differentiator

"By default, Clover Mini and Flex are set to take offline payments for up to 7 days", and merchants "can set limits on the transaction amount for offline payments or the total amount processed in an offline state" — both the per-transaction and the cumulative limit the claim requires. Region pills on the page: United States, Canada, Europe (an earlier note asserting a Canada/UK/Ireland exclusion is not supported by the page and has been removed). Two documented limits: the page opens "Some merchants are configured to accept payments offline", so it is a per-merchant configuration; and an integrator can defeat the rails — "Allowing any offline payment with one of the offlineOptions overrides any merchant-configured limits ... This includes the limit on days before going online, as well as the amount limit on each transaction and the total offline payments limit." https://docs.clover.com/dev/docs/handling-offline-payments · retrieved 2026-08-02 adversarially verified

payments-offline-decline-liability differentiator

The risk model is partly documented — a 7-day default offline window on Mini and Flex, merchant-settable per-transaction and cumulative caps, and the statement that by using the offline settings "you assume responsibility for warning the merchant of any possible risk and enforcing any limits on offline transactions required for the merchant". Shortfall — that sentence assigns a duty to warn to the integrator, not decline liability to a party; the docs never state who absorbs a declined offline transaction, and describe no post-reconnect failure report. The 2026-08-01 pass read this as a full liability assignment; re-read on 2026-08-02 it does not say that. https://docs.clover.com/dev/docs/handling-offline-payments · retrieved 2026-08-02 adversarially verified

payments-gift-cards

SHORTFALL — cross-location redemption is undocumented. Native first-party gift cards are real: "Clover native gift cards use the Clover-integrated Gift Card Solution, managed through the Fiserv payment gateway", "Fully integrated into the Clover POS system", physical (4-8 digit SCV) and virtual, with activate / redeem / balance inquiry / reload / cash out / refund / void endpoints, split tender and multi-lock, and no expiry. The online-ordering leg is documented via "Settings > Business Operations > Sell Digital Gift Cards Online" on the Merchant Dashboard. But nothing states a card is redeemable across every location in a group — the API roots at one merchantId. Two further limits: the page is region-pilled United States and Canada only, and merchants must "Sign up for Clover Gift Cards plans" first, so this is a separately subscribed product. https://docs.clover.com/dev/docs/gift-card-api · retrieved 2026-08-02 adversarially verified

payments-house-accounts

2026-08-05 sweep with full help-centre text (searched house account, on account, tab, credit limit, statement). No house-account construct exists in the help centre; nearest documented features are Invoices, Estimates-to-invoice conversion, recurring payment plans with card/ACH on file (recurring-payments-faqs), and Pay by Bank/ACH one-time tenders. None provides per-account credit limits or a running balance with periodic statements. Absence not closed by enumeration, so unknown stands.

payments-split-tender

One split-tender path is documented — "Use the complete or partial value on an active gift card for a transaction", i.e. a partial gift-card redemption leaves a remaining balance due. Shortfall — general multi-tender (two cards, or card plus cash, on one order) is not documented in the payments or orders documentation. https://docs.clover.com/dev/docs/gift-card-api · retrieved 2026-08-02

payments-refund-void-controls

API-side controls are documented: "Write payments — Required to add and update payment records" gates refund and void calls, and the developer FAQ covers void and refund procedures. Shortfall — no documentation of manager-approval thresholds, mandatory reason codes, or a void/refund exception report at the POS. https://docs.clover.com/dev/docs/permissions · retrieved 2026-08-02

payments-chargeback-tooling differentiator

The Clover Dashboard surfaces disputes with evidence submission; scope and assembly from the POS record not documented publicly.

payments-card-on-file differentiator

Card vaulting exists as a documented method — the region table lists "Cards cannot be stored for future transactions using the vaultCard() method" as a limitation for Ireland, the United Kingdom and Argentina, which establishes vaultCard() is available elsewhere. Shortfall — no documentation of consent capture, token expiry handling, network tokenisation or account-updater behaviour. https://docs.clover.com/dev/docs/region-specific-features · retrieved 2026-08-02

payments-payout-timing differentiator

Next-day funding is the standard Clover schedule and an instant/Rapid Deposit option exists for a fee; exact published schedule not retrievable.

payments-p2pe-pci4

Clover states it "is compliant with applicable PCI DSS requirements, including those related to card-not-present (CNP) transactions", "validated by a Qualified Security Assessor (QSA)", and documents TransArmor tokenization that replaces cardholder data with tokens. Shortfall — no Attestation of Compliance is published or linked, no PCI-listed P2PE solution is named, and merchants on their own domains are told they are "responsible for their own PCI compliance". https://docs.clover.com/dev/docs/pci-dss-version-40-requirements-643-and-1161 · retrieved 2026-08-02

kitchen-station-routing

Routing is by Printer label: on each KDS, 'For Kitchen mode: Tap the Printer labels you would like routed to that specific display. For Expo mode: Tap the Printer labels you would not like routed to that specific display', plus a per-KDS 'Filter tickets by order type' setting (dine-in, take-out, delivery). Printer label is an item attribute and can vary by location. Shortfall: no routing rules by category or revenue centre, and no rule editor beyond item labels and the per-display order-type filter. https://www.clover.com/en-US/help/route-order-tickets-to-kds · retrieved 2026-09-03 adversarially verified

kitchen-expo-consolidation

Clover KDS setup offers two device modes: 'Kitchen mode shows items with a printer label, while Expo mode displays all items and orders in the restaurant' — a consolidated all-station expo view exists. Read on a Clover reseller's mirror of the first-party KDS help content (grade E) because clover.com/help/kitchen-display returns only 'Clover Help' to a non-JS fetch (retested 2026-08-04). Shortfall — completion gating is not documented: the same text describes a manual flow ('Tap each item to mark it as ready... Select the ticket menu and mark the order as finished'), and nothing states an expo order only completes once every contributing station has bumped its items. https://processwithturnkey.com/clover-support-how-to-set-up-a-kitchen-display-system/ · retrieved 2026-08-04

kitchen-course-firing differentiator

Coursing is native to Clover Dining and enabled by default: 'Clover Dining coursing lets you separate items and fire them to the kitchen in sequence' with 'Manual coursing: server fires courses manually' (set-up-meal-coursing; Dining settings > Coursing). Auto-coursing adds scheduled firing from a Station or Flex handheld — 'preset coursing times... so your courses are automatically sent to the kitchen', per-table on-the-fly adjustment in +/-5-minute increments, 'available for all Table Service Restaurant plans'. The prior passes could not read this page (SPA shell); full text retrieved 2026-08-05 via the help centre's own search API. https://www.clover.com/en-US/help/auto-coursing · retrieved 2026-08-05

kitchen-prep-time-pacing differentiator

Positive absence by enumeration: 'Two time settings are available on the KDS' — a ticket timestamp/live timer and delay thresholds (yellow/red escalation). That is the complete documented KDS timing model; no per-item cook time field exists (the item object has none — docs.clover.com/dev/reference/inventoryupdateitem) and no staggered item start/display logic appears anywhere in the KDS settings suite (layout, interaction, timing, order-type filter, other settings). https://www.clover.com/en-US/help/kds-configure-ticket-timing · retrieved 2026-08-05

kitchen-order-throttling differentiator

Overturned from no on the 2026-08-06 enumeration audit. Clover Hospitality by BentoBox online ordering documents Order Pacing, a configurable order-volume threshold that automatically extends quoted prep time: a recurring day-of-week/time-of-day maximum of up to 50 orders per 15-minute slot set at 'Online Ordering > Location > Edit Location > Hours > Order Pacing'; 'Clover Hospitality by BentoBox tracks the prepare-by time for incoming orders and monitors those times for your pacing cap'; once a slot is at capacity the next order is quoted the following 15-minute increment (Prep Time plus the pacing threshold) and full future slots grey out. Shortfall - what is throttled is the promise, not the kitchen: tickets are not held back from or released to the KDS on a pacing rule, there is no ticket-time (as opposed to order-count) trigger, one cap spans pickup and delivery rather than per channel, third-party marketplace orders bypass it entirely, and the Clover POS's own online-ordering settings still offer only the manual stop/pause toggle with timed auto-resume plus a manually entered receipt-print buffer. https://help.getbento.com/en/articles/419841 · retrieved 2026-08-06 adversarially verified

kitchen-channel-pause-propagation differentiator

86 propagation is documented for Uber Eats: 'Does this integration support marking items as unavailable (86'ing) items? Yes... Uber Eats then gets notified and takes action in real time', with 'Out-of-stock updates are immediate'; item availability can be toggled 'from the web or on the device' (item-availability-faqs) and auto-86 fires when stock hits zero (automatically-manage-item-availability). Store pause per channel exists from the dashboard (DoorDash toggle with timed resume). Shortfall — modifier/item-option 86 propagation is undocumented, DoorDash-side 86 sync behaviour is not described, and neither pause nor 86 is documented as actionable from the KDS itself. https://www.clover.com/en-US/help/uber-eats-faq · retrieved 2026-08-05

kitchen-order-ready-callback differentiator

2026-08-05 sweep with full help-centre text. The KDS bump flow is documented (Kitchen mode: mark items complete, 'Mark Ready'; Expo mode: 'Mark Complete'), and the only documented downstream effect is a guest SMS ('the customer will receive a text message letting them know their order is ready' — kiosk-order-notifications). Whether a KDS bump emits an order-ready event to DoorDash/Uber Eats for courier dispatch is stated nowhere in the Uber Eats FAQ, DoorDash articles, or KDS suite. Unknown stands.

kitchen-bump-bar-hardware

'Both Clover kitchen display system models support a bump bar' (setup guide and video published), and the supported model is specified by the troubleshooting article: 'Purchase the bump bar from Clover or Fiserv for it to work properly with the KDS. Third-party bump bars may not function correctly due to compatibility limitations' — USB-connected, with documented power/connection diagnostics (tsg-kitchen-display-system-resolve-bump-bar-issues). https://www.clover.com/en-US/help/bump-bar · retrieved 2026-08-05

kitchen-all-day-counts

Positive absence by enumeration of the KDS settings suite (layout, interaction, timing, order-type filter, other settings). The only aggregation documented is per-ticket: 'Group identical items together' collapses repeats within one order ('Burger × 5'). No all-day view aggregates outstanding quantities per item across open tickets on a station, and no such screen appears in Kitchen mode or Expo mode documentation. https://www.clover.com/en-US/help/kds-other-settings · retrieved 2026-08-05

kitchen-sla-alerts

Configurable per-display delay thresholds with colour escalation, on by default: 'Tickets approaching delay display as yellow after 7 minutes and in red after 10 minutes', adjustable per KDS under Settings > Ticket timing ('set your preferred delay thresholds'), with an optional live count-up timer per ticket — 'Once the ticket reaches the configured delay thresholds, the ticket will turn yellow and then red accordingly.' Thresholds are per display (station), not per order type; no audible alert is documented (claim requires either). https://www.clover.com/en-US/help/kds-configure-ticket-timing · retrieved 2026-08-05

kitchen-printer-fallback differentiator

A fallback is documented in the Print API: print requests route "to the firing device's order printer or, if none is available, to its onboard printer". Shortfall — that is a single hop to the device's own printer; no failover between kitchen printers, no failover from KDS to printer, and no alerting on a failed print is documented. https://docs.clover.com/dev/docs/printing-orders-rest-api · retrieved 2026-08-02

kitchen-offline-operation differentiator

Clover Local Connect provides exactly this: 'even if the internet is down, you can still take an order at the register on a Clover device, and it will show up on the Clover KDS' — devices talk 'directly through a local network' (Wi-Fi or wired), designed for standard LAN equipment, explicitly positioned as temporary outage coverage ('You still need the internet to do things like process credit card payments'). The prior pass saw only the SPA shell and an index snippet; full article text retrieved 2026-08-05 via the help centre's own search API. https://www.clover.com/en-US/help/use-kds-offline · retrieved 2026-08-05

kitchen-item-build-screens differentiator

Kitchen mode shows per-item detail beyond the ticket line: 'any applicable course modifiers will be shown below each respective item', special instructions are displayable ('Show custom items in tickets' — e.g. 'No onions', 'Extra cheese'), and kitchen-specific alternate item/modifier names can be shown full or compact (kds-other-settings). Shortfall — no recipe steps or portioning detail can be displayed: no recipe object exists in the platform, so build detail is limited to modifiers, custom items and alternate names. https://www.clover.com/en-US/help/kds-kitchen-mode · retrieved 2026-08-05

kitchen-pizza-fractional-display differentiator

No fractional placement exists in the menu model, so nothing sectioned can be rendered on the make line.

kitchen-recall-refire

Refire exists at the POS: in Clover Dining 'Tap More. Tap Refire to Kitchen. Select the checkboxes for the item(s) you want to fire, then tap Print' re-sends chosen items to the kitchen printer without re-entering the order. Shortfall: no KDS recall/unbump is documented; Kitchen mode ('tap the open circle next to an item to mark the item as complete... tap Mark Ready') and Expo mode ('tap Mark Complete to clear the ticket') are forward-only. https://www.clover.com/en-US/help/selectively-fire-items-in-an-order · retrieved 2026-09-03 adversarially verified

kitchen-order-modification-alerts differentiator

2026-08-05 sweep with full help-centre text across the KDS suite (kitchen/expo modes, ticket layout, interaction, timing, other settings) and Dining order-editing articles. Nothing documents how an edit to an already-fired order renders on the KDS — added/changed/removed items flagging is neither described nor denied. Unknown stands.

kitchen-guest-ready-notification differentiator

Clover Online Ordering sends guest order-status texts; whether a KDS bump is the trigger is not documented.

kitchen-waste-logging

Downgraded from no on the enumeration audit of 2026-08-06. The cited page is 'Set up other KDS settings', which enumerates display checkboxes (move ready items to the bottom, group identical items, show custom items, show guest number, alternate inventory names) - a settings list, not a list of the actions available on the KDS screen, so it cannot establish that no waste/remake action exists there. The second leg rests on clover-reports-overview, an overview page, which does not qualify as an exhaustive enumeration. I separately searched the help centre for waste, spoilage and remake logging and found only the Removed Items report ('items removed from orders after the item was entered, but before the sale occurred') and the Track reasons for voids and refunds setting - neither is kitchen-side and neither depletes stock - but a null search is absence of evidence. Assessed and unresolved. adversarially verified

kitchen-speed-of-service-reporting

Kitchen operations report (Reports > Kitchen operations): 'Item volume per hour. Average time for item preparation. Average time for order fulfillment. Chart displaying items prepared per station. List of items that take the longest to prepare', date range today / this week / this month, 'available only to merchants using the Kitchen Display System'. Shortfall: averages only (no percentiles), no daypart or order-channel slice, and no export or API stated. https://www.clover.com/en-US/help/track-kitchen-operations · retrieved 2026-09-03 adversarially verified

kitchen-prep-forecasting

2026-08-05 sweep with full help-centre text. The Kitchen operations report is retrospective (item volume, prep and fulfillment times, station-level activity — clover-reports-overview) and Insights produces backward-looking AI summaries and recommendations; no prep list or predicted prep quantities surfaced to kitchen staff is documented anywhere. Absence not closed by enumeration, so unknown stands.

delivery-driver-roster

Re-evidenced on the 2026-08-06 propagation audit. The prior basis - the Clover POS REST data model enumerating no driver object - covers the POS platform only and does not reach Clover Hospitality by BentoBox, which does support in-house delivery; that leg is withdrawn. Rebuilt on the Hospitality product's own documentation, which bounds what in-house delivery gets you: 'If you staff your own delivery drivers, you can set up your delivery zones and fees for each zone in Clover Hospitality by BentoBox' (Delivery Zones and Fees, articles/418497). The driver is never modelled anywhere downstream of that. The live delivery board publishes its complete order lifecycle - 'As you begin and complete orders, the order status will change automatically... All statuses are listed below: Not Started... Started... Done... Cancelled... Refunded', plus a non-notifying Overdue tag - with no assigned, on-run or returning state; the Clover Hospitality POS repeats the same closed set ('Each order moves through the following stages: Not Started, Started, Overdue, Ready', articles/7980545); and the Sales Report's enumerated metrics report in-house delivery tips as one store-level line with no per-driver dimension (articles/5661825). No driver entity, no assignment state and no per-driver run history exists on any Clover delivery surface. https://help.getbento.com/en/articles/419009 · retrieved 2026-08-06 adversarially verified

delivery-dispatch-board

Re-evidenced on the 2026-08-06 propagation audit; the prior POS-data-model argument is withdrawn because it does not cover Clover Hospitality by BentoBox, which runs in-house delivery. The Hospitality Pickup & Delivery screen IS the in-house delivery board, and its capability is documented exhaustively: 'On the Pickup & Delivery screen, you can perform three main actions with orders: View Order Details... Start Orders... Mark as Ready' (Starting Pickup & Delivery Orders). Its controls are separately listed in full - location filter, Adjust Current Prep Time, Adjust Delivery Time, Hide Started Orders - and time pressure is surfaced only as an Overdue tag plus 'a visual red banner at the top of the screen with the total number of orders that are ready to be prepped' and a beeping alert (Pickup & Delivery Page). There is no undispatched queue, no driver-availability view, no assign-to-driver action and no multi-order run batching; the same is true of the Clover Hospitality POS order screen, whose sorting is explicitly capped ('sorting options are currently limited to prepare time and newest first'). 'Dispatch' returns zero hits across the entire Clover Hospitality knowledge base and zero across the Clover help centre. https://help.getbento.com/en/articles/419393 · retrieved 2026-08-06 adversarially verified

delivery-route-map differentiator

Re-evidenced on the 2026-08-06 propagation audit, replacing a grade-F derivation off the withdrawn POS-data-model argument. Clover Hospitality by BentoBox does run in-house delivery, and its live board is documented in full: orders are 'displayed in chronological order based on fulfillment time', and the screen's controls are enumerated as a location filter, Adjust Current Prep Time, Adjust Delivery Time and Hide Started Orders. There is no map view, no geocoded stop plot and no sequencing of a multi-stop run - and no run exists to sequence, since the board offers only View Details / Start / Mark as Ready. Clover's map tooling is documented for one purpose only, drawing priced delivery areas: 'Polygon: Draw your own shape on the map with as many edges as you need... Circle... Radius', each carrying a Zone Name, Zone Fee and Zone Transit Time (articles/418497). A full-text search of the entire Clover Hospitality knowledge base returns zero hits for 'dispatch' and no route-optimization article of any kind. https://help.getbento.com/en/articles/419009 · retrieved 2026-08-06 adversarially verified

delivery-driver-tracking differentiator

Re-evidenced on the 2026-08-06 propagation audit, replacing a grade-F absence-of-mention rationale. On the in-house path there is no driver record to track at all - Clover Hospitality by BentoBox supplies zones and fees for merchants who 'staff your own delivery drivers', and its live board's statuses are enumerated with no assignment or on-run state. On the courier path Clover documents precisely what comes back, and it is not position: 'Clicking in an order's detail page shows further information like order status (i.e. Driver Unassigned, Driver Assigned), courier's name, ETA, and phone number' (Door-to-Door Delivery FAQ), and the order-detail article adds only that 'When a courier is assigned, their name and phone number will be displayed here' plus the DoorDash support line (articles/407297). The live map belongs to DoorDash and is shown to the diner, not the store - 'Customers receive notifications with their order details and a link to track the delivery' (clover.com/en-US/help/accept-delivery-orders-retail). Clover ships no driver-facing mobile app on any surface, and no GPS position is surfaced to a dispatch screen. https://help.getbento.com/en/articles/407361 · retrieved 2026-08-06 adversarially verified

delivery-zones-polygon differentiator

Overturned from no on the 2026-08-06 enumeration audit. Clover Hospitality by BentoBox online ordering defines delivery areas with a map tool offering three shape modes - 'Polygon: Draw your own shape on the map with as many edges as you need', 'Circle: Draw a circle on the map to set your delivery area', and 'Radius: The map tool will draw a circle around your restaurant's location, just enter your radius in miles here' - configured at Online Ordering > Locations > edit location. Each zone carries a Zone Name, a Zone Fee ('a flat dollar amount or percentage fee (calculated from order's subtotal)') and Zone Transit Times, which 'will account into the total delivery time when placing an order'. Shortfall - arbitrary polygons exist only for in-house delivery inside the Clover Hospitality (BentoBox) ordering product; 'If you are accepting delivery orders with Door-to-Door Delivery fulfillment through our partnership with DoorDash Drive, your zones and fees will be predetermined', and the Clover POS's own online ordering exposes no merchant-configurable delivery area whatsoever (DoorDash's ~3-mile urban / 5-mile rural range). No drive-time isochrone option is documented in either product. https://help.getbento.com/en/articles/418497 · retrieved 2026-08-06 adversarially verified

delivery-zone-pricing

Overturned from no on the 2026-08-06 propagation audit; the prior no rested on the blog description of Clover's DoorDash-couriered delivery (flat '$6.99 delivery fee per order' plus one 'minimum amount for delivery orders'), which is not the only delivery product Clover ships. In Clover Hospitality by BentoBox each drawn zone is independently priced and timed: 'Zone Name: Here you can choose to name your delivery zones', 'Zone Fee: Choose a flat dollar amount or percentage fee (calculated from order's subtotal)', and 'Zone Transit Times: This will account into the total delivery time when placing an order' (total quote = Prep Time + Zone Transit Time + live order adjustments). Fees resolve automatically from the address entered at checkout. Shortfall - two of the three levers the claim asks for: no per-zone order minimum is documented anywhere in the Delivery Zones and Fees article, and the zone construct exists only inside the Clover Hospitality (BentoBox) ordering product for in-house delivery. On DoorDash Drive fulfilment 'your zones and fees will be predetermined', and the Clover POS's own online ordering exposes no merchant-configurable zone at all. https://help.getbento.com/en/articles/418497 · retrieved 2026-08-06

delivery-address-validation

Serviceability is checked at order time for first-party delivery: 'DoorDash checks if the delivery address is within the accepted range (~3 miles urban / 5 miles rural). If the delivery can be made, DoorDash accepts the order and a receipt prints from your Clover POS' — out-of-range orders are not accepted. Shortfall — the check is DoorDash's fixed range, not merchant-configured zones; no address geocoding/validation is documented for non-delivery order types, and address changes require contacting DoorDash support (doordash-delivery-retail-faqs). https://www.clover.com/en-US/help/accept-delivery-orders-retail · retrieved 2026-08-05

delivery-driver-comp differentiator

Re-evidenced on the 2026-08-06 propagation audit, replacing a grade-F derivation off the withdrawn POS-data-model argument. Clover Hospitality by BentoBox does run in-house delivery, and its reporting definitions are published in full - Summary, Fees, Orders by Type, Gift Cards, Top Menu Items - with exactly one delivery-compensation metric: 'Delivery Tips v/s DoorDash Delivery Tips: We have broken out in-house delivery tips v/s DoorDash Delivery Tips'. That is a store-level split, not a per-driver figure, and no metric for distance, run count or reimbursement is defined anywhere in the enumeration. There is nothing upstream to compute one from either: the delivery board never assigns an order to a person and never records a departure or return, so no mileage or per-delivery reimbursement is captured, and no payroll export separating reimbursement from wage lines exists. Full-text search of the whole Clover Hospitality knowledge base returns zero hits for 'mileage' and zero for 'reimbursement'. https://help.getbento.com/en/articles/5661825 · retrieved 2026-08-06 adversarially verified

delivery-cash-reconcile

Re-evidenced on the 2026-08-06 propagation audit, replacing a grade-F derivation off the withdrawn POS-data-model argument. Clover Hospitality by BentoBox does ship an end-of-shift settlement, and it enumerates its own scope: 'What Closeout Supports: Employee Closeout: Individual shift reconciliation for employees, bartenders, etc. Restaurant Closeout: End-of-day financial summary and credit card batch out. Cash Tip Declaration... Credit Card Batch Out'. The employee flow is close all checks, enter card tips, then 'Declare Cash Tips... This value is self-reported', ending in 'a summary of your shift, including sales, tips, payments' - there is no counted cash bank, no drop, and no over/short figure, and the only stated blocker is an open check. It is also a server settlement, not a driver settlement: delivery orders live on the separate Pickup & Delivery board, are never assigned to an employee, and carry no per-person cash-collected total. No per-driver over/short exists on any Clover surface. https://help.getbento.com/en/articles/7980737 · retrieved 2026-08-06 adversarially verified

delivery-daas-dispatch

Native DaaS handoff is documented in first-party help (Clover Hospitality by BentoBox, Fiserv-owned): Door-to-Door Delivery via DoorDash Drive is toggled on from the Online Ordering page of the Clover Dashboard, Clover "simply passes on a $6.99 per-order fee from DoorDash Drive; we do not take a cut of this order fee", and a Dasher marking the order "Out for Delivery" can "simultaneously update the Online Ordering order status to 'Done'". Shortfall — the claim requires the courier QUOTE as well as status to return into the order record, and no quote, fee estimate or ETA is returned; the $6.99 is a flat pass-through. A paid monthly Online Ordering subscription is a prerequisite. https://help.getbento.com/en/articles/407425 · retrieved 2026-08-02 adversarially verified

delivery-daas-fallback differentiator

Re-evidenced on the 2026-08-06 propagation audit; the prior rationale ('no in-house driver pool exists to overflow from') is wrong, because Clover Hospitality by BentoBox does offer In-House delivery with merchant-drawn zones. Hybrid overflow is nevertheless ruled out by a stated limitation in the same product's Door-to-Door Delivery documentation: 'You must choose either In-House or DoorDash Drive delivery for any given location at one time. You cannot do a combination of both at the same time.' Fulfilment is a per-location setting toggled on the locations page ('Fulfillment Method' > 'Delivery' > 'DoorDash'), not a per-order routing decision, so there are no rules that push an order to a courier when no driver is free, the address is out of zone, or a wait threshold is passed. On the Clover POS's own online ordering the question does not arise at all - delivery there is DoorDash Drive only, with no in-house driver, dispatch or assignment object in the documented data model. https://help.getbento.com/en/articles/407425 · retrieved 2026-08-06

delivery-3p-direct-integration differentiator

Clover's own status page lists "Uber Eats" as a monitored North America component alongside Online Ordering and Ecommerce, evidencing a Clover-operated first-party Uber Eats integration. Shortfall — no equivalent component, and no documentation at all, for DoorDash or Grubhub; and the status page establishes only that the service exists, not what it does. https://status.clover.com/ · retrieved 2026-08-02

delivery-3p-injection

Third-party orders can be injected: "The Clover APIs allow you to create two types of orders", and orders created through the Orders or Atomic Orders REST API "appear in the Orders and Register apps". Shortfall — those orders "are not compatible with Clover Dining, which uses a private data schema for features such as table mapping and guest seating", so an injected order cannot carry table or seat context on a table-service site. https://docs.clover.com/dev/docs/orders-faqs · retrieved 2026-08-02

delivery-menu-push

The POS master inventory publishes outward with per-channel control: 'Multiple menus allows you to create and manage separate menus for each online ordering partner, including Clover Online Ordering, BentoBox, Uber Eats, Grubhub, Order with Google, and Doordash. Each menu can display different categories, items, and prices.' DoorDash menus are created, pre-validated, previewed and published from the Clover dashboard; Uber Eats uses the Clover menu with hourly refreshes covering 'Menu Sections, Item Descriptions, Item Modifiers, Item and modifier prices', and item images sync ('you can add images to items in your inventory. Changes are updated to your Uber Eats menu' — uber-eats-faq). No separate portal-side menu maintenance is required. https://www.clover.com/en-US/help/work-with-multiple-menus · retrieved 2026-08-05

delivery-86-sync

Item-level 86 sync is documented and fast for Uber Eats: 'Out-of-stock updates are immediate'; 'During each menu refresh, Uber Eats manages item availability. These items are set as available or suspended accordingly. Uber Eats then gets notified and takes action in real time' — both directions (suspend and restore), driven from the POS availability toggle or automatic zero-stock 86 (automatically-manage-item-availability). Shortfall — modifier/item-option-level 86 is not documented for any channel, and no equivalent 86-sync statement exists for the DoorDash marketplace integration. https://www.clover.com/en-US/help/uber-eats-faq · retrieved 2026-08-05

delivery-store-pause

Per-channel pause with timed auto-reactivation from inside Clover: for DoorDash, 'Use the Accept or pause orders toggle... When you pause online orders, orders remain paused until you turn the option back on or set a time limit... When you select a time interval, the resume time appears. Orders will automatically resume at the time indicated' (Settings > Online ordering > DoorDash > Manage); first-party online ordering pauses the same way ('ordering automatically resumes when time is up'), and each partner has its own toggle on the Manage panel — no marketplace tablet or portal required. https://www.clover.com/en-US/help/manage-doordash-orders · retrieved 2026-08-05

delivery-3p-reconciliation differentiator

Fee reconciliation artifacts exist for first-party DoorDash Drive delivery: a monthly emailed invoice with a CSV of 'delivery level detail with the store name and address identified for each delivery', refunds appearing 'in your monthly invoice as an adjustment' per a published refund matrix, and dasher tips owed surfaced in the POS ('Go to the Sales overview report, select Tips, and review the amount for DoorDash dasher tips'). Shortfall — this is the DaaS fee side only: no report matches marketplace payout deposits to POS-recorded 3P sales, itemizes marketplace commission/marketing fees, or identifies missing/unpaid orders. https://www.clover.com/en-US/help/doordash-delivery-retail-faqs · retrieved 2026-08-05

delivery-injection-error-visibility differentiator

Integration status is exposed at the channel level: DoorDash onboarding surfaces menu-validation errors with retry ('retry menu sync', 3 attempts, then 'an error message stating that the integration failed'), activation states are visible in the dashboard ('Pending', 'Retry Activation', activation confirmation message under Settings > Online ordering), and each channel's accept/pause state shows on the Manage panel. Shortfall — no per-order injection-failure alerting is documented; whether a failed inbound marketplace order is surfaced to the operator, or fails silently, is not addressed. https://www.clover.com/en-US/help/doordash-frequent-questions · retrieved 2026-08-05

delivery-tracking-page

For first-party delivery orders 'Customers receive notifications with their order details and a link to track the delivery', and for online-shopping orders 'Customers receive a confirmation email, along with an email when their order is ready and after their order has been picked up... All communications are sent through DoorDash' (setup-online-shopping). Shortfall — the tracking experience is DoorDash's, not a branded page on the restaurant's own domain, and driver state display is not described. https://www.clover.com/en-US/help/accept-delivery-orders-retail · retrieved 2026-08-05

delivery-promise-time differentiator

Overturned in part from no on the 2026-08-06 enumeration audit. The quote is not a fixed per-store constant across Clover's products. In Clover Hospitality by BentoBox the promise is Prep Time plus a per-zone drive allowance - 'Zone Transit Times: This will account into the total delivery time when placing an order' (Delivery Zones and Fees) - and it extends automatically with order volume: Order Pacing caps orders per 15-minute slot and, once a slot is full, quotes the diner the next available increment (Prep Time plus the pacing threshold). Shortfall - every input is a configured constant rather than live state. Autopilot's documentation lists among the things it does not do 'Adjust automatically when you are running behind for current orders', and notes that 'these triggers operate off Prep Time, so it is up to FOH staff and the kitchen to make sure Prep Time reflects current pacing'. Driver availability is never an input on either path, and the Clover POS's own online ordering still quotes a single static per-store Food preparation time that 'directly affects the pickup times and delivery estimates shown to customers'. https://help.getbento.com/en/articles/419841 · retrieved 2026-08-06 adversarially verified

delivery-offline-behavior

Downgraded from no on the enumeration audit of 2026-08-06. The claim asks whether the vendor documents explicit offline behaviour for delivery - cash delivery orders, driver assignment, driver settlement. The cited page is 'Use your KDS offline with Clover Local Connect', which is about Clover devices displaying orders to each other over a local network and never mentions delivery; it does state its own limit ('You still need the internet to do things like process credit card payments and save your sales information online'), but that is a statement about payments, not about a delivery workflow. The remaining basis is a help-centre full-text search that returned nothing, which is absence of evidence. I re-searched the help centre and the Clover Hospitality (BentoBox) help estate on 2026-08-06 and likewise found no offline delivery documentation - but a null search cannot support a positive assertion about a named business. Assessed and unresolved. adversarially verified

digital-first-party-web

A first-party ordering site on the restaurant's own domain is documented: Clover Hospitality by BentoBox publishes eight go-live articles covering domain purchase, hosting and launching on GoDaddy, Dreamhost and Network Solutions, instructing operators to "point your domain to Clover Hospitality by BentoBox" after QA. Shortfall — the claim also requires commission-free, and that language exists only on getbento.com/products/online-ordering, which now 308-redirects to clover.com/pos-systems/online-ordering, a client-rendered page returning no body. Online ordering is also a separate "monthly Online Ordering subscription", so this is not a base-tier inclusion. https://help.getbento.com/en/categories/129729 · retrieved 2026-08-02 adversarially verified

digital-menu-single-source

Inventory is a single merchant-scoped catalogue — "Inventory can be associated with a single merchant" — which the Register, Ecommerce and Online Ordering surfaces all read. Shortfall — the catalogue is not genuinely single-source across the product: Clover Dining "uses a private data schema" that REST API orders cannot reach, and channel-specific price books are not documented. https://docs.clover.com/dev/docs/clover-data-model · retrieved 2026-08-02

digital-native-app differentiator

Downgraded from no on adversarial re-read 2026-08-02. The nearest evidence located is that Clover publishes a consumer "Clover app" in the iOS and Android stores listing Clover merchants for discovery and ordering — which is precisely the shared multi-restaurant marketplace app this claim excludes, so it does not establish a restaurant-branded app, but neither does it affirmatively state that no branded-app product exists. The Clover Hospitality go-live documentation covers websites and domains only and never mentions app-store submission. No first-party document denies the capability. adversarially verified

digital-account-saved-payment

The first-party Clover consumer app (seller: Clover Network, Inc.) documents guest accounts with tokenized cards and order history: “Securely save your preferred credit cards for faster payments, or use Google Pay and Apple Pay”, “Easily view past orders and check upcoming bookings”, plus loyalty (“Track your points and find ways to instantly redeem them”), and Clover’s blog confirms app and web guests land in the merchant Customers tool. Shortfall — one-tap reorder of a previous order is not stated anywhere retrievable, and whether accounts with saved cards work on the merchant-branded ordering web page (as opposed to the Clover app) is undocumented; the help centre is client-rendered. https://apps.apple.com/us/app/clover/id428620381 · retrieved 2026-08-03

digital-upsell-engine differentiator

2026-08-05 sweep with full help-centre text (online ordering setup steps 1-4, menu preparation, kiosk setup, Register). No rules-based or algorithmic add-on suggestion at digital checkout is documented, and no attach-rate reporting exists in the enumerated report suite. Absence not closed by enumeration of checkout behaviour, so unknown stands.

digital-scheduled-pacing

Scheduled/future orders are native: customers can order up to a configurable window ('Select your ordering window, such as 3 calendar days'), with kitchen-timing control over when the ticket fires ('Immediately when order is placed' / '25 minutes before pickup time' / 'After an additional buffer time plus 25 minutes... Enter the amount of extra time to add to your prep window, such as +10 minutes') and email notification per scheduled order. Shortfall — no per-daypart capacity limits: nothing caps orders or items per time slot or closes saturated slots automatically; the buffer is a static manual entry and overload handling is the manual pause toggle. https://www.clover.com/en-US/help/route-order-tickets-to-kds · retrieved 2026-08-05

digital-fulfillment-modes

Pickup and courier delivery are supported; curbside arrival check-in and mode-specific prep timing not documented.

digital-qr-table

Clover offers QR scan-to-order; whether it attaches to an existing open POS check rather than creating a new order is not documented.

digital-kiosk differentiator

Clover Kiosk is first-party and shares the POS menu; accessibility compliance documentation not found.

digital-group-ordering

On the Clover Hospitality (BentoBox) online ordering surface, Group Ordering is a documented merchant toggle (Online Ordering > Settings > Locations > Group Ordering) with a configurable maximum number of people per group order and custom or preset ($15/$20/$25) spending limits shown to diners; 'Once the diner completes a group order, the consolidated order is pulled into the backend as a standard online order.' Shortfall — the help article documents neither a shareable participant link nor split payment: checkout is a single consolidated order, and 'Group Orders are charged a 3% service fee'. Nothing documents group ordering for core Clover Online Ordering outside the Hospitality line. https://help.getbento.com/en/articles/418753 · retrieved 2026-08-04

digital-catering-portal differentiator

2026-08-05 sweep with full help-centre text. No catering ordering flow, catering menu/minimums, lead-time rules or deposit workflow exists in the help centre; adjacent documented pieces are scheduled orders, multiple menus, Estimates (quote-to-invoice) and invoicing with ACH via Pay by Bank — none assembled into a catering portal. Absence not closed by enumeration, so unknown stands.

digital-voice-ai-phone differentiator

2026-08-05 sweep with full help-centre text (searched voice, phone ordering, AI answering, call). No first-party or named certified AI phone-ordering product appears anywhere in the help centre; Clover's documented AI investments are Insights/'Ask me' analytics, the Vera support chatbot, and AI menu generation from an uploaded menu — none touch inbound calls. Unknown stands.

digital-drivethru-ai

Downgraded from no on the enumeration audit of 2026-08-06. This cell was derived from order-capture-drive-thru, which is itself downgraded in this pass: the cited fulfillment-method list covers online ordering only, and the 'complete device catalogue' premise is false - the tech-specs page asserts no completeness and its sections cover Station, Mini, Flex, Compact and Go, omitting the Kiosk and KDS the note credits to it. What remains is a help-centre full-text search for voice ordering that returned nothing, plus my own re-check of Clover's July 2026 restaurant platform announcement, which lists no voice AI. Both are null results. Assessed and unresolved. adversarially verified

digital-sms-ordering

2026-08-05 sweep with full help-centre text. Documented SMS is one-way or transactional: Promos announcements via a vetted toll-free number, order-ready texts, digital gift cards and receipts by SMS, and texting a 3-word rewards code to 73752 for points. No conversational text-to-order or text-a-link ordering flow that lands in the POS is documented. Unknown stands.

digital-google-order differentiator

Clover Hospitality help documents exactly the claim: owners 'add a direct ordering link for your business (i.e. www.your-restaurant.com/online-ordering) by going to Info > Order ahead links', and can 'mark your direct link as preferred, so diners see a note that says "Preferred by this business" when they click your "Order" link on Google Search or "Place an Order" on Google Maps', with orders syncing back at no additional cost. Core Clover's own blog separately claims Order with Google through the Online Ordering Hub (ORDER PICKUP / ORDER DELIVERY buttons, delivery via DoorDash at a flat $6.99 per order), but the matching first-party help page clover.com/en-US/help/order-with-google renders empty to a non-JS fetch, so the grade-B evidence is the Hospitality help centre. https://help.getbento.com/en/articles/407745 · retrieved 2026-08-04

digital-apple-business-connect

2026-08-03 sweep. Searched the web and Clover’s retrievable first-party surfaces for Apple Business Connect, Apple Maps place-card ordering, or an ‘Order Food’ action pointing at Clover ordering; nothing first-party (docs.clover.com, blog.clover.com) or credibly third-party mentions it. Clover’s own ordering-channel material names Order with Google as the maps channel and is silent on Apple Maps. Unresolved rather than absent because clover.com help and marketing pages are client-rendered (return only the title ‘Clover Help’ to a non-JS fetch), so a help-centre-only mention cannot be ruled out.

digital-loyalty-attach

Clover's rewards/customer engagement products share the Clover customer record; parity of accrual and redemption inside the online ordering flow is not documented.

digital-subscriptions

Recurring billing is platform-native: plans “define billing cycles and amounts for recurring payments”, subscriptions “associate customers with specific plans, including billing details, start dates, and intervals”, with card-on-file charging and automatically generated invoices (excluded for HIPAA merchants). Shortfall — billing only, no entitlement management: nothing in the platform manages a delivery-fee waiver, per-period item credits or a paid loyalty tier, and Clover’s own guidance on restaurant meal subscriptions sends merchants to a third-party App Market app — “The ChewCrew app on the Clover App Market will allow you to easily redeem customer item credits” (blog.clover.com/the-future-of-restaurant-loyalty-restaurant-meal-subscriptions/, read 2026-08-03). https://docs.clover.com/dev/docs/recurring-payments-and-subscriptions-apis · retrieved 2026-08-03

digital-promo-parity

2026-08-05 sweep with full help-centre text. Rewards redemption is documented at the Register/Sale app and in the Clover consumer app, and promos print codes on receipts; but whether a discount or offer defined once is honoured identically on kiosk and the first-party ordering site — or gated per channel — is documented nowhere; Uber Eats loyalty explicitly requires separate setup ('This promotion will need to be set up in Uber Eats'). Unknown stands.

digital-guest-data-ownership differentiator

Bulk export is documented on two surfaces: the REST endpoint 'Get a list of customers in CSV format' ('information for every customer of a merchant by default') and the dashboard's Customers > Options > Download ('All the information you entered about a customer is exported' to CSV), self-service with no fee or approval step. Shortfall: no published statement that the operator owns the guest records or limiting Clover's own use; the Merchant Terms are not publicly retrievable. https://docs.clover.com/dev/reference/handlersgetcustomerscsv · retrieved 2026-09-03 adversarially verified

digital-checkout-pci-sca

Clover documents PCI DSS v4.0 requirements 6.4.3 and 11.6.1 as "mandated from April 1, 2025" and returns a tokenized card from its hosted iframe, reducing merchant scope. Shortfall — no SCA/3-D Secure behaviour is documented, and "Merchants using their own domains or payment plugins are responsible for their own PCI compliance", so the hosted protection does not extend to every checkout shape. https://docs.clover.com/dev/docs/pci-dss-version-40-requirements-643-and-1161 · retrieved 2026-08-02

digital-surcharge-transparency differentiator

Digital surcharging with guest-facing disclosure is documented for Clover ecommerce checkout: “If the merchant is configured for surcharges on a specific Clover account, the customers can view an image on the e-commerce website” and “a note on the Payment by card (Clover) section indicates that a surcharge may be applicable on credit card transactions”. Prohibited-jurisdiction handling sits at onboarding — surcharging is only enabled in “Canada, excluding Quebec [and] United States, excluding states with legal restrictions or prohibitions”, and only on credit BINs (docs.clover.com/dev/docs/transaction-data, read 2026-08-03). Shortfall — documented for ecommerce plugin checkout only; parity on Clover Online Ordering (the first-party restaurant ordering page) is undocumented, and dual pricing / service-fee configuration online is not covered anywhere retrievable. https://docs.clover.com/dev/docs/viewing-surcharges · retrieved 2026-08-03

guest-loyalty-unified-profile

Customers are a first-class top-level object: "A customer can be associated with a single merchant" and "zero or more orders", so purchase history attaches to a guest record. Shortfall — the profile is bound to one merchantId, so it does not unify across locations, and no loyalty, points or tier object appears anywhere in the documented data model. https://docs.clover.com/dev/docs/clover-data-model · retrieved 2026-08-02

guest-loyalty-thirdparty-identity-attach differentiator

Checked 2026-08-04: docs.clover.com Orders FAQs document only manual customer attachment through the API ('Clover does not support creating and assigning a customer to an order in a single atomic request' — create customer, create order, then update the order with the customer id) and say nothing about marketplace orders; marketplace ingestion on Clover runs through third-party apps (e.g. OrderOut) whose materials document order injection and menu sync, not guest-identity mapping; help.getbento.com delivery articles cover first-party orders fulfilled by DoorDash Drive, not marketplace order identity. The merchant help centre (clover.com/help) is client-side rendered and returns only its title to a non-JS fetch, so a help-centre-only answer would be invisible to this pass. Unresolved.

guest-loyalty-accrual-models

Clover's rewards product supports points and visit-based rewards; tier-spend accrual not confirmed.

guest-loyalty-tiers differentiator

Visit-count status tiers with automatic promotion exist: 'A loyalty rewards member reaches Regular status after a set number of visits that you can customize' and a VIP tier above it ('VIP Bonus: Use this to help your best customers earn points faster'); defaults are visible in customer filters — 'Regulars: Customers that visited 12 (default) or more times... VIPs. Customers that visited more than 25 (default) times. You can change this number in the Rewards app' (search-for-a-customer-using-filters), and promotion 'is automatic' (become-a-vip-with-the-clover-app). Shortfall — tiers are lifetime visit counts only: no rolling-window measurement, no spend-based tiers, and no demotion is documented. Requires the bonus-plus rewards subscription. https://www.clover.com/en-US/help/create-custom-bonus-plus-rewards-new · retrieved 2026-08-05

guest-loyalty-offline-behavior differentiator

Downgraded from no on the enumeration audit of 2026-08-06. The cited page is 'Use your KDS offline with Clover Local Connect', which describes Clover devices exchanging orders over a local network and never mentions loyalty, rewards, accrual or redemption; it enumerates nothing and asserts no completeness. The remainder of the argument is that the Rewards documentation suite never addresses connectivity loss - a suite of help articles that nowhere claims to be complete, which is a null search rather than an enumeration. I re-read the Rewards articles on 2026-08-06 and confirmed they are silent on offline behaviour, which leaves the question genuinely open rather than answered. Assessed and unresolved. adversarially verified

guest-loyalty-offer-stacking-rules differentiator

2026-08-05 sweep with full help-centre text (searched stacking, combine discounts, exclusive, precedence). The Rewards and Promos documentation shows single-offer redemption flows ('tapping redeem will automatically discount the total') and manual discounts, but exposes no stacking or precedence configuration and none is denied. Unknown stands.

guest-loyalty-targeted-offers differentiator

Offers can target behaviour-defined audiences, not just the whole list: Regulars Bonus 'to target your Regular customers' (threshold customizable), VIP Bonus for the highest-frequency customers, Welcome Bonus 'only be visible for customers who have not yet checked in', Birthday Bonus with a 30-day redemption window; the customer list filters by the same audiences (Members / Regulars / VIPs). Shortfall — audiences are preset frequency segments only: no rule builder over recency, spend or items purchased is documented. Requires the bonus-plus rewards subscription. https://www.clover.com/en-US/help/create-custom-bonus-plus-rewards-new · retrieved 2026-08-05

guest-loyalty-rfm-segmentation differentiator

Frequency-based lifecycle segments are computed automatically: the Customers list ships preset filters — 'Regulars: Customers that visited 12 (default) or more times' and 'VIPs. Customers that visited more than 25 (default) times', thresholds adjustable in the Rewards app, plus Members and Audience — with no operator-built queries. Shortfall — segmentation is frequency-only: no recency or monetary dimension and no at-risk/lapsed segment is documented. https://www.clover.com/en-US/help/search-for-a-customer-using-filters · retrieved 2026-08-05

guest-loyalty-lifecycle-automation

Always-on triggered bonuses exist: Welcome Bonus (first-visit enrollment reward, shown only to customers who have not yet checked in) and Birthday Bonus ('rewards your customers on their birthday. After receiving it, they have 30 days to redeem') are configured once on the Rewards Program tab and run continuously; Promos adds 'Automatic offers' cancellable by toggle (stop-or-cancel-real-time-promotions). Shortfall — no lapsed-customer win-back automation is documented, and the bonus set is fixed (welcome/regulars/VIP/birthday) rather than a configurable trigger library. Requires the bonus-plus rewards subscription. https://www.clover.com/en-US/help/create-custom-bonus-plus-rewards-new · retrieved 2026-08-05

guest-loyalty-native-email-sms differentiator

Clover's promotions product sends email and text offers natively; channel depth not documented.

guest-loyalty-consent-management

Consent is captured, but as a single flag: the Customer Engagement import schema carries one “Is Marketing Allowed?” field per customer, and Clover gates imports on consent — “we’ll ask you for written confirmation that your customers have previously opted in to communications from you”, with the import process confirming “customers being imported have opted in to receive communications from the merchant and that Clover has permission to work with customer data”. Shortfall — no per-channel consent granularity, no timestamp or source-of-consent field appears in the documented schema, and revocation handling across channels (beyond unsubscribe norms) is documented nowhere retrievable; the Promos/Rewards help pages are client-rendered. https://assets.ctfassets.net/3mu3dzx76r6a/a9PJx69PH2iYYW1ngmhWE/c2378e298340a24f7dc4064ed8753037/Customer-engagement-import-whitepaper.pdf · retrieved 2026-08-03

guest-loyalty-10dlc-registration

Clover handles merchant SMS sender registration, via toll-free verification rather than 10DLC: merchants apply in-dashboard ('Apply for a toll-free phone number' under Promos or Customer communication preferences), Clover runs a documented vetting process — 'your information is reviewed and processed. This can take up to 7 business days... we also review your business websites and social media pages, as well as your opt-in policy' — against CTIA content rules, and approved merchants send promos and transactional SMS from their unique toll-free number ('carriers... are requiring the use of toll-free numbers, instead of short codes, for marketing communications' — request-a-toll-free-number). Shortfall — A2P 10DLC brand/campaign registration specifically is neither performed nor documented; the platform route is toll-free only. https://www.clover.com/en-US/help/toll-free-number-process-transactional-sms · retrieved 2026-08-05

guest-loyalty-campaign-attribution differentiator

Promotion redemption reporting exists; tying redemptions to incremental check totals is not documented.

guest-loyalty-data-export-portability differentiator

Customer records are readable and writable through the REST API under merchant-granted "Read customers" and "Write customers" permissions, so a merchant can authorise an app to extract its guest list. Shortfall — no bulk export format, no documented export of loyalty balances or consent state, and no post-termination access window. https://docs.clover.com/dev/docs/permissions · retrieved 2026-08-02

guest-loyalty-review-capture-routing differentiator

Clover Feedback captures private post-transaction feedback; score-based routing to public review sites not documented.

guest-loyalty-referral-program

Clover's own guidance on referral discounts recommends workarounds rather than a native mechanic: 'a customer referral reward app such as BuyFi' that 'makes it easy to track and reward those who spread the word', plus manually using 'a code to "tag" new customers who come through a referral'. Corroborating absence: Clover UserVoice idea 50730461 (restaurant forum, Nov 2025) requesting per-guest referral codes with automatic tracking sits at 'Submitted' with only a boilerplate acknowledgement, and Clover's Dec 2024 UK apps catalogue places referral incentives under the third-party Trezoro Loyalty app. Per-guest referral codes with first-order attribution and two-sided rewards are not a native Clover capability. https://blog.clover.com/crowd-pleasers-how-why-to-offer-a-referral-discount/ · retrieved 2026-08-04

guest-loyalty-wallet-pass differentiator

Positive absence by enumeration of the documented earn/redeem channels: points are collected via printed receipt codes ('Locate the 3-word code at the bottom of your receipt. Text the code to 73752'), the Clover consumer app (check-in, including beacon-based hands-free check-in), or Register check-in; redemption is by app check-in or 'a redeemable QR code that they received through a text message or email' (redeem-points). No Apple Wallet or Google Wallet pass exists anywhere in the Rewards documentation — the consumer-app download is exactly the alternative this claim excludes. https://www.clover.com/en-US/help/collect-points-and-redeem-offers · retrieved 2026-08-05

guest-loyalty-privacy-rights-tooling

In-app tooling for access and deletion is documented: 'your Clover device and dashboard provide a number of tools to help you fulfill the request... open the Customers app... From a customer's profile you can: Access the customer's data; Edit the data...; Delete the customer's profile; Gather such information... with a tool that makes the data portable', plus receipt-level privacy-policy linking and a parallel CCPA guide (calif-consumer-privacy-act). Shortfall — deletion propagation to loyalty and marketing records is not documented (whether deleting a profile clears rewards balances and Promos audience membership is unstated), and there is no request-tracking workflow. https://www.clover.com/en-US/help/clover-supports-the-general-data-protection-regulation · retrieved 2026-08-05

guest-loyalty-redemption-fraud-controls

Clover’s own loyalty-fraud guidance is a manual workaround, which is the tell: merchants are told to “establish a benchmark for how many program participants you have and how often they make purchases”, watch their weekly “run rate”, “stay attuned to your loyalty program’s daily stats”, and watch for “employees who are overly generous awarding points or punches”. No redemption velocity limit, manager-approval gate on point adjustments, employee self-redemption flag or audit log is named there or anywhere else in Clover’s retrievable Rewards material — advice this labour-intensive would be redundant if platform controls existed. https://blog.clover.com/how-to-reduce-loyalty-program-fraud/ · retrieved 2026-08-03

guest-loyalty-ai-offer-recommendation differentiator

2026-08-05 sweep with full help-centre text. Clover's shipped AI features are documented — Insights ('AI-generated insights, and personalized recommendations', e.g. 'improving order size or expanding to online ordering') and the 'Ask me' assistant — but the recommendations are merchant growth actions, not offer content, target audiences or send timing for guest offers. No AI offer-recommendation feature is documented; absence not closed. Unknown stands.

guest-loyalty-stored-value-gift

SHORTFALL — no documented link between a stored-value balance and a guest profile, and no documented cross-location redemption. Native stored value exists and reloads without expiry ("Does not have an expiry date and can be reloaded with a specified amount"), but cards are identified by card number plus a 4-8 digit security card value or a virtual promo code, not by a customer record; Customers is a separate permission category and does not appear in the Gift Card API flow. Region-pilled United States and Canada, and gated behind signing up for "Clover Gift Cards plans". https://docs.clover.com/dev/docs/gift-card-api · retrieved 2026-08-02 adversarially verified

labor-clock-in-at-pos

SHORTFALL — the on-device clock-in flow is undocumented and the catalogued time clock is a paid add-on. The Shifts API models it at the employee: POST /v3/merchants/{mId}/employees/{empId}/shifts with inTime "Clock in time", outTime "Clock out time", overrideInTime/overrideOutTime, cashTipsCollected and serverBanking. Identification at the terminal is documented — Station Duo 2 "Employee login method: Employee passcode", Station Solo (international) "MSR reader for merchant and employee login". But no Clover document describes clocking in on the device, and Clover's own UK apps guide catalogues the first-party Employees app only as "tools for tracking employee hours, managing shifts", while the dedicated time clock is "Time Clock by Homebase", "Essentials: £9.95/month", "Devices/Platform: Web". https://docs.clover.com/dev/reference/employeecreateshift · retrieved 2026-08-02 adversarially verified

labor-photo-punch-verification differentiator

Available only through the add-on Time Clock by Homebase app, which Clover distributes and documents for its own devices ('Once you've launched the Time Clock app on your Clover device, your team members are synced and employees can start'; 'The Time Clock app prevents this practice [buddy punching] by taking a photo of your employee and alerting you if someone else is' clocking in for them). Shortfall: the native Shifts clock-in flow (open Shifts, tap the clock icon, optional 'I'm holding my cash sales during this shift' checkbox, Clock In) captures no photo, so this requires the third-party app; and no photo-only mode versus biometric-template mode is distinguished in any Clover or Homebase documentation retrieved. Evidence is a vendor blog post, not configuration documentation. https://blog.clover.com/reasons-clover-merchants-use-time-clock-by-homebase · retrieved 2026-08-06

labor-offline-time-punch differentiator

2026-08-05 sweep with full help-centre text. The Shifts app clock-in is documented as 'based on the time set on your Clover device', suggesting local operation, and the reboot article notes 'Clover saves all settings and data, including any offline payments' — but no document states whether punches recorded while offline sync losslessly on reconnect, and the offline documentation's enumerated scope (payments, Local Connect/KDS) omits the time clock. Unknown stands.

labor-granular-rbac

Role information is retrievable — GET /v3/merchants/{mId}/employees/{employeeId}?expand=roles — and app data access is gated per category by Read/Write permissions over customers, employees, inventory, merchant, orders and payments. Shortfall — the enumerated role catalogue Clover documents (Owner, Admin, Business, Technical, plus custom roles) is for the *developer* dashboard, not for merchant staff; no store-level permission matrix is published. https://docs.clover.com/dev/docs/permissions · retrieved 2026-08-02

labor-manager-override-audit

Time-punch overrides are audited at the object level: the shift carries overrideInTime, overrideOutTime, overrideInEmployee and overrideOutEmployee, so an edited punch records who edited it. Shortfall — this covers time punches only; no equivalent documented audit object for void, comp, discount or price-override approvals. https://docs.clover.com/dev/reference/employeecreateshift · retrieved 2026-08-02

labor-native-scheduling differentiator

'Scheduling by Homebase is a scheduling tool available in the Clover dashboard' (Employees > Scheduling): create and assign shifts, publish with notifications, availability, time off, conflict detection, estimated labour cost, duplication. Timekeeping is the Shifts app or Time Clock by Homebase on the device. Shortfalls: Homebase-powered rather than Clover-built; 'subscribed to the Essentials plan or above'; 'available only through the Clover dashboard' (not on a device); 'Scheduling is limited to single-location merchants at this time'. https://www.clover.com/en-US/help/scheduling-by-homebase-faqs · retrieved 2026-09-03 adversarially verified

labor-demand-labor-forecast differentiator

2026-08-05 sweep with full help-centre text. Scheduling is delivered by the embedded 'Scheduling by Homebase' (Essentials plan+): its documented capabilities are schedule creation/publication, availability, time off, labor-cost monitoring and conflict detection — no sales-history-driven staffing recommendation is mentioned, and native Clover reporting has no forecast. Whether the fuller Homebase product adds demand forecasting on Clover is not documented on any Clover surface. Unknown stands.

labor-realtime-labor-percent differentiator

2026-08-05 sweep with full help-centre text. The inputs exist natively (Wages assigns pay rates to employee jobs, Essentials+; Shifts records clocked hours) and 'Homebase can use wage rates and employee hours worked to support labor-cost calculations' (setup-wages-with-clover) — but no document shows labor cost as a percentage of sales displayed in real time during service on any manager view; the enumerated report suite has no labor-percent report at all. Unknown stands.

labor-overtime-prevention differentiator

Approaching-overtime alerting exists on Clover devices through the add-on Time Clock by Homebase app: 'When an employee is about to reach overtime, you'll receive an alert for that as well, helping you make smarter' decisions. Shortfall: it is an alert to the manager, not a configurable threshold that warns or blocks the employee at the clock-in prompt; the native Shifts clock-in flow carries no warning of any kind; and the capability requires installing the third-party Homebase time clock rather than shipping with Clover. Clover Payroll by ADP handles overtime only after the fact ('calculates overtime in accordance with applicable federal rules'). https://blog.clover.com/reasons-clover-merchants-use-time-clock-by-homebase · retrieved 2026-08-06

labor-break-compliance-by-state differentiator

The platform's complete auto-generated Shift data object carries exactly ten fields: id, employee, cashTipsCollected, serverBanking, inTime, overrideInTime, overrideInEmployee, outTime, overrideOutTime, overrideOutEmployee. No break entity exists anywhere in the employees package (AccountRole, Employee, EmployeeCard, Role, Shift, permission types), so per-jurisdiction break rules, break attestation prompts and missed-break premium flags have nothing in the data model to record against. Clover's own Dec 2024 apps catalogue sells 'break tracking' through the paid Time Clock by Homebase app (Essentials £9.95/month), and even that listing documents no per-state rule engine, no attestation and no premium-pay flagging. https://clover.github.io/clover-android-sdk/clover-android-sdk/com.clover.sdk.v3.employees/-shift/index.html · retrieved 2026-08-04

labor-minor-labor-rules

The complete auto-generated Employee data object carries: id, name, nickname, customId, email, inviteSent, claimedTime, deletedTime, pin, unhashedPin, role, roles, isOwner, shifts, payments, orders, employeeCards, merchant. There is no date-of-birth or age field, so age-based hour caps, prohibited time windows and school-day limits have no data to act on at clock-in, and the Shift object carries no schedule or restriction fields either — the employees package holds only employees, roles, permissions, cards and shifts. Scheduling itself is positioned in the paid Time Clock by Homebase partner app in Clover's own Dec 2024 apps catalogue, whose listing documents no minor-labor enforcement. https://clover.github.io/clover-android-sdk/clover-android-sdk/com.clover.sdk.v3.employees/-employee/index.html · retrieved 2026-08-04

labor-tip-pooling-rules

Positive absence by enumeration: the complete Tips documentation suite (tip suggestions, smart tipping, entry location, paper-receipt adjustment, autofill zero) contains no pooling or tip-out computation; the platform Shift object records only cashTipsCollected with no pool or distribution fields (grade-A prior finding); and Clover's own materials position time/tip tooling in the paid third-party Homebase app. Automatic rule-based pool computation per shift does not exist natively — the only first-party trace is an unqualified blog marketing sentence with no configuration behind it. https://www.clover.com/en-US/help/set-tip-amounts · retrieved 2026-08-05

labor-tip-distribution-audit-trail

The ‘received’ half is documented at the object level and exportable over the REST API: the per-employee shift object carries cashTipsCollected alongside inTime/outTime, and every payment carries an employee reference (Get all payments example: “\"employee\": {\"id\": ...}”) with tip adjustment supported. Shortfall — there is no pool: no object in the documented data model records amounts contributed to or distributed from a tip pool, tip pooling appears nowhere in Clover’s retrievable first-party documentation, and the record’s prior enumeration of top-level data-model objects (merchants, employees, customers, inventory, orders, payments) contains nothing that could hold a distribution ledger — so the FLSA-defensible distribution math cannot be produced natively. https://docs.clover.com/dev/reference/employeecreateshift · retrieved 2026-08-03

labor-qualified-tips-w2-reporting differentiator

The vendor's own payroll FAQ answers this directly, in the negative: 'Clover Payroll by ADP does not determine whether tips or overtime are "qualified." Payroll records actual earnings... Eligibility is determined by the IRS when an employee files their tax return', and 'Employers do not need to change payroll tax settings' under the One Big Beautiful Bill Act — tips remain recorded simply as taxable wages. No qualified-tip separation or Treasury tipped-occupation code support is provided or planned in the documented product. https://www.clover.com/en-US/help/clover-payroll-by-adp-faqs · retrieved 2026-08-05

labor-native-payroll differentiator

The payroll product is 'Clover Payroll by ADP', bought from Employees > Payroll ('select Get started to purchase the Essential Payroll bundle'). It 'calculates payroll taxes', processes tips and overtime and 'handles payroll calculations and disbursements', with Homebase timesheets syncing in. Shortfall: ADP, not Clover, is the processor - 'ADP becomes the system of record for payroll and employee data' - so this is an embedded third-party payroll, not first-party tax filing and direct deposit. https://www.clover.com/en-US/help/clover-payroll-by-adp-faqs · retrieved 2026-09-03 adversarially verified

labor-payroll-export-formats

Payroll connectors exist through the App Market rather than as vendor-maintained native exports.

labor-shift-swap-workflow differentiator

2026-08-05 sweep with full help-centre text. The embedded 'Scheduling by Homebase' (Essentials+, dashboard-only) enumerates its capabilities — create/assign/publish schedules, availability, time off, labor costs, duplication, pinned events, notifications — without any employee-initiated swap or open-shift claim workflow; whether the paid full Homebase product adds swaps on Clover is not documented on any Clover surface. Unknown stands.

labor-server-performance-metrics differentiator

Per-employee sales reporting exists in the Clover Dashboard; attachment, void and comp rates per server not documented.

inventory-recipe-bom-costing

The inventory model is enumerated as items, categories, subcategories, item stock, modifiers, item groups and tags. No recipe, bill-of-materials, ingredient or unit-cost object exists. https://docs.clover.com/dev/docs/working-with-inventory · retrieved 2026-08-02

inventory-unit-conversion-yields

No purchase/recipe/count unit model or yield percentage documented.

inventory-theoretical-vs-actual differentiator

Follows from the absence of recipe costing; requires an App Market partner.

inventory-realtime-depletion differentiator

Item stock — "Quantity of a specific item available in the inventory" — is tracked per item and inventory changes emit webhooks (keys I, IC, IG, IM). Shortfall — depletion is item-level only; with no recipe or BOM object, selling a dish cannot deplete its ingredients, and no automatic depletion mechanism is described in the docs. https://docs.clover.com/dev/docs/working-with-inventory · retrieved 2026-08-02

inventory-86-auto-sync differentiator

Item stock is tracked and inventory webhooks fire on change, so a subscribed channel can learn an item ran out. Shortfall — nothing in the docs performs the 86 automatically or propagates it to online ordering, kiosk or marketplace menus; the integrator has to build that. https://docs.clover.com/dev/docs/working-with-inventory · retrieved 2026-08-02

inventory-count-modes

Positive absence: the complete documented stock-management model is a single editable quantity — 'Select Edit stock count and enter the available stock quantity' (per item, dashboard or device), with a low-stock threshold and an in-stock toggle. No counting workflow exists at all: no full physical count session, no spot count, no scheduled cycle count, and no count-variance history (each edit simply overwrites the number). The inventory settings suite (adjust-stock-tracking, item settings) enumerates its options and none is a count mode. https://www.clover.com/en-US/help/manage-stock-count-and-low-stock-threshold · retrieved 2026-08-05

inventory-mobile-count-offline

Follows a fortiori from the documented counting model: no counting app exists — stock is maintained by editing a per-item stock-count field — so there is no mobile counting workflow to run offline. Barcode scanning is documented for ringing sales and adding items to inventory (add-items-to-orders, add-one-or-more-items-using-a-barcode-scanner), not for counting; and the offline documentation's enumerated scope (payments, Local Connect) omits inventory entirely. https://www.clover.com/en-US/help/manage-stock-count-and-low-stock-threshold · retrieved 2026-08-05

inventory-vendor-catalogs-edi differentiator

Downgraded from no on adversarial re-read 2026-08-02. The claim names Sysco, US Foods and Performance Food Group; no Clover document I could retrieve either offers or denies distributor EDI, and the documentation never mentions purchase orders or supplier catalogues in any form. "I did not find it" is unknown, not evidence that a named business lacks the capability. adversarially verified

inventory-invoice-ocr differentiator

Downgraded from no on adversarial re-read 2026-08-02: the previous value was absence of evidence recorded as positive absence. Unlike the driver and recipe cells, which rest on the data model page affirmatively enumerating its top-level objects, no fetchable Clover document addresses supplier-invoice ingestion at all — the inventory documentation never discusses procurement — and the App Market catalogue lives on clover.com, which is client-rendered and returns no body, so even the "App Market territory" framing is unevidenced. adversarially verified

inventory-price-change-alerts differentiator

Positive absence: no purchasing construct exists to track prices across — the platform inventory model enumerates items, categories, subcategories, item stock, modifiers, item groups and tags with no purchase order, supplier or invoice object (grade-B prior finding), and the item object's only cost field is a single scalar. The alerting that does exist is enumerated: low-stock alerts against a per-item threshold. Per-item purchase-price history with variance alerts against invoices cannot exist without a receiving/invoice model, and none is documented. https://www.clover.com/en-US/help/manage-item-stock-and-low-stock-alerts · retrieved 2026-08-05

inventory-par-auto-suggest differentiator

A per-item par-with-alert mechanism exists: 'In the Low stock threshold field, enter a stock quantity to trigger a low stock alert' (per item, up to 6 decimal places for unit-priced items), with alert icons on the Items page and low-stock alert delivery (receive-low-stock-alerts). Shortfall — no suggested purchase-order quantities are generated from on-hand versus par (no PO or supplier object exists in the platform), and no forecast-driven par mode is documented. https://www.clover.com/en-US/help/manage-stock-count-and-low-stock-threshold · retrieved 2026-08-05

inventory-waste-logging

Positive absence: the documented inventory workflows are stock tracking (auto-decrement on sale), manual stock-count edits, low-stock thresholds and availability management — no waste/spoilage entry, no reason codes, and no waste-cost reporting exists in the enumerated report suite (clover-reports-overview); the Removed items report tracks order-line removals by employee, without reasons or inventory impact. A structured waste workflow that debits inventory does not exist in the documented product. https://www.clover.com/en-US/help/manage-stock-count-and-low-stock-threshold · retrieved 2026-08-05

inventory-shelf-life-expiry

Positive absence at the schema level: the complete item object field set is enumerated in the API reference — name, alternateName, code, sku, price, priceType, unitName, cost, hidden, available, autoManage, defaultTaxRates, isRevenue, isAgeRestricted, ageRestrictedObj, itemGroup, categories, tags, modifierGroups, options, colorCode, priceWithoutVat — and contains no expiration, use-by or received-date field; item stock is a bare quantity. Nothing in the help centre's inventory suite (checked 2026-08-05) adds expiry tracking or an expiring-soon report. https://docs.clover.com/dev/reference/inventoryupdateitem · retrieved 2026-08-05

inventory-bar-partial-bottle

Fractional counting is possible but nothing bar-specific exists: stock counts and low-stock thresholds accept 'Only positive values with up to 6 decimal points for items with per unit price', so bottle fractions can be recorded. Shortfall — no bar inventory workflow is documented: the documented weight-scale integrations (CAS scales, NTEP-certified) are for selling retail items by weight at the register, not for weighing bottles into inventory, and no pour-tracking or bottle-weighing count flow exists. https://www.clover.com/en-US/help/manage-stock-count-and-low-stock-threshold · retrieved 2026-08-05

inventory-cogs-gl-export

Accounting sync 'enables the automatic sharing of your sales data with QuickBooks online' on a daily / weekly / monthly schedule, with mapping of sales, tax rates, fees and tender types; 'no additional fee' on a plan that includes it. Shortfall: sales-side only - no COGS, no accounts-payable invoice detail and no per-category GL account mapping; vendor bills are paid through the separate 'Pay bills by Melio'. https://www.clover.com/en-US/help/use-accounting-sync · retrieved 2026-09-03 adversarially verified

inventory-native-not-partner differentiator

Basic inventory is native, not a partner app: items, categories, subcategories, item stock, modifiers, item groups and tags are core API objects. Shortfall — everything a restaurant means by inventory (recipe/BOM costing, unit conversion and yields, theoretical-vs-actual, vendor invoicing) is absent from the documented model and is supplied by App Market subscriptions. https://docs.clover.com/dev/docs/working-with-inventory · retrieved 2026-08-02

inventory-menu-margin-linkage differentiator

Without recipe cost there is no native contribution-margin-per-item report.

reporting-realtime-dashboard

A Clover Dashboard exists and is a separately monitored component on Clover's own status page in every region, and the developer docs route merchants to it for settings and merchant IDs. Shortfall — no fetchable documentation states which reports it contains or how current they are; clover.com help returns only a page title to a non-JS fetch. The previous pass scored this yes on the same status-page evidence, which does not support a capability claim. https://status.clover.com/ · retrieved 2026-08-02

reporting-eod-closeout

Clover produces end-of-day sales and shift close reports; whether one document reconciles every listed element is not documented.

reporting-pmix-modifier-level

Item-level sales reporting exists; modifier-level PMIX with daypart and revenue-center filters is not documented.

reporting-comps-voids-audit

Void and discount reporting attributed to employees exists; approver attribution and reason codes not documented.

reporting-cash-over-short

Clover Cash Log tracks drawer counts against expected cash; per-employee and per-shift breakdown depth not documented.

reporting-labor-productivity

Re-audited 2026-08-06. The prior no rested on the reports overview page, which disclaims exhaustiveness in its first sentence ('Clover offers a variety of reports... This guide provides an overview of the different types of reports available'), so it cannot establish that no labor-productivity report exists. Partial counter-evidence exists but does not meet the claim as worded: Scheduling by Homebase in the Clover dashboard shows 'estimated labor costs based on scheduled hours, assigned wage rates, and unpaid breaks' (scheduled, not clocked, hours), and Homebase's Clover page advertises syncing 'employees and Clover sales for easier sales versus labor reporting' without specifying metrics. No source retrieved shows sales per labor hour or labor cost as a percentage of sales, by hour, department and employee, from POS-clocked hours - and none shows their absence. Unresolved.

reporting-server-scorecards differentiator

Per-employee sales metrics exist; category attachment rate and tips-as-percent-of-sales not documented.

reporting-channel-profitability differentiator

Revenue by channel exists: 'The order types report shows a breakdown of sales by order type, such as appointment orders, in-store, online, or delivery. It is beneficial to see which order channels drive the most revenue', filterable in Sales Overview by order type. Shortfall — revenue only: no margin per channel, no netting of marketplace commission (marketplace fees are billed outside the POS — DoorDash Drive fees arrive as a monthly emailed invoice), and no per-marketplace breakout is documented. https://www.clover.com/en-US/help/clover-reports-overview · retrieved 2026-08-05

reporting-scheduled-delivery

One report ships on an automatic recurring schedule: 'activate an option to automatically email the closeout report to the owner's email after closing a batch' (Closeout app > Settings > 'Automatically email the closeout report after completion'), gated by notification preferences and restricted — 'Only the account owner may receive the batch closeout report by email.' Shortfall — no other report can be scheduled: dashboard reports are run on demand, with ranges over 3 months delivered as one-time emailed Requested reports; there is no cadence or recipient-list configuration for arbitrary reports. https://www.clover.com/en-US/help/get-closeout-report · retrieved 2026-08-05

reporting-public-api differentiator

Re-sourced from the thin overview page to the endpoints themselves. All four domains the claim names are covered at reference level: menu — POST /v3/merchants/{mId}/items/{itemId} writing name, price, priceType, cost, categories, modifierGroups, tags, defaultTaxRates; labor — POST /v3/merchants/{mId}/employees/{empId}/shifts with inTime/outTime; orders and payments — separate read/write permission categories (https://docs.clover.com/dev/docs/permissions). Credentials are self-service: "If you are only building and testing your app only in the sandbox environment, production account approval is not required. You can develop and test entirely in a sandbox without submitting a production account." The production approval that does exist is identity KYC for App Market submission, not a partner agreement. https://docs.clover.com/dev/reference/inventoryupdateitem · retrieved 2026-08-02 adversarially verified

reporting-webhooks differentiator

Twelve documented event-type keys — A (apps), C (customers), CA (cash adjustments), E (employees), I / IC / IG / IM (inventory, category, modifier group, modifier), O (orders), M (merchants), P (payments), SH (service hours) — delivered to a merchant-app callback URL. Shortfall — the claim requires documented retry behaviour and payload signature verification, and neither exists: authenticity is a static shared secret ("X-Clover-Auth":"0307e264-...") that "displays in every message header after the webhook callback URL is validated", not an HMAC over the payload, and the page documents no retry policy, no backoff, no delivery guarantee and no event replay. Downgraded from yes on adversarial re-read 2026-08-02. https://docs.clover.com/dev/docs/webhooks · retrieved 2026-08-02 adversarially verified

reporting-api-not-upcharged differentiator

No purchase gate for REST API access is documented anywhere: docs are public, the sandbox is self-signup, and the published limits (50 requests/second per app, 16 per token; 10 concurrent requests per app, 5 per token) apply without reference to a paid tier. Shortfall — Clover never states in writing that API access is free, and no route to higher limits is published, so this is the absence of a fee schedule rather than an affirmative no-charge commitment. https://docs.clover.com/dev/docs/api-usage-rate-limits · retrieved 2026-08-02 adversarially verified

reporting-tier-paywall differentiator

Unknown stands, but flag a live risk the dossier does not surface: third-party sources consistently claim online ordering and delivery integrations require Clover's upgraded restaurant plan and that app availability is narrower on Essentials tiers. Those are roundups and therefore unusable as evidence, but they mean several 'yes' scores in the digital and delivery sections may be tier-gated rather than base-product capabilities. The digital/delivery yes cells must not be read as included at the entry plan. adversarially verified

reporting-history-retention differentiator

One hard, documented constraint exists: "Clover is now enforcing a 90-day window on calls to Payments and Orders API endpoints", so historical data must be paged with createdTime filters in 90-day slices. Shortfall — no total retention period for merchant data is published, no archive or bulk-history export is documented, and nothing states how far back the 90-day windows may be walked. https://docs.clover.com/dev/docs/limits-added-to-calls-to-payments-and-orders-endpoints · retrieved 2026-08-02

reporting-anomaly-alerts differentiator

2026-08-05 sweep with full help-centre text. Documented alerting is low-stock alerts (per-item threshold) and status-page subscription emails; Insights produces AI summaries and recommendations but no operator-configured metric thresholds, and no void-spike/sales-deviation alert exists in the enumerated report suite. A metric-threshold alerting feature is neither documented nor denied. Unknown stands.

reporting-nl-query

Insights ships a natural-language assistant over the merchant's own data: 'The Ask me button opens an AI assistant that lets you ask questions about your business data and receive answers directly in the dashboard', with suggested prompts like 'What are today's sales? What are my top items? Who are my top employees?' (create-and-manage-insights), alongside real-time metrics, trends and AI summaries. Documented limits: 'available to single-location merchants in the U.S. with the Essentials plan or higher'; multi-location merchants are excluded ('Can I use business insights for multiple locations? No.'). The separate Vera chatbot also opens standard reports with filters applied from natural-language requests, respecting role permissions. https://www.clover.com/en-US/help/insights-faqs · retrieved 2026-08-05

reporting-guest-cohorts differentiator

Guest-level records carry the raw analytics: customer profiles show 'Individual order details and the total amount spent per order', order history, points, feedback and audience membership, and the customer list auto-segments by visit frequency (Regulars 12+ visits, VIPs 25+, thresholds adjustable). Shortfall — no cohort reporting is documented: no new-versus-returning guest counts, no visit-frequency distribution report, and no lifetime-spend cohort analysis appears in the enumerated report suite; the Guest count report counts covers, not identified guests. https://www.clover.com/en-US/help/view-customer-details · retrieved 2026-08-05

reporting-sales-forecast differentiator

2026-08-05 sweep with full help-centre text. The documented analytics are backward-looking: Sales Overview Trends (comparisons over prior periods), daypart-filtered sales, and Insights' AI summaries of recent performance ('a short, plain-language summary of recent performance'). No forward sales forecast at any granularity is documented, and no forecast feeds scheduling or ordering. Absence not closed by enumeration of the analytics surface, so unknown stands.

reporting-tip-tax-compliance

The declared-versus-charged foundation exists in the platform data model: Shift.cashTipsCollected records employee-declared cash tips per shift alongside a serverBanking flag, and card tips are recorded on payments attributed to employees. Shortfalls — tip pool distribution detail appears only as a marketing claim (blog.clover.com on the 80/20 rule: Clover can 'Pool tips so they can share and distribute gratuities with employees', with no documented report behind it); no tax liability summary by jurisdiction is documented anywhere fetchable; and Clover's Dec 2024 apps catalogue positions 'cash tip declaration... and payroll-ready timesheet export' in the paid Time Clock by Homebase app rather than the native stack. The merchant Reporting help pages are client-rendered and returned only 'Clover Help' to a non-JS fetch. https://clover.github.io/clover-android-sdk/clover-android-sdk/com.clover.sdk.v3.employees/-shift/index.html · retrieved 2026-08-04

multi-location-org-hierarchy

The data model enumerates its top-level objects — merchants, employees, customers, inventory, orders, payments — and merchant is the root: there is no parent, group, brand or organisation object above it, and every other object binds to "a single merchant". Each location is an independent merchantId with its own separately scoped API token. https://docs.clover.com/dev/docs/clover-data-model · retrieved 2026-08-02 adversarially verified

multi-location-central-menu-publish

'Enable enterprise merchants to create and publish POS menus to their franchise or chain locations': a parent (enterprise / corporate / chain) authors a menu, assigns some or all child locations, and 'Publish to make the menu available for ordering at all assigned locations'; propagation 'takes place through a queue and can take time ranging from seconds to hours'; local edits reconcile upward as variation badges. Shortfalls: 'only available for merchants on the Restaurant Growth plan'; 'currently, only POS menus are available for multi-location'; and no publish / version history - the menu carries only a Draft / Processing / Published status. https://www.clover.com/en-US/help/manage-multi-location-menus · retrieved 2026-09-03 adversarially verified

multi-location-price-zones

One item record, several prices: per location group via 'Add location variation' on base price and on menu price ('Variation price: Different menu prices are set for specific locations'), with a badge counting variations; per channel via unique menus per online partner ('You can create unique menus for each platform, giving you full control over which items appear and at what prices'); per daypart via daypart-assigned POS and online menus whose menu price 'overrides the item's base price'. Multi-location menus need the Restaurant Growth plan. https://www.clover.com/en-US/help/update-multi-location-menu · retrieved 2026-09-03 adversarially verified

multi-location-consolidated-reporting

A consolidated multi-location Dashboard view exists; ranking and variance flagging not documented.

multi-location-cross-location-giftcard

2026-08-05 sweep with full help-centre text. The liability half exists — the Gift Cards dashboard's Outstanding Balance report lists card numbers, starting/remaining balances and activation dates, with a monthly 'Outstanding liability report' (view-reports-on-the-gift-cards-dashboard) — but no article states whether a card sold at one location of a multi-location business is redeemable at the others, and nothing documents inter-store settlement. The Gift Card API roots at one merchantId (prior finding). Unknown stands.

multi-location-cross-location-loyalty

Cross-location sync is affirmed for the rewards balance: 'Do rewards work across all my Clover devices and locations? Yes. Rewards are synced across all connected Clover devices and eligible business locations, ensuring consistency for your customers.' Shortfall — 'eligible business locations' is undefined, and a shared cross-location guest profile with order history is not documented: the platform Customers object binds to a single merchant (prior grade-B finding), so what unifies beyond the points balance is unstated. https://www.clover.com/en-US/help/rewards-program-faqs · retrieved 2026-08-05

multi-location-multi-brand differentiator

One terminal can carry distinct menus: 'Multiple menus let you create and manage multiple menus for your point of sale (POS) devices. Each menu can display different categories, items, and prices, allowing you to control what appears on each device' — e.g. separate dining-room and bar menus — and separate online menus exist per ordering channel. Shortfall — nothing supports distinct brands: no per-menu receipt branding, no brand-level revenue segregation in reporting (order types are the only channel dimension), and one business identity per merchant account. https://www.clover.com/en-US/help/work-with-multiple-menus-devices · retrieved 2026-08-05

multi-location-multi-tax-jurisdiction

Tax is configured per merchant account with multiple simultaneous rates; jurisdiction-specific prepared-food rules and per-location exemptions not documented.

multi-location-central-labor-policy

Positive absence: the labor stack is documented as per-location with no policy engine — 'If you have multiple locations, jobs are managed separately for each location' and 'Are wage rates shared across locations? No. Wage rates are managed separately for each location'; scheduling (embedded Homebase) checks only shift overlaps and time-off conflicts; and at the terminal there is nothing to enforce — the platform has no break, schedule-restriction or age fields at all (grade-A prior findings on the Shift and Employee objects). Location-group labor rules enforced at the terminal do not exist in the documented product. https://www.clover.com/en-US/help/setup-wages-with-clover · retrieved 2026-08-05

hardware-commodity-devices differentiator

Clover software runs on Clover-branded Android hardware — the device tech-spec page enumerates only Station (2018), Station Solo, Station Duo, Station Duo 2, Mini 2, Mini 3, Compact, Flex 3, Flex 4, Flex Pocket and the Go Reader. Shortfall/exception — only the Clover Go card reader works with commodity hardware, pairing over Bluetooth to the merchant's own iOS or Android phone; there is no way to run the full POS on a generic tablet. https://docs.clover.com/dev/docs/clover-devices-tech-specs · retrieved 2026-08-02

hardware-os-platforms

Android AOSP across the fleet: 7.0 (Station 2018), 8.1 upgradable to 10.0 (Station Duo, Mini 2), 10.0 (Station Solo, Station Duo 2, Mini 3, Flex 3), 13 / API 33 (Compact, Flex 4, Flex Pocket). The Go Reader "Operates with iOS 10 and Android 4.4 (and higher)". Shortfall — no Windows, no browser-based terminal and no iPad-native full POS; the older devices are pinned to Android 7/8 vintages. https://docs.clover.com/dev/docs/clover-devices-tech-specs · retrieved 2026-08-02

hardware-handheld-purpose-built

SHORTFALL — no published drop rating and no IP ingress rating, which the claim requires. The purpose-built handheld itself is fully documented: Flex 4 "5.99 inch IPS LCD, 1440 x 720 pixels", "4G/LTE, WiFi, and Bluetooth", "EMV Contact (chip), EMV Contactless (tap), and Magstripe Reader", "Internal thermal receipt printer", Android 13 API level 33; Flex Pocket is the printerless variant. Searching the raw page source for drop / ingress / IP5x / IP6x / water / dust / rugged returns nothing for any device. Clover does publish such ratings for its KDS ("protection from water, duster ingress ... and a 50C temperature tolerance"), so the handheld silence is not a search artifact. https://docs.clover.com/dev/docs/clover-devices-tech-specs · retrieved 2026-08-02 adversarially verified

hardware-handheld-battery-swap differentiator

Field-replaceable: 'Your Clover Flex or Flex Pocket battery replacement kit contains a rechargeable Lithium-Ion (Li-ion) battery. Once the new battery is installed in your Flex device, the old battery should be recycled', and the SIM article has the merchant 'remove the battery' with a 1.5 mm hex key. Shortfalls: not hot-swappable (device off, screws out), and no rated full-shift battery life is published for Flex - the developer tech-specs page rates only the Clover Go reader ('160 dip, 160 swipe, or 130 contactless transactions per charge') and the 2018 Station tablet ('up to four hours'). https://www.clover.com/en-US/help/battery-disposal · retrieved 2026-09-03 adversarially verified

hardware-handheld-lte

Cellular is a built-in radio on every current handheld: Flex 4 and Flex Pocket "4G/LTE, WiFi, and Bluetooth"; Flex 3 "Wi-Fi, 4G/LTE", with region SKUs listed — "North America (C045U)—4G/LTE only", "Europe (C045E)—4G/LTE fallback support for 3G", "Argentina (C045L)—4G/LTE fallback support for 3G". Precision: the only "fallback" the page documents is 4G/LTE to 3G, a cellular-generation fallback, not an automatic Wi-Fi-to-cellular failover. https://docs.clover.com/dev/docs/clover-devices-tech-specs · retrieved 2026-08-02 adversarially verified

hardware-offline-mode

"Clover Mini and Flex are set to take offline payments for up to 7 days", with merchant-settable per-transaction and cumulative caps. Shortfall — offline mode is regionally withheld ("Canadian merchants cannot use their Clover devices to process any payments in offline mode"; UK/Ireland "Payments are not processed if the Clover device is offline"), and no offline feature matrix covers anything beyond payments. https://docs.clover.com/dev/docs/handling-offline-payments · retrieved 2026-08-02

hardware-kds

SHORTFALL — station routing is documented as NOT merchant-selectable, and course/fire timing is undocumented. First-party KDS hardware is real: "available in 14" and 24" models", "a touch-responsive KDS bump bar", "protection from water, duster ingress ... and a 50C temperature tolerance" (https://blog.clover.com/introducing-clover-kitchen-display-system-kds), and it is a supported destination — "you can set up a KDS as the order printer for a default firing device". But the developer FAQ states a merchant "can only select a single default firing device", and: "If the default firing device has more than one order printer connected, can the merchant select which order printer to fire online orders to? No, the merchant cannot select an order printer in this case." The blog's "supports high-volume kitchens and multiple stations" is a capacity statement, not routing configuration. https://docs.clover.com/dev/docs/faqs · retrieved 2026-08-02 adversarially verified

hardware-kiosk differentiator

Clover Kiosk is first-party with integrated payment; freestanding form factor and documented ADA compliance not confirmed.

hardware-drive-thru

Re-audited 2026-08-06. The prior no rested on the developer device tech-specs page, which describes itself as covering 'various models of Clover devices suited for various business needs' and asserts no completeness; it also enumerates only Clover-branded terminals (Station Solo, Station Duo/Duo 2, Station 2018, Mini 2/3, Compact, Flex 3/4, Flex Pocket, Go), which is not the surface on which outdoor menu boards, order confirmation displays or headsets would appear. A full-text help-centre sweep for drive-thru, headset, menu board, order confirmation display and lane returned nothing relevant, but a search returning nothing is not positive evidence of absence. Third-party digital-signage vendors advertise Clover menu-board integrations; no first-party drive-thru hardware programme or speed-of-service lane timer was located either way. Unresolved.

hardware-printer-compatibility

Internal thermal receipt printers ship in Station (2018), Mini 2, Mini 3, Compact, Flex 3 and Flex 4, and the Print API drives "the printer on a merchant's device". Shortfall — no published compatibility matrix for third-party or kitchen printers, and no supported-model list; "Kitchen Printers" appears only as a status-page component. https://docs.clover.com/dev/docs/clover-devices-tech-specs · retrieved 2026-08-02

hardware-peripherals

Some peripherals are integrated rather than attached: Station Duo 2 has "Dual cameras: 5.0M pixels" doing "1D/2D" scanning, and the Go Reader pairs over "Bluetooth to mobile device". Shortfall — no published compatibility list for cash drawers, scales, third-party barcode scanners, caller-ID boxes or customer displays. https://docs.clover.com/dev/docs/clover-devices-tech-specs · retrieved 2026-08-02

hardware-p2pe-terminal

Card data handling is documented as scope-reducing: cardholder data "encryption and transmission are handled entirely inside the Clover ecosystem" for semi-integrations, and TransArmor tokens replace cardholder data. Shortfall — no PCI-listed P2PE solution is named and no validation listing or AOC is published, so this is tokenisation plus a QSA-validated DSS claim, not a documented P2PE terminal. https://docs.clover.com/dev/docs/pci-dss-version-40-requirements-643-and-1161 · retrieved 2026-08-02

hardware-tap-to-phone differentiator

Re-sourced from a Fiserv press release to Clover developer documentation. "While Tap to Pay on iPhone allows contactless payments without additional hardware, this feature is not available for Android devices." Clover Go is the bring-your-own-device surface — its app "is available for download from both the Apple App Store and Google Play" and it "accepts chip, dip, and contactless payments, including Tap-to-Pay on iPhone" (https://docs.clover.com/dev/docs/clover-devices-tech-specs). iOS-only, and that limit is documented rather than merely unevidenced: "For Android, a physical Clover card reader ... or a dedicated Clover device ... is still required to process contactless payments." https://docs.clover.com/dev/docs/android-sdk-faqs · retrieved 2026-08-02 adversarially verified

hardware-pricing-transparency differentiator

Device prices are published on clover.com but the page is JS-rendered and unfetchable; ISO/bank channel pricing differs from the direct rate card.

hardware-ownership-vs-lease differentiator

Direct purchase is available; ISO- and bank-sold Clover is frequently leased, and the lease terms are the reseller's, not Clover's.

hardware-usable-after-churn differentiator

Not determinable. Clover devices run Clover's own Android build and Clover's payment stack, but no first-party document states whether a device keeps any function after the merchant leaves Clover. The 2026-08-01 pass scored this "no" citing the developer architecture page, which does not address it — absence of evidence is unknown.

hardware-rma-sla differentiator

A warranty term is published for subscription hardware: 'A full warranty is included and lasts for the full term of the agreement, with unlimited device replacements as needed. The Equipment Protection Program covers defects, broken screens, liquid damage, environmental conditions, and more' (device protection unavailable in NY/OR; subscriptions non-cancelable, not offered in VT). The replacement workflow is documented (contact support, shipping labels printed from Devices and printers — replace-return-clover-devices). Shortfall — no turnaround SLA: neither replacement shipping time nor advance exchange is committed anywhere, and warranty terms for outright-purchased devices are not published. https://www.clover.com/en-US/help/understand-device-subscriptions · retrieved 2026-08-05

hardware-byod

One BYOD tier exists: the Clover Go Reader pairs over Bluetooth to the merchant's own phone and "Operates with iOS 10 and Android 4.4 (and higher)", with battery life quoted as "Estimated 160 dip, 160 swipe, or 130 contactless transactions per charge". Shortfall — the full POS, Register and Dining run only on Clover-branded devices. https://docs.clover.com/dev/docs/clover-devices-tech-specs · retrieved 2026-08-02

hardware-remote-device-management differentiator

On-device diagnostics are documented: connection history with "IP addresses and connection uptime or downtime", a Speed Test page, a printer queue that can be cleared or retried, a network transmission queue, and merchant/device identity (MID, Clover ID, device serial). Shortfall — this is a technician tool run on the device itself; no remote or fleet-wide management console, no push configuration and no remote lock/wipe is documented. https://docs.clover.com/dev/docs/device-diagnostics · retrieved 2026-08-02

hardware-selfpour-scales

2026-08-05 sweep with full help-centre text. The documented specialty hardware is retail weight scales (CAS models, NTEP trade certification, sale-by-weight at the register) — no self-pour tap wall, flow meter or liquor-spout integration appears anywhere in the help centre or device documentation, and no such App Market partner is named on a readable surface. Absence not closed by enumeration of supported peripherals, so unknown stands.

hardware-callerid-integration

2026-08-05 sweep with full help-centre text (searched caller ID, phone integration, incoming call). Nothing documents caller-ID hardware or a telephony integration popping the customer record; the hits are billing, lease and support-contact articles. The peripheral compatibility surface remains unpublished (prior finding), so absence cannot be closed. Unknown stands.

extensibility-public-api-docs

Fetched anonymously, no login, full body renders: API reference, Android and Ecommerce build tutorials, REST Pay Display, OAuth flows, API changelog, release notes and executable recipes — "Recipes provide response details and are a great option if you don't have an OAuth token". No NDA, account or sales call is required to read any of it, and the developer FAQ confirms "You can develop and test entirely in a sandbox without submitting a production account". https://docs.clover.com/dev/docs/developer-documentation · retrieved 2026-08-02 adversarially verified

extensibility-api-access-cost differentiator

Nothing in the developer documentation charges for REST API access, and the published limits apply uniformly with no paid tier referenced: "50" requests per second per app, "16" per token, "10" in-progress requests per app and "5" per token, returning 429 when exceeded. Shortfall — Clover never affirmatively states API access is free, and publishes no route to higher limits, so the cost position is undocumented rather than confirmed. https://docs.clover.com/dev/docs/api-usage-rate-limits · retrieved 2026-08-02

extensibility-free-sandbox differentiator

Self-serve access is documented — create a sandbox developer account, create test merchant accounts, generate a test API token from the sandbox Developer Dashboard, with no production merchant account, NDA or partner agreement referenced, against a gateway that "neither checks for card validity nor verifies that the payment request is correct or complete". Shortfall — the claim requires a FREE sandbox WITH SEEDED DATA and neither is documented: Clover never states the sandbox is free of charge, and the developer creates their own test merchants rather than receiving seeded sample data. Downgraded from yes on adversarial re-read 2026-08-02. https://docs.clover.com/dev/docs/get-started-with-sandbox-environment · retrieved 2026-08-02 adversarially verified

extensibility-oauth-partner-apps

Re-sourced from the OAuth mechanics page, which does not address scoping or revocation, to the permissions page, which does. Grants are per data category — customers, employees, inventory, merchant, orders, payments, Ecommerce API — each with separate Read and Write, and are operator-made: "When a merchant installs your app, they approve the permissions your app requests." Revocation is per-app uninstall, and grants are pinned to the installed version: "If you change app permissions after a merchant downloads your app, the merchant must uninstall and reinstall the app for the new permissions to take effect." Tokens are expiring access_token/refresh_token pairs scoped to one merchantId (https://docs.clover.com/dev/docs/use-oauth), not shared static keys. https://docs.clover.com/dev/docs/permissions · retrieved 2026-08-02 adversarially verified

extensibility-webhooks-push

SHORTFALL — no lifecycle granularity. Push delivery is real and replaces polling, but the event table gives orders one key, O, with operations CREATE/UPDATE/DELETE ("Order is created, updated, or deleted"), and payments key P with CREATE/UPDATE. Created and modified are covered and paid is inferable from a payment CREATE; voided and refunded are not distinguishable — each arrives as an order UPDATE carrying an object id, so the consumer must read the order back to learn what changed. Authenticity is a static X-Clover-Auth header rather than a payload signature, and no retry or replay policy is published. https://docs.clover.com/dev/docs/webhooks · retrieved 2026-08-02 adversarially verified

extensibility-webhook-reliability differentiator

Authentication is a static shared secret, not a payload signature: "This key displays in every message header after the webhook callback URL is validated", as "X-Clover-Auth":"0307e264-...". Shortfall — there is no HMAC payload signature, and the page documents no retry policy, no backoff, no delivery guarantee and no event replay; it is silent on all four rather than denying them. https://docs.clover.com/dev/docs/webhooks · retrieved 2026-08-02 adversarially verified

extensibility-order-injection-api

Orders can be created programmatically through the Orders and Atomic Orders REST APIs and "appear in the Orders and Register apps". Shortfall — they "are not compatible with Clover Dining, which uses a private data schema for features such as table mapping and guest seating", and the page adds "The Dining app does not recognize table assignments or dining-specific metadata from external order creation", so on a table-service site an injected order cannot carry a table or a seat. https://docs.clover.com/dev/docs/orders-faqs · retrieved 2026-08-02 adversarially verified

extensibility-menu-write-api differentiator

POST /v3/merchants/{mId}/items/{itemId} writes name, alternateName, code, sku, price, priceType, unitName, cost, hidden, available, autoManage, defaultTaxRates, isRevenue, isAgeRestricted, ageRestrictedObj, itemGroup, categories, tags, modifierGroups, options, colorCode and priceWithoutVat — so items, modifiers and prices are all mutable, not read-only. Documented carve-out, orthogonal to this claim: "This endpoint cannot be used to update an item's stock quantity. To create or update stock for an item, you must use the Update item stock endpoint." https://docs.clover.com/dev/reference/inventoryupdateitem · retrieved 2026-08-02 adversarially verified

extensibility-doordash-preferred differentiator

Verified against DoorDash's own newsroom: the 2026 Preferred Integration Partner roster is Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper — Clover is absent. The roster was generated on performance and feature data as of 2026-05-08. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-01 adversarially verified

extensibility-first-party-delivery-integrations differentiator

"Uber Eats" is a monitored component on Clover's own status page in North America, evidencing a Clover-operated first-party marketplace integration, and Door-to-Door Delivery via DoorDash Drive is documented in Clover Hospitality help. Shortfall — no first-party DoorDash or Grubhub *marketplace* integration is documented, and Clover is absent from DoorDash's 2026 Preferred Integration Partner roster. https://status.clover.com/ · retrieved 2026-08-02

extensibility-middleware-compatibility

Two of the five named aggregators confirmed at their own sites. Deliverect: "Deliverect has partnered with Clover to build a reliable two-way integration so you can manage your online orders from a single point-of-sale with ease" — Canada, Germany, Netherlands, United Kingdom, United States — plus a published setup article, "Clover: Authorize POS" (https://help.deliverect.com/en/articles/7979132-clover-authorize-pos). Otter: "Otter's integration with Clover POS make every one of your restaurant's activities more valuable", with auto-accept ("Accept every order your restaurant receives, and push them all straight to your Clover POS") and menu sync ("Update items and menus in seconds, and see changes in your restaurant's Clover POS instantly"), US and Canada (https://www.tryotter.com/integrations/clover). Grade E is correct: the proposition is about third parties, not about Clover. https://www.deliverect.com/en-us/integrations/clover · retrieved 2026-08-02 adversarially verified

extensibility-accounting-connectors

QuickBooks and other GL connectors are available through the App Market as third-party apps rather than vendor-maintained connectors.

extensibility-payroll-export

Payroll integrations are App Market partner products, not first-party named exports.

extensibility-app-marketplace

SHORTFALL — the marketplace is not publicly browsable. Third-party apps and self-install are documented: merchants "subscribe to an app through the Clover App Market" and select a tier "before installing your app"; "You receive 70% of the amount that Clover collects from the merchant for an installed app". Clover's UK apps guide describes the App Market as "access to a wide range of third-party apps that integrate with Clover POS systems", available on "Clover Device", and names third-party developers (LoyLap, Homebase, Pintuna). But https://www.clover.com/appmarket, an app-detail path and a search path all return the same 4,601-byte shell titled "Clover Dashboard" with no listing — browsing requires the merchant Dashboard or a device. The only public catalogue retrievable is a December 2024 UK PDF. https://docs.clover.com/dev/docs/monetizing-your-apps · retrieved 2026-08-02 adversarially verified

extensibility-headless-embedded

Clover documents semi-integration, where a third-party POS drives the Clover device for payment — the inverse of a headless POS engine driven by a third-party UI. https://docs.clover.com/dev/docs/clover-development-basics-semi · retrieved 2026-08-01

extensibility-data-portability-exit differentiator

A live merchant can authorise an app to read orders, payments, customers, inventory and employees through documented REST permissions, which is a real portability path. Shortfall — payments and orders reads are capped at a 90-day window per call, no bulk export format is documented, and no post-termination access window exists in any published document. https://docs.clover.com/dev/docs/permissions · retrieved 2026-08-02

reliability-offline-order-entry

Orders can be taken and recorded on-device with no connection while store-and-forward is active — up to 7 days on Mini and Flex. Shortfall — the capability is withheld entirely in Canada, the UK and Ireland per the region table, and no document describes which POS functions besides payment survive an outage. https://docs.clover.com/dev/docs/handling-offline-payments · retrieved 2026-08-02 adversarially verified

reliability-offline-card-auth differentiator

"The Clover device records offline payments when a merchant attempts a transaction without a network or Wi-Fi connection", and "By default, Clover Mini and Flex are set to take offline payments for up to 7 days" — cards, not a cash-only fallback. Precision, in Clover's own words: this is deferred capture, not offline authorization — "the device also can't verify the payment gateway or check if the card is valid and has sufficient funds", and an eventual decline is the merchant's loss. Integrator offlineOptions overrides can defeat the merchant's configured limits entirely. https://docs.clover.com/dev/docs/handling-offline-payments · retrieved 2026-08-02 adversarially verified

reliability-offline-decline-liability differentiator

Partly documented: the 7-day default window, the merchant-configurable per-transaction and cumulative caps, and the integrator's stated duty to "assume responsibility for warning the merchant of any possible risk". Shortfall — the docs never assign liability for a declined offline transaction to a named party, and document no post-reconnect failure report or recovery workflow. https://docs.clover.com/dev/docs/handling-offline-payments · retrieved 2026-08-02 adversarially verified

reliability-lan-degraded-multi-terminal differentiator

Local Connect 'is a local network solution that shares information between Clover devices' and fires register orders to the KDS with the internet down. Shortfall: the documented offline path is POS-to-KDS; nothing states that two POS terminals keep sharing one open check or table state over the LAN during an outage. https://www.clover.com/en-US/help/manage-clover-local-connect-network · retrieved 2026-09-03 adversarially verified

reliability-local-transaction-engine differentiator

No edge server: Local Connect is device-to-device over the merchant's router ('configure the local network so your Clover devices can communicate directly with each other'), and offline card payments are queued per device ('devices can take offline payments for up to 7 days', with per-payment and total limits) then 'processed as soon as you're back online'. Shortfall: the ordering path is local only in this peer-to-peer sense; 'You still need the internet to do things like process credit card payments and save your sales information online'. https://www.clover.com/en-US/help/use-kds-offline · retrieved 2026-09-03 adversarially verified

reliability-offline-kds-printing

'Clover Local Connect allows your Clover devices to talk to each other directly through a local network. This means that even if the internet is down, you can still take an order at the register on a Clover device, and it will show up on the Clover KDS'; 'Enables devices, such as the Clover Mini or Station Duo, to fire orders to the Kitchen Display System (KDS) immediately, even when the internet is down'. Temporary support: payments and cloud sync still need the internet. https://www.clover.com/en-US/help/use-kds-offline · retrieved 2026-09-03 adversarially verified

reliability-printer-fallback

Documented single-hop fallback: an API print request routes "to the firing device's order printer or, if none is available, to its onboard printer", and the print_event GET endpoint lets an app check job status. Shortfall — no failover between kitchen printers, no KDS-to-printer failover, and no documented alert when a print fails. https://docs.clover.com/dev/docs/printing-orders-rest-api · retrieved 2026-08-02

reliability-sync-conflict-handling

Checked 2026-08-04 across docs.clover.com (Handle offline payments, Orders FAQs, general FAQs, webhooks, device diagnostics, status-code reference): the only documented 'conflict' is a synchronous payment-request concurrency error ('Conflicting request (CreateCharge) currently in progress'), and the offline documentation covers the queued-payment path only — no fetchable page states how divergent edits made on two devices during a network partition are reconciled (last-write-wins, merge, or operator prompt). The merchant help centre (clover.com/help) is client-rendered and returns only its title to a non-JS fetch, so a help-centre-only statement would be invisible to this pass. Unresolved.

reliability-offline-feature-matrix

A published limitation matrix exists, organised by region rather than by feature: offline payment processing unavailable to Canadian merchants and in the UK/Ireland; auth and pre-auth unsupported in Ireland and the UK; pre-auth unsupported in Austria, Germany and the Netherlands; vaultCard() unsupported in Ireland, the UK and Argentina; readCardData() unsupported in Argentina. Shortfall — it is a regional restriction table, not a matrix of which POS functions work offline. https://docs.clover.com/dev/docs/region-specific-features · retrieved 2026-08-02

reliability-public-status-page

Public, no login, per-component and per-region: "North America - Clover Services" covering Payment Authorization Services, Clover Platform Services, Clover GO, Dashboard, Clover Sport, Tips, Refunds, Payments, Batch Closeouts, Card Issuer Processing, Ecommerce, Online Ordering, Cloud Pay Display, Invoicing, Kitchen Printers and Uber Eats, with separate trees for Europe, Latin America, Australia and Brazil. Historical state is public — Past Incidents rendered dated daily entries from 2026-08-02 back through 2026-07-22. CORRECTION to an earlier note: there is no "Developer Services" section; platform components appear as "Clover Platform Services" per region, and Webhooks and Sandbox are not listed as components. https://status.clover.com/ · retrieved 2026-08-02 adversarially verified

reliability-247-live-support

No source URL was produced and I could not produce one — clover.com is client-rendered and every help/marketing URL returns only a page title. Under the stated rule (no URL, no yes) this cannot stand. It is also the cell most exposed to Clover's indirect distribution: for bank/ISO-sold accounts the first-line support path is the reseller, and no public document states which support tier is included with which plan. adversarially verified

reliability-onsite-install differentiator

On-site install typically comes from the selling bank or ISO rather than a first-party Clover field service.

reliability-menu-build-service differentiator

The build is automated but self-serve: 'You can upload a digital copy of your menu, such as an image or PDF, to generate a draft item list, complete with categories, modifier groups, and modifiers' using AI, which the operator must then review ('The AI-generated list may not be fully accurate. Review, edit, and finalize the draft before publishing'). Shortfall — no human vendor-performed menu build is documented as part of onboarding; the operator runs the import and owns the validation. https://www.clover.com/en-US/help/generate-item-list-from-digital-menu · retrieved 2026-08-05

reliability-hardware-replacement-sla

A replacement program exists and is documented end-to-end: contact Clover support with MID/serial/purchase date, support 'will also create a shipping label for the new device being shipped to you', labels print from the dashboard (Devices and printers), and subscription hardware carries 'unlimited device replacements as needed' under the included Equipment Protection Program (understand-device-subscriptions). Shortfall — no stated turnaround: neither a replacement ship-time commitment nor advance exchange appears anywhere. https://www.clover.com/en-US/help/replace-return-clover-devices · retrieved 2026-08-05

reliability-pci-dss-4-attestation

Clover states it "is compliant with applicable PCI DSS requirements" and that this is "validated by a Qualified Security Assessor (QSA)", and documents PCI DSS v4.0 requirements 6.4.3 and 11.6.1 as mandated from 2025-04-01. Shortfall — no Attestation of Compliance is published or linked anywhere on the page; enquiries are routed to an email address. https://docs.clover.com/dev/docs/pci-dss-version-40-requirements-643-and-1161 · retrieved 2026-08-02

reliability-mfa-role-based-access

Two-factor authentication on the Clover Dashboard and role-based employee permissions exist; enforceability policy not documented.

reliability-self-serve-training

Clover maintains a public help center and training content; an on-terminal practice/training mode was not confirmed.

reliability-failover-terminal-role differentiator

There is no master terminal to fail: each Clover device runs the POS independently against the cloud, and during internet outages Clover Local Connect lets devices reach each other peer-to-peer over the LAN ('you can still take an order at the register on a Clover device, and it will show up on the Clover KDS'), so no single terminal's failure takes down the others. Shortfall — no failover semantics are documented for coordinating roles that do exist (the single 'default firing device' for online orders, KDS pairings): whether another device assumes those roles automatically is unstated. https://www.clover.com/en-US/help/use-kds-offline · retrieved 2026-08-05

reliability-cellular-backup

SHORTFALL — the automatic failover the claim requires is undocumented, and the radio is not universal. LTE is built into most terminals (Station Solo "Ethernet, Wi-Fi, and 4G LTE connectivity"; Station Duo and Duo 2 "Ethernet, WiFi, and 4G/LTE"; Mini 2/3 "Ethernet, Wi-Fi, 4G/LTE"; Compact "4G/LTE (North America)"), but searching the raw page for failover/fallback/switch returns only Flex 3's "4G/LTE fallback support for 3G" — a cellular-generation fallback, not a Wi-Fi handover. Clover's UK Flex page says only "connecting via Wi-Fi or LTE" (https://uk.clover.com/flex/). And Clover Station (2018) lists "Connectivity—Ethernet, Wi-Fi" with no cellular at all. https://docs.clover.com/dev/docs/clover-devices-tech-specs · retrieved 2026-08-02 adversarially verified

commercial-month-to-month-contract differentiator

Clover-direct software plans are marketed month-to-month, but bank/ISO-sold accounts commonly carry multi-year processing agreements. Could not fetch the terms page.

commercial-no-early-termination-fee differentiator

Channel-dependent — Clover-direct is marketed without a term, while reseller processing agreements frequently carry ETFs. No published MSA statement retrievable.

commercial-autorenew-terms-published

The UK Merchant Acquiring Terms and Conditions are a publicly downloadable PDF (linked from uk.clover.com/legal/) and state the exit terms in full: clause 28.1 “You may terminate your Merchant Agreement at any time by giving not less than one (1) months’ notice to Clover”, Clover’s side requires “not less than ninety (90) days written notice” (28.2.1), and “A £200 fee may be charged in the event your Merchant Agreement is terminated” in enumerated cases — an open-ended agreement with a stated notice window rather than an auto-renewing fixed term. Shortfall — the equivalent US contract terms could not be read: clover.com/legal and eu.clover.com/terms are served as client-rendered JS applications that return no document text to a non-JS fetch (2026-08-03), so the US notice window remains verifiable only in a signed quote as far as this pass could establish. https://uk.clover.com/content/dam/firstdata/clover-uk/en/assets/pdf-legal/Clover-UK-Merchant-Acquiring-TCs-non-i99-April2026.pdf · retrieved 2026-08-03

commercial-processing-not-bundled differentiator

Processing is bundled and assigned, not selectable: Brazil and Mexico "Payment transactions" are "processed through SiTef", gift cards run "through the Fiserv payment gateway", and no third-party processor route appears anywhere in the payments documentation. https://docs.clover.com/dev/docs/region-specific-features · retrieved 2026-08-02

commercial-interchange-plus-published differentiator

Not determinable. Clover publishes rate information only on clover.com, which is client-rendered and returned nothing but a page title on 2026-08-02, and most Clover accounts are sold by banks and ISOs that price independently. Whether an interchange-plus option is published anywhere first-party could not be established, so this is unknown rather than no.

commercial-rate-increase-clause differentiator

Not scored by the 2026-08-01 research pass.

commercial-pricing-published

Clover publishes a direct-channel rate card on clover.com, but the page is client-rendered and unfetchable, and the reseller channel that sells most Clover accounts is quote-only.

commercial-module-unbundling differentiator

App Market apps are individually subscribable and cancellable, but Clover's own plan bundles could not be inspected.

commercial-hardware-purchase-outright

Devices can be bought outright direct, but published SKU prices were not retrievable and reseller leases are common.

commercial-hardware-not-locked differentiator

Third-party peripherals are documented first-party: Star Micronics TSP143III thermal and SP742M / SP742ME impact order printers (Ethernet or Wi-Fi to the same router), Zebra DS9308 and other USB barcode scanners ('compatible with several external USB barcode scanners'), and CAS weight scales. The terminals themselves are Clover-only devices; the claim is satisfied by the non-proprietary printer and scanner options it names as examples. https://www.clover.com/en-US/help/connect-a-star-micronics-tsp143lll-printer-for-orders · retrieved 2026-09-03 adversarially verified

commercial-data-export-self-serve

Self-serve export exists through the REST API under merchant-granted read permissions across orders, payments, inventory, customers and employees. Shortfall — "Clover is now enforcing a 90-day window on calls to Payments and Orders API endpoints", so transactional history must be walked in 90-day slices, and no one-click bulk export of the full account is documented. https://docs.clover.com/dev/docs/limits-added-to-calls-to-payments-and-orders-endpoints · retrieved 2026-08-02

commercial-export-customer-and-loyalty differentiator

Guest data is exportable: "Read customers — Required to read customer information" under merchant-granted permission. Shortfall — no loyalty object exists anywhere in the documented data model, so loyalty balances, tiers and consent state have no documented export path at all. https://docs.clover.com/dev/docs/permissions · retrieved 2026-08-02

commercial-post-termination-export-window differentiator

2026-08-05 sweep with full help-centre text. Account closure is documented only as a support-assisted process (close-cancel-account, cancel-clover-account: contact live support with MID/TIN) with a step to 'Review contract and subscription terms'; the Annual Data Storage Fee article describes cloud storage during the relationship. No document states whether or how long data remains exportable after termination. The UK acquiring T&Cs PDF (read for a prior cell) is likewise silent on a retrieval window. Unknown stands.

commercial-data-ownership-clause differentiator

2026-08-05 sweep. The GDPR guide assigns roles informally (merchants are 'data controllers'; 'Section 8 of our Privacy Notice and Section 10 of our Merchant Terms detail how we handle data and the respective data roles') but the Merchant Terms themselves remain unreadable — clover.com/legal is a client-rendered JS application returning no document text — so whether published terms state merchant ownership and constrain Clover/Fiserv's use or resale of transaction and customer data cannot be verified. Unknown stands.

commercial-pci-p2pe-tokenization

Tokenisation is documented and first-party: the Clover iframe "returns a tokenized card for use with the Clover payment system", and TransArmor tokens replace cardholder data to reduce PCI scope. Shortfall — no PCI-listed P2PE solution is named, and merchants on their own domains remain "responsible for their own PCI compliance", with each domain "individually assessed". https://docs.clover.com/dev/docs/pci-dss-version-40-requirements-643-and-1161 · retrieved 2026-08-02

commercial-pci-dss-4-controls

PCI DSS v4.0 is addressed directly — requirements 6.4.3 and 11.6.1 are documented as mandated from 2025-04-01, with Clover's own compliance "validated by a Qualified Security Assessor (QSA)". Shortfall — the page describes what merchants and developers must do, not the control set Clover operates, and publishes no AOC or responsibility matrix. https://docs.clover.com/dev/docs/pci-dss-version-40-requirements-643-and-1161 · retrieved 2026-08-02

commercial-privacy-dsar-tooling

In-app DSAR tooling is documented for both regimes: 'your Clover device and dashboard provide a number of tools to help you fulfill the request' — locate the guest in the Customers app, then 'Access the customer's data; Edit the data...; Delete the customer's profile; Gather such information... with a tool that makes the data portable' — with a parallel CCPA guide (calif-consumer-privacy-act) and receipt-level privacy-policy links (EU receipts carry Clover's policy and link to the merchant's). Shortfall — no executable DPA is published (data-handling terms live in the Privacy Notice and unreadable Merchant Terms), the 'portable' export is not specified, and deletion propagation to rewards/marketing records is undocumented. https://www.clover.com/en-US/help/clover-supports-the-general-data-protection-regulation · retrieved 2026-08-05

commercial-wcag-kiosk-accessibility differentiator

No VPAT/ACR found for Clover Kiosk or Clover Online Ordering.

commercial-dual-pricing-compliant differentiator

Cash-discount and surcharge programs are widely deployed on Clover via resellers and App Market apps; native debit/prepaid BIN exclusion and disclosure handling are not documented.