Clover

Provides a graphical floor-plan editor where an operator can draw sections, place tables of varying shape/capacity, save multiple floor-plan layouts per location, and assign sections to servers.

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 lines can be tagged to a seat number at entry, and the check can be split by seat afterward without re-keying items.

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

Items can be assigned to courses and held, with a fire-next-course action available from a handheld or terminal that releases only that course to the kitchen.

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

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

order-capture-split-merge

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

Opens a bar tab against a card pre-authorization with a configurable auth amount, supports incremental re-auth as the tab grows, and auto-closes stale tabs at end of day. differentiator

order-capture-bar-tab-preauth

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

An open check can be transferred between servers, tables, and devices, and the transfer is recorded in an audit log naming both employees.

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

Ships a first-party handheld ordering app running natively on the handheld device (not a remote/mirrored desktop session) that can send to kitchen and take a card payment tableside.

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

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

order-capture-offline-order-entry

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

Guest QR at-table ordering writes items onto the same open check as server-entered items, rather than creating a separate order ticket. differentiator

order-capture-qr-same-check

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

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

order-capture-kiosk-first-party

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

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

order-capture-drive-thru

Clover's order-type doc (pub 2026-07-24) enumerates the restaurant set: "Order types give each order a specific purpose. For restaurants, you can set up order types for delivery, to-go, and dine-in purchases." An order type only surfaces "In the Register app at the start of an order" and on receipts - it is an accounting label, not a lane/window workflow. The 1,309-article Contentful census and docs.clover.com contain zero occurrences of drive-thru/drive thru. https://www.clover.com/en-US/help/create-rename-delete-order-types · retrieved 2026-09-05 adversarially verified

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

order-capture-drive-thru-timers

Clover's only speed-of-service report is closed-enumerated (pub 2026-07-03): "The Kitchen operations report displays metrics for KDS merchants and includes: 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." No order/total/window segment timers; zero drive-thru hits corpus-wide. https://www.clover.com/en-US/help/track-kitchen-operations · retrieved 2026-09-05 adversarially verified

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

order-capture-voice-ai

create-an-atomic-order is a generic single-call order-injection endpoint and never mentions voice. "voice" has zero hits across all 1,309 help articles, and in the complete 905-page developer mirror it appears only as the card-entry enum VOICE, voice authorization, and a biometrics list in privacy text. No first-party agent, no named voice partner, no voice-specific partner program. https://docs.clover.com/dev/docs/create-an-atomic-order · retrieved 2026-09-05 adversarially verified

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

order-capture-throttling

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

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

order-capture-scheduled-orders

Scheduling 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

Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.

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

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

order-capture-order-ready-signal

DoorDash publishes a machine-readable registry of its integration partners at https://merchants.doordash.com/api/partner-integrations — 64 providers, each tiered PREFERRED (12), CERTIFIED (47) or AT_RISK_OF_SUSPENSION (5), and each carrying an explicit true/false flag for 23 named integration features across four collections. It is served anonymously and merchants.doordash.com/robots.txt permits it. The programme is described, and its eight high-quality features defined in prose, at https://merchants.doordash.com/en-us/learning-center/doordash-preferred-integrations-program; the merchant-facing label for each flag comes from the label dictionary embedded in DoorDash's integrations comparison page. SCOPE: this attests the vendor's DOORDASH integration specifically — not Uber Eats, not Grubhub, and not the POS in general. DIRECTION: a true flag is a positive attestation; a false flag is NOT a reliable negative on its own, because Lavu's help centre documents a DoorDash temporary-closure control with scheduled auto-reopen while Lavu's `STORE_AVAILABILITY_WEBHOOKS` flag reads false, and Xenial's developer docs enumerate an order-ready notification while its `SUPPORT_ORDER_READY_SIGNAL` flag reads false. The flag `SUPPORT_ORDER_READY_SIGNAL` is TRUE for `clover`. DoorDash labels the flag 'Order ready signal' and defines it on the programme page as 'Order ready signal - Notifies Dashers when an order is ready for pickup to improve timing and coordination.' This corrects a `no` that generalised a single-marketplace answer to every marketplace: the evidence cited was Clover's UBER EATS FAQ, in which Clover says it does not send Uber Eats a food-ready update. That is sound about Uber Eats and silent about DoorDash — and the prior note's bridge to DoorDash conflated DoorDash DRIVE, a white-label courier product, with the DoorDash MARKETPLACE integration this registry covers. With one marketplace attested built and another vendor-attested absent, `partial` is the honest value. https://merchants.doordash.com/api/partner-integrations · retrieved 2026-09-12

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

order-capture-void-comp-controls

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

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

menu-pricing-nested-modifiers

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

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

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

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

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

menu-pricing-fractional-placement

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

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

menu-pricing-half-and-half-rule

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

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

menu-pricing-topping-quantity-tiers

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

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

menu-pricing-size-style-matrix

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

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

menu-pricing-included-allowance

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

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

menu-pricing-combos

Modifiers carry a name and a price, a group sets "minimum and maximum required modifiers" and is assigned to items, with a "Show upon order entry on POS" toggle - component swapping with a price delta, which is how a combo is built on Clover. Shortfall: there is no combo or meal entity, and nothing detects or converts eligible a-la-carte cart items to a combo price. https://www.clover.com/en-US/help/add-modifiers-and-their-modifier-groups · retrieved 2026-09-05 adversarially verified

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

menu-pricing-upsell-prompts

The reports overview (pub 2026-04-03) enumerates every Clover report - Employee sales, Item sales, Sales, Tender and card types, Removed items, Discounts, Order types, Gift cards, Kitchen operations, Guest count, Requested reports - with no attach-rate or upsell-conversion metric. Separately, no upsell/suggestive-sell/cross-sell prompt configuration appears anywhere in the 1,309-article census or the kiosk setting articles. https://www.clover.com/en-US/help/clover-reports-overview · retrieved 2026-09-05 adversarially verified

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

menu-pricing-86-propagation

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

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

menu-pricing-countdown-auto-86

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

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

menu-pricing-dayparting

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

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

menu-pricing-channel-price-books

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

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

menu-pricing-dual-pricing

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.

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

menu-pricing-allergen-nutrition

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 items and modifiers can be linked to recipes/bills of materials so that a sale depletes theoretical inventory and yields item-level theoretical food cost. differentiator

menu-pricing-recipe-linkage

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

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

menu-pricing-3p-menu-push

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

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

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

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

payments-processor-choice

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

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

payments-published-rates

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.

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

payments-dual-pricing

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

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

payments-surcharge-guardrails

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

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

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

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

payments-softpos-tap-to-pay

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

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

payments-pay-at-table

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

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

payments-qr-guest-pay

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

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

payments-tip-adjust

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

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

payments-tip-pooling

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

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

payments-offline-store-and-forward

"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

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

payments-offline-decline-liability

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

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

payments-gift-cards

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

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

payments-house-accounts

Clover enumerates its tenders (pub 2026-07-24): "Cash, Debit cards, Credit cards, Prepaid cards, Checks, Gift cards, EBT cards", then names the workaround and its limit: "If you accept a payment type that isn't already listed, such as store credit, you can add it as a custom tender type so those payments are tracked separately. No cards or account numbers are entered for custom tenders, and no funding is provided." No credit limit, running balance or statement run. https://www.clover.com/en-US/help/set-up-payment-methods · retrieved 2026-09-05 adversarially verified

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

payments-split-tender

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

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

payments-refund-void-controls

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

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

payments-chargeback-tooling

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

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

payments-card-on-file

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

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

payments-payout-timing

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

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

payments-p2pe-pci4

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

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

kitchen-station-routing

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

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

kitchen-expo-consolidation

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

Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator

kitchen-course-firing

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

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

kitchen-prep-time-pacing

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 load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator

kitchen-order-throttling

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

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

kitchen-channel-pause-propagation

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

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

kitchen-order-ready-callback

