Linga POS

order-capture-floor-plan-editor

Back Office > Settings > Table Layout is a graphical editor: "To add a new service Floor, click + Add Floor" with floor name, dimensions and background; tables and static objects are added and "click and drag the table/object to its floor location"; per table you "Update the Name, Number of seats then select the Table Shape" (oval or rectangle); multiple floors persist as tabs on the POS Table Layout screen and changes are committed with Save then Publish. SHORTFALL: no section-to-server assignment is documented - the POS Table Layout Overview article only says each table DISPLAYS "Employee - Name of the Employee currently serving the Table", i.e. the server is derived from who owns the check, not assigned to a drawn section. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-table-layout-application-settings · retrieved 2026-08-07

order-capture-seat-level

POS: Table Layout - Split Checks documents "Split By Seat - This action will automatically move all Items on individual Seats to new Checks", alongside per-item moves, Split Evenly, and manual item moves between checks; splits are blocked only once a payment has been taken. Seat tagging at entry is corroborated by POS: Seat Order Override, which has the server "place Menu Items with different Seat Numbers" before tapping Finish, and by the Back Office General Application setting "Hide Seat Number in Kitchen Print". https://support.lingaros.com/portal/en/kb/articles/pos-table-layout-split-checks · retrieved 2026-08-07

order-capture-coursing-hold-fire

"Fire Coursing is a way to take an Order and divide it across the time spent at a Table"; from the POS Check Options screen the server selects a coursing name, which "will be sent to the Kitchen so that the Chef will be able to prepare the respective Menu Item(s) available in the selected Coursing first". Courses themselves are created in Back Office > Products/Items > Coursing with a Name and a Priority. SHORTFALL: the same article requires that "menu items must be sent to the kitchen before using this feature", so the kitchen already has the whole order and the fire action only re-prioritises it - no per-course hold that withholds a course from the kitchen is documented, the Coursing setup article does not show how a course is bound to a menu item, and no handheld/GO-device coursing flow is described. https://support.lingaros.com/portal/en/kb/articles/pos-fire-coursing · retrieved 2026-08-07

order-capture-split-merge

"Flexible Group Check Processing" with ability to split or merge items and checks. Split-by-seat, even N-way, arbitrary amount, and post-partial-payment merge not documented. https://www.lingapos.com/solutions/linga-pos · retrieved 2026-08-01

order-capture-bar-tab-preauth differentiator

The Bar Tab KB article confirms a configurable Pre-Auth setting tied to opening a tab: "If the Pre-Auth setting is enabled in the Back Office (Settings > General Settings): upon starting a new Bar Tab..." — pre-authorization on tab open is a real, documented feature. The article is primarily about renaming the Bar Tab order type ('Floating Tab') and does not state a configurable auth amount, incremental re-auth as the tab grows, or auto-close of stale tabs at end of day. https://support.lingaros.com/portal/en/kb/articles/pos-bar-tab-floating-tab · retrieved 2026-08-04

order-capture-transfer-audit

"This option is used to transfer the Check from one Server to another", and a check can be moved "from one Table to another Table of same / different Floor"; Back Office > User Management > Roles has a manager-access permission covering Discount, Transfer and Void. SHORTFALL: transfer between DEVICES is not documented, and while the Audit Log Report's POS source lists Check No, Action, Event Date & Time, Employee, Device Name, Device Type, Node and a Log of Field Name / Old Value / New Value, neither article enumerates transfer as a logged event or shows a row naming both the originating and the receiving employee. https://support.lingaros.com/portal/en/kb/articles/pos-table-layout-transfer-a-check · retrieved 2026-08-07

order-capture-native-handheld

Handheld form factor marketed and Linga Pay ships EMV/NFC terminals, but native-app architecture and send-to-kitchen plus tableside card capture on that handheld are not documented. https://www.lingapos.com/solutions/linga-pos · retrieved 2026-08-01

order-capture-offline-order-entry

KB documents an Offline Mode toggle under POS settings, disabled by default; marketing claims operation "even when the Wi-Fi goes out." No published list of what works or fails offline. https://support.lingaros.com/portal/en/home · retrieved 2026-08-01

order-capture-qr-same-check differentiator

Walked the support.lingaros.com Zoho Desk KB (JS-rendering fetch; plain fetches return an empty SPA shell). /kb/linga-pos/pos/table-layout-screen > POS: Table Layout - QR Payment is explicitly payment-only: the guest "can scan the QR code using a compatible app on their personal phone/device" and proceeds to "Complete the Payment for the Check", with no item entry. Separately, Back Office: Online Ordering Stores enumerates a Payment Settings toggle "Require Payment Before QR Menu Orders", which proves a QR menu-ordering channel exists - but neither that article nor the three articles under /kb/linga-pos/back-office/online-ordering (Stores, Account, Batch) says whether a QR menu order appends to the same open check as server-entered items or opens a separate order. Unresolved for want of a QR-menu-ordering article, not for want of the feature.

order-capture-kiosk-first-party differentiator

First-party kiosk with fully customizable menus, items, pricing and modifiers syncing in real time. No ADA/accessibility conformance documentation. https://lingapos.com/solutions/kiosk · retrieved 2026-08-01

order-capture-drive-thru

2026-09-03 re-sweep (195th): the full support.lingaros.com KB (605 articles, 48 release-notes issues through 26-08-003) and www.lingapos.com were read; an analyst proposed no from https://support.lingaros.com/portal/en/kb/articles/pos-operation-pos-settings and the adversarial pass returned it to unknown: pos-operation-pos-settings.txt line 1 URL matches, but the proposal's quote is TRUNCATED: the source list continues with a sixth option, 'Web Order – This option is used for denoting whether the restaurant is open or not while creating an online order by the Customer.', and the note itself concedes Dine In and Bar Tab are order surfaces not on this list, so 'The following options are available:' closes only the Order Type pop-up toggles, not the product's order flows. More decisively, lingapos-com/restaurant__quick-service.txt (www.lingapos.com/restaurant/quick-service) states 'Contactless curbside pickup and drive-thru let guests pick up orders from their vehicles: safely, efficiently, and on their schedule.' - a vendor page asserting drive-thru, which a corpus-silence no cannot stand against. Nothing anywhere (606 KB files + lingapos-com) mentions order-point/pay-window separation, lane sequencing, or pull-forward; the KB's only vehicle construct is the OLO Curbside order type ('Curbside – Details of the vehicle used when picking up the customer's orders'). The marketing sentence does not evidence any of the three claim elements, so not partial; the enumeration is not closed, so not no. Prior rationale: Walked support.lingaros.com /kb/linga-pos: all 17 entries under /pos (including Phone / Web Orders and its 13 leaf articles, Third Party Integration, Table Layout Screen, Check Options), /back-office/online-ordering, and Back Office: Online Ordering Stores, whose Order Settings enumerate Delivery, Pickup, Curbside Pickup, ASAP and Future Orders - no drive-thru order type. No order-point / pay-window / pickup-window separation, lane sequencing or pull-forward/parking-spot assignment appears in any article reached. Kept unknown rather than no because the /software section index returned an empty body on a JS-rendering fetch and the Order Types configuration article was not reachable by tree navigation, so I have no enumeration that asserts the order-type list is complete. adversarially verified

order-capture-drive-thru-timers

2026-09-03 re-sweep (195th): the full support.lingaros.com KB (605 articles, 48 release-notes issues through 26-08-003) and www.lingapos.com were read; an analyst proposed no from https://support.lingaros.com/portal/en/kb/articles/pos-operation-pos-settings and the adversarial pass returned it to unknown: Rests entirely on the same Order Type enumeration as order-capture-drive-thru, which is not closed (Web Order omitted from the quote; Dine In/Bar Tab elsewhere) and is contradicted by the lingapos.com quick-service page's 'drive-thru' sentence; the analyst's own audit note says to hold this at unknown if that cell is. Independently, 'speed of service', 'timer', 'elapsed' occur nowhere on the quick-service or KDS marketing pages, and the KB's only elapsed-time surfaces are generic KDS colour thresholds and 'Order Elapsed Time' on Table Layout. No evidence of segment timers either way. Prior rationale: Enumerated support.lingaros.com /kb/linga-pos/back-office/reports - 25 report families (Void, Transaction, Till, Tax, Sale Reports incl. Hourly/Daily/Sale Recap/Future Order/Online Sales, Revenue Center, Refund, Paid In/Out, Membership, Inventory, House Account, Gift Card, Fiscal/ZATCA, Feedback, Employee incl. Attendance/Role Based Payroll/Labor, Driver, Discounts, Exporting, Daily Tender, Daily Summary, Customer Preference, Comparison, Batch, Audit Log, Account Balance) - and none is a drive-thru or segment speed-of-service report; the only elapsed-time surface found is the per-table "elapsed time" shown on the POS Table Layout screen. Left unknown because a KB section index is not a document asserting its own completeness, and no drive-thru order flow exists to time (see order-capture-drive-thru). adversarially verified

order-capture-voice-ai differentiator

Read Back Office: Third Party Integrations Settings (Settings > Integrations > Third Party Integrations), which lists Chowly, Compeat, Deliverect, DoorDash, PayPal, Platform Price Level, Restaurant 365, Uber Eats, Urban Piper and Yemek Sepeti; the /kb/linga-pos/back-office/integration-hub index (Octopus, Order Webhook, Servme, Uber Eats, Shogo, Restaurant365, Deliverect, Chowly, ADP, DoorDash Drive, Dash Solutions, Factor4, ADP WFN); and /kb/linga-pos/pos/third-party-integration (Uber Eats, Servme, DoorDash Drive, Deliverect, Chowly). No first-party AI voice-ordering agent and no voice-AI partner program appears in any of them. Both surfaces are integration DIRECTORIES, which do not carry the enumeration bar, so this stays unknown; developer.lingaros.com was not reachable for a partner-program check within this pass.

order-capture-throttling differentiator

The Online Ordering store settings page carries a Throttling Settings section with two tabs. Time Based: separate Delivery Preparation Time and Pickup Preparation Time (minutes) plus, per day of week, Enable Delivery / Enable Pickup, Start and End times, a Time Period, a "Maximum Orders" cap for that period, and an "Additional Wait Time" applied when the cap is exceeded. Order & Crew Based: Order Per Crew, Base Quote Time, Maximum Orders Per Crew and Additional Wait Time for kitchen load, and Deliveries Per Driver, Base Quote Time, Maximum Orders Per Driver and Additional Wait Time for delivery. That is per-channel capacity per time slot with automatic quote-time extension above a configured threshold. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-online-ordering-stores · retrieved 2026-08-07

order-capture-scheduled-orders

Back Office: Online Ordering Stores > Order Settings has "Enable/Disable Future Orders with advance time limits (days and hours)" alongside ASAP, and separate Delivery Preparation Time and Pickup Preparation Time. Orders marked Later (in-store) or Future (online) sit in the POS Phone / Web Orders "Future" tab, and the Back Office setting "Print Future Orders Before" (Settings > Application > Delivery > Delivery Settings) sets how many minutes ahead the order fires: an order due 4:20pm with a 10-minute setting "will be moved to the Active order tab based on the Time set in BO" at 4:10pm. Note the print-ahead lead itself is a single store-level value; the per-channel component is the separate delivery vs pickup preparation times. https://support.lingaros.com/portal/en/kb/articles/pos-phone-web-orders-print-before-future-order · retrieved 2026-08-07

order-capture-catering

Checked, on support.lingaros.com, the full Back Office: Online Ordering Stores settings enumeration (General, Ordering Hours, Order Settings, Checkout Settings, Payment Settings, Notifications, Links, Throttling, Delivery Zones - no catering), the 13 POS Phone / Web Orders leaf articles, /kb/linga-pos/back-office/online-ordering, and Back Office: Third Party Integrations Settings. Nothing describes a catering order type, quotes, deposits, balance-due tracking or an event schedule separate from the standard queue. Kept unknown because deposit/balance mechanics could plausibly sit in House Account (Back Office > Customers > House Account) or Membership, neither of which I read in full, and no document asserts the order-type list is complete.

order-capture-order-ready-signal differentiator

With Uber Eats, Deliverect or Chowly enabled, the POS Phone / Web Orders screen gains an extra Ready control: "Tap the Order in the New tab and tap Ready to send notification to the 3rd party service", which alerts the third-party driver that the order is prepared. SHORTFALL: this is a manual tap by staff, not a signal derived from POS or KDS state - the Integration Hub Order Webhook settings article enumerates only Close Order, Open Order, Update Order and 3rd Order webhooks, with no order-ready or order-status event, and the Deliverect integration article describes only the outbound menu push. https://support.lingaros.com/portal/en/kb/articles/phone-web-orders-third-party-integration-differences · retrieved 2026-08-07

order-capture-void-comp-controls

Role-permission-gated void with mandatory Back Office-configured reasons is documented ("Only Employees with the proper Role and Permission settings have access to Void the Order"); role permissions separately enumerate Void Item, Discount and Void Check, the Void Report records Void By and Void Reason, and the Audit Log Report captures employee, timestamp and old/new values for POS/BO actions generally. Shortfall: comps are not named as a distinct gated action alongside voids/discounts, and no single consolidated exception report covering void+comp+discount instances together is documented — the record is split across the Void Report and the Audit Log Report. https://support.lingaros.com/portal/en/kb/articles/pos-check-options-void-item-23-9-2025 · retrieved 2026-08-04

menu-pricing-nested-modifiers

"Add mandatory and optional modifiers" (forced-selection flag) and "smart modifiers"; POS markets menu structure "from simple to complex." Nesting depth and per-level min/max counts not documented. https://lingapos.com/restaurant/pizzeria · retrieved 2026-08-01

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

Modifier record carries a Serving Sizes price table — "For each Serving Size, enter a Price for the Serving Size and each Prefix" — so one modifier is priced per parent size without duplication. Pricing the same modifier differently on two parent items at the same size is not documented; the matrix is size x prefix, not item x size. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-modifiers · retrieved 2026-08-03

menu-pricing-fractional-placement differentiator

I verified both strings verbatim on /restaurant/pizzeria and confirmed the page contains nothing about pricing methodology. Upheld at partial, but hardened: the only source is a vertical marketing landing page, 'smart modifiers' is undefined anywhere on the site, and nothing establishes a fractional placement data model as opposed to pre-built half/half menu items. The dossier's downstream conclusion is right — per-section pricing, included-topping allowances and size-by-crust matrices are entirely unevidenced. https://lingapos.com/restaurant/pizzeria · retrieved 2026-08-01 adversarially verified

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

"Half and Half" is one of the Menu Types offered when creating a Products/Items record (alongside Menu Item, Menu Item With Serving Size, Open Item, Scale Item and Combo Item), and Back Office > Products/Items > Serving Size Level carries a "Half and Half" toggle on each level. SHORTFALL: the configuration surface for it is a fixed price table - "For Selected Items: a table appears with a Half and Half Item representing each row" and the operator sets "the S. No and Unit Price for the item". No operator-selectable pricing rule (charge the higher-priced half, average the halves, or charge toppings at a fraction of full price) appears on the item article, the Serving Size Level article, the Modifiers or Modifier Groups articles, or the Upcharges article; prices are keyed per combination instead. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-products-items · retrieved 2026-08-07 adversarially verified

menu-pricing-topping-quantity-tiers

Per-modifier Prefix rows (light/extra-style tiers) each carry a Price Field with an "Override Modifier Price" toggle, and the serving-size table takes a price per Serving Size and each Prefix — a configurable per-tier price distinct from adding the modifier twice. Tier price is an absolute amount, not a multiplier. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-modifiers · retrieved 2026-08-03

menu-pricing-size-style-matrix differentiator

The item editor offers a "Menu Item With Serving Size" Menu Type, and Back Office > Products/Items > Serving Size Level defines the size set (Name, Description, Half and Half toggle), giving a per-size base price - one axis. SHORTFALL: no second variant axis on the base price is documented. The item article's pricing surface is Menu Type + Cost Type (Fixed/Variable) + a Price Level Settings toggle with a Level field, not a size x style grid, and the only two-axis price table in the corpus is on MODIFIERS (serving size x prefix, per menu-pricing-modifier-price-by-parent-size), not on the base item. Crust/preparation variants would have to be carried as modifiers with upcharges rather than as per-cell base-price overrides. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-products-items · retrieved 2026-08-07

menu-pricing-included-allowance differentiator

Included Modifiers are "automatically added to the Order screen" and removal credits the guest — "the price of the Modifier will be reduced from the Menu Item Cost"; "Negative pricing for the prefixes will be allowed only for the Included Modifier." A count-based allowance (e.g. any 3 toppings included, charge only overage) is not documented — inclusion is per named modifier. https://support.lingaros.com/portal/en/kb/articles/pos-modifiers · retrieved 2026-08-03

menu-pricing-combos

Combo Item is one of the Menu Types in Back Office > Products/Items; to build one you "Select the Menu Item and Serving Size from the dropdowns. Enter the Number of Servings [S. No] ... Enter the Unit Price." The Price Level Settings toggle is the one item option explicitly withheld from Combo Item. SHORTFALL: components are priced by a fixed per-component Unit Price with no swap-with-price-delta mechanism documented, and nothing in the item article or the Discounts (Mix-and-Match) article describes the POS detecting eligible a-la-carte items in an open check and converting them to the combo price. This also supersedes the earlier note that the "Special Combo Menu Item" article 404s: the combo surface is documented, on the main Products/Items article. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-products-items · retrieved 2026-08-07

menu-pricing-upsell-prompts differentiator

Quote: "Point of sale prompts making staff and customers aware of upsell options like chargers, cases, or add-ons with core items." Feature pages claim upsell prompting on the customer-facing display ('Add a promotional message to customer-facing displays to boost special menu items' on the CFD page) and item-linked add-on prompts in retail ('Point of sale prompts making staff and customers aware of upsell options like chargers, cases, or add-ons with core items' and 'Easily connect products with compatible add-ons to simplify upselling' on retail/electronics). Shortfall: the CFD prompt is a store-level promotional message, not a per-item rule; nothing says prompts are configurable per channel (POS/kiosk/online); no attach-rate reporting is claimed anywhere; and the KB item field walk has no suggestive-sell field. Grade C -> partial. https://www.lingapos.com/retail/electronics · retrieved 2026-09-03 adversarially verified

menu-pricing-86-propagation

