Restroworks

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

POS and table management are listed as modules but no feature-level documentation is public.

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

Restroworks' own competitor-comparison pages assert an offline mode with a quantified window: 'Restroworks ensures your operations stay uninterrupted even when the internet drops. Orders, billing, and KDS continue to function without a single lag for up to 48 hours.' The identical block appears on the NCR Aloha, Oracle Micros Simphony, PAR POS and LS Retail comparison pages, and the ice-cream vertical page repeats 'Reliable offline mode to keep billing and order flow running even during internet disruptions.' Shortfall: this is vendor-authored comparison marketing (grade D), and the claim's second half is unmet - nothing published says what does NOT work offline. Card authorisation offline, cash tender specifically, handheld/tablet scope, KDS-to-terminal behaviour on a LAN-only outage, and sync-conflict handling on reconnect are all unaddressed; the word 'offline' appears nowhere in the api.restroworks.com API reference, and docs.restroworks.com is Auth0-gated (HTTP 400 at the org selector), so no first-party documentation of offline scope is publicly readable. https://www.restroworks.com/compare/ncr-aloha-vs-toast/ · 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

Cloud POS 'Push Order to Kitchen' documents isAdvance (Boolean, 'set to true if the order is an advance order') and advanceOrderDetails containing expectedDeliveryTime and preparationStartTime, both ISO date-time strings. The API states that if preparationStartTime is not supplied 'it will be set to one hour prior to the delivery time' - so future-dated orders are held and fired at a computed time rather than on receipt. Shortfall: the lead time is a fixed one-hour default otherwise supplied per order by the calling channel; no per-channel configurable lead time is documented, and the field appears only on the cloud-kitchen order-push endpoint, not on the dine-in/POS order path. https://api.restroworks.com/ · 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

The Standard Menu (Menu Sync V2) schema is recursive, which establishes at least two levels: an entity carries 'modifiers' (Array, 'List of modifiers for the entity'), each modifier group carrying min ('Minimum selection for the modifier'), max ('Maximum selection for the modifier'), order, isActive and constituentItems; and each constituent item is itself a full entity record that again carries its own 'modifiers' (Array, 'List of modifiers for the entity') plus 'variants'. So min/max are independent per level, as the claim requires. Shortfall: the reference never states a supported nesting depth, and every published example has constituentItems[].modifiers empty ([]), so a third level is structurally expressible but nowhere documented or demonstrated. There is also no separate forced-selection/required flag anywhere in the modifier schema - the only mechanism is min >= 1, which the docs do not describe as enforcing a required choice. The admin-side menu builder that would settle both points is behind the Auth0-gated docs.restroworks.com, and restaurant-menu-management-software/ describes only offers and combo creation. https://api.restroworks.com/ · retrieved 2026-08-04

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

The Standard Menu (Menu Sync V2) reference enumerates the full modifier schema - type, _id, name, original_name, min, max, order, isActive, aliases, constituentItems, image, multiplePunchMin/Max/MaxItem, isPackagingType - and the constituent-item schema (price, tableTab, packingCharge, modifiers, variants, taxes). No per-parent or per-size price matrix field exists in either. The docs state Restroworks supports four menu item types (Normal, Modifiers/Add-ons, Variant Items, Combo) and that variants are separate child item records mapped to a parent ('regular, medium, and large are the variant items for the pizza'). The vendor's own sample data shows the duplication pattern the claim excludes: modifier groups named 'Choose From SIDE. for Classic Burger Chicken' and 'Choose From SIDE. for Jack Daddy Burger', and add-on items named 'Add On 7 UP Reg'. https://api.restroworks.com/ · 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

The enumerated modifier schema in the Standard Menu (Menu Sync V2) reference expresses modifier quantity as repeated punches - multiplePunchMin (0), multiplePunchMax (14), multiplePunchMaxItem (1), documented as 'Minimum punches for the modifier' and 'Maximum punches for the modifier'. The constituent item carries a single flat 'price'. There is no named tier (light/regular/extra) and no per-tier price multiplier anywhere in the schema. The documented mechanism for more of a topping is punching the same modifier again, which is precisely what the claim requires tiering to be distinct from. https://api.restroworks.com/ · retrieved 2026-08-03

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-versioning-effective-dates differentiator

Not scored by this record.

menu-pricing-franchise-hierarchy 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

Payment gateway integrations are referenced; no first-party terminal estate documented.

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