DoorDash publishes a machine-readable registry of its integration partners at https://merchants.doordash.com/api/partner-integrations — 64 providers, each tiered PREFERRED (12), CERTIFIED (47) or AT_RISK_OF_SUSPENSION (5), and each carrying an explicit true/false flag for 23 named integration features across four collections. It is served anonymously and merchants.doordash.com/robots.txt permits it. The programme is described, and its eight high-quality features defined in prose, at https://merchants.doordash.com/en-us/learning-center/doordash-preferred-integrations-program; the merchant-facing label for each flag comes from the label dictionary embedded in DoorDash's integrations comparison page. SCOPE: this attests the vendor's DOORDASH integration specifically — not Uber Eats, not Grubhub, and not the POS in general. DIRECTION: a true flag is a positive attestation; a false flag is NOT a reliable negative on its own, because Lavu's help centre documents a DoorDash temporary-closure control with scheduled auto-reopen while Lavu's `STORE_AVAILABILITY_WEBHOOKS` flag reads false, and Xenial's developer docs enumerate an order-ready notification while its `SUPPORT_ORDER_READY_SIGNAL` flag reads false. The flag `SUPPORT_ORDER_READY_SIGNAL` is TRUE for `clover`, which falsifies a prior `no` that reached DoorDash by way of Clover's Uber Eats FAQ and of DoorDash DRIVE, a courier product rather than the marketplace integration. The claim additionally requires that BUMPING AN ORDER READY ON THE KDS is what emits the event, and the registry carries no flag identifying the signal's trigger. A necessary condition is attested and a sufficient one is not. Clover's documented consumer of a KDS Mark Ready is its own kiosk SMS notification, which is suggestive but not exclusive. https://merchants.doordash.com/api/partner-integrations · retrieved 2026-09-12

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

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

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

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

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

kitchen-sla-alerts

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

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

kitchen-printer-fallback

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

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

kitchen-offline-operation

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

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

kitchen-item-build-screens

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

Sectioned/fractional topping placement (halves, quarters, specific sections) is rendered visually and unambiguously on the make-line screen or ticket. differentiator

kitchen-pizza-fractional-display

Upheld, and the prior rationale's premise ("no fractional placement exists in the menu model") is now measured rather than asserted. The complete published Modifier request schema is six fields -- `id`, `name`, `alternateName` ("Alternate name of the modifier"), `available`, `price` ("Additional cost when used") and `modifierGroup` -- with no section, position, fraction or placement attribute of any kind, so a half-and-half topping can only be carried as modifier TEXT. Across 1,309 help-centre documents (2.22M chars, the Contentful space's own task+topic census) and 905 developer-docs pages (13.6M chars), tokenised: `fractional` 0 in the help centre and 2 in the developer docs, both describing the int64 data type ("Whole number without a fractional component"); `topping` 0; `half and half` 0; `left half` 0; `split topping` 0. The KDS surface is documented only for setup, routing, power and troubleshooting -- no rendering rule for modifiers is published at all, and the Kitchen operations report measures prep times, not ticket layout. Recorded as a FLOOR on the schema side: `additionalProperties: false` occurs just 3 times across 905 developer pages, so the six-field list is the documented ceiling and not a logical one; the verdict rests on that plus the zero-hit vocabulary and the absence of any pizza-sectioning feature in Clover's own restaurant app-type table. Grade B: the vendor's own API reference. https://docs.clover.com/dev/reference/modifiercreatemodifier · retrieved 2026-09-09

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

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

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

kitchen-order-modification-alerts

CLAIM: edits made in the POS to an order already on the kitchen display visually flag added, changed or removed items on the live ticket. VERDICT: partial/B. NEW SURFACE: the help centre SPA's own Contentful GraphQL Delivery API (space vyqnxxjc374u, production token embedded in the public bundle cloverstatic.com/web/apps/web-help-center/release::v1.2.7-4c2d163ec17c1/assets/js/main.82ac065e.js; the SPA itself pages DESCENDANT_ROUTES over routeCollection anonymously). Census 2026-09-16: routeCollection total 1,523; 906 routes resolve to Task articles; 78 of those slugs are ABSENT from the Elastic App Search engine (1,119 docs) that every prior pass mined, so the App Search corpus was never a census of the help centre. Published assets: 722 (99 PDFs). EVIDENCE (manage-uber-eats-delivery-orders-on-POS (route-only; not in App Search; published 2026-06-19, limitedAudience null, no target audience; the live www.clover.com/en-US/help/manage-uber-eats-delivery-orders-on-POS is the 984-byte SPA shell that renders this entry)): cancelling from the POS: 'Open the Orders app and tap an active Uber Eats order ... tap Cancel Order. Enter your Owner, Admin, or Manager PIN ... Tap Cancel order. Once confirmed, on the Kitchen Display System (KDS), the ticket appears as Canceled with strike-through items, and a Void order receipt automatically prints.' and '(Optional) On the Kitchen Display System (KDS), tap Remove ticket for Canceled orders with strike-through items.' So removing an already-fired order at the POS shows on the live KDS ticket as struck-through items. SHORTFALL: documented only for whole-order cancellation of Uber Eats orders; no document describes items ADDED or CHANGED on a fired order, or removal of a single item, rendering on the KDS. CONTROLS: 'strike|struck|crossed' over the 906 Task routes: 1 doc (this one). The KDS suite (kds-other-settings, kds-configure-ticket-layout/-interaction/-timing, kds-kitchen-mode, kds-expo-mode, route-order-tickets-to-kds) says nothing about edits; 'Orders in Expo mode will update as they are prepared by the kitchen' describes prep status, not edits. POISON: kitchen-receipt-faqs ('Existing printed physical receipts are never modified; changes always result in a new paper artifact', with cancellation markers in Japanese) is the JAPAN printer article, not KDS; void-kitchen-receipts is paper only. Retrieved 2026-09-16. https://www.clover.com/en-US/help/manage-uber-eats-delivery-orders-on-POS · retrieved 2026-09-16 adversarially verified

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

kitchen-guest-ready-notification

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

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

kitchen-waste-logging

Clover stock adjustment is a bare count edit (pub 2026-04-21): "Select Edit stock count and enter the available stock quantity" and on the Items page "select the stock count number and update" - no reason code, no waste or spoilage entity. The census has zero occurrences of spoilage or remake, and the only 'waste' hit is a printer article about wasting paper. No KDS article offers any logging action beyond marking items complete. https://www.clover.com/en-US/help/manage-stock-count-and-low-stock-threshold · retrieved 2026-09-05 adversarially verified

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

kitchen-speed-of-service-reporting

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

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

kitchen-prep-forecasting

The reports overview (pub 2026-04-03) lists all eleven Clover report types - Employee sales, Item sales, Sales, Tender and card types, Removed items, Discounts, Order types, Gift cards, Kitchen operations, Guest count, Requested reports - none of which is a prep list or predicted prep quantity. Zero occurrences of 'prep list' or 'par level' in the 1,309-article census; the only forecasting language is a Sales Trends line about spotting patterns to "forecast future growth". https://www.clover.com/en-US/help/clover-reports-overview · retrieved 2026-09-05 adversarially verified

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

delivery-driver-roster

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

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

delivery-dispatch-board

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

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

delivery-route-map

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

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

delivery-driver-tracking

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 areas can be defined as arbitrary map polygons or by drive-time isochrones, not solely as a radius or a ZIP/postcode list. differentiator

delivery-zones-polygon

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

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

delivery-zone-pricing

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

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

delivery-address-validation

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

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

delivery-driver-comp

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

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

delivery-cash-reconcile

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

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

delivery-daas-dispatch

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

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

delivery-daas-fallback

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

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

delivery-3p-direct-integration

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

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

delivery-3p-injection

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

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

delivery-menu-push

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

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

delivery-86-sync

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

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

delivery-store-pause

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

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

delivery-3p-reconciliation

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

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

delivery-injection-error-visibility

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

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

delivery-tracking-page

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

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

delivery-promise-time

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

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

delivery-offline-behavior

