Loyverse POS

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

Not scored by this record.

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

Not scored by this record.

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

Not scored by this record.

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

Upgraded from unknown: this is documented, and the prior note's own phrase for it, not documented, was wrong — the help centre carries two dedicated articles, both listed in the sitemap. Splitting: "The Split Ticket feature allows a cashier to divide an existing open ticket into multiple new tickets", moving selected items between a left and right pane, "You can create up to 20 tickets", with modifiers, comments, item-level discounts and taxes travelling with their items, whole-ticket percentage discounts applying to all resulting tickets and amount discounts movable by hand; bills can be printed per ticket or all at once. Merging: "The Merge Tickets function allows cashiers to combine items from multiple open tickets into a single ticket", from the ticket list by checkbox or from the sale screen, with a Move-ticket variant when predefined tickets are on. Partial rather than yes on three conjuncts: splitting is by ITEM only — there is no seat entity anywhere in the product, no even N-way split and no split by arbitrary amount or percentage (split TENDER at payment is a separate documented feature); table merging does not exist because tables are not objects, only ticket comments; and nothing describes merging or splitting after a partial payment, since a ticket closes at payment. https://help.loyverse.com/help/how-split-open-ticket-loyverse-pos · retrieved 2026-09-09

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

Not scored by this record.

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

Not scored by this record.

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

Not scored by this record.

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

Documented: sales and shifts continue offline; refunds, new customer registration and adding items do not. Offline kitchen send is not addressed. https://loyverse.com/ · retrieved 2026-08-01

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

Not scored by this record.

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

Loyverse's only mechanism for holding an order is Open Tickets, and the help centre defines it as a manual park-and-return: "The Open Tickets feature allows you to create, edit, and save orders before completing a sale", where "You can rename the ticket (by default, it's named using the current time)" and the ticket is closed when the customer is ready to pay. The name records when the ticket was PARKED; there is no promise time, lead time or fire time anywhere in the flow, and nothing injects a ticket into the make queue on a clock. The vendor's OpenAPI spec agrees at the data layer: Receipt carries created_at, updated_at and cancelled_at, and its one settable time field is documented for the past only — "You can set receipt_date to the value that is equal to the date and time in the past when the receipt was created in another system." There is also only one capture channel (the POS app), so the claim's per-channel lead time has nothing to range over. Corpus control: across the 265-document English corpus (loyverse.com, its blog, all 46 marketplace pages and the 134-article help centre) the token 'scheduled' occurs 5 times in 3 documents and not once about an order — twice in a 2020 blog post reviewing third-party appointment-booking software and twice about automatic bank transfers on the Zettle page; 'pre-order' occurs zero times. https://help.loyverse.com/help/open-tickets · retrieved 2026-09-09

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

Not scored by this record.

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

The vendor's own OpenAPI 3.0 spec makes nesting structurally impossible rather than merely undocumented. Item carries modifiers_ids — "The list of modifiers ids applied to this item" — each Modifier has exactly four authored fields (name, position, stores, modifier_options), and modifier_options is an array of Modifier_option, a leaf object of id/name/price/position with no $ref back to Modifier. There is no recursion, and no min-selection, max-selection or required/forced field exists on either schema; the receipt side agrees, where line_modifier records a single modifier_option_id per applied modifier. The help centre matches: modifiers are created as a flat name plus a list of options, assigned by ticking a checkbox per item, and applied by selecting options in one dialog. The decisive point is internal: Loyverse DOES document nesting depth where nesting exists — "The maximum nesting level for composite items is 3", spelled out as Composite item -> Component -> Sub-component -> Sub-sub-component — so the vocabulary is in the vendor's hands and is simply never applied to modifiers. Control: the token 'sub-modifier' and the phrase 'modifier group' occur zero times in the 265-document corpus, and 'nest*' occurs twice, both in that composite-item note. Caveat on strength: the spec declares additionalProperties nowhere at all, so it is a floor rather than a closed ceiling; the verdict rests on the absent $ref recursion plus the help centre, not on the field list alone. https://developer.loyverse.com/docs/API-Reference__v1.0.yaml · 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 two axes the claim needs are on different objects in Loyverse's data model, and they never meet. Size is a VARIANT concept — Item carries option1_name, described as "The name of the first option" with Size as its own example value and each Variant carries option1_value (example "Large") — while modifiers attach one level up, at the item: "The list of modifiers ids applied to this item". A Modifier_option therefore has exactly one scalar price shared by every variant of every item the modifier is ticked onto. The only price-override axis the schema provides anywhere is store_override, which is keyed on store_id; there is no variant_override and no per-parent price object, so a price matrix cannot be expressed. Duplicating the modifier per size is precisely the workaround the claim excludes. Control: 'matrix' occurs twice in the 265-document corpus, both times describing dot-matrix printers, and modifier-level pricing is never discussed in any size context. Caveat: the spec declares additionalProperties nowhere, so it is a documented floor; the verdict rests on the item/variant split and the single store-keyed override, not on field silence alone. https://developer.loyverse.com/docs/API-Reference__v1.0.yaml · retrieved 2026-09-09

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

