Vendors / Pizza & delivery-led
SpeedLine Solutions
dossier live
- Claims in scope
- 311
- Scored
- 311
- Assessed
- 292
- Unknown
- 19
- Not applicable
- 3
- Cells challenged
- 79
Identity
- Owner
- SpeedLine Solutions Inc. — independently held. No parent company, PE sponsor, or acquisition disclosed on the vendor site. Leadership named on About Us: John deWolde (President & CEO), Bryan Champ (Managing Director), Mike Anderson (Product & Senior Development Manager), Scott Sclater (Director, Sales & Marketing).
- Founded
- 1990 (per SpeedLine About Us page). Product lines observed in 2026: SpeedLine+ (cloud-managed) and SpeedLine 8 (legacy on-premise Windows), both actively supported and separately documented in the vendor FAQ.
- Scale
- unknown as a hard number. Vendor claims (claim-level, About Us) it serves 'thousands of restaurants and franchises' across the USA, Canada, Mexico and 'select countries abroad'. Its own Reddit account describes it as 'the leading developer of pizza delivery point of sale software in North America since 1990'. No ARR, location count, or market-share figure is published. Signal of small footprint: only 6 Capterra reviews exist, and SpeedLine does not appear in Capterra's restaurant-POS category listing at all.
- Who it is for
- Independent and small-to-mid multi-unit pizzerias and delivery-led QSRs in North America — the archetypal pizza-only POS buyer. Vendor also markets to sub/sandwich, QSR/fast-casual and full-service, but every flagship capability (dispatch, LiveMaps driver routing, caller-ID pop, placement/portion pizza build, deferred holiday orders) is delivery-pizza-shaped. Enterprise tier (SpeedLink, master menu, chain reporting) targets franchise groups comparing 2 to 100+ locations, per the vendor FAQ.
- Site
- https://speedlinesolutions.com/
Pricing
transparency: quote-only · unit: unknown · processor lock-in: no
- Software
- quote-only. The URL supplied in the brief, speedlinesolutions.com/pricing/, returns HTTP 404 — there is no pricing page on the site and no pricing item in the site navigation. Every CTA routes to 'Book a Demo' or 1-888-400-9185. No tier names, no dollar figures, no per-terminal rate published anywhere on the vendor site or in any of the 12 public PDF brochures reviewed. CAVEAT, third-party and vendor-submitted, not the vendor's own pricing page: Capterra's SpeedLine Pizza POS profile lists a 'Basic' plan at CA$4,300 per user as a ONE-TIME fee (perpetual-license shape, consistent with the on-prem SpeedLine 8 heritage). Treat that as a vendor-supplied directory field, not published pricing.
- Card processing
- quote-only. No rate, markup, or interchange-plus figure is published. The SpeedLine Payments page markets 'lower card-present processing fees' with no number attached. A 'Credit Card Processing Comparison' PDF is offered as a lead magnet rather than a rate card.
- Contract
- unknown — no MSA, terms of service, or subscription agreement is publicly accessible. Note that Support is a separate paid subscription: the vendor states 'A SpeedLine Support subscription includes unlimited phone and email support and SpeedLine software upgrades', and sells tiered Remote / Standard / Premiere / Store Management support levels. Software upgrades are therefore gated behind an active support subscription.
- Early termination
- unknown — no published contract terms.
API posture
public API: partner-gated
- Cost to integrate
- Not free and not published. SpeedLine's own integration material references a third-party integration support and maintenance fee, and requires the store to run a SpeedLine-specified SonicWALL security appliance to expose the Connect socket — an on-prem networking dependency plus recurring hardware/licence cost before a single API call is made. Partner onboarding is 'contact SpeedLine' rather than self-serve. No sandbox, no self-service credentials, no published rate limits, no OAuth (auth is network-perimeter based, not scoped tokens). Revenue-share or referral terms are not published.
- Webhooks
- Partial and partner-only. An 'EventStream' outbound event feed exists and is referenced as the mechanism by which DTiQ, ITech, March Networks, Remote Eyes (video surveillance) and BeerBoard (draft-beer control) synchronize to POS transactions. It is not documented as a customer-configurable HTTP webhook, and there is no public statement of signing, retry, backoff, or replay behavior. The primary integration transport is not webhook-shaped at all: SpeedLine Connect is a request/response XML-over-TCP socket interface to the store's on-premise SpeedLine server.
- Data export on exit
- Better than the API posture suggests, because of the on-prem heritage. SpeedLink Enterprise pushes scheduled data files — including a DayFile (transaction/sales detail), Employee Info, Inventory Period, and Sales Forecast — into a SQL Server database the customer controls, which is a genuine customer-owned raw-data destination rather than a vendor-UI-only export. Store-level SpeedLine 8 data also lives in a local database on hardware the operator possesses. BUT: SpeedLink is a separately licensed enterprise product, not part of a base subscription, and no contract clause on data ownership, post-termination retrieval window, or vendor use of merchant data is published anywhere.
- Notes
- The structural point: SpeedLine's extension model is a 1990s-shaped on-premise integration bus, not a cloud API. Everything third parties do — Onosys, Menufy, Brygid, RTO online ordering; GojiKiosk, Nextep, Checkmate kiosks; Chowly aggregation; Voicify voice AI — is brokered through SpeedLine Connect into the store box. That makes SpeedLine unusually good at headless order injection (many independent front ends drive its transaction engine) and unusually bad at everything a modern developer expects: no public docs, no sandbox, no OAuth scopes, no published rate limits, no changelog or deprecation policy, and a per-integration fee. Notably, SpeedLine is NOT on DoorDash's 2026 Preferred Integration Partner list (Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper), despite operating a direct DoorDash integration.
Capabilities
Every claim is binary and checkable. Grades: A primary documentation · B product documentation · C pricing or feature page · D marketing claim · E third-party reporting · F inference with no source. A yes on a differentiator claim requires A or B.
Order capture & FOH workflow
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-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
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
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
order-capture-bar-tab-preauth differentiator
Unresolved in both directions. SpeedLine does document card pre-authorization, contrary to an earlier reading: the Deferred Orders chapter's Credit Card Options group offers 'Pre-Authorize: Select to pre-authorize credit card payments, in order to reserve the funds in the cardholder account and prevent the authorization from being declined at activation', with a 'Tokenize If Ticket Activation Is in More than X Days' threshold ('The recommended setting is 2 days for Worldpay, and 10 days for Monetra') and a 'Print Tickets with Failed Postauthorizations' option - a real reserve-then-post-authorize cycle, but documented for future-dated orders rather than for an open bar tab. Nothing in the Store Manager or Menu Designer manuals, the 139-topic SpeedLine Portal manual, the SpeedLine 8.0 release notes or 153 support advisories describes a tab construct, a configurable tab authorization amount, incremental re-authorization or stale-tab expiry; the nearest documented mechanism is Station Options > Register > 'Tender Without Closing Order for These Order Types', a paid-then-open ticket for line busting. The order-entry application's own manual, the 150-page Terminal User's Guide, is distributed only inside Store Manager's Document Viewer or sold in print, so the operator-side tab workflow cannot be checked from public sources.
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
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
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
order-capture-qr-same-check differentiator
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
order-capture-kiosk-first-party differentiator
Kiosks are third-party partners only — GojiKiosk, Nextep Systems, Checkmate. No first-party kiosk SKU. https://www.speedlinesolutions.com/partners · retrieved 2026-08-01
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
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
order-capture-voice-ai differentiator
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
order-capture-throttling differentiator
Quoted times auto-extend from kitchen volume. Per-channel per-slot capacity caps not documented. https://www.speedlinesolutions.com/delivery · retrieved 2026-08-01
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
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
order-capture-order-ready-signal differentiator
Unresolved, on corrected grounds - the marketplace documentation IS published, in a manual an earlier pass never found. SpeedLine Plus Portal Help carries SSIO Onboarding Information for DoorDash, Onboarding Information for Uber Eats / Grubhub / ezCater, Store Availability DoorDash / Uber Eats / Grubhub, Menu Management for each, Order Cancel Third Party Marketplaces and Store Hours. Taken together those enumerate what SpeedLine sends outbound to a marketplace: the menu on Make Live, out-of-stock marks set on the Terminal, store hours, a Pause Store / Resume Store availability toggle, and an operator-initiated cancellation - 'The request will be sent to the Third Party Marketplace for approval. A notification will appear in the Terminal notification area to indicate whether the cancellation was accepted or denied.' None of them is an order-ready event, and on the older SpeedLine Connect path the Notifications sub-tab still lists only 'changes to quoted times, activation of deferred tickets, and failed post-authorizations of deferred ticket payments'. But an order-ready callback would be part of the SSIO message contract rather than a configurable setting, and that contract is published nowhere: the Store Manager topic links the onboarding pages to a SpeedLineNext manual whose URLs return a hard IIS 404. Absent in the admin surface is not the same as absent from the protocol. adversarially verified
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
Menu, modifiers & pricing engine
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
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
menu-pricing-fractional-placement differentiator
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
menu-pricing-half-and-half-rule differentiator
'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
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
menu-pricing-size-style-matrix differentiator
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
menu-pricing-included-allowance differentiator
'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
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
menu-pricing-upsell-prompts differentiator
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
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
menu-pricing-countdown-auto-86 differentiator
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
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
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
menu-pricing-dual-pricing differentiator
'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-pricing-versioning-effective-dates differentiator
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
menu-pricing-franchise-hierarchy differentiator
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
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-pricing-recipe-linkage differentiator
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
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
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
Payments & money movement
payments-processor-choice differentiator
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
payments-published-rates differentiator
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
payments-dual-pricing differentiator
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
payments-surcharge-guardrails differentiator
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
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
payments-softpos-tap-to-pay differentiator
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
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
payments-qr-guest-pay differentiator
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
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
payments-tip-pooling differentiator
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
payments-offline-store-and-forward differentiator
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
payments-offline-decline-liability differentiator
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
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
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
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
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
payments-chargeback-tooling differentiator
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
payments-card-on-file differentiator
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
payments-payout-timing differentiator
'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
payments-multi-entity-routing differentiator
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
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
Kitchen & production
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
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
kitchen-course-firing differentiator
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
kitchen-prep-time-pacing differentiator
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-order-throttling differentiator
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
kitchen-channel-pause-propagation differentiator
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
kitchen-order-ready-callback differentiator
No order-ready callback to a marketplace is documented anywhere in SpeedLine's public corpus, and the one manual that would settle it is not published. Read all 784 topics of the four WebHelp manuals now dumped (Store Manager 458, Menu Designer 183, New Features 5, SpeedLine Portal 138), the 8.0 Release Notes to release 8.0.413, and all 153 support advisories. The only documented consequence of a bump is local: 'Print When Bumped events are triggered when the Bump button is pressed on the bump bar or touchscreen monitor', processed by a nominated station to print a ticket. The SpeedLine Connect Notifications sub-tab enumerates what Terminal pushes outward - quoted time changes, deferred ticket activation, failed post-authorisations of deferred ticket payments - with no order-ready event, and the release notes' outbound-status entries are all DoorDash Drive courier ones ('Added support for DoorDash Drive order tracking messages to customers', 'DoorDash Drive delivery requests can now be cancelled'), not marketplace readiness. Correcting the earlier rationale: the SpeedLine Portal help is NOT customer-gated - it is public at support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/ - and it contains no order-status surface. What is unpublished is a separate manual: Enable SpeedLine Marketplace links out to 'SSIO Onboarding Information for DoorDash / Uber Eats / Grubhub' under Portals/0/CustomerDocumentation_SF/SpeedLineNext/SpeedLine_Next_Admin_Help_Web/, and all three of those URLs 404. Unresolved because the SSIO integration contract is where a ready-status callback would be described, and it cannot be read. adversarially verified
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
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
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
kitchen-printer-fallback differentiator
'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
kitchen-offline-operation differentiator
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
kitchen-item-build-screens differentiator
'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
kitchen-pizza-fractional-display differentiator
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
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
kitchen-order-modification-alerts differentiator
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
kitchen-guest-ready-notification differentiator
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
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
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
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
Delivery, dispatch & third-party channels
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
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
delivery-route-map differentiator
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
delivery-driver-tracking differentiator
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-zones-polygon differentiator
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
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
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
delivery-driver-comp differentiator
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
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
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
delivery-daas-fallback differentiator
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
delivery-3p-direct-integration differentiator
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
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
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
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
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
delivery-3p-reconciliation differentiator
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
delivery-injection-error-visibility differentiator
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
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
delivery-promise-time differentiator
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
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
Digital ordering & guest-facing channels
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
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
digital-native-app differentiator
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
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-upsell-engine differentiator
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
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
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
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
digital-kiosk differentiator
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
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
digital-catering-portal differentiator
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
digital-voice-ai-phone differentiator
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
digital-drivethru-ai
SpeedLine markets AI voice ordering for the telephone, not the lane. The 2026 blog post 'Too Many Calls, Not Enough Hands: Can AI Fix the High Volume Crunch?' claims 'the AI assistant handles the entire ordering conversation' with 'Direct injection of structured order data into SpeedLine POS' - it is about unanswered phone calls, names no AI provider, and says nothing about a drive-thru lane or escalation-to-human handoff. Re-searched the full local corpus that now exists: all 784 topics of the four published WebHelp manuals (Store Manager 458, Menu Designer 183, New Features 5, SpeedLine Portal 138), the 8.0 Release Notes through release 8.0.413, and all 153 support advisories. Drive-thru coverage is hardware only - 'Add a Drive-thru Order Confirmation Display', kitchen monitors, station order types - and the Off-Site Ordering chapter lists 'Remote Drive-Thru Order Centers' and 'Automated Telephone Order Services' as example source types SpeedLine Connect can accept orders from, so a third-party lane AI could inject through Connect without SpeedLine documenting it. That is why this cannot be closed either way. No product page for the AI offering exists in the sitemap (574 URLs). adversarially verified
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
digital-google-order differentiator
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
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
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
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
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
digital-guest-data-ownership differentiator
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-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-surcharge-transparency differentiator
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
Guest data, loyalty & marketing
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
guest-loyalty-thirdparty-identity-attach differentiator
Re-checked against the now-public SpeedLine Portal manual, which the earlier pass wrongly recorded as unpublished. The Portal's 138 topics cover menu, store, company, theme, tender, tokenization, loyalty and employee administration and contain no third-party marketplace chapter; the DoorDash, Uber Eats and Grubhub onboarding topics that Enable SpeedLine Marketplace links to point at .../CustomerDocumentation_SF/SpeedLineNext/SpeedLine_Next_Admin_Help_Web/onboarding-doordash.html and its siblings, all of which return 404 on the public host (re-probed 2026-08-09 with a browser and a Googlebot UA). What is newly readable is the SpeedLine Connect field-description set, which documents guest identity for Connect sources generically rather than for marketplaces specifically: the Send Manager Alerts For list defines 'Customer Record Discrepancy - There are differences in the customer information (name, address) at the store and the source' and '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 8.0 release notes record 'Adding or editing a customer through SpeedLine Connect more closely mirrors the process in Terminal' alongside 'New: Direct integrations for DoorDash, Grubhub, and Uber Eats'. So Connect can create and phone-match store customer records, and Uber Eats self-delivery orders demonstrably carry a delivery address (a release-note fix concerns delivery charges on those orders). SpeedLine still never states that a marketplace order creates or matches a Customer record, what guest fields the marketplaces pass through, or whether loyalty can attach to such a ticket - loyalty prompting is documented only as a per-order-type Terminal Customer-screen prompt.
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
guest-loyalty-tiers differentiator
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
guest-loyalty-offline-behavior differentiator
Re-read every loyalty topic across all four published manuals, including the three SpeedLine Portal topics the earlier pass could not see (Add SpeedLine Loyalty, Add Paytronix Loyalty, Add Punchh Loyalty) and the Portal's Enter Loyalty Rewards Program Settings. None describes connectivity loss. The nearest first-party statements are: the SpeedLine Connect manager-alert list, now readable, which defines 'Loyalty Authorization Failure - For example, the store could not contact the loyalty provider'; Paytronix's 'Authorization Timeout (sec) ... The recommended time is 30 seconds; increase this to 60 seconds if authorization problems are encountered'; and an 8.0 release note, 'Enhanced: Improved handling of Punchh connection errors'. All three establish that SpeedLine detects a loyalty outage and tells a manager; none states whether lookup, accrual or redemption is queued, skipped or blocked. Withdrawing the earlier inference: SpeedLine Loyalty is not store-local - the Portal describes it as 'a cardless single or multi-store loyalty option', with rewards defined on a separate 'SpeedLine Loyalty administration site' and surfaced into the Portal, so nothing about the on-premise database implies the program survives an outage. Terminal runtime behaviour is documented in the Terminal User's Guide, which is distributed only inside Store Manager's Document Viewer and is not on the public host.
guest-loyalty-offer-stacking-rules differentiator
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
guest-loyalty-targeted-offers differentiator
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
guest-loyalty-rfm-segmentation differentiator
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
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
guest-loyalty-native-email-sms differentiator
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
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
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
guest-loyalty-campaign-attribution differentiator
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
guest-loyalty-data-export-portability differentiator
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
guest-loyalty-cdp-event-api differentiator
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
guest-loyalty-review-capture-routing differentiator
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
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
guest-loyalty-wallet-pass differentiator
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
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
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
guest-loyalty-ai-offer-recommendation differentiator
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
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
Labor & workforce
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
labor-photo-punch-verification differentiator
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
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
labor-offline-time-punch differentiator
The Time Clock tab is no longer an unreadable image map: its 14 popup field descriptions and its 18-entry control list are both recovered, and together they are the complete configurable surface of the screen - Enable Time Clock, On-Site/Off-Site Tracking (Leave and Return buttons), Alternate Pay When Out of Store, Round to 1/4 Hour on Clock-In/Clock-Out, Auto Log-Off after Clock-In, Print Time Slip, Print Slip on Time Clock Edit, Allow Time Sheet, Include Breaks / Earnings / Period-to-Date, Time Clock Edit Requires Employee Confirmation, and three driver licence/insurance clock-in overrides. Nothing there concerns connectivity, a punch queue or reconciliation. Monitor Time Clock Use, Monitor Terminal Clock-in/out Times, Change Day End Clock-out Options and Delete Old Shift Data are equally silent, 'offline' appears in the manuals only in relation to Worldpay store-and-forward card authorization and to printers, and the 8.0 release notes contain no offline time-clock entry. Left unknown rather than no because the one document that would state Terminal runtime behaviour - the Terminal User's Guide, which this very topic points to for time-clock instructions - is distributed only through Store Manager's Document Viewer and is not published on support.speedlinesolutions.com, so the behaviour may be documented for customers without being publicly verifiable.
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
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
labor-native-scheduling differentiator
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
labor-demand-labor-forecast differentiator
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
labor-realtime-labor-percent differentiator
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
labor-overtime-prevention differentiator
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
labor-break-compliance-by-state differentiator
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
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
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
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
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
labor-qualified-tips-w2-reporting differentiator
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
labor-native-payroll differentiator
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
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
labor-shift-swap-workflow differentiator
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
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
labor-server-performance-metrics differentiator
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
Inventory, purchasing & cost control
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
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
inventory-theoretical-vs-actual differentiator
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
inventory-realtime-depletion differentiator
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
inventory-86-auto-sync differentiator
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
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
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
inventory-vendor-catalogs-edi differentiator
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
inventory-invoice-ocr differentiator
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
inventory-price-change-alerts differentiator
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
inventory-par-auto-suggest differentiator
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
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
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
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
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
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
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
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-native-not-partner differentiator
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
inventory-menu-margin-linkage differentiator
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
Reporting, BI & data access
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
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
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
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
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
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
reporting-server-scorecards differentiator
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
reporting-channel-profitability differentiator
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
reporting-multiloc-drilldown differentiator
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
reporting-custom-report-builder differentiator
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
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
reporting-raw-warehouse-export differentiator
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
reporting-public-api differentiator
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
reporting-webhooks differentiator
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
reporting-api-not-upcharged differentiator
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
reporting-tier-paywall differentiator
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
reporting-history-retention differentiator
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
reporting-anomaly-alerts differentiator
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
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
reporting-guest-cohorts differentiator
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
reporting-sales-forecast differentiator
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
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
Multi-location, franchise & enterprise governance
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
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
multi-location-local-override-policy differentiator
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
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
multi-location-scheduled-publish differentiator
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
multi-location-new-store-template differentiator
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
multi-location-corp-vs-franchisee-roles differentiator
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
multi-location-royalty-calculation differentiator
Re-examined with the three support.speedlinesolutions.com manuals in hand (they were never found by earlier passes). The 11-topic Multi-Store Administration chapter of the 458-topic Store Manager manual covers only Above Store profiles, store/store-group registration and Setting Update Package creation, distribution and implementation; reportdescriptions.htm, self-described as listing all reports on the Reports tab, contains no royalty, ad-fund or franchise-fee report, and no royalty basis or percentage-of-sales setting appears anywhere in the dump. On the marketing side www.speedlinesolutions.com/enterprise describes SpeedLink Enterprise as consolidating sales, payroll, customer, delivery and inventory data and pushing coupons, price changes and setting updates; it says nothing about royalties, and the SpeedLine+ brochure's only franchise line remains "For Franchise Owners: Centralized control with a consistent branding experience." Left unknown rather than no because royalty calculation would live in the head-office SpeedLink Enterprise server, and no manual for that component is published on support.speedlinesolutions.com (help./docs./api./developers.speedlinesolutions.com do not resolve).
multi-location-royalty-collection
Checked the full local dump of the three support.speedlinesolutions.com manuals. Money-side configuration in Store Manager is entirely store-level - tender types, card processing (Worldpay Express/MercuryPay, Monetra), bank options, pay-ins and pay-outs, house accounts and customer credits - and the only ACH-like mechanism documented is customer House Accounts with statements printed for guests, not franchisee fee collection. reportdescriptions.htm, which asserts it lists all reports on the Reports tab, has no franchise statement or fee report; House Account Statement is a customer document. Nothing on www.speedlinesolutions.com/enterprise or in the SpeedLine+ brochure mentions collecting fees from franchisees. Unresolved because, as with multi-location-royalty-calculation, any such function would sit in the SpeedLink Enterprise head-office component, for which SpeedLine publishes no manual on its documentation host.
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
multi-location-normalized-item-rollup differentiator
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
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
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
multi-location-multi-brand differentiator
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
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
multi-location-config-audit-log differentiator
Checked the full dump of the three support.speedlinesolutions.com manuals. reportdescriptions.htm, which states it lists all reports on the Reports tab, contains a System Events report - "Lists the details, date and time of events that were logged during the specified period of time. A specific event type can be chosen on the Event Type page of the report wizard" - but the wizard's event-type list is never enumerated in the manual, and the one narrative description is explicitly open-ended: the System Event log "tracks notable events that are prone to misuse, such as canceling a ticket, clock changes, training mode activity, street and zone table modifications, language filter exceptions, and possible labor code violations for minor employees." Configuration objects named in the claim (price, tax, permission, discount) do not appear in that list, and Time Clock Edits covers only shift edits (original versus edited values). On the distribution side, Setting Update Packages carry an optional free-text Description and can be browsed before publishing, but they are files moved by SpeedLink, FTP, email or USB with no central record of what was applied where; Store Management Services on www.speedlinesolutions.com/support-services offers "weekly reports on system changes" as a paid human service rather than a product feature. Unresolved because the System Events type list is the one place a configuration-change entry could hide and SpeedLine does not publish it; note also the record already holds View Stocking Unit Changes as a narrow inventory-side change history.
multi-location-enterprise-api differentiator
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
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
Hardware & physical footprint
hardware-commodity-devices differentiator
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
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
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
hardware-handheld-battery-swap differentiator
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.
hardware-handheld-lte
Checked the full dump of the three support.speedlinesolutions.com manuals plus www.speedlinesolutions.com. SpeedLine Terminal is a Windows client on the store LAN and every station-side topic (Set Station Configuration Options, Add Secure Card Payment Hardware, Refresh Terminals at Day End) assumes local network reach to the store server and to NETePay/triPOS on a station; the Link/2500 mobile PIN pad is paired to the tablet over Bluetooth on a virtual COM port. The only cellular-capable component documented is the SpeedLine Pay iPhone app, which "communicates securely with a mobile EMV chip card reader, and with the Worldpay Express online server" for payment away from a station - a payment path, not a POS failover. No cellular, LTE, dual-WAN or failover setting appears anywhere in the dump, and the record's existing FAQ citation says mobile ordering works "anywhere within range of your Wi-Fi network". Left unknown rather than no because device connectivity is a property of the third-party tablet and the SpeedLine Minimum Requirements and Supported Hardware document, which supportedhardware.htm points to, is published only behind the customer-site login; help./docs./api.speedlinesolutions.com do not resolve.
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
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
hardware-kiosk differentiator
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
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
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
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
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
hardware-tap-to-phone differentiator
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-pricing-transparency differentiator
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-ownership-vs-lease differentiator
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
hardware-usable-after-churn differentiator
Checked the full dump of the three support.speedlinesolutions.com manuals and the marketing host. The manuals describe SpeedLine as software installed on the operator's own Windows stations (Change Database Backup Interval, Password Maintenance for Windows accounts, C:\SpeedLine\Data folders copied between machines for Above Store profiles) with peripherals configured by make/model on a COM port and payment software (NETePay, triPOS, Monetra) installed under the merchant's own processor accounts - none of which suggests vendor-locked hardware, but none of which is a statement about what happens after cancellation. Neither manual, nor www.speedlinesolutions.com/support-services, nor the Terms of Use page (a website terms-of-use, not a product licence) says whether hardware bought from SpeedLine remains usable with other software. The online store where hardware is purchased, and any warranty or licence terms attached to it, require a SpeedLine Customer Site login (support.speedlinesolutions.com/Store). Left unknown: an inference from architecture is not a vendor statement, and this is a differentiator cell.
hardware-rma-sla differentiator
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
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
hardware-remote-device-management differentiator
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
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
Integrations, API & extensibility
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
extensibility-api-access-cost differentiator
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
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
extensibility-free-sandbox differentiator
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
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
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
extensibility-webhook-reliability differentiator
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
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
extensibility-menu-write-api differentiator
Unresolved rather than absent: the enumeration the `no` rested on is not the message catalogue. SpeedLine Connect (formerly OrderLink Gateway) is a versioned XML protocol - the manuals reference 'SpeedLine Connect/OrderLink Gateway version 2.3 or later' for Notifications and 'the DeliveryDetails request message (added in OrderLink Gateway - now SpeedLine Connect - v2.5)' - and its message specification is distributed to partners and published on no resolving host (api./developers./developer./docs./help./partners./sandbox.speedlinesolutions.com all fail to resolve; support.speedlinesolutions.com/llms.txt 404s). SpeedLine's own SpeedLine Connect product sheet enumerates the payload types directly - "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, Paytronix, or SpeedLine Loyalty" - so menu information is carried over Connect and there is an explicit 'Connect API version'; the sheet does not state the direction, and a 2011 trade account of the same gateway describes third parties being given access to 'add customers, edit customer information, add and recall orders'. What the manuals establish is only that every menu path they document is UI or file based - Menu Designer authoring, File > Export to SpeedDine producing a JSON file that an operator imports into the SpeedLine Portal, and Make Live to publish to a marketplace - plus a manager-alert string ('Menu Designer Configuration Errors - For example, the PLU, item, or size requested does not exist in Menu Designer') that describes an ORDER message naming an unknown item, not a menu message. An error label in a settings-screen alert list is not an API reference with no such field, so this does not meet the positive-evidence-of-absence bar. Re-check if the Connect message specification is ever published.
extensibility-data-symmetry differentiator
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
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
extensibility-doordash-preferred differentiator
Roster confirmed and SpeedLine confirmed absent — but the cited URL (get.doordash.com/en-us/blog/preferred-integration-partners-2026) returns HTTP 404. The live source is about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026. Separately, the note's "consistent with the 250-live-store threshold" is unsupported: DoorDash publishes only that selection was "based on current performance and feature capabilities" and that "partners must meet clear, measurable requirements" — no store-count threshold is disclosed. Delete that clause. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-01 adversarially verified
extensibility-first-party-delivery-integrations differentiator
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
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
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
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
extensibility-bi-data-warehouse differentiator
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
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
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
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
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
extensibility-data-portability-exit differentiator
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
Reliability, offline & operations
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
reliability-offline-card-auth differentiator
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
reliability-offline-decline-liability differentiator
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
reliability-lan-degraded-multi-terminal differentiator
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
reliability-local-transaction-engine differentiator
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
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
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
reliability-sync-conflict-handling
Read the complete published corpus - 784 topics across four manuals including the 138-topic SpeedLine Portal (SpeedDine Admin) help that an earlier pass wrongly recorded as customer-gated, all 870 field-description popups, the public 8.0 Release Notes to release 8.0.413, and 153 support advisories - and no conflict-resolution rule for concurrent edits during a network partition is stated anywhere. What the documentation does describe is a single-writer topology: 'your SpeedLine database is automatically backed up (copied) from the primary server (typically Station1) to the secondary server' at a recommended one-minute interval (change_database_backup_interval), with the secondary passive until the primary is unusable, and the same pattern for KDS ('The secondary CSK/KDS server acts as a backup if the primary KDS server is not active'). Between the two authoring surfaces that can genuinely diverge - the Portal menu and the in-store menu - the rule is directional rather than a merge: Automatic Menu Version Synchronization queries the in-store menu every 30 minutes and 'Website prices and coupons, the file name, and version are updated to those of the current in-store menu', with divergence surfacing as a PLU price error to be fixed by hand. That is an architecture that avoids the conflict, not a documented resolution behavior, so the claim remains unresolved.
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
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
reliability-contractual-uptime-sla differentiator
No uptime percentage or service-credit remedy is published anywhere reachable. The three public legal documents are /terms (a website Terms of Use that disclaims warranties for the web site and says nothing about the POS or hosted services), /privacy, and /speedlinepayappprivacy (a MobilePay app privacy policy, in effect since 15 February 2023); /legal 404s and the complete 574-URL sitemap.xml has no SLA, security or trust page. /support-services describes support tiers - Standard, Premiere, Store Management, Second-Level - and says 'A SpeedLine Support subscription includes unlimited phone and email support and SpeedLine software upgrades', with no availability commitment. I also searched the corpora that were unavailable at first scoring: 784 published manual topics, the public 8.0 Release Notes and all 153 support advisories contain no uptime figure, no service-level language and no credit remedy. The customer agreement covering SpeedLine POS, SpeedDine and Cloud Reporting and Analytics is not public, so whether the standard agreement carries an SLA cannot be determined.
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
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
reliability-onsite-install differentiator
'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
reliability-menu-build-service differentiator
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
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
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
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
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
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
reliability-failover-terminal-role differentiator
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
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
Commercial, compliance & data ownership
commercial-month-to-month-contract differentiator
No subscription term for the core POS is published anywhere public. /pricing 404s and the complete 574-URL www.speedlinesolutions.com sitemap.xml contains no pricing page at all - only an /roi-calculator, a /bundled-pos-calculator and /pos-quotes-comparing-apples-to-apples. Three legal documents are public - /terms and /privacy (both footer-linked) and /speedlinepayappprivacy (a MobilePay app privacy policy, reachable only from the app and the sitemap) - and none contains a subscription or term provision. The manuals route every commercial question to a person ('contact your SpeedLine account manager', 'contact your SpeedLine sales representative for options and pricing' for triPOS, SpeedLine Pay and LiveMaps), and /support-services describes a 'SpeedLine Support subscription' that 'includes unlimited phone and email support and SpeedLine software upgrades' without stating its term. The 153 support advisories add only that upgrades are 'included in your support services subscription or may be purchased separately if you are not currently on support', and that SpeedDine is sold 'for a flat monthly fee' - a monthly-billed add-on, which says nothing about a minimum term on the POS software itself. Whether a month-to-month option exists is a quote-level fact that is not public.
commercial-no-early-termination-fee differentiator
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
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
commercial-processing-not-bundled differentiator
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
commercial-interchange-plus-published differentiator
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
commercial-rate-increase-clause differentiator
SpeedLine sells first-party processing (SpeedLine Payments, /speedlinepayments and /speedline-payments-information) and integrates Worldpay Express/triPOS, MercuryPay and Monetra, but no merchant processing agreement, fee schedule or rate-change clause is published: /pricing and /legal 404, the complete 574-URL sitemap.xml carries no agreement page, and the three public legal documents are the website Terms of Use, the Privacy Statement and the MobilePay app privacy policy, none of which addresses processing economics. Processing appears in the documentation only operationally - add_surcharges_for_tender_type.htm explains how to compute a tender surcharge that recoups the processor's percentage fee, and a marketing advisory estimates 'savings of up to $4200 per year in lower processing rates' for a $20-ticket delivery store - and never contractually. The 153 support advisories, including the 37 Monetra and 5 Worldpay platform notices, announce security releases and platform changes, never pricing changes or a rate-change right. The processing agreement is not public, so a cap, prohibition or penalty-free-exit right can be neither confirmed nor denied.
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
commercial-module-unbundling differentiator
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
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
commercial-hardware-not-locked differentiator
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
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
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
commercial-export-customer-and-loyalty differentiator
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
commercial-post-termination-export-window differentiator
No contractual retrieval window is published. The public legal surface is three documents - /terms, /privacy and /speedlinepayappprivacy - /legal 404s, and the 574-URL sitemap.xml has no agreement page; the only retention language anywhere is the MobilePay app policy's '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', which is not a post-termination export term. What the documentation establishes is a practical, not contractual, position: SpeedLine POS is on-premise, the database is copied from the primary station to the secondary every minute and the DayFiles sit on operator hardware (change_database_backup_interval.htm, change_file_backup_settings.htm, restore_data_from_a_backup.htm), the operator can export customer data and reports at will (exportcustomerinformation.htm, exportreports.htm), and SpeedLine's own CCPA advisory states '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.' That says nothing about the hosted side - Cloud Reporting and Analytics and SpeedDine - for which no retention or post-termination export term is published. Unresolved.
commercial-data-ownership-clause differentiator
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
commercial-source-available-selfhost
Fully proprietary. No source is published under any licence and no self-hosting option is offered — though the product is, unusually, on-premise deployed.
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
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
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
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
commercial-wcag-kiosk-accessibility differentiator
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
commercial-dual-pricing-compliant differentiator
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
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 184 values — 68 upheld, 7 downgraded, 4 upgraded. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Pricing and identity
| Field | Verdict | What the verifier found |
|---|---|---|
| pricing.url | upheld | Independently confirmed HTTP 404. No pricing page exists. source |
| pricing.software | upheld | Verified on Capterra: starting price CA$4,300 per user, one-time payment, not monthly. Also verified the 6-review / 4.7-rating figure used in the complaints section. Correctly labelled as a vendor-submitted directory field rather than published pricing — this is the right handling and should not be promoted to a pricing fact. Sole evidence was www.capterra.com, which the source policy forbids as evidence for a capability claim. Requires re-verification against the vendor's own documentation. |
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| reliability-offline-order-entry | yes / documented | downgrade-to-partial | 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. source |
| extensibility-data-symmetry | no / inferred | downgrade-to-unknown | I read the SpeedLine Connect flyer directly. It says Connect "messages pass data back and forth" and enumerates message contents including "Customer records", "Employee shift information", "Menu information", "Delivery zones" and "Store hours and quoted times". Direction per object is unspecified, so a flat "no write path for employees, inventory or customers" is not supported by the cited document — it is contradicted by it as much as supported. Unknown is the honest score. source |
| extensibility-api-access-cost | no / documented | upheld | 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 guidance with an explicit disclaimer that it "is general in nature". "Mandated SonicWALL appliance" should be struck from the narrative. source |
| extensibility-doordash-preferred | no / documented | upheld | Roster confirmed and SpeedLine confirmed absent — but the cited URL (get.doordash.com/en-us/blog/preferred-integration-partners-2026) returns HTTP 404. The live source is about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026. Separately, the note's "consistent with the 250-live-store threshold" is unsupported: DoorDash publishes only that selection was "based on current performance and feature capabilities" and that "partners must meet clear, measurable requirements" — no store-count threshold is disclosed. Delete that clause. source |
| labor-minor-labor-rules | yes / documented | downgrade-to-partial | 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. source |
| reporting-anomaly-alerts | yes / documented | upheld | 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. source |
| reporting-realtime-dashboard | yes / documented | upheld | 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. source |
| kitchen-station-routing | yes / documented | upheld | 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. source |
| kitchen-channel-pause-propagation | yes / documented | upheld | Capability confirmed, but not by the cited source. I read the full SpeedLine Marketplace brochure PDF and it contains no pause feature at all. The claim is on the web page: "Allows you to pause online orders from all third-party marketplaces in one convenient place." Re-point the citation to https://www.speedlinesolutions.com/speedline-marketplace. source |
| delivery-zones-polygon | yes / documented | upheld | 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. source |
| delivery-zone-pricing | yes / documented | upheld | 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. source |
| delivery-dispatch-board | yes / documented | upheld | 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. source |
| delivery-daas-dispatch | yes / documented | upheld | Confirmed in first-party product literature, stronger than the partners-page citation: SpeedLine+ brochure, "DoorDash Drive: Effortless delivery management by assigning orders to DoorDash drivers from our POS Dispatch screen." source |
| menu-pricing-fractional-placement | partial / documented | upheld | I read the brochure image directly. Order screen shows a Full / 1st Half / 2nd Half row, sizes Mini/Small/Medium/Large/Xtra Large, crusts Regular/Thin/Deep Dish/Gluten Free/Whole Wheat, and modifier row Light/Heavy/On Side/Xtra Cheese/Xtra Sauce. The SpeedDine cart also shows "Large Half & Half — Hand Tossed, Left Create Your Own [...], Right Create Your Own [...]", proving halves carry through to online. No quarters, no per-section pricing config anywhere. Partial is correct — resist any urge to call this "yes". source |
| menu-pricing-half-and-half-rule | unknown | upheld | Held to the highest bar as instructed. Placement UI is proven; the pricing rule (higher half vs average vs fractional) is stated nowhere in the brochure, the SpeedDine page, the FAQ or the Marketplace brochure. Correctly unknown. source |
| menu-pricing-channel-price-books | yes / documented | upheld | 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." source |
| delivery-86-sync | yes / documented | upheld | 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. source |
| labor-native-scheduling | yes / documented | upheld | 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. source |
| labor-payroll-export-formats | partial / documented | upheld | 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. source |
| order-capture-native-handheld | partial / documented | upheld | 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. source |
| digital-checkout-pci-sca | partial / documented | upheld | 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. source |
| reliability-247-live-support | partial / documented | upheld | 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. source |
| multi-location-royalty-calculation | unknown | upheld | Held to the highest bar. The only franchise statement in first-party literature is the SpeedLine+ brochure's "For Franchise Owners: Centralized control with a consistent branding experience." No royalty calculation, percentage-of-sales rule, or collection mechanism appears in any brochure, the enterprise page or the FAQ. Unknown is correct; same for multi-location-royalty-collection. source |
| extensibility-oauth-partner-apps | no / documented | upheld | 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. source |
| extensibility-order-injection-api | yes / documented | upheld | 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. source |
| payments-processor-choice | yes / grade D, cites the marketing FAQ | downgrade-to-partial | The sole evidence was the FAQ line "SpeedLine allows you to use the processor of your choice so you can obtain the best rate" - a marketing sentence, grade D, which cannot carry a yes on a differentiator. I located the Store Manager Help admin guide myself and it contradicts the unbounded reading: Enter Credit Card Settings states "Either Monetra or Worldpay payment processing software must be set up before credit card payments can be processed through Terminal", and the Card Processing chapter lists only Monetra, Worldpay Express and Worldpay MercuryPay. Set Up Worldpay Express Processing adds that "SpeedLine supports two Worldpay platforms: Express and DataCap (MercuryPay)" and that EMV requires Worldpay triPOS bought via a SpeedLine sales rep. A two-vendor Processor Interface list is real choice but bounded choice, and no acquirer list behind Monetra is published. Partial, with the shortfall named. source |
| commercial-processing-not-bundled | yes / grade D, cites the marketing FAQ | upheld | Value upheld but the evidence was replaced, because the FAQ could not carry a differentiator yes. I went to the Store Manager Help admin guide and found the affirmative documentation the researcher never cited: Set Up Monetra Payment Processing describes "third-party payment processing software that allows your SpeedLine point of sale system to process payment cards" with "Payments will be settled into your bank account at day end using the Monetra software". Settlement runs to the merchant's own bank account through software SpeedLine does not own, and integrated processing is opt-in via a Process Cards checkbox. That is documented absence of an in-house processing lock, so the cell survives at grade B rather than D. What I could not establish, and what stops this being airtight: no MSA or price sheet is public, so a rate penalty for declining SpeedLine Payments remains unfalsifiable. source |
| menu-pricing-fractional-placement | partial / B - "No quarters, no per-section pricing config anywhere. Partial is correct - resist any urge" | upgrade-to-yes | The cited hubfs URL 404s; it was a truncated path to the SpeedLine+ brochure, which I recovered and read, but a brochure is only marketing. I then found SpeedLine's Menu Designer manual, which the record had never used. Create Portions defines portions as percentages and gives 33% thirds as a worked example; Add Quantity, Portion or Other Linked Button Sets lists 1st through 4th Quarter as shipped Portion link types; and the Portion Price Method list offers five pricing rules including Independent Portions, which charges toppings on each portion as if it were an individual item. Quarters exist and per-section pricing is configurable, so both grounds for the partial fail. This differentiator yes is carried at grade B by vendor product documentation. source |
| menu-pricing-topping-quantity-tiers | partial / B - "Light / Heavy / On Side / Xtra Cheese / Xtra Sauce shown as first-class buttons distinct" | upheld | The cited hubfs URL 404s. I replaced it with the Menu Designer Modifier Types topic, which both confirms the tiers as first-class actions and names the exact limitation the researcher could only guess at: Light and Heavy multiply topping WEIGHT (0.5x, 1.5x) and explicitly do not affect price, while Double and Triple multiply cost and weight by a fixed 2x and 3x. No configurable per-tier price multiplier appears anywhere in the 183-topic manual, which I downloaded in full and searched. Partial stands, now with a documented shortfall. source |
| menu-pricing-size-style-matrix | partial / B - "Two visible axes - size (Mini/Small/Medium/Large/Xtra Large) and crust (Regular/Thin/Deep" | upheld | The cited hubfs URL 404s, so the brochure screenshot the axes were read from is not retrievable at that address. I worked the Menu Designer manual instead: Understanding Prices enumerates exactly three price node types, and Price a Sized Item shows the Multi Price table is sizes by quantity level. Crust is a modifier, and modifier price nodes can be sized and restricted to an item, so a per-(size, crust) amount is reachable as base plus modifier - but nothing in the manual describes a two-variant-axis price grid on the item itself. Partial now stands on documentation rather than on a picture. source |
| menu-pricing-allergen-nutrition | partial / B - "SpeedDine menu displays per-item calories online. Structured allergen flags and recipe-de" | upheld | The cited hubfs URL 404s. I recovered the brochure at its real address and then read the Menu Designer manual. The only allergen facility documented is the free-text Help Text tab ("allergy warnings"), shown in a Terminal pop-up to staff; grepping the whole downloaded manual returns no occurrence of nutrition or calorie as a menu field, and Item Contents nodes carry ingredient amounts and unit weights for inventory and make tickets only. The online calories are part of the SpeedDine description copy, not a stored value published from the item record. Partial stands, with the shortfall now named from documentation rather than inferred from silence. source |
| kitchen-pizza-fractional-display | partial / E - "Placement (1st Half / 2nd Half) and quantity modifiers exist in order entry and Make Rout" | upheld | The cited hubfs URL 404s, which removed the record's only support here. I downloaded the whole 183-topic Menu Designer manual and searched it: make tickets and kitchen displays are documented (make routes, modifier order, item contents on tickets, highlighted modifier types), and portions are documented separately, but no topic joins them - nothing shows a portion caption or a sectioned layout on a make ticket or make-line screen. Store Manager's Kitchen Monitors topic further shows the make-line screen is QSR Automations CSK/KDS, a third-party product whose rendering SpeedLine does not document. Partial stands, and the grade rises from E to B because it now rests on vendor product documentation. source |
| delivery-daas-dispatch | yes / B - "Confirmed in first-party product literature, stronger than the partners-page citation: Spe" | upheld | The cited hubfs URL 404s. The quote was real - the path had been truncated at the space in 'SpeedLine+ brochure.pdf' - and I re-downloaded the brochure and confirmed the DoorDash Drive line verbatim. I then upgraded the evidence from marketing to administration documentation: Store Manager Help documents the 3rd Party Delivery tab, the DOORDASH entry appearing in the Terminal Dispatch driver list, and a dedicated Assign Ticket to 3rd Party Delivery Service privilege. The DoorDash Drive brochure supplies the return leg - estimated pickup and delivery times reviewed before confirming, order status inside Terminal. Yes stands, now on a live retrievable citation. source |
| order-capture-coursing-hold-fire | unknown | resolve-to-no | Three enumerated configuration surfaces (Order Types Printing tab, Table Service General tab, Terminal security privilege set) plus a full-text search of all 646 topics: the word 'course' occurs only as the Kitchen Monitors 'Start New Course' setting, which controls where ADDITIONS to a completed order appear on the KDS grid, not culinary coursing. source |
| order-capture-bar-tab-preauth | unknown | resolve-to-no | Enumerated the Station Options Register tab, the Order Types General tab (20 settings), the whole Card Processing settings group and the complete Terminal privilege list. Pre-authorization appears nowhere across the 646 topics, and the vendor documents a different mechanism for holding an open ticket. source |
| order-capture-transfer-audit | unknown | resolve-to-partial | Transfer between servers, tables and seats is documented at privilege level; the two-named-employee audit line is not visible in the published corpus because the Terminal User's Guide is a customer-portal PDF outside the three WebHelp manuals. source |
| order-capture-drive-thru-timers | unknown | resolve-to-no | The Reports tab catalogue asserts its own completeness and contains no speed-of-service report; the Hardware chapter's only drive-thru topic is a display integration. 'Speed of service' returns nothing across all 646 topics. source |
| menu-pricing-nested-modifiers | unknown | resolve-to-partial | Min/max and required-selection are documented per enforced-modifier node, so the cell is not unknown; the three-level nesting depth the claim asks for is not documented anywhere in the 183-topic Menu Designer manual. source |
| menu-pricing-half-and-half-rule | unknown | resolve-to-yes | The Portions tab is the entire configurable surface for portion pricing and it exposes at least three of the rules the claim names (higher-priced half, averaged, fractional). Grade B primary product documentation, which meets the differentiator bar. The previous rationale's premise - that the rule is 'stated nowhere' - was true of the marketing corpus only; the Menu Designer manual states it outright. source |
| menu-pricing-included-allowance | unknown | resolve-to-partial | Overage-only charging is documented as a first-class price node type; the substitution credit/forbid half of the claim is absent from the Menu Designer pricing chapter, which enumerates its price node types (Single, Multi, Manual) and selection types exhaustively. source |
| menu-pricing-countdown-auto-86 | unknown | resolve-to-partial | Scheduled auto-restore at day end is documented and configurable, so the cell is not unknown; the decrement-on-sale countdown that triggers the 86 is not documented, and the feature's two settings topics enumerate its whole surface. source |
| menu-pricing-dual-pricing | unknown | resolve-to-no | The Menu Designer pricing chapter enumerates its price node types and the dimensions an alternate price may vary by; tender is not among them. 'Cash discount' and 'dual pricing' return zero hits across all 646 topics, and the vendor documents a different mechanism for the same commercial goal. source |
| payments-dual-pricing | unknown | resolve-to-no | Two enumerated settings screens (Tender Surcharge tab, Format Printed Tickets) plus the Menu Designer price model. SpeedLine implements the economics as a surcharge line; it does not store two prices per item nor print both totals. source |
| payments-surcharge-guardrails | unknown | resolve-to-no | An explicit vendor statement of absence rather than an inference: SpeedLine says the product cannot perform the debit/prepaid detection the claim requires, and the surcharge screen's complete field set contains no cap enforcement. source |
| payments-qr-guest-pay | unknown | resolve-to-no | The printed-check content surface is enumerated and its single QR option is documented twice as staff-scanned. That is positive evidence about what the code is for, not merely a failed search. source |
| payments-tip-adjust | unknown | resolve-to-partial | Both flows exist in the documentation, so this is not unknown; but the two qualifiers the claim adds - a documented batch/adjust window and an unadjusted-tips manager screen - are absent from the Card Processing settings group and from the self-described complete Reports catalogue. source |
| payments-tip-pooling | unknown | resolve-to-no | 'Pool', 'tip out' and 'tip share' return zero hits across all 646 topics, and the three enumerated surfaces that would have to hold such a rule - Employee Options tip settings, the Terminal tip privileges, the complete report catalogue - attach every tip to one named employee's bank. source |
| payments-offline-store-and-forward | unknown | resolve-to-yes | Primary settings documentation naming both a per-transaction and a cumulative offline ceiling. Retrieved from the topic's popup fragment at .../Store_Manager_help_Web/jspopups/enable_store_and_forward.js, which carries the field text the rendered topic shows only as an image hotspot. source |
| payments-offline-decline-liability | unknown | resolve-to-yes | An unusually explicit publication of offline decline liability in vendor documentation, with a documented post-reconnect notification path. Recorded as yes with the alert-versus-report distinction stated in the note so a reader is not misled. source |
| payments-house-accounts | unknown | resolve-to-yes | All three elements of the claim - per-account credit limits, running balance, periodic statements - are stated in the settings topic and reinforced by the Terminal privilege set. source |
| payments-payout-timing | unknown | resolve-to-no | Positive structural evidence rather than a failed search: the card-processing chapter documents settlement as an action of third-party processor software into the merchant's own bank account, which is the reason no SpeedLine deposit schedule exists. source |
| payments-multi-entity-routing | unknown | resolve-to-partial | Per-location settlement destinations follow directly from the documented per-store credential model, so the cell is not unknown; but the 'single account, split settlement, unified reporting' shape the claim describes is not what SpeedLine documents. source |
| kitchen-expo-consolidation | unknown | resolve-to-partial | The Kitchen Monitors chapter is the entire POS-side surface of SpeedLine's kitchen display integration and it names the third-party dependency explicitly. Expo screens are reachable only through QSR CSK/KDS, and the consolidation semantics the claim describes appear in neither manual. source |
| kitchen-course-firing | unknown | resolve-to-no | Same enumerated surfaces as order-capture-coursing-hold-fire, plus the Kitchen Monitors General tab's complete field list (Active, primary and secondary server address and port, Send End Of Day, Reset Activity Level, Start New Course, Virtual Display print check boxes, Send Employee Name), which contains no course firing. source |
| kitchen-bump-bar-hardware | unknown | resolve-to-partial | Bump bar support is stated in the product documentation; the claim's 'documented supported models' half is explicitly deferred to an off-web-help PDF, which is a named shortfall rather than an absence of the capability. source |
| kitchen-all-day-counts | unknown | resolve-to-partial | The POS-side setting exists specifically so KDS summary tables aggregate correctly, so the capability is reachable, but only through the separately licensed QSR product and without documented per-modifier aggregation. source |
| kitchen-printer-fallback | unknown | resolve-to-partial | Designated backup printers exist and fail over automatically for one failure mode; the vendor documents the other failure mode as potentially undetectable and manually handled, and the KDS secondary server is an operator-selected switch, so 'automatic, no ticket loss' is only partly true. source |
| kitchen-item-build-screens | unknown | resolve-to-yes | Explicit vendor documentation of ingredient-level build detail on station screens, configured by a named check box. The units caveat is recorded in the note rather than treated as a shortfall, since the claim accepts recipe steps, portioning or full modifier breakout. source |
| kitchen-recall-refire | unknown | resolve-to-partial | Recall of a saved ticket and reprint of kitchen instructions without re-entering the order are documented, and per-item reprint exists for labels; the unbump and per-item kitchen refire halves are not, and sit inside the third-party display product. source |
| kitchen-order-modification-alerts | unknown | resolve-to-partial | Three named highlight settings make this real for printer-based kitchens, so the cell is not unknown; the display-based half of the claim is only partly served, hence partial with the print/display split named. source |
| kitchen-waste-logging | unknown | resolve-to-no | Positive evidence of a different mechanism rather than a failed search: the vendor documents where waste and remakes ARE logged (Inventory adjust batches and Terminal voids with reasons), and the enumerated Kitchen Monitors settings surface provides no inbound path from the display. source |
| delivery-driver-tracking | unknown | resolve-to-no | Read the whole LiveMaps/Delivery Service chapter and the dispatch-screen topics in the dumped Store Manager manual. Driver comms are an emailed ticket list plus mapping links keyed to the driver's own phone; the dispatch Out Store view tracks manual on-way/delivered ticket state. No driver app, no position feed, and the marketing delivery page sends the operator to DoorDash's portal for third-party tracking. source |
| delivery-daas-fallback | unknown | resolve-to-partial | The Activate 3rd Party Delivery Service topic documents the entire feature: a virtual DOORDASH driver in the Terminal dispatch list that staff assign to by hand. Every setting on the tab is listed and none is a rule; the companion topic exists only to add a column showing which tickets a human already assigned. source |
| delivery-injection-error-visibility | unknown | resolve-to-partial | Read the whole Off-Site Ordering chapter (Connect activation, general properties, restrictions, connection, notifications, secure connections, Control Connect Service Count) plus Enable SpeedLine Marketplace. Two named price/tax manager alerts are the only operator-facing anomaly surface; failure handling otherwise reads as silent rejection at the source. source |
| delivery-offline-behavior | unknown | resolve-to-partial | Searched the dumped manuals for outage/offline/connectivity language. Exactly two delivery-relevant offline behaviours are stated - the address-validation skip and card voice authorization - and both are named as remedies for an internet outage. Dispatch and driver settlement behaviour during an outage is nowhere addressed. source |
| digital-qr-table | unknown | resolve-to-no | Read Activate SpeedLine Pay, the Ticket Print Options topics, the Table Service topics and the SpeedDine Connect-source tutorial. Every QR occurrence in the 646-topic corpus is either the SpeedLine Pay setup/ticket code scanned by staff or a printed survey link; no guest-scanned order-or-pay flow that opens or attaches to the existing check exists in the documentation. source |
| digital-sms-ordering | unknown | resolve-to-partial | Read the full Customer Messages chapter (Twilio setup, test SMS, delivery confirmation SMS, confirmation emails, Tattle survey) - all outbound - then found the vendor's AI-ordering blog post claiming text-based ordering with direct injection into the POS. A marketing claim with no named provider and no documentation is not a documented capability, but it is more than nothing. source |
| digital-surcharge-transparency | unknown | resolve-to-partial | Read Add Surcharges for Tender Types, Add Duplicate Tender Types and Change Order Surcharge or Discount. The mechanism is real and order-type scoped with an on-ticket caption, but the vendor documents that it cannot enforce the card-brand rule and advises non-surcharged tenders for online orders, which is a material limit on exactly the parity the claim asks about. source |
| guest-loyalty-tiers | unknown | resolve-to-partial | Read the enumerated Set Point Accumulation and Enter General Loyalty Settings topics (which fix the single-store program's entire configurable surface), the SpeedLine/Paytronix/Punchh setup topics, the three Menu Designer loyalty-integration topics and the vendor's SpeedLine Loyalty launch advisory. Multi-level rewards are documented; automatic status promotion/demotion on a rolling window is not. source |
| guest-loyalty-rfm-segmentation | unknown | resolve-to-yes | Read the full Report Descriptions topic, which states it lists all reports in the Reports tab, plus the Customer Messages chapter. New/Active/Frequent/Lazy plus Customer Sales cover the new-regular-at-risk-lapsed lifecycle, are computed by the product (the Lazy report explicitly against each customer's own prior pattern), and require no query building. source |
| guest-loyalty-consent-management | unknown | resolve-to-partial | Read Market with E-mail, Enter Email Settings, Send E-mail to Customers, the Customer Export field list in Report Descriptions and the whole Twilio SMS trio. A dated per-guest email opt-in exists and gates sending; per-channel consent, source of consent and platform-side revocation do not. source |
| guest-loyalty-10dlc-registration | unknown | resolve-to-no | The Connect Twilio topic plus Send Test SMS and Send Delivery Confirmation SMS are the complete documented SMS surface and they are a finished end-to-end procedure. Registration is left entirely inside the operator's own Twilio account, unmentioned, so the claim's 'handles or explicitly documents' fails on both limbs. source |
| guest-loyalty-referral-program | unknown | resolve-to-partial | Found a first-party statement that referral rewards ship in SpeedLine Loyalty Basic, which moves this off unknown, but the coupon and loyalty documentation in both manuals contains no per-guest code, attribution or two-sided reward construct, so it cannot be scored yes. source |
| guest-loyalty-privacy-rights-tooling | unknown | resolve-to-partial | Read Clear Old Customer Records, Delete Old Transaction Data, Delete Old Shift Data, Export Customer Information, the Customer Export field list and the Terminal privilege set, then SpeedLine's CCPA support advisory. Single-record deletion and full export are both available to an admin, but there is no DSAR workflow and deletion demonstrably does not propagate. source |
| guest-loyalty-redemption-fraud-controls | unknown | resolve-to-partial | Read the complete Terminal and Store Manager security privilege descriptions and the complete Report Descriptions list. Manager-approval-with-cap on manual point adjustments and a per-guest loyalty transaction log are both documented; velocity limits and self-redemption flagging appear in neither the privilege set nor the report set. source |
| labor-photo-punch-verification | unknown | resolve-to-no | The Change the User Access Method topic is a settings screen whose options are the whole configurable surface for how an employee identifies themselves to SpeedLine, and it offers exactly two. Cross-checked against the Finger Sensors chapter, Set Up Time Clock Options and the full Terminal privilege list - no photo or facial capture anywhere. source |
| labor-geofenced-mobile-punch | unknown | resolve-to-no | Checked the User Access Method enumeration, every Time Clock topic, the complete Terminal privilege list and the 7shifts partnership advisory. Terminal is the punch device and the third-party labor integration consumes Terminal punches rather than replacing them; no location-restricted mobile clock-in is offered. source |
| labor-fair-workweek-support | unknown | resolve-to-partial | Read the whole Scheduling chapter and the Employee Work Restrictions topics - nothing about predictive-scheduling ordinances - then found the first-party 7shifts partnership advisory, which names Fair Work Week compliance as a capability of the partner platform reached through the SpeedLine Plus integration. source |
| labor-tip-pooling-rules | unknown | resolve-to-partial | Searched the dumped manuals for pooling, tip-outs and tip sharing - none, only tip entry limits, declared-tip prompting and reporting - then found the first-party 7shifts advisory describing customizable tip pool contribution and distribution logic driven by SpeedLine Terminal labor data. Present, but only via the partner platform. source |
| labor-tip-distribution-audit-trail | unknown | resolve-to-partial | Read the complete Report Descriptions list, Export Reports, Control Tip Reporting and the Time Reports privileges. Tips received per employee per shift are retained and exportable for audit; contributions to and distributions from a pool are not SpeedLine data at all. source |
| labor-qualified-tips-w2-reporting | unknown | resolve-to-no | Customize Export of Employee Shifts for Payroll enumerates every column of both ADP formats - an export schema with no such field, which is the enumeration standard. Tips arrive as a single total; cash versus charged separation and any occupation coding are absent. source |
| labor-shift-swap-workflow | unknown | resolve-to-partial | Read the whole Scheduling chapter plus Schedule Requested Days Off and the complete Terminal privilege list - manager-entry only, view-and-print for staff - then found the first-party 7shifts partnership advisory documenting employee-initiated swaps and shift-pool claiming under manager approval via the SpeedLine Plus integration. source |
| inventory-unit-conversion-yields | unknown | resolve-to-partial | Three unit roles plus explicit multipliers are documented on the Stock Items Custom Conversions tab (unitsofmeasure.htm, addacustomunitconversion.htm, addstockcountingunits.htm). The yield/waste-percentage half of the claim is absent: a grep of the full local dump of all three SpeedLine manuals returns no yield, shrinkage or usable-percentage field on a stock item; waste is a separate posted batch. Partial, not yes. source |
| inventory-count-modes | unknown | resolve-to-partial | countingstockitems.htm enumerates the whole count-batch construction surface (five Add options) and states the one-open-count constraint verbatim; reportdescriptions.htm and inventory_report_descriptions.htm are self-described complete report lists and contain no cycle-count schedule report. Full and ad-hoc counts yes, scheduled recurring cycle counts not documented. source |
| inventory-mobile-count-offline | unknown | resolve-to-no | Enumeration bar met on the workflow, not on an overview: the six-topic Stock Counts chapter (countyourstock, countingstockitems, postcountbatch, correctcountmistakes, addstockcountingunits, addchangestockcountlocation) is the complete documented counting surface and every step is print-then-key. A grep of the whole 1.7MB dump of all three manuals for barcode/scanner returns only coupon bar codes, Punchh loyalty bar codes, SpeedLine Pay QR codes and fingerprint/mag-card employee login. Recorded as no for the counting application specifically; the manuals are end-user application manuals and would not describe a separately marketed mobile tool if one existed. source |
| inventory-vendor-catalogs-edi | unknown | resolve-to-partial | Named distributor integration is real and first-party documented (McLane SourceLink, catalog dictionary plus electronic receives; Sysco and Agar named for the .psf route). The order-transmission half of the claim fails: createprintpurchaseorder.htm ends at "Click the Printer button and follow the Report Options Wizard instructions to print the purchase order", and export_purchase_orders_at_eod.htm sends the .pof to head office, not to the supplier. source |
| inventory-invoice-ocr | unknown | resolve-to-no | Two independent enumerations, both of the qualifying kind: the Receive wizard's source selection is the entire set of ways stock can enter a receive batch, and packing_slip_file__psf_format.htm is a published schema with no document-image or attachment field. Absence here is a closed-surface finding, not a failed search. source |
| inventory-price-change-alerts | unknown | resolve-to-partial | Price history half documented at grade B on the receive and costing topics. Alert half: the Inventory Options tabs enumerated by the setup tutorial (General, Purchase Orders, Void, End of Day, Initial Settings, Supplier Specific, Imports) and the self-described complete Inventory report list contain no configurable price-threshold alert. source |
| inventory-par-auto-suggest | unknown | resolve-to-partial | Par plus computed suggested order quantity is documented verbatim at grade B. The forecast-driven half fails: across all three manuals, sales forecasting appears only under Operations Planning (prep plans) and labour scheduling, and the Purchase Order topics offer only the static Target Stock Quantity. source |
| inventory-waste-logging | unknown | resolve-to-partial | Structured waste batch, stock debit and separate waste reporting all documented at grade B. The reason-code element of the claim is contradicted by the same topic, which specifies a free-text Reference; the contrast with SpeedLine's maintained void/comp reason lists makes that a deliberate design, not an omission in the docs. source |
| inventory-transfers | unknown | resolve-to-partial | Inter-store transfer exists and is valued, so not unknown and not no; but the two-sided, in-transit/approval structure the claim asks for is contradicted by the topic itself, which instructs the receiving store to post an independent receive batch. source |
| inventory-commissary | unknown | resolve-to-partial | Scored against the 60-topic Inventory Use and Maintenance chapter and the Operations Planning topics of the 458-topic Store Manager manual, which together are the product's whole stock-movement and production surface. Valued inter-store movement is present; the commissary model as worded (produce, issue, computed transfer cost) is not. source |
| inventory-lot-traceability | unknown | resolve-to-no | Schema-with-no-such-field plus a fully enumerated receive workflow - both qualifying enumerations. Stated against the corpus: the 458-topic Store Manager manual, including its published .psf integration schema, captures no lot or batch identifier at receiving. source |
| inventory-shelf-life-expiry | unknown | resolve-to-no | Two self-asserting complete report catalogues plus the published receive schema. The claim is conjunctive (track dates AND surface an expiring-soon report or alert) and both halves are absent from the enumerated surfaces of the 458-topic Store Manager manual. source |
| inventory-bar-partial-bottle | unknown | resolve-to-partial | The mechanism for counting partial containers by weight is documented at grade B with a worked example, satisfying the by-fraction half; the scale-integration half fails against the Hardware chapter, which enumerates the supported peripheral device types and includes no scale. source |
| inventory-menu-margin-linkage | unknown | resolve-to-partial | Recipe-cost-to-sales-mix margin reporting is documented at grade B in the complete Inventory report list and in Menu Designer's Sales Mix chapter. The threshold-flagging half is absent from both manuals; the only alerting product SpeedLine publishes is the cloud analytics add-on, and its feature page does not list margin among its Pulse Alert metrics. source |
| reporting-tier-paywall | unknown | resolve-to-partial | Previously unassessable because no tiers are published. That framing was wrong: SpeedLine is licensed by module, and the module boundary is documented. Three of the four reports the claim names are in the base Store Manager catalogue at grade B; the fourth, multi-location comparison, is behind separately sold cloud/enterprise products (grade C feature pages). Partial with the shortfall named. source |
| reporting-nl-query | unknown | resolve-to-no | The in-store enumeration qualifies: a self-described complete report catalogue plus the single wizard that parameterises it. The cloud add-on is corroborating grade-C marketing rather than an enumeration, so this no rests on the POS product's own documented query surface; recorded against that corpus. source |
| reporting-tip-tax-compliance | unknown | resolve-to-partial | Two of the three named elements are documented at grade B in the complete report catalogue; the third, tip pool distribution detail, is absent from all three manuals (a full-text search of the dump for pool/tip-out/tip share returns only that one advisory sentence). source |
| multi-location-new-store-template | unknown | resolve-to-partial | Configuration cloning is documented in detail at grade B across the 11-topic Multi-Store Administration chapter plus Menu Designer Store Groups. The claim's second, testable half - the vendor publishing an expected time-to-open - is not met anywhere on the doc host or the marketing host. source |
| multi-location-normalized-item-rollup | unknown | resolve-to-partial | The shared-corporate-item-ID half is documented at grade B in Menu Designer and corroborated by Store Manager's PLU-collision warning. The roll-up half rests only on grade-C/D vendor pages for add-on products whose report sets are not published, so it cannot carry a yes on a differentiator cell. source |
| multi-location-cross-location-giftcard | unknown | resolve-to-partial | Integrated processor-hosted gift cards are documented at grade B, which is the mechanism by which cross-location redemption works, but the two reporting/settlement elements the claim names are absent from a self-described complete report catalogue. Also corrects the Valutec attribution in the prior rationale. source |
| multi-location-multi-brand | unknown | resolve-to-partial | Positively documented at grade B that more than one menu file can be live on a station simultaneously, which is the load-bearing part of the claim; the branding and separately-reportable-revenue parts are only achievable by convention (order types, item categories) and are named as the shortfall. source |
| hardware-tap-to-phone | unknown | resolve-to-no | Enumeration bar met on a settings screen: Station Options > Secure Card Entry with its Device Type list is the whole configurable card-entry surface, and the vendor's own away-from-station product explicitly requires a separate mobile EMV reader. Recorded against the 458-topic Store Manager manual and the current 8.0 release notes. source |
| hardware-ownership-vs-lease | unknown | resolve-to-partial | First-party evidence of outright purchase (SpeedLine's own e-commerce store, described on the support-services page and in a dated support advisory) at grade C, which cannot carry a yes on a differentiator cell; and the claim's second requirement - the vendor stating which model applies - is only half met, since no lease alternative is affirmed or denied. Also removes a denylisted-aggregator citation from the record. source |
| extensibility-custom-fields-scripting | unknown / grade F - 'No public documentation located during the 2026-08-01 research pass.' | resolve-to-yes | Read addcustomfieldscustscreen.htm and runansqlquery.htm in the 458-topic Store Manager manual dumped 2026-08-09. Custom fields are defined by the operator in Settings; SQL queries are typed or pasted, saved, reloaded and printed by the operator, gated by the 'SQL Query Read Access' / 'SQL Query Read/Write Access' privileges enumerated in smsecurityprivilegesdesc.htm. No vendor engagement is involved. source |
| reliability-offline-card-auth | unknown / grade F - 'No public documentation located during the 2026-08-01 research pass.' | resolve-to-yes | Read enter-tripos-settings.htm and setupvantivpaymentproc.htm in the Store Manager manual. Store and Forward is a named, operator-enabled setting on the triPOS sub-tab; the MercuryPay topic's exclusion list corroborates it. Terminal also supports a phoned-in authorization code when there is no Internet connection (terminalsecurityprivilegesdesc.htm). source |
| reliability-printer-fallback | unknown / grade F - 'No public documentation located during the 2026-08-01 research pass.' | resolve-to-partial | Read assignanalternateprinterroute.htm and setprintermakeroutes (Printer Make Routes) in the Store Manager manual, plus the four Kitchen Monitor topics. The alternate-printer route is automatic for station failure only; the topic explicitly disclaims detection of printer-level failure and prescribes a manual override, and nothing alerts staff. source |
| reliability-public-status-page | unknown / grade F - 'No status page was linked from any page reviewed, and no status subdomain was verified in this session. Absence is not established.' | resolve-to-no | Probed status.speedlinesolutions.com (does not resolve) and /security (404), enumerated the complete 501-URL www sitemap.xml with no status or trust URL, and read /support-services, where the vendor's stated incident-communication channel is the emailed Support Advisories subscription. Absence is now positively evidenced rather than merely unfound. source |
| reliability-incident-postmortems | unknown / grade F - 'No public documentation located during the 2026-08-01 research pass.' | resolve-to-partial | Enumerated the whole /supportadvisories archive from the 501-URL sitemap and read three outage-related posts in full: the 2025-09-30 Windows-update advisory (root cause, scope, remediation, workaround), the 2026-05-14 Valutec Azure migration notice (scheduled window and impact), and the 2025-08-12 'Services Restored' notice (restoration only, no cause). Root-cause publication exists but is inconsistent and absent for SpeedLine's own outages. source |
| reliability-backup-restore | unknown / grade F - 'No public documentation located during the 2026-08-01 research pass.' | resolve-to-yes | Read change_database_backup_interval.htm, change_file_backup_settings.htm and restore_data_from_a_backup.htm in the Store Manager manual. The operator sets the interval, adds files to the backup list and runs the restore wizard themselves; the claim's first limb is met, so the absent RPO/RTO figures do not gate it. source |
| reliability-failover-terminal-role | unknown / grade F - 'No public documentation located during the 2026-08-01 research pass.' | resolve-to-partial | Read restore_data_from_a_backup.htm plus the primary/secondary/work-station role definitions repeated across the Backup topics in the Store Manager manual. Failover capability exists and is real, but is manual, single-designated-secondary, and leaves card processing down until third-party software is reinstalled by hand. source |
| commercial-no-early-termination-fee | unknown / grade F - 'No public documentation located during the 2026-08-01 research pass.' | resolve-to-no | Read /terms end to end and /privacy end to end, enumerated the complete 501-URL sitemap.xml (no MSA, subscription agreement, or legal page beyond those two), confirmed /legal and /security 404, and checked the 26 PDFs linked from /guides-and-brochures - all product brochures. The document that would carry the clause exists and demonstrably lacks it. source |
| commercial-autorenew-terms-published | unknown / grade F - 'No terms of service, MSA or subscription agreement is publicly accessible on the site.' | resolve-to-no | Retrieved and read /terms and /privacy in full, enumerated the 501-URL sitemap.xml, confirmed /legal 404s, and checked the /guides-and-brochures PDF set. The prior rationale asserted the same conclusion without having read the documents; it is now positively evidenced. source |
| commercial-data-ownership-clause | unknown / grade F - 'No published terms address merchant data ownership or constrain vendor reuse...' | resolve-to-no | Retrieved /terms and /privacy in full and read every section, enumerated the 501-URL sitemap.xml for any other legal document (none; /legal 404s), and read the CCPA support advisory whose 'never sold by SpeedLine' line is informational rather than contractual. The absence is now evidenced from inside the documents rather than inferred. source |
| commercial-soc2-attestation | unknown / grade F - 'No SOC 2, ISO 27001 or trust-center reference appears anywhere on the public site.' | resolve-to-no | Grepped the complete local dump of all three manuals for SOC 2 / SOC2 / ISO 27 / ISO-IEC (zero hits), enumerated the 501-URL sitemap.xml (no trust or security page; /security 404s), and read /support-services, where the compliance claims made are QIR certification and PCI DSS. The prior rationale asserted this without having read the corpus. source |
| commercial-privacy-dsar-tooling | unknown / grade F - 'No public documentation located during the 2026-08-01 research pass.' | resolve-to-partial | Read exportcustomerinformation.htm, exportreports.htm and terminalsecurityprivilegesdesc.htm in the Store Manager manual, plus www.speedlinesolutions.com/privacy and the CCPA support advisory. The product operations are documented; the DSAR framing and the DPA are not. source |
| commercial-dual-pricing-compliant | unknown / grade F - 'No public documentation located during the 2026-08-01 research pass.' | resolve-to-partial | Read add_surcharges_for_tender_type.htm, add-duplicate-tender-types.htm and changeordersurchargediscount.htm in the Store Manager manual. The card-network compliance condition in the claim - automatic debit and prepaid exclusion - is explicitly disclaimed by the vendor in its own documentation. source |
| payments-tip-pooling | no / grade B - "The tip surface is enumerated in three places and is entirely individual. Employe" | upgrade-to-partial | The researcher's enumeration of SpeedLine's own tip surface is accurate and I re-verified it (Reports tab catalogue, Day Report section list, Employee Options tip settings, Terminal tip privileges - all per-employee). But it was drawn only from the SpeedLine 8 Store Manager manual, and SpeedLine ships a second, current product line, SpeedLine Plus. Its own support advisory of 2026-06-11 announces a direct SpeedLine Plus / 7shifts integration whose feature list includes 'Tip Pooling: Managers can customize tip pool logic for equitable contribution and distribution, while 7shifts manages the funds based on SpeedLine Terminal labor data'. A named, dated, first-party partnership delivering configurable pooling on SpeedLine's own labor data makes an unqualified no a false statement about the product; partial, with the shortfall named as non-native and 7shifts-dependent, is the supportable value. source |
| order-capture-bar-tab-preauth | no / grade B - "Station Options > Register tab, 'Tender Without Closing Order for These Order T" | downgrade-to-unknown | The researcher wrote that 'the Card Processing settings group is fully enumerated... and contains no pre-authorization' and that 'pre-authorization appears nowhere across the 646 topics'. Both are false. I re-fetched every topic page and, separately, all 648 settings-popup bodies from the manual's jspopups/ directory - content the plain-text dump omits - and found tokenize-or-preauth.js on activateorchangedeferredorders.htm: 'Pre-Authorize: Select to pre-authorize credit card payments, in order to reserve the funds in the cardholder account and prevent the authorization from being declined at activation.' That pre-auth is scoped to deferred orders rather than tabs, so it is not evidence the claim is met; but an enumeration that missed the one place the capability appears cannot carry positive evidence of absence, and the Terminal User's Guide covering the order-entry application is not published. Unknown in both directions. source |
| order-capture-qr-same-check | unknown / F - 'the guest side of SpeedDine is documented in the SpeedLine Portal ... which is customer-gated and not published on this host' | resolve-to-no | The gating premise is false. SpeedLine Portal Help is published unauthenticated at /Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/ (index.htm 200, titled 'Welcome to SpeedLine Portal Help'; 139 topics covering Menu Management, Store Management, Site Appearance, Company Management and Employees). Read against the claim it is an enumeration, not a silence: Configure Order Types names the guest order types as Pickup and Delivery and nothing else, and dine-in / at-table / curbside / table appear in none of the 139 topics. Combined with the Store Manager Table Service chapter, which has no guest ordering option, and with the fact that every documented QR code in the product is staff-facing (SpeedLine Pay ticket QR, Tattle survey QR), there is no guest QR at-table ordering to write onto an open check. source |
| payments-chargeback-tooling | unknown / F - 'no documentation for either is published on this host, so a portal-side dispute dashboard cannot be excluded' | resolve-to-no | The escape hatch is closed. SpeedLine Portal Help is published unauthenticated (139 topics, /Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/) and covers the Portal's complete navigation including the Cloud Reporting & Analytics access model; chargeback and dispute occur nowhere in it. Looking for a replacement basis found the vendor describing its own chargeback workflow as a POS ticket lookup - the 7.3 R300 advisory, 'Search for tickets by the last four digits of the payment card number: find orders and investigate chargebacks more easily' - which is what a product without a dispute console ships instead. With the Store Manager Card Processing group and Reports catalogue already enumerated and empty of any dispute view, this is positive evidence of absence rather than absence of mention. source |
| order-capture-scheduled-orders | partial / B - "'Defer Orders' in POS; SpeedDine deferral up to 30 days. Computed fire-time injec" | upheld | Partial stands but for a different reason than recorded. The cited /online-ordering marketing page is not what establishes this. The Deferred Orders settings topic and its field-description popups document a genuine computed fire time - Fixed Activation Time, Initial Print Increment, Initial Required Increment and 'Minutes Between Print and Required' - so the note's claim that fire-time injection is undocumented is withdrawn. What is actually missing is a per-channel lead time: that interval is explicitly store-wide and identical for all orders. The 30-day figure is also wrong; the Portal caps deferral at 31 days. source |
| order-capture-catering | partial / B - "ezCater marketplace integration only. No native catering flow with quotes, deposits" | upheld | Re-evidenced from documentation rather than the /partners marketing page. The SpeedLine Plus Portal Help now publishes Onboarding Information for ezCater and Menu Management ezCater, which show the integration is real and reasonably deep (servings per selection, tax category, individual-wrap status, dietary tags, free tableware, quantity unit, checkout upsell). It remains a marketplace pipe: no quote, no deposit, no balance-due tracking and no event schedule appear anywhere, and the Portal's answer to large orders is a maximum-order-amount block that routes the customer to store staff. Partial stands. source |
| order-capture-order-ready-signal | unknown / F - "...is onboarded through the SpeedLine Portal and its integration documentation is not" | upheld | The stated reason for the unknown is withdrawn. The marketplace integration documentation is published - I located SpeedLine Plus Portal Help (392 topics), reachable only from cross-links inside the other manuals, and read its DoorDash, Uber Eats, Grubhub and ezCater onboarding, store-availability and menu-management topics plus Order Cancel Third Party Marketplaces. They document outbound menu publish, out-of-stock reflection, store hours, store pause/resume and an operator-initiated cancel that the marketplace approves or denies; there is no order-ready event. I stopped short of scoring `no` because a status callback belongs to the SSIO message contract, not to an admin screen, and that contract is unpublished - the SpeedLineNext manual that Store Manager links for it 404s at the server. Unknown, re-reasoned. source |
| menu-pricing-upsell-prompts | partial / B - "'Cross-Sell Prompts' is a first-class cloud-menu node; SpeedDine runs upsell prompts" | upheld | Partial upheld from documentation instead of the SpeedLine Marketplace brochure. The Portal help configures upsells per product with type, frequency, placement and exclusions, and cross-sells separately - so the per-item half is solid. The per-channel half is weaker than the brochure implied: Choice upsells are explicitly not supported in Terminal and topping upsells only work on portioned products. The attach-rate half fails outright - the only measurement offered is that the upsell name surfaces in Google Analytics, and the cloud Report Definitions topic enumerates the whole report catalogue with no attach-rate report in it. source |
| menu-pricing-86-propagation | yes / B - "Out-of-stock in POS propagates to SpeedDine and to DoorDash/Uber Eats/Grubhub; FAQ" | upheld | Upheld and re-sourced. The SpeedLine Marketplace brochure was carrying this; the behaviour is now documented in the vendor's own admin help, per marketplace, with the propagation direction (Terminal outward), the operator action (Operations > Out of Stock) and a stated latency of 'a few minutes'. The SpeedDine leg is separately documented as a polled Synchronize Out of Stock with Store setting. Nothing here depends on the Portal-is-gated premise. source |
| menu-pricing-dayparting | yes / B - "'Set up designated times where prices on specific items automatically adjust'; SpeedD" | upheld | Upheld, but the evidence was a marketing page on /enterprise and is now documentation. Manage Price Groups documents automatic time- and date-based price application in Terminal including overlap handling, and the Portal's time-restriction topic documents scheduling item and discount visibility by date range, day of week and time of day, assigned per store group. The note's open item - per-location timezone - is answered as far as the docs go: stores carry a Time Zone field, described in relation to quoted, ready and deferred order times. source |
| menu-pricing-allergen-nutrition | partial / B - "That is unstructured free text ... nothing published to third-party menus" | upheld | Partial upheld, one clause of the reasoning retracted. The earlier pass concluded 'nothing published to third-party menus', which the newly published SpeedLine Plus Portal Help contradicts: Menu Management ezCater exposes a structured per-selection Dietary Tags field ('For example, Gluten free or Kosher') that is published to the ezCater menu. That is real structured dietary data, but it is diet-preference labelling rather than allergen flags, and it exists on the ezCater tab alone - the DoorDash, Uber Eats and Grubhub menu topics have no counterpart. Nutrition is still absent everywhere and there is still no recipe-derived nutrition, so the value does not move. source |
| payments-card-on-file | yes / B - "Tokenization 'securely stores credit card information for future orders'; SpeedDine ac" | downgrade-to-partial | A differentiator yes carried by the /speedlinepayments marketing page. The documentation that has since become readable supports the capability but not the claim's scope: the Portal's tokenization topic is explicitly about the online ordering process, and the token is attached to the guest's account on the ordering site. I searched all four manuals and their field descriptions for any way to reuse a saved guest card from Terminal - 'card on file', 'saved card', 'saved credit card' - and the single hit is the store-level ordering-site setting. Terminal's own tokenization is per deferred ticket, not a guest profile credential. Add the processor gate (SpeedLine Payments or Worldpay Express only, with Worldpay Support setup required) and per-store activation, and partial with a named shortfall is the correct value. source |
| payments-p2pe-pci4 | partial / B - "Claims end-to-end encryption (E2EE, not validated P2PE) and resells SaferPayments as " | upheld | Partial upheld, the reasoning corrected. The note's E2EE-not-P2PE distinction does not survive the support-advisory corpus: SpeedLine states outright that the Ingenico Lane 3000 'Is P2PE certified when using Worldpay Express'. That is a first-party claim about a device on a specific processor, not a SpeedLine P2PE solution listing, and it changes nothing about the second half of the claim - I found no PCI DSS 4.x AoC anywhere on the marketing site, the support site or in any of the four manuals, and the PA-DSS Implementation Guide is only distributed inside Store Manager's Document Viewer. Partial stands with an accurate note. source |
| kitchen-channel-pause-propagation | yes / B - "Capability confirmed, but not by the cited source ... The claim is on the web page" | upheld | Upheld and moved off marketing copy. The previous verifier was right that the brochure does not contain it and re-pointed to the /speedline-marketplace web page - a single sentence of vendor marketing carrying a differentiator yes. The behaviour is now documented per marketplace in SpeedLine Plus Portal Help: an explicit Pause Store / Resume Store control with confirmation and connection-status transitions, plus Terminal out-of-stock marks reflected onto the marketplace within a few minutes, plus Portal store hours pushing to all three marketplaces. One correction to the record: the store pause is performed in the Portal rather than from the POS or KDS; the POS-originated propagation is the item 86. source |
| kitchen-order-ready-callback | unknown / F - "...onboarded through the customer-gated SpeedLine Portal whose SSIO documentat" | upheld | Re-checked against three corpora that did not exist when this was scored. The refuted premise is withdrawn: the SpeedLine Portal help is public and I read all 138 topics; it configures menu, store, company, themes, tender types, loyalty and employees and has no order-status or readiness surface. The unreadable document is a different one - the SSIO onboarding manual under SpeedLineNext/SpeedLine_Next_Admin_Help_Web/, whose three links from Enable SpeedLine Marketplace all return HTTP 404. Nothing in the 8.0 Release Notes or the 153 advisories describes a bump-triggered status push to a marketplace. Unknown stands on corrected reasoning. source |
| delivery-3p-direct-integration | yes / B - "'SpeedLine Marketplace connects directly with DoorDash, Uber Eats and Grubhub' (pl" | upheld | The value is right but the evidence was a hubfs brochure - vendor marketing, grade D - carrying a B, and a differentiator yes needs A or B. I located first-party documentation instead: Store Manager's Enable SpeedLine Marketplace topic (activation switch, version floor 8.0 R400, per-channel SpeedLine onboarding, Make Live publishing to onboarded marketplaces) and the 8.0 Release Notes line 'New: Direct integrations for DoorDash, Grubhub, and Uber Eats.' The manuals separately name Chowly and ItsaCheckmate as the non-integrated aggregator path, which is what makes 'direct' checkable rather than asserted. Yes upheld on documentation. source |
| delivery-menu-push | yes / B - "Automatic simultaneous menu and price sync from the SpeedLine cloud menu to all pla" | upheld | Re-evidenced off the brochure and onto the SpeedLine Portal help, which was assumed unpublished and is not. Make Live publishes the one cloud menu to SpeedDine and to every onboarded marketplace; each selection carries Order Source check boxes controlling which platforms it appears on; out-of-stock state is pulled from the Terminal User screen and prices re-synced every 30 minutes. Two parts of the claim remain marketing-only and are now named in the note: the per-marketplace percent markup, and photo publishing to the marketplaces. Yes stands, on documentation this time. source |
| delivery-store-pause | partial / B - "Pause online orders from all third-party marketplaces in one place inside the POS;" | upheld | The cited page was a marketing page graded B. In the now-public SpeedLine Portal help I found the actual mechanism - the Special Days Online Ordering toggle - which both strengthens and bounds the claim: it does notify online ordering providers, but only 'if they support that function', with no list of which do; and reactivation is automatic the following day rather than after a chosen interval. Partial upheld, shortfall renamed from 'timed auto-reactivation not documented' to a conditional propagation plus day-granular reopen. source |
| delivery-3p-reconciliation | partial / B - "Consolidated Third-Party Delivery and Remote Order Sources dashboards show 3P sales" | upheld | The shortfall the researcher inferred from absence turns out to be stated by the vendor. Taxes for Marketplace Orders instructs operators that SpeedLine's marketplace figures are 'for reference only' and that remittance amounts must be taken from the source portal, which is the vendor conceding the reports are not payout-grade. The consolidation half is real - net sales by order source, the Third-Party Delivery dashboard, and the 8.0 split of marketplace-remitted tax. Partial upheld and re-cited from a marketing page to documentation. source |
| digital-first-party-web | yes / B - "SpeedDine is a first-party branded ordering site writing directly into the POS. Comm" | upheld | Re-checked against the SpeedDine/SpeedLine Portal administration manual, which the record had recorded as unpublished and which is in fact public. It documents the per-store unique site URL, the theming that makes the site the operator's own, and the live pricing round-trip to Terminal (Store Pricing Request/Response XML). Yes upheld and re-cited from /online-ordering to documentation. I did not find any first-party statement of commission-free pricing, so the note now records that rather than calling it implied. source |
| digital-group-ordering | unknown / F - "...the ordering site itself is configured in the SpeedLine Portal ('SpeedDine Menu M" | resolve-to-no | The reason this was parked has been removed: the SpeedLine Portal / SpeedDine administration manual is public at support.speedlinesolutions.com/Portals/0/CustomerDocumentation_SF/SpeedDine/SpeedDine_Admin_help_Web/ and I read all 138 topics. Company Management and Store Management each print a closed list of the settings that exist, and the checkout, order-type and order-limit topics are the complete configurable surface of the ordering site. A shareable multi-participant cart with spend caps would have to appear there and does not; the only caps are a single maximum order total and a minimum, both per cart. Resolved to no on enumeration rather than silence. source |
| digital-catering-portal | partial / B - "ezCater marketplace connection only. No native catering menu, lead-time rules, quot" | upheld | Checked in the now-public SpeedLine Portal help rather than on the partners page. ezCater is wired in as a fourth Marketplace channel with per-product availability, dietary tags and suggested add-ons; deferred ordering allows up to 31 days ahead but is not catering-specific; nothing in the corpus provides catering minimums, quotes, deposits or invoice terms. The one topic that might have gone further, Menu Management ezCater, is a dangling cross-reference - not in the Menu Management contents and not resolvable on the host. Partial upheld with the shortfall unchanged and the citation now first-party documentation. source |
| digital-drivethru-ai | unknown / F - "SpeedLine does market AI voice ordering, but for the telephone, not the lane..." | upheld | Re-ran the search over the corpus as it now stands - four manuals and 784 topics rather than three and 646, plus the 8.0 Release Notes and 153 support advisories that were not available before. Nothing changes: drive-thru appears only as an order confirmation display and as a Connect source type, and the AI story remains a phone-call blog post with no named provider. Unknown upheld; the rationale's stale counts (three manuals, 501-URL sitemap) are corrected to four manuals and 574 URLs. source |
| digital-google-order | unknown / F - "Unresolved because SpeedDine channel provisioning is administered in the SpeedLine P" | resolve-to-no | The premise this was parked on is refuted: the SpeedLine Portal help is public and includes a topic devoted to exactly this question. View Google Services Information documents the Google Services panel and, through the manual's popup field fragments, every control on it - reCaptcha, Maps API key and signing secret, two Analytics tracking IDs and a Tag Manager code. A screen whose controls list and field descriptions are both published is the complete configurable surface of that screen, and there is no Order with Google provisioning on it, nor anywhere in the enumerated Company Management settings. Resolved to no. source |
| digital-apple-business-connect | unknown / F - "Unresolved for the same reason as the Google cell: SpeedDine channel provisioning li" | resolve-to-no | Same refuted premise, same correction. Having read all 138 topics of the public SpeedLine Portal help, the company and store administration surfaces are closed enumerations and every outbound-link feature is documented individually - social footer links, an alternate locations page, and the per-store SpeedDine site URL exposed with a copy button. Nothing registers an ordering action with a mapping or place-card provider; SpeedLine has a Google Services panel and no Apple equivalent. Resolved to no, with the note stating plainly that a merchant can still paste the site URL into Apple Business Connect unaided. source |
| digital-loyalty-attach | yes / B - "Loyalty Rewards is a node in the same cloud menu that drives SpeedDine; loyalty trac" | upheld | The researcher's characterisation was right but sourced to /speedline-loyalty, a marketing page carrying a B. The public SpeedLine Portal help documents the mechanism: rewards are read from the SpeedLine Loyalty administration site into the SpeedDine menu, bound to menu items through a Linked Product field, and redeemed by a guest signing in to the same cardless account the app uses to identify them in store, with the sign-up prompt rendered by the site theme rather than after checkout. Punchh and Paytronix have equivalent setup topics. Yes upheld on documentation. source |
| digital-subscriptions | unknown / F - "Checked the complete local dump of SpeedLine's three published WebHelp manuals ... 'subscript" | resolve-to-no | The SpeedLine Portal documentation the earlier pass believed to be unpublished is public and unauthenticated. Its tender-type topic is a closed list of five addable payment types plus a default zero-dollar type, none of which bills a guest on a recurring schedule, and the Portal's complete Company Management chapter has no membership or entitlement function. Combined with the absence of any membership add-on in Store Manager's own list of optional modules, this is positive evidence of absence rather than absence of mention. source |
| guest-loyalty-thirdparty-identity-attach | unknown / F - "Read both SpeedLine Marketplace topics ... Unresolved: this would be settled by the Speed" | upheld | The premise this cell rested on is false but the verdict survives. The SpeedLine Portal manual is published and has no marketplace chapter, and the marketplace onboarding topics Store Manager links to are dead (404) on the public host, so the documents that would settle the question still cannot be read. The newly dumped Connect field descriptions document Add Customer / Edit Customer requests, phone-number matching and a name/address discrepancy alert for Connect sources in general, which is suggestive but is never tied to marketplace order sources. Unknown stands on corrected evidence. source |
| guest-loyalty-offline-behavior | unknown / F - "Read every loyalty topic in the dumped corpus ... The single-store program is held in the" | upheld | Verdict unchanged, reasoning corrected. The Portal loyalty topics are public and say nothing about connectivity; the newly readable Connect alert list adds 'Loyalty Authorization Failure - the store could not contact the loyalty provider', which documents detection but not behaviour. The old note's supporting inference is withdrawn: the Portal describes SpeedLine Loyalty as a cardless single-or-multi-store cloud program administered on its own site, not a store-local one, so the on-premise-database argument for survival does not hold. source |
| guest-loyalty-ai-offer-recommendation | unknown / F - "'AI', 'artificial intelligence' and 'machine learning' return zero occurrences across all" | resolve-to-no | The earlier pass left this unknown because the surfaces where such a feature would live published nothing. One has since been shown to publish 138 topics, and two new first-party corpora - the 8.0 release notes through 8.0.413 and all 153 support advisories - are now readable. Across the whole published record SpeedLine documents Voice AI order taking and an accessibility widget and nothing else AI-related; offer content, audiences and timing are operator-authored throughout. For a claim whose test is whether the vendor documents a shipped feature, that is positive evidence of absence. source |
| labor-offline-time-punch | unknown / F - "the Time Clock tab's own settings are delivered as a clickable image map ... so the field " | upheld | Verdict unchanged, blocker removed. The Help and Manual popup fragments behind the Time Clock image map are recovered, so the screen's full field list is now in evidence and demonstrably contains no offline, queue or reconcile setting; the same is true of the whole Employees chapter and of the 8.0 release notes. The reason for stopping short of no is different now: the Terminal User's Guide, which the topic itself cites for time-clock operation, is customer-distributed and unpublished. source |
| labor-digital-onboarding-i9 | unknown / F - "Onboarding is a manager typing into an employee profile; W-4, I-9, E-Verify and new-hire " | resolve-to-no | The Employment tab's own instruction - select I-9 Received or TD-1 received 'if you have received the employee's I-9 or TD-1 form' - is an affirmative statement that the document is collected outside SpeedLine and only its receipt is recorded. That plus the screen's complete control list, the absence of W-4 and E-Verify from every published corpus, and the 7shifts advisory's own enumeration of integration scope closes the hedge the earlier pass left open. source |
| inventory-86-auto-sync | partial / B - "Manual 86 in the POS syncs to SpeedDine and all connected marketplaces. Automatic 86 trig" | upheld | Partial survives but the evidence had to be replaced: the cell cited only the SpeedLine Marketplace brochure, a marketing PDF carrying a grade B it does not earn. Store Manager's Activate Out-of-stock Menu Restrictions and the Portal's Synchronize Out of Stock with Store document the manual mark and its propagation to the ordering site at documentation grade, while the now-readable Inventory Options and stock item field descriptions show there is no threshold or par level anywhere in Inventory to trigger an automatic 86. Marketplace propagation remains a marketing claim only. source |
| reporting-channel-profitability | partial / B - "Dedicated Third-Party Delivery, Remote Order Sources and Delivery Performance dashboards s" | upheld | Partial stands, re-evidenced away from the Analytics product page. Report Descriptions, which asserts it lists the reports on the Reports tab, contains Remote Order Sales Summary and Remote Order Discounts (net sales and discounts per Connect source, with the aggregator's order-source name), Hourly Order Type Sales and Delivery Performance, and the 8.0 release notes add a marketplace tax split. The same enumeration's only margin report is Product Margin, computed from ingredient cost and product price by item category, and nothing anywhere nets marketplace commission. source |
| reporting-history-retention | unknown / F - "Nothing states how long ticket-level detail remains queryable ... a retention window is a c" | resolve-to-yes | Resolved from a corpus the earlier pass never had: the 153 support advisories, most of which are reachable only from sitemap.xml. The June 2026 Cloud Reporting & Analytics advisory names the retention window explicitly - a three-year cap, now removed for Employee Item Sales, Pay Period, Pay Period Details and Ticket Details, which become unlimited. Three years clears the 24-month bar, ticket-level detail is among the uncapped reports, the limit is published rather than silently enforced, and no retrieval fee is charged; restoring beyond three years requires re-transmitting Day Files via Support, which is noted but is not a fee or a truncation. source |
| multi-location-price-zones | yes / B - "One item carries regional/store price differences, per-channel price books (in-store vs eac" | upheld | Yes survives, but only after replacing the evidence: the cell cited the enterprise marketing page at grade B, which the rules do not allow to carry a yes. Menu Designer's Add Store Groups, Create Alternate Pricing with Price Groups and Create Order Type Specific Pricing document location, daypart and channel pricing respectively, all as additional price nodes hung off the same item, and the SpeedLine Portal documents an all-stores / store-group / individual-store override hierarchy for SpeedLine Plus. The per-marketplace price book in the original note is not documented and I have flagged it as marketing-only. source |
| hardware-os-platforms | partial / B - "Windows-based POS (SpeedLine 8 and SpeedLine+), tablets, and a web portal; Capterra lists W" | upheld | Partial stands, evidence rebuilt. The note leaned on Capterra for its deployment list, which the source policy forbids for capability claims; that leg is withdrawn. In its place SpeedLine's own support advisories name the supported Windows editions (Embedded POSReady 7, 8.1 Professional, 8.1 Embedded Industry Pro, 10 Pro/Enterprise, 10 IoT 2016+ on Posiflex, 11) and state a minimum of Windows 10 for EMV stations, and first-party material covers the Apple/Android SpeedLine Pay app and the browser-based Portal. The shortfall is unchanged and now sourced to SpeedLine's own pointer: the Minimum Requirements and Supported Hardware document is customer-gated, and I confirmed it is not retrievable on the public host. source |
| hardware-handheld-battery-swap | unknown / F - "Checked the full dump of the three support.speedlinesolutions.com manuals. supportedh" | upheld | Re-evidencing, not a value change. The cell did not depend on the refuted premise that SpeedDine/Portal documentation is unpublished - it depends on the separate Customer Site login over the Minimum Requirements and Supported Hardware PDF, which I re-probed and could not reach publicly. Searching the two corpora that did not exist when this was scored (8.0 Release Notes, 153 advisories) plus the 138-topic Portal manual added no battery or shift-life data. The rationale is corrected for the stale "three manuals" and "501 URLs" figures. source |
| hardware-ownership-vs-lease | partial / C - "The Support Services page lists among the customer support website's resources an \"Onl" | upgrade-to-yes | The prior partial named as its shortfall that "the vendor never states the alternative". The support-advisory corpus, which did not exist in the record when this was scored, states it in the vendor's own words: computers are "purchased from SpeedLine", self-supplied computers are permitted, and replacement stations and PIN pads are bought from the online store or After-Market Sales. That is first-party support documentation (grade B), not the grade C support-services marketing page, so it clears the differentiator bar. I searched all 153 advisories, all 784 manual topics and the 574-URL sitemap for lease, leasing, rental and rent: no lease or bundled-rental programme exists. source |
| hardware-rma-sla | unknown / F - "Read www.speedlinesolutions.com/support-services in full: it enumerates the support of" | resolve-to-partial | The 153-advisory corpus was not available when this cell was scored and the marketing /supportadvisories page lists only about ten of them, so the Lane 3000 "Optional 3-year advanced exchange warranty" was invisible. It is a real published warranty term plus an advance-exchange mechanism, which is more than the record's unknown allowed, but it covers a single optional PIN pad and carries no turnaround, so the claim's SLA half is unmet. Grade C rather than B because the source is an upgrade-options advisory written to sell the newer device. source |
| extensibility-partner-revshare | unknown / F - "Checked www.speedlinesolutions.com /partners, /integrations and /speedline-marketplace" | resolve-to-no | The prior unknown was written against three manuals and a 501-URL sitemap. With the 138-topic SpeedDine/Portal manual, the 8.0 Release Notes and all 153 advisories added, and /partners re-fetched, SpeedLine's entire public surface has been searched and publishes no partner commercial terms of any kind. This claim asks whether the vendor PUBLISHES its terms, so an exhausted publication surface is positive evidence, not absence of evidence; the terms plainly exist privately and are obtained by contacting sales. source |
| extensibility-free-sandbox | unknown / F - "There is no developer surface to check: api., developers., docs. and help.speedlinesolu" | resolve-to-no | The premise that only three /releasedocs manuals exist is refuted, so I re-read the whole 784-topic corpus plus the Release Notes and 153 advisories. That produced the affirmative finding the earlier pass lacked: SpeedLine does publish its developer on-ramps, and both are gated - the EventStream SDK via a Sales Representative, and Connect via an onboarding that binds the provider to a live store's certificate, IP and port. Together those enumerate the routes a developer can take and none is available without an account, which is the positive-evidence bar for no. source |
| extensibility-webhook-reliability | unknown / F - "The only event-push mechanism documented is SpeedLine Connect Notifications: Store Mana" | resolve-to-no | The earlier pass left this undetermined partly because settings screens rendered as unreadable image maps. With every popup field fragment inlined, the Notifications sub-tab is readable end to end and holds exactly one control, and the topic itself prescribes a ping-then-pull reconciliation pattern in place of guaranteed delivery. The claim's subject is what is documented (signed, documented to retry, replayable log); none of the three is, and the mechanism's full surface is now visible rather than assumed. source |
| extensibility-menu-write-api | unknown / F - "Menu authoring lives in the 183-topic Menu Designer desktop application, and the Connec" | resolve-to-no | The prior unknown turned on the possibility of an unseen inbound menu-write message. Two pieces of newly readable documentation close it: the Connect manager-alert descriptions, which show incoming messages can only reference PLUs, items and sizes that already exist in Menu Designer, and the SpeedDine/Portal manual, whose entire menu lifecycle - authoring, pricing, activation and marketplace publication via Make Live - is a UI workflow. Combined with the still-current instruction to forward the menu file to a provider by hand, this is the documented-workaround-in-place-of-an-API pattern. source |
| extensibility-data-symmetry | unknown / F - "Prior reading of the SpeedLine Connect flyer stands: it says Connect 'messages pass dat" | resolve-to-partial | The cell was parked at unknown because no first-party document stated direction per object. The 8.0 Release Notes PDF (public, printed May 2026) and the now-readable Connect field descriptions state it for two objects: Connect providers send Add Ticket, Void Ticket and Add/Edit Customer messages, so orders and customers are writable, while store, menu and employee data appear only in responses. Symmetry across all core objects therefore fails on a documented basis rather than an unexamined one, which is partial with the shortfall named, not unknown. source |
| extensibility-published-rate-limits | unknown / F - "No numeric quota, throttling rule or header is published, and no host serves API docume" | resolve-to-no | Re-searched after the three-manual premise was refuted: the 138-topic Portal manual, the 8.0 Release Notes and 153 advisories add no quota, and the newly readable Connect field descriptions show the throughput model is per-station concurrency on a store-owned listening port. For a claim whose subject is whether limits are published, an exhausted publication surface plus an architecture with no central gateway to meter is positive evidence of absence, not a gap in the search. source |
| extensibility-first-party-delivery-integrations | yes / B - "SpeedLine Marketplace connects directly to DoorDash, Uber Eats, Grubhub and ezCater wit" | upheld | Value upheld, evidence replaced. The cited SpeedLine-Marketplace-Brochure.pdf is a sales brochure carrying a grade B label it does not earn, and a differentiator yes needs A or B, so the cell was one bad grade away from collapsing. The Store Manager manual documents the same capability properly - per-marketplace onboarding including DoorDash SSIO, menu publication by Make Live, and orders landing in Terminal - and Taxes for Marketplace Orders corroborates it operationally. Re-pointed to the manual and the paid-subscription and 8.0 R400 preconditions added, which the brochure note omitted. source |
| extensibility-api-versioning-deprecation | unknown / F - "SpeedLine does publish a versioned product release stream - 58 'SpeedLine Releases' post" | resolve-to-partial | The earlier pass reasoned about the release stream from advisory titles only; the 8.0 Release Notes PDF was not in the record. Reading it shows the changelog half of this claim is genuinely satisfied for the Connect API, item by item and by Test Track number, which is more than an unknown allows. The deprecation half fails: 153 advisories contain dated end-of-support notices but no stated notice period and nothing about the Connect message contract, so partial with the shortfall named is the correct score. source |
| reliability-offline-decline-liability | unknown / F - "Store-and-forward itself is documented (enter-tripos-settings.htm exposes an 'Enable Sto" | resolve-to-yes | The prior rationale said in terms that "the triPOS topic renders its field descriptions as an image map with no text". Those descriptions are now readable at Store_Manager_help_Web/jspopups/enable_store_and_forward.js, inlined into the topic, and I fetched both the topic (200, 29,882 bytes) and the fragment (200, 3,829 bytes) directly. They state who bears the loss - the merchant, by an explicit liability prompt - and give both a per-transaction cap and a cumulative per-outage cap, which is exactly what the claim asks for. Grade B vendor product documentation, so the differentiator bar is met. source |
| reliability-sync-conflict-handling | unknown / grade F - 'Checked the architecture topics in the 458-topic Store Manager manual ... No design or archi' | upheld | Re-checked against the three corpora that did not exist when this was scored: the published SpeedLine Portal manual, the inlined field descriptions and the 8.0 Release Notes. Still no last-write-wins, merge or prompt rule. The rationale's assertion that no architecture documentation exists on a resolving host is withdrawn - it does exist and it describes a single-primary database with a one-minute copy to a passive secondary, and a one-way 30-minute pull of store prices into the web menu. Unknown stands on better evidence. source |
| reliability-public-status-page | no / grade C - 'status.speedlinesolutions.com does not resolve (DNS failure, no HTTP response at all), and' | upheld | Re-verified the DNS failure and the 404s myself, re-counted the sitemap at 574 URLs (the note's 501 was stale) and read the full 153-advisory archive that backs the vendor's stated incident channel. The archive publishes maintenance windows and one outage apology as blog posts; there is no component state, no current-status view and no historical incident record. Positive evidence of absence holds. source |
| reliability-contractual-uptime-sla | unknown / grade F - 'No uptime percentage or service-credit remedy is published anywhere reachable: the only agre' | upheld | Corrected two stale facts the rationale rested on (sitemap is 574 URLs not 501; there are three public legal documents not two - /speedlinepayappprivacy, which I read end to end and which carries no availability or service-level term) and extended the search to the 8.0 Release Notes and the full 153-advisory archive. No uptime percentage or credit remedy anywhere. Unknown is still the honest score because the customer agreement itself is not published. source |
| reliability-hardware-replacement-sla | unknown / grade F - 'Read www.speedlinesolutions.com/support-services in full: it enumerates the support offerings' | resolve-to-partial | The 153-advisory archive, which had never been dumped when this was scored, contains a first-party page offering an 'Optional 3-year advanced exchange warranty' on the Ingenico Lane 3000 purchasable through SpeedLine After Market Sales. That is an advance-exchange program available to buy, so a flat unknown understates it; but it covers one payment device rather than the POS estate and states no turnaround time, so it is partial, not yes. I re-read /support-services to confirm it still carries no hardware-replacement offering. source |
| reliability-pci-dss-4-attestation | no / grade B - 'The only compliance validation SpeedLine publishes is PA-DSS validated for SpeedDine - PA-DS' | upheld | Value upheld, note corrected. The old note said no P2PE listing appears anywhere on the site; a 2022 support advisory does say the Ingenico Lane 3000 'Is P2PE certified when using Worldpay Express', but that is the processor's and device's validation and is not an attestation SpeedLine publishes for itself. Against it, the current (Jan 2026) Store Manager help still routes buyers to a PA-DSS Implementation Guide held in the in-product Document Viewer, which is positive evidence that no v4 attestation has replaced it publicly. source |
| reliability-cellular-backup | unknown / grade F - 'Neither manual documents connectivity failover of any kind. The Store Manager Hardware sectio' | resolve-to-no | The two grounds for the unknown were that only two manuals were readable and that settings screens rendered as unreadable image maps. Both are gone: four manuals and every field description are now in the dump, and there is no cellular, LTE or failover control on any screen. The documented alternatives to a lost connection are enumerated instead - triPOS Store and Forward with a per-outage dollar cap, and a store-offline message on the ordering site - which is the enumerated-alternatives pattern that justifies a no rather than an unfound. The gated supported-hardware PDF is named as the residual caveat. source |
| commercial-month-to-month-contract | unknown / grade F - 'No subscription term is published anywhere public. /pricing 404s and the complete 501-URL si' | upheld | Re-enumerated the sitemap (574 URLs, not the 501 the rationale quoted; still no pricing or agreement page), read the third public legal document /speedlinepayappprivacy that the old count missed, and searched all 153 advisories for term, renewal and billing language. The only monthly-billing statement is for the SpeedDine add-on. Nothing establishes or refutes a month-to-month option on the core POS tier, so unknown stands on corrected facts. source |
| commercial-no-early-termination-fee | no / grade B - 'I read the whole of the only agreement SpeedLine publishes. www.speedlinesolutions.com/terms' | upheld | The conclusion is independent of the refuted Portal premise. I re-verified /terms (200) and /legal (404), re-counted the sitemap at 574 URLs, and read the third public legal document the note had missed, /speedlinepayappprivacy, which is an app privacy policy with no commercial term. The document that would carry an ETF clause exists and demonstrably lacks it; nothing in the newly dumped advisory archive changes that. source |
| commercial-autorenew-terms-published | no / grade B - 'The publicly accessible contract terms are exactly two documents, both linked in the site foo' | upheld | Independent of the refuted premise. Re-read /terms and /privacy, added the third public legal document /speedlinepayappprivacy that the note's 'exactly two' had missed, corrected the sitemap count to 574, and searched all 153 advisories for renewal or notice language. No auto-renewal term or cancellation window is published; the no stands on corrected facts. source |
| commercial-rate-increase-clause | unknown / grade F - 'SpeedLine sells first-party processing (SpeedLine Payments, /speedlinepayments and /speedline' | upheld | Corrected the stale sitemap count (574) and legal-document count (three) the rationale rested on, and extended the search to the 153-advisory archive that had never been dumped - which carries Monetra and Worldpay platform notices but no fee schedule and no rate-change provision. The processing agreement remains unpublished, so unknown is still correct. source |
| commercial-module-unbundling | partial / grade E - 'Modules are separately branded, separately brochured and separately sold - Marketplace, Speed' | upheld | The value is right but the evidence was a brochure index graded E, which is the third-party band and does not fit a vendor page at all. Replaced it with product documentation: the Store Manager help enumerates five 'Optional Additions' obtained from an account manager, and an advisory records support upgrades as separately purchasable. That documents separate acquisition, which is the half this cell was crediting; the cancellation-and-repricing half is still nowhere stated, so partial stands at grade B. source |
| commercial-post-termination-export-window | unknown / grade F - 'No contractual retrieval window is published: the footer-linked /terms and /privacy are websi' | upheld | Corrected the legal-surface count (three documents, not two) and the sitemap count (574), read the third document for a retention clause - it has one, but only the vague 'as long as necessary or relevant' app-data form - and added the CCPA advisory's statement that customer data remains in the store system. None of it gives a defined number of days after termination, and the hosted products are still unaddressed, so unknown holds. source |
| commercial-pci-dss-4-controls | no / grade B - 'Nothing addresses the post-31-Mar-2025 future-dated requirements. No MFA-for-CDE statement, n' | upheld | The premise refutation cuts for this cell, not against it: the corpus that was previously unreadable is now complete, and MFA/multi-factor/two-factor/2FA appear nowhere in 784 topics, 870 field descriptions, the 8.0 Release Notes or 153 advisories. The documented control is strong single-factor Windows and SpeedLine passwords with expiry lockouts, referred back to the retired PA-DSS guide, and no script-integrity monitoring is claimed for SpeedDine. That converts an absence-of-mention into an enumerated absence. source |
| extensibility-menu-write-api | no / grade B - "Menu authoring is a desktop and portal function and the integration surface can only r" | downgrade-to-unknown | Contested the enumeration. The `no` was built from a manager-alert string about order messages naming unknown PLUs plus the UI menu lifecycle in the Portal manual, while the Connect/OrderLink message specification - the only document that could settle what an inbound message may write - is admittedly unpublished. SpeedLine's own Connect product sheet lists 'Menu information' and 'Connect API version' among the things Connect messages can contain, which is at minimum inconsistent with 'the integration surface can only reference' the menu. No evidence of a menu write either, so unknown, not partial. source |
| reliability-cellular-backup | no / grade B - 'No cellular or LTE failover exists in the documented product. Searching the whole published c' | upgrade-to-partial | The no rested on a corpus search plus the concession that the supported-hardware PDF was unread behind a DNN login wall. That document is not gated - the Store Manager topic supportedhardware.htm defers to it by name, and a title search finds it served openly at www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/TrainingDocs_SF/SpeedLineMinimumRequirementsAndSupportedHardware.pdf (HTTP 200, 76 KB, ten pages). I read it: the Modems section lists the Digi 6310-DX Cellular Extender Router with Plug-In Modem as a backup modem for internet connection failure requiring a cellular data plan, supported in conjunction with a SonicWall SOHO/SOHO 250, and the Card Processing tables recommend it per processing partner so cards keep authorizing when the line drops. That is documented cellular backup, so the no is refuted; it stays short of yes because it is an optional third-party appliance on the merchant's own data plan rather than terminal-native automatic failover. source |
Sources
Every URL this record cites. 199 in total.
- https://www.speedlinesolutions.com/full-service
- https://www.speedlinesolutions.com/faqs
- https://www.speedlinesolutions.com/partners
- https://www.speedlinesolutions.com/quick-service-and-fast-casual
- https://www.speedlinesolutions.com/delivery
- https://www.speedlinesolutions.com/online-ordering
- https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/MarketingDocs_SF/Ebook_Employee_Management.pdf
- https://www.speedlinesolutions.com/point-of-sale
- https://www.speedlinesolutions.com/hubfs/SpeedLine+%20brochure.pdf
- https://www.speedlinesolutions.com/hubfs/SpeedLine-Marketplace-Brochure.pdf
- https://www.speedlinesolutions.com/enterprise
- https://www.speedlinesolutions.com/hubfs/SpeedLink.pdf
- https://www.speedlinesolutions.com/speedlinepayments
- https://www.speedlinesolutions.com/speedline-marketplace
- https://www.speedlinesolutions.com/speedline-analytics
- https://www.speedlinesolutions.com/speedline-loyalty
- https://www.speedlinesolutions.com/hubfs/SpeedLine%20Connect%20Flyer.pdf
- https://support.speedlinesolutions.com/Home
- https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026
- https://www.speedlinesolutions.com/support-services
- https://www.speedlinesolutions.com/
- https://www.speedlinesolutions.com/guides-and-brochures
- https://www.speedlinesolutions.com/pricing/
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- https://www.speedlinesolutions.com/hubfs/SpeedLine+%20brochure.pdf
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- https://www.speedlinesolutions.com/hubfs/DoorDash%202-page%20brochure.pdf
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- https://www.speedlinesolutions.com/blog/too-many-calls-not-enough-hands-can-ai-fix-the-high-volume-crunch
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- https://www.speedlinesolutions.com/supportadvisories/speedline-loyalty-is-now-available
- not refetchable
- https://www.speedlinesolutions.com/supportadvisories/california-consumer-privacy-act-ccpa-and-speedline
- not refetchable
- https://www.speedlinesolutions.com/supportadvisories/speedline-and-7shifts-join-forces-to-optimize-your-labor
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- https://www.speedlinesolutions.com/supportadvisories/announcing-our-canadian-online-store-0
- https://support.speedlinesolutions.com/Store
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- https://www.speedlinesolutions.com/privacy
- https://www.speedlinesolutions.com/sitemap.xml
- https://www.speedlinesolutions.com/supportadvisories/08/12/25-services-restored
- not refetchable
- https://www.speedlinesolutions.com/supportadvisories/microsoft-update-impacts-network-connectivity-for-some-locations
- not refetchable
- https://www.speedlinesolutions.com/terms
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- https://www.speedlinesolutions.com/supportadvisories/speedline-7.3-release-300-available-now-security-fixes
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- https://www.speedlinesolutions.com/supportadvisories/worldpay-update-removes-msd-contactless-payments
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- https://www.speedlinesolutions.com/supportadvisories
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- https://www.speedlinesolutions.com/supportadvisories/speedline-cloud-reporting-analytics-enhancements
- not refetchable
- https://www.speedlinesolutions.com/supportadvisories/microsoft-ends-support-for-windows-10
- https://www.speedlinesolutions.com/supportadvisories/upcoming-worldpay-cipher-removal-important-action-required
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- https://www.speedlinesolutions.com/speedlinepayappprivacy
- not refetchable
- not refetchable
- not refetchable
- https://170069.fs1.hubspotusercontent-na1.net/hubfs/170069/SpeedLine_Connect_product_sheet.pdf
- https://www.speedlinesolutions.com/hubfs/Portals/0/PublicWebsiteDocs_SF/TrainingDocs_SF/SpeedLineMinimumRequirementsAndSupportedHardware.pdf
- https://www.speedlinesolutions.com/supportadvisories/monetra-discontinued-security-maintenance-ending