CLAIM: vendor DOCUMENTS explicit offline behaviour for delivery - whether cash delivery orders, driver assignment and driver settlement continue during an internet outage. VERDICT: no; this is a documentation claim and the documentation does not exist on a bounded corpus. NEW SURFACE (327th): 905/905 pages of https://docs.clover.com/dev/llms.txt (adds the 309-page /dev/reference REST API reference, first census; 0 shells, 25.6 MB, nonsense-path control passed) re-grepped with the 1,119-article clover.com/help body corpus for this cell, which had never been checked against either. EVIDENCE: the intersection of 'offline' with 'delivery' across 1,119 help articles is TWO articles and both are about ONLINE-ordering printing, not delivery continuity: 'What if my remote device or printer is offline? Orders may not print if your remote device or printer is disconnected or offline. If your remote device is offline, you won't receive notifications for online orders, and your remote firing option will not work' (olo-manage-order-printing, olo-manage-order-printing-). That is the opposite of a continuity statement, and it is about printing, not cash delivery orders, driver assignment or driver settlement. On the dev side 'dispatch' hits 1 of 905 pages (a 3DS SDK topic) and 'driver' 32 pages, all of them the `driver` field of the payment/card object in the Orders and Payments API schemas - POISON NAMED: `driver` in this corpus is a PAYMENT-DRIVER string, not a delivery driver. Clover's only published outage behaviour is payment-scoped ('devices can take offline payments for up to 7 days ... This functionality doesn't work with Electronic Benefit Transfer (EBT) or gift cards', set-up-offline-payments) and delivery is absent from that enumeration in both directions. POSITIVE CONTROLS on the same corpora: 'offline' 35 help / 86 dev, 'DoorDash' 23 help, 'Order with Google' 8 help. Retrieved 2026-09-18. https://www.clover.com/en-US/help/set-up-offline-payments · retrieved 2026-09-18 adversarially verified

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

digital-first-party-web

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

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

digital-menu-single-source

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

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

digital-native-app

"Customers can immediately start ordering through your dedicated web page or the Clover consumer app." Clover's OLO topic (2026-09-01) enumerates both first-party consumer surfaces: a branded web PAGE and the shared Clover consumer app (help/get-the-clover-app: one app used to “get rewarded at your favorite businesses”). No merchant-branded native iOS/Android app. https://www.clover.com/en-US/help/set-up-online-ordering · retrieved 2026-09-05 adversarially verified

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

digital-account-saved-payment

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 checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator

digital-upsell-engine

"Clover offers a variety of reports to help you track, monitor, and analyze business performance." Then it enumerates them: Employee sales, Item sales, Sales, Tender and card types, Removed items, Discounts, Order types, Gift cards, Kitchen operations, Guest count, Requested. None reports suggestion attach rate, and upsell/cross-sell/suggested-item appear in no ordering article. https://www.clover.com/en-US/help/clover-reports-overview · retrieved 2026-09-05 adversarially verified

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

digital-scheduled-pacing

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

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

digital-fulfillment-modes

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

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

digital-qr-table

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

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

digital-kiosk

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

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

digital-group-ordering

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

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

digital-catering-portal

"You can fulfill online orders in the following ways:" The closed list is In-store pickup, Curbside pickup, Delivery through DoorDash drive (U.S. only), and Dine-in scan-to-order. No catering flow, minimums, lead-time rules, quotes, deposits or house accounts; “catering” occurs in zero of the 1,309 help articles. https://www.clover.com/en-US/help/manage-additional-online-ordering-options · retrieved 2026-09-05 adversarially verified

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

digital-voice-ai-phone

"Create the order using Bar & More, select Takeout or Delivery, add the items, and complete payment as usual." That is Clover's documented answer to “How do I take a phone order for delivery or takeout?” — staff transcription into Register/Dining. No AI voice answering, native or named partner, anywhere in the corpus or dev docs. https://www.clover.com/en-US/help/take-non-table-orders-with-the-Clover-Dining-app · retrieved 2026-09-05 adversarially verified

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

digital-drivethru-ai

"Contactless dining (QR-code ordering)" The QSR bundle matrix enumerates order management as QR-code ordering, item/order-level discounts, remote order firing and line busting. No drive-thru of any kind; “drive-thru”/“drive thru” appear in zero help articles and zero dev docs. https://www.clover.com/pricing/quick-service-restaurant · retrieved 2026-09-05 adversarially verified

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

digital-sms-ordering

"You can send announcements through text message, email, and push notifications" Clover's SMS surface is outbound only: announcements and promos from the dashboard, on a toll-free number provisioned as either promotions-related or transactional (toll-free-number-faqs). No text-to-order or conversational reordering path into the POS. https://www.clover.com/en-US/help/send-announcements · retrieved 2026-09-05 adversarially verified

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

digital-google-order

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

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

digital-apple-business-connect

