Lightspeed Restaurant

order-capture-floor-plan-editor

Graphical editor is real: tables are scaled by 'pulling and pushing the table edge', a Table type field offers round or square, Number of covers sets capacity, and multiple floor plans represent 'each area in your restaurant'. Shortfall: the claim's fourth element, assigning sections to servers, is not documented. Neither this article nor Managing users and floor plans links a floor plan or section to a POS user; that article covers permissions via user groups only. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804656709-Creating-and-managing-floor-plans-and-tables · retrieved 2026-08-02 adversarially verified

order-capture-seat-level

'If an order was taken in table service mode with items assigned to particular seats, the check can be split according to those seats,' and 'Split the checks by tapping Distribute by seat. Once done, each item is automatically put onto a separate check for its corresponding seat.' Seat tagging at entry plus automatic post-hoc split with no re-keying - both halves of the claim documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/360051089493-Check-splitting · retrieved 2026-08-02 adversarially verified

order-capture-coursing-hold-fire

Coursing documented in Table Service mode. An explicit hold-and-fire-next-course action from a handheld is not documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/360050328374-About-ordering · retrieved 2026-08-01

order-capture-split-merge

Split by seat and by covers (even shares) documented. Arbitrary-amount splits and merging checks/tables after partial payment are not. https://k-series-support.lightspeedhq.com/hc/en-us/articles/360051089493-Check-splitting · retrieved 2026-08-01

order-capture-bar-tab-preauth differentiator

Pre-authorization is real: 'Pre-authorization guarantees payment of the pre-authorized amount, not necessarily the order total,' with a default hold amount set in Back Office. Shortfall: the two other halves of the claim are undocumented — no mechanism to incrementally re-authorize as the tab grows (a tab exceeding its hold only turns the card status yellow), and no end-of-day auto-close of stale tabs. Further gated to 'accounts using Lightspeed Payments located in Australia, UK, and the US.' https://k-series-support.lightspeedhq.com/hc/en-us/articles/4408089985179-Creating-and-managing-bar-tabs · retrieved 2026-08-02 adversarially verified

order-capture-transfer-audit

Transfers between tables and users are documented, gated by permission: POS configurations offer 'Restrict table transferring to managers only: When enabled, only POS users with manager permissions can transfer customers between tables', and 'You can control who can transfer items to another table from the Back Office though your POS user permissions.' The Transactions report (4403189403675) records transfer events as types 'Foreign: An order was transferred from one table to another' and 'Transfer'. Shortfall: the report entry is not documented as naming both employees. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804606610-Managing-and-understanding-POS-configurations · retrieved 2026-09-03 adversarially verified

order-capture-native-handheld

Vendor documentation, not just a store listing: Tap to Pay on iPhone lets the K-Series app 'accept Apple Pay, contactless credit and debit cards, and other digital wallets through a quick tap on an iPhone' with no additional hardware. The App Store listing (Lightspeed Commerce Inc., iOS 18.5+/iPadOS 18.5+) states orders are 'sent directly to the kitchen or the bar'. Native app on the handheld itself, not a mirrored session. https://k-series-support.lightspeedhq.com/hc/en-us/articles/10071706424347-Tap-to-Pay-on-iPhone-with-Lightspeed-Payments · retrieved 2026-08-02 adversarially verified

order-capture-offline-order-entry

The vendor does publish an offline assurance, under 'Handling an outage': 'If your network or internet service goes out, most basic order-taking functions will still work offline. But you'll still want to get back online quickly to use your hardware and process card payments.' That is offline order entry stated by the vendor, and it is why this is no longer unknown. Shortfall: 'most basic order-taking functions' is never enumerated, so what does and does not work offline is NOT published — modifiers, kitchen send and cash tender are nowhere confirmed, and the same sentence puts hardware and card payments outside the offline envelope. The counter-evidence stands: the 'Networking for Lightspeed Restaurant' guide requires outbound connectivity to *.lightspeed.app, *.ikentoo.com and *.adyen.com and 20 Mbps per POS device, describing no offline mode; peer-to-peer LAN ports are supplementary. Same source and same reading as reliability-local-transaction-engine, which is partial on this article for the same shortfall. https://k-series-support.lightspeedhq.com/hc/en-us/articles/53288894613787-Troubleshooting-network-issues · retrieved 2026-08-11 adversarially verified

order-capture-qr-same-check differentiator

Contactless/QR ordering exists as an add-on; whether items land on the same open POS check is not documented.

order-capture-kiosk-first-party differentiator

Assessed and unresolved. The only first-party support for a kiosk is marketing - one sentence on the QSR page ('Equip your restaurant with self-order kiosks directly connected to your POS system') and an AU Lightspeed Kiosk page whose sole hardware statement is 'Tablet-based hardware keeps costs affordable and setup simple'. Every kiosk support article I could locate belongs to a different product line (L-Series Kiosk mode / Self-Order Menu, O-Series Setting up Lightspeed Kiosk); there is no K-Series kiosk documentation. Menu-and-modifier parity with the POS is therefore unverified, and no ADA or WCAG conformance material exists for any Lightspeed kiosk. A differentiator yes needs grade A or B and this has neither. adversarially verified

order-capture-drive-thru

No drive-thru order flow documented.

order-capture-drive-thru-timers

No drive-thru capability exists anywhere in the K-Series product surface. The Supported hardware article enumerates every supported peripheral class (barcode scanners, receipt/label printers, network accessories, cash drawers, payment terminals, KDS, Order Display Screen) - no lane hardware, headsets, or timers. The Sales Reports catalog likewise enumerates its reports (Business, Products, Product Mix, Shifts, Staff, Hourly Performance, Text Messages, Device, KDS Statistics) with no drive-thru or speed-of-service-by-lane report. 'Drive-thru' appears in zero of the 527 help-centre articles. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260800124209-Supported-hardware · retrieved 2026-08-05

order-capture-voice-ai differentiator

'Lightspeed AI' and an 'AI Assistant' component exist, but no voice-ordering agent or voice-AI partner program is documented.

order-capture-throttling differentiator

Per-slot capacity limits exist for the online channel: Order ahead settings include 'Time slot duration: The time in minutes between future orders' and 'Limited orders... In the Orders per time-slot field, enter the number of orders accepted in each time slot duration. For example, accept only five orders every 15 minutes.' Shortfall: no automatic quote-time extension on kitchen load - prep time is changed manually ('From the Restaurant POS app, you can edit prep time to better match current production speed'), and the caps are static per profile, not load-triggered. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407098296091-Managing-Order-Anywhere-service-profiles · retrieved 2026-08-05

order-capture-scheduled-orders

Order Anywhere service profiles have an 'Order ahead' toggle: 'Allow customers to schedule future orders for pickup or delivery by toggling on this button. This option is not available for the Table profile'; profiles set a 'Custom delivery delay or Custom deadline' in minutes per profile (the per-channel lead time), and future orders are listed by pickup time with a 'Carried forward' reporting treatment. Shortfall: no documentation of a computed fire time that injects the ticket into the KDS/print queue later than receipt. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407098296091-Managing-Order-Anywhere-service-profiles · retrieved 2026-09-03 adversarially verified

order-capture-catering

'Customer invoices allow you to manage catering and wholesale orders within Lightspeed POS... manage orders or services that a customer can pay for at a later time' via an Invoice payment method, Accounts Receivable page and per-customer Balance view; separately, 'Customer deposits allow you to accept advance payments for upcoming events and functions... recorded as a positive balance on the customer's profile and remain excluded from daily revenue and sales until they are redeemed' (Creating and applying customer deposits). Shortfall: no quote/proposal workflow and no separate catering order queue or event schedule - catering orders ride the normal POS order flow. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4403941107099-Creating-customer-invoices · retrieved 2026-08-05

order-capture-order-ready-signal differentiator

Same evidence as kitchen-order-ready-callback: the KDS 'Ready to collect' status change pushes a notification to installed third-party online ordering integrations, with no POS or tablet action ('no need to update it again on the POS', March 2026 release notes). Not enumerated per marketplace. https://k-series-support.lightspeedhq.com/hc/en-us/articles/22708154090267-Using-the-Kitchen-Display-System-2-0 · retrieved 2026-09-03 adversarially verified

order-capture-void-comp-controls

'Understanding void reasons': reasons are created in Back Office (Payment > Refunds and voids) and 'Only POS users with the appropriate permissions can refund or void receipts from the POS'; every void or refund carries a reason, optionally printing an internal receipt, and 'Void reasons display in the Cancellations and corrections report'. Shortfall: reason codes are documented for voids and refunds, not for comps or discounts, and gating is by standing user permission rather than a manager-approval prompt. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804657449-Understanding-void-reasons · retrieved 2026-09-03 adversarially verified

menu-pricing-nested-modifiers

'Understanding modifiers and modifier groups' (June 2026): a modifier group carries a per-modifier price, a Default toggle, and 'Toggle on Selection is required to require customers to choose one or more modifiers, then set a minimum and maximum number of selections' between 1 and 99; 'Modifier groups can only be added to single items, not Combos or Groups'. The OpenAPI schema apeMenuModifierGroupV2 (minimumSelection, maximumSelection, mustSelectAnItem, productModifiers) has no child-group field. Shortfall: one level of grouping with min/max/required is documented; nesting a group beneath a modifier, let alone three levels, is not. https://k-series-support.lightspeedhq.com/hc/en-us/articles/51623634913051-Understanding-modifiers-and-modifier-groups · retrieved 2026-09-03 adversarially verified

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

The 'Understanding modifiers and modifier groups' article enumerates the entire pricing surface: 'By default, modifiers have a price of zero. To add a price to a modifier, assign it to a modifier group,' where you 'Add a price for each modifier' - one price per modifier per group. No per-parent-item or per-size price matrix exists among the documented modifier or group settings; varying a modifier's price by parent size requires duplicating modifier groups, exactly the pattern the claim excludes. https://k-series-support.lightspeedhq.com/hc/en-us/articles/51623634913051-Understanding-modifiers-and-modifier-groups · retrieved 2026-08-03

menu-pricing-fractional-placement differentiator

Targeted searching of the K-Series help centre for half-and-half and fractional topping pricing returns only generic items, modifiers, price-list and check-splitting articles. Modifiers carry their own price, but per-section placement and fractional topping charge are undocumented. Absence of documentation, not proven absence. adversarially verified

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

The modifier engine is documented end-to-end and contains no fractional-placement or half-and-half pricing concept: a modifier carries a name, accounting group and SKU; a price exists only via its modifier group ('Add a price for each modifier'), plus Default and min/max selection counts (1-99). No placement (left/right/whole), no per-portion price fraction, and no configurable half-and-half rule (higher-price / average / fractional) appears anywhere in the menu documentation. https://k-series-support.lightspeedhq.com/hc/en-us/articles/51623634913051-Understanding-modifiers-and-modifier-groups · retrieved 2026-08-05

menu-pricing-topping-quantity-tiers

The modifiers article's only quantity control is the required-selection toggle with minimum/maximum choices (1-99) governing how many times options in a group can be selected - the 'adding the modifier twice' pattern the claim explicitly distinguishes from tiers. No light/regular/extra/double tier concept and no per-tier price multiplier appear anywhere in the documented settings, and kitchen-note production instructions are explicitly separate ('Production instructions cannot be used with modifiers and modifier groups') and carry no price. https://k-series-support.lightspeedhq.com/hc/en-us/articles/51623634913051-Understanding-modifiers-and-modifier-groups · retrieved 2026-08-03

menu-pricing-size-style-matrix differentiator

Item price types are enumerated: 'Single price (default)... Manually-entered price... Manually-entered negative price... No price... Multiple prices: There is a regular base price but can use modified prices based on the order profile selected at the POS... Price as a percentage: The price is based on a percentage of the order's value.' Price variation axes are order profile and price list (location) only - there is no two-axis size x style grid with per-cell overrides anywhere in the items, combos, or price-list documentation. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804656569-Creating-combos · retrieved 2026-08-05

menu-pricing-included-allowance differentiator

The modifier-group settings are enumerated in full - per-modifier price, a Default toggle for pre-selected add-ons, and a required-selection toggle with min/max choices (1-99). There is no included-allowance concept: no setting charges only for overage past N included selections, and no substitution credit or forbid-substitution configuration exists. The documented approximations are zero-priced modifiers or default add-ons, which charge all-or-nothing rather than overage-only. https://k-series-support.lightspeedhq.com/hc/en-us/articles/51623634913051-Understanding-modifiers-and-modifier-groups · retrieved 2026-08-03

menu-pricing-combos

'Combos allow you to group items together for a fixed price. Customers can choose from a preset group of items or a list of applicable items' — fixed-price bundles with choice groups, plus a companion article on combo/item sequencing. Shortfall: no price-delta upcharge when a component is swapped, and no automatic detection or conversion of eligible a-la-carte items already in the cart into combo pricing. Both are named in the claim. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804647349-About-menus-and-items · retrieved 2026-08-02 adversarially verified

menu-pricing-upsell-prompts differentiator

Online-channel upsells exist and are configurable: 'Use smart upselling, powered by AI, to recommend specific products... managed through the Upsell Manager in the Back Office' (requires 150+ orders in past 21 days), and since July 2026 operators can 'Override automated recommendations by removing dishes... or pinning high-margin items' under Menu > Menu Upsells. Shortfalls: Order Anywhere only - no POS or kiosk prompt configuration - and no attach-rate reporting on the prompts is documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/50574509323291-Understanding-Menu-upsells-in-Order-Anywhere · retrieved 2026-08-05

menu-pricing-86-propagation

Item availability lets staff 'snooze' an item from the Restaurant POS app (via the OA-Availability web extension) or the Order Anywhere Back Office; snoozed items 'appear gray and marked as Currently unavailable on your online menu' and auto-return after the chosen duration. January 2026 release notes add that items 'automatically become unavailable in Order Anywhere when POS stock hits zero and reappear when stock is restored'. Shortfall: the documented scope is Order Anywhere; no single action is documented to reach KDS, kiosk or third-party marketplaces, and no latency is stated. https://k-series-support.lightspeedhq.com/hc/en-us/articles/10724827631259-Setting-up-and-using-Item-availability · retrieved 2026-09-03 adversarially verified

menu-pricing-countdown-auto-86 differentiator

The countdown half is documented: sales restrictions monitor inventory quantities - 'Set the quantity to the inventory amount (or leave at 0, if unavailable)' and 'When items reach zero quantity, these items are automatically marked as unavailable in Order Anywhere' or supported third-party channels, becoming available again on restock. Shortfalls: no scheduled auto-restore of the count is documented - restore requires restocking or manual action - and the automatic 86-at-zero is described for online ordering channels rather than the POS itself, whose documented mechanism is manual snoozing (1, 12 or 24 hours, or indefinitely). https://k-series-support.lightspeedhq.com/hc/en-us/articles/10724827631259-Setting-up-and-using-Item-availability · retrieved 2026-08-03

menu-pricing-dayparting

Automatic scheduling exists - 'Order profiles allow you to apply preset settings to orders at the POS, either manually or on an automatic schedule' - and price lists ride on it: a Happy hour profile 'will automatically apply that pricing at a scheduled time'. Shortfall: what is dayparted is price, not menu or item availability; no day-of-week rule and no start/end time fields are documented in either the order-profile or price-list article; and the claim's timezone requirement is not addressed anywhere I could retrieve. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804657389-About-order-profiles · retrieved 2026-08-02 adversarially verified

menu-pricing-channel-price-books

Two documented mechanisms: items support 'Multiple prices' with 'modified prices based on the order profile selected at the POS', and price lists 'apply to menu items based on restaurant location and order profile' with order-profile linking (UEAT integration expects distinct prices on Default/Pickup/Delivery profiles; Uber Eats uses a dedicated order profile). Shortfalls: no percentage-markup rule over a base price - per-profile prices are entered per item or imported per price list - and the price-list feature must be enabled by Support ('Price lists are not enabled by default'). https://k-series-support.lightspeedhq.com/hc/en-us/articles/4402274951323-About-price-lists · retrieved 2026-08-05

menu-pricing-dual-pricing differentiator

The Payments FAQ enumerates exactly one card-cost-offset mechanism - 'Surcharging with Lightspeed Payments is available from the Settings page' - and mentions no dual pricing, no cash discounting and no separate cash/card price per item. The menu side stores one price per item per price list, and modifiers carry one price per group, with no field for a second cash price and no documented cash/card receipt presentation across POS or Order Anywhere. Consistent with the sibling payments-dual-pricing cell: surcharging, card-present and POS-only, is the vendor's documented alternative. https://k-series-support.lightspeedhq.com/hc/en-us/articles/15214224728987-Lightspeed-Payments-FAQ · retrieved 2026-08-04

menu-pricing-allergen-nutrition

K-Series API supports allergen data on items. Nutrition values and derivation from linked recipes are not documented. https://api-docs.lsk.lightspeed.app/ · retrieved 2026-08-01

menu-pricing-recipe-linkage differentiator

Inventory add-on links recipes/ingredients to items with costing; item-level theoretical food cost reporting is not documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407511552155-Creating-and-managing-recipes · retrieved 2026-08-01

menu-pricing-3p-menu-push

Menu syncs from Back Office to DoorDash/Uber Eats — but via Deliverect, which Lightspeed white-labels as 'Lightspeed Delivery by Deliverect'. Uber Eats also has a direct integration. Per-item rejection visibility not documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/25208938481691-Setting-up-the-Deliverect-integration · retrieved 2026-08-01

menu-pricing-dynamic-pricing

Time-based automatic repricing is documented: 'For your daily drink specials, you link an order profile called Happy hour to a sixth price list, which will automatically apply that pricing at a scheduled time', and order profiles can be applied automatically on a schedule (Adding order profiles, Schedule section). Shortfalls: no demand- or load-responsive pricing and no floor/ceiling guardrail settings exist - variation is limited to pre-scheduled profile/price-list switches. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4402274951323-About-price-lists · retrieved 2026-08-05

payments-processor-choice differentiator

Rests entirely on Merchant Maverick naming Dejavoo/Worldpay, Cayan, BridgePay. Lightspeed's own payments page documents the opposite posture (certified-firmware terminals only, BYO terminal explicitly refused) and its integrations page lists only PayPal Reader, sunday, inKind and Atlas under Payments — none of them a general-purpose card processor substitute. No vendor documentation of third-party processing on K-Series. Unknown, leaning unfavorable. adversarially verified

