Paytronix

Supports modifier groups nested at least three levels deep, each level with independent min/max selection counts and a forced-selection (required) flag.

menu-pricing-nested-modifiers

329th: NEW SURFACE SETTLES TWO OF THE THREE CONJUNCTS. CLAIM: modifier groups nested at least three levels deep, each level with independent min/max selection counts and a forced-selection (required) flag. VERDICT: partial/A. SURFACE: an ANONYMOUS OpenAPI 3.0.0 spec, 'Paytronix Online Ordering Api Docs' v1.0.26, 50,790 bytes, 93 paths, 64 schemas, GET https://od.pxsweb.com/admin/swagger/load.php with no key -- the spec URL declared inside the Swagger UI page at http://docs.opendining.net/api/ , which is the host developers.paytronix.com itself links as 'Online Ordering Developer Documents'. developers.paytronix.com (Sphinx, 'Integrating to Paytronix 26.6') was also crawled to a fixpoint from its own toctree: 78 pages at 200, 1 404, 1.38 MB of stripped text; neither host was named in any prior pass (only their robots.txt had been fetched, in q206). EVIDENCE that min/max/required ARE configuration, which the 320th note recorded as absent: schema OptionGroup carries `min` -- "How many options must be selected at minimum? If this is greater than 1, the option is required" -- `max` -- "How many options can be selected, at most? This field is optional; if not present or set to a falsy value, assume that there is no maximum." -- `max_unique` -- "How many different options can be selected, at most, regardless of their quantities? Only applies when `quantities` is true" -- and `multiselect` ("Can a customer select multiple options?"); per-option `min_quantity` ("How many of this option must be taken once it is selected?"). So independent min/max counts and a required flag exist per option group, at grade A, contradicting the 'no minimum-selection field documented' shortfall. THIRD LEVEL OF CHOICE EXISTS, BUT NOT AS A NESTED GROUP: OptionLevelSet is "Option level configuration, for modifying individual options (e.g. 'Light', 'Normal', 'Extra', 'No'). It can be set for the whole option group or for each option separately", each level with `price_multiplier`/`price`; the request encoding is verbatim `option_levels[Grinder][Mayo]=Normal&option_levels[Grinder][Onion]=No` (group > option > level). Dependent groups exist too: OptionGroup.option_conditions is "an array of condition lists to match for this option group to become available. If any of the first-level arrays is completely matched, the option group should become available", plus `size_conditions`. SHORTFALL (the named part that fails): option groups cannot contain option groups. In the 64-schema $ref graph, OptionGroup is referenced ONLY from MenuItem.option_groups and MenuCategory.option_groups; Option has no option_groups member; the only recursive schema in the whole spec is CategoryGroupNode (menu CATEGORIES: "May represent a group containing more nodes"). Option levels carry no min/max and no required flag, so the deepest level is not independently constrained. BOUND/CONTROLS over the whole 50,790-byte spec, tokenised, word-boundary, case-insensitive: nest 0, nested 0, sub-option 0, sub_option 0, suboption 0, sub-modifier 0, child 0, parent 0, recursive 0, depth 0; 'modifier' 1 hit, MenuItem.option_groups = "The [options/modifiers](#model-OptionGroup)", which is what fixes option group = modifier in Paytronix's vocabulary. Corroboration on the second host: the PXS Check API's own `Modifier` object (developers.paytronix.com/pxs_api_reference/check.html) is flat -- a menu item or combo item carries "A list of any modifiers (such as condiments)" and a Modifier has no modifiers member. The spec bounds the Paytronix Online Ordering product only; it is not a census of the merchant's POS menu. Retrieved 2026-09-18. https://od.pxsweb.com/admin/swagger/load.php · retrieved 2026-09-18 adversarially verified

A single modifier can carry different prices depending on the parent item and the selected size, configured as a matrix rather than by duplicating the modifier.

menu-pricing-modifier-price-by-parent-size

The size half is documented and is a real matrix: an Option Level carries an 'Extra Cost by Size' field that 'adds a fixed cost to the option price, based on the item size selected (e.g., adds $1 for Small items, $2 for Large items)', alongside Price Multiplier and a flat Extra Cost. Shortfall is the parent-item half: option groups are defined either on the individual menu item or category-wide, and the documented way to give one item a different option configuration is to tick 'Exclude from Category-Wide option' on that item and then edit the now-editable copy (help article 12582822, 'How to edit greyed out category wide options'). That is per-parent divergence by separating the definition, not one shared modifier carrying a parent-item price matrix. https://help-paytronix.theaccessgroup.com/en/articles/12600801-how-to-set-up-option-levels · retrieved 2026-08-04

Supports fractional/sectioned modifier placement (at minimum halves, ideally quarters) with independent pricing per section. differentiator

menu-pricing-fractional-placement

Not scored by this record.

The half-and-half pricing rule is operator-configurable among at least two of: charge the higher-priced half, average the halves, or charge each topping at a fraction of full price. differentiator

menu-pricing-half-and-half-rule

Not scored by this record.

Supports modifier quantity tiers (light / regular / extra / double) with a configurable price multiplier per tier, distinct from adding the modifier twice.

menu-pricing-topping-quantity-tiers

Option Levels are exactly this feature: 'Option levels allow customers to modify an individual option selection, such as specifying "double" for a topping/ingredient or "no" to exclude a given topping/ingredient', with worked examples 'Cheese on a Pizza: No, Easy, Normal, Extra' and 'Green Peppers on a Chef Salad: No, Easy, Normal'. Each level value carries: Level Value (name), 'Is Default Value?', 'Price Multiplier: Multiplies the option price by a given value (e.g., multiplies the cost by 2 for double price, or 0.5 for half price)', 'Extra Cost' (fixed add) and 'Extra Cost by Size'. Levels are created once under Menu > Option Levels and attached to an option group via a 'Levels' drop-down, so this is a tier applied to the modifier rather than adding the modifier twice. https://help-paytronix.theaccessgroup.com/en/articles/12600801-how-to-set-up-option-levels · retrieved 2026-08-04

Item base price can be defined as a grid across two variant axes (e.g. size x crust/preparation) with a per-cell price override. differentiator

menu-pricing-size-style-matrix

Not scored by this record.

Items can define an included-modifier allowance (e.g. three toppings included) that automatically charges only for overage and credits or forbids substitutions per configuration. differentiator

menu-pricing-included-allowance

Not scored by this record.

Supports combo/meal construction where components can be swapped with a price delta, and the system can automatically detect and convert eligible a-la-carte items in the cart into the combo price.

menu-pricing-combos

Not scored by this record.

Upsell/suggestive-sell prompts can be configured per item and per channel (POS, kiosk, online), and the vendor reports attach-rate on those prompts. differentiator

menu-pricing-upsell-prompts

Not scored by this record.

A single 86 action propagates automatically to POS, KDS, the vendor's own online ordering, kiosk, and connected third-party marketplaces, with a documented propagation latency.

menu-pricing-86-propagation

Not scored by this record.

Supports per-item countdown/par counts that decrement on sale and automatically 86 the item at zero, with a scheduled auto-restore. differentiator

menu-pricing-countdown-auto-86

Not scored by this record.

Menus, individual items, and prices can be scheduled to activate and deactivate automatically by day and time in the location's own timezone.

menu-pricing-dayparting

Not scored by this record.

