Rezku POS

order-capture-floor-plan-editor

Not scored by this record.

order-capture-seat-level

Not scored by this record.

order-capture-coursing-hold-fire

Not scored by this record.

order-capture-split-merge

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

order-capture-bar-tab-preauth differentiator

Not scored by this record.

order-capture-transfer-audit

Not scored by this record.

order-capture-native-handheld

Not scored by this record.

order-capture-offline-order-entry

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

order-capture-qr-same-check differentiator

Not scored by this record.

order-capture-kiosk-first-party differentiator

Not scored by this record.

order-capture-drive-thru

Not scored by this record.

order-capture-drive-thru-timers

Not scored by this record.

order-capture-voice-ai differentiator

Not scored by this record.

order-capture-throttling differentiator

Not scored by this record.

order-capture-scheduled-orders

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

order-capture-catering

Not scored by this record.

order-capture-order-ready-signal differentiator

Not scored by this record.

order-capture-void-comp-controls

Not scored by this record.

menu-pricing-nested-modifiers

Per-group selection control is fully there: "Minimum -- No less than this number of modifiers in the group can be selected, including quantity" and "Maximum -- No more than this number of modifiers in the group can be selected, including quantity", with requiredness implemented through the Minimum field ("This is used to make a modifier required") rather than a separate forced-selection flag. Named shortfall: depth. The vendor states the cap outright -- "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." That is two levels (modifier group -> modifier -> submodifier), not the three the claim asks for, and the second sentence is an explicit guard against chaining groups to get deeper. https://support.rezku.com/portal/en/kb/articles/modifiers-and-submodifiers · retrieved 2026-08-04

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

Variations article: "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." Configured per product under Product Properties > Modifier Matrix by picking a variation from a dropdown and entering that size's modifier price. The Modifiers and Submodifiers article independently confirms "Product / Modifier price matrices (Edit Modifier Matrix)" exist as a distinct object (they are not cloned when a modifier group is duplicated). A matrix, not per-size duplication. https://support.rezku.com/portal/en/kb/articles/variations · retrieved 2026-08-03

menu-pricing-fractional-placement differentiator

Not scored by this record.

menu-pricing-half-and-half-rule differentiator

Not scored by this record.

menu-pricing-topping-quantity-tiers

A dedicated Pizza POS edition with "custom menu management" is marketed, but no half-and-half, fractional or quantity-tier pricing mechanics are documented.

menu-pricing-size-style-matrix differentiator

Not scored by this record.

menu-pricing-included-allowance differentiator

Not scored by this record.

menu-pricing-combos

Not scored by this record.

menu-pricing-upsell-prompts differentiator

Not scored by this record.

menu-pricing-86-propagation

Not scored by this record.

menu-pricing-countdown-auto-86 differentiator

Not scored by this record.

menu-pricing-dayparting

Not scored by this record.

menu-pricing-channel-price-books

Not scored by this record.

menu-pricing-dual-pricing differentiator

Not scored by this record.

menu-pricing-allergen-nutrition

Not scored by this record.

menu-pricing-recipe-linkage differentiator

Not scored by this record.

menu-pricing-3p-menu-push

Not scored by this record.

menu-pricing-dynamic-pricing

Not scored by this record.

payments-processor-choice differentiator

Not scored by this record.

payments-published-rates differentiator

Not scored by this record.

payments-dual-pricing differentiator

Not scored by this record.

payments-surcharge-guardrails differentiator

Not scored by this record.

payments-emv-nfc

Hardware bundle includes a "credit card reader"; EMV/NFC and Apple/Google Pay support are not specified.

payments-softpos-tap-to-pay differentiator

Not scored by this record.

payments-pay-at-table

Not scored by this record.

payments-qr-guest-pay differentiator

Not scored by this record.

payments-tip-adjust

Not scored by this record.

payments-tip-pooling differentiator

Not scored by this record.

payments-offline-store-and-forward differentiator

Not scored by this record.

payments-offline-decline-liability differentiator

