Revel Systems

order-capture-floor-plan-editor

A real graphical editor is documented. In the Management Console under Establishments > Tables an operator gets a grid, adds named sections via '+Add New Section' (the POS sorts sections alphabetically), picks 'the most appropriate table shape from the options in the top section', drags it into place, then sets the 'Table Name' field and a 'Capacity' field for 'the number of guests the table seats', and clicks Save. Tables can be dragged to move, marked Inactive (grey, hidden from the POS but visible in the console), and whole sections deleted. Table Tags (Wheelchair Accessible, Patio, Booth) can be assigned per table but must be switched on by Revel Support and are only useful with Table Reservations. Shortfall, and it is the reason this stays partial: the documentation describes ONE layout per establishment with sections inside it - there is no save/select of multiple named floor-plan layouts - and no assignment of sections to servers is documented anywhere, including in Table Service Settings, which covers only course prompts and auto-gratuity. https://support.revelsystems.com/s/article/Building-Your-Table-Layout-1583149094553 · retrieved 2026-08-02 adversarially verified

order-capture-seat-level

Quick Course/Seat Menu adds a Course/Seat widget on the POS: after an item is added, +/- controls set the seat (and course) number per line, with the widget stickied at top right since v2.78. Split Bills then offers 'Split By Seat Number' alongside Split Evenly / Split Manually / Split By Item, so the check divides by the seats tagged at entry without re-keying items. https://support.revelsystems.com/s/article/Split-Bills-1582901435396 · retrieved 2026-08-04

order-capture-coursing-hold-fire

TSR: Course Fire documents 'Prompt for course' at item entry, per-course release to the kitchen (Send to Kitchen > Send Course), and a Fire Next Course action on the POS ('tapping Fire Next Course on the POS will print a simple Fire Course X receipt to the kitchen'), plus optional 'Automatic course firing from Done on KDS' with a configurable delay and per-order manual override. https://support.revelsystems.com/s/article/TSR-Course-Fire-1582902249374 · retrieved 2026-08-04

order-capture-split-merge

Four split modes are documented by name, and they cover the split half of the claim well: 'Split Evenly' (prompts for a headcount and 'the system will automatically create 3 evenly split checks'), 'Split Manually' (prompts for a headcount then an explicit amount per check, with the last check taking the remaining balance), 'Split By Item' ('add as many checks as needed as well selecting which items to put on each check'), and 'Split By Seat Number'. The feature must first be enabled in the Management Console Settings. Shortfall: merging is the weak half. The only documented merge is 'Clear Split Bills', which 'merges split bill back into one total' but 'because it also refunds all payments on the order, clearing a split bill requires a security PIN from an employee with refund permission' - so merging after partial payment is destructive and permission-gated rather than an ordinary operation, and no documentation describes merging two separate checks or two tables into one. https://support.revelsystems.com/s/article/Split-Bills-1582901435396 · retrieved 2026-08-02 adversarially verified

order-capture-bar-tab-preauth differentiator

Bar tabs link a card and preauthorize a configurable 'Preauthorization Amount' (blank = prompt per tab; Bar Tabs setting supports 104 tabs per page), and swiping the card re-opens the tab. Shortfalls: preauth-and-link requires the Revel Advantage or FreedomPay integrations; 'Incremental authorizations are supported with our Freedompay iFCC integration' only; and no automatic end-of-day close of stale tabs is documented - the End of Day wizard offers manual 'Reconcile Open Orders' presets instead. https://support.revelsystems.com/s/article/Preauthorizations-and-Linking-Cards-to-Bar-Tabs-Tables-and-Orders-1582901172680 · retrieved 2026-08-04

order-capture-transfer-audit

A Transfer Owner action moves an open order between logged-in employees ('A list of logged in employees will appear. Tap on the employee and tap the Transfer button'), tables can be moved/merged, and a 'Transfer Orders' POS role permission gates who may transfer. Shortfall: no audit-log entry naming both employees is documented - the Action Log Report's enumerated actions (Item Deleted, Login Attempt, Price Override, etc.) do not include order transfers. https://support.revelsystems.com/s/article/TSR-Transferring-Order-Owners-1582902249371 · retrieved 2026-08-04

order-capture-native-handheld

Revel version 2.77 added an IPORT 'mobile order taker (MOT)' case: a handheld iPad case whose features are listed as 'Full protection for card swipe', 'Fast charging', 'Highly reduced cabling' and 'Support for Link 2500 and Moby 5500 payment devices', with a CONNECT PRO PayCase that magnetically attaches the payment device to the iPad case so both charge together in a MultiDock. The paired readers are documented as full tableside acceptance devices - the Moby 5500 'enables all payment methods - including EMV chip, magstripe NFC/contactless cards, or mobile wallets - anywhere, anytime that a merchant and consumer interaction may take place', and the Link 2500 is a portable device over WiFi and/or Bluetooth. The ordering app is the first-party Revel POS iOS app running natively on the iPad (App Store listing by Revel Systems INC: 'Requires iPadOS 15.0 or later'), not a mirrored desktop session. Caveat worth recording: the form factor is an iPad Mini in an accessory case rather than a purpose-built handheld terminal, and there is no iPhone or Android POS build - the only Revel iPhone app is Insights, which is reporting-only. https://support.revelsystems.com/s/article/iPort-stands-and-cases · retrieved 2026-08-02 adversarially verified

order-capture-offline-order-entry