Supports distinct price books per channel (dine-in, pickup, delivery, kiosk, each third-party marketplace) including percentage-markup rules applied to a base price rather than manual per-item entry.

menu-pricing-channel-price-books

Not scored by this record.

Supports dual pricing / cash-discount at the item level with the card price displayed as the base price, applied consistently across POS, kiosk, and online ordering, and printed on the receipt. differentiator

menu-pricing-dual-pricing

Not scored by this record.

Menu changes can be staged as an effective-dated version, previewed before publish, and rolled back to a prior version after publish. differentiator

menu-pricing-versioning-effective-dates

Not scored by this record.

Supports a central corporate menu template pushed to locations with field-level governance controlling which attributes a location may override. differentiator

menu-pricing-franchise-hierarchy

Not scored by this record.

Stores allergen flags and nutrition values per item and publishes them to online ordering and third-party menus, and can derive nutrition from linked recipe components rather than manual entry.

menu-pricing-allergen-nutrition

Not scored by this record.

Menu items and modifiers can be linked to recipes/bills of materials so that a sale depletes theoretical inventory and yields item-level theoretical food cost. differentiator

menu-pricing-recipe-linkage

Not scored by this record.

Pushes menus to third-party marketplaces through a certified direct integration (not scraping or a menu-management middleman) and surfaces per-item sync status and rejection errors to the operator.

menu-pricing-3p-menu-push

Not scored by this record.

Supports rule-based dynamic pricing where item price varies automatically by time, demand, or channel, with configurable floor/ceiling guardrails.

menu-pricing-dynamic-pricing

Not scored by this record.

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

NEW: the Paytronix KB (help-paytronix.theaccessgroup.com, 611 pages crawled) indicates Paytronix sells NO first-party payment terminal, so the claim has no object: 'Paytronix does not provide hardware or any other equipment to merchants and stores' (/en/articles/12603242). The only card-reading hardware documented is MagTek magstripe swipers (uDynamo, eDynamo) with a Paytronix KSID injected, 'to swipe Paytronix cards' (loyalty/stored value), not bank-card EMV acceptance. Wallets appear only card-not-present in online ordering: 'Enabling or disabling Apple Pay or Google Pay from the dashboard now correctly updates payment acceptance across all of that merchant's locations' (/en/articles/16150697-august-2026-release-notes). Tokenised EMV|chip|contactless|NFC|tap to pay: no terminal hits (NFC only as Apple Passbook loyalty enrolment). Neither yes nor no fits a vendor with no terminals; this looks like a scope question (peer group / scope_overrides), not research. crt.sh %.paytronix.com: 39 names, only staging/test/train/demo/corp hosts, no docs surface. Retrieved 2026-09-16. || 329th: 329th: two new surfaces, both corroborating that the claim has no object, still held unknown as a scope question. (1) The anonymous Paytronix Online Ordering OpenAPI 3.0.0 spec (https://od.pxsweb.com/admin/swagger/load.php , 50,790 b, 93 paths, 64 schemas) has a purely card-not-present payment surface: /tokens/spreedly_signature (Spreedly tokenisation, 43 mentions), /account/apple_pay_session/{order_id}, /tokens/google_pay, /account/mobile_pay_card, /account/cards. Tokenised controls over the whole spec: emv 0, nfc 0, chip 0, swipe 0, 'card reader' 0, 'pin pad' 0, 'tap to pay' 0. POISON: 'contactless' has 2 hits and BOTH are `contactless_delivery` ("For orders using DoorDash delivery, set this to true if you want to enable contactless delivery"); 'terminal' has 1 hit and it is posPing -- "The status ping request is used to notify Paytronix the connectivity status of the Point Of Sale terminals" -- i.e. the terminals are the MERCHANT's POS, whose uptime Paytronix is told about. (2) developers.paytronix.com/nfc_loyalty.html, the only NFC page on the 78-page developer site: "If you are looking to create an NFC loyalty integration, please contact us by emailing support@paytronix.com for NFC loyalty integration documentation" -- NFC at Paytronix is loyalty credential reading and its documentation is not public. No first-party payment terminal appears on either new host. Retrieved 2026-09-18. adversarially verified

Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. differentiator

payments-softpos-tap-to-pay

Not scored by this record.

Vendor ships a handheld that takes EMV/NFC payment at the table, including tip prompt and check splitting, without carrying the card away.

payments-pay-at-table

Not scored by this record.

Guest can scan a QR code on the printed check or table tent to view and pay the check from their own phone, with the payment closing the check in the POS automatically. differentiator

payments-qr-guest-pay

Not scored by this record.

Supports both pre-auth-then-tip-adjust and on-device tip prompt flows, with a documented batch/adjust window and a manager screen for unadjusted tips.

payments-tip-adjust

Not scored by this record.

Configurable tip pooling and distribution rules (by hours worked, sales, role percentage, or points) that produce a per-employee tip allocation exportable to payroll. differentiator

payments-tip-pooling

Not scored by this record.

Card payments can be captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. differentiator

payments-offline-store-and-forward

Not scored by this record.

Vendor publicly documents who bears the loss when a stored offline transaction declines on reconnect, and surfaces a post-reconnect report of failed offline payments. differentiator

payments-offline-decline-liability

Not scored by this record.

First-party gift cards with real-time balance tracking, redeemable across every location in the group and through the online-ordering channel.

payments-gift-cards

Stored value/gift is a founding Paytronix product line sold alongside loyalty across the chain's locations and channels. https://www.paytronix.com/platform · retrieved 2026-08-01

House/on-account tabs with per-account credit limits, running balance, and periodic statement or invoice generation.

payments-house-accounts

Not scored by this record.

A single check can be settled with multiple tenders and split by seat, by item, by even shares, or by arbitrary amount, with no hard cap below eight ways.

payments-split-tender

Not scored by this record.

Voids, refunds, discounts, and no-sales require role-based authorization (manager PIN or approval) and write to an immutable audit log identifying the approver.

payments-refund-void-controls

Role-based authorization exists for the transactions Paytronix owns: the Online Ordering permission table carries 'O&D - Refunds - Controls access to the ability to process refunds' and 'O&D - Refund Reasons - Controls access to the Refund Reasons page', assignable per custom permission group at Read/Write/Delete/New/Update level (help article 13731009), and Managing Completed Orders (12609529) requires a reason on every refund: 'Under Refund Reason, select a refund reason'. An attributed void trail exists for stored value: the Fraud Void Detail Report records Check No., Terminal ID and Cashier ID ('in the case of CSR adjustments, this is the Paytronix user number') and 'is updated in real time' (12582072). Shortfalls: no manager-PIN or second-approver flow is documented - authorization is a standing permission gate, not per-transaction approval; the online-ordering payment activity log shows 'charges, refunds, and adjustments' but no document attributes an online-order refund to the admin user who issued it (12603269); no document asserts any of these logs are immutable; and register-side voids, discounts and no-sales are enforced by the integrated POS, not Paytronix - the Aloha guide has the operator build access levels in Aloha CFC (12591641). https://help-paytronix.theaccessgroup.com/en/articles/12582332-online-ordering-permissions · retrieved 2026-08-04

In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator

payments-chargeback-tooling

Not scored by this record.

Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator

payments-card-on-file

Not scored by this record.

Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator

payments-payout-timing

Not scored by this record.