Not scored by this record.

payments-gift-cards

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

payments-house-accounts

Not scored by this record.

payments-split-tender

Not scored by this record.

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

payments-chargeback-tooling differentiator

Not scored by this record.

payments-card-on-file differentiator

Not scored by this record.

payments-payout-timing differentiator

Not scored by this record.

payments-p2pe-pci4

Not scored by this record.

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

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

kitchen-course-firing differentiator

Not scored by this record.

kitchen-prep-time-pacing differentiator

Not scored by this record.

kitchen-order-throttling differentiator

Not scored by this record.

kitchen-channel-pause-propagation differentiator

Not scored by this record.

kitchen-order-ready-callback differentiator

Not scored by this record.

kitchen-bump-bar-hardware

The 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

kitchen-all-day-counts

Not scored by this record.

kitchen-sla-alerts

Not scored by this record.

kitchen-printer-fallback differentiator

Not scored by this record.

kitchen-offline-operation differentiator

Not scored by this record.

kitchen-item-build-screens differentiator

Not scored by this record.

kitchen-pizza-fractional-display differentiator

Not scored by this record.

kitchen-recall-refire

Not scored by this record.

kitchen-order-modification-alerts differentiator

Not scored by this record.

kitchen-guest-ready-notification differentiator

Not scored by this record.

kitchen-waste-logging

Not scored by this record.

kitchen-speed-of-service-reporting

Not scored by this record.

kitchen-prep-forecasting

Not scored by this record.

delivery-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

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

delivery-route-map differentiator

Not scored by this record.

delivery-driver-tracking differentiator

Not scored by this record.

delivery-zones-polygon differentiator

Not scored by this record.

delivery-zone-pricing

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

delivery-address-validation

Not scored by this record.

delivery-driver-comp differentiator

Not scored by this record.

delivery-cash-reconcile

Not scored by this record.

delivery-daas-dispatch

Not scored by this record.

delivery-daas-fallback differentiator

Not scored by this record.

delivery-3p-direct-integration differentiator

Not scored by this record.

delivery-3p-injection

Not scored by this record.

delivery-menu-push

Not scored by this record.

delivery-86-sync

Not scored by this record.

delivery-store-pause

Not scored by this record.

delivery-3p-reconciliation differentiator

Not scored by this record.

delivery-injection-error-visibility differentiator

Not scored by this record.

delivery-tracking-page

Not scored by this record.

delivery-promise-time differentiator

Not scored by this record.

delivery-offline-behavior

Not scored by this record.

digital-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

digital-menu-single-source

The online ordering menu is not a separate build -- Online Product Settings' "Choose Products" is a visibility toggle over the existing Back Office menu tree: expand each menu section and "Use the toggle to enable the desired products for online ordering", with a Select All toggle that enables every item from the menu at once; the up-to-three featured products are likewise picked from dropdowns of the same product list, organized by the menu's own categories. The KB describes Back Office as "where your menu and the majority of settings live", and item edits (Product Properties, Variations, modifier matrices) are made once against that record. Nothing in the Online Ordering section (Online Ordering Settings, Online Site Settings, Set Online Hours, Closures, Gift Card Portal Settings, Online Product Settings) describes a second digital menu record or duplicate item entry. https://support.rezku.com/portal/en/kb/articles/online-product-settings · retrieved 2026-08-04

digital-native-app differentiator

Not scored by this record.

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-upsell-engine differentiator

Not scored by this record.

digital-scheduled-pacing

Not scored by this record.

digital-fulfillment-modes

Not scored by this record.

digital-qr-table

Not scored by this record.

digital-kiosk differentiator

Not scored by this record.

digital-group-ordering

Not scored by this record.

digital-catering-portal differentiator

Not scored by this record.

digital-voice-ai-phone differentiator

Not scored by this record.

digital-drivethru-ai

Not scored by this record.

digital-sms-ordering

Not scored by this record.

digital-google-order differentiator

Not scored by this record.

digital-apple-business-connect