The 86 List article states the decremented Quantity "will be reflected in iPad, POS and OLO" (Linga's own online ordering), and in a worked example the Quantity is reduced "in iPad, Zenpepper and POS" — cross-device and first-party-online-ordering propagation is documented. KDS, kiosk, and connected third-party marketplace propagation are not mentioned anywhere in the article, and no propagation-latency figure is stated. https://support.lingaros.com/portal/en/kb/articles/pos-operation-86-list · retrieved 2026-08-04

menu-pricing-countdown-auto-86 differentiator

86 List holds a Back Office-configured per-item quantity that decrements on every sale across devices and blocks the sale at zero ("Quantity is not enough"); voids restore the count. No scheduled auto-restore is documented — replenishment is manual or via void reversal. https://support.lingaros.com/portal/en/kb/articles/pos-operation-86-list · retrieved 2026-08-03

menu-pricing-dayparting

The Back Office item editor has an Availability section offering always-visible or time-based restriction, with Days of Week, Days of Month, Date Range, Specific Date and Date Range with Time options, plus per-channel visibility (hide from Kiosk, POS, Online Order). Timezone is handled on the ordering side: Back Office: Online Ordering Stores > Ordering Hours begins with a Time Zone selection, then per-day Store Time / Delivery Time / Pick Up Time and Holiday Hours. SHORTFALL: the schedule is per ITEM. No menu-level activation schedule is documented (Enterprise > Menu Configuration is a store-to-store copy tool, not a schedule), and no time-scheduled PRICE change is documented - the item's Price Level Settings toggle and Level field have no article describing what drives the level. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-products-items · retrieved 2026-08-07

menu-pricing-channel-price-books

The Uber Eats integration article documents "you can set the order platform price level for menu price level, and modifiers percentage" — a distinct price level with a percentage markup applied automatically per delivery-platform integration. Shortfall: this covers only the delivery-marketplace channel dimension; it does not state that dine-in, pickup, and kiosk each carry their own distinct price book, and a separately search-indexed article ('Price Levels for Food Delivery Channels') that appears to cover this in more depth returns HTTP 404 on direct fetch and could not be read. https://support.lingaros.com/portal/en/kb/articles/uber-eats-integration · retrieved 2026-08-04

menu-pricing-dual-pricing differentiator

Dual Price is a single store-level percentage (Settings > Payments > Payment Settings, "Dual Price Percentage" to 3 decimal places), not item-level stored prices — that is the shortfall. Channel coverage is otherwise complete: the order screen shows the Dual Price value as the Cash Price, the CDS shows it before payment, kiosk and online ordering show it "after Total as Pay with Cash", and receipts print a Cash Subtotal line (Sub Total $10.40 - Dual Price $0.40 = $10.00) with the card price as the base menu price. https://support.lingaros.com/portal/en/kb/articles/pos-payment-surcharge-dual-price · retrieved 2026-08-04

menu-pricing-allergen-nutrition

Back Office: Products/Items - Products/Items walks the complete create/edit surface of a menu item: POS Display Button, Name, Secondary Name, PLU Code, Preparation Time, Kitchen Printer Name, Category/Sub-Category, Description; Menu Type, Cost Type, Price Level Settings, Taxes; Included / Mandatory / Optional Modifier Groups; Availability (days of week, days of month, date range, specific date, date range with time); visibility per channel, EBT designation, 86 List, kitchen and label printer routing; and Inventory (Inventory Items, Sub-Recipes, manual cost entries). There is no allergen flag and no nutrition or calorie field anywhere on that surface, and the inventory linkage carries cost, not nutrition, so recipe-derived nutrition has no input. Read against the item editor as the enumeration - a free-text Description is the only place allergen text could be typed, and it is not a structured flag publishable to online ordering or third-party menus. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-products-items · retrieved 2026-08-07

menu-pricing-recipe-linkage differentiator

Support KB documents Recipes linking products so a sale deducts inventory. Item-level theoretical food cost output not documented. https://support.lingaros.com/portal/en/home · retrieved 2026-08-01

menu-pricing-3p-menu-push

Achieved largely through middleware — Deliverect and Chowly are named partners, with Uber Eats also listed. Per-item sync status and rejection-error surfacing not documented. https://lingapos.com/integration-hub · retrieved 2026-08-01

menu-pricing-dynamic-pricing

Quote: "Platforms – The names of the platforms that are currently integrated with Linga. Price Level – Set the price level from Price Level 1 to Price Level 9 . Modifiers % – Set the modifier percentage." Establishes rule-based price variation by CHANNEL: each integrated platform is mapped to one of nine per-item Price Levels plus a modifier mark-up percentage (Products/Items: 'The Price Level Settings toggle appears for all Menu Types except Combo Item'). Time-based variation exists only indirectly: Upcharges and Discounts carry Available/Restriction Time windows ('The respective Upcharge will appear in the POS only during the Available Time configured in the Back Office (BO)'). Shortfall: no demand-driven rules, no automatic time-of-day base-price change (only add-on upcharges/discounts), and no floor/ceiling guardrail anywhere - 'dynamic pric', 'happy hour', 'surge' occur zero times. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-third-party-integrations-settings · retrieved 2026-09-03 adversarially verified

payments-processor-choice differentiator

Re-pointed: the previously cited pnc.mediaroom.com URL was truncated and 404s; the release is live at investor.pnc.com and at pnc.mediaroom.com/2022-09-26-...-FIRM,-LINGA, and the sentence is verified there - Linga 'was the first processor agnostic, cloud-based POS system designed specifically for the hospitality industry'. That is boilerplate in the 'About Linga' section of a September 2022 press release, i.e. vendor marketing (grade D), and it describes the product pre-acquisition. Named shortfall: no first-party documented list of supported processors or gateways could be located anywhere in 2026 - LINGA's own Integration Hub (lingapos.com/integration-hub) enumerates DoorDash Drive, Deliverect, Chowly, Uber Eats, Octopus Bridge, ADP, Restaurant365, Shogo, Dash Solutions and Factor4, and contains no payment processor or gateway at all - while LINGA's Sales Terms and Conditions positively document the counter-pressure: a customer opting into the Complimentary Hardware Program 'agrees to three (3) year term for SaaS Services and Hybrid Payments Merchant Processing', with a cancellation fee of 100% at 0-3 months tapering thereafter. Processor agnosticism is asserted architecturally and unevidenced commercially; a differentiator yes needs grade A or B and this is D. https://investor.pnc.com/news-events/financial-press-releases/detail/360/pnc-announces-acquisition-of-point-of-sale-and-payments-solutions-firm-linga · retrieved 2026-08-09

payments-published-rates differentiator

The Linga Pay product page markets capability and same-day funding but publishes no flat rate and no interchange-plus markup. https://www.lingapos.com/solutions/linga-pay/ · retrieved 2026-08-01

payments-dual-pricing differentiator

Payment Settings > Payment Surcharge > Dual Price applies a "Dual Price Percentage" (up to 3 decimal places) as a cash discount and prints a Cash Subtotal line (Sub Total $10.40 - Dual Price $0.40 = $10.00) on the check and receipt. It is a single store-level percentage computed at tender, not two stored prices per item; gratuity and multi-currency checks are excluded. https://support.lingaros.com/portal/en/kb/articles/pos-payment-surcharge-dual-price · retrieved 2026-08-03

payments-surcharge-guardrails differentiator

Surcharge is enabled per store (Settings > Payments > Payment Settings) and payment types flagged Debit are force-exempted ("the Exempt Surcharge toggle will automatically be set to YES ... and will be greyed out"), with a compliance acknowledgment logged with date and time. Exemption keys off the operator-configured payment type, not BIN/product-code detection; prepaid cards and network percentage-cap enforcement are not documented. https://support.lingaros.com/portal/en/kb/articles/pos-payment-surcharge-surcharge · retrieved 2026-08-03

payments-emv-nfc

"EMV-Ready Terminal"; "EMV, NFC, Apple Pay, and more—built-in and ready"; swipe, insert, or tap. https://www.lingapos.com/solutions/linga-pay/ · retrieved 2026-08-01

payments-softpos-tap-to-pay differentiator

2026-09-03 re-sweep (195th): the full support.lingaros.com KB (605 articles, 48 release-notes issues through 26-08-003) and www.lingapos.com were read; an analyst proposed no from https://support.lingaros.com/portal/en/kb/articles/pos-hardware-requirements and the adversarial pass returned it to unknown: pos-hardware-requirements.txt line 1 matches and 'Note: Linga POS is currently unavailable on iPhone' is verbatim - the iPhone half is a durable structural no (keep it in the rationale). The Android half fails the enumeration bar: pos-operation-card-reader-hardware-settings.txt lists EMV devices 'configured in the Back Office' plus Edynamo/Tdynamo, and the Payment Method tender list is a list of processors, not of acceptance methods; neither self-describes as the complete set of ways a card can be presented. lingapos-com/solutions__linga-go.txt says 'Swipe, insert, and tap to pay are the current transaction capabilities.' and 'LINGA Mobile, LINGA Tablet, or a compatible Android device is required.' - tap on a hardware reader (swipe/insert need one), so it does not establish softPOS, but 'a compatible Android device' with 'tap to pay' leaves the phone-only question open. 'softpos', 'tap to phone', 'NFC' occur zero times corpus-wide; KB 'Insert/Tap/Swipe the Card screen ... for PAX devices' is terminal tap. Claim is 'iPhone and/or Android'; one half structurally no, the other silent -> unknown. Prior rationale: Read Back Office: Payment Method Settings on support.lingaros.com, which enumerates the tender set: Cash, Side CC, SPPAX, Dejavoo, MPPG Credit Card, Membership, Evertec, PayPal, Venmo, Gift Card, Bionet Meal Card, GiveX, NMI Tokenization, Optomany, Ingenico, LPG - every card path is a physical reader or gateway, and no Tap to Pay on iPhone or Android tap-to-pay entry appears. Also read Back Office: Store Payment Settings (manual submit, tokenize, loyalty restriction, refund service charge, offline payments, payment surcharge, surcharge exemptions) with no softPOS option. Left unknown rather than no because tap-to-pay on a phone would plausibly be a property of a device/terminal profile rather than a tender type, and the hardware side could not be confirmed: /kb/articles/back-office-2024-hardware-requirements returns HTTP 404 and /kb/linga-pos/hardware-and-networking lists only Bluetooth Scanner, POS Terminal Requirements, Hardware Requirements and Domain as unopened section stubs. adversarially verified

payments-pay-at-table

Handheld form factor plus EMV/NFC terminals marketed; tip prompt and check splitting on the handheld at the table not documented. https://www.lingapos.com/solutions/linga-pay/ · retrieved 2026-08-01

payments-qr-guest-pay differentiator

"QR Code Payments" for fast contactless payment, and "QR Pay" on the online-ordering page. Automatic closure of the corresponding POS check not documented. https://www.lingapos.com/solutions/linga-pay/ · retrieved 2026-08-01

payments-tip-adjust

A "Batch/Tip Adjustment" function is confirmed to exist — it is named directly in the Offline Mode KB's list of operations unavailable offline ("Submit Batch, Process Offline, Till, Reports, Audit, Open Cash Drawer, Pay in, pay out, 86 list, Refund, and Batch/Tip Adjustment"), and the separate POS: Tip Threshold article documents a manager-approval popup triggered when a tip exceeds a configured dollar threshold. Shortfall: whether Batch/Tip Adjustment is specifically a pre-auth-then-adjust workflow with a defined adjust window, and whether it surfaces a manager screen listing unadjusted tips, is not described. THE QUOTED LIST WAS WRONG IN THE RECORD AND IS CORRECTED HERE: the prior note omitted "Open Cash Drawer" from the middle of the enumeration. The verdict never turned on it, but a quotation that has drifted is how a false verdict gets built later. [Citation repaired 2026-08-09: the cited article 404s and this evidence now rests on pos-offline-mode-8-5-2025, the successor, where the quotation above was re-verified verbatim.] https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-8-5-2025 · retrieved 2026-08-09

payments-tip-pooling differentiator

The Tip Out & Tip Sharing settings page (Back Office > Settings > Reports) has Tip Outs and Tip Sharing tabs: you "Select the role in the dropdown that the tip out will be shared from" and to, "Enter the percentage amount ... of tip out to the employee", select whether "the employee tip out will be paid from the percentage of Sales or Tips", optionally enable a "Tip Share Per Hour" toggle, and scope by department; each rule appears as a row in the table. The allocation lands per employee in the Employee > Role Based Payroll report, whose columns include CC Tip, Grat, Other Tips (gift card, membership, house accounts, loyalty, GiveX), Declared Cash Tip and Overall Tip ("sum of tip out, tip share, gratuity, driver compensation and declared tips"), with a dedicated Tip Out Share report showing "a breakdown of employees' Tip Sharing, based on Role"; Back Office: Exporting Reports covers export, and ADP / ADP WFN payroll integrations are in the Integration Hub. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-tip-out-tip-sharing-report-settings · retrieved 2026-08-07

payments-offline-store-and-forward differentiator

Back Office > Settings > Payments > Store Payment Settings carries an Offline Payments Settings block with two configurable caps: "Each Offline Payment Amount Limit - For the Limit Amount, enter maximum value that can be processed for each offline transaction" and "Total Offline Payments Limit - Enter the Maximum Amount that represents the sum of all payments during the offline period", constrained so "The Maximum Amount must be greater than the Limit Amount. Both values must be greater than 0.00." On the POS side, an "Allow Offline Payment" toggle (POS Operations > POS Settings) warns "Payments will be taken in offline mode. Make sure to authorize your offline payments"; "the actions stored locally during offline mode will be posted to the server" on reconnect, and the operator is prompted to process the accumulated offline payments. The docs also warn not to accept debit cards offline because the transaction is more likely to be declined, i.e. decline liability sits with the merchant. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-store-payment-settings · retrieved 2026-08-07 adversarially verified

payments-offline-decline-liability differentiator

Post-reconnect visibility exists: the batch screen flags failed offline transactions ("the dark red highlight indicates already processed offline clicked checks which are failed/invalid"). The shortfall is the liability half of the claim: no Linga page states who bears the loss when a stored offline transaction declines; the Offline Mode KB only advises "Do not accept Debit Card payment from the customer, as the transaction is more likely to be Declined". https://support.lingaros.com/portal/en/kb/articles/pos-payments-offlinemode · retrieved 2026-08-04

payments-gift-cards

Partial upheld but the citation is wrong and should be replaced. The Linga Pay page mentions gift cards only as a footer navigation link — that is not evidence. The real source is /solutions/gift-cards, which documents 'Digital and Physical Card Options', 'Reloadable Balances', and 'Works Across All Store Locations' with redemption 'at any participating store'. Better support for cross-location balance than the dossier had, though liability reporting and online-channel redemption remain undocumented. The ambiguity the dossier flags is real: Factor4 'brings gift cards directly into LINGA's POS' https://www.lingapos.com/solutions/gift-cards · retrieved 2026-08-01 adversarially verified

payments-house-accounts

The Offline Mode KB confirms House Account is a real object type in Linga: "Memberships, Customers and House account can't be created" while offline (i.e. it can be created when online). Per-account credit limits, running balance, and periodic statement/invoice generation are not described anywhere in this or other reachable Linga documentation. [Citation repaired 2026-08-09: the cited article 404s and this evidence now rests on pos-offline-mode-8-5-2025, the successor, where the quotation above was re-verified verbatim.] https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-8-5-2025 · retrieved 2026-08-09

payments-split-tender

The POS Payment screen's Split option "Divides payment into fractions (1/2 through 1/9)" and "If another Split combination is selected for the Balance Due amount: that Amount will be split based on the combination selected, and the value will appear under the Payment Method section" - so nine even shares, above the claim's eight-way bar. Multiple tenders on one check: POS: Multi Cash Payments states "If the paid multi-currency value is less than the Check, then the remaining balance can be paid using the same multi cash or with another payment method", and POS: Partial Payments in OLO states "Partial payments can be made via loyalty, Cash, credit card or gift card or any other payment options", with each shown as "Payment 1 Success", "Payment 2 Success" and the order closing only at a $0.00 balance; no cap on the number of payments is stated. By seat and by item come from POS: Table Layout - Split Checks (Split By Seat, Separate Item, Split Evenly, manual moves). https://support.lingaros.com/portal/en/kb/articles/pos-payment-screen-options · retrieved 2026-08-07

payments-refund-void-controls

"Only Employees with the proper Role and Permission settings have access to Void the Order", with mandatory Back Office-configured void reasons; role permissions include Void Item, Discount and Void Check, the Void Report records Void By and Void Reason, and the Audit Log Report captures POS/BO actions with employee, timestamp and old/new values. No-sale authorization, a distinct approver identity, and log immutability are not documented. https://support.lingaros.com/portal/en/kb/articles/pos-check-options-void-item-23-9-2025 · retrieved 2026-08-03

payments-chargeback-tooling differentiator

On support.lingaros.com read Back Office: Store Payment Settings (manual submit for credit card, tokenize the credit card, restrict loyalty payment on membership discount, include service charge for refunds, offline payments settings, payment surcharge, surcharge exemptions), Back Office: Payment Method Settings (16 tender types), Back Office: EMV Payment Settings, Back Office: Payment Till Settings, and the /back-office/reports index including Refund Reports, Transaction Report and Batch Reports (Batch / Failed Batch). None of them exposes an open-disputes list, a chargeback dashboard, or evidence submission assembled from the transaction record - the closest is a Failed Batch view, which is settlement failure, not a dispute. Left unknown because disputes would normally live in the processor's own portal (Linga Pay / MPPG / SPPAX) rather than the POS back office, and none of these pages asserts it is the complete payment feature set.

payments-card-on-file differentiator

Back Office > Settings > Payments > Store Payment Settings has "Tokenize the Credit Card - If Enabled (set to YES), then Card details will be saved for the selected (highlighted in pink) Service Type(s)", and NMI Tokenization is one of the tender types in Payment Method Settings, so tokenized card storage exists and the merchant is not holding PANs. SHORTFALL: the token is scoped to a SERVICE TYPE on the store (the bar-tab / pre-auth pattern), not to a guest. Back Office: Customers - Customer Info enumerates the whole customer record - name, phone, email, gender, DOB, nationality, anniversary, photo, gate code, customer ID, notes, stores, address, loyalty enrolment, points, gift card number, and past receipts - with no saved payment method, and Back Office: Online Ordering Stores' Payment Settings (online payment sale/authorization, accepted card brands, cash, gift card) has no saved-card management. Nothing documents one token being reused by a guest across online, phone and in-store. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-store-payment-settings · retrieved 2026-08-07

payments-payout-timing differentiator

A two-word marketing bullet on a sales page cannot support a 'yes'. There is no cutoff time, no eligibility criteria, no fee for expedited funding, no standard deposit schedule, no bank-day qualification, and no statement of whether same-day funding requires a PNC deposit relationship — which, given the parent, is a live question. The dossier's own note concedes 'standard deposit schedule and eligibility conditions not published', which is a partial by its own reasoning. https://www.lingapos.com/solutions/linga-pay/ · retrieved 2026-08-01 adversarially verified

payments-p2pe-pci4

Marketing claims "100% PCI Compliant" and "Always PCI Compliant." No AOC, no PCI DSS version named, no validated P2PE listing, no SAQ type stated. https://www.lingapos.com/solutions/linga-pay/ · retrieved 2026-08-01

kitchen-station-routing

"Send items by type (e.g., appetizer, entrée) to specific screens or printers." Routing by order type or revenue center not documented. https://www.lingapos.com/solutions/kitchen-display-system-kds/ · retrieved 2026-08-01

kitchen-expo-consolidation

Back Office > Settings > Hardware > Kitchen Printers configures a device of type 'KDS' with an 'Expo Device' option: 'If YES, enter the: Expo Printer IP Address [and] Queue Device IP Address', and a store-wide setting 'Send Notification from Every KDS Station'. Shortfall: an expo/queue device is configurable and multi-station notification exists, but no Linga documentation describes the expo screen consolidating items from multiple prep stations into a single order view, and nothing states that an order is marked complete only once every contributing station has bumped. The Zoho Desk KB has no KDS operating article at all - the 17-entry /portal/en/kb/linga-pos/pos section and the 4-article hardware-and-networking section contain none. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-kitchen-printer-hardware-settings · retrieved 2026-08-07

kitchen-course-firing differentiator

POS: Check Options - Fire Coursing: from the Menu screen select the options button, choose 'fireCoursing', then 'select any one of the Coursing names by tapping on it'; 'The selected Coursing will be sent to the Kitchen so that the Chef will be able to prepare the respective Menu Item(s)' in that course first. Courses are defined in Back Office under Products/Items > Coursing (Name, Priority) and reassigned per item at the POS via Menu Options > Change Coursing. Hold is a separate POS action (Check Options > Hold; Menu Options > Hold an Item). Caveat recorded: the article states 'Before selecting Fire Coursing, the ordered Menu Item(s) must be sent to the Kitchen', so the fire acts on already-sent items; the interaction between Hold and coursing is not spelled out. Firing is documented from the POS terminal only - no handheld or expo-screen fire action is described. https://support.lingaros.com/portal/en/kb/articles/pos-fire-coursing · retrieved 2026-08-07

kitchen-prep-time-pacing differentiator

Quote: "Sort By Due Time – Item Preparation Time is sent from BO to POS." Per-item cook time IS configurable: Products/Items has a 'Preparation Time' field ('use ▲▼ to set the Prep Time'), KDS Configuration notes 'KDS Done Button – If Enabled , KDS can't store item-based prep time. If disabled, KDS can store it', and 26.03.001 sends Item Preparation Time to the KDS. Shortfall: the only documented use is ORDER-level sorting by due time (26.08.001 bug fix: 'orders were being sorted based on menu item preparation time instead of the order's Pickup/Due Time'); nothing describes staggering item start/display so items on one order finish together - KDS Separate Cards splits by send-to-kitchen action, not by cook time. https://support.lingaros.com/portal/en/kb/articles/26-03-001-release-notes · retrieved 2026-09-03 adversarially verified

kitchen-order-throttling differentiator

Back Office > Online Ordering > Stores has three sections - General, Throttling, Delivery Zones. Time Based tab: 'Delivery Preparation Time', 'Pickup Preparation Time'; per day of week, 'Base Quote Time - Enter the minimum amount of time (in minutes) for an order to be prepared', 'Maximum Orders - Enter the maximum number of orders allowed for the service per day', 'Additional Wait Time - Enter any potential additional amount of time (in minutes) beyond the Time Period'. Order & Crew Based tab: 'Order Per Crew', 'Maximum Orders Per Crew', 'Base Quote Time', 'Additional Wait Time' for crew, and 'Deliveries Per Driver', 'Maximum Orders Per Driver', 'Base Quote Time', 'Additional Wait Time' for delivery. That is a configurable order-volume threshold extending the quoted prep time - the mechanism the claim asks about. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-online-ordering-stores · retrieved 2026-08-07

kitchen-channel-pause-propagation differentiator

Quote: "If the quantity of any item on the 86 List reaches zero ( 0 ), Redis will communicate to Deliverect that these items are out of stock (the PLU Code of each item will be snoozed)" Automatic 86 propagation exists, but only through the Deliverect middleware partner (also Nov-12-2024 notes: 'Deliverect - 86 list snooze time for Menu item - Online Ordering'). Shortfall: the native Uber Eats and Chowly integrations expose only manual 'Publish Menu Items' actions and no availability sync; the native 86 List article says quantity changes reflect in 'iPad , Zenpepper and POS' (Linga channels only); no store-pause propagation is documented for any marketplace; DoorDash marketplace and Grubhub are not integrated natively (DoorDash Drive is delivery dispatch). Yemek Sepeti has an 'Is Restaurant Open' toggle but it is a manual setting, not propagation. https://support.lingaros.com/portal/en/kb/articles/deliverect-integration · retrieved 2026-09-03 adversarially verified

kitchen-order-ready-callback differentiator

POS: Phone / Web Orders - Third Party Integration Differences: for Uber Eats, Deliverect or Chowly accounts a 'Ready' button appears in the bottom navigation - tap an order in the New tab and select 'Ready to send notification to the 3rd party service that the Order is ready for their Driver'. The POS Uber Eats article repeats it: 'This button is to notify the 3rd party drivers that the order is ready for pick up'. Shortfall: the ready event is raised by a cashier tapping a button on the POS order list, not by bumping the ticket on the KDS, and no KDS-to-marketplace status callback is documented; DoorDash Drive has no Ready button at all (it uses 'Request Driver' instead), so courier dispatch there is a manual request rather than a readiness signal. https://support.lingaros.com/portal/en/kb/articles/phone-web-orders-third-party-integration-differences · retrieved 2026-08-07

kitchen-bump-bar-hardware

"Easy to Use Bump Bar" documented. No list of supported bump-bar or keypad models published. https://www.lingapos.com/solutions/kitchen-display-system-kds/ · retrieved 2026-08-01

kitchen-all-day-counts

Checked support.lingaros.com by navigating the tree (the portal is a JS-rendered Zoho Desk site; plain fetches return an empty SPA shell and the in-portal search returns a fixed default list regardless of query). The KB has exactly one product category, Linga POS, with nine sections. The KDS appears only as a configurable device type in Back Office > Settings > Hardware > Kitchen Printers (name, IP, Expo Device with Expo Printer IP and Queue Device IP, allowed Service Types, Print ToGo Items, category scoping) - that screen has no all-day or quantity-aggregation option. Neither the 17-entry POS section nor the 4-article hardware-and-networking section contains an article describing the KDS screen in operation, so whether a station can show outstanding quantities per item/modifier across open tickets is unresolved.

kitchen-sla-alerts

Cook-time monitoring plus color-coded status labels ("cooking, done, delayed"). Operator-configurable target times per station and audible alerting not documented. https://www.lingapos.com/solutions/kitchen-display-system-kds/ · retrieved 2026-08-01

kitchen-printer-fallback differentiator

The kitchen-printer leg is documented: after three failed connection checks the POS routes tickets to the Back Office-mapped Alternate Printer and alerts staff ("Unable to connect [Printer Name]. Hence the printing will be continued in [Alternate Printer Name]"). Shortfall: no documented failover path when a KDS screen goes offline (the KDS KB articles return HTTP 404), and no explicit no-ticket-loss guarantee. https://support.lingaros.com/portal/en/kb/articles/pos-operation-printer-hardware-settings · retrieved 2026-08-04

kitchen-offline-operation differentiator