A single account can route settlement funds to different bank accounts per location or legal entity (separate MIDs or split settlement) under unified reporting. differentiator

payments-multi-entity-routing

Not scored by this record.

Vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance / P2PE listing available to merchants on request.

payments-p2pe-pci4

Not scored by this record.

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

Paytronix First-Party Delivery is a geography-and-fee configuration, not a driver module. The Delivery Settings article frames the operator's own drivers as a fulfilment choice - 'You may choose to deliver using your own staff driver' - and the only thing it asks the operator to set up is coverage: on enabling First-Party Delivery a notice says to 'configure at least one of the following: Delivery Radius, Delivery Zones, or Zip/Postal Codes', followed by fees, hours, cutoffs and minimums. No driver is ever created, named, assigned or reported on. The delivery data model corroborates: in the Online Ordering OpenAPI document the only driver-shaped object on an order is a third-party `courier` carrying a name and a phone number plus a tracking URL, populated by the delivery service provider, and the whole 81-document Paytronix API reference at developers.paytronix.com contains the words `driver`, `dispatch` and `courier` zero times. https://help-paytronix.theaccessgroup.com/en/articles/12581935-what-are-delivery-settings · retrieved 2026-09-09 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

The delivery surface Paytronix gives store staff is the Online Ordering tablet, and its Delivery workflow is an ordered list of status labels with optional SMS text, not a dispatch board. The article states that an operator who has not customised anything 'will see the two default steps for both Takeout and Delivery' - Submitted and Done - and that further steps are added with an Add Step button, each carrying a name and a customer SMS message. Nothing in that surface holds driver availability, elapsed time per order, or an assignment; `dispatch board`, `driver assignment`, `expo screen` and `run batching` occur zero times across the 683-document corpus, and `dispatch` occurs exactly twice - once describing what happens inside Focus POS rather than in Paytronix, once naming a messaging test-send feature in the July 2026 release notes. Multi-order run batching has no analogue at all: third-party delivery is dispatched by the provider, and first-party delivery is dispatched by the operator off-system. https://help-paytronix.theaccessgroup.com/en/articles/12601346-takeout-and-delivery-workflow-steps-tablet-application · retrieved 2026-09-09 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

Every element of the claim is configured per zone. Zones are drawn on a map with a rectangle or polygon tool, and the panel beside the map carries four independent per-zone settings: 'Fee: Delivery fee for this zone', a 'Fee %' taken as a percentage of order total, a Delivery Time that is lead time additive to the base order delivery time, and 'Minimum Subtotal: Minimum subtotal required for delivery to this zone'. A per-zone fee overrides the flat Delivery Fee set on the Delivery Settings page and the per-zone time is added to the General Settings lead time, so the zone value is the operative one. Application is automatic from the guest's address rather than a staff choice - the platform routes an address inside a zone to first-party delivery and one outside it to a delivery service provider, and where zones overlap 'the system will automatically choose the zone with the smaller delivery fee'. The Online Ordering API carries a matching address-validation endpoint and a DeliveryArea schema. https://help-paytronix.theaccessgroup.com/en/articles/12600832-how-do-i-create-delivery-zones-using-a-drawn-map · retrieved 2026-09-09 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.

Menu, pricing, modifiers, and photos publish from the POS master menu out to connected third-party marketplaces, including channel-specific price markups, without maintaining a separate menu in each portal.

delivery-menu-push

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.

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

Online Ordering is a first-party platform module on the brand's own channels, sold alongside loyalty rather than as a marketplace. https://www.paytronix.com/platform · retrieved 2026-08-01

The web/app ordering menu is generated from the same POS menu record as in-store — one item edit propagates to all first-party digital channels without a separate digital menu build.

digital-menu-single-source

Whether the ordering menu is single-sourced depends entirely on which POS the operator runs, and for most of the named list it is not. The Paytronix Online Ordering menu is authored in Paytronix and then bound to the POS by ID: 'you may need to map your menu items to sync to the POS', and the vendor's own table splits eight POS types into two auto-mapping ones, Revel and Toast, against six requiring manual mapping - Aldelo, Breadcrumb, Focus, Micros 3700, POSitouch and POSLavu - plus SpeedLine. Manual mapping is per category, per item and per category-wide option, must be repeated for every new item added, and the Auto-Map alternative is described as 'a "best guess" by our system to properly map the items'. Genuine single-sourcing exists where the POS pushes the menu: the March 2026 release notes (help article 14040785) record that Square menu sync continues to update items, prices, descriptions and structure in the ordering menu. Shortfall is that this is a per-integration property, not a platform one, and on a manually mapped POS a new item is a separate digital menu build plus a mapping chore. https://help-paytronix.theaccessgroup.com/en/articles/12609465-how-do-i-map-menu-items-to-my-pos · retrieved 2026-09-09 adversarially verified

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

Two of the three components are documented. Saved payment: 'Your customers can create an account through Paytronix Online Ordering, which can be used to store credit card details securely', 'stored credit card details are automatically populated' at checkout when logged in, and 'All stored credit card information is encrypted and is not viewable by Paytronix Online Ordering or any of its clients'. Reorder: 'Once you have an account, you'll be able to view your order history and re-order past orders', via a Past Orders button on the order confirmation screen, the Account > Orders tab, or a reorder link in the confirmation email (help article 12573473), and the branded mobile app performs 'the steps of a reorder' from item selection (12599051). Shortfall: saved delivery addresses are not documented anywhere in the help centre - searches for saved/stored addresses surface only delivery zones, AVS address verification and the delivery instructions field - and the docs say 'encrypted' rather than describing a tokenization scheme. https://help-paytronix.theaccessgroup.com/en/articles/12600877-can-my-customers-save-their-credit-card-information-to-expedite-orders · retrieved 2026-08-04

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.

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

450+ integrations including 30+ POS feed one guest record across ordering, kiosk and in-store; documented dedup/merge behaviour not public. https://www.paytronix.com/platform · retrieved 2026-08-01