CLAIM: supports Apple Business Connect ordering placement - an 'Order Food' custom action on the Apple Maps place card pointing at Clover's first-party ordering flow. VERDICT: no. NEW SURFACE (327th): docs.clover.com/dev censused to 100% of the PUBLISHER'S OWN INDEX. llms.txt (https://docs.clover.com/dev/llms.txt) lists 905 .md pages; all 905 fetched via the ReadMe `.md` suffix, 0 HTML shells, 25,594,425 bytes. This adds the 309-page /dev/reference REST API reference, which the 326th's 582-page /dev/docs census did not cover (582 + 309 + 14 = 905). Nonsense control: https://docs.clover.com/dev/reference/zzz-nonsense.md returns the ReadMe SPA shell, so a 200 markdown body is discriminated from a soft 200. EVIDENCE (tokenised, word-boundary, case-insensitive, run over THREE corpora): 'Apple Business Connect' 0 / 'Apple Maps' 0 / 'place card' 0 in (a) the 905-page dev corpus, (b) the 1,119-article clover.com/help body corpus (.cache/q319/clover/docs.json, 1,700,773 chars of prose), and (c) the ENTIRE www.clover.com Contentful space v6ivjcl8qjz2, 11,832 entries / 6,630,316 chars - the publisher that would announce a marketing channel. POSITIVE CONTROLS on the same corpora prove the regex and the corpora: 'Order with Google' help 8 docs / mktg 13 ('Order with Google: Open a new channel for more orders and enable customers on Google to find, order, and reorder from you', sign-up-with-partner); 'Google Business Profile' help 2 / mktg 1; 'Yelp' help 1 / mktg 10; 'DoorDash' help 23 / mktg 19. So Clover enumerates its discovery/ordering channels and Apple is not among them. POISON NAMED: the only Apple-Maps-adjacent Clover text is a 2023 blog post '4 reasons you should list your business with Apple Maps' (held at .cache/q319/clover/blog-4-reasons-you-should-list-your-business-with-apple-maps.html) - generic advice about claiming a Maps listing, not an ABC ordering action, and it is a blog (grade C) not a product surface. BOUND CAVEAT: the help corpus is the 1,119-doc App Search set; the 319th recorded 78 route-only slugs absent from it, so the help side is a floor - but the marketing Contentful space is a full CDA dump and the dev corpus is 905/905 of the publisher's own index. Retrieved 2026-09-18. https://docs.clover.com/dev/llms.txt · retrieved 2026-09-18 adversarially verified

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

digital-loyalty-attach

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

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

digital-subscriptions

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

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

digital-promo-parity

"Discounts and promotions are not supported for Clover online ordering. Any discounts configured in Clover apply only at the register or supported in‑person workflows, not to online orders placed through the OLO experience." OLO FAQ, 2026-08-27. Loyalty is the one exception: logged-in consumers can redeem rewards on web orders. https://www.clover.com/en-US/help/online-ordering-faqs · retrieved 2026-09-05 adversarially verified

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

digital-guest-data-ownership

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

digital-checkout-pci-sca

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

digital-surcharge-transparency

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

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

guest-loyalty-unified-profile

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

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

guest-loyalty-thirdparty-identity-attach

CLAIM: marketplace orders (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. VERDICT: partial/B, weak. NEW SURFACE: the help centre SPA's own Contentful GraphQL Delivery API (space vyqnxxjc374u, production token embedded in the public bundle cloverstatic.com/web/apps/web-help-center/release::v1.2.7-4c2d163ec17c1/assets/js/main.82ac065e.js; the SPA itself pages DESCENDANT_ROUTES over routeCollection anonymously). Census 2026-09-16: routeCollection total 1,523; 906 routes resolve to Task articles; 78 of those slugs are ABSENT from the Elastic App Search engine (1,119 docs) that every prior pass mined, so the App Search corpus was never a census of the help centre. Published assets: 722 (99 PDFs). EVIDENCE (manage-uber-eats-delivery-orders-on-POS (route-only; not in App Search; published 2026-06-19, limitedAudience null, no target audience; the live www.clover.com/en-US/help/manage-uber-eats-delivery-orders-on-POS is the 984-byte SPA shell that renders this entry)): Uber Eats orders are NOT anonymous on the POS: 'On the Order detail view, locate the customer information in the Online Order Details section. View the customer's first and last name, phone number, and the Contact PIN, displayed as a formatted code' and 'you can find their masked contact information directly on your Clover device. To protect customer privacy, this contact information is securely purged from the system two months after the order is placed.' SHORTFALL (the core conjunct): the identity sits on the order, as a masked relay phone plus PIN, and is purged after two months. Nothing says the order is attached to, or creates, a record in Clover's Customers database, so no native profile attach is documented, and the purge argues against one. Only Uber Eats is documented: manage-doordash-orders- (route-only) has an empty body, and online-grubhub- has only fee, URL and QR text. A verifier may fairly hold this at unknown, since it meets 'not anonymous' for one marketplace only. Retrieved 2026-09-16. https://www.clover.com/en-US/help/manage-uber-eats-delivery-orders-on-POS · retrieved 2026-09-16 adversarially verified

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

guest-loyalty-accrual-models

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

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

guest-loyalty-tiers

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

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

guest-loyalty-offline-behavior

CLAIM: DOCUMENTS EXPLICITLY what loyalty lookup, accrual and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). VERDICT: no - the claim is a documentation claim, and on a bounded corpus Clover publishes nothing on it. NEW SURFACE (327th): the 905/905 docs.clover.com/dev census (llms.txt manifest; adds the 309-page /dev/reference API reference the 326th did not hold) re-grepped together with the 1,119-article clover.com/help body corpus, which this cell had never been checked against. EVIDENCE: the intersection of 'offline' with 'loyalty' is ZERO across all 1,119 help articles, although both tokens are abundant separately - POSITIVE CONTROLS: 'offline' 35 help docs / 126 hits, 'loyalty' 40 help docs / 707 hits. Clover's entire published offline story is payment-scoped and enumerates exactly what is in and out of it: 'You can continue to take payments when you're not connected to the internet by turning on the Offline Payments option. Payments are processed as soon as you're back online and logged in ... devices can take offline payments for up to 7 days ... This functionality doesn't work with Electronic Benefit Transfer (EBT) or gift cards' (set-up-offline-payments; accept-offline-payments repeats it). That is an ENUMERATION of the offline-capable tender path and loyalty is not in it, in either direction. On the dev side, 'loyalty' appears in 10 of 905 pages (custom-tenders, app permissions, device build guides) and none of them states an offline behaviour. BOUND: 905/905 of the publisher's own dev index, 0 shells, 25.6 MB, nonsense-path control passed; plus 1,119 help bodies (a floor - 78 route-only slugs unfetched - but the offline articles themselves are held and are silent). Retrieved 2026-09-18. https://www.clover.com/en-US/help/set-up-offline-payments · retrieved 2026-09-18 adversarially verified

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

guest-loyalty-offer-stacking-rules

The Discounts app entity is a closed field list - a name and either a percentage or an amount - with no exclusive-vs-combinable flag, no precedence order and no channel eligibility. Stacking exists only as fixed system behaviour ("the system applies the item discounts first"), which is the opposite of the configuration the claim asks for. https://www.clover.com/en-US/help/set-up-discounts-in-Discounts-app · retrieved 2026-09-05 adversarially verified

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

guest-loyalty-targeted-offers

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

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

guest-loyalty-rfm-segmentation

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

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

guest-loyalty-lifecycle-automation

Always-on 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

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

guest-loyalty-native-email-sms

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

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

guest-loyalty-consent-management

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

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

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

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

guest-loyalty-campaign-attribution

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

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

guest-loyalty-data-export-portability

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

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

guest-loyalty-review-capture-routing

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

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

guest-loyalty-referral-program

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

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

guest-loyalty-wallet-pass

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

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

guest-loyalty-privacy-rights-tooling

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

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

guest-loyalty-redemption-fraud-controls

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

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

guest-loyalty-ai-offer-recommendation

CLAIM: vendor documents AI/ML-generated recommendations for offer CONTENT, target AUDIENCE, or SEND TIMING, as a shipped feature. VERDICT: no. This is NOT an absence of AI - Clover ships two named, documented AI features, and neither one takes up this claim. NEW SURFACE (327th): the 1,119-article clover.com/help body corpus re-grepped for AI vocabulary (this cell had never been checked against it) plus the 905/905 docs.clover.com/dev census. (1) INSIGHTS: 'Insights is an analytics hub in the Clover dashboard ... It combines real-time performance metrics, visual dashboards, and an AI-powered assistant ... with daily summaries, peer benchmarking, and personalized recommendations' (getting-started-with-insights). Its recommendations are OPERATOR ACTIONS, not marketing offers: 'Under Recommended actions for you, review personalized recommendations based on your business data, such as improving order size or expanding to online ordering' (create-and-manage-insights), and 'Recommendations are generated using your business data and comparisons to similar merchants to highlight opportunities for growth or improvement' (insights-faqs). It is also single-location-only and US-only: 'Can I use business insights for multiple locations? No.' (2) VERA: 'Vera is an AI chatbot originally designed for help and support that now also helps you find and open Clover reports with the right filters applied ... Vera does not generate new calculations, charts, or tables directly in chat' (Find-Clover-reports-with-Vera). POISON NAMED: 'personalized recommendations' is a HOMONYM of this claim - it recommends what the OPERATOR should do, not what OFFER to send, to whom, or when. CONTROLS (tokenised, word-boundary, case-insensitive) over help(1,119 docs) / dev(905) / www.clover.com Contentful (11,832 entries): 'target audience' 0/0/0, 'send time' 0/0/0, 'best time to send' 0/0/0, 'AI-generated offer' 0/0/0, 'artificial intelligence' 0/0/0, 'Clover Assistant' 0/0/0; 'segment' 0/1/1, 'audience' 2/1/13 (none about offer targeting), 'campaign' 1/0/16. 'AI' appears in exactly 7 help articles, all of them Insights (5), the digital-menu item-list generator, and Vera; 'machine learning' has one marketing hit and it is the Terms and Conditions of Use disclaimer ('GIVEN THE PROBABILISTIC NATURE OF MACHINE LEARNING, THE CLOVER SERVICES MAY IN SOME SITUATIONS PRODUCE OUTPUT THAT IS INACCURATE...'), i.e. a liability clause, not a feature. POSITIVE CONTROLS on the same corpora: 'Order with Google' help 8, 'DoorDash' help 23, 'loyalty' help 40. Retrieved 2026-09-18. https://www.clover.com/en-US/help/insights-faqs · retrieved 2026-09-18 adversarially verified

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

guest-loyalty-stored-value-gift

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

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

labor-clock-in-at-pos

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

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

labor-photo-punch-verification

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

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

labor-offline-time-punch

NEW SURFACES 2026-09-16, still silent. NEW SURFACE: the help centre SPA's own Contentful GraphQL Delivery API (space vyqnxxjc374u, production token embedded in the public bundle cloverstatic.com/web/apps/web-help-center/release::v1.2.7-4c2d163ec17c1/assets/js/main.82ac065e.js; the SPA itself pages DESCENDANT_ROUTES over routeCollection anonymously). Census 2026-09-16: routeCollection total 1,523; 906 routes resolve to Task articles; 78 of those slugs are ABSENT from the Elastic App Search engine (1,119 docs) that every prior pass mined, so the App Search corpus was never a census of the help centre. Published assets: 722 (99 PDFs). 'offline' hits 35 Task docs, and none concerns shifts or clock-in. The Local Connect Network Set-Up Guide PDF scopes offline operation to firing orders only: 'Orders created at front of house devices such as the Clover Mini or Station Duo will be fired to the Clover Kitchen Display System immediately even when the Internet connection is down'. In the Clover Android SDK source (api.github.com tree fc25a64c, 1,355 files), the offline paths are payments (EXTRA_ALLOW_OFFLINE_ACCEPTANCE), refunds (addRefundOffline) and order deletes ('adding message to server queue'); there is no offline employee or shift method. Retrieved 2026-09-16. || 322nd: NEW SURFACE 2026-09-17: PUBLIC SOURCE MAPS of Clover's merchant web dashboard. The web-portal app registry (85 apps, .cache/q319/clover/apps-config.json) serves every app from cloverstatic.com/web/apps/<app>/<release>/ (entry asset-manifest.json or Module Federation remoteEntry.js), and every bundle's .js.map is anonymous: 1,944 JS bundles fetched, 1,894 maps (per-app misses in .cache/q322/clover/dl-summary.json), 43,083 unique first-party source files once node_modules is dropped. The web-portal i18n namespaces are also public at cloverstatic.com/web/apps/web-portal/release_21Aug2026ServerWebCut-476fd2c5b435c/assets/locales/en/<ns>.json (22 of the 26 namespaces referenced in source return 200). These are production release builds (release names dated Aug-Sep 2026). Grade B as vendor-shipped code, but they cover the WEB DASHBOARD only, not the Android POS apps, the Clover Go app or the help centre, so they cannot bound a 'no' about device behaviour. No login and no backend calls. web-app-shifts (12 maps, none missing, 1,121 sources): the shift settings page (pages/SettingsPage/SettingsPage.tsx) exposes only two merchant properties, 'logInClockInPrompt' and 'allowClockOutWithOpenOrders'. Shift edits write overrideInEmployee/overrideInTime/overrideOutEmployee/overrideOutTime (utils/shiftReport.tsx). 'offline' has 0 hits in the app's own sources. Every user-facing 'offline' string across all bundles concerns offline PAYMENTS (per-payment and cumulative limits, 'Allow pending offline transaction during closeout', declined offline payments) or multi-location maintenance. None concerns time punches. Punch behaviour lives in the Android Employees app, which this corpus does not cover. Retrieved 2026-09-17. || 327th: NEW SURFACE (327th), cell deliberately held. The /dev/reference REST API reference (309 pages, censused for the first time - part of the 905/905 llms.txt pull) publishes the full Shifts object: employeecreateshift, employeegetemployeeshift(s), employeeupdateshift, employeedeleteshift, merchantgetshift, merchantgetallshifts. 'clock in' appears in 6 dev pages, all six of them those shift endpoints, so the POS-clock vocabulary IS in the corpus. What is absent is any offline statement about it: across the 905 dev pages and the 1,119 help bodies, the intersection of 'offline' with 'clock in|time clock|shift' is ONE article and it is about payment batching, not punches ('If your device temporarily loses connectivity, Clover may store transactions offline and process them later', difference-between-sales-activity-and-statements-faqs). Clover's offline documentation is payment-scoped and device-enumerated: 'The offline payments option is device specific ... When enabled, devices can take offline payments for up to 7 days ... enabled by default for: Clover Station, Station 2, Clover Mini, Flex, Mobile' with per-device and total dollar limits, and 'This functionality doesn't work with Electronic Benefit Transfer (EBT) or gift cards' (set-up-offline-payments). Time punches are in neither the enabled nor the excluded list. Held unknown rather than scored no because the claim's primary conjunct is a CAPABILITY (punches recorded offline and reconciled without loss or duplicates) and a payment-scoped silence does not bound an on-device Android app's local behaviour. Retrieved 2026-09-18. || 330th: 330th: NEW SURFACE, CELL STILL HELD (no move). The published Clover Android SDK API REFERENCE is a Dokka site whose own index file is a complete member manifest: https://clover.github.io/clover-android-sdk/scripts/pages.json, 34,829 entries over the four published modules (clover-android-sdk, clover-android-connector-sdk, clover-android-loyalty-kit, clover-android-sdk-retrofit), fetched anonymously 2026-09-18 (975 KB). Prior passes read the SDK's SOURCE on GitHub; nobody had held the publisher's own enumeration of what the SDK exposes. TWO MEASUREMENTS ON IT. (1) The Shift object is published in full and has no offline/queue/sync surface: com.clover.sdk.v3.employees.Shift has exactly 62 indexed members and its whole data model is id, employee, inTime, outTime, overrideInEmployee, overrideInTime, overrideOutEmployee, overrideOutTime, cashTipsCollected, serverBanking (plus the generic has*/clear*/isNotNull*/mergeChanges/validate scaffolding every Clover model gets). (2) The SAME SDK models offline origination explicitly where it exists, which is what makes the silence informative rather than merely absent: 'offline' matches 225 indexed members, and they fall in com.clover.sdk.v3.device (75: setOfflinePayments, setOfflinePaymentsAll, setOfflinePaymentsLimit, setMaxOfflineDays, getShowOfflinePayments), remotepay (46), order (30, incl. TimedSession.getCreatedOfflineOriginated and ItemEntitlementSession.getCreatedOfflineOriginated), payments (24, incl. Payment.getOffline, CardEntryType.OFFLINE_KEYED/OFFLINE_SWIPED, Result.OFFLINE_RETRYING, TransactionSettings.getAllowOfflinePayment/getForceOfflinePayment), pay, payment.raw.model, report and merchant — and in com.clover.sdk.v3.employees, ZERO. Poison checked: 'offline' inside onlineorder.OnboardingStatus.OFFLINE is a merchant-onboarding state, not a device state; the report-package hits are offline-payment report rows. THIRD, A HELP-CENTRE SENTENCE NOT PREVIOUSLY RECORDED, which is the closest Clover comes to describing where a punch is recorded: 'Record when your employees clock in, when they clock out, and the duration of their shifts, based on the time set on your Clover device' (https://www.clover.com/en-US/help/set-up-login-methods-for-shift-workers, the complete Shifts-app clock-in/clock-out procedure; the Time Clock articles in the corpus are Homebase's product, a third party). WHY STILL UNKNOWN: this bounds the PUBLISHED data model and the published procedure, not the Shifts app's on-device storage during a WAN outage, and the claim's conjuncts (punches recorded offline, reconciled without loss or duplicates, behaviour documented) are neither affirmed nor denied anywhere Clover publishes. Under the standing rule that 'never affirmed' is not a no on offline behaviour, held. Retrieved 2026-09-18. adversarially verified

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

labor-granular-rbac

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

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

labor-manager-override-audit

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

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

labor-native-scheduling

'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

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

labor-demand-labor-forecast

"Estimated labor costs are calculated using:" scheduled hours, assigned wage rates, unpaid breaks — no sales history. The closed “What can I do with Scheduling? You can:” list (create/assign/publish, availability, time off, labor costs, duplicate, pinned events, communicate) has no forecast or recommended staffing. Homebase-powered, not native. https://www.clover.com/en-US/help/scheduling-by-homebase-faqs · retrieved 2026-09-05 adversarially verified

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

labor-realtime-labor-percent

"No. Scheduling is available only through the Clover dashboard." Labor cost exists only as an estimate from scheduled hours, wage rates and unpaid breaks — no sales denominator and no actual punches — and it is not on the device. Clover's reports overview enumerates eleven reports and none is a labor report. https://www.clover.com/en-US/help/scheduling-by-homebase-faqs · retrieved 2026-09-05 adversarially verified

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

labor-overtime-prevention

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

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

labor-break-compliance-by-state

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

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

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

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

labor-tip-pooling-rules

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

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

labor-tip-distribution-audit-trail

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

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

labor-qualified-tips-w2-reporting

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

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

labor-native-payroll

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

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

labor-payroll-export-formats

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

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

labor-shift-swap-workflow

"Manage employee availability" The closed “What can I do with Scheduling? You can:” list is create schedules, assign shifts, publish, manage availability, manage time off, monitor labor costs, duplicate, pinned events, communicate. Employees receive notifications only; no swap request, no open-shift claim, no approval workflow. Homebase-powered, not native. https://www.clover.com/en-US/help/scheduling-by-homebase-faqs · retrieved 2026-09-05 adversarially verified

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

labor-server-performance-metrics

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

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

inventory-recipe-bom-costing

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

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

inventory-unit-conversion-yields

Upheld, and now measured against the item schema rather than inferred. Clover's inventory Item carries exactly ONE unit field -- `unitName`, "Unit of measurement for the item, such as pound or meter" -- one flat `cost` integer, and an `itemStock` object holding a stock quantity (`stockCount` is documented as "Deprecated. Use itemStock."). There is no purchase unit, no recipe unit, no count unit, no conversion factor and no yield or waste percentage anywhere in the model. Across 1,309 help-centre documents (2.22M chars, the Contentful space's own task+topic census) and 905 developer-docs pages (13.6M chars), tokenised with word boundaries: `unit conversion` 0, `yield` 2 in the help centre and 1 in the developer docs and ALL THREE are false friends (Annual Percentage Yield on Clover Savings; a currency-rounding page), `recipe` 0 in the help centre and 4 in the developer docs, every one of them a code "Recipe" example. Matcher proven in the same runs: `clover` matched 1,304 of 1,309 and 905 of 905, a nonsense control 0. Note the specs are a FLOOR and not a ceiling -- `additionalProperties: false` appears just 3 times across 905 developer pages -- so this rests on the affirmative single-unit model plus Clover's own routing of the capability to third parties (see inventory-theoretical-vs-actual). Grade B: the vendor's own API reference. https://docs.clover.com/dev/reference/inventorycreateitem · retrieved 2026-09-09

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

