Lavu

order-capture-floor-plan-editor

Vendor claims 'Easily manage tables, menus, and more'; graphical editor depth, multiple saved layouts and server-section assignment are not documented publicly. https://lavu.com/compare-lavu/ · retrieved 2026-08-01

order-capture-seat-level

Documented help-center article "POS - Active Seat and Course" — seat assignment of items is a shipped POS function, not an inference. https://support.lavu.com/en/knowledge/lavu-pos · retrieved 2026-08-01 adversarially verified

order-capture-coursing-hold-fire

Two documented articles: "POS - Active Seat and Course" and "Hold & Fire". https://support.lavu.com/en/knowledge/lavu-pos · retrieved 2026-08-01 adversarially verified

order-capture-split-merge

Both halves are documented: "POS - Merging Orders" and "POS Video - Splitting Orders". Reviewer complaints about UX difficulty are a usability finding, not a capability gap, and should not have held the score at partial. https://support.lavu.com/en/knowledge/lavu-pos · retrieved 2026-08-01 adversarially verified

order-capture-bar-tab-preauth differentiator

Card pre-auth tabs exist — help-centre articles "Pre-Authorization Flow on POS App" and "POS - Change Service Types (Quick Serve, Tables, and Tabs)". Shortfall: the claim additionally requires a configurable auth amount, incremental re-auth as the tab grows, and end-of-day auto-close of stale tabs; none of the three is documented. https://support.lavu.com/en/knowledge/lavu-pos · retrieved 2026-08-02 adversarially verified

order-capture-transfer-audit

Transfer is documented: tap the Order #/table/tab header > Assigned Server > select the receiving server > Confirm, restrictable via Advanced Location Settings; item movement between orders has its own 'Disable inter-order item transfers' switch. The Action Log report records front-end activity filterable by employee and device and exports to CSV, but no doc states that a transfer event is logged naming both employees. https://support.lavu.com/en/knowledge/manager-handbook-transfer-orders · retrieved 2026-08-05

order-capture-native-handheld

The Lavu POS is a native iOS app, not a mirrored session: the KB carries iPhone/iPod-specific interface settings ("Order pad font (iPhone/iPod)", "Return to order pad after selecting an item on your iPhones/iPods") and an explicit device-capability difference ("Reordering is only available on iPads and this feature is not available on iPhones or iPods"). Sending to kitchen is in-app ("Allow order resend ... the option of resending items to the kitchen"). Card payment is taken on the same device: the VP3300 "connects to your POS through Bluetooth, and is capable of swiped transactions, EMV chip inserts, tap to pay programs like Apple Pay, and manual entry directly through the POS", paired from Settings > Card Reader Settings > VP3300, and Lavu sells a carried configuration (iPad mini + VAULT GoWork Pro case + Adyen NYC1 reader) as its Wi-Fi Handheld Bundle. https://support.lavu.com/en/knowledge/how-to-connect-your-vp3300-card-reader-to-your-lavu-pos · retrieved 2026-08-09 adversarially verified

order-capture-offline-order-entry

Order entry offline is documented at grade B — Lavu’s "Crash Kit 101" lists "Conduct cash transactions", "Open the cash drawer", "Add food and drink to open orders", "Start new orders", "Send orders to the kitchen" and "Print checks" as working without internet. Shortfall: the claim also requires the vendor to publish what does and does not work offline, and Lavu’s two first-party sources conflict — the marketing page says "Every POS function works locally — orders, payments, modifiers, kitchen tickets", while Crash Kit 101 says credit and gift card transactions require active internet to validate card details. https://support.lavu.com/en/knowledge/lavu-crash-kit-101 · retrieved 2026-08-02 adversarially verified

order-capture-qr-same-check differentiator

Lavu documents two QR surfaces and neither writes to an open POS check. Up N' Go prints a per-order payment QR on the check and the article states the codes "are not meant to show your customer's your menu", referring menu QR to MenuDrive. MenuDrive QR ordering requires "an additional location added to your account... used exclusively for your customers to place orders through your QR codes" because its required settings (dine-in only, ASAP only, specific prep times) "may conflict with your already established online storefront"; those orders arrive as new MenuDrive orders through an order-receiving method - "Email and text notifications, Order Dashboard, IP Printer, Lavu POS integration" - carrying the table/seat on the kitchen ticket, not as items appended to a server-entered check. https://support.lavu.com/en/knowledge/menu-drive-qr-codes · retrieved 2026-08-08

order-capture-kiosk-first-party differentiator

'Self-Ordering Kiosks' marketed and 'Kiosk' is a monitored component on the public status page; shared menu tree and ADA conformance undocumented. https://lavu.com/contactless-payments-ordering/ · retrieved 2026-08-01

order-capture-drive-thru

Positive absence across every first-party surface, with one caveat recorded honestly: the Order Types article's default list is illustrative rather than exhaustive ('Your account comes with default Order Types LIKE Dine In, Pickup, and Carry Out'), so the weight does not rest on it. What it does establish is the shape of the model - an order type is a label carrying a tax-exemption flag, attached to one of three service layouts enumerated as 'Quick Serve, Tables, and Tabs' - which has no lane, order-point, pay-window or pickup-window entity to sequence against and no pull-forward or parking-spot assignment. Against that, 'drive-thru' occurs zero times across the complete 249-URL help centre (its sitemap and its seven category pages agree exactly), zero times in the 4,844-URL first-party sitemap census, and Lavu's 43-page site carries segment pages for fine dining, food trucks, international and multi-location but none for QSR or drive-thru. https://support.lavu.com/en/knowledge/order-types · retrieved 2026-09-04 adversarially verified

order-capture-drive-thru-timers

Follows from the absence of the drive-thru flow itself: with no order-point or window separation in the Order Types surface there are no segment boundaries to time. The only order timing Lavu documents is the KDS per-tile order timer and its colour-change duration thresholds (Lavu KDS - Settings, Functions and Features), which is ticket age on one screen rather than order/total/window segments tied to individual cars, and the enumerated Reports catalogue contains no speed-of-service report. https://support.lavu.com/en/knowledge/order-types · retrieved 2026-09-04 adversarially verified

order-capture-voice-ai differentiator

Re-checked 2026-09-04 against a freshly proven-complete corpus: the 249-article help centre (the sitemap and all seven category pages agree exactly, closing the 'this dump may be incomplete' caveat earlier passes carried) plus a 4,844-URL sitemap census of lavu.com, support.lavu.com and shop.lavu.com. 'Voice' occurs zero times in any of them, and api.lavu.com's OpenAPI spec exposes no voice or telephony surface. But Lavu markets an AI line (Marty) across roughly twenty lavu.com pages, and a documented API partner program for third-party voice AI would live in commercial material this census does not adjudicate, so silence here cannot carry a no. adversarially verified

order-capture-throttling differentiator

Positive evidence of the opposite mechanism. MenuDrive's capacity control is a single static Preparation Time per fulfilment type, and the article's whole worked example is that the constant is subtracted from the closing time to compute the last orderable minute: a 30-minute prep time and a 9 p.m. close block an 8:35 p.m. order and quote 8:55 for an 8:25 order. There are no per-slot capacity limits, no order-count ceilings, and the quoted time never moves with kitchen load; the documented remedy for wanting later orders is to widen the pickup/delivery hours, not to throttle. https://support.lavu.com/en/knowledge/menu-drive-order-types-and-prep-time · retrieved 2026-09-04 adversarially verified

order-capture-scheduled-orders

Future-dated orders exist on the MenuDrive digital channel: the storefront checkout carries an "Order Pickup Time (ASAP/Advanced)" selector, and the Item 86 Count article separately distinguishes "ASAP orders" from "In Advance orders". Shortfalls: the only timing control documented is MenuDrive prep time, which sets the last-order cutoff ("Whatever is set for prep time is subtracted from your closing time making the last available time your customer can place an order") rather than a per-channel lead time; and no article states whether a scheduled order is injected into the make queue at a computed fire time or transmitted on receipt — the fire-time half of the claim is undocumented. https://support.lavu.com/en/knowledge/menudrives-online-ordering-storefront-3.0 · retrieved 2026-08-03

order-capture-catering

Deposit and balance-due pieces exist as generic POS features: items with 'Allow Deposits' enabled take a partial payment at checkout and the order is flagged 'Underpaid' in reports 'so you know your customer still has an amount due on their order'; MenuDrive supports Advance Orders and per-item minimums pitched at 'catering menus where there is a 5 person minimum'. Shortfall: no distinct catering queue, no quotes, and no delivery/event schedule are documented. https://support.lavu.com/en/knowledge/item-deposits · retrieved 2026-08-05

order-capture-order-ready-signal differentiator

Positive absence by architecture enumeration rather than by settings silence. The DSP Integration article declares its own contents - Store Onboarding, Menu Export, Order Ingestion, Limitations - and gives an explicit inner process flow for each: for onboarding and for menu sync, MenuDrive calls Lavu DSP, Lavu DSP calls the DoorDash API, and the confirmation returns; for orders, the flow terminates at ingestion, 'the final step in DSP integration'. There is no fourth flow carrying order state outward. The companion article's settings surface corroborates it: Connect/Onboard, Sync Menu, automatic out-of-stock removal, dual-pricing percentage, temporary closures and special store hours are the whole of what the integration exposes, and none of them is readiness. https://support.lavu.com/en/knowledge/dsp-integration-delivery-service-provider-integration · retrieved 2026-09-04 adversarially verified

order-capture-void-comp-controls

All three limbs are documented. Reason codes: 'Lavu POS - Voiding Orders & Items' - 'Depending on your settings, you may be prompted to enter a reason for voiding'; 'Creating Discounts in Lavu' has a per-discount 'Prompt for a reason' setting. Role gating: the same discount editor has an 'Access Level' field ('For manager discounts or entire meal comps, we recommend setting this to at least level 2'), 'Lavu Access Levels' puts voids, discounts and refunds at Level 2, and 'Advanced Location Settings - Order Options' sets the 'Access level required (0, 1, 2, 3, or 4)... to edit and remove saved items, and to edit and remove sent items'. Exception reporting: the Voided Items and Voided Orders reports list every void with order id, cashier and price and export to csv/xls/txt, and the void reason is retrievable per order via the order's View action log. https://support.lavu.com/en/knowledge/lavu-pos-voiding-orders-and-items · retrieved 2026-08-08

menu-pricing-nested-modifiers

Nesting and min/max both exist but not at the depth the claim asks for. MenuDrive modifier groups take a type (Checkbox, Radio, Dropdown, Quantity, Toppings Matrix) plus 'Min and Max settings, which determine how many or how few options a customer must select', and each option carries a 'Nested Modifier' toggle that 'allows you to attach another modifier group to that specific option' - one documented additional level. Lavu POS reaches the same one level through Detours ('Detours cannot be used on Checklist Forced Modifiers'), and its forced-modifier lists are typed Choice or Checklist with no min/max count fields documented anywhere. Shortfall: three-level depth is documented nowhere in either product, and on the POS side there are no independent min/max selection counts - only the Choice/Checklist type and the forced-vs-optional distinction. https://support.lavu.com/en/knowledge/menu-builder-page · retrieved 2026-08-08

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

Checked 'Menu Drive - Menu Builder Page', 'Basic Menu Building in Menu Drive', 'Basic Menu Building in Lavu' and 'Using Pizza Creator' in the 250-article support.lavu.com help centre dumped in full on 2026-08-08 (244 sitemap articles plus 9 found by cross-link). MenuDrive prices sizes on the item ('you will need to add a price to each size') and attaches modifier groups per size ('Each size will also have its own section for attaching modifiers'), while a modifier option itself takes 'a name and a price' - one price - which implies duplication rather than a matrix. The gap that keeps this unresolved is specific: for Toppings Matrix groups the article says 'you will have access to Advanced Settings... these advanced settings allow you to control features specific to modifiers like Pizza or Sandwich Toppings' and then documents NOTHING about what those settings are, showing them only as a screenshot. Per-size or per-parent modifier pricing is exactly the control that would live there, so the documented single-price option field cannot be treated as the whole model. Unresolved.

menu-pricing-fractional-placement differentiator

Pizza Creator "automatically comes equipped with certain modifications commonly used by pizza restaurants" — "you will have the options for half toppings, light, and extra automatically built in" — and the Partial Serving Price fraction (default 0.5) prices a half topping independently. Halves only; quarters and thirds are not documented. https://support.lavu.com/en/knowledge/using-pizza-creator · retrieved 2026-08-02 adversarially verified

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

One pricing lever only. Pizza Creator exposes "Partial Serving Price ... The default is 0.5 which will cut the price of your topping in half" — the fraction-of-full-price rule. The claim requires the rule be operator-configurable among at least two of {charge the higher half, average the halves, fraction of full}; charge-higher-half and average-the-halves are absent, and how the pizza base price is derived when two halves differ is undocumented. Verification could not corroborate a "1st Half / Whole / 2nd Half" matrix on the cited page. https://support.lavu.com/en/knowledge/using-pizza-creator · retrieved 2026-08-02 adversarially verified

menu-pricing-topping-quantity-tiers

"light, and extra modifiers" are built into Pizza Creator's topping selection automatically. Whether extra carries an independent price multiplier is not stated. https://support.lavu.com/en/knowledge/using-pizza-creator · retrieved 2026-08-01 adversarially verified

menu-pricing-size-style-matrix differentiator

Price varies across both axes, but additively rather than as a per-cell grid. In MenuDrive, sizes are a property of the CATEGORY ('Sizes are applied to every item within your category') and the item carries one price per size; a second axis such as crust is a modifier group whose options each carry a single price, added on top. In Lavu POS, Pizza Creator assembles separate forced-modifier lists for size, crust and toppings and its only price mechanic is a per-section 'Partial Serving Price' fraction (default 0.5) for half toppings. Shortfall: no documented per-cell override for a given size x crust pair - the second axis is a flat up-charge on the per-size base price, so a 14-inch deep-dish cannot be priced independently of that additive result. https://support.lavu.com/en/knowledge/menu-builder-page · retrieved 2026-08-08

menu-pricing-included-allowance differentiator

Re-checked 'Menu Drive - Menu Builder Page', 'Basic Menu Building in Menu Drive', 'Using Pizza Creator', 'Combo Builder' and 'How to create a Meal Deal or Special offers in Menudrive' in the 250-article support.lavu.com help centre dumped in full on 2026-08-08 (244 sitemap articles plus 9 found by cross-link). Combo Builder is the closest documented mechanic and it is a different one: it links whole menu items into a bundle with 'flexible pricing - you can import the menu item prices, add up charges for specific items, or have the price for the combo set as a whole', i.e. an up-charge per option rather than an n-included-then-charge-overage allowance, and it says nothing about crediting or forbidding substitutions. Pizza Creator prices toppings per selection with only the Partial Serving Price fraction. The Toppings Matrix 'Advanced Settings' in MenuDrive - the one place an included-topping count would plausibly be configured - is shown only as a screenshot with no text, so the mechanic can be neither confirmed nor excluded. Unresolved.

menu-pricing-combos

Combo Builder links menu items into combos with swap price deltas ('You can add an up-charge to options within the combo for special add ons like sweet potato fries in place of regular fries'), imported item prices or a set whole-combo price, per-component printer routing, mixed tax profiles, and Hold & Fire per component. Shortfall: automatic detection/conversion of eligible a-la-carte cart items into the combo price is not documented. https://support.lavu.com/en/knowledge/combo-builder · retrieved 2026-08-05

menu-pricing-upsell-prompts differentiator

MenuDrive has 'Built-in upsell and add-on marketing' on the digital channel only; no per-channel configuration or attach-rate reporting documented. https://lavu.com/online-ordering/ · retrieved 2026-08-01

menu-pricing-86-propagation

Cross-channel propagation is documented but conditional. Item 86 counts decrement jointly across POS and MenuDrive ("When an item is ordered on Menu Drive or Lavu POS, that number will decrease by 1"), and the DoorDash article confirms an out-of-stock POS item "will automatically be removed from the DoorDash storefront". Named shortfalls: the feature must be switched on by Lavu support and requires "Track in LavuPOS" enabled in the Location Profile; it "is only applicable for ASAP orders and not applicable for In Advance orders"; and sold-out items can still be added to a guest cart, with the alert appearing only "until they get to the Order Summary screen". No propagation latency is published. https://support.lavu.com/en/knowledge/item-86-count-tracking-in-menu-drive · retrieved 2026-08-02

menu-pricing-countdown-auto-86 differentiator

Countdown and auto-86 are documented — "As the item is ordered, the number will decrease by 1", "When the number reaches 0, the item will be 86ed" — but the claim also requires a scheduled auto-restore, and the same article says the item "cannot be ordered until the number of servings is updated in the Control Panel menu". Shortfall: restock is a manual Control Panel edit; no nightly or scheduled reset is documented. https://support.lavu.com/en/knowledge/86-countdown-in-lavu · retrieved 2026-08-02 adversarially verified

menu-pricing-dayparting

Happy Hours schedule both prices and availability by time-of-day and days-of-week at menu category, item, and modifier level: price mode adds/subtracts a dollar or percentage amount or sets a specific price; availability mode marks items Available/Not Available on schedule ('a brunch menu only being available in the morning, or just on weekends'); multiple overlapping happy hours per day are supported via an Advanced Location Settings toggle. MenuDrive items additionally take specific-hours/days and date-range visibility and availability windows. https://support.lavu.com/en/knowledge/happy-hours · retrieved 2026-08-05

menu-pricing-channel-price-books

