SpeedLine Solutions

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

'Customizable Floor Plans' to match physical space. Multiple saved layouts per location and server-section assignment not documented. https://www.speedlinesolutions.com/full-service · retrieved 2026-08-01

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

'Manage seats and separate checks in multiple ways.' Seat tagging at entry vs post-hoc split not distinguished. https://www.speedlinesolutions.com/full-service · retrieved 2026-08-01

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

Order Types > Printing tab, Send to Make Route setting: 'Automatic: Automatically sends the menu items to their make routes when the ticket is completed... Manual: The order-taker must touch the Send to Kitchen button in the Full Review window to send the menu items to their make routes.' The hold/fire unit is the whole ticket. The Table Service > General tab (12 settings: appearance, table/section selection, table alerts, colours, split-ticket assignment, auto-bus, multiple tickets, active tickets, initial order type) and the complete Terminal Security Privilege list (its Table Service section is Add Seat, Delete Seat, Move Selections, Split Selections) contain no course assignment and no fire-next-course action. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/setticketprintoptions.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Split checks 'in multiple ways' documented; merge, and splitting after partial payment, not documented. https://www.speedlinesolutions.com/full-service · retrieved 2026-08-01

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

order-capture-bar-tab-preauth

CLAIM: opens a bar tab against a card pre-authorization with a configurable auth amount, incremental re-auth as the tab grows, and auto-close of stale tabs at day end. VERDICT: no, on the published product help rather than the QA spec the prior pass had to disqualify. NEW SURFACE (326th) - THE PUBLISHER'S OWN TOPIC MANIFEST, FETCHED TO 100%. support.speedlinesolutions.com serves five Help+Manual ('hmWebHelp') webhelp sets under /Portals/0/CustomerDocumentation_SF/. Each ships its own complete topic manifest at js/hmcontextids.js (the hmContextIds[] array). Fetched all four live sets and then crawled every in-body href to a FIXPOINT (2 rounds each, 0 new files in the last round): Store Manager (the SpeedLine POS back office) ReleaseDocs/Store_Manager_help_Web 528 topics; Menu Designer ReleaseDocs/Menu_Designer_help_Web 269; SpeedLine+ Portal (the cloud above-store portal) SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web 398; SpeedDine Admin (online ordering admin) SpeedDine/SpeedDine_Admin_help_Web 140. TOTAL 1,335 topics / 3,144,482 characters / 521,711 word tokens / 7,037 distinct tokens. The href fixpoint added only 14 files beyond the context-id manifest and all 14 were fetched, so the corpus is closed: manifest union href-fixpoint, nothing unreached. A fifth set, SpeedLineNext/SpeedLine_Next_Admin_Help_Web, is referenced by seven dead links inside Store Manager topics and is 404 for index.html, hmcontextids.js and every named topic (retired, not withheld). robots.txt on this host is a GENERIC 'User-agent: *' bar on /Portals/ that names no crawler, so it was read like a browser under the standing order; no login, no auth. This is the vendor's own product documentation = grade B. SCOPE: these four sets cover the back office (Store Manager), the menu tool, the cloud portal and the online-ordering admin - i.e. every configuration surface of the SpeedLine product. The Terminal (the POS station itself) has no separate published help set: 'terminal help' returns 0 and Terminal behaviour is documented inside Store Manager Help. BOUND + CONTROLS over all 1,335 topics: `bar tab` 0, `open tab` 0, `start a tab` 0, `pre-auth` 0, `preauthorization` 0, `preauthorisation` 0, `preauthorize` 0, `pre authorize` 0, `authorization hold` 0, `incremental auth` 0. POISON NAMED AND MEASURED: the bare token `tab` returns 2,047 hits across the corpus and EVERY sampled one is a user-interface tab ('On the Settings tab, click System', 'Click the WorldPay (Vantiv) tab') - a raw `tab` count here would be a false positive of the worst kind. `Bar` is likewise an order type ('4 = Bar', importsalesdata.htm) and the cash 'bank', never a tab. The card-processing chapter (Worldpay/Vantiv, Monetra, SpeedLine Pay, EMV) documents sale, refund, tip adjust and tokenised card-on-file and no authorisation-hold workflow at all. Retrieved 2026-09-18. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/ReleaseDocs/Store_Manager_help_Web/index.htm · retrieved 2026-09-18 adversarially verified

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

Terminal privileges include 'Change Tickets to a Different Table - Move tickets to a different table', 'Change Tickets to a Different Server - Assign tickets to a different server', 'Move Selections - Move selections from one ticket or seat to another' and 'Recall Other Employee's Tickets'. Split-ticket ownership is configurable (Table Service General tab: Original User / Current User / Ask), so the system does distinguish the creating from the transferring employee. SHORTFALL: the audit artefact is the Terminal Ticket Activity report - 'to see a detailed list of the activities on a suspect ticket, the Ticket Activity Report can be viewed in Terminal' - whose fields are documented only in chapter 18 of the Terminal User's Guide PDF in the Store Manager Document Viewer, so it is not shown that a transfer entry names both employees. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/terminalsecurityprivilegesdesc.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Upheld and the note should be harsher. FAQ verbatim: "SpeedLine has mobile options for taking orders and payments anywhere within range of your Wi-Fi network." Wi-Fi-bounded, tablet-plus-paired-PIN-pad. No LTE, no purpose-built device. The dossier's note omits the Wi-Fi constraint, which is material for curbside/doorstep MobilePay claims elsewhere in the dossier. https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01 adversarially verified

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

FAQ: local copies maintained, system continues working if internet disconnects. No published works/does-not-work matrix. https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01

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

order-capture-qr-same-check

The SpeedLine Portal Help (139 topics) is the admin manual for the guest-facing SpeedDine ordering site, and it enumerates the guest order types: Company Management > Configure Order Types has one panel per order type and names them - 'if you do not want to use the default name shown for the order type ("Pickup" for the Pickup order type, or "Delivery" for the Delivery order type), enter a new one. This name will show on the "What type of order is this?" buttons on the ordering site.' Store-level Override Order Types only enables or disables those same panels. There is no dine-in or at-table order type: the strings dine-in, at-table, curbside and table do not occur anywhere in the 139 topics. Every QR code in SpeedLine's documentation is staff-facing - Store Manager's 'Print SpeedLine Pay QR Code' check box prints a ticket QR for a driver or server to scan into the SpeedLine Pay app, and 8.0 adds a Tattle survey QR on the receipt - none is a guest scan-to-order code. On the POS side the Store Manager Table Service chapter and Order Types settings screens contain no guest at-table ordering option, and incoming Connect and Marketplace orders 'appear in Terminal' as their own tickets. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/config-order-types.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Kiosks are third-party partners only — GojiKiosk, Nextep Systems, Checkmate. No first-party kiosk SKU. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

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

order-capture-drive-thru

Tablet-based drive-thru displays with EMV, order taken before the speaker. Order-point/pay-window/pickup-window separation and tandem lanes not documented. https://www.speedlinesolutions.com/quick-service-and-fast-casual · retrieved 2026-08-01

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

order-capture-drive-thru-timers

Report Descriptions introduces itself as 'a list of all the different reports available in the Reports tab'. Its only order-timing reports are Dispatch/Delivery Times - 'Dispatch (previously known as Out-The-Door/OTD) time is the number of minutes from ticket completion to dispatch. Delivery time is the time from ticket assignment at dispatch to the driver return' - and the per-ticket delivery statistics report. Both are delivery, not drive-thru. Drive-thru appears in the manual only as hardware: 'SpeedLine integrates with drive-thru order confirmation displays from Delphi Digital Systems. This topic covers how to set up communication between SpeedLine and a drive-thru display. It does not cover how to specify what is displayed.' No order, total or window segment timer is captured or reported. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/reportdescriptions.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Voicify is a named certified voice-AI partner injecting orders via SpeedLine Connect. Not first-party; no public API partner program. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

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

Quoted times auto-extend from kitchen volume. Per-channel per-slot capacity caps not documented. https://www.speedlinesolutions.com/delivery · retrieved 2026-08-01

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

Computed fire-time injection IS documented, contrary to the earlier note. Store Manager, Settings > Orders > Deferred Orders: 'Fixed Activation Time: Select to have all deferred tickets at the store activate at the same time each day ... If Terminal is not running at the activation time, the tickets will activate when Terminal is started', with 'Minutes Between Print and Required: Type or select the number of minutes between when tickets will print for preparation, and when deferred orders need to be ready', plus 'Initial Print Increment' (minutes added when the Print At button is pressed), 'Initial Required Increment' (minutes added when Ready For is pressed) and 'Max. Days to Defer'. The ticket therefore prints to its make route at required-time minus a configured lead, not on receipt. On the guest side, SpeedLine Portal > Set Deferred Ticket Restrictions offers a 'Defer Time Interval' for the time selector and 'Maximum Days to Defer ... (up to 31)'. SHORTFALL: the lead time is a single store-wide interval - the docs state 'This time interval will be the same for all orders, so enter enough time for staff to prepare even your larger deferred orders' - so there is no per-channel lead time. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/activateorchangedeferredorders.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

Catering reaches SpeedLine only as an ezCater marketplace channel, now documented first-party. SpeedLine Plus Portal Help, Menu Management ezCater: each product gets an ezCater tab with a 'Configure Number of Servings panel to define how many servings are included for each item selection', an 'ezCater Tax Category' list ('Orders sent to ezCater use tax categories and rates established in their platform; tax settings configured in the SpeedLine portal do not apply to ezCater orders'), an 'Individual Wrap Status' list (Always / Never / Possible), per-selection Dietary Tags, Free Tableware and Quantity Unit fields, and a checkout upsell field; onboarding is by SpeedLine Support entering the ezCater store UUID, and orders are cancelled from Terminal via the shared marketplace void flow. SHORTFALL: this is a channel, not a catering module. Nothing across the four Help & Manual manuals documents a catering quote, a deposit, balance-due tracking or an event/delivery schedule separate from the order queue; the Portal's own handling of large orders is the opposite - a Maximum Order Amount whose purpose is stated as 'to encourage customers to speak to store staff regarding large orders'. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web/menu_management-ezcater.html · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

order-capture-order-ready-signal

DoorDash publishes a machine-readable registry of its integration partners at https://merchants.doordash.com/api/partner-integrations — 64 providers, each tiered PREFERRED (12), CERTIFIED (47) or AT_RISK_OF_SUSPENSION (5), and each carrying an explicit true/false flag for 23 named integration features across four collections. It is served anonymously and merchants.doordash.com/robots.txt permits it. The programme is described, and its eight high-quality features defined in prose, at https://merchants.doordash.com/en-us/learning-center/doordash-preferred-integrations-program; the merchant-facing label for each flag comes from the label dictionary embedded in DoorDash's integrations comparison page. SCOPE: this attests the vendor's DOORDASH integration specifically — not Uber Eats, not Grubhub, and not the POS in general. DIRECTION: a true flag is a positive attestation; a false flag is NOT a reliable negative on its own, because Lavu's help centre documents a DoorDash temporary-closure control with scheduled auto-reopen while Lavu's `STORE_AVAILABILITY_WEBHOOKS` flag reads false, and Xenial's developer docs enumerate an order-ready notification while its `SUPPORT_ORDER_READY_SIGNAL` flag reads false. The flag `SUPPORT_ORDER_READY_SIGNAL` is TRUE for `speedline_production`. DoorDash labels the flag 'Order ready signal' and defines it on the programme page as 'Order ready signal - Notifies Dashers when an order is ready for pickup to improve timing and coordination.' That resolves a cell the vendor corpus left open: SpeedLine Plus Portal Help enumerates menu, out-of-stock marks, store hours, a pause/resume toggle and an operator-initiated cancel as what SpeedLine sends outbound, which is a floor on the documentation rather than a ceiling on the integration. `partial` and not `yes` because the claim reads on third-party marketplaces generally and names DoorDash only as an example, while DoorDash is the single channel this instrument can speak to; and because the claim specifies the signal fire from POS or KDS state rather than a tablet tap, which no flag identifies. https://merchants.doordash.com/api/partner-integrations · retrieved 2026-09-12

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

Per-employee/department/station security levels, manager overrides, and Employee Discounts / Coupons & Discounts exception reporting. Mandatory reason codes not documented. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01

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

Enforced Modifier nodes have a Behavior list (Popup, On Screen, Auto Add, Yes/No - the forced-selection flag), 'Min Qty and Max Qty boxes specify the minimum and maximum number of enforced modifiers that can be selected by the order-taker', per-node Min Qty Error and Max Qty Error messages, a Restrict By Size tab, and a Modifier Prerequisites tab with its own Min./Max. Qty. SHORTFALL: 'You can only have one enforced modifier in a group node, but you can add a second prompt to an existing enforced modifier.' The manual illustrates item-then-modifier prompting (an enforced 'Meat' modifier attached to a hand-tossed crust item) but never states that modifier groups can be nested three levels deep with independent counts at each level. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Menu_Designer_help_Web/addanenforcedmodifier.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Pricing engine spans size and crust axes with 'accurate pricing' automation; a modifier price matrix by parent and size is not explicitly documented. https://www.speedlinesolutions.com/point-of-sale · retrieved 2026-08-01

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

menu-pricing-fractional-placement

Menu Designer Help, Create Portions: "If you offer menu items in portions, such as a 'half pepperoni and half house special' pizza, you enter your available portions in the Portions tab. In Menu Designer, percentages are used to determine the size of portions... a 1/2 and 1/2 pizza would have two 50% portions. To create 1/3rd portions, create three 33% portions." Portions are arbitrary, not halves-only; the linked-button-set topic lists "1st Half, 2nd Half, 1st Quarter, 2nd Quarter, 3rd Quarter, 4th Quarter" as shipped Portion link types. Per-section pricing is a configurable Portion Price Method with five documented options - Highest Portion, Nearest Whole, Total Portions, Exact Portions, and "Independent Portions: Charges customers for toppings on each portion, as if each portion was an individual item." Modifiers attach to a portion of a portioned CYO base item (Use a CYO Item for Portions). https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Menu_Designer_help_Web/portionstab.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read 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 Portion Price Method list controls how item portions are priced in your menu.' Five options: Highest Portion ('The entire menu item will be priced based on the most expensive portion'); Nearest Whole (adds the modifiers from each portion, divides by the number of portions, rounds up - 2 and 3 toppings gives 3); Exact Portions (the same average unrounded - gives 2.5); Total Portions (sums every portion's modifiers); Independent Portions ('Charges customers for toppings on each portion, as if each portion was an individual item'). Portions themselves are percentage-defined, so thirds and quarters are supported as well as halves ('To create 1/3rd portions, create three 33% portions'). https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Menu_Designer_help_Web/portionstab.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Menu Designer Help, Define Modifier Types: modifier types are first-class order-entry buttons whose actions are "Add, Remove, Light, Heavy, On Side, Double, and Triple", applied to the next modifier the order-taker touches - genuinely distinct from adding the modifier twice. The multipliers are stated and fixed, not configurable: "Light multiplies the topping weight of the modifier by 0.5, but does not affect the price"; "Heavy multiplies the topping weight of the modifier by 1.5, but does not affect the price"; "On Side will add the modifier to the order as a separate item, but does not affect the ticket price"; Double and Triple multiply "the cost and weight of the modifier" by 2 and 3. Shortfall: there is no per-tier price multiplier field - light and heavy are weight-only (weight drives the Topping Matrix inventory draw), and the only price-bearing tiers are the hard-coded 2x and 3x. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Menu_Designer_help_Web/modifiertypestab.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

Menu Designer Help, Price a Sized Item: a Multi Price node carries a Sizes tab ("select the Sized box, and then select the sizes that the menu item is available in") and a Prices tab where you "Enter a price for each menu item size by clicking on a cell in the table", with Qty Levels forming the table's second axis. The shipped grid is therefore size x quantity level, not size x style. Crust/style is modelled as a modifier, and a modifier price node can itself be sized and scoped with Restrict To Item, so an effective per-(size, style) amount is settable - but additively, as item base price plus modifier price. Understanding Prices enumerates exactly three price node types (Single, Multi, Manual) and no topic describes a two-variant-axis grid with a per-cell override on the item's own base price. Partial: two axes are expressible, a single grid with per-cell overrides is not. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Menu_Designer_help_Web/addamultiprice.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

'A modifier that is included in the base price of an item is called an included modifier. The price of an included modifier is actually deducted from an item's price, rather than added to it... an included modifier will never cause the price of a menu item to fall below its base price.' The worked example is a create-your-own pizza with its first topping free; the Independent Portions price method similarly charges only when a customer orders 'more than two' toppings on a portion. Multi-price included-modifier nodes give a per-size allowance value, and the node can be restricted to an item, price group or order type. SHORTFALL: no allowance-linked substitution rule - Terminal has a generic 'Substitute Selected Ticket Item' privilege, but crediting a removed included topping against an added one, or forbidding substitution, is not a documented configuration. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Menu_Designer_help_Web/addanincludedmodifier.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

'Meal deals' and special groups priced automatically. Automatic a-la-carte-to-combo cart detection not documented. https://www.speedlinesolutions.com/point-of-sale · retrieved 2026-08-01

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

SpeedLine Plus Portal Help, Add an Upsell Prompt to a Product: 'Upselling prompts appear in the order cart either as a popup on the Customize page, or on the Order Details page during checkout (you choose)', configured per product or product group on an Upsell tab with an Upsell Name, an Upsell Type of Choice, Topping or Modifier Action, a Frequency slider setting 'the percentage of checkouts that will have this prompt', accept/reject button text and per-choice/selection/topping exclusions; a separate Cross-Sell Prompts node offers up to three items after the Checkout button. SHORTFALL 1, channel: 'Choice upsells only function on SpeedDine. Choice upsells are not currently supported in-store (Terminal). For upsells in-store using Terminal, use a Topping upsell type', and 'Topping upsells are only available for portioned products' - a channel constraint rather than per-channel configuration, and no kiosk surface exists. SHORTFALL 2, attach rate: the vendor reports none. The upsell's internal name 'will not appear on the ordering site, but will appear in Google Analytics tracking', i.e. measurement is handed to a third-party tag, and the cloud Report Definitions catalogue - which names every SpeedLine Analytics dashboard and every SpeedLine Report - contains no upsell, suggestive-sell or attach-rate report. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web/add-an-upsell-prompt-to-a-prod.html · retrieved 2026-08-09 · not refetchable · site policy · graded B when read 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

SpeedLine Plus Portal Help, Menu Management DoorDash, Out of Stock section: 'Items that are marked as Out of Stock on the SpeedLine Terminal will be reflected on your DoorDash Marketplace', marked by 'Navigate to the Operations panel in Terminal and touch the Out of Stock button', with the stated latency 'It may take a few minutes for the item or modifier to show as out of stock on your DoorDash Marketplace' and a symmetric procedure to make it available again; the Uber Eats and Grubhub topics carry the same section. For first-party online ordering, SpeedLine Portal > Synchronize Out of Stock with Store: 'Select ... to make regular checks for items that have been marked out of stock on the Terminal User screen at the store, and show out of stock status on the ordering site', with a Clear Out of Stock button and a company-level override. Store Manager, Activate Out-of-stock Menu Restrictions, closes the POS side: 'when an online order submitted through SpeedDine or SpeedLine Connect contains out of stock items or modifiers, SpeedDine, (or the third-party Connect provider, if they support this feature) will inform the customer.' One 86 action in Terminal therefore reaches POS, SpeedDine and all three marketplaces. Kiosk is excluded - SpeedLine ships no first-party kiosk. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web/menu-management-doordash.html · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

Items and modifiers are 86'd by hand: they are 'marked as out of stock using the Out of Stock button on the Terminal User screen', gated by Enable Out of Stock Menu Restrictions in System Options, with an order-taker prompt (OK / Cancel Item / Override) and propagation to SpeedDine and Connect providers. Auto-restore IS configurable: End of Day Options > Out of Stock Items - Clear Options offers Do not Clear, Clear, or Ask to Clear when day end runs. SHORTFALL: no per-item countdown or par count. Inventory tracks stock quantity and ideal usage, but nothing decrements a per-item sale counter to zero and 86s the item automatically; the two Out of Stock topics are the entire configurable surface of the feature. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/limitoutofstockitems.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Store Manager, Manage Price Groups: price groups support 'Time- or date-based pricing: alternative pricing for certain items at specified times or on specified days', and once Price Group by Item is set, 'When an item with the time-based price group specified in its price node is ordered during the enforced time, the price group is automatically applied' - with a documented overlap behaviour ('if "Monday Madness" and "Happy Hour" both apply ... the order-taker receives a prompt'). Online, SpeedLine Plus Portal Help, Add a Time Restriction to a Product or Discount, schedules the item itself: Date Range, Day Of Week and Time Of Day check boxes on an Available Items list assigned to Store Groups, with worked examples for a game-day meal deal, a weeknight 8 pm-1 am special spanning midnight (via a duplicated time frame) and an annual Feb 13-14 item. Timezone: each store record carries a Time Zone field - 'click the arrow to show a list of time zones, and then click the zone that matches the location of your store' - though the docs tie it explicitly to quoted/ready times and to ensuring 'deferred orders are sent to the store at the correct local time' rather than to evaluation of the menu schedule. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/editpricegroupsettings.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

Verified from the brochure screenshot: cloud menu has GENERAL / IN-STORE / THIRD-PARTY MARKETPLACES tabs, with DOORDASH split into "Increase Prices (Delivery)" and "Increase Prices (Pickup)", separate UBER EATS and GRUBHUB percentage fields, and a "Round to the nearest dollar" checkbox on each. Body text: "Add a percent increase per third party ordering site to recoup your costs for their service." https://www.speedlinesolutions.com/hubfs/SpeedLine-Marketplace-Brochure.pdf · retrieved 2026-08-01 adversarially verified

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

'There are three types of price nodes in Menu Designer': Single Price, Multi Price, Manual Price. Additional price nodes 'apply when specific order types or price groups are selected' - never a tender type. The cash/card differential SpeedLine documents instead is a tender surcharge applied at payment (Money > Tender Types > Tender Surcharge: name, caption, order types, flat rate or percentage, amount, tax group), a charge line added after the item price rather than a second stored price. The Format Printed Tickets surface enumerates guest-check content and includes no cash-and-card dual total. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Menu_Designer_help_Web/understanding_prices.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

Menu changes can be staged as an effective-dated version, previewed before publish, and rolled back to a prior version after publish. differentiator

menu-pricing-versioning-effective-dates

FAQ: preview a menu change before it goes live; Validate/Save/Preview controls in the cloud menu editor. Effective-dated versions and post-publish rollback not documented. https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01

Supports a central corporate menu template pushed to locations with field-level governance controlling which attributes a location may override. differentiator

menu-pricing-franchise-hierarchy

Master menu standardizes chain-wide while allowing regional or store-level differences. Field-level lock governance not documented. https://www.speedlinesolutions.com/enterprise · retrieved 2026-08-01

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

Two partial mechanisms, neither a per-item allergen/nutrition record. (1) Staff-facing free text: Menu Designer Help, Add Help Text to an Item or Modifier - 'Every item and modifier has a Help Text tab ... Use the help text tab to enter additional information about an item, such as ingredients, recipes, selling points, or allergy warnings', shown in a Terminal pop-up behind the Help button. Unstructured, and not published to any guest channel. (2) Structured but single-channel: SpeedLine Plus Portal Help, Menu Management ezCater, publishes a per-selection Dietary Tags field - 'Select any dietary tags that apply to the product. For example, Gluten free or Kosher' - alongside servings, quantity unit, individual-wrap status and free tableware. SHORTFALL: dietary tags are diet-preference labels, not an allergen flag set, and they exist only on the ezCater tab - the DoorDash, Uber Eats, Grubhub and SpeedDine menu topics have no equivalent. No nutrition or calorie field appears anywhere across the Store Manager, Menu Designer, SpeedLine Portal and SpeedLine Plus manuals; Item Contents nodes hold recipe ingredients and unit weights for inventory and make-ticket printing only, so there is no recipe-derived nutrition. The per-item calories on the SpeedDine menu sit inside the item's hand-typed description sentence. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web/menu_management-ezcater.html · retrieved 2026-08-09 · not refetchable · site policy · graded B when read 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

SpeedLink exposes an Inventory Period data file and the product carries food-cost reporting, implying sales-driven theoretical depletion. Explicit item-to-recipe linkage not documented. https://www.speedlinesolutions.com/hubfs/SpeedLink.pdf · retrieved 2026-08-01

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 integrations to DoorDash, Uber Eats, Grubhub, ezCater with automatic simultaneous menu/price sync — no middleman. Per-item sync status and rejection-error surfacing not documented. https://www.speedlinesolutions.com/hubfs/SpeedLine-Marketplace-Brochure.pdf · retrieved 2026-08-01

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

menu-pricing-dynamic-pricing

Time-based automatic price adjustment and per-channel markup rules exist. Demand-driven pricing with floor/ceiling guardrails not documented. https://www.speedlinesolutions.com/enterprise · retrieved 2026-08-01

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

Shortfall named: the documented Processor Interface list has exactly two vendors, not open choice. Store Manager Help, Enter Credit Card Settings: "Either Monetra or Worldpay payment processing software must be set up before credit card payments can be processed through Terminal." The Card Processing chapter enumerates only Monetra, Worldpay Express and Worldpay MercuryPay (plus a Worldpay Express (Gift Only) interface). Worldpay Express supports "two Worldpay platforms: Express and DataCap (MercuryPay)". EMV card-present additionally requires Worldpay triPOS purchased through SpeedLine ("If you have not yet purchased triPOS, please contact your SpeedLine sales representative for options and pricing"). No list of acquirers reachable via Monetra is published. The FAQ's "processor of your choice" is a marketing-grade overstatement of a two-interface list. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/entercreditcardsettings.htm · retrieved 2026-08-02 · not refetchable · site policy · graded B when read adversarially verified

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

payments-published-rates

No rate published on any page or brochure; the site has no pricing page at all (/pricing 404s). Rate comparison is offered as a lead-gen PDF, not a rate card. https://www.speedlinesolutions.com/speedlinepayments · retrieved 2026-08-01

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

payments-dual-pricing

Money > Tender Types > Tender Surcharge is the documented mechanism: 'add a surcharge that will be applied when specific tender types are used for selected order types', configured as Name, Caption, Order Types, Type (flat rate or a percentage 'applied to the final amount (excluding tips)'), Amount and Tax Group. That is a charge added at tender, not a stored card price. Menu Designer's three price node types vary by size, quantity, order type and price group only. The Format Printed Tickets settings enumerate what prints on a guest check (header, footer, item contents, quantities, modifiers, bar code, SpeedLine Pay QR, highlights, customer position, summarised taxes) and there is no cash-and-card dual total. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/add_surcharges_for_tender_type.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

The vendor's own warning on the Tender Surcharge topic: 'SpeedLine cannot detect debit-capable credit cards (including branded gift cards) before they're surcharged. For instructions on how to set up duplicate tender types, please click here.' The surcharge is configured per tender type and its complete field set is Name, Caption, Order Types, Type (flat or percentage), Amount and Tax Group - no BIN or product-code lookup and no network percentage cap enforcement. Compliance is pushed to the operator: 'Credit card surcharging, while legal in some regions, is heavily restricted by card brands. Please refer to your merchant agreement and the laws that apply to your region before proceeding. As the merchant you are responsible for all penalties imposed by card brands.' https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/add_surcharges_for_tender_type.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

payments-emv-nfc

'Supports all major credit cards, debit cards, mobile wallets, and contactless payments'; EMV PIN pads on tablets. https://www.speedlinesolutions.com/speedlinepayments · retrieved 2026-08-01

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

payments-softpos-tap-to-pay

MobilePay is consistently described as an app used with a card reader, not reader-free phone acceptance. No Tap to Pay on iPhone/Android claim. https://www.speedlinesolutions.com/speedlinepayments · retrieved 2026-08-01

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

MobilePay takes cards in the dining room, at the patio table, curbside and at the doorstep; full-service page markets contactless payment at table. https://www.speedlinesolutions.com/speedlinepayments · retrieved 2026-08-01

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

payments-qr-guest-pay

Format Printed Tickets, Print SpeedLine Pay QR Code: 'Select to print a QR code with the encoded ticket number and amount owing at the bottom of tickets using this format. The code can be scanned by the SpeedLine Pay app on the driver's phone to quickly transfer the amount owing to the app.' Activate SpeedLine Pay repeats it - 'the driver or server can scan it using the SpeedLine Pay phone app' - and payment is then taken on a staff-held mobile EMV reader talking to the Worldpay Express server. The ticket-content settings enumerate every element that can print on a guest check and this is the only QR code among them; the check QR is a staff data-transfer aid, not a guest payment link. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/formatprintedtickets.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