menu-pricing-fractional-placement

Not scored by this record.

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

Not scored by this record.

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

menu-pricing-topping-quantity-tiers

The spec states the modifier arithmetic explicitly and it leaves no room for a tier multiplier: line_modifier.money_amount is "The total money amount of the modifier applied to the line item. It is equal to the price of the modifier option multiplied by the line item's quantity" (the spec's description ends there, without a full stop) The only quantity in that product is the LINE ITEM's; there is no modifier quantity, no tier and no multiplier factor, so light/regular/extra cannot change what a modifier costs. Loyverse's documented alternative is exactly the mechanism the claim excludes: the help centre's worked example creates separate options named "Extra Cheese" and "No Onion", each with its own price. Control: 'multiplier' occurs zero times in the 265-document corpus and 'tier' never occurs in a menu or modifier context at all — its only appearances are a blog essay on other vendors' tiered loyalty schemes, "top-tier payment providers" on the payment-systems page, and the "first-tier"/"second-tier" customer service of a merchant's BANK on the pricing page. https://developer.loyverse.com/docs/API-Reference__v1.0.yaml · retrieved 2026-09-09

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.

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

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

Software-only; Loyverse sells no first-party payment terminal and its API docs state payment-system integration is unsupported. https://support.loyverse.com/en/articles/8061203-faqs-about-loyverse-api · retrieved 2026-08-01

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

payments-softpos-tap-to-pay

Not scored by this record.

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

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.

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

Not scored by this record.

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

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

Loyverse staff on the vendor's own community: 'Unfortunately, Loyverse POS does not have the functionality to deal with gift cards.' The documented workaround is to create a customer record per card ('Gift card 22'), print its customer code on the physical card and hand-load loyalty points (100 points = $1.00), which redeem as a discount rather than a tender — merchants in-thread flag the resulting sales-tax distortion. A second staff answer (moderator Georg, 2023-07-30) repeats 'It is not possible to create gift cards with Loyverse'. The Payments section of the help centre enumerates 16 articles — payment-type configuration, split payment, tips, refunds and eight card-acquirer integrations — and contains no gift-card or stored-value article. https://loyverse.town/topic/3836-how-can-i-use-gift-cards-with-the-system/ · retrieved 2026-08-04

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

payments-house-accounts

Not scored by this record.

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

Employee Management add-on ($25/mo/store) manages access rights covering refunds and discounts; an immutable approver audit log is not documented. https://loyverse.com/pricing · retrieved 2026-08-01

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

Items route to a kitchen display via printer groups with item categories ticked per group; no routing by order type or revenue center. https://help.loyverse.com/help/kds-configuration · retrieved 2026-08-01

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

Resolved from unknown. Loyverse's kitchen routing is a fan-out with no re-join, documented as such: stations are printer groups with item categories ticked per group, and where several stations share one device "the kitchen printer will create two tickets for both kitchen stations with their own list of items". A KDS station is the same object on a tablet — the configuration guide is install app, name the device, create a printer group, pair with the POS — so each station receives its own slice of the order and bumps it independently. Nothing aggregates those slices back into one order view and no completion state waits on all contributing stations, which is the whole of the claim. Control across the 265-document corpus: 'expo' occurs three times, all of them coffee trade shows in a 2017 blog post ('SCAA Expo', 'Melbourne International Coffee Expo'), and 'consolidat*' nine times, all about analytics dashboards, e-invoice batching or multi-store data roll-up. Those word counts are corroboration only; the verdict rests on the documented per-group ticket split. https://help.loyverse.com/help/set-up-multiple-kitchen-station · retrieved 2026-09-09

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

Not scored by this record.

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

KDS setup docs cover tablet touch and network pairing only; no bump bar or keypad models are listed. https://help.loyverse.com/help/kds-configuration · retrieved 2026-08-01

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.

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

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.

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

In Loyverse, delivery is a label on a receipt and nothing else. The help centre's dining-options article is the whole of it: "Dining options help you specify the type of customer order" — "By default, you'll see three standard types", listed as Dine in, Takeout and Delivery — and its documented purposes are organising kitchen workflow and driving tax rules (a companion article applies tax by dining option). The API agrees: Receipt.dining_option is a free-text string (example "To go"). Drivers are not modelled at any layer — there is no driver entity, no assignment state, no run history and no clock-in for one; the Employee schema is name/email/phone/stores/is_owner. Control, tokenised over all 265 English documents: 'driver' occurs ZERO times — notable because the corpus includes the fourteen-article Printers section and eight hardware pages, where a printer driver would be the natural use of the word; 'rider' and 'fleet' are also zero; 'courier' occurs twice, both in a 2020 blog post describing third-party delivery marketplaces. Loyverse's own editorial position on delivery is that operators should buy it elsewhere. https://help.loyverse.com/help/dining-options · retrieved 2026-09-09

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

A dispatch board needs undispatched orders, driver availability and run batching; Loyverse has none of the three because delivery is only a receipt label — "Dining options help you specify the type of customer order", one of three defaults alongside Dine in and Takeout, used for kitchen workflow and tax. The product ships exactly two operational screens beyond the register — the Kitchen Display System and the Customer Display System — both enumerated as core products in the vendor's own footer and llms.txt, and the KDS is configured as a printer group of item categories on a tablet, not an order-routing surface. Control over the 265-document corpus: 'driver', 'rider' and 'fleet' are zero, and 'dispatch' occurs exactly once, in a 2020 blog interview where a Ghanaian manicurist describes posting press-on nails "through a dispatch service". Every element of the claim is absent by product scope. https://help.loyverse.com/help/dining-options · retrieved 2026-09-09

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

Not scored by this record.

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

delivery-driver-tracking

Not scored by this record.

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

Not scored by this record.

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

Zone pricing presupposes an ordering channel with a customer address to validate, and Loyverse ships none: delivery exists only as one of three default dining options — "Dining options help you specify the type of customer order" — attached to a receipt for kitchen workflow and tax purposes. Nothing in the product prices or times a delivery. Control, tokenised across all 265 English documents: 'delivery fee', 'order minimum', 'promise time' and 'geofence' each occur ZERO times, and the bare token 'zone' occurs twice, both inside 'time zone' in low-stock email-notification settings. That last figure is worth recording as a warning: a naive substring search for 'zone' returns six hits on this corpus and every one of them is 'timezone'. The customer record confirms there is nothing to zone from — Customer carries address, city, region and postal_code as CRM fields with no association to any order. https://help.loyverse.com/help/dining-options · 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.

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

Not scored by this record.

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

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.

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

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 documents explicit offline behavior for delivery: whether cash delivery orders, driver assignment, and driver settlement continue during an internet outage.

delivery-offline-behavior

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

Loyverse routes online ordering to other companies and says so in its own help centre, which lists the integration categories a merchant can connect and files under "Online ordering: UberEats Doordash Grubhub Zomato Glovo Rappi and many other regional players". The vendor's app marketplace is the enumerable proof: its Online ordering category holds seven apps — Otter, Fuudey (Orderlina), My Menu, Instalacarte, FeedUs, MENU TIGER and GrabConnect — and every one is bylined to an outside developer. The marketplace does mark Loyverse's own apps (Zapier and Workato are both "By Loyverse"), so the absence of a Loyverse byline in the ordering category is a distinction the directory itself draws rather than one inferred. Loyverse's published product set is nine items — POS, Back Office, Dashboard, Kitchen Display, Customer Display, Employee Management, Multi-store Management, Inventory Management, Loyalty Program — with no ordering channel among them, and its own 2020 blog post on online ordering exists to recommend third-party services. There is no first-party site, hence no commission position to take. https://help.loyverse.com/help/connect-apps-from-marketplace · 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

The claim is about propagation to FIRST-PARTY digital channels, and Loyverse ships none — its Online ordering marketplace category is seven third-party apps and its product set contains no ordering channel — so there is nothing for a POS menu edit to propagate to. The mechanism is documented affirmatively rather than merely missing: the item form's Description is "Optional field used mainly for e-commerce and online ordering services connected to Loyverse" and is retrievable through the API, i.e. the POS record is explicitly positioned as a menu SOURCE that outside channels read. What that produces in practice is uneven and partner-specific — the Instalacarte listing states that the Loyverse item list is transferred into Instalacarte but "This integration does not include order sync" — which is the opposite of the single-source guarantee the claim describes. Recorded as absent by product scope; if Loyverse ever ships a first-party channel this cell must be re-opened together with digital-first-party-web. https://help.loyverse.com/help/how-add-items-loyverse-back-office · retrieved 2026-09-09

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

Re-grounded on the right instrument. The prior rationale leaned on the API being unable to integrate a payment system, which is true and quotable — the vendor's support centre says "Loyverse API does not support the possibility of integration with the payment system at this moment" — but that settles an INTEGRATION limit, not the existence of a guest account. The Customer schema settles it: a Loyverse customer is a merchant-side CRM record of id, name, email, phone_number, address, city, region, postal_code, country_code, customer_code, note, first_visit, last_visit, total_visits, total_spent and total_points. There is no credential, no password, no session, no saved address book scoped to a guest, no payment token or card-on-file object, and no order-history association to reorder from; customers are created BY staff at the POS or in the Back Office and identified by barcode card, phone or name. There is also no first-party channel for such an account to exist on. Control: 'tokenized/tokenised' occurs zero times in the 265-document corpus and 'reorder' occurs twice, both meaning drag-to-reorder of a list in the Back Office UI. https://developer.loyverse.com/docs/API-Reference__v1.0.yaml · 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.

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

Not scored by this record.

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

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

One customer base across stores, identified by phone number or barcode; no digital channels exist to merge, and dedup/merge behavior is not documented. https://loyverse.com/ · retrieved 2026-08-01

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

Built-in points loyalty documented; only one accrual model is described, not two of points/punch/tier. https://loyverse.com/ · retrieved 2026-08-01

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

guest-loyalty-tiers

Not scored by this record.

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

Loyverse's entire loyalty configuration is one number. The help centre's setup article has three steps — enable it, set the rate, use it — and the rate is the whole of step 2: "By default, the loyalty program gives 1 point for every 100 currency units (e.g., dollars, euros) spent", adjustable as a percentage. Points accrue when a customer is added to a sale and redeem as a discount at checkout. There is no campaign object, no trigger, no schedule and no send mechanism of any kind, so triggered always-on automations have nothing to be built from. Control across the 265-document corpus: 'win-back' and 'lapsed' occur ZERO times; 'birthday' occurs three times and never in Loyverse's own product documentation — twice in blog essays about other vendors' loyalty software and once in the marketplace listing for BrandWallet, a third-party wallet app advertising "Automated Birthday Celebrations", which is the tell that merchants who want this buy it from someone else. Noted for honesty: the vendor's llms.txt summary claims customer segmentation (VIPs, inactive accounts); the help centre documents no segmentation feature and no campaign send either way, and segmentation would not by itself satisfy this claim. https://help.loyverse.com/help/how-customer-loyalty-program · retrieved 2026-09-09

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

Timecards and automatic hour calculation at the POS via the Employee Management add-on; no separate time clock hardware. https://loyverse.com/pricing · retrieved 2026-08-01

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.

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

Add-on 'manage access rights' per employee/role; whether permissions are grantable per discrete action and per location is not documented on the pages fetched. https://loyverse.com/pricing · retrieved 2026-08-01

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

The override mechanism exists: 13 POS access rights (apply restricted discounts, change taxes in a sale, perform returns, void saved items in open tickets, open cash drawer without a sale, reprint and resend receipts, view cost of items...) and 15 back-office rights, and 'When an employee tries to access a function on the POS that they do not have access to, the PIN panel will be opened with the request to enter the PIN. After entering the PIN code of an employee who has access to the function, a one-time access is granted'. Shortfall: nothing records WHOSE PIN granted that one-time access. The receipts report stores items, taxes, discounts, payment method, POS device and employee, filterable by employee and CSV-exportable, but that employee is the operator, not the approver; the article never states the authorising manager is captured. The Reports catalogue (13 articles across sales, exports, stock notifications, dashboard, shift reports, customer history) contains no activity log or override audit. Attribution is per-sale only; approvals are unattributed and unqueryable. https://help.loyverse.com/help/how-manage-access-rights-employees · 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.

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

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.

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

Not scored by this record.

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

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

Upgraded from unknown: multi-level BOM costing is documented, and explicitly depth-limited. Composite items are built from component items with a quantity each, and "The maximum nesting level for composite items is 3", spelled out as Composite item -> Component -> Sub-component -> Sub-sub-component, with items at the limit removed from the component picker. Prep items are supported in the sense the claim intends: a component not sold on its own is created with "The item is available for sale" deselected so it never reaches the sales screen. Cost rolls up automatically — "The system automatically calculates the total cost of the composite item based on the cost and quantity of its components" — and the Production flow states it a second time and independently: "The 'Cost' field reflects the value that is calculated based on the cost of the components of the item." Partial rather than yes because the claim's second half is a change-propagation guarantee — that plate cost recalculates when any component's cost changes — and neither article states that trigger; both describe derivation at the point of use. Note also that Production, which is where the second cost statement lives, is part of the paid Advanced Inventory add-on. https://help.loyverse.com/help/how-create-composite-item · 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

Purchase-unit vs sell-unit conversion is achievable but only as a modelling workaround, not as unit fields on the item. The vendor's own instruction is to create two items — a piece-level item ('Water, bottle 0.5L') and a second composite item ('Water, box 0.5L, 25p') with 'Use production' switched on, whose component is the piece item at quantity 25 — then purchase-order the box item and disassemble it into pieces. There is no purchase/recipe/count unit field with a conversion factor on a single item. Shortfall, and it is two-part: composite items take only a component and a Quantity (cost is derived from component cost x quantity), with no per-ingredient unit of measure; and no yield or waste percentage exists anywhere — conversion is assumed lossless, one box always yields exactly 25. Stock adjustment reasons are limited to Receive Items, Inventory Recount and Loss or Damaged, so raw-to-usable shrink can only be booked after the fact as a manual loss adjustment. https://help.loyverse.com/help/how-order-items-by-boxes · retrieved 2026-08-04

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

Advanced Inventory add-on manages stock and valuation; the three count modes and per-count variance history are not documented. https://loyverse.com/pricing · retrieved 2026-08-01

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.

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

Not scored by this record.

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

inventory-bar-partial-bottle

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

Free Dashboard product: sales analytics accessible from any device, browser back office plus mobile app. https://loyverse.com/ · retrieved 2026-08-01

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

reporting-eod-closeout

Shift open/close reporting is documented; a single EOD document reconciling tax, tips, discounts, refunds, tenders and expected deposit is not. https://loyverse.com/ · retrieved 2026-08-01

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

Upgraded from unknown. Item-level PMIX is documented in full: the Sales by Item report covers "sales volume, revenue, costs, and profitability" over Today / Yesterday / This week / This month / Custom period, with a chart that can "Group data by Hours, Days, Weeks, Months, Quarters, or Years", a detail table with configurable columns and sorting, and a top-five-by-net-sales overview; sibling reports exist for Category, Employee and Payment type. Modifier level exists but is thinner — the modifiers article directs the reader to the Sales by modifier report, "to see how often each option is selected", which is a usage count, and unlike Item and Category it has no article of its own in the Reports section, so quantity is documented while gross and net sales at modifier level are not. The filter half of the claim fails outright on one conjunct: 'revenue center' occurs ZERO times across the 265-document corpus and no such object exists in the product or the API, so a revenue-centre filter cannot exist; hour GROUPING is available but named dayparts are not ('daypart' is likewise zero). https://help.loyverse.com/help/sales-item-report-back-office · 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 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

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.

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

Loyverse's org model is exactly two levels, account and store, and both scoping surfaces the claim names are documented at that depth. Permissions: "Select the store(s) the employee should have access to" — a multi-select of stores on the employee form, not a group object. Reporting: "Use the store filter to view reports for a specific store or all stores combined" — two scopes with nothing between them. The API is an independent second instrument and agrees: the Store schema is nine identity and address fields (name, address, city, state, postal_code, country, phone_number, description) with no parent, group or region reference, and Employee.stores is "The list of store ids where this employee has access", a flat array. Control: 'hierarchy' and its inflections occur ZERO times in the 265-document corpus. A caution for anyone re-checking this by keyword: 'region' is NOT a usable control here — it appears in the spec as a postal-address field on Customer, and searching for it will return a false positive that has nothing to do with org structure. https://help.loyverse.com/help/how-create-and-manage-multiple · retrieved 2026-09-09

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

Items are maintained centrally in the browser back office across stores, but there is no documented publish action, version history or audit of what was pushed.

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

Only the per-store leg exists: the multi-store guide's Stores section lets one item carry a different price, in-stock quantity and low-stock alert per store without duplication. Per-channel fails outright — moderator Hanna (loyverse.town, 2023-09-09) answers a dine-in vs takeaway pricing request with 'make 2 items with different prices' sharing stock via a component, exactly the item duplication the claim wording excludes. Per-daypart also fails: a discount takes only name, type, value and restricted-access — no schedule field — and vendor forum staff confirm time-based (happy hour) application is manual per ticket. https://help.loyverse.com/help/how-create-and-manage-multiple · retrieved 2026-08-04

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

Not scored by this record.

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

Not scored by this record.

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

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.

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

Not scored by this record.

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

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

Android and iOS apps plus browser back office are named; minimum OS versions and device specs are not stated on the pages fetched. https://loyverse.com/ · retrieved 2026-08-01

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

Vendor states sales and shifts continue offline and explicitly enumerates what does not: refunds, new customer registration, adding items. https://loyverse.com/ · retrieved 2026-08-01

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

First-party KDS shipped free, with category-based routing and elapsed-time colour escalation; touch input only, no course/fire timing documented. https://help.loyverse.com/help/kitchen-display-system · retrieved 2026-08-01

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.

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

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.

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

Not scored by this record.

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

Not scored by this record.

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

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

Public API reference at developer.loyverse.com, readable without a partner agreement; support article links it openly. https://support.loyverse.com/en/articles/8061203-faqs-about-loyverse-api · retrieved 2026-08-01

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

extensibility-api-access-cost

Not scored by this record.

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

extensibility-free-sandbox

Not scored by this record.

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

extensibility-oauth-partner-apps

OAuth 2.0 supported in addition to personal access tokens; only OAuth-created webhooks carry the X-Loyverse-Signature HMAC header. https://support.loyverse.com/en/articles/8061203-faqs-about-loyverse-api · retrieved 2026-08-01

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

extensibility-webhooks-push

Webhooks documented and creatable three ways; but only paid receipts are exposed via the API, so there is no full created/modified/voided order lifecycle. https://developer.loyverse.com/docs/ · retrieved 2026-08-01

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

extensibility-webhook-reliability

Not scored by this record.

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

extensibility-order-injection-api

Not scored by this record.

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

extensibility-menu-write-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

Sales continue on-device without internet. https://loyverse.com/ · retrieved 2026-08-01

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.

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

Not scored by this record.

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

Not scored by this record.

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

reliability-offline-kds-printing

CLAIM: kitchen display and/or kitchen printer routing continues to function while offline. VERDICT: unknown, held. The transport is documented as LAN, but no page says kitchen printing or KDS keeps working without internet. NEW SURFACES (321st): (1) help.loyverse.com English sitemap census: 134 articles, all 200. The href fixpoint adds only 45 topic-index pages, no articles. Controls: offline, internet connection, without internet, local network and LAN (tokenised, case-insensitive). No hit mentions kitchen, KDS or printer, except a LAN port in a printer-cabling step. (2) help.loyverse.com/help/offline-work-of-pos lists what works offline ("Sales transactions can be processed and recorded", "Shifts can be managed without interruption") and eight limitations: unsynced receipts, logout, refunds, customers, open tickets ("will not sync with other devices until the Internet connection is restored"), email receipts, integrated card terminals, stock. Kitchen printers and KDS appear in NEITHER list. That silence cannot carry a yes or a no. (3) help.loyverse.com/help/kds-configuration: "Make sure that both POS and KDS devices are connected to the same Wi-Fi network"; pairing is by LAN search or manual IP. (4) loyverse.com/kitchen-display-system: live page answers 405 to curl and to fetch (a refusal). Wayback 20260606172335 FAQ: "POS and KDS connect via Wi-Fi through your router." No offline statement. (5) App Store id1218352383 and Google Play com.loyverse.kds descriptions: no offline statement. The sibling Loyverse CDS listing DOES say "Loyverse CDS works even without an Internet connection" (a contrast only, not evidence about KDS). (6) crt.sh %.loyverse.com: wildcard/QA/stage names only. docs.loyverse.com 403, dat.loyverse.com 405, store.loyverse.com is a hardware shop; no spec found. Retrieved 2026-09-17. || 330th: 330th -- TWO NEW VENDOR SURFACES, neither of which settles it, and one of them CLOSES the enumeration route for good. (1) loyverse.town (the vendor's own Invision community, not previously mined) has a Downloads area whose "User Guide" category serves the Loyverse POS User Guide PDF anonymously (32,118,070 bytes, published 2024-05-03, 112,292 views / 8,206 downloads; fetched via ?do=download with the page's own guest csrfKey, no sign-in). It is a 344-page manual, far larger than the 134-article English help centre, and it covers exactly the modules in question: 9.8 Using Kitchen Printers, 9.11 Kitchen Printer for Each Kitchen Station, 9.12 Multiple Kitchen Stations Sharing One Printer, 9.20 How to Use Loyverse KDS, 9.21 KDS Configuration Guide, 9.22 Troubleshooting When Working with KDS. THE DECISIVE FINDING IS NEGATIVE FOR THE ENUMERATION ARGUMENT: section 2.22 'Offline Use of Loyverse POS' opens "The Loyverse POS app works offline. Your device can continue to make sales and work with shifts even when it's not connected to the Internet. However, not all functions are supported offline; such as refunds, new customer registration, adding items, AND FEW OTHER RESTRICTIONS." -- the offline restriction list is EXPLICITLY OPEN-ENDED, so the absence of kitchen printers and KDS from it (the box 'Other restrictions of the offline work' names only integrated card terminals and stock/negative-stock alerts) cannot be read as a guarantee that they keep working. No sentence anywhere in the manual affirms offline kitchen printing or offline KDS. What the manual does add is transport: printers are paired directly to the POS device and "when a customer orders, the kitchen printer automatically produces a ticket", and 9.22.1 recommends "having separate router with Wi-Fi connection only to the mobile device with Loyverse POS App and mobile devices with KDS App", with 9.22.2 assigning the KDS tablet a static LAN IP -- local-network only, but still an implication, not a statement. (2) The same Downloads area serves the Loyverse KDS Android app itself (22,133,502-byte APK, version 1.9.0 released 2026-03-03, from the vendor's host, not a mirror). Unpacked (not executed); its resources.arsc string pool (8,154 extracted strings) contains NO token 'offline' in any language -- the app's only connectivity strings are 'No internet connection.' / 'Network not available.' and their 20 translations. A lossy arsc extraction cannot carry a no, and an absent string is not an absent behaviour, so this is recorded as a dead end rather than evidence. Also re-derived today: help.loyverse.com/sitemap.xml is 1,955 URLs across 15 locales but still exactly 134 English /help/ articles -- the corpus the 321st censused has not grown. Retrieved 2026-09-18. 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

Resolved from unknown. The 2026-08-04 assessment read the whole fourteen-article Printers set and found no failover, but left the cell open because two troubleshooting articles named in the section indexes returned 404 and might have settled it. Their real slugs are /help/troubleshooting-when-setting (Ethernet printers) and /help/troubleshooting-when-working-kds — both are in help.loyverse.com's sitemap, both fetch at 200, and both have now been read in full. Neither describes fallback of any kind: the Ethernet article is a hardware-then-network checklist (paper jams, cable and power lights, printing the printer's network configuration report, comparing printer and router IP addresses for a subnet mismatch), and the KDS article offers two remedies, use a separate router and assign the tablet a static IP. There is no backup printer for a group, no rerouting to another printer or to the KDS, no retry and no staff alert when a device is unreachable. The one documented remedy remains manual and after the fact — reopen the saved ticket and tap Reprint order, available for two hours after the ticket closes. The blocking evidence gap named in the prior note is now closed. https://help.loyverse.com/help/troubleshooting-when-setting · retrieved 2026-09-09

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

Not scored by this record.

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

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.

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

reliability-failover-terminal-role

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

Upgraded from unknown: both facts the claim asks for are published, but not in a contract document. The pricing page FAQ states the renewal trigger — "your subscription will be automatically renewed at the end of the billing period" — and the opt-out window, which is that there is none: "You can easily cancel your subscription at any time", with the cancellation steps given inline. The billing period is defined on the same page (monthly or annual per add-on), and trial mechanics are covered too: 14 days, no card, and the trial itself cannot be cancelled early. Partial rather than yes on the claim's 'contract terms' qualifier — loyverse.com/terms-use serves a 200 whose body is navigation and footer only (about 2.2 KB of text in a 30 KB shell, with no clause text rendered), so the substance is disclosed on a pricing FAQ rather than in readable published terms. Graded C accordingly: this is a vendor pricing page, first-party but written to sell. Control: 'auto-renew' as a token occurs zero times — the vendor's own spelling is the verb phrase 'automatically renewed', which is exactly why a hyphenated-token control would have produced a false absence here. https://loyverse.com/pricing · 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

Every SKU carries a specific per-store dollar figure, with the core POS and KDS free; no contact-sales gate. https://loyverse.com/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

Fully BYOD on off-the-shelf Android/iOS tablets, receipt printers and barcode scanners, so nothing is leased; but Loyverse publishes no hardware price list of its own.

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.