Orders arriving from third-party marketplaces (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. differentiator

guest-loyalty-thirdparty-identity-attach

Not scored by this record.

Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.

guest-loyalty-accrual-models

Marketed as "the most core design options in the industry" for custom programme design; specific accrual models are not enumerated. https://www.paytronix.com/platform · retrieved 2026-08-01

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

Marketing automation and segmentation are listed as suite solutions; named always-on birthday/win-back campaigns not documented on the platform page. https://www.paytronix.com/platform · retrieved 2026-08-01

Sends both email and SMS campaigns natively from the platform, not solely by handing the list to a third-party ESP. differentiator

guest-loyalty-native-email-sms

Not scored by this record.

Captures per-channel marketing consent with timestamp and source of consent, and honors revocation received by any reasonable means (not just the STOP keyword) across all channels.

guest-loyalty-consent-management

Not scored by this record.

Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.

guest-loyalty-10dlc-registration

Not scored by this record.

Reports redemption and incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. differentiator

guest-loyalty-campaign-attribution

Not scored by this record.

Provides self-serve export of the full guest list and transaction history, including contact PII, via CSV or API, without a vendor fee or support ticket. differentiator

guest-loyalty-data-export-portability

Not scored by this record.

Exposes a documented outbound guest and order event API or webhook stream that a CDP or marketing platform can subscribe to (e.g. Olo, Punchh, Bridg, Klaviyo). differentiator

guest-loyalty-cdp-event-api

Not scored by this record.

Triggers post-transaction feedback requests and routes responses by score, sending low scores to private service recovery and high scores toward public review sites. differentiator

guest-loyalty-review-capture-routing

Not scored by this record.

Includes a native referral mechanic with per-guest codes or links, attribution of the referred guest's first order, and two-sided rewards.

guest-loyalty-referral-program

Not scored by this record.

Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance, as an alternative to requiring a branded app download. differentiator

guest-loyalty-wallet-pass

Not scored by this record.

Provides admin tooling to fulfill guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records.

guest-loyalty-privacy-rights-tooling

Not scored by this record.

Enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log.

guest-loyalty-redemption-fraud-controls

Not scored by this record.

Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing (claim-level; verify it is a shipped product feature, not a roadmap statement). differentiator

guest-loyalty-ai-offer-recommendation

Not scored by this record.

Offers native stored-value/gift card balances tied to the same guest profile and redeemable across all locations of the brand.

guest-loyalty-stored-value-gift

Not scored by this record.

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

Paytronix has no terminal of its own and no employee-time surface; where employee identity is needed it is configured inside the third-party POS. The Aloha setup article walks the operator through building the access level in Aloha's own Configuration Center, down to POS-native payroll settings such as 'Consider Jobcode as salaried for close payroll', which is an Aloha field the operator ticks in Aloha. Across the whole 683-document corpus - 593 knowledge-base articles, the 81-document Paytronix API reference and the Online Ordering API docs - `clock in`, `time clock`, `time card`, `timesheet`, `punch in`, `attendance` and `overtime` occur zero times, and the single `payroll` occurrence is the Aloha field quoted above. The 743 property names in the Online Ordering OpenAPI document contain no employee, clock or shift field. https://help-paytronix.theaccessgroup.com/en/articles/12591641-aloha-pos-paytronix-manager-user-definition-for-gift-cards · retrieved 2026-09-09 adversarially verified

Captures a photo at punch (or performs facial verification) attached to the timecard entry, with a photo-only mode available that stores no biometric template. differentiator

labor-photo-punch-verification

Not scored by this record.

Supports mobile clock-in restricted by geofence or location validation for staff who do not punch at a fixed terminal.

labor-geofenced-mobile-punch

Not scored by this record.

Records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, with the behavior documented. differentiator

labor-offline-time-punch

Not scored by this record.

Permissions are grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers.

labor-granular-rbac

Roles are genuinely custom, not fixed tiers: 'Permission Groups are collections of access rights and privileges... Each merchant can have multiple permission groups tailored to different roles', created via User Administration > Manage Permission Groups, and each web-page permission can be granted at Read / Write / Delete / New / Update level. The Online Ordering permission table (help article 12582332) enumerates ~50 discrete permissions including 'O&D - Refund Reasons', 'O&D - Add / Remove Items', 'O&D - Edit Items' and one permission per report page. Location scoping exists: 'Each user can only view data for the stores they are authorized to see. This is enforced automatically' (help article 15723331). Shortfall: the permissions govern the Paytronix merchant portal and Order & Delivery back office, not the register — void, comp, discount approval, drawer open and price change at the terminal are configured in the integrated POS (the Aloha guide, help article 12591641, has the operator build a Jobcode and POS Access Level in Aloha CFC for Paytronix functions). Elevated Analytics roles are also not self-service: 'Restricted Querier access... contact Paytronix Support.' https://help-paytronix.theaccessgroup.com/en/articles/13731009-creating-managing-custom-permission-groups · retrieved 2026-08-04

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

There is an attributed, queryable trail for the transactions Paytronix owns. The Fraud Void Detail Report 'contains information about all stored value void transactions that have been processed by the Paytronix servers. The transactions usually come through the POS, but some come directly through the web via a CSR action', and carries Check No., Terminal ID and 'Cashier ID - the cashier who was logged in to the terminal when the transaction took place; in the case of CSR adjustments, this is the Paytronix user number.' It is queryable by date range, single store, store group or all stores, and 'This report is updated in real time.' Companion Fraud Cashier Activity Detail/Summary and General Manager Card Activity Detail reports do the same for card activity. Shortfalls: attribution is to the terminal's logged-in cashier, not to a separately identified approving manager; coverage is Paytronix stored-value and loyalty transactions only, not POS voids, comps or discounts generally; and no Paytronix document asserts the trail is immutable. https://help-paytronix.theaccessgroup.com/en/articles/12582072-fraud-void-detail-report · retrieved 2026-08-04

Builds and publishes employee shift schedules inside the same platform that holds the timekeeping data, rather than requiring a third-party scheduling app. differentiator

labor-native-scheduling

Not scored by this record.

Generates recommended staffing levels or labor hours by daypart from the operator's own POS sales history, not just a static template. differentiator

labor-demand-labor-forecast

Not scored by this record.

Displays labor cost as a percentage of sales in real time during service on a manager view or POS, not only in end-of-day or next-morning reports. differentiator

labor-realtime-labor-percent

Not scored by this record.

Warns or blocks at clock-in when an employee is approaching or would cross a configured overtime threshold, before the overtime is incurred. differentiator

labor-overtime-prevention

Not scored by this record.

Configures meal and rest break rules per state or jurisdiction, prompts required break attestation, and flags missed breaks for premium pay. differentiator

labor-break-compliance-by-state

Not scored by this record.

Supports predictive-scheduling ordinances by tracking advance-notice deadlines for published schedules and calculating predictability pay owed for employer-initiated changes.

labor-fair-workweek-support

Not scored by this record.

Enforces minor-labor restrictions (age-based maximum hours, prohibited time windows, school-day limits) at both scheduling and clock-in.

labor-minor-labor-rules

Not scored by this record.

Computes tip pooling and tip-outs automatically per shift from configurable rules (percentage of sales, hours worked, points, or role), rather than requiring a manual spreadsheet.

labor-tip-pooling-rules

Not scored by this record.

Retains a per-shift, per-employee record of tips received, amounts contributed to the pool, and amounts distributed from the pool, exportable for audit.

labor-tip-distribution-audit-trail

Not scored by this record.

Payroll export separates cash from charged qualified tips and carries a Treasury tipped-occupation code, supporting the W-2 Box 12 code TP and Box 14b reporting required for tax year 2026. differentiator

labor-qualified-tips-w2-reporting

Not scored by this record.

Vendor processes payroll itself as a first-party product (tax filing and direct deposit), as opposed to exporting to a third-party payroll provider only. differentiator

labor-native-payroll

Not scored by this record.

Exports timecards, wages, and tips in documented formats or via direct integration for at least two major payroll providers (e.g. Gusto, ADP, Paychex, QuickBooks).

labor-payroll-export-formats

Not scored by this record.

Employees can request shift swaps or claim open shifts in a self-service app, subject to a manager approval workflow that enforces overtime and role eligibility. differentiator

labor-shift-swap-workflow

Not scored by this record.

Provides digital new-hire onboarding that collects W-4 and I-9 documentation and supports E-Verify submission.

labor-digital-onboarding-i9

Not scored by this record.

Reports per-employee sales performance metrics (average check, items or category attachment rate, void and comp rate) by server or cashier. differentiator

labor-server-performance-metrics

Not scored by this record.

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

Paytronix menu items have no ingredient layer to cost. The item model exposed to operators is category, item, option group, option and option level, and the only stock-facing control on an item is a binary availability toggle - the article's whole procedure is to 'click the Sold Out button next to that item'. There is no component, no sub-recipe and no cost field anywhere in it. `recipe` occurs in exactly one corpus document, help article 13687314 on item-level feedback, where it names something for the kitchen to check after a low rating rather than a Paytronix object; `bill of materials` occurs zero times. The Report Center index at help article 12580647, which introduces itself as an index and guide to all reports that exist, has no food-cost, plate-cost or ingredient category among its General, Stored Value, Loyalty/Comp, Fraud, Billing, Charge, Variance and System groups. https://help-paytronix.theaccessgroup.com/en/articles/12583131-how-to-mark-an-item-out-of-stock · retrieved 2026-09-09 adversarially verified

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

There is no purchase, recipe or count unit in Paytronix to convert between. An item's only stock state is the manual availability flag the article documents - 'click the Sold Out button next to that item', with 'Back in Stock' and 'Back in Stock Tomorrow' as the two ways back - so nothing is ever measured in a unit at all. Unit conversion, waste and usable-yield fields appear nowhere in the corpus, and the 743 property names in the Online Ordering OpenAPI document contain no unit, conversion, yield or waste property. `unit conversion` occurs zero times, and `yield` occurs once corpus-wide, in a marketing sentence about campaigns. https://help-paytronix.theaccessgroup.com/en/articles/12583131-how-to-mark-an-item-out-of-stock · retrieved 2026-09-09 adversarially verified

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

Paytronix records no counts, so it cannot record count history. The documented stock workflow is entirely a per-item on/off switch: the operator navigates to the menu, selects a category and then must 'click the Sold Out button next to that item', after which the two offered options are to bring it back immediately or the following morning. Nothing is counted, no quantity is entered and no variance is retained. `physical inventory`, `cycle count` and `spot count` occur zero times across the corpus, and none of the eight documents containing `inventory` describes a Paytronix count: five are gift-card stock or data migration, two are advisory prose about the operator's own kitchen, and the eighth is the March 2026 release note that defines the term for this product outright - it calls the sold-out / in-stock flag the inventory status. The Out of Stock Report described in the Online Ordering dashboards article is an audit of who toggled which item and when, not a count. https://help-paytronix.theaccessgroup.com/en/articles/12583131-how-to-mark-an-item-out-of-stock · retrieved 2026-09-09 adversarially verified

Provides a mobile/tablet counting app supporting barcode or QR scanning that continues to accept counts with no network connectivity and syncs on reconnect.

inventory-mobile-count-offline

Not scored by this record.

Ships pre-built electronic vendor catalog and order-transmission integrations with named broadline distributors (e.g. Sysco, US Foods, Performance Food Group) that send purchase orders and receive invoices electronically rather than by emailed PDF. differentiator

inventory-vendor-catalogs-edi

Not scored by this record.

Ingests supplier invoices from photo, PDF, or email and extracts line-item detail (item, quantity, unit, price) into the inventory ledger without manual line entry. differentiator

inventory-invoice-ocr

Not scored by this record.

Tracks per-item purchase price history across invoices and alerts when a received price exceeds the prior or contracted price by a configurable threshold. differentiator

inventory-price-change-alerts

Not scored by this record.

Maintains par levels per item per location and generates suggested purchase order quantities from on-hand versus par, with at least one mode driven by a sales forecast rather than a static par. differentiator

inventory-par-auto-suggest

Not scored by this record.

Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.

inventory-waste-logging

Not scored by this record.

Supports inter-location inventory transfers as a two-sided transaction crediting the sending location and debiting the receiving location, with an in-transit or approval state.

inventory-transfers

Not scored by this record.

Supports a commissary/central kitchen model where one location produces prep items and issues or sells them to other locations at a computed transfer cost.

inventory-commissary

Not scored by this record.

Captures lot/batch numbers at receiving and links them through production to sales or transfers, enabling a backward and forward recall trace.

inventory-lot-traceability

Not scored by this record.

Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.

inventory-shelf-life-expiry

Not scored by this record.

Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting.

inventory-bar-partial-bottle

Not scored by this record.

Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.

inventory-cogs-gl-export

Not scored by this record.

Inventory and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator

inventory-native-not-partner

Not scored by this record.

Joins recipe cost to actual item sales mix to report contribution margin per menu item, and flags items whose margin fell below a configured threshold after ingredient cost changes. differentiator

inventory-menu-margin-linkage

Not scored by this record.

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 live-sales half is documented outright: 'All reporting for sales and orders is presented in real-time in the Reporting section of your Paytronix Online Ordering account dashboard.' Store-level dashboards carry Most Recent Data Sync, Orders Over Time, Sales Over Time, Submitted Orders, Average Check and Sales By Day (help article 12609750), and the Fraud Void Detail report is likewise 'updated in real time'. Shortfall: browser only. The only off-premise mobile access Paytronix documents for the back office is a web shortcut - 'save the Paytronix Online Ordering backoffice link to your homescreen' via iPhone Share > Add to Home Screen or Chrome > Add to homescreen (help article 12573540). Paytronix's native mobile apps in the help centre are guest-facing loyalty/ordering apps; no manager reporting app is documented. https://help-paytronix.theaccessgroup.com/en/articles/12601037-is-reporting-done-in-real-time · 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

Most of the EOD line items exist in one exportable, schedulable document, but there is no close-out artefact and no cash side. The PXS Analytics Sales dashboard carries 'Sales by Payment Type, Tender Total Breakdown' alongside Total Sales, Average Tax, Average Tip, Refunded Orders and Canceled Orders; the Detailed Reports dashboard adds a Refunds Report and Tax/Fees Reports; and any dashboard can be downloaded whole as CSV or PDF and put on a scheduled recurring delivery. Shortfall is threefold: discounts live in a separate Discounts dashboard rather than the same document; there is no expected-cash-deposit figure anywhere, because cash is settled by staff at pickup and never enters Paytronix; and there is no day-close operation - these are date-filtered analytics over the ordering channel, not a nightly reconciliation a manager signs off. `z report` and `daily report` occur zero times across the corpus, and the single `end of day` occurrence is a heading in an item-feedback article recommending a daily scan of ratings, not a report. Scope note: this covers the online-ordering channel only, never whole-store sales, which stay in the POS. https://help-paytronix.theaccessgroup.com/en/articles/12601856-what-online-ordering-reports-and-dashboards-are-available-in-the-pxs · retrieved 2026-09-09 adversarially verified

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

Item and modifier mix both exist, but not with the sales split or the dimensions the claim names. The PXS Analytics KPI Summary reports 'Top Items, Top Options (or Modifiers)', the store-level Online Ordering General Reports carry Top Items and Top Options, the merchant-level General Reports add Best Sellers and Least Sold Items, and the Detailed Reports dashboard carries 'Check Level Report, Item Level Check Details, Item Rollup' - so quantity at both item and modifier level is available and exportable as CSV. Three shortfalls: the item and option reports are rankings by volume, with no per-item gross-versus-net sales split published anywhere; there is no revenue-center concept in the product at all; and daypart is only reachable through generic date and time filters plus a Spend by Hour of Week visualisation, not as a named daypart dimension. Scope is also narrower than the claim assumes - these cover the online-ordering channel, never whole-store product mix, which stays in the POS. https://help-paytronix.theaccessgroup.com/en/articles/12601856-what-online-ordering-reports-and-dashboards-are-available-in-the-pxs · retrieved 2026-09-09 adversarially verified

Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.

reporting-comps-voids-audit

Not scored by this record.

Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.

reporting-cash-over-short

Not scored by this record.

Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.

reporting-labor-productivity

Not scored by this record.

Reports per-server metrics including average check, items per check, attachment rate for named categories, and tips as a percentage of sales. differentiator

reporting-server-scorecards

Not scored by this record.

Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator

reporting-channel-profitability

Not scored by this record.

Provides a consolidated multi-location report with side-by-side location comparison and drill-down from group total to a single location and then to an individual transaction. differentiator

reporting-multiloc-drilldown

Not scored by this record.

Includes a self-service report builder letting a non-developer choose dimensions, measures, and filters and save the result, rather than only fixed canned reports. differentiator

reporting-custom-report-builder

Not scored by this record.

Supports scheduling any report for automatic recurring delivery by email or to a shared destination on a defined cadence and recipient list.

reporting-scheduled-delivery

Not scored by this record.

Offers automated recurring bulk export of transaction-level raw data to a customer-controlled destination (S3, SFTP, Snowflake, BigQuery, or equivalent), not just manual CSV download. differentiator

reporting-raw-warehouse-export

Not scored by this record.

Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator

reporting-public-api

Not scored by this record.

Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator

reporting-webhooks

Not scored by this record.

API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator

reporting-api-not-upcharged

Not scored by this record.

Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator

reporting-tier-paywall

Not scored by this record.

Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator

reporting-history-retention

Not scored by this record.

Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator

reporting-anomaly-alerts

Not scored by this record.

Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.

reporting-nl-query

Not scored by this record.

Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator

reporting-guest-cohorts

Not scored by this record.

Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator

reporting-sales-forecast

Not scored by this record.

Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.

reporting-tip-tax-compliance

Not scored by this record.

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

One named grouping level exists between merchant and store, and reporting can be scoped to it. Store Groups 'allow you to create, and edit groups of stores used in promotions and reporting', carry a category of Concept, Region, Franchisee or Other, are built by checkbox selection or file upload, and can be Fixed or Auto-add for new stores. Reports honour them - the Fraud Void Detail Report is queryable by 'single store, store group or all stores' (help article 12582072) - and Enterprise Settings Management groups 'align stores with similar settings, such as taxes, order types offered... or payment types accepted' for bulk changes (12591900). Shortfalls: the structure is one flat grouping level, not a hierarchy - no document describes nesting groups (region > district > store) and ESM groups are overlapping many-to-many labels ('you may assign multiple sites to multiple groups'); and user permission scoping is documented per individual store, not per group: 'Each user can only view data for the stores they are authorized to see' (15723331). https://help-paytronix.theaccessgroup.com/en/articles/12609161-store-group-maintenance · retrieved 2026-08-04

A corporate-level menu can be authored once and published to a chosen set of locations in a single action, with a publish/version history showing what was pushed, when, and by whom.

multi-location-central-menu-publish

The publish half is real and is a single action; the history half is not documented. From the Merchant page an operator opens Menu then Sync Menus, picks the location holding the updated menu as the source, and can 'choose the individual destinations' or Select All, with a separate toggle for whether disabled items travel too - one Synchronize Menus click, ending in a success message. The vendor prefers it to copying because 'it keeps the menu id intact and, therefore, does not break repeat orders'. Enterprise Settings Management does the same for non-menu values, batch-editing store hours, prices and promo codes across a group or All, immediately or scheduled. Shortfall is the audit trail the claim requires: nothing in the corpus describes a publish or version history recording what was pushed, when and by whom, there is no rollback, and the confirmation is a transient banner rather than a retained record. https://help-paytronix.theaccessgroup.com/en/articles/12591916-synchronizing-menus-in-a-merchant-account · retrieved 2026-09-09 adversarially verified

Corporate menu items expose per-field override rules so a location can change some attributes (e.g. price, availability) while corporate locks others (e.g. name, image, recipe), and locked fields are not editable at store level. differentiator

multi-location-local-override-policy

Not scored by this record.

Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.

multi-location-price-zones

Central per-group price management exists, but not as price zones on a single item record. Enterprise Settings Management lets an operator 'make the same edit to multiple locations at once' by selecting a restaurant group or All, publishing immediately or on a schedule, and 'Store hours, prices, and promo codes are just a few examples of settings that support batch editing'; Individual Settings Management bulk-edits location-specific values from one view. The underlying architecture is per-store menu copies: Synchronizing Menus in a Merchant Account (help article 12591916) propagates a source store's menu to destination stores, where 'Syncing menus is typically better than copying menus because it keeps the menu id intact and, therefore, does not break repeat orders.' Shortfalls: per-location-group divergence is achieved by batch-editing each store's own menu copy, not by a price tier on one shared item; no per-order-channel price dimension is documented; and the daypart mechanism (Advanced Menu Management - Daily Specials, 12601898) schedules availability only - 'if your item is only available on certain days, check the Not available on all other days' - with no time-based price. https://help-paytronix.theaccessgroup.com/en/articles/12581918-enterprise-settings-management · retrieved 2026-08-04

Menu, price, and promo changes can be scheduled to activate at a future date/time interpreted in each target location's own timezone, and can be rolled back after activation. differentiator

multi-location-scheduled-publish

Not scored by this record.

A new location can be provisioned by cloning a documented configuration template (menu, taxes, roles, printers, modifiers, tenders) rather than being configured from scratch, and the vendor publishes the expected time-to-open. differentiator

multi-location-new-store-template

Not scored by this record.

The permission model distinguishes a franchisor/corporate tenant from an independently-owned franchisee tenant, so corporate can see franchisee sales and enforce config while the franchisee owns its own employees, banking, and labor data. differentiator

multi-location-corp-vs-franchisee-roles

Not scored by this record.

Calculates franchise royalty, ad-fund, and marketing-fee amounts automatically from POS net sales on a defined schedule, with a configurable royalty basis (gross vs net of discounts/comps/third-party). differentiator

multi-location-royalty-calculation

Not scored by this record.

Supports automated ACH/debit collection of calculated royalties and fees from franchisee accounts, with a franchisee-visible statement of what was charged.

multi-location-royalty-collection

Not scored by this record.

Provides above-store reporting that aggregates sales, labor, discounts, voids, and item mix across any selected set of locations in one view, with store-vs-store ranking and variance flags.

multi-location-consolidated-reporting

Not scored by this record.

Item-level sales roll up across locations under a shared corporate item ID even when stores have renamed or locally priced the item. differentiator

multi-location-normalized-item-rollup

Not scored by this record.

Gift cards issued at one location are redeemable at any other location in the brand, with a reported outstanding-liability balance and inter-store settlement/redemption reconciliation between owners.

multi-location-cross-location-giftcard

Not scored by this record.

A single customer loyalty profile, balance, and stored order history is shared across all locations in the brand rather than being per-location.

multi-location-cross-location-loyalty

Not scored by this record.

A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. differentiator

multi-location-multi-brand

Not scored by this record.

Tax configuration is per-location with support for multiple simultaneous tax rates, jurisdiction-specific rules (e.g. prepared-food vs grocery, inclusive vs exclusive tax), and per-location tax exemptions.

multi-location-multi-tax-jurisdiction

Not scored by this record.

Supports locations operating in different currencies and languages within one enterprise account, with consolidated reporting converted to a reporting currency.

multi-location-multi-currency-locale

Not scored by this record.

Produces an immutable audit log of who changed which configuration object (price, tax, permission, discount) at which location and when, exportable or queryable by corporate. differentiator

multi-location-config-audit-log

Not scored by this record.

Supports SSO via SAML or OIDC against the customer's identity provider for back-office/above-store users, with SCIM or equivalent for automated deprovisioning. differentiator

multi-location-enterprise-sso

Not scored by this record.

Publishes a documented multi-location API (or data warehouse/BI export) that returns transaction-level data across all locations in one authenticated call, without per-location credentials. differentiator

multi-location-enterprise-api

Not scored by this record.

Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.

multi-location-central-labor-policy

Not scored by this record.

Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.

extensibility-public-api-docs

REPLACES an undated first-pass placeholder that said '450+ integrations advertised; no self-serve public API reference located at check time' -- while extensibility-oauth-partner-apps sits at no A in this same record citing this very page, retrieved 2026-08-04. developers.paytronix.com serves 'Integrating to Paytronix 26.6 documentation' with no robots.txt (404, allowed under RFC 9309) and returns HTTP 200 anonymously with the reference body rendered server-side. Its contents page is a complete public API reference: a 'Paytronix Server API Reference' section enumerating roughly forty services by name -- Action to Load (ATL), Balance Transfer, Campaign Feedback, Challenge, Check, Checkin, Coupon, CSR, Enrollment, Geolocation, Gift, Guest Authentication, Guest Management, Message, OAuth, One Time Password, Payment, Push Messaging, Sale, Store, Subscription, Survey, Transaction and Web Sale Order Lookup among them -- plus 'JSON Encoding Details', 'API Authentication', an 'API Change Log', an 'Errors Overview', and functional guides for guest website and mobile registration, login, SSO flows, Apple Passbook and push messaging. Nothing on the path required a signed agreement, NDA or sales call. https://developers.paytronix.com/pxs_api_reference/authentication.html · retrieved 2026-09-01

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.

The vendor publishes its partner/marketplace commercial terms (referral fee, revenue share percentage, or per-location partner fee) in public documentation.

extensibility-partner-revshare

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

The API reference enumerates the partner-app auth mechanism and it is a static shared secret: 'All API calls to Paytronix require that an integration identifier and secret, essentially a username and password for your integration, be sent as part of the request', sent 'with every API call in an HTTP Basic authorization header (formatted as the base64-encoded representation of identifier:secret)', with 'the identifier and secret values will be provided by the Paytronix integrations team once the integration process has begun.' Paytronix does run OAuth 2.0, but the OAuth Service page scopes it to guests, not partners - 'OAuth Service for REST allows for an integrator to authenticate a guest in a merchant program', with grants (password, OTP, authorization code, refresh, user fields) and scopes (user_read, user_write, account_read, account_write, register) that are all about a guest's own account. There is no operator-facing consent screen, no per-app scope grant and no operator-side revocation documented; de-authorising an integrator means rotating a secret issued by Paytronix. https://developers.paytronix.com/pxs_api_reference/authentication.html · retrieved 2026-08-04

The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.

extensibility-webhooks-push

Push exists and is real: 'Paytronix Online Ordering supports order injection via webhooks, where an HTTP POST notification with order information is sent to the third-party integrator upon order submission', configurable integrator-level (one URL for all merchants and stores) or store-level, authenticated with a per-webhook shared secret sent as 'Authorization: Bearer <SHARED_BEARER_TOKEN>'. Shortfall: the documented Request Types table is only four actions - new_order, validate_order, is_online (POS health check) and order_dsp_event (third-party delivery status). There is no modified, paid, voided, refunded or cancelled event; downstream state is acknowledged back to Paytronix through the POS Acknowledgement and POS Confirmation APIs rather than pushed out. Setup is also not self-service: 'Currently, webhooks must be configured by the Paytronix Online Ordering support team', with the only merchant-side control an undocumented-in-nav 'Webhook Endpoint' field reached by appending /advanced to the General Settings URL (help article 12599659). Note this host serves the docs over HTTP only; HTTPS did not complete. http://docs.opendining.net/pages/webhooks_v2.html · retrieved 2026-08-04

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.

Menu items, modifiers, and prices can be written and updated via API, not just read. differentiator

extensibility-menu-write-api

Not scored by this record.

Every core object the API can read (orders, menu, customers, employees, inventory) can also be written or updated via the same API. differentiator

extensibility-data-symmetry

Not scored by this record.

API rate limits are published as specific numeric quotas with documented throttling behavior and headers.

extensibility-published-rate-limits

Not scored by this record.

The vendor is a named DoorDash Preferred Integration Partner (DPIP) under the 2026 program requirements. differentiator

extensibility-doordash-preferred

Not scored by this record.

Direct, first-party certified integrations exist with DoorDash, Uber Eats, and Grubhub without requiring a paid middleware layer (Otter/Chowly/Deliverect/Checkmate). differentiator

extensibility-first-party-delivery-integrations

Not scored by this record.

The POS is a supported endpoint for at least two major aggregation middleware platforms (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate).

extensibility-middleware-compatibility

Not scored by this record.

Native, vendor-maintained connectors exist for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export.

extensibility-accounting-connectors

Not scored by this record.

Labor hours export natively to at least two named payroll providers (e.g. Gusto, ADP, Paychex, Paylocity) without manual re-keying.

extensibility-payroll-export

Not scored by this record.

Raw transaction-level data can be exported on a schedule to a customer-controlled destination (S3/SFTP/warehouse/Snowflake share), not only viewed in the vendor's reporting UI. differentiator

extensibility-bi-data-warehouse

Not scored by this record.

The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.

extensibility-app-marketplace

Not scored by this record.

Operators can define custom fields or run vendor-hosted custom logic/scripts against POS objects without a vendor engineering engagement.

extensibility-custom-fields-scripting

Not scored by this record.

The vendor supports a headless/embedded mode where a third-party UI (kiosk, web ordering, drive-thru) drives the POS transaction engine via API.

extensibility-headless-embedded

Not scored by this record.

The vendor publishes an API changelog and a stated deprecation/notice policy for breaking changes.

extensibility-api-versioning-deprecation

Not scored by this record.

A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator

extensibility-data-portability-exit

Not scored by this record.

Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.

reliability-offline-order-entry

Paytronix's documented behaviour when the connection drops is the opposite of continued order entry. On the in-store side the Paytronix Controller installed on the POS server enters Store and Forward mode, in which 'loyalty point accruals will be stored on the POS server' and nothing else - the article states plainly that 'S&F only supports loyalty point accrual', an offline stored value system being judged too risky. Order entry in that scenario belongs to the POS, not to Paytronix. On the online-ordering side the failure mode is a shutdown rather than a degraded mode: help article 12573210 describes a failsafe in the printer app that also shuts online ordering off for the corresponding restaurant when the printer goes offline, and the PXS carries a Store Ordering Disabled Report whose columns are Time Disabled, Time Re-enabled and which user did each. `offline` appears in 16 corpus documents and in none of them does an order get taken while offline. https://help-paytronix.theaccessgroup.com/en/articles/12609657-pxc-process-when-internet-lost · retrieved 2026-09-09 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

There is no kitchen display in the product - `KDS` and `kitchen display` occur zero times across the 683-document corpus - and kitchen printing is not Paytronix's to continue: the three corpus occurrences of `kitchen printer` are all instructions for configuring Revel's own kitchen printer settings inside the Revel admin. Paytronix's own printing path is a Windows receipt-printer app whose documented response to going offline is to stop the flow rather than sustain it: it 'contains a kind of failsafe that also shuts off online ordering for the corresponding restaurant when it goes offline', because the restaurant may otherwise have no immediate indication that orders are arriving. https://help-paytronix.theaccessgroup.com/en/articles/12573210-printer-app-and-ordering-offline · retrieved 2026-09-09 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

Paytronix does document multiple order-notification destinations, but they are configured to run together, not as automatic failover, and the documented response to an unreachable printer is to stop taking orders. The printer app 'contains a kind of failsafe that also shuts off online ordering for the corresponding restaurant when it goes offline', and the stated reason is that the restaurant may not be configured to receive any other form of notification - so no substitute destination is assumed or selected. Recovery is manual: shut the app down in Windows, then click the Enable Live Orders button on the dashboard to turn ordering back on. `failover`, `fail over`, `backup printer`, `secondary printer` and `automatically retry` occur zero times across the corpus, and the printer troubleshooting article is manual remediation throughout - restart the service, install the driver in Windows, fix the paper size. https://help-paytronix.theaccessgroup.com/en/articles/12573210-printer-app-and-ordering-offline · retrieved 2026-09-09 adversarially verified

The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).

