Vendors / Regional & international
Restroworks
Restroworks (formerly Posist)
A broad unified restaurant platform — POS, kitchen suite, supply chain, kiosk/QR/app/web ordering and 200+ reports — but essentially everything is marketing-page-level claim with no public product documentation to verify against.
scored live legacy rubric
- Claims in scope
- 312
- Scored
- 45
- Assessed
- 45
- Unknown
- 267
- Not applicable
- 2
- Values challenged
- 1
unknown, never as no.Identity
- Owner
- Restroworks — privately held, India-headquartered; rebranded from Posist (rebrand not confirmed on the current site, which makes no reference to the former name)
- Who it is for
- Restaurant chains, cloud kitchens and franchises in India, the Middle East and Southeast Asia, expanding into the US; claims 25,000+ restaurants globally across QSR, fine dining, food courts, stadiums and cinemas
- Site
- https://www.restroworks.com/
Pricing
transparency: unknown · unit: Quote only (modules × terminals × hardware) · processor lock-in: unknown
- Software
- No figures published. Pricing page states it varies by software modules selected, restaurant size and terminal count, and hardware requirements; routes to "Get an estimate" / sales.
Capabilities
Every claim is binary and checkable. Grades: A primary documentation · B product documentation · C pricing or feature page · D marketing claim · E third-party reporting · F inference with no source. A yes on a differentiator claim requires A or B.
Order capture & FOH workflow
Provides a graphical floor-plan editor where an operator can draw sections, place tables of varying shape/capacity, save multiple floor-plan layouts per location, and assign sections to servers.
order-capture-floor-plan-editor
Not scored by this record.
Order lines can be tagged to a seat number at entry, and the check can be split by seat afterward without re-keying items.
order-capture-seat-level
Not scored by this record.
Items can be assigned to courses and held, with a fire-next-course action available from a handheld or terminal that releases only that course to the kitchen.
order-capture-coursing-hold-fire
Not scored by this record.
Supports splitting a check by item, by seat, by even N-way, and by arbitrary dollar/percentage amount, and merging checks or tables back together, including after partial payment.
order-capture-split-merge
CLAIM: split by item, seat, even N-way and arbitrary amount, plus merge incl. after partial payment. VERDICT: partial/C. NEW SURFACE: the legacy Posist WordPress site www.posist.com, still live, never cited before. Its WP REST API answers anonymously (112 pages, 10 posts, 17 events, 25 glossary) and so does its blog at /restaurant-times/wp-json (1,528 posts). EVIDENCE: https://www.posist.com/restaurant-pos-system/ (HTTP 200, modified 2024-08-26): 'Generate split bills on demand and facilitate easy transfer between tables'. wp-json/wp/v2/pages/7944 (restaurant-order-taking-app, public URL now 301s to restroworks.com/restaurant-tablet-ordering-system/): 'Cater to customer's demands to split bills on the basis of amount or items consumed'. wp-json/wp/v2/pages/7713 (pubs-bar-breweries-software, 301): 'Split the food and drinks bill or split one large bill into smaller ones as per the customers' preference'. Blog post 539 (/restaurant-times/posist-product/8-ways-restaurant-billing-promotes-improved-customer-experience.html, published 2015, bulk re-save stamp 2023-08-24, now 301): 'Posist introduced split bill module ... generates separate bills upon request, in two ways: a) Amount ... b) Items'. SHORTFALL: split by seat, even N-way split, merging checks and anything after partial payment are named nowhere. Table transfer is not a check merge. The current restroworks.com pages (192 via WP REST) mention split bills only in a tip calculator and a marketplace partner blurb. docs.restroworks.com is GitBook behind VA-Auth0 visitor auth (307 to integrations.gitbook.com/.../visitor-auth), so it is gated. Retrieved 2026-09-16. https://www.posist.com/restaurant-pos-system/ · retrieved 2026-09-16 adversarially verified
Opens a bar tab against a card pre-authorization with a configurable auth amount, supports incremental re-auth as the tab grows, and auto-closes stale tabs at end of day. differentiator
order-capture-bar-tab-preauth
Not scored by this record.
An open check can be transferred between servers, tables, and devices, and the transfer is recorded in an audit log naming both employees.
order-capture-transfer-audit
Not scored by this record.
Ships a first-party handheld ordering app running natively on the handheld device (not a remote/mirrored desktop session) that can send to kitchen and take a card payment tableside.
order-capture-native-handheld
Not scored by this record.
With the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen, and tender cash, and the vendor publishes what does and does not work offline.
order-capture-offline-order-entry
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
Guest QR at-table ordering writes items onto the same open check as server-entered items, rather than creating a separate order ticket. differentiator
order-capture-qr-same-check
Not scored by this record.
Offers a first-party self-order kiosk that renders the same menu and modifier tree as the POS with no separate menu build, and the vendor documents ADA/accessibility conformance for it. differentiator
order-capture-kiosk-first-party
Not scored by this record.
Supports drive-thru-specific order flow: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment.
order-capture-drive-thru
Not scored by this record.
Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.
order-capture-drive-thru-timers
Not scored by this record.
Vendor ships a first-party AI voice ordering agent for phone and/or drive-thru that injects orders directly as POS orders, or publishes a documented API partner program for third-party voice AI. differentiator
order-capture-voice-ai
Not scored by this record.
Supports order throttling: per-channel capacity limits per time slot with automatic quote-time extension when kitchen load exceeds a configured threshold. differentiator
order-capture-throttling
Not scored by this record.
Accepts future-dated/scheduled orders with a per-channel lead time and automatically injects them into the make queue at a computed fire time rather than on receipt.
order-capture-scheduled-orders
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
Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.
order-capture-catering
Not scored by this record.
Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator
order-capture-order-ready-signal
Not scored by this record.
Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.
order-capture-void-comp-controls
Not scored by this record.
Menu, modifiers & pricing engine
Payments & money movement
The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator
payments-processor-choice
Not scored by this record.
Vendor publishes card-processing pricing publicly (a specific flat rate or interchange-plus markup) rather than quote-only. differentiator
payments-published-rates
Not scored by this record.
Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator
payments-dual-pricing
Not scored by this record.
Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator
payments-surcharge-guardrails
Not scored by this record.
All first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay.
payments-emv-nfc
CLAIM: all first-party payment terminals accept EMV chip and NFC incl. Apple Pay/Google Pay. VERDICT: no/C, on the same basis as acrelec's no/C: Restroworks ships no first-party payment terminal; card-present payment is delegated to third-party acquirer terminals. NEW SURFACE: the Restroworks Kiosk app at https://kiosk.restroworks.com/ (bundle /assets/index-B_lv9Q6e.js, 1.4 MB, anonymous). EVIDENCE: its payment options are all third-party: 'payUsingPaytmEdc:"Pay Using Card Machine"', 'payUsingMashreq:"Pay Using Mashreq"', 'payUsingGeidea:"Pay Using Card"', 'payUsingNeoLeap:"Pay Using Card"', 'payUsingDojo:"Pay Using Card"', plus Pine Labs (20 hits) and an acquirer ECR error table ('E071:"EMV Processing Error"', 'Please use the chip reader instead of swiping your card.'), i.e. the terminal belongs to the acquirer. Marketing (grade C): https://www.restroworks.com/ 'being payment gateway and hardware agnostic'; /compare/ pages: 'Restroworks runs on your existing devices like POS terminals, tablets (iOS/Android), printers, KDS, and cash drawers'. The q314 WP REST census of www.restroworks.com (192 pages + 63 marketplace) names Geidea (9), Mashreq (8), Razorpay (11), Paytm (16) as partners and no Restroworks-branded terminal. BOUND: not a census of every hardware SKU a reseller might bundle; keep unknown if a Restroworks-branded payment device surfaces. Retrieved 2026-09-16. https://kiosk.restroworks.com/ · retrieved 2026-09-16 adversarially verified
Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. differentiator
payments-softpos-tap-to-pay
Not scored by this record.
Vendor ships a handheld that takes EMV/NFC payment at the table, including tip prompt and check splitting, without carrying the card away.
payments-pay-at-table
Not scored by this record.
Guest can scan a QR code on the printed check or table tent to view and pay the check from their own phone, with the payment closing the check in the POS automatically. differentiator
payments-qr-guest-pay
Not scored by this record.
Supports both pre-auth-then-tip-adjust and on-device tip prompt flows, with a documented batch/adjust window and a manager screen for unadjusted tips.
payments-tip-adjust
Not scored by this record.
Configurable tip pooling and distribution rules (by hours worked, sales, role percentage, or points) that produce a per-employee tip allocation exportable to payroll. differentiator
payments-tip-pooling
Not scored by this record.
Card payments can be captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. differentiator
payments-offline-store-and-forward
Not scored by this record.
Vendor publicly documents who bears the loss when a stored offline transaction declines on reconnect, and surfaces a post-reconnect report of failed offline payments. differentiator
payments-offline-decline-liability
Not scored by this record.
First-party gift cards with real-time balance tracking, redeemable across every location in the group and through the online-ordering channel.
payments-gift-cards
CLAIM: first-party gift cards with real-time balance tracking, redeemable across every location and through online ordering. VERDICT: partial/B, on the same basis as grubbrr's Paytronix partial/B. NEW SURFACE: https://posist.biz/ (<title>Posist</title>). This is the production Restroworks (ex-Posist) POS/back-office web client. Its HTML loads restroworks-stock-report-bucket.s3 and tickets.posist.co widgets, and the host was found through posist.biz's socket.io source map. The login page loads the AngularJS bundle https://posist.biz/app/99687fd3.app.js anonymously: 37.8 MB, concatenated, with templates inlined through $templateCache. It is the vendor's shipped code, so grade B. It has no source map (.map returns the SPA shell). A second copy, apptest.posist.co, is a TEST host that serves the same app unminified as 1,521 files (70 MB). It was used only to locate code, and every quote below is from the production bundle. EVIDENCE: the POS has a gift card module whose calls all go to a partner. Endpoints: /api/giftCards/activatePartner, /activateCard, /balance, /reloadCard, /redeem, /reverseRedeem, /cashOut, /exchange, /accountLookUp, /postBillToPaytronix, /transactionReverse. Every payload carries 'partner_name' ('return p.partner_name.toLowerCase() === 'paytronix''). The settings group "Qwikcilver Setting" has '{label:"Use Qwikcilver Gift card as Coupon",name:"qwikcilver_coupon"}' and "Send Item detail to Qwikcilver". A partner must be activated per deployment ('GiftCard.activatePartner(partner, $scope.deployment)'). There is an enterprise "Gift Card Report" (gift_card_report). So live balance lookup, redeem, reload and cash-out exist at the POS. SHORTFALL: the programme belongs to Paytronix or Qwikcilver; no Restroworks-issued card or ledger is present (tokenised: paytronix 83, qwikcilver 25, givex 0, valutec 0). Online-ordering redemption and cross-location redemption are not shown. The food-court 'recharge' card in the earlier note is a separate closed-loop card. Retrieved 2026-09-17. https://posist.biz/app/99687fd3.app.js · retrieved 2026-09-17 adversarially verified
House/on-account tabs with per-account credit limits, running balance, and periodic statement or invoice generation.
payments-house-accounts
Not scored by this record.
A single check can be settled with multiple tenders and split by seat, by item, by even shares, or by arbitrary amount, with no hard cap below eight ways.
payments-split-tender
Not scored by this record.
Voids, refunds, discounts, and no-sales require role-based authorization (manager PIN or approval) and write to an immutable audit log identifying the approver.
payments-refund-void-controls
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
In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator
payments-chargeback-tooling
Not scored by this record.
Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator
payments-card-on-file
Not scored by this record.
Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator
payments-payout-timing
Not scored by this record.
A single account can route settlement funds to different bank accounts per location or legal entity (separate MIDs or split settlement) under unified reporting. differentiator
payments-multi-entity-routing
Not scored by this record.
Vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance / P2PE listing available to merchants on request.
payments-p2pe-pci4
Not scored by this record.
Kitchen & production
Items route to specific KDS stations by item, category, order type, or revenue center, with routing rules configurable per location without vendor involvement.
kitchen-station-routing
CLAIM: items route to KDS stations by item/category/order type/revenue center, configurable per location without vendor involvement. VERDICT: partial/C. EVIDENCE: https://www.restroworks.com/kitchen-display-system/ (HTTP 200), section 'Multiple stations and channels support': 'Categorize orders for station assignment based on order characteristics. Optimize kitchen workflow, assigning orders seamlessly to specialized stations. Reduce cross-station confusion'. https://www.restroworks.com/compare/restroworks-vs-qsr-automations/ (grade D): 'Restroworks goes further with customizable routing workflows that ensure every order reaches the right station. We also offer multiple ways to bump orders, whether auto, KOT-wise, item-wise, or via bump bars'. The same page's table lists 'Customizable routing'. SHORTFALL: routing by named dimensions (item, category, order type, revenue center) is not enumerated, and nothing says operators configure it per location themselves. The admin guide (docs.restroworks.com, GitBook + Auth0 visitor auth) is gated. The Postman API reference (api.restroworks.com, 2.26 MB collection 26990305/2s93Y2RgPD) has 0 tokenised hits for kds/kitchen/station/routing. Retrieved 2026-09-16. https://www.restroworks.com/kitchen-display-system/ · retrieved 2026-09-16 adversarially verified
An expo screen consolidates items from multiple prep stations into a single order view and only marks the order complete when every contributing station has bumped its items.
kitchen-expo-consolidation
CLAIM: an expo screen consolidates items from multiple prep stations into one order view and only marks the order complete when every contributing station has bumped. VERDICT: yes/B. NEW SURFACE: the Restroworks KDS web app at https://kitchen.restroworks.com/ (Angular, HTML 200, never cited before; /robots.txt returns the SPA shell, so no bar and no ClaudeBot naming). Its JS is served anonymously: the HTML lists 26 chunks and following every static chunk-*.js reference reaches a fixpoint of 54 files (2.7 MB). Live orders need a login; none was used. EVIDENCE (user-visible strings in the bundle): a screen selects stations ('All Stations' label; saveStations stores every selected station, so one screen can show several stations) and a flow stage ('Select Stage for this screen.'); items map to per-item flows of stages ('show_unprepared_items': 'Show KOTs with unprepared items in the kitchen. Works only with stages & flows.'; 'auto_refresh_item_flow_mapping': 'Fetches the latest item flow mapping from the server every minute'). The completion gate: marking a KOT done on a stage screen walks every item and combo sub-item and, if any item's flow has not reached its final stage, refuses with 'All items are not bumped from all stages yet' (chunk-P5S4B57C.js). The default can be overridden by 'mark_done_from_last_stage': 'Mark a kot done from last stage of flows irrespective of previous stage bumps.' A pickup screen (/pickup route, 'pickupScreen' deployment setting) also exists. The 48-entry KDS settings enumeration is saved at .cache/q317/restroworks/kds-settings.txt. CAVEATS: the words expo/expeditor do not appear (tokenised 'expo' hits are only export/exponent poison); consolidation is by station+stage configuration and the gate is read from minified code, so a reviewer may prefer partial. Retrieved 2026-09-16. https://kitchen.restroworks.com/ · retrieved 2026-09-16 adversarially verified
Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator
kitchen-course-firing
Not scored by this record.
Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator
kitchen-prep-time-pacing
Not scored by this record.
Kitchen load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator
kitchen-order-throttling
Not scored by this record.
Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator
kitchen-channel-pause-propagation
Not scored by this record.
Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator
kitchen-order-ready-callback
Not scored by this record.
KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.
kitchen-bump-bar-hardware
The 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
An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.
kitchen-all-day-counts
Not scored by this record.
Configurable target cook times per station or order type, with visual color escalation and/or audible alert when a ticket exceeds target.
kitchen-sla-alerts
Not scored by this record.
If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator
kitchen-printer-fallback
Not scored by this record.
KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator
kitchen-offline-operation
Not scored by this record.
Station screens can display item-level build/assembly detail (recipe steps, portioning, or full modifier breakout) rather than only the ticket line text. differentiator
kitchen-item-build-screens
Not scored by this record.
Sectioned/fractional topping placement (halves, quarters, specific sections) is rendered visually and unambiguously on the make-line screen or ticket. differentiator
kitchen-pizza-fractional-display
Not scored by this record.
A bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order.
kitchen-recall-refire
Not scored by this record.
Edits made in the POS to an order already displayed in the kitchen visually flag the added, changed, or removed items on the live ticket. differentiator
kitchen-order-modification-alerts
Not scored by this record.
Bumping an order ready triggers a guest-facing notification — SMS/text, app push, or an order-status display board — without a separate product purchase. differentiator
kitchen-guest-ready-notification
Not scored by this record.
Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.
kitchen-waste-logging
Not scored by this record.
Reports actual ticket and per-station times (average and percentile) sliced by daypart, station, and order channel, exportable to CSV or an API.
kitchen-speed-of-service-reporting
Not scored by this record.
Generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list.
kitchen-prep-forecasting
Not scored by this record.
Delivery, dispatch & third-party channels
Product includes a native in-house driver module: drivers are first-class entities with clock-in/out, assignment state (in-store / on-run / returning), and per-driver run history reportable from the POS itself (not via a third-party add-on).
delivery-driver-roster
CLAIM: native driver module; drivers are entities with clock-in/out, assignment state and per-driver run history reportable in the POS. VERDICT: partial/D (graded down because the strongest quote is a retired marketing page whose public URL now redirects). EVIDENCE: Posist WP REST https://www.posist.com/wp-json/wp/v2/pages/7732 (biryani-shop-software, status publish, modified 2025-02-24, public URL 301s to restroworks.com/fast-casual-pos/): 'Delivery Module View the checked-in status of the Delivery Boys and assign orders to them based on their availability. Track the real-time location of the Delivery Boys through GPS tracking'. Live https://www.posist.com/restaurant-pos-system/ (200): 'Track the delivery status in real-time and the performance of your delivery staff'. https://www.restroworks.com/restroapp-food-delivery-app/ (200): 'Delivery riders are assigned automatically ... Seamless delivery rider assignment'. api.restroworks.com Delivery folder: 'Assign Delivery Person'. SHORTFALL: check-in status and availability-based assignment are named. The on-run/returning state model and a per-driver run-history report are not. Retrieved 2026-09-16. https://www.posist.com/wp-json/wp/v2/pages/7732 · retrieved 2026-09-16 adversarially verified
Provides a dedicated dispatch/expo screen showing undispatched orders, driver availability, and elapsed time per order, with multi-order run batching (assigning 2+ orders to one driver as a single run).
delivery-dispatch-board
The Delivery 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
Dispatch includes a live map view with geocoded stops and system-generated route sequencing (turn order optimization) for a multi-stop run, not just a static address list. differentiator
delivery-route-map
Not scored by this record.
Captures live driver GPS position from a driver-facing mobile app and surfaces it back to the dispatch screen. differentiator
delivery-driver-tracking
Not scored by this record.
Delivery areas can be defined as arbitrary map polygons or by drive-time isochrones, not solely as a radius or a ZIP/postcode list. differentiator
delivery-zones-polygon
Not scored by this record.
Each delivery zone carries its own independently configurable delivery fee, order minimum, and quoted promise time, applied automatically from the validated customer address.
delivery-zone-pricing
329th: NEW SURFACE + CENSUS THAT CLOSES THIS. (a) The complete SETTINGS ENUMERATION of the store-level POS/admin web client was extracted from the production bundle https://posist.biz/app/99687fd3.app.js (37,787,481 bytes, re-fetched 2026-09-18, byte-identical to the 322nd's copy, still the build posist.biz/index references): 2,736 labelled setting objects in 127 named groups. The client has NO lazy-chunk loader (ocLazyLoad / require.ensure / __webpack_require__ / System.import / webpackChunkName = 0 hits; index.html has 16 script tags = app.js + vendor.js + bower libs), so this bundle IS the whole web client and the group list IS a closed enumeration. (b) The ENTIRE online-ordering settings surface is 8 settings: group 'Online Order Settings' = {label:"Minimum Order on Delivery",name:"minimum_order_delivery"}, {label:"Time To Deliver(in mins)",name:"time_to_deliver",fieldType:"text",value:"30"}, Auto Reject Time, Enable Delivery Boy App, Allow More than 10 Digit Mobile Numbers, Allow International SMS, Set Online Order By Super Category, Use Categories as Supercategories On Aggregators; group 'Online Order' = 4 (Online Order Config [oo_config], Online Order Sync, Online Order Tab Mapping, Test Order Pushing); group 'Delivery Partner' = 9, of which the only geography is a single latitude/longitude pair (the rest are Delhivery/RoadRunnr/Grab credentials); group 'Delivery App' = 2 (Zomato Trace credentials). POSITIVE EVIDENCE OF ABSENCE, not mere silence: the delivery minimum and the quoted promise time are SINGLE SCALAR deployment values, and the promise time is read globally with a hard-coded fallback - 'var t=j.getSettingValue("time_to_deliver",b.settings);a.bill.delivery_time=t||50' (three call sites) - so one promise time serves every address. oo_config is only a permission flag on an 'Online Order Configuration' panel whose buttons are configureCCAvenue() / configureMobile() (payment gateways), not zones. (c) A SECOND, PREVIOUSLY UNKNOWN APP was censused and has no delivery surface at all: neo.posist.co ('Neo', Vite SPA, /assets/index--SwiVT8H.js, 921,037 bytes on the wire / 3,414,432 chars, anonymous; nonsense control /assets/index--ZZNONSENSE.js returns the 290-byte SPA shell, so the 200 is real). Its 77 declared routes are brand/outlet/menu distribution (/menu-management/:menuId/circuits, /overrides, /locations, /stores, /activity/publish/:publishId, /settings/cross-location, /admin/audit-logs); tokenised counts in it: delivery* 0, dispatch* 0, fee* 0, charge* 0, serviceab* 0, deliveryZone/delivery_zone/'delivery zone'/geofence 0. CONTROLS (tokenised, case-insensitive, over the 37.8 MB POS bundle): deliveryZone, delivery_zone, 'Delivery Zone', 'Delivery Area', polygon, geofence = 0. POISON NAMED: 'radius' = 1,015 hits, almost all CSS border-radius; 'zone' is timezone/Zone.js. BOUND: this bounds the Restroworks POS web client and the Neo channel-menu app; the aggregators' own zone tables (Zomato/Swiggy/Uber) are those partners' products, not Restroworks'. Retrieved 2026-09-18. https://posist.biz/app/99687fd3.app.js · retrieved 2026-09-18 adversarially verified
Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.
delivery-address-validation
Not scored by this record.
Tracks per-delivery driver compensation inputs — mileage or distance driven per run, per-delivery flat reimbursement, and driver-retained tips — and exports them to payroll as separate reimbursement vs. wage lines. differentiator
delivery-driver-comp
Not scored by this record.
Provides a driver cash bank / settle-up flow that reconciles cash collected, orders assigned, and tips owed at end of shift, producing a per-driver over/short figure.
delivery-cash-reconcile
Not scored by this record.
Can hand a first-party order to an on-demand courier marketplace (DoorDash Drive, Uber Direct, Nash, Relay or equivalent) natively from the POS, with the courier quote and status returning into the order record.
delivery-daas-dispatch
Not scored by this record.
Supports hybrid dispatch: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. differentiator
delivery-daas-fallback
Not scored by this record.
Offers direct, first-party certified API integrations with DoorDash, Uber Eats, and Grubhub marketplaces (vendor-owned, not solely resold through Otter/Deliverect/Chowly/ItsaCheckmate middleware). differentiator
delivery-3p-direct-integration
Not scored by this record.
Third-party marketplace orders inject automatically into the POS as normal tickets that fire to KDS/printers without tablet re-keying or manual accept.
delivery-3p-injection
Not scored by this record.
Marking an item or modifier 86'd in the POS pushes item-level out-of-stock status to connected third-party channels in near real time, and restores it on availability (DoorDash requires item and item-option 86ing of new POS partners).
delivery-86-sync
Not scored by this record.
Store can be paused/deactivated on each connected third-party marketplace from inside the POS with a timed auto-reactivation, rather than only from each marketplace's own tablet or portal.
delivery-store-pause
Not scored by this record.
Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. differentiator
delivery-3p-reconciliation
Not scored by this record.
Vendor exposes integration health to the operator — failed/rejected order injections, connection status per channel, and alerts on failure — rather than failing silently. differentiator
delivery-injection-error-visibility
Not scored by this record.
Guests receive a branded order status / driver tracking page or SMS link on the restaurant's own domain for first-party delivery orders, driven by real order and driver state.
delivery-tracking-page
Not scored by this record.
Quoted delivery promise times adjust dynamically from current kitchen load, driver availability, and zone drive time, rather than a fixed per-store constant. differentiator
delivery-promise-time
Not scored by this record.
Vendor documents explicit offline behavior for delivery: whether cash delivery orders, driver assignment, and driver settlement continue during an internet outage.
delivery-offline-behavior
Not scored by this record.
Digital ordering & guest-facing channels
Vendor ships a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission.
digital-first-party-web
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
Vendor offers a branded native iOS and Android ordering app (published under the restaurant's own brand in the App Store/Play Store), not only a mobile web page or a shared multi-restaurant marketplace app. differentiator
digital-native-app
Not scored by this record.
Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels.
digital-account-saved-payment
CLAIM: guest account with saved addresses, saved tokenized payment methods, and one-tap reorder of a previous order. VERDICT: partial/B (2 of 3 conjuncts). NEW SURFACE: the 'Restroworks Web' guest ordering app at https://qr4events.restroworks.com/ (Vite/React, bundle /assets/index-875Hbdgb.js, 2.2 MB, served anonymously; /robots.txt is the SPA shell). EVIDENCE: in-app FAQ: 'Can I use the app without creating an account?' -> 'Yes, you can browse the menu as a guest. However, to place orders, save addresses, and access order history, you'll need to sign in with your phone number.'; 'Can I reorder a previous order?' -> 'Yes! Visit your Order History in the Profile section, find a past order, and you can quickly reorder the same items.'; UI strings 'Saved Addresses', 'No saved addresses found', a 'Reorder' button on past orders, 'Order Again'. SHORTFALL: no saved/tokenized payment method. Controls over the bundle (case-insensitive): 'saved card', 'save card', 'saveCard', 'saved payment', 'savedPayment', 'tokeni', 'Saved Cards' = 0 hits; the FAQ says only 'Payment details are processed through secure payment gateways', and checkout is Razorpay. Not a no for that conjunct: the gateway's hosted checkout could remember cards outside this bundle. Retrieved 2026-09-16. https://qr4events.restroworks.com/ · retrieved 2026-09-16 adversarially verified
Digital checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator
digital-upsell-engine
Not scored by this record.
Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.
digital-scheduled-pacing
Not scored by this record.
Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.
digital-fulfillment-modes
Not scored by this record.
Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.
digital-qr-table
Not scored by this record.
Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator
digital-kiosk
Not scored by this record.
Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.
digital-group-ordering
Not scored by this record.
Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator
digital-catering-portal
Not scored by this record.
Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator
digital-voice-ai-phone
Not scored by this record.
Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.
digital-drivethru-ai
Not scored by this record.
Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.
digital-sms-ordering
Not scored by this record.
Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator
digital-google-order
Not scored by this record.
Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.
digital-apple-business-connect
Not scored by this record.
Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.
digital-loyalty-attach
Not scored by this record.
Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.
digital-subscriptions
Not scored by this record.
Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.
digital-promo-parity
Not scored by this record.
Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator
digital-guest-data-ownership
Not scored by this record.
Digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.
digital-checkout-pci-sca
Not scored by this record.
Digital channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator
digital-surcharge-transparency
Not scored by this record.
Guest data, loyalty & marketing
Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.
guest-loyalty-unified-profile
CLAIM: one guest profile auto-merging in-store POS, first-party web/app and kiosk transactions under one identity, with documented dedup/merge. VERDICT: partial/C. NEW: the CRM product page (restaurant-crm-software) was missing from the earlier read. EVIDENCE: https://www.restroworks.com/restaurant-crm-software/ (HTTP 200), 'Centralized Guest Database': 'Unify customer information from every touchpoint to understand your guests better. Capture guest data automatically from POS, online ordering, and reservations. Maintain a single customer profile across all outlets and channels. Track visit frequency, preferences, and spending patterns in one dashboard'. Legacy https://www.posist.com/wp-json/wp/v2/pages (biryani-shop-software, id 7732): 'CRM Integration Automatically update customer data from multiple sources into the central CRM'. SHORTFALL: kiosk is not named as a source, the identity key (phone/email) is not stated, and no dedup or merge behaviour is documented. Retrieved 2026-09-16. https://www.restroworks.com/restaurant-crm-software/ · retrieved 2026-09-16 adversarially verified
Orders arriving from third-party marketplaces (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. differentiator
guest-loyalty-thirdparty-identity-attach
Not scored by this record.
Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.
guest-loyalty-accrual-models
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
Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator
guest-loyalty-tiers
Not scored by this record.
Documents explicitly what loyalty lookup, accrual, and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). differentiator
guest-loyalty-offline-behavior
Not scored by this record.
Offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. differentiator
guest-loyalty-offer-stacking-rules
Not scored by this record.
Offers can be issued to a dynamically defined audience (rules over recency, frequency, spend, or items purchased) rather than only broadcast to the whole list. differentiator
guest-loyalty-targeted-offers
Not scored by this record.
Automatically computes recency/frequency/monetary or equivalent lifecycle segments (new, regular, at-risk, lapsed, VIP) without the operator building the queries. differentiator
guest-loyalty-rfm-segmentation
Not scored by this record.
Ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns rather than one-off manual sends.
guest-loyalty-lifecycle-automation
The 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
Sends both email and SMS campaigns natively from the platform, not solely by handing the list to a third-party ESP. differentiator
guest-loyalty-native-email-sms
Not scored by this record.
Captures per-channel marketing consent with timestamp and source of consent, and honors revocation received by any reasonable means (not just the STOP keyword) across all channels.
guest-loyalty-consent-management
Not scored by this record.
Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.
guest-loyalty-10dlc-registration
Not scored by this record.
Reports redemption and incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. differentiator
guest-loyalty-campaign-attribution
Not scored by this record.
Provides self-serve export of the full guest list and transaction history, including contact PII, via CSV or API, without a vendor fee or support ticket. differentiator
guest-loyalty-data-export-portability
Not scored by this record.
Exposes a documented outbound guest and order event API or webhook stream that a CDP or marketing platform can subscribe to (e.g. Olo, Punchh, Bridg, Klaviyo). differentiator
guest-loyalty-cdp-event-api
Not scored by this record.
Triggers post-transaction feedback requests and routes responses by score, sending low scores to private service recovery and high scores toward public review sites. differentiator
guest-loyalty-review-capture-routing
Not scored by this record.
Includes a native referral mechanic with per-guest codes or links, attribution of the referred guest's first order, and two-sided rewards.
guest-loyalty-referral-program
Not scored by this record.
Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance, as an alternative to requiring a branded app download. differentiator
guest-loyalty-wallet-pass
Not scored by this record.
Provides admin tooling to fulfill guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records.
guest-loyalty-privacy-rights-tooling
Not scored by this record.
Enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log.
guest-loyalty-redemption-fraud-controls
Not scored by this record.
Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing (claim-level; verify it is a shipped product feature, not a roadmap statement). differentiator
guest-loyalty-ai-offer-recommendation
Not scored by this record.
Offers native stored-value/gift card balances tied to the same guest profile and redeemable across all locations of the brand.
guest-loyalty-stored-value-gift
Not scored by this record.
Labor & workforce
Employees clock in and out at the POS terminal using a PIN, badge, or card, with no separate time-clock hardware required.
labor-clock-in-at-pos
The 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
Captures a photo at punch (or performs facial verification) attached to the timecard entry, with a photo-only mode available that stores no biometric template. differentiator
labor-photo-punch-verification
Not scored by this record.
Supports mobile clock-in restricted by geofence or location validation for staff who do not punch at a fixed terminal.
labor-geofenced-mobile-punch
Not scored by this record.
Records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, with the behavior documented. differentiator
labor-offline-time-punch
Not scored by this record.
Permissions are grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers.
labor-granular-rbac
CLAIM: permissions grantable per discrete action per role per location, beyond fixed tiers. VERDICT: partial/C. EVIDENCE: https://www.restroworks.com/security-compliance/ (HTTP 200): 'Role-Based Access Control: Our platform offers role-based access control, allowing easy management of user permissions'. https://www.restroworks.com/large-chain-restaurant-software/: 'Role-based access controls ensure operational efficiency, accountability, and enterprise-grade security'. Legacy Posist WP REST (www.posist.com/wp-json/wp/v2/pages/8869, restaurant-cockpit-app, public URL 301s to restroworks.com): 'Set roles and permissions for each task and get instant notifications'. Posist blog post 665 (/restaurant-times/posist-product/need-know-inventory-management-restaurants.html, 2015, now 301): 'Posist's roles and permissions feature. With this, you can create specific roles for each task ... All activities are logged'. The restroworks.com DoorDash help page (/doordash-help-center/): 'Only users with proper permissions can void orders'. SHORTFALL: custom roles and a per-task grant are asserted, but the discrete action list (void, comp, discount, refund, drawer, price change, report access) and per-location scoping are not published. The admin guide is gated (GitBook + Auth0). Retrieved 2026-09-16. https://www.restroworks.com/security-compliance/ · retrieved 2026-09-16 adversarially verified
Manager overrides and approvals are attributed to the individual approver and written to an immutable audit trail queryable after the fact.
labor-manager-override-audit
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
Builds and publishes employee shift schedules inside the same platform that holds the timekeeping data, rather than requiring a third-party scheduling app. differentiator
labor-native-scheduling
Not scored by this record.
Generates recommended staffing levels or labor hours by daypart from the operator's own POS sales history, not just a static template. differentiator
labor-demand-labor-forecast
Not scored by this record.
Displays labor cost as a percentage of sales in real time during service on a manager view or POS, not only in end-of-day or next-morning reports. differentiator
labor-realtime-labor-percent
Not scored by this record.
Warns or blocks at clock-in when an employee is approaching or would cross a configured overtime threshold, before the overtime is incurred. differentiator
labor-overtime-prevention
Not scored by this record.
Configures meal and rest break rules per state or jurisdiction, prompts required break attestation, and flags missed breaks for premium pay. differentiator
labor-break-compliance-by-state
Not scored by this record.
Supports predictive-scheduling ordinances by tracking advance-notice deadlines for published schedules and calculating predictability pay owed for employer-initiated changes.
labor-fair-workweek-support
Not scored by this record.
Enforces minor-labor restrictions (age-based maximum hours, prohibited time windows, school-day limits) at both scheduling and clock-in.
labor-minor-labor-rules
Not scored by this record.
Computes tip pooling and tip-outs automatically per shift from configurable rules (percentage of sales, hours worked, points, or role), rather than requiring a manual spreadsheet.
labor-tip-pooling-rules
Not scored by this record.
Retains a per-shift, per-employee record of tips received, amounts contributed to the pool, and amounts distributed from the pool, exportable for audit.
labor-tip-distribution-audit-trail
Not scored by this record.
Payroll export separates cash from charged qualified tips and carries a Treasury tipped-occupation code, supporting the W-2 Box 12 code TP and Box 14b reporting required for tax year 2026. differentiator
labor-qualified-tips-w2-reporting
Not scored by this record.
Vendor processes payroll itself as a first-party product (tax filing and direct deposit), as opposed to exporting to a third-party payroll provider only. differentiator
labor-native-payroll
Not scored by this record.
Exports timecards, wages, and tips in documented formats or via direct integration for at least two major payroll providers (e.g. Gusto, ADP, Paychex, QuickBooks).
labor-payroll-export-formats
Not scored by this record.
Employees can request shift swaps or claim open shifts in a self-service app, subject to a manager approval workflow that enforces overtime and role eligibility. differentiator
labor-shift-swap-workflow
Not scored by this record.
Provides digital new-hire onboarding that collects W-4 and I-9 documentation and supports E-Verify submission.
labor-digital-onboarding-i9
Not scored by this record.
Reports per-employee sales performance metrics (average check, items or category attachment rate, void and comp rate) by server or cashier. differentiator
labor-server-performance-metrics
Not scored by this record.
Inventory, purchasing & cost control
Supports multi-level recipe/BOM costing where a recipe can contain sub-recipes (prep items) and plate cost recalculates automatically when any component ingredient's cost changes.
inventory-recipe-bom-costing
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
Stores purchase unit, recipe unit, and count unit per item with explicit conversion factors, plus a yield/waste percentage applied to raw-to-usable conversion.
inventory-unit-conversion-yields
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
Produces a theoretical-vs-actual usage variance report per item for a defined count period, showing theoretical usage from POS sales times recipe, actual usage from counts plus receipts, and the variance in both units and currency. differentiator
inventory-theoretical-vs-actual
Not scored by this record.
Depletes ingredient on-hand quantities in near real time as orders are fired at the POS, including depletion driven by modifier selections, not only in an end-of-day batch. differentiator
inventory-realtime-depletion
Not scored by this record.
Automatically 86s (marks unavailable) menu items on the POS, online ordering, and connected third-party delivery menus when a component ingredient hits zero or a configured threshold. differentiator
inventory-86-auto-sync
Not scored by this record.
Supports full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts.
inventory-count-modes
The 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
Provides a mobile/tablet counting app supporting barcode or QR scanning that continues to accept counts with no network connectivity and syncs on reconnect.
inventory-mobile-count-offline
Not scored by this record.
Ships pre-built electronic vendor catalog and order-transmission integrations with named broadline distributors (e.g. Sysco, US Foods, Performance Food Group) that send purchase orders and receive invoices electronically rather than by emailed PDF. differentiator
inventory-vendor-catalogs-edi
Not scored by this record.
Ingests supplier invoices from photo, PDF, or email and extracts line-item detail (item, quantity, unit, price) into the inventory ledger without manual line entry. differentiator
inventory-invoice-ocr
Not scored by this record.
Tracks per-item purchase price history across invoices and alerts when a received price exceeds the prior or contracted price by a configurable threshold. differentiator
inventory-price-change-alerts
Not scored by this record.
Maintains par levels per item per location and generates suggested purchase order quantities from on-hand versus par, with at least one mode driven by a sales forecast rather than a static par. differentiator
inventory-par-auto-suggest
Not scored by this record.
Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.
inventory-waste-logging
Not scored by this record.
Supports inter-location inventory transfers as a two-sided transaction crediting the sending location and debiting the receiving location, with an in-transit or approval state.
inventory-transfers
Not scored by this record.
Supports a commissary/central kitchen model where one location produces prep items and issues or sells them to other locations at a computed transfer cost.
inventory-commissary
Not scored by this record.
Captures lot/batch numbers at receiving and links them through production to sales or transfers, enabling a backward and forward recall trace.
inventory-lot-traceability
Not scored by this record.
Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.
inventory-shelf-life-expiry
Not scored by this record.
Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting.
inventory-bar-partial-bottle
Not scored by this record.
Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.
inventory-cogs-gl-export
Not scored by this record.
Inventory and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator
inventory-native-not-partner
Not scored by this record.
Reporting, BI & data access
Provides a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise.
reporting-realtime-dashboard
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
Generates a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types, and expected cash deposit in one document.
reporting-eod-closeout
CLAIM: a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types and expected cash deposit in one document. VERDICT: partial/B. NEW SURFACE: https://posist.biz/ (<title>Posist</title>). This is the production Restroworks (ex-Posist) POS/back-office web client. Its HTML loads restroworks-stock-report-bucket.s3 and tickets.posist.co widgets, and the host was found through posist.biz's socket.io source map. The login page loads the AngularJS bundle https://posist.biz/app/99687fd3.app.js anonymously: 37.8 MB, concatenated, with templates inlined through $templateCache. It is the vendor's shipped code, so grade B. It has no source map (.map returns the SPA shell). A second copy, apptest.posist.co, is a TEST host that serves the same app unminified as 1,521 files (70 MB). It was used only to locate code, and every quote below is from the production bundle. EVIDENCE: a setting '{label:"Enable Printing Day end Slip",name:"enable_day_end_slip",group:"Billing Other Settings"}'. The POS menu item "Print Day end slip" asks "Do you want to print Day end Receipt for the complete Outlet or this this terminal only ?". The slip builder's section headers: "Sales Summary By Tab", "SALES", "SESSIONS", "Day End Cash Denominations", "Collection Breakup", "Debit Card Breakup", "Credit Card Breakup", "Tip Collection Breakup", "Complementary Sales", "Discount Details". Its lines: "Subtotal", "Discount", 'O.setString("Net Sales",17)+":"+O.setAmount((h.subtotal-h.discount)...', per-tax totals ('h.taxes[b.name]+=Number(b.tax_amount)'), "Round Off", "Total Amount", "Tip Amount", "Cancel Bills", "Cancel Amount", then 'O.setString("Total Cash:",15)...e.closeDeposit&&(p+=O.setString("Bank Deposit:",15)...'. So gross/subtotal, net, tax, tips, discounts, tender breakdown and cash/bank deposit do sit in one day-end document. The separate shift Z-report (settings z_report_shift, permission generate_z_report) prints "Sales", "Total Discount", "Net Sales", "Total Tax", "Gross Sales", "Voided Amount", a PAYMENT COLLECTION table, "Cash Refund", "Expected Closing Cash", "Closing Cash" and "Variance Amount". SHORTFALL: the day-end slip has no refund line ('refund' = 0 hits in the 33 KB of code around the slip builder; only voids and cancellations appear), and its "Bank Deposit" is the entered close deposit, not a computed expected deposit. Refunds and expected cash appear only on the per-shift report. So one daily document does not carry every conjunct. Retrieved 2026-09-17. https://posist.biz/app/99687fd3.app.js · retrieved 2026-09-17 adversarially verified
Provides a product mix (PMIX) report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center.
reporting-pmix-modifier-level
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
Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.
reporting-comps-voids-audit
Not scored by this record.
Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.
reporting-cash-over-short
Not scored by this record.
Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.
reporting-labor-productivity
Not scored by this record.
Reports per-server metrics including average check, items per check, attachment rate for named categories, and tips as a percentage of sales. differentiator
reporting-server-scorecards
Not scored by this record.
Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator
reporting-channel-profitability
Not scored by this record.
Provides a consolidated multi-location report with side-by-side location comparison and drill-down from group total to a single location and then to an individual transaction. differentiator
reporting-multiloc-drilldown
Not scored by this record.
Includes a self-service report builder letting a non-developer choose dimensions, measures, and filters and save the result, rather than only fixed canned reports. differentiator
reporting-custom-report-builder
Not scored by this record.
Supports scheduling any report for automatic recurring delivery by email or to a shared destination on a defined cadence and recipient list.
reporting-scheduled-delivery
Not scored by this record.
Offers automated recurring bulk export of transaction-level raw data to a customer-controlled destination (S3, SFTP, Snowflake, BigQuery, or equivalent), not just manual CSV download. differentiator
reporting-raw-warehouse-export
Not scored by this record.
Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator
reporting-public-api
Not scored by this record.
Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator
reporting-webhooks
Not scored by this record.
API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator
reporting-api-not-upcharged
Not scored by this record.
Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator
reporting-tier-paywall
Not scored by this record.
Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator
reporting-history-retention
Not scored by this record.
Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator
reporting-anomaly-alerts
Not scored by this record.
Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.
reporting-nl-query
Not scored by this record.
Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator
reporting-guest-cohorts
Not scored by this record.
Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator
reporting-sales-forecast
Not scored by this record.
Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.
reporting-tip-tax-compliance
Not scored by this record.
Multi-location, franchise & enterprise governance
Supports a named organizational hierarchy of at least three levels (e.g. enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations.
multi-location-org-hierarchy
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
Corporate menu items expose per-field override rules so a location can change some attributes (e.g. price, availability) while corporate locks others (e.g. name, image, recipe), and locked fields are not editable at store level. differentiator
multi-location-local-override-policy
Not scored by this record.
Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.
multi-location-price-zones
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
Menu, price, and promo changes can be scheduled to activate at a future date/time interpreted in each target location's own timezone, and can be rolled back after activation. differentiator
multi-location-scheduled-publish
Not scored by this record.
A new location can be provisioned by cloning a documented configuration template (menu, taxes, roles, printers, modifiers, tenders) rather than being configured from scratch, and the vendor publishes the expected time-to-open. differentiator
multi-location-new-store-template
Not scored by this record.
The permission model distinguishes a franchisor/corporate tenant from an independently-owned franchisee tenant, so corporate can see franchisee sales and enforce config while the franchisee owns its own employees, banking, and labor data. differentiator
multi-location-corp-vs-franchisee-roles
Not scored by this record.
Calculates franchise royalty, ad-fund, and marketing-fee amounts automatically from POS net sales on a defined schedule, with a configurable royalty basis (gross vs net of discounts/comps/third-party). differentiator
multi-location-royalty-calculation
Not scored by this record.
Supports automated ACH/debit collection of calculated royalties and fees from franchisee accounts, with a franchisee-visible statement of what was charged.
multi-location-royalty-collection
Not scored by this record.
Provides above-store reporting that aggregates sales, labor, discounts, voids, and item mix across any selected set of locations in one view, with store-vs-store ranking and variance flags.
multi-location-consolidated-reporting
Not scored by this record.
Item-level sales roll up across locations under a shared corporate item ID even when stores have renamed or locally priced the item. differentiator
multi-location-normalized-item-rollup
Not scored by this record.
Gift cards issued at one location are redeemable at any other location in the brand, with a reported outstanding-liability balance and inter-store settlement/redemption reconciliation between owners.
multi-location-cross-location-giftcard
Not scored by this record.
A single customer loyalty profile, balance, and stored order history is shared across all locations in the brand rather than being per-location.
multi-location-cross-location-loyalty
Not scored by this record.
A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. differentiator
multi-location-multi-brand
Not scored by this record.
Tax configuration is per-location with support for multiple simultaneous tax rates, jurisdiction-specific rules (e.g. prepared-food vs grocery, inclusive vs exclusive tax), and per-location tax exemptions.
multi-location-multi-tax-jurisdiction
Not scored by this record.
Produces an immutable audit log of who changed which configuration object (price, tax, permission, discount) at which location and when, exportable or queryable by corporate. differentiator
multi-location-config-audit-log
Not scored by this record.
Publishes a documented multi-location API (or data warehouse/BI export) that returns transaction-level data across all locations in one authenticated call, without per-location credentials. differentiator
multi-location-enterprise-api
Not scored by this record.
Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.
multi-location-central-labor-policy
Not scored by this record.
Hardware & physical footprint
The POS software runs on commodity off-the-shelf hardware (standard iPads, Android tablets, or PCs) that the operator can buy from a third party, rather than only on vendor-supplied proprietary terminals. differentiator
hardware-commodity-devices
Not scored by this record.
Vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs.
hardware-os-platforms
CLAIM: documentation names the supported client OSes and states minimum OS versions and device specs. VERDICT: partial/D. EVIDENCE: https://www.restroworks.com/compare/restroworks-vs-lightspeed/ (200): 'Restroworks offers greater flexibility in deployment options, supporting web app, Windows, and mobile platforms'. https://www.restroworks.com/compare/restroworks-vs-toast-pos/for-bakeries/ (200): 'Restroworks supports Android tablets, iOS devices, and standard POS terminals'. The /compare/par-pos-vs-revel-systems/ family: 'runs on your existing devices like POS terminals, tablets (iOS/Android), printers, KDS, and cash drawers'. The App Store lookup API (itunes.apple.com/lookup?id=1459641305) lists the seller's Posist-Lite server app (POSist Technologies Private Limited, v2.195.0, 2026-09-09) with minimumOsVersion 15.0. That is store metadata, not vendor documentation. SHORTFALL: no vendor page gives minimum iOS/Android/Windows versions or device specs. The admin guide (docs.restroworks.com) is gated behind GitBook VA-Auth0 visitor auth. Retrieved 2026-09-16. https://www.restroworks.com/compare/restroworks-vs-lightspeed/ · retrieved 2026-09-16 adversarially verified
Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.
hardware-handheld-purpose-built
Not scored by this record.
The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator
hardware-handheld-battery-swap
Not scored by this record.
Handhelds support cellular/LTE connectivity as a documented fallback when store Wi-Fi drops, either built into the device or via a vendor-supplied failover.
hardware-handheld-lte
Not scored by this record.
Terminals continue to take orders, print to kitchen, and record cash sales with the internet down, and the vendor documents explicitly which functions degrade (card auth, loyalty lookup, refunds).
hardware-offline-mode
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
Sells or supports a dedicated kitchen display system with bump-bar or touch input, station routing, and course/fire timing, as a first-party product rather than an integration-only dependency.
hardware-kds
Kitchen Display System is a first-party module within the Kitchen Suite, not an integration dependency. https://www.restroworks.com/ · retrieved 2026-08-01
Offers a self-order kiosk running the same menu and modifier engine as the POS, in both countertop and freestanding form factors, with integrated payment and accessibility (ADA) compliance documented. differentiator
hardware-kiosk
Not scored by this record.
Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, and speaker/headset integration, with a documented timer/speed-of-service measurement.
hardware-drive-thru
Not scored by this record.
Works with standard ESC/POS thermal receipt and kitchen printers from more than one manufacturer (e.g. Epson and Star), including LAN/Ethernet printers, rather than only vendor-branded printers.
hardware-printer-compatibility
Not scored by this record.
Supports the standard peripheral set — cash drawers (including multi-drawer per terminal), barcode scanners, scales for by-weight items, and customer-facing displays — with a published compatibility list.
hardware-peripherals
Not scored by this record.
Card entry happens on a PCI-listed PTS device using validated point-to-point encryption, so the POS application and tablet stay out of PCI scope; the vendor states the merchant's SAQ type.
hardware-p2pe-terminal
Not scored by this record.
Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. differentiator
hardware-tap-to-phone
Not scored by this record.
Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator
hardware-pricing-transparency
Not scored by this record.
Hardware can be purchased outright (owned) as an alternative to a mandatory lease or subscription-bundled rental, and the vendor states which. differentiator
hardware-ownership-vs-lease
Not scored by this record.
Vendor documentation confirms whether hardware purchased from the vendor remains usable with other software after cancellation, i.e. it is not software-locked or remotely bricked. differentiator
hardware-usable-after-churn
Not scored by this record.
Publishes a hardware warranty term and a replacement/advance-exchange SLA with a stated turnaround (e.g. next-business-day depot swap). differentiator
hardware-rma-sla
Not scored by this record.
Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.
hardware-byod
Not scored by this record.
Provides a remote device-management console showing each terminal, printer, and KDS as online/offline, with remote reboot, software-version visibility, and staged rollout of updates. differentiator
hardware-remote-device-management
Not scored by this record.
Integrates with specialty beverage hardware — self-pour tap walls, flow meters, or liquor pour spouts — such that pours post to a POS tab automatically.
hardware-selfpour-scales
Not scored by this record.
Supports inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call.
hardware-callerid-integration
Not scored by this record.
Integrations, API & extensibility
Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.
extensibility-public-api-docs
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
API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator
extensibility-api-access-cost
Not scored by this record.
A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator
extensibility-free-sandbox
Not scored by this record.
Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).
extensibility-oauth-partner-apps
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
The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.
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
Webhooks are cryptographically signed (e.g. HMAC) AND documented to retry with backoff, with a replayable event log for missed deliveries. differentiator
extensibility-webhook-reliability
Not scored by this record.
A public write API accepts externally originated orders into the POS as first-class tickets that fire to KDS/printers and land in reporting.
extensibility-order-injection-api
Not scored by this record.
Every core object the API can read (orders, menu, customers, employees, inventory) can also be written or updated via the same API. differentiator
extensibility-data-symmetry
Not scored by this record.
API rate limits are published as specific numeric quotas with documented throttling behavior and headers.
extensibility-published-rate-limits
Not scored by this record.
The vendor is a named DoorDash Preferred Integration Partner (DPIP) under the 2026 program requirements. differentiator
extensibility-doordash-preferred
Not scored by this record.
Direct, first-party certified integrations exist with DoorDash, Uber Eats, and Grubhub without requiring a paid middleware layer (Otter/Chowly/Deliverect/Checkmate). differentiator
extensibility-first-party-delivery-integrations
Not scored by this record.
The POS is a supported endpoint for at least two major aggregation middleware platforms (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate).
extensibility-middleware-compatibility
Not scored by this record.
Native, vendor-maintained connectors exist for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export.
extensibility-accounting-connectors
Not scored by this record.
Labor hours export natively to at least two named payroll providers (e.g. Gusto, ADP, Paychex, Paylocity) without manual re-keying.
extensibility-payroll-export
Not scored by this record.
Raw transaction-level data can be exported on a schedule to a customer-controlled destination (S3/SFTP/warehouse/Snowflake share), not only viewed in the vendor's reporting UI. differentiator
extensibility-bi-data-warehouse
Not scored by this record.
The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.
extensibility-app-marketplace
Not scored by this record.
Operators can define custom fields or run vendor-hosted custom logic/scripts against POS objects without a vendor engineering engagement.
extensibility-custom-fields-scripting
Not scored by this record.
The vendor supports a headless/embedded mode where a third-party UI (kiosk, web ordering, drive-thru) drives the POS transaction engine via API.
extensibility-headless-embedded
Not scored by this record.
The vendor publishes an API changelog and a stated deprecation/notice policy for breaking changes.
extensibility-api-versioning-deprecation
Not scored by this record.
A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator
extensibility-data-portability-exit
Not scored by this record.
Reliability, offline & operations
Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.
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
Card payments can be accepted while offline via store-and-forward, not just cash-only fallback. differentiator
reliability-offline-card-auth
Not scored by this record.
The vendor publicly documents who bears the loss when a store-and-forward transaction declines after connectivity returns, and states any per-transaction or cumulative offline cap. differentiator
reliability-offline-decline-liability
Not scored by this record.
Multiple terminals continue to share a single check/table state over the local network while the internet is down (LAN-only degraded operation, not per-terminal islands). differentiator
reliability-lan-degraded-multi-terminal
Not scored by this record.
The vendor documents a local/on-premise transaction engine or edge server (not purely cloud-hosted request/response) for the ordering path. differentiator
reliability-local-transaction-engine
Not scored by this record.
Kitchen display and/or kitchen printer routing continues to function while offline.
reliability-offline-kds-printing
CLAIM: KDS and/or kitchen printer routing keeps working while offline. VERDICT: yes/D. The earlier pass found 'offline' once, on the Inventory page. The full WP REST census of www.restroworks.com (192 pages + 63 marketplace entries) has 143 hits, most on /compare/ pages missing from the sitemap sweep. EVIDENCE (vendor-written comparison pages, grade D, all HTTP 200): https://www.restroworks.com/compare/oracle-micros-simphony-vs-revel-systems/ and /compare/ncr-aloha-vs-ls-retail/ and /compare/oracle-micros-simphony-vs-ls-retail/: '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'. https://www.restroworks.com/compare/par-pos-vs-revel-systems/: 'Restroworks is built for restaurant continuity first, keeping orders, billing, and KDS running smoothly for up to 48 hours'. /compare/restroworks-vs-toast-pos/for-bakeries/: 'Restroworks includes a full offline mode, allowing billing, ordering, and payment processing to continue seamlessly. All data automatically syncs once the in[ternet returns]'. Older supporting copy on posist.com/restaurant-times (the offline-mode billing post): 'Posist software alternates from online to offline mode by storing all the data on the local server'. CAVEAT: this is a direct first-party statement naming the KDS, but only on comparison marketing. No admin doc describes the mechanism (local server, LAN routing), and kitchen printing offline is not named. Retrieved 2026-09-16. https://www.restroworks.com/compare/oracle-micros-simphony-vs-revel-systems/ · retrieved 2026-09-16 adversarially verified
The system automatically fails over to a backup printer or KDS station when a configured kitchen printer is unreachable, and alerts staff.
reliability-printer-fallback
MERGE CALL: landed at partial/B, not the proposed no/B. The alert conjunct IS met (print_failure_log, check_utility_status) and an operator redirect to the bill printer exists (kot_on_bill_print / reprint_KOT_on_bill_printer); the named shortfall is that the redirect is MANUAL and no backup/alternate printer setting exists among all 100 print settings, so there is no automatic failover (agilysys precedent). 329th: THE COMPLETE PRINT SETTINGS ENUMERATION, from the same closed bundle census described for delivery-zone-pricing (https://posist.biz/app/99687fd3.app.js, 37,787,481 bytes, re-fetched 2026-09-18 and byte-identical; 2,736 labelled settings in 127 groups; no lazy-chunk loader, so the bundle is the whole client). Every print-related group, read in full: 'KOT Print Settings' 60 settings, 'Print Settings' 21, 'Billing Print Settings' 1, 'SmartPrints Settings' 3, 'KDS Settings' 15 = 100 settings. NOT ONE is a backup, alternate, secondary, standby or failover printer. The routing settings are Print Server [print_server], Station wise print [station_wise_print], Tabwise Station wise print, Use Item wise Stations [item_station], Enable e-POS Epson TM-i Print, Enable Bluetooth Printer, EPSON Printer IP, Activate New Print Utility [a_n_p_u]. The failure-handling settings are only alerting/blocking: 'Enable Print Failure Log' [print_failure_log] (writes to an IndexedDB store: 'a.dbLog.transaction("PrintFailureLog","readwrite")'), 'Enable Printing Logs' [print_log], and 'Disable Billing If Print Utility Not Running' [check_utility_status] (polls the local utility at <print_server|localhost>:65505). The ONLY redirect to another device is OPERATOR-INITIATED, not automatic: {label:"Enable Button to send KOT on Bill Printer",name:"kot_on_bill_print",group:"KOT Print Settings",fieldType:"checkbox"}, rendered as a manual button 'ng-click="clickEvent(\'kotBillprint\')" ng-if=kot_on_bill_print' labelled reprint_KOT_on_bill_printer, next to reprint_KOT. VERDICT: no. The claim's failover conjunct ('automatically fails over to a backup printer or KDS station when a configured kitchen printer is unreachable') is positively absent from a closed configuration enumeration - a backup printer cannot be configured where no setting for one exists, and the 100-setting print surface is complete. FOR THE MERGE, THE HONEST COUNTERWEIGHT: the alert conjunct IS met (toast 'Print is Not Successful' / 'Printer Not available', 'Print Utility is Not Running . Kindly Start the POSIST Print Utility', plus the PrintFailureLog), and a manual one-tap redirect to the bill printer exists, so a merge that prefers partial/B with the shortfall named 'manual redirect only, no automatic failover' has the evidence to do so (precedent: agilysys partial/B on automatic receipt-printer fallback). CONTROLS (tokenised, case-insensitive, 37.8 MB bundle): 'Backup Printer' 0, 'default printer' 0, 'printer offline' 0, reroute 0, standby 0, failover 0, 'backup printer'/'alternate printer'/'secondary printer'/'fallback printer' 0; 'printer not available' 3 (the alert path). BOUND/RESIDUAL: the local POSIST Print Utility Windows service (port 65505) is not on a public download host - download/downloads/dl/files/static/cdn/apps/release/utility.posist.com and download(s).restroworks.com all NXDOMAIN - so its internal retry behaviour is unmeasured; what is measured is that the POS exposes no backup-printer configuration to route to. Retrieved 2026-09-18. https://posist.biz/app/99687fd3.app.js · retrieved 2026-09-18 adversarially verified
The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).
reliability-sync-conflict-handling
Not scored by this record.
The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).
reliability-offline-feature-matrix
Not scored by this record.
A public, per-component status page exists showing current and historical incident state without a login.
reliability-public-status-page
Not scored by this record.
A contractual uptime SLA with a stated percentage AND a service credit remedy is published or available in the standard agreement. differentiator
reliability-contractual-uptime-sla
Not scored by this record.
The vendor publishes written post-incident reports or root-cause summaries for major outages.
reliability-incident-postmortems
Not scored by this record.
24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.
reliability-247-live-support
Not scored by this record.
The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator
reliability-onsite-install
Not scored by this record.
A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.
reliability-hardware-replacement-sla
Not scored by this record.
Operators can trigger and retrieve their own data backup/restore, or the vendor publishes RPO/RTO figures for data recovery.
reliability-backup-restore
Not scored by this record.
The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.
reliability-pci-dss-4-attestation
Not scored by this record.
Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.
reliability-mfa-role-based-access
Not scored by this record.
A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.
reliability-self-serve-training
Not scored by this record.
Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. differentiator
reliability-failover-terminal-role
Not scored by this record.
Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.
reliability-cellular-backup
Not scored by this record.
Commercial, compliance & data ownership
Vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core POS software tier. differentiator
commercial-month-to-month-contract
Not scored by this record.
Vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. differentiator
commercial-no-early-termination-fee
Not scored by this record.
The auto-renewal term and the required cancellation notice window (e.g. 30/60/90 days) are stated in publicly accessible contract terms rather than only in a signed quote.
commercial-autorenew-terms-published
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
The POS software can be purchased and operated with a third-party payment processor of the operator's choice (no mandatory in-house processing lock). differentiator
commercial-processing-not-bundled
Not scored by this record.
Vendor publishes an interchange-plus (cost-plus) processing rate option with the markup stated as a specific bps + per-transaction figure, rather than only blended/flat card-present rates. differentiator
commercial-interchange-plus-published
Not scored by this record.
The processing agreement caps or prohibits unilateral vendor-initiated rate increases outside of pass-through interchange/network changes, or grants penalty-free exit on any increase. differentiator
commercial-rate-increase-clause
Not scored by this record.
Per-location and per-additional-terminal software pricing is published as specific dollar figures on the vendor's public site (not 'contact sales' only).
commercial-pricing-published
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
Individual modules (online ordering, KDS, loyalty, inventory, payroll, marketing) can be purchased à la carte and cancelled independently without repricing the base POS subscription. differentiator
commercial-module-unbundling
Not scored by this record.
All required terminals, KDS screens, and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental.
commercial-hardware-purchase-outright
CLAIM: all required terminals, KDS screens and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental. VERDICT: partial/C (was unknown/F; this cell had never been worked individually - its note was a one-line placeholder). SHORTFALL NAMED: no hardware price is published anywhere by Restroworks, and Restroworks does not sell the hardware at all - it is quoted through third-party 'hardware partners'. WHAT IS SATISFIED: there is no Restroworks-supplied hardware and therefore no lease or rental instrument; the operator buys commodity devices outright from whomever they like. EVIDENCE: the pricing page (https://www.restroworks.com/pricing/, retrieved 2026-09-18, 13,125 chars of stripped text) has three quote-only drivers - 'Software Requirements', 'Size and Terminals', and 'Hardware Requirements: If you wish to update the hardware, Restroworks hardware partners can offer various solutions like Tablets for order taking, POS terminal setups, printers, Kitchen display systems and more.' Every tile ends in 'Get an estimate'; no figure appears on the page. Restroworks' own comparison pages state the device posture: 'Hardware Agnostic. Unlike other platforms, Restroworks runs on your existing devices like POS terminals, tablets (iOS/Android), printers, KDS, and cash drawers. It provides you with the flexibility and choice to avoid vendor lock-in, cut upgrade costs, and roll out in phases without disruption' (restroworks.com comparison pages, grade D, corroboration only), and the kiosk product is described as 'RestroGO hardware agnostic self-service kiosk software'. CONTROLS/BOUND: tokenised, case-insensitive, over the full WordPress REST census of www.restroworks.com (255 documents, 3,476,274 chars, .cache/q314/restroworks/rw-wp.json) - lease 0, leases 0, leased 0, leasing 0, rental 0, rent 0, rents 0, buyout 0, 'security deposit' 0, instalment 0, installment 0, 'hire purchase' 0. POISON NAMED AND REMOVED: case-insensitive substring 'lease' matched 21 times in the marketing corpus purely inside 'please', and 'EMI' matched 39 times inside 'premium'/'semi'; tokenised, both fall to 0-1 (the one real 'lease' is a blog sentence about signing a property lease). The WP page registry holds no MSA, EULA, SLA, DPA or hardware terms - /terms, /terms-and-conditions, /terms-of-service, /legal, /msa, /eula, /sla, /dpa, /hardware, /subscription-agreement, /master-service-agreement all 404 with a fixed ~41.9 KB soft-404 body, and the only legal pages published are /privacy-policy and /website-terms-of-use (which governs the website, not the product). So: no lease is imposed and none is documented, but no price is published either. Retrieved 2026-09-18. https://www.restroworks.com/pricing/ · retrieved 2026-09-18 adversarially verified
Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator
commercial-hardware-not-locked
Not scored by this record.
One-time implementation, menu-build, onboarding, and training fees are published as specific amounts or explicitly stated as $0.
commercial-implementation-fee-published
Not scored by this record.
Operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee.
commercial-data-export-self-serve
Not scored by this record.
Guest/customer records, loyalty balances or point ledgers, and gift-card liability balances are exportable in machine-readable form by the operator. differentiator
commercial-export-customer-and-loyalty
Not scored by this record.
Contract or documentation specifies a post-termination data retrieval window (a defined number of days during which the operator can still export their data) rather than immediate cutoff. differentiator
commercial-post-termination-export-window
Not scored by this record.
Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator
commercial-data-ownership-clause
Not scored by this record.
The POS is source-available or open source with a documented self-hosting option (source published under an OSI or source-available license, not merely an open API).
commercial-source-available-selfhost
Not scored by this record.
Vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A / SAQ P2PE-HW, and names the applicable SAQ.
commercial-pci-p2pe-tokenization
Not scored by this record.
Vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — notably MFA for all access to the cardholder data environment including POS and back-office logins, and (for hosted ordering pages) payment-page script integrity monitoring per Req 6.4.3/11.6.1.
commercial-pci-dss-4-controls
Not scored by this record.
Vendor states it holds a current SOC 2 Type II (or ISO 27001) attestation and will provide the report under NDA via a trust center or on request.
commercial-soc2-attestation
Not scored by this record.
Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.
commercial-privacy-dsar-tooling
Not scored by this record.
Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator
commercial-wcag-kiosk-accessibility
Not scored by this record.
POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator
commercial-dual-pricing-compliant
Not scored by this record.
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 1 values — 1 upheld, 0 downgraded, 0 upgraded. It separately resolved 21 previously unknown values. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| order-capture-scheduled-orders | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | 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. source |
| menu-pricing-modifier-price-by-parent-size | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-no | 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'. source |
| menu-pricing-topping-quantity-tiers | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-no | 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. source |
| kitchen-bump-bar-hardware | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | 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'. source |
| guest-loyalty-accrual-models | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | 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. source |
| guest-loyalty-lifecycle-automation | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | 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. source |
| labor-clock-in-at-pos | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | 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. source |
| labor-manager-override-audit | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | 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. source |
| inventory-unit-conversion-yields | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | 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. source |
| inventory-count-modes | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | 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. source |
| reporting-pmix-modifier-level | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | 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. source |
| multi-location-central-menu-publish | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | 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. source |
| multi-location-price-zones | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | 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. source |
| extensibility-oauth-partner-apps | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-no | 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. source |
| extensibility-webhooks-push | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | 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. source |
| commercial-autorenew-terms-published | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-no | 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. source |
| order-capture-offline-order-entry | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | Site-wide sweep of page-sitemap.xml found the vendor's own competitor-comparison pages (NCR Aloha vs Toast, vs Revel, vs LS Retail; Oracle Micros Simphony vs LS Retail/Revel/Toast; PAR POS vs LS Retail/Revel) all carrying an identical 'Reliable Offline Mode' block: '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 ice-cream vertical page repeats 'Reliable offline mode to keep billing and order flow running even during internet disruptions.' Named shortfall: grade D vendor comparison marketing, and the claim's explicit second requirement - that the vendor publish what does and does not work offline - is unmet. No published statement covers card authorisation while offline, cash tender specifically, handheld scope, or reconnect sync-conflict handling; 'offline' does not occur anywhere in the api.restroworks.com reference; docs.restroworks.com is Auth0-gated (HTTP 400). source |
| menu-pricing-nested-modifiers | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | The Standard Menu (Menu Sync V2) schema is recursive: an entity carries 'modifiers' (Array, 'List of modifiers for the entity'); each modifier group carries min ('Minimum selection for the modifier'), max ('Maximum selection for the modifier'), order and constituentItems; and each constituent item is documented as a full entity record with its own 'modifiers' array and 'variants'. Two levels with independent min/max are therefore documented. Named shortfall: no supported nesting depth is stated and all published examples show constituentItems[].modifiers as [], so the claim's three-level requirement is not evidenced; and no forced-selection/required flag exists in the modifier schema - min >= 1 is the only candidate and the docs never describe it as enforcing a required choice. restaurant-menu-management-software/ covers only offers and combos, and the menu builder itself is behind the gated docs portal. source |
| delivery-dispatch-board | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | 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 to multiple delivery partners, live status updates and cancellation monitoring, and the API's Delivery folder shows per-order assignment of a delivery person from the POS. Named shortfall: no driver-availability display, no per-order elapsed-time indicator and no multi-order run batching is documented anywhere - the assignment surface is strictly one order to one delivery person - and the module is oriented to third-party partner routing rather than an own-driver dispatch board; no dispatch or expo screen is named. The admin docs that could settle batching are behind the Auth0-gated docs.restroworks.com. source |
| hardware-offline-mode | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | The vendor's competitor-comparison pages carry its only quantified offline statement: 'Orders, billing, and KDS continue to function without a single lag for up to 48 hours' when 'the internet drops' (identical block across the NCR Aloha, Oracle Micros Simphony, PAR POS, LS Retail and Revel comparison pages), and the ice-cream vertical page repeats 'Reliable offline mode to keep billing and order flow running even during internet disruptions.' Named shortfall: the claim's second requirement is wholly unmet - nothing published enumerates which functions degrade offline (card auth, loyalty lookup, refunds all unaddressed), cash-sale recording offline is never specifically stated, and kitchen printing is not named (only KDS). The main POS page and Front of House page contain no offline mention, 'offline' appears nowhere in the api.restroworks.com reference, and docs.restroworks.com is Auth0-gated (HTTP 400). source |
| reliability-offline-order-entry | unknown (grade F) - placeholder rationale: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | The comparison pages state 'Orders, billing, and KDS continue to function without a single lag for up to 48 hours' during an internet outage and the ice-cream vertical page repeats 'Reliable offline mode to keep billing and order flow running even during internet disruptions', so order entry and billing continuing offline is first-party confirmed. Named 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 continues 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 says nothing about offline and no admin documentation of the offline mechanism is publicly readable (docs.restroworks.com Auth0-gated, HTTP 400). source |
| commercial-pricing-published | no, grade B - Pricing page affirmatively declines to publish figures, list | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
Sources
Every URL this record cites. 25 in total.
- https://www.restroworks.com/
- https://www.restroworks.com/pricing/
- https://api.restroworks.com/
- https://www.restroworks.com/kitchen-display-system/
- https://www.restroworks.com/restaurant-crm-software/
- https://www.restroworks.com/restroapp-food-delivery-app/
- https://www.restroworks.com/restroweb-online-ordering-website/
- https://www.restroworks.com/restaurant-anti-theft-software/
- https://www.restroworks.com/restaurant-analytics-software/
- https://www.restroworks.com/restaurant-reporting-software/
- https://www.restroworks.com/solution-architecture/
- https://www.restroworks.com/restaurant-inventory-management-software/
- https://www.restroworks.com/website-terms-of-use/
- https://www.restroworks.com/page-sitemap.xml
- https://www.restroworks.com/blog/best-restaurant-scheduling-app/
- https://www.restroworks.com/llm-info/
- https://docs.restroworks.com/
- https://www.restroworks.com/compare/ncr-aloha-vs-toast/
- https://www.restroworks.com/ice-cream-shop-software/
- https://www.restroworks.com/marketplace/qwikcilver/
- https://www.restroworks.com/restaurant-menu-management-software/
- https://www.restroworks.com/marketplace-sitemap.xml
- https://www.restroworks.com/restaurant-delivery-management-software/
- https://www.restroworks.com/restaurant-pos-system/
- https://www.restroworks.com/front-of-house-software/