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
- 36
- Unknown
- 278
- Not applicable
- 0
- Cells 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
order-capture-floor-plan-editor
Not scored by this record.
order-capture-seat-level
Not scored by this record.
order-capture-coursing-hold-fire
Not scored by this record.
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
order-capture-bar-tab-preauth differentiator
Not scored by this record.
order-capture-transfer-audit
Not scored by this record.
order-capture-native-handheld
Not scored by this record.
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
order-capture-qr-same-check differentiator
Not scored by this record.
order-capture-kiosk-first-party differentiator
Not scored by this record.
order-capture-drive-thru
Not scored by this record.
order-capture-drive-thru-timers
Not scored by this record.
order-capture-voice-ai differentiator
Not scored by this record.
order-capture-throttling differentiator
Not scored by this record.
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
order-capture-catering
Not scored by this record.
order-capture-order-ready-signal differentiator
Not scored by this record.
order-capture-void-comp-controls
Not scored by this record.
Menu, modifiers & pricing engine
menu-pricing-nested-modifiers
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. https://www.focuspos.com/manual/Content/1p_Menu/Menu_Items.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
menu-pricing-modifier-price-by-parent-size
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. https://www.focuspos.com/manual/Content/1p_Menu/Menu_Items.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
menu-pricing-fractional-placement differentiator
Not scored by this record.
menu-pricing-half-and-half-rule differentiator
Not scored by this record.
menu-pricing-topping-quantity-tiers
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. https://www.focuspos.com/manual/Content/1p_Menu/Menu_Items.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
menu-pricing-size-style-matrix differentiator
Not scored by this record.
menu-pricing-included-allowance differentiator
Not scored by this record.
menu-pricing-combos
Not scored by this record.
menu-pricing-upsell-prompts differentiator
Not scored by this record.
menu-pricing-86-propagation
Not scored by this record.
menu-pricing-countdown-auto-86 differentiator
Not scored by this record.
menu-pricing-dayparting
Not scored by this record.
menu-pricing-channel-price-books
Not scored by this record.
menu-pricing-dual-pricing differentiator
Not scored by this record.
menu-pricing-versioning-effective-dates differentiator
Not scored by this record.
menu-pricing-franchise-hierarchy differentiator
Not scored by this record.
menu-pricing-allergen-nutrition
Not scored by this record.
menu-pricing-recipe-linkage differentiator
Not scored by this record.
menu-pricing-3p-menu-push
Not scored by this record.
menu-pricing-dynamic-pricing
Not scored by this record.
Payments & money movement
payments-processor-choice differentiator
Not scored by this record.
payments-published-rates differentiator
Not scored by this record.
payments-dual-pricing differentiator
Not scored by this record.
payments-surcharge-guardrails differentiator
Not scored by this record.
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
payments-softpos-tap-to-pay differentiator
Not scored by this record.
payments-pay-at-table
Not scored by this record.
payments-qr-guest-pay differentiator
Not scored by this record.
payments-tip-adjust
Not scored by this record.
payments-tip-pooling differentiator
Not scored by this record.
payments-offline-store-and-forward differentiator
Not scored by this record.
payments-offline-decline-liability differentiator
Not scored by this record.
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
payments-house-accounts
Not scored by this record.
payments-split-tender
Not scored by this record.
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
payments-chargeback-tooling differentiator
Not scored by this record.
payments-card-on-file differentiator
Not scored by this record.
payments-payout-timing differentiator
Not scored by this record.
payments-multi-entity-routing differentiator
Not scored by this record.
payments-p2pe-pci4
Not scored by this record.
Kitchen & production
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
kitchen-expo-consolidation
Checked the FocusKITCHEN product page (focuspos.com/solutions/kitchen-display-system-pos-focuskitchen), whose entire feature list is "Bump individual items / Check recall / Dynamic item routing / Decrease paper waste / Bump to print / Prioritize rush orders / Bump to text" with no expo or consolidation screen mentioned, and the full 546-topic Focus Setup Manual, in which the only KDS references are the Printers > Remotes port options "Logic Controls KDS" and "PartnerTech KVS", the Prep Modifiers Add/Cut colour fields "used in KVS", and the Menu Items Cook Time field "primarily used with the kitchen video system". No topic describes an expo screen, nor a completion rule that waits for every contributing station to bump its items. Unresolved.
kitchen-course-firing differentiator
Not scored by this record.
kitchen-prep-time-pacing differentiator
Not scored by this record.
kitchen-order-throttling differentiator
Not scored by this record.
kitchen-channel-pause-propagation differentiator
Not scored by this record.
kitchen-order-ready-callback differentiator
Not scored by this record.
kitchen-bump-bar-hardware
The FocusKITCHEN page describes a cloud KDS and lists "Bump individual items" as a screen action; it names no input hardware and no supported models. The Focus Setup Manual (Printers > Remotes) documents KDS integration only as two port types on a remote printer - "Logic Controls KDS - Interfaces with the Logic Controls KDS" and "PartnerTech KVS" - and the Partners page lists Chef TAB and QSR Automations under KDS. Neither the manual nor any vendor page states whether physical bump bars or programmable keypads are supported, or which models. Unresolved.
kitchen-all-day-counts
Not scored by this record.
kitchen-sla-alerts
Not scored by this record.
kitchen-printer-fallback differentiator
Not scored by this record.
kitchen-offline-operation differentiator
Not scored by this record.
kitchen-item-build-screens differentiator
Not scored by this record.
kitchen-pizza-fractional-display differentiator
Not scored by this record.
kitchen-recall-refire
Not scored by this record.
kitchen-order-modification-alerts differentiator
Not scored by this record.
kitchen-guest-ready-notification differentiator
Not scored by this record.
kitchen-waste-logging
Not scored by this record.
kitchen-speed-of-service-reporting
Not scored by this record.
kitchen-prep-forecasting
Not scored by this record.
Delivery, dispatch & third-party channels
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
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
delivery-route-map differentiator
Not scored by this record.
delivery-driver-tracking differentiator
Not scored by this record.
delivery-zones-polygon differentiator
Not scored by this record.
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
delivery-address-validation
Not scored by this record.
delivery-driver-comp differentiator
Not scored by this record.
delivery-cash-reconcile
Not scored by this record.
delivery-daas-dispatch
Not scored by this record.
delivery-daas-fallback differentiator
Not scored by this record.
delivery-3p-direct-integration differentiator
Not scored by this record.
delivery-3p-injection
Not scored by this record.
delivery-menu-push
Not scored by this record.
delivery-86-sync
Not scored by this record.
delivery-store-pause
Not scored by this record.
delivery-3p-reconciliation differentiator
Not scored by this record.
delivery-injection-error-visibility differentiator
Not scored by this record.
delivery-tracking-page
Not scored by this record.
delivery-promise-time differentiator
Not scored by this record.
delivery-offline-behavior
Not scored by this record.
Digital ordering & guest-facing channels
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
digital-menu-single-source
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. https://www.focuspos.com/manual/Content/1p_Menu/Online.htm · retrieved 2026-08-03 · not refetchable · site policy · graded B when read
digital-native-app differentiator
Not scored by this record.
digital-account-saved-payment
The Focus POS Online Ordering page (focuspos.com/solutions/restaurant-online-ordering) lists five features - order from a mobile device, "Pay online with security and convenience", upsell, instantaneous menu and price updates, orders sent straight to the kitchen - and says nothing about guest accounts, saved addresses, stored payment methods or reorder. The Setup Manual's Miscellaneous > General > Online Ordering window covers only order-intake plumbing (processing station, receiving employee, credit-card and gift-card payment mapping, order-type mapping), and card storage would sit with the online-ordering provider rather than with Focus. No first-party statement either way. Unresolved.
digital-upsell-engine differentiator
Not scored by this record.
digital-scheduled-pacing
Not scored by this record.
digital-fulfillment-modes
Not scored by this record.
digital-qr-table
Not scored by this record.
digital-kiosk differentiator
Not scored by this record.
digital-group-ordering
Not scored by this record.
digital-catering-portal differentiator
Not scored by this record.
digital-voice-ai-phone differentiator
Not scored by this record.
digital-drivethru-ai
Not scored by this record.
digital-sms-ordering
Not scored by this record.
digital-google-order differentiator
Not scored by this record.
digital-apple-business-connect
Not scored by this record.
digital-loyalty-attach
Not scored by this record.
digital-subscriptions
Not scored by this record.
digital-promo-parity
Not scored by this record.
digital-guest-data-ownership differentiator
Not scored by this record.
digital-checkout-pci-sca
Not scored by this record.
digital-surcharge-transparency differentiator
Not scored by this record.
Guest data, loyalty & marketing
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
guest-loyalty-thirdparty-identity-attach differentiator
Not scored by this record.
guest-loyalty-accrual-models
A Customer Loyalty product is listed but no accrual model is described.
guest-loyalty-tiers differentiator
Not scored by this record.
guest-loyalty-offline-behavior differentiator
Not scored by this record.
guest-loyalty-offer-stacking-rules differentiator
Not scored by this record.
guest-loyalty-targeted-offers differentiator
Not scored by this record.
guest-loyalty-rfm-segmentation differentiator
Not scored by this record.
guest-loyalty-lifecycle-automation
Checked the myFocus Web Suite section of the manual (Loyalty MF, Manage Members, Awards, Loyalty Plans, Loyalty Reports) and the Customer Loyalty product page. Member records store Birth Date and Anniversary, and the myFocus Gift/Loyalty page lists "Coupons", "Marketing Lists", "Marketing Templates" and "Campaigns" among its setup options - but the manual gives Campaigns, Marketing Lists and Marketing Templates no topic page and no field documentation at all. The product page describes only broadcast mechanics ("Marketing list generation, Email blasts, Text message blasts"). Setup > Customers > Coupons > Smart Options triggers printed coupons on item-filter and check-frequency rules at the register, not on birthday, first visit or lapse. Cannot establish whether triggered always-on lifecycle campaigns ship. Unresolved.
guest-loyalty-native-email-sms differentiator
Not scored by this record.
guest-loyalty-consent-management
Not scored by this record.
guest-loyalty-10dlc-registration
Not scored by this record.
guest-loyalty-campaign-attribution differentiator
Not scored by this record.
guest-loyalty-data-export-portability differentiator
Not scored by this record.
guest-loyalty-cdp-event-api differentiator
Not scored by this record.
guest-loyalty-review-capture-routing differentiator
Not scored by this record.
guest-loyalty-referral-program
Not scored by this record.
guest-loyalty-wallet-pass differentiator
Not scored by this record.
guest-loyalty-privacy-rights-tooling
Not scored by this record.
guest-loyalty-redemption-fraud-controls
Not scored by this record.
guest-loyalty-ai-offer-recommendation differentiator
Not scored by this record.
guest-loyalty-stored-value-gift
Not scored by this record.
Labor & workforce
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
labor-photo-punch-verification differentiator
Not scored by this record.
labor-geofenced-mobile-punch
Not scored by this record.
labor-offline-time-punch differentiator
Not scored by this record.
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
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
labor-native-scheduling differentiator
Not scored by this record.
labor-demand-labor-forecast differentiator
Not scored by this record.
labor-realtime-labor-percent differentiator
Not scored by this record.
labor-overtime-prevention differentiator
Not scored by this record.
labor-break-compliance-by-state differentiator
Not scored by this record.
labor-fair-workweek-support
Not scored by this record.
labor-minor-labor-rules
Not scored by this record.
labor-tip-pooling-rules
Not scored by this record.
labor-tip-distribution-audit-trail
Not scored by this record.
labor-qualified-tips-w2-reporting differentiator
Not scored by this record.
labor-native-payroll differentiator
Not scored by this record.
labor-payroll-export-formats
Not scored by this record.
labor-shift-swap-workflow differentiator
Not scored by this record.
labor-digital-onboarding-i9
Not scored by this record.
labor-server-performance-metrics differentiator
Not scored by this record.
Inventory, purchasing & cost control
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
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
inventory-theoretical-vs-actual differentiator
Not scored by this record.
inventory-realtime-depletion differentiator
Not scored by this record.
inventory-86-auto-sync differentiator
Not scored by this record.
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
inventory-mobile-count-offline
Not scored by this record.
inventory-vendor-catalogs-edi differentiator
Not scored by this record.
inventory-invoice-ocr differentiator
Not scored by this record.
inventory-price-change-alerts differentiator
Not scored by this record.
inventory-par-auto-suggest differentiator
Not scored by this record.
inventory-waste-logging
Not scored by this record.
inventory-transfers
Not scored by this record.
inventory-commissary
Not scored by this record.
inventory-lot-traceability
Not scored by this record.
inventory-shelf-life-expiry
Not scored by this record.
inventory-bar-partial-bottle
Not scored by this record.
inventory-cogs-gl-export
Not scored by this record.
inventory-native-not-partner differentiator
Not scored by this record.
inventory-menu-margin-linkage differentiator
Not scored by this record.
Reporting, BI & data access
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
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
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
reporting-comps-voids-audit
Not scored by this record.
reporting-cash-over-short
Not scored by this record.
reporting-labor-productivity
Not scored by this record.
reporting-server-scorecards differentiator
Not scored by this record.
reporting-channel-profitability differentiator
Not scored by this record.
reporting-multiloc-drilldown differentiator
Not scored by this record.
reporting-custom-report-builder differentiator
Not scored by this record.
reporting-scheduled-delivery
Not scored by this record.
reporting-raw-warehouse-export differentiator
Not scored by this record.
reporting-public-api differentiator
Not scored by this record.
reporting-webhooks differentiator
Not scored by this record.
reporting-api-not-upcharged differentiator
Not scored by this record.
reporting-tier-paywall differentiator
Not scored by this record.
reporting-history-retention differentiator
Not scored by this record.
reporting-anomaly-alerts differentiator
Not scored by this record.
reporting-nl-query
Not scored by this record.
reporting-guest-cohorts differentiator
Not scored by this record.
reporting-sales-forecast differentiator
Not scored by this record.
reporting-tip-tax-compliance
Not scored by this record.
Multi-location, franchise & enterprise governance
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
multi-location-central-menu-publish
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. https://www.focuspos.com/entmanual/scr/howtocreateanewdownload.htm · retrieved 2026-08-03
multi-location-local-override-policy differentiator
Not scored by this 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
multi-location-scheduled-publish differentiator
Not scored by this record.
multi-location-new-store-template differentiator
Not scored by this record.
multi-location-corp-vs-franchisee-roles differentiator
Not scored by this record.
multi-location-royalty-calculation differentiator
Not scored by this record.
multi-location-royalty-collection
Not scored by this record.
multi-location-consolidated-reporting
Not scored by this record.
multi-location-normalized-item-rollup differentiator
Not scored by this record.
multi-location-cross-location-giftcard
Not scored by this record.
multi-location-cross-location-loyalty
Not scored by this record.
multi-location-multi-brand differentiator
Not scored by this record.
multi-location-multi-tax-jurisdiction
Not scored by this record.
multi-location-multi-currency-locale
Not scored by this record.
multi-location-config-audit-log differentiator
Not scored by this record.
multi-location-enterprise-sso differentiator
Not scored by this record.
multi-location-enterprise-api differentiator
Not scored by this record.
multi-location-central-labor-policy
Not scored by this record.
Hardware & physical footprint
hardware-commodity-devices differentiator
Not scored by this record.
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
hardware-handheld-purpose-built
Not scored by this record.
hardware-handheld-battery-swap differentiator
Not scored by this record.
hardware-handheld-lte
Not scored by this record.
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
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
hardware-kiosk differentiator
Not scored by this record.
hardware-drive-thru
Not scored by this record.
hardware-printer-compatibility
Not scored by this record.
hardware-peripherals
Not scored by this record.
hardware-p2pe-terminal
Not scored by this record.
hardware-tap-to-phone differentiator
Not scored by this record.
hardware-pricing-transparency differentiator
Not scored by this record.
hardware-ownership-vs-lease differentiator
Not scored by this record.
hardware-usable-after-churn differentiator
Not scored by this record.
hardware-rma-sla differentiator
Not scored by this record.
hardware-byod
Not scored by this record.
hardware-remote-device-management differentiator
Not scored by this record.
hardware-selfpour-scales
Not scored by this record.
hardware-callerid-integration
Not scored by this record.
Integrations, API & extensibility
extensibility-public-api-docs
No developer/API documentation found on the vendor site.
extensibility-api-access-cost differentiator
Not scored by this record.
extensibility-partner-revshare
Not scored by this record.
extensibility-free-sandbox differentiator
Not scored by this record.
extensibility-oauth-partner-apps
The Partners page asserts "Focus' open API platform offers integrations with popular hospitality and restaurant software" and lists roughly 40 named partners by category, but focuspos.com publishes no developer portal, no API reference and no authentication documentation - the site has no /developers, /api or /docs section, and the Focus Setup Manual's integration surfaces are file-based (an XML menu export and an order/response folder under C:\Focus\OnlineOrders, an accounting-interface export, and FTP polling with a stored user name and password). Nothing describes OAuth 2.0, scopes, operator-granted consent or per-app revocation. The open-API line is a grade-D marketing assertion with no documentation behind it. Unresolved.
extensibility-webhooks-push
Same search as the OAuth cell: no developer or API documentation exists on focuspos.com, so no event catalogue, delivery model or subscription mechanism can be read. Every integration mechanism the Focus Setup Manual does document is pull or file-drop - online orders are written into and read out of C:\Focus\OnlineOrders with an optional Response file, the menu leaves as an exported XML file, and Enterprise stores poll over FTP at Close Day - and the manual never mentions an outbound HTTP callback. That is suggestive but the manual covers the on-premise product, not the newer cloud modules (FocusKITCHEN, myFocus), so it is not positive evidence that no webhook exists. Unresolved.
extensibility-webhook-reliability differentiator
Not scored by this record.
extensibility-order-injection-api
Not scored by this record.
extensibility-menu-write-api differentiator
Not scored by this record.
extensibility-data-symmetry differentiator
Not scored by this record.
extensibility-published-rate-limits
Not scored by this record.
extensibility-doordash-preferred differentiator
Not scored by this record.
extensibility-first-party-delivery-integrations differentiator
Not scored by this record.
extensibility-middleware-compatibility
Not scored by this record.
extensibility-accounting-connectors
Not scored by this record.
extensibility-payroll-export
Not scored by this record.
extensibility-bi-data-warehouse differentiator
Not scored by this record.
extensibility-app-marketplace
Not scored by this record.
extensibility-custom-fields-scripting
Not scored by this record.
extensibility-headless-embedded
Not scored by this record.
extensibility-api-versioning-deprecation
Not scored by this record.
extensibility-data-portability-exit differentiator
Not scored by this record.
Reliability, offline & operations
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
reliability-offline-card-auth differentiator
Not scored by this record.
reliability-offline-decline-liability differentiator
Not scored by this record.
reliability-lan-degraded-multi-terminal differentiator
Not scored by this record.
reliability-local-transaction-engine differentiator
Not scored by this record.
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
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
reliability-sync-conflict-handling
Not scored by this record.
reliability-offline-feature-matrix
Not scored by this record.
reliability-public-status-page
Not scored by this record.
reliability-contractual-uptime-sla differentiator
Not scored by this record.
reliability-incident-postmortems
Not scored by this record.
reliability-247-live-support
Not scored by this record.
reliability-onsite-install differentiator
Not scored by this record.
reliability-menu-build-service differentiator
Not scored by this record.
reliability-hardware-replacement-sla
Not scored by this record.
reliability-backup-restore
Not scored by this record.
reliability-pci-dss-4-attestation
Not scored by this record.
reliability-mfa-role-based-access
Not scored by this record.
reliability-self-serve-training
Not scored by this record.
reliability-failover-terminal-role differentiator
Not scored by this record.
reliability-cellular-backup
Not scored by this record.
Commercial, compliance & data ownership
commercial-month-to-month-contract differentiator
Not scored by this record.
commercial-no-early-termination-fee differentiator
Not scored by this record.
commercial-autorenew-terms-published
No public contract terms located; dealer contracts are private.
commercial-processing-not-bundled differentiator
Not scored by this record.
commercial-interchange-plus-published differentiator
Not scored by this record.
commercial-rate-increase-clause differentiator
Not scored by this record.
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
commercial-module-unbundling differentiator
Not scored by this record.
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
commercial-hardware-not-locked differentiator
Not scored by this record.
commercial-implementation-fee-published
Not scored by this record.
commercial-data-export-self-serve
Not scored by this record.
commercial-export-customer-and-loyalty differentiator
Not scored by this record.
commercial-post-termination-export-window differentiator
Not scored by this record.
commercial-data-ownership-clause differentiator
Not scored by this record.
commercial-source-available-selfhost
Not scored by this record.
commercial-pci-p2pe-tokenization
Not scored by this record.
commercial-pci-dss-4-controls
Not scored by this record.
commercial-soc2-attestation
Not scored by this record.
commercial-privacy-dsar-tooling
Not scored by this record.
commercial-wcag-kiosk-accessibility differentiator
Not scored by this record.
commercial-dual-pricing-compliant differentiator
Not scored by this record.
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 31 values — 0 upheld, 0 downgraded, 0 upgraded. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
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