Checked and unresolved, not unexamined. Swept all 170 URLs in page-sitemap.xml (135 fetched, rest timed out) plus the marketplace and glossary sitemaps: the strings 'gift', 'voucher', 'prepaid', 'e-gift', 'stored value' and 'top-up' appear in no first-party Restroworks product page, and there is no gift-card product page in the sitemap at all. The api.restroworks.com API reference (full 2.2 MB Postman collection read; folders Data Integration, Online Order, Delivery, Loyalty Integration, Cloud POS, Stock) contains zero occurrences of 'gift' - its Loyalty Integration endpoints cover points redemption and coupons/rewards only. The only gift-card evidence found is two marketplace partner pages, /marketplace/qwikcilver/ and /marketplace/ticket-xpress/, which describe those vendors as gift-card platforms but are filed under 'Integration Category: Loyalty', describe only enrollment, points accumulation and rewards redemption, require a separate partner subscription, and are limited to India, Saudi Arabia and the UAE. That establishes a third-party route exists but not that Restroworks issues, tracks a balance for, or redeems a gift card - so it will not carry a 'partial' either. RestroAPP's 'in-app loyalty and wallet' is points/cashback/credits, not a transferable gift card. The one place this could be settled, docs.restroworks.com, redirects to restroworks.eu.auth0.com and returns HTTP 400 at the organization selector; academy.restroworks.com is likewise login-gated.

payments-house-accounts

Not scored by this record.

payments-split-tender

Not scored by this record.

payments-refund-void-controls

Site markets anti-theft controls within Insights, which implies void/discount policing, but no role-based approval or immutable audit trail is documented. https://www.restroworks.com/ · retrieved 2026-08-01

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-multi-entity-routing differentiator

Not scored by this record.

payments-p2pe-pci4

Not scored by this record.

kitchen-station-routing

Kitchen Suite includes a KDS and production system; routing configurability is not documented.

kitchen-expo-consolidation

Read the Kitchen Display System product page and the Kitchen Management Software page in full. The KDS page documents 'Multiple stations and channels support - categorize orders for station assignment based on order characteristics' and, separately, 'Order consolidation simplified - view a consolidated list of all orders to be prepared in a clutter-free view'. That is a single queue view of orders, not an expo screen aggregating one order's items across prep stations; no expo or expeditor screen is named anywhere on the site, and nothing describes an order being held incomplete until every contributing station has bumped. The API reference has no KDS or station endpoints. Unresolved because the only place this would be settled is the admin guide at docs.restroworks.com, which is Auth0 login-gated.

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 KDS page's first feature block is 'Order management - Maximize kitchen teamwork, minimize chaos with the bump bar feature', and a separate block documents 'Barcode bumping - swiftly marks orders ready with barcode scanning'. So non-touch bumping is a first-party KDS feature. Shortfall: the claim requires documented supported models, and no bump-bar or keypad hardware compatibility list is published anywhere - the pricing page refers only to unnamed 'hardware partners' offering 'tablets for order taking, POS terminal setups, printers, kitchen display systems and more'. https://www.restroworks.com/kitchen-display-system/ · 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

A delivery module is listed under back of house; driver entities and clock-in are not described.

delivery-dispatch-board

The Delivery Management page documents a 'Single screen view - streamline delivery management by overseeing all orders on a single screen with real-time tracking for efficiency', order routing ('efficiently route orders to multiple delivery partners'), live order-status updates and cancellation monitoring; the API's Delivery folder (Assign Delivery Person, Order Delivery Accepted/Rejected/Picked Up/Delivered) shows per-order assignment of a delivery person from the POS. Shortfall: none of the claim's distinguishing elements is documented - no driver-availability display, no per-order elapsed-time indicator, and no multi-order run batching anywhere (the documented assignment surface is strictly one order to one delivery person). The page is oriented to routing orders across third-party delivery partners rather than dispatching an own-driver fleet, and no dispatch or expo screen is named; the admin documentation that could settle batching is behind the Auth0-gated docs.restroworks.com (HTTP 400 at the org selector). https://www.restroworks.com/restaurant-delivery-management-software/ · retrieved 2026-08-04

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

Read the Delivery Management product page and the Delivery folder of the API reference (Assign Delivery Person, Order Delivery Accepted, Rejected, Picked Up, Delivered, Tracking Url, Get Delivery info). The word 'zone' appears nowhere in either. The Cloud POS order push carries delivery_area as a free-text string ('eg: Dubai Marina') and a charges array in which 'Delivery Charge' is a name/value pair supplied by the caller on the inbound order - the fee is passed in, not derived by Restroworks from a zone. Nothing describes a zone entity carrying its own fee, order minimum or promise time, but nothing states it is absent either, so this is unresolved rather than negative.

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

