Vendors / Mainstream commercial restaurant POS
Linga POS
Linga POS (Linga rOS)
dossier live legacy rubric
- Claims in scope
- 278
- Scored
- 278
- Assessed
- 278
- Unknown
- 0
- Not applicable
- 36
- Values challenged
- 113
Identity
- Owner
- Linga is a wholly owned subsidiary of The PNC Financial Services Group, Inc. (NYSE: PNC), which announced the acquisition on 2022-09-26 (https://investor.pnc.com/news-events/financial-press-releases/detail/360/pnc-announces-acquisition-of-point-of-sale-and-payments-solutions-firm-linga). Deal value undisclosed. The vendor About page itself discloses no parent, which is why the 2026-08-01 first pass recorded ownership as unknown; the verification rows of the same day established the PNC ownership and the field was reconciled on 2026-09-03.
- Parent
- The PNC Financial Services Group, Inc.
- Founded
- 2004, as Benseron Hospitality; renamed Linga in July 2019. Not on lingapos.com/about-us; stated in PNC acquisition release of 2022-09-26 (https://investor.pnc.com/news-events/financial-press-releases/detail/360/pnc-announces-acquisition-of-point-of-sale-and-payments-solutions-firm-linga).
- Scale
- unknown — Linga publishes no customer count, location count, ARR, or market-share figure. The only third-party scale signal located is review volume: 39 verified reviews at 3.4/5 across the Gartner review network (SoftwareAdvice/GetApp), which is small relative to Toast/Square and suggests a modest installed base, but review counts are not a reliable proxy for scale.
- Who it is for
- Small-to-midmarket independents and multi-location/franchise groups across restaurant AND retail. Vendor markets segments including full-service, QSR, pizzeria, coffee, bubble tea, cigar lounges, plus retail verticals (apparel, c-store, liquor, grocery). Franchise page markets 30+ user languages and "worldwide" analysis, consistent with an international footprint. Store-count of a typical buyer is not published.
- Site
- https://www.lingapos.com/
Pricing
transparency: quote-only · unit: unknown · processor lock-in: partial
- Software
- quote-only. Linga's own pricing pages (/pricing, /pricing/plans, /payment-plans) render navigation and a sales CTA but publish no dollar figures; /payment-plans directs visitors to "contact a LINGA sales representative." The only dollar figure located anywhere is a vendor-supplied starting price of $29.99/month per user listed on the Gartner review network (SoftwareAdvice and GetApp both show it). That is a third-party listing field, not a published Linga rate card, and it is a floor price with no tier detail — do not treat it as the real cost of a configured system.
- Card processing
- unknown — Linga Pay's own product page publishes no rate, no flat rate, and no interchange-plus markup. It advertises capability (EMV, NFC, Apple Pay, QR payments, same-day funding, "100% PCI Compliant") without price.
- Contract
- 3 years, documented for the flagship plan. Linga's /payment-plans page states the "Complimentary Hardware Plan" requires "a 3-year Merchant Processing Agreement and 3-year LINGA SaaS commitment." The page references three payment plan options; terms for the other two are not published. No month-to-month tier is published anywhere on the site.
- Early termination
- unknown — no terms of service or MSA was locatable at the conventional URLs (/terms-of-service and /terms-and-conditions both 404). Given a documented 3-year dual commitment, an ETF or liquidated-damages clause is plausible but is NOT established; treat as unknown.
API posture
public API: partner-gated
- Cost to integrate
- unknown — no partner fee, revenue share, or certification cost is published. The API agreement text itself is not publicly readable.
- Webhooks
- unknown — no webhook documentation, signing scheme, retry policy, or event catalog was locatable.
- Data export on exit
- unknown — no post-termination data retrieval window, export format, or data-ownership clause was locatable; the terms pages 404 at conventional URLs.
- Notes
- Documented API surface is narrow and read/write scope is unclear. The developer-partner page enumerates exactly four API areas: "menu item arrangement & categorization, online ordering, device syncing, user role management." Notably absent: payments, labor/timecards, and inventory. No evidence of OAuth 2.0 scoped authorization, no published rate limits, no sandbox, no changelog or deprecation policy. For an integration-heavy buyer this is the weakest area in the dossier — Linga leans on middleware (Deliverect, Chowly) and named point integrations rather than a self-serve platform API.
Capabilities
Every claim is binary and checkable. Grades: A primary documentation · B product documentation · C pricing or feature page · D marketing claim · E third-party reporting · F inference with no source. A yes on a differentiator claim requires A or B.
Order capture & FOH workflow
Provides a graphical floor-plan editor where an operator can draw sections, place tables of varying shape/capacity, save multiple floor-plan layouts per location, and assign sections to servers.
order-capture-floor-plan-editor
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 lines can be tagged to a seat number at entry, and the check can be split by seat afterward without re-keying items.
order-capture-seat-level
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
Items can be assigned to courses and held, with a fire-next-course action available from a handheld or terminal that releases only that course to the kitchen.
order-capture-coursing-hold-fire
"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
Supports splitting a check by item, by seat, by even N-way, and by arbitrary dollar/percentage amount, and merging checks or tables back together, including after partial payment.
order-capture-split-merge
"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
Opens a bar tab against a card pre-authorization with a configurable auth amount, supports incremental re-auth as the tab grows, and auto-closes stale tabs at end of day. differentiator
order-capture-bar-tab-preauth
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
An open check can be transferred between servers, tables, and devices, and the transfer is recorded in an audit log naming both employees.
order-capture-transfer-audit
"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
Ships a first-party handheld ordering app running natively on the handheld device (not a remote/mirrored desktop session) that can send to kitchen and take a card payment tableside.
order-capture-native-handheld
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
With the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen, and tender cash, and the vendor publishes what does and does not work offline.
order-capture-offline-order-entry
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
Guest QR at-table ordering writes items onto the same open check as server-entered items, rather than creating a separate order ticket. differentiator
order-capture-qr-same-check
The record's prior rationale said no QR-menu-ordering article exists; it does. 'QR Code for Virtual Kiosk' documents the whole flow: QR codes are generated per table (Settings > Store > Table Layout > Print QR Code), the guest's OLO order is attached to that table and 'Orders can be displayed on IPAD screen by touching the related table on table layout screen', and the order object is shared both ways - 'New items can be added to an existing order through Online Ordering (by tapping the Add More button and selecting new items) or IPAD app'. Named shortfall keeping this off yes: the same article's 'Multiple Orders From the Same Table' section says 'Each person joining the table places their own order by scanning the QR Code of the table', i.e. several guests at one table produce several orders rather than one shared check. Capture 2023-02-09. ARCHIVE CAVEAT (203rd): support.lingaros.com serves a byte-identical 25,169-byte SPA shell for every path today and its Help Center API 401s on the portal's own orgId, so this article body was read from the Wayback capture named in the URL. https://web.archive.org/web/20230209030341/https://support.lingaros.com/portal/en/kb/articles/qr-code-for-virtual-kiosk · retrieved 2026-09-04
Offers a first-party self-order kiosk that renders the same menu and modifier tree as the POS with no separate menu build, and the vendor documents ADA/accessibility conformance for it. differentiator
order-capture-kiosk-first-party
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
Supports drive-thru-specific order flow: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment.
order-capture-drive-thru
329th: the corpus was RE-DERIVED, not inherited, and the census is CURRENT. The Zoho portal listing API (support.lingaros.com/portal/api/kbArticles, the publisher's own listing) was re-paged today and returns 618 articles - the same 618 as the 323rd - and all 618 bodies were re-fetched, so the 3,915,973-char corpus (618 KB articles + the 137-page www href fixpoint + 44 developer.lingapos.com pages) is the vendor's complete published surface as of 2026-09-18 and has NOT grown. CONTROLS re-run first-hand over those 3,915,973 chars (tokenised, word-boundary, case-insensitive; `drive[\s-]?thru` written with a double backslash after checking the heredoc trap): 'order point' 0, 'pay window' 0, 'pickup window' 0, `pull[\s-]?forward` 0, 'lanes' 0, 'stall' 0, 'menu board' 0 - i.e. EVERY conjunct of the claim scores zero. POISON NAMED: 'lane' 6 is the 'LANE 1 OPEN / LANE 2 OPEN / EXPRESS LANE OPEN' graphic on the retail liquor-store page (3 pages x 2 copies), never a drive-thru lane; 'tandem' 1 is the prose 'online ordering and kiosk technology working in tandem'; 'parking' 3 are courier statuses ('Delivery supplied parking details', 'Driver has reached the store and spotted at parking location') and the 'Park Sale' pop-up (parking a CHECK, not assigning a parking spot); `drive[\s-]?thru` 3 = the curbside sentence twice plus one payments blog. NEW SURFACE 2026-09-18: the vendor's App Store publisher census, itunes.apple.com/lookup?id=662556954 (BENSERON INFORMATION TECHNOLOGIES INC.) = exactly 5 apps, the complete Linga app family: LINGA POS (id 1105717161, v5.4, 2026-04-21), Linga Insights, Linga SC, Linga Customer Display, Linga Driver. The LINGA POS screenshots read at full resolution (mzstatic /1000x0w.png) show the POS's own top-level order-surface tab bar - 'Check Stats | Table Layout | BarTab | Phone Order' - and, on the Delivery Dispatch screen, the complete order-type filter row 'All | DELIVERY | For Here | To Go | Web | Paid | UnPaid' over a Type column reading ToGo / DELIVERY / FORHERE. No drive-thru surface, order point, window or lane appears in either enumeration. (Caveat: the screenshots embed 'Version: 2.0.3.6' while the shipping app is 5.4, so they corroborate rather than bound; they are vendor-authored, grade C.) VERDICT: no. The claim is a conjunction of order-point/pay-window/pickup-window separation, lane sequencing or tandem-lane assignment, and pull-forward/parking-spot assignment; all three are absent from a bounded, re-derived census of the vendor's complete documentation, and the sibling cell hardware-drive-thru is already a `no` on the complete supported-device enumeration in pos-hardware-requirements - a POS with no drive-thru hardware and no window/lane construct anywhere. The surviving marketing sentence ('Contactless curbside pickup and drive-thru let guests pick up orders from their vehicles') asserts a vehicle PICKUP mode and evidences none of the three conjuncts; it is a homonym of the claim's drive-thru FLOW, which is why this now reads no rather than unknown. Retrieved 2026-09-18. https://support.lingaros.com/portal/en/kb/linga-pos/pos · retrieved 2026-09-18 adversarially verified
Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.
order-capture-drive-thru-timers
329th: same re-derived, still-current census as order-capture-drive-thru (Zoho portal listing API re-paged 2026-09-18: 618 articles, unchanged; 618 bodies re-fetched; 3,915,973 chars with the 137-page www fixpoint and 44 developer pages). CONTROLS re-run first-hand: 'speed of service' 0; 'timer' 5 and 'timers' 1 and 'elapsed' 3 - and every one is accounted for: 4 of the 5 'timer' hits are the POS receipt-delivery screens' auto-close 'countdown timer' ('the receipt has been sent via text message screen appears ... A countdown timer will appear at the bottom for the screen to auto-close'), the 5th and all 3 'elapsed' hits are the Table Layout 'Order Elapsed Time - How long since the order was started [HH:MM]', and 'timers' 1 is the KDS release note 'maintaining existing KDS behaviors such as bumping, timers, and completion tracking'. POISON NAMED: a countdown to dismiss a receipt screen, a single order-open clock on the table map, and KDS colour/bump timers are none of them a drive-thru segment timer, and none is broken into order/total/window segments. The 25 enumerated Back Office report families contain no speed-of-service, drive-thru or segment-time report. NEW SURFACE 2026-09-18: Linga Insights (App Store id 1416560938), the vendor's own mobile reporting app, screenshots read at full resolution - the My Stores dashboard exposes exactly four per-store measures, NET SALES / TAXES / DISCOUNTS / VOID, with no service-time measure (vendor-authored, grade C, corroborating). VERDICT: no. There is no drive-thru flow in the product to time (order-capture-drive-thru is now no on the same census) and no segment speed-of-service capture or report exists anywhere in the vendor's complete published documentation. Retrieved 2026-09-18. https://support.lingaros.com/portal/en/kb/linga-pos/back-office/reports · retrieved 2026-09-18 adversarially verified
Vendor ships a first-party AI voice ordering agent for phone and/or drive-thru that injects orders directly as POS orders, or publishes a documented API partner program for third-party voice AI. differentiator
order-capture-voice-ai
P4 retested and holds: the sitemap's 21 /solutions/* pages are all in the corpus and are the vendor's complete published product set, and the footer's own 22-item Solutions enumeration repeats that set on every page. No voice-AI product is among them, and Linga's phone-order product is explicitly human-staffed: agents 'place orders directly into your point of sale system'. 'voice' appears in the corpus only in blog SEO prose and 'artificial intelligence' zero times. On the second disjunct: Linga publishes a developer partner program, but nothing in the 44-page reference is a voice-AI partner program - the API agreement page renders client-side and is empty chrome, so nothing is read out of it. AUDIT (2026-09-04): The stated basis is overstated - the 21 /solutions/* pages are NOT the complete product set (the developer-docs footer lists Linga C-Kitchen and Linga Alerts, absent from the 21) - but the verdict does not need that enumeration. It rests on positive contradiction: Linga's own phone-ordering product page asserts live human operators who 'place orders directly into your point of sale system'. And the marketing-necessity test answers yes more clearly here than for any other capability class: 'artificial intelligence' occurs zero times corpus-wide as a product claim while the blog demonstrably chases AI SEO topics - a vendor writing AI content that omits its own AI voice agent is not plausible. https://lingapos.com/solutions/call-center-system-for-restaurants · retrieved 2026-09-04
Supports order throttling: per-channel capacity limits per time slot with automatic quote-time extension when kitchen load exceeds a configured threshold. differentiator
order-capture-throttling
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
Accepts future-dated/scheduled orders with a per-channel lead time and automatically injects them into the make queue at a computed fire time rather than on receipt.
order-capture-scheduled-orders
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
Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.
order-capture-catering
CLAIM: Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue. VERDICT: no. EVIDENCE: The strongest zero in this vendor: 'cater(ing|er|ers)' scores 0 across the whole 3.94 MB corpus - 618 KB articles, 137 marketing pages (which include eight restaurant-type pages and nine retail-type pages) and 44 developer pages. The order-type vocabulary that IS present is the enumerated alternative: Dine In, Take Out, Delivery, Pickup, Curbside Pickup, Bar Tab, Web Order, ASAP and Future Orders. Adjacent constructs exist but are not catering: 'deposit(s)' 86 are bottle/container deposits and till deposits; 'quote(s)' 3 are 'Base Quote Time' prep and delivery minutes; Future Orders is scheduling, with no event schedule, minimum, proposal or balance-due tracking attached. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://lingapos.com/restaurant/full-service · retrieved 2026-09-17 adversarially verified
Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator
order-capture-order-ready-signal
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
Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.
order-capture-void-comp-controls
Role-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, modifiers & pricing engine
Payments & money movement
The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator
payments-processor-choice
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
Vendor publishes card-processing pricing publicly (a specific flat rate or interchange-plus markup) rather than quote-only. differentiator
payments-published-rates
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
Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator
payments-dual-pricing
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
Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator
payments-surcharge-guardrails
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
All first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay.
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
Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. differentiator
payments-softpos-tap-to-pay
CLAIM: Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. VERDICT: no. EVIDENCE: Same two enumerations as hardware-tap-to-phone and they are decisive here too: "Linga POS is currently unavailable on iPhone" (pos-hardware-requirements), and the card-reader screen offers only networked EMV devices addressed by IP plus Bluetooth Edynamo/Tdynamo readers - a reader is always in the path. The five 'tap to pay' hits in the corpus are all terminal contactless on the quick-service and LINGA Go pages ("Process credit cards, tap to pay, and more", "Support Apple Pay, Google Pay, and tap to pay"), and the LINGA Go FAQ answers the hardware question directly: "Is there any specific hardware required? LINGA Mobile, LINGA Tablet, or a compatible Android device is required." Tokenised 'softpos|tap to phone|tap on phone' 0 across 3.94 MB. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://support.lingaros.com/portal/en/kb/articles/pos-operation-card-reader-hardware-settings · retrieved 2026-09-17 adversarially verified
Vendor ships a handheld that takes EMV/NFC payment at the table, including tip prompt and check splitting, without carrying the card away.
payments-pay-at-table
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
Guest can scan a QR code on the printed check or table tent to view and pay the check from their own phone, with the payment closing the check in the POS automatically. differentiator
payments-qr-guest-pay
"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
Supports both pre-auth-then-tip-adjust and on-device tip prompt flows, with a documented batch/adjust window and a manager screen for unadjusted tips.
payments-tip-adjust
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
Configurable tip pooling and distribution rules (by hours worked, sales, role percentage, or points) that produce a per-employee tip allocation exportable to payroll. differentiator
payments-tip-pooling
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
Card payments can be captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. differentiator
payments-offline-store-and-forward
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
Vendor publicly documents who bears the loss when a stored offline transaction declines on reconnect, and surfaces a post-reconnect report of failed offline payments. differentiator
payments-offline-decline-liability
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
First-party gift cards with real-time balance tracking, redeemable across every location in the group and through the online-ordering channel.
payments-gift-cards
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
House/on-account tabs with per-account credit limits, running balance, and periodic statement or invoice generation.
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
A single check can be settled with multiple tenders and split by seat, by item, by even shares, or by arbitrary amount, with no hard cap below eight ways.
payments-split-tender
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
Voids, refunds, discounts, and no-sales require role-based authorization (manager PIN or approval) and write to an immutable audit log identifying the approver.
payments-refund-void-controls
"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
In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator
payments-chargeback-tooling
CLAIM: In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission. VERDICT: no. EVIDENCE: Tokenised controls over the whole 3.94 MB corpus: 'chargeback(s)' 0, 'representment(s)' 0, 'retrieval request' 0, 'dispute(s)' 5 - and all 5 dispute hits are the arbitration clause and the payment clause of the General Terms ("such dispute shall be resolved exclusively through final and binding arbitration"; "Any dispute between LINGA and Customer over the performance and service of the Services shall not serve as grounds for the customer to not pay"), none a payments feature. The Back Office is documented screen by screen in the KB (the back-office-2024-* article family), including EMV Payment Settings and the 25 report families, and no dispute/chargeback screen or report appears in any of them. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-emv-payment-settings · retrieved 2026-09-17 adversarially verified
Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator
payments-card-on-file
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
Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator
payments-payout-timing
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
Vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance / P2PE listing available to merchants on request.
payments-p2pe-pci4
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 & production
Items route to specific KDS stations by item, category, order type, or revenue center, with routing rules configurable per location without vendor involvement.
kitchen-station-routing
"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
An expo screen consolidates items from multiple prep stations into a single order view and only marks the order complete when every contributing station has bumped its items.
kitchen-expo-consolidation
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
Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator
kitchen-course-firing
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
Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator
kitchen-prep-time-pacing
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 load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator
kitchen-order-throttling
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
Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator
kitchen-channel-pause-propagation
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
Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator
kitchen-order-ready-callback
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
KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.
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
An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.
kitchen-all-day-counts
CLAIM: An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station. VERDICT: no. EVIDENCE: ENUMERATION: back-office-2024-kds-configuration-template-settings is the KDS Configuration screen and lists every field option it ships (Table Name, Check Number, Time, Server Name, Service Type, Seat Number, Notes, KDS Done Button, Horizontal View for Modifier, Disable KDS Broadcast) plus Style Options and SMS Order Notifications - there is no all-day / item-summary view among them. Tokenised controls over the whole corpus: 'all[\\s-]?day' 0, 'prep list(s)' 0, 'quantity view' 0, 'summary view' 0. The KB's kitchen vocabulary is present and positive - 'Expo KDS view', Sequential Flow ("items will become visible on the next screen only after the previous screen bumps the order"), bump, recall, timers - so the absence is measured against a corpus that does discuss the KDS in detail. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-kds-configuration-template-settings · retrieved 2026-09-17 adversarially verified
Configurable target cook times per station or order type, with visual color escalation and/or audible alert when a ticket exceeds target.
kitchen-sla-alerts
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
If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator
kitchen-printer-fallback
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
KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator
kitchen-offline-operation
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
Station screens can display item-level build/assembly detail (recipe steps, portioning, or full modifier breakout) rather than only the ticket line text. differentiator
kitchen-item-build-screens
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
Sectioned/fractional topping placement (halves, quarters, specific sections) is rendered visually and unambiguously on the make-line screen or ticket. differentiator
kitchen-pizza-fractional-display
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
A bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order.
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
Edits made in the POS to an order already displayed in the kitchen visually flag the added, changed, or removed items on the live ticket. differentiator
kitchen-order-modification-alerts
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
Bumping an order ready triggers a guest-facing notification — SMS/text, app push, or an order-status display board — without a separate product purchase. differentiator
kitchen-guest-ready-notification
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
Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.
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
Reports actual ticket and per-station times (average and percentile) sliced by daypart, station, and order channel, exportable to CSV or an API.
kitchen-speed-of-service-reporting
Back Office: Home (Zoho Desk KB, modified 2026-04-13), KDS dashboard tab: "Avg Time Per Check ... Displays the Average amount of Time Per Check, from opening to closing, during the selected Time Period"; its table "contains the Orders broken down by Kitchen Area along with their Avg Time for KDS and EXPO"; an "Avg Time Per Item" tile gives "the Average Time it took to prepare an Item" with Preparation Time (minutes) per item, and a "Time Vs Kitchen Display System" chart shows "amount of Time by Kitchen locations". So average ticket time per station (kitchen area and expo) is reported. Not to be confused with the Summary tab's "Avg. Time per Check", which is a sales-derived formula. SHORTFALL: averages only, no percentiles; sliced by kitchen area over a selected time period only, with no daypart or order-channel breakdown; no CSV or API export is documented for these figures - it is a dashboard tab, not an exportable report. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-home-9-1-2025 · retrieved 2026-09-12 adversarially verified
Generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list.
kitchen-prep-forecasting
CLAIM: Generates prep lists or predicted prep quantities from historical sales and forecast demand. VERDICT: no. EVIDENCE: Tokenised: 'forecast(s|ing|ed)' 23 hits, ALL 23 in www marketing/blog prose about the industry ("Advanced AI-driven forecasting methods have been shown to reduce excess stock", "Predictive tools also help forecast demand") and ZERO in the 618-article KB, which is where every shipped Back Office screen is documented. 'prep list(s)' 0, 'par level' 25 (all KB, and all the inventory Low Stock / par threshold screen, which is reorder-point stock control, not a predicted prep quantity). No prep-forecasting screen or report exists in the Back Office documentation. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://lingapos.com/solutions/inventory-management · retrieved 2026-09-17 adversarially verified
Delivery, dispatch & third-party channels
Product includes a native in-house driver module: drivers are first-class entities with clock-in/out, assignment state (in-store / on-run / returning), and per-driver run history reportable from the POS itself (not via a third-party add-on).
delivery-driver-roster
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
Provides a dedicated dispatch/expo screen showing undispatched orders, driver availability, and elapsed time per order, with multi-order run batching (assigning 2+ orders to one driver as a single run).
delivery-dispatch-board
"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
Dispatch includes a live map view with geocoded stops and system-generated route sequencing (turn order optimization) for a multi-stop run, not just a static address list. differentiator
delivery-route-map
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
Captures live driver GPS position from a driver-facing mobile app and surfaces it back to the dispatch screen. differentiator
delivery-driver-tracking
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 areas can be defined as arbitrary map polygons or by drive-time isochrones, not solely as a radius or a ZIP/postcode list. differentiator
delivery-zones-polygon
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
Each delivery zone carries its own independently configurable delivery fee, order minimum, and quoted promise time, applied automatically from the validated customer address.
delivery-zone-pricing
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
Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.
delivery-address-validation
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
Tracks per-delivery driver compensation inputs — mileage or distance driven per run, per-delivery flat reimbursement, and driver-retained tips — and exports them to payroll as separate reimbursement vs. wage lines. differentiator
delivery-driver-comp
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
Provides a driver cash bank / settle-up flow that reconciles cash collected, orders assigned, and tips owed at end of shift, producing a per-driver over/short figure.
delivery-cash-reconcile
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
Can hand a first-party order to an on-demand courier marketplace (DoorDash Drive, Uber Direct, Nash, Relay or equivalent) natively from the POS, with the courier quote and status returning into the order record.
delivery-daas-dispatch
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
Supports hybrid dispatch: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. differentiator
delivery-daas-fallback
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
Offers direct, first-party certified API integrations with DoorDash, Uber Eats, and Grubhub marketplaces (vendor-owned, not solely resold through Otter/Deliverect/Chowly/ItsaCheckmate middleware). differentiator
delivery-3p-direct-integration
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
Third-party marketplace orders inject automatically into the POS as normal tickets that fire to KDS/printers without tablet re-keying or manual accept.
delivery-3p-injection
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
Marking an item or modifier 86'd in the POS pushes item-level out-of-stock status to connected third-party channels in near real time, and restores it on availability (DoorDash requires item and item-option 86ing of new POS partners).
delivery-86-sync
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
Store can be paused/deactivated on each connected third-party marketplace from inside the POS with a timed auto-reactivation, rather than only from each marketplace's own tablet or portal.
delivery-store-pause
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
Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. differentiator
delivery-3p-reconciliation
CLAIM: Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. VERDICT: no. EVIDENCE: Linga's 3P story is an integration hub with named partners (Deliverect, Chowly, DoorDash Drive, Uber Eats, Octopus Bridge, Shogo, Restaurant365 - the /integration-hub index lists them all). Tokenised over the whole corpus: 'reconcil*' 6, none of which is a 3P payout report (they are end-of-day deposit reconciliation, a Vexen payment-integration parity note, negative-stock reconciliation and a blog line about "reconciling reports"); 'payout(s)' 8, all of them till Pay Out / tip payouts / bottle-deposit and lottery payouts at the POS; 'commission(s)' 11, none a marketplace commission report; 'marketplace' 8, none a settlement report. No report in the KB's report-family documentation matches marketplace deposits against POS-recorded 3P sales. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://lingapos.com/integration-hub · retrieved 2026-09-17 adversarially verified
Vendor exposes integration health to the operator — failed/rejected order injections, connection status per channel, and alerts on failure — rather than failing silently. differentiator
delivery-injection-error-visibility
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
Guests receive a branded order status / driver tracking page or SMS link on the restaurant's own domain for first-party delivery orders, driven by real order and driver state.
delivery-tracking-page
"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
Quoted delivery promise times adjust dynamically from current kitchen load, driver availability, and zone drive time, rather than a fixed per-store constant. differentiator
delivery-promise-time
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
Vendor documents explicit offline behavior for delivery: whether cash delivery orders, driver assignment, and driver settlement continue during an internet outage.
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 ordering & guest-facing channels
Vendor ships a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission.
digital-first-party-web
"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
Vendor offers a branded native iOS and Android ordering app (published under the restaurant's own brand in the App Store/Play Store), not only a mobile web page or a shared multi-restaurant marketplace app. differentiator
digital-native-app
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
Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels.
digital-account-saved-payment
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 checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator
digital-upsell-engine
Vendor asserts an upsell surface, but the named mechanic on the same page is 'Show offers on customer-facing screens to boost add-ons' - promotional offers on the CDS, not rules-based or personalized item suggestions in a digital cart. Shortfall 1: the archived Mobile OLO App walkthrough takes the guest categories -> item detail -> cart -> 'Continue to Payment' with no suggestion or cross-sell step anywhere in the flow. Shortfall 2: no attach-rate reporting - P3 retested, the Reports family is exactly Sale, Discount, Void, Transactions, HA Statement, Employee, Paid In/Paid Out and Exchange; no upsell or attach-rate endpoint appears in the published 44-page API reference. Grade C because the only positive evidence is a marketing page. https://lingapos.com/restaurant/quick-service · retrieved 2026-09-04
Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.
digital-scheduled-pacing
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
Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.
digital-fulfillment-modes
Pickup and 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
Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.
digital-qr-table
"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
Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator
digital-kiosk
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
Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.
digital-group-ordering
CLAIM: Supports group ordering: a shareable link where multiple participants add their own items to one order. VERDICT: no. EVIDENCE: Tokenised: 'group order(s)' 0, 'shared cart' 0, 'split the link' 0 across 3.94 MB. The online-ordering surface IS documented in depth - the KB's back-office-2024-online-ordering-* family covers the Stores order settings (Delivery, Pickup, Curbside Pickup, ASAP and Future Orders), account creation ("Enable Sign Up with Google", Facebook, guest checkout) and the checkout flow - and no multi-participant or shareable-cart construct appears anywhere in it. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://lingapos.com/solutions/online-ordering · retrieved 2026-09-17 adversarially verified
Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator
digital-catering-portal
CLAIM: Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. VERDICT: no. EVIDENCE: Same zero: 'cater(ing|er|ers)' 0 across 3.94 MB, so the digital side has no catering flow either. The online-ordering product is documented screen by screen in the KB's back-office-2024-online-ordering-* family (Stores, Order Settings, Account, checkout) and its order types are Delivery, Pickup, Curbside Pickup, ASAP and Future Orders - no catering menu, minimum, lead-time rule or proposal. House Accounts DO exist as a payment method (back-office-2024-customers-house-account, pos-house-account-payments), which is the only conjunct of this claim the product could satisfy, and it is not wired to any catering flow; one conjunct out of five, and not the flow itself, so not partial. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://lingapos.com/solutions/online-ordering · retrieved 2026-09-17 adversarially verified
Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator
digital-voice-ai-phone
CLAIM: Vendor offers AI voice phone ordering (native or a named certified partner) that answers calls and places orders. VERDICT: no. EVIDENCE: Linga's phone-order products are a human Call Center system and Caller ID integration (both have dedicated /solutions pages and KB articles: "Caller ID in POS Settings - When a Customer calls and places an Order, the Caller ID..."). Tokenised over the whole corpus: 'voice' 7 total, and every one is poison - 2 are the KB's own typo 'E-Voice URL' (for the E-Invoice pay-online URL on a receipt template), 3 are a blog on "Voice Search Optimization" for local SEO, 2 are "their voice matters" in a loyalty blog. 'artificial intelligence' 0, 'AI' 11 (all blog prose about the industry, zero in the KB), 'assistant(s)' 2 ("a digital hostess assistant" on the membership page - a waitlist/queue feature). No first-party or named-partner AI voice agent exists on any Linga surface. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://lingapos.com/solutions/call-center-system-for-restaurants · retrieved 2026-09-17 adversarially verified
Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.
digital-drivethru-ai
CLAIM: Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers. VERDICT: no. EVIDENCE: Compound absence: there is no AI voice agent at all (see digital-voice-ai-phone: 'voice' 7 hits, all poison; 'AI' 11, all blog prose, 0 in the 618-article KB) and no drive-thru lane construct ('drive[\\s-]?thru' 3 hits, all marketing/blog prose; 'lane(s)' 6, all the 'LANE 1 / LANE 2 / EXPRESS LANE' graphic on the retail liquor-store page; 'headset(s)' 0, 'speaker post' 0, 'menu board(s)' 0). BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://lingapos.com/restaurant/quick-service · retrieved 2026-09-17 adversarially verified
Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.
digital-sms-ordering
CLAIM: Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS. VERDICT: no. EVIDENCE: ENUMERATION on the vendor's own product page: /solutions/text-alerts is LINGA's entire SMS product and its FAQ closes the list in both directions - "What types of Alerts can be sent? Text Alerts can be sent for waitlist notifications, POS actions such as voids and discounts, and alerts to customers on the status of their delivery" and "Can I schedule one-time alerts? No, alerts are triggered automatically by actions at the point of sale." It is strictly outbound and POS-triggered; nothing inbound. Tokenised over 3.94 MB with 'SMS' present 272 times (so the vocabulary is richly represented): 'text to order' 0, 'text-to-order' 0, 'SMS ordering' 0, 'order by text' 0, 'chatbot' 0, 'chat ordering' 0. The 21 'conversational' hits are the poison named above - 'Conversational UI' is a Back Office display toggle on menu items and subcategories. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://lingapos.com/solutions/text-alerts · retrieved 2026-09-17 adversarially verified
Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator
digital-google-order
CLAIM: Supports Order with Google - the restaurant's direct ordering link is provisioned to the Google Business Profile / Search / Maps ordering slot. VERDICT: no. EVIDENCE: Tokenised: 'order with google' 0, 'reserve with google' 0, 'food ordering end-to-end' 0, 'place card' 0. 'google business profile' scores exactly 1 and it is a THIRD PARTY'S bundle, not Linga's: the /integration-hub/chowly page's "What's included" list for the Chowly Platform reads "Website Builder, 1st-Party Online Ordering, Google Business Profile Management, Google & Meta Ads, 3rd-Party Marketplace Integration..." - a partner marketing service that manages the profile listing, not provisioning of Linga's direct ordering link into Google's ordering slot, and it satisfies none of the claim. 'google' itself scores 46, and every other hit is a different Google product, which is the control that makes the absence measurable: Google Tag Manager ("GTM Online Ordering - the Google Tag Manager integration with Linga OLO"), Google reCAPTCHA on the OLO checkout, "Enable Sign Up with Google" social login, the Google Play app-link field, a Google map view of the store, and Google Chrome in the hardware requirements. The online-ordering documentation enumerates its channels and Google's ordering slot is not among them. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://lingapos.com/solutions/online-ordering · retrieved 2026-09-17 adversarially verified
Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.
digital-apple-business-connect
CLAIM: Supports Apple Business Connect ordering placement - an 'Order Food' custom action on the Apple Maps place card. VERDICT: no. EVIDENCE: Tokenised over 3.94 MB: 'apple business connect' 0, 'apple maps' 0, 'business connect' 0, 'place card' 0, 'showcase' 0. Apple vocabulary is otherwise present ('iphone|ios' 57 hits, App Store app-link field, Apple Pay on the LINGA Go page), so the absence is measured against a corpus that does talk about Apple surfaces. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://lingapos.com/solutions/online-ordering · retrieved 2026-09-17 adversarially verified
Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.
digital-loyalty-attach
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
Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.
digital-subscriptions
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
Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.
digital-promo-parity
Discounts 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
Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator
digital-guest-data-ownership
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 uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.
digital-checkout-pci-sca
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 channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator
digital-surcharge-transparency
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 data, loyalty & marketing
Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.
guest-loyalty-unified-profile
"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
Orders arriving from third-party marketplaces (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. differentiator
guest-loyalty-thirdparty-identity-attach
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
Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.
guest-loyalty-accrual-models
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
Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator
guest-loyalty-tiers
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
Documents explicitly what loyalty lookup, accrual, and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). differentiator
guest-loyalty-offline-behavior
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
Offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. differentiator
guest-loyalty-offer-stacking-rules
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
Offers can be issued to a dynamically defined audience (rules over recency, frequency, spend, or items purchased) rather than only broadcast to the whole list. differentiator
guest-loyalty-targeted-offers
"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
Automatically computes recency/frequency/monetary or equivalent lifecycle segments (new, regular, at-risk, lapsed, VIP) without the operator building the queries. differentiator
guest-loyalty-rfm-segmentation
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
Ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns rather than one-off manual sends.
guest-loyalty-lifecycle-automation
"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
Sends both email and SMS campaigns natively from the platform, not solely by handing the list to a third-party ESP. differentiator
guest-loyalty-native-email-sms
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
Captures per-channel marketing consent with timestamp and source of consent, and honors revocation received by any reasonable means (not just the STOP keyword) across all channels.
guest-loyalty-consent-management
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
Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.
guest-loyalty-10dlc-registration
CLAIM: Handles or explicitly documents A2P 10DLC brand and campaign registration required for the SMS channel. VERDICT: no. EVIDENCE: Linga ships an SMS channel ('SMS' 272 tokenised hits; a dedicated Text Alerts product page; an SMS Order Notifications section inside the Back Office KDS Configuration screen; SMS marketing campaigns on /solutions/marketing), so the claim applies. Tokenised controls: '10DLC' 0, '10 DLC' 0, 'A2P' 0, 'campaign registry' 0, 'TCR' 0, 'brand registration' 0, 'toll-free verification' 0, 'short code' 0 - nothing anywhere in the 618-article KB, the 137-page site or the developer docs documents who registers the brand and campaign. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://lingapos.com/solutions/text-alerts · retrieved 2026-09-17 adversarially verified
Reports redemption and incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. differentiator
guest-loyalty-campaign-attribution
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
Provides self-serve export of the full guest list and transaction history, including contact PII, via CSV or API, without a vendor fee or support ticket. differentiator
guest-loyalty-data-export-portability
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
Triggers post-transaction feedback requests and routes responses by score, sending low scores to private service recovery and high scores toward public review sites. differentiator
guest-loyalty-review-capture-routing
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
Includes a native referral mechanic with per-guest codes or links, attribution of the referred guest's first order, and two-sided rewards.
guest-loyalty-referral-program
CLAIM: Includes a native referral mechanic with per-guest codes or links and attribution of the referred guest. VERDICT: no. EVIDENCE: Tokenised: 'referral(s)' 1 hit in the whole 3.94 MB corpus, and it is the poison named above - the LINGA Partner Program page ("Gain access to reseller, referral, and white label partner programs"), a RESELLER tier, not a guest mechanic. 'refer a friend' 0, 'invite a friend' 0, 'referral code' 0, 'referred by' 0. The loyalty product is documented in the KB (loyalty points, membership, gift cards, marketing campaigns) and carries no referral construct. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://lingapos.com/solutions/customer-loyalty-programs · retrieved 2026-09-17 adversarially verified
Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance, as an alternative to requiring a branded app download. differentiator
guest-loyalty-wallet-pass
CLAIM: Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance. VERDICT: no. EVIDENCE: Tokenised with the plural handled ('wallets?'): 11 hits, and all 11 are the generic payment-acceptance sense - "mobile wallets and contactless payments", "Accept contactless, mobile wallets, and EBTs", "deliver payments through prepaid cards or digital wallets" (the ADP tip-payout integration). Zero are a pass. 'apple wallet' 0, 'google wallet' 0, 'passbook' 0, 'pkpass' 0, 'wallet pass' 0, 'loyalty card' 0 (the plural trap matters here: a naive \\bwallet\\b control returns 0 and would have looked like a cleaner zero than it is). BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://lingapos.com/solutions/customer-loyalty-programs · retrieved 2026-09-17 adversarially verified
Provides admin tooling to fulfill guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records.
guest-loyalty-privacy-rights-tooling
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
Enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log.
guest-loyalty-redemption-fraud-controls
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
Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing (claim-level; verify it is a shipped product feature, not a roadmap statement). differentiator
guest-loyalty-ai-offer-recommendation
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
Offers native stored-value/gift card balances tied to the same guest profile and redeemable across all locations of the brand.
guest-loyalty-stored-value-gift
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 & workforce
Employees clock in and out at the POS terminal using a PIN, badge, or card, with no separate time-clock hardware required.
labor-clock-in-at-pos
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
Captures a photo at punch (or performs facial verification) attached to the timecard entry, with a photo-only mode available that stores no biometric template. differentiator
labor-photo-punch-verification
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
Records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, with the behavior documented. differentiator
labor-offline-time-punch
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
Permissions are grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers.
labor-granular-rbac
"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
Manager overrides and approvals are attributed to the individual approver and written to an immutable audit trail queryable after the fact.
labor-manager-override-audit
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
Builds and publishes employee shift schedules inside the same platform that holds the timekeeping data, rather than requiring a third-party scheduling app. differentiator
labor-native-scheduling
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
Generates recommended staffing levels or labor hours by daypart from the operator's own POS sales history, not just a static template. differentiator
labor-demand-labor-forecast
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
Displays labor cost as a percentage of sales in real time during service on a manager view or POS, not only in end-of-day or next-morning reports. differentiator
labor-realtime-labor-percent
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
Warns or blocks at clock-in when an employee is approaching or would cross a configured overtime threshold, before the overtime is incurred. differentiator
labor-overtime-prevention
This OVERTURNS the standing rationale, which asserted the Scheduler article 'states no overtime warning either when building a schedule or when an employee clocks in'. The article does state one. In fairness the line reads as a screenshot caption, but it is vendor documentation asserting the Scheduler warns on an overtime shift. Thresholds are operator-configured: store-settings says 'Define your OT settings here. You can add by weekly or daily OT depending on your local laws.' Named shortfall, which is why this is partial and not yes: the claim requires the warn/block AT CLOCK-IN, and the documented warning fires at schedule-build time in the back-office Scheduler. Nothing documents a punch-time prompt or block. Capture 2022-05-23. ARCHIVE CAVEAT (203rd): support.lingaros.com serves a byte-identical 25,169-byte SPA shell for every path today and its Help Center API 401s on the portal's own orgId, so this article body was read from the Wayback capture named in the URL. https://web.archive.org/web/20220523133652/https://support.lingaros.com/portal/en/kb/articles/linga-scheduler · retrieved 2026-09-04
Configures meal and rest break rules per state or jurisdiction, prompts required break attestation, and flags missed breaks for premium pay. differentiator
labor-break-compliance-by-state
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
Enforces minor-labor restrictions (age-based maximum hours, prohibited time windows, school-day limits) at both scheduling and clock-in.
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
Computes tip pooling and tip-outs automatically per shift from configurable rules (percentage of sales, hours worked, points, or role), rather than requiring a manual spreadsheet.
labor-tip-pooling-rules
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
Retains a per-shift, per-employee record of tips received, amounts contributed to the pool, and amounts distributed from the pool, exportable for audit.
labor-tip-distribution-audit-trail
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
Payroll export separates cash from charged qualified tips and carries a Treasury tipped-occupation code, supporting the W-2 Box 12 code TP and Box 14b reporting required for tax year 2026. differentiator
labor-qualified-tips-w2-reporting
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
Vendor processes payroll itself as a first-party product (tax filing and direct deposit), as opposed to exporting to a third-party payroll provider only. differentiator
labor-native-payroll
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
Exports timecards, wages, and tips in documented formats or via direct integration for at least two major payroll providers (e.g. Gusto, ADP, Paychex, QuickBooks).
labor-payroll-export-formats
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
Employees can request shift swaps or claim open shifts in a self-service app, subject to a manager approval workflow that enforces overtime and role eligibility. differentiator
labor-shift-swap-workflow
"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
Reports per-employee sales performance metrics (average check, items or category attachment rate, void and comp rate) by server or cashier. differentiator
labor-server-performance-metrics
"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, purchasing & cost control
Supports multi-level recipe/BOM costing where a recipe can contain sub-recipes (prep items) and plate cost recalculates automatically when any component ingredient's cost changes.
inventory-recipe-bom-costing
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
Stores purchase unit, recipe unit, and count unit per item with explicit conversion factors, plus a yield/waste percentage applied to raw-to-usable conversion.
inventory-unit-conversion-yields
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
Produces a theoretical-vs-actual usage variance report per item for a defined count period, showing theoretical usage from POS sales times recipe, actual usage from counts plus receipts, and the variance in both units and currency. differentiator
inventory-theoretical-vs-actual
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
Depletes ingredient on-hand quantities in near real time as orders are fired at the POS, including depletion driven by modifier selections, not only in an end-of-day batch. differentiator
inventory-realtime-depletion
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
Automatically 86s (marks unavailable) menu items on the POS, online ordering, and connected third-party delivery menus when a component ingredient hits zero or a configured threshold. differentiator
inventory-86-auto-sync
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
Supports full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts.
inventory-count-modes
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
Provides a mobile/tablet counting app supporting barcode or QR scanning that continues to accept counts with no network connectivity and syncs on reconnect.
inventory-mobile-count-offline
"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
Ships pre-built electronic vendor catalog and order-transmission integrations with named broadline distributors (e.g. Sysco, US Foods, Performance Food Group) that send purchase orders and receive invoices electronically rather than by emailed PDF. differentiator
inventory-vendor-catalogs-edi
The 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
Ingests supplier invoices from photo, PDF, or email and extracts line-item detail (item, quantity, unit, price) into the inventory ledger without manual line entry. differentiator
inventory-invoice-ocr
CLAIM: Ingests supplier invoices from photo, PDF, or email and extracts line-item detail. VERDICT: no. EVIDENCE: Linga has a documented Purchase Invoice screen ('purchase invoice' 11 KB hits) and a Stock app that was revamped in 2025 (july-16th-2025-stock-app-revamp, august-20th-2025-stock-app-revamp-improvements), so the claim applies. Tokenised controls: 'OCR' 0, 'upload invoice' 0, 'email invoice' 0, 'vendor bill' 0, 'invoice scan' 0, 'line-item extraction' 0. 'scan' 49 and 'photo' 42 are both present but neither is invoice capture - 'scan' is barcode/QR scanning at the POS and 'photo' is menu-item and product images. Invoices are entered by hand. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-inventory-item · retrieved 2026-09-17 adversarially verified
Tracks per-item purchase price history across invoices and alerts when a received price exceeds the prior or contracted price by a configurable threshold. differentiator
inventory-price-change-alerts
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
Maintains par levels per item per location and generates suggested purchase order quantities from on-hand versus par, with at least one mode driven by a sales forecast rather than a static par. differentiator
inventory-par-auto-suggest
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
Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.
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
Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.
inventory-shelf-life-expiry
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
Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting.
inventory-bar-partial-bottle
CLAIM: Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting. VERDICT: partial - fractional liquid stock is supported by unit conversion; nothing bar-specific and nothing by weighing is documented. EVIDENCE: AFFIRMATIVE HALF: Back Office > Inventory > In House Units defines units with a "Measure Type - (Mandatory) Select either Weight or Volume via the toggle" and Conversion Units entered "up to 4 decimal places" in the form "1 [Name] equal to [Measurements] [Unit]", and the article's own worked example is a bottle: "You buy a bottle of Vodka (1 Liter) but when we make drinks, we use Vodka in ml. So, you convert 1L bottle into 1000 ml." So a bottle is decomposed into a fractional in-house unit and stock is carried in that unit. NEGATIVE HALF: nothing documents counting a part-used bottle. Tokenised over 3.94 MB: 'partial bottle' 0, 'bottle fraction' 0, 'tenth(s)' 0, 'pour(s|ing)' 0, 'keg(s)' 0, 'wine by the glass' 0, 'half bottle' 0. 'scale(s)' 211 is the poison named above - a weighing scale wired to the POS for retail weight-based pricing (pos-operation-scale-hardware-settings, retail-pos-scale-hardware-settings), never an inventory-counting scale. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-in-house-units · retrieved 2026-09-17 adversarially verified
Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.
inventory-cogs-gl-export
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 and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator
inventory-native-not-partner
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
Reporting, BI & data access
Provides a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise.
reporting-realtime-dashboard
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
Generates a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types, and expected cash deposit in one document.
reporting-eod-closeout
"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
Provides a product mix (PMIX) report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center.
reporting-pmix-modifier-level
"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
Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.
reporting-comps-voids-audit
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
Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.
reporting-cash-over-short
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
Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.
reporting-labor-productivity
"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
Reports per-server metrics including average check, items per check, attachment rate for named categories, and tips as a percentage of sales. differentiator
reporting-server-scorecards
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
Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator
reporting-channel-profitability
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
Supports scheduling any report for automatic recurring delivery by email or to a shared destination on a defined cadence and recipient list.
reporting-scheduled-delivery
"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
Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator
reporting-public-api
Re-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
Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator
reporting-webhooks
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
API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator
reporting-api-not-upcharged
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
Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator
reporting-tier-paywall
Restaurant Feature Comparison Matrix (retired www.lingaros.com, Wayback 2024-03-01; plans CORE $29.99 / PRO $49.99 / ENTERPRISE $89.99 per register per month paid annually, plus LINGA ONE by quote). Read from raw table cells: on the entry Core plan 'Reports', 'Void transactions', 'Payroll reporting', 'Employee performance tracking', 'Sales Dashboard' and 'Employees Dashboard' are all 'Included in that plan', so comps/voids audit and basic labour reporting are not paywalled. The Core/Pro/Enterprise tier names are still used in live KB articles (2025-10-27, 2026-01). SHORTFALL: 'Consolidated reporting', 'Multi-site management' and 'Royalty / ACH reporting' are 'Unavailable for that plan' on Core and Pro and included only on Enterprise, so multi-location comparison is top-tier only; 'Food costing' and 'Inventory comparison' are unavailable on Core; the 'Kitchen Display System Dashboard' and 'Online Ordering Dashboard' are paid add-ons below Linga One. The page is retired and the live lingapos.com/pricing is an unreadable SPA shell, so current packaging is unconfirmed. https://web.archive.org/web/20240301023505/https://www.lingaros.com/pricing/restaurant/feature-comparison-matrix/ · retrieved 2026-09-12 adversarially verified
Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator
reporting-history-retention
CLAIM: Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. VERDICT: no - no window is published, and the product ships an archive-offload mechanism whose window is undocumented. EVIDENCE: AFFIRMATIVE COUNTER-EVIDENCE that the claim's risk is live: the Back Office Admin > Accounts screen (retail-back-office-admin-accounts) exposes "ArchiveDB Information - ArchiveDB Is Active: If enabled, the archive database information will be activated" followed by "AWS Access Key ID / AWS Secret Access Key / AWS Region / AWS S3 Bucket / AWS S3 Storage Class", alongside "DB Information - Upon clicking Generate, the Sales Count and DB Size will appear". So transaction history is offloaded to a customer-supplied S3 bucket and the live database is sized and managed - and nowhere is it stated how much detail stays queryable in the reporting UI. Tokenised over 3.94 MB: 'data retention' 0, 'retention window' 0, 'retention policy' 0, 'years of data' 0, '24 months' 0, '13 months' 0, 'purge' 0. 'archiv*' scores 9 - the ArchiveDB fields above plus an Archive action that archives a store or a user account - and 'truncat*' scores 1 (a UI bug about menu-item names "appear[ing] truncated at the end"). 'retention' scores 33 and every hit is poison: "POS Settings Retention After Signing Out" (a toggle that remembers UI state), the "RETENTION RATION" dashboard permission (a customer Retention Ratio metric), and marketing prose on "customer retention". The only 'retention period' text in the corpus is the GDPR privacy policy's generic "Once the retention period expires, Personal Data shall be deleted", which names no window and concerns personal data, not transaction detail. The KB documents the reporting UI's date filters screen by screen and never states how far back detail is queryable. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://support.lingaros.com/portal/en/kb/articles/retail-back-office-admin-accounts · retrieved 2026-09-17 adversarially verified
Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator
reporting-anomaly-alerts
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
Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.
reporting-nl-query
CLAIM: Offers a natural-language query or AI assistant that answers ad-hoc questions against the reporting data. VERDICT: no. EVIDENCE: LINGA Insights is the analytics product and has both a marketing page and KB report documentation. Tokenised: 'natural language' 0, 'ask a question' 0, 'AI assistant' 0, 'copilot' 0, 'chat' as an analytics surface 0. 'AI' scores 11 and all 11 are blog prose about the industry with zero hits in the 618-article KB; 'assistant(s)' 2 is "a digital hostess assistant" on the membership page (waitlist/queue). 'quer(y|ies)' scores 88 and all 88 are in the developer API docs (HTTP query parameters) - a substring-class trap for this cell, not a reporting feature. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://lingapos.com/solutions/insights · retrieved 2026-09-17 adversarially verified
Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator
reporting-guest-cohorts
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
Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator
reporting-sales-forecast
"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
Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.
reporting-tip-tax-compliance
The 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, franchise & enterprise governance
Supports a named organizational hierarchy of at least three levels (e.g. enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations.
multi-location-org-hierarchy
"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
Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.
multi-location-price-zones
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
Provides above-store reporting that aggregates sales, labor, discounts, voids, and item mix across any selected set of locations in one view, with store-vs-store ranking and variance flags.
multi-location-consolidated-reporting
"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
Gift cards issued at one location are redeemable at any other location in the brand, with a reported outstanding-liability balance and inter-store settlement/redemption reconciliation between owners.
multi-location-cross-location-giftcard
"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
A single customer loyalty profile, balance, and stored order history is shared across all locations in the brand rather than being per-location.
multi-location-cross-location-loyalty
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
A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. differentiator
multi-location-multi-brand
CLAIM: A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. VERDICT: no - the only virtual-brand capability published is a third party's, and it is adjacent to the claim, not the claim. EVIDENCE: The one hit is on Linga's own integration-hub page for Deliverect: "Virtual Brands Integration: Integrate virtual brands with the ability to manage multiple storefronts through a single delivery platform." That is a partner managing DELIVERY-PLATFORM storefronts, not a Linga terminal running two brands on one drawer, and it satisfies none of the claim's three conjuncts (separate menus per brand at the terminal, per-brand receipt branding, separately reportable revenue). Tokenised over the whole corpus: 'virtual brand(s)|ghost kitchen(s)' 2 (both that one Deliverect paragraph), 'multi-brand' 0, 'concept(s)' 0 in the brand sense, 'banner(s)' 153 all UI toast confirmations (poison). The KB's Enterprise Settings and store-hierarchy articles describe stores, not brands within a store. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://lingapos.com/integration-hub/deliverect · retrieved 2026-09-17 adversarially verified
Tax configuration is per-location with support for multiple simultaneous tax rates, jurisdiction-specific rules (e.g. prepared-food vs grocery, inclusive vs exclusive tax), and per-location tax exemptions.
multi-location-multi-tax-jurisdiction
Tax is configured 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
Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.
multi-location-central-labor-policy
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 & physical footprint
The POS software runs on commodity off-the-shelf hardware (standard iPads, Android tablets, or PCs) that the operator can buy from a third party, rather than only on vendor-supplied proprietary terminals. differentiator
hardware-commodity-devices
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
Vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs.
hardware-os-platforms
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
Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.
hardware-handheld-purpose-built
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
The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator
hardware-handheld-battery-swap
Archived Linga first-party hardware shop (Wayback capture 2020-08-11; also 2020-09-26). Grade C: vendor commerce page. Linga published a rated battery life for the handheld it sold for mobile ordering. The 'Apple iPad mini 5 Wi-Fi - 64 GB' listing states 'Battery Run Time: Up to 10 hours'. The shop's 'Mobile Bundle for iPad Mini 5 64GB' (https://web.archive.org/web/20200929165314/https://shop.lingaros.com/products/mobile-bundle-for-ipad-mini-5-64gb) 'is used for table or pool side ordering as well as line busting' and includes a hand strap enclosure. SHORTFALLS: (1) the 10 hours is Apple's 'up to' manufacturer figure, not a POS-workload or full-shift rating by Linga. (2) No swappable or field-replaceable battery is documented for any handheld; the iPad battery is sealed. (3) The current handheld listing publishes capacity only: the 2023 PAX A920 Pro 'Mobile Bundle' (https://web.archive.org/web/20231004003020/https://shop.lingaros.com/products/mobile-pos-bundle) gives 'Battery 5250mAh | 3.7V' and 'high-capacity battery', with no run time. (4) The 2019 Stock-take Handheld lists 'Battery: Non-detachable lithium 3.8v/3000mAh', but it is an inventory counting device, not the ordering handheld. DATE CAVEAT: the run-time figure is from 2020; shop.lingaros.com now 301s to a Zoho Books sign-in wall. This corrects the earlier note's 'battery occurs ZERO times', which was bound to the KB, www and API corpora and not to the shop. POISON: 'battery life' also hits the Galaxy Tab kiosk (13 hours, a fixed kiosk), the mobile receipt printer, barcode scanners, and the 2025 'Linga Card Reader ... extended battery life' (a payment reader, not a handheld). https://web.archive.org/web/20200811103334/https://shop.lingaros.com/products/ipad-mini-4-128gb · retrieved 2026-09-13 adversarially verified
Handhelds support cellular/LTE connectivity as a documented fallback when store Wi-Fi drops, either built into the device or via a vendor-supplied failover.
hardware-handheld-lte
Archived Linga first-party hardware shop, 'Mobile Bundle' page (Wayback capture 2023-10-04). Grade C: vendor commerce page. Linga sells a cellular-capable ordering handheld. The bundle is a PAX A920 Pro with a required 'LINGA CORE SaaS subscription' (Table Layout & Management, Loyalty & Marketing, Gift Card). Its specification block reads 'Comms Configurations 4G + WiFi (2.4GHz, optional 5GHz) + Bluetooth 4.0' and 'SIM / SAM 1 x SIM + 2 x SAM'. The device is current Linga hardware: the live KB article pos-sppax-payments (support.lingaros.com) says 'Linga GO app is installed in A77 SPPAX device for sale and payments. Device Name : A77 , A920 , A920 pro , A800'. The 26.08.001 release notes (2026) resolve 'performance issues observed on some A920 Pro devices'. Earlier, the shop sold 'iPad 32GB 9.7-inch WiFi + Cellular' (shop.lingapos.com 2019-12-11) and 'iPad 32GB 10.2-inch WiFi + Cellular ... Data plan required' (shop.lingaros.com 2020-08-11). It also sold a Netgear 4G LTE failover modem for the store uplink. SHORTFALLS: nothing documents cellular as a FALLBACK when store Wi-Fi drops. There is no automatic switchover, SIM provisioning or carrier plan, and the KB never mentions cellular. The iPad mini handheld bundle the shop sold was Wi-Fi only ('Includes iPad Mini 5 WIFI 64GB'). The 270th's rejected slogan 'Full mobility with Wi-Fi and LTE!' also appears on the shop's LINGA GO SaaS listing (2024-03-03) and adds no mechanism. DATE CAVEAT: the radio spec is from a 2023 shop capture, and shop.lingaros.com now 301s to a Zoho Books sign-in wall. POISON: 'iPhone' hits 777 pages, all from the Apple-trademark footer; 'battery'/'LTE' also hit barcode scanners, the mobile receipt printer and the Galaxy Tab kiosk. https://web.archive.org/web/20231004003020/https://shop.lingaros.com/products/mobile-pos-bundle · retrieved 2026-09-13 adversarially verified
Terminals continue to take orders, print to kitchen, and record cash sales with the internet down, and the vendor documents explicitly which functions degrade (card auth, loyalty lookup, refunds).
hardware-offline-mode
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
Sells or supports a dedicated kitchen display system with bump-bar or touch input, station routing, and course/fire timing, as a first-party product rather than an integration-only dependency.
hardware-kds
First-party KDS 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
Offers a self-order kiosk running the same menu and modifier engine as the POS, in both countertop and freestanding form factors, with integrated payment and accessibility (ADA) compliance documented. differentiator
hardware-kiosk
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
Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, and speaker/headset integration, with a documented timer/speed-of-service measurement.
hardware-drive-thru
CLAIM: Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, headsets/intercom. VERDICT: no. EVIDENCE: ENUMERATION: pos-hardware-requirements publishes the complete supported-device list (iPad 10.2" 8th Gen or later / iPad Mini 5th Gen / iPad Air 4th Gen / iPad Pro 12.9" 4th Gen / iPad Pro 11" 2nd Gen; Android 4 GB RAM, 8 GB storage, Android 11+; Windows 11 with Google Chrome, 8 GB RAM - plus "Note: Linga POS is currently unavailable on iPhone"), and the KB's hardware-settings family enumerates every peripheral class it supports: receipt printer, kitchen printer, label printer, printer rerouting, card reader, customer display, scale. No outdoor or lane device appears in either list. Tokenised: 'menu board(s)' 0, 'order confirmation board' 0, 'headset(s)' 0, 'speaker post(s)' 0, 'intercom' 0, 'outdoor' 3 (food trucks on the LINGA Go page and shade at the LINGA Summit - poison). 'order confirmation' 8 is an online-ordering email/SMS confirmation. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://support.lingaros.com/portal/en/kb/articles/pos-hardware-requirements · retrieved 2026-09-17 adversarially verified
Works with standard ESC/POS thermal receipt and kitchen printers from more than one manufacturer (e.g. Epson and Star), including LAN/Ethernet printers, rather than only vendor-branded printers.
hardware-printer-compatibility
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
Supports the standard peripheral set — cash drawers (including multi-drawer per terminal), barcode scanners, scales for by-weight items, and customer-facing displays — with a published compatibility list.
hardware-peripherals
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
Card entry happens on a PCI-listed PTS device using validated point-to-point encryption, so the POS application and tablet stay out of PCI scope; the vendor states the merchant's SAQ type.
hardware-p2pe-terminal
"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
Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. differentiator
hardware-tap-to-phone
CLAIM: Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. VERDICT: no. EVIDENCE: Two independent enumerations close this. (1) pos-hardware-requirements states "Note: Linga POS is currently unavailable on iPhone" - Tap to Pay on iPhone is therefore impossible on this product. (2) pos-operation-card-reader-hardware-settings is the card-reader screen and every acceptance path it enumerates needs a SEPARATE reader: "The Card Reader screen allows you to Select a Card Reader. It displays a list of EMV devices configured in the Back Office, with their Name and IP Address", plus Bluetooth readers "select Edynamo or Tdynamo". The LINGA Go FAQ closes it from the marketing side too: "Swipe, insert, and tap to pay are the current transaction capabilities" with "LINGA Mobile, LINGA Tablet, or a compatible Android device" - i.e. tap on a terminal/reader. Tokenised: 'tap to phone' 0, 'softpos' 0, 'tap on phone' 0, 'tap to pay on iphone' 0, 'contactless' 177 (all terminal-side acceptance). BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://support.lingaros.com/portal/en/kb/articles/pos-hardware-requirements · retrieved 2026-09-17 adversarially verified
Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator
hardware-pricing-transparency
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 can be purchased outright (owned) as an alternative to a mandatory lease or subscription-bundled rental, and the vendor states which. differentiator
hardware-ownership-vs-lease
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
Vendor documentation confirms whether hardware purchased from the vendor remains usable with other software after cancellation, i.e. it is not software-locked or remotely bricked. differentiator
hardware-usable-after-churn
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
Publishes a hardware warranty term and a replacement/advance-exchange SLA with a stated turnaround (e.g. next-business-day depot swap). differentiator
hardware-rma-sla
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
Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.
hardware-byod
CLAIM: Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model. VERDICT: partial - commodity personal hardware is explicitly supported and specced; a BYOD permission/security model is not documented. EVIDENCE: AFFIRMATIVE HALF: the app is published for commodity devices with minimum specs a staff-owned device can meet - pos-hardware-requirements gives Android "RAM: Minimum 4 GB, Storage: Minimum 8 GB, OS Version: Android 11 and above" and Windows "Google Chrome, 8 GB RAM, Windows 11", and the LINGA Go FAQ says "LINGA Mobile, LINGA Tablet, or a compatible Android device is required" - a non-Linga Android device is affirmatively supported. NEGATIVE HALF: nothing addresses personal devices as such. Tokenised over 3.94 MB: 'BYOD' 0, 'bring your own' 0, 'own device' 1 (marketing prose, "from the comfort of your own device"), 'personal (device|phone)' 1 and it is a CUSTOMER scanning a QR code, not staff. The Back Office does document a role/permission model in detail (the user-management roles articles enumerate permissions), but no device-trust, enrolment, remote-wipe or personal-device policy is published, so the claim's second conjunct is unmet. Also note "Linga POS is currently unavailable on iPhone", which excludes the most common staff-owned phone. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://support.lingaros.com/portal/en/kb/articles/pos-hardware-requirements · retrieved 2026-09-17 adversarially verified
Provides a remote device-management console showing each terminal, printer, and KDS as online/offline, with remote reboot, software-version visibility, and staged rollout of updates. differentiator
hardware-remote-device-management
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
Integrates with specialty beverage hardware — self-pour tap walls, flow meters, or liquor pour spouts — such that pours post to a POS tab automatically.
hardware-selfpour-scales
Archived LINGA blog 'Brewery POS System' (retired www.lingaros.com, Wayback 2022-03-13): "LINGA's integration partner AndroBar, allows bartenders to only dispense liquor after a sale has been rung into the brewery POS. The integrated solution controls the brand and amount for each order", with "Cloud-based digital tracking" of "ingredients used, portion size, date, time, and user". The 2023-09-23 integrations directory lists AndroBar under 'Liquor Control' as 'a complete and integrated liquor control system' and a 2022 blog calls it 'LINGA's latest integration'. So a liquor pour-control system is integrated with the POS. SHORTFALL: the flow is sale-first, dispense-second - a POS ring releases the pour, pours do not post to a tab automatically; no self-pour tap wall or flow meter is named; AndroBar appears in none of the 617 live KB articles or live lingapos.com integration pages, so current availability is unconfirmed. https://web.archive.org/web/20220313044047/https://www.lingaros.com/blog/brewery-pos-system-craft-beer-restaurants/ · retrieved 2026-09-12 adversarially verified
Supports inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call.
hardware-callerid-integration
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
Integrations, API & extensibility
Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.
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
API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator
extensibility-api-access-cost
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
A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator
extensibility-free-sandbox
P1 is dead and P3 holds, so this cell moves. A staging environment IS documented: this line heads 12 of the 44 doc pages and ships a real seeded Store_id, and two endpoints publish staging hostnames directly. That is the yes half. Named shortfall, which is why this is partial: the sample credential pairs that store id with the literal placeholder 'API Key: generated-api-key', and /docs/introduction documents exactly one way to obtain a real key - sign in to www.lingaros.com, add a store, then Licenses > Developer API > Key Generator. That presupposes a provisioned store, so the claim's 'without owning a paid production account' is NOT established. Neither is 'free': /docs/api-limit's 'Free Edition' / '250 credits' is a per-24h credit allowance tied to a product edition, not a sandbox price. https://developer.lingapos.com/docs/doc-categories/ · retrieved 2026-09-04
Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).
extensibility-oauth-partner-apps
The 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
The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.
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
Webhooks are cryptographically signed (e.g. HMAC) AND documented to retry with backoff, with a replayable event log for missed deliveries. differentiator
extensibility-webhook-reliability
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
A public write API accepts externally originated orders into the POS as first-class tickets that fire to KDS/printers and land in reporting.
extensibility-order-injection-api
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
The vendor is a named DoorDash Preferred Integration Partner (DPIP) under the 2026 program requirements. differentiator
extensibility-doordash-preferred
DoorDash publishes its own complete provider registry at https://merchants.doordash.com/api/partner-integrations — 64 providers, each carrying a `qualityStatus` of PREFERRED (12), CERTIFIED (47) or AT_RISK_OF_SUSPENSION (5), plus a count of how many of the eight high-quality features the provider has built. It is served anonymously and merchants.doordash.com/robots.txt permits it (Allow: / with only /cdn-cgi/ and /monitoring barred). This is what the program page means when it says the roster is tracked in real time, and it is a CENSUS rather than a floor: every provider integrated with DoorDash appears in it with a tier, so a vendor that is absent altogether is not in the programme at any tier. This vendor appears nowhere in the 64 entries, under any provider id or friendly name — checked mechanically against both fields, with the only near-misses being substring coincidences (Speedline against Lightspeed, vroom_restaurant against Restaurant365) that were read and rejected. SUPERSEDES the 2026 announcement post most of this corpus cited: that post introduces its ten names with the word `include`, which makes it a floor and never a ceiling, and reading it as a ceiling is what produced this cell's prior grade. GRADE HARMONISED TO B, 2026-09-11: this URL was first written at grade A. The adversarial pass ruled E on the principle that the rubric grades by the publisher's relationship to the SCORED vendor, and DoorDash is not that vendor. B is the settlement, for two reasons that are not preference: 39 rows already graded a DoorDash-published document B on this claim before today, and one URL on one claim cannot carry two grades; and E is unworkable, because nine of the 47 rows are `yes` on a differentiator-weight claim, which the grade floor refuses below B. B reads as the product documentation of the programme's own publisher, which is what this registry is. The dissent is recorded in verification.jsonl. https://merchants.doordash.com/api/partner-integrations · retrieved 2026-09-11
Direct, first-party certified integrations exist with DoorDash, Uber Eats, and Grubhub without requiring a paid middleware layer (Otter/Chowly/Deliverect/Checkmate). differentiator
extensibility-first-party-delivery-integrations
Uber Eats 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
The POS is a supported endpoint for at least two major aggregation middleware platforms (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate).
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
Native, vendor-maintained connectors exist for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export.
extensibility-accounting-connectors
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
Labor hours export natively to at least two named payroll providers (e.g. Gusto, ADP, Paychex, Paylocity) without manual re-keying.
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
The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.
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
The vendor supports a headless/embedded mode where a third-party UI (kiosk, web ordering, drive-thru) drives the POS transaction engine via API.
extensibility-headless-embedded
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
A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator
extensibility-data-portability-exit
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 & operations
Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.
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
Card payments can be accepted while offline via store-and-forward, not just cash-only fallback. differentiator
reliability-offline-card-auth
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
The vendor publicly documents who bears the loss when a store-and-forward transaction declines after connectivity returns, and states any per-transaction or cumulative offline cap. differentiator
reliability-offline-decline-liability
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
Multiple terminals continue to share a single check/table state over the local network while the internet is down (LAN-only degraded operation, not per-terminal islands). differentiator
reliability-lan-degraded-multi-terminal
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
The vendor documents a local/on-premise transaction engine or edge server (not purely cloud-hosted request/response) for the ordering path. differentiator
reliability-local-transaction-engine
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
Kitchen display and/or kitchen printer routing continues to function while offline.
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
The system automatically fails over to a backup printer or KDS station when a configured kitchen printer is unreachable, and alerts staff.
reliability-printer-fallback
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
The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).
reliability-sync-conflict-handling
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
The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).
reliability-offline-feature-matrix
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
A public, per-component status page exists showing current and historical incident state without a login.
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
24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.
reliability-247-live-support
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
The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator
reliability-onsite-install
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
A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.
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
The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.
reliability-pci-dss-4-attestation
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
Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.
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
A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.
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
Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. differentiator
reliability-failover-terminal-role
CLAIM: Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. VERDICT: no - the architecture has no such role, and the documented continuity mechanism is a different one. EVIDENCE: Linga's continuity mechanism is per-device Offline Mode 2.0, documented in five dedicated KB articles (pos-offline-mode-8-5-2025, -allow-offline-payment, -restrict-offline-payment, -process-offline-alert-message, pos-payments-offlinemode; 'offline mode' 195 tokenised hits). It is per terminal and automatic against the CLOUD, not against a peer: "When the system goes offline, the Offline Mode toggle will be enabled... When the system comes online, the Offline Mode and Allow Offline Payment toggles will automatically be disabled." Tokenised controls for the claim's own vocabulary: 'local server' 0, 'failover' 0, 'standby' 0, 'peer' 0, 'backup (terminal|server)' 0, 'hub (device|terminal)' 0, 'master terminal' 0. 'master' 24 is only 'Master Stock Report' and 'primary' 44 is only 'Primary Storage' / 'primary language' - both named as poison above. No primary/master terminal role is defined anywhere, so none can be assumed on failure. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-8-5-2025 · retrieved 2026-09-17 adversarially verified
Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.
reliability-cellular-backup
Archived Linga first-party hardware shop (Wayback captures: shop.lingapos.com 2019-07-19 and 2019-12-11; shop.lingaros.com 2020-08-11 to 2020-09-29). Grade C: vendor commerce page. Linga sold a vendor-supplied cellular failover for the store uplink. The Networking collection, beside the Ubiquiti POE switches and access points it specifies for installs, lists 'Netgear 4G LTE Modem with Boost Antenna (requires data package)' at $349 and 'Netgear 4G LTE Modem with 2 Gigabit Ethernet Ports' at $289. The product copy reads: 'Get automatic 4G LTE connection', 'Works with any AT&T data plan', 'failover to LTE', 'Reliable backup source when Broadband connectivity is not available'. SHORTFALLS: (1) the automatic-failover wording is Netgear's manufacturer copy; Linga documents no POS-side behaviour, configuration or support for the switchover. (2) The merchant supplies the data plan. (3) It is not current. The last capture carrying it is 2020-09. shop.lingaros.com now 301s to shop.lingapos.com, a Zoho Books sign-in wall. The current KB Network Requirements article specifies wired Cat6 plus 5GHz Wi-Fi and says 'Linga is not responsible for network issues'. DATE CAVEAT: this is 2019-2020 evidence, a historical accessory rather than a current documented failover. POISON: 'Pax Modem Dial Backup' ($49) is a PSTN dial fallback for card authorisation, not WAN; 'failover' has zero hits anywhere in the corpus outside the Netgear copy. https://web.archive.org/web/20200924071541/https://shop.lingaros.com/products/netgear-4g-lte-modem-with-boost-antenna · retrieved 2026-09-13 adversarially verified
Commercial, compliance & data ownership
Vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core POS software tier. differentiator
commercial-month-to-month-contract
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
Vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. differentiator
commercial-no-early-termination-fee
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
The auto-renewal term and the required cancellation notice window (e.g. 30/60/90 days) are stated in publicly accessible contract terms rather than only in a signed quote.
commercial-autorenew-terms-published
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
The POS software can be purchased and operated with a third-party payment processor of the operator's choice (no mandatory in-house processing lock). differentiator
commercial-processing-not-bundled
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
Vendor publishes an interchange-plus (cost-plus) processing rate option with the markup stated as a specific bps + per-transaction figure, rather than only blended/flat card-present rates. differentiator
commercial-interchange-plus-published
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
The processing agreement caps or prohibits unilateral vendor-initiated rate increases outside of pass-through interchange/network changes, or grants penalty-free exit on any increase. differentiator
commercial-rate-increase-clause
CLAIM: The processing agreement caps or prohibits unilateral vendor-initiated rate increases outside pass-through interchange/network changes, or grants penalty-free exit on any increase. VERDICT: no - the published agreement does neither, and its exit is expressly penalised. EVIDENCE: NEW SURFACE: the rebuilt marketing site publishes LINGA's full General Terms and Conditions (62.6 KB, https://lingapos.com/sales-terms-and-conditions) plus an EULA (26.9 KB) - vendor legal text, grade B. Tokenised controls over those two documents: 'increase(s|d)?' 0, 'adjust(ment)?' 0, 'revise' 0, 'modify the Fees' 0, 'change the Fees' 0, 'surcharge' 0, 'prices' 0. Positive in-document controls prove the fee vocabulary is present: 'Fees' is a defined term ("Customer shall pay LINGA the fees, costs, expenses, and charges as set forth on the Sales Order"), 'Cancellation Fee' 12, 'interchange' 2. So no cap, no prohibition and no repricing clause of any kind is published. The exit side is affirmatively falsified: "LINGA or Customer may terminate this Agreement without cause, for any reason, upon written notice to the other party; subject to any conditions contained in this Agreement and/or any Sales Order impacted by the termination including any Cancellation Fees due and owing", and under the Complimentary Hardware Program "The Customer agrees to three (3) year term for SaaS Services and Hybrid Payments Merchant Processing" with a Cancellation Fee that "is not a penalty but is a reasonable amount of liquidated damages", charged on a published sliding scale by timing of cancellation. Interchange risk is pushed to the merchant: "IT IS THE CUSTOMER'S RESPONSIBILITY TO MONITOR AND MANAGE PROPER INTERCHANGE FEES AND ASSESSMENTS WITH THEIR ACQUIRER." LIMIT OF THE BOUND: card processing itself runs through a named third party ("Hybrid Payments Merchant Processing") whose own agreement is not published; what is bounded here is LINGA's complete published contract set, which governs every Sales Order and neither caps increases nor grants penalty-free exit. BOUND (re-derived 2026-09-17, not inherited): Linga's whole current public surface = 3.94 MB. (a) support.lingaros.com Zoho Desk KB: 618 articles enumerated by the anonymous portal listing API (/portal/api/kbArticles?portalId=edbsnad7f...&limit=50&from=N, paged to exhaustion), bodies 2.72 MB - the HTML portal returns an identical 25,276-byte SPA shell for a real slug and for a fabricated one, so the API is the only discriminator. The href fixpoint holds: 101 article links inside the bodies, 11 without a current permalink, and all 11 resolve to a renamed article that IS in the census (factor4-sppax-payment -> factor4-integration; store-hours-24-4-2023 -> back-office-2024-store-business-hours-settings; renenue-center-settings -> back-office-2024-revenue-center-report-settings; etc.). (b) www.lingapos.com was REBUILT as a Next.js site since the 195th pass: sitemap.xml = 137 URLs / 0.81 MB, and an href fixpoint over all 137 fetched bodies yields exactly 137 internal URLs, none outside the sitemap. (c) developer.lingapos.com Docusaurus = 44 URLs, byte-identical URL set to the prior corpus. RESIDUE: 5 of 618 KB articles (april-21st-2025-release-notes, august-5th-2025-release-notes, august-14th-2025-card-reader-manager-and-gift-card-swipe-support, may-14-2024-release-notes, may-21-2024-release-notes) say 'see attached document' and the portal API exposes no attachments field; all five are release notes whose surrounding text names the feature (e.g. the Star TSP100 printer). POISON FOUND (all controls run tokenised, case-insensitive, as \\b(?:term)s?\\b): the plural trap is live here - \\bwallet\\b scores 0 while 'wallets' scores 11; substring 'voice' matches 'invoice' and the KB's own typo 'E-Voice URL' (for E-Invoice); substring 'expo' matches 'export' (107 substring vs 9 tokenised); 'conversational' is 'Conversational UI', a menu-item/subcategory DISPLAY toggle (21 hits), not conversational ordering; 'master' is only 'Master Stock Report'; 'primary' is only 'Primary Storage' and 'primary language'; 'banner' is a UI toast confirmation (153 hits); 'scales' is a weighing scale for retail weight-based pricing; 'quote' is 'Base Quote Time' (prep/delivery minutes); 'lane' is 'LANE 1 / LANE 2 / EXPRESS LANE' on the retail liquor-store page; 'outdoor' is food trucks and the LINGA Summit party; 'referral' is the LINGA Partner Program's reseller/referral PARTNER tier. Retrieved 2026-09-17. https://lingapos.com/sales-terms-and-conditions · retrieved 2026-09-17 adversarially verified
Per-location and per-additional-terminal software pricing is published as specific dollar figures on the vendor's public site (not 'contact sales' only).
commercial-pricing-published
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
Individual modules (online ordering, KDS, loyalty, inventory, payroll, marketing) can be purchased à la carte and cancelled independently without repricing the base POS subscription. differentiator
commercial-module-unbundling
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
All required terminals, KDS screens, and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental.
commercial-hardware-purchase-outright
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
Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator
commercial-hardware-not-locked
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
Operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee.
commercial-data-export-self-serve
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
Guest/customer records, loyalty balances or point ledgers, and gift-card liability balances are exportable in machine-readable form by the operator. differentiator
commercial-export-customer-and-loyalty
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
Contract or documentation specifies a post-termination data retrieval window (a defined number of days during which the operator can still export their data) rather than immediate cutoff. differentiator
commercial-post-termination-export-window
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
Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator
commercial-data-ownership-clause
The 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
Vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A / SAQ P2PE-HW, and names the applicable SAQ.
commercial-pci-p2pe-tokenization
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
Vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — notably MFA for all access to the cardholder data environment including POS and back-office logins, and (for hosted ordering pages) payment-page script integrity monitoring per Req 6.4.3/11.6.1.
commercial-pci-dss-4-controls
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
Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.
commercial-privacy-dsar-tooling
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
Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator
commercial-wcag-kiosk-accessibility
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
POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator
commercial-dual-pricing-compliant
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
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 113 values — 59 upheld, 47 downgraded, 7 upgraded. It separately resolved 158 previously unknown values. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Pricing and identity
| Field | Verdict | What the verifier found |
|---|---|---|
| org.ownership | resolve-to-yes | Researcher searched only the vendor's own About page and stopped. Linga is a wholly-owned subsidiary of The PNC Financial Services Group (NYSE: PNC), acquired 26 Sep 2022. This is a newsroom/investor-relations source — the strongest evidence tier available — and it materially changes the diligence picture: the vendor is bank-owned, which explains the aggressive payments-bundled economics (free hardware for a 3-year merchant processing agreement) far better than the dossier's read of it as a scrappy independent's entry ramp. Founder/CEO Onur Haytac and the management team were retained; operations continue out of Naples FL and Toronto. source |
| org.ownership | upgrade-to-yes | Wrong as stated. Linga itself files nothing, but it is a subsidiary of an NYSE-listed bank holding company. For a buyer this is the opposite of the risk profile 'private, no filings' implies — counterparty risk is low, but processor neutrality is structurally compromised by the parent's merchant-services interest. Deal value undisclosed. [2026-08-12, same-document re-point only: the URL recorded here on 2026-08-01 was this slug truncated before '-solutions-firm-linga'; verified first-hand that it 301s to the URL now recorded and returns a byte-identical body (29,899b, sha256 3b21cb35d7df81ca), so both linga-pos citations of this release are ONE document. The slug is decorative and self-correcting; only the numeric id 360 is honest, and a fabricated id answers 404. The verdict, the reasoning and the date checked are untouched — re-pointing a URL is not re-checking a claim.] source |
| identity.founded | resolve-to-yes | Established 2004 (as Benseron Hospitality; renamed Linga in July 2019). Stated in PNC's acquisition release. The dossier's 'unknown' was correct about the vendor's own site and wrong about the public record. source |
| identity.scale | resolve-to-yes | PNC's release states Linga 'currently serves clients in 48 countries' (as of Sep 2022). Still no location or ARR figure, so scale remains partly unknown — but the dossier's inference that 39 reviews 'suggests a modest installed base' is unsupported and should be struck. A 48-country footprint corroborates the international/multi-language differentiator on a strong source rather than marketing copy. source |
| api_posture.public_api | upgrade-to-yes | This is the dossier's biggest factual error and it inverts the headline conclusion. A public, login-free, search-indexed API reference exists at developer.lingaros.com/docs — the researcher only checked the lingapos.com marketing funnel and never followed to the lingaros.com developer host. Documented base URL is https://api.lingaros.com/v1/lingapos/ (explicitly versioned), auth is an API key in request headers (Basic). Reading the docs requires no registration; only credential issuance is gated. Correct posture is 'public docs, key-gated credentials', not 'partner-gated'. source |
| api_posture.notes | upgrade-to-yes | Refuted. Those four areas are marketing-page prose, not the API surface. The actual reference documents at minimum: Products/Items (menu items) with pricing, categories, vendors, storage locations and units; Inventory Menu Items (paginated GET with search and active/inactive filters); Transactions Reports (filterable by date option and tender name/type); Paid In / Paid Out Reports; Stores; Roles; Departments; Service Types. Inventory and transaction/tender-level financial reporting are present, directly contradicting 'notably absent'. Payments-acceptance and labor/timecard endpoints remain undocumented as far as I could enumerate. source |
| best_at.delivery | downgrade-to-partial | The 'rather than an add-on' half is fabricated. Nothing on the Linga Driver page, the payment-plans page, or any pricing page states that driver tracking is included in base subscription rather than sold as a separate module — and Linga publishes no module-by-module pricing at all, so inclusion cannot be established in either direction. Given the vendor markets 22 discrete 'solutions', the prior should be that these are separately licensed. The bullet also pairs this with 'a native DoorDash Drive integration' — DoorDash Drive is a named third-party hub integration whose detail page renders no description, which is the opposite of native. source |
| pricing.processor_lock_in | downgrade-to-unknown | 'Penalty' is not established by anything located. There is a documented requirement to add Hybrid Payments to qualify for free hardware, and a 3-year MPA, but no published ETF, no liquidated-damages clause, no hardware clawback term, and no retrievable MSA (the dossier itself scores ETF as unknown). The correct label is 'preferred / bundled-incentive'; asserting a penalty imports a contract term nobody has read. Note the internal tension the dossier never resolves: it labels lock-in 'with-penalty' here while scoring the ETF cell unknown. source |
| pricing.contract_length | upheld | Verified verbatim on the vendor's own page: 'Requires Hybrid Payments 3-year Merchant Processing Agreement, and 3-year LINGA SaaS.' The page markets 'three flexible plans' but details only the Complimentary Hardware Plan; terms for the other two are genuinely unpublished. This is the dossier's best-sourced pricing claim and it holds. source |
| pricing.software | upheld | The quote-only verdict is upheld — I re-checked /pricing and confirmed zero dollar figures, tier names or per-user prices. But 'no tier detail' is inaccurate: the same Gartner-network listing publishes a three-tier structure with a range, From $29.99–$89.99/month, listing Core $29.99, Pro $49.99 and Enterprise $89.99 per user per month, plus a claimed free version and free trial. Still a vendor-supplied third-party listing field and not a rate card, so it must not be scored — but the dossier understates what is in circulation, and a claimed free version sits oddly against a 3-year SaaS commitment. Worth putting to the vendor as a contradiction. Sole evidence was www.softwareadvice.com, which the source policy forbids as evidence for a capability claim. Requires re-verification against the vendor's own documentation. |
| pricing.processing_rate | upheld | Independently re-verified: the Linga Pay page publishes no rates or percentages of any kind — no flat rate, no interchange-plus markup, no per-transaction fee. It also says nothing about surcharging or dual pricing, confirming those adjacent cells as unknown. source |
| vs_reference | downgrade-to-partial | The comparative conclusion needs rewriting on its central point. A public, versioned, key-authenticated REST API with documented menu, inventory, store, role and transaction/tender reporting endpoints does let an operator extract their data programmatically. What survives: no webhooks (now affirmatively established, so integrations must poll), no published rate limits, no sandbox, no OAuth, no deprecation policy, no retrievable terms and therefore no data-ownership or post-termination export clause. The honest framing is 'a real but thin, read-oriented API with no event model and no contractual data guarantees', not 'partner-gated with no public reference'. The lock-in argument should rest on the 3-year dual commitment and the missing contract terms, which are solid, rather than on API opacity, which is overstated. source |
| org.ownership | upheld | The enum contradicted the record's own audit trail: two 2026-08-01 rows on this same field already established that Linga is a wholly owned subsidiary of The PNC Financial Services Group (NYSE: PNC), acquired 2022-09-26, and identity.founded (2004 as Benseron Hospitality, renamed Linga July 2019) was resolved from the same release, yet product.yaml was never updated. Same handling as the olo and hungerrush corrections: the verdicts were right and the fields were stale; org.ownership set to subsidiary with parent and ticker, org.name and identity.founded rewritten to carry the PNC citation. source |
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| extensibility-public-api-docs | no — Access is gated: the developer-partner page routes prospective integrators to 'Register as a Developer' via an API agreement. No publicly readable, self-serve API reference host was locatable. | upgrade-to-yes | Affirmatively false. developer.lingaros.com/docs/ is publicly readable with per-endpoint pages showing methods, parameters and auth. A scored 'no' on a weighted extensibility cell, based on failure to find a host that Google indexes, is the inverse of the error class I was asked to hunt — the researcher was under-generous here while over-generous elsewhere. Caveat retained: I could not load the docs pages directly during this check (host returned 502 repeatedly); confirmation is via search-engine extraction of page content plus an independent third-party connector doc. source |
| reporting-public-api | partial — enumerated coverage is menu categorization, online ordering, device syncing and user roles — payments and labor absent. Self-serve credentials not available. | upgrade-to-yes | Reporting endpoints are explicitly documented: Transactions Reports (by date range and by tender name or tender type) and Paid In / Paid Out Reports. That is transaction- and tender-level sales data over a documented, versioned REST API. Self-serve credential issuance is still not available, so this is a 'yes' on API existence and documentation, not on frictionless access. source |
| extensibility-webhooks-push | unknown | resolve-to-no | Now affirmatively established rather than merely undocumented. Pandium, an independent integration platform that ships a production Linga rOS connector, publishes a capability matrix for the connector stating webhook support: 'No'. Combined with the absence of any webhook, signing-scheme or retry documentation on Linga's own developer host, this meets the bar for a documented 'no' rather than 'unknown'. Integrators must poll. source |
| reporting-webhooks | unknown | resolve-to-no | 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. source |
| delivery-route-map | yes — Live map monitoring of each driver in real time plus 'Reduce travel time with optimal delivery paths' and system sequencing of orders by location nearest to furthest. | downgrade-to-partial | 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 Pricing Plans' CTA. source |
| delivery-driver-tracking | yes — 'Monitor each driver in real-time' — live GPS surfaced back to the operator. | downgrade-to-partial | 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. source |
| kitchen-pizza-fractional-display | partial — Vendor blog states a connected KDS displays 'each section exactly as intended' for quarter and section-based pizza builds. | downgrade-to-unknown | The sole source is a vendor blog post — the weakest evidence class on the site, below even a product page, and written as SEO content about splitting pizza toppings. Linga's actual KDS product page makes no mention of pizza, sections, halves or quarters anywhere; it documents routing by course type, a bump bar, color-coded status and cook timers. A blog sentence contradicted by silence in the product documentation should not carry a score on a pizza-critical cell. source |
| menu-pricing-fractional-placement | partial — 'Supports full, half, and quarter builds with smart modifiers' and 'Customize toppings by section.' | upheld | 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. source |
| menu-pricing-half-and-half-rule | unknown | upheld | Independently confirmed. No pricing rule (higher-half, average, fractional, or per-section) appears on the pizzeria page, the POS page, or the vendor's pizza-toppings blog post. For a pizza-first buyer this is the single most important unanswered question and it must go to the vendor as a scripted demo request, not an RFI checkbox. source |
| payments-payout-timing | yes — 'Same-day Funding' advertised, 'No paperwork, and you choose the payment options.' | downgrade-to-partial | 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. source |
| payments-processor-choice | unknown — Not documented either way. Commercially Linga steers to its own Hybrid Payments via a 3-year MPA. | resolve-to-yes | UPGRADE ONLY TO PARTIAL, not to yes (the verdict enum has no upgrade-to-partial option). PNC's acquisition release describes Linga as 'the first processor agnostic, cloud-based POS system designed specifically for the hospitality industry' — a strong-tier source affirmatively stating processor choice exists architecturally. It stops short of yes for two reasons: the statement describes the product as of 2022 pre-acquisition, and the current commercial structure plus a reviewer report of inability to connect an existing merchant account both cut against it in practice. The right buyer question is now specific: does processor agnosticism survive PNC ownership, and at what price delta versus Hybrid Payments. source |
| payments-offline-store-and-forward | unknown | upheld | Upheld, and flagging the trap the researcher correctly avoided. The POS page markets a 'Never Down Network' with 'full functionality even when Wi-Fi connectivity is lost' — language a less careful reader would score as offline card authorization. The Linga Pay page says nothing whatsoever about offline, store-and-forward, or decline liability. 'Full functionality' is unsubstantiated puffery and must not be read as offline card auth. source |
| reliability-offline-feature-matrix | no — No explicit list of features unavailable offline is published anywhere located. | upheld | 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. source |
| digital-native-app | yes — 'Custom branded app with your restaurant logo, brand colors, and menu loaded instantly' | downgrade-to-partial | 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'. source |
| digital-loyalty-attach | yes — Online ordering documents 'Customer Loyalty Integration' with reward systems. | downgrade-to-partial | 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. source |
| reporting-realtime-dashboard | yes — 'Smart Dashboards' with custom KPI dashboards, plus a mobile app on Android and iOS. | downgrade-to-partial | 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. source |
| payments-gift-cards | partial — Gift cards are a first-party solution and are accepted at kiosk; Factor4 is also a named gift-card integration. (cited to the linga-pay page) | upheld | 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', so it is unclear whether first-party and partner products are alternatives or layers. source |
| hardware-peripherals | partial — Barcode scanning documented for inventory. Cash drawers, scales, and customer-facing displays not documented. | upheld | 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. source |
| extensibility-doordash-preferred | no — Linga is not in DoorDash's 2026 Preferred Integration Partner cohort. | upheld | 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. source |
| delivery-3p-direct-integration | partial — Uber Eats and DoorDash Drive named as direct integrations, but Grubhub is absent. | upheld | 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 or Chowly. Grubhub absence re-verified. source |
| menu-pricing-modifier-price-by-parent-size | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | KB modifier article documents a per-modifier Serving Sizes price table ("For each Serving Size, enter a Price for the Serving Size and each Prefix") — the size dimension of the matrix exists, but nothing documents pricing the same modifier differently on two parent items at the same size. source |
| menu-pricing-topping-quantity-tiers | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-yes | KB documents per-modifier Prefix rows with a Price Field and "Override Modifier Price" toggle, plus a per-serving-size price for each Prefix; the POS article shows prefixes surfacing at order time. That is a configurable per-tier price distinct from ringing the modifier twice. source |
| menu-pricing-included-allowance | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | POS Modifiers KB documents Included Modifiers auto-added to the check with a credit on removal ("the price of the Modifier will be reduced from the Menu Item Cost") and negative pricing restricted to included modifiers. No count-based allowance with overage-only charging is documented, so the differentiator is only half present. source |
| menu-pricing-countdown-auto-86 | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | POS Operation 86 List KB documents a BO-configured per-item quantity that decrements on sale across devices and blocks the sale at zero ("Quantity is not enough"), with void reversal restoring the count. Scheduled auto-restore is absent from the article, so the claim cannot carry a yes. source |
| payments-dual-pricing | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | KB documents a native Dual Price mode under Payment Surcharge: a store-level "Dual Price Percentage" producing a Cash Subtotal line on check and receipt. The mechanism is a percentage discount computed at tender, not two stored prices per item, which is the specific thing the claim asks for. source |
| payments-surcharge-guardrails | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | KB documents per-store surcharge enablement, forced exemption of payment types flagged Debit, and a logged compliance acknowledgment. Exemption is driven by operator configuration of the payment type rather than BIN/product-code detection, and neither prepaid handling nor a network cap is documented. source |
| payments-refund-void-controls | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | Void flow is role/permission-gated with mandatory reasons; role permissions enumerate Void Item / Discount / Void Check; Void Report identifies Void By; Audit Log Report records employee, timestamp and old/new values. No-sale authorization, approver identity distinct from the actor, and immutability are not documented. source |
| delivery-zone-pricing | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | Delivery Application Settings KB documents map-drawn zones with per-zone Delivery Charge and Expected Delivery Time. Per-zone order minimum and automatic application from a validated address are not documented. source |
| digital-subscriptions | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | Customers - Membership KB documents plans with an Allowance Period (Monthly/Quarterly/Half-Yearly/Yearly), Allowance amount, auto Balance and Expiry — a managed paid membership with per-period entitlement. Automatic recurring card billing is not documented, so partial rather than yes. source |
| labor-tip-distribution-audit-trail | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | Employee Report KB documents per-employee tip columns and a Tip Out Share tab with per-business-date share and adjustment amounts; Exporting Reports documents XLSX/CSV/PDF export. Per-shift granularity and a two-sided contributed/distributed ledger are not documented. source |
| multi-location-price-zones | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | Uber Eats integration KB documents order-platform price levels ("set the order platform price level for menu price level, and modifiers percentage") — the channel dimension exists. Enterprise Menu Configuration documents copying menu records between stores, which is duplication, not location-group price zones; daypart pricing is undocumented. source |
| extensibility-oauth-partner-apps | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-no | The public API reference documents the auth mechanism exhaustively: a static per-store key passed as an apikey header, generated from Licenses > Developer API > Key Generator. OAuth 2.0, tokens, and scopes appear nowhere. The docs enumerate the alternative, which is positive evidence of absence, not a mere gap. source |
| reliability-printer-fallback | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-yes | POS Printer Hardware Settings KB documents automatic failover — three connection checks, then routing to the Back Office-mapped Alternate Printer — with an on-screen staff alert naming both printers. All three elements of the claim (automatic, backup device, alert) are documented. source |
| menu-pricing-dual-pricing | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | The Dual Price KB documents a single store-level "Dual Price Percentage", not item-level stored prices — the named shortfall — but coverage spans the claim's channels: order screen Cash Price, CDS, kiosk and online ordering ("after Total as Pay with Cash"), and a printed Cash Subtotal receipt line with the card price as base. source |
| payments-offline-decline-liability | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | The offline payments KB surfaces failed offline checks after reconnect ("dark red highlight indicates already processed offline clicked checks which are failed/invalid"), satisfying the reporting half; no page assigns decline-loss liability — the docs only advise refusing debit cards offline. source |
| kitchen-printer-fallback | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | Printer Hardware Settings documents automatic failover (three connection checks, then the Back Office-mapped Alternate Printer, with a staff alert naming both printers), covering the kitchen-printer leg; KDS-screen failover is undocumented (the KDS KB articles return HTTP 404) and no no-ticket-loss guarantee is stated. source |
| inventory-unit-conversion-yields | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | In House Units documents explicit conversion factors ("1 bag of potatoes (5kg) = 5000 grams", Measurement to 4 decimal places, Volume/Weight types) and the menu-items KB documents per-item Recipe Units; no yield/waste percentage appears in the units, menu-items, or preparation articles. source |
| reporting-tip-tax-compliance | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | The Employee Report documents per-employee CC Tip and Declared Cash Tip columns, a Cash Tip tab (expected versus declared) and a Tip Out Share tab by role and business date — declared-vs-charged and pool-distribution detail exist; a jurisdiction-level tax liability summary is documented nowhere in the reporting KB. source |
| reliability-offline-kds-printing | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-yes | The Offline Mode KB states affirmatively that with the toggle enabled and printers on the intranet, "the IP address printers (Kitchen printers, Receipt printers) will continue to work" offline — the claim is and/or, so the documented kitchen-printer leg carries it; KDS offline routing stays undocumented and is noted. source |
| reliability-sync-conflict-handling | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-no | The claim asks whether the vendor documents conflict-resolution behavior. The dedicated Offline Mode article documents the sync model — one-way local storage, then "transfer all offline data to the back office" on reconnect, with conflict-prone shared-state operations blocked offline — and no conflict semantics appear. The docs enumerate the alternative, which is positive evidence of absence. source |
| order-capture-bar-tab-preauth | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | 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. source |
| order-capture-void-comp-controls | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | 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. source |
| menu-pricing-86-propagation | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | 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. source |
| menu-pricing-channel-price-books | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | 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. source |
| payments-tip-adjust | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | 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, 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 dedicated 'Batch and Tip Adjustment' article search-indexed at that URL returns HTTP 404 on direct fetch. source |
| payments-house-accounts | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | 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; the dedicated 'Loyalty and House Account' KB article search-indexed at support.lingaros.com returns HTTP 404 on direct fetch. source |
| guest-loyalty-offline-behavior | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | 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. source |
| labor-offline-time-punch | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | 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. 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). source |
| labor-tip-pooling-rules | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-yes | 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. source |
| reliability-offline-card-auth | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | The Offline Mode KB documents card payment processing while offline via a Magtek reader ("When an Offline payment is made by using Magtek, the toggle will automatically be enabled") — this is store-and-forward, not cash-only fallback. Shortfall: the article does not describe the store-and-forward mechanism, settlement window, or any per-transaction/cumulative cap, and separately warns "do not accept Debit Card payment from the customer, as the transaction is more likely to be Declined" — so coverage is real but narrower and less reliable than a full offline-card-auth claim implies. source |
| commercial-dual-pricing-compliant | unknown (grade F) — placeholder "No public documentation located during the 2026-08-01 research pass"; the cell was never examined. | resolve-to-partial | 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. source |
| order-capture-split-merge | partial, grade B - "Flexible Group Check Processing" with ability to split or m | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| order-capture-kiosk-first-party | partial, grade B - First-party kiosk with fully customizable menus, items, pric | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| payments-published-rates | no, grade B - The Linga Pay product page markets capability and same-day f | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| payments-gift-cards | partial, grade B - Partial upheld but the citation is wrong and should be repla | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| payments-payout-timing | partial, grade B - A two-word marketing bullet on a sales page cannot support a | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| kitchen-station-routing | yes, grade B - "Send items by type (e.g., appetizer, entrée) to specific sc | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| kitchen-bump-bar-hardware | partial, grade B - "Easy to Use Bump Bar" documented. No list of supported bump | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| kitchen-sla-alerts | partial, grade B - Cook-time monitoring plus color-coded status labels ("cookin | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| kitchen-order-modification-alerts | partial, grade B - KDS will "instantly reflect changes and modifications to any | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| delivery-driver-roster | partial, grade B - Drivers are first-class in Linga Driver with per-driver perf | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| delivery-dispatch-board | partial, grade B - "Auto-assign orders based on availability and proximity" imp | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| delivery-route-map | partial, grade B - Native delivery dispatch is a flagged flip-the-conclusion ce | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| delivery-driver-tracking | partial, grade B - One marketing sentence on the same sales page, scored as 'do | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| delivery-tracking-page | partial, grade B - "Send automatic texts to customers when orders are out for d | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| digital-menu-single-source | partial, grade B - "Simplified Online Menu Synchronization" with guided upload/ | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| digital-native-app | partial, grade B - Marketing-page claim with no verification path. No named exa | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| digital-fulfillment-modes | partial, grade B - Pickup and delivery with configurable delivery zones and ord | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| digital-qr-table | partial, grade B - "QR Pay" contactless documented — scan-to-pay. Scan-to-order | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| digital-kiosk | partial, grade B - First-party kiosk with customizable items/pricing/modifiers, | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| digital-loyalty-attach | partial, grade B - The literal wording is 'Customer Loyalty Integration', which | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| labor-shift-swap-workflow | partial, grade B - "Allow employees to switch or request a shift change with a | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| inventory-mobile-count-offline | partial, grade B - "Adjust inventory counts directly from your phone" plus "Fas | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| inventory-native-not-partner | partial, grade B - A native inventory module exists with ingredient-level track | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| reporting-realtime-dashboard | partial, grade B - Marketing page only, and nothing establishes the 'real-time' | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| reporting-pmix-modifier-level | partial, grade B - "Top-Selling Item Reports" and "Sales Heatmaps" give item-le | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| reporting-labor-productivity | partial, grade B - "Live Staff Metrics" monitoring employee performance, clock- | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| reporting-scheduled-delivery | partial, grade B - "Easily download or email insights." Recurring automatic del | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| hardware-kds | yes, grade B - First-party KDS product with bump bar, station routing to sc | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| hardware-kiosk | partial, grade B - Wall-mounted and countertop form factors with integrated pay | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| hardware-peripherals | partial, grade B - Partial upheld, one factual correction: customer-facing disp | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| reliability-offline-feature-matrix | no, grade B - Upheld and strengthened. The vendor makes an affirmative bla | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| reliability-menu-build-service | partial, grade B - Online ordering documents "Upload, test, and manage menus wi | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| commercial-interchange-plus-published | no, grade B - Linga Pay publishes no processing pricing of any kind — neit | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| commercial-pricing-published | no, grade B - All three pricing URLs (/pricing, /pricing/plans, /payment-p | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| commercial-data-export-self-serve | partial, grade B - Insights allows users to "easily download or email insights" | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| labor-native-scheduling | yes/B - "Build your weekly staff schedule easily, in a matter of minutes" with real-t | upheld | The cited page was lingapos.com/solutions/schedules, a first-party marketing/solutions page (grade C at best) carrying a yes on a differentiator. Re-probed the support host, which has moved to support.lingaros.com; its Zoho Desk portal API still 401s and the portal returns an SPA shell to a Googlebot UA, but the KB category and article pages render and enumerate. The Back Office Scheduler article describes the actual mechanism - per-employee week/month grid, New Shift pane with role, start/finish time past midnight, unpaid break deduction, shift templates, Publish & Notify with SMS notification, and payroll-rate-costed hour totals - inside the same Back Office that holds employee wage and time data, so the yes survives on grade-B documentation rather than on sales copy. source |
| order-capture-floor-plan-editor | unknown / F / "POS page documents Real-Time Table Tracking only. No graphical floor-plan editor... documented." | resolve-to-partial | The prior rationale rested on the lingapos.com marketing page. The Zoho Desk KB (reachable only via a JS-rendering fetch) carries a step-by-step Back Office Table Layout settings article with the floor editor, drag placement, seat count and table shape; server-section assignment is the only element of the claim not documented. source |
| order-capture-seat-level | unknown / F / "no seat-numbering data model or seat-tagged order line is described anywhere reachable" | resolve-to-yes | The prior pass only had the lingapos.com solutions page. The support KB documents seat numbers on order lines and an automatic Split By Seat that moves each seat's items to its own check without re-entry. source |
| order-capture-coursing-hold-fire | unknown / F / "No course assignment, hold, or fire-next-course action is described" | resolve-to-partial | The prior pass looked only at the KDS marketing page. The support KB has both a Back Office Coursing setup article and a POS Fire Coursing article; the fire action exists but operates on items already sent to the kitchen, which is materially weaker than hold-and-release coursing. source |
| order-capture-transfer-audit | unknown / F / "Checked support.lingaros.com search for transfer/check-transfer articles; none surfaced." | resolve-to-partial | Search was the wrong route into this portal; navigating the KB tree to /kb/linga-pos/pos/table-layout-screen surfaces a dedicated Transfer a Check article. Transfer between servers and tables is documented; the both-employees audit row still is not. source |
| order-capture-throttling | unknown / F / "only 'Customize Ordering Hours' and daily delivery scheduling are documented" | resolve-to-yes | The prior pass scored from the lingapos.com online-ordering marketing page. The Back Office online-ordering settings article documents an explicit Throttling Settings surface with maximum-orders caps per time period and per crew/driver and an Additional Wait Time that extends the quote automatically. source |
| order-capture-scheduled-orders | unknown / F / "Online ordering documents 'Customize Ordering Hours' and daily delivery schedules - store hours, not future-dated order acceptance with a computed fire time." | resolve-to-yes | The support KB documents future-dated order acceptance (Future Orders toggle with days/hours advance limit), a Future tab holding them, and a Print Future Orders Before lead time that automatically promotes the order into the active queue at a computed time - exactly the mechanism the prior rationale said was absent. source |
| order-capture-order-ready-signal | unknown / F / "No order-ready callback event sent from POS/KDS bump state back to a marketplace is described." | resolve-to-partial | The support KB does document a ready notification to the marketplace, which the prior pass (working from Integration Hub marketing tiles) missed; it is manual rather than state-driven, which is precisely the shortfall the claim's wording targets. source |
| menu-pricing-half-and-half-rule | unknown / F / "No pricing rule (higher-half, average, fractional, or per-section) appears on the pizzeria page, the POS page, or the vendor's pizza-toppings blog post." | resolve-to-partial | The earlier pass only had marketing pages. The Back Office Products/Items article shows Half and Half as a real menu type with a dedicated configuration surface, which upgrades this off unknown; that surface is a per-combination Unit Price table with no rule selector, which is the shortfall. source |
| menu-pricing-size-style-matrix | unknown / F / "No per-cell base-price override grid is documented anywhere reachable." | resolve-to-partial | Reading the actual Back Office item-creation article (rather than the pizzeria landing page) establishes a documented one-axis size price surface, which moves this off unknown; the second axis and per-cell override remain absent from the item configuration surface. source |
| menu-pricing-combos | unknown / F / "A KB article titled 'Special Combo Menu Item' ... returns HTTP 404 on direct fetch" | resolve-to-partial | The 404 was a fabricated/stale search-engine slug; navigating the KB tree to Back Office > Products/Items reaches the live article, which documents the Combo Item menu type and its component pricing but neither swap deltas nor auto-conversion. source |
| menu-pricing-dayparting | unknown / F / "no menu-, item-, or price-level activation schedule by day/time in the location's own timezone is documented" | resolve-to-partial | The item-level schedule is documented in detail on the Back Office Products/Items article and the timezone selector on the Online Ordering store settings article; both were missed by a pass working from the online-ordering marketing page. Menu-level and price-level scheduling remain undocumented. source |
| menu-pricing-allergen-nutrition | unknown / F / "attempted the Inventory Menu Items KB article, which returns HTTP 404 on direct fetch" | resolve-to-no | The live menu-item configuration article was reached by tree navigation and enumerates the whole item field set twice over on separate reads; neither pass shows an allergen or nutrition field, and the inventory tab links sub-recipes for cost only. This meets the settings-screen enumeration bar rather than being mere absence of evidence. source |
| payments-tip-pooling | unknown / F / "The Dash Solutions integration provides 'real-time tip payouts and payroll delivery' - distribution rails, not configurable pooling allocation rules." | resolve-to-yes | The prior pass had only the payout-rails integration. The support KB has a first-party Tip Out & Tip Sharing configuration screen covering role, percentage, sales-vs-tips basis, per-hour sharing and department scope, and a Role Based Payroll report carrying the resulting per-employee tip allocation. source |
| payments-offline-store-and-forward | unknown / F / "The Linga Pay page says nothing whatsoever about offline, store-and-forward, or decline liability." | resolve-to-yes | The earlier verifier was right to reject the 'Never Down Network' marketing line, but the support KB independently documents genuine store-and-forward: local storage and post-on-reconnect, an Allow/Restrict Offline Payment toggle pair, and per-transaction plus cumulative offline dollar limits configured in Store Payment Settings. source |
| payments-split-tender | unknown / F / "Check split/merge documented, but settling one check with multiple simultaneous tenders is not." | resolve-to-yes | The support KB documents sequential multi-tender settlement explicitly (multi cash remainder to another payment method; numbered partial payments in OLO) plus a 1/2-1/9 split control and split by seat/item/evenly, covering every limb of the claim. source |
| payments-card-on-file | unknown / F / "No PAN-storage or tokenization statement for a guest card-on-file exists anywhere reachable." | resolve-to-partial | A tokenization statement does exist, on the Store Payment Settings article the prior pass had not reached; it is scoped to service types rather than to a guest profile, and the fully enumerated customer record holds no payment method, so the cross-channel guest card-on-file in the claim is not met. source |
| kitchen-expo-consolidation | unknown (grade F) - 'The KDS marketing page says only Help your expo or head chef be more productive ... The KB articles that would settle it both return HTTP 404' | resolve-to-partial | Walked the Zoho Desk tree rather than guessing slugs: /kb/linga-pos/back-office/settings/hardware lists four leaf articles, one of which is Kitchen Printer Hardware Settings. It documents KDS as a kitchen-printer device type and an Expo Device toggle taking an Expo Printer IP Address and a Queue Device IP Address, plus a global 'Send Notification from Every KDS Station' toggle. That establishes an expo device exists and is configured per store; it does not establish consolidation semantics or all-stations-bumped completion, hence partial and not yes. source |
| kitchen-course-firing | unknown (grade F) - 'Checked the KDS product page (2026-08-04) ... No course assignment or on-demand course-fire action ... is described.' | resolve-to-yes | The prior pass scored off the lingapos.com KDS marketing page and never reached the support portal. The Zoho Desk KB carries a dedicated Fire Coursing check-option article, a Change the Coursing of a Menu Item article, and a Back Office Coursing setup article. Assignment plus on-demand per-course firing from the server terminal is documented step-by-step with screenshots - grade B, which is what a differentiator yes requires. source |
| kitchen-order-throttling | unknown (grade F) - 'Checked the KDS product page and the online-ordering page (2026-08-04); neither documents automatic pacing or delay ... tied to a configurable order-volume or ticket-time threshold.' | resolve-to-yes | The prior pass read the lingapos.com online-ordering marketing page, not the admin guide. The support-portal article for the Online Ordering Stores screen has a section literally named Throttling with maximum-orders caps per period and per crew/driver and an Additional Wait Time applied beyond them. Grade B admin documentation, so a differentiator yes is supported. It extends quoted times rather than holding order release, which the claim allows ('or extends quoted prep times'). source |
| kitchen-order-ready-callback | unknown (grade F) - 'Checked the Integration Hub; no order-ready status event sent from a KDS bump back to a third-party marketplace is documented' | resolve-to-partial | The support portal's POS third-party integration articles document a Ready button that sends an order-ready notification to the third-party service for its driver. The capability the claim targets - telling the marketplace the food is actually ready so couriers are timed to it - exists, but the trigger is a manual POS tap rather than a KDS bump, and it is absent for DoorDash Drive. That is present-but-limited, so partial rather than yes or unknown. source |
| kitchen-offline-operation | unknown (grade F) - 'the Offline Mode KB ... does not separately state that a KDS screen continues to receive and display tickets when the cloud backend is unreachable; the KDS-specific KB articles referenced elsewhere in this record 404.' | resolve-to-yes | The current Offline Mode leaf article (pos-offline-mode-8-5-2025) names KDS explicitly alongside kitchen and receipt printers as remaining accessible offline over the intranet - not merely printers as the earlier rationale had it. Grade B vendor documentation, sufficient for a differentiator yes. The prior pass had been reading an older/parent page and 404ing on guessed slugs. source |
| kitchen-item-build-screens | unknown (grade F) - 'Checked the KDS product page (2026-08-04); no item-level build/assembly detail ... is described beyond ticket line text and color-coded categorization.' | resolve-to-partial | The admin guide for kitchen devices (which is also the KDS configuration screen) documents store-wide toggles that add included-modifier breakout and serving size to kitchen output. That satisfies the weakest limb of the claim's disjunction - fuller modifier detail than the line text - but recipe/portioning build detail is entirely undocumented and no article describes the KDS display itself, so partial with the shortfall named rather than yes. source |
| kitchen-recall-refire | unknown (grade F) - 'Checked the KDS product page; Track Order Completion and the bump bar are documented, but no recall/unbump ... or refire/reprint of an individual item ... is described.' | resolve-to-partial | The support portal, which the prior pass never reached, has a dedicated Resend to Kitchen check option and an item-level Fire action, so re-sending kitchen work without re-keying the order is documented. The recall/unbump half is not documented anywhere reachable, so the honest value is partial with that shortfall stated, not yes. source |
| kitchen-waste-logging | unknown (grade F) - 'Checked the KDS product page; no waste/spoilage/remake logging with reason codes at the kitchen screen is described' | resolve-to-partial | The support portal's 16-article Inventory section includes Adjust Inventory and Adjust Inventory Reasons, so reason-coded stock depletion for waste exists as a documented function. It lives only in the Back Office, which is precisely the limitation this claim tests, so partial with the shortfall named. Walked the POS > Operation section (Till Management, Hardware Settings, Close Day, Employee, 86 List, POS Settings, Support, Sync Back Office) to confirm no POS-side waste entry is documented. source |
| delivery-zones-polygon | unknown (grade F) - 'Set Delivery Zones documented on the online-ordering page but the geometry model (polygon vs radius vs ZIP) is not stated.' | resolve-to-yes | The geometry model is stated in the admin guide the prior pass never reached: zones are drawn on a map with Circle, Shape, Line or Rectangle tools, Shape being a traced polygon. Grade B documentation with step-by-step drawing instructions, which is what a differentiator yes requires. The claim asks for arbitrary polygons OR isochrones - polygons are documented, isochrones are not. source |
| delivery-driver-comp | unknown (grade F) - 'Checked the Linga Driver product page; ... mileage/distance per run, per-delivery flat reimbursement, and driver-retained tips exported to payroll ... are not described.' | resolve-to-partial | The support portal documents a real per-delivery compensation input (Delivery Charge Compensation to Driver percentage) and per-driver tip tracking, reported on both the POS driver cashier report and the Back Office Driver Report. The mileage input and the payroll reimbursement-vs-wage split are absent from the Delivery settings screen, which does enumerate its own fields. Present but materially limited, so partial with those shortfalls named. source |
| delivery-cash-reconcile | unknown (grade F) - 'Checked the Linga Driver product page; no driver cash bank / settle-up flow ... is described.' | resolve-to-partial | The support portal has a driver-scoped cashier report toggle that moves sales onto the driver's name and a Back Office Driver Report with an explicit 'Owed' column defined as the total owed by the driver excluding card payments, plus tips and delivery-charge compensation. That is a settle-up figure per driver. The cash bank and the over/short number the claim asks for are not documented, so partial. source |
| delivery-daas-fallback | unknown (grade F) - 'Checked the Integration Hub; DoorDash Drive and the Uber tile ... but no automatic overflow rule ... is documented.' | resolve-to-partial | The Integration Hub leaf article documents the actual dispatch workflow, which the marketing tiles did not: per-order courier request from the POS, a full status ladder, and an explicit fallback to an internal driver after cancelling the DoorDash driver. So hybrid dispatch exists; the automation the claim specifies does not. Partial with the manual-trigger shortfall named. source |
| delivery-store-pause | unknown (grade F) - 'Checked the Integration Hub; no store pause/deactivation on a connected third-party marketplace from inside the POS, with timed auto-reactivation, is documented.' | resolve-to-partial | The third-party integrations settings screen - the page that enumerates the whole per-partner configurable surface - carries store availability toggles for Yemek Sepeti and Urban Piper and store publish actions for Chowly and Deliverect. So a marketplace store can be taken offline from inside Linga for some partners. It is Back Office rather than POS, does not cover Uber Eats or DoorDash, and has no timed reactivation, so partial with those shortfalls named. source |
| delivery-promise-time | unknown (grade F) - 'Checked the Linga Driver product page; Smart Routes and nearest-to-furthest order sorting are documented ... but no dynamic adjustment of quoted delivery promise times ... is described.' | resolve-to-partial | The Online Ordering Stores admin article documents a Throttling model that lengthens the quoted time as orders per crew and deliveries per driver rise - kitchen load and driver availability, two of the claim's three inputs. The third, zone drive time, is a fixed per-zone Expected Delivery Time, and the whole mechanism is threshold-stepped rather than dynamic. Partial with that named. source |
| delivery-offline-behavior | unknown (grade F) - 'Checked the Linga Driver page (silent on offline behavior) and the Offline Mode KB, which lists blocked-while-offline operations ... but does not separately address whether cash delivery orders, driver assignment, or driver settlement continue during an outage.' | resolve-to-partial | This claim scores whether the vendor documents offline behaviour, and the current Offline Mode leaf article is an explicit works/does-not-work enumeration covering payments, printers/KDS, cash drawer, clock-in and the blocked back-office functions. It is genuine offline documentation, so not unknown; it omits all three delivery-specific questions the claim names, so not yes. Partial with the omissions named. source |
| digital-upsell-engine | unknown | resolve-to-no | Enumeration bar met on three configurable surfaces: the full Add/Edit Product form, the full Kiosk Addon settings, and the full Online Ordering Stores settings, none of which offers a suggested-item or upsell field. source |
| digital-scheduled-pacing | unknown | resolve-to-partial | Future orders with a lead-time limit and a Maximum Orders / Time Period throttle are documented in the OLO store settings; per-slot capacity with automatic slot closure is not. source |
| digital-promo-parity | unknown | resolve-to-partial | Central discount definition with coupon codes reaching OLO checkout is documented; per-channel eligibility controls on the offer itself are not. source |
| digital-guest-data-ownership | unknown | resolve-to-partial | Self-serve bulk export of the guest list with contact PII is documented in the Back Office Customers article; ownership, fee-free status, consent flags and order history are not. source |
| digital-surcharge-transparency | unknown | resolve-to-partial | Cross-channel dual pricing with guest-facing disclosure at online checkout is documented; jurisdiction and card-brand prohibition handling is not, and card-surcharge parity online is unstated. source |
| guest-loyalty-thirdparty-identity-attach | unknown | resolve-to-partial | Uber Eats orders carry name, address, phone and email onto the POS check, so identity is usable; attachment to a native guest profile is not documented. source |
| guest-loyalty-tiers | unknown | resolve-to-partial | Automatic rolling-window member classes with promotion and demotion exist as marketing segments; benefit-bearing membership plans are assigned manually with no automatic tiering. source |
| guest-loyalty-offer-stacking-rules | unknown | resolve-to-yes | Priority (order of application) and Combine With Other Discounts (exclusive vs combinable) are documented configuration fields on the Back Office discount form - grade B, sufficient for a differentiator yes. source |
| guest-loyalty-rfm-segmentation | unknown | resolve-to-yes | Recency- and value-based lifecycle segments (New, Recurring, At Risk, Inactive, Bounced, VIP) are computed by the platform from operator-set day thresholds and are selectable audiences in campaigns - grade B documentation. source |
| guest-loyalty-data-export-portability | unknown | resolve-to-partial | Self-serve CSV/XLSX export of the guest list with contact PII is documented; full per-guest transaction history and an API export path are not. source |
| guest-loyalty-review-capture-routing | unknown | resolve-to-partial | Score-conditional branching to a follow-up question and contact capture is documented in the Feedback App addon settings; routing high scores to public review sites is absent from that complete settings surface. source |
| guest-loyalty-privacy-rights-tooling | unknown | resolve-to-partial | Per-customer delete and self-serve export exist as admin actions, but the delete is documented as inactivation and deletion propagation to loyalty and marketing records is undocumented. source |
| guest-loyalty-redemption-fraud-controls | unknown | resolve-to-partial | Reason-coded manual point adjustment plus an employee-attributed audit log with old/new values is documented; velocity limits, manager approval and self-redemption flagging are not. source |
| guest-loyalty-ai-offer-recommendation | unknown | resolve-to-partial | Shipped Smart Headings and Magic Image suggestion controls cover campaign content; audience and send-time recommendation are absent and the article does not confirm the mechanism is AI/ML. source |
| labor-photo-punch-verification | unknown | resolve-to-partial | Face ID clock-in is a documented Back Office setting; timecard photo attachment and a non-biometric photo-only mode are not documented. source |
| labor-manager-override-audit | unknown | resolve-to-partial | An employee-attributed, queryable audit log with old/new values is documented; approver-distinct attribution on overrides and immutability are not. source |
| labor-realtime-labor-percent | unknown | resolve-to-partial | Labor as a percent of net sales is a documented report with a published formula, but only as a period-filtered back-office report, not a live in-service manager or POS view. source |
| labor-break-compliance-by-state | unknown | resolve-to-partial | Meal and rest break lengths and unpaid deduction are documented store-level settings, but there is no per-state rule set, no attestation prompt and no missed-break premium flag. source |
| labor-qualified-tips-w2-reporting | unknown | resolve-to-partial | Cash versus charged tips are separated by named payroll columns and broken out by role, but no Treasury tipped-occupation code or W-2 Box 12 TP / Box 14b support is documented. source |
| inventory-theoretical-vs-actual | unknown / grade F - scored off the lingapos.com inventory-management marketing page only | resolve-to-yes | Walked the Zoho Desk KB tree to /kb/linga-pos/back-office/inventory and read the Inventory Reports leaf article. The Compare Inventory report carries explicit Ideal Used vs Actual vs Variance columns, each as a Quantity/Price pair. The prior rationale rested on a product page that was never going to name a report. source |
| inventory-count-modes | unknown / grade F - scored off the lingapos.com inventory-management marketing page | resolve-to-partial | The Adjust Inventory leaf article documents individual, bulk and template-upload counting with mandatory reason codes, and the Inventory Reports article documents an Adjust Inventory report with before/after quantities. Held at partial because no scheduled recurring cycle count exists in the documented inventory surface. source |
| inventory-vendor-catalogs-edi | unknown / grade F - "vendor tagging", no EDI documented | resolve-to-no | Two enumerations rather than an absence of search hits: the vendor record's complete field list contains no catalog or EDI identifier, and the purchase-order screen's communication-method option set is exactly {Print, Email}. Electronic PO transmission and invoice receipt therefore have no configured path. source |
| inventory-price-change-alerts | unknown / grade F - reasoned from the marketing page's "Automated Alerts" language | resolve-to-partial | The inventory item and purchases articles show per-item purchase price history (weighted-average / latest unit price, ordered vs received price). The notification settings screen enumerates every configurable alert and contains no price-variance trigger, so the alerting half of the claim fails. source |
| inventory-par-auto-suggest | unknown / grade F - "par levels ... are not documented" | resolve-to-partial | Par Level is an explicit per-item field in a per-store inventory, and the Low Stock screen turns below-par items into a vendor-grouped purchase order. Held at partial: the second half of the claim, a forecast-driven mode as an alternative to static par, has no documented counterpart. source |
| inventory-waste-logging | unknown / grade F - marketing references monitoring "losses" | resolve-to-yes | Three leaf articles together give the whole claim: a mandatory configurable reason code on every inventory adjustment, the debit to the count, and a Wastage Report costing waste separately from the usage-variance report. source |
| inventory-shelf-life-expiry | unknown / grade F - scored off the inventory-management marketing page | resolve-to-partial | The Wastage Report's own description and its "Purchase Expired" loss type show the system holds expiration dates for purchased stock, which the marketing page never revealed. Held at partial because the alerting half - an expiring-soon report before spoilage - is absent from the enumerated notification settings and no expiry field is documented on receiving or on prepped items. source |
| inventory-menu-margin-linkage | unknown / grade F - "Real Costs Analysis" and "Cost vs. Revenue Analysis" marketing language | resolve-to-partial | The Matrix Report is a documented menu-engineering join of item cost to sales mix with an operator-set profit threshold. It stops short of the claim's second half: no alerting, and no trigger on ingredient cost movement. source |
| reporting-eod-closeout | unknown / grade F - scored off the lingapos.com Insights marketing page | resolve-to-partial | The Daily Summary leaf article enumerates the report's tables and columns: gross/net sales, comps and promos, tax, tips by card type, and a cash+gift-card Deposits table. Held at partial because refunds and the cash over/short reconciliation are on separate reports, so it is not the single document the claim describes. source |
| reporting-comps-voids-audit | unknown / grade F - "No comps/voids/override audit report documented" | resolve-to-partial | Read the Discount, Void and Audit Log leaf articles. Comps are an explicit discount coupon type with reason, timestamp and employee attribution, and voids carry reason plus opening and voiding employee. Held at partial: no price-override coverage and no manager-approval attribution. source |
| reporting-cash-over-short | unknown / grade F - scored off the Insights marketing page | resolve-to-partial | The Till Report leaf article names an explicit Over/Shortage column computed as Cash Expected minus counted Amount, per node and per user, with paid-in/paid-out transactions alongside. Held at partial only because the claim's per-shift dimension has no documented counterpart. source |
| reporting-channel-profitability | unknown / grade F - scored off the Insights marketing page | resolve-to-partial | Enterprise reporting does separate online from in-store revenue and revenue-center reporting splits net sales by node and shift, so channel revenue is partly reportable. The commission-netting and per-marketplace halves of the claim have no documented counterpart. source |
| reporting-anomaly-alerts | unknown / grade F - scored off the Insights marketing page | resolve-to-yes | The notifications settings article enumerates the configurable alert surface and three of the entries are exactly the claim's pattern: an operator-configured metric threshold (discount amount, void amount, no-sale drawer opens) that fires a text or email when breached. The claim's alternative branch - historical-pattern deviation - is not required for it to hold. source |
| reporting-guest-cohorts | unknown / grade F - scored off the Insights and loyalty marketing pages | resolve-to-partial | Read the Enterprise Reports, Customer Preference and Membership leaf articles. Identifiable per-guest purchase and loyalty history is reported, so guest-level analytics exist, but every metric the claim names is missing. source |
| multi-location-multi-tax-jurisdiction | unknown / grade F - scored off the franchise marketing page | resolve-to-partial | The Taxes leaf article shows a per-store tax table with inclusive/exclusive, apply-to-item-or-check, per-service-type and quantity-tiered rates - the jurisdiction-rule machinery the claim asks for. Held at partial because the exemption half is undocumented. source |
| hardware-printer-compatibility | unknown / grade F - "no multi-manufacturer ESC/POS compatibility list ... was retrievable" | resolve-to-partial | The receipt and kitchen printer settings articles establish IP/Ethernet printers configured against a Printer Model dropdown, which settles the LAN half and implies a model list. It stays partial because Linga never publishes which models or manufacturers that dropdown contains. source |
| hardware-remote-device-management | unknown / grade F - reasoned from developer API "device syncing" and the back office controlling each location | resolve-to-partial | The Store Licenses settings article documents an actual per-device console with a remote sign-out action, which the prior rationale missed. It falls short of the claim on all four of the specifics named - status, reboot, version, staged rollout - so it is partial rather than yes. source |
| extensibility-webhook-reliability | unknown (grade F) - developer.lingaros.com/docs/doc-automation/ returned HTTP 502 Bad Gateway on three attempts; signing, retry and replay could not be confirmed. | resolve-to-no | developer.lingaros.com 302-redirects to developer.lingapos.com; fetching the webhooks page on the correct host returns the real reference. It documents the complete webhook configuration surface (destination URL, active toggle, user-supplied request header) and two event types, with no signature/HMAC mechanism, no retry-with-backoff and no delivery log or replay - so this is an enumeration of the configurable surface, not merely a failure to find the feature. source |
| extensibility-headless-embedded | unknown (grade F) - checked the partners/become-a-developer-partner page; API areas named are online ordering, menu and reporting, with no headless/embedded mode documented. | resolve-to-partial | The prior pass scored this off a partner marketing page and never opened the API reference. developer.lingapos.com documents a POST saveWebOrder order-injection endpoint and a kiosk login/config pair, which is partial headless operation, but documents no pricing, tender or payment endpoints and makes the ext-app order API read-only - so the transaction engine is not driven by the third-party UI. source |
| extensibility-data-portability-exit | unknown (grade F) - checked the Insights product page (report-level export only) and found no publicly retrievable Linga terms document. | resolve-to-partial | The terms are in fact published at lingapos.com/sales-terms-and-conditions (linked from the footer Legal block, not at the conventional /terms-and-conditions path that 404s), and the support portal documents the export mechanism concretely. Together they establish per-report XLSX/CSV/PDF export plus a customer-list export, and an immediate access cutoff at termination with no bundled historical export - partial, not unknown. source |
| reliability-offline-decline-liability | unknown (grade F) - the batch screen flags failed offline transactions after reconnect and the Offline Mode KB warns Debit is more likely to decline, but no per-transaction or cumulative offline cap was located. | resolve-to-partial | The caps do exist and are documented on the Back Office Store Payment Settings article as two distinct fields (per-transaction and cumulative), scoped by the Restrict Offline Payment article to MPPG card payments. Liability allocation remains undocumented across the support portal, the Sales Terms and the EULA, so the claim is half-satisfied rather than unresolved. source |
| reliability-lan-degraded-multi-terminal | unknown (grade F) - 'Not documented. Reviewers report terminal-to-terminal communication failures - a negative signal about local networking robustness, not documentation of the design.' | resolve-to-no | The prior line was a bare assertion resting on review chatter. The vendor's own KB article on Offline Mode states affirmatively that the POS-to-redis link stops and checks from one POS node are not reflected in other nodes - positive documentation that LAN-only shared check state is absent, not merely unfound. source |
| reliability-local-transaction-engine | unknown (grade F) - offline local storage of orders and time punches is suggestive of on-premise transaction handling but no page frames it as a local engine versus cloud request/response. | resolve-to-no | Re-read the POS: Offline Mode article in full. It names the mediating component (a redis server) and states that when it is unreachable, node-to-node check propagation stops and each device falls back to local storage that is replayed to the server on reconnect. That is a cloud/server-mediated architecture with per-device caching; a local transaction engine or edge server would keep shared state alive, and the vendor documents that it does not. source |
| reliability-public-status-page | unknown (grade F) - 'status.lingapos.com does not resolve in DNS and no status page was linked from any Linga page fetched. Absence is not conclusively established - a status page could exist on an unconventional host.' | resolve-to-no | The prior pass tried the wrong host. status.lingaros.com does resolve, to a Zoho StatusIQ endpoint that reports 'No status page found with this domain mapping' - i.e. the vendor holds the status subdomain and publishes nothing on it. Combined with the full footer link inventory and the Contact Support page's own enumeration of support channels, this is positive evidence of absence rather than a failed search. source |
| reliability-247-live-support | unknown (grade F) - 'Marketing references "white glove support" but no 24/7/365 commitment is published. Reviewers state after-hours calls route to a separate call center with poor responsiveness, and support is not US-based.' | resolve-to-partial | The prior line rested on review chatter and missed the vendor's own explicit statement. Linga's full-service restaurant and kiosk pages both carry 'We provide 24/7 technical support through multiple channels including phone, email, and chat' - a first-party 24/7 phone claim. It stays partial rather than yes because it is grade C feature-page copy: the Contact Support page publishes no hours, the Sales Terms define no support levels or SLA, and nothing establishes 365-day coverage or that it is bundled into the base subscription rather than a tier. source |
| reliability-hardware-replacement-sla | unknown (grade F) - checked the Hardware and Networking KB category and payment-plans page; no hardware replacement/advance-exchange program with a stated turnaround time is documented as included or purchasable. | resolve-to-partial | The prior pass never found the published terms (they sit at /sales-terms-and-conditions, linked from the footer, not the /terms-and-conditions path that 404s). Those terms do document a replacement program - a 12-month defect warranty with replace-or-refund and a 14-day rejection window - so the capability partly exists; it falls short of the claim only on the stated-turnaround and advance-exchange elements. source |
| commercial-no-early-termination-fee | unknown (grade F) - 'No public MSA or terms of service retrievable, so no ETF or liquidated-damages clause could be confirmed or ruled out.' | resolve-to-no | The terms are public - lingapos.com/sales-terms-and-conditions, reached from the footer Legal block; the prior pass only tried /terms-and-conditions, which 404s. Those terms set a 100/75/50/25/0 percent Cancellation Fee schedule by elapsed months and expressly characterise it as liquidated damages, which is direct documentary evidence against the claim rather than absence of evidence. source |
| commercial-autorenew-terms-published | unknown (grade F) - 'Terms pages 404 at conventional URLs; the footer references Terms and Conditions and an EULA but the documents were not retrievable.' | resolve-to-partial | The documents are retrievable - the footer's Terms and Conditions link points to /sales-terms-and-conditions and the EULA to /end-user-license-agreement, both of which render. The terms publish the auto-renewal mechanism (successive terms equal in duration, written notice of non-renewal) and the cancellation form URL, which satisfies the first half of the claim; they omit any numeric notice window and leave the term length to the unpublished Sales Order, which is the shortfall. source |
| commercial-processing-not-bundled | unknown (grade F) - 'Not documented either way, but the documented commercial structure pushes hard the other direction: the hardware-inclusive plan explicitly requires adding Hybrid Payments plus a 3-year Merchant Processing Agreement.' | resolve-to-partial | The product side is documented after all: the Back Office EMV Payment Settings article enumerates a Type dropdown of seven third-party terminal/processor integrations (PAX, Optomany, Ingenico, Clover, Moneris, Evertec, Dejavoo), so the POS is technically operable with processing other than Linga's own. The prior pass's commercial observation is confirmed by the published Sales Terms and becomes the named shortfall rather than the whole answer. source |
| commercial-hardware-purchase-outright | unknown (grade F) - 'No published hardware prices. The marketed path is bundled/complimentary hardware tied to 3-year commitments; outright purchase availability and price are quote-only.' | resolve-to-partial | The availability half is now documented: the published Sales Terms state title to Hardware transfers to the Customer upon sale unless the Sales Order says otherwise, which confirms outright purchase is the default and that no mandatory multi-year lease or rental exists. The prior pass's price observation survives intact as the named shortfall, so the cell moves from unresolved to partial rather than to yes. source |
| commercial-hardware-not-locked | unknown (grade F) - 'no non-proprietary/third-party hardware option ... is confirmed on a page actually read. A LINGA STORE product listing for a standard iPad surfaced in search results but could not be verified as the supported POS terminal itself.' | resolve-to-yes | The prior pass could not open the leaf article - /kb/articles/pos-terminal-requirements 404s, but the real article is /kb/articles/pos-hardware-requirements, reached from the Hardware and Networking section index. It names stock iPad models, generic Android 11+ devices and Windows 11 + Chrome as the supported POS terminals, which is exactly the claim's 'standard iPad' example, on vendor product documentation (grade B) as required for a differentiator yes. source |
| commercial-export-customer-and-loyalty | unknown (grade F) - 'Loyalty data "can be accessed from the back office," but bulk machine-readable export of guest records, point ledgers and gift-card liability is not documented.' | resolve-to-partial | The Customer Info article documents an explicit Export button on the customer list, and that list carries Loyalty Points and Gift Card Number columns, with format options XLSX/CSV/PDF documented on the Exporting Reports article - so bulk machine-readable export of guest records with loyalty balances is documented, not merely back-office viewing. It stays partial because the Gift Card Report article documents no export control and no aggregate liability figure, and point ledgers are not exported. source |
| commercial-post-termination-export-window | unknown (grade F) - 'no Linga terms of service, EULA, or MSA is publicly retrievable (they 404 at conventional URLs), so no post-termination data-retrieval window is documented either way.' | resolve-to-no | Both documents are public via the footer Legal block - /sales-terms-and-conditions and /end-user-license-agreement. The Sales Terms' termination clause states access 'shall immediately terminate and cease' and obliges the customer to stop use and delete LINGA Items, with no retrieval period anywhere in either document. That is a documented immediate cutoff, i.e. positive evidence against the claim, not absence of evidence. source |
| commercial-data-ownership-clause | unknown (grade F) - 'No retrievable terms document, so merchant data ownership and constraints on vendor use or resale are entirely undocumented publicly.' | resolve-to-yes | The terms are retrievable at lingapos.com/sales-terms-and-conditions via the footer Legal block. They contain both elements the claim requires: an express customer retention of all right, title and interest in inputted/stored data, and a disclosure right limited to aggregate or de-identified form, with LINGA's broader use right scoped to service provision/performance telemetry for improvement and diagnostics. This is a primary legal instrument, so grade A supports a differentiator yes. source |
| commercial-privacy-dsar-tooling | unknown (grade F) - 'the Marketing Settings, Marketing Customers, and Customer Info KB articles document no in-app tooling for locating, exporting, or deleting an individual guest's records, and no published DPA was located.' | resolve-to-partial | Re-read the Back Office Customers - Customer Info article, which does document exactly those actions: a searchable customer list, an Export button downloading customer data in a selected file format, a Delete Customer action, and per-customer metrics with full transaction history. The prior finding of absence was wrong on the product side. It stays partial because deletion is an inactivation rather than erasure, no DSAR workflow or verification exists, and the Privacy Policy handles rights requests by manual email with no DPA published anywhere. source |
| digital-upsell-engine | no / B / "The Products/Items article enumerates the complete Add/Edit Product form - POS display b" | downgrade-to-unknown | Re-fetched the cited Add/Edit Product article: it carries no completeness language, and a second extraction returned fields the first pass had missed (Standard Color, image upload, Conversational UI at POS, Cut And Modify, Number of Slices, Tare Group, Default Tare), so it cannot carry an exhaustive-enumeration argument. The attach-rate leg rested on the Reports section index, which is a directory-style listing. Linga's retail vertical page separately advertises POS upsell prompts, so absence is not established either way. source |
| reliability-local-transaction-engine | no / B / "The only architectural statement Linga publishes about the ordering path is in POS: Off" | downgrade-to-unknown | Re-fetched POS: Offline Mode in full. It states that the POS-to-redis link stops and that payments and clock-ins are stored locally and posted to the server on reconnect - but it never states where redis runs, never frames the architecture, and makes no completeness claim, so it cannot support a positive assertion that no local engine exists. The second leg of the argument was that no other page describes one, which is absence of evidence. Device-side capture and replay of orders and payments is itself arguably local transaction handling. source |
| extensibility-webhooks-push | no / B / "Now affirmatively established rather than merely undocumented. Pandium, an inde" | upgrade-to-partial | Refuted by the vendor's own developer reference, which the prior pass never reached: developer.lingapos.com documents Open Order and Close Order webhooks delivered as JSON by HTTP POST, so the prior finding that "integrators must poll" is false. Not a yes, because the claim asks for the order lifecycle (created, modified, paid, voided, refunded) and only order-open and order-close fire. Pandium is a third-party integration platform; its connector capability matrix was also mis-graded B, which is reserved for vendor product documentation. source |
| payments-processor-choice | yes / B - "UPGRADE ONLY TO PARTIAL, not to yes (the verdict enum has no upgrade-to-part" | downgrade-to-partial | Citation staleness re-check. The PNC release is not deleted - the recorded URL was missing its ',-LINGA' suffix; I retrieved the full release at investor.pnc.com and confirmed the 'first processor agnostic' wording verbatim. Two things then defeat the yes. First, grade: the sentence is 'About Linga' press-release boilerplate, grade D vendor marketing, and a differentiator yes requires A or B. Second, evidence: the claim asks for a documented list of supported processors or gateways and none exists first-party - LINGA's Integration Hub lists ten integrations (DoorDash Drive, Deliverect, Chowly, Uber Eats, Octopus Bridge, ADP, Restaurant365, Shogo, Dash Solutions, Factor4) with zero processors, the developer docs at developer.lingapos.com have no gateway or processor configuration page, and the Sales Terms and Conditions document a three-year Hybrid Payments Merchant Processing tie-in with a 100% cancellation fee in months 0-3. The prior cell's own note said 'UPGRADE ONLY TO PARTIAL'; partial is now recordable directly. source |
| reporting-public-api | yes / B - "Reporting endpoints are explicitly documented: Transactions Reports (by date rang" | upheld | Citation staleness re-check, and a re-evidencing rather than a value change. The cited host is not dead: developer.lingaros.com returns a 16-byte Cloudflare 'error code: 502' on every path, but its root 302s to developer.lingapos.com, which serves the same Docusaurus corpus. I retrieved /docs/doc-paid-reports/ (200, 74,252 bytes) and read the body, after calibrating the host with a fabricated path that returned a real nginx 404 at 153 bytes. The reporting endpoints the researcher described are present and I quote them in the corrected note. Two corrections to the reasoning: the doc set is an API reference with per-endpoint URLs, headers, parameters and curl examples, which is grade A rather than B; and the researcher's caveat that self-serve credentials are unavailable is wrong - the Introduction page walks a merchant through generating a Developer API key from the Licenses screen with no agreement step. Coverage of orders, payments, menu and labor is all enumerated in the published sidebar. Value stands at yes; citation and grade corrected. source |
| extensibility-public-api-docs | yes / B - "Affirmatively false. developer.lingaros.com/docs/ is publicly readable with per-e" | upheld | Citation staleness re-check, and a re-evidencing rather than a value change. The recorded 502 was a stale host, not bot mitigation and not a gate: developer.lingaros.com/ 302s to developer.lingapos.com, where /docs/docs-schedule-api-token/ returns 200 at 68,930 bytes to a plain browser user agent with no credentials, no NDA and no sales call, and the body carries real endpoint documentation (auth/login POST with a parameter table, nstore/list GET with a token header, curl examples). I calibrated the host first with a fabricated path inside /docs/, which returned a genuine nginx 404 at 153 bytes, so a soft 404 could not have passed as a hit. This retires the previous entry's own admitted weakness, that it confirmed the docs only through search-engine extraction and a third-party connector doc. Grade raised from B to A because the pages are per-endpoint API reference. Value stands at yes. source |
| payments-tip-adjust | partial / B / "A "Batch/Tip Adjustment" function is confirmed to exist — it is named directly in the Offl" | upheld | Upheld at partial; citation repaired and a quotation corrected. The cited article 404s. Its successor carries the operations list verbatim and still names Batch/Tip Adjustment, so the evidence for the cell is intact — but the record's transcription of that list had dropped "Open Cash Drawer", which is now fixed against the live text. source |
| payments-house-accounts | partial / B / "The Offline Mode KB confirms House Account is a real object type in Linga: "Memberships, C" | upheld | Upheld at partial; citation repaired. The load-bearing sentence survives verbatim on the successor article, so the object's existence is still evidenced and the named shortfall — no credit limits, balance or statements — is untouched. Worth recording that this cell briefly looked like it had lost its evidence entirely: the rewritten sibling pos-payments-offlinemode says only "Membership cannot be created" and drops Customers and House account, so re-pointing to that sibling would have deleted the basis for this cell without changing its value. source |
| guest-loyalty-offline-behavior | partial / B / "The Offline Mode KB states "Memberships, Customers and House account can't be created" whi" | upheld | Upheld at partial; citation repaired. The enrollment-blocked sentence survives verbatim on the successor, and nothing there addresses lookup, accrual or redemption for an existing member, so the shortfall that holds this at partial is unchanged. source |
| labor-offline-time-punch | partial / B / "The Offline Mode KB directly documents the behavior: "application should allow to perform " | upheld | Upheld at partial; citation repaired. The quotation survives verbatim on the successor, including the Break in/out clause — which matters, because the rewritten sibling pos-payments-offlinemode mentions clock-in only and says nothing about breaks at all. The duplicate-and-loss half of the claim remains undocumented, so the value does not move. source |
| reliability-offline-card-auth | partial / B / "The Offline Mode KB documents card payment processing while offline via a Magtek reader ("" | upgrade-to-yes | Upgraded partial to yes while repairing a dead citation, which is why it was re-read at all. The old basis (a Magtek sentence) does not exist on any live article and is withdrawn rather than moved. The sibling Restrict Offline Payment article documents the mechanism the claim asks for — offline card acceptance under an offline limit, queued and processed on reconnect via a prompt, settled through the Batch screen — which is store-and-forward and not cash-only fallback. Held at B, and the debit-card warning and the unstated cap basis are written into the note. source |
| reliability-offline-kds-printing | yes / B / "The Offline Mode KB states that with the toggle enabled and printers on the intranet, "the" | upheld | Upheld at yes, and strengthened. The citation was dead; the successor carries the printer sentence verbatim and additionally names KDS explicitly while in Offline mode, which closes the one caveat the prior note carried. Recorded as a survival with its trap: a sibling article states the same idea under a condition (network available, toggle on) that would not support the claim. source |
| reliability-sync-conflict-handling | no / B / "The dedicated Offline Mode article documents the sync model and it contains no conflict re" | upheld | Upheld at no; citation repaired. The one-way transfer sentence survives verbatim on the successor and no conflict-resolution semantics appear on it or on the three sibling offline articles, so the basis for the no is intact on a live source. source |
| reliability-local-transaction-engine | unknown at F. The only architectural statement Linga publishes about the ordering path is POS: Offline Mode, which names a mediating redis server ("The POS to redis server will also stop") without saying where it runs, and describes per-device offline capture - "The payments, employee clock in, etc. will be store | resolve-to-no | Analyst proposed no at B from https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-8-5-2025; adversarial pass upheld it. pos-offline-mode-8-5-2025.txt line 1 matches; quote verbatim. Read whole. The article defines offline as loss of internet/server reachability ('When the system is reconnected to the internet, the actions stored locally during offline mode will be posted to the server'; 'if the server is down during a payment transaction - or when there is no internet connection - the Offline Mode toggle will be enabled by default') and then describes the entire in-store topology in that state: each device stores its own actions locally, the LAN still reaches printers, KDS and the IP cash drawer, and 'Any Checks from a POS Node will not be reflected in other Nodes' because 'the POS to Redis Server will also stop'. That is structural, not merely a sync remark: node-to-node check sharing exists only through a server that disappears with the WAN, so nothing in the building runs the ordering path. Counter-evidence checked: back-office-2024-general-application-settings.txt 'Enable Intranet sync ... allow the systems to communicate via local network connection including printing while in Offline mode' - the offline article states what that LAN reaches ('the local network connects all devices, (Printers) and KDS') and still says checks are not shared, so it is device-to-peripheral, not an engine. 26-02-001 'The Redis URL has been changed to Sync servers in V2' names the mediator as a URL-addressed server. 'local server', 'on-prem', 'edge server', 'master device' occur zero times in KB and lingapos.com. source |
| commercial-pci-dss-4-controls | unknown at F. Read the published Sales Terms and Conditions and the End User License Agreement in full (neither mentions PCI DSS, compliance obligations for the cardholder data environment, MFA, or script integrity) and the Privacy Policy (PCI DSS is not referenced). On the product side, read the Back Office EMV | resolve-to-no | Analyst proposed no at B from https://support.lingaros.com/portal/en/kb/articles/pos-sign-in-screen; adversarial pass upheld it. pos-sign-in-screen.txt line 1 matches; the quote is verbatim across line breaks ('Enter / the same Email Address and Password to access the web portal'). The claim is that the vendor DOCUMENTS the v4.0.1 controls in effect (MFA on POS/BO logins; 6.4.3/11.6.1 script integrity). The KB documents the complete BO sign-in procedure (email + password, Forgot Password) and POS log-in (PIN or Face ID) with no second factor, and - the quotable contradiction - the Password Rules in Creating a New User: 'Between 6 and 12 characters', a 12-character MAXIMUM where v4.0.1 Req 8.3.6 sets a 12-character minimum; a vendor whose documented password rule is below the v4 floor is not documenting v4 controls as in effect. Grep MFA/multi-factor/two-factor/2FA/OTP across 606 KB files and lingapos-com: every OTP hit is consumer-facing (OLO/VRT/Custom App sign-up OTP, optional NMI 3D Secure), none is merchant CDE access. 'PCI' on lingapos.com appears only as 'Accept fast, secure EMV and PCI-compliant payments.' (cigar-lounge page) with no DSS version or control; sales terms, EULA and privacy policy contain no authentication or PCI text. This is the weaker of the two accepts: it rests on a complete documented procedure plus a contradicting rule rather than an 'MFA not supported' sentence. source |
| menu-pricing-dynamic-pricing | unknown at F. On support.lingaros.com, Back Office: Products/Items - Products/Items shows a "Price Level Settings" toggle with a Level field on every menu type except Combo Item, and Back Office: Third Party Integrations Settings lists "Platform Price Level" among the integrations (Chowly, Compeat, Deliverect, Do | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/back-office-2024-third-party-integrations-settings; adversarial pass upheld it. Quote verified verbatim in linga/back-office-2024-third-party-integrations-settings.txt (URL line 1 matches). The Platform Price Level table maps each integrated ordering platform to one of nine per-item price levels plus a modifier mark-up percentage, and products-items confirms 'The Price Level Settings toggle appears for all Menu Types except Combo Item'; february-11th-2025 moves the same per-platform price level into Integration Hub for Deliverect and Chowly. That is rule-based price variation by channel, the one leg of the claim that is documented. Re-grepped the corpus for happy hour, day part pricing, time-based price, surge, price schedule: only Day Part appears, as a reporting dimension (pos-revenue-center), and the time windows on Upcharges/Discounts (pos-available-time-discount-display-groups-and-upcharges) are add-ons, not base-price rules. No floor/ceiling guardrail anywhere. Thin but real: partial B holds. source |
| kitchen-prep-time-pacing | unknown at F. Checked support.lingaros.com (Zoho Desk portal, JS-rendered): Back Office > Settings > Hardware > Kitchen Printers is the entire KDS configuration surface documented and its fields are device model/name/IP, Expo Device (Expo Printer IP, Queue Device IP), allowed Service Types, Print ToGo Items, Appl | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/26-03-001-release-notes; adversarial pass upheld it. Both quote segments verified in linga/26-03-001-release-notes.txt. Per-item Preparation Time is a field on Products/Items ('use the arrows to set the Prep Time'), KDS Configuration references 'item-based prep time', and 26.03.001 sends Item Preparation Time to the POS/KDS for Sort by Due Time. Re-grepped for stagger, cook time, fire time, hold time: the only hold construct is pos-holding-an-order (manual/automatic hold by elapsed time, not by cook-time difference), and 26.08.001's fix confirms the KDS sorts orders by due time, not by item prep time. Nothing documents staggering item display so items finish together; the Sequential Flow feature (26.03.001) moves whole orders between stations. Partial B holds. source |
| kitchen-channel-pause-propagation | unknown at F. Checked on support.lingaros.com: (a) Back Office > Settings > Integrations > Third Party Integrations Settings, which enumerates the per-partner fields for Urban Piper, DoorDash, Uber Eats, Chowly, Compeat, Deliverect, PayPal, Restaurant 365 and Yemek Sepeti - the marketplace-facing controls are man | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/deliverect-integration; adversarial pass upheld it. Quote verified in linga/deliverect-integration.txt. The only automatic availability propagation is via the Deliverect middleware partner (also november-12-2024: 'Deliverect - 86 list snooze time for Menu item'); the proposal names Deliverect as the shortfall correctly. Checked pos-uber-eats-integration.txt and chowly-integration.txt for out of stock / snooze / 86 / availability: none (Chowly even says 'Suspend Until - This feature is currently not available'); urban-piper has none. Store pause: re-grepped busy mode, pause store, store closed, store status: only OLO hides hours when the store is closed and Yemek Sepeti has a manual 'Is Restaurant Open' toggle - no pause propagation to DoorDash/Uber Eats/Grubhub. Partial B, partner-dependent, holds. source |
| kitchen-pizza-fractional-display | unknown at F. Re-examined on support.lingaros.com rather than the vendor blog. Back Office > Products/Items > Cut and Modify does document a fractional-portion pricing model - a 'Slice Fraction' whose 'Modifier Price Percentage' is raised or lowered per fraction - so sectioned portions are a real configured objec | resolve-to-partial | Analyst proposed yes at B from https://support.lingaros.com/portal/en/kb/articles/26-03-003-release-notes; adversarial pass changed it to partial. 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. source |
| kitchen-guest-ready-notification | unknown at F. Checked two admin screens on support.lingaros.com. Back Office > Settings > Store > Notifications enumerates ten alert types - Discount, Void, Max No Cash Drawer Accessed For No Sale, Time Clock, Daily KPI, End Of the Day Alert, Wait List, Sale Recap Report, One Page PDF, Offline Payment - all sent | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/back-office-2024-kds-configuration-template-settings; adversarial pass upheld it. Both quote segments verified in linga/back-office-2024-kds-configuration-template-settings.txt. KDS completion triggers a per-service-type guest SMS, but the same article gates it: 'only available to users with an SMS texting license', and octopus-bridge and 26-04-001 say the Text add-on 'must be purchased and enabled' - so the claim's 'without a separate product purchase' is not met. The Queue App (26.07.001: 'real-time synchronization of order statuses with KDS EXPO') is a native status board synced to KDS bumps, but nothing states whether it is included or separately licensed, so it cannot lift this to yes. Octopus pickup notification (26.04.001) is partner-routed. Partial B holds. source |
| delivery-address-validation | unknown at F. Checked three support.lingaros.com articles. POS: Phone / Web Orders - New Tab documents the order row's 'Delivery address field ... Only a partial address is shown on the screen. Tap on the address to see the full address' and a 'Zone: Identifies the Delivery area or region assigned to the Order', | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/may-27th-2025-release-notes; adversarial pass upheld it. Quote verified in linga/may-27th-2025-release-notes.txt. The bug-fix line establishes that out-of-zone delivery orders are meant to be rejected. It is corroborated beyond the analyst's citation: pos-phone-web-orders-driver-tracking.txt defines the order column 'Zone – The number representing the Zone (per Store settings) that contains the Delivery Address', and zones are drawn on a map ('Select a form to draw the zone ( Circle , Shape , Line , or Rectangle )', delivery-application-settings), so the address is being located against map geometry. What is still missing: no article names the geocoder, describes address autocomplete/validation at entry, or shows the customer-facing out-of-zone message; the Google Maps references are for driver ETA/directions. A bug fix plus an inferred mechanism is enough for partial, not yes. Partial B holds. source |
| delivery-86-sync | unknown at F. Checked POS: Operation - 86 List on support.lingaros.com, which names the surfaces item quantity reflects across: 'Whenever any Sale takes place in POS then the Quantity of this Item will be reduced in iPad, Zenpepper and POS', and 'the Quantity changes occur when there is a parallel Sale that takes | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/deliverect-integration; adversarial pass upheld it. Quote verified in linga/deliverect-integration.txt. Automatic item-level out-of-stock push exists only through Deliverect (partner correctly named as the shortfall); 26.05.001 documents the native 86 List countdown across POS terminals and pos-operation-86-list extends it to iPad/OLO/ZenPepper - Linga channels only. Re-checked pos-uber-eats-integration.txt (no stock/86 language at all), chowly-integration.txt ('Suspend Until - This feature is currently not available'), urban-piper and third-party-integrations-settings (manual Publish only). Modifier-level 86 and restore-on-availability are not documented for Deliverect ('snooze time' only). Partial B holds. source |
| delivery-injection-error-visibility | unknown at F. Checked on support.lingaros.com: (a) Back Office > Settings > Integrations > Third Party Integrations Settings, which lists every per-partner field for nine partners (API keys, Location/Account IDs, publish buttons, enable toggles) and contains no health, status, log or alert element; (b) Integratio | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/february-11th-2025-release-notes; adversarial pass upheld it. All four quote segments verified in linga/february-11th-2025-release-notes.txt. Per-partner menu-sync failure notifications, an Integration Hub Audit Log, and per-integration Active/Inactive state (integration-hub-user-manual) are documented. Re-grepped for failed order, rejected order, order not received, inject: no hits; integration-hub-user-manual's order content is only the Order Webhook page. april-21st-2025 adds 'Automating error logging process so our development team will be emailed in the event of any failures' - vendor-side, not operator-facing. Failed inbound order injections and per-channel connection health remain undocumented. Partial B holds. source |
| digital-account-saved-payment | unknown at F. Checked 2026-08-07 on support.lingaros.com: the Online Ordering Stores settings article (back-office-2024-online-ordering-stores), which enumerates the merchant-configurable surface of first-party OLO, documents ordering hours, delivery/pickup/curbside, ASAP and Future Order, coupon code, tips, serv | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/26-06-001-release-notes; adversarial pass upheld it. Quote verified in linga/26-06-001-release-notes.txt. OLO accounts (Sign Up with Facebook/Google, Allow Guest Checkout in back-office-2024-online-ordering-account) and tokenised saved cards ('Save the card for faster check out', pos-partial-payments-in-online-ordering-olo; 26.02.001 cross-channel card deletion) are documented. Read the OLO Account article in full: no saved-address field; the customer record holds a single mailing address. Reorder: 'Repeat Order' is documented only on the POS Customer Profile screen; 26.08.001's 'Repeat Orders' bug sits among POS/hardware fixes; OLO documents an Order History screen but no reorder action. Partial B holds. source |
| digital-checkout-pci-sca | unknown at F. Checked 2026-08-07: the Online Ordering Stores settings article on support.lingaros.com documents online checkout payment configuration as "Online Payment - If Enabled, the Sale and Authorization checkboxes appear" (Sale batches automatically, Authorization batches manually) plus accepted card brand | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/26-06-001-release-notes; adversarial pass upheld it. Both quote segments verified in linga/26-06-001-release-notes.txt. Hosted card capture and 3DS exist only via the NMI gateway partner's iframe, behind a Super Admin toggle that defaults to the legacy flow, with 3DS 'optional' - the proposal names NMI as the dependency correctly. Re-grepped PCI / 3D Secure / hosted payment across both corpora: the only PCI text is a marketing line on lingapos-com/restaurant__cigar-lounge.txt ('Accept fast, secure EMV and PCI-compliant payments', grade C, no DSS version); sales terms and EULA carry no PCI or script-integrity statement. Partial B holds. source |
| guest-loyalty-consent-management | unknown at F. Checked 2026-08-07 on support.lingaros.com. The Customers > Customer Info article enumerates the complete Add/Edit Customer form - General (first/last name, phone, email, gender, DOB, nationality, anniversary, gate code, customer ID, notes, photo), Customer Store, Loyalty (enrollment Yes/No, balance | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/back-office-2024-enterprise-settings-addons; adversarial pass upheld it. Quote verified in linga/back-office-2024-enterprise-settings-addons.txt. The SMS Loyalty flow is a genuine opt-in capture for one channel: invite text, an explicit confirmation reply step, thank-you text, gated by 'Enable SMS Loyalty Confirmation ... Twilio Number' (retail-back-office-admin-accounts). Re-grepped opt-in, opt-out, unsubscribe, STOP, consent, TCPA: no marketing opt-in/unsubscribe handling anywhere (the only 'consent' hits are ADP data-transfer consent and the EULA); Marketing > Settings holds only member-type thresholds; Customer Info has no consent field. Timestamp, source of consent and cross-channel revocation are all absent - this is the thinnest partial in the set, resting on an enrolment confirmation rather than consent management. Kept as partial because a documented per-channel confirmation step is a real, if minimal, consent capture; the parent may reasonably prefer unknown. source |
| labor-minor-labor-rules | unknown at F. Checked 2026-08-07 on support.lingaros.com: Store Scheduler Settings enumerates the store's labor configuration - start day of week, currency, timezone, time/date format, temperature unit, Default Mealtime, Default Break Time, overtime Hours per day and Hours per week with pay multipliers, and holid | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/back-office-2024-payroll-report-settings; adversarial pass upheld it. Quote verified in linga/back-office-2024-payroll-report-settings.txt. A store-level 'Minimum Age' rule pairing an age in years with a mandatory hours limit exists, and the employee record carries Date of Birth (employees-scheduler), so an age-based maximum-hours rule is configurable. Re-grepped minor, school, Minimum Age: the only other age constructs are guest-facing menu age restrictions. The setting sits under Payroll Report Settings whose own note reads 'Based on Payroll Report settings, the report will function accordingly' - so it may only drive payroll reporting; no scheduler or time-clock article documents enforcement at schedule build or clock-in, and prohibited windows / school-day limits are absent. One-sentence evidence, but it is an explicit vendor-documented age+hours rule: partial B holds. source |
| inventory-86-auto-sync | unknown at F. Checked support.lingaros.com: the Inventory Item article says only "If an Item goes below the Par Level, you will get a Low Stock notification"; the Low Stock article (/kb/articles/back-office-2024-inventory-low-stock) lists below-par items by vendor and offers Create Purchase Order, with no mention | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/26-05-001-release-notes; adversarial pass upheld it. All three quote segments verified in linga/26-05-001-release-notes.txt. Automatic 86 at zero count propagates across POS terminals (26.05.001), iPad/OLO (pos-operation-86-list) and to Deliverect-connected delivery menus (deliverect-integration) - Deliverect is named as the only third-party path. The trigger is a manually maintained menu-item count, not a component ingredient: inventory-inventory-item says only 'If an Item goes below the Par Level , you will get a Low Stock notification', inventory-low-stock offers purchase orders, and no article links inventory depletion to the 86 List (grep for 86 in inventory articles: zero hits). Partial B holds. source |
| reporting-api-not-upcharged | unknown at F. Re-checked www.lingapos.com/payment-plans on 2026-08-07: it advertises "three flexible plans" but details only the Complimentary Hardware Plan (equipment free against a 3-year Hybrid Payments merchant agreement plus 3-year LINGA SaaS) and publishes no dollar figures or feature-by-plan matrix. On the | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/retail-back-office-enterprise-settings-addons; adversarial pass upheld it. All three quote segments verified in linga/retail-back-office-enterprise-settings-addons.txt. Raw-data access via report export and self-service API key generation (Back Office / Integration Hub, any user with the Developer API Key role) are included with no enterprise-only gate. But the same article makes API calls a metered 'Developer API License' bought in request-count blocks ('displays count purchased by you by default'; $1 per 100 requests, auto-renew below 50) - a usage surcharge the claim excludes. Note the pricing text is in the Retail article; the restaurant Enterprise Settings - Addons article shows only 'Copy the API key ... or Generate a New API Key' with no license section, and developer.lingapos.com (earlier 'Free Edition 250 credits/24h') was 502 today, so whether an included allowance exists is unresolved. Partial B holds. source |
| multi-location-central-labor-policy | unknown at F. Walked /kb/linga-pos/back-office/scheduler (Introduction to Scheduler and Adding It To Your Account, Scheduler, Employees, Requests, Messaging - shift management, time-off and swap requests, staff messaging, no overtime or break rule), /kb/linga-pos/back-office/user-management (10 articles: Roles, R | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/pos-time-clock; adversarial pass upheld it. Quote verified in linga/pos-time-clock.txt. Break rules are configured per store (Payroll Report Settings > Manage Breaks) and enforced at the POS time clock with a manager override - terminal enforcement of one labor rule is documented. Overtime is configurable per store (Overtime Settings; 26.07.001 adds a bi-weekly rule) but only for pay calculation (employee-report), with no terminal block. Enterprise Settings articles (Account, Royalty/Franchise, Addons) carry no labor section, so no location-group inheritance; predictive scheduling is absent. Partial B holds. source |
| extensibility-api-access-cost | unknown at F. developer.lingaros.com 302s to developer.lingapos.com; read /docs/introduction (API keys are self-generated in the live Back Office via Licenses > Developer API > Key Generator) and /docs/api-limit, which meters API calls in credits deducted by 'the intensiveness of the performance, and the memory u | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/retail-back-office-enterprise-settings-addons; adversarial pass upheld it. All three quote segments verified in linga/retail-back-office-enterprise-settings-addons.txt. No plan upgrade is needed to generate a key (Enterprise or store level since january-7th-2025; role-gated per integration-hub-user-manual), so the 'upgraded plan' leg is met. Calls, however, are sold as an explicit per-request license ('License Price ... For an API Request Count of 100 , then a License Price of $1 appears') - a surcharge, and the article is explicit enough that a no would be arguable if no included allowance existed; the earlier developer-portal 'Free Edition 250 credits/24h' reading (unreachable today, 502) and the restaurant Addons article's lack of any license section keep this at partial rather than no. Partial B holds. source |
| commercial-module-unbundling | unknown at F. lingapos.com/pricing, /pricing/plans?storetype=Single%20Store and /pricing/plans?storetype=Multi+Store all render their plan tables client-side and returned only navigation and header markup through a JS-rendering fetch, so no plan contents, module list or per-module price could be read. lingapos.co | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/retail-back-office-subscriptions-upgrades-summary; adversarial pass upheld it. All three quote segments verified in linga/retail-back-office-subscriptions-upgrades-summary.txt. A la carte add-on purchase per station/per site with separate billing lines is documented, and per-module licences (OLO, Text, Integration Hub) are confirmed elsewhere. Cancellation independence is not: the article documents plan downgrade ('Some of your addons are not available in your new plan') but no add-on removal flow; lingapos-com/sales-terms-and-conditions.txt says 'SaaS Service Fees are not refundable. LINGA shall not prorate SaaS Service Fees if Customer terminates a Sales Order before the end of the month' and terms auto-renew, and cancellation goes through a Cancellation Request Form - none of which addresses dropping one module without repricing. Partial B holds. source |
| commercial-wcag-kiosk-accessibility | unknown at F. Read lingapos.com/solutions/kiosk in full - it describes the self-ordering kiosk in operational and form-factor terms ('wall-mounted and countertop options') and contains no accessibility statement, ADA reference, WCAG level, VPAT/ACR, screen-reader support, audio jack, or tactile/keypad navigation | resolve-to-partial | Analyst proposed partial at B from https://support.lingaros.com/portal/en/kb/articles/october-14th-2025-release-notes; adversarial pass upheld it. Quote verified in linga/october-14th-2025-release-notes.txt; november-17th-2025 repeats it for VRT. Re-grepped VPAT, WCAG, accessib, ADA across both corpora: the only accessibility statements are these two release-note lines naming colour contrast and readable content for OLO / Call Center / VRT; the kiosk articles (kiosk-addon-settings, 26.07.001 idle advertisements) contain no non-visual access mode; the prior rationale's enumeration of the lingapos.com Legal/Resources footer found no VPAT/ACR. None of the claim's three named elements (published VPAT/ACR, WCAG 2.1 AA, tactile/audio kiosk mode) is met, so this is a weak partial resting on a vendor-documented accessibility effort for the consumer web surfaces only; it is not unknown (the effort is documented) and not no (the corpus does not enumerate published conformance documents). Partial B holds. source |
| hardware-usable-after-churn | unknown at F. Re-fetched www.lingapos.com/payment-plans on 2026-08-07: the Complimentary Hardware Plan is "Get ALL Your Equipment FREE" conditioned on a "Hybrid Payments 3-year Merchant Processing Agreement, and 3-year LINGA SaaS", with pricing routed to a sales rep. Nothing on that page or in the support portal | resolve-to-partial | Analyst proposed partial at B from https://www.lingapos.com/sales-terms-and-conditions; adversarial pass upheld it. sales-terms-and-conditions.txt (line 1 = the URL, 62.7 KB). Appendix B L89 '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.' L33 termination reclaims only 'the Services ... Work Product, LINGA IP and LINGA Proprietary Information and all other items (collectively, LINGA Items)' - Hardware is a separately defined term and is not listed; there is no hardware-return-on-termination clause anywhere (grep 'return' hits only the 60-day Return Policy L95 and the Complimentary Hardware 'may return ... for up to sixty (60) days' L103). The only remote-disable right is L17 'LINGA may terminate this Agreement immediately and/or deactivate any and all Services' and L37 'Suspension of Service' - both act on Services, not the device; the EULA (end-user-license-agreement.txt) has no remote-disable or hardware clause. Contradiction check: L92 'Customer shall not be entitled to (i) equip the Hardware with software that does not correspond to LINGA's factory default specifications ... unless expressly approved by LINGA in writing' is a live covenant against exactly what the claim asks, and L100's Embedded Software licence is LINGA IP whose right to use ends under L33; L33's survival sentence does not say whether L92 survives. So ownership passes and nothing reclaims or bricks the unit, but the vendor contractually restricts loading other software and does not say the restriction lapses - partial is the honest value, not yes. KB (linga/) has nothing on device ownership beyond store-licence sign-out. Grade B vendor legal text. source |
| hardware-rma-sla | unknown at F. Re-checked www.lingapos.com/payment-plans (2026-08-07), which markets free equipment against a 3-year commitment and addresses neither warranty term nor replacement procedure, and walked support.lingaros.com /kb/linga-pos/hardware-and-networking (Bluetooth Scanner, POS Terminal Requirements, Hardwar | resolve-to-partial | Analyst proposed partial at B from https://www.lingapos.com/sales-terms-and-conditions; adversarial pass upheld it. sales-terms-and-conditions.txt L97 verbatim: 12-month Defect Warranty, replacement as sole remedy. L95 Return Policy: return at Customer's own expense; advance replacement only 'If LINGA agrees to provide replacement hardware before Customer has shipped the return hardware', with a 30-day return window whose breach lets LINGA 'charge Customer the price of the advance replacement part plus shipping costs, or b) suspend Customer's access to SaaS Services'; out-of-warranty 'repaired or replaced at LINGA's then standard price'. L91 adds a 14-day DOA inspection window. No sentence in the 62 KB file states a turnaround (grep next.day, business day, hours, turnaround: none); L98 passes through manufacturer warranties only 'as permitted by the manufacturer'. KB grep (warrant, RMA, advance exchange, swap) hits only shift-swap scheduler articles; hardware__linga-mobile.txt and payment-plans.txt carry no warranty text. Claim = warranty term AND replacement SLA with stated turnaround; only the first half is published. Partial B stands. source |
| reliability-onsite-install | unknown at F. Checked lingapos.com/partners/become-a-partner, which documents a channel - 'Gain access to reseller, referral, and white label partner programs' with 'Partnership Levels' naming 'POS specialists' and 'Hardware Resellers' and offering 'world-class training resources' - but never says the delivery is | resolve-to-partial | Analyst proposed partial at B from https://www.lingapos.com/sales-terms-and-conditions; adversarial pass upheld it. sales-terms-and-conditions.txt: the definitions sentence makes 'implementation, application branding and configuration services ... ( "Professional Services" )', so Appendix C governs implementation. L118 'Location of Services' verbatim as quoted: default venue is 'any facility owned or operated by LINGA and/or its subcontractors'; on-site is 'If Customer requests LINGA to perform the Professional Services at any Customer sites', with LINGA bound to site H&S policies, able to 'suspend or refuse to deliver Services if conditions at the site are ... unsafe or hazardous to LINGA employees required to work on that site', and travel reimbursed on prior written approval. L27 'Implementation services shall be provided solely by LINGA or LINGA's approved service provider'. Nearby contradiction check: L26 'Customer is solely responsible for preparation and maintenance of its site(s)' is site-prep, not an exclusion of on-site services; no on-site exclusion exists. Weakness I weighed: this is contract machinery for an on-request option, not a published on-site install/go-live offering - no lingapos.com page (contact-support, become-a-partner, get-started, solutions) and no KB article (grep onsite, on-site, go-live, in-person, technician, site visit: zero product hits) describes one. That is the named shortfall, and it keeps this at partial rather than yes; I do not push it to unknown because the vendor's own legal text does establish that LINGA employees/subcontractors perform implementation at customer sites when asked. Grade B. source |
| guest-loyalty-campaign-attribution | unknown at F. Checked 2026-08-07 on support.lingaros.com: Marketing > Manage List exposes exactly two campaign metrics - "Customers Targeted - The number of customers targeted" and "Sent Targeted - The number of Emails sent to the target group" - which are send counts, not redemption or incremental sales. The Mar | resolve-to-partial | Analyst proposed partial at C from https://www.lingapos.com/solutions/marketing; adversarial pass upheld it. solutions__marketing.txt (line 1 URL matches) L55-58 '● Live Email Stats / Track open rates, clicks, and redemptions / ● ROI Dashboard / Measure how much each campaign brings in' and L98-103 'Integrated Promotions / See which promotions worked and which didn't. / Engagement Metrics / Track campaign open, click, and conversion rates. / Revenue Impact / Measure sales uplift from each communication.' - the analyst's quote is these lines joined with bullets, verbatim. This is the exact claim (per-campaign redemptions and sales attributable to the campaign) but on a feature page, grade C, and differentiator weight caps C at partial. KB check: back-office-2024-marketing-campaigns.txt lists only Status/Clone/Delete per campaign; back-office-2024-marketing-manage-list.txt only 'Customers Targeted' and 'Sent Targeted'; back-office-2024-discounts-report.txt has no campaign or promotion filter; grep ROI/uplift across linga/ finds nothing. The KB neither contradicts (no closed enumeration of campaign metrics) nor strengthens. Partial C with the shortfall 'no help-centre article documents the ROI dashboard or how redemptions tie to check totals' is correct. source |
| menu-pricing-upsell-prompts | unknown at F. Read three configuration surfaces on support.lingaros.com in full: Back Office: Products/Items - Products/Items (item fields cover POS button, name, PLU, prep time, category, description, menu type, cost type, price level, taxes, included / mandatory / optional modifier groups, availability, visibil | resolve-to-partial | Analyst proposed partial at C from https://www.lingapos.com/restaurant/quick-service; adversarial pass upheld it. Quotes verified: restaurant__quick-service.txt L84-88 'Upsell Tools / Maximize Revenue by Increasing Your Average Check Size / Elevate your check averages with smart upsell features, recommended tips, and seamless loyalty enrollment. / Offer Promos and Upsells at Checkout / Show offers on customer-facing screens to boost add-ons.' and retail__electronics.txt 'Point of sale prompts making staff and customers aware of upsell options like chargers, cases, or add-ons with core items.' / 'Easily connect products with compatible add-ons to simplify upselling.' The quick-service sentence is thin (a CFD offer display, which the CFD page describes as 'Add a promotional message to customer-facing displays', i.e. a store-level message); the retail/electronics sentence is the one that actually asserts item-linked prompts, so I moved the primary URL there and kept quick-service as supporting. KB check: grep upsell, up-sell, suggestive, cross-sell, recommended item, attach rate across 605 articles = zero hits; the item, kiosk and online-ordering settings walkthroughs (per the August rationale) show no upsell field, and the 25-report index has no attach-rate report - not a closed enumeration, so no contradiction, but no strengthening either. Present half = vendor asserts item-linked POS prompts and CFD offers; shortfall = retail-page claim only, nothing per channel, no attach-rate reporting anywhere, KB silent. Partial C stands. source |
| order-capture-qr-same-check | unknown (grade F) — 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 | resolve-to-partial | The record's prior rationale said no QR-menu-ordering article exists; it does. 'QR Code for Virtual Kiosk' documents the whole flow: QR codes are generated per table (Settings > Store > Table Layout > Print QR Code), the guest's OLO order is attached to that table and 'Orders can be displayed on IPAD screen by touching the related table on table layout screen', and the order object is shared both ways - 'New items can be added to an existing order through Online Ordering (by tapping the Add More button and selecting new items) or IPAD app'. Named shortfall keeping this off yes: the same article's 'Multiple Orders From the Same Table' section says 'Each person joining the table places their own order by scanning the QR Code of the table', i.e. several guests at one table produce several orders rather than one shared check. Capture 2023-02-09. ARCHIVE CAVEAT (203rd): support.lingaros.com serves a byte-identical 25,169-byte SPA shell for every path today and its Help Center API 401s on the portal's own orgId, so this article body was read from the Wayback capture named in the URL. source |
| order-capture-drive-thru | unknown (grade F) | downgrade-to-unknown | P3 retested and holds: 44/44 doc pages are in the corpus at 200 and doc-sync publishes the complete field-level check schema. Its taxPerServiceTypeTaxes object carries one key per service type and the set is closed at seven - qsrTax, barTabTax, toGoTax, deliveryTax, forHereTax, webOrderTax, dineInTax - with no drive-thru member. The check schema has no lane, window, order-point or pull-forward field of any kind, and 'order point', 'pay window', 'pickup window', 'tandem', 'pull forward' and 'headset' occur zero times in the whole corpus. www.lingapos.com/restaurant/quick-service does say guests 'pick up orders from their vehicles' - the vendor asserts vehicle pickup and I am not contradicting that; the claim is the three flow mechanics, none of which is evidenced. The only vehicle construct in the product is the Curbside Pickup order type. AUDIT (2026-09-04): The doc-sync argument is refuted inside doc-sync itself. Its own field table documents 'serviceType | string | TABLESERVICE, QSR, BARTAB' - a three-value set neither equal to nor contained in the seven-key taxPerServiceTypeTaxes map; TABLESERVICE is in no tax key and toGo/delivery/webOrder/dineIn are in no serviceType value. The seven keys are never in the field table at all; they appear ONLY inside sample payloads from a single Turkish store dated saleOpenDate '08-Apr-2020', and the API publishes GET /store/{id}/getServiceTypesByStore, proving service types are per-store configuration read at runtime and never a published enum. www.lingapos.com/restaurant/quick-service also positively asserts drive-thru - the same sentence the 195th session's audit used to overturn this cell. source |
| order-capture-drive-thru-timers | unknown (grade F) | downgrade-to-unknown | Same P3 census. The complete check schema's only time stamps are whole-order ones - saleOpenDate/saleOpenHour/saleOpenMin/saleOpenTime, orderDate/orderHour/orderMin, lastUpdateInMillisec, holdStartDate/holdEndHour. There is no segment structure (order time, window time, total time) tied to an order, and no drive-thru service type exists to segment. 'speed of service' and 'timer' occur zero times across the 137-page site and the 44-page API reference; the only elapsed-time surfaces are the KDS on-screen Timer and per-table elapsed time, neither segmented nor drive-thru. DEPENDENCY: if order-capture-drive-thru returns to unknown, this must follow it. AUDIT (2026-09-04): Downgraded by the author's own stated DEPENDENCY on order-capture-drive-thru, now returned to unknown. Independently its reporting half dies to the P3 subset defect the analyst itself reported: the API publishes exactly EIGHT report families against roughly 25 in the back office, so an API-side report absence cannot close a reporting claim. The check-schema half fails for the same reason as the parent cell. source |
| order-capture-voice-ai | unknown (grade F) — Read Back Office: Third Party Integrations Settings (Settings > Integrations > Third Party Integrations), which lists Chowly, Compeat, Deliverect, DoorDash, PayPal, Platform Price Level, Restaurant 36 | resolve-to-no | P4 retested and holds: the sitemap's 21 /solutions/* pages are all in the corpus and are the vendor's complete published product set, and the footer's own 22-item Solutions enumeration repeats that set on every page. No voice-AI product is among them, and Linga's phone-order product is explicitly human-staffed: agents 'place orders directly into your point of sale system'. 'voice' appears in the corpus only in blog SEO prose and 'artificial intelligence' zero times. On the second disjunct: Linga publishes a developer partner program, but nothing in the 44-page reference is a voice-AI partner program - the API agreement page renders client-side and is empty chrome, so nothing is read out of it. AUDIT (2026-09-04): The stated basis is overstated - the 21 /solutions/* pages are NOT the complete product set (the developer-docs footer lists Linga C-Kitchen and Linga Alerts, absent from the 21) - but the verdict does not need that enumeration. It rests on positive contradiction: Linga's own phone-ordering product page asserts live human operators who 'place orders directly into your point of sale system'. And the marketing-necessity test answers yes more clearly here than for any other capability class: 'artificial intelligence' occurs zero times corpus-wide as a product claim while the blog demonstrably chases AI SEO topics - a vendor writing AI content that omits its own AI voice agent is not plausible. source |
| order-capture-catering | unknown (grade F) | downgrade-to-unknown | The string 'catering' occurs ZERO times in the entire corpus - 44 API pages, 137 www pages (including all 17 business-type pages and all 21 solution pages), and 347 archived KB articles. doc-online-ordering publishes the complete order document; its only forward-dated construct is the boolean quoted here plus deliveryDetail.date, and the deliveryType example value is 'PICKUP'. There is no quote/proposal object, no deposit or balance-due field, and no event schedule separate from the order queue; the service-type set in doc-sync is closed at seven with no catering member. Both census surfaces P3 and P4 close; the KB floor is not doing the work. AUDIT (2026-09-04): 'catering' is indeed zero in the corpus, but that count is doing all the work and it spans the P2 FLOOR - 347 archived articles where a prior session read 605. The census half is the same doc-sync sampled-payload argument refuted on order-capture-drive-thru: doc-sync's own serviceType field table publishes a different and shorter list, and getServiceTypesByStore shows the set is per-store config, so 'the service-type set is closed at seven with no catering member' is false as stated. The prior rationale's reservation - that deposit and balance-due mechanics could sit in House Account or Membership - is untouched, and House Account is a published API surface, which cuts toward the reservation. source |
| payments-softpos-tap-to-pay | unknown (grade F) | downgrade-to-unknown | The iPhone half is closed by the P4 census and closed NEGATIVE: 'iPhone' occurs zero times in all 137 www pages and all 44 API pages, and 'Tap to Pay on iPhone' is a named Apple program no vendor leaves unmarketed. Note the KB article the record previously leaned on ('Linga POS is currently unavailable on iPhone') is NOT in the archived 347 - do not re-cite it from this corpus. The Android half stays genuinely open: 'Swipe, insert, and tap to pay are the current transaction capabilities' implies terminal tap, but the hardware answer allows 'a compatible Android device', which could be an NFC phone. 'softpos', 'tap to phone' and 'NFC' occur zero times corpus-wide, which is silence, not denial. One half negative, the other unevidenced, so unknown. source |
| payments-chargeback-tooling | unknown (grade F) | downgrade-to-unknown | 'chargeback' occurs zero times in the corpus and the only dispute machinery documented anywhere is the OLO 1.3 'Stripe Dispute Process', a deduction from the store's merchant account driven by the processor - disputes handled outside the POS. Suggestive but not sufficient: an in-product disputes dashboard would live in the back-office payment screens, which are KB-only surfaces, and P2 makes the KB a floor. The API reference cannot close it either - its Reports section publishes only eight families against the back office's ~25, so it is a subset, not a mirror. ARCHIVE CAVEAT (203rd): support.lingaros.com serves a byte-identical 25,169-byte SPA shell for every path today and its Help Center API 401s on the portal's own orgId, so this article body was read from the Wayback capture named in the URL. source |
| kitchen-all-day-counts | unknown (grade F) | downgrade-to-unknown | Corrects the record: the prior rationale asserted 'no article describing the KDS screen in operation' and 'Linga's KDS has no documentation at all'. There is one - a full KDS manual covering device definition, KDS Configuration, and both the Expo and Non-Expo screens element by element. Everything on it is per-CHECK, and no aggregate view or per-item quantity roll-up appears; 'all day' occurs nowhere in a kitchen sense. Still unknown, not no: the article covers 'key functionalities', which is not a completeness claim, and it is a 2021-12-09 capture while release notes in this same corpus run to KDS 3.6.8 (2026). ARCHIVE CAVEAT (203rd): support.lingaros.com serves a byte-identical 25,169-byte SPA shell for every path today and its Help Center API 401s on the portal's own orgId, so this article body was read from the Wayback capture named in the URL. source |
| kitchen-speed-of-service-reporting | unknown (grade F) | downgrade-to-unknown | The KDS manual documents timing as a live on-screen counter only - the quoted Timer field plus colour thresholds - with no report, average, percentile or export. Against a no there is positive evidence I could not dismiss: the store-settings article states that with the 'KDS Done Button' toggle enabled 'the item-based prep time is not stored by the KDS', which implies item-level prep times ARE stored when disabled. Where they surface is undocumented. The API reference cannot close this: its Reports section publishes eight families against roughly 25 in the back office, so an absence in it is not an absence in the product. ARCHIVE CAVEAT (203rd): support.lingaros.com serves a byte-identical 25,169-byte SPA shell for every path today and its Help Center API 401s on the portal's own orgId, so this article body was read from the Wayback capture named in the URL. source |
| kitchen-prep-forecasting | unknown (grade F) | downgrade-to-unknown | A positive finding about the mechanism, not an argument from silence. The product's prep screen (Inventory > Preparation, captured 2025-12-07, current) is a back-office screen where a manager picks a Menu Item or Sub Recipe and hand-enters Quantity To Prepare; the columns are Name, Price, Production On Hand, Action, with a Production Log. Nothing derives a quantity from historical sales, and nothing is surfaced to kitchen staff as a daily task list. The vendor's own analytics page closes the forecasting side by enumeration: /solutions/insights states what Predictive Trends forecasts - 'Forecast inventory, sales, and staffing'. Prep quantities are not among the three. 'prep list' occurs zero times corpus-wide. ARCHIVE CAVEAT (203rd): support.lingaros.com serves a byte-identical 25,169-byte SPA shell for every path today and its Help Center API 401s on the portal's own orgId, so this article body was read from the Wayback capture named in the URL. AUDIT (2026-09-04): The forecasting half is closed by a marketing tile, not an enumeration: /solutions/insights renders a nine-cell feature grid of three-word captions, and 'Predictive Trends - Forecast inventory, sales, and staffing' is one caption on it, on a page that also says 'and more'. That is a bulleted marketing list, grade C not B. Worse, prep quantities ARE inventory production, so 'Forecast inventory' reads toward the capability rather than against it. The mechanism half is one screen read out of the P2 floor; showing one screen is hand-keyed does not show no other screen derives quantities. source |
| delivery-3p-reconciliation | unknown (grade F) | downgrade-to-unknown | The reconciliation vocabulary does not exist in Linga's data model, which is the census-backed half: doc-online-ordering publishes the complete order document and doc-sync the complete check document, and between them they carry deliveryCharge, driverTipAmount, refund and saleOrigin but no commission, marketplace fee, marketing fee or payout/deposit field at all - a payout-matching report has nothing to match against. 'commission' occurs exactly once in the whole corpus, on the Uber Direct page. All 11 integration-hub pages are in the corpus: the 3P integrations are order injection, and the vendor's published answer to sales accounting is to hand data off to QuickBooks/Xero/Zoho/Sage/NetSuite. Graded C because the load-bearing citation is a vendor product page; the corroborating schema evidence is grade A. AUDIT (2026-09-04): The load-bearing citation is a grade-C Shogo marketing page whose quoted sentence says nothing about the absence, and the census-backed half is a category error: reconciliation is a REPORT that matches payouts to sales, so the absence of a commission field on a CHECK document is not evidence about it. The P3 subset defect is decisive - the API publishes eight report families against roughly 25 in the back office, so a payout-matching report in Back Office > Reports would be structurally invisible. The Integration Hub also self-describes as an 'ever-growing catalog'. source |
| digital-upsell-engine | unknown (grade F) — 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, | resolve-to-partial | Vendor asserts an upsell surface, but the named mechanic on the same page is 'Show offers on customer-facing screens to boost add-ons' - promotional offers on the CDS, not rules-based or personalized item suggestions in a digital cart. Shortfall 1: the archived Mobile OLO App walkthrough takes the guest categories -> item detail -> cart -> 'Continue to Payment' with no suggestion or cross-sell step anywhere in the flow. Shortfall 2: no attach-rate reporting - P3 retested, the Reports family is exactly Sale, Discount, Void, Transactions, HA Statement, Employee, Paid In/Paid Out and Exchange; no upsell or attach-rate endpoint appears in the published 44-page API reference. Grade C because the only positive evidence is a marketing page. source |
| digital-group-ordering | unknown (grade F) | downgrade-to-unknown | Zero-hit over P4 (the complete 137-page www census): 'group order' 0, 'share a link' 0, 'spend cap' 0, 'per-person' 0, 'participants' 0 across all three corpus files. The vendor's own definition of the OLO product names a single ordering party ordering ahead for pick-up or delivery, and the archived Mobile OLO App walkthrough describes a one-user cart under a single Linga OLO login. Caveat named rather than hidden: the same FAQ block ends an advanced-feature list with 'and more', so the page does not assert its own completeness; the no rests on the P4 census plus the single-cart guest walkthrough, not on that list. AUDIT (2026-09-04): Pure zero-hit over the www sitemap, proven not a feature census: Linga C-Kitchen is a Linga product named 44 times in the developer-docs footer and 0 times across all 137 www pages. The supporting KB walkthrough is over the P2 floor and enumerates nothing; the note itself concedes the FAQ ends with 'and more'. source |
| digital-catering-portal | unknown (grade F) | downgrade-to-unknown | Strongest zero-hit in this batch, over P4: the string 'catering' occurs ZERO times in the entire 2.7MB corpus - 137 www pages (including nine restaurant business-type pages and 25 /solutions/ product pages), 44 API doc pages and 347 archived KB articles. 'banquet' occurs once, as an example revenue-centre name. The published digital ordering product is pick-up/delivery/curbside only; no catering menu, minimum, lead-time rule, quote, proposal or deposit construct exists anywhere. The claim's invoice-terms half is separately unresolvable because /pricing renders client-side and is empty chrome in the corpus. AUDIT (2026-09-04): The strongest zero-hit in the batch and still only a zero-hit: catering is 0 across a KB that is a proven subset (the record cites 153 articles of which 129 are missing here) and a www set that omits C-Kitchen and Hotel & Resorts. The claim is also conjunctive on invoice/ACH terms, unresolvable because /pricing is empty chrome. source |
| digital-voice-ai-phone | unknown (grade F) | downgrade-to-unknown | Positive evidence of absence, not merely a zero-hit: Linga has a dedicated inbound-phone-ordering product and it is explicitly staffed by people. The same page sells that as the benefit - 'Let callers know that you value their time with a live operator, always.' - and the FAQ describes 'direct dispatch centers to handle incoming calls' with 'call agents'. Corroborating P4 census: 'AI' appears 11 times site-wide, all in blog copy plus one partner blurb; zero AI voice, zero conversational ordering. Note the Integration Hub calls itself an 'ever-growing catalog', so the partner list is not closure; the no rests on the human-agent product. AUDIT (2026-09-04): Selling a human call centre is a different capability, not a denial of the claimed one; 'human-first' is marketing positioning, not a non-support statement. The claim explicitly admits a named certified partner, and the Integration Hub self-describes as an ever-growing catalog. The 195th-session rationale rejected this exact partner-list argument already. source |
| digital-drivethru-ai | unknown (grade F) | downgrade-to-unknown | Zero-hit over P4 with a positive contrary framing: 'drive-thru' occurs three times site-wide and every one treats it as a PICKUP mode for orders placed elsewhere, not an ordering lane. No lane screen, no lane timer, no menu-board, no escalation-to-human handoff anywhere in the corpus. Drive-thru is not among the nine restaurant business types the site enumerates. Combined with the finding that Linga's answer to inbound voice is human call-centre agents, there is no AI voice capability to bring to a lane. AUDIT (2026-09-04): Absence over the same porous census, one step weaker because it depends on the voice-AI cell. Three drive-thru mentions treating it as a pickup mode establish only that the marketing site does not sell a lane product; the site also omits C-Kitchen, which exists. source |
| digital-sms-ordering | unknown (grade F) | downgrade-to-unknown | This is the vendor's dedicated SMS product page and its FAQ enumerates what the channel does, entirely outbound. The next FAQ answer closes the direction question outright: 'No, alerts are triggered automatically by actions at the point of sale.' The page's subtitle is staff-facing and the product's summary definition is 'Text Alerts enables SMS Text Message notifications from LINGA software.' No inbound conversational text-to-order, no text-a-link ordering, nothing landing in the POS from a guest text. Zero-hit corroboration over P4 across all 137 pages. AUDIT (2026-09-04): The load-bearing quote is misattributed. 'No, alerts are triggered automatically by actions at the point of sale' answers the FAQ question 'Can I schedule one-time alerts?', not any question about inbound direction - and the same page hero reads 'Send, receive, and schedule SMS notifications'. source |
| digital-google-order | unknown (grade F) | downgrade-to-unknown | Deliberately NOT a no. 'Order with Google' is 0 hits corpus-wide and Google appears in Linga's own material only as Google Pay, a Google Maps API key, and a Google Play Store URL toggle. But Linga's own Integration Hub carries a listed partner whose advertised bundle includes 'Google Business Profile Management' alongside '1st-Party Online Ordering' - precisely the mechanism this claim is about, reachable to a Linga operator through a partner Linga itself publishes. That is a live unresolved route to the capability, not an absence, so a P4 zero-hit cannot close it. source |
| digital-apple-business-connect | unknown (grade F) | downgrade-to-unknown | Zero-hit over P4: 'Apple Business Connect' 0, 'Apple Maps' 0, 'Order Food' custom action 0 across all 137 www pages, all 44 API pages and all 347 archived KB articles. Apple appears in Linga material only as Apple Pay and as an Apple App Store URL toggle in Online Order settings, i.e. a link to a downloadable app, not a map-listing ordering action. The vendor enumerates its own digital ordering surfaces as branded app + website. Weaker than the catering or SMS no above - an absence over a marketing census rather than a contrary published mechanic - but unlike digital-google-order no partner on the Integration Hub offers an Apple-listing route. AUDIT (2026-09-04): Its author called it the thinnest no in the batch and that is right. An absence over the www census with no contrary mechanic at all, and Apple Business Connect is a listing-management action a POS vendor can support without marketing it - the same census omits C-Kitchen and Hotel & Resorts. source |
| guest-loyalty-10dlc-registration | unknown (grade F) | downgrade-to-unknown | '10DLC' and 'A2P' are 0 hits corpus-wide, and 'brand registration', 'short code', 'opt-in', 'Twilio' and 'SendGrid' are all 0 in kb-archived.txt. That is NOT a no, and P2 is why. The record's own prior rationale cites a support.lingaros.com article 'DNS Records for Domain Authentication (SendGrid)' as proof the vendor documents deliverability setup where it exists - and that article is NOT among the 347 slugs in kb-archived.txt. So the archive demonstrably omits the vendor's deliverability documentation, exactly the category an SMS registration article would sit in. The corpus is a FLOOR and the omission is in the worst possible place for this cell. source |
| guest-loyalty-referral-program | unknown (grade F) | downgrade-to-unknown | NEW BASIS - the 195th session's adversarial pass reversed a no here because the KB enumeration it rested on does not close, which under P2 was correct. This no rests on different ground: the complete 137-page www census (P4), which includes a dedicated loyalty product page whose FAQ defines the reward mechanic as discounts or free items driven by buying patterns, with enrollment as on-screen POS registration. The only occurrence of 'referral' in all 137 pages is Linga's own PARTNER programme, not a guest mechanic. Corroborating over P3: the published Loyalty API surface is exactly three endpoints with no referral code, referrer field or attribution parameter. AUDIT (2026-09-04): Same argument in new clothes, on a SMALLER corpus, against a prior adversarial reversal - that needs a higher bar and clears a lower one. The www loyalty page is a four-question marketing FAQ that closes nothing and says 'LINGA's Loyalty integrations', leaving a third-party surface open. The prior rationale records that the loyalty configuration screen was never located - exactly where referral rules would live. source |
| guest-loyalty-wallet-pass | unknown (grade F) | downgrade-to-unknown | Zero-hit over P4 on a dedicated product page: 'Apple Wallet' 0, 'Google Wallet' 0, 'wallet pass' 0, '.pkpass' 0 corpus-wide; the six 'wallet' hits in kb-archived.txt are all the PayPal/Venmo digital-wallet payment article. The vendor's own loyalty page answers the credential question directly and the answer is POS on-screen registration at checkout, not an issued pass. Corroborating over P3: the published Loyalty API is POST customer / updateAccountInfo / Customerloyalty{customer_id} - no pass issuance, no push-update endpoint. AUDIT (2026-09-04): Rests on the same non-closing marketing FAQ: describing one enrollment path does not assert it is the only credential the program issues. The 195th session left this unknown precisely because the loyalty configuration article could not be located, and the www census that supplies the zero-hit omits whole Linga products. source |
| labor-overtime-prevention | unknown (grade F) — 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, an | resolve-to-partial | This OVERTURNS the standing rationale, which asserted the Scheduler article 'states no overtime warning either when building a schedule or when an employee clocks in'. The article does state one. In fairness the line reads as a screenshot caption, but it is vendor documentation asserting the Scheduler warns on an overtime shift. Thresholds are operator-configured: store-settings says 'Define your OT settings here. You can add by weekly or daily OT depending on your local laws.' Named shortfall, which is why this is partial and not yes: the claim requires the warn/block AT CLOCK-IN, and the documented warning fires at schedule-build time in the back-office Scheduler. Nothing documents a punch-time prompt or block. Capture 2022-05-23. ARCHIVE CAVEAT (203rd): support.lingaros.com serves a byte-identical 25,169-byte SPA shell for every path today and its Help Center API 401s on the portal's own orgId, so this article body was read from the Wayback capture named in the URL. source |
| inventory-invoice-ocr | unknown (grade F) | downgrade-to-unknown | Zero hits corpus-wide for OCR, optical character, invoice scan or scan invoice across all three files. This is a no over P4, not over P2: Linga's dedicated inventory module page enumerates its own capture and entry methods across six feature groups, and the mobile section's 'Check item status using manual or scanned barcodes.' Manual keying and barcode scanning are the only ingestion routes the vendor names; invoice capture appears nowhere in the 137-page www census nor in the 44-page API reference, which does carry inventory endpoints. Grade C because the enumerating page is marketing; the KB purchases flow corroborates but the KB is a floor so the verdict does not rest on it. AUDIT (2026-09-04): A marketing page's six feature groups are not a closed enumeration of ingestion routes, and the earlier session read the actual purchases flow end to end from the LARGER corpus and still declined. The function is also routable: Linga's own Integration Hub carries Restaurant365, whose product is line-item invoice capture, so the subject of the claim may be the partner. source |
| inventory-bar-partial-bottle | unknown (grade F) | downgrade-to-unknown | Floor, so unknown. Zero corpus hits for flow meter, pour spout, jigger, keg or tap wall. The only scale in the corpus is a selling scale, not an inventory scale: this article routes the operator to Operations -> Hardware Settings -> Scale on the iPad via a Sunix box, and the menu-item editor exposes a 'Scale Item' type taking a Tare Group and Default Tare - that is sell-by-weight retail and cannot count a partial bottle. The nearest real mechanism is recipe-unit conversion (Purchase Unit with quantity multiplier and Yield %, recipe line takes a Recipe Unit), which depletes a bottle fractionally in theory but is generic recipe costing. Peripheral support would live in the KB, a 347-article FLOOR with no index, so the absence does not close. ARCHIVE CAVEAT (203rd): support.lingaros.com serves a byte-identical 25,169-byte SPA shell for every path today and its Help Center API 401s on the portal's own orgId, so this article body was read from the Wayback capture named in the URL. source |
| reporting-tier-paywall | unknown (grade F) | downgrade-to-unknown | The P4 trap applies directly. /pricing (33,973 bytes) and /pricing/plans (35,142 bytes) both return 200 and both contain only nav chrome plus the CTA block - no plan names, no prices, no feature matrix. Every solutions page ends its hero with this quoted CTA pointing at a page that publishes nothing we can read. So which tier carries labor-vs-sales, PMIX, comps/voids audit and multi-location comparison is not published in anything we hold, and no absence may be read out of those two pages. One unresolved signal not scored: /solutions/insights presents reporting as a separate artifact and the KB marks Store Payment Settings 'Enterprise Accounts only' - suggestive of an add-on SKU, not evidence of one. source |
| reporting-history-retention | unknown (grade F) | downgrade-to-unknown | The claim asks whether a retention window of at least 24 months is DOCUMENTED. It is not documented anywhere in the corpus, but the absence does not close, so unknown. The one retention sentence in all 2.7 MB is on the GDPR page - 'Once the retention period expires, Personal Data shall be deleted' - which governs personal data subject rights, not transaction-detail reporting history, and never names a period. The reporting surface is filtered by an operator-chosen Time Period whose enumerated options run Today, Yesterday, Last 'N' Days, This Week and so on, with no stated lower bound and no truncation notice. A retention policy would live in the KB, a 347-article FLOOR. Capture 2025-12-07. ARCHIVE CAVEAT (203rd): support.lingaros.com serves a byte-identical 25,169-byte SPA shell for every path today and its Help Center API 401s on the portal's own orgId, so this article body was read from the Wayback capture named in the URL. source |
| reporting-nl-query | unknown (grade F) | downgrade-to-unknown | A no over P4. Linga's dedicated reporting product page enumerates the Insights module in nine bullets under three headings - Real-Time Reporting, Business Intelligence and Anywhere Visibility - and no natural-language or assistant surface is among them. Across the whole 137-page census the only AI mentions are industry-trend blog copy and one partner blurb for a third party, Octopus Bridge, which is not Linga's product. Corroborating and not load-bearing: the 44-page API reference exposes only fixed report endpoints with no query surface. The corpus's many 'conversational' hits are Conversational Modifiers, an order-entry prompting feature, irrelevant to this claim. Grade C - the enumerating page is marketing. AUDIT (2026-09-04): Nine marketing bullets under three headings is exactly the enumeration that never claimed to be closed, and the Insights product's own documentation is not in this corpus. The API reference is a partner integration surface and cannot speak to a back-office assistant. source |
| multi-location-multi-brand | unknown (grade F) | downgrade-to-unknown | Retested rather than deferred, and reaches the same place the adversarial pass did. This sentence is the only virtual-brand text in the corpus and it describes Deliverect's own platform, not what a Linga terminal does. Fresh grep of all 347 KB articles for brand resolves to three unrelated things: a vendor-brand field on inventory items, a menu-item image gallery searchable by brand name, and 6.3 release-note theme copy about branded elements. No brand or concept entity, no second menu on one node, no per-brand receipt identity. Stays unknown and not no because the KB is a 347-article FLOOR and because revenue centers do partition a store's transactions by node, so the mechanism may exist undocumented. source |
| extensibility-free-sandbox | unknown (grade F) — 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 Configuratio | resolve-to-partial | P1 is dead and P3 holds, so this cell moves. A staging environment IS documented: this line heads 12 of the 44 doc pages and ships a real seeded Store_id, and two endpoints publish staging hostnames directly. That is the yes half. Named shortfall, which is why this is partial: the sample credential pairs that store id with the literal placeholder 'API Key: generated-api-key', and /docs/introduction documents exactly one way to obtain a real key - sign in to www.lingaros.com, add a store, then Licenses > Developer API > Key Generator. That presupposes a provisioned store, so the claim's 'without owning a paid production account' is NOT established. Neither is 'free': /docs/api-limit's 'Free Edition' / '250 credits' is a per-24h credit allowance tied to a product edition, not a sandbox price. source |
| commercial-rate-increase-clause | unknown (grade F) | downgrade-to-unknown | Read the Sales Terms and the EULA to the end. Neither caps vendor-initiated rate increases, requires notice of a fee change, limits changes to pass-through interchange, or grants penalty-free exit on an increase; the fee sections run the other way, with immediate termination if Fees are unpaid seven days past due, auto-renewing Order Terms, and a Cancellation Fee the parties agree 'is not a penalty but is a reasonable amount of liquidated damages'. But the claim is scoped to the PROCESSING agreement, and the quoted clause shows the Hybrid Payments Merchant Processing Agreement is a distinct instrument the Sales Terms merely reference - it is published nowhere in the 137-page census. Absence of a cap in the SaaS terms is not an enumeration of a document we have never seen, so unknown, not no. source |
| hardware-handheld-battery-swap | unknown (grade F) | downgrade-to-unknown | The string 'battery' occurs ZERO times in all three corpora. But this cannot be converted to a 'no': Linga's actual device catalogue is the 'Recommended Hardware - PDF' KB article, whose entire body is a pointer to an unfetched PDF attachment we do not hold, so the one document that would carry a model list and a battery spec is outside the corpus. www.lingapos.com/hardware/linga-mobile, the only handheld product page in the 137-page census, names no device model, no battery capacity and no runtime. Capture 2023-02-09. Unresolved, not absent. ARCHIVE CAVEAT (203rd): support.lingaros.com serves a byte-identical 25,169-byte SPA shell for every path today and its Help Center API 401s on the portal's own orgId, so this article body was read from the Wayback capture named in the URL. source |
| hardware-handheld-lte | unknown (grade F) | downgrade-to-unknown | A positive enumeration, not an absence. Linga's Network Requirements articles enumerate every supported connectivity path and all are LAN: dedicated Cat6 per device, 5GHz Wi-Fi for mobile terminals, and a 'Wi-Fi Hot Spot or Access Point' that 'has to be on the same IP range and subnet with the wired network'. No cellular path exists in that enumeration, and the handheld-specific wireless section covers only iPad Mini and Linga Go on the store's own Wi-Fi. Corroborated by census: LTE/4G/5G/cellular/SIM/hotspot/tethering return zero across the complete 137-page www sitemap (P4) and the complete 44-page API reference (P3). Capture 2023-11-30. ARCHIVE CAVEAT (203rd): support.lingaros.com serves a byte-identical 25,169-byte SPA shell for every path today and its Help Center API 401s on the portal's own orgId, so this article body was read from the Wayback capture named in the URL. AUDIT (2026-09-04): The cited 2023 article does not make this statement in its own body - the quoted sentence appears there only inside the Related Articles teaser block; the substantive enumeration is in network-requirements-7-4-2020, a 2020 document. The corpus documents a back-office IOT > Hot Spot > Wifi module the article never mentions, and Linga markets LINGA Go as 'no cables required' and 'Ideal for food trucks, events, and outdoor service'. P2 bites hardest here: pos-hardware-requirements is absent from this corpus entirely. source |
| hardware-drive-thru | unknown (grade F) | downgrade-to-unknown | The POS front-of-house hardware picker enumerates exactly four peripheral classes - Card Reader, Printer, Customer Display, Scale - and no outdoor menu board, order-confirmation display or speaker/headset device. Over the P4 census the only two drive-thru mentions in 137 pages are curbside marketing copy on /restaurant/quick-service - guests collecting at a vehicle, not drive-thru equipment. The 21-item solutions catalogue lists Kiosk, KDS, Customer Facing Display, Queue and Caller ID but no menu board, headset or speed-of-service timer. The claim is conjunctive (hardware AND a documented timer) and fails on both halves. Capture 2023-11-30. ARCHIVE CAVEAT (203rd): support.lingaros.com serves a byte-identical 25,169-byte SPA shell for every path today and its Help Center API 401s on the portal's own orgId, so this article body was read from the Wayback capture named in the URL. AUDIT (2026-09-04): The four-item picker is a configuration screen for peripherals Linga supports, not a supported/unsupported hardware table - the exact reasoning the earlier session recorded when it declined this cell. The 21-item solutions catalogue is not a closed product list either: the www census omits C-Kitchen outright. source |
| hardware-tap-to-phone | unknown (grade F) | downgrade-to-unknown | Linga's 'tap to pay' language throughout the site means contactless acceptance on a reader, not softPOS. The LINGA Go FAQ pairs that capability list with 'LINGA Mobile, LINGA Tablet, or a compatible Android device is required.' - a device that also swipes and inserts is a reader-equipped terminal. The KB hardware picker enumerates 'Card Reader' as the payment peripheral. Over the P4 census (137 pages) and P3 census (44 API pages) 'NFC', 'softpos' and 'Tap to Pay on' return ZERO. Reader-free acceptance on a commodity phone is not offered. Grade C because the carrying page is a marketing/solutions page. AUDIT (2026-09-04): The inference is doing the work: 'a device that also swipes and inserts is a reader-equipped terminal' is analyst reasoning, not a vendor statement, and the same FAQ pairs tap to pay with 'or a compatible Android device is required', which reads at least as easily toward softPOS as against it. The KB article that would settle the iPhone half is not in this corpus at all. source |
| hardware-byod | unknown (grade F) | downgrade-to-unknown | Half-addressed at best. The hardware minimums (Android 11+, 4 GB RAM, 8 GB storage) impose no device-class restriction, and 'a compatible Android device' would admit a staff member's own phone - but that is a spec sheet, not a BYOD position. The claim's second conjunct, a documented permission and security model for personal devices, is unsupported: 'BYOD', 'personal device' and 'own phone' return zero corpus-wide, and no MDM, enrolment or containerisation guidance exists. Per P2 the KB is a FLOOR, so the absence of a device-security article there is unknown, not no. source |
| hardware-selfpour-scales | unknown (grade F) | downgrade-to-unknown | The 'Scale' in that four-item enumeration is a weighing scale, not a pour meter - the Scale Set up article describes connecting a CAS scale to the iPad through a Sunix box for weighed items. 'pour', 'keg', 'draft beer', 'flow meter' and 'tap wall' return ZERO across all 2.7 MB of corpus including the complete P4 census; the Integration Hub's ten partners are delivery, accounting, payroll and gift-card vendors with no beverage-hardware name. Caveat recorded: that hub page calls itself an 'ever-growing catalog of solutions', so the no rests on the closed FOH device picker plus the P4 zero-hit, not on the partner list alone. ARCHIVE CAVEAT (203rd): support.lingaros.com serves a byte-identical 25,169-byte SPA shell for every path today and its Help Center API 401s on the portal's own orgId, so this article body was read from the Wayback capture named in the URL. AUDIT (2026-09-04): The verdict names the disclaimer and then leans on the surface anyway - the Integration Hub calls itself an ever-growing catalog. The FOH device picker is a 2023 settings screen the earlier session already refused as an enumeration, and it also noted that the published Order Webhook would let a third party post pours without Linga documenting it. source |
| reliability-failover-terminal-role | unknown (grade F) | downgrade-to-unknown | Moved on positive evidence, not absence. Linga documents its multi-terminal architecture explicitly: cross-terminal check state flows through a remote redis/sync server (port 9096, per the Network Setup Guide), there is no designated primary terminal or local server anywhere in the corpus ('primary terminal', 'local server' and 'backup server' are zero-hit; every 'master' hit is Master Stock or masterMenuItems), and the vendor states what happens when that link fails - the nodes go isolated and stop reflecting each other's checks. That is degradation, not role takeover; no terminal is promoted. Capture 2026-04-10. ARCHIVE CAVEAT (203rd): support.lingaros.com serves a byte-identical 25,169-byte SPA shell for every path today and its Help Center API 401s on the portal's own orgId, so this article body was read from the Wayback capture named in the URL. AUDIT (2026-09-04): Wrong failure mode. The offline-mode article describes what happens when the internet link drops - nodes stop reflecting each other's checks - which is not evidence about what happens when a primary terminal or local server dies; the earlier session read this same article and named that distinction exactly. The rest is zero-hit greps over a KB corpus proven to be a subset. source |
| reliability-cellular-backup | unknown (grade F) | downgrade-to-unknown | Same enumeration as hardware-handheld-lte applied to fixed terminals: the supported WAN/LAN paths are wired Cat6 to a central switch plus 5GHz Wi-Fi, with the vendor adding that 'Linga will not support customers who are solely on Wi-Fi setup' - the redundancy story runs toward more wire, not an alternate radio WAN. Independently corroborated by the vendor's own outage-planning blog post, which enumerates recommended redundancy measures (generators, UPS, offline mode, manual card slips, staff drills) and names no cellular or dual-WAN failover. Zero word-boundary hits for LTE/4G/5G/cellular/SIM/dual-WAN across P4 and P3. ARCHIVE CAVEAT (203rd): support.lingaros.com serves a byte-identical 25,169-byte SPA shell for every path today and its Help Center API 401s on the portal's own orgId, so this article body was read from the Wayback capture named in the URL. AUDIT (2026-09-04): The enumeration does not close and is not current: the wired-network text is the 2020-slugged article and never addresses WAN redundancy at all, and the corpus contains a back-office IOT/Hot Spot/Mesh Wi-Fi module it does not mention. Linga expressly disclaims the network - 'Linga is not responsible for network issues' - so dual-WAN sits with the integrator, making vendor silence uninformative. source |
| kitchen-speed-of-service-reporting | unknown, grade F | resolve-to-partial | Verified first-hand against the Zoho Desk KB body (portal API, modifiedTime 2026-04-13): the quote is verbatim in the KDS dashboard tab. Checked the adversarial reading that 'Avg Time Per Check' is the Summary-tab figure computed from net sales - it is not: the Summary tile is '(Net sales/ Number of sales)/100', while the KDS-tab tile is 'the Average amount of Time Per Check, from opening to closing' with a table by Kitchen Area for KDS and EXPO, plus a 'Time Vs Kitchen Display System' chart by kitchen location. Meets the average ticket/per-station-time conjunct; falls short on percentiles, daypart/channel slicing and export, so partial not yes. source |
| reporting-tier-paywall | unknown, grade F | resolve-to-partial | Verified first-hand by parsing every raw <tr> of the 2024-03-01 capture (not stripped text): Core column is fa-check for Reports, Void transactions, Payroll reporting, Employee performance tracking, Sales and Employees dashboards; fa-minus for Consolidated reporting, Multi-site management, Royalty/ACH reporting, Food costing, Inventory comparison; KDS and OLO dashboards are fa-plus (add-on) on Core/Pro/Enterprise. Plan names are current: live KB articles dated 2025-10-27 ('If you're using a Core plan') and 2026-01 (Basic/Pro/Enterprise/Linga One store counts) still use this tier structure. Retired page, grade C, capped at partial. source |
| hardware-handheld-lte | unknown, grade F | upheld | Proposed partial from the full 617-article Linga Zoho Desk KB (census via portal API), live lingapos.com pages and the archived www.lingaros.com site / requests.lingapos.com board (270th session); rejected on verification: The only evidence is two marketing slogans: 'Full mobility with Wi-Fi and LTE!' (2020 LINGA GO page) and 'With wifi and LTE enabled, LINGA Go offers flexible offline functions' (2022 blog). Neither names a device model, a SIM/radio spec or any fallback behaviour; a full-corpus search of the 617-article KB, 38 live pages and 657 archived pages for LTE/4G/cellular/SIM found nothing else, and the live LINGA GO page no longer mentions LTE and now names 'a compatible Android device'. A marketing slogan is not a shipped feature, so the partial rests on no conjunct. source |
| hardware-selfpour-scales | unknown, grade F | resolve-to-partial | Verified first-hand in the archived bodies: the 2023-09-23 ros-integrations capture lists AndroBar under 'Liquor Control' ('Order and dispense your liquor with our pouring control system'), the 2022-07-19 bar-profits blog calls it 'LINGA's latest integration with AndroBar', and the 2022-03-13 brewery blog describes the mechanism (dispense only after a sale is rung in; digital tracking of portion, date, time, user). Re-pointed the citation from the directory listing to the brewery blog, the only page that describes what the integration does. The integration-with-liquor-pour-control conjunct is met; the pour-posts-to-tab conjunct is not (the direction is reversed). Absent from all live sources, so old material capped at partial. source |
| reliability-cellular-backup | unknown, grade F | resolve-to-partial | Upheld as partial/C, the grade for a vendor commerce page, after a challenge on three fronts. (1) Is it first-party? The host is Linga's own storefront: the header reads 'LINGA POS / BEVO POS', support contact is support@lingapos.com, and the modem is listed in the Networking collection beside the Ubiquiti POE switches and access points Linga specifies for installs. It is a vendor-supplied failover device, which the claim admits ('first-party or documented'). (2) Is it automatic? The copy says 'automatic 4G LTE connection' and 'failover to LTE', but that is Netgear's manufacturer copy; Linga never documents how the POS behaves on switchover. (3) Is it current? No: the newest capture is 2020-09. The current KB network requirements (270th) enumerate wired Cat6 plus 5GHz Wi-Fi and disclaim the network. Peer precedent: lavu holds hardware-handheld-lte partial/B on a vendor-sold failover modem, and reliability-cellular-backup has 3 partial/C peers. Not a yes, because nothing POS-side is documented. source |
| hardware-handheld-lte | unknown, grade F | resolve-to-partial | The 270th rejected a partial here because its only evidence was the slogan 'Full mobility with Wi-Fi and LTE!'. This is a different basis: a named, vendor-sold ordering handheld with a published 4G/SIM radio. (1) Is the device an ordering handheld or only a card reader? The shop bundles it with a required 'LINGA CORE SaaS subscription' (Table Layout & Management, Loyalty, Gift Card). The live KB article pos-sppax-payments says 'Linga GO app is installed in A77 SPPAX device for sale and payments. Device Name : A77 , A920 , A920 pro , A800'. So it runs the POS, not just payments. (2) Is it current? The 26.08.001 release notes (2026) fix 'performance issues observed on some A920 Pro devices'. (3) Is the fallback conjunct met? No. Nothing says the device switches to 4G when store Wi-Fi drops, so this is not a yes. Peer precedent: revel holds partial/C for vendor-sold cellular iPads with the fallback undocumented, and lavu holds partial/B on a failover modem. Grade C, because the radio spec is a commerce page and the KB (B) does not mention cellular. source |
| hardware-handheld-battery-swap | unknown, grade F | resolve-to-partial | The claim's second disjunct is a published rated battery life for a full shift. Linga's shop published one for the handheld it sold for mobile ordering, the iPad mini 5 ('Battery Run Time: Up to 10 hours'), and the 'Mobile Bundle for iPad Mini 5' is 'used for table or pool side ordering as well as line busting'. Challenged down from yes on three points. The figure is Apple's 'up to' manufacturer rating, not a POS-use rating. It is historical (2020). And the current handheld listing (A920 Pro, 2023) publishes only capacity ('Battery 5250mAh'), not run time, while no listing documents a swappable or field-replaceable battery. Not a no: a runtime was published, and the one explicit 'Non-detachable' battery is the 2019 Stock-take Handheld, an inventory counting device rather than the ordering handheld. This corrects the prior note's 'battery occurs ZERO times in all three corpora', which held only for those corpora. Peers: lavu no/B (sealed iPad, no published life); lightspeed and clover partial/B. source |
| multi-location-multi-brand | unknown, grade F | upheld | Proposed partial from a surface the record never cited - Linga's archived first-party hardware shop (shop.lingapos.com 2019, shop.lingaros.com 2020-2025, Wayback) (279th session); rejected on verification: 'Multi-Brand/Company - Optimal for franchises or owners who have multiple concepts and multiple locations' is an ORGANISATION-level plan feature: several concepts, each at its own location, under one account. The claim needs one location or terminal running two or more brands with separate menus, receipts and revenue on the same hardware and drawer, and the page says nothing about that. It restates the enterprise-hierarchy reading the prior verification already set aside. The only virtual-brand text in the corpus is still Deliverect's own platform ('manage multiple storefronts through a single delivery platform'), and partner content cannot establish a vendor capability. The 2026 cloud-kitchen solution page is inventory, central reporting and a delivery dashboard, with no brand entity. POISON: 'Multi-Brand/Company' is a pricing-tier row label, and 'Ghost kitchen software' is SEO copy. source |
| payments-chargeback-tooling | unknown, grade F | upheld | Proposed partial from a surface the record never cited - Linga's archived first-party hardware shop (shop.lingapos.com 2019, shop.lingaros.com 2020-2025, Wayback) (279th session); rejected on verification: The 'online chargeback management interface' belongs to Chase Paymentech, the acquirer, and the blog describes Chase's merchant portal, not a Linga product surface. The claim needs an IN-PRODUCT dispute dashboard with evidence assembled from the POS transaction record, and nothing ties the Chase portal to Linga data. It is also a single 2018-19 blog post about a Canada-only integration. The other 'dispute' hits are EULA arbitration, the GDPR policy, Sales Terms s24 and review-site disputes. The record's existing basis (the OLO 1.3 'Stripe Dispute Process' deduction) is unchanged. source |
Sources
Every URL this record cites. 239 in total.
- https://www.lingapos.com/solutions/linga-pos
- https://support.lingaros.com/portal/en/home
- https://lingapos.com/solutions/kiosk
- https://lingapos.com/restaurant/pizzeria
- https://lingapos.com/integration-hub
- https://pnc.mediaroom.com/2022-09-26-PNC-ANNOUNCES-ACQUISITION-OF-POINT-OF-SALE-AND-PAYMENTS-SOLUTIONS-FIRM
- https://www.lingapos.com/solutions/linga-pay/
- https://www.lingapos.com/solutions/gift-cards
- https://www.lingapos.com/solutions/kitchen-display-system-kds/
- https://lingapos.com/solutions/linga-driver
- https://www.lingapos.com/solutions/online-ordering/
- https://lingapos.com/solutions/customer-loyalty-programs
- https://lingapos.com/restaurant/franchise
- https://lingapos.com/solutions/schedules
- https://lingapos.com/solutions/insights
- https://lingapos.com/solutions/inventory-management
- https://developer.lingapos.com/docs/doc-paid-reports/
- https://docs.pandium.com/connectors/connectors-101/linga-ros
- https://lingapos.com/payment-plans
- https://www.lingapos.com/
- https://developer.lingapos.com/docs/docs-schedule-api-token/
- https://lingapos.com/partners/become-a-developer-partner
- https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026
- https://lingapos.com/pricing
- https://investor.pnc.com/news-events/financial-press-releases/detail/360/pnc-announces-acquisition-of-point-of-sale-and-payments-solutions-firm-linga
- https://developer.lingapos.com/docs/doc-categories/
- https://developer.lingapos.com/docs/doc-transactions-reports/
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-modifiers
- https://support.lingaros.com/portal/en/kb/articles/pos-modifiers
- https://support.lingaros.com/portal/en/kb/articles/pos-operation-86-list
- https://support.lingaros.com/portal/en/kb/articles/pos-payment-surcharge-dual-price
- https://support.lingaros.com/portal/en/kb/articles/pos-payment-surcharge-surcharge
- https://support.lingaros.com/portal/en/kb/articles/pos-check-options-void-item-23-9-2025
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-delivery-application-settings
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-customers-membership
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-employee-report
- https://support.lingaros.com/portal/en/kb/articles/uber-eats-integration
- https://support.lingaros.com/portal/en/kb/articles/pos-operation-printer-hardware-settings
- https://developer.lingapos.com/docs/doc-categories/
- https://developer.lingapos.com/docs/introduction/
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-payment-method-settings
- https://support.lingaros.com/portal/en/kb/articles/back-office-audit-log-reports
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-void-report
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-user-management-roles-manager-access-discount-transfer-void
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-exporting-reports
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-membership-reports
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-tip-out-tip-sharing-report-settings
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-marketing-settings
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-marketing-customers
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-customers-customer-info
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-enterprise-menu-configuration
- https://www.lingapos.com/solutions/membership
- https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-8-5-2025
- https://support.lingaros.com/portal/en/kb/articles/pos-payments-offlinemode
- https://support.lingaros.com/portal/en/kb/articles/back-office-inventory-in-house-units
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-menuitems
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-preparation
- https://support.lingaros.com/portal/en/kb/articles/back-office-introduction-to-scheduler
- https://support.lingaros.com/portal/en/kb/articles/pos-bar-tab-floating-tab
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-scheduler
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-table-layout-application-settings
- https://support.lingaros.com/portal/en/kb/articles/pos-table-layout-overview
- https://support.lingaros.com/portal/en/kb/articles/pos-table-layout-split-checks
- https://support.lingaros.com/portal/en/kb/articles/pos-seat-order-override
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-general-application-settings
- https://support.lingaros.com/portal/en/kb/articles/pos-fire-coursing
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-coursing
- https://support.lingaros.com/portal/en/kb/articles/pos-table-layout-transfer-a-check
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-online-ordering-stores
- https://support.lingaros.com/portal/en/kb/articles/pos-phone-web-orders-print-before-future-order
- https://support.lingaros.com/portal/en/kb/articles/pos-phone-web-orders-future-tab
- https://support.lingaros.com/portal/en/kb/articles/phone-web-orders-third-party-integration-differences
- https://support.lingaros.com/portal/en/kb/articles/integration-hub-order-webhook-settings
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-products-items
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-serving-size-level
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-store-payment-settings
- https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-8-5-2025
- https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-allow-offline-payment
- https://support.lingaros.com/portal/en/kb/articles/pos-payment-screen-options
- https://support.lingaros.com/portal/en/kb/articles/pos-multi-cash-payments
- https://support.lingaros.com/portal/en/kb/articles/pos-partial-payments-in-online-ordering-olo
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-kitchen-printer-hardware-settings
- https://support.lingaros.com/portal/en/kb/articles/pos-menu-options-change-the-coursing-of-a-menu-item
- https://support.lingaros.com/portal/en/kb/articles/pos-menu-options-fire
- https://support.lingaros.com/portal/en/kb/articles/pos-uber-eats-integration
- https://support.lingaros.com/portal/en/kb/articles/pos-resend-to-kitchen
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-adjust-inventory
- https://support.lingaros.com/portal/en/kb/articles/phone-web-orders-driver-reporting
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-driver-report
- https://support.lingaros.com/portal/en/kb/articles/pos-phone-web-orders-cashier-report-for-driver
- https://support.lingaros.com/portal/en/kb/articles/doordash-drive-integration
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-third-party-integrations-settings
- https://www.lingapos.com/online-ordering
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-kiosk-addon-settings
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-discounts-check-based
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-marketing-manage-list
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-marketing-campaigns
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-store-scheduler-settings
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-reports
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-vendors
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-purchases
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-low-stock
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-inventory-item
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-store-notifications-settings
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-matrix-report-inventory-settings
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-daily-summary-report
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-discounts-report
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-till-report
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-enterprise-reports
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-revenue-center-reports
- https://support.lingaros.com/portal/en/kb/articles/back-office-customer-preference-report
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-taxes
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-stores
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-receipt-printer-hardware-settings
- https://support.lingaros.com/portal/en/kb/articles/pos-hardware-requirements
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-store-licenses-settings
- https://developer.lingapos.com/docs/doc-automation/
- https://developer.lingapos.com/docs/doc-online-ordering/
- https://developer.lingapos.com/docs/doc-sync-kiosk/
- https://developer.lingapos.com/docs/doc-orders-for-ext-app/
- https://developer.lingapos.com/docs/api-limit/
- https://support.lingaros.com/portal/en/kb/linga-pos/back-office/reports
- https://support.lingaros.com/portal/en/kb/articles/pos-offline-mode-restrict-offline-payment
- https://status.lingaros.com/
- https://www.lingapos.com/contact-support
- https://www.lingapos.com/restaurant/full-service
- https://www.lingapos.com/sales-terms-and-conditions
- https://www.lingapos.com/end-user-license-agreement
- https://www.lingapos.com/privacy-policy
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-emv-payment-settings
- https://support.lingaros.com/portal/en/kb/linga-pos/back-office/settings/payments
- https://support.lingaros.com/portal/en/kb/linga-pos/hardware-and-networking
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-gift-card-report
- https://support.lingaros.com/portal/en/kb/linga-pos/back-office/customers
- https://www.lingapos.com/retail/electronics
- https://www.lingapos.com/solutions/kiosk
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-feedback-app-addon-settings
- https://investor.pnc.com/news-events/financial-press-releases/detail/360/pnc-announces-acquisition-of-point-of-sale-and-payments-solutions-firm-linga
- https://www.lingapos.com/integration-hub
- https://developer.lingapos.com/docs/doc-paid-reports/
- https://developer.lingapos.com/docs/docs-schedule-api-token/
- https://support.lingaros.com/robots.txt
- https://support.lingaros.com/portal/en/kb
- https://developer.lingapos.com/
- https://developer.lingapos.com/sitemap.xml
- https://www.lingapos.com/robots.txt
- https://support.lingaros.com/portal/en/kb/articles/retail-back-office-user-management-creating-a-new-user
- https://support.lingaros.com/portal/en/kb/articles/26-03-001-release-notes
- https://support.lingaros.com/portal/en/kb/articles/deliverect-integration
- https://support.lingaros.com/portal/en/kb/articles/26-03-003-release-notes
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-kds-configuration-template-settings
- https://support.lingaros.com/portal/en/kb/articles/may-27th-2025-release-notes
- https://support.lingaros.com/portal/en/kb/articles/february-11th-2025-release-notes
- https://support.lingaros.com/portal/en/kb/articles/26-06-001-release-notes
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-enterprise-settings-addons
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-payroll-report-settings
- https://support.lingaros.com/portal/en/kb/articles/26-05-001-release-notes
- https://support.lingaros.com/portal/en/kb/articles/retail-back-office-enterprise-settings-addons
- https://support.lingaros.com/portal/en/kb/articles/pos-time-clock
- https://support.lingaros.com/portal/en/kb/articles/retail-back-office-subscriptions-upgrades-summary
- https://support.lingaros.com/portal/en/kb/articles/october-14th-2025-release-notes
- https://support.lingaros.com/portal/en/kb/articles/26-03-002-release-notes
- https://support.lingaros.com/portal/en/kb/articles/pos-table-layout-qr-payment
- https://support.lingaros.com/portal/en/kb/articles/pos-operation-pos-settings
- https://support.lingaros.com/portal/en/kb/articles/26-02-001-release-notes-6-3-2026
- https://support.lingaros.com/portal/en/kb/articles/pos-check-status-screen-future-tab
- https://support.lingaros.com/portal/en/kb/articles/pos-available-time-discount-display-groups-and-upcharges
- https://support.lingaros.com/portal/en/kb/articles/pos-operation-card-reader-hardware-settings
- https://support.lingaros.com/portal/en/kb/articles/adding-a-manager-card
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-sale-reports
- https://support.lingaros.com/portal/en/kb/articles/26-08-001-release-notes
- https://support.lingaros.com/portal/en/kb/articles/november-12-2024-release-notes
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-kitchen-printer-receipt-template-settings
- https://support.lingaros.com/portal/en/kb/articles/26-07-001-release-notes
- https://support.lingaros.com/portal/en/kb/articles/26-04-001-release-notes
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-products-items-cut-and-modify
- https://support.lingaros.com/portal/en/kb/articles/octopus-bridge-integration-pick-up-orders
- https://support.lingaros.com/portal/en/kb/articles/pos-phone-web-orders-out-tab
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-additional-report-settings
- https://support.lingaros.com/portal/en/kb/articles/march-11-2025-release-notes-13-3-2025
- https://support.lingaros.com/portal/en/kb/articles/integration-hub-user-manual-13-6-2025
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-online-ordering-account
- https://support.lingaros.com/portal/en/kb/articles/pos-customer-profile-screen
- https://support.lingaros.com/portal/en/kb/articles/pos-phone-web-orders-overview
- https://support.lingaros.com/portal/en/kb/articles/retail-back-office-admin-accounts
- https://support.lingaros.com/portal/en/kb/articles/dns-records-domain-authentication
- https://support.lingaros.com/portal/en/kb/articles/retail-back-office-payroll-report-settings
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-employees-scheduler
- https://support.lingaros.com/portal/en/kb/articles/november-17th-2025-release-notes
- https://support.lingaros.com/portal/en/kb/articles/retail-back-office-inventory-purchases
- https://support.lingaros.com/portal/en/kb/articles/july-16th-2025-stock-app-revamp
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-inventory-in-house-units
- https://support.lingaros.com/portal/en/kb/articles/august-6-2024-release-notes-5-8-2024
- https://support.lingaros.com/portal/en/kb/articles/january-7-2025-release-notes
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-user-management-roles
- https://www.lingapos.com/pricing/plans
- https://support.lingaros.com/portal/en/kb/articles/august-19th-2025-compare-inventory-report-enhancement
- https://support.lingaros.com/portal/en/kb/articles/back-office-comparison-report
- https://support.lingaros.com/portal/en/kb/articles/26-08-003-release-notes
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-enterprise-settings-account
- https://www.lingapos.com/partners/become-a-developer-partner
- https://www.lingapos.com/partners/become-a-developer-partner/api-agreement
- https://support.lingaros.com/portal/en/kb/articles/september-8th-2025-release-notes
- https://support.lingaros.com/portal/en/kb/articles/july-8th-2025-release-notes
- https://support.lingaros.com/portal/en/kb/articles/august-14th-2025-card-reader-manager-and-gift-card-swipe-support
- https://support.lingaros.com/portal/en/kb/articles/factor4-integration
- https://support.lingaros.com/portal/en/kb/articles/retail-pos-hardware-settings-overview-and-recommended-devices
- https://support.lingaros.com/portal/en/kb/articles/pos-operation-scale-hardware-settings
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-scale-barcode-addon-settings
- https://support.lingaros.com/portal/en/kb/articles/26-01-001-release-notes-6-3-2026
- https://support.lingaros.com/portal/en/kb/articles/pos-log-in-screen
- https://support.lingaros.com/portal/en/kb/articles/may-14-2024-release-notes
- https://support.lingaros.com/portal/en/kb/articles/pos-sign-in-screen
- https://support.lingaros.com/portal/en/kb/articles/26-04-002-release-notes
- https://www.lingapos.com/solutions/marketing
- https://www.lingapos.com/payment-plans
- https://www.lingapos.com/partners/become-a-partner
- https://www.lingapos.com/solutions/qr-menu
- https://www.lingapos.com/restaurant/quick-service
- https://www.lingapos.com/solutions/customer-facing-display-terminal
- https://www.lingapos.com/integration-hub/deliverect
- https://www.lingapos.com/solutions/call-center-system-for-restaurants
- https://www.lingapos.com/solutions/caller-id
- https://www.lingapos.com/integration-hub/chowly
- https://www.lingapos.com/solutions/insights
- https://www.lingapos.com/solutions/inventory-management
- https://web.archive.org/web/20230209030341/https://support.lingaros.com/portal/en/kb/articles/qr-code-for-virtual-kiosk
- https://lingapos.com/solutions/call-center-system-for-restaurants
- https://lingapos.com/restaurant/quick-service
- https://web.archive.org/web/20220523133652/https://support.lingaros.com/portal/en/kb/articles/linga-scheduler
- https://support.lingaros.com/portal/en/kb/articles/back-office-2024-home-9-1-2025
- https://web.archive.org/web/20240301023505/https://www.lingaros.com/pricing/restaurant/feature-comparison-matrix/
- https://web.archive.org/web/20201109130046/https://www.lingaros.com/restaurant-operating-system/linga-go/
- https://web.archive.org/web/20220313044047/https://www.lingaros.com/blog/brewery-pos-system-craft-beer-restaurants/
- https://web.archive.org/web/20200924071541/https://shop.lingaros.com/products/netgear-4g-lte-modem-with-boost-antenna
- https://web.archive.org/web/20231004003020/https://shop.lingaros.com/products/mobile-pos-bundle
- https://web.archive.org/web/20200811103334/https://shop.lingaros.com/products/ipad-mini-4-128gb
- https://web.archive.org/web/20160930212922/http://www.lingapos.com:80/plans/
- https://web.archive.org/web/20190718215231/https://www.lingapos.com/linga-pos-offers-integrated-payments-in-canada-with-chase-paymentech/