Not scored by this record.

digital-loyalty-attach

Not scored by this record.

digital-subscriptions

Not scored by this record.

digital-promo-parity

Not scored by this record.

digital-guest-data-ownership differentiator

Not scored by this record.

digital-checkout-pci-sca

Not scored by this record.

digital-surcharge-transparency differentiator

Not scored by this record.

guest-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

guest-loyalty-thirdparty-identity-attach differentiator

Not scored by this record.

guest-loyalty-accrual-models

A loyalty program exists in marketing; accrual models are not described.

guest-loyalty-tiers differentiator

Not scored by this record.

guest-loyalty-offline-behavior differentiator

Not scored by this record.

guest-loyalty-offer-stacking-rules differentiator

Not scored by this record.

guest-loyalty-targeted-offers differentiator

Not scored by this record.

guest-loyalty-rfm-segmentation differentiator

Not scored by this record.

guest-loyalty-lifecycle-automation

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

guest-loyalty-native-email-sms differentiator

Not scored by this record.

guest-loyalty-consent-management

Not scored by this record.

guest-loyalty-10dlc-registration

Not scored by this record.

guest-loyalty-campaign-attribution differentiator

Not scored by this record.

guest-loyalty-data-export-portability differentiator

Not scored by this record.

guest-loyalty-review-capture-routing differentiator

Not scored by this record.

guest-loyalty-referral-program

Not scored by this record.

guest-loyalty-wallet-pass differentiator

Not scored by this record.

guest-loyalty-privacy-rights-tooling

Not scored by this record.

guest-loyalty-redemption-fraud-controls

Not scored by this record.

guest-loyalty-ai-offer-recommendation differentiator

Not scored by this record.

guest-loyalty-stored-value-gift

Not scored by this record.

labor-clock-in-at-pos

Employee management and tip pooling are marketed; POS PIN/badge clock-in is not explicitly documented.

labor-photo-punch-verification differentiator

Not scored by this record.

labor-offline-time-punch differentiator

Not scored by this record.

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

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

labor-native-scheduling differentiator

Not scored by this record.

labor-demand-labor-forecast differentiator

Not scored by this record.

labor-realtime-labor-percent differentiator

Not scored by this record.

labor-overtime-prevention differentiator

Not scored by this record.

labor-break-compliance-by-state differentiator

Not scored by this record.

labor-minor-labor-rules

Not scored by this record.

labor-tip-pooling-rules

Not scored by this record.

labor-tip-distribution-audit-trail

Not scored by this record.

labor-qualified-tips-w2-reporting differentiator

Not scored by this record.

labor-native-payroll differentiator

Not scored by this record.

labor-payroll-export-formats

Not scored by this record.

labor-shift-swap-workflow differentiator

Not scored by this record.

labor-server-performance-metrics differentiator

Not scored by this record.

inventory-recipe-bom-costing

"Inventory management" is marketed with no recipe/BOM or sub-recipe detail.

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

inventory-theoretical-vs-actual differentiator

Not scored by this record.

inventory-realtime-depletion differentiator

Not scored by this record.

inventory-86-auto-sync differentiator

Not scored by this record.

inventory-count-modes

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

inventory-mobile-count-offline

Not scored by this record.

inventory-vendor-catalogs-edi differentiator

Not scored by this record.

inventory-invoice-ocr differentiator

Not scored by this record.

inventory-price-change-alerts differentiator

Not scored by this record.

inventory-par-auto-suggest differentiator

Not scored by this record.

inventory-waste-logging

Not scored by this record.

inventory-shelf-life-expiry

Not scored by this record.

inventory-bar-partial-bottle

Not scored by this record.

inventory-cogs-gl-export

Not scored by this record.

inventory-native-not-partner differentiator

Not scored by this record.

inventory-menu-margin-linkage differentiator

Not scored by this record.

reporting-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

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

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

reporting-comps-voids-audit

Not scored by this record.

reporting-cash-over-short

Not scored by this record.

reporting-labor-productivity