RestroWEB (own-branded ordering site) and RestroAPP (branded app) are first-party modules on the vendor's own platform. https://www.restroworks.com/ · retrieved 2026-08-01

digital-menu-single-source

Marketed as a unified platform where POS, kiosk, QR and web ordering are one system, which implies one menu record; no documentation of propagation behavior. https://www.restroworks.com/ · retrieved 2026-08-01

digital-native-app differentiator

Not scored by this record.

digital-account-saved-payment

Read the RestroAPP, RestroWEB, RestroNext suite and Online Ordering System pages. They document a branded native iOS/Android app and ordering website with 'secure payments', 'diverse payment options' and an 'in-app loyalty and wallet' offering 'points, cashback, or credits per order'. None of the three components the claim requires - a guest account with saved addresses, saved tokenized payment methods, and one-tap reorder of a previous order - is named on any of them; the RestroWEB aggregator comparison table lists 'Customer Data Access: Yes' but says nothing about stored credentials. The API reference contains no tokenization or saved-card endpoint, and the online-order push carries the customer address inline per order. Unresolved: a stored-value wallet is documented, card-on-file is not.

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

Loyalty and CRM are not clearly enumerated as first-party modules on the pages I could read.

guest-loyalty-thirdparty-identity-attach differentiator

Not scored by this record.

guest-loyalty-accrual-models

RestroAPP documents first-party 'In-app loyalty and wallet' - 'offer points, cashback, or credits per order' and 'run personalized offers and loyalty tiers'; the CRM page adds 'launch flexible loyalty programs with points, rewards, and coupons'. Shortfall: only a points/credit accrual model is documented. Neither visit/punch-count nor spend-tier accrual is described, so the claim's 'at least two of three' is not met, and both the CRM page ('seamlessly integrate with leading loyalty software') and the API reference (a Loyalty Integration folder whose endpoints are partner-hosted URLs Restroworks calls out to) frame serious loyalty as a bolt-on vendor. https://www.restroworks.com/restroapp-food-delivery-app/ · retrieved 2026-08-03

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 CRM page documents 'run automated campaigns via SMS, email, and WhatsApp', segmentation 'based on order history, frequency, and spending', and 'spot lapsed guests early and re-engage them with targeted retention campaigns'; RestroAPP adds 'drive repeat orders with event-based triggers' and 'bring back lapsed customers with smart notifications'. Shortfall: lapsed win-back is the only one of the claim's three named automations that appears; birthday and first-visit thank-you are mentioned nowhere as shipped campaigns - the sole birthday reference is in a generic 'how does CRM improve customer retention' FAQ describing the category, not the product - and nothing describes these as always-on configurable triggers rather than manually launched segment sends. https://www.restroworks.com/restaurant-crm-software/ · 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-cdp-event-api 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

The vendor's own scheduling round-up describes its Shift Management as 'employees can easily clock in and clock out within the billing system, recording their availability and attendance for the day', plus 'detailed attendance reports to help managers view and track daily employee attendance'. The POS product page separately lists 'Shift management'. Shortfall: the same passage continues 'pair this with detailed Day reports, and you can see which users have logged into the billing system throughout the day', which suggests attendance is derived from POS login sessions rather than a discrete time punch; no credential mechanism (PIN, badge or card) is stated anywhere, and this exists only as a vendor marketing claim with no admin documentation behind it. https://www.restroworks.com/blog/best-restaurant-scheduling-app/ · retrieved 2026-08-03

labor-photo-punch-verification differentiator

Not scored by this record.

labor-geofenced-mobile-punch

Not scored by this record.

labor-offline-time-punch differentiator

Not scored by this record.

labor-granular-rbac

Distinct IT, operations, finance and owner personas are marketed, which hints at role scoping, but no permission model is published.

labor-manager-override-audit

The Anti-Theft Application page documents tracking of 'potential theft transactions, including voiding bills, discounting items, reprinting bills, and refunds', 'bill-level theft insights - get deeper insight with each bill approval of the transaction', historical analysis and real-time alerts; the Data Integration bills API returns a _currentUser object (username, first and last name) on each bill. Shortfall: the docs never state that the approving manager is recorded separately from the employee who applied the discount or void, and nothing describes the trail as immutable or as a queryable override log - it is presented as a loss-prevention analytics layer over transactions rather than an attributed approval audit trail. https://www.restroworks.com/restaurant-anti-theft-software/ · 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-fair-workweek-support

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