reliability-sync-conflict-handling

Not scored by this record.

The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).

reliability-offline-feature-matrix

Not scored by this record.

A public, per-component status page exists showing current and historical incident state without a login.

reliability-public-status-page

Not scored by this record.

A contractual uptime SLA with a stated percentage AND a service credit remedy is published or available in the standard agreement. differentiator

reliability-contractual-uptime-sla

Not scored by this record.

The vendor publishes written post-incident reports or root-cause summaries for major outages.

reliability-incident-postmortems

Not scored by this record.

24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.

reliability-247-live-support

Not scored by this record.

The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator

reliability-onsite-install

Not scored by this record.

The vendor performs the initial menu build as part of onboarding rather than leaving it entirely to the operator. differentiator

reliability-menu-build-service

Not scored by this record.

A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.

reliability-hardware-replacement-sla

Not scored by this record.

Operators can trigger and retrieve their own data backup/restore, or the vendor publishes RPO/RTO figures for data recovery.

reliability-backup-restore

Not scored by this record.

The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.

reliability-pci-dss-4-attestation

Not scored by this record.

Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.

reliability-mfa-role-based-access

Not scored by this record.

A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.

reliability-self-serve-training

Not scored by this record.

Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. differentiator

reliability-failover-terminal-role

Not scored by this record.

Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.