A percentage markup over base menu price is documented only for the DoorDash channel ('enable the feature, and enter a number for the percentage increase to your menu items' prices' under Dual Pricing, 5% recommended); MenuDrive items can hold prices independent of the POS when unlocked from sync. Shortfall: no general per-channel price books for dine-in/pickup/delivery/kiosk and no markup rules for other channels. https://support.lavu.com/en/knowledge/lavu-menu-drive-and-door-dash · retrieved 2026-08-05

menu-pricing-dual-pricing differentiator

Item- and modifier-level configuration and dual display at the POS are documented (5% increase applied per selection in the Control Panel; cashier, server and guest all see both prices). Shortfall: the claim requires consistent application across POS, kiosk and online ordering, which is never addressed, and the program is gated — "This program is currently only available in the U.S., and to Lavu Pay customers", with "CDP can only be enabled by a Lavu admin" by phone. https://support.lavu.com/en/knowledge/cash-discount-program · retrieved 2026-08-02 adversarially verified

menu-pricing-allergen-nutrition

The words 'allergen', 'nutrition' and 'calorie' appear ZERO times in all 250 help-centre articles, and the item field surface is enumerated in three places that leave no room for them. MenuDrive item creation: 'you will need to provide a Name, a Menu, a Category, and a price for each size. Everything else is completely optional', plus photos and modifier groups; 'Menu Items - Advanced Settings' then states exactly what the advanced tier holds - 'Advanced Settings contains options for Special Notes, Visibility and Availability options, making Upsells, and Special Offer settings'. Publishing is enumerated too: the DoorDash menu export sends 'MenuGroup/Category/Item/ModifierGroup/Modifier Option' entities only. And api.lavu.com/docs/swagger.json - a grade-A schema, exhaustive as to that API - exposes GET /v1/customer/menus/ with no allergen or nutrition field. Ingredients can be linked to items for stock and cost, but no article derives nutrition from them. https://support.lavu.com/en/knowledge/menu-builder-page · retrieved 2026-08-08

menu-pricing-recipe-linkage differentiator

Documented end to end. 'Inventory: Link Ingredients to Menu Items': 'Navigate to your menu item and look for the white box with the word Ingredients. When you click on it, you will be able to add your ingredients from the drop down menu, and designate how much of that ingredient is used in one serving of this menu item... With the ingredient attached to the menu item, whenever the item is sold, stock automatically be deducted from your inventory', with automatic 86 when stock runs out. Costing is real, not inferred: 'Inventory Settings' sets a Costing Method (Average/Periodic or FIFO) that 'will dictate how the Food and Beverage report tabulates cost of goods sold', and 'Tracking Food & Liquor Costs' states 'the cost of creating that menu item from your ingredients will be calculated against the price of the menu item, to give you a cost percentage', surfaced in End of Day Overview v2 through Food/Liquor super groups. Caveat on the claim's wording: ingredient linkage is documented at menu-item level only; no article shows ingredients attached to a modifier. https://support.lavu.com/en/knowledge/inventory-link-ingredients-to-menu-items · retrieved 2026-08-08

menu-pricing-3p-menu-push

Direct certified push exists for DoorDash only: after a progressive sync, menu entities (MenuGroup/Category/Item/ModifierGroup/Modifier Option) 'get updated automatically from MD to DX', plus a manual Sync Menu button showing last-sync date/time; 'If the sync fails, it throws an error and asks you to try again.' Shortfalls: Uber Eats and Grubhub go through integrator middleware (Otter/Chowly/Checkmate), and no per-item sync status or per-item rejection reporting is documented. https://support.lavu.com/en/knowledge/dsp-integration-delivery-service-provider-integration · retrieved 2026-08-05

menu-pricing-dynamic-pricing

Happy Hours is a genuine rule engine: each rule carries a name, a time window, the days of the week it runs, and an effect that can 'add to your item's price', 'subtract from your item's price' or 'set your item to a specific price', by dollar amount or by percentage; rules are applied per menu category, per item and directly to forced and optional modifiers, several can apply at once, and overlapping same-day rules are permitted once 'Disable Multiple Happy Hours per Day' is unchecked in Advanced Location Settings. A second mode marks items Available/Not Available instead. Shortfall: the only trigger is time of day and day of week - no demand-driven or per-channel variation is documented - and there is no floor/ceiling guardrail field; the article also warns that a price-changing happy hour shows 'no indicator that a happy hour is in affect' on the POS. https://support.lavu.com/en/knowledge/happy-hours · retrieved 2026-08-08

payments-processor-choice differentiator

Merchant gateway choice is documented, but only for the online-ordering half. MenuDrive's Payment Options page offers Lavu Pay (CardConnect) or Verifone - 'MenuDrive's newest payment gateway partner... now available for U.S. customers' - and the merchant supplies their OWN Verifone credentials ('You will then be asked if you have API credentials for Verifone... Click the orange Edit button to enter your credentials... make sure the credit card gateway is enabled'). Shortfall: for the iPad POS itself no third-party processor list is published - every documented reader path (VP3300, LANE 3000, NYC1, PAX, BOLT, iCT250 in Canada) runs through Lavu Pay/CardConnect, and the only non-Lavu-Pay POS mode documented is unintegrated, where 'Credit card info to ask for when integration is turned off' has staff key card type and last four by hand. https://support.lavu.com/en/knowledge/menu-drive-and-verifone · retrieved 2026-08-08

payments-published-rates differentiator

Lavu's own payment-processing page claims 'some of the lowest processing rates available' and 'transparent pricing' while publishing no rate; no rate appears anywhere on lavu.com. https://lavu.com/payment-processing/ · retrieved 2026-08-01

payments-dual-pricing differentiator

Raised from partial on verification, onto documentation. Cash Discount Program: "Your cashier, server, and your customers will see two prices. One discounted price if they pay in cash, and the other original total if they pay with a credit or debit card." Configured by applying a 5% increase to selected menu items and modifiers in the Control Panel, and the article shows a receipt with both totals printed on the check. Gating (US-only, Lavu Pay customers only, "CDP can only be enabled by a Lavu admin") is recorded on the adjacent menu-pricing and compliance cells. https://support.lavu.com/en/knowledge/cash-discount-program · retrieved 2026-08-02 adversarially verified

payments-surcharge-guardrails differentiator

Checked the 250-article support.lavu.com help centre dumped in full on 2026-08-08 (244 sitemap articles plus 9 found by cross-link): the string 'surcharg' occurs ZERO times in all 250 articles, as does 'convenience fee'. Lavu's documented card-cost-recovery product is different in kind: 'Cash Discount Program' describes Dual Pricing, where the Control Panel raises menu item and/or modifier prices by a flat 5% ('select what in your menu you would like to increase the prices of, and select Increase Price (5%)') and both prices show to staff and print on the check; it is US-only, Lavu-Pay-only, and 'can only be enabled by a Lavu admin'. That article is a product explainer, not an enumeration of Lavu's payment settings, and it contains no card-brand or BIN logic at all - so BIN/product-code debit exclusion, network cap enforcement and a per-location toggle are undocumented rather than shown absent. support.cardpointe.com is the processor's documentation and was not treated as evidence for what Lavu exposes. Unresolved.

payments-emv-nfc

Upheld, but the dossier's source was the help-center homepage with confidence "documented", which does not meet the bar. Real evidence exists: the VP3300 article documents "triple-track MagStripe, smart card, and contactless technologies", Bluetooth connection to the POS, "EMV chip inserts, tap to pay programs like Apple Pay, and manual entry". Ingenico LANE3000 is also documented as a hard-wired option. https://support.lavu.com/en/knowledge/how-to-connect-your-vp3300-card-reader-to-your-lavu-pos · retrieved 2026-08-01 adversarially verified

payments-softpos-tap-to-pay differentiator

Checked every contactless mention in the 250-article support.lavu.com help centre dumped in full on 2026-08-08 (244 sitemap articles plus 9 found by cross-link). All four are reader-based, never phone-based: the VP3300 'can accept card payments through card swipes, insert (EMV), or tap to pay (Apple Pay, Google Wallet, etc.)', the same phrasing for the Ingenico LANE 3000 and for the NYC1, and 'Pairing your VP3300 with Lavu Kiosk' lists Tap to Pay among the kiosk's transaction types via that Bluetooth reader. The Store & Forward fallback in 'Lavu Crash Kit 101' likewise requires an iDynamo plugged into the iPad. What is missing is a supported-hardware table or any statement that acceptance requires a reader - the card-reader articles are per-device setup guides, so their silence about Tap to Pay on iPhone or Android tap-to-pay is not evidence of absence, and no Lavu announcement of either programme was found. Unresolved.

payments-pay-at-table

Tip prompt: "Lavu allows you to have customers sign and leave tips through the iPad screen at the time of sale", with configurable Quicktip buttons (percentage or amount, order, hidden options), and Tip Configuration by Device lets individual iPads prompt on screen rather than print a tip line. Splitting: the KB carries a splitting-orders walkthrough with per-check navigation. Card entry travels to the table: the VP3300 pairs over Bluetooth and does chip, contactless and Apple Pay through the POS, and Lavu's store sells a Wi-Fi Handheld Bundle and a Cellular Handheld (iPad mini + VAULT GoWork Pro case + Adyen NYC1 reader, "contactless, chip, and swipe") so "staff can take secure card payments at the table". Caveat worth stating: the reader is a separate Bluetooth/dock device rather than integrated into the tablet. https://support.lavu.com/en/knowledge/customize-the-sign-and-tip-screen · retrieved 2026-08-09 adversarially verified

payments-qr-guest-pay differentiator

The mechanics are documented and work: a QR code is "specifically generated for each order, so there’s no chance of one of your customers paying for someone else’s order", and "Once the order is paid for, the order will automatically be closed on the POS." Shortfall: this is partner-delivered, not native — "Lavu’s partnership with Up N’ Go provides a way for you print QR codes on your printed checks", with enrolment through Lavu sales; Lavu ships no first-party scan-to-pay. https://support.lavu.com/en/knowledge/lavu-qr-codes-with-up-n-go · retrieved 2026-08-02 adversarially verified

payments-tip-adjust

Documented: "Editing Tips on the POS (Server Tips)", "POS - Refund a Tip", "Tip Configuration by Device", "Custom Gratuity". https://support.lavu.com/en/knowledge/lavu-pos · retrieved 2026-08-01 adversarially verified

payments-tip-pooling differentiator

Workforce Settings documents configurable Tip Out rules (a percentage of total/cash-only/card-only tips, or of total or super-group sales, paid to one or more employee classes, split evenly or by hours worked) and Tip Pooling within a class (evenly or hours-worked over shift/daily/weekly periods), with results on each Server Summary. Shortfalls: no exportable per-employee pool-distribution ledger is documented, and Lavu Payroll requires tips to be keyed manually, 'be sure to account for... tips that are shared with other team members through tip outs or tip pooling'. https://support.lavu.com/en/knowledge/workforce-settings · retrieved 2026-08-05

payments-offline-store-and-forward differentiator

Two offline card paths are documented: manual key-entry into the CardPointe virtual terminal, and "Store & Forward" using an iDynamo reader on the iPad, which stores card data locally and processes it once connectivity returns, described as trading verification speed for operational continuity. Shortfall: the claim requires configurable per-transaction and cumulative offline limits — no limit of any kind is published — and store-and-forward is tied to the iDynamo rather than the standard VP3300. https://support.lavu.com/en/knowledge/lavu-crash-kit-101 · retrieved 2026-08-02 adversarially verified

payments-offline-decline-liability differentiator

OVERTURNED on the first limb. Lavu does publicly document loss allocation for offline card transactions, just not in the help centre: lavu.com/terms-of-service/ (last updated 12/01/2025) states "We may offer a feature that facilitates transacting Offline Credit Card Transactions with the Lavu Products, or your User Account. If you choose to utilize this feature you agree that we are not liable for any damages or losses from the use of this feature", provided "As Is" and at the merchant's "sole risk". That answers who bears the loss - the operator does. This is also where Lavu Crash Kit 101 was pointing when it said "Before using this feature, you will need to agree to the following terms and conditions in your Control Panel, and on the POS." Named shortfall: the second limb is still unmet - no post-reconnect report of failed offline payments appears in any documented Lavu Reports family (Sales, Cash Management, Labor, Refund Summary, V1 Reports), and the terms describe liability in the abstract rather than a reconcilable list of declines. https://lavu.com/terms-of-service/ · retrieved 2026-08-08 adversarially verified

payments-gift-cards

Not just a Gartner/Software Advice feature-list entry — Lavu's help center has a native "Lavu Gift/Loyalty" category with a "Digital Gift Cards" article. First-party stored value is shipped. Multi-location and online-channel redemption still undocumented. https://support.lavu.com/en/knowledge/lavu-pos · retrieved 2026-08-01 adversarially verified

payments-house-accounts

Positive absence by enumeration of both halves of the claim. The customer object is fully documented in Customer Management and holds identity only - name, address, phone, email and operator-defined custom fields, with a configurable signup form, an order History view, CSV Customer Import and Customer Export - and carries no balance, no credit limit and no statement or invoice run. The tender side is enumerated in The Checkout Layout Editor, where every payment button the POS can present is configured: up to two rows of four, drawn from the standard set plus 'custom payment options like gift card or check', with an Other button holding the overflow. A custom payment method is a label on a button, not an account ledger, and tabs in Lavu are an open-check service layout rather than a stored customer account. https://support.lavu.com/en/knowledge/customer-management · retrieved 2026-09-04 adversarially verified

payments-split-tender

Tab splitting is marketed; supported split modes, multi-tender settlement and any split-count cap are undocumented, and reviewers report the flow is very hard to use. https://lavu.com/compare-lavu/ · retrieved 2026-08-01

payments-refund-void-controls

Role gating is documented for three of the four action types: "Require admin PIN to void orders or checks", "Require admin PIN to void payments or refunds", "Require admin PIN to perform refunds", "Access level required to void items" and "Access level required for generic discount types", plus optional reason prompts for refunds and generic discounts; the void/refund article adds an "Access level required to perform voids and refunds from the Open/Closed Orders screen" (disabled by default). The Action Log "shows all frontend activity" including "Refund Applied", filters to "see which employees conducted refunds", and exports to .txt/.xls/.csv. Shortfalls: no documented gating for no-sales; the log records the acting employee but nothing states it captures the approving manager's identity; immutability of the log is not documented. https://support.lavu.com/en/knowledge/advanced-location-settings-checkout-options · retrieved 2026-08-03

payments-chargeback-tooling differentiator

Positive evidence that the dispute surface lives outside the product. Lavu's own instruction for examining card transactions is to leave Lavu: 'Log into your CardPointe account using the link here', then Reporting > Transactions, searching by the last four digits or the auth code, 'Both of these are available in the Lavu Control Panel' - Lavu supplies the lookup keys and CardConnect holds the record. The words chargeback and dispute occur nowhere in the complete 249-article help centre, there is no open-disputes list or evidence-submission flow in the Control Panel's documented Transactions module, and the Terms and Conditions place processing entirely with the third-party gateway. https://support.lavu.com/en/knowledge/reviewing-transactions-in-cardpointe · retrieved 2026-09-04 adversarially verified

payments-card-on-file differentiator

A stored card exists, but only inside the online storefront. 'Menu Drive's Online Ordering Storefront' says that once a customer signs up and logs in, 'Customers can update their contact information, credit card numbers, and delivery address for faster ordering'. Shortfall: that store is scoped to the MenuDrive storefront account - nothing documents reuse of it for a phone order taken on the POS or for an in-store check; Lavu's POS-side customer object ('Customer Management') holds contact fields, custom fields and order history with no payment instrument; and neither the storefront article nor any Lavu Pay/CardPointe article states that the stored value is a token rather than a PAN. api.lavu.com/docs/swagger.json exposes no token or stored-instrument endpoint - its payment paths are create-payment-record, external-payment and payment-intent. https://support.lavu.com/en/knowledge/menudrives-online-ordering-storefront-3.0 · retrieved 2026-08-08

payments-payout-timing differentiator

Positive evidence of non-publication in the document where funding terms would be stated. The Accepting Credit Card Payments section disclaims the role outright - 'We do not directly handle processing of credit card transactions. The Lavu Products simply facilitate transacting credit cards through integrated third-party Credit Card Gateway and Processing partners' - and puts settlement verification on the merchant: 'You are responsible for verifying that your credit card batch is settled and that all amounts are correct on a daily basis', with a seven-day window to report a discrepancy. No deposit schedule, funding window, or next-day or instant-funding option is published there, on lavu.com/payment-processing/, or in the CardPointe articles; batching is documented as a per-terminal operator action. https://lavu.com/terms-and-conditions/ · retrieved 2026-09-04 adversarially verified

payments-p2pe-pci4

Verified the underlying quote, which the researcher paraphrased: "Lavu Pay is PCI-compliant, keeps data secure, accepts payments offline, and provides real 24/7 support." No AoC, no PCI DSS version, no P2PE listing, no SAQ type. Partial with confidence "claimed" is correct. https://lavu.com/payment-processing/ · retrieved 2026-08-01 adversarially verified

kitchen-station-routing

Sole evidence is marketing bullets on the KDS product page ("Route orders to the right station automatically. Set up multiple screens"). I found no KDS configuration documentation in the public help center to corroborate operator-configurable station routing rules. Claim-level marketing should not carry a "yes" on a differentiator cell. https://lavu.com/kitchen-display-system-kds/ · retrieved 2026-08-01 adversarially verified

kitchen-expo-consolidation

Positive absence in the vendor's own complete KDS reference, which enumerates every setting and function of the product: User Sign In, Show Date/Time, Show Table, Show Timer, Show Ticket Updates, Show Paid Status, Show Ingredients, Expanded Ticket View, Tile Display (Row x Column and Order Queue Direction), Company Logo and Item Count. There is no expo or expeditor screen type, no multi-station consolidated order view, and no all-stations-bumped completion rule - routing is one printer profile per menu category (Lavu KDS - Printer Profile) and each screen bumps independently, the only cross-item aggregation being a bumped/total item count inside a single ticket. https://support.lavu.com/en/knowledge/lavu-kds-settings-functions-and-features · retrieved 2026-09-04 adversarially verified

kitchen-course-firing differentiator

'The Active Course feature allows course numbers to be assigned to menu items for an order, allowing each course to be sent to the kitchen separately'; at send time, 'Tap the appropriate course to send to the kitchen OR send all unsent items.' Hold & Fire alternatively holds items on a per-item timer or indefinitely for manual fire; the two modes are mutually exclusive ('You cannot use course labels if you are using Hold & Fire'). https://support.lavu.com/en/knowledge/pos-active-seat-and-course · retrieved 2026-08-05

kitchen-prep-time-pacing differentiator

OVERTURNED by the no-audit on 2026-09-04. The KDS reference does establish that the SCREEN has no pacing logic - its only timing controls are the per-tile order timer and the colour-change duration thresholds - but per-item cook times would be a menu-item field, not a KDS setting, and the menu surface is the one place in this corpus that is provably NOT enumerated: Basic Menu Building in Lavu ends by deferring to 'other more advanced features in menu building like Modifier Groups, Detours, Combo Builders, and more that you can read about in other articles'. Item Details is referenced by the KDS article (Show Ingredients displays 'the item's description, as entered in the Item Details') but no article walks that record field by field. A cook-time field could sit there unread, so silence cannot carry a no. adversarially verified

kitchen-order-throttling differentiator

The only pacing lever between digital ordering and the kitchen is MenuDrive's static Preparation Time, which fixes both the quoted ready-time and the last orderable minute and never varies with kitchen load or ticket volume. The KDS reference exposes no load threshold, no release delay and no queue hold - its Tile Display setting caps how many tickets are visible on screen (1x3 or 2x3), not how many are released - so neither release pacing nor automatic quote extension exists. https://support.lavu.com/en/knowledge/menu-drive-order-types-and-prep-time · retrieved 2026-09-04 adversarially verified

kitchen-channel-pause-propagation differentiator

86 propagation to DoorDash is automatic: 'If an item is out of stock on the POS, then the item will automatically be removed from the DoorDash storefront', working with Item-Level 86 Tracking or ingredient inventory; sold-out items also auto-block MenuDrive orders. Shortfalls: DoorDash is the only directly connected marketplace (Uber Eats/Grubhub via integrator middleware), and store pause is a manual Temporary Closure toggle in the MenuDrive control panel, not an action from POS/KDS. https://support.lavu.com/en/knowledge/lavu-menu-drive-and-door-dash · retrieved 2026-08-05

kitchen-order-ready-callback differentiator

The same architecture enumeration read from the KDS end: the DSP integration declares three process flows - store activation, menu export, order ingestion - each with an explicit inner call sequence, and ingestion is named 'the final step'. Nothing carries state back out. Bumping is a KDS-local action; Lavu KDS - Settings, Functions and Features documents the Bump button and the per-ticket bumped/total item count with no downstream event, so courier dispatch cannot be driven by actual readiness. https://support.lavu.com/en/knowledge/dsp-integration-delivery-service-provider-integration · retrieved 2026-09-04 adversarially verified

kitchen-bump-bar-hardware

KDS is driven by a tile-based touchscreen interface with bump functionality, and the certified hardware is the Epson KDS with a MicroTouch screen. Shortfall: the claim requires physical bump bars or programmable keypads in addition to touch, with documented supported models; Lavu’s equipment article lists printers, cash drawers, card readers, a scale and a tablet stand, and names no bump bar model. https://support.lavu.com/en/knowledge/lavu-kds-settings-functions-and-features · retrieved 2026-08-02 adversarially verified

kitchen-all-day-counts

Positive absence by enumeration: the KDS reference lists every display mode and aggregation the screen offers, and the only count in the product is per-ticket - 'A count of bumped / total items has been added to the center of the lower margin of each order ticket'. No view aggregates outstanding quantities per item, or per modifier, across the open tickets on a station; the Tile Display setting only controls how many order tiles fit on screen. https://support.lavu.com/en/knowledge/lavu-kds-settings-functions-and-features · retrieved 2026-09-04 adversarially verified

kitchen-sla-alerts

Configurable time-based color escalation is documented: 'the order duration settings... will trigger a color change at the designated interval(s) whether the order timer is enabled or not.' Shortfalls: no per-station or per-order-type target times and no audible alert are documented. https://support.lavu.com/en/knowledge/lavu-kds-settings-functions-and-features · retrieved 2026-08-05

kitchen-printer-fallback differentiator

Lavu's documented answer to an unavailable kitchen printer is manual, not automatic: Printer Redirects "are a way you can temporarily change which kitchen printers your menu items print from", must be enabled per order-taking device ("if you need all of your iPads to redirect, you will need to follow these steps for each individual order taking device") and manually reversed afterwards ("When you are finished using that redirect, you will need to come back to this screen to disable your redirect"). Basic Printer Setup enumerates the complete per-printer configuration — setting, name, static IP, port, type, command set, model, image capability — with no backup-printer or failover field, and the Epson "Failed to Write" article ("the iPad is unable to find your printer") prescribes restoring connectivity only. A documented manual workaround plus an enumerated settings surface lacking any backup option is positive evidence there is no automatic failover; consistent with the reliability-printer-fallback finding. https://support.lavu.com/en/knowledge/printer-redirects · retrieved 2026-08-04

kitchen-offline-operation differentiator

A KDS screen is bound to the POS over the LAN — the printer profile is created by entering "the iPad’s IP address" and port 5288 — which makes local ticket delivery architecturally plausible. Shortfall: neither the KDS documentation nor Crash Kit 101 states that KDS screens continue receiving and displaying tickets while the cloud backend is unreachable; the vendor never asserts it. https://support.lavu.com/en/knowledge/lavu-kds-printer-profile · retrieved 2026-08-02 adversarially verified

kitchen-item-build-screens differentiator

The Show Ingredients setting, 'in conjunction with User Sign In, permits the KDS to display a given item's ingredients in an expanded window' with quantities and the item description, via the 'i' icon beside each order item. Shortfalls: the build detail is a tap-opened window rather than on the ticket face, and User Sign In exists 'to support the KDS's premium features' priced through the sales team. https://support.lavu.com/en/knowledge/lavu-kds-settings-functions-and-features · retrieved 2026-08-05

kitchen-pizza-fractional-display differentiator

The KDS reference enumerates how modifiers render on the make line and the rendering is textual and flat: modifiers appear under their item, altered ones turn orange with a (MOD) tag, new ones carry a (NEW) tag, voids strike through, and Show Ingredients opens a list window. There is no sectioned, halved or quartered visual representation of topping placement anywhere in the display model. https://support.lavu.com/en/knowledge/lavu-kds-settings-functions-and-features · retrieved 2026-09-04 adversarially verified

kitchen-recall-refire

POS-side refire exists: the 'Allow order resend' setting enables 'resending items to the kitchen' without re-entering the order. Shortfall: KDS-side recall/unbump of a bumped ticket is not documented, and the KDS doc states that when an item is added to an already-bumped order 'the KDS will create a new order tile rather than retrieving the previously bumped order contents'. https://support.lavu.com/en/knowledge/advanced-location-settings-order-options · retrieved 2026-08-05

kitchen-order-modification-alerts differentiator

Raised from partial on verification. Lavu’s KDS settings documentation describes items modified after the ticket is displayed rendering with an orange highlight and a "(MOD)" tag on the live ticket — the claim is exactly that POS edits to an already-displayed order visually flag the changed items. https://support.lavu.com/en/knowledge/lavu-kds-settings-functions-and-features · retrieved 2026-08-02 adversarially verified

kitchen-guest-ready-notification differentiator

Lavu's Kiosk listing (seller Lavu Inc, v2.5, July 2024) lists 'Works with Lavu Order Monitor Screen' among its features, and status.lavu.com monitors an 'Order Status Monitor' component, so a guest-facing order-status display exists in the product line; lavu.com/kitchen-display-system-kds/ adds that the KDS can 'notify servers when orders are ready'. Shortfall: no article or listing says a KDS bump drives the monitor (the documented context is kiosk order placement), no SMS or app-push guest notification is documented anywhere, the help centre has no Order Monitor article, and whether the monitor is included or a separate purchase is unpublished. https://apps.apple.com/us/app/lavu-kiosk/id1314002834 · retrieved 2026-09-02 adversarially verified

kitchen-waste-logging

Waste logging with reason codes that depletes stock is documented: Waste Items requires Item Name, Waste Quantity, and Waste Reason, with preloaded reasons (Damage, Spoilage, Mismade) plus custom reasons 'to be used in the Control Panel and POS'. Shortfall: entry is from the Inventory Manage area or POS functions, not from the kitchen/KDS screen. https://support.lavu.com/en/knowledge/inventory-manage-tab · retrieved 2026-08-05

kitchen-speed-of-service-reporting

Ticket timing exists only as a live on-screen artefact - the per-tile order timer and its colour-change duration thresholds - and is not persisted into any report. The help centre's Reports set is fully enumerable under Lavu Control Panel > Reports (Bank Deposit, Best Sellers, Change Bank, Daily Totals, General Ledger, Hourly Sales, Kitchen Change Log, Paid In/Out, Refund Summary, Register Sales, Sales by Category, Sales by Item, Super Groups, Time Cards, Voided Orders, Reopened Orders and the End of Day overviews); none reports actual ticket or per-station times, and Kitchen Change Log records edits rather than durations. https://support.lavu.com/en/knowledge/lavu-kds-settings-functions-and-features · retrieved 2026-09-04 adversarially verified

kitchen-prep-forecasting

Checked the whole Inventory module in the 250-article support.lavu.com help centre dumped in full on 2026-08-08 (244 sitemap articles plus 9 found by cross-link) - Settings, Dashboard, Manage Tab, Import/Export, Reconciliation, Transfers, Vendors, Link Ingredients, Alerts, Creating Ingredients - plus the report enumeration. The strings 'forecast', 'prep list', 'par level' and 'production' occur ZERO times in all 250 articles. The Inventory Dashboard is enumerated (Low Stock Level, Inventory Value, Pending Transfers, Waste Summary, Purchase Order Summary, and a 'Use First' list of perishables older than a chosen age in a chosen category) and is reactive stock management, not predicted prep quantities; 'Inventory Settings' self-scopes as 'a small section of settings'. Marty AI is marketed on lavu.com as generating operational predictions (grade D) and appears nowhere in the help centre. Unresolved.

delivery-driver-roster

OVERTURNED. Drivers are not absent from the product, only from the help centre. Lavu's Delivery and Routing extension is documented in Lavu's own 17 July 2014 release: "The iPad terminal displays delivery orders and lets staff assign drivers to those orders", with the extension "available for all Lavu iPad POS accounts" at $30 added to the monthly hosting fee; lavu.com currently markets "Lavu's driver management tools" and "You know where your drivers are". Named shortfall: driver-order assignment is the only limb evidenced. Driver clock-in/out as a distinct state, the in-store / on-run / returning assignment states, and per-driver run-history reporting are documented nowhere, the module is a paid add-on rather than base POS, and the 250-article support.lavu.com corpus contains no article on it at all - so the depth of the roster cannot be established and the evidence is grade D marketing. https://www.prnewswire.com/news-releases/lavu-includes-delivery-and-routing-extension-for-restaurant-ipad-pos-267481231.html · retrieved 2026-08-08 adversarially verified

delivery-dispatch-board

OVERTURNED. A delivery-order screen with driver assignment and multi-order batching is documented: "The iPad terminal displays delivery orders and lets staff assign drivers to those orders" and "Multiple Order Routing groups two or more orders together and Lavu maps out the most efficient route with turn by turn directions" - which is exactly the 2+ orders to one driver as a single run that the claim asks for. Named shortfall: the three status columns the claim also requires - an undispatched queue, driver availability, and elapsed time per order - are not described anywhere; the release only says the system manages "orders down to the minute" by factoring "delivery preparation, route duration, and time at the door". The feature is a paid $30/month extension, is absent from the 250-article help centre entirely, and the evidence is a vendor release, so no screen-level confirmation exists. https://www.prnewswire.com/news-releases/lavu-includes-delivery-and-routing-extension-for-restaurant-ipad-pos-267481231.html · retrieved 2026-08-08 adversarially verified

delivery-route-map differentiator

OVERTURNED on the sequencing limb. Lavu's Delivery and Routing extension performs system-generated route sequencing: "Lavu will consider the options for the sequence of deliveries, and give you the best one" and "Multiple Order Routing groups two or more orders together and Lavu maps out the most efficient route with turn by turn directions" (17 July 2014, $30 added to the monthly hosting fee). Named shortfall: the claim additionally requires a live map view on the dispatch screen with geocoded stops, and the documented delivery of the route is to the driver, not to a dispatcher - "Drivers are provided with a map and directions to each delivery location via text message or printed receipt". No dispatcher-side live map is described, the module is a paid add-on absent from the 250-article help centre, and the evidence is a vendor release (grade D), which is below the A/B bar a differentiator `yes` would need in any case. https://www.prnewswire.com/news-releases/lavu-includes-delivery-and-routing-extension-for-restaurant-ipad-pos-267481231.html · retrieved 2026-08-08 adversarially verified

delivery-driver-tracking differentiator

Downgraded from `no` on 2026-08-08. The premise the `no` rested on - that Lavu has no driver entity and no driver-facing app, so 'there is no channel by which a position could be surfaced' - is false. Lavu's Delivery and Routing extension assigns drivers to orders (Lavu release, 17 July 2014) and lavu.com currently markets "Lavu's driver management tools make this simple. You know where your drivers are." But that marketing line is grade D and vague, and no evidence was found for the specific mechanism the claim names: a driver-facing mobile app emitting live GPS back to a dispatch screen. The one documented route-delivery mechanism runs the other way - "Drivers are provided with a map and directions to each delivery location via text message or printed receipt" - which implies no driver app. Lavu's only other iOS app, Lavu Pilot 2, is an owner reporting app ('access real-time sales data from their iOS device'), not a driver app. Neither present nor absent on the evidence available. adversarially verified

delivery-zones-polygon differentiator

MenuDrive: "You can define a delivery area as a radius around your store or create custom delivery zones on a map using geofencing", and the documented mechanic is dragging the edges of the radius on a map to make zones with different fees. Shortfall: a deformable radius, not vertex-drawn arbitrary polygons; no drive-time isochrones and no ZIP/postcode list. https://support.lavu.com/en/knowledge/how-do-i-set-up-delivery · retrieved 2026-08-02 adversarially verified

delivery-zone-pricing

Same doc: once a zone exists, "the delivery charge set on the ACP Location Profile page will be ignored and the delivery charge set on the Customize Your Delivery Zones page will be the charge applied" — per-zone fee override, documented. https://support.lavu.com/en/knowledge/how-do-i-set-up-delivery · retrieved 2026-08-01 adversarially verified

delivery-address-validation

MenuDrive validates the guest address against the configured delivery geometry at checkout: "the system will check to see if his or her delivery address is in your defined area", and a guest outside the boundary is notified rather than allowed to place the order. Boundary is either a radius around the store or a map-drawn geofence. https://support.lavu.com/en/knowledge/how-do-i-set-up-delivery · retrieved 2026-08-02

delivery-driver-comp differentiator

Downgraded from `no` on 2026-08-08. The `no` was built entirely on the claim that 'orders cannot be attributed to a driver at all', and that is false: Lavu's Delivery and Routing extension "lets staff assign drivers to those orders" (Lavu release, 17 July 2014, $30 added to the monthly hosting fee) and lavu.com still markets driver management. With the driver-order linkage restored, nothing forecloses per-run compensation capture, and the researcher's own caveat was that Lavu Payroll's earning-code surface was never enumerated. Positively, no evidence was found either way for per-run mileage or distance, a per-delivery flat reimbursement value, or a reimbursement-versus-wage split on the payroll export; 'mileage' and 'reimburse' have zero occurrences in the 250-article help centre, but that corpus demonstrably omits the delivery extension itself. Undetermined. adversarially verified

delivery-cash-reconcile

Lavu ships two settle-up flows: Cash Reconciliation for a shared till, and - per this article's own note - Server Reconciliation 'if you have specific employees tied to specific cash tills'. Either tills in and out by denomination, tracks 'every cash transaction, card tip, refund, deposit, refunded deposit, pay in, and pay out', and on close prints a till summary including 'your variance, or the difference between what you entered and what Lavu calculated you should have'; the add/subtract/ignore treatment of each Till-In/Till-Out line is configurable under Advanced Location Settings - Account Settings. Shortfall: this is a generic per-employee bank, not a driver settle-up. Orders carry no driver linkage (no driver field in the public order schema), so 'orders assigned' and driver-retained tips owed are not part of the reconciliation, and no delivery-specific over/short is produced. https://support.lavu.com/en/knowledge/management-tools-cash-reconciliation · retrieved 2026-08-08

delivery-daas-dispatch

Positive evidence of absence, stated as the article's own premise. MenuDrive's delivery guide is written for the operator who says 'I have staff to deliver ... I am not interested in using a third-party delivery service', and the whole configured surface is in-house: the order-type toggle, a radius or geofenced zones, per-zone charges, and zone enforcement at checkout. Lavu's only courier-marketplace surface is the DoorDash DSP integration, which ingests orders placed on DoorDash rather than handing a first-party order to a courier; no DoorDash Drive, Uber Direct, Nash or Relay handoff exists in the complete 249-article help centre or in the api.lavu.com OpenAPI spec. https://support.lavu.com/en/knowledge/how-do-i-set-up-delivery · retrieved 2026-09-04 adversarially verified

delivery-daas-fallback differentiator

Hybrid overflow presupposes a courier handoff that does not exist. The delivery configuration the article enumerates has exactly one failure branch and it is refusal, not escalation: an out-of-zone address triggers a message and the guest is 'asked if he or she wants to resume with pickup or use another delivery address'. There is no driver-availability condition, no wait threshold, and no rule that routes an order to a third-party courier. https://support.lavu.com/en/knowledge/how-do-i-set-up-delivery · retrieved 2026-09-04 adversarially verified

delivery-3p-direct-integration differentiator

Partial is right but the researcher's reasoning was wrong in both directions. Lavu's own integrations page annotates DoorDash, Grubhub, Uber Eats and Xero with "Integration available with integrator" — affirmative evidence those are middleware-brokered, which the researcher did not find. But the DSP support doc shows a genuinely direct Lavu DSP→DoorDash API path. So: DoorDash direct (US only), Uber Eats and Grubhub integrator-mediated. Partial stands on corrected evidence. https://lavu.com/integrations/ · retrieved 2026-08-01 adversarially verified

delivery-3p-injection

DSP Integration doc describes a first-party pipe: "MenuDrive sends the request to Lavu DSP, then Lavu DSP calls the DoorDash API, finally DoorDash confirms the store activation to Lavu DSP", and "Orders from DoorDash go straight to the kitchen". US-only; explicitly not available for Mexico locations. https://support.lavu.com/en/knowledge/dsp-integration-delivery-service-provider-integration · retrieved 2026-08-01 adversarially verified

delivery-menu-push

Same doc documents a "Sync Menu" function with progressive POS→MenuDrive sync propagating to DoorDash. 86 sync and store pause remain undocumented. https://support.lavu.com/en/knowledge/dsp-integration-delivery-service-provider-integration · retrieved 2026-08-01 adversarially verified

delivery-86-sync

Documented POS-to-marketplace availability sync: "The DoorDash and Lavu POS integration automatically adds inventory tracking to DoorDash. If an item is out of stock on the POS, then the item will automatically be removed from the DoorDash storefront." Doc states this works from either Item Level 86 Tracking or the Lavu inventory platform. https://support.lavu.com/en/knowledge/lavu-menu-drive-and-door-dash · retrieved 2026-08-02

delivery-store-pause

Temporary-closure control in the DoorDash integration screen: a slider activates the closure and the operator selects when the store automatically reopens; the doc states it "will immediately prevent your customers from submitting orders" through DoorDash. Scheduled auto-reopen is part of the same control, so the operator is not required to remember to unpause. https://support.lavu.com/en/knowledge/lavu-menu-drive-and-door-dash · retrieved 2026-08-02

delivery-3p-reconciliation differentiator

The DoorDash integration article enumerates every screen it adds to the MenuDrive Control Panel - Delivery Providers with Connect/Onboard, Sync Menu, out-of-stock sync, dual pricing, temporary closures, special store hours - and none of them reports money. Payout deposits, commission, marketing fees and adjustments are not surfaced on the Lavu side at all, and the MenuDrive reporting set (Menu Drive - All Reports, automated reports, Coupon Reports, Google Analytics) reports orders and coupons rather than marketplace remittance, so there is nothing to match deposits against POS-recorded 3P sales. https://support.lavu.com/en/knowledge/lavu-menu-drive-and-door-dash · retrieved 2026-09-04 adversarially verified

delivery-injection-error-visibility differentiator

Menu-sync health is surfaced to the operator: 'If the sync fails, it throws an error and asks you to try again', with last-sync date/time shown on the Delivery Providers page, which also shows the DoorDash connection state. Shortfall: order-level injection failures are not surfaced - no alerting or failed-order queue is documented for order ingestion. https://support.lavu.com/en/knowledge/dsp-integration-delivery-service-provider-integration · retrieved 2026-08-05

delivery-tracking-page

Guest-facing status exists but is order-state only. From the Order Dashboard the operator taps Confirm, checks 'send confirmation' and picks a ready time, which 'send[s] an email to the customer' with the estimated prep time; on the storefront, registered customers 'can select from various pages to manage their account' including Order History, where they can also provide feedback. Shortfall: there is no branded tracking page driven by real driver state - no driver entity exists anywhere in the product (the public order schema has no driver field) - and no SMS status link to the guest is documented; MenuDrive's 'text notifications' order-receiving method notifies the restaurant, not the guest. https://support.lavu.com/en/knowledge/menu-drive-order-dashboard · retrieved 2026-08-08

delivery-promise-time differentiator

Positive evidence of the excluded mechanism: the quote is a fixed per-store constant by design. Preparation Time is set per fulfilment type on the Location Profile and the worked example applies it unconditionally - a 30-minute setting tells an 8:25 p.m. guest the order will be ready 'around' 8:55 - with the only documented adjustment being an operator editing the pickup/delivery hours. Kitchen load, driver availability and zone drive time are not inputs; the delivery zones the operator draws carry a charge, not a duration. https://support.lavu.com/en/knowledge/menu-drive-order-types-and-prep-time · retrieved 2026-09-04 adversarially verified

delivery-offline-behavior

Downgraded from `no` on 2026-08-08. Two problems. First, the note's closing reason - 'no driver entity exists to have an outage behaviour' - is false; Lavu's Delivery and Routing extension assigns drivers to orders (Lavu release, 17 July 2014). Second, the remaining argument is a corpus-wide null grep ('offline' resolves only to lavu-crash-kit-101 and basic-network-troubleshooting), and that corpus is not a census: status.lavu.com monitors Lavu components (Lavu To Go, Pilot, Order Status Monitor, Lavu Local Server, Phone System) with no help-centre coverage, and the delivery extension itself is absent from all 250 articles. What Crash Kit 101 does document is generic rather than delivery-specific - cash transactions, opening the drawer, adding to and starting orders, sending to the kitchen and printing checks all continue offline - and it says nothing about driver assignment or driver settlement. Whether delivery-specific offline behaviour is documented elsewhere is undetermined. adversarially verified

digital-first-party-web

MenuDrive by Lavu is a first-party ordering site on the restaurant’s own branding that writes into the POS, positioned to keep "your customers ordering from you – not third parties". Shortfall: the claim requires it be commission-free, and Lavu publishes no MenuDrive commercial terms anywhere — no per-order fee, no rate card, no statement that no commission applies. Scoring yes would assume an unpublished term favourable. https://lavu.com/online-ordering/ · retrieved 2026-08-02 adversarially verified

digital-menu-single-source

The 'POS Menu Auto-Sync with MenuDrive' feature 'helps business owners to manage the same menus on both platforms (Lavu POS & MenuDrive) from a single point of origin', and propagates onward: 'Lavu POS menu will take up to 5 minutes to get updated from Lavu POS to the MenuDrive and another 2 minutes to update it to the DoorDash menu.' Shortfalls: MenuDrive is a separate menu record with its own builder (basic-menu-building-in-menu-drive), and only 'locked' MenuDrive items sync - 'Any unlocked menu items in the MenuDrive will be exempted from the sync process'; the operator cannot enable it themselves ('a representative from the Customer Success team will enable the POS Sync V2 option'); and MenuDrive QR dine-in ordering runs on a separate MenuDrive location whose menu the customer success team copies over, so that channel is a second build. https://support.lavu.com/en/knowledge/auto-sync-your-menu-drive-menu-with-lavu-pos · retrieved 2026-08-08

digital-native-app differentiator

Positive absence across the product's own documentation index. The Menu Drive category page enumerates all forty of its articles under Order Receiving Methods, Marketing, Reports, Menu Building, Payments, Settings, General Walkthrough, Design Settings and DoorDash; the guest-facing artefact throughout is a hosted web storefront (each location gets an orders.<name> URL) styled through Design Settings and the Photo Manager and reached by QR code. No article covers publishing a branded iOS or Android app, and menudrive.com's own feature catalogue lists storefront and template tooling with no app build. The only Lavu-published App Store title is the operator-side Lavu POS client. https://support.lavu.com/en/knowledge/menu-drive · retrieved 2026-09-04 adversarially verified

digital-account-saved-payment

MenuDrive storefront supports registered guest accounts: customers "create an account within your storefront", then manage contact information, saved credit card numbers and a saved delivery address "for faster ordering", plus order history. Account-creation form fields are configurable by the operator in the Control Panel. https://support.lavu.com/en/knowledge/menudrives-online-ordering-storefront-3.0 · retrieved 2026-08-02

digital-upsell-engine differentiator

'Built-in upsell and add-on marketing' in MenuDrive; no attach-rate reporting documented. https://lavu.com/online-ordering/ · retrieved 2026-08-01

digital-scheduled-pacing

Named shortfall: scheduling exists, pacing does not. Checkout exposes "Order Pickup Time" with ASAP and Advanced options, so a guest can place an order for later. No throttle, capacity-per-interval, quote-time stretch or blackout-slot control is documented anywhere in the storefront, checkout or Location Profile articles — the same gap the 86-count doc exposes, where advance orders are explicitly outside availability tracking. https://support.lavu.com/en/knowledge/menudrives-online-ordering-storefront-3.0 · retrieved 2026-08-02

digital-fulfillment-modes

Named shortfall: only two fulfillment modes are documented. The storefront order-type popup lets a guest choose "what kind of order they would like (ASAP vs. Advanced, Pick Up vs. Delivery, etc.)". Pickup and delivery are documented; curbside, dine-in/table and drive-up modes appear nowhere in the storefront or checkout articles. https://support.lavu.com/en/knowledge/menudrives-online-ordering-storefront-3.0 · retrieved 2026-08-02

digital-qr-table

QR scan-to-pay from the printed receipt is documented; scan-to-order attaching to an open POS check, splitting and tipping are not. https://lavu.com/contactless-payments-ordering/ · retrieved 2026-08-01

digital-kiosk differentiator

A first-party kiosk ships — help-centre articles "Lavu Kiosk - Order Workflow", "Lavu Kiosk - Basic Customization" and "Lavu Kiosk - Receipt Printers", plus a monitored Kiosk status component. Shortfall: the claim also requires accessibility-compliant UI and unattended EMV payment; Lavu publishes no ADA/WCAG conformance statement and names no unattended payment device. https://support.lavu.com/en/knowledge/lavu-pos · retrieved 2026-08-02 adversarially verified

digital-group-ordering

Positive absence by enumeration of the ordering product's whole documented surface: the forty Menu Drive articles cover the storefront, order types, prep time, delivery zones, payments (tips, taxes, custom options), coupons, loyalty, email automations, QR codes, menu building and reporting. Nothing creates a shareable multi-participant cart, a per-person or total spend cap, or a payment split across participants; MenuDrive checkout is one guest, one order, on the account-and-saved-payment model documented in the storefront article. https://support.lavu.com/en/knowledge/menu-drive · retrieved 2026-09-04 adversarially verified

digital-catering-portal differentiator

MenuDrive covers slices of catering: per-item 'MIN OR MAX PER ORDER' is 'especially helpful with catering menus where there is a 5 person minimum', item visibility supports 'advanced ordering', and stores can accept Advance Orders alongside ASAP. Shortfalls: no separate catering ordering flow or menu, no lead-time rules beyond prep time, no quotes/proposals, no deposits online, and no invoice/house-account or ACH payment terms. https://support.lavu.com/en/knowledge/menu-items-advanced-settings · retrieved 2026-08-05

digital-voice-ai-phone differentiator

A live /_hcms/search for 'voice' returns 0 knowledge articles and the string appears once in the whole dumped corpus (unrelated). No certified phone-ordering partner is named in the 250-article support.lavu.com help centre dumped 2026-08-08 (sitemap plus cross-linked articles). lavu.com/marty-ai/ - grade D, and the only Lavu surface that discusses AI - lists overnight signal scanning, menu pricing, labor scheduling, slow-hour promotions, server coaching, margin protection, inventory and marketing automation, and says nothing about answering inbound calls. 'Marty' appears zero times in the help centre, so no shipped-feature documentation exists for any of it. A 'Phone System' component on status.lavu.com is a monitored service name and cannot establish a capability. Unresolved in either direction.

digital-drivethru-ai

There is no drive-thru lane in the product for a voice agent to sit in front of. Order Types enumerates the shipped order flows as Dine In, Pickup and Carry Out across the Quick Serve, Tables and Tabs service layouts, and 'drive-thru' occurs zero times in the complete 249-article help centre or the 4,844-URL first-party sitemap census. Lavu sells no lane hardware - no speaker post, headset or confirmation display - in its forty-product store, and no AI voice surface of any kind, escalation path included, is documented anywhere. https://support.lavu.com/en/knowledge/order-types · retrieved 2026-09-04 adversarially verified

digital-sms-ordering

Positive absence by enumeration. SMS appears in MenuDrive only as an order-receiving alert to the operator - menudrive.com/how-it-works lists 'Accept orders through email, text, and/or your online dashboard' - and the Order Receiving Methods articles configure that outbound notification. No article in the forty-article Menu Drive set, or anywhere in the 249-article help centre, documents a guest-facing conversational SMS or chat ordering path that lands an order in the POS, and Lavu's campaign tooling is email-only (Marketing - Email Automations, with a built-in or custom mail server). https://support.lavu.com/en/knowledge/menu-drive · retrieved 2026-09-04 adversarially verified

digital-google-order differentiator

OVERTURNED by the no-audit on 2026-09-04. The finding that survives is narrow: nothing in the 40-article Menu Drive set or on menudrive.com provisions a Google Business Profile ordering link, and the two Google references in the corpus are analytics and a lead-generation Business Profile audit. But Order with Google provisioning is a relationship between Google and the ordering provider that is often invisible in the provider's own help centre, and the determining evidence - whether MenuDrive appears in Google's ordering-partner list - is a Google-side fact this pass did not retrieve. Documentation silence on the vendor's side is not positive absence here. adversarially verified

digital-apple-business-connect

OVERTURNED by the no-audit on 2026-09-04, on the same ground as the Order with Google cell. Apple Business Connect place-card actions are configured by the merchant in Apple's own console and can point at any ordering URL, so the vendor-side integration this claim asks about - a documented placement of the first-party ordering flow as an 'Order Food' custom action - would not necessarily surface in Lavu's help centre even if it existed. Corpus-wide silence (Apple appears only as the iPad platform and Apple Pay acceptance) is real but is not evidence of absence. adversarially verified

digital-loyalty-attach

Named shortfall: redemption online, accrual undocumented online. The MenuDrive storefront lets a signed-in customer "redeem loyalty points for discounts", so the online channel reads the loyalty balance. But the POS-side award flow requires staff to select Lavu Loyalty and key or scan a loyalty card at checkout, and no article documents points being earned on a MenuDrive web order or the two identities being merged. https://support.lavu.com/en/knowledge/menudrives-online-ordering-storefront-3.0 · retrieved 2026-08-02

digital-subscriptions

Positive absence by enumeration of the guest-monetisation surface. MenuDrive's retention tooling is fully documented and consists of coupons, a points-based loyalty program with redeemable rewards, email automations and announcements; the coupon object exposes discount type, validity dates, login requirement, usage limits, minimum subtotals and public/private, with no recurring charge, entitlement period or membership tier. Nothing in the Menu Drive or Lavu Gift/Loyalty sets bills a guest on a schedule or waives fees for a paid tier. https://support.lavu.com/en/knowledge/menu-drive · retrieved 2026-09-04 adversarially verified

digital-promo-parity

Named shortfall: online coupons are a separate object from POS discounts. The storefront checkout includes a "Coupon Codes" section and MenuDrive carries its own Coupon Reports showing "the amount of money your customers have saved by using coupons and the average discount per order". Lavu POS discounts are configured independently under Settings > Payment > Discount Types in the Control Panel; no shared promotion record or parity-enforcement between the two is documented. https://support.lavu.com/en/knowledge/menudrives-online-ordering-storefront-3.0 · retrieved 2026-08-02

digital-guest-data-ownership differentiator

ToS grants Lavu a perpetual, irrevocable, sublicensable license over user content including AI training, and states Lavu 'has no obligation to... allow extraction of User Content or User Data post-termination'. No operator bulk-export right is documented. https://lavu.com/terms-of-service/ · retrieved 2026-08-01

digital-checkout-pci-sca

Checkout runs entirely on the vendor-hosted storefront (each location gets 'https://orderstart.com/<the name of the restaurant>'), so card entry never touches a restaurant-owned page, and Lavu publishes that its software and readers are PCI compliant, with Lavu Pay compliance maintained 'through your card reader and your CardConnect account'. Shortfalls: no published PCI DSS 4.0 attestation (the compliance article is generic) and no documented 3DS/SCA support for MenuDrive checkout. https://support.lavu.com/en/knowledge/menu-drive-location-profile · retrieved 2026-08-05

digital-surcharge-transparency differentiator

The digital channel does carry payment-conditional fees: MenuDrive's Payments > Custom Options page creates custom charges 'on all orders, orders paid with cash only, or orders paid with cards only', fixed or percentage, named as they appear on the guest's receipt; and lavu-menu-drive-and-door-dash documents a Dual Pricing percentage applied to the DoorDash storefront ('We recommend a dual pricing increase of 5%'). Shortfalls: this is not the POS configuration - the Cash Discount Program article scopes CDP to the register (two prices shown at checkout, both totals on the printed check), is 'only available in the U.S., and to Lavu Pay customers', and never mentions MenuDrive; the digital surcharge is a separately configured custom charge rather than the same dual-price record. No guest-facing disclosure text, no jurisdiction list and no card-brand prohibition handling is documented for any channel. https://support.lavu.com/en/knowledge/menu-drive-payments-custom-options · retrieved 2026-08-08

guest-loyalty-unified-profile

Named shortfall: the identity is a card, not a person. Loyalty is attached at checkout by entering "the customer's loyalty number" or scanning their card, and the Control Panel Gift & Loyalty Cards page keys balances and history to the card record. A MenuDrive registered account is a separate record with its own credentials, saved cards and address. No documented merge, lookup-by-phone/email, or single guest profile spanning POS, online ordering and gift/loyalty. https://support.lavu.com/en/knowledge/awarding-loyalty-points-and-redeeming-loyalty-discounts · retrieved 2026-08-02

guest-loyalty-thirdparty-identity-attach differentiator

The public order schema does carry a guest object - LavuApiOrderSerializer has a `customer` member (LavuApiCustomer: f_name, l_name, email, phone, street, city, state, zip) plus togo_name/togo_phone and an order-level email - so a marketplace order could in principle arrive attached. But nothing documents that it does: dsp-integration-delivery-service-provider-integration walks store onboarding, menu export and order ingestion and specifies only that 'the financial details for each DX order' (item price, modifier price, taxes, tips) now display, and lavu-menu-drive-and-door-dash covers connection, menu sync, 86 handling, dual pricing and store hours. Neither says what guest identity accompanies the order. Lavu's own loyalty identity is a loyalty number or barcoded physical card presented at the register, which is not a channel-independent guest profile. Uber Eats and Grubhub appear nowhere in the 250-article support.lavu.com help centre dumped 2026-08-08 (sitemap plus cross-linked articles). Unresolved.

guest-loyalty-accrual-models

Named shortfall: one accrual model only. Points accrue per menu item — items "must have point values pre-assigned" and staff then "Award the points available" at checkout. Redemption offers two "Loyalty Style" options: the discount either "will cost the amount of Loyalty Points" or "will be unlocked at the point threshold". No spend-based, visit-based, category-multiplier or time-boosted accrual is documented, and the award doc states outright that "You cannot award and redeem points within the same transaction". https://support.lavu.com/en/knowledge/creating-lavu-loyalty-discounts · retrieved 2026-08-02

guest-loyalty-tiers differentiator

A rudimentary status level exists: 'You can also create discounts that provide a permanent discount once a customer reaches a certain number of points', configured by setting Loyalty Points to the threshold and Loyalty Style to unlocked-at-threshold rather than costs-points ('or if it will be unlocked at the point threshold entered for step thirteen (uncommon)'). Shortfalls: promotion is by lifetime accumulated points, not a rolling window of spend or visits; there is no demotion mechanism, no member level or tier entity, and no tier-specific benefits beyond the single attached discount. The MenuDrive loyalty program is separate and has no tier setting at all - its page configures only on/off, title, earn basis (orders or dollars), points per unit, subtotal-or-total, Facebook-like points, terms, and rewards each requiring an attached coupon. https://support.lavu.com/en/knowledge/creating-lavu-loyalty-discounts · retrieved 2026-08-08

guest-loyalty-offline-behavior differentiator

OVERTURNED in part. Lavu Crash Kit 101 does state connectivity behaviour for the gift/loyalty card system, in an explicit list of what survives an outage: 'Conduct cash transactions... Open the cash drawer... Add food and drink to open orders... Start new orders... Send orders to the kitchen... Print checks', followed by 'None of the features above require an internet, or database connection. Most notably what is missing, are credit card and gift card transactions. Both of which require an active connection to the internet to validate card details.' Lavu's loyalty product is Lavu Gift/Loyalty and the documented POS lookup path is the loyalty card number or barcode scan, so redemption against a card is documented as blocked, not queued. Named shortfall: the article never separates loyalty from gift, and it says nothing about what point ACCRUAL does during an outage - whether points earned on an order closed offline are queued and reconciled on reconnect or silently lost is nowhere stated, and none of the loyalty articles (awarding-loyalty-points-and-redeeming-loyalty-discounts, creating-lavu-loyalty-discounts, manage-lavu-gift-and-loyalty-card-balance-and-expiration-date) mentions connectivity at all. https://support.lavu.com/en/knowledge/lavu-crash-kit-101 · retrieved 2026-08-08 adversarially verified

guest-loyalty-offer-stacking-rules differentiator

Positive absence in a complete configuration enumeration. Marketing - Creating Coupons walks the entire coupon record: enable/disable, coupon code, discount type and amount, validity dates or Never Expires, login requirement, usage limit, a brand-wide limit across MenuDrive accounts, minimum subtotals including a delivery-specific one, public/private, and under Advanced Settings a per-email allow list and a required cart item or category. There is no exclusive-versus-combinable flag and no precedence or order-of-application setting; redemption is by entering one code at checkout, and the loyalty tie-in requires a reward's coupon to be limited to a single use. https://support.lavu.com/en/knowledge/marketing-creating-coupons · retrieved 2026-09-04 adversarially verified

guest-loyalty-targeted-offers differentiator

Recency-rule targeting is documented: email automations trigger on events such as 'last order' - 'choosing last order and sending a message out with a coupon for a free item after one of your customers hasn't ordered from you for 30 days' - plus birthdays, anniversaries, and sign-ups, with private coupons attachable and coupons restrictable to specific customer email addresses. Shortfalls: no frequency, spend, or items-purchased audience rules, and delivery is email-only. https://support.lavu.com/en/knowledge/marketing-email-automations · retrieved 2026-08-05

guest-loyalty-rfm-segmentation differentiator

Positive absence by enumeration of the targeting model. Marketing - Email Automations documents the whole campaign record - enable, name, subject line, trigger, message body, an optional attached coupon and an active date range - and targeting is an operator-authored event rule, the article's own example being 'choosing last order and sending a message out with a coupon for a free item after one of your customers hasn't ordered from you for 30 days'. No segment object exists, and nothing computes recency/frequency/monetary or lifecycle classes (new, regular, at-risk, lapsed, VIP) on the operator's behalf. https://support.lavu.com/en/knowledge/marketing-email-automations · retrieved 2026-09-04 adversarially verified

guest-loyalty-lifecycle-automation

MenuDrive ships CRM tools and 'email automation' plus a coupon/QR generator; specific birthday, first-visit and lapsed win-back triggers are not named. https://lavu.com/online-ordering/ · retrieved 2026-08-01

guest-loyalty-native-email-sms differentiator

Native email automation is documented; native SMS campaigning is not. https://lavu.com/online-ordering/ · retrieved 2026-08-01

guest-loyalty-consent-management

Checked the three places a guest hands over contact details. customer-management documents the POS signup form as configurable ('marking certain fields as required or optional and adding new custom fields') with no consent checkbox, timestamp or source field described. menudrives-online-ordering-storefront-3.0 covers registered accounts (contact details, saved cards, delivery address, order history) with no marketing opt-in. marketing-email-automations walks mail-server setup and trigger-based campaigns end to end with no subscriber list, opt-in state or unsubscribe handling. 'Consent', 'opt-in' and 'unsubscribe' appear zero times in the 250-article support.lavu.com help centre dumped 2026-08-08 (sitemap plus cross-linked articles) and return 0 live search hits. None of these articles purports to enumerate the compliance surface, so per-channel consent capture and revocation are undocumented rather than shown absent.

guest-loyalty-10dlc-registration

Downgraded from `no` on 2026-08-08. The entire basis is a help-centre search that returned nothing ('10DLC', 'A2P' and 'SMS' zero across 250 articles; a live /_hcms/search for 'sms' returning 0), which the absence bar disqualifies, and the corpus is demonstrably not a census of the product - status.lavu.com monitors Lavu components (Lavu To Go, Pilot, Order Status Monitor, Lavu Local Server, Phone System) that the help centre never documents, and Lavu's own Delivery and Routing extension, which sends drivers routes 'via text message', appears in no article at all. The cited page, marketing-email-automations, is an email setup guide and never purports to enumerate Lavu's messaging channels. Lavu does operate text surfaces (MenuDrive text notifications, status-page text alerts, driver route texts), so the premise that there is no SMS to register is also unsafe. Whether Lavu handles or documents A2P 10DLC registration is undetermined. adversarially verified

guest-loyalty-campaign-attribution differentiator

Coupon Reports track per-coupon usage - 'the amount of money your customers have saved by using coupons, and the average discount per order' - and coupons are the redemption vehicle attached to email campaigns and loyalty rewards, so campaign redemptions are countable per coupon code. Shortfalls: no incremental-sales attribution, and redemptions are not tied to actual check totals by campaign in any documented report. https://support.lavu.com/en/knowledge/menu-drive-all-reports · retrieved 2026-08-05

guest-loyalty-data-export-portability differentiator

Self-serve export exists on both sides. In the Lavu Control Panel: 'Once you have captured customer information in the POS, you can export it from your V1 reports. Click on Reports, then V1 Reports, and under the column labeled Special, click on Customer Export' - the profile carries name, address, phone, email and custom fields, and a matching Customer Import accepts CSV. In MenuDrive, the Order History report can be filtered by order type and date and 'download[ed] ... in a PDF or CSV file'. Shortfalls: Customer Management 'will first need to be turned on by a Lavu admin', so the guest list is gated behind a support request; the two exports live in different products and nothing documents an export that joins a guest to their transaction history; the MenuDrive Registered/Guest Customers reports are on-screen tabular views with no stated download; and the public API (api.lavu.com/docs/swagger.json) exposes orders, menus, payments and the API user's own profile but has no guest-list endpoint. https://support.lavu.com/en/knowledge/customer-management · retrieved 2026-08-08

guest-loyalty-review-capture-routing differentiator

A feedback channel exists and is guest-initiated: on the MenuDrive storefront, signed-in customers 'can update their contact information, credit card numbers, and delivery address for faster ordering, provide feedback through their Order History, and redeem loyalty points for discounts.' Shortfalls: nothing triggers a post-transaction request - the only automated guest email documented is the Order Dashboard's ready-time confirmation, and marketing-email-automations' triggers are birthdays, anniversaries, sign-ups and last-order recency, not order completion; there is no score capture, no threshold and no routing, and only registered customers have an Order History to leave feedback in. For public reviews, Lavu's documented method is manual: let-yelp-help teaches the operator to save a Yelp badge image, upload it under Add Footer Image and set the link URL. https://support.lavu.com/en/knowledge/menudrives-online-ordering-storefront-3.0 · retrieved 2026-08-08

guest-loyalty-referral-program

Positive absence, with the near-miss resolved. Lavu does run a referral program with attribution and rewards, but its terms make it a merchant-acquisition scheme rather than a guest mechanic: participants refer restaurants and bars to Lavu's POS platform, Lavu 'determine[s], in its sole discretion, whether a referral is eligible for a Referral Reward', and the payout schedule sits at go.lavu.com/en-us/refer-and-earn (the marketing page prices it at $2,500 for referring a restaurant). On the guest side, Marketing - Loyalty and Rewards enumerates every program setting - earn by orders placed or by dollars spent, points per dollar on subtotal or total, a Facebook-like bonus, terms text, and rewards defined by title, description, point cost and repeatability - and none of them issues a per-guest referral code, attributes a referred guest's first order, or pays both sides. https://lavu.com/lavu-referral-program-terms-and-conditions/ · retrieved 2026-09-04 adversarially verified

guest-loyalty-wallet-pass differentiator

Positive evidence of a different delivery mechanism. Lavu's digital stored-value path is documented end to end and is an emailed barcode, not a wallet pass: keying 55555 at load time 'will generate a unique 24 digit gift card number that will be sent to the customer's email address', redemption is 'select Scan your card', which 'will turn on your iPad's rear facing camera, allowing to scan the bar code from the customer's email', and re-delivery is a resend from the Control Panel's History & Tracking list. There is no push-updatable balance and no Apple or Google Wallet pass anywhere in the complete 249-article help centre. https://support.lavu.com/en/knowledge/digital-gift-cards · retrieved 2026-09-04 adversarially verified

guest-loyalty-privacy-rights-tooling

Rudimentary tooling exists: in Customer Management the operator can search a guest by any captured detail and 'if you want to update or remove the information attached to the customer profile, click the Edit button', view their order History, and export the whole guest list from Reports > V1 Reports > Special > Customer Export - which covers the access half of a request by hand. Shortfalls: there is no rights-request workflow, no requester verification, no audit trail and no documented deletion propagation - the POS customer record, MenuDrive registered accounts, Lavu Loyalty point balances and the email-campaign audience are separate stores and no article describes a delete reaching more than the one profile in front of you. Lavu's privacy policy handles requests for Lavu's own data subjects by email/phone and caps CCPA requests at one per customer per year; it gives the operator no in-product tooling. https://support.lavu.com/en/knowledge/customer-management · retrieved 2026-08-08

guest-loyalty-redemption-fraud-controls

An audit trail is documented: the Control Panel card view shows "every action that has taken place on the card, including creation, loyalty and gift balances used, and manual adjustments", and card histories are "exclusive to the Control Panel for restaurant managers"; on the POS, balance adjustment sits behind the Functions > Manager Functions > Management Tools > Adjust Lavu Card path. Shortfalls: no redemption velocity limits and no flagging of employee self-redemption are documented anywhere, and manual adjustments are gated by menu placement and Control Panel access rather than a documented approval step. https://support.lavu.com/en/knowledge/manage-lavu-gift-and-loyalty-card-balance-and-expiration-date · retrieved 2026-08-03

guest-loyalty-ai-offer-recommendation differentiator

Lavu's own AI feature comparison (February 2026) scores Marty 'AI marketing campaign creation: No' - a vendor statement that offer content is not generated - while the site-wide Marty FAQ claims a timing recommendation: 'Marty spots slow periods. Lavu triggers targeted outreach or bundle suggestions', and the Enterprise plan on buy.lavu.com sells an 'AI Marketing' line. Shortfall: only the send-timing half of the claim is asserted; content and audience generation are denied by the vendor's own comparison; the mechanism is undocumented (MenuDrive's documented campaign engine is rule-based - birthday, anniversary, sign-up and days-since-last-order triggers with operator-written messages); and the feature is quote-only Enterprise. https://lavu.com/2026-restaurant-pos-ai-capabilities-report/ · retrieved 2026-09-02 adversarially verified

guest-loyalty-stored-value-gift

Lavu Gift is a documented first-party stored-value system, not a reseller wrapper: gift card items are sold from the POS via "Issue Card" (fixed or variable amount), redeemed as a payment type by swipe, manual entry or barcode scan, and "If the gift card used does not have a sufficient balance to pay for the order, the remaining balance will automatically be used." The Control Panel Gift & Loyalty Cards page shows "the cards current gift card and loyalty balance" plus "every action that has taken place on the card, including creation, loyalty and gift balances used, and manual adjustments", and an optional expiration date. Shortfall keeping this at partial: balances are keyed to a card ID rather than to a guest profile, and no brand-wide or cross-location redemption is documented anywhere in the Lavu Gift articles. https://support.lavu.com/en/knowledge/lavu-gift-selling-redeeming-gift-cards · retrieved 2026-08-02 adversarially verified

labor-clock-in-at-pos

Documented two ways, both on the POS terminal with no separate time-clock hardware: from the main POS screen, "Tap the menu button in the bottom left. Tap on Time Clock. Enter your PIN, or Passcode. Tap the clock icon on the PIN pad."; or from the PIN pad screen by tapping the server name then the clock icon. Punches land in the Time Cards report, reachable from End of Day > Manage Time Cards or Workforce > Manage Time Cards. https://support.lavu.com/en/knowledge/pos-clocking-in-and-out · retrieved 2026-08-02 adversarially verified

labor-photo-punch-verification differentiator

The punch flow is enumerated: enter PIN or Passcode and tap the clock icon (from Time Clock or the PIN pad screen), then 'complete the popups'; Manage Users documents RFID cards as the alternative credential. No photo capture or facial verification exists at punch anywhere in the labor documentation. https://support.lavu.com/en/knowledge/pos-clocking-in-and-out · retrieved 2026-08-05

labor-offline-time-punch differentiator

Checked 2026-08-08 against the full 250-article support.lavu.com dump. Lavu Crash Kit 101 (support.lavu.com/en/knowledge/lavu-crash-kit-101) is the only article that states what works without connectivity: 'Conduct cash transactions, Open the cash drawer, Add food and drink to open orders, Start new orders, Send orders to the kitchen, Print checks ... None of the features above require an internet, or database connection', and the only thing it names as missing is credit-card and gift-card processing. Time clock is not in either list. POS - Clocking In and Out documents the punch flow as menu > Time Clock > PIN > clock icon with no mention of connectivity, and Adjusting Time Cards / Time Card Reports are Control Panel (cp.poslavu.com) functions. Because Crash Kit 101 is an onboarding/installation overview whose list is order-centric rather than a completeness assertion, its silence cannot carry a no, and no source documents reconciliation-on-reconnect behaviour for punches.

labor-granular-rbac

Named shortfall: permissions resolve to five fixed hierarchical tiers, not per-action grants. "Lavu has five access levels (0-4) that are used to control which features of the application your employees are able to access" — 0 is "restricted to clocking in and out only", 1 servers, 2 floor managers ("access to voids, discounts, refunds, ability to re-open closed orders"), 3 owner/back end, 4 multi-location Control Panel switching only. Manage Users confirms assignment is by tier alone ("Here you will set the access level to your employee"), with no per-user permission checkboxes and no per-location grant. A few functions can be gated to a minimum level in Advanced Settings (PIN use while clocked out, server summary, Management Tools), which is why this is partial rather than a flat absence; void, comp, discount, refund, drawer open and price change cannot be granted independently of the tier. https://support.lavu.com/en/knowledge/lavu-access-levels · retrieved 2026-08-02 adversarially verified

labor-manager-override-audit

Named shortfall: an actor log, not an approval log. The Action Log records "all frontend activity including when orders are opened/closed, when cash drawers are opened, when employees clock in and out, and much more", and the current version supports filtering "to focus on a specific action or employee" — the doc's worked example is finding "which employees conducted refunds". What is not documented is a distinct manager-override event carrying the approver's identity separately from the operator's, nor a required reason code. The legacy V1 report "lacks all of the filtering options that are available in the newer version". https://support.lavu.com/en/knowledge/lavu-reports-the-action-log · retrieved 2026-08-02

labor-native-scheduling differentiator

Help-centre article 'Scheduling' (Lavu Control Panel > Workforce): "Lavu's scheduling platform is a great way to create and manage your employee's schedule. When a schedule is created, your staff can access their schedule online at my.poslavu.com, or you can export your schedule and print it." Documented flow: 'Open the Workforce - Scheduling Module', '+ New Shift', select Employee, select the Class they will work as during the shift, '+ Add Employee', From/To times, 'Click on all of the days the shift will Copy to', 'Add Shift'; plus Actions > Duplicate a previous week / Print / Hide Estimated Pay, and weekly management notes. Publication to staff is native ('have your employees check out my.poslavu.com to see their schedule online and request coverage'), and Workforce Settings carries the matching shift-change notification rules. This is the same Control Panel Workforce section that holds Time Cards, so timekeeping and scheduling are one platform - no third-party scheduling app is required. Earlier rationale relied on a multi-location marketing line about connecting external labor-scheduling platforms; the documentation overrides it. https://support.lavu.com/en/knowledge/scheduling · retrieved 2026-08-08

labor-demand-labor-forecast differentiator

Lavu markets Marty as recommending 'optimal staffing levels for every shift' from 'historical sales data... seasonal trends and local events', with morning briefings that 'recommend necessary staff levels', recommendations 'updated daily', and 'Marty forecasts sales. Lavu generates the schedule with labor control' (site-wide FAQ); the Marty companion app is shipped (App Store, Lavu Inc, June 2026) and the Enterprise plan sells 'Digital General Manager' and 'AI Reporting' lines. Shortfall: marketing-only description with no product documentation - the help centre's Scheduling article shows no recommended-hours output and Workforce Settings lists no forecasting element - daypart granularity is unstated, and Marty is quote-only Enterprise. https://lavu.com/marty-ai-scheduling-recommendations/ · retrieved 2026-09-02 adversarially verified

labor-realtime-labor-percent differentiator

"Management Tools - Live Labor Report" is a documented manager tool, so a real-time labor view exists. Shortfall: the claim is specifically labor cost expressed as a percentage of sales in real time during service, and no Lavu documentation states that the live labor report produces a labor-percent-of-sales figure. https://support.lavu.com/en/knowledge/lavu-pos · retrieved 2026-08-02 adversarially verified

labor-overtime-prevention differentiator

Workforce Settings enumerates the labor controls: Overtime Settings 'determine when overtime and/or double-time is paid' (pay calculation only - hours per day, days per week, hours per week), and the documented clock-in restrictions are schedule-window based ('Disallow user from clocking minutes before / after shift') and open-order based. The Overtime report is retrospective. No approaching-overtime warning or block at clock-in exists. https://support.lavu.com/en/knowledge/workforce-settings · retrieved 2026-08-05

labor-break-compliance-by-state differentiator

Workforce Settings' Employee Breaks section is the entirety of Lavu's documented break configuration and it is a flat tracker: "Set Length of Paid Break to 15 minutes using the dropdown. Set Allow paid breaks every (hours/minutes) to 4 hours by using the first dropdown" — one global break length and one frequency, with no state or jurisdiction dimension, no attestation prompt and no missed-break premium flag anywhere in the enumerated settings (employee classes, overtime thresholds, shift-change notifications, advanced settings, employee breaks). The article then delegates compliance to the operator outright: "Please refer to your local labor laws to understand how this feature should be used." A fully enumerated break feature offering a single global rule, plus the vendor's own instruction that the operator must apply local labor law themselves, is positive evidence that the jurisdiction-aware rules, attestation and premium-pay flagging the claim describes are absent. https://support.lavu.com/en/knowledge/workforce-settings · retrieved 2026-08-04

labor-minor-labor-rules

Re-checked 2026-08-08 across the full 250-article support.lavu.com dump. Workforce Settings states 'This page contains the following sections' and lists Employee Classes, Overtime Settings, Shift Change Notifications, Advanced Settings and Employee Breaks - no age, minor, school-day or prohibited-hours dimension. The Scheduling article walks the entire shift-creation flow (+ New Shift, employee, class, From/To times, copy to days, duplicate previous week, print, hide estimated pay) with no restriction or warning mechanic. POS - Clocking In and Out documents PIN/passcode entry only, and Auto Clock Out is a time-based cutoff, not a rules engine. Nothing in the corpus mentions minors. The only contrary evidence is the lavu.com SEO post 'How to Manage Restaurant Minor Labor Law Compliance' claiming 'Marty AI ... flags potential schedule violations before you publish' - grade D, advisory flagging rather than enforcement at scheduling and clock-in, and corroborated by no documentation. The marketing claim blocks a no; the absence of any documented mechanism blocks anything higher.

labor-tip-pooling-rules

Rules are configurable and computed by the system, not by spreadsheet. Tip pooling is enabled per employee class ("Use tip pooling in this employee class") and split either evenly among clocked-in class members or by "Hours worked"; the pool period is Shift (split at a configured "Shift change occurs" time), Daily, or Weekly with a configurable work-week start. Tip Out pushes a configurable percentage of tips or of sales from one class to other classes, with multiple recipient classes splitting the designated percentage and the calculation source selectable as total, cash-only or card-only tips, or total or super-group sales. Tip Withholding deducts a percentage of credit-card tips for processing cost. Points-based allocation is not offered; the claim lists percentage of sales, hours worked, points or role, and Lavu satisfies three of the four. https://support.lavu.com/en/knowledge/workforce-settings · retrieved 2026-08-02 adversarially verified

labor-tip-distribution-audit-trail

Per-employee tip records are documented and exportable — Time Card Reports track "tip and gratuity collection" with tips and gratuity carried in all five export options — and Workforce Settings documents the pool computation itself (pooling per employee class, split evenly or by hours worked over shift/daily/weekly periods; class-to-class tip outs by percentage; credit-card tip withholding). Shortfall: no documented report itemises, per shift and per employee, the amounts contributed to the pool versus distributed from it — Tip Engine V2 surfaces only a "Net Tips" figure on the server summary, so the pool-side ledger the claim requires is not documented. https://support.lavu.com/en/knowledge/time-card-reports · retrieved 2026-08-03

labor-qualified-tips-w2-reporting differentiator

Lavu Payroll is native and the Run Payroll flow does separate tip channels per employee: "Next to Paycheck Tips, enter the amount of tips that are paid to your employees directly on their paycheck ... Next to Cash Tips, enter the amount of tips your employee has received in cash. This includes any credit card tips the employee is cashed out at the end of each shift", with an instruction to account for gratuity and tip-outs/tip-pooling. Lavu also issues W-2s (Onboarding Your Employees into Lavu Payroll: information must be accurate 'so that there are no issues in receiving pay checks, or their W-2 in the first quarter of the new year'). SHORTFALLS, all three: (1) the split is a manual per-period entry field, not a machine-carried designation - it is cash-received vs paid-on-paycheck, not a 'qualified tip' classification; (2) no Treasury tipped-occupation code field appears anywhere in the payroll, employee-profile or Workforce Settings articles (Employee Classes carry only a name and FOH/BOH, which the doc says 'will have no affect on your employee profiles'); (3) the 250-article help centre contains no reference to W-2 Box 12 code TP or Box 14b, and no payroll-export field list. Retrieved from the 250-article support.lavu.com dump 2026-08-08. https://support.lavu.com/en/knowledge/how-to-run-payroll · retrieved 2026-08-08

labor-native-payroll differentiator

Lavu markets Payroll as its own product with payroll specialists and automated runs, and its blog describes EFTPS tax deposits and Forms 940/941. Shortfall: the claim requires Lavu itself to be the filing agent and to remit direct deposit; no first-party source states whether Lavu files and remits or white-labels a provider, there is no payroll article in the support knowledge base, and payroll is not a monitored status component. https://lavu.com/payroll/ · retrieved 2026-08-02 adversarially verified

labor-payroll-export-formats

QuickBooks (with payroll) and Restaurant365 workforce are named integrations; Gusto, ADP, Paychex and Paylocity are not listed. https://lavu.com/integrations/ · retrieved 2026-08-01

labor-shift-swap-workflow differentiator

Employees can self-service 'request shift coverages' through my.poslavu.com when using Lavu's scheduling platform, and Shift Change Notifications settings control whether and which managers (levels 2-3, or 2-4 on chained accounts) receive those emails. Shortfalls: no documented approval workflow - the mechanism is email notification - and no overtime or role-eligibility enforcement on the swap. https://support.lavu.com/en/knowledge/workforce-settings · retrieved 2026-08-05

labor-server-performance-metrics differentiator

Per-employee sales exist: the Cashier Sales report "will show you a breakdown of users who have closed orders, including card totals, cash sales, tips, gratuity, and more", exportable, and the printed Server Summary "reflects sales and transaction data conducted by the specific user". Void and discount attribution exist: the Voided Items report shows "the cashier associated with the order, which is likely the same person that voided the item", and the Discount report is filterable by "Order Server" or "Order Cashier" with a Check Discounts List "broken down by Order ID, Server, Cashier, Discount, and Total Amount". Shortfall: no report publishes an average check per server, an items or category attachment rate, or a void/comp rate as a rate rather than a list - the manager has to derive them from exports. https://support.lavu.com/en/knowledge/lavu-reports-cashier-sales · retrieved 2026-08-09 adversarially verified

inventory-recipe-bom-costing

Documented ingredient-level bill of materials per menu item: on the menu item there is a box labelled Ingredients where "you will be able to add your ingredients from the drop down menu, and designate how much of that ingredient is used in one serving of this menu item." Costing basis is operator-selectable in Inventory Settings between "Average Costing (Periodic)" and "FIFO (First In, First Out)", which "dictate how the Food and Beverage report tabulates cost of goods sold". https://support.lavu.com/en/knowledge/inventory-link-ingredients-to-menu-items · retrieved 2026-08-02

inventory-unit-conversion-yields

Named shortfall: units convert, yields do not. Inventory Settings ships default units of weight and volume ("Several units of weight and volume are created for your account by default") and supports operator-defined composite units — the doc's example is "Dozen, which contain 12 units". Each item carries distinct "Purchase/Sales Unit(s)", and the two alert types key off different units (low stock on Purchase Units, 86 count on Sales Units). What is absent from the documentation is any raw-to-prepared yield percentage, trim loss factor or cooked-weight conversion, so recipe cost is computed on as-purchased quantity. https://support.lavu.com/en/knowledge/inventory-settings · retrieved 2026-08-02

inventory-theoretical-vs-actual differentiator

A variance comparison exists and is documented: "To update your stock, simple type in the number under the Count column ... When you are finished, click the green reconcile button ... Once this is done, you can navigate to your inventory reports, and click on Variance to see your recently saved changes. This can help you track the variance of a particular item from week to week, or month to month." The counted figure is compared against system stock that is genuinely theoretical - ingredients are linked to menu items and 'the system can deduct from item stock with each sale' (Inventory Import and Export), receipts come in through Purchase Orders and out-of-PO Receive, and waste is decremented with reasons (Inventory Settings). Costing is present too: Inventory Settings offers Average (Periodic) or FIFO, which 'will dictate how the Food and Beverage report tabulates cost of goods sold'. SHORTFALLS: the Variance report is documented in a single sentence with no column list - nothing states that it presents theoretical usage and actual usage as separate figures, and nothing states the variance is expressed in currency as well as units. The Inventory Dashboard panel enumeration (Low Stock Level, Inventory Value, Pending Transfers, Waste Summary, Purchase Order Summary, Use First) contains no variance tile. Checked against the full 250-article support.lavu.com dump, 2026-08-08. https://support.lavu.com/en/knowledge/inventory-reconciliation · retrieved 2026-08-08

inventory-realtime-depletion differentiator

Depletion is automatic and on-sale, not batch: ingredients carry a per-serving quantity on the menu item, and "whenever the item is sold, stock automatically be deducted from your inventory". Shortfall: the claim requires depletion driven by modifier selections, and the article attaches ingredients only to menu items — modifiers are never named as an ingredient host, so add-ons under-deplete. https://support.lavu.com/en/knowledge/inventory-link-ingredients-to-menu-items · retrieved 2026-08-02 adversarially verified

inventory-86-auto-sync differentiator

All three channels documented. POS: setting "Track 86 countdown" to "Track by Inventory Item Level" means "when the inventory stock level is too low, the menu item it is attached to will grey out, and it will not be able to be added to any orders." Third-party: "If an item is out of stock on the POS, then the item will automatically be removed from the DoorDash storefront", explicitly "whether you are using Item Level 86 Tracking, or Lavu’s inventory platform with ingredients." Online ordering carries its own "Item 86 Count Tracking in Menu Drive" article. https://support.lavu.com/en/knowledge/lavu-menu-drive-and-door-dash · retrieved 2026-08-02 adversarially verified

inventory-count-modes

Named shortfall: adjustments yes, count sessions no. The Manage tab supports two documented stock adjustments — Waste Items (item, quantity and waste reason queued to a "Pending Item" list then saved) and Receive Items (item, cost per unit, quantity, unit of purchase) for stock arriving outside a purchase order — and ingredients can be bulk loaded by CSV import. No count sheet, blind count, cycle-count schedule or count-session variance posting is documented anywhere in the inventory articles. https://support.lavu.com/en/knowledge/inventory-manage-tab · retrieved 2026-08-02

inventory-mobile-count-offline

Re-checked 2026-08-08 against the full 250-article support.lavu.com dump. Every documented inventory entry point is the web Control Panel: Inventory: Reconciliation ('navigate to the Inventory page, and click on Reconciliation ... simply type in the number under the Count column'), Inventory Manage Tab, Inventory: Vendors receiving, and Inventory Import and Export (CSV). The Manage tab Action Menu enumerates Add / Archive / Copy / Waste / Receive / Import-Export - no count or stocktake action on a device. Lavu's Camera Scanner covers iPad barcode scanning but is scoped to the POS app and says the camera can scan barcodes 'to perform a number of actions', listing three (ring items up, accept Lavu Gift payment, accept Lavu Loyalty numbers) - non-exhaustive by its own wording, so it cannot carry an absence. Lavu Crash Kit 101, the corpus's only offline-behaviour article, lists order functions only and says nothing about inventory. No source states there is no offline mobile count, and none documents one. Unresolved.

inventory-vendor-catalogs-edi differentiator

Positive evidence of absence, re-read verbatim: "Lavu Inventory does not have the ability to contact your vendors. Lavu will not send emails or contact your vendors in any way." A vendor record needs only "the name and the email address of the vendor. All other information is optional" — no catalog, no price file, no transmission path. Receiving is manual quantity entry closing the order as "Closed" or "Partial". https://support.lavu.com/en/knowledge/inventory-vendors · retrieved 2026-08-02 adversarially verified

inventory-invoice-ocr differentiator

Positive evidence that manual line entry is the only path. Inventory: Vendors documents the entire vendor and purchasing flow: a vendor record requires only a name and email address, orders are built by 'selecting items you want to order, and how much you are ordering', and receiving is 'Type in the amount for each ingredient that you received and click Receive'. The article also states flatly that 'Lavu Inventory does not have the ability to contact your vendors. Lavu will not send emails or contact your vendors in any way', so no invoice reaches the system by email, and no photo or PDF ingestion appears anywhere in the Inventory category. Sourcery, Lavu's AP-automation brand still named in the Terms of Service and the privacy policy, has no remaining product surface - getsourcery.com 301s to lavu.com and 'sourcery' appears in zero of the 4,844 first-party sitemap URLs. https://support.lavu.com/en/knowledge/inventory-vendors · retrieved 2026-09-04 adversarially verified

inventory-price-change-alerts differentiator

Positive evidence of absence by enumeration: the alerts article describes exactly two alert types — "Low Stock Alerts" (purchase units, Control Panel dashboard) and "86 Count alerts" (sales units, surfaced on the POS, with "real time iPad notifications when selected menu items are low in stock"). No cost-variance, vendor-price-increase or other price-based alert appears in the enumerated set, and no email delivery is offered. https://support.lavu.com/en/knowledge/inventory-alerts-in-lavu · retrieved 2026-08-02 adversarially verified

inventory-par-auto-suggest differentiator

Threshold half is documented: item details expose 'Item Name, Primary Vendor, 86 Count, Low Stock Alert, Category, Location, BIN, Serial Number, SKU, and Purchase/Sales Unit(s)' (Inventory Manage Tab), Inventory Alerts in Lavu explains 'Low stock alerts are triggered once the current stock level, in terms of Purchase Units, is lower than the threshold marked for an ingredient', and the Inventory Dashboard's Low Stock Level tile is 'A running count of items that are at or below their Low Stock Alert value ... Clicking the Low Stock Level tile will direct you to a filtered view of the Manage tab, displaying only inventory items at risk of depletion.' SHORTFALLS: (1) no suggested order quantity - Inventory: Vendors walks the whole ordering flow and it is manual, 'select the vendor you want to order from to start. Then start selecting items you want to order, and how much you are ordering'; nothing pre-fills par minus on-hand; (2) no forecast-driven mode at all - the string 'forecast' occurs zero times in the 250-article support.lavu.com corpus; (3) the item-detail field list contains no par level as such, only the alert threshold. Retrieved 2026-08-08. https://support.lavu.com/en/knowledge/inventory-manage-tab · retrieved 2026-08-08

inventory-waste-logging

First-class waste workflow with reason codes: "Waste Reasons are the specific, predefined causes that indicate why part of an item's stock had to be discarded", preloaded with Damage, Spoilage and Mismade and extensible. Waste is entered from the Manage tab (item, quantity, reason, queued then saved) and rolls up on the Inventory Dashboard as the "total value of wasted inventory items for the current and previous day's business". https://support.lavu.com/en/knowledge/inventory-settings · retrieved 2026-08-02

inventory-shelf-life-expiry

Named shortfall: age-based, not date-based. The Use First Inventory panel tracks perishables by category and age, surfacing stock "that have been in inventory for Y days" so older stock is consumed first, and "Use First" is a named settings group. There is no per-lot expiry date field, no expiry alert and no automatic block on selling expired stock — the Manage tab item fields are Item Name, Primary Vendor, 86 Count, Low Stock Alert, Category, Location, BIN, Serial Number, SKU and Purchase/Sales Unit(s), with no expiry among them. https://support.lavu.com/en/knowledge/inventory-dashboard · retrieved 2026-08-02

inventory-bar-partial-bottle

Achieved via partners, not natively: Bar-i Liquid Accounting (weight-based liquid inventory) and Digital Pour (tap metrics) are listed integrations. https://lavu.com/integrations/ · retrieved 2026-08-01

inventory-cogs-gl-export

Named shortfall: COGS is computed, GL mapping is not documented. The operator selects a costing method — "Average Costing (Periodic)" or "FIFO (First In, First Out)" — which "dictate how the Food and Beverage report tabulates cost of goods sold", and Control Panel reports export to .txt, .xls and .csv. What no article documents is assigning inventory categories to general-ledger account codes, so posting to QuickBooks/Xero/Restaurant365 still depends on the third-party connector doing the mapping. https://support.lavu.com/en/knowledge/inventory-settings · retrieved 2026-08-02

inventory-native-not-partner differentiator

First-party inventory with first-party costing. Lavu Inventory Settings offers two selectable costing methods — "Average Costing (Periodic)" ("cost of goods sold will be calculated based on the average of all purchase costs/unit for a given item’s stock over the selected period") and "FIFO (First In, First Out)" — plus units of measure, storage locations, waste reasons and "Use First" perishable handling. The Inventory Dashboard reports Inventory Value, waste value for current and previous business day, and Expected Receivables. MarketMan, Restaurant365 and Bar-i extend this rather than supply it. https://support.lavu.com/en/knowledge/inventory-settings · retrieved 2026-08-02 adversarially verified

inventory-menu-margin-linkage differentiator

The recipe-cost-to-sales join is documented and real: after ingredients are attached to menu items and super groups are typed FOOD or LIQUOR, "whenever sales are made, the cost of creating that menu item from your ingredients will be calculated against the price of the menu item, to give you a cost percentage of either Food or Liquor depending on your settings", viewed under End of Day > Overview v2. Costing method is configurable (Average Periodic or FIFO) and 'will dictate how the Food and Beverage report tabulates cost of goods sold' (Inventory Settings). SHORTFALLS: (1) the output is a cost percentage aggregated to the FOOD/LIQUOR super-group type, not contribution margin per menu item - Lavu Reports - Sales by Item reports item sales but is not documented as carrying ingredient cost or margin; (2) no margin-threshold flag or alert of any kind is documented - the only inventory alerts are Low Stock and 86 Count, which are stock thresholds; (3) nothing re-evaluates margin after an ingredient cost change. Checked against the full 250-article support.lavu.com dump, 2026-08-08; the Marty 'profit leak identification' line on lavu.com is grade D and was not relied on. https://support.lavu.com/en/knowledge/tracking-food-liquor-costs · retrieved 2026-08-08

reporting-realtime-dashboard

Cloud reporting with mobile access is marketed, plus a Marty-generated "Morning Deposit" digest. Shortfall: the claim requires transactions reflected within minutes and access from both a browser and a mobile app off-premise; no Lavu source states a refresh interval, and no separate manager reporting app is published alongside the POS and KDS iOS clients. https://lavu.com/compare-lavu/ · retrieved 2026-08-02 adversarially verified

reporting-eod-closeout

Documented "Manager Functions - X and Z Report" plus "Management Tools - Shifts". https://support.lavu.com/en/knowledge/lavu-pos · retrieved 2026-08-01 adversarially verified

reporting-pmix-modifier-level

Item level: "The Sales by Item report will automatically break down your sales report by individual items sold ... Sales by item are broken down by item total, modifiers, subtotal, etc. It can also be broken down by individual cashiers", exportable to txt/xls/csv with bar and pie charts. Modifier level: a separate report exists - "Modifier Usage breaks down the activity of forced and optional modifiers. You can think of it like a sales report but for you modifiers ... Modifiers are broken down by quantity and cost ... Forced modifiers are displayed at the top of the report. Scroll down to see the Optional Modifier usage report." Daypart filtering is documented: 'A single day can also be filtered by the Start Time and End Time you would like to view. For example, you can view all sales on Tuesday that occurred from 1:00 p.m. to 5:00 p.m.' (Lavu Reports - Using Filters). SHORTFALLS: (1) modifier-level product mix lives in a separate report expressed as quantity and cost, not gross and net sales alongside the item; (2) neither article documents a revenue-center filter - Revenue Centers are described as letting you 'compare sales from different areas of your restaurant' between service layouts or tables, but no report page is documented as filterable by them; (3) no article states that Sales by Item distinguishes gross from net (post-discount) sales. Checked against the full 250-article support.lavu.com dump, 2026-08-08. https://support.lavu.com/en/knowledge/lavu-reports-sales-by-item · retrieved 2026-08-08

reporting-comps-voids-audit

Named shortfall: attribution yes, reason codes no. The Discount Report shows "which discounts were applied to orders, including when they were applied, who applied them, and how much was discounted", and the Action Log adds per-employee filtering across order open/close, drawer opens and refunds. No documented void/comp reason-code taxonomy, and no approver-vs-actor distinction. Upgraded from a marketing-page citation to first-party report documentation. https://support.lavu.com/en/knowledge/lavu-reports-the-action-log · retrieved 2026-08-02

reporting-cash-over-short

Documented "Management Tools - Cash Reconciliation", "Management Tools - Vault Management", "Register Functions - Paid In / Paid Out", "POS - Tilling In and Out". https://support.lavu.com/en/knowledge/lavu-pos · retrieved 2026-08-01 adversarially verified

reporting-labor-productivity

Labor is a reportable dimension alongside sales; sales-per-labor-hour and labor % by hour/department/employee are not documented. https://lavu.com/restaurant-pos/multi-location · retrieved 2026-08-01

reporting-server-scorecards differentiator

"Manager Handbook: Server Summaries" is a documented manager function. Shortfall: the claim requires per-server average check, items per check, attachment rate for named categories, and tips as a percentage of sales; the metric set is not enumerated in any retrievable Lavu source. https://support.lavu.com/en/knowledge/lavu-pos · retrieved 2026-08-02 adversarially verified

reporting-channel-profitability differentiator

Revenue slicing by channel exists: Revenue Centers compare sales across the service layouts (Quick Serve, Tables, Tabs) and even individual tables, Order Types (Dine In, Pickup, Carry Out, custom) tag every order for reports, and DoorDash/MenuDrive orders carry per-order financial detail into MD reports and the POS. Shortfalls: no margin reporting net of marketplace commission - DoorDash fees never appear in any Lavu report - and no consolidated per-channel profitability view. https://support.lavu.com/en/knowledge/revenue-centers · retrieved 2026-08-05

reporting-scheduled-delivery

Scheduled delivery exists, but only in MenuDrive: "Automated reports are a way you can have Menu Drive reports sent directly to your email ... Start by logging into your Admin Control Panel, click on Reports, and then click on Report Settings. The first section allows you to determine who will receive this report. Simply add their email addresses to the list. You can add as many people as you want ... Next you will need to create your 'close of business day rules'. This determines when your report will be sent ... Select the day of the week, and the time you wish the report to be sent. You can set as many of these as you want." SHORTFALLS: (1) the claim asks for ANY report to be schedulable - this is a single fixed report, self-described as 'a very high level report, detailing your sales, payments, discounts redeemed, what was collected in tips, and more'; (2) it covers MenuDrive online ordering only, not the Lavu POS Control Panel, whose reporting is documented as pull-only ('All four categories can be exported to a .txt file, a .xls file, and a .csv file' after setting a date range); (3) no shared destination (SFTP/drive) is offered, email only; (4) the cadence is quirky - 'the report will include information since the last time the report was sent'. Checked against the full 250-article support.lavu.com dump, 2026-08-08. https://support.lavu.com/en/knowledge/how-to-set-up-automated-reports-in-menudrive · retrieved 2026-08-08

reporting-public-api differentiator

Confirmed independently: api.lavu.com presents only an API-portal shell with Swagger (JSON/YAML) and ReDoc links plus a Login link; no auth model, no rate limits, no sandbox, no endpoint reference without credentials. Lavu's integrations page does add a first-party marketing hook — "Need something different? Try our open API!" — and the multi-location page repeats "Open API", but neither yields a public reference. Partner-gated is the right read. https://api.lavu.com/ · retrieved 2026-08-01 adversarially verified

reporting-webhooks differentiator

Downgraded from `no` on 2026-08-08. Two defects, the first the researcher flagged themselves. api.lavu.com/docs/swagger.json is Swagger 2.0, a format with no webhooks or callbacks construct at all, so the absence of event delivery, retry semantics and payload signing from it is a format artifact rather than a documented negative. Second, that spec is not Lavu's complete published API surface: Lavu sells 'open API' access as a priced add-on and its long-standing integration endpoint is the legacy POST interface documented at admin.poslavu.com/cp/areas/api_doc.html, a page headed 'Confidential: POSLavu API Documentation' - a partner-gated document is by definition not an enumeration a verifier can read to the end. The remaining support is a zero-hit grep for 'webhook' over a 250-article help centre that omits whole Lavu components. The absence of a callback-registration path among the 26 public paths is suggestive but does not meet the positive-evidence bar. Undetermined. adversarially verified

reporting-api-not-upcharged differentiator

The purchase gateway prices every add-on module individually (Kitchen Display $29, Payroll $39, Reservations $19, Marketing $25, Inventory $29, Gift Cards $15, Loyalty $19, Customer Display $12, Employee Scheduling $22) and lists no API or data-access SKU; the plan catalogue at buy.lavu.com/api/plans lists none either; the Terms of Service fee section names subscription fees, the MenuDrive revenue share and LavuCare only; report export to txt/xls/csv is documented with no fee; and lavu.com/restaurant-pos/multi-location markets 'Open API for integrations' as a standard feature. Shortfall: API credentials are issued rather than self-served (api_posture: partner-gated), no page states that API access is included in Starter or Growth, and the Enterprise feature list is expressly open-ended ('include, but are not limited to'). https://buy.lavu.com/api/addons · retrieved 2026-09-02 adversarially verified

reporting-tier-paywall differentiator

Lavu's self-serve purchase gateway publishes three plans: Starter $0/mo and Growth $79/mo each list only 'Core POS' (plus one terminal or custom hardware, 24/7 support, 'Add-ons available'), while 'Advanced Analytics' and 'AI Reporting' appear only under the quote-only Enterprise plan ('You select the features that fit your needs'). The Control Panel reports the help centre documents - Summary, Sales by Item, Modifier Usage, Voided Orders/Items, Discounts, Overtime, Live Labor Report - carry no tier notice, so labor-vs-sales, PMIX and comps/voids appear to sit on the base product. Shortfall: multi-location comparison needs the Multi Location Menu Management / Enterprise Management extension, 'Advanced Analytics' is Enterprise-only, and Lavu publishes no feature-by-tier matrix saying where 'Core POS' reporting ends. https://buy.lavu.com/api/plans · retrieved 2026-09-02 adversarially verified

reporting-history-retention differentiator

Positive evidence of absence in the contract, twice over. No retention window of any length is published for the reporting UI, and the Terms of Service reserve the opposite right: Lavu may 'suspend or terminate your User Account, revoke your Software License ... and delete all data associated with your User Account without prior notice if there has been no Account Activity in your User Account for a period of 180 days', where Account Activity is itself defined on a rolling 30-day basis (payments, orders or clock punches recorded in the last 30 days). The Lavu Terms and Conditions add that on termination 'Lavu has no obligation to retain, provide access to, or allow extraction of User Content or User Data' and 'may delete all User Content and User Data immediately'. A 24-month queryable window is therefore not merely unpublished but contractually disclaimed. https://www.menudrive.com/terms/ · retrieved 2026-09-04 adversarially verified

reporting-anomaly-alerts differentiator

Marty 'surfaces margin leaks, labor inefficiencies, and revenue trends' and flags underperforming sites 'before month-end reports'; operator-configurable thresholds are not documented. https://lavu.com/restaurant-pos/multi-location · retrieved 2026-08-01

reporting-nl-query

Lavu ships 'MARTY - AI Companion' (seller Lavu Inc, v1.0.21, June 2026) on the App Store, described as 'an AI-enhanced analytics companion... going beyond manual reporting to predict trends', with release notes that reference 'the chat feature'; Lavu's own February-2026 feature comparison (lavu.com/2026-restaurant-pos-ai-capabilities-report/) scores Marty 'Chat AI (natural language Q&A): Yes', and its site-wide Marty FAQ invites operators to 'Hit us on Marty Chat'. Shortfall: Marty is sold only under the quote-only Enterprise plan ('AI Reporting' on buy.lavu.com/api/plans); no documentation shows a question against the operator's own sales or labor data returning a figure or chart; Lavu's comparison marks 'In-chat task execution: No' and describes Marty's core output as an overnight push briefing rather than answers to ad-hoc questions; and 'Marty' appears nowhere in the 250-article help centre. https://apps.apple.com/us/app/marty-ai-companion/id6752260419 · retrieved 2026-09-02 adversarially verified

reporting-guest-cohorts differentiator

Guest-level analytics are documented for online-ordering customers: the Registered Customers report shows 'how many times they have placed orders, the average bill, the total amount they have spent, and the date of their last order' (Guest Customers mirrors it for unregistered guests), and POS Customer Management keeps per-customer order history. Shortfalls: no new-vs-returning counts, no lifetime-spend cohort groupings, and coverage is limited to MenuDrive/Customer Management records rather than all guests. https://support.lavu.com/en/knowledge/menu-drive-all-reports · retrieved 2026-08-05

reporting-sales-forecast differentiator

Lavu's Marty AI marketing states 'Marty analyzes your restaurant's historical sales data. It considers seasonal trends and local events. This intelligence predicts future demand', that morning briefings 'outline predicted sales for the day', and - in the FAQ block Lavu repeats site-wide - 'Marty forecasts sales. Lavu generates the schedule with labor control'; the Marty companion app shipped on the App Store in June 2026 (Lavu Inc, v1.0.21). Shortfall: the forecast is described only at whole-day granularity inside a briefing, not at daypart or hourly resolution in a reporting UI; consumption by scheduling is asserted in marketing, not documented; Marty is available only on the quote-only Enterprise plan; and 'forecast' occurs zero times in the 250-article help centre. https://lavu.com/marty-ai-scheduling-recommendations/ · retrieved 2026-09-02 adversarially verified

reporting-tip-tax-compliance

Declared and charged tips are both captured per employee: Advanced Location Settings - Reports documents a prompt "to have servers enter cash tips before printing their Server Summary" plus a "Server Cash Tips Record Mode" dropdown and tip-out entry prompts; the End of Day - Tips & CC Batching page shows editable per-server "Card Tips" and "Cash Tips" columns reviewable until batch settlement; and Time Card Reports carry tips and gratuity in all five export options, two of them formatted to "make it easier to upload into your payroll software". Shortfalls: no documented report itemises tip-pool contribution versus distribution per employee — Tip Engine V2 surfaces only "Net Tips" on the server summary even though Workforce Settings computes pools and tip-outs — and no tax liability summary by jurisdiction is documented anywhere in the reporting suite. https://support.lavu.com/en/knowledge/advanced-location-settings-reports · retrieved 2026-08-04

multi-location-org-hierarchy

Named shortfall: two levels, no region or brand tier. MLMM runs on an "umbrella configuration" in which "one or more primary locations can be configured for a chain of locations. The menu can be managed from a primary to non-primary locations." Access level 4 lets a multi-location owner switch locations without re-login. There is no documented region, district, group or brand object between the umbrella and the location, so policy and reporting roll-ups above the location level are limited to the whole set. https://support.lavu.com/en/knowledge/multi-location-menu-management · retrieved 2026-08-02

multi-location-central-menu-publish

Multi-Location Menu Management publishes from a primary location: "Menu can be updated quickly and managed to multiple locations in a single action." Two documented modes — a full sync that replaces the target menu, and an incremental sync where "changes are updated in the target location without altering any items that were added specifically to the target location(s) beforehand. This means you can have location-specific items." https://support.lavu.com/en/knowledge/multi-location-menu-management · retrieved 2026-08-02

multi-location-price-zones

Named shortfall: propagation from a primary, not a named zone object. MLMM offers a bulk price update that can "update the prices of your menu items, modifiers, or both simultaneously" at the primary location and then sync that to selected targets, and incremental sync preserves location-specific overrides. But there is no price-zone or price-band entity to which a set of locations is assigned; grouping is expressed only as which targets an operator picks for a given sync. https://support.lavu.com/en/knowledge/multi-location-menu-management · retrieved 2026-08-02

multi-location-consolidated-reporting

"Per-location and consolidated reporting... roll it up into a group view" covering sales, labor, voids and comps. Shortfall: the claim also requires store-vs-store ranking and variance flags, neither of which is documented; evidence remains a vendor marketing page with no supporting help-centre article for an above-store reporting view. https://lavu.com/restaurant-pos/multi-location · retrieved 2026-08-02 adversarially verified

multi-location-cross-location-giftcard

Re-checked 2026-08-08 against the full 250-article support.lavu.com dump. The Lavu Gift set (Selling & Redeeming, Creating the Payment Method, Adding Gift Card Items, Importing 3rd Party Gift Cards, Digital Gift Cards) documents issue/reload/check-balance/deactivate and redemption by swipe, manual entry or camera barcode scan, always against 'your account'; Manage Lavu Gift and Loyalty Card Balance and Expiration Date manages balances per card from the Control Panel or POS. None of them says whether a card issued at one chained location can be redeemed at another. The chain-level articles do not close it either: Multi Location Menu Management syncs menu items, pricing, specials, taxes and discounts from a primary location and never mentions gift ledgers, and Cross-Country Reporting - the chain reporting feature - converts sales and payment data into a base currency but documents no gift-liability figure. Advanced Location Settings - Reports offers only a 'Gift Revenue Tracked' When Sold / When Redeemed switch, which is a single-location revenue-recognition setting, not inter-store settlement. Nothing states the answer in either direction. Unresolved.

multi-location-cross-location-loyalty

Re-checked 2026-08-08 against the full 250-article support.lavu.com dump. On the POS side loyalty is card-based: Assigning Loyalty Points to Menu Items, Awarding Loyalty Points and Redeeming Loyalty Discounts and Creating Lavu Loyalty Discounts all operate on a physical or digital card number within an account, and Manage Lavu Gift and Loyalty Card Balance manages that balance per card. Customer Management documents customer profiles inside a location's Control Panel. On the online side MenuDrive marketing/loyalty runs per storefront account. Multi Location Menu Management enumerates what it propagates - menu items, pricing, specials, taxes, discounts, other settings - and customer or loyalty data is not among them; Cross-Country Reporting consolidates sales and payment data only. So nothing documents a shared chain-wide loyalty profile, balance and order history, and equally nothing documents that balances are location-bound. Unresolved.

multi-location-multi-brand differentiator

Re-checked 2026-08-08 against the full 250-article support.lavu.com dump. Multi Location Menu Management is a single-brand umbrella by design: 'One or more primary locations can be configured for a chain of locations ... The primary location's menu will need to be synced fully to other locations in the chain, replacing the chained location's menu with the primary location's menu.' The same-terminal segmentation that does exist is partial at best - Revenue Centers 'allow to compare sales from different areas of your restaurant ... between the different service layouts in Lavu (Quick Serve, Tables, and Tabs) or even between individual tables', which gives separately reportable revenue on one terminal but not separate menus; Order Types and Super Groups likewise slice one menu rather than hosting two. Receipt branding is documented as one logo per location (Adding a Logo to your Receipts, Lavu Onboarding - Add a Logo to Your Receipts) with no per-brand variant. No article addresses running two distinct or virtual brands on the same hardware and drawer, so the combination the claim asks for is neither documented nor documented as impossible. Unresolved.

multi-location-multi-tax-jurisdiction

Explicitly designed for it: "If you have multiple business locations in different regions or states with varying tax structures, Tax Configuration will allow you to maintain those differences while also syncing your menu over time. It also allows you to keep taxes from changing with each sync." Underneath, each location builds tax profiles under Payments > Tax Profiles carrying one or more named rates (entered as decimals, e.g. 0.085 for 8.5%) attached to menu categories and items, with an option to include tax in displayed prices. Lavu is explicit that it "cannot tell you or assist in determining what you should be charging for taxes" — rate determination is the operator's. https://support.lavu.com/en/knowledge/multi-location-menu-management · retrieved 2026-08-02

multi-location-central-labor-policy

Per-location labor rules are configurable and partly terminal-enforced: overtime/double-time thresholds (hours per day, days per week, hours per week, or combinations), paid-break settings, and clock restrictions ('Prevent servers from clocking out when they have open orders', early/late clock-in blocks). Shortfalls: no location-group central management - MLMM syncs menus, taxes, discounts, payment types, and happy hours, not workforce settings - and no predictive-scheduling compliance features. https://support.lavu.com/en/knowledge/workforce-settings · retrieved 2026-08-05

hardware-commodity-devices differentiator

Retrieved on verification: "Lavu POS" is published free on the App Store by "Lavu Inc" with stated compatibility "Requires iPadOS 13.0 or later" (iOS 13.0+ on iPhone, macOS 11.0+ on Apple silicon). Any operator-purchased iPad meeting that floor runs the client; there is no vendor-imaged or proprietary terminal gate. Scope caveat: commodity within the Apple ecosystem only — Lavu publishes no Android or Windows POS client. https://apps.apple.com/us/app/lavu-pos/id1449885676 · retrieved 2026-08-02 adversarially verified

hardware-os-platforms

iPad / iOS is named as the client platform; minimum iPadOS version and device specs are not published on the public site. https://lavu.com/restaurant-pos/ · retrieved 2026-08-01

hardware-handheld-purpose-built

Positive enumeration, twice over. The KB's Equipment and Hardware category lists every supported device by group, and its entire Card Readers group is separate readers driven from a tablet: IDTech VP3300, LANE 3000, Adyen NYC1, BOLT EMV, Verifone, PAX. Lavu's own store (46 priced SKUs) sells its handheld as a bundle, not a device: the Wi-Fi Handheld Bundle is "1 x Apple iPad mini (A17 Pro) ... 1 x VAULT GoWork Pro case ... 1 x Adyen NYC1 Card Reader". No integrated-reader handheld appears in either list, and no drop rating or IP ingress rating is published for anything - the case is described only as "rugged" with "drop protection". https://support.lavu.com/en/knowledge/lavu-equipment-hardware · retrieved 2026-08-09 adversarially verified

hardware-handheld-battery-swap differentiator

Lavu's order-taking hardware is standard Apple iOS devices - the product is an iPad POS and the settings expose order pads for 'iPad' and 'iPhone/iPod' - with sealed, non-swappable batteries; Lavu publishes no rated shift battery life anywhere on lavu.com or in the help centre, and no vendor battery-swap program exists. https://support.lavu.com/en/knowledge/advanced-location-settings-order-options · retrieved 2026-08-05

hardware-handheld-lte

A vendor-sold failover modem provides 'a 5G LTE connection to the internet for your restaurant', is 'compatible with the networking equipment that we sell', activates automatically on ISP outage and reroutes iPad traffic transparently with 'no acknowledgments nor limitations on your software'. Shortfalls: it is a store-network WAN failover, not handheld-level cellular - nothing documents LTE in the handheld devices themselves or a fallback that survives loss of the local Wi-Fi network (as opposed to the ISP). https://support.lavu.com/en/knowledge/lavu-crash-kit-101 · retrieved 2026-08-05

hardware-offline-mode

Orders, kitchen sends and cash sales continue offline per Crash Kit 101. Shortfall: the claim requires the vendor to document explicitly which functions degrade. Only card and gift-card validation is named as internet-dependent; loyalty lookup and refunds are addressed nowhere, and the marketing offline page contradicts the support article by claiming payments work locally. https://support.lavu.com/en/knowledge/lavu-crash-kit-101 · retrieved 2026-08-02 adversarially verified

hardware-kds

First-party KDS with documented station routing: create a printer profile with the kitchen label per screen, then "assign your menu categories to your new KDS printer profile. That way when your employees click Send on an order, the order will be sent to your Lavu KDS screen." Touch input and order timers are documented in the KDS settings article, and Lavu sells Epson KDS station bundles under its own brand, so this is first-party rather than integration-only. Course/fire timing beyond elapsed-time timers remains thin. https://support.lavu.com/en/knowledge/lavu-kds-printer-profile · retrieved 2026-08-02 adversarially verified

hardware-kiosk differentiator

Kiosk is a documented first-party product (three help-centre articles, monitored status component). Shortfall: the claim requires both countertop and freestanding form factors and documented ADA compliance; Lavu publishes neither a kiosk form-factor list nor any accessibility conformance statement. https://support.lavu.com/en/knowledge/lavu-pos · retrieved 2026-08-02 adversarially verified

hardware-drive-thru

Positive absence across two independent first-party enumerations of the same proposition. The help centre's Equipment & Hardware category declares its own complete subsection list - Networking, Printers & Cash Drawers, Card Readers, Other, Epson KDS - and every article beneath it is a printer, cash drawer, router, access point, card reader or KDS screen. Lavu's own store is separately enumerable through its Shopify collection JSON and holds forty products across twelve collections (card readers, terminals, KDS, cash drawer, networking, printers, stands, iPad, gift cards, discounted, plus paper and accessories); neither list contains an outdoor menu board, an order confirmation display, a speaker post or a headset system, and no timer or speed-of-service measurement is documented for a lane. https://support.lavu.com/en/knowledge/lavu-equipment-hardware · retrieved 2026-09-04 adversarially verified

hardware-printer-compatibility

Help-centre article 'Compatible Star Micronics Printers', subtitled 'Model of Star Printers that Lavu supports': "Lavu is compatible with 2 series of Star Micronics printers. The TSP 650 series (currently the TSP 654) [and] The SP700 series (currently the SP742) ... The TSP 650 printers are thermal printers, and are best used as receipt printers in your front of house. Meanwhile, the SP 700 printers are impact printers, and work great in the kitchen." A second manufacturer is documented at equal depth under Lavu Equipment & Hardware > Printers & Cash Drawers: Installation - Epson TM-T88VII Printer, Setting a Static IP Address to the Epson TM-m30iii Thermal Receipt Printer, Set a Static IP address for your Epson Printer, Epson Wireless Printer Setup (and the TM Utility variant), Basic Printer Setup, Printer Redirects and Epson Printer Error Light Codes. The static-IP articles are the LAN/Ethernet path, and Printer Redirects plus Assigning Printers To Modifiers document kitchen routing. Both are standard third-party ESC/POS thermal and impact units, not vendor-locked hardware. Retrieved from the 250-article support.lavu.com dump, 2026-08-08. https://support.lavu.com/en/knowledge/compatible-star-micronics-printers · retrieved 2026-08-08

hardware-peripherals

Every element of the peripheral set is documented in the help centre. Multi-drawer per terminal: 'Dual Cash Drawer Setup' - "with a dual cash drawer setup, you can connect a single receipt printer/POS to two cash drawers ... the additional piece of hardware you will need is Lavu's Dual Cash Drawer Splitter ... allows Lavu to open specific cash drawers based on the employee that is logged in", with the matching Advanced Location Settings > Checkout Options and per-printer-profile toggles; plus 'APG Cash Drawer: Setup and Usage Guide'. Scales: 'Using the Tor Rey L-EQ Bluetooth Scale' - "Lavu sells a Bluetooth connect scale to assist customers in determining prices for weighed menu items", configured from Advanced Location Settings. Customer display: 'Lavu Customer Facing Display' - "displays items, taxes, and check totals to the restaurant patron and can capture signatures for credit card transactions ... an additional iPad connected to your network with the Lavu Display App installed." Barcode scanning: "The Lavu POS is able to use the iPad's built in camera to scan bar codes" to ring items up, take Lavu Gift payment and read loyalty numbers (Lavu's Camera Scanner). SHORTFALLS: (1) no published compatibility list except for printers - 'Compatible Star Micronics Printers' is the only supported-models article in the corpus; drawers, scales and displays are documented as single named units (APG, Tor Rey L-EQ, Lavu Display App on iPad) with no statement of what else works; (2) barcode input is documented via the iPad camera only, with no supported USB/Bluetooth scanner list; (3) lavu.com/hardware/ redirects to the homepage, so no first-party catalogue exists. Retrieved 2026-08-08. https://support.lavu.com/en/knowledge/lavu-equipment-hardware · retrieved 2026-08-08

hardware-p2pe-terminal

Encrypting card entry is documented and hardware-based - "the basics of PCI compliance include using properly encrypted card readers", and "the card readers you purchase through Lavu, as well as the Lavu POS software, are all PCI compliant" - on PTS-listed devices (IDTech VP3300, Ingenico LANE 3000, Adyen NYC1). The shortfall is explicit rather than merely undocumented: Lavu's own guide to the CardPointe PCI form instructs merchants to answer "Q: Your Point-to-point Encryption system? A: No", and walks them through a full guided assessment (payment application, remote access, information security policy). No validated P2PE listing is cited and no resulting SAQ type is ever named. https://support.lavu.com/en/knowledge/cardpointe-pci-compliance · retrieved 2026-08-09 adversarially verified

hardware-tap-to-phone differentiator

Re-checked 2026-08-08 against the full 250-article support.lavu.com dump. 'Tap to Pay' occurs exactly four times and every occurrence attaches the capability to a separate reader, not to the tablet: 'Pairing your VP3300 with Lavu Kiosk' lists the VP3300's transaction types as 'Traditional card swipes / EMV chip inserts / Tap to Pay (Apple Pay, Google Wallet, etc.) / Lavu Gift Cards'; the VP3300 connection and indicator-light articles repeat it ('bluetooth device that can accept card payments through card swipes, insert (EMV), or tap to pay'); and the LANE 3000 troubleshooting article says the same of Ingenico's terminal. The corpus documents six readers in total (VP3300, LANE 3000, NYC1, PAX, Verifone, iDynamo) and every payment path runs through one of them. Neither 'Tap to Pay on iPhone' nor 'Tap to Pay on Android' appears anywhere in the help centre, and lavu.com/contactless-payments-ordering/ and lavu.com/payment-processing/ do not mention either. Lavu publishes no supported-payment-methods list that asserts its own completeness, so the uniform reader-scoping is strong but not a positive statement of absence. Unresolved.

hardware-pricing-transparency differentiator

Lavu publishes 46 hardware SKUs with public prices, no login and no quote request: Adyen NYC1 Card Reader $119 (SKU ADYEN-NYC1), NYC1 Dock $125, APG Cash Drawer 16in $120, Epson receipt printer $275, Epson TM-L90II label printer $440, Epson TrueOrder KDS $1,128, iPad mini (A17 Pro) Wi-Fi $499 / Wi-Fi+Cellular $749, iPad Air 13in $799, VAULT GoWork Pro case $240, Wi-Fi Handheld Bundle $1,270 (BUNDLE-MOBILE-IPADMINI), Cellular Handheld $1,350, Complete POS Station Bundle iPad Air 13in $2,374, networking bundles $1,800 / $3,348 / $4,140. The same catalogue is served as JSON from buy.lavu.com/api/hardware with per-SKU price, category and finance fields. https://shop.lavu.com/ · retrieved 2026-08-09 adversarially verified

hardware-ownership-vs-lease differentiator

The Terms of Service state both models explicitly: 'Lavu Products may be purchased or leased as indicated in your order'; 'Title for Lavu Products purchased from us passes to the purchaser at the time of delivery by Lavu to the freight carrier', while leased or financed products 'shall at all times remain the property of Lavu or our Financing Partner' and must be returned when the lease expires. https://lavu.com/terms-of-service/ · retrieved 2026-08-05

hardware-usable-after-churn differentiator

Lavu's own comparison page states 'It is flexible and not hardware locked. You are not forced into proprietary hardware. You can buy replacements anywhere.' The terminal is a customer-owned iPad running App Store apps (Lavu POS, apps.apple.com/us/app/lavu-pos/id1449885676), and shop.lavu.com sells commodity Epson, Star, APG and Apple hardware that the vendor has no means to brick. Shortfall: the statement is marketing and does not address post-cancellation specifically; the card readers Lavu sells (Adyen NYC1, IDTech VP3300, Ingenico LANE 3000) are documented only as paired to Lavu Pay / CardConnect gateways and their re-use with another processor is not addressed anywhere. https://lavu.com/restaurant-pos/multi-location/ · retrieved 2026-09-02 adversarially verified

hardware-rma-sla differentiator

A replacement SLA is published: LavuCare ('included by default on all Lavu deals for $199 per year') offers 'overnight hardware replacement in the event of equipment defect or failure', and the subscribable NDR Service processes weekday replacement orders received before 5PM ET for same-business-day shipment and next-business-day delivery. Shortfall: no hardware warranty term is published - the ToS references an 'original warranty period' without stating its length. https://lavu.com/terms-of-service/ · retrieved 2026-08-05

hardware-byod

The POS app installs from the public App Store onto customer-supplied iOS hardware ('the availability of the Lavu Products is dependent on the App Store from which you received the license'; you must provide 'compatible mobile devices'), and the settings expose iPhone/iPod order pads alongside iPads. Shortfalls: no documented BYOD program or permission/security model for staff personal phones - the only device-security requirement stated is that illegally altered (jailbroken) devices are prohibited. https://lavu.com/terms-of-service/ · retrieved 2026-08-05

hardware-remote-device-management differentiator

Positive evidence of the opposite operating model. Lavu documents version handling as a manual per-device chore performed by the operator on each iPad - 'Tap the menu button ... Tap Settings ... Tap About Lavu POS. The app version will be listed at the top' and 'To get the latest version of the app, simply search for Lavu in the Apple App Store, and tap the Update button' - with the consistency burden also on the operator ('if you are using multiple iPads, that they all have the same version of Lavu installed'). That forecloses both fleet version visibility and staged rollout. Device health is likewise per-device and physical: Basic Network Troubleshooting diagnoses terminals, printers and readers by reading router port lights and access-point LEDs rather than a console. The only remote-access capability Lavu documents belongs to Lavu rather than the merchant - the Terms and Conditions reserve tooling 'to allow remote access to the devices or computers' for Lavu's own technical support. https://support.lavu.com/en/knowledge/lavu-app-version · retrieved 2026-09-04 adversarially verified

hardware-selfpour-scales

Named partners exist and nothing beyond the name does. Lavu's own integrations catalogue lists Digital Pour (self-pour and draft-beverage monitoring) and Bar-i (weight-based liquid accounting) as supported integrations, which is more than an absence. Shortfall: the integration is asserted only as a catalogue tile at grade C - the complete 249-article help centre carries no setup or configuration article for either partner, nothing documents that a pour posts automatically to an open POS tab rather than feeding a back-office variance report, and Lavu's own forty-SKU store sells no flow meter, pour spout or tap-wall hardware. The one beverage-adjacent device Lavu documents is a Tor Rey L-EQ Bluetooth scale for pricing weighed items at the POS. https://lavu.com/integrations/ · retrieved 2026-09-04 adversarially verified

hardware-callerid-integration

Re-checked 2026-08-08 against the full 250-article support.lavu.com dump: 'caller id', 'caller-id', 'telephony' and 'incoming call' each occur zero times. The nearest documented surface is manual: orders carry togo_phone/togo_time fields (visible in the legacy API table dump at admin.poslavu.com/cp/areas/api_doc.html, retrieved 2026-08-08) and Customer Management stores customer records that are looked up by the operator, not popped by an inbound call. A 'Phone System' component is listed on status.lavu.com, but a status-page component name is not documentation of a POS caller-ID pop and may equally refer to Lavu's own support telephony. No compatibility list or integration article addresses telephony hardware in either direction. Unresolved.

extensibility-public-api-docs

Re-probed 2026-08-06 with unauthenticated curl: /docs/swagger.json returns the complete Swagger 2.0 spec (72KB, 26 paths, 40 definitions, securityDefinitions), /docs/swagger.yaml returns the same 84KB in YAML, and /docs/swagger/ and /docs/redoc/ both render. No signed agreement, NDA or sales call intervenes. The earlier 'requires login' reading confused endpoint auth with doc access: the spec's own text says 'LavuAPI is completely protected and requires authentication to access any of the endpoints', and /api/v1/customer/menus/ does return 401, but the reference itself is open. Caveats short of a shortfall: the spec self-describes as 'under completion' and one link still points at http://127.0.0.1:8000/docs/swagger.yaml. https://api.lavu.com/docs/swagger.json · retrieved 2026-08-06

extensibility-api-access-cost differentiator

No API line appears anywhere in Lavu's published price list: the plan catalogue (Starter $0, Growth $79, Enterprise quote-only) and the nine-module add-on catalogue at buy.lavu.com/api/addons price everything Lavu sells a la carte and contain no API, integration or data-access fee; the Terms of Service fee clauses never mention the API; and 'Open API for integrations' is marketed as a standard feature on lavu.com/restaurant-pos/multi-location. Shortfall: access is partner-gated with issued credentials, and no source says in words that API access is included at the base tier, so a fee or plan requirement applied inside the credential process cannot be excluded. https://buy.lavu.com/api/plans · retrieved 2026-09-02 adversarially verified

extensibility-free-sandbox differentiator

The API portal's own documentation states 'LavuAPI is completely protected and requires authentication to access any of the endpoints, including the documentation', with OAuth authorization granted by an existing customer account ('the user should authorize the OAuth application explicitly'). No sandbox, test environment, seeded data, or open developer signup exists anywhere in the API documentation. https://api.lavu.com/docs/swagger.json · retrieved 2026-08-05

extensibility-oauth-partner-apps

The publicly retrievable OpenAPI spec at api.lavu.com documents an OAuth 2 flow for third-party apps: "To work with LavuAPI.Customer, the user should authorize the OAuth application explicitly", with /oauth/authorize/, /oauth/token/ and /oauth/revoke-token/ endpoints and per-endpoint scopes — "Each endpoint has a unique scope to access and consume it" (e.g. customer_profile on the profile endpoint). Operator-granted, scoped and revocable are all present. Caveat: the spec's formal securityDefinitions also declare HTTP Basic, and the info text lists session login as an alternative scheme, so OAuth is available rather than enforced. https://api.lavu.com/docs/swagger.json · retrieved 2026-08-03

extensibility-webhooks-push

The complete published OpenAPI spec for api.lavu.com enumerates 26 endpoint paths — token, profile, location, menus, orders, checks, payments, payment intents — and contains no webhook, event-subscription, callback or notification endpoint in any path or description; order lifecycle data is exposed only through pollable GET /v1/customer/orders/ and /v2/customer/orders/ resources. No support-centre article mentions webhooks either. The vendor's enumerated integration surface is pull-only, which is positive evidence that push webhooks are not offered. https://api.lavu.com/docs/swagger.json · retrieved 2026-08-03

extensibility-webhook-reliability differentiator

No webhooks exist in either published API surface: the OpenAPI spec's 26 paths are all request/response (reads plus order/payment creation), and the legacy admin.poslavu.com API is a poll-only table query interface. Nothing documents event delivery, signing, retries, or a replayable event log, so the claim's documented-reliability requirements cannot be met. https://api.lavu.com/docs/swagger.json · retrieved 2026-08-05

extensibility-order-injection-api

Order injection is documented in both API generations. The published OpenAPI spec exposes POST /v2/customer/create-order/, whose LavuApiOrderSerializer body requires customer, items[] (item_id, quantity), location_id, tablename/tabname and order_status and optionally carries subtotal, tax, total, server and special_instructions, with POST /v2/customer/close-order/, POST /v2/create-payment-record/ and external-payment/payment-intent routes completing the lifecycle. The legacy doc at admin.poslavu.com/cp/areas/api_doc.html demonstrates the same thing on the old stack: 'cmd=insert&table=orders', then 'cmd=insert&table=order_contents' (item name, price, quantity, modifiers), then 'cmd=insert&table=order_payments', authenticated by dataname/key/token and returning '<result><id>id of the new entry</id><order_id>the order id</order_id></result>'. Caveat, scored elsewhere: access is gated to an authorized customer account and there is no open sandbox or developer signup. https://api.lavu.com/docs/swagger.json · retrieved 2026-08-06

extensibility-menu-write-api differentiator

Both published API surfaces were read, and the audit changed what this note says. The modern contract is read-only for menus: the Swagger 2.0 spec (72,254 bytes, retrieved unauthenticated) declares 26 paths of which the menu resources are GET /api/v1/customer/menus/ and GET /api/v1/customer/menus/{id}/, and every write path is accounted for elsewhere (three token routes, create-order, close-order, create-payment-record, external-payment, payment-intent). The legacy POSLavu API at admin.poslavu.com/cp/areas/api_doc.html is NOT read-only as an earlier reading had it - its worked PHP example posts 'cmd=insert&table=orders', 'cmd=insert&table=order_contents' and 'cmd=insert&table=order_payments', a generic insert verb that the document's own Post Variables list never declares. Its Available Tables list does include menu_groups, menu_categories and menu_items, so an undocumented menu insert cannot be excluded. What can be excluded is the claim as written: no update or delete verb is documented on either surface, and neither surface exposes a modifier resource at all - the legacy table list has none, and the modern MenuSerializer returns modifications as read-only output. Menu maintenance is documented instead as UI or sync work: Multi-Location Menu Management pushes from a primary location, and MenuDrive's Sync Menu exports entities outward to DoorDash. https://api.lavu.com/docs/swagger.json · retrieved 2026-09-04 adversarially verified

extensibility-doordash-preferred differentiator

Checked 2026-08-08 at the source rather than from memory. merchants.doordash.com/en-us/learning-center/doordash-preferred-integrations-program describes the DPIP framework and criteria and names no partners, stating that you can see which integrations are currently DoorDash Preferred on the Integrations webpage. get.doordash.com/en-us/integrations 301s to merchants.doordash.com/en-us/integrations, which was fetched with a Googlebot user agent (HTTP 200, 358,241 bytes): the provider roster is behind a client-side 'Select your POS provider' comparison tool and is not in the delivered HTML - the string 'Lavu' does not appear on the page at all, and only Toast, Square and Olo appear incidentally, so the page cannot be read as an enumeration in either direction. get.doordash.com/en-us/products/pos-integrations 301s and then 404s. On Lavu's side, the 250-article help centre documents a direct DSP integration ('Lavu, Menu Drive, and DoorDash', 'DSP Integration') describing menu sync, dual pricing and orders routed into the POS, but the phrase 'preferred integration' occurs zero times in the corpus and Lavu claims no DPIP status. Unresolved - the authoritative list is not publicly readable.

extensibility-first-party-delivery-integrations differentiator

Same correction — the integrations page's "Integration available with integrator" annotation on Uber Eats and Grubhub is affirmative evidence against first-party status for those two; DoorDash alone is documented direct. https://lavu.com/integrations/ · retrieved 2026-08-01 adversarially verified

extensibility-middleware-compatibility

Three major aggregation platforms are named as supported endpoints on Lavu's own integrations page: Otter, Chowly and Checkmate. https://lavu.com/integrations/ · retrieved 2026-08-01

extensibility-accounting-connectors

Xero — one of the two headline connectors — is annotated "Integration available with integrator" on Lavu's own integrations page, i.e. not a first-party connector. QuickBooks, Shogo, Restaurant365 and Davo are listed without that caveat. Journal-entry/GL mapping depth remains undocumented. https://lavu.com/integrations/ · retrieved 2026-08-01 adversarially verified

extensibility-payroll-export

Lavu sells its own payroll and integrates QuickBooks and Restaurant365 workforce; two named third-party payroll providers (Gusto, ADP, Paychex, Paylocity) are not listed. https://lavu.com/integrations/ · retrieved 2026-08-01

extensibility-app-marketplace

A public integrations catalog lists named third-party apps by category, and 'Lavu Store' is a monitored status-page component; operator self-install is not documented. https://lavu.com/integrations/ · retrieved 2026-08-01

extensibility-headless-embedded

The API can drive transactions: documented POST endpoints /v2/customer/create-order/ (a full order payload including items, modifiers, seats/courses, checks, custom charges, and delivery address), /v2/customer/close-order/, /v2/create-payment-record/, and external-payment/payment-intent routes. Shortfalls: no vendor-documented headless or embedded-ordering program surrounds them, access is gated to authorized customer accounts, and the docs self-describe as 'under completion'. https://api.lavu.com/docs/swagger.json · retrieved 2026-08-05

extensibility-data-portability-exit differentiator

Verified verbatim: "Lavu has no obligation to retain, provide access to, or allow extraction of User Content or User Data post-termination, except as required by applicable law or card association rules. Lavu may delete all User Content and User Data immediately upon termination, without liability to you or any third party." An express disclaimer of the extraction obligation is positive evidence of absence. https://lavu.com/terms-of-service/ · retrieved 2026-08-02 adversarially verified

reliability-offline-order-entry

Crash Kit 101 lists, for operation without internet, "Add food and drink to open orders", "Start new orders", "Send orders to the kitchen" and "Print checks" — order entry, ticket routing and check printing, which is the claim exactly. Re-evidenced from a marketing page to vendor documentation on verification. https://support.lavu.com/en/knowledge/lavu-crash-kit-101 · retrieved 2026-08-02 adversarially verified

reliability-offline-card-auth differentiator

The vendor sentence is "Lavu caches card transactions locally during an outage and processes them when connectivity is restored. Standard risk thresholds apply." That is store-and-forward CAPTURE, not offline AUTHORIZATION — nothing is authorized while offline, and Lavu never claims it is. Source is a marketing page with a comparison table, not documentation. This is exactly the cell the brief says to hold to the highest bar; the dossier already scores payments-offline-store-and-forward as partial, so scoring the same mechanism "yes" here is double-counting marketing copy. https://lavu.com/restaurant-pos/offline-mode · retrieved 2026-08-01 adversarially verified

reliability-offline-decline-liability differentiator

Positive absence in the place the disclosure would live. Crash Kit 101 is Lavu’s own outage guidance and characterises store-and-forward only as trading verification speed for operational continuity — no allocation of loss on a post-reconnect decline, no per-transaction cap, no cumulative cap, no reconnect failure report. The marketing offline page says only "Standard risk thresholds apply." https://support.lavu.com/en/knowledge/lavu-crash-kit-101 · retrieved 2026-08-02 adversarially verified

reliability-lan-degraded-multi-terminal differentiator

Re-examined 2026-08-08 against the full support.lavu.com dump (250 articles). Lavu Crash Kit 101 is the only article that enumerates degraded operation and it is written per-device: during an outage you can 'conduct cash transactions, open the cash drawer, add food and drink to open orders, start new orders, send orders to the kitchen, print checks', with card and gift-card transactions unavailable. It never says whether a second iPad sees those orders. Basic Network Troubleshooting treats 'Offline' in the POS header purely as a WiFi/access-point fault, and its remedy is fixing the access point, not describing a LAN-only mode. Lavu app version says only that mismatched app versions across iPads 'reduce the risk of orders not properly syncing across all devices'. Grepping the dump for 'local server', 'master iPad', 'primary terminal' and 'peer-to-peer' returns nothing, and api.lavu.com/docs/swagger.json is a cloud REST API with no local-sync surface. Neither presence nor absence of shared LAN check state is documented, so unknown.

reliability-local-transaction-engine differentiator

An on-premise component exists: "Lavu Local Server" is one of 14 independently monitored components on the public status page, alongside Point of Sale, KDS, Kiosk, Loyalty, Menu Drive, API, Lavu To Go, Order Status Monitor, Pilot, Lavu Store, Phone System, Payment Processing and Admin Control Panel. Shortfall: Lavu publishes no architecture, install or configuration documentation for it — the legacy article stating it is a prerequisite for KDS Pro (support.lavu.com/hc/en-us/articles/200108983) returns HTTP 404 to retrieval, and the current outage article never mentions a local server at all. Its role on the ordering path is asserted nowhere. https://status.lavu.com/ · retrieved 2026-08-02 adversarially verified

reliability-offline-kds-printing

Crash Kit 101 lists "Send orders to the kitchen" and "Print checks" among the functions that continue during an outage. The claim is satisfied by kitchen printer routing alone ("kitchen display and/or kitchen printer routing"). Re-evidenced from a marketing page to vendor documentation on verification. https://support.lavu.com/en/knowledge/lavu-crash-kit-101 · retrieved 2026-08-02 adversarially verified

reliability-printer-fallback

Lavu's documented mechanism for an unavailable kitchen printer is a manual workaround, not failover: Printer Redirects "are a way you can temporarily change which kitchen printers your menu items print from", enabled by hand on the POS, and "when you are finished using that redirect, you will need to come back to this screen to disable your redirect". Basic Printer Setup's enumerated per-printer settings (setting, name, static IP, port, type, command set, model, image capability) contain no backup-printer or failover option, and the Epson troubleshooting article shows an unreachable printer surfaces a "Failed to Write" error rather than re-routing. A documented manual redirect plus a settings enumeration with no backup option is positive evidence there is no automatic failover with staff alerting. https://support.lavu.com/en/knowledge/printer-redirects · retrieved 2026-08-03

reliability-sync-conflict-handling

Re-examined 2026-08-08. The only reconciliation mechanic Lavu documents is payment-side: Lavu Crash Kit 101 describes Store and Forward, where an iDynamo reader stores card details in iPad memory and 'once you are back online, all card details captured will slowly begin to process'. That is card capture, not order-record merge. No article in the 250-article support.lavu.com dump states last-write-wins, merge or operator-prompt behaviour for two devices editing the same check during a partition; the closest is Lavu app version warning that mixed app versions across iPads risk 'orders not properly syncing'. api.lavu.com/docs/swagger.json (26 paths) exposes order/check/item/payment resources with no version, etag or conflict field, but a cloud read API is not where a client-side partition policy would be stated. Unresolved.

reliability-offline-feature-matrix

Raised from "no" on verification. Crash Kit 101 does state offline behaviour affirmatively on both sides: it enumerates six functions that keep working and states that credit and gift card transactions specifically require active internet to validate card details, offering a CardPointe virtual terminal or iDynamo store-and-forward as workarounds. Shortfall: that is not the published matrix the claim describes — loyalty lookup, refunds and text-to-pay are never addressed, it lives in a troubleshooting article rather than a feature matrix, and it contradicts lavu.com/restaurant-pos/offline-mode. https://support.lavu.com/en/knowledge/lavu-crash-kit-101 · retrieved 2026-08-02 adversarially verified

reliability-public-status-page

status.lavu.com, no login, monitored components include Menu Drive, POS, Admin Control Panel, Kiosk, Loyalty, Lavu To Go, Order Status Monitor, Pilot, Lavu Local Server, Payment Processing, KDS, API, Lavu Store and Phone System, plus incident history and email/SMS/webhook/RSS subscriptions. No uptime percentages published. https://status.lavu.com/ · retrieved 2026-08-01

reliability-247-live-support

Pure marketing copy ("24/7 live support from real humans. No tickets. No runaround.") that the dossier's own dominant complaint theme directly contradicts, and that Lavu itself contradicts by requiring cancellations to go through a business-hours-style Customer Care line. Scoring it "yes" while simultaneously logging "Effectively there is no customer support" as the top complaint is internally inconsistent. https://lavu.com/service-promise/ · retrieved 2026-08-01 adversarially verified

reliability-onsite-install differentiator

Lavu's purchase gateway (buy.lavu.com, linked from the lavu.com homepage) offers three implementation tiers: 'Self Setup' free ('Self-guided hardware install', 'Go-live check-in', knowledge base and email support); 'Guided Remote' $299 one-time ('Expert-led remote install', 'Remote staff training', 'Go-live support'), marked recommended; and 'Premium Onsite' $1,499 one-time, described as 'A Lavu technician comes to you to build, install, and train on-site' with features 'Onsite technician visit', 'In-person hardware & printer setup', 'In-person staff training', 'Launch-day support'. Shortfall: in-person install is a paid premium upgrade, not included in either the $0 Starter or $79/mo Growth plan, and it appears nowhere in the 250-article help centre, whose Onboarding hub calls the programme 'our self onboarding process' and whose only install article is the Pre-Remote Installation Checklist, which requires the merchant to drill counters, mount access points, unbox iPads and set up printers before a remote onboarding specialist begins. Graded C because the source is Lavu's commercial catalogue, not implementation documentation. https://buy.lavu.com/api/services · retrieved 2026-08-08

reliability-menu-build-service differentiator

MenuDrive advertises 'Done-for-you menu setup' for online ordering and Lavu claims a dedicated onboarding specialist; a first-party POS menu build as part of onboarding is not explicitly stated. https://lavu.com/online-ordering/ · retrieved 2026-08-01

reliability-hardware-replacement-sla

LavuCare is 'included by default on all Lavu deals for $199 per year, payable on the anniversary month of your contract' and provides 'overnight hardware replacement in the event of equipment defect or failure' (shipping and handling per replacement; excludes mass loss and natural disasters). The subscribable NDR Service additionally commits weekday orders before 5PM ET to same-business-day shipment for next-business-day delivery. https://lavu.com/terms-of-service/ · retrieved 2026-08-05

reliability-pci-dss-4-attestation

Lavu states only 'PCI compliant' on its payment-processing page. No AoC, no PCI DSS version, no P2PE listing reference and no trust center are published. https://lavu.com/payment-processing/ · retrieved 2026-08-01

reliability-mfa-role-based-access

Role-based permissions are documented: five access levels (0-4) gate POS and back-office functions from clock-in-only (0) through voids/discounts/refunds and reopening orders (2), full back-end menu/reports/inventory/management access (3), and multi-location switching (4), with per-function access-level dropdowns throughout Advanced Location Settings. Shortfall: no multi-factor authentication is documented for Control Panel or POS administrative logins anywhere - credentials are username/password (minimum 8 characters) and numeric PINs. https://support.lavu.com/en/knowledge/lavu-access-levels · retrieved 2026-08-05

reliability-self-serve-training

The library is public, free and login-free: a HubSpot help centre of roughly 250 articles with a dedicated Onboarding section (menu building, employee profiles, tax profiles, payroll, time cards) and some video content - Lavu Product Demonstration Videos ("Two demonstration videos showing off the Lavu POS, and Lavu Control Panel"), POS Video - Splitting Orders, POS - Tilling In and Out Video. Lavu's own $0 Self Setup service is described as "Knowledge base & step-by-step videos". Two shortfalls: the video content is a handful of clips, not a structured LMS, and nothing in the whole corpus documents a training or practice mode on the terminal. https://support.lavu.com/en/knowledge/lavu-product-demonstration-videos · retrieved 2026-08-09 adversarially verified

reliability-failover-terminal-role differentiator

Re-examined 2026-08-08 against the full 250-article support.lavu.com dump. Grep across every article for 'local server', 'master iPad', 'master terminal', 'primary terminal', 'primary device' and 'failover' returns only two things, neither on point: Cross-Country Reporting's 'Primary Account' (a multi-location reporting hierarchy) and Lavu Crash Kit 101's failover MODEM (a 5G LTE backup WAN link that reroutes iPad traffic when the ISP drops). The Pre-Remote Installation Checklist's network build is router, switch, access points, iPads and IP printers with no on-premise server appliance. So Lavu never names a master/server terminal role in the first place, and consequently never states whether another terminal can assume it. Absence of the role in the docs is not evidence the architecture lacks one, and this dump is known to be incomplete (9 of the 250 articles were reachable only via cross-links, not the sitemap). Unresolved.

reliability-cellular-backup

Vendor-documented and vendor-aligned hardware: 'a failover modem is a device that can be connected to a wireless data provider (like Verizon, AT&T, or T-Mobile) and provide a 5G LTE connection to the internet for your restaurant', sold as 'compatible with the networking equipment that we sell'; it 'will monitor the status of your internet connection, and will only activate once it has detected an outage', after which 'the iPads network traffic will automatically be routed through the failover modem' with 'no acknowledgments nor limitations on your software', including card and gift card transactions. https://support.lavu.com/en/knowledge/lavu-crash-kit-101 · retrieved 2026-08-05

commercial-month-to-month-contract differentiator

ToS references a 'selected subscription term (e.g., monthly, annual)', so a monthly term appears to exist, but Lavu publishes no month-to-month offer or price. https://lavu.com/terms-of-service/ · retrieved 2026-08-01

commercial-no-early-termination-fee differentiator

Verified verbatim in the ToS: "You may not cancel your subscription prior to the end of your then current subscription term", and "you will not be eligible for a prorated refund of any portion of the subscription fee paid for the then current subscription period." No dollar ETF is stated because early exit is forbidden outright — economically a term-remainder liability. https://lavu.com/terms-of-service/ · retrieved 2026-08-02 adversarially verified

commercial-autorenew-terms-published

Auto-renewal for an equivalent period 'at our then current price' is published, and cancellation must precede the Renewal Commencement Date via a phone call to 505-559-5100 — but no notice window in days is stated. https://lavu.com/terms-of-service/ · retrieved 2026-08-01

commercial-processing-not-bundled differentiator

Third-party processing is documented, not forbidden. 'Is Lavu PCI Compliant?' addresses non-Lavu-Pay merchants directly: 'If you are not signed up for Lavu Pay, the card readers you will use are also PCI compliant. You should also reach out to your credit card processor to ensure that you remain PCI compliant through their standards and services.' End of Day - Tips & CC Batching is written processor-agnostically ('You can make changes to tips for most processors up until the point that you settle your batch'; 'We recommend setting up automatic batching with your credit card gateway'), and Advanced Location Settings - Checkout Options documents a non-integrated mode - 'Credit card info to ask for when integration is turned off' with options None / Card Type, Last Four, and Card Tip / Card Type and Card Tip - which lets any external terminal be used. Shortfall: Lavu publishes no list of supported integrated processors or gateways anywhere on support.lavu.com (250 articles) or lavu.com, so 'a processor of the operator's choice' is not established for integrated processing; the integrated path documented is Lavu Pay via CardConnect/CardPointe (plus Adyen NYC1 and Verifone readers), and Lavu itself calls the CC-integration-off setting 'uncommon'. Commercial terms for running off Lavu Pay are not published either - lavu.com has no pricing page (/pricing, /plans and /buy-now all 301 to the homepage). https://support.lavu.com/en/knowledge/advanced-location-settings-checkout-options · retrieved 2026-08-08

commercial-interchange-plus-published differentiator

No processing rate of any structure is published — the payment-processing page claims 'transparent pricing' while disclosing nothing. https://lavu.com/payment-processing/ · retrieved 2026-08-01

commercial-rate-increase-clause differentiator

Verified verbatim: the subscription "will automatically commence on the first day following the end of such period ... and continue for an additional equivalent period, at our then current price for such subscription." No cap on the increase, no stated notice period, and the cancellation clause forecloses a penalty-free exit in response. https://lavu.com/terms-of-service/ · retrieved 2026-08-02 adversarially verified

commercial-pricing-published

Real published figures exist on Lavu's own ungated commerce host: three plans - Starter $0/month ("Core POS", "One terminal", 24/7 support), Growth $79/month ("Core POS", "Custom hardware options"), Enterprise quote-only (customPricing true) - plus per-module add-on prices (Kitchen Display $29, Payroll $39, Inventory $29, Reservations $19, Marketing $25, Loyalty $19, Gift Cards $15 per month) and onboarding services (Self Setup $0, Guided Remote $299 one-time). Read from buy.lavu.com/api/plans, /api/addons and /api/services. Shortfalls: no per-additional-terminal or per-additional-location increment is published anywhere - Starter simply includes "One terminal" - no card processing rate is published, and the Enterprise tier is contact-sales. lavu.com/pricing/ itself now 301s to the homepage. https://buy.lavu.com/ · retrieved 2026-08-09 adversarially verified

commercial-module-unbundling differentiator

Lavu's self-serve purchase gateway prices modules individually as monthly add-ons: Kitchen Display $29, Payroll $39, Reservations $19, Marketing $25, Inventory $29, Gift Cards $15, Loyalty $19, Customer Display $12, Employee Scheduling $22. Base plans are Starter $0/mo ('Core POS', one terminal, 24/7 support, 'Add-ons available'), Growth $79/mo ('Add-ons available'), and Enterprise at custom pricing, whose bundle list includes Digital General Manager, AI Reporting, AI Marketing, Inventory Management, Online Ordering, Loyalty Programs, Gift Cards and Advanced Analytics. Shortfalls: (1) the claim's cancellation half is unaddressed - no published terms state that an add-on can be dropped independently or that doing so leaves the base subscription priced as-is; lavu.com/terms-and-conditions is the only commercial document linked from the site and lavu.com has no pricing page at all (/pricing, /plans, /buy-now all 301 to the homepage); (2) online ordering (MenuDrive) is not among the nine priced add-ons - it appears only inside the custom-priced Enterprise bundle. https://buy.lavu.com/api/addons · retrieved 2026-08-08

commercial-hardware-purchase-outright

Lavu runs a public storefront at shop.lavu.com (linked from the lavu.com homepage) with published outright prices across every required category: terminals - Complete POS Station Bundle, iPad Air 13in (M4) $2,374, Wi-Fi Handheld Bundle $1,270, Cellular Handheld $1,350; tablets - iPad Air 13in $799, iPad mini $499 / $749 cellular; KDS - Epson TrueOrder Kitchen Display System $1,119 (21.5in monitor with bump bar) to $1,262; printers - Epson receipt $275, kitchen $345, label $440; cash drawers - APG 16in $120; stands $240-$325; networking bundles $1,800-$4,140. The same catalogue is served as 51 one-time-priced SKUs by the buy.lavu.com purchase gateway. No lease, rental or financing option is offered on the storefront, and the string 'lease' appears zero times across all 250 support.lavu.com articles (the help-centre search API returns total 0 for the term). Hardware language throughout the docs is purchase language - 'the card readers you purchase through Lavu', 'the networking equipment that we sell'. Graded C: this is a first-party commerce catalogue, which is a pricing surface rather than documentation. https://shop.lavu.com/collections/ · retrieved 2026-08-08

commercial-hardware-not-locked differentiator

The KB's Equipment and Hardware category documents third-party, non-proprietary hardware as the normal path: a Compatible Star Micronics Printers list, nine Epson printer articles (TM-T88VII, TM-m30iii, wireless setup via Epson's own TM Utility app), APG Cash Drawer setup and dual-drawer configuration, Apple iPads and iPhones/iPods as the terminal, a Tor Rey L-EQ Bluetooth scale and a Socket Bluetooth scanner. Card acceptance is not single-vendor either - IDTech VP3300, Ingenico LANE 3000, Adyen NYC1, Verifone and PAX readers all have setup or troubleshooting articles - and Lavu documents operating without Lavu Pay ("If you are not signed up for Lavu Pay, the card readers you will use are also PCI compliant"). Caveat for the reader: readers are sourced through Lavu and no merchant-chosen gateway list is published, but the claim's bar is at least one non-proprietary option and Lavu clears it on the terminal, printers and cash drawer. https://support.lavu.com/en/knowledge/lavu-equipment-hardware · retrieved 2026-08-09 adversarially verified

commercial-data-export-self-serve

Control Panel - Transactions: the module 'allows to see and search through ALL of your restaurants orders', split into Orders and Payments pages, and under Export states 'You can export any or all of your orders from either of these pages', selecting individual rows or the whole page. Lavu Reports - How to Export a Report: 'Any report within Lavu can be exported into a CSV file... Similar steps can be followed for reports in the Transactions and Manage Time Cards pages', which covers labour via the Time Card reports, line items via Sales by Item and Modifier Usage, and payments via the End of Day and Bank Deposit reports. Inventory Import and Export and Menu Export / Import cover the reference data. Both routes are in-product, self-serve from the Control Panel, with no fee or support ticket mentioned. Independently, api.lavu.com/docs/swagger.json exposes GET /v1/customer/orders/, /orders/{id}/checks/, /checks/{id}/payments/, /orders/{id}/items/ and /items/{id}/modifiers-used/ under OAuth 2, so the transactional record is also machine-readable; the 26-path spec has no labour or time-card resource, which is why the CSV route is the one cited for labour. https://support.lavu.com/en/knowledge/control-panel-transactions · retrieved 2026-08-08

commercial-export-customer-and-loyalty differentiator

Customer records export machine-readable: Reports > V1 Reports > Special > Customer Export (with a matching CSV Customer Import). Shortfalls: loyalty point balances and gift-card balances are only viewable and adjustable per individual card (with per-card history) - no documented bulk export of the loyalty ledger or outstanding gift liability - and the ToS disclaims post-termination extraction: Lavu 'has no obligation to retain, provide access to, or allow extraction of User Content or User Data post-termination' and 'may delete all User Content and User Data immediately upon termination'. https://support.lavu.com/en/knowledge/customer-management · retrieved 2026-08-05

commercial-post-termination-export-window differentiator

Same clause, checked for this proposition on verification: the ToS permits immediate deletion on termination and disclaims any obligation to allow extraction. A retrieval window is not merely unpublished — the contract reserves the right to eliminate it. https://lavu.com/terms-of-service/ · retrieved 2026-08-02 adversarially verified

commercial-data-ownership-clause differentiator

Verified verbatim: "You grant Lavu a perpetual, irrevocable, worldwide, royalty-free, nonexclusive, fully sublicensable license to use, reproduce, modify, distribute, display, perform, create derivative works from, and incorporate your User Content into Lavu Products or other works for any purpose, including marketing, product development, AI training, or promotion, without compensation or further permission." No merchant-ownership statement and no constraint on vendor reuse. https://lavu.com/terms-of-service/ · retrieved 2026-08-02 adversarially verified

commercial-pci-p2pe-tokenization

Hardware-encrypted card entry is documented - "using properly encrypted card readers", and for Lavu Pay merchants "we will ensure that you remain PCI compliant through your card reader and your CardConnect account" - but the scope-reduction half of the claim is contradicted by Lavu's own instructions for the CardPointe PCI questionnaire: "Q: Your Point-to-point Encryption system? A: No", followed by a full guided assessment covering payment application type, remote access, printed card data and information security policy. No validated P2PE listing, no tokenization architecture and no SAQ type (A, A-EP, P2PE-HW or otherwise) is named anywhere in the help centre. https://support.lavu.com/en/knowledge/cardpointe-pci-compliance · retrieved 2026-08-09 adversarially verified

commercial-pci-dss-4-controls

Examined 2026-08-08. support.lavu.com carries exactly two PCI articles. 'Is Lavu PCI Compliant?' is a customer FAQ that asserts only that 'the card readers you purchase through Lavu, as well as the Lavu POS software, are all PCI compliant', with no standard version and no control detail. 'CardPointe PCI Compliance' is a walkthrough of the SAQ in the CardConnect merchant portal and does reference the standard - 'Read through the PCI DSS 4.0 update, check I Understand' - but it is a script of recommended SAQ answers (Point-to-point Encryption: No; Remote Access: No) about the MERCHANT's environment, not a statement of Lavu's own controls. Grepping all 250 dumped articles for 'MFA', 'multi-factor', 'two-factor', '4.0.1', '6.4.3', '11.6' and 'script integrity' returns zero hits, and the help-centre search API returns total 0 for 'MFA' and 'multi-factor'. lavu.com has no security, trust or compliance page - its complete link set exposes only privacy-policy and terms-and-conditions, and guessed paths 301 to the homepage. So the specific v4.0.1 future-dated controls (CDE MFA, payment-page script integrity per 6.4.3/11.6.1) are not documented on any Lavu surface I reached, but that is a search miss over a corpus known to be incomplete (9 of 250 articles were reachable only by cross-link), which is not positive evidence of absence. Unresolved.

commercial-privacy-dsar-tooling

Privacy policy documents an email/phone rights process (delete, correct, access, portability) via support@lavu.com, with CCPA requests limited to one per customer per year. No in-product operator tooling for guest DSARs and no published DPA. https://lavu.com/privacy-policy/ · retrieved 2026-08-01

commercial-wcag-kiosk-accessibility differentiator

Positive absence at both ends of the claim. Lavu Kiosk - Basic Customization enumerates the kiosk's entire settings surface - theme colour by hex, tip allowance, idle and start-page imagery (standard, menu carousel or custom image), Pickup and Dine-In dining options, order timeout duration, receipt printer, payment gateway, and the checkout fields, of which only the guest's name is mandatory - and no tactile keypad, audio or other non-visual access mode appears in it. On the publication half, the 4,844-URL first-party sitemap census across lavu.com, support.lavu.com and shop.lavu.com contains no accessibility, VPAT or ACR page of any kind; the only compliance documents Lavu publishes are the privacy policy and the terms. https://support.lavu.com/en/knowledge/lavu-kiosk-basic-customization · retrieved 2026-09-04 adversarially verified

commercial-dual-pricing-compliant differentiator

Lavu operates a cash-discount program, not surcharging, so the claim’s automatic debit and prepaid exclusion is structurally moot rather than satisfied. Receipt disclosure is documented — the support article shows both totals on the printed check — but menu-board disclosure is only restated as a federal requirement, not implemented in product. Shortfall: US-only, Lavu Pay only, admin-enabled, and no surcharging product exists. https://support.lavu.com/en/knowledge/cash-discount-program · retrieved 2026-08-02 adversarially verified