Not scored by this record.

labor-server-performance-metrics differentiator

Not scored by this record.

inventory-recipe-bom-costing

Kitchen Suite includes recipe management and central kitchen management alongside inventory and supply chain; sub-recipe nesting and automatic recost are not documented. https://www.restroworks.com/ · retrieved 2026-08-01

inventory-unit-conversion-yields

The Stock API inventory payload models units explicitly: unit: { unitName: 'KG', conversionFactor: 1000, baseUnit: { name: 'GRAM', id: 1 } }, with items carrying both quantity and baseQuantity (e.g. quantity 0.13 / baseQuantity 130) and basePrice alongside price. A stocking unit with an explicit conversion factor to a base unit is therefore first-class. Shortfall: only one unit-with-conversion is modelled per item - there is no separate purchase, recipe and count unit - and the word yield appears nowhere in the reference; no yield or waste percentage is applied to raw-to-usable conversion in any documented field. https://api.restroworks.com/ · 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 Stock API fetch_Inventory_data endpoint enumerates its accepted transactionType values in full: stock_entry, physical_stock, vendor_return, wastage_entry, stock_opening, stock_sale, retrievable per customer and date range. physical_stock establishes that full physical counts are a distinct recorded transaction with its own dated history rather than an overwrite. Shortfall: that enumeration is the complete list of stock transaction types and contains no ad-hoc spot count of a subset and no scheduled recurring cycle count; the inventory product page speaks only of 'automating stock counts' and barcode/QR scanning without distinguishing count modes. https://api.restroworks.com/ · 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-transfers

Not scored by this record.

inventory-commissary

Not scored by this record.

inventory-lot-traceability

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

Insights offers 200+ reports and a mobile "cockpit" app for off-premise viewing; refresh latency is not stated. https://www.restroworks.com/ · retrieved 2026-08-01

reporting-eod-closeout

Read the Enterprise Reporting page (marketed as 200+ reports), the Analytics page, the Cockpit App page and the Operations page. The Operations page documents 'sales reconciliation - verify that payments and receipts match sales records', and the Data Integration API returns per-invoice NetSales, TotalTax, GrossSales, Discount and ReturnValue plus a bill-level aggregation of net rounded amount, total tax and total amount with payments broken out by card type. But no daily close-out, day-end or Z-report artifact is named on any page, and tips, tender-type totals and expected cash deposit appear in no documented report or payload. The 200+ report catalogue itself is not published, so I could neither confirm nor exclude an EOD packet.

reporting-pmix-modifier-level

The Analytics page documents item-level sales reporting - 'compare historical data to track trends and item sales across multiple stores', 'item journey tracking: discover the life cycle of your items, from production costs to profit', and 'identify your peak days and hours and understand your daily sales trends' - against a catalogue of 200+ enterprise reports. Shortfall: this is item-level only. Modifier-level product mix is not mentioned on any page, and filtering is described by outlet/deployment, aggregator and time period rather than by revenue centre; no report showing quantity plus gross and net sales per modifier is documented. https://www.restroworks.com/restaurant-analytics-software/ · 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-multiloc-drilldown differentiator

Not scored by this record.

reporting-custom-report-builder differentiator

Not scored by this record.

reporting-scheduled-delivery

Not scored by this record.

reporting-raw-warehouse-export differentiator

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

Explicitly targets multi-location chains, franchises and enterprises as distinct org types; a named three-level hierarchy object is not documented. https://www.restroworks.com/ · retrieved 2026-08-01

multi-location-central-menu-publish

The BFCD (Brand, Format, Cluster, Deployment) architecture page documents 'create and manage your menu from one central location, then deploy it to all of your restaurants with just a few clicks', 'live menu updates: take charge of your menu at different locations by easily updating prices with a few clicks', and 'roll out offers region-wise'; the POS and Menu Management pages repeat centralised authoring with real-time sync. Shortfall: publication is described as pushing to all restaurants or to a region, with no documented ability to select an arbitrary set of target locations for a single publish, and no publish or version history recording what was pushed, when, and by whom. https://www.restroworks.com/solution-architecture/ · retrieved 2026-08-03

multi-location-local-override-policy differentiator

Not scored by this record.

multi-location-price-zones