payments-published-rates differentiator

Neither first-party page carries a rate. The payments page redirects — 'View our competitive processing rates on our pricing page' — and the pricing page publishes software tiers and a $30/screen/month KDS line and no card-processing rate at all. The only published payment figures anywhere are a $15 chargeback fee and two-business-day deposits. https://www.lightspeedhq.com/pos/restaurant/pricing/ · retrieved 2026-08-02 adversarially verified

payments-dual-pricing differentiator

The Lightspeed Payments FAQ enumerates exactly one card-cost-offset mechanism - surcharging ('Surcharging with Lightspeed Payments is available from the Settings page') - and mentions no dual pricing, no cash discounting and no separate cash/card price storage. Nothing in the payments documentation set (FAQ, Surcharging with Lightspeed Payments, Processing service charges) or the menu pricing docs describes storing two prices per item or printing cash and card totals side by side on the check. Surcharging is the vendor's documented alternative. https://k-series-support.lightspeedhq.com/hc/en-us/articles/15214224728987-Lightspeed-Payments-FAQ · retrieved 2026-08-03

payments-surcharge-guardrails differentiator

All three named elements are documented. Exclusions: 'Debit and prepaid cards (US and Canada)' are excluded from surcharging automatically, alongside card-not-present transactions. Caps: the surcharge must not exceed the processing rate the merchant is charged and 'can never exceed 3%' in the US (2.4% in Canada). Location control: enabled from the settings for the business/location, and 'Surcharging cannot be enabled for locations in the province of Quebec.' Gates worth knowing: Lightspeed Payments only, Australia/Canada/US only, At Sale payment authorization mode only, and Mobile Tap terminals excluded. https://k-series-support.lightspeedhq.com/hc/en-us/articles/12625085075995-Surcharging-with-Lightspeed-Payments · retrieved 2026-08-03

payments-emv-nfc

Chip and contactless run on a closed certified fleet (Verifone P400+, V400m, e285/e280, Mobile Tap, AMS1, S1F2). Tap to Pay on iPhone documentation names the wallet directly - 'accept Apple Pay, contactless credit and debit cards, and other digital wallets'. Google Pay is named only on the payments product page (grade C), which lists 'American Express, Visa, Mastercard, Diners, Discover, JCB, UnionPay' plus Google Pay and Apple Pay; it is not enumerated in support documentation. https://k-series-support.lightspeedhq.com/hc/en-us/articles/10071706424347-Tap-to-Pay-on-iPhone-with-Lightspeed-Payments · retrieved 2026-08-02 adversarially verified

payments-softpos-tap-to-pay differentiator

'With Tap to Pay on iPhone, Lightspeed Payments gives you the ability to accept payments directly on your iPhone with no additional hardware required', accepting Apple Pay, contactless cards and wallets. Requirements: iPhone XR or above, iOS 18.4+, a Lightspeed Payments account, Lightspeed Restaurant for iOS 24.2+; enabled under Payment > Payment methods > Lightspeed Payments > Tap to Pay for iPhone. iPhone only; no Android tap-to-pay is documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/10071706424347-Tap-to-Pay-on-iPhone-with-Lightspeed-Payments · retrieved 2026-09-03 adversarially verified

payments-pay-at-table

All three elements documented separately: mobile terminals (Verifone e285/e280, V400m, Mobile Tap, AMS1, S1F2) are carried to the table; 'For payment terminals with a screen, such as the Smart Terminal, customers can tip on the terminal itself' and 'If prompted, the customer confirms the tip amount on the payment terminal'; and the check splits by seat via Distribute by seat before payment. The card never leaves the guest. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4415116773403-Handling-tips-and-gratuities · retrieved 2026-08-02 adversarially verified

payments-qr-guest-pay differentiator

'Scan and Pay allows customers to pay for Order Anywhere orders by scanning the QR code attached to their specific table after their meal. From their mobile device, customers can pay by debit or credit card, split the bill with others, and receive an email receipt' (Order Anywhere Back Office > Settings > Payment settings > Scan and pay). The guest flow ('Scan the unique QR code on your table... Tap Pay the bill', split by amount or by item) is in Placing orders using Order Anywhere; payments sync to the POS and 'the order will be removed from the order management screen automatically when the check is fully paid' when enabled in the order profile. Payment methods also expose 'Initiate payment via QR code'. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260803521850-Enabling-payments-for-Order-Anywhere · retrieved 2026-08-05

payments-tip-adjust

Tips and gratuities handling documented including declared tips; batch/adjust window and an unadjusted-tip manager screen are not. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4415116773403-Handling-tips-and-gratuities · retrieved 2026-08-01

payments-tip-pooling differentiator

Synced tip pools with automated calculation are delivered through the 7shifts partnership, not natively in the POS. https://www.lightspeedhq.com/pos/restaurant/payroll/ · retrieved 2026-08-01

payments-offline-store-and-forward differentiator

Offline card store-and-forward is documented for Lightspeed Retail X-Series, not for Restaurant K-Series.

payments-offline-decline-liability differentiator

K-Series documents no store-and-forward offline payments mode at all, so neither half of the claim is published. The vendor's documented internet-outage fallback is standalone mode - payments processed directly on the terminal 'as a fallback in case of an internet outage' - and those payments 'do not generate a receipt ID and are reported exclusively in the Payments report'; no offline queue, no post-reconnect decline handling and no failed-offline-payments report appear there, in the Lightspeed Payments FAQ, or in the Troubleshooting Lightspeed Payments article (all retrieved 2026-08-04). The gap is product-specific: Lightspeed documents exactly this for Retail X-Series ('Each payment with the Offline declined status represents a loss') but publishes nothing equivalent for Restaurant K-Series. https://k-series-support.lightspeedhq.com/hc/en-us/articles/5028210082715-Standalone-payments · retrieved 2026-08-04

payments-gift-cards

First-party stored value is a documented product set — Gift cards 2.0: About / Setting up / Using at the POS / Selling online / Importing / Printing. Shortfall: the article addresses neither redemption across every location in a group nor real-time balance tracking, both named in the claim; cross-location gift-card behaviour is unresolved across this record. Selling gift cards online additionally requires Lightspeed Payments. https://k-series-support.lightspeedhq.com/hc/en-us/articles/6339161622427-About-gift-cards-2-0 · retrieved 2026-08-02 adversarially verified

payments-house-accounts

On-account charging is native: orders are tendered to the Invoice payment method (code IKDEBT), accumulate on the Back Office Accounts receivable page per customer, show as a running Balance on the customer profile at the POS, and 'Make invoice' generates a single invoice for all of a customer's pending invoice orders, which can then be settled, viewed, and exported (PDF/CSV/XLSX). ID cards can bill 'the guest's consumption through the generated account'. Shortfall: no per-account credit limit setting is documented, and statements are on-demand batch invoices rather than periodic statement runs. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4403941259291-Managing-customer-invoices-in-the-Back-Office · retrieved 2026-08-05

payments-split-tender

Split by seat and by covers documented; multi-tender settlement and any split cap are not. https://k-series-support.lightspeedhq.com/hc/en-us/articles/360051089493-Check-splitting · retrieved 2026-08-01

payments-refund-void-controls

Role-based authorization is documented: per-user-group permissions for 'Order refunds' ('void and refund processed transactions'), 'Partial refunds', 'Order reopen via refund', 'Line voids' ('cancel items that have already been sent to production') and 'Cash drawer access' ('open the cash drawer without processing a transaction'), plus group-scoped discount availability ('define which discounts this user group can apply'). Shortfall: the audit half is not documented as identifying the approver - the Cancellations and Corrections report's columns are Receipt ID, Account, Item, Qty, Amount, Date, Reason and Reason #2 with no user field, and while the Invoices report exposes a per-check Journal 'event log used for auditing purposes', neither approver identity nor immutability is documented for it. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804594730-Managing-POS-user-groups · retrieved 2026-08-03

payments-chargeback-tooling differentiator

In-product dispute dashboard, not an email chase: 'From the Disputes tab, you can view the status of all current and past chargeback disputes, including the response deadline, current status, reason for the dispute, and total amount of the dispute.' Merchants open a dispute, click Challenge dispute, and 'drag and drop or select any relevant evidence' with typed evidence categories including transaction details and proof of refund. Evidence is gathered by the merchant rather than auto-assembled from the transaction record; the fee is described as a non-refundable chargeback fee without a published amount. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4402294260251-Managing-chargebacks-with-Lightspeed-Payments · retrieved 2026-08-02 adversarially verified

payments-card-on-file differentiator

'By creating an account, customers can add credit and debit cards to a digital wallet in Order Anywhere... payment and contact details will be pre-filled at checkout'; the default card is auto-selected and cards are managed under profile > Wallet. Shortfall: the stored card is usable only inside Order Anywhere online checkout - no documented reuse for phone orders or in-store POS payments (in-store manual entry requires keying the card each time). https://k-series-support.lightspeedhq.com/hc/en-us/articles/6732200120091-Managing-customer-accounts-in-Order-Anywhere · retrieved 2026-08-05

payments-payout-timing differentiator

Schedule published and faster funding offered. K-Series docs enumerate 'three types of payouts with varying schedules: Scheduled: A scheduled daily payout. Funds are usually paid out within 1-3 business days. Same-day: An instant payout configured to pay out automatically at a set time each day. Funds are paid out within 30 minutes. Instant: An instant payment that you can manually request... Funds are paid out within 30 minutes.' Same-day is a self-serve toggle (Financial Services > Settings > Payouts > 'Enable same-day payout') with a chosen daily time. The companion article 'Getting paid with Lightspeed Payments' publishes the standard schedule in detail: 6 AM local batch cutoff and 'settlements deposited into your bank account within 2 business days after the original transaction,' with a day-by-day settlement table. Priced, not free: instant 1%-1.75% and same-day .5%-1.5% of the payout by region, min $150, max $9,999 per deposit / $15,000 per 24 hours, US/UK/EU/AU and eligibility-reviewed. https://k-series-support.lightspeedhq.com/hc/en-us/articles/28477493132571-Receiving-Instant-Payouts-with-Lightspeed-Payments · retrieved 2026-08-09 adversarially verified

payments-p2pe-pci4

Lightspeed's own published Attestation of Compliance (ControlCase QSA, Gerald Drake III) covers 'Lightspeed e-commerce and retail Card Tokenization Service (CTS); Lightspeed Cloud Point of Sale Application' and states 'Lightspeed is a PCI DSS Level 1 Service Provider'. On encryption: 'Lightspeed K and L series support P2PE compliant devices and PTS compliant magnetic stripe readers... employ encryption technology that come preconfigured from the payment gateways'. Shortfall: the attestation is PCI DSS v3.2.1, based on a ROC dated January 11, 2024 and signed February 2024 - not the 4.x the claim requires - and 'P2PE compliant' devices are not a PCI SSC validated P2PE solution listing. https://pdf.lightspeedhq.com/documentation/PCI_AOC_R-C-X-K-L-O-G-Payments.pdf · retrieved 2026-08-02 · not refetchable · site policy · graded A when read adversarially verified

kitchen-station-routing

Operator-configured in Back Office with no vendor involvement: stations are created by name ('Enter a unique name for this KDS screen, with a maximum of 25 characters') and items routed to them - 'Select which items you wish to have routed to this station', with the article's own example being 'you might want the Menu categories > Alcohol items to go to this station if it's for a bar area', or 'All items' for a single-station kitchen. Routing by item and by menu category is documented; order type and revenue center are not, which the claim's or-list does not require. https://k-series-support.lightspeedhq.com/hc/en-us/articles/22168531609499-Setting-up-Kitchen-Display-System-2-0 · retrieved 2026-08-02 adversarially verified

kitchen-expo-consolidation

Re-checked the KDS 2.0 setup and usage articles on 2026-08-02 against the claim as written. Stations, per-station routing, an Items list and a Condensed view are documented; an expo or pass screen that consolidates one guest check across multiple prep stations and withholds completion until every contributing station has bumped is not described anywhere. Absence of documentation, not proven absence. adversarially verified

kitchen-course-firing differentiator

POS Configurations > Order Management documents 'Coursing options: Assign groups to specific courses to manage course firing and meal pace', 'Automatically fire the first course', and that 'Courses beyond the first are not fired automatically by default'. On the POS, 'When the POS user is ready to have the second course fired, they can tap the Fire course button' (Adding orders in Table Service mode, 360051089273); KDS 2.0 shows 'Tickets on hold or unfired' and the course number. Firing is from the POS (iPad or iPhone); no expo-screen fire is documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804606610-Managing-and-understanding-POS-configurations · retrieved 2026-09-03 adversarially verified

kitchen-prep-time-pacing differentiator

KDS timing settings are enumerated and are ticket-level lateness flags, not per-item cook-time pacing: 'Enable Timer... Average: Displays the expected wait time for completed orders... Delayed After: the elapsed time after which KDS will flag a ticket as being delayed... Late after: ...flag a ticket as being late' (orange/red pulse). No per-item cook time field exists anywhere in menu or KDS configuration, and no staggered start/display logic to land items simultaneously is documented in KDS 1.0 or 2.0. https://k-series-support.lightspeedhq.com/hc/en-us/articles/22708154090267-Using-the-Kitchen-Display-System-2-0 · retrieved 2026-08-05

kitchen-order-throttling differentiator

Order Anywhere service profiles carry a configurable order-volume cap that automatically refuses further orders in a slot once crossed: 'Limited orders: Click this option to restrict the number of orders taken. In the Orders per time-slot field, enter the number of orders accepted in each time slot duration. For example, accept only five orders every 15 minutes,' paired with 'Time slot duration: The time in minutes between future orders.' Crossing the cap defers the customer to a later slot, which paces release of incoming digital orders automatically. Shortfall: the cap applies only to Order ahead (scheduled) orders and is not available on the Table profile, so ASAP orders are unthrottled; there is no ticket-time or kitchen-load trigger; and quoted times are never extended automatically - 'you can edit prep time to better match current production speed' is a manual POS action, as is the Control center 'Online orders enabled' kill switch. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407098296091-Managing-Order-Anywhere-service-profiles · retrieved 2026-08-06

kitchen-channel-pause-propagation differentiator

Item-level 86 propagates natively to Order Anywhere and Uber Eats: snoozing via the OA-Availability web extension on the POS makes items unavailable online, and 'you can snooze Uber Eats in Order Anywhere... you will need to have item availability activated'; sales restrictions auto-mark items 'unavailable in Order Anywhere (or other supported third-party partners)' at zero stock. Uber Eats ordering can be paused from Integration Hub > Online ordering and delivery > Uber Eats ('use the toggle... to pause or enable ordering'). Shortfalls: DoorDash/Grubhub run through the separate Deliverect (Lightspeed Delivery) product, pause is Back Office not POS/KDS, and no timed auto-reactivation exists for the marketplace pause. https://k-series-support.lightspeedhq.com/hc/en-us/articles/25724049883675-Setting-up-the-Uber-Eats-integration · retrieved 2026-08-05

kitchen-order-ready-callback differentiator

'If you have a third-party online ordering integration installed, a Ready to collect notification is sent to them when you update the status in KDS.' The March 2026 release notes (47746434645275) add: 'Orders marked ready on the KDS now trigger automatic notifications to integrated third-party ordering platforms. There's no need to update it again on the POS' (app version 24.6 or later). Which marketplaces act on the signal is not enumerated. https://k-series-support.lightspeedhq.com/hc/en-us/articles/22708154090267-Using-the-Kitchen-Display-System-2-0 · retrieved 2026-09-03 adversarially verified

kitchen-bump-bar-hardware

Lightspeed's own KDS 2.0 is operated by 'Double-tapping the ticket' or 'Tapping and holding the ticket' on an iPad; no bump bar is listed in Supported hardware. Bump-bar support is documented only for the partner Fresh KDS integration: 'Support for label printing and bump bar functionality.' Shortfall: partner-delivered, and no supported bump-bar models are named by Lightspeed. https://k-series-support.lightspeedhq.com/hc/en-us/articles/11432070108827-Setting-up-the-Fresh-KDS-integration · retrieved 2026-09-03 adversarially verified

kitchen-all-day-counts

The Items list view does aggregate: 'When the same item is ordered across many tickets... the KDS can display the ordered items combined together across all of the tickets so the station knows how many of each item needs to be prepared,' with bulk status updates from that view. Shortfall: aggregation is per item only. Modifiers appear as 'Accompanying instructions for each item in the list' - listed per line, never rolled up into a per-modifier count - so a cook cannot read an all-day quantity for a modifier, which is the second half of the claim. https://k-series-support.lightspeedhq.com/hc/en-us/articles/22708154090267-Using-the-Kitchen-Display-System-2-0 · retrieved 2026-08-02 adversarially verified

kitchen-sla-alerts

Two operator-set thresholds per KDS station with colour escalation: 'Delayed After: This is the elapsed time after which KDS will flag a ticket as being delayed, in minutes. Delayed tickets will pulse with an orange glow' and 'Late after: ... Late tickets will pulse with a red glow.' The claim asks for colour escalation and/or an audible alert; the visual half is documented, audible is not, and no manager-device escalation or speed-of-service report exists. https://k-series-support.lightspeedhq.com/hc/en-us/articles/22708154090267-Using-the-Kitchen-Display-System-2-0 · retrieved 2026-08-02 adversarially verified

kitchen-printer-fallback differentiator

The printer half is documented as an ordered fallback list: 'The first printer listed will be the main printer, followed by fallback printers,' and 'If this printer is turned off or cannot print, the device will attempt to print on the second printer in the list, and so on,' with an optional _BACKUP PRINTER_ header stamped on rerouted tickets. Shortfalls: no failover for a dead KDS screen is documented anywhere in the KDS 2.0 set - the setup article's only guidance when 'a Hub or KDS display disconnects' is to check the network, and a disconnected screen's sync count 'will stall until the connection is restored' - and no article states the no-ticket-loss guarantee the claim requires. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804607010-Managing-printing-profiles · retrieved 2026-08-04

kitchen-offline-operation differentiator

Internet down, LAN up: 'Kitchen Display System: KDS remains function[al] as it connects via the local network.' The limit is named too: if the local network is also lost, 'KDS is not functional as it connects via the local network.' https://k-series-support.lightspeedhq.com/hc/en-us/articles/53028167251867-Offline-POS-functionality · retrieved 2026-09-03 adversarially verified

