Vendors / Mainstream commercial restaurant POS
Epos Now
UK-headquartered SMB hospitality/retail POS with an app-store model and the only genuinely self-serve developer documentation in this batch — a public REST reference (v2/v4) with documented webhook event types — while its US "pricing" page is a lead-capture form advertising a discounted hardware bundle ("WAS $1049, NOW FROM $249") rather than any published software subscription or processing rate.
scored live legacy rubric
- Claims in scope
- 278
- Scored
- 45
- Assessed
- 43
- Unknown
- 235
- Not applicable
- 36
- Values challenged
- 5
unknown, never as no.Identity
- Owner
- Epos Now Ltd (UK, private; ownership structure not verified here)
- Who it is for
- UK and international small hospitality and retail merchants — single-site and very small multi-site, self-serve leaning
- Site
- https://www.eposnow.com/us/hospitality/
Pricing
transparency: unknown · unit: unknown for software; hardware quoted as a one-off bundle price · processor lock-in: unknown
- Software
- US pricing page publishes no software subscription, per-terminal or card-processing rate — only a hardware bundle promotion ("WAS $1049, NOW FROM $249", up to 77% off) behind 15+ contact forms and a sales phone number.
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
The payment screen documents one split mode only: "choose to split by cover option / Choose the number of covers you would like to split the order by" (even N-way). No split by item, by seat, or by arbitrary amount is described. Merging exists as the separate Move/Merge feature (enabled via the Epos Now Labs app), which moves individual items or partial quantities between tables, but its guide states "the partial move of tables doesn't support moving partially paid bills or promotions". https://support.eposnow.com/s/article/Split-bill-by?language=en_US · retrieved 2026-08-03
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
Epos Now publishes an offline scope, but it covers the payment leg only. Offline Mode "allows your Epos Now card terminal to accept transactions even without an active internet connection"; it is "automatically switched on when no WiFi or 4G network is detected during Standalone Mode", card data is "securely stored on the card terminal" and processed on reconnection, with default caps of 10 stored transactions and a low per-transaction ceiling, and "your business assumes full responsibility for any declined transactions, expired payments, chargebacks, or disputes". Named shortfalls against this claim: nothing in the 215-article knowledge base states what the till itself can do with the internet down - no offline order-entry, modifier or cash-tender scope is published anywhere - and the send-to-kitchen half is contradicted, since the KDS guide states flatly "An internet connection is required" and the network guide opens "Any device running Epos Now requires a strong and stable internet connection to function effectively." The documented fallback for a total outage is Epos Now Standalone, an unintegrated card-terminal path that bypasses the till and "will not generate a payout reference on the Transaction Report". https://support.eposnow.com/s/article/Epos-Now-Payments-Offline-Payments?language=en_US · retrieved 2026-08-04
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
CLAIM: accepts future-dated or scheduled orders with a per-channel lead time and injects them into the make queue at a computed fire time rather than on receipt. VERDICT: partial. Pre-orders with per-channel lead times exist, but only in the Yoello-powered Epos Now Order & Pay add-on, only for later the same day, and no fire-time injection is documented. EVIDENCE: Epos Now Order & Pay - Step 5: Settings (https://support.eposnow.com/s/article/Epos-Now-Order-Pay---Step-5?language=en_US). The August note recorded it as a title-only stub; it now renders in full: "Pre-Ordering for Delivery & Collection - This toggle allows you to control whether customers can place an order before you are open for that day, to be delivered or collected within your opening times. Please note this is currently only available for orders to be placed later that same-day and not multiple days in advance." Lead times are set per channel: "Preparation Time ... applicable for both Dine-in and Collection orders. With collection, the prep time determines the next available time slot for collection. Collection slots are every 15 mins", and "Delivery Time ... will also determine the next available time slot for delivery orders. For example, if the Delivery Time is set at 45mins then the next available time slot that a customer will be able to select for delivery will be in 45mins time." Step 7 (https://support.eposnow.com/s/article/Step-7-Order-Management-and-Reporting?language=en_US) lists the order states "Placed - orders have been made and not yet accepted by you. Accepted - orders have been accepted and are sitting in your 'Open' tab"; its Order Line Item Detail Report includes "Delivery Time, Collection Time". Step 1 calls the product "Epos Now Order & Pay, powered by Yoello", and release note 2.124 says "Our partners at Yoello". For contrast, the third-party FoodHub guide (https://support.eposnow.com/s/article/FoodHub?language=en_US) says "All scheduled or pre-orders placed via FoodHub are immediately sent to Epos Now along with the scheduled delivery/pickup time", i.e. sent on receipt, not at a fire time. SHORTFALL: a partner-powered add-on (Yoello), not the core POS; same-day only; no page describes holding an order and releasing it to the till or KDS at a computed fire time. SURFACES 2026-09-16: support.eposnow.com (Salesforce Experience Cloud) re-censused from the live sitemap-topicarticle-1.xml = 258 slugs (was 257). A guest Aura call returns no body field, so every article was rendered in headless Chromium over CDP and the LWC article layout text captured: 238 bodies held; 20 sitemap slugs (19 Spanish plus Epos-Now-Delivery-Deliverect) render the "Oops! We can’t seem to find that page" error under both en_US and es. The Salesforce sitemap is a floor, not a census. Also read: all 117 release notes listed at www.eposnow.com/us/release-notes/; 205 eposnow.com store, app and hardware pages; the current developer portal api.eposnowhq.com/docs/ (MkDocs, 21 nav pages) with its 7 anonymous OpenAPI 3.0.1 module specs (api.eposnowhq.com/swagger/<module>/v4/swagger.json, 242 paths); and the legacy developer.eposnowhq.com (18 nav pages plus the docs/v4/json Swagger 2.0 spec, 133 paths). Wayback CDX for help.eposnow.com, eposnow.zendesk.com and developer.eposnowhq.com answered 503 "Temporarily Offline" on every attempt, so retired Zendesk articles were NOT checked. Retrieved 2026-09-16. https://support.eposnow.com/s/article/Epos-Now-Order-Pay---Step-5?language=en_US · 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
The card-machines page covers the terminal range (Link, Air, Pro+) with a collective statement: "All our machines support contactless payments, chip cards, and mobile wallets", and "You can also use Epos Now Payments to accept eWallets for the same rate, including Apple Pay, Google Pay, and Samsung Pay". The Air device page confirms per-device: "You can take payments through chip and pin, contactless cards using tap to pay" and "Payments can be made via digital wallets for the same rate, including Apple Pay, Google Pay, and Samsung Pay" (https://www.eposnow.com/us/payment-processing/air-device/). Grade C because these are first-party feature pages; the help-centre terminal setup guides (AMS1 Air, Pro Saturn S1F2, Payments Lite) cover assembly, network and boarding only and never enumerate acceptance methods. https://www.eposnow.com/us/payment-processing/card-machines/ · retrieved 2026-08-04
Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. differentiator
payments-softpos-tap-to-pay
Not scored by this record.
Vendor ships a handheld that takes EMV/NFC payment at the table, including tip prompt and check splitting, without carrying the card away.
payments-pay-at-table
Not scored by this record.
Guest can scan a QR code on the printed check or table tent to view and pay the check from their own phone, with the payment closing the check in the POS automatically. differentiator
payments-qr-guest-pay
Not scored by this record.
Supports both pre-auth-then-tip-adjust and on-device tip prompt flows, with a documented batch/adjust window and a manager screen for unadjusted tips.
payments-tip-adjust
Not scored by this record.
Configurable tip pooling and distribution rules (by hours worked, sales, role percentage, or points) that produce a per-employee tip allocation exportable to payroll. differentiator
payments-tip-pooling
Not scored by this record.
Card payments can be captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. differentiator
payments-offline-store-and-forward
Not scored by this record.
Vendor publicly documents who bears the loss when a stored offline transaction declines on reconnect, and surfaces a post-reconnect report of failed offline payments. differentiator
payments-offline-decline-liability
Not scored by this record.
First-party gift cards with real-time balance tracking, redeemable across every location in the group and through the online-ordering channel.
payments-gift-cards
Epos Now has no first-party gift card. Its own guide for issuing and redeeming vouchers is a workaround built on Customer Credit: "Name the customer with the same code that the physical voucher is named with", load credit against that customer record, then redeem by selecting Customer Credit as the tender and "record the available balance on the physical voucher or staple the receipt to it". Real gift-card programmes are delivered by third-party AppStore integrations (Factor4, VoucherCart), each requiring credentials issued by that vendor. https://support.eposnow.com/s/article/Using-Customer-Credit-as-a-Voucher?language=en_US · retrieved 2026-08-03
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
Void and delete are gated by discrete staff-role permissions - "Delete Unordered Items" and "Void Ordered Items and Delete Unordered Items" - and the End of Day plus the Reporting > Auditing > Void/Delete Lines report show every void and delete with staff member, till and time; Refunds, Discounts and No Sales have their own auditing reports filterable by location, device and staff, and refunds require a reason code from a configured list. Shortfall: the docs describe permission-gating of the operator only, with no manager-PIN override or approval step, so no separate approver is ever recorded, and no immutability guarantee is stated for these reports. https://support.eposnow.com/s/article/Performing-a-VOID?language=en_US · retrieved 2026-08-03
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
Routing exists and the merchant configures it without vendor involvement, but the only routing key is the product category. The order-printing guide states the mechanism in full: "Products are contained in Categories which are assigned to order channels. Printers then print from these order channels. When an order is placed, tickets print to any printer assigned to the relevant order channel" - example given, the "Burgers" category assigned to the "KITCHEN" channel. The KDS guide reuses the same key: before use, "all sellable products are correctly assigned to a category, and these categories are correctly assigned to an order printer/display (e.g., KITCHEN, BAR)", and the per-screen Order Views setting lets you "select which product types the KDS will display (e.g., only KITCHEN categories)". Named shortfalls: no per-item routing override (an item routes wherever its category routes), no routing by order type - eat-in, takeaway and delivery only drive display colour coding under Display Appearance, not the destination - and no revenue-centre or seating-area routing axis appears in either guide. https://support.eposnow.com/s/article/Order-Printing-Setup?language=en_US · retrieved 2026-08-04
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
329th: verdict change on re-reading the two surfaces against the claim's two conjuncts, plus a re-census. CONJUNCT 1 (an expo screen consolidating items from multiple prep stations into one order view) IS vendor-claimed: KDS store page (grade C) 'Reduce waste with combined order view in expeditor mode'; 'Multiple station view and order grouping'; 'allow chefs to see new orders from multiple stations'; 'Whether you prefer a single prep station, an expeditor view, or separate screens for the bar and kitchen, you can easily configure it'; 'Expeditor view: This view provides a summarised overview of all dishes on order.' The help centre (grade B) supplies the station mechanism -- 'Order Routing: Seamlessly direct orders to different KDS stations' and 'Order Views: You can select which product types the KDS will display (e.g., only KITCHEN categories)' -- and the unfiltered counterpart 'Summary View ... showing how many of each item have been ordered' (https://support.eposnow.com/s/article/Kitchen-Display-Screens?language=en_US). CONJUNCT 2 IS NOT MET AND THAT IS THE NAMED SHORTFALL: the only completion rule Epos Now publishes is per-screen -- 'Mark individual items as complete by checking them off, and once all items in a ticket are marked, the entire order will disappear from the queue' -- and since each KDS shows only its own categories, nothing states that an order stays open until every contributing station has bumped; 'Inter-KDS communication improvements' (2.106: 'completely revamping the way KDS systems communicate with each other') and 'multi-KDS syncing' (2.119, 2.122) are performance/reliability work with no cross-station completion rule. Epos Now's Summary/Expeditor view is an ITEM-COUNT digest, not an order-level all-stations-bumped gate. Re-census 2026-09-18: support.eposnow.com sitemap index is at /s/sitemap.xml (6 sub-sitemaps; sitemap-topicarticle-1.xml 334 locs = the SAME 258 unique article slugs as the 16 Sep pass, zero added, zero removed, and sitemap-topicarticle-weekly.xml lists 5 articles all last modified 2025-06 to 2026-06), so no new or updated KB article exists to change this. Tokenised controls over the 258 KB bodies + 117 release notes + 410 marketing pages + 106 API/dev-portal files: expo 0, runner 0, 'prep station' 2 (both the same store page), bump 5 (all the 2.93/2.104 digital bump bar), station 5. Retrieved 2026-09-18. https://www.eposnow.com/uk/store/software/apps/kitchen-display-system/ · retrieved 2026-09-18 adversarially verified
Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator
kitchen-course-firing
Not scored by this record.
Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator
kitchen-prep-time-pacing
Not scored by this record.
Kitchen load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator
kitchen-order-throttling
Not scored by this record.
Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator
kitchen-channel-pause-propagation
Not scored by this record.
Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator
kitchen-order-ready-callback
Not scored by this record.
KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.
kitchen-bump-bar-hardware
The article's Compatibility and Requirements section enumerates the supported KDS hardware: "compatible with Android and Windows devices, including monitors, tablets, and mobile phones. For maximum efficiency, touchscreen devices are recommended", plus Epos Now's own 21.5-inch Android touch screen. Every documented interaction is touch (check items off, Recall Order, Move Ticket, hamburger Summary View). No bump bar or programmable keypad is offered and no supported models are listed. https://support.eposnow.com/s/article/Kitchen-Display-Screens?language=en_US · retrieved 2026-08-03
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
CLAIM: a native in-house driver module (drivers as entities, clock-in, run state, per-driver history). VERDICT: unknown (unchanged). Re-checked against the full rendered corpus. In the 238 help-centre bodies, all 16 tokenised driver/drivers hits but one are printer or device drivers (POISON: Bixolon, Star TSP, POS80Gx, the "seagull driver wizard", the Global Payments "Jungo driver"). The exception is the consumer FAQ heading "I placed an order but there were no delivery drivers available" (https://support.eposnow.com/s/article/Yoello-Order-Pay-Customer-Orders-Refunds?language=en_US), which sends the customer back to the venue. In the 117 release notes the only hit is "Improved drivers for the Countertop/Duo Countertop built-in printer" (3.19). The 7 OpenAPI module specs (242 paths) contain no "driver" token; staff and clocking only. Delivery goes through Epos Now Delivery powered by Otter or Deliverect, FoodHub, and Order & Pay (Yoello), whose Step 5 settings cover radius, fees and delivery time but no driver. The corpus is not a census (the Salesforce sitemap is a floor), so this is not a no. SURFACES 2026-09-16: support.eposnow.com (Salesforce Experience Cloud) re-censused from the live sitemap-topicarticle-1.xml = 258 slugs (was 257). A guest Aura call returns no body field, so every article was rendered in headless Chromium over CDP and the LWC article layout text captured: 238 bodies held; 20 sitemap slugs (19 Spanish plus Epos-Now-Delivery-Deliverect) render the "Oops! We can’t seem to find that page" error under both en_US and es. The Salesforce sitemap is a floor, not a census. Also read: all 117 release notes listed at www.eposnow.com/us/release-notes/; 205 eposnow.com store, app and hardware pages; the current developer portal api.eposnowhq.com/docs/ (MkDocs, 21 nav pages) with its 7 anonymous OpenAPI 3.0.1 module specs (api.eposnowhq.com/swagger/<module>/v4/swagger.json, 242 paths); and the legacy developer.eposnowhq.com (18 nav pages plus the docs/v4/json Swagger 2.0 spec, 133 paths). Wayback CDX for help.eposnow.com, eposnow.zendesk.com and developer.eposnowhq.com answered 503 "Temporarily Offline" on every attempt, so retired Zendesk articles were NOT checked. Retrieved 2026-09-16. || 322nd: NEW SURFACES (322nd): crt.sh (322nd): eposnow.com 1,287 cert rows / 27 names; eposnowhq.com 3,889 rows / 677 names (632 under *.eu-01, mostly sandbox/ephemeral branch hosts; production app hosts hide behind *.production.eu-01 and *.eposnowhq.com wildcards, which answer a 146-byte 404 catch-all). 64 non-sandbox names probed. Live production SPAs: reporting.eposnowhq.com (CRA; /asset-manifest.json lists 525 JS chunks and all 525 .js.map files return 200: 254 own source files, a reporting/data-downloader/tronc app) and setup.eposnowhq.com (onboarding wizard); account/money/onboarding/organisations/products.eposnowhq.com redirect server-side to OIDC login; www.eposnowhq.com back office and Pages/Till/DownloadApp.aspx redirect to /sso/Auth/SignIn; androidupdater.production.eu-01 does not answer; drivers/backofficecdn/cdn/static.eposnowhq.com 403 (refusals). Order & Pay is 'powered by Yoello' (https://support.eposnow.com/s/article/Epos-Now-Order-Pay---Step-1?language=en_US: "Epos Now Order & Pay, powered by Yoello"; merchants log into eposnow.yoello.com). PUBLIC SOURCE MAPS on both Yoello production apps: eposnow.yoello.com merchant dashboard (https://eposnow.yoello.com/static/js/main.26980a47.chunk.js.map, 949 own sources; services/generateConsumerURLs.ts: prod: "https://pay.yoello.com", venue links https://pay.yoello.com/v/{venue_nickname}) and the consumer ordering app pay.yoello.com (/asset-manifest.json lists 73 JS chunks, all 73 .js.map 200, nonsense-map control 404; 2,146 sources, 715 own). Tokenised case-insensitive controls driver(s)/rider(s)/courier(s)/stuart/'uber direct'/kitchen over the dashboard (949 files), consumer app (715 files) and reporting app (254 files): all 0. 'dispatch' 500 / 582 / 1 hits are Redux dispatch() calls (POISON); 'dispatched' 1 is a snackbar code comment. These are Yoello's and one Epos Now reporting app, not a census of Epos Now (back office is login-gated; Order & Pay by Otter is an alternative channel). VERDICT: still unknown. Retrieved 2026-09-17. || 329th: 329th: NEW SURFACES, none carried the claim, and the public corpus is now PROVABLY not a census. (1) Google Play publisher census (https://play.google.com/store/apps/developer?id=EPOS+NOW, 2026-09-18) lists exactly ONE Epos Now Android app -- com.eposnow.till -- so there is no separate driver/dispatch app to find. (2) That APK (v1.1.107, the version Play currently serves, 20.1 MB, 7 dex + resources.arsc, 367,270 extracted strings) was unpacked: tokenised controls driver/drivers/courier/rider/dispatch/delivery over every string find only printer drivers (Bixolon/Star/Sunmi/PAX/'getPrinterDriverVersion') and androidx 'view_tree_on_back_pressed_dispatcher_owner' (POISON) -- but the app is a WebView shell over the cloud till (strings 'https://www.eposnowhq.com', 'Lcom/eposnow/till/WebViewClient;'), so this absence bounds only the app's NATIVE layer (payments via Optomany/CreditCall ChipDNA, peripherals, order printing) and cannot bound till features at all. (3) The iOS publisher census (itunes.apple.com/lookup?id=907427785&entity=software) is 2 apps: Epos Now POS Till (v1.2.20, last updated 2023-10-16) and Epos Now My Business (the Adyen-powered banking app); all 10 till screenshots pulled at 1000x0w are 2014-era composites with no delivery surface. (4) THE KB IS NOT A CENSUS, MEASURED: the 258 sitemap slugs are unchanged since 16 Sep, and the href fixpoint inside the 258 article bodies references only 4 slugs outside the sitemap -- 3 (Orders, POS80Gx-Ethernet-FAQ-s, Epos-Now-My-Business) return the same 104 KB 404 shell as a nonsense control, but Android-Online-Order-Utility returns a 550-byte SSO redirect to /services/auth/sso/eposnow_oidc, i.e. a LOGIN-GATED article; the till APK also names a gated topic id (https://support.eposnow.com/s/topic/0TO3X000000VRzSWAW/printer, also an SSO redirect) that is absent from the 93-topic public sitemap. Guest Salesforce Knowledge REST is closed here (support.eposnow.com/services/data/v59.0/support/knowledgeArticles = 401 INVALID_SESSION_ID; /s/... = the SPA shell). With gated ids present, no `no` may be published. Retrieved 2026-09-18. adversarially verified
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
CLAIM: a dispatch screen showing undispatched orders, driver availability and elapsed time, with multi-order run batching. VERDICT: unknown (unchanged). No dispatch, run or driver-assignment construct appears in the 238 rendered help-centre bodies, the 117 release notes, or the 7 OpenAPI module specs (242 paths). The single tokenised "dispatched" hit in the help centre is a card reader being shipped (POISON: "to get your card reader dispatched"), the release notes have none, and every "driver" hit is a printer driver except one Yoello consumer FAQ. First-party delivery surfaces are Order & Pay (Yoello) Step 5 (delivery radius, fees by distance band, delivery time slots) and Step 7 order history ("filter the order history page by dine-in, home delivery, collection"). Third-party ones are Epos Now Delivery powered by Otter or Deliverect; the "Order Manager" in the Otter guide is Otter's own tablet app. No page states the limitation, and the Salesforce sitemap is a floor, not a census. SURFACES 2026-09-16: support.eposnow.com (Salesforce Experience Cloud) re-censused from the live sitemap-topicarticle-1.xml = 258 slugs (was 257). A guest Aura call returns no body field, so every article was rendered in headless Chromium over CDP and the LWC article layout text captured: 238 bodies held; 20 sitemap slugs (19 Spanish plus Epos-Now-Delivery-Deliverect) render the "Oops! We can’t seem to find that page" error under both en_US and es. The Salesforce sitemap is a floor, not a census. Also read: all 117 release notes listed at www.eposnow.com/us/release-notes/; 205 eposnow.com store, app and hardware pages; the current developer portal api.eposnowhq.com/docs/ (MkDocs, 21 nav pages) with its 7 anonymous OpenAPI 3.0.1 module specs (api.eposnowhq.com/swagger/<module>/v4/swagger.json, 242 paths); and the legacy developer.eposnowhq.com (18 nav pages plus the docs/v4/json Swagger 2.0 spec, 133 paths). Wayback CDX for help.eposnow.com, eposnow.zendesk.com and developer.eposnowhq.com answered 503 "Temporarily Offline" on every attempt, so retired Zendesk articles were NOT checked. Retrieved 2026-09-16. || 322nd: NEW SURFACES (322nd): crt.sh (322nd): eposnow.com 1,287 cert rows / 27 names; eposnowhq.com 3,889 rows / 677 names (632 under *.eu-01, mostly sandbox/ephemeral branch hosts; production app hosts hide behind *.production.eu-01 and *.eposnowhq.com wildcards, which answer a 146-byte 404 catch-all). 64 non-sandbox names probed. Live production SPAs: reporting.eposnowhq.com (CRA; /asset-manifest.json lists 525 JS chunks and all 525 .js.map files return 200: 254 own source files, a reporting/data-downloader/tronc app) and setup.eposnowhq.com (onboarding wizard); account/money/onboarding/organisations/products.eposnowhq.com redirect server-side to OIDC login; www.eposnowhq.com back office and Pages/Till/DownloadApp.aspx redirect to /sso/Auth/SignIn; androidupdater.production.eu-01 does not answer; drivers/backofficecdn/cdn/static.eposnowhq.com 403 (refusals). Order & Pay is 'powered by Yoello' (https://support.eposnow.com/s/article/Epos-Now-Order-Pay---Step-1?language=en_US: "Epos Now Order & Pay, powered by Yoello"; merchants log into eposnow.yoello.com). PUBLIC SOURCE MAPS on both Yoello production apps: eposnow.yoello.com merchant dashboard (https://eposnow.yoello.com/static/js/main.26980a47.chunk.js.map, 949 own sources; services/generateConsumerURLs.ts: prod: "https://pay.yoello.com", venue links https://pay.yoello.com/v/{venue_nickname}) and the consumer ordering app pay.yoello.com (/asset-manifest.json lists 73 JS chunks, all 73 .js.map 200, nonsense-map control 404; 2,146 sources, 715 own). No dispatch screen: tokenised controls driver(s)/rider(s)/courier(s)/dispatch board over 1,918 own source files of the three apps find only Redux dispatch() calls (POISON: 500 in the dashboard, 582 in the consumer app, 1 in reporting) and one code comment 'before the call is dispatched'. Not a census of Epos Now's back office (login-gated). VERDICT: still unknown. Retrieved 2026-09-17. || 329th: 329th: same new surfaces as delivery-driver-roster, same result. The store-level Android till APK (com.eposnow.till v1.1.107, the version Google Play serves, 20.1 MB, 367,270 strings) holds no dispatch, run-batching or driver-assignment construct -- the only 'dispatch' tokens are androidx 'view_tree_on_back_pressed_dispatcher_owner' / 'view_tree_navigation_event_dispatcher_owner' (POISON) -- but the till UI is a remote WebView on www.eposnowhq.com, so the APK bounds only the native payments/peripheral/order-printer layer and cannot bound till screens. Google Play publisher census: one Epos Now app total. Apple publisher census: two, neither a dispatch app. The support KB is unchanged since 16 Sep (258 unique slugs from /s/sitemap-topicarticle-1.xml, 334 locs incl. language variants; weekly sitemap lists 5 articles, newest lastmod 2026-06-22) and is demonstrably NOT a census: one article slug referenced from inside the KB bodies (Android-Online-Order-Utility) and one topic id found in the APK (0TO3X000000VRzSWAW) both return SSO redirects rather than content, and guest Salesforce Knowledge REST 401s. Retrieved 2026-09-18. adversarially verified
Dispatch includes a live map view with geocoded stops and system-generated route sequencing (turn order optimization) for a multi-stop run, not just a static address list. differentiator
delivery-route-map
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
CLAIM: each delivery zone has its own delivery fee, order minimum and quoted promise time, applied automatically from the validated customer address. VERDICT: partial. The Yoello-powered Epos Now Order & Pay add-on checks the customer's postcode and charges delivery FEES by distance band, but the order minimum and promise time are single venue-wide values, not per zone. EVIDENCE: Epos Now Order & Pay - Step 5: Settings (https://support.eposnow.com/s/article/Epos-Now-Order-Pay---Step-5?language=en_US): "Delivery Radius- this is the maximum distance to which you travel for deliveries in km. When a customer accesses the delivery menu, they are prompted to enter their postcode to see if the venue is within reach. If the customer is within the radius set then this is confirmed ... If the customer is outside the radius set then they will see an error message letting them know they cannot order for delivery". Also: "if the customer lives between 0.5 km and 2 km away from your venue, they will be charged £1.00. If they live between 2 km and 4 km, they will be charged £2.50. And if they live over 4 km away, they will be charged £5.00. If this customer lived less than 0.5 km away, they will be charged the standard account delivery fee". Release note 2.124 (https://www.eposnow.com/us/release-notes/epos-now-2-124/): "Delivery Fees by Distance - Instead of having just 1 delivery fee, we have improved the delivery fee feature to have multiple fees by distance (km)." The same Step 5 defines only one "Delivery Minimum Order Value - Customers will be unable to place an order for delivery if their cart value is less than the minimum order value" and one "Delivery Time - this will display to customers ... how long their order is likely to take to be delivered". SHORTFALL: only the fee varies, by radial distance bands rather than drawn zones; the order minimum and promise time do not vary by zone; and it comes through the partner-powered Order & Pay (Yoello) add-on, not the core till. SURFACES 2026-09-16: support.eposnow.com (Salesforce Experience Cloud) re-censused from the live sitemap-topicarticle-1.xml = 258 slugs (was 257). A guest Aura call returns no body field, so every article was rendered in headless Chromium over CDP and the LWC article layout text captured: 238 bodies held; 20 sitemap slugs (19 Spanish plus Epos-Now-Delivery-Deliverect) render the "Oops! We can’t seem to find that page" error under both en_US and es. The Salesforce sitemap is a floor, not a census. Also read: all 117 release notes listed at www.eposnow.com/us/release-notes/; 205 eposnow.com store, app and hardware pages; the current developer portal api.eposnowhq.com/docs/ (MkDocs, 21 nav pages) with its 7 anonymous OpenAPI 3.0.1 module specs (api.eposnowhq.com/swagger/<module>/v4/swagger.json, 242 paths); and the legacy developer.eposnowhq.com (18 nav pages plus the docs/v4/json Swagger 2.0 spec, 133 paths). Wayback CDX for help.eposnow.com, eposnow.zendesk.com and developer.eposnowhq.com answered 503 "Temporarily Offline" on every attempt, so retired Zendesk articles were NOT checked. Retrieved 2026-09-16. https://support.eposnow.com/s/article/Epos-Now-Order-Pay---Step-5?language=en_US · retrieved 2026-09-16 adversarially verified
Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.
delivery-address-validation
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
Epos Now sells Order & Pay (AppStore AppID 1165, "powered by Yoello") as commission-free web ordering: the product page states "Completely Commission free" / "Yoello charges no additional fees for any order made through it" and customers "browse the menu, make an order, and pay by scanning a QR code or typing in a URL using any smartphone", with orders managed "through the Epos Now system". Named shortfalls: the ordering site is not on the restaurant's own domain - Step 6 states "Your URL will appear as: pay.yoello.com/v/[yourvenuenickname]", a 12-character nickname that "you will not be able to change" once saved, with branding limited to a logo on the QR plaque; the platform is a partner white-label (Yoello), not built in-house; and the orders-into-the-POS leg is asserted only on the marketing page - the setup docs read (Steps 1, 2, 5, 6, 7) show order accept/finish in an order-management portal, and Steps 3 and 5 render as title-only stubs, so direct till write-in is not documented. https://support.eposnow.com/s/article/Epos-Now-Order-Pay---Step-6?language=en_US · retrieved 2026-08-04
Vendor offers a branded native iOS and Android ordering app (published under the restaurant's own brand in the App Store/Play Store), not only a mobile web page or a shared multi-restaurant marketplace app. differentiator
digital-native-app
Not scored by this record.
Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels.
digital-account-saved-payment
CLAIM: guests can create an account with saved addresses, saved (tokenised) payment methods, and one-tap reorder. VERDICT: unknown -> partial/B. Order & Pay is 'powered by Yoello' (https://support.eposnow.com/s/article/Epos-Now-Order-Pay---Step-1?language=en_US: "Epos Now Order & Pay, powered by Yoello"; merchants log into eposnow.yoello.com). PUBLIC SOURCE MAPS on both Yoello production apps: eposnow.yoello.com merchant dashboard (https://eposnow.yoello.com/static/js/main.26980a47.chunk.js.map, 949 own sources; services/generateConsumerURLs.ts: prod: "https://pay.yoello.com", venue links https://pay.yoello.com/v/{venue_nickname}) and the consumer ordering app pay.yoello.com (/asset-manifest.json lists 73 JS chunks, all 73 .js.map 200, nonsense-map control 404; 2,146 sources, 715 own). EVIDENCE (consumer app pay.yoello.com, original source from sourcesContent): ACCOUNT: Components/LoginV2 (EmailLogin/EmailInput.tsx; SocialLoginButtons GoogleButton/FacebookButton calling Auth.federatedSignIn with CognitoHostedUIIdentityProvider.Google / .Facebook), distinct from a guest mode (LoginV2/GuestView, useGuestUserData isGuest). SAVED PAYMENT: Components/Payment/PaymentDrawer/Stripe/CardDetailsForm.tsx (https://pay.yoello.com/static/js/4902.0f1866d0.chunk.js.map): "{!props.isGuest && ( <div ... data-component-name=\"RememberMyCard\"> <Checkbox onChange={props.rememberCardOnChange} checked={props.rememberCard}> {t('Payment.RememberMyCardDetails')}" — the same checkbox exists in the Square drawer (name=\"save-card\") and the order body sends save_card / card_token; Pay360 path reads stored cards via APIExtensions.consumerPay360Cards and maps "masked_card_number: detailsItem.last4, token: detailsItem.card_token"; Stripe path useStripe.getCard(token) -> getPaymentDetails(token). SAVED ADDRESS: customHooks/useConsumerLocations.tsx POSTs/PATCHes consumer?.id + '/locations/' + addressID "Not updating if it's not delivery or the user is not fully logged in yet", and DeliveryAddressForm offers title="UseExistingAddress" for currentUser?.addresses[0]. REORDER: customHooks/useGetLastOrder.tsx (https://pay.yoello.com/static/js/3548.f50ea52e.chunk.js.map) "/** Uses the last order data to try and re-create last order if items are available */ function addOrderToCart()" behind Components/Menu/UI/CartButtons.tsx title={'RepeatOrder'} dataComponentName="RepeatOrderButton" (authenticated or guest). WHY PARTIAL: account + tokenised remembered card are shown; but only ONE stored address is read or written (addresses[0], PATCH the first id) rather than saved addresses, and RepeatOrder refills the cart and navigates to the cart page, not a one-tap placed order. Also the code is Yoello's (the white-label provider Epos Now names), not Epos Now's own repo, and the help centre does not document these consumer features. Retrieved 2026-09-17. MERGE (322nd): graded C not B - the source is the white-label provider Yoello's shipped code (eposnow.yoello.com / pay.yoello.com), not Epos Now's own docs or code, and Epos Now's help centre does not document these features. https://pay.yoello.com/static/js/main.628b552f.js.map · retrieved 2026-09-17 adversarially verified
Digital checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator
digital-upsell-engine
Not scored by this record.
Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.
digital-scheduled-pacing
Not scored by this record.
Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.
digital-fulfillment-modes
Not scored by this record.
Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.
digital-qr-table
Not scored by this record.
Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator
digital-kiosk
Not scored by this record.
Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.
digital-group-ordering
Not scored by this record.
Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator
digital-catering-portal
Not scored by this record.
Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator
digital-voice-ai-phone
Not scored by this record.
Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.
digital-drivethru-ai
Not scored by this record.
Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.
digital-sms-ordering
Not scored by this record.
Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator
digital-google-order
Not scored by this record.
Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.
digital-apple-business-connect
Not scored by this record.
Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.
digital-loyalty-attach
Not scored by this record.
Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.
digital-subscriptions
Not scored by this record.
Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.
digital-promo-parity
Not scored by this record.
Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator
digital-guest-data-ownership
Not scored by this record.
Digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.
digital-checkout-pci-sca
Not scored by this record.
Digital channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator
digital-surcharge-transparency
Not scored by this record.
Guest data, loyalty & marketing
Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.
guest-loyalty-unified-profile
One customer record is shared by Back Office and Front Till ("Customers can be added, edited and accessed via the Back Office and Front Till") and carries title, name, DOB, phone, email, Customer Type, loyalty Card Number, Signup Location and a marketing-consent opt-in. Shortfalls: the guide documents no phone- or email-match dedup and no merge behaviour for duplicate records, and does not state that orders arriving from Epos Now Online or Order & Pay attach to the same profile - customers are created by hand at the till or in the Back Office. https://support.eposnow.com/s/article/Customer-Management?language=en_US · retrieved 2026-08-03
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
The claim needs at least two of points-per-dollar, visit/punch-count and spend-tier accrual as native configuration; Epos Now's in-house Loyalty app has exactly one. Its setup guide enumerates the whole points scheme - "Enter the Minimum Points Spend", "Enter the Points Value in your local currency ... i.e. 1 point = 0.01p", "Enter the relevant Get 0 Points per 0 p Spent section ... i.e. Get 1 Point per 10p Spent", plus a checkbox choosing pro-rata versus full-qualifying-value earning. No visit, punch-card or tier construct exists anywhere in the article; the only other lever is a flat Discount % on a Customer Type. Epos Now's own routes to other accrual models are bolt-on AppStore loyalty vendors (LoyalZoo, Loyalty Dog), which the claim excludes. https://support.eposnow.com/s/article/Apps-Loyalty?language=en_US · retrieved 2026-08-04
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
The in-house Loyalty app's features are enumerated as "a customisable points-based system", promotions targeted at Customer Types, optional printed loyalty cards, and customer reports; configuration is limited to Minimum Points Spend, Points Value and a points-per-spend ratio. No triggered birthday, first-visit or lapsed win-back campaign exists. Epos Now's own answer for campaign automation is the paid Mailchimp integration, whose article says Mailchimp is where you "build workflows and custom rules so you can target your customers with timely and relevant content" - the automations run in the third-party ESP, not the platform. https://support.eposnow.com/s/article/Apps-Loyalty?language=en_US · retrieved 2026-08-03
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
The Front Till is the time clock, using the staff passcode (PIN): "On the Front Till, tap Clock In/Out (top left corner of the Log In screen). Select the staff tile for the person clocking in. Enter the passcode, then select Clock In." Clock-out mirrors it and "A small print-out will be generated confirming the clock out." No separate time-clock hardware or app is required, and forgotten clock-outs are corrected in the Back Office: "Go to Staff Reports or Time Tracking in the Back Office. Manually edit the Clock In/Out times as needed." https://support.eposnow.com/s/article/Clock-In-Out?language=en_US · retrieved 2026-08-04
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
Staff Roles are operator-defined rather than fixed tiers, and permissions are granted per discrete action: the Void guide names "Delete Unordered Items" and "Void Ordered Items and Delete Unordered Items" as separate checkboxes, and the End of Day guide names "Close Till" and "Blind End of Day" as further per-role permissions. Shortfalls: the Adding Staff Roles guide never enumerates the permission set (it only says enabling Permissions reveals four checkboxes that expand further), and no per-location scoping of a role is documented - roles are created once at organisation level. https://support.eposnow.com/s/article/Performing-a-VOID?language=en_US · retrieved 2026-08-03
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
Reporting > Auditing provides Refunds, Discounts, No Sales and Void Lines reports, each filterable by location, device and staff and exportable to CSV/Excel; No Sales shows "the date, time, staff member and the device the no sale was processed on", and the End of Day shows all voids and deletes with the staff member and time. Shortfall: Epos Now documents no manager-override or approval step at all - actions are permitted or refused by the acting user's own staff-role permissions - so the audit trail attributes the performer and never a separate approver, and no immutability property is claimed for these reports. https://support.eposnow.com/s/article/Auditing?language=en_US · retrieved 2026-08-03
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
There is no recipe or bill-of-materials entity in Epos Now. The knowledge base enumerates its stock features - Stock Management, Stock Takes, Stock Movements, Master Products, Purchase Orders, Measurements, Adding Stock, Stock Reports - and recipe costing is not among them. The native depletion model is single-level pack conversion: a Master Product carries a cost price, a Unit of Sale and a Volume of Sale ("the amount of child products within the master product"), and selling the child deducts from the master - one level, and the master is a purchase pack, not a prep item that can itself contain components. Ingredients appear only as free text: the Product Plus app adds "an extended description to allow for ingredients, variants, or allergy information", with no quantity or cost attached. Epos Now's own documented answer for the capability is a third-party partner-billed AppStore integration - Apicbase, "a back of house management software for food businesses ... an easy to use platform for food cost control that integrates seamlessly with Epos Systems" that will "simplify your stock counts, recipe costings", quoted by Apicbase's own sales team with "basic packages start at GBP175" billed by Apicbase directly. Multi-level sub-recipes and automatic plate-cost recalculation are therefore not an Epos Now capability. https://support.eposnow.com/s/article/Apicbase?language=en_US · retrieved 2026-08-04
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
Master Products model the purchase pack against the sold unit: the master carries a "Unit of Sale" and a "Volume of Sale" (the number of child products inside it), and each child product is linked to the master with an "Amount" deducted per sale. The free Measurements app adds Weighed and Measured product types with a Measurement Scheme, a Unit of Purchase and a Unit of Sale with cost and sale price per measurement unit. Shortfalls: there is no separate count unit distinct from the sale unit, and no yield or waste percentage is applied to the raw-to-usable conversion anywhere in these guides. https://support.eposnow.com/s/article/Master-Products-Back-Office?language=en_US · retrieved 2026-08-03
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
Stock takes run from either the Back Office or the Front Till, and the list can be a full count or a subset filtered by supplier, category, or wet/dry - plus a Quick Scan mode that builds the count by barcode. Counts can Add To or Set the expected figure, carry a reason and notes, are reviewed for discrepancies before completion, and past stock takes are retained and browsable by date range and location, so history is not overwritten. Shortfall: nothing in the guide schedules recurring or cycle counts - every stock take is started manually by a named staff member. https://support.eposnow.com/s/article/Stock-Takes?language=en_US · retrieved 2026-08-03
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
The browser half is documented and the freshness requirement is met explicitly: the Back Office Home Page is "the landing page after you log in", carries three sales overview metrics with prior-period comparison, a sales overview line chart, and a top-ten products table, filterable by today/yesterday/this week/last week and by area or location - and of the chart, "The graph can be refreshed to view sales made up to 5 minutes prior." Separately, Setting up a Reporting Dashboard documents user-composed dashboards assembled from Back Office reports with a monthly/weekly/daily/hourly display granularity plus scheduled email delivery. Named shortfalls: no dedicated mobile reporting app is documented - the published mobile clients are the Till app (com.eposnow.till) and the iOS POS Till, and the knowledge base routes owners to the Back Office web portal, not to an owner app; and the refresh is manual on two counts, since the Home Page graph must be refreshed by the user and "By default, the Back Office does not load dashboards or reports automatically" until the "Do not run reports on initial page load" checkbox is unticked under Organisations > Company > Company Details. https://support.eposnow.com/s/article/Home-Page?language=en_US · retrieved 2026-08-04
Generates a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types, and expected cash deposit in one document.
reporting-eod-closeout
The End of Day report submitted to the Back Office is one document per till close carrying opening balance, net sales inc VAT, gratuity, pay-outs, petty cash, banked, Expected, Actual and Variance, with the staff who opened and closed and the times; "Show Tenders" expands it into Tender Type, Sale, Wet/Dry, Sales by Product, Sales by Employee, Refund, Sale by Category, Void Summary, Tax Summary and Credit breakdowns, and the data is locked once submitted ("cannot be changed"). Shortfalls: the enumerated breakdowns include no discount total and no gross-sales line (net sales inc VAT only), and tips appear only for operators who have bought the separate Gratuity app. https://support.eposnow.com/s/article/End-of-day-reports?language=en_US · retrieved 2026-08-03
Provides a product mix (PMIX) report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center.
reporting-pmix-modifier-level
The Sales by Product report lists per product the quantity, measured quantity, sales inc tax, discount, net sales inc and exc tax, cost price, margin and margin %, filterable by location area, location, device group, device, staff, wet/dry and product tag, and exportable. Shortfalls: the documented filters offer a date range but no daypart and no revenue centre, and the report is defined over products only - modifiers are not a reported dimension (they are separate Multiple Choice products, so they can appear as ordinary product rows, but no modifier-level view of a parent item's mix is documented). https://support.eposnow.com/s/article/Sales-by-Product-Report?language=en_US · retrieved 2026-08-03
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
Multi-Site Manager defines three first-class levels - Location Areas, Locations and Devices - and a Location Area can be given "a Parent Location Area where the Location Area you are currently creating will sit within, this could be an HQ Location Area", giving four. Reporting is scoped to it ("Filter by Location Area" appears on the End of Day and Sales by Product reports only when Multi-Site Manager is used) and it is used to "Manage restrictions on access more effectively to reduce visibility of sensitive information". Shortfall: hierarchy is not in the base product - Multi-Site Manager is a chargeable AppStore add-on (Buy App or 30-day trial, monthly charge thereafter). https://support.eposnow.com/s/article/Multi-Site-Manager?language=en_US · retrieved 2026-08-03
Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.
multi-location-price-zones
One item can hold several prices without duplication: the free Price Scheduling app defines Price Bands (Sale Price inc tax and Eat Out Price inc tax per product) activated by Price Schedules on a duration/time basis with a 1-99 priority to resolve collisions, and Multi-Site Manager adds "Location Area specific rules (Pricing, Promotions, Multiple Choice Products)". Shortfalls: a Price Schedule targets a single location - "you can only select one location. If you wish for this to apply to multiple locations, you will need to create additional Price Schedules" - and the only channel axis on a band is eat-in versus eat-out, with no per-marketplace or per-delivery-channel price book; location-group pricing needs the paid Multi-Site Manager app. https://support.eposnow.com/s/article/Price-Scheduling?language=en_US · retrieved 2026-08-03
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
CLAIM: vendor docs name the client OSes supported and state minimum OS versions and device specs. VERDICT: partial. Platforms are named and first-party hardware has full spec sheets, but no minimum OS version or device spec is published for running the till on the merchant's own Android, Windows or macOS hardware. EVIDENCE: help centre Accessing your Epos Now back office (https://support.eposnow.com/s/article/Accessing-your-Epos-Now-back-office?language=en_US) lists Till App downloads for "Windows", "Android - Visit the Google Play Store", "iOS - Visit the Apple App Store" and "MacOS". Bixolon 275 guide: "compatible with Epos Now Android and Windows Till Systems as well as iOS & iPadOS". Kitchen Display Screens: "compatible with Android and Windows devices". The (Duo) Countertop Compatibility and Specs Guide has a full spec table: "Processor Kryo-260 Octa-core 2.2GHz / Memory (RAM) 4GB / Storage 64GB / OS epOS Android 9.0 ARM", a 15.6" 1920*1080 display, ports and power. Release note 2.114 (https://www.eposnow.com/us/release-notes/epos-now-2-114/, 24/01/2023) sets one minimum: "please ensure that your iOS device runs on iOS 11.0 or above and that your iOS POS app is updated to version 1.2.18 or above" (for Epos Now Payments on iOS). The Android POS system store page (https://www.eposnow.com/uk/store/hardware/android-pos-system/, grade C) gives the bundled Lenovo Tab M10 "Operating system: Android 10", 4GB RAM, and "System requirements: Google Play Store account. Internet access." Global Payments Integration gives app-version minimums, not OS minimums: "Android Version required: 1.1.84 or above", "Windows Version required: 3.4.1.7 or above". SHORTFALL: no page found states a minimum Android, Windows, macOS or iPadOS version, or a minimum device spec, for running the Till App on the merchant's own hardware. The only OS floor is iOS 11.0, in a payments release note. SURFACES 2026-09-16: support.eposnow.com (Salesforce Experience Cloud) re-censused from the live sitemap-topicarticle-1.xml = 258 slugs (was 257). A guest Aura call returns no body field, so every article was rendered in headless Chromium over CDP and the LWC article layout text captured: 238 bodies held; 20 sitemap slugs (19 Spanish plus Epos-Now-Delivery-Deliverect) render the "Oops! We can’t seem to find that page" error under both en_US and es. The Salesforce sitemap is a floor, not a census. Also read: all 117 release notes listed at www.eposnow.com/us/release-notes/; 205 eposnow.com store, app and hardware pages; the current developer portal api.eposnowhq.com/docs/ (MkDocs, 21 nav pages) with its 7 anonymous OpenAPI 3.0.1 module specs (api.eposnowhq.com/swagger/<module>/v4/swagger.json, 242 paths); and the legacy developer.eposnowhq.com (18 nav pages plus the docs/v4/json Swagger 2.0 spec, 133 paths). Wayback CDX for help.eposnow.com, eposnow.zendesk.com and developer.eposnowhq.com answered 503 "Temporarily Offline" on every attempt, so retired Zendesk articles were NOT checked. Retrieved 2026-09-16. https://support.eposnow.com/s/article/Duo-Countertop-Compatibility-and-Specifications-Guide?language=en_US · retrieved 2026-09-16 adversarially verified
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
CLAIM: terminals keep taking orders, printing to the kitchen and recording cash sales with the internet down, and the vendor documents which functions degrade. VERDICT: partial. Epos Now documents that the till keeps trading offline and states the card-side limits, but never says whether kitchen printing continues or lists which till pages are blocked. EVIDENCE: release note 3.21 (https://www.eposnow.com/us/release-notes/epos-now-release-notes-3-21/, 18 June 2025): "ENHANCEMENT: Offline Mode improvements - We've made several enhancements to improve the experience when using the till offline: ... A pop-up now appears when the till enters offline mode ... When viewing Orders or Tabs/Table Plan for the first time offline, a pop-up provides guidance and best practices ... New offline banners: Replaces the resync timer on the Table Plan; Added to the Orders page ... Pages that aren't accessible offline are now blocked". Release note 3.38 (17 March 2026): "a new unsynced transactions section into the End of Day screens ... transactions that may not have reached your Back Office due to a number of reasons, such as trading offline." Release note 3.46 (21 July 2026): "when your Till loses its internet connection ... the till realizes it's offline immediately and instantly processes the payment using its local backup." The help-centre article Epos Now Payments - Offline Mode (https://support.eposnow.com/s/article/Epos-Now-Payments-Offline-Payments?language=en_US) documents the card side: "Maximum offline transactions stored: 10 transactions" (GBP 20 each); "You cannot process a refund when you are in Offline Mode"; "MOTO payments ... are not supported in offline mode"; "all staff will have access to process payments using Offline Mode"; and "if your Till loses internet connection your Till will display that it is offline". SHORTFALL: no page names the pages that are "not accessible offline", and none says kitchen or order printing continues offline. The printer guides (POS80Gx, Star TSP100, Bixolon 275) label a till setting "Offline Order Printing", but that is a menu name, not a statement of behaviour. The KDS needs internet ("An internet connection is required", Kitchen Display Screens). SURFACES 2026-09-16: support.eposnow.com (Salesforce Experience Cloud) re-censused from the live sitemap-topicarticle-1.xml = 258 slugs (was 257). A guest Aura call returns no body field, so every article was rendered in headless Chromium over CDP and the LWC article layout text captured: 238 bodies held; 20 sitemap slugs (19 Spanish plus Epos-Now-Delivery-Deliverect) render the "Oops! We can’t seem to find that page" error under both en_US and es. The Salesforce sitemap is a floor, not a census. Also read: all 117 release notes listed at www.eposnow.com/us/release-notes/; 205 eposnow.com store, app and hardware pages; the current developer portal api.eposnowhq.com/docs/ (MkDocs, 21 nav pages) with its 7 anonymous OpenAPI 3.0.1 module specs (api.eposnowhq.com/swagger/<module>/v4/swagger.json, 242 paths); and the legacy developer.eposnowhq.com (18 nav pages plus the docs/v4/json Swagger 2.0 spec, 133 paths). Wayback CDX for help.eposnow.com, eposnow.zendesk.com and developer.eposnowhq.com answered 503 "Temporarily Offline" on every attempt, so retired Zendesk articles were NOT checked. Retrieved 2026-09-16. https://support.eposnow.com/s/article/Epos-Now-Payments-Offline-Payments?language=en_US · retrieved 2026-09-16 adversarially verified
Sells or supports a dedicated kitchen display system with bump-bar or touch input, station routing, and course/fire timing, as a first-party product rather than an integration-only dependency.
hardware-kds
First-party product, touch-driven, with station routing: Epos Now sells the KDS software licence Upfront, as HaaS or Software Only, "Epos Now offers a 21.5-inch Full HD 1080p Android Touch Screen with built-in WiFi, but you can also use your own hardware"; input is touch ("Mark individual items as complete by checking them off" - no bump bar is offered, but the claim accepts touch); and "Order Routing: Seamlessly direct orders to different KDS stations" via categories assigned to order channels plus a per-screen Order Views filter. Named shortfall: no course or fire timing on the KDS - the only timing feature is order-age countdown ("Timers: Highlight orders that have been waiting too long with configurable timers", turning tickets orange or red), and Epos Now's coursing construct is a course number on a category that controls the printed ticket sequence (Courses guide); no course view, fire, or hold/fire control appears anywhere in the KDS guide. https://support.eposnow.com/s/article/Kitchen-Display-Screens?language=en_US · retrieved 2026-08-04
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
Public Swagger reference reachable anonymously - no login, NDA or sales call. The v4 index renders 60+ resources (Product, Transaction, Customer, Stock, Staff, Webhook, TokenInfo) plus a Types section, and the machine-readable Swagger 2.0 document is served at /docs/v4/json; the v2 reference at /Docs/V2 is equally open. Previously cited as /Docs/Global, which now 301s here. https://developer.eposnowhq.com/Docs/v4/index · retrieved 2026-08-09
API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator
extensibility-api-access-cost
Not scored by this record.
A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator
extensibility-free-sandbox
Not scored by this record.
Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).
extensibility-oauth-partner-apps
CLAIM: third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions, not static API keys. VERDICT: no. EVIDENCE: the developer portal has seven anonymous OpenAPI 3.0.1 specs (customer, management, products, reports, setup, stocks, transactions at https://api.eposnowhq.com/swagger/<module>/v4/swagger.json, 242 paths). Each declares exactly ONE security scheme, "Basic" (type apiKey, in header, name Authorization): "The Epos Now API uses Location specific API keys to authenticate requests. You can view and manage your API keys from the Epos Now Back Office under the API Device located in the App Store ... Epos Now APIs use Basic access authentication. When authenticating construct your key as follows - **Basic {{API_KEY}}**." The portal index (https://api.eposnowhq.com/docs/) gives one header form: "Authorization: Basic ${API_KEY}". For App Store partner apps, App Manifest (https://api.eposnowhq.com/docs/appstore/manifest/) says the installation webhook payload "contains basic information about the user as well as a Token which can be used to access Epos Now data through our API. The Token sent in the payload is specific to the location the app was installed at". That is a location key pushed to the app, with no scope list, consent screen or grant flow; the merchant's only control is install or uninstall. The legacy portal says the same. https://developer.eposnowhq.com/Docs/Authentication: "pass an Authorization header with your request, containing Basic and your API access token ... concatenate your API Key, a colon character ":", and you API Secret ... then Base64 encode it". Its docs/v4/json securityDefinitions = {"BasicAuth":{"type":"basic"}}. Its JavaScript library page says App Store apps must not set a token because "other customers will have their access token automatically picked up". The help-centre Zapier guide has the merchant "copy the API Access Token" and paste it into Zapier. BOUND/CONTROLS: a security-scheme block is the list of auth methods an OpenAPI spec accepts. The 7 module specs are every swagger(env, "<module>") call on the portal's API Documentation pages. All 21 nav pages of the current portal and all 18 nav pages of the legacy portal were fetched. Tokenised, case-insensitive, word-bounded counts (new portal / 7 specs / legacy portal + v4 spec / 238 help-centre bodies / 117 release notes): oauth 1/0/0/0/0; oauth2, openid, bearer, scopes, client_id, refresh token, authorization code and revoke 0 everywhere; basic 6/401/9/9/3. POISON found and excluded: (1) The single "OAuth" hit is on Partner Lead Sharing (https://api.eposnowhq.com/docs/partner_sf_lead/), where Epos Now sends referral leads OUT to a partner's endpoint: "We support multiple authentication methods and can submit to Basic Auth or all the way to full OAuth 2.0 REST endpoints". That is outbound and uses the partner's auth, not app access to Epos Now. (2) The legacy Swashbuckle page carries the config literal oAuth2Enabled: ('false' == 'true'). (3) "scope" in the specs is a ReceiptQR source-parameter description. (4) "consent" is GDPR marketing consent in the help centre and cookieconsent CSS on eposnow.com. (5) login.eposnowhq.com redirects with a login_challenge and support.eposnow.com links an eposnow_oidc SSO; both are merchant sign-in, not third-party app authorisation. Retrieved 2026-09-16. https://api.eposnowhq.com/swagger/transactions/v4/swagger.json · retrieved 2026-09-16 adversarially verified
The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.
extensibility-webhooks-push
POST /api/v4/Webhook registers a subscription shaped {BaseUrl, Triggers:[{EventTypeId, Path}]} - the merchant supplies a callback URL, so events are pushed. The Webhook Event Type table enumerates CompleteTransaction (304), CreateOrderedTransaction (305), CancelOrderedTransaction (308) and DeleteTransaction (309). Note the enumeration carries no refund-specific event, so refunds are not separately subscribable. Previously cited as /Docs/Global, which now 301s here. https://developer.eposnowhq.com/Docs/v4/index · retrieved 2026-08-09
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
CLAIM: order entry, ticket routing and check printing continue on-terminal when the internet connection is lost. VERDICT: partial. Epos Now documents that the till keeps trading and shows Orders and Tabs/Table Plan while offline; it does not say whether tickets route or checks print offline. EVIDENCE: release note 3.21 (https://www.eposnow.com/us/release-notes/epos-now-release-notes-3-21/, 18 June 2025): "We've made several enhancements to improve the experience when using the till offline: Improved offline detection: The system now enters and exits offline mode more reliably ... When viewing Orders or Tabs/Table Plan for the first time offline, a pop-up provides guidance and best practices. New offline banners: Replaces the resync timer on the Table Plan; Added to the Orders page for better clarity. Improved navigation handling: Pages that aren't accessible offline are now blocked". Release note 3.38 (https://www.eposnow.com/us/release-notes/epos-now-release-notes-3-38/): an unsynced-transactions section for "transactions that may not have reached your Back Office due to a number of reasons, such as trading offline ... the till will look to push any unsynced data to your account prior to being able to close the trading period." Epos Now Wrapped 2025 (https://www.eposnow.com/us/release-notes/epos-now-2025-wrapped-hospitality/): "Improvements to offline mode gives clearer alerts when the till is offline, while ensuring merchants can keep trading with minimal disruption." Help centre, Epos Now Payments - Offline Mode: "if your Till loses internet connection your Till will display that it is offline". SHORTFALL: nothing states that orders route to kitchen printers or that checks or receipts print offline (the printer guides' "Offline Order Printing" is only a settings label), and the pages "not accessible offline" are not listed. The order-entry evidence is release notes, not a help-centre article. The KDS needs internet. SURFACES 2026-09-16: support.eposnow.com (Salesforce Experience Cloud) re-censused from the live sitemap-topicarticle-1.xml = 258 slugs (was 257). A guest Aura call returns no body field, so every article was rendered in headless Chromium over CDP and the LWC article layout text captured: 238 bodies held; 20 sitemap slugs (19 Spanish plus Epos-Now-Delivery-Deliverect) render the "Oops! We can’t seem to find that page" error under both en_US and es. The Salesforce sitemap is a floor, not a census. Also read: all 117 release notes listed at www.eposnow.com/us/release-notes/; 205 eposnow.com store, app and hardware pages; the current developer portal api.eposnowhq.com/docs/ (MkDocs, 21 nav pages) with its 7 anonymous OpenAPI 3.0.1 module specs (api.eposnowhq.com/swagger/<module>/v4/swagger.json, 242 paths); and the legacy developer.eposnowhq.com (18 nav pages plus the docs/v4/json Swagger 2.0 spec, 133 paths). Wayback CDX for help.eposnow.com, eposnow.zendesk.com and developer.eposnowhq.com answered 503 "Temporarily Offline" on every attempt, so retired Zendesk articles were NOT checked. Retrieved 2026-09-16. https://www.eposnow.com/us/release-notes/epos-now-release-notes-3-21/ · retrieved 2026-09-16 adversarially verified
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
329th: NEW SURFACE, THE STORE-LEVEL TILL APP ITSELF. Google Play publisher census (https://play.google.com/store/apps/developer?id=EPOS+NOW, retrieved 2026-09-18) lists exactly ONE Epos Now Android app, com.eposnow.till (Play shows current version 1.1.107, updated 13 Feb 2026); the 20.1 MB APK of that same version 1.1.107 was downloaded anonymously and unpacked (7 dex files, 41 MB, resources.arsc, assets/): 367,270 extracted strings. The till APK is a WebView shell over the cloud till (strings 'https://www.eposnowhq.com', 'Lcom/eposnow/till/WebViewClient;', 'Android System WebView is not found'), so it is NOT a census of till FEATURES -- but ORDER PRINTING IS IMPLEMENTED NATIVELY ON THE DEVICE, and that is the half of this claim that was unresolved. The app ships a self-contained offline order-printer subsystem: classes com/eposnow/till/orderprinter/OrderPrinterHandler, OrderPrinterQueueService, OrderPrinterTransaction, OfflineOrderPrinterRepository (IOfflineOrderPrinterRepository), OrderPrinterSettingsActivity / OrderPrinterAdvancedSettingsActivity; a LOCAL SQLite schema ('CREATE/ALTER TABLE orderprinters', 'orderprinterdetails', 'orderprinterTypes', 'delete from orderprinters WHERE printerID = ?', columns fontSize/fontWidth/shouldBeep/printPacketSize/printPacketDelay/useImagePrinting/enabledForOnlineOrders); and user-visible labels in resources.arsc: 'Offline Order Printer', 'Add Offline Order Printer', 'Offline Order Printer Settings', 'Advanced Offline Order Printer Settings', 'Enable order Printer', 'Clear queued prints', 'Order printer queue cleared.', 'No Order Printers have been added.', plus native drivers for Bixolon, Star Micronics, XPrinter (UDP discovery), Sunmi, PAX, Kozen and generic EscPos. VERDICT: unknown -> partial/B. The kitchen-printer half is satisfied: printer definitions, per-Order-Type routing and the print QUEUE all live on the till device, so kitchen/bar ticket printing does not traverse the cloud -- the vendor's own setup guides route by station in exactly this module ('Select Offline Order Printing in the list on the left ... Select the Order Type you wish to use, for example Bar, Kitchen, or Front', https://support.eposnow.com/s/article/POS80Gx-Printer-Set-Up-Ethernet?language=en_US; 'Under Offline Order Printer, select Offline Order Printer Settings ... Enter the IP Address ... leave the Port as 9100'), and release 3.21 documents a till offline trading mode. NAMED SHORTFALL: (a) the display half fails on the vendor's own words -- Kitchen Display Screens, 'An internet connection is required'; (b) no Epos Now sentence states in prose that order tickets still print during an internet outage, so the printer half rests on the vendor's own module naming plus the on-device queue/DB implementation, not on a published statement. Retrieved 2026-09-18. https://support.eposnow.com/s/article/POS80Gx-Printer-Set-Up-Ethernet?language=en_US · retrieved 2026-09-18 adversarially verified
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
The order-printing setup wizard enumerates the whole configuration - printer brand, connection method (USB, Ethernet or built-in), detection or manual IP entry, "Choose Order Channels ... You can assign multiple channels and choose how many copies to print for each", category-to-channel assignment, and a "Print orders from this till" toggle. No backup printer, failover target or unreachable-printer alert appears anywhere in it. Epos Now's documented remedy when a ticket does not reach the line is the manual Resend Orders function, used "when an order ticket is lost, damaged, or when items need to be re-prepared". https://support.eposnow.com/s/article/Order-Printing-Setup?language=en_US · retrieved 2026-08-03
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
Both the renewal term and the notice window are stated in the publicly posted contract, reached without login from https://www.eposnow.com/us/terms/ which redirects to this PDF. Section 10.7: "The Software licence shall apply for a minimum period of 12 months (\"Initial Term\") and shall automatically renew for further 12 month periods (each a \"Renewal Period\") unless and until a party provides the other party with written notice to cancel the Software licence at least 30 days before the start of the next Renewal Period, which shall take effect no earlier than the end of the Initial Term or the end of the then current Renewal Period. Upon the start of each Renewal Period, the Customer shall be charged for the Software licence fees (at the then current rates) via the original billing method." Section 12 covers the Support Plan on the same pattern - it "shall automatically renew for another year unless the Customer advises Epos Now before the renewal date" - and adds a 30-day post-renewal cooling-off period during which cancellation carries "no penalty to the Customer". So: 12-month auto-renew, 30 days written notice, published rather than quote-only. https://eposnow-marketing.s3.eu-west-1.amazonaws.com/public/terms/terms-us.pdf · retrieved 2026-08-04
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
The US pricing page publishes no per-location or per-terminal software figure — only a hardware bundle promo and contact forms. https://www.eposnow.com/us/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
A complete-system hardware bundle is advertised as an outright purchase from $249 (was $1049), but no per-item price list for terminals, KDS screens or printers. https://www.eposnow.com/us/pricing/ · retrieved 2026-08-01
Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator
commercial-hardware-not-locked
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 5 values — 5 upheld, 0 downgraded, 0 upgraded. It separately resolved 30 previously unknown values. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| order-capture-split-merge | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | The payment screen documents one split mode only: "choose to split by cover option / Choose the number of covers you would like to split the order by" (even N-way). No split by item, by seat, or by arbitrary amount is described. Merging exists as the separate Move/Merge feature (enabled via the Epos Now Labs app), which moves individual items or partial quantities between tables, but its guide states "the partial move of tables doesn't support moving partially paid bills or promotions". source |
| menu-pricing-nested-modifiers | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | Multiple Choice Product Groups carry a minimum selection and a maximum selection, and a per-product "Make multiple choice products optional for this product" checkbox (so forced selection is the default). Multiple groups can be attached to one product with a Till Order to sequence them. The guide describes only groups attached directly to a sellable product; no nesting of a group beneath another modifier, and therefore nothing approaching three levels, is documented. source |
| menu-pricing-modifier-price-by-parent-size | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-no | Sizes are not an axis on the item: the free Product Matrix app builds a Variant Map and then "the original Base Product has been removed and replaced with a button for each size" - one duplicated product record per size. Modifiers are separate products grouped into Multiple Choice Product Groups, and the group-to-product assignment screen exposes only the group, a Till Order and an optional-selection checkbox - no per-parent or per-size price field. A modifier's price therefore lives on the modifier product itself; there is no price matrix. source |
| menu-pricing-topping-quantity-tiers | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-no | The Multiple Choice Product Group configuration is enumerated in full - name, description, minimum selection, maximum selection, member products, Till Order, optional-selection checkbox. There is no quantity tier (light/regular/extra/double) and no price multiplier per tier; a modifier is a product carrying its own price, so extra portions can only be expressed by selecting the modifier again. source |
| payments-gift-cards | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-no | Epos Now has no first-party gift card. Its own guide for issuing and redeeming vouchers is a workaround built on Customer Credit: "Name the customer with the same code that the physical voucher is named with", load credit against that customer record, then redeem by selecting Customer Credit as the tender and "record the available balance on the physical voucher or staple the receipt to it". Real gift-card programmes are delivered by third-party AppStore integrations (Factor4, VoucherCart), each requiring credentials issued by that vendor. source |
| payments-refund-void-controls | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | Void and delete are gated by discrete staff-role permissions - "Delete Unordered Items" and "Void Ordered Items and Delete Unordered Items" - and the End of Day plus the Reporting > Auditing > Void/Delete Lines report show every void and delete with staff member, till and time; Refunds, Discounts and No Sales have their own auditing reports filterable by location, device and staff, and refunds require a reason code from a configured list. Shortfall: the docs describe permission-gating of the operator only, with no manager-PIN override or approval step, so no separate approver is ever recorded, and no immutability guarantee is stated for these reports. source |
| kitchen-bump-bar-hardware | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-no | The article's Compatibility and Requirements section enumerates the supported KDS hardware: "compatible with Android and Windows devices, including monitors, tablets, and mobile phones. For maximum efficiency, touchscreen devices are recommended", plus Epos Now's own 21.5-inch Android touch screen. Every documented interaction is touch (check items off, Recall Order, Move Ticket, hamburger Summary View). No bump bar or programmable keypad is offered and no supported models are listed. source |
| digital-menu-single-source | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | Epos Now Online is described as "Transferring your products and data from your Epos Now account into your online store so you only have to manage one set of products"; the site publishes "any Products within your Epos Now account that have been marked as 'Sell on web'", toggled from the core Back Office product list, a Sell on Web column, or Bulk Import, and categories appear automatically if they contain an active web product. Shortfalls: it is a separately purchased tiered app ("depending on the plan you purchased will determine how many products can be sent across"), publication is opt-in per product via the Sell on Web flag, and "you can later alter some elements of the product information from within the eCommerce website", so the web record can diverge. source |
| guest-loyalty-unified-profile | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | One customer record is shared by Back Office and Front Till ("Customers can be added, edited and accessed via the Back Office and Front Till") and carries title, name, DOB, phone, email, Customer Type, loyalty Card Number, Signup Location and a marketing-consent opt-in. Shortfalls: the guide documents no phone- or email-match dedup and no merge behaviour for duplicate records, and does not state that orders arriving from Epos Now Online or Order & Pay attach to the same profile - customers are created by hand at the till or in the Back Office. source |
| guest-loyalty-lifecycle-automation | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-no | The in-house Loyalty app's features are enumerated as "a customisable points-based system", promotions targeted at Customer Types, optional printed loyalty cards, and customer reports; configuration is limited to Minimum Points Spend, Points Value and a points-per-spend ratio. No triggered birthday, first-visit or lapsed win-back campaign exists. Epos Now's own answer for campaign automation is the paid Mailchimp integration, whose article says Mailchimp is where you "build workflows and custom rules so you can target your customers with timely and relevant content" - the automations run in the third-party ESP, not the platform. source |
| labor-granular-rbac | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | Staff Roles are operator-defined rather than fixed tiers, and permissions are granted per discrete action: the Void guide names "Delete Unordered Items" and "Void Ordered Items and Delete Unordered Items" as separate checkboxes, and the End of Day guide names "Close Till" and "Blind End of Day" as further per-role permissions. Shortfalls: the Adding Staff Roles guide never enumerates the permission set (it only says enabling Permissions reveals four checkboxes that expand further), and no per-location scoping of a role is documented - roles are created once at organisation level. source |
| labor-manager-override-audit | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | Reporting > Auditing provides Refunds, Discounts, No Sales and Void Lines reports, each filterable by location, device and staff and exportable to CSV/Excel; No Sales shows "the date, time, staff member and the device the no sale was processed on", and the End of Day shows all voids and deletes with the staff member and time. Shortfall: Epos Now documents no manager-override or approval step at all - actions are permitted or refused by the acting user's own staff-role permissions - so the audit trail attributes the performer and never a separate approver, and no immutability property is claimed for these reports. source |
| inventory-unit-conversion-yields | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | Master Products model the purchase pack against the sold unit: the master carries a "Unit of Sale" and a "Volume of Sale" (the number of child products inside it), and each child product is linked to the master with an "Amount" deducted per sale. The free Measurements app adds Weighed and Measured product types with a Measurement Scheme, a Unit of Purchase and a Unit of Sale with cost and sale price per measurement unit. Shortfalls: there is no separate count unit distinct from the sale unit, and no yield or waste percentage is applied to the raw-to-usable conversion anywhere in these guides. source |
| inventory-count-modes | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | Stock takes run from either the Back Office or the Front Till, and the list can be a full count or a subset filtered by supplier, category, or wet/dry - plus a Quick Scan mode that builds the count by barcode. Counts can Add To or Set the expected figure, carry a reason and notes, are reviewed for discrepancies before completion, and past stock takes are retained and browsable by date range and location, so history is not overwritten. Shortfall: nothing in the guide schedules recurring or cycle counts - every stock take is started manually by a named staff member. source |
| reporting-eod-closeout | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | The End of Day report submitted to the Back Office is one document per till close carrying opening balance, net sales inc VAT, gratuity, pay-outs, petty cash, banked, Expected, Actual and Variance, with the staff who opened and closed and the times; "Show Tenders" expands it into Tender Type, Sale, Wet/Dry, Sales by Product, Sales by Employee, Refund, Sale by Category, Void Summary, Tax Summary and Credit breakdowns, and the data is locked once submitted ("cannot be changed"). Shortfalls: the enumerated breakdowns include no discount total and no gross-sales line (net sales inc VAT only), and tips appear only for operators who have bought the separate Gratuity app. source |
| reporting-pmix-modifier-level | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | The Sales by Product report lists per product the quantity, measured quantity, sales inc tax, discount, net sales inc and exc tax, cost price, margin and margin %, filterable by location area, location, device group, device, staff, wet/dry and product tag, and exportable. Shortfalls: the documented filters offer a date range but no daypart and no revenue centre, and the report is defined over products only - modifiers are not a reported dimension (they are separate Multiple Choice products, so they can appear as ordinary product rows, but no modifier-level view of a parent item's mix is documented). source |
| multi-location-org-hierarchy | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | Multi-Site Manager defines three first-class levels - Location Areas, Locations and Devices - and a Location Area can be given "a Parent Location Area where the Location Area you are currently creating will sit within, this could be an HQ Location Area", giving four. Reporting is scoped to it ("Filter by Location Area" appears on the End of Day and Sales by Product reports only when Multi-Site Manager is used) and it is used to "Manage restrictions on access more effectively to reduce visibility of sensitive information". Shortfall: hierarchy is not in the base product - Multi-Site Manager is a chargeable AppStore add-on (Buy App or 30-day trial, monthly charge thereafter). source |
| multi-location-central-menu-publish | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | Products live in a single Back Office catalogue shared by every location, and Multi-Site Manager adds Product Groups that "allow you to segment your categories and/or products into groups that are only accessible on tills within the Location Areas you assign to them", plus Location-Area-scoped rules for Pricing, Promotions, Discounts, Multiple Choice Products and receipt content. Shortfalls: there is no publish action targeting a chosen set of locations and no publish/version history recording what was pushed, when or by whom - changes reach a till when it performs a Cloud Sync - and Product Groups require the paid Multi-Site Manager app. source |
| multi-location-price-zones | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | One item can hold several prices without duplication: the free Price Scheduling app defines Price Bands (Sale Price inc tax and Eat Out Price inc tax per product) activated by Price Schedules on a duration/time basis with a 1-99 priority to resolve collisions, and Multi-Site Manager adds "Location Area specific rules (Pricing, Promotions, Multiple Choice Products)". Shortfalls: a Price Schedule targets a single location - "you can only select one location. If you wish for this to apply to multiple locations, you will need to create additional Price Schedules" - and the only channel axis on a band is eat-in versus eat-out, with no per-marketplace or per-delivery-channel price book; location-group pricing needs the paid Multi-Site Manager app. source |
| reliability-printer-fallback | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-no | The order-printing setup wizard enumerates the whole configuration - printer brand, connection method (USB, Ethernet or built-in), detection or manual IP entry, "Choose Order Channels ... You can assign multiple channels and choose how many copies to print for each", category-to-channel assignment, and a "Print orders from this till" toggle. No backup printer, failover target or unreachable-printer alert appears anywhere in it. Epos Now's documented remedy when a ticket does not reach the line is the manual Resend Orders function, used "when an order ticket is lost, damaged, or when items need to be re-prepared". source |
| order-capture-offline-order-entry | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | Epos Now does publish an offline scope, but only for the payment leg: Offline Mode stores card transactions on the terminal when no WiFi or 4G is detected, capped by default at 10 stored transactions with merchant liability for the resulting declines and chargebacks. Shortfalls: no published statement anywhere in the 215-article knowledge base of what the till can do offline - order entry, modifiers, cash tender are all unaddressed - and the send-to-kitchen half is contradicted, the KDS guide stating "An internet connection is required" and the network guide "Any device running Epos Now requires a strong and stable internet connection to function effectively." Epos Now Standalone, the documented total-outage fallback, bypasses the till entirely. source |
| kitchen-station-routing | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | Merchant-configurable routing exists on one axis only. "Products are contained in Categories which are assigned to order channels. Printers then print from these order channels", and the KDS consumes the same key - categories "assigned to an order printer/display (e.g., KITCHEN, BAR)", with a per-screen Order Views setting to "select which product types the KDS will display". Shortfalls: no per-item routing override, no routing by order type (eat-in/takeaway/delivery drive only Display Appearance colour coding), and no revenue-centre axis in either guide. source |
| inventory-recipe-bom-costing | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-no | The knowledge base enumerates every stock feature - Stock Management, Stock Takes, Stock Movements, Master Products, Purchase Orders, Measurements, Adding Stock, Stock Reports - and no recipe or BOM entity is among them. Native depletion is single-level pack conversion (Master Product cost price, Unit of Sale, Volume of Sale = "the amount of child products within the master product"), and the master is a purchase pack, not a nestable prep item. Ingredients exist only as free text in the Product Plus extended description, with no quantity or cost. Epos Now's own documented route to "recipe costings" is the partner-billed Apicbase AppStore integration, quoted by Apicbase and billed by Apicbase from GBP175/month. source |
| reporting-realtime-dashboard | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | The freshness bar is met in the browser: the Back Office Home Page landing dashboard carries sales metrics, a comparison line chart and a top-ten product table filterable by period and by area/location, and "The graph can be refreshed to view sales made up to 5 minutes prior." Shortfalls: no dedicated mobile reporting app is documented - the published mobile clients are the Till apps, and owners are routed to the Back Office web portal; and loading is manual, since the Home Page graph is refreshed by the user and "By default, the Back Office does not load dashboards or reports automatically" until the "Do not run reports on initial page load" checkbox is unticked. source |
| commercial-autorenew-terms-published | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-yes | Both figures are in the publicly posted General Terms and Conditions of Trading (www.eposnow.com/us/terms/ redirects, without login, to the PDF). Section 10.7: 12-month Initial Term, automatic renewal for further 12-month Renewal Periods "unless and until a party provides the other party with written notice to cancel the Software licence at least 30 days before the start of the next Renewal Period", charged at then-current rates via the original billing method. Section 12 renews the Support Plan annually on the same pattern and adds a 30-day post-renewal cooling-off period cancellable "with no penalty to the Customer". source |
| payments-emv-nfc | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-yes | First-party feature pages state acceptance across the terminal range: "All our machines support contactless payments, chip cards, and mobile wallets" and eWallets "including Apple Pay, Google Pay, and Samsung Pay" on the card-machines page, with the Air device page confirming "chip and pin, contactless cards using tap to pay" and the same wallet list. Graded C, not B: the help-centre setup guides for the AMS1 Air, Pro (Saturn S1F2) and Payments Lite terminals cover assembly, network setup and boarding only and never enumerate acceptance methods. C may carry a yes on a table-stakes claim. source |
| digital-first-party-web | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | Order & Pay (AppID 1165, "powered by Yoello") is sold by Epos Now as commission-free QR/URL ordering with orders managed "through the Epos Now system". Shortfalls: not the restaurant's own domain - Step 6 fixes the site at "pay.yoello.com/v/[yourvenuenickname]" with a 12-character nickname that cannot be changed once saved; the platform is a Yoello white-label rather than in-house; and the direct-to-POS write is stated only in marketing, with Steps 3 and 5 of the setup series rendering as title-only stubs. source |
| guest-loyalty-accrual-models | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-no | The claim requires at least two native accrual models; the in-house Loyalty app documents exactly one. Its setup enumerates the entire scheme - Minimum Points Spend, Points Value ("1 point = 0.01p"), "Get 1 Point per 10p Spent", and a pro-rata versus full-qualifying-value checkbox. No visit/punch-count or spend-tier accrual exists in the article, and Epos Now's documented routes to other models are bolt-on AppStore vendors (LoyalZoo, Loyalty Dog), which the claim excludes. source |
| labor-clock-in-at-pos | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-yes | The Clock In/Out guide puts the time clock on the Front Till Log In screen: tap Clock In/Out, "Select the staff tile for the person clocking in. Enter the passcode, then select Clock In." Clock-out mirrors it with a printed confirmation, and missed clock-outs are edited in Back Office Staff Reports or Time Tracking. No separate time-clock hardware is required. source |
| hardware-kds | unknown (placeholder rationale "No public documentation located during the 2026-08-01 research pass." - the cell had never been examined) | resolve-to-partial | The KDS is first-party (software licence sold Upfront/HaaS/Software Only, with Epos Now's own 21.5-inch Android touchscreen or BYO hardware), touch-driven, and station-routed ("Order Routing: Seamlessly direct orders to different KDS stations" via categories on order channels plus per-screen Order Views). Shortfall: no course/fire timing - the KDS documents only order-age countdown timers turning tickets orange/red, and coursing elsewhere in the product is a category course number sequencing printed tickets; no course view or fire control appears in the KDS guide. source |
| commercial-pricing-published | no, grade B - The US pricing page publishes no per-location or per-termina | 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-hardware-purchase-outright | partial, grade B - A complete-system hardware bundle is advertised as an outrig | 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 A - cited to https://eposnow-marketing.s3.eu-west-1.amazonaws.com/public/terms/terms-us.pdf | upheld | Grade only, value and evidence untouched. Vendor LEGAL pages (terms, EULA, MSA, product-specific terms) are graded B corpus-wide - measured, not argued: 217 of 259 claims citing a legal-shaped URL are B. This claim was one of 21 stragglers still at A across 8 vendors. Each was inspected and every one is a genuine contract rather than a technical document, so the loose URL predicate produced no false positives here. The ladder does not name contracts explicitly, which is why this keeps recurring. source |
| extensibility-public-api-docs | yes / B - "Public REST reference (v2 and v4) with resource and type listings readable without login, NDA" | upheld | The cited /Docs/Global now 301s to /Docs/v4/index. Fetched the destination with plain curl and no credentials: 200, 29,499 bytes of real content, not an SPA shell or a login form - the nav lists every resource controller and the Types tables are rendered server-side into the HTML. The Swagger discovery document itself is public at /docs/v4/json (218,396 bytes, parses as swagger 2.0 with paths and definitions), and /Docs/V2 also returns the v2 reference anonymously. Calibrated the host first: https://developer.eposnowhq.com/Docs/v4/zzzfakepath9182 returns 404, so a soft 404 could not have passed as a hit. Value unchanged; URL re-pointed and grade raised B->A because the evidence is an OpenAPI/Swagger spec rather than a prose manual. source |
| extensibility-webhooks-push | yes / B - "Webhook resource plus a Webhook Event Type enum including CreateOrderedTransaction (305), Comp" | upheld | Re-verified the quotation rather than just the URL, per the MOVED rule. At the 301 destination /Docs/v4/index the rendered Webhook Event Type table gives exactly the values the record quotes - CompleteTransaction 304, CreateOrderedTransaction 305, CancelOrderedTransaction 308 - plus DeleteTransaction 309, so the quote is not conflated. The mechanism is push: /docs/v4/json defines path /api/v4/Webhook and definitions Webhook {BaseUrl, Triggers} and WebhookTrigger {EventTypeId, Path}, which is subscriber-supplied callback registration, not a poll endpoint. One thing the original note did not say: the ~70-entry event enum contains no Refund event, so refunds are not independently subscribable; the claim's push-vs-poll substance is unaffected and yes stands, with the gap now named in the note. source |
Sources
Every URL this record cites. 49 in total.
- https://developer.eposnowhq.com/Docs/Global
- https://www.eposnow.com/us/pricing/
- https://support.eposnow.com/s/article/Split-bill-by?language=en_US
- https://support.eposnow.com/s/article/Multiple-Choice-Products?language=en_US
- https://support.eposnow.com/s/article/Apps-Product-Matrix-Guide?language=en_US
- https://support.eposnow.com/s/article/Using-Customer-Credit-as-a-Voucher?language=en_US
- https://support.eposnow.com/s/article/Performing-a-VOID?language=en_US
- https://support.eposnow.com/s/article/Auditing?language=en_US
- https://support.eposnow.com/s/article/Kitchen-Display-Screens?language=en_US
- https://support.eposnow.com/s/article/Apps-Epos-Now-Online?language=en_US
- https://support.eposnow.com/s/article/Customer-Management?language=en_US
- https://support.eposnow.com/s/article/Apps-Loyalty?language=en_US
- https://support.eposnow.com/s/article/Master-Products-Back-Office?language=en_US
- https://support.eposnow.com/s/article/Stock-Takes?language=en_US
- https://support.eposnow.com/s/article/End-of-day-reports?language=en_US
- https://support.eposnow.com/s/article/Sales-by-Product-Report?language=en_US
- https://support.eposnow.com/s/article/Multi-Site-Manager?language=en_US
- https://support.eposnow.com/s/article/Price-Scheduling?language=en_US
- https://support.eposnow.com/s/article/Order-Printing-Setup?language=en_US
- https://support.eposnow.com/s/sitemap-topicarticle-1.xml
- https://support.eposnow.com/s/article/Moving-Part-of-a-Table-Tab?language=en_US
- https://support.eposnow.com/s/article/Mailchimp?language=en_US
- https://support.eposnow.com/s/article/Epos-Now-Payments-Offline-Payments?language=en_US
- https://support.eposnow.com/s/article/Epos-Now-Standalone?language=en_US
- https://support.eposnow.com/s/article/Running-Epos-Now-Devices-on-Your-Network-Best-Practices?language=en_US
- https://support.eposnow.com/s/article/Epos-Now-Order-Pay---Step-2?language=en_US
- https://support.eposnow.com/s/article/Add-Roles?language=en_US
- https://support.eposnow.com/s/article/Factor4?language=en_US
- https://support.eposnow.com/s/article/Tabs-and-Tables?language=en_US
- https://support.eposnow.com/s/article/Home-Page?language=en_US
- https://support.eposnow.com/s/article/Setting-up-Dashboard?language=en_US
- https://support.eposnow.com/s/article/Apicbase?language=en_US
- https://support.eposnow.com/s/article/Stock-Management?language=en_US
- https://support.eposnow.com/s/article/Apps-Product-Plus?language=en_US
- https://support.eposnow.com/s/article/Cloud-Sync?language=en_US
- https://support.eposnow.com/s/article/Understanding-your-billing?language=en_US
- https://www.eposnow.com/us/terms/
- https://eposnow-marketing.s3.eu-west-1.amazonaws.com/public/terms/terms-us.pdf
- https://www.eposnow.com/us/resources/offline-credit-card-processing/
- https://support.eposnow.com/s/article/Clock-In-Out?language=en_US
- https://support.eposnow.com/s/article/Courses?language=en_US
- https://www.eposnow.com/us/payment-processing/card-machines/
- https://www.eposnow.com/us/payment-processing/air-device/
- https://support.eposnow.com/s/article/Epos-Now-Order-Pay---Step-6?language=en_US
- https://support.eposnow.com/s/article/Step-7-Order-Management-and-Reporting?language=en_US
- https://www.eposnow.com/uk/store/software/apps/order-and-pay/
- https://www.eposnow.com/us/systems/hospitality-pos/delivery/
- https://developer.eposnowhq.com/Docs/v4/index
- https://developer.eposnowhq.com/docs/v4/json