Zettle by PayPal

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

Resolves an `unknown`. Splitting by item is documented in detail and survives partial payment: 'Can I split the order and charge for separate items?' is answered 'You're able to select specific items in a saved cart to pay off, the remaining items can be paid later, or separately.', with 'A receipt will be printed for each split, and they're treated as separate transactions in your sales reports.' and a published rule for prorating an order-level discount across splits. SHORTFALL: merging is refused outright -- 'Can I combine two saved carts?' is answered 'Afraid not. You need to open a saved cart and make changes to it.' -- and the only split axis is the item. There is no seat, no even N-way and no arbitrary amount or percentage split; tokenised over the 301-document corpus, `split the bill` occurs 0 times and `seat` once, not in this sense. https://www.zettle.com/gb/help/articles/4430703-saved-cart · retrieved 2026-09-09

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

The vendor's only published offline article excludes its own POS app: 'Offline payments are currently only available through select Point of Sale (POS) Apps that have integrated PayPal's POS SDK and enabled the Offline Payments feature. This functionality is not available for standard PayPal POS App.' Offline card acceptance is therefore a capability the SDK grants to third-party apps built on Zettle, not a capability of the Zettle/PayPal Point of Sale app being scored (developer.zettle.com/docs/payment-integrations/android-sdk/user-guides/manage-offline-card-payments, retrieved 2026-08-08). The product overview article states the connectivity requirement directly: 'For PayPal Point of Sale to work, you need to be connected to a 3G, 4G or wifi network' (https://www.zettle.com/gb/help/articles/1083274-what-is-paypal-point-of-sale, retrieved 2026-08-08). I retrieved all 91 articles in the GB help centre and grepped them for offline / no internet / connection lost; the only substantive hits are the offline-payments article above and the 'Repeat Payments' article's advice to keep 'a stable internet connection'. No article describes creating orders, applying modifiers, routing to a kitchen or tendering cash while the connection is down, and none publishes a degraded-mode matrix. Cash tender itself is documented only as an in-app payment method with no offline behaviour stated (https://www.zettle.com/gb/help/articles/1084756-taking-cash-payments, retrieved 2026-08-08). https://www.zettle.com/gb/help/articles/7102116-offline-payments · retrieved 2026-08-08 adversarially verified

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

order-capture-kiosk-first-party

Not scored by this record.

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

order-capture-drive-thru

Not scored by this record.

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

order-capture-drive-thru-timers

Not scored by this record.

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

order-capture-voice-ai

Not scored by this record.

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

order-capture-throttling

Not scored by this record.

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

order-capture-scheduled-orders

The nearest thing PayPal Point of Sale publishes to a future-dated order is a Saved cart, and it is a hold-and-recall, not a fire-time queue: 'The save cart feature allows you to put together a customer's order in the cart and hold it until they're ready to pay.', reopened by hand -- the article tells the user to tap View saved carts and 'select a cart to open it', with no date, time or channel attached beyond an optional description or table number. Nothing computes a fire time, and the printed kitchen ticket is produced with the receipt at payment (see Order tickets), which is the failure mode this claim is about. Tokenised over the 301-document corpus, `scheduled order`, `pre-order`, `lead time` and `fire time` each occur 0 times. https://www.zettle.com/gb/help/articles/4430703-saved-cart · retrieved 2026-09-09

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

order-capture-order-ready-signal

Not scored by this record.

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

order-capture-void-comp-controls

Not scored by this record.

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

menu-pricing-nested-modifiers

Resolves an `unknown` structurally rather than by silence. The published Product Library API is the product model, and its option tree is exactly two levels deep and cannot be three: a product carries `variantOptionDefinitions`, each a `VariantOptionDefinition` of a name plus an array of `VariantOptionProperties`, and that object is a leaf of `value` and `imageUrl` with no reference back to a group. A variant's own `options` are `VariantOption` objects of two strings, `name` and `value`. No selection counts and no forced-selection flag exist at any level -- the spec's `minimum` and `maximum` keywords are all JSON Schema string-length and array-size bounds. Tokenised over the 301-document corpus, including all 97 help articles, `modifier` occurs 0 times. Floor, not ceiling: `additionalProperties: false` appears zero times in all six published specs, so this bounds the documented model. https://developer.zettle.com/docs/api/product-library/reference · retrieved 2026-09-09

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

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

The Product library help article is the complete product-model reference and contains no modifier entity of any kind. The only compositional construct is variants: 'You can add multiple variants to a product that comes in more than one option, such as size, colour and style. You can add up to three options per product... A product can have up to 100 variants in total.' Variant prices are per-product only ('these attributes are editable on variant-level'); there is no shared modifier reusable across parent items, so no parent-by-size price matrix exists. Corroborated at grade A: the Purchase API reference (https://developer.zettle.com/docs/api/purchase/api-reference-md, retrieved 2026-08-04) line-item model has variant fields and zero occurrences of 'modifier' or 'addon'. The one Zettle article that ever documented modifiers, 2388639-using-product-modifiers-with-zettle-food-and-drink, now 30x-redirects to paypal.com/uk/business/pos-system/restaurants — that surface belonged to the retired Zettle Food & Drink product. https://www.zettle.com/gb/help/articles/1165263-product-library · retrieved 2026-08-04

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

menu-pricing-topping-quantity-tiers

No modifier construct exists to tier. The Product library article enumerates the whole model — products, up to three variant options per product, categories, folders, discounts, Pages — with no modifiers, no add-ons and no quantity or multiplier field. Variant option values are discrete named values ('The size option has three values: Small, Medium, Large'), a selection not a quantity tier, and each carries a flat price rather than a multiplier. Corroborated at grade A by the Purchase API reference (https://developer.zettle.com/docs/api/purchase/api-reference-md, retrieved 2026-08-04), whose line-item schema contains no modifier or multiplier field. Light/regular/extra pricing is therefore only reachable by creating separate variant values or separate products. https://www.zettle.com/gb/help/articles/1165263-product-library · retrieved 2026-08-04

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

menu-pricing-size-style-matrix

Not scored by this record.

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

menu-pricing-included-allowance

Not scored by this record.

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

menu-pricing-combos

Not scored by this record.

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

menu-pricing-upsell-prompts

Not scored by this record.

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

menu-pricing-86-propagation

Not scored by this record.

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

menu-pricing-countdown-auto-86

Not scored by this record.

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

menu-pricing-dayparting

Not scored by this record.

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

menu-pricing-channel-price-books

Not scored by this record.

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

menu-pricing-dual-pricing

Not scored by this record.

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

menu-pricing-allergen-nutrition

Not scored by this record.

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

menu-pricing-3p-menu-push

Not scored by this record.

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

menu-pricing-dynamic-pricing

Not scored by this record.

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

payments-processor-choice

Not scored by this record.

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

payments-published-rates

Not scored by this record.

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

payments-dual-pricing

Not scored by this record.

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

payments-surcharge-guardrails

Not scored by this record.

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

payments-emv-nfc

Accepted payment methods names the devices and the wallets: 'The PayPal Reader, Zettle Reader 2 and Terminal allow you to accept contactless and card payments as well as transactions with mobile wallets such as Apple, Samsung, and Google Pay', with Apple Pay, Google Pay and Samsung Pay listed individually. Chip is documented procedurally in Taking card & contactless payments - 'For contactless cards: Tap the card on the screen. For chip card payments: Insert the card in the card slot' followed by 'Enter PIN or sign (if applicable)' (https://www.zettle.com/gb/help/articles/1084729-taking-card-and-contactless-payments, retrieved 2026-08-08). The shortfall is the other direction: magstripe is gone, not EMV/NFC - 'Our latest card readers do not support swipe transactions with magnetic stripe cards.' https://www.zettle.com/gb/help/articles/1084715-accepted-payment-methods · retrieved 2026-08-08

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

payments-softpos-tap-to-pay

Not scored by this record.

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

payments-qr-guest-pay

Not scored by this record.

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

payments-offline-store-and-forward

Not scored by this record.

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

payments-offline-decline-liability

Not scored by this record.

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

payments-gift-cards

Resolves an `unknown`. The gift cards are first-party and balances are live: 'You can sell and redeem gift cards using your PayPal Point of Sale app; You can also track all the gift cards you sell in the gift card register in the app or online at my.zettle.com', issuance covers 'gift cards sent via email, handmade physical cards, or pre-made physical cards that are scannable' with random or custom codes and an expiry date, and at redemption 'The card's expiry date and the remaining balance will be checked.', with part-payment supported. SHORTFALL on the other two elements of the claim. Redemption across every location in a group depends on Multisite, which is closed: 'Note: The multisite feature is not available for new merchants at this time. Existing merchants can continue using the feature.' And there is no first-party online-ordering channel to redeem through -- Zettle's web selling is third-party e-commerce integrations. https://www.zettle.com/gb/help/articles/2982348-selling-gift-cards · retrieved 2026-09-09

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

payments-split-tender

Not scored by this record.

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

payments-refund-void-controls

Resolves an `unknown`. Authorisation is real and role-based, if coarse: 'Refunds can only be issued by the Zettle account owner, or the staff member who made the original sale.', and the refund flow stops for a credential -- 'Enter the account owner's password if asked.' The staff model reinforces it from the other side: a staff member can 'Issue a refund of a sale they made' but not 'Issue a refund of a sale made by someone else, such as the PayPal Point of Sale account owner or other staff'. SHORTFALL: the gate is the owner's account password rather than a per-role manager PIN, it covers refunds only -- discounts are an ordinary product-library object and no void or no-sale approval is documented -- and what is recorded is the operator, not the approver: receipts show 'The staff member's first and last name', and the transaction export tells you 'which of your staff members made a specific transaction'. No approver identity and no immutability are published. https://www.zettle.com/gb/help/articles/1609699-refunds · retrieved 2026-09-09

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

payments-chargeback-tooling

Not scored by this record.

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

payments-card-on-file

Not scored by this record.

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

payments-payout-timing

Not scored by this record.

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

payments-p2pe-pci4

Not scored by this record.

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

kitchen-station-routing

The routing ceiling is two printers and one ticket, with no rules of any kind. The hardware guide states it: 'Each smartphone, tablet or PayPal Terminal can be connected to two printers at the same time - a plus if you use both a receipt printer and a kitchen printer' The Order tickets article then fixes what goes to the second one -- the whole order, once: 'Order tickets can only be printed on a receipt printer.' and 'The order ticket can only be printed once.' There is no per-item, per-category, per-order-type or per-revenue-centre assignment anywhere, and no KDS to route to. Tokenised over the 301-document corpus, `KDS` and `kitchen display` each occur 0 times. https://www.zettle.com/gb/help/articles/1084760-accessories · retrieved 2026-09-09

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

There is no screen in the kitchen at all, so nothing can consolidate or be bumped. The vendor's entire kitchen path is one paper ticket printed alongside the receipt: 'If for instance, you have a restaurant, you can use PayPal Point of Sale to print your customer's receipt at the counter and then send an order ticket to a printer in the kitchen.', with 'An order number is printed on both the order ticket and on the customer's receipt.' as the only cross-reference. The ticket cannot be reprinted and carries no station or completion state. Tokenised over the 301-document corpus, `expo`, `expediter`, `KDS` and `kitchen display` each occur 0 times. https://www.zettle.com/gb/help/articles/1705420-order-tickets · retrieved 2026-09-09

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

kitchen-prep-time-pacing

Not scored by this record.

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

kitchen-order-throttling

Not scored by this record.

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

kitchen-channel-pause-propagation

Not scored by this record.

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

kitchen-order-ready-callback

Not scored by this record.

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

kitchen-bump-bar-hardware

No KDS exists, so there is no surface a bump bar could attach to. The compatible-hardware article is the vendor's own enumeration of what may be connected and it is a payments kit: 'We support a variety of handy accessories like docks, receipt printers, cash drawers, and barcode scanners that you can use when accepting payments with PayPal Point of Sale.' Kitchen involvement stops at a second receipt printer. Tokenised over the 301-document corpus, `bump bar`, `KDS` and `kitchen display` each occur 0 times. https://www.zettle.com/gb/help/articles/1084760-accessories · retrieved 2026-09-09

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

kitchen-all-day-counts

Not scored by this record.

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

kitchen-sla-alerts

Not scored by this record.

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

kitchen-printer-fallback

Not scored by this record.

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

kitchen-offline-operation

Not scored by this record.

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

kitchen-item-build-screens

Not scored by this record.

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

kitchen-recall-refire

Not scored by this record.

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

kitchen-order-modification-alerts

Not scored by this record.

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

kitchen-guest-ready-notification

Not scored by this record.

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

kitchen-waste-logging

Not scored by this record.

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

kitchen-speed-of-service-reporting

Not scored by this record.

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

kitchen-prep-forecasting

Not scored by this record.

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

delivery-dispatch-board

There is no delivery product, so there is no board. The integrations directory is the vendor's own map of what it connects to and it has exactly three functional categories -- POS Integration, E-commerce, and Accounting & Bookkeeping, plus Other -- with no delivery or dispatch category and no delivery partner among the 30-plus named apps. Tokenised over the 301-document corpus, `dispatch` occurs 0 times and `driver` twice, neither in a delivery sense. https://www.zettle.com/gb/integrations · retrieved 2026-09-09

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

delivery-address-validation

Not scored by this record.

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

delivery-daas-dispatch

Not scored by this record.

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

delivery-3p-direct-integration

Not scored by this record.

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

delivery-3p-injection

Not scored by this record.

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

delivery-menu-push

Not scored by this record.

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

delivery-86-sync

Not scored by this record.

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

delivery-store-pause

Not scored by this record.

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

delivery-3p-reconciliation

Not scored by this record.

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

delivery-injection-error-visibility

Not scored by this record.

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

delivery-tracking-page

Not scored by this record.

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

delivery-promise-time

Not scored by this record.

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

digital-first-party-web

Resolves an `unknown`. Zettle ships no branded ordering site of its own; web selling is somebody else's storefront wired to Zettle's inventory. The integrations directory enumerates the e-commerce route by name -- Adobe Commerce, BigCommerce, CubeCart, ePages, nopCommerce, PrestaShop, Shopify, Shopware, WooCommerce -- all under an 'E-commerce' category and described as syncing, not as a Zettle-hosted store. The first-party remote-payment surfaces are not ordering sites and are both restricted: the pricing page lists 'Zettle Invoice* 2.5%' and 'Payment Links** 2.5%' with the footnotes '*Available to sellers who signed up before May 8th, 2023.' and '**Temporarily unavailable for new sellers due to ongoing product enhancements.' https://www.zettle.com/gb/integrations · retrieved 2026-09-09

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

There is no first-party digital ordering channel to single-source. The help centre's 'Getting started with integrations' article presents online selling solely as connecting a third-party e-commerce platform — Adobe Commerce, BigCommerce, ePages Now, PrestaShop, Shopify, Shopware or WooCommerce — with data synced between the Zettle product library and the external store; no Zettle-owned web or app ordering channel, online menu or first-party checkout appears in the article or anywhere in the help centre. The Product library reference (1165263, retrieved 2026-08-04) likewise contains no digital-menu or online-channel concept in the product model. A digital menu therefore always lives in a third-party platform as a separate build kept aligned by integration sync — exactly what the claim's 'first-party digital channels ... without a separate digital menu build' excludes. The former zettle.com/gb/integrations/e-commerce page now 301-redirects to paypal.com/uk/zettle. https://www.zettle.com/gb/help/articles/2645279-getting-started-with-integrations · retrieved 2026-08-04

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

digital-native-app

Not scored by this record.

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

digital-account-saved-payment

Resolves an `unknown`. What Zettle publishes is a merchant-held record of a customer, not an account the guest creates and logs into. The customer list article enumerates the whole of it: it 'helps businesses save and manage customer data, gain insights into their activity, reward their loyalty, and send digital receipts', and the loyalty layer on top of it is emailed discount vouchers with a validity period, not a wallet. No card is stored against a customer, no address is stored, and there is no reorder path -- there is no first-party ordering channel to reorder through in the first place. Tokenised over the 301-document corpus, `customer account`, `saved address` and `one-tap` each occur 0 times. https://www.zettle.com/gb/help/articles/2442005-paypal-point-of-sale-customer-lists · retrieved 2026-09-09

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

digital-upsell-engine

Not scored by this record.

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

digital-scheduled-pacing

Not scored by this record.

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

digital-fulfillment-modes

Not scored by this record.

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

digital-qr-table

Not scored by this record.

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

digital-kiosk

Not scored by this record.

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

digital-voice-ai-phone

Not scored by this record.

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

digital-drivethru-ai

Not scored by this record.

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

digital-sms-ordering

Not scored by this record.

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

digital-google-order

Not scored by this record.

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

digital-apple-business-connect

Not scored by this record.

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

digital-loyalty-attach

Not scored by this record.

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

digital-subscriptions

Not scored by this record.

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

digital-promo-parity

Not scored by this record.

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

digital-guest-data-ownership

Not scored by this record.

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

digital-checkout-pci-sca

Not scored by this record.

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

digital-surcharge-transparency

Not scored by this record.

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

guest-loyalty-unified-profile

The documented linking mechanism is manual, per sale, in-store only - the opposite of automatic cross-channel merge. Per the Customer lists article (renamed 'PayPal Point of Sale Customer lists'; all quotes re-verified verbatim on 2026-08-08): 'You can only create new customers in your Customers menu in the app, or add them to the sale in the receipt view after taking payment', and both documented sign-up paths - 'Pass the device to your customer and ask them to enter their information' and 'Click Sign-up via QR code and ask your customer to scan the code with their smartphone camera' - begin with the same manual step, 'After taking payment, click Add or search for customer.' Insights accrue only to sales staff attach this way: 'To view analytics, customers must be added to your customer list. This is done during check-out by: Adding your products to the cart and check-out as usual. Click Add Customer and search for the customer shopping with you. This sale will now be logged under customer insights.' No dedup or merge behaviour is documented anywhere in the article - the only identity operations described are create and delete ('Open their profile and click the Delete button') - and there are no other first-party channels to merge in any case: Zettle offers no first-party web/app ordering or kiosk, the help centre's Integrations section being third-party e-commerce platforms only (Adobe Commerce, BigCommerce, ePages, PrestaShop, Shopify, Shopware, WooCommerce). https://www.zettle.com/gb/help/articles/2442005-paypal-point-of-sale-customer-lists · retrieved 2026-08-08

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

guest-loyalty-thirdparty-identity-attach

Not scored by this record.

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

guest-loyalty-accrual-models

One accrual model, not the required two. The loyalty article enumerates the entire configuration surface: signup vouchers (discount of 5%, 10%, 15% or 20%; validity 30, 90 or 365 days) and loyalty vouchers earned 'by spending a certain amount with your business, pre-defined by you in your loyalty settings' (a milestone amount; percentage or fixed-amount discount; validity 30, 90 or 365 days). Spend-milestone vouchers are the only accrual mechanism — there is no points-per-dollar balance and no visit/punch-count option anywhere in the documented settings, and vouchers 'can only be redeemed in full'. The claim requires at least two of points-per-dollar, visit/punch-count and spend-tier as configuration; Zettle's native program offers exactly one. https://www.zettle.com/gb/help/articles/6502151-loyalty-program-for-your-customers · retrieved 2026-08-04

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

guest-loyalty-offline-behavior

Not scored by this record.

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

guest-loyalty-offer-stacking-rules

Not scored by this record.

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

guest-loyalty-targeted-offers

Not scored by this record.

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

guest-loyalty-rfm-segmentation

Not scored by this record.

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

guest-loyalty-lifecycle-automation

Two always-on triggered automations exist, but not the three the claim names. Enrolment and milestone emails fire automatically once configured: 'each time you add a new customer to your Customer List, they'll receive the welcome email with the discount code. The codes are automatically generated', and 'Your customers receive the voucher in email every time they earn one (signup action, or milestone reached).' The automatic signup welcome covers the first-visit thank-you. SHORTFALL: no birthday automation and no lapsed win-back — the loyalty settings expose only the signup and spend-milestone triggers, and the help centre documents no campaign builder or other native marketing automation that could add them. https://www.zettle.com/gb/help/articles/6502151-loyalty-program-for-your-customers · retrieved 2026-08-04

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

guest-loyalty-native-email-sms

Not scored by this record.

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

guest-loyalty-consent-management

Not scored by this record.

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

guest-loyalty-10dlc-registration

Not scored by this record.

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

guest-loyalty-campaign-attribution

Not scored by this record.

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

guest-loyalty-data-export-portability

Not scored by this record.

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

guest-loyalty-review-capture-routing

Not scored by this record.

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

guest-loyalty-referral-program

Not scored by this record.

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

guest-loyalty-wallet-pass

Not scored by this record.

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

guest-loyalty-privacy-rights-tooling

Not scored by this record.

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

guest-loyalty-redemption-fraud-controls

Not scored by this record.

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

guest-loyalty-ai-offer-recommendation

Not scored by this record.

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

guest-loyalty-stored-value-gift

Not scored by this record.

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

labor-clock-in-at-pos

Resolves an `unknown`. The My staff article is the complete staff model and it is authentication, not attendance. A staff account is created by email invitation -- 'Enter your staff member's name and email address, then click Send invite.' -- and the person then chooses 'a password for your staff account' and signs in to the app. The article enumerates exactly what staff can and cannot do across six areas, and no shift, break, hours or attendance function appears in any of them; the owner's own visibility is 'a detailed overview of your transactions', not hours. There is no PIN, no badge and no card sign-in. Tokenised over the 301-document corpus, `clock in`, `clock-in`, `time clock` and `timesheet` each occur 0 times. https://www.zettle.com/gb/help/articles/1084768-my-staff · retrieved 2026-09-09

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

labor-photo-punch-verification

Not scored by this record.

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

labor-geofenced-mobile-punch

Not scored by this record.

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

labor-offline-time-punch

Not scored by this record.

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

labor-granular-rbac

Two fixed tiers, owner and staff, with a hard-coded capability list the operator cannot alter. The My staff article enumerates the staff role exhaustively by section: staff CAN check out, use all activated payment methods, view all products and stock, view and search all receipts, 'Issue a refund of a sale they made', and 'Get an overview of their own sales only'; staff CAN'T add, edit or remove products, edit stock quantity, 'Issue a refund of a sale made by someone else', 'Access Sales reports', 'Access Product reports', invite other staff, or sign in to my.zettle.com at all. The only per-staff controls documented are rename and Inactivate — no per-action grants for void, comp, discount, drawer open or price change, and no per-location scoping. PayPal's US article (https://www.paypal.com/us/cshelp/article/how-do-i-add-staff-to-my-paypal-zettle-account-help664, retrieved 2026-08-04) gives the same fixed 'Staff users can: / Staff users can't:' pair, and the single permission toggle at creation is the all-or-nothing 'Use Zettle by PayPal tools'. https://www.zettle.com/gb/help/articles/1084768-my-staff · retrieved 2026-08-04

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

There is no override to audit. The My staff article enumerates the staff permission model section by section and every restriction is a hard block, not a manager-approvable action — a staff member simply 'can't' issue a refund of someone else's sale, edit products, or open Sales reports, and no approval, escalation or manager-PIN path is offered anywhere in the article. Attribution that does exist is sale-level, not override-level: 'The staff member's first and last name are displayed on the receipt' and 'you can see which of your staff members made a specific transaction' in the my.zettle.com transaction download. That is a sales ledger, not a queryable immutable approvals trail attributing an approver to an override event. A site-scoped search of zettle.com, paypal.com help and the PayPal community for manager approval, override or PIN authorisation on Point of Sale returned no such feature. https://www.zettle.com/gb/help/articles/1084768-my-staff · retrieved 2026-08-04

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

labor-native-scheduling

Not scored by this record.

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

labor-demand-labor-forecast

Not scored by this record.

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

labor-realtime-labor-percent

Not scored by this record.

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

labor-overtime-prevention

Not scored by this record.

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

labor-minor-labor-rules

Not scored by this record.

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

labor-qualified-tips-w2-reporting

Not scored by this record.

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

labor-native-payroll

Not scored by this record.

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

labor-payroll-export-formats

Not scored by this record.

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

labor-shift-swap-workflow

Not scored by this record.

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

labor-server-performance-metrics

Not scored by this record.

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

inventory-recipe-bom-costing

The inventory model is published as an OpenAPI document and it has no recipe layer to cost. Inventory API V3 exposes twelve paths, all of them balances and movements (`/stock`, `/stock/updates`, `/movements`, `/inventories`, `/products`, `/custom-low-stock`), and twelve schemas of which the only product-shaped one is `Variant`. There is no ingredient, no component, no roll-up and no plate cost; stock is tracked per variant, and a variant is a saleable line, not a build. Tokenised over the 301-document corpus, `recipe`, `sub-recipe`, `ingredient`, `bill of materials` and `plate cost` each occur 0 times. Floor, not ceiling: `additionalProperties: false` appears zero times in all six of Zettle's published specs, so the spec bounds what is documented, not what could exist. https://developer.zettle.com/docs/api/inventory/reference · retrieved 2026-09-09

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

Stock is one number per variant, in one unit, with no conversion and no yield. Inventory API V3's schemas are balances, movements and low-stock definitions; the Product Library's `VariantDTO` carries a single free-text `unitName` alongside `sku`, `barcode`, `price` and `costPrice`, and there is no purchase unit, recipe unit, count unit or conversion factor anywhere in either model. Tokenised over the 301-document corpus, `unit conversion`, `purchase unit`, `yield` and `waste` each occur 0 times. Floor, not ceiling: `additionalProperties: false` appears zero times in all six published specs. https://developer.zettle.com/docs/api/inventory/reference · 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

Not scored by this record.

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

inventory-realtime-depletion

Not scored by this record.

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

inventory-86-auto-sync

Not scored by this record.

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

inventory-count-modes

No count workflow of any kind exists — the only documented stock adjustment is a direct quantity overwrite. The Inventory help article covers the entire feature: a per-product 'Inventory tracking' toggle, entering a starting number per variant, and updating stock from the Inventory view by tapping products, entering the new quantity and saving. Low-stock alerts ('By default, you'll be notified when you only have 3 left of a product. You can set your own low-stock limits') and oversell behaviour ('Inventory will never prevent you from selling... the inventory count will show as negative (-1)') complete the article. There is no full physical count session, no ad-hoc spot count, no scheduled recurring cycle count, and no variance record — a manual quantity edit replaces the prior number rather than logging a counted-vs-expected variance history. https://www.zettle.com/gb/help/articles/2771896-inventory · retrieved 2026-08-04

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

inventory-mobile-count-offline

Not scored by this record.

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

inventory-vendor-catalogs-edi

Not scored by this record.

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

inventory-invoice-ocr

Not scored by this record.

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

inventory-price-change-alerts

Not scored by this record.

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

inventory-par-auto-suggest

Not scored by this record.

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

inventory-waste-logging

Not scored by this record.

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

inventory-cogs-gl-export

Not scored by this record.

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

inventory-native-not-partner

Not scored by this record.

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

inventory-menu-margin-linkage

Not scored by this record.

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

reporting-realtime-dashboard

Both surfaces are documented. In the app: 'The reports section in the app is designed to give you a quick overview of your business. When you first enter the reports section, you can see a list of your last day's sales amount, number of sales and returns', with 'sales amount, sales, returns, fees, average sale, cash, redeemed gift cards' and top-selling products. On the web: 'Reports on my.zettle.com... The Reports overview page shows the summary of your daily, weekly and monthly sales', plus a Sales by hour graph for the selected day and sales/payments breakdowns by channel and payment method. Shortfall: the article never states refresh latency - no 'real time', no 'within minutes', and the finest documented granularity is an hourly bar for the current day - so 'reflecting transactions within minutes of the sale' is undocumented. The article also warns that behaviour differs for PayPal Business account users: 'If you are using Zettle with your PayPal Business account, the features differ slightly from what is described in this article.' https://www.zettle.com/gb/help/articles/1084803-about-reports · retrieved 2026-08-08

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

A printable per-day sales report exists; a close-out reconciling to an expected cash deposit does not. 'About reports' documents daily/weekly/monthly reports in the app and at my.zettle.com covering sales amount, number of sales, returns, fees, average sale, payment-method breakdown, and VAT — 'collected VAT per VAT rate and what your sales are excluding and including VAT' — plus sales by product, category and staff member, printable ('Print the overview of your sales report on your receipt printer or a standard printer') and exportable ('choose between PDF or Excel report'). SHORTFALL: nothing reconciles the drawer — no expected cash deposit, float, paid-in/paid-out or counted-vs-expected cash section appears anywhere in the article, and tips and discount totals are not among the documented report contents, so the single end-of-day close-out document the claim describes is not among the enumerated reports. https://www.zettle.com/gb/help/articles/1084803-about-reports · retrieved 2026-08-04

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

Resolves an `unknown`. Item-level product mix exists and is named: the reports hub carries 'Sales by product' -- 'Get an overview of how your products are performing.' -- alongside 'Sales by category', with CSV and PDF export and an in-app 'Top selling products' view. SHORTFALL on the rest of the claim. There is no modifier level to report, because the product model has no modifiers at all; and neither of the two filters the claim requires exists -- tokenised over the 301-document corpus, `daypart`, `revenue centre` and `revenue center` each occur 0 times. The reports are filtered by date range and, for merchants who have it, by site. https://www.zettle.com/gb/help/articles/1084803-about-reports · retrieved 2026-09-09

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

reporting-comps-voids-audit

Not scored by this record.

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

reporting-cash-over-short

Not scored by this record.

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

reporting-labor-productivity

Not scored by this record.

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

reporting-channel-profitability

Not scored by this record.

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

reporting-scheduled-delivery

Not scored by this record.

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

reporting-public-api

Not scored by this record.

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

reporting-webhooks

Not scored by this record.

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

reporting-api-not-upcharged

Not scored by this record.

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

reporting-tier-paywall

Not scored by this record.

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

reporting-history-retention

Not scored by this record.

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

reporting-anomaly-alerts

Not scored by this record.

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

reporting-nl-query

Not scored by this record.

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

reporting-guest-cohorts

Not scored by this record.

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

reporting-sales-forecast

Not scored by this record.

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

reporting-tip-tax-compliance

Not scored by this record.

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

multi-location-multi-brand

Not scored by this record.

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

hardware-commodity-devices

Not scored by this record.

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

hardware-os-platforms

The Compatible smartphones and tablets article names the client platforms and states minimum versions and device requirements: 'Our card readers have been developed for compatibility with smartphones and tablets that run iOS or Android and have Bluetooth and an internet connection', then gives the floor per device - PayPal Reader, Zettle Reader 2 and Zettle Reader each 'Requires you to run Apple iOS 14 and higher or Android 8.1 and higher.' The Terminal is documented as its own client rather than a paired one: 'The PayPal Terminal is an all-in-one solution, which means it both runs the Zettle by PayPal app and accepts payments... the Terminal cannot be connected to other smartphones or tablets.' The back office is browser-based at my.zettle.com (About reports). No Windows or Linux register client exists, which is a scope fact rather than a shortfall. https://www.zettle.com/gb/help/articles/1084705-compatible-smartphones-and-tablets · retrieved 2026-08-08

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

hardware-handheld-purpose-built

Not scored by this record.

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

hardware-handheld-battery-swap

Not scored by this record.

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

hardware-handheld-lte

Not scored by this record.

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

hardware-offline-mode

Resolves an `unknown`, and the vendor answers it in one sentence. Offline payments exist at PayPal, but not in this product: 'Offline payments are currently only available through select Point of Sale (POS) Apps that have integrated PayPal's POS SDK and enabled the Offline Payments feature. This functionality is not available for standard PayPal POS App.' Everything the article then documents -- encrypted on-device queueing, automatic submission on reconnect, a 1,000 GBP per-transaction and 10,000 GBP accumulated cap, and a hard stop where 'If your device remains offline for more than 24 hours, the offline payments functionality will be paused' -- describes what a third-party integrator's app gets, not what Zettle's own terminals do. https://www.zettle.com/gb/help/articles/7102116-offline-payments · retrieved 2026-09-09

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

Zettle neither sells nor supports a kitchen display. The compatible-hardware article enumerates the whole supported set -- 'docks, receipt printers, cash drawers, and barcode scanners' -- and the only kitchen affordance in the product is a second receipt printer: 'Each smartphone, tablet or PayPal Terminal can be connected to two printers at the same time - a plus if you use both a receipt printer and a kitchen printer' No display, no bump input, no station routing, no course or fire timing. Tokenised over the 301-document corpus, `KDS`, `kitchen display` and `bump bar` each occur 0 times. https://www.zettle.com/gb/help/articles/1084760-accessories · retrieved 2026-09-09

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

hardware-kiosk

Not scored by this record.

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

hardware-drive-thru

Not scored by this record.

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

hardware-printer-compatibility

Not scored by this record.

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

hardware-peripherals

Not scored by this record.

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

hardware-p2pe-terminal

Not scored by this record.

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

hardware-tap-to-phone

Not scored by this record.

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

hardware-pricing-transparency

Not scored by this record.

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

hardware-ownership-vs-lease

Not scored by this record.

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

hardware-usable-after-churn

Not scored by this record.

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

hardware-byod

Not scored by this record.

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

extensibility-public-api-docs

developer.zettle.com is fully public: no login, no partner agreement, no gating. The reference pages embed the machine-readable spec itself - the Product Library reference page's payload begins '"spec":{"openapi":"3.0.1","info":{"title":"Product Library API","description":"The Product Library API is used for managing merchant's product information and product images.","version":"1.0.0"}' - retrieved anonymously with an ordinary browser user agent. developer.zettle.com/sitemap-0.xml lists 179 URLs, of which roughly 170 are docs: OAuth, Finance, Purchase, Product Library, Inventory (v1 and v2), Pusher webhooks, Gift Card, Image and Card Payments API sections each with an overview, concept pages, task guides and a reference, plus iOS SDK, Android SDK and Reader Connect integration docs, a changelog, a glossary, an FAQ and a downloadable Postman collection at /docs/api/get-postman-collection. A developer account is needed to create app credentials (/docs/get-started/user-guides/sign-up-for-a-developer-account), but not to read any of the above. https://developer.zettle.com/docs/api/product-library/reference · retrieved 2026-08-08 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

Not scored by this record.

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

extensibility-free-sandbox

Not scored by this record.

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

extensibility-oauth-partner-apps

'The OAuth API handles merchants authentication and authorisation of external integrators... The OAuth API implements the OAuth 2.0 protocol.' Three documented flows: authorisation code grant with PKCE (the default, 'This flow should be used by all apps by default'), authorisation code grant for partner-hosted apps, and JWT assertion grant for self-hosted apps. The grant is merchant-issued — 'Redirect the merchant to the Zettle authorisation flow. The merchant will authorise the access request from the app' — and scoped: the OAuth API reference (https://developer.zettle.com/docs/api/oauth/api-reference, retrieved 2026-08-04) shows per-endpoint scopes in READ:/WRITE: form, e.g. READ:PRODUCT and WRITE:PAYMENT. Revocation is individual and operator-side both ways: a documented 'Disconnect app from user' endpoint — 'Remove a Zettle merchant from your app by disconnecting them from the app... clean up registered webhooks and remove access' — plus 'The API key may be revoked by your app users at my.zettle.com.' No shared static key or credential-sharing pattern is offered. https://developer.zettle.com/docs/api/oauth/overview · retrieved 2026-08-04

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

extensibility-webhooks-push

Genuine server push, not polling: 'The Pusher API provides events for you to listen to certain activities of the Zettle Go app at a working HTTPS endpoint on your server... the Pusher API sends the event in a POST request to the HTTPS endpoint', payload 'in real time', with a 10-second response timeout and a documented retry policy. Subscriptions are CRUD-managed. SHORTFALL: only one of the five order-lifecycle events in this claim is emitted. The event-payloads reference (https://developer.zettle.com/docs/api/pusher/concepts/event-payloads, retrieved 2026-08-04) enumerates the complete available set as nine events — PurchaseCreated, InventoryBalanceChanged, InventoryTrackingStarted, InventoryTrackingStopped, ProductCreated, ProductUpdated, ProductDeleted, OrganizationUpdated, ApplicationConnectionRemoved. There is no modified, paid, voided or refunded event, so refunds and cart changes still require polling the Purchase API. https://developer.zettle.com/docs/api/pusher/overview · retrieved 2026-08-04

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

extensibility-webhook-reliability

Not scored by this record.

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

extensibility-order-injection-api

Not scored by this record.

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

extensibility-doordash-preferred

Not scored by this record.

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

extensibility-first-party-delivery-integrations

Not scored by this record.

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

extensibility-middleware-compatibility

Not scored by this record.

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

extensibility-accounting-connectors

Not scored by this record.

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

extensibility-payroll-export

Not scored by this record.

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

extensibility-app-marketplace

Not scored by this record.

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

extensibility-headless-embedded

Not scored by this record.

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

extensibility-data-portability-exit

Not scored by this record.

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

reliability-offline-order-entry

Resolves an `unknown` that a prior pass recorded as unresolvable; the offline-payments article, which post-dates it, settles it. 'This functionality is not available for standard PayPal POS App.' -- so on Zettle's own app a lost connection stops the transaction rather than queueing it. Ticket routing stops with it, because the kitchen ticket is printed at payment, and check printing has no offline path of its own. Even where offline payments are available through the SDK, they are card acceptance only and still require the reader: 'Your POS device still needs to be connected to a PayPal Reader to accept payments.' https://www.zettle.com/gb/help/articles/7102116-offline-payments · retrieved 2026-09-09

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

reliability-offline-card-auth

Not scored by this record.

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

reliability-offline-decline-liability

Not scored by this record.

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

reliability-offline-kds-printing

Nothing reaches a kitchen printer offline because the sale itself cannot complete offline on Zettle's own app. The vendor is explicit that offline payments belong to other people's software: 'Offline payments are currently only available through select Point of Sale (POS) Apps that have integrated PayPal's POS SDK and enabled the Offline Payments feature. This functionality is not available for standard PayPal POS App.' The order ticket is produced at payment, so with no payment there is no ticket, and there is no kitchen display to fall back to. https://www.zettle.com/gb/help/articles/7102116-offline-payments · retrieved 2026-09-09

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

There is no second destination to fail over to and no re-issue path. A device may hold at most two printers, one receipt and one kitchen, and the kitchen ticket is single-shot: 'The order ticket can only be printed once.' Nothing monitors reachability and nothing tells staff a ticket was lost -- tokenised over the 301-document corpus, `backup printer`, `failover`, `fail over`, `unreachable` and `printer offline` each occur 0 times. The printing troubleshooting the vendor does publish is manual reconnection of the printer, not automatic redirection of the job. https://www.zettle.com/gb/help/articles/1705420-order-tickets · retrieved 2026-09-09

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

reliability-offline-feature-matrix

Not scored by this record.

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

reliability-public-status-page

Not scored by this record.

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

reliability-247-live-support

Not scored by this record.

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

reliability-menu-build-service

Not scored by this record.

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

reliability-hardware-replacement-sla

Not scored by this record.

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

reliability-pci-dss-4-attestation

Not scored by this record.

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

reliability-mfa-role-based-access

Not scored by this record.

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

reliability-self-serve-training

Not scored by this record.

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

reliability-cellular-backup

Not scored by this record.

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

commercial-month-to-month-contract

Not scored by this record.

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

commercial-no-early-termination-fee

Not scored by this record.

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

commercial-autorenew-terms-published

OVERTURNS a `no` whose uncited rationale asserted there is no software subscription and therefore no auto-renewal term. Both halves are false. The live PayPal Point of Sale Terms contemplate subscriptions and state the renewal term in public: 'We (or another company within the PayPal Group) may offer one or more of such Point of Sale Services as a subscription (" Subscription ").' and 'A Subscription will automatically renew each month until you terminate it in accordance with these Terms or any Additional Terms.' -- the same sentence appears in the General Terms and Conditions. The cancellation window is published too, in the Additional Terms for the subscription products: the Zettle Food & Drink Terms let a merchant terminate on 30 days of 'prior notice by contacting our customer success team', and they publish the fixed-term case as well, an 'Upfront Payment Subscription' for a term 'such as twelve (12) months' whose early exit 'will require you to pay a penalty equivalent to the discount on the Subscription Fee received'. Nothing here is behind a signed quote. https://www.zettle.com/gb/legal/paypal-pos · retrieved 2026-09-09

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

commercial-processing-not-bundled

Not scored by this record.

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

commercial-interchange-plus-published

Not scored by this record.

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

commercial-rate-increase-clause

Not scored by this record.

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

commercial-pricing-published

Exact US rates and hardware prices published: 2.29% + $0.09 card-present, no monthly or setup fee, reader $29/$79, terminal $199/$239. https://www.paypal.com/us/business/pos-system/pricing · retrieved 2026-08-01

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

commercial-module-unbundling

Not scored by this record.

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

commercial-hardware-purchase-outright

Reader and Terminal sold outright at published prices; no lease or rental requirement stated. https://www.paypal.com/us/business/pos-system/pricing · retrieved 2026-08-01

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

commercial-hardware-not-locked

Not scored by this record.

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

commercial-data-export-self-serve

Not scored by this record.

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

commercial-export-customer-and-loyalty

Not scored by this record.

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

commercial-post-termination-export-window

Not scored by this record.

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

commercial-data-ownership-clause

Not scored by this record.

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

commercial-pci-p2pe-tokenization

Not scored by this record.

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

commercial-pci-dss-4-controls

Not scored by this record.

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

commercial-privacy-dsar-tooling

Not scored by this record.

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

commercial-wcag-kiosk-accessibility

Not scored by this record.

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

commercial-dual-pricing-compliant

Not scored by this record.