POS: Offline Mode: 'All the printers are connected to local network through intranet. When this is in Offline mode, then you will be able to access all printers such as kitchen printers, receipt printers, KDS etc.' The same article confirms the cash drawer keeps working over IP and that what fails offline is the cloud side - 'Back Office to POS connection won't function (sync won't be available)', reporting, till, refunds. Linga configures the KDS as a kitchen-printer device addressed by IP on the store LAN, which is why it survives a cloud outage. https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-8-5-2025 · retrieved 2026-08-07

kitchen-item-build-screens differentiator

The Settings tab on Back Office > Settings > Hardware > Kitchen Printers 'applies to all kitchen printers' store-wide, and KDS is one of the four configurable device types on that same screen (Printer, KDS, Runner, Driver). Its options include 'Print Included Modifier In Kitchen' (so modifiers bundled into an item are broken out, not just chosen ones) and 'Serving Size in Front of Menu in KOT'. Shortfall: that is modifier and size text only - no recipe steps, no portioning or per-section build detail, and no documentation that a KDS station renders anything other than ticket lines. Linga publishes no KDS operating article, so the on-screen layout is unverified. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-kitchen-printer-hardware-settings · retrieved 2026-08-07

kitchen-pizza-fractional-display differentiator

Quote: "This update ensures clear segregation of Left and Right Halves with accurate topping and quantity representation, improving kitchen efficiency and order accuracy." Quote verified in linga/26-03-003-release-notes.txt. Read both notes in full against the claim (halves, quarters, specific sections rendered visually and unambiguously on the make-line screen or ticket). 26.03.003 documents the KDS explicitly, but only for Half & Half: 'clear segregation of Left and Right Halves'. 26.04.001's structured headers 'e.g., Left/Right Half, 1/3, 1/4 sections' are stated for 'POS, CDS App' - cashier/customer surfaces - with the KDS named only in the heading's parenthetical '(also Online Ordering in KDS and Custom App)', which reads as scope for online orders rather than a statement that thirds/quarters are rendered on the KDS. The kitchen ticket is documented only for the Half & Half item name (26.08.001: 'The Half & Half main menu name is now displayed correctly on the Kitchen Printer and KDS'), and the Cut and Modify article covers pricing (Slice Fraction / Modifier Price Percentage) with no display statement. Halves on the KDS are documented at B; quarters and arbitrary sections on the make-line or ticket are not. A differentiator yes needs the full claim; this is partial B. Analyst note: Release notes 26.03.003 (KDS) and 26.04.001 ('Modifier Grouping (also Online Ordering in KDS and Custom App) - Enhanced POS, CDS App with updated Cut & Modify modifier grouping, introducing structured headers (e.g., Left/Right Half, 1/3, 1/4 sections) for improved clarity and consistency across order displays') document that halves, thirds and quarters from Cut & Modify are rendered as segregated, headed sections on the KDS; 26.08.001 confirms 'The Half & Half main menu name is now displayed correctly on the Kitchen Printer and KDS'. Cut and Modify (Back Office) and POS: Modifiers define the fractional model (left/right/whole, Slice Fraction pricing). Rendering is sectioned text headers rather than a graphic wheel on the KDS, but the claim asks for visual-and-unambiguous, which grouped Left/Right/1/3/1/4 headers satisfy. https://support.lingaros.com/portal/en/kb/articles/26-03-003-release-notes · retrieved 2026-09-03 adversarially verified

kitchen-recall-refire

POS: Check Options - Resend to Kitchen: 'On the Menu screen, select the Option button at the bottom. On the Check Options screen, select Resend to Kitchen.' Item-level sending is separately documented - POS: Menu Options - Fire (Expedite) an Item: 'When a Menu Item is Fired, that selected Item will be sent to the Kitchen immediately' with a green check mark confirming it went. Shortfall: Resend to Kitchen operates on the check, not a single item, and no Linga documentation describes recalling or unbumping a ticket that has already been bumped on a KDS station - the portal publishes no KDS operating article. https://support.lingaros.com/portal/en/kb/articles/pos-resend-to-kitchen · retrieved 2026-08-07

kitchen-order-modification-alerts differentiator

KDS will "instantly reflect changes and modifications to any order." Visual flagging of specifically added/changed/removed lines not documented. https://www.lingapos.com/solutions/kitchen-display-system-kds/ · retrieved 2026-08-01

kitchen-guest-ready-notification differentiator

Quote: "Completed Order: QSR - If Enabled (YES) , a guest will receive an SMS text notification when their Quick Service Order ( QSR ) is completed." Completing an order on the KDS triggers a guest SMS, configurable per service type (QSR, Table Service, Online, Delivery, To Go, For Here, Bar Tab) with a templated message - the mechanism the claim asks for. Shortfall: it is gated on a separately purchased texting licence ('only available to users with an SMS texting license'; Octopus article: 'the Text add-on should be purchased and enabled in the account license settings'), which contradicts 'without a separate product purchase'. Linga also ships a Queue App status board synchronised to KDS Expo (26.07.001: 'real-time synchronization of order statuses with KDS EXPO and POS actions ... recalled orders will automatically move back to Preparing Orders'), but whether Queue App is included or a separate licence is not documented. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-kds-configuration-template-settings · retrieved 2026-09-03 adversarially verified

kitchen-waste-logging

Back Office: Inventory - Adjust Inventory documents adjusting stock with a reason, the reasons being 'created from the Adjust Inventory Reason screen' (a sibling article, Inventory > Adjust Inventory Reasons, defines the code list). Shortfall: navigation is explicitly 'Sign into the Back Office. On the left-side, select Inventory then Adjust Inventory' - the article describes no POS or kitchen/KDS entry point, so waste cannot be logged at the station where it happens; remakes are not a documented adjustment concept at all; and the article does not state the reason codes shipped by default. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-adjust-inventory · retrieved 2026-08-07

kitchen-speed-of-service-reporting

2026-09-03 re-sweep (195th): the full support.lingaros.com KB (605 articles) and www.lingapos.com were read; an analyst proposed partial from https://www.lingapos.com/solutions/kitchen-display-system-kds and the adversarial pass returned it to unknown: solutions__kitchen-display-system-kds.txt L54-58 verbatim 'Improve Cooking Time / ● Easy to Use Bump Bar / Manage and organize orders more efficiently. / ● Track Cooking Times / Track and improve the time required to prepare dishes.' The claim is a REPORT of ticket and per-station times (average and percentile) by daypart/station/channel with CSV/API export. 'Track ... the time required to prepare dishes' is satisfied by the on-screen elapsed timer the KB already documents (back-office-2024-kds-configuration-template-settings.txt: 'Time – The Time the Order was placed', 'After Mins' colour thresholds; 26-03-001 release notes: 'existing KDS behaviors such as bumping, timers, and completion tracking'), so the sentence does not establish any reporting half of the claim. KB grep (cook time, prep time report, ticket time, bump time, kitchen report, speed of service, KDS report, average time) yields no report; the only 'AVERAGE TIME' hit is an employee-dashboard permission in user-management-roles; the 25 Back Office report titles contain no kitchen-time report. Nearest hint: KDS settings 'KDS Done Button – If Enabled, KDS can't store item-based prep time', implying prep times are stored somewhere, but no article surfaces them. A marketing 'track' verb with zero documented report is too thin for partial; unknown. Prior rationale: Checked on support.lingaros.com: Back Office > Reports lists 25 report articles (Void, Transaction, Till, Tax, Sale, Revenue Center, Refund, Paid In/Out, Membership, Inventory, House Account, Gift Card, Fiscal/ZATCA, Feedback, Employee, Driver, Discounts, Exporting, Daily Tender, Daily Summary, Customer Preference, Comparison, Batch, Audit Log, Account Balance) - none is a kitchen, ticket-time or speed-of-service report. The Sale Reports article enumerates that screen's 13 tabs (Department, Category, Sub Category, Menu Item, Modifier, Hourly, Daily, Sale Recap, Cashier Out, Weekly Summary, Sale Summary, Future Order, Online Sales) and its filters (Time Period, Employee, Service Type, Floor/Table, Payment Type, Order Source such as Web Order/Mobile, Order Type Pick Up/Delivery) - the slices the claim wants exist as dimensions, but no elapsed-time measure does, and no percentile anywhere. Back Office > Settings > Reports holds only six configuration articles (tip out, sales recap, revenue center, payroll, additional, account balance). Left unknown rather than no because a section index is not an exhaustive enumeration and Linga's KDS has no documentation at all, so a station-side timing report cannot be ruled out. adversarially verified

kitchen-prep-forecasting

Checked Back Office: Inventory - Preparation on support.lingaros.com, the only prep screen in the 16-article Inventory section: a manager selects a Menu Item or Sub Recipe to prepare, picks 'Serving Size' and 'Quantity To Prepare' ('use the up/down arrows or manually enter the value'), and a Production Log tab records produced-inventory history. Quantities are keyed by hand - nothing derives them from historical sales or a demand forecast - and the screen is reached by signing into the Back Office, not surfaced to kitchen staff as a daily task list. Also checked the 25-article Reports section for a forecast report: none. Left unknown rather than no because Linga markets 'Predictive Trends' analytics on lingapos.com whose underlying screens are not documented in the portal, so a forecast-driven prep list elsewhere in the product cannot be excluded.

delivery-driver-roster

Drivers are first-class in Linga Driver with per-driver performance tracking (speed, punctuality, delivery count) and availability-based assignment. Driver clock-in/out and explicit in-store/on-run/returning state not documented. https://lingapos.com/solutions/linga-driver · retrieved 2026-08-01

delivery-dispatch-board

"Auto-assign orders based on availability and proximity" implies a dispatch surface, and orders sort nearest-to-furthest. A dedicated board showing undispatched orders with elapsed time, and explicit multi-order run batching, not documented. https://lingapos.com/solutions/linga-driver · retrieved 2026-08-01

delivery-route-map differentiator

Native delivery dispatch is a flagged flip-the-conclusion cell and this 'yes' rests entirely on a marketing page with no product documentation behind it. The verbatim text is 'orders are sorted by location from nearest to furthest' — that is list sequencing, not route optimization. 'Reduce travel time with optimal delivery paths' is a benefit claim with no mechanism. No turn-by-turn navigation, no map provider named, no multi-stop route solving, no screenshot or KB article. Confidence was also mislabeled 'documented' when the source is /solutions/linga-driver, a sales page carrying a 'See Pric https://lingapos.com/solutions/linga-driver · retrieved 2026-08-01 adversarially verified

delivery-driver-tracking differentiator

One marketing sentence on the same sales page, scored as 'documented'. There is no product doc, no KB article, no screenshot, and no statement of what the driver-side app is, what platform it runs on, how often position is reported, or whether the driver must keep an app foregrounded. 'Live GPS surfaced back to the operator' is the researcher's inference layered on 'monitor each driver in real-time'. Plausible and probably true, but claim-level — and the dossier leans on it to build an entire best_at bullet. https://lingapos.com/solutions/linga-driver · retrieved 2026-08-01 adversarially verified

delivery-zones-polygon differentiator

Back Office > Settings > Application > Delivery, Delivery Zones section: '+ Add Delivery Zone' takes a Name, Delivery Charge, Expected Delivery Time and a Zone Area with colour, then 'Select a form to draw the zone (Circle, Shape, Line, or Rectangle)'. Shape is a free-traced polygon - 'Select a starting point on the map ... keep tracing your desired zone until you want to return to the original point'; Circle is drawn by dragging a radius from a point; Rectangle by dragging a corner. So zones are arbitrary map polygons, not merely a radius or a ZIP list (the Name field merely suggests naming the zone after a neighbourhood or ZIP). Drive-time isochrones are not offered; each zone instead carries a fixed Expected Delivery Time. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-delivery-application-settings · retrieved 2026-08-07

delivery-zone-pricing

Delivery Zones are drawn on a map (circle, shape, line, rectangle) with a per-zone Delivery Charge and Expected Delivery Time in minutes. A per-zone order minimum is not documented, and the docs do not show the zone fee being applied automatically from a validated customer address. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-delivery-application-settings · retrieved 2026-08-03

delivery-address-validation

Quote: "Fixed a bug where Delivery Orders originating from outside the Delivery Zone were being accepted." The bug-fix line establishes that rejecting delivery orders whose address falls outside the configured Delivery Zone is intended, live behaviour of Linga's online ordering (the previous pass found no such statement). Zones are drawn on a map as Circle/Shape/Line/Rectangle with a radius in miles (back-office-2024-delivery-application-settings), so the address must be geocoded against the map to be matched, and the same article's 'Map API key' plus 'Google maps estimated time to drive to the address' (pos-phone-web-orders-out-tab) name the mapping service. Shortfall: the geocoding step and the customer-facing out-of-zone message are never described; the rejection is evidenced only by a bug-fix sentence, not a feature article, and address entry on staff phone orders is not documented as validated. Not yes because the mechanism is inferred from the map-zone construct rather than stated. https://support.lingaros.com/portal/en/kb/articles/may-27th-2025-release-notes · retrieved 2026-09-03 adversarially verified

delivery-driver-comp differentiator

POS: Phone / Web Orders - Driver Reporting: the driver's cashier report shows 'Delivery Charge, Driver Compensation and Store Compensation', and 'The amount of Driver compensation for delivery charges on orders they delivered is determined by the percentage set on the Delivery Charge Compensation to Driver setting'; 'Credit Card tips for Orders that the Driver was assigned to will show on this report'. The setting itself is in Back Office > Settings > Application > Delivery: 'Enter the Percentage (%) of the Delivery Charge that goes to the Driver'. The Back Office Driver Report adds per-check columns Name, Date, Time, Check #, Amount, Owed, Delivery Charge Cost, Driver Tip, Total. Shortfall: compensation is a percentage of the delivery charge only - no mileage or distance-per-run input exists anywhere in the delivery settings - and neither report documents an export to payroll, let alone one splitting reimbursement from wage lines. https://support.lingaros.com/portal/en/kb/articles/phone-web-orders-driver-reporting · retrieved 2026-08-07

delivery-cash-reconcile

Back Office: Driver Report is per driver, per check: Name, Date, Time, Check #, Amount, 'Owed - The total amount owed by the driver (no card payments)', Delivery Charge Cost, Driver Tip, and 'Total' summing Amount, Owed, Delivery Charge Cost and Driver Tip. On the POS side, Back Office > Settings > Application > Delivery has 'Select whether to generate a Cashier Report for the Driver', and POS: Phone / Web Orders - Cashier Report for Driver documents that with the toggle on 'the Sale will be assigned to the Driver' and checks appear under the driver's name rather than the cashier's. Shortfall: the flow produces the cash owed and tips per driver but no starting cash bank is issued to a driver and no over/short variance figure is computed or documented anywhere - reconciliation is the manager comparing the Owed total against cash handed back. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-driver-report · retrieved 2026-08-07

delivery-daas-dispatch

DoorDash Drive is a named integration in the Integration Hub. The detail page renders no description, so courier quote and status return into the order record is unverified. https://lingapos.com/integration-hub · retrieved 2026-08-01

delivery-daas-fallback differentiator

DoorDash Drive Integration: staff 'select the Order(s) request for DoorDash Driver' from the NEW tab and the order then walks the statuses Order Confirmed, Driver Confirmed, Driver Enroute To Pick Up, Driver Arriving at Store, Order picked up, Driver Enroute to drop off, Order Delivered. Both directions of the hybrid are documented - 'DoorDash Driver can be assigned only for online orders & not for direct store orders', and 'Cancelling a Driver will be possible until the minimum closet time ... After DoorDash driver cancellation, an internal driver can be confirmed'. Shortfall: every handoff is a manual tap (POS: Phone/Web Orders shows a 'Request Driver' button for DoorDash Drive), and no rule engine is documented that overflows an order to the courier network automatically when no in-house driver is available, the address is out of zone, or a wait threshold is passed. https://support.lingaros.com/portal/en/kb/articles/doordash-drive-integration · retrieved 2026-08-07

delivery-3p-direct-integration differentiator

Partial upheld, with a mischaracterization to fix. Neither named integration is a marketplace order-injection integration. DoorDash Drive is described as 'advanced logistics and a vast driver network' — delivery-as-a-service, not the DoorDash marketplace. The 'Uber Eats' tile is described as 'Commission-free delivery with a low flat fee using Uber's extensive network', which describes Uber Direct (DaaS), not Uber Eats marketplace. So Linga's hub contains two courier-network integrations and zero confirmed first-party marketplace injections; marketplace coverage runs entirely through Deliverect https://lingapos.com/integration-hub · retrieved 2026-08-01 adversarially verified

delivery-3p-injection

Deliverect is described as connecting delivery services to the POS, "integrating third-party food orders seamlessly." Middleware-mediated rather than demonstrably first-party auto-injection. https://lingapos.com/integration-hub · retrieved 2026-08-01

delivery-menu-push

Available via Deliverect/Chowly middleware. Channel-specific markups and single-master publishing from the POS menu not documented. https://lingapos.com/integration-hub · retrieved 2026-08-01

delivery-86-sync

Quote: "If the quantity of any item on the 86 List reaches zero ( 0 ), Redis will communicate to Deliverect that these items are out of stock (the PLU Code of each item will be snoozed)" Item-level out-of-stock is pushed automatically to third-party channels, but only through the Deliverect middleware partner (Nov 12 2024 release notes: 'Deliverect - 86 list snooze time for Menu item - Online Ordering'). The 86 List itself decrements in real time across POS terminals (26-05-001: 'When an item included in the 86 List is sold at any POS terminal, the available count is automatically decremented in real time across all POS terminals'). Shortfalls: (1) not native to the direct Uber Eats, Chowly, Urban Piper or DoorDash integrations - their articles and the Third Party Integrations settings page document only manual 'Publish Menu' pushes and no availability sync; (2) modifier-level 86 is not mentioned for Deliverect (only item PLUs are snoozed); (3) restore-on-availability is described only as a 'snooze time', not an un-snooze when stock is re-entered. https://support.lingaros.com/portal/en/kb/articles/deliverect-integration · retrieved 2026-09-03 adversarially verified

delivery-store-pause

Back Office > Settings > Integrations > Third Party Integrations Settings: Yemek Sepeti has 'Is Restaurant Open' - 'When enabled, the restaurant will be available for online ordering. When disabled, the restaurant will not be available for online ordering'; Urban Piper has a Store Action toggle - 'If Enabled (YES), the stores will be published in Urban Piper'; Chowly and Deliverect each have a Publish Store button after which 'the store will be available in Chowly'/'Deliverect'; DoorDash has only an 'Enable Doordash Drive' toggle and Uber Eats an 'Activate Integration' toggle. Shortfall: the controls live in the Back Office, not the POS; they are per-partner and absent for the two largest US marketplaces as a pause action (Uber Eats and DoorDash expose only integration enable/disable); and no timed auto-reactivation exists on any of them - each must be switched back on by hand. The POS Uber Eats article states outright that 'Store Cancellation is not available in Uber Eats' and 'Store will not be able to Deny Orders'. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-third-party-integrations-settings · retrieved 2026-08-07

delivery-3p-reconciliation differentiator

Checked support.lingaros.com Back Office > Reports (25 report articles: Void, Transaction, Till, Tax, Sale, Revenue Center, Refund, Paid In/Out, Membership, Inventory, House Account, Gift Card, Fiscal/ZATCA, Feedback, Employee, Driver, Discounts, Exporting, Daily Tender, Daily Summary, Customer Preference, Comparison, Batch, Audit Log, Account Balance) - no marketplace payout or commission report. The Sale Reports article enumerates that screen's 13 tabs including 'Online Sales' and a filter on Order Source (Web Order, Mobile), so 3P volume can be isolated, but no deposit, commission, marketing-fee or unpaid-order matching is described. Back Office > Settings > Reports > Additional Report Settings offers only a '3rd Party OLO Tax Summary' toggle that 'displays 3rd Party OLO Tax in Sale Recap Report'. Unresolved rather than no because Linga's Shogo and Restaurant365 integrations export sales to accounting systems where such reconciliation would occur, and their leaf articles do not describe what is exported.

delivery-injection-error-visibility differentiator

Quote: "Audit Log - Logs will be visible when logging into the BO and entering Integration Hub (Audit Log)" Linga does surface integration failures to the operator: named per-partner notifications when a menu push to Deliverect, Chowly or Uber Eats fails, an Integration Hub Audit Log that records failures (March 11 2025 notes: 'if an error occurs, it will be captured in the Audit Log as Publish menu-Menu items failed to sync with Deliverect' and 'Configuration update failed - Technical glitch'), and an Active/Inactive state per integration on the Current Integrations page (integration-hub-user-manual). Shortfall: every documented failure surface concerns menu publishing or credential configuration; no article or release note documents a log, notification or alert for a failed or rejected inbound ORDER injection, nor a live connection-health indicator per channel beyond the Active/Inactive toggle. The only order-side failure message is DoorDash Drive's synchronous 'related Error message will appear in ZenPepper' on an invalid dispatch request. https://support.lingaros.com/portal/en/kb/articles/february-11th-2025-release-notes · retrieved 2026-09-03 adversarially verified

delivery-tracking-page

"Send automatic texts to customers when orders are out for delivery" and "Customers can view estimated arrival time." Whether the tracking page is branded on the restaurant's own domain is not documented. https://lingapos.com/solutions/linga-driver · retrieved 2026-08-01

delivery-promise-time differentiator

Back Office > Online Ordering > Stores > Throttling, Order & Crew Based tab - 'Establish the settings for Crew and Delivery': Crew takes 'Order Per Crew', 'Base Quote Time - Enter the minimum amount of time (in minutes) for an order to be prepared', 'Maximum Orders Per Crew' and 'Additional Wait Time'; Delivery takes 'Deliveries Per Driver', 'Base Quote Time - Enter the minimum amount of time for an order to be delivered', 'Maximum Orders Per Driver' and 'Additional Wait Time'. So the quote moves with current kitchen load and driver load rather than being one per-store constant, and a Time Based tab adds per-day-of-week Maximum Orders and Additional Wait Time. Shortfall: adjustment is stepwise off manually configured thresholds, not a live model; and drive time never enters it - each delivery zone carries a static 'Expected Delivery Time' set when the zone is drawn (Settings > Application > Delivery), with no traffic or distance input. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-online-ordering-stores · retrieved 2026-08-07

delivery-offline-behavior

POS: Offline Mode states what survives an outage - 'All the printers are connected to local network through intranet. When this is in Offline mode, then you will be able to access all printers such as kitchen printers, receipt printers, KDS etc.', 'Cash Drawer will continue to function since it's connected on IP (through Intranet)', clock in/out stored locally, cash payments normal, card payments only if the 'Allow Offline Payment' toggle is on (with 'When in Offline Mode, do not accept Debit Card payment ... more likely to be Declined') - and what does not: 'Back Office to POS connection won't function (sync won't be available)', reporting, audits, till, 'Refund will not apply', 'Memberships, Customers and House account can't be created'. Three sibling articles cover Allow/Restrict Offline Payment and the Process Offline alert. Shortfall: cash tender offline is answered, but the article never addresses delivery specifically - not whether a delivery order can be taken and zoned offline, not whether a driver can be assigned or reassigned (both are POS actions that read the Active Driver panel), and not whether the driver cashier report or settle-up can be run offline; since Reports and Till are listed as unavailable, driver settlement is implicitly blocked but never stated. https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-8-5-2025 · retrieved 2026-08-07

digital-first-party-web

"Your Own Branded Online Ordering for Customers" with a custom website, POS-integrated. Commission terms not published, so the commission-free element is inferred from it being a first-party channel. https://www.lingapos.com/solutions/online-ordering/ · retrieved 2026-08-01

digital-menu-single-source