inventory-theoretical-vs-actual

Upheld, and the prior rationale's aside -- "requires an App Market partner" -- turns out to be Clover's own published position, which is a much better citation than an absence. The developer guide's table of app types to BUILD for quick-service restaurants lists "Recipe-based inventory | Track inventory based on the components that make up a menu item." Clover documents recipe-based inventory as a gap for outside developers to fill, not as a platform feature. The measurement agrees: across 1,309 help-centre documents (2.22M chars, the Contentful space's own task+topic census) and 905 developer-docs pages (13.6M chars), tokenised, `theoretical` occurs ZERO times, `variance` once (unrelated), `food cost` 0, `bill of materials` 0, and `recipe` never once in a stock-control sense. Without a recipe the theoretical-usage side of the report has no input, and no report joining counts plus receipts against sales-times-recipe is documented in either surface. Grade B: the vendor's own developer documentation. https://docs.clover.com/dev/docs/merchant-needs · retrieved 2026-09-09

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

inventory-realtime-depletion

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

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

inventory-86-auto-sync

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

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

inventory-count-modes

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

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

inventory-mobile-count-offline

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

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

inventory-vendor-catalogs-edi

The platform data model enumerates its categories: "The Clover Platform REST API and Clover Android SDK provide access points for retrieving and working with data in several categories" - Merchants, Employees, Customers, Inventory, Orders, Payments. There is no vendor, supplier, purchase-order or receiving entity. The 1,309-article help census returns zero hits for "purchase order", "Sysco", "broadline" or "EDI"; the only vendor-facing surface is Pay Bills by Melio (accounts payable). https://docs.clover.com/dev/docs/clover-data-model · retrieved 2026-09-05 adversarially verified

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