kitchen-item-build-screens differentiator

Beyond ticket line text, production instructions ('preparation notes that can be manually added or automatically tied to an item... the POS will prompt the server to include the relevant preparation info') and modifiers flow to production tickets and KDS stations, and KDS ticket content is configurable (Customer, Order ID, Server, Type, Floor, Order Source, Pickup Time toggles). Shortfall: instructions are text notes only - no recipe steps, portioning specs, images, or structured build cards can be displayed at a station. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804656349-About-production-instructions · retrieved 2026-08-05

kitchen-pizza-fractional-display differentiator

No fractional topping model is documented anywhere in the menu engine, so there is nothing to render.

kitchen-recall-refire

KDS 2.0 documents advancing a ticket or item to the next status ('bumping') by double-tap or tap-and-hold, and an Undo that reverts completed items — but only within a five-second window, which is a mis-tap guard rather than recall. Returning a bumped ticket to an active state after that window, refiring an individual item to a station, or reprinting it, is not described in the setup or usage articles. adversarially verified

kitchen-order-modification-alerts differentiator

When an order is modified from the POS, 'its order ticket will blink with the new information until a user taps on it to confirm the update,' and new orders announce with a bell. Shortfall: the alert is ticket-level with acknowledgement, not the item-level flagging of added, changed or removed lines the claim describes — the cook is told the ticket changed, not which line changed. https://k-series-support.lightspeedhq.com/hc/en-us/articles/22708154090267-Using-the-Kitchen-Display-System-2-0 · retrieved 2026-08-02 adversarially verified

kitchen-guest-ready-notification differentiator

A guest-facing status board exists: the Order Display Screen 'displays order numbers on an external screen so customers can see the status of their order, whether it is in progress or ready for pickup. The screen updates automatically as POS users manage orders in the... app or on a Kitchen Display System.' Order Anywhere guests also get email status updates ('Your order confirmation, status updates, and receipt will be sent to the email provided'). Shortfalls: the ODS 'is available as a paid add-on to your existing Lightspeed Restaurant subscription' (claim requires no separate purchase), and no SMS or push notification on bump exists. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4413369711771-About-Lightspeed-Order-Display-Screen · retrieved 2026-08-05

kitchen-waste-logging

Waste can be flagged at the POS via wastage discounts - 'Discount indicates wastage: Enable this if the reason for this discount is food waste... Items that have this type of discount applied will appear as a loss in your reports' - and the Inventory module's Wastage feature records waste events with reasons and value and adjusts stock. Shortfall: neither runs on the kitchen/KDS screen; KDS supports ticket actions only, so kitchen staff cannot log waste or remakes with reason codes from the station display. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804657089-Understanding-discounts · retrieved 2026-08-05

kitchen-speed-of-service-reporting

KDS Statistics reports 'the total number of products prepared, the average preparation times for each product, and which products are prepared fastest or slowest', with a per-item Heatmap of production time across a 24-hour timeline and by day of week, plus a Modes distribution of production speeds. Shortfalls against the claim: per-item rather than per-ticket/per-station, no percentile figures, and no slicing by order channel; Lightspeed Tempo adds table-service timing analytics but not kitchen station times. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4403156122651-KDS-Statistics · retrieved 2026-08-05

kitchen-prep-forecasting

Inventory 'Produce' covers batch production and recipe management; a demand-forecast-driven prep list is not documented.

delivery-driver-roster

Nothing in the K-Series help centre, the integrations catalogue or the QSR product page describes an in-house driver entity, dispatch board or driver settle-up. The QSR page's delivery language is entirely marketplace aggregation: 'Get orders from UberEats, Foodora or DoorDash sent directly to your POS.' Positive evidence of absence. https://www.lightspeedhq.com/pos/restaurant/quick-service-restaurant-pos/ · retrieved 2026-08-01 adversarially verified

delivery-dispatch-board

The 'one screen' delivery view consolidates third-party orders, not driver dispatch. No dispatch board documented.

delivery-route-map differentiator

First-party delivery's complete documented feature set is enumerated in the self-delivery release note - 'Self-delivery enables merchants to: Offer delivery service to customers using your own couriers, Create a geographic delivery zone, and Set a delivery time estimate, fee, and minimum order total by delivery zone' - and the matching Delivery settings in Managing Order Anywhere service profiles (zone, fee, minimum, estimated time). There is no dispatch board, no map of stops, and no route sequencing anywhere in the product; courier logistics beyond that are delegated to Uber Direct. https://k-series-support.lightspeedhq.com/hc/en-us/articles/34339315446171-What-s-new-Self-delivery-for-Order-Anywhere · retrieved 2026-08-05

delivery-driver-tracking differentiator

No driver-facing app exists. Self-delivery's documented capabilities are limited to 'Offer delivery service to customers using your own couriers, Create a geographic delivery zone, and Set a delivery time estimate, fee, and minimum order total by delivery zone.' No article describes capturing driver GPS or any dispatch screen; for outsourced delivery, couriers belong to Uber Direct/Uber Eats and their position is not surfaced in Lightspeed. https://k-series-support.lightspeedhq.com/hc/en-us/articles/34339315446171-What-s-new-Self-delivery-for-Order-Anywhere · retrieved 2026-08-05

delivery-zones-polygon differentiator