"Simplified Online Menu Synchronization" with guided upload/test/manage; kiosk menus and pricing "update instantly." Whether it is literally the same POS menu record versus a synced copy is not stated. https://www.lingapos.com/solutions/online-ordering/ · retrieved 2026-08-01

digital-native-app differentiator

Marketing-page claim with no verification path. No named example app, no App Store or Google Play developer listing, no statement of whether the app is published under the restaurant's own developer account or as a white-label shell, no submission/review handling, and no fee. The dossier's own note concedes store publication under the restaurant's brand is not stated — that concession is inconsistent with scoring 'yes'. https://www.lingapos.com/solutions/online-ordering/ · retrieved 2026-08-01 adversarially verified

digital-account-saved-payment

Quote: "This release also enhances the customer payment experience by introducing saved card management, Edit/Add New Card options, and an updated payment screen layout" Guest accounts and tokenised saved cards on first-party channels are documented: OLO Account settings offer 'Enable Sign Up with Facebook', 'Enable Sign Up with Google' and 'Allow Guest Checkout ... without creating an Account' (back-office-2024-online-ordering-account); the OLO card screen has 'a checkbox option to Save the card for faster check out' (pos-partial-payments-in-online-ordering-olo); 26-02-001 documents 'Tokenization Card Details Deletion in Online Ordering/Call Center/VRT: Saved credit card details can now be deleted from the Online Ordering. When a card is deleted, it is automatically removed across all related channels, including POS, OLO, VRT, Call Center, and the payment gateway' and the same for the OLO Custom App. Shortfalls: saved delivery addresses on the guest account are never documented (the customer record holds one mailing address, back-office-2024-customers-customer-info), and one-tap reorder is documented only staff-side ('Select an Order from the Customer's list of Previous Order and select Repeat Order', pos-customer-profile-screen); OLO has an 'Order History screen' (26-07-001) but no guest-side reorder action. https://support.lingaros.com/portal/en/kb/articles/26-06-001-release-notes · retrieved 2026-09-03 adversarially verified

digital-upsell-engine differentiator

No suggested-item, related-item or upsell field appears on the Back Office Add/Edit Product form, the Kiosk Addon settings or the Online Ordering Stores settings as documented at support.lingaros.com, and no attach-rate report appears among the 25 report families in the Reports section index. But none of those articles asserts its own completeness - a re-extraction of the Add/Edit Product article surfaced seven fields an earlier read of the same page had dropped, so it cannot be treated as an exhaustive field reference - and a KB section index is a suite listing, not an enumeration. Against that, Linga's own retail page (lingapos.com/retail/electronics) claims "Point of sale prompts making staff and customers aware of upsell options like chargers, cases, or add-ons with core items", so the vendor asserts some prompting capability exists. Unresolved: an upsell prompt could be a kiosk/CDS-side behaviour with no back-office toggle, and no article describes the kiosk ordering screen in operation. adversarially verified

digital-scheduled-pacing

Order Settings document "Enable Future Order - If Enabled, set the Limit on the amount of Time (Days and Hours) in advance an Online Order can be placed", plus throttling: "Maximum Orders - Enter the maximum number of orders allowed for the service per day" and "Time Period - Enter the designated timeframe (in minutes) during which the throttling rules (Maximum Orders) are actively applied", with Delivery/Pickup Preparation Time fields and a General Application Settings option to "Display Dynamic Preparation Time". Shortfall: the throttle is a per-service order-rate cap, not per-daypart capacity per booked time slot, the docs do not describe item-level slot capacity, and no text states that a saturated slot is automatically removed from the guest's pickup-time picker. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-online-ordering-stores · retrieved 2026-08-07

digital-fulfillment-modes

Pickup and delivery with configurable delivery zones and ordering hours, plus QR Pay. Curbside arrival check-in and mode-specific fee/prep-timing configuration not documented. https://www.lingapos.com/solutions/online-ordering/ · retrieved 2026-08-01

digital-qr-table

"QR Pay" contactless documented — scan-to-pay. Scan-to-order attaching to an existing POS check, with splitting and tipping, not documented. https://www.lingapos.com/solutions/online-ordering/ · retrieved 2026-08-01

digital-kiosk differentiator

First-party kiosk with customizable items/pricing/modifiers, real-time sync, and integrated payment accepting tap/chip/swipe/gift/digital wallets. Accessibility-compliant UI not documented. https://lingapos.com/solutions/kiosk · retrieved 2026-08-01

digital-group-ordering

Checked 2026-08-07: the Online Ordering Stores settings article on support.lingaros.com (which enumerates the OLO merchant configuration - ordering hours, order types, checkout, payments, notifications, throttling, delivery zones) has no shareable-link ordering, per-person or total spend cap, or multi-participant cart; www.lingapos.com/online-ordering names only delivery zones, order types, menu builder, CRM, reports and kitchen printing. The vendor's only group-related documented feature is POS-side split/merge of checks. A guest-facing group-order link would not necessarily appear in a merchant settings screen, so absence here is not positive evidence of absence.

digital-catering-portal differentiator

Checked 2026-08-07 on support.lingaros.com: the Online Ordering Stores settings article documents a single ordering flow (delivery / pickup / curbside / ASAP / Future Order with a days-and-hours advance limit, delivery minimum spend, delivery zones) with no separate catering menu, catering minimum, quote or proposal step, or deposit. House Account exists as a back-office credit construct (back-office-2024-customers-house-account and the House Account Report) but no article links it to a catering ordering flow or to ACH/invoice terms on a digital order. Sections walked: back-office/online-ordering, back-office/enterprise, back-office/customers, pos/phone-web-orders. No page affirms or denies a catering portal.

digital-voice-ai-phone differentiator

Checked 2026-08-07: the POS > Phone / Web Orders section on support.lingaros.com lists 13 articles (Overview, New/Future/Out/Complete tabs, Delivery Charge, Driver Tracking, Reassign Driver, Driver Reporting, Cashier Report for Driver, Print Before Future Order, DoorDash Delivery for OLO Custom App, Third Party Integration Differences) and describes staff-keyed phone orders only. The POS > Third Party Integration section names exactly five partners (Uber Eats, Servme, DoorDash Drive, Deliverect, Chowly) - none is a voice-AI answering service. www.lingapos.com/online-ordering names no AI voice product. A partner directory is not an exhaustive enumeration, so this stays unresolved rather than a no.

digital-drivethru-ai

Checked 2026-08-07: the POS section index on support.lingaros.com lists 17 entries (sign-in, log-in, pos, check options, menu options, payments, check status, table layout, bar tab, phone/web orders, wait list, payment surcharge, operation, third-party integration, initial screen, offline mode, seat order override) with no drive-thru lane screen or timer, and the five documented third-party integrations are marketplace/delivery and reservation partners. No AI voice lane ordering, POS menu/modifier grounding, or escalation-to-human handoff is documented on support.lingaros.com or www.lingapos.com; nothing denies it either.

digital-sms-ordering

Checked 2026-08-07: the Online Ordering Stores settings article on support.lingaros.com documents SMS strictly as outbound notification (pending / confirmed / cancelled order alerts) alongside new-order email alerts; the Marketing > Campaigns article documents campaign sends by channel with Email as the demonstrated example. No article in back-office/online-ordering, back-office/marketing or pos/phone-web-orders describes an inbound conversational text-to-order or text-a-link ordering flow landing in the POS. Absence from the notification and campaign settings is not positive evidence about an unbuilt inbound channel.

digital-google-order differentiator

Checked 2026-08-07: the Online Ordering Stores settings article on support.lingaros.com has a Social Links block covering Facebook, Twitter/X, Instagram, TripAdvisor and Yelp and no Google Business Profile field or Order with Google provisioning; Google appears in Linga documentation only as a payment method (Google Pay). A targeted search for Linga plus Order with Google / Google Business Profile returned only Google's own support pages and Linga marketing pages, no Linga documentation. Ordering-link placement on GBP can be done by the operator outside the POS, so silence here is not evidence of absence.

digital-apple-business-connect

Checked 2026-08-07: no mention of Apple Business Connect or an Apple Maps "Order Food" custom action in the Online Ordering Stores settings article (whose Social Links block covers Facebook, Twitter/X, Instagram, TripAdvisor and Yelp only), anywhere in the back-office/online-ordering or back-office/enterprise sections of support.lingaros.com, or on www.lingapos.com/online-ordering. Apple appears in Linga material only as Apple Pay. The vendor publishes nothing on map-listing ordering placement either way.

digital-loyalty-attach

The literal wording is 'Customer Loyalty Integration', which signals an integration point rather than demonstrated accrual and redemption inside the online checkout flow. Nothing documents that a guest can apply points or a reward at web checkout, that accrual happens on digital orders, or that the digital identity resolves to the same loyalty profile as in-store. Scoring 'yes' from the word 'Integration' is reading marketing copy as capability. https://www.lingapos.com/solutions/online-ordering/ · retrieved 2026-08-01 adversarially verified

digital-subscriptions

Membership plans carry an "Allowance Period" (Monthly/Quarterly/Half-Yearly/Yearly) and an "Allowance" amount with auto-computed Balance Amount and Expiry Date, and Membership Reports track per-period allowance use — a platform-managed paid membership with a per-period entitlement. Automatic recurring card billing/collection is not documented, and delivery-fee-waiver or paid-loyalty-tier constructs are not shown. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-customers-membership · retrieved 2026-08-03

digital-promo-parity

Discounts are defined once in Back Office > Products/Items; the Check-Based Discount form carries Priority, Quantity to unlock, tax basis, Discount Type (Promo/Comp/Donation), Employee Discount, "Coupon Only" with a unique alphanumeric code, Auto Discount, Combine With Other Discounts, Customer Attachment Required, Membership Plan, category/item exclusions, availability by day/date/time and role-based visibility. Online Ordering picks these up through "Enable Coupon Code - If Enabled, the promo/coupon code field will be available during Online Ordering checkout" in the OLO store settings. Shortfall: the discount form has no per-channel or order-type eligibility control (channel visibility exists only at item level - Hide in Kiosk / Hide in POS / Hide in Online Order on the product form), and no article states that loyalty offers redeem identically at the kiosk, where loyalty appears only as a tender type. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-discounts-check-based · retrieved 2026-08-07

digital-guest-data-ownership differentiator

The Customers article documents a self-serve bulk export: "At the top-right of the main Customers page, click Export. The Export pane appears.", against a customer record holding first/last name, phone number, email address, gender, date of birth, nationality, anniversary, customer ID, notes, address and loyalty balance - so an operator can pull first-party guest records with contact PII without a support ticket, and the Exporting Reports article documents XLSX/CSV/PDF output with Direct Download or Send by Email. Shortfall: no Linga document asserts operator ownership of guest data or that export is free of vendor fee or approval; consented marketing status is not a field on the customer record at all; and order history is not part of this export (it lives in separate reports such as Customer Preference Report). https://support.lingaros.com/portal/en/kb/articles/back-office-2024-customers-customer-info · retrieved 2026-08-07

digital-checkout-pci-sca

Quote: "When the toggle is set to Yes, the NMI iFrame payment screen will be displayed for payment processing, along with 3D Secure authentication if 3D Secure is enabled for the account; when the toggle is set to No, the existing payment flow will be retained." A gateway-hosted iframe (NMI) for OLO card capture and optional 3-D Secure are now documented (June 2026 release), which the previous pass had not found. Shortfalls: (1) the iframe is a Super-Admin toggle and 'when the toggle is set to No, the existing payment flow will be retained', so hosted capture is not the guaranteed default; (2) 3DS is 'optional' and tied to the NMI account, and the OTP-by-email/phone description reads as gateway-side step-up rather than EMV 3DS; (3) no PCI DSS 4.0 attestation, script-integrity (6.4.3 / 11.6.1) statement or security page exists in the KB, and lingapos.com legal pages were 301 stubs today so the marketing '100% PCI Compliant' line could not be re-read. Tokenisation of stored cards is separately documented (back-office-2024-store-payment-settings 'Tokenize the Credit Card'). https://support.lingaros.com/portal/en/kb/articles/26-06-001-release-notes · retrieved 2026-09-03 adversarially verified

digital-surcharge-transparency differentiator

Dual Price is configured once in Back Office > Settings > Payments > Payment Settings (Payment Surcharge toggle, name, percentage to 3dp, Before/After Tax) and the article documents it rendering across channels: on the iPad POS "Dual Price will work like Open discount but will appear on the Order Summary screen", and for Online Ordering and Call Center "The Dual Price will be calculated based on the Percentage set in BO, and will appear after Total as Pay with Cash". Guest-facing disclosure is documented on receipts as a line item, on the Customer Display Screen to "inform the Customers in advance about the Cash Price", and at online checkout. Shortfall: the article addresses no jurisdiction where surcharging is prohibited and no card-brand restrictions; Dual Price "applies only to Cash payments"; and the separate card-Surcharge and Service Charge articles are written against the POS and do not state that those configurations reach first-party online ordering. https://support.lingaros.com/portal/en/kb/articles/pos-payment-surcharge-dual-price · retrieved 2026-08-07

guest-loyalty-unified-profile

"Loyalty activity is tracked from anywhere the customer is active and their history can be tracked from any device." No documented dedup/merge behavior or match key. https://lingapos.com/solutions/customer-loyalty-programs · retrieved 2026-08-01

guest-loyalty-thirdparty-identity-attach differentiator

Uber Eats orders transmit usable guest identity into the POS: the article states "The customer details appear in the top left section: address, phone number, email address" alongside the Uber account name, order type UBEREATSDELIVERY, time placed and check total - so marketplace tickets do not land anonymous. Shortfall: no Linga article states that this identity is written to, or matched against, a native customer record in Back Office > Customers; the Customer Info article documents no marketplace-sourced records, and the Phone/Web Orders "Third Party Integration Differences" article covers only the extra Ready and Request Driver buttons, not customer-data handling. Guest identity is visible on the check but native profile attachment is undocumented. https://support.lingaros.com/portal/en/kb/articles/pos-uber-eats-integration · retrieved 2026-08-07

guest-loyalty-accrual-models

Points/rewards issuing discounts or free items based on tracked behavior. Only one accrual model clearly documented; visit/punch and spend-tier are not. https://lingapos.com/solutions/customer-loyalty-programs · retrieved 2026-08-01

guest-loyalty-tiers differentiator

Marketing > Settings configures automatic rolling-window classification of loyalty members: "New - Customers who have signed up as Members of your loyalty program within the last entered number of Days", "Recurring - Members who have ordered from your store within the last entered number of Days", "At Risk - Members who haven't visited your business within the last entered number of Days", and "VIP - Recurring customers with one or more Life Days" (Life Points being the total accumulation of earned Loyalty points). These classes are selectable as campaign audiences (All Members, New, Recurring, At Risk, Inactive, Bounced, VIP). Shortfall: they are marketing segments for targeting, not status tiers - no tier-specific earn rate, discount or benefit is attached to them. The construct that does confer benefits, Customers > Membership (Type / Plan / Account with price level, allowance and allowance period), is assigned manually per customer and the article documents no automatic advancement on spend or visit frequency. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-marketing-settings · retrieved 2026-08-07

guest-loyalty-offline-behavior differentiator

The Offline Mode KB states "Memberships, Customers and House account can't be created" while offline — new-member enrollment is documented as blocked during an outage. Shortfall: the article does not state what happens to lookup, accrual, or redemption for an EXISTING loyalty member while offline (queue-and-reconcile vs blocked), which is the more operationally important half of the claim; the customer-loyalty-programs product page itself is silent on offline behavior entirely. [Citation repaired 2026-08-09: the cited article 404s and this evidence now rests on pos-offline-mode-8-5-2025, the successor, where the quotation above was re-verified verbatim.] https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-8-5-2025 · retrieved 2026-08-09

guest-loyalty-offer-stacking-rules differentiator

The Check-Based Discount configuration form carries a "Priority" field (order of application, typically set to 1) and a "Combine With Other Discounts" Yes/No toggle - explicit precedence and exclusive-vs-combinable configuration - together with "Auto Discount" (automatic application), "Coupon Only" with a unique alphanumeric code, "Customer Attachment Required", Membership Plan gating, category and menu-item exclusions, availability windows and role-based visibility. The same discount builder is documented across the five discount types (Check-Based, Item-Based, Open Check, Open Item, Mix-and-Match) under Back Office > Products/Items. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-discounts-check-based · retrieved 2026-08-07

guest-loyalty-targeted-offers differentiator

"Drive repeat purchases by offering personalized incentives" with behavior-based targeting. No documented audience rule builder over recency/frequency/spend/items. https://lingapos.com/solutions/customer-loyalty-programs · retrieved 2026-08-01

guest-loyalty-rfm-segmentation differentiator

Marketing > Customers offers a member-type dropdown of "All Members (default), New, Recurring, At Risk, Inactive, Bounced or VIP" as ready-made lifecycle segments, and Marketing > Settings defines them by recency and value thresholds the operator enters once in days: New = signed up within the last N days, Recurring = ordered within the last N days, At Risk = has not visited within the last N days, VIP = recurring customers with one or more Life Points (total accumulated loyalty points). Segments can be saved as a Static or Dynamic list ("Dynamic - updates automatically per data changes") and targeted directly from Marketing > Campaigns, which lists "All Members, New, Recurring, At Risk, etc." as selectable audiences. The operator sets thresholds but builds no queries. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-marketing-customers · retrieved 2026-08-07

guest-loyalty-lifecycle-automation

"Automatically issues alerts and rewards after sign-up" — a single post-enrollment trigger. Birthday, first-visit and lapsed win-back automations not documented. https://lingapos.com/solutions/customer-loyalty-programs · retrieved 2026-08-01

guest-loyalty-native-email-sms differentiator

SMS Notifications and Marketing Campaigns exist as named solutions. Native email campaign sending is not confirmed. https://lingapos.com/solutions/customer-loyalty-programs · retrieved 2026-08-01

guest-loyalty-consent-management

Quote: "Enter the Message to request the Customer’s Email Address to confirm joining." A documented per-channel opt-in capture exists for SMS loyalty enrolment: an invite text, a confirmation step ('request the Customer's Email Address to confirm joining') and a thank-you message, gated by the account flag 'Enable SMS Loyalty Confirmation ... The new option Twilio Number will appear' (retail-back-office-admin-accounts). A blunt account-wide 'Disable Marketing' flag also exists there. Shortfalls, which are most of the claim: no consent timestamp or source-of-consent field appears on the Customer Info form or the Marketing Customers table; email marketing campaigns have no documented opt-in or unsubscribe handling; and no article describes honouring revocation by any means (STOP keyword or otherwise) across channels. Weak partial - the parent may prefer unknown if an enrolment confirmation is judged not to be consent management. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-enterprise-settings-addons · retrieved 2026-09-03 adversarially verified

guest-loyalty-10dlc-registration

Checked 2026-08-07 on support.lingaros.com: the Online Ordering Stores settings article configures outbound SMS notifications (pending, confirmed, cancelled) and the Marketing > Campaigns article configures campaign sends by channel, but neither mentions A2P 10DLC, brand or campaign registration, a sending number, or carrier vetting. The portal does publish a sender-reputation article for the email side ("DNS Records for Domain Authentication (SendGrid)"), which shows the vendor documents deliverability setup where it exists - but no equivalent exists for SMS. Onboarding paperwork of this kind is often handled off-portal by the reseller, so silence is not positive evidence that registration is unhandled.

guest-loyalty-campaign-attribution differentiator

Quote: "ROI Dashboard Measure how much each campaign brings in" The marketing-module feature page claims per-campaign redemption tracking, an 'ROI Dashboard' measuring what each campaign brings in, and 'sales uplift from each communication' - i.e. exactly the claim. Shortfall: this is a grade-C feature page; the only KB documentation (Marketing > Manage List) exposes 'Customers Targeted' and 'Sent Targeted' counts and the Discounts Report has no campaign dimension, so no help-centre article describes how redemptions are tied to check totals or where the ROI dashboard lives. Differentiator weight with C evidence -> partial, not yes. https://www.lingapos.com/solutions/marketing · retrieved 2026-09-03 adversarially verified

guest-loyalty-data-export-portability differentiator

Self-serve export exists and needs no support ticket: Customers > Customer Info documents "At the top-right of the main Customers page, click Export. The Export pane appears." over records holding first/last name, phone, email, DOB, anniversary, address and loyalty balance, and the Exporting Reports article documents output as "XLSX (excel file), CSV ... or PDF" with a choice of "Direct Download" or "Send by Email". Shortfall: the guest export is the customer list, not transaction history - per-guest ordering activity lives in a separate Customer Preference Report and the article does not state that it exports with contact PII attached; the exported column set is not documented; and no guest-data export endpoint is documented for the API. Whether any fee attaches is not addressed. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-exporting-reports · retrieved 2026-08-07

guest-loyalty-review-capture-routing differentiator

The Feedback App addon configures a scored first question (message up to 160 characters, up to four emoji answer options such as Love It, Very Good, It can be Better, each max 60 characters) and a conditional second question with "Secondary Question Triggers" - selecting which Question 1 answers activate it - plus "Capture User Information" checkboxes to collect customer data. That is genuine response-conditional branching, so a low scorer can be routed to a follow-up and to contact capture for private recovery, and results land in the Back Office Feedback Report. Shortfall: this is the complete configurable surface of the module and it contains no routing of high scores to Google, Yelp or any public review site, no review-site links, and no post-transaction send mechanism (email or SMS request) - the prompt is an in-store app, and the article does not document what triggers it. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-feedback-app-addon-settings · retrieved 2026-08-07

guest-loyalty-referral-program

2026-09-03 re-sweep (195th): the full support.lingaros.com KB (605 articles, 48 release-notes issues through 26-08-003) and www.lingapos.com were read; an analyst proposed no from https://support.lingaros.com/portal/en/kb/articles/back-office-2024-enterprise-settings-addons and the adversarial pass returned it to unknown: back-office-2024-enterprise-settings-addons.txt line 1 matches; 'Enter your Accumulation settings for Points Earned' followed by At Sign Up / For Each Visit / Cash vs Non-Cash / Menu Item Based / Category is verbatim. It is a settings walkthrough of the points-earning fields, not a list presented as THE ways a guest can be rewarded; a referral reward could be issued as a coupon or discount rather than as points, so the list does not close the claim's space (per-guest code, first-order attribution, two-sided reward). Grep for referr/refer a friend/invite/friend/share link across 606 KB files: only 'Enter the Message to Invite a Customer to join the Loyalty Program' (SMS opt-in, not referral). lingapos-com/solutions__customer-loyalty-programs.txt: 'Give regulars a reason to promote your business to friends.' - marketing aspiration, no mechanic; does not support partial. No non-support sentence, no closed enumeration -> unknown. Prior rationale: Checked 2026-08-07 on support.lingaros.com: the Check-Based Discount form's only code construct is "Coupon Only" with a single unique alphanumeric code per discount - not per-guest referral codes - and offers no referrer field or two-sided reward. The Customers > Customer Info form has no referral or referred-by field; Customers > Membership covers Type/Plan/Account only; the Marketing module (Settings, Customers, Manage List, Campaigns) has no referral mechanic. The article the search index returns as "Loyalty and House Account" 404s on support.lingaros.com, and there is no loyalty section under back-office/settings (addons holds only Scale Barcode, Kiosk, Feedback App and CDS), so the loyalty program's own configuration screen could not be located - referral rules could live there. adversarially verified

guest-loyalty-wallet-pass differentiator

Checked 2026-08-07 on support.lingaros.com: no Apple Wallet or Google Wallet pass, .pkpass, or push-updatable balance appears in Customers > Customer Info (which carries the loyalty enrollment flag and balance), Customers > Membership (Card Number, max 25 characters alphanumeric - a keyed card, not a wallet pass), the Kiosk Addon settings (loyalty appears only as a tender type), or the Online Ordering Stores settings. Linga does document a "MOBILE OLO APP" / custom app path, which is the branded-app alternative the claim contrasts with. The loyalty program's own configuration article was not locatable - back-office/settings/addons holds only Scale Barcode, Kiosk, Feedback App and CDS, and the indexed loyalty-and-house-account slug 404s - so wallet issuance is unresolved rather than absent.

guest-loyalty-privacy-rights-tooling

The Customers page provides the two admin actions a rights request needs: an Export control ("At the top-right of the main Customers page, click Export") covering the record's contact PII, and a per-customer delete from the row menu - "Click the corresponding ... of a Customer, then click Delete" (the three-dot menu also offers Edit Customer, View Customer Metrics and Edit Loyalty Points). Shortfall: the delete is documented as a soft action - the system confirms "Customer inactivated successfully", i.e. inactivation rather than erasure - and no article describes propagation of the deletion to loyalty balances, membership accounts, marketing lists or campaign audiences, no retention or purge policy is published, and there is no request-tracking or CCPA/CPRA-specific workflow. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-customers-customer-info · retrieved 2026-08-07

guest-loyalty-redemption-fraud-controls

The audit half of the claim is met: manual loyalty adjustment is a discrete action ("Edit Loyalty Points" on the customer row menu) against a Loyalty block carrying enrollment status, Loyalty Balance and a "Reason" field for updates, and the Audit Log Report captures back-office changes with Action, Event Date & Time, Employee ("The employee's name"), Device Type and a Log column giving "which field the update has been made to" with Field Name, Old Value and New Value; the POS view adds Check No, Device Name and Node. Shortfall: no redemption velocity or frequency limit is configurable anywhere (loyalty appears in the Kiosk addon only as an accepted tender), no manager-approval gate on point adjustment is documented - the only documented approval threshold in General Application Settings is Tip Threshold - and no employee self-redemption detection or flag exists. The Audit Log article also does not enumerate its event list, so loyalty adjustment is not confirmed by name as a logged event type. https://support.lingaros.com/portal/en/kb/articles/back-office-audit-log-reports · retrieved 2026-08-07

guest-loyalty-ai-offer-recommendation differentiator

The Marketing > Campaigns builder ships in-product suggestion helpers for offer content: "Get Suggestion: For Smart Headings, click Try It Now to get heading suggestions" and "Get Suggestion - For Magic Image, click Try It Now to get image suggestions". These are documented in the admin guide as live controls, not roadmap. Shortfall: the suggestions cover creative only - no AI/ML recommendation of target audience (audiences are picked from the fixed New/Recurring/At Risk/VIP classes or from filters on loyalty points, anniversary and date of birth) and no send-time optimisation; and the article never states that the suggestion engine is AI or ML rather than a template library, so the mechanism behind Smart Headings and Magic Image is inferred from the naming, not documented. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-marketing-campaigns · retrieved 2026-08-07

guest-loyalty-stored-value-gift

Native gift cards plus the Factor4 gift-card integration; franchise page markets customizable gift cards across locations. Binding of balance to the same guest loyalty profile not documented. https://lingapos.com/integration-hub · retrieved 2026-08-01

labor-clock-in-at-pos

Franchise page documents a "Staff Time Clock" tracking work hours by user and location; Schedules markets time and attendance from anywhere. PIN/badge punch at the POS terminal specifically not documented. https://lingapos.com/restaurant/franchise · retrieved 2026-08-01

labor-photo-punch-verification differentiator

Back Office > Settings > Application > General documents "Log In/Clock In Via - Enables PIN and/or Face ID authentication", so facial verification at clock-in is a real configurable feature rather than an inference. Shortfall: the setting is an authentication gate - no article states that a photo is captured and attached to the timecard entry for later review, the Employee Report > Attendance columns (Date, Name, Employee ID, Check In, Check Out, Total UnPaid Break, Hours, Job Code, Total) carry no image, and there is no photo-only mode documented as an alternative that stores no biometric template. Face ID implies a stored biometric template; the docs publish no retention or consent handling for it. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-general-application-settings · retrieved 2026-08-07

labor-offline-time-punch differentiator

The Offline Mode KB directly documents the behavior: "Application should allow to perform Clock-in/out or Break in/out and it will stored locally. Once an internet connection is re-established, then it will be posted to Back Office." Local storage and post-reconnect sync are confirmed, breaks included. Shortfall: no statement addresses duplicate-entry prevention or loss prevention specifically (e.g. what happens if the device is replaced or the app is reinstalled before reconnecting), which is the half of the claim that asks for reconciliation "without loss or duplicate entries". [Citation repaired 2026-08-09: the cited article 404s and this evidence now rests on pos-offline-mode-8-5-2025, the successor, where the quotation above was re-verified verbatim.] https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-8-5-2025 · retrieved 2026-08-09

labor-granular-rbac

"Set Groups & Management Levels" assigning roles and permissions across the franchise hierarchy, plus user role management exposed via API. Per-discrete-action grants (void, comp, price change, report access) not enumerated. https://lingapos.com/restaurant/franchise · retrieved 2026-08-01

labor-manager-override-audit

A queryable after-the-fact trail exists: the Audit Log Report is filterable by source, with Back Office rows carrying Action, Event Date & Time, Employee, Device Type and a Log column of Field Name / Old Value / New Value, and POS rows adding Check No, Device Name and Node; the article states the report shows "The employee's name" and "which field the update has been made to". Manager-gated actions exist (User Management > Roles names Discount, Transfer and Void as manager-access items; General Application Settings adds a Tip Threshold that "triggers manager approval for excessive tips"). Shortfall: the article does not enumerate its event types, so it is not established that a manager override or approval is itself a logged event; nothing states the log records the approving manager distinct from the employee operating the terminal; and no immutability, tamper-evidence or retention guarantee is published. https://support.lingaros.com/portal/en/kb/articles/back-office-audit-log-reports · retrieved 2026-08-07

labor-native-scheduling differentiator

Back Office KB: Scheduler > Scheduler gives a Week/Month grid of every store employee; hovering a date opens a New Shift pane with Role, Start/Finish Time (may be configured past 12am), unpaid Meal and Rest Break minutes deducted from Total Paid, Save for All (rest of week) and Save as Template. "the changes will be reflected only when the option Publish & Notify is clicked. Otherwise any new or updated Shifts will be treated as unpublished"; published shifts notify employees by SMS. Hours and Payroll totals per employee, per day and per week are computed from the employee's wage/salary in the same Back Office. Scheduler is a paid add-on (Upgrade > Employee Scheduling). https://support.lingaros.com/portal/en/kb/articles/back-office-2024-scheduler · retrieved 2026-08-06

labor-demand-labor-forecast differentiator

Insights markets "Predictive Trends" covering staffing forecasts. Whether it emits recommended hours by daypart from the operator's own history is not documented. https://lingapos.com/solutions/insights · retrieved 2026-08-01

labor-realtime-labor-percent differentiator

Labor cost as a percentage of sales is computed and reported: the Employee Report's Labor sub-report shows "employee net sales vs labor" with columns Name, Employee ID, Net sales, Hours, Labor Amount, % of Net Sales, Labor Percentage, Shift Status and Summary, and publishes the formula "Labor Percentage: Formula = (Labor of each employee / Net Sales of all Employees) * 100". Shortfall: this is a Back Office report driven by a process-type filter (Daily / Weekly / Daily-Weekly); no article places the figure on a POS screen or a live manager dashboard during service, and nothing states the figure refreshes intra-shift. The vendor's "Live Staff Metrics" marketing language covers clock-ins and productivity, not a live labor percentage. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-employee-report · retrieved 2026-08-07

labor-overtime-prevention differentiator

Checked 2026-08-07 on support.lingaros.com: overtime thresholds are configurable in Store Scheduler Settings as "Hours per day" and "Hours per week", each enable/disable with a pay-rate multiplier, and overtime is reported after the fact (Employee Report > Role Based Payroll carries OT Hrs, TTL OT Pay and, in Daily/Weekly format, 1.5x Hrs and 2x Hrs columns). Both are pay computation, not prevention. The Scheduler article documents shift creation, payroll totals and break deductions and states no overtime warning either when building a schedule or when an employee clocks in. What I could not check: the POS clock-in screen itself - the User Management section covers Forced Punch In/Out and manager cards but not clock-in prompts - so a punch-time warning is undocumented rather than shown absent.

labor-break-compliance-by-state differentiator

Break rules are configurable at store level: Store Scheduler Settings documents "Default Mealtime - Set the default time length of meals in minutes" and "Default Break Time - Set the default time length of breaks in minutes" alongside overtime thresholds, and the Scheduler article has managers "Enter the amount of time allotted for the types of breaks (in minutes)" for meal and rest breaks, which are "unpaid breaks and will deduct those Breaks from the Total Paid amounts"; the Employee Report > Attendance sub-report carries a Total UnPaid Break column and the POS records Break in/out even offline. Shortfall: these are single store-level defaults, not per-state or per-jurisdiction rule sets - the settings screen enumerates business info, week start, currency, timezone, formats, temperature unit, mealtime/break defaults, overtime hours-per-day and hours-per-week, and holidays, with no jurisdiction selector. No break attestation prompt at punch and no missed-break flag or premium-pay calculation is documented anywhere. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-store-scheduler-settings · retrieved 2026-08-07

labor-minor-labor-rules

Quote: "Minimum Age – For the Age (years) and the number limit of Hours (both mandatory ): enter the values, or use ▲/▼ to increase/decrease the values by 1 ." Payroll Report Settings carries a store-level Minimum Age rule pairing an age in years with an hour limit, and the employee record holds Date of Birth (Employees Scheduler: 'Date of Birth – View the employee's date of birth.'), so an age-based maximum-hours rule is configurable. Shortfall: only an age + hour-limit pair is documented; no prohibited time windows or school-day limits, and neither the Scheduler article nor POS: Time Clock documents where the limit is enforced (schedule build vs clock-in) or what happens when it is exceeded. The retail article repeats the same setting. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-payroll-report-settings · retrieved 2026-09-03 adversarially verified

labor-tip-pooling-rules

Tip-out/tip-sharing is configurable, not manual: a percentage amount of tip out per employee is entered ("Enter the percentage amount ... of tip out to the employee"), rules are defined by originating and receiving role ("Select the role in the dropdown that the tip out will be shared from", with recipient roles selected separately and the source role excluded from recipient options), scoped to one or more departments, and a Manual/Automatic toggle controls whether the collected Net Tip is distributed automatically or left to staff ("Manual and Automatic toggles cannot both be Enabled at the same time"). This is a configurable, role-based, automated tip-pooling engine, matching the claim. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-tip-out-tip-sharing-report-settings · retrieved 2026-08-04

labor-tip-distribution-audit-trail

Employee Report keeps per-employee tip records (CC Tip, Declared Cash Tip, Other Tips, OLO Pkup Tip) plus a Tip Out Share tab with "Tip Out Share" and "Tip Out Adjusted" per employee per business date, and Tip Shared / Tip Out Shared payroll columns; Back Office reports export to XLSX/CSV/PDF. Documented granularity is per business date, not per shift, and pool contributions vs distributions are not itemized as a two-sided ledger. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-employee-report · retrieved 2026-08-03

labor-qualified-tips-w2-reporting differentiator

Half the claim is met and documented by column name: the Employee Report > Role Based Payroll sub-report separates charged from cash tips - CC Tip, Grat, Other Tips, OLO Pkup Tip, Driver Comp, Declared Cash Tip - alongside Pay Rate, Reg Hrs, Reg Pay, OT Hrs, TTL OT Pay, Net Sales, Expected Tip, Tip Shared, Tip Adjustment, Tip Out Share, Tip Out Adjustment and Overall Pay, is broken out by Role (and a Labor By Job Code variant exists), and exports via the standard XLSX/CSV path. Shortfall: nothing in the report carries a Treasury tipped-occupation code, and no article mentions W-2 Box 12 code TP, Box 14b, or a qualified-tip designation for tax year 2026 - the role/job-code dimension is an operational grouping, not a TTOC mapping, so the export does not on its own support the 2026 reporting requirement. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-employee-report · retrieved 2026-08-07

labor-native-payroll differentiator

Payroll is delivered by integration, not first-party: ADP is the named partner connecting employee salary data with Linga, and Dash Solutions handles payroll delivery. No Linga-operated tax filing or direct deposit product. https://lingapos.com/integration-hub · retrieved 2026-08-01

labor-payroll-export-formats

Only one payroll provider (ADP) is named; Shogo and Dash Solutions cover accounting and payout rails respectively. The two-named-provider bar is not met. https://lingapos.com/integration-hub · retrieved 2026-08-01

labor-shift-swap-workflow differentiator

"Allow employees to switch or request a shift change with a click." Manager approval workflow enforcing overtime and role eligibility not documented. https://lingapos.com/solutions/schedules · retrieved 2026-08-01

labor-server-performance-metrics differentiator

"Live Staff Metrics" monitoring employee performance and productivity. Average check, category attach rate, and void/comp rate per server not documented. https://lingapos.com/solutions/insights · retrieved 2026-08-01

inventory-recipe-bom-costing

Support KB documents Recipes linking products for inventory deduction. Multi-level sub-recipes and automatic plate-cost recalculation on ingredient price change not documented. https://support.lingaros.com/portal/en/home · retrieved 2026-08-01

inventory-unit-conversion-yields

In House Units documents explicit purchase-to-usage conversion factors — "1 bag of potatoes (5kg) = 5000 grams", a Measurement field to 4 decimal places, and Volume/Weight measure types — and the inventory menu-items KB documents a per-item Recipe Unit ("if the Item selected is Milk, then the Recipe Unit could be Pint or Gallon"). Shortfall: no yield or waste percentage for raw-to-usable conversion is documented in the units, menu-items, or preparation articles. https://support.lingaros.com/portal/en/kb/articles/back-office-inventory-in-house-units · retrieved 2026-08-04

inventory-theoretical-vs-actual differentiator

Compare Inventory report: "High-level details comparing Inventory levels based on activity over a Time Period." Columns are Name, SKU Code, Beginning, Purchase, Ideal Used, Actual, Variance, Wastage/Restore, Usage, Transfer In, Transfer Out, On Hand, Unit, Type - and every one of those is reported as a Quantity/Price pair, so the variance between ideal (recipe-driven) and actual usage appears in both units and currency. Purchases feed the Purchase column and counts feed Actual/On Hand via Adjust Inventory. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-reports · retrieved 2026-08-07

inventory-realtime-depletion differentiator

Recipe-linked deduction on sale documented and ingredient-level tracking marketed. Near-real-time timing and modifier-driven depletion not stated. https://support.lingaros.com/portal/en/home · retrieved 2026-08-01

inventory-86-auto-sync differentiator

Quote: "Once the item count reaches zero, the item is flagged as unavailable, preventing further sales of that item across all POS terminals." Linga's 86 List propagates an item-level countdown across POS, iPad and online ordering ('When the Quantity is entered on the iPad then it will be reflected in iPad, POS and OLO' - POS: Operation - 86 List) and to Deliverect-connected delivery menus ('If the quantity of any item on the 86 List reaches zero ( 0 ), Redis will communicate to Deliverect that these items are out of stock (the PLU Code of each item will be snoozed)' - Deliverect Integration). Shortfall: the trigger is a manually set menu-item quantity, not a component ingredient hitting zero or a threshold; the inventory module's par level only raises a Low Stock notification ('If an Item goes below the Par Level , you will get a Low Stock notification.' - Inventory Item) and no article links inventory levels to the 86 List. Third-party sync is documented only for Deliverect. https://support.lingaros.com/portal/en/kb/articles/26-05-001-release-notes · retrieved 2026-09-03 adversarially verified

inventory-count-modes

Adjust Inventory offers three routes: a per-item "Tune" pane (a spot count of one item), "+ Bulk Adjustment" over a table of items, and download/upload of an AdjustInventoryItem.xlsx template for a whole-store count. A Reason Type is mandatory - "No other updates can be made until a Reason Type is selected" - and the Adjust Inventory report shows adjustments by type and reason with before/after quantities, so counts accumulate as history rather than overwriting. Shortfall: no scheduled or recurring cycle-count function is documented anywhere in /kb/linga-pos/back-office/inventory - all counting is operator-initiated ad hoc. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-adjust-inventory · retrieved 2026-08-07

inventory-mobile-count-offline

"Adjust inventory counts directly from your phone" plus "Fast, barcode-based stock control." Offline counting with sync-on-reconnect not documented. https://lingapos.com/solutions/inventory-management · retrieved 2026-08-01

inventory-vendor-catalogs-edi differentiator

The vendor record's full field set is enumerated - General (Name, Phone Number, Email, Description), Contact (Contact Name, Contact Number), Address (Address Line 1, Apt/Suite, City, State, Zip) - "Only Name is a Mandatory field." There is no catalog link, EDI/GLN identifier or account number. The Purchases article (/kb/articles/back-office-2024-inventory-purchases) states the purchase order carries a communication-method selection of "Email or Print", and the Low Stock article repeats "Delivery method selection (Print or Email)" - those two values are the entire documented transmission surface. Items are priced from operator-entered vendor Brand/SKU/Price rows on the inventory item, not from a distributor catalog. No named broadline distributor (Sysco, US Foods, PFG) appears anywhere in the KB. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-vendors · retrieved 2026-08-07

inventory-invoice-ocr differentiator

Read /kb/articles/back-office-2024-inventory-purchases end to end: the documented routes are Purchase Template, Place Purchase Order, Receive Purchase Order (operator types Vendor Invoice Number, Receive Date, Received Quantity and Received Price per line), an auto-generated Purchase Invoice where "Only the Vendor Invoice field remains editable", and "Receive New Item" for manual logging of off-system deliveries. No photo, PDF, email or OCR ingestion appears there, nor in /kb/linga-pos/back-office/settings/inventory (Inventory Taxes, Store Inventory, Matrix Report settings) or the Integration Hub index (14 entries; the accounting connectors are Shogo and Restaurant365, neither documented here as an invoice-capture path). Left unknown rather than no because none of those pages enumerates the ways an invoice may enter the ledger.

inventory-price-change-alerts differentiator

The inventory item carries a per-vendor Price and an auto-calculated Price/Unit, and Recipe Price is "Populated based on the formula = [Weighted Average / Latest Unit Price]" - i.e. the system retains prices across successive purchases rather than a single current price. Receiving records a Received Price per line separate from the ordered Price (/kb/articles/back-office-2024-inventory-purchases), and the Purchased Item report gives "High-level details about the store's purchased items". Shortfall: nothing generates an alert when a received price exceeds the prior or a contracted price - the configurable notifications in Back Office > Settings > Store > Notifications are Discount Limit, Void Limit, Max No Cash Drawer Accessed For No Sale, Time Clock, Daily KPI, End Of Day, Wait List, Sale Recap, One Page PDF and Offline Payment, with no price-variance entry, and no contract-price field exists on the vendor or item record. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-inventory-item · retrieved 2026-08-07

inventory-par-auto-suggest differentiator

Inventory is configured per store (Back Office > select Store > Inventory) and each inventory item has a "Par Level" field - "If an Item goes below the Par Level, you will get a Low Stock notification." The Low Stock page lists items below par in vendor-specific tables with Min Quantity ("referred to as Par Level"), Available Quantity and Inventory Unit, and a "Create Purchase Order" button that opens a PO pre-populated with the vendor, address, ship-to and the shortfall items, quantities adjustable. A Sub Recipe tab does the same for prepped items. Shortfall: order quantities are operator-adjusted off the on-hand-vs-par gap only - no sales-forecast-driven suggestion mode is documented, and the KB describes no forecasting engine. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-low-stock · retrieved 2026-08-07

inventory-waste-logging

Wastage Report: "Displays wastage activity of the Store's inventory, such as items that were voided, sold after their expiration date, or even not ever used", with columns Date, Item Name, Item Type, Wastage Type, SKU Code, Quantity, Cost Per Unit, Cost - so waste cost is reported separately from the Compare Inventory report's Ideal Used / Actual / Variance columns. The logging workflow is Adjust Inventory (/kb/articles/back-office-2024-inventory-adjust-inventory), where a Reason from a dropdown is mandatory before the count can be changed - "No other updates can be made until a Reason Type is selected" - and the reason list is itself configurable (Inventory > Adjust Inventory Reasons). The Adjust Inventory report then "Shows inventory adjustments by type and reason with before/after quantities". https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-reports · retrieved 2026-08-07

inventory-shelf-life-expiry

Expiry is tracked on purchased stock: the Wastage Report "Displays wastage activity of the Store's inventory, such as items that were voided, sold after their expiration date, or even not ever used", and its loss types include "Purchase Expired" alongside "Item Yield". Shortfalls: the report is retrospective - it costs spoilage that has already happened - and no expiring-soon report or alert exists (the Store Notifications settings enumerate Discount, Void, No-Sale drawer, Time Clock, Daily KPI, End Of Day, Wait List, Sale Recap, One Page PDF and Offline Payment alerts, none of them expiry). No expiration or use-by field is documented on the inventory item record (whose Tracking options are No Tracking, By Serial Number, By Lot Number) or on the receiving screen, and prepped items (Preparation / Sub Recipe) carry no documented shelf life. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-reports · retrieved 2026-08-07

inventory-bar-partial-bottle

Read /kb/articles/back-office-2024-inventory-inventory-item in full: units are handled as Inventory Unit (from In House Units), Purchase Unit with a Quantity multiplier and Yield %, and a Recipe Unit with Recipe Quantity - a fractional pour can therefore be expressed as a recipe quantity, but nothing documents counting a partial bottle. The only scale hardware in the KB is /kb/articles/back-office-2024-scale-barcode-addon-settings (Back Office > Settings > Addons), which is a retail weighed-item barcode addon, not a bar scale; /kb/linga-pos/back-office/settings/hardware holds only Receipt, Kitchen, Label and Rerouting printer articles. No tap-wall, flow-meter or pour-spout integration appears in the 14-entry Integration Hub index. Not resolvable to no: none of those pages claims to enumerate supported peripherals.

inventory-cogs-gl-export

Restaurant365 (complete accounting and back office) and Shogo (automated bookkeeping posting) are named integrations. Per-category GL account mapping configurable by the operator not documented. https://lingapos.com/integration-hub · retrieved 2026-08-01

inventory-native-not-partner differentiator

A native inventory module exists with ingredient-level tracking and KB-documented recipes, but the depth implied by the Restaurant365 partnership suggests serious costing is expected to be outsourced. https://lingapos.com/solutions/inventory-management · retrieved 2026-08-01

inventory-menu-margin-linkage differentiator

Matrix Report: "Displays high-level sales inventory activity based on Categories and/or Sub Categories", columns Item, Sold Quantity, Popularity, Avg. Cost/Unit, Sale Price/Unit, Profit/Unit, Total Cost, Total Revenue, Total Profit, Profit Category, Popularity Category, Menu Item Class - i.e. recipe-derived cost joined to actual sold quantity, with Profit/Unit defined as "Selling Price - Discount - Inclusive Tax - Total Cost". The threshold is real and configurable: Back Office > Settings > Inventory > Matrix Report requires a "Profit Threshold Amount - (Mandatory) Enter the threshold value Amount for the profit" and a "Popularity Threshold %", and items between 0 and the amount are classed Low. Shortfall: the classification only appears when the report is run - no flag or notification is raised when an item's margin crosses the threshold, and nothing ties the check to an ingredient cost change (the Matrix settings article states no alerts). https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-reports · retrieved 2026-08-07

reporting-realtime-dashboard

Marketing page only, and nothing establishes the 'real-time' half — no refresh interval, no streaming/live indicator, no statement of data latency between POS transaction and dashboard. Given that the dominant reviewer complaint is that Linga's sales reports do not reconcile against each other within the same system, an unqualified 'yes' on the reporting headline cell is exactly where scepticism should be highest. https://lingapos.com/solutions/insights · retrieved 2026-08-01 adversarially verified

reporting-eod-closeout

"The Daily Summary page displays a table that contains sales revenue information, broken down by Date, Department and revenue sources." Main table: Date, G/L Department, Gross Sales, Comps, Promo, Loyalty, Donation, Net Sales, Tax, Grand Sales. Summary table: Item Tax, Check Tax, Tax On Item Tax, Tax Rounding Off, Gift Card Sold Amount, Total After Tax. Deposits table: Cash, Gift Card, Total. Credit Card Summary: Card Type, Amount, Tip, Total, Credits, Net. Shortfalls: refunds are not a line on it - they sit in a separate Refund Report - and the expected-vs-counted cash reconciliation is on the Till Report, so a full close-out still means running three reports. A separate "End Of the Day Alert" and a "Sale Recap Report" can be mailed nightly (Settings > Store > Notifications). https://support.lingaros.com/portal/en/kb/articles/back-office-2024-daily-summary-report · retrieved 2026-08-07

reporting-pmix-modifier-level

"Top-Selling Item Reports" and "Sales Heatmaps" give item-level mix. Modifier-level PMIX and revenue-center filtering not documented. https://lingapos.com/solutions/insights · retrieved 2026-08-01

reporting-comps-voids-audit

Discount Report columns include "Discount Coupon Type" carrying "Promo, Comp or Donation", "Reason - The Reason and feedback for the discount", a Date with time (HH.MM AM/PM), and three employee attributions: "Sales Created By", "Applied By" and "Approved By". Void Report (/kb/articles/back-office-2024-void-report) shows voided check activity by Node or Employee with "Void Reason - The Reason the user selected when voiding the check", "Open By" and "Void By". An Audit Log report additionally logs Action, Event Date & Time, Employee, Device Type and old/new field values. Shortfalls: no price-override report or column exists anywhere in the 25-article Reports section; "Approved By" is documented as "the employee who closed the check", not a manager authorising the comp; the Void Report shows Date without a time; and comps/voids/discounts are split across separate reports rather than one audit. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-discounts-report · retrieved 2026-08-07

reporting-cash-over-short

Till Report columns: "Node: Which node (device) on which the transaction was performed", "Date: The creation of the till", "User: The name of the employee who set the till", "Cash Expected: The amount of money in cash form expected to be in the till", "Amount: The amount of money is left in the till", "Over/Shortage: The difference between the Cash Expected and the Amount". A Cash Transactions tab adds Transaction Date, Employee, Check, Node, Transaction Type, Amount and Reason, which is where paid-ins and paid-outs appear (a separate Paid In / Paid Out report also exists). Shortfall: the report is dimensioned by till/node/user and date - no shift designation is documented, so per-shift over/short is only available insofar as a till is opened and closed within a shift. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-till-report · retrieved 2026-08-07

reporting-labor-productivity

"Live Staff Metrics" monitoring employee performance, clock-ins and productivity. Sales per labor hour and labor cost percentage by hour/department not documented. https://lingapos.com/solutions/insights · retrieved 2026-08-01

reporting-server-scorecards differentiator

Employee performance monitoring is marketed; the specific scorecard metrics (average check, items per check, attach rate, tip percentage) are not enumerated. https://lingapos.com/solutions/insights · retrieved 2026-08-01

reporting-channel-profitability differentiator

The Enterprise Sale Report's tabs are Departments, Categories, Sub Categories, Menu Items, Modifiers, Hourly Sales, Daily Sales, Sale Recap, Cashier Out, Weekly Summary, Sale Summary, Enterprise Detailed Report and Online Sales, filterable by store - so online is separable from in-store, and gift-card activity is split in-store/online. The Revenue Center report (/kb/articles/back-office-2024-revenue-center-reports) "Displays a breakdown of the Store's Revenue ... based on the POS Node" with Net Sales by Category, by Shift and by Revenue Center, which is how dine-in areas and order channels are separated. Shortfalls: no report breaks out each third-party marketplace (Uber Eats, DoorDash, Deliverect, Chowly are integrations but do not appear as reporting dimensions), no commission or marketplace fee is netted anywhere, and margin by channel is not produced - the only margin reporting is the item-level Matrix Report. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-enterprise-reports · retrieved 2026-08-07

reporting-scheduled-delivery

"Easily download or email insights." Recurring automatic delivery on a defined cadence to a recipient list not documented. https://lingapos.com/solutions/insights · retrieved 2026-08-01

reporting-public-api differentiator

Re-pointed: developer.lingaros.com now answers Cloudflare 502 on every path and its root 302s to developer.lingapos.com, where the same Docusaurus doc set is live (fabricated path calibration: /docs/fabricated-nonexistent-xyz/ returns a genuine nginx 404 at 153 bytes, so these are real hits). Read directly: Paid In / Paid Out Reports documents GET https://api.lingaros.com/v1/lingapos/store/{store-id}/paidInOutReport with a curl example, an apikey header, and dateOption query parameters (T, Y, LND&numberOfDay, W, L7D, M, LM, L30D, SD&specificDate, DR&fromDate&toDate) plus paymentType=Paid_In|Paid_Out. The published sidebar covers all four required domains: orders (Online Ordering, Online Order API For Ext App), payments (Transactions Reports, Exchange Reports, HA Statement), menu (Products/Items, Modifiers, Modifier Groups, Categories, Subcategories, Discounts, Taxes, Menu Configuration) and labor (Employee Reports, Shift, Schedule Role, Schedule User), with Webhooks and API Limits pages as well. The previous note's 'self-serve credential issuance is still not available' is withdrawn: the Introduction page documents merchant self-service key issuance - sign in at lingaros.com, My Stores, Licenses, iPad Licenses page, Developer API, Key Generator - with no partner agreement step described. https://developer.lingapos.com/docs/doc-paid-reports/ · retrieved 2026-08-09

reporting-webhooks differentiator

Same evidence as extensibility-webhooks-push. No event push exists; reporting consumers must poll the transactions/paid-in-out report endpoints. Relevant to the reference platform comparison: an event-catalog-driven architecture cannot be mirrored against Linga without a polling shim. https://docs.pandium.com/connectors/connectors-101/linga-ros · retrieved 2026-08-01 adversarially verified

reporting-api-not-upcharged differentiator

Quote: "The Remaining Request field displays how many times the API is called, and displays count purchased by you by default." Raw-data access through the reporting UI is included: every Back Office report exports to XLSX/CSV/PDF ('Select one of XLSX (excel file), CSV ... or PDF' - Exporting Reports) and the Developer API key is self-generated in Back Office at enterprise or store level (Jan 7 2025 release notes: 'Move the developer API key option to the enterprise and store level configuration'), so there is no enterprise-only contract or revenue share. Shortfall: API calls are a metered 'Developer API License' bought in request-count blocks at a published $1 per 100 requests (1000 - $10 ... 5000 - $50) with an auto-renew when the count drops below 50 - an additional usage fee on top of the subscription. Whether the fee is per account or per location is not stated. developer.lingaros.com returned 502 for every page today, so the earlier 'Free Edition 250 credits per 24h' allowance could not be re-read. https://support.lingaros.com/portal/en/kb/articles/retail-back-office-enterprise-settings-addons · retrieved 2026-09-03 adversarially verified

reporting-tier-paywall differentiator

Walked /kb/linga-pos/back-office/reports (25 articles incl. Sale Reports, Void, Discounts, Till, Comparison, Employee, Matrix via inventory) and /kb/linga-pos/back-office/settings/reports (Tip Out & Tip Sharing, Sales Recap, Revenue Center, Payroll, Additional, Account Balance) - none of those articles marks a report as tier-restricted, and the enterprise-only marker the KB does use elsewhere (Store Payment Settings: "Enterprise Accounts only") never appears on a report. That is an absence of a gate notice, not a statement of inclusion. www.lingapos.com/payment-plans (re-fetched 2026-08-07) names "three flexible plans" without a feature comparison, so which plan carries labor-vs-sales, PMIX, comps/voids audit and multi-location comparison is still unpublished; the cross-store reports are structurally under Enterprise, which itself may be a separate SKU.

reporting-history-retention differentiator

Re-walked support.lingaros.com on 2026-08-07: /kb/linga-pos/back-office/reports lists 25 report articles (Transaction, Comparison, Daily Summary, Audit Log, Exporting Reports among them) and /kb/linga-pos/back-office/settings/reports lists 6 settings articles (Tip Out & Tip Sharing, Sales Recap, Revenue Center, Payroll, Additional, Account Balance). Reports are filtered by an operator-chosen Time Period with no documented lower bound, and no article states a retention window, an archive tier or a truncation point. developer.lingaros.com documents endpoints without a retention statement and lingapos.com publishes nothing on it. Unresolved: no page purports to define the retention policy, so absence of a 24-month guarantee is not evidence of truncation.

reporting-anomaly-alerts differentiator

The Store Notifications settings screen carries three operator-set numeric thresholds, each with "Text" and "Email" delivery options: Discount - "enter the discount amount in the Discount Limit field"; Void - "enter the Void amount in the Void Limit field"; and "Max No Cash Drawer Accessed For No Sale" - "enter the limit amount in the Limit field". Alerts go to the registered email address / phone number on the store account. The same screen adds untriggered periodic sends - Time Clock, Daily KPI, End Of the Day Alert, Sale Recap Report, One Page PDF - and an Offline Payment failure email. Note the thresholds are absolute limits, not deviation-from-historical-pattern detection, and there is no sales-below-forecast alert. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-store-notifications-settings · retrieved 2026-08-07

reporting-nl-query

Walked support.lingaros.com /kb/linga-pos (9 sections), /kb/linga-pos/back-office (14 subsections), /kb/linga-pos/back-office/reports (25 articles) and /kb/linga-pos/back-office/enterprise/reports: every documented reporting surface is a named fixed report - Sale, Transaction, Matrix, Comparison, Daily Summary and so on - driven by store/department/category/time-period filters. No AI assistant, chat or natural-language query article exists in any index, and the Enterprise Reports article describes dashboards rather than a query surface. Left unknown rather than no because a section index is not an enumeration of the product's features, and a recently shipped assistant could sit in /kb/linga-pos/release-notes-1 unread.

reporting-guest-cohorts differentiator

Enterprise reports include per-customer records: "Customer Item History" (Date, Check Number, SKU/Barcode, Description, Quantity, Net Sale, Discount, Total), "Item Sale History" (Item Name, Transaction Date, Check Number, Customer Name, Quantity Purchased), and a Loyalty report with per-customer Total Accumulated Points, Redeemed Points and Current Available Points - all tied to identifiable guest records and spanning stores. Shortfalls: no new-versus-returning guest count, no visit-frequency measure and no lifetime-spend cohorting is produced by any of them; the Customer Preference Report, despite its name, "displays Customers' ordering activity" only as aggregated item quantity and amount by category, not per guest; and the Membership report covers plan balances (Allowance, Overdraft Due, Beginning/Current Balance), not visit behaviour. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-enterprise-reports · retrieved 2026-08-07

reporting-sales-forecast differentiator

"Predictive Trends" for inventory, sales and staffing forecasts. Daypart/hourly granularity and consumability by scheduling or ordering workflows not documented. https://lingapos.com/solutions/insights · retrieved 2026-08-01

reporting-tip-tax-compliance

The Employee Report carries per-employee "CC Tip" and "Declared Cash Tip" columns, a Cash Tip tab tracking expected versus declared amounts, and a Tip Out Share tab breaking distribution down by role and business date, with "Overall Tip" summing tip out, tip share, gratuity, driver compensation and declared tip. Shortfall: no tax liability summary by jurisdiction is documented in the reporting KB. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-employee-report · retrieved 2026-08-04

multi-location-org-hierarchy

"Set Groups & Management Levels" with roles and permissions assigned "across your franchise hierarchy." A named three-level enterprise > region > location object model not documented. https://lingapos.com/restaurant/franchise · retrieved 2026-08-01

multi-location-central-menu-publish

Corporate can "create, update, and control each POS location from the backend" and kiosk menus/pricing update instantly across locations. Single-action publish to a selected set with version history showing what/when/who not documented. https://lingapos.com/restaurant/franchise · retrieved 2026-08-01

multi-location-price-zones

Channel dimension only: delivery-platform integrations let you "set the order platform price level for menu price level, and modifiers percentage". Per-location-group price tiers and daypart pricing are not documented — Enterprise Menu Configuration instead documents transferring/copying menu records between stores, i.e. per-store copies rather than zone pricing on one item record. https://support.lingaros.com/portal/en/kb/articles/uber-eats-integration · retrieved 2026-08-03

multi-location-consolidated-reporting

"Live overview of all store activities," ability to "analyze detailed sales and inventory operations worldwide," compare performance across locations and time periods, and monitor transactions by location and time of day. https://lingapos.com/restaurant/franchise · retrieved 2026-08-01

multi-location-cross-location-giftcard

"Customizable Gift Cards" marketed across franchise locations. Outstanding-liability reporting and inter-store redemption settlement between owners not documented. https://lingapos.com/restaurant/franchise · retrieved 2026-08-01

multi-location-cross-location-loyalty

Loyalty marketed as built for franchise businesses and activity is "tracked from anywhere the customer is active." A single shared profile and balance across all brand locations is implied but not explicitly documented. https://lingapos.com/restaurant/franchise · retrieved 2026-08-01

multi-location-multi-brand differentiator

2026-09-03 re-sweep (195th): the full support.lingaros.com KB (605 articles) and www.lingapos.com were read; an analyst proposed partial from https://www.lingapos.com/integration-hub/deliverect and the adversarial pass returned it to unknown: integration-hub__deliverect.txt (URL matches) 'Virtual Brands Integration : Integrate virtual brands with the ability to manage multiple storefronts through a single delivery platform.' is a description of Deliverect's platform, not of anything the Linga terminal does. The claim asks whether ONE location/terminal operates two brands with separate menus, receipts/branding and separately reportable revenue on the same hardware and drawer. The KB article linga/deliverect-integration.txt shows the integration is one 'Deliverect Location Id' per store, 'Publish Menu to publish the store's menu items to Deliverect' with an order-platform price level - a single store menu pushed out, with nothing about a second brand's menu, receipt identity, or separate revenue coming back into the POS. The partner rule allows partial when the partner supplies the claimed capability; here the partner sentence does not supply it, it supplies delivery-storefront management on Deliverect's side. KB grep (virtual brand, multi-brand, brand identity, second brand, concept, storefront) finds only 'Virtual Kiosk' and virtual gift cards; revenue-center articles partition by node, not brand. No closed enumeration either, so not no. Unknown - the analyst itself flagged this as weak. Prior rationale: Read /kb/articles/back-office-2024-stores: one account holds many stores, each with its own Store Name, Account Type (Restaurant or Retail), Business Type, time zone, language and address, organised by Store Groups, and a new store can "Copy Menu From an Existing Store" - so separate menus and separate reportable revenue exist AT THE STORE LEVEL. That is not the claim, which asks for two brands on one location's hardware and drawer. Also checked /kb/linga-pos/back-office/enterprise (Home, Menu Configuration, Central Inventory, Customers, Reports, Settings) and the Enterprise Settings index (Royalty Franchise, Account, Central Inventory, Addons), plus /kb/linga-pos/back-office/settings/printer-templates for per-brand receipt branding - no concept, brand or virtual-brand entity is documented, and nothing says a single node can run two menus with separate receipts. Unknown rather than no: revenue centers do partition a store's transactions by node, so the underlying mechanism may exist undocumented. adversarially verified

multi-location-multi-tax-jurisdiction

Tax is configured after selecting a Store, and the screen shows "a table containing all currently existing Taxes within the Store" - so multiple simultaneous rates per location, and rates differ store to store. Each tax has an "Inclusive" column and field ("Select whether it is Inclusive"), an "Apply To" of Item or Check, a "Tax Per Service Type" toggle whose Value "specifies how the Tax is applied, broken down by Service Type" (the dine-in vs takeout style rule), and a "Quantity Based" mode with threshold-specific percentages. A separate Inventory Taxes setting exists under Settings > Inventory. Shortfall: no per-location tax exemption is documented - the Taxes article describes no exempt customer, exempt organisation or tax-exempt flag, and none appears in the Customers or Store settings indexes. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-taxes · retrieved 2026-08-07

multi-location-central-labor-policy

Quote: "If an Employee wants to end their Break early, only a Manager can perform this action from the Manager screen or from BO (the Employee cannot end their Break early)." Break rules are defined per store in Back Office (Payroll Report Settings > Manage Breaks: Break Name, 'Duration (Minutes)', Paid/Unpaid, 'Apply To : All Employees / Specific Roles / Specific Employees', plus 'Select the Terminal to log Break-In/Out') and are enforced at the POS time clock, which greys out End Break until the configured duration has elapsed and requires a manager override. Shortfall: the rule is per store, with no documented location-group inheritance from Enterprise Settings (Enterprise Settings covers Account, Royalty/Franchise, Central Inventory, Addons - no labor section); overtime is configured per store only as pay tiers with no terminal enforcement; and nothing covers predictive-scheduling compliance. https://support.lingaros.com/portal/en/kb/articles/pos-time-clock · retrieved 2026-09-03 adversarially verified

hardware-commodity-devices differentiator

Linga markets "cross-platform compatibility" and multiple form factors including handheld, and Insights ships an Android and iOS app. Specific commodity devices the operator may source independently are not enumerated. https://lingapos.com/payment-plans · retrieved 2026-08-01

hardware-os-platforms

A "Hardware Requirements" section exists in the public support KB and the Insights mobile app names Android and iOS. Specific minimum OS versions and device specs were not retrievable. https://support.lingaros.com/portal/en/home · retrieved 2026-08-01

hardware-handheld-purpose-built

Handheld marketed as an available form factor. No published drop rating, IP ingress rating, or integrated-reader model. https://www.lingapos.com/solutions/linga-pos · retrieved 2026-08-01

hardware-handheld-battery-swap differentiator

Read /kb/articles/pos-hardware-requirements in full: it states minimum specifications rather than a device catalogue - iOS is "iPad 10.2" 8th Gen (2020) or later", iPad Mini 5th Gen+, iPad Air 4th Gen+, iPad Pro 12.9" 4th Gen+ and 11" 2nd Gen+ with iPhone explicitly not supported; Android is "Minimum 4 GB" RAM, "Minimum 8 GB" storage, "Android 11 and above"; Windows is 8 GB RAM, Windows 11, Chrome. No model, battery capacity, runtime or swappable-battery statement appears there or in the rest of /kb/linga-pos/hardware-and-networking (Bluetooth Scanner, POS Terminal Requirements, Hardware Requirements, Domain). Because Linga runs on operator-supplied tablets rather than a vendor handheld, there may be no vendor battery claim to find - but that is inference, not a published statement.

hardware-handheld-lte

Read /kb/articles/pos-hardware-requirements (iPad/Android/Windows minimum specs; the article says nothing about network connectivity at all) and walked /kb/linga-pos/hardware-and-networking, whose four entries are Bluetooth Scanner, POS Terminal Requirements, Hardware Requirements and Domain. The failure story the docs do tell is /kb/linga-pos/pos/offline-mode - continuing to trade when the connection drops - not a cellular failover. No LTE, SIM, hotspot or vendor-supplied backup-connectivity statement is published on support.lingaros.com. Unresolved: a device the operator buys may well have LTE, but Linga documents no such fallback itself.

hardware-offline-mode

KB documents an Offline Mode toggle under POS settings (disabled by default) and marketing claims continued operation without Wi-Fi. Which functions degrade is not documented. https://support.lingaros.com/portal/en/home · retrieved 2026-08-01

hardware-kds

First-party KDS product with bump bar, station routing to screens or printers, color-coded item organization, and cook-time/status tracking. https://www.lingapos.com/solutions/kitchen-display-system-kds/ · retrieved 2026-08-01

hardware-kiosk differentiator

Wall-mounted and countertop form factors with integrated payment accepting tap, chip, swipe, gift cards and digital wallets. Freestanding form factor and ADA compliance documentation absent. https://lingapos.com/solutions/kiosk · retrieved 2026-08-01

hardware-drive-thru

Re-checked support.lingaros.com on 2026-08-07: /kb/linga-pos/back-office/settings/hardware holds Receipt Printer, Printer Rerouting, Label Printer and Kitchen Printer articles (the Kitchen Printer article's printer types are Printer, KDS, Driver and Runner); /kb/linga-pos/back-office/settings/addons holds Scale Barcode, Kiosk, Feedback App and Customer Display Screen (CDS); /kb/linga-pos/hardware-and-networking holds four networking/spec articles; the 17-entry /kb/linga-pos/pos index has no drive-thru screen. No outdoor menu board, order-confirmation display, speaker/headset integration or speed-of-service timer is documented. Left unknown, not no: these are configuration screens for the peripherals Linga does support, not a supported/unsupported hardware table.

hardware-printer-compatibility

Back Office > Settings > Hardware > Receipt Printers: each printer takes a "Name (mandatory)", an "IP Address (mandatory), which can be found when the printer is connected via an Ethernet cable", a "Printer Model" selected "from the dropdown", and a default flag ("There can only be one Default printer at a time"). Kitchen Printers (/kb/articles/back-office-2024-kitchen-printer-hardware-settings) work the same way with types Printer, KDS, Driver and Runner, service-type restrictions, category routing and an "Alternate Printer" failover; separate Label Printer and Printer Rerouting articles exist. So networked (LAN/Ethernet) printing and a choice of models are documented. Shortfalls: the Printer Model dropdown's values are never published, no manufacturer is named anywhere in the KB (no Epson, Star or Bixolon), and /kb/articles/pos-hardware-requirements specifies only tablet/PC minimums, so multi-manufacturer ESC/POS compatibility is asserted nowhere first-party. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-receipt-printer-hardware-settings · retrieved 2026-08-07

hardware-peripherals

Partial upheld, one factual correction: customer-facing displays ARE documented. 'Customer Facing Display' is a named first-party solution in Linga's solutions menu, and the POS page lists 'customer display' among supported form factors alongside handheld, tablet and kitchen display. Cash drawers (single or multi), scales for by-weight items, and any multi-manufacturer compatibility list remain genuinely absent, so the score does not move. https://www.lingapos.com/solutions/linga-pos · retrieved 2026-08-01 adversarially verified

hardware-p2pe-terminal

"EMV-Ready Terminal" plus "100% PCI Compliant" marketing. No PCI PTS device listing, no validated P2PE solution reference, no merchant SAQ type stated. https://www.lingapos.com/solutions/linga-pay/ · retrieved 2026-08-01

hardware-tap-to-phone differentiator

Read /kb/articles/pos-hardware-requirements: supported devices are listed iPad models, Android devices with 4 GB RAM / 8 GB storage / Android 11+, and Windows 11 with Chrome, and it states iPhone is not supported - so Tap to Pay on iPhone cannot apply. The claim's other branch (Tap to Pay on Android, no separate reader) is not addressed: /kb/linga-pos/back-office/settings/payments holds Payment Till, Store Payment, Payment Method and EMV Payment settings, and the EMV article describes "a table which contains all current EMVs under the Store" - paired reader devices - without ever saying whether the tablet's own NFC radio can take a tap. No softPOS article exists in the 17-entry POS index or the Payments subsection. Unresolved rather than no because the payments settings do not enumerate acceptance methods.

hardware-pricing-transparency differentiator

No hardware prices published per SKU. The payment-plans page instead offers hardware "included at no extra cost" bundled against 3-year processing and SaaS commitments, and directs pricing questions to a sales rep. https://lingapos.com/payment-plans · retrieved 2026-08-01

hardware-ownership-vs-lease differentiator

Vendor documents a hardware-included plan tied to 3-year commitments; whether the operator owns that hardware, and what outright purchase costs, are not stated. https://lingapos.com/payment-plans · retrieved 2026-08-01

hardware-usable-after-churn differentiator

Quote: "Transfer of Title and Risk of Loss Unless otherwise set forth in the Sales Order, title to the Hardware shall transfer to Customer upon sale of the Hardware." The published Sales Terms (Appendix B) now answer part of the question: title to purchased Hardware passes to the Customer at sale, and the termination clause reclaims only 'LINGA Items' (Services, Work Product, IP, Proprietary Information) - Hardware is not among them, so the vendor asserts no post-termination reclaim of purchased units. Shortfall: the same appendix contractually forbids loading non-factory software on the Hardware and nothing says whether that covenant survives termination; no sentence addresses remote lock/bricking; and Complimentary Hardware Program units (3-year SaaS + Hybrid Payments term, graduated Cancellation Fee) are governed by a fee schedule with no ownership statement beyond the general title clause. Grade B (vendor legal text). Prior August note said no terms were retrievable; the www host now serves them. https://www.lingapos.com/sales-terms-and-conditions · retrieved 2026-09-03 adversarially verified

hardware-rma-sla differentiator

Quote: "LINGA warrants that from the sale of the Hardware and for a period of twelve (12) months ( "Defect Warranty Period" ) thereafter, such Hardware will be materially free from defects in material and workmanship under normal use and operation for its intended purpose ( "Defect Warranty" ). LINGA's sole and exclusive obligation and liability under the Defect Warranty shall be for LINGA to replace any " Establishes a published 12-month hardware Defect Warranty with replacement as the remedy, and that an advance-replacement path exists ('If LINGA agrees to provide replacement hardware before Customer has shipped the return hardware'). Shortfall: advance exchange is discretionary ('If LINGA agrees'), no turnaround (next-business-day or otherwise) is stated anywhere, the Customer pays return shipping ('at its own expense and in secure packaging'), and out-of-warranty repair is 'at LINGA's then standard price' with no price published. Warranty term yes, SLA no - hence partial. Grade B. https://www.lingapos.com/sales-terms-and-conditions · retrieved 2026-09-03 adversarially verified

hardware-byod

Read /kb/articles/pos-hardware-requirements: Linga POS runs on any Android device meeting 4 GB RAM / 8 GB storage / Android 11+, listed iPads, or Windows 11 with Chrome, and iPhone is explicitly not supported - so a staff member's own Android tablet would meet spec, but the article is a spec sheet, not a BYOD policy. The permission machinery lives in /kb/linga-pos/back-office/user-management (Roles; Roles - Manager Access: Discount Transfer Void; Adding a Manager Card; Disabling a User from Sign In) and device sessions can be revoked from Store Licenses settings, yet nothing frames any of that as a personal-device model, and no MDM, containerisation or device-enrolment guidance is published. Unresolved: the security model for a personal phone is simply not addressed.

hardware-remote-device-management differentiator

Back Office > Settings > Store > Store Licenses: "Each currently connected device and its activity is listed", with an Actions column offering Sign Out per device behind a confirmation - i.e. a central roster of terminals with a remote revoke. Devices are also identifiable in reporting (the Audit Log report carries Device Name, Device Type and Node columns, and the Till Report is dimensioned by Node). Shortfalls: no online/offline status indicator, no software version display, no remote reboot, and no staged or phased update rollout is documented on that page or anywhere in /kb/linga-pos/back-office/settings; printers and KDS are configured by IP under Settings > Hardware with only an "Alternate Printer" failover, and their up/down state is not surfaced. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-store-licenses-settings · retrieved 2026-08-07

hardware-selfpour-scales

Checked /kb/linga-pos/back-office/settings/addons, whose four entries are Scale Barcode, Kiosk, Feedback App and Customer Display Screen - the Scale Barcode addon parses weighed-item barcodes from a retail scale, which is deli/retail weighing, not a pour-measurement device. /kb/linga-pos/back-office/integration-hub lists 14 partners (Octopus, Order Webhook, Servme, Uber Eats, Shogo, Restaurant365, Deliverect, Chowly, ADP, ADP WFN, DoorDash Drive, Dash Solutions, Factor4, User Manual) with no self-pour, tap-wall or flow-meter vendor; /kb/linga-pos/pos/bar-tab covers tabs and pre-auth, not metered pours. Left unknown, not no: an integration directory is not an exhaustive enumeration, and Order Webhook would let a third party post pours without Linga documenting it.

hardware-callerid-integration

Caller ID integration listed as a first-party module in Linga's own solution set — relevant for phone-order-heavy pizzerias. https://www.lingapos.com/ · retrieved 2026-08-01

extensibility-public-api-docs

Re-pointed and now confirmed first-hand. developer.lingaros.com answers a 16-byte Cloudflare 502 everywhere; its root 302s to developer.lingapos.com, which serves the live doc set. Fetched anonymously with an ordinary browser user agent, no login, NDA or partner agreement: /docs/docs-schedule-api-token/ returns 200 at 68,930 bytes and shows POST https://api.lingaros.com/v1/schedule/v1/auth/login with a username/password body table and a curl example, then GET .../v1/schedule/v1/nstore/list taking a token header. A fabricated sibling path returns a genuine nginx 404 at 153 bytes, so this is a real document and not a soft-404 shell. The publicly readable sidebar spans about 42 pages from Introduction and API Limits through Users, Roles, Customers, Loyalty, Gift Card, Store, Modifiers, Categories, Products/Items, Discounts, Taxes, Online Ordering, the report family, Shift and Schedule endpoints, to Webhooks. The prior note's caveat that the pages could not be loaded directly and were confirmed only via search-engine extraction is withdrawn - they load. https://developer.lingapos.com/docs/docs-schedule-api-token/ · retrieved 2026-08-09

extensibility-api-access-cost differentiator

Quote: "License Price Displays the Price of the API Request Count . For an API Request Count of 100 , then a License Price of $1 appears." API access needs no plan upgrade: the Developer API Key page lives under Enterprise Settings > Addons and, since January 2025, at store level too, and any Back Office user with the 'Developer API Key' role can open it (Integration Hub User Manual). Shortfall: calls are metered against a purchased request count ('The Remaining Request field displays how many times the API is called, and displays count purchased by you by default') sold at $1 per 100 requests with optional auto-renew when the balance drops below 50 - a usage surcharge rather than inclusion in the base subscription. Whether the count is per account or per location is not stated. developer.lingaros.com (Free Edition 250 credits/24h in the August reading) returned 502 on every page today and www.lingapos.com/partners/become-a-developer-partner (fetched today because the lingapos.com corpus file is a bare 301) only points to the API documentation site with no pricing statement. https://support.lingaros.com/portal/en/kb/articles/retail-back-office-enterprise-settings-addons · retrieved 2026-09-03 adversarially verified

extensibility-free-sandbox differentiator

Walked the entire developer.lingapos.com table of contents (Get Started: Introduction, API Limits, HTTP Methods; Users; Customer; Sync; Kiosk; Store; Products/Items; Online Ordering; Menu Configuration; Reports; Schedule; Automation: Webhooks; Others: API Usage). No sandbox, test, staging or demo environment appears anywhere in it, and /docs/introduction documents exactly one credentialing path: generate an apikey inside the live Back Office under the Developer API section via 'Key Generator', which presupposes a provisioned store. /docs/api-limit's 'Free Edition - 250 credits' is a per-24h credit allowance tied to a product edition, not a developer sandbox with seeded data. Because a Get Started page is not an exhaustive enumeration of commercial access options, absence here is not scored as a finding of absence.

extensibility-oauth-partner-apps

The API reference documents exactly one auth mechanism: a static per-store key in an apikey header (curl -X GET -H "apikey: generated-api-key"), generated under Licenses > Developer API > Key Generator per the Introduction page. No OAuth 2.0, bearer tokens, scopes, or per-app operator grants appear anywhere in the reference. developer.lingaros.com now redirects to developer.lingapos.com. https://developer.lingapos.com/docs/doc-categories/ · retrieved 2026-08-03

extensibility-webhooks-push

Linga rOS does push webhooks rather than requiring polling: "As soon as the order is sent to the kitchen and after the order is closed, information about the order is sent in json format to the address specified by the customer via HTTP Post method." Shortfall: only two of the five lifecycle events in the claim are covered. The developer reference documents exactly two - "Open Order Web Hooks: The address to which the order information will be transmitted when the order is sent to the kitchen" and "Close Order Web Hooks: ... when the order is closed" - with no modified, voided or refunded event, and the whole configuration surface is a request header plus a URL and an active toggle per event. This corrects a prior `no` taken from Pandium's third-party connector matrix ("webhook support: No"), which is contradicted by the vendor's own API documentation. https://developer.lingapos.com/docs/doc-automation/ · retrieved 2026-08-07 adversarially verified

extensibility-webhook-reliability differentiator

The Linga rOS API webhooks reference documents exactly two events - Open Order Webhooks, fired 'when the order is sent to the kitchen', and Close Order Webhooks, fired 'when the order is closed' - delivered as JSON 'to the address specified by the customer via HTTP Post method'. The full configuration surface it enumerates is: the destination address, an active/inactive toggle per webhook type ('Determine whether the web hook will be active'), and a free-text 'Request header ... used to add header information to the http request to be made'. There is no signing secret, HMAC or signature header, no retry or backoff behaviour, and no delivery history or replayable event log; a customer-supplied static request header is the only receiver-side authentication offered. Note for a future pass: this page also contradicts the existing extensibility-webhooks-push='no' cell (sourced from Pandium's connector matrix), which is outside this sweep's scope - push webhooks demonstrably exist. https://developer.lingapos.com/docs/doc-automation/ · retrieved 2026-08-07

extensibility-order-injection-api

An "online ordering" API is named among the four documented API areas, but whether it writes externally-originated orders as first-class tickets firing to KDS/printers is not stated. https://lingapos.com/partners/become-a-developer-partner · retrieved 2026-08-01

extensibility-menu-write-api differentiator

"Menu item arrangement & categorization" is a named API area, implying write capability, but price and modifier write operations are not confirmed. https://lingapos.com/partners/become-a-developer-partner · retrieved 2026-08-01

extensibility-doordash-preferred differentiator

Verified against DoorDash's own newsroom, and supplying the URL the dossier omitted — a scored cell with no source URL violates the evidence bar even when the score is right. The 2026 cohort is Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast and UrbanPiper. Linga is absent. Mitigating context the dossier should carry: Chowly and Deliverect are both preferred partners and both are named Linga integrations, so DoorDash coverage via middleware is available. 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 DoorDash Drive appear as direct hub integrations, but Grubhub is absent and Deliverect/Chowly are offered in parallel, indicating middleware is the expected path for full marketplace coverage. https://lingapos.com/integration-hub · retrieved 2026-08-01

extensibility-middleware-compatibility

Two major aggregation platforms are named partners: Deliverect ("Connects delivery services to your POS") and Chowly ("All-in-one digital ordering platform"). https://lingapos.com/integration-hub · retrieved 2026-08-01

extensibility-accounting-connectors

Restaurant365 and Shogo are named vendor-maintained accounting connectors. QuickBooks Online is not named directly (Shogo is a posting intermediary), and mapped journal entries versus CSV are not documented. https://lingapos.com/integration-hub · retrieved 2026-08-01

extensibility-payroll-export

Only ADP is named as a payroll integration. The bar of two named providers is not met. https://lingapos.com/integration-hub · retrieved 2026-08-01

extensibility-app-marketplace

A public, browsable Integration Hub lists named third-party apps (DoorDash Drive, Uber Eats, Deliverect, Chowly, Restaurant365, Shogo, ADP, Dash Solutions, Factor4, Octopus Bridge). Operator self-install is not documented. https://lingapos.com/integration-hub · retrieved 2026-08-01

extensibility-headless-embedded

The Online Ordering API documents POST https://api.lingaros.com/v1/online-order/store/{store_id}/saveWebOrder (apikey header, application/json) alongside GET .../placedOrders, so a 'Web or app-based ordering platform' can submit orders into the POS; the separate Kiosk API (http://developer.lingapos.com/docs/doc-sync-kiosk/) exposes POST /v1/lingapos/kioskLogin and GET /v1/lingapos/store/{store-id}/kioskJSON, i.e. authentication plus a store/menu configuration payload a kiosk UI can render from. Shortfall: the documented surface stops at order submission and configuration retrieval. The 'Online Order API For Ext App' endpoint is read-only (GET .../ordersForExtApp with count, currentPage, fromDate, toDate, orderStatus). No endpoint is documented for check pricing/tax calculation, tender or payment authorisation, or drive-thru, so a third-party UI cannot drive the POS transaction engine end to end - it hands a finished order over to it. https://developer.lingapos.com/docs/doc-online-ordering/ · retrieved 2026-08-07

extensibility-data-portability-exit differentiator

Back Office: Exporting Reports documents a machine-readable export on Back Office reports - 'Select a Format - Select one of XLSX (excel file), CSV (Character Separated Valuables, typically opened in spreadsheet [Excel]) or PDF' with a Delivery Option of 'Direct Download (directly to your computer)' or 'Send by Email (file sent as Email Attachment)'. The report catalogue that feeds it includes Transaction Report, Sale Reports, Tax, Discounts, Void, Refund, Gift Card, Membership, Employee and Audit Log reports, and the Customer Info screen carries a separate Export button. Shortfall: the export acts on a report's displayed/filtered results, one report at a time; no complete historical dump of orders, customers, menu and payments metadata is documented, no scheduled or API-driven bulk export is described, and the published Sales Terms and Conditions state that on expiration or termination 'the Services and Customer's right to access and use the Services ... shall immediately terminate and cease', so there is no documented at-exit extraction path. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-exporting-reports · retrieved 2026-08-07

reliability-offline-order-entry

Offline Mode toggle documented in the KB and marketing claims operation without Wi-Fi. Whether ticket routing and check printing specifically continue is not stated. https://support.lingaros.com/portal/en/home · retrieved 2026-08-01

reliability-offline-card-auth differentiator

UPGRADED WHEN THE DEAD CITATION WAS CHASED, AND THE OLD EVIDENCE IS WITHDRAWN RATHER THAN RE-POINTED. The prior note rested on "When an Offline payment is made by using Magtek, the toggle will automatically be enabled" — and Magtek appears in NONE of the four live Linga offline articles, so that sentence is withdrawn. What replaced it is stronger and answers the exact shortfall the old note named ("does not describe the store-and-forward mechanism, settlement window, or any per-transaction/cumulative cap"). The Restrict Offline Payment article documents a real store-and-forward path for cards: an offline limit that gates them ("The offline limit value will be settled only for Card payments made in MPPG offline payments only", "each offline payment amount limit validation will apply only to MPPG payments"), a reset on processing ("When process offline is clicked, the Offline Limit value will be reset"), an explicit reconnect prompt ("Offline payments are available. Do you want to process it?") that re-triggers after thirty minutes if declined, and settlement through the Batch screen. That is card acceptance while offline with deferred capture, which is the claim. TWO LIMITS KEPT: whether the offline limit is per-transaction or cumulative is still not stated, and the vendor warns in the Offline Mode article "When in Offline Mode, do not accept Debit Card payment from the customer, as the transaction is more likely to be Declined" — so the capability is real but credit-weighted. Grade B: vendor KB documentation. https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-restrict-offline-payment · retrieved 2026-08-09

reliability-offline-decline-liability differentiator

The Store Payment Settings screen exposes an 'Offline Payments Settings' YES/NO toggle with two operator-configurable caps: 'Each Offline Payment Amount Limit' (maximum per transaction) and 'Total Offline Payments Limit' (the sum of all offline payments). The companion article POS: Offline Mode - Restrict Offline Payment adds that 'The offline limit value will be settled only for Card payments made in MPPG offline payments only', that 'Other payments won't be considered', and that 'When process offline is clicked, the Offline Limit value will be reset'; POS: Offline Mode - Process Offline Alert Message states that 'Any error/invalid offline checks will also be added along with the valid offline transactions in the alert messages'. Shortfall: the cap side of the claim is documented, but no Linga page - support portal, Sales Terms and Conditions, or EULA - states who bears the loss when a stored-and-forwarded transaction declines after connectivity returns. The caps are also a merchant-set exposure ceiling, not a vendor liability commitment. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-store-payment-settings · retrieved 2026-08-07

reliability-lan-degraded-multi-terminal differentiator

The POS: Offline Mode article documents the degraded-mode behaviour directly: 'The POS to redis server will also stop. So, the checks made from one POS node will not be reflected in other nodes.' Each device instead works locally - 'if enabled, this toggle then system works in Offline mode. The payments, employee clock in, etc. will be stored locally' - and checks connectivity every 15 minutes, with 'the actions stored locally during offline mode ... posted to the server' once the link returns. This is the vendor's own statement that shared check/table state does NOT survive an internet outage over the LAN; terminals run as isolated islands until reconnect. https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-8-5-2025 · retrieved 2026-08-07

reliability-local-transaction-engine differentiator

Quote: "The Back Office to POS connection won’t function (sync won’t be available), and the POS to Redis Server will also stop. Any Checks from a POS Node will not be reflected in other Nodes." Positive evidence of absence. The article defines offline as loss of internet ('When the system is reconnected to the internet, the actions stored locally during offline mode will be posted to the server') and states that in that state node-to-node check sharing stops and the only things the local network still connects are printers and KDS. The mediating redis is cloud-side: release notes 26-02-001 and 26-03-001 say 'The Redis URL has been changed to Sync servers in V2'. A LAN-resident transaction engine would by definition keep checks shared between nodes with the WAN down; Linga documents the opposite - per-device store-and-forward only ('The payments , employee clock in , etc. will be stored locally'). This is structural absence from the vendor's own architecture description, not a failure to find. Flag: it is an inference from the offline-mode behaviour rather than a sentence saying 'no local server'. https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-8-5-2025 · retrieved 2026-09-03 adversarially verified

reliability-offline-kds-printing

The Offline Mode KB states "IP address printers (Kitchen printers, Receipt printers) will continue to work" while offline, and the successor article is EXPLICIT that KDS is included and that the reason is local connectivity: "All the printers are connected to local network through intranet. When this is in Offline mode, then you will be able to access all printers such as kitchen printers, receipt printers, KDS etc." That retires the prior caveat that "KDS offline routing is not separately documented" — it is documented, by name. The remaining caveat stands: the Offline Mode toggle ships disabled by default. A TRAP RECORDED, because it nearly cost this cell its verdict: the rewritten sibling pos-payments-offlinemode carries a much weaker sentence, "When the network is available but the offline mode toggle is enabled, the IP Address printers will continue to work as-usual", which is about a toggled state under a LIVE network and would not support this claim at all. Re-pointing to the nearest-looking sibling would have quietly hollowed out a yes. [Citation repaired 2026-08-09: the cited article 404s and this evidence now rests on pos-offline-mode-8-5-2025, the successor, where the quotation above was re-verified verbatim.] https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-8-5-2025 · retrieved 2026-08-09

reliability-printer-fallback

When a kitchen printer is offline the POS retries — "a check will be performed 3 times, then connect to the Alternate Printer" mapped in Back Office — and alerts staff: "Unable to connect [Printer Name]. Hence the printing will be continued in [Alternate Printer Name]". https://support.lingaros.com/portal/en/kb/articles/pos-operation-printer-hardware-settings · retrieved 2026-08-03

reliability-sync-conflict-handling

The dedicated Offline Mode article documents the sync model and it contains no conflict resolution: offline actions are stored locally and "Once the connection is restored, POS will transfer all offline data to the back office", while the shared-state operations that could conflict (Back Office connection, customers, memberships, till, reports, refunds, 86 list) are blocked offline. The documented behavior is a one-way post of stored actions — last-write-wins/merge/prompt semantics for concurrent edits are documented nowhere, which is the claim's subject. [Citation repaired 2026-08-09: the cited article 404s and this evidence now rests on pos-offline-mode-8-5-2025, the successor, where the quotation above was re-verified verbatim.] https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-8-5-2025 · retrieved 2026-08-09

reliability-offline-feature-matrix

Upheld and strengthened. The vendor makes an affirmative blanket claim of 'full functionality' offline while its own KB exposes only an on/off Offline Mode toggle that ships disabled by default. A blanket claim, plus a default-off toggle, plus reviewer reports of terminal-to-terminal communication failures is the worst combination for an offline-is-a-feature buyer. https://www.lingapos.com/solutions/linga-pos · retrieved 2026-08-01 adversarially verified

reliability-public-status-page

status.lingaros.com resolves to a Zoho StatusIQ instance that returns the error 'No status page found with this domain mapping' - the host is provisioned but no status page is published on it, and no login prompt is shown. The lingapos.com footer's complete link inventory (Solutions, Business Types, Pricing, Partners, Company, Legal - Privacy Policy / Sales Terms and Conditions / End User License Agreement / Cookie Policy - and Resources: Contact Support, Blog, Downloads, Media Center) contains no status or trust page, and lingapos.com/contact-support enumerates the support routes as 'Live Chat, Phone, and Email' with regional phone numbers (US 1-833-MY-LINGA, Australia, Canada, Turkiye, India) and links no status page. No public, per-component status page with current and historical incident state exists. https://status.lingaros.com/ · retrieved 2026-08-07

reliability-247-live-support

Linga states on its first-party solution and business-type pages, verbatim and repeatedly (full-service restaurant page, kiosk solution page): 'We provide 24/7 technical support through multiple channels including phone, email, and chat.' Phone is explicitly one of the channels. Shortfall: this is a page written to sell, not a support policy - lingapos.com/contact-support lists regional support numbers (US 1-833-MY-LINGA / 1-833-695-4642, plus Australia, Canada, Turkiye, India) and the channels 'Live Chat, Phone, and Email' but publishes no hours and no coverage commitment; the Sales Terms and Conditions define no support hours, service levels or support tiers at all, so neither the '365' half of the claim (holiday coverage) nor inclusion in the base subscription versus a premium tier is documented anywhere. No SLA, response-time target or escalation path is published. https://www.lingapos.com/restaurant/full-service · retrieved 2026-08-07

reliability-onsite-install differentiator

Quote: "If Customer requests LINGA to perform the Professional Services at any Customer sites, LINGA agrees to comply with any of Customer's policies and procedures related to the use of, or access to, such sites (including work health and safety and security policies) specified in the Agreement." Appendix C contemplates LINGA (or its approved service provider / subcontractor) performing implementation Professional Services at the Customer's site on request, with travel billed back - so on-site work is an offered, contractually-framed option rather than remote-only. Shortfall: it is on request and travel-reimbursed, the default location is LINGA's own facility, and no page describes a standard on-site go-live engagement, a dealer network that performs installs, or what an on-site visit includes; the General Terms also make the Customer 'solely responsible for preparation and maintenance of its site(s)'. Grade B legal text; no KB article describes on-site installation. https://www.lingapos.com/sales-terms-and-conditions · retrieved 2026-09-03 adversarially verified

reliability-menu-build-service differentiator

Online ordering documents "Upload, test, and manage menus with guided support." Whether Linga performs the initial menu build as part of onboarding is not stated, and reviewers report going live with little training. https://www.lingapos.com/solutions/online-ordering/ · retrieved 2026-08-01

reliability-hardware-replacement-sla

The published Sales Terms and Conditions provide a hardware warranty: 'LINGA warrants that from the sale of the Hardware and for a period of twelve (12) months thereafter, such Hardware will be materially free from defects in material and workmanship under normal use and operation for its intended purpose.' On a valid defect claim LINGA will replace or refund at its own discretion, and the customer has 14 days post-delivery to inspect and reject nonconforming hardware. Shortfall: the remedy carries no stated turnaround time, no shipping or downtime commitment, and no advance-exchange or hot-spare program - replacement versus refund is expressly LINGA's election, so the merchant cannot rely on getting a working terminal back within any defined window, and no purchasable expedited-replacement tier is offered in the terms or on any pricing page. https://www.lingapos.com/sales-terms-and-conditions · retrieved 2026-08-07

reliability-pci-dss-4-attestation

Marketing asserts "100% PCI Compliant" and "Always PCI Compliant" with processing "to the highest standards." No AOC, no PCI DSS version cited, no P2PE listing, no trust center. https://www.lingapos.com/solutions/linga-pay/ · retrieved 2026-08-01

reliability-mfa-role-based-access

Role-based permissions across a franchise hierarchy documented, and user role management exposed via API. MFA enforcement on back-office or POS admin logins not documented. https://lingapos.com/restaurant/franchise · retrieved 2026-08-01

reliability-self-serve-training

A public, login-free knowledge base exists at support.lingaros.com with Hardware Requirements, Release Notes, User Management and POS Operations sections. No video/LMS library and no terminal training mode located; reviewers cite documentation gaps. https://support.lingaros.com/portal/en/home · retrieved 2026-08-01

reliability-failover-terminal-role differentiator

Read POS: Offline Mode (support.lingaros.com/portal/en/kb/articles/pos-offline-mode-8-5-2025), which is the only article that describes the multi-terminal architecture - it refers to POS 'nodes' synchronising through a redis server and states that when that link stops 'the checks made from one POS node will not be reflected in other nodes', but it designates no master, primary or server terminal and describes no role reassignment. Also walked the Hardware and Networking section (Bluetooth Scanner, POS Terminal Requirements, Hardware Requirements, Domain) and read POS Hardware Requirements in full - it covers only device OS/RAM minimums for iPad, Android and Windows and explicitly is not a complete hardware or network specification - plus the Back Office Store Payment Settings and the Linga rOS API reference, which has no node-role or cluster endpoints. Because Linga documents no designated primary terminal or local server role in the first place, neither the presence nor the absence of automatic role takeover is established; the terminal-to-terminal isolation documented for internet outages is a different failure mode from primary-terminal failure.

reliability-cellular-backup

Read POS Hardware Requirements in full (support.lingaros.com/portal/en/kb/articles/pos-hardware-requirements): it gives 'the minimum hardware requirements for operating Linga POS' as iPad models from 2019-2020 onward (iPad 10.2", iPad Mini, iPad Air, iPad Pro; 'Linga POS is currently unavailable on iPhone'), Android with 4 GB RAM / 8 GB storage / Android 11 or above, and Windows 11 with Google Chrome - and covers no network, connectivity or peripheral requirements at all, so it cannot carry an enumeration argument. Also walked the rest of the Hardware and Networking section (Bluetooth Scanner, Domain, POS Terminal Requirements - whose leaf article 404s at /kb/articles/pos-terminal-requirements) and the four POS: Offline Mode articles, which describe a 15-minute connectivity poll and local store-and-forward but never an alternate WAN path. Neither the support portal nor developer.lingapos.com nor lingapos.com mentions cellular, LTE, 4G/5G, dual-WAN or automatic connectivity failover for terminals, in either direction.

commercial-month-to-month-contract differentiator

No month-to-month tier is published. The documented flagship plan requires "a 3-year Merchant Processing Agreement and 3-year LINGA SaaS commitment." Two other payment plans are referenced without terms. https://lingapos.com/payment-plans · retrieved 2026-08-01

commercial-no-early-termination-fee differentiator

Linga's publicly posted Sales Terms and Conditions impose an early termination charge rather than disclaiming one. For customers in the Complimentary Hardware Program the Cancellation Fee is graduated by elapsed term: 100% at 0-3 months, 75% at 4-6 months, 50% at 7-9 months, 25% at 10-12 months, and 0% after 12 months - and the terms characterise it explicitly: 'The parties agree that the Cancellation Fee is not a penalty but is a reasonable amount of liquidated damages to compensate LINGA for termination expenses.' The same program requires maintaining Hybrid Payments Merchant Processing across a three-year term. No clause anywhere in the terms or the EULA states that cancelling the software subscription before term end is free of charge, so the published terms affirmatively contradict the claim. https://www.lingapos.com/sales-terms-and-conditions · retrieved 2026-08-07

commercial-autorenew-terms-published

Publicly accessible terms do state the auto-renewal structure: 'After the termination date provided in the Sales Order or the initial term provided under this paragraph, the Sales Order will automatically renew for successive terms equal in duration ... unless one party gives the other party written notice of non-renewal prior to the end of the Initial Order Term or any Renewal Order Term', with the agreement running 'until the expiration or termination of all Sales Orders'. The cancellation channel is also published: 'Notice of Termination by Customer must be provided using the Cancellation Request Form which may be accessed at [https://lingapos.com/forms/partner-cancel-request/]'. Shortfall: the required notice window carries no number - there is no 30/60/90-day figure, only 'prior to the end of' the term - and the initial term length itself is set in the per-customer Sales Order and is not published, so a buyer cannot determine from public terms how long the renewal locks them in or by when they must act. The related Complimentary Hardware Program is separately documented as a three-year commitment. https://www.lingapos.com/sales-terms-and-conditions · retrieved 2026-08-07

commercial-processing-not-bundled differentiator

The Back Office EMV Payment Settings screen configures card acceptance against third-party devices/processors: the mandatory Type dropdown enumerates SP-PAX (Serial Number plus a Go Device toggle), OPTOMANY (port), INGENICO (port), CLOVER (port), MONERIS (port and Device Type), EVERTEC (port and Terminal ID) and DEJAVOO (Auth Key, TPN and Token), each configured with a Name and IP Address; nothing on the screen or in the Payments settings section states that only Linga or Hybrid Payments processing is permitted. Shortfall: commercially the flagship path is locked - the published Sales Terms require Complimentary Hardware Program customers to maintain 'Hybrid Payments Merchant Processing' as part of a three-year term commitment, with a 100/75/50/25 percent graduated cancellation fee if they exit early, so the third-party-processor route is available only to buyers who forgo the marketed hardware-inclusive plan. Note the vendor's owner, PNC, has a direct merchant-services interest. Also note: 'The Type and supporting fields of an existing EMV cannot be edited' after creation. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-emv-payment-settings · retrieved 2026-08-07

commercial-interchange-plus-published differentiator

Linga Pay publishes no processing pricing of any kind — neither blended card-present rates nor an interchange-plus markup in bps plus per-transaction terms. https://www.lingapos.com/solutions/linga-pay/ · retrieved 2026-08-01

commercial-rate-increase-clause differentiator

Read the full published Sales Terms and Conditions (lingapos.com/sales-terms-and-conditions) and the End User License Agreement (lingapos.com/end-user-license-agreement). Neither contains a rate-increase cap, a notice requirement for fee changes, a pass-through-only limitation, or a penalty-free-exit-on-increase right; the Sales Terms instead run the other way, referencing a three-year Hybrid Payments Merchant Processing commitment for Complimentary Hardware Program customers and a graduated cancellation fee expressly framed as liquidated damages. Crucially, the claim is about the processing agreement, and the Hybrid Payments Merchant Processing Agreement itself is a separate document that is not published anywhere on lingapos.com - the Sales Terms only reference it. Also checked lingapos.com/merchant-account, which publishes no rates, no rate-lock guarantee and no contract terms, and lingapos.com/pricing and /pricing/plans, which render client-side and returned only navigation markup. The absence of a cap in the SaaS terms is therefore not an enumeration of the processing agreement's contents.

commercial-pricing-published

All three pricing URLs (/pricing, /pricing/plans, /payment-plans) render navigation and a sales CTA with no dollar figures, directing visitors to contact a sales representative. The only figure in circulation is a $29.99/user/month starting price on third-party Gartner-network listings, not a Linga rate card. https://lingapos.com/pricing · retrieved 2026-08-01

commercial-module-unbundling differentiator

Quote: "Addons Per Station and Addons Per Site will be available for Pro plan and customer can add addons according to the requirement and pricing will be calculated and displayed in the billing screen on the right side." A la carte purchase is documented at grade B: add-ons are bought individually per station or per site from Manage Plan with separate line-item billing, and other articles confirm module-level licences (Integration Hub 'Enter the number of licenses (quantity)'; 'OLO addon license ... purchased and enabled under account license settings', March 2025; 'Text add-on in Account License settings must be purchased and enabled', 26-04-001). The article says 'Use cases will be identical between POS and Retail'. Shortfalls that keep it partial: (1) independent cancellation is not documented - 'Removing Cancel Subscription from Old Backoffice' (Nov 2024) and 'When Upgrading your Account (or changing Addons), an Email will be sent to the Billing Team to assist you' (Oct 2025) route add-on changes through billing staff; (2) whether the base subscription is repriced on removal is not stated; (3) several modules are plan-bundled rather than separable ('Addons like Insights , Inventory and Stock will be included with a Pro Plan'; 'the Marketing module is included at no charge for Accounts with the Loyalty addon'), and downgrading a plan strips add-ons ('Some of your addons are not available in your new plan'). https://support.lingaros.com/portal/en/kb/articles/retail-back-office-subscriptions-upgrades-summary · retrieved 2026-09-03 adversarially verified

commercial-hardware-purchase-outright

The published Sales Terms and Conditions establish outright purchase as the default hardware structure: 'Unless otherwise set forth in the Sales Order, title to the Hardware shall transfer to Customer upon sale of the Hardware' - a sale with title transfer, not a lease or rental - backed by a twelve-month defect warranty and a 14-day post-delivery inspection/rejection right. Shortfall: the claim's 'at a published price' half fails. No hardware prices are published - lingapos.com/pricing and /pricing/plans render client-side and disclose no figures, /merchant-account names tiers (Starter, Basic, Pro, Enterprise, Custom) without prices, and no terminal, KDS screen or printer price appears on any retrievable Linga page - so hardware cost is quote-only. The heavily marketed alternative is the Complimentary Hardware Program, which is not a purchase at all: it requires maintaining Hybrid Payments Merchant Processing over a three-year term and carries a graduated cancellation fee (100% at 0-3 months down to 0% after 12) framed as liquidated damages. https://www.lingapos.com/sales-terms-and-conditions · retrieved 2026-08-07

commercial-hardware-not-locked differentiator

The POS Hardware Requirements article states 'These specifications outline the minimum hardware requirements for operating Linga POS' and lists non-proprietary consumer devices as the terminal: iPad models from 2019-2020 onward including iPad 10.2", iPad Mini, iPad Air and iPad Pro variants (with the note 'Linga POS is currently unavailable on iPhone'); Android devices with at least 4 GB RAM, 8 GB storage and Android 11 or above; and Windows 11 machines running Google Chrome with 8 GB RAM minimum. None of these are vendor-supplied devices - a merchant can run Linga POS on a stock iPad or a generic Windows PC. Corroborating this on the peripheral side, the Back Office EMV Payment Settings Type dropdown configures third-party payment terminals by brand (SP-PAX, OPTOMANY, INGENICO, CLOVER, MONERIS, EVERTEC, DEJAVOO), and the section carries a separate Bluetooth Scanner article. Note the article covers device OS minimums only and does not enumerate printers or cash drawers, so the specific ESC/POS printer and generic-drawer examples in the claim are not individually confirmed. https://support.lingaros.com/portal/en/kb/articles/pos-hardware-requirements · retrieved 2026-08-07

commercial-data-export-self-serve

Insights allows users to "easily download or email insights" — report-level export. Self-serve export of full transactional history (orders, line items, payments, labor) not documented. https://lingapos.com/solutions/insights · retrieved 2026-08-01

commercial-export-customer-and-loyalty differentiator

The Back Office Customer Info screen carries a top-right 'Export' button that 'downloads customer data in selected file format', and the customer table it exports from has columns Image, Name, Email, Phone Number, Loyalty Points ('Current balance'), Reason ('Loyalty points update notes'), Gift Card Number, Stores and Actions - so guest records with loyalty balances and assigned gift-card numbers come out together in a machine-readable file. Back Office: Exporting Reports documents the format options as 'XLSX (excel file), CSV ... or PDF' with Direct Download or email delivery, and the Back Office Gift Card Report lists per-card rows with 'Card Number, Business Date, Transaction Date, Employee, Sale Number, Node, Activity Type, Sold In, Amount' and 'Balance', plus a Give X tab. Shortfall: the Gift Card Report article documents no Export control of its own and shows no aggregate outstanding gift-card liability figure - only per-card balances and activity rows; and loyalty comes out as a current point balance, not a point ledger, with the transaction-level loyalty history visible only in the per-customer Customer Metrics view rather than in a bulk export. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-customers-customer-info · retrieved 2026-08-07

commercial-post-termination-export-window differentiator

The published Sales Terms and Conditions specify the opposite of a retrieval window: 'Upon expiration or earlier termination of this Agreement, the Services and Customer's right to access and use the Services ... shall immediately terminate and cease', and the customer must '(a) immediately stop access and use of all LINGA Items; (b) shall return all copies of LINGA Items to LINGA; (c) delete all LINGA Items off of any and all storage media possessed or controlled by Customer.' No grace period, defined number of days, export-on-request obligation or data-return commitment appears in the termination provisions, and the EULA - the only other published legal document - specifies no post-termination retrieval window either. The terms therefore affirmatively document immediate cutoff rather than a defined export window, which is the condition the claim tests for. https://www.lingapos.com/sales-terms-and-conditions · retrieved 2026-08-07

commercial-data-ownership-clause differentiator

The published Sales Terms and Conditions state ownership explicitly: 'Customer retains all right, title and interest in and to any information or data inputted or stored in the Services by Customer and/or its users.' The vendor's countervailing right is drafted narrowly and is confined to service telemetry plus an aggregate-only disclosure limit: 'LINGA shall have the right to collect and analyze data and other information relating to the provision, use and performance of various aspects of the Services ... and LINGA will be free to (i) use such information and data to improve and enhance the Services and for other development, diagnostic and corrective purposes ... and (ii) disclose such data solely in aggregate or other de-identified form in connection with its business.' The 'solely in aggregate or other de-identified form' limit on disclosure is the constraint the claim asks for - there is no right to sell or disclose identifiable merchant transaction or customer data. The EULA is consistent, permitting only 'aggregated, anonymized statistics regarding the payments and other transactions conducted via the Platform'. https://www.lingapos.com/sales-terms-and-conditions · retrieved 2026-08-07

commercial-pci-p2pe-tokenization

Generic "100% PCI Compliant" claim with an EMV-ready terminal. No validated P2PE solution named, no tokenization architecture described, no applicable SAQ type (SAQ A / SAQ P2PE-HW) stated. https://www.lingapos.com/solutions/linga-pay/ · retrieved 2026-08-01

commercial-pci-dss-4-controls

Quote: "Password Rules – The Password must include: Between 6 and 12 characters An uppercase character A lowercase character A number A Special character (such as !, @, #, or $)" Positive evidence that the specific v4.0.1 controls are not documented as in effect. The complete documented sign-in procedure for POS and Back Office is email + password (then a staff PIN or Face ID at the POS Login screen), with no second factor anywhere in the flow; the password policy is 'Between 6 and 12 characters An uppercase character A lowercase character A number A Special character' (Creating a New User) - a 12-character maximum, below the v4.0 12-character minimum. The only OTPs in the corpus are consumer-facing (OLO/Custom App sign-up email OTP; optional NMI 3D Secure, 26-06-001 'Note: 3D Secure implementation within the NMI iFrame is optional'), not merchant CDE access. No article mentions PCI DSS, MFA, 6.4.3/11.6.1 or payment-page script integrity; the nearest security statement is 26-03-001 'Card data is encrypted at the point of entry ... all activities are monitored to ensure security and compliance'. Flag for the audit: this is 'the documented login procedure has no MFA step' plus a contradicting password rule, not a sentence saying MFA is unsupported. https://support.lingaros.com/portal/en/kb/articles/retail-back-office-user-management-creating-a-new-user · retrieved 2026-09-03 adversarially verified

commercial-privacy-dsar-tooling

The Back Office Customer Info screen gives an operator the three primitive actions a DSAR needs: the customer list is searchable/filterable with Name, Email, Phone Number, Loyalty Points, Gift Card Number and Stores columns; a top-right 'Export' button 'downloads customer data in selected file format'; and the per-row three-dot Actions menu offers Edit Customer, View Customer Metrics, Delete Customer and Edit the Customer's Loyalty Points, with View Customer Metrics showing visit count, sales amounts, loyalty balance, feedback scores and transaction history with receipt breakdowns. Shortfall: deletion is documented as deactivation, not erasure - the confirmation message is 'Customer inactivated successfully' - so the record persists; there is no DSAR-specific workflow, requester verification, deadline tracking or fulfilment audit trail, and no per-guest export distinct from the bulk customer export. On the contract side the Privacy Policy enumerates the GDPR/CPRA rights (withdraw consent, access, rectify, restrict, delete, and receive data 'in structured, machine-readable format') but routes their exercise entirely off-product - requests are 'directed to the Owner through the contact details provided in this document' (linga.global@gmail.com, 4501 Tamiami Trail N, Suite 400, Naples, FL 34103) and 'will be addressed by the Owner as early as possible and always within one month'. No Data Processing Agreement is published, linked or offered in the Privacy Policy, the Sales Terms or the EULA. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-customers-customer-info · retrieved 2026-08-07

commercial-wcag-kiosk-accessibility differentiator

Quote: "ADA Compliance in OLO / Call Center – Ensuring digital platforms are accessible to all users, including those with disabilities, such as proper color contrast with clear and readable content." Linga documents an accessibility effort for its consumer web-ordering surfaces only: 'ADA Compliance in OLO / Call Center' (Oct 2025) and 'ADA Compliance in VRT: Ensuring that digital platforms are accessible to all users, including those with disabilities via proper color contrast, and clear and readable content' (Nov 2025; VRT is the virtual kiosk / web ordering front end). Shortfalls: no VPAT/ACR is published, no WCAG version or level is claimed (the only named criterion is colour contrast), and the physical self-order Kiosk's documentation (Kiosk Addon Settings: payment types, tips, theme, layout, background images; Idle Time Advertisement; configurable receipts) contains no accessibility mode - no tactile keypad, audio/headphone-jack or screen-reader navigation. Present but materially short of the claim on every named element. https://support.lingaros.com/portal/en/kb/articles/october-14th-2025-release-notes · retrieved 2026-09-03 adversarially verified

commercial-dual-pricing-compliant differentiator

Already-documented evidence (payments-surcharge-guardrails, payments-dual-pricing) establishes the compliant core: Surcharge is enabled per store, payment types flagged Debit are force-exempted ("the Exempt Surcharge toggle will automatically be set to YES ... and will be greyed out") with a logged compliance acknowledgment, and Dual Price prints a Cash Subtotal line on the check/receipt disclosing the fee. Shortfall: exemption is documented for Debit specifically, not prepaid cards by name, and no menu-board disclosure requirement (as opposed to receipt disclosure) is documented — only the receipt-level Cash Subtotal line is confirmed. https://support.lingaros.com/portal/en/kb/articles/pos-payment-surcharge-surcharge · retrieved 2026-08-04