SpotOn

Provides a graphical floor-plan editor where an operator can draw sections, place tables of varying shape/capacity, save multiple floor-plan layouts per location, and assign sections to servers.

order-capture-floor-plan-editor

Table Layout Editor in BOH: "The Table Layout Editor screen will open, allowing you to modify tables, walls, and other layout properties"; multiple layouts per location ("Main Dining Room, Patio, Bar Area, Event Setup"), unique table numbers per location, live edit while open, and a "Table Occupied Time Before Alert" blink threshold. Shortfall: nothing in the POS floor-plan documentation assigns sections to servers — server-to-section assignment is documented only in SpotOn Reserve's Host App, a separately priced product. https://help.spoton.com/space/SK/4711514162 · retrieved 2026-08-03

Order lines can be tagged to a seat number at entry, and the check can be split by seat afterward without re-keying items.

order-capture-seat-level

Edit Guests on an Order: guests carry a "Guest #" label that can be renamed, and "SpotOn Restaurant allows you to organize items by guest and print separate checks for each guest"; the order can be split "by guest or seat". Kitchen tickets can be set to "Sort by Course and Specify Guest Position", where "the guest name or seat number is displayed for each item" (Auto Coursing BOH Setup). Split by Guest divides the check by the items each guest ordered without re-keying. https://help.spoton.com/space/SK/2666561606 · retrieved 2026-08-03 adversarially verified

Items can be assigned to courses and held, with a fire-next-course action available from a handheld or terminal that releases only that course to the kitchen.

order-capture-coursing-hold-fire

Item Commands include Change Course ("changes the course assigned to an item before it is sent"), Hold ("Places an item on hold so it is entered into the order but not sent to the kitchen") and Release ("Releases held items so they can be sent"). Auto Course assigns sequential course numbers. Serve (handheld) exposes Change Course and Autocourse in its Order Commands, so hold/fire is available from the handheld as well as the terminal. https://help.spoton.com/space/SK/2055536951 · retrieved 2026-08-03

Supports splitting a check by item, by seat, by even N-way, and by arbitrary dollar/percentage amount, and merging checks or tables back together, including after partial payment.

order-capture-split-merge

Ticket Commands: "Split by Guest — Use to quickly split guest check by guests"; "Manage — Manage and/or split check(s) by adding guests and moving items"; "Combine Orders — Select from other open orders to combine with current order"; "Move to Table". Item Commands add "Split — Splits an item among the selected number of guests". Split Payment of Check Equally divides evenly and each portion "can be paid using any accepted payment method"; Serve's split screen defaults to 50/50 "but can be adjusted as requested by guests by using the slider bars". https://help.spoton.com/space/SK/2055733392 · retrieved 2026-08-03

Opens a bar tab against a card pre-authorization with a configurable auth amount, supports incremental re-auth as the tab grows, and auto-closes stale tabs at end of day. differentiator

order-capture-bar-tab-preauth

Start a Tab is documented end to end: a BOH "Default Tab Amount", a "Can Start Tabs" permission per job position, "Can Approve Default Tab Amount Adjustments", and "Increment as Tab Increases" so "the card will continue to be pre-authorized as the tab increases with each send (not each item)". Shortfalls: American Express is excluded — "Start a Tab works with Visa, MasterCard, and Discover (American Express is not currently supported)" — Start a Tab "is not available on serve software for handhelds or QR ordering", and no automatic end-of-day close of stale pre-authorised tabs is documented anywhere in the KB. https://help.spoton.com/space/SK/2589261836 · retrieved 2026-08-03

An open check can be transferred between servers, tables, and devices, and the transfer is recorded in an audit log naming both employees.

order-capture-transfer-audit

Ticket Commands document "Transfer — Transfer order to another employee (must be clocked in and eligible to receive order)"; a TRANSFER-equivalent permission sits under Job Positions, and Express documents Check Transferring by employee name which "operates in offline mode". Shortfall: no transfer log or exception report naming both the releasing and receiving employee is documented — transfers appear only as a change of order ownership. https://help.spoton.com/space/SK/2055733392 · retrieved 2026-08-03

Ships a first-party handheld ordering app running natively on the handheld device (not a remote/mirrored desktop session) that can send to kitchen and take a card payment tableside.

order-capture-native-handheld

SpotOn Serve runs natively on the A920/A77 handheld with its own order screens, modifier flow, Print Requisition, Send, and card payment including Split Payment by Guest. A separate SpotOn Express Handheld section and a Mobile RPOS set (Attach a credit card, Completing an Order, Split Payment) document the same for the other two POS lines. https://help.spoton.com/space/SK/2340356127 · retrieved 2026-08-03

With the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen, and tender cash, and the vendor publishes what does and does not work offline.

order-capture-offline-order-entry

Configuring Offline Mode (Express): "Orders and payments continue; data syncs once the internet connection is restored. Orders are still sent to the kitchen printer or KDS," with Auto/On/Off modes and manager-code gating. Shortfall: the same article states plainly "Offline Mode is not available for RPOS devices" — so the offline path is documented for SpotOn Express and the A800 terminal, not for SpotOn Restaurant (RPOS), which is the flagship table-service product. The marketing page at spoton.com/restaurant-pos/ nonetheless advertises an offline mode that "switches on automatically the moment your internet goes down"; the documentation is the more precise source and they disagree. https://help.spoton.com/space/SK/4073652945 · retrieved 2026-08-03

Guest QR at-table ordering writes items onto the same open check as server-entered items, rather than creating a separate order ticket. differentiator

order-capture-qr-same-check

QR Collaborative Ordering puts guest-entered and server-entered items on one ticket: "QR Collaborative Ordering enables guests and staff to collaborate on the same order. It allows staff to start an order with a tab and invite guests (via an SMS link) to view, add, and check out at any time from their mobile devices." It is enabled per location in BOH under QR Order & Pay and invoked from the FOH Ticket Commands menu ("Invite a Guest"), and the guest-side view attributes both sources on the same order: "Items that have been added will be listed underneath the name of the guest who added it to the order... Items displayed under “Unassigned” are items that were added to the order by the server." Settlement closes the POS check via Auto Close When Paid. https://help.spoton.com/space/SK/2797993987 · retrieved 2026-08-03 adversarially verified

Offers a first-party self-order kiosk that renders the same menu and modifier tree as the POS with no separate menu build, and the vendor documents ADA/accessibility conformance for it. differentiator

order-capture-kiosk-first-party

SpotOn Express treats Kiosk as a first-party device class: Offline Mode is configured "on SpotOn Express POS and Kiosk devices", menu categories can be excluded per "POS, Handheld, and Kiosk" surface, and Express Checkout notes "Cash (Not supported on Kiosks)" — so the kiosk runs the Express menu engine. Shortfalls: no kiosk is documented for SpotOn Restaurant (RPOS), where kiosks are supplied by the Bite Kiosk and Reddie Group integrations; and no ADA or accessibility conformance is documented for any SpotOn kiosk. https://help.spoton.com/space/SK/4073652945 · retrieved 2026-08-03

Supports drive-thru-specific order flow: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment.

order-capture-drive-thru

SpotOn Express carries a Drive Thru order type alongside Dine In, Delivery and To Go (Change Order Type: custom order types are unsupported, 'One exception is Drive Thru', added by SpotOn Support), and an RPOS station can default to Drive-Thru as its order type (Prompt for Order Type When Starting New Order). Shortfalls: it is an order-type label only - no order-point/pay-window separation, no lane sequencing or tandem-lane assignment, no pull-forward or parking-spot assignment; Express cannot route tickets by order type (Print Routing Setup from POS FAQ: 'No. Currently, SpotOn Express does not support routing based on order type'). https://help.spoton.com/space/SK/3615883324 · retrieved 2026-09-03 adversarially verified

Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.

order-capture-drive-thru-timers