reliability-cellular-backup

Not scored by this record.

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

Enumerated rather than merely not-found. paytronix.com/sitemap.xml lists exactly four legal documents: /cookie-policy, /privacy-policy/, /merchant-privacy-policy/, /service-provider-privacy-policy/, plus /terms-and-conditions/ and its single child /terms-and-conditions/data-processing-agreement/. /terms-of-service, /terms, /legal and /master-services-agreement all return 404. The /terms-and-conditions/ page itself renders no contract body - the only prose above boilerplate navigation is a marketing line - and the 62k-character Data Processing Agreement contains no occurrence of 'renew', 'initial term' or a cancellation notice period. On the operator side the help centre's Billing collection holds one article (deposit/withdrawal reconciliation), the online-ordering billing article covers only pass-through Twilio/fax/Spreedly per-unit rates, and the cancellation article says only that 'the account deactivation process can be initiated by emailing us at support', stating no notice window. No auto-renewal term or cancellation notice window is published anywhere on the vendor's own domains. https://www.paytronix.com/terms-and-conditions/ · 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

Platform page shows no prices and routes to demo requests. https://www.paytronix.com/platform · 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

CLAIM: all required terminals, KDS screens and printers can be purchased outright at a published price, with no mandatory lease. VERDICT: partial/B -- hardware is bought outright or brought, but no price is published. EVIDENCE (help-paytronix.theaccessgroup.com Intercom KB, 611 pages at 200): order-receiving tablet: 'You can either purchase an ELO tablet from us, and we will install the software, or If you purchase your own, you can install the software' (/en/articles/12592366-thinking-of-using-the-tablet-app); 'If you would more information about obtaining our business-grade tablets please contact support ... If you're purchasing a tablet from a 3rd party ... our current recommendation is the Galaxy Tab A from Samsung' (/en/articles/12593303-tablet-app-hardware-requirements); printers are third-party Epson/Star models from a supported list, 'See a Paytronix employee for recommended printers if you are looking to purchase' (/en/articles/12591508-tablet-supported-printers-for-online-ordering); for the loyalty/gift iPad app, 'Paytronix does not provide hardware or any other equipment to merchants and stores. Merchant headquarters or corporate is responsible for purchasing hardware ... Hardware prices may vary', iPads from store.apple.com, card readers ordered from MagTek (/en/articles/12603242). Kiosks are third-party integrations (Bite, Grubbrr, Nanonation, Tillster, Ziosk). CONTROL: tokenised lease|leased|leases|leasing|rental|rent|financing = 0 hits across all 611 bodies. SHORTFALL: no published price for the ELO tablet ('contact support') or any hardware; no lease is unstated rather than stated. Retrieved 2026-09-16. https://help-paytronix.theaccessgroup.com/en/articles/12592366-thinking-of-using-the-tablet-app · retrieved 2026-09-16 adversarially verified

Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator

commercial-hardware-not-locked

Not scored by this record.

One-time implementation, menu-build, onboarding, and training fees are published as specific amounts or explicitly stated as $0.

commercial-implementation-fee-published

Not scored by this record.

Operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee.

commercial-data-export-self-serve

Not scored by this record.

Guest/customer records, loyalty balances or point ledgers, and gift-card liability balances are exportable in machine-readable form by the operator. differentiator

commercial-export-customer-and-loyalty

Not scored by this record.

Contract or documentation specifies a post-termination data retrieval window (a defined number of days during which the operator can still export their data) rather than immediate cutoff. differentiator

commercial-post-termination-export-window

Not scored by this record.

Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator

commercial-data-ownership-clause

Not scored by this record.

The POS is source-available or open source with a documented self-hosting option (source published under an OSI or source-available license, not merely an open API).

commercial-source-available-selfhost

Not scored by this record.

Vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A / SAQ P2PE-HW, and names the applicable SAQ.

commercial-pci-p2pe-tokenization

Not scored by this record.

Vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — notably MFA for all access to the cardholder data environment including POS and back-office logins, and (for hosted ordering pages) payment-page script integrity monitoring per Req 6.4.3/11.6.1.

commercial-pci-dss-4-controls

Not scored by this record.

Vendor states it holds a current SOC 2 Type II (or ISO 27001) attestation and will provide the report under NDA via a trust center or on request.

commercial-soc2-attestation

Not scored by this record.

Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.

commercial-privacy-dsar-tooling

Not scored by this record.

Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator

commercial-wcag-kiosk-accessibility

Not scored by this record.

POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator

commercial-dual-pricing-compliant

Not scored by this record.