The Standard Menu (Menu Sync V2) schema carries per-channel pricing on the item record itself: a tableTab array of { tabId, itemRate, itemStatus } on each entity and on each modifier constituent item, where a tab is an order type (dine-in / takeaway / delivery). The Online Order docs confirm 'Restroworks customers have the provision that they can keep a different menu for takeaway and delivery as well'. So one item record does carry different prices per order channel without duplication. Shortfall: no location-group or price-zone object appears anywhere in the schema, and no daypart price tier exists - configuration>rules holds date, time and day validity governing availability, not price. https://api.restroworks.com/ · retrieved 2026-08-03

multi-location-scheduled-publish differentiator

Not scored by this record.

multi-location-new-store-template differentiator

Not scored by this record.

multi-location-corp-vs-franchisee-roles differentiator

Not scored by this record.

multi-location-royalty-calculation differentiator

Not scored by this record.

multi-location-royalty-collection

Not scored by this record.

multi-location-consolidated-reporting

Not scored by this record.

multi-location-normalized-item-rollup differentiator

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-config-audit-log differentiator

Not scored by this record.

multi-location-enterprise-api differentiator

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

Tablets, terminals, printers and KDS are referenced as hardware options; no OS versions or device specs published.

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

Restroworks' own competitor-comparison pages carry the only quantified offline statement it publishes: 'Restroworks ensures your operations stay uninterrupted even when the internet drops. Orders, billing, and KDS continue to function without a single lag for up to 48 hours' (identical block across the NCR Aloha, Oracle Micros Simphony, PAR POS, LS Retail and Revel comparison pages); the ice-cream vertical page repeats 'Reliable offline mode to keep billing and order flow running even during internet disruptions.' Shortfall: the claim's second requirement is wholly unmet - no published page enumerates which functions degrade offline (card auth, loyalty lookup and refunds are all unaddressed), cash-sale recording offline is never specifically stated, and kitchen printing is not named (only KDS). The main POS product page (restaurant-pos-system/) and the Front of House page contain no offline mention at all, 'offline' appears nowhere in the api.restroworks.com reference, and docs.restroworks.com is Auth0-gated (HTTP 400 at the org selector) - so offline scope exists publicly only as comparison-page marketing. https://www.restroworks.com/compare/ncr-aloha-vs-toast/ · retrieved 2026-08-04

hardware-kds

Kitchen Display System is a first-party module within the Kitchen Suite, not an integration dependency. https://www.restroworks.com/ · retrieved 2026-08-01

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

REPLACES an undated first-pass placeholder that said 'Claims API integrations with 500+ third-party apps but I found no publicly readable API reference' -- while nine cells in this same record cite api.restroworks.com at grade A, retrieved 2026-08-03 and 2026-08-04, quoting its schemas field by field. Re-fetched anonymously 2026-09-01 under our own UA: HTTP 200, no robots.txt on the host (404, so allowed under RFC 9309), no login wall and no partner gate. The page is titled 'Restroworks API Reference' and its own introduction says 'A quick introduction about Restroworks and how you can get started with our API', adding separately that 'The Restroworks API reference document includes detailed information'. The substance behind that landing page is recorded in this record's own grade-A cells, which read its sub-pages on 2026-08-03 and 2026-08-04: the Cloud POS push-order endpoint with its advance-order fields, the recursive Standard Menu (Menu Sync V2) modifier schema, the Stock API transaction-type enumeration, and per-endpoint authentication statements. SHORTFALL, recorded not scored: this reference is rendered client-side, so only the introduction is present in the initial HTML payload and the per-endpoint pages named by those sibling cells are not reachable from this URL alone -- their quotations belong to those sub-pages, not to this one. https://api.restroworks.com/ · retrieved 2026-09-01

extensibility-api-access-cost differentiator

Not scored by this record.

extensibility-partner-revshare

Not scored by this record.

extensibility-free-sandbox differentiator

Not scored by this record.

extensibility-oauth-partner-apps

The API reference states its authentication mechanism per endpoint and OAuth is not among them. Data Integration: 'Authorization for the request is achieved using an API Key', with apiKey passed as a query parameter alongside customer_key. Stock: 'This API requires Basic Authentication. Authorization header: Authorization: Basic'. Online Order, Delivery, Cloud POS and Loyalty endpoints are all keyed on a static per-outlet customer_key in the query string. The published collection declares no collection-level auth at all, and the words OAuth, scope, consent and revoke appear nowhere in the reference. These are shared static credentials, not scoped operator-granted individually revocable grants. https://api.restroworks.com/ · retrieved 2026-08-03