On-device: Tip Prompt Options on the Worldpay triPOS sub-tab set up to three percentages plus Other Dollar Amount and None (No Tip) on the EMV PIN pad, gated by the order type's 'Tips on EMV PIN Pad' setting and the tender type's 'Prompt for Tip on Overpayment'; the Monetra equivalents are entered in Monetra Administrator. After the fact: Terminal privileges '($) Add, Edit, Delete Tips - Add, edit or delete tip adjustments on tickets (payments will be adjusted for the difference)' and 'Add Tip to Closed Ticket', plus an 'Adjust for Tips' dialog that house-account tickets can be made to appear in. SHORTFALL: the adjustment is documented as an edit to an already-authorised payment, with Card Processing > Miscellaneous choosing 'Void and Re-charge' or 'Add Second Charge' - not a pre-auth then capture; and no adjust-window deadline or manager screen listing unadjusted tips is documented, settlement being simply 'Settle at Day End'. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/enter-tripos-settings.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Not native - available only through the 7shifts partnership on SpeedLine Plus. SpeedLine's advisory of 2026-06-11: 'SpeedLine has partnered with 7shifts to provide a direct integration between SpeedLine Plus and 7shifts... Tip Pooling: Managers can customize tip pool logic for equitable contribution and distribution, while 7shifts manages the funds based on SpeedLine Terminal labor data', with 'Clock-in and Clock-out data from Terminal flows seamlessly into 7shifts'. The allocation rules, the fund handling and the payroll hand-off all sit in 7shifts, a separately licensed product, and SpeedLine publishes no rule set of its own. SpeedLine's native tip surface is individual only: the Reports tab catalogue, which introduces itself as a list of all reports available, offers Tip Details, 'the details of all tip adjustments on tickets: ticket total, tip, and tip percentage'; the Day Report offers Tip Totals per employee; and the legacy ADP payroll export carries a single 'Earnings 3 Amount: The employee's total tips'. No pooling by hours worked, sales, role percentage or points exists inside SpeedLine itself. https://www.speedlinesolutions.com/supportadvisories/speedline-and-7shifts-join-forces-to-optimize-your-labor · retrieved 2026-08-09

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

Worldpay triPOS sub-tab: 'Enable Store and Forward: Select to activate Worldpay Express triPOS Store and Forward mode, which allows EMV payments to be accepted without a connection to the Express server (for example, when not connected to the internet).' Both limits the claim asks for are present and named: 'Store and Forward Transaction Limit: Type or select the dollar amount per transaction that can be approved locally while offline. Transactions over this limit will be declined.' and 'Total Limit Per Outage: Type or select the total dollar limit per station that can be approved locally during one outage period. This limit will be reset each time the connection to the Express server is lost.' The setting is exported to the SpeedLine Pay mobile app on configuration and can then be enabled, disabled or re-limited per device. Scope note: the mode belongs to the Worldpay Express/triPOS path. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/jspopups/enable_store_and_forward.js · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Caution on the Enable Store and Forward setting: 'When the Enable Store and Forward setting is selected, you will be prompted to accept liability for any offline transactions that are later declined when the connection to the Express server is restored. Managers will receive an alert when offline transactions are declined, or approved for less than the total owing, and must obtain alternate payment, or discount the amount owing.' Both halves of the claim are documented: who bears the loss (the merchant, by explicit in-product acceptance at the moment the mode is switched on) and post-reconnect surfacing of failed offline payments, including partial approvals. The surfacing mechanism is a manager alert rather than a standalone report. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/jspopups/enable_store_and_forward.js · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Valutec gift cards via direct integration, with mobile/contactless storage. Third-party stored value, not first-party; cross-location redemption not documented. https://www.speedlinesolutions.com/speedlinepayments · retrieved 2026-08-01

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

payments-house-accounts

'House Accounts are a simple accounts receivable system for those customers who want to charge their purchases to an account... Accounts are typically due on a monthly basis, and statements are printed from Store Manager or Terminal, and then mailed or faxed to the customer.' Settings tab: Enable House Accounts, Allow Charge to Third Party Account, Default Credit Limit, Change Credit Limit by Account (per-account override in Terminal), Prompt for Tip on Overpayment, Allow Tip Adjustments, signature and tip lines, forced reprint and additional copies. Running balance and history: 'The Customer Account Details report lists all the charges and other activity for a house account', with a Utilities tab that purges paid charges older than a chosen date while keeping outstanding ones. Terminal privileges add '($) Charge to Account' with a ceiling, 'Override Credit Limit', 'Payment to Account' and 'Account Charges and Credit Memos'. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/usehouseaccounts.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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 checks and seat handling 'in multiple ways'. No stated maximum split count and no documented multi-tender behavior. https://www.speedlinesolutions.com/full-service · retrieved 2026-08-01

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

Role-based security per employee/department/station plus manager override; discount and coupon activity reportable by employee. Immutable audit log naming the approver not documented. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01

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

payments-chargeback-tooling

Three enumerations, none of which holds a dispute view. (1) Store Manager's Money > Card Processing settings group (Credit Cards, Worldpay Express, triPOS, SpeedLine Pay, Monetra, Gift Cards, Miscellaneous) and its Reports tab catalogue, which describes itself as a list of all reports available, offer only settled/unsettled transaction and batch-total reports plus a manual settlement button - settlement and card reporting belong to the processor's own software (Monetra Administrator, Worldpay Express). (2) SpeedLine Portal Help, 139 topics covering the Portal's entire navigation (Menu Management, Store Management, Site Appearance, Company Management, Employees), contains the strings chargeback and dispute zero times; the Portal's Analytics side is exposed there only as employee permissions - 'Allow Analytics & Reporting', employee types Standard Analytics User / Store Owner-Administrator / Head Office Employee, Create/Edit Employees, View Pay Data - with no dispute or evidence-submission function. (3) SpeedLine's own documented chargeback workflow is a ticket search, not a dashboard: the 7.3 R300 advisory lists 'Search for tickets by the last four digits of the payment card number: find orders and investigate chargebacks more easily.' https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/assign-employee-permissions.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Real tokenized card-on-file, but online-ordering only. SpeedLine Portal Help, Tokenize Customer Credit Cards for Future Orders: 'To streamline the online ordering process, you can allow your customers to save their credit card information to a token for future use' - enabled at Company > General > Payment Card Processing > 'Tokenize credit cards', then per store at Tender Types > Payrix / Worldpay Express > 'Allow customers to save credit card details for future orders', with an optional 'Allow cards that have been saved to other stores in the franchise'. No PAN is held by the merchant ('stores a token representing the card information ... without storing sensitive card information'). SHORTFALL: (a) the saved credential belongs to the guest's account on the SpeedDine ordering site - nothing across the Store Manager, Menu Designer, SpeedLine Portal or SpeedLine Plus manuals documents an order-taker recalling a guest's saved card in Terminal for a phone or in-store order, and Terminal's own tokenization is a different mechanism scoped to one ticket ('Tokenize: Select to tokenize credit card information for deferred orders'); (b) 'Tokenization is available for SpeedLine Payments and Worldpay Express clients only' and 'You must first contact Worldpay Support to set up tokenization before activating this feature'; (c) it 'must be individually applied to each store location', and franchise-wide reuse needs the merchant account configured for it. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/tokenize-customer-credit-cards.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

payments-payout-timing

'Monetra is third-party payment processing software that allows your SpeedLine point of sale system to process payment cards (credit, debit and gift cards) automatically... Payments will be settled into your bank account at day end using the Monetra software.' The Worldpay Express equivalent is 'Settle at Day End: Select in order to settle card payments when Day End is run', with credentials (Account ID, Acceptor ID, Application ID, Access Token) issued by Worldpay. What SpeedLine controls is when the batch closes, not when money lands - deposit timing sits in the merchant's processor agreement. No deposit schedule and no next-day, same-day or instant funding option appears in the 458-topic Store Manager manual or on the vendor's payments page at www.speedlinesolutions.com/speedlinepayments. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/set_up_monetra_payment_process.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

A single account can route settlement funds to different bank accounts per location or legal entity (separate MIDs or split settlement) under unified reporting. differentiator

payments-multi-entity-routing

Card processing credentials live in each store's own database: the Worldpay Express tab takes that store's Account ID, Acceptor ID, Application ID, Access Token and StoreCard ID, and the Monetra tab a store-specific username of the form 'processor:slmonetra'; funds are 'settled into your bank account at day end'. Chain administration is separate - Multi-Store Administration and the Above Store add-on provide setting update packages, store profiles and store groups, and SpeedLine Cloud Reporting and Analytics provides cross-store dashboards. SHORTFALL: this is one merchant account per install rather than a single account splitting settlement; nothing in either manual documents routing funds to different bank accounts within one account, and the chain-level layer is documented for settings distribution rather than consolidated settlement reporting. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/setupvantivexpress.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

P2PE is asserted, an AoC is not published. SpeedLine's own support advisory of 4 Apr 2022, listing the advantages of the Ingenico Lane 3000 upgrade, states the device 'Is P2PE certified when using Worldpay Express' - so a validated-P2PE path is claimed for a specific pin pad and processor combination, and the earlier reading of E2EE-only is withdrawn. SHORTFALL: the validation belongs to Worldpay's solution rather than to SpeedLine, and SpeedLine publishes no P2PE listing reference and no PCI DSS 4.x Attestation of Compliance. Its PA-DSS Implementation Guide is reachable only from inside the product ('on the Store Manager Today tab, click Document Viewer'), PA-DSS itself was retired in Oct 2022, and the only PCI DSS mention in 784 documentation topics is an operational warning that 'Self-signed certificates may cause you to fail a vulnerability scan when completed by certain PCI DSS assessors.' Merchants are pointed to the resold SaferPayments service as a compliance aid rather than to an attestation. https://www.speedlinesolutions.com/supportadvisories/worldpay-update-removes-msd-contactless-payments · retrieved 2026-08-09 adversarially verified

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

Confirmed on the QSR page: "Route items strategically to customized prep or expediter stations" and "Prioritize rush items" / "Ensure all items in an order are ready at the same time." But the term "Make Routes" appears nowhere on the cited /point-of-sale or /quick-service-and-fast-casual pages; it recurs across four notes in this dossier as if it were a documented product name. Treat it as unverified terminology. https://www.speedlinesolutions.com/quick-service-and-fast-casual · retrieved 2026-08-01 adversarially verified

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

'Currently, SpeedLine supports the QSR ConnectSmart Kitchen (CSK) and Kitchen Display System (KDS) products from QSR Automations Inc.' SpeedLine's side is make-route selection and display formatting. Expediter screens are acknowledged: the Print When Bumped setting says 'In the Virtual Displays area, select the Print check boxes beside the displays you want to initiate the bump-printing. Usually you will want only expediter (expo) stations to initiate bump-printing', and 'If the Kitchen Builder Pro software is set to bump orders to the next display, select the Print check box only for the last display in the series, or you will get multiple printouts for the same ticket.' SHORTFALL: that is sequential bump routing configured in QSR's Kitchen Builder Pro, not consolidation. Nothing in the SpeedLine manuals states that an expo view aggregates items from multiple prep stations, or that an order completes only once every contributing station has bumped, and the expo screen requires the separately licensed third-party product. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/kitchenmonitors.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Order Types > Printing > Send to Make Route = Manual makes the order-taker 'touch the Send to Kitchen button in the Full Review window to send the menu items to their make routes when the ticket is completed' - whole ticket, one action, from the terminal. There is no course assignment in Menu Designer and no course privilege in the Terminal security set. The single occurrence of the word in the corpus is unrelated: 'Start New Course: Determines where additions to a completed order appear. On Complete Ticket: Select to show additions in a new grid (recommended). Never: Select to have additions appear in the same grid as the original order.' Firing a held course from an expo screen would be a QSR ConnectSmart function, and SpeedLine documents no course data going to the display at all. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/setticketprintoptions.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

KDS 'ensures order completion synchronization', prioritizes rush items, and adjusts for kitchen activity level. Per-item cook times and staggered start math not documented. https://www.speedlinesolutions.com/quick-service-and-fast-casual · retrieved 2026-08-01

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

Quote times extend automatically based on kitchen volume. Automatic pacing or delayed release of digital orders at a threshold not documented. https://www.speedlinesolutions.com/delivery · retrieved 2026-08-01

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

Both halves documented. Store pause: SpeedLine Plus Portal Help, Store Availability DoorDash - 'Navigate to Order Sources > Marketplace ... Click on the DOORDASH tab ... click the Pause Store button', which raises 'a message ... to confirm that you want to pause the connection and prevent DoorDash from accepting orders', drops Store Connection Status to PENDING, and is reversed by Resume Store returning it to ENABLED; Store Availability Uber Eats and Store Availability Grubhub are the same topic per marketplace, and the onboarding topics warn to 'Use the Pause Store feature instead' of disconnecting for a temporary stop. Item 86: Menu Management DoorDash - 'Items that are marked as Out of Stock on the SpeedLine Terminal will be reflected on your DoorDash Marketplace', set from 'the Operations panel in Terminal', taking 'a few minutes'. Store hours set in the Portal likewise push out: 'The store hours will update in all locations including SpeedDine, In-Store (SpeedLine Plus), and third-party marketplaces such as DoorDash, Uber Eats, and Grubhub.' Note the asymmetry: the availability toggle is a Portal action, not a Terminal or KDS button - the POS-originated half is the item 86. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web/store-availability-doordash.html · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

kitchen-order-ready-callback

DoorDash publishes a machine-readable registry of its integration partners at https://merchants.doordash.com/api/partner-integrations — 64 providers, each tiered PREFERRED (12), CERTIFIED (47) or AT_RISK_OF_SUSPENSION (5), and each carrying an explicit true/false flag for 23 named integration features across four collections. It is served anonymously and merchants.doordash.com/robots.txt permits it. The programme is described, and its eight high-quality features defined in prose, at https://merchants.doordash.com/en-us/learning-center/doordash-preferred-integrations-program; the merchant-facing label for each flag comes from the label dictionary embedded in DoorDash's integrations comparison page. SCOPE: this attests the vendor's DOORDASH integration specifically — not Uber Eats, not Grubhub, and not the POS in general. DIRECTION: a true flag is a positive attestation; a false flag is NOT a reliable negative on its own, because Lavu's help centre documents a DoorDash temporary-closure control with scheduled auto-reopen while Lavu's `STORE_AVAILABILITY_WEBHOOKS` flag reads false, and Xenial's developer docs enumerate an order-ready notification while its `SUPPORT_ORDER_READY_SIGNAL` flag reads false. The flag `SUPPORT_ORDER_READY_SIGNAL` is TRUE for `speedline_production`, so the outbound signal exists — which the vendor corpus never established. The claim additionally requires that BUMPING AN ORDER READY ON THE KDS is what emits the event, and the registry carries no flag identifying the signal's trigger. A necessary condition is attested and a sufficient one is not. The only documented consequence of a bump anywhere in SpeedLine's corpus is local: a Print When Bumped event printing a ticket at a nominated station. https://merchants.doordash.com/api/partner-integrations · retrieved 2026-09-12

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

kitchen-bump-bar-hardware

'Print When Bumped events are triggered when the Bump button is pressed on the bump bar or touchscreen monitor' - both input methods named, so physical bump bars are supported alongside touch. SHORTFALL: no models. The Supported Hardware and Software topic is a pointer rather than a list: 'Minimum requirements and supported hardware change regularly and are subject to change without notice. For the most up-to-date information, please see the SpeedLine Minimum Requirements and Supported Hardware document, available on the Customer Support web site as a PDF, in the Knowledge Base, or from SpeedLine Support.' The Kitchen Monitors overview repeats the same deferral for QSR products specifically, so supported bump bar models are not documented in the 458-topic web help. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/specify_print_whenbumped_processing_station.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

kitchen-all-day-counts

Assign Kitchen Monitor Make Routes, Consolidation area: 'select Combine Size With ItemId if you use the CSK or KDS summary tables, and have set the Size Display Location to Above Item or Beside Item in step 4', and 'Select Include Grouped Coupons to display a coupon's name grouped together with the items it applies to.' SHORTFALL: the summary (all-day) table is a QSR Automations ConnectSmart Kitchen / KDS capability configured in Kitchen Builder Pro - SpeedLine's contribution is item-key consolidation so that counts aggregate correctly. Neither manual documents an all-day quantity view native to SpeedLine, nor aggregation at modifier level. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/assignkitchenmonitormakeroutes.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Color-coded service alerts for wait times and table turnover; KDS monitors speed of service in real time. Operator-configurable target times per station not documented. https://www.speedlinesolutions.com/full-service · retrieved 2026-08-01

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

kitchen-printer-fallback

'It is important to have an alternate printer route set so that tickets can still print if the station connected to the original printer is not functioning... In the Alternate Printer list, select the printer to act as an alternate. If the station that the main printer is connected to is not working, print jobs will automatically be sent to this alternate printer.' SHORTFALL, in the vendor's own words: 'If a printer is offline or broken but the computer it is attached to is working, SpeedLine may not be able to detect this and may continue to route print jobs to the failed printer. If a printer has failed, route tickets to the alternate printer manually by selecting the Send Print Jobs to Alternate Printer check box.' So automatic failover covers station failure, not printer failure. The KDS side is equally manual: the Kitchen Monitors General tab has a Secondary Server Address whose 'Secondary Active' check box 'should only be selected if the primary CSK/KDS server is not active (for example, due to hardware failure)'. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/assignanalternateprinterroute.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

kitchen-offline-operation

Store-local transaction engine and local data copies imply KDS keeps receiving from on-site terminals during an outage; not explicitly documented for KDS. https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01

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

'You can also set item contents (but not units) to show on kitchen displays.' Procedure: enter recipes on the Menu Designer Contents tab, then 'On the Store Manager Settings tab, click the Hardware group, and then click Kitchen Monitors. Select the Include Item Contents check box... Displays will show the item contents for menu items (amounts are not shown).' The same make-route screen controls size display location and pushes ticket notes and selection notes to the display, and Menu Designer modifier types (Light, Heavy, Double, Triple, On Side, Remove) carry through, so a station screen shows more than ticket line text. Quantities and units print on make tickets but are not shown on screens. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/print_recipes_on_tickets.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Portions are real order structure (modifiers attach to a portion of a portioned CYO base item) and they reach prep: Menu Designer, Print Recipes on Tickets - "A modifier's As Modifier tab, Modifier Order setting will determine the order of modifiers printed on make tickets or displayed on kitchen displays", and Define Modifier Types illustrates a make ticket with a Remove modifier type highlighted in red. Shortfall: no topic in the manual shows the portion caption (1st Half, 2nd Quarter) or any sectioned layout rendered on the make ticket or the make-line screen - the only illustrated make ticket is a flat modifier list - and the make-line screen is not SpeedLine's own. Store Manager Help, Kitchen Monitors: "SpeedLine supports the QSR ConnectSmart Kitchen (CSK) and Kitchen Display System (KDS) products from QSR Automations Inc." Partial: the sectioning exists in the order and is routed to prep, but unambiguous visual rendering of sections on the make line is not documented. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Menu_Designer_help_Web/printitemcontents.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

kitchen-recall-refire

Terminal privileges, Printing section: 'Reprint Kitchen Instructions - Reprint kitchen make tickets from the Full Review Options', plus 'Reprint Labels', 'Allow Force Print' and 'Reprint Range of Tickets'; the Tickets section adds 'Recall Ticket' and 'Recall Other Employee's Tickets' for pulling a saved ticket back up without re-entry. Labels can be reprinted selectively - 'Reprint Labels for Modified Selections: will reprint labels only for modified items (this is the option typically selected)'. SHORTFALL: kitchen make-ticket reprint is ticket-level rather than a per-item refire, and no recall or unbump of an already-bumped display ticket is documented anywhere in the Store Manager manual; bumping is a QSR ConnectSmart Kitchen / KDS action whose only documented POS-side effect is Print When Bumped. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/terminalsecurityprivilegesdesc.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Format Printed Tickets exposes Highlight Additions, Highlight Changes and Highlight Deletions check boxes: 'select these check boxes to make additions, changes, deletions, or the ticket header and footer stand out on make tickets... If using an impact printer with red and black ink, highlights will print in red ink on the ticket... if using a thermal printer, highlights will print according to the Highlight Style option'. Order Types > Printing adds 'Print When Modified: Prints the ticket each time it is modified and completed (saved)', and label reprints can be limited to modified selections. SHORTFALL: on kitchen displays the only documented treatment of a post-send edit is the Kitchen Monitors 'Start New Course' setting - additions to a completed order appear either in a new grid or in the original one - with no documented visual flag for changed or removed items on a live KDS ticket. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/formatprintedtickets.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Real-time SMS or email order-status notifications to the guest, driven by order state; Twilio is the messaging partner. https://www.speedlinesolutions.com/delivery · retrieved 2026-08-01

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

kitchen-waste-logging

'There are three Adjust / Transfer Batch Types: Adjust... Adjust for Waste: This feature is used to decrease the stock levels to account for waste. It allows for a short note describing how the waste happened, such as "dropped on floor". Adjust for Waste is only meant to track stock items that are wasted... Transfer'. The entry is made in Settings > Inventory > Adjust/Transfer and posted to deplete stock, and the reason is a free-text Reference field rather than a reason-code list. Remakes are explicitly routed elsewhere: 'For menu items that are made for an order and then dropped or burnt, for example a pizza, re-enter the item in Terminal, and then void it and select "made" when prompted' - a Terminal action governed by the Void Reason List. SpeedLine's kitchen display integration surface (Kitchen Monitors General and Make Routes tabs) is outbound display formatting only and accepts no entry back from the screen. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/adjusttransferstock.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Strong on the delivery half — out-the-door time, on-the-road time, on-time delivery, late deliveries by timeframe, exportable. Per-station percentile ticket times not documented. https://www.speedlinesolutions.com/delivery · retrieved 2026-08-01

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

A Sales Forecast is a first-class object (exported as its own SpeedLink file and used to drive labor scheduling). A kitchen-facing prep task list is not documented. https://www.speedlinesolutions.com/hubfs/SpeedLink.pdf · retrieved 2026-08-01

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

Native in-house driver module: drivers are first-class, with dispatch state, out-the-door and on-the-road tracking, and per-driver run and reimbursement reporting from the POS itself. https://www.speedlinesolutions.com/delivery · retrieved 2026-08-01

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

delivery-dispatch-board

Verified twice. Delivery page: "Dispatch delivery drivers from an interactive map view to easily group orders together for delivery. Quoted times, estimated return times, and order totals are displayed at a glance." Ebook adds "Order status alerts will show any order delays or drivers that are running late, and will be color-coded according to priority." Pushpin grouping confirmed. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01 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

LiveMaps renders geocoded stops on a live map with optimized route sequencing and traffic-aware return estimates. https://www.speedlinesolutions.com/delivery · retrieved 2026-08-01

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

delivery-driver-tracking

Driver communication is one-way email. Each driver's profile carries a 'Phone E-Mail' field and a 'Driving Directions Provider' on the Driver and Vehicle tab; SpeedLine emails the driver a list of tickets with links, and the provider 'will resolve the address sent by SpeedLine and show a link to driving directions from the driver's current location' - position is resolved on the driver's own handset ('Drivers will need to enable GPS (Location Services) on their phones for some of the emailed directions to work') and is never sent back. The Dispatch Out Store view and the Driver Detail screen are ticket-grid layouts showing tickets 'assigned to a driver and are on way or delivered', not positions. No driver-facing app is documented anywhere in the 458-topic Store Manager manual - the only SpeedLine phone app in the manuals is SpeedLine Pay, for card payment - and 'GPS' occurs exactly once in all 646 topics, in the sentence quoted above. The vendor's own delivery page matches: for DoorDash Drive you 'Track the delivery on the DoorDash Drive portal'. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/senddrivingdirections.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Independently confirmed and the evidence is stronger than the dossier cited. Employee Management ebook, LiveMaps panel: "Need changes? Click and drag the points on the map to adjust zone boundaries at any time. When an order is placed, LiveMaps will assign the customer to a delivery zone based on their address, and charge the appropriate delivery fees for that zone." This is genuine point-editable boundary drawing, not radius/ZIP. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01 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

Delivery page verbatim: "Set custom delivery zones with adjustable boundaries so delivery fees are always correct" and "Set order minimums or time frame restrictions for certain zones to minimize low-profit routes." All three sub-claims (fee, minimum, time restriction) verified. https://www.speedlinesolutions.com/delivery · retrieved 2026-08-01 adversarially verified

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

FAQ: the system 'automatically assign[s] deliveries to the appropriate zone based on the address'; addresses geocode onto the LiveMaps view. https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01

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

Driver fees and mileage tracked by odometer and/or optimal-route distance, with a Driver Reimbursement Summary report and an ADP payroll export path separating reimbursement from wages. https://www.speedlinesolutions.com/delivery · retrieved 2026-08-01

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

Driver fees, mileage and tip totals are reported per driver and bank/cash reporting exists, but an explicit driver settle-up over/short flow is not documented. https://www.speedlinesolutions.com/delivery · retrieved 2026-08-01

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

Store Manager Help, Activate 3rd Party Delivery Service: "When you activate third-party delivery, SpeedLine can display a generic third-party delivery driver on the Terminal Dispatch screen, so delivery orders can be assigned to it. For example, you can summon a 'DoorDash Dasher' to pick up any delivery order by assigning the order to 'DOORDASH' in the driver list." Configured under Settings > Orders > Dispatch Options > 3rd Party Delivery with an External Business Name and driver pickup instructions, and gated by the Terminal > Dispatch > Assign Ticket to 3rd Party Delivery Service security privilege - a native handoff, not a portal round-trip. Quote and status return are corroborated by the SpeedLine/DoorDash Drive brochure: "Operators can quickly review the estimated pickup and delivery times, confirm the request, and watch the order as it moves through each stage", "Clear order status inside SpeedLine Terminal and the DoorDash Drive portal." Scope limits stated in the same docs: DoorDash is currently the only third-party delivery service integrated, and third-party orders must be pre-paid (no house-account tender). https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/activate-3rd-party-delivery-se.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

Hybrid dispatch is present but entirely manual. Activating third-party delivery makes SpeedLine 'display a generic third-party delivery driver on the Terminal Dispatch screen, so delivery orders can be assigned to it. For example, you can summon a "DoorDash Dasher" to pick up any delivery order by assigning the order to "DOORDASH" in the driver list ... when an in-store delivery driver may not be available', gated by the Terminal privilege 'Assign Ticket to 3rd Party Delivery Service'. Shortfall: the 3rd Party Delivery tab's configurable surface is enumerated in full - Active, External Business Name, Pickup Instructions for Driver, plus the tender types flagged 'Allow for 3rd Party Delivery Services' - and contains no automatic overflow rule of any kind (no out-of-zone, no wait threshold, no driver-availability trigger). All third-party orders must be pre-paid, and 'Currently, DoorDash is the only third-party delivery service integrated with SpeedLine.' https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/activate-3rd-party-delivery-se.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Store Manager Help, Enable SpeedLine Marketplace: 'SpeedLine Marketplace streamlines your operations by integrating online third-party ordering channels like DoorDash, Uber Eats, and Grubhub with your POS.' Activated at Settings > System > Store Information > SpeedLine Portal tab by selecting Active under Third Party Marketplaces, requires 8.0 R400 or later, and each channel is then onboarded through SpeedLine's own integration process ('SSIO Onboarding Information for DoorDash', 'Onboarding Information for Uber Eats', 'Onboarding Information for Grubhub'); 'Click Make Live on your SpeedDine Menu live to publish the menu to any third-party marketplace that has been onboarded. Orders placed on third-party marketplaces will appear in Terminal.' The 8.0 Release Notes record it as shipped: 'New: Direct integrations for DoorDash, Grubhub, and Uber Eats.' Vendor-owned rather than middleware is documented by contrast: the manuals treat Chowly and ItsaCheckmate as the separate, non-integrated aggregator route ('sources like third-party delivery companies (e.g., Grubhub) that are not integrated with SpeedLine via an aggregator service such as Chowly or ItsaCheckmate'). ezCater is a fourth Marketplace channel with per-product options in the SpeedLine Portal menu editor. Caveat on depth: the three SSIO onboarding pages themselves are unpublished - all three linked URLs under SpeedLineNext/SpeedLine_Next_Admin_Help_Web/ return 404 - so the certification detail cannot be read. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/enable-speedline-marketplace.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

delivery-3p-injection

'Orders flow directly into your SpeedLine POS'; eliminates multiple tablets and extra hardware. https://www.speedlinesolutions.com/hubfs/SpeedLine-Marketplace-Brochure.pdf · retrieved 2026-08-01

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

One cloud menu publishes to every channel. SpeedLine Portal Help, Preview and Activate a Menu: 'Beside the menu that you want to publish online, click the Make Live button. The previous online menu is replaced with the menu you are publishing'; Store Manager's Enable SpeedLine Marketplace completes it - 'Click Make Live on your SpeedDine Menu live to publish the menu to any third-party marketplace that has been onboarded.' Per-channel availability is a documented per-selection field: 'Select the Order Source (where the selection may be ordered from)... Clear any check boxes if you do not wish to allow orders from those sources', with in-store, SpeedDine and third-party platforms as the sources, plus ezCater-specific product options and dietary tags for Marketplace subscribers. Modifiers, toppings and value meals are edited in the same tree; product photos are managed there too (Add or Remove a Product Image). Availability syncs from the POS: 'Select the Synchronize Out of Stock with Store check box to make regular checks for items that have been marked out of stock on the Terminal User screen at the store', and prices refresh on a 30-minute Automatic Menu Version Synchronization or on demand. Shortfall in the evidence, not in the note's favour: the channel-specific markup is documented only in vendor marketing - the Marketplace brochure and /speedline-marketplace, 'Price Adjustment for Each Marketplace: Add a percent increase per third party ordering site to recoup your costs' - and appears nowhere in the 138-topic Portal help; photo publishing to marketplaces is likewise not stated. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/preview-and-activate-a-menu.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