inventory-invoice-ocr

The only documented bill-ingest flow is accounts payable, not inventory: "You can add a bill manually, upload a bill, or sync your QuickBooks online account", then "Manually enter the details and upload the bill." The uploaded file is an attachment to a manually keyed bill under Finances > Pay bills; no line-item (item/quantity/unit/price) extraction is described and nothing posts to the inventory ledger. https://www.clover.com/en-US/help/pay-bills · retrieved 2026-09-05 adversarially verified

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

inventory-price-change-alerts

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

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

inventory-par-auto-suggest

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

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

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

Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.

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

Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting.

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

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

inventory-cogs-gl-export

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

inventory-native-not-partner

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

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

inventory-menu-margin-linkage

OVERTURNED from `no`. The prior rationale -- "Without recipe cost there is no native contribution-margin-per-item report" -- does not follow, and the report exists. The Item Sales report publishes per-item Gross Profit ("Projected profits, based on items with a defined cost; appears only for revenue items", "Gross profit equals net sales minus cost of goods sold") and Gross Profit Margin ("Gross profit margin percentage equals (Net sales minus the cost of goods sold) divided by net sales and multiplied by 100"), alongside a COGS column -- "Your cost of goods sold (COGS); appears only for revenue items" -- computed as "net sold quantity multiplied by the individual cost for each item". That is margin per menu item joined to actual sales mix. `partial`, not `yes`, on both remaining halves of the claim: the cost input is a flat per-item `cost` field on the inventory Item ("Cost of the item to a merchant as compared to the price payable by the customer"), NOT a recipe roll-up, and Clover says so itself in the caveat -- "The gross profit number is higher than it should be if you have items without a defined cost in your inventory"; and nothing flags an item whose margin fell below a configured threshold after an ingredient cost change -- `contribution margin` and `menu engineering` are each ZERO across both corpora, and the 22 `threshold` hits in the help centre are stock-level and other operational thresholds, none of them a margin alert. Grade B: the vendor's own help documentation, retrieved through the Contentful CDA the help centre renders from (the HTML address is a 984-byte JavaScript shell). https://www.clover.com/en-US/help/understand-item-sales-report-information · retrieved 2026-09-09

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

reporting-realtime-dashboard

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

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

reporting-eod-closeout

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

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

reporting-pmix-modifier-level

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

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

reporting-comps-voids-audit

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

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

reporting-cash-over-short

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

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

reporting-labor-productivity

Two closed enumerations settle it: the reports overview lists all eleven report types and none is a labor report, and Scheduling by Homebase computes "estimated labor costs based on scheduled hours, assigned wage rates, and unpaid breaks" - no punch data and no sales figure. Track sales by employee gives sales by employee, never against hours. https://www.clover.com/en-US/help/clover-reports-overview · retrieved 2026-09-05 adversarially verified

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

reporting-server-scorecards

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

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

reporting-channel-profitability

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

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

reporting-scheduled-delivery

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

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

reporting-public-api

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

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

reporting-webhooks

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

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

reporting-api-not-upcharged

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

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

reporting-tier-paywall

Detailed sales reporting is NOT paywalled for restaurants - the restaurant and QSR pricing tables render "Real-time sales tracking, Detailed sales reports, Tax reporting, Cost tracking by item" as Included on all three tiers. Shortfall: "Locations with the Starter plan will not have multi-location capabilities or be part of multi-location groups", and Insights and Scheduling require Essentials or above. https://www.clover.com/en-US/help/multi-location-faqs · retrieved 2026-09-05 adversarially verified

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

reporting-history-retention

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

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

reporting-anomaly-alerts

Operator-configured threshold alerting exists, but only for inventory: a low stock threshold is set per item and "Select or clear the Email or Mobile push checkboxes to set your notification preferences." Three alert types are documented - an immediate email, a weekly summary email, and a mobile push. Shortfall: no void-spike, discount-rate or sales-below-expectation alerting is documented anywhere in the 1,309-article help census; the only other notifications are dispute and system-status. https://www.clover.com/en-US/help/receive-low-stock-alerts · retrieved 2026-09-05 adversarially verified

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