Not scored by this record.

reporting-server-scorecards differentiator

Not scored by this record.

reporting-channel-profitability differentiator

Not scored by this record.

reporting-scheduled-delivery

Not scored by this record.

reporting-public-api differentiator

Not scored by this record.

reporting-webhooks differentiator

Not scored by this record.

reporting-api-not-upcharged differentiator

Not scored by this record.

reporting-tier-paywall differentiator

Not scored by this record.

reporting-history-retention differentiator

Not scored by this record.

reporting-anomaly-alerts differentiator

Not scored by this record.

reporting-nl-query

Not scored by this record.

reporting-guest-cohorts differentiator

Not scored by this record.

reporting-sales-forecast differentiator

Not scored by this record.

reporting-tip-tax-compliance

Not scored by this record.

multi-location-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

multi-location-central-menu-publish

Walked the whole Back Office KB tree at support.rezku.com/portal/en/kb/rezku-pos-back-office looking for a corporate-menu publish flow; no article covers one. Menu Design, the rest of Product Management (Components, Variations, Modifiers and Submodifiers, Product Properties, Print Queues, Courses, Product Taxes) and Settings > Restaurant Information are all written in single-restaurant terms: Menu Design covers creating menus, submenus, products and prices for one site, and Restaurant Information configures one restaurant profile. Multi-location surfaces only in the Reports article location picker and the Sales by Restaurant report, neither of which touches menu authoring. No publish action, target-location selection or publish/version history is described -- but equally no statement that menus cannot be pushed, so this is unresolved rather than absent. The Manager's App page claims price changes sync "across POS, online ordering, and kiosks", which is cross-channel, not cross-location.

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

multi-location-consolidated-reporting

Not scored by this record.

multi-location-cross-location-giftcard

Not scored by this record.

multi-location-cross-location-loyalty

Not scored by this record.

multi-location-multi-brand differentiator

Not scored by this record.

multi-location-multi-tax-jurisdiction

Not scored by this record.

multi-location-central-labor-policy

Not scored by this record.

hardware-commodity-devices differentiator

Not scored by this record.

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

hardware-handheld-purpose-built

Not scored by this record.

hardware-handheld-battery-swap differentiator

Not scored by this record.

hardware-handheld-lte

Not scored by this record.

hardware-offline-mode

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

hardware-kds

"Kitchen management" is marketed; whether a first-party KDS with routing and bump input is sold is not documented.

hardware-kiosk differentiator

Not scored by this record.

hardware-drive-thru

Not scored by this record.

hardware-printer-compatibility

Not scored by this record.

hardware-peripherals

Not scored by this record.

hardware-p2pe-terminal

Not scored by this record.

hardware-tap-to-phone differentiator

Not scored by this record.

hardware-pricing-transparency differentiator

Not scored by this record.

hardware-ownership-vs-lease differentiator

Not scored by this record.

hardware-usable-after-churn differentiator

Not scored by this record.

hardware-rma-sla differentiator

Not scored by this record.

hardware-byod

Not scored by this record.

hardware-remote-device-management differentiator

Not scored by this record.

hardware-selfpour-scales

Not scored by this record.

hardware-callerid-integration

Not scored by this record.

extensibility-public-api-docs

Still unresolved on 2026-09-01, but re-grounded on what was measured rather than on a failed search. developer.rezku.com is live and IS a developer portal: it answers HTTP 200 and immediately 302s the whole site to auth.rezku.com/login carrying a complete OAuth 2.0 authorization-code request -- response_type=code, a fixed client_id, redirect_uri back to developer.rezku.com/auth-redirect, scope https://rezku.com/profile#read and a state nonce. So the portal exists and every page of it sits behind that flow; nothing of the reference is readable anonymously. Its robots.txt is a genuine 63-byte HTTP 404, so the host permits us under RFC 9309 2.3.1.3 and the gate is authentication, not policy. WHY THIS IS NOT SCORED `no`: the login page is the ordinary Rezku back-office sign-in and it offers self-serve account creation ('Not a user? Create account'), so the barrier may be a free registration rather than the signed partner agreement, NDA or sales call the claim actually excludes -- and those are different verdicts. Settling it needs an account, which is out of scope for an anonymous read. NOT to be re-probed anonymously: the redirect is deterministic and re-fetching developer.rezku.com will only reproduce the login.

