Vendors / QSR & drive-thru
Bite
Bite (getbite.com)
Guest-ordering layer that rides on someone else's POS, shipping five first-party channels its own API enumerates — kiosk, Linebuster handheld, Flash (contactless QR), web (Online Ordering Website) and catering — each branded by the operator. It holds no tender, kitchen, labor or inventory system of record; it is not a POS, and it is a different company from Bite Ninja.
scored unknown legacy rubric
- Claims in scope
- 296
- Scored
- 44
- Assessed
- 44
- Unknown
- 252
- Not applicable
- 18
- Values challenged
- 2
unknown, never as no.Identity
- Owner
- Bite Technologies, Inc. — private US company; no parent or investor disclosed on the site. NOTE: unrelated to Bite Ninja despite the brief pairing them.
- Who it is for
- QSR and fast-casual operators buying self-order kiosks and mobile line-busting to run alongside an existing POS (PAR, Olo named as partners)
- Site
- https://getbite.com/
Pricing
transparency: quote-only · unit: unknown (quote-only) · processor lock-in: unknown
- Software
- No pricing published anywhere on getbite.com; demo/quote only.
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
Bite's published order model is atomic and single-tender: the Close Order endpoint 'Closes a fully paid order so that it can be sent to the kitchen for fulfillment', so an order leaves Bite only once it is paid in full. The v2 schema set (167 named schemas) carries no check, seat, split or merge object - Order holds one OrderedItem list, one SubTotal/DiscountTotal/TaxTotal/ServiceChargeTotal/TipTotal/Total block and a single TableNumber - and the words split, seat, merge and 'separate check' occur zero times across the OpenAPI bundle, the 187-article help centre and the 28-page marketing site, on a matcher proved in the same run by kiosk 511 / refund 62 / modifier 114 hits. Splitting by item, seat, even N-way or arbitrary amount, and merging after partial payment, are all absent; a self-order kiosk takes one guest's order and tenders it whole. https://documentation.getbite.com/openapi/v2/bite-api-v2 · retrieved 2026-09-08
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
Kiosks cannot take orders without connectivity: the support page's causes for 'Kiosk is unable to place an order' are 'Internet Blip... please re-try sending the order', unplugged cables/modem, 'Internet down', a firewall 'blocking our connection to the kiosk', and 'POS connection down or interrupted'. The offline-kiosk articles (Elo, Esper) treat an offline kiosk purely as a fault to repair (reconnect, whitelist, factory reset), no offline ordering scope is published anywhere in the help centre, and kiosks tender no cash. Every element of the claim - offline order creation, offline kitchen send, cash tender, published offline scope - is absent. https://getbite.zendesk.com/hc/en-us/articles/360036891332-Kiosk-unable-to-place-Order · retrieved 2026-08-04
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
Future-dated ordering exists as a location feature: guests at 'locations that have future orders enabled' pick pickup time slots and can change them mid-order (unavailable slots grey out); Order Throttling caps 'the volume OR number of orders that can be placed at given time windows' per dining option in 10/15-minute or whole-interval buckets ('ASAP orders will never be throttled'); Order Lead Times rules bump the quoted prep tier (ASAP/30/45/60 min) by items-in-cart per menu section; and a 'Future Orders' report 'shows all pre-orders coming up'. Shortfall: lead-time rules are per location and menu section, not per channel, and nothing documents Bite holding a future order and injecting it into the make queue at a computed fire time - Bite hands orders to the host POS, and kitchen routing 'is controlled entirely by your POS and KDS configuration—not by Bite', so fire-at-time behaviour belongs to the connected POS. https://getbite.zendesk.com/hc/en-us/articles/360060759151-Changing-Dining-Option-or-Pickup-Time-Mid-Order · retrieved 2026-08-04
Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.
order-capture-catering
Not scored by this record.
Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator
order-capture-order-ready-signal
Not scored by this record.
Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.
order-capture-void-comp-controls
Not scored by this record.
Menu, modifiers & pricing engine
Payments & money movement
The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator
payments-processor-choice
Not scored by this record.
Vendor publishes card-processing pricing publicly (a specific flat rate or interchange-plus markup) rather than quote-only. differentiator
payments-published-rates
Not scored by this record.
Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator
payments-dual-pricing
Not scored by this record.
Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator
payments-surcharge-guardrails
Not scored by this record.
All first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay.
payments-emv-nfc
CLAIM: all first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay. SHORTFALLS, numbered. (1) Bite ships no payment terminal of its own; acceptance is delivered by a third-party pinpad and a gateway the operator procures, so 'all first-party terminals' cannot be asserted uniformly. (2) Apple Pay is never named anywhere in either Bite corpus - 0 hits across 187 help-centre articles and 0 hits across all 166,656 bytes of the OpenAPI spec (I ran the token 'Apple' over the spec myself: zero). MET (1) EMV is a mandatory line item in Bite's own kiosk bills of material: 'EMV Cradle for Ingenico iPP320/350/315 - Elo P/N: E699053' appears for every stand option, 'Note - EMV may require a separate mount', and the network switch and power strip are budgeted with '1x EMV terminal' (this url, Support / Kiosk & Device Setup and Troubleshooting); the 22-inch guide repeats it (https://getbite.zendesk.com/hc/en-us/articles/360036941391-Elo-22-Setup). MET (2) CONTACTLESS AND GOOGLE PAY: Bite's order webhook sample carries a transactions array with 'gateway: "Worldpay", cardEntryMethod: "Contactless"' (https://getbite.zendesk.com/hc/en-us/articles/13433960302868-Bite-order-webhooks-for-operators), and the OpenAPI spec documents the field generically - 'cardEntryMethod: The method used to used the card during the transaction. ex: Swipe, Google Pay'. Note the grade of that evidence honestly: cardEntryMethod is a free-form string with an example, not an enum, so it records that a Google Pay tap is a recognised entry method on a Bite order rather than declaring a supported tender list. CORRECTION I AM ADDING TO THE PRIOR PASS, AND IT IS THE HYPHEN TRAP IN REVERSE: a control written as 'tap to pay' returns 0, but 'tap-to-pay' returns 1 and it is substantive - 'Partial Download: Used for applying updated setting to the device (enable tap-to-pay, for example)' in 'Heartland Lane 3000/5000: How to Perform Partial or Full Download' (https://getbite.zendesk.com/hc/en-us/articles/29371179876628, Support / Kiosk & Device Setup and Troubleshooting, 2026-03-09). Bite documents enabling contactless acceptance on the operator's pinpad. Run the spaced AND hyphenated forms. GATEWAYS: Worldpay, Heartland, CardConnect, Verifone Pointe and FreedomPay are named across 13 articles (68 hits), and Bite documents a gateway-level limit - 'debit refunds are not supported for WorldPay and FreedomPay Canada due to system limitations' (https://getbite.zendesk.com/hc/en-us/articles/42423872875412-Refunds). THE BIG POISON: NFC|contactless|tap to pay returns 11 hits in 7 articles and 5 of the 7 use 'contactless' as the NAME OF A BITE ORDERING CHANNEL, not a card entry method - 'available on both kiosks and contactless', 'the kiosk/contactless solution would be in the off state'. The spec settles the homonym: the OrderChannel enum comment reads 'flash - Contactless (QR-code)'. Counting 'contactless' naively manufactures a yes. NFC alone = 0 in both corpora. PDF HAZARD MEASURED PER DOCUMENT, INVARIANCE PUBLISHED: the one payment-bearing attachment, Ingenico-Lane-3000_World_Pay_setup.pdf (516,992 bytes, attached to 'WorldPay activation code missing'), was extracted three ways - pdftotext -layout (8,168 chars), plain pdftotext (6,187 chars), and a whitespace-squashed normalisation of each. EMV, NFC, contactless, Apple, Google, tap, chip and swipe all read 0 under every probe and the counts are INVARIANT between extraction modes, so the file genuinely carries no payment-type detail (it is a cabling and static-IP guide) and neither supports nor rebuts the cell. The squashed probe does carry poison in the other direction - it scores 'lease' 4 and 'rent' 2 on this PDF, both artefacts of joining across whitespace - so trust the tokenised figure, not the squashed one. Positive controls: Bite 450/133, order 251/45, the 3,537/181; all control scripts were written to disk, never inlined in a shell. BOUND CORPUS AND ITS HOLE, WHICH IS WHY THIS IS NOT A ZERO: href fixpoint re-derived - 28 referenced ids, 12 absent, 0 unlisted published 200s, 5 gated 401s, 7 stale 404s, three fabricated 14-digit controls all 404. All five gated articles sit in Support / Kiosk & Device Setup and Troubleshooting, the SAME section as the payment-hardware BOMs, so no absolute zero about Bite's payment hardware is publishable from this corpus. 541 attachments, 3 non-image. 0 iframes in 187 raw bodies. https://getbite.zendesk.com/hc/en-us/articles/360036196252-Elo-15-Setup · retrieved 2026-09-15 adversarially verified
Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. differentiator
payments-softpos-tap-to-pay
Not scored by this record.
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
No first-party gift card product exists. The kiosks page positions gift cards as someone else's system that Bite connects to - it 'seamlessly integrates with your existing tech stacks, including Point of Sale (POS), Loyalty, Gift Cards, and more' - and the 181-article help centre contains no gift-card issuance, balance or redemption article (a 'gift card' search returns only refund, coupon and loyalty-integration articles). https://www.getbite.com/kiosks · 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
Bite does run its own refund back office, contrary to the migrated rationale. The rights registry gates money actions by role: 'Refund Orders' ('Allows the user to search and refund orders, in the Bite Admin Portal or on the kiosk', prerequisite View Orders), 'Manage Discounts', and 'Verify Alcohol Purchases' ('Allows the user to use their access code on kiosks to allow guests to order alcohol'); the kiosk refund path additionally requires a passcode, and Bite Admin refunds full or partial amounts from Orders > View Transactions > Request Refund. Audit surfaces exist and are themselves rights-gated: 'View Activities', 'View System Logs', and transaction JSON logs visible to roles holding the Refund Orders right. Shortfall: no void or no-sale function is documented anywhere (the kiosk holds no drawer), and no published document says the transaction or activity log records the identity of the approving user, so the 'immutable audit log identifying the approver' half of the claim is undocumented rather than shown. https://getbite.zendesk.com/hc/en-us/articles/42423338254100-Rights-Roles · retrieved 2026-09-08
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
The vendor draws the boundary itself and draws it exclusively: 'Bite is responsible for sending orders to your Point of Sale (POS) system. Once the POS has accepted an order, how it routes to your KDS is controlled entirely by your POS and KDS configuration-not by Bite.' The article's remedy for a mis-routed order is to contact the POS provider, and it names the causes as POS-side - 'KDS routing rules that filter by order type or dining option, a new dining option that hasn't been mapped to a KDS destination, or a display filter excluding certain item categories'. No routing rule by item, category, order type or revenue centre exists in Bite Admin; station and 'station routing' return zero hits across the help centre, the marketing site and the OpenAPI bundle. https://getbite.zendesk.com/hc/en-us/articles/49061341209364-Orders-Not-Appearing-on-Kitchen-Display-KDS · retrieved 2026-09-08
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
Bite's only 'expo' artefact is a printer, not a screen. Expo Printer Onboarding configures a customer-sourced Epson via its Server Direct Print setting so that 'orders placed on the Bite Kiosk are printed for your staff', listing compatible models (TM-T88V-i firmware 3.0+, TM-88VI, TM M30 select models, TM-L90-i, TM-VII) that 'you will need to source these independently of Bite'; the HP ePrint article routes a receipt copy to a printer email address 'in addition to your POS'. A printer cannot consolidate multiple prep stations into one order view and cannot be bumped, so neither half of the claim can be met, and Bite owns no station concept at all: 'how it routes to your KDS is controlled entirely by your POS and KDS configuration-not by Bite.' https://getbite.zendesk.com/hc/en-us/articles/360059232492-Expo-Printer-Onboarding · retrieved 2026-09-08
Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator
kitchen-course-firing
Not scored by this record.
Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator
kitchen-prep-time-pacing
Not scored by this record.
Kitchen load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator
kitchen-order-throttling
Not scored by this record.
Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator
kitchen-channel-pause-propagation
Not scored by this record.
Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator
kitchen-order-ready-callback
Not scored by this record.
KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.
kitchen-bump-bar-hardware
The claim presupposes a KDS, and Bite ships none: 'Bite is responsible for sending orders to your Point of Sale (POS) system. Once the POS has accepted an order, how it routes to your KDS is controlled entirely by your POS and KDS configuration-not by Bite.' The KDS the operator uses is a third-party product - Bite's own partner intake form offers Fresh KDS, QSR Automations, Logic Controls, Kitchen Printer, 'Homegrown KDS from POS', None or Other - so no supported bump-bar or keypad models can be documented by Bite. The single corpus hit for 'bump' is an order lead time that can 'bump to the next lead time tier'; bump bar, bump-bar and programmable keypad occur zero times. https://getbite.zendesk.com/hc/en-us/articles/49061341209364-Orders-Not-Appearing-on-Kitchen-Display-KDS · retrieved 2026-09-08
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
Delivery exists in Bite only as a guest fulfilment method, never as a driver operation. The v2 API models the guest side in full - DeliveryAddress, DeliveryInstructions, CustomerDeliveryAddress with create/update/delete, and a Validate the Delivery Address at a Location endpoint - while driver, courier and runner occur zero times among the 167 schema names and across the whole bundle, the 187-article help centre and the marketing site. There is no driver entity, no clock-in or assignment state (in-store / on-run / returning), and no per-driver run history in any Bite report; the reporting set covers 86ing Activity, Channel Summary, Coupon Redemption History, Future Orders, Item Upsell, Order & Guest Engagement Data, Order Breakdown Data, Pilot Engagement, Pilot Labor Analysis, Sales Summary, Third Party Orders and Transactions Data. Bite hands the order to the connected POS, which owns fulfilment. https://documentation.getbite.com/openapi/v2/bite-api-v2 · retrieved 2026-09-08
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
No dispatch surface is published. Across the OpenAPI bundle, the 187-article help centre and the marketing site, 'dispatch' occurs exactly once and it belongs to another vendor: an Olo troubleshooting article lists Olo's handoff modes as 'Dine-In Pickup Dispatch (Third Party) Drive-Thru'. Bite therefore neither owns nor documents a dispatch board; there are no undispatched-order queues, no driver availability, no elapsed-time-per-order display and no multi-order run batching ('run batching' and 'batch runs' return zero, while the six 'batch' hits are all credit-card settlement times changed in the processor's own portal). Bite's published responsibility ends at sending the order to the POS. https://documentation.getbite.com/openapi/v2/bite-api-v2 · retrieved 2026-09-08
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
Web ordering IS a Bite product, contrary to the migrated rationale. The vendor's own OrderChannel enum registers five first-party channels: 'catering - Catering Website', 'flash - Contactless (QR-code)', 'kiosk - Kiosk', 'linebuster - Linebuster' and 'web - Online Ordering Website', and PropertyUrlSlug is 'The location's unique slug that's used in the location's web ordering'. Bite Flash is a live web channel with its own settings tab, desktop and mobile layouts (a 'Web Dining Option Modal Background Image' at 2560x1440 for Flash desktop), a Flash Payouts roll-up report and a closed screen shown 'when a guest navigates to the Flash URL'. The guest terms confirm the branding: Bite technology powers 'a kiosk, a web ordering page, or a mobile application' that is 'deployed and branded by the Brand'. Shortfall: nothing published says the site runs on the restaurant's own domain rather than a Bite-hosted location slug, and 'commission' occurs zero times corpus-wide, so the commission-free half of the claim is unstated in either direction. https://documentation.getbite.com/openapi/v2/bite-api-v2 · retrieved 2026-09-08
Vendor offers a branded native iOS and Android ordering app (published under the restaurant's own brand in the App Store/Play Store), not only a mobile web page or a shared multi-restaurant marketplace app. differentiator
digital-native-app
Not scored by this record.
Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels.
digital-account-saved-payment
CLAIM: guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels. GRADE A VERIFIED INDEPENDENTLY: the evidence is Bite's anonymous OpenAPI 3.1 spec (refetched at https://documentation.getbite.com/_spec/openapi/v2/bite-api-v2.yaml, HTTP 200, 166,656 bytes, 31 paths), not marketing or a help article. MET (1) ACCOUNT: the spec's own introduction defines the object - 'A Bite "Customer" represents a full end-user account created on Bite's platform. Customers can be created with a Bite password or can be authenticated against a Single Sign-On provider such as Paytronix or Punchh... Storing credit cards on file so that they could be used for future purchases. Access to the customer's favorite ordered items and recent order history. Storing delivery addresses on file for future purchases.' Endpoints verified present in the path list: POST /v2/customer/signup, /v2/customer/login, /v2/customer/reset-password, /v2/customer/change-password, /v2/customer/verify-account and /v2/customer. MET (2) SAVED ADDRESSES: /v2/customer/delivery-addresses and /v2/customer/delivery-addresses/{deliveryAddressId}, with an isDefault property whose description reads 'If this value is set to true, then the previously default delivery address on this customer's account will no longer be default.' MET (3) TOKENIZED PAYMENT: /v2/customer/payment-methods and /{paymentMethodId} (get, update, delete). I read the CustomerPaymentMethod schema in full: its required set is _id, last4, expirationMonth, expirationYear, cardSchemeId, plus optional postalCode, nickname and isDefault. There is no PAN and no CVV anywhere in the object - the card is held by reference only, which is what '(tokenized)' asks for, and isDefault supplies the default-card behaviour. MET (4) REORDER: GET /v2/customer/orders 'Returns the most recent 20 orders that the customer has placed through the bite platform', and /v2/customer/favorites plus /{favoriteId} hold favourite ordered items. On the kiosk the same thing is a menu section: 'Guests can now view and reorder from previous purchases using Bite kiosks... Create new "Previous Orders" section... Set the selection for the "Designation" configuration to "Order History"' (https://getbite.zendesk.com/hc/en-us/articles/42423175526676-Previous-Orders-Configuration-WIP, Support / Getting Started & Known Issues). MET (5) ACROSS FIRST-PARTY CHANNELS: I verified that the shared parameter order-channel-header (name x-bite-order-channel, required: true) is attached to all fourteen /v2/customer/* operations, and that its schema OrderChannel is a CLOSED five-value enum - catering (Catering Website), flash (Contactless QR-code), kiosk, linebuster, web (Online Ordering Website). One account, one address book and one wallet are therefore addressed from all five of Bite's own channels. SHORTFALLS WORTH KNOWING, none of which defeats the claim: the kiosk Previous Orders article is marked '(WIP)' and its richer configuration ('Order lookup on loyalty (all ordering platforms)') depends on a Punchh/Olo loyalty integration; and the spec exposes no single 'reorder' verb - reorder is composed from order history plus favourites. CONTROLS, tokenised, comments stripped before tags, scripts written to disk: over the 187-article help centre 'Apple Pay|Google Pay|Samsung Pay|mobile wallet|digital wallet' = 0 and 'card on file|saved card|tokeniz' = 0, which is precisely why the previous pass left this cell unknown/F - the help centre is silent and the finding comes from a corpus the previous pass never opened. HOMONYM THAT WOULD HAVE FAKED A DIFFERENT ANSWER: 'wallet' returns 14 hits in 2 help-centre articles and neither is a payment wallet - both are POS WALLET SETTINGS, the tiered modifier-allowance mechanism ('first 3 are free'), at https://getbite.zendesk.com/hc/en-us/articles/46637630237844 and .../42423271834772. Positive controls: Bite 450/133, order 251/45, the 3,537/181. BOUND CORPUS AND HOLES: href fixpoint re-run from scratch - 28 referenced ids, 12 absent, 0 unlisted published 200s, 5 gated 401s, 7 stale 404s, three fabricated 14-digit controls all 404. The 5 gated articles are all Kiosk & Device Setup and Troubleshooting hardware pieces and none touches accounts or checkout. 541 attachments over 187 articles, 3 non-image, none account-related. 0 iframes in 187 raw bodies, so no evidence is hiding in video. https://documentation.getbite.com/openapi/v2/bite-api-v2 · retrieved 2026-09-15 adversarially verified
Digital checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator
digital-upsell-engine
Not scored by this record.
Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.
digital-scheduled-pacing
Not scored by this record.
Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.
digital-fulfillment-modes
Not scored by this record.
Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.
digital-qr-table
Not scored by this record.
Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator
digital-kiosk
Not scored by this record.
Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.
digital-group-ordering
Not scored by this record.
Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator
digital-catering-portal
Not scored by this record.
Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator
digital-voice-ai-phone
Not scored by this record.
Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.
digital-drivethru-ai
Not scored by this record.
Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.
digital-sms-ordering
Not scored by this record.
Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator
digital-google-order
Not scored by this record.
Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.
digital-apple-business-connect
Not scored by this record.
Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.
digital-loyalty-attach
Not scored by this record.
Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.
digital-subscriptions
Not scored by this record.
Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.
digital-promo-parity
Not scored by this record.
Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator
digital-guest-data-ownership
Not scored by this record.
Digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.
digital-checkout-pci-sca
Not scored by this record.
Digital channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator
digital-surcharge-transparency
Not scored by this record.
Guest data, loyalty & marketing
Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.
guest-loyalty-unified-profile
A cross-channel guest history is reachable at the kiosk, but only through the integrated third-party loyalty program: with the 'lookup order history on loyalty' flag enabled (Punchh/Olo integration), 'Previous orders will display across all ordering platforms (online, kiosk, app) when customer is logged into loyalty', and Incentivio guests identify by phone, card number, email+phone or barcode. Shortfall: the unified profile is maintained by the loyalty provider, not Bite - the alternative configuration 'order lookup on Bite only' covers kiosk orders alone, Bite's own signup feature merely SMSes guests a link to the operator's external loyalty program, and no dedup/merge behaviour is documented anywhere in the help centre. https://getbite.zendesk.com/hc/en-us/articles/42423175526676-Previous-Orders-Configuration-WIP · retrieved 2026-08-04
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
Bite runs no accrual engine; it authenticates the guest against the brand's loyalty vendor and hands off. Its 'Simple Loyalty Sign Up' feature only 'send[s] a link to a web sign-up form or a loyalty app download link via SMS to guests at checkout', requiring the operator's own Twilio credentials. The Incentivio integration needs a location ID from the operator's Incentivio account manager and 'an open discount must be configured' on the POS, and the API models loyalty purely as authentication and redemption - guests are 'authenticated against a Single Sign-On provider such as Paytronix or Punchh', with a redeemedLoyaltyReward boolean and a rewardsProgramLogo. No accrual model of any kind is configurable in Bite: 'accrual' and 'points per dollar' return zero, and all 23 'tier' hits are POS modifier pricing tiers, order lead-time tiers, or Bite's Tier I/II/III support escalation. https://getbite.zendesk.com/hc/en-us/articles/360060833911-Simple-Loyalty-Sign-Up · retrieved 2026-09-08
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
Bite ships no campaign engine. Its only guest messaging is transactional or one-shot at the kiosk: the Simple Loyalty Sign Up SMS ('Maximum limit of 160 characters') fired at checkout in Order Summary, Payment Completed or 'Payment Completed | Forced' mode, emailed and printed receipts, and marketing consent capture for SMS and email opt-in. Triggered lifecycle automation is absent in the vendor's own vocabulary: 'birthday', 'campaign', 'win-back' and 'accrual' each return zero hits across the help centre, the marketing site and the OpenAPI bundle, and the six apparent 'lapsed' matches are all the modifier-group setting showAsCollapsed. Loyalty membership itself lives with Paytronix, Punchh or Incentivio, so lifecycle sends belong to those platforms. https://getbite.zendesk.com/hc/en-us/articles/360060833911-Simple-Loyalty-Sign-Up · retrieved 2026-09-08
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
Bite has no employee record to clock in. Its user model is administrative only: users are created in the Bite Admin Portal, assigned a Role built from rights such as Refund Orders, Manage Menu, Control Kiosk and Verify Alcohol Purchases, and scoped by location access - there is no timekeeping right, no shift, no timecard and no payroll field anywhere in the rights registry. Across the help centre, the marketing site and the OpenAPI bundle, 'time clock', 'timecard', 'timesheet', 'punch in' and 'shift' return zero; the two apparent 'clock in' matches are an operating-system instruction, 'Click the clock in the bottom-right corner of the screen'. The only labor artefact is a 'Pilot Labor Analysis' report that 'compares labor costs to sales' for pilot programs, which consumes labor data rather than capturing it. https://getbite.zendesk.com/hc/en-us/articles/42423338254100-Rights-Roles · retrieved 2026-09-08
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
Custom roles are composed from discrete named rights - 86 Menu Items, Refund Orders ('search and refund orders, in the Bite Admin Portal or on the kiosk'), Generate Reports, Manage Menu, Control Kiosk, Create and Manage Users, View Activities, Manage Integrations (Limited), and more, several with stated prerequisite rights - and a user's location access is scoped to every location, a single location, or a Location Group ('User Location Access'). Shortfall: 'Each user added to the Bite Admin Portal can be assigned single Role', so one user's rights cannot differ by location; and the register actions the claim names (void, comp, discount, drawer open, price change) do not exist in a kiosk layer - Bite's rights govern admin-portal and kiosk-management actions only. https://getbite.zendesk.com/hc/en-us/articles/42423338254100-Rights-Roles · retrieved 2026-08-04
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
CLAIM: manager overrides and approvals attributed to the individual approver and written to an immutable audit trail queryable after the fact. VERDICT: partial. EVIDENCE (Bite Admin Portal production source, via source map): (1) REFUNDS ARE ATTRIBUTED TO THE INDIVIDUAL USER: @biteinc/db-models-interface factories/universal_transaction_factory.js buildRefundTransactionData writes "refunderUserId: accessOrSessionUser.id, refunderUsername: accessOrSessionUser.data.username" onto the refund transaction; utils/order_utils.js createRefundReference/addRefund does "order.saveWithDict({ $push: { refunds: refund } })" with accessUserId, accessUsername, createdAt, refundTransactionId; schemas order_schema.js declares "refunds: { type: 'array', elementType: 'object', isReadOnly: true, fields: { _id, accessUserId, transactionId, ... accessUsername, createdAt } }". The Admin order view renders "Refunded: $${refundTotal} on ${refundTime} by ${accessUsername}" (client/js/views/cell_views/order_cell_view.js) and the transaction view "Requested by ${transaction.get('refunderUsername')}" (transaction_cell_view.js). The right is per user: user_right_helper.ts RefundOrders 'Allows the user to search and refund orders, in the Bite Admin Portal or on the kiosk.' (2) A QUERYABLE ACTIVITY LOG: client/js/models/maitred_activity.js reads /api/v2/activities (schemas requests/paginated_list/paginated_list_get.js lists it under method 'GET'), each row carrying userId, username, type (enum MaitredActivityType: Create, Update, Delete, Add, Remove, Move, LoggedIn, LocationBackup, LocationRestore, Checkpoint, CheckpointRevert, FrontEndBuildRelease, ConfigurationAudit), modelType/modelId/modelName, orig and diff, scope bite/org/site/location, wasChangeConfirmed ('Confirmation was Required'), exported by toCsv(); gated by right ViewActivities 'Allows user to view activities on the organization and location levels.' SHORTFALL: Bite has no comp/void/discount manager-override concept (it is an ordering layer, not a POS); the activity log covers configuration models, not refunds; immutability is NOT stated anywhere (isReadOnly is a client-write guard, and a GET list route is not a stated immutability guarantee). SURFACE (new, production): certspotter listing of getbite.com (45 names) -> admin.getbite.com (Bite Admin Portal, root HTTP 200 anonymously, every other path 302s to /v2/login; no robots.txt served) loads https://static.bureau.getbite.com/builds/3e0d7697945b7b5f11e2d1f5af08c87bae977c56/js/bureau-3e0d7697945b7b5f11e2d1f5af08c87bae977c56.min.js (4,401,689 bytes, single bundle) whose public source map https://static.bureau.getbite.com/builds/3e0d7697945b7b5f11e2d1f5af08c87bae977c56/js/bureau-3e0d7697945b7b5f11e2d1f5af08c87bae977c56.min.js.map (HTTP 200, 10,911,796 bytes) carries 1,465 sources ALL with sourcesContent (942 first-party @biteinc files: bureau client + @biteinc/enums, schemas, db-models-interface). No login was used; static.bureau.getbite.com serves no robots.txt (S3 AccessDenied). Retrieved 2026-09-17. https://static.bureau.getbite.com/builds/3e0d7697945b7b5f11e2d1f5af08c87bae977c56/js/bureau-3e0d7697945b7b5f11e2d1f5af08c87bae977c56.min.js.map · retrieved 2026-09-17 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
Bite holds no ingredient layer at all. Its item model, published as the v2 menu schemas MenuItem, ModGroup, Mod, SaleUnit and MenuStructure, describes what a guest can order and what it costs, with no component, ingredient or sub-recipe object; pricing is not even Bite's to hold, since modifier pricing 'lives in the POS (such as Toast) and is not directly editable within Bite'. Across the help centre, the marketing site and the OpenAPI bundle, 'bill of materials', 'sub-recipe' and 'plate cost' return zero and 'ingredient' never denotes a stock entity - its only five hits are one repeated case-study sentence about guests who 'subtract or add ingredients they choose', which is modifier selection - while the single 'recipe' hit is the customer name 'Recipe Unlimited'. The closest inventory-adjacent artefact is the 86ing Activity report, which 'helps you keep track of menu items that are out of stock' - availability, not cost. https://getbite.zendesk.com/hc/en-us/articles/34412123120660-Generating-One-Time-Reports-Setting-up-Report-Schedules · retrieved 2026-09-08
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
No purchasing or stock unit exists to convert between. Bite's published unit concept is the guest-facing SaleUnit on a menu item's price option, paired with OrderedPriceOptionQuantity, OrderedPriceOptionWeight and OrderedPriceOptionUnitPrice - a selling unit, with no purchase unit, no count unit and no conversion factor. 'Unit conversion', 'conversion factor', 'par level' and 'waste' return zero across the help centre, the marketing site and the OpenAPI bundle, and the single 'yield' hit is unrelated prose about an Esper dashboard search that 'may yield a new link'. Yield and waste percentages presuppose a raw-to-usable inventory model Bite does not have; its only stock signal is 86ing an item for the day or indefinitely. https://getbite.zendesk.com/hc/en-us/articles/34412123120660-Generating-One-Time-Reports-Setting-up-Report-Schedules · retrieved 2026-09-08
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
Bite counts nothing. Its entire stock surface is binary availability: the '86 Menu Items' right 'Allows the user to 86 items from the Bite Admin Portal, hiding items for the day, or indefinitely', 86ed items can be shown greyed out with Out of Stock text, and the 86ing Activity report 'helps you keep track of menu items that are out of stock'. There is no quantity on hand anywhere, and therefore no count to record: 'physical inventory', 'cycle count', 'spot count' and 'stock count' return zero across the help centre, the marketing site and the OpenAPI bundle, and the single 'inventory' hit is the 86ing report blurb. With no count entity there is no per-count variance history either. https://getbite.zendesk.com/hc/en-us/articles/34412123120660-Generating-One-Time-Reports-Setting-up-Report-Schedules · retrieved 2026-09-08
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
Same-day sales are viewable from any browser: the Reporting tab runs a Sales Summary on demand ('Clicking on this report will pop up a window right in your browser') for time ranges including today, and the Orders tab surfaces individual orders immediately (order-send-failure alert emails link straight to the order in Bite Admin). Shortfall: there is no persistent live dashboard - reporting is generate-on-demand or scheduled email delivery (Excel for detail reports) - and no off-premise mobile admin app is documented anywhere in the help centre. https://getbite.zendesk.com/hc/en-us/articles/34412123120660-Generating-One-Time-Reports-Setting-up-Report-Schedules · retrieved 2026-08-04
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
Bite is not the tender system of record, so the closing packet is not its to produce. Settlement is changed in the processor's own portal, never in Bite: CardConnect customers 'Login to Co-pilot/Cardpointe', Worldpay customers 'Login to accessmyiq', Heartland customers 'Contact your CSM for change requests'. Bite's kiosks hold no drawer - 'drawer', 'cash deposit', 'reconcile', 'net sales' and 'gross sales' return zero across the help centre, the marketing site and the OpenAPI bundle - and when a debit refund cannot be processed the operator must act 'directly in-store, either through store credit or cash'. Bite does publish a schedulable report set (Sales Summary, Transactions Data, Order Breakdown Data, Channel Summary, Coupon Redemption History and others, deliverable daily), but Sales Summary is by its own description 'a high-level look at your sales performance, perfect for quick overviews', and no single document reconciles gross and net sales, tax, tips, discounts, refunds, tender types and an expected cash deposit. https://getbite.zendesk.com/hc/en-us/articles/360037683251-Changing-Credit-Card-Batching-Time · retrieved 2026-09-08
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
MERGE (321st): proposed no DOWNGRADED to partial/B -- the Sales Summary shows item-level sales and counts (TOP ITEMS, BREAKDOWN BY SECTION) and server-built Order Breakdown Data columns are unbounded, so item-level mix exists in part; the closed report-input enumeration (no daypart, no revenue-center filter) and absent modifier stats rule out yes. CLAIM: a PMIX report at item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center. VERDICT (proposed): no. ENUMERATION: @biteinc/enums report_type.js is a CLOSED 29-value enum and report_type_helper.js names every one: Coupon Redemption History, Customer Orders, Upsell by Day (internal only), 86ing Activity, Flash Payouts, Future Orders, Industry Benchmark (internal only), Recommended Items (item-upsell), Kiosk Usage Overlap (internal only), Kiosk Peripherals, KOR, Loyalty Login Attempts, Loyalty Signups, Loyalty Usage, Order Conversion Rate, Order Insertion Rate, Pilot Engagement, Pilot Labor Analysis, Punchh Location Orders, Order & Guest Engagement Data, Order Breakdown Data, Channel Summary, Sales Summary, Org Summary, Site Summary, Transactions Data, Third Party Orders, Vendor Payouts, Vitrine Session Metrics - no product-mix/item-sales report. The ONLY input fields any report accepts are enumerated in client/js/models/one_time_report_schema.ts (type, locationGroupId, dateRange, salesByLocationGroupIds, emailAddresses, orderChannels, isBiteOnly, generateMonthlyReportsForGivenTimeRange, vendorId) and schemas report_schedule_schema.js (type, scope, currentDay, day, dayOfMonth, time, timezone, locationGroupId, salesByLocationGroupIds, emailAddresses, isEnabled, orderChannels, isBiteOnly, vendorId): no daypart and no revenue-center filter on any report. Closest item-level output: the Sales Summary modal (client/js/views/sales_summary_view.js) shows 'TOP ITEMS' = the first 3 of sortedItemStats and 'BREAKDOWN BY SECTION' (name: $sales (count items)), with no modifier statistics (sortedItemStats in 1 file; modStats/modifierStats 0). CONTROLS over the 942 first-party sources, case-insensitive word-boundary: daypart|dayparts|day part|meal period|revenue center|pmix|product mix. POISON named: every 'day part' hit is menu timing (menu_structure.js 'No assigned day part (menu will not be shown)', menu_timing_details_view.js, location_view.js open-hours warning), and 'Revenue Center' appears only as POS-integration mapping fields (common i9n_schemas.js 'Revenue Center', 'Revenue Center ID'); pmix / product mix = 0. BOUND: report Excel columns are generated server-side and are not in the bundle, so modifier columns inside 'Order Breakdown Data' cannot be excluded; the no rests on the filter conjunct (no daypart or revenue-center filter anywhere in the complete report input enumeration) plus the absence of any PMIX report type. SURFACE (new, production): certspotter listing of getbite.com (45 names) -> admin.getbite.com (Bite Admin Portal, root HTTP 200 anonymously, every other path 302s to /v2/login; no robots.txt served) loads https://static.bureau.getbite.com/builds/3e0d7697945b7b5f11e2d1f5af08c87bae977c56/js/bureau-3e0d7697945b7b5f11e2d1f5af08c87bae977c56.min.js (4,401,689 bytes, single bundle) whose public source map https://static.bureau.getbite.com/builds/3e0d7697945b7b5f11e2d1f5af08c87bae977c56/js/bureau-3e0d7697945b7b5f11e2d1f5af08c87bae977c56.min.js.map (HTTP 200, 10,911,796 bytes) carries 1,465 sources ALL with sourcesContent (942 first-party @biteinc files: bureau client + @biteinc/enums, schemas, db-models-interface). No login was used; static.bureau.getbite.com serves no robots.txt (S3 AccessDenied). Retrieved 2026-09-17. https://static.bureau.getbite.com/builds/3e0d7697945b7b5f11e2d1f5af08c87bae977c56/js/bureau-3e0d7697945b7b5f11e2d1f5af08c87bae977c56.min.js.map · retrieved 2026-09-17 adversarially verified
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
Three named levels exist - org > Location Group > location - and the middle tier is a first-class object: 'A Location Group is a subset of locations in an org', created by Admins 'at the top-level page for an org', with regional groups ('West Coast Locations'), franchisee groups ('ABC Franchisee Group') and per-GM purviews as the documented uses. Permissions scope to it - a user's access is 'every location in the org', 'a single specific location', or 'a set of locations in a Location Group' - and reporting scopes to each tier: report schedules take a Scope field ('Choose which locations or regions you want the report to cover'), a Daily Org Summary Report runs at organization level ('Disable Org Summary Reports'), and one-time reports run per location. https://getbite.zendesk.com/hc/en-us/articles/360044040291-User-Location-Access · retrieved 2026-08-04
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
Bite carries no pricing engine to put tiers in: pricing configuration 'lives in the POS (such as Toast) and is not directly editable within Bite', 'Bite does not independently calculate' pricing logic, and 'the kiosk pricing should mirror the behavior seen in the POS and in any connected mobile ordering channels'. Menu data itself arrives by POS sync every 10 minutes ('Manually Syncing Menu from POS'). With no Bite-side price field at all, per-location-group, per-channel or per-daypart price tiers cannot exist in Bite - price zoning is a property of the connected POS. https://getbite.zendesk.com/hc/en-us/articles/46637630237844-Understanding-POS-Wallet-Settings-for-Modifier-Pricing · retrieved 2026-08-04
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
ELO, Lenovo and ChromeOS named as hardware partners; no minimum OS versions or device specs published. https://getbite.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
Kiosks stop taking orders when connectivity drops rather than degrading gracefully: the support page's enumerated causes for 'Kiosk is unable to place an order' are an internet blip ('please re-try sending the order'), unplugged cables/modem, 'Internet down', a firewall 'blocking our connection to the kiosk', and 'POS connection down or interrupted'. The Elo and Esper offline-kiosk articles treat an offline device purely as a fault to repair (reboot, whitelist check, factory reset) - neither describes any degraded operating mode. No documented list of which functions degrade exists because none continue: kiosks tender no cash, and the expo printer prints via cloud-polled Epson Server Direct Print, so nothing reaches the kitchen offline either. https://getbite.zendesk.com/hc/en-us/articles/360036891332-Kiosk-unable-to-place-Order · 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
The KDS is always someone else's product. Bite states its own boundary: 'Bite is responsible for sending orders to your Point of Sale (POS) system. Once the POS has accepted an order, how it routes to your KDS is controlled entirely by your POS and KDS configuration-not by Bite', and directs mis-routing complaints to the POS provider. Its partner intake form treats KDS as a field the operator fills in from third parties - Fresh KDS, QSR Automations, Logic Controls, Kitchen Printer, 'Homegrown KDS from POS', None or Other. The only kitchen hardware Bite documents is an expo receipt printer the customer must 'source these independently of Bite'. Bite sells no display, and with no station model, no bump input and no course or fire timing anywhere in its corpus, the integration-only dependency the claim excludes is exactly what Bite has. https://getbite.zendesk.com/hc/en-us/articles/49061341209364-Orders-Not-Appearing-on-Kitchen-Display-KDS · retrieved 2026-09-08
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
REPLACES an undated first-pass placeholder that said 'No developer portal or public API reference found from the marketing site' -- while extensibility-oauth-partner-apps sits at no A in this same record citing this very page, retrieved 2026-08-04. Re-fetched 2026-09-01: HTTP 200 anonymously, 650 KB, no robots.txt on the host (404, allowed under RFC 9309). The document states its own purpose -- 'Bite exposes online ordering functionality through a REST API which third party developers can use to create applications on top of the Bite platform' -- and its navigation enumerates the v2 surface: Introduction, Bite Nomenclature, Usage Basics, Changelog, then API Reference sections for Customer v2 (Account Management, Delivery Addresses, Order History, Payment Methods, Push Tokens), Locations v2 (Pick a Location), Menu v2, Orders v2, Mobile App Config v2, Reporting v2, Webhooks, and Embedding Bite in a 3rd Party Mobile App. Nothing on the path required an agreement, NDA or sales call. https://documentation.getbite.com/openapi/v2/bite-api-v2 · retrieved 2026-09-01
API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator
extensibility-api-access-cost
Not scored by this record.
A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator
extensibility-free-sandbox
Not scored by this record.
Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).
extensibility-oauth-partner-apps
The API reference specifies static bearer-token auth, not OAuth: 'Authorization: Must be set to Bearer: API_TOKEN' alongside fixed x-bite-org-id and x-customer-app-scope headers; OAuth 2.0 appears nowhere in the document. Operator tokens are issued from the Bite Admin Portal > org > API Token tab (the Reporting API help article says to email support if none exist), third-party developer credentials are provisioned per sandbox by Bite, and webhooks 'can be configured by Bite employees at the organization level' - there is no scoped, operator-granted, individually revocable OAuth flow. https://documentation.getbite.com/openapi/v2/bite-api-v2 · retrieved 2026-08-04
The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.
extensibility-webhooks-push
Push webhooks exist but cover exactly two event types: 'Order sent webhooks will be sent as soon as the order is sent to the POS', and order-updated fires 'if the guest provides an email address for a receipt after completing an order, provides a satisfaction score, or if there has been a refund made for an order'. Shortfall: no distinct paid or voided events (payment state rides inside the order-sent payload; refunds surface only via order-updated), and registration is not self-serve - operators email support@getbite.com with a destination URL and 'we will set it up and reach back out with a private key'; the API reference likewise says webhooks 'can be configured by Bite employees at the organization level'. https://getbite.zendesk.com/hc/en-us/articles/13433960302868-Bite-order-webhooks-for-operators · retrieved 2026-08-04
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 does not continue on-terminal through an outage: 'Kiosk is unable to place an order' is diagnosed entirely as connectivity - internet blip (remedy: 're-try sending the order'), unplugged cables, 'Internet down', firewall, 'POS connection down or interrupted' - and the offline-kiosk runbooks (Elo, Esper) exist to bring the device back online, not to keep it selling. Ticket routing is not Bite's either ('how it routes to your KDS is controlled entirely by your POS and KDS configuration—not by Bite'), and the only Bite-attached printer polls a cloud endpoint via Epson Server Direct Print, so no order capture, routing or printing survives a WAN loss. https://getbite.zendesk.com/hc/en-us/articles/360036891332-Kiosk-unable-to-place-Order · 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
Bite has no offline kitchen path. KDS routing is not Bite's function at all - 'Once the POS has accepted an order, how it routes to your KDS is controlled entirely by your POS and KDS configuration—not by Bite' - and the order pipeline feeding it requires live internet and a live POS connection ('Kiosk unable to place Order' lists 'Internet down' and 'POS connection down or interrupted' among the causes). The optional expo printer prints via Epson Server Direct Print polling a cloud endpoint. With no offline order capture and no Bite-side ticket routing, nothing prints or displays during an outage. https://getbite.zendesk.com/hc/en-us/articles/49061341209364-Orders-Not-Appearing-on-Kitchen-Display-KDS · retrieved 2026-08-04
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
No failover and no printer alert exists. The available alert rules are enumerated - Generic Sending Order Error, Item 86'd sending Order, Kiosk Down or Missing, Kiosk Inactive, Kiosk Turned Off Manually, Ordering, Sending Order Time Out, Sending Webhook Error, Uncommitted Transactions - and none concerns an unreachable printer. 'Expo Printer Onboarding' configures a single Epson via Server Direct Print with no backup printer, fallback routing or ticket-loss protection described; kitchen-ticket routing generally belongs to the host POS, not Bite. https://getbite.zendesk.com/hc/en-us/articles/360035091252-Kiosk-Alerting-Rules · retrieved 2026-08-04
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
Bite does publish legal documents, but none of them is the merchant agreement, and the vendor states that the cancellation terms live in the private signed contract. Its cancellation guide routes every operator to a bilateral review - 'our team will review your contract and terms, including the effective agreed cancel date, and respond back with this information' - and tells operators unsure 'whether your contract has any special cancellation terms' to contact Customer Success. The two published documents are scoped elsewhere: /tos is website terms of use plus a privacy policy governing 'accessing the website', and /product-tos is guest-facing ordering terms for people using 'a kiosk, a web ordering page, or a mobile application'. Neither states a renewal term or a notice window, and 'auto-renew', 'automatically renew', 'initial term', 'subscription term' and 'master service agreement' return zero across the help centre, the marketing site and the OpenAPI bundle. https://getbite.zendesk.com/hc/en-us/articles/50311281983252-How-to-cancel-your-Bite-service-when-your-store-is-closing · retrieved 2026-09-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
Site discloses no per-kiosk, per-location or subscription figures; every path leads to a demo request. https://getbite.com/ · retrieved 2026-08-01
Individual modules (online ordering, KDS, loyalty, inventory, payroll, marketing) can be purchased à la carte and cancelled independently without repricing the base POS subscription. differentiator
commercial-module-unbundling
Not scored by this record.
All required terminals, KDS screens, and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental.
commercial-hardware-purchase-outright
CLAIM: all required terminals, KDS screens and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental. SHORTFALL, numbered. (1) THE PRICE IS NOT PUBLISHED. I probed getbite.com/pricing myself: HTTP 404 at 906 bytes. No price list of any kind appears on the site and the record's pricing.transparency is quote-only. MET (1) OUTRIGHT PURCHASE. Bite's own /warranties page (refetched, HTTP 200) is a 'Component Warranties' link list of the manufacturers' sale and warranty documents for exactly the kiosk stack its setup guides require - 'Elo Terms of Sale', 'Wallaby Self-Service Stand', 'Warranty Information', 'Epson TM-m30 Warranty', 'TM-T88VI Warranty', 'TM-T88VI-i Warranty', 'Ethernet Cables', 'TP-Link TL-SF1005D V15'. A vendor that leased you the hardware would not publish the manufacturer's terms of SALE. The linked Elo document is unambiguous: 'These terms and conditions of sale ("Terms") apply to all orders accepted and all sales made by Elo Touch Solutions, Inc. ... "Buyer" means an entity ordering the Products from Elo or an Elo authorized distributor or reseller ... Buyer undertakes to purchase all Products listed in the [Order]' (https://assets.admin.getabite.co/warranties/elo-touch-terms-of-sale-2019-03-26.pdf). Bite says the same from the operator's side: 'By default (after purchasing the device from Elo or another retailer), or after performing a Factory Reset, the Elo device will use DHCP' (https://getbite.zendesk.com/hc/en-us/articles/14162050542100-Elo-QuickGuide-DHCP-or-Static-IP-Configuration). MET (2) THE BOM IS OPEN AND THIRD-PARTY, with manufacturer part numbers an operator can source anywhere - screen Elo E462193 or E611296, Wallaby countertop stand E796783 or floor stand E796965+E797162, EMV cradle E699053, VESA wall kit E143088, Epson TM-88V/TM-88VI printer, 5-port switch, 2D barcode scanner E926356 (https://getbite.zendesk.com/hc/en-us/articles/360036196252-Elo-15-Setup and .../360036941391-Elo-22-Setup, Support / Kiosk & Device Setup and Troubleshooting). MET (3) NO LEASE - see controls. CONTROLS, tokenised with word boundaries, comments stripped before tags, scripts written to disk: over 187 help-centre articles leas(e|ed|ing)|rent(al|ed|s)? = 1 hit in 1 article and IT IS A FICTION - the token is 'P LEASE NOTE', the word PLEASE split by markup inside the Expo Printer Onboarding article, which a word-boundary matcher then reads as 'LEASE'. Reporting 'lease appears in this corpus' would have been false. 'subscription' = 8 hits in 3 articles and none is a hardware rental: they are 'Subscription service application is down' in the Support Policy SLA tiers and 'Kiosk Alert Subscriptions', an email alert feed. purchas(e|ed|ing) = 5 hits in 3 articles, all genuine. PDF HAZARD MEASURED, INVARIANCE PUBLISHED: the Elo terms-of-sale PDF was extracted with pdftotext -layout (40,792 chars) and plain pdftotext (40,203 chars) and both were also probed whitespace-squashed. Tokenised, lease/leased/leasing = 0 and rental = 0 under every probe while purchase = 12, buyer = 135, warranty = 24, sale = 6, title = 8 and price = 6 read IDENTICALLY in both extraction modes - the invariance is the control, not the figures. PUBLISH THE POISON: the squashed probe is not safe here - squashed 'rent' scores 3 on this PDF and squashed 'tap' scores 4, both artefacts of joining across whitespace, so the tokenised zero is the trustworthy one. Positive controls Bite 450/133, order 251/45, the 3,537/181. BOUND CORPUS AND ITS HOLE: href fixpoint - 28 referenced ids, 12 absent, 0 unlisted published 200s, 5 gated 401s, 7 stale 404s, three fabricated 14-digit control ids all 404. All five gated articles are in Support / Kiosk & Device Setup and Troubleshooting, the hardware section itself, which is a second reason this is a partial and not a stronger claim. 541 attachments over 187 articles, 3 non-image; neither PDF (a scanner trigger-modes guide and an Ingenico cabling guide) carries commercial terms. 0 iframes in 187 raw bodies. https://www.getbite.com/warranties · retrieved 2026-09-15 adversarially verified
Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator
commercial-hardware-not-locked
Not scored by this record.
One-time implementation, menu-build, onboarding, and training fees are published as specific amounts or explicitly stated as $0.
commercial-implementation-fee-published
Not scored by this record.
Operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee.
commercial-data-export-self-serve
Not scored by this record.
Guest/customer records, loyalty balances or point ledgers, and gift-card liability balances are exportable in machine-readable form by the operator. differentiator
commercial-export-customer-and-loyalty
Not scored by this record.
Contract or documentation specifies a post-termination data retrieval window (a defined number of days during which the operator can still export their data) rather than immediate cutoff. differentiator
commercial-post-termination-export-window
Not scored by this record.
Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator
commercial-data-ownership-clause
Not scored by this record.
The POS is source-available or open source with a documented self-hosting option (source published under an OSI or source-available license, not merely an open API).
commercial-source-available-selfhost
Not scored by this record.
Vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A / SAQ P2PE-HW, and names the applicable SAQ.
commercial-pci-p2pe-tokenization
Not scored by this record.
Vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — notably MFA for all access to the cardholder data environment including POS and back-office logins, and (for hosted ordering pages) payment-page script integrity monitoring per Req 6.4.3/11.6.1.
commercial-pci-dss-4-controls
Not scored by this record.
Vendor states it holds a current SOC 2 Type II (or ISO 27001) attestation and will provide the report under NDA via a trust center or on request.
commercial-soc2-attestation
Not scored by this record.
Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.
commercial-privacy-dsar-tooling
Not scored by this record.
Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator
commercial-wcag-kiosk-accessibility
Not scored by this record.
POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator
commercial-dual-pricing-compliant
Not scored by this record.
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 2 values — 0 upheld, 0 downgraded, 2 upgraded. It separately resolved 37 previously unknown values. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| order-capture-offline-order-entry | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-no | The vendor's own support page enumerates the causes of a kiosk being unable to place an order, and they are connectivity: 'Internet down', unplugged cables/modem, firewall blocks, and 'POS connection down or interrupted', with the remedy 're-try sending the order'. The Elo and Esper offline-kiosk articles treat offline purely as a fault to repair. No offline ordering scope is published and kiosks tender no cash, so every element of the claim is positively absent. source |
| menu-pricing-modifier-price-by-parent-size | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-no | The POS Wallet Settings article states modifier pricing 'lives in the POS (such as Toast) and is not directly editable within Bite' and that 'Bite does not independently calculate modifier allowance logic' - the kiosk mirrors synced POS prices. There is no Bite-side price configuration at all, so no matrix by parent item and size can be configured in Bite; the capability belongs to the connected POS. source |
| menu-pricing-topping-quantity-tiers | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-partial | The kiosk demonstrably applies POS-defined tiered modifier pricing at order time (first-N-free allowances with per-extra charges) and syncs Revel intensity descriptors like 'light on the onions' via mod codes. Held at partial because nothing is configurable in Bite - tiers are count-based allowances defined in the host POS, not per-tier price multipliers, and light/extra/double descriptors are documented only for the Revel integration. source |
| payments-gift-cards | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-no | The vendor's own kiosks page classifies gift cards as part of 'your existing tech stacks' that Bite 'seamlessly integrates with', i.e. an external system, and the 181-article help centre has no gift-card issuance, balance or redemption article. A first-party gift card program with cross-location balance does not exist in the product. source |
| labor-granular-rbac | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-partial | Rights & Roles documents custom roles built from discrete named rights with prerequisites, and User Location Access documents scoping a user to all locations, one location, or a Location Group. Held at partial because each user carries exactly one org-level role, so rights cannot vary per location for a user, and the claim's register actions (void, comp, discount, drawer open) have no equivalent in a kiosk layer. source |
| reporting-realtime-dashboard | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-partial | A browser-run on-demand Sales Summary covers same-day sales and the Orders tab shows individual orders immediately (failure-alert emails deep-link to orders in Bite Admin), so off-premise browser visibility exists. Held at partial because the documented model is generate-on-demand or scheduled email, not a persistent live dashboard, and no mobile admin app appears anywhere in the help centre. source |
| extensibility-oauth-partner-apps | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-no | The API reference mandates 'Authorization: Must be set to Bearer: API_TOKEN' with fixed org headers and never mentions OAuth 2.0; operator tokens come from an Admin Portal API Token tab, developer credentials are provisioned by Bite per sandbox, and webhooks are 'configured by Bite employees at the organization level'. The documented auth model is static tokens, which is the enumerated alternative to the claimed OAuth flow. source |
| extensibility-webhooks-push | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-partial | Push webhooks are documented (order-sent fires as soon as the order reaches the POS; order-updated on receipt email, satisfaction score, or refund), so the platform is not polling-only. Held at partial because coverage is two event types with no distinct paid/voided events and setup is done by Bite support via email with a private key, not self-serve. source |
| reliability-offline-kds-printing | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-no | Bite's own KDS troubleshooting article states routing to the KDS 'is controlled entirely by your POS and KDS configuration - not by Bite', and the order path that would feed any kitchen output requires live internet and POS connectivity per 'Kiosk unable to place Order'. The expo printer is cloud-driven (Epson Server Direct Print). There is no Bite kitchen path that could continue offline. source |
| reliability-printer-fallback | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-no | The Kiosk Alerting Rules article enumerates the nine available alert types and none concerns an unreachable printer, which defeats the claim's alerting half; Expo Printer Onboarding configures a single Epson target via Server Direct Print with no backup routing or failover described, and kitchen-ticket routing otherwise belongs to the host POS. source |
| order-capture-scheduled-orders | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-partial | Future-dated ordering is documented as a location feature - pickup time slots at 'locations that have future orders enabled', per-dining-option Order Throttling of time windows, Order Lead Times tiers, and a 'Future Orders' report of 'all pre-orders coming up'. Held at partial because lead-time rules are per location/menu section rather than per channel, and no document shows Bite firing a held order into the make queue at a computed time - kitchen routing is 'controlled entirely by your POS and KDS configuration', so fire timing belongs to the host POS. source |
| guest-loyalty-unified-profile | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-partial | Previous Orders Configuration documents cross-channel history at the kiosk: with 'lookup order history on loyalty' enabled, 'Previous orders will display across all ordering platforms (online, kiosk, app) when customer is logged into loyalty'. Held at partial because the profile is maintained by the integrated loyalty provider (Punchh/Olo/Incentivio), not Bite - the Bite-only lookup covers kiosk orders alone, signup is an SMS link out to the external loyalty program, and no dedup/merge behaviour is documented. source |
| multi-location-org-hierarchy | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-yes | User Location Access documents org > Location Group > location with the group as a first-class object ('A Location Group is a subset of locations in an org', created by Admins at the org's top-level page) that user permissions scope to, and reporting scopes to every tier: report-schedule Scope 'Choose which locations or regions you want the report to cover', an org-level Daily Org Summary Report, and per-location one-time reports. That satisfies the three-level, permission- and reporting-scoped hierarchy the claim asks for. source |
| multi-location-central-menu-publish | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-no | The documented menu pipeline is per-location POS mirroring - 'Bite syncs POS data every 10 minutes during working hours' with a per-location manual Sync Menu button, and menu setup guides cover authoring in the host POS (Toast). Bite Admin menu tabs are per-location presentation edits. There is no org-level menu object, no publish-to-locations action and no version history; central publish is the connected POS's job, which is the enumerated alternative. source |
| multi-location-price-zones | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-no | Bite's own pricing article states configuration 'lives in the POS (such as Toast) and is not directly editable within Bite' and that 'the kiosk pricing should mirror the behavior seen in the POS'; menus arrive by POS sync. With no Bite-side price field, per-location-group, per-channel or per-daypart tiers cannot be configured in Bite - the capability belongs to the connected POS, consistent with the modifier-price-by-parent-size resolution. source |
| hardware-offline-mode | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-no | 'Kiosk unable to place Order' enumerates the causes of a kiosk not taking orders and they are all connectivity ('Internet down', cables, firewall, 'POS connection down or interrupted'), with retry as the remedy; the Elo and Esper offline-kiosk articles are pure repair runbooks with no degraded operating mode. Kiosks tender no cash and the expo printer is cloud-polled, so no function continues offline and no degradation list exists to publish. source |
| reliability-offline-order-entry | unknown / F - placeholder rationale "No public documentation located during the 2026-08-01 research pass", meaning the cell was never examined | resolve-to-no | Same evidence base as hardware-offline-mode and the already-resolved order-capture-offline-order-entry: order placement requires live internet and a live POS connection per the vendor's own troubleshooting page, ticket routing is 'controlled entirely by your POS and KDS configuration - not by Bite', and the only Bite-attached printer polls a cloud endpoint via Epson Server Direct Print. Order entry, routing and printing all stop when the WAN drops. source |
| order-capture-split-merge | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | resolve-to-no | The claim needs split by item/seat/even/amount plus merge including after partial payment. Bite's own Close Order description makes an order atomic - 'Closes a fully paid order so that it can be sent to the kitchen for fulfillment' - so partial payment cannot exist, and no split/seat/merge/check object appears among the 167 published schemas. Corpus-wide zero for split, seat, merge and 'separate check' with a matcher proved positive on kiosk/refund/modifier in the same run. Note the spec declares additionalProperties nowhere, so its silence is a floor; the verdict rests on the affirmative atomic-payment sentence, not on schema silence alone. source |
| payments-refund-void-controls | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | upgrade-to-partial | The stored rationale, 'No POS back office; voids and refunds are handled in the connected POS', is false. Bite Admin has an Orders tab that issues full and partial refunds, and the vendor's rights registry gates it behind a named 'Refund Orders' right with 'Manage Discounts' alongside it, plus a kiosk passcode and an alcohol-verification access code. Rights-gated activity, system and transaction-JSON logs exist. It stops short of yes because voids and no-sales are absent and approver identity in the log is nowhere stated. source |
| kitchen-station-routing | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | resolve-to-no | An exclusive vendor statement, not an inference from silence: routing after POS acceptance is 'controlled entirely by your POS and KDS configuration-not by Bite'. The configurable routing the claim requires is therefore in the connected POS by the vendor's own account, and Bite Admin exposes no station concept at all. source |
| kitchen-expo-consolidation | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | resolve-to-no | Opening the artefact settles it: the 16 'expo' hits in the help centre are all an expo PRINTER that Bite does not even sell, configured through Epson's Web Config Utility. The claim requires an expo screen that consolidates prep stations and completes only when every station has bumped its items; a print-out has no bump state and no station model, and Bite disclaims KDS routing entirely. source |
| kitchen-bump-bar-hardware | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | resolve-to-no | No first-party KDS exists, so bump-bar support cannot. The one lexical hit for 'bump' is a lead-time tier escalation, an unrelated sense, and the vendor's partner form treats KDS as a third-party field the operator fills in. source |
| delivery-driver-roster | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | resolve-to-no | The claim asks for drivers as first-class entities with clock-in/out, assignment state and per-driver run history native to the product. Bite publishes the guest-address side of delivery in detail and nothing at all on the driver side - zero hits for driver, courier and runner on a matcher proved positive in the same run - and its own report list has no driver report. The spec closes no schema, so this rests on the absence of any driver surface across three corpora plus the affirmative fact that Bite's role ends at sending the order to the POS. source |
| delivery-dispatch-board | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | resolve-to-no | The single 'dispatch' hit in the entire corpus is Olo's handoff-mode vocabulary quoted inside a Bite troubleshooting article, not a Bite feature - the artefact belongs to a different publisher. Every component of the claim (undispatched queue, driver availability, elapsed time, run batching) is absent, and Bite ships no driver entity for a board to display. source |
| digital-first-party-web | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | upgrade-to-partial | The stored rationale, 'Web ordering is not a Bite product; Olo is listed as an integration partner for that channel', is falsified by Bite's own channel registry, which lists 'web - Online Ordering Website' and 'catering - Catering Website' as Bite order channels alongside kiosk and linebuster, each with a per-location URL slug. The guest terms describe a Bite-powered 'web ordering page' 'deployed and branded by the Brand'. Held to partial rather than yes because own-domain hosting and commission-free economics are both unstated. source |
| guest-loyalty-accrual-models | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | resolve-to-no | The claim requires at least two accrual models configurable in the product without a bolt-on loyalty vendor. Every loyalty artefact Bite publishes is a bolt-on: an SMS link to the brand's sign-up page, an Incentivio integration keyed on the operator's own account, and SSO plus a redemption flag against Paytronix or Punchh. The 23 'tier' hits are homonyms - POS modifier pricing tiers, lead-time tiers and support tiers - so no spend-tier accrual exists either. source |
| guest-loyalty-lifecycle-automation | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | resolve-to-no | None of the three named automations - birthday, first-visit thank-you, lapsed win-back - exists in any Bite surface, and the apparent 'lapsed' hits were the substring inside showAsCollapsed, a modifier-group display setting. Bite's messaging is a single 160-character checkout SMS pointing at the brand's loyalty vendor, which is the opposite of an always-on configurable campaign. source |
| labor-clock-in-at-pos | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | resolve-to-no | The two corpus hits for 'clock in' are the Windows taskbar clock in a network-settings instruction, not a time clock. Bite's rights registry is the complete published account of what a Bite user can do and contains no timekeeping capability; the vendor is not the system of record for staff, and its one labor report analyses costs supplied from elsewhere. source |
| inventory-recipe-bom-costing | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | resolve-to-no | Multi-level recipe costing requires an ingredient entity, and Bite publishes none - the one 'recipe' token in the whole corpus is the restaurant group Recipe Unlimited, a customer name. Bite does not even own item pricing, which it reads from the connected POS, so plate cost recalculation cannot occur here. source |
| inventory-unit-conversion-yields | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | resolve-to-no | The claim needs purchase, recipe and count units with explicit conversion factors plus a yield/waste percentage. Bite's only unit is the SaleUnit attached to a sellable price option; there is no stock item to buy or count. The lone 'yield' token is the ordinary verb in an Esper troubleshooting note, not a yield percentage. source |
| inventory-count-modes | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | resolve-to-no | Full, spot and cycle counts with retained per-count variance history all require a quantity on hand, and Bite's published stock model is an on/off 86 flag hiding an item for the day or indefinitely. The one 'inventory' token in the corpus is the marketing sentence describing that 86ing report, which tracks availability rather than counting anything. source |
| reporting-eod-closeout | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | resolve-to-no | The claim is a composite single document and it fails on the cash leg outright: Bite never holds cash, so an expected cash deposit cannot be computed, and card settlement is batched in CardConnect, Worldpay or Heartland's own portal rather than in Bite. Its report list is explicitly a floor - the same article mentions a 'Sales Details' report the list omits - so this rests on the affirmative facts about settlement and cash rather than on the enumeration being complete. source |
| hardware-kds | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | resolve-to-no | The claim requires a first-party KDS rather than an integration-only dependency, and the vendor's own troubleshooting article disclaims KDS behaviour entirely once the POS has the order. Bite's partner form enumerates third-party KDS vendors as the operator's choice, and the only kitchen device it documents is an Epson expo printer it does not sell. source |
| commercial-autorenew-terms-published | no / F - uncited: the migrated 2026-08-01 rationale carried no source URL | resolve-to-no | The verdict stands but the stored rationale was wrong: Bite does publish terms of service - two documents, /tos and /product-tos - so 'no public terms of service or contract terms surfaced' is false. What is genuinely absent is a public merchant agreement stating the auto-renewal term and notice window; the vendor's own cancellation article confirms those live in the individual contract subject to case-by-case review, which is precisely the signed-quote-only condition the claim penalises. source |
| menu-pricing-nested-modifiers | unknown (F) — never examined | resolve-to-yes | Grade A challenged and survives: the source is an anonymous OpenAPI 3.1 spec, not a help article. I refetched it (200, 166,656 bytes) and read the ModGroup, Mod and MenuItem schemas myself; the recursion via Mod.priceOptions[].modGroupIds and the per-ModGroup minSelectable/maxSelectable are both present as quoted. The one genuine weakness - no boolean required flag, with isRequired/mandatory/forced all returning 0 across the spec - was already disclosed by the proposer and is now recorded in the note as a named qualification. All five gated help-centre articles are hardware troubleshooting, none in a menu subject area, so nothing in this cell's evidence base is behind a wall. |
| digital-account-saved-payment | unknown (F) — never examined | resolve-to-yes | Grade A challenged and survives. The claim does not rest on a help-centre article or an admin screenshot - the help centre is provably silent on card-on-file (0 hits for 'card on file|saved card|tokeniz') and the whole verdict comes from the anonymous OpenAPI spec, which I refetched and read. I verified the four customer endpoint families, the CustomerPaymentMethod schema's reference-only card storage, and that the required x-bite-order-channel header carries a closed five-value enum on all fourteen customer operations, which is what settles 'across first-party channels'. |
| payments-emv-nfc | unknown (F) — never examined | resolve-to-partial | Value and grade upheld at partial/B, note amended for a control fault. The prior pass's control used only the spaced form 'tap to pay' and so reported no tap-to-pay evidence; the hyphenated 'tap-to-pay' appears in the Heartland Lane 3000/5000 article as a setting Bite documents enabling, which strengthens the contactless conjunct. Apple Pay remains genuinely absent from both the help centre and the OpenAPI spec, at least one conjunct (EMV) is fully met, and the five gated articles sit in the same hardware section as this cell's evidence, which correctly keeps it off a zero. |
| digital-menu-single-source | unknown (F) — never examined | resolve-to-partial | Upheld at partial/B with the shortfall independently re-verified. I confirmed the Toast 'new sections must always be added manually' quote against the raw body, confirmed the 10-minute POS sync quote, and tested the claim that Bite runs its own presentation layer with a fresh tokenised census (menu page 10/3, menu cover 13/5, badge 26/2, invisible|secret 31/2) rather than taking it on trust. Two conjuncts are genuinely met, so the partial is not self-refuting. |
| commercial-hardware-purchase-outright | unknown (F) — never examined | resolve-to-partial | Upheld at partial/B. I re-probed getbite.com/pricing (404, 906 bytes) and the /warranties page (200), refetched the Elo terms-of-sale PDF and ran the three-way extraction myself, reproducing the invariance and adding the poison the prior pass missed: the whitespace-squashed probe scores 'rent' 3 on that very PDF, so only the tokenised zero is publishable. One conjunct (published price) fails and two are met, which is a proper partial. |
Sources
Every URL this record cites. 31 in total.
- https://getbite.com/
- https://getbite.zendesk.com/hc/en-us/articles/360036891332-Kiosk-unable-to-place-Order
- https://getbite.zendesk.com/hc/en-us/articles/46637630237844-Understanding-POS-Wallet-Settings-for-Modifier-Pricing
- https://getbite.zendesk.com/hc/en-us/articles/12403816125460-Revel-Modifier-Options-support
- https://www.getbite.com/kiosks
- https://getbite.zendesk.com/hc/en-us/articles/42423338254100-Rights-Roles
- https://getbite.zendesk.com/hc/en-us/articles/360044038891-User-Permissions-Roles-and-Rights
- https://getbite.zendesk.com/hc/en-us/articles/360044040291-User-Location-Access
- https://getbite.zendesk.com/hc/en-us/articles/34412123120660-Generating-One-Time-Reports-Setting-up-Report-Schedules
- https://documentation.getbite.com/openapi/v2/bite-api-v2
- https://getbite.zendesk.com/hc/en-us/articles/10404805470484-Reporting-API
- https://getbite.zendesk.com/hc/en-us/articles/13433960302868-Bite-order-webhooks-for-operators
- https://getbite.zendesk.com/hc/en-us/articles/49061341209364-Orders-Not-Appearing-on-Kitchen-Display-KDS
- https://getbite.zendesk.com/hc/en-us/articles/360035091252-Kiosk-Alerting-Rules
- https://getbite.zendesk.com/hc/en-us/articles/43320607036820-Kiosk-Order-Alerts
- https://getbite.zendesk.com/hc/en-us/articles/360059232492-Expo-Printer-Onboarding
- https://getbite.zendesk.com/hc/en-us/articles/42423872875412-Refunds
- https://getbite.zendesk.com/hc/en-us/articles/4404943556500-Viewing-transaction-logs-for-orders-in-Bite-Admin-Portal
- https://getbite.zendesk.com/hc/en-us/articles/360060759151-Changing-Dining-Option-or-Pickup-Time-Mid-Order
- https://getbite.zendesk.com/hc/en-us/articles/360060481752-Order-Throttling
- https://getbite.zendesk.com/hc/en-us/articles/4402003782932-Order-Lead-Times
- https://getbite.zendesk.com/hc/en-us/articles/42423175526676-Previous-Orders-Configuration-WIP
- https://getbite.zendesk.com/hc/en-us/articles/360060833911-Simple-Loyalty-Sign-Up
- https://getbite.zendesk.com/hc/en-us/articles/4433583711380-Incentivio-Loyalty-Integration
- https://getbite.zendesk.com/hc/en-us/articles/360051199311-Manually-Syncing-Menu-from-POS
- https://getbite.zendesk.com/hc/en-us/articles/42424010004116-Disable-Org-Summary-Reports
- https://getbite.zendesk.com/hc/en-us/articles/360058313812-Configuring-Dining-Options
- https://getbite.zendesk.com/hc/en-us/articles/43320710041108-Troubleshooting-an-Offline-Android-Elo-Kiosk
- https://getbite.zendesk.com/hc/en-us/articles/43320739051412-Troubleshooting-an-Offline-Android-Esper-Kiosk-English
- https://getbite.zendesk.com/hc/en-us/articles/360037683251-Changing-Credit-Card-Batching-Time
- https://getbite.zendesk.com/hc/en-us/articles/50311281983252-How-to-cancel-your-Bite-service-when-your-store-is-closing