Vendors / Enterprise & chain restaurant POS
Focus POS
Long-tenured on-prem restaurant POS ("more than 20 years") sold entirely through a dealer/VAR channel; the site lists POS, Online Ordering, Cloud Reporting and Management, Order and Pay at Table, MobilePay QR, Customer Loyalty, Gift Cards, KDS and a mobile POS app, but publishes no pricing, no OS/spec documentation and no developer docs — nearly every capability below is unverifiable from primary sources.
scored live legacy rubric
- Claims in scope
- 314
- Scored
- 45
- Assessed
- 43
- Unknown
- 271
- Not applicable
- 0
- Values challenged
- 0
unknown, never as no.Identity
- Owner
- Focus POS Systems (private, San Antonio TX; ownership not disclosed on its own site) — sold through a local dealer/VAR network
- Who it is for
- Independent and small-chain full-service restaurants in the US, bought and serviced through a local dealer rather than direct
- Site
- https://www.focuspos.com/
Pricing
transparency: quote-only · unit: unknown (dealer-quoted) · processor lock-in: unknown
- Software
- Not published. No pricing page; the site routes buyers to a regional dealer for a quote.
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
Provides a graphical floor-plan editor where an operator can draw sections, place tables of varying shape/capacity, save multiple floor-plan layouts per location, and assign sections to servers.
order-capture-floor-plan-editor
Not scored by this record.
Order lines can be tagged to a seat number at entry, and the check can be split by seat afterward without re-keying items.
order-capture-seat-level
Not scored by this record.
Items can be assigned to courses and held, with a fire-next-course action available from a handheld or terminal that releases only that course to the kitchen.
order-capture-coursing-hold-fire
Not scored by this record.
Supports splitting a check by item, by seat, by even N-way, and by arbitrary dollar/percentage amount, and merging checks or tables back together, including after partial payment.
order-capture-split-merge
Order Entry > Packages documents Split ("create multiple seats on a check and move Menu Items between those seats. Also allows the employee to move the item portions from one seat to another"), Split Item, Unsplit Item, Cashier Split ("split a check with multiple seats into separate checks"), Cashier Combine, Position Split / Position Split All, Transfer Combine, Transfer Combine/No Seats, Transfer Seat and Transfer Items. Employees > Jobs > Rights adds "Checks - Split After Print", "Checks - Split First Seat After Print" and "Checks - Split Payments" (move payments between seats), so splitting and re-combining survive a printed check and a partial payment. Shortfall: every documented split is by seat, by item or by position - the manual documents no way to split a check by an arbitrary dollar amount or percentage, and no even N-way check split. https://www.focuspos.com/manual/Content/1j_Order_Entry/Packages.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
Opens a bar tab against a card pre-authorization with a configurable auth amount, supports incremental re-auth as the tab grows, and auto-closes stale tabs at end of day. differentiator
order-capture-bar-tab-preauth
Not scored by this record.
An open check can be transferred between servers, tables, and devices, and the transfer is recorded in an audit log naming both employees.
order-capture-transfer-audit
Not scored by this record.
Ships a first-party handheld ordering app running natively on the handheld device (not a remote/mirrored desktop session) that can send to kitchen and take a card payment tableside.
order-capture-native-handheld
Not scored by this record.
With the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen, and tender cash, and the vendor publishes what does and does not work offline.
order-capture-offline-order-entry
Focus is on-premise and runs with no internet at all: Miscellaneous > General > Restaurant offers an Internet Connection Type of "<None> - No Internet connection is present", the alternatives being Dial Up and Always Connected, and the connection is used only for SMTP mail and Close-Day FTP polling. Order entry, modifiers and kitchen send are LAN-local - Stations are Windows machines resolved by Computer Name against a local Focus file server, and Printers > Remotes binds every kitchen printer to a Station on "Com1 through Com32, Lpt1, Lpt2, and IP", with Logic Controls KDS and PartnerTech KVS as port types. Focus also publishes what does NOT work: Close Day > Credit Cards > Offline states the window "is used when the credit card process is not responding due to a phone line or Internet connection being down. When in Offline Mode, credit cards are stored as a swiped transaction but not actually sent to the processor. Therefore, a credit card may be approved 'Offline' but be declined when turned back 'Online'", and Order Entry > Packages carries Offline, Offline Prompt (Credit / Loyalty) and Points Offline commands. Cash tender is unaffected. Caveat carried from the reliability cells: FocusKITCHEN, the separately marketed cloud KDS, has no published offline behaviour. https://www.focuspos.com/manual/Content/1r_Miscellaneous/Restaurant.htm · retrieved 2026-08-04 · not refetchable · site policy · graded B when read
Guest QR at-table ordering writes items onto the same open check as server-entered items, rather than creating a separate order ticket. differentiator
order-capture-qr-same-check
Not scored by this record.
Offers a first-party self-order kiosk that renders the same menu and modifier tree as the POS with no separate menu build, and the vendor documents ADA/accessibility conformance for it. differentiator
order-capture-kiosk-first-party
Not scored by this record.
Supports drive-thru-specific order flow: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment.
order-capture-drive-thru
Not scored by this record.
Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.
order-capture-drive-thru-timers
Not scored by this record.
Vendor ships a first-party AI voice ordering agent for phone and/or drive-thru that injects orders directly as POS orders, or publishes a documented API partner program for third-party voice AI. differentiator
order-capture-voice-ai
Not scored by this record.
Supports order throttling: per-channel capacity limits per time slot with automatic quote-time extension when kitchen load exceeds a configured threshold. differentiator
order-capture-throttling
Not scored by this record.
Accepts future-dated/scheduled orders with a per-channel lead time and automatically injects them into the make queue at a computed fire time rather than on receipt.
order-capture-scheduled-orders
Miscellaneous > General > Customer > Future Orders Options: "Print When Moved - the kitchen chit will print on the day the order is moved, at the specific time the order is due", "Move Orders at Close Day - the Future Orders will automatically move into the current business day at Close Day", and "Print Lead Time (minutes) - the number of minutes prior to the specified order time, that the kitchen chit will print" (zero prints at Close Day). A Future Orders package command enters the order and the check record stores future-order date, time and notes. Shortfall: Print Lead Time is a single system-wide setting on the Customer General window, not a per-channel lead time, and the alternative setting "Print When Entered" fires the chit on receipt. https://www.focuspos.com/manual/Content/1r_Miscellaneous/Customer_General.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.
order-capture-catering
Not scored by this record.
Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator
order-capture-order-ready-signal
Not scored by this record.
Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.
order-capture-void-comp-controls
Not scored by this record.
Menu, modifiers & pricing engine
Payments & money movement
The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator
payments-processor-choice
Not scored by this record.
Vendor publishes card-processing pricing publicly (a specific flat rate or interchange-plus markup) rather than quote-only. differentiator
payments-published-rates
Not scored by this record.
Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator
payments-dual-pricing
Not scored by this record.
Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator
payments-surcharge-guardrails
Not scored by this record.
All first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay.
payments-emv-nfc
Focus sells no first-party terminal; EMV and NFC arrive via processor-supplied semi-integrated pads, and the only pages that say so are 2016 press releases. Mercury (2016-01-29): "EMV and end-to-end encryption (E2E), as well as NFC and tokenization capabilities needed for Apple Pay and other mobile wallets... Customers who utilize the VeriFone VX 805 and have upgraded to Focus POS version X will be able to take advantage"; Sterling (2016-06-07) repeats the pairing ("Focus POS customers who use the VeriFone VX 805 and the latest Focus software") and adds "accept payments from mobile wallets thanks to NFC and tokenization technologies". Named shortfall: acceptance is contingent on the dealer-chosen processor and the named VX 805 pad rather than a property of all terminals; the Setup Manual's own credit-card chapters (Credit Card Direct, NETePay, Close Day > Credit Cards) never mention EMV, chip or contactless - offline cards are "stored as a swiped transaction" - and Google Pay is never named anywhere on the site. https://www.focuspos.com/focus-pos-partners-with-mercury-payment-systems-to-offer-emv-solution/ · retrieved 2026-08-04
Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. differentiator
payments-softpos-tap-to-pay
Not scored by this record.
Vendor ships a handheld that takes EMV/NFC payment at the table, including tip prompt and check splitting, without carrying the card away.
payments-pay-at-table
Not scored by this record.
Guest can scan a QR code on the printed check or table tent to view and pay the check from their own phone, with the payment closing the check in the POS automatically. differentiator
payments-qr-guest-pay
Not scored by this record.
Supports both pre-auth-then-tip-adjust and on-device tip prompt flows, with a documented batch/adjust window and a manager screen for unadjusted tips.
payments-tip-adjust
Not scored by this record.
Configurable tip pooling and distribution rules (by hours worked, sales, role percentage, or points) that produce a per-employee tip allocation exportable to payroll. differentiator
payments-tip-pooling
Not scored by this record.
Card payments can be captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. differentiator
payments-offline-store-and-forward
Not scored by this record.
Vendor publicly documents who bears the loss when a stored offline transaction declines on reconnect, and surfaces a post-reconnect report of failed offline payments. differentiator
payments-offline-decline-liability
Not scored by this record.
First-party gift cards with real-time balance tracking, redeemable across every location in the group and through the online-ordering channel.
payments-gift-cards
Gift Cards listed as a first-party Focus product; cross-location and online-ordering redemption and real-time balance handling not documented. https://www.focuspos.com/ · retrieved 2026-08-01
House/on-account tabs with per-account credit limits, running balance, and periodic statement or invoice generation.
payments-house-accounts
Not scored by this record.
A single check can be settled with multiple tenders and split by seat, by item, by even shares, or by arbitrary amount, with no hard cap below eight ways.
payments-split-tender
Not scored by this record.
Voids, refunds, discounts, and no-sales require role-based authorization (manager PIN or approval) and write to an immutable audit log identifying the approver.
payments-refund-void-controls
Order Entry > Voids defines up to 50 Void reasons and "the user must select a reason to justify the Void of the Menu Item or Payment". Job Rights gate each action separately (Check Items - Void, Payments - Void, Payments - Refunds, Discounts - Approve, Cashier - Open Drawer), and "Always Require Approval - requires the user to enter access code for FOH functions like voids, even when they are logged in". The Discounts/Voids/Audit Report carries "Approved By - the employee that approved the Void" and the same field for discounts and paid outs, with check number, date and time, plus Refunds, Variable Price Items and Drawer Opens sections; the Check Detail window separately retains time, employee and reason for every void, payment void and payment adjustment. The manual never uses the word immutable, but the attribution and the retained check-level record are documented. https://www.focuspos.com/manual/Content/1n_Reports/Sample_Discount_Voids_Report.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator
payments-chargeback-tooling
Not scored by this record.
Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator
payments-card-on-file
Not scored by this record.
Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator
payments-payout-timing
Not scored by this record.
A single account can route settlement funds to different bank accounts per location or legal entity (separate MIDs or split settlement) under unified reporting. differentiator
payments-multi-entity-routing
Not scored by this record.
Vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance / P2PE listing available to merchants on request.
payments-p2pe-pci4
Not scored by this record.
Kitchen & production
Items route to specific KDS stations by item, category, order type, or revenue center, with routing rules configurable per location without vendor involvement.
kitchen-station-routing
Routing is item-level and operator-configurable per Location. Printers > Groups establishes "a maximum of 32 Printer Groups... logical groupings of similar Menu Items that are assigned to Remote Printers"; each Menu Item carries its Printer Group. Locations > Locations > Printer Assignments then maps group to destination: "Menu Items assigned to Printer Groups will be printed at the Remote Printers selected... Multiple Remote Printers may be selected for each Printer Group", with three named, time-activated assignment sets ("i.e., Normal, Busy, Hot Only") each with an Active Time range, so "Printer Groups may be routed to different Remote Printers based on the time of day". The destination may be a KDS: Printers > Remotes lists Port types including "Logic Controls KDS - Interfaces with the Logic Controls KDS" and "PartnerTech KVS". No vendor involvement is required - the screens sit in Focus Setup behind Job Rights 'Office - Locations' and 'Printer Groups'. Routing key is the per-item Printer Group (optionally time-of-day), not order type or revenue center; Remotes exposes order type only as a Remote Check Format selector. https://www.focuspos.com/manual/Content/1l_Locations/Printer_Assignments.htm · retrieved 2026-08-04 · not refetchable · site policy · graded B when read
An expo screen consolidates items from multiple prep stations into a single order view and only marks the order complete when every contributing station has bumped its items.
kitchen-expo-consolidation
CLAIM: an expo screen consolidating multiple stations, completing only when all have bumped. VERDICT: unknown. NEW SURFACE: the anonymous Zendesk Help Center API at focuspos.zendesk.com (rendered at help.focusca.com; 338 articles held; publisher is Focus POS California, the CA/AZ/NV regional Focus operation at focusca.com, not Secret POS Systems Inc. itself - hence grade C; an href fixpoint over the bodies found 6 absent ids: 3 return 401 gated, 1 returns 404, so the KB is NOT a census), including "Focus Kitchen Release Notes" 1.0-1.9 (https://help.focusca.com/hc/en-us/articles/360039260111): per-device station names, recall, urgent time and bumping, but no expo view or cross-station completion rule. CONTROLS (tokenised) over 338 KB articles + 356 focuspos.com WP pages/posts: expo/expediter/expeditor 3 hits in 2 docs - "expo printers" in a wiring checklist (360031636171) and "an expo person" in tip-share setup (360059608251); neither is a KDS screen. The 74-request Focus POS API collection at https://api.focuspos.com/ has no kitchen-display endpoints. KB not a census (3 gated ids), so no no. Retrieved 2026-09-16. || 321st: NEW SURFACE 2026-09-17: the Focus Setup User Manual at https://www.focuspos.com/manual/ (MadCap Flare build 10/23/2019, live production, 546 topics in Toc_Chunk0/1.js; generic robots bar on /manual/, no ClaudeBot name). Only 199 of 546 topic bodies were retrieved before the Sucuri WAF refused all further requests (and Wayback CDX returned 503/429), so it is NOT a census. In the held topics, kitchen display exists only as third-party controllers driven as remote printers ('Logic Controls KDS', 'PartnerTech KVS' in https://www.focuspos.com/manual/Content/1h_Printers/Remotes.htm) with send-timing 'Kitchen Video Options' None / On the Fly / One Behind / At Payment (Locations3.htm). CONTROLS (tokenised, case-insensitive) over the 199 topics: expo 0, expediter/expeditor 0; 'expedite' 1 hit ('the Liquor Modifier Canvas can automatically be displayed to expedite entry' - POISON, order-entry speed). No expo view or all-stations-bumped completion rule described; corpus incomplete, so no no. Retrieved 2026-09-17. || 329th: MERGE HOLD (proposed partial/C, held unknown): Every expo-screen quote is on focusca.com, a regional DEALER's site (third party, grade D), while the vendor's own closed FocusKITCHEN feature list names no expo screen; the vendor's only related sentence contradicts conjunct 2. The agent flags it as the weakest row of its session. Held. PROPOSAL AS WRITTEN: 329th: NEW SURFACES, and the first evidence that an expo screen exists. (1) https://www.focuspos.com/solutions/kitchen-display-system-pos-focuskitchen/ - the FocusKITCHEN product page, which was NOT in the 315th WordPress corpus and is unmined: 'Cloud-Based Kitchen Display System / Streamline Order Prep from Online, In-House, and Drive-Thru', with a closed 'FocusKITCHEN Features' list: 'Bump individual items | Check recall | Dynamic item routing | Decrease paper waste | Bump individual items | Bump to print | Prioritize rush orders | Bump to text'. (2) https://focusca.com/2022/07/01/kds-is-for-your-entire-operation-not-just-the-kitchen/ states of Focus Kitchen: 'Expo screens and line screens can display the same information or different pieces of the order based on your routing rules', 'Orders can be bumped from or to different screens allowing prep to progress across the line', 'Manager functionality from the screens allows kitchen managers to view and update stock status from expo screens. All-day counts allow your expos and line cooks to see total prep counts for current orders.' That satisfies the FIRST conjunct - a named expo screen that can display the whole order while line screens receive routed pieces, with all-day counts for the expo - so this is no longer unknown. SHORTFALL, which is the claim's second conjunct: no source anywhere states that the order is marked complete only when every contributing station has bumped its items, and the vendor's own page https://www.focuspos.com/integrate-self-serve-kiosks-with-qsr-pos-system/ describes the opposite ('They can route individual items to the most efficient station, bump items when there is a lag, and mark off items as complete even if the entire order isn't ready'), i.e. per-item completion independent of the order. GRADE: C, and the reason is the publisher - the expo-screen quotes are on focusca.com, Focus POS California, the CA/AZ/NV regional Focus operation, not Secret POS Systems Inc.; the focuspos.com quotes are marketing/blog. CORPORA CONTROLLED for this cell, all confirming the absence of any expo-completion rule: the now-complete Focus Setup User Manual (559 topics / 3,410,540 chars, TOC + a 75-topic orphan href fixpoint, residue 2 dead/malformed paths) - 'expo' 0, `expedit\w*` 1 and it is POISON ('the Liquor Modifier Canvas can automatically be displayed to expedite entry'), `consolidat\w*` 21 and every one is POISON, guest-check/chit consolidation of identical menu items ('Consolidate: Consolidates Menu Items that have the same prices and modifiers', Guest_Check.htm); the re-paged focuspos.com WP corpus (356 docs, 1,719,142 chars) - 'expo' 0, 'expediter'/'expeditor' 0; the re-paged focuspos.zendesk.com KB (338 articles, unchanged) - 'expo' 2 (POISON: 'expo printers' in FOCUS-Wiring-Power-Requirements, 'you don't have an expo person' in Hub-Tip-Share-Setup), 'expediter' 1 (POISON: 'printers used to print orders to the kitchen, bar or expediter'). NOTE ON BOUNDS: the manual is a 10/23/2019 MadCap Flare build of the legacy Focus POS setup application and does NOT cover FocusKITCHEN, the later cloud KDS, which has no published documentation at all (the 'FocusKITCHEN Brochure' link at /focuskitchen-brochure/ is a form page, and Wayback holds only brochure cover IMAGES, no PDF) - so no `no` could rest on the manual for a FocusKITCHEN behaviour. WEAKEST POINT, stated plainly: the entire positive case is grade-C marketing prose from a regional Focus operation; if the owner judges 'expo screens can display the same information' too thin for the consolidation conjunct, this should return to unknown rather than become a yes. Retrieved 2026-09-18. adversarially verified
Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator
kitchen-course-firing
Not scored by this record.
Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator
kitchen-prep-time-pacing
Not scored by this record.
Kitchen load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator
kitchen-order-throttling
Not scored by this record.
Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator
kitchen-channel-pause-propagation
Not scored by this record.
Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator
kitchen-order-ready-callback
Not scored by this record.
KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.
kitchen-bump-bar-hardware
NEW SURFACES 2026-09-17. (1) The Focus Setup User Manual at https://www.focuspos.com/manual/ is LIVE again: a MadCap Flare WebHelp2 build (Data/HelpSystem.xml BuildTime 10/23/2019, BuildVersion 11.1.2.31113; Last-Modified 2019-10-23, so it is a dated but production copy). robots.txt bars /manual/ under a generic 'User-agent: *' only (no ClaudeBot/anthropic name), fetched per the standing browser-UA order. Toc_Chunk0/1.js list 546 topics. Only 199 bodies were retrieved before the host's Sucuri WAF began refusing every request (429/403/307, then connection timeouts site-wide, still refused ~30 min later); Wayback CDX returned 503/429. So the manual is NOT held as a census and no no may rest on it. What it holds: 'Remotes Printers Window' (https://www.focuspos.com/manual/Content/1h_Printers/Remotes.htm) enumerates remote-printer ports 'Com 1-32', 'LPT 1-2', 'IP', 'Logic Controls KDS - Interfaces with the Logic Controls KDS.', 'PartnerTech KVS - Interfaces with the PartnerTech KVS.' - i.e. the legacy Focus POS drives third-party kitchen video controllers as remote printers; Locations 'Kitchen Video Options' are None / On the Fly / One Behind / At Payment (send timing only). The 'Devices Window' enumeration (Serial NFC, Scanner, Scale, Pole Display, Drawer, Changer, Caller ID, Fingerprint, Berg, Bar Vision, IP Log/Camera, Text Inserter, Order Confirmation, Pole Disp (ASCII), Panasonic/RI/Partner Tech/RSS drawers, Fingerprint 64 bit) has no bump bar or keypad. CONTROLS over the 199 held topics (tokenised, case-insensitive): 'bump bar'/bumpbar 0; bump 2 hits, both timekeeping 'Bump Up Early Clock Ins' (POISON); KDS 2, KVS 2, 'Kitchen Video' 1 (the lines quoted above). No statement that Focus supports bump bars; naming a third-party KDS controller is not the bump-bar claim, so no partial. (2) crt.sh %.focuspos.com (16 names) and %.focusca.com (28 names), every resolving host probed for /swagger, /swagger/v1/swagger.json, /openapi.json, /api-docs, /docs, /sitemap.xml and a nonsense path: boh, boh-staging, marketplace, marketplace-staging, licensing, pos-api-staging all 404 on every path (empty body); office-staging and onlineorder are SPA catch-alls (same body for the nonsense path); focuslink 403/404; portal.focusca.com 403; store.focusca.com 404; no spec found. NEXT PASS: re-crawl the remaining 347 manual topics slowly (1 request / several seconds) once Sucuri lifts the block. Retrieved 2026-09-17. || 329th: MERGE HOLD (proposed no/B, held unknown): The note's own bound says the 2019 manual 'does NOT cover FocusKITCHEN, the later cloud KDS, which has no published documentation at all'. A bump bar attaches to the KDS, not to the POS Devices Window, so a census of the legacy POS setup manual does not bound the KDS product (325th rule: a census of one app does not bound another). The manual census itself (559 topics, 544/545 TOC + 75 orphans) is recorded. PROPOSAL AS WRITTEN: 329th: THE MANUAL IS NOW A CENSUS. The Sucuri block lifted; the remaining topics were fetched one at a time >= 3.2 s apart with a browser UA (generic `*` bar on /manual/ only, re-read today: no ClaudeBot/anthropic-ai name). Held: 559 topic bodies, 3,410,540 chars of stripped text - the 545 Toc_Chunk0/1.js entries (544 at 200; the 545th, /Content/1n_Reports/Page=Employees.htm, is a MALFORMED toc entry with a query-string-shaped filename and 403s on re-probe) PLUS 75 ORPHAN topics that no TOC entry lists, found by running an href/src fixpoint over all the bodies to a stable round (rounds 2 and 3 produced no new file). Residue after the fixpoint: exactly 2 paths, /Content/1t_Close_Day/How_To_Section/Cash_Trays_Section.htm (confirmed 404, a dead link inside the manual) and the malformed toc entry above. ENUMERATION THAT CARRIES THE ZERO: the 'Devices Window' topic (https://www.focuspos.com/manual/Content/1l_Locations/Devices.htm) is the manual's complete per-station peripheral list, a closed Field/Description table introduced as 'Devices define the communication details for each peripheral attached to the Station' and enumerating Serial NFC, Scanner, Scale, Pole Display, Drawer, Changer, Caller ID, Fingerprint, Berg, Bar Vision, IP Log/Camera, Text Inserter, Order Confirmation, Pole Disp (ASCII), Drawer 1 (Panasonic), Drawer 1 (RI=Open), Partner Tech, RSS Drawer, Serial NFC, Fingerprint (64 bit) - it has a drive-thru Order Confirmation board but NO bump bar and no programmable keypad. The only kitchen-video surface in the whole manual is the 'Remotes Printers Window' Port list, where 'Logic Controls KDS - Interfaces with the Logic Controls KDS' and 'PartnerTech KVS - Interfaces with the PartnerTech KVS' are PORTS for a remote printer, i.e. third-party controllers driven as print destinations. CONTROLS (tokenised, word-boundary, case-insensitive; known-positive 'KVS' returned 7 on the same normaliser): over the 559 topics - 'bump bar' 0, `bump[\s-]?bar` 0, bumpbar 0, `key[\s-]?pad` 1 and that one hit is POISON ('Enter Amount When selected, a keypad is displayed to allow the employee to enter the amount', an on-screen payment keypad in Packages.htm), 'bump' 10 and ALL ten are timekeeping ('Bump Up Early Clock In', 'Bump Back Late Clock In' in Rights.htm/Schedules.htm/How_to_Clock_In.htm). NEW SURFACES also controlled for this cell, both zero: (a) the focuspos.com WordPress corpus re-paged today via wp-json (123 pages + 233 posts = 356 docs, 1,719,142 chars; `/wp-json/wp/v2/types` also revealed custom types `features` 6 and `my-product` 12, which are theme demo content, plus clients/galleries/testimonial - nothing product) - 'bump bar'/bumpbar/keypad 0, and the FocusKITCHEN product page's own closed feature list is 'Bump individual items | Check recall | Dynamic item routing | Decrease paper waste | Bump individual items | Bump to print | Prioritize rush orders | Bump to text' with no bump bar; (b) the focuspos.zendesk.com Help Center API re-paged today, still exactly 338 articles / 736,344 chars, unchanged since the 315th - 'bump bar' 0, keypad 5 and all five are POISON ('from the Main Focus Login, choose the Wrench Icon on the log-in Keypad'). VERDICT: no. The claim requires physical bump bars or programmable keypads WITH documented supported models; the vendor's own complete setup manual enumerates every supported station peripheral and every remote-printer port and names none, and no other vendor surface mentions one. Retrieved 2026-09-18. adversarially verified
An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.
kitchen-all-day-counts
Not scored by this record.
Configurable target cook times per station or order type, with visual color escalation and/or audible alert when a ticket exceeds target.
kitchen-sla-alerts
Not scored by this record.
If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator
kitchen-printer-fallback
Not scored by this record.
KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator
kitchen-offline-operation
Not scored by this record.
Station screens can display item-level build/assembly detail (recipe steps, portioning, or full modifier breakout) rather than only the ticket line text. differentiator
kitchen-item-build-screens
Not scored by this record.
Sectioned/fractional topping placement (halves, quarters, specific sections) is rendered visually and unambiguously on the make-line screen or ticket. differentiator
kitchen-pizza-fractional-display
Not scored by this record.
A bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order.
kitchen-recall-refire
Not scored by this record.
Edits made in the POS to an order already displayed in the kitchen visually flag the added, changed, or removed items on the live ticket. differentiator
kitchen-order-modification-alerts
Not scored by this record.
Bumping an order ready triggers a guest-facing notification — SMS/text, app push, or an order-status display board — without a separate product purchase. differentiator
kitchen-guest-ready-notification
Not scored by this record.
Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.
kitchen-waste-logging
Not scored by this record.
Reports actual ticket and per-station times (average and percentile) sliced by daypart, station, and order channel, exportable to CSV or an API.
kitchen-speed-of-service-reporting
Not scored by this record.
Generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list.
kitchen-prep-forecasting
Not scored by this record.
Delivery, dispatch & third-party channels
Product includes a native in-house driver module: drivers are first-class entities with clock-in/out, assignment state (in-store / on-run / returning), and per-driver run history reportable from the POS itself (not via a third-party add-on).
delivery-driver-roster
The driver module is native and in the core manual, not an add-on. Employees > Jobs > Rights: "Customer - Driver - Allows the user to be the delivery driver. Drivers may be assigned checks with the 'Driver' command as well as the 'Assign' command on the Dispatch screen. Drivers are automatically prompted to close their open orders to cash when returning from route when logging in", plus "Customer - Dispatch", "Customer - Dispatch to Any Driver" and "Customer - Print Check When Assigned". Drivers clock in and out like any employee at the Order Entry Time Clock. Named shortfall: the rest of the claim is undocumented - no assignment-state model (in-store / on-run / returning; the return prompt at login is the only documented state transition) and no per-driver run-history report: the manual's report catalogue of 50-odd reports contains no driver or delivery report, and the Employee Performance Report's fields are guest counts and sales metrics with nothing about deliveries. https://www.focuspos.com/manual/Content/1d_Employees/Rights.htm · retrieved 2026-08-04 · not refetchable · site policy · graded B when read
Provides a dedicated dispatch/expo screen showing undispatched orders, driver availability, and elapsed time per order, with multi-order run batching (assigning 2+ orders to one driver as a single run).
delivery-dispatch-board
A dedicated Dispatch Window exists. Order Entry > Order Types: "Delivery Pending - the Check is placed in the Delivery Pending state automatically. A check in the Delivery Pending state automatically appears on the Dispatch Window." Job Rights: "Customer - Dispatch - allows the user to dispatch checks to drivers. All checks that are Delivery Pending appear on the Dispatch Screen"; "Customer - Dispatch to Any Driver"; "Customer - Driver - drivers may be assigned checks with the Driver command as well as the Assign command on the Dispatch screen. Drivers are automatically prompted to close their open orders to cash when returning from route." Locations can display the Dispatch Window at login. Shortfall: the manual documents no driver availability state (in-store / on-run / returning), no elapsed-time-per-order column, and no multi-order run batching - checks are assigned to a driver one at a time. https://www.focuspos.com/manual/Content/1d_Employees/Rights.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
Dispatch includes a live map view with geocoded stops and system-generated route sequencing (turn order optimization) for a multi-stop run, not just a static address list. differentiator
delivery-route-map
Not scored by this record.
Captures live driver GPS position from a driver-facing mobile app and surfaces it back to the dispatch screen. differentiator
delivery-driver-tracking
Not scored by this record.
Delivery areas can be defined as arbitrary map polygons or by drive-time isochrones, not solely as a radius or a ZIP/postcode list. differentiator
delivery-zones-polygon
Not scored by this record.
Each delivery zone carries its own independently configurable delivery fee, order minimum, and quoted promise time, applied automatically from the validated customer address.
delivery-zone-pricing
Customers > Zones establishes up to 100 Delivery Zones, each carrying its own Gratuity Fee and Order Type Fee as either a Flat dollar amount or a Percentage with a Rate, plus an Active Time range limiting when the fee applies; Order Entry > Order Types > "Delivery Zone Fee - if selected, the fees configured in Customers > Zones will apply to each customer tied to a particular Zone". Shortfall: the zone record holds a fee only - there is no per-zone order minimum and no per-zone quoted promise time. Zone is also a field stored on the customer record (Order Types > Customer > Zone) rather than derived automatically from a validated or geocoded address. https://www.focuspos.com/manual/Content/1e_Customers/Zones.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.
delivery-address-validation
Not scored by this record.
Tracks per-delivery driver compensation inputs — mileage or distance driven per run, per-delivery flat reimbursement, and driver-retained tips — and exports them to payroll as separate reimbursement vs. wage lines. differentiator
delivery-driver-comp
Not scored by this record.
Provides a driver cash bank / settle-up flow that reconciles cash collected, orders assigned, and tips owed at end of shift, producing a per-driver over/short figure.
delivery-cash-reconcile
Not scored by this record.
Can hand a first-party order to an on-demand courier marketplace (DoorDash Drive, Uber Direct, Nash, Relay or equivalent) natively from the POS, with the courier quote and status returning into the order record.
delivery-daas-dispatch
Not scored by this record.
Supports hybrid dispatch: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. differentiator
delivery-daas-fallback
Not scored by this record.
Offers direct, first-party certified API integrations with DoorDash, Uber Eats, and Grubhub marketplaces (vendor-owned, not solely resold through Otter/Deliverect/Chowly/ItsaCheckmate middleware). differentiator
delivery-3p-direct-integration
Not scored by this record.
Third-party marketplace orders inject automatically into the POS as normal tickets that fire to KDS/printers without tablet re-keying or manual accept.
delivery-3p-injection
Not scored by this record.
Marking an item or modifier 86'd in the POS pushes item-level out-of-stock status to connected third-party channels in near real time, and restores it on availability (DoorDash requires item and item-option 86ing of new POS partners).
delivery-86-sync
Not scored by this record.
Store can be paused/deactivated on each connected third-party marketplace from inside the POS with a timed auto-reactivation, rather than only from each marketplace's own tablet or portal.
delivery-store-pause
Not scored by this record.
Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. differentiator
delivery-3p-reconciliation
Not scored by this record.
Vendor exposes integration health to the operator — failed/rejected order injections, connection status per channel, and alerts on failure — rather than failing silently. differentiator
delivery-injection-error-visibility
Not scored by this record.
Guests receive a branded order status / driver tracking page or SMS link on the restaurant's own domain for first-party delivery orders, driven by real order and driver state.
delivery-tracking-page
Not scored by this record.
Quoted delivery promise times adjust dynamically from current kitchen load, driver availability, and zone drive time, rather than a fixed per-store constant. differentiator
delivery-promise-time
Not scored by this record.
Vendor documents explicit offline behavior for delivery: whether cash delivery orders, driver assignment, and driver settlement continue during an internet outage.
delivery-offline-behavior
Not scored by this record.
Digital ordering & guest-facing channels
Vendor ships a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission.
digital-first-party-web
First-party Online Ordering product plus MobilePay QR ordering marketed; commission model and branded-domain behavior not stated. https://www.focuspos.com/ · retrieved 2026-08-01
Vendor offers a branded native iOS and Android ordering app (published under the restaurant's own brand in the App Store/Play Store), not only a mobile web page or a shared multi-restaurant marketplace app. differentiator
digital-native-app
Not scored by this record.
Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels.
digital-account-saved-payment
CLAIM: guest accounts with saved addresses, saved tokenized payment methods and one-tap reorder across first-party channels. VERDICT: partial. EVIDENCE: the anonymous Zendesk Help Center API at focuspos.zendesk.com (rendered at help.focusca.com; 338 articles held; publisher is Focus POS California, the CA/AZ/NV regional Focus operation at focusca.com, not Secret POS Systems Inc. itself - hence grade C; an href fixpoint over the bodies found 6 absent ids: 3 return 401 gated, 1 returns 404, so the KB is NOT a census). "FocusOnline Available Features" (https://help.focusca.com/hc/en-us/articles/360046922872): "Guests can add a password to store their information for faster checkout next time."; "FocusOnline: Guest Ordering Process" (360048828871): "From the confirmation area, the guest can input a password to save their information for a faster checkout process the next time they order." Saved card tokens exist on the pay-at-table channel: "Focus MobilePay: Cloud Setup & Options" (360059925012): "When a guest uses a credit card, Focus MobilePay securely stores that card token and presents it to the guest for future use. Only venues using Focus POS with Shift4 Payments have access to this feature." SHORTFALL: no reorder or order-history function is documented for FocusOnline (every reorder hit in the 37,634-character FocusOnline Release Notes is admin menu reordering), the stored FocusOnline information is not stated to include the card, and card storage is Shift4-only. Retrieved 2026-09-16. https://help.focusca.com/hc/en-us/articles/360046922872-FocusOnline-Available-Features · retrieved 2026-09-16 adversarially verified
Digital checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator
digital-upsell-engine
Not scored by this record.
Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.
digital-scheduled-pacing
Not scored by this record.
Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.
digital-fulfillment-modes
Not scored by this record.
Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.
digital-qr-table
Not scored by this record.
Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator
digital-kiosk
Not scored by this record.
Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.
digital-group-ordering
Not scored by this record.
Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator
digital-catering-portal
Not scored by this record.
Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator
digital-voice-ai-phone
Not scored by this record.
Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.
digital-drivethru-ai
Not scored by this record.
Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.
digital-sms-ordering
Not scored by this record.
Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator
digital-google-order
Not scored by this record.
Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.
digital-apple-business-connect
Not scored by this record.
Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.
digital-loyalty-attach
Not scored by this record.
Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.
digital-subscriptions
Not scored by this record.
Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.
digital-promo-parity
Not scored by this record.
Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator
digital-guest-data-ownership
Not scored by this record.
Digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.
digital-checkout-pci-sca
Not scored by this record.
Digital channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator
digital-surcharge-transparency
Not scored by this record.
Guest data, loyalty & marketing
Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.
guest-loyalty-unified-profile
myFocus Loyalty "is a web-based loyalty program that centralizes loyalty members and plans into a single database. Members can accumulate points at one store and redeem them at another", and Manage Members holds one record per card number with name, address, phone, birth date and anniversary; store-side, the Customer Account Loyalty Detail window rolls up first order, last order, number of orders, cumulative sales and coupons issued/redeemed per customer. Shortfall: identity is the loyalty card number - the documentation describes no automatic phone or email match, no dedup or merge behaviour, and no attachment of first-party web ordering (which Focus routes through a third-party online-ordering processor) or kiosk traffic to the same member record. https://www.focuspos.com/manual/Content/myFocus_Web_Suite/Loyalty_MF.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
Orders arriving from third-party marketplaces (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. differentiator
guest-loyalty-thirdparty-identity-attach
Not scored by this record.
Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.
guest-loyalty-accrual-models
CLAIM: at least two of points-per-dollar, visit/punch-count and spend-tier accrual as configuration. VERDICT: yes (grade C). EVIDENCE: https://www.focuspos.com/myfocus/customer-loyalty-program/ enumerates the plans: "Points: Points are assigned to menu items, and when customers accumulate enough points, they receive a reward. Sales: Customers earn points for each dollar they spend. 'Around the World': Customers earn points for purchasing a variety of different menu items. Incremental: Customers can attain different levels based on visits or dollar amounts." plus "Unlimited plans". Sales (points per dollar) and Incremental (levels by visits or dollars) are two of the three models, native to myFocus. Corroborated in the anonymous Zendesk Help Center API at focuspos.zendesk.com (rendered at help.focusca.com; 338 articles held; publisher is Focus POS California, the CA/AZ/NV regional Focus operation at focusca.com, not Secret POS Systems Inc. itself - hence grade C; an href fixpoint over the bodies found 6 absent ids: 3 return 401 gated, 1 returns 404, so the KB is NOT a census): "Add Bonus Points To Your MyFocus Loyalty Plan" (https://help.focusca.com/hc/en-us/articles/360003839092: "customers earning points for their MyFocus Loyalty accounts based on the current Points Plan... Bonus points awarded based on multipliers on certain days of the week") and "FocusRewards - Plan Setup" (360052463251: "After X Spent - How much does a guest need to spend to earn a reward coupon?"). Grade C: the plan-type enumeration is marketing copy and no KB article documents the Incremental plan's fields. Retrieved 2026-09-16. https://www.focuspos.com/myfocus/customer-loyalty-program/ · retrieved 2026-09-16 adversarially verified
Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator
guest-loyalty-tiers
Not scored by this record.
Documents explicitly what loyalty lookup, accrual, and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). differentiator
guest-loyalty-offline-behavior
Not scored by this record.
Offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. differentiator
guest-loyalty-offer-stacking-rules
Not scored by this record.
Offers can be issued to a dynamically defined audience (rules over recency, frequency, spend, or items purchased) rather than only broadcast to the whole list. differentiator
guest-loyalty-targeted-offers
Not scored by this record.
Automatically computes recency/frequency/monetary or equivalent lifecycle segments (new, regular, at-risk, lapsed, VIP) without the operator building the queries. differentiator
guest-loyalty-rfm-segmentation
Not scored by this record.
Ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns rather than one-off manual sends.
guest-loyalty-lifecycle-automation
CLAIM: triggered always-on birthday, first-visit thank-you and lapsed win-back automations. VERDICT: partial. EVIDENCE: the anonymous Zendesk Help Center API at focuspos.zendesk.com (rendered at help.focusca.com; 338 articles held; publisher is Focus POS California, the CA/AZ/NV regional Focus operation at focusca.com, not Secret POS Systems Inc. itself - hence grade C; an href fixpoint over the bodies found 6 absent ids: 3 return 401 gated, 1 returns 404, so the KB is NOT a census). "FocusRewards - Plan Setup" (https://help.focusca.com/hc/en-us/articles/360052463251) documents always-on triggered SMS: "SMS Welcome Message - The SMS/text message sent to a guest the first time they are attached to a transaction", "Send SMS when new members added", "SMS on points added", "SMS on new coupon" - a first-visit message ships. SHORTFALL: no birthday or lapsed/win-back trigger is documented. myFocus campaigns are manual and static: "myFocus Marketing Lists" (360003860031): "Marketing Campaigns are static. Once saved, only the current members are saved to the list. The list will not automatically add new members who meet the set criteria"; "myFocus Marketing Templates" (360003860011): "select Send to send your email immediately" (birthday appears only as a merge field). CONTROLS over 338 KB articles + 356 focuspos.com WP pages/posts (tokenised): birthday/lapsed/win-back/anniversary 10 hits in 6 docs - the four WP docs are blog advice (e.g. build-your-own-restaurant-tech-stack: "Haven't seen a customer in a while? No problem! Reach out with a special offer"), the KB hits are the merge field and a release-note bug ("A birthday bomb"). Not a no: the KB is not a census (3 gated ids). Retrieved 2026-09-16. https://help.focusca.com/hc/en-us/articles/360052463251-FocusRewards-Plan-Setup · retrieved 2026-09-16 adversarially verified
Sends both email and SMS campaigns natively from the platform, not solely by handing the list to a third-party ESP. differentiator
guest-loyalty-native-email-sms
Not scored by this record.
Captures per-channel marketing consent with timestamp and source of consent, and honors revocation received by any reasonable means (not just the STOP keyword) across all channels.
guest-loyalty-consent-management
Not scored by this record.
Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.
guest-loyalty-10dlc-registration
Not scored by this record.
Reports redemption and incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. differentiator
guest-loyalty-campaign-attribution
Not scored by this record.
Provides self-serve export of the full guest list and transaction history, including contact PII, via CSV or API, without a vendor fee or support ticket. differentiator
guest-loyalty-data-export-portability
Not scored by this record.
Exposes a documented outbound guest and order event API or webhook stream that a CDP or marketing platform can subscribe to (e.g. Olo, Punchh, Bridg, Klaviyo). differentiator
guest-loyalty-cdp-event-api
Not scored by this record.
Triggers post-transaction feedback requests and routes responses by score, sending low scores to private service recovery and high scores toward public review sites. differentiator
guest-loyalty-review-capture-routing
Not scored by this record.
Includes a native referral mechanic with per-guest codes or links, attribution of the referred guest's first order, and two-sided rewards.
guest-loyalty-referral-program
Not scored by this record.
Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance, as an alternative to requiring a branded app download. differentiator
guest-loyalty-wallet-pass
Not scored by this record.
Provides admin tooling to fulfill guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records.
guest-loyalty-privacy-rights-tooling
Not scored by this record.
Enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log.
guest-loyalty-redemption-fraud-controls
Not scored by this record.
Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing (claim-level; verify it is a shipped product feature, not a roadmap statement). differentiator
guest-loyalty-ai-offer-recommendation
Not scored by this record.
Offers native stored-value/gift card balances tied to the same guest profile and redeemable across all locations of the brand.
guest-loyalty-stored-value-gift
Not scored by this record.
Labor & workforce
Employees clock in and out at the POS terminal using a PIN, badge, or card, with no separate time-clock hardware required.
labor-clock-in-at-pos
The time clock is the POS terminal itself: "While in Focus Order Entry, select the Time Clock icon", and "Employees may clock in with an Access Code, Magnetic Card or with a Fingerprint Scanner" - i.e. PIN-style code, card or biometric, with no separate time-clock hardware described anywhere. How to Clock In walks the same flow on "the Focus Order Entry Screen": enter the Access Code "via the Number Pad, Magnetic Card or Fingerprint Scanner", select a Job if scheduling is not used, touch Clock In; a Clock In Chit prints. On Break / Off Break buttons and a "Required Break Minimum" option handle breaks, and job rights can require manager approval of the punch. https://www.focuspos.com/manual/Content/Front_of_House/Time_Clock.htm · retrieved 2026-08-04 · not refetchable · site policy · graded B when read
Captures a photo at punch (or performs facial verification) attached to the timecard entry, with a photo-only mode available that stores no biometric template. differentiator
labor-photo-punch-verification
Not scored by this record.
Supports mobile clock-in restricted by geofence or location validation for staff who do not punch at a fixed terminal.
labor-geofenced-mobile-punch
Not scored by this record.
Records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, with the behavior documented. differentiator
labor-offline-time-punch
Not scored by this record.
Permissions are grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers.
labor-granular-rbac
Employees > Jobs > Rights grants roughly 200 individually switchable Job Rights per Job, enumerated one discrete action at a time - Check Items - Void, Discounts - Approve, Payments - Refunds, Payments - Void, Payments - Force, Cashier - Open Drawer, Cashier - Open Any Drawer, Menu - Change Item Price, Checks - Split After Print, Report Security Code (1-9) and so on - rather than fixed cashier/manager/admin tiers. Rights extend across all of an employee's Jobs except where marked (NE), which "only considers the Job associated with the employee's clock in". Above store, Focus Enterprise keeps a parallel Rights window over Corporate User Groups and Setup > Users assigns each user both a set of Rights and a restaurant Group. https://www.focuspos.com/manual/Content/1d_Employees/Rights.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
Manager overrides and approvals are attributed to the individual approver and written to an immutable audit trail queryable after the fact.
labor-manager-override-audit
The Discounts/Voids/Audit Report attributes each override to the individual approver - "Approved By: The employee that approved the Discount", "Approved By: The employee that approved the Void", and the same field on Paid Outs - alongside check number, date, time and reopen time, and can be sorted and totalled by Approved By. Further sections cover Refunds, Variable Price Items, Tax Exempt, Deletes, Kitchen Comments, Drawer Opens, Time Card Audits and Schedule Audits. Order Entry > Checks > Detail independently retains, per check, the employee and timestamp for each void, payment void and payment adjustment, so the trail is queryable after the fact. Tamper-evidence is not asserted by the vendor. https://www.focuspos.com/manual/Content/1n_Reports/Sample_Discount_Voids_Report.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
Builds and publishes employee shift schedules inside the same platform that holds the timekeeping data, rather than requiring a third-party scheduling app. differentiator
labor-native-scheduling
Not scored by this record.
Generates recommended staffing levels or labor hours by daypart from the operator's own POS sales history, not just a static template. differentiator
labor-demand-labor-forecast
Not scored by this record.
Displays labor cost as a percentage of sales in real time during service on a manager view or POS, not only in end-of-day or next-morning reports. differentiator
labor-realtime-labor-percent
Not scored by this record.
Warns or blocks at clock-in when an employee is approaching or would cross a configured overtime threshold, before the overtime is incurred. differentiator
labor-overtime-prevention
Not scored by this record.
Configures meal and rest break rules per state or jurisdiction, prompts required break attestation, and flags missed breaks for premium pay. differentiator
labor-break-compliance-by-state
Not scored by this record.
Supports predictive-scheduling ordinances by tracking advance-notice deadlines for published schedules and calculating predictability pay owed for employer-initiated changes.
labor-fair-workweek-support
Not scored by this record.
Enforces minor-labor restrictions (age-based maximum hours, prohibited time windows, school-day limits) at both scheduling and clock-in.
labor-minor-labor-rules
Not scored by this record.
Computes tip pooling and tip-outs automatically per shift from configurable rules (percentage of sales, hours worked, points, or role), rather than requiring a manual spreadsheet.
labor-tip-pooling-rules
Not scored by this record.
Retains a per-shift, per-employee record of tips received, amounts contributed to the pool, and amounts distributed from the pool, exportable for audit.
labor-tip-distribution-audit-trail
Not scored by this record.
Payroll export separates cash from charged qualified tips and carries a Treasury tipped-occupation code, supporting the W-2 Box 12 code TP and Box 14b reporting required for tax year 2026. differentiator
labor-qualified-tips-w2-reporting
Not scored by this record.
Vendor processes payroll itself as a first-party product (tax filing and direct deposit), as opposed to exporting to a third-party payroll provider only. differentiator
labor-native-payroll
Not scored by this record.
Exports timecards, wages, and tips in documented formats or via direct integration for at least two major payroll providers (e.g. Gusto, ADP, Paychex, QuickBooks).
labor-payroll-export-formats
Not scored by this record.
Employees can request shift swaps or claim open shifts in a self-service app, subject to a manager approval workflow that enforces overtime and role eligibility. differentiator
labor-shift-swap-workflow
Not scored by this record.
Provides digital new-hire onboarding that collects W-4 and I-9 documentation and supports E-Verify submission.
labor-digital-onboarding-i9
Not scored by this record.
Reports per-employee sales performance metrics (average check, items or category attachment rate, void and comp rate) by server or cashier. differentiator
labor-server-performance-metrics
Not scored by this record.
Inventory, purchasing & cost control
Supports multi-level recipe/BOM costing where a recipe can contain sub-recipes (prep items) and plate cost recalculates automatically when any component ingredient's cost changes.
inventory-recipe-bom-costing
Two documented recipe layers make this genuinely multi-level. Menu > Menu Items > Recipe sets "Cost from Recipe - The cost of the Menu Item is derived from the Recipe", with Ingredients / Qty / Unit / Cost and a Total whose "food cost percentage is displayed to the right of the Cost in parentheses and is based on Price 1". Beneath it, Inventory > Inventory Items > Recipe "is used to input the Recipe of Inventory Items" - an inventory item may itself be built from other inventory items, i.e. a prep item - and Inventory Items states "Recipe - Displays the Recipe for the Inventory. The Recipe Cost is calculated automatically from the cost of the Ingredients." That a recipe turns an item into a made good rather than a bought one is confirmed structurally: "The Stock to Purchase Conversion field is not displayed for Inventoried Items if a Recipe has been specified", likewise Purchase Unit. Recalculation is driven from real cost movement because "The Purchase Cost is automatically updated when Invoices are entered." Recipe Quick Set applies an ingredient or quantity across filtered menu items. Constraint noted: "An Ingredient may not be included in the Recipe more than once"; the manual documents these two nesting layers and does not state a maximum depth beyond them. https://www.focuspos.com/manual/Content/1f_Inventory/Recipe.htm · retrieved 2026-08-04 · not refetchable · site policy · graded B when read
Stores purchase unit, recipe unit, and count unit per item with explicit conversion factors, plus a yield/waste percentage applied to raw-to-usable conversion.
inventory-unit-conversion-yields
Each Inventory Item stores a Recipe Unit, a Stock Unit (the unit it is counted in) and a Purchase Unit, with two explicit conversion factors: "Recipe to Stock Conversion is the number of Recipe Units in one Stock Unit (Example: if the Unit used in the Recipe is ounces and the Inventoried Item is counted in pounds, then the Recipe to Stock Conversion value is 16)" and "Stock to Purchase Conversion is the quantity of Stock Units in one Purchase Unit". Shortfall: no yield or waste percentage field exists anywhere in the Inventory section - the word does not occur in the manual - so raw-to-usable loss cannot be applied to the conversion. https://www.focuspos.com/manual/Content/1f_Inventory/Inventory_Items.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
Produces a theoretical-vs-actual usage variance report per item for a defined count period, showing theoretical usage from POS sales times recipe, actual usage from counts plus receipts, and the variance in both units and currency. differentiator
inventory-theoretical-vs-actual
Not scored by this record.
Depletes ingredient on-hand quantities in near real time as orders are fired at the POS, including depletion driven by modifier selections, not only in an end-of-day batch. differentiator
inventory-realtime-depletion
Not scored by this record.
Automatically 86s (marks unavailable) menu items on the POS, online ordering, and connected third-party delivery menus when a component ingredient hits zero or a configured threshold. differentiator
inventory-86-auto-sync
Not scored by this record.
Supports full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts.
inventory-count-modes
Three documented modes. Full physical counts: Inventory > Enter Inventory holds "a list of all previously entered Inventories... each entry in the list contains the Date the Inventory was taken, the Inventory Worksheet used to record the inventory, and the Inventory Posted status", and "if the Inventory has been Posted it can not be deleted or edited without first being Reopened" - separate dated history rather than an overwritten snapshot. Subset counts: an Inventory Worksheet is built from selected Vendors, Subgroups or individual Items, and each count is entered against a chosen Worksheet. Recurring counts: Close Day > Daily Inventory takes "the daily beginning count, incremental stock count, and ending inventory count for predefined Inventory Items... used to compute the variance between the actual and theoretical usage of these Inventory Items". https://www.focuspos.com/manual/Content/1f_Inventory/Enter_Inventory.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
Provides a mobile/tablet counting app supporting barcode or QR scanning that continues to accept counts with no network connectivity and syncs on reconnect.
inventory-mobile-count-offline
Not scored by this record.
Ships pre-built electronic vendor catalog and order-transmission integrations with named broadline distributors (e.g. Sysco, US Foods, Performance Food Group) that send purchase orders and receive invoices electronically rather than by emailed PDF. differentiator
inventory-vendor-catalogs-edi
Not scored by this record.
Ingests supplier invoices from photo, PDF, or email and extracts line-item detail (item, quantity, unit, price) into the inventory ledger without manual line entry. differentiator
inventory-invoice-ocr
Not scored by this record.
Tracks per-item purchase price history across invoices and alerts when a received price exceeds the prior or contracted price by a configurable threshold. differentiator
inventory-price-change-alerts
Not scored by this record.
Maintains par levels per item per location and generates suggested purchase order quantities from on-hand versus par, with at least one mode driven by a sales forecast rather than a static par. differentiator
inventory-par-auto-suggest
Not scored by this record.
Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.
inventory-waste-logging
Not scored by this record.
Supports inter-location inventory transfers as a two-sided transaction crediting the sending location and debiting the receiving location, with an in-transit or approval state.
inventory-transfers
Not scored by this record.
Supports a commissary/central kitchen model where one location produces prep items and issues or sells them to other locations at a computed transfer cost.
inventory-commissary
Not scored by this record.
Captures lot/batch numbers at receiving and links them through production to sales or transfers, enabling a backward and forward recall trace.
inventory-lot-traceability
Not scored by this record.
Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.
inventory-shelf-life-expiry
Not scored by this record.
Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting.
inventory-bar-partial-bottle
Not scored by this record.
Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.
inventory-cogs-gl-export
Not scored by this record.
Inventory and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator
inventory-native-not-partner
Not scored by this record.
Reporting, BI & data access
Provides a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise.
reporting-realtime-dashboard
"Cloud Reporting and Management" listed as a product; refresh latency and off-premise mobile app not documented. https://www.focuspos.com/ · retrieved 2026-08-01
Generates a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types, and expected cash deposit in one document.
reporting-eod-closeout
The Daily Report reconciles the night in one document: Report Group Sales plus Order Type Charges to Subtotal, then less Inclusive Tax and Subtotal Discounts to Net Sales; per-tax collected, taxable and exempt amounts to Total Tax and Total Sales; Paid Outs, Paid Ins, Gift Cards, CC Tip Fee, Refunds and Retained Tips to Total Accountable; Gross Cash to Net Cash; then Cash Deposit and "Deposit Over/Short - Net Cash minus Cash & Check Deposit", each non-cash Payment type listed individually with units and amount, Total Payments, CC Total, Order Type Sales, and Discount and Paid Out detail. It slices into four named shifts, filters by Order Type, Station or Revenue Center, and exports comma-delimited or through an accounting interface. https://www.focuspos.com/manual/Content/1n_Reports/Sample_Daily_Report.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
Provides a product mix (PMIX) report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center.
reporting-pmix-modifier-level
The Item Count Daily Report "displays Menu Items sold and the associated cost information", sortable by Report Group, Sort Key or Item and secondarily by Units Sold, Sales or Profit, with Include Cost Information, Include Totals for Each Price, Include Zero Price Items, a Menu Item Filter, Start Time and End Time, Order Type and Station filters, top/bottom-N selection, and CSV or XML output. Shortfalls: the report setup exposes Order Type and Station filters but no Revenue Center filter (the Daily Report has one; this report does not); and modifier-level reporting is only implicit - modifiers are Menu Item records and an Include Zero Price Items option exists, but the manual documents no distinct modifier breakdown and no separate gross-versus-net sales columns. https://www.focuspos.com/manual/Content/1n_Reports/Item_Count_Daily_Report.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.
reporting-comps-voids-audit
Not scored by this record.
Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.
reporting-cash-over-short
Not scored by this record.
Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.
reporting-labor-productivity
Not scored by this record.
Reports per-server metrics including average check, items per check, attachment rate for named categories, and tips as a percentage of sales. differentiator
reporting-server-scorecards
Not scored by this record.
Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator
reporting-channel-profitability
Not scored by this record.
Provides a consolidated multi-location report with side-by-side location comparison and drill-down from group total to a single location and then to an individual transaction. differentiator
reporting-multiloc-drilldown
Not scored by this record.
Includes a self-service report builder letting a non-developer choose dimensions, measures, and filters and save the result, rather than only fixed canned reports. differentiator
reporting-custom-report-builder
Not scored by this record.
Supports scheduling any report for automatic recurring delivery by email or to a shared destination on a defined cadence and recipient list.
reporting-scheduled-delivery
Not scored by this record.
Offers automated recurring bulk export of transaction-level raw data to a customer-controlled destination (S3, SFTP, Snowflake, BigQuery, or equivalent), not just manual CSV download. differentiator
reporting-raw-warehouse-export
Not scored by this record.
Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator
reporting-public-api
Not scored by this record.
Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator
reporting-webhooks
Not scored by this record.
API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator
reporting-api-not-upcharged
Not scored by this record.
Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator
reporting-tier-paywall
Not scored by this record.
Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator
reporting-history-retention
Not scored by this record.
Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator
reporting-anomaly-alerts
Not scored by this record.
Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.
reporting-nl-query
Not scored by this record.
Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator
reporting-guest-cohorts
Not scored by this record.
Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator
reporting-sales-forecast
Not scored by this record.
Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.
reporting-tip-tax-compliance
Not scored by this record.
Multi-location, franchise & enterprise governance
Supports a named organizational hierarchy of at least three levels (e.g. enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations.
multi-location-org-hierarchy
Focus Enterprise adds a named layer between corporate and store: "The Restaurant Groups Window is used to establish and maintain up to 250 Restaurant Groups. Restaurant Groups allow stores to be grouped by state, regions or owners. A store can be included in multiple Groups." Reporting scopes to it - every Enterprise report Filters window offers a Report Filter of Groups, Restaurants or Current Restaurant - and so do permissions: Setup > Users assigns each Enterprise user a set of Rights and a Group. Groups are a flat multi-membership layer rather than a nested tree, so the documented depth is enterprise > group > restaurant and no deeper. https://www.focuspos.com/entmanual/scr/groups.htm · retrieved 2026-08-03
Corporate menu items expose per-field override rules so a location can change some attributes (e.g. price, availability) while corporate locks others (e.g. name, image, recipe), and locked fields are not editable at store level. differentiator
multi-location-local-override-policy
Not scored by this record.
Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.
multi-location-price-zones
Per-daypart pricing is native: each Menu Item carries Prices 1-6 with Price Times 1-6, and item-level Price Times override the Menu's. Per-location variation is handled by Focus Enterprise's Corporate/Local Control, which marks the Menu Item configuration file as Corporate while nominating Local Fields the store may override - "Price 1-6, Sub Price, Extra Price, No Price, Mod Price, Dbl% and Price Time 1-6... This is a global setting for all Menu Items." Shortfall: there is no price-zone or price-tier object. Differing prices across a group of stores are achieved by targeting separate corporate Downloads at Restaurant Groups or by per-store local override, and per-channel pricing is only an Order Type surcharge (Check %, Check $, Item %, Item $) added on top of one base price, not a distinct channel price book. https://www.focuspos.com/entmanual/scr/corpcontrol.htm · retrieved 2026-08-03
Menu, price, and promo changes can be scheduled to activate at a future date/time interpreted in each target location's own timezone, and can be rolled back after activation. differentiator
multi-location-scheduled-publish
Not scored by this record.
A new location can be provisioned by cloning a documented configuration template (menu, taxes, roles, printers, modifiers, tenders) rather than being configured from scratch, and the vendor publishes the expected time-to-open. differentiator
multi-location-new-store-template
Not scored by this record.
The permission model distinguishes a franchisor/corporate tenant from an independently-owned franchisee tenant, so corporate can see franchisee sales and enforce config while the franchisee owns its own employees, banking, and labor data. differentiator
multi-location-corp-vs-franchisee-roles
Not scored by this record.
Calculates franchise royalty, ad-fund, and marketing-fee amounts automatically from POS net sales on a defined schedule, with a configurable royalty basis (gross vs net of discounts/comps/third-party). differentiator
multi-location-royalty-calculation
Not scored by this record.
Supports automated ACH/debit collection of calculated royalties and fees from franchisee accounts, with a franchisee-visible statement of what was charged.
multi-location-royalty-collection
Not scored by this record.
Provides above-store reporting that aggregates sales, labor, discounts, voids, and item mix across any selected set of locations in one view, with store-vs-store ranking and variance flags.
multi-location-consolidated-reporting
Not scored by this record.
Item-level sales roll up across locations under a shared corporate item ID even when stores have renamed or locally priced the item. differentiator
multi-location-normalized-item-rollup
Not scored by this record.
Gift cards issued at one location are redeemable at any other location in the brand, with a reported outstanding-liability balance and inter-store settlement/redemption reconciliation between owners.
multi-location-cross-location-giftcard
Not scored by this record.
A single customer loyalty profile, balance, and stored order history is shared across all locations in the brand rather than being per-location.
multi-location-cross-location-loyalty
Not scored by this record.
A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. differentiator
multi-location-multi-brand
Not scored by this record.
Tax configuration is per-location with support for multiple simultaneous tax rates, jurisdiction-specific rules (e.g. prepared-food vs grocery, inclusive vs exclusive tax), and per-location tax exemptions.
multi-location-multi-tax-jurisdiction
Not scored by this record.
Supports locations operating in different currencies and languages within one enterprise account, with consolidated reporting converted to a reporting currency.
multi-location-multi-currency-locale
Not scored by this record.
Produces an immutable audit log of who changed which configuration object (price, tax, permission, discount) at which location and when, exportable or queryable by corporate. differentiator
multi-location-config-audit-log
Not scored by this record.
Supports SSO via SAML or OIDC against the customer's identity provider for back-office/above-store users, with SCIM or equivalent for automated deprovisioning. differentiator
multi-location-enterprise-sso
Not scored by this record.
Publishes a documented multi-location API (or data warehouse/BI export) that returns transaction-level data across all locations in one authenticated call, without per-location credentials. differentiator
multi-location-enterprise-api
Not scored by this record.
Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.
multi-location-central-labor-policy
Not scored by this record.
Hardware & physical footprint
The POS software runs on commodity off-the-shelf hardware (standard iPads, Android tablets, or PCs) that the operator can buy from a third party, rather than only on vendor-supplied proprietary terminals. differentiator
hardware-commodity-devices
Not scored by this record.
Vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs.
hardware-os-platforms
The platform is named but the requirements are not usably published. The client OS is Windows throughout - Locations > Stations identifies each of up to 150 terminals by Windows Computer Name - and iPad support is a thin client: "How to Setup iPad Solution with Focus RDP" has the iPad remote-desktop into a Windows PC running Focus, and is the one topic in the 546-topic manual that states minimum versions: "Required O/S includes: Windows 7 Pro, POSReady7" and "Required iOS is Version 7.X and higher" (plus "If running more than one iPad on a PC, Thinstuff or a like product is required"). Named shortfall: those minimums cover only the iPad-RDP scenario and name long-EOL versions (Windows 7 / POSReady7 / iOS 7); no topic in the manual and no page under /solutions/ states the supported Windows versions for the POS itself, and no device specs (CPU, RAM, storage, screen) are published anywhere - the Stations topics define name, printers and devices, not hardware requirements. https://www.focuspos.com/manual/Content/How_To_Section/How_to_Setup_iPad_Solution_with_Focus_RDP.htm · retrieved 2026-08-04 · not refetchable · site policy · graded B when read
Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.
hardware-handheld-purpose-built
Not scored by this record.
The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator
hardware-handheld-battery-swap
Not scored by this record.
Handhelds support cellular/LTE connectivity as a documented fallback when store Wi-Fi drops, either built into the device or via a vendor-supplied failover.
hardware-handheld-lte
Not scored by this record.
Terminals continue to take orders, print to kitchen, and record cash sales with the internet down, and the vendor documents explicitly which functions degrade (card auth, loyalty lookup, refunds).
hardware-offline-mode
Focus is an on-premise client/server system that does not need a WAN to sell: Miscellaneous > General > Restaurant offers an Internet Connection Type of "<None> - No Internet connection is present", the connection being used for SMTP mail and Close-Day FTP polling; stations run against a local file server and drive check, report, credit and remote printers on their own Com/LPT/local-IP ports. Degradation is documented only piecemeal: Close Day > Credit Cards > Offline warns that "a credit card may be approved Offline but be declined when turned back Online", the Batch Report has an Offline Declined Transaction section, and the myFocus Web Suite topic states "an active Internet connection is required at each location in order to use these products". Shortfall: no single published statement of which functions degrade when connectivity drops. https://www.focuspos.com/manual/Content/1r_Miscellaneous/Restaurant.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
Sells or supports a dedicated kitchen display system with bump-bar or touch input, station routing, and course/fire timing, as a first-party product rather than an integration-only dependency.
hardware-kds
Kitchen Display System listed as a first-party Focus product; bump-bar input, station routing rules and course/fire timing not documented. https://www.focuspos.com/ · retrieved 2026-08-01
Offers a self-order kiosk running the same menu and modifier engine as the POS, in both countertop and freestanding form factors, with integrated payment and accessibility (ADA) compliance documented. differentiator
hardware-kiosk
Not scored by this record.
Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, and speaker/headset integration, with a documented timer/speed-of-service measurement.
hardware-drive-thru
Not scored by this record.
Works with standard ESC/POS thermal receipt and kitchen printers from more than one manufacturer (e.g. Epson and Star), including LAN/Ethernet printers, rather than only vendor-branded printers.
hardware-printer-compatibility
Not scored by this record.
Supports the standard peripheral set — cash drawers (including multi-drawer per terminal), barcode scanners, scales for by-weight items, and customer-facing displays — with a published compatibility list.
hardware-peripherals
Not scored by this record.
Card entry happens on a PCI-listed PTS device using validated point-to-point encryption, so the POS application and tablet stay out of PCI scope; the vendor states the merchant's SAQ type.
hardware-p2pe-terminal
Not scored by this record.
Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. differentiator
hardware-tap-to-phone
Not scored by this record.
Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator
hardware-pricing-transparency
Not scored by this record.
Hardware can be purchased outright (owned) as an alternative to a mandatory lease or subscription-bundled rental, and the vendor states which. differentiator
hardware-ownership-vs-lease
Not scored by this record.
Vendor documentation confirms whether hardware purchased from the vendor remains usable with other software after cancellation, i.e. it is not software-locked or remotely bricked. differentiator
hardware-usable-after-churn
Not scored by this record.
Publishes a hardware warranty term and a replacement/advance-exchange SLA with a stated turnaround (e.g. next-business-day depot swap). differentiator
hardware-rma-sla
Not scored by this record.
Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.
hardware-byod
Not scored by this record.
Provides a remote device-management console showing each terminal, printer, and KDS as online/offline, with remote reboot, software-version visibility, and staged rollout of updates. differentiator
hardware-remote-device-management
Not scored by this record.
Integrates with specialty beverage hardware — self-pour tap walls, flow meters, or liquor pour spouts — such that pours post to a POS tab automatically.
hardware-selfpour-scales
Not scored by this record.
Supports inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call.
hardware-callerid-integration
Not scored by this record.
Integrations, API & extensibility
Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.
extensibility-public-api-docs
CLAIM: public, self-serve API reference readable without an agreement. VERDICT: yes. EVIDENCE: https://api.focuspos.com/ (Postman documenter "Focus POS API", publishedId TVmMgHYN, collection JSON at https://api.focuspos.com/api/collections/1972708/TVmMgHYN?segregateAuth=true&versionTag=latest, 16,725,928 bytes, 74 requests, served anonymously at HTTP 200; also at https://documenter.getpostman.com/view/1972708/TVmMgHYN). Its description: "The Focus POS API is a collection of RESTful endpoints for interacting with the Focus POS system." It documents "Production URL: https://focuslink.focuspos.com" and "Sandbox URL: https://dev.focuslink.focuspos.com", and folders Checks (9 requests), Sales, Labor, Orders (GET/POST/Validate), Gift Cards (4), Other Functions, Data (Configuration 16, Jobs 2, Employees 3, Labor 13, Sales 10, Focus Datafeed 1), Webhooks (4) and Customer Subscriptions (5), with request bodies and example responses, readable with no login. Corroborated by the anonymous Zendesk Help Center API at focuspos.zendesk.com (rendered at help.focusca.com; 338 articles held; publisher is Focus POS California, the CA/AZ/NV regional Focus operation at focusca.com, not Secret POS Systems Inc. itself - hence grade C; an href fixpoint over the bodies found 6 absent ids: 3 return 401 gated, 1 returns 404, so the KB is NOT a census): "FocusLink - Data Models" (https://help.focusca.com/hc/en-us/articles/360053530711) and "Getting access to your FOCUS Data" (360040815431). Credentials need an Integrator License ("Upon configuration of your Integrator License, you will be provided with a FocusLink API Key and API Secret") but the claim is about reading the docs. The earlier "no developer/API documentation found" note was written from focuspos.com only; api.focuspos.com is not linked from any of its 123 WP pages. Retrieved 2026-09-16. https://api.focuspos.com/ · retrieved 2026-09-16 adversarially verified
API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator
extensibility-api-access-cost
Not scored by this record.
A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator
extensibility-free-sandbox
Not scored by this record.
Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).
extensibility-oauth-partner-apps
CLAIM: third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions, not shared static API keys. VERDICT: no. EVIDENCE: https://api.focuspos.com/ (Postman documenter "Focus POS API", publishedId TVmMgHYN, collection JSON at https://api.focuspos.com/api/collections/1972708/TVmMgHYN?segregateAuth=true&versionTag=latest, 16,725,928 bytes, 74 requests, served anonymously at HTTP 200; also at https://documenter.getpostman.com/view/1972708/TVmMgHYN), Authentication section: "For integrators utilizing server to server communication, Basic Authentication is used. Upon configuration of your Integrator License, you will be provided with a FocusLink API Key and API Secret. These idenfity you as a licensed integrator across our ecosystem. For the purposes of Basic Authentication, your API Key will serve as your username and your API Secret will serve as your password." Access is granted by Focus, not the operator: "your License has certain endpoints accessible to it based upon the type of integration you are constructing. Integrators wishing to access endpoints that are not currently accessible to their License type should contact Focus Support". BOUND: the collection is the vendor's own published API manifest; its collection-level auth is type basic and all 97 auth objects across the 74 requests are type basic (0 of any other type). CONTROLS (tokenised, case-insensitive) over the 16,725,928-byte collection: oauth 0, refresh_token 0, client_id 0, scope 0, bearer 0, revok 0; over 338 KB articles + 356 focuspos.com WP pages/posts: oauth 0. POISON: "token" hits in the collection are receiptToken and card-payment token fields; "authoriz" hits are HTTP response headers. Corroboration from the anonymous Zendesk Help Center API at focuspos.zendesk.com (rendered at help.focusca.com; 338 articles held; publisher is Focus POS California, the CA/AZ/NV regional Focus operation at focusca.com, not Secret POS Systems Inc. itself - hence grade C; an href fixpoint over the bodies found 6 absent ids: 3 return 401 gated, 1 returns 404, so the KB is NOT a census): "FocusLink Integrators use Basic Authentication to authenticate to the FocusLink API" (https://help.focusca.com/hc/en-us/articles/360041196371), the deprecated per-store HMAC scheme (360036052272) and the FOCUS Data API AppID/SecurityKey HMAC bearer (360026931811) - all static integrator secrets. Caveat: KB 360040815431 says private custom endpoints can be built per integrator; they are unpublished. Retrieved 2026-09-16. https://api.focuspos.com/ · retrieved 2026-09-16 adversarially verified
The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.
extensibility-webhooks-push
CLAIM: real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than polling. VERDICT: partial. EVIDENCE: https://api.focuspos.com/ (Postman documenter "Focus POS API", publishedId TVmMgHYN, collection JSON at https://api.focuspos.com/api/collections/1972708/TVmMgHYN?segregateAuth=true&versionTag=latest, 16,725,928 bytes, 74 requests, served anonymously at HTTP 200; also at https://documenter.getpostman.com/view/1972708/TVmMgHYN), Webhooks folder: "The Focus API offers a variety of webhooks to hook into Focus events... All Venues with the Data feature enabled have access to webhooks... Focus Webhooks will make a POST call to the URL that you provide for each subscription." Signed: "Included in the HTTP Header of a Focus Webhook is the x-focussignature property. The x-focussignature is the body of the payload HMAC SHA256 encoded using your LicenseKey as the key." Events "as of Feb 12, 2021": "Check activity - Get a webhook when a check is created/edited/closed", Menu Item, Employee, Item Count Change, Out of Stock Record, "Closeday", Venue Configuration; V2 (Q2 2022): MenuItemRecordV2, OutOfStockRecordV2, CountStatusChangeV2, MenuItemIDChangeV2, MenuItemPriceListChangeV2, MenuItemRecordDeleteV2. Subscribe by POST (LicenseKey, WebhookGuid, WebhookUrl), list, DELETE to unsubscribe. SHORTFALL: the check event names only created/edited/closed - no void, refund or payment event is named (voids could only surface as a generic "edited"), the V2 set has no check/order event, and webhooks need the licensed Data feature. Tokenised controls over the collection: webhook 53, retry 0, callback 0. Retrieved 2026-09-16. https://api.focuspos.com/ · retrieved 2026-09-16 adversarially verified
Webhooks are cryptographically signed (e.g. HMAC) AND documented to retry with backoff, with a replayable event log for missed deliveries. differentiator
extensibility-webhook-reliability
Not scored by this record.
A public write API accepts externally originated orders into the POS as first-class tickets that fire to KDS/printers and land in reporting.
extensibility-order-injection-api
Not scored by this record.
Every core object the API can read (orders, menu, customers, employees, inventory) can also be written or updated via the same API. differentiator
extensibility-data-symmetry
Not scored by this record.
API rate limits are published as specific numeric quotas with documented throttling behavior and headers.
extensibility-published-rate-limits
Not scored by this record.
The vendor is a named DoorDash Preferred Integration Partner (DPIP) under the 2026 program requirements. differentiator
extensibility-doordash-preferred
Not scored by this record.
Direct, first-party certified integrations exist with DoorDash, Uber Eats, and Grubhub without requiring a paid middleware layer (Otter/Chowly/Deliverect/Checkmate). differentiator
extensibility-first-party-delivery-integrations
Not scored by this record.
The POS is a supported endpoint for at least two major aggregation middleware platforms (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate).
extensibility-middleware-compatibility
Not scored by this record.
Native, vendor-maintained connectors exist for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export.
extensibility-accounting-connectors
Not scored by this record.
Labor hours export natively to at least two named payroll providers (e.g. Gusto, ADP, Paychex, Paylocity) without manual re-keying.
extensibility-payroll-export
Not scored by this record.
Raw transaction-level data can be exported on a schedule to a customer-controlled destination (S3/SFTP/warehouse/Snowflake share), not only viewed in the vendor's reporting UI. differentiator
extensibility-bi-data-warehouse
Not scored by this record.
The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.
extensibility-app-marketplace
Not scored by this record.
Operators can define custom fields or run vendor-hosted custom logic/scripts against POS objects without a vendor engineering engagement.
extensibility-custom-fields-scripting
Not scored by this record.
The vendor supports a headless/embedded mode where a third-party UI (kiosk, web ordering, drive-thru) drives the POS transaction engine via API.
extensibility-headless-embedded
Not scored by this record.
The vendor publishes an API changelog and a stated deprecation/notice policy for breaking changes.
extensibility-api-versioning-deprecation
Not scored by this record.
A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator
extensibility-data-portability-exit
Not scored by this record.
Reliability, offline & operations
Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.
reliability-offline-order-entry
Order entry, routing and printing are all on-premise and LAN-local. Stations (up to 150) are Windows machines identified by Computer Name and Working Directory against a local Focus file server, each with its own Check, Report and Credit printers on "Com1 through Com32, Lpt1, Lpt2, and IP"; Printers > Remotes attaches every kitchen printer to a Station on a Com/LPT/IP port. Miscellaneous > General > Restaurant permits an Internet Connection Type of "<None> - No Internet connection is present", the connection being used only for SMTP and Close-Day FTP polling, and the myFocus topic isolates the cloud dependency to the subscription modules. Loss of the internet therefore does not interrupt on-terminal order entry, ticket routing or check printing. https://www.focuspos.com/manual/Content/1l_Locations/Stations1.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
Card payments can be accepted while offline via store-and-forward, not just cash-only fallback. differentiator
reliability-offline-card-auth
Not scored by this record.
The vendor publicly documents who bears the loss when a store-and-forward transaction declines after connectivity returns, and states any per-transaction or cumulative offline cap. differentiator
reliability-offline-decline-liability
Not scored by this record.
Multiple terminals continue to share a single check/table state over the local network while the internet is down (LAN-only degraded operation, not per-terminal islands). differentiator
reliability-lan-degraded-multi-terminal
Not scored by this record.
The vendor documents a local/on-premise transaction engine or edge server (not purely cloud-hosted request/response) for the ordering path. differentiator
reliability-local-transaction-engine
Not scored by this record.
Kitchen display and/or kitchen printer routing continues to function while offline.
reliability-offline-kds-printing
Kitchen printing is unaffected by an internet outage: each Remote Printer is bound to a Station and a local Com/LPT/IP port, with Printer Assignments, Chase Printing and Backup Printer routing all resolved on the LAN, and the base system runs with Internet Connection Type set to <None>. Shortfall: the KDS half is not established. Focus markets FocusKITCHEN as a "Cloud-Based Kitchen Display System" and publishes nothing about its behaviour without connectivity, while the Setup Manual treats a KDS only as a remote-printer port type (Logic Controls KDS, PartnerTech KVS) and never states what happens to either when the connection drops. https://www.focuspos.com/manual/Content/1h_Printers/Remotes.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
The system automatically fails over to a backup printer or KDS station when a configured kitchen printer is unreachable, and alerts staff.
reliability-printer-fallback
Printers > Remotes gives every remote printer a "Backup Printer - the Printer that will be used if the status of the original printer is offline", and the setup procedure makes selecting one a numbered step. The failure is surfaced rather than silent: the nFocus System Alerts window "displays the current date, business date, last batch information, offline status, printer errors and special pricing status" and names "the remote printer(s) that is currently offline. Note: This field is only displayed if a remote printer is offline". A Reroute command additionally lets staff redirect a remote printer by hand, and the Remotes window flags a printer as Rerouted. https://www.focuspos.com/manual/Content/1h_Printers/Remotes.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).
reliability-sync-conflict-handling
Not scored by this record.
The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).
reliability-offline-feature-matrix
Not scored by this record.
A public, per-component status page exists showing current and historical incident state without a login.
reliability-public-status-page
Not scored by this record.
A contractual uptime SLA with a stated percentage AND a service credit remedy is published or available in the standard agreement. differentiator
reliability-contractual-uptime-sla
Not scored by this record.
The vendor publishes written post-incident reports or root-cause summaries for major outages.
reliability-incident-postmortems
Not scored by this record.
24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.
reliability-247-live-support
Not scored by this record.
The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator
reliability-onsite-install
Not scored by this record.
A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.
reliability-hardware-replacement-sla
Not scored by this record.
Operators can trigger and retrieve their own data backup/restore, or the vendor publishes RPO/RTO figures for data recovery.
reliability-backup-restore
Not scored by this record.
The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.
reliability-pci-dss-4-attestation
Not scored by this record.
Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.
reliability-mfa-role-based-access
Not scored by this record.
A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.
reliability-self-serve-training
Not scored by this record.
Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. differentiator
reliability-failover-terminal-role
Not scored by this record.
Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.
reliability-cellular-backup
Not scored by this record.
Commercial, compliance & data ownership
Vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core POS software tier. differentiator
commercial-month-to-month-contract
Not scored by this record.
Vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. differentiator
commercial-no-early-termination-fee
Not scored by this record.
The auto-renewal term and the required cancellation notice window (e.g. 30/60/90 days) are stated in publicly accessible contract terms rather than only in a signed quote.
commercial-autorenew-terms-published
CLAIM: auto-renewal term and cancellation notice window stated in public contract terms. VERDICT: partial. EVIDENCE: the anonymous Zendesk Help Center API at focuspos.zendesk.com (rendered at help.focusca.com; 338 articles held; publisher is Focus POS California, the CA/AZ/NV regional Focus operation at focusca.com, not Secret POS Systems Inc. itself - hence grade C; an href fixpoint over the bodies found 6 absent ids: 3 return 401 gated, 1 returns 404, so the KB is NOT a census). "Equipment Return or Exchange Policies" (https://help.focusca.com/hc/en-us/articles/360004432411): "If you've licensed a recurring subscription service from us, such as FocusCloud, MyFocus or Focus RemoteAccess and would like to cancel your subscription, you'll just need to give us a 30-day notice... If you're subscription service is under contract, you may cancel the subscription, but you'll be responsible for paying the balance of your contract"; "we cannot cancel maintenance services in the middle of the maintenance contract term. You can request maintenance service contracts to be cancelled at the end of the contract". SHORTFALL: the notice window is published but no contract length and no auto-renewal term, and it is a regional operation's support policy rather than contract terms. The vendor's only public contract, https://www.focuspos.com/terms-and-conditions/ (Secret POS Systems, Inc. d/b/a Focus POS Systems, modified 2021-04-05), has no term or renewal clause - only "We may terminate this Agreement and close your account for any reason or no reason at any time upon notice to you". CONTROLS over all 356 focuspos.com WP pages+posts (X-WP-Total 123 + 233) and 338 KB articles, tokenised: renew* 0, notice-period phrasing 0, initial/minimum/subscription term 0 (2 hits: "any term of this Agreement" and foot traffic "month to month"). Retrieved 2026-09-16. https://help.focusca.com/hc/en-us/articles/360004432411-Equipment-Return-or-Exchange-Policies · retrieved 2026-09-16 adversarially verified
The POS software can be purchased and operated with a third-party payment processor of the operator's choice (no mandatory in-house processing lock). differentiator
commercial-processing-not-bundled
Not scored by this record.
Vendor publishes an interchange-plus (cost-plus) processing rate option with the markup stated as a specific bps + per-transaction figure, rather than only blended/flat card-present rates. differentiator
commercial-interchange-plus-published
Not scored by this record.
The processing agreement caps or prohibits unilateral vendor-initiated rate increases outside of pass-through interchange/network changes, or grants penalty-free exit on any increase. differentiator
commercial-rate-increase-clause
Not scored by this record.
Per-location and per-additional-terminal software pricing is published as specific dollar figures on the vendor's public site (not 'contact sales' only).
commercial-pricing-published
No pricing figures anywhere on focuspos.com; the site directs buyers to find a local dealer. https://www.focuspos.com/ · retrieved 2026-08-01
Individual modules (online ordering, KDS, loyalty, inventory, payroll, marketing) can be purchased à la carte and cancelled independently without repricing the base POS subscription. differentiator
commercial-module-unbundling
Not scored by this record.
All required terminals, KDS screens, and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental.
commercial-hardware-purchase-outright
Outright purchase is the traditional model and nothing forces a lease, but no price is published anywhere - the shortfall. Focus as a Subscription describes itself as offering the "same great features as Focus POS purchased through a traditional license" on "a monthly, subscription basis, lowering upfront costs and risk", so a perpetual-licence purchase is the alternative it is contrasted against, and no lease, rental or minimum term is described for either route. The hardware is commodity rather than proprietary: Locations > Stations identifies each of up to 150 terminals by its Windows Computer Name, Printers > Remotes attaches printers on "Com1 through Com32, Lpt1, Lpt2, and IP", and KDS support is third-party (Logic Controls KDS, PartnerTech KVS), so terminals, printers and screens are bought as ordinary Windows-compatible kit through the dealer. Shortfall: the published-price half of the claim fails outright. The Solutions index carries no hardware page and no pricing page, the subscription page gives no dollar figure and routes to a brochure or demo request, and every purchase path ends at a regional dealer quote - so no terminal, KDS screen or printer price is published by the vendor. https://www.focuspos.com/solutions/focus-as-a-subscription/ · retrieved 2026-08-04
Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator
commercial-hardware-not-locked
Not scored by this record.
One-time implementation, menu-build, onboarding, and training fees are published as specific amounts or explicitly stated as $0.
commercial-implementation-fee-published
Not scored by this record.
Operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee.
commercial-data-export-self-serve
Not scored by this record.
Guest/customer records, loyalty balances or point ledgers, and gift-card liability balances are exportable in machine-readable form by the operator. differentiator
commercial-export-customer-and-loyalty
Not scored by this record.
Contract or documentation specifies a post-termination data retrieval window (a defined number of days during which the operator can still export their data) rather than immediate cutoff. differentiator
commercial-post-termination-export-window
Not scored by this record.
Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator
commercial-data-ownership-clause
Not scored by this record.
The POS is source-available or open source with a documented self-hosting option (source published under an OSI or source-available license, not merely an open API).
commercial-source-available-selfhost
Not scored by this record.
Vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A / SAQ P2PE-HW, and names the applicable SAQ.
commercial-pci-p2pe-tokenization
Not scored by this record.
Vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — notably MFA for all access to the cardholder data environment including POS and back-office logins, and (for hosted ordering pages) payment-page script integrity monitoring per Req 6.4.3/11.6.1.
commercial-pci-dss-4-controls
Not scored by this record.
Vendor states it holds a current SOC 2 Type II (or ISO 27001) attestation and will provide the report under NDA via a trust center or on request.
commercial-soc2-attestation
Not scored by this record.
Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.
commercial-privacy-dsar-tooling
Not scored by this record.
Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator
commercial-wcag-kiosk-accessibility
Not scored by this record.
POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator
commercial-dual-pricing-compliant
Not scored by this record.
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 0 values — 0 upheld, 0 downgraded, 0 upgraded. It separately resolved 31 previously unknown values. 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.
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| order-capture-split-merge | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Order Entry > Packages documents Split ("create multiple seats on a check and move Menu Items between those seats. Also allows the employee to move the item portions from one seat to another"), Split Item, Unsplit Item, Cashier Split ("split a check with multiple seats into separate checks"), Cashier Combine, Position Split / Position Split All, Transfer Combine, Transfer Combine/No Seats, Transfer Seat and Transfer Items. Employees > Jobs > Rights adds "Checks - Split After Print", "Checks - Split First Seat After Print" and "Checks - Split Payments" (move payments between seats), so splitting and re-combining survive a printed check and a partial payment. Shortfall: every documented split is by seat, by item or by position - the manual documents no way to split a check by an arbitrary dollar amount or percentage, and no even N-way check split. source |
| order-capture-scheduled-orders | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Miscellaneous > General > Customer > Future Orders Options: "Print When Moved - the kitchen chit will print on the day the order is moved, at the specific time the order is due", "Move Orders at Close Day - the Future Orders will automatically move into the current business day at Close Day", and "Print Lead Time (minutes) - the number of minutes prior to the specified order time, that the kitchen chit will print" (zero prints at Close Day). A Future Orders package command enters the order and the check record stores future-order date, time and notes. Shortfall: Print Lead Time is a single system-wide setting on the Customer General window, not a per-channel lead time, and the alternative setting "Print When Entered" fires the chit on receipt. source |
| menu-pricing-nested-modifiers | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-yes | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Menu > Menu Items maintains "options and attributes for Menu Items and Modifiers" in one record type, and each record carries Modifier Canvas 1-8, each with its own Min ("If a Minimum of zero is entered, the selection of modifiers is optional"), Max and Free counts. Because modifiers are themselves Menu Item records they carry their own Modifier Canvases: Menu > Canvases notes "all modifiers that also have GoTo Modifiers should also be conversational", giving item > modifier > sub-modifier depth. Forced selection is Locations > Locations > Menus > "Goto Modifiers (Forced) - the Modifier Canvas will be displayed automatically if the Menu Item has a Max value greater than 0", configurable per Location. source |
| menu-pricing-modifier-price-by-parent-size | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Menu Items > Price Level: "Price Levels are only used when ordering Menu Items, not Modifiers. When a Price Level is selected the price of any associated Modifiers default to the same Price Level as the item it modifies unless Sub, Extra, or No is selected." Each modifier therefore carries Prices 1-6 and the parent item's selected size picks which one applies, with no duplication per size. Shortfall: the matrix has only the size axis. A modifier holds one set of six prices globally, so charging the same topping differently on two different parent items still requires duplicating the modifier record. source |
| menu-pricing-topping-quantity-tiers | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-yes | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Every Menu Item/modifier record carries separate Sub, Extra, No and Mod prices ("Extra: the price charged when using the Extra command"; Sub and No may be negative to decrease the sale) plus "Dbl% - the percentage of the Menu Item price to charge. For example, if a Vodka is $5.00 and the modifier Double is used with a Dbl% of 1 (100%), the total amount of the drink will be $10.00", i.e. a configurable multiplier rather than a second line. Miscellaneous > General > Prep Modifiers adds up to 10 further operator-named tier commands for modifier canvases, each mapped to a Price Number. source |
| payments-refund-void-controls | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-yes | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Order Entry > Voids defines up to 50 Void reasons and "the user must select a reason to justify the Void of the Menu Item or Payment". Job Rights gate each action separately (Check Items - Void, Payments - Void, Payments - Refunds, Discounts - Approve, Cashier - Open Drawer), and "Always Require Approval - requires the user to enter access code for FOH functions like voids, even when they are logged in". The Discounts/Voids/Audit Report carries "Approved By - the employee that approved the Void" and the same field for discounts and paid outs, with check number, date and time, plus Refunds, Variable Price Items and Drawer Opens sections; the Check Detail window separately retains time, employee and reason for every void, payment void and payment adjustment. The manual never uses the word immutable, but the attribution and the retained check-level record are documented. source |
| delivery-dispatch-board | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. A dedicated Dispatch Window exists. Order Entry > Order Types: "Delivery Pending - the Check is placed in the Delivery Pending state automatically. A check in the Delivery Pending state automatically appears on the Dispatch Window." Job Rights: "Customer - Dispatch - allows the user to dispatch checks to drivers. All checks that are Delivery Pending appear on the Dispatch Screen"; "Customer - Dispatch to Any Driver"; "Customer - Driver - drivers may be assigned checks with the Driver command as well as the Assign command on the Dispatch screen. Drivers are automatically prompted to close their open orders to cash when returning from route." Locations can display the Dispatch Window at login. Shortfall: the manual documents no driver availability state (in-store / on-run / returning), no elapsed-time-per-order column, and no multi-order run batching - checks are assigned to a driver one at a time. source |
| delivery-zone-pricing | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Customers > Zones establishes up to 100 Delivery Zones, each carrying its own Gratuity Fee and Order Type Fee as either a Flat dollar amount or a Percentage with a Rate, plus an Active Time range limiting when the fee applies; Order Entry > Order Types > "Delivery Zone Fee - if selected, the fees configured in Customers > Zones will apply to each customer tied to a particular Zone". Shortfall: the zone record holds a fee only - there is no per-zone order minimum and no per-zone quoted promise time. Zone is also a field stored on the customer record (Order Types > Customer > Zone) rather than derived automatically from a validated or geocoded address. source |
| digital-menu-single-source | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. The online menu originates from the POS menu record, but by an operator-run export rather than propagation: Menu > Menu Items > Tools > Online "will create an XML file in the \\focus\c\focus\onlineorders\menu folder to provide to the Online Order company", with a per-Location selection and a Goto-Modifiers-only option. Named shortfalls: the export is a manual per-Location action; "Only Menu 1 will export"; and Miscellaneous > General > Online Ordering requires the operator to configure a "Menu Item Exceptions" item used "if the Menu ID or price does not match the item ordered online" - positive documentation that the two menus can diverge. source |
| guest-loyalty-unified-profile | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. myFocus Loyalty "is a web-based loyalty program that centralizes loyalty members and plans into a single database. Members can accumulate points at one store and redeem them at another", and Manage Members holds one record per card number with name, address, phone, birth date and anniversary; store-side, the Customer Account Loyalty Detail window rolls up first order, last order, number of orders, cumulative sales and coupons issued/redeemed per customer. Shortfall: identity is the loyalty card number - the documentation describes no automatic phone or email match, no dedup or merge behaviour, and no attachment of first-party web ordering (which Focus routes through a third-party online-ordering processor) or kiosk traffic to the same member record. source |
| labor-granular-rbac | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-yes | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Employees > Jobs > Rights grants roughly 200 individually switchable Job Rights per Job, enumerated one discrete action at a time - Check Items - Void, Discounts - Approve, Payments - Refunds, Payments - Void, Payments - Force, Cashier - Open Drawer, Cashier - Open Any Drawer, Menu - Change Item Price, Checks - Split After Print, Report Security Code (1-9) and so on - rather than fixed cashier/manager/admin tiers. Rights extend across all of an employee's Jobs except where marked (NE), which "only considers the Job associated with the employee's clock in". Above store, Focus Enterprise keeps a parallel Rights window over Corporate User Groups and Setup > Users assigns each user both a set of Rights and a restaurant Group. source |
| labor-manager-override-audit | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-yes | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. The Discounts/Voids/Audit Report attributes each override to the individual approver - "Approved By: The employee that approved the Discount", "Approved By: The employee that approved the Void", and the same field on Paid Outs - alongside check number, date, time and reopen time, and can be sorted and totalled by Approved By. Further sections cover Refunds, Variable Price Items, Tax Exempt, Deletes, Kitchen Comments, Drawer Opens, Time Card Audits and Schedule Audits. Order Entry > Checks > Detail independently retains, per check, the employee and timestamp for each void, payment void and payment adjustment, so the trail is queryable after the fact. Tamper-evidence is not asserted by the vendor. source |
| inventory-unit-conversion-yields | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Each Inventory Item stores a Recipe Unit, a Stock Unit (the unit it is counted in) and a Purchase Unit, with two explicit conversion factors: "Recipe to Stock Conversion is the number of Recipe Units in one Stock Unit (Example: if the Unit used in the Recipe is ounces and the Inventoried Item is counted in pounds, then the Recipe to Stock Conversion value is 16)" and "Stock to Purchase Conversion is the quantity of Stock Units in one Purchase Unit". Shortfall: no yield or waste percentage field exists anywhere in the Inventory section - the word does not occur in the manual - so raw-to-usable loss cannot be applied to the conversion. source |
| inventory-count-modes | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-yes | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Three documented modes. Full physical counts: Inventory > Enter Inventory holds "a list of all previously entered Inventories... each entry in the list contains the Date the Inventory was taken, the Inventory Worksheet used to record the inventory, and the Inventory Posted status", and "if the Inventory has been Posted it can not be deleted or edited without first being Reopened" - separate dated history rather than an overwritten snapshot. Subset counts: an Inventory Worksheet is built from selected Vendors, Subgroups or individual Items, and each count is entered against a chosen Worksheet. Recurring counts: Close Day > Daily Inventory takes "the daily beginning count, incremental stock count, and ending inventory count for predefined Inventory Items... used to compute the variance between the actual and theoretical usage of these Inventory Items". source |
| reporting-eod-closeout | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-yes | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. The Daily Report reconciles the night in one document: Report Group Sales plus Order Type Charges to Subtotal, then less Inclusive Tax and Subtotal Discounts to Net Sales; per-tax collected, taxable and exempt amounts to Total Tax and Total Sales; Paid Outs, Paid Ins, Gift Cards, CC Tip Fee, Refunds and Retained Tips to Total Accountable; Gross Cash to Net Cash; then Cash Deposit and "Deposit Over/Short - Net Cash minus Cash & Check Deposit", each non-cash Payment type listed individually with units and amount, Total Payments, CC Total, Order Type Sales, and Discount and Paid Out detail. It slices into four named shifts, filters by Order Type, Station or Revenue Center, and exports comma-delimited or through an accounting interface. source |
| reporting-pmix-modifier-level | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. The Item Count Daily Report "displays Menu Items sold and the associated cost information", sortable by Report Group, Sort Key or Item and secondarily by Units Sold, Sales or Profit, with Include Cost Information, Include Totals for Each Price, Include Zero Price Items, a Menu Item Filter, Start Time and End Time, Order Type and Station filters, top/bottom-N selection, and CSV or XML output. Shortfalls: the report setup exposes Order Type and Station filters but no Revenue Center filter (the Daily Report has one; this report does not); and modifier-level reporting is only implicit - modifiers are Menu Item records and an Include Zero Price Items option exists, but the manual documents no distinct modifier breakdown and no separate gross-versus-net sales columns. source |
| multi-location-org-hierarchy | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-yes | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Focus Enterprise adds a named layer between corporate and store: "The Restaurant Groups Window is used to establish and maintain up to 250 Restaurant Groups. Restaurant Groups allow stores to be grouped by state, regions or owners. A store can be included in multiple Groups." Reporting scopes to it - every Enterprise report Filters window offers a Report Filter of Groups, Restaurants or Current Restaurant - and so do permissions: Setup > Users assigns each Enterprise user a set of Rights and a Group. Groups are a flat multi-membership layer rather than a nested tree, so the documented depth is enterprise > group > restaurant and no deeper. source |
| multi-location-central-menu-publish | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Corporate > Downloads authors once and publishes in a single action: set an Installation Date and Time, choose a Destination of Groups, Restaurants or All, add whole Configuration Files and/or individual Records (Menu Items, Canvases, Price Levels, Discounts and 25 further record types, optionally with images), Save, then Post. "Restaurants will receive the file the next time they poll" and hold it until the installation date and time. Which fields a store may then change is governed centrally by Setup > General > Control. Shortfall: the version history is thin - the Downloads window is a working list that can be edited and deleted, it records what was pushed and when but not by whom, and delivery is evidenced separately by a Polling Report listing restaurants that have not polled. source |
| multi-location-price-zones | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Per-daypart pricing is native: each Menu Item carries Prices 1-6 with Price Times 1-6, and item-level Price Times override the Menu's. Per-location variation is handled by Focus Enterprise's Corporate/Local Control, which marks the Menu Item configuration file as Corporate while nominating Local Fields the store may override - "Price 1-6, Sub Price, Extra Price, No Price, Mod Price, Dbl% and Price Time 1-6... This is a global setting for all Menu Items." Shortfall: there is no price-zone or price-tier object. Differing prices across a group of stores are achieved by targeting separate corporate Downloads at Restaurant Groups or by per-store local override, and per-channel pricing is only an Order Type surcharge (Check %, Check $, Item %, Item $) added on top of one base price, not a distinct channel price book. source |
| hardware-offline-mode | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Focus is an on-premise client/server system that does not need a WAN to sell: Miscellaneous > General > Restaurant offers an Internet Connection Type of "<None> - No Internet connection is present", the connection being used for SMTP mail and Close-Day FTP polling; stations run against a local file server and drive check, report, credit and remote printers on their own Com/LPT/local-IP ports. Degradation is documented only piecemeal: Close Day > Credit Cards > Offline warns that "a credit card may be approved Offline but be declined when turned back Online", the Batch Report has an Offline Declined Transaction section, and the myFocus Web Suite topic states "an active Internet connection is required at each location in order to use these products". Shortfall: no single published statement of which functions degrade when connectivity drops. source |
| reliability-offline-order-entry | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-yes | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Order entry, routing and printing are all on-premise and LAN-local. Stations (up to 150) are Windows machines identified by Computer Name and Working Directory against a local Focus file server, each with its own Check, Report and Credit printers on "Com1 through Com32, Lpt1, Lpt2, and IP"; Printers > Remotes attaches every kitchen printer to a Station on a Com/LPT/IP port. Miscellaneous > General > Restaurant permits an Internet Connection Type of "<None> - No Internet connection is present", the connection being used only for SMTP and Close-Day FTP polling, and the myFocus topic isolates the cloud dependency to the subscription modules. Loss of the internet therefore does not interrupt on-terminal order entry, ticket routing or check printing. source |
| reliability-offline-kds-printing | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Kitchen printing is unaffected by an internet outage: each Remote Printer is bound to a Station and a local Com/LPT/IP port, with Printer Assignments, Chase Printing and Backup Printer routing all resolved on the LAN, and the base system runs with Internet Connection Type set to <None>. Shortfall: the KDS half is not established. Focus markets FocusKITCHEN as a "Cloud-Based Kitchen Display System" and publishes nothing about its behaviour without connectivity, while the Setup Manual treats a KDS only as a remote-printer port type (Logic Controls KDS, PartnerTech KVS) and never states what happens to either when the connection drops. source |
| reliability-printer-fallback | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-yes | Focus does publish primary documentation: a 546-topic Focus Setup Manual at focuspos.com/manual (topic list enumerated from Data/Toc.js) and a Focus Enterprise manual at focuspos.com/entmanual. Neither was consulted by the migration pass. Printers > Remotes gives every remote printer a "Backup Printer - the Printer that will be used if the status of the original printer is offline", and the setup procedure makes selecting one a numbered step. The failure is surfaced rather than silent: the nFocus System Alerts window "displays the current date, business date, last batch information, offline status, printer errors and special pricing status" and names "the remote printer(s) that is currently offline. Note: This field is only displayed if a remote printer is offline". A Reroute command additionally lets staff redirect a remote printer by hand, and the Remotes window flags a printer as Rerouted. source |
| order-capture-offline-order-entry | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-yes | Read the Focus Setup Manual rather than the marketing site. The architecture is on-premise and will run with no internet whatsoever: Miscellaneous > General > Restaurant offers Internet Connection Type "<None> - No Internet connection is present" alongside Dial Up and Always Connected, and the connection serves only SMTP mail and Close-Day FTP polling. Order entry, modifier application and kitchen send are therefore LAN-local - Locations > Stations resolves each of up to 150 terminals by Windows Computer Name against a local Focus file server, and Printers > Remotes binds kitchen printers to a Station on Com1-32, Lpt1-2 or IP. Cash tender needs nothing external. The second half of the claim is also met: Focus publishes the offline scope for the parts that degrade. Close Day > Credit Cards > Offline states cards are "stored as a swiped transaction but not actually sent to the processor" and "may be approved 'Offline' but be declined when turned back 'Online'", and Order Entry > Packages exposes Offline, Offline Prompt (Credit / Loyalty) and Points Offline commands behind job rights. Residual caveat, consistent with the reliability-offline-kds-printing partial: FocusKITCHEN, marketed as a cloud KDS, publishes no offline behaviour. source |
| kitchen-station-routing | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-yes | The manual documents item-level routing configured by the operator, per location, in two screens. Printers > Groups creates "a maximum of 32 Printer Groups... logical groupings of similar Menu Items that are assigned to Remote Printers". Locations > Locations > Printer Assignments then binds group to destination - "Menu Items assigned to Printer Groups will be printed at the Remote Printers selected... Multiple Remote Printers may be selected for each Printer Group" - across three named assignment sets ("i.e., Normal, Busy, Hot Only") that may be time-activated, so "Printer Groups may be routed to different Remote Printers based on the time of day". The worked example routes the Hot Food group to the Hot Kitchen printer only. Destinations include KDS hardware: Printers > Remotes lists Port types "Logic Controls KDS - Interfaces with the Logic Controls KDS" and "PartnerTech KVS". Both screens sit in Focus Setup behind job rights ('Office - Locations', 'Printer Groups'), so no vendor involvement is needed. Scored yes on the item axis of a disjunctive claim; order-type and revenue-center routing are not offered - Remotes uses order type only to pick a Remote Check Format. source |
| inventory-recipe-bom-costing | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-yes | Focus documents two stacked recipe layers, which is what makes this multi-level rather than flat. At the top, Menu > Menu Items > Recipe carries "Cost from Recipe - The cost of the Menu Item is derived from the Recipe", with Ingredients, Qty, Unit, extended Cost and a Total that also prints food cost percentage against Price 1. Beneath it, Inventory > Inventory Items > Recipe "is used to input the Recipe of Inventory Items", so an inventory item can itself be assembled from other inventory items - a prep item - and Inventory Items states plainly "The Recipe Cost is calculated automatically from the cost of the Ingredients." The made-versus-bought distinction is enforced in the UI: "The Stock to Purchase Conversion field is not displayed for Inventoried Items if a Recipe has been specified", and the same for Purchase Unit. Cost movement is real, not hand-keyed: "The Purchase Cost is automatically updated when Invoices are entered", so an invoice repricing a base ingredient flows into the recipe cost. Recipe Quick Set pushes ingredient and quantity changes across a filtered menu-item set. The only documented limits are that an ingredient may not appear twice in one recipe and that the manual describes exactly these two nesting layers without stating a depth limit beyond them - neither defeats the claim. source |
| commercial-hardware-purchase-outright | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | Half the claim holds and half fails, and the failing half is verified rather than merely unfound. Holding: nothing forces a lease. Focus as a Subscription contrasts itself with "Focus POS purchased through a traditional license", framing monthly billing as the low-upfront-cost alternative to an outright purchase, and describes no lease, rental or minimum term on either route. The hardware is commodity, not proprietary - Locations > Stations identifies terminals by Windows Computer Name, Printers > Remotes runs printers on Com1-32, Lpt1-2 or IP, and KDS support is third-party Logic Controls KDS and PartnerTech KVS - so the kit is ordinary Windows-compatible equipment sourced through the dealer. Failing, and the named shortfall: no price is published. The Solutions index has neither a hardware page nor a pricing page, the subscription page gives no dollar figure and routes to a brochure or demo request, and the site channels every buyer to a regional dealer quote. The claim requires purchase "at a published price", and Focus publishes none for terminals, KDS screens or printers. source |
| payments-emv-nfc | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | The Setup Manual is silent - its credit-card chapters (Credit Card Direct with Vital/TSYS, SecureNet and Paymentech; NETePay setup; Close Day > Credit Cards) never mention EMV, chip, contactless or NFC, and the offline topic still describes cards "stored as a swiped transaction". What does exist is a pair of vendor press releases pairing Focus with processor-supplied semi-integrated hardware: Mercury Payment Systems (2016-01-29) - "EMV and end-to-end encryption (E2E), as well as NFC and tokenization capabilities needed for Apple Pay and other mobile wallets... Customers who utilize the VeriFone VX 805 and have upgraded to Focus POS version X" - and Sterling Payment Technologies (2016-06-07), again naming the VeriFone VX 805 and "payments from mobile wallets thanks to NFC and tokenization technologies"; a third (2015-11-24) adds Ingenico Telium Semi-Integrated support. Scored partial at grade D rather than yes: the claim asserts all first-party terminals accept EMV and NFC including Apple Pay and Google Pay, but Focus has no first-party terminal line - acceptance rides on the dealer-chosen processor and pad - the evidence is decade-old press-release marketing rather than documentation, and Google Pay is never named on the site. source |
| delivery-driver-roster | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | The driver module is native: Employees > Jobs > Rights carries "Customer - Driver - Allows the user to be the delivery driver. Drivers may be assigned checks with the 'Driver' command as well as the 'Assign' command on the Dispatch screen. Drivers are automatically prompted to close their open orders to cash when returning from route when logging in", alongside Customer - Dispatch, Customer - Dispatch to Any Driver and Customer - Print Check When Assigned; drivers, being employees, clock in and out at the Order Entry Time Clock like everyone else. That satisfies first-class drivers with clock-in/out and assignment, natively. The claim's other two elements are undocumented: no assignment-state model (in-store / on-run / returning) appears anywhere - the login-time return prompt is the only documented state transition - and no per-driver run history is reportable: the report catalogue extracted from the manual's TOC (546 topics) contains no driver or delivery report, and the Sample Employee Performance Report's columns are Employee, Number of Guests, Number of Checks, Per Person Average and drink counts, with nothing about deliveries. Consistent with the delivery-dispatch-board partial already on file. source |
| labor-clock-in-at-pos | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-yes | The Front of House section of the Setup Manual documents the punch happening on the POS terminal itself with exactly the credentials the claim names. Time Clock: "While in Focus Order Entry, select the Time Clock icon" and "Employees may clock in with an Access Code, Magnetic Card or with a Fingerprint Scanner". How to Clock In repeats the flow on "the Focus Order Entry Screen" - enter the Access Code "via the Number Pad, Magnetic Card or Fingerprint Scanner", select a Job ("only necessary if scheduling is not used"), touch Clock In - after which a Clock In Chit prints and, where job rights require it, a supervisor approves. Break handling (On Break / Off Break, Required Break Minimum minutes) lives on the same window. No separate time-clock device is described anywhere in the manual; the SMS Alerts topic even carries a Time Card Clock In alert type fed from these punches. source |
| hardware-os-platforms | unknown (grade F) - "No public documentation located during the 2026-08-01 research pass", a placeholder meaning the cell was never examined | resolve-to-partial | The OS naming half of the claim is met, the versions-and-specs half mostly is not. Windows is the client platform - Locations > Stations resolves up to 150 terminals by Windows Computer Name - and the sole tablet path is a thin client: How to Setup iPad Solution with Focus RDP has the iPad remote-desktop into a Windows PC running Focus and is the only topic among the manual's 546 that states minimums: "Required O/S includes: Windows 7 Pro, POSReady7", "Required iOS is Version 7.X and higher", "If running more than one iPad on a PC, Thinstuff or a like product is required". Named shortfall: those minimums apply only to the iPad-RDP scenario and cite long-EOL software (Windows 7 Pro, POSReady7, iOS 7); neither the Stations topics, End User Configuration, nor any page under /solutions/ states supported Windows versions for the POS terminals themselves, and no device specs (CPU, RAM, storage) are published anywhere on the site. Android and Linux are never mentioned. source |
Sources
Every URL this record cites. 42 in total.
- https://www.focuspos.com/
- 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.focuspos.com/entmanual/scr/groups.htm
- https://www.focuspos.com/entmanual/scr/howtocreateanewdownload.htm
- https://www.focuspos.com/entmanual/scr/corpcontrol.htm
- https://www.focuspos.com/solutions/kitchen-display-system-pos-focuskitchen/
- https://www.focuspos.com/solutions/restaurant-online-ordering/
- https://www.focuspos.com/partners/
- https://www.focuspos.com/myfocus/customer-loyalty-program/
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- https://www.focuspos.com/solutions/focus-as-a-subscription/
- https://www.focuspos.com/solutions/
- not refetchable
- not refetchable
- not refetchable
- not refetchable
- https://www.focuspos.com/focus-pos-partners-with-mercury-payment-systems-to-offer-emv-solution/
- https://www.focuspos.com/focus-pos-and-sterling-payment-technologies-team-up-for-emv-solution/
- not refetchable