reporting-nl-query

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

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

reporting-guest-cohorts

Guest-level 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

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

reporting-sales-forecast

The reports catalogue - "This guide provides an overview of the different types of reports available, how to interpret their data, and best practices for using these insights" - lists Employee sales, Item sales, Sales, Tender and card types, Removed items, Discounts, Order types, Gift cards, Kitchen operations, Guest count and Requested reports. Every one is retrospective; the Trends report is for comparing past and current performance. No forward daypart or hourly forecast is produced. https://www.clover.com/en-US/help/clover-reports-overview · retrieved 2026-09-05 adversarially verified

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

reporting-tip-tax-compliance

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

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

multi-location-org-hierarchy

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

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

multi-location-central-menu-publish

'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

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

multi-location-price-zones

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

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

multi-location-consolidated-reporting

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

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

multi-location-cross-location-giftcard

CLAIM: gift cards issued at one location are redeemable at any other location in the brand, WITH a reported outstanding-liability balance AND inter-store settlement/redemption reconciliation between owners. VERDICT: partial - the liability-reporting conjunct is documented; the cross-location and inter-store-settlement conjuncts are not. NEW SURFACE (327th): the /dev/reference API reference (309 pages, first census) plus a re-grep of the 1,119-article help body corpus for this cell, which had never been checked against it. LIABILITY CONJUNCT - SATISFIED: 'If you need the remaining balance of your outstanding gift cards for your business, you can view and download the report on the Gift Cards dashboard. This report is also referred to as the gift card liability report ... Select the Transactions tab. Select Generate Liability Report ... The Gift Card Liability report for your business downloads as a comma-separated value (CSV) format spreadsheet' (help: check-outstanding-gift-card-balance-liability-report). The Gift Card API is first-party and real-time: activation, balanceinquiry, redeem, reload, cashout, refund/void are published endpoints at docs.clover.com/dev/reference, and 'Clover native gift cards use the Clover-integrated Gift Card Solution, managed through the Fiserv payment gateway' (dev: gift-card-api). CROSS-LOCATION CONJUNCT - NOT DOCUMENTED: Clover has an extensive documented Multi-location dashboard (consolidate-employees-multiple-locations, replace-inventory-multiple-locations, merge-multi-location-items, track-sales-multiple-locations, read-a-multi-location-sales-report, employee-sales-report-multi-location, different-software-plans-multi-location), so the vocabulary is plainly present in the corpus - but across the 54 help articles that mention 'gift card', the token 'location' occurs in ONE, and that one is the multi-location SALES report, not gift cards. 'cross-location' 0 across all three corpora; 'merchant group' 2 dev pages, both tokenization/glossary. Every gift-card surface is scoped to a single merchant account: the liability report is 'for your business', and the prerequisite is 'Configure a merchant account for the gift card tiers on a Clover device'. INTER-STORE SETTLEMENT - 0 evidence either way. Also recorded: gift cards are excluded from Clover's offline payment path - 'This functionality doesn't work with Electronic Benefit Transfer (EBT) or gift cards' (help: set-up-offline-payments). Not a no, because the help corpus is a 1,119-doc floor (78 route-only slugs known unfetched) and an undocumented multi-merchant gift programme may still exist through the Fiserv gateway. Retrieved 2026-09-18. https://www.clover.com/en-US/help/check-outstanding-gift-card-balance-liability-report · retrieved 2026-09-18 adversarially verified

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

multi-location-cross-location-loyalty

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

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

multi-location-multi-brand

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

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

multi-location-multi-tax-jurisdiction

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

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

multi-location-central-labor-policy

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

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

hardware-commodity-devices

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

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

hardware-os-platforms

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

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

hardware-handheld-purpose-built

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

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

hardware-handheld-battery-swap

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

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

hardware-handheld-lte

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

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

hardware-offline-mode

"Clover 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

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

hardware-kds

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

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

hardware-kiosk

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

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

hardware-drive-thru

The QSR feature matrix - the vertical where drive-thru would live - enumerates order management as "Contactless dining (QR-code ordering)", "Item and order-level discounts", "Remote order firing" and "Line busting", and available accessories as "Cash drawer" and "Kitchen printer". No menu board, order confirmation display, headset or drive-thru timer appears. The 1,309-article help census returns zero hits for drive-thru, menu board or headset. https://www.clover.com/pricing/quick-service-restaurant · retrieved 2026-09-05 adversarially verified

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

hardware-printer-compatibility

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

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

hardware-peripherals

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

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

hardware-p2pe-terminal

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

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

hardware-tap-to-phone

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 prices are published per SKU on the vendor's public site, rather than quote-only. differentiator

hardware-pricing-transparency

Only one SKU family carries a published price in the page as delivered: "24 inch: $899 + $25/mo per device" and "14 inch: $799 + $25/mo per device" for the KDS. Shortfall: Flex, Flex Pocket, Compact, Mini, Station Solo, Station Duo, Kiosk and Go appear as Shop or Contact sales entries with no price in the page, and all seven pricing tables render Contact sales where a figure would go. https://www.clover.com/shop · retrieved 2026-09-05 adversarially verified

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

hardware-ownership-vs-lease

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

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

hardware-usable-after-churn

Clover states the lock directly: "While Clover POS devices may be purchased or leased from other entities, they cannot be used with other payment processors." The subscription FAQ adds that at the end of the term "you have the option to purchase or return your equipment" - so hardware can be owned outright and still cannot be moved to another processor's software. https://www.clover.com/pricing · retrieved 2026-09-05 adversarially verified

Publishes a hardware warranty term and a replacement/advance-exchange SLA with a stated turnaround (e.g. next-business-day depot swap). differentiator

hardware-rma-sla

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

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

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

Provides a remote device-management console showing each terminal, printer, and KDS as online/offline, with remote reboot, software-version visibility, and staged rollout of updates. differentiator

hardware-remote-device-management

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

Integrates with specialty beverage hardware — self-pour tap walls, flow meters, or liquor pour spouts — such that pours post to a POS tab automatically.

hardware-selfpour-scales

CLAIM: integrates with self-pour tap walls / flow meters / pour spouts such that pours post to a POS tab automatically. VERDICT: yes at grade D (partner-published only). EVIDENCE: PourMyBeer's own integration page (published 2021-05-20, modified 2023-11-07): 'With Clover POS, closing a customer out is much smoother since the beer wall purchases automatically show up on the customer's tab.'; 'The staff member opens a tab in Clover by swiping the customer's credit card. Then, the ticket is paired in the PourMyBeer terminal ... hands ... their PourMyBeer RFID card'; 'The PourMyBeer system automatically syncs to your Clover POS inventory'; names a live deployment (Crave Hot Dogs & BBQ, Colorado Springs). Corroborated by Brewbound 2021-06-24 (https://www.brewbound.com/news/supplier-news/pourmybeer-announces-integration-with-clover-pos/). CAVEAT: Clover publishes none of it: 0 hits for self-pour/PourMyBeer/iPourIt/tap wall/flow meter in the 1,309-article help centre, docs.clover.com, and the anonymous App Market listing api.clover.com/v3/apps (585 published US apps; filter name=PourMyBeer returns 0). If a partner-only source cannot carry a yes, downgrade to partial D with that shortfall. Retrieved 2026-09-16. https://pourmybeer.com/clover-pos-integration/ · retrieved 2026-09-16 adversarially verified

Supports inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call.

hardware-callerid-integration