Brochure verbatim: "Changes to menu items and restaurant hours reflect instantly across your platforms. Stock availability is updated after items are marked out of stock in the POS system." Modifier-level 86 correctly left unclaimed. https://www.speedlinesolutions.com/hubfs/SpeedLine-Marketplace-Brochure.pdf · retrieved 2026-08-01 adversarially verified

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

delivery-store-pause

SpeedLine Portal Help, Enter Special Days: 'The Online Ordering toggle in the SpeedLine portal allows you to quickly close or reopen the store for the current day. Closing the store will disable online orders until it is reopened or until the following day.' Set at Store > Store List > Operations > Special Days by flipping the Closed - Open switch and entering a mandatory Reason for Closure. Outward propagation is documented but conditional: 'Note Closing Online Orders will notify online ordering providers if they support that function' - SpeedLine never states which of DoorDash, Uber Eats, Grubhub or ezCater do, and the marketplace pause is asserted only in marketing ('Allows you to pause online orders from all third-party marketplaces in one convenient place', www.speedlinesolutions.com/speedline-marketplace). Reactivation is day-granular, not timed: 'Otherwise, Online Ordering will be automatically enabled again on the following day' - there is no pause-for-N-minutes control. A second, coarser lever exists in Terminal (Close the Online Store from Terminal, 'set to "closed" status temporarily from your in-store Terminal... without the need to access SpeedLine Portal'), and a long closure is not self-service at all: 'you can request that it be deactivated by contacting SpeedDine Support.' https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/enter-special-days.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

Consolidation exists; payout matching is explicitly disclaimed. Store Manager Help, Taxes for Marketplace Orders: 'Important Marketplace information shown in SpeedLine reports are for reference only. External factors like voids, refunds, etc., may affect these values. You must use the amounts from the source portal for tax remittance.' What SpeedLine does report is order-side: net sales by Connect source and by remote order source, a Third-Party Delivery dashboard comparing in-store deliveries with DoorDash Drive, and - added in 8.0 - 'new sections to the Sales Tax Report and the Sales Tax section of the Day Report to separate out taxes from 3rd Party Marketplaces depending on who is responsible for remitting those taxes'. No deposit-to-order matching, no commission or marketing-fee itemisation, no refund/adjustment ledger and no missing-or-unpaid-order exception list is documented in the 784-topic corpus or the 8.0 Release Notes. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/taxes-for-marketplace-orders.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

delivery-injection-error-visibility

Partial. Documented health signalling on incoming online orders: selecting 'Use Pricing from Source' automatically enables the manager alerts 'Item Price Difference >= 50%' and 'Tax Difference >= $0.10' on the SpeedLine Connect Sources General sub-tab, and Terminal 'can inform the Connect source when important events, such as changes to quoted times, activation of deferred tickets, and failed post-authorizations of deferred ticket payments, take place at the store' by calling a URL the source supplies. Shortfall: that notification runs outward to the provider, not to the operator. The Off-Site Ordering chapter documents no per-channel connection-status display, no queue or log of rejected injections and no alert when a channel stops delivering - it instead tells the operator to confirm in the Windows services list that the SpeedLine Application and Management Services are 'Started', warns that 'orders will be rejected if Terminal is shut down', and notes orders may be 'rejected during service pause' while the database backs up. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/connect_restrictions_2.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Real-time SMS or email status notifications on dispatch, with automatic updates from kitchen volume. A branded driver-tracking page on the restaurant's own domain is not documented. https://www.speedlinesolutions.com/delivery · retrieved 2026-08-01

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

delivery-promise-time

Quoted times adjust automatically from kitchen volume; LiveMaps computes return estimates from route distance and traffic; zone-level promise times configured per zone. https://www.speedlinesolutions.com/delivery · retrieved 2026-08-01

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

delivery-offline-behavior

Partial. Two delivery behaviours are explicitly tied to loss of connectivity. LiveMaps address validation offers 'Validate (Allow Skip): Select to allow staff to complete orders without address validation, if the address entered on the Customer screen is not found. This is useful if your store has frequent issues that prevent delivery address mapping, such as internet outages'. And the Terminal privilege 'Credit Card Voice Authorization' lets staff 'Enter an authorization code obtained over the phone in Terminal to allow credit card payment authorization if there is no Internet connection available.' Shortfall: neither manual makes any statement about whether cash delivery orders, driver assignment on the Dispatch screen, driver returns or driver bank settlement continue during an outage, and there is no queue-and-reconcile description; the on-premise architecture (store-local SQL database, station refresh, day-end) implies they do, but SpeedLine never says so. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/change_validation_settings.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

SpeedDine is administered as the restaurant's own site, and the SpeedLine Portal help documents it end to end. Each location gets its own address - 'Each store location will have a unique website address, or URL (Uniform Resource Locator) based on the street address and Store ID entered in the Store Info Panel' - and the Themes section sets Website Title, footer, colours, card styles and 'a custom logo or background image' so it carries the operator's brand; an Alternate Locations Page field points at the company's own site. Orders are priced by, and land in, the store's POS rather than a marketplace: in Preview, 'pricing will update if you have Terminal running on at least one station', with 'Store Pricing Request XML' and 'Store Pricing Response XML' tabs showing 'the order request sent to Terminal, and the response sent back'; out-of-stock state and menu versions sync from the store. Not documented anywhere first-party: the word commission. SpeedDine is sold as a subscription and no per-order commission is described, but SpeedLine never states a commission-free rate, so that half of the claim rests on the absence of any per-order fee in the pricing surface rather than on a stated one. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/using-the-unique-speeddine-url.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

'Online pricing, out of stock items, and coupons always match the in-store POS' — one cloud menu record drives both. https://www.speedlinesolutions.com/online-ordering · retrieved 2026-08-01

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

digital-native-app

Branded mobile app published under the restaurant's brand on the Apple App Store and Google Play. https://www.speedlinesolutions.com/online-ordering · retrieved 2026-08-01

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

Order as guest or with an account; accounts save payment info via tokenization. One-tap reorder not explicitly documented. https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01

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

Configurable Cross-Sell Prompts as a cloud-menu object, presented throughout the customer journey. No attach-rate reporting and no personalization from order history documented. https://www.speedlinesolutions.com/online-ordering · retrieved 2026-08-01

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

digital-scheduled-pacing

Order deferral up to 30 days from order time. Per-daypart capacity limits that close slots when saturated are not documented. https://www.speedlinesolutions.com/online-ordering · retrieved 2026-08-01

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

digital-fulfillment-modes

Pickup, delivery and curbside (MobilePay explicitly covers curbside) supported with delivery-specific pricing. Curbside arrival check-in and QR dine-in ordering not documented. https://www.speedlinesolutions.com/speedlinepayments · retrieved 2026-08-01

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

digital-qr-table

The one documented table/kerbside QR flow is staff-operated, not guest-facing. Ticket Print Options carries a single QR setting, 'Print SpeedLine Pay QR Code': 'The QR code will print at the bottom of tickets, and the driver or server can scan it using the SpeedLine Pay phone app to quickly transfer the ticket number and amount owing into the app.' Payment is then taken by the staff member on a 'mobile EMV chip card reader' paired to the app. The guest scans nothing. The Table Service topics (Set General Table Service Options, Build a Table Floor Plan, Assign Section or Table Numbers, Use Seats with Table Service) describe splitting and seat handling as Terminal operations under the Add Seat / Split Selections / Move Selections privileges, and SpeedDine is documented throughout as a website and branded mobile app, never as a code attaching to an open POS check. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/activate-speedline-pay.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

No first-party kiosk. Kiosk is delivered by GojiKiosk, Nextep Systems or Checkmate through SpeedLine Connect. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

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

digital-group-ordering

The SpeedDine ordering-site configuration surface is fully documented and contains no group-ordering concept. SpeedLine Portal Help enumerates it: Company Management lists every company-level setting ('Change how your ordering site looks, Change Messaging Options, Add a Company-Wide Checkout Page Message, Set a Maximum Order Amount, Choose Store Synchronization Options, Enter Company Contact Information, View Company Site URL Settings, Enter Social Media Links, Configure Order Types, View Read-Only Settings') and Store Management lists every store-level one (special days, coupon restrictions, out-of-stock sync, notices, checkout message, address, geolocation, order types, tender types, hours, closing the online store, analytics). The order-limit controls that a shared-cart feature would extend exist and are single-cart only: Set Ordering Restrictions covers 'coupons, out-of-stock, minimum and maximum order totals', and Set a Maximum Order Amount caps 'the maximum total order amount (after taxes) that will be accepted online' with an over-cap message telling the guest to phone the store - there is no per-participant cap and no second contributor. Across all 784 topics of the four manuals, the 8.0 Release Notes and the 153 support advisories there is no occurrence of group order, shared cart, order link or invite, and the marketing pages for SpeedDine describe build-your-own pizzas, half-and-half, coupons, deferred orders and a branded app only. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/set-ordering-restrictions.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

digital-catering-portal

Catering is a marketplace channel, not a native flow. SpeedLine Portal Help, on every product editor: 'For SpeedLine Marketplace customers (optional): ezCater subscribers may define products that are available on ezCater, assign dietary tags, or choose additional items to offer when the Product is ordered.' That is the whole documented surface - a per-product availability flag, dietary tags and add-on suggestions on a third-party catering marketplace. The nearest native lead-time control is generic deferred ordering, not catering-specific: a Defer Time Interval and 'Maximum Days to Defer field, type or select the maximum number of days (up to 31)'. No separate catering menu, no order minimum beyond the site-wide maximum/minimum order total, no quote or proposal step, no deposit, and no invoice, house-account or ACH terms appear in the 784-topic corpus. Retrieval note: the 'Menu Management ezCater' topic is cited from eight product topics but is not published - it is absent from the Menu Management contents list and no ezCater page resolves on the host - so the depth of the ezCater configuration cannot be read. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/add-choices-portioned-product.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read 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

Voicify, described as a leading restaurant voice-AI company, is a named certified partner integrated via SpeedLine Connect; SpeedLine markets direct integration with voice AI ordering. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

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

digital-drivethru-ai

CLAIM: AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers, with escalation-to-human handoff. VERDICT: no. NEW SURFACE (326th) - THE PUBLISHER'S OWN TOPIC MANIFEST, FETCHED TO 100%. support.speedlinesolutions.com serves five Help+Manual ('hmWebHelp') webhelp sets under /Portals/0/CustomerDocumentation_SF/. Each ships its own complete topic manifest at js/hmcontextids.js (the hmContextIds[] array). Fetched all four live sets and then crawled every in-body href to a FIXPOINT (2 rounds each, 0 new files in the last round): Store Manager (the SpeedLine POS back office) ReleaseDocs/Store_Manager_help_Web 528 topics; Menu Designer ReleaseDocs/Menu_Designer_help_Web 269; SpeedLine+ Portal (the cloud above-store portal) SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web 398; SpeedDine Admin (online ordering admin) SpeedDine/SpeedDine_Admin_help_Web 140. TOTAL 1,335 topics / 3,144,482 characters / 521,711 word tokens / 7,037 distinct tokens. The href fixpoint added only 14 files beyond the context-id manifest and all 14 were fetched, so the corpus is closed: manifest union href-fixpoint, nothing unreached. A fifth set, SpeedLineNext/SpeedLine_Next_Admin_Help_Web, is referenced by seven dead links inside Store Manager topics and is 404 for index.html, hmcontextids.js and every named topic (retired, not withheld). robots.txt on this host is a GENERIC 'User-agent: *' bar on /Portals/ that names no crawler, so it was read like a browser under the standing order; no login, no auth. This is the vendor's own product documentation = grade B. SCOPE: these four sets cover the back office (Store Manager), the menu tool, the cloud portal and the online-ordering admin - i.e. every configuration surface of the SpeedLine product. The Terminal (the POS station itself) has no separate published help set: 'terminal help' returns 0 and Terminal behaviour is documented inside Store Manager Help. BOUND + CONTROLS over all 1,335 topics: `voice ordering` 0, `voice ai` 0, `artificial intelligence` 0, `conversational` 0, `speech recognition` 0, `speech-to-text` 0, `escalation` 0. The drive-thru IS documented, and documented fully as a human lane: `drive-thru` 31 hits / `drive through` 6 - an order TYPE ('Drive-Thru: the order is given to drive-through order-takers and picked up at a drive-through window', ordertypes.htm), an outdoor Order Confirmation DISPLAY ('Add a Drive-thru Order Confirmation Display', adddrivethrudisplay.htm; assigned per station in assigncustomerdisplaystostations.htm), a security privilege ('Drive-thru Order Confirmation: access the Drive-thru Order Confirmation display settings', smsecurityprivilegesdesc.htm), and an off-site order source ('Remote Drive-Thru Order Centers', off-site_ordering.htm - staffed remote order-takers, the human alternative to lane AI). POISON: `DriveThru` also appears once as sales-import order-type code 7 (importsalesdata.htm). The vendor documents the lane it supports in detail and nowhere documents automated voice ordering in it; the 325th already established that SpeedLine's own description of its voice AI is PHONE-only. Retrieved 2026-09-18. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/ReleaseDocs/Store_Manager_help_Web/adddrivethrudisplay.htm · retrieved 2026-09-18 adversarially verified

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

digital-sms-ordering

Vendor marketing claim only. The 2026 blog post on AI ordering states 'SpeedLine with AI ordering capabilities isn't limited to phone calls. Text-based ordering gives customers another fast, convenient way to place orders, without adding work for staff', alongside 'Direct injection of structured order data into SpeedLine POS'. Shortfalls: this is grade-D marketing on a blog with no product page, no named AI/messaging provider and no integration documentation; and SpeedLine's own documented SMS facility is one-way outbound only - 'Connect Twilio for Delivery Dispatch SMS' uses the operator's own Twilio account and toll-free number so that 'when orders are assigned to drivers on the Dispatch screen, an SMS can be sent to customers letting them know their order is on its way', with companion topics for a test SMS and a delivery-confirmation SMS and no inbound handling anywhere in the 458-topic Store Manager manual. https://www.speedlinesolutions.com/blog/too-many-calls-not-enough-hands-can-ai-fix-the-high-volume-crunch · retrieved 2026-08-09

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

SpeedLine's entire Google surface is one enumerated panel and it is analytics and anti-fraud, not ordering. SpeedLine Portal Help, View Google Services Information (Company > General > Adjustable Settings > Google Services), with a field description published for every control on the screen: Enable Google reCaptcha ('will automatically analyze the activities of your customers during payment activity, and will show a captcha if they are deemed "high risk"'), 'Google Maps API Key and Google Maps Signing Secret: Credentials required to display a map to your location on the ordering site Our Store Locations page', 'Google Analytics ID', 'Google Analytics ID - External (Optional)' and 'Google Tag Manager Code'. That is the complete list. Company Management enumerates every other company-level setting - appearance, messaging, checkout message, maximum order amount, synchronization, contact info, site URL settings, social links, order types, read-only settings - and none provisions an ordering link to a Google Business Profile. Across all 784 topics of the four manuals, the 8.0 Release Notes and the 153 advisories, 'Order with Google', 'Business Profile' and 'Reserve with Google' return zero occurrences; the only other Google mentions are LiveMaps as a mapping provider, KML delivery-zone export 'into KML-compatible mapping systems, such as Google Maps', and the Google Play Store as a distribution channel for the branded SpeedDine app. The site URL is exposed for the operator to paste elsewhere ('click the copy button under SpeedDine Site URL'), which is a manual workaround, not a provisioned ordering integration. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/view-google-services-info.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read 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

SpeedLine documents no Apple integration of any kind. The SpeedLine Portal help enumerates the company-level surface in a closed list - 'Change how your ordering site looks, Change Messaging Options, Add a Company-Wide Checkout Page Message, Set a Maximum Order Amount, Choose Store Synchronization Options, Enter Company Contact Information, View Company Site URL Settings, Enter Social Media Links, Configure Order Types, View Read-Only Settings' - and the store-level surface likewise. Every place SpeedDine emits an outbound link is specified there: Enter Social Media Links ('Your customers will be taken to the social media links you have entered when they click the icons in the footer'), the Alternate Locations Page URL in the theme, and the per-store SpeedDine Site URL with a copy button for pasting into a corporate locations page. There is no place-card, custom-action or ordering-channel registration, and no Apple panel to sit beside the Google Services one. Across all 784 topics of the four manuals, the 8.0 Release Notes and the 153 support advisories, 'Apple Business Connect', 'Apple Maps' and 'place card' return zero occurrences; Apple appears only as the App Store the SpeedLine Pay app must be downloaded from and as a distribution channel for the branded SpeedDine app. An operator can of course paste the SpeedDine URL into Apple Business Connect themselves - that is a manual step the vendor neither performs nor documents. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/company-management.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read 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

SpeedLine Portal Help, Add SpeedLine Loyalty: 'SpeedLine Loyalty is a cardless single or multi-store loyalty option... Customers can install the optional app on their smartphones to check their balances or identify themselves at stores' - one account, used in store and online. In the ordering-site menu, 'In the sidebar menu, click Loyalty Rewards. A list of rewards set up on the SpeedLine Loyalty administration site appears', each mapped to a real menu item via a Linked Product ('for a "Free Small 1-Topping Pizza" reward, you would select the Pizza linked product') or left blank for free delivery, with an optional Delivery Orders Only restriction. Enrolment is in the flow, not after it: the theme's Rewards > Sign Up panel produces a prompt 'to encourage customers to sign up for the loyalty program (or sign in, if they have previously signed up for an account)', and after making the menu live 'customers who sign in with a SpeedLine Loyalty account will be able to earn points and redeem rewards'. Accrual and redemption therefore both run inside SpeedDine. Third-party programmes are supported the same way - Punchh and Paytronix each have their own Portal setup topic, and the 8.0 Release Notes track Punchh reward redemption from SpeedLine Connect orders. Prerequisite worth naming: the store side must be configured first ('the Store Manager, Loyalty, SpeedLine Loyalty tab must be configured') and SpeedLine Loyalty is a paid subscription. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/add-speedline-loyalty.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read adversarially verified

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

digital-subscriptions

Enumerated, not merely unmentioned. The SpeedLine Portal (SpeedDine admin) manual is public after all - 138 topics - and its tender-type topic lists every payment instrument the ordering site can accept: 'To add a new tender type, click the Add Tender Type link, and select the type of tender from the list: Simple Tender ... Gift Card ... Worldpay MercuryPay and Payrix/Worldpay Express ... Pay In-Store (Pickup Only) ... SpeedLine MobilePay (Delivery Only)', plus a Zero Dollar Orders type 'present by default for every store' for coupon/loyalty-free orders. There is no recurring-billing, membership or entitlement tender. The Portal's Company Management chapter (messaging, maximum order amount, maximum item quantity, store synchronization, Google services, contact info, site URL, social links, order types, card tokenization, billing-address requirement, tenant groups, read-only settings, employees, accessibility) contains no membership module, and Store Manager's welcome topic enumerates the optional add-ons as Analytics, SpeedLine Pay, SpeedDine, LiveMaps and Inventory. 'Subscription', 'membership' and 'recurring' occur zero times across the 784 dumped topics except as references to a Cloud Reporting & Analytics subscription and to loyalty-program membership. The only guest money constructs are gift certificates, gift cards, customer credits and House Accounts (invoiced charge accounts). Tokenize Customer Credit Cards for Future Orders is card-on-file, not recurring billing. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/enter-tender-types.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Coupons always match the in-store POS; a single coupon engine with restriction rules (quantity, time, minimum purchase) serves both channels. https://www.speedlinesolutions.com/online-ordering · retrieved 2026-08-01

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

SpeedLink Enterprise pushes customer data into a database the operator controls, and Customer Data dashboards exist. No published clause granting bulk export without fee or approval; SpeedLink is separately licensed. https://www.speedlinesolutions.com/hubfs/SpeedLink.pdf · retrieved 2026-08-01

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

digital-checkout-pci-sca

Quote verified word-for-word on the online-ordering page: "SpeedLine software is PA-DSS validated for PCI compliance so your customers' online transactions are always secure." PA-DSS was retired 28 Oct 2022. No PCI DSS 4.x, SSF or 3DS statement anywhere. Same evidence upholds reliability-pci-dss-4-attestation = no and commercial-pci-dss-4-controls = no. https://www.speedlinesolutions.com/online-ordering · retrieved 2026-08-01 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 surcharge engine is order-type scoped, so it does reach the digital order types: on the Tender Surcharge tab you 'select the check boxes beside the order types that will be surcharged when the selected tender type is used', choose flat rate or 'a percentage applied to the final amount (excluding tips)', and set a Caption that 'will appear on the ticket' - plus an order-type-level surcharge or discount and a separate Merchant Surcharging Guide in the Doc Viewer. Shortfalls: card-brand compliance is explicitly not handled in software - 'SpeedLine cannot detect debit-capable credit cards before they're surcharged ... Therefore, we do not recommend setting up credit card surcharging', the documented workaround being duplicate Visa Debit / MasterCard Debit / Visa Gift / MasterCard Gift tender types and asking the cardholder which they hold; and for the digital channel SpeedLine's own instruction is to avoid it - 'For online ordering, you are recommended to always use the non-surcharged tender types noted in step 9.' No jurisdiction table and no guest-facing pre-checkout disclosure on the ordering site is documented. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/add_surcharges_for_tender_type.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Unified customer profiles tracking the guest in-person, online and via delivery, and across multiple locations. https://www.speedlinesolutions.com/speedline-loyalty · retrieved 2026-08-01

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

guest-loyalty-thirdparty-identity-attach

CLAIM: orders arriving from DoorDash / Uber Eats / Grubhub attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. VERDICT: no. NEW SURFACE (326th) - THE PUBLISHER'S OWN TOPIC MANIFEST, FETCHED TO 100%. support.speedlinesolutions.com serves five Help+Manual ('hmWebHelp') webhelp sets under /Portals/0/CustomerDocumentation_SF/. Each ships its own complete topic manifest at js/hmcontextids.js (the hmContextIds[] array). Fetched all four live sets and then crawled every in-body href to a FIXPOINT (2 rounds each, 0 new files in the last round): Store Manager (the SpeedLine POS back office) ReleaseDocs/Store_Manager_help_Web 528 topics; Menu Designer ReleaseDocs/Menu_Designer_help_Web 269; SpeedLine+ Portal (the cloud above-store portal) SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web 398; SpeedDine Admin (online ordering admin) SpeedDine/SpeedDine_Admin_help_Web 140. TOTAL 1,335 topics / 3,144,482 characters / 521,711 word tokens / 7,037 distinct tokens. The href fixpoint added only 14 files beyond the context-id manifest and all 14 were fetched, so the corpus is closed: manifest union href-fixpoint, nothing unreached. A fifth set, SpeedLineNext/SpeedLine_Next_Admin_Help_Web, is referenced by seven dead links inside Store Manager topics and is 404 for index.html, hmcontextids.js and every named topic (retired, not withheld). robots.txt on this host is a GENERIC 'User-agent: *' bar on /Portals/ that names no crawler, so it was read like a browser under the standing order; no login, no auth. This is the vendor's own product documentation = grade B. SCOPE: these four sets cover the back office (Store Manager), the menu tool, the cloud portal and the online-ordering admin - i.e. every configuration surface of the SpeedLine product. The Terminal (the POS station itself) has no separate published help set: 'terminal help' returns 0 and Terminal behaviour is documented inside Store Manager Help. BOUND: the marketplace surface is documented as a closed set of 20 topics - sm/enable-speedline-marketplace.htm, sm/activate-3rd-party-delivery-se.htm, sm/taxes-for-marketplace-orders.htm, sm/indicate-tickets-assigned-to-3rd-party-drivers.htm, sp/onboarding-{doordash,grubhub,uber-eats,ezcater}.html, sp/menu-management-{doordash,grubhub,uber-eats}.html, sp/store-availability-*.html, sp/order-cancel-third-party-marketplaces.html, sp/add-3rd-party-connect-source.html and the four 'Set 3rd Party Connect Source ...' tutorial steps (`DoorDash` 115 hits). VERBATIM, the whole of what the vendor says happens to such an order: 'Orders placed on third-party marketplaces will appear in Terminal.' (enable-speedline-marketplace.htm). CONTROLS over all 1,335 topics: `customer record` 0, `guest profile` 0, `customer database` 0, `anonymous` 0, `marketplace order` 0 (the phrase appears only in the tax topic title 'Taxes for Marketplace Orders'). The Connect source configuration steps (general properties, restrictions, connections, local source certificate, notification URL) enumerate every setting a 3rd-party source has and none of them is customer matching. Where the customer file IS reached by a third party it is in the OTHER direction - activate-3rd-party-delivery-se.htm requires 'all your customer phone numbers include a valid area code' so a DoorDash Drive driver can be dispatched against an order the store already owns, which is not marketplace identity attach. Retrieved 2026-09-18. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/ReleaseDocs/Store_Manager_help_Web/enable-speedline-marketplace.htm · retrieved 2026-09-18 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

Two shipped models: bankable Points with a rewards catalog, and Stamp Cards (punch/visit). https://www.speedlinesolutions.com/speedline-loyalty · retrieved 2026-08-01

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

guest-loyalty-tiers

Tiering exists in the first-party multi-store product but not as the claim describes it. Menu Designer: 'SpeedLine's built-in loyalty program is a cardless multi-store loyalty option ... Loyalty points can be set up as multi-level, point-based rewards with differing reward earning criteria', and the vendor's launch advisory lists 'Option for Points-based system with automatic reward tiers if preferred'. Shortfalls: (a) no promotion or demotion driven by a rolling window of spend or visits is documented anywhere - the levels attach to rewards, not to guest status; (b) the program is configured by SpeedLine and head office, not by the operator ('Your SpeedLine account representative will work with your head office to put together rewards'), and the Store Manager SpeedLine tab is an image map rather than a documented field list; (c) the built-in single-store program, whose settings ARE enumerated, has no tier concept - it offers only the accumulation methods Ticket Value, Ticket Count, Product Value, Product Count and Visit-based, an Accumulation Multiplier and Initial Points. Third-party Punchh 'Points Unlock' can add tiers, but there they are 'set up with Punchh by head office'. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Menu_Designer_help_Web/integrating_speedline_loyalty.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

guest-loyalty-offline-behavior

CLAIM: documents explicitly what loyalty lookup, accrual and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). VERDICT: no. NEW SURFACE (326th) - THE PUBLISHER'S OWN TOPIC MANIFEST, FETCHED TO 100%. support.speedlinesolutions.com serves five Help+Manual ('hmWebHelp') webhelp sets under /Portals/0/CustomerDocumentation_SF/. Each ships its own complete topic manifest at js/hmcontextids.js (the hmContextIds[] array). Fetched all four live sets and then crawled every in-body href to a FIXPOINT (2 rounds each, 0 new files in the last round): Store Manager (the SpeedLine POS back office) ReleaseDocs/Store_Manager_help_Web 528 topics; Menu Designer ReleaseDocs/Menu_Designer_help_Web 269; SpeedLine+ Portal (the cloud above-store portal) SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web 398; SpeedDine Admin (online ordering admin) SpeedDine/SpeedDine_Admin_help_Web 140. TOTAL 1,335 topics / 3,144,482 characters / 521,711 word tokens / 7,037 distinct tokens. The href fixpoint added only 14 files beyond the context-id manifest and all 14 were fetched, so the corpus is closed: manifest union href-fixpoint, nothing unreached. A fifth set, SpeedLineNext/SpeedLine_Next_Admin_Help_Web, is referenced by seven dead links inside Store Manager topics and is 404 for index.html, hmcontextids.js and every named topic (retired, not withheld). robots.txt on this host is a GENERIC 'User-agent: *' bar on /Portals/ that names no crawler, so it was read like a browser under the standing order; no login, no auth. This is the vendor's own product documentation = grade B. SCOPE: these four sets cover the back office (Store Manager), the menu tool, the cloud portal and the online-ordering admin - i.e. every configuration surface of the SpeedLine product. The Terminal (the POS station itself) has no separate published help set: 'terminal help' returns 0 and Terminal behaviour is documented inside Store Manager Help. BOUND: loyalty is not a thin corner of this corpus - it is a documented chapter of 30 dedicated topics across all four sets (sm/loyalty.htm, sm/enter_loyalty_settings.htm, sm/create_loyalty_rewards.htm, sm/speedline-loyalty.htm, sm/punchh-loyalty.htm, sm/set_up_paytronix_loyalty.htm, sm/loyalty_program_speedstart_tut.htm, md/creatingacustomerloyaltyprogram.htm, md/integrating_punchh_loyalty.htm, md/integrating_paytronix_loyalty.htm, md/integrating_speedline_loyalty.htm, sd/add-punchh-loyalty.htm, sd/add-paytronix-loyalty.htm, sd/add-speedline-loyalty.htm, sp/loyalty-program-overview.html, sp/configure-punchh-loyalty.html, ... ; `loyalty` 913 hits). CONTROLS over the whole 1,335-topic corpus: `offline` 9 hits, NONE of them loyalty - 5 are 'if a printer is offline or broken' (assignanalternateprinterroute.htm and its portal twin), 1 is the manual Set Store to Online/offline switch on the ordering site, 3 are 'disconnecting SpeedLine does not make the DoorDash/Uber Eats/Grubhub store offline'. `loss of connectivity` 0, `no internet` 0, `queue and reconcile` 0; `disconnected` 3 and `reconnect` 2, all marketplace store-connection wording (POISON). Three loyalty engines are documented (SpeedLine Loyalty, Punchh, Paytronix) and for none of them is the connectivity-loss path stated. Retrieved 2026-09-18. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/ReleaseDocs/Store_Manager_help_Web/loyalty.htm · retrieved 2026-09-18 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

