Vendors / QSR & drive-thru
GRUBBRR
A kiosk-and-self-checkout hardware/software vendor rather than a POS, and its distinguishing asset is breadth of POS neutrality — it claims integrations with 93+ POS systems including Toast, Square, Clover, NCR, PAR, Oracle, Xenial and Focus — but it publishes no price, no ownership and no developer documentation.
scored live legacy rubric
- Claims in scope
- 296
- Scored
- 44
- Assessed
- 44
- Unknown
- 252
- Not applicable
- 18
- Values challenged
- 13
unknown, never as no.Identity
- Owner
- Private; self-described as a self-ordering technology startup headquartered in Boca Raton, Florida. Ownership, parent and investors are not disclosed on its own site.
- Who it is for
- QSR, fast-casual, stadiums/venues and c-stores buying self-ordering kiosks and self-checkout to cut labor and lift ticket, keeping their existing POS.
- Site
- https://grubbrr.com/
Pricing
transparency: unknown · unit: unknown (per kiosk and/or per location, quote-only) · processor lock-in: unknown
- Software
- None published. The pricing page contains an ROI calculator (e.g. an illustrative '$75K per year' per-store return) and a 20% average upsell-lift claim, plus 'setup in as few as 48 hrs' — but no subscription tiers, kiosk hardware prices or contract terms. All pricing routes through a sales call (sales@grubbrr.com, 855-547-8227).
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.
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
Overturns a `no` whose prior rationale -- that GRUBBRR has no POS product, so check splitting and merging stay with the integrated POS -- is contradicted by GRUBBRR's own published prose: 'The customers can even split group orders and payments and speed up the end-of-service process.' The same sentence appears on /industry-template/ and /products/product-template/, and the knowledge-base article Version 14 Beta Deployment Notes lists, among its fixes, one made to partial payments for WorldPay, so a split-tender path demonstrably exists on the kiosk. Held at partial, not yes, because the claim requires four split modes plus merge and nothing documents any of them: across the full 549-document corpus (283 knowledge-base articles + 266 grubbrr.com posts and pages) `split check`, `merge check` and `merge tables` each occur zero times, and there is no check or table object for a merge to operate on -- a kiosk cart is finalised in one transaction. Graded C because the only affirmative statement is marketing prose; the vendor publishes no operational article on splitting. https://grubbrr.com/grubbrr-software-integration/ · retrieved 2026-09-09
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
CLAIM: with the internet down, terminals/handhelds still create orders, apply modifiers, send to kitchen and tender cash, AND the vendor publishes what does and does not work offline. VERDICT: unknown -> partial/B. The kiosk's own shipped source implements store-and-forward ordering with a direct-to-KDS fallback and blocks only online-dependent tenders; but GRUBBRR publishes no offline-scope statement (help.grubbrr.com 186-article Pylon KB: store-and-forward/queued/cached = 0, prior pass), so the publication conjunct fails. EVIDENCE (https://kiosk-preview.merchant.grubbrr.com/main.71026c23b5100e348186.js.map): src/app/components/order-review/order-review-footer/order-review-footer.component.ts: "console.log('sending order to kds direct with timeout of 5 seconds'); await this.kdsService.sendToKds(orderData);" in the error branch of "this.dataService.IsOnlineCheckSK().pipe(timeout(5000))"; when submitOrderAsync fails: "this.paymentService.setOrderToOfflineDb(orderData);". src/app/services/payment.service.ts setOrderToOfflineDb: "listObjOrderMasterData[0].IsOrderFailed = 'true';" then inserts order items AND "listOrderItemModifier" rows into the local DB. src/app/services/offline-order.service.ts: "select * from OrderMasters where IsOrderFailed='true'" re-sent by a timer loop ('Offline Order loop called', app.component.ts) and a manager-settings button "Process Offline Transaction" (settings-order-history.component.html). src/app/services/kds.service.ts sendToKds routes items per kitchen via local "Kitchen_Item_Mapping"/"Kitchen_Ingredient_Mapping" tables to "kdsm.KDSIPAddress". Tender scope: order-review-footer "// Check for offline in US connect payment" requires IsOnlineCheckSK for Card (non-Verifone), HouseCredit, USConnect, IDCard, RFID and otherwise shows 'device_offline_error'; other payment types (EPaymentType.Cash = 1) skip the check. CORROBORATION (production NGE kiosk, no map): https://kiosk.nge.grubbrr.com/assets/LazyApp-b437a63d.js Dexie schema "offlineOrders:\"++id\"", "Shift4 offline credit transactions" settlement, and "offline non card transactions" filtered by "!n.isSubmittedToCloud". SHORTFALL: self-service kiosk, not staff terminals/handhelds; code is not a published offline-scope statement. SURFACE (new, 2026-09-17): PUBLIC SOURCE MAP https://kiosk-preview.merchant.grubbrr.com/main.71026c23b5100e348186.js.map (12.6 MB; 846 sources, 431 first-party src/ files with sourcesContent; src/environments/environment.prod.ts: "environment: 'Production'", "apiUrl: 'https://api.merchant.grubbrr.com/api/kiosk/legacy/'") = the GRUBBRR legacy/SMB kiosk Angular app, found via crt.sh %.grubbrr.com (200 names) then bundle -> .map probes on every live SPA. Host is 'kiosk-preview' on the production merchant domain with a production build; it covers THIS kiosk app only. Other SPAs probed: api.merchant (Admin Portal 2.0), merchant/portal.merchant (SMB), kiosk.nge (NGE kiosk, Vite, 12 chunks, every .map returns the SPA shell = no maps), samsungtizen (no map), onlineorder (no map), console/gcc (SvelteKit). Retrieved 2026-09-17. https://kiosk-preview.merchant.grubbrr.com/main.71026c23b5100e348186.js.map · retrieved 2026-09-17 adversarially verified
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
CLAIM: future-dated orders with per-channel lead time, injected at a computed fire time. VERDICT: partial/A - GRUBBRR's QR/online ordering has a per-location future-order switch and the legacy kiosk order carries a pickup date. SHORTFALL: no lead-time setting and no fire-time or hold-and-release logic is defined in any spec (the only computed kitchen delay is the Toast-only Order Promise Time already recorded, which is POS-side and applies to immediate orders). EVIDENCE: https://api.nge.grubbrr.com/swagger/v1/swagger.json schema App.QROrdering.Models.LocationSetting: "pickupEnabled", "deliveryEnabled", "curbsideEnabled", "onlineOrderPaused", "tableOrderingEnabled", "futureOrderEnabled":{"type":"boolean"}, "timeZone"; https://api.merchant.grubbrr.com/swagger/v1/swagger.json schema LegacyKioskApi.Models.OrderMasterReq: "pickupDate", "pickupDateUTC". CONTROLS over all three specs, keys and strings, case-insensitive: lead|prep.?time|fire.?time|promise|asap = 0 hits; "schedul" hits are menuSyncSchedule, schedulePromotionID and discount schedules (poison). WEAKNESS: bare field names without descriptions. SURFACE (new, 2026-09-16): three ANONYMOUS OpenAPI 3.0.1 specs, found via the crt.sh certificate listing of %.grubbrr.com (202 names) plus /swagger probes: https://api.merchant.grubbrr.com/swagger/v1/swagger.json ('GRUBBRR.Web.UI', 170 paths, 221 schemas, 502 KB), https://api.nge.grubbrr.com/swagger/v1/swagger.json ('Grubbrr API', 86 paths, 271 schemas, 384 KB) and https://api.nge.grubbrr.com/swagger/partner-v1/swagger.json ('GRUBBRR Partner Ordering API', 20 operations, listed in the api.nge Swagger UI index). Each spec is a complete enumeration of ITS OWN API only; other GRUBBRR APIs exist but are not anonymous (sandbox.api.nge and test.api.ecm return 403; api.gem serves an Azure Functions placeholder; endpoint calls return 401), so the specs are not a platform census. Retrieved 2026-09-16. https://api.nge.grubbrr.com/swagger/v1/swagger.json · retrieved 2026-09-16 adversarially verified
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
Kiosks are built on partner hardware including Verifone payment devices, which implies EMV and contactless; Apple Pay/Google Pay are not enumerated on the pages fetched. https://www.grubbrr.com/ · retrieved 2026-08-01
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.
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.
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
Gift cards exist on the kiosk but are not GRUBBRR's own program. Redemption is enumerated in the v14 release notes' Payments section as a single third-party integration: 'Paytronix Giftcard - Users must enter the Gift Card Number on the Kiosk to redeem their balance.' Sale is a location-level toggle only: General Settings > Common > Gift Cards, 'Allow Purchase of Gifts Cards using Kiosk' ('Common Kiosk Configurations in the GRUBBRR Portal'). Named shortfalls: no first-party card issuance or balance ledger is documented anywhere in the 282-article knowledge base (balance is held by Paytronix and read by entering the card number); no cross-location redemption scope is stated; and no online-ordering-channel gift card flow is documented - GRUBBRR's online-ordering channel appears only as an order-type checkbox. Redemption outside Paytronix is undocumented, and the payment-option list itself says 'If a payment option you are looking for is missing, contact GRUBBRR customer support.' https://help.grubbrr.com/s/article/Version-14-Limited-Release-notes · retrieved 2026-08-04
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
Refunds are documented and reasonably rich — Refund By Item, Refund by Amount and Full Refund from Orders > Detailed Orders, and the same full/partial refund flow from the Enterprise Console's Order History. Shortfalls: the control is back-office sign-in plus a Portal role privilege, not a manager PIN or approval prompt at the point of sale; no article describes an immutable audit log identifying the approver of a refund; and voids, comps and no-sales have no equivalent flow because there is no register or cash drawer. The article also warns the refund runs through a GRUBBRR virtual terminal and 'will not appear in your POS records'. https://help.grubbrr.com/s/article/How-to-Refund-Kiosk-Orders-through-the-GRUBBRR-Portal · retrieved 2026-08-03
In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator
payments-chargeback-tooling
Not scored by this record.
Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator
payments-card-on-file
Not scored by this record.
Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator
payments-payout-timing
Not scored by this record.
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 specific KDS stations by item, category, order type, or revenue center, configurable per location without vendor involvement. VERDICT: yes/B - item-level routing to named kitchens, each with its own KDS and/or printer, configured in the Portal at Location level. EVIDENCE: 'How to Manage Kitchens in the GRUBBRR Portal' (https://help.grubbrr.com/articles/6231833665-how-to-manage-kitchens-in-the-grubbrr-portal): "Can my GRUBBRR Kiosk send different tickets to different stations in my restaurant? ... In restaurants with multiple kitchens, we use kitchen mapping. Items can be sent to a specific kitchen for preparation or all kitchens. ... In kitchens with a KDS, the appropriate items and order information will appear on the assigned screen. 1. Sign in to the GRUBBRR Portal at the Location level 2. Click "Configure" 3. Click "Kitchen Settings" 4. Click "Add New" ... 7. Assign an active KDS device to the kitchen ... 9. ... click "Item Mapping" 10. Assign any relevant items to the kitchen 11. Click "Update All"". LIMITS: the claim is disjunctive and item-level mapping satisfies it; category/order-type/revenue-centre routing is not documented, and the article sits in the 'GRUBBRR First Generation Platform Guides' collection (no Console-platform equivalent found). SURFACE: help.grubbrr.com has MIGRATED from the Salesforce guest knowledge API (282 articles, prior pass; that endpoint now returns the KB's 404 page) to a Pylon knowledge base. Census 2026-09-16: sitemap.xml lists 186 /articles/ URLs, llms.txt lists the same 186 (zero diff); all 186 fetched at 200; the href fixpoint over bodies adds 21 further ids, all 14-digit Zendesk-shaped legacy ids that 404 (a fabricated id also 404s, so Pylon cannot discriminate retired from hidden) - therefore NOT a census and no `no` may rest on it. Also read: grubbrr.com WordPress REST, 461 posts/pages/news (elementor_library, feedback, jetpack_form 401). Retrieved 2026-09-16. https://help.grubbrr.com/articles/6231833665-how-to-manage-kitchens-in-the-grubbrr-portal · 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
An expediter role exists as a distinct device: the OPB Order Update Flow configures four separate triggers — 'Completing an Order on the KDS', 'Completing an Order on the Expediter KDS', 'Highlighting an Order on the KDS' and 'Highlighting an Order on the Expediter' — each of which can move an order to Ready for Pickup or Picked Up. Combined with kitchen mapping ('How to Manage Kitchens in the GRUBBRR Portal': items are sent to a specific kitchen or all kitchens, each with its own printer and/or KDS). Shortfall: nothing in the knowledge base describes the expediter screen consolidating items from multiple prep stations into one order view, or gating order completion until every contributing station has bumped its items; the documented completion trigger is a single action on the expediter. https://help.grubbrr.com/s/article/Common-Order-Progress-Board-Configurations-in-the-GRUBBRR-portal · retrieved 2026-08-03
Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator
kitchen-course-firing
Not scored by this record.
Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator
kitchen-prep-time-pacing
Not scored by this record.
Kitchen load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator
kitchen-order-throttling
Not scored by this record.
Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator
kitchen-channel-pause-propagation
Not scored by this record.
Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator
kitchen-order-ready-callback
Not scored by this record.
KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.
kitchen-bump-bar-hardware
CLAIM: KDS supports physical bump bars or programmable keypads in addition to touchscreen, with documented supported models. VERDICT: partial/A - GRUBBRR's own KDS device settings carry a bump-bar switch. SHORTFALL: no supported bump-bar models or keypad mapping are published anywhere. EVIDENCE: https://api.merchant.grubbrr.com/swagger/v1/swagger.json, schemas GRUBBRR.Application.LegacyKDSApi.Models.KdsVM, LegacyKDSApi.KdsDeviceUpdate and LegacyKioskApi.Models.KDSSettingReq (the KDS settings bodies behind POST /api/kiosk/legacy/UpdateKDSSetting and PUT /api/location/{locationId}/kds/upsert) each define "useBumpBar":{"type":"boolean"} alongside the other KDS display settings ("showDelayOrderButton", "isAutoScrollToNewOrders", "numberOfTicketsVisible", "hideActions"). The field has no description. WEAKNESS: a bare boolean shows a bump-bar input mode exists, not which hardware. SURFACE (new, 2026-09-16): three ANONYMOUS OpenAPI 3.0.1 specs, found via the crt.sh certificate listing of %.grubbrr.com (202 names) plus /swagger probes: https://api.merchant.grubbrr.com/swagger/v1/swagger.json ('GRUBBRR.Web.UI', 170 paths, 221 schemas, 502 KB), https://api.nge.grubbrr.com/swagger/v1/swagger.json ('Grubbrr API', 86 paths, 271 schemas, 384 KB) and https://api.nge.grubbrr.com/swagger/partner-v1/swagger.json ('GRUBBRR Partner Ordering API', 20 operations, listed in the api.nge Swagger UI index). Each spec is a complete enumeration of ITS OWN API only; other GRUBBRR APIs exist but are not anonymous (sandbox.api.nge and test.api.ecm return 403; api.gem serves an Azure Functions placeholder; endpoint calls return 401), so the specs are not a platform census. Retrieved 2026-09-16. https://api.merchant.grubbrr.com/swagger/v1/swagger.json · retrieved 2026-09-16 adversarially verified
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.
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
Upheld and now cited. GRUBBRR is a self-ordering front end, and this article states that in integrated mode 'all orders are finalized through the POS.' -- fulfilment, including any delivery leg, belongs to the merchant's POS, not to GRUBBRR. For the standalone mode the absence is measured directly: across all 283 published knowledge-base articles (enumerated via the Salesforce guest knowledge API at help.grubbrr.com/services/data/v59.0/support/knowledgeArticles, which returns every article the record already cited) the terms `driver`, `dispatch` and `courier` each occur zero times, and there is no employee record type for a driver -- Employee Management stores only a name, a 4-digit access code, a phone number, an email and a role. The nine products in the published catalogue are Self-Ordering Kiosks, Line Buster, Contactless Ordering, Order Progress Board, Self-Checkout, Kitchen Display, Digital Menu Board, Drive-Thru and Food Locker; none is a driver module. https://help.grubbrr.com/s/article/Introduction-to-POS-Integrations · retrieved 2026-09-09
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
Upheld and now cited. The documented order path ends at the merchant's back of house, not at a GRUBBRR dispatch surface: 'The POS processes the order through the location's Back of House environment and returns an Order ID to the GRUBBRR Portal'. GRUBBRR does ship two order-status screens -- the Kitchen Display System and the Order Progress Board -- but both are prep-and-pickup displays; neither shows undispatched orders, driver availability or run batching, and `dispatch` occurs zero times in all 283 knowledge-base articles; its single occurrence in the whole 549-document corpus is in the kiosk EULA, where the word describes GRUBBRR sending an e-mail notice. `driver` and `courier` are likewise zero across the knowledge base. https://help.grubbrr.com/s/article/Introduction-to-POS-Integrations · retrieved 2026-09-09
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.
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.
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
Mobile ordering ('Line Buster') and QR/drive-thru ordering are first-party and brand-owned rather than marketplace; a full commission-free web ordering site on the restaurant's domain is not clearly documented. https://www.grubbrr.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
One-tap reorder is present and is a default of the loyalty flow: a signed-in guest sees 'their past five Kiosk orders from any of your locations' and selecting an item 'will automatically apply all of the same customizations from the customer's past order'. Version 14 added the same flow for non-loyalty guests via a guest sign-in. Shortfalls: no tokenized saved card is documented anywhere — the only account-based payment methods in the knowledge base are ID Pay / Member Pay, prepaid monthly-allowance accounts keyed to a member ID or scanned ID card, and house accounts; and no saved-address concept exists, consistent with there being no first-party delivery. https://help.grubbrr.com/s/article/How-Past-Orders-Works-With-Loyalty-or-with-GRUBBRR-Frequent-Customer · retrieved 2026-08-03
Digital checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator
digital-upsell-engine
Not scored by this record.
Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.
digital-scheduled-pacing
Not scored by this record.
Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.
digital-fulfillment-modes
Not scored by this record.
Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.
digital-qr-table
Not scored by this record.
Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator
digital-kiosk
Not scored by this record.
Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.
digital-group-ordering
Not scored by this record.
Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator
digital-catering-portal
Not scored by this record.
Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator
digital-voice-ai-phone
Not scored by this record.
Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.
digital-drivethru-ai
Not scored by this record.
Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.
digital-sms-ordering
Not scored by this record.
Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator
digital-google-order
Not scored by this record.
Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.
digital-apple-business-connect
Not scored by this record.
Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.
digital-loyalty-attach
Not scored by this record.
Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.
digital-subscriptions
Not scored by this record.
Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.
digital-promo-parity
Not scored by this record.
Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator
digital-guest-data-ownership
Not scored by this record.
Digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.
digital-checkout-pci-sca
Not scored by this record.
Digital channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator
digital-surcharge-transparency
Not scored by this record.
Guest data, loyalty & marketing
Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.
guest-loyalty-unified-profile
A guest identity does span locations: signing in to loyalty on the kiosk surfaces 'their past five Kiosk orders from any of your locations', and GRUBBRR ships an in-house 'Frequent Customer' feature alongside third-party providers (Punchh, Como, Bruster's, OloPunchh). Shortfalls: the documented history is explicitly kiosk orders only and capped at five, with nothing describing merge of in-store POS or first-party web/app transactions into the same profile; identity is held by the loyalty provider, with GRUBBRR configuring only login method (QR, phone or email), points display and redemption; and no dedup/merge behaviour is documented in any article. https://help.grubbrr.com/s/article/How-Past-Orders-Works-With-Loyalty-or-with-GRUBBRR-Frequent-Customer · retrieved 2026-08-03
Orders arriving from third-party marketplaces (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. differentiator
guest-loyalty-thirdparty-identity-attach
Not scored by this record.
Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.
guest-loyalty-accrual-models
329th: NOW PUBLISHABLE AS NO, on a COMPLETE census of GRUBBRR's own configuration app. SURFACE (new): console.grubbrr.com, title "GRUBBRR Enterprise Console" (SvelteKit, anonymous login page). Its entry bundle /_app/immutable/entry/app.BkIEgCT8.js ships __vite__mapDeps with 315 file paths; fetched to a fixpoint (2 rounds, 9 further files discovered inside the chunks) = 324/324 files at 200, 0 misses, 28.3 MB, 4,995,244 tokens; a nonsense sibling entry (app.ZZQNONSENSE.js) 404s with a 2,400 B body, so the host discriminates. The app ships the FULL protobuf message registry for every service it calls, i.e. a field-level enumeration, plus 701 distinct endpoint paths incl. the whole /v1/<Service>/<Method> catalogue. THE DECISIVE ENUMERATION: loyalty configuration is a protobuf `oneof instrument` with exactly nine alternatives - cloverSportConfig, paytronixIntegrationConfig, punchhIntegrationConfig, genericIntegrationConfig, paytronixOloIntegrationConfig, rbiIntegrationConfig, oloPunchhIntegrationConfig, spendGoIntegrationConfig, grubbrrFrequentCustomerConfig - eight of which are bolt-on providers, and the ONE first-party alternative is declared with an EMPTY field list: `super("GrubbrrFrequentCustomerConfig",[])`. GRUBBRR's own guest programme therefore has zero configurable parameters: no points-per-dollar, no punch/visit count, no spend tier. The wider first-party "Frequent Customer" surface is a ROSTER plus a login discount, not an accrual engine: console routes /frequent-customer, /frequent-customer-sign-up, /frequent-customer/bulk (bulk upload, frequent_customer_import_template), /frequent-customer/confirm, /frequent-customer/order; flags EnableFrequentCustomers, enableFrequentCustomerLoginDiscounts, isFrequentCustomersEnabled; LoyaltyDisplaySettingsConfigVM_FrequentCustomerDiscountApplicationModeEnum = {ManualSelect=0, AutoApply=1} (HOW a discount is applied, not how it is earned); reporting only (FrequentCustomerReportApi, CustomerSummaryOutputDto.frequentCustomerOrderPercentage). The complete LoyaltyService method list is likewise provider-plumbing only: GetDiscountTenders, GetIntegrationDefinitions, GetLocationConfig, GetLocationIntegrationDefinitions, PullLoyaltyConfiguration, RemoveIntegrationDefinition, UpdateLocationConfig, UpdateLoyaltyDisplaySettings, UpdateSquareLocationConfig, UpdateSquareLoyaltyDisplaySettings, UpsertIntegrationDefinition (+ CompaniesService/AddSqaureLoyaltyIntegration, KioskConfigService/Get|UpdateLoyaltyFeatureFlag, UpdateAllowRealTimeRewardValidationFlag). The 119 *Loyalty*/*IntegrationConfig* message names are all provider adapters (Brusters, Como, DeliverEct, Demo, Incentivo, NCR, Olo, OloLoyaltyV2, PARRetail, Paytronix, Punchh, Qubriux, RBI, Sparkfly, SpendGo, Square, Thanx) or display/lookup DTOs (LoyaltyColorsVM, LoyaltyDisplaySettingsConfigVM, LoyaltyUserVisitInfo = provider-returned visit data, showLoyaltyPointsOnHeader). CONTROLS, tokenised, over the 4,995,244-token console census: accru*=0, pointsPer=0, stamp*=4 (all the word "stamp" in timestamp contexts), referrizer=0, levelup=0; punch*=294 and punchh=158 are ALL the vendor Punchh (poison - a substring trap this cell hit before), paytronix=34 likewise. SECOND COMPLETE APP: portal.merchant.grubbrr.com (SMB Console, Angular) main.4f3429438223a423.js 7.03 MB (1,128,321 tokens) + the runtime's only two lazy chunks (574.ba395f5895c16b04.js, 919.62614f46a762bb5b.js) = the whole app: accru*=0, pointsPer=0, punchh=0, paytronix=0, word-boundary tier=0, earn=3 and the only loyalty content is a kiosk PREVIEW graphic ("LOYALTY PROGRAM / Earn Rewards! / Get discounts and offers with our fantastic customer loyalty program", img customerLoginLoyalty.png) - no earn rule; points*=146 and visit*=100 there are chart.js pointStyle/pointStrokeColor and Angular/babel visitor-AST poison. Together with the previously recorded closed kiosk enum (LoyaltyType {None, OLOPunchh, Referrizer, LevelUp, OLOPaytronix}) and the 3 published specs' provider-pointer LoyaltySettingVM, every configuration surface GRUBBRR ships enumerates loyalty as a third-party provider, which is exactly what the claim excludes. BOUND: the two Consoles are GRUBBRR's own and only merchant-facing configuration apps; this does not speak to what a provider like Punchh offers inside its own product. Retrieved 2026-09-18. https://console.grubbrr.com/_app/immutable/entry/app.BkIEgCT8.js · retrieved 2026-09-18 adversarially verified
Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator
guest-loyalty-tiers
Not scored by this record.
Documents explicitly what loyalty lookup, accrual, and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). differentiator
guest-loyalty-offline-behavior
Not scored by this record.
Offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. differentiator
guest-loyalty-offer-stacking-rules
Not scored by this record.
Offers can be issued to a dynamically defined audience (rules over recency, frequency, spend, or items purchased) rather than only broadcast to the whole list. differentiator
guest-loyalty-targeted-offers
Not scored by this record.
Automatically computes recency/frequency/monetary or equivalent lifecycle segments (new, regular, at-risk, lapsed, VIP) without the operator building the queries. differentiator
guest-loyalty-rfm-segmentation
Not scored by this record.
Ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns rather than one-off manual sends.
guest-loyalty-lifecycle-automation
GRUBBRR does not ship campaign automation; it configures somebody else's loyalty engine. This article enumerates the entire loyalty surface GRUBBRR exposes — provider enablement, Punchh location/business keys, receipt features, redemption modes (scan-and-redeem, visit-based), maximum rewards per order, guest check codes, login method and display strings — and campaigns are not among them; the only lifecycle-adjacent item is a flag asking Punchh to collect date of birth and gender. Across all 282 articles the words 'campaign', 'birthday' (outside that flag) and 'win-back' do not appear. GRUBBRR's own CRM module is Members (prepaid ID Pay accounts) and guest surveys; its only guest messaging is on-screen behaviour-based messages and Toast-sourced order-ready SMS. https://help.grubbrr.com/s/article/How-to-Set-Up-Punchh-in-the-GRUBBRR-Console · 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
Overturns a `no` whose prior rationale -- no POS terminal and no labor module -- is wrong on the second half: GRUBBRR does have an employee module. This article documents it -- 'GRUBBRR creates access codes for "Employee" Accounts, which are configured through the GRUBBRR Portal.' -- with each employee carrying a name, a custom 4-digit access code and a role, and it states that 'Access codes are also used on the POS for opening and closing tills, opening the cash drawer, and other functions.' The separate article How to Access Basic Reports in the GRUBBRR Portal adds an Employee Attendance section to the Z Report which, where employee management is in use, lists employee shifts and hours. Held at partial because the claim's mechanism is not documented: no article describes a clock-in or clock-out action, GRUBBRR ships no POS terminal of its own (the tills and cash drawer named here are the integrated third-party POS), and the terms `clock in`, `clock out`, `time clock`, `timesheet` and `payroll` occur zero times across all 283 knowledge-base articles. https://help.grubbrr.com/s/article/How-to-Find-Edit-Access-Codes-for-the-Kiosk-in-the-GRUBBRR-Portal · retrieved 2026-09-09
Captures a photo at punch (or performs facial verification) attached to the timecard entry, with a photo-only mode available that stores no biometric template. differentiator
labor-photo-punch-verification
Not scored by this record.
Supports mobile clock-in restricted by geofence or location validation for staff who do not punch at a fixed terminal.
labor-geofenced-mobile-punch
Not scored by this record.
Records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, with the behavior documented. differentiator
labor-offline-time-punch
Not scored by this record.
Permissions are grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers.
labor-granular-rbac
Roles are genuinely custom rather than fixed tiers: Users > Role Master > Add New, then 'privileges' to 'Grant the user access to the required features/settings', and 'we give users access to the company or location level'. Temporary users can additionally carry a start and end date. Shortfalls: the privilege set governs GRUBBRR Portal features and settings, not register actions — void, comp, drawer-open and price-change have no equivalent because there is no terminal or cash drawer; scoping is documented at two levels (company or location), not per location group; and the actual list of grantable privileges is published only as a screenshot inside the article, so the granularity cannot be verified from text. https://help.grubbrr.com/s/article/How-to-manage-Users-Roles-in-the-GRUBBRR-Portal · retrieved 2026-08-03
Manager overrides and approvals are attributed to the individual approver and written to an immutable audit trail queryable after the fact.
labor-manager-override-audit
329th: MOVED TO NO. The premise of the old note - that there is no override or approval flow to audit - is falsified by the new console census: GRUBBRR DOES ship configured manager/staff approvals, and they are simply not attributed. SURFACE (new): console.grubbrr.com "GRUBBRR Enterprise Console" (SvelteKit), __vite__mapDeps 315 files fetched to a fixpoint = 324/324 at 200, 0 misses, 28.3 MB, 4,995,244 tokens, 701 endpoints, full protobuf field registry (nonsense entry app.ZZQNONSENSE.js 404s). THE APPROVAL FLOWS IT ENUMERATES: the order-limits config message carries field 13 `isRequiresManagerApproval` alongside quantityLimitPerItem, maxAlcoholItemsPerOrder, maxNumberOfItemsPerOrder and maxDiscountPerOrder; `AgeVerificationSettingsVM` is exactly {enabled, selfValidationRequired, staffApprovalRequired}. Neither message, and no request/response DTO in the 4.99M-token census, carries an approver, staffId, employeeId, pin-holder or reason field for the approval event. CONTROLS, tokenised, over the console census: approver*=0, approve*=0, immutab*=0, supervisor*=0; approval*=17 and every hit is either isRequiresManagerApproval/staffApprovalRequired (the settings above) or `approvalCode` in card-payment data (poison); audit*=54 and EVERY hit is menu-configuration audit (MenuAuditEntityCountDto {name, totalCount, itemWithoutImageCount, unassignedCategoriesCount, unassignedItemsCount, posDeletedRecordsCount}, MenuAuditEntityDto, route /menu-manager/menu-audit) - a config-drift count, not a transaction log. The two candidate audit-shaped surfaces both fail on inspection: /users/track-action posts `TrackUserActionCommand = {actionType (enum 0|12|13|14|15), sessionId, summary, data}` with NO user field - UI telemetry, not attribution; and GEM/Event Monitor (/gem2, /gem/event-monitor/, nav "Support > Events") is an alerting tool whose table columns are Scenario, Scenario Description, Status, Actions/"View Logs" - scenario monitoring, not a user-action trail. The enumerated reporting catalogue has no audit report either: /insights/{glance, sales-analytics, product-analytics, discounts-analytics, order-timing-analytics, aborted-orders-analytics, store-performance-analytics, upsell-analytics, upsell-summary, user-behavior-analytics, system-health-analytics, customer-surveys, benchmark-report, custom-reports-analytics}. SECOND COMPLETE APP: portal.merchant.grubbrr.com (SMB Console, Angular) main.4f3429438223a423.js 7.03 MB (1,128,321 tokens) + the runtime chunk table's only two lazy chunks = the whole app: audit*=0, approv*=0, approver*=0, immutab*=0, supervisor*=0. THIRD SURFACE (already held): the kiosk's own source map shows the approval itself is unattributed - manager-pin-dialog.component.ts checks "SELECT * FROM StaffMasters WHERE Code=?" and logs only `new loggingData('KIOSK','Manager Login','Log','Manager login clicked.',false)`, with no staff id and nothing written to the order. So across every app GRUBBRR ships, manager approvals exist, are not attributed to an individual approver, and no immutable queryable trail of them is offered: all three conjuncts of the claim fail. BOUND: production JS of GRUBBRR's two merchant Consoles plus the kiosk app (grade B, not A - this is shipped code, not published documentation); a server-side trail GRUBBRR never exposes in its own admin UI or reports would not be visible here, which is the one residual risk. Retrieved 2026-09-18. https://console.grubbrr.com/_app/immutable/entry/app.BkIEgCT8.js · retrieved 2026-09-18 adversarially verified
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
Upheld, but the previous rationale -- that the published catalogue holds no inventory or recipe-costing module -- was false in its first half and is replaced: GRUBBRR does publish an inventory module, and this article is its complete scope -- 'how to enable inventory management for individual items, how to create and manage your "on-hand" stock, and how to enable automated notifications when your inventory reaches a preset "low stock" threshold.' That is finished-goods depletion of menu items, not ingredient costing. There is no bill of materials, no sub-recipe and no plate cost: `recipe` occurs zero times across all 283 knowledge-base articles, and GRUBBRR's own use of the word ingredient is a redefinition that runs the other way: the knowledge-base article Intro to Nested Modifiers in the GRUBBRR Portal defines any modifier that does not trigger a further choice as an Ingredient, so an ingredient in this product is a modifier option on a menu, not a stocked raw material. Nothing recalculates a cost when a component price changes. https://help.grubbrr.com/s/article/How-to-use-Inventory-Tracking-in-the-GRUBBRR-Portal · retrieved 2026-09-09
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
Upheld, with the previous rationale -- that the published catalogue holds no inventory module -- replaced: an inventory module exists, and this article shows that its stock figure is a single undimensioned integer per menu item: 'You can manually change an item stock in the "Add Current Stock" field', and 'You can both add and subtract from your stock with this field.' The screen is titled Ready Item Stock and carries two numeric columns, Stock on Hand and Low Threshold. No purchase unit, recipe unit or count unit is stored and no conversion factor exists anywhere: `unit of measure`, `par level` and `yield` each occur zero times across all 283 knowledge-base articles. A case-to-pound-to-ounce conversion is not expressible. https://help.grubbrr.com/s/article/How-to-Manually-Update-your-Item-Inventory-in-the-GRUBBRR-Portal · retrieved 2026-09-09
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
Upheld, with the previous rationale -- that the published catalogue holds no inventory module -- replaced: an inventory module exists, but it offers exactly one adjustment mode and no count session at all. Stock moves in two ways only: automatic depletion on sale, since 'The GRUBBRR portal will automatically begin subtracting sold items from this listing, so it's best to update these settings outside of normal business hours.', and a typed delta into the Add Current Stock field. There is no full physical count, no spot count and no scheduled cycle count, and no variance is computed or retained -- an adjustment overwrites the on-hand figure and the article documents no history. `cycle count` and `stock count` each occur zero times across all 283 knowledge-base articles; the single occurrence of the word variance anywhere in the corpus is the Z Report's cash-management line, which is about cash, not stock. https://help.grubbrr.com/s/article/How-to-Manually-Update-your-Item-Inventory-in-the-GRUBBRR-Portal · retrieved 2026-09-09
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.
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
Browser dashboards exist at both levels — a Company Dashboard tracking KPIs across all active locations plus a Location Dashboard with Sales, Item Mix, Payment Types and a KPI panel ('Introduction to the GRUBBRR Portal Dashboard'), and the Console's 'At a Glance' dashboard with Sales, Upsells, Device Health, Aborted Orders and Store Performance tiles. Shortfall on latency, stated by the vendor: 'This dashboard updates at 6 AM, 10 AM, 2PM, 6PM and 10PM Eastern Time every day' — five refreshes a day, not within minutes of the sale. The Portal dashboard's refresh cadence is not stated anywhere, and device telemetry is separately documented as heartbeat-based with up to a 15-minute lag. Second shortfall: no mobile app is documented for either console; every reporting article routes through a browser sign-in. https://help.grubbrr.com/s/article/Using-GRUBBRR-Analytics · retrieved 2026-08-03
Generates a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types, and expected cash deposit in one document.
reporting-eod-closeout
Overturns a `no` whose prior rationale -- no cash drawer or tender reconciliation, with EOD left to the integrated POS -- is directly contradicted by this article. GRUBBRR publishes a Z Report that is the EOD packet the claim describes: 'Z Reports summarize all data for selected dates, including sales, taxes, tips, discounts, refunds, and employee attendance.' Its enumerated sections cover every element the claim requires in one document -- gross sales ('Gross Sales The total amount of revenue generated from selling product'), net sales, Amount Collected, tender types ('Payment Types This breaks down total sales for the selected period by payment type'), Channel Sales, a Credit Card Sales Breakdown, Fees, Discounts & Loyalty, Sales by Category, a Canceled Orders Summary covering voided and refunded orders, Tip and Gratuity summaries, and cash reconciliation: 'Cash Management Summary Shows all cash management data, including variance'. It is a true business-day close, not a calendar-day cut: 'If your business operates past midnight, you can set a custom report cut-off time in the Portal. This way, the orders between midnight and closing are factored into the same business day.' The report is runnable from the Portal, a POS or a kiosk, and its layout is customisable. https://help.grubbrr.com/s/article/How-to-Access-Basic-Reports-in-the-GRUBBRR-Portal · retrieved 2026-09-09
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
A Product Mix report exists under Reports > Sales > Product Mix and 'will show the assortment of items sold for a specifically selected date filter... can also be refined to show items from a specific category'. Shortfalls: the documented breakdown is item-level with a category filter only — no modifier-level line, and no daypart or revenue-centre filter; the article does not state which measures the report carries (the quantity/gross/net breakdown the claim asks for is described for the Z Report, not for Product Mix). The Console's separate 'Products' insight page likewise 'tracks the performance of individual menu items' with no modifier dimension. https://help.grubbrr.com/s/article/How-to-Access-Basic-Reports-in-the-GRUBBRR-Portal · 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 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
More than a flat list: the Console has a Scope tool switching between Enterprise and Location views, an Organizations object administered under Support > Organizations & Users, and a grouping layer above the store that reporting uses — 'Store Performance provides a detailed breakdown of the active location against other locations in the organization/location group' — with a 'Location Group ID' issued by GRUBBRR Operations during Clover Sport setup. Shortfalls: the group tier is never documented as an operator-manageable object (no article covers creating or editing a location group), and permissions do not scope to it — 'How to manage Users & Roles' places user access at 'the company or location level' only, so the third level exists for analytics but not for permission grants. https://help.grubbrr.com/s/article/Using-GRUBBRR-Analytics · retrieved 2026-08-03
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 docs enumerate what is authored centrally and price is deliberately excluded: 'Categories, Items, Modifier Groups, Modifiers, Combos, Upsells, and Discounts are all configured at the Company level. Menu Prices, Item 86 Status, General settings, and Kiosk settings are all configured at the Location level', and 'All menu prices are still defined at the location level.' The ECM path says the same — 'When an organization uses ECM controls, prices are managed by the POS at each individual location' — and the v14.6 enhancement was only the ability to view location pricing from the enterprise menu manager, not set it. There is therefore no price tier/zone object: differential pricing is inherited from each store's POS, and no per-channel or per-daypart price variant is documented either. https://help.grubbrr.com/s/article/How-Company-Level-Menu-Management-works-with-POS-Integrations · 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.
Supports locations operating in different currencies and languages within one enterprise account, with consolidated reporting converted to a reporting currency.
multi-location-multi-currency-locale
Not scored by this record.
Produces an immutable audit log of who changed which configuration object (price, tax, permission, discount) at which location and when, exportable or queryable by corporate. differentiator
multi-location-config-audit-log
Not scored by this record.
Supports SSO via SAML or OIDC against the customer's identity provider for back-office/above-store users, with SCIM or equivalent for automated deprovisioning. differentiator
multi-location-enterprise-sso
Not scored by this record.
Publishes a documented multi-location API (or data warehouse/BI export) that returns transaction-level data across all locations in one authenticated call, without per-location credentials. differentiator
multi-location-enterprise-api
Not scored by this record.
Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.
multi-location-central-labor-policy
Not scored by this record.
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
Hardware partners are named (Samsung, Verifone) and floor-standing vs countertop kiosk form factors are described; no client OS names or minimum specs are published. https://www.grubbrr.com/ · retrieved 2026-08-01
Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.
hardware-handheld-purpose-built
Not scored by this record.
The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator
hardware-handheld-battery-swap
Not scored by this record.
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
The vendor's documented answer to an offline terminal is to stop selling, not to degrade: kiosks on v12.5+ 'can be set up to block any orders when the device is offline', displaying 'a pop-up to let customers know that the device can't connect to the internet, and to speak to location staff instead' — the article summary states 'the Kiosk will automatically direct customers to the POS if the device is offline'. There is no continued-offline operation behind the flag, because 'Introduction to POS Integrations' documents that every order round-trips the cloud mid-transaction: the kiosk submits the order total to the GRUBBRR Portal, 'the Portal submits the order total back to the POS for verification', payment is taken only after the verified total returns, and the guest receipt prints only after the Portal returns the POS's Order ID. No article documents offline capture or queueing, offline cash recording, or an enumerated list of degraded functions; knowledge-base searches (282 published articles) for offline, internet, network connection and store-and-forward return only device-down alerting (Cockpit) and this blocking flag. The sole contrary text is the KDS product page's marketing bullet 'Offline Functionality', which concerns the kitchen display, not order-taking, and is bounded at reliability-offline-kds-printing. https://help.grubbrr.com/s/article/How-to-Block-Kiosk-Ordering-when-the-Device-is-Offline · 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 named first-party product alongside order progress boards; bump-bar input and course/fire timing are not documented. https://www.grubbrr.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.
Integrations, API & extensibility
Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.
extensibility-public-api-docs
Upheld and now cited. GRUBBRR routes integration through a sales conversation rather than self-serve documentation -- after naming its supported POS platforms the FAQ says 'If you use a different provider, our sales team can discuss custom integration options.' No developer surface exists to read: developers., docs., developer. and apidocs.grubbrr.com do not resolve; /developers/, /developer/, /docs/, /api-docs/ and /swagger/ on the main host all return the WordPress 404 page, byte-identical to a fabricated control path. api.grubbrr.com is live but publishes nothing -- and it is a trap for a future pass, because any single-segment path under it (including /swagger and /openapi.json) 301s to the grubbrr.com marketing home page and so reads as HTTP 200 at 502,215 bytes, exactly as the fabricated control does, while its bare root and any deeper path return a 54-byte 404. `swagger` and `openapi` occur zero times across the full 549-document corpus; the word endpoint appears once, as part of a firewall hostname in a device-whitelisting guide. The API tokens the knowledge base does document are credentials GRUBBRR asks the merchant to mint in Clover, NCR or Olo so that GRUBBRR can consume those vendors' APIs -- not an API GRUBBRR exposes. The 'Open API' phrase on two marketing pages is a positioning claim with no reference behind it. https://grubbrr.com/faq/ · retrieved 2026-09-09
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
CLAIM: third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions, not shared static keys. VERDICT: partial/A - GRUBBRR publishes a partner authentication scheme with per-partner-device, rotating, individually disableable credentials bound to one location, but it is NOT OAuth 2.0 and has no permission scopes. EVIDENCE: 'GRUBBRR Partner Ordering API' (https://api.nge.grubbrr.com/swagger/partner-v1/swagger.json) info.description: "Partner-facing Ordering API for voice-AI and drive-through integrations ... Callers authenticate as a Partner Ordering device (JWT claim deviceType=ExternalDevice). Your GRUBBRR administrator provisions the device once and gives you a single-use enrollment code. Then: 1. Register - redeem the enrollment code at POST /auth/register to get the device's first refresh token. 2. Refresh - exchange the refresh token at POST /auth/refresh for a short-lived access token (this also rotates the refresh token, so persist the new one each time) ... Company and location always come from the access token - never the request body." POST /auth/register: "Returns 401 for an unknown or expired code, or one that has already been redeemed; 403 when the location is not licensed or the device has been disabled." POST /auth/refresh: "a fresh access token (valid 3 days) plus a rotated, single-use refresh token (valid 14 days)". SHORTFALLS: a custom enrollment/refresh-token flow, not OAuth 2.0; no scopes (a token reaches the whole partner API for its location); provisioning is by "your GRUBBRR administrator", with no operator consent screen documented. The OAuth2 authorizationCode scheme in the other two specs (Auth0 tenant prod-grubbrr-identity, scopes openid/profile/email) is first-party user sign-in, not partner grants. No app marketplace found. SURFACE (new, 2026-09-16): three ANONYMOUS OpenAPI 3.0.1 specs, found via the crt.sh certificate listing of %.grubbrr.com (202 names) plus /swagger probes: https://api.merchant.grubbrr.com/swagger/v1/swagger.json ('GRUBBRR.Web.UI', 170 paths, 221 schemas, 502 KB), https://api.nge.grubbrr.com/swagger/v1/swagger.json ('Grubbrr API', 86 paths, 271 schemas, 384 KB) and https://api.nge.grubbrr.com/swagger/partner-v1/swagger.json ('GRUBBRR Partner Ordering API', 20 operations, listed in the api.nge Swagger UI index). Each spec is a complete enumeration of ITS OWN API only; other GRUBBRR APIs exist but are not anonymous (sandbox.api.nge and test.api.ecm return 403; api.gem serves an Azure Functions placeholder; endpoint calls return 401), so the specs are not a platform census. Retrieved 2026-09-16. https://api.nge.grubbrr.com/swagger/partner-v1/swagger.json · retrieved 2026-09-16 adversarially verified
The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.
extensibility-webhooks-push
329th: NOW PUBLISHABLE AS NO. The publisher's OWN spec manifest is a census of what GRUBBRR publishes: https://api.nge.grubbrr.com/swagger/index.html enumerates exactly two spec groups ("urls":[{"url":"/swagger/v1/swagger.json","name":"Grubbrr API V1"},{"url":"/swagger/partner-v1/swagger.json","name":"GRUBBRR Partner Ordering API v1"}]) and https://api.merchant.grubbrr.com/swagger/index.html exactly one ([{"url":"/swagger/v1/swagger.json","name":"Grubbrr API V1"}]); all three fetched at 200 on 2026-09-18 at byte-identical sizes to the 318th (186,520 / 383,748 / 502,489 B, 276 paths, 61,129 tokens), and a nonsense group (/swagger/partner-v2/, /swagger/zzqnonsense/) 404s, so the manifest discriminates. The published order API states the mechanism affirmatively rather than merely omitting one: info.description "### Order lifecycle **validate -> submit -> poll status** ... POST /orders/submit accepts the order and returns 202 Accepted with status: PENDING before the POS confirms ... GET /orders/status/{sessionId} - poll until the order reaches a terminal SUBMITTED or FAILED state", and its own complete "Endpoints at a glance" table lists all 7 partner operations (auth/register, auth/refresh, menu, menu/availability, orders/validate, orders/submit, orders/status/{sessionId}) with no delivery/subscription endpoint among the spec's 20 paths. CONTROLS, tokenised over the 3 specs: callback*=1 (GET /api/clover/callback, a Clover OAuth redirect - poison), subscribe*=0, subscription*=1 (LocationSubscriptions, billing - poison), sse=0, websocket*=0, signalr=0, push*=2 (both "pusher", i.e. POST /api/pusher/auth channel auth for GRUBBRR's own UI), webhook*=10 and EVERY hit is POS-INBOUND or reflection poison: PosIntegrationDefinition.webhooksSupported / webhookIdField / webhookRecordName / webhookNextSyncTime, SnapshotSource enum "Unknown|ManualSync|Webhook|DailySync", and System.Reflection.EventAttributes/EventInfo/eventHandlerType (the .NET reflection graph, poison - it is why a naive event* count returns 7). CORROBORATION on two further complete censuses built this session. (1) console.grubbrr.com "GRUBBRR Enterprise Console" (SvelteKit): __vite__mapDeps in /_app/immutable/entry/app.BkIEgCT8.js lists 315 files, fetched to a fixpoint in 2 rounds = 324/324 at 200, 0 misses, 28.3 MB, 4,995,244 tokens; its 701 enumerated endpoints include /pusher, /pusher/auth, /pusher/user-auth, /xhr_send, /xhr_streaming (SockJS/Pusher for its own UI) and no webhook-subscription route; /PutEvents, /PutSubscribers, /PutSubscriptions, /GetEventsV3, /DownloadEventsV2 are the bundled AWS SDK (Amazon Connect/Pinpoint), poison. (2) portal.merchant.grubbrr.com (SMB Console, Angular): main.4f3429438223a423.js 7.03 MB + the runtime chunk table's only two lazy chunks (574.ba395f5895c16b04.js 423 KB, 919.62614f46a762bb5b.js 6 KB) = the whole app; its 3 webhook hits are one Clover setting whose tooltip reads "When webhook is turned on, when a change is made in clover, it will reflect immediately, both in SMB portal and in kiosk" - inbound. (3) The help.grubbrr.com KB (188 /articles/ in sitemap.xml today, 186 in the 316th; the 2 additions are 5304311009-ncr-faqs and 8772986526-how-to-link-your-square-and-grubbrr-accounts, both fetched) mentions webhooks in 11 articles and all 11 are GRUBBRR SUBSCRIBING to a POS's webhooks (Olo: "Webhook URL: https://staging.grubbrr.com/api/OloCallback"; Toast: "GRUBBRR receives automatic menu status updates from Toast via webhook"; Square: "Enable Process Webhook for Auto-Sync Menu"; NCR, Revel, Bruster's likewise) plus a glossary entry. So GRUBBRR consumes webhooks and publishes no outbound order-lifecycle push; integrators poll. Retrieved 2026-09-18. https://api.nge.grubbrr.com/swagger/partner-v1/swagger.json · retrieved 2026-09-18 adversarially verified
Webhooks are cryptographically signed (e.g. HMAC) AND documented to retry with backoff, with a replayable event log for missed deliveries. differentiator
extensibility-webhook-reliability
Not scored by this record.
A public write API accepts externally originated orders into the POS as first-class tickets that fire to KDS/printers and land in reporting.
extensibility-order-injection-api
Not scored by this record.
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
Order entry cannot continue on-terminal without the internet because the documented per-order sequence is cloud-mediated at every step: the kiosk menu 'pulls all its menu data... from the client's POS via the Internet'; when a guest submits, the kiosk 'submits an order total back to the Portal', which 'submits the order total back to the POS for verification'; payment happens only after the verified total returns; the final order then flows kiosk to Portal to POS, and 'the GRUBBRR Portal returns the final order ID to the Kiosk, and the Kiosk prints a receipt' — so check printing and ticket routing (via the POS back-of-house) both sit downstream of the cloud hand-off. The vendor's own offline provision confirms the stop rather than continuity: 'How to Block Kiosk Ordering when the Device is Offline' (v12.5+) has the kiosk 'display a pop-up to let customers know that the device can't connect to the internet, and to speak to location staff instead'. When the agent/POS link fails mid-order the customer-facing result is an error, not a queued ticket ('No connection could be made because the target machine actively refused it' — PixelPoint troubleshooting article). No article in the 282-article knowledge base documents local order caching, offline queueing or store-and-forward. https://help.grubbrr.com/s/article/Introduction-to-POS-Integrations · 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
The only positive evidence is a marketing bullet on the KDS product page, 'Offline Functionality', asserting the KDS continues to function if systems go offline. No documentation supports or bounds it: across 282 knowledge base articles 'offline' appears only as a device-down condition to alert on, and GRUBBRR's documented offline provision runs the other way — 'How to Block Kiosk Ordering when the Device is Offline' has the kiosk display a pop-up telling customers to speak to staff instead. Order flow is cloud-mediated (kiosk to GRUBBRR to POS via the GRUBBRR Agent), and nothing states what is cached locally, for how long, or whether kitchen printer routing survives a WAN outage. Grade D because a product-page bullet is a claim, not a fact. https://grubbrr.com/products/kitchen-display-system/ · retrieved 2026-08-03
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
The alerting half of the claim is documented and specific: with 'Send Device Status Email from Cockpit' enabled, named recipients 'receive email updates within fifteen minutes of your Kiosks, printers, payment devices, or GRUBBRR agents experiencing changes in their status, such as running out of paper or losing internet connectivity', and the Console's System Health page flags devices as operational, 'partially up', in error or offline. Shortfall: no automatic failover. 'How to Manage Kitchens in the GRUBBRR Portal' assigns each kitchen one printer and/or one KDS with items mapped to it, and offers redundancy only as a manual configuration choice — print KOTs, use a KDS, or do both simultaneously. No article describes rerouting to a backup printer or KDS station when the configured device is unreachable. https://help.grubbrr.com/s/article/How-to-Get-Automated-Device-Status-Updates-from-the-GRUBBRR-Portal · retrieved 2026-08-03
The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).
reliability-sync-conflict-handling
Not scored by this record.
The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).
reliability-offline-feature-matrix
Not scored by this record.
A public, per-component status page exists showing current and historical incident state without a login.
reliability-public-status-page
Not scored by this record.
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
GRUBBRR's public General Terms (effective March 3, 2023) section 9.3.2: "Unless otherwise set forth in an Order, the initial subscription term shall be 36 months from (i) the Order date or (ii) in the event of a Pilot, from the day immediately following the expiration of the Pilot ... Thereafter, the Order will automatically renew for successive 12-month periods ... unless either Party gives the other Party written notice at least 30 days prior to the expiration of the Initial Subscription Term or the then-current Renewal Subscription Term." Term, auto-renewal period and the 30-day cancellation-notice window are all published, not confined to a signed quote. https://grubbrr.com/general-terms/ · retrieved 2026-08-08
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
No general price list: grubbrr.com/pricing/ now redirects to /request-a-demo/, and /faq/, /grubbrr-guarantee/ and the product pages carry no dollar figures. But GRUBBRR does publish specific figures on its open, sitemap-listed brand order-form pages - the Dave's Hot Chicken franchisee page prints a "Kiosk Pricing" table: "Samsung Countertop Kiosk with Verifone P400 $500", "Kiosk Floor Stand $500", "Kiosk Wall Mount $500", "Setup & Installation $500", and "Kiosk SaaS per Month $150 / Two kiosks per location". Shortfall: this is one negotiated franchise program, not list pricing for the general buyer, and no per-additional-terminal software rate is given (the $150 covers two kiosks; the order form accepts 2 or 3 with no incremental figure). The parallel Bojangles, Church's, Pita Pit, Ziggi's, Boar's Head and NCR Voyix reseller order forms publish no figures at all. https://grubbrr.com/daves-hot-chicken-franchisee/ · retrieved 2026-08-08
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
Outright purchase is a documented, standard route, not a forced lease. General Terms 1.8: "'Hardware' means the kiosks, displays, printers, cables, or other hardware or equipment, specified on an applicable Order ... Hardware purchased hereunder is resold to You by GRUBBRR." Schedule 1 - Hardware governs it: "The terms in this Schedule 1 apply to Your purchase of Hardware pursuant to an Order", headed "DELIVERY, INSTALLATION, TITLE AND RISK OF LOSS", with "Hardware fees and shipping costs are due upon execution of the Order" and OEM warranties passed through. Leasing is a separate, elective Offering - 1.9 defines HaaS as "the provision of Hardware for use on a subscription basis", and only under HaaS does "At no time during the Subscription Term shall title to the Hardware pass to You ... You shall not have any right to purchase the Hardware" apply. Shortfall: prices are barely published. The only first-party figures are on one franchise order form (Dave's Hot Chicken franchisee page, retrieved 2026-08-08): "Samsung Countertop Kiosk with Verifone P400 $500", "Kiosk Floor Stand $500", "Kiosk Wall Mount $500", "Setup & Installation $500". No KDS-screen or printer price appears anywhere, grubbrr.com/pricing/ redirects to /request-a-demo/, and the parallel Bojangles, Church's, Pita Pit, Ziggi's and Boar's Head order forms print no figures at all. https://grubbrr.com/general-terms/ · retrieved 2026-08-08
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 13 values — 8 upheld, 0 downgraded, 5 upgraded. It separately resolved 19 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 |
|---|---|---|---|
| menu-pricing-modifier-price-by-parent-size | unknown (grade F) — placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-no | The knowledge base documents exactly two ways to price a modifier and neither is a parent-by-size matrix. Common Modifiers carry one shared 'Extra Price' per ingredient and are then bulk-mapped to items ('How to Edit Modifier Prices in the GRUBBRR Portal' + 'Building your First Menu #10'), so the price is identical on every parent. The documented way to get a different price on a different parent is this article's route: build a separate modifier group under the individual item, where 'you can also add upcharges for specific modifiers in this table' — i.e. duplication, which the claim explicitly excludes. Size is a separate construct entirely ('Intro to Variation Modifiers': one variation group per item, each option carrying its own additive price) and does not intersect modifier pricing. For POS-integrated menus GRUBBRR does not set modifier prices at all. source |
| menu-pricing-topping-quantity-tiers | unknown (grade F) — placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-partial | Quantity/style tiers exist only as NCR modifier codes: 'codes- such as "no," "light," "extra," or "on the side"- can be selected by customers at the kiosk and will be printed on the KOT'. Shortfalls, all stated by the article: the feature is NCR-integration-only; 'GRUBBRR can not add or remove modifier codes from the Portal... All modifier codes must be defined in the client's POS before we pull the menu'; a maximum of four active codes per ingredient with one mandatory default; and no per-tier price multiplier is documented anywhere — the codes are described purely as prefixes sent to the kitchen printer. GRUBBRR's own quantity mechanism ('How to Enable Aggregate Mode for High Volume Modifiers', with Choice Increment and min/max aggregate quantities) is repeat-selection counting, which the claim distinguishes from tiering. source |
| payments-refund-void-controls | unknown (grade F) — placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-partial | Refunds are documented and reasonably rich — Refund By Item, Refund by Amount and Full Refund from Orders > Detailed Orders, and the same full/partial refund flow from the Enterprise Console's Order History. Shortfalls: the control is back-office sign-in plus a Portal role privilege, not a manager PIN or approval prompt at the point of sale; no article describes an immutable audit log identifying the approver of a refund; and voids, comps and no-sales have no equivalent flow because there is no register or cash drawer. The article also warns the refund runs through a GRUBBRR virtual terminal and 'will not appear in your POS records'. source |
| kitchen-expo-consolidation | unknown (grade F) — placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-partial | An expediter role exists as a distinct device: the OPB Order Update Flow configures four separate triggers — 'Completing an Order on the KDS', 'Completing an Order on the Expediter KDS', 'Highlighting an Order on the KDS' and 'Highlighting an Order on the Expediter' — each of which can move an order to Ready for Pickup or Picked Up. Combined with kitchen mapping ('How to Manage Kitchens in the GRUBBRR Portal': items are sent to a specific kitchen or all kitchens, each with its own printer and/or KDS). Shortfall: nothing in the knowledge base describes the expediter screen consolidating items from multiple prep stations into one order view, or gating order completion until every contributing station has bumped its items; the documented completion trigger is a single action on the expediter. source |
| digital-account-saved-payment | unknown (grade F) — placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-partial | One-tap reorder is present and is a default of the loyalty flow: a signed-in guest sees 'their past five Kiosk orders from any of your locations' and selecting an item 'will automatically apply all of the same customizations from the customer's past order'. Version 14 added the same flow for non-loyalty guests via a guest sign-in. Shortfalls: no tokenized saved card is documented anywhere — the only account-based payment methods in the knowledge base are ID Pay / Member Pay, prepaid monthly-allowance accounts keyed to a member ID or scanned ID card, and house accounts; and no saved-address concept exists, consistent with there being no first-party delivery. source |
| guest-loyalty-unified-profile | unknown (grade F) — placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-partial | A guest identity does span locations: signing in to loyalty on the kiosk surfaces 'their past five Kiosk orders from any of your locations', and GRUBBRR ships an in-house 'Frequent Customer' feature alongside third-party providers (Punchh, Como, Bruster's, OloPunchh). Shortfalls: the documented history is explicitly kiosk orders only and capped at five, with nothing describing merge of in-store POS or first-party web/app transactions into the same profile; identity is held by the loyalty provider, with GRUBBRR configuring only login method (QR, phone or email), points display and redemption; and no dedup/merge behaviour is documented in any article. source |
| guest-loyalty-lifecycle-automation | unknown (grade F) — placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-no | GRUBBRR does not ship campaign automation; it configures somebody else's loyalty engine. This article enumerates the entire loyalty surface GRUBBRR exposes — provider enablement, Punchh location/business keys, receipt features, redemption modes (scan-and-redeem, visit-based), maximum rewards per order, guest check codes, login method and display strings — and campaigns are not among them; the only lifecycle-adjacent item is a flag asking Punchh to collect date of birth and gender. Across all 282 articles the words 'campaign', 'birthday' (outside that flag) and 'win-back' do not appear. GRUBBRR's own CRM module is Members (prepaid ID Pay accounts) and guest surveys; its only guest messaging is on-screen behaviour-based messages and Toast-sourced order-ready SMS. source |
| labor-granular-rbac | unknown (grade F) — placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-partial | Roles are genuinely custom rather than fixed tiers: Users > Role Master > Add New, then 'privileges' to 'Grant the user access to the required features/settings', and 'we give users access to the company or location level'. Temporary users can additionally carry a start and end date. Shortfalls: the privilege set governs GRUBBRR Portal features and settings, not register actions — void, comp, drawer-open and price-change have no equivalent because there is no terminal or cash drawer; scoping is documented at two levels (company or location), not per location group; and the actual list of grantable privileges is published only as a screenshot inside the article, so the granularity cannot be verified from text. source |
| reporting-realtime-dashboard | unknown (grade F) — placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-partial | Browser dashboards exist at both levels — a Company Dashboard tracking KPIs across all active locations plus a Location Dashboard with Sales, Item Mix, Payment Types and a KPI panel ('Introduction to the GRUBBRR Portal Dashboard'), and the Console's 'At a Glance' dashboard with Sales, Upsells, Device Health, Aborted Orders and Store Performance tiles. Shortfall on latency, stated by the vendor: 'This dashboard updates at 6 AM, 10 AM, 2PM, 6PM and 10PM Eastern Time every day' — five refreshes a day, not within minutes of the sale. The Portal dashboard's refresh cadence is not stated anywhere, and device telemetry is separately documented as heartbeat-based with up to a 15-minute lag. Second shortfall: no mobile app is documented for either console; every reporting article routes through a browser sign-in. source |
| reporting-pmix-modifier-level | unknown (grade F) — placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-partial | A Product Mix report exists under Reports > Sales > Product Mix and 'will show the assortment of items sold for a specifically selected date filter... can also be refined to show items from a specific category'. Shortfalls: the documented breakdown is item-level with a category filter only — no modifier-level line, and no daypart or revenue-centre filter; the article does not state which measures the report carries (the quantity/gross/net breakdown the claim asks for is described for the Z Report, not for Product Mix). The Console's separate 'Products' insight page likewise 'tracks the performance of individual menu items' with no modifier dimension. source |
| multi-location-org-hierarchy | unknown (grade F) — placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-partial | More than a flat list: the Console has a Scope tool switching between Enterprise and Location views, an Organizations object administered under Support > Organizations & Users, and a grouping layer above the store that reporting uses — 'Store Performance provides a detailed breakdown of the active location against other locations in the organization/location group' — with a 'Location Group ID' issued by GRUBBRR Operations during Clover Sport setup. Shortfalls: the group tier is never documented as an operator-manageable object (no article covers creating or editing a location group), and permissions do not scope to it — 'How to manage Users & Roles' places user access at 'the company or location level' only, so the third level exists for analytics but not for permission grants. source |
| multi-location-central-menu-publish | unknown (grade F) — placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-partial | Enterprise Configuration Management is real central authoring: a Master Menu Dataset built from all onboarded POS menus, custom datasets defining which categories/items each cohort offers, a parallel Master Kiosk settings dataset, and deployment jobs where 'we can assign which locations will be included, which datasets to share, and when to apply the changes', clonable for later updates. Shortfalls named by the vendor: 'With ECM, we don't have a one-button "push to Kiosk" option; instead, we set up custom deployments' — publishing is a configured job, not a single action; and no publish/version history recording what was pushed, when and by whom is documented for deployments (the 'Menu Audits' and GEM user-event tracking in the v15 notes cover menu record changes, not deployment runs). source |
| multi-location-price-zones | unknown (grade F) — placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-no | The docs enumerate what is authored centrally and price is deliberately excluded: 'Categories, Items, Modifier Groups, Modifiers, Combos, Upsells, and Discounts are all configured at the Company level. Menu Prices, Item 86 Status, General settings, and Kiosk settings are all configured at the Location level', and 'All menu prices are still defined at the location level.' The ECM path says the same — 'When an organization uses ECM controls, prices are managed by the POS at each individual location' — and the v14.6 enhancement was only the ability to view location pricing from the enterprise menu manager, not set it. There is therefore no price tier/zone object: differential pricing is inherited from each store's POS, and no per-channel or per-daypart price variant is documented either. source |
| reliability-offline-kds-printing | unknown (grade F) — placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-partial | The only positive evidence is a marketing bullet on the KDS product page, 'Offline Functionality', asserting the KDS continues to function if systems go offline. No documentation supports or bounds it: across 282 knowledge base articles 'offline' appears only as a device-down condition to alert on, and GRUBBRR's documented offline provision runs the other way — 'How to Block Kiosk Ordering when the Device is Offline' has the kiosk display a pop-up telling customers to speak to staff instead. Order flow is cloud-mediated (kiosk to GRUBBRR to POS via the GRUBBRR Agent), and nothing states what is cached locally, for how long, or whether kitchen printer routing survives a WAN outage. Grade D because a product-page bullet is a claim, not a fact. source |
| reliability-printer-fallback | unknown (grade F) — placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-partial | The alerting half of the claim is documented and specific: with 'Send Device Status Email from Cockpit' enabled, named recipients 'receive email updates within fifteen minutes of your Kiosks, printers, payment devices, or GRUBBRR agents experiencing changes in their status, such as running out of paper or losing internet connectivity', and the Console's System Health page flags devices as operational, 'partially up', in error or offline. Shortfall: no automatic failover. 'How to Manage Kitchens in the GRUBBRR Portal' assigns each kitchen one printer and/or one KDS with items mapped to it, and offers redundancy only as a manual configuration choice — print KOTs, use a KDS, or do both simultaneously. No article describes rerouting to a backup printer or KDS station when the configured device is unreachable. source |
| payments-gift-cards | unknown (grade F) - placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-partial | Swept all 282 articles in the GRUBBRR knowledge base for 'gift'; three articles match. Redemption is documented only as a third-party integration in the v14 release notes' Payments section: 'Paytronix Giftcard - Users must enter the Gift Card Number on the Kiosk to redeem their balance'. Sale is a location-level toggle, 'Allow Purchase of Gifts Cards using Kiosk' (Common Kiosk Configurations). The v14 beta notes mention 'gift card and stored value screens' only in a kiosk-timeout bugfix. Shortfalls that hold this below yes: no first-party issuance or balance ledger is documented - the balance lives in Paytronix and is read by keying the card number; no cross-location redemption scope is stated; and no online-ordering-channel gift card flow exists in the docs. Not 'no', because a working purchase-and-redeem path is positively documented. source |
| hardware-offline-mode | unknown (grade F) - placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-no | The vendor's own help centre states the offline behaviour and it is a stop, not a degraded mode: 'How to Block Kiosk Ordering when the Device is Offline' (v12.5+) blocks orders and shows 'a pop-up to let customers know that the device can't connect to the internet, and to speak to location staff instead'; its summary says 'the Kiosk will automatically direct customers to the POS if the device is offline'. 'Introduction to POS Integrations' documents why nothing can continue: every order round-trips the cloud mid-transaction (order total to Portal, 'the Portal submits the order total back to the POS for verification', payment only after the verified total returns, receipt only after the Portal returns the POS Order ID). No article documents offline capture, offline cash recording, or an enumerated degraded-functions list; KB searches (offline, internet, network connection, store and forward) across the 282 published articles return only device-down alerting and this blocking flag. The KDS product page's 'Offline Functionality' marketing bullet concerns the kitchen display only and is already bounded at reliability-offline-kds-printing. source |
| reliability-offline-order-entry | unknown (grade F) - placeholder rationale 'No public documentation located during the 2026-08-01 research pass', which recorded that the cell was never examined rather than a finding of absence. | resolve-to-no | The documented per-order data flow is cloud-mediated at every step: menu data 'pulls... from the client's POS via the Internet'; the kiosk 'submits an order total back to the Portal'; 'the Portal submits the order total back to the POS for verification'; payment is taken only after the verified total returns; and 'the GRUBBRR Portal returns the final order ID to the Kiosk, and the Kiosk prints a receipt' - check printing and ticket routing both sit downstream of the cloud hand-off. The vendor's documented offline provision is to stop ordering ('Block Kiosk when Offline' pop-up directing guests to staff), and the documented mid-order failure mode when the POS link drops is a customer-facing error ('No connection could be made because the target machine actively refused it', PixelPoint troubleshooting). No article documents local caching, offline queueing or store-and-forward. Positive evidence of absence per the evidence rules: the vendor's own support pages state the limitation and enumerate the alternative (send guests to staff/POS). source |
| commercial-autorenew-terms-published | no, grade B - No contract terms, renewal term or cancellation-notice windo | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| commercial-pricing-published | no, grade B - The vendor's own pricing page publishes no subscription tier | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| commercial-autorenew-terms-published | no, grade C - No contract terms, renewal term or cancellation-notice window is publicly acc | upgrade-to-yes | The cited https://www.grubbrr.com/pricing/ now redirects to https://grubbrr.com/request-a-demo/, a demo booking form with no terms and no figures, so the original basis is gone. Walking grubbrr.com/page-sitemap.xml surfaced /general-terms/ (200, full contract text, last updated March 3rd 2023) alongside /kiosk-eula/ and an archived copy at /general-terms/archive/. Section 9.3.2 states a 36-month initial subscription term, automatic renewal for successive 12-month periods, and written notice at least 30 days before expiry of the initial or then-current renewal term. That is exactly what the claim asks for, published on the open web, so the no does not survive. source |
| commercial-pricing-published | no, grade C - The vendor's own pricing page publishes no subscription tiers, hardware costs | upgrade-to-partial | Re-fetched the cited URL: https://www.grubbrr.com/pricing/ 301s to https://grubbrr.com/request-a-demo/, a lead form, so the original evidence is dead. Enumerated grubbrr.com/page-sitemap.xml (68 pages) and fetched every candidate. /request-a-demo/, /faq/, /grubbrr-guarantee/ and /products/self-ordering-kiosk-machine/ contain no dollar amounts; the Bojangles, Church's, Pita Pit, Ziggi's, Boar's Head, Dairy Queen Texas and NCR Voyix reseller order forms contain none either. /daves-hot-chicken-franchisee/ does: hardware and installation at $500 per line item and "Kiosk SaaS per Month $150 - Two kiosks per location". Specific per-location software pricing is published on the vendor's public site, which defeats a flat no, but there is no general price list and no per-additional-terminal figure, so partial is the honest value. source |
| commercial-hardware-purchase-outright | unknown / F - "Kiosk hardware is clearly sold or placed, but no prices and no purchase-vs-lease t | resolve-to-partial | The rationale predates the discovery of grubbrr.com/general-terms/ via page-sitemap.xml. I retrieved the General Terms in full: 1.8 states "Hardware purchased hereunder is resold to You by GRUBBRR" and Schedule 1 applies expressly to "Your purchase of Hardware pursuant to an Order", covering delivery FOB Shipping Point, title and risk of loss, fees due on execution, and pass-through OEM warranty - so purchase-vs-lease terms ARE published and purchase is the default route. The lease alternative is separate and optional: HaaS is defined at 1.9 as subscription provision, and its no-title/no-right-to-purchase language sits only in that schedule. Not a full yes, because published prices remain thin - the sole first-party figures are on the Dave's Hot Chicken franchisee order form ($500 kiosk, $500 stand or wall mount, $500 setup and installation), with no KDS or printer pricing and no general list price. source |
| order-capture-split-merge | no (grade F), uncited: GRUBBRR has no POS product, so check splitting and merging were said to remain in the integrated POS. | upgrade-to-partial | GRUBBRR publishes the opposite claim in its own prose, and a knowledge-base release note records a partial-payment fix, so a split path exists. Held below yes because no split mode and no merge is documented anywhere in 549 documents. source |
| delivery-driver-roster | no (grade F), uncited: no driver or dispatch module in the published catalog. | upheld | Now bounded rather than asserted: driver, dispatch and courier each occur zero times across all 283 knowledge-base articles, the nine-product catalogue holds no driver module, and integrated orders are finalised through the merchant POS. source |
| delivery-dispatch-board | no (grade F), uncited: absent from the published catalog. | upheld | The two order-status screens GRUBBRR does ship, the KDS and the Order Progress Board, are prep-and-pickup displays. dispatch occurs zero times in the knowledge base; its only corpus occurrence is the EULA sense of sending an e-mail. source |
| labor-clock-in-at-pos | no (grade F), uncited: no POS terminal and no labor module. | upgrade-to-partial | The second half was wrong. GRUBBRR has Employee Management with per-employee 4-digit access codes used to log in and out of devices, and its Z Report carries an Employee Attendance section listing employee shifts and hours. No clock-in or clock-out procedure is documented and GRUBBRR ships no POS terminal of its own, so partial rather than yes. source |
| inventory-recipe-bom-costing | no (grade F), uncited: no inventory or recipe-costing module in the published catalog. | upheld | The premise was false -- an inventory module is published -- but the verdict survives on better evidence: the module tracks finished menu items only, and recipe occurs zero times across all 283 knowledge-base articles. GRUBBRR uses Ingredient to mean a terminal modifier, not a stocked material. source |
| inventory-unit-conversion-yields | no (grade F), uncited: no inventory module in the published catalog. | upheld | Premise false, verdict survives: stock is one undimensioned integer per item in the Ready Item Stock screen. unit of measure, par level and yield each occur zero times across the knowledge base. source |
| inventory-count-modes | no (grade F), uncited: no inventory module in the published catalog. | upheld | Premise false, verdict survives: the only documented adjustment is a typed delta into Add Current Stock plus automatic depletion on sale. No count session, no variance and no retained history; cycle count and stock count are zero across the knowledge base. source |
| reporting-eod-closeout | no (grade F), uncited: no cash drawer or tender reconciliation, EOD left to the integrated POS. | upgrade-to-yes | Directly contradicted. GRUBBRR publishes a Z Report covering gross and net sales, tax, tips and gratuity, discounts, refunds and voids, tender types, and a Cash Management Summary including variance, in one document, with a configurable business-day cut-off for locations trading past midnight. source |
| extensibility-public-api-docs | no (grade F), uncited: no public developer portal or API reference on grubbrr.com. | upheld | Now probed rather than asserted: no developer or docs subdomain resolves, every documentation path on the main host returns the WordPress 404 byte-identical to a fabricated control, and api.grubbrr.com is a redirect-to-homepage catch-all for single-segment paths that would read as a false 200 to any future pass. swagger and openapi are zero across 549 documents, and the FAQ routes non-listed POS platforms to a sales conversation. source |
Sources
Every URL this record cites. 46 in total.
- https://www.grubbrr.com/
- https://www.grubbrr.com/pricing/
- https://help.grubbrr.com/services/data/v59.0/support/knowledgeArticles
- https://help.grubbrr.com/s/article/How-to-manage-Users-Roles-in-the-GRUBBRR-Portal
- https://help.grubbrr.com/s/article/How-to-Refund-Kiosk-Orders-through-the-GRUBBRR-Portal
- https://help.grubbrr.com/s/article/How-to-Access-Basic-Reports-in-the-GRUBBRR-Portal
- https://help.grubbrr.com/s/article/Using-GRUBBRR-Analytics
- https://help.grubbrr.com/s/article/Introduction-to-the-GRUBBRR-Portal-Dashboard
- https://help.grubbrr.com/s/article/ECM-Functions-Best-Practices
- https://help.grubbrr.com/s/article/How-Company-Level-Menu-Management-works-with-POS-Integrations
- https://help.grubbrr.com/s/article/How-to-Check-Item-Prices-across-Locations
- https://help.grubbrr.com/s/article/How-to-apply-NCR-Modifier-Codes-in-the-GRUBBRR-Portal
- https://help.grubbrr.com/s/article/Building-your-First-Menu-11-Mapping-Modifiers-to-a-Single-Item
- https://help.grubbrr.com/s/article/How-to-Edit-Modifier-Prices-in-the-GRUBBRR-Portal
- https://help.grubbrr.com/s/article/Intro-to-Variation-Modifiers-in-the-GRUBBRR-Portal
- https://help.grubbrr.com/s/article/How-to-Manage-Kitchens-in-the-GRUBBRR-Portal
- https://help.grubbrr.com/s/article/How-to-Link-a-KDS-to-the-GRUBBRR-Portal
- https://help.grubbrr.com/s/article/Common-Order-Progress-Board-Configurations-in-the-GRUBBRR-portal
- https://help.grubbrr.com/s/article/How-to-Get-Automated-Device-Status-Updates-from-the-GRUBBRR-Portal
- https://help.grubbrr.com/s/article/How-to-Block-Kiosk-Ordering-when-the-Device-is-Offline
- https://help.grubbrr.com/s/article/How-Past-Orders-Works-With-Loyalty-or-with-GRUBBRR-Frequent-Customer
- https://help.grubbrr.com/s/article/How-to-Set-Up-Punchh-in-the-GRUBBRR-Console
- https://help.grubbrr.com/s/article/How-to-Enable-ID-Pay-in-the-GRUBBRR-Portal
- https://help.grubbrr.com/s/article/How-to-Subscribe-to-GRUBBRR-Webhooks-in-Olo
- https://help.grubbrr.com/s/article/How-to-Create-API-Tokens-in-the-Clover-Admin-Portal
- https://help.grubbrr.com/s/article/How-to-link-your-Square-and-GRUBBRR-Accounts
- https://help.grubbrr.com/s/article/How-to-use-Advanced-Ordering-Options-in-the-GRUBBRR-Console
- https://help.grubbrr.com/s/article/Version-15-Beta-Deployment-Notes
- https://help.grubbrr.com/s/article/How-to-use-GRUBBRR-System-Health-Monitoring
- https://help.grubbrr.com/s/article/GRUBBRR-Hardware-Compatibility-Matrix
- https://grubbrr.com/products/kitchen-display-system/
- https://help.grubbrr.com/s/article/Version-14-Limited-Release-notes
- https://help.grubbrr.com/s/article/Common-Kiosk-Configurations-in-the-GRUBBRR-Portal
- https://help.grubbrr.com/s/article/Introduction-to-POS-Integrations
- https://help.grubbrr.com/s/article/How-to-Troubleshoot-No-Connection-could-be-made-Errors-During-Kiosk-Orders
- https://grubbrr.com/general-terms/
- https://grubbrr.com/daves-hot-chicken-franchisee/
- https://grubbrr.com/page-sitemap.xml
- https://grubbrr.com/faq/
- https://grubbrr.com/products/
- https://grubbrr.com/grubbrr-software-integration/
- https://help.grubbrr.com/s/article/How-to-Find-Edit-Access-Codes-for-the-Kiosk-in-the-GRUBBRR-Portal
- https://help.grubbrr.com/s/article/How-to-use-Inventory-Tracking-in-the-GRUBBRR-Portal
- https://help.grubbrr.com/s/article/How-to-Manually-Update-your-Item-Inventory-in-the-GRUBBRR-Portal
- https://help.grubbrr.com/s/article/How-to-Enable-Inventory-Tracking-in-the-GRUBBRR-Portal
- https://help.grubbrr.com/s/article/Intro-to-Nested-Modifiers-in-the-GRUBBRR-Portal