CLAIM: captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders. VERDICT: no (moved from unknown). NEW SURFACE, published since the last pass: 'Kitchen Performance Report for Fresh KDS | Dashboard' (help.spoton.com/space/SK/5087166465 Express and /5037785135 Restaurant, both version 2026-09-11). This is SpotOn's WHOLE speed-of-service reporting surface and it is Fresh-powered and view-only: 'FreshKDS users can now access Fresh-powered kitchen performance metrics directly within the SpotOn Dashboard'; 'Known Limitation: Currently, the Kitchen report in the SpotOn Dashboard is view-only'. Its complete metric list is KDS Orders Processed, 'In-Store POS Median Bump Speed' ('The median time it took the kitchen to finish ASAP orders (orders without a quoted pickup time)'), 'Online Median Difference from Pickup', calendar heat maps, the two trends, 'KDS Orders Processed by Type' ('Hover over dates to see order type counts (e.g., for here, pick up, etc.)') and 'KDS Order Details' - one kitchen median, no lane/order/window segment and no drive-thru cut. The KDS itself enumerates the order types: 'Each order is assigned 1 of 3 order types: Dine in, To go, or Delivery' (4341727233; the three names sit in separate bold spans in the raw storage body, checked) and its only timer is per-ticket completion ('the time it took for each ticket to be completed. The timer stops as soon as the ticket transitions to complete'), which resets to 00:00 on split or combine. CONTROLS: drive.?thru over the census appears only as an ORDER TYPE or a dashboard label, never as a timer; 'speed of service' as a phrase appears in no metric definition. This adds to the 320th/323rd bundle censuses (1,234 merchant-dashboard files, the 255-file reporting app, RPOS BO+FOH, the 482-source settings map set), where drive.?thru resolved to the 'Fulfillment mix' tile alone. BOUND: the FIRST full-BODY census of help.spoton.com, taken from the publisher's own listing (Confluence v2 API https://help.spoton.com/api/v2/pages?limit=100&sort=-modified-date&body-format=storage, paged to fixpoint - rounds 29 and 30 returned 0 new pages): 2,145 pages WITH BODIES (1,083 current + 1,062 archived), 4,154,015 chars of tag-stripped text, version dates 2020-11-24..2026-09-17. Validation: 141 of the 142 help-centre page ids already cited in this record are inside the listing; the one absent (4456513592) now 404s on the API itself, so the KB is a census minus one deleted page. Prior passes held bodies for only the 121 most-recently-modified pages and titles for the rest. Controls are tokenised word-boundary case-insensitive over all 2,145 bodies; the denominator is 2,145. Retrieved 2026-09-17. https://help.spoton.com/space/SK/5087166465 · retrieved 2026-09-17 adversarially verified

Vendor ships a first-party AI voice ordering agent for phone and/or drive-thru that injects orders directly as POS orders, or publishes a documented API partner program for third-party voice AI. differentiator

order-capture-voice-ai

Loman AI is a documented SpotOn integration providing "a 24/7 AI phone answering service tailored for restaurants... enabling restaurants to automate phone-based tasks such as order taking, reservation management, and customer inquiries", and a companion article documents Loman voice reservations writing into SpotOn Reserve in real time. Popmenu is documented with "AI Phone Answering". Shortfall: neither is first-party — SpotOn ships no voice agent of its own — and SpotOn publishes no API partner programme a third-party voice vendor could self-serve against. https://help.spoton.com/space/SK/4801134599 · retrieved 2026-08-03

Supports order throttling: per-channel capacity limits per time slot with automatic quote-time extension when kitchen load exceeds a configured threshold. differentiator

order-capture-throttling

Order Pacing "helps restaurants manage online order volume by controlling how many orders can be accepted during specific times of the day", enabled by an Order Pacing checkbox, and is described as ensuring "customers receive accurate wait times during peak hours". Shortfall: it is a fixed per-time-slot cap on SpotOn's own online ordering channel — the same article states "Orders submitted through third-party services or integrations, including DineLoyal, ItsaCheckmate, DoorDash Marketplace, Uber Eats, and similar platforms, are not managed by Order Pacing" — and no automatic quote-time extension driven by kitchen load is documented. https://help.spoton.com/space/SK/1792245867 · retrieved 2026-08-03

Accepts future-dated/scheduled orders with a per-channel lead time and automatically injects them into the make queue at a computed fire time rather than on receipt.

order-capture-scheduled-orders

"Scheduled Order — Use to create/edit scheduled orders for a later date/time. Minutes Before to Release determines when the ticket is sent to the kitchen", with "Release Scheduled Order" to override the computed fire time. Express adds Scheduled Online Ordering with a choice between lead-time-based release and release-immediately, per channel. https://help.spoton.com/space/SK/2055733392 · retrieved 2026-08-03

Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.

order-capture-catering

Scheduled Orders explicitly cover the catering case — "ideal for catering orders, large group reservations, special events" and "accepting installment payments for a large catering order" — and the pieces exist around it: a Catering order type with automatically applied surcharges, Open Items for room rentals and custom charges, House Accounts for billing, and Paid In for "catering or event deposits". Shortfall: there is no distinct catering module — no quote or proposal object, no separate catering menu with its own minimums and lead-time rules, and no event schedule separate from the order queue. https://help.spoton.com/space/SK/814088713 · retrieved 2026-08-03

Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator

order-capture-order-ready-signal

Marking Online Orders Ready for Pickup: staff mark an online order Ready from the RPOS or Express POS (All Orders > Online Ordering > Mark as Ready); 'For supported online ordering services - such as DoorDash, Uber Eats, and SpotOn Order (including orders placed through the GoTo Place app) - this action will automatically send notifications to guests and couriers'. The status update takes 15-30 seconds and applies 'if supported by the delivery service'. https://help.spoton.com/space/SK/4295032833 · retrieved 2026-09-03 adversarially verified

Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.

order-capture-void-comp-controls

Job Positions carry discrete permissions and the FOH gates Void behind them — Item Commands note "The Remove command is available only for items that have not yet been sent... use Void instead (if your permissions allow it)" — and manager approval is enforced by manager code or manager card. Shortfalls: no reason-code requirement is documented for voids or comps (Express states outright that "No sale, Pay in, and Pay out reasons are preset and cannot be customized"), and no comps/voids exception report attributing the approver is documented in the reporting set. https://help.spoton.com/space/SK/2660663297 · retrieved 2026-08-03

Supports modifier groups nested at least three levels deep, each level with independent min/max selection counts and a forced-selection (required) flag.

menu-pricing-nested-modifiers

Forced selection and min/max are both documented: Choice Modifiers ("Forced Modifiers") make a selection mandatory with an orange blinking indicator, and sub-item linkages carry Min and Max ("If Min is blank, the order flow can proceed without selecting any sub items. If Max is blank, an unlimited number of sub items can be added"). Shortfall: modifiers explicitly do not nest — the Sub Items comparison table scores "Offer different choices based on previous selection" as No for Modifier and Yes for Sub Item, and the prose states "Modifiers do not provide a way to ask the dressing question only when the salad option is selected." Conditional depth therefore requires building a second menu-item group as a sub-item group; three-level nesting is nowhere documented. https://help.spoton.com/space/SK/2658076199 · retrieved 2026-08-03

A single modifier can carry different prices depending on the parent item and the selected size, configured as a matrix rather than by duplicating the modifier.

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

Modifier prices are real and configurable: "Under the Modifiers section, select Edit Modifiers... Scroll to Location Specific Settings. Under Pricing, enter the desired price", and modifiers "Obey Price Levels" so an alternate price can be attached to a Price Level. Shortfall: there is no size x modifier price matrix. Size is itself modelled as a Choice Modifier group or a sub-item group ("unless that subgroup is used as a size choice (for example, pizza sizes)"), so a topping that costs more on a large is achieved by duplicating the modifier group or the Price Level, which is precisely the maintenance problem the claim describes. https://help.spoton.com/space/SK/5254742018 · retrieved 2026-08-03

Supports fractional/sectioned modifier placement (at minimum halves, ideally quarters) with independent pricing per section. differentiator

menu-pricing-fractional-placement

Half-and-half is documented and vendor-recommended, but as duplicated groups rather than as placement: "Pizza – Correct Setup. Correct Configuration (Best Practice): Create separate groups for each half: Toppings – Left Half, Toppings – Right Half. This allows customers to customize each half independently without conflicts." The wrong configuration is reusing one Toppings group twice, which "prevents proper selection for half-and-half pizzas". Shortfall: this is the Side-A/Side-B duplicated-modifier-set pattern, not a section attribute on a topping — there is no portion/placement field, no quarters, and no per-portion price multiplier. Each half's pricing is independent only because it is a separate group. https://help.spoton.com/space/SK/5040406703 · retrieved 2026-08-03 adversarially verified

The half-and-half pricing rule is operator-configurable among at least two of: charge the higher-priced half, average the halves, or charge each topping at a fraction of full price. differentiator

menu-pricing-half-and-half-rule

The Sub Items article enumerates the entire pricing choice for a sub-item linkage: "Choose a Price Level in the Pricing drop-down. If the price of the sub items is included in the parent item, select None. Current uses the Standard price of the menu item. Other price levels are created in the Price Levels section... Rollup Pricing adds the price of the sub item to the parent item." It also names half-and-half as the canonical use: combining two specialty pizzas is where "sub item items are often the best way to calculate the correct price". Shortfall: of the three rules the claim asks for, only "charge each half at a fraction of full price" is reachable, and only by hand-entering a dedicated Price Level per item. There is no higher-of-the-two-halves rule and no averaging rule anywhere in the enumerated options. https://help.spoton.com/space/SK/2658076199 · retrieved 2026-08-03

Supports modifier quantity tiers (light / regular / extra / double) with a configurable price multiplier per tier, distinct from adding the modifier twice.

menu-pricing-topping-quantity-tiers

Modifier Options are the tiering mechanism and are documented: "Modifiers Options indicate how the Menu Item is to be modified, i.e., extra onion, no onion, onion on the side", named "Add, No, Extra, Sub, On Side, etc." with a per-option button colour. Shortfall: no price multiplier is attached to the option. Pricing lives on the modifier itself under Location Specific Settings, so "Extra Cheese" and "Cheese" carry the same price unless the operator builds a second priced modifier — the doubling-by-duplication the claim excludes. https://help.spoton.com/space/SK/2658075833 · retrieved 2026-08-03

Item base price can be defined as a grid across two variant axes (e.g. size x crust/preparation) with a per-cell price override. differentiator

menu-pricing-size-style-matrix

Two axes are constructible: sizes are documented as a sub-item group ("unless that subgroup is used as a size choice (for example, pizza sizes)") and a second axis as a further group or Choice Modifier, with Rollup Pricing or a Price Level supplying the price. Shortfall: there is no grid UI and no per-cell price override — a 5-size by 4-crust menu is priced by populating Price Levels item by item, and the Menu Best Practices article warns that reusing a group across slots "causes conflicts", so each cell needs its own group. https://help.spoton.com/space/SK/2658076199 · retrieved 2026-08-03

Items can define an included-modifier allowance (e.g. three toppings included) that automatically charges only for overage and credits or forbids substitutions per configuration. differentiator

menu-pricing-included-allowance

The allowance-and-overage pattern is documented explicitly: "If the parent item includes one sub item, but additional sub items can be added for a price, consider attaching the sub item group twice: Once with Max: 1 and Pricing: None, and again with no Max and a different Price Level." Shortfall: the allowance is expressed as two linkages rather than an included-count field, there is no substitution credit or substitution-forbidden setting, and the same construction has to be repeated on every item. https://help.spoton.com/space/SK/2658076199 · retrieved 2026-08-03

Supports combo/meal construction where components can be swapped with a price delta, and the system can automatically detect and convert eligible a-la-carte items in the cart into the combo price.

menu-pricing-combos

SpotOn Express ships genuine combo items: "combo items allow merchants to bundle multiple menu items together and offer them as a single menu option at a set price", configured from predefined item groups called combo options. RPOS builds combos from unique sub-item groups per slot ({Combo} Combo Choice 1/2/3). Shortfalls: no automatic detection or conversion of eligible a-la-carte items in the cart into the combo price is documented on either product, component swap price deltas are handled by Price Level rather than a delta field, and Express notes "Skip Modifier Screen is not yet supported for combo items." https://help.spoton.com/space/SK/4969463882 · retrieved 2026-08-03

Upsell/suggestive-sell prompts can be configured per item and per channel (POS, kiosk, online), and the vendor reports attach-rate on those prompts. differentiator

menu-pricing-upsell-prompts

'The Upsell Items tab allows users the ability to suggest another item that goes well with the selected item when checking out in Interact.' Per item, POS channel; kiosk too ('Upsell Item Text... to upsell recommended items to guests. This is configured in Connect'). Shortfall: SpotOn Enterprise only, both pages archived, no attach-rate report anywhere. https://help.spoton.com/space/SK/2413297699 · retrieved 2026-09-05 adversarially verified

A single 86 action propagates automatically to POS, KDS, the vendor's own online ordering, kiosk, and connected third-party marketplaces, with a documented propagation latency.

menu-pricing-86-propagation

86 is a first-class FOH action: "Tap and hold the Menu Item button... Tap 86 Item", the item greys out, and Quantity on Hand hitting zero can 86 it automatically. Outbound propagation is documented only through partners — Chowly "ensures item availability and 86 status is always reflected in your 3rd party marketplaces", Deliverect "syncs your POS menu across all connected marketplaces in real time", and Uber Eats "publishes items, prices, and availability to Uber Eats in real time". Shortfalls: propagation of an 86 to SpotOn's own online ordering and kiosk surfaces is nowhere stated, and no propagation latency is published for any channel. https://help.spoton.com/space/SK/2665578707 · retrieved 2026-08-03

Supports per-item countdown/par counts that decrement on sale and automatically 86 the item at zero, with a scheduled auto-restore. differentiator

menu-pricing-countdown-auto-86

Quantity on Hand is a real countdown: "When enabled, menu items will display the remaining quantity available and automatically become unavailable once inventory reaches zero", and the bulk editor confirms "Use Quantity On Hand – Enable this option to automatically subtract sold items from inventory." Shortfalls: no scheduled auto-restore exists — restoring availability is a manual "Make Available" or a manual quantity edit — and the feature is absent from the newer product entirely: "Quantity on Hand is not available in SpotOn Express." https://help.spoton.com/space/SK/2299887676 · retrieved 2026-08-03

Menus, individual items, and prices can be scheduled to activate and deactivate automatically by day and time in the location's own timezone.

menu-pricing-dayparting

Price Levels and Pricing Events: "A Price Level acts as a pricing label (such as Happy Hour or Late Night)... A Pricing Event uses those Price Levels — or other price adjustments — to automatically apply pricing changes during specific days, times, or conditions", and can also drive "item availability changes". Fiscal hours are separately configurable per location (Customizing Fiscal Hours), and Location Specific Settings shows "all active or scheduled Pricing Events (e.g., Happy Hour, specials) associated with the item at this location." https://help.spoton.com/space/SK/752222269 · retrieved 2026-08-03

Supports distinct price books per channel (dine-in, pickup, delivery, kiosk, each third-party marketplace) including percentage-markup rules applied to a base price rather than manual per-item entry.

menu-pricing-channel-price-books

Channel pricing exists on two axes: Order Types carry "Price Level: Use this to set a Price Level to use for all Menu Items", so dine-in, carry-out and delivery can each run a different price book; and DoorDash marketplace pricing is a percentage markup applied in the SpotOn Dashboard rather than per item ("Navigate to Dashboard > Integrations > DoorDash > Price Markup. Select a price markup percentage"). Shortfalls: the markup rule is documented only for DoorDash Marketplace delivery — "There is not currently a setting for Marketplace pickup menu prices, or Storefront menu prices" — and no per-marketplace price book exists for Uber Eats or for kiosk. https://help.spoton.com/space/SK/2659516933 · retrieved 2026-08-03

Supports dual pricing / cash-discount at the item level with the card price displayed as the base price, applied consistently across POS, kiosk, and online ordering, and printed on the receipt. differentiator

menu-pricing-dual-pricing

Dual Pricing is a shipped, documented programme: "Our Dual Pricing solution displays two pricing options to the customer when they are making a purchase. This allows the customer to see both totals and choose their method of payment", with automatic discount handling on cash tender and a configurable POS Tender Discount percentage. Shortfall: the article requires the operator to display both prices on menus and signage and describes receipt footers as a disclosure mechanism; it never documents both the cash and card totals printing on the guest check itself, and it does not state that the programme applies on kiosk or in online ordering. https://help.spoton.com/space/SK/4166484081 · retrieved 2026-08-03

Stores allergen flags and nutrition values per item and publishes them to online ordering and third-party menus, and can derive nutrition from linked recipe components rather than manual entry.

menu-pricing-allergen-nutrition

RPOS Menu Item Creation: each menu item carries a Menu Facts field for 'Serving Size, Calories, Calories from Fat, Total Fat, Saturated Fat, Trans Fat, Cholesterol, Sodium, Total Carbohydrate, Dietary Fiber, Sugars, Protein', and staff or guests can view it in FOH by long-pressing the item and selecting Item Info. Shortfalls: no allergen flags (the only allergen mention is a prose suggestion in the Express item-description article); no publication of Menu Facts to SpotOn Order, the GoTo Place app or third-party menus is documented; values are keyed by hand, not derived from linked recipe components. https://help.spoton.com/space/SK/2656960513 · retrieved 2026-09-03 adversarially verified

Menu items and modifiers can be linked to recipes/bills of materials so that a sale depletes theoretical inventory and yields item-level theoretical food cost. differentiator

menu-pricing-recipe-linkage

The menu item carries a single flat cost field and nothing else: "Item Cost – Enter the actual cost of the item (not the selling price)... Item Cost refers to the internal cost of the item to the business." No recipe, bill of materials, or component linkage exists on the item record. Recipe costing is explicitly the partners' job — MarginEdge is described as "a recipe cost-tracking and restaurant inventory management solution" that SpotOn feeds sales data to, and COGS-Well, Craftable and BevSpot occupy the same slot. https://help.spoton.com/space/SK/2658041953 · retrieved 2026-08-03

Pushes menus to third-party marketplaces through a certified direct integration (not scraping or a menu-management middleman) and surfaces per-item sync status and rejection errors to the operator.

menu-pricing-3p-menu-push

Direct, certified push exists for two marketplaces: "Menus from the SpotOn POS are automatically kept in sync, and orders from DoorDash are injected directly to the SpotOn POS", and Uber Eats "SpotOn automatically publishes items, prices, and availability to Uber Eats in real time". Sync failure is surfaced to the operator with a named error and a retry: "Error: Menu Sync Failed... select the Try Again option to reinitiate the syncing process." Shortfalls: the error is whole-menu, not per item — no item-level rejection detail is documented — and Grubhub is reachable only through Chowly, Deliverect or Checkmate middleware. https://help.spoton.com/space/SK/4629856267 · retrieved 2026-08-03

Supports rule-based dynamic pricing where item price varies automatically by time, demand, or channel, with configurable floor/ceiling guardrails.

menu-pricing-dynamic-pricing

RPOS Pricing Events 'automatically adjust Menu Item prices based on selected Order Types, dates, days, and times', with Price Levels as alternate price fields per item and advanced events such as BOGO; events can be customised per location. Shortfalls: rules are schedule- and order-type-driven only - no demand- or volume-driven pricing, and no floor/ceiling guardrails; Express offers scheduled discounts rather than pricing events. https://help.spoton.com/space/SK/5529468936 · retrieved 2026-09-03 adversarially verified

The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator

payments-processor-choice

More than one acquiring rail is visibly configurable in BOH: Start a Tab requires "valid TransIT credentials", instructs that "all PAX devices have the Payment Terminal Credit Card Processor set to PAX/TransIt", warns that "having PAX/TSYS enabled will not be recognized for Start a Tab", and a sibling article covers "QR Start a Tab on WorldPay". The public status page separately lists TSYS and Worldpay payment components. Shortfall: these are SpotOn-provisioned processors behind SpotOn's own merchant agreement, not an operator choice — no documented list of supported third-party gateways exists, and the POS Terms treat the POS subscription and the processing agreement as a single contract. https://help.spoton.com/space/SK/2589261836 · retrieved 2026-08-03

Vendor publishes card-processing pricing publicly (a specific flat rate or interchange-plus markup) rather than quote-only. differentiator

payments-published-rates

Specific card-present rates are published per plan on the public pricing page - POS Essentials at "Card present: 2.45% + $0.15 (except Amex: 3.19% + $0.15)" and "Keyed: 3.45% + $0.15", All-In at "Card present: 2.79% + $0.20" and "Keyed: 3.79% + $0.20". Shortfalls: the third plan (Build Your Own) is quote-only at "Custom rates"; no interchange-plus markup is published anywhere, so the disclosure covers only the blended structure; and the evidence is a vendor pricing page rather than documentation, which is not strong enough to carry a yes on a differentiator under this rubric. https://www.spoton.com/pricing/ · retrieved 2026-08-03 adversarially verified

Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator

payments-dual-pricing

Dual Pricing stores a card price and applies a cash discount automatically: "Dual Pricing is a type of cash discount program, so by default it will discount your item price when cash is selected", with "Automatic discount handling — SpotOn's solutions can automatically apply the discount when cash is selected" and a POS Tender Discount percentage that must match the posted signage. Shortfall: the documentation covers the discount at tender and the disclosure obligations, but never states that both the cash and card totals print on the guest check and receipt — receipts are described as carrying a footer disclosure of the programme. https://help.spoton.com/space/SK/4166484081 · retrieved 2026-08-03

Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator

payments-surcharge-guardrails

Automatic exclusion and the network cap are both documented: "SpotOn’s Credit Card Surcharge automatically applies the surcharge to credit card transactions, but not debit or prepaid transactions", extending to "debit or prepaid card transactions processed as credit (bypassing PIN)"; and surcharges are "limited to the lesser of either the merchant’s current discount rate (as specified by card network rules), or 3% of the transaction total", with a documented 2% ceiling in Colorado and Oklahoma. Shortfalls: no per-location enable/disable control is documented anywhere - eligibility is described per merchant and per state (excluding Connecticut, Maine and Massachusetts, and merchants holding a direct Amex agreement) and enrolment runs through a "Get Started with Surcharging" request rather than a settings toggle; and two channels sit outside the engine entirely - "Does the surcharge apply to Manual Entry sales? No" and "Does the surcharge apply to Online Ordering sales? No", both marked coming soon. Surcharging also cannot be combined with any other programme: "if a business is surcharging, that is the only program that the business can use." https://help.spoton.com/space/SK/4126277723 · retrieved 2026-08-03 adversarially verified

All first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay.

payments-emv-nfc

Express Start-A-Tab documents both chip and contactless acceptance at the terminal: "When starting a tab via chip reader, the customer's name will automatically be read from the card itself. Customers who use tap to pay will still need their name entered manually." SpotOn Mobile "makes it easy to accept tap, swipe, and cash payments from an iOS or Android mobile device", and the Virtual Terminal article documents Google Pay acceptance. https://help.spoton.com/space/SK/3566862372 · retrieved 2026-08-03

Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. differentiator

payments-softpos-tap-to-pay

SpotOn's only phone-based acceptance product, SpotOn Mobile, 'makes it easy to accept tap, swipe, and cash payments from an iOS or Android mobile device' only through its Bluetooth card reader ('SpotOn account must be activated before connecting the Bluetooth card reader to a mobile device'), and that reader is deprecated: 'we do not offer any swaps or replacements. Please consider a hardware upgrade if needed' (Connecting the SpotOn Mobile Card Reader). The Express Start-A-Tab reference to 'Tap to Pay' is the terminal's NFC reader. No Tap to Pay on iPhone or Tap to Pay on Android acceptance exists in the knowledge base, on the handheld page or on the pricing page, which refuses customer-owned tablets outright. https://help.spoton.com/space/SK/1091043420 · retrieved 2026-09-03 adversarially verified

Vendor ships a handheld that takes EMV/NFC payment at the table, including tip prompt and check splitting, without carrying the card away.

payments-pay-at-table

SpotOn Serve on the A920/A77 handheld runs the full tableside flow: create order, add guests, apply payment, Split Payment by Guest with adjustable slider bars, tip prompt, and Print Requisition — all on the device, with the integrated card reader. https://help.spoton.com/space/SK/2340356127 · retrieved 2026-08-03

Guest can scan a QR code on the printed check or table tent to view and pay the check from their own phone, with the payment closing the check in the POS automatically. differentiator

payments-qr-guest-pay

QR Scan & Pay lets guests "browse menus, place orders, pay checks, tip staff, and redeem Loyalty rewards through QR codes"; QR codes "can also be printed on guest receipts". Settlement closes the POS check: "Auto Close When Paid — Enabled" is the documented configuration, and Mobile Pay & Review states "the table is cleared if Auto Close When Paid is enabled". Notify Staff of QR Payment prints a slip at a designated station on payment. https://help.spoton.com/space/SK/2457829381 · retrieved 2026-08-03 adversarially verified

Supports both pre-auth-then-tip-adjust and on-device tip prompt flows, with a documented batch/adjust window and a manager screen for unadjusted tips.

payments-tip-adjust

Both flows are documented: on-device digital tip screens (Express "Manage Digital Tips Pre or Post-Payment", and tip screens on CFD, handhelds and kiosks) and post-authorisation adjustment from the POS — "Adjust Tips from the List Orders Screen" and "Adjust Tips from the Show Commands Menu", including per-order-type suppression of tip prompts. The adjust window is bounded by batch: Auto End of Day Time and unified batch settings are documented in BOH and the Dashboard, and partial tip refunds/edits are covered separately. https://help.spoton.com/space/SK/2403238344 · retrieved 2026-08-03

Configurable tip pooling and distribution rules (by hours worked, sales, role percentage, or points) that produce a per-employee tip allocation exportable to payroll. differentiator

payments-tip-pooling

RPOS Teams is a real pooling mechanism: members are added to a team, the pool is allocated "by percentage of hours each member worked on the team", and "Team tip distribution appears in the Team Closeout section under Closeouts, above individual employee closeouts". Express adds a Dashboard Tip Pooling feature. Shortfalls: hours-worked is the only documented allocation basis on RPOS; Express pooling "is disabled by default and must be explicitly enabled per location" and "applies only to credit card tips"; and role-percentage, points and sales-based rules are reached only via SpotOn Teamwork (a paid add-on) or the TipHaus/GratShare partner integrations. https://help.spoton.com/space/SK/2021425371 · retrieved 2026-08-03

Card payments can be captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. differentiator

payments-offline-store-and-forward

Store-and-forward is documented in detail on the A800 terminal, with exactly the limits the claim asks for: "Payments are stored securely on the device. Transactions are not approved in real time... Offline Mode includes limits: Maximum amount per transaction; Maximum total amount accepted offline; Maximum time the terminal can remain offline. If a limit is reached, new offline payments will be declined." Express POS and Kiosk carry a comparable Auto/On/Off offline mode. Shortfall: the same Express article states "Offline Mode is not available for RPOS devices", so the flagship restaurant POS has no documented card store-and-forward path. https://help.spoton.com/space/SK/4658331708 · retrieved 2026-08-03

Vendor publicly documents who bears the loss when a stored offline transaction declines on reconnect, and surfaces a post-reconnect report of failed offline payments. differentiator

payments-offline-decline-liability

Liability is stated plainly and repeatedly: "Funds are not guaranteed, as payments are not processed until the device reconnects"; "Offline payments may still be declined later when they are processed online"; and on SpotOn Lite, "Note before proceeding: You are fully liable for failed captures, chargebacks, and disputes of offline payments." The caps are published (per transaction, cumulative, and maximum offline duration). Shortfall: no post-reconnect report of failed offline payments is documented — the article says only that reporting does not update while offline and that stored payments are lost if the terminal powers off before reconnecting. https://help.spoton.com/space/SK/4658331708 · retrieved 2026-08-03

First-party gift cards with real-time balance tracking, redeemable across every location in the group and through the online-ordering channel.

payments-gift-cards

Gift cards work across the estate — Show Commands has a Gift Card button "for creating a gift card, adding to an existing gift card or when using a gift card for payment", balances appear on server reports, and an eCard Systems Gift Cards report is embedded in the Dashboard for both RPOS and Express. Shortfall: the stored-value ledger is a partner's. Physical cards are ordered from "SpotOnOrders@ecardsystems.com", a "Supported Gift Card Vendors" article enumerates third-party issuers, and the e-gift storefront is built by Netmasons. Cross-location redemption and outstanding-liability reporting are not documented. https://help.spoton.com/space/SK/3311173661 · retrieved 2026-08-03

House/on-account tabs with per-account credit limits, running balance, and periodic statement or invoice generation.

payments-house-accounts

House Accounts are native and documented: "House Accounts allow SpotOn Restaurant (RPOS) businesses to extend credit to customers, enabling them to charge purchases to an account instead of making payment at the time of service", with a "House Account Credit Limit window" at creation, a running balance, settlement gated on the Paid In permission, and a House Accounts Report in the reporting set. Shortfall: no periodic statement or invoice generation is documented — the operator reads the report and bills outside the system. https://help.spoton.com/space/SK/2662793359 · retrieved 2026-08-03

A single check can be settled with multiple tenders and split by seat, by item, by even shares, or by arbitrary amount, with no hard cap below eight ways.

payments-split-tender

Split Payment of Check Equally divides the balance and "each divided portion can be paid using any accepted payment method (e.g., cash, credit card, gift card)", with each guest's portion adjustable after the split. Itemised splitting is handled by Split Check by Guest, which "allows you to divide a single check based on the items each guest ordered", and Serve supports the same on the handheld. No split-count ceiling is stated anywhere. https://help.spoton.com/space/SK/2666627715 · retrieved 2026-08-03

Voids, refunds, discounts, and no-sales require role-based authorization (manager PIN or approval) and write to an immutable audit log identifying the approver.

payments-refund-void-controls

Refund and void authority is permission-gated per job position (Void is available "if your permissions allow it"; refunds are a manager-level FOH function), partial refunds are supported down to the tip line, and the system constrains the refund path — "Refunding to a different payment method than the one originally used is not supported." Manager approval is enforced by manager code or a Manager Card, and the Credit Card Transactions report retains the transaction record with partial PANs "for security and PCI compliance". https://help.spoton.com/space/SK/2666628237 · retrieved 2026-08-03

In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator

payments-chargeback-tooling

How to Appeal a Chargeback | SpotOn Merchant Dashboard: Reports > Disputes lists every dispute with created date, case number, transaction ID, status (Action required / Under review / Case closed) and amount, and 'Appeal Dispute' > 'Submit Appeal Online' uploads supporting documents. Shortfalls: evidence is gathered and uploaded by the merchant (proof of delivery, signed invoice) rather than assembled from the POS transaction record; the article warns the appeal option 'may not appear in your dashboard for every case'; the dashboard is SpotOn's cross-product Merchant Dashboard and the FAQ points RPOS users to find the original transaction by day and card number. https://help.spoton.com/space/SK/2058190873 · retrieved 2026-09-03 adversarially verified

Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator

payments-card-on-file

Tokenised card-on-file is documented in the Virtual Terminal: "On subsequent invoices, saved cards are presented at checkout... You can charge a stored card on your customer's behalf from the invoice detail screen. Each card is stored per customer", and recurring payments/subscriptions run off the same stored credential. Start a Tab holds a card on file for an open tab. Shortfall: the stored card lives on the Virtual Terminal customer record, not on a unified guest profile shared with first-party online ordering and the restaurant POS; no cross-channel card-on-file is documented. https://help.spoton.com/space/SK/910032971 · retrieved 2026-08-03

Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator

payments-payout-timing

The deposit schedule is published: "Daily sales that are batched out before 9.00PM ET are deposited into your bank account the next business day", with a morning funding deposit time over RTP/FedNow and an explicit note that batches after 9pm ET add a business day. Faster funding is a named product — Rapid Fund — with a self-serve enrolment and cancellation article in the Dashboard, and Rapid Funding enrolment locks BOH batch time to unified batching. https://help.spoton.com/space/SK/2035548277 · retrieved 2026-08-03 adversarially verified

Vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance / P2PE listing available to merchants on request.

payments-p2pe-pci4

A current PCI claim exists and is version-specific: trust.spoton.com lists 'PCI DSS v4.0.1' and 'SOC 2 Type 2', and the merchant-facing PCI guide states 'our solutions minimize your exposure to cardholder data, reducing the PCI DSS compliance scope' with SecureTrust by Viking Cloud guiding merchants through SAQ selection. Shortfall: the Attestation of Compliance is not available on request in any open sense — the trust centre requires an access request to 'view & download sensitive information' — no PCI-listed P2PE solution is named, and SpotOn never states which SAQ type its merchants qualify for. https://trust.spoton.com/ · retrieved 2026-08-03

Items route to specific KDS stations by item, category, order type, or revenue center, with routing rules configurable per location without vendor involvement.

kitchen-station-routing

RPOS routes by Requisition Group, configurable per location by the operator, including a documented Conditional Print Route engine: "Set the conditions for the route beneath When an order is sent that has... Items From All These Routes... Route all To... And Still to These", with Enhanced CPR styling for secondary items. A worked example routes online-only items ("Print Only When Ordered Online" creates an ORD Print Only requisition group). Express has an equivalent Routing Group Setup in the Dashboard, including an AI menu assistant that builds routing groups. https://help.spoton.com/space/SK/2361492065 · retrieved 2026-08-03

An expo screen consolidates items from multiple prep stations into a single order view and only marks the order complete when every contributing station has bumped its items.

kitchen-expo-consolidation

Express KDS documents a distinct Expo screen and its completion semantics: "On Expo KDS, bumping all items will not automatically bump the ticket — tickets must be manually bumped on Expo", with a Fire to Expo routing option and multi-screen sequencing ("When you bump or clear an item on one screen, it automatically appears on the next screen in the sequence... This is common for prep stations working with expo screens"). Shortfall: this is the first-party Express KDS only. SpotOn Restaurant (RPOS) ships no KDS of its own — expo consolidation there depends on whichever partner screen the operator buys (Fresh KDS, ChefTab or QSR Automations), and the RPOS-side documentation covers requisition printing rather than an expo screen. https://help.spoton.com/space/SK/4341727233 · retrieved 2026-08-03

Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator

kitchen-course-firing

"Hold & Fire allows FOH to send an entire order to the kitchen but place specific items on hold, pacing when they should be prepared. When the item is ready to be cooked, FOH releases the hold manually in the POS by releasing (Fire) the item." Coursing groups items on the ticket, and firing is also available kitchen-side: "Fresh KDS also allows the kitchen to fire held items on the KDS" (with the documented caveat that "firing from Fresh KDS does not send the update to RPOS"). https://help.spoton.com/space/SK/4642242728 · retrieved 2026-08-03 adversarially verified

Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator

kitchen-prep-time-pacing

'Can lead times be configured at the menu item level? No. SpotOn currently supports lead times at the order level, such as Pickup Lead Times and Delivery Lead Times, but does not support lead times for individual menu items.' Pacing is operator-driven: Auto Coursing 'only assigns course numbers to items'; Fresh KDS Hold & Fire is manual. https://help.spoton.com/space/SK/896892991 · retrieved 2026-09-05 adversarially verified

Kitchen load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator

kitchen-order-throttling

Order Pacing caps how many online orders are accepted per time window and is described as removing "the guesswork from managing online ordering capacity". Shortfall: the trigger is a static per-slot order count set by the operator, not a kitchen-load or ticket-time threshold, no automatic quote-time extension is documented, and third-party marketplace orders bypass it entirely. https://help.spoton.com/space/SK/1792245867 · retrieved 2026-08-03

Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator

kitchen-channel-pause-propagation

86 status does reach the marketplaces through the certified aggregators: Chowly is a "two-way integration" whose POS-to-Chowly sync lets the operator "ensure item availability and 86 status is always reflected in your 3rd party marketplaces", and Deliverect "syncs your POS menu across all connected marketplaces in real time". Shortfall: nothing documents a POS-side action pausing a store on DoorDash, Uber Eats or Grubhub — SpotOn's own Pause Online Ordering acts on SpotOn's first-party channel only — and item-option (modifier) 86 propagation is not described. https://help.spoton.com/space/SK/2843705345 · retrieved 2026-08-03

Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator

kitchen-order-ready-callback

The order-ready courier notification to DoorDash and Uber Eats is sent when staff tap Mark as Ready on the RPOS or Express POS (Marking Online Orders Ready for Pickup). Shortfall: the event is a POS action, not a KDS state - the Express KDS article (Order Management on the KDS) documents bumping as moving a ticket to Completed and says nothing about a courier notification, and the RPOS/Fresh KDS articles document none either. https://help.spoton.com/space/SK/4295032833 · retrieved 2026-09-03 adversarially verified

KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.

kitchen-bump-bar-hardware

Bump bars are supported but not supplied: "When touch screens do not work for your kitchen, a bump bar is a small, programmable device that connects to your Fresh KDS setup... While SpotOn does not supply bump bars for Fresh KDS, Fresh KDS does support them. Compatible bump bars can be purchased independently, and Fresh KDS will provide bump bar setup support." Shortfall: no supported models are enumerated by SpotOn, and no bump-bar support is documented for the first-party Express KDS. https://help.spoton.com/space/SK/4838981646 · retrieved 2026-08-03

An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.

kitchen-all-day-counts

The SpotOn KDS product page lists 'All-day view - Switch to an all-day view to see how many of each item should be working' and includes 'All-day view' in the $20/station SpotOn KDS feature list. Shortfalls: marketing-page evidence only - the Express KDS help article (Order Management on the KDS) documents order cards, bumping, prep-time alerts and voids but no all-day view; per-modifier aggregation is not stated. https://www.spoton.com/solutions/kitchen-display-system/ · retrieved 2026-09-03 adversarially verified

Configurable target cook times per station or order type, with visual color escalation and/or audible alert when a ticket exceeds target.

kitchen-sla-alerts

Escalation exists and is colour-coded: "Prep time alerts allow kitchen staff to quickly identify aging orders. These alerts are displayed as prep time background colors... The warning alert is displayed as a yellow background behind the prep time. The critical alert is displayed as a red background." Shortfall: the thresholds are not operator-configurable — "Currently, prep time alert settings are managed by SpotOn Support. To update prep time alert settings, please call us at (877) 814-4102" — and no per-station or per-order-type target is documented. https://help.spoton.com/space/SK/4341727233 · retrieved 2026-08-03

If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator

kitchen-printer-fallback

RPOS Printers | Failover Print Routing: 'A Failover Print Route is an alternate printer route that will automatically print should the default printer fail'; the failover lists printers in priority order (1, 2, ...) per location and is enabled per printer under Printer Failover Settings > Enable Printer Failover / Print Failover Plan (Sidekick article 1600422044 shows the same BOH controls). Shortfalls: printers only - no KDS-screen failover is documented; no staff alert on failover; no statement about ticket loss during the switch; documented for RPOS, not for Express print routing. https://help.spoton.com/space/SK/762314779 · retrieved 2026-09-03 adversarially verified

KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator

kitchen-offline-operation

Documented for Express: "Fresh KDS for Express supports partial offline mode functionality. When a Fresh KDS is connected to the local SpotOn provided network, but the local network doesn't have an active internet (ISP) connection, orders sent from the POS will still show up on Fresh KDS", and the Express offline article confirms "Orders are still sent to the kitchen printer or KDS." Shortfalls: screen-to-screen bumping, SMS, online-order receipt and real-time analytics all stop while offline, new KDS logins require internet, and nothing equivalent is documented for RPOS, which has no offline mode. https://help.spoton.com/space/SK/5085823000 · retrieved 2026-08-03

Station screens can display item-level build/assembly detail (recipe steps, portioning, or full modifier breakout) rather than only the ticket line text. differentiator

kitchen-item-build-screens

'Fresh KDS shows detailed order information on tickets: Order number Guest name Table name... Item modifiers Special notes and instructions Custom formatting with color-highlighted modifiers'; styles configurable by keyword. Shortfall: only via the Fresh KDS integration - SpotOn's own 'Order Management on the KDS' never lists modifiers - and no recipe or portioning detail. https://help.spoton.com/space/SK/4944036017 · retrieved 2026-09-05 adversarially verified

Sectioned/fractional topping placement (halves, quarters, specific sections) is rendered visually and unambiguously on the make-line screen or ticket. differentiator

kitchen-pizza-fractional-display

Half assignment does reach the kitchen, but as text: sub-item groups "can be configured to follow their own requisition group or to follow the parent item", and the operator is told to "select the checkbox Print in Red to ensure that the subgroups print in red on the kitchen printer, unless that subgroup is used as a size choice (for example, pizza sizes)". Shortfall: with the documented left-half/right-half group construction the halves appear only as separately named sub-item lines; no sectioned or graphical rendering of topping placement on a make-line screen is documented anywhere. https://help.spoton.com/space/SK/2658076199 · retrieved 2026-08-03

A bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order.

kitchen-recall-refire

On the KDS: "Tap an item to bump it, marking it as completed. Tap it again to unbump the item, marking it as pending." On the POS side, Ticket Commands include "Reprint Requisitions — Use to resend kitchen and/or bar tickets (sends entire order; Reprint will show in red on ticket)", and Item Commands include Unvoid to restore a voided line. https://help.spoton.com/space/SK/4341727233 · retrieved 2026-08-03

Edits made in the POS to an order already displayed in the kitchen visually flag the added, changed, or removed items on the live ticket. differentiator

kitchen-order-modification-alerts

RPOS: 'Enable Void Notifications for Kitchen Printers & KDS' - with Print Void Requisitions enabled, 'Voided items will automatically send notifications to configured kitchen printers and KDS devices'; on the Express KDS 'voided items will appear in red as voided, and refunded items will appear crossed out' (Order Management on the KDS). Shortfalls: voids only - items added to or changed on an already-sent order are not flagged on the live ticket in either product's documentation; RPOS 'Reprint Requisitions' resends the entire order marked Reprint in red rather than diffing it; removed-before-send items generate nothing. https://help.spoton.com/space/SK/2666660375 · retrieved 2026-09-03 adversarially verified

Bumping an order ready triggers a guest-facing notification — SMS/text, app push, or an order-status display board — without a separate product purchase. differentiator

kitchen-guest-ready-notification

Guest messaging exists: "SpotOn Order SMS Text Messaging allows restaurants to communicate directly with guests through text messages. Merchants can send automated order confirmation messages, create custom SMS templates, and use Quick Responses", and SpotOn Reserve's Host App can "Send an Order Ready Text" for takeout via the Page button. Shortfalls: neither is triggered by a KDS bump — the Reserve page is a manual host action — and the Reserve paging path requires SpotOn Reserve, a separately priced product. https://help.spoton.com/space/SK/1493205054 · retrieved 2026-08-03

Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.

kitchen-waste-logging

CLAIM: waste, spoilage and remakes can be logged at the kitchen/KDS screen with reason codes, and the entry depletes inventory. VERDICT: no (moved from unknown). EVIDENCE: 'Order Management on the KDS | SpotOn Express' (help.spoton.com/space/SK/4341727233, version 2026-08-17) is a complete enumeration of what the Express KDS can do - Order Cards, order type, order status ('after the 1st item is bumped, the ticket ... transitions to In progress'), 'Track Timing of Completed Orders', 'Bumping Items' ('Tap an item to bump it, marking it as completed. Tap it again to unbump'), multi-KDS/Expo/prep-station bumping tables, 'See All Items View', 'Reopening Completed Orders', 'Prep Time Alerts', 'Order Auto-Completion', 'Item Level Voids & Refunds' ('items from that order may be voided or refunded from the POS') and split/combine behaviour. There is no waste, spoilage or remake entry anywhere on it, and the only reason-coded destruction path runs through the POS void screen, not the KDS, and is not said to touch stock. CONTROLS over the census: waste 18 pages - every one POISON or third-party (paper waste on chits/labels/print routing: 5610831979, 801472707, 5320704104, 2713158442; the partner-integration pages Sculpture Hospitality 2320171216, BevSpot 4223008935, BarTrack 4232478813, Bevchek 2318893418, Craftable 2320466111, BeerSAVER 2319516057, MarginEdge 2319286766, Restaurant Systems Pro 4238442504, Tenzo 2320859161, which is where SpotOn merchants get waste control); wastage 0; remake 0; shrinkage 1 (Bevchek); spoil* 3 - BevSpot plus two ARCHIVED SpotOn Enterprise (ex-Appetize venue) reports of 2023-10-04, 'Spoilage Report' (2340371904: 'The Spoilage Report displays a breakdown of comps, wastes, and total spoilage by event, inventory item, vendor, and category. Total Spoilage calculation: Comps + Wastes') and 'Inventory Reports' (2340372114: 'Wastes (Cost) = Wastes * Item Cost'). Those two are a DIFFERENT, archived product and are a report, not a KDS entry screen, so they do not carry the claim - they are recorded here so the next pass does not mistake them for Restaurant/Express behaviour. BOUND: the FIRST full-BODY census of help.spoton.com, taken from the publisher's own listing (Confluence v2 API https://help.spoton.com/api/v2/pages?limit=100&sort=-modified-date&body-format=storage, paged to fixpoint - rounds 29 and 30 returned 0 new pages): 2,145 pages WITH BODIES (1,083 current + 1,062 archived), 4,154,015 chars of tag-stripped text, version dates 2020-11-24..2026-09-17. Validation: 141 of the 142 help-centre page ids already cited in this record are inside the listing; the one absent (4456513592) now 404s on the API itself, so the KB is a census minus one deleted page. Prior passes held bodies for only the 121 most-recently-modified pages and titles for the rest. Controls are tokenised word-boundary case-insensitive over all 2,145 bodies; the denominator is 2,145. Retrieved 2026-09-17. https://help.spoton.com/space/SK/4341727233 · retrieved 2026-09-17 adversarially verified

Reports actual ticket and per-station times (average and percentile) sliced by daypart, station, and order channel, exportable to CSV or an API.

kitchen-speed-of-service-reporting

A Kitchen Performance report is embedded in the SpotOn Dashboard for both RPOS and Express, with "In-Store POS Median Bump Speed", online median difference from quoted pickup, trend lines and calendar heat maps, "included at no additional cost for SpotOn clients using Fresh KDS". Shortfalls: it requires the Fresh KDS integration, it is explicitly read-only ("The embedded dashboard is a read-only view of key kitchen performance metrics. Full configuration and management of Fresh KDS still lives in their standalone portal"), and no per-station percentile breakdown or export is documented. https://help.spoton.com/space/SK/5037785135 · retrieved 2026-08-03

Generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list.

kitchen-prep-forecasting

CLAIM: generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list. VERDICT: no (moved from unknown). EVIDENCE/CONTROLS over the census: 'prep list' 0 pages, 'prep quantit*' 0, 'production plan' 0. forecast* is 7 pages and none is kitchen prep: SpotOn Teamwork is LABOR ('SpotOn Teamwork is a labor management platform ... scheduling, labor forecasting, time and attendance', 2239594711); SpotOn Reserve forecasts COVERS and table availability ('Expected Covers Forecast expected guest traffic by booking date, capacity, hour, meal time, and source using historical data', 5099192331; 'accurately forecast table availability', 1458865646); two hits are 'forecasted delivery date' in Serve/Sidekick FAQs (POISON); and the only SALES forecasting is a THIRD PARTY - 'Tenzo is a comprehensive restaurant analytics and sales forecasting platform ... sales and transaction data from the POS are transmitted to Tenzo. Tenzo utilizes this data to generate precise future sales forecasts' (2320859161), with Shogo 'also provides additional reporting and forecasting tools that complement those already available in SpotOn Restaurant' (2320138531) - i.e. the vendor's own docs place demand forecasting outside the product. The kitchen surface itself (Order Management on the KDS, 4341727233, a full function enumeration) has no prep list: its only 'prep' feature is 'Prep Time Alerts ... displayed as prep time background colors', an aging-order colour, not a quantity. par level 3 pages: Restaurant Systems Pro (third-party 'Par-Level System') and two archived Enterprise inventory reports. BOUND: the FIRST full-BODY census of help.spoton.com, taken from the publisher's own listing (Confluence v2 API https://help.spoton.com/api/v2/pages?limit=100&sort=-modified-date&body-format=storage, paged to fixpoint - rounds 29 and 30 returned 0 new pages): 2,145 pages WITH BODIES (1,083 current + 1,062 archived), 4,154,015 chars of tag-stripped text, version dates 2020-11-24..2026-09-17. Validation: 141 of the 142 help-centre page ids already cited in this record are inside the listing; the one absent (4456513592) now 404s on the API itself, so the KB is a census minus one deleted page. Prior passes held bodies for only the 121 most-recently-modified pages and titles for the rest. Controls are tokenised word-boundary case-insensitive over all 2,145 bodies; the denominator is 2,145. Retrieved 2026-09-17. https://help.spoton.com/space/SK/2320859161 · retrieved 2026-09-17 adversarially verified

Product includes a native in-house driver module: drivers are first-class entities with clock-in/out, assignment state (in-store / on-run / returning), and per-driver run history reportable from the POS itself (not via a third-party add-on).

delivery-driver-roster

In-house delivery is a real, first-party RPOS module — Driver Management is a Start Screen option and a Command Bar button, and "Driver Management allows delivery drivers to view, select, and manage their assigned delivery orders directly from the FOH. Drivers can organize their delivery sequence, transfer orders to their login, and close out completed deliveries once payment and tips are applied." Shortfall: a driver is an ordinary employee with a login, not a first-class driver entity — there is no documented assignment state (in-store / on-run / returning) and no per-driver run-history report; the only durable artefact is the server report and the closeout. https://help.spoton.com/space/SK/4471914578 · retrieved 2026-08-03 adversarially verified

Provides a dedicated dispatch/expo screen showing undispatched orders, driver availability, and elapsed time per order, with multi-order run batching (assigning 2+ orders to one driver as a single run).

delivery-dispatch-board

The Driver Manage screen is a dispatch board with run batching: "This screen displays all delivery orders that have been entered. The driver will select the delivery orders in the sequence they will be delivered (e.g., Delivery Stop #1, Delivery Stop #2)... Once the orders are selected, tap Transfer Orders. This action moves the selected delivery orders to the driver's login", including a prompt to transfer current and future tips to the new user. Shortfalls: the board shows orders, not driver availability, and no elapsed-time-per-order column is documented. https://help.spoton.com/space/SK/4471914578 · retrieved 2026-08-03 adversarially verified

Dispatch includes a live map view with geocoded stops and system-generated route sequencing (turn order optimization) for a multi-stop run, not just a static address list. differentiator

delivery-route-map

Route sequencing is manual and the vendor cedes optimisation to a partner. The Driver Management article has the driver hand-pick the delivery order sequence, and the Captain integration page exists precisely to supply what is missing: "Captain is an in-house delivery driver management solution that integrates with SpotOn Restaurant's point-of-sale for customer online orders. This integration helps restaurants manage and optimize online order delivery routes more effectively... With optimized, efficient routes, drivers can complete more deliveries in a shorter amount of time." https://help.spoton.com/space/SK/2320105759 · retrieved 2026-08-03 adversarially verified

Captures live driver GPS position from a driver-facing mobile app and surfaces it back to the dispatch screen. differentiator

delivery-driver-tracking

No driver-facing GPS app or dispatch map is documented for SpotOn's own driver module. Live driver position is what the Captain partner adds — "With Captain, your guests will be able to see how long their order will take, who their driver is, and where they are at all times" — and for DaaS orders the tracking comes from DoorDash ("Tap Track Delivery on DoorDash to view real-time driver status"). https://help.spoton.com/space/SK/2320105759 · retrieved 2026-08-03

Delivery areas can be defined as arbitrary map polygons or by drive-time isochrones, not solely as a radius or a ZIP/postcode list. differentiator

delivery-zones-polygon

A polygon map editor is documented: "Under Delivery Area, tap View/Edit to open the map editor... Drag the boundary lines by holding and moving the circles on the map to adjust your delivery zone", plus arbitrary exclusion polygons — "Tap the Exclusion Area button. Tap points on the map to outline your exclusion area... Adjust the shape by dragging the circles on the border", with multiple exclusion areas supported per location. https://help.spoton.com/space/SK/4472242281 · retrieved 2026-08-03 adversarially verified

Each delivery zone carries its own independently configurable delivery fee, order minimum, and quoted promise time, applied automatically from the validated customer address.

delivery-zone-pricing

Per-zone pricing is structurally impossible in the documented model: the same article states "Can I create more than one Delivery Area? No. Each location can have only one Delivery Area. However, you can create multiple Exclusion Areas within that Delivery Area." With one zone per location there is no zone to price. Delivery fees are configured as a location-level surcharge or an order-type fee, and Express sets a single "Delivery Fee" and "Minimum Delivery Amount" per location. https://help.spoton.com/space/SK/4472242281 · retrieved 2026-08-03

Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.

delivery-address-validation

Out-of-zone addresses are caught at order time on the digital channel: the delivery area polygon governs "where online delivery orders can be accepted", and the DoorDash Drive flow confirms the behaviour — "If they are outside delivery range, or delivery is unavailable due to scheduling, the guest will be able to select Pickup instead." Shortfall: no geocoding or address-verification service is named, and the in-POS delivery order flow simply captures a free-text address on the customer record ("Tap New Address. Enter the delivery address and tap Accept") with no documented validation. https://help.spoton.com/space/SK/4472242281 · retrieved 2026-08-03

Tracks per-delivery driver compensation inputs — mileage or distance driven per run, per-delivery flat reimbursement, and driver-retained tips — and exports them to payroll as separate reimbursement vs. wage lines. differentiator

delivery-driver-comp

Assignment and tip ownership only: 'Drivers can organize their delivery sequence, transfer orders to their login, and close out completed deliveries once payment and tips are applied', with the prompt 'Would you like to transfer all tips (current and future) to the new user?'. Shortfall: no mileage, no distance per run, no per-delivery flat reimbursement. https://help.spoton.com/space/SK/4471914578 · retrieved 2026-09-05 adversarially verified

Provides a driver cash bank / settle-up flow that reconciles cash collected, orders assigned, and tips owed at end of shift, producing a per-driver over/short figure.

delivery-cash-reconcile

A settle-up flow exists: "When the driver returns to the store, they will: Apply the payment; Adjust their tip (if applicable); Close out the tab", with tip ownership explicitly transferred at dispatch and the warning that "orders remain open until the driver returns to the store and manually closes them in the FOH... Verify all orders have been closed before running end-of-day reports." Shortfall: no driver cash bank and no per-driver over/short figure are documented; reconciliation falls back to the generic Server Report and drawer closeout. https://help.spoton.com/space/SK/4471914578 · retrieved 2026-08-03

Can hand a first-party order to an on-demand courier marketplace (DoorDash Drive, Uber Direct, Nash, Relay or equivalent) natively from the POS, with the courier quote and status returning into the order record.

delivery-daas-dispatch

SpotOn Delivery powered by DoorDash Drive dispatches a courier natively from the POS and returns courier state into the order: the operator sets "a DoorDash Drive Delivery Lead Time... the number of minutes before the DoorDash driver will pick up the order", and the order record carries the pickup time, "the driver's name" and "the driver's telephone number". Cancellation scenarios by dispatch stage are documented. Express has a parallel DoorDash Drive Delivery Setup Guide with the flat $7.95 ($9.95 in California) per-delivery fee. https://help.spoton.com/space/SK/1706524708 · retrieved 2026-08-03

Supports hybrid dispatch: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. differentiator

delivery-daas-fallback

SpotOn Delivery Powered by DoorDash: 'We can only support one delivery method at this time. If a restaurant is using internal delivery, but wants DoorDash Drive, they can only use one or the other. If a restaurant has both internal delivery and DoorDash turned on, DoorDash will override internal.' No overflow rule, wait threshold or out-of-zone handoff exists between in-house Driver Management and DoorDash Drive. https://help.spoton.com/space/SK/1706524708 · retrieved 2026-09-03 adversarially verified

Offers direct, first-party certified API integrations with DoorDash, Uber Eats, and Grubhub marketplaces (vendor-owned, not solely resold through Otter/Deliverect/Chowly/ItsaCheckmate middleware). differentiator

delivery-3p-direct-integration

Two of the three are first-party and certified: DoorDash ("The DoorDash integration directly connects your choice of DoorDash Marketplace (15-30% commission) and/or DoorDash Online Ordering (commission-free)... This integration works with SpotOn Restaurant POS and Express POS") and Uber Eats ("Orders from the Uber Eats app route straight into the POS — no tablets, no manual re-keying"). Shortfall: Grubhub has no direct SpotOn integration article and is reachable only through the Chowly, Deliverect or Checkmate middleware layers. https://help.spoton.com/space/SK/4629856267 · retrieved 2026-08-03

Third-party marketplace orders inject automatically into the POS as normal tickets that fire to KDS/printers without tablet re-keying or manual accept.

delivery-3p-injection

"Orders flow directly into the POS (prepaid) and out to printers or kitchen display systems for fulfillment without any manual intervention", and "the direct integration eliminates the need for aggregators or additional hardware for restaurants to fulfill orders coming in from DoorDash." Uber Eats is described the same way: "no tablets, no manual re-keying... Prep times, modifiers, and order tickets flow to your KDS or printers exactly as they should." https://help.spoton.com/space/SK/4629856267 · retrieved 2026-08-03

Menu, pricing, modifiers, and photos publish from the POS master menu out to connected third-party marketplaces, including channel-specific price markups, without maintaining a separate menu in each portal.

delivery-menu-push

"Menus stay perfectly in sync. SpotOn automatically publishes items, prices, and availability to Uber Eats in real time" (Uber Eats), and for DoorDash "menus from the SpotOn POS are automatically kept in sync", with channel markup applied centrally: "Navigate to Dashboard > Integrations > DoorDash > Price Markup. Select a price markup percentage", plus an explicit warning that configuring markup in both SpotOn and the DoorDash portal double-applies it. https://help.spoton.com/space/SK/4649091119 · retrieved 2026-08-03

Marking an item or modifier 86'd in the POS pushes item-level out-of-stock status to connected third-party channels in near real time, and restores it on availability (DoorDash requires item and item-option 86ing of new POS partners).

delivery-86-sync

Availability propagation is documented through the certified channels — Chowly's POS-to-marketplace sync lets operators "ensure item availability and 86 status is always reflected in your 3rd party marketplaces", and Uber Eats receives "items, prices, and availability... in real time". Shortfall: item-option (modifier) level 86 propagation, restore-on-availability behaviour, and propagation latency are not documented for any channel, and no 86 sync is described for the DoorDash direct integration specifically. https://help.spoton.com/space/SK/2843705345 · retrieved 2026-08-03

Store can be paused/deactivated on each connected third-party marketplace from inside the POS with a timed auto-reactivation, rather than only from each marketplace's own tablet or portal.

delivery-store-pause

Pause Online Ordering is a documented FOH action with a timed override window — "During the override time period, the online ordering site will display that orders are unavailable" — and the offline guidance tells operators to pause online ordering while disconnected. Shortfall: the pause acts on SpotOn's own online ordering channel; no POS-initiated store pause on DoorDash, Uber Eats or Grubhub is documented, so marketplace pausing still happens in each marketplace's own portal. https://help.spoton.com/space/SK/2353004545 · retrieved 2026-08-03

Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. differentiator

delivery-3p-reconciliation

Marketplace sales land in SpotOn reporting for reconciliation — "Uber Eats sales and item performance roll into SpotOn reporting for clean reconciliation", and the Express Sales Summary breaks out "Order Origin: POS, Kiosk, Digital Ordering, DoorDash Marketplace, etc." Shortfall: no report matches marketplace payout deposits to POS-recorded sales, and commission, marketing fees, refunds and missing/unpaid orders are not itemised anywhere in the documented report set. https://help.spoton.com/space/SK/4649091119 · retrieved 2026-08-03

Vendor exposes integration health to the operator — failed/rejected order injections, connection status per channel, and alerts on failure — rather than failing silently. differentiator

delivery-injection-error-visibility

Menu-sync health is surfaced to the operator with an actionable error: "While the menu syncing is in progress, the waiting screen provides real-time updates on the synchronization status... Error: Menu Sync Failed. Steps to Resolve Menu Sync Failure: Contact Support... Try Again." A separate Express article covers "Online Orders Not Showing on Express KDS". Shortfall: no per-channel connection-status view and no failed-order-injection alerting are documented — the visibility that exists is for menu sync, not for order delivery. https://help.spoton.com/space/SK/3097755789 · retrieved 2026-08-03

Guests receive a branded order status / driver tracking page or SMS link on the restaurant's own domain for first-party delivery orders, driven by real order and driver state.

delivery-tracking-page

Guests do get live tracking on DaaS orders: "Tap Track Delivery on DoorDash to view real-time driver status", and the DoorDash Drive flow sends the guest a delivery notification with a tracking link. Shortfall: the tracking page is DoorDash-branded and DoorDash-hosted, not on the restaurant's own domain, and no tracking page at all is documented for in-house driver deliveries run through Driver Management. https://help.spoton.com/space/SK/4281565224 · retrieved 2026-08-03

Quoted delivery promise times adjust dynamically from current kitchen load, driver availability, and zone drive time, rather than a fixed per-store constant. differentiator

delivery-promise-time

Promise times are configurable per channel — a DoorDash Drive Delivery Lead Time "must be a number between 1 and 999", SpotOn Order has a Lead Times article, and Order Pacing is described as helping "ensure customers receive accurate wait times during peak hours". Shortfall: the lead time is a static per-store constant; nothing documents it flexing with live kitchen load, driver availability or zone drive time. https://help.spoton.com/space/SK/1706524708 · retrieved 2026-08-03

Vendor documents explicit offline behavior for delivery: whether cash delivery orders, driver assignment, and driver settlement continue during an internet outage.

delivery-offline-behavior

The one offline document is generic and silent on delivery: 'Key Information: Orders and payments continue; data syncs once the internet connection is restored. Orders are still sent to the kitchen printer or KDS.' It adds 'Offline Mode is not available for RPOS devices' - RPOS carries Driver Management. Cash delivery orders, driver assignment and settlement are unaddressed. https://help.spoton.com/space/SK/4073652945 · retrieved 2026-09-05 adversarially verified

Vendor ships a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission.

digital-first-party-web

SpotOn Order is a first-party commission-free ordering channel on the restaurant's own site ("Branded website for your restaurant, even if you have multiple locations"), with orders writing into the POS; Express has a parallel "Set Up Online Ordering Right from Your Dashboard". SpotOn markets it against the marketplaces in its own material: an "Online Ordering Marketing Kit" of "free templates for both Restaurant POS and Express to encourage guests to order directly from you instead of costly third-party marketplaces." https://help.spoton.com/space/SK/2149712035 · retrieved 2026-08-03

The web/app ordering menu is generated from the same POS menu record as in-store — one item edit propagates to all first-party digital channels without a separate digital menu build.

digital-menu-single-source

One menu record drives every surface, with per-channel visibility rather than a second build: "Exclude menu categories from customer view on online ordering platforms or from POS, handheld, and kiosk stations via the SpotOn Dashboard Menu & Table Settings", and the Sales Channels article answers whether hiding a category on the POS also hides it on handhelds and kiosks. The RPOS sub-item best-practice article notes the same menu structures drive "online ordering (GoTo / Order 2.0)". https://help.spoton.com/space/SK/3908042869 · retrieved 2026-08-03

Vendor offers a branded native iOS and Android ordering app (published under the restaurant's own brand in the App Store/Play Store), not only a mobile web page or a shared multi-restaurant marketplace app. differentiator

digital-native-app

A native consumer app exists and takes orders into the POS — GoTo Place is documented for placing pickup and DoorDash Drive delivery orders, with a dedicated "Scheduled Pickup Orders via GoTo Place App" flow for RPOS. Shortfall: GoTo Place is SpotOn's own multi-restaurant marketplace app, not an app published under the restaurant's brand in the App Store or Play Store; no white-label app product is documented. https://help.spoton.com/space/SK/4281565224 · retrieved 2026-08-03

Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels.

digital-account-saved-payment

GoTo Place (SpotOn's consumer ordering app): guests create a profile with phone number or email, 'Use the Order History tab to quickly reorder previous items', and pay with Apple Pay, Google Pay or a credit card (How to Place an Order). Shortfalls: no saved tokenised card on file and no saved addresses are documented - card entry each time or a device wallet; the app is pickup-only (Scheduled Pickup Orders via GoTo Place), so there is no address book; the SpotOn Order web checkout documents no guest account at all. https://help.spoton.com/space/SK/4026925098 · retrieved 2026-09-03 adversarially verified

Digital checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator

digital-upsell-engine

SpotOn's 2025-07-07 announcement describes 'Picked for You', a feature of its first-party SpotOn Order web ordering that 'analyzes signals like time of day, day of week, and purchase history to suggest the most relevant menu items', places them at the top of the digital menu, needs 'no setup', and is 'live for all SpotOn Order web users' with the GoTo mobile app to follow. That is an algorithmic, personalised recommendation at digital checkout. Shortfall: no attach-rate or recommendation-performance reporting is mentioned anywhere (the release cites only a 6% average lift in orders), there is no operator-configurable rules-based upsell, the online-ordering product page does not mention the feature, and no knowledge-base article documents it. https://www.spoton.com/blog/picked-for-you-ai-powered-menu-recommendation-restaurants/ · retrieved 2026-09-02 adversarially verified

Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.

digital-scheduled-pacing

Scheduled online ordering is documented with two release models — "lead-time-based keeps food hot and ready right as your customer arrives. Release immediately is handy if you take large or catering-style orders and want to plan prep as soon as orders come in. You can switch anytime" — and per-slot capacity comes from Order Pacing, which caps "how many orders can be accepted during specific times of the day" and automatically shows the site as unavailable when the window is exhausted. https://help.spoton.com/space/SK/5273976862 · retrieved 2026-08-03

Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.

digital-fulfillment-modes

One ordering flow covers dine-in, To Go and Delivery with mode-specific fees — "Order type fees allow Express merchants to automatically apply fees to the order types: Dine In, To Go, and Delivery... like delivery fees for online delivery orders or packaging fees for To-Go orders" — plus QR dine-in and scheduled pickup with per-mode lead times. Shortfall: curbside with an arrival check-in step is not documented as a fulfilment mode on either product. https://help.spoton.com/space/SK/4573593647 · retrieved 2026-08-03

Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.

digital-qr-table

Table Service QR Order & Pay has its own configuration article alongside a counter-service variant; guests "browse menus, place orders, pay checks, tip staff, and redeem Loyalty rewards", the items land on the existing POS check, staff can be notified on payment, and QR Collaborative Ordering & Tab Share plus QR Group Order & Pay cover multi-guest splitting on the same tab. https://help.spoton.com/space/SK/5245108569 · retrieved 2026-08-03

Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator

digital-kiosk

Express treats the kiosk as a POS surface running the same menu: offline mode is configured "on SpotOn Express POS and Kiosk devices", the menu engine is shared (categories are excluded per "POS, Handheld, and Kiosk"), and unattended payment is implied by "Cash (Not supported on Kiosks)". Shortfalls: no accessibility or ADA conformance is documented for the kiosk, no form factors are described, and RPOS operators get a kiosk only through the Bite Kiosk or Reddie Group integrations. https://help.spoton.com/space/SK/4073652945 · retrieved 2026-08-03

Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.

digital-group-ordering

Two documented mechanisms: QR Group Order & Pay, where "When the configuration is Pay Now, customers have to build their order & pay before the items are sent to the kitchen", and QR Collaborative Ordering & Tab Share, configured from the location's QR Order & Pay settings, which lets multiple guests contribute to and split one tab. https://help.spoton.com/space/SK/2087780512 · retrieved 2026-08-03

Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator

digital-catering-portal

RPOS Scheduled Orders are described as 'ideal for catering orders, large group reservations, special events': payment can be collected when placed, when ready or any time before fulfilment, 'both full and partial payments are supported', with 'accepting installment payments for a large catering order' as the worked example, and the order auto-releases to Open Orders at the scheduled time. Shortfalls: staff-entered on the POS - no guest-facing catering portal, separate catering menu, order minimums, lead-time rules, quotes/proposals or invoice terms; Express scheduled online ordering is same-day pickup only ('Scheduling for future days ... is not yet available'). https://help.spoton.com/space/SK/814088713 · retrieved 2026-09-03 adversarially verified

Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator

digital-voice-ai-phone

A named, documented partner does exactly this: "Loman AI... provides a 24/7 AI phone answering service tailored for restaurants. Their platform integrates seamlessly with existing Point of Sale (POS) systems, enabling restaurants to automate phone-based tasks such as order taking", with a further article covering Loman voice reservations writing into SpotOn Reserve. Popmenu is documented with AI phone answering as well. Shortfall: this is a partner capability sold separately, not a SpotOn product, and SpotOn publishes no certification criteria or API for it. https://help.spoton.com/space/SK/4801134599 · retrieved 2026-08-03

Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.

digital-drivethru-ai

'Maple is a voice AI platform built specifically for restaurants that automates phone-based customer interactions end to end', its core features being 'AI-powered call handling (24/7)', order/reservation management and 'Automated upselling... during calls'. Loman AI is likewise phone ordering. SpotOn's drive-thru partner Reddie supplies menu boards, not voice. https://help.spoton.com/space/SK/5448564880 · retrieved 2026-09-05 adversarially verified

Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.

digital-sms-ordering

SMS is wired into the ordering flow: "SpotOn Order also supports SMS text messaging for QR orders, enabling restaurants to send automated updates and communicate directly with guests throughout the ordering process. When SMS is enabled for QR orders, guests are prompted to enter their phone number when starting a new QR order", with custom templates and Quick Responses on the FOH side. Shortfall: this is outbound and conversational messaging around an order, not text-to-order — no SMS ordering or text-a-link reorder flow is documented. https://help.spoton.com/space/SK/1916370973 · retrieved 2026-08-03

Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator

digital-google-order

"Order with Google allows your restaurant to seamlessly direct guests from your Google Business Profile to your preferred online ordering channels for pickup and/or delivery. By marking your commission-free online ordering channel as 'Preferred by business,' you can maximize your profits by reducing marketplace commission costs." A companion Express article ("Google x SpotOn Online Ordering") and a Disable Order with Google article cover the other end of the lifecycle. https://help.spoton.com/space/SK/4235002023 · retrieved 2026-08-03 adversarially verified

Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.

digital-apple-business-connect

CLAIM: supports Apple Business Connect ordering placement - an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow. VERDICT: no (moved from unknown). EVIDENCE: the only map/search ordering placement SpotOn documents is Google's - 'Google x SpotOn Online Ordering | SpotOn Express' (help.spoton.com/space/SK/4384489480, version 2026-09-02) plus the archived 'Order with Google Search & Maps FAQ' (1781268665) and the '10-07-21 Google My Business Update | Order with Google' release note (1958576142); 13 pages mention Google Business and 5 Google My Business. CONTROLS over the census: 'apple business' 0 pages, 'apple maps' 0, 'business connect' 0 - against a denominator of 2,145 pages whose 'Apple' hits are Apple Pay/Wallet and iPad hardware. That closes the last open surface: the 320th had already bounded the merchant dashboard (1,234 JS files; the listings module google-my-business-web's 1,334-string dictionary is Google Business Profile only) and the 323rd the 482-source settings map set. BOUND: the FIRST full-BODY census of help.spoton.com, taken from the publisher's own listing (Confluence v2 API https://help.spoton.com/api/v2/pages?limit=100&sort=-modified-date&body-format=storage, paged to fixpoint - rounds 29 and 30 returned 0 new pages): 2,145 pages WITH BODIES (1,083 current + 1,062 archived), 4,154,015 chars of tag-stripped text, version dates 2020-11-24..2026-09-17. Validation: 141 of the 142 help-centre page ids already cited in this record are inside the listing; the one absent (4456513592) now 404s on the API itself, so the KB is a census minus one deleted page. Prior passes held bodies for only the 121 most-recently-modified pages and titles for the rest. Controls are tokenised word-boundary case-insensitive over all 2,145 bodies; the denominator is 2,145. Retrieved 2026-09-17. https://help.spoton.com/space/SK/4384489480 · retrieved 2026-09-17 adversarially verified

Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.

digital-loyalty-attach

Loyalty is native to the digital flow rather than a post-purchase enrolment: the SpotOn Order loyalty article documents in-flow reward selection with "unavailable rewards (grayed out, with explanation why they cannot be used)", and "once the account is created, loyalty is enabled automatically, no extra steps needed". QR Scan & Pay lists redeeming Loyalty rewards among what the guest can do from their phone, using the same phone/email identity as in-store check-in. https://help.spoton.com/space/SK/1366392978 · retrieved 2026-08-03

Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.

digital-subscriptions

'Recurring payment plans in SpotOn Virtual Terminal make it easy to manage subscriptions and memberships - set it up once, and your customers are automatically charged on your schedule', with plans, subscribers, proration and cancellation. Shortfall: billing only - no plan binds to a delivery-fee waiver, item entitlement or loyalty tier. https://help.spoton.com/space/SK/961052981 · retrieved 2026-09-05 adversarially verified

Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.

digital-promo-parity

Offers are defined once and redeemed on both sides: SpotOn Marketing "creates single-use deals and discounts redeemable by guests online and in person with the new Marketing Deals feature", and BOH Discounts and Pricing Events drive POS and online alike. Shortfall: channel eligibility controls are documented for menu visibility (Sales Channels) but not for discounts, and no article states that a given discount or coupon code behaves identically on the kiosk. https://help.spoton.com/space/SK/2349760951 · retrieved 2026-08-03

Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator

digital-guest-data-ownership

The published Merchant Terms take the opposite position. SpotOn "reserves the right to access, retain, aggregate, process and share with third parties... all data available to SpotOn as a result of its performance of the Services", and on termination there is no return obligation — the client must request the data and "SpotOn makes no representations or warranties about its ability to return information". Nothing in the knowledge base documents a bulk export of guest records either: the Dashboard Customers article documents importing a customer list and editing profiles, not exporting them. https://www.spoton.com/legal/merchant-terms/ · retrieved 2026-08-03

Digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.

digital-checkout-pci-sca

SpotOn hosts the ordering site itself, so card entry never sits on a merchant page. But the published PCI material covers the merchant's obligations - 'As a SpotOn merchant, you are responsible for ensuring your business meets PCI DSS requirements each year' via the Viking Cloud SAQ - and never states SpotOn's own PCI DSS 4.0 validation, the March 2025 script-integrity rules, or 3DS. https://help.spoton.com/space/SK/5295079466 · retrieved 2026-09-05 adversarially verified

Digital channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator

digital-surcharge-transparency

The compliance framework is documented and strong on the POS side: automatic debit/prepaid exclusion, the lesser-of-discount-rate-or-3% cap, mandatory receipt line item, and state-by-state prohibition. Shortfall: neither the Surcharging Overview nor the Dual Pricing Overview states how the programme behaves in first-party online ordering or on kiosk; the guest-facing disclosure described is in-store signage and on-device prompts. https://help.spoton.com/space/SK/4126277723 · retrieved 2026-08-03

Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.

guest-loyalty-unified-profile

One customer list spans the guest-facing products: "The Customer List in the Dashboard includes all customers enrolled in Marketing and Loyalty", identity is a phone number, email address or the SpotOn app, and guests can enrol at the POS, online ordering, website or a shareable link. Shortfall: no merge or dedup behaviour is documented, and nothing states that kiosk or third-party-marketplace transactions attach to the same profile. https://help.spoton.com/space/SK/1059913822 · retrieved 2026-08-03

Orders arriving from third-party marketplaces (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. differentiator

guest-loyalty-thirdparty-identity-attach

The article enumerates every field a marketplace order carries: "Customer Name Order Time Order Type Order Origin (e.g. DoorDash, SpotOn Order) Items ordered with prices Discounts, Fees, Taxes, Tips", and "This Online Ordering view from the POS is view-only". No guest-profile link, no loyalty attach. The DoorDash and Uber Eats pages describe the sync as menus, prices, availability and orders. https://help.spoton.com/space/SK/4033511512 · retrieved 2026-09-05 adversarially verified

Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.

guest-loyalty-accrual-models

"Loyalty is SpotOn's customer rewards program that helps merchants encourage repeat business by rewarding customers for their visits or the amount they spend. Merchants can choose between two loyalty program types" — visit-based and spend-based — configured in the Dashboard with no bolt-on vendor. Enrolment is by phone number, email address or the free SpotOn mobile app, and Loyalty runs on the integrated payment devices and POS systems. https://help.spoton.com/space/SK/1299939609 · retrieved 2026-08-03

Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator

guest-loyalty-tiers

SpotOn Reserve Member Tiers 'allow restaurants to assign loyalty levels (such as VIP or Priority Seating) to guests', shown on the Host App reservation tile, with Priority Seating giving selected tiers precedence in table assignment. Shortfalls: tiers are assigned by hand in the separately priced Reserve product - no automatic promotion or demotion by rolling-window spend or visits; the Loyalty product (Spots by Visit / Spots by Dollar) has no tier concept. https://help.spoton.com/space/SK/5015109683 · retrieved 2026-09-03 adversarially verified

Documents explicitly what loyalty lookup, accrual, and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). differentiator

guest-loyalty-offline-behavior

SpotOn's offline-mode guide enumerates what stops during an outage and includes loyalty: 'Loyalty programs: Customer data and loyalty program features that require a live connection to your payment gateway won't be available during offline activity.' That is an explicit vendor statement that loyalty is blocked offline rather than queued and reconciled. Shortfall: the guide does not separate lookup, accrual and redemption, does not say whether a check closed offline earns points once connectivity returns, and is a marketing guide rather than the knowledge base's A800 offline article, which does not mention loyalty at all. https://www.spoton.com/blog/pos-offline-mode/ · retrieved 2026-09-02 adversarially verified

Offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. differentiator

guest-loyalty-offer-stacking-rules

The stacking rules are documented but fixed: Express 'Can I apply multiple discounts to the same item? No. Only one discount may apply to an item at a time' and fixed-price discounts 'can be combined with other manual discounts' but not with overlapping scheduled ones (Create a Fixed-Price Happy Hour Discount); RPOS Loyalty FAQs: 'At this time only a reward or promo code can be applied'. Shortfalls: the rules are not exposed as configuration - no exclusive/combinable flag and no precedence ordering on a deal, discount or reward (that configuration exists only in the SpotOn Enterprise venue product's Combinable and Priority fields, a different product line). https://help.spoton.com/space/SK/4561305760 · retrieved 2026-09-03 adversarially verified

Offers can be issued to a dynamically defined audience (rules over recency, frequency, spend, or items purchased) rather than only broadcast to the whole list. differentiator

guest-loyalty-targeted-offers

Trigger-based deals are a documented, reportable feature ("Trigger-based Deals Reporting | SpotOn Restaurant"), and Marketing Deals issue "single-use deals and discounts redeemable by guests online and in person". Shortfall: the audience definition is not documented — no rules over recency, frequency, spend or items purchased appear in the Marketing or Loyalty articles, so the documented capability is closer to broadcast plus behavioural triggers than to a segment builder. https://help.spoton.com/space/SK/4187488261 · retrieved 2026-08-03

Automatically computes recency/frequency/monetary or equivalent lifecycle segments (new, regular, at-risk, lapsed, VIP) without the operator building the queries. differentiator

guest-loyalty-rfm-segmentation

The Dashboard does compute lifecycle-ish buckets automatically: "Choose between the Check-ins, New, Repeat, and Imported buttons to further refine customer data when a Loyalty Program is enabled", alongside a Loyalty Performance view. Shortfall: new/repeat/check-in counts are not recency-frequency-monetary segmentation — there are no at-risk, lapsed or VIP segments and no monetary dimension documented. https://help.spoton.com/space/SK/1059913822 · retrieved 2026-08-03

Ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns rather than one-off manual sends.

guest-loyalty-lifecycle-automation

Triggered offers ship as a product — trigger-based deals have their own reporting article — and SpotOn Marketing provides always-on deal creation. Shortfall: the specific lifecycle automations the claim names (birthday, first-visit thank-you, lapsed win-back) are not documented as configurable campaign templates anywhere in the Marketing or Loyalty article set. https://help.spoton.com/space/SK/4187488261 · retrieved 2026-08-03

Sends both email and SMS campaigns natively from the platform, not solely by handing the list to a third-party ESP. differentiator

guest-loyalty-native-email-sms

Email marketing is native — SpotOn Marketing runs campaigns from the Dashboard, and the website builder carries a newsletter subscription block that feeds it. Shortfall: no native SMS marketing campaign capability is documented. Every documented SMS surface is transactional: SpotOn Order SMS for order updates, and Reserve paging for reservations and waitlists. https://help.spoton.com/space/SK/1106018602 · retrieved 2026-08-03

Captures per-channel marketing consent with timestamp and source of consent, and honors revocation received by any reasonable means (not just the STOP keyword) across all channels.

guest-loyalty-consent-management

Consent is captured and revocable per guest: the customer record carries an "Opt-in to Deals and Offers (checkbox)", and from the Loyalty view "this redirects to the Customers tab, where you can add/remove spots, edit contact details, and manage opt-in status." Shortfall: consent is a single boolean rather than per channel, and no timestamp or source-of-consent capture is documented. https://help.spoton.com/space/SK/1059913822 · retrieved 2026-08-03

Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.

guest-loyalty-10dlc-registration

SpotOn runs the carrier work: "Once approved, SpotOn will set you up with a dedicated text messaging phone number. This typically takes 2 to 4 weeks due to the carrier approval process", with website, branded-email and 21+ criteria. Shortfall: the strings 10DLC, A2P and Campaign Registry appear zero times in all 2,125 pages, so neither the number class nor brand/campaign registration is documented. https://help.spoton.com/space/SK/5174427929 · retrieved 2026-09-05 adversarially verified

Reports redemption and incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. differentiator

guest-loyalty-campaign-attribution

Trigger-based Deals Reporting exists for RPOS, and the Merchant Dashboard exposes "Loyalty Spend & Redemption" and "Loyalty Performance" views alongside a Reviews view that tracks loyalty redemption. Shortfall: no article documents attributing incremental sales to a specific campaign, or tying a redeemed offer to the check total it moved. https://help.spoton.com/space/SK/4187488261 · retrieved 2026-08-03

Provides self-serve export of the full guest list and transaction history, including contact PII, via CSV or API, without a vendor fee or support ticket. differentiator

guest-loyalty-data-export-portability

The current Customer Directory article enumerates every action on the guest list: search, filter, "Add a Customer", "Import Customers", "Edit Customer Profile", "Add or Remove Spots", "Email a Customer", "Add a Note to a Customer", "Add a Customer to a Group". Import in, nothing out. SpotOn publishes no open API and the merchant terms carry no data-return clause. https://help.spoton.com/space/SK/1059913822 · retrieved 2026-09-05 adversarially verified

Triggers post-transaction feedback requests and routes responses by score, sending low scores to private service recovery and high scores toward public review sites. differentiator

guest-loyalty-review-capture-routing

A Reviews surface exists in the Merchant Dashboard and is tied to loyalty redemption, and the Mobile Pay & Review flow solicits guest feedback at payment. Shortfall: no score-based routing is documented — nothing describes sending low scores to private service recovery and high scores to public review sites. https://help.spoton.com/space/SK/1083441179 · retrieved 2026-08-03

Includes a native referral mechanic with per-guest codes or links, attribution of the referred guest's first order, and two-sided rewards.

guest-loyalty-referral-program

The current Loyalty article enumerates the whole programme: earning is "Select Points per Dollar or Points per visit"; a reward is a name, points and a discount; Guest Engagement is only "Sign Up Page Copy the sign-up link" and a website "Loyalty Widget". No per-guest code, no first-order attribution, no two-sided reward. The only SpotOn referral programme is merchant-refers-merchant. https://help.spoton.com/space/SK/1066992036 · retrieved 2026-09-05 adversarially verified

Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance, as an alternative to requiring a branded app download. differentiator

guest-loyalty-wallet-pass

Loyalty | SpotOn Merchant Dashboard enumerates the check-in identifiers: 'Customers can easily check in using just a phone number, email address, or the free SpotOn mobile app'; SpotOn Loyalty lists enrolment as phone number and email at check-in or the SpotOn App, and the Dashboard's Order Loyalty Cards function supplies physical cards. No Apple Wallet or Google Wallet pass exists anywhere in the 1,958-article knowledge base or on the loyalty product page. https://help.spoton.com/space/SK/1066992036 · retrieved 2026-09-03 adversarially verified

Provides admin tooling to fulfill guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records.

guest-loyalty-privacy-rights-tooling

RPOS Create and Manage Customer Profiles (BOH): a customer record can be deleted from Back Office (Customers > select > Delete; 'Customer records can only be deleted from the Back Office'). Shortfalls: no data-access (export) request tooling, no DSAR workflow, and no documented propagation of a deletion to the Merchant Dashboard loyalty profile or to marketing lists; the legal-request article covers third-party subpoenas only. https://help.spoton.com/space/SK/2666627192 · retrieved 2026-09-03 adversarially verified

Enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log.

guest-loyalty-redemption-fraud-controls

RPOS job positions carry a permission for 'Emagine Gift Cards, House Accounts, & Loyalty' functions, so loyalty operations on the POS can be restricted to specific positions; Express Employee POS Permissions require a manager PIN for cancel check, open drawer, void, and refunds, but 'Manager approval does not currently include applying discounts' (roadmap). Shortfalls: no redemption velocity limits, no manager approval on manual Spot adjustments (done from the Dashboard Customers tab), no employee self-redemption flag and no loyalty audit log are documented. https://help.spoton.com/space/SK/2660892673 · retrieved 2026-09-03 adversarially verified

Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing (claim-level; verify it is a shipped product feature, not a roadmap statement). differentiator

guest-loyalty-ai-offer-recommendation

SpotOn's marketing product page sells Marketing Assist as 'a paid digital marketing option that uses restaurant marketing automation to automatically send campaigns based on your goals, without day-to-day management' - 'just answer a few questions, then let automated campaigns run in the background all year' - at $95 per month. The launch announcement (www.spoton.com/blog/spoton-unveils-first-automated-ai-marketing-tool-restaurants/, 2024-03-05) is specific about what is generated: 'Using AI, SpotOn Marketing Assist creates the marketing campaign content', it 'defines marketing events each month and then creates and schedules campaigns', and the 'Slow Day Boost' campaign 'auto-generate[s] a campaign with a limited-time offer for those shoulder periods the operator outlined'. That is AI-generated offer content and send timing on a shipped, priced product. Shortfall: it is a $95/month add-on rather than part of the loyalty product; audience selection is the operator's whole SpotOn Order and Reserve list, with no documented targeting recommendation; and the 1,044-page knowledge base dumped on 2026-08-03 carries no configuration article for it. https://www.spoton.com/solutions/marketing/ · retrieved 2026-09-02 adversarially verified

Offers native stored-value/gift card balances tied to the same guest profile and redeemable across all locations of the brand.

guest-loyalty-stored-value-gift

Gift balances are integrated into the POS and reported in the Dashboard — an "eCard Systems Gift Cards Report" ships for both RPOS and Express, and the FOH Gift Card button creates, reloads and redeems cards. Shortfall: the stored value sits with eCard Systems rather than in a SpotOn ledger tied to the guest profile, a separate "Supported Gift Card Vendors" article lists further third-party issuers, and cross-location redemption is not documented. https://help.spoton.com/space/SK/5229084693 · retrieved 2026-08-03

Employees clock in and out at the POS terminal using a PIN, badge, or card, with no separate time-clock hardware required.

labor-clock-in-at-pos

Employees clock in and out at the terminal — Express has a dedicated "Login & Time Clock | SpotOn Express (FOH)" article covering Clock In, Clock Out and Start Break from the login screen or the POS manager menu, plus Employee ID Management and customisable breaks, and RPOS clocking is documented under SpotOn Teamwork ("Clocking In | SpotOn Teamwork"). No separate time-clock hardware is described. The article is also candid about a limit: "Currently, forced clock-in is not an integrated feature of SpotOn Express." RE-POINTED 2026-08-10: the previously cited article (space/SK/4477911076, "How to Clock In, Clock Out, and Take Breaks | SpotOn Express POS") is ARCHIVED — the Confluence API reports status=archived while the web UI still serves it at HTTP 200 with its own title, so no status, size or title check could see the withdrawal. The quoted sentence was re-verified verbatim on the successor before re-pointing; value and grade are unchanged. https://help.spoton.com/space/SK/3644358718 · retrieved 2026-08-10

Captures a photo at punch (or performs facial verification) attached to the timecard entry, with a photo-only mode available that stores no biometric template. differentiator

labor-photo-punch-verification

Teamwork captures a photo "at all moments of engagement with the time clock; clock-in, out, and break activity", photo-only with no biometric template. Shortfall, stated verbatim on the same page: "This feature is only available when you are using SpotOn Teamwork clock-in stations (not when employees are clocking in on the POS)" - it is off on the POS, the default punch surface. https://support.dolceclock.com/help/photo-authentication · retrieved 2026-09-05 adversarially verified

Records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, with the behavior documented. differentiator

labor-offline-time-punch

OWNER RULING 2026-09-18 (Q7): labor-offline-time-punch ("...with the behavior documented") is a DOCUMENTATION-SHAPED claim, so a publication census that finds no documented offline time-punch behaviour carries `no`. Landed no/B on the census below. Retrieved 2026-09-18. PRIOR EVIDENCE: VERDICT: still unknown. NEW: (1) "Login & Time Clock | SpotOn Express (FOH)" (help.spoton.com/space/SK/3644358718, version of 2026-09-04) is the full Express time-clock article. It has 0 hits for offline, internet or connection; its only relevant line is "Forgot to clock out? A manager can manually adjust your time in the Dashboard." (2) "Configuring Offline Mode" (4073652945) says "Orders and payments continue; data syncs once the internet connection is restored" and "Offline Mode is not available for RPOS devices"; it does not mention clock-ins. (3) NEW SURFACE (320th): the PRODUCTION SpotOn merchant-dashboard micro-frontend import map, https://spoton-prod-import-map-public.s3.amazonaws.com/import-map.json (anonymous, 200, 10,900 bytes; linked from https://express-dashboard.spoton.com/runtime-config.js as REACT_APP_IMPORT_MAP_URL; express-dashboard.spoton.com robots.txt is "User-agent: * Disallow:", i.e. no bar). It names 38 dashboard modules. All were fetched anonymously with their statically referenced chunks: 1,234 JS files, 113.6 MB. Refused (403) and therefore NOT held: settings-web, virtual-terminal-web, virtual-terminal-legacy-web, invoices-web, partnerships-embedded, mbo-agent-web; restaurant-reporting-dashboard-frontend did not resolve. Because settings-web is refused, this is NOT a census of the dashboard and cannot carry a no. labor-web (170 files, 6.9 MB with chunks) has no offline-punch strings: every "offline" hit is react-query's online/offline listener. (4) certspotter listing for dolceclock.com (19 names): stable/stable2/stable3/teststable.dolceclock.com and stable.spotonteamwork.com are PHP login apps (302 to /public/login.php); teamwork.spoton.com is 403 on every path; nothing served docs. Retrieved 2026-09-16. || 323rd: 323rd, NEW SURFACE: NEW SURFACE (323rd) and a CORRECTION OF THE 320th: the merchant-dashboard modules the 320th recorded as "Refused (403) and therefore NOT held" are NOT refused. Two things were wrong. (1) A Cloudflare/CloudFront 403 to node's fetch is a FALSE refusal: with curl carrying a browser UA plus Accept and Accept-Language, invoices-web (3,091,564 B), mbo-agent-web (1,626,895 B), partnerships-embedded (2,026,725 B) and virtual-terminal-legacy-web (3,963,912 B) all return 200. (2) settings-web and virtual-terminal-web were never blocked at all - their import-map URL is a 489-byte / 337-byte System.register LOADER STUB that names the real bundle, e.g. settings-web's stub loads ./assets/spoton-settings-web-BVYEUikC.js (991,568 B). AND THAT APP SHIPS PUBLIC SOURCE MAPS. Taking settings-web's './<chunk>.js' reference set to fixpoint: 116 chunks, and 116 of 116 carry a real source map (12,975,309 B of maps, every one {"version":3, with sourcesContent) - ZERO unmapped chunks - yielding 482 original TypeScript/TSX source files, 2,192,895 bytes, of SpotOn's own settings application (grade B, the vendor's own shipped source). Soft-200 control: /assets/zzz-nope.js returns 1,572 bytes of text/html, nothing like a map, so these are real files. The 482 sources are the COMPLETE merchant-dashboard settings surface for both Express and RPOS merchants: accountSettings, bankAndTax, batchTimes, businessHours + newBusinessHours (incl. Dayparts and Reporting/fiscal hours), businessInformation (incl. ReceiptCustomization), employees + multiLocationEmployees, giftcards, laborAndCompliance (AutoClockout, BreakTypes, Overtime, CashTipsManagement, ScheduleEnforcement), managerPermissions, permissions, myAccount, ordersAndTips (OrderTypes, AutoGratuity, TipAmounts, AutoprintReceipts, RequireName), paymentTypes (cash, customTenders), posUiSettings (DefaultTab, GuestCount), reportSubscriptions, revenueCenters, security, support, taxesFees (taxes, fees, surcharge), plus the legacy settings app. BOUND/LIMIT: this is the SETTINGS app only - menu (express-menu-web), loyalty (loyalty-web, reached from settings by an external link to `${applicationBase}loyalty/settings`), reporting and the POS/KDS device apps are separate modules and are not covered by this census. It does not settle the cell, but it bounds the labor SETTINGS surface: features/laborAndCompliance ships exactly AutoClockoutSettings (AutoClockoutMode enum NONE|FISCAL|HOURS, API labor/employees/autoclockout with {fiscalDayChangeEnabled, shiftDurationEnabled, maxShiftDurationMinutes}), BreakTypeSettings, OvertimeRules, CashTipsManagementSetting and ScheduleEnforcementSettings - nothing configures offline punching or punch reconciliation. POISON worth recording: the token offline scores exactly ONE hit in all 482 sources and it is the AmEx clause inside the raw instant-funding terms-and-conditions HTML ("or offline transactions (collectively, 'Non-eligible Transactions')"), i.e. card processing, not time clocks. The punch behaviour itself lives in the Express FOH device app, which this census does not cover. Retrieved 2026-09-17. || 325th: MERGE HOLD (proposed no/B, held unknown): time and attendance is SpotOn Teamwork, which documents itself on a separate KnowledgeOwl knowledge base (support.dolceclock.com, 333 articles, found in the 317th). The help.spoton.com census does not bound that publisher, so the absence is bounded to the wrong corpus. Run the offline/clock controls over the Teamwork KB before proposing this again. PROPOSAL AS WRITTEN: CLAIM: records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, WITH THE BEHAVIOUR DOCUMENTED. VERDICT: no (moved from unknown) - the documented-behaviour conjunct fails against a census, and the vendor's own offline enumeration excludes the time clock. EVIDENCE: 'Configuring Offline Mode | SpotOn Express (FOH)' (4073652945, version 2026-05-21) enumerates offline scope in a 'Key Information' list - 'Orders and payments continue; data syncs once the internet connection is restored'; 'Orders are still sent to the kitchen printer or KDS'; 'If the internet is working but payments can't be processed, offline mode won't activate, and new orders cannot be captured'; 'Offline Mode is not available for RPOS devices' - with no clock-in/clock-out entry, and the surrounding prose warns that extended offline use 'can result in loss of transactions and funding'. CONTROLS over the census: /clock (in|out).{0,30}offline/ 0 pages and /offline.{0,40}(clock|punch|time ?card)/ 0 pages. The Express time-clock article (3644358718) offers only a manager fix after the fact ('Forgot to clock out? A manager can manually adjust your time in the Dashboard'), and the Express Labor Analytics report names the offline state only as a reporting gap ('Net sales missing ... The POS is currently running offline mode ... Wait until the POS is back online', 4609212417). The 320th had already found labor-web (170 files) carrying no offline-punch string. WEAKEST ROW of this batch: an undocumented queue could still exist in the device, so this no rests on the claim's documentation conjunct. BOUND: the FIRST full-BODY census of help.spoton.com, taken from the publisher's own listing (Confluence v2 API https://help.spoton.com/api/v2/pages?limit=100&sort=-modified-date&body-format=storage, paged to fixpoint - rounds 29 and 30 returned 0 new pages): 2,145 pages WITH BODIES (1,083 current + 1,062 archived), 4,154,015 chars of tag-stripped text, version dates 2020-11-24..2026-09-17. Validation: 141 of the 142 help-centre page ids already cited in this record are inside the listing; the one absent (4456513592) now 404s on the API itself, so the KB is a census minus one deleted page. Prior passes held bodies for only the 121 most-recently-modified pages and titles for the rest. Controls are tokenised word-boundary case-insensitive over all 2,145 bodies; the denominator is 2,145. Retrieved 2026-09-17. || 327th: 327th: the 325th's merge hold is respected - the SpotOn Teamwork KB (a separate KnowledgeOwl publisher) was NOT used and remains the corpus that would have to be censused. NEW SURFACE instead: the Centralized API's Labor service, held complete inside the 49-page llms.txt census - Retrieve Time Punches, Retrieve Time Punch Details, Retrieve Break Types/Details, Retrieve/Create/Update/Delete Employee, Retrieve Jobs - every one of them tagged 'EXPRESS ONLY' in the vendor's own index. Across those specs there is no offline, queue, sync, reconcile or conflict semantics on a punch object at all: the time-punch resource is read-only over HTTP against api.spoton.com, so the API layer neither supports nor refutes an offline punch and cannot settle the cell either. Retrieved 2026-09-18. || 328th: 328th, NEW SURFACE inside the on-disk 2,145-body Confluence census: a SECOND vendor-authored offline enumeration nobody had cited, 'Offline Mode with Fresh KDS | SpotOn Express' (help.spoton.com/space/SK/5085823000, version of 2026-04-15). It is an explicit closed list of what does NOT survive an offline period - 'Signing into Fresh KDS (new login)', 'Receiving online orders', 'Screen-to-screen communication (bumping items between screens)', 'SMS updates', 'Real-time Fresh KDS analytics' - and a time punch appears neither there nor in the positive list of the configuration article ('Orders and payments continue; data syncs once the internet connection is restored. Orders are still sent to the kitchen printer or KDS'). A third offline enumeration, 'Offline Payments on Your SpotOn A800' (/4658331708), likewise scopes offline behaviour to card transactions only ('Payments are stored securely on the device ... Once the terminal reconnects, stored payments are automatically sent for processing') and lists offline LIMITS (max per transaction, max total, max time offline) with no labour object. Tokenised over the whole 2,145-doc census: `time punch` 3 docs, and the only two that are SpotOn Express both carry the same FAQ sentence - 'Currently, forced clock-in is not an integrated feature of SpotOn Express. However, requiring a time punch for POS access is on the future roadmap' (/3644358718, /4477911076) - while the third (/2239266968) is the SpotOn TEAMWORK article, a different publisher (support.dolceclock.com), which the 325th merge hold bars from carrying this cell. So SpotOn now has three published offline enumerations and none of them states punch capture or reconcile-on-reconnect semantics; the claim's 'with the behavior documented' conjunct is unmet, but per the 326th hold that a missing offline statement does not carry a capability `no`, this stays unknown. Retrieved 2026-09-18. || 330th: 330th: the 325th merge hold on this cell (the absence was bounded to help.spoton.com, the wrong publisher, because time & attendance is SpotOn Teamwork on its own KnowledgeOwl KB) is now DISCHARGED - the Teamwork KB is censused. support.dolceclock.com/sitemap.xml re-derived 2026-09-18: 333 URLs (332 articles + root), all 333 held as rendered bodies, 335,268 stripped chars; HREF FIXPOINT run over the 333 stored HTML files found 328 distinct /help/<slug> references and 0 articles outside the sitemap (the 5 apparent extras are truncated-string artefacts and every one of them 404s, e.g. /help/adding-salary-wages 404, /help/manager-approval-of-payroll-7564b01 404 - the 404 body is a constant 46,885 bytes, which is the discriminator). TOKENISED, word-boundary, case-insensitive controls over that census (known-positives: `time punch` 32 docs, `clock in` 9, `sync` 22): `offline` 0 docs, `internet connection` 0, `no internet` 0, `outage` 0, `cellular` 0, `data connection` 0, `unable to clock` 0, `cannot clock` 0; `network` 1 doc (an FTP export article), `connectivity` 1 (a payroll-integration overview), `internet` 1 (a login article), `wifi` 2 (geofence setup, onboarding timeline). So the labour publisher itself never describes offline punch capture or reconcile-on-reconnect anywhere. The nearest documents describe an ONLINE round trip: 'SpotOn Restaurant POS | Two Way Sync Behavior' (a complete sync matrix - 'Clock in/out in POS (with or without breaks) -> Teamwork Yes', 'Edit start/end time on a past time punch ... Yes') with no offline or queued row, and 'Spoton Integrated Clock-In', where each punch waits on a server round trip ('After PIN-In ... a 2nd screen will pop up with additional choices, ie schedule enforcement, compliance questions etc. (this can take 3 seconds)') and a manager override is validated against the employee's 'Manager's TEAMWORK password' / 'TEAMWORK PIN'. One more POS-side fragment, in the SpotOn Express Labor Analytics Report troubleshooting table (help.spoton.com/space/SK/4609212417): the only offline-caused symptom it lists is 'Net sales missing ... The POS is currently running offline mode ... Wait until the POS is back online and the data syncs to the system' - labour hours are not listed as affected, but that is an inference from a troubleshooting table, not a statement about punch capture. Both publishers are now bounded and neither documents the behaviour; per the standing holds that a missing offline statement does not carry a capability `no` and that 'never affirmed' is not a `no` on offline behaviour, this stays unknown - the only thing that has changed is that the corpus objection is gone. Retrieved 2026-09-18. https://help.spoton.com/space/SK/4073652945 · retrieved 2026-09-18 adversarially verified

Permissions are grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers.

labor-granular-rbac

Job Positions grant permissions per discrete action, not per tier. The Create Job Position article enumerates individually toggled rights including "Pre-Authorize Credit Cards", "Manage House Accounts", "Can Start Tabs", "Can Approve Default Tab Amount Adjustments" (under Cash Management), Take Payment Ownership, Transfer, and gift-card/loyalty handling, with a companion "Job Positions: Permissions, FAQs, and Best Practices" article. Express has an equivalent split between Employee POS Permissions and Manager Permissions, and permissions are set per location through Location Specific Settings. https://help.spoton.com/space/SK/2660663297 · retrieved 2026-08-03

Manager overrides and approvals are attributed to the individual approver and written to an immutable audit trail queryable after the fact.

labor-manager-override-audit

Overrides are attributed to an individual: approvals require a manager code or a Manager Card, and "the system reads the numeric swipe code printed on the back of the card and matches it to the employee profile configured in BOH". Shortfalls: the same article discloses a real weakness — "Are manager cards encrypted? No. Manager cards are not encrypted. The system reads the plain-text numeric code printed on the back of the card" — and no immutable, queryable override audit trail is documented in the reporting set. https://help.spoton.com/space/SK/5197037595 · retrieved 2026-08-03

Builds and publishes employee shift schedules inside the same platform that holds the timekeeping data, rather than requiring a third-party scheduling app. differentiator

labor-native-scheduling

Scheduling and timekeeping do sit in one system, but that system is not the POS. SpotOn’s own "Scheduling | SpotOn Teamwork" article contains no documentation - it is a five-link stub whose every target is support.dolceclock.com, the knowledge base of the Dolce product SpotOn acquired and rebadged. Behind it the capability is real: schedule authoring and publishing, copy-forward from a prior week or template, sales projections and weather on the schedule, availability and time off, and an employee app, all against the same punch data. Shortfalls: Teamwork is a separately sold SKU rather than part of any POS plan - the word "Teamwork" does not appear on spoton.com/pricing/ at all, which lists only an unpriced "Labor management suite" link - and it is documented on a separate legacy domain under its pre-acquisition brand. https://support.dolceclock.com/help/scheduling-overview · retrieved 2026-08-03 adversarially verified

Generates recommended staffing levels or labor hours by daypart from the operator's own POS sales history, not just a static template. differentiator

labor-demand-labor-forecast

SpotOn Teamwork is described as covering "scheduling, labor forecasting, time and attendance, payroll preparation, tip distribution, employee communication, compliance, and workforce management — all within a single platform". Shortfall: labour forecasting appears only in that capability list; no article documents how a recommended staffing level or hour target is generated from the operator's own POS sales history, and none of the 25 Teamwork articles covers a forecast screen. https://help.spoton.com/space/SK/2239594711 · retrieved 2026-08-03

Displays labor cost as a percentage of sales in real time during service on a manager view or POS, not only in end-of-day or next-morning reports. differentiator

labor-realtime-labor-percent

Labour against sales is reported at hourly granularity — "Sales & Labor by Hour Report" for RPOS and a "Labor Analytics Report" plus "Clocked In Employees" view for Express, all built from actual clocked hours. Shortfall: these are reporting surfaces refreshed from the Dashboard, not a live labour-percentage readout on a manager screen during service; no real-time labour target or alert is documented. https://help.spoton.com/space/SK/4659609601 · retrieved 2026-08-03

Warns or blocks at clock-in when an employee is approaching or would cross a configured overtime threshold, before the overtime is incurred. differentiator

labor-overtime-prevention

Overtime is configurable — Express has an "Overtime Settings" article under Team Management and an auto-clock-out feature, and Teamwork carries California labour settings and payroll approval. Shortfall: no warning or block at clock-in when an employee is approaching a threshold is documented; the documented controls set how overtime is calculated and paid, not how it is prevented. https://help.spoton.com/space/SK/3838410774 · retrieved 2026-08-03

Configures meal and rest break rules per state or jurisdiction, prompts required break attestation, and flags missed breaks for premium pay. differentiator

labor-break-compliance-by-state

Break compliance is genuinely built, but for one jurisdiction: SpotOn Teamwork ships "California Break Law Tracking & Control" and "California Labor Settings" as dedicated articles, and Express adds customisable breaks and "Auto-End Breaks When Clocking Out". Shortfall: California is the only state with documented rules; no per-jurisdiction rule library, no break attestation prompt, and no missed-break premium-pay flag are documented for anywhere else. https://help.spoton.com/space/SK/2239398079 · retrieved 2026-08-03

Enforces minor-labor restrictions (age-based maximum hours, prohibited time windows, school-day limits) at both scheduling and clock-in.

labor-minor-labor-rules

Teamwork's Labor Compliance overview enumerates the entire compliance engine: meal and rest break tracking and enforcement, break waivers, violation reporting and payroll penalties, punch validation, "Split Shift Premium", "Spread of Hours", and "Teamwork tracks 40hr, 8hr, 12hr, 6-day consecutive, and rolling-24 overtime." No age-based cap, prohibited-hours window or school-day rule. https://support.dolceclock.com/help/labor-compliance-and-time-punch-validation-overview · retrieved 2026-09-05 adversarially verified

Computes tip pooling and tip-outs automatically per shift from configurable rules (percentage of sales, hours worked, points, or role), rather than requiring a manual spreadsheet.

labor-tip-pooling-rules

Pooling is computed automatically rather than by spreadsheet: RPOS Teams allocates "by percentage of hours each member worked on the team" and produces a Team Closeout, Express has Dashboard Tip Pooling with its own setup, FAQ and troubleshooting articles, and Teamwork carries a Tips article and a DayCheck payout path. Shortfalls: hours-worked is the only documented allocation basis; Express pooling "applies only to credit card tips" and is off by default; and percentage-of-sales, points and role-based rules are reached only through the TipHaus or GratShare partner integrations. https://help.spoton.com/space/SK/2021425371 · retrieved 2026-08-03

Retains a per-shift, per-employee record of tips received, amounts contributed to the pool, and amounts distributed from the pool, exportable for audit.

labor-tip-distribution-audit-trail

A per-shift record exists and is used operationally: Teamwork requires the manager to "confirm the Bundle Total... the sum of all the tips earned through your company's Teamwork tip rules for the day, often excluding declared cash tips" before approving payouts to DayCheck, and Team Closeouts show team tip distribution above individual closeouts. Shortfall: no article documents an exportable per-employee record of contributions into and distributions out of the pool for audit; the documented artefacts are closeouts and payroll reports. https://help.spoton.com/space/SK/4140433518 · retrieved 2026-08-03

Payroll export separates cash from charged qualified tips and carries a Treasury tipped-occupation code, supporting the W-2 Box 12 code TP and Box 14b reporting required for tax year 2026. differentiator

labor-qualified-tips-w2-reporting

Express Payroll Report exports hours, wages and tips per employee and job position to CSV, with auto gratuity 'shown in its own column because gratuity is taxed differently than tips'; RPOS close reports separate Cash from Non-Cash Tips ('credit card or electronic tips') and auto-gratuity (Close Report Summaries; Cash Reconciliation). Shortfalls: no Treasury tipped-occupation code, no W-2 Box 12 code TP or Box 14b handling, and no qualified/non-qualified tip designation is documented; the only SpotOn treatment of the 2025 rule is a blog explainer that says operators 'will still track, report, and run payroll for tip income the same way they always have'. https://help.spoton.com/space/SK/4512907295 · retrieved 2026-09-03 adversarially verified

Vendor processes payroll itself as a first-party product (tax filing and direct deposit), as opposed to exporting to a third-party payroll provider only. differentiator

labor-native-payroll

Teamwork carries the payroll preparation half of the job: dedicated articles cover Payroll Routines, Manager Approval of Payroll, Employee Wages, Entering & Updating Payment and ADP Onboarding, and DayCheck provides employee-side earned-wage transfers to a bank account. Shortfall: SpotOn does not file payroll taxes or run direct deposit as a first-party payroll product — the documented terminus is an approved payroll run handed to a third-party provider (ADP onboarding, ADP and Paycor formatted exports). https://help.spoton.com/space/SK/2239660191 · retrieved 2026-08-03

Exports timecards, wages, and tips in documented formats or via direct integration for at least two major payroll providers (e.g. Gusto, ADP, Paychex, QuickBooks).

labor-payroll-export-formats

The Payroll, Tip Distribution & Scheduling integrations page enumerates named, vendor-maintained connections: an "ADP Formatted Export", a "Paycor (Export)", plus 7shifts, HotSchedules, TipHaus and GratShare. Payroll Reports exist as first-class reports on both RPOS and Express, and QuickBooks is separately connected for the accounting side. https://help.spoton.com/space/SK/2320269514 · retrieved 2026-08-03

Employees can request shift swaps or claim open shifts in a self-service app, subject to a manager approval workflow that enforces overtime and role eligibility. differentiator

labor-shift-swap-workflow

The self-service and approval halves are documented: an employee presses "Offer this Shift" to release it for pickup, others "Request" it (subject to being qualified for the role), direct employee-to-employee swaps are supported, and managers "can Approve or Deny from the dropdown menu" from their dashboard, with request timestamps shown and approving one request automatically denying the rest. Shortfalls: the overtime limb of the claim is unaddressed - no overtime projection, warning or block is described anywhere in the trade validation flow; and the whole workflow lives in SpotOn Teamwork, a separately priced product documented on support.dolceclock.com, not in the POS. https://support.dolceclock.com/help/manage-shift-trades-swaps · retrieved 2026-08-03 adversarially verified

Reports per-employee sales performance metrics (average check, items or category attachment rate, void and comp rate) by server or cashier. differentiator

labor-server-performance-metrics

Per-employee performance data is produced at closeout: "Server Reports include cash totals, payments, discounts, paid ins/outs, surcharges, group sales, POS activity, and gift card details", and closeout rules are configurable per job position. Shortfall: the documented metrics are financial totals — average check, items per check, category attachment rate and void/comp rate per server are not documented as reported figures anywhere in the report set. https://help.spoton.com/space/SK/2056815023 · retrieved 2026-08-03

Supports multi-level recipe/BOM costing where a recipe can contain sub-recipes (prep items) and plate cost recalculates automatically when any component ingredient's cost changes.

inventory-recipe-bom-costing

The menu item carries one flat cost field and no components: "Item Cost – Enter the actual cost of the item (not the selling price)". There is no recipe object, no sub-recipe, and no ingredient linkage in the RPOS BOH menu articles or the Express menu settings. Multi-level recipe costing is explicitly the partners' territory — MarginEdge is introduced as "a recipe cost-tracking and restaurant inventory management solution", and COGS-Well provides "Inventory Control, Recipe Management, Food & Beverage Cost Analysis". https://help.spoton.com/space/SK/2658041953 · retrieved 2026-08-03

Stores purchase unit, recipe unit, and count unit per item with explicit conversion factors, plus a yield/waste percentage applied to raw-to-usable conversion.

inventory-unit-conversion-yields

The bulk editor enumerates the complete inventory field set on a menu item: Price, Price Levels, Item Cost ("Enter the actual cost of the item (not the selling price)"), an Available checkbox, Use Quantity On Hand ("Enable this option to automatically subtract sold items from inventory") and Quantity On Hand. No purchase, recipe or count unit, no conversion factor, no yield percentage. https://help.spoton.com/space/SK/2658041953 · retrieved 2026-09-05 adversarially verified

Produces a theoretical-vs-actual usage variance report per item for a defined count period, showing theoretical usage from POS sales times recipe, actual usage from counts plus receipts, and the variance in both units and currency. differentiator

inventory-theoretical-vs-actual

Variance analysis is delivered by a partner, not the POS: "SpotOn Restaurant's system sends all sales and transaction data to MarginEdge. By combining the invoice and sales data, MarginEdge can help track theoretical versus actual" usage. The COGS-Well integration is likewise "a read-only connection that allows COGS-Well to receive item-specific sales data directly from your POS system". SpotOn's own inventory surface is a per-menu-item Quantity on Hand counter, which cannot produce an ingredient-level variance. https://help.spoton.com/space/SK/2319286766 · retrieved 2026-08-03

Depletes ingredient on-hand quantities in near real time as orders are fired at the POS, including depletion driven by modifier selections, not only in an end-of-day batch. differentiator

inventory-realtime-depletion

Depletion is real but shallow: "Use Quantity On Hand – Enable this option to automatically subtract sold items from inventory. Quantity On Hand – Reflects the actual number of items available in your business", decrementing as orders are rung and greying the item out at zero. Shortfalls: depletion is per menu item, not per ingredient, so modifier-driven consumption is not tracked; and the feature does not exist on the newer product at all — "Quantity on Hand is not available in SpotOn Express." https://help.spoton.com/space/SK/2658041953 · retrieved 2026-08-03

Automatically 86s (marks unavailable) menu items on the POS, online ordering, and connected third-party delivery menus when a component ingredient hits zero or a configured threshold. differentiator

inventory-86-auto-sync

The POS half works: "menu items will display the remaining quantity available and automatically become unavailable once inventory reaches zero", and items with zero quantity "appear grayed out on the menu and cannot be selected". Shortfalls: the trigger is the menu item's own count, not a component ingredient hitting a threshold, and no article states that an auto-86 from Quantity on Hand propagates to first-party online ordering or to connected third-party menus. https://help.spoton.com/space/SK/2299887676 · retrieved 2026-08-03

Supports full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts.

inventory-count-modes

There is no count object. The only restock path: "Can I manually restock an item? Yes. Open the item settings, update the Quantity on Hand value, and save the changes." Editing the field overwrites the number - no count session, no spot count, no cycle count, no variance history. Standsheets and True Up Count Variance exist only in the archived Enterprise venue product. https://help.spoton.com/space/SK/2299887676 · retrieved 2026-09-05 adversarially verified

Provides a mobile/tablet counting app supporting barcode or QR scanning that continues to accept counts with no network connectivity and syncs on reconnect.

inventory-mobile-count-offline

CLAIM: a mobile/tablet counting app with barcode or QR scanning that keeps accepting counts with no network connectivity and syncs on reconnect. VERDICT: unknown -> no. NEW SURFACE (323rd) and a CORRECTION OF THE 320th: the merchant-dashboard modules the 320th recorded as "Refused (403) and therefore NOT held" are NOT refused. Two things were wrong. (1) A Cloudflare/CloudFront 403 to node's fetch is a FALSE refusal: with curl carrying a browser UA plus Accept and Accept-Language, invoices-web (3,091,564 B), mbo-agent-web (1,626,895 B), partnerships-embedded (2,026,725 B) and virtual-terminal-legacy-web (3,963,912 B) all return 200. (2) settings-web and virtual-terminal-web were never blocked at all - their import-map URL is a 489-byte / 337-byte System.register LOADER STUB that names the real bundle, e.g. settings-web's stub loads ./assets/spoton-settings-web-BVYEUikC.js (991,568 B). AND THAT APP SHIPS PUBLIC SOURCE MAPS. Taking settings-web's './<chunk>.js' reference set to fixpoint: 116 chunks, and 116 of 116 carry a real source map (12,975,309 B of maps, every one {"version":3, with sourcesContent) - ZERO unmapped chunks - yielding 482 original TypeScript/TSX source files, 2,192,895 bytes, of SpotOn's own settings application (grade B, the vendor's own shipped source). Soft-200 control: /assets/zzz-nope.js returns 1,572 bytes of text/html, nothing like a map, so these are real files. The 482 sources are the COMPLETE merchant-dashboard settings surface for both Express and RPOS merchants: accountSettings, bankAndTax, batchTimes, businessHours + newBusinessHours (incl. Dayparts and Reporting/fiscal hours), businessInformation (incl. ReceiptCustomization), employees + multiLocationEmployees, giftcards, laborAndCompliance (AutoClockout, BreakTypes, Overtime, CashTipsManagement, ScheduleEnforcement), managerPermissions, permissions, myAccount, ordersAndTips (OrderTypes, AutoGratuity, TipAmounts, AutoprintReceipts, RequireName), paymentTypes (cash, customTenders), posUiSettings (DefaultTab, GuestCount), reportSubscriptions, revenueCenters, security, support, taxesFees (taxes, fees, surcharge), plus the legacy settings app. BOUND/LIMIT: this is the SETTINGS app only - menu (express-menu-web), loyalty (loyalty-web, reached from settings by an external link to `${applicationBase}loyalty/settings`), reporting and the POS/KDS device apps are separate modules and are not covered by this census. EVIDENCE: the token inventory scores ZERO across all 482 settings source files - there is no inventory feature, no count sheet, no unit-of-measure and no stock configuration anywhere in the merchant dashboard's settings application, whose feature list is enumerated above and is complete. That closes the gap the 320th note left open (it could only say the dashboard NAV dictionary showed no inventory module, and that settings-web was refused). Taken with the 320th's controls over the 38-module import map ("inventory count" 0, "stock count" 0, "count sheet" 0, the barcode hits being the shared BarcodeIcon in every module) and the help centre, whose only stock feature is Quantity on Hand ("Enable / Edit Quantity on Hand | SpotOn Restaurant FOH", 2299887676) which decrements on sale rather than counting, SpotOn ships no counting app at all - so the offline and scanning conjuncts cannot be met. Retrieved 2026-09-17. https://settings-web.spoton.com/assets/spoton-settings-web-BVYEUikC.js.map · retrieved 2026-09-17 adversarially verified

Ships pre-built electronic vendor catalog and order-transmission integrations with named broadline distributors (e.g. Sysco, US Foods, Performance Food Group) that send purchase orders and receive invoices electronically rather than by emailed PDF. differentiator

inventory-vendor-catalogs-edi

Purchasing is ceded, not shipped. The current Craftable article sells the ordering workflow as the partner's: "Save time and simplify the inventory ordering process by placing all orders from one central location." SpotOn's KB has no vendor, purchase order or invoice object for RPOS or Express; the only Purchase Orders Report is archived Enterprise. No broadline distributor is named. https://help.spoton.com/space/SK/2320466111 · retrieved 2026-09-05 adversarially verified

Ingests supplier invoices from photo, PDF, or email and extracts line-item detail (item, quantity, unit, price) into the inventory ledger without manual line entry. differentiator

inventory-invoice-ocr

Invoice capture is explicitly a partner function: with MarginEdge, "users can take photos of their invoices, and MarginEdge will automatically translate them into prices and quantities in its system". SpotOn ships no invoice ingestion of its own — there is no accounts-payable or supplier-invoice object anywhere in the knowledge base. https://help.spoton.com/space/SK/2319286766 · retrieved 2026-08-03

Tracks per-item purchase price history across invoices and alerts when a received price exceeds the prior or contracted price by a configurable threshold. differentiator

inventory-price-change-alerts

SpotOn holds no invoice and so no purchase price history. The current MarginEdge article puts the whole function with the partner: "users can take photos of their invoices, and MarginEdge will automatically translate them into prices and quantities in its system." SpotOn's own item record carries one flat Item Cost field typed in by a user, with no received-price series and no threshold alert. https://help.spoton.com/space/SK/2319286766 · retrieved 2026-09-05 adversarially verified

Maintains par levels per item per location and generates suggested purchase order quantities from on-hand versus par, with at least one mode driven by a sales forecast rather than a static par. differentiator

inventory-par-auto-suggest

No par level and no suggested order. Replenishment is a manual field edit: "Can I manually restock an item? Yes. Open the item settings, update the Quantity on Hand value, and save the changes", and the only threshold is zero - "The menu item automatically becomes unavailable and appears grayed out in FOH." Par Level Configurations are archived-Enterprise only. No forecast mode. https://help.spoton.com/space/SK/2299887676 · retrieved 2026-09-05 adversarially verified

Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.

inventory-waste-logging

Waste is partner territory: "Reduce Theft, Spoilage, and Waste Track and compare product usage versus sales to identify discrepancies, reduce waste, and protect your margins." SpotOn's own inventory surface has no waste path - Quantity on Hand (SK/2299887676) changes only by sale, manual edit, Out of Stock or a void - no reason codes, no waste cost report. Spoilage Reports are archived Enterprise. https://help.spoton.com/space/SK/4223008935 · retrieved 2026-09-05 adversarially verified

Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.

inventory-shelf-life-expiry

The complete inventory field set on a menu item is enumerated here: Price, Price Levels, Item Cost ("Enter the actual cost of the item (not the selling price)"), an Available checkbox and Quantity On Hand ("Reflects the actual number of items available in your business"). A quantity and a cost, with no lot, batch, received or use-by date, and no receiving record for a date to hang on. https://help.spoton.com/space/SK/2658041953 · retrieved 2026-09-05 adversarially verified

Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting.

inventory-bar-partial-bottle

Beverage-level inventory is delivered entirely by named third parties. The Inventory Management Integrations index enumerates BarTrack, BarVision, BeerSAVER, Bevchek, BevSpot, COGS-Well, Craftable, MarginEdge, QSROnline and Sculpture Hospitality — BarVision exists to identify "over-pours, unrecorded pours, and loss points" — and SpotOn itself has no weight-based or fractional-bottle inventory construct, only a whole-unit Quantity on Hand per menu item. https://help.spoton.com/space/SK/2319024540 · retrieved 2026-08-03

Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.

inventory-cogs-gl-export

Accounting export is native and named: a "QuickBooks Export | SpotOn Restaurant Reporting" report ships in the reporting set, alongside Shogo, DAVO, BackOffice (formerly RASI) and Restaurant365 connectors. Shortfall: what exports is sales and tender data, not period COGS or accounts-payable invoice detail — SpotOn holds no invoice ledger and no ingredient cost, so GL account mapping per item category is not documented. https://help.spoton.com/space/SK/4659576833 · retrieved 2026-08-03

Inventory and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator

inventory-native-not-partner

SpotOn's own inventory is a per-menu-item Quantity on Hand counter that decrements on sale — no ingredients, no recipes, no counts, no invoices. Everything above that line is contracted separately: the Inventory Management Integrations index lists ten third-party products (BarTrack, BarVision, BeerSAVER, Bevchek, BevSpot, COGS-Well, Craftable, MarginEdge, QSROnline, Sculpture Hospitality), and Restaurant365 is listed again under accounting. This is the clearest case of ceded territory in the record. https://help.spoton.com/space/SK/2319024540 · retrieved 2026-08-03

Joins recipe cost to actual item sales mix to report contribution margin per menu item, and flags items whose margin fell below a configured threshold after ingredient cost changes. differentiator

inventory-menu-margin-linkage

A first-party Profit Report ships in the RPOS reporting set, and it has something to work with: the menu item carries an Item Cost field distinct from price, and Express offers colour coding for "high-margin items". Shortfall: margin is computed from a hand-entered flat item cost rather than a recipe, so it does not move when an ingredient price changes, and no threshold alerting on margin erosion is documented. https://help.spoton.com/space/SK/4652466180 · retrieved 2026-08-03

Provides a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise.

reporting-realtime-dashboard

The SpotOn Dashboard is the reporting home for both product lines, with Custom Views for restaurant POS, a customisable restaurant reporting view, and Daily Recap. Off-premise mobile access is a documented first-party app: "SpotOn Restaurant Reports App (RPOS)" sits in the RPOS reporting section alongside the browser Dashboard. https://help.spoton.com/space/SK/3783491608 · retrieved 2026-08-03

Generates a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types, and expected cash deposit in one document.

reporting-eod-closeout

"Closeout & End of Day Reports | SpotOn Restaurant Reporting" documents a single close document covering sales, surcharges and taxes, with "Surcharge Summary — the specific breakdown of any surcharges that were used during this shift", sales average by guest, and companion articles for Close Out Settings, Close Report Summaries, "Set Up Cash Due Equals and Open Cash Exclusion Rules for Your Location" and per-job-position closeout rules. https://help.spoton.com/space/SK/2405498881 · retrieved 2026-08-03

Provides a product mix (PMIX) report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center.

reporting-pmix-modifier-level

A Product Mix Report ships as a named report on RPOS and Express, and modifier-level sales are captured in it — the Sub Items article notes "Modifiers are still tracked in reporting. If front-of-house usability benefits from implementing Fries as a modifier, the sales can easily be calculated by adding the Fries item to the Fries modifier." Express adds "DayParts Reporting" for the daypart slice, and revenue-centre style grouping comes from Report Groups in the closeout ("Surcharges, Report Groups, and POS Summaries"). https://help.spoton.com/space/SK/2320859149 · retrieved 2026-08-03

Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.

reporting-comps-voids-audit

Discount and POS-activity data is reported per employee — "Server Reports include cash totals, payments, discounts, paid ins/outs, surcharges, group sales, POS activity" — and voids are permission-gated with manager approval at the point of action. Shortfall: no dedicated comps/voids/price-override exception report is documented, and nothing records the approving manager alongside the acting employee with a reason code and timestamp in a queryable report. https://help.spoton.com/space/SK/2056815023 · retrieved 2026-08-03

Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.

reporting-cash-over-short

Closeout & End of Day Reports covers "shift checkouts, balance cash drawers, track revenue, and handle special transactions", cash drawers are assignable to individual users so "the cash drawers will only open if that employee does a cash transaction or no sale", paid-ins and paid-outs are recorded against the drawer, and "Set Up Cash Due Equals and Open Cash Exclusion Rules for Your Location" configures how expected cash is derived. https://help.spoton.com/space/SK/2403664096 · retrieved 2026-08-03

Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.

reporting-labor-productivity

"Sales & Labor by Hour Report | SpotOn Restaurant Reporting" reports labour against sales by hour from clocked time, Payroll Reports ship on both product lines, and Express adds a Labor Analytics Report plus a Clocked In Employees view. Timekeeping is the POS clock (Teamwork on RPOS, Team Management on Express), so the hours are actuals rather than scheduled. https://help.spoton.com/space/SK/4659609601 · retrieved 2026-08-03

Reports per-server metrics including average check, items per check, attachment rate for named categories, and tips as a percentage of sales. differentiator

reporting-server-scorecards

Per-server reporting exists at closeout with cash totals, payments, discounts, surcharges, group sales, POS activity and gift-card detail, printable from the FOH. Shortfall: none of the four metrics the claim names — average check, items per check, category attachment rate, tips as a percentage of sales — is documented as a reported figure. https://help.spoton.com/space/SK/2056815023 · retrieved 2026-08-03

Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator

reporting-channel-profitability

Revenue is sliced by channel: the Express Sales Summary reports "Order Origin: POS, Kiosk, Digital Ordering, DoorDash Marketplace, etc.", and Uber Eats sales "roll into SpotOn reporting for clean reconciliation". Shortfall: the figure is gross revenue by origin — marketplace commission, marketing fees and refunds are not subtracted, so no margin or net contribution by channel is produced. https://help.spoton.com/space/SK/4514021383 · retrieved 2026-08-03

Supports scheduling any report for automatic recurring delivery by email or to a shared destination on a defined cadence and recipient list.

reporting-scheduled-delivery

"Reporting Subscriptions allow you to receive automated daily email reports for any report that includes the Print button with a drop-down menu. This makes it easy to receive reports such as Product Mix, Sales, or Labor summaries without logging in each day", with multi-location handling addressed in the same article, and Express has a confirmed-email subscription for the Daily Recap. Shortfall: only a daily cadence is documented — no weekly/monthly schedule and no defined recipient-list management is described. https://help.spoton.com/space/SK/2349728048 · retrieved 2026-08-03

Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator

reporting-public-api

SpotOn documents a public REST API covering the claimed data domains, but credentials are not self-service. Met: the anonymous Centralized API reference (developers.spoton.com/central-api, re-fetched 2026-09-15) documents 'The Centralized Reporting API' with GET /reporting/v1/locations/{location_id}/orders on https://api.spoton.com ('Retrieve a list of historical orders for a given location'), filterable by created time, fiscal date and updated time with pagination; each order carries checks, discounts, taxes, gratuity and payments[] with tips_amount, fees_amount, surcharges, is_refund, is_void, card_type and employee. The index also lists menu reads (Retrieve Menus, Retrieve Reporting Categories) and labor reads (Retrieve Employees, Retrieve Jobs, Retrieve Time Punches), so orders, payments, menu and labor are all covered. Falls short: (1) credentials are not self-service. The SpotOn OAuth guide says 'To get started, you'll need to request the following credentials from SpotOn: Client ID ...'; scopes are assigned 'Based on the nature of your business and integration needs' and 'Additional scopes might be available as per your specific integration agreement'; the Certification Process page says integrations must be certified before launch and comply 'with the terms outlined in SpotOn's API agreement', followed by a mandatory 5-10 merchant pilot. No signup or key self-issue is documented. (2) Labor endpoints and menu-item lists are marked 'EXPRESS ONLY', so the labor domain does not cover SpotOn Restaurant (RPOS) merchants. (3) Access to any location requires that merchant to authorize the app via Sign In With SpotOn. https://developers.spoton.com/central-api/reference/reportingservice_getorders.md · retrieved 2026-09-15 adversarially verified

Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator

reporting-webhooks

No webhook, event-stream or callback documentation exists on any public SpotOn property. The developer centre offers only a partner intake form, and no knowledge-base article describes subscribing to order or payment events. https://www.spoton.com/developer-center/ · retrieved 2026-08-03

API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator

reporting-api-not-upcharged

330th: the RAW-DATA half of this claim is now settled on two surfaces. (1) The published Point-of-Sale Terms (https://www.spoton.com/legal/point-of-sale-terms/, retrieved 2026-09-18) enumerate SpotOn Restaurant's whole standard fee schedule - deposit, hardware, implementation, shipping, tax, 'The monthly POS service fee includes software licensing fee, software updates and 24/7 technical support', a $995 processor-conversion fee, a $15/GB LTE overage - with no data, export, analytics or API line item, and no tier. (2) Over the 2,145-body help.spoton.com Confluence census (the publisher's own v2 listing API, fixpoint), tokenised controls: `higher tier` 0 docs, `enterprise plan` 0 docs, while `export` scores 96 docs and `CSV` 71, and the report articles offer the export unconditionally - e.g. Labor Analytics Report (/4609212417): 'Can I export this report? Yes. Select the Export button at the top right to download your results (CSV).' No article in the census conditions a report, an export or a data feed on a plan, an add-on or a contract type. WHY PARTIAL AND NOT YES: the claim also covers API access, and SpotOn publishes no price for it - developers.spoton.com grants access 'on a per location basis' under an unpublished 'API agreement', so a per-location API or revenue-share term cannot be excluded from a public corpus. Raw-data access is included; the API price remains unstated. Retrieved 2026-09-18. https://www.spoton.com/legal/point-of-sale-terms/ · retrieved 2026-09-18 adversarially verified

Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator

reporting-tier-paywall

The public pricing page states reporting is included rather than tiered, and the report set documented in the knowledge base (Product Mix, Sales & Labor by Hour, Payroll, Profit, House Accounts, Daily Sales Recap, Closeout) is presented without plan gating. Shortfall: this is a pricing-page claim rather than documentation — no article states which reports are available on which plan, and multi-location comparison reporting is not documented at all, so the entry-plan boundary cannot be verified. https://www.spoton.com/pricing/ · retrieved 2026-08-03

Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator

reporting-history-retention

Merchant Terms 6.12 'Accuracy, Currency, and Retention of Data' states the opposite of a committed window: 'Client will not rely on the information it transmits to SpotOn as an archive or backup, and will be responsible for retaining copies of all information Client sends SpotOn', and 'SpotOn makes no representations or warranties about its ability to return information'. No retention period is stated anywhere in the 21-document legal set. https://www.spoton.com/legal/merchant-terms/ · retrieved 2026-09-05 adversarially verified

Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator

reporting-anomaly-alerts

An "Alerts Configuration | SpotOn Restaurant Reporting" article exists and is cross-linked from the Profit Report, QuickBooks Export and the customisable reporting view, so alerting is wired into the restaurant reporting surface. Shortfall: the published article body carries no metric list, threshold model or delivery-channel detail, so the scope of what can be alerted on cannot be established from public documentation. https://help.spoton.com/space/SK/4617109547 · retrieved 2026-08-03

Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.

reporting-nl-query

SpotOn Profit AI produces AI insights over the operator's own data: 'Insights use your Point of Sale data, along with weather data, to explain changes in revenue and customer traffic', with KPI tiles that link through to reports. Shortfall: it is push, not query - 'A new set of insights is generated at the start of each week. Only the latest week is shown.' No ad-hoc natural-language question interface is documented. https://help.spoton.com/space/SK/5062950950 · retrieved 2026-09-05 adversarially verified

Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator

reporting-guest-cohorts

Guest-level counts are reported: the Dashboard Customers view segments by "Check-ins, New, Repeat, and Imported" when a loyalty programme is enabled, with a Loyalty Performance panel and Loyalty Spend & Redemption reporting. Shortfall: no visit-frequency distribution and no lifetime-spend cohorts are documented, so the analysis stops at new-versus-returning counts. https://help.spoton.com/space/SK/1059913822 · retrieved 2026-08-03

Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator

reporting-sales-forecast

CLAIM: a forward sales forecast at daypart or hourly granularity, built from the location's own history, shown in the reporting UI and usable by scheduling or ordering. VERDICT: partial/B. NEW SURFACE: the SpotOn Teamwork Knowledge Base (support.dolceclock.com, KnowledgeOwl). Its sitemap https://support.dolceclock.com/help/sitemap.xml lists 333 pages; all 333 returned 200 and 254 have article bodies. No earlier pass read these bodies: the record cited only SpotOn's stub page that links to them. The KB describes the product this way: "Teamwork is a labor management suite that is optimized for restaurants. We are a product within the greater SpotOn ecosystem used for scheduling employees, forecasting labor costs ...". EVIDENCE: https://support.dolceclock.com/help/entering-projected-sales says "From the schedule view, click on the sales forecast icon. From here, Teamwork gives you the ability to add a week's worth of sales projections with one click ... Use 4 Week Trend vs Prior Year applies Teamwork's algorithm. We observe year-over-year data and apply the trend (+/-) to your projections. Use 4 Week Average is a straight average of the previous four weeks of sales. Use Prior Week Actuals will take the previous weeks sales figures as this week's projection." It also says "Actual sales can be synced to your cloud-based POS ... Click Apply to use the software's projection based on trend data" and "When sales projections are populated, you will get a clear picture of your forecasted labor costs based on the schedules you build." So a forecast built from the location's own history exists and feeds scheduling, which meets those two parts of the claim. SHORTFALL: (1) the forecast is DAILY, one figure per day. (2) The only hourly figures are actuals, not forecasts: "Hourly Sales and Labor ... Sales are based on closed checks" (https://support.dolceclock.com/help/viewing-hourly-labor-analytics). No daypart or hourly projection is documented. (3) The forecast sits in the scheduling screen of Teamwork, a separate SpotOn labour product, not in the POS reporting UI. (4) Nothing feeds ordering. Retrieved 2026-09-16. https://support.dolceclock.com/help/entering-projected-sales · retrieved 2026-09-16 adversarially verified

Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.

reporting-tip-tax-compliance

Payroll Reports ship as a named report on both product lines, cash tips have a dedicated declaration workflow ("How to Report Cash Tips in SpotOn Express"), digital tips are managed pre- or post-payment, and Teamwork produces the tip bundle used for payout approval. Shortfall: no tax-liability summary by jurisdiction is documented, and the declared-versus-charged split is described operationally rather than as a report output. https://help.spoton.com/space/SK/4648075278 · retrieved 2026-08-03

Supports a named organizational hierarchy of at least three levels (e.g. enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations.

multi-location-org-hierarchy

Multi-unit is a first-class construct: "Menu upkeep for multi location organizations (RPOS)" describes chain-wide menus with per-location divergence, Location Specific Settings exist on menu items, modifiers, modifier groups and pricing events, and a "Company" grouping spans locations for employee access ("Employees can be added to multiple locations within the same Company using a single email address and login profile"). Shortfall: the documented shape is Company > Location — two levels. No region or group tier that reporting and permissions can be scoped to is documented. https://help.spoton.com/space/SK/2660663948 · retrieved 2026-08-03 adversarially verified

A corporate-level menu can be authored once and published to a chosen set of locations in a single action, with a publish/version history showing what was pushed, when, and by whom.

multi-location-central-menu-publish

Central authoring exists: the Menu Items Bulk Editor operates across locations — "If your organization has multiple locations, select one or more from the Locations field" — with a caution that "changes made in the bulk editor may affect multiple locations and menu groups simultaneously", and Location Specific Settings hold per-store overrides for price, availability, requisition routing and quantity on hand. Shortfall: no publish/version history showing what was pushed, when and by whom is documented, and no rollback of a bad push is described. https://help.spoton.com/space/SK/2658041953 · retrieved 2026-08-03

Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.

multi-location-price-zones

Three axes work without duplicating the item record. Per location: Location Specific Settings let the operator "Adjust individual item Price, toggle Availability (active/inactive), configure Requisition Settings... and manage Quantity on Hand", and "Changes made within Location-Specific Settings only apply to the individual location you selected. Global settings remain unaffected." Per daypart: Pricing Events (e.g. Happy Hour) are listed per item per location. Per channel: Order Types carry their own Price Level. Shortfall: there is no location-group or region object to price against - the documented org model is two levels, Company > Location - so the only choices are global or store-by-store, which the article states outright: "If you need to apply the exact same price or tax change to every location, make the edit in the main Menu Items tab rather than doing them individually per location." https://help.spoton.com/space/SK/2660893508 · retrieved 2026-08-03 adversarially verified

Provides above-store reporting that aggregates sales, labor, discounts, voids, and item mix across any selected set of locations in one view, with store-vs-store ranking and variance flags.

multi-location-consolidated-reporting

Above-store reporting exists — Reporting Subscriptions carries a dedicated "Using multiple locations?" section, the Dashboard scopes reports across the operator's locations, and Express reports run per location from one login. Shortfall: no store-versus-store ranking and no variance flagging are documented, and no article demonstrates an aggregated multi-location view of labour, discounts and item mix in one screen. https://help.spoton.com/space/SK/2349728048 · retrieved 2026-08-03

Gift cards issued at one location are redeemable at any other location in the brand, with a reported outstanding-liability balance and inter-store settlement/redemption reconciliation between owners.

multi-location-cross-location-giftcard

E-Gift Cards | SpotOn Order: e-gift cards 'can be used at all locations linked to the same organization (through group ID)', with organisation-level templates and promo cards; the gift-card product page adds 'Multi-location pooling - Automatically move gift card value across locations and accounts so revenue lands where it belongs'. Shortfalls: no outstanding-liability balance report and no inter-store settlement/redemption reconciliation are documented; physical card stored value is administered by eCard Systems. https://help.spoton.com/space/SK/1441267735 · retrieved 2026-09-03 adversarially verified

A single customer loyalty profile, balance, and stored order history is shared across all locations in the brand rather than being per-location.

multi-location-cross-location-loyalty

330th, NEW SURFACE and it settles the half the 328th could not: the PRODUCTION merchant-dashboard Customers micro-frontend, @spoton/customers-web (fetched anonymously from the live import map https://spoton-prod-import-map-public.s3.amazonaws.com/import-map.json, 75 entries, re-probed 2026-09-18 and still pointing at the SAME build hash 0bcc685..., 6,116,827 bytes; grade B = the vendor's shipped production code, not documentation). CLAIM: one profile, one BALANCE and one order history across all locations of the brand. WHAT THE CODE SAYS, verbatim: the loyalty client is `const LOYALTY_GUESTS_PATH="/loyalty/guests"; function fetchGuestBalance(K,Y){return API_V1.get(`${LOYALTY_GUESTS_PATH}/${K}/balances`,{params:{businessId:Y}})} function adjustGuestBalance(K,Y,J){return API_V1.patch(`${LOYALTY_GUESTS_PATH}/${K}/balances`,Y,{params:{businessId:J}})}` and the react-query key is `guestBalance:(K,Y)=>[...loyaltyServiceQueryKeys.all,"balance",K,Y]` - i.e. a guest's SPOT/POINT BALANCE is fetched and mutated PER businessId, and `getLocationBusinessIdFromDom` resolves that id out of the merchant hierarchy's `organizations[].locations[].business_location_id`, so the key is the LOCATION, not the brand. The Edit-Spots drawer makes it visible to the operator: the English dictionary holds `SELECT_A_LOCATION_SPOTS="Select a location to apply Spots"`, `SELECT_A_LOCATION_POINTS="Select a location to apply Points"` and the drawer renders a `SelectLocationSection` whose options come from that customer's own location list, and the adjust mutation invalidates TWO balances (`guestBalance(e0,t0)` and, when `invalidateBusinessId` differs, `guestBalance(e0,n0)`), which only makes sense if a guest holds a distinct balance at more than one business. WHAT IS SHARED (why this is a partial, not a `no`): the PROFILE and the program are brand-wide - one guestId carries `customerLocations`/`customerLocationsTotal`, the directory header renders a LocationPicker with `showAllLocationsOption:!0, defaultLocationId:"all"`, transactions/redemptions are keyed by guestId alone (`fetchGuestTransactions(K,Y)` params only), and @spoton/loyalty-web states `SETTINGS_ARE_VIEW_ONLY_DESCRIPTION="Loyalty settings for this location are managed at the group level. To make changes, please log in to the group account or contact your administrator."` plus `OPTED_IN_OUT_DISABLED_FOR_ROOT="Cannot be updated at Group level, please select a location."` This matches the published Central API, whose accrue/redeem/status/upsert paths are all `/loyalty/v1/locations/{location_id}/...`. VERDICT: one customer profile and one group-level program across the brand, but the earned balance is held and adjusted per location - the claim's 'balance ... shared across all locations' conjunct is NOT satisfied. Retrieved 2026-09-18. https://customers-web.ue1.prod.spoton.sh/spoton-customers-web-0bcc68512374e22b0bb98911a65a796980a83e63.js · retrieved 2026-09-18 adversarially verified

A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. differentiator

multi-location-multi-brand

CLAIM: a single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding and separately reportable revenue, on the same hardware and drawer. VERDICT: unknown -> no. NEW SURFACE (323rd) and a CORRECTION OF THE 320th: the merchant-dashboard modules the 320th recorded as "Refused (403) and therefore NOT held" are NOT refused. Two things were wrong. (1) A Cloudflare/CloudFront 403 to node's fetch is a FALSE refusal: with curl carrying a browser UA plus Accept and Accept-Language, invoices-web (3,091,564 B), mbo-agent-web (1,626,895 B), partnerships-embedded (2,026,725 B) and virtual-terminal-legacy-web (3,963,912 B) all return 200. (2) settings-web and virtual-terminal-web were never blocked at all - their import-map URL is a 489-byte / 337-byte System.register LOADER STUB that names the real bundle, e.g. settings-web's stub loads ./assets/spoton-settings-web-BVYEUikC.js (991,568 B). AND THAT APP SHIPS PUBLIC SOURCE MAPS. Taking settings-web's './<chunk>.js' reference set to fixpoint: 116 chunks, and 116 of 116 carry a real source map (12,975,309 B of maps, every one {"version":3, with sourcesContent) - ZERO unmapped chunks - yielding 482 original TypeScript/TSX source files, 2,192,895 bytes, of SpotOn's own settings application (grade B, the vendor's own shipped source). Soft-200 control: /assets/zzz-nope.js returns 1,572 bytes of text/html, nothing like a map, so these are real files. The 482 sources are the COMPLETE merchant-dashboard settings surface for both Express and RPOS merchants: accountSettings, bankAndTax, batchTimes, businessHours + newBusinessHours (incl. Dayparts and Reporting/fiscal hours), businessInformation (incl. ReceiptCustomization), employees + multiLocationEmployees, giftcards, laborAndCompliance (AutoClockout, BreakTypes, Overtime, CashTipsManagement, ScheduleEnforcement), managerPermissions, permissions, myAccount, ordersAndTips (OrderTypes, AutoGratuity, TipAmounts, AutoprintReceipts, RequireName), paymentTypes (cash, customTenders), posUiSettings (DefaultTab, GuestCount), reportSubscriptions, revenueCenters, security, support, taxesFees (taxes, fees, surcharge), plus the legacy settings app. BOUND/LIMIT: this is the SETTINGS app only - menu (express-menu-web), loyalty (loyalty-web, reached from settings by an external link to `${applicationBase}loyalty/settings`), reporting and the POS/KDS device apps are separate modules and are not covered by this census. EVIDENCE: SpotOn's own source says what a "concept" is, and it is an ORG, not a brand on a terminal. features/taxesFees/useMultilocation.ts defines exactly three shapes, with these comments: `/** One org, multiple merchant locations, multiple user locations */ const isSameConceptMultipleLocations = orgCount === 1 && merchantHasMultipleLocations && userHasMultipleLocations && isMultilocationEnabled`, `/** One org, multiple merchant locations, single user location */ const isSameConceptSingleLocation = ...`, and `const isMultiConcept = orgCount > 1 && userHasMultipleLocations && isMultilocationEnabled`. Multi-concept therefore means a user spanning SEVERAL ORGS, i.e. separate businesses in separate dashboards - the opposite of two brands sharing one terminal. The branding surface confirms it: features/businessInformation ships ONE BusinessLogo, ONE BusinessHeroImage and ONE ReceiptCustomization per location (a single PrintedReceiptLogo plus the single formik fields customReceiptHeader/customReceiptFooter), with no brand dimension. features/revenueCenters is a single free-text field (EXPRESS_REVENUE_CENTERS_INITIAL_VALUES = {expressMerchantInput:''} / RPOS_REVENUE_CENTERS_INITIAL_VALUES = {rposMerchantInput:''}), so it cannot separate per-brand revenue either. CONTROLS over the 482 sources, tokenised and case-insensitive: "virtual brand" 0, "multi-brand" 0; the 90 brand/concept hits are entirely the org-level concept helpers above plus design-token names. BOUND: the settings app is where per-location branding, receipts and revenue centers are configured, and it is held complete (116/116 chunks mapped); menu configuration lives in express-menu-web and is not covered, but a second menu alone cannot satisfy the receipts/branding and separately-reportable-revenue conjuncts, which this census shows are single-valued per location. Retrieved 2026-09-17. https://settings-web.spoton.com/assets/spoton-settings-web-BVYEUikC.js.map · retrieved 2026-09-17 adversarially verified

Tax configuration is per-location with support for multiple simultaneous tax rates, jurisdiction-specific rules (e.g. prepared-food vs grocery, inclusive vs exclusive tax), and per-location tax exemptions.

multi-location-multi-tax-jurisdiction

Tax is configured per location with multiple simultaneous rates and per-channel overrides: "Manage Taxes | Dashboard | SpotOn Express" plus a dedicated "To Go & Delivery Tax Overrides | SpotOn Express Dashboard" article, order-level exemption at the POS ("Make Tax Exempt — Removes all pre-programmed taxes from entire order"), and a documented rounding model ("For payment processing and tax rounding we utilize bankers rounding, also known as rounding to half even"). RPOS carries the same per-location tax settings under Locations, and DAVO is integrated for automated per-jurisdiction filing. https://help.spoton.com/space/SK/4605968412 · retrieved 2026-08-03

Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.

multi-location-central-labor-policy

Jurisdictional labour policy is configurable in Teamwork — "California Labor Settings" and "California Break Law Tracking & Control" are dedicated articles, and Express holds Overtime Settings and pay periods per location. Shortfall: no location-group scoping of labour policy is documented, and enforcement at the terminal is not described — the documented behaviour is tracking and reporting. https://help.spoton.com/space/SK/2239430825 · retrieved 2026-08-03

The POS software runs on commodity off-the-shelf hardware (standard iPads, Android tablets, or PCs) that the operator can buy from a third party, rather than only on vendor-supplied proprietary terminals. differentiator

hardware-commodity-devices

Some surfaces run on operator-owned hardware: "SpotOn Mobile makes it easy to accept tap, swipe, and cash payments from an iOS or Android mobile device", SpotOn Reserve's Host App runs on an iPad, and Fresh KDS runs on tablets the operator sources ("SpotOn does not supply bump bars for Fresh KDS"). Shortfall: the restaurant POS itself does not — Station 15, Station 10, the SpotOn Handheld, Serve (A920/A77) and the A800 are all vendor-supplied terminals, and no article documents installing the restaurant POS on a third-party tablet or PC. https://help.spoton.com/space/SK/1091043420 · retrieved 2026-08-03

Vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs.

hardware-os-platforms

Platforms are named in places: Serve is Android ("Yes, it's like an Android cell phone. Pull down the top bar menu and tap on the Wi-Fi icon"), SpotOn Mobile runs on "an iOS or Android mobile device", and the Reserve Host App is iPad-based. Shortfall: no article publishes minimum OS versions or device specifications for any client, and the client OS for Station 15/10 and the RPOS back office is never stated. https://help.spoton.com/space/SK/1194557666 · retrieved 2026-08-03

Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.

hardware-handheld-purpose-built

The handheld is purpose-built with an integrated reader: SpotOn Serve runs on the A920 or A77, taking orders, printing requisitions and accepting card payment on the device, with a separate SpotOn Handheld SKU published at $375 on the pricing page and a Multi Charger best-practices guide. Shortfall: no drop rating and no IP ingress rating are published for any SpotOn handheld. https://help.spoton.com/space/SK/1139474863 · retrieved 2026-08-03

The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator

hardware-handheld-battery-swap

The only rated battery life SpotOn publishes belongs to a discontinued device. The FAQ page carrying "Run time - 8 hours" and the measured "App open with max screen brightness for 8 hours = battery drop from 100% to 36%" opens by stating "SpotOn Serve is an EOL. We still offer support, but no new services are implemented." For current hardware there is no rating: the Express Handheld articles carry no battery section, the "SpotOn Handhelds" and "Handheld | SpotOn Express" pages render empty, and the A800 spec sheet gives only the cell - "Battery + Charging: 7.2 V / 2300 mAh" - with no run time. Shortfalls: no hot-swap or field-replaceable battery is documented for any SpotOn device (the fleet answer is a multi-charger cradle), and the published full-shift figure covers an end-of-life handheld rather than the one on the price list. https://help.spoton.com/space/SK/3176005634 · retrieved 2026-08-03 adversarially verified

Handhelds support cellular/LTE connectivity as a documented fallback when store Wi-Fi drops, either built into the device or via a vendor-supplied failover.

hardware-handheld-lte

"It's been confirmed that the Android device prioritizes Wi-Fi over cellular. It will automatically switch to cellular if the Wi-Fi connection is lost (assuming cellular is turned on)" — documented automatic cellular fallback on the Serve handheld. https://help.spoton.com/space/SK/1194557666 · retrieved 2026-08-03

Terminals continue to take orders, print to kitchen, and record cash sales with the internet down, and the vendor documents explicitly which functions degrade (card auth, loyalty lookup, refunds).

hardware-offline-mode

Offline is documented properly where it exists: Express POS and Kiosk offer Auto/On/Off modes where "orders and payments continue; data syncs once the internet connection is restored. Orders are still sent to the kitchen printer or KDS", and the A800 article enumerates exactly what degrades (PIN debit unavailable, reporting does not update, surcharging unsupported, final payment status delayed) with per-transaction, cumulative and duration caps. Shortfall: "Offline Mode is not available for RPOS devices" — the flagship table-service POS has no documented offline path, which contradicts the marketing page's "blackout-proof offline mode". https://help.spoton.com/space/SK/4073652945 · retrieved 2026-08-03

Sells or supports a dedicated kitchen display system with bump-bar or touch input, station routing, and course/fire timing, as a first-party product rather than an integration-only dependency.

hardware-kds

Express KDS is genuinely first-party: order cards with per-type header colours, In Progress and Completed states with completion timing, item and ticket bumping, a distinct Expo screen, multi-KDS bump propagation, Spanish language support at device level, and Express KDS Hardware documentation. Shortfall: SpotOn Restaurant (RPOS) has no first-party KDS — its kitchen screen is an integration, and the Kitchen Display System Integrations index lists Fresh KDS, ChefTab and QSR Automations as the options. https://help.spoton.com/space/SK/4341727233 · retrieved 2026-08-03

Offers a self-order kiosk running the same menu and modifier engine as the POS, in both countertop and freestanding form factors, with integrated payment and accessibility (ADA) compliance documented. differentiator

hardware-kiosk

The kiosk is a supported Express device class sharing the POS menu engine — categories are shown or hidden per "POS, Handheld, and Kiosk", offline mode is configured on "SpotOn Express POS and Kiosk devices", and tip screens are documented for kiosks. Shortfalls: no countertop-versus-freestanding form factors are described, no ADA or accessibility conformance is published, and RPOS kiosks come from the Bite Kiosk or Reddie Group partners rather than SpotOn. https://help.spoton.com/space/SK/3896770593 · retrieved 2026-08-03

Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, and speaker/headset integration, with a documented timer/speed-of-service measurement.

hardware-drive-thru

Reddie Group | SpotOn Integrations: Reddie digital menu boards sync with the SpotOn menu and are offered 'from countertop kiosks to full drive-thru setups'; SpotOn's own integration page lists 'Indoor and drive-thru display options ... digital drive-thru boards' in 43", 49" and 55" sizes with cloud remote management. Shortfalls: partner hardware sold and supported by Reddie, not SpotOn; no order confirmation display, no speaker/headset integration and no speed-of-service timer is documented. https://help.spoton.com/space/SK/4240539654 · retrieved 2026-09-03 adversarially verified

Works with standard ESC/POS thermal receipt and kitchen printers from more than one manufacturer (e.g. Epson and Star), including LAN/Ethernet printers, rather than only vendor-branded printers.

hardware-printer-compatibility

Third-party printers are documented by model: an Epson TM-L100 label printer has two dedicated setup articles (static IP assignment and disabling paper-removal standby), a "Worldpay Cash Drawer Hardware Guide & Setup" covers a non-SpotOn drawer, and RPOS printer configuration is generic (Printers & Kitchen Displays, requisition groups, conditional print routes). Shortfall: no published compatibility list of supported ESC/POS models or manufacturers exists, and network-printer support is implied by the static-IP guidance rather than stated. https://help.spoton.com/space/SK/5004329007 · retrieved 2026-08-03

Supports the standard peripheral set — cash drawers (including multi-drawer per terminal), barcode scanners, scales for by-weight items, and customer-facing displays — with a published compatibility list.

hardware-peripherals

The standard peripheral set is documented individually: cash drawers with per-user assignment ("Assign Cash Drawer | SpotOn Restaurant FOH", plus a Worldpay cash drawer hardware guide), a named barcode scanner with setup and reconfiguration articles (Honeywell Genesis 7580g), scales via price-embedded barcodes ("merchants can use a barcode scale to pre-label products. When the barcode is scanned, the POS identifies the item and applies the correct price automatically. Requirements: a compatible Honeywell scanner and a barcode scale that prints GS1-standard barcodes (UPC-A, UPC-B, or EAN-13)"), and a customer-facing display with its own connection and MSR-cover articles. https://help.spoton.com/space/SK/2161016852 · retrieved 2026-08-03

Card entry happens on a PCI-listed PTS device using validated point-to-point encryption, so the POS application and tablet stay out of PCI scope; the vendor states the merchant's SAQ type.

hardware-p2pe-terminal

Card entry is on payment terminals under a managed PCI programme, and SpotOn states "our solutions minimize your exposure to cardholder data, reducing the PCI DSS compliance scope", with SecureTrust by Viking Cloud guiding merchants "through the SAQ process, tailored to your specific business model and compliance level". Shortfall: no PCI-listed P2PE solution is named and SpotOn does not state which SAQ type its merchants qualify for — the merchant is routed to a third party to determine it. https://help.spoton.com/space/SK/4283203664 · retrieved 2026-08-03

Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. differentiator

hardware-tap-to-phone

The SpotOn Mobile card reader article: 'This product is deprecated ... we do not offer any swaps or replacements. Please consider a hardware upgrade if needed'; SpotOn Mobile acceptance on iOS/Android requires that Bluetooth reader (Activation | SpotOn Mobile). The pricing page's FAQ refuses customer-owned POS hardware or tablets, and the hardware page states SpotOn 'uses proprietary, secured, and closed-system hardware'. No commodity-device contactless acceptance without a reader is documented anywhere. https://help.spoton.com/space/SK/1169129688 · retrieved 2026-09-03 adversarially verified

Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator

hardware-pricing-transparency

Per-SKU list prices are published on the public pricing page: "Station 15: $995 $750/each", "Station 10: $550 $415", "Handheld: $500 $375/each", "Guest-facing display: $200", "Wireless router: $300". Shortfalls: this is the pricing page rather than documentation, KDS screens and kitchen printers are not priced anywhere, and implementation costs are acknowledged but not quantified. https://www.spoton.com/pricing/ · retrieved 2026-08-03 adversarially verified

Hardware can be purchased outright (owned) as an alternative to a mandatory lease or subscription-bundled rental, and the vendor states which. differentiator

hardware-ownership-vs-lease

Hardware is bought, not leased, and ownership vests on a stated timetable: the published POS terms provide that cancelling within one year of installation requires the customer to "pay SpotOn the difference between your initial purchase amount and the full List Price of all hardware purchased", and that after one year of installation the customer owns the equipment with no penalty. Purchase prices are published per SKU on the pricing page. https://www.spoton.com/legal/point-of-sale-terms/ · retrieved 2026-08-03 adversarially verified

Vendor documentation confirms whether hardware purchased from the vendor remains usable with other software after cancellation, i.e. it is not software-locked or remotely bricked. differentiator

hardware-usable-after-churn

SpotOn's own hardware page answers the question in its FAQ: 'Can I run my own software on SpotOn POS hardware? No. SpotOn uses proprietary, secured, and closed-system hardware designed specifically for our software.' The same page lists the Station 15 at $995 and the Station 10 at $550 as SpotOn's proprietary units. Combined with the POS terms already on the record (the customer owns the equipment after one year), the position is that the operator owns terminals that will run nothing but SpotOn. A statement that the hardware is closed by design is positive evidence that it is not usable with other software after cancellation, which is what the claim asks. https://www.spoton.com/hardware/ · retrieved 2026-09-02 adversarially verified

Publishes a hardware warranty term and a replacement/advance-exchange SLA with a stated turnaround (e.g. next-business-day depot swap). differentiator

hardware-rma-sla

The Limited SpotOn Restaurant System Warranty publishes a term - hardware 'will function, under normal use, in accordance with the documentation, for one (1) year from the SpotOn Restaurant systems shipment date' - and SpotOn bears transport both ways. Shortfall: no turnaround is stated at all; remedy is at SpotOn's election, 'either (1) repair or replace the SpotOn Restaurant system, or (2) refund fees', and replacements 'may be new or refurbished'. https://www.spoton.com/legal/point-of-sale-terms/ · retrieved 2026-09-05 adversarially verified

Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.

hardware-byod

A staff-facing app runs on personal devices: SpotOn Mobile "makes it easy to accept tap, swipe, and cash payments from an iOS or Android mobile device" using a paired Bluetooth reader, with its own activation flow. Shortfall: no permission or security model for personal devices is documented, and the restaurant POS ordering app is not offered on staff-owned hardware. https://help.spoton.com/space/SK/1091043420 · retrieved 2026-08-03

Provides a remote device-management console showing each terminal, printer, and KDS as online/offline, with remote reboot, software-version visibility, and staged rollout of updates. differentiator

hardware-remote-device-management

CLAIM: a remote device-management console showing each terminal, printer and KDS as online/offline, with remote reboot, software-version visibility and staged rollout of updates. VERDICT: partial/B. The capabilities exist in SpotOn's own fleet service, but the operator-facing console is not shown to have them all. NEW SURFACE 1 (found by a certificate-transparency listing via certspotter): https://device-management.spoton.com/openapi.json. It is an anonymous FastAPI OpenAPI 3.1 spec, served at 200 with 151,865 bytes (sha256 6b21f617...). The same spec is on device-management-staging.spoton.com, with Swagger UI at /docs. robots.txt returns 404. info: {"title":"device-management","description":"Device Management","version":"v2.106.0"}. EVIDENCE: "GET /api/v1/devices-by-location/{blid} Returns devices from given location."; DeviceType enum ["UNKNOWN","AX","POS","KDS","KIOSK","EXPRESS_POS",...,"PRINTER","GATEWAY","SWITCH","ACCESS_POINT","CELLULAR_BACKUP",...]; "POST /api/v1/devices/{device_serial_number}/reboot Reboots a device by serial number." (with the response "400 Device is offline and cannot be rebooted."); "POST /api/v1/devices/{device_serial_number}/os-update Triggers an OS update for a device if eligible."; the EloView device details hold "online_since", "offline_since" and "os_version"; the location wave is described as "Location-level (merchant-level) deployment wave" with enum ["general","early","late"], and PATCH /api/v1/locations/{blid}/wave "Updates the location-level deployment wave (early | general | late)"; POST /api/v1/fleet/reconcile "Sets the desired software configuration for the given wave_identifier", and a report feeds "the Device GitOps modal". So SpotOn runs staged (early/general/late) rollouts, device reboot, per-location device inventory and online/offline state. LIMITS: every one of these endpoints needs an "S2S Bearer Token" (service-to-service), and the tool that uses them (hub.spoton.com / supportal.spoton.com) sits behind Zscaler ZPA for employees only. Online/offline state is only on the EloView (Elo hardware) MDM record; no printer online field exists in the spec. NEW SURFACE 2, the merchant-side part: the anonymous Restaurant POS web clients. The back office is https://client.restaurantpos.spoton.com/b/boindex.js?v=1.312.1 (8,529,826 bytes) and the FOH is /p/posindex.js (11,217,314 bytes); /client-versions.json gives "foh.1.312.1". Their station edit panel shows "Eservice Version" (readonly) with a "See Latest Version" button. The printer panel warns "This Printer is offline and may be used by one or more Print Routings!" and has the setting "Show offline notifications after (seconds)". The payment-terminal table asks 'Do you want to reboot terminal "..."?. BroadPOS updates won't be upgraded if the batch is not empty.' Clients raise "POS Update Available" / "Critical update" banners. That is per-station version visibility, printer offline warnings and payment-terminal reboot in the merchant back office. No merchant page combines KDS online state with staged rollout. A yes would need the operator console itself documented. Retrieved 2026-09-16. https://device-management.spoton.com/openapi.json · retrieved 2026-09-16 adversarially verified

Integrates with specialty beverage hardware — self-pour tap walls, flow meters, or liquor pour spouts — such that pours post to a POS tab automatically.

hardware-selfpour-scales

Beverage hardware is integrated through named partners: BarTrack and Bevchek for draft monitoring, BeerSAVER, and BarVision for pour spouts that identify "over-pours, unrecorded pours, and loss points", all listed under Inventory Management Integrations with individual articles. Shortfall: these feed inventory and variance analysis; no article documents a pour posting automatically as a line onto an open POS tab, and no self-pour tap wall integration is listed. https://help.spoton.com/space/SK/2319024540 · retrieved 2026-08-03

Supports inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call.

hardware-callerid-integration

Caller ID is a built-in FOH surface with BOH configuration: "This section covers the configuration and management of stations and tables in SpotOn Restaurant's Back of House. Use the guides below to set up station types, customize command bars, design table layouts, manage table statuses, and configure caller ID settings for your restaurant." Caller ID is a Show Commands button ("Utilize Caller ID Screen"), a Command Bar button under Customer & Communication Tools, and a selectable POS Start Screen, alongside Customer Lookup with contact info, notes, address and order history. https://help.spoton.com/space/SK/2099314897 · retrieved 2026-08-03

Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.

extensibility-public-api-docs

SpotOn publishes an anonymous ReadMe developer hub at developers.spoton.com. Its 'Centralized API' project index (https://developers.spoton.com/central-api/llms.txt, 200, 8,540 bytes, re-fetched without credentials 2026-09-15) lists 8 guides and 38 API reference pages, each served as markdown with an embedded OpenAPI definition: e.g. 'Submit Order: Inject an order into the POS at a given location', 'Retrieve Orders: Retrieve a list of historical orders for a given location', 'Retrieve Time Punches', 'Manage Customer', 'Onboard Location', 'Webhooks'. The Retrieve Orders page gives the path /reporting/v1/locations/{location_id}/orders on https://api.spoton.com, its query parameters, response schema and Bearer auth. The introduction states Centralized APIs are 'the primary and only publicly available APIs for Express' and abstract both SpotOn Express and SpotOn Restaurant (RPOS). Met: endpoint-level reference readable with no login, NDA, agreement or sales call. Limits worth noting (not failing this claim): many labor and menu-item endpoints are marked 'EXPRESS ONLY'; separate 'Enterprise' and 'Restaurant' projects exist on the hub but their llms.txt return 404; obtaining credentials to call the API is a separate matter (see reporting-public-api). The prior note's basis, that developers.spoton.com 302s to a marketing intake form, is no longer true. https://developers.spoton.com/central-api/llms.txt · retrieved 2026-09-15 adversarially verified

API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator

extensibility-api-access-cost

VERDICT: still unknown. NEW SURFACE (320th): the PRODUCTION SpotOn merchant-dashboard micro-frontend import map, https://spoton-prod-import-map-public.s3.amazonaws.com/import-map.json (anonymous, 200, 10,900 bytes; linked from https://express-dashboard.spoton.com/runtime-config.js as REACT_APP_IMPORT_MAP_URL; express-dashboard.spoton.com robots.txt is "User-agent: * Disallow:", i.e. no bar). It names 38 dashboard modules. All were fetched anonymously with their statically referenced chunks: 1,234 JS files, 113.6 MB. Refused (403) and therefore NOT held: settings-web, virtual-terminal-web, virtual-terminal-legacy-web, invoices-web, partnerships-embedded, mbo-agent-web; restaurant-reporting-dashboard-frontend did not resolve. Because settings-web is refused, this is NOT a census of the dashboard and cannot carry a no. The integrations marketplace (partnerships-dashboard, 861 strings) states no API-access fee: "The Marketplace currently features integrations powered by SpotOn's Centralized API"; "We'll email you instructions to help you set up your {{name}} integration". The only fee string, "Cancel anytime with no fees. Prorated refunds", is a partner app's benefit copy (POISON). Its 861-string dictionary has 0 hits for "developer" and 0 for "api key". Retrieved 2026-09-16. || 323rd: 323rd, NEW EVIDENCE, still no published price. The developer doc index was re-derived today (central-api/llms.txt, 8,554 bytes, 49 URLs; reserve/llms.txt, 36 URLs) and contains no pricing, plan or fee page. What it does publish is a GATING PROCESS rather than a fee: "All integrations with SpotOn's API must be certified before launch and the start of the pilot period"; certification is a live demo call scenario by scenario; then "SpotOn requires a pilot phase with 5-10 merchants ... After all critical issues are addressed, your integration will be certified and ready to move to General Availability"; and "Partners with physical hardware will be required to send devices to a SpotOn lab for additional testing prior to receiving certification". Access is per merchant location, granted by the merchant (onboardingservice_onboardlocation) and revocable (offboardlocation). Whether SpotOn charges the merchant a per-location fee or plan upgrade for that access is published nowhere, so the cell stays unknown. Retrieved 2026-09-17. || 325th: 325th, NEW BOUND, still unknown: SpotOn publishes no price for API access on the merchant-facing side either. Over a full-body census of the vendor's KB, /\bAPI\b.{0,60}(fee|cost|charge|price|pricing)/ 0 pages and the reverse order 0 pages; /integration.{0,70}(fee|additional cost|monthly cost|no cost)/ 0 pages. The five (fee|cost)-near-integration hits are third-party partner blurbs (COGS-Well, DoorDash 'Cost Savings ... eliminates the need for aggregators', Restaurant Systems Pro) and archived Enterprise tax settings (POISON). The KB does price an adjacent embedded analytics feature - 'Is there any additional cost? No. The Kitchen Performance report is included at no additional cost for SPotOn clients using Fresh KDS' (5087166465) - which shows the KB WOULD say so when something is free, but that page is about a report, not API access. BOUND: the FIRST full-BODY census of help.spoton.com, taken from the publisher's own listing (Confluence v2 API https://help.spoton.com/api/v2/pages?limit=100&sort=-modified-date&body-format=storage, paged to fixpoint - rounds 29 and 30 returned 0 new pages): 2,145 pages WITH BODIES (1,083 current + 1,062 archived), 4,154,015 chars of tag-stripped text, version dates 2020-11-24..2026-09-17. Validation: 141 of the 142 help-centre page ids already cited in this record are inside the listing; the one absent (4456513592) now 404s on the API itself, so the KB is a census minus one deleted page. Prior passes held bodies for only the 121 most-recently-modified pages and titles for the rest. Controls are tokenised word-boundary case-insensitive over all 2,145 bodies; the denominator is 2,145. Retrieved 2026-09-17. || 327th: 327th, NEW SURFACE: the Centralized API documentation at 100% of its own llms.txt manifest (49/49 pages, 348,216 chars). It prices nothing: tokenised controls give cost 0, 'revenue share' 0, and the 7 'fee' hits are ALL the order schema's `v1Fee` object ('Name of the fee/surcharge', example 'Packaging') while the 8 'pricing' hits are all MENU pricing (day-part pricing, item price overrides) - POISON on both counts. What the census DOES establish is the shape of the gate, which is procedural rather than priced: access is per-location and vendor-granted ('API Consumers must have an API key ... access is granted on a per location basis', /restaurant/docs/api-access), and every integration must pass a Certification call and 'a pilot phase with 5-10 merchants', complying with 'the terms outlined in SpotOn's API agreement'. That API agreement is NOT published anywhere on developers.spoton.com, so whether it carries a per-location fee is still unstated by the vendor. Retrieved 2026-09-18. || 328th: 328th, NEW SURFACE - the merchant-facing SELLING surface, which no prior pass checked against this cell (the 327th bounded only developers.spoton.com). Two enumerations inside the 2,145-body Confluence census: (1) 'Add Services | SpotOn Merchant Dashboard | SpotOn Restaurant' (help.spoton.com/space/SK/1008762924, version of 2026-08-11) is the complete self-serve upsell catalogue a merchant can buy from the Dashboard, and it lists exactly five items - 'Website ... Loyalty ... SpotOn Restaurant / Online Ordering ... DoorDash ... SpotOn Reserve' - with no API, developer, data-export or integration SKU among them. (2) 'SpotOn Billing Invoices | SpotOn Merchant Dashboard' (/3535470600) enumerates the vendor's own invoice fee CATEGORIES - 'records of your implementation, software, and hardware fees plus any credits applied to your account' (processing fees being billed separately) - again with no data/API category. So SpotOn does not SELL API access as an add-on on either surface. WHY THAT IS STILL NOT A `yes`: neither statement says API access is included, and the developer corpus (held at 100% of its llms.txt in the 327th) describes a non-priced but real gate - access granted per location by the vendor, a Certification call, a 5-10 merchant pilot, and 'the terms outlined in SpotOn's API agreement', an agreement SpotOn does not publish. An absence from an upsell catalogue is consistent with either inclusion or a price living only in that unpublished agreement, so the cell is now bounded on both sides and still unresolved. Retrieved 2026-09-18. || 330th: MERGE HOLD (proposed partial/B, held unknown): The 329th rule, applied in both directions: an API-cost verdict needs a STATED fee, plan gate, or stated inclusion. The Point-of-Sale Terms fee schedule is silent on API access and the API agreement that grants it per location is unpublished, so silence in the schedule does not price it. Keep the fee-schedule reading as the bound. PROPOSAL AS WRITTEN: 330th, NEW SURFACE - the vendor's own PUBLISHED Point-of-Sale Terms (https://www.spoton.com/legal/point-of-sale-terms/, fetched 2026-09-18, 14,718 chars of stripped text), which no prior pass on this cell had read (the 327th bounded developers.spoton.com, the 328th the Dashboard 'Add Services' catalogue and the invoice fee categories). It is SpotOn's complete standard fee schedule for SpotOn Restaurant and it enumerates every recurring and one-off charge: a '$400' refundable deposit on approval, hardware, 'your implementation fee, shipping & handling costs and sales taxes', then 'The monthly POS service fee includes software licensing fee, software updates and 24/7 technical support', a '$995 conversion fee' (and doubled software licence) if you move payment processing elsewhere, and a '$15 per additional gigabyte' LTE overage. There is no API fee, no data-access fee, no per-integration fee and no tier in that schedule. The same document states the configured system ships 'with as many users and software integrations as you need', and 'we will continue to provide unlimited 24/7 phone support at no cost'. Corroboration on the merchant surface: the Reserve API key is self-serve inside the merchant's own portal with no purchase step ('Settings -> API -> API Key ... This section contains: API Key, SDK setup examples ... Restaurant ID', help.spoton.com/space/SK/5050302466), and the Dashboard's complete 'Add Services' upsell catalogue (5 items) has no API SKU. WHY PARTIAL AND NOT YES: no SpotOn document states that API access is included at no additional cost. The published fee schedule rules out a surcharge or an upgraded plan as a PUBLISHED price, but developers.spoton.com still says 'access is granted on a per location basis' under 'the terms outlined in SpotOn's API agreement', an agreement SpotOn does not publish, so a per-location API charge living in that agreement cannot be excluded. Per the API-cost merge rule (a `no`/`yes` needs a STATED fee or a stated 'no additional cost') this is proposed as partial, not yes. Retrieved 2026-09-18. adversarially verified

A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator

extensibility-free-sandbox

327th: the 325th's remaining blocker is now EXTINGUISHED and the cell can be published. That blocker was a ReadMe `environment` variable defaulting to an appetize-dev sandbox hostname. NEW SURFACE: the Centralized API documentation fetched to 100% of the PUBLISHER'S OWN MANIFEST - https://developers.spoton.com/central-api/llms.txt lists 49 .md pages (8 guides + 41 reference pages) and all 49 were fetched anonymously at 200 (348,216 chars of markdown, .cache/q327/spoton/cdocs/). Every OpenAPI definition embedded in those pages declares exactly ONE server: the string "url": "https://api.spoton.com" occurs 39 times and NO other server url occurs at all. There is no sandbox host in the published reference. CONTROLS over the 49-page census, tokenised, word-boundary, case-insensitive: sandbox 0, 'test environment' 0, staging 0, demo 0, 'developer account' 0, seeded 0, 'test data' 0, 'test merchant' 0. POSITIVE CONTRARY EVIDENCE: the published Certification Process says how a partner is actually expected to test - 'All integrations with SpotOn's API must be certified before launch and the start of the pilot period ... our team will request that you demonstrate a series of scenarios' and 'Once your integration is certified, SpotOn requires a pilot phase with 5-10 merchants to ensure the integration's quality.' i.e. validation happens against live merchants under SpotOn supervision, not in a self-serve sandbox. POISON NAMED: 'sandbox' scores 3 hits in the dashboard JS and all 3 are junk - React DOM's attribute table (`sandbox:un` next to `scope`, `scoped`, `seamless`) and a Storybook link (spoton-lib.netlify.app/?path=/docs/components-toast--sandbox). Retrieved 2026-09-18. https://developers.spoton.com/central-api/docs/certification-process · retrieved 2026-09-18 adversarially verified

Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).

extensibility-oauth-partner-apps

SpotOn's partner API (the Centralized API, developers.spoton.com/central-api, retrieved 2026-09-15; the guide page is dated updatedAt 2026-06-05) authenticates third-party apps with OAuth 2.0. The operator grants access per location through 'Sign In With SpotOn', and each location's grant can be revoked. The permissions are scoped, but the operator cannot choose which scopes to grant, and the only documented way to revoke is an API call inside the partner's own integration. MET: OAuth 2.0 ('The integration uses a standard OAuth2 flow with two distinct token types': authorization_code user tokens with a 1-hour expiration period, and client_credentials service tokens with a 24-hour expiration period; 'GET https://api.spoton.com/oauth2/v1/authorize'). MET: named scopes, eleven listed, e.g. 'business:all:read', 'menu:all:read', 'order:submit:write', 'reporting:orders:read', 'labor:all:read'. MET: operator-granted ('Your application cannot access any SpotOn location that has not granted access to your application through Sign In With SpotOn.'; the intro page lists 'SpotOn OAuth * Merchant Self-serve Partner Authorization'). MET: revocable per location and per partner. The Partnerships Onboarding API v1 Offboard Location endpoint (POST /onboarding/v1/location-offboard, https://developers.spoton.com/central-api/reference/onboardingservice_offboardlocation.md) says 'Provide the merchant's Business Location ID to revoke a third-party integration's API access. This endpoint supports both User Authorization tokens and Client Credential tokens for authentication.' SHORTFALL 1, the operator cannot choose scopes. SpotOn assigns the scope set ('a subset of these scopes will be assigned to your application'), the partner must request 'all scopes SpotOn has granted your client', and 'the user will be required to consent to all scopes assigned to your partner application'. The operator's only choices are to accept every scope or to refuse the app. SHORTFALL 2, revocation is not in the operator's own hands. Both token types that the offboard endpoint accepts are issued to the partner's client_id/client_secret, so the call is made through the partner's integration. No merchant-side disconnect screen in the SpotOn dashboard is documented, and 'revoke' appears nowhere else on the fetched hub pages. SHORTFALL 3, access is gated. Client ID and Client Secret must be requested from SpotOn ('request the following credentials from SpotOn'), and refresh tokens are not provided. SCOPE OF THIS VERDICT: it covers the Centralized API only. SpotOn's separate reservations-only Reserve API (legacy SeatNinja, developers.spoton.com/reserve) uses static x-api-key keys, and the auth model of the Gen 1 RPOS APIs is not published. POISON, not cited: the Submit Order OpenAPI securitySchemes entry is typed 'apiKey' but is described as 'Authentication token, prefixed by Bearer: Bearer <token>', which is the OAuth bearer token in a header, not a static key. The ReadMe HTML-shell 'oauth' flags are docs-product config. https://developers.spoton.com/central-api/docs/spoton-oauth-integration-guide.md · retrieved 2026-09-15 adversarially verified

The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.

extensibility-webhooks-push

SpotOn publishes a push-webhook OpenAPI definition, 'Webhook Event v1', in its Centralized API ReadMe hub (https://developers.spoton.com/central-api/reference/webhookevent_delivery-1.md, 44,180 bytes, sha256 1a91afb1957036c05cef923d51c2272bde63d6c223f7e8870fb053155ef3d3a0, retrieved 2026-09-15). The spec defines a single POST delivery to the partner's endpoint, so this is real-time push rather than polling. For orders, though, only two event types exist. SHORTFALL: no order created, modified, paid, voided or refunded event is defined. Of the claim's five lifecycle events, only a cancel (at best a void analogue, and not stated as one) and a fulfillment-status update are pushed. QUOTES info.description 'The Webhook Event provides standardised way of informing third party integrations about events to orders and menu updates for relevant locations.'; enum v1EventEventCategory = [EVENT_CATEGORY_MENU, EVENT_CATEGORY_ITEM, EVENT_CATEGORY_MODIFIER, EVENT_CATEGORY_ORDER, EVENT_CATEGORY_LOCATION_CONNECTION, EVENT_CATEGORY_LABOR_TIME_PUNCH, EVENT_CATEGORY_FOH]; enum v1OrderEventType = [EVENT_TYPE_CANCELED, EVENT_TYPE_ORDER_FULFILLMENT_UPDATE]. The v1Event envelope carries id, timestamp, category, location_id and details. The intro page (https://developers.spoton.com/central-api/docs/getting-started.md) lists webhooks as 'Menu Updates * Item Availability * Order Cancelation'. The Orders Overview (https://developers.spoton.com/central-api/docs/create-order.md) says submitted orders move to ACCEPTED and 'An ACCEPTED order can then be CANCELED either by the merchant on the POS, or by the API consumer who submitted the order. These are currently the only two statuses for an order'. CREATED events exist only for non-order categories: v1MenuEventType [CREATED, UPDATED, DELETED, ACTIVATED, DEACTIVATED], v1ItemEventType [CREATED, UPDATED, DELETED, AVAILABILITY_UPDATED] and v1LaborTimePunchEventType [CREATED, UPDATED, DELETED]. v1ModifierEventType is [UPDATED, AVAILABILITY_UPDATED], and v1LocationConnectionEventType covers connection states only. CONTROLS/POISON The enums were parsed from the spec as JSON, not matched by substring. The token EVENT_TYPE_CREATED appears 9 times, all of them inside the menu, item and labor enums, so none is an order event. EVENT_TYPE_PAID, VOIDED and REFUNDED each have 0 hits. The only 'PAID' strings are the labor enum LaborTimePunchBreakType [BREAK_TYPE_UNPAID, BREAK_TYPE_PAID]. 'void' and 'refund' have 0 hits. The FOH category's v1FOHReservationTicket payload ('POS ticket data associated with a partner reservation') has opened_at, updated_at, closed_at and payments fields, but it has no type field and no FOH event-type enum. It is also scoped to partner reservations, so it does not establish ticket created or paid pushes. ReadMe '"webhookEnabled":false' flags in the HTML shell are docs-platform config and are not cited. CAVEATS The documented order events concern orders submitted through the Order API; whether POS-originated orders emit any event is not documented. Subscriptions and their signing key are created by SpotOn ('shared-key generated on subscription creation'), and no self-serve subscription endpoint appears among the llms.txt reference entries. https://developers.spoton.com/central-api/reference/webhookevent_delivery-1.md · retrieved 2026-09-15 adversarially verified

Webhooks are cryptographically signed (e.g. HMAC) AND documented to retry with backoff, with a replayable event log for missed deliveries. differentiator

extensibility-webhook-reliability

SpotOn's Webhook Event v1 OpenAPI definition (Centralized API, developers.spoton.com, page updatedAt 2026-06-10, retrieved 2026-09-15) documents HMAC signing and a retry rule. It does not document backoff or a replayable event log. The spec describes the POST that SpotOn makes to the partner's endpoint (operationId 'WebhookEvent_Delivery', request body v1Event), so its response codes describe SpotOn's delivery behaviour, not partner calls to SpotOn. MET, signing: header 'x-spoton-webhook-signature', 'Payload signature using the shared-key generated on subscription creation.' Header 'x-spoton-webhook-signature-version': 'Currently only `v1` is supported. The v1 signature standard is a SHA265 HMAC of the request body in its entirety using the shared-key generated when the subscription is created as the secret. The key as shared by SpoOn is Base64-encoded and will need to be decoded before use.' The typos 'SHA265' (i.e. HMAC-SHA256) and 'SpoOn' are the vendor's own. PARTLY MET, retry: '400': 'Bad request. Delivery will not be retried.' and '500': 'There was an error processing the request. Delivery will be retried.' SHORTFALLS: (1) No backoff schedule, retry count, interval or give-up rule is published, and the spec does not say how timeouts or other non-500 failures are handled. (2) No replayable event log or redelivery endpoint exists. llms.txt lists a single webhook entry (this spec) and no events-list or redelivery reference. v1Event does carry a required 'id' ('Unique id of the event'), but de-duplication is not stated. (3) Both signature headers are declared '"required": false', so the spec does not guarantee that every delivery is signed. The only 'retry and backoff' wording on the hub is in docs/rate-limiting.md ('SpotOn recommends that you implement retry and backoff logic'). That page advises partners about 429 responses to their own API calls, so it is not evidence of webhook backoff. Subscriptions and their shared keys are created by SpotOn for certified partners. https://developers.spoton.com/central-api/reference/webhookevent_delivery-1.md · retrieved 2026-09-15 adversarially verified

A public write API accepts externally originated orders into the POS as first-class tickets that fire to KDS/printers and land in reporting.

extensibility-order-injection-api

SpotOn publishes an order-injection write API, but it accepts only fully paid, closed orders. Its anonymous Centralized API developer hub (developers.spoton.com/central-api, retrieved 2026-09-15) documents it. Submit Order is POST /order/v1/locations/{location_id}/orders on api.spoton.com, and its OpenAPI summary reads 'Inject an order into the POS at a given location.' The Orders Overview (create-order.md) says: 'The SpotOn Order API allows the injection of fully paid orders into the POS.' There are two flows, 'Propose then Submit' and 'Submit without Propose'. MET, the order becomes a real ticket that reaches the kitchen: 'An Order must be one of three fulfillment types: Dine-in, Pickup, or Delivery. This affects its printer/KDS routing and lead time estimation.' MET, the order lands in reporting: 'The Order Source Name string will appear on receipts, KDS, and as a filter attribute in sales reporting'. The Submit spec's display_id is 'visible to merchants and customers on the POS tablet, sales reports, KDS, and printed receipts'. A submitted EXTERNAL payment's provider_name becomes 'the name of the custom tender and in a merchants reporting'. The introduction says Centralized APIs let a partner build 'a single integration that works for all SpotOn merchants' across Express and Restaurant (RPOS). SHORTFALL 1, paid closed orders only: 'Currently only fully paid CLOSED orders can be handled by the /submit endpoint. Trying to /submit orders with a state of DRAFT or OPEN will result in an error.' The overview also says 'It is required that you attach a payment to the order that matches the total.' An external system therefore cannot open an unpaid ticket, such as pay-at-pickup or a tab. The Submit spec's state field describes 'open, draft, closed', but the guide's footnote overrides it. SHORTFALL 2, paying by card on SpotOn's own rails needs 'a card transaction id received from our payments API (currently private)'. Otherwise the payment is recorded as an EXTERNAL tender. SHORTFALL 3, access is gated: 'All integrations with SpotOn's API must be certified before launch', followed by a mandatory 'pilot phase with 5-10 merchants'. Credentials must be requested from SpotOn (OAuth guide). Once submitted, an order's only statuses are ACCEPTED and CANCELED. The earlier note called the interface 'entirely undocumented publicly'. That is no longer true: the request and response contract is published. https://developers.spoton.com/central-api/docs/create-order.md · retrieved 2026-09-15 adversarially verified

Menu items, modifiers, and prices can be written and updated via API, not just read. differentiator

extensibility-menu-write-api

Programmatic menu movement in both directions is evidenced through partners: SpotOn publishes menus outbound to DoorDash and Uber Eats in real time, and Reddie Group's digital signage integration states "Menu Syncing — Programmatic updates ensure that any changes made in SpotOn are reflected instantly on digital menu boards and kiosks." Shortfall: every documented flow is read/publish outward from the SpotOn menu; no inbound menu write API is documented, and no schema exists publicly for either direction. https://help.spoton.com/space/SK/4240539654 · retrieved 2026-08-03

The vendor is a named DoorDash Preferred Integration Partner (DPIP) under the 2026 program requirements. differentiator

extensibility-doordash-preferred

DoorDash publishes its own complete provider registry at https://merchants.doordash.com/api/partner-integrations — 64 providers, each carrying a `qualityStatus` of PREFERRED (12), CERTIFIED (47) or AT_RISK_OF_SUSPENSION (5), plus a features-completed count against the eight high-quality features the program requires. It is served anonymously and merchants.doordash.com/robots.txt permits it (Allow: / with only /cdn-cgi/ and /monitoring barred). This is the instrument the program page points to when it says the roster is tracked in real time, and it supersedes the 2026 announcement post most of this corpus cited — that post introduces its ten names with the word `include`, which makes it a floor, not a ceiling. In that registry this vendor is the entry `spoton_production`, rendered as 'SpotOn', with qualityStatus CERTIFIED and 6 of the 8 high-quality features built. CERTIFIED and AT_RISK are the program's other two tiers, so this is positive evidence of non-membership rather than a failure to find the vendor: it is present in the registry and carries a status that is not PREFERRED. GRADE HARMONISED TO B, 2026-09-11: this URL was first written at grade A. The adversarial pass ruled E on the principle that the rubric grades by the publisher's relationship to the SCORED vendor, and DoorDash is not that vendor. B is the settlement, for two reasons that are not preference: 39 rows already graded a DoorDash-published document B on this claim before today, and one URL on one claim cannot carry two grades; and E is unworkable, because nine of the 47 rows are `yes` on a differentiator-weight claim, which the grade floor refuses below B. B reads as the product documentation of the programme's own publisher, which is what this registry is. The dissent is recorded in verification.jsonl. https://merchants.doordash.com/api/partner-integrations · retrieved 2026-09-11

Direct, first-party certified integrations exist with DoorDash, Uber Eats, and Grubhub without requiring a paid middleware layer (Otter/Chowly/Deliverect/Checkmate). differentiator

extensibility-first-party-delivery-integrations

DoorDash and Uber Eats both have direct, first-party SpotOn integrations covering menu sync and order injection with no middleware layer, documented individually and working across both RPOS and Express. Shortfall: Grubhub has no direct integration article — it is reachable only through Chowly, Deliverect or Checkmate, all of which are separately contracted paid layers. https://help.spoton.com/space/SK/4629856267 · retrieved 2026-08-03

The POS is a supported endpoint for at least two major aggregation middleware platforms (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate).

extensibility-middleware-compatibility

The Online Ordering Integrations index enumerates the aggregation layer explicitly: "It includes integrations across key third-party ordering platforms and marketplaces, with partners such as DoorDash, Uber Eats, Chowly, Deliverect, Incentivio, and Order with Google." Checkmate has its own article plus a "Checkmate Partners Compatibility" page, and Chowly and Deliverect each have dedicated setup articles — four of the five named middleware platforms are supported endpoints. https://help.spoton.com/space/SK/2319286787 · retrieved 2026-08-03

Native, vendor-maintained connectors exist for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export.

extensibility-accounting-connectors

The Accounting Integrations index lists vendor-maintained connectors with individual articles: QuickBooks, Restaurant365, BackOffice (formerly RASI), Restaurant Systems Pro, Shogo and DAVO for sales-tax withholding and filing. A first-party "QuickBooks Export" report also ships in the RPOS reporting set, so the QuickBooks path is journal-mapped rather than raw CSV. https://help.spoton.com/space/SK/2293072079 · retrieved 2026-08-03

Labor hours export natively to at least two named payroll providers (e.g. Gusto, ADP, Paychex, Paylocity) without manual re-keying.

extensibility-payroll-export

Named payroll destinations with their own articles: "ADP Formatted Export | SpotOn Restaurant Integrations" and "Paycor (Export) | SpotOn Restaurant Integrations", plus 7shifts and HotSchedules for scheduling and TipHaus and GratShare for tip distribution, all fed from POS labour hours. https://help.spoton.com/space/SK/2320269514 · retrieved 2026-08-03

The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.

extensibility-app-marketplace

A public, browsable integration catalogue exists: SpotOn Integrations is organised into Accounting, Food Delivery, Inventory Management, Kitchen Display System, Online Ordering, Payroll/Tip/Scheduling, Reporting and Reservation categories, each with per-partner articles — roughly forty named third-party products, all readable without a login. Shortfall: it is documentation, not a marketplace — there is no self-install, no operator-granted authorisation flow, and nothing an operator can enable without contacting SpotOn or the partner. https://help.spoton.com/space/SK/2292285666 · retrieved 2026-08-03

The vendor supports a headless/embedded mode where a third-party UI (kiosk, web ordering, drive-thru) drives the POS transaction engine via API.

extensibility-headless-embedded

SpotOn's public Centralized API developer docs let a third-party ordering UI use the POS as its pricing and tax engine, not just drop orders into it. The API offers 'Menus READ' and 'Order WRITE' under Online Ordering, and says it works across both Express and Restaurant (RPOS) ('a single integration that works for all SpotOn merchants'). The Orders Overview says: 'If you want to use SpotOn to calculate your cart taxes and discounts, and validate item availability and pricing against a menu, you can Propose then Submit.' It also says 'Order proposal is currently a strict validation, which means that it will validate pricing, availability, and taxes against the menu_id provided.' Submitted orders then go through the POS: 'An Order must be one of three fulfillment types: Dine-in, Pickup, or Delivery. This affects its printer/KDS routing', and 'The Order Source Name string will appear on receipts, KDS, and as a filter attribute in sales reporting.' Shortfalls: (1) the engine only takes finished orders. 'The SpotOn Order API allows the injection of fully paid orders into the POS', and 'Currently only fully paid CLOSED orders can be handled by the /submit endpoint. Trying to /submit orders with a state of DRAFT or OPEN will result in an error.' So a third-party UI cannot open, hold or add to an unpaid check. (2) To pay by card on SpotOn's own payment system, 'you submit a card transaction id received from our payments API (currently private)'. Without that, the UI takes payment elsewhere and records it as an EXTERNAL tender. (3) Access requires an approval process: 'All integrations with SpotOn's API must be certified before launch', followed by a 'pilot phase with 5-10 merchants'. (4) The only order statuses are ACCEPTED and CANCELED. SpotOn's docs never use the words 'headless' or 'embedded' (0 hits across the Orders Overview, Submit Order and Propose Order pages), so this verdict rests on how the API works, not on vendor wording. The docs do not say whether Bite Kiosk or Reddie use this API. https://developers.spoton.com/central-api/docs/create-order.md · retrieved 2026-09-15 adversarially verified

A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator

extensibility-data-portability-exit

The published Merchant Terms decline to commit to it: on termination the client must request its data and "SpotOn makes no representations or warranties about its ability to return information", while SpotOn separately "reserves the right to access, retain, aggregate, process and share with third parties... all data available to SpotOn as a result of its performance of the Services". No machine-readable export format is documented, and there is no API to pull the history through. https://www.spoton.com/legal/merchant-terms/ · retrieved 2026-08-03

Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.

reliability-offline-order-entry

On SpotOn Express and Kiosk, order entry survives an outage and the vendor documents it: "Orders and payments continue; data syncs once the internet connection is restored. Orders are still sent to the kitchen printer or KDS", with Auto mode entering and leaving offline automatically. Shortfall: the same article states "Offline Mode is not available for RPOS devices". SpotOn Restaurant — the table-service flagship the pricing page sells — has no documented offline order-entry behaviour, while the marketing page claims offline mode "keeps all stations and devices connected and orders firing to the kitchen". The documentation and the marketing disagree and the documentation is the better source. https://help.spoton.com/space/SK/4073652945 · retrieved 2026-08-03

Card payments can be accepted while offline via store-and-forward, not just cash-only fallback. differentiator

reliability-offline-card-auth

Store-and-forward is documented on the A800 terminal in full — payments stored on device, sent automatically on reconnect, with per-transaction, cumulative and maximum-offline-duration caps — and Express carries the same offline mode for POS and Kiosk. Shortfall: not available on RPOS devices, and the same article warns that "if the terminal powers off before reconnecting, stored offline payments cannot be recovered." https://help.spoton.com/space/SK/4658331708 · retrieved 2026-08-03 adversarially verified

The vendor publicly documents who bears the loss when a store-and-forward transaction declines after connectivity returns, and states any per-transaction or cumulative offline cap. differentiator

reliability-offline-decline-liability

Liability is stated unambiguously and the caps are published. "Funds are not guaranteed, as payments are not processed until the device reconnects"; "offline payments may still be declined later when they are processed online"; "Will I get paid for offline payments? Yes. As long as the terminal reconnects and the payments are successfully processed... Payments are not guaranteed until they are submitted online." The SpotOn Lite settings article puts it bluntly: "You are fully liable for failed captures, chargebacks, and disputes of offline payments." Caps are enumerated as maximum per transaction, maximum total accepted offline, and maximum time offline. https://help.spoton.com/space/SK/4658331708 · retrieved 2026-08-03 adversarially verified

Multiple terminals continue to share a single check/table state over the local network while the internet is down (LAN-only degraded operation, not per-terminal islands). differentiator

reliability-lan-degraded-multi-terminal

SpotOn's offline-mode guide describes multi-device operation during an internet outage: 'All stations, terminals, and handheld devices stay connected to each other via your local network. You can even start an order on one device and pick it up from another device - POS station, handheld, both work. Orders keep firing to your kitchen display system and receipt printer', and lists 'Keeping all devices and stations connected to each other via local network' among the functions that remain available, citing a stress test 'with 15,000 guests and 100 POS devices'. Shortfall: this is a marketing guide, not the knowledge base - the A800 offline article documents per-device behaviour only - it does not say which product line (SpotOn Restaurant or Express) it describes, and it does not state how table state or a check open on two devices is reconciled. https://www.spoton.com/blog/pos-offline-mode/ · retrieved 2026-09-02 adversarially verified

The vendor documents a local/on-premise transaction engine or edge server (not purely cloud-hosted request/response) for the ordering path. differentiator

reliability-local-transaction-engine

Configuring Offline Mode | SpotOn Express: with Auto offline mode the POS or kiosk 'continues functioning during internet disruptions', 'orders are still sent to the kitchen printer or KDS', and orders and payments sync on reconnect; Offline Mode with Fresh KDS states that on 'the local SpotOn provided network' orders sent from the POS still reach the KDS without an ISP connection. Shortfalls: no named local server, edge appliance or store controller is documented - the ordering path is device-local store-and-forward over the SpotOn-provided LAN; the same article states 'Offline Mode is not available for RPOS devices'. https://help.spoton.com/space/SK/4073652945 · retrieved 2026-09-03 adversarially verified

Kitchen display and/or kitchen printer routing continues to function while offline.

reliability-offline-kds-printing

Documented for Express: "Fresh KDS for Express supports partial offline mode functionality. When a Fresh KDS is connected to the local SpotOn provided network, but the local network doesn't have an active internet (ISP) connection, orders sent from the POS will still show up on Fresh KDS", and the Express offline article confirms tickets still reach "the kitchen printer or KDS". Shortfalls: screen-to-screen bumping requires internet, new KDS logins fail offline, and no equivalent behaviour is documented for RPOS. https://help.spoton.com/space/SK/5085823000 · retrieved 2026-08-03

The system automatically fails over to a backup printer or KDS station when a configured kitchen printer is unreachable, and alerts staff.

reliability-printer-fallback

RPOS Failover Print Routing: an alternate printer route 'will automatically print should the default printer fail', with an ordered failover printer list per location and an Enable Printer Failover / Print Failover Plan setting on the printer. Shortfalls: no staff alert when failover occurs; failover targets are printers, not KDS stations; Express print routing documents no failover. https://help.spoton.com/space/SK/762314779 · retrieved 2026-09-03 adversarially verified

The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).

reliability-sync-conflict-handling

CLAIM: the vendor DOCUMENTS its conflict-resolution behaviour for edits made on two devices during a network partition (last-write-wins, merge, or operator prompt). VERDICT: no (moved from unknown) - the claim asks for published documentation and a census of the publisher's own KB shows there is none. CONTROLS: 'conflict' hits 17 of 2,145 pages and every one is POISON - conflicting DNS records when connecting a domain (1874526761, 4051861567), 'conflicting Special Hours' in Reserve (1679492071), 'Duplicate swipe codes may create conflicts' for manager cards (5197037595), 'account conflicts' from a duplicate employee email (5192941586), 'multiple categories with conflicting tax settings' (4605968412). 'last write', 'wins', 'merge conflict' and 'overwrite' produce no sync rule either. What SpotOn does publish is the SHAPE of the gap: '86 Menu Items and Modifiers | SpotOn Express (FOH)' (5591007235, version 2026-09-17) still says only 'Devices must be online for 86ing updates to sync', and 'Configuring Offline Mode' (4073652945, version 2026-05-21) enumerates what survives a partition - 'Orders and payments are processed normally and automatically synced once the device reconnects', 'Orders are still sent to the kitchen printer or KDS', 'Devices should only be placed in Offline mode in emergencies - keeping devices in offline mode for an extended period of time can result in loss of transactions and funding' - and never states which edit wins. BOUND: the FIRST full-BODY census of help.spoton.com, taken from the publisher's own listing (Confluence v2 API https://help.spoton.com/api/v2/pages?limit=100&sort=-modified-date&body-format=storage, paged to fixpoint - rounds 29 and 30 returned 0 new pages): 2,145 pages WITH BODIES (1,083 current + 1,062 archived), 4,154,015 chars of tag-stripped text, version dates 2020-11-24..2026-09-17. Validation: 141 of the 142 help-centre page ids already cited in this record are inside the listing; the one absent (4456513592) now 404s on the API itself, so the KB is a census minus one deleted page. Prior passes held bodies for only the 121 most-recently-modified pages and titles for the rest. Controls are tokenised word-boundary case-insensitive over all 2,145 bodies; the denominator is 2,145. Retrieved 2026-09-17. https://help.spoton.com/space/SK/5591007235 · retrieved 2026-09-17 adversarially verified

The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).

reliability-offline-feature-matrix

SpotOn publishes an explicit degradation list rather than a marketing claim. "Features Not Available Offline... PIN Debit is not available. The card MUST be processed as a credit. Reporting does not update. Surcharging is not supported. Final payment status is delayed." It also lists what not to do while offline (power off the terminal, let the battery die, close the app) and warns that stored payments are unrecoverable if the device powers down. Fresh KDS carries a second matrix — new logins, online order receipt, screen-to-screen bumping, SMS updates and real-time analytics are all enumerated as offline-unavailable. https://help.spoton.com/space/SK/4658331708 · retrieved 2026-08-03 adversarially verified

A public, per-component status page exists showing current and historical incident state without a login.

reliability-public-status-page

status.spoton.com is public and requires no login. It publishes per-component state across Core Services (POS, Retail, Online Ordering, Reporting, Dashboards), Payments (TSYS and Worldpay), Support, additional products (Loyalty, Reserve, Kiosk, Teamwork, KDS, Serve, Virtual Terminal) and 30+ named integrations, with "uptime over the past 90 days" published per component — most reading 100.0% or 99.99% — plus a historical uptime view. Publishing rolling uptime percentages per component is better disclosure than most of this peer group manages. https://status.spoton.com/ · retrieved 2026-08-03

24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.

reliability-247-live-support

The public pricing page states "24/7 support included" at no extra charge on every plan, and the knowledge base publishes a live support number, (877) 814-4102, as the escalation path in articles across the product set (Express offline mode, KDS prep-time alerts, Retail fee configuration). https://www.spoton.com/pricing/ · retrieved 2026-08-03 adversarially verified

The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator

reliability-onsite-install

Installer is a distinct first-party field role with its own documented implementation workflow. The knowledge base’s "Installer & Onboarding Specialist Referral Talk Tracks" is written for installers working "the Implementation environment", gated on an "Implementation Triage Slack channel" with green/yellow/red per-merchant status, and scripts the installer’s own words after a "Successful Install": "I’m really glad everything went smoothly today!", with instructions to hold off where "the install or training faced delays or quality issues". A separate article, "Booking a Virtual Site Survey (VSS)", documents the pre-install site-readiness step and marks it explicitly as the remote option - "a remote assessment conducted via video call to evaluate a site’s readiness". The pricing FAQ confirms it is billed: "Implementation costs go toward your custom menu build, installation, and personalized training for your team." PROVENANCE NOTED 2026-08-10: the cited URL is served under /space/SK/ (the public knowledge base, space 944898303) but the Confluence API reports the page lives in space 4015718532, "CX: PMO Shared Services" — an internal enablement space. The space segment is not validated against membership, so the page resolves under SK while its own space key 404s. The document is publicly readable first-party vendor material either way, so the grade is unchanged; it is recorded because the URL alone does not reveal that this is sales-enablement rather than product documentation. https://help.spoton.com/space/SK/4456513592 · retrieved 2026-08-03 adversarially verified

The vendor performs the initial menu build as part of onboarding rather than leaving it entirely to the operator. differentiator

reliability-menu-build-service

Login | SpotOn Restaurant BOH: before install day the operator may add employees, but 'Full Back of House access - including printer/KDS setup, stations, and advanced configurations - is locked until the SpotOn installer unlocks it on install day. The installer completes the remaining setup during installation.' The Change of Ownership article treats 'whether a new menu build is required' as an item SpotOn's team scopes for a new owner. Shortfalls: no page commits SpotOn to building the initial menu as part of onboarding or says whether it is charged; the knowledge base teaches the operator to build it, and Express offers an AI Menu Editor instead. https://help.spoton.com/space/SK/516686416 · retrieved 2026-09-03 adversarially verified

A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.

reliability-hardware-replacement-sla

A replacement program is included with the one-year system warranty and costs nothing to invoke: SpotOn 'shall either (1) repair or replace the SpotOn Restaurant system, or (2) refund fees', and transport costs both to SpotOn and back to the client 'shall be borne by SpotOn'. Shortfall: no turnaround time is stated anywhere, the remedy is SpotOn's election rather than a swap, and it is a return-to-depot flow, not advance exchange. https://www.spoton.com/legal/point-of-sale-terms/ · retrieved 2026-09-05 adversarially verified

The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.

reliability-pci-dss-4-attestation

SpotOn does run a trust centre at trust.spoton.com listing 'PCI DSS v4.0.1' and 'SOC 2 Type 2', which is a current-version PCI claim covering the post-March-2025 requirements, and the merchant side is separately staffed — the PCI Compliance Merchant Guide gives 24/7 access to SecureTrust by Viking Cloud at 1-800-363-1621. Shortfall: the attestation itself is not published. The trust centre gates the artefacts behind 'Get access' and 'View & download sensitive information', so no Attestation of Compliance, no validated P2PE listing and no SAQ-type statement for SpotOn merchants is readable without requesting access. https://trust.spoton.com/ · retrieved 2026-08-03

Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.

reliability-mfa-role-based-access

MFA is enforced on sensitive Dashboard operations and documented as a prerequisite: changing the bank account requires "Multi-Factor Authentication (MFA) enabled for your account" and a "Step 4: Verify Your Identity (MFA)", and a "Complete any MFA prompt if requested" step recurs through the Dashboard article set (Reviews, Statements, Custom Views, My Team, DayCheck, Profit Assist, online ordering settings). Role-based access is the Job Positions / Employee POS Permissions / Manager Permissions model, granular per action and per location. https://help.spoton.com/space/SK/4176969851 · retrieved 2026-08-03

A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.

reliability-self-serve-training

A free public training library exists and is substantial: 1,044 public knowledge-base pages requiring no login, organised by product, with video tutorial articles for Terminal, Serve (Quick Send & Pay) and SpotOn Order, plus release-note subscriptions and Spanish-language KDS documentation. Shortfall: no training or practice mode on the terminal is documented — staff learn on the live system or from video. https://help.spoton.com/space/SK/1762951196 · retrieved 2026-08-03

Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. differentiator

reliability-failover-terminal-role

OWNER RULING 2026-09-18 (Q5): a cloud-hosted POS with no in-store master/primary terminal role scores `no` on reliability-failover-terminal-role rather than unknown. Landed no/B on the evidence below, which establishes that architecture. Retrieved 2026-09-18. PRIOR EVIDENCE: VERDICT: still unknown. Express's documented offline model is per-device: "Offline Mode allows your POS or Kiosk to continue functioning during internet disruptions ... Orders are still sent to the kitchen printer or KDS", and "Offline Mode is not available for RPOS devices" (help.spoton.com/space/SK/4073652945). "Offline Mode with Fresh KDS" (5085823000) says orders reach the KDS over the local SpotOn network when the ISP is down. No help-centre page names a master/primary station or promotion on failure. The "failover" hits are printer failover routes ("Failover Print Routing", legacy RPOS BOH) and a handheld "4G cellular failover" question (1194557666), not a terminal role. NEW SURFACE (320th): the PRODUCTION SpotOn merchant-dashboard micro-frontend import map, https://spoton-prod-import-map-public.s3.amazonaws.com/import-map.json (anonymous, 200, 10,900 bytes; linked from https://express-dashboard.spoton.com/runtime-config.js as REACT_APP_IMPORT_MAP_URL; express-dashboard.spoton.com robots.txt is "User-agent: * Disallow:", i.e. no bar). It names 38 dashboard modules. All were fetched anonymously with their statically referenced chunks: 1,234 JS files, 113.6 MB. Refused (403) and therefore NOT held: settings-web, virtual-terminal-web, virtual-terminal-legacy-web, invoices-web, partnerships-embedded, mbo-agent-web; restaurant-reporting-dashboard-frontend did not resolve. Because settings-web is refused, this is NOT a census of the dashboard and cannot carry a no. fail.?over and "primary (terminal|station|device)" have 0 hits in it. Retrieved 2026-09-16. || 323rd: 323rd, NEW SURFACE: NEW SURFACE (323rd) and a CORRECTION OF THE 320th: the merchant-dashboard modules the 320th recorded as "Refused (403) and therefore NOT held" are NOT refused. Two things were wrong. (1) A Cloudflare/CloudFront 403 to node's fetch is a FALSE refusal: with curl carrying a browser UA plus Accept and Accept-Language, invoices-web (3,091,564 B), mbo-agent-web (1,626,895 B), partnerships-embedded (2,026,725 B) and virtual-terminal-legacy-web (3,963,912 B) all return 200. (2) settings-web and virtual-terminal-web were never blocked at all - their import-map URL is a 489-byte / 337-byte System.register LOADER STUB that names the real bundle, e.g. settings-web's stub loads ./assets/spoton-settings-web-BVYEUikC.js (991,568 B). AND THAT APP SHIPS PUBLIC SOURCE MAPS. Taking settings-web's './<chunk>.js' reference set to fixpoint: 116 chunks, and 116 of 116 carry a real source map (12,975,309 B of maps, every one {"version":3, with sourcesContent) - ZERO unmapped chunks - yielding 482 original TypeScript/TSX source files, 2,192,895 bytes, of SpotOn's own settings application (grade B, the vendor's own shipped source). Soft-200 control: /assets/zzz-nope.js returns 1,572 bytes of text/html, nothing like a map, so these are real files. The 482 sources are the COMPLETE merchant-dashboard settings surface for both Express and RPOS merchants: accountSettings, bankAndTax, batchTimes, businessHours + newBusinessHours (incl. Dayparts and Reporting/fiscal hours), businessInformation (incl. ReceiptCustomization), employees + multiLocationEmployees, giftcards, laborAndCompliance (AutoClockout, BreakTypes, Overtime, CashTipsManagement, ScheduleEnforcement), managerPermissions, permissions, myAccount, ordersAndTips (OrderTypes, AutoGratuity, TipAmounts, AutoprintReceipts, RequireName), paymentTypes (cash, customTenders), posUiSettings (DefaultTab, GuestCount), reportSubscriptions, revenueCenters, security, support, taxesFees (taxes, fees, surcharge), plus the legacy settings app. BOUND/LIMIT: this is the SETTINGS app only - menu (express-menu-web), loyalty (loyalty-web, reached from settings by an external link to `${applicationBase}loyalty/settings`), reporting and the POS/KDS device apps are separate modules and are not covered by this census. fail.?over, "master terminal", "primary terminal" and "terminal role" all score 0 across the 482 sources, and the only POS-device configuration the dashboard exposes is features/posUiSettings, which is just two settings (DefaultTab and GuestCount). So no terminal-role or promotion-on-failure setting exists in the merchant dashboard; the behaviour, if any, would be device-side and is not published, so the cell stays unknown. Retrieved 2026-09-17. || 325th: 325th, NEW BOUND, still unknown - and the reason is that the claim's PREMISE is absent rather than the capability. Across a full-body census of the vendor's KB, /\b(primary|master) (terminal|station|device|register)/ hits 1 page and it is the Reserve host iPad ('a backup if the primary iPad is unavailable (lost, damaged, or uncharged)', 1455685695); 'local server' 0 pages; 'main terminal' 1 page, an archived 2022 Serve release note about clocking out for cash management; fail.?over 6 pages, all of them PRINTER failover ('A Failover Print Route is an alternate printer route that will automatically print should the default printer fail', 762314779), a Sidekick Bluetooth printer fallback, a Serve handheld '4G cellular failover' FAQ, and an archived venue Void Group typed Primary/Failover. SpotOn Express documents no designated master/server station at all - offline resilience is PER DEVICE ('Offline Mode allows your POS or Kiosk to continue functioning during internet disruptions', 4073652945) - so there is no primary role for another terminal to assume, and a no would assert an absence about an architecture the claim does not fit. Held unknown per the lacks-entirely rule. BOUND: the FIRST full-BODY census of help.spoton.com, taken from the publisher's own listing (Confluence v2 API https://help.spoton.com/api/v2/pages?limit=100&sort=-modified-date&body-format=storage, paged to fixpoint - rounds 29 and 30 returned 0 new pages): 2,145 pages WITH BODIES (1,083 current + 1,062 archived), 4,154,015 chars of tag-stripped text, version dates 2020-11-24..2026-09-17. Validation: 141 of the 142 help-centre page ids already cited in this record are inside the listing; the one absent (4456513592) now 404s on the API itself, so the KB is a census minus one deleted page. Prior passes held bodies for only the 121 most-recently-modified pages and titles for the rest. Controls are tokenised word-boundary case-insensitive over all 2,145 bodies; the denominator is 2,145. Retrieved 2026-09-17. || 327th: 327th, NEW SURFACE - and it is the one the 320th and 323rd recorded as REFUSED. Applying the curl rule to the six merchant-dashboard micro-frontends those passes could not fetch, ALL SIX now return 200: settings-web (489 B System.register entry -> 2 files, 992,057 B at fixpoint), virtual-terminal-web (337 B), virtual-terminal-legacy-web (3,963,912 B), invoices-web (3,091,564 B), partnerships-embedded (2,026,725 B), mbo-agent-web (1,626,895 B). NONSENSE CONTROL PASSED: https://settings-web.spoton.com/zzz-nonsense-control.js returns a 1,572-byte HTML shell (`<!doctype html>... <title>SpotOn</title>`), while the real bundle is 489 bytes of `System.register(["./assets/spoton-settings-web-BVYEUikC.js", ...])` - different length and different first bytes, so these are real files. So the 38-module dashboard census that blocked several cells can now be COMPLETED by a future pass. CONTROLS over the 11.63 MB newly opened: failover 0, 'primary terminal' 0; 'master' 6 hits, ALL POISON (the ua-parser-js device table's `/master.|lts./` Cobalt-version regex, repeated per bundle). STILL UNKNOWN for the reason the 325th gave: this is the BACK-OFFICE dashboard, which does not bound the store-level POS, and SpotOn Express documents no designated master/server station for another terminal to assume. Retrieved 2026-09-18. || 328th: 328th, PER-CELL RE-GREP (no new fetching) of the corpus nobody had run this cell against: the help.spoton.com Confluence census, 2,145 bodies / 4,182,309 stripped chars, taken to a fixpoint by the publisher's own v2 listing API in the 325th (rounds 27-30 all returned 2,145). It covers the STORE-LEVEL products (SpotOn Restaurant FOH/BOH incl. the Legacy set, Express FOH/POS/Kiosk, Serve, Sidekick, Counter, Enterprise), so the 325th/327th objection that only the back-office dashboard was held no longer applies. TOKENISED, word-boundary, case-insensitive controls over all 2,145 docs (known-positive: `terminal` 232 docs): `master terminal` 0, `primary terminal` 0, `backup terminal` 0, `designated terminal` 0, `host terminal` 0, `local server` 0, `database server` 0, `back office computer` 0, `BOH computer` 0, `SQL` 0, `takes over` 0, `assume the role` 0, `high availability` 0, `self-healing` 0, `peer` 0, `failover terminal` 0, `on-prem` 0. POISON NAMED: `failover`/`fail over` scores 7 docs and EVERY hit is one of two unrelated features - 'Failover Print Routing A Failover Print Route is an alternate printer route that will automatically print should the default printer fail' (Printers | SpotOn Restaurant BOH, help.spoton.com/space/SK/762314779) and 'select Primary to make the Void Group a Primary Group or Failover to make the Void Group a backup Group' (Create a New Void Group, /2340366737). `master` scores 4 docs, all poison (a Retail 'master or main product' variant parent; a KDS 'Master Vendor'; 'Master Suites access Setting'; a 'master FedEx account'). `redundancy` 1 doc, poison (an Appointments release note about a redundant booking step). THE BIGGEST TRAP IS THE VENDOR'S OWN WORD: `Server` in SpotOn Restaurant is a STATION TYPE meaning a waiter workflow, not a master role - 'What is the difference between the Bartender, Cashier, and Server Station Types? ... Server Typically used where multiple employees share POS terminals without dedicated cash drawer access' (Station Type FAQs | SpotOn Restaurant BOH, /5435260930), and the Station Type FAQ enumerates what a Station Type controls ('Command Bars, Payment behavior, Receipt settings, Print routing, Order workflow, Operational permissions, Station appearance and functionality') with no server/master role among them. WHY THIS IS STILL NOT A `no`: the architecture the claim presupposes is absent rather than denied - the only architecture statement in the whole census is 'SpotOn Enterprise hardware communicates directly with the server to perform nearly all functions. The client hardware communicates with the server over a standard network connection' (Network Requirement Guide | SpotOn Enterprise, /2340356672), i.e. a hosted server, not an in-store master terminal. Per the lacks-entirely rule this is held unknown. Retrieved 2026-09-18. || 330th: 330th, one new PUBLISHED vendor statement on the architecture this claim presupposes, from the Point-of-Sale Terms (https://www.spoton.com/legal/point-of-sale-terms/, retrieved 2026-09-18): SpotOn's answer to a store-level failure is a CONNECTIVITY backup, not a terminal role - 'SpotOn will provide one (1) gigabyte of LTE access each calendar month, to be used as backup connectivity for SpotOn Restaurant in the event that internet access is limited or disrupted at the business location', delivered on a SpotOn-supplied Cisco Meraki router, and the same terms prohibit customer-supplied hardware in that path ('the use of external devices not provided by SpotOn, such as personal routers and computers, is prohibited'). That is consistent with the 328th finding that no master/primary/backup terminal role exists anywhere in the 2,145-body help.spoton.com census, and it identifies what the product substitutes for one: an uplink failover to the cloud. It is still not a denial of the claim's mechanism, so per the lacks-entirely rule the cell is held unknown and is an OWNER POLICY call: if a hosted-cloud POS with no in-store master terminal is to score `no` on this differentiator rather than unknown, SpotOn now has the evidence for it (no local server, no designated primary, an LTE uplink as the documented outage answer); if 'the architecture does not apply' keeps its unknown, nothing further on this vendor will move it - two full censuses (help.spoton.com 2,145/2,145 and the 38-module dashboard import map) have now been run against it. Retrieved 2026-09-18. https://www.spoton.com/legal/point-of-sale-terms/ · retrieved 2026-09-18 adversarially verified

Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.

reliability-cellular-backup

Documented automatic failover on the Serve handheld: "It's been confirmed that the Android device prioritizes Wi-Fi over cellular. It will automatically switch to cellular if the Wi-Fi connection is lost (assuming cellular is turned on)." Reserve's iPad Host App carries a comparable documented LTE path. https://help.spoton.com/space/SK/1194557666 · retrieved 2026-08-03

Vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core POS software tier. differentiator

commercial-month-to-month-contract

The published POS terms state it directly for the paid software tier: "Your Restaurant POS and processing agreement is on a month-to-month contract that you may cancel at any time", with cancellation by email to restaurant@spoton.com or by phone. The pricing page corroborates: POS Essentials at $55/station is sold with "month-to-month flexibility" while only the $0/station All-In plan carries a "2yr minimum term". https://www.spoton.com/legal/point-of-sale-terms/ · retrieved 2026-08-03 adversarially verified

Vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. differentiator

commercial-no-early-termination-fee

Two distinct exit charges are published. The POS terms impose a hardware clawback within the first year — cancelling requires the customer to "pay SpotOn the difference between your initial purchase amount and the full List Price of all hardware purchased", reclaiming the promotional discount on every terminal — and the Merchant Terms add liquidated damages on the subscription: on termination other than for SpotOn's breach, "Client shall owe and pay all Fees due for monthly subscription months for all unpaid months remaining during the Term", which bites on the 2-year All-In plan. https://www.spoton.com/legal/point-of-sale-terms/ · retrieved 2026-08-03

The auto-renewal term and the required cancellation notice window (e.g. 30/60/90 days) are stated in publicly accessible contract terms rather than only in a signed quote.

commercial-autorenew-terms-published

The term structure is public: the Merchant Terms provide that the contract "shall remain in effect so long as Client has contracted for or is receiving or using any Services", client termination requires "thirty (30) days' written notice... if SpotOn materially breaches", and fee changes carry at least 30 days' notice. Shortfall: no auto-renewal term length and no required non-renewal notice window are published for the 2-year All-In plan — the published documents cover a month-to-month agreement and a breach-termination right, not renewal mechanics. https://www.spoton.com/legal/merchant-terms/ · retrieved 2026-08-03

The POS software can be purchased and operated with a third-party payment processor of the operator's choice (no mandatory in-house processing lock). differentiator

commercial-processing-not-bundled

A third-party processor is contemplated by the published POS terms, and priced: "Should you wish to continue to use your SpotOn Restaurant system, but partner with a different payment processor, you will pay a $995 conversion fee and your software license costs will double." Shortfalls: the conversion charge is four figures and the software penalty is permanent rather than one-off; the same terms sell POS and processing as a single instrument ("Your Restaurant POS and processing agreement is on a month-to-month contract"); and the $0/station All-In plan cannot survive de-integration at all, because the pricing FAQ states "you pay for your hardware and software costs over time with a higher credit card processing rate." https://www.spoton.com/legal/point-of-sale-terms/ · retrieved 2026-08-03 adversarially verified

Vendor publishes an interchange-plus (cost-plus) processing rate option with the markup stated as a specific bps + per-transaction figure, rather than only blended/flat card-present rates. differentiator

commercial-interchange-plus-published

The pricing page enumerates the available rate structures and interchange-plus is not among them: All-In at "2.79% + $0.20" card present, POS Essentials at "2.45% + $0.15", keyed rates for each, an Amex carve-out, and "Custom rates" only under the quote-only Build Your Own plan. No cost-plus option and no bps markup over interchange is published anywhere on SpotOn's public site. https://www.spoton.com/pricing/ · retrieved 2026-08-03 adversarially verified

The processing agreement caps or prohibits unilateral vendor-initiated rate increases outside of pass-through interchange/network changes, or grants penalty-free exit on any increase. differentiator

commercial-rate-increase-clause

The exit right is real and verbatim: "SpotOn may change any Fees that it charges for any Services or Hardware provided by SpotOn by giving Client notice of such change (“Fee Change”) at least 30 days before the change becomes effective. Unless otherwise stated, if Client does not agree to any such Fee Change, Client may terminate this Contract... by notifying SpotOn of termination prior to the effective date of the Fee Change." Terminating that way is "expressly permitted under this Contract" and so escapes the remaining-months liquidated damages. Shortfalls: increases are not capped and are not confined to pass-through interchange or network changes; and the exit is not penalty-free, because the same Merchant Terms provide that "Clients using Hardware that terminate this Contract within two years of its Effective Date may be charged the difference between the list price for the Hardware purchased from SpotOn and the discounted price paid by the Client", unconditional on the reason for termination. Every SpotOn terminal is sold at a promotional discount, so an operator leaving over a rate rise inside two years repays it. https://www.spoton.com/legal/merchant-terms/ · retrieved 2026-08-03 adversarially verified

Per-location and per-additional-terminal software pricing is published as specific dollar figures on the vendor's public site (not 'contact sales' only).

commercial-pricing-published

Specific dollar figures are published per station and per plan: All-In "$0/station per month" with a 2-year minimum term, POS Essentials "$55/station per month" month-to-month, a "Core Bundle" at "$50/month" plus "20bps of GPV (capped at $200)", and Build Your Own at custom pricing. Hardware is priced per SKU on the same page. This is materially more disclosure than most of the mainstream restaurant peer group. https://www.spoton.com/pricing/ · retrieved 2026-08-03 adversarially verified

Individual modules (online ordering, KDS, loyalty, inventory, payroll, marketing) can be purchased à la carte and cancelled independently without repricing the base POS subscription. differentiator

commercial-module-unbundling

SpotOn's marketing product page publishes an a-la-carte module price: 'Restaurant owners that want hands-off restaurant marketing automation can add Marketing Assist for $95 per month. Restaurant SMS marketing software is available for an additional monthly cost based on message volume', while the base marketing tools and the AI menu assistant are 'included at no extra cost' (www.spoton.com/solutions/ai-menu-assistant/). So at least one named module is purchasable individually at a published monthly price on top of the POS. Shortfall: the pricing page itself sells bundles (Core Bundle at $50/month plus 20 bps of GPV) rather than a per-module price list, only Marketing Assist and SMS carry a standalone figure, and nothing states that a module can be cancelled without repricing the base subscription. https://www.spoton.com/solutions/marketing/ · retrieved 2026-09-02 adversarially verified

All required terminals, KDS screens, and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental.

commercial-hardware-purchase-outright

Hardware is purchased, at published per-SKU prices, and ownership is explicit: under the POS terms, after one year of installation the customer owns the equipment and no cancellation penalty applies. The clawback within the first year is framed as recovering the discount off "the full List Price of all hardware purchased" — a purchase, not a lease. No mandatory hardware rental or multi-year lease appears in the published terms or on the pricing page. https://www.spoton.com/legal/point-of-sale-terms/ · retrieved 2026-08-03

Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator

commercial-hardware-not-locked

Non-proprietary hardware is documented by model in several places: an Epson TM-L100 label printer with two dedicated configuration articles, a Honeywell Genesis 7580g barcode scanner with setup and reconfiguration guides, a GS1-standard barcode scale, a Worldpay cash drawer, an ELO customer-facing display, and operator-sourced tablets and bump bars for Fresh KDS. Shortfall: the POS terminals themselves are vendor-supplied only — Station 15, Station 10, the Handheld, Serve and the A800 — and no article documents running SpotOn Restaurant or Express on third-party hardware. https://help.spoton.com/space/SK/5004329007 · retrieved 2026-08-03

Operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee.

commercial-data-export-self-serve

Reports are self-serve and pushable: any report with the Print drop-down can be subscribed to for "automated daily email reports", a QuickBooks Export report ships in the RPOS reporting set, and Express offers a Daily Recap subscription. Shortfall: what is exportable is the report layer — no full transactional export of orders, line items, payments and labour is documented, there is no API to pull it, and the Merchant Terms disclaim any warranty that SpotOn can return client information on request. https://help.spoton.com/space/SK/2349728048 · retrieved 2026-08-03 adversarially verified

Guest/customer records, loyalty balances or point ledgers, and gift-card liability balances are exportable in machine-readable form by the operator. differentiator

commercial-export-customer-and-loyalty

SpotOn Restaurant Reporting exports natively - "All data displayed can be downloaded or exported for further analysis... Use Export to Excel or CSV" - and the reporting categories include Gift Cards and Loyalty (DineLoyal). Shortfall: neither the Customer Directory nor the loyalty point ledger itself exports; only aggregate reports do, and the loyalty report's contents are undocumented. https://help.spoton.com/space/SK/4644995176 · retrieved 2026-09-05 adversarially verified

Contract or documentation specifies a post-termination data retrieval window (a defined number of days during which the operator can still export their data) rather than immediate cutoff. differentiator

commercial-post-termination-export-window

The published Merchant Terms create no retrieval window and no return obligation: the client must request its data and "SpotOn makes no representations or warranties about its ability to return information". There is no defined number of days, no format commitment, and no counterpart provision in the POS terms. https://www.spoton.com/legal/merchant-terms/ · retrieved 2026-08-03

Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator

commercial-data-ownership-clause

The published Merchant Terms assert the opposite of the claim. SpotOn "reserves the right to access, retain, aggregate, process and share with third parties... all data available to SpotOn as a result of its performance of the Services" — a right that is not confined to aggregated or de-identified use — and no clause states that the merchant owns its transaction and customer data. Disputes are additionally routed to binding arbitration with jury-trial and class-action waivers. https://www.spoton.com/legal/merchant-terms/ · retrieved 2026-08-03

Vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A / SAQ P2PE-HW, and names the applicable SAQ.

commercial-pci-p2pe-tokenization

The vendor makes a scope-reduction claim and backs it with a versioned attestation listing: trust.spoton.com carries 'PCI DSS v4.0.1' and 'SOC 2 Type 2', and the PCI Compliance Guide for Merchants states 'our solutions minimize your exposure to cardholder data, reducing the PCI DSS compliance scope'; the Credit Card Transactions report shows partial PANs only. Shortfall: no validated P2PE listing is named, no tokenisation architecture is described, and SpotOn does not name the applicable SAQ — the determination is delegated to the merchant and to SecureTrust by Viking Cloud. https://trust.spoton.com/ · retrieved 2026-08-03

Vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — notably MFA for all access to the cardholder data environment including POS and back-office logins, and (for hosted ordering pages) payment-page script integrity monitoring per Req 6.4.3/11.6.1.

commercial-pci-dss-4-controls

One of the two named controls is demonstrably in force: MFA is required on the merchant Dashboard, documented as a prerequisite for sensitive changes ("Multi-Factor Authentication (MFA) enabled for your account", "Step 4: Verify Your Identity (MFA)") and recurring as a step across the Dashboard article set. Shortfalls: nothing published addresses payment-page script integrity monitoring under Requirements 6.4.3 and 11.6.1 for SpotOn-hosted ordering pages, and MFA on POS terminal administrative login is not documented — POS authority is a manager code or an unencrypted Manager Card ("Manager cards are not encrypted. The system reads the plain-text numeric code printed on the back of the card"). https://help.spoton.com/space/SK/4176969851 · retrieved 2026-08-03

Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.

commercial-privacy-dsar-tooling

There is a published, documented intake route for data requests — "How to Submit Legal Requests for Customer Information" — and the guest record carries an editable opt-in status that an operator can change on request. Shortfall: that article is a legal-process channel, not operator-facing DSAR tooling; no in-app workflow to locate, export or delete an individual guest's records is documented, and no executable DPA was found on SpotOn's public legal pages. https://help.spoton.com/space/SK/4673863715 · retrieved 2026-08-03

Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator

commercial-wcag-kiosk-accessibility

SpotOn publishes an accessibility statement committing to 'conform with applicable accessibility standards included in the W3C's WCAG 2.1 Level A and AA guidelines'. Shortfalls: it is a general web accessibility statement, not an accessibility conformance report — no VPAT or ACR is published, the statement does not name the self-order kiosk or the consumer ordering flow as in scope, and no tactile or audio non-visual access mode is documented for the kiosk anywhere in the knowledge base. https://www.spoton.com/legal/accessibility-statement/ · retrieved 2026-08-03

POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator

commercial-dual-pricing-compliant

Both compliant fee-offset programmes are documented with their guardrails. Surcharging: "SpotOn's Credit Card Surcharge automatically applies the surcharge to credit card transactions, but not debit or prepaid transactions", capped at "the lesser of either the merchant's current discount rate... or 3% of the transaction total", with a required receipt line item ("Credit Card Surcharge (3%): $3.00"), entrance and point-of-sale signage, equal application across all card brands, and 30-day network notification to Visa and Mastercard. Dual Pricing runs as a cash discount showing both totals at checkout, is "legal in all 50 states", is supplied with compliant signage, and carries an explicit warning that non-compliant framing exposes the merchant to Visa surcharge violations starting at $1,000. https://help.spoton.com/space/SK/4126277723 · retrieved 2026-08-03 adversarially verified