Coupons carry restrictions on quantity, time and minimum purchase. Explicit exclusive-vs-combinable precedence ordering is not documented. https://www.speedlinesolutions.com/point-of-sale · retrieved 2026-08-01

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

Signup, birthday/anniversary and win-back rewards are configurable triggers. A rules-based audience builder over recency/frequency/spend/items is not documented. https://www.speedlinesolutions.com/speedline-loyalty · retrieved 2026-08-01

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

guest-loyalty-rfm-segmentation

The Report Descriptions topic ('a list of all the different reports available in the Reports tab') enumerates a built-in lifecycle set under Customer: 'New Customers - Lists all of the customers who made their first purchase during the specified period'; 'Active Customers - Reports how many customers have ordered within the last 30, 60, 90 and 120 days ... Used to see how many customers are recent, versus lapsed'; 'Frequent Customers - Reports customers whose last orders were during the specified period of time and have ordered a specified number of times ... Used to identify your best customers'; 'Lazy Customers - ... Shows how many days delayed a customer is in placing an order, based on their previous pattern of ordering. Used to recover customers who may otherwise be lost to a competitor'; plus Customer Sales ('order count, total value, and average value'). SpeedLine computes the at-risk/lapsed measure itself against each guest's own ordering pattern; the operator only picks a period and threshold in the Report Options wizard. The segments drive action directly - each is available as mailing labels or export, and Terminal displays matching New Customer, Welcome Back and Frequent Customer messages at the Customer screen. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/reportdescriptions.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Ships signup rewards, birthday/anniversary rewards and win-back programs as always-on configurable campaigns, with push notifications. https://www.speedlinesolutions.com/speedline-loyalty · retrieved 2026-08-01

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

guest-loyalty-native-email-sms

Push notifications are native and order-status SMS/email exists; a native campaign email and SMS sender is not documented — Twilio is the named messaging partner. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

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

guest-loyalty-consent-management

Partial, and email-only. Consent is captured as an 'Opt-In for Email Promotions check box in the Customer screen Options window' - 'If they say "yes," record their consent' - and both 'Email Opt In' and 'Email Opt In Date' are fields on the Customer Export report, so a timestamp is retained. Mass Mail sends only 'to all the customers with e-mail addresses in your database who have given consent', with a separate 'Also Send to E-Mail Addresses Where Opt-In Status is Unknown' checkbox for non-promotional messages. Shortfalls: (a) it is one flag for one channel - the Twilio SMS facility (delivery-dispatch confirmations) has no consent field at all, so there is no per-channel consent; (b) no source-of-consent is recorded, only the date; (c) revocation is not handled by the platform - SpeedLine instructs the operator to 'comply with anti-SPAM e-mail legislation for your region ... including giving an unsubscribe option, either in the message body, or in the signature', processes no replies or unsubscribe links, and warns that managing 'mailing lists and unsubscribes' is the operator's problem when exporting to an email service. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/marketwithmassemail.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

guest-loyalty-10dlc-registration