extensibility-webhooks-push

Outbound push exists but is narrow. The Delivery folder documents 'Assign Order to delivery - this hook will notify the integrated partner whenever a delivery order is assigned to a delivery boy from POS', with the payload posted to a partner-supplied webhook URL, and the production checklist lists 'menu updates via webhook / menu pull on webhook asynchronously'. Shortfall: those are the only two push surfaces documented - a delivery-assignment event and menu updates. None of the order lifecycle events the claim names is pushed; bills and invoices are retrieved by polling GET /pos/bills with from/to epoch timestamps and a page parameter, and order state is read back through GET /online_order/order_status. https://api.restroworks.com/ · retrieved 2026-08-03

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-data-symmetry differentiator

Not scored by this record.

extensibility-published-rate-limits

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-bi-data-warehouse differentiator

Not scored by this record.

extensibility-app-marketplace

Not scored by this record.

extensibility-custom-fields-scripting

Not scored by this record.

extensibility-headless-embedded

Not scored by this record.

extensibility-api-versioning-deprecation

Not scored by this record.

extensibility-data-portability-exit differentiator

Not scored by this record.

reliability-offline-order-entry

The vendor's comparison pages state 'Restroworks ensures your operations stay uninterrupted even when the internet drops. Orders, billing, and KDS continue to function without a single lag for up to 48 hours', and the ice-cream vertical page repeats 'Reliable offline mode to keep billing and order flow running even during internet disruptions' - first-party confirmation that order entry and billing continue through an outage. Shortfall: of the claim's three elements only order entry is squarely covered. Check printing is never named (only 'billing'), and ticket routing rests on the bare assertion that KDS 'continue[s] to function' with no description of on-terminal routing versus a cloud round-trip; both statements are vendor comparison/vertical marketing (grade D), the main POS product page itself says nothing about offline, and no admin documentation of the offline mechanism or reconnect behaviour is publicly readable - docs.restroworks.com is Auth0-gated (HTTP 400 at the org selector). https://www.restroworks.com/compare/ncr-aloha-vs-toast/ · 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

Searched every first-party product page I retrieved (POS, KDS, Kitchen Management, Front of House, Back of House, Operations, Solution Architecture, Online Ordering, RestroNext and the four CX product pages) for the word offline. It occurs exactly once, on the Inventory page - 'offline connectivity: keep track of your inventory, even when you are offline, easily sync your data when you are back online' - which is the stock-taking mobile app, not the kitchen path. Nothing states whether KDS routing or kitchen printing survives a network outage, and the API reference has no offline or printer surface. Unresolved rather than negative because the vendor also never enumerates what does stop working offline.

reliability-printer-fallback

The word printer appears once across all first-party pages I retrieved - on the pricing page, listing printers among the hardware categories partners supply. No page describes kitchen printer configuration, printer groups, failover to a backup printer or KDS station, or unreachable-device alerting, and the API reference exposes no printing endpoints. The KDS page's alerting content concerns order status and colour coding, not device health. Unresolved: nothing confirms the behaviour and nothing states it is unsupported.

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-contractual-uptime-sla differentiator

Not scored by this record.

reliability-incident-postmortems

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-backup-restore

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

The only terms document Restroworks publishes is a website terms of use, and it expressly places the commercial agreement outside public reach: 'Your use of Software is subject to all agreements such as Terms of Service and/or any other Service Level Agreements, License Agreements or any other Agreements that accompany the use of such Software and will be signed separately between you and Restroworks.' The words renew, renewal, subscription term, cancellation and notice period appear nowhere in it. I also walked the complete page sitemap at /page-sitemap.xml: there is no MSA, subscription agreement, service terms or SLA page, and the pricing page publishes no figures and routes to 'Get an estimate'. The renewal term and notice window are therefore available only in a signed quote. https://www.restroworks.com/website-terms-of-use/ · retrieved 2026-08-03

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

Pricing page affirmatively declines to publish figures, listing only the three variables that determine a quote. https://www.restroworks.com/pricing/ · retrieved 2026-08-01

commercial-module-unbundling differentiator

Not scored by this record.

commercial-hardware-purchase-outright

Hardware is priced separately per the pricing page, but no list prices and no statement on lease versus purchase.

commercial-hardware-not-locked differentiator

Not scored by this record.

commercial-implementation-fee-published

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-source-available-selfhost

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-soc2-attestation

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.