extensibility-api-access-cost differentiator

Not scored by this record.

extensibility-free-sandbox differentiator

Not scored by this record.

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

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.

extensibility-webhook-reliability differentiator

Not scored by this record.

extensibility-order-injection-api

Not scored by this record.

extensibility-menu-write-api differentiator

Not scored by this record.

extensibility-doordash-preferred differentiator

Not scored by this record.

extensibility-first-party-delivery-integrations differentiator

Not scored by this record.

extensibility-middleware-compatibility

Not scored by this record.

extensibility-accounting-connectors

Not scored by this record.

extensibility-payroll-export

Not scored by this record.

extensibility-app-marketplace

Not scored by this record.

extensibility-headless-embedded

Not scored by this record.

extensibility-data-portability-exit differentiator

Not scored by this record.

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

reliability-offline-card-auth differentiator

Not scored by this record.

reliability-offline-decline-liability differentiator

Not scored by this record.

reliability-lan-degraded-multi-terminal differentiator

Not scored by this record.

reliability-local-transaction-engine differentiator

Not scored by this record.

reliability-offline-kds-printing

Rezku's offline documentation is scoped entirely to card payments and never addresses the kitchen. The Offline Mode article covers storing credit card transactions until the internet returns and warns "Do not exceed 48 hours in Offline Mode"; Rezku POS App Settings offers only "Enable offline mode to store credit card payments until internet service is restored" plus an Offline History view. Neither kitchen printing nor KDS behaviour during an outage is mentioned there, in Configuring POS Printers, or in Print Queues. The Smart KDS article states "Both the POS and the KDS must be open and on the same network" and printers are configured on the LAN, which would suggest local routing survives a WAN outage -- but that is inference, not documentation, and the vendor makes no such statement either way.

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

reliability-sync-conflict-handling

Not scored by this record.

reliability-offline-feature-matrix

Not scored by this record.

reliability-public-status-page

Not scored by this record.

reliability-247-live-support

Not scored by this record.

reliability-onsite-install differentiator

Not scored by this record.

reliability-menu-build-service differentiator

Not scored by this record.

reliability-hardware-replacement-sla

Not scored by this record.

reliability-pci-dss-4-attestation

Not scored by this record.

reliability-mfa-role-based-access

Not scored by this record.

reliability-self-serve-training

Not scored by this record.

reliability-failover-terminal-role differentiator

Not scored by this record.

reliability-cellular-backup

Not scored by this record.

commercial-month-to-month-contract differentiator

Not scored by this record.

commercial-no-early-termination-fee differentiator

Not scored by this record.

commercial-autorenew-terms-published

Pricing page states no minimum contract length and no renewal or cancellation-notice window.

commercial-processing-not-bundled differentiator

Not scored by this record.

commercial-interchange-plus-published differentiator

Not scored by this record.

commercial-rate-increase-clause differentiator

Not scored by this record.

commercial-pricing-published

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

commercial-module-unbundling differentiator

Not scored by this record.

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

commercial-hardware-not-locked differentiator

Not scored by this record.

commercial-data-export-self-serve

Not scored by this record.

commercial-export-customer-and-loyalty differentiator

Not scored by this record.

commercial-post-termination-export-window differentiator

Not scored by this record.

commercial-data-ownership-clause differentiator

Not scored by this record.

commercial-pci-p2pe-tokenization

Not scored by this record.

commercial-pci-dss-4-controls

Not scored by this record.

commercial-privacy-dsar-tooling

Not scored by this record.

commercial-wcag-kiosk-accessibility differentiator

Not scored by this record.

commercial-dual-pricing-compliant differentiator

Not scored by this record.