Vendors / Mainstream commercial restaurant POS
Rezku POS
iPad-based SMB restaurant POS from Guest Innovations, the rare vendor in this batch publishing real dollar figures ($99/mo for up to three stations, $19/mo per hardware bundle, $50/mo per kiosk, $399/mo marketing add-on) and marketing a pizza edition plus in-house driver dispatch — but every operational feature claim is marketing-level with no public product docs or API reference, and the published hardware price is a monthly bundle, not an outright purchase.
scored live legacy rubric
- Claims in scope
- 278
- Scored
- 45
- Assessed
- 42
- Unknown
- 236
- Not applicable
- 36
- Values challenged
- 4
unknown, never as no.Identity
- Owner
- Guest Innovations, Inc. (private; Sacramento, CA)
- Parent
- Guest Innovations
- Who it is for
- Independent US restaurants, bars and pizzerias — iPad-based, small footprint, price-sensitive
- Site
- https://www.rezku.com/pos/
Pricing
transparency: unknown · unit: per month per site (station-count tier) + per-station hardware/mo + per-kiosk/mo + per-add-on/mo · processor lock-in: unknown
- Software
- $99/mo software for up to 3 POS stations; hardware $19/mo per station (iPad, stand, printer, card reader) as a "limited time promotion"; customer-facing kiosk $50/mo per kiosk (software only); DoorDash Drive integration $39/mo plus fees; "Rezku Advantage" website/marketing $399/mo. Contract length not stated.
Capabilities
Every claim is binary and checkable. Grades: A primary documentation · B product documentation · C pricing or feature page · D marketing claim · E third-party reporting · F inference with no source. A yes on a differentiator claim requires A or B.
Order capture & FOH workflow
Provides a graphical floor-plan editor where an operator can draw sections, place tables of varying shape/capacity, save multiple floor-plan layouts per location, and assign sections to servers.
order-capture-floor-plan-editor
Not scored by this record.
Order lines can be tagged to a seat number at entry, and the check can be split by seat afterward without re-keying items.
order-capture-seat-level
Not scored by this record.
Items can be assigned to courses and held, with a fire-next-course action available from a handheld or terminal that releases only that course to the kitchen.
order-capture-coursing-hold-fire
Not scored by this record.
Supports splitting a check by item, by seat, by even N-way, and by arbitrary dollar/percentage amount, and merging checks or tables back together, including after partial payment.
order-capture-split-merge
Four split modes are documented: Split Order (More button, moves items off into a separate order), Itemized Split ("allows you to split checks by item"; when seats are in use each seat automatically becomes its own split, and shared items can be divided with the Split Even or Split Custom buttons), Split By Seat (auto-divides strictly by seat number), and Easy Split ("By default splits are even"; tap a split and "Enter the new amount" with the other splits auto-adjusting -- i.e. arbitrary dollar splits). Merging is documented on The "More" Button article: "Merge -- Merge another ticket into the active order. The merged ticket will close with the status 'merged'." Named shortfalls: no percentage-based split appears in any mode, and merging after a partial payment -- which the claim explicitly requires -- is documented nowhere in the live KB; the retired rezku.com/pos/support/merging-tickets page that covered merge restrictions now 302s to a dead Freshdesk portal and could not be read. https://support.rezku.com/portal/en/kb/articles/splitting-orders-and-payments · retrieved 2026-08-04
Opens a bar tab against a card pre-authorization with a configurable auth amount, supports incremental re-auth as the tab grows, and auto-closes stale tabs at end of day. differentiator
order-capture-bar-tab-preauth
Not scored by this record.
An open check can be transferred between servers, tables, and devices, and the transfer is recorded in an audit log naming both employees.
order-capture-transfer-audit
Not scored by this record.
Ships a first-party handheld ordering app running natively on the handheld device (not a remote/mirrored desktop session) that can send to kitchen and take a card payment tableside.
order-capture-native-handheld
Not scored by this record.
With the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen, and tender cash, and the vendor publishes what does and does not work offline.
order-capture-offline-order-entry
Offline Mode "allows you to store credit card transaction data if the internet is down and process the transactions when internet access is restored"; while offline, non-credit transactions -- "cash, gift card, external payment" -- and refunds can still be processed, so orders can be rung and cash-tendered on-terminal. Shortfall: the published offline scope is payments only. Neither this article nor Rezku POS App Settings (which offers just "Enable offline mode to store credit card payments" plus a View Offline History screen) says anything about modifiers, kitchen printing or KDS send while the WAN is down, and the Smart KDS article states "Both the POS and the KDS must be open and on the same network" with an on-screen error when they cannot communicate -- i.e. LAN-scoped, not WAN, but never stated as an offline guarantee. The vendor also caps it: "Offline Mode is designed for short term disruptions in the internet. Do not exceed 48 hours in Offline Mode." The claim's second half -- that the vendor publishes what does and does not work offline -- is not met. https://support.rezku.com/portal/en/kb/articles/offline-mode · retrieved 2026-08-04
Guest QR at-table ordering writes items onto the same open check as server-entered items, rather than creating a separate order ticket. differentiator
order-capture-qr-same-check
Not scored by this record.
Offers a first-party self-order kiosk that renders the same menu and modifier tree as the POS with no separate menu build, and the vendor documents ADA/accessibility conformance for it. differentiator
order-capture-kiosk-first-party
Not scored by this record.
Supports drive-thru-specific order flow: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment.
order-capture-drive-thru
Not scored by this record.
Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.
order-capture-drive-thru-timers
Not scored by this record.
Vendor ships a first-party AI voice ordering agent for phone and/or drive-thru that injects orders directly as POS orders, or publishes a documented API partner program for third-party voice AI. differentiator
order-capture-voice-ai
Not scored by this record.
Supports order throttling: per-channel capacity limits per time slot with automatic quote-time extension when kitchen load exceeds a configured threshold. differentiator
order-capture-throttling
Not scored by this record.
Accepts future-dated/scheduled orders with a per-channel lead time and automatically injects them into the make queue at a computed fire time rather than on receipt.
order-capture-scheduled-orders
Online Ordering Settings documents "Open for Pre-Orders -- When enabled, guests can place an order for days in advance" with a "Preorders Days In Advance" setting, and the POS permission list includes "Open orders for future dates". Shortfall: no per-channel lead time is configurable and no fire-time injection is documented -- the Order Settings article states kitchen printing happens only at "Checkout" (when the Checkout button is pressed, before payment) or at "Payment" (after the order is settled), with no computed release into the make queue. https://support.rezku.com/portal/en/kb/articles/online-ordering-settings · retrieved 2026-08-03
Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.
order-capture-catering
Not scored by this record.
Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator
order-capture-order-ready-signal
Not scored by this record.
Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.
order-capture-void-comp-controls
Not scored by this record.
Menu, modifiers & pricing engine
Payments & money movement
The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator
payments-processor-choice
Not scored by this record.
Vendor publishes card-processing pricing publicly (a specific flat rate or interchange-plus markup) rather than quote-only. differentiator
payments-published-rates
Not scored by this record.
Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator
payments-dual-pricing
Not scored by this record.
Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator
payments-surcharge-guardrails
Not scored by this record.
All first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay.
payments-emv-nfc
CLAIM: all first-party terminals accept EMV chip and NFC incl. Apple Pay and Google Pay. VERDICT: yes, grade C (vendor marketing; table-stakes weight, so C may carry yes). EVIDENCE: https://rezku.com/pos/hardware-pricing FAQ "What payment options does Rezku's restaurant POS system software support?": "Rezku supports all major credit and debit cards, Apple Pay, Google Pay, gift cards, and contactless tap-to-pay. Payments are processed directly through the POS using secure, integrated hardware." https://rezku.com/restaurant-pos/features/all under Secure Technology: "Latest EMV and tap-to-pay card readers"; https://rezku.com/restaurant-pos/mobile-pos: "Integrated EMV-secure card reader with fast-chip technology for tap, chip and swipe payments"; https://rezku.com/restaurant-pos/tableside-ordering-system: "Integrated EMV-secure card reader supports chip, tap, and swipe payments". The prior B-grade hardware KB article (now login-gated) said "All Current card readers are EMV enabled and manufactured by MagTek". WEAKNESS: no per-model reader spec; wallets are stated at platform level, not per terminal. NEW SURFACE STATE 2026-09-16: support.rezku.com/portal/en/kb/* no longer renders anonymously -- a headless-Chrome render of /portal/en/kb/articles/ingredients lands on auth.rezku.com/login ("Sign in to backoffice ... Not a user? Create account"), and the Zoho portal API (/portal/api/kbRootCategories, /kbArticles/articleByPermalink, with the page's own portalId and crmcsrfparam token) answers 403 FORBIDDEN; Wayback CDX was 503. The anonymous corpus used here is the rezku.com marketing/legal site: 124-URL sitemap.xml plus an href fixpoint = 271 URLs fetched, 260 at 200, 11 at 404 (soft-404 body ~38 KB, calibrated on /nonsense-xyz-123). Retrieved 2026-09-16. https://rezku.com/pos/hardware-pricing · retrieved 2026-09-16 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
Back Office > Promotions > Gift Cards documents first-party issuance and balance ledger: "Current Balance -- The current dollar value stored on the card", "Add Funds", "Deduct Funds", and a dashboard tracking "loads, spends, redeems and manual adjustments". Gift Card Portal Settings adds guest self-service ("Guests can also check the balance of their gift cards from the portal by clicking the link and entering their card number") and online redemption ("eGift cards work in-store and online"). Shortfall: cross-location redemption is nowhere documented - the article's only multi-location text is about applying a gift card TAG to several accounts ("Select the restaurants (accounts) the tag will be added to"), which is reporting, not a shared balance. https://support.rezku.com/portal/en/kb/articles/gift-cards · retrieved 2026-08-08
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
Employee Permissions enumerates discrete per-action POS toggles including "Void a transaction", "Adjust a transaction", "Refund cash", "Refund credit cards", "Apply custom discounts to orders and products", "Apply preset discounts to orders and products", "Manage the cash drawer" and "Cash drawer pay-in/pay-out", granted by role and overridable per user. Audit side, from the Reports List: "Product Voids -- items removed from orders already sent to kitchen showing user and manager override if applicable", "Transaction Voids" (time, user, order ID, payment type, amount), "Refunds" (user, order ID, refund type, amount, reason, time), "Comped Orders" and "Discounted Orders" carrying reasons, "Cash Drawer Activity" covering no-sale functions, and "Sales Exception by User". The docs do not assert log immutability. https://support.rezku.com/portal/en/kb/articles/employee-permissions · retrieved 2026-08-03
In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator
payments-chargeback-tooling
Not scored by this record.
Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator
payments-card-on-file
Not scored by this record.
Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator
payments-payout-timing
Not scored by this record.
Vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance / P2PE listing available to merchants on request.
payments-p2pe-pci4
Not scored by this record.
Kitchen & production
Items route to specific KDS stations by item, category, order type, or revenue center, with routing rules configurable per location without vendor involvement.
kitchen-station-routing
Print Queues documents the whole path in three numbered steps: "1. Creating the print queue 2. Assigning products to the queue 3. Assigning the queue to a device (printer or KDS)". Products are attached by "Click the Choose Products button next to the Print Queue name" then "Select the products assigned to the queue using the toggles" -- item-level routing, which is the granularity the claim asks for. The queue is flagged for a screen rather than a printer via Smart KDS ("Select if the queue will be used with Rezku Smart KDS instead of a printer"), and the Smart KDS article confirms the device side: "Select the queue name to assign this station or set up as Expediter." Per-location/per-station configurability is an explicit toggle: Global means "all tablets obey the same printer rules", and when deselected "queue assignments will be made locally for each POS station" -- all self-serve in Back Office, no vendor involvement. Caveat, not a downgrade: routing conditions are product membership only; nothing in the docs conditions a queue on order type or revenue center, and the KDS article mentions order type only as a label "displayed at the top of the ticket". https://support.rezku.com/portal/en/kb/articles/print-queues · retrieved 2026-08-04
An expo screen consolidates items from multiple prep stations into a single order view and only marks the order complete when every contributing station has bumped its items.
kitchen-expo-consolidation
Smart KDS documents an Expo view with cross-station reach: "Expo can mark items done and bump tickets in this view and it will ALSO perform the operation on the selected station KDS", and the kitchen-management page offers "Switch between Expo or any station view for seamless communication across the kitchen". Shortfall: the documented Expo behaviour is switching to and acting on a *selected* station, not a single consolidated order view; nothing states that an order is held incomplete until every contributing station has bumped its own items. https://support.rezku.com/portal/en/kb/articles/rezku-smart-kds-kitchen-display-system · retrieved 2026-08-03
Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator
kitchen-course-firing
Not scored by this record.
Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator
kitchen-prep-time-pacing
Not scored by this record.
Kitchen load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator
kitchen-order-throttling
Not scored by this record.
Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator
kitchen-channel-pause-propagation
Not scored by this record.
Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator
kitchen-order-ready-callback
Not scored by this record.
KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.
kitchen-bump-bar-hardware
The Rezku POS Hardware KB enumerates supported peripherals by category with named models -- Printers (Star TSP-100, Star SP-700, Star mC-Print3 MCP30/MCP31, SII RP F-10, Epson TM-u220, Epson TM-m30, sticky-label printers), Stands and Cases, Card Readers ("All Current card readers are EMV enabled and manufactured by MagTek"), and Accessories (Ubiquiti Amplifi router, Ubiquiti gateway/access point, automatic cash drawer, Viewsonic touchscreen display for KDS, Socket Mobile Bluetooth barcode scanner). No bump bar or programmable kitchen keypad appears in any category; the only KDS input hardware Rezku documents is a touchscreen, and the Smart KDS article describes touch interaction only. The claim requires documented supported models, and in a hardware KB that names a model for every other peripheral, none exists. https://support.rezku.com/portal/en/kb/rezku-pos-hardware/accessories · retrieved 2026-08-03
An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.
kitchen-all-day-counts
Not scored by this record.
Configurable target cook times per station or order type, with visual color escalation and/or audible alert when a ticket exceeds target.
kitchen-sla-alerts
Not scored by this record.
If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator
kitchen-printer-fallback
Not scored by this record.
KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator
kitchen-offline-operation
Not scored by this record.
Station screens can display item-level build/assembly detail (recipe steps, portioning, or full modifier breakout) rather than only the ticket line text. differentiator
kitchen-item-build-screens
Not scored by this record.
Sectioned/fractional topping placement (halves, quarters, specific sections) is rendered visually and unambiguously on the make-line screen or ticket. differentiator
kitchen-pizza-fractional-display
Not scored by this record.
A bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order.
kitchen-recall-refire
Not scored by this record.
Edits made in the POS to an order already displayed in the kitchen visually flag the added, changed, or removed items on the live ticket. differentiator
kitchen-order-modification-alerts
Not scored by this record.
Bumping an order ready triggers a guest-facing notification — SMS/text, app push, or an order-status display board — without a separate product purchase. differentiator
kitchen-guest-ready-notification
Not scored by this record.
Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.
kitchen-waste-logging
Not scored by this record.
Reports actual ticket and per-station times (average and percentile) sliced by daypart, station, and order channel, exportable to CSV or an API.
kitchen-speed-of-service-reporting
Not scored by this record.
Generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list.
kitchen-prep-forecasting
Not scored by this record.
Delivery, dispatch & third-party channels
Product includes a native in-house driver module: drivers are first-class entities with clock-in/out, assignment state (in-store / on-run / returning), and per-driver run history reportable from the POS itself (not via a third-party add-on).
delivery-driver-roster
"Delivery Driver Dispatch Management" marketed as a first-party module; driver clock-in, assignment states and per-driver run history are not documented. https://www.rezku.com/pos/delivery/ · retrieved 2026-08-01
Provides a dedicated dispatch/expo screen showing undispatched orders, driver availability, and elapsed time per order, with multi-order run batching (assigning 2+ orders to one driver as a single run).
delivery-dispatch-board
A dispatch screen for the driving crew is claimed; undispatched queue, elapsed timers and multi-order run batching are not documented. https://www.rezku.com/pos/delivery/ · retrieved 2026-08-01
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
The Fees article documents map-drawn delivery fee zones: "Multiple fee zones can be created with overlapping areas to apply fees based on distance from the restaurant automatically", configured via a "Set Delivery Area" button by adjusting vertex points to draw the area. Shortfall: only the FEE varies by zone. The order minimum is a single system-wide setting -- Online Ordering Settings has "Delivery Minimum Order Total -- Set a minimum order total for online delivery orders" -- and no per-zone quoted promise time is documented anywhere. Delivery Venues are preset addresses for hotels, office complexes and campuses, not zones. https://support.rezku.com/portal/en/kb/articles/fees · retrieved 2026-08-03
Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.
delivery-address-validation
Not scored by this record.
Tracks per-delivery driver compensation inputs — mileage or distance driven per run, per-delivery flat reimbursement, and driver-retained tips — and exports them to payroll as separate reimbursement vs. wage lines. differentiator
delivery-driver-comp
Not scored by this record.
Provides a driver cash bank / settle-up flow that reconciles cash collected, orders assigned, and tips owed at end of shift, producing a per-driver over/short figure.
delivery-cash-reconcile
Not scored by this record.
Can hand a first-party order to an on-demand courier marketplace (DoorDash Drive, Uber Direct, Nash, Relay or equivalent) natively from the POS, with the courier quote and status returning into the order record.
delivery-daas-dispatch
Not scored by this record.
Supports hybrid dispatch: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. differentiator
delivery-daas-fallback
Not scored by this record.
Offers direct, first-party certified API integrations with DoorDash, Uber Eats, and Grubhub marketplaces (vendor-owned, not solely resold through Otter/Deliverect/Chowly/ItsaCheckmate middleware). differentiator
delivery-3p-direct-integration
Not scored by this record.
Third-party marketplace orders inject automatically into the POS as normal tickets that fire to KDS/printers without tablet re-keying or manual accept.
delivery-3p-injection
Not scored by this record.
Marking an item or modifier 86'd in the POS pushes item-level out-of-stock status to connected third-party channels in near real time, and restores it on availability (DoorDash requires item and item-option 86ing of new POS partners).
delivery-86-sync
Not scored by this record.
Store can be paused/deactivated on each connected third-party marketplace from inside the POS with a timed auto-reactivation, rather than only from each marketplace's own tablet or portal.
delivery-store-pause
Not scored by this record.
Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. differentiator
delivery-3p-reconciliation
Not scored by this record.
Vendor exposes integration health to the operator — failed/rejected order injections, connection status per channel, and alerts on failure — rather than failing silently. differentiator
delivery-injection-error-visibility
Not scored by this record.
Guests receive a branded order status / driver tracking page or SMS link on the restaurant's own domain for first-party delivery orders, driven by real order and driver state.
delivery-tracking-page
Not scored by this record.
Quoted delivery promise times adjust dynamically from current kitchen load, driver availability, and zone drive time, rather than a fixed per-store constant. differentiator
delivery-promise-time
Not scored by this record.
Vendor documents explicit offline behavior for delivery: whether cash delivery orders, driver assignment, and driver settlement continue during an internet outage.
delivery-offline-behavior
Not scored by this record.
Digital ordering & guest-facing channels
Vendor ships a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission.
digital-first-party-web
First-party OLO is real and writes into the POS, but it is not on the restaurant's own domain: "All Rezku OLO websites are hosted on Rezku servers at the URL 'Order.Rezku.com', followed by a serial number", customisable only to a vanity path (example https://order.rezku.com/BestPizzaEver). The marketing page claims a "fully branded online ordering system" whose "orders go straight to your POS", and the pricing page lists "Branded Online Ordering" inside the $99/mo Basic plan, but no page states a per-order commission rate either way. Shortfall: vendor subdomain rather than customer domain, and commission terms unstated. https://support.rezku.com/portal/en/kb/articles/online-site-settings · retrieved 2026-08-08
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
The online-ordering product page claims "one-click reordering" to "drive repeat orders" plus "Multiple payment methods". Shortfall: that is one leg of a three-part claim and it is marketing-level. Guest account creation, saved delivery addresses and saved/tokenized cards on file appear nowhere in the Back Office KB -- neither Online Site Settings nor Online Ordering Settings mentions accounts, an address book or stored cards, and Checkout and Payment Types enumerates the tender options (credit card, cash, check, gift card, key-in card, CRM charge, house account, external payment, bar tab) with no card-on-file among them. https://rezku.com/restaurant-pos/online-ordering · retrieved 2026-08-03
Digital checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator
digital-upsell-engine
Not scored by this record.
Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.
digital-scheduled-pacing
Not scored by this record.
Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.
digital-fulfillment-modes
Not scored by this record.
Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.
digital-qr-table
Not scored by this record.
Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator
digital-kiosk
Not scored by this record.
Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.
digital-group-ordering
Not scored by this record.
Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator
digital-catering-portal
Not scored by this record.
Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator
digital-voice-ai-phone
Not scored by this record.
Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.
digital-drivethru-ai
Not scored by this record.
Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.
digital-sms-ordering
Not scored by this record.
Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator
digital-google-order
Not scored by this record.
Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.
digital-apple-business-connect
Not scored by this record.
Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.
digital-loyalty-attach
Not scored by this record.
Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.
digital-subscriptions
Not scored by this record.
Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.
digital-promo-parity
Not scored by this record.
Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator
digital-guest-data-ownership
Not scored by this record.
Digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.
digital-checkout-pci-sca
Not scored by this record.
Digital channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator
digital-surcharge-transparency
Not scored by this record.
Guest data, loyalty & marketing
Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.
guest-loyalty-unified-profile
The CRM article documents one customer database fed from both channels: "Typically, new customers will be added when they place an order online or on the POS and their information is entered for the first time", with a profile holding name, email, phone, address, tax-exempt status, customer ID, card ID, birthday, anniversary, notes, order count, average/high/total sales and top-3 favourite items, plus system-tracked fields the operator cannot hand-edit. Shortfall: no dedup or merge behaviour is described -- nothing states that a phone or email match consolidates an online record with an in-store one -- and kiosk orders are not addressed at all. https://support.rezku.com/portal/en/kb/articles/crm · retrieved 2026-08-03
Orders arriving from third-party marketplaces (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. differentiator
guest-loyalty-thirdparty-identity-attach
Not scored by this record.
Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.
guest-loyalty-accrual-models
CLAIM: at least two of points-per-dollar, visit/punch-count, spend-tier accrual, as configuration, native. VERDICT: yes, grade C (vendor marketing, table-stakes). EVIDENCE: https://rezku.com/restaurant-pos/features/loyalty: "Customer loyalty program | Reward guests with points per dollar or purchase, redeemable online or in-store, at any of your locations." and "Customize rewards | Set points per purchase or dollar and define how customers redeem rewards to fit your brand's loyalty strategy." -- points-per-dollar AND points-per-purchase (visit-count accrual) as settings ("Turn on the loyalty program in your Rezku dashboard"). https://rezku.com/restaurant-pos/features/all: "Loyalty rewards program (dollars and points)". Native, no bolt-on vendor. WEAKNESS: no back-office doc of the settings screen (KB now gated); spend-tier accrual not evidenced. Retrieved 2026-09-16. MERGE-TIME DOWNGRADE (315th): yes -> partial. The claim needs TWO of points-per-dollar, visit/punch-count and spend-tier; "Set points per purchase or dollar" evidences points-per-dollar, and reading per-purchase points as visit-count accrual is an inference marketing copy does not state. https://rezku.com/restaurant-pos/features/loyalty · retrieved 2026-09-16 adversarially verified
Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator
guest-loyalty-tiers
Not scored by this record.
Documents explicitly what loyalty lookup, accrual, and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). differentiator
guest-loyalty-offline-behavior
Not scored by this record.
Offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. differentiator
guest-loyalty-offer-stacking-rules
Not scored by this record.
Offers can be issued to a dynamically defined audience (rules over recency, frequency, spend, or items purchased) rather than only broadcast to the whole list. differentiator
guest-loyalty-targeted-offers
Not scored by this record.
Automatically computes recency/frequency/monetary or equivalent lifecycle segments (new, regular, at-risk, lapsed, VIP) without the operator building the queries. differentiator
guest-loyalty-rfm-segmentation
Not scored by this record.
Ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns rather than one-off manual sends.
guest-loyalty-lifecycle-automation
The email-marketing page claims "Schedule campaigns in advance or automate messages for birthdays, special promotions, loyalty milestones, and more"; the text-marketing page claims "Automated texts", "Automations so you can focus on operations while your repeat orders skyrocket" and "Personalized birthday and follow-up messages". Shortfall: birthday is the only named trigger, lapsed/win-back is named nowhere, and none of it is documented -- the Back Office KB has no campaign or automation article, its Loyalty Points article describes a manual four-step flow (add CRM customers, create point-earning rules, create discount presets that cost points, apply on the POS), and its CRM article routes marketing off-platform via CSV export "as a mailing list for marketing" and a Mailchimp integration. https://rezku.com/restaurant-pos/email-marketing · retrieved 2026-08-03
Sends both email and SMS campaigns natively from the platform, not solely by handing the list to a third-party ESP. differentiator
guest-loyalty-native-email-sms
Not scored by this record.
Captures per-channel marketing consent with timestamp and source of consent, and honors revocation received by any reasonable means (not just the STOP keyword) across all channels.
guest-loyalty-consent-management
Not scored by this record.
Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.
guest-loyalty-10dlc-registration
Not scored by this record.
Reports redemption and incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. differentiator
guest-loyalty-campaign-attribution
Not scored by this record.
Provides self-serve export of the full guest list and transaction history, including contact PII, via CSV or API, without a vendor fee or support ticket. differentiator
guest-loyalty-data-export-portability
Not scored by this record.
Triggers post-transaction feedback requests and routes responses by score, sending low scores to private service recovery and high scores toward public review sites. differentiator
guest-loyalty-review-capture-routing
Not scored by this record.
Includes a native referral mechanic with per-guest codes or links, attribution of the referred guest's first order, and two-sided rewards.
guest-loyalty-referral-program
Not scored by this record.
Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance, as an alternative to requiring a branded app download. differentiator
guest-loyalty-wallet-pass
Not scored by this record.
Provides admin tooling to fulfill guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records.
guest-loyalty-privacy-rights-tooling
Not scored by this record.
Enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log.
guest-loyalty-redemption-fraud-controls
Not scored by this record.
Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing (claim-level; verify it is a shipped product feature, not a roadmap statement). differentiator
guest-loyalty-ai-offer-recommendation
Not scored by this record.
Offers native stored-value/gift card balances tied to the same guest profile and redeemable across all locations of the brand.
guest-loyalty-stored-value-gift
Not scored by this record.
Labor & workforce
Employees clock in and out at the POS terminal using a PIN, badge, or card, with no separate time-clock hardware required.
labor-clock-in-at-pos
CLAIM: employees clock in/out at the POS terminal with PIN, badge or card, no separate time-clock hardware. VERDICT: yes, grade C (vendor marketing, table-stakes). EVIDENCE: https://rezku.com/restaurant-pos/features/employee-management: "Clock in/out via Rezku POS with data synced to 7shifts, including sales, breaks, and grace periods for full schedule compliance" and "Effortless time tracking | Lower your bookkeeping hours with Rezku's simple-to-master integrated timecard system"; "See who's clocked in". https://rezku.com/restaurant-pos/features/all Secure Technology list: "Employee photo-capture at clock-in", "Swipe-card access", "Employee PINs w/ activity tracking". Corroborated by the atlas's existing B-grade employee-permissions citation (recorded 2026-08-03, now login-gated): role "No Access -- No POS access. Can only clock in/out". Retrieved 2026-09-16. https://rezku.com/restaurant-pos/features/employee-management · retrieved 2026-09-16 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.
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
Permissions are per discrete action rather than fixed tiers: four role defaults (Owner "All permissions granted", Manager, Employee, No Access "No POS access. Can only clock in/out") plus "Make individual permissions exceptions on a per-user basis without changing their role", over roughly 55 named toggles including "Void a transaction", "Apply custom discounts to orders and products", "Refund cash", "Refund credit cards", "Manage the cash drawer", "Manually set a price for a product", "Access settings", "Enable offline mode", "View performance data" and "View user performance data". Shortfall: the claim also requires grants scoped per location, and the article is silent on location scoping -- permissions are documented only at role and individual-user level. https://support.rezku.com/portal/en/kb/articles/employee-permissions · retrieved 2026-08-03
Manager overrides and approvals are attributed to the individual approver and written to an immutable audit trail queryable after the fact.
labor-manager-override-audit
Event Logs are queryable after the fact -- "Changes made to Back Office settings are captured in the event logs", filterable by date range and by user ("You can filter the event log by user and only view Back Office activity performed by the selected user"), with per-event detail expandable. On the POS side the Product Voids report shows "user and manager override if applicable". Shortfall: the Event Log is scoped to Back Office setting changes, not POS manager approvals; approver attribution surfaces only inside one void report rather than a general override trail; and the docs make no statement about immutability or retention. https://support.rezku.com/portal/en/kb/articles/event-logs · retrieved 2026-08-03
Builds and publishes employee shift schedules inside the same platform that holds the timekeeping data, rather than requiring a third-party scheduling app. differentiator
labor-native-scheduling
Not scored by this record.
Generates recommended staffing levels or labor hours by daypart from the operator's own POS sales history, not just a static template. differentiator
labor-demand-labor-forecast
Not scored by this record.
Displays labor cost as a percentage of sales in real time during service on a manager view or POS, not only in end-of-day or next-morning reports. differentiator
labor-realtime-labor-percent
Not scored by this record.
Warns or blocks at clock-in when an employee is approaching or would cross a configured overtime threshold, before the overtime is incurred. differentiator
labor-overtime-prevention
Not scored by this record.
Configures meal and rest break rules per state or jurisdiction, prompts required break attestation, and flags missed breaks for premium pay. differentiator
labor-break-compliance-by-state
Not scored by this record.
Enforces minor-labor restrictions (age-based maximum hours, prohibited time windows, school-day limits) at both scheduling and clock-in.
labor-minor-labor-rules
Not scored by this record.
Computes tip pooling and tip-outs automatically per shift from configurable rules (percentage of sales, hours worked, points, or role), rather than requiring a manual spreadsheet.
labor-tip-pooling-rules
Not scored by this record.
Retains a per-shift, per-employee record of tips received, amounts contributed to the pool, and amounts distributed from the pool, exportable for audit.
labor-tip-distribution-audit-trail
Not scored by this record.
Payroll export separates cash from charged qualified tips and carries a Treasury tipped-occupation code, supporting the W-2 Box 12 code TP and Box 14b reporting required for tax year 2026. differentiator
labor-qualified-tips-w2-reporting
Not scored by this record.
Vendor processes payroll itself as a first-party product (tax filing and direct deposit), as opposed to exporting to a third-party payroll provider only. differentiator
labor-native-payroll
Not scored by this record.
Exports timecards, wages, and tips in documented formats or via direct integration for at least two major payroll providers (e.g. Gusto, ADP, Paychex, QuickBooks).
labor-payroll-export-formats
Not scored by this record.
Employees can request shift swaps or claim open shifts in a self-service app, subject to a manager approval workflow that enforces overtime and role eligibility. differentiator
labor-shift-swap-workflow
Not scored by this record.
Reports per-employee sales performance metrics (average check, items or category attachment rate, void and comp rate) by server or cashier. differentiator
labor-server-performance-metrics
Not scored by this record.
Inventory, purchasing & cost control
Supports multi-level recipe/BOM costing where a recipe can contain sub-recipes (prep items) and plate cost recalculates automatically when any component ingredient's cost changes.
inventory-recipe-bom-costing
CLAIM: multi-level recipe/BOM costing with sub-recipes and automatic plate-cost recalculation. VERDICT: still unknown. EVIDENCE: https://rezku.com/restaurant-pos/features/all lists "Ingredient-level inventory tracking" and "Ingredient-level food cost calculation"; https://rezku.com/restaurant-pos/features: "Ingredient-level inventory tracking lets you see exactly where food costs are going". Single-level ingredient costing is marketed, but no page names sub-recipes, prep items or nested components (case-insensitive controls over the 260 rezku.com pages at 200: "sub-recipe" 0, "prep item" 0, "plate cost" 3, all generic blog advice in /blog/mastering-inventory-management, /blog/pos-reports-explained, /blog/restaurant-food-waste-reduction, none describing a nested recipe model). POISON: "recipe" hits are the KDS "Recipe book" / bar "drink recipes" prep-instruction features and third-party integration pages (Yellow Dog, Craftable, Ctuit) describing the PARTNER's recipe costing. The KB Components article that could settle nesting is now login-gated. Not a no: marketing is not an enumeration of the inventory model. NEW SURFACE STATE 2026-09-16: support.rezku.com/portal/en/kb/* no longer renders anonymously -- a headless-Chrome render of /portal/en/kb/articles/ingredients lands on auth.rezku.com/login ("Sign in to backoffice ... Not a user? Create account"), and the Zoho portal API (/portal/api/kbRootCategories, /kbArticles/articleByPermalink, with the page's own portalId and crmcsrfparam token) answers 403 FORBIDDEN; Wayback CDX was 503. The anonymous corpus used here is the rezku.com marketing/legal site: 124-URL sitemap.xml plus an href fixpoint = 271 URLs fetched, 260 at 200, 11 at 404 (soft-404 body ~38 KB, calibrated on /nonsense-xyz-123). Retrieved 2026-09-16. || 329th: 329th, NEW SURFACE -- the back-office app read from the store instead of the login-gated web app: Rezku Manager (iOS id 1609454922, v2.4.1, 2026-08-04; Android com.dinnerwire.RezkuPOSBackoffice, updated Aug 3 2026), whose release note says "This version brings the Rezku Manager app to feature parity with the web version". Its listing enumerates the back office as 17 modules -- Over 60 Reports, Multi Location Reporting, Gift Card Dashboard, Employee Management, Online Ordering Management, QR Codes Management, Product Management, Floor Plan Designer, Inventory Management, INGREDIENT LEVEL INVENTORY MANAGEMENT, KPI Dashboard, Loyalty Program Management, CRM Management, Marketing, Staff Scheduling, Happy Hour Management, Coupons Management -- and the app's own navigation drawer, read at full resolution from the store screenshot (ip17-nav.png rewritten to 1600x0w), is Dashboard, Orders, Reporting, Product Management, Promotions, Inventory, Employees, Settings, Online Ordering, Payments (New), Floor Plan Designer, Feedback, Referrals (list continues below the fold). Ingredient-level costing is confirmed a second time at the app level, but nothing names a sub-recipe, prep item or nested component, and the nav is not a census of what sits inside Inventory. RE-GREP OF CORPORA ALREADY ON DISK for this cell's vocabulary (the 270-file rezku.com page corpus in .cache/q315/rezku-pos/pages plus the 4 app bundles in .cache/q322/rezku-pos, 5.6 MB: order.rezku.com ord-all.js + order-main.js, giftcard, stockimage): sub-recipe/subrecipe 0 files, "prep item" 0, "batch recipe" 0, "bill of materials" 0, "portion cost" 0, nested 0; "theoretical" 7 files and "plate cost" 3 are ALL generic blog advice (POISON: /blog/restaurant-food-waste-reduction alone supplies 5 of the 7 "theoretical" hits and /blog/best-restaurant-inventory-management-software 2 more, all third-person guidance, none describing Rezku's data model); "prepped" 9 files are likewise blog prose about over-prepping food. The client bundles contain 0 hits for recipe/ingredient/food_cost at all -- they are ordering and gift-card clients, so they cannot bound the inventory model. Still unknown. Retrieved 2026-09-18. 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
An ingredient record stores a purchase-to-tracking conversion. Named fields: Ingredient Name, Ingredient Unit Type (Count, Solid or Liquid), Ingredient Tracking Unit, "My cost is" / "For every" / "Tracking unit" (supplier cost for a supplier-unit quantity, converted automatically between like unit types), Custom Units, Minimum Par Level, Attached Products, Amount. Shortfall: there is no third recipe unit distinct from the tracking unit -- the Components article says only "Enter the amount of each component that is used" -- and no yield or waste percentage applying a raw-to-usable factor. Waste appears in the Ingredient Use reports as an observed quantity, not as a conversion factor. https://support.rezku.com/portal/en/kb/articles/ingredients · retrieved 2026-08-03
Produces a theoretical-vs-actual usage variance report per item for a defined count period, showing theoretical usage from POS sales times recipe, actual usage from counts plus receipts, and the variance in both units and currency. differentiator
inventory-theoretical-vs-actual
Not scored by this record.
Depletes ingredient on-hand quantities in near real time as orders are fired at the POS, including depletion driven by modifier selections, not only in an end-of-day batch. differentiator
inventory-realtime-depletion
Not scored by this record.
Automatically 86s (marks unavailable) menu items on the POS, online ordering, and connected third-party delivery menus when a component ingredient hits zero or a configured threshold. differentiator
inventory-86-auto-sync
Not scored by this record.
Supports full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts.
inventory-count-modes
The Inventory Take Report "helps you when re-ordering or performing a physical count/audit for ingredients"; its Amount column is "a placeholder for you to enter a value" that "can be used in 2 different ways" -- to enter planned order amounts, or to write physical counts onto a printed sheet. The POS permission "Change inventory counts on the iPad" also exists. Shortfall: only an ad-hoc full/physical count is documented and it is a printable worksheet. No scheduled recurring cycle counts, no subset spot-count mode, and no statement that each count is retained as separate dated variance history rather than overwriting the prior on-hand figure. https://support.rezku.com/portal/en/kb/articles/inventory-take-report · retrieved 2026-08-03
Provides a mobile/tablet counting app supporting barcode or QR scanning that continues to accept counts with no network connectivity and syncs on reconnect.
inventory-mobile-count-offline
Not scored by this record.
Ships pre-built electronic vendor catalog and order-transmission integrations with named broadline distributors (e.g. Sysco, US Foods, Performance Food Group) that send purchase orders and receive invoices electronically rather than by emailed PDF. differentiator
inventory-vendor-catalogs-edi
Not scored by this record.
Ingests supplier invoices from photo, PDF, or email and extracts line-item detail (item, quantity, unit, price) into the inventory ledger without manual line entry. differentiator
inventory-invoice-ocr
Not scored by this record.
Tracks per-item purchase price history across invoices and alerts when a received price exceeds the prior or contracted price by a configurable threshold. differentiator
inventory-price-change-alerts
Not scored by this record.
Maintains par levels per item per location and generates suggested purchase order quantities from on-hand versus par, with at least one mode driven by a sales forecast rather than a static par. differentiator
inventory-par-auto-suggest
Not scored by this record.
Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.
inventory-waste-logging
Not scored by this record.
Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.
inventory-shelf-life-expiry
Not scored by this record.
Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting.
inventory-bar-partial-bottle
Not scored by this record.
Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.
inventory-cogs-gl-export
Not scored by this record.
Inventory and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator
inventory-native-not-partner
Not scored by this record.
Reporting, BI & data access
Provides a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise.
reporting-realtime-dashboard
The Back Office Dashboard "gives you a quick, clear view of restaurant performance in a graphical format" and "By default, when the dashboard loads it shows you stats for the current day". Shortfall: the docs never state data freshness -- no latency, refresh interval or live/real-time wording appears in the Dashboard or Reports articles, and the Reports article says flatly "Reports are viewed in the browser" with no mobile app mentioned. The real-time and off-premise-mobile legs of the claim rest only on marketing (rezku.com/restaurant-pos/advanced-reporting: "access real-time data anytime, anywhere" and "view multiple locations directly from iOS or Android devices with the Manager's App"). https://support.rezku.com/portal/en/kb/articles/dashboard · retrieved 2026-08-03
Generates a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types, and expected cash deposit in one document.
reporting-eod-closeout
"The Daily Report is a 'paper dashboard' that contains multiple reports. It is divided into 2 sections, Sales and Transactions with multiple tables in each", delivered as a PDF download. Its tables cover Sales Overview (gross sales, comps, discounts, net sales, gift card loads, taxes, fees, gratuity, prepaid orders, early pay, tips, refunds, totals), Product Category Sales, Sales by Order Type, Sales by Source (OLO and POS), a copy of the Taxes report, a copy of the Transactions report -- which the Reports List defines as "total transactions by payment type", i.e. the tender breakdown -- Cash In/Out (cash transactions, tip payouts, pay-outs/ins, bank drops, refunds, adjustments) and Credit In/Out (swiped, unfinalized, tips, undercharged funds, refunds). One document reconciling every element the claim names. https://support.rezku.com/portal/en/kb/articles/exports-list · retrieved 2026-08-03
Provides a product mix (PMIX) report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center.
reporting-pmix-modifier-level
Both halves exist but as separate reports. Item side: "Top Products" (quantity, sales, profit, percentage contribution), "Sales by Category" (count, gross, comps, discounts, net sales), "Variants" (variation selection count and sales contribution). Modifier side: a distinct "Modifier" report -- "product modifier usage showing default/selected status and upcharges". Shortfall: there is no single PMIX spanning items AND modifiers; the Modifier report is documented as usage-and-upcharge rather than gross and net sales; and while the Reports article supports "Filter by Time" with configured meal periods offered as daypart presets, revenue-center filtering is documented nowhere. The Exports list carries "Sales by Product" but no product-mix export covering modifiers. https://support.rezku.com/portal/en/kb/articles/reports-list · retrieved 2026-08-03
Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.
reporting-comps-voids-audit
Not scored by this record.
Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.
reporting-cash-over-short
Not scored by this record.
Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.
reporting-labor-productivity
Not scored by this record.
Reports per-server metrics including average check, items per check, attachment rate for named categories, and tips as a percentage of sales. differentiator
reporting-server-scorecards
Not scored by this record.
Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator
reporting-channel-profitability
Not scored by this record.
Supports scheduling any report for automatic recurring delivery by email or to a shared destination on a defined cadence and recipient list.
reporting-scheduled-delivery
Not scored by this record.
Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator
reporting-public-api
Not scored by this record.
Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator
reporting-webhooks
Not scored by this record.
API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator
reporting-api-not-upcharged
Not scored by this record.
Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator
reporting-tier-paywall
Not scored by this record.
Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator
reporting-history-retention
Not scored by this record.
Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator
reporting-anomaly-alerts
Not scored by this record.
Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.
reporting-nl-query
Not scored by this record.
Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator
reporting-guest-cohorts
Not scored by this record.
Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator
reporting-sales-forecast
Not scored by this record.
Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.
reporting-tip-tax-compliance
Not scored by this record.
Multi-location, franchise & enterprise governance
Supports a named organizational hierarchy of at least three levels (e.g. enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations.
multi-location-org-hierarchy
Multi-location is real: the Reports article lets you "select the locations to include in the report" and choose whether to merge data across locations or produce separate reports per location, and the Reports List includes "Sales by Restaurant -- multi-location comparison showing orders, sales, labor, food cost, and profit". Shortfall: locations are addressed as a flat selectable list. No region, group or enterprise tier exists as a first-class object anywhere in the Back Office KB -- Restaurant Information configures a single restaurant profile, and neither reporting nor permissions can be scoped to a group. https://support.rezku.com/portal/en/kb/articles/reports · retrieved 2026-08-03
Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.
multi-location-price-zones
Channel price tiers exist on the item record without duplication: Menu Design documents an "Online Price" and a "3rd Party Price -- Set the 3rd party app price if different than the online price" alongside the base price. Daypart pricing exists via Happy Hours (Back Office > Promotions) and the POS permission "Apply period pricing outside of period". Shortfall: the location-group leg of the claim is missing -- no price tier, zone or location group is documented that would give one item different prices at different sites, and Menu Design exposes no per-location price field. https://support.rezku.com/portal/en/kb/articles/menu-design · retrieved 2026-08-03
Provides above-store reporting that aggregates sales, labor, discounts, voids, and item mix across any selected set of locations in one view, with store-vs-store ranking and variance flags.
multi-location-consolidated-reporting
Not scored by this record.
Gift cards issued at one location are redeemable at any other location in the brand, with a reported outstanding-liability balance and inter-store settlement/redemption reconciliation between owners.
multi-location-cross-location-giftcard
Not scored by this record.
A single customer loyalty profile, balance, and stored order history is shared across all locations in the brand rather than being per-location.
multi-location-cross-location-loyalty
Not scored by this record.
A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. differentiator
multi-location-multi-brand
Not scored by this record.
Tax configuration is per-location with support for multiple simultaneous tax rates, jurisdiction-specific rules (e.g. prepared-food vs grocery, inclusive vs exclusive tax), and per-location tax exemptions.
multi-location-multi-tax-jurisdiction
Not scored by this record.
Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.
multi-location-central-labor-policy
Not scored by this record.
Hardware & physical footprint
The POS software runs on commodity off-the-shelf hardware (standard iPads, Android tablets, or PCs) that the operator can buy from a third party, rather than only on vendor-supplied proprietary terminals. differentiator
hardware-commodity-devices
Not scored by this record.
Vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs.
hardware-os-platforms
Published hardware bundle includes an iPad, so clients are iPadOS; no minimum OS versions or device specs are published. https://www.rezku.com/pos/pricing/ · retrieved 2026-08-01
Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.
hardware-handheld-purpose-built
Not scored by this record.
The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator
hardware-handheld-battery-swap
Not scored by this record.
Handhelds support cellular/LTE connectivity as a documented fallback when store Wi-Fi drops, either built into the device or via a vendor-supplied failover.
hardware-handheld-lte
Not scored by this record.
Terminals continue to take orders, print to kitchen, and record cash sales with the internet down, and the vendor documents explicitly which functions degrade (card auth, loyalty lookup, refunds).
hardware-offline-mode
Offline Mode "allows you to store credit card transaction data if the internet is down and process the transactions when internet access is restored", and non-credit tenders -- "cash, gift card, external payment" -- plus refunds still process while offline, so orders can be rung and cash sales recorded with the WAN down and synced to Rezku servers afterwards. Named shortfalls: kitchen printing offline is documented nowhere (the published offline scope is payments only, and the Smart KDS article's "Both the POS and the KDS must be open and on the same network" is a LAN requirement, never stated as an offline guarantee); the claim's second leg fails outright because the vendor publishes no enumeration of which functions degrade -- loyalty lookup and online-order intake are unaddressed; and the mode is a manager-activated toggle (PIN, chosen duration, signed disclaimer) with the vendor's own cap "Offline Mode is designed for short term disruptions in the internet. Do not exceed 48 hours in Offline Mode.", not automatic continuation. https://support.rezku.com/portal/en/kb/articles/offline-mode · retrieved 2026-08-04
Sells or supports a dedicated kitchen display system with bump-bar or touch input, station routing, and course/fire timing, as a first-party product rather than an integration-only dependency.
hardware-kds
CLAIM: first-party KDS with bump-bar or touch input, station routing, and course/fire timing. VERDICT: yes, grade C (vendor marketing, table-stakes). EVIDENCE: https://rezku.com/restaurant-pos/restaurant-kitchen-management-software: "smart kitchen display system", "Advanced touchscreen displays give kitchen managers greater control", "Switch between Expo or any station view", "Track orders live as items are marked complete", "Highlight urgent tickets in red". https://rezku.com/restaurant-pos/features/all Hardware & Compatibility: "Smart KDS touch-screen displays", "Route tickets between KDS stations", "Expo KDS with advanced controls"; Full Service: "Coursing w/ fire button". https://rezku.com/restaurant-pos/pizza (and quick-service, full-service): "Rezku's touchscreen KDS", "Control order flow with station-to-station bump management", "Prioritize prep using ticket timers and status such as RUSH or DONE"; https://rezku.com/restaurant-pos/restaurant-delivery-management-software: "Route items to multiple stations, bump orders through production lines, and monitor ticket times". First-party: the atlas's B-grade kitchen-expo-consolidation cell cites Rezku's own "Rezku Smart KDS" KB article; input is touch only (kitchen-bump-bar-hardware is already no). WEAKNESS: coursing/fire is listed as a POS feature; no page says fire timing drives the KDS view. Retrieved 2026-09-16. MERGE-TIME DOWNGRADE (315th): yes -> partial. The claim requires course/fire timing ON the KDS; the feature list names "Coursing w/ fire button" as a POS feature, not tied to the KDS product. https://rezku.com/restaurant-pos/restaurant-kitchen-management-software · retrieved 2026-09-16 adversarially verified
Offers a self-order kiosk running the same menu and modifier engine as the POS, in both countertop and freestanding form factors, with integrated payment and accessibility (ADA) compliance documented. differentiator
hardware-kiosk
Not scored by this record.
Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, and speaker/headset integration, with a documented timer/speed-of-service measurement.
hardware-drive-thru
Not scored by this record.
Works with standard ESC/POS thermal receipt and kitchen printers from more than one manufacturer (e.g. Epson and Star), including LAN/Ethernet printers, rather than only vendor-branded printers.
hardware-printer-compatibility
Not scored by this record.
Supports the standard peripheral set — cash drawers (including multi-drawer per terminal), barcode scanners, scales for by-weight items, and customer-facing displays — with a published compatibility list.
hardware-peripherals
Not scored by this record.
Card entry happens on a PCI-listed PTS device using validated point-to-point encryption, so the POS application and tablet stay out of PCI scope; the vendor states the merchant's SAQ type.
hardware-p2pe-terminal
Not scored by this record.
Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. differentiator
hardware-tap-to-phone
Not scored by this record.
Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator
hardware-pricing-transparency
Not scored by this record.
Hardware can be purchased outright (owned) as an alternative to a mandatory lease or subscription-bundled rental, and the vendor states which. differentiator
hardware-ownership-vs-lease
Not scored by this record.
Vendor documentation confirms whether hardware purchased from the vendor remains usable with other software after cancellation, i.e. it is not software-locked or remotely bricked. differentiator
hardware-usable-after-churn
Not scored by this record.
Publishes a hardware warranty term and a replacement/advance-exchange SLA with a stated turnaround (e.g. next-business-day depot swap). differentiator
hardware-rma-sla
Not scored by this record.
Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.
hardware-byod
Not scored by this record.
Provides a remote device-management console showing each terminal, printer, and KDS as online/offline, with remote reboot, software-version visibility, and staged rollout of updates. differentiator
hardware-remote-device-management
Not scored by this record.
Integrates with specialty beverage hardware — self-pour tap walls, flow meters, or liquor pour spouts — such that pours post to a POS tab automatically.
hardware-selfpour-scales
Not scored by this record.
Supports inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call.
hardware-callerid-integration
Not scored by this record.
Integrations, API & extensibility
Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.
extensibility-public-api-docs
329th, NEW DOMAIN CENSUSED: rezkupos.com. CLAIM: public self-serve API reference readable without a signed partner agreement, NDA or sales call. VERDICT: unknown -> no / B. The prior passes censused rezku.com, rezkustaging.com and guestinnovations.com only; the back-office host linked from rezku.com's own footer is manager.rezkupos.com, a FOURTH domain nobody had run crt.sh on. crt.sh %.rezkupos.com returns 10 distinct names (rezkupos.com, www, manager, manager-origin, lb, api.rezkupos.com, developer.rezkupos.com, reporting.rezkupos.com, files.reporting.rezkupos.com, training.rezkupos.com). Probed each live host for /, /robots.txt, /swagger, /swagger/index.html, /swagger/v1/swagger.json, /openapi.json, /api-docs, /docs, /redoc, /v3/api-docs plus the nonsense control /zzz-nonsense-xyz: api.rezkupos.com and reporting.rezkupos.com answer 404 on ALL TEN paths with a real 404 handler whose body length tracks the path length (49-72 bytes) and is byte-identical in shape to the nonsense control (65 bytes); developer.rezkupos.com, lb and manager-origin do not resolve (NXDOMAIN); files.reporting.rezkupos.com answers 403 on every path including the nonsense control (a refusal, not an absence); manager.rezkupos.com/ 302s to /v4/ then to auth.rezku.com/oauth/authorize (client_id fa20c870, scope https://rezku.com/pos#backoffice) then to auth.rezku.com/login; training.rezkupos.com 302s to the same OAuth gate (client_id 98db17c0). WAYBACK (working over https today): CDX for developer.rezku.com/* holds exactly ONE capture ever -- 20240930054029, status 301 -- so the developer portal has never served public content into the archive; docs.rezku.com and api.rezku.com have zero captures. auth.rezku.com/.well-known/oauth-authorization-server is anonymous and complete: {issuer, authorization_endpoint, token_endpoint, jwks_uri, token_endpoint_auth_methods_supported:[client_secret_basic], response_types_supported:[code], code_challenge_methods_supported:[plain,S256], grant_types_supported:[client_credentials, authorization_code, password, refresh_token]} -- 530 bytes with NO registration_endpoint, i.e. no self-serve client registration; client credentials are issued out of band. The only account-creation link anywhere is on auth.rezku.com/login, and it is a merchant back-office signup, not a developer one (page text: "Sign in to backoffice ... Not a user? Create account ... By signing in you are agreeing to the Terms of Use"). The support KB is gated at the API too, re-confirmed with curl and a VALID CSRF token: support.rezku.com/portal/api/kbRootCategories?portalId=edbsneae...c4b18e4682&orgId=672908509 with X-ZCSRF-TOKEN from the portal's own crmcsr cookie returns 403 {"errorCode":"FORBIDDEN"} (an invalid token returns 422, so the 403 is authorisation, not a client artefact). BOUND: all four vendor domains (rezku.com 44 CT names, rezkustaging.com 32, guestinnovations.com, rezkupos.com 10), the 271-URL rezku.com href-fixpoint corpus (0 hits for webhook/endpoint/REST API/api key; "developer" hits are careers postings and the legal boilerplate "Developer Name and Address"), Wayback CDX on three doc-shaped hosts, and the OAuth metadata. ROBOTS: auth.rezku.com robots.txt is 26 bytes, "User-agent: *" + "Disallow: /" -- a GENERIC bar, it does not name ClaudeBot/anthropic-ai/Claude-User, so the .well-known and /login reads were browser-reads permitted by the standing order; recorded here. Retrieved 2026-09-18. https://developer.rezku.com/ · retrieved 2026-09-18 adversarially verified
API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator
extensibility-api-access-cost
Not scored by this record.
A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator
extensibility-free-sandbox
Not scored by this record.
Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).
extensibility-oauth-partner-apps
Rezku runs a real OAuth 2.0 authorization server. Its RFC 8414 metadata document returns HTTP 200 with issuer https://auth.rezku.com, authorization_endpoint /oauth/authorize, token_endpoint /oauth/token, jwks_uri /.well-known/jwks.json, response_types_supported ["code"], code_challenge_methods_supported ["plain", "S256"] and grant_types_supported ["client_credentials", "authorization_code", "password", "refresh_token"]. developer.rezku.com is itself a client of it, redirecting to /oauth/authorize with client_id, redirect_uri, state and a scoped request (scope=https://rezku.com/profile#read), so scoped authorization-code grants are in use. Shortfall: the metadata advertises no scopes_supported and does include the resource-owner "password" grant, which is credential sharing; and developer.rezku.com is login-gated (302 to auth.rezku.com/login), so there is no public evidence that an operator can grant and individually revoke a third-party app's access. https://auth.rezku.com/.well-known/oauth-authorization-server · retrieved 2026-08-03 · not refetchable · site policy · graded A when read
The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.
extensibility-webhooks-push
No webhook or event-push documentation is publicly reachable. developer.rezku.com returns 302 to auth.rezku.com/login and both /docs and /api on that host 404 unauthenticated; rezku.com/pos/api and rezku.com/api render the generic marketing shell with no API reference. The support KB Integrations section holds only an Integration List (ADP, Paychex, MailChimp, 7shifts, Chowly, It's A Checkmate, YellowDog, Shogo, Restaurant 365, Ziosk, Bar-i, Bev-Check, MarginEdge, DoorDash Drive) and a Chowly article, none of which mentions webhooks, event subscriptions or polling. The OAuth authorization-server metadata at auth.rezku.com establishes that an API exists but says nothing about event delivery, so neither push nor polling-only can be established from public sources. || 322nd: NEW 2026-09-17: the crt.sh subdomain census (rezku.com, rezkustaging.com, guestinnovations.com) found no anonymous API or webhook doc. developer.rezku.com and developer.rezkustaging.com are both behind OAuth, and swagger/openapi probes on every api.* host were 404, 500 or AccessDenied. The Online Ordering app bundle (order.rezku.com/v2, 27 files, 2.57 MB) has 0 tokenised hits for webhook/webhooks/callback_url (POISON: subscription = 15 hits, all RxJS Subscription). That is one client app, so it cannot bound a no. Retrieved 2026-09-17. || 329th: 329th: the fourth vendor domain rezkupos.com (crt.sh, 10 CT names: api, developer, reporting, files.reporting, training, manager, manager-origin, lb, apex, www) was censused for the first time and holds no anonymous API or event doc -- api.rezkupos.com and reporting.rezkupos.com 404 on /swagger, /swagger/index.html, /swagger/v1/swagger.json, /openapi.json, /api-docs, /docs, /redoc, /v3/api-docs with bodies indistinguishable from the /zzz-nonsense-xyz control; developer.rezkupos.com is NXDOMAIN; manager.rezkupos.com and training.rezkupos.com both 302 into auth.rezku.com/oauth/authorize. auth.rezku.com/.well-known/oauth-authorization-server (530 bytes, anonymous) enumerates grant types and endpoints only -- no registration_endpoint, no event or callback surface named. HELD UNKNOWN, not `no`: Rezku's API is an UNPUBLISHED partner API (the 327th rule -- a capability `no` on webhooks is not bounded by any public census when the vendor's API is unpublished), and the Zoho KB that documents the integrations is 403 at both the HTML and the portal API even with a valid CSRF token. Retrieved 2026-09-18. adversarially verified
Webhooks are cryptographically signed (e.g. HMAC) AND documented to retry with backoff, with a replayable event log for missed deliveries. differentiator
extensibility-webhook-reliability
Not scored by this record.
A public write API accepts externally originated orders into the POS as first-class tickets that fire to KDS/printers and land in reporting.
extensibility-order-injection-api
Not scored by this record.
The vendor is a named DoorDash Preferred Integration Partner (DPIP) under the 2026 program requirements. differentiator
extensibility-doordash-preferred
Not scored by this record.
Direct, first-party certified integrations exist with DoorDash, Uber Eats, and Grubhub without requiring a paid middleware layer (Otter/Chowly/Deliverect/Checkmate). differentiator
extensibility-first-party-delivery-integrations
Not scored by this record.
The POS is a supported endpoint for at least two major aggregation middleware platforms (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate).
extensibility-middleware-compatibility
Not scored by this record.
Native, vendor-maintained connectors exist for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export.
extensibility-accounting-connectors
Not scored by this record.
Labor hours export natively to at least two named payroll providers (e.g. Gusto, ADP, Paychex, Paylocity) without manual re-keying.
extensibility-payroll-export
Not scored by this record.
The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.
extensibility-app-marketplace
Not scored by this record.
The vendor supports a headless/embedded mode where a third-party UI (kiosk, web ordering, drive-thru) drives the POS transaction engine via API.
extensibility-headless-embedded
Not scored by this record.
A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator
extensibility-data-portability-exit
Not scored by this record.
Reliability, offline & operations
Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.
reliability-offline-order-entry
Of the claim's three legs only order entry is supported by the docs: with Offline Mode active, orders can be created and tendered on-terminal -- credit card data is stored and forwarded ("store credit card transaction data if the internet is down and process the transactions when internet access is restored") and non-credit transactions ("cash, gift card, external payment") plus refunds process offline, with an Offline History screen tracking Queued vs Sent. Named shortfall: ticket routing and check printing while offline are documented nowhere -- the Offline Mode and Rezku POS App Settings articles are payments-scoped and silent on kitchen and receipt printing, and the Back Office Settings index (20 articles) contains no connectivity or offline-behaviour article that covers it. Offline Mode is also a manual manager toggle (PIN, chosen duration, signed disclaimer) capped by "Do not exceed 48 hours in Offline Mode", not automatic on-terminal continuation. https://support.rezku.com/portal/en/kb/articles/offline-mode · retrieved 2026-08-04
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
CLAIM: KDS and/or kitchen printer routing continues offline. VERDICT: still unknown. NEW EVIDENCE: https://rezku.com/pos/hardware-pricing FAQ "Does Rezku's restaurant POS service work offline?": "Absolutely. Rezku's restaurant POS works offline, allowing your staff to take orders and process payments without an internet connection. All data syncs automatically once you're back online." -- offline order-taking is marketed, the kitchen is not mentioned. The contract scopes it narrower: Rezku POS Terms of Use (https://rezku.com/pos/terms-of-use) "Offline Mode" -- "allows you to temporarily operate certain elements of the Services and maintain data relating thereto, such as accepting credit and debit cards and storing transaction and card information", and while offline "you may not have access to or use" features normally available with a Connection. Pricing page: "Industry leading offline mode"; features/all: "24hr offline payments". Control over the 271-URL corpus: KDS within 80 chars of offline/internet/network/local = 0 hits. NEW SURFACE STATE 2026-09-16: support.rezku.com/portal/en/kb/* no longer renders anonymously -- a headless-Chrome render of /portal/en/kb/articles/ingredients lands on auth.rezku.com/login ("Sign in to backoffice ... Not a user? Create account"), and the Zoho portal API (/portal/api/kbRootCategories, /kbArticles/articleByPermalink, with the page's own portalId and crmcsrfparam token) answers 403 FORBIDDEN; Wayback CDX was 503. The anonymous corpus used here is the rezku.com marketing/legal site: 124-URL sitemap.xml plus an href fixpoint = 271 URLs fetched, 260 at 200, 11 at 404 (soft-404 body ~38 KB, calibrated on /nonsense-xyz-123). Retrieved 2026-09-16. || 329th: 329th, APP-LEVEL SURFACES FOR THE KDS PRODUCT ITSELF (new): (1) the App Store publisher census -- itunes.apple.com/lookup?id=549623317&entity=software lists all ELEVEN Guest Innovations apps, incl. Rezku Smart KDS (id 1569081712, v1.2.8, updated 2026-03-09) and Rezku Restaurant POS System (id 1154674244, v26.9.1, 2026-09-02). The POS listing says "* 3-day offline transactions mode" (vendor-authored store copy, grade C) and separately "* Kitchen display app", but the offline bullet is scoped to TRANSACTIONS. The Smart KDS listing enumerates ten features -- "Touch-screen control of orders / All wireless easy-setup / Automatic queue configuration / Rush Orders to the front of the queue / Per-product done status / Unlimited multi-station control / Timers and time reporting / Sticker printer integration / All day make items list / Integration with 3rd party delivery systems" -- with no offline, cache, local-network or store-and-forward statement. Google Play (com.dinnerwire.SmartKDS, updated Mar 6 2026) carries only the one-liner "Restaurant kitchen display system exclusively for users of Rezku Point of Sale." (2) The KDS app's own SETTINGS MODAL, read at full resolution from the store screenshots (mzstatic .../1600x0w.png rewrite of the 2732x2048 originals, app build 1.1.4(1)): the whole dialog is Time Limits (ticket timer turns orange after 5 min, red after 10), Font Size, Ticket Width (360 px), Hide Ticket Numbers, Always Show Customer, Alert Sound, and the buttons Reset Expeditor / Refresh / Save -- no offline, network, cache or retry setting; the station bar is All Day | Grill | Salad | More | Show Finished | Last with a per-ticket Bump and a live All-Day column. (3) rezku.com/restaurant-pos/restaurant-kitchen-management-software is a complete Smart KDS feature enumeration (Sequential order numbers, Multiple view modes, Real time ticket progress, Set RUSH status, printer integration, All-day orders, Recipe book, Fully adjustable, Custom alert sounds, Update inventory/86, Adjust pacing live, "Direct print from KDS printer -- Send orders from the KDS straight to impact, thermal, or label printers", Send SMS) and again says nothing about operating while offline. HELD UNKNOWN, not `no`: per the 326th merge rule an absent offline statement does not carry a capability `no`, and one screenshot of a settings modal is not a census of the KDS app's configuration. Retrieved 2026-09-18. adversarially verified
The system automatically fails over to a backup printer or KDS station when a configured kitchen printer is unreachable, and alerts staff.
reliability-printer-fallback
Staff are alerted: Configuring POS Printers documents a per-printer status indicator including "Disconnected (Red) -- The configured printer did not respond when Rezku tried to print", and the POS permission list carries manual recovery actions "Reprint items in the print queue" and "Resend items to the kitchen printer". Shortfall: recovery is manual and the automatic-failover half of the claim is absent -- Print Queues describes "Assigning the queue to a device (printer or KDS)", singular, with no backup-device field, and no rerouting to a secondary printer or KDS on failure is documented in either the printer or print-queue articles. https://support.rezku.com/portal/en/kb/articles/configuring-pos-printers · retrieved 2026-08-03
The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).
reliability-sync-conflict-handling
Not scored by this record.
The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).
reliability-offline-feature-matrix
Not scored by this record.
A public, per-component status page exists showing current and historical incident state without a login.
reliability-public-status-page
Not scored by this record.
24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.
reliability-247-live-support
Not scored by this record.
The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator
reliability-onsite-install
Not scored by this record.
A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.
reliability-hardware-replacement-sla
Not scored by this record.
The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.
reliability-pci-dss-4-attestation
Not scored by this record.
Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.
reliability-mfa-role-based-access
Not scored by this record.
A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.
reliability-self-serve-training
Not scored by this record.
Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. differentiator
reliability-failover-terminal-role
Not scored by this record.
Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.
reliability-cellular-backup
Not scored by this record.
Commercial, compliance & data ownership
Vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core POS software tier. differentiator
commercial-month-to-month-contract
Not scored by this record.
Vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. differentiator
commercial-no-early-termination-fee
Not scored by this record.
The auto-renewal term and the required cancellation notice window (e.g. 30/60/90 days) are stated in publicly accessible contract terms rather than only in a signed quote.
commercial-autorenew-terms-published
CLAIM: auto-renewal term and cancellation notice window stated in public contract terms. VERDICT: yes, grade B (vendor's own legal terms, anonymous, HTTP 200). EVIDENCE: Rezku POS Terms of Use ("Last modified January 15, 2026"), https://rezku.com/pos/terms-of-use , section 13 "Term of Agreement.": "Unless otherwise stated in the Order Form or other writing signed by us, the initial term ("Initial Term") of this Agreement is 3 years (36 months). Following the end of the Initial Term and any renewal term, the Agreement automatically renews for periods of 12 months (each a "Renewal Term"), unless either party gives written notice of its intent to terminate or not renew the Agreement at least 90 days before the then-current term expires." Cancellation mechanics: "you may terminate all or a portion of your Services subscription and/or Agreement at any time at the end of the Term by completing and e[mailing the] Cancellation Form by email to support@rezku.com"; early termination fee "$149 plus your monthly fees multiplied by the number of months remaining until the end of the current term"; $299 reinstatement fee. The same text is repeated in the combined https://rezku.com/privacy-policies-and-terms-of-use page. POISON: that combined page also carries an older Restaurant Management / Waitku app terms block ("Last modified December 14, 2020") saying "There are no set up or cancellation fees" with month-to-month card charging -- a superseded app-subscription clause, not the current POS agreement; the dedicated /pos/terms-of-use page does not contain it (0 hits). Supersedes the old note "Pricing page states no minimum contract length", which read only the pricing page. Retrieved 2026-09-16. https://rezku.com/pos/terms-of-use · retrieved 2026-09-16 adversarially verified
The POS software can be purchased and operated with a third-party payment processor of the operator's choice (no mandatory in-house processing lock). differentiator
commercial-processing-not-bundled
Not scored by this record.
Vendor publishes an interchange-plus (cost-plus) processing rate option with the markup stated as a specific bps + per-transaction figure, rather than only blended/flat card-present rates. differentiator
commercial-interchange-plus-published
Not scored by this record.
The processing agreement caps or prohibits unilateral vendor-initiated rate increases outside of pass-through interchange/network changes, or grants penalty-free exit on any increase. differentiator
commercial-rate-increase-clause
Not scored by this record.
Per-location and per-additional-terminal software pricing is published as specific dollar figures on the vendor's public site (not 'contact sales' only).
commercial-pricing-published
Specific figures published: $99/mo up to 3 stations, $19/mo per hardware station, $50/mo per kiosk, $39/mo DoorDash Drive, $399/mo Advantage. https://www.rezku.com/pos/pricing/ · retrieved 2026-08-01
Individual modules (online ordering, KDS, loyalty, inventory, payroll, marketing) can be purchased à la carte and cancelled independently without repricing the base POS subscription. differentiator
commercial-module-unbundling
Not scored by this record.
All required terminals, KDS screens, and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental.
commercial-hardware-purchase-outright
Pricing page lists hardware only as a $19/mo per-station rental bundle; no outright purchase price is published. https://www.rezku.com/pos/pricing/ · retrieved 2026-08-01
Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator
commercial-hardware-not-locked
Not scored by this record.
Operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee.
commercial-data-export-self-serve
Not scored by this record.
Guest/customer records, loyalty balances or point ledgers, and gift-card liability balances are exportable in machine-readable form by the operator. differentiator
commercial-export-customer-and-loyalty
Not scored by this record.
Contract or documentation specifies a post-termination data retrieval window (a defined number of days during which the operator can still export their data) rather than immediate cutoff. differentiator
commercial-post-termination-export-window
Not scored by this record.
Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator
commercial-data-ownership-clause
Not scored by this record.
Vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A / SAQ P2PE-HW, and names the applicable SAQ.
commercial-pci-p2pe-tokenization
Not scored by this record.
Vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — notably MFA for all access to the cardholder data environment including POS and back-office logins, and (for hosted ordering pages) payment-page script integrity monitoring per Req 6.4.3/11.6.1.
commercial-pci-dss-4-controls
Not scored by this record.
Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.
commercial-privacy-dsar-tooling
Not scored by this record.
Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator
commercial-wcag-kiosk-accessibility
Not scored by this record.
POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator
commercial-dual-pricing-compliant
Not scored by this record.
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 4 values — 4 upheld, 0 downgraded, 0 upgraded. It separately resolved 27 previously unknown values. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| order-capture-scheduled-orders | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | The 2026-08-01 pass recorded no docs because it looked at rezku.com/pos/*, which 302s to a dead Freshdesk portal. The live knowledge base is at support.rezku.com/portal/en/kb (Zoho Desk). Online Ordering Settings there documents "Open for Pre-Orders" with a "Preorders Days In Advance" setting and the POS permission list has "Open orders for future dates", so future-dating is real. Held at partial because Order Settings documents kitchen release only at Checkout or Payment, with no per-channel lead time and no computed fire time. source |
| menu-pricing-modifier-price-by-parent-size | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-yes | The Variations article states the mechanism outright: "The modifier matrix allows you to change the price of modifiers based on product variants. This is ideal for something like Pizza, where the cost of toppings modifiers can change based on the size of the product." It is configured per product under Product Properties > Modifier Matrix, one price per variation. Corroborated independently by the Modifiers and Submodifiers article, which lists "Product / Modifier price matrices (Edit Modifier Matrix)" among the things NOT cloned when a modifier group is duplicated. Grade B product documentation, matrix rather than duplication — exactly what the claim asks for. source |
| payments-refund-void-controls | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-yes | Both legs are documented. Authorization: Employee Permissions carries discrete toggles "Void a transaction", "Adjust a transaction", "Refund cash", "Refund credit cards", "Apply custom discounts to orders and products", "Manage the cash drawer" and "Cash drawer pay-in/pay-out", assignable by role and overridable per user. Audit: the Reports List documents Product Voids "showing user and manager override if applicable", Transaction Voids, Refunds (with reason), Comped and Discounted Orders (with reason), Cash Drawer Activity including no-sale, and Sales Exception by User. Immutability is not asserted by the vendor and is noted as such rather than assumed. source |
| kitchen-expo-consolidation | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | Rezku Smart KDS does have an Expo mode — "Expo can mark items done and bump tickets in this view and it will ALSO perform the operation on the selected station KDS" — so the capability is not absent. But the documented model is switching to a selected station and acting on it, and neither the KDS article nor the kitchen-management page states that an order stays open until every contributing station has bumped. That completion-gating is the substance of the claim, so partial with the shortfall named. source |
| kitchen-bump-bar-hardware | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-no | Positive absence, not silence. Rezku's hardware KB is an exhaustive supported-model catalogue split into four categories, and I read all four: Printers (Star TSP-100, SP-700, mC-Print3, SII RP F-10, Epson TM-u220, TM-m30, sticky-label), Stands and Cases, Card Readers (MagTek), Accessories (Ubiquiti router, Ubiquiti gateway/AP, automatic cash drawer, Viewsonic touchscreen for KDS, Socket Mobile barcode scanner). The KDS input device Rezku documents and sells is a touchscreen; no bump bar or programmable keypad appears in any category, and the Smart KDS article describes only touch. The claim's own bar is "documented supported models", and in a catalogue that names a model for every other peripheral there is none. source |
| delivery-zone-pricing | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | The Fees article documents map-drawn zones — "Multiple fee zones can be created with overlapping areas to apply fees based on distance from the restaurant automatically", drawn by adjusting vertex points under "Set Delivery Area". Only the fee is per-zone: the order minimum is a single global "Delivery Minimum Order Total" in Online Ordering Settings, and no per-zone promise time exists in Delivery Settings, Delivery Management or Delivery Venues (which are preset hotel/campus addresses, not zones). Two of the claim's three per-zone attributes are missing. source |
| digital-account-saved-payment | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | Only "one-click reordering" is claimed, and only on the marketing page — grade D. I checked the documentation for the other two legs: Online Site Settings covers design, logos, notifications and SEO with no account management; Online Ordering Settings covers order types and timing with no address book or stored cards; Checkout and Payment Types enumerates every tender (credit, cash, check, gift card, key-in, CRM charge, house account, external, bar tab) and card-on-file is not among them. Partial with the missing legs named. source |
| guest-loyalty-unified-profile | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | One CRM database is fed by both channels — "Typically, new customers will be added when they place an order online or on the POS and their information is entered for the first time" — with a rich profile (contact, birthday, anniversary, order count, average/high/total sales, top-3 favourites) and system-tracked fields the operator cannot edit. What the claim additionally requires and the article does not supply is documented dedup/merge behaviour on phone or email match; kiosk is not mentioned anywhere in the CRM article either. source |
| guest-loyalty-lifecycle-automation | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | Rezku's marketing does claim automation — "automate messages for birthdays, special promotions, loyalty milestones, and more" (email-marketing page) and "Automated texts" plus "Personalized birthday and follow-up messages" (text-marketing page). That is grade D and covers one of the three named triggers. The documentation contradicts nothing but supports nothing: the Back Office KB has no campaign or automation article, Loyalty Points documents a manual four-step points-and-discount-preset flow, and the CRM article's marketing path is CSV export as "a mailing list" plus a Mailchimp integration. Lapsed win-back appears nowhere. source |
| labor-granular-rbac | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | The granularity leg is emphatically satisfied — roughly 55 named per-action toggles (Void a transaction, Refund cash, Refund credit cards, Apply custom discounts, Manage the cash drawer, Manually set a price for a product, Access settings, Enable offline mode, View performance data, and so on), with four role defaults plus "Make individual permissions exceptions on a per-user basis without changing their role". Held at partial only because the claim also requires grants scoped per location and the article is silent on it; Rezku does sell multi-location, so this is a real gap rather than an inapplicable one. source |
| labor-manager-override-audit | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | There is an audit trail and it is queryable — Event Logs capture Back Office setting changes, filterable by date range and by user ("You can filter the event log by user and only view Back Office activity performed by the selected user"), with expandable per-event detail. But its scope is Back Office configuration, not POS manager approvals; the only approver attribution I found for an override is inside the Product Voids report ("showing user and manager override if applicable"). No general override trail and no immutability or retention statement. source |
| inventory-unit-conversion-yields | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | The ingredient record does carry a purchase-to-tracking conversion — "My cost is" / "For every" / "Tracking unit", an Ingredient Unit Type of Count, Solid or Liquid, a Tracking Unit and Custom Units, converting automatically between like unit types. Two of the claim's requirements are missing: no third recipe unit distinct from the tracking unit (Components says only "Enter the amount of each component that is used"), and no yield or waste percentage applying a raw-to-usable factor. Waste is an observed quantity in the Ingredient Use reports, not a conversion. source |
| inventory-count-modes | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | Counting exists but in one mode. The Inventory Take Report "helps you when re-ordering or performing a physical count/audit for ingredients" and its Amount column is "a placeholder for you to enter a value" used either for planned order amounts or for writing physical counts on a printed sheet; a POS permission "Change inventory counts on the iPad" also exists. No scheduled recurring cycle count, no subset spot-count mode, and no statement that each count is retained as dated variance history rather than overwriting the prior on-hand figure. I also read Inventory Countdown and Low Ingredient Emails, which do not address counting workflow. source |
| reporting-realtime-dashboard | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | A dashboard exists and defaults to the current day — "The dashboard gives you a quick, clear view of restaurant performance in a graphical format", "By default, when the dashboard loads it shows you stats for the current day". Neither the Dashboard nor the Reports article states any refresh latency or uses live/real-time wording, and the Reports article says "Reports are viewed in the browser" without mentioning a mobile app. The real-time and off-premise-mobile legs of the claim are asserted only on the advanced-reporting and Manager's App marketing pages, which is grade D and cannot carry them. source |
| reporting-eod-closeout | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-yes | Rezku ships exactly the single-document EOD packet the claim describes. The Exports List documents it: "The Daily Report is a 'paper dashboard' that contains multiple reports. It is divided into 2 sections, Sales and Transactions with multiple tables in each", downloadable as PDF. Its tables reconcile gross sales, comps, discounts, net sales, gift-card loads, taxes, fees, gratuity, prepaid orders, tips and refunds (Sales Overview); tender types via an embedded copy of the Transactions report, which the Reports List defines as "total transactions by payment type"; and cash position via Cash In/Out including bank drops, pay-ins/outs and tip payouts. Every element named in the claim is present in one artifact. source |
| reporting-pmix-modifier-level | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | Item-level product mix exists (Top Products with quantity, sales, profit and share; Sales by Category with gross, comps, discounts and net; Variants with selection counts) and modifier-level exists as a separate "Modifier" report — "product modifier usage showing default/selected status and upcharges". The claim wants one report at item AND modifier level with quantity, gross and net sales: they are split, the Modifier report is documented as usage-and-upcharge rather than gross/net, and no revenue-center filter is documented (daypart is available via "Filter by Time" and configured meal periods). The Exports list has no product-mix export covering modifiers. source |
| multi-location-org-hierarchy | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | Multi-location reporting is genuine — the Reports article lets you "select the locations to include in the report" and merge or split them, and the Reports List documents "Sales by Restaurant" comparing orders, sales, labor, food cost and profit across sites. But that is a flat set of restaurants. I read the whole Back Office KB tree and no region, group or enterprise object exists as a first-class entity; Restaurant Information configures one restaurant profile, and nothing scopes reporting or permissions to a group. Three named levels is the bar and only two are evidenced. source |
| multi-location-price-zones | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | Two of the three axes are documented on the item record without duplication: channel, via Menu Design's "Online Price" and "3rd Party Price -- Set the 3rd party app price if different than the online price"; and daypart, via Happy Hours under Promotions plus the POS permission "Apply period pricing outside of period". The location-group axis is absent — no price tier, zone or location group appears in Menu Design or anywhere else in the Back Office KB, and there is no per-location price field. source |
| extensibility-oauth-partner-apps | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | Found primary evidence the 2026-08-01 pass missed: auth.rezku.com serves an RFC 8414 authorization-server metadata document (HTTP 200) declaring authorization_endpoint /oauth/authorize, token_endpoint /oauth/token, a jwks_uri, response_types_supported ["code"], PKCE via code_challenge_methods_supported ["plain", "S256"], and grant_types_supported ["client_credentials", "authorization_code", "password", "refresh_token"]. developer.rezku.com is itself an OAuth client of it and issues a scoped request (scope=https://rezku.com/profile#read). So this is OAuth 2.0, not static shared keys. Not a yes: no scopes_supported is published, the resource-owner "password" grant is enabled, and the developer portal is login-gated (302 to auth.rezku.com/login) so operator-granted, individually revocable third-party access cannot be verified. source |
| reliability-printer-fallback | unknown / grade F — placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | Half the claim is documented: Configuring POS Printers shows a per-printer status indicator with "Disconnected (Red) -- The configured printer did not respond when Rezku tried to print", which is the staff alert, and the permission list carries "Reprint items in the print queue" and "Resend items to the kitchen printer" as manual recovery. The automatic-failover half is absent — Print Queues documents "Assigning the queue to a device (printer or KDS)", singular, with no backup-device field, and no article describes rerouting to a secondary printer or KDS on failure. source |
| order-capture-offline-order-entry | unknown / grade F -- placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | The live KB (support.rezku.com/portal/en/kb, Zoho Desk) has a dedicated Offline Mode article the 2026-08-01 pass never reached. It establishes that cash, gift card and external-payment transactions plus refunds process while offline and that card transactions are stored and forwarded, so on-terminal order entry and cash tender are real. Held at partial rather than yes because the published offline scope stops at payments: neither Offline Mode nor Rezku POS App Settings addresses modifiers, kitchen printing or KDS send during an outage, and the claim explicitly requires the vendor to publish what does and does not work offline. Vendor also warns "Do not exceed 48 hours in Offline Mode." The rezku.com/pos/offline-mode marketing URL now 302s to /restaurant-pos/features, whose only offline sentence is "Your restaurant does not go down if internet fails" -- grade D and too vague to lift the cell. source |
| menu-pricing-nested-modifiers | unknown / grade F -- placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | Modifiers and Submodifiers documents per-group Minimum and Maximum selection counts and requiredness driven off Minimum, but states a hard depth cap in the vendor's own words: "Submodifiers can only nest one level deep. If a modifier in a group has any submodifiers already applied, that group can not be used as a submodifier in another group." Two levels available against the three the claim requires, with the workaround of chaining groups explicitly blocked. That is positive documented evidence of a limitation, so partial with a named shortfall rather than unknown -- and not no, since the selection-count and forced-selection halves of the claim are fully met. source |
| kitchen-station-routing | unknown / grade F -- placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-yes | Print Queues gives the configuration path end to end -- create queue, Choose Products and toggle the products into it, assign the queue to a printer or (via the Smart KDS flag) a KDS -- and the Smart KDS article confirms the device end with "Select the queue name to assign this station or set up as Expediter." Item-level routing satisfies the claim's granularity, and per-location control is an explicit Global toggle: on, "all tablets obey the same printer rules"; off, "queue assignments will be made locally for each POS station." All configured in Back Office by the operator. Grade B product documentation, which is what a yes on this claim needs. Noted but not penalised: queue membership is by product only, with no documented order-type or revenue-center routing condition. source |
| order-capture-split-merge | unknown / grade F -- placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | Splitting Orders and Payments documents four modes -- Split Order, Itemized Split (by item; auto-per-seat when seats are used), Split By Seat, and Easy Split (even by default, arbitrary dollar amounts by tapping a split and entering a new amount with the rest auto-adjusting) -- and The More Button documents Merge: "Merge another ticket into the active order. The merged ticket will close with the status 'merged'." Held at partial because two elements the claim names are undocumented: a percentage-based split appears in no mode, and merging after a partial payment is stated nowhere in the live KB (the legacy merging-tickets article that covered merge restrictions 302s to a dead Freshdesk portal). source |
| digital-menu-single-source | unknown / grade F -- placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-yes | Online Product Settings shows the online menu is a visibility toggle over the Back Office menu record, not a second build: "Choose Products" expands the menu's own sections and "Use the toggle to enable the desired products for online ordering", with Select All enabling every item at once, and featured products picked from dropdowns of the same product list. The KB's own framing is that Back Office "is where your menu and the majority of settings live", and no article in the Online Ordering section describes maintaining a separate digital menu. Grade B product documentation on a table-stakes claim. source |
| hardware-offline-mode | unknown / grade F -- placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | The Offline Mode article documents order-taking and cash recording with the WAN down -- credit data is stored and forwarded, and non-credit tenders ("cash, gift card, external payment") plus refunds process offline, syncing to Rezku servers afterwards. Held at partial on three named grounds: kitchen printing offline is documented nowhere (the published offline scope is payments only); the claim's requirement that the vendor documents explicitly which functions degrade is unmet -- no such enumeration exists; and the mode is a manager-activated toggle with a signed disclaimer and the vendor's cap "Do not exceed 48 hours in Offline Mode", not automatic continuation. source |
| reliability-offline-order-entry | unknown / grade F -- placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | One of the claim's three legs is documented: with Offline Mode active, orders can be created and tendered on-terminal, since credit transactions store-and-forward and non-credit transactions plus refunds process offline with a Queued/Sent Offline History. The other two legs -- ticket routing and check printing while offline -- appear nowhere: the Offline Mode and Rezku POS App Settings articles are payments-scoped and silent on kitchen and receipt printing, and the Back Office Settings index has no connectivity article covering it. Scored consistently with the record's order-capture-offline-order-entry cell, which reached the same payments-only reading of the same article on 2026-08-04. source |
| commercial-pricing-published | yes, grade B - Specific figures published: $99/mo up to 3 stations, $19/mo | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| commercial-hardware-purchase-outright | no, grade B - Pricing page lists hardware only as a $19/mo per-station ren | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| payments-gift-cards | partial / D - "Loyalty Program & Gift Cards" marketed as first-party; real-time balances and cro | upheld | The cited https://www.rezku.com/pos/ now 301s to https://rezku.com/restaurant-pos/, which does still carry the phrase "Loyalty Program & Gift Cards" - but that is a feature-list bullet and cannot establish a balance ledger. I re-retrieved the real evidence in the support KB instead. The Gift Cards article gives the ledger (Current Balance, Add/Deduct Funds, dashboard of loads/spends/redeems/manual adjustments) and Gift Card Portal Settings gives guest balance lookup and the sentence "eGift cards work in-store and online", which closes the online-redemption half the old note wrongly called undocumented. I looked for a shared cross-location balance and found none; the Promotions section contains only CRM, Gift Cards, Loyalty Points, Coupons, Discount Presets and Happy Hours, and the sole multi-location mention is tag propagation. Value unchanged, evidence moved D -> B, note corrected. source |
| digital-first-party-web | partial / D - First-party online ordering plus QR, kiosk and tableside channels marketed; commi | upheld | The cited https://www.rezku.com/pos/ 301s to https://rezku.com/restaurant-pos/, a feature index that is not evidence of anything, so I re-retrieved. Online Site Settings in the support KB answers the branded-domain question the old note called unstated, and answers it negatively: "All Rezku OLO websites are hosted on Rezku servers at the URL 'Order.Rezku.com', followed by a serial number", with only a vanity keyword replacing the serial. The marketing page rezku.com/restaurant-pos/online-ordering supports the first-party/direct-to-POS half - "Your brand, your profits", "stop losing revenue to marketplace fees", "orders go straight to your POS" - and rezku.com/pos/pricing includes "Branded Online Ordering" in the $99/mo Basic plan. I found no statement of a per-order commission in either direction, so the second shortfall survives. Value unchanged; evidence D -> B and the note corrected from "not stated" to what the docs actually state. source |
Sources
Every URL this record cites. 52 in total.
- https://www.rezku.com/pos/
- https://www.rezku.com/pos/delivery/
- https://www.rezku.com/pos/pricing/
- https://support.rezku.com/portal/en/kb
- https://support.rezku.com/portal/en/kb/articles/variations
- https://support.rezku.com/portal/en/kb/articles/modifiers-and-submodifiers
- https://support.rezku.com/portal/en/kb/articles/employee-permissions
- https://support.rezku.com/portal/en/kb/articles/event-logs
- https://support.rezku.com/portal/en/kb/articles/reports-list
- https://support.rezku.com/portal/en/kb/articles/exports-list
- https://support.rezku.com/portal/en/kb/articles/reports
- https://support.rezku.com/portal/en/kb/articles/dashboard
- https://support.rezku.com/portal/en/kb/articles/ingredients
- https://support.rezku.com/portal/en/kb/articles/inventory-take-report
- https://support.rezku.com/portal/en/kb/articles/components
- https://support.rezku.com/portal/en/kb/articles/crm
- https://support.rezku.com/portal/en/kb/articles/loyalty-points
- https://support.rezku.com/portal/en/kb/articles/fees
- https://support.rezku.com/portal/en/kb/articles/delivery-venues
- https://support.rezku.com/portal/en/kb/articles/online-ordering-settings
- https://support.rezku.com/portal/en/kb/articles/order-settings
- https://support.rezku.com/portal/en/kb/articles/menu-design
- https://support.rezku.com/portal/en/kb/articles/rezku-smart-kds-kitchen-display-system
- https://support.rezku.com/portal/en/kb/articles/print-queues
- https://support.rezku.com/portal/en/kb/articles/configuring-pos-printers
- https://support.rezku.com/portal/en/kb/articles/offline-mode
- https://support.rezku.com/portal/en/kb/articles/rezku-pos-app-settings
- https://support.rezku.com/portal/en/kb/rezku-pos-hardware/accessories
- https://support.rezku.com/portal/en/kb/articles/integration-list
- not refetchable
- https://developer.rezku.com/
- https://rezku.com/restaurant-pos/online-ordering
- https://rezku.com/restaurant-pos/email-marketing
- https://rezku.com/restaurant-pos/text-marketing
- https://rezku.com/restaurant-pos/advanced-reporting
- https://rezku.com/restaurant-pos/restaurant-kitchen-management-software
- https://rezku.com/restaurant-pos/multi-location-restaurant-system
- https://support.rezku.com/portal/en/kb/articles/modifiers-and-submodifiers
- https://support.rezku.com/portal/en/kb/articles/print-queues
- https://support.rezku.com/portal/en/kb/articles/offline-mode
- https://rezku.com/pos/offline-mode
- https://support.rezku.com/portal/en/kb/rezku-pos-back-office/settings
- https://support.rezku.com/portal/en/kb/articles/splitting-orders-and-payments
- https://support.rezku.com/portal/en/kb/articles/the-more-button
- https://support.rezku.com/portal/en/kb/articles/online-product-settings
- https://support.rezku.com/portal/en/kb/rezku-pos-back-office/online-ordering
- https://rezku.com/pos/support/merging-tickets
- https://support.rezku.com/portal/en/kb/articles/gift-cards
- https://support.rezku.com/portal/en/kb/articles/gift-card-portal-settings
- https://rezku.com/restaurant-pos/
- https://support.rezku.com/portal/en/kb/articles/online-site-settings
- https://rezku.com/pos/pricing