Delivery areas support free-form map polygons, not just radius: 'Set one or multiple zones to deliver within by clicking Create new... Radius: Choose this option to create a delivery area based on distance. Custom shape: Choose this option to draw a custom delivery area on the map.' Since January 2025, 'you can define multiple delivery zones with customizable fees and minimum order requirements for each area' (What's new: January 2025). https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407098296091-Managing-Order-Anywhere-service-profiles · retrieved 2026-08-05

delivery-zone-pricing

Per-zone economics are documented for Order Anywhere delivery service profiles: one or multiple zones, each radius-based ('create a delivery area based on distance') or drawn ('draw a custom delivery area on the map'), each carrying 'a delivery fee to be applied to each order', 'a minimum amount an order needs to reach before you'll deliver' and 'an estimated delivery time in minutes to display to the customer'; fulfilment by own staff or Uber Direct. Shortfall: the article never describes address validation or the automatic assignment of an order to its zone from the customer's entered address - the claim's application mechanism is undocumented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407098296091-Managing-Order-Anywhere-service-profiles · retrieved 2026-08-03

delivery-address-validation

Delivery ordering is gated by map-defined zones: profiles carry one or more delivery areas (radius or custom shape drawn on a map) each with its own fee, minimum order, and time estimate, so a customer's address is resolved against zones at checkout to price and permit delivery. Shortfall: the docs never describe the validation behavior itself - no statement of geocoding provider, rejection/flagging UX for out-of-zone addresses, or address-correction handling. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260803546769-Creating-Order-Anywhere-service-profiles · retrieved 2026-08-05

delivery-driver-comp differentiator

No driver entity exists in the product. Self-delivery's enumerated scope is zones, fees, minimums, and time estimates with 'your own couriers'; there is no per-delivery assignment record, no mileage or reimbursement capture, and no payroll export of any kind (labor features are clock-in/out hours plus tip declaration; payroll/scheduling is delegated to the 7shifts integration). Nothing to compute per-delivery compensation from is present. https://k-series-support.lightspeedhq.com/hc/en-us/articles/34339315446171-What-s-new-Self-delivery-for-Order-Anywhere · retrieved 2026-08-05

delivery-cash-reconcile

Per-user cash accountability exists via user banks: every POS user has a 'user bank, or wallet... set up by default', counted at shift start/end, with the Shift/User reports computing 'Overage: Dollar value based on the discrepancy between what should be in the cash drawer and what was counted' - so a driver clocked in as a POS user gets a per-person over/short. Shortfall: nothing links orders or deliveries to a driver, so there is no delivery-specific settle-up (orders assigned vs cash collected vs tips owed); it is generic drawer accountability only. https://k-series-support.lightspeedhq.com/hc/en-us/articles/360050436394-Managing-cash-drawer-operations · retrieved 2026-08-05

delivery-daas-dispatch

Uber Direct is a listed integration; partner UEAT routes to DoorDash Drive and Uber Direct. Whether courier quotes and status return into the POS order record is not documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/36914000260891-Setting-up-and-using-the-UEAT-integration · retrieved 2026-08-01

delivery-daas-fallback differentiator

Dispatch mode is a static per-profile choice, not a rule: 'You can choose to offer delivery using your own staff or through Uber Direct' - the profile's Delivery section is configured to one or the other ('Choose Delivery by my staff... or Delivery via Uber Direct'). No overflow, timeout, or zone-based fallback rules exist; the Uber Direct setup article confirms its delivery range is 'a fixed distance dependent on country' and 'cannot be edited'. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407098296091-Managing-Order-Anywhere-service-profiles · retrieved 2026-08-05

delivery-3p-direct-integration differentiator

Uber Eats has a direct K-Series integration. DoorDash and Grubhub reach the POS through Deliverect, which Lightspeed resells as 'Lightspeed Delivery by Deliverect'. https://www.lightspeedhq.com/pos/restaurant-k-series/integrations/ · retrieved 2026-08-01

delivery-3p-injection

Injection itself is real and real-time: menus sync 'from Back Office to platforms like DoorDash and Uber Eats, then have online orders sent straight to your POS device', and 'Once an order is accepted from the delivery channels, it's sent to your POS device in real time.' Shortfall: the path is Deliverect middleware, not a native Lightspeed integration - the setup procedure begins 'Request a demo from Deliverect', so the operator signs a second contract with a third party, and no cost is published on either side. https://k-series-support.lightspeedhq.com/hc/en-us/articles/25208938481691-Setting-up-the-Deliverect-integration · retrieved 2026-08-02 adversarially verified

delivery-menu-push

Menu syncs from Back Office out to DoorDash/Uber Eats through the Deliverect-based Lightspeed Delivery. Shortfall: channel-specific price markups — explicitly part of the claim, and the lever that makes marketplace margin work — are not documented, nor is photo publication. Sync yes; per-channel price books not established. https://k-series-support.lightspeedhq.com/hc/en-us/articles/25208938481691-Setting-up-the-Deliverect-integration · retrieved 2026-08-02 adversarially verified

delivery-86-sync

Item-level out-of-stock sync is documented for Order Anywhere and Uber Eats: items snoozed from the POS (OA-Availability web extension) go 'Currently unavailable' online with timed auto-unsnooze, and sales restrictions mean 'When items reach zero quantity, these items are automatically marked as unavailable in Order Anywhere (or other supported third-party partners)... When inventory is restocked, the item automatically becomes available once again'; the Uber Eats FAQ confirms snoozing Uber Eats items via Item availability. Shortfalls: modifier/item-option 86 is not documented (DoorDash's standard requires item-option 86ing), and DoorDash/Grubhub availability runs through the separate Deliverect product, not this mechanism. https://k-series-support.lightspeedhq.com/hc/en-us/articles/10724827631259-Setting-up-and-using-Item-availability · retrieved 2026-08-05

delivery-store-pause

Uber Eats can be paused from inside Lightspeed: 'The Back Office allows you to pause Uber Eats orders. Navigate to Integration Hub > Online ordering and delivery > Uber Eats and use the toggle... You can also pause orders from the Manage Uber Eats page by clicking Pause orders.' First-party profiles pause from the POS itself (Order Anywhere web extension > Order Profiles > Pause orders). Shortfalls: no timed auto-reactivation for either pause, marketplace pause is Back Office (browser) rather than the POS app, and DoorDash/Grubhub pausing is not documented (they ride Deliverect). https://k-series-support.lightspeedhq.com/hc/en-us/articles/25724049883675-Setting-up-the-Uber-Eats-integration · retrieved 2026-08-05

delivery-3p-reconciliation differentiator

Order-level payment reconciliation exists: the Online orders report (Operations > Online orders) shows per-order 'Online payment: The total amount paid on the order via the third-party integration', 'Payment over/under: The total amount over or under if the total in the integration doesn't match the total from the POS', 'Total corrections for period', and per-order failure reasons. Shortfall: nothing matches marketplace payout deposits to recorded sales or itemizes commission/marketing fees - reconciliation stops at order-amount differences (the documented payment difference tolerance, default $0.02). https://k-series-support.lightspeedhq.com/hc/en-us/articles/38418918961819-Understanding-the-Online-orders-report · retrieved 2026-08-05

delivery-injection-error-visibility differentiator

Failed injections are visible per order in two places: the Lightspeed Delivery (Deliverect) dashboard statuses include 'Failed: There was an issue sending the order to Lightspeed', 'Parsed', 'POS failed', 'Receipt not found', and 'Rejected'; the Order Anywhere Orders page shows 'Failed: An error prevented the order from being received at the POS' and the Back Office Online orders report exposes 'Issue: The reason that the order was unsuccessful'. Shortfalls: no per-channel connection-status view and no proactive alerting on failure is documented - the operator must be watching the dashboards. https://k-series-support.lightspeedhq.com/hc/en-us/articles/5780735561883-Viewing-orders-in-the-Lightspeed-Delivery-Dashboard · retrieved 2026-08-05

delivery-tracking-page

Guests get order-status visibility but not driver tracking: 'Your order confirmation, status updates, and receipt will be sent to the email provided', and the Order Anywhere account Orders page shows 'Any current orders that are pending or in preparation' plus failed orders 'so there is no question whether an order went through or not'. Shortfall: no branded tracking page with courier position or delivery progress exists for self-delivery or Uber Direct orders - status is order-state emails and the account history page only. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260803553189-Placing-orders-using-Order-Anywhere · retrieved 2026-08-05

delivery-promise-time differentiator

Quoted times are operator-entered constants, documented as such: 'Order preparation time: Choose to set an average preparation time in minutes or omit any time estimate', and per delivery zone 'Estimated delivery time: Enter an estimated delivery time in minutes to display to the customer.' Load-responsiveness is manual: 'you can edit prep time to better match current production speed. Edited prep times only affect orders placed after the time was changed.' No automatic adjustment from kitchen load, driver availability, or drive time exists. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407098296091-Managing-Order-Anywhere-service-profiles · retrieved 2026-08-05

delivery-offline-behavior

The claim requires documented offline behavior for delivery; Lightspeed documents the opposite precondition: 'Before you begin fulfilling orders from Order Anywhere, make sure that: Your POS device is online and connected to the internet.' The OA order lifecycle (Pending until 'received by the POS', Failed 'if the Restaurant POS app is not open') shows online orders do not flow during an outage, and no article addresses cash delivery orders, driver assignment, or settlement offline. General offline guidance is one line - 'most basic order-taking functions will still work offline' (Troubleshooting network issues) - with nothing delivery-specific. https://k-series-support.lightspeedhq.com/hc/en-us/articles/23267765915547-Fulfilling-orders-from-Order-Anywhere · retrieved 2026-08-05

digital-first-party-web

Order Anywhere is first-party and branded - setup includes 'Upload a banner image or logo to display at the top of your customer-facing Order Anywhere page' and separate light and dark mode logos - and it 'integrates directly with the Restaurant POS app' for takeaway, pickup and in-restaurant table orders. Commission-free is a vendor product-page claim ('0% commission, no marketplace fees', 'fully branded experience with a white-label solution'), grade C. It is a paid add-on to any Lightspeed Restaurant subscription, not a Starter-tier-only charge, and a custom domain is not documented - the page is Lightspeed-hosted. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260803518310-Setting-up-Order-Anywhere · retrieved 2026-08-02 adversarially verified

digital-menu-single-source

Order Anywhere is first-party ('our integrated online ordering system') and orders land in the POS, but the vendor article describes setup via order profiles and refers pricing and feature questions to Lightspeed Support. Shortfall: it never states that the digital menu is generated from the Back Office menu record, so single-source-of-truth behaviour is inferred rather than documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4686224687259-Online-ordering · retrieved 2026-08-01 adversarially verified

digital-native-app differentiator

No branded native consumer ordering app documented; partner UEAT offers branded apps.

digital-account-saved-payment

Accounts with tokenized cards are documented: customers 'log in with your Google or Apple account or with the email address and password' used at sign-up, can 'add credit and debit cards to a digital wallet in Order Anywhere' and save contact info, with payment and contact details 'pre-filled at checkout' and the default card auto-selected. Shortfalls: saved delivery addresses and one-tap reorder of a previous order are not documented anywhere in the Order Anywhere account articles - the claim's reorder element is absent from the vendor's description. https://k-series-support.lightspeedhq.com/hc/en-us/articles/6732200120091-Managing-customer-accounts-in-Order-Anywhere · retrieved 2026-08-03

digital-upsell-engine differentiator

Algorithmic and configurable suggestions exist in Order Anywhere: 'Use smart upselling, powered by AI, to recommend specific products... These recommendations are based on your sales data and automatically update daily' (Popular items, 3-8 recommendations, requires 150+ orders in past 21 days), and operators can override by 'removing dishes you don't want to feature or pinning high-margin items, daily specials or surplus stock' (Menu > Menu Upsells, July 2026). Shortfall: no attach-rate reporting on the suggestions is documented anywhere in OA reports. https://k-series-support.lightspeedhq.com/hc/en-us/articles/50574509323291-Understanding-Menu-upsells-in-Order-Anywhere · retrieved 2026-08-05

digital-scheduled-pacing

Scheduled orders with per-slot caps: Order ahead supports 'Maximum days ahead', 'Time slot duration: The time in minutes between future orders', and 'Limited orders... enter the number of orders accepted in each time slot duration. For example, accept only five orders every 15 minutes' - full slots stop accepting orders. Release to the kitchen is also paced: a future pickup order syncs to the POS 'at the selected pickup time minus your preparation time and a few additional minutes' (Fulfilling orders from Order Anywhere), with a POS Future orders tab (Later today / Tomorrow / Future upcoming). https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407098296091-Managing-Order-Anywhere-service-profiles · retrieved 2026-08-05

digital-fulfillment-modes

Pickup/delivery/dine-in/curbside are documented for the UEAT partner integration; the same breadth for first-party Order Anywhere is not documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/36914000260891-Setting-up-and-using-the-UEAT-integration · retrieved 2026-08-01

digital-qr-table

Documented end to end: 'Open the restaurant's Order Anywhere page by scanning the specific QR code assigned to your table', tipping ('Select a tip option or enter a custom tip amount in the Tip section'), payment choice ('Card to pay online or Pay before leaving to pay in person'), and splitting both ways - 'To split the bill by amount, click By amount' and 'To split the bill by item, click By item and select the items you'd like to pay for.' Scan and Pay lets guests settle a table order after eating without waiting for a server. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260803553189-Placing-orders-using-Order-Anywhere · retrieved 2026-08-02 adversarially verified

digital-kiosk differentiator

Assessed and unresolved, on the same evidence as order-capture-kiosk-first-party. The claim requires a kiosk running the same menu and modifier logic as the POS, an accessibility-compliant UI and unattended EMV. No K-Series kiosk documentation exists; kiosk support articles are published only for L-Series and O-Series. The AU Lightspeed Kiosk page asserts 'Orders flow straight into Lightspeed POS and Payments' but describes no menu synchronisation, no payment device and no accessibility conformance. adversarially verified

digital-group-ordering

Assessed and unresolved. The feature K-Series documents under the name Group Ordering ('Setting up and using Group Ordering', retrieved 2026-08-04) is a staff-side counter tool - servers ring up each customer's order individually by table and the system batches them onto one kitchen ticket on a timer - with no shareable link, no spend caps and no split-payment mechanic. The Order Anywhere consumer articles document individual ordering only, and whether multiple guests scanning the same table QR even land on one check is itself undocumented (see order-capture-qr-same-check). No vendor page affirms or denies a shareable group-cart with per-person or total spend caps, so this stays unknown rather than no.

digital-catering-portal differentiator

Order Anywhere's order types are exhaustively enumerated - 'Select order type: Click this button to switch between Pickup and delivery, Table, and Menu browsing profiles' - and none is a catering flow; no catering menu, minimum, lead-time, quote, or deposit setting exists in OA. The deposits and customer-invoice features live in the POS/Back Office, not in any guest-facing ordering portal, and Lightspeed's restaurant integration directory lists no catering-portal partner (checked 2026-08-05). https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407098296091-Managing-Order-Anywhere-service-profiles · retrieved 2026-08-05

digital-voice-ai-phone differentiator

The prior no rested on the public Lightspeed integration directory returning no AI phone partner. An app directory is not an exhaustive enumeration, and it demonstrably missed at least one telephony partner: Lightspeed publishes an integration page for Voicee, a cloud phone system with caller ID and call flows, listed as compatible with Lightspeed Restaurant POS (O-Series). Separately, Goodcall advertises an AI phone assistant integrating with Lightspeed Restaurant through its API, but that is a partner's own marketing and does not establish certification by Lightspeed or order injection without staff transcription. The K-Series help centre (all 528 articles retrieved via the Help Center API on 2026-08-06) contains no voice-ordering documentation, and Lightspeed AI is a Back Office analytics assistant rather than an ordering agent. Whether Lightspeed offers or certifies AI voice phone ordering that lands the order in the POS is unresolved.

digital-drivethru-ai

There is no drive-thru mode to attach voice AI to: no drive-thru workflow, hardware, or configuration appears in any of the 527 help-centre articles; the supported-hardware catalog enumerates peripherals with no lane displays or headset systems; and neither the help centre nor the public integration directory names any drive-thru voice partner (checked 2026-08-05). https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260800124209-Supported-hardware · retrieved 2026-08-05

digital-sms-ordering

The prior no cited the Gift cards 2.0 FAQ, which speaks only to how a gift card can be delivered and enumerates no ordering channel. Its stated premise - that the platform has no outbound SMS channel at all - is refuted by Setting up Lightspeed Tasks, which documents staff who 'Receive SMS or email notifications before tasks are due', so the platform does send SMS. I searched the complete 528-article K-Series corpus retrieved via the Help Center API on 2026-08-06 and found no text-to-order or conversational-ordering documentation, and Order Anywhere is documented as a web/QR channel with email-only guest messaging; but absence across a help centre is not positive evidence of absence, and an SMS ordering channel could arrive through an integration partner not documented there. Unresolved.

digital-google-order differentiator

'Order with Google allows customers to search for your restaurant on Google and click Order Pickup or Order Delivery to place orders via your Order Anywhere website,' and 'your Order Anywhere menu and images will also sync for customers to view in your Google profile, even if they don't click your ordering link.' Prerequisites: a Google Business Profile 'registered under the same name and address' as the Lightspeed account and at least one Pickup and delivery service profile; only one menu can be linked to Google per business location. Gate: rides on Order Anywhere, a paid add-on. The claim's parenthetical 'Preferred by Business' designation is not mentioned in the article. https://k-series-support.lightspeedhq.com/hc/en-us/articles/39777750001051-Google-integrations-for-Order-Anywhere · retrieved 2026-08-04

digital-apple-business-connect

Searched the K-Series help centre and lightspeedhq.com for Apple Business Connect, Apple Maps and 'Order Food' placement on 2026-08-03; no vendor documentation, marketing page or announcement mentions the channel for any Lightspeed Restaurant ordering product. Third-party ordering vendors advertise such integrations; Lightspeed does not. Unresolved for lack of any vendor statement either way.

digital-loyalty-attach

Native loyalty instruments (punch, VIP, gift, ID cards) are QR vouchers redeemed by scanning at the POS; nothing accrues or redeems inside the first-party digital flow. The Order Anywhere account is enumerated as wallet cards plus contact info and email preferences - no loyalty balance - and the gift-card FAQ is explicit: 'Can a customer pay with a gift card for an order placed through Order Anywhere? No, customers cannot currently use K-Series gift cards to pay for an order placed through Order Anywhere.' Apple Wallet passes store cards but no in-checkout accrual/redemption is documented; richer loyalty is delegated to Marsello. https://k-series-support.lightspeedhq.com/hc/en-us/articles/6339630673435-Gift-cards-2-0-FAQ · retrieved 2026-08-05

digital-subscriptions

Checked 2026-08-03: no guest subscription or membership module appears in the K-Series help centre (the O-Series 'Managing your Lightspeed Restaurant subscription' article concerns the merchant's own software plan, not guest programs). The 'Lightspeed Subscriptions' recurring-payments module announced 2022-11-01 is a retail product. A 2025-12 VoucherCart press release claims membership sales via a partner integration, which would not be platform-managed. No vendor documentation settles whether any platform-managed guest membership exists for K-Series.

digital-promo-parity

Promotions are defined per channel in separate engines with different mechanics and availability: POS discounts are configured in Back Office Settings > Discounts (with codes, QR application, wastage flags), while Order Anywhere promotions (BOGO, item discount, profile-wide discount) are created separately in the OA Back Office Offers module and 'are only available in Europe, the Middle East, and Africa'; Uber Eats promotions must be 'set up in Uber Eats'. Nothing defines an offer once for POS, kiosk, and digital with channel eligibility controls. https://k-series-support.lightspeedhq.com/hc/en-us/articles/41912627014939-Creating-promotions-with-Order-Anywhere · retrieved 2026-08-05

digital-guest-data-ownership differentiator

Bulk self-serve export is documented and unrestricted: Customers > Customer list > Export - 'All data will export by default, so deselect any information you wish to exclude from the file', with file-format choice; Guest book lists can likewise 'export key data to your marketing software'. Shortfall: no published statement that the operator owns the guest records was found - data rights live in the Trust Center DPA (About data privacy and security), which the help centre references without an ownership assertion. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804657189-Importing-or-exporting-customer-data · retrieved 2026-08-05

digital-checkout-pci-sca

The AOC covers the Cloud Point of Sale Application and Card Tokenization Service at Level 1, and Lightspeed's position is that cardholder data is handled by assessed providers rather than the restaurant's own page. Shortfall: the attestation is v3.2.1 (ROC January 11, 2024), so by construction it does not evidence the client-side script-integrity requirements 6.4.3 and 11.6.1 that took effect 31 March 2025; and 3DS support is nowhere stated for Order Anywhere - the AOC's scope form lists '3-D Secure Hosting Provider' only as one of its printed checkbox options. https://pdf.lightspeedhq.com/documentation/PCI_AOC_R-C-X-K-L-O-G-Payments.pdf · retrieved 2026-08-02 · not refetchable · site policy · graded A when read adversarially verified

digital-surcharge-transparency differentiator

The vendor's own surcharging article excludes digital channels outright: 'Card-not-present transactions (e.g. Order Anywhere and manual entry)' are listed among the transaction types that will not include surcharges, so the POS surcharge configuration cannot carry to first-party digital ordering at all. No dual-pricing mode exists anywhere in the payments docs, and the Processing service charges article describes POS order profiles and manual buttons only, never Order Anywhere. The claim's channel-parity premise is positively contradicted for the one surcharge mechanism Lightspeed offers. https://k-series-support.lightspeedhq.com/hc/en-us/articles/12625085075995-Surcharging-with-Lightspeed-Payments · retrieved 2026-08-03

guest-loyalty-unified-profile

Guest book (Advanced Insights, NA/AU/NZ, sales-activated) 'automatically creates a customer profile with each credit card transaction and updates the profile when the customer returns', tracks 'number of visits across locations', and documents merge behavior: 'If a guest returns... and pays using a different credit card with the same name, their check data and credit card payments sync with their original profile.' Shortfalls: card-based identity only ('excludes guests who pay with cash'), it is a separate profile store from Back Office customer profiles and Order Anywhere accounts, and no phone/email dedup across POS, online ordering, and kiosk is documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/7340976689051-Guest-book · retrieved 2026-08-05

guest-loyalty-thirdparty-identity-attach differentiator

The only automatic guest-identity mechanism K-Series documents is Guest book, and its stated scope excludes marketplace orders: 'Guest book uses card data to create unique guest profiles. It automatically adds customers who use a credit card at your restaurant and excludes guests who pay with cash or other tenders.' A DoorDash, Uber Eats or Grubhub order is paid on the marketplace and arrives via the Deliverect integration as an externally-paid ticket - no card is processed at the restaurant, so it falls under the documented exclusion. The Deliverect setup article says nothing about guest identity, and the manual Customers profiles attach only when staff select them on an order. Gates on Guest book itself: part of Advanced Insights, North America/Australia/New Zealand only, enabled through a Sales Account Manager. https://k-series-support.lightspeedhq.com/hc/en-us/articles/7340976689051-Guest-book · retrieved 2026-08-04

guest-loyalty-accrual-models

K-Series includes a native 'Loyalty cards module' with VIP (automatic discount when scanned), GIFT, PUNCH ('a buy-x-and-get-y-for-free program', e.g. five coffees then a free one) and ID cards. Shortfall: punch count is the only accrual model; points-per-dollar and spend tiers are not native (the Loyalty section's program integrations are Marsello and Toggle), and card batches must be requested from Lightspeed Support rather than configured self-serve. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4404649891099-About-Loyalty-cards · retrieved 2026-09-03 adversarially verified

guest-loyalty-tiers differentiator

No native tiers: the built-in loyalty instruments are VIP/gift/punch/ID card batches with no status levels. Tiers arrive only via the documented Marsello integration - 'Marsello streamlines customer engagement by integrating loyalty programs... awarding points for purchases, and offering exclusive perks through VIP tiers.' Shortfall: requires a separate Marsello subscription, and automatic promotion/demotion on rolling-window spend is not documented even in Lightspeed's integration article. https://k-series-support.lightspeedhq.com/hc/en-us/articles/24012819812891-Setting-up-the-Marsello-integration · retrieved 2026-08-05

guest-loyalty-offline-behavior differentiator

The offline article states the behaviour: 'Cloud-based services: Services like gift card processing and K-series loyalty programs are unavailable' while the internet is down. Shortfall: a single line that does not separate lookup, accrual and redemption, or say whether accrual is queued for later posting. https://k-series-support.lightspeedhq.com/hc/en-us/articles/53028167251867-Offline-POS-functionality · retrieved 2026-09-03 adversarially verified

guest-loyalty-offer-stacking-rules differentiator

A precedence rule is documented but fixed, not configurable: 'Item discounts and BOGO promotions take priority over profile-wide discounts for items with the same SKU. Profile-wide discounts do not apply to delivery fees.' POS discount settings (Understanding discounts) expose codes, accounting-group scoping and amount limits but no exclusive-vs-combinable flags or application-order configuration. Shortfall: no operator-configurable stacking/precedence engine on either surface. https://k-series-support.lightspeedhq.com/hc/en-us/articles/41912627014939-Creating-promotions-with-Order-Anywhere · retrieved 2026-08-05

guest-loyalty-targeted-offers differentiator

Dynamic audiences exist; offer issuance to them does not. Guest book supports rule-built lists ('Build your own list based on customer or ticket criteria, such as a customer's number of visits'), and 'If you collect customer email addresses, you can also contact customers from a list' or 'export key data to your marketing software.' Shortfall: no native mechanism issues a redeemable offer/discount to a segment - offer targeting requires the Marsello integration, and Guest book itself is Advanced Insights-gated (NA/AU/NZ). https://k-series-support.lightspeedhq.com/hc/en-us/articles/7340976689051-Guest-book · retrieved 2026-08-05

guest-loyalty-rfm-segmentation differentiator

Two automatic segments plus a computed value score ship with Guest book: 'By default, Guest book automatically includes the Best Guests and Recent Guests lists' (top 100 by spend; most recent visitors) and an 'Estimated Lifetime Value... prediction based on a customer's past behavior.' Shortfalls: no at-risk/lapsed/regular lifecycle segments are computed - anything beyond the two defaults is an operator-built rule list - and the whole feature is Advanced Insights-gated (NA/AU/NZ, activated via sales). https://k-series-support.lightspeedhq.com/hc/en-us/articles/7340976689051-Guest-book · retrieved 2026-08-05

guest-loyalty-lifecycle-automation

No native triggered campaigns exist - Campaigns (Advanced Insights) is a passive date-range sales snapshot, and Daily Digest is a fixed summary email. Lifecycle marketing is delegated to the documented Marsello integration ('rewarding your customers with personalized incentives to keep them coming back'). Shortfall: requires a Marsello subscription, and Lightspeed's own article does not detail which automations (birthday, win-back) Marsello provides. https://k-series-support.lightspeedhq.com/hc/en-us/articles/24012819812891-Setting-up-the-Marsello-integration · retrieved 2026-08-05

guest-loyalty-native-email-sms differentiator

Marketing/loyalty is largely partner-delivered (Kangaroo Rewards, Loyale, Freebees, DYNE).

guest-loyalty-consent-management

Checked 2026-08-03: the K-Series Loyalty section still contains only the Marsello and Toggle integration articles, so loyalty/marketing consent capture would live in the partner product, and the 'Managing customer accounts in Order Anywhere' article documents login, contact info and saved cards with no marketing opt-in, consent timestamp or revocation handling. No vendor documentation describes per-channel consent capture in the platform; nothing establishes its absence as a positive statement either.

guest-loyalty-10dlc-registration

There is no SMS sending through the platform to register: guest communications are email-only (order status emails, emailed gift/loyalty cards - 'Can I send a gift card via SMS text? No'), no SMS marketing product exists in the help centre, and '10DLC', 'A2P', and 'campaign registry' appear nowhere in the corpus (searched 2026-08-05). With no SMS channel, the platform neither handles nor documents A2P 10DLC brand/campaign registration. https://k-series-support.lightspeedhq.com/hc/en-us/articles/6339630673435-Gift-cards-2-0-FAQ · retrieved 2026-08-05

guest-loyalty-campaign-attribution differentiator

Campaign measurement is a date-window comparison, not redemption attribution: an Advanced Insights campaign is 'a snapshot of your sales data during special events, promotions, or holidays' reporting total sales/visits, average sale, 'the number of new vs. repeat customers, and the profiles of your top spenders', with comparison 'to the average sales for the same day of the week from the prior year.' Shortfalls: nothing ties a specific redeemed offer to check totals or computes incremental lift beyond the prior-year baseline; Advanced Insights-gated (NA/AU/NZ), data 48h delayed, one campaign per location. https://k-series-support.lightspeedhq.com/hc/en-us/articles/7341353071131-Campaigns · retrieved 2026-08-05

guest-loyalty-data-export-portability differentiator

Self-serve, no fee, no ticket: Customers > Customer list > Export - 'All data will export by default, so deselect any information you wish to exclude from the file. Select the File format... Click Export and the download will start automatically.' Per-customer transaction history exports from Payment > Customer invoices in 'PDF, CSV, and XLSX' (Managing customer invoices), Guest book lists export to marketing software, and the partner API adds Financials/receipts endpoints. Contact PII (name, email, phone) is part of the customer profile export. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804657189-Importing-or-exporting-customer-data · retrieved 2026-08-05

guest-loyalty-review-capture-routing differentiator

Order Anywhere collects post-order reviews and routes by score: with a Google Business Profile connected, guests are invited to leave reviews, low/ordinary feedback stays in the OA reviews inbox ('gather valuable feedback, address concerns'), and 5-star responses are pushed onward - the reputation dashboard reports 'OA 5-star redirects: The total number of reviews from Order Anywhere pushed to Google' and a 'Ratings breakdown... comparing the amount of 5-star reviews made directly on Google and the amount of times Order Anywhere redirected a 5-star review to Google.' Setup is Order Anywhere > Integrations > Google Business Profile (November 2025 release). https://k-series-support.lightspeedhq.com/hc/en-us/articles/39777750001051-Google-integrations-for-Order-Anywhere · retrieved 2026-08-05

guest-loyalty-referral-program

There is no native loyalty product for a referral mechanic to live in: the help centre's entire Loyalty section is two third-party integration guides, 'Setting up the Marsello integration' and 'Setting up the Toggle integration' (re-retrieved 2026-08-04, contents unchanged from the 2026-08-02 adversarial pass). The vendor's own enumeration of its loyalty surface is partner products, so per-guest referral codes, first-order attribution and two-sided rewards - where a merchant gets them at all - come from Marsello, not natively from Lightspeed. https://k-series-support.lightspeedhq.com/hc/en-us/sections/34839005050651-Loyalty · retrieved 2026-08-04

guest-loyalty-wallet-pass differentiator

Apple Wallet passes exist for loyalty instruments: 'customers can easily manage their punch cards, VIP cards, and gift cards in Apple Wallet. Merchants can create electronic loyalty cards or gift cards for customers and email them a QR code to add the card to their Apple Wallet' (Feb 2024). Shortfalls: Google Wallet is not mentioned, and push-updated balances on the pass are not documented (guests cannot even self-check gift-card balances per the Gift cards 2.0 FAQ). https://k-series-support.lightspeedhq.com/hc/en-us/articles/34338126103195-What-s-new-Loyalty-cards-in-Apple-Wallet · retrieved 2026-08-05

guest-loyalty-privacy-rights-tooling

Per-guest locate/export/delete primitives exist: the Customers page lets you 'export customer data, view their transaction history, and make changes to or delete customers' (About customers), the customer-list export is field-selectable, and Order Anywhere guests can self-delete accounts ('Delete my account... Deleted accounts cannot be restored'). A DPA and data-retention policy are published in the Trust Center (About data privacy and security). Shortfall: no DSAR-framed workflow, and deletion propagation to Guest book profiles, card batches, or Marsello marketing records is not documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804657189-Importing-or-exporting-customer-data · retrieved 2026-08-05

guest-loyalty-redemption-fraud-controls

K-Series has no first-party loyalty program to attach fraud controls to - the help centre Loyalty section holds only the Marsello and Toggle integration setup articles (re-checked 2026-08-03) - and neither integration article documents redemption velocity limits, manual-adjustment approvals or employee self-redemption flagging on the POS side. Any such controls would belong to the partner product. Consistent with guest-loyalty-accrual-models, left unknown rather than scored against the partner.

guest-loyalty-ai-offer-recommendation differentiator

'Lightspeed AI' is bundled from the Essential tier and an AI Assistant component appears on the status page, but no documented offer-recommendation feature.

guest-loyalty-stored-value-gift

Backed by the first-party Gift cards 2.0 documentation set. Shortfall: the claim requires balances tied to the same guest profile and redeemable across all locations of the brand, and neither is documented. There is no first-party guest-profile product in the K-Series help centre for a balance to attach to — the Loyalty section carries only the Marsello and Toggle integrations. https://k-series-support.lightspeedhq.com/hc/en-us/articles/6339161622427-About-gift-cards-2-0 · retrieved 2026-08-02 adversarially verified

labor-clock-in-at-pos

'Employees clock in and out of the Restaurant POS app daily to start and end their shift', authenticating with 'your PIN code or place your QR code in front of your device's camera to scan it' - PIN or badge-equivalent, on the same iPad or iPhone that runs service, with no separate time-clock hardware. Permissions distinguish staff who must clock in before using the POS from kitchen users who can only clock in and out. https://k-series-support.lightspeedhq.com/hc/en-us/articles/360050309174-Clocking-in-and-out · retrieved 2026-08-02 adversarially verified

labor-photo-punch-verification differentiator

Clock-in authentication methods are enumerated and photo capture is not among them: 'If prompted, enter your PIN code or place your QR code in front of your device's camera to scan it. Note: Add or change employee PIN or QR codes by editing POS users in the Back Office' - the same two credentials (or none) apply at clock-out and login. No photo-at-punch or facial verification option exists anywhere in POS user or time-clock configuration. https://k-series-support.lightspeedhq.com/hc/en-us/articles/360050309174-Clocking-in-and-out · retrieved 2026-08-05

labor-offline-time-punch differentiator

'Clocking in/out: Staff can clock in and out, with time entries stored locally', and the active POS will 'send its stored data once the internet connection is restored'. Shortfall: nothing describes reconciliation, duplicate suppression, or what happens to punches taken on a passive device that loses the LAN. https://k-series-support.lightspeedhq.com/hc/en-us/articles/53028167251867-Offline-POS-functionality · retrieved 2026-09-03 adversarially verified

labor-granular-rbac

API exposes user groups, permissions and per-business-location access. Per-action granularity (void/comp/price change/report access) is not enumerated publicly. https://api-docs.lsk.lightspeed.app/ · retrieved 2026-08-01

labor-manager-override-audit

After-the-fact audit surfaces exist: the Invoices report opens a per-check Journal view - 'an event log used for auditing purposes and for tracking all actions performed on the selected check' - and Back Office devices expose an Activity events log of 'basic actions performed on a POS device (such as a POS user opening a sales period or clocking in)'. Shortfalls: no manager-override or per-transaction approval flow is documented at all (permissions are granted per user group, not approved case by case), neither log is documented to identify an approver distinct from the acting user, immutability is nowhere stated, and the Cancellations and Corrections report carries no user column. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4403197629595-Invoices-report · retrieved 2026-08-03

labor-native-scheduling differentiator

Scheduling is delivered through the 7shifts partnership, not inside the platform holding the timekeeping data. https://www.lightspeedhq.com/pos/restaurant/payroll/ · retrieved 2026-08-01

labor-demand-labor-forecast differentiator

Sales and labor forecasting exists but is produced by 7shifts consuming Lightspeed sales data, not a native Lightspeed feature. https://www.lightspeedhq.com/pos/restaurant/payroll/ · retrieved 2026-08-01

labor-realtime-labor-percent differentiator

The real-time manager surfaces enumerate their metrics and labor cost percentage is not among them: Pulse's live info boxes are 'Orders, Covers, Voids, Discounts, Comps, Order Average, Cover Average, Table turn time, Refunds, Sales per labour hour' ('Sales per labour hour: The amount of sales generated per clocked in employee hour'). No wage-rate field exists anywhere in Back Office labor docs (hours + tip declaration only; pay rates live in 7shifts/Planday integrations), so labor cost as % of sales cannot be computed or displayed, in real time or otherwise. https://k-series-support.lightspeedhq.com/hc/en-us/articles/29496064755099-About-the-Lightspeed-Pulse-App · retrieved 2026-08-05

labor-overtime-prevention differentiator

The clock-in flow is documented step-by-step (select name, PIN/QR, confirm user shift, optional drawer count) with no warning or block of any kind, and no overtime threshold exists anywhere in Back Office configuration - 'overtime' appears in zero of the 527 help-centre articles. K-Series labor is limited to punches, hours ('All hours worked by employees can be managed from the Back Office'), and reports; scheduling/labor-compliance is delegated to the 7shifts integration ('hiring, training, scheduling, and paying'). https://k-series-support.lightspeedhq.com/hc/en-us/articles/360050309174-Clocking-in-and-out · retrieved 2026-08-05

labor-break-compliance-by-state differentiator

Assessed and unresolved. 'Clocking in and out' (retrieved 2026-08-04) documents the entire native time-clock flow - PIN/QR clock-in, optional cash counts, tip declaration at clock-out - and never mentions meal or rest breaks, attestation prompts, jurisdiction rules or premium-pay flags; the Labor Report's documented columns are tips, sales, discounts, hours worked, service charges and voids. Scheduling and labor compliance are positioned on the 7shifts and Planday integrations, where break scheduling lives. No vendor page states break tracking is unsupported, so absence of documentation leaves this unknown rather than no.

labor-minor-labor-rules

Assessed and unresolved. K-Series documents no native scheduling module at all - scheduling is delivered through the 7shifts and Planday integrations - so the claim's enforcement-at-scheduling half has no native surface to live on, and the clock-in documentation ('Clocking in and out', retrieved 2026-08-04) contains no age-based hour caps, prohibited time windows or school-day limits. No vendor page positively states minor-labor rules are unsupported, so this remains unknown.

labor-tip-pooling-rules

Automated tip-pool calculation is a 7shifts capability synced with Lightspeed, not native POS logic. https://www.lightspeedhq.com/pos/restaurant/payroll/ · retrieved 2026-08-01

labor-tip-distribution-audit-trail

Per-employee tip records are documented: tip declaration prompts at clock-out ('enter the amount of tips to declare... The declared tip amount should be the total you leave with across all payment methods'), declarations 'cannot be changed later', and the Labor Report shows 'employee-specific data, including tips and service charges, alongside everyone's hours worked', with business-wide earned and declared totals in the Business Report. Shortfall: pool contribution and distribution amounts are never recorded - pooling happens outside the system ('Factor in any tips you receive from, or pay out to, other staff'; declared tips 'will differ from their earned amount when they pay out tips to others') - and no per-shift tip-detail export is documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4415116773403-Handling-tips-and-gratuities · retrieved 2026-08-03

labor-qualified-tips-w2-reporting differentiator

No documentation of Treasury tipped-occupation codes or W-2 Box 12 TP / Box 14b handling for TY2026.

labor-native-payroll differentiator

The vendor payroll page routes payroll processing and payroll support to 7shifts, and restricts it to 'businesses based in the US only.' Scheduling, shift swaps, tip-credit automation and sales/labour forecasting on that page are 7shifts capabilities, not Lightspeed ones. https://www.lightspeedhq.com/pos/restaurant/payroll/ · retrieved 2026-08-01 adversarially verified

labor-payroll-export-formats

The vendor's integrations page lists a Payroll category naming 7shifts, Atlas, Planday, Push Operations, Restaurant Accounting Services Inc and Restaurant365 - more partners than the record previously credited. Shortfall: the page is a marketing directory and no first-party documentation states which fields cross the boundary. The claim requires timecards, wages and tips to export in documented formats, and nothing documents whether tips or wage rates transfer at all; none of the major payroll processors the claim names as examples (Gusto, ADP, Paychex, QuickBooks Payroll) appear in the list. https://www.lightspeedhq.com/pos/restaurant-k-series/integrations/ · retrieved 2026-08-02 adversarially verified

labor-shift-swap-workflow differentiator

Employees update availability and swap shifts — via 7shifts, not natively. https://www.lightspeedhq.com/pos/restaurant/payroll/ · retrieved 2026-08-01

labor-server-performance-metrics differentiator

The Staff Performance report breaks the table down 'by the employees that worked that date' with per-employee Gross/Net sales, Tips, Covers, Cover average, Orders, Order average (average check), Refunds, Discounts, Voids, Comps, Service charges and Losses, filterable by user, user group, shift, and interval; Advanced Insights adds Servers reports and the Daily Digest shows per-employee discount usage. Shortfall: no item/category attachment-rate metric, and void/comp figures are dollar totals rather than rates. https://k-series-support.lightspeedhq.com/hc/en-us/articles/40994945471515-Understanding-the-Staff-Performance-report · retrieved 2026-08-05

inventory-recipe-bom-costing

Inventory add-on includes recipes with costing plus a 'Produce' batch-production module implying prep items. Multi-level sub-recipe rollup and automatic recalculation on ingredient cost change are not documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407511552155-Creating-and-managing-recipes · retrieved 2026-08-01

inventory-unit-conversion-yields

The unit chain is documented across two Inventory add-on articles. Purchase-to-count: packaging formats carry 'the number of units contained within this packaging type', and on a purchase order 'the total quantity of items is automatically calculated in terms of the base units... if you order a case, 24 bottles will be added to your inventory' (About Items). Count-to-recipe: 'Decrease in stock level = Quantity used in the recipe / Total capacity of one stock unit' - using 60ml from a 1L bottle decrements stock by 0.06 (Stock levels). Shortfall: no yield or waste percentage exists anywhere in the set - the conversion is straight division with no raw-to-usable trim loss, and the only yield concept is an optional expected-yield field on made-in-batches recipes. Gate: requires the Inventory add-on (purchasable on all tiers). https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407517612699-Stock-levels · retrieved 2026-08-04

inventory-theoretical-vs-actual differentiator

'Discrepancy reports within Inventory allow you to compare your theoretical stock with the actual stock levels, reflecting your most recent stock counts' for a chosen start/end period, per item: Theoretical Stock Level/Value ('after all stock movements recorded'), Last Counted level/value, 'Variance Qty' and 'Variance Value', plus Purchased Qty/Value, 'Consumed Qty: The total quantity of the item that was consumed in recipes during the selected time period, including batched and Made to order', Batch Yield, Wasted, and Transferred columns - variance in both units and currency, derived from POS-sales recipe consumption, counts, and receipts. https://k-series-support.lightspeedhq.com/hc/en-us/articles/20537741099419-Discrepancy-reports · retrieved 2026-08-05

inventory-realtime-depletion differentiator

Depletion on sale is documented, not merely marketed: 'When a customer orders one of these items, it will automatically be assembled using its specified ingredients, and your inventory will update accordingly,' with a stated conversion between stock units and recipe measures. Shortfall: the trigger is a recipe-linked item sale only. Modifier-driven depletion - the explicit second half of the claim - is not mentioned anywhere in the recipe or stock documentation, and no article states the depletion latency, so 'near real time' rather than batch is not established. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407511552155-Creating-and-managing-recipes · retrieved 2026-08-02 adversarially verified

inventory-86-auto-sync differentiator

Threshold-triggered auto-86 exists at item level: 'Sales restrictions can be used to monitor inventory quantities. When items reach zero quantity, these items are automatically marked as unavailable in Order Anywhere (or other supported third-party partners)... When inventory is restocked, the item automatically becomes available once again' (counter set via POS long-press > Availability > Limited). Shortfalls: the trigger is a per-item POS-button counter, not component-ingredient/recipe depletion from the Inventory module, and coverage of third-party menus is limited to 'supported' partners (Uber Eats via Item availability; DoorDash/Grubhub ride Deliverect). https://k-series-support.lightspeedhq.com/hc/en-us/articles/10724827631259-Setting-up-and-using-Item-availability · retrieved 2026-08-05

inventory-count-modes

Stock management supports monitoring quantities/values, reorder thresholds and inventory audits. Distinct full/spot/recurring cycle-count modes with separate variance history are not documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407509542043-Stock-management-Inventory · retrieved 2026-08-01

inventory-mobile-count-offline

Counting is multi-device and concurrent - 'Multiple employees can count together by each resuming the same stock count from different devices... real-time updates across all devices ensure everyone stays coordinated. Changes save automatically every few seconds' with draft resume and per-location item lists. Shortfalls: the documented count flow is search/scroll entry with no barcode or QR scanning (supported barcode scanners are for adding items to orders at the POS), and offline counting with sync-on-reconnect is not documented - the real-time sync model presumes connectivity. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407510354715-Performing-stock-counts · retrieved 2026-08-05

inventory-vendor-catalogs-edi differentiator

Purchase orders and supplier tracking exist; no named broadline EDI catalog (Sysco/US Foods/PFG) integration is documented.

inventory-invoice-ocr differentiator

Native Inventory purchase orders are manual entry (create, place, receive; no scan/ingest option in About Purchase). Invoice ingestion arrives via the documented MarketMan integration - 'a cloud-based inventory and supplier management system... including inventory, purchasing, recipes, vendor payments' - whose invoice product uploads 'via photo, email, or PDF' and extracts line items, matches them to the ingredient list, and flags price changes (marketman.com/page/restaurant-invoice-management-system, retrieved 2026-08-05). Shortfalls: requires a separate MarketMan subscription, and the extracted ledger lives in MarketMan (daily sync), not Lightspeed's Inventory module. https://k-series-support.lightspeedhq.com/hc/en-us/articles/22675539589787-Setting-up-the-MarketMan-integration · retrieved 2026-08-05

inventory-price-change-alerts differentiator

Price history is tracked per item across invoices: Purchase Reports show 'the goods you've purchased, the quantities ordered, price changes over time, and the suppliers', and each item's History page has 'a graph [that] depicts the changes in cost price for the selected item based on previous purchases' with per-order supplier, cost price, and stock level at purchase. Shortfall: no alerting - nothing notifies when a received price exceeds the prior or contracted price by a threshold (threshold alerts exist only in the legacy Stock rules, which cover on-hand quantity, not purchase price). https://k-series-support.lightspeedhq.com/hc/en-us/articles/11207355170203-Purchase-Reports · retrieved 2026-08-05

inventory-par-auto-suggest differentiator

Reorder thresholds plus purchase-order generation. Forecast-driven suggested order quantities are not documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407509542043-Stock-management-Inventory · retrieved 2026-08-01

inventory-waste-logging

'Use the Wastage feature to update stock levels when items are discarded or destroyed and keep track of waste reasons and the value of what was lost' - Stock management > Wastage provides a dashboard of waste events filterable by date and waste reason showing 'the reason and value behind what was lost', and creating a wastage event adjusts inventory. Waste cost is reported separately from count variance: Discrepancy reports carry distinct 'Wasted Qty/Value' columns alongside Variance, and POS-side wastage discounts surface as 'Loss' apart from comps in Business/Shift reports. https://k-series-support.lightspeedhq.com/hc/en-us/articles/7116014889499-Wastage · retrieved 2026-08-05

inventory-shelf-life-expiry

Downgraded on audit 2026-08-06. The prior 'no' rested on the Stock management (Inventory) help-centre page, which is an overview hub of links ('Visit these articles to learn more about using Stock management') and asserts no completeness, plus a keyword search for 'expiry'/'expiration' that returned only card-expiry and MFA hits. Neither is positive evidence of absence. The Inventory add-on's item-level field list was not retrievable without an account, so whether received or prepped items carry a use-by date, and whether any expiring-soon report exists, is undetermined.

inventory-bar-partial-bottle

Partner integrations (WISK, BevSpot, Kegtron) address bar inventory; native partial-bottle weighing is not documented.

inventory-cogs-gl-export

Vendor-listed accounting connectors: QuickBooks, Xero, Restaurant365. Per-category GL mapping and period COGS export shape are not documented. https://www.lightspeedhq.com/pos/restaurant-k-series/integrations/ · retrieved 2026-08-01

inventory-native-not-partner differentiator

'The Inventory module added to Lightspeed Restaurant K Series' - first-party, with Stock, Produce and Purchase sections and native recipe management, not a contracted third product. Costing is present but shallow: recipes carry a Gross profit percentage field and a derived Suggested sell price. It is a paid add-on with advanced inventory at the $399 Premium tier, which raises cost but does not make it a partner product, and the claim's test is native versus bolt-on. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4407517428891-About-Inventory · retrieved 2026-08-02 adversarially verified

inventory-menu-margin-linkage differentiator

Recipe cost joins to sales per item: recipes carry cost and a Gross Profit % field, and Product Mix / Products reports compute per-item 'Margin (tax excl.): The profit margin for the item: total item sales without taxes - costs' with a Costs column; Magic Menu Quadrant (Advanced Insights) adds popularity/retention menu engineering, and April 2026 Benchmarks & Trends adds market pricepoint comparisons. Shortfall: no threshold flagging - nothing alerts when an item's margin falls below a configured level after ingredient-cost changes. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4403156004763-Product-Mix-Report · retrieved 2026-08-05

reporting-realtime-dashboard

The mobile half is documented and genuinely live: Pulse shows 'Live gross revenue, % change compared to the previous period, and time of last update', plus orders, covers, voids, discounts, comps, order and cover averages, table turn time, refunds and sales per labour hour, with an All locations view. Shortfall: the browser half is not. The Back Office Dashboard article says only that it 'summarizes important business activity in easy-to-read graphs and charts' and states no refresh interval or latency, so 'within minutes of the sale' is unevidenced for the browser, which the claim requires alongside the mobile app. https://k-series-support.lightspeedhq.com/hc/en-us/articles/29496064755099-About-the-Lightspeed-Pulse-App · retrieved 2026-08-02 adversarially verified

reporting-eod-closeout

API exposes daily financials, sales data, tax rates and payment methods, implying an EOD close. A single reconciling close-out document is not documented publicly. https://api-docs.lsk.lightspeed.app/ · retrieved 2026-08-01

reporting-pmix-modifier-level

Item-level PMIX is documented: the Product Mix Report gives sales by accounting group, order profile, statistical category and product, with quantity sold, Sales (tax incl.), Sales (tax excl.), margin and cost columns, filterable by order profile, device, staff, shift or tag over a chosen period. Shortfalls: modifier-level rows are not documented - modifiers appear nowhere in the report's described output (combos show component items only on hover) - and no daypart filter is documented on this report; the separate Filtering Reports feature offers an Hourly interval but only for 'date ranges of 1 to 3 days' and 'only to European Lightspeed Restaurant customers'. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4403156004763-Product-Mix-Report · retrieved 2026-08-03

reporting-comps-voids-audit

Reason-coded, permission-gated voids with per-employee reporting: 'Void reasons are used to explain a refund or void applied to an order... Only POS users with the appropriate permissions can refund or void receipts', Discounts and Corrections reports show 'an overview of which void reasons have been applied to refunds or voids' plus discount breakdowns, and Staff Performance attributes Voids/Comps/Discounts dollar values to each employee; Daily Digest 'illustrates which employees are using discounts, how frequently, and for how much.' Shortfall: no report ties an approving manager to each void/comp - attribution is to the transacting user only - and per-event timestamped audit lines exist only on individual receipts, not as an audit report. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804657449-Understanding-void-reasons · retrieved 2026-08-05

reporting-cash-over-short

Counted-vs-expected reconciliation at drawer, shift, and employee level: the Drawer report 'shows the cash drawer amount entered at the start of the sales period, payments taken during the shift, cash amount expected to be in the drawer, and the actual cash drawer amount entered when the sales period is closed'; Consolidated Shift Reports compute 'Overage: Dollar value based on the discrepancy between what should be in the cash drawer and what was counted when performing a cash count'; every user has a personal 'user bank' drawer counted at user-shift start/end (Managing cash drawer operations), and the Cash drawer report shows 'how they were counted, and where discrepancies may have happened.' https://k-series-support.lightspeedhq.com/hc/en-us/articles/360050328874-About-POS-reports · retrieved 2026-08-05

reporting-labor-productivity

Sales per labor hour from actual punches is native: Staff Performance reports 'Sales per hour: The average amount in sales per hour' with 'Hours worked... based on all staff clock-in and clock-out times on the POS', sliceable hourly/daily, by user and user group; Pulse shows live 'Sales per labour hour'. Shortfall: labor cost as a percentage of sales is unavailable - no wage rates exist in the product, so no dollar labor cost by hour, department, or employee can be reported (cost-based labor analytics require the 7shifts integration). https://k-series-support.lightspeedhq.com/hc/en-us/articles/40994945471515-Understanding-the-Staff-Performance-report · retrieved 2026-08-05

reporting-server-scorecards differentiator

Per-server metrics cover average check and more: per-employee Order average (gross/net), Cover average, Covers, Orders, Tips, Refunds, Discounts, Voids, Comps in the Staff Performance table; Advanced Insights Staff reports 'display your sales data by server... view your server's average sales by check or cover and compare a server's performance to an overall average.' Shortfalls: no items-per-check metric, no attachment rate for named categories, and tips are reported as dollars, not as a percentage of sales. https://k-series-support.lightspeedhq.com/hc/en-us/articles/40994945471515-Understanding-the-Staff-Performance-report · retrieved 2026-08-05

reporting-channel-profitability differentiator

Revenue splits by channel exist: Product Mix reports break sales down 'by accounting groups, order profiles, statistical categories, and products' (order profiles map to dine-in/takeaway/delivery/Uber Eats/UEAT/Order Anywhere channels), the Online orders report isolates third-party order payments, and item margin (sales minus costs) is computed. Shortfall: no channel P&L net of marketplace commission - commission and marketplace fees are not captured (the Online orders report reconciles only order-amount differences), so margin by third-party channel net of fees is not reported. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4403156004763-Product-Mix-Report · retrieved 2026-08-05

reporting-scheduled-delivery

Scheduled email reports exist but only for a fixed menu of reports: Reports > Reporting automation offers 'Daily revenue, all locations' or 'Daily Settlements, all locations', 'At the end of the day or At the end of the week', with a comma-separated recipient list; Advanced Insights adds the fixed 5:30 AM Daily Digest per location, and Lightspeed Tasks sends daily/weekly checklist summary emails to chosen recipients. Shortfall: arbitrary Back Office reports cannot be scheduled - there is no schedule option on the general reports. https://k-series-support.lightspeedhq.com/hc/en-us/articles/12285092786203-Automated-reporting-with-Lightspeed-Payments · retrieved 2026-08-05

reporting-public-api differentiator

The reference is public and covers orders, payments, menu and labour data. Shortfall: credentials are not self-service. 'Access to the Lightspeed Restaurant K-Series APIs is reserved for Lightspeed partners and approved merchants' — partners register for the Developer Portal, merchants 'can request access by contacting their Account Managers,' and other developers 'can apply to become partners.' The docs are public; the API is not. https://api-portal.lsk.lightspeed.app/quick-start/intro · retrieved 2026-08-02 adversarially verified

reporting-webhooks differentiator

Order and payment lifecycle webhooks exist alongside staff-shift, reservation and PMS events, managed via API with Bearer auth. Shortfall: the claim requires documented retry behaviour and payload signature verification, and the K-Series reference documents neither — no HMAC signing, no retry/backoff policy, no replayable event log, no published rate limits. Delivery is unguaranteed and payloads are unauthenticated. https://api-docs.lsk.lightspeed.app/ · retrieved 2026-08-02 adversarially verified

reporting-api-not-upcharged differentiator

'Raw API access' appears under the Premium tier only on the vendor pricing page — absent from Starter ($69) and Essential ($189), present at $399. API access therefore carries a $330/month subscription delta from entry, per location, on top of partner approval. https://www.lightspeedhq.com/pos/restaurant/pricing/ · retrieved 2026-08-02 adversarially verified

reporting-tier-paywall differentiator

The vendor pricing page tiers capability heavily: Advanced Insights, Lightspeed AI, Tempo, Tasks, multi-location management, advanced inventory management, 'Multiple revenue center support for hotels' and 'Raw API access' are all plan-gated line items, and launch/onboarding services are Enterprise-only. Shortfall: reporting and integration access are not tier-neutral. https://www.lightspeedhq.com/pos/restaurant/pricing/ · retrieved 2026-08-01 adversarially verified

reporting-history-retention differentiator

Checked 2026-08-03: About Reports, Filtering Reports and the Reports category publish no maximum look-back window and no retention statement - date pickers accept custom ranges without a documented limit. 'About data privacy and security' references a data-retention policy without publishing a number for reporting data. The only published windows are for adjacent tools - Lightspeed Tempo holds 89 days and the Advanced Insights Most Popular Report caps custom ranges at three months - neither of which states the transaction-detail retention of Back Office reporting. No 24-month commitment, nor any window at all, is documented.

reporting-anomaly-alerts differentiator

Operator-configured threshold alerts exist only in the legacy Stock feature: a rule fires 'When the corresponding stock level goes below the specified quantity' for any stock/product and can 'Send an alert by email', 'Include an email report', or 'Invoke a HTTP end-point' (webhook) - but 'As of June 2023, the legacy Stock feature is no longer available to new customers.' No sales-metric alerting exists: Daily Digest is a fixed daily summary, Advanced Insights notifications cover Logbook mentions, and account emails cover 'certain sensitive actions', none operator-configurable on voids, discounts, or sales patterns. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4406100835227-Adding-rules · retrieved 2026-08-05

reporting-nl-query

The Back Office Lightspeed AI agent 'pulls sales data from reports in the Back Office and presents it in an easy to read format, including charts and graphs', supports follow-up questions and custom instructions, and keeps chat history. Crucially it is gated on tenant data access: 'For users to ask questions about sales data, you will also need to enable the permission Sales report access' - a separate permission from general AI access, which is what distinguishes querying the operator's own data from a help-article bot. https://k-series-support.lightspeedhq.com/hc/en-us/articles/42676619412251-Understanding-the-Back-Office-Lightspeed-AI-agent · retrieved 2026-08-02 adversarially verified

reporting-guest-cohorts differentiator

Guest-level analytics ship with Advanced Insights: Guest book auto-builds card-based guest profiles with All Time Spend, Average Spend, Visits, Last Visit and 'Estimated Lifetime Value'; rule-based lists segment by spend/visits; Campaigns reports 'the number of new vs. repeat customers'; the Customer scorecard shows per-guest history, favorite items and a 12-month activity grid; Repeat Customer Favorites and Benchmarks add retention views. Shortfalls: gated behind the Advanced Insights add-on (NA/AU/NZ, activated via account manager), and identity is payment-card based rather than loyalty/online-ordering records - cash guests are excluded. https://k-series-support.lightspeedhq.com/hc/en-us/articles/7340976689051-Guest-book · retrieved 2026-08-05

reporting-sales-forecast differentiator

Benchmarks & Trends exists as a component; forward forecasting in the Lightspeed UI is not documented (7shifts does the labor-side forecast).

reporting-tip-tax-compliance

Declared-versus-charged per employee is documented: a clock-out declaration prompt ('Enter the amount of tips to declare... or tap Skip to proceed with zero'), earned tips in the employee's User report, manager breakdowns in the Labor and Business reports, and the article's note that declared tips 'will differ from their earned amount when they pay out tips to others or receive tips outside the POS app'. Shortfalls: tip pooling happens outside the system - staff are told to adjust their declaration for pool payouts, so no pool-distribution detail exists - and there is no tip tax-liability summary by jurisdiction; the article's only tax guidance is 'Speak with a tax professional to ensure you follow the correct rules... in your region.' https://k-series-support.lightspeedhq.com/hc/en-us/articles/4415116773403-Handling-tips-and-gratuities · retrieved 2026-08-04

multi-location-org-hierarchy

API scopes access by business location; a named three-level enterprise > region > location object is not documented.

multi-location-central-menu-publish

Central authoring and propagation are documented: items are set Local, Shared or Global, a menu is pushed via 'Share with a location', and updates offer 'Update menu' or 'Update menu and reload all devices' to push to connected devices at the other locations. Two shortfalls: the share action takes one location per pass ('Select a location from the drop-down menu', then Share), not a chosen set in a single action; and there is no publish or version history - nothing records what was pushed, when, or by whom. Shared menus are also editable only from the originating location. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4755505361947-Sharing-menus-with-business-locations · retrieved 2026-08-02 adversarially verified

multi-location-price-zones

'Price lists allow you to create preset pricing schemes to apply to menu items based on restaurant location and order profile.' One item record carries per-location pricing, and the order-profile link adds the channel and time axes over that same record - the article's own example links a Happy hour profile to a sixth price list. No item duplication is involved, which is the failure the claim exists to catch. https://k-series-support.lightspeedhq.com/hc/en-us/articles/4402274951323-About-price-lists · retrieved 2026-08-02 adversarially verified

multi-location-consolidated-reporting

A documented Location Reports family aggregates across locations: Consolidated Business Reports ('the financial information for the selected time period for all locations linked to your account'), Consolidated Product Reports, Consolidated Discounts Breakdown, Consolidated Shift Reports and Consolidated Fiscal Summary, exportable to spreadsheet or PDF. Shortfall: these are aggregations, not comparisons - no store-versus-store ranking and no variance flagging is documented, which is the half of the claim that makes above-store reporting actionable. https://k-series-support.lightspeedhq.com/hc/en-us/categories/8348673720987-Reports · retrieved 2026-08-02 adversarially verified

multi-location-cross-location-giftcard

Liability reporting exists with multi-location filtering: the Gift cards statistics dashboard (Customers > Statistics) reports 'Outstanding balance: The total amount, including refills, currently loaded onto gift cards for the chosen location', with a Location filter that can 'Check the box beside each location', plus Loads and Redemptions activity; gift cards are managed business-wide under Customers > Gift cards and the gift-card payment method 'will be available in all locations.' Shortfalls: no article states a card sold at one location is redeemable at another, and no inter-store settlement/redemption reconciliation between owners is documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/43733543286683-Understanding-Gift-cards-statistics · retrieved 2026-08-05

multi-location-cross-location-loyalty

The customer record is shared: 'Customer profiles are consistent across locations, simplifying their management', and Back Office exposes Statistics, Transactions, Products and Loyalty cards per customer. Shortfalls, both explicit: the same article states 'invoices, amounts owed, and accounts receivable are managed separately at each location', and nothing documents whether a loyalty balance or stored order history is chain-wide or per location - the claim's operative test is a single balance across the brand, and that is unaddressed. https://k-series-support.lightspeedhq.com/hc/en-us/articles/23973504428059-Navigating-business-locations · retrieved 2026-08-02 adversarially verified

multi-location-multi-brand differentiator

Multi-concept operation on one account is positively steered away from: 'Business locations are used when operating the same restaurant concept at different physical sites. If you oversee restaurants with different concepts, we recommend setting up a separate Lightspeed Restaurant business for each.' A POS device belongs to one business location with one configuration; there is no mechanism for two brands with separate menus, receipts, and separately reportable revenue on the same terminal and drawer. https://k-series-support.lightspeedhq.com/hc/en-us/articles/23973504428059-Navigating-business-locations · retrieved 2026-08-05

multi-location-multi-tax-jurisdiction

Tax rates and accounting groups are per business location in the API, and Lightspeed ships Quebec WEB-SRM fiscal support — evidence of real jurisdictional handling. Inclusive/exclusive rules and exemption depth are not documented. https://api-docs.lsk.lightspeed.app/ · retrieved 2026-08-01

multi-location-central-labor-policy

No labor-rule engine exists to centralize: K-Series labor is clock-in/out with PIN/QR, hours in Back Office, and tip declaration; there are no break, overtime, or predictive-scheduling settings at any level - 'overtime' and 'break enforcement' appear nowhere in the 527-article corpus - and nothing is enforced at the terminal. Scheduling and compliance are explicitly delegated to integrations (7shifts: 'the employee lifecycle, including hiring, training, scheduling, and paying'). https://k-series-support.lightspeedhq.com/hc/en-us/articles/360050309174-Clocking-in-and-out · retrieved 2026-08-05

hardware-commodity-devices differentiator

The vendor explicitly contemplates third-party purchase: 'If you choose to purchase your hardware elsewhere, we encourage you to purchase the supported models listed in this article.' The supported list is standard Apple retail hardware - iPad 7th gen and later, iPad mini 5th gen and later, iPad Air 3rd gen and later, iPad Pro, iPhone XS through iPhone 15 - buyable anywhere. The single exception is card terminals, which must be Lightspeed-certified because they ship with injected firmware. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260800124209-Supported-hardware · retrieved 2026-08-02 adversarially verified

hardware-os-platforms

Minimum version stated exactly - 'The Lightspeed Restaurant (K Series) POS app requires a supported Apple device running iPadOS or iOS 18 or higher' - with device generations enumerated (iPad 7th gen+, iPad mini 5th gen+, iPad Air 3rd gen+, iPad Pro 11-inch 1st gen+ and 12.9-inch 3rd gen+, iPhone XS/XR through iPhone 15, iPhone SE 2nd and 3rd gen). Apple-only by design: no Android, Windows or Linux client is offered, which the claim treats as a named platform decision rather than a gap. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260800124209-Supported-hardware · retrieved 2026-08-02 adversarially verified

hardware-handheld-purpose-built

Supported hardware is a closed list ('Lightspeed only provides support for the hardware listed in this article'): POS devices are Apple iPads and iPhones only, and the Payment terminals table holds Mobile Tap, Verifone P400+, AMS1 Smart Terminal, Verifone V400m, S1F2 Smart Terminal with Printer, Verifone e285 and e280. The handheld ordering setup is 'Setting up Mobile Tap' (13189156370459): a Bluetooth card reader on an 'Adhesive metal plate' stuck to the back of an iPhone, or the 'Tableside Case for iPhone', 'a phone case designed to securely hold the Mobile Tap and your iPhone 12, 13, or 14'. No drop or IP rating is published for it. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260800124209-Supported-hardware · retrieved 2026-09-03 adversarially verified

hardware-handheld-battery-swap differentiator

The mobile payment terminals have user-removable batteries - the Verifone V400m and e285 SIM-replacement procedures document sliding off the battery cover and removing/reinstalling the battery in the field. Shortfall: the ordering handheld is a standard iPhone (iPhone XS/XR or later per Supported hardware) with a sealed battery, and Lightspeed publishes no rated full-shift battery life for any handheld; the Mobile Tap reader charges via USB/dock rather than swapping. https://k-series-support.lightspeedhq.com/hc/en-us/articles/18140638499355-Troubleshooting-Lightspeed-Payments-for-Restaurant-POS · retrieved 2026-08-05

hardware-handheld-lte

The documented outage strategy is 4G on payment terminals, not handheld POS devices: 'Consider using payment terminals with 4G capability for standalone payments in case of outages by your ISP.' POS handhelds (iPhones/iPads) are documented exclusively on the dedicated store LAN - network requirements mandate Wi-Fi RSSI above -67 dBm on a dedicated router, and the only cellular reference for POS devices is using a mobile hotspot as a troubleshooting test. No cellular/LTE fallback for ordering handhelds is offered or documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/27536544139547-Network-optimization-checklist · retrieved 2026-08-05

hardware-offline-mode

The article documents both what keeps working (orders, table holds, multi-register sync, local kitchen and guest-check printing, cash/check/manual tenders, full menu access, clock in/out) and, in an 'Offline limitations' table, exactly what degrades: integrated Lightspeed Payments 'are not handled in real-time' and must use the terminal 'in standalone mode, with LTE/4G'; live reports and inventory do not update; new Back Office configuration is not visible; item pictures/descriptions/allergens are unavailable; 'gift card processing and K-series loyalty programs are unavailable'; accounting, delivery and online-order integrations are unavailable. https://k-series-support.lightspeedhq.com/hc/en-us/articles/53028167251867-Offline-POS-functionality · retrieved 2026-09-03 adversarially verified

hardware-kds

First-party product with its own setup documentation, its own status-page component and a published price of $30/screen/month on all plans. KDS 2.0 documents named stations, per-station item routing, touch interaction and per-station Delayed/Late wait-time thresholds - the station-routing and fire-timing elements of the claim. It is not an integration-only dependency. https://k-series-support.lightspeedhq.com/hc/en-us/articles/22168531609499-Setting-up-Kitchen-Display-System-2-0 · retrieved 2026-08-02 adversarially verified

hardware-kiosk differentiator

Assessed and unresolved. The claim requires countertop and freestanding form factors plus documented ADA compliance. The only hardware statement Lightspeed publishes about its kiosk is 'Tablet-based hardware keeps costs affordable and setup simple'; the K-Series supported-hardware matrix, which lists terminals, printers, scanners, cash drawers and network gear by model, contains no kiosk enclosure at all. No accessibility documentation exists for any Lightspeed kiosk. adversarially verified

hardware-drive-thru

The supported-hardware catalog is enumerated - Apple devices, barcode scanners, receipt and label printers, network accessories, physical cash drawers, payment terminals, Kitchen Display System, Order Display Screen (plus fiscal modules) - and includes no outdoor menu boards, order confirmation displays, or speaker/headset systems; no timer or speed-of-service measurement exists (KDS Statistics is per-item prep time). 'Drive-thru' appears nowhere in the 527-article help centre. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260800124209-Supported-hardware · retrieved 2026-08-05

hardware-printer-compatibility

Six receipt/kitchen printer manufacturers with connection types: SNBC (LAN), Blue Bamboo (Bluetooth), Epson (LAN/USB/Wi-Fi/Bluetooth), Seiko (LAN/Bluetooth), Bixolon (LAN/Wi-Fi) and Star Micronics (USB/LAN/Wi-Fi/Bluetooth). Both manufacturers the claim names as its test - Epson and Star - are present, and LAN/Ethernet kitchen printers are covered on four of the six. Not a vendor-branded-only list. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260800124209-Supported-hardware · retrieved 2026-08-02 adversarially verified

hardware-peripherals

A named-model compatibility list is published: barcode scanners (Socket Mobile SocketScan S740 2D, CHS 7Ci, CHS 7Qi), cash drawers (Safescan LD 3336, APG Minota, Lightspeed Branded VPOS), receipt and label printers, certified payment terminals, and an Order Display Screen running on Apple TV 4th gen or newer over HDMI. Shortfall: no scales for by-weight items appear anywhere in the list, and multi-drawer-per-terminal is not addressed. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260800124209-Supported-hardware · retrieved 2026-08-02 adversarially verified

hardware-p2pe-terminal

The published AOC documents the device posture: customers 'deploy P2PE POI terminals and PTS compliant magnetic stripe readers deployed at the customer premises', and 'Lightspeed K and L series support P2PE compliant devices and PTS compliant magnetic stripe readers'. The supported-hardware page reinforces the closed fleet - existing terminals cannot be used because they lack the certified firmware injection. Shortfall: the merchant's applicable SAQ type is stated nowhere in the AOC or the support documentation, and P2PE-compliant is not the same as a PCI SSC listed validated P2PE solution. https://pdf.lightspeedhq.com/documentation/PCI_AOC_R-C-X-K-L-O-G-Payments.pdf · retrieved 2026-08-02 · not refetchable · site policy · graded A when read adversarially verified

hardware-tap-to-phone differentiator

'With Tap to Pay on iPhone, Lightspeed Payments gives you the ability to accept payments directly on your iPhone with no additional hardware required... accept Apple Pay, contactless credit and debit cards, and other digital wallets through a quick tap on an iPhone.' Requirements: iPhone XR or above, iOS 18.4+, screen lock enabled, Lightspeed Payments, app 24.2+; activated under Payment > Payment methods > Lightspeed Payments > Tap to Pay for iPhone. https://k-series-support.lightspeedhq.com/hc/en-us/articles/10071706424347-Tap-to-Pay-on-iPhone-with-Lightspeed-Payments · retrieved 2026-08-05

hardware-pricing-transparency differentiator

Only KDS ($30/screen/month) is published on the vendor site. Terminal, reader, stand and printer prices are quote-only from Lightspeed; the $359–$519 reader figures are third-party. https://www.lightspeedhq.com/pos/restaurant/pricing/ · retrieved 2026-08-01

hardware-ownership-vs-lease differentiator

Hardware is purchased outright, from Lightspeed or elsewhere: 'You can purchase supported hardware directly from Lightspeed. Our online stores are customized for each region' (store.lightspeedhq.com and regional variants), and 'If you choose to buy your hardware elsewhere, we encourage you to purchase the supported models listed in this article' - merchants may even supply their own iPads/iPhones. No mandatory lease or subscription-bundled rental exists in the documentation. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260800124209-Supported-hardware · retrieved 2026-08-05

hardware-usable-after-churn differentiator

Notable risk signal: Lightspeed states merchants cannot use existing terminals with Lightspeed due to certification, which implies the reverse is constrained too — but the vendor does not document it.

hardware-rma-sla differentiator

Searched for published warranty terms and replacement SLAs on 2026-08-05: 'warranty', 'RMA', 'advance exchange', and 'replacement' (in a hardware sense) return nothing in the 527-article help centre; the Supported hardware article and About hardware say only that Lightspeed 'provides support for the hardware listed'; the store.lightspeedhq.com storefront shows products and prices with no warranty or replacement-turnaround statements on its landing page (terms pages not indexed). No published warranty term or advance-exchange SLA could be located on any vendor surface.

hardware-byod

Bring-your-own-Apple-device is the documented model: the POS app runs on any supported iPhone/iPad on iOS/iPadOS 18+, hardware may be bought 'elsewhere', and per-user security exists (PIN/QR login per POS user, Back Office permission groups; Tap to Pay requires a passcode/Touch ID/Face ID on the phone). Shortfall: nothing addresses staff-owned personal phones specifically - no MDM guidance, data-separation, or personal-device policy is documented, so the claim's 'documented permission and security model' for personal BYOD is only partly met. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260800124209-Supported-hardware · retrieved 2026-08-05

hardware-remote-device-management differentiator

A device console exists for POS devices: Back Office POS > Devices shows each device's state ('Connected... In background... Disconnected'), sync status (Ok / Remote reload requested / Reload required), Application version, OS version, IP/SSID, with remote configuration reload from the Back Office plus disable, audit, and export; the KDS hub separately lists connected displays with Connected/Disconnected status and event-sync counters. Shortfalls: printers and payment terminals are not in this console, there is no remote reboot, and app updates come via the App Store with no staged rollout. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804658149-Managing-POS-devices · retrieved 2026-08-05

hardware-selfpour-scales

Kegtron (keg volume monitoring) is a listed partner, but pour-posts-to-tab behavior is not documented.

hardware-callerid-integration

Downgraded on audit 2026-08-06. The Supported hardware article is genuinely closed ('Lightspeed only provides support for the hardware listed in this article') and contains no telephony or caller-ID peripheral, so no first-party caller-ID hardware exists. But the claim is satisfiable by a telephony integration instead, and the only evidence against that was the public integrations directory plus a zero-hit help-centre search for 'caller' - a directory listing is not an exhaustive statement of what partners exist, and Lightspeed's Integration Hub advertises 200+ partners without publishing a complete roster. Whether any partner delivers an inbound-call customer pop at the POS is undetermined.

extensibility-public-api-docs

The full K-Series API reference renders without login, NDA or sales contact, exposing named endpoint groups: Order and Pay, Financial and FinancialV2, Items, Rich Item, Staff (shifts, users, permissions, webhooks), Reservations for Platforms, PMS, Tax Breakdown and ID Cards. A developer can size an integration before purchase, which is what the claim tests. https://api-docs.lsk.lightspeed.app/ · retrieved 2026-08-02 adversarially verified

extensibility-api-access-cost differentiator

'Raw API access' is a Premium-only line item on the vendor restaurant pricing page, so the merchant-side cost of integrating is a $330/month delta from Starter or $210/month from Essential, per location. Lightspeed publishes no separate partner fee, revenue share or per-location API charge on top of that. https://www.lightspeedhq.com/pos/restaurant/pricing/ · retrieved 2026-08-02 adversarially verified

extensibility-free-sandbox differentiator

A demo environment exists (auth.lsk-demo.app) but the portal states demo accounts are created by approved partners registered in the Developer Portal — not open to any developer. https://api-portal.lsk.lightspeed.app/quick-start/intro · retrieved 2026-08-01

extensibility-oauth-partner-apps

OAuth 2.0 authorization-code grant is genuine, with space-delimited URL-encoded scopes and a merchant consent step. Shortfalls: only three scopes are published (financial-api, orders-api, offline_access), which is coarse rather than granular; scope allocation is gated on Lightspeed, not the operator - 'You will only be able to request the access scopes that your API client has been granted permission to request', and 'Merchants can contact their account manager to request additional scopes'; and no merchant-facing mechanism to revoke an individual app's grant is documented. https://api-portal.lsk.lightspeed.app/quick-start/authentication/authorization-overview · retrieved 2026-08-02 adversarially verified

extensibility-webhooks-push

Push exists and polling is not required: the reference publishes Order Notification, Payment Notification and Item Availability Notification callbacks, plus shift, reservation and PMS notification categories. Shortfall: the claim enumerates created, modified, paid, voided and refunded as the order lifecycle, and the reference exposes a single order notification and a single payment notification - no void event and no refund event is published, so an integrator cannot subscribe to the two states that matter most for reconciliation. https://api-docs.lsk.lightspeed.app/ · retrieved 2026-08-02 adversarially verified

extensibility-webhook-reliability differentiator

The public K-Series OpenAPI spec (914 KB, 74 paths, host robots fully permissive) documents webhook delivery credentials rather than signatures: apeWebhookEndpoint has withBasicAuth/username/password, and the Reservations platform webhooks accept BASIC_AUTH, BEARER_TOKEN, API_KEYS or OAUTH2 client credentials that Lightspeed sends with each call (reservation-servicePlatformWebhookResponseDto.currentAuthType). 'signature' occurs only as cardholder signature data and 'HMAC' nowhere; 'retry' occurs only for PMS charge retries. Shortfall: no HMAC signing, no retry/backoff policy, no replayable event log. https://api-docs.lsk.lightspeed.app/source.json · retrieved 2026-09-03 adversarially verified

extensibility-order-injection-api

The Order and Pay group publishes 'Create Local Order' and 'Create To Go Order' write endpoints alongside check and payment operations, so an external system can originate both dine-in and takeaway tickets. Corroborated operationally by the Deliverect path, where externally-originated marketplace orders arrive as POS tickets in real time. The reference does not itself state that injected orders fire to KDS or printers. https://api-docs.lsk.lightspeed.app/ · retrieved 2026-08-02 adversarially verified

extensibility-menu-write-api differentiator

Items are writable — Create Item (POST) and Update Item by ID (PUT), including pictures and allergen data. Shortfall: modifiers are read-only. The only modifier operation in the reference is Get Modifiers (GET); there are no create or update endpoints for modifiers or modifier groups, and no standalone price-write endpoint. A pizza or franchise operator cannot push a modifier tree through this API. https://api-docs.lsk.lightspeed.app/ · retrieved 2026-08-02 adversarially verified

extensibility-doordash-preferred differentiator

Lightspeed is absent from DoorDash's 2026 Preferred Integration Partner cohort — Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast and UrbanPiper, benchmarked as of 8 May 2026 — per DoorDash's own newsroom post. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-01 adversarially verified

extensibility-first-party-delivery-integrations differentiator

Uber Eats and Uber Direct are direct integrations. DoorDash and Grubhub run through Deliverect, resold as 'Lightspeed Delivery by Deliverect' — a paid middleware layer by another name. https://www.lightspeedhq.com/pos/restaurant-k-series/integrations/ · retrieved 2026-08-01

extensibility-middleware-compatibility

Deliverect confirmed as a supported endpoint. A second major aggregator (Chowly, Otter, Checkmate) is not confirmed in Lightspeed's own integration listing. https://k-series-support.lightspeedhq.com/hc/en-us/articles/25208938481691-Setting-up-the-Deliverect-integration · retrieved 2026-08-01

extensibility-accounting-connectors

The Accounting category names QuickBooks, Xero, Restaurant365, DAVO Sales Tax, Tiphaus and Restaurant Accounting Services Inc, so QuickBooks plus a second GL is satisfied on the counting test. Shortfall: the claim's discriminator is 'mapped journal entries rather than CSV-only export', and the integrations page is a partner directory that describes no field mapping, no chart-of-accounts configuration and no journal structure for any of the six. Whether these post mapped journals or export files is unestablished. https://www.lightspeedhq.com/pos/restaurant-k-series/integrations/ · retrieved 2026-08-02 adversarially verified

extensibility-payroll-export

Two or more named partners exist under Payroll on the vendor's integrations page (7shifts, Atlas, Planday, Push Operations, Restaurant Accounting Services Inc, Restaurant365), so the counting half of the claim is met. Shortfall: 'without manual re-keying' is unevidenced - no first-party documentation describes labour hours flowing to any of these partners, and the directory entry is a marketing listing rather than an integration guide. https://www.lightspeedhq.com/pos/restaurant-k-series/integrations/ · retrieved 2026-08-02 adversarially verified

extensibility-app-marketplace

'The Integration Hub is a directory of third-party integrations that work with Lightspeed Restaurant', browsable in Back Office with topic filters (Inventory, Marketing among them) and a documented self-service path - search a solution and follow its onboarding steps - describing hundreds of integrations. The public lightspeedhq.com integrations page carries the same directory with partners named by category for prospects who are not yet customers. https://k-series-support.lightspeedhq.com/hc/en-us/articles/40834565217691-About-the-Integration-Hub · retrieved 2026-08-02 adversarially verified

extensibility-headless-embedded

The K-Series API's Order and Pay group exposes the transaction engine to third-party UIs: 'Create Local Order' and 'Create To Go Order' POST endpoints inject orders, with operations to apply payments and manage open checks, plus Order and Pay webhooks for lifecycle events. This is how certified ordering fronts drive the POS in production (UEAT web/kiosk ordering posts orders via the external payment API; Deliverect injects marketplace orders). Access requires partner/approved-merchant API credentials via the developer portal. https://api-docs.lsk.lightspeed.app/ · retrieved 2026-08-05

extensibility-data-portability-exit differentiator

Domain-by-domain machine-readable exports are self-serve: full customer list ('All data will export by default') with format choice; items, menus, and price lists import/export in bulk; per-customer transactions and invoices in PDF/CSV/XLSX; report tables export CSV/XLSX; German accounts get the mandated DSFinV-K full POS-data export; and the partner API serves Financials and receipts. Shortfall: no documented complete historical exit export - order/receipt history has no single bulk export, and no contract-end data-handover process is published (the Trust Center data-retention policy covers deletion, not handover). https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804657189-Importing-or-exporting-customer-data · retrieved 2026-08-05

reliability-offline-order-entry

'Offline POS functionality': with the internet down but the LAN up, 'New orders can be taken, added to tables, and held as normal'; 'Production dockets (to kitchen or bar) and local guest checks can be printed, provided the POS device and local printers remain connected on the local area network'; 'The full menu, modifiers, discounts, and prices are available as they are stored locally on the device'; the active POS 'will log all activity and send its stored data once the internet connection is restored'. If the LAN also fails, only the active POS keeps taking orders and local printing stops. https://k-series-support.lightspeedhq.com/hc/en-us/articles/53028167251867-Offline-POS-functionality · retrieved 2026-09-03 adversarially verified

reliability-offline-card-auth differentiator

Offline limitations table: 'Integrated payments (Lightspeed Payments) are not handled in real-time. The actual payment transaction must be handled using the terminal in standalone mode, with LTE/4G connection', and 'Payment terminals with a 4G (cellular phone network) backup will remain functional without internet or local connections'. Shortfall: this is a cellular-backed terminal fallback, not store-and-forward; a terminal without a cell connection 'will not function'. https://k-series-support.lightspeedhq.com/hc/en-us/articles/53028167251867-Offline-POS-functionality · retrieved 2026-09-03 adversarially verified

reliability-offline-decline-liability differentiator

There is no store-and-forward card acceptance to carry liability: during an outage 'most basic order-taking functions will still work offline. But you'll still want to get back online quickly to use your hardware and process card payments' - card payments require connectivity (integrated terminals need the network; the documented outage fallback is 4G standalone payment terminals, which process online over cellular). With no offline card capture mode, no decline-liability policy exists or is needed, and none is published. https://k-series-support.lightspeedhq.com/hc/en-us/articles/53288894613787-Troubleshooting-network-issues · retrieved 2026-08-05

reliability-lan-degraded-multi-terminal differentiator

'Multi-register sync: Orders opened on one POS will sync to other POS. Data will be stored locally, in the Active Device(s).' The connectivity model: 'If the connection with the internet is lost, devices can still communicate with each other on the local network'; 'Passive POS devices can still send data to active POS devices, but the active devices cannot forward the data to the cloud.' Only when the LAN itself fails does operation collapse to the single active POS. https://k-series-support.lightspeedhq.com/hc/en-us/articles/53028167251867-Offline-POS-functionality · retrieved 2026-09-03 adversarially verified

reliability-local-transaction-engine differentiator

Local continuity is documented but thin: 'If your network or internet service goes out, most basic order-taking functions will still work offline' (the App Store listing likewise advertises an offline mode), Quebec's WEB-SRM 'works in offline mode right out of the box. All transactions are stored locally on the POS', and the KDS 2.0 hub is a genuinely local server (a dedicated POS 'creates secure websites' serving station screens over LAN IP). Shortfall: no documented on-premise transaction engine or edge-server architecture for the ordering path - offline behavior is a one-line assurance with no described scope, sync, or multi-terminal consistency model. https://k-series-support.lightspeedhq.com/hc/en-us/articles/53288894613787-Troubleshooting-network-issues · retrieved 2026-08-05

reliability-offline-kds-printing

Internet down, LAN up: 'Printers remain functional as they connect via the local network' and 'KDS remains function[al]'; production dockets and guest checks print 'provided the POS device and local printers remain connected on the local area network (LAN/Wifi)'. Both stop if the LAN fails. https://k-series-support.lightspeedhq.com/hc/en-us/articles/53028167251867-Offline-POS-functionality · retrieved 2026-09-03 adversarially verified

reliability-printer-fallback

Automatic failover is documented as an ordered printer list: 'When a device prints a receipt on a printing profile, it first tries to print on the first printer in the list. If this printer is turned off or cannot print, the device will attempt to print on the second printer in the list, and so on.' Shortfall: the claim's alert element is only half met - the sole documented signal is the optional 'Add a header when printing on a fallback printer' setting, which stamps _BACKUP PRINTER_ on rerouted tickets; no POS or KDS notification that a printer has failed is documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804607010-Managing-printing-profiles · retrieved 2026-08-03

reliability-sync-conflict-handling

Assessed and unresolved. The claim asks whether the vendor documents conflict-resolution behavior for edits on two devices during a network partition; nothing of the kind was found in the surfaces checked on 2026-08-04 - 'Networking for Lightspeed Restaurant' (connectivity requirements and peer-to-peer LAN ports, no sync semantics), the KDS 2.0 articles (a disconnected screen's 'sync count will stall until the connection is restored', nothing on divergent edits), the Printing FAQ, and the public K-Series API reference. Neither last-write-wins, merge nor operator-prompt behavior is described anywhere, and no page states offline concurrent editing is possible in the first place.

reliability-offline-feature-matrix

No offline-capability matrix exists in the K-Series help centre. The closest vendor artefact is 'Networking for Lightspeed Restaurant', which specifies mandatory outbound connectivity to *.lightspeed.app, *.ikentoo.com and *.adyen.com and 20 Mbps per POS device and payment terminal, and describes no degraded mode. An operator cannot find out from Lightspeed which functions survive an outage. https://k-series-support.lightspeedhq.com/hc/en-us/articles/16154347413275-Network-requirements-for-Lightspeed-Restaurant · retrieved 2026-08-02 adversarially verified

reliability-public-status-page

Sixteen per-component states for K-Series with no login - POS, Back Office, Back Office - Reporting, API (incl. Online Orders), Order Anywhere, Payments, Lightspeed Payments, Advanced Insights, Inventory, Pulse, Reservations, Tasks, Tempo, Benchmarks & Trends, KDS and AI Assistant - each carrying a 90-day uptime history, so an operator can separate a vendor incident from a local fault during service. https://status.lightspeedhq.com/ · retrieved 2026-08-02 adversarially verified

reliability-247-live-support

The K-Series support documentation publishes the channel and hours matrix. English phone support: 'Every day, 24 hours per day', with numbers listed by region (+1 833-573-7437 North America, +44 20 3695 9599 UK). Chat: 'We're available 24 hours a day, 7 days a week in all languages.' Non-English phone lines are limited (French 08:00-24:00 CET, German 08:00-23:00 CET, Dutch Mon-Fri 09:00-17:00 CET). No tier gate is stated - support is not presented as a premium add-on. https://k-series-support.lightspeedhq.com/hc/en-us/articles/360056758213-Contact-us · retrieved 2026-08-02 adversarially verified

reliability-onsite-install differentiator

Lightspeed dispatches its own installers: the site-preparation guide constrains what they will do on site - 'Lightspeed-contracted technicians cannot drill into or mount hardware on tile, concrete, stainless steel, marble, or granite. If needed, have a licensed contractor handle this work beforehand' - and instructs the merchant to 'Schedule your Lightspeed Restaurant hardware installation during a time when there is no active construction and your business is not open', to complete space modifications 'before your install date', and to 'Gather all necessary hardware and cables in a central location within your business prior to your installation'. Shortfall: the in-person service covers hardware installation only. Go-live itself is remote - the multilocation offering advertises 'hardware validation sessions prior to Go-Live accompanied with remote Go-Live support' and 'one-on-one, tailored onboarding' delivered remotely - and the hardware guide still allows the self-install path ('You may have hired an on-site professional to set up your hardware, or you might be doing it yourself'), so on-site attendance is not universal and no certified reseller/dealer network is published. https://k-series-support.lightspeedhq.com/hc/en-us/articles/10275376724507-Preparing-your-site-for-installation · retrieved 2026-08-06

reliability-menu-build-service differentiator

Enterprise tier advertises 'unlimited launch and consultation services'; lower tiers appear self-onboarding, a dominant Capterra complaint. https://www.lightspeedhq.com/pos/restaurant/pricing/ · retrieved 2026-08-01

reliability-hardware-replacement-sla

Searched 2026-08-05 for a replacement/advance-exchange program: no help-centre article mentions hardware replacement turnaround, advance exchange, or warranty service ('replacement' hits concern card replacement and menu items); Supported hardware says only that Lightspeed 'provides full technical support and software updates' for listed devices; the store.lightspeedhq.com landing page carries no replacement-program terms, and the regional store terms pages were not retrievable. Whether a paid or included advance-exchange program exists is not determinable from public vendor documentation.

reliability-pci-dss-4-attestation

Lightspeed publishes an AOC covering R/C/X/K/L/O/G and Payments, asserting Level 1 service-provider compliance, assessed onsite by ControlCase. Shortfall, and it is decisive for this claim: the published attestation is 'PCI DSS v3.2.1 Attestation of Compliance for Onsite Assessments - Service Providers', 'based on results noted in the ROC dated (January 11, 2024)' and signed February 2024. It therefore cannot cover the v4.x future-dated requirements that became enforceable on 31 March 2025. No v4.0/4.0.1 attestation covering the restaurant product was retrievable. https://pdf.lightspeedhq.com/documentation/PCI_AOC_R-C-X-K-L-O-G-Payments.pdf · retrieved 2026-08-02 · not refetchable · site policy · graded A when read adversarially verified

reliability-mfa-role-based-access

Both halves are now documented, and one fails. Role-based access is strong: POS user groups ship as Floor staff, Manager, Trainee and Shift tracker with granular per-group permissions (order refunds, partial refunds, item price, table access, order split, tipping, time clock access, shift management). MFA exists for merchant Back Office logins via TOTP authenticator apps. Shortfall: it cannot be required. The article states 'Each user will need to enable MFA for their account. MFA cannot be enabled by location or by business' - so MFA is per-user opt-in and an administrator cannot enforce it, which is precisely what the claim's word 'enforceable' asks for. https://k-series-support.lightspeedhq.com/hc/en-us/articles/43642296058139-Setting-up-multi-factor-authentication · retrieved 2026-08-02 adversarially verified

reliability-self-serve-training

Extensive public help center including a 'Launching Lightspeed Restaurant checklist'. A terminal training/practice mode is not documented, and reviewers describe onboarding as self-teaching. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260805671909-Launching-Lightspeed-Restaurant-checklist · retrieved 2026-08-01

reliability-failover-terminal-role differentiator

The one server-role device in the architecture cannot fail over: KDS 2.0 requires 'a dedicated POS to be the hub' and 'The POS assigned to be the hub for the KDS must always remain on for the system to function. Please keep it charged or plugged in at all times'; if the hub disconnects, screens stall ('If a screen drops offline, its sync count will stall until the connection is restored') and recovery is manual reconnection. No article documents another terminal automatically assuming the hub role; the ordering path itself is cloud-per-device with no promotable master. https://k-series-support.lightspeedhq.com/hc/en-us/articles/22168531609499-Setting-up-Kitchen-Display-System-2-0 · retrieved 2026-08-05

reliability-cellular-backup

Documented for payment continuity only: 'Consider using payment terminals with 4G capability for standalone payments in case of outages by your ISP' - the Verifone terminals carry SIM cards (Settings > Network > Cellular per the troubleshooting guide), so card acceptance can continue standalone over cellular. Shortfalls: this is not automatic failover of the POS - ordering devices have no documented cellular fallback (a mobile hotspot appears only as a troubleshooting test), and standalone-mode payments are decoupled from the POS check. https://k-series-support.lightspeedhq.com/hc/en-us/articles/27536544139547-Network-optimization-checklist · retrieved 2026-08-05

commercial-month-to-month-contract differentiator

Pricing is quoted per month on the public page, but the Service Agreement is built around an Initial Term with automatic renewal and a 90-day notice window; third parties report 1–3 year terms as standard. https://www.lightspeedhq.com/legal/lightspeed-service-agreement/ · retrieved 2026-08-01

commercial-no-early-termination-fee differentiator

The published Service Agreement provides that early customer termination incurs non-recurring fees owed, the remaining recurring fees for the term, and the difference between list and discounted pricing, and that 'all payments by Customer to Lightspeed under this Agreement are non-refundable.' An ETF exists; Lightspeed publishes no dollar figure. https://www.lightspeedhq.com/legal/lightspeed-service-agreement/ · retrieved 2026-08-01 adversarially verified

commercial-autorenew-terms-published

Section 4.2 of the public Service Agreement: 'Upon expiration of the Initial Term and unless otherwise stated in the Order Form or herein, this Agreement will automatically renew for a duration equal to the Initial Term', terminable on 'written notice to the other party at least (i) where the Current Term is more than ninety (90) days, ninety (90) days prior to the end of the Current Term; or (ii) where the Current Term is less than ninety (90) days, such period of notice equal to the Current Term'. Both the renewal mechanic and the notice window are diligenceable before signing; the Initial Term length itself is quote-specific. https://www.lightspeedhq.com/legal/lightspeed-service-agreement/ · retrieved 2026-08-02 adversarially verified

commercial-processing-not-bundled differentiator

Same weak footing, and the specific penalty figure is now contested. Cross-checking turned up claims that the $99/month gateway fee belongs to the legacy U-Series (Upserve) platform, and separate third-party reporting of a much larger volume-tiered non-Lightspeed-Payments fee (~$400/month) driven by region-specific PDF tables that Lightspeed does not publish. Conflicting third-party numbers with no vendor source: unknown. adversarially verified

commercial-interchange-plus-published differentiator

Nothing interchange-plus is published for Lightspeed Restaurant. The Restaurant payments page defers rates to the pricing page - 'View our competitive processing rates on our pricing page' - and the Restaurant pricing page then publishes no processing rate at all: no percentage, no bps markup, no per-transaction cents figure, and the word interchange appears nowhere. Payment processing is listed only as a plan feature ('Integrated payments'). The sole published rate path is a bespoke one: 'Processing over $50K? Your current processor may be overcharging you... Contact our experts today for a customized quote.' A claim about what the vendor publishes is directly checkable, and the published answer is nothing, so a stated interchange-plus option with a specific markup does not exist. Note: the previous citation (lightspeedhq.com/payments/) now redirects to the Lightspeed RETAIL payments page and its blended-rate quotation is not carried here. https://www.lightspeedhq.com/pos/restaurant/pricing/ · retrieved 2026-08-09 adversarially verified

commercial-rate-increase-clause differentiator

No rate-increase cap or penalty-free-exit clause located. Reviewers report mid-relationship price increases.

commercial-pricing-published

Per-location software tiers published ($69/$189/$399 + Enterprise quote) and KDS at $30/screen/month. Additional register/terminal pricing is NOT on the vendor page (the $59/month figure is third-party). https://www.lightspeedhq.com/pos/restaurant/pricing/ · retrieved 2026-08-01

commercial-module-unbundling differentiator

Online ordering, Contactless ordering, Reservations, Tasks and KDS are separately priced add-ons on Starter, but independent cancellation without repricing the base subscription is not documented. https://www.lightspeedhq.com/pos/restaurant/pricing/ · retrieved 2026-08-01

commercial-hardware-purchase-outright

No published purchase-vs-lease statement or hardware price list on the US site.

commercial-hardware-not-locked differentiator

The supported-hardware article documents standard off-the-shelf devices throughout, not vendor-only ones. The POS 'requires a supported Apple device running iPadOS or iOS 18 or higher' - ordinary consumer iPad 7th gen and later, iPad mini 5th gen and later, iPad Air, iPad Pro, iPhone SE/XS through 15 - with Back Office in Chrome, Safari or Firefox. Receipt printers are third-party ESC/POS models with per-model setup guides: Epson TM-T88V(VI), TM-T20II/III, TM-T82 III, TM-T70, TM-m30 series, TM-m10, TM-P80, TM-L90/L100, TM-U220 series; Star Micronics TSP100/143 (I/III/IV), TSP650 BT series, TSP700, mC-Print3; plus Seiko RP-D10/RP-E10/MP-B20, Bixolon SRP-275III and SPP-R300, and Zebra ZD410 labels. Cash drawers are Safescan LD 3336 (EMEA) and APG Minota (NOAM) on RJ12; barcode scanners are Socket Mobile. Purchasing from Lightspeed is offered, not required: 'If you choose to buy your hardware elsewhere, we encourage you to purchase the supported models listed in this article.' The real limit is scope of support, not lock-in - 'Lightspeed only provides support for the hardware listed in this article' - and separately the integrated payment terminals are a fixed certified list (Verifone P400+/V400m/e280/e285, AMS1 and S1F2 Smart Terminals, Mobile Tap), which is a payments constraint rather than a POS-hardware one. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260800124209-Supported-hardware · retrieved 2026-08-09 adversarially verified

commercial-data-export-self-serve

Back Office supports report and stock exports, and the API exposes orders/payments/financials — but API credentials are partner- or account-manager-gated, and no complete self-serve transactional history export is documented. https://api-portal.lsk.lightspeed.app/quick-start/intro · retrieved 2026-08-01

commercial-export-customer-and-loyalty differentiator

Customer records export self-serve: Customers > Customer list > Export, 'All data will export by default, so deselect any information you wish to exclude', in Mac or PC file format. Loyalty card batches (VIP, punch) export to CSV from Back Office. Shortfall: no export of a points ledger (K-Series has no native points program) and no documented gift-card liability export; gift cards have a statistics page only. https://k-series-support.lightspeedhq.com/hc/en-us/articles/1260804657189-Importing-or-exporting-customer-data · retrieved 2026-09-03 adversarially verified

commercial-post-termination-export-window differentiator

Affirmatively adverse rather than merely undocumented: the Service Agreement states that on termination 'Lightspeed may immediately deactivate Customer's account and delete Customer Content.' No grace window is reserved for the customer. https://www.lightspeedhq.com/legal/lightspeed-service-agreement/ · retrieved 2026-08-01 adversarially verified

commercial-data-ownership-clause differentiator

Ownership is stated plainly in section 8.2: 'Customer retains all right, title, and interest in the Customer Content.' Shortfall: the same section grants the opposite of a constraint - 'a worldwide, royalty-free, sublicensable, transferable, and non-exclusive license to use, access, copy, reproduce, modify, create derivative works of, publish, communicate, transmit, translate, display, and/or otherwise exploit the Customer Content for the purpose of providing, operating, promoting, or improving the Products, including but not limited to creating benchmarking insights, market trend analysis, and recommendations using aggregate and de-identified Customer Content.' Sublicensable, transferable, and extending to promoting the Products, with the aggregate/de-identified language framed as a non-exhaustive example rather than a limit. https://www.lightspeedhq.com/legal/lightspeed-service-agreement/ · retrieved 2026-08-02 adversarially verified

commercial-pci-p2pe-tokenization

Tokenization is named in scope in the AOC - the assessed service is the 'Card Tokenization Service (CTS)' alongside the Cloud Point of Sale Application - and K series is documented as supporting P2PE compliant devices. Shortfall: the claim requires the vendor to name the resulting merchant SAQ, and no SAQ type appears anywhere in the attestation; the document is v3.2.1 (ROC January 11, 2024), and no PCI SSC validated P2PE solution listing is cited. https://pdf.lightspeedhq.com/documentation/PCI_AOC_R-C-X-K-L-O-G-Payments.pdf · retrieved 2026-08-02 · not refetchable · site policy · graded A when read adversarially verified

commercial-pci-dss-4-controls

Back Office MFA is documented: a TOTP second factor via Google/Microsoft Authenticator or OneLogin Protect, enabled per user under My account > Configure MFA; the January 2026 release notes introduce it. Shortfalls: 'Each user will need to enable MFA for their account. MFA cannot be enabled by location or by business', so it is optional rather than enforced for all cardholder-environment access, POS logins are PIN-based, and no payment-page script-integrity (Req 6.4.3/11.6.1) statement exists in the help centre or the trust-centre article (54212034872475). https://k-series-support.lightspeedhq.com/hc/en-us/articles/43642296058139-Setting-up-multi-factor-authentication · retrieved 2026-09-03 adversarially verified

commercial-privacy-dsar-tooling

A DPA is published and per-guest primitives exist: the Trust Center holds the 'Data processing agreement', 'Data retention policy', and a 'Data privacy request option'; in-app, operators can locate a customer, export their data (field-selectable customer-list export; per-customer transaction export in PDF/CSV/XLSX) and 'make changes to or delete customers', while Order Anywhere guests can self-delete accounts. Shortfalls: no DSAR-framed workflow names CCPA/GDPR request handling for guests, and deletion propagation to Guest book, card batches, or partner marketing records is not documented. https://k-series-support.lightspeedhq.com/hc/en-us/articles/23340222300059-About-data-privacy-and-security · retrieved 2026-08-05

commercial-wcag-kiosk-accessibility differentiator

No VPAT/ACR or WCAG conformance claim published for the kiosk or consumer ordering surfaces.

commercial-dual-pricing-compliant differentiator

Automatic surcharging with the compliance mechanics the claim names: 'Automatic surcharging with Lightspeed Payments is only available in Australia, Canada, and the United States'; excluded transaction types include 'Debit and prepaid cards (US and Canada)' - the automatic exclusion the claim requires - plus card-not-present and DCC; the fee is 'a percentage of the total bill added as a separate line item', the docs require that 'clear signage must alert customers of the surcharge at the point of entry, the point of sale, and on every receipt', caps are enforced by rule (max 3% US / 2.4% CA, never above cost of acceptance), and advance card-brand notification duties are spelled out. (Surcharge model only - no separate cash/card dual-price display mode - and unavailable on Mobile Tap or in Quebec.) https://k-series-support.lightspeedhq.com/hc/en-us/articles/12625085075995-Surcharging-with-Lightspeed-Payments · retrieved 2026-08-05