CLAIM: inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call. VERDICT: partial. NEW SURFACE: the Clover App Market is served anonymously as JSON at api.clover.com/v3/apps (default filter hidden=false; 585 published US apps, identical at limit=100 paged and limit=1000; snapshot .cache/q316/clover/appmarket.json). Its listing for 'Phone Orders' (id 9W7VREWG0Z620, developer Seven Spaces, installCount 1053, PUBLISHED) says: 'Access Caller's phone number in App with the integration of Caller ID device ... View customer's phone order history ... Search Customers by phone number' and 'The Phone Orders app can work with caller ID hardware from CallerID.com ... EL/POS 2 (Connects 2 phone lines) - $335; EL/POS 4 (Connects 4 phone lines) - $513'. The developer's KB (https://7spaces.uservoice.com/knowledgebase/articles/461808-what-is-phone-orders-app) adds: 'You will receive a notification for incoming calls with the caller's phone number and name. You may Tap on the notification to launch the Phone Orders app and search for the customer by phone number ... You may either view the customer's order history, or start a new phone order'; hardware is the 'Ethernet Link - Whozz Calling? POS (Basic)' device on the same network as Clover Station (articles/452128). SHORTFALLS: (1) third-party App Market app, not native Clover; (2) the call raises a notification with number and name, but the customer record and history are reached by a tap plus a manual 'Search Customer' step, not popped automatically. Clover's own 1,309-article help centre still has zero caller-ID hits. Retrieved 2026-09-16. https://api.clover.com/v3/apps/9W7VREWG0Z620 · retrieved 2026-09-16 adversarially verified

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

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

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

extensibility-api-access-cost

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

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

extensibility-free-sandbox

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

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

extensibility-oauth-partner-apps

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

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

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

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

extensibility-webhook-reliability

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

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

extensibility-order-injection-api

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

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

extensibility-menu-write-api

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

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

extensibility-doordash-preferred

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

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

extensibility-first-party-delivery-integrations

"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

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

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

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

extensibility-accounting-connectors

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

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

extensibility-payroll-export

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

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

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

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

extensibility-headless-embedded

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

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

extensibility-data-portability-exit

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

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

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

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

reliability-offline-card-auth

"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

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

reliability-offline-decline-liability

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

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

reliability-lan-degraded-multi-terminal

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

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

reliability-local-transaction-engine

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

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

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

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

reliability-printer-fallback

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

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

reliability-sync-conflict-handling

CLAIM: the vendor DOCUMENTS its conflict-resolution behaviour for edits made on two devices during a network partition (last-write-wins, merge, or operator prompt). VERDICT: no - the claim is purely about published documentation, and a 100%-of-manifest census of the publisher's developer docs shows none exists. NEW SURFACE (327th): the /dev/reference REST API reference, 309 pages, never censused before (the 326th held only /dev/docs, 582). Whole corpus = 905/905 pages named in https://docs.clover.com/dev/llms.txt, 0 shells, 25.6 MB; nonsense control /dev/reference/zzz-nonsense.md returns the SPA shell. EVIDENCE: tokenised controls over the 905 dev pages -> 'conflict resolution' 0, 'last write wins' 0, 'last-write-wins' 0, 'network partition' 0, 'merge' 1 (unrelated), 'idempoten' 0. The six 'conflict' files are all homonyms and are named here as the poison: dev__docs__appendix(-1) is the HTTP status table ('409 | Conflict'), ecommerce-faqs uses it for a vaulted-card save ('The 409 Conflict occurs when trying to save a card that Clover recognizes as already existing'), clover-policies is 'Reviewer has a conflict of interest', plus the privacy-policy template and an app-approval archive. Same controls on the 1,119-article clover.com/help bodies: 'conflict' 1 doc, 'last write wins' 0, 'network partition' 0; and on the 11,832-entry www.clover.com Contentful space: 'last write wins' 0, 'network partition' 0. The one API object that could have carried the semantics is RETIRED: /v3/merchants/{mId}/sync/{table} 'Get a sync token' is published with "deprecated": true and an empty description. What Clover DOES publish about a partition is payment-only and says nothing about concurrent edits: offline payments queue for up to 7 days and are submitted on reconnect (help: set-up-offline-payments). POSITIVE CONTROL on the same dev corpus: 'offline' 86 files / 834 hits. Retrieved 2026-09-18. https://docs.clover.com/dev/reference/syncgetsynctoken · retrieved 2026-09-18 adversarially verified

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

reliability-offline-feature-matrix

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

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

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

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

reliability-247-live-support

The 24/7/365 line is the tail of a sales paragraph on /pricing. Clover's own support article states no hours at all and routes phone support with "Find your direct support phone number on your statement" - the statement issued by the reselling bank. Shortfall: no documented hours in the help centre and phone entitlement delivered through the reselling institution. No premium support SKU exists. https://www.clover.com/en-US/help/contact-clover · retrieved 2026-09-05 adversarially verified

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

reliability-onsite-install

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

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

reliability-menu-build-service

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

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

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

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

reliability-pci-dss-4-attestation

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

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

reliability-mfa-role-based-access

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

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

reliability-self-serve-training

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

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

reliability-failover-terminal-role

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

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

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

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

commercial-month-to-month-contract

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.

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

commercial-no-early-termination-fee

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

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

commercial-autorenew-terms-published

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

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

commercial-processing-not-bundled

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

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

commercial-interchange-plus-published

Clover describes its rate structure exhaustively and it is blended only: "Our credit card processing rates consist of a transaction fee, which is a percentage of the amount charged, and a flat fee per charge", and "Credit card processing rates also come in pairs, meaning there is an in-person fee where the card is presented at your POS card reader, and a slightly higher typed-in fee". No interchange-plus or cost-plus option and no bps markup figure is published; the vertical pages quote flat pairs such as 3.5% + 10 cents. https://www.clover.com/pricing · retrieved 2026-09-05 adversarially verified

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

commercial-rate-increase-clause

Section 9 reserves unilateral repricing twice and caps nothing: "Clover may add or change fees for Clover Services at any time" with 30 days notice, then "Clover may change the fees at any time." Section 20 lets Clover "change or add to these Terms at any time". There is no cap, no interchange-pass-through carve-out and no penalty-free exit tied to an increase; termination under 10.1 needs 30 days notice, and the hardware promotion separately "Requires a 3-year contract." https://www.clover.com/terms · retrieved 2026-09-05 adversarially verified

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

commercial-pricing-published

Clover 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.

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

commercial-module-unbundling

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

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

commercial-hardware-purchase-outright

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

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

commercial-hardware-not-locked

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

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

commercial-data-export-self-serve

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

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

commercial-export-customer-and-loyalty

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

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

commercial-post-termination-export-window

Section 10.3: "Upon your termination of these Terms, Clover will provide you with a reasonable period of time to allow you to extract your Account Data (defined below) that Clover has stored on its servers as of the termination date." Shortfalls: the window is a reasonable period of time with no stated number of days, and it is granted only on the merchant's own termination - 10.2 lets Clover terminate or suspend access "without any notice and liability for any reason" with no export period attached. https://www.clover.com/terms · retrieved 2026-09-05 adversarially verified

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

commercial-data-ownership-clause

The terms assert close to the opposite of merchant ownership. Section 11.1 defines everything collected, including customer information and information about the business, as "Clover Data" that "is collected by Clover". Section 11.8 permits use "for marketing purposes" and for "providing additional products and services to you, other merchants, and/or third parties", and states "Clover may continue to access, retain, use, share and combine the Clover Data for the Permitted Purposes following termination of these Terms." No merchant-ownership sentence appears and the permitted uses are not confined to aggregated or de-identified data. https://www.clover.com/terms · retrieved 2026-09-05 adversarially verified

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

commercial-pci-p2pe-tokenization

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

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

commercial-pci-dss-4-controls

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

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

commercial-privacy-dsar-tooling

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

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

commercial-wcag-kiosk-accessibility

The accessibility statement is the page where a conformance report would be linked, and it publishes an aspiration instead: "Our ongoing accessibility effort works towards conforming to the Web Content Accessibility Guidelines (WCAG) version 2.2, level AA criteria." No VPAT or ACR is offered, no product scope is stated, and kiosks and consumer ordering surfaces are not mentioned - the page's only mechanism is an email address for reporting barriers. A non-visual mode does exist on the hardware: the developer device catalogue records a 3.5mm audio jack for Google Talkback on Clover Kiosk. https://www.clover.com/accessibility · retrieved 2026-09-05 adversarially verified

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

commercial-dual-pricing-compliant

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.