Re-homed from the customer-gated Zendesk URL onto the live Salesforce help centre. Revel's outage best-practices article publishes a three-tier matrix per outage type. Under 'ISP / Network Outage' it states that 'When ISP/Network is down, you'll still be able to access the following functions: Create and close orders; Operate tills and take cash payments; Print to kitchen and receipt printers (ethernet or BT connected)', with 'Process CC / Debit Payments in offline mode' listed as available-but-limited, and under 'Revel Server Outage' it adds 'Use CDS & KDS'. It then lists what will NOT work (loyalty/rewards/gift cards, manual credit card or debit payments, EOD, house accounts, customer order history, frontend inventory). The companion Offline Mode article (https://support.revelsystems.com/s/article/Offline-Mode-Always-On-Mode-1582898971418) documents the settings side. So both halves of the claim hold: offline order entry and cash tender are documented, and the vendor does publish what does and does not work. https://support.revelsystems.com/s/article/outage · retrieved 2026-08-09 adversarially verified

order-capture-qr-same-check differentiator

Re-read the Smart Order article in the complete 693-article help-centre mirror (Googlebot capture 2026-08-04). The article is a configuration guide - Enabling Smart Order, Creating a QR Code, Creating a Custom Skin - closing with 'Revel Smart Order Limitations': 'At this time, Revel Smart Order: Cannot swap entirely different menus... Cannot use customer accounts... Cannot use a loyalty integration... Customer cannot edit order after payment is completed... Does not support pay at store option.' That list enumerates limitations without asserting it is exhaustive, and nothing in it, or anywhere else in the mirror, states whether Smart Order items land on the table's existing open check or on a separate ticket. The earlier 'no' inferred a separate ticket from 'Does not support pay at store option', but guests paying inside the QR flow is also how the market-leading at-table QR implementations behave and does not settle check attachment. Pulling the other way, Smart Order requires an Eat In dining option, requires 'at least one table' to be set, and generates QR codes per table, so orders are table-bound; Revel separately documents a manual merge path (TSR Moving Tables and Merging Orders) but never connects it to Smart Order. Searches of the mirror for smart order, open check, existing check and merge order surface nothing that resolves this. Undetermined either way. adversarially verified

order-capture-kiosk-first-party differentiator

Kiosk XT is Revel's first-party self-service kiosk driven by the same Management Console catalog: a Custom Menu with Mode/Station = Kiosk selects included products from the POS product list, and modifier classes carry over (including split modifiers, e.g. half-pizza toppings with the same Charge Full Price / half-price behavior as the POS). Shortfall: no ADA/accessibility conformance documentation for the kiosk exists anywhere in the help centre. https://support.revelsystems.com/s/article/Kiosk-XT · retrieved 2026-08-04

order-capture-drive-thru

Revel Drive Through (v2.72+) provides a Drive Through dining type with vehicle-data and call-name prompts (No/Prompt/Required), a dedicated Drive Thru Queue (oldest first, time-lapsed stamp, in-queue payment via cash/gift/fast credit), and an optional 'Support Fulfilled state' so a station acts as expediter; v2.79 added vehicle data on KDS/expo chits. Shortfalls: no order-point/pay-window/pickup-window separation, no tandem-lane sequencing or lane assignment, and no pull-forward/parking-spot assignment are documented. https://support.revelsystems.com/s/article/Revel-Drive-Through · retrieved 2026-08-04

order-capture-drive-thru-timers

The Speed of Service report records per-order/per-item Start Time, KDS Complete, Expedite Complete, Time on KDS, Time on Expedite, and Total Kitchen Time (requires KDS In-Progress Mode), and the Drive Thru Queue displays a time-lapsed stamp per car. Shortfall: timing is kitchen-stage based, not drive-thru segment based - no order-point / pay-window / pickup-window segment timers are documented (the only drive-thru lane hardware doc is the Delphi OCS order-confirmation-screen integration, which has no timer function). https://support.revelsystems.com/s/article/Speed-of-Service-Report-1583149670649 · retrieved 2026-08-04

order-capture-voice-ai differentiator

Searched the complete 693-article public help-centre mirror (captured 2026-08-04) for voice, voice AI, AI ordering, phone ordering, drive-thru AI and conversational ordering: the only phone-order feature documented is the Caller ID integration (incoming caller info shown for manual order entry), and the only drive-thru peripheral is the Delphi OCS confirmation screen; no first-party voice agent appears anywhere. The developer.revelsystems.com portal home (fetched 2026-08-05) lists its full guide catalog (Getting Started, Authentication, Capabilities, Data Connector, Cash Management through Weborders) with no voice-AI content and no named voice-AI partner program. Absence from documentation is not positive evidence of absence, so this stays unknown rather than no.

order-capture-throttling differentiator

Online ordering settings include 'Max number of online orders: Maximum number of online orders per time slot' and 'Online order time slot: Interval in minutes that defines available pickup/arrival/delivery time slots'. Shortfalls: the cap applies to online ordering only, not per channel, and there is no automatic quote-time extension from kitchen load - the Online Ordering FAQ answers the capacity question with the time-slot limit and states 'The functionality for multiple prep times doesn't exist at this time.' https://support.revelsystems.com/s/article/Online-Ordering-Setting-Up-Online-Ordering · retrieved 2026-08-04

order-capture-scheduled-orders

Future-dated orders are accepted on POS and online ('Max date window for online ordering' sets how many days ahead) and can be stored as invoices, with 'Automatically turn invoices into orders on their due date' releasing them at a configured time of day; kitchen print options note this prints future orders on their due date automatically (blocked if Send to Kitchen on Demand is enabled). Shortfalls: release is a single configured time of day, not a per-order computed fire time, and there is no per-channel lead time - 'The functionality for multiple prep times doesn't exist at this time' (Online Ordering FAQ). https://support.revelsystems.com/s/article/Future-Orders-1582902249369 · retrieved 2026-08-04

order-capture-catering

Catering Delivery Tracking gives a Catering dining option that prompts for a delivery date/time, a Catering button on the POS dashboard opening a Catering Delivery page of active/completed orders viewable by day, week, month or all future orders - separate from the standard order queue; deposits and installment payments run through Invoices & Deposits (including a 'Catering Specific Deposits' flow and house-account billing), and a Catering Delivery Report tracks orders, products and delivery dates. Shortfall: no quote/proposal stage is documented - the flow begins directly as an order or invoice. https://support.revelsystems.com/s/article/Delivery-Catering-1583149409698 · retrieved 2026-08-04

order-capture-order-ready-signal differentiator

Searched the complete 693-article public help-centre mirror (captured 2026-08-04) for order ready, ready signal, prep time, marketplace and DoorDash: 'SMS on Order Ready in the Kitchen' fires on KDS Done/Complete but sends an SMS to the guest via a Twilio integration, not a signal to marketplaces. The DoorDash Marketplace integration article's detailed supported/unsupported tables (eligibility, menus, products, modifiers, inventory/86ing, discounts, taxes, tips, orders, CRM, store info, Dasher details) never mention pushing an order-ready or prep-complete state to DoorDash, and merchants are told to keep using the DoorDash tablet/portal for several order actions - but the tables do not explicitly address readiness signalling either way, so this remains unresolved rather than a documented absence.

order-capture-void-comp-controls

Voids and comps each require a reason ('This requires the user to select a pre-existing reason or type in a new reason'; the POS Void Item(s) window prompts to 'enter the reason for the void'); Comps and Manual Discount are POS role-permission tokens, with Manager/Owner Access PINs required for restricted actions; and exceptions are reported via the Adjustments report ('a pre-payment auditing report focused on specific void, return, and exchange actions' drillable by order or employee), the Action Log, and Product Mix void/return/comp columns with an employee-sales audit mode. https://support.revelsystems.com/s/article/Loss-Management-Prevention-and-Auditing-1583149672029 · retrieved 2026-08-04

menu-pricing-nested-modifiers

One level of modifier groups is fully documented: modifier classes attach per product with 'Minimum Modifiers per Group' and 'Maximum Modifiers per Group' set independently per class, defaults (DFLT), and forced selection via minimums plus the 'Validate Modifier selection on submit' setting ('Select at least 1 modifier(s) please'). Shortfall: no nesting beyond one level — nowhere in the modifier documentation set (Introduction to Modifiers, Advanced Modifier Features, and the other 11 modifier articles in the complete help centre) can a modifier carry its own sub-modifier groups; deeper choice trees exist only by routing through combo products (combo set > product > that product's modifier classes), not as nested modifier groups. https://support.revelsystems.com/s/article/Introduction-to-Modifiers-1583154976165 · retrieved 2026-08-04

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

'Per Product Modifier Pricing' (a setting a Revel agent must enable) lets a single modifier carry a different 'Modifier Price' on each product it is attached to, set on the product's modifier screen without duplicating the modifier. Size itself is a modifier class whose members can carry an 'Override Price' replacing the product's base price. Shortfall: no size-by-modifier price matrix within a single product — a modifier's price cannot vary with the selected Size modifier; per-size modifier prices are only achievable by building sizes as separate matrix child products and pricing the modifier per product. Also, per-product modifier pricing requires Revel support/agent enablement. https://support.revelsystems.com/s/article/Advanced-Modifier-Features-1583154976185 · retrieved 2026-08-04

menu-pricing-fractional-placement differentiator

Documented natively. Split Modifiers apply modifiers to fractions of a product; Revel documentation states products can be split by halves, thirds and quarters, with split prices displayed as the order develops. The POS flow is documented ('tap First Half or Second Half on the modifier pop-up'), splitting is enabled per modifier class, and a parallel 'Split Modifiers for Online Ordering XT' article covers the digital channel. https://support.revelsystems.com/s/article/Advanced-Modifier-Features-1583154976185 · retrieved 2026-08-01 adversarially verified

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

UPGRADE TO PARTIAL ONLY (the schema offers no upgrade-to-partial verdict — do not record this as yes). A configurable pricing rule is documented: 'Charge Full Price for Split Modifiers' makes a topping ring at full price regardless of fractional placement (a $0.50 pepperoni still rings $0.50 on half), with proportional split pricing as the alternative. So fractional-vs-full is operator-configurable. Not yes: I found no documentation of a higher-half or average-of-halves rule, which is the discriminating case for specialty-pizza pricing. https://support.revelsystems.com/s/article/Advanced-Modifier-Features-1583154976185 · retrieved 2026-08-01 adversarially verified

menu-pricing-topping-quantity-tiers

'Add Quantity to Modifier' lets a modifier be applied N times via press-and-hold with the per-unit charge multiplying accordingly, with per-product 'Default Quantity' and 'Max QTY' fields. Descriptor buttons No / Side / Only / Lite (labels editable via 'Editable Modifier Options') cover light/on-side requests: 'No' removes the modifier's upcharge, 'Lite' is a kitchen instruction only. Shortfall: no configurable price multiplier per tier — light/extra tiers carry no distinct pricing (Lite does not change price; extra is quantity N at N x unit price), which is exactly the 'adding the modifier twice' mechanism the claim excludes. https://support.revelsystems.com/s/article/Advanced-Modifier-Features-1583154976185 · retrieved 2026-08-04

menu-pricing-size-style-matrix differentiator

Matrix Inventory defines a parent product with up to two Attribute Sets ('Matrix can even be used in Pizza Establishments that sell their pizzas in different sizes with different crust options'); the console generates a grid of all attribute combinations where 'Each product ... defined by a combination of attributes is a unique product with its own price, inventory and/or recipe'. Name and price are required per cell; price can be auto-filled from the parent then overridden per cell ('if the pricing is different for certain products, simply type in the new product price to override'). Matrix Inventory is disabled by default and enabled on request via Revel Support (no extra tier documented). https://support.revelsystems.com/s/article/Creating-Matrix-Inventory-on-the-Management-Console-1583150212824 · retrieved 2026-08-04

menu-pricing-included-allowance differentiator

Free modifier allowances are native: per modifier class per product, 'Free Type' is either Quantity ('the customer will be given the first three modifiers/toppings for free, and all other toppings will be charged at the price listed for that particular modifier') or Price ('up to $3 worth of modifiers would be given for free'), so only overage is charged. Substitution control is separately configurable: the Modifier Substitutions feature lets you specify per modifier exactly which substitutions are allowed ('you may, for example, wish to allow only substitutions of equal or lesser price'), enabled per product via a Sub column. https://support.revelsystems.com/s/article/Introduction-to-Modifiers-1583154976165 · retrieved 2026-08-04

menu-pricing-combos

Combo construction with swappable components and price deltas is thoroughly documented: Linked/Upsell combos have product sets with defaults where non-default choices carry a 'Product upsell Amount' / 'Upcharge Price' delta, editable per base product; Group Combos support per-set 'Price in Combo' and 'Default Product Upcharge Amount'; the Unified Combo Builder presents all sets on one screen. Shortfall: no automatic detection or conversion of eligible a-la-carte items already in the cart into a combo price — across all six combo articles in the complete help centre, combos must be entered as combo products (or the linked-combo prompt taken when the base product is added); no auto-combo recognition is documented. https://support.revelsystems.com/s/article/Linked-Combos · retrieved 2026-08-04

menu-pricing-upsell-prompts differentiator

Per-item upsell prompts exist on POS and kiosk: a linked combo's 'Prompt for upsell' setting is configured per base product (Yes = combo screen offered, No = not shown, Required = combo mandatory), and Kiosk XT natively shows a 'Make it a combo!' window after modifier selection. Shortfall: no upsell prompt is documented for Revel's online ordering channel (linked/upsell combos are also unsupported on the DoorDash integration), and no attach-rate reporting exists — the docs state only that 'Revel reports the savings involved in upsell combos as discounts against the base product'. https://support.revelsystems.com/s/article/Linked-Combos · retrieved 2026-08-04

menu-pricing-86-propagation

A single Item Availability action on the POS marks a product or ingredient unavailable and cascades: 'If an ingredient is unavailable, any products or modifiers that are linked to that ingredient with a recipe will also be unavailable', combos included. Propagation is documented to Revel's own online ordering ('If an item becomes unavailable before the customer checks out, it will show as unavailable in their cart'), to DoorDash Marketplace ('Items marked as unavailable on the POS will not be displayed on DoorDash', with 'on the fly changes using webhooks ... for instantaneous updates, including item availability for products, modifiers, and ingredients') and Uber Eats (zero/negative tracked stock unavailable), and Kiosk XT disables out-of-stock products. Shortfalls: no numeric propagation latency is documented (only 'real time'/'instantaneous' for DoorDash webhooks); no KDS propagation of 86s is documented; kiosk behavior is documented for stock-count-driven out-of-stock rather than the manual Item Availability flag. https://support.revelsystems.com/s/article/Managing-Item-Availability-on-the-Point-of-Sale · retrieved 2026-08-04

menu-pricing-countdown-auto-86 differentiator

Stock countdown with auto-86 at zero is documented: with 'Track in Inventory' plus 'Do not allow sale of this product without stock on hand' (Online Ordering XT: Product and Ingredient Inventory Tracking), sales decrement stock and the product shows as unavailable/unsellable at zero across POS, Online Ordering XT, DoorDash and Uber Eats; stock can be set on the POS via Set Stock. A scheduled auto-restore exists ('set a time in which the item will automatically return to available status' via Set Return Time with date and time). Shortfall: the scheduled auto-restore is documented only for items manually marked unavailable through Item Availability — stock-driven 86s return only when stock is updated, so countdown-plus-scheduled-restore as a single combined flow is not documented. https://support.revelsystems.com/s/article/Managing-Item-Availability-on-the-Point-of-Sale · retrieved 2026-08-04

menu-pricing-dayparting

Custom Menus schedule menus, items and prices by time: Application Type 'Time Slot Only' restricts a menu to a specific time of day; per menu you 'set the Price Tiers, effective dates and times of the menu. Once these times are set, the custom menu will only be active during the specified time ranges', and products are included per menu by category, subcategory or item. Day-part menus are an explicitly supported pattern ('Day parts menus (multiple custom menus with varying hours of availability) are supported' — DoorDash Marketplace article, 'think breakfast, brunch, dinner'). Timetables are configured per establishment in the Management Console. https://support.revelsystems.com/s/article/Custom-Menus-1583150454200 · retrieved 2026-08-04

menu-pricing-channel-price-books

Distinct menus per channel are native: custom menus with Mode set to Online, Bar, Kiosk, Menu Board, Catering, or Multi-Channel (one per third-party marketplace, e.g. named 'Uber Eats Menu, DoorDash'), each carrying its own Price Tier with per-item tier prices. A percentage-markup rule exists for third-party menus: '3rd Party Price Upcharge (%)' 'automatically markup the cost of products (base product price + upcharge percentage)'. Shortfalls: the percentage markup applies only to multi-channel (third-party) menus and only to delivery orders ('pick up orders do ignore this upcharge'); every other channel's price book is manual per-item Price Tier entry, and 'Custom Price Tiers cannot currently be edited on Revel's import/export spreadsheet' so each product must be updated individually. https://support.revelsystems.com/s/article/DoorDash-Marketplace · retrieved 2026-08-04

menu-pricing-dual-pricing differentiator

Searched the complete 693-article public help-centre mirror (captured 2026-08-04) for 'dual pricing', 'cash discount', 'cash price', 'surcharge' and 'non-cash'. The only related findings are an order-level percentage Surcharge setting (Creating a Surcharge: a named percentage 'applied to every order' — not item-level, not card-vs-cash) and Como Loyalty's 'use points directly as cash discount', which is unrelated. No article documents an item-level dual-pricing / cash-discount program, card price display, or receipt treatment, and no article enumerates price-display alternatives that would establish positive absence. developer.revelsystems.com guide pages checked in earlier passes do not cover pricing display either. Unresolved: absence from the complete help centre alone does not prove the capability (often sold through the Revel Advantage payments program) does not exist.

menu-pricing-allergen-nutrition

No allergen or nutrition capability appears anywhere in the complete 693-article public help centre: searches for 'allergen', 'nutrition' and 'calorie' match only a SNAP/EBT definition, and the product/modifier/ingredient setup guides define no allergen flag or nutrition fields. Positive evidence for the publication half: Revel's own DoorDash Marketplace documentation states 'Recipes / ingredients details are not displayed on DoorDash' and recommends the workaround that 'Merchants can leverage product descriptions to provide this information to customers' — i.e., free-text descriptions, not structured allergen/nutrition data, are the documented mechanism for conveying item composition to online/third-party menus. https://support.revelsystems.com/s/article/DoorDash-Marketplace · retrieved 2026-08-04

menu-pricing-recipe-linkage differentiator

Recipes link ingredients (each with name, cost and unit of measurement) to products and to modifiers: 'When the product is sold, this will automatically deducted ingredients from your inventory', and for modifiers 'If the modifier is selected at the time of sale the ingredients attached to modifiers will pull the corresponding inventory quantities' (How to Attach Ingredients to Modifiers with Recipes). Item-level theoretical food cost is native via Dynamic Cost: enabling 'Use Ingredient Cost to Calculate Product Cost' makes Revel compute product cost as 'the total cost of all counterpart ingredients in a product', displayed next to each product (Setting Up Product Cost and Dynamic Cost). https://support.revelsystems.com/s/article/Ingredients-Recipes-Guide-1583150212848 · retrieved 2026-08-04

menu-pricing-3p-menu-push

Direct, middleware-free menu push exists: 'Revel now offers direct integration with DoorDash Marketplace, eliminating the need for middleware' ($20/month/establishment, v2.79+, 'Revel becomes the source of truth for all menus and products'), and an equivalent direct Uber Eats integration. Shortfalls: syncing is a manual operator action ('Menu updates are done manually and are only sent to DoorDash upon pressing the setting Push Changes'), each change then awaits DoorDash confirmation ('usually only takes a few minutes per change request but, in rare instances, can take up to 2 hours'); and no per-item sync status or rejection-error surfacing is documented — the Troubleshooting section relies on symptom-based manual workarounds (e.g. modify a product, revert, and Push Changes to force a resync; image rejections surface only as images not appearing after DoorDash's 3-5 day review). https://support.revelsystems.com/s/article/DoorDash-Marketplace · retrieved 2026-08-04

menu-pricing-dynamic-pricing

Rule-based price variation by time and by channel is documented: timed custom menus each carry their own Price Tier and 'will only be active during the specified time ranges' (time-based), and multi-channel menus support an automatic '3rd Party Price Upcharge (%)' markup on base prices (channel-based). Shortfalls: no demand-based pricing exists anywhere in the complete help centre, and no floor/ceiling guardrail configuration is documented for any pricing mechanism. https://support.revelsystems.com/s/article/Custom-Menus-1583150454200 · retrieved 2026-08-04

payments-processor-choice differentiator

Verified and in fact understated: live components include Worldpay TriPOS, FreedomPay, Adyen, Worldpay, Eigen and the Revel Advantage Merchant Portal. Weakness to record: a status page proves integrations are operated, not that a merchant may freely select an acquirer at signing; no processor-choice policy document is publicly reachable. https://status.revelsystems.com/ · retrieved 2026-08-01 adversarially verified

payments-published-rates differentiator

No processing rate published anywhere; the vendor pricing page itself no longer exists. https://revelsystems.com/pricing/ · retrieved 2026-08-01

payments-dual-pricing differentiator

Still unresolved after searching the complete 693-article public help-centre mirror of support.revelsystems.com (captured 2026-08-04) for 'dual pricing', 'cash discount', 'two prices', 'cash price', 'card price' and 'non-cash adjustment': zero relevant hits (the only 'cash discount' match is the Como Loyalty XT integration using points as a discount). Revel's documented mechanism for offsetting card cost is surcharging (Creating a Surcharge; FAQ: Credit Card Surcharging; Adyen AU/NZ surcharge setup) - no article stores two prices per item or prints cash vs card totals on the check. Because the surcharge articles do not enumerate an exhaustive list of pricing modes, this absence is recorded as unknown rather than no. developer.revelsystems.com guide pages contain no dual-pricing resource either.

payments-surcharge-guardrails differentiator

Surcharging exists but the guardrails do not: 'Creating a Surcharge' documents a flat percentage 'applied to every order' configured per establishment in Management Console Settings (Surcharge Name / Surcharge Percentage fields) with no card-type detection at all, and 'FAQ: Credit Card Surcharging' states debit/prepaid cards cannot be surcharged and cites 'a 3% surcharge cap' while making clear 'it is your responsibility as a business owner to stay current with the latest compliance rules and regulations' - i.e. the merchant, not the engine, enforces the exclusions and the cap. Named shortfall: no automatic BIN/product-code debit-prepaid exclusion or network-cap enforcement is documented anywhere in the complete help centre; the only per-card-type surcharge configuration is the Adyen AU/NZ setup, applied on the terminal and provisioned by Revel Payment Operations via email request (payments-management@revelsystems.com), not merchant-controlled. https://support.revelsystems.com/s/article/Creating-a-Surcharge-1583149094546 · retrieved 2026-08-04

payments-emv-nfc

EMV and contactless are documented across the whole active terminal fleet: the Active Supported Hardware catalogue describes the Ingenico iSMP4 as enabling 'EMV chip & sign, magstripe, and NFC/contactless cards or mobile wallets', the Lane 3000 as accepting 'EMV chip and pin, card swipes, NFC, and all contactless payments', the Lane 3600 with 'advanced NFC and contactless capabilities', the Moby 5500 with 'EMV chip, magstripe NFC/contactless cards, or mobile wallets', and the Verifone V400m, Adyen P400 Plus and Adyen AMS1 each as an 'EMV, contactless-enabled payment device'. Named shortfall, which is why this is not yes: wallet coverage is gateway-dependent, not universal. The full list of 'Mobile Wallets: ApplePay, GooglePay, Samsung' alongside types 'Manual Entry (MKE) / Swipe / Insert EMV / Contactless-Tap' appears only in the Revel Advantage INTERNATIONAL FAQ, covering the Adyen/Verifone estate. The general Payment Gateways & Processors Overview lists supported methods as 'Mobile Wallets (Apple Pay, etc.)' without naming Google Pay, and Revel's release notes record Apple Pay being added per gateway (FreedomPay at the 2.73 release). No document establishes Google Pay across all first-party terminals on the domestic TriPOS/FreedomPay estate. https://support.revelsystems.com/s/article/Revel-Advantage-International-FAQ · retrieved 2026-08-02 adversarially verified

payments-softpos-tap-to-pay differentiator

Still unresolved after searching the complete 693-article public help-centre mirror of support.revelsystems.com (captured 2026-08-04) for 'tap to pay', 'softpos' and phone-as-reader phrasing: zero hits. Every documented acceptance device is a dedicated reader or terminal (Moby 5500 Bluetooth reader, Ingenico Lane 3000/3600 and iSMP4, Verifone V400m, Adyen P400 Plus/AMS1), and the Payment Device Purchase Policy requires payment devices be purchased from Revel - but no article affirmatively states phone-only Tap to Pay is unsupported, so absence from the complete help centre is recorded as unknown rather than no.

payments-pay-at-table

The mobile hardware is documented: the Moby 5500 'provides a smaller, more cost-effective way to accept payments and is optimized for mobility', pairing over Bluetooth with the iPad POS to 'accept contactless, inserted, or swiped payments', and Revel documents an IPORT mobile order taker (MOT) case (added in 2.77) plus MOT operating practices (Revel Wi-Fi requirement, single-dock charging) for iPads running the full POS app - so orders can be taken and EMV/NFC payment accepted away from the counter, with the POS app's split-bill and tip-entry features available on that device. Named shortfall: no article documents a guest-facing tip prompt on the handheld flow - customer-facing tip prompts are documented only on the countertop CDS XT ('tip suggestions by thresholds'), on Adyen terminals of the international estate (tipping options configured via the Adyen portal), and in the SmartPay guest-phone flow - and no dedicated pay-at-the-table workflow article exists. https://support.revelsystems.com/s/article/Moby-5500 · retrieved 2026-08-04

payments-qr-guest-pay differentiator

'Revel SmartPay lets guests pay for their orders from their smartphones, either by scanning a QR code or by following a link sent through SMS'. Enabling 'Print QR Barcode on Receipt' prints a QR on the customer receipt copy; scanning it 'will take the customer to the order status page, where they can see details of their order' and, if enabled, add a tip via Suggested Tip Amounts prompts (e.g. 10/15/20%), then pay and receive a confirmation page. SmartPay is enabled per establishment in the Management Console for Adyen, TriPOS, or Revel Advantage FreedomPay; the SMS variant additionally requires the Twilio integration. Separately, Revel Smart Order is 'our fully contactless dine-in solution' where customers 'scan a QR code, order, and pay at the table, all without ever having to talk to a waiter' via Online Ordering XT. https://support.revelsystems.com/s/article/Revel-SmartPay · retrieved 2026-08-04

payments-tip-adjust

Both flows and the window are documented. Post-auth tip adjust: tips are added on the payment screen ('the tip amount can only be added after the initial order transaction has been processed') or in bulk on the Payments Waiting to Batch screen, whose Tip field is editable per transaction and searchable by Order ID, Transaction #, last-4 or cardholder name; the adjust window is explicit - tips must be entered before capture ('all tips must be entered before the auto capture time'; 'Make sure to add any tips prior to capturing your payments for the day'), after which a tip can only be run as a separate authorization via the Revel Advantage portal (bulk tip-adds not supported). On-device prompts: the Revel Advantage International FAQ documents 'adjusting tipping options on our payment terminals instead of the POS' (configured in the Adyen portal), and the CDS XT customer display supports 'tip suggestions by thresholds'. The batch screen is permission-gated (Batch Process permission), serving as the manager screen for unadjusted tips. https://support.revelsystems.com/s/article/How-to-Add-Credit-Card-Tips-on-the-Point-of-Sale-1582900280542 · retrieved 2026-08-04

payments-tip-pooling differentiator

Fully documented native module: Settings offer Tip In Based On Tips or Sales, Tip Share Even (allocated by hours worked) or Percentage by role, Treat Declared Tips As Total/Cash Only/Ignore, periodicity By Week/Day/Shift, and per-role tip-in %/tip-share % tables; the Schedules > Tip Pooling tool computes a per-employee breakdown (Declared Tips, Payment Tips, Tip In Amount, Tip Share Amount, Final Tips - 'their final take home tips and the amount that should be reported to the IRS') that a manager must submit, and a Final Tips column plus Tip Pool Results then appear on the Payroll report ('The saved results will be updated in the Payroll tab'). Points-based allocation is not offered, but the claim's enumerated methods (hours worked, sales, role percentage) are all covered and the allocation flows to payroll reporting. https://support.revelsystems.com/s/article/Tip-Pooling-1583150213556 · retrieved 2026-08-04

payments-offline-store-and-forward differentiator

Re-homed onto the live Salesforce URL and re-quoted - the previously recorded setting names were not the ones the article uses. Offline Payment Settings in the Management Console are 'Enable offline credit card payments', 'Request customer data when accept payment offline' and 'Show warning message before approve offline payment', with three configurable ceilings: 'Max amount for single offline payment', 'Max total amount for all unprocessed offline payments' ('Once your system reaches this threshold, you can only take any more offline credit card payments once the system is back online and all offline payments are processed') and 'Max threshold of total amount for all outstanding declined payments'. Store-and-forward is named as such in the Adyen section: 'Store-and-forward payments: the payment terminal approves payments without any verification.' Forwarding on reconnect is documented in the manual-batching article, where an Offline Payments tab holds transactions 'authorized but not yet validated by the system' with a Force control. Real limitations: 'Debit payments can't be accepted in Offline Mode' (Apple Pay does work), and per Revel POS Payments Overview 'Offline mode is not available for all payment integrations' - TriPOS and FreedomPay iFCC cannot toggle offline processing at all and must be forced by unplugging the ethernet cable, and Adyen requires Capture on Swipe plus vendor enablement. https://support.revelsystems.com/s/article/Offline-Mode-Always-On-Mode-1582898971418 · retrieved 2026-08-09 adversarially verified

payments-offline-decline-liability differentiator

Liability is stated in the vendor's own docs: 'Forcing offline payments is performed at the Merchant's risk. As with any payment taken offline, there is a risk of authorization failure based on card status and available funds which can only be determined once reprocessed when online', with enumerated risk factors borne by the merchant (chargebacks - 'your chances of winning are meager', credit card fraud, additional processing fees per attempted re-authorization). Post-reconnect failures are surfaced: the POS Operations tab includes a Declined Payments tab with a per-status counter, Retry All/Retry and Delete controls, and (since 2.79) an offline-replay UI showing replay status and daily replay count, with declined offline transactions automatically retried daily for up to 10 days; the Management Console Payments Summary report is the prescribed review ('It is a mandatory practice for merchants to check credit card transactions regularly'). https://support.revelsystems.com/s/article/Offline-Mode-Always-On-Mode-1582898971418 · retrieved 2026-08-04

payments-gift-cards

Gift card management listed; Givex is a monitored integration. Cross-location and online redemption unverified. https://status.revelsystems.com/ · retrieved 2026-08-01

payments-house-accounts

House accounts are first-class API resources -- HouseAccount, HouseAccountPayment and HouseAccountTransaction -- readable with patch/put (no post). The schema carries `balance` and `end_balance`, so the claim's running-balance conjunct is met. Shortfall re-measured on the new surface rather than carried over: the spec contains no credit-limit field and no statement or invoice generation operation, so two of the claim's three conjuncts are unmet and partial holds. https://oas-prod.s3.amazonaws.com/oas/2025.3.0/house_accounts_suite.yaml · retrieved 2026-08-10

payments-split-tender

The Split Bills article (already cited elsewhere in this record, support.revelsystems.com/s/article/Split-Bills-1582901435396, retrieved 2026-08-02) documents four named split modes - Split Evenly, Split Manually, Split By Item, and Split By Seat Number - each producing multiple separate checks from one order. That is real evidence a single order can be divided many ways. Named shortfall: the article documents splitting the ORDER into checks, not the settlement of ONE check across multiple tenders (cash+card, gift+card, etc.), and states no numeric cap on split count, so 'no hard cap below eight ways' cannot be confirmed either way. support.revelsystems.com is otherwise inaccessible this pass (401/JS shell), so a dedicated tender-splitting article could not be located. https://support.revelsystems.com/s/article/Split-Bills-1582901435396 · retrieved 2026-08-04

payments-refund-void-controls

The Split Bills article (support.revelsystems.com/s/article/Split-Bills-1582901435396, already cited in this record, retrieved 2026-08-02) states that 'Clear Split Bills' (merging split checks back together) 'requires a security PIN from an employee with refund permission' because it refunds all payments on the order - real evidence that refunds are gated behind a named permission. Named shortfall: this is the only documented authorization control found; void, discount, and no-sale specifically are not addressed in any page this pass could open, and no immutable audit log identifying the approving employee is described anywhere - only that a PIN is required at the point of action. support.revelsystems.com (help centre) returned either HTTP 401 (the /hc/en-us Zendesk-style path) or an unrendered client-side app shell with no server-delivered article text (the /s/article/ Salesforce help-site path, which shows only a loading spinner and a 'CSS Error' notice to every fetch method available this pass); reveluniversity.revelsystems.com returned HTTP 403; web.archive.org is blocked outright to the fetch tool; www.shift4.com/food-beverage, where revelsystems.com's own marketing pages now redirect, returned HTTP 403/429. https://support.revelsystems.com/s/article/Split-Bills-1582901435396 · retrieved 2026-08-04

payments-chargeback-tooling differentiator

The Revel Advantage merchant portal (portal.revelup.com) has a Disputes page (Dashboard > Disputes or Dashboard > Notifications) listing each chargeback with a Transaction Details screen and three actions - Respond (add contact name/note, attach documentation such as receipts, order information or a signed invoice as PDF, and Submit Response), Accept Liability, and Mark as Unread - plus configurable email Chargeback Alerts and per-dispute reason codes (Disputes > Dispute Details > Reason Code). Named shortfall: this dashboard exists only for Revel Advantage (in-house processing) merchants - users of other processors are pointed to the processor's own portal (e.g. Adyen Risk > Disputes) - and dispute evidence is manually uploaded PDF documentation, not assembled from the POS transaction record. https://support.revelsystems.com/s/article/Managing-Chargebacks-Disputes-in-Your-Revel-Advantage-Portal · retrieved 2026-08-04

payments-card-on-file differentiator

Documented only for online ordering: guests with an account on the Online Ordering site can check 'Save for future payments' at checkout - card entry happens on the Vantiv (Mercury) Hosted Checkout page, so the PAN is captured on the processor-hosted page rather than by the merchant - then reuse the stored card from a Choose Card drop-down on later orders and manage/remove cards under Payment Methods in their profile (cards can only be added at checkout, not from the profile). Named shortfall: the tutorial is explicitly 'for Mercury/ Vantiv hosted checkout' only, and no article documents reusing a stored card for phone orders or in-store POS payments, so the cross-channel half of the claim is not established. https://support.revelsystems.com/s/article/Saving-and-Changing-Credit-Card-Details-for-Online-Ordering-1583152074721 · retrieved 2026-08-04

payments-payout-timing differentiator

A next-day option exists but no deposit schedule is published: the Revel Advantage XT fee schedule lists a 'Next Day Funding Fee: Charges for receiving funds from transactions on the next business day, offering faster access to your funds. Not all clients or transactions are eligible for next-day funding', and the Batching Payments article states funding times 'can depend on your processor and other factors, such as your processor's standard funding schedule and any additional funding services you may have signed up for' - i.e. the standard deposit schedule itself is nowhere published. (On the Adyen international estate the Sales to Payouts report shows daily disbursement totals, but as reconciliation reporting, not a committed schedule; no same-day/instant option is documented.) https://support.revelsystems.com/s/article/Revel-Advantage-XT-Payment-Processing-Fees · retrieved 2026-08-04

payments-p2pe-pci4

Both halves are partly there: the FreedomPay setup article states 'FreedomPay fully protects the merchant environment with validated P2PE (Point-to-Point Encryption)', and the PCI FAQ states 'Revel Systems is fully PCI DSS compliant and can provide an attestation of compliance (AOC) upon request' via the customer success manager or risk-payments@revelsystems.com. Named shortfall: no document anywhere in the complete help centre states the PCI DSS version - '4.x'/'4.0' never appears in a PCI context - and validated P2PE is documented only on the FreedomPay gateway path; the Adyen estate is described only as using Adyen encryption on Revel-supplied devices, with no P2PE listing named. https://support.revelsystems.com/s/article/Revel-Advantage-FAQ-for-Merchant-PCI-Compliance · retrieved 2026-08-04

kitchen-station-routing

Re-homed onto the live Salesforce slug (the Zendesk article is customer-gated). Per-item routing is self-serve: in the Management Console under a product's Display/Print Options, 'enter the printer and/or display unit names you want to assign to this product. If a printer or display unit is assigned, that means the product will print or show when it's ordered and sent from the Point of Sale', and the same field is settable in bulk through Products > Import/Export > Products (Advanced export, Printers in Column K). Routing by order type is separately documented as 'Printer Setup by Dining Type' under Settings, which sends chosen dining options to the kitchen (https://support.revelsystems.com/s/article/How-to-Send-to-the-Kitchen-by-Dining-Option-1582898971400). Shortfall worth recording, though it does not defeat the claim: multi-station kitchen FLOWS - the ordered sequence of displays an item traverses - must be created by Revel Support ('Please contact the Support team to help to set up a kitchen flow'), after which the merchant may assign products to a flow and modify it without vendor involvement. https://support.revelsystems.com/s/article/How-to-assign-products-to-kitchen-printers-display-unit-KDS-1583149941086 · retrieved 2026-08-09 adversarially verified

kitchen-expo-consolidation

Re-evidenced; the sentence previously quoted is not present in the migrated help centre and is withdrawn. The Automated Expo Experience article states the consolidation and the completion condition in its own words: 'A single order may have food coming from several different kitchen prep/cook stations and the person standing at the expo window needs an easy way to know when food is ready', solved by 'Automatically printing a ticket from the expo view KDS when all items are marked done on the kitchen view KDS', with a companion setting 'Auto Close Tickets/Orders. This will automatically close an order on the expo screen once all items are completed.' Expo is a first-class configured role, not a view: Kitchen Views are assigned a 'Default Kitchen View: Line Expedite' or 'Line Kitchen', and 'You can set up multiple kitchen views that use one expedite view' (https://support.revelsystems.com/s/article/Kitchen-Flow-Bump-Feature-Setup-1582899129146). Products that need no station work can be flagged 'Auto Complete on KDS' so they still appear on the expo ticket. https://support.revelsystems.com/s/article/Automated-Expo-Experience · retrieved 2026-08-09 adversarially verified

kitchen-course-firing differentiator

Documented TSR Course Fire feature: 'Prompt for course' assigns each item to a course; courses are held and fired manually via Fire Next Course / Send Course on the POS ('To send each course to the kitchen separately... Tap Send to Kitchen: Tap Send Course'), with an optional 'Automatic course firing from Done on KDS' with a configurable delay that employees may override on the POS. Optimize KDS for Coursing 'will only send products to the KDS when that course is ready for preparation.' https://support.revelsystems.com/s/article/TSR-Course-Fire-1582902249374 · retrieved 2026-08-04

kitchen-prep-time-pacing differentiator

Prep/Cook Time article: a per-product 'Prep/Cook Time' field (minutes) is set in Products; 'The Use Prep Time to display items on KDS setting displays items with longer prep times on the KDS before items with shorter prep time, so all items will be ready and can go to the table together.' The Dynamic Prep Times option additionally shows the next item(s) immediately if an item finishes early rather than waiting out the set prep time. https://support.revelsystems.com/s/article/Prep-Cook-Time-1583152074715 · retrieved 2026-08-04

kitchen-order-throttling differentiator

Online ordering settings include 'Max number of online orders: Maximum number of online orders per time slot' and 'Online order time slot: Interval in minutes that defines available pickup/arrival/delivery time slots', which caps incoming digital orders per interval. Shortfall: the cap is a fixed configured number, not driven by live kitchen load or ticket times, and quoted prep times cannot be extended dynamically - the Online Ordering FAQ states 'The functionality for multiple prep times doesn't exist at this time.' https://support.revelsystems.com/s/article/Online-Ordering-Setting-Up-Online-Ordering · retrieved 2026-08-04

kitchen-channel-pause-propagation differentiator

DoorDash Marketplace integration: 'Item availability (86ing) for products / modifiers / ingredients' is supported and 'On the fly changes using webhooks can be utilized for instantaneous updates, including item availability'; store pause 'can be done on Revel via the management console setting Pause orders from DoorDash Marketplace'. Uber Eats onboarding: 'Item availability feature can be utilized to update product inventory on Uber Eats. The Item availability Webhook needs to be enabled.' 86ing is performed from the POS Item Availability feature; group-combo 86ing to DoorDash was not yet supported at time of writing. https://support.revelsystems.com/s/article/DoorDash-Marketplace · retrieved 2026-08-04

kitchen-order-ready-callback differentiator

Searched the complete 693-article public help-centre mirror (retrieved 2026-08-04) for 'order ready', 'readiness', 'mark ready', courier/dispatch terms, and the full DoorDash Marketplace and UberEats Onboarding integration articles. The DoorDash article's detailed supported/unsupported feature enumeration contains no order-ready or KDS-bump status sync to the marketplace, and states POS-side order modifications 'will not update the order on DoorDash's end', suggesting order flow is one-way - but no article addresses readiness callbacks either way, so this is not positive evidence of absence. The KDS 'SMS on Order Ready' feature is guest-facing (Twilio), not a marketplace callback. developer.revelsystems.com guide pages checked 2026-08-05 cover developer policy only; the /reference API explorer is client-rendered and unreadable, so an API-level status webhook could not be confirmed or excluded.

kitchen-bump-bar-hardware

Withdrawing the previous note's claim that no supported-hardware list exists - it does. Revel's Active Supported Hardware page ('all the active and supported hardware by Revel Systems') lists a Bump Bar under Screens & Additional Peripherals: 'Protect your kitchen display system (KDS) screen with a 20-key bump bar. Boasting a sealed membrane input surface, this durable bump bar enables your staff to update orders on the KDS without touching the screen directly', connection 'Plug and Play', with a vendor-hosted spec sheet at revelup-techpubs.s3.us-west-2.amazonaws.com/support/hc/en-us/000002619/bumpbar.pdf. Physical bump bars are also treated as standard equipment in the KDS setup documentation, which includes an 'Updating Your Bump Bar Layout' procedure and ships a printable key layout (https://support.revelsystems.com/s/article/Kitchen-Flow-Bump-Feature-Setup-1582899129146). Honest limit: it is one Revel-branded 20-key SKU rather than a compatibility matrix of third-party models. https://support.revelsystems.com/s/article/Active-Supported-Hardware · retrieved 2026-08-09 adversarially verified

kitchen-all-day-counts

Production View on the KDS: 'shows the queued orders on the left and the individual products or tags from those order on the right... an easy-to-read view of ordered items (and their quantities)' as 'a running list of products'; selecting Tagged shows 'tags of how many products and modifiers are in the current orders', covering modifier-level counts. Voided items are excluded from production totals. Configured per KDS under Establishment > Kitchen Views > Kitchen > Production View. https://support.revelsystems.com/s/article/Production-View-on-the-KDS-1582899129813 · retrieved 2026-08-04

kitchen-sla-alerts

Colored Timing on Tile Expedite View: per Kitchen View, 'enter a time in HH:MM:SS... to indicate when you want the order to turn green, yellow, or red', with configurable Reset Expedite Timers behavior (never / after each item / after all items / from initial item); timers are independent per view and can be set from the Management Console or on the KDS itself. Visual color escalation only - no audible alert is documented (claim accepts visual and/or audible). https://support.revelsystems.com/s/article/Colored-Timing-on-Tile-Expedite-View-1582899129853 · retrieved 2026-08-04

kitchen-printer-fallback differentiator

Auto Redirect (Printing Failover) provides 'temporary and automatically redirect a receipt from non-working or busy printer', with an ordered list of failover printers retried in a loop 3 times. Shortfall: it works for Epson ePOS LAN printers only, only between matching printer models and types, and 'is configured per POS and configuration is not shared between POS'; there is no documented automatic failover for a KDS screen going offline - screen/other-printer redirection is a manual Redirect setting per station that must be re-established after app updates. https://support.revelsystems.com/s/article/Printing-Failover · retrieved 2026-08-04

kitchen-offline-operation differentiator

Outage best-practices article: 'When Server is down, you'll still be able to access the following functions: Create and close orders... Print to kitchen and receipt printers (ethernet or BT connected); Use CDS & KDS.' During an ISP/Network outage, 'Create and close orders' and 'Print to kitchen and receipt printers (ethernet or BT connected)' remain available - Revel runs on the establishment's local network, with POS and KDS devices on static local IPs (192.168.22.x). https://support.revelsystems.com/s/article/outage · retrieved 2026-08-04

kitchen-item-build-screens differentiator

KDS Styles Overview: as of 2.79 a 'list view option for modifiers... will display all modifiers for the item in a list' (full modifier breakout), enabled under Establishments > Peripherals > Kitchen Views > [Device] > Tile Expedite > Modifier List View. KDS Tags additionally let stations show per-component tags on products and modifiers - 'useful for employees who are responsible for only one section of the kitchen line and only need to know what items they need to prepare' - including quantity tagging (e.g., the burger tag added twice for a double hamburger). Recipe-step display is not documented; the claim accepts full modifier breakout. https://support.revelsystems.com/s/article/KDS-Styles-Overview-1582899129825 · retrieved 2026-08-04

kitchen-pizza-fractional-display differentiator

Split Modifiers are documented: 'On the bottom of the modifier pop-up, tap First Half or Second Half. Tap a modifier to add to that half of the pizza', with split or full pricing options ('a pepperoni topping priced at $.50 will ring up as $.25 if a customer orders pepperoni on only half'). Shortfall: only halves (First Half / Second Half) are supported - no quarters or arbitrary sections - and the kitchen ticket/KDS shows the half assignment as text labels; no graphical make-line rendering is documented. https://support.revelsystems.com/s/article/Advanced-Modifier-Features-1583154976185 · retrieved 2026-08-04

kitchen-recall-refire

'Revel allows items or entire orders to be reprinted to the kitchen, if necessary. When reprinted, the receipt will indicate that it is a reprint' - gated by the Manual Receipt Print permission, with order lookup by Order ID, customer name, card, or date range so nothing is re-rung. On the KDS side, completed orders can be recalled: Tile Expo has a Recall Mode ('you no longer need to recall the order to get the reprint - you can instead simply go into Recall Mode, press the Print button'), and the Speed of Service report explicitly accounts for recalled orders. https://support.revelsystems.com/s/article/How-to-Reprint-to-Kitchen-Receipts-1582901899083 · retrieved 2026-08-04

kitchen-order-modification-alerts differentiator

KDS Styles Overview, 'Send New Tickets on Send After the Order Reopened/Modified': 'as a new item is added to an existing order, a sub ticket will be created... labelled with the original order number, and consist of a ticket count (e.g., 1235-1, 1235-2, 1235-3). This enhancement will ensure your kitchen staff can easily view new items, so that nothing is missed.' Shortfall: additions surface as separate sub-tickets rather than flagged changes on the live ticket, and only additions are covered - the article states 'After an order has been sent, it cannot be modified'; removed/changed items are not flagged at item level (voided orders show red only in the Expedite Status section). https://support.revelsystems.com/s/article/KDS-Styles-Overview-1582899129825 · retrieved 2026-08-04

kitchen-guest-ready-notification differentiator

'Send SMS on Order Ready in the Kitchen' sends a customizable SMS 'on Done or Complete on an Expo KDS', filterable by order type - but 'this feature requires a Twilio integration.' The branded Order Ready XT split-screen preparing/ready board for Android TV 'requires a paid subscription.' Included without extra purchase is only the basic Order Display KDS style ('Normally used as a customer display to show customers when their order is completed'). Shortfall: SMS depends on a third-party Twilio account and the flagship status board is a paid add-on; no app push exists. https://support.revelsystems.com/s/article/SMS-on-Order-Ready-in-the-Kitchen · retrieved 2026-08-04

kitchen-waste-logging

Product Setup on the Point of Sale lets staff 'update quantities for Received, Actual and Wasted amounts... Use Wasted if a product has been broken or expired to deduct from inventory numbers', so waste entry depletes inventory from the front-of-house device. Shortfall: entry happens in the POS Product Setup screen (or the separate Revel Inventory mobile app), not at the kitchen/KDS screen, and there are no reason codes - only a single Wasted quantity field. https://support.revelsystems.com/s/article/How-to-Use-Product-Setup-on-the-Point-of-Sale-1582899333978 · retrieved 2026-08-04

kitchen-speed-of-service-reporting

The Speed of Service report 'records the time an item spent on the Kitchen Display Screen (KDS) until the time it was delivered to the customer', with columns for Start Time, KDS Complete, Expedite Complete, Time on KDS, Time on Expedite, and Total Kitchen Time, viewable by item or order and filterable by Employee, Product Class, and custom date/time range (requires In-Progress Mode on the KDS). Shortfall: no percentile statistics and no slicing by daypart, station, or order channel is documented; the report itself warns that recalled orders inflate reported KDS times. https://support.revelsystems.com/s/article/Speed-of-Service-Report-1583149670649 · retrieved 2026-08-04

kitchen-prep-forecasting

Item Tracking / Product Forecasting 'allows users to plan for how many of those items to have prepared and ready before the customer orders': forecast prep amounts are computed from a configurable number of weeks of Net or Gross sales history per time-slot interval, and scheduled prep reports print automatically to a designated kitchen printer - Start of Day Report (X minutes before open, with per-time-slot forecast totals), Interval Prep Reports (every 15 min to 4 hours, with prior-hour and cumulative totals and next-slot forecast), and a Closing Prep Report summarizing 'what will need to be prepared for the next day.' https://support.revelsystems.com/s/article/Item-Tracking-Product-Forecasting-1583149672017 · retrieved 2026-08-04

delivery-driver-roster

A Driver employee role exists and gates access to the Delivery XT Agent app; Manager/Dispatcher is a distinct role gating the Dispatch app. Driver is a first-class entity, not a workaround. https://apps.apple.com/us/app/revel-delivery-xt-dispatch/id1531919449 · retrieved 2026-08-01 adversarially verified

delivery-dispatch-board

Revel ships Delivery XT: a Dispatch iPad app (Manager/Dispatcher role only) giving a single dashboard to assign orders, estimate delivery times and track drivers, plus a Driver Agent app on iOS and Android. Published by 'Revel Systems INC' on the App Store, last updated 2025-08-25, and both 'Delivery XT' and 'Driver XT' are live monitored components on status.revelsystems.com as of 2026-08-01. Material caveat the dossier could not flag because it missed the product entirely: Delivery XT is a separate add-on module and is powered by Captain AI, so it is white-labelled rather than wholly in-hous https://apps.apple.com/us/app/revel-delivery-xt-dispatch/id1531919449 · retrieved 2026-08-01 adversarially verified

delivery-route-map differentiator

Delivery Management's Map View shows all orders as geocoded pins with ready-time/distance detail and 'the best route'; a Delivery Optimization setting recommends which unassigned orders a driver should batch into their run (green flag, with 'Max time between addresses' and 'Max wait for next order' fields), and driver check-out can print/email 'Order & Route Info' with directions. Shortfall: explicit stop-sequencing/turn-order optimization within a multi-stop run is never documented, and the newer Delivery XT dispatch app documents manual assignment only ('The system does not assign drivers automatically') with per-order navigation via Google/Apple/Waze. https://support.revelsystems.com/s/article/Delivery-Management-Written-Instructions · retrieved 2026-08-04

delivery-driver-tracking differentiator

Live driver tracking is the headline documented function — 'Watch your drivers move around the city' / 'Know when they are returning' — with in-app navigation for the driver. https://apps.apple.com/us/app/revel-delivery-xt-dispatch/id1531919449 · retrieved 2026-08-01 adversarially verified

delivery-zones-polygon differentiator

'Delivery area by GeoJson' — a GeoJSON string describing the delivery area, drawn with tools such as geojson.io and pasted into the Management Console Delivery settings; 'Only polygon strings are supported. Revel does NOT support line strings.' A postcode-list alternative also exists, and zone-based delivery service fees use additional GeoJSON polygon zones. https://support.revelsystems.com/s/article/Delivery-Management-Settings-1583149409705 · retrieved 2026-08-04

delivery-zone-pricing

Zone-based delivery fees are documented: draw GeoJSON zones, attach each set of zones to its own service fee (e.g. all $7.99 zones on one fee, $9.99 zones on another), and fees are 'assessed according to the zone that includes the customer's address' (where zones overlap, the lower fee is charged); distance-based fee tiers (e.g. 'Delivery Fee 5-10 Miles') auto-apply by the Delivery dining type. Shortfall: per-zone order minimums and per-zone quoted promise times are not documented — order minimums exist only as global Online Ordering 'Order Rules', and delivery-time estimation is prep-plus-drive-time based, not per zone. https://support.revelsystems.com/s/article/Delivery-Zone-Service-Fees · retrieved 2026-08-04

delivery-address-validation

Delivery-area checks run at address entry: with 'Delivery area by post codes', 'The POS will check delivery addresses against the list of acceptable post codes. If the post code is not found, the system will warn the user that delivery cannot be made to this address'; with a GeoJSON area, 'an error will occur when trying to enter in a customer's Delivery address' outside it. The Driver Manager role holds an explicit permission to 'approve a delivery to an address outside the approved delivery area', and delivery mileage defaults come from the Google Maps service. https://support.revelsystems.com/s/article/Delivery-Management-Settings-1583149409705 · retrieved 2026-08-04

delivery-driver-comp differentiator

Per-run mileage is captured at driver check-in ('Enter the mileage value in the Enter Total Mileage of Delivery pop-up' — default value is the Google Maps trip distance), credit-card tips are entered per driver at check-in, and a Delivery Drivers report (Reports > Other Reports > Delivery Drivers) holds 'total trips, delivery time, cash payments, tips, etc.'. Shortfall: no per-delivery flat reimbursement rate is documented, and no payroll export separating reimbursement lines from wage lines is documented. https://support.revelsystems.com/s/article/Delivery-Management-Written-Instructions · retrieved 2026-08-04

delivery-cash-reconcile

Drivers carry per-employee Virtual Tills; check-in prompts credit-card tip entry, closing unpaid orders to cash, and mileage; the End Shift process counts the till (sum total or per-bill quantities), shows a checkout summary, submits payment for all open orders ('close to cash'), and prints a driver Sales Summary plus manager/driver-signed clock-out receipts. The Tills Report Variance column is the per-till over/short: 'Positive numbers mean a cash overage, negative numbers means less cash than expected' (Tills Reports, https://support.revelsystems.com/s/article/Tills-Reports-1582899801519). https://support.revelsystems.com/s/article/Delivery-Management-Written-Instructions · retrieved 2026-08-04

delivery-daas-dispatch

'Driver XT Powered by DoorDash' natively hands first-party delivery orders to DoorDash Drive: after checkout 'a request for a DoorDash driver at your location will be sent to DoorDash', the courier tracking link is 'available in the sidebar for each order' on the POS, and 'Delivery fee and driver tip do go into Revel and DoorDash reporting'. Shortfalls: dispatch fires only for orders placed on the Online Ordering XT site (OOXT subscription required — 'DoorDash Drive cannot operate without it'), delivery radius is capped at 5 miles ('Max Delivery distance' must be 1-5), it 'must not' be combined with Delivery XT, and it is QSR/TSR-only in US/CA/AU. No Uber Direct, Nash or Relay equivalent is documented. https://support.revelsystems.com/s/article/Driver-XT · retrieved 2026-08-04

delivery-daas-fallback differentiator

Documented mutual exclusivity rules out hybrid dispatch: Driver XT (DoorDash Drive) requirements state 'Must not use Delivery XT', so the in-house driver product and the DaaS courier product cannot run together, and under Driver XT every OOXT delivery order is sent to DoorDash with no overflow rules. Conversely, Delivery XT documents 'All drivers must be assigned by the dispatcher or manager. The system does not assign drivers automatically', and both marketplace integrations state self-delivery is not supported. No overflow/fallback rule engine (driver-unavailable, out-of-zone, or wait-threshold) appears anywhere in the complete public help centre. https://support.revelsystems.com/s/article/Driver-XT · retrieved 2026-08-04

delivery-3p-direct-integration differentiator

'Revel now offers direct integration with DoorDash Marketplace, eliminating the need for middleware' ($20/month/establishment subscription, 'no additional transaction or order fees from Revel') and 'direct integration with Uber Eats, eliminating the need for middleware' (UberEats-Onboarding, which even instructs ex-middleware merchants to return their Uber Eats tablet). Shortfall: Grubhub is not among them — zero Grubhub mentions across the complete 693-article public help centre; marketplaces other than DoorDash and Uber Eats route through Revel's online-ordering partner integrations. https://support.revelsystems.com/s/article/DoorDash-Marketplace · retrieved 2026-08-04

delivery-3p-injection

DoorDash Marketplace orders sync to the POS in real time as normal tickets under the 'DD Marketplace' dining option: 'a notification will appear at the top of your point of sale screen', orders arrive fully paid ($0.00 due), Auto-close paid orders closes them automatically, the 'Print online orders' setting fires them to printers, and special requests display on the KDS; no tablet re-keying or manual accept step is part of the documented flow. Uber Eats orders likewise 'arrive to POS fully paid under the Uber Eats dining option'. https://support.revelsystems.com/s/article/DoorDash-Marketplace · retrieved 2026-08-04

delivery-menu-push

'With this integration Revel becomes the source of truth for all menus and products.' Custom multi-channel menus publish products, descriptions, product/modifier images, per-modifier pricing and a per-menu '3rd Party Price Upcharge (%)' markup (applied to delivery, not pickup) from the Revel Management Console to DoorDash and Uber Eats; DoorDash sync is triggered by 'Push Changes' (manual, verified by DoorDash within minutes, up to 2 hours), Uber Eats updates automatically once per 24 hours or on demand via the 'Menu Changed' webhook. Products and menus 'should only be created and managed in Revel'. https://support.revelsystems.com/s/article/DoorDash-Marketplace · retrieved 2026-08-04

delivery-86-sync

Item availability (86ing) syncs for products, modifiers and ingredients: 'On the fly changes using webhooks can be utilized for instantaneous updates, including item availability'; 'Items marked as unavailable on the POS will not be displayed on DoorDash. Once the item is marked as available again on the POS, then it will be displayed on DoorDash' — even removing an in-cart item mid-checkout. Uber Eats supports the same via the Item Availability webhook, and zero/negative-stock items are withheld on both channels. Caveat: 86ing group combo products is not yet supported on DoorDash. https://support.revelsystems.com/s/article/DoorDash-Marketplace · retrieved 2026-08-04

delivery-store-pause

A Management Console setting 'Pause orders from DoorDash Marketplace' pauses the store from Revel's side, documented as an alternative to the DoorDash merchant portal or tablet. Shortfalls: no timed auto-reactivation is documented (and while the setting is enabled, menu changes stop syncing to DoorDash until it is disabled); no equivalent Revel-side pause is documented for Uber Eats; and the control lives in the Management Console rather than on the POS station. https://support.revelsystems.com/s/article/DoorDash-Marketplace · retrieved 2026-08-04

delivery-3p-reconciliation differentiator

The data a payout reconciliation needs is documented as absent from Revel: 'Any fees collected by DoorDash will not be reported to Revel: Delivery fee, Dasher tips, Other fees collected by DoorDash'; the Uber Eats article states the same ('Any Fees collected by Uber Eats will not be reported to Revel (Delivery fee, tips, Tax on delivery fee, other fees)'); DoorDash-applied discounts 'will not report the discount in Revel', refunds/voids 'will need to be modified in both systems for reports to be accurate', and merchants are directed to the marketplace portals 'for more robust reporting on DoorDash specific orders and other DoorDash related data'. Revel reporting shows 3P sales via the DD Marketplace/Uber Eats order and payment types only — no commission, marketing-fee or payout-matching reconciliation report exists. https://support.revelsystems.com/s/article/DoorDash-Marketplace · retrieved 2026-08-04

delivery-injection-error-visibility differentiator

Failure modes are documented as silent on the operator side: DoorDash orders containing out-of-stock items 'will not be processed, will be canceled after submission, and will not show up on the POS or in reports'; orders containing products created manually in DoorDash 'will cause the order to fail and not sync to Revel'; Uber Eats orders violating the global order rules 'will get canceled after' checkout. No operator-facing integration-health view, per-channel connection status, or injection-failure alert is documented anywhere in the complete 693-article help centre — the only failure surface is the developer-facing webhook message-log API noted in the prior pass. https://support.revelsystems.com/s/article/DoorDash-Marketplace · retrieved 2026-08-04

delivery-tracking-page

A customer tracking link showing order status and driver proximity is documented as part of Delivery XT. https://apps.apple.com/us/app/revel-delivery-xt-dispatch/id1531919449 · retrieved 2026-08-01 adversarially verified

delivery-promise-time differentiator

UPGRADE TO PARTIAL ONLY (schema lacks that verdict). Delivery time estimation is a documented Delivery XT function; the estimation model, whether promise times feed the POS/KDS, and load-based adjustment are undocumented. https://apps.apple.com/us/app/revel-delivery-xt-dispatch/id1531919449 · retrieved 2026-08-01 adversarially verified

delivery-offline-behavior

Re-read the Offline Mode article end to end in the complete help-centre mirror (Googlebot capture 2026-08-04). Its declared scope is transaction processing: 'Offline Mode allows you to process transactions while any of the three are experiencing an outage' (ISP, management console server, payment gateway). Its contents are POS Offline Status Notification Settings, Offline Payment Settings (enable offline credit card payments, max single offline payment, max total unprocessed, max declined threshold), Offline Tills Management, and ISP outage procedures per gateway, ending with 'ADDITIONAL NOTES: Apple Pay works in Offline Mode. Debit payments can't be accepted in Offline Mode.' Nowhere does it assert that it lists everything that does or does not function offline, so it is not an exhaustive enumeration - it is a payments guide. Searches of the 693-article mirror for offline, outage, delivery, driver and dispatch turn up no article documenting whether cash delivery orders, driver assignment or driver settlement continue during an outage, but that is a help-centre search returning nothing, and the mirror covers only the public help centre - Revel University and the Captain AI / Delivery XT partner portal documentation are outside it. Whether Revel documents delivery offline behavior anywhere cannot be settled from what is retrievable. adversarially verified

digital-first-party-web

Weborders is its own suite: /specialresources/cart/calculate, /validate and /submit alongside /weborders/menu/, products, modifiers, attributes and product_categories (8 GET, 3 POST). Orders written this way land in the POS. Own-domain branding and commission-free terms remain unverified -- an OAS spec is a technical reference and establishes neither, so partial holds. https://oas-prod.s3.amazonaws.com/oas/2025.3.0/weborders_suite.yaml · retrieved 2026-08-10

digital-menu-single-source

Online menus are built in Products > Custom Menus from the same product catalog as the POS ('control exactly which products are available online and when they're available without altering your main menu'), so items are defined once; but a custom online menu is a required separate build step before launching online ordering, newly added products must be explicitly added to the custom menu 'even if the product is in a category that's already included', and changes are pushed manually via Settings > Online Ordering Settings > Refresh Menu rather than propagating automatically. https://support.revelsystems.com/s/article/Online-Ordering-Creating-a-Custom-Online-Menu · retrieved 2026-08-04

digital-native-app differentiator

The Custom Commerce App is a Revel-built, restaurant-branded native ordering app 'supported on both iOS and Android platforms', submitted to the App Store/Play Store under the merchant's own Apple ID, with Revel Loyalty, Revel Gift Card, customer profiles, order history and reorder, stored tokenized cards, and Apple Pay (via Stripe). However the article opens: 'The Custom Commerce App is not currently available for purchase' — it exists only for existing users, so new merchants cannot buy a branded native app from Revel. https://support.revelsystems.com/s/article/Custom-Commerce-App-FAQ-1582893045686 · retrieved 2026-08-04

digital-account-saved-payment

Online Ordering XT accounts save name/email/phone and multiple delivery addresses (auto-synced to the CRM, pre-filled at checkout), and guests can check 'Save for future payments' to store a tokenized card and later pick it from a Choose Card drop-down — but the card-saving tutorial states 'This tutorial is for Mercury/Vantiv hosted checkout', so saved cards are gateway-dependent, and one-tap reorder of a previous order is documented only in the discontinued Custom Commerce App, not in the OO XT web flow. https://support.revelsystems.com/s/article/Saving-and-Changing-Credit-Card-Details-for-Online-Ordering-1583152074721 · retrieved 2026-08-04

digital-upsell-engine differentiator

Kiosk XT documents a rules-based upsell: after item/modifier selection 'a Make it a combo! window will appear. It will show what's included in the combo and the price', with Yes/No choice. Online Ordering XT documents group combos as orderable products but no upsell/cross-sell prompt at checkout, and no algorithmic recommendations or attach-rate reporting on suggestions is documented anywhere in the help centre. https://support.revelsystems.com/s/article/Kiosk-XT · retrieved 2026-08-04

digital-scheduled-pacing

Online Ordering Order Rules include 'Max number of online orders: Maximum number of online orders per time slot', a configurable 'Online order time slot' interval ('if you set this to 5 - you will have time slots available every 5 minutes'), 'Max date window for online ordering' (days orders can be placed in advance), estimated order preparation time, and max products/transaction-value caps; the Online Ordering XT checkout surfaces errors when 'selected order time is no longer available, or order maximum has been reached', i.e. saturated slots close to further orders. https://support.revelsystems.com/s/article/Online-Ordering-Setting-Up-Online-Ordering · retrieved 2026-08-04

digital-fulfillment-modes

One Online Ordering XT flow covers pickup (Walk Up), curbside (Drive Up with vehicle make/type/color capture and an order-status link the guest uses 'to notify your establishment when they've arrived', badging the POS) and delivery (with configurable delivery constraints, estimated prep time, and tax/service-fee options). Dine-in QR ordering exists but only as the separately activated Revel Smart Order mode, which 'cannot change order dining option', cannot use customer accounts, and must share the OO XT processor/branding — not the same single flow. https://support.revelsystems.com/s/article/Pickup-Ordering · retrieved 2026-08-04

digital-qr-table

Revel Smart Order is 'our fully contactless dine-in solution... scan a QR code, order, and pay at the table' via per-table QR codes generated in the Management Console, and Revel SmartPay lets guests scan a receipt QR code or follow an SMS link to view an existing POS order's status and pay it with suggested tip prompts. However Smart Order places a new online order rather than attaching to an open server check, and guest-side check splitting is not documented for either flow. https://support.revelsystems.com/s/article/Smart-Order · retrieved 2026-08-04

digital-kiosk differentiator

Kiosk XT is a brandable self-order kiosk driven by the same Management Console products, modifier classes (including split modifiers with the same 'Charge Full Price for Split Modifiers' pricing rules), min/max modifier restrictions, group and upsell combos, discount codes and suggested-tip settings as the POS, with card payment via pin pad ('the kiosk will connect to card swipe, prompt you to follow the directions on the pin pad'). Shortfalls: payment processors limited to Vantiv/TriPOS and FreedomPay; no accessibility (ADA/WCAG) compliance for the kiosk UI is documented; and it does not support customer accounts, CRM data, or loyalty programs other than Revel Loyalty and Punchh. https://support.revelsystems.com/s/article/Kiosk-XT · retrieved 2026-08-04

digital-group-ordering

Unresolved after searching the complete 693-article public help-centre mirror (support.revelsystems.com, captured 2026-08-04) for 'group order', 'shareable link', and shared-cart concepts. The only 'group' feature documented is Group Combos (a menu bundle product on Kiosk XT and Online Ordering XT), which is unrelated to multi-participant ordering. No article describes a shareable link letting multiple participants add items to one order under a spend cap. Absence from the complete public help centre is suggestive but is not positive evidence of absence, so this stays unknown.

digital-catering-portal differentiator

Catering exists as a distinct POS dining option scheduled to a future day/time with delivery-range validation, and can be billed to a House Account so 'a customer or company with multiple orders, can be billed in one lump sum'; separately, the online ordering Order Rule 'Future Orders shall be created as invoices' makes payments on far-out orders come in 'marked as deposits'. However no guest-facing catering ordering portal, separate catering menu/minimums, lead-time rules, or quote/proposal workflow is documented. https://support.revelsystems.com/s/article/Catering-Overview-1583149409691 · retrieved 2026-08-04

digital-voice-ai-phone differentiator

Unresolved after searching the complete 693-article public help-centre mirror (support.revelsystems.com, captured 2026-08-04) for 'voice', 'AI', 'phone order', and 'call center'. Phone ordering is documented as staff-taken, aided by a Caller ID hardware integration ('Caller ID helps you manage phone orders by recognizing customers'); the only AI-branded product in the help centre is Captain AI, the Delivery XT routing/analytics portal. No AI voice phone-ordering product or named certified partner is documented, but the docs do not affirmatively rule one out, so this stays unknown rather than no.

digital-drivethru-ai

Unresolved after searching the complete 693-article public help-centre mirror (support.revelsystems.com, captured 2026-08-04) for 'drive thru', 'drive through', 'voice', and 'AI'. The 'Revel Drive Through' article documents a staff-operated drive-thru: employee-taken orders on the POS with vehicle-data prompts and a dedicated drive-thru order queue. No AI voice ordering at the lane is documented anywhere, but the article does not enumerate order-capture methods exhaustively, so absence of evidence keeps this unknown rather than no.

digital-sms-ordering

Unresolved after searching the complete 693-article public help-centre mirror (support.revelsystems.com, captured 2026-08-04) for 'SMS', 'text to order', 'text a link', and 'chat'. All documented SMS is either one-way status notification (Twilio-powered pickup confirmation/in-progress/order-ready messages) or Revel SmartPay, which texts a payment link for an order already rung up on the POS — neither is conversational SMS/chat ordering or reordering that lands an order in the POS. No text-to-order capability is documented, but absence from the help centre alone is not positive evidence of absence.

digital-google-order differentiator

Unresolved after searching the complete 693-article public help-centre mirror (support.revelsystems.com, captured 2026-08-04) for 'Order with Google', 'Google Business', and 'Google'. The only Google references are Google Play app distribution and Google Maps navigation in the Delivery XT Agent app. Nothing documents provisioning the first-party ordering link to a Google Business Profile as an ordering option. Absence from the complete public help centre keeps this unknown, not no.

digital-apple-business-connect

Unresolved after searching the complete 693-article public help-centre mirror (support.revelsystems.com, captured 2026-08-04) for 'Apple Business Connect' and 'Apple Maps'. The only Apple Maps reference is driver navigation in the Delivery XT Agent app; Apple references otherwise concern Apple Pay and App Store distribution. No Apple Maps place-card 'Order Food' action placement is documented. Absence from the complete public help centre keeps this unknown, not no.

digital-loyalty-attach

Loyalty XT (powered by Como) redemption works inside the Online Ordering XT checkout: a 'Pay with loyalty' payment method spends 'the points that they have accumulated with Como' against the same Como member account used in-store (customer must be logged in and phone-confirmed with Como; SMS 2FA at redemption). Shortfalls: points accrual is documented only for the in-store POS/CDS flow, not for online orders; and the Smart Order QR dine-in flow 'cannot use a loyalty integration'. https://support.revelsystems.com/s/article/Loyalty-XT · retrieved 2026-08-04

digital-subscriptions

Unresolved after searching the complete 693-article public help-centre mirror (support.revelsystems.com, captured 2026-08-04) for 'subscription', 'membership', and 'recurring billing'. All hits concern merchant-side billing (ACH autopay of Revel's own invoices in the Billing Portal) or Como's merchant-side Marketing Communications subscription; Loyalty XT punch cards are earn-based, not paid memberships. No guest-facing recurring-billing subscription or paid loyalty tier is documented. Absence from the complete public help centre keeps this unknown, not no.

digital-promo-parity

Discounts and discount codes are defined once in Products > Discounts and redeemable on the POS (scan or manual entry), on Kiosk XT ('a discount code must be set up in the Management Console under Products>Discounts>Details>Discount Code Enabled'), and in online ordering via the Promotion Code field at checkout. Parity is not identical: 'At this time, Revel does not support the Apply Multiple Times setting in web ordering', discount codes are single-establishment, and loyalty offer support differs by channel (Kiosk XT supports only Revel Loyalty and Punchh; Smart Order supports no loyalty integration). https://support.revelsystems.com/s/article/Discount-Codes-1583151656831 · retrieved 2026-08-04

digital-guest-data-ownership differentiator

Customer is readable AND writable (11 GET, 5 POST, 5 PATCH, 5 PUT, 2 DELETE), so bulk extraction is technically possible. What the claim actually asks for -- that the vendor DOCUMENTS operator ownership and fee-free bulk export -- is established by no live surface: the spec is silent on ownership and on fees. Partial holds. https://oas-prod.s3.amazonaws.com/oas/2025.3.0/customers_suite.yaml · retrieved 2026-08-10

digital-checkout-pci-sca

Online ordering card entry is documented as gateway-hosted ('You will be brought to the Vantiv Hosted Checkout page, enter your credit card information'), and the v2.73 release added AVS plus 3DS to Online Ordering XT — but with the stated limit '3DS feature is only available for merchants using FreedomPay with Online Ordering XT in the United Kingdom'. No PCI DSS 4.0 attestation or client-side script-integrity documentation for the digital checkout was found in the help centre. https://support.revelsystems.com/s/article/Version-2-73 · retrieved 2026-08-04

digital-surcharge-transparency differentiator

Credit-card surcharges are configurable and reach digital channels: the v2.73 release notes state 'Surcharges will now be displayed at checkout in OOXT' (guest-facing disclosure), and Revel's surcharging FAQ confirms online/CNP orders 'are acceptable options for surcharging as long as disclosures and/or signage are shared clearly'. Shortfall: the FAQ repeatedly places jurisdiction and card-brand compliance on the merchant ('it is your responsibility as a business owner to stay current with the latest compliance rules') — no automatic blocking in prohibited states or for prohibited card types is documented, and dual pricing is not documented for digital channels. https://support.revelsystems.com/s/article/FAQ-Credit-Card-Surcharging · retrieved 2026-08-04

guest-loyalty-unified-profile

One CRM across Management Console, POS and CDS; dedup is via an 'Enforce Customer Uniqueness' (phone/email) setting, but 'If you would like to set up customer uniqueness, contact Revel Support' — it is not operator-self-serve, and detailed merge behavior is only summarized (v2.78 change log: 'Improved CRM uniqueness and record merge functionality for online ordering customers'). Kiosk XT explicitly 'does not currently support ... Creation of customer accounts [or] CRM data (login, order history)' — kiosk guests get loyalty lookup/redeem only, not a full CRM identity. https://support.revelsystems.com/s/article/CRM-Automated-Server-Search · retrieved 2026-08-04

guest-loyalty-thirdparty-identity-attach differentiator

Splits by marketplace, and the vendor documents both halves. Uber Eats works: the Uber Eats Onboarding article's CRM row states 'A CRM profile will be created for each Uber Eats order in the following format: First name, First letter of Last name, Phone number, Email format: UberSupport<last5digitsofUberOrderID>@uber.com', and the What to Expect - Point of Sale section confirms Uber Eats orders 'have a unique customer linked to them. The customer name and phone number will be the actual customers contact information while the email is going to be in the UberSupport(last5digitsofUberOrderID)@uber.com format'. A real per-order native CRM profile carrying the guest's actual phone number is usable guest identity. Shortfall, and the reason this is not yes: DoorDash Marketplace behaves the opposite way. Its integration article states 'Only the customer's first name and first letter of their last name are synced to Revel and are reported in the Call Name field', 'All DDM orders will have the same phone number and email address' (the phone number 'will always be the DoorDash support number: 855-973-1040', the email ordernumber@doordash.com), customer uniqueness by phone or email is 'not recommended' because 'all customer orders for DoorDash will be merged to the same CRM account in Revel', and 'the customer name on all previous DoorDash Marketplace orders will be overridden by the new customer's name'. The guest's address does not sync at all. Grubhub has no direct Revel integration documented. So native guest identity attaches on one of the two supported marketplaces, not across marketplace volume generally. https://support.revelsystems.com/s/article/UberEats-Onboarding · retrieved 2026-08-06 adversarially verified

guest-loyalty-accrual-models

Native rewards program offers three configurable reward types: 'Visit: one Visit reward point every time the customer makes a purchase', 'Purchase: points based on the total amount of the customer's purchase', 'Item: points based on the products purchased' (with per-product Point Value and Purchase Reward Multiplier fields). Configured in Management Console under Gift, Rewards, and Admin Cards / Loyalty; the desired reward type is enabled by contacting Revel Support, but no custom development or bolt-on loyalty vendor is needed. https://support.revelsystems.com/s/article/Creating-a-Loyalty-Program-1583151656809 · retrieved 2026-08-04

guest-loyalty-tiers differentiator

CRM tab has a Loyalty Tiers page 'to segment customers into tiers that are eligible for special discounts or deals', with tier-based payment/discount restrictions and a 'Stacking of Loyalty Tier Rules' (Competitive vs Stacked) accrual setting — but tier membership is defined by rewards-card number ranges ('Card Range From and Card Range To'), i.e. static assignment. No automatic promotion/demotion driven by rolling-window spend or visit counts is documented anywhere in the complete help centre. https://support.revelsystems.com/s/article/CRM-Tab-Overview-1583148889940 · retrieved 2026-08-04

guest-loyalty-offline-behavior differentiator

Re-read the Offline Mode article in the complete help-centre mirror (Googlebot capture 2026-08-04). It declares its scope as processing transactions during an ISP, management-console or gateway outage, and its sections are POS offline status notification intervals, offline payment settings and thresholds, offline tills management, and per-gateway outage procedures (TriPOS, FreedomPay, iFCC, Freeway, Adyen), closing with 'Apple Pay works in Offline Mode. Debit payments can't be accepted in Offline Mode.' It contains no statement that the functions it lists are the only ones available offline, so it is not an exhaustive enumeration and loyalty's absence from it is not positive evidence. Searching the 693-article mirror for offline, Always On Mode, loyalty, reward, points and redemption produces no article stating what loyalty lookup, accrual or redemption do without connectivity - including in the Loyalty XT, Como, Punchh, Paytronix, LoyaltyPlant and Open Loyalty integration articles, most of which describe cloud-hosted third-party loyalty engines whose offline behavior would in any case be the partner's to document. Absence from the public help centre is not documented absence, and the mirror does not cover Revel University or the loyalty partners' own documentation. adversarially verified

guest-loyalty-offer-stacking-rules differentiator

Per-discount 'Stacked Discount Type' drop-down: Competitive, Competitive Not Stacked, or Stackable. Docs state stackable discounts 'can be assessed against objects that already have discounts on them. They do not compete', Competitive Not Stacked discounts are 'the only discount on the object', and give explicit application-order rules (stacked % applies against the original item price; against the reprice amount for reprice/alt-price; against combo reprice only for combos). Additionally 'Tiered discounts' allow ranking discounts so 'Only one discount per tier will be applied', and loyalty-tier accrual has a Competitive-vs-Stacked setting. https://support.revelsystems.com/s/article/Stackable-Discounts-1583151656823 · retrieved 2026-08-04

guest-loyalty-targeted-offers differentiator

Loyalty XT's Campaign Center supports one-time actions issued to a filtered audience: 'Select which members to perform the action on by specifying criteria ... based on the members attributes, or actions (like: member that performed a purchase that included a coffee item in the last week)', and flexible campaigns can be limited 'to specific members ... by their attributes'. Shortfall: this requires the separately purchased Loyalty XT add-on (powered by Como, managed in the Como Hub, sales-assisted onboarding); Revel's core loyalty/discount engine has no audience targeting, and message sends need an additional Marketing Communications subscription. https://support.revelsystems.com/s/article/Loyalty-XT · retrieved 2026-08-04

guest-loyalty-rfm-segmentation differentiator

Loyalty XT: 'All members are automatically segmented in the system based on their Days since last visit', driving the Win Back Members campaign (1/2/3-month lapsed thresholds with automatic SMS/email when members enter the segment). Shortfall: only recency-based lapsed segmentation is documented — no automatic frequency/monetary or full lifecycle segments (new, regular, VIP) — and it requires the separately purchased Loyalty XT (Como) add-on. https://support.revelsystems.com/s/article/Loyalty-XT · retrieved 2026-08-04

guest-loyalty-lifecycle-automation

Loyalty XT ships always-on lifecycle rules: a joining gift 'sent using a Rule, upon joining the program', a birthday gift 'sent to the member's once a year on its birthday', and a Win Back Members deal that applies automatically to guests returning after 1/2/3 months, with optional automatic SMS/email. Shortfall: these exist only in the separately purchased Loyalty XT (Como) add-on — core Revel loyalty has no triggered campaigns — and the SMS/email sends require an additional Marketing Communications subscription. https://support.revelsystems.com/s/article/Loyalty-XT · retrieved 2026-08-04

guest-loyalty-native-email-sms differentiator

Loyalty XT can send both SMS ('choose the Send SMS action and simply type your SMS', with @-parameter merge fields) and email (template builder, 'choose the Send Email action and select which template') campaigns. Shortfall: sends happen from the Como Hub of the Loyalty XT add-on, not from Revel's Management Console, and 'an additional Marketing Communications subscription is needed for this functionality to be available' — core Revel has no campaign sending at all. https://support.revelsystems.com/s/article/Loyalty-XT · retrieved 2026-08-04

guest-loyalty-consent-management

'Consumer Marketing Opt-in/out & Logging' captures per-channel consent (separate Email, Phone/SMS, and Mail drop-downs) editable on the Management Console and POS, and 'Every time a change is made to the Marketing Opt In/Out settings on a CRM entry, the changes will be tracked in your Action Log' (which records who, when, and before/after values); online-ordering signup also offers opt-out at account creation (v2.74). Shortfalls: the feature must be enabled by Revel Support, and no documented linkage suppresses Loyalty XT/Como messaging from these CRM flags — consent SMS for Como is managed separately in the Como Dashboard. https://support.revelsystems.com/s/article/Enabling-Consumer-Marketing-Opt-in-out-Logging-1583148890442 · retrieved 2026-08-04

guest-loyalty-10dlc-registration

Searched the complete 693-article public help-centre mirror (captured 2026-08-04) for 10DLC, A2P, SMS campaign, text message campaign, carrier registration: zero hits. SMS sending exists only via the Loyalty XT (Como) add-on's Marketing Communications subscription, and neither Revel's Loyalty XT article nor any other article says who performs A2P 10DLC brand/campaign registration or whether it is handled at all — Como may handle it invisibly, so this is unresolved rather than absent.

guest-loyalty-campaign-attribution differentiator

The Discounts report ties every redeemed discount (including loyalty reward discounts, filterable as 'Loyalty Discounts') to the specific Order #, item, SKU, quantity, and date, grouped by Order/Reason/Item/Discount Type — i.e. redemption reporting against actual checks. Shortfall: no incremental-sales measurement per campaign is documented anywhere in the help centre; campaign-level analytics for Loyalty XT live in the third-party Como Hub ('Data & BI' dashboard), documented only by Como's own knowledge base. https://support.revelsystems.com/s/article/Discounts-Report-1583149669643 · retrieved 2026-08-04

guest-loyalty-data-export-portability differentiator

The customers suite reads and writes guest records, so an API export path exists. The claim's self-serve conjunct is unmet: nothing on any live surface shows an operator obtaining credentials without a partner arrangement, and the page that documented credential issuance has been withdrawn (see extensibility-oauth-partner-apps, now quarantined). Partial holds -- on an unestablished conjunct, not a disproved one. https://oas-prod.s3.amazonaws.com/oas/2025.3.0/customers_suite.yaml · retrieved 2026-08-10

guest-loyalty-review-capture-routing differentiator

Searched the complete 693-article public help-centre mirror (captured 2026-08-04) for feedback, survey, review site, Yelp, Google review, NPS, net promoter: the only hit is a marketing bullet in the third-party Open Dining online-ordering integration article ('Feedback surveys help the client correct service issues'), which describes no score-based routing and is not a Revel capability. No native post-transaction feedback request or score-routing feature is documented, but the vendor's marketing site (now redirecting to shift4.com, HTTP 403 to fetch tools) could not be checked, so this stays unresolved rather than absent.

guest-loyalty-referral-program

Searched the complete 693-article public help-centre mirror (captured 2026-08-04) for referral, refer a friend, invite, two-sided reward: zero product hits (the only 'referral' match is a card-decline error code). No referral mechanic is documented in Revel's help centre or in the Loyalty XT article's campaign list; a referral feature could still exist inside the Como Hub or partner loyalty products (Punchh, Paytronix) without Revel documentation, so absence from the mirror alone leaves this unresolved.

guest-loyalty-wallet-pass differentiator

Searched the complete 693-article public help-centre mirror (captured 2026-08-04) for Apple Wallet, Google Wallet, wallet pass, passbook: zero hits. Neither the native rewards program (physical/manual rewards cards) nor the Loyalty XT article mentions wallet passes; partner loyalty apps (LoyaltyPlant QR codes, Punchh app) are the only documented digital credentials. A wallet pass could exist in Como's or a partner's product without Revel documentation, so this stays unresolved.

guest-loyalty-privacy-rights-tooling

Customer Anonymization 'searches for and permanently removes all key information about a customer (name, email, address, phone, date of birth, etc.) from the entire system', iterating all customer database fields and related models with documented replacement formats (e.g. noreply+anonymous_<ID>@revelup.com), plus photo deletion and forced POS refresh to clear local data; the CRM Export/Import tool covers data access requests. Shortfalls: the feature must be enabled by Revel Support, 'there is no way to perform this action in bulk', the anonymized record remains reachable by customer ID, and no deletion propagation into the Como-hosted Loyalty XT marketing records is documented. https://support.revelsystems.com/s/article/Customer-Anonymization-1583148890445 · retrieved 2026-08-04

guest-loyalty-redemption-fraud-controls

Manual point changes are permission-gated: the 'Reward Cards' POS role permission 'Allows user to manually add or subtract rewards points from a card', and 'Create Gift/Rewards Cards' is a separate grantable permission. Shortfalls: no redemption velocity limits and no employee self-redemption flagging are documented anywhere in the help centre, and the Action Log report's enumerated recorded actions (item deleted, price override, product change, etc.) do not include loyalty point adjustments or redemptions — no loyalty audit trail is documented. https://support.revelsystems.com/s/article/Employees-Roles-and-Permissions-Guide-1583149941746 · retrieved 2026-08-04

guest-loyalty-ai-offer-recommendation differentiator

Searched the complete 693-article public help-centre mirror (captured 2026-08-04) for AI, artificial intelligence, machine learning, recommendation: the only AI product documented is Captain AI, a delivery routing/dispatch portal for Delivery XT — nothing about AI/ML-generated offer content, audience, or send-timing recommendations in Revel's loyalty, CRM, or Loyalty XT documentation. The claim allows vendor marketing-level documentation, but revelsystems.com marketing pages now redirect to shift4.com which returns HTTP 403 to available fetch tools, so a marketing-level claim could not be checked either; unresolved.

guest-loyalty-stored-value-gift

Gift card management listed; Givex and Paytronix monitored as integrations. Brand-wide redemption tied to one guest profile unverified. https://status.revelsystems.com/ · retrieved 2026-08-01

labor-clock-in-at-pos

TimeSheetEntry is a first-class readable/writable resource alongside TimeSchedule and TimeScheduleRule, implying the POS holds timekeeping. PIN/badge punch mechanics remain undocumented, so partial holds. CORRECTION on re-check 2026-08-10: the dossier previously rested this on a timesheet-entry WEBHOOK. The vendor's current webhook surface enumerates six event types and timesheets is not among them, so that half of the note is withdrawn rather than re-pointed. The resource inference stands on its own. https://oas-prod.s3.amazonaws.com/oas/2025.3.0/scheduling_suite.yaml · retrieved 2026-08-10

labor-photo-punch-verification differentiator

Advanced POS Settings documents a 'Photo clockin' setting: 'This setting forces employees to take their picture as a part of the clock in process. A manager/owner must allow the POS to store photos on the iPad's photo library in addition to enabling this setting.' Photo-only capture with no facial verification or biometric template anywhere in the docs. Shortfall: the documentation describes storage in the iPad's local photo library, not attachment of the photo to the timecard entry for later manager review, and no verification mode exists. https://support.revelsystems.com/s/article/Advanced-POS-Settings-1583149942304 · retrieved 2026-08-04

labor-offline-time-punch differentiator

Searched the complete 693-article public help-centre mirror (captured 2026-08-04) for 'offline' combined with 'clock', 'punch', 'time worked' and 'connectivity'. The Offline Mode / Always On Mode article documents offline transaction processing (payments, order taking, batching) only and is silent on time punches; Time Management on the Point of Sale and Time Sheet Rules never address connectivity loss. No article documents whether punches are recorded offline or how they reconcile on reconnect, so the behavior can be neither affirmed nor denied.

labor-granular-rbac

Employees: Roles and Permissions Guide documents per-action POS permission tokens assignable per role: Comps, Item Discount, Manual Discount, Open Cash Drawer, Void Items ('Allows users to void or return items without a password'), Refund Payment, Price Override, Override Void/Return/Exchange Limits, iPad Reports, plus separate Management Console permission sets. Custom permission sets can be created and copied ('If the default permissions aren't sufficient... you can further customize or add additional permission sets'). Permissions are managed per establishment, with a brand-level Employee Permissions Audit export across locations via the EMS Establishment Hierarchy Tree. https://support.revelsystems.com/s/article/Employees-Roles-and-Permissions-Guide-1583149941746 · retrieved 2026-08-04

labor-manager-override-audit

The Action Log report 'displays specific employee actions done on the POS and Management Console' with Date, Employee ('The employee who performed the action'), Action, Target, and Description of Change columns. Logged actions include Price Override, Time Worked Created/Edited/Deleted Manually on POS, Administrator Permission Change, Role Permission Change, Item Deleted and Login Attempt. The report is filterable by POS station, employee and action, groupable by employee, and exportable in various formats — an after-the-fact queryable, individually-attributed audit trail. https://support.revelsystems.com/s/article/Action-Log-Report-1583149671561 · retrieved 2026-08-04

labor-native-scheduling differentiator

Scheduling is a distinct suite -- TimeSchedule, TimeScheduleRule and TimeSheetEntry, all readable and writable (6 GET, 2 POST/PATCH/PUT, 2 DELETE) -- held in the same platform as the timekeeping data, which is what the claim asks. The publish/notify workflow is undocumented: the spec exposes no publish or notification operation, so partial holds. https://oas-prod.s3.amazonaws.com/oas/2025.3.0/scheduling_suite.yaml · retrieved 2026-08-10

labor-demand-labor-forecast differentiator

The scheduling documentation enumerates the entire Shift Schedules toolset: manual shift creation, Excel import, week-to-week shift copying, and a 'Wage/Forcasting' view that only displays projected payroll and sales for shifts already entered by the manager. No function generates recommended staffing levels or labor hours from the operator's sales history; the Labor Report defines 'Projected Hours' as 'the hours scheduled through the Shift Schedule tab'. Revel's only sales-history forecasting (Item Tracking / Product Forecasting) drives food-prep quantities, not labor. Complete public help centre searched. https://support.revelsystems.com/s/article/Creating-Shift-Schedules-1583150213550 · retrieved 2026-08-04

labor-realtime-labor-percent differentiator

The Labor Report is available on the Point of Sale itself via the drop-down reports: 'This report will display labor data, including your labor costs, labor percentage, and total sales per hour. As of the 2.79 update, we have added a labor hours column and a sales per man hour (SPMH) column.' Printable POS reports can additionally include 'man hours, wages and percentage of labor'. Access is gated by the iPad Reports role permission, so managers can view labor percentage intraday during service. https://support.revelsystems.com/s/article/Viewing-Reports-on-the-Point-of-Sale-1582899334000 · retrieved 2026-08-04

labor-overtime-prevention differentiator

Shift alerts 'for late employees and for employees in or nearing overtime' can be configured on the Settings > Reports > Insights Application page and appear on the Schedules screen of the Insights by Revel iPhone app. Shortfalls: the alert surfaces only in the separately licensed Insights app (per-device license keys purchased through Revel Sales), is a manager-side notification, and nothing warns or blocks the employee at clock-in on the POS — Time Sheet Rules set overtime thresholds and multipliers for pay calculation only. https://support.revelsystems.com/s/article/Insights-by-Revel-1582893045693 · retrieved 2026-08-04

labor-break-compliance-by-state differentiator

Time Sheet Rules provides configurable break rules: 'Calculate Paid/Unpaid Breaks By Rules' (documented explicitly around California's 5-hour meal rest period requirement, with the note that 'Businesses in California must be able to produce a report that reflects these breaks'), Work Time To Qualify For Paid Break, Duration Of Paid Break, Employee Declares Break Type, and 'Prevent Employee Clock-In Before Break End' requiring a manager PIN. Shortfalls: a single rule set per establishment with no per-state/jurisdiction rule library, no required break attestation prompt, and no missed-break premium-pay flagging documented. https://support.revelsystems.com/s/article/Time-Sheet-Rules-1583150213539 · retrieved 2026-08-04

labor-minor-labor-rules

Searched the complete 693-article public help-centre mirror (captured 2026-08-04) for 'minor', 'age', 'under 18', 'school', 'curfew' and related terms. The Time Sheet Rules settings table — the documented clock-in rule surface — contains no age-based maximum-hour or prohibited-time-window settings, and the scheduling docs show none either, but no article affirmatively addresses minor labor enforcement one way or the other, so absence cannot be asserted.

labor-tip-pooling-rules

Tip Pooling is a documented native feature: pool contributions computed from configurable rules — Tip In Based On Tips or Sales, per-role Tip In % ('servers might tip in 50% of their tips'), Tip Share distributed Even (based on hours worked) or by Percentage per role, Periodicity By the Week, By the Day, or By the Shift, and Treat Declared Tips As Total Tips / Cash Only / Ignore. The Tip Pool tool (Schedules > Tip Pooling) calculates the Share Plan and per-employee breakdown automatically from these rules; a manager reviews and submits each pool. No spreadsheet required. https://support.revelsystems.com/s/article/Tip-Pooling-1583150213556 · retrieved 2026-08-04

labor-tip-distribution-audit-trail

The Tip Pool tool retains submitted pools per day or per shift ('You may also view past submitted pool here'); the Employee Breakdown records each employee's tips, Tip In Amount owed to the pool, and Tip Share received, with role-level Share Plan detail (hours, sales/tips, tip-in %, adjusted share %). Final tips post to the Payroll report ('Adding Final Tips to Payroll'), which shows per-employee Declared Tips and Non-Cash Tips columns and exports in multiple formats for audit. https://support.revelsystems.com/s/article/Tip-Pooling-1583150213556 · retrieved 2026-08-04

labor-qualified-tips-w2-reporting differentiator

Searched the complete 693-article public help-centre mirror (captured 2026-08-04) for 'W-2', 'Box 12', 'Box 14', 'code TP', 'qualified tips' and 'occupation code'. The documented payroll exports (ADP Workforce Now / Total Force CSV/XLSX; QuickBooks Online Payroll sync, which carries hours only) separate declared cash tips from non-cash payment tips in the Payroll report, but no page addresses the tax-year-2026 W-2 Box 12 code TP / Box 14b requirements or any Treasury tipped-occupation coding — the help-centre content predates the requirement, so support can be neither affirmed nor denied.

labor-native-payroll differentiator

Revel's 'Payroll' is a reporting tab (Schedules > Payroll) that summarizes employee hours, wages and tips with export links — 'Your Payroll can easily be managed in Revel as long as you have your employees clock in and clock out.' The documented paths to actually pay employees are third-party: the ADP export (Workforce Now / Total Force) and the QuickBooks Online Payroll integration, where 'QBO payroll does not allow Revel to send any other information other than hours worked' and payroll is run inside QuickBooks ('go to QuickBooks > Payroll and select to Run Payroll'). No first-party tax filing or direct deposit exists anywhere in the help centre. https://support.revelsystems.com/s/article/Payroll-Guide-1583150213542 · retrieved 2026-08-04

labor-payroll-export-formats

Two named major providers with documented formats/integrations: (1) ADP — 'You can export the hours your employees worked (in CSV or XLSX form) to import into ADP. We support both Workforce Now and Total Force formats', exported from Schedules > Payroll with each employee's ADP number stored in the External ID field; (2) QuickBooks Online Payroll — the integration 'will automatically populate employee worked hours to Payroll on QuickBooks' (Employees: QBO article). The Payroll report itself also exports hours, wages, declared and non-cash tips in multiple formats. https://support.revelsystems.com/s/article/How-to-Export-Employee-Hours-to-ADP-1583150213536 · retrieved 2026-08-04

labor-shift-swap-workflow differentiator

Re-read Creating Shift Schedules in the complete help-centre mirror (Googlebot capture 2026-08-04). It is a how-to with six sections (Viewing Shift Schedules, Creating a Shift Schedule, Configuring Your Scheduling Email, Emailing Schedules, Copying Shift Schedules, Shift Schedule Details) and makes no claim to describe the whole employee-facing surface. The documented employee interaction is that a schedule is emailed and 'Your employee can then choose to confirm or reject their scheduled shifts' after PIN login, with a four-colour status key (White = No Email Sent, Yellow = Email Sent, Green = Employee Accepted Schedule, Red = Employee Rejected Schedule) - that key enumerates the states of an emailed schedule, not the actions an employee may take, and the article nowhere says shifts can only be created, edited or cancelled by managers. Searches of the 693-article mirror for shift swap, swap shift, open shift, trade shift, self-service, employee app, employee portal and availability request return nothing relevant, and a web search for a Revel employee scheduling app surfaced only third-party workforce products that integrate with Revel (7shifts, HotSchedules/Fourth). Absence from the public help centre is not documented absence, so this cannot be asserted as a no. adversarially verified

labor-server-performance-metrics differentiator

The Employee Profit Report gives per-employee Sales, Sales/h., Trans., Avg Trans. (average check), QTY/Trans. (items per transaction), Cost, Profit, %Profit and Profit/h., filterable by role/department and date range — solid per-server sales metrics. Shortfall: no documented per-employee void and comp rate; voids, returns and comps are reported in aggregate sections of the Operations and Adjustments reports rather than as an employee scorecard metric. https://support.revelsystems.com/s/article/Employee-Profit-Report-1583149670660 · retrieved 2026-08-04

inventory-recipe-bom-costing

Multi-level BOM costing is documented natively: 'Use ingredient cost to calculate product cost — If a product is assigned ingredients through a recipe, the total cost of the product is derived from the sum total of all ingredients... the ingredient itself will have a dynamic cost based on the inventory cost' (Introduction to Inventory settings). Ingredients can themselves carry recipes of other ingredients for house-made prep items ('housemade sauces, buns, or ice cream... track your inventory to the micro-ingredient level' — Attaching Recipes to Ingredients), and Total Recipe Cost is system-computed (view-only in the import/export tool). https://support.revelsystems.com/s/article/Introduction-to-Inventory-1583148890898 · retrieved 2026-08-04

inventory-unit-conversion-yields

Inventory Stock Unit Conversions documents per-product stock units with explicit conversion factors ('enter how many individual units of this item go into the stock unit. For example, 24 units (cans) of soda make up a case'), a Primary unit flag, and per-stock-unit default reorder prices; POs are placed in reorder units while receiving and sales depletion post in individual units. Prep recipes carry a Recipe Yield and per-batch Actual Yield. Shortfall: no per-item yield/waste percentage applied to raw-to-usable conversion — yield exists only as a batch output quantity on prep recipes. https://support.revelsystems.com/s/article/Inventory-Stock-Unit-Conversions-1583149942770 · retrieved 2026-08-04

inventory-theoretical-vs-actual differentiator

The Physical Inventory Report keeps history per completed count cycle and 'summarizes the expected count versus the actual count (variance)': Total Quantity Expected/Counted, Variance in Quantity, Total Value Expected/Counted, Variance in Value, drillable by Category or Class, where expected on-hand derives from recipe-driven sales depletion plus receipts. Shortfall: this is an on-hand shrink/variance report per count cycle, not a per-item usage decomposition showing theoretical usage (POS sales x recipe) versus actual usage for the period as separate figures. https://support.revelsystems.com/s/article/Physical-Inventory-Report-1583149672025 · retrieved 2026-08-04

inventory-realtime-depletion differentiator

The vendor's own webhook request form enumerates 'In/Out Stock' as a selectable event type, so inventory status changes are pushed rather than polled. Modifier-driven depletion granularity is still unverified, so partial holds. Re-pointed 2026-08-10: the inout.stock event previously cited on the withdrawn developer portal survives on this form, which additionally shows webhooks are enabled BY REQUEST (partner name, establishment ID, target URL, environment) rather than self-serve. https://support.revelsystems.com/s/webhook-access · retrieved 2026-08-10

inventory-86-auto-sync differentiator

With 'Track in Inventory' plus 'Do not allow sale of this product without stock on hand', items become unsellable at zero stock. Online Ordering XT tracks by product or recipe ingredient — 'the pizza will show as out of stock when you... are out of pepperoni, mozzarella, or any other item in the recipe. Modifiers with recipes attached will be tracked too. If an item becomes unavailable before the customer checks out, it will show as unavailable in their cart' (ingredient-level tracking is enabled by Revel Support on request; not yet supported for linked/split combos). The DoorDash Marketplace integration honors the same state: 'Items with zero or negative stock count in Revel cannot be ordered on DoorDash if the product, modifier, and or ingredient as part of a recipe... has track in inventory enabled.' https://support.revelsystems.com/s/article/Online-Ordering-XT-Product-and-Ingredient-Inventory-Tracking · retrieved 2026-08-04

inventory-count-modes

Full or subset counts are documented: Physical Inventory sessions select Group/Class/Category to count and divide the store into sections; the successor Stocktake feature adds reusable templates, sections with variance handling, in-progress viewing, per-section recounts, count-figure editing, and a list of completed stocktakes; the Physical Inventory History report retains each cycle's expected-vs-counted variance separately in quantity and value. Shortfall: no scheduled recurring cycle-count automation is documented — every count is started manually (templates ease repetition but nothing runs on a schedule). https://support.revelsystems.com/s/article/Stocktake-1583149941735 · retrieved 2026-08-04

inventory-mobile-count-offline

The Revel Inventory App (iOS) supports section-based counting with barcode scanning by wired scanner, Bluetooth scanner, or the iPhone's internal camera, with expected-vs-counted per item, blind-scan and require-count-by-scan options, and sync of finalized counts to the Management Console. Shortfalls: 'The physical inventory itself is done on the Revel Inventory App and requires a separate paid subscription', and no documentation states that the app continues accepting counts with no network connectivity and syncs on reconnect. https://support.revelsystems.com/s/article/Physical-Inventory-1583149941728 · retrieved 2026-08-04

inventory-vendor-catalogs-edi differentiator

PO transmission is documented as email of a PDF ('Enable Emailing Purchase Orders: If checked, user will have the option to email a PDF of a purchase order upon completion') or print; the Inventory FAQs' answer for getting an order list into 'a wholesale order site' is 'You can export your inventory list to Excel'. The complete Inventory tab tour (Vendors, Reorder, Purchase Orders, RMAs, Transfer...) contains no distributor catalog or EDI order/invoice integration, and no broadline distributor (Sysco, US Foods, PFG) appears anywhere in the complete public help centre. https://support.revelsystems.com/s/article/Inventory-FAQs · retrieved 2026-08-04

inventory-invoice-ocr differentiator

Every documented invoice-entry path is manual: receiving against POs (with the 'Require Invoice number when receiving' setting), the Periodic Inventory Purchase Ledger where users key invoice number, date, vendor, products, quantities ('This field can currently only support whole numbers') and cost line by line, and Excel import/export. No photo, PDF, or email ingestion with line-item extraction exists anywhere in the complete public help centre, whose Inventory tab tour enumerates all receiving surfaces. https://support.revelsystems.com/s/article/Periodic-Inventory-1583149942773 · retrieved 2026-08-04

inventory-price-change-alerts differentiator

The Inventory FAQs state the limitation directly: 'Will Revel show the last purchased price when creating purchase orders? — No. The purchase order will display the cost as entered on the product or ingredient list.' No per-item purchase price history is surfaced at ordering, and no received-price-vs-prior/contract alerting exists anywhere in the help centre; the Vendor Invoices report lists invoices without any price-comparison or threshold alert. https://support.revelsystems.com/s/article/Inventory-FAQs · retrieved 2026-08-04

inventory-par-auto-suggest differentiator

Reorder to PAR is documented: per-product/ingredient PAR via the Default Reorder Quantity field with 'Reorder to PAR' checked; the Inventory > Reorder tab computes the suggested quantity as PAR minus current stock and generates the PO ('if the Default Order Quantity is set to 144, and you have 14 of the product in stock, 130 will appear on your purchase order'). Shortfall: static PAR only — Revel's only sales-history forecasting (Item Tracking / Product Forecasting) drives prep-report printing for QSR item prep, and is not linked to purchase-order suggestion. https://support.revelsystems.com/s/article/Reorder-to-PAR-1583149943286 · retrieved 2026-08-04

inventory-waste-logging

Revel Inventory (App Store listing, published by 'Revel Systems INC', bundleId com.revelsystems.inventory) states in its own description: 'Manage Your Inventory. Quickly receive items, input waste and spoilage, and update item cost and price right from the app.' That documents a waste/spoilage entry workflow that debits inventory (the app's stated purpose is updating on-hand quantities). Named shortfall: the listing does not mention reason codes on waste entries, nor does it say waste cost is reported separately from usage variance - both required by this claim - and an App Store description is vendor marketing copy, not an admin guide, so it is capped at grade C regardless. https://apps.apple.com/us/app/revel-inventory/id1051198587 · retrieved 2026-08-04

inventory-shelf-life-expiry

The vendor's own Inventory FAQs state the absence directly. Q: 'If we follow FIFO and know the shelf life of ingredients, is there a way for the system to estimate the wastage / spoilage given receivables vs. sales?' A: 'No. There is no way to automate shelf life/expiration dates and wastage.' No expiration-date tracking or expiring-soon report exists anywhere in the help centre. https://support.revelsystems.com/s/article/Inventory-FAQs · retrieved 2026-08-04

inventory-bar-partial-bottle

Searched the complete 693-article public help-centre mirror (captured 2026-08-04) for 'bottle', 'partial', 'pour', 'liquor', 'scale', 'weight' and 'tenth'. Scale references concern retail weighing at the point of sale, and inventory counting is documented as hand-entered quantities or barcode scans with no bar-specific liquid inventory workflow; whether fractional bottle counts can be entered is not documented, and no article affirmatively excludes them, so the claim cannot be resolved either way.

inventory-cogs-gl-export

The cost side does reach QuickBooks Online in QBO's own format: selecting the Inventory module 'will send Purchase Orders and Inventory Cost of Goods to QBO Daily. No Quantity on Hand or inventory lists will sync.' The GL targets are documented as specific QBO account types and subtypes - COGS Account = Cost of Goods Sold / 'Supplies Materials-COGS', Asset Account = Other Current Asset / Inventory, Payable Account = Accounts payable (A/P), plus a POS Inventory Adjustment account - and Location Tracking stamps the establishment name on each entry. Named shortfall, and it is the operative one: the claim requires GL account mapping configurable PER ITEM CATEGORY, and the documented mapping is a single fixed set of account slots. Revel states 'our integration does not allow you to choose accounts that would conflict with the business logic of QuickBooks. Accounts available within the QBO Settings drop-down are accounts that fit the integration requirements' and 'Customers cannot change these to any account that is not available in those drop downs'. Product-class breakout ('Summary by Product Classes') exists only on the sales side, not as per-category COGS mapping, and quantity on hand never syncs. https://support.revelsystems.com/s/article/QBO-Mapping-Account-Types-1583148425273 · retrieved 2026-08-02 adversarially verified

inventory-native-not-partner differentiator

UPGRADED partial -> yes on 2026-08-10. The claim asks that inventory AND recipe costing be native rather than a separately-contracted third-party product. Inventory is 32 paths (37 GET) beside a 20-path purchase-orders suite; recipes are first-class and writable (ProductRecipe, IngredientRecipe, ModifierRecipe, all get/post/patch/put); and costing is explicit in the schema -- `costing_method` ("Can be avg, lifo, fifo"), `total_value`, a reorder/par `threshold`, `adjust_cost`, and `cost_override` ("Override of the modifier cost for this Product"). The dossier's "recipe costing depth unverified" shortfall is REFUTED. The 'Inventory X' product the dossier referenced is confirmed live rather than dropped: /inventoryx/api/inventory/{CurrentStock,Product,Ingredient} paths, including receive operations, are published in this spec. https://oas-prod.s3.amazonaws.com/oas/2025.3.0/inventory_suite.yaml · retrieved 2026-08-10

inventory-menu-margin-linkage differentiator

The Product Mix Report joins cost to sales mix per item: optional Margin/Pricing columns include Cost of Goods Sold %, Average Price, Gross Margin and Gross Margin %, plus a 'Top 10 Profit By Product' graph 'based on product cost and product sales'; with 'Use Ingredient Cost to Calculate Product Cost' enabled, that cost is recipe-derived and moves with ingredient costs. Shortfall: no configurable margin threshold that flags items whose margin fell after ingredient cost changes — margin is a report column, not an alert. https://support.revelsystems.com/s/article/Product-Mix-Report-1583149670668 · retrieved 2026-08-04

reporting-realtime-dashboard

The off-premise mobile dashboard is 'Insights by Revel' (the documented replacement for the Manager App), whose Dashboard screen 'provides insights on transactions, payments, top selling products, labor trends, and shift alerts', supports day-over-day trending percentages, drill-down reports in Data/Pie/Graph views, and filtering by trend, employee or role. Named shortfalls, all from Revel's own article: (1) it is a PAID add-on, not included - 'Upon purchasing the app, you will receive an email containing a license key... A license key is required to active Insights', and additional device keys require a call to Revel Sales; (2) 'The Insights by Revel app is available on the iPhone via the App Store. This app is not available for Android devices'; (3) 'The reporting range is one day' and trending is only available on a single-day report; (4) access requires POS role plus Manager permission. Critically for this claim, no refresh latency is stated in any Revel document I could retrieve - the article never says how current the dashboard is, so 'reflecting transactions within minutes of the sale' remains unestablished. https://support.revelsystems.com/s/article/Insights-by-Revel-1582893045693 · retrieved 2026-08-02 adversarially verified

reporting-eod-closeout

The Operations Report is 'a combination of various reports all rolled into one... reconciles the essentials from each report into one large report': Gross Product Sales, Discounts, Net Sales, Taxes (with rates), Tips (cash/credit/auto gratuity/adjustments), Adjustments, Voids/Returns/Comps/Exchanges with reason and total, Payments by method (grand total equals the Sales Summary's Net To Account For), Cash Summary with pay-ins/pay-outs and cash deposits, and Labor wages. The companion Sales Summary Report adds Cash Due house/employee and refunds detail. https://support.revelsystems.com/s/article/Operations-Report-1583149671565 · retrieved 2026-08-04

reporting-pmix-modifier-level

Product Mix Report has a Modifier display field and a documented Modifier Totals section ('the total displayed for each modifier will be the number of products with that modifier sold', with a pepperoni-pizza worked example), plus item-level sales, discounts, tax, and margin columns, filterable by Employee, Day of the Week, Dining Options, Online Orders, and Product Class. Shortfall: modifier rows are documented as quantity counts only — per-modifier gross/net sales columns are not documented — and there is no daypart filter (day-of-week and dining-option filters only). https://support.revelsystems.com/s/article/Product-Mix-Report-1583149670668 · retrieved 2026-08-04

reporting-comps-voids-audit

The Discounts Report houses item/order/exchange discounts and coupons with Order #, Item, QTY, Date, and 'Reason: The reason entered on the POS when the discount was applied', filterable by Employee and groupable by Order/Reason/Item/Discount Type; the Operations Report shows voids, returns, comps, and exchanges by reason, quantity and total and points to the Discounts report for detail; the Action Log Report records Price Override and Item Deleted actions with Date and Employee columns. Shortfall: no documented attribution of the approving manager on comps/voids/discounts — attribution is to the employee only. https://support.revelsystems.com/s/article/Discounts-Report-1583149669643 · retrieved 2026-08-04

reporting-cash-over-short

Cash management exposes BankDrop, CashOffice, Payout and Till (8 GET, 4 POST/PATCH/PUT), implying drawer reconciliation. Shortfall re-measured, not carried: the spec contains no over/short field and no over/short report operation, and nothing addresses the claim's per-shift or per-employee dimensions. Partial holds. https://oas-prod.s3.amazonaws.com/oas/2025.3.0/cash_management_suite.yaml · retrieved 2026-08-10

reporting-labor-productivity

The Labor Report 'shows your labor cost compared to the amount of sales done per hour', with per-hour rows for Actual Hours ('Based on clock ins/ clock outs'), Wage, Sales, Sales Per Man Hour, and Qty. Per Man Hour, filterable by roles/departments; the Employee Profit Report gives per-employee Labor, Hours, Sales, % Sales (Sales/Labor), Sales/h., and transactions, filterable by role. Shortfall: no documented labor-cost-as-a-percentage-of-sales column — the hourly report shows wage and sales side by side and the per-employee report shows the inverse Sales/Labor ratio, split across two reports rather than one hourly/department/employee view. https://support.revelsystems.com/s/article/Labor-Report-1583149671122 · retrieved 2026-08-04

reporting-server-scorecards differentiator

The Employee Profit Report displays per-employee Sales, Trans., Avg Trans. (average sales per transaction), QTY, QTY/Trans. (average items per transaction), Sales/h., Profit/h., and % Profit, filterable by role and date range. Shortfall: no documented attachment-rate metric for named categories and no tips-as-a-percentage-of-sales metric — tips appear per employee in the Payroll report, not in this per-server sales scorecard. https://support.revelsystems.com/s/article/Employee-Profit-Report-1583149670660 · retrieved 2026-08-04

reporting-channel-profitability differentiator

Marketplace channels are tracked through named custom objects: for Uber Eats, 'The custom payment option, dining option, and discount will also be named Uber Eats. These are all used for tracking and reporting of Uber Eats orders and sales', and reports filter by Dining Options and Online Orders, so per-channel revenue is reportable. Shortfall: no commission-netted margin view — the DoorDash Marketplace article states merchants 'will continue to use the DoorDash merchant portal and/or the DoorDash tablet for... DoorDash specific reporting', so marketplace-fee-net profitability lives in the marketplace's portal, not Revel. https://support.revelsystems.com/s/article/UberEats-Onboarding · retrieved 2026-08-04

reporting-scheduled-delivery

Auto Delivery of Reports documents Email Report Jobs with named jobs, daily/weekly/monthly/quarterly/yearly cadences, CSV/Excel/PDF formats, multiple comma-separated recipients, per-establishment selection, and even an HTTP web-server target. Shortfall: only seven reports are schedulable — Sales Summary, Product Mix, Operations, Product Inventory Summary, Ingredient Inventory Summary, Labor, and Trending Sales (weekly only) — not any report, and the auto-delivered Product Mix arrives with default columns, ignoring customized selections. https://support.revelsystems.com/s/article/Auto-Delivery-of-Reports-1583149669622 · retrieved 2026-08-04

reporting-public-api differentiator

A public Swagger UI serves 14 OAS 3.0 suite specs (v2025.3.0) covering orders, payments and cash management, products/pricing, customers, employees and scheduling -- the claim's coverage conjunct, established more completely than the withdrawn ReadMe did. The self-serve-credentials conjunct is unmet: the page that documented credential issuance is gone, and the specs declare only an `API-AUTHENTICATION` apiKey header plus a placeholder OAuth2 block. Partial holds on an unestablished conjunct -- the vendor is NOT recorded as having withdrawn self-serve credentials, only as no longer publishing how credentials are issued. https://developer.revelsystems.com/ · retrieved 2026-08-10

reporting-webhooks differentiator

DOWNGRADED yes -> partial on 2026-08-10. The claim needs outbound webhooks for order and payment lifecycle events AND documented retry behaviour AND payload signature verification. The vendor's live webhook surface is a request form enumerating six event types -- In/Out Stock, Menu Updated, Order Finalized, Customer Created, Customer Updated, RewardCard Created -- which establishes the push mechanism but publishes nothing about retry or signing. The retry schedule and HMAC-SHA1 signature the dossier verified verbatim were on developer.revelsystems.com/revelsystems/docs/webhooks, now withdrawn; that reading is preserved under extensibility-webhook-reliability, which is quarantined rather than deleted. This is a downgrade of what is CURRENTLY PUBLISHED, not a finding that the vendor removed retry or signing. https://support.revelsystems.com/s/webhook-access · retrieved 2026-08-10

reporting-api-not-upcharged differentiator

Assessed against the complete 693-article support.revelsystems.com public help-centre mirror (searched: API, fee, subscription, pricing, developer) and developer.revelsystems.com's FAQ page (re-read live 2026-08-05): neither documents whether API or raw-data access carries an extra fee, revenue share, or plan requirement. The FAQ documents partner-issued credentials and a partner testing instance but is silent on cost. The only integration pricing found anywhere is the $20/month-per-establishment DoorDash Marketplace subscription — a marketplace integration fee, not API access. Whether API access is included in the standard subscription remains undocumented.

reporting-tier-paywall differentiator

Searched the complete 693-article public help-centre mirror for plan tiers or paywalls around reporting (terms: plan, tier, upgrade, subscription, add-on, Insights). The Management Console reporting articles (Sales Summary, Product Mix, Operations, Labor, Discounts, Tax) describe the reports with no mention of plan gating; the only separately-purchased reporting surface documented is the Insights by Revel iPhone app, which requires buying the app and a license key. Revel publishes no reachable plan-composition page (revelsystems.com marketing URLs 301 to www.shift4.com/food-beverage, which returned HTTP 403 on 2026-08-05), so whether core reports require a higher tier or add-on SKU cannot be determined.

reporting-history-retention differentiator

Searched the complete 693-article public help-centre mirror for a retention statement (terms: retention, 24 months, historical, archive, purge, year). Exporting Sales Data documents only that a single report export 'can cover up to a year at a time' and may time out on large ranges — a per-query range cap, not a retention window — and the Data Dictionary's 15-minute/15,000-row ceiling (developer.revelsystems.com/revelsystems/docs/data-dictionary) is likewise a query limit. No page states how many months of transaction-level detail remain queryable in the reporting UI, so the documented ≥24-month retention claim stays unresolved.

reporting-anomaly-alerts differentiator

Operator-configured threshold alerts are documented for cash: Till Alerts fire 'when the dollar amount in the cash drawer reaches this amount' with an Alert Email field ('Enter your email address to get your till alerts via email'), day/night thresholds, and a Deny Transaction Amount; Low Stock Alerts cover inventory, and the Insights app surfaces configurable late-employee/overtime shift alerts (Settings > Reports > Insights Application). Shortfall: no documented alerting on sales, void, or discount metrics, and no historical-pattern deviation detection — the claim's example anomalies are not covered. https://support.revelsystems.com/s/article/Tills-How-to-Setup-Till-Alerts-1582899801523 · retrieved 2026-08-04

reporting-nl-query

Searched the complete 693-article public help-centre mirror for any natural-language or AI analytics feature (terms: natural language, AI, artificial intelligence, assistant, Ask) — zero hits; the documented reporting surface is entirely fixed reports plus the Insights iPhone app. Absence from the help centre is not positive evidence of absence, and no current marketing page is reachable to check for a newer AI analytics SKU (revelsystems.com 301s to www.shift4.com/food-beverage, HTTP 403 on 2026-08-05), so this niche claim stays unresolved.

reporting-guest-cohorts differentiator

Searched the complete 693-article public help-centre mirror (terms: returning, lifetime, cohort, visit frequency, CRM, customer report, loyalty). The customer-level reporting documented is the Customers' Orders Report — a per-customer order list with order counts and Excel/CSV export — plus the Customer (CRM) Import/Export tool and Rewards Cards Report; no article documents new-vs-returning guest counts, visit-frequency analytics, or lifetime-spend cohorts. The help centre does not exhaustively enumerate every report, so this is recorded as unresolved rather than absent.

reporting-sales-forecast differentiator

Item Tracking / Product Forecasting documents forward forecasting from the location's own history: 'Forecast Item Quantities Based on Number of Weeks', 'Forecast Sales Based on Number of Weeks', net-or-gross basis, 'Hourly Forecasting Sales - Includes the forecast hourly sales for the day', per-time-slot forecasts at 15/30/60-minute intervals, safety factors, and auto-printed Start of Day/Interval/Closing prep reports; the report lives at Reports > Other Reports > Item Tracking Report. Shortfall: the forecast drives kitchen prep printing only — no documented consumption by labor scheduling (Labor Report's Projected Hours come from the manually built Shift Schedule) or purchase-ordering workflows. https://support.revelsystems.com/s/article/Item-Tracking-Product-Forecasting-1583149672017 · retrieved 2026-08-04

reporting-tip-tax-compliance

The Payroll report (Schedules > Payroll) shows per-employee Declared Tips ('employees can input the value of cash tips received on the Point of Sale') alongside Non-Cash Tips from credit transactions, toggled via Time Sheet Rules 'Display Declared Tips in Payroll' / 'Display Payment Tips in Payroll', and exports for payroll use; the Tip Pooling tool documents full distribution detail per employee (Declared Tips, Payment Tips, Tip In Amount, Tip Share Amount, Final Tips — 'the amount that should be reported to the IRS'); the Tax Report separates each tax rate with totals and offers By Zipcode/By State/By Country breakdowns (breakdown drop-down appears only when shipping is enabled). https://support.revelsystems.com/s/article/Payroll-Guide-1583150213542 · retrieved 2026-08-04

multi-location-org-hierarchy

The EMS Establishment Hierarchy Tree is a first-class structure of brand > divisions ('Divisions can have numerous layers of sub divisions') > establishments, plus cross-cutting groups (an establishment can belong to many groups); clicking a division or group enables EMS mode for all establishments under it, EMS pushes and locks employee roles/permissions across establishments, and enterprise reports read data across levels. EMS is a paid add-on at $29/month per establishment. https://support.revelsystems.com/s/article/EMS-Establishment-Hierarchy-Tree-1582898526017 · retrieved 2026-08-04

multi-location-central-menu-publish

Products in EMS pushes categories, subcategories, products, product details and product modifiers from a base establishment to selected establishments or groups in one action ('Click save and the entire product shall be updated to all targeted establishments'), with field-level locks and Push ALL Details. Shortfalls: it requires the EMS add-on ($29/month/establishment), and there is no publish/version history - Push Settings in EMS states 'There is currently no Management Console dashboard for this... You will, however, receive an email verification', so what was pushed, when, and by whom is not visible in-console. https://support.revelsystems.com/s/article/Products-in-EMS-1582898526007 · retrieved 2026-08-04

multi-location-price-zones

Per-location prices exist without duplicating the item: EMS links the same product across establishments and lets price be set or locked per establishment from the base. Shortfalls: no channel or daypart price zones on the item record - third-party channel pricing is only a '3rd party price upcharge (%)' (DoorDash Marketplace) or a Weborder API price override, and Price Tiers are alternate prices attached to discounts (VIP/employee/promotion style), not location-group/channel/daypart price books. https://support.revelsystems.com/s/article/Products-in-EMS-1582898526007 · retrieved 2026-08-04

multi-location-consolidated-reporting

Above-store reporting exists as a named report. The Establishment Payments Report, reached from Management Console > Reports > Other Reports > Establishment Payments, 'is used mainly by business owners with multiple establishments to view a condensed version of the Sales Summary report for each establishment' and is 'also used for chain or franchise owners who collect a percentage of payments for royalties'. Basic columns are Establishment, Gross Sales, Total Discounts, Net Sales, Total Taxes, Total Liabilities, Total Payments, % of Total Payments, Total Transactions and Total Invoices; the All view adds Taxable/Non-Taxable Sales, service fees, Average Check, Item Discounts, Order Discounts, Coupons, Surcharges, house-account payments, gift card and store-credit activity. It filters by date range and exports. Named shortfalls: the claim asks for sales, labor, discounts, voids AND item mix in one cross-location view - labor, voids and item mix are not columns here and live in separate single-report surfaces (Labor Report, Product Mix Report) - and no store-vs-store ranking and no variance flags are documented in this report or in the Insights app, whose multi-store view is a plain per-store Total Payments list. https://support.revelsystems.com/s/article/Establishment-Payments-Report · retrieved 2026-08-02 adversarially verified

multi-location-cross-location-giftcard

Gift cards are redeemable across establishments and sales are reported as liabilities, but settlement is manual: 'Revel Systems' Gift Cards do not handle royalties... the establishment in which a gift card is purchased receives the full amount of the gift card, even if the gift card is redeemed at a separate location. For this reason, Revel provides a gift transactions report that shows the variance between establishments and allows merchants to keep track of a central bank and manually calculate royalties for individual locations.' https://support.revelsystems.com/s/article/Overview-of-Revel-Gift-Cards · retrieved 2026-08-04

multi-location-cross-location-loyalty

'Data that Updates for All Establishments' lists Customers and Customer Groups, Gift Cards, and Rewards Cards as data that updates across all establishments on the account URL - so a customer's CRM profile and rewards-card balance are account-wide rather than per-location, and the CRM's customer item/order export can be pulled across selected establishments. https://support.revelsystems.com/s/article/Data-that-Updates-for-All-Establishments · retrieved 2026-08-04

multi-location-multi-brand differentiator

Re-checked the complete 693-article public help-centre mirror (captured 2026-08-04) for virtual brand, ghost kitchen, multi-brand and concept. Only three relevant hits exist: the DoorDash Marketplace article ('If the Virtual Store / Ghost Kitchen has its own establishment in Revel, then it can be integrated... If the virtual store / ghost kitchen shares an establishment in Revel, then it cannot be integrated', plus 'You can only have one store integrated with DoorDash Marketplace per establishment'), the EMS Establishment Hierarchy Tree article ('In a multi-brand company, corporate administrators require different levels of access and control'), and the Branding Tool, which skins CDS XT and Kiosk XT and is listed under Data that Updates for All Establishments. The DoorDash constraints are properties of that integration, not of the POS, and no article enumerates how brands, menus, receipt branding or revenue reporting can be separated within a single establishment or on a single terminal. Positive evidence of absence for the claim as worded does not exist, so this is unresolved rather than no. adversarially verified

multi-location-multi-tax-jurisdiction

Multiple simultaneous individual taxes stack per product (worked example: 10% state + 5% county on one item), tax groups scope taxes to selected products with tax rules and effective dates, Tax by Dining/Order Option applies jurisdiction rules like prepared-food eat-in vs take-out, tax-inclusive products are supported ('removing the tax on all tax included products'), and tax-exempt products are selected per tax group. Configuration is per establishment: EMS deliberately does not push tax settings globally ('This is for security purposes (i.e. tax settings, etc.)'), and establishment groups are recommended where 'you need your tax rates to vary for one state to the next', with station/order-level prevailing-rate overrides gated by permission. https://support.revelsystems.com/s/article/Taxes-Implementing-Different-Tax-Types-1583152075662 · retrieved 2026-08-04

multi-location-central-labor-policy

Time Sheet Rules (per establishment, under Schedules) set daily/weekly overtime and doubletime thresholds and multipliers, seventh-day overtime, auto clock-out, and break rules ('Calculate Paid/Unpaid Breaks By Rules', explicitly referencing California meal-period law), with terminal-level enforcement: 'Prevent Employee Clock-In Before Break End' requires a manager PIN and clock-in-before-shift limits block early punches. Shortfalls: no predictive-scheduling compliance is documented, and Schedules/Time Sheet Rules are not among the documented EMS-pushable scopes, so centrally enforced group-level labor policy is not documented. https://support.revelsystems.com/s/article/Time-Sheet-Rules-1583150213539 · retrieved 2026-08-04

hardware-commodity-devices differentiator

Substantively right (iPad-based POS on off-the-shelf Apple hardware), and the live help site and Revel University document iPad-based operation directly, so confidence can rise above an aggregator claim. Not downgraded, but the citation should not be an aggregator profile. https://reveluniversity.revelsystems.com/s/advanced-features/kds · retrieved 2026-08-01 adversarially verified

hardware-os-platforms

iOS/iPadOS identified as the client platform; minimum OS versions and device specs not published (vendor docs site removed). https://sourceforge.net/software/product/Revel-Systems/ · retrieved 2026-08-01

hardware-handheld-purpose-built

Revel's documented mobile order taker (MOT) is not a purpose-built handheld: v2.77 introduced an 'IPORT mobile order taker (MOT) case' - an iPad in an IPORT CONNECT PRO case with an optional hand strap, paired with a magnet-attached CONNECT PRO PayCase holding a separate Link 2500 or Moby 5500 payment device - exactly the case-add-on architecture this claim excludes. The 'Active Supported Hardware' catalogue ('all the active and supported hardware by Revel Systems') lists no handheld with an integrated card reader, and no drop rating or IP ingress rating is published for the MOT assembly anywhere in the complete help centre. https://support.revelsystems.com/s/article/iPort-stands-and-cases · retrieved 2026-08-04

hardware-handheld-battery-swap differentiator

The handheld is an iPad in an IPORT CONNECT PRO case; the vendor's documented uptime strategy is dock charging, not battery swap: CONNECT MultiDock 6 'simultaneously charges up to 6 devices, each with its own 5V 3A power source' and the CONNECT Dock 'provides PD fast charging to iPad allowing for rapid recharging for minimal downtime of iPads in the field'. No hot-swappable or field-replaceable battery option exists in the Active Supported Hardware catalogue or MOT documentation (the only quick-swap battery mentioned anywhere belongs to the CipherLab 2564 scanner), and no vendor-published full-shift battery rating exists. https://support.revelsystems.com/s/article/iPort-stands-and-cases · retrieved 2026-08-04

hardware-handheld-lte

Re-checked the complete 693-article public help-centre mirror (captured 2026-08-04) for cellular, LTE, 4G, 5G, SIM and hotspot: only three articles hit, and none addresses handheld connectivity. The SAQ merchant-profile guide's 'Revel Systems does not sell card swipes that could be used with a SIM card' concerns payment terminals; the outage playbook's 'Temporarily connect to a Wireless HotSpot' is a manual power-outage workaround; the Inventory FAQs hit is a stocktake question. The iPad Compatibility article's supported/unsupported device chart is enumerated by model generation (iPad Pro M4, iPad Air M2, iPad gen 9/10, iPad mini gen 6, etc.) and never distinguishes Wi-Fi from Wi-Fi + Cellular configurations, and Revel's Best Practices Guide only instructs that 'Mobile Order Takers should always be connected to the Revel Wi-Fi network' - a configuration instruction, not a hardware limit. Nothing documents a cellular handheld or a vendor-supplied failover, and nothing excludes one, so this is unresolved rather than no. adversarially verified

hardware-offline-mode

Withdrawing the reference to the 'Manual Offline Mode on the Point of Sale' article - it did not survive the migration to the Salesforce help centre and is not in the 693-article corpus. It is not needed. The outage best-practices article documents continuity and degradation together, per outage type: with the server down, 'Create and close orders; Operate tills and take cash payments; Take credit card payments; Print to kitchen and receipt printers (ethernet or BT connected); Use CDS & KDS' remain available, while Clock In/Out and reports are 'limited' and the Management Console, 'Use Loyalty/rewards/gift cards', EOD, House Accounts, customer order history and frontend inventory are explicitly NOT available. With ISP down the same shape applies, with 'Process CC / Debit Payments in offline mode' limited and 'Take manual credit card or Debit payments' unavailable. Card-auth degradation is documented separately and at length in the Offline Mode article (offline transactions 'do not communicate with the server or cardholders' bank'). Refund behavior offline is the one item in the claim's parenthetical that Revel does not address. https://support.revelsystems.com/s/article/outage · retrieved 2026-08-09 adversarially verified

hardware-kds

Re-homed off the customer-gated Zendesk section onto vendor hardware and KDS documentation, and the first-party question is now settled by Revel's own catalogue rather than inferred from a docs section existing. Active Supported Hardware lists the 'IC-215P-AA2 MicroTouch (KDS)' all-in-one ('equipped with Rockchip's latest architecture, the RK3399', Ethernet, spec sheet) alongside a 20-key Bump Bar and a Vesa Mount (KDS); the KDS also runs on iPad and on the ViewSonic VSD243, both of which have their own Revel KDS app articles. Station routing: products are assigned to named printers/display units per item or in bulk (https://support.revelsystems.com/s/article/How-to-assign-products-to-kitchen-printers-display-unit-KDS-1583149941086). Course/fire timing: 'Optimize KDS for Coursing... will only send products to the KDS when that course is ready for preparation', with Send to Kitchen on Hold or on Done, and per-product automatic coursing (https://support.revelsystems.com/s/article/Optimize-KDS-for-Coursing-1582899129817). Multi-station flow and expo behavior are documented separately again. https://support.revelsystems.com/s/article/Active-Supported-Hardware · retrieved 2026-08-09 adversarially verified

hardware-kiosk differentiator

Kiosk XT is a first-party self-order kiosk running the same menu and modifier engine as the POS - split modifiers with left/right coverage, group and upsell combos, discount codes, gift cards, Revel and Punchh loyalty, and 'Kiosk XT uses the same settings UI as the regular POS app' - with integrated card payment via Vantiv/TriPOS and FreedomPay pin pads. Named shortfalls: no ADA/accessibility compliance documentation; no documented countertop-vs-freestanding enclosure options (the hardware catalogue lists only iPad stands); payment processors limited to TriPOS and FreedomPay; and documented feature limitations (no customer account creation, no CRM login/order history, most third-party loyalty unsupported, no matrix inventory, no split combos). https://support.revelsystems.com/s/article/Kiosk-XT · retrieved 2026-08-04

hardware-drive-thru

Two elements are documented: an order confirmation display via the Delphi OCS integration ('offer an industry standard drive through order display system ... send order details to a customer-facing drive-thru screen', one POS to one OCS, with a connection-loss alert on the POS; https://support.revelsystems.com/s/article/Delphi-OCS-Integration) and a dedicated Drive Thru Order Queue (v2.72+) that 'places the oldest orders at the top and displays a clear time lapsed stamp', with vehicle-data and call-name prompts and in-queue payment. Named shortfalls: no speaker/headset integration is documented; Digital Menu Boards are documented as indoor flat-screen TVs with no outdoor-rated option; and there is no drive-thru lane timer or speed-of-service measurement (the Speed of Service report measures KDS/kitchen time only). https://support.revelsystems.com/s/article/Revel-Drive-Through · retrieved 2026-08-04

hardware-printer-compatibility

The Active Supported Hardware catalogue lists thermal receipt/kitchen printers from multiple manufacturers, predominantly LAN/Ethernet: Epson T88VII ('Ethernet'), TM-U220, M-M30III (Ethernet/Bluetooth), TM-M30II-SL, P60 (Bluetooth mobile) and TM-L90 Plus, plus the Star MCP31L (Ethernet), alongside Zebra ZD411 and Dymo 550 Turbo label printers - none vendor-branded. The Auto Redirect article separately confirms native Epson ePOS LAN printer support. https://support.revelsystems.com/s/article/Active-Supported-Hardware · retrieved 2026-08-04

hardware-peripherals

The Active Supported Hardware page is a published compatibility list covering the full peripheral set: M-S 16-inch cash drawers, CipherLab 2200/2504/2564 barcode scanners, Brecknell 6702U/6720U scales and the Magellan 9400i scanner-scale for by-weight items, and customer-facing displays (Revel L Stand + CDS). Multi-drawer per terminal is separately documented: 'Revel supports dual cash drawers for one printer' using a CD-D1D2EP splitter, an 'Enable two cash drawers' POS setting, and per-employee drawer assignment with drawer locks (https://support.revelsystems.com/s/article/Running-Dual-Cash-Drawers-Setup-1582902926329). https://support.revelsystems.com/s/article/Active-Supported-Hardware · retrieved 2026-08-04

hardware-p2pe-terminal

Card entry happens on dedicated PCI PTS payment terminals: the SAQ merchant-profile guide states 'The only payment terminals Revel merchants can use are' Ingenico iPP350, iSMP4, Lane 3000, Link 2500, Moby 5500 and Lane 3600, describes them as 'ingenico encrypted swipes', and states merchants 'cannot view full card numbers' and that Revel 'cannot access any Cardholder Data Environment (CDE)'. Named shortfalls: no PCI-validated P2PE solution listing is claimed; the vendor does not state a single merchant SAQ type ('initial business profiling determines which SAQ type must be completed by the merchant'); and quarterly ASV vulnerability scans of the merchant CDE 'under which all POS and payment devices are communicating' are required, indicating the POS environment is not descoped the way a validated P2PE listing would allow. https://support.revelsystems.com/s/article/Merchant-Profile-Questionnaire-guide-for-RA-XT-TriPOS-and-FreedomPay · retrieved 2026-08-04

hardware-tap-to-phone differentiator

Re-checked the complete 693-article public help-centre mirror (captured 2026-08-04) for tap to pay, tap to phone, softpos and contactless-on-device: zero hits. All documented acceptance hardware is a dedicated reader (Ingenico iSMP4 / Link 2500 / Lane 3000 / Lane 3600 / MOBY5500, Verifone V400m, Adyen P400 Plus, Adyen AMS1), and Revel SmartPay is a QR/text payment-link product, not on-device NFC acceptance. The two enumerations previously relied on do not carry a no: the SAQ merchant-profile guide's 'The only payment terminals Revel merchants can use are' list of six Ingenico devices omits the Verifone and Adyen terminals that the Active Supported Hardware catalogue lists, showing it is scoped to that questionnaire's processors rather than to the product; and a hardware catalogue cannot enumerate a software-only acceptance capability. A 2026-08-06 web search surfaced tap-on-phone only for Shift4 Dine / Shift4 Air, a sibling product line, with nothing stating either way whether Revel merchants can use it. Unresolved rather than no. adversarially verified

hardware-pricing-transparency differentiator

Verdict correct, sourcing improper: an affiliate-monetized review site cannot carry 'documented' confidence. The defensible evidence is first-party — the vendor pricing and hardware pages no longer exist (301 to shift4.com/food-beverage) and no SKU pricing is published on any Revel-controlled domain. https://revelsystems.com/pricing/ · retrieved 2026-08-01 adversarially verified

hardware-ownership-vs-lease differentiator

Hardware is documented as sold: the Operations FAQ describes DocuSign 'purchase documents', shipment 'within five (5) business days' after payment, defective-item exchanges and RMA credits for returned items; the Hardware Manufacturer Warranty page states 'Revel ONLY covers the FIRST year of the manufacturer's warranty. After that, please contact the manufacturer directly' - an ownership relationship with the OEM. Named shortfall: no published statement of purchase-versus-lease options or any hardware pricing exists on a Revel-controlled page, so the claim's requirement that 'the vendor states which' is only half met. https://support.revelsystems.com/s/article/Operations-FAQ · retrieved 2026-08-04

hardware-usable-after-churn differentiator

Still unresolved after searching the complete 693-article public help-centre mirror (captured 2026-08-04) - terms searched: cancel/cancellation, reprovision, deactivate, brick, lock, MDM, churn. The Billing FAQ's cancellation section addresses only post-cancellation DATA access ('I already canceled but need to access my data ... Fees may apply'), and no article states whether vendor-purchased hardware remains usable with other software after cancellation. The hardware is commodity (Apple iPads, Epson/Star printers per the Active Supported Hardware catalogue), which suggests reusability, but Revel Guard XT MDM can lock iPads to a single app and assign restriction profiles, so post-churn usability cannot be established in either direction from vendor documentation.

hardware-rma-sla differentiator

A warranty term is published - 'Revel ONLY covers the FIRST year of the manufacturer's warranty', with a per-device manufacturer warranty table (https://support.revelsystems.com/s/article/Hardware-Manufacturer-Warranty-1582902925055) - and the exchange process has stated turnarounds: after support confirms an item 'defective and within warranty, we'll send the exchange documents within two (2) business days', exchange orders ship 'within five (5) business days', and RMA credits issue '5-10 business days after receipt and assessment'. Named shortfall: this is a confirm-then-ship depot exchange, not an advance-exchange or next-business-day swap, and no committed end-to-end replacement turnaround is published. https://support.revelsystems.com/s/article/Operations-FAQ · retrieved 2026-08-04

hardware-byod

Still unresolved after searching the complete 693-article public help-centre mirror (captured 2026-08-04) for BYOD, 'personal device', 'own iPad' and 'personally owned'. The only hit is a Revel Guard XT third-party iPad MDM enrollment note concerning merchant-owned iPads. All POS and mobile-order-taker documentation assumes merchant-provisioned iPads in IPORT cases; no article documents staff running the ordering or payment app on personal phones, and none prohibits it, so there is no documented permission/security model to score in either direction.

hardware-remote-device-management differentiator

Revel Guard XT is 'the single source for managing all the devices in your establishment' - iPads (POS, Kiosk, CDS, KDS, MOT), printers, payment terminals, scanners, scales - reporting Device Status and Connectivity Status per device plus firmware version, iOS version, installed apps and battery charge, with MDM remote actions (test print, 'Reboot Payment Terminal', lock device, install/remove applications, assign restriction profiles, network scans) via the RGXT Canopy portal, and Revel-coordinated 'unattended, overnight App update across all locations' on the Pro tier. Named shortfalls: it requires the separately purchased Revel Guard XT appliance; capabilities are tiered (client-performed updates and self-managed custom profiles only on the White Label tier; Single App Mode unavailable on Baseline); and remote reboot is documented for payment terminals and the Guard device but not for iPads. https://support.revelsystems.com/s/article/RevelGuard-1582903575827 · retrieved 2026-08-04

hardware-selfpour-scales

Still unresolved after searching the complete 693-article public help-centre mirror (captured 2026-08-04) for self-pour, 'pour spout', 'flow meter', 'tap wall', 'beer wall', keg and PourMyBeer - zero hits. The Active Supported Hardware catalogue's scales section lists only weighing scales (Brecknell 6702U/6720U, Magellan 9400i) and no beverage-flow hardware; however, third-party integrations are catalogued on revelsystems.com/partners, outside the help centre, so a partner-delivered pour-to-tab integration cannot be ruled out from this corpus.

hardware-callerid-integration

First-party Caller ID with dedicated hardware: a Basic analog unit ('Whozz Calling? POS', available through Revel), a Deluxe analog unit, and Vertex VOIP Caller ID for SIP lines; 'Whozz Calling ID for Revel POS' also appears in the Active Supported Hardware catalogue (Ethernet). On an incoming call, 'tap the green New Order button. If the number belongs to a customer in your system, the new order will be automatically attached to that customer. If it's a new number, Caller ID will convert it to a new customer account', with per-station enablement under Establishment > Stations, hold/recall of calls, and a month-long call log on the POS. https://support.revelsystems.com/s/article/Caller-ID-1582898972497 · retrieved 2026-08-04

extensibility-public-api-docs

developer.revelsystems.com serves a public Swagger UI listing 14 OAS 3.0 suite specs (v2025.3.0: orders, weborders, products, customers, employees, scheduling, inventory, purchase orders, cash management, house accounts, discounts, tables, taxes, general), readable with no login, NDA or sales call. CORRECTION on re-check 2026-08-10: the guides and changelog the dossier previously credited are gone with the ReadMe tree. An API changelog topic still exists on the support site, so the claim -- which asks only for readable public reference docs -- is met more narrowly than before but is still met. https://developer.revelsystems.com/ · retrieved 2026-08-10

extensibility-api-access-cost differentiator

Assessed against the complete 693-article support.revelsystems.com public help-centre mirror (searched: API, fee, subscription, pricing, developer, partner) and developer.revelsystems.com's FAQ (re-read live 2026-08-05): no page states whether API access is included in the base subscription or carries a per-location fee or plan requirement. The FAQ confirms partner-issued credentials and a partner testing instance but says nothing about commercial terms; the $20/month DoorDash Marketplace integration subscription documented in the mirror shows Revel does price some integrations separately, but that is a marketplace integration, not general API access. Unresolved.

extensibility-free-sandbox differentiator

developer.revelsystems.com's FAQ states: 'If you have signed up as an API partner with Revel Systems, you will be provided a testing instance with a login and password.' Shortfall: the testing instance is issued only after signing up as an API partner (credentials are partner-issued by email, not self-serve), the docs do not state whether partnership or the instance is free, and seeded data is not mentioned. CITATION QUARANTINED 2026-08-10: https://developer.revelsystems.com/revelsystems/docs/frequently-asked-questions is DELETED (404, S3 NoSuchKey) and NO REPLACEMENT WAS LOCATED. The verdict and its reasoning are KEPT -- the page was read and quoted on the date recorded -- but the URL is moved to dead_url and stamped do-not-refetch, because a live URL is an instruction to future tooling. https://developer.revelsystems.com/revelsystems/docs/frequently-asked-questions · retrieved 2026-08-05 · not refetchable · page gone · graded A when read

extensibility-oauth-partner-apps

Verified verbatim: 'The same Client ID and Client secret will be used for all merchants', and 'The Client-Id is the merchant's Revel URL without .revelup.com'. Correct and appropriately harsh. The docs describe partner-credential recovery by automated email and no operator-granted, individually revocable scopes. CITATION QUARANTINED 2026-08-10: https://developer.revelsystems.com/revelsystems/docs/api-platform-authentication is DELETED (404, S3 NoSuchKey) and NO REPLACEMENT WAS LOCATED. The verdict and its reasoning are KEPT -- the page was read and quoted on the date recorded -- but the URL is moved to dead_url and stamped do-not-refetch, because a live URL is an instruction to future tooling. https://developer.revelsystems.com/revelsystems/docs/api-platform-authentication · retrieved 2026-08-01 · not refetchable · page gone · graded B when read adversarially verified

extensibility-webhooks-push

DOWNGRADED yes -> partial on 2026-08-10. The claim asks for real-time pushes across the ORDER LIFECYCLE (created, modified, paid, voided, refunded). The vendor's live webhook request form enumerates six selectable event types -- In/Out Stock, Menu Updated, Order Finalized, Customer Created, Customer Updated, RewardCard Created -- of which exactly one, Order Finalized, is an order-lifecycle event. Webhooks are real and pushed, so the mechanism conjunct is met; lifecycle coverage is not. The dossier's "nine push event types including timesheet entries" came from the withdrawn developer docs and cannot be re-verified. Caveat recorded honestly: this form is a REQUEST form and its event list may not be an exhaustive enumeration of what the platform supports -- it is, however, the only enumeration the vendor currently publishes. https://support.revelsystems.com/s/webhook-access · retrieved 2026-08-10

extensibility-webhook-reliability differentiator

Verified verbatim against the vendor docs: retry delays '1st: 60sec; 2nd: 300sec; 3rd: 900sec; 4th: 900sec'; HMAC-SHA1 X-Revel-Signature plus X-Revel-Instance / Event-Type / Event-Id / Message-Id headers; message log at GET https://api.revelsystems.com/external/message-log. Nine event codes confirmed. One correction: X-Revel-Establishment-Id is documented as OPTIONAL, so the dossier's per-location scoping claim (repeated in multi-location-org-hierarchy) is slightly overstated. CITATION QUARANTINED 2026-08-10: https://developer.revelsystems.com/revelsystems/docs/webhooks is DELETED (404, S3 NoSuchKey) and NO REPLACEMENT WAS LOCATED. The verdict and its reasoning are KEPT -- the page was read and quoted on the date recorded -- but the URL is moved to dead_url and stamped do-not-refetch, because a live URL is an instruction to future tooling. https://developer.revelsystems.com/revelsystems/docs/webhooks · retrieved 2026-08-01 · not refetchable · page gone · graded B when read adversarially verified

extensibility-order-injection-api

Orders is writable (41 GET, 15 each of POST/PATCH/PUT) and weborders adds /specialresources/cart/submit, so a public write API accepts externally originated orders. Whether injected orders fire to KDS/printers as first-class tickets and land in reporting is stated on no live surface, so partial holds. https://oas-prod.s3.amazonaws.com/oas/2025.3.0/orders_suite.yaml · retrieved 2026-08-10

extensibility-menu-write-api differentiator

UPGRADED partial -> yes on 2026-08-10. The claim's three conjuncts are menu items, modifiers AND prices writable, and all three are met on the current spec: Product (get/post/put/patch), Modifier, ModifierClass and ProductModifier (all get/post/put/patch), and prices via ProductVariablePrice (get/post/put/patch) and ProductPriceLifeCycleAction. The dossier's recorded shortfall -- "modifier-tree write depth unverified" -- is REFUTED, not merely re-sourced: ModifierRecipe, ModifierDiscount and ProductModifierClass are writable too. Remaining caveat, which is a sub-surface limit and not an unmet conjunct: PriceTier and ProductPriceTierPrice are GET-only, so tiered prices are read-only. https://oas-prod.s3.amazonaws.com/oas/2025.3.0/products_suite.yaml · retrieved 2026-08-10

extensibility-doordash-preferred differentiator

The mirror confirms Revel ships a direct DoorDash Marketplace integration (support.revelsystems.com/s/article/DoorDash-Marketplace: 'direct integration with DoorDash Marketplace, eliminating the need for middleware', $20/month per establishment), but the claim is DoorDash's 2026 Preferred Integration Partner designation, which only a DoorDash-controlled page can establish. Checked 2026-08-05: merchants.doordash.com/en-us/learning-center/pos-integration-partners and .../preferred-pos-integration-partners both return HTTP 404, and the previously cited get.doordash.com blog URL still redirects into the 404. The DPIP roster is unverifiable from any reachable DoorDash page; unverifiable is not absent.

extensibility-first-party-delivery-integrations differentiator

Direct, middleware-free integrations are documented for two of the three marketplaces: 'Revel now offers direct integration with DoorDash Marketplace, eliminating the need for middleware' ($20/month per establishment Revel subscription, no per-order fees, menu sync via Store Onboarding Webhook) and 'Revel now offers direct integration with Uber Eats, eliminating the need for middleware' (Uber Eats add-on subscription with custom menu/payment/dining option). Shortfall: no Grubhub direct integration is documented anywhere in the complete 693-article help centre, and each direct integration is a paid Revel add-on. https://support.revelsystems.com/s/article/DoorDash-Marketplace · retrieved 2026-08-04

extensibility-middleware-compatibility

Two of the named aggregation middleware platforms list Revel as a supported POS endpoint on their own public integration directories: Otter (tryotter.com/integrations) names Revel among its Point of Sale integrations, and Checkmate/ItsaCheckmate (itsacheckmate.com/integrations) lists Revel among its Point of Sale partners. Both checked 2026-08-05. Revel's own Uber Eats article also references merchants 'previously integrated to Uber Eats through a middleware provider', confirming middleware paths exist. https://www.itsacheckmate.com/integrations · retrieved 2026-08-05

extensibility-accounting-connectors

QuickBooks Online is a genuine native, vendor-maintained connector pushing mapped journal entries, not a CSV drop. Revel documents selectable modules - Sales (required), Payment Reconciliation, Payroll, Inventory, Payout, Location Tracking, and sales granularity as Summary, Summary by Product Classes or Summary by Product - and a mapping screen reached via 'Integration on Revel URL and Select Advanced View Mode' with Revel accounts on the left and QBO accounts on the right. The mapping is deliberately constrained: 'The integration is designed to only allow customers to change accounts to those that make accounting sense and no others', and a companion article enumerates the required QBO account types and subtypes (Income / Sales Of Product Income, Cost of Goods Sold / Supplies Materials-COGS, Other Current Asset / Inventory, Accounts payable (A/P), Discounts/Refunds Given). Named shortfall: the claim requires QBO plus at least one OTHER native vendor-maintained GL connector, and I could not find one. Xero - the second system the original record named - is delivered by Amaka, a third-party middleware vendor whose own site markets the Revel-to-Xero sync, not by Revel. 'Summary by Product' additionally 'will break integration if there are more then 999 products (active and inactive) in Revel'. https://support.revelsystems.com/s/article/QBO-Mapping-and-Modules-1583148058187 · retrieved 2026-08-02 adversarially verified

extensibility-payroll-export

A native ADP export is documented: enable 'Enable ADP Report' under Time Sheet Rules with an ADP Company Code, choose Workforce Now or Total Force format, map each employee's ADP number to the External ID field, then export CSV (ADP) or XLSX (ADP) from Schedules > Payroll. Shortfall: ADP is the only named payroll provider in the complete 693-article help centre — searches for Gusto, Paychex, Paylocity, and 'payroll provider' return nothing — so the claim's two-named-provider threshold is not met; other providers get only generic CSV/XLSX payroll exports. https://support.revelsystems.com/s/article/How-to-Export-Employee-Hours-to-ADP-1583150213536 · retrieved 2026-08-04

extensibility-app-marketplace

Searched the complete 693-article public help-centre mirror (terms: marketplace, app store, directory, integration partners): the help centre documents individual named integrations (QuickBooks Online, Como, Paytronix, LoyaltyPlant, Deputy, Kosmos, Open Dining, Twilio, DoorDash Marketplace, Uber Eats), each enabled through Revel support/operations rather than self-installed, but no browsable marketplace. The site nav's 'Integration Partners' link points at revelsystems.com marketing, which now 301s to www.shift4.com/food-beverage — HTTP 403 on 2026-08-05 — so whether a public, browsable directory still exists cannot be established.

extensibility-headless-embedded

The WebOrders API is documented as the path for external ordering UIs to drive orders into Revel: 'The third party will submit the order to Revel with the price set within their platform. Revel will then accept this price as the product price for that particular order' (WebOrders API Price Override), with a companion WebOrders API Tax Exemption article; the Uber Eats and DoorDash direct integrations run over the same mechanism. Shortfall: this covers order injection by third-party ordering platforms only — no documented full headless mode where a third-party kiosk/drive-thru UI drives the transaction engine including payments, and price override must be enabled by Revel Support account-wide. https://support.revelsystems.com/s/article/WebOrders-API-Price-Override · retrieved 2026-08-04

extensibility-data-portability-exit differentiator

Self-service export is documented: 'Revel provides clients the ability to export any of the 35+ reports available on the Revel Management Console' in six formats (PDF, CSV, Excel, Short, JSON, XML/XLS), and separate tools export customers (Customer CRM Import/Export), products/modifiers (Excel import/export), and order history. Shortfall: exports are one report at a time, capped at a one-year date range per pull (with documented timeouts pushing large accounts to 3-6 month chunks), and no article documents a complete historical bulk export or any contract-end export process. https://support.revelsystems.com/s/article/Exporting-Sales-Data · retrieved 2026-08-04

reliability-offline-order-entry

Revel documents Offline Mode (Always On Mode) as processing transactions through three distinct failure classes: loss of the ISP connection ('Revel runs on a Local Network powered by your ISP'), loss of the management console server ('POS data can't reach the cloud during a server outage'), and loss of the payment gateway/processor. Configurable guardrails are documented in the Management Console - 'Enable offline credit card payments', 'Show warning message before approve offline payment', 'Max amount for single offline payment', 'Max total amount for all unprocessed offline payments', 'Max threshold of total amount for all outstanding declined payments', plus 'Notify if station is offline' with a 5/10/15 minute POS offline interval and Offline Tills Management. Shortfalls: (1) the claim covers ticket routing and check printing during an outage, and neither is separately documented in the offline article - only transaction and payment processing is; (2) 'Offline mode is not available for all payment integrations' per the Payments Overview; (3) on applications older than 2.79 with TriPOS, the POS 'must be physically forced into offline mode by unplugging the ethernet cable', and 'offline mode will not trigger during a partial ISP outage if DNS servers are reachable' - a manual 'Enforce Offline Payments' toggle only arrived at 2.79. https://support.revelsystems.com/s/article/Offline-Mode-Always-On-Mode-1582898971418 · retrieved 2026-08-02 adversarially verified

reliability-offline-card-auth differentiator

Re-homed onto the live Salesforce URL. Cards are captured while the POS has no path to the gateway and forwarded afterwards, not merely refused: 'Enable offline credit card payments' is a Management Console setting, the Adyen section describes 'Store-and-forward payments: the payment terminal approves payments without any verification', and the manual-batching article defines the resulting state as 'Offline (Not Captured in Offline Mode): Customers' payment transaction data has been authorized but was not yet validated by the system... ready for an attempt to be captured once the system is back to online mode', with a Force control on the POS Offline Payments tab. The outage article independently lists 'Process CC / Debit Payments in offline mode' as available during an ISP or gateway outage. Named limits rather than a vague caveat: 'Debit payments can't be accepted in Offline Mode' (Apple Pay does work); offline mode is not available for all payment integrations; TriPOS and FreedomPay iFCC cannot toggle it and must be forced physically; Adyen needs Capture on Swipe and vendor enablement. https://support.revelsystems.com/s/article/Offline-Mode-Always-On-Mode-1582898971418 · retrieved 2026-08-09 adversarially verified

reliability-offline-decline-liability differentiator

Re-homed and re-argued. Who bears the loss is published without euphemism: 'Forcing offline payments is performed at the Merchant's risk. As with any payment taken offline, there is a risk of authorization failure based on card status and available funds which can only be determined once reprocessed when online', with the consequences enumerated as the merchant's - chargebacks ('Your chances of winning are meager if your customer disputes the new authorization... This may result in additional chargeback fees on top of the lost transaction'), credit card fraud, higher processing fees per re-authorization attempt, and PCI DSS exposure. The manual-batching article adds 'Merchants are responsible for their transaction monitoring' and warns that capturing transactions over 30 days old 'carries a high probability of a chargeback. Merchants get fined by fixed rates for each chargeback.' Caps are stated, and there are three: 'Max amount for single offline payment', 'Max total amount for all unprocessed offline payments' and 'Max threshold of total amount for all outstanding declined payments'. Remaining limit: this is operational disclosure, not contractual - no merchant-agreement liability or chargeback-protection language is publicly reachable, and FreedomPay iFCC's automatic daily replay for up to 10 days is the only recovery mechanism documented. https://support.revelsystems.com/s/article/Offline-Mode-Always-On-Mode-1582898971418 · retrieved 2026-08-09 adversarially verified

reliability-lan-degraded-multi-terminal differentiator

Station syncing is documented as local: 'Synced Point of Sale systems share order data in real time through a Main Syncing Station' over the local network using shared network keys, 'so that an order placed on one station can be accessed on another'; and the outage best-practices article documents that during an ISP/network outage stations can still 'Create and close orders', operate tills and 'Print to kitchen and receipt printers'. Named shortfall: no article explicitly states that cross-station check/table sharing keeps working while the internet is down - LAN syncing and offline operation are documented separately, never jointly. https://support.revelsystems.com/s/article/Syncing-and-Non-Syncing-Stations-1582903575834 · retrieved 2026-08-04

reliability-local-transaction-engine differentiator

The ordering path is documented as local rather than cloud request/response: during a full Revel server outage the POS can still 'Create and close orders', 'Operate tills and take cash payments', 'Take credit card payments', 'Print to kitchen and receipt printers (ethernet or BT connected)' and 'Use CDS & KDS'; the Offline Mode article states 'Revel runs on a Local Network powered by your ISP'; and the Syncing and Non-Syncing Stations article documents an on-premise Main Syncing Station (any designated POS station) through which stations 'share order data in real time' and handle credit-card batch processing. https://support.revelsystems.com/s/article/outage · retrieved 2026-08-04

reliability-offline-kds-printing

The outage best-practices article states that during a Revel server outage you can still 'Print to kitchen and receipt printers (ethernet or BT connected)' and 'Use CDS & KDS', and during an ISP/network outage you can still 'Create and close orders' and 'Print to kitchen and receipt printers (ethernet or BT connected)' - kitchen ticket routing and KDS operation continue offline. https://support.revelsystems.com/s/article/outage · retrieved 2026-08-04

reliability-printer-fallback

Auto Redirect (POS 2.70.13+) 'allows temporary and automatically redirect a receipt from non-working or busy printer': an ordered list of fallback printers is retried in a loop three times, and 'if printing fails on all Auto Redirect printers a standard error is displayed'. Named shortfalls: 'Auto Redirect is available for Epson ePOS LAN printers only' and only between matching printer models and types (m30 fails over to m30, U-220 to U-220); configuration is per-POS and 'not shared between POS'; failover to a KDS station is not supported; and staff are alerted only after every redirect printer has failed. https://support.revelsystems.com/s/article/Printing-Failover · retrieved 2026-08-04

reliability-sync-conflict-handling

Still unresolved after searching the complete 693-article public help-centre mirror (captured 2026-08-04) for conflict, 'last write', merge, 'network partition' and resolution behavior. The only 'conflict' hits are unrelated (R212 serial-server reconfiguration, QuickBooks account-mapping constraints, Revel Guard configuration conflicts). The Syncing and Non-Syncing Stations article documents the Main Syncing Station mechanism and the outage best-practices article documents degraded-mode operation, but no article documents how edits made on two stations during a network partition are reconciled.

reliability-offline-feature-matrix

The article previously cited no longer exists in the migrated help centre; this replaces it with a stronger source. Revel's outage best-practices article is a genuine matrix, structured per outage type (Revel Server, ISP/Network, Payment Processor/Gateway, Loyalty/Gift Card, Revel Guard XT, Delivery XT, Auth0, Power) into three explicit tiers: works, 'still be able to access... but they will be limited', and 'will NOT be able to access the following functions'. The unavailable list during an ISP/network outage names the items this claim asks about: 'Use Loyalty/rewards/gift cards', 'Take manual credit card or Debit payments', 'Receive Online Orders on the POS', 'Complete EOD', 'Use House Accounts', 'View customers past orders', 'Utilize inventory management on the frontend'. The Loyalty/Gift Card section goes further and enumerates 'Sell / activate new gift cards; Process gift card payments; Look up gift card balances; Look up reward balances; Accrue loyalty points; Create new loyalty account; Redeem rewards'. The Offline Mode article supplies the payment-side detail ('Debit payments can't be accepted in Offline Mode', 'Apple Pay works in Offline Mode'). Two items in the claim's parenthetical are not addressed anywhere: refunds and text-to-pay. https://support.revelsystems.com/s/article/outage · retrieved 2026-08-09 adversarially verified

reliability-public-status-page

Verified, but the dossier's component list is incomplete in a way that cost it findings. Actual components also include Delivery XT, Driver XT, Revel Guard XT, Revel Data Connector, Loyalty XT, Como, Punchh, Loyalty Plant, Session M, Valutec, SVS, Synergy, Eigen, QSR Automations and User Authentication (Auth0). Loyalty XT (a Revel-branded, Como-powered in-house loyalty product) and Revel Data Connector (a reporting/warehouse feed) are first-party products the dossier never discovered and which likely lift several guest-loyalty and reporting-raw-warehouse-export cells off unknown. No uptime per https://status.revelsystems.com/ · retrieved 2026-08-01 adversarially verified

reliability-247-live-support

The Revel Resource Snapshot lists Technical Support by phone (+1 415.744.1433, Ext. 1, Option 1) and email with 'Hours of operation: 24/7', with no premium-tier qualifier; the 24/7 designation is deliberate, since the same page gives restricted weekday hours for billing (7am-6pm PT M-F), operations (5am-5pm PT M-F) and payments support. The Offline Mode article likewise refers to 'our 24/7 technical support'. https://support.revelsystems.com/s/article/Resources-and-Contacts · retrieved 2026-08-04

reliability-onsite-install differentiator

The onboarding Welcome Checklist states: 'We offer full Management Console Training with either a Remote Installation or Full Onsite Installation depending on the Size and Amount of Equipment being Installed', coordinated through Revel Navigators with a scheduled Welcome Call to 'discuss the full roll out of your New Revel Platform' - first-party onsite installation is offered, with allocation depending on deployment size. https://support.revelsystems.com/s/article/Welcome-Checklist · retrieved 2026-08-04

reliability-menu-build-service differentiator

The Welcome Checklist does direct the merchant to the Menu Build Guide, Products training videos and Excel import ('You should fully set up and configure your system before your go-live date'), but it is a merchant-facing onboarding checklist, not an enumeration of what Revel's implementation organisation performs, and it links out to a Sales advisor, the Revel Navigators team and a Services page for anything it does not cover. Positive counter-indications in the same mirror: Client Training Programs lists 'Must have completed Revel basic training with Professional Services' as a prerequisite, establishing a Professional Services delivery arm whose scope the help centre never states, and Inventory FAQs route merchants to implementation@revelsystems.com for 1:1 configuration sessions. revelsystems.com/services was re-probed on 2026-08-06 and redirects to shift4.com/food-beverage behind a Vercel security checkpoint (HTTP 429), so the services catalogue could not be read. Whether a vendor-performed initial menu build is offered, included or sold is unresolved. adversarially verified

reliability-hardware-replacement-sla

A warranty exchange program with stated turnarounds is included: once support confirms an item is 'defective and within warranty, we'll send the exchange documents within two (2) business days'; orders 'new or exchange' are 'shipped within five (5) business days'; and RMA credits issue 'approximately 5-10 business days after receipt and assessment of the item'. Revel covers the first year of each manufacturer's warranty per the published Hardware Manufacturer Warranty table. https://support.revelsystems.com/s/article/Operations-FAQ · retrieved 2026-08-04

reliability-pci-dss-4-attestation

First-party compliance statement only: 'Yes, Revel Systems is fully PCI DSS compliant and can provide an attestation of compliance (AOC) upon request' (via a customer success manager or risk-payments@revelsystems.com). Named shortfalls: the AoC itself is not published, only supplied on request; Revel states no DSS version anywhere for its own attestation, so v4.0/4.0.1 currency and post-March-2025 future-dated requirement coverage are unevidenced; and no validated P2PE listing is claimed - the only P2PE mentions in the 693-article help centre are gateway/terminal setup pages for FreedomPay and the iPP350, not a Revel listing. CORRECTED 2026-08-06: the previous note inferred that Revel is on PCI v4.0 from the title of the SaferPayments guide 'Merchant Profile Questionnaire guide for RA XT PCI v4.0 June 2024'. That document is scoped to the Revel Advantage XT MERCHANT compliance programme - it walks a merchant through choosing an SAQ type - and says nothing about the version of Revel's own attestation. Same product-scope error as the RA XT terminal list this audit already refuted. https://support.revelsystems.com/s/article/Revel-Advantage-FAQ-for-Merchant-PCI-Compliance · retrieved 2026-08-06

reliability-mfa-role-based-access

Role-based permissions are documented in depth: POS Roles with a rank hierarchy (1-999; 'A POS role with a lower rank cannot view or edit roles of higher rank'), a full permission matrix under Employees > Role Permissions (Owner Access, Manager Access, Batch Process, Offline Payments, Point of Sale Settings, etc.) and separate Administrator Permission Sets for the Management Console. Named shortfall: MFA is documented as required only on the Revel Advantage Payment Portal - 'Starting March 18, 2024, Multi-Factor Authentication setup will be available for enablement and will be a required measure moving forward', via SMS or authenticator app (https://support.revelsystems.com/s/article/Revel-Advantage-Portal-User-Logins) - and no article documents enforceable MFA on Management Console or POS administrative logins (the Management Console runs on Auth0, but its MFA is undocumented). https://support.revelsystems.com/s/article/Employees-Roles-and-Permissions-Guide-1583149941746 · retrieved 2026-08-04

reliability-self-serve-training

Revel University (reveluniversity.revelsystems.com) is a live, publicly reachable structured training library with per-feature courses, alongside the login-free help site. https://reveluniversity.revelsystems.com/s/advanced-features/kds · retrieved 2026-08-01 adversarially verified

reliability-failover-terminal-role differentiator

'You can designate any Point of Sale station as the main station' - so any terminal can hold the master (Main Syncing Station) role - but assumption of the role is not automatic: setup goes through a Revel agent ('To set up syncing stations, contact your Revel agent'), each network key must have exactly one main station ('Two main syncing stations with the same network key can cause problems with syncing payment data'), and no article documents automatic failover of the main-station role when the designated station fails. https://support.revelsystems.com/s/article/Syncing-and-Non-Syncing-Stations-1582903575834 · retrieved 2026-08-04

reliability-cellular-backup

Re-checked the complete 693-article public help-centre mirror (captured 2026-08-04) for cellular, LTE, 4G, 5G and hotspot: the only hits are the SAQ guide's payment-terminal SIM sentence, an Inventory FAQ stocktake question, and the outage article's 'Temporarily connect to a Wireless HotSpot', which appears under Power Outage as a manual workaround rather than under ISP/Network Outage. The outage article is a per-scenario troubleshooting playbook and never claims to enumerate Revel's connectivity options. Against the no, the Active Supported Hardware catalogue's networking section sells the Cisco Meraki MX64 and Z4, and Cisco's own documentation states the MX64 'includes a USB port to support approved 3G/4G cards for failover to cellular networks' - so the vendor-supplied edge device is capable of automatic cellular failover, and only Revel's provisioning and support posture is undocumented. Neither yes nor no is supportable; unresolved. adversarially verified

commercial-month-to-month-contract differentiator

Still unresolved after searching the complete 693-article public help-centre mirror of support.revelsystems.com (captured 2026-08-04) for 'month-to-month', 'contract', 'subscription', 'term' and 'renewal'. The Billing FAQ confirms fixed-term contracts exist ('My contract came to an end and I want to review my service package and price') and that cancellation is by email to cancellationnotice@revelsystems.com, but no article states whether a month-to-month tier is offered or any minimum term length; the vendor's commercial pages (revelsystems.com/pricing, apiterms) remain dead/redirected to shift4.com. The help centre is operational documentation rather than the contract, so absence of a public month-to-month offer could not be converted to no.

commercial-no-early-termination-fee differentiator

Still unresolved after searching the complete 693-article public help-centre mirror of support.revelsystems.com (captured 2026-08-04) for 'termination', 'cancellation fee', 'early termination' and 'liquidated damages'. The only termination-adjacent content is the Billing FAQ's cancellation-by-email process (cancellationnotice@revelsystems.com) and post-cancellation data access ('Fees may apply'), neither of which states whether an early termination fee exists. No MSA or ToS text is published in the help centre, and the 'Revel Systems, Inc. Supplemental Revel Advantage XT Program Terms and Conditions' referenced by the fee-schedule article is not publicly posted.

commercial-autorenew-terms-published

Still unresolved after searching the complete 693-article public help-centre mirror of support.revelsystems.com (captured 2026-08-04) for 'auto-renew', 'renewal' and 'notice'. The Billing FAQ acknowledges contract end and renewal conversations ('My contract came to an end...' - email clientrelations@revelsystems.com) and the Data Access FAQ notes 'Contract renewal does not reset the clock for data access', proving term renewals exist, but no auto-renewal term or required cancellation-notice window is stated in any publicly accessible document; the contract documents themselves are not posted anywhere reachable.

commercial-processing-not-bundled differentiator

Adyen, Worldpay and FreedomPay are monitored as live processor integrations alongside in-house Revel Advantage. https://status.revelsystems.com/ · retrieved 2026-08-01

commercial-interchange-plus-published differentiator

No processing rate of any structure is published; the pricing page no longer exists. https://revelsystems.com/pricing/ · retrieved 2026-08-01

commercial-rate-increase-clause differentiator

Still unresolved after searching the complete 693-article public help-centre mirror of support.revelsystems.com (captured 2026-08-04) for 'rate increase', 'price increase' and fee-change language. The Revel Advantage XT Payment Processing Fees article defines every fee category and cites the 'Revel Systems, Inc. Supplemental Revel Advantage XT Program Terms and Conditions' (section heading 'Transaction Risk Fees') as the governing document, but that document is not publicly posted, so whether vendor-initiated rate increases are capped, prohibited, or grant penalty-free exit cannot be determined from any reachable source.

commercial-pricing-published

Correct, but re-source to the dead first-party pricing page rather than an aggregator profile. https://revelsystems.com/pricing/ · retrieved 2026-08-01 adversarially verified

commercial-module-unbundling differentiator

Modules are separate billing objects: the Billing FAQ's cancellation entry is titled 'How can I cancel my subscription/establishments/add-ons?' - add-ons can be cancelled distinctly from the base subscription (by emailing cancellationnotice@revelsystems.com for a client-relations callback, or via an account manager) - and the Data Access article sells paid data-retention tiers as a distinct purchasable add-on chosen at the legal-entity level. Named shortfalls: cancellation is a manual email/account-manager process rather than self-serve, no a-la-carte module price list is published, and nothing documents whether dropping a module leaves the base POS subscription price unchanged - the no-repricing half of the claim is unverified. https://support.revelsystems.com/s/article/Billing-FAQ · retrieved 2026-08-04

commercial-hardware-purchase-outright

Outright purchase is the documented model, but no prices are published. The Payment Device Purchase Policy requires that 'any form of payment should only be performed through a supported and authorized payment device purchased directly from Revel Systems' (purchase, not lease - no hardware rental or multi-year lease requirement appears anywhere in the complete help centre), and 'Can I set up my own card swipe, iPad, or printer?' concedes 'it is possible for a client to source their own hardware' for commodity items (iPads, printers), though Revel recommends buying pre-configured units from Revel. Named shortfall: no published hardware price list exists on any reachable Revel page, so the 'at a published price' half of the claim cannot be met. https://support.revelsystems.com/s/article/Payment-Device-Purchase-Policy · retrieved 2026-08-04

commercial-hardware-not-locked differentiator

Vendor's own 'Active Supported Hardware' catalogue lists commodity third-party devices throughout: Apple iPad (10th gen), iPad Air (6th gen) and iPad Mini (7th gen) as the POS screens; Epson T88VII, TM-U220, M-M30III, TM-M30II-SL, P60 and TM-L90 Plus plus Star MCP31L receipt/kitchen printers; Zebra ZD411 and Dymo LabelWriter 550 Turbo label printers; CipherLab 2200/2504/2564 scanners; Brecknell 6702U/6720U scales; Cisco Meraki networking. None of these are Revel-proprietary. The named shortfall is confined to payments: the Revel Advantage International FAQ states 'third-party terminals will not work, and only authorized devices that match Adyen encryption can be obtained from Revel', so the card terminal specifically is vendor-supplied. The claim only requires at least one documented non-proprietary option, and the iPad plus Epson/Star ESC/POS printers meet it outright. https://support.revelsystems.com/s/article/Active-Supported-Hardware · retrieved 2026-08-02 adversarially verified

commercial-data-export-self-serve

The public OAS covers orders and line items, payments and cash management, customers and employees, so a documented export API exists. The claim's "without contacting support or paying a fee" conjunct is unestablished on every live surface -- the authentication page that spoke to it has been withdrawn. Partial holds. https://developer.revelsystems.com/ · retrieved 2026-08-10

commercial-export-customer-and-loyalty differentiator

Customer records are readable and writable, and the vendor's webhook request form offers Customer Created, Customer Updated and RewardCard Created events, so guest records and reward-card activity are both machine-readable. Conjunct check, re-measured 2026-08-10: the claim requires guest records AND loyalty balances AND gift-card liability balances. There is NO gift-card resource, tag or path anywhere in the 14 specs, so the third conjunct is unmet and partial holds. https://oas-prod.s3.amazonaws.com/oas/2025.3.0/customers_suite.yaml · retrieved 2026-08-10

commercial-post-termination-export-window differentiator

Post-termination access exists but has no defined window: the Billing FAQ entry 'I already canceled but need to access my data' instructs former customers to contact the billing team, 'and someone can help you access your data. (Fees may apply.)' - so there is documented access after cancellation rather than immediate cutoff. Named shortfall: no defined number of days is specified anywhere, access is a manual, fee-bearing request rather than a self-serve export window, and the in-term Data Access policy already limits included history to a rolling ~13 months with the advice to 'export your data and store it yourself'. https://support.revelsystems.com/s/article/Billing-FAQ · retrieved 2026-08-04

commercial-data-ownership-clause differentiator

Still unresolved after searching the complete 693-article public help-centre mirror of support.revelsystems.com (captured 2026-08-04) for 'ownership', 'owns the', 'your data' and data-rights language. The Data Access article treats exported data as the merchant's responsibility ('Store all exported data securely. This is your responsibility.') and describes Revel-side retention limits and paid retention tiers, but no published terms state that the merchant owns its transaction and customer data or constrain Revel's/Shift4's use or resale of it; the ToS/MSA and the API terms page (revelsystems.com/apiterms) remain unpublished or dead.

commercial-pci-p2pe-tokenization

The encryption half is documented: 'FreedomPay fully protects the merchant environment with validated P2PE (Point-to-Point Encryption)' on the FreedomPay gateway path, and online ordering card storage runs on processor-hosted checkout (Vantiv Hosted Checkout) so the PAN bypasses the merchant environment. Named shortfall: no Revel document names the applicable SAQ or claims scope reduction to SAQ A / SAQ P2PE-HW - the PCI FAQ instead says initial 'business profiling determines which SAQ type must be completed by the merchant' and requires ALL Revel Advantage merchants to pass an ASV vulnerability scan of their cardholder data environment at least every three months, a regime inconsistent with a documented SAQ-A/P2PE-HW scope reduction. https://support.revelsystems.com/s/article/FreedomPay-Setup-1582893044828 · retrieved 2026-08-04

commercial-pci-dss-4-controls

One control is documented, the rest are not: 'Starting March 18, 2024, Multi-Factor Authentication setup will be available for enablement and will be a required measure moving forward in order to enhance the security of your Revel Advantage Payment Portal' (portal.revelup.com), with Text (SMS) or Authenticator App methods (Microsoft/Google/Okta recommended). Named shortfall: MFA is documented only for that payment portal - no MFA is documented for Management Console or POS logins (the POS Authentication article describes no second factor) - the string 'PCI DSS v4'/'4.0.1' never appears anywhere in the help centre, and no payment-page script integrity monitoring per Req 6.4.3/11.6.1 is documented for hosted ordering pages. https://support.revelsystems.com/s/article/Revel-Advantage-Portal-User-Logins · retrieved 2026-08-04

commercial-privacy-dsar-tooling

Deletion tooling is real and in-app: the Customer Personal Data Anonymization feature 'searches for and permanently removes all key information about a customer (name, email, address, phone, date of birth, etc.) from the entire system', run per-customer from Management Console > CRM, with documented under-the-hood behavior (fields nulled; email replaced with noreply+anonymous_<ID>@revelup.com; phone zero-padded to ID; duplicates processed; customer photo deleted; POS logout/refresh required to clear local data; online-ordering account credentials reset). Named shortfalls: the feature must first be enabled by Revel Support, 'there is no way to perform this action in bulk at the moment', no dedicated locate-and-export (access request) workflow is documented beyond ordinary CRM/report exports, and no executable DPA is published in the help centre (the CCPA/privacy pages sit on revelsystems.com outside it). https://support.revelsystems.com/s/article/Customer-Anonymization-1583148890445 · retrieved 2026-08-04

commercial-wcag-kiosk-accessibility differentiator

Still unresolved after searching the complete 693-article public help-centre mirror of support.revelsystems.com (captured 2026-08-04) for 'WCAG', 'VPAT', 'Section 508', 'accessibility conformance' and 'non-visual': zero hits. Kiosk articles (e.g. How to Set Up Custom Menu for Kiosk) do not address accessibility at all, and no accessibility conformance report is published anywhere reachable; revelsystems.com and shift4.com corporate pages that might host a VPAT/ACR remain unfetchable to this pass. Absence from the help centre alone cannot establish no.

commercial-dual-pricing-compliant differentiator

Surcharging is supported but the compliance automation is not documented: Revel documents surcharge creation (a flat 'Surcharge Percentage' applied to every order, configured per establishment in Management Console Settings) and, for AU/NZ on Adyen, per-card-type surcharge values applied on the terminal with an on-screen guest acceptance prompt, a printed-receipt breakdown into order amount and surcharge amount, and automatic surcharge inclusion in refunds. Named shortfall: no automatic exclusion of debit/prepaid cards is documented anywhere - the US surcharge applies to every order regardless of tender - and the surcharging FAQ makes the debit/prepaid exclusion, the 3% cap and the required point-of-entry disclosures the merchant's responsibility ('it is your responsibility as a business owner to stay current with the latest compliance rules and regulations'). Dual pricing / cash-discount mode is not documented at all. https://support.revelsystems.com/s/article/FAQ-Credit-Card-Surcharging · retrieved 2026-08-04