SpeedLine neither handles nor documents A2P 10DLC registration. The end-to-end SMS setup procedure is four steps: 'If you haven't already, please create a Twilio account'; 'Under Settings, go to People then click SMS'; 'Enter the Twilio SID, Auth Token, and toll-free phone number (found in your Twilio account's dashboard)'; then send a test SMS and enable delivery-confirmation SMS. Messaging runs on the operator's own Twilio account and an unregistered-by-SpeedLine toll-free number, and the only compliance guidance given is a 160-character cost warning. No brand registration, campaign registration, use-case vetting or 10DLC mention appears in the 458-topic Store Manager manual, the 183-topic Menu Designer manual, or the vendor's /supportadvisories stream. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/connect-twilio-for-delivery-dispatch-sms.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

guest-loyalty-campaign-attribution

A Coupon & Discounts dashboard reports promotional effectiveness and coupon usage. Tying a specific campaign's redemptions to incremental check totals is not documented. https://www.speedlinesolutions.com/speedline-analytics · retrieved 2026-08-01

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

Customer data exports to an operator-controlled database via SpeedLink, and dashboards export to multiple formats. Self-serve full-list export at no cost is not documented; SpeedLink is a separate enterprise product. https://www.speedlinesolutions.com/hubfs/SpeedLink.pdf · retrieved 2026-08-01

Exposes a documented outbound guest and order event API or webhook stream that a CDP or marketing platform can subscribe to (e.g. Olo, Punchh, Bridg, Klaviyo). differentiator

guest-loyalty-cdp-event-api

An outbound EventStream API exists and is consumed by DTiQ and BeerBoard, but it is partner-gated through SpeedLine Connect with no public docs, so a CDP cannot self-serve subscribe. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

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

Tattle, a hospitality CXI platform for collecting actionable feedback, is an integrated partner. Score-based routing to private recovery vs public review sites is Tattle's function, not SpeedLine's, and is not documented. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

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

Claimed but undocumented. SpeedLine's own product advisory lists, under the Basic Loyalty program, 'Sign-up reward and referral rewards'. Shortfalls: nothing describes the mechanic - no per-guest referral code or link, no attribution of the referred guest's first order, and no two-sided reward is documented in either manual, and the /speedline-loyalty product page drops referral from its feature list altogether (points, signup rewards, stamp cards, birthday/anniversary, win-back). The Menu Designer coupon engine that implements every SpeedLine reward offers only the four wizard types Simple Discount, 2 for 1, Buy X Get Y Discounted and Value Meal, with coupon IDs and bar codes registered per-coupon rather than per-guest. Note the record's earlier reading was of SpeedLine's own customer-referral program for selling SpeedLine, which is a different thing; this is a guest-facing claim on the loyalty product. https://www.speedlinesolutions.com/supportadvisories/speedline-loyalty-is-now-available · retrieved 2026-08-09

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 offers a 'Digital Wallet' and a 'QR Code Link' as an alternative to the branded app. Apple Wallet / Google Wallet passes with push-updatable balance are not named. https://www.speedlinesolutions.com/speedline-loyalty · retrieved 2026-08-01

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

guest-loyalty-privacy-rights-tooling

The primitives exist; the workflow does not. For access: the Customer Export report emits the full per-guest record (name, address, phone, first/last order, YTD and total order counts and values, zones, CustomerID, email, Email Opt In and date, Loyalty Point Balance, birthdate). For deletion: the Terminal privilege 'Delete Customer - Delete a customer record from the Customer Options screen', plus bulk Clear Old Customer Records ('The records of all customers with no orders after this date will be marked for deletion ... Once cleared, deleted records cannot be recovered') and Delete Old Transaction Data. Shortfalls: (a) there is no request intake, verification, deadline or fulfilment log - SpeedLine's own CCPA advisory explains the 45-day disclosure duty and the deletion right, then simply inventories what SpeedLine and SpeedDine collect and states 'The information is never sold by SpeedLine', offering the operator no tooling; (b) deletion is incomplete by design - 'The original sales and transaction data in the DayFiles will not be removed'; (c) no propagation is documented to SpeedLine Loyalty's cloud, Paytronix or Punchh, which hold guest records outside the store database. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/clearoldcustomerrecords.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Real controls, incomplete against the claim. The Terminal privilege set - which enumerates every Terminal action - gates loyalty with '($) Manual Add Loyalty Points - Add SpeedLine loyalty points to a customer record using the Add button in the Loyalty window. (A maximum number of points can be set.)' and '($) Manual Redeem Loyalty Points ... (A maximum number of points can be set.)', plus 'Enroll in Loyalty Program' and 'Manually Enter Loyalty Cards'; anything beyond a privilege holder's cap needs 'Can do Manager Override'. Paytronix adds 'Require Card Number for Redeems ... Selecting this setting helps prevent loyalty coupons from being applied fraudulently'. Audit: the Loyalty Transaction Detail and Loyalty Point Balances reports, plus Coupon Usage Details, Employee Discount Details and Complimentary/Manual Discounts reports described as audit tools 'to review discounts for potential abuse'. Shortfalls: no redemption velocity or frequency limit is configurable anywhere, and nothing flags or reports employee self-redemption - the loyalty reports key on the customer, not on the employee who applied the reward. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/terminalsecurityprivilegesdesc.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Tested against SpeedLine's complete published first-party record rather than against silence. Searched all 784 topics of the four WebHelp manuals (Store Manager 458, Menu Designer 183, SpeedLine Portal 138, New Features 5), the public 8.0 Release Notes PDF printed May 2026 and running per-module to release 8.0.413, and all 153 support advisories. 'AI', 'artificial intelligence' and 'machine learning' occur zero times in the manuals and zero times in the release notes. The only AI in the advisory corpus is order-capture Voice AI ('enhanced efficiency with Voice AI ordering') and accessiBe's accessWidget for site accessibility - neither is offer generation, audience selection or send timing. Every marketing construct SpeedLine documents is operator-authored: the Menu Designer Coupon Wizard, Store Manager Mass Mail, customer lifecycle reports and manually defined loyalty rewards. The claim also requires a shipped feature rather than a roadmap statement, and the release notes are exactly that ledger; it does not contain one. Residual: reward definitions themselves live on a separate SpeedLine Loyalty administration site whose UI is not documented, but no SpeedLine channel claims an AI capability for it. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/index.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Valutec gift cards integrate directly and support mobile storage, but they are third-party stored value; linkage to the loyalty guest profile and brand-wide redemption are not documented. https://www.speedlinesolutions.com/speedlinepayments · retrieved 2026-08-01

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

Built-in time clock: employees punch in and out at the POS terminal, no separate time-clock hardware. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01

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

labor-photo-punch-verification

Identity at punch is enumerated and closed. 'The User Access Method sets the way your employees log in to access SpeedLine ... In the User Access Method area, select one of the following: Select User ID ... - or - Select Fingerprint and User ID'. That is the entire list; employees clock in by logging in to Terminal. The biometric option is a fingerprint sensor, and the docs are explicit that no image is kept ('SpeedLine POS software does not retain an image of the employee's fingerprint ... an employee's fingerprint is automatically securely deleted when his or her status is set to Terminated'). No camera capture, photo-on-punch or facial verification appears in the 458-topic Store Manager manual, in the Finger Sensors chapter, in the Time Clock topics or in the complete Terminal privilege set; the hardware SpeedLine documents adding is cash drawers, magnetic stripe readers, secure card payment hardware, printers, kitchen monitors and customer displays. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/changetheuseraccessmethod.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

Supports mobile clock-in restricted by geofence or location validation for staff who do not punch at a fixed terminal.

labor-geofenced-mobile-punch

Time punches are taken at a Terminal station. The User Access Method screen offers exactly two ways to identify an employee - 'Select User ID' or 'Select Fingerprint and User ID' - and every time-clock topic describes clocking in to Terminal (schedule-window enforcement 'when they clock in to Terminal', driver licence expiry blocking clock-in, day-end auto clock-out, the Time Clock window for time sheets and slips). Published schedules are viewable 'from the Employee Dashboard or the Time Clock window in Terminal'. The one first-party statement about a phone-based labor app runs the other way: the SpeedLine/7shifts advisory says 'Clock-in and Clock-out data from Terminal flows seamlessly into 7shifts, reducing manual entry errors'. No geofence, location validation or mobile punch appears anywhere in the 458-topic manual, and the only SpeedLine phone app documented is SpeedLine Pay, for card payment. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/changetheuseraccessmethod.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

CLAIM: records time punches while the POS is offline and reconciles them on reconnect without loss or duplicates, with the behaviour documented. VERDICT: no, on the published help (the prior pass could only reach the pre-release QA OpenAPI, which merge policy bars). NEW SURFACE (326th) - THE PUBLISHER'S OWN TOPIC MANIFEST, FETCHED TO 100%. support.speedlinesolutions.com serves five Help+Manual ('hmWebHelp') webhelp sets under /Portals/0/CustomerDocumentation_SF/. Each ships its own complete topic manifest at js/hmcontextids.js (the hmContextIds[] array). Fetched all four live sets and then crawled every in-body href to a FIXPOINT (2 rounds each, 0 new files in the last round): Store Manager (the SpeedLine POS back office) ReleaseDocs/Store_Manager_help_Web 528 topics; Menu Designer ReleaseDocs/Menu_Designer_help_Web 269; SpeedLine+ Portal (the cloud above-store portal) SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web 398; SpeedDine Admin (online ordering admin) SpeedDine/SpeedDine_Admin_help_Web 140. TOTAL 1,335 topics / 3,144,482 characters / 521,711 word tokens / 7,037 distinct tokens. The href fixpoint added only 14 files beyond the context-id manifest and all 14 were fetched, so the corpus is closed: manifest union href-fixpoint, nothing unreached. A fifth set, SpeedLineNext/SpeedLine_Next_Admin_Help_Web, is referenced by seven dead links inside Store Manager topics and is 404 for index.html, hmcontextids.js and every named topic (retired, not withheld). robots.txt on this host is a GENERIC 'User-agent: *' bar on /Portals/ that names no crawler, so it was read like a browser under the standing order; no login, no auth. This is the vendor's own product documentation = grade B. SCOPE: these four sets cover the back office (Store Manager), the menu tool, the cloud portal and the online-ordering admin - i.e. every configuration surface of the SpeedLine product. The Terminal (the POS station itself) has no separate published help set: 'terminal help' returns 0 and Terminal behaviour is documented inside Store Manager Help. BOUND: the time clock is a documented chapter, not a gap - setuptimeclockoptions.htm ('Set Time Clock Options'), monitorclockinorout.htm ('Monitor Terminal Clock-in/out Times'), Change Day End Clock-out Options, setstationconfiguration.htm ('This tab holds station clock-in and automatic log-out settings'), editemployeebankoptions.htm ('automatically opening banks on shift clock-in'), setemployeemessagingoptions.htm ('Select Clock-In to notify employees of new messages when they clock in to Terminal'); `clock in`/`clock-in` 27 hits. CONTROLS over all 1,335 topics: `offline` 9 and none is a punch (printer-offline x5, the ordering-site online/offline switch, marketplace store-offline x3); `loss of connectivity` 0, `no internet` 0, `reconcile` 0 (zero in the whole corpus, in any sense), `duplicate punch` 0. POISON MEASURED: `punchh` (the loyalty vendor) returns 184 hits and is a substring trap for `punch`; tokenised and excluding it, the single `punch` hit is 'give them our pizza punch card' (displayprintnewcustomermsg.htm), and `Punchh` (the loyalty vendor) is a homonym of `punch` that must be excluded before counting. The vendor documents the time clock in detail and never states its behaviour when the station is disconnected. Retrieved 2026-09-18. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/ReleaseDocs/Store_Manager_help_Web/setuptimeclockoptions.htm · 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

Access is set per employee, per department and per station, gating individual POS functions rather than fixed cashier/manager tiers. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01

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

labor-manager-override-audit

Manager override required to exceed configured limits, and time-clock edits retain an audit trail of changes. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01

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

The employee ebook is marketing collateral but carries product-specific, checkable statements: "The Employee Scheduling system in SpeedLine POS, for example, uses your sales forecast and recommends ideal labor targets based on historical and projected sales for the week. It even accounts for lunch and dinner peaks and forecasts by order type." Native scheduling and forecast-driven labor targets both verified; 7shifts is genuinely optional. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01 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

Schedules are built against a sales forecast derived from the store's own history, producing labor targets by daypart; Sales Forecast is a first-class exportable object in SpeedLink. https://www.speedlinesolutions.com/hubfs/SpeedLink.pdf · retrieved 2026-08-01

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

labor-realtime-labor-percent

Hourly Labor vs Sales reporting and live labor-cost tracking against sales during service, not only end-of-day. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01

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

The POS warns or blocks at clock-in when an employee would cross a configured overtime threshold, subject to manager override. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01

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 tracking and enforcement exist at the terminal. Per-state/jurisdiction rule libraries, attestation prompts and missed-break premium-pay flagging are not documented. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01

Supports predictive-scheduling ordinances by tracking advance-notice deadlines for published schedules and calculating predictability pay owed for employer-initiated changes.

labor-fair-workweek-support

Available only through a partner, and only in outline. SpeedLine's 7shifts advisory states '7shifts helps you stay compliant with built-in tools for break tracking, "Right to Rest" requirements, and Fair Work Week regulations', via 'a direct integration between SpeedLine Plus and 7shifts'. Shortfalls: it requires SpeedLine Plus plus a separate 7shifts subscription; the advisory names the regulation category without documenting advance-notice deadline tracking for published schedules or predictability-pay calculation for employer-initiated changes; and SpeedLine's own Store Manager scheduling has nothing of the kind - its compliance feature is Employee Work Restrictions, which is age-based (max hours per week, how early or late minors can work on school nights, manager alerts with an 'Advance Warning (Minutes)' before a restriction is breached), and its payroll export schemas carry no predictability-pay earnings code. https://www.speedlinesolutions.com/supportadvisories/speedline-and-7shifts-join-forces-to-optimize-your-labor · retrieved 2026-08-09

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

labor-minor-labor-rules

Ebook verbatim: "Set employee restrictions to help you manage minor employees, ensuring that you don't inadvertently schedule them or let them work in violation of your local labor codes... SpeedLine alerts managers with an override prompt when an employee is nearing or exceeding a restriction." That is an operator-configured restriction engine, not a shipped jurisdiction rule library — the operator must know and encode the local code themselves. Enforcement at schedule and clock-in is real; "minor labor rules" as a built-in capability is partial. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01 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

Rule-driven pooling exists, but through the partner. SpeedLine's 7shifts advisory: 'Managers can customize tip pool logic for equitable contribution and distribution, while 7shifts manages the funds based on SpeedLine Terminal labor data', with 'Employees can track their individual tips or tip pool earnings directly in the app'. Shortfalls: it requires SpeedLine Plus and a separate 7shifts subscription; the pool rule basis (percentage of sales, hours, points, role) is not documented in any first-party SpeedLine source; and SpeedLine's own tip handling stops well short - the 458-topic Store Manager manual covers only Limit Tip Amount Employees Can Enter, Control Tip Reporting (an estimated tip percentage with a manager override to report below it at clock-out), the Tip Details and Pay Period reports, and the Terminal privileges 'Add, Edit, Delete Tips', 'Add, Edit, Delete Additional Tips' and 'Add Tips to Employee Accounts - Add a manual tip amount to an employee account from the Manager screen', which is exactly the manual step the claim asks to be replaced. No pooling or tip-out rule exists in SpeedLine's own configuration. https://www.speedlinesolutions.com/supportadvisories/speedline-and-7shifts-join-forces-to-optimize-your-labor · retrieved 2026-08-09

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

The 'received' half is fully covered; the pool half is not. Report Descriptions: 'Pay Period - Lists a summary of shifts worked, hours, gross pay, declared tips (if the Tip Prompt setting is selected), tips included in pay (if paying tips at pay period end) ... and fees paid to drivers for each employee for the specified period'; 'Tip Details - Reports the details of all tip adjustments on tickets: ticket total, tip, and tip percentage. These totals may not always match the tip totals on the Pay Period and Time Sheet reports if employees declare cash tips at clock out that were not recorded in Terminal'; plus Time Sheet and Time Clock Edits, and every report is exportable to XLS/CSV/PDF through the Report Options wizard. Shortfalls: because SpeedLine computes no tip pool, no record of amounts contributed to or distributed from a pool exists in SpeedLine - those sit in 7shifts when that integration is used - and the docs themselves flag that declared cash tips and ticket tip adjustments will not reconcile. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/reportdescriptions.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

The export schemas are enumerated in full and do not carry what the claim requires. Legacy ADP (PREPI.csv) columns are listed exhaustively: Co Code, Batch ID, File #, Reg Hours, Reg Earnings, O/T Hours, O/T Earnings, 'Earnings 3 Code: TP (for Tip), or blank if the employee had no tips', 'Earnings 3 Amount: The employee's total tips', 'Earnings 4 Code: DF (for fees paid to driver)', Earnings 4 Amount, Temp Dept, Temp Rate. (That TP is an ADP earnings code, not W-2 Box 12 code TP.) The RUN by ADP columns are likewise listed in full - IDD, Pay Frequency, Pay Period Start/End Date, Employee ID, Pay Hours, Dollars, Separate Check, Worked in Dept, Rate Code - and carry no tips field at all; the third option is a plain SpeedLine Text shifts.txt. There is one tips total per employee, no split between cash-declared and charged tips (which the docs elsewhere say do not even reconcile), no Treasury tipped-occupation code and no Box 12 / Box 14b construct anywhere in the 458-topic manual. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/customizeexportofemployeeshifts.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Export-only. SpeedLine exports time-clock data for payroll processed elsewhere; 7shifts is the named partner for payroll. No first-party tax filing or direct deposit. https://www.speedlinesolutions.com/enterprise · retrieved 2026-08-01

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

labor-payroll-export-formats

Verbatim: "you can export your shift data to RUN by ADP® or to a custom format for fast, accurate payroll." Exactly one named provider plus a generic format — partial is the right call, and no Gusto/Paychex/QuickBooks appears anywhere. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01 adversarially verified

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

Present through the partner integration. SpeedLine's 7shifts advisory: 'Let your team swap shifts or claim open spots themselves (subject to manager approval)'; 'Employees can trade shifts, grab a shift from a shift pool, or offer theirs up'; 'Managers can seamlessly offer a sick or no-show employee's shift as an Open Shift in the Shift Pool for others to claim. The original shift remains assigned to the absent employee for attendance tracking'; 'With the 7shifts mobile app, your team can view their schedules, swap shifts, and request time off'. Shortfalls: it requires SpeedLine Plus and a separate 7shifts subscription; overtime is described as a notification ('Get notified before an employee hits overtime') rather than enforced eligibility, and role eligibility on claim is not documented; and SpeedLine's own Store Manager scheduling has no self-service path at all - the manager enters shifts and days off in the employee record, publishing only makes the schedule 'available for viewing or printing from the Employee Dashboard or the Time Clock window in Terminal', and the complete Terminal privilege set contains no swap, claim or request action. https://www.speedlinesolutions.com/supportadvisories/speedline-and-7shifts-join-forces-to-optimize-your-labor · retrieved 2026-08-09

Provides digital new-hire onboarding that collects W-4 and I-9 documentation and supports E-Verify submission.

labor-digital-onboarding-i9

SpeedLine documents the paper workflow explicitly, which is positive evidence rather than silence. Enter Employment Information instructs: 'If you have received the employee's I-9 or TD-1 form, select I-9 Received or TD-1 received.' The form is collected outside the system and the POS stores only a manager's attestation check box; the same screen's control list (Status area, I-9 Received, TD-1 received, Tax Exemption Code, Hire Date, pay card) contains no document upload, no W-4 and no E-Verify field, and the Employee Events feature illustrates the intent with the sample message 'Submit your I-9 form before beginning your shift.' W-4 and E-Verify appear nowhere in the 784 dumped topics, the 8.0 release notes or the 153 support advisories, and the only bulk path in is a generic HR XML import. The 7shifts partnership advisory - the first-party account of what that integration adds - enumerates scheduling, sales-based forecasting, real-time labor tracking, in-app messaging, shift pools, tip pooling, break/Right-to-Rest/Fair Work Week compliance and clock-in data flowing to payroll, and does not include hiring or onboarding document collection. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/enteremploymentinfo.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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 sales, item sales, category sales, discounts applied and coupon usage are all reportable by employee. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01

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

Native inventory and food-cost capability exists (an Inventory Period is a first-class exportable data object). Multi-level sub-recipes and automatic plate-cost recalculation are not documented. https://www.speedlinesolutions.com/hubfs/SpeedLink.pdf · retrieved 2026-08-01

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

inventory-unit-conversion-yields

Units of Measure: "The stocking unit may differ from the units you use to buy the item (purchase units), how you use it in recipes (usage units), or how you count it when you take inventory (count units)." Item-specific Custom Conversions carry a Multiplier field ("the number of smaller units contained in each large unit") and every conversion must be to or from the stocking unit; Global Conversions cover weight/volume units chain-wide. SHORTFALL: no yield, shrink or waste percentage is applied to a raw-to-usable conversion anywhere in the 458-topic Store Manager manual or the 183-topic Menu Designer manual - trim and spillage are handled after the fact as an Adjust for Waste batch, not as a costed yield factor on the item. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/unitsofmeasure.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Inventory is periodized with usage and food cost reported, implying a theoretical-vs-actual comparison, but no variance report in units and currency is documented. https://www.speedlinesolutions.com/hubfs/SpeedLink.pdf · retrieved 2026-08-01

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

Items can be marked out of stock in the POS and that state propagates, but ingredient-level near-real-time depletion driven by modifier selection is not documented. https://www.speedlinesolutions.com/hubfs/SpeedLine-Marketplace-Brochure.pdf · retrieved 2026-08-01

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

inventory-86-auto-sync

Propagation is documented; the automatic trigger is documented not to exist. The 86 itself is a manual act: Activate Out-of-stock Menu Restrictions describes limiting 'items or modifiers that have been marked as out of stock using the Out of Stock button on the Terminal User screen'. It then propagates - the SpeedLine Portal's Synchronize Out of Stock with Store setting makes 'regular checks for items that have been marked out of stock on the Terminal User screen at the store, and show out of stock status on the ordering site' (with a company-level equivalent and a Clear Out of Stock button), and marketplace propagation is claimed only in marketing ('Easily mark items out of stock or change business hours, and updates are reflected across all connected platforms'), not in the manuals. At order time an out-of-stock item is also caught: 'when an online order submitted through SpeedDine or SpeedLine Connect contains out of stock items or modifiers, SpeedDine (or the third-party Connect provider, if they support this feature) will inform the customer.' Shortfall, now positively evidenced rather than merely unfound: the complete field description sets for Inventory Options (General tab) and for stock item settings contain no par level, reorder point or availability threshold, and SpeedLine Inventory is a periodic posted-batch system - Track Stock 'post[s] ideal usage of the item and show[s] expected stock levels on inventory reports' - so nothing links a depleted ingredient to an 86. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/synchronize-out-of-stock.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Count Stock Items: a count batch is populated with Add Item, Add Count Category, Add Item Category, Add All Items or "Add Critical Items: Select to add only those stock items designated as critical items (usually more expensive or theft-prone items)" - so a full physical count and an ad-hoc subset spot count are both supported. Posted batches are kept as history (Batch Summary and Transaction Details reports list posted Count, Receive, ideal-usage and adjust/transfer batches by date, employee and value). SHORTFALL: no scheduled or recurring cycle-count function is documented, and "Inventory only allows one open (unposted) count" at a time. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/countingstockitems.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Count Stock Items documents the entire counting procedure: "Print a Count List. The Count List is a worksheet used when physically counting your stock items. These stock counts are then entered into Inventory", then "Take physical inventory of your stock items and record quantities on the count list you printed", then "For each item you counted, click the Count Quantity field and enter the physical count you recorded on the count list." Counting is paper-and-keyboard in the Store Manager Windows back office. The only bar-code scanning documented in either manual is coupon redemption (Menu Designer Register a Coupon Bar Code); stock items carry a product look-up number but no scan-to-count path. Offline tolerance is moot - Store Manager is on-premise - but there is no mobile or tablet counting app to sync. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/countingstockitems.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Electronic Supplier Integration: "The topics below apply to SourceLink, an electronic ordering and receiving system from McLane Foodservice Distribution. Once SourceLink is integrated, stock receives from McLane can be imported into Store Manager Inventory." SourceLink supplies items.dat, "a 'dictionary' of the stock items available from SourceLink", plus receipt.dat per order, with Auto Post Receiving. Add an Electronic Supplier: "In the Electronic Supplier list, select McLane if that is your supplier, or if your supplier is integrated via packing slip files, for example Sysco or Agar, select Other." SHORTFALLS: (1) the Sysco/Agar route is a published XML .psf spec, not a pre-built connector - "some development effort is required in order to convert the format of the supplier's file to match the format required by SpeedLine"; (2) it is inbound only. Purchase orders are printed to send to the supplier, and the only PO export is a binary .pof file created at day end that "is typically used to send order information to a corporate head office" via SpeedLink - not transmitted to the distributor. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/supplierspecific.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Receive Stock Items, step 3: "Select a source for the received items: Select A pre-existing Purchase Order... Select A Supplier... Select An Import File received from a Supplier to receive from an electronic import or packing slip file." The import file is a structured feed, not a scanned document: the Packing Slip File (.psf) Formatting Guide specifies "a document declaration, followed by 18 elements" (SupplierName, InvoiceDate, InvoiceNumber, SupplierPartNumber, SupplierReceiveUOMName, Quantity, TotalPrice, PerUnitPrice and the rest), and McLane SourceLink supplies items.dat/receipt.dat. Line-item extraction from a photo, PDF or emailed invoice is not offered; unmatched lines land in an Unknown Items list for manual correction. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/receive_from_a_supplier_or_pur.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Every receive line records Quantity, Unit and Per Unit Price with Total Value calculated, so purchase price history accumulates per item per supplier; Set Costing Method offers First In First Out ("a new cost on product received will not affect the cost of any old product still in stock"), Weighted Average Cost and Standard Cost, and Set Purchase Order Options offers "Use Last Posted Cost For New Purchase Orders" so the buyer sees the previous price. The Receipt Summary report totals purchases by supplier and period and Transaction Details lists every posted batch line. SHORTFALL: no price-change alert. The only warning on the Purchase Orders options tab is "Warn About Missing Critical Items", and the complete Inventory report list (inventory_report_descriptions.htm) contains no price-variance or contract-price report - a buyer must eyeball the last posted cost. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/receive_from_a_supplier_or_pur.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Set Target Stock Quantity: "In the Target Stock Quantity field, type or select the quantity of stock (in the item's stocking unit) you would like to keep on hand. This quantity, along with the quantity currently in stock and the quantity on any purchase orders completed but not yet received, will be used to calculate a suggested quantity to order on the Purchase Order screen." Par is per stock item in a store's own database, so it is inherently per location. SHORTFALL: the par is static. No mode generates order quantities from a sales forecast - the forecast engine in Store Manager feeds Operations Planning / Prep Planning (advance food prep) and labour scheduling, and the Prep Variance report compares forecast prep to actual sales; neither touches purchase orders. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/set_target_stock_quantity.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

inventory-waste-logging

Adjust and Transfer Stock: "Adjust for Waste: This feature is used to decrease the stock levels to account for waste. It allows for a short note describing how the waste happened, such as 'dropped on floor.'" The batch records the posting employee and type and can be filtered by Type, Employee or Reference. Interpret the Usage Variance Report keeps waste distinct from variance: "End = start + receives +or- count +or- adjust - adjust waste - transfer - ideal usage", with "Adjust Waste: The sum of all waste adjustments for the item during the report period" as its own column, and actual usage computed with the waste adjustment added back. SHORTFALL: no reason-code list. The reason is typed prose in the Reference field, so waste cannot be grouped or reported by cause - unlike voids and comps, which do have maintained reason lists (Change Void Reason List, Change Pay or Comp Reasons). https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/adjusttransferstock.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

Supports inter-location inventory transfers as a two-sided transaction crediting the sending location and debiting the receiving location, with an in-transit or approval state.

inventory-transfers

Adjust and Transfer Stock: "Transfer: Enter a number to decrease the stock quantities for a transfer to another store. For example, if you transferred nine bottles of wine to another location, you would enter '9'. You can enter a short note describing the reason for the transfer and identifying the location that received the items." The counterparty side is explicitly manual and unlinked: "Hint If you are receiving stock that was transferred to your store from another store, use a receive batch to adjust your stock levels." SHORTFALLS: the destination store is free text in the Reference field rather than a selected location; the credit and the debit are two unconnected batches in two separate store databases; and there is no in-transit or approval state - a transfer posts immediately and is rejected outright if it would drive stock negative. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/adjusttransferstock.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

Supports a commissary/central kitchen model where one location produces prep items and issues or sells them to other locations at a computed transfer cost.

inventory-commissary

Stock can be moved between stores with a Transfer batch, valued at the item's cost under the store's costing method (FIFO, weighted average or standard), and prepped items can be modelled: Menu Designer's Prep Items wizard and Prep Parts feed Store Manager's Prep Planning, which forecasts how much of each prep item to make in advance. SHORTFALLS: production is planned per store, not issued from one store to others - the Prep Variance report compares a store's forecast prep plan to its own item sales. There is no commissary or central-kitchen entity, no production order that converts ingredients into a finished prep stock item for issue, no transfer price distinct from cost, and no inter-store billing or statement. The transfer itself is one-sided free text (see inventory-transfers). https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/adjusttransferstock.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

Captures lot/batch numbers at receiving and links them through production to sales or transfers, enabling a backward and forward recall trace.

inventory-lot-traceability

The Packing Slip File (.psf) Formatting Guide is a published schema - "a document declaration, followed by 18 elements" - and the per-item elements are exactly SupplierItemName, SupplierPartNumber, SupplierReceiveUOMName, Quantity, TotalPrice and PerUnitPrice. No lot, batch, pack date or country-of-origin field exists. Manual receiving matches: on all three add-paths in Receive Stock Items the receiver enters only "the Quantity, Unit, and Per Unit Price for each item." Stock is tracked as a quantity of a stock item under FIFO, weighted-average or standard costing, not as identified lots, and the Inventory report list (self-described as the reports available in Store Manager) offers no forward or backward trace. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/packing_slip_file__psf_format.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

inventory_report_descriptions.htm lists the Inventory reports available in Store Manager - Batch Details, Stock Item Definitions, Suppliers, Purchase Order Summary, Purchase Order, Count List, Negative Stock, Receipt Summary, Stock Valuation, Interim Inventory, Usage Variance, Transaction Details, Batch Summary, Product Margin - and reportdescriptions.htm says of the Reports tab "Below is a list of all the different reports available." Neither list contains an expiry, shelf-life or expiring-soon report. No date-of-expiry field appears on the receive line, in the 18-element packing-slip schema or on the Stock Items tabs (General, Purchasing, Suppliers, Count Units, Custom Conversions). Expiration dates in SpeedLine attach to menu-item availability (Menu Designer effective/expiration dates), coupons, customer credits and driver licence/insurance - never to stock. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/inventory_report_descriptions.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

inventory-bar-partial-bottle

Add Stock Counting Units: count units beyond the stocking unit are added per item and selected while taking stock, and the Inventory setup tutorial states the purpose outright - "This can make it easier to account for partial units. For example, there may be 10 unopened cans of pineapple on the shelf, along with the partial contents of a can in a container in the cooler or on the prep table. If you have added count units of both 'can' and 'ounce,' the stock taker can weigh the partial contents to get a more accurate count." With a stocking unit of bottle and a custom conversion to ounces, a partial bottle is counted as a fraction of its contents, and the count line shows the conversion. SHORTFALLS: no scale is integrated - the manuals document no scale device anywhere (Station Options hardware covers cash drawers, mag-stripe readers, EMV PIN pads, printers, customer displays and kitchen monitors), so weights are read off a bench scale and typed in; and there is no bar-specific pour or bottle-fraction tooling, this is the generic count-unit mechanism. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/addstockcountingunits.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

inventory-cogs-gl-export

Restaurant365 is a native accounting/operations integration and SpeedLink pushes Inventory Period data to the operator's database. QuickBooks, Sage Intacct and NetSuite are not named, and per-category GL mapping is not documented. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

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

inventory-native-not-partner

Native inventory and food-cost functions exist, but SpeedLine actively markets WookAI for inventory management and Restaurant365 for costing/accounting, indicating the native module is not considered sufficient on its own. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

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

Inventory Report Descriptions, Product Margin: "lists the profit margin on items in the categories you specify, based on the cost of ingredients and item pricing. When you run the wizard for this report, you select a DayFile to analyze." It requires Track Usage Costs on the Inventory Options General tab, Archive for Reporting plus Include Sales Mix Tickets on the End of Day Day File tab, and a sales mix defined in Menu Designer with Add Sales Mix Tickets at Day End - so actual sold mix, actual ingredient cost and menu price are joined per item. Menu Designer's Sales Mix additionally re-prices a past DayFile to model margin before a price change. SHORTFALL: it is a run-on-demand report, not a monitor. No configurable margin threshold and no alert on ingredient-cost movement exists in either manual; the only threshold-triggered notification SpeedLine publishes is Pulse Alerts in the separately sold Cloud Reporting & Analytics product, whose documented metrics are sales, voids, delivery times and store hours rather than item margin. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/inventory_report_descriptions.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Confirmed capability, but the specific figure "data available within 15 minutes of the transaction" is not in the cited FAQ or on the analytics page, which says only "near real-time reporting". The FAQ's 5-minute figure I did retrieve applies to cloud menu/settings changes going live, not reporting latency — the researcher appears to have crossed the two. Drop the 15-minute number. https://www.speedlinesolutions.com/speedline-analytics · retrieved 2026-08-01 adversarially verified

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

reporting-eod-closeout

Day Reports plus Today/Yesterday dashboards and bank/cash reporting reconcile the day in one document. https://www.speedlinesolutions.com/point-of-sale · retrieved 2026-08-01

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

Menu item analysis and item sales reporting (including by employee) exist and filter by time. Modifier-level PMIX is not documented. https://www.speedlinesolutions.com/speedline-analytics · retrieved 2026-08-01

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

reporting-comps-voids-audit

Employee Discounts, Coupons & Discounts and a 'Notable Activity' dashboard cover the exception surface. Voids and price overrides attributed to both applier and approving manager, with reason codes, are not documented. https://www.speedlinesolutions.com/speedline-analytics · retrieved 2026-08-01

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

Bank account and cash reporting exist in the analytics report tree. An explicit per-drawer, per-shift, per-employee over/short figure is not documented. https://www.speedlinesolutions.com/speedline-analytics · retrieved 2026-08-01

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

Hourly Labor vs Sales, labor cost as a percentage of sales, and per-employee labor reporting driven by the built-in time clock. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01

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

reporting-server-scorecards

Per-employee item sales, category sales, discounts and coupon usage. Average check, items per check and tips as a percentage of sales are not documented. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01

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

reporting-channel-profitability

Revenue splits by channel; margin does not. Report Descriptions defines Remote Order Sales Summary - 'Reports the net sales from each Connect source (e.g., SpeedDine, or Chowly) over the specified period of time. For third-party order aggregators like Chowly and ItsaCheckmate, includes the name of order source (e.g., GrubHub) if it was sent by the aggregator' - plus Remote Order Discounts on the same basis, Hourly Order Type Sales for dine-in/pickup/delivery, and Delivery Performance. Non-integrated marketplaces are captured by naming Remote Order Sources on the DEFAULT station and selecting Prompt for Remote Order Source, so 'the recorded order sources will appear in reports'. Marketplace tax is separated as of 8.0: 'Introduced new sections to the Sales Tax Report and the Sales Tax section of the Day Report to separate out taxes from 3rd Party Marketplaces depending on who is responsible for remitting those taxes.' Shortfall: the only margin report in the enumeration is Product Margin, which 'Lists the margin on products in specified item categories, based on ingredient cost and product price' - by item category, not by channel - and no report nets marketplace commission. Commission appears in first-party material once, as a pricing lever rather than a reporting one: 'Markup Flexibility: Increase pricing for each delivery service to help recover commission costs directly from the SpeedLine Portal.' https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/reportdescriptions.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

Provides a consolidated multi-location report with side-by-side location comparison and drill-down from group total to a single location and then to an individual transaction. differentiator

reporting-multiloc-drilldown

Store Comparison dashboard combining all locations; FAQ states side-by-side comparison of 2 to 100+ locations. https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01

Includes a self-service report builder letting a non-developer choose dimensions, measures, and filters and save the result, rather than only fixed canned reports. differentiator

reporting-custom-report-builder

Dashboards carry customizable metrics and filters by location/time/sales, and SpeedLink enables custom reporting — but SpeedLink's path is SQL against an exported database, which is a developer task, not a non-developer builder. https://www.speedlinesolutions.com/hubfs/SpeedLink.pdf · retrieved 2026-08-01

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

Email notifications and scheduled recurring report delivery are documented features of Cloud Reporting & Analytics. https://www.speedlinesolutions.com/speedline-analytics · retrieved 2026-08-01

Offers automated recurring bulk export of transaction-level raw data to a customer-controlled destination (S3, SFTP, Snowflake, BigQuery, or equivalent), not just manual CSV download. differentiator

reporting-raw-warehouse-export

SpeedLink Enterprise pushes scheduled data files — DayFile transaction detail, Employee Info, Inventory Period, Sales Forecast — into a SQL Server the customer controls. Genuine customer-owned destination, but a separately licensed enterprise product. https://www.speedlinesolutions.com/hubfs/SpeedLink.pdf · retrieved 2026-08-01

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

reporting-public-api

No public REST or GraphQL API. SpeedLine Connect is a partner-gated XML-over-TCP socket to the on-prem store server; credentials require a vendor engagement and the knowledge base is login-gated. https://www.speedlinesolutions.com/hubfs/SpeedLine%20Connect%20Flyer.pdf · retrieved 2026-08-01

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

An outbound EventStream feed exists (used by DTiQ and BeerBoard) but is not documented as a customer-supplied endpoint webhook, and no retry or signature behavior is published. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

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

SpeedLine's integration material references a third-party integration support and maintenance fee, and requires a specified SonicWALL appliance at the store. SpeedLink Enterprise is a separately licensed product. https://www.speedlinesolutions.com/hubfs/SpeedLine%20Connect%20Flyer.pdf · retrieved 2026-08-01

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

Report Descriptions is the complete in-store catalogue - "Below is a list of all the different reports available in the Reports tab" - and it carries no tier or SKU annotation. It includes the labour side (Pay Period, Time Sheet, Time Clock Edits, Minimum Wage Shortfall, plus a Labor vs Sales graph and report with its own customization topic), product mix (Sales By Item, Sales by Category, Modifier Usage, Sizes Sold, Hourly Item Sales), and the comps/voids audit set (Voided Tickets, Voided Items, Complimentary Discounts, Manual Discounts, Employee Discount Details). SHORTFALL: every one of those runs against a single store's database. Multi-location comparison is a separate purchase - SpeedLine Cloud Reporting & Analytics "combines data from all locations running the SpeedLine POS to compare performance in a single view" and is sold with its own sign-up and sales contact, SpeedLink Enterprise "pulls sales, employee payroll, customer, delivery and inventory data from your stores and consolidates it", and even head-office setting administration needs the Above Store add-on. The gating is by module, not by plan tier: SpeedLine publishes no plan tiers at all. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/reportdescriptions.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

SpeedLine publishes the number. The Cloud Reporting & Analytics Enhancements advisory of 2 June 2026 says the platform 'now supports extended data retention beyond the previous three-year limit for specific reports' and that 'we removed the three-year data cap exclusively for these key reports: Employee Item Sales, Pay Period, Pay Period Details, Ticket Details ... You can now access unlimited historical data through these specific reports.' So the floor for every report is three years - well past the 24-month bar - and ticket-level detail (Ticket Details) is uncapped, queryable in the reporting UI by calendar or custom date range. The cap is stated, not silent, and no archive-retrieval fee is mentioned. On-premise reporting has no cap at all: reports run over an operator-chosen date range against the store's own SQL database and DayFile archive, and every removal is an explicit operator action (Delete Old Transaction Data by an Older Than date, Delete Old Shift Data, Purge Old Schedules), with the manual advising 'only one or two years of transaction data is required for reports' rather than enforcing a limit. Friction worth knowing: to see past three years on the four extended reports, 'stores must re-transmit older Day Files to populate the new extended history. Contact SpeedLine Support to get started.' https://www.speedlinesolutions.com/supportadvisories/speedline-cloud-reporting-analytics-enhancements · retrieved 2026-08-09

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

Capability confirmed verbatim on the analytics page: "Set up email notifications for almost any dashboard metric that are triggered when a custom threshold is met." However the product name "Pulse Alerts" does not appear anywhere on the cited page. Strip the branding — it looks invented. https://www.speedlinesolutions.com/speedline-analytics · retrieved 2026-08-01 adversarially verified

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

Report Descriptions states "Below is a list of all the different reports available in the Reports tab" and every entry is a named, parameterised report; Run the Report Options Wizard documents the only way to vary one (sort options, date ranges, category/group selections). There is no free-form or natural-language query path. The separately sold SpeedLine Cloud Reporting & Analytics publishes five capability areas - Real-Time Reporting, All Locations Reporting, Intuitive Dashboards, Pulse Alerts ("email notifications for almost any dashboard metric ... triggered when a custom threshold is met") and Email Notifications - none of which is a question-answering assistant, and the current release notes for SpeedLine 8.0 list only Tattle survey integration, Ingenico Moby/5500 support and extra Deferred Tickets List columns. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/reportdescriptions.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

A Customer Data dashboard and customer reporting exist. New-vs-returning counts, visit frequency and lifetime-spend cohorts are not documented. https://www.speedlinesolutions.com/speedline-analytics · retrieved 2026-08-01

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

A Sales Forecast is a first-class object — exported as its own SpeedLink data file and consumed by the labor scheduling workflow. https://www.speedlinesolutions.com/hubfs/SpeedLink.pdf · retrieved 2026-08-01

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

reporting-tip-tax-compliance

Payroll side: Pay Period "Lists a summary of shifts worked, hours, gross pay, declared tips (if the Tip Prompt setting is selected), tips included in pay (if paying tips at pay period end)"; Tip Details "Reports the details of all tip adjustments on tickets: ticket total, tip, and tip percentage. These totals may not always match the tip totals on the Pay Period and Time Sheet reports if employees declare cash tips at clock out that were not recorded in Terminal" - i.e. declared versus charged is explicitly reconcilable. Control Tip Reporting drives the declaration: a per-department Tip % estimate shown in the Tips to Report window at clock out, the Allow Tip Reporting Less Than Recorded switch, and an Override Reporting of Tips Below Estimate privilege. Also Minimum Wage Shortfall for tip-credit exposure. Tax side: Sales Tax "Lists and totals all taxes collected", Tax Exempt Sales, with tax items and tax groups configured per jurisdiction and Apply Taxes by Delivery Location for delivery-address-based rates. SHORTFALL: no tip pool. Neither manual documents a pooling, tip-share or tip-out function - the only pooling reference is advice to switch on the tip prompt for cooks "if your employees share tips" - so no pool distribution detail exists. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/reportdescriptions.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Menus and reporting operate at chain-wide, regional and store levels — three tiers in practice. Not documented as a first-class object that permissions scope to. https://www.speedlinesolutions.com/enterprise · retrieved 2026-08-01

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

'Package and push updates to store POS systems' from a corporate master menu in one action. https://www.speedlinesolutions.com/enterprise · retrieved 2026-08-01

Corporate menu items expose per-field override rules so a location can change some attributes (e.g. price, availability) while corporate locks others (e.g. name, image, recipe), and locked fields are not editable at store level. differentiator

multi-location-local-override-policy

Master menu 'standardize[s] offerings while allowing for regional or store-level differences'. Per-field lock/override governance is not documented. https://www.speedlinesolutions.com/enterprise · retrieved 2026-08-01

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

multi-location-price-zones

One item record, several price nodes - the manuals document each axis. Location: 'The Store Groups tab in the menu root allows a head office to list a store or group of stores that may have different menus from each other ... store groups can be assigned to any menu node', and Create Alternate Pricing states 'If you want to change pricing based on location, the best method is to create Store Groups in your menu, and then assign the groups to price nodes.' Daypart: time-and-day-based Price Groups are defined with per-weekday Start Time and End Time ranges and 'Terminal will use the alternate price node automatically during the days and times specified' (happy hour, Wing Wednesdays); customer-based Price Groups cover VIP and organisation rates on the same mechanism. Channel: Create Order Type Specific Pricing - 'Price nodes can be set to apply only when a certain order type is used ... you can price items differently for each order type method (for example, delivery, take out)', selected from the Order Type list on the price node. For SpeedLine Plus the Portal adds an explicit price hierarchy: 'If you are setting up the most common pricing across all of your stores, Select All Stores from the Group / Store list. The global pricing can be overridden at the lower store group and individual store levels at a later time.' Nothing duplicates the item; the price node is the unit. Weaker leg: per-marketplace price books are claimed only in marketing ('Increase pricing for each delivery service ... directly from the SpeedLine Portal') and are not in any manual. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Menu_Designer_help_Web/storegroupstab.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

Menu, price, and promo changes can be scheduled to activate at a future date/time interpreted in each target location's own timezone, and can be rolled back after activation. differentiator

multi-location-scheduled-publish

Timed automatic price activation and pre-publish preview exist. Per-target-timezone interpretation and post-activation rollback are not documented. https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01

A new location can be provisioned by cloning a documented configuration template (menu, taxes, roles, printers, modifiers, tenders) rather than being configured from scratch, and the vendor publishes the expected time-to-open. differentiator

multi-location-new-store-template

Multi-Store Administration: "A Setting Update Package is a series of Store Manager settings contained in one file. After the package is saved or published, it can be distributed to one or more stores. When the package is implemented at the stores, those settings are transferred to the local copy of Store Manager." Create a Setting Update Package: "Most settings can be selected in Store Manager and packaged in a Binary Setting Update Package (.sup) file, which can then be sent to your franchise stores", drawn from the Settings groups (Money - tax items and groups, tender types; Hardware - printer setup, station options; People - employee options; Orders - order types) with documented dependency ordering (Order Types depends on Printer Setup; Tax Groups depends on Tax Items; Stock Items depends on Item Categories, Suppliers, Units of Measure). Store Profiles let head office load an existing store's settings as the starting point, and Menu Designer Store Groups scope one master menu to the new location. SHORTFALL: no published time-to-open. Nothing in the manuals or on www.speedlinesolutions.com states how long provisioning a new location takes, and packages are not a one-click clone - they are hand-assembled per settings area, warned to be tested first, and delivered by SpeedLink, FTP, email or USB. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/multi-storeadministration.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

The permission model distinguishes a franchisor/corporate tenant from an independently-owned franchisee tenant, so corporate can see franchisee sales and enforce config while the franchisee owns its own employees, banking, and labor data. differentiator

multi-location-corp-vs-franchisee-roles

Payroll and time-clock data can be managed 'at individual stores or from head office', implying a split. A distinct franchisor vs independently-owned-franchisee tenancy model is not documented. https://www.speedlinesolutions.com/enterprise · retrieved 2026-08-01

Calculates franchise royalty, ad-fund, and marketing-fee amounts automatically from POS net sales on a defined schedule, with a configurable royalty basis (gross vs net of discounts/comps/third-party). differentiator

multi-location-royalty-calculation

CLAIM: automatic royalty / ad-fund / marketing-fee calculation from POS net sales on a schedule, with a configurable basis. VERDICT: no. NEW SURFACE (326th) - THE PUBLISHER'S OWN TOPIC MANIFEST, FETCHED TO 100%. support.speedlinesolutions.com serves five Help+Manual ('hmWebHelp') webhelp sets under /Portals/0/CustomerDocumentation_SF/. Each ships its own complete topic manifest at js/hmcontextids.js (the hmContextIds[] array). Fetched all four live sets and then crawled every in-body href to a FIXPOINT (2 rounds each, 0 new files in the last round): Store Manager (the SpeedLine POS back office) ReleaseDocs/Store_Manager_help_Web 528 topics; Menu Designer ReleaseDocs/Menu_Designer_help_Web 269; SpeedLine+ Portal (the cloud above-store portal) SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web 398; SpeedDine Admin (online ordering admin) SpeedDine/SpeedDine_Admin_help_Web 140. TOTAL 1,335 topics / 3,144,482 characters / 521,711 word tokens / 7,037 distinct tokens. The href fixpoint added only 14 files beyond the context-id manifest and all 14 were fetched, so the corpus is closed: manifest union href-fixpoint, nothing unreached. A fifth set, SpeedLineNext/SpeedLine_Next_Admin_Help_Web, is referenced by seven dead links inside Store Manager topics and is 404 for index.html, hmcontextids.js and every named topic (retired, not withheld). robots.txt on this host is a GENERIC 'User-agent: *' bar on /Portals/ that names no crawler, so it was read like a browser under the standing order; no login, no auth. This is the vendor's own product documentation = grade B. SCOPE: these four sets cover the back office (Store Manager), the menu tool, the cloud portal and the online-ordering admin - i.e. every configuration surface of the SpeedLine product. The Terminal (the POS station itself) has no separate published help set: 'terminal help' returns 0 and Terminal behaviour is documented inside Store Manager Help. BOUND + CONTROLS (tokenised, word-boundary, case-insensitive, over all 1,335 topics / 521,711 tokens): `royalty` 0, `royalties` 0, `franchisee` 0, `franchisor` 0, `ad fund` 0, `marketing fee` 0. THE INFORMATIVE CONTROL: `franchise` is NOT zero - 6 hits, and every one is a real franchise FEATURE that is not a fee. Verbatim: 'Above Store, an add-on component of Store Manager, is a tool for managing Store Manager settings across a franchise that may have stores in different regions with varying settings' (installabovestore.htm); 'Setting Update Packages allow you to package Store Manager settings or data into files that can be sent to your franchise stores' (createsettingupdatepackages.htm); 'Allow Head Office Access ... to access this store's data in SpeedLine Analytics' (sp/enable-head-office-access.html and sd/allow-head-office-access.htm); 'Allow cards that have been saved to other stores in the franchise' (sd/tokenize-customer-credit-cards.htm). So SpeedLine DOES ship franchise tooling - settings distribution, head-office reporting access, cross-store card tokens - and inside that documented franchise feature set there is no fee, basis, schedule or statement object at all. That makes this an enumeration absence rather than a silence: the vendor's franchise chapter is complete and royalty is not in it. It supersedes the prior 'this is a marketing corpus and bounds nothing' note - the denominator is now the publisher's own manifest. Retrieved 2026-09-18. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web/index.html · retrieved 2026-09-18 adversarially verified

Supports automated ACH/debit collection of calculated royalties and fees from franchisee accounts, with a franchisee-visible statement of what was charged.

multi-location-royalty-collection

CLAIM: automated ACH/debit collection of calculated royalties and fees from franchisee accounts with a franchisee-visible statement. VERDICT: no. NEW SURFACE (326th) - THE PUBLISHER'S OWN TOPIC MANIFEST, FETCHED TO 100%. support.speedlinesolutions.com serves five Help+Manual ('hmWebHelp') webhelp sets under /Portals/0/CustomerDocumentation_SF/. Each ships its own complete topic manifest at js/hmcontextids.js (the hmContextIds[] array). Fetched all four live sets and then crawled every in-body href to a FIXPOINT (2 rounds each, 0 new files in the last round): Store Manager (the SpeedLine POS back office) ReleaseDocs/Store_Manager_help_Web 528 topics; Menu Designer ReleaseDocs/Menu_Designer_help_Web 269; SpeedLine+ Portal (the cloud above-store portal) SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web 398; SpeedDine Admin (online ordering admin) SpeedDine/SpeedDine_Admin_help_Web 140. TOTAL 1,335 topics / 3,144,482 characters / 521,711 word tokens / 7,037 distinct tokens. The href fixpoint added only 14 files beyond the context-id manifest and all 14 were fetched, so the corpus is closed: manifest union href-fixpoint, nothing unreached. A fifth set, SpeedLineNext/SpeedLine_Next_Admin_Help_Web, is referenced by seven dead links inside Store Manager topics and is 404 for index.html, hmcontextids.js and every named topic (retired, not withheld). robots.txt on this host is a GENERIC 'User-agent: *' bar on /Portals/ that names no crawler, so it was read like a browser under the standing order; no login, no auth. This is the vendor's own product documentation = grade B. SCOPE: these four sets cover the back office (Store Manager), the menu tool, the cloud portal and the online-ordering admin - i.e. every configuration surface of the SpeedLine product. The Terminal (the POS station itself) has no separate published help set: 'terminal help' returns 0 and Terminal behaviour is documented inside Store Manager Help. BOUND + CONTROLS over all 1,335 topics: `royalty` 0, `royalties` 0, `franchisee` 0, `ach` 0, `direct debit` 0, `sweep` 0. POISON: `statement` returns 6 hits, all poison - 4 are the House Account Statement report ('A presentation quality statement that can be sent to customers', reportdescriptions.htm and sp/report-definitions.html), 2 are Bing Maps' 'Privacy Statement'; none is a franchisee fee statement. The franchise tooling that DOES exist (Above Store settings distribution, head-office access to Analytics - quoted at multi-location-royalty-calculation) moves configuration and reporting rights, never money. There is no money-movement object of any kind between corporate and stores in the back office or the cloud portal; the only funds flows documented are card processing (Worldpay/Vantiv, Monetra), store banks and pay-ins/pay-outs. Collection cannot exist where the calculation does not (see multi-location-royalty-calculation). Retrieved 2026-09-18. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web/index.html · retrieved 2026-09-18 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

Chain-wide reports aggregating sales, labor, discounts and item mix, with a Store Comparison dashboard across 2 to 100+ locations. https://www.speedlinesolutions.com/enterprise · retrieved 2026-08-01

Item-level sales roll up across locations under a shared corporate item ID even when stores have renamed or locally priced the item. differentiator

multi-location-normalized-item-rollup

Menu Designer Store Groups: "The Store Groups tab in the menu root allows a head office to list a store or group of stores that may have different menus from each other. These groups then appear in menu nodes so you can restrict menu elements to groups of stores, or to individual store locations", with the store's group set in Store Manager under System > Store Information. Price nodes carry Store Group scoping - "If you want to change pricing based on location, the best method is to create Store Groups in your menu, and then assign the groups to price nodes" - so a chain item exists once, under one PLU, priced differently per location rather than duplicated per store; PLUs are edited centrally and Store Manager warns that running panels from two menus at once breaks if PLUs collide. SHORTFALL: the roll-up. Store Manager's complete report catalogue is single-store, and consolidation is only asserted on marketing pages for separately sold products - SpeedLink Enterprise "pulls sales, employee payroll, customer, delivery and inventory data from your stores and consolidates it for easy daily reporting", Cloud Reporting & Analytics "combines data from all locations ... to compare performance in a single view" with "templated reports". Neither publishes an item-level consolidated report or any name-normalisation behaviour, and a store that renames or reprices locally is outside the master-menu model rather than reconciled by it. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Menu_Designer_help_Web/storegroupstab.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Enter Gift Card Settings: integrated gift cards are activated per store by selecting a Processor Interface, and the balance lives on the processor network - "If you are using end-to-end encryption (E2EE), in order to read gift cards with an EMV PIN pad swipe, you must be processing both credit and gift cards through the same processor network (for example, Worldpay with StoreCard, or First Data with ValueLink)". Terminal privileges cover activating cards, adding value (each with a maximum) and voiding same-day activations, receipts can print the remaining Card Balance, and up to 10 cards can be activated in one transaction. Because the balance is processor-held rather than in the store database, redemption at any store on the same merchant account follows from the processor, not from SpeedLine. SHORTFALLS: SpeedLine publishes nothing about brand-wide redemption; its complete report catalogue has an Open Credits and a House Account Balances report for those liabilities but no gift card outstanding-liability report; and no inter-store settlement or reconciliation between owners is documented anywhere in the 458-topic manual. The earlier note in this record attributing the cards to Valutec is not supported - the manuals name Worldpay StoreCard, First Data ValueLink and Monetra. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/entergiftcardsettings.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

multi-location-cross-location-loyalty

Loyalty explicitly offers unified customer profiles and multi-location management, so one profile and balance spans the brand. https://www.speedlinesolutions.com/speedline-loyalty · retrieved 2026-08-01

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

multi-location-multi-brand

Activate a New Menu or Panel: menus built in Menu Designer are selected panel-by-panel for Terminal, and "Caution Using panels from more than one menu at a time is possible, but will cause errors if the menus contain the same PLUs or Coupon IDs" - so a second brand's menu can run on the same terminal provided its PLUs and coupon IDs are disjoint, with panel order and a preferred panel controlling the Terminal menu buttons. SHORTFALLS: SpeedLine models no brand or concept object. Receipt content and branding are configured per ticket format and per order type (Format Printed Tickets, Set Content of Tickets for Order Types), not per brand, so the two brands share one receipt identity unless they are also separated by order type. Revenue is separable only indirectly, by item category, menu panel or order type - the report catalogue has Sales by Category and Hourly Order Type Sales but no per-brand revenue report. The vendor markets to "multi-concept restaurant chains" but publishes no virtual-brand feature, and a store's Store Groups field takes a single group. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/activatenewmenu.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Automates multiple tax rates and tax exemptions per location. Jurisdiction-specific rules such as prepared-food vs grocery and inclusive-vs-exclusive handling are not documented. https://www.speedlinesolutions.com/point-of-sale · retrieved 2026-08-01

Produces an immutable audit log of who changed which configuration object (price, tax, permission, discount) at which location and when, exportable or queryable by corporate. differentiator

multi-location-config-audit-log

CLAIM: immutable audit log of who changed which configuration object (price, tax, permission, discount) at which location and when, exportable or queryable by corporate. VERDICT: no - and this time on the PRODUCTION, published surface rather than the QA OpenAPI the prior pass had to disqualify. NEW SURFACE (326th) - THE PUBLISHER'S OWN TOPIC MANIFEST, FETCHED TO 100%. support.speedlinesolutions.com serves five Help+Manual ('hmWebHelp') webhelp sets under /Portals/0/CustomerDocumentation_SF/. Each ships its own complete topic manifest at js/hmcontextids.js (the hmContextIds[] array). Fetched all four live sets and then crawled every in-body href to a FIXPOINT (2 rounds each, 0 new files in the last round): Store Manager (the SpeedLine POS back office) ReleaseDocs/Store_Manager_help_Web 528 topics; Menu Designer ReleaseDocs/Menu_Designer_help_Web 269; SpeedLine+ Portal (the cloud above-store portal) SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web 398; SpeedDine Admin (online ordering admin) SpeedDine/SpeedDine_Admin_help_Web 140. TOTAL 1,335 topics / 3,144,482 characters / 521,711 word tokens / 7,037 distinct tokens. The href fixpoint added only 14 files beyond the context-id manifest and all 14 were fetched, so the corpus is closed: manifest union href-fixpoint, nothing unreached. A fifth set, SpeedLineNext/SpeedLine_Next_Admin_Help_Web, is referenced by seven dead links inside Store Manager topics and is 404 for index.html, hmcontextids.js and every named topic (retired, not withheld). robots.txt on this host is a GENERIC 'User-agent: *' bar on /Portals/ that names no crawler, so it was read like a browser under the standing order; no login, no auth. This is the vendor's own product documentation = grade B. SCOPE: these four sets cover the back office (Store Manager), the menu tool, the cloud portal and the online-ordering admin - i.e. every configuration surface of the SpeedLine product. The Terminal (the POS station itself) has no separate published help set: 'terminal help' returns 0 and Terminal behaviour is documented inside Store Manager Help. BOUND + CONTROLS over all 1,335 topics: `audit log` 0, `audit trail` 0, `change log` 0, `changelog` 0, `who changed` 0, `activity log` 0, `event log` 0, `tamper` 0, `immutable` 0, `revision history` 0, `changelog` 0, `track changes` 0, `user activity` 0, `who made` 0. SECOND POISON: `history` returns 25 hits and every one is SALES history (sales forecasting, customer order history, importing sales history from a previous POS), never configuration history. POISON NAMED: `audit` returns 10 hits and every one is a report-usage phrase, not a log - 'Used to audit cash handling activity' (Pay-Out Details report, reportdescriptions.htm) and 'Used as an audit tool to review discounts for potential abuse' (Discounts by Employee report, sp/report-definitions.html); a sales report is not a configuration change record. The full security-privilege enumeration (smsecurityprivilegesdesc.htm) lists every privilege in Store Manager and contains no log/history/audit privilege. The 1,335-topic set IS the configuration surface of the product, so its silence is an enumeration absence. Retrieved 2026-09-18. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/ReleaseDocs/Store_Manager_help_Web/index.htm · retrieved 2026-09-18 adversarially verified

Publishes a documented multi-location API (or data warehouse/BI export) that returns transaction-level data across all locations in one authenticated call, without per-location credentials. differentiator

multi-location-enterprise-api

SpeedLink Enterprise consolidates all stores' data into one customer-controlled database, which serves the use case — but by scheduled file push, not a single authenticated multi-location API call. https://www.speedlinesolutions.com/hubfs/SpeedLink.pdf · retrieved 2026-08-01

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

Overtime, break and minor-labor rules are enforced at the terminal, not merely reported. Configuration per location group from head office is not documented. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01

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

Runs on Windows PC terminals plus Android/iOS tablets, and the FAQ says the team assesses whether a buyer's existing hardware can be reused — implying non-proprietary. SpeedLine also sells hardware through its own store. No published statement that the operator may freely source terminals elsewhere. https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01

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

hardware-os-platforms

Named operating systems, withheld device specs. SpeedLine's support advisories enumerate the Windows versions it supports on POS stations: an end-of-support advisory lists 'other non-server Windows operating systems SpeedLine currently supports' as Windows Embedded POSReady 7, Windows 8.1 Professional and Windows 8.1 Embedded Industry Pro (alongside Windows 7 and Windows Embedded Standard 7 as then-supported), the Windows 10 Pro advisory of 14 Aug 2025 covers Windows 10 Pro and Enterprise and the Windows 11 upgrade path and exempts Posiflex terminals with extended lifecycles, and a Worldpay EMV advisory sets a hard floor: 'All stations with EMV devices must be running Windows 10 or higher ... Posiflex stations running Windows 10 IoT 2016 or higher will remain supported through October 2026.' Client-side, SpeedLine Pay ships as an app for 'both the Apple and Android versions', SpeedDine is a mobile-web site with an installable web-app icon for 'the desktop of Apple or Android devices', and SpeedLine Portal / Cloud Reporting are browser-based. Shortfall: minimum OS versions per component and device specs are in 'the SpeedLine Minimum Requirements and Supported Hardware document, available on the Customer Support web site as a PDF, in the Knowledge Base, or from SpeedLine Support' - the Store Manager help says so twice and gives no public link; probed 2026-08-09 and it is behind the customer login. Withdrawn from the previous note: a Capterra deployment listing, which source policy forbids as evidence for a capability claim. https://www.speedlinesolutions.com/supportadvisories/microsoft-ends-support-for-windows-10 · retrieved 2026-08-09

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 mobile offering is a tablet or phone running MobilePay with a Bluetooth card reader and Bluetooth printer — an accessory pairing, not a purpose-built handheld. No drop rating or IP ingress rating published. https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01

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

hardware-handheld-battery-swap

Re-checked against the complete public corpus: 784 topics across the four support.speedlinesolutions.com manuals (Store Manager 458, Menu Designer 183, SpeedDine/Portal Admin 138, New Features 5), the public 8.0 Release Notes PDF, all 153 support advisories, and the 574-URL www.speedlinesolutions.com sitemap. No battery chemistry, hot-swap, charging or rated shift-life statement appears anywhere. supportedhardware.htm is the manual's own hardware-specification topic and defers entirely: "Minimum requirements and supported hardware change regularly and are subject to change without notice. For the most up-to-date information, please see the SpeedLine Minimum Requirements and Supported Hardware document, available on the Customer Support web site as a PDF, in the Knowledge Base, or from SpeedLine Support." I probed five candidate public paths for that PDF under support.speedlinesolutions.com/portals/0/ on 2026-08-09 and none resolved; the Knowledge Base and /Store both require a Customer Site account. Devices are named only incidentally and without power specifications - Dynamic Quest tablets with a built-in ID TECH MiniSmart reader, the Ingenico Link/2500 mobile PIN pad paired to a Windows tablet over Bluetooth on a virtual COM port, and the Ingenico Moby/5500 for the SpeedLine Pay app ("compact design that fits in your pocket", PCI PTS V6) with no battery data. Battery behaviour is a property of the third-party tablet and SpeedLine states nothing about it either way. || 325th: NEW CONTROL (325th), cell NOT moved, and the reason it cannot move in either direction is now measured rather than assumed: SpeedLine appears to ship no handheld of its own for a battery spec to attach to. Tokenised controls over the 46 text-extracted PDFs of the hubfs document library (the whole library the 324th took to completion): `batter` 0 of 46 - no rated battery life, no hot-swap, no spare-pack claim anywhere; `handheld` 1 of 46 and that hit is not a POS terminal but an accessory, 'inexpensive handheld reader, allows you to...' in SpeedLine-Brochure.pdf; `iPad` 0 of 46. What the library does document as the mobile surface is third-party consumer hardware the operator supplies: the SpeedLine Pay / MobilePay app 'available on Apple and Android devices, paired with a mobile EMV card reader', and WhatsNewInSL73-R300.pdf's 'Terminal can prompt order takers for the order source when transcribing orders from a 3rd-party tablet.' Per merge policy a claim the product does not implement at all is held unknown with a note rather than published as `no`, and a brochure set is not a hardware catalogue, so no `no` is proposed. What would settle it: a SpeedLine hardware price list or spec sheet - the only two hardware sheets the library holds are PIN pads (Lane 3600/7000, Link 2500), neither of them a handheld POS. Retrieved 2026-09-17. || 326th: NEW CONTROL (326th) over a new and bounded corpus. NEW SURFACE (326th) - THE PUBLISHER'S OWN TOPIC MANIFEST, FETCHED TO 100%. support.speedlinesolutions.com serves five Help+Manual ('hmWebHelp') webhelp sets under /Portals/0/CustomerDocumentation_SF/. Each ships its own complete topic manifest at js/hmcontextids.js (the hmContextIds[] array). Fetched all four live sets and then crawled every in-body href to a FIXPOINT (2 rounds each, 0 new files in the last round): Store Manager (the SpeedLine POS back office) ReleaseDocs/Store_Manager_help_Web 528 topics; Menu Designer ReleaseDocs/Menu_Designer_help_Web 269; SpeedLine+ Portal (the cloud above-store portal) SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web 398; SpeedDine Admin (online ordering admin) SpeedDine/SpeedDine_Admin_help_Web 140. TOTAL 1,335 topics / 3,144,482 characters / 521,711 word tokens / 7,037 distinct tokens. The href fixpoint added only 14 files beyond the context-id manifest and all 14 were fetched, so the corpus is closed: manifest union href-fixpoint, nothing unreached. A fifth set, SpeedLineNext/SpeedLine_Next_Admin_Help_Web, is referenced by seven dead links inside Store Manager topics and is 404 for index.html, hmcontextids.js and every named topic (retired, not withheld). robots.txt on this host is a GENERIC 'User-agent: *' bar on /Portals/ that names no crawler, so it was read like a browser under the standing order; no login, no auth. This is the vendor's own product documentation = grade B. SCOPE: these four sets cover the back office (Store Manager), the menu tool, the cloud portal and the online-ordering admin - i.e. every configuration surface of the SpeedLine product. The Terminal (the POS station itself) has no separate published help set: 'terminal help' returns 0 and Terminal behaviour is documented inside Store Manager Help. CONTROLS: `handheld` 0, `hand-held` 0, `battery` 0, `charging` 0, `dock` 0 across all 1,335 topics; `tablet` 11 hits, all of them the Windows tablet form factor of a normal station. The complete configuration manual of the product therefore contains no handheld device object at all, which corroborates the 325th's finding that SpeedLine ships no handheld of its own for a battery specification to attach to. Cell cannot move in either direction: a claim about a device the product does not have is held unknown, not `no`. Retrieved 2026-09-18. || 327th: NEW SURFACE (327th): the HubSpot site-search index swept for hardware vocabulary over the whole public site. 'battery' returns exactly 2 pages and 'swappable battery' the same 2; BOTH are UPS/power-protection prose, not a device battery - /pos-quotes-comparing-apples-to-apples ('Other protective hardware includes battery backups and surge protectors ... uninterrupted power supply (UPS) and battery backup ... the printers should be connected to a battery backup') and /blog/prepare-your-restaurant-for-emergencies. POISON NAMED: 'battery' in this vendor's vocabulary means UPS battery backup, 100% of the time; any count run without reading the bodies would be a false positive. 'hot-swappable' scores 31 only because the HubSpot index treats the phrase as OR over 'hot' and 'swappable' (top hits are '5-hottest-dietary-trends', 'dog-days-of-summer'). Still unknown: SpeedLine ships no vendor-branded handheld whose battery could be field-replaceable, so the surface that would answer the claim does not exist in its catalogue. Retrieved 2026-09-18. 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

SpeedLine's Minimum Requirements and Supported Hardware PDF is public (fetched anonymously at 200 from the www host on 2026-09-15, not login-gated as an earlier pass recorded) and has now been read. Its cellular content covers two things, neither of them the POS handheld: the store's WAN, where a Digi 6310-DX cellular extender paired with a SonicWall router is recommended "so that payment cards can continue to be accepted in the case of internet connection failure" (already scored at reliability-cellular-backup, partial/B on this same document); and the payment-only companion app triPOS Mobile / SpeedLine Pay, for which "An active built-in cellular connection with cellular data plan" is the stated minimum requirement rather than a Wi-Fi fallback, and which cannot enter an order at all (its workflow starts from a ticket already rung and printed at the POS). The handheld that runs the POS is a Windows tablet (Surface Go 2, Surface Pro 7, or any device meeting IEEE 802.11ac) whose stated requirement is "A secured wireless connection"; no SIM, cellular or dual-WAN option appears for it. That is silence about the failure mode the claim names, not a positive declination, so the cell stays unknown. || 323rd: NEW (323rd): two live product sheets for the mobile device state its cellular behaviour in the vendor's own words. https://www.speedlinesolutions.com/hubfs/SpeedLine-MobilePay-Brochure.pdf (HTTP 200, 1,218,694 B) and https://www.speedlinesolutions.com/hubfs/SpeedLine-Pay-Brochure.pdf: "Payments are accepted securely with the SpeedLine MobilePay app, available on Apple and Android devices, paired* with a mobile EMV card reader" / "*Card readers are to be paired only with cellular devices on the same operating system (iOS or Android) as initially paired"; and "No cell reception? No problem! Continue to take payments if cellular reception is lost: 'store and forward' mode securely stores the customer's payment card information, and then sends it when the connection is restored" (the SpeedLine Pay wording adds "and then sends it to WorldPay when the connection is restored"). So the vendor requires a CELLULAR device for its handheld and its documented resilience story is store-and-forward for LOST cellular, not cellular failover for lost Wi-Fi. TOKENISED CONTROLS over the 46-PDF library (38,077 tokens): `LTE` 0, `cellular` 4 (all four quoted or duplicated above), `failover` 0, `hotspot` 0. The handheld in question also remains payment-only - no order-entry handheld exists in the line - so the claim's Wi-Fi-drop fallback is not merely unevidenced, it is not the scenario SpeedLine documents. Retrieved 2026-09-17. || 325th: MERGE HOLD (proposed partial/C, held unknown): the handheld is the operator own phone paired with a card reader, and the Wi-Fi-to-cellular fallback conjunct is inferred from the device class rather than stated; grade C marketing. The agent flagged it as its weakest row. PROPOSAL AS WRITTEN: CLAIM: 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. VERDICT: partial. SHORTFALL NAMED: SpeedLine's handheld is not a vendor device at all - it is the operator's own Apple or Android phone running the SpeedLine Pay / MobilePay app paired to a Bluetooth EMV reader - and while the vendor documents that the pairing requires a CELLULAR device and documents what happens when cellular reception is lost, it nowhere states that cellular is a fallback for store Wi-Fi, and it publishes no cellular failover for the POS terminals themselves. EVIDENCE, both live at 200 today on the permitted hubfs host: 'Payments are accepted securely with the SpeedLine Pay app, available on Apple and Android devices, paired* with a mobile EMV card reader' and the footnote '*Card readers are to be paired only with cellular devices on the same operating system (iOS or Android) as initially paired' (https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/SpeedLine-Pay-Brochure.pdf, 1,809,708 bytes). The same brochure documents the loss-of-cellular behaviour under the heading 'No cell reception? No problem!': 'Continue to take payments if cellular reception is lost: "store and forward" mode securely stores the customer's payment card information, and then sends it to [the processor] when the connection is restored.' The MobilePay brochure (https://www.speedlinesolutions.com/hubfs/SpeedLine-MobilePay-Brochure.pdf, 1,218,694 bytes) carries the same two statements verbatim. So the cellular half of the claim is affirmatively documented and the offline-resilience half is documented as store-and-forward; the Wi-Fi-failover conjunct is not, which is why this is partial and not yes. POISON RECORDED: an untokenised case-insensitive search for `LTE` over the 46 SpeedLine PDF texts returns 9 files and every single hit is the substring inside ALTERNATIVE ('As an alternative to SpeedLine's cloud reporting...'); tokenised `\bLTE\b` is 0 of 46. Retrieved 2026-09-17. || 327th: NEW SURFACE (327th), and it WEAKENS the partial that was held at merge in the 325th: swept over the bounded public site via the HubSpot `_hcms/search` index, 'LTE' returns 1 page, '4G' the same 1 page, 'cellular' 1 unrelated page, 'hotspot' 0. The single LTE page is an OPERATOR INTERVIEW about the customer's own store network, not about a SpeedLine handheld: 'Travis: We have a 4G LTE fail over on most of our stores. So for online order connections, credit card processing, and invoice service, that's all backed up, with caller ID.' That is a store-level WAN failover installed by the franchisee, and it is a third-party arrangement. The vendor publishes no statement that a handheld (the SpeedLine Pay app runs on the operator's own phone) supports cellular as a documented Wi-Fi fallback. Retrieved 2026-09-18. adversarially verified

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

hardware-offline-mode

FAQ confirms local copies are maintained and the system continues working when the internet disconnects. No explicit statement of which functions degrade (card auth, loyalty, refunds). https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01

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

hardware-kds

First-party kitchen displays with Make Routes station routing, speed-of-service monitoring and rush-item prioritization; QSR Automations exists as an optional alternative, not a dependency. https://www.speedlinesolutions.com/quick-service-and-fast-casual · retrieved 2026-08-01

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

hardware-kiosk

No first-party kiosk in either form factor. GojiKiosk, Nextep Systems and Checkmate supply kiosks through SpeedLine Connect. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

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

hardware-drive-thru

Tablet-based drive-thru displays and customer-facing displays with product images are offered. Outdoor digital menu boards, order confirmation displays, headset integration and timer measurement are not documented. https://www.speedlinesolutions.com/quick-service-and-fast-casual · retrieved 2026-08-01

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

Kitchen/make-ticket printing and Bluetooth mobile printers are documented, and the architecture is standard Windows POS, but no multi-manufacturer ESC/POS compatibility list is published publicly (the hardware store is login-gated). https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01

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

Cash drawer/bank reporting, customer-facing displays and caller-ID hardware are documented. Barcode scanners, by-weight scales and a published compatibility list are not. https://www.speedlinesolutions.com/quick-service-and-fast-casual · retrieved 2026-08-01

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

hardware-p2pe-terminal

EMV PIN pads with end-to-end encryption are used for card entry, and SaferPayments is bundled to help with PCI. Neither a validated P2PE listing nor the resulting merchant SAQ type is stated. https://www.speedlinesolutions.com/speedlinepayments · retrieved 2026-08-01

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

hardware-tap-to-phone

Add Secure Card Payment Hardware is the complete secure-entry configuration surface: "On the sidebar, click Hardware, and then click Station Options... Click the Secure Card Entry tab. In the Device Type list, select the make and model of secure entry device you are using", then a COM Port - with worked hints for Verifone (COM9), Ingenico (COM8), the Bluetooth-paired Ingenico Link/2500 mobile PIN pad and the ID TECH MiniSmart built into Dynamic Quest tablets. The mobile path is no different: Activate SpeedLine Pay states "Payments are processed using a mobile app that communicates securely with a mobile EMV chip card reader, and with the Worldpay Express online server" - the app scans a QR code off the ticket and drives a separate reader. The current release notes (SpeedLine 8.0) add "Support of Ingenico Moby/5500", another external reader. No softPOS, Tap to Pay on iPhone or Tap to Pay on Android capability is documented in either manual or in the release notes. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/add_secure_card_payment_hardware.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

hardware-pricing-transparency

SpeedLine runs its own hardware store at support.speedlinesolutions.com/Store, but it is behind a customer login, so no SKU prices are public. https://support.speedlinesolutions.com/Home · retrieved 2026-08-01

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

hardware-ownership-vs-lease

SpeedLine states the ownership model directly in its support advisories. Microsoft Ends Support for Windows 10: "All Dell computers purchased from SpeedLine in 2020 or later, should be eligible for the free Windows 11 upgrade from Microsoft. Self-supplied computers will be dependent on the manufacturers hardware" - so stations are bought outright from SpeedLine, and an operator may also supply its own. Upcoming Worldpay Cipher Removal: "Hardware Replacement: If your hardware cannot support Windows 10 or higher, new stations are available at our online store or by emailing aftermarketsales@speedlinesolutions.com." The MSD contactless advisory tells operators to "purchase new iPP320 EMV PIN pads through the SpeedLine Customer Online Store". An older Windows advisory tells operators to "Assess the age and condition of your hardware... check with your hardware vendor", which is the language of an owned asset. No lease, rental or subscription-bundled hardware programme appears in the 784 topics of the four support.speedlinesolutions.com manuals, the 153 support advisories, or the 574-URL www.speedlinesolutions.com sitemap. The catalogue and prices in the online store are behind the Customer Site login, so unit prices are not readable, but the purchase-vs-lease question the claim asks is settled. https://www.speedlinesolutions.com/supportadvisories/microsoft-ends-support-for-windows-10 · retrieved 2026-08-09

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

CLAIM: vendor DOCUMENTATION confirms whether hardware purchased from the vendor remains usable with other software after cancellation. VERDICT: no - the documentation makes no such statement either way. BOUND: the 1,335-topic Help+Manual census plus the bounded public site (HubSpot `_hcms/search` 219 URLs, subset of the 589-URL sitemap). CONTROLS, tokenised: over the docs, 'warranty' 1 hit and it is about a barcode SENSOR cleaning warning ('Using glass cleaner ... may invalidate the warranty'), not a hardware programme; 'resell' 0 site-wide; 'unlock' 8 site hits, none about hardware; 'buy out' returns only fuzzy multi-word noise. The vendor's own hardware guidance page /pos-quotes-comparing-apples-to-apples discusses brand-name hardware and manufacturer warranties ('brand-name hardware components ... typically come with better warranties') and the /support-services page advertises an 'Online hardware & software store', but neither states any post-cancellation right. NOTE the product is Windows-PC based, so third-party reuse is physically plausible - but the claim asks for a DOCUMENTED confirmation and there is none in a bounded corpus. Retrieved 2026-09-18. https://www.speedlinesolutions.com/pos-quotes-comparing-apples-to-apples · retrieved 2026-09-18 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

One published warranty term exists, for one device. The WorldPay Update Removes MSD Contactless Payments advisory (SpeedLine Support, Apr 4 2022) lists the advantages of upgrading to the Ingenico Lane 3000 as "Faster transaction processing times; Supports EMV contactless and NFC payments; Optional 3-year advanced exchange warranty; Lane 3000 is designed to provide long-term encryption capabilities; Is P2PE certified when using Worldpay Express", and directs buyers to the After Market Sales team. SHORTFALLS: the term is optional, purchasable and specific to one PIN pad model, not a programme covering hardware bought from SpeedLine generally; no replacement turnaround is stated anywhere (the only turnaround figure SpeedLine publishes is for PIN pad key re-injection - "approximately 3 weeks"); and www.speedlinesolutions.com/support-services enumerates the whole support offering (Remote Support Services, Support Services, Customer Support Website, Premiere Support, Store Management Services, Second-Level Support, "unlimited phone and email support and SpeedLine software upgrades") with no hardware warranty, depot swap or advance exchange in it. Checked across the 574-URL sitemap, all 153 support advisories and the 784 topics of the four support.speedlinesolutions.com manuals; general warranty terms would sit with the order in the login-gated online store. https://www.speedlinesolutions.com/supportadvisories/worldpay-update-removes-msd-contactless-payments · retrieved 2026-08-09

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

hardware-byod

MobilePay runs on tablets and phones, which makes BYOD physically possible, but no documented BYOD permission or security model exists. https://www.speedlinesolutions.com/speedlinepayments · retrieved 2026-08-01

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

Software updates deploy automatically overnight and complete before store open, and support performs encrypted remote takeover of terminals. A device console showing each terminal/printer/KDS online-offline with remote reboot and staged rollout is not documented. https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01

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

hardware-callerid-integration

Caller ID integration recognizes the customer on an inbound call and surfaces their record and order history at the POS — a signature SpeedLine phone-order feature. https://www.speedlinesolutions.com/delivery · retrieved 2026-08-01

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

extensibility-public-api-docs

No self-serve API reference exists. Integration is described only in a marketing flyer that directs prospective partners to contact SpeedLine, and the entire knowledge base requires a login. https://www.speedlinesolutions.com/hubfs/SpeedLine%20Connect%20Flyer.pdf · retrieved 2026-08-01

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

extensibility-api-access-cost

Fee is real — flyer: "A third-party integration support and maintenance fee will apply to customers using third-party ordering services, when not using SpeedDine and SpeedLine Marketplace." BUT two dossier characterizations are wrong and repeat across api_posture, best_at and vs_reference: (1) the fee is conditional — it does not apply to operators on SpeedDine/Marketplace; (2) the SonicWALL is NOT mandated. The flyer says "The preferred way of achieving this is to use a SonicWALL..." and "It is recommended that you purchase the SonicWALL security appliance from SpeedLine", framed as PCI guida https://www.speedlinesolutions.com/hubfs/SpeedLine%20Connect%20Flyer.pdf · retrieved 2026-08-01 adversarially verified

The vendor publishes its partner/marketplace commercial terms (referral fee, revenue share percentage, or per-location partner fee) in public documentation.

extensibility-partner-revshare

The Technology Partners page is SpeedLine's partner programme surface and it publishes a directory, not terms: "We also offer a wide range of integrations with other industry-leading providers", followed by a per-partner list (accessiBe, DoorDash Drive, QSR Automations, Tattle, Twilio, Voicify, 7shifts, Onosys, ezCater, Skip, DoorDash, Grubhub, Uber Eats) with a one-line description each and a "Schedule a Call" button. No referral fee, revenue-share percentage or per-location partner fee appears there, on /integrations or /speedline-marketplace, in the 26 PDFs linked from /guides-and-brochures, anywhere in the 574-URL sitemap, in the 784 topics of the four support.speedlinesolutions.com manuals, in the public 8.0 Release Notes, or in any of the 153 support advisories - the only commercial percentage in the whole corpus is the operator's own third-party markup lever ("Increase pricing for each delivery service to help recover commission costs directly from the SpeedLine Portal"). There is no partner or developer portal to hold such terms: api./developers./docs./help.speedlinesolutions.com do not resolve and support.speedlinesolutions.com/llms.txt 404s. The programme's published route to commercial terms is a sales call. https://www.speedlinesolutions.com/partners · retrieved 2026-08-09

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

extensibility-free-sandbox

The documentation names both developer on-ramps and neither is a free sandbox. (1) EventStream: "An EventStream SDK that includes event and XML structure information, testing utilities, and XML samples is available to developers and IT staff who want to develop in-house security applications. For more information about EventStream and its capabilities, please contact your SpeedLine Sales Representative." The SDK is handed out by sales, is scoped to in-house applications for an existing installation, and is not a hosted environment with seeded data. (2) SpeedLine Connect: the Add a 3rd Party Connect Source tutorial's target is the operator's own production store - "Typically, you need to collect and forward the following information to your new Connect Provider: The SpeedLine menu file. The External TLS certificate you created. The password for the TLS certificate (communicated securely). The IP address and port number used for the source connection" - with the store's Terminal listening on a port and optionally restricted to the provider's static IP. A developer without a paid production store has nothing to point at. No sandbox, test tenant or demo environment appears in the 784 topics of the four manuals, the 8.0 Release Notes, the 153 support advisories or the 574-URL sitemap, and there is no developer host to serve one: api./developers./docs./help.speedlinesolutions.com do not resolve and support.speedlinesolutions.com/llms.txt 404s. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/integrate_video_surveillance.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Upheld, with one factual correction to the note. Auth is not purely "network-perimeter based": the flyer's architecture diagram legends "Mutually-Authenticated SSL" alongside "Incoming connections restricted by IP Address filtering". Still no OAuth, no operator-granted revocable scopes, no self-serve credentials — the score stands, the mechanism description should be corrected. https://www.speedlinesolutions.com/hubfs/SpeedLine%20Connect%20Flyer.pdf · retrieved 2026-08-01 adversarially verified

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

extensibility-webhooks-push

An EventStream outbound feed exists and is consumed by video-surveillance and beverage partners, but the primary Connect transport is request/response and no customer-configurable event push is documented. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

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

Set URL for Notifications of Connect Store Changes is the complete notification mechanism, and its complete control set is a single field: "In the Web Service Address field, enter the URL supplied by the Connect provider." "Terminal can inform the Connect source when important events, such as changes to quoted times, activation of deferred tickets, and failed post-authorizations of deferred ticket payments, take place at the store. The source is notified when Terminal calls a URL provided by the source. The notification can be performed using a HTTP or HTTPS request." There is no signing secret, no HMAC, no retry or backoff setting and no event log or replay facility on the screen; authentication of the channel is by mutual TLS certificates generated in tutorial steps 5 and 6, and integrity of the payload is by XSD validation ("Validate Request XML" / "Validate Response XML", with a manager alert for "Incoming XML validation errors... could indicate... that the message is not coming from your Connect provider, and could be malicious"). The documented answer to missed deliveries is a pull, not a redelivery: "Upon notification that events have occurred, the host should send a Store Info Request or Ticket Request message to the store to get the details of the changes made." HTTP is permitted as well as HTTPS. The Connect/OrderLink Gateway message specification is distributed to providers and is not published, so a provider-side retry may exist privately, but nothing signed, retried or replayable is published. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/set_url_for_notifications.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Strongly supported by the flyer itself rather than the partners page: "With SpeedLine Connect, your SpeedLine POS can accept and process orders from virtually any external third party ordering system", listing self-serve kiosks, external call centers, internet ordering websites, third-party aggregators, remote drive-thru order centers and automated telephone order services. Partner-gated but genuine. https://www.speedlinesolutions.com/hubfs/SpeedLine%20Connect%20Flyer.pdf · retrieved 2026-08-01 adversarially verified

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

extensibility-menu-write-api

CLAIM: menu items/modifiers/prices writable via API. VERDICT: unknown (unchanged). NEW SURFACES (316th): (a) the SpeedLine Portal SPA bundle https://portal.speedlinesolutions.com/assets/100205-f6232d-0/bundlec03ab81875368020fff7.js served anonymously at 200 (22,309,785 bytes, sha256 43d9e874a0bef98f..., webpack dev-style output with 1,146 './src/' module banners and comments intact, no dynamic chunk loader: a complete census of the Portal client); (b) the 391-topic SpeedLine Plus Portal Help at https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web/ (hmcontent.js re-fetched 2026-09-16 byte-identical to the 2026-08-09 dump; nonsense topic 404s, so no catch-all) - earlier notes counted only the other four manuals (784 topics) and never cited this one. EVIDENCE: the Portal writes menus through its own authenticated backend (MenuDefinitionAPI.ts, MenuDefinitionCompileAPIActions.ts, a changeset store-settings service under cloudFrontUrl/{region}/store-settings) and pushes them outward ('Make Live' to SpeedDine and marketplaces) - a first-party UI backend, with no API-key issuance, developer, partner or public menu-write surface in any of the 1,146 modules (tokenised 'api key' hits are Google Maps and SpeedLine Loyalty credentials; 'webhook'/'developer' hits are AWS SDK - POISON). portal.speedlinesolutions.com 403s every path incl. a nonsense path (CloudFront default), so /swagger, /openapi.json and /api-docs probes carry no signal. The SL Plus help's only developer artefact is 'An EventStream SDK that includes event and XML structure information... available to developers' (eventstream.html) - outbound security events, not menu. SpeedLine Connect's message catalogue remains unpublished. Retrieved 2026-09-16. || 319th: CLAIM: menu items/modifiers/prices writable via API. VERDICT: unknown (unchanged). NEW SURFACE (319th, via crt.sh on speeddine.com - SpeedLine's own online-ordering domain, whose apex 307s to www.speedlinesolutions.com/features/online_ordering; 400+ CT names incl. posapi.qa/posapi.automatedqa): https://posapi.qa.speeddine.com/api-docs served anonymously at 200 (4,894,927 B, sha256 cfb48b9c...; byte-identical at posapi.automatedqa.speeddine.com/api-docs; nonsense path 404 {"message":"Not Found"}, so not a catch-all; no robots.txt on host). A RapiDoc page embedding a full OpenAPI 3.0.0 spec, info.title 'POS API', description 'API for the SpeedLine Point of Sale system', 112 operations, bearer 'storeToken' auth. CAVEATS capping its weight: QA hosts only (posapi.prod.speeddine.com NXDOMAIN); it is the internal backend of an iOS/iPad terminal ('hold the request open until one of the store's iPads answers'); it cites in-progress milestones ('MS-07 ships manual only; automatic arrives with the scheduled day end', 'See iOS-pos-workspace/design-doc/ms08/...') and parity with 'the legacy terminal'/'Delphi' - pre-release SpeedLine+ POS rebuild documentation, not a published partner API. EVIDENCE: the menu surface of the 112-operation spec is GET /menu 'Retrieves the live instore menu' (read-only) and GET/PUT /menu/outOfStock 'Replaces the complete list of PLUs marked as out of stock for this store' (availability only). No POST/PUT/PATCH on menu items, modifiers or prices. Not a bounded 'no': this is the internal terminal backend on a QA host, not SpeedLine's full API estate (SpeedLine Connect XML and the Portal menu tools are separate surfaces). Retrieved 2026-09-16. || 323rd: NEW (323rd): the cell's note predates the POS API spec found in the 319th, so the spec's PATH TABLE is recorded here for the first time. The embedded OpenAPI 3.0.0 document at https://posapi.qa.speeddine.com/api-docs (re-fetched live 2026-09-17, HTTP 200, 4,896,103 B; nonsense sibling paths 404 {"message":"Not Found"}, so not a catch-all) enumerates 80 paths / 112 operations. MENU SURFACE, complete: "GET /menu" and "GET,PUT /menu/outOfStock" - the only menu WRITE in the whole document sets out-of-stock state. There is no POST/PUT/PATCH for items, modifiers, modifier groups, prices, price levels or menu versions; the writable objects are customers, customer phones/comments/credits, house-account transactions, shifts, employee logins, employee messages, deferred orders, orders (incl. /orders:bulkSave), parties, calls, dispatch, banks, transactions, manager alerts, system events and settings refresh. SECOND NEW SURFACE: the live SpeedLine Connect product sheet https://www.speedlinesolutions.com/hubfs/SpeedLine%20Connect%20Flyer.pdf (HTTP 200, 582,292 B) is the only public description of SpeedLine's integration API and it enumerates its payloads: "SpeedLine Connect messages pass data back and forth between your remote ordering system and SpeedLine POS ... converted to a formatted XML message and sent to the SpeedLine POS via a dedicated WAN IP on a specific port at the store"; "Messages can contain: Orders and ticket information; Payment information; Store hours and quoted times; Customer records; Street addresses; Delivery zones; Employee shift information; Menu information; Connect API version; Information for Punchh." "If the remote ordering system has requested information from the SpeedLine POS, it will be sent in the reply" - menu data flows POS -> partner (read), and the sheet describes no inbound menu write. WHY STILL UNKNOWN: the OpenAPI document is served only on QA hosts (posapi.prod.speeddine.com still does not resolve on 2026-09-17) and is pre-release SpeedLine+ material, so under merge policy it cannot carry a `no`; the Connect sheet is grade C marketing. Retrieved 2026-09-17. || 326th: NEW SURFACE (326th), cell NOT moved, but the denominator is now measured. NEW SURFACE (326th) - THE PUBLISHER'S OWN TOPIC MANIFEST, FETCHED TO 100%. support.speedlinesolutions.com serves five Help+Manual ('hmWebHelp') webhelp sets under /Portals/0/CustomerDocumentation_SF/. Each ships its own complete topic manifest at js/hmcontextids.js (the hmContextIds[] array). Fetched all four live sets and then crawled every in-body href to a FIXPOINT (2 rounds each, 0 new files in the last round): Store Manager (the SpeedLine POS back office) ReleaseDocs/Store_Manager_help_Web 528 topics; Menu Designer ReleaseDocs/Menu_Designer_help_Web 269; SpeedLine+ Portal (the cloud above-store portal) SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web 398; SpeedDine Admin (online ordering admin) SpeedDine/SpeedDine_Admin_help_Web 140. TOTAL 1,335 topics / 3,144,482 characters / 521,711 word tokens / 7,037 distinct tokens. The href fixpoint added only 14 files beyond the context-id manifest and all 14 were fetched, so the corpus is closed: manifest union href-fixpoint, nothing unreached. A fifth set, SpeedLineNext/SpeedLine_Next_Admin_Help_Web, is referenced by seven dead links inside Store Manager topics and is 404 for index.html, hmcontextids.js and every named topic (retired, not withheld). robots.txt on this host is a GENERIC 'User-agent: *' bar on /Portals/ that names no crawler, so it was read like a browser under the standing order; no login, no auth. This is the vendor's own product documentation = grade B. SCOPE: these four sets cover the back office (Store Manager), the menu tool, the cloud portal and the online-ordering admin - i.e. every configuration surface of the SpeedLine product. The Terminal (the POS station itself) has no separate published help set: 'terminal help' returns 0 and Terminal behaviour is documented inside Store Manager Help. WHAT IT HOLDS ON THIS CELL: across all 1,335 topics the token `api` occurs exactly TWICE, both the same sentence in two sets - 'SpeedDine communicates with stores through the built-in SpeedLine Connect API' (speeddinesourcespeedstarttutorial.htm and sp/add-speeddine-order-source.html). `webhook` 0, `rest api` 0, `web api` 0, `endpoint` 0, `swagger` 0, `openapi` 0, `developer` 0. Menu WRITING is documented only as a vendor-internal publish action, not an API: 'Click Make Live on your SpeedDine Menu to publish the menu to any third-party marketplace that has been onboarded' (enable-speedline-marketplace.htm). WHY STILL UNKNOWN: a customer-facing help system is not a census of a vendor's APIs - SpeedLine Connect demonstrably exists and is simply not documented here - so this corpus cannot carry a `no` on an API claim; and the only specification that does describe it remains QA/pre-release (posapi.qa.speeddine.com), which merge policy bars. What is new: SpeedLine publishes NO developer documentation at all on its support site. Retrieved 2026-09-18. || 327th: NEW SURFACE (327th): controls run for the first time over the 1,335-topic Help+Manual census (.cache/q326/speedline/corpus_all.txt, five sets at 100% of their hmcontextids manifests). The integration surface the documentation describes is SpeedLine Connect, and its documented DIRECTION is store-outbound: 'SpeedDine communicates with stores through the built-in SpeedLine Connect API', and the setup tutorial enumerates its steps as 'Step 7: Set Info to Include in Store Info Response' and 'Step 8: Set URL for Notifications of Connect Store Changes' (26 'Store Info' hits, all response/read shaped). Tokenised controls: 'webhook' 0; 'menu updates' 0; 'update the menu' 0; 'API' only 2 hits, both the SpeedDine sentence above. So the store-side documentation shows Connect as a read-and-notify surface with no menu write. WHY STILL UNKNOWN, not a `no`: SpeedLine publishes no API reference at all (the only spec on disk is posapi.qa.speeddine.com, which is PRE-RELEASE QA and may not carry a verdict per merge policy), and a help manual for store staff is not a census of an API it does not document. An `no` here needs the Connect provider documentation, which is issued privately to partners. Retrieved 2026-09-18. adversarially verified

Every core object the API can read (orders, menu, customers, employees, inventory) can also be written or updated via the same API. differentiator

extensibility-data-symmetry

Two of the five core objects have a documented write path over SpeedLine Connect, the rest do not. WRITES: tickets - "An Add Ticket request was received for a ticket with out of stock items or modifiers", plus "Allow Voiding of Tickets" with a "Maximum Ticket Age (seconds)" window (connect_restrictions.htm); customers - the manager-alert table names "Customer Record Failure - For example, the requested customer record on an Edit Customer request does not exist, or the phone number on an Add Customer request matches an existing record", and the public 8.0 Release Notes track that path across releases ("Changed: Adding or editing a customer through SpeedLine Connect more closely mirrors the process in Terminal"; "Fixed: Issue in Release 14 where Add/Edit Customer messages from Connect providers would sometimes not take effect"; "Fixed: A customer record's delivery zone tax jurisdiction was not being properly set via SpeedLine Connect"). READS ONLY: store data is served through the Store Info Request Response with per-field include checkboxes for quoted times, store hours and taxes (set_info_to_include_info_response.htm), ticket data through Ticket Request, and the source may be limited to "Tickets From This Source" or granted "All Tickets". SHORTFALLS: no write path is documented for menu items, modifiers or prices (an incoming message can only reference a PLU that "does not exist in Menu Designer" as an error), for employees (employee shift data appears only outbound), or for inventory (out-of-stock state is held at the store and governs whether an incoming ticket is accepted or rejected). The Connect/OrderLink message specification is partner-distributed and unpublished, so this is the documented surface, not necessarily the whole protocol. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/set_connect_general_properties_2.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

API rate limits are published as specific numeric quotas with documented throttling behavior and headers.

extensibility-published-rate-limits

No numeric quota, throttling behaviour or rate-limit header is published anywhere in SpeedLine's public surface: 784 topics across the four support.speedlinesolutions.com manuals, the public 8.0 Release Notes PDF, all 153 support advisories and the 574-URL www.speedlinesolutions.com sitemap. What SpeedLine documents instead is store-local capacity management, which is the architectural reason no quota exists to publish: Connect is a listener on the store's own station ("In the Port field, type or select the port number that Terminal will listen on for messages from the Connect provider", with an optional "Restrict to IP Addresses" allowlist), and Control Connect Service governs how many instances of the Connect Service run on a station, defaulting to a count derived from the station's processor cores - "If you have some SpeedLine stations with reduced processing power and you experience slowdowns when receiving Connect orders, you can control the number of copies of Connect running on a station." The only numeric limits in the whole Connect surface are a per-source "Maximum Ticket Age (seconds)" void window and a 0-300 second duplicate-error suppression window for SQS connection alerts - neither is a request quota. There is also no host that could publish one: api./developers./docs./help.speedlinesolutions.com do not resolve and support.speedlinesolutions.com/llms.txt 404s. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/control-connect-service.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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 `speedline_production`, rendered as 'Speedline Solutions ', 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

Enable SpeedLine Marketplace: "SpeedLine Marketplace streamlines your operations by integrating online third-party ordering channels like DoorDash, Uber Eats, and Grubhub with your POS." The setup is first-party end to end - activate Third Party Marketplaces on the SpeedLine Portal tab in Store Manager, then "Complete the SpeedLine integration onboarding process for third-party marketplaces: DoorDash: SSIO Onboarding Information for DoorDash. Uber Eats: Onboarding Information for Uber Eats. Grubhub: Onboarding Information for Grubhub", then "Click Make Live on your SpeedDine Menu live to publish the menu to any third-party marketplace that has been onboarded. Orders placed on third-party marketplaces will appear in Terminal." Taxes for Marketplace Orders confirms live order handling per marketplace: "For subscribers of SpeedLine Marketplace, the responsibility for remitting taxes on orders is determined by the third-party marketplace (DoorDash, Uber Eats, or Grubhub)." No Otter, Chowly, Deliverect or ItsaCheckmate layer is required - those aggregators appear elsewhere in the manual only as the alternative for operators NOT on Marketplace. QUALIFICATIONS: Marketplace is a paid SpeedLine subscription ("Contact SpeedLine Support to subscribe to SpeedLine Marketplace and enable your SpeedLine Portal access") and requires "SpeedLine version 8.0 R400 or later"; the operator still sets up its own merchant accounts with each marketplace. ezCater is named on the Marketplace brochure and the partners page but not in this topic. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/enable-speedline-marketplace.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

extensibility-middleware-compatibility

Both Chowly and Checkmate are named SpeedLine integration partners, so the POS is a supported endpoint for at least two major aggregators. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

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

extensibility-accounting-connectors

Restaurant365 is a named native accounting/operations connector. QuickBooks Online is not named, and mapped journal entries versus file export are not documented. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

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

extensibility-payroll-export

Native ADP (RUN by ADP) export plus a custom format, and a 7shifts payroll/scheduling integration. Gusto, Paychex and Paylocity are not named. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01

Raw transaction-level data can be exported on a schedule to a customer-controlled destination (S3/SFTP/warehouse/Snowflake share), not only viewed in the vendor's reporting UI. differentiator

extensibility-bi-data-warehouse

SpeedLink Enterprise pushes scheduled transaction-level and operational files into a SQL Server database the customer owns and controls. https://www.speedlinesolutions.com/hubfs/SpeedLink.pdf · retrieved 2026-08-01

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

extensibility-app-marketplace

A public Partners page catalogues ~25 named integrations across payments, delivery, loyalty, kiosk, KDS, inventory, security and messaging — browsable, but not self-installable; each requires a SpeedLine engagement. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

Operators can define custom fields or run vendor-hosted custom logic/scripts against POS objects without a vendor engineering engagement.

extensibility-custom-fields-scripting

Store Manager documents operator-defined custom fields on the Terminal Customer screen ('Add Custom Fields to the Customer Screen'; the numbered zones Zone 1, Zone 2 and so on 'refer to custom fields on the Terminal Customer screen, one of which may be a delivery zone field'), and custom street-level fields appear on the street entry screen. It also ships a built-in SQL Query screen (Settings > System > SQL Query, runansqlquery.htm) where the operator types or pastes SQL directly against the store database, saves and reloads named queries, and prints results as a report; access is gated by two enumerated security privileges, 'SQL Query Read Access' and 'SQL Query Read/Write Access'. Neither requires a vendor engineering engagement. The scripting runs against the operator's own on-premise database rather than being vendor-hosted. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/addcustomfieldscustscreen.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Effectively a headless engine already: third-party kiosks (GojiKiosk, Nextep, Checkmate), third-party ordering front ends (Onosys, Menufy, Brygid, RTO) and Voicify voice AI all drive SpeedLine's transaction engine via SpeedLine Connect. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

The vendor publishes an API changelog and a stated deprecation/notice policy for breaking changes.

extensibility-api-versioning-deprecation

Half the claim is met. CHANGELOG: the 8.0 Release Notes PDF is public and unauthenticated (printed May 2026, running to release 8.0.413), organised per module and per Test Track number, and it does record integration-surface changes - "Enhanced: Worldpay Omnitoken fields added to SpeedLine Connect API", "Changed: Adding or editing a customer through SpeedLine Connect more closely mirrors the process in Terminal", "Fixed: A customer record's delivery zone tax jurisdiction was not being properly set via SpeedLine Connect" - alongside 58 SpeedLine Releases advisories covering 7.2 r414 through 8.0 r413. Gateway compatibility floors are published in the manual too (Notifications require Connect/OrderLink Gateway 2.3 or later, DeliveryDetails 2.5 or later), so the integration is versioned and its version requirements are stated. SHORTFALLS: there is no API-specific changelog - Connect entries are scattered through a product release stream and there is no way to subscribe to or filter them; and no deprecation or breaking-change notice policy is published anywhere. SpeedLine does publish individual dated end-of-support notices with lead time ("As of July 1, 2023, SpeedLine will no longer support SpeedLine 7.2 or earlier versions"; "As of September 1, 2025, SpeedLine will be discontinuing support for all non-PCI compliant versions: SpeedLine 8.0 R300 and earlier"; "Monetra Discontinued, Security Maintenance Ending"), but these are product-support notices with no stated notice period, and none concerns the Connect message contract. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/8_0_ReleaseNotes.pdf · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

SpeedLink can deliver orders, employees, inventory and forecast data into an operator-owned database, and the on-prem store database is physically on operator hardware. No published contract-end export policy or documented machine-readable exit package. https://www.speedlinesolutions.com/hubfs/SpeedLink.pdf · retrieved 2026-08-01

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

reliability-offline-order-entry

The only public evidence is one FAQ sentence, which I retrieved verbatim: "When the settings and menu are downloaded, local copies are kept in the store, so if it goes offline, it will continue to work with those offline settings." That documents menu/settings caching, not an affirmative statement that order entry, tender and check state survive an outage. The architectural inference (on-prem engine) is sound but SpeedLine never states the outcome. This is a differentiator cell and should be held to the documentation bar, not the inference bar. https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01 adversarially verified

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

reliability-offline-card-auth

Store Manager's triPOS settings topic documents an 'Enable Store and Forward' setting on the Settings > System > Card Processing > WorldPay (Vantiv) > triPOS sub-tab, and singles it out as the one setting there that is not confined to wired in-store PIN pads. The MercuryPay topic confirms it is a real platform feature by naming who lacks it: 'MercuryPay (Datacap) supports in-store payments (EMV and non-EMV)... it does not support SpeedLine Pay, Store & Forward, or third-party payment processors. For these features, use the Worldpay Express platform with triPOS.' Separately, Terminal security privileges include entering a phone-obtained code 'to allow credit card payment authorization if there is no Internet connection available'. Conditional on the Worldpay Express/triPOS platform: stores on Worldpay MercuryPay (Datacap) do not get store-and-forward. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/enter-tripos-settings.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Enter triPOS Settings, Enable Store and Forward field description, states liability and both caps. LIABILITY: "When the Enable Store and Forward setting is selected, you will be prompted to accept liability for any offline transactions that are later declined when the connection to the Express server is restored. Managers will receive an alert when offline transactions are declined, or approved for less than the total owing, and must obtain alternate payment, or discount the amount owing." The merchant bears the loss, is made to accept it explicitly at the moment the feature is switched on, and is told the recovery procedure. CAPS: "Store and Forward Transaction Limit: Type or select the dollar amount per transaction that can be approved locally while offline. Transactions over this limit will be declined" and "Total Limit Per Outage: Type or select the total dollar limit per station that can be approved locally during one outage period. This limit will be reset each time the connection to the Express server is lost." Both caps are operator-set rather than fixed by SpeedLine, and they are per station. The setting also propagates to mobile: "what is set here will also be the initial setting exported to the SpeedLine Pay app during app configuration. Store and Forward can later be enabled or disabled, and limits changed, on the Configuration screen for each device running the app." This is Worldpay Express triPOS store-and-forward; the underlying processing terms remain in the Worldpay merchant agreement, which SpeedLine does not publish. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/enter-tripos-settings.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

Store terminals share a local server on the store LAN — SpeedLine Connect opens a socket to that store-level system — which implies shared check state survives an internet outage, but this is not explicitly documented. https://www.speedlinesolutions.com/hubfs/SpeedLine%20Connect%20Flyer.pdf · retrieved 2026-08-01

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

Explicitly on-premise: SpeedLine Connect integrates by connecting over TCP to the SpeedLine system running at the store location, and SpeedLine 8 is a locally installed Windows product. This is architecturally rare in 2026 and is SpeedLine's main reliability advantage. https://www.speedlinesolutions.com/hubfs/SpeedLine%20Connect%20Flyer.pdf · retrieved 2026-08-01

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

reliability-offline-kds-printing

Kitchen routing runs off the store-local engine, so it should survive an internet outage, but SpeedLine does not state this for KDS and printers specifically. https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01

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

Every printer has an Alternate Printer setting (Settings > Hardware Setup > Printers > Device tab): 'If the station that the main printer is connected to is not working, print jobs will automatically be sent to this alternate printer.' Named shortfalls: automatic failover covers only station failure, and the same topic warns that 'If a printer is offline or broken but the computer it is attached to is working, SpeedLine may not be able to detect this and may continue to route print jobs to the failed printer' - recovery is then a manager ticking 'Send Print Jobs to Alternate Printer' by hand, and remembering to clear it afterwards. No staff alert or notification on printer failure is documented anywhere in the 458-topic manual, and the four Kitchen Monitor topics document make-route assignment but no printer-to-KDS fallback. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/assignanalternateprinterroute.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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. VERDICT: no, on the published help (the 409/first-write-wins evidence the prior pass found is in the pre-release QA OpenAPI, which merge policy bars from carrying a verdict). NEW SURFACE (326th) - THE PUBLISHER'S OWN TOPIC MANIFEST, FETCHED TO 100%. support.speedlinesolutions.com serves five Help+Manual ('hmWebHelp') webhelp sets under /Portals/0/CustomerDocumentation_SF/. Each ships its own complete topic manifest at js/hmcontextids.js (the hmContextIds[] array). Fetched all four live sets and then crawled every in-body href to a FIXPOINT (2 rounds each, 0 new files in the last round): Store Manager (the SpeedLine POS back office) ReleaseDocs/Store_Manager_help_Web 528 topics; Menu Designer ReleaseDocs/Menu_Designer_help_Web 269; SpeedLine+ Portal (the cloud above-store portal) SpeedLinePlus/SpeedLine_Plus_Portal_Help_Web 398; SpeedDine Admin (online ordering admin) SpeedDine/SpeedDine_Admin_help_Web 140. TOTAL 1,335 topics / 3,144,482 characters / 521,711 word tokens / 7,037 distinct tokens. The href fixpoint added only 14 files beyond the context-id manifest and all 14 were fetched, so the corpus is closed: manifest union href-fixpoint, nothing unreached. A fifth set, SpeedLineNext/SpeedLine_Next_Admin_Help_Web, is referenced by seven dead links inside Store Manager topics and is 404 for index.html, hmcontextids.js and every named topic (retired, not withheld). robots.txt on this host is a GENERIC 'User-agent: *' bar on /Portals/ that names no crawler, so it was read like a browser under the standing order; no login, no auth. This is the vendor's own product documentation = grade B. SCOPE: these four sets cover the back office (Store Manager), the menu tool, the cloud portal and the online-ordering admin - i.e. every configuration surface of the SpeedLine product. The Terminal (the POS station itself) has no separate published help set: 'terminal help' returns 0 and Terminal behaviour is documented inside Store Manager Help. CONTROLS over all 1,335 topics: `partition` 0, `last write` 0, `last-write-wins` 0, `merge conflict` 0, `primary station` 0, `secondary station` 0, `resolve` 0. POISON NAMED: `conflict` returns exactly 3 hits and all 3 are configuration validation, not data reconciliation - 'Clearing the Minor Employee Restrictions > Work As settings may conflict with the Work as Driver and Work as Server settings' (setupuseemployeerestrictions.htm) and, twice, 'If the options you have selected conflict (for example, if gluten-free crust is only available in small sizes...)' (add-choices-to-a-portioned-product-group). `sync` returns 12 hits and every one is MENU SYNC to a marketplace ('the Menu Sync fails because it is too large for Grubhub's menu size limitations'), not terminal-to-terminal state (POISON). A multi-station product whose complete back-office manual never states what happens to divergent edits is not documenting this. Retrieved 2026-09-18. https://support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/ReleaseDocs/Store_Manager_help_Web/index.htm · retrieved 2026-09-18 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

The FAQ addresses offline operation generically ('local copies are maintained') but publishes no feature-by-feature list of what stops working — no statement on gift cards, loyalty lookup, refunds or manual card entry offline. https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01

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

reliability-public-status-page

Re-probed 2026-08-09: status.speedlinesolutions.com has no A record (nslookup returns the SOA only; curl fails to resolve, exit 6), /security and /legal 404, and the complete www.speedlinesolutions.com sitemap.xml - 574 URLs, the vendor's whole public site - contains no status, trust or uptime page. SpeedLine's documented mechanism for service-affecting events is an email list plus a dated archive: /support-services says 'Support Advisories: Occasional email alerts are sent to inform you of important updates about SpeedLine and other networks that may affect your restaurant operations.' The full archive behind it is 153 posts (only about ten are linked from the marketing page; the rest are reachable only via sitemap.xml) and it does carry real incident content - a Valutec gift-card migration with 'Estimated Duration: Approximately 8 hours', SpeedLine Analytics maintenance windows, and 'Thank you for your patience during today's Remote Connection software service outage' - but as undated-by-component blog entries with no current state, no per-component breakdown and no historical uptime. No login is required to read them; there is simply no status page. https://www.speedlinesolutions.com/support-services · retrieved 2026-08-09

A contractual uptime SLA with a stated percentage AND a service credit remedy is published or available in the standard agreement. differentiator

reliability-contractual-uptime-sla

CLAIM: a contractual uptime SLA with a stated percentage AND a service-credit remedy is published or contractually committed. VERDICT: no. NEW SURFACE (327th): the HubSpot site search index, https://www.speedlinesolutions.com/_hcms/search?term=<t>&limit=50, swept over 18 commercial/legal terms. It returns 219 distinct URLs, EVERY ONE of which is already in the 589-URL sitemap captured in the 324th - i.e. the site has no unlinked legal or pricing page; the HubSpot index is a strict subset of the sitemap, so the public corpus is bounded. EVIDENCE: the only support-commitment page, /support-services, describes the support product in full and commits to no availability figure: 'A SpeedLine Support subscription includes unlimited phone and email support and SpeedLine software upgrades.' Premiere Support is enumerated as upgrades, 1 hour of menu changes per store, etc. BOUND/CONTROLS: corpus 1 = the 1,335-topic Help+Manual census (.cache/q326/speedline, five sets censused to 100% of js/hmcontextids.js); corpus 2 = the bounded public site. Tokenised, word-boundary, case-insensitive: uptime 0/1,335 topics and 0 on /support-services; 'service level' 0; 'service credit' 0; 'guarantee' 0 on /support-services; 'SLA' 0. POISON NAMED: 'termination' scores 15 hits in the docs and every one is an EMPLOYEE termination reason (sm/addremoveterminationreasons.htm), not contract termination; the HubSpot search is OR/fuzzy on multi-word queries, so its raw totals for phrases (e.g. 'service level agreement' -> 250) are a reader artefact and were not used - only single-token counts and the fetched bodies were. Retrieved 2026-09-18. https://www.speedlinesolutions.com/support-services · retrieved 2026-09-18 adversarially verified

The vendor publishes written post-incident reports or root-cause summaries for major outages.

reliability-incident-postmortems

SpeedLine publishes a public, dated, uncited Support Advisories stream (about 190 posts in sitemap.xml, categorised, including 'Emergencies') and some entries are genuine written root-cause summaries of widespread service-affecting incidents: the 2025-09-30 advisory names the cause ('A recent Microsoft Windows update will modify a network feature... This Windows update will block SpeedLine stations from communicating with the primary station (Station 1) causing them to be unusable'), the exact affected population ('all SpeedLine stations purchased between 2016 and mid-September 2025'), the remediation and its per-station duration, plus a customer workaround. Named shortfall: outages of SpeedLine's own services get only terse restoration notices with no root cause, timeline or impact analysis - the 2025-08-12 'Services Restored' advisory says only 'Thank you for your patience during today's Remote Connection software service outage. All SpeedLine Customer Support Call Center services are now available.' No post-incident report format, severity scale or commitment to publish one exists. https://www.speedlinesolutions.com/supportadvisories/microsoft-update-impacts-network-connectivity-for-some-locations · retrieved 2026-08-09

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

Contradiction confirmed on both sides. Vendor site: "Live toll-free support available 365 days a year", never 24/7, and support is sold as Standard / Premiere / Store Management tiers (Premiere = "one hour of monthly menu adjustments per location"). Capterra's vendor-submitted profile does assert "24/7 Live Rep". Partial with the discrepancy flagged is exactly right. https://www.speedlinesolutions.com/support-services · retrieved 2026-08-01 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

'SpeedLine's extensive on-site installation and training', delivered by QIR-certified Installation & Training Specialists or company-trained Certified Technicians. A real first-party field organization, not remote-only. https://www.speedlinesolutions.com/support-services · retrieved 2026-08-01

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

reliability-menu-build-service

The Support Team customizes menus and backend settings before installation; Premiere Support then includes one hour of menu changes per store per month, and Store Management Services handles menu changes ongoing. https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01

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

reliability-hardware-replacement-sla

An advance-exchange program is purchasable but only for payment hardware, and no turnaround time is published. SpeedLine's support advisory on the Worldpay MSD contactless withdrawal offers an upgrade path to the Ingenico Lane 3000 whose listed advantages include an 'Optional 3-year advanced exchange warranty', bought through 'our After Market Sales Team at ams@SpeedlineSolutions.com'. The shortfalls: it is scoped to one pin pad model, not to terminals, printers or kitchen displays; no replacement turnaround or SLA is stated (the 'approximately 3 weeks' on the same page is the pin-pad key re-injection process, not an exchange); and no price is given. /support-services, re-read 2026-08-09, enumerates Standard Support ('unlimited phone and email support and SpeedLine software upgrades'), Remote Support, Premiere Support Services, Store Management Services and Second-Level Support with no hardware replacement of any kind, and the 574-URL sitemap carries no warranty or RMA page. The only other warranty language in the 784 published manual topics is a scanner-cleaning caution that abrasives 'may invalidate the warranty'. https://www.speedlinesolutions.com/supportadvisories/worldpay-update-removes-msd-contactless-payments · retrieved 2026-08-09

Operators can trigger and retrieve their own data backup/restore, or the vendor publishes RPO/RTO figures for data recovery.

reliability-backup-restore

Backup and restore are operator-controlled and documented. The database is copied continuously from the primary server (typically Station1) to the secondary server on an operator-set interval (Settings > System > Backup > Continuous Database Backup; 'The recommended backup interval is one minute', settable 'up to a maximum of 60 minutes', with the caution that increasing it 'increases the chance of data loss'). A HotBackup utility copies a preset file list plus any files or directories the operator adds, either continuously or once daily at a set time (change_file_backup_settings.htm). Restore is an operator-run wizard: on the secondary server, Start > SpeedLine Solutions Inc > 'Hot Backup Restore', which converts the secondary to primary and restores the data. Noted limits that do not change the verdict: no RPO/RTO figures are published, and third-party files - 'for example, Monetra or Worldpay' - must be reinstalled and restored manually. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/restore_data_from_a_backup.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

SpeedLine publishes no PCI DSS 4.0/4.0.1 Attestation of Compliance, no Software Security Framework validation and no P2PE solution listing of its own. Its own compliance document is still the PA-DSS Implementation Guide - PA-DSS was retired in October 2022 - and the Store Manager help, in a build stamped SM_8.0.409_1/14/2026, still describes it as 'An explanation of the Payment Application Data Security Standard (PA-DSS) guidelines for protection of payment cardholder data. Includes installation, configuration and management best practices for using SpeedLine in a PCI DSS compliant environment', available only through the in-product Document Viewer, not on any public host. The marketing claim for SpeedDine remains 'PA-DSS validated'. The single P2PE reference anywhere on the site is a 2022 support advisory listing, among the advantages of upgrading a pin pad, that the Ingenico Lane 3000 'Is P2PE certified when using Worldpay Express' - a hardware-and-processor validation belonging to Worldpay, not a SpeedLine attestation, and predating the v4.0 future-dated requirements. Searched the 574-URL sitemap, 784 manual topics, the 8.0 Release Notes and all 153 advisories: no AoC, no ROC, no SSF listing. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/additionalhelpdocumentation.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

reliability-mfa-role-based-access

Role-based permissions are granular (per employee, department and station). MFA enforcement on back-office or POS administrative logins is not documented — a gap given PCI DSS 4.0.1 Req 8.4.2 has been in force since March 2025. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf · retrieved 2026-08-01

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

reliability-self-serve-training

Training videos, user guides, system guides and a knowledge base exist, plus a POS Quick Tips newsletter and a terminal training mode — but the library sits behind a customer login and an active support subscription, so it is not public or free. https://support.speedlinesolutions.com/Home · retrieved 2026-08-01

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

reliability-failover-terminal-role

Roles are fixed and named, not floating: a station is the primary server (typically Station1), the secondary server, or a work station, identified from Terminal's status line or the WS Config utility. Failover exists - 'If your primary server fails, you can restore your SpeedLine data from a backup copy that is automatically made to the secondary server... This procedure allows you to convert your secondary server to a primary server and restore the SpeedLine data previously backed up there, so you can continue to make sales with SpeedLine.' Named shortfalls: promotion is manual, performed by a person running the Hot Backup Restore wizard from the Windows Start menu on the secondary server; only the one designated secondary can take the role, not any terminal; and card payments do not come back automatically because 'Files for third-party programs must be restored manually... you may not be able to accept card payment types until third-party software (for example, Monetra or Worldpay) is re-installed and third-party data is manually restored.' https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/restore_data_from_a_backup.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

reliability-cellular-backup

SpeedLine does document a cellular backup path, in the one document the online manuals defer to. The 'Minimum Requirements and Supported Hardware' Knowledge Base article - a supported-hardware table, publicly served from www.speedlinesolutions.com/hubfs even though the support-site Knowledge Base itself is login-gated - has a Modems section naming the 'Digi 6310-DX Cellular Extender Router with Plug-In Modem' as a 'Backup modem, used in the case of internet connection failure. Requires a cellular data plan. Supported configuration is use of the Digi modem in conjunction with a SonicWall SOHO or SOHO 250 router running SonicOS 5.6 or higher.' The Card Processing table recommends it for triPOS Direct, Datacap/MercuryPay and Monetra alike, 'so that payment cards can continue to be accepted in the case of internet connection failure', alongside broadband with an internet router as the required primary link. Separately, triPOS Mobile (SpeedLine Pay) on iPhone/iPad requires 'An active built-in cellular connection with cellular data plan' as its primary connectivity, with in-store Wi-Fi only as the alternative. SHORTFALL: this is not a terminal-native LTE radio and not a first-party service. It is a separately purchased third-party WAN-failover appliance pair (Digi extender plus SonicWall firewall) on the merchant's own cellular data plan - SpeedLine states 'SpeedLine is not responsible for data usage charges' - it is 'recommended', never required or bundled, no automatic-cutover behaviour or failback timing is described, and its documented purpose is keeping card authorization alive rather than full store connectivity. The document carries a 2010-2021 copyright, so the named models are dated. Nothing in the 784 topics across four manuals, the 8.0 Release Notes or the 153 support advisories adds a software-side failover control. https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/TrainingDocs_SF/SpeedLineMinimumRequirementsAndSupportedHardware.pdf · retrieved 2026-08-09

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

CLAIM: vendor PUBLICLY offers a month-to-month subscription with no minimum multi-year term for its core POS tier. VERDICT: no - nothing of the kind is offered publicly. NEW SURFACE (327th): the HubSpot `_hcms/search` index (see the uptime cell) proves the public site has NO unlinked legal document: 219 indexed URLs, all inside the 589-URL sitemap. The single legal document SpeedLine publishes is https://www.speedlinesolutions.com/terms, and it is a WEBSITE Terms of Use only (14.7 KB stripped): 'AGREEMENT BETWEEN USER AND SpeedLine Solutions Inc.', a Communication Services clause, a DMCA agent notice, and 'TERMINATION/ACCESS RESTRICTION SpeedLine Solutions Inc. reserves the right, in its sole discretion, to terminate your access to the SpeedLine Solutions Inc. Web Site'. There is no subscription agreement, MSA, order form or EULA on the public site. CONTROLS over that document, tokenised: 'month-to-month' 0, 'renew' 0, 'increase' 0, 'hardware' 0, 'export' 0, 'refund' 0; 'terminate' 2 and 'termination' 1, all three about website access, not a subscription. The vendor's buying-guide page /pos-quotes-comparing-apples-to-apples instead tells the reader to ASK a vendor 'Can you cancel anytime, or are you under contract for a set period?' - i.e. SpeedLine itself treats the term as a per-deal negotiation. Retrieved 2026-09-18. https://www.speedlinesolutions.com/terms · retrieved 2026-09-18 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

I read the whole of the only agreement SpeedLine publishes. www.speedlinesolutions.com/terms is a website Terms of Use - agreement between user and SpeedLine Solutions Inc. covering web-site use, links to third-party sites, communication services, submissions, a liability disclaimer, and Washington-law governance - and it contains no subscription, term, renewal or termination-fee provision; its only termination clause is SpeedLine's own right to 'terminate your access to the SpeedLine Solutions Inc. Web Site... at any time, without notice'. No MSA or subscription agreement is published to state the absence of an early termination fee: /legal 404s, the complete 574-URL sitemap.xml contains no agreement page, and the three public legal documents are /terms, /privacy and /speedlinepayappprivacy - the last a MobilePay app privacy policy in effect since 15 February 2023, which I read in full and which governs app data collection, retention and storage location only, with no commercial term. The 26 PDFs on /guides-and-brochures are all product brochures, and none of the 153 support advisories states a termination fee or its absence. https://www.speedlinesolutions.com/terms · retrieved 2026-08-09

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 publicly accessible contract terms are three documents: /terms and /privacy, both linked in the site footer, and /speedlinepayappprivacy, reachable only from the MobilePay app and the sitemap. /terms is a website Terms of Use governing use of the web site and states no auto-renewal term and no cancellation notice window; /privacy is a website privacy statement; /speedlinepayappprivacy is an app privacy policy whose only retention language is 'We retain your information for as long as necessary or relevant for the listed purposes in this privacy policy, or as required or permitted by law.' No subscription agreement is published anywhere - /legal 404s and the complete 574-URL sitemap.xml has no agreement, MSA, pricing or terms page beyond those three - while /support-services refers to a 'SpeedLine Support subscription' without stating its renewal or notice terms, and the 153-post support advisory archive states only that upgrades are included in that subscription. Renewal terms therefore exist only in the signed quote, which is exactly what this claim asks about. https://www.speedlinesolutions.com/terms · retrieved 2026-08-09

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

There is no in-house processing mandate: the vendor's own support-advisory stream documents a supported set of payment paths in which SpeedLine's own product is one option among several. "Monetra Discontinued, Security Maintenance Ending" (SpeedLine Support, Feb 9 2026) announces that "Monetra development has officially ended" and that "As of March 4, 2026 Monetra customers will no longer receive critical security maintenance", then enumerates the alternatives under "Making the Change ... payment and gift card solution alternatives": under Payments, "Speedline Payments", "Worldpay Core" and "Worldpay Express Gateway", the last of which is listed as "supporting: TSYS, Fiserv/First Data, Global Payments, Paymentech"; under Gift Cards, "Valutec" and "ValueLink". SpeedLine Payments appears as one entry in that list rather than as the destination, and four named third-party processors remain reachable through Worldpay Express Gateway, so an operator is not locked to the vendor's own processing. TWO CAVEATS, both narrowing: contract terms are not public, so a pricing penalty for declining SpeedLine Payments cannot be ruled out (this caveat is carried over unchanged from the quarantined citation); and because this document is an end-of-life notice, it establishes the supported set as of Feb 2026 and not a standing commitment. RE-EVIDENCED 2026-08-30: the cell previously rested on https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/set_up_monetra_payment_process.htm, quarantined behind the "Disallow: /Portals/" bar on support.speedlinesolutions.com and NOT re-fetched. The barred manual is not recovered; a different document on a permitted host carries the proposition. www.speedlinesolutions.com/robots.txt was fetched whole (131 bytes, HTTP 200, one group "*", four Disallow rules, none of them /supportadvisories/) and matched mechanically with the shared parseRobots/refusedForUs: refusedForUs("/supportadvisories/monetra-discontinued-security-maintenance-ending") returns null. GRADE B, STATED SO IT CAN BE CHALLENGED: this is a first-party technical support advisory - a PCI end-of-life notice carrying dates and a supported-gateway list - not a feature page written to sell, which is why it is graded B rather than C. It does carry a sales call-to-action in its footer; what is cited above is the compliance notice, not the CTA. WHAT WAS REJECTED AND WHY: the same advisory stream's "SpeedLine Marketplace is now available" post (13 May 2025) would have re-homed delivery-3p-direct-integration and extensibility-first-party-delivery-integrations, but it is a product announcement written in marketing register ("A game-changing integration") - grade D, which does not meet the A-or-B floor a yes on a differentiator requires. Those two cells stay quarantined rather than take a worse citation. The verified flag on this row records the 2026-08 adversarial pass on the VALUE, taken against the original citation; it does not carry over to this replacement document. No verification.jsonl row was added, because a re-citation is not an adversarial pass and must never be counted as one. https://www.speedlinesolutions.com/supportadvisories/monetra-discontinued-security-maintenance-ending · retrieved 2026-08-02 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

No processing rate of any kind is published — neither flat, blended nor interchange-plus. The 'Credit Card Processing Comparison' PDF is lead-gen material, not a rate card. https://www.speedlinesolutions.com/speedlinepayments · retrieved 2026-08-01

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

commercial-rate-increase-clause

CLAIM: the PROCESSING agreement caps or prohibits unilateral rate increases, or grants penalty-free exit on an increase. VERDICT: no. NEW SURFACE (327th): the bounded public corpus described in the month-to-month cell (HubSpot `_hcms/search` index = 219 URLs, a strict subset of the 589-URL sitemap; no unlinked legal page exists) plus the 1,335-topic Help+Manual census. SpeedLine publishes NO processing agreement, merchant agreement or card-services terms at all - the only legal document is a website Terms of Use. CONTROLS, tokenised, word-boundary: over the Terms of Use, 'increase' 0, 'rate' 0, 'fee' 0 in any pricing sense; over the 1,335-topic documentation census, 'rate increase' 0. Payment processing in the docs is configured per third-party processor, so the commercial terms sit in the processor's contract, which SpeedLine does not publish. Retrieved 2026-09-18. https://www.speedlinesolutions.com/terms · retrieved 2026-09-18 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

The brief's /pricing URL returns HTTP 404 and there is no pricing entry in site navigation. No per-location or per-terminal figure appears on the site or in any of the 12 public brochures. Every path leads to Book a Demo. https://www.speedlinesolutions.com/ · retrieved 2026-08-01

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

commercial-module-unbundling

A la carte purchase is documented; independent cancellation without repricing the base POS is not. The Store Manager help's home topic (build stamp SM_8.0.409_1/14/2026) carries a heading 'Optional Additions to Store Manager - Please contact your SpeedLine Account Manager if you do not yet have these add-ons and are interested in learning more', then enumerates SpeedLine Analytics, SpeedLine Pay, SpeedDine, SpeedLine LiveMaps and SpeedLine Inventory as separately acquired modules, each with its own setup path; support is a further separable line ('Upgrades are included in your support services subscription or may be purchased separately if you are not currently on support'). Named shortfalls: no price or bundle structure is published for any module, nothing states that cancelling one leaves the base POS price unchanged, and every acquisition routes through an account manager rather than a self-serve catalogue. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/index.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

SpeedLine sells hardware through its own store and Capterra's vendor-submitted profile describes a one-time purchase model, suggesting outright ownership with no mandatory lease — but no prices are published and the store is login-gated. https://support.speedlinesolutions.com/Home · retrieved 2026-08-01

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

Bluetooth printers, EMV PIN pads and commodity Windows/Android/iOS devices are supported, and the FAQ says existing hardware may be reusable. No published third-party compatibility list naming Epson, Star or generic drawers. https://www.speedlinesolutions.com/faqs · retrieved 2026-08-01

One-time implementation, menu-build, onboarding, and training fees are published as specific amounts or explicitly stated as $0.

commercial-implementation-fee-published

On-site installation, training and pre-install menu build are all offered as services, but no amount is published and none is stated as $0. https://www.speedlinesolutions.com/support-services · retrieved 2026-08-01

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

Dashboards and reports export to PDF, image and other formats self-serve. Full transaction-level history (orders, line items, payments, labor) requires SpeedLink Enterprise — a separately licensed product — or direct access to the on-prem SQL database. https://www.speedlinesolutions.com/hubfs/SpeedLink.pdf · retrieved 2026-08-01

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

commercial-export-customer-and-loyalty

Customer records and employee data export via SpeedLink; Customer Data dashboards export from analytics. Loyalty point ledgers and Valutec gift-card liability balances are not documented as operator-exportable. https://www.speedlinesolutions.com/hubfs/SpeedLink.pdf · retrieved 2026-08-01

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

CLAIM: contract or documentation specifies a defined post-termination window during which the operator can still export its data. VERDICT: no - no such window is specified anywhere SpeedLine publishes. BOUND: (a) the public site, bounded as above (HubSpot `_hcms/search` 219 URLs subset of the 589-URL sitemap; the only legal doc is a website Terms of Use with 'export' 0 hits); (b) the 1,335-topic Help+Manual census (.cache/q326/speedline/corpus_all.txt, 3.14 MB, five sets to 100% of their hmcontextids manifests). CONTROLS over the documentation, tokenised: 'export data' 4 and 'data export' 2, and EVERY hit is an operational in-product export - 'Click a button to select the format to export data in', the ADP/General Journal payroll and accounting exports, shift data export - none is a post-cancellation retrieval right; 'retention' / 'retrieval period' / 'post-termination' 0. POISON NAMED: 'termination' 15/15 hits in the docs are employee termination reasons. CAVEAT for the owner: the POS itself is on-premise (store-resident data), which makes the window less consequential, but SpeedLine Plus / Cloud Reporting & Analytics and SpeedDine are hosted subscriptions and no retrieval window is published for them either. Retrieved 2026-09-18. https://www.speedlinesolutions.com/terms · retrieved 2026-09-18 adversarially verified

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

SpeedLine's complete published legal corpus is the two documents linked from every page footer, /terms and /privacy, and I read both in full. /terms is a website Terms of Use whose only ownership language covers user 'Submissions' to the web site ('SpeedLine Solutions Inc. does not claim ownership of the materials you provide'); /privacy states in its first line that it 'applies to the SpeedLine Solutions Inc. website and governs data collection and usage'. Neither states that the merchant owns its transaction or customer data, and neither constrains SpeedLine's right to use or resell it. The closest first-party statement sits outside any agreement, in a 2019 support advisory: 'The consumer information remains in the store in the SpeedLine system, and/or in restaurant head office reporting systems. The information is never sold by SpeedLine' - explicitly published 'for informational purposes only, and not for the purpose of providing legal advice'. Mitigating but not a substitute: the POS database physically resides on operator-controlled on-premise hardware. https://www.speedlinesolutions.com/terms · retrieved 2026-08-09

The POS is source-available or open source with a documented self-hosting option (source published under an OSI or source-available license, not merely an open API).

commercial-source-available-selfhost

Upheld, and now answered by the publisher's own registry instead of by assertion. GitHub reports the `SpeedlineSolutions` organisation -- self-identified as "SpeedLine Solutions Inc." with `blog: http://www.speedlinesolutions.com/`, created 2015-10-15 -- as publishing `public_repos: 0`, and the repository listing returns an empty array. SpeedLine claimed a namespace a decade ago and has never published a line of code in it. How the software IS obtained is documented and is the opposite of source-available: the vendor FAQ describes installation by SpeedLine staff or by "a member of your team [who] can become a SpeedLine Certified Technician to train and install your POS themselves", with binaries and updates delivered under a paid support subscription. The 583-URL sitemap carries no licensing, source or developer page, and `source code`, `open source` and `licen` are absent from the FAQ. The product being on-premise deployed is not the same as self-hostable source, which is what the claim asks. Grade A: a source registry answering about itself. https://github.com/SpeedlineSolutions · retrieved 2026-09-09

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

Tokenization for card-on-file and end-to-end encryption (E2EE) are documented, and SaferPayments is bundled to help merchants attest. Neither a validated P2PE solution listing nor the resulting SAQ type (A or P2PE-HW) is named. https://www.speedlinesolutions.com/speedlinepayments · retrieved 2026-08-01

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

commercial-pci-dss-4-controls

Nothing addresses the post-31-Mar-2025 future-dated requirements, and the access-control model SpeedLine documents is the pre-v4 one. Searching the complete published corpus - 784 topics across four manuals, all 870 inlined field descriptions covering every settings screen, the public 8.0 Release Notes to release 8.0.413, and 153 support advisories - returns zero occurrences of MFA, multi-factor, two-factor or 2FA. What is documented is single-factor: 'Setting strong Windows and SpeedLine passwords, and changing them regularly, is a Payment Card Industry Data Security Standard (PCI DSS) compliance requirement', with Password Maintenance, expiry-driven lockouts and a five-day Terminal lockout buffer before Windows passwords expire, and the reader is referred to the PA-DSS Implementation Guide - a standard retired in 2022 - for the requirements. No payment-page script-integrity claim is made for SpeedDine under Req 6.4.3/11.6.1 anywhere in the SpeedDine Portal manual or the advisories. Buyers should demand a current AoC in diligence. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/avoid_system_lockouts.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

Vendor states it holds a current SOC 2 Type II (or ISO 27001) attestation and will provide the report under NDA via a trust center or on request.

commercial-soc2-attestation

No SOC 2, SOC 2 Type II, ISO 27001 or trust-centre reference exists in any SpeedLine public material I can reach: zero occurrences across the 646 topics of the Store Manager (458), Menu Designer (183) and New Features (5) manuals dumped 2026-08-09, and no security, trust or compliance URL among the 501 in www.speedlinesolutions.com/sitemap.xml (/security 404s). SpeedLine's published assurance position is payment-scoped instead and is stated in its own words: installation and training specialists are 'QIR-certified... special training by the PCI Security Standards Council', remote support is 'PCI-DSS compliant', and the in-product Document Viewer ships a 'PA-DSS Implementation Guide... for using SpeedLine in a PCI DSS compliant environment', with PCI DSS password and vulnerability-scan requirements recurring through the manual. The vendor does not state it holds SOC 2 or ISO 27001. https://www.speedlinesolutions.com/support-services · retrieved 2026-08-09

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

commercial-privacy-dsar-tooling

The component operations exist in-product. An individual guest record can be located on the Terminal Customer screen and deleted - 'Delete Customer' and 'Delete Customer Comments' are enumerated Terminal security privileges (terminalsecurityprivilegesdesc.htm) - and customer data can be exported two ways: through the Report Options Wizard in Export Format, saved 'to a number of file formats, including Microsoft Excel (XLS)', where the no-formatting option 'will often give you additional data fields (for example, email)'; or as an automatic Day End text file of names, addresses and order information, scoped to All Customers, New Customers or Customers with Activity. Named shortfalls: both export routes are bulk exports built for marketing and head-office mailings rather than a per-subject DSAR package; no CCPA/CPRA or GDPR request workflow, consent record or subject-request log exists in the 458-topic manual; and no DPA is published - /privacy is scoped to 'the SpeedLine Solutions Inc. website', and the vendor's CCPA advisory is explicitly 'provided this content for informational purposes only', placing the compliance duty on the operator. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/exportcustomerinformation.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read

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

accessiBe is integrated to provide AI-powered ADA accessibility for online ordering — a third-party overlay, which is contested as a conformance strategy. No VPAT or ACR is published, and kiosks are third-party so no kiosk tactile/audio mode is claimed. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01

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

The mechanics are fully configurable and documented. Settings > Money > Tender Types > Tender Surcharge adds a surcharge to a chosen tender type, restricted to selected order types, as 'a flat rate, or a percentage applied to the final amount (excluding tips)', with a Tax Group and an amount, and the manual even shows how to size the percentage so it recoups the processor's fee; Order Types > Order Surcharge applies a per-order-type charge or, with a negative rate, a discount - 'you may want to promote your pick up service by offering a 10% discount for all pick up orders' - with a printed Caption. Named shortfall on network compliance: SpeedLine states plainly that 'SpeedLine cannot detect debit-capable credit cards, including branded gift cards, before they're surcharged. Therefore, we do not recommend setting up credit card surcharging', and its only remedy is manual - create separate Visa Debit, MasterCard Debit, Visa Gift and MasterCard Gift tender types without the surcharge and 'ask the cardholder if their card is a debit or gift card', with online orders told to 'always use the non-surcharged tender types'. There is no automatic exclusion of debit and prepaid cards, and no menu-board disclosure feature is documented. https://support.speedlinesolutions.com/portals/0/customerdocumentation_sf/releasedocs/Store_Manager_help_Web/add_surcharges_for_tender_type.htm · retrieved 2026-08-09 · not refetchable · site policy · graded B when read