Vendors / Mainstream commercial restaurant POS
Owner.com
Was an ordering/marketing layer over third-party POS; it now also sells its own: Owner POS, marked New in the site nav, running a first-party Kitchen App on a loaned-or-purchased Lenovo tablet with an Owner Bluetooth printer, with stations, split tender, time clocking, cash drawer sessions and a product mix report. Still strongest on marketing, loyalty, web ordering and published subscription pricing; the POS is young and thin below the counter — no offline mode by the vendor's own statement, no inventory or labour module, no item-level station routing, and no documented card reader.
scored live legacy rubric
- Claims in scope
- 278
- Scored
- 45
- Assessed
- 43
- Unknown
- 235
- Not applicable
- 36
- Values challenged
- 24
unknown, never as no.Identity
- Owner
- Owner.com, Inc. — private, venture-backed. Independent as of this check.
- Who it is for
- Independent restaurants, heavily pizzerias, that want commission-free direct online ordering plus website, branded app and marketing automation — and, since 2026, an in-store POS from the same vendor. Owner still integrates with Toast, Clover and Otter for restaurants keeping their existing POS, so both shapes are supported.
- Site
- https://www.owner.com/
Pricing
transparency: unknown · unit: per location per month, plus optional 5% per-order restaurant fee · processor lock-in: unknown
- Software
- Two published month-to-month plans: Flexible $249/mo + 5% restaurant fee per order (for lower online volume), and Flat Rate $499/mo with no per-order restaurant fee (aimed at $5,000+/mo online sales). Custom rates for multi-location. No long-term contract and no cancellation fee. Separately a 5% order support fee is charged to the diner, not the restaurant. The widely repeated single '$499/mo' figure on review sites is incomplete — it omits the $249 tier.
Capabilities
Every claim is binary and checkable. Grades: A primary documentation · B product documentation · C pricing or feature page · D marketing claim · E third-party reporting · F inference with no source. A yes on a differentiator claim requires A or B.
Order capture & FOH workflow
Provides a graphical floor-plan editor where an operator can draw sections, place tables of varying shape/capacity, save multiple floor-plan layouts per location, and assign sections to servers.
order-capture-floor-plan-editor
Not scored by this record.
Order lines can be tagged to a seat number at entry, and the check can be split by seat afterward without re-keying items.
order-capture-seat-level
Not scored by this record.
Items can be assigned to courses and held, with a fire-next-course action available from a handheld or terminal that releases only that course to the kitchen.
order-capture-coursing-hold-fire
Not scored by this record.
Supports splitting a check by item, by seat, by even N-way, and by arbitrary dollar/percentage amount, and merging checks or tables back together, including after partial payment.
order-capture-split-merge
OVERTURNED. The standing rationale read 'No POS product; no in-store check handling', and the vendor now ships one: Owner POS, marked New in the site nav, with a Checkout screen in the Kitchen App. Split tender is documented on both sides of the transaction — at checkout, 'To add a tip or split the payment, tap Actions in the top right corner before completing the transaction', and afterwards, 'Split-payment receipts: for an order paid with more than one payment, you'll see a Payment picker. Choose All payments for one receipt covering everything, or pick a single payment (like Visa 4242) to hand that guest their own receipt.' Shortfall, and it is most of the claim: no article documents splitting by item, by seat or by an even N-way division, no dollar/percentage split is described, and nothing in the 141-article help centre describes merging checks or tables, or splitting after partial payment. Partial on split tender alone. https://help.owner.com/en/articles/16419487-print-receipts-and-tickets-on-your-owner-tablet-or-pos · retrieved 2026-09-08
Opens a bar tab against a card pre-authorization with a configurable auth amount, supports incremental re-auth as the tab grows, and auto-closes stale tabs at end of day. differentiator
order-capture-bar-tab-preauth
Not scored by this record.
An open check can be transferred between servers, tables, and devices, and the transfer is recorded in an audit log naming both employees.
order-capture-transfer-audit
Not scored by this record.
Ships a first-party handheld ordering app running natively on the handheld device (not a remote/mirrored desktop session) that can send to kitchen and take a card payment tableside.
order-capture-native-handheld
Not scored by this record.
With the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen, and tender cash, and the vendor publishes what does and does not work offline.
order-capture-offline-order-entry
UPHELD, reason corrected. 'Cloud ordering layer with no terminal software' is falsified — the Owner tablet is a first-party terminal running the Kitchen App, and the Kitchen App's Checkout screen creates orders. But the vendor answers this claim directly and in the negative on its own tablet page: 'Does the tablet work if my internet goes down? The tablet requires an internet connection to process orders and sync with your Owner account. We recommend keeping a reliable Wi-Fi connection in your kitchen.' Order creation is therefore documented as internet-dependent, and the vendor publishes no offline capability matrix of what does and does not work. Grade C — this is a marketing product page, but it is the vendor answering the offline question in its own FAQ. https://www.owner.com/kitchen-tablet · retrieved 2026-09-08
Guest QR at-table ordering writes items onto the same open check as server-entered items, rather than creating a separate order ticket. differentiator
order-capture-qr-same-check
Not scored by this record.
Offers a first-party self-order kiosk that renders the same menu and modifier tree as the POS with no separate menu build, and the vendor documents ADA/accessibility conformance for it. differentiator
order-capture-kiosk-first-party
Not scored by this record.
Supports drive-thru-specific order flow: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment.
order-capture-drive-thru
Not scored by this record.
Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.
order-capture-drive-thru-timers
Not scored by this record.
Vendor ships a first-party AI voice ordering agent for phone and/or drive-thru that injects orders directly as POS orders, or publishes a documented API partner program for third-party voice AI. differentiator
order-capture-voice-ai
Not scored by this record.
Supports order throttling: per-channel capacity limits per time slot with automatic quote-time extension when kitchen load exceeds a configured threshold. differentiator
order-capture-throttling
Not scored by this record.
Accepts future-dated/scheduled orders with a per-channel lead time and automatically injects them into the make queue at a computed fire time rather than on receipt.
order-capture-scheduled-orders
MERGE NOTE (2026-09-16): downgraded from a proposed yes/B to partial/B. SHORTFALL: the claim requires a per-CHANNEL lead time; Owner sets lead time per order type and location (catering 0-720h, 1-60 day window), and the mobile app takes ASAP orders only, so channel-level lead time is not documented. Deferred ticket firing ("at prep time") is documented. CLAIM: future-dated orders with per-channel lead time and automatic injection into the make queue at a computed fire time. VERDICT: yes/B. EVIDENCE: 'Manage your printing settings' (https://help.owner.com/en/articles/16419469-manage-your-printing-settings): "Print tickets for scheduled orders when placed : when on, scheduled and catering orders print a kitchen ticket as soon as they are within 7 days of prep, instead of only at prep time. Off by default." By default, then, the ticket fires at prep time, not on receipt. 'How do I turn off scheduled orders?' (https://help.owner.com/en/articles/11833449): "Under Scheduling, toggle Scheduled Orders off ... They'll only be able to place ASAP orders." Lead times by order type and channel: 'How far in advance can guests place a catering order?' (https://help.owner.com/en/articles/13047011): "minimum lead time (the soonest they can order, 0–720 hours) and your maximum order window (the farthest ahead they can schedule, 1–60 days) ... Catering request form: ... aren't restricted by these lead times ... Mobile app: ... The app only supports ASAP orders , not scheduled ones." The prep time the fire time is computed from: 'How can I change prep times for peak hours and large orders?' (https://help.owner.com/en/articles/11954845) documents Default Prep Time, day/time Prep Time Overrides and Large order extra time by items or dollars. Kitchen App phone orders: "Select when the order is needed: ASAP or a scheduled time" (https://help.owner.com/en/articles/13922131). CAVEAT: lead time is set per order type (catering vs standard) and per location. Channel differences are fixed (app = ASAP only), not a configurable per-channel lead time. BOUND: help.owner.com is an Intercom help centre. Census = 13 top collections + 33 sub-collections (46, all 200) and 142 articles (all 200). The href fixpoint over the bodies added one id: 11833154 "How do I adjust my menu's hours?", a 404 (unpublished, superseded by 11954934). Server-rendered site search for 24 terms surfaced zero ids outside the census. Wayback CDX was offline (503) this pass. Retrieved 2026-09-16. https://help.owner.com/en/articles/16419469-manage-your-printing-settings · retrieved 2026-09-16 adversarially verified
Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.
order-capture-catering
Not scored by this record.
Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator
order-capture-order-ready-signal
Not scored by this record.
Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.
order-capture-void-comp-controls
Not scored by this record.
Menu, modifiers & pricing engine
Payments & money movement
The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator
payments-processor-choice
Not scored by this record.
Vendor publishes card-processing pricing publicly (a specific flat rate or interchange-plus markup) rather than quote-only. differentiator
payments-published-rates
Not scored by this record.
Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator
payments-dual-pricing
Not scored by this record.
Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator
payments-surcharge-guardrails
Not scored by this record.
All first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay.
payments-emv-nfc
CLAIM: all first-party terminals accept EMV chip and NFC contactless. VERDICT: still unknown, though the card-present path is now identified. NEW SURFACE: Storefront bundle: pudgeeseatery.com is an Owner Astro storefront with static-content.owner.com assets. Its HTML sits behind a Cloudflare challenge and was fetched with headless Chromium; /_astro JS is served to curl. 92 JS files, 3.13 MB, closed over static imports and __vite__mapDeps, with 0 non-literal import(). All 78 hashed chunk names referenced are held. src.wIz1V6eZ.js ships Owner's full internal API route tree (3,313 router/endpoint nodes). Under the location router it has "getStripeConnectionToken ... /stripe-terminal-connection-token", and a sales router has "/hardware-orders/{orderId}". Owner POS therefore takes card-present payments through Stripe Terminal. Stripe Terminal readers accept EMV and contactless, but nothing public states which reader models Owner ships. The help census has no reader article: card reader(s) 0; EMV 0; chip 0 (its 1 hit is a UI "alert chip", poison); contactless 0; NFC 0; terminal(s) 0. 'Apple Pay' appears only in the branded mobile app's merchant terms (https://help.owner.com/en/articles/15326906). www.owner.com/pos, llms.txt and the 159-URL sitemap mention hardware only in "a few business days after receiving their hardware". Do not move this cell without a page that names the reader. BOUND: help.owner.com is an Intercom help centre. Census = 13 top collections + 33 sub-collections (46, all 200) and 142 articles (all 200). The href fixpoint over the bodies added one id: 11833154 "How do I adjust my menu's hours?", a 404 (unpublished, superseded by 11954934). Server-rendered site search for 24 terms surfaced zero ids outside the census. Wayback CDX was offline (503) this pass. Retrieved 2026-09-16. || 318th: NEW (318th): NEW SURFACE: app.owner.com (found via certspotter CT log for *.owner.com; crt.sh was 502) is Owner's merchant dashboard, an Expo/react-native-web SPA whose login-gated screens ship in an anonymous static bundle: 14 JS files, 20.9 MB (index-f609244e... 18.0 MB), every /_expo/static/js/web/*.js path referenced in the bundle held at 200. No login used. Card-present setup is Stripe Terminal ("Create terminal location", registerStripeReader POST /register-stripe-reader, "This location doesn't have a payment account yet. Complete payments setup to activate card readers."). The hardware-order flow ships only "Order Tablet" and "Receipt Printer" ("Free 2-day shipping. No charges for hardware."). Tokenised word-boundary case-insensitive controls over all 14 files: EMV 0; contactless 0; "tap to pay" 0; "Google Pay" 0; WisePOS 0; S700 0; "Reader M2" 0; BBPOS 0. Poison: chip 24 (all UI chip components, e.g. attachment-chip-remove); NFC 1 (Unicode normalize('NFC')); "Apple Pay" 5 (all the branded mobile app's Apple Pay merchant-identifier terms, not card-present). No reader model named, so still unknown. Retrieved 2026-09-16. || 322nd: NEW (322nd): NEW SURFACES: (a) public source maps probed on every live Owner SPA from the certspotter list: app.owner.com, dev-app.owner.com and embed-app.owner.com answer <bundle>.js.map, /asset-manifest.json, /.vite/manifest.json and a nonsense path with the same 2,228-byte HTML shell (soft-200 SPA catch-all, not a map); internal.owner.com, dev-internal.owner.com (Expo) and ai-phone-host.owner.com, photographer.owner.com (Vite) return 404 for every .map. No source map is public. (b) internal.owner.com, Owner's staff console (production), ships an anonymous Expo web bundle: 81 JS files, 17 MB, closed over every /_expo/static/js/web/*.js path referenced (all 200, 0 non-200). No login used. api.owner.com and dev-api.owner.com answer / with "Olympus ... is running in production/staging" but /swagger, /openapi.json, /docs, /redoc and a nonsense path all return a Cloudflare 403 challenge (a refusal, not an absence). Tokenised word-boundary case-insensitive controls over the 81 staff-console files and the current app.owner.com bundle (index-f8833182..., 18.0 MB): EMV 0/0; contactless 0/0; "tap to pay" 0/0; WisePOS 0/0; S700 0/0; "Reader M2" 0/0; BBPOS 0/0; "card reader(s)" 0. Poison: "reader(s)" 22 (ReadableStream readers in the bundled AI SDK, "screen reader" UI copy, and one Devices relation described as "Printers, POS stations, kiosks, and readers at this location" whose fields are only name/type/state/station, no model); chip 29 (UI chip components); NFC 1 (normalize('NFC')); swipe 47 (toast CSS). The staff console's hardware routes are createHardwareOrder, requestHardwareOrderApproval and confirmHardwareReceipt (Salesforce shipment), and the only hardware copy is "Confirm where to ship your Owner tablet and printer"; payments are typed 'card-present' but no reader model is named. Still unknown. Retrieved 2026-09-17. || 329th: NEW (329th): NEW SURFACES, none names a reader. (1) api.owner.com re-probed with curl + browser UA per Rule 1: /swagger, /openapi.json, /docs, /v3/api-docs all return a real 404 (414-419 bytes, same shape as the nonsense control /zzz-nonsense-329, 422 bytes); only /api-docs, /redoc, /graphql, /swagger/index.html and /swagger/v1/swagger.json give the Cloudflare 403 challenge. The 322nd's '403 everywhere' was partly a node-fetch artefact; Owner publishes no API spec. developer.owner.com, docs.owner.com, pos.owner.com, register.owner.com, kds.owner.com and terminal.owner.com do not resolve (certspotter, 63 names, re-run 2026-09-18). (2) app.owner.com was REBUILT today (shell 1,206 bytes; entry index-aa6c965cc16dd4371231e5f046f8ae83.js, was index-f609244e in the 318th): re-censused to a fixpoint, 3 rounds, 14 files, 20,948,162 bytes, every /_expo/static/js/web/*.js path referenced held at 200, 0 misses. It ships a TYPED ROUTE MANIFEST of Owner's whole Olympus backend: 2,353 {type:"endpoint",name,method,path,errors} nodes under 1,015 routers (saved as endpoints.txt/routers.txt). Card-present is Stripe Terminal and nothing else: registerStripeReader POST /register-stripe-reader, createTerminalLocation POST /create-terminal-location, getStripeConnectionToken GET /stripe-terminal-connection-token, UI string 'Stripe Terminal Location created'. The fee screen labels it 'Card-present processing fee' / 'POS processing fee' and ships STANDARD_CONNECT_RACK_RATES cardPresent {percentageBps:270, fixedAmount:5} vs cardNotPresent {290, 30}; TRANSACTION_PAYMENT_METHODS is the closed set ["card","cash","card-present","third-party","gift-card"]. Tokenised word-boundary case-insensitive controls over all 14 files: EMV 0, contactless 0, 'tap to pay' 0, tapToPay 0, 'Google Pay' 0, 'card reader' 0, cardReader 0, readerType 0, WisePOS 0, S700 0, BBPOS 0, 'Reader M2' 0, bbpos_wisepos_e 0, stripe_m2 0, verifone 0, P400 0, chipper 0, interac 0, 'insert card' 0. Poison found: chip 39 (UI chip components), NFC 1 (normalize('NFC')), swipe 11 (toast CSS), 'Apple Pay' 16 (all the branded consumer app's Apple Developer merchant-identifier terms), 'Stripe Reader' 1 (the registerStripeReader endpoint name), terminal 36 -- of which reportMe2TerminalStatus POST /by-slug/{slug}/me2-status is MARKETING-ENGINE-v2 campaign terminal state, not hardware (new poison). (3) www.owner.com was rebuilt today ('Last Published: Fri Sep 18 2026') and now sells a POS: /pos, /pos-integrations and /kitchen-tablet are real pages (130-198 KB; nonsense control /zzz-nope-329 returns a 19.8 KB 'Not Found'). Across 10 product pages plus /pricing: reader 0, EMV 0, contactless 0, NFC 0, 'tap to pay' 0, 'Apple Pay' 0, 'card reader' 0; hardware 1 ('a few business days after receiving their hardware'). (4) NEW: the Restaurant Participation Agreement (https://www.owner.com/restaurant-participation-agreement, 78 KB of stripped text) is Owner's merchant contract and ITEMISES the equipment Owner supplies -- Section 8 'Tablets' (Loaned Tablet, Purchased Tablet, Tablet Fee, pass-through warranty from 'third party equipment manufacturers') and Section 9 'Printers'. 'Setup and Equipment Fees' is defined as Setup + Tablet + Printer fees only. Controls over it: reader 0, EMV 0, contactless 0, terminal 0, 'card reader' 0. Owner's own contract therefore names NO first-party card reader as loaned or sold equipment, which is why this cell cannot be settled either way: card-present acceptance demonstrably exists via Stripe Terminal, but no Owner-published page names a reader model or asserts EMV/contactless/Apple Pay/Google Pay acceptance at the counter. (5) Help centre re-censused (see the labor-manager-override-audit note for the census): reader 0, EMV 0, contactless 0, NFC 0, 'tap to pay' 0, 'card reader' 0; chip 2 (both 'alert chip' UI), swipe 3 (Android/iOS touch gestures), 'Apple Pay' 13 in 5 articles -- ALL of them the branded consumer app's Apple Pay Merchant Agreement chore (https://help.owner.com/en/articles/15326906), i.e. card-not-present in the guest app. (6) App-store census: the iTunes publisher lookup for artistId 1649789741 returns exactly ONE iOS app (Owner.com, com.owner.restaurant, v1.39.34, 2026-08-13, 7 screenshots), an operator command-centre; its 7 screenshots were downloaded at 1200x0w and read as images -- menu/photo/86 screens, no checkout or reader. The Google Play publisher page for Owner.com lists 20 white-labelled per-restaurant consumer apps (com.owner.alvinospizza ... com.owner.theheightspizzeriaanddrafthouse) plus the operator app; there is NO POS/register app in either store, so the Owner tablet app is not publicly distributed. (Play 'emv' hits were base64 image-URL poison.) Retrieved 2026-09-18. adversarially verified
Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. differentiator
payments-softpos-tap-to-pay
Not scored by this record.
Vendor ships a handheld that takes EMV/NFC payment at the table, including tip prompt and check splitting, without carrying the card away.
payments-pay-at-table
Not scored by this record.
Guest can scan a QR code on the printed check or table tent to view and pay the check from their own phone, with the payment closing the check in the POS automatically. differentiator
payments-qr-guest-pay
Not scored by this record.
Supports both pre-auth-then-tip-adjust and on-device tip prompt flows, with a documented batch/adjust window and a manager screen for unadjusted tips.
payments-tip-adjust
Not scored by this record.
Configurable tip pooling and distribution rules (by hours worked, sales, role percentage, or points) that produce a per-employee tip allocation exportable to payroll. differentiator
payments-tip-pooling
Not scored by this record.
Card payments can be captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. differentiator
payments-offline-store-and-forward
Not scored by this record.
Vendor publicly documents who bears the loss when a stored offline transaction declines on reconnect, and surfaces a post-reconnect report of failed offline payments. differentiator
payments-offline-decline-liability
Not scored by this record.
First-party gift cards with real-time balance tracking, redeemable across every location in the group and through the online-ordering channel.
payments-gift-cards
First-party digital gift cards: 'Guests can buy digital gift cards directly from your website', the buyer receives a redemption code by email, and codes work 'online at any of your brand's locations, or in store via the Owner Tablet or Owner Dashboard' — so cross-location redemption and the online-ordering channel are both explicit. A companion article, 'How do I see all my gift cards and their balances?', documents a dashboard list showing recipient, current balance, purchase date and location, searchable by gift card code or recipient email, and the dashboard carries separate Gift Card Purchases and Gift Card Charges reports. Funds settle through Stripe to the Stripe account of the location where the card was purchased. Physical/plastic cards are not mentioned anywhere in the help centre. https://help.owner.com/en/articles/11832729-how-do-gift-cards-work-on-owner-com · retrieved 2026-08-04
House/on-account tabs with per-account credit limits, running balance, and periodic statement or invoice generation.
payments-house-accounts
Not scored by this record.
A single check can be settled with multiple tenders and split by seat, by item, by even shares, or by arbitrary amount, with no hard cap below eight ways.
payments-split-tender
Not scored by this record.
Voids, refunds, discounts, and no-sales require role-based authorization (manager PIN or approval) and write to an immutable audit log identifying the approver.
payments-refund-void-controls
CLAIM: voids, refunds, discounts and no-sales require role-based authorization and write an immutable audit log naming the approver. VERDICT: partial (authorization half shown; audit-log half not). NEW SURFACE: app.owner.com (found via certspotter CT log for *.owner.com; crt.sh was 502) is Owner's merchant dashboard, an Expo/react-native-web SPA whose login-gated screens ship in an anonymous static bundle: 14 JS files, 20.9 MB (index-f609244e... 18.0 MB), every /_expo/static/js/web/*.js path referenced in the bundle held at 200. No login used. EVIDENCE: the staff-roles module exports PERMISSION_CATEGORIES, category 'Orders and Checkout': "b('discount-orders','Discount orders','apply discounts to orders'),b('void-orders','Void orders','void orders'),b('refund-or-charge-orders','Refund or charge orders','issue refunds or apply additional charges')"; category 'Operations': "b('manage-cash-drawers','Manage cash drawers','access and manage cash drawer operations')" (b() renders "Allow staff to ..."). Jobs carry permissionGroupSlugs ("Select at least one permission"), staff get a 4-digit passcode (validatePasscodeSecurity rejects repeating/consecutive digits), and a TabletPermissionsScreen applies the same catalog to shared tablets (locations.location.putTabletPermissions). Corroborates the help centre's role-permission toggles (https://help.owner.com/en/articles/16400920). SHORTFALL: no approver-identifying void/refund audit log: the dashboard activity-log screens (the four settings routes are internalOnly, i.e. Owner staff only) are FeesActivityLog, HoursActivityLog, OrderingActivityLog, PrepTimeActivityLog and CouponActivityLogFlyout; no refundedBy/voidedBy/approvedBy field or 'manager override' string in the bundle; Voids/Refunds reports have no user column (https://help.owner.com/en/articles/16738749, /16738748). No separate per-transaction manager-PIN approval step is shown either; the gate is the role permission. Retrieved 2026-09-16. https://app.owner.com/_expo/static/js/web/index-f609244ee9bda68395d903bee3c33ede.js · retrieved 2026-09-16 adversarially verified
In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator
payments-chargeback-tooling
Not scored by this record.
Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator
payments-card-on-file
Not scored by this record.
Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator
payments-payout-timing
Not scored by this record.
Vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance / P2PE listing available to merchants on request.
payments-p2pe-pci4
Not scored by this record.
Kitchen & production
Items route to specific KDS stations by item, category, order type, or revenue center, with routing rules configurable per location without vendor involvement.
kitchen-station-routing
UPHELD, reason corrected. 'No KDS product' is falsified — Owner has stations ('Stations and tablets', and a per-station 'select your station, then click Printing') and its own Owner App page names a KDS. But the station routing surface, enumerated in full by the vendor, is by ORIGIN CHANNEL, not by menu structure: receipts are 'Print orders placed online', 'Print orders from this station', 'Print orders from other stations', with the note 'Each order matches only one of these three'; tickets are 'Print tickets' and 'Print tickets for scheduled orders when placed'. That is the whole enumerated toggle set. No control routes an item, a category, an order type or a revenue centre to a particular station or printer, so the specific mechanism this claim asks for is documented as absent rather than merely unmentioned. https://help.owner.com/en/articles/16419469-manage-your-printing-settings · retrieved 2026-09-08
An expo screen consolidates items from multiple prep stations into a single order view and only marks the order complete when every contributing station has bumped its items.
kitchen-expo-consolidation
UPHELD, reason corrected. 'No KDS product' is falsified; there is a first-party Kitchen tab on the Owner tablet, and the vendor documents its operations: 'In the side drawer, tap Kitchen', then 'The button is on the ticket card, and also inside the ticket once you open it', with the scoping note 'The Kitchen tab only prints kitchen tickets.' The claim needs multiple prep stations feeding one consolidated expo view whose completion waits on every contributing station bumping its items; the corpus documents no multi-station item split at all (routing is by order origin, not by item), and 'bump' occurs zero times across 141 help articles and 86 product pages. There is one kitchen view per station, not an expo consolidating several. https://help.owner.com/en/articles/16419487-print-receipts-and-tickets-on-your-owner-tablet-or-pos · retrieved 2026-09-08
Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator
kitchen-course-firing
Not scored by this record.
Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator
kitchen-prep-time-pacing
Not scored by this record.
Kitchen load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator
kitchen-order-throttling
Not scored by this record.
Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator
kitchen-channel-pause-propagation
Not scored by this record.
Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator
kitchen-order-ready-callback
Not scored by this record.
KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.
kitchen-bump-bar-hardware
UPHELD, reason corrected. 'No KDS or hardware product' is falsified — Owner ships kitchen hardware and identifies it precisely: 'What does the Owner kitchen tablet come with? The tablet comes pre-installed with the Owner kitchen app and connects to an Owner printer via Bluetooth. It is a Lenovo Yoga Tab 11 with a built-in stand.' That is a touchscreen tablet and a Bluetooth receipt printer, and the Restaurant Participation Agreement's equipment sections define exactly two categories of Owner-supplied hardware, Tablets (section 8) and Printers (section 9). No bump bar or programmable keypad appears in either the marketed hardware or the contract's equipment definitions, and 'bump bar' occurs zero times corpus-wide. Touch is the documented and only input. https://www.owner.com/kitchen-tablet · retrieved 2026-09-08
An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.
kitchen-all-day-counts
Not scored by this record.
Configurable target cook times per station or order type, with visual color escalation and/or audible alert when a ticket exceeds target.
kitchen-sla-alerts
Not scored by this record.
If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator
kitchen-printer-fallback
Not scored by this record.
KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator
kitchen-offline-operation
Not scored by this record.
Station screens can display item-level build/assembly detail (recipe steps, portioning, or full modifier breakout) rather than only the ticket line text. differentiator
kitchen-item-build-screens
Not scored by this record.
Sectioned/fractional topping placement (halves, quarters, specific sections) is rendered visually and unambiguously on the make-line screen or ticket. differentiator
kitchen-pizza-fractional-display
Not scored by this record.
A bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order.
kitchen-recall-refire
Not scored by this record.
Edits made in the POS to an order already displayed in the kitchen visually flag the added, changed, or removed items on the live ticket. differentiator
kitchen-order-modification-alerts
Not scored by this record.
Bumping an order ready triggers a guest-facing notification — SMS/text, app push, or an order-status display board — without a separate product purchase. differentiator
kitchen-guest-ready-notification
Not scored by this record.
Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.
kitchen-waste-logging
Not scored by this record.
Reports actual ticket and per-station times (average and percentile) sliced by daypart, station, and order channel, exportable to CSV or an API.
kitchen-speed-of-service-reporting
Not scored by this record.
Generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list.
kitchen-prep-forecasting
Not scored by this record.
Delivery, dispatch & third-party channels
Product includes a native in-house driver module: drivers are first-class entities with clock-in/out, assignment state (in-store / on-run / returning), and per-driver run history reportable from the POS itself (not via a third-party add-on).
delivery-driver-roster
UPHELD, reason sharpened. 'No native in-house driver module in the published catalog' understates what the catalogue does contain: in-house delivery is a supported fulfilment mode with its own zones ('Standard In-House delivery zones') and its own tip rule ('In-house delivery: 100% of the tip goes to the restaurant'). What is absent is the driver as an entity. The vendor draws that line itself: 'Delivery tracking only appears for orders fulfilled by Uber Eats or DoorDash. If you're using your own drivers, tracking won't show up for those orders.' No article gives a driver record, driver clock-in/out, an assignment state, or per-driver run history; 'roster' and 'dispatch' each occur zero times across the 227-document product corpus. In-house delivery is a zone setting, not a driver module. https://help.owner.com/en/articles/15485357-how-do-i-track-a-third-party-delivery-on-the-owner-app · retrieved 2026-09-08
Provides a dedicated dispatch/expo screen showing undispatched orders, driver availability, and elapsed time per order, with multi-order run batching (assigning 2+ orders to one driver as a single run).
delivery-dispatch-board
UPHELD, reason corrected. 'Absent from the published catalog' is now measured rather than asserted: the delivery surface is the Orders tab of the Owner app, and what it shows is one third-party courier's progress on one order — 'Assigning driver The order is paid, but no driver has accepted it yet', 'Driver has multiple stops The courier picked up an earlier delivery first and is on a batched route.' Note that the batching there is the marketplace's, performed on the courier's own runs and merely reported to the restaurant; the restaurant assigns nothing. There is no screen listing undispatched orders with driver availability and elapsed time, and no control for assigning two or more orders to one driver as a run. 'Dispatch' occurs zero times across 227 product documents. https://help.owner.com/en/articles/15485357-how-do-i-track-a-third-party-delivery-on-the-owner-app · retrieved 2026-09-08
Dispatch includes a live map view with geocoded stops and system-generated route sequencing (turn order optimization) for a multi-stop run, not just a static address list. differentiator
delivery-route-map
Not scored by this record.
Captures live driver GPS position from a driver-facing mobile app and surfaces it back to the dispatch screen. differentiator
delivery-driver-tracking
Not scored by this record.
Delivery areas can be defined as arbitrary map polygons or by drive-time isochrones, not solely as a radius or a ZIP/postcode list. differentiator
delivery-zones-polygon
Not scored by this record.
Each delivery zone carries its own independently configurable delivery fee, order minimum, and quoted promise time, applied automatically from the validated customer address.
delivery-zone-pricing
Zones exist and are address-driven: 'How do I add a delivery zone / radius / serviceable area?' documents radius zones ('a circle drawn from your restaurant location outward'), zip-code zones and custom-drawn polygon zones (the last set up by Owner Support), and 'How do I turn on delivery for my restaurant?' confirms guests can only order delivery inside an enabled zone. Per-zone money controls exist, but only as a subsidy: under Settings > Orders and delivery > Delivery each zone carries a 'Cost Covered' field ('the dollar amount you will contribute toward the delivery fee on each order in this zone') and a 'Min Spend' threshold ('the minimum order total a guest must reach for your delivery fee coverage to apply'). Shortfalls: the base delivery fee itself is set by the third-party courier, not configured per zone — 'Delivery fees vary by provider', e.g. Uber Eats $6.45 vs DoorDash $7.00 — and no per-zone order minimum or quoted promise time is documented for standard delivery. Only catering zones get restaurant-set fees ('Add delivery fee tiers based on order subtotal') and an optional minimum order requirement. https://help.owner.com/en/articles/14502948-how-do-i-cover-a-portion-of-the-delivery-fee-for-my-guests · retrieved 2026-08-04
Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.
delivery-address-validation
Not scored by this record.
Tracks per-delivery driver compensation inputs — mileage or distance driven per run, per-delivery flat reimbursement, and driver-retained tips — and exports them to payroll as separate reimbursement vs. wage lines. differentiator
delivery-driver-comp
Not scored by this record.
Provides a driver cash bank / settle-up flow that reconciles cash collected, orders assigned, and tips owed at end of shift, producing a per-driver over/short figure.
delivery-cash-reconcile
Not scored by this record.
Can hand a first-party order to an on-demand courier marketplace (DoorDash Drive, Uber Direct, Nash, Relay or equivalent) natively from the POS, with the courier quote and status returning into the order record.
delivery-daas-dispatch
Not scored by this record.
Supports hybrid dispatch: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. differentiator
delivery-daas-fallback
Not scored by this record.
Offers direct, first-party certified API integrations with DoorDash, Uber Eats, and Grubhub marketplaces (vendor-owned, not solely resold through Otter/Deliverect/Chowly/ItsaCheckmate middleware). differentiator
delivery-3p-direct-integration
Not scored by this record.
Third-party marketplace orders inject automatically into the POS as normal tickets that fire to KDS/printers without tablet re-keying or manual accept.
delivery-3p-injection
Not scored by this record.
Marking an item or modifier 86'd in the POS pushes item-level out-of-stock status to connected third-party channels in near real time, and restores it on availability (DoorDash requires item and item-option 86ing of new POS partners).
delivery-86-sync
Not scored by this record.
Store can be paused/deactivated on each connected third-party marketplace from inside the POS with a timed auto-reactivation, rather than only from each marketplace's own tablet or portal.
delivery-store-pause
Not scored by this record.
Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. differentiator
delivery-3p-reconciliation
Not scored by this record.
Vendor exposes integration health to the operator — failed/rejected order injections, connection status per channel, and alerts on failure — rather than failing silently. differentiator
delivery-injection-error-visibility
Not scored by this record.
Guests receive a branded order status / driver tracking page or SMS link on the restaurant's own domain for first-party delivery orders, driven by real order and driver state.
delivery-tracking-page
Not scored by this record.
Quoted delivery promise times adjust dynamically from current kitchen load, driver availability, and zone drive time, rather than a fixed per-store constant. differentiator
delivery-promise-time
Not scored by this record.
Vendor documents explicit offline behavior for delivery: whether cash delivery orders, driver assignment, and driver settlement continue during an internet outage.
delivery-offline-behavior
Not scored by this record.
Digital ordering & guest-facing channels
Vendor ships a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission.
digital-first-party-web
The core product: commission-free direct online ordering on an AI-built, SEO-optimized site on the restaurant's own branding, plus a branded mobile app. https://www.owner.com/pricing · retrieved 2026-08-01
Vendor offers a branded native iOS and Android ordering app (published under the restaurant's own brand in the App Store/Play Store), not only a mobile web page or a shared multi-restaurant marketplace app. differentiator
digital-native-app
Not scored by this record.
Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels.
digital-account-saved-payment
Branded app with loyalty and rewards implies guest accounts; saved tokenized payment methods and one-tap reorder are not explicitly documented. https://www.owner.com/pricing · retrieved 2026-08-01
Digital checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator
digital-upsell-engine
Not scored by this record.
Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.
digital-scheduled-pacing
Not scored by this record.
Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.
digital-fulfillment-modes
Not scored by this record.
Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.
digital-qr-table
Not scored by this record.
Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator
digital-kiosk
Not scored by this record.
Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.
digital-group-ordering
Not scored by this record.
Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator
digital-catering-portal
Not scored by this record.
Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator
digital-voice-ai-phone
Not scored by this record.
Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.
digital-drivethru-ai
Not scored by this record.
Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.
digital-sms-ordering
Not scored by this record.
Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator
digital-google-order
Not scored by this record.
Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.
digital-apple-business-connect
Not scored by this record.
Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.
digital-loyalty-attach
Not scored by this record.
Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.
digital-subscriptions
Not scored by this record.
Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.
digital-promo-parity
Not scored by this record.
Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator
digital-guest-data-ownership
Not scored by this record.
Digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.
digital-checkout-pci-sca
Not scored by this record.
Digital channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator
digital-surcharge-transparency
Not scored by this record.
Guest data, loyalty & marketing
Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.
guest-loyalty-unified-profile
Unified guest data across Owner's own web/app channels feeds its marketing; merge with in-store POS transactions and dedup rules are not documented. https://www.owner.com/pricing · retrieved 2026-08-01
Orders arriving from third-party marketplaces (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. differentiator
guest-loyalty-thirdparty-identity-attach
Not scored by this record.
Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.
guest-loyalty-accrual-models
MERGE NOTE (2026-09-16): changed from a proposed no/B to partial/B. Two accrual models exist (points per dollar, 10/$1, and a lifetime-points tier escalator to 11/12/13 per $1), which is the claim's spend-tier model; SHORTFALL: neither is operator configuration ("This rate is set automatically and can't be adjusted") and visit/punch accrual is absent (punch 0, stamp 0 over the 142-article help centre). CLAIM: at least two of points-per-dollar, visit/punch-count and spend-tier accrual as configuration. VERDICT: no/B. This rests on an affirmative vendor statement, not on an absence. EVIDENCE: 'How does the Owner Loyalty Program work?' (https://help.owner.com/en/articles/11833522-how-does-the-owner-loyalty-program-work), section 'How guests earn points': "New guests get 100 bonus points when they join your VIP mailing list or place their first order. After that, guests earn 10 points for every $1 spent , rising to 11, 12, and 13 points per $1 once their lifetime points pass 1,000, 4,000, and 10,000. This rate is set automatically and can't be adjusted." Also "Catering orders don't earn points", "Points expire 6 months after they're earned" and "Owner's loyalty program doesn't sync with external systems". The only operator-configurable loyalty setting documented is the per-item redemption value ("Points to Redeem"). So there is one accrual model, points per dollar with an automatic lifetime escalator, and it cannot be configured. CONTROLS over the 142-article census (tokenised, word-boundary, case-insensitive): punch* 0; stamp(s) 0; visit(s) 1, poison ("If you visit your own site often", an SEO article); tier(s) 1, poison (catering "delivery fee tiers"); "points per" 1 (this article). BOUND: help.owner.com is an Intercom help centre. Census = 13 top collections + 33 sub-collections (46, all 200) and 142 articles (all 200). The href fixpoint over the bodies added one id: 11833154 "How do I adjust my menu's hours?", a 404 (unpublished, superseded by 11954934). Server-rendered site search for 24 terms surfaced zero ids outside the census. Wayback CDX was offline (503) this pass. Retrieved 2026-09-16. https://help.owner.com/en/articles/11833522-how-does-the-owner-loyalty-program-work · retrieved 2026-09-16 adversarially verified
Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator
guest-loyalty-tiers
Not scored by this record.
Documents explicitly what loyalty lookup, accrual, and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). differentiator
guest-loyalty-offline-behavior
Not scored by this record.
Offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. differentiator
guest-loyalty-offer-stacking-rules
Not scored by this record.
Offers can be issued to a dynamically defined audience (rules over recency, frequency, spend, or items purchased) rather than only broadcast to the whole list. differentiator
guest-loyalty-targeted-offers
Not scored by this record.
Automatically computes recency/frequency/monetary or equivalent lifecycle segments (new, regular, at-risk, lapsed, VIP) without the operator building the queries. differentiator
guest-loyalty-rfm-segmentation
Not scored by this record.
Ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns rather than one-off manual sends.
guest-loyalty-lifecycle-automation
AI-powered email and SMS marketing automation is included in both plans; specific always-on birthday/first-visit/win-back triggers are not enumerated publicly. https://www.owner.com/pricing · retrieved 2026-08-01
Sends both email and SMS campaigns natively from the platform, not solely by handing the list to a third-party ESP. differentiator
guest-loyalty-native-email-sms
Not scored by this record.
Captures per-channel marketing consent with timestamp and source of consent, and honors revocation received by any reasonable means (not just the STOP keyword) across all channels.
guest-loyalty-consent-management
Not scored by this record.
Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.
guest-loyalty-10dlc-registration
Not scored by this record.
Reports redemption and incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. differentiator
guest-loyalty-campaign-attribution
Not scored by this record.
Provides self-serve export of the full guest list and transaction history, including contact PII, via CSV or API, without a vendor fee or support ticket. differentiator
guest-loyalty-data-export-portability
Not scored by this record.
Triggers post-transaction feedback requests and routes responses by score, sending low scores to private service recovery and high scores toward public review sites. differentiator
guest-loyalty-review-capture-routing
Not scored by this record.
Includes a native referral mechanic with per-guest codes or links, attribution of the referred guest's first order, and two-sided rewards.
guest-loyalty-referral-program
Not scored by this record.
Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance, as an alternative to requiring a branded app download. differentiator
guest-loyalty-wallet-pass
Not scored by this record.
Provides admin tooling to fulfill guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records.
guest-loyalty-privacy-rights-tooling
Not scored by this record.
Enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log.
guest-loyalty-redemption-fraud-controls
Not scored by this record.
Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing (claim-level; verify it is a shipped product feature, not a roadmap statement). differentiator
guest-loyalty-ai-offer-recommendation
Not scored by this record.
Offers native stored-value/gift card balances tied to the same guest profile and redeemable across all locations of the brand.
guest-loyalty-stored-value-gift
Not scored by this record.
Labor & workforce
Employees clock in and out at the POS terminal using a PIN, badge, or card, with no separate time-clock hardware required.
labor-clock-in-at-pos
OVERTURNED. 'No POS terminal and no labor module' is wrong on both halves. Owner ships a POS, and its printing settings expose a time-clocking feature keyed to the station: 'Time slips (if you use time clocking)' / 'Print time slips on clock in / clock out : prints a time slip automatically each time an employee clocks in and out.' Employees therefore clock in and out at the Owner tablet or POS itself, with no separate time-clock hardware, which is the substance of this claim. Shortfall: the credential is not documented — no article states whether clock-in uses a PIN, a badge or a card — and no timesheet, labour report or approval flow appears in the nine-section Reports catalogue. Partial on the clock-in mechanism alone. https://help.owner.com/en/articles/16419469-manage-your-printing-settings · retrieved 2026-09-08
Captures a photo at punch (or performs facial verification) attached to the timecard entry, with a photo-only mode available that stores no biometric template. differentiator
labor-photo-punch-verification
Not scored by this record.
Records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, with the behavior documented. differentiator
labor-offline-time-punch
Not scored by this record.
Permissions are grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers.
labor-granular-rbac
CLAIM: permissions grantable per discrete action, per role and per location. VERDICT: partial/B. EVIDENCE: roles carry individually toggled, named permissions. 'How do I change my sales tax rate?' (https://help.owner.com/en/articles/16400920-how-do-i-change-my-sales-tax-rate): "You'll need a role with the Manage store settings permission turned on." 'Manage a guest's marketing subscription' (https://help.owner.com/en/articles/16414492): "You'll need a role with the Manage customers permission turned on." 'How do I turn a menu on or off?' (https://help.owner.com/en/articles/15139944): "your account may not have permission to edit menu availability. Ask the account owner or an admin on your team to update your access." Roles are therefore not fixed tiers; permissions are granted per capability. SUPPORTING, WEAKER (bundle): Storefront bundle: pudgeeseatery.com is an Owner Astro storefront with static-content.owner.com assets. Its HTML sits behind a Cloudflare challenge and was fetched with headless Chromium; /_astro JS is served to curl. 92 JS files, 3.13 MB, closed over static imports and __vite__mapDeps, with 0 non-literal import(). All 78 hashed chunk names referenced are held. Its internal route tree has auth getRolesAndScopes, location getTabletPermissions/putTabletPermissions, brand admins upsertBrandAdmin, and staff createStaffMember/updateStaffMember with the error "insufficient-location-access" (suggesting location-scoped grants), plus staff PIN endpoints. SHORTFALL: there is no public permission list. Void, comp, discount, refund, drawer-open and report-access permissions are not named, and per-location grants are inferred only from an error code. CONTROLS over the help census: 'permission' occurs in 5 sentences across 3 articles; one is marketing consent (poison). 'role' also matches the careers button "New Role" (poison). BOUND: help.owner.com is an Intercom help centre. Census = 13 top collections + 33 sub-collections (46, all 200) and 142 articles (all 200). The href fixpoint over the bodies added one id: 11833154 "How do I adjust my menu's hours?", a 404 (unpublished, superseded by 11954934). Server-rendered site search for 24 terms surfaced zero ids outside the census. Wayback CDX was offline (503) this pass. Retrieved 2026-09-16. https://help.owner.com/en/articles/16400920-how-do-i-change-my-sales-tax-rate · retrieved 2026-09-16 adversarially verified
Manager overrides and approvals are attributed to the individual approver and written to an immutable audit trail queryable after the fact.
labor-manager-override-audit
CLAIM: manager overrides are attributed to the individual approver in an immutable, queryable audit trail. VERDICT: still unknown. EVIDENCE: the help census (142 articles) has no audit or activity-log article (audit* 0, "activity log" 0). The Voids report records "Reason" with values like "Cancelled by operator", and the Refunds report records "Comment"; neither has a user or approver column (https://help.owner.com/en/articles/16738749, https://help.owner.com/en/articles/16738748). NEW SURFACE: the storefront bundle's internal API route tree (Storefront bundle: pudgeeseatery.com is an Owner Astro storefront with static-content.owner.com assets. Its HTML sits behind a Cloudflare challenge and was fetched with headless Chromium; /_astro JS is served to curl. 92 JS files, 3.13 MB, closed over static imports and __vite__mapDeps, with 0 non-literal import(). All 78 hashed chunk names referenced are held.) contains "router activity ... getActivityLogs GET /logs" at brand, location and ownership-group scope, plus getGlobalActivityLogs, staff PIN endpoints (getPin, setPin, resetPin) and a reporting router with sales-summary-by-staff. An activity-log API therefore exists, but nothing public says what it records, whether overrides are attributed to an approver, or whether it is immutable. BOUND: help.owner.com is an Intercom help centre. Census = 13 top collections + 33 sub-collections (46, all 200) and 142 articles (all 200). The href fixpoint over the bodies added one id: 11833154 "How do I adjust my menu's hours?", a 404 (unpublished, superseded by 11954934). Server-rendered site search for 24 terms surfaced zero ids outside the census. Wayback CDX was offline (503) this pass. Retrieved 2026-09-16. || 318th: NEW (318th): NEW SURFACE: app.owner.com (found via certspotter CT log for *.owner.com; crt.sh was 502) is Owner's merchant dashboard, an Expo/react-native-web SPA whose login-gated screens ship in an anonymous static bundle: 14 JS files, 20.9 MB (index-f609244e... 18.0 MB), every /_expo/static/js/web/*.js path referenced in the bundle held at 200. No login used. The dashboard renders activity logs (activity.v1.locations.location.getActivityLogs, paged by type) only for settings: FeesActivityLogScreen, HoursActivityLogScreen, OrderingActivityLogScreen, PrepTimeActivityLogScreen, CouponActivityLogFlyout. Authorization RESOURCES enum lists 'order.void', 'order.refund', 'order.charge' and 'cash-drawer.session' as resources, but no screen displays an attributed override/approval trail. The fees, hours, ordering-options and prep-time activity-log routes are flagged internalOnly:!0 (Owner staff only). getAuditLogs /audit-logs sits under the domains router and auditGiftCards is a gift-card import check (poison). Bundle controls: refundedBy 0, voidedBy 0, approvedBy 0, "manager override" 0. Roles are permission toggles (void-orders, refund-or-charge-orders, discount-orders), not a per-event manager approval, so there is no approver to attribute. Still unknown: a server log may exist that the UI does not show. Retrieved 2026-09-16. || 322nd: NEW (322nd): NEW SURFACES: (a) public source maps probed on every live Owner SPA from the certspotter list: app.owner.com, dev-app.owner.com and embed-app.owner.com answer <bundle>.js.map, /asset-manifest.json, /.vite/manifest.json and a nonsense path with the same 2,228-byte HTML shell (soft-200 SPA catch-all, not a map); internal.owner.com, dev-internal.owner.com (Expo) and ai-phone-host.owner.com, photographer.owner.com (Vite) return 404 for every .map. No source map is public. (b) internal.owner.com, Owner's staff console (production), ships an anonymous Expo web bundle: 81 JS files, 17 MB, closed over every /_expo/static/js/web/*.js path referenced (all 200, 0 non-200). No login used. api.owner.com and dev-api.owner.com answer / with "Olympus ... is running in production/staging" but /swagger, /openapi.json, /docs, /redoc and a nonsense path all return a Cloudflare 403 challenge (a refusal, not an absence). The staff console has an AuditLogViewer ("Activity log") that calls activity.v1.brands.brand.getActivityLogs with typed filters. Every activity-event type literal in the staff console plus app.owner.com (quoted 'domain:event' strings) is: menu:coupon-created/-updated/-deleted(-brand), menu:coupon-availability-toggled, virtualcards:card-created/-details-viewed/-state-changed/-transaction-received, and crm:case-* (14 CRM case events). No void, refund, discount, comp or override event type appears; controls: "manager override" 0, voidedBy 0, "audit log(s)" 0 as prose (approvedBy 9 hits are all AI-agent tool-approval UI, poison). The activity log demonstrably attributes coupon and card events, but nothing shows override attribution. Still unknown. Retrieved 2026-09-17. || 329th: NEW (329th): NEW SURFACES. (1) help.owner.com re-censused from scratch (curl + browser UA, -L for the /en/collections/<id> 301-to-slug redirect the 322nd's crawler needed): collection BFS to a fixpoint in 3 rounds = 39 collections (13 top + 26 sub, titles extracted, incl. Reports, Billing & Payouts, Order Management, Settings, Hardware>Tablet/Printer), then an article fixpoint in 3 rounds = 143 ids, 142 live 200s and the same single 404 (11833154). The id set is IDENTICAL to the 314th's (comm: 142 common, 0 only-old, 0 only-new), so the KB has not grown; but the JSON-LD dateModified census is new and shows 12 articles re-edited since 2026-08-28, the newest 2026-09-17 (Phone Routing) -- none of them about audit or overrides. (2) The report catalogue article (https://help.owner.com/en/articles/13950704, updated 2026-08-28) is a CLOSED enumeration of every report in the dashboard: 9 groups (Sales 16, Orders 6, Customers, Sources, Cash Drawer, Marketing, Website, General, Advanced). There is no audit-log, activity-log, override or approvals report in it. (3) The Voids and Refunds report articles ENUMERATE their columns verbatim: Voids = 'Date, Order number, Customer, Amount, Tip, Reason' with a closed reason list (Cancelled by guest / by store / by operator, Denied by store, Confirmation expired/rejected/failed, Cancelled by DoorDash / Uber Eats / Grubhub); Refunds = 'Issued date, Refunded, Customer, Original payment, Total, Comment, Status'. Neither column list contains a user, staff, manager or approver field, and 'Cancelled by operator' is the whole team, not a person. (4) app.owner.com (today's rebuild, 14 files, 20.9 MB, fixpoint, see the payments-emv-nfc note) ships the merchant RBAC enumeration in full: PERMISSION_CATEGORIES with 23 permission-group slugs and human descriptions -- use-checkout, use-kds, use-time-clock, adjust-order-fulfillment, adjust-prep-time, discount-orders ('apply discounts to orders'), void-orders ('void orders'), refund-or-charge-orders, edit-menus, manage-stations, manage-gift-cards, manage-cash-drawers, manage-shifts, manage-jobs, manage-users, manage-inbox, edit-store-settings, view-reports, manage-billing, manage-marketing, manage-website, manage-customers, plus two internal tablet slugs -- and a 4-digit staff PIN validator ({pin,userId,brandId} DTO; rejects wrong length, repeating and consecutive digits) with getPin/setPin/reset-pin endpoints. There is NO 'requires manager approval' permission, no approval step and no override concept: void/discount/refund are per-user PERMISSIONS, so there is no approver to attribute. (5) The merchant-visible activity log is now fully enumerable: activityDescription is a dictionary of 29 event types with labels -- checkout:* 8 (busy-kitchen, kitchen-capacity-schedule, store-paused/unpaused, throttle-counters-cleared, scheduled-orders), partner:* 13 (store hours, online hours, special hours, pickup, dine-in, owner-fee-settings, processing-fee-bearer), delivery:* 3, processing:* 3 (custom rate card), pos-integrations:uber-store-settings-changed. All 29 are SETTINGS changes; zero void, refund, discount, comp or override event. Each row renders date/time, a description and before-to-after value rows, and its only attribution field is {label:'Device', value: fingerprint.metadata.audience} -- a device audience, not a person. (6) WHY THIS STILL CANNOT BE A 'no': activityDescription falls back to `t[s.type] ?? s.name.replaceAll('-',' ')`, i.e. the client renders event types it does not know, so the 29-entry dictionary is a DISPLAY MAP, not a census of what the server emits. Controls over the 14 files: actorName 0, actorType 0, actorId 0, performedBy 0, voidedBy 0, refundedBy 0, 'manager override' 0, 'audit log' 0 as prose; createdBy 2 (unrelated). Re-grep of the 322nd's internal.owner.com staff console (83 files, 35.2 MB, on disk) for this cell's vocabulary found actorId 1 -- useActorName(entry.actorId) in internal-screens-76dd734c..., which is the BRAND LIFECYCLE timeline (onboarding attestations and check waivers, attestedBy, 'legacy-approval'), Owner-staff onboarding, not restaurant manager overrides: new poison. 'requires approval' 2 = the internal AI browser-agent tool approval; immutable 3 = a hero-video proxy path and a published taxonomy version; approvedBy 9 = the same AI tool UI. KB controls: override/overrides 19 hits in 6 articles, every one a PREP-TIME override, a Kitchen Override throttle or a menu-field override on an integrated menu (https://help.owner.com/en/articles/11954845, 14709107) -- the atlas's 'manager override' sense scores 0; pin 2 (both 'pinned'), 'activity log' 0, audit 0. Retrieved 2026-09-18. adversarially verified
Builds and publishes employee shift schedules inside the same platform that holds the timekeeping data, rather than requiring a third-party scheduling app. differentiator
labor-native-scheduling
Not scored by this record.
Generates recommended staffing levels or labor hours by daypart from the operator's own POS sales history, not just a static template. differentiator
labor-demand-labor-forecast
Not scored by this record.
Displays labor cost as a percentage of sales in real time during service on a manager view or POS, not only in end-of-day or next-morning reports. differentiator
labor-realtime-labor-percent
Not scored by this record.
Warns or blocks at clock-in when an employee is approaching or would cross a configured overtime threshold, before the overtime is incurred. differentiator
labor-overtime-prevention
Not scored by this record.
Configures meal and rest break rules per state or jurisdiction, prompts required break attestation, and flags missed breaks for premium pay. differentiator
labor-break-compliance-by-state
Not scored by this record.
Enforces minor-labor restrictions (age-based maximum hours, prohibited time windows, school-day limits) at both scheduling and clock-in.
labor-minor-labor-rules
Not scored by this record.
Computes tip pooling and tip-outs automatically per shift from configurable rules (percentage of sales, hours worked, points, or role), rather than requiring a manual spreadsheet.
labor-tip-pooling-rules
Not scored by this record.
Retains a per-shift, per-employee record of tips received, amounts contributed to the pool, and amounts distributed from the pool, exportable for audit.
labor-tip-distribution-audit-trail
Not scored by this record.
Payroll export separates cash from charged qualified tips and carries a Treasury tipped-occupation code, supporting the W-2 Box 12 code TP and Box 14b reporting required for tax year 2026. differentiator
labor-qualified-tips-w2-reporting
Not scored by this record.
Vendor processes payroll itself as a first-party product (tax filing and direct deposit), as opposed to exporting to a third-party payroll provider only. differentiator
labor-native-payroll
Not scored by this record.
Exports timecards, wages, and tips in documented formats or via direct integration for at least two major payroll providers (e.g. Gusto, ADP, Paychex, QuickBooks).
labor-payroll-export-formats
Not scored by this record.
Employees can request shift swaps or claim open shifts in a self-service app, subject to a manager approval workflow that enforces overtime and role eligibility. differentiator
labor-shift-swap-workflow
Not scored by this record.
Reports per-employee sales performance metrics (average check, items or category attachment rate, void and comp rate) by server or cashier. differentiator
labor-server-performance-metrics
Not scored by this record.
Inventory, purchasing & cost control
Supports multi-level recipe/BOM costing where a recipe can contain sub-recipes (prep items) and plate cost recalculates automatically when any component ingredient's cost changes.
inventory-recipe-bom-costing
UPHELD, reason re-measured. The help centre's 38 collections, censused by an href fixpoint that closed at 141 articles, contain no inventory collection, and the Reports catalogue's nine numbered sections contain no inventory or cost report. More than silence, the vendor assigns the task outward: the Product Mix report's stated use is 'Forecast inventory based on what is actually selling' — i.e. inventory is forecast by the operator from sales data, not held and costed inside Owner. 'Recipe' occurs once across 227 product documents, in a customer case study. No ingredient, sub-recipe, plate cost or component-cost recalculation construct exists anywhere in the corpus. https://help.owner.com/en/articles/16419715-product-mix-report · retrieved 2026-09-08
Stores purchase unit, recipe unit, and count unit per item with explicit conversion factors, plus a yield/waste percentage applied to raw-to-usable conversion.
inventory-unit-conversion-yields
UPHELD, reason re-measured. The premise is not 'no module named in a catalog' but a censused surface: 38 help collections and 141 articles hold no inventory collection, and the Reports catalogue enumerates its nine sections in full — Sales, Orders, Customers, Sources, Cash Drawer, Marketing, Website, General, Advanced — with no inventory or cost section among them. 'Unit conversion' occurs zero times across the 227-document product corpus, and no purchase, recipe or count unit is stored anywhere; the only quantity Owner records against a menu item is the sold quantity in Product Mix. There is no raw-to-usable conversion or yield/waste percentage to grade. https://help.owner.com/en/articles/13950704-what-reports-are-available-in-my-owner-dashboard · retrieved 2026-09-08
Produces a theoretical-vs-actual usage variance report per item for a defined count period, showing theoretical usage from POS sales times recipe, actual usage from counts plus receipts, and the variance in both units and currency. differentiator
inventory-theoretical-vs-actual
Not scored by this record.
Depletes ingredient on-hand quantities in near real time as orders are fired at the POS, including depletion driven by modifier selections, not only in an end-of-day batch. differentiator
inventory-realtime-depletion
Not scored by this record.
Automatically 86s (marks unavailable) menu items on the POS, online ordering, and connected third-party delivery menus when a component ingredient hits zero or a configured threshold. differentiator
inventory-86-auto-sync
Not scored by this record.
Supports full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts.
inventory-count-modes
UPHELD, reason re-measured against a closed census rather than a catalog impression. Owner's stock-level vocabulary is availability, not counting: items are marked available or unavailable and can be 86'd from the Owner app, which is a boolean on a menu item. No physical count, spot count, cycle count or variance history appears in any of the 141 help articles, and the Reports catalogue's nine sections include no count or variance report. Caveat recorded rather than hidden: this help centre grew materially in 2026 as Owner POS shipped, so this is an absence over a surface that is actively expanding — but all three inventory constructs this claim needs are missing together, which is a product shape, not a documentation gap. https://help.owner.com/en/articles/13950704-what-reports-are-available-in-my-owner-dashboard · retrieved 2026-09-08
Provides a mobile/tablet counting app supporting barcode or QR scanning that continues to accept counts with no network connectivity and syncs on reconnect.
inventory-mobile-count-offline
Not scored by this record.
Ships pre-built electronic vendor catalog and order-transmission integrations with named broadline distributors (e.g. Sysco, US Foods, Performance Food Group) that send purchase orders and receive invoices electronically rather than by emailed PDF. differentiator
inventory-vendor-catalogs-edi
Not scored by this record.
Ingests supplier invoices from photo, PDF, or email and extracts line-item detail (item, quantity, unit, price) into the inventory ledger without manual line entry. differentiator
inventory-invoice-ocr
Not scored by this record.
Tracks per-item purchase price history across invoices and alerts when a received price exceeds the prior or contracted price by a configurable threshold. differentiator
inventory-price-change-alerts
Not scored by this record.
Maintains par levels per item per location and generates suggested purchase order quantities from on-hand versus par, with at least one mode driven by a sales forecast rather than a static par. differentiator
inventory-par-auto-suggest
Not scored by this record.
Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.
inventory-waste-logging
Not scored by this record.
Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.
inventory-shelf-life-expiry
Not scored by this record.
Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting.
inventory-bar-partial-bottle
Not scored by this record.
Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.
inventory-cogs-gl-export
Not scored by this record.
Inventory and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator
inventory-native-not-partner
Not scored by this record.
Reporting, BI & data access
Provides a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise.
reporting-realtime-dashboard
An operator dashboard covers Owner's own online channels only, not in-store sales; refresh latency and mobile access are not documented.
Generates a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types, and expected cash deposit in one document.
reporting-eod-closeout
OVERTURNED. The standing rationale — 'No cash drawer, tender types or EOD reconciliation — that stays with the POS' — is falsified on all three counts by the vendor's own reports catalogue. Cash drawer: an entire numbered section, 'Cash Drawer View data about your cash drawer sessions. You can also filter by individual device', whose Cash Drawer History shows 'Opening balance, cash sales, refunds, and paid in/out per session'. Tender types: 'Payments By Type Sales, taxes, tips, and fees broken down by payment method'. The remaining components exist as named reports too — Total Sales, Taxes, Tips, Refunds, Coupon Usage, and an Explore Orders view giving 'subtotal, tax, tip, discounts, fees, and net sales'. Shortfall, and it is why this is not a yes: these are separate reports on separate screens. No article describes a single daily close-out or EOD document assembling them, and no expected cash deposit figure is reconciled anywhere. Partial. https://help.owner.com/en/articles/13950704-what-reports-are-available-in-my-owner-dashboard · retrieved 2026-09-08
Provides a product mix (PMIX) report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center.
reporting-pmix-modifier-level
Value unchanged at partial; the standing rationale is falsified and replaced. That rationale said the report catalogue 'names no menu-item PMIX report' — it now does, and there is a dedicated article for it. Product Mix is nested the full depth this claim asks for: 'Menu > Category > Item > Option group > Option', and 'For each row you see: Quantity sold: how many times it sold. Average price: the average it sold for. Gross sales: the total revenue it brought in.' Item level and modifier level are therefore both covered, with quantity and gross sales, and the older Option Group Sales report survives alongside it. Shortfall, and it is why this stays partial: the report gives average price where the claim asks for net sales, and the only filter documented is a date range ('Choose a date range, and export the data if you want to dig in elsewhere') — no daypart and no revenue-centre dimension exists here or anywhere in the nine-section Reports catalogue. https://help.owner.com/en/articles/16419715-product-mix-report · retrieved 2026-09-08
Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.
reporting-comps-voids-audit
Not scored by this record.
Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.
reporting-cash-over-short
Not scored by this record.
Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.
reporting-labor-productivity
Not scored by this record.
Reports per-server metrics including average check, items per check, attachment rate for named categories, and tips as a percentage of sales. differentiator
reporting-server-scorecards
Not scored by this record.
Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator
reporting-channel-profitability
Not scored by this record.
Supports scheduling any report for automatic recurring delivery by email or to a shared destination on a defined cadence and recipient list.
reporting-scheduled-delivery
Not scored by this record.
Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator
reporting-public-api
Not scored by this record.
Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator
reporting-webhooks
Not scored by this record.
API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator
reporting-api-not-upcharged
Not scored by this record.
Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator
reporting-tier-paywall
Not scored by this record.
Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator
reporting-history-retention
Not scored by this record.
Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator
reporting-anomaly-alerts
Not scored by this record.
Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.
reporting-nl-query
Not scored by this record.
Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator
reporting-guest-cohorts
Not scored by this record.
Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator
reporting-sales-forecast
Not scored by this record.
Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.
reporting-tip-tax-compliance
Not scored by this record.
Multi-location, franchise & enterprise governance
Supports a named organizational hierarchy of at least three levels (e.g. enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations.
multi-location-org-hierarchy
CLAIM: a named hierarchy of at least three levels, as a first-class object that reporting and permissions scope to. VERDICT: partial/C. EVIDENCE (help, B): brand and location are first-class ("Settings , then Brand settings", https://help.owner.com/en/articles/11833522; "Turning off a brand-level menu hides it at every connected location at once", https://help.owner.com/en/articles/15139944; "Brand-level price updates will override any location-level changes", https://help.owner.com/en/articles/12632121). A middle grouping also exists. 'Add your legal business and tax details' (https://help.owner.com/en/articles/16635938-add-your-legal-business-and-tax-details): "Add one entity for each legal business that owns your locations ... Under Locations owned , check every location this business owns ... If different legal businesses own different locations, add a separate entity for each." Marketing sends go to "a location or select All locations" (https://help.owner.com/en/articles/11832799). EVIDENCE (bundle, C): Storefront bundle: pudgeeseatery.com is an Owner Astro storefront with static-content.owner.com assets. Its HTML sits behind a Cloudflare challenge and was fetched with headless Chromium; /_astro JS is served to curl. 92 JS files, 3.13 MB, closed over static imports and __vite__mapDeps, with 0 non-literal import(). All 78 hashed chunk names referenced are held. Its internal route tree has "ownershipGroups ... createOwnershipGroup ... listOwnershipGroups ... assignLocations POST /locations", and getActivityLogs at /brands/{brandId}, /ownership-groups/{ownershipGroupId} and /locations/{locationId}. That is a brand > ownership group > location structure, which at least the activity logs scope to. SHORTFALL: the middle level is a legal-ownership grouping, not a documented operator region or group. No public doc says reports or permissions scope to it, and reports filter by brand or location (route error "invalid-brand-or-location-filter"). BOUND: help.owner.com is an Intercom help centre. Census = 13 top collections + 33 sub-collections (46, all 200) and 142 articles (all 200). The href fixpoint over the bodies added one id: 11833154 "How do I adjust my menu's hours?", a 404 (unpublished, superseded by 11954934). Server-rendered site search for 24 terms surfaced zero ids outside the census. Wayback CDX was offline (503) this pass. Retrieved 2026-09-16. https://help.owner.com/en/articles/16635938-add-your-legal-business-and-tax-details · retrieved 2026-09-16 adversarially verified
Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.
multi-location-price-zones
The help centre enumerates the entire price-management surface and no tier/zone construct is in it. An item record carries exactly one price — 'How do I change a menu item's price?' is 'Click Amount and update the price', a single field with no location-group, channel or daypart dimension — and the only multi-item tool, the Bulk Price Editor ('Increase or decrease prices by a $ amount or %', with rounding to $0.00/$0.50/$0.95/$0.99), states its own scope limit: 'You can only use the bulk editor at the location level', and 'This feature is not available for Clover or Toast-integrated locations'. On POS-integrated locations Owner cannot set prices at all: 'Prices, allergens, and dietary options cannot be overridden and must be changed in your integrated system.' A different price at another location therefore means a separate per-location item record (or the underlying POS), which is precisely the duplication this claim excludes. https://help.owner.com/en/articles/12632121-can-i-update-prices-for-multiple-menu-items-at-once · retrieved 2026-08-04
Provides above-store reporting that aggregates sales, labor, discounts, voids, and item mix across any selected set of locations in one view, with store-vs-store ranking and variance flags.
multi-location-consolidated-reporting
Not scored by this record.
Gift cards issued at one location are redeemable at any other location in the brand, with a reported outstanding-liability balance and inter-store settlement/redemption reconciliation between owners.
multi-location-cross-location-giftcard
Not scored by this record.
A single customer loyalty profile, balance, and stored order history is shared across all locations in the brand rather than being per-location.
multi-location-cross-location-loyalty
Not scored by this record.
A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. differentiator
multi-location-multi-brand
Not scored by this record.
Tax configuration is per-location with support for multiple simultaneous tax rates, jurisdiction-specific rules (e.g. prepared-food vs grocery, inclusive vs exclusive tax), and per-location tax exemptions.
multi-location-multi-tax-jurisdiction
Not scored by this record.
Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.
multi-location-central-labor-policy
Not scored by this record.
Hardware & physical footprint
The POS software runs on commodity off-the-shelf hardware (standard iPads, Android tablets, or PCs) that the operator can buy from a third party, rather than only on vendor-supplied proprietary terminals. differentiator
hardware-commodity-devices
Not scored by this record.
Vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs.
hardware-os-platforms
OVERTURNED. Both halves of the standing rationale are wrong: there is client terminal software (the Kitchen App on the Owner tablet), and the app platforms ARE specified with minimum versions — 'Which devices does the Owner App support? Any iPhone running iOS 15 or later and any Android phone on Android 11 or later.' The in-restaurant hardware is named to the model as well: 'It is a Lenovo Yoga Tab 11 with a built-in stand.' Shortfall: that is one device model, not a spec floor — the vendor states no minimum OS version, memory or screen size for the tablet or the POS app, publishes no supported-device list a restaurant could check its existing hardware against, and names no Windows, Linux or browser client. Documented for the operator phone app, undocumented for the terminal. Grade C: both sources are marketing product pages. https://www.owner.com/mobile · retrieved 2026-09-08
Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.
hardware-handheld-purpose-built
Not scored by this record.
The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator
hardware-handheld-battery-swap
Not scored by this record.
Handhelds support cellular/LTE connectivity as a documented fallback when store Wi-Fi drops, either built into the device or via a vendor-supplied failover.
hardware-handheld-lte
Not scored by this record.
Terminals continue to take orders, print to kitchen, and record cash sales with the internet down, and the vendor documents explicitly which functions degrade (card auth, loyalty lookup, refunds).
hardware-offline-mode
UPHELD, reason corrected. 'Cloud-only; no terminals' is half wrong — Owner ships a terminal — but the offline verdict survives on the vendor's own answer about that terminal: 'Does the tablet work if my internet goes down? The tablet requires an internet connection to process orders and sync with your Owner account. We recommend keeping a reliable Wi-Fi connection in your kitchen. The app updates automatically whenever it is connected.' Orders are not taken, kitchen printing does not proceed and cash sales are not recorded offline, and the vendor publishes no degradation matrix naming which functions survive. The printer is Bluetooth-paired to the tablet, but the tablet is the thing that requires the connection. https://www.owner.com/kitchen-tablet · retrieved 2026-09-08
Sells or supports a dedicated kitchen display system with bump-bar or touch input, station routing, and course/fire timing, as a first-party product rather than an integration-only dependency.
hardware-kds
OVERTURNED. 'No KDS product' is contradicted by the vendor naming one — the Owner App page states that changes 'appear on the dashboard, KDS, and POS within seconds' — and by a documented first-party kitchen display: a Kitchen tab in the Owner tablet's side drawer showing ticket cards that open ('The button is on the ticket card, and also inside the ticket once you open it'), a Kitchen Status control that switches the station between Normal and Busy, and item labels that print 'when an order fires to the kitchen'. It is first-party, on Owner's own hardware, not an integration dependency. Shortfall: touch only, with no bump bar or keypad; no station routing by item or category (printing routes by order origin); and no course or fire timing — 'course' and 'fire' as kitchen terms occur zero times across 227 product documents. Partial, not yes. https://help.owner.com/en/articles/16419487-print-receipts-and-tickets-on-your-owner-tablet-or-pos · retrieved 2026-09-08
Offers a self-order kiosk running the same menu and modifier engine as the POS, in both countertop and freestanding form factors, with integrated payment and accessibility (ADA) compliance documented. differentiator
hardware-kiosk
Not scored by this record.
Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, and speaker/headset integration, with a documented timer/speed-of-service measurement.
hardware-drive-thru
Not scored by this record.
Works with standard ESC/POS thermal receipt and kitchen printers from more than one manufacturer (e.g. Epson and Star), including LAN/Ethernet printers, rather than only vendor-branded printers.
hardware-printer-compatibility
Not scored by this record.
Supports the standard peripheral set — cash drawers (including multi-drawer per terminal), barcode scanners, scales for by-weight items, and customer-facing displays — with a published compatibility list.
hardware-peripherals
Not scored by this record.
Card entry happens on a PCI-listed PTS device using validated point-to-point encryption, so the POS application and tablet stay out of PCI scope; the vendor states the merchant's SAQ type.
hardware-p2pe-terminal
Not scored by this record.
Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. differentiator
hardware-tap-to-phone
Not scored by this record.
Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator
hardware-pricing-transparency
Not scored by this record.
Hardware can be purchased outright (owned) as an alternative to a mandatory lease or subscription-bundled rental, and the vendor states which. differentiator
hardware-ownership-vs-lease
Not scored by this record.
Vendor documentation confirms whether hardware purchased from the vendor remains usable with other software after cancellation, i.e. it is not software-locked or remotely bricked. differentiator
hardware-usable-after-churn
Not scored by this record.
Publishes a hardware warranty term and a replacement/advance-exchange SLA with a stated turnaround (e.g. next-business-day depot swap). differentiator
hardware-rma-sla
Not scored by this record.
Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.
hardware-byod
Not scored by this record.
Provides a remote device-management console showing each terminal, printer, and KDS as online/offline, with remote reboot, software-version visibility, and staged rollout of updates. differentiator
hardware-remote-device-management
Not scored by this record.
Integrates with specialty beverage hardware — self-pour tap walls, flow meters, or liquor pour spouts — such that pours post to a POS tab automatically.
hardware-selfpour-scales
Not scored by this record.
Supports inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call.
hardware-callerid-integration
Not scored by this record.
Integrations, API & extensibility
Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.
extensibility-public-api-docs
CLAIM: public, self-serve API reference readable without an agreement or sales call. VERDICT: no/B. BOUND: (1) www.owner.com/sitemap.xml has 159 URLs and none contains api or developer. www.owner.com/llms.txt, the vendor's own 18 KB site manifest, lists product, integration, case-study and blog pages and no developer or API page. /api, /docs and /developers return the site's 404 (the same 19,831-byte body as a nonsense path). (2) The full help.owner.com census (142 articles) has 34 hits for API/developer(s)/endpoint(s)/webhook(s)/OAuth in 6 articles. Every one concerns Apple App Store Connect or Apple Developer accounts (e.g. "Enable Owner.com API access in App Store Connect", https://help.owner.com/en/articles/16600799) or Google Business Profile access. POISON: "API access" there means Owner's access to the restaurant's Apple account, not an Owner API. (3) developers., developer., docs. and partners.owner.com do not resolve. api.owner.com answers 403, recorded as a refusal and not read as docs. (4) The storefront bundle ships Owner's internal route tree (3,313 nodes) but no reference docs, auth guide or developer-portal link. zapier.com/apps/owner and /apps/ownercom both 404. BOUND: help.owner.com is an Intercom help centre. Census = 13 top collections + 33 sub-collections (46, all 200) and 142 articles (all 200). The href fixpoint over the bodies added one id: 11833154 "How do I adjust my menu's hours?", a 404 (unpublished, superseded by 11954934). Server-rendered site search for 24 terms surfaced zero ids outside the census. Wayback CDX was offline (503) this pass. Retrieved 2026-09-16. https://www.owner.com/llms.txt · retrieved 2026-09-16 adversarially verified
API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator
extensibility-api-access-cost
Not scored by this record.
A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator
extensibility-free-sandbox
Not scored by this record.
Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).
extensibility-oauth-partner-apps
OWNER RULING 2026-09-18 (Q6): a COMPLETE route manifest of the vendor's own app may stand in for a published API doc. Owner.com's typed route table (app.owner.com rebuild, 14 files, fixpoint, 0 misses, 2,353 endpoint nodes under 1,015 routers) is the whole backend's route surface; it carries the `no` at grade B as the evidence below states. Retrieved 2026-09-18. PRIOR EVIDENCE: CLAIM: third-party apps authenticate via scoped, operator-granted, revocable OAuth. VERDICT: still unknown. NEW SURFACE: Storefront bundle: pudgeeseatery.com is an Owner Astro storefront with static-content.owner.com assets. Its HTML sits behind a Cloudflare challenge and was fetched with headless Chromium; /_astro JS is served to curl. 92 JS files, 3.13 MB, closed over static imports and __vite__mapDeps, with 0 non-literal import(). All 78 hashed chunk names referenced are held. src.wIz1V6eZ.js holds Owner's internal API route tree (3,313 nodes). Every OAuth route in it has Owner acting as the CLIENT of another platform: createCloverOAuthUrl, createUberOAuthUrl, /oauth/uber/authorize|callback|complete|kickoff, Google "/grants ... createGrant ... listGrants" for Google Business Profile, and a social "/oauth". There is no authorize/consent or client-registration route through which a third party could obtain grants against Owner data. The help census (142 articles) has 0 OAuth hits. A route tree shipped in a customer bundle is not a proven census of the server API, so no 'no' is published. BOUND: help.owner.com is an Intercom help centre. Census = 13 top collections + 33 sub-collections (46, all 200) and 142 articles (all 200). The href fixpoint over the bodies added one id: 11833154 "How do I adjust my menu's hours?", a 404 (unpublished, superseded by 11954934). Server-rendered site search for 24 terms surfaced zero ids outside the census. Wayback CDX was offline (503) this pass. Retrieved 2026-09-16. || 322nd: NEW (322nd): NEW SURFACES: (a) public source maps probed on every live Owner SPA from the certspotter list: app.owner.com, dev-app.owner.com and embed-app.owner.com answer <bundle>.js.map, /asset-manifest.json, /.vite/manifest.json and a nonsense path with the same 2,228-byte HTML shell (soft-200 SPA catch-all, not a map); internal.owner.com, dev-internal.owner.com (Expo) and ai-phone-host.owner.com, photographer.owner.com (Vite) return 404 for every .map. No source map is public. (b) internal.owner.com, Owner's staff console (production), ships an anonymous Expo web bundle: 81 JS files, 17 MB, closed over every /_expo/static/js/web/*.js path referenced (all 200, 0 non-200). No login used. api.owner.com and dev-api.owner.com answer / with "Olympus ... is running in production/staging" but /swagger, /openapi.json, /docs, /redoc and a nonsense path all return a Cloudflare 403 challenge (a refusal, not an absence). The staff console ships the same internal route tree; every OAuth route still has Owner as the CLIENT: /oauth/mobile, Google Workspace callback (oauth/google-workspace-callback.tsx), a calendar /oauth/start and /oauth/complete ("owner-account-required"), createCloverOAuthUrl, createUberOAuthUrl, and Google Business Profile service-grant errors. client_secret 0; "api key(s)" 55, all Vercel AI Gateway errors, Google Maps keys and Apple App Store Connect keys (poison). No authorize/consent screen for third parties. Still unknown (client-shipped route tree is not a census of the server). Retrieved 2026-09-17. || 329th: NEW (329th): NEW SURFACES. (1) Owner publishes no API at all, now measured rather than inferred: api.owner.com/swagger, /openapi.json, /docs and /v3/api-docs return real 404s to curl + browser UA (414-419 bytes vs a 422-byte nonsense-path control), not the Cloudflare 403 the 322nd recorded from node fetch; api.owner.com/ still answers 'Olympus ... is running in production' (105 bytes). developer.owner.com and docs.owner.com do not resolve; the 159-URL sitemap of the rebuilt www.owner.com has no /api or /developers page (both probed: 404), and there is no 'Partner with Owner' developer surface beyond a lead form. (2) The strongest census yet of what Owner's server exposes: today's app.owner.com rebuild (14 files, 20,948,162 bytes, fixpoint, 0 misses) carries a TYPED ROUTE MANIFEST of the whole Olympus backend -- 2,353 endpoint nodes with method, path and error codes under 1,015 routers, including routes the merchant UI never calls (staff/internalOnly, CRM, lifecycle). All 14 OAuth routes in it still have Owner acting as the CLIENT of someone else: createCloverOAuthUrl POST /clover-oauth-url, createUberOAuthUrl POST /uber-oauth-url, createTestPosCloverOAuthUrl and createTestPosUberOAuthUrl (/test-pos/...), uberOAuthAuthorize GET /oauth/uber/authorize, uberOAuthCallback, uberOAuthComplete, uberOAuthKickoff, and a calendar pair start POST /oauth/start + complete POST /oauth/complete. There is no client-registration, authorize/consent, token-issuance, scope-grant or revocation endpoint through which a third party could obtain a scoped grant against Owner data, and no /apps or marketplace router. (3) Controls over the 14 files of the new build: client_secret 0, clientSecret 0, 'personal access token' 0, pkce 0, authorization_code 0, 'partner app' 0, 'app marketplace' 0, scopes 0 in the OAuth sense. A re-grep of the 322nd internal.owner.com console (83 files, 35.2 MB) and the 314th storefront _astro corpus (92 files, 3.13 MB) for this cell's vocabulary returns high counts that are all vendored-SDK poison: hmac = the jose JWE library, callbackUrl = the Vercel AI SDK plus the Clover OAuth return URL, 'api key' = AI-gateway/Google-Maps/App-Store-Connect key errors. (4) The help census (143 ids, fixpoint, 142 live -- see the labor note) has OAuth 0 and 'api key' 0; its only API article is 'Enable Owner.com API access in App Store Connect' (16600799), i.e. granting OWNER access to the restaurant's Apple developer account -- the reverse direction, and long-standing poison. (5) Why still not a 'no': per the 327th merge rule a capability 'no' on OAuth/partner apps is not bounded by a client-shipped manifest when the vendor runs an unpublished partner API, and Owner's API is demonstrably unpublished (404, not a spec). The manifest is Owner's own typed route table for the entire backend, which is the strongest bound available short of a published spec; if the OWNER accepts a route-manifest census as equivalent to a published doc, this cell is a 'no' at grade B on it. Retrieved 2026-09-18. https://app.owner.com/_expo/static/js/web/index-aa6c965cc16dd4371231e5f046f8ae83.js · retrieved 2026-09-18 adversarially verified
The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.
extensibility-webhooks-push
OWNER RULING 2026-09-18 (Q6): a COMPLETE route manifest of the vendor's own app may stand in for a published API doc. Owner.com's typed route table (app.owner.com rebuild, 14 files, fixpoint, 0 misses, 2,353 endpoint nodes under 1,015 routers) is the whole backend's route surface; it carries the `no` at grade B as the evidence below states. Retrieved 2026-09-18. PRIOR EVIDENCE: CLAIM: real-time outbound webhooks for order lifecycle events. VERDICT: still unknown. NEW SURFACE: Storefront bundle: pudgeeseatery.com is an Owner Astro storefront with static-content.owner.com assets. Its HTML sits behind a Cloudflare challenge and was fetched with headless Chromium; /_astro JS is served to curl. 92 JS files, 3.13 MB, closed over static imports and __vite__mapDeps, with 0 non-literal import(). All 78 hashed chunk names referenced are held. src.wIz1V6eZ.js holds Owner's internal API route tree (3,313 nodes). Its "/webhooks" router lists only INBOUND receivers: calcom, calendly, cloudconvert, clover, customerio, dnsimple, doordash, growth-service, intercom, livekit, loyalty/hang, mailgun, marketplace (doordash, grubhub, ubereats), physical-media, posintegration/uber, posthog, postmark, postmates, privacy, push, quo, scaleserp, scout, slack, square, stripe, toast, twilio, uber-eats, woflow, yext and zapier. No route registers or manages an outbound webhook subscription for a third party. The help census (142 articles) has 0 webhook(s) hits. Not published as 'no': the route tree is client-shipped and not a proven census of the server, and no vendor sentence rules outbound events out. BOUND: help.owner.com is an Intercom help centre. Census = 13 top collections + 33 sub-collections (46, all 200) and 142 articles (all 200). The href fixpoint over the bodies added one id: 11833154 "How do I adjust my menu's hours?", a 404 (unpublished, superseded by 11954934). Server-rendered site search for 24 terms surfaced zero ids outside the census. Wayback CDX was offline (503) this pass. Retrieved 2026-09-16. || 322nd: NEW (322nd): NEW SURFACES: (a) public source maps probed on every live Owner SPA from the certspotter list: app.owner.com, dev-app.owner.com and embed-app.owner.com answer <bundle>.js.map, /asset-manifest.json, /.vite/manifest.json and a nonsense path with the same 2,228-byte HTML shell (soft-200 SPA catch-all, not a map); internal.owner.com, dev-internal.owner.com (Expo) and ai-phone-host.owner.com, photographer.owner.com (Vite) return 404 for every .map. No source map is public. (b) internal.owner.com, Owner's staff console (production), ships an anonymous Expo web bundle: 81 JS files, 17 MB, closed over every /_expo/static/js/web/*.js path referenced (all 200, 0 non-200). No login used. api.owner.com and dev-api.owner.com answer / with "Olympus ... is running in production/staging" but /swagger, /openapi.json, /docs, /redoc and a nonsense path all return a Cloudflare 403 challenge (a refusal, not an absence). Controls over the 81 staff-console files: webhook(s) 63: the same INBOUND /webhooks router already recorded (toast, uber posintegration, privacy, parallel, otter, phone-ordering egress, etc.), a data-ingest monitor ('webhook'===source.delivery), Twilio inbound-message wiring, and the bundled Vercel AI SDK ("This model does not support webhooks. Falling back to polling.") -- all poison; a staff-console permission list names resources 'webhook' and 'webhook.otter' (internal RBAC, not a merchant/partner subscription); "webhook-subscription(s)" 0 in the staff console and in app.owner.com; "outbound webhook" 0. No route or screen registers an outbound webhook for a third party. Still unknown. Retrieved 2026-09-17. || 329th: NEW (329th): NEW SURFACE: the typed route manifest in today's app.owner.com rebuild (entry index-aa6c965cc16dd4371231e5f046f8ae83.js; 14 files, 20,948,162 bytes, fixpoint in 3 rounds, every referenced /_expo/static/js/web/*.js path 200, 0 misses) -- 2,353 endpoint nodes with method, path and error codes under 1,015 routers, extracted to endpoints.txt. Every one of the 28 webhook routes in it is an INBOUND receiver Owner exposes for a partner to POST to: calcomWebhook, calendlyWebhook, cloudconvertWebhook, growthServiceWebhook, hangWebhook (loyalty), cancelWebhook POST /orders/cancel, dasherStatusWebhook POST /dasher-status, menuRequestWebhook GET /menu-request/:id, menuStatusWebhook, onboardingStatusWebhook, orderWebhook POST /orders (three marketplace copies), storeDeactivationWebhook, deliveryUpdatesWebhook POST /delivery-status, menuIngestionStatusWebhook, orderValidationWebhook POST /order-validation, postmarkBounce/Delivery/InboundWebhook, privacyWebhook, scoutWebhook and three slackEventsWebhooks. No endpoint creates, lists, updates or deletes an outbound webhook subscription for a merchant or a third party, and there is no /webhooks management router, no event-type catalogue and no signing-secret route. Controls over the 14 files: 'webhook subscription' 0, webhookSubscription 0, 'outbound' 0, 'callback url' 0 (Owner's own), 'signing secret' 0, signingSecret 0, hmac 0, 'order.created' 0, orderCreated 0, sse 0, pubsub 0. Re-grep of the 322nd internal.owner.com corpus (83 files, 35.2 MB) for this vocabulary: every hit is vendored-SDK poison -- hmac 36 = the jose JWE library, callbackUrl 7 = the Vercel AI SDK start-url plus the Clover OAuth return URL, retry 607 = HTTP client backoff, eventType 178 = analytics; 'webhook subscription' remains 0. The 143-id help census (fixpoint, 142 live) has webhook(s) 0; its 'subscription' hits are the merchant's own billing subscription and guests' SMS/email marketing subscriptions (new poison for this cell). api.owner.com now returns a genuine 404 (not the 322nd's node-fetch 403) for /swagger, /openapi.json, /docs and /v3/api-docs, so no published spec exists to bound the server; per the 327th rule the cell is held rather than published as 'no', but the manifest is the whole backend's route table, so a 'no' at grade B is available if the OWNER accepts a route-manifest census. Retrieved 2026-09-18. https://app.owner.com/_expo/static/js/web/index-aa6c965cc16dd4371231e5f046f8ae83.js · retrieved 2026-09-18 adversarially verified
Webhooks are cryptographically signed (e.g. HMAC) AND documented to retry with backoff, with a replayable event log for missed deliveries. differentiator
extensibility-webhook-reliability
Not scored by this record.
A public write API accepts externally originated orders into the POS as first-class tickets that fire to KDS/printers and land in reporting.
extensibility-order-injection-api
Not scored by this record.
The vendor is a named DoorDash Preferred Integration Partner (DPIP) under the 2026 program requirements. differentiator
extensibility-doordash-preferred
Not scored by this record.
Direct, first-party certified integrations exist with DoorDash, Uber Eats, and Grubhub without requiring a paid middleware layer (Otter/Chowly/Deliverect/Checkmate). differentiator
extensibility-first-party-delivery-integrations
Not scored by this record.
The POS is a supported endpoint for at least two major aggregation middleware platforms (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate).
extensibility-middleware-compatibility
Not scored by this record.
Native, vendor-maintained connectors exist for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export.
extensibility-accounting-connectors
Not scored by this record.
Labor hours export natively to at least two named payroll providers (e.g. Gusto, ADP, Paychex, Paylocity) without manual re-keying.
extensibility-payroll-export
Not scored by this record.
The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.
extensibility-app-marketplace
Not scored by this record.
The vendor supports a headless/embedded mode where a third-party UI (kiosk, web ordering, drive-thru) drives the POS transaction engine via API.
extensibility-headless-embedded
Not scored by this record.
A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator
extensibility-data-portability-exit
Not scored by this record.
Reliability, offline & operations
Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.
reliability-offline-order-entry
UPHELD, reason corrected. 'No on-terminal software to degrade to' is false — the Kitchen App is on-terminal software that takes phone and in-store orders — so the verdict now rests on the vendor's direct statement about that terminal instead: 'The tablet requires an internet connection to process orders and sync with your Owner account.' Order entry, ticket routing and check printing all run through the tablet's connection to the Owner account, so none of the three continues when the connection is lost. https://www.owner.com/kitchen-tablet · retrieved 2026-09-08
Card payments can be accepted while offline via store-and-forward, not just cash-only fallback. differentiator
reliability-offline-card-auth
Not scored by this record.
The vendor publicly documents who bears the loss when a store-and-forward transaction declines after connectivity returns, and states any per-transaction or cumulative offline cap. differentiator
reliability-offline-decline-liability
Not scored by this record.
Multiple terminals continue to share a single check/table state over the local network while the internet is down (LAN-only degraded operation, not per-terminal islands). differentiator
reliability-lan-degraded-multi-terminal
Not scored by this record.
The vendor documents a local/on-premise transaction engine or edge server (not purely cloud-hosted request/response) for the ordering path. differentiator
reliability-local-transaction-engine
Not scored by this record.
Kitchen display and/or kitchen printer routing continues to function while offline.
reliability-offline-kds-printing
UPHELD, reason corrected. 'No first-party kitchen routing' is falsified — Owner runs a first-party Kitchen tab and drives an Owner-branded Bluetooth printer from it, with automatic ticket and item-label printing when an order fires. The offline half stands on the vendor's own tablet FAQ: 'The tablet requires an internet connection to process orders and sync with your Owner account.' Kitchen display and kitchen printing are both downstream of an order the tablet cannot receive offline; the printer's Bluetooth link to the tablet does not change that, and no article claims any queued or degraded kitchen mode. https://www.owner.com/kitchen-tablet · retrieved 2026-09-08
The system automatically fails over to a backup printer or KDS station when a configured kitchen printer is unreachable, and alerts staff.
reliability-printer-fallback
UPHELD, reason corrected — and the old reason was badly wrong. 'No first-party printer management' is falsified by an entire Printer collection under Hardware: pairing an Owner TSP-100 over Bluetooth, a Station printer list reached by 'Settings , then Station , then Printing', a Test Print, per-station auto-print toggles, copy counts of 1 to 5, font sizes, and item-label printing. That article enumerates the complete printing settings surface, and no backup or failover printer can be configured in it: there is no secondary printer field, no rule for an unreachable printer, and no alert. The only recovery documented anywhere is manual and human — reprinting on demand from the Kitchen or Orders tab, and a troubleshooting step to 'confirm it's still paired'. Automatic failover with staff alerting is absent from the surface that would define it. https://help.owner.com/en/articles/16419469-manage-your-printing-settings · retrieved 2026-09-08
The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).
reliability-sync-conflict-handling
Not scored by this record.
The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).
reliability-offline-feature-matrix
Not scored by this record.
A public, per-component status page exists showing current and historical incident state without a login.
reliability-public-status-page
Not scored by this record.
24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.
reliability-247-live-support
Not scored by this record.
The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator
reliability-onsite-install
Not scored by this record.
A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.
reliability-hardware-replacement-sla
Not scored by this record.
The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.
reliability-pci-dss-4-attestation
Not scored by this record.
Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.
reliability-mfa-role-based-access
Not scored by this record.
A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.
reliability-self-serve-training
Not scored by this record.
Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. differentiator
reliability-failover-terminal-role
Not scored by this record.
Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.
reliability-cellular-backup
Not scored by this record.
Commercial, compliance & data ownership
Vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core POS software tier. differentiator
commercial-month-to-month-contract
Not scored by this record.
Vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. differentiator
commercial-no-early-termination-fee
Not scored by this record.
The auto-renewal term and the required cancellation notice window (e.g. 30/60/90 days) are stated in publicly accessible contract terms rather than only in a signed quote.
commercial-autorenew-terms-published
Publicly states month-to-month billing with no long-term contract, no commitment and no cancellation fee — so no notice window applies. https://www.owner.com/pricing · retrieved 2026-08-01
The POS software can be purchased and operated with a third-party payment processor of the operator's choice (no mandatory in-house processing lock). differentiator
commercial-processing-not-bundled
Not scored by this record.
Vendor publishes an interchange-plus (cost-plus) processing rate option with the markup stated as a specific bps + per-transaction figure, rather than only blended/flat card-present rates. differentiator
commercial-interchange-plus-published
Not scored by this record.
The processing agreement caps or prohibits unilateral vendor-initiated rate increases outside of pass-through interchange/network changes, or grants penalty-free exit on any increase. differentiator
commercial-rate-increase-clause
Not scored by this record.
Per-location and per-additional-terminal software pricing is published as specific dollar figures on the vendor's public site (not 'contact sales' only).
commercial-pricing-published
Both plans carry specific monthly figures and the per-order fee structure is stated; only multi-location is quote-based. https://www.owner.com/pricing · retrieved 2026-08-01
Individual modules (online ordering, KDS, loyalty, inventory, payroll, marketing) can be purchased à la carte and cancelled independently without repricing the base POS subscription. differentiator
commercial-module-unbundling
Not scored by this record.
All required terminals, KDS screens, and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental.
commercial-hardware-purchase-outright
OVERTURNED. 'Ships no terminals, KDS screens or printers at all, so there is nothing to purchase and nothing leased' is contradicted by two dedicated sections of Owner's own contract. Tablets and Printers are each supplied under a loan or a purchase model: 'Owner may charge Business a monthly per-Loaned Tablet fee as indicated on the Pricing Page', and 'If Business chooses to purchase any Tablets provided to Business by Owner, and Owner provides an option for Business to do so, Owner may charge a fee per Purchased Tablet... as agreed by Owner and Business at the time of that purchase', with the parallel construction for Printers in section 9. What supports partial rather than yes: purchase is at Owner's discretion ('and Owner provides an option for Business to do so') and priced 'as agreed... at the time of that purchase', so there is no published hardware price — the Pricing Page the contract points to publishes only the $249 and Flat Rate subscription tiers and names no tablet, printer or setup fee. What supports partial rather than no: the loan alternative is explicitly monthly and terminates with the agreement ('Loaned Tablets are loaned, not sold'; returned within five business days on termination), so no multi-year hardware lease is mandatory. https://www.owner.com/restaurant-participation-agreement · retrieved 2026-09-08
Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator
commercial-hardware-not-locked
Not scored by this record.
Operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee.
commercial-data-export-self-serve
Not scored by this record.
Guest/customer records, loyalty balances or point ledgers, and gift-card liability balances are exportable in machine-readable form by the operator. differentiator
commercial-export-customer-and-loyalty
Not scored by this record.
Contract or documentation specifies a post-termination data retrieval window (a defined number of days during which the operator can still export their data) rather than immediate cutoff. differentiator
commercial-post-termination-export-window
Not scored by this record.
Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator
commercial-data-ownership-clause
Not scored by this record.
Vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A / SAQ P2PE-HW, and names the applicable SAQ.
commercial-pci-p2pe-tokenization
Not scored by this record.
Vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — notably MFA for all access to the cardholder data environment including POS and back-office logins, and (for hosted ordering pages) payment-page script integrity monitoring per Req 6.4.3/11.6.1.
commercial-pci-dss-4-controls
Not scored by this record.
Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.
commercial-privacy-dsar-tooling
Not scored by this record.
Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator
commercial-wcag-kiosk-accessibility
Not scored by this record.
POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator
commercial-dual-pricing-compliant
Not scored by this record.
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 24 values — 17 upheld, 1 downgraded, 6 upgraded. It separately resolved 5 previously unknown values. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| menu-pricing-nested-modifiers | unknown / placeholder | resolve-to-partial | The 2026-08-01 rationale was a never-examined marker. Owner does publish an option editor: help.owner.com 'How do I create a new modifier?' enumerates Display name, Description, Amount, Selection ('the minimum and maximum number of selections required for this option'), Options and allergens, Variation groups ('different versions of a option... like Size or Flavor'), Apply sales tax and Set availability, and 'How do I add modifiers to an item?' shows items taking Option Groups. Min/max and forced selection are therefore documented, and one nested level exists, but the enumerated field set reaches two levels only and no min/max or required flag is documented on variation groups. Partial with that shortfall named. source |
| payments-gift-cards | unknown / placeholder | resolve-to-yes | Never-examined marker, and the capability is fully documented. 'How do gift cards work on Owner.com?' states guests buy digital gift cards from the restaurant's own website, receive a redemption code by email, and redeem 'online at any of your brand's locations, or in store via the Owner Tablet or Owner Dashboard'. 'How do I see all my gift cards and their balances?' documents a dashboard list with recipient, current balance, purchase date and location; the reports catalogue carries Gift Card Purchases and Gift Card Charges. Cross-location, online-channel and balance tracking are all first-party and grade B, so yes. source |
| reporting-pmix-modifier-level | unknown / placeholder | resolve-to-partial | Never-examined marker. The published report catalogue does include a modifier-level report — 'Option Group Sales: Which option groups and options (modifiers) guests choose most' — which is the half of this claim most vendors miss. Against it: the same catalogue names no menu-item PMIX report, describes the modifier report as choice frequency rather than quantity plus gross and net sales, and offers date filtering only ('All reports support date filtering and data export'), with no daypart or revenue-centre dimension. Partial, not yes. source |
| delivery-zone-pricing | unknown / placeholder | resolve-to-partial | The 2026-08-01 rationale was a never-examined marker. The Orders & Delivery collection (14 articles, all read) documents multiple address-driven zone types (radius, zip code, custom polygon) and per-zone money controls in 'How do I cover a portion of the delivery fee for my guests?' — a 'Cost Covered' subsidy and a 'Min Spend' threshold, configured per selected zone under Settings > Orders and delivery > Delivery. But the base fee is courier-set ('Delivery fees vary by provider', Uber Eats $6.45 vs DoorDash $7.00 given as examples), and no per-zone order minimum or quoted promise time exists for standard delivery; restaurant-set zone fees and minimums are documented only for catering ('Add delivery fee tiers based on order subtotal', optional minimum order). Partial with those shortfalls named. source |
| multi-location-price-zones | unknown / placeholder | resolve-to-no | Never-examined marker. This is positive evidence of absence, not silence: the help centre enumerates the whole price surface — a single 'Amount' field per item ('Click Amount and update the price'), a Bulk Price Editor that the vendor itself scopes with 'You can only use the bulk editor at the location level' and 'This feature is not available for Clover or Toast-integrated locations', and, on integrated locations, 'Prices, allergens, and dietary options cannot be overridden and must be changed in your integrated system'. No tier, zone, channel or daypart price construct appears anywhere in the 28-article Menu & Hours collection, and the documented route to a different price elsewhere is a separate per-location item record, which is the duplication the claim excludes. source |
| digital-first-party-web | yes, grade B - The core product: commission-free direct online ordering on | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| commercial-autorenew-terms-published | yes, grade B - Publicly states month-to-month billing with no long-term con | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| commercial-pricing-published | yes, grade B - Both plans carry specific monthly figures and the per-order | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| order-capture-split-merge | no, grade F - No POS product; no in-store check handling. | upgrade-to-partial | OVERTURNED. The standing rationale read 'No POS product; no in-store check handling', and the vendor now ships one: Owner POS, marked New in the site nav, with a Checkout screen in the Kitchen App. Split tender is documented on both sides of the transaction — at checkout, 'To add a tip or split the payment, tap Actions in the top right corner before completing the transaction', and afterwards, 'Split-payment receipts: for an order paid with more than one payment, you'll see a Payment picker. Choose All payments for one receipt covering everything, or pick a single payment (like Visa 4242) to hand that guest their own receipt.' Shortfall, and it is most of the claim: no article documents splitting by item, by seat or by an even N-way division, no dollar/percentage split is described, and nothing in the 141-article help centre describes merging checks or tables, or splitting after partial payment. Partial on split tender alone. source |
| order-capture-offline-order-entry | no, grade F - Cloud ordering layer with no terminal software. | upheld | UPHELD, reason corrected. 'Cloud ordering layer with no terminal software' is falsified — the Owner tablet is a first-party terminal running the Kitchen App, and the Kitchen App's Checkout screen creates orders. But the vendor answers this claim directly and in the negative on its own tablet page: 'Does the tablet work if my internet goes down? The tablet requires an internet connection to process orders and sync with your Owner account. We recommend keeping a reliable Wi-Fi connection in your kitchen.' Order creation is therefore documented as internet-dependent, and the vendor publishes no offline capability matrix of what does and does not work. Grade C — this is a marketing product page, but it is the vendor answering the offline question in its own FAQ. source |
| payments-emv-nfc | no, grade F - Ships no payment terminals. | downgrade-to-unknown | The standing reason, 'Ships no payment terminals', is falsified: Owner ships first-party hardware (a tablet and a Bluetooth receipt printer, both defined as loanable or purchasable equipment in the Restaurant Participation Agreement sections 8 and 9) and markets Owner POS for in-store checkout. What the corpus does not settle is the card-present path. Across 141 help articles and 86 www product pages, 'card reader', 'EMV', 'contactless', 'tap to pay' and 'Stripe Terminal' each occur zero times, and the only payment step documented is 'Enter the guest's payment details' in the Kitchen App phone-order flow — manual entry, which is card-not-present. Whether a first-party reader exists and what it accepts is undocumented, not absent. Unknown, not no. |
| kitchen-station-routing | no, grade F - No KDS product. | upheld | UPHELD, reason corrected. 'No KDS product' is falsified — Owner has stations ('Stations and tablets', and a per-station 'select your station, then click Printing') and its own Owner App page names a KDS. But the station routing surface, enumerated in full by the vendor, is by ORIGIN CHANNEL, not by menu structure: receipts are 'Print orders placed online', 'Print orders from this station', 'Print orders from other stations', with the note 'Each order matches only one of these three'; tickets are 'Print tickets' and 'Print tickets for scheduled orders when placed'. That is the whole enumerated toggle set. No control routes an item, a category, an order type or a revenue centre to a particular station or printer, so the specific mechanism this claim asks for is documented as absent rather than merely unmentioned. source |
| kitchen-expo-consolidation | no, grade F - No KDS product. | upheld | UPHELD, reason corrected. 'No KDS product' is falsified; there is a first-party Kitchen tab on the Owner tablet, and the vendor documents its operations: 'In the side drawer, tap Kitchen', then 'The button is on the ticket card, and also inside the ticket once you open it', with the scoping note 'The Kitchen tab only prints kitchen tickets.' The claim needs multiple prep stations feeding one consolidated expo view whose completion waits on every contributing station bumping its items; the corpus documents no multi-station item split at all (routing is by order origin, not by item), and 'bump' occurs zero times across 141 help articles and 86 product pages. There is one kitchen view per station, not an expo consolidating several. source |
| kitchen-bump-bar-hardware | no, grade F - No KDS or hardware product. | upheld | UPHELD, reason corrected. 'No KDS or hardware product' is falsified — Owner ships kitchen hardware and identifies it precisely: 'What does the Owner kitchen tablet come with? The tablet comes pre-installed with the Owner kitchen app and connects to an Owner printer via Bluetooth. It is a Lenovo Yoga Tab 11 with a built-in stand.' That is a touchscreen tablet and a Bluetooth receipt printer, and the Restaurant Participation Agreement's equipment sections define exactly two categories of Owner-supplied hardware, Tablets (section 8) and Printers (section 9). No bump bar or programmable keypad appears in either the marketed hardware or the contract's equipment definitions, and 'bump bar' occurs zero times corpus-wide. Touch is the documented and only input. source |
| delivery-driver-roster | no, grade F - No native in-house driver module in the published catalog. | upheld | UPHELD, reason sharpened. 'No native in-house driver module in the published catalog' understates what the catalogue does contain: in-house delivery is a supported fulfilment mode with its own zones ('Standard In-House delivery zones') and its own tip rule ('In-house delivery: 100% of the tip goes to the restaurant'). What is absent is the driver as an entity. The vendor draws that line itself: 'Delivery tracking only appears for orders fulfilled by Uber Eats or DoorDash. If you're using your own drivers, tracking won't show up for those orders.' No article gives a driver record, driver clock-in/out, an assignment state, or per-driver run history; 'roster' and 'dispatch' each occur zero times across the 227-document product corpus. In-house delivery is a zone setting, not a driver module. source |
| delivery-dispatch-board | no, grade F - Absent from the published catalog. | upheld | UPHELD, reason corrected. 'Absent from the published catalog' is now measured rather than asserted: the delivery surface is the Orders tab of the Owner app, and what it shows is one third-party courier's progress on one order — 'Assigning driver The order is paid, but no driver has accepted it yet', 'Driver has multiple stops The courier picked up an earlier delivery first and is on a batched route.' Note that the batching there is the marketplace's, performed on the courier's own runs and merely reported to the restaurant; the restaurant assigns nothing. There is no screen listing undispatched orders with driver availability and elapsed time, and no control for assigning two or more orders to one driver as a run. 'Dispatch' occurs zero times across 227 product documents. source |
| labor-clock-in-at-pos | no, grade F - No POS terminal and no labor module. | upgrade-to-partial | OVERTURNED. 'No POS terminal and no labor module' is wrong on both halves. Owner ships a POS, and its printing settings expose a time-clocking feature keyed to the station: 'Time slips (if you use time clocking)' / 'Print time slips on clock in / clock out : prints a time slip automatically each time an employee clocks in and out.' Employees therefore clock in and out at the Owner tablet or POS itself, with no separate time-clock hardware, which is the substance of this claim. Shortfall: the credential is not documented — no article states whether clock-in uses a PIN, a badge or a card — and no timesheet, labour report or approval flow appears in the nine-section Reports catalogue. Partial on the clock-in mechanism alone. source |
| inventory-recipe-bom-costing | no, grade F - No inventory module in the published catalog. | upheld | UPHELD, reason re-measured. The help centre's 38 collections, censused by an href fixpoint that closed at 141 articles, contain no inventory collection, and the Reports catalogue's nine numbered sections contain no inventory or cost report. More than silence, the vendor assigns the task outward: the Product Mix report's stated use is 'Forecast inventory based on what is actually selling' — i.e. inventory is forecast by the operator from sales data, not held and costed inside Owner. 'Recipe' occurs once across 227 product documents, in a customer case study. No ingredient, sub-recipe, plate cost or component-cost recalculation construct exists anywhere in the corpus. source |
| inventory-unit-conversion-yields | no, grade F - No inventory module in the published catalog. | upheld | UPHELD, reason re-measured. The premise is not 'no module named in a catalog' but a censused surface: 38 help collections and 141 articles hold no inventory collection, and the Reports catalogue enumerates its nine sections in full — Sales, Orders, Customers, Sources, Cash Drawer, Marketing, Website, General, Advanced — with no inventory or cost section among them. 'Unit conversion' occurs zero times across the 227-document product corpus, and no purchase, recipe or count unit is stored anywhere; the only quantity Owner records against a menu item is the sold quantity in Product Mix. There is no raw-to-usable conversion or yield/waste percentage to grade. source |
| inventory-count-modes | no, grade F - No inventory module in the published catalog. | upheld | UPHELD, reason re-measured against a closed census rather than a catalog impression. Owner's stock-level vocabulary is availability, not counting: items are marked available or unavailable and can be 86'd from the Owner app, which is a boolean on a menu item. No physical count, spot count, cycle count or variance history appears in any of the 141 help articles, and the Reports catalogue's nine sections include no count or variance report. Caveat recorded rather than hidden: this help centre grew materially in 2026 as Owner POS shipped, so this is an absence over a surface that is actively expanding — but all three inventory constructs this claim needs are missing together, which is a product shape, not a documentation gap. source |
| reporting-eod-closeout | no, grade F - No cash drawer, tender types or EOD reconciliation. | upgrade-to-partial | OVERTURNED. The standing rationale — 'No cash drawer, tender types or EOD reconciliation — that stays with the POS' — is falsified on all three counts by the vendor's own reports catalogue. Cash drawer: an entire numbered section, 'Cash Drawer View data about your cash drawer sessions. You can also filter by individual device', whose Cash Drawer History shows 'Opening balance, cash sales, refunds, and paid in/out per session'. Tender types: 'Payments By Type Sales, taxes, tips, and fees broken down by payment method'. The remaining components exist as named reports too — Total Sales, Taxes, Tips, Refunds, Coupon Usage, and an Explore Orders view giving 'subtotal, tax, tip, discounts, fees, and net sales'. Shortfall, and it is why this is not a yes: these are separate reports on separate screens. No article describes a single daily close-out or EOD document assembling them, and no expected cash deposit figure is reconciled anywhere. Partial. source |
| hardware-os-platforms | no, grade F - No client terminal software; branded app platforms not specified with minimum versions. | upgrade-to-partial | OVERTURNED. Both halves of the standing rationale are wrong: there is client terminal software (the Kitchen App on the Owner tablet), and the app platforms ARE specified with minimum versions — 'Which devices does the Owner App support? Any iPhone running iOS 15 or later and any Android phone on Android 11 or later.' The in-restaurant hardware is named to the model as well: 'It is a Lenovo Yoga Tab 11 with a built-in stand.' Shortfall: that is one device model, not a spec floor — the vendor states no minimum OS version, memory or screen size for the tablet or the POS app, publishes no supported-device list a restaurant could check its existing hardware against, and names no Windows, Linux or browser client. Documented for the operator phone app, undocumented for the terminal. Grade C: both sources are marketing product pages. source |
| hardware-offline-mode | no, grade F - Cloud-only; no terminals. | upheld | UPHELD, reason corrected. 'Cloud-only; no terminals' is half wrong — Owner ships a terminal — but the offline verdict survives on the vendor's own answer about that terminal: 'Does the tablet work if my internet goes down? The tablet requires an internet connection to process orders and sync with your Owner account. We recommend keeping a reliable Wi-Fi connection in your kitchen. The app updates automatically whenever it is connected.' Orders are not taken, kitchen printing does not proceed and cash sales are not recorded offline, and the vendor publishes no degradation matrix naming which functions survive. The printer is Bluetooth-paired to the tablet, but the tablet is the thing that requires the connection. source |
| hardware-kds | no, grade F - No KDS product. | upgrade-to-partial | OVERTURNED. 'No KDS product' is contradicted by the vendor naming one — the Owner App page states that changes 'appear on the dashboard, KDS, and POS within seconds' — and by a documented first-party kitchen display: a Kitchen tab in the Owner tablet's side drawer showing ticket cards that open ('The button is on the ticket card, and also inside the ticket once you open it'), a Kitchen Status control that switches the station between Normal and Busy, and item labels that print 'when an order fires to the kitchen'. It is first-party, on Owner's own hardware, not an integration dependency. Shortfall: touch only, with no bump bar or keypad; no station routing by item or category (printing routes by order origin); and no course or fire timing — 'course' and 'fire' as kitchen terms occur zero times across 227 product documents. Partial, not yes. source |
| reliability-offline-order-entry | no, grade F - No on-terminal software to degrade to. | upheld | UPHELD, reason corrected. 'No on-terminal software to degrade to' is false — the Kitchen App is on-terminal software that takes phone and in-store orders — so the verdict now rests on the vendor's direct statement about that terminal instead: 'The tablet requires an internet connection to process orders and sync with your Owner account.' Order entry, ticket routing and check printing all run through the tablet's connection to the Owner account, so none of the three continues when the connection is lost. source |
| reliability-offline-kds-printing | no, grade F - No first-party kitchen routing. | upheld | UPHELD, reason corrected. 'No first-party kitchen routing' is falsified — Owner runs a first-party Kitchen tab and drives an Owner-branded Bluetooth printer from it, with automatic ticket and item-label printing when an order fires. The offline half stands on the vendor's own tablet FAQ: 'The tablet requires an internet connection to process orders and sync with your Owner account.' Kitchen display and kitchen printing are both downstream of an order the tablet cannot receive offline; the printer's Bluetooth link to the tablet does not change that, and no article claims any queued or degraded kitchen mode. source |
| reliability-printer-fallback | no, grade F - No first-party printer management. | upheld | UPHELD, reason corrected — and the old reason was badly wrong. 'No first-party printer management' is falsified by an entire Printer collection under Hardware: pairing an Owner TSP-100 over Bluetooth, a Station printer list reached by 'Settings , then Station , then Printing', a Test Print, per-station auto-print toggles, copy counts of 1 to 5, font sizes, and item-label printing. That article enumerates the complete printing settings surface, and no backup or failover printer can be configured in it: there is no secondary printer field, no rule for an unreachable printer, and no alert. The only recovery documented anywhere is manual and human — reprinting on demand from the Kitchen or Orders tab, and a troubleshooting step to 'confirm it's still paired'. Automatic failover with staff alerting is absent from the surface that would define it. source |
| commercial-hardware-purchase-outright | no, grade F - Ships no terminals, KDS screens or printers at all. | upgrade-to-partial | OVERTURNED. 'Ships no terminals, KDS screens or printers at all, so there is nothing to purchase and nothing leased' is contradicted by two dedicated sections of Owner's own contract. Tablets and Printers are each supplied under a loan or a purchase model: 'Owner may charge Business a monthly per-Loaned Tablet fee as indicated on the Pricing Page', and 'If Business chooses to purchase any Tablets provided to Business by Owner, and Owner provides an option for Business to do so, Owner may charge a fee per Purchased Tablet... as agreed by Owner and Business at the time of that purchase', with the parallel construction for Printers in section 9. What supports partial rather than yes: purchase is at Owner's discretion ('and Owner provides an option for Business to do so') and priced 'as agreed... at the time of that purchase', so there is no published hardware price — the Pricing Page the contract points to publishes only the $249 and Flat Rate subscription tiers and names no tablet, printer or setup fee. What supports partial rather than no: the loan alternative is explicitly monthly and terminates with the agreement ('Loaned Tablets are loaned, not sold'; returned within five business days on termination), so no multi-year hardware lease is mandatory. source |
| reporting-pmix-modifier-level | partial, grade B - rationale asserted the catalogue 'names no menu-item PMIX report' | upheld | Value unchanged at partial; the standing rationale is falsified and replaced. That rationale said the report catalogue 'names no menu-item PMIX report' — it now does, and there is a dedicated article for it. Product Mix is nested the full depth this claim asks for: 'Menu > Category > Item > Option group > Option', and 'For each row you see: Quantity sold: how many times it sold. Average price: the average it sold for. Gross sales: the total revenue it brought in.' Item level and modifier level are therefore both covered, with quantity and gross sales, and the older Option Group Sales report survives alongside it. Shortfall, and it is why this stays partial: the report gives average price where the claim asks for net sales, and the only filter documented is a date range ('Choose a date range, and export the data if you want to dig in elsewhere') — no daypart and no revenue-centre dimension exists here or anywhere in the nine-section Reports catalogue. source |
Sources
Every URL this record cites. 38 in total.
- https://www.owner.com/pricing
- https://help.owner.com/en/collections/14143525-menu-hours
- https://help.owner.com/en/articles/11833508-how-do-i-create-a-new-modifier
- https://help.owner.com/en/articles/11833491-how-do-i-add-modifiers-to-an-item
- https://help.owner.com/en/articles/11833179-how-do-i-change-a-menu-item-s-price
- https://help.owner.com/en/articles/14709107-how-do-i-customize-my-integrated-menu-for-online-ordering
- https://help.owner.com/en/articles/11832729-how-do-gift-cards-work-on-owner-com
- https://help.owner.com/en/articles/11833430-how-do-i-see-all-my-gift-cards-and-their-balances
- https://help.owner.com/en/articles/13950704-what-reports-are-available-in-my-owner-dashboard
- https://help.owner.com/en/articles/15139944-how-do-i-turn-a-menu-on-or-off
- https://help.owner.com/en/articles/11833380-how-do-i-issue-a-refund-or-add-a-charge-to-an-order
- https://www.owner.com/sitemap.xml
- https://www.owner.com/partner-with-owner
- https://www.owner.com/pos-integrations
- https://www.owner.com/reporting-analytics
- https://help.owner.com/en/collections/14143715-orders-delivery
- https://help.owner.com/en/articles/11832907-how-do-i-add-a-delivery-zone-radius-serviceable-area
- https://help.owner.com/en/articles/14502948-how-do-i-cover-a-portion-of-the-delivery-fee-for-my-guests
- https://help.owner.com/en/articles/15033590-how-do-i-turn-on-delivery-for-my-restaurant
- https://help.owner.com/en/articles/12834416-how-do-i-set-delivery-zones-for-catering
- https://help.owner.com/en/articles/12834421-how-to-add-tiered-delivery-fees-for-catering
- https://help.owner.com/en/articles/12632121-can-i-update-prices-for-multiple-menu-items-at-once
- https://help.owner.com/en/articles/12243716-can-i-copy-an-existing-menu
- https://help.owner.com/en/collections/14143726-dashboard
- https://help.owner.com/en/collections/14143731-integrations
- https://help.owner.com/en/articles/16419487-print-receipts-and-tickets-on-your-owner-tablet-or-pos
- https://www.owner.com/kitchen-tablet
- https://help.owner.com/en/articles/16419469-manage-your-printing-settings
- https://help.owner.com/en/articles/15485357-how-do-i-track-a-third-party-delivery-on-the-owner-app
- https://help.owner.com/en/articles/16419715-product-mix-report
- https://www.owner.com/mobile
- https://www.owner.com/restaurant-participation-agreement
- https://www.owner.com/pos
- https://help.owner.com/en/articles/16562632-print-item-labels
- https://help.owner.com/en/articles/11833255-how-do-i-connect-the-owner-tablet-and-printer-for-the-first-time
- https://help.owner.com/en/articles/11833396-how-do-i-log-into-the-kitchen-app-on-the-owner-tablet
- https://help.owner.com/en/articles/13922131-how-do-i-take-a-phone-order-in-the-kitchen-app
- https://help.owner.com/en/articles/16738749-voids-report