Tillster

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

Upheld, and the premise is now the vendor's own positioning rather than our inference. Tillster places the POS among the things the operator already owns: the cited page offers to 'Connect seamlessly with the systems you already use, including POS, payments, loyalty, and delivery partners.' It is a digital-ordering layer, and its published tool set is six products -- a customer data platform, Order Manager, Menu Manager, a recommender, kiosk software and an offers and loyalty engine -- none of them a check-handling surface. The claim wants splitting by item, by seat, by even N-way and by arbitrary amount, plus merging after partial payment; across a 91-page corpus read 2026-09-09 -- the whole of www.tillster.com, closed as a census rather than assumed: the sitemap lists 92 URLs of which 91 return content, and an href fixpoint over every one of them surfaced 21 further internal links that all 301 into pages already listed (8 legacy product URLs into the current /solutions/ set, 11 legacy blog URLs into /blog), so the sitemap is the census here and not a floor. A fabricated sibling returns a hard 404 at 0 bytes, so absence on this host is distinguishable from a shell, `split check`, `split checks`, `merge check`, `combine checks`, `transfer check` and `table management` occur zero times, tokenised and as bare substrings alike, and the only occurrences of any seat word anywhere are two seats, one seating and one seated, none of them a check-splitting construct, against present-controls of kiosk in all 91 documents and pos in all 91. Note that the six-tool list is a navigation menu and therefore a floor on the product set, but a check-splitting product absent from the menu AND from every word of the corpus is not a cataloguing oversight. https://www.tillster.com/platform/integrations · retrieved 2026-09-09

Ships a first-party handheld ordering app running natively on the handheld device (not a remote/mirrored desktop session) that can send to kitchen and take a card payment tableside.

order-capture-native-handheld

Not scored by this record.

With the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen, and tender cash, and the vendor publishes what does and does not work offline.

order-capture-offline-order-entry

CLAIM: with the internet down, terminals/handhelds still create orders, apply modifiers, send to kitchen and tender cash, AND the vendor publishes what does and does not work offline. VERDICT: unknown -> partial/C. EVIDENCE (www.tillster.com/solutions/restaurant-kiosks): 'Operates on the local network to eliminate cloud latency and downtime.' and 'Continues functioning even during internet outages, ensuring uninterrupted service.'; (www.tillster.com/blog/kiosks-for-restaurants): kiosks are designed to 'remain operational even if internet connectivity is disrupted'; (www.tillster.com/blog/reliable-restaurant-kiosks): 'The most recent data is cached on each kiosk, so service continues even when cloud connectivity drops.' This is the same evidence that already grounds reliability-offline-order-entry and hardware-offline-mode at partial/C; this cell was left at unknown/F with a stale rationale ('kiosk offline behavior is not documented publicly') that the kiosk page contradicts. SHORTFALL: the only Tillster terminal is a guest self-order kiosk (no staff terminal or handheld); cash is not tendered on it ('Cash orders seamlessly routed to POS for employee-assisted payment.'); no published offline scope - 'offline mode', 'store and forward', 'local mode' are zero across the census; the sentence 'Core functions like ordering, payment, and kitchen routing should work offline' in reliable-restaurant-kiosks is buyer advice, not a Tillster statement, and is not cited as one. CORPUS: www.tillster.com sitemap.xml = 92 URLs, all fetched 200 (robots.txt has no Disallow; a nonsense path 404s, so no catch-all); the href fixpoint over the 92 bodies found 20 extra first-party paths and all 20 301 into sitemap URLs (e.g. /self-service-kiosk -> /solutions/restaurant-kiosks), so the sitemap is the census of the marketing host. pages.tillster.com is a separate event/webinar landing SPA (3 linked event pages; sitemap.xml 404) and is outside this bound. Retrieved 2026-09-16. https://www.tillster.com/solutions/restaurant-kiosks · retrieved 2026-09-16 adversarially verified

Offers a first-party self-order kiosk that renders the same menu and modifier tree as the POS with no separate menu build, and the vendor documents ADA/accessibility conformance for it. differentiator

order-capture-kiosk-first-party

Not scored by this record.

Supports drive-thru-specific order flow: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment.

order-capture-drive-thru

Not scored by this record.

Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.

order-capture-drive-thru-timers

Not scored by this record.

Vendor ships a first-party AI voice ordering agent for phone and/or drive-thru that injects orders directly as POS orders, or publishes a documented API partner program for third-party voice AI. differentiator

order-capture-voice-ai

Not scored by this record.

Supports order throttling: per-channel capacity limits per time slot with automatic quote-time extension when kitchen load exceeds a configured threshold. differentiator

order-capture-throttling

Not scored by this record.

Accepts future-dated/scheduled orders with a per-channel lead time and automatically injects them into the make queue at a computed fire time rather than on receipt.

order-capture-scheduled-orders

The call-center product page states 'Configurable prep-time and throttling rules to manage future order windows' and 'Visibility into active and scheduled orders for proactive kitchen coordination' - scheduled/future orders are a real order type, distinguished from active orders, with configurable windows. Named shortfall: fire-time injection is not described - nothing says the order enters the make queue at a computed fire time rather than on receipt - and scheduled ordering is only evidenced on the call-center channel; the web/mobile ordering page (solutions/restaurant-web-and-mobile-ordering) and kiosk page mention no order-ahead or pickup-time selection, and the ordering solutions page goes only as far as 'Configure promise times by disposition, product, and channel'. https://www.tillster.com/solutions/call-center-ordering-software · 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.

Supports modifier groups nested at least three levels deep, each level with independent min/max selection counts and a forced-selection (required) flag.

menu-pricing-nested-modifiers

Partial. Tillster's emn8 storyboard ordering engine (as served for the Jollibee PH tenant from responsive.tillster.com, Wayback id_ capture 2023-08-10, 10,958,224 b; host no longer resolves, so this is 2023 evidence of a retired storefront) carries per-step minimum/maximum selection counts and derives required-ness from the minimum: 'modList.maxQuantity=childToMatch.maxQuantity,modList.minimumQuantity=childToMatch.minimumQuantity,modList.requiresSelection=0<childToMatch.minimumQuantity'. Steps nest: an 'Encapsulation' / 'Mod Encapsulation' step holds childSteps, each with its own minimumQuantity/maxQuantity. The Ordering Web Api schema (v5.0.141-master, basePath /mobilem8-web-service/rest, uploaded to SwaggerHub by an integrator account, corroboration only) defines json_ConsolidatedStoryboardStep.childSteps as an array of json_ConsolidatedStoryboardStep, so the step type is self-recursive. SHORTFALLS: (1) no demonstrated three-level modifier nesting; the bundle reads at most storyboardSteps[0].childSteps[0].childSteps[0] for a weights list, and a 'resetCaptionFromChildStepsForComplexProducts' path flattens an encapsulation by copying childSteps[0] min/max up to the parent rather than rendering a group inside a group; (2) no required flag separate from min > 0; (3) evidence is a single-tenant consumer web ordering build, not POS or back-office menu configuration documentation. https://web.archive.org/web/20230810103557id_/https://responsive.tillster.com/responsive/jb-ph/1691125272/phApp.js · retrieved 2026-09-15 adversarially verified

A single modifier can carry different prices depending on the parent item and the selected size, configured as a matrix rather than by duplicating the modifier.

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

330th, NEW SURFACE AND A MOVE: unknown -> partial/B. SURFACE: Tillster's PRODUCTION operator console for the new Tillster Commerce Engine, https://admin-txp.prod.tce.tillster.com/ (Next.js/Turbopack, x-powered-by: Next.js, CloudFront; found from a certspotter listing of tillster.com that the 2026-09-17 crt.sh pass did not hold: admin-txp.prod.tce.tillster.com, prod not staging). Its /login, /brand and /internal pages are anonymous 200s and ship the chunk table inline; a script-loader census fetched to a FIXPOINT gives 117 chunk references / 116 files / 4,814,431 bytes in 2 rounds with 0 misses (nonsense control: /_next/static/chunks/zzznope123.js = 404, 9 bytes, so no soft-200). EVIDENCE for the parent-item axis, from the platform's own pricing module (js/0m-dnzj16mub_.js, 290,464 b): the shipped code exports `applyContextualModifierPricing` = `function n(e,t){let r=t?.price,n=t?.dispositionPricing,s=void 0!==r,a=void 0!==n;return s||a?e.map(e=>({...e,...s?{price:r}:{},...a?{dispositionPricing:i(e.dispositionPricing,n)}:{}})):e}`, and it is applied where a PARENT product's own modifier-group reference is resolved: `let h=(0,u.applyContextualModifierPricing)(p,o);return s.push({...m,...void 0!==o.price?{price:o.price}:{},...void 0!==o.dispositionPricing?{dispositionPricing:(0,u.mergeDispositionPricing)(m.dispositionPricing,o.dispositionPricing)}:{},displayedInstructions:...})`. `o` is the entry inside `product.modifierGroups[].modifiers[]`, whose id is the composite `"<modifierId>#<instructionId>"` (`String(e?.id??"").split("#")`), and `m`/`p` are the SHARED modifier and its instructions looked up by that id from the catalog's global `modifiers`/`instructions` maps. So one shared modifier option is referenced by id from each parent item and the parent's reference may override that option's price (and its per-disposition prices) WITHOUT duplicating the modifier - i.e. the platform does carry per-parent-item modifier prices as an override matrix, and the price-resolution helper `getClassificationUpcharge(product,dispositionPricing,dispositionType)` adds a second axis (service type/disposition). SHORTFALL (why partial, not yes): the SIZE conjunct is unobserved. This corpus has no size entity at all - a tokenised census of the 116 files gives 1,120 `size` hits and every non-layout one is CSS/typography/image sizing (`fontSize`, `imageSizes`, `deviceSizes`, `ResizeObserver`), POISON already named in the 327th note; `sizeGroup`, `priceBySize`, `variant` 0. Sizes in this model appear to be ordinary catalog products or instructions, which the same override reaches, but no menu document is readable anonymously to prove a parent x size matrix (the mobilem8 menu service returns empty envelopes without a session - see the 328th note - and the TCE APIs api-us-east-1.tce.tillster.com and api-txp-us-east-1.prod.tce.tillster.com return a uniform 403/404 on /v3/api-docs, /openapi.json, /swagger/v1/swagger.json and a nonsense control alike). CORPUS BOUND: this census covers the TXP Experience Designer and the consumer renderer it embeds, not the authenticated catalog/reporting modules. Retrieved 2026-09-18. https://admin-txp.prod.tce.tillster.com/_next/static/chunks/0m-dnzj16mub_.js · retrieved 2026-09-18 adversarially verified

Supports modifier quantity tiers (light / regular / extra / double) with a configurable price multiplier per tier, distinct from adding the modifier twice.

menu-pricing-topping-quantity-tiers

CLAIM: modifier quantity tiers (light/regular/extra/double) with a configurable price multiplier per tier, distinct from adding the modifier twice. VERDICT: unknown -> partial/B. Tillster's ordering engine models modifier WEIGHTS as named tiers, each carrying its own price, with tenant config choosing which tiers charge and a double-topping setting; SHORTFALL: the price is an absolute per-weight menu price, not a multiplier, and no back-office documentation of configuring it is public. EVIDENCE (https://order.baskinrobbins.com/1782924863/phApp.js): constant MODIFIER_WEIGHTS_TYPES / .constant("MODIFIER_WEIGHTS",{ADD:{key:"Add",value:"W Add",...},AS_IS:{key:"As Is",value:"W As IS",...},REMOVE:{key:"Remove",value:"None",...},EXTRA:{key:"Extra",value:"W EXTRA",...},SIDE:{key:"Side",value:"SIDE",...},NO:{key:"No",value:"W NO",...},WITH:{key:"With",value:"W WITH",...},NONE:{...value:["W NONE"]...},NORMAL:{key:"Normal",value:["W NORMAL"],...},...,ALL_WEIGHT_TAGS:["Whole","As Is","Add","Extra","Side","Light","With","Sub"]}); per-weight price: "modifierWeightName===MODIFIER_WEIGHTS.EXTRA.value&&(menuItem.weightTypes[MODIFIER_WEIGHTS.EXTRA.value]=modifierWeights[i].menuItemPrice),modifierWeightName===MODIFIER_WEIGHTS.ADD.value&&(menuItem.weightTypes[MODIFIER_WEIGHTS.ADD.value]=modifierWeights[i].menuItemPrice)"; tier-priced (not duplicate-line) quantity change: "const PAID_WEIGHTS=$rootScope.appConfig.get(\"multistep.paidWeights\")||[]" and "0<=PAID_WEIGHTS.indexOf(itemWeights[i].menuItemName)?itemWeights[i].menuItemName===MODIFIER_WEIGHTS.EXTRA.value&&0===oldQuantity?($scope.updatedItemPrice+=(quantityDifference-1)*itemWeights[i].menuItemPrice" ; double tier: "DOUBLE_TOPPING_WEIGHT=$rootScope.appConfig.get(\"builder.doubleToppingWeight\")" and "hasTagsFilter(weight,[\"whole\",\"double\"])"; cart line items: "multistep.paidWeightsForRolledUpPrice", "menu.disregardAsIsPrice". Tokens 'multiplier' x12 are layout (offsetMultiplier) and "calorieMultiplierForWeights" x18 is calories, not price (poison). SURFACE (new, 2026-09-17): Tillster's production white-label web-ordering bundle https://order.baskinrobbins.com/1782924863/phApp.js (12,075,163 b, Angular 'emn8' engine, HTML Last-Modified 2026-07-08). Provenance: DNS order.baskinrobbins.com CNAME www-br-us.tillster.com; the page's window.k8sEnv names "nativeAppVersionInfo":"https://brm-cdn.tillster.com/us/prod/data/app-manifest.json". No source map (phApp.js.map returns the 4,146 b SPA shell, same as a nonsense .map path). Found after crt.sh %.tillster.com (533 names): every host probed; 530 are NXDOMAIN/timeouts (internal k8s/rabbitmq/sync/api), live ones are www, dev/stage/prod.tce (403 {"message":"Forbidden"}), prod-snd-a-* ({"message":"no services for this route"} on every path incl. /swagger-ui.html, /v3/api-docs) and prod-pds-a-ape1 (Tomcat 404 on all doc paths) - no anonymous spec or admin SPA. The bundle is the consumer ordering front end: it cannot bound back-office features. Retrieved 2026-09-17. https://order.baskinrobbins.com/1782924863/phApp.js · retrieved 2026-09-17 adversarially verified

Item base price can be defined as a grid across two variant axes (e.g. size x crust/preparation) with a per-cell price override. differentiator

menu-pricing-size-style-matrix

Not scored by this record.

Items can define an included-modifier allowance (e.g. three toppings included) that automatically charges only for overage and credits or forbids substitutions per configuration. differentiator

menu-pricing-included-allowance

Not scored by this record.

Supports combo/meal construction where components can be swapped with a price delta, and the system can automatically detect and convert eligible a-la-carte items in the cart into the combo price.

menu-pricing-combos

Not scored by this record.

Upsell/suggestive-sell prompts can be configured per item and per channel (POS, kiosk, online), and the vendor reports attach-rate on those prompts. differentiator

menu-pricing-upsell-prompts

Not scored by this record.

A single 86 action propagates automatically to POS, KDS, the vendor's own online ordering, kiosk, and connected third-party marketplaces, with a documented propagation latency.

menu-pricing-86-propagation

Not scored by this record.

Supports per-item countdown/par counts that decrement on sale and automatically 86 the item at zero, with a scheduled auto-restore. differentiator

menu-pricing-countdown-auto-86

Not scored by this record.

Menus, individual items, and prices can be scheduled to activate and deactivate automatically by day and time in the location's own timezone.

menu-pricing-dayparting

Not scored by this record.

Supports distinct price books per channel (dine-in, pickup, delivery, kiosk, each third-party marketplace) including percentage-markup rules applied to a base price rather than manual per-item entry.

menu-pricing-channel-price-books

Not scored by this record.

Supports dual pricing / cash-discount at the item level with the card price displayed as the base price, applied consistently across POS, kiosk, and online ordering, and printed on the receipt. differentiator

menu-pricing-dual-pricing

Not scored by this record.

Menu changes can be staged as an effective-dated version, previewed before publish, and rolled back to a prior version after publish. differentiator

menu-pricing-versioning-effective-dates

Not scored by this record.

Supports a central corporate menu template pushed to locations with field-level governance controlling which attributes a location may override. differentiator

menu-pricing-franchise-hierarchy

Not scored by this record.

Stores allergen flags and nutrition values per item and publishes them to online ordering and third-party menus, and can derive nutrition from linked recipe components rather than manual entry.

menu-pricing-allergen-nutrition

Not scored by this record.

Menu items and modifiers can be linked to recipes/bills of materials so that a sale depletes theoretical inventory and yields item-level theoretical food cost. differentiator

menu-pricing-recipe-linkage

Not scored by this record.

Pushes menus to third-party marketplaces through a certified direct integration (not scraping or a menu-management middleman) and surfaces per-item sync status and rejection errors to the operator.

menu-pricing-3p-menu-push

Not scored by this record.

Supports rule-based dynamic pricing where item price varies automatically by time, demand, or channel, with configurable floor/ceiling guardrails.

menu-pricing-dynamic-pricing

Not scored by this record.

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. VERDICT: unknown -> partial/C. EVIDENCE (www.tillster.com/solutions/restaurant-kiosks, 'Payments & security' block): 'EMV and digital wallet support with point-to-point encryption for secure transactions.'; (www.tillster.com/blog/reliable-restaurant-kiosks): Tillster supports 'EMV terminals with point-to-point encryption (P2PE)'. SHORTFALL: the readers are partner EMV terminals integrated into the kiosk, not Tillster first-party hardware; NFC/contactless card tap is never named for the kiosk ('NFC' 0 hits; 'contactless' 8 hits, none about kiosk card acceptance); Apple Pay / Google Pay appear only in buyer advice about mobile-app checkout (blog/top-restaurant-mobile-app-features: 'Support Apple Pay, Google Pay, PayPal, and saved tokenized cards'), not terminal acceptance. 'Digital wallet support' on the kiosk implies wallet tap but does not name the wallets. CORPUS: www.tillster.com sitemap.xml = 92 URLs, all fetched 200 (robots.txt has no Disallow; a nonsense path 404s, so no catch-all); the href fixpoint over the 92 bodies found 20 extra first-party paths and all 20 301 into sitemap URLs (e.g. /self-service-kiosk -> /solutions/restaurant-kiosks), so the sitemap is the census of the marketing host. pages.tillster.com is a separate event/webinar landing SPA (3 linked event pages; sitemap.xml 404) and is outside this bound. Retrieved 2026-09-16. https://www.tillster.com/solutions/restaurant-kiosks · retrieved 2026-09-16 adversarially verified

Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. differentiator

payments-softpos-tap-to-pay

Not scored by this record.

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

The ordering solutions page's payments block reads 'Store guest payment preferences securely with tokenization. Support digital wallets, stored cards, and gift cards.' That establishes gift cards as an accepted tender in Tillster's own ordering channels. Named shortfall: nothing on the site describes a first-party Tillster gift card program - no issuance, no real-time balance lookup, no cross-location in-store redemption - and the loyalty page (solutions/restaurant-loyalty-and-promotions) covers points, coupons and offer wallets with no stored-value product. Tillster is a digital-ordering layer over the brand's POS, so card issuance and balance authority appear to sit with the brand's POS or processor. https://www.tillster.com/solutions/restaurant-ordering · 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

Checked 2026-08-04: Tillster takes payment in its own channels (kiosk EMV/wallets, web/mobile vaulted-card checkout), so refund/void handling of digital transactions is in scope, but no page describes it. solutions/restaurant-ordering's payments block covers tokenization, wallets, stored cards and gift cards with no refund or void wording; platform/restaurant-technology's security block (PCI DSS, MFA, 'Secure APIs') has no role model, approval flow or audit-log language; the kiosk page routes cash orders 'to POS for employee-assisted payment'. A client help centre at por-us-clientportal.tillster.com is indexed by search engines but the host no longer resolves (DNS NXDOMAIN), and the API portal at api-docs.dev.tillster.com is Cognito-gated with its S3 spec bucket returning HTTP 403. Unresolved. || 327th: 327th, NEW SURFACE and an explicit negative result worth recording so nobody re-mines it: Tillster's shipped ordering application (5.32 M chars of the Angular app served for order.baskinrobbins.com) contains NO void/refund/manager-authorisation surface at all - tokenised, `refund` 0 and `manager` 1. POISON NAMED, and it is severe: a raw count of `void` in this bundle is 1,072 and EVERY one is the JavaScript idiom `void 0` inside jQuery/Sizzle and Angular internals; the single `manager` hit is 'Expected a Google Tag Manager ID'; the 4 `override` hits are the CSS property table (`font-language-override`) and a coupon-replacement prompt (`cart.label.coupon.override.body`). This is a guest-facing ordering client, so its silence is expected and does NOT bound the claim - Tillster ships no POS terminal where a void or comp would be authorised, and its operator console documentation (client.help.tillster.com) is a gated Jira Service Desk. Retrieved 2026-09-18. || 330th: 330th, NEW SURFACE, negative and bounded to what it covers. The production TXP operator console (admin-txp.prod.tce.tillster.com, 117-chunk / 4.81 MB fixpoint census, 0 misses) carries no void/refund/authorisation surface: tokenised, `refund` 0, `audit` 0, `manager` 0, `approval` 0; `void` 3,468 is entirely the JavaScript `void 0` idiom (POISON, same trap as the 327th). Its payment surface is the PGAAS gateway client only - the endpoint registry exposes PGAAS.TRANSACTIONS, PGAAS.PAYMENT_METHOD, PGAAS.APPLE_PAY_SESSION (48 endpoint constants in total, all consumer-side: ACCOUNT.*, CART.*, MENU.*, LOYALTY.*, COUPONS.*, STORES.*, ORDER) and the order lifecycle enumeration ends at `Order Canceled`/`Order Failed` with no void or refund state. BOUND: the anonymously reachable part of this console is the Experience Designer plus the consumer renderer it embeds, NOT the authenticated order-management modules, so this does not carry a `no` - it only shows that the platform's published/shipped consumer-and-design surface models no approver-attributed void or refund. Retrieved 2026-09-18. adversarially verified

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.

Items route to specific KDS stations by item, category, order type, or revenue center, with routing rules configurable per location without vendor involvement.

kitchen-station-routing

CLAIM: items route to specific KDS stations by item/category/order type/revenue centre, configurable per location without vendor involvement. VERDICT: unknown -> no/C. Tillster ships no KDS (see hardware-kds, kitchen-expo-consolidation, kitchen-bump-bar-hardware, all no/C on this census); kitchen routing is handed to the brand's POS/KDS: (www.tillster.com/solutions/restaurant-ordering) 'Route orders directly to POS and kitchen systems for faster throughput and fewer errors.'; (www.tillster.com/blog/kiosks-for-restaurants) 'Tillster’s kiosk software connects directly to a restaurant’s POS and kitchen display system (KDS)'. BOUND: CORPUS: www.tillster.com sitemap.xml = 92 URLs, all fetched 200 (robots.txt has no Disallow; a nonsense path 404s, so no catch-all); the href fixpoint over the 92 bodies found 20 extra first-party paths and all 20 301 into sitemap URLs (e.g. /self-service-kiosk -> /solutions/restaurant-kiosks), so the sitemap is the census of the marketing host. pages.tillster.com is a separate event/webinar landing SPA (3 linked event pages; sitemap.xml 404) and is outside this bound. CONTROLS: 'stations' 1 (gas stations - poison), 'prep station' 0, 'revenue center' 0, 'routing rule(s)' 0; 'kitchen routing' 2 hits, both buyer advice ('Core functions like ordering, payment, and kitchen routing should work offline'; an FAQ listing 'kitchen routing through a KDS' among features to look for), neither describes a Tillster station-routing configuration. Ordering WS spec (SwaggerHub Nagarro89/ordering-web_api, 211 ops): 0 station/kitchen operations. Retrieved 2026-09-16. https://www.tillster.com/platform · retrieved 2026-09-16 adversarially verified

An expo screen consolidates items from multiple prep stations into a single order view and only marks the order complete when every contributing station has bumped its items.

kitchen-expo-consolidation

Tillster enumerates its product set as Customer Data Platform, Order Manager, Menu Manager, Recommender AI, Kiosk Software and Offers & Loyalty Engine; the solutions set is by channel (kiosk, web/mobile, delivery & marketplaces, call center, in-store). No expo screen, prep station or kitchen display product appears in that enumeration or anywhere else on the site, and the kiosk page places kitchen-side execution with the store POS ('Directly connected to the store POS for real-time pricing, menu item, and stock updates'). Order Manager consolidates orders across channels for fulfillment visibility, not station bumps. Expo consolidation belongs to the brand's own POS/KDS (Oracle MICROS, NCR Aloha, PAR Brink, Toast, Xenial and others listed on platform/integrations). https://www.tillster.com/platform · retrieved 2026-08-04

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

Tillster enumerates its full tool set - Customer Data Platform, Order Manager, Menu Manager, Recommender AI, Kiosk Software, Offers & Loyalty Engine - and no KDS appears in it; the kiosk page assigns kitchen-side execution to the store POS ('Directly connected to the store POS for real-time pricing, menu item, and stock updates') and the ordering page routes 'orders directly to POS and kitchen systems'. With no kitchen display product there is no bump-bar or keypad hardware to support - the same enumeration that grounds the kitchen-expo-consolidation 'no'. Bump bars belong to the brand's own KDS (Oracle MICROS, NCR Aloha, PAR Brink, Toast, Xenial and other POS partners on platform/integrations). https://www.tillster.com/platform · retrieved 2026-08-04

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.

Product includes a native in-house driver module: drivers are first-class entities with clock-in/out, assignment state (in-store / on-run / returning), and per-driver run history reportable from the POS itself (not via a third-party add-on).

delivery-driver-roster

CLAIM: native 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 product itself. VERDICT: unknown -> partial/C. The old rationale ('channel/marketplace management, not an in-house driver roster') is contradicted by the page that already grounds delivery-dispatch-board partial/C. EVIDENCE (www.tillster.com/solutions/restaurant-delivery-and-marketplaces, section 'Take better control of your owned delivery fleet'): 'by managing in-house drivers, marketplaces, and orders in one centralized dashboard.'; Branded driver app - 'Keep drivers connected with real-time order assignments, customer info, and delivery updates.'; Multi-order delivery support - 'Configure how many orders each driver can fulfill per run, based on vehicle type or time window.'; Driver tracking - 'Order Manager shows store teams active locations, ETAs, and delivery statuses at a glance.'; Driver KPIs in-app - 'Delivery drivers can view planned vs. actual drive times, on-time percentages, and completed deliveries.' MET: drivers are named entities with per-driver run metrics and live delivery status. SHORT: no driver clock-in/out ('clock-in'/'clock in' 0 hits; 'shift' hits are prose - poison); no in-store/on-run/returning state model; per-driver history is shown to the driver in-app, and back-office reporting is described per store/fleet. Tillster is not a POS, so 'from the POS itself' is read as from Tillster's Order Manager. CORPUS: www.tillster.com sitemap.xml = 92 URLs, all fetched 200 (robots.txt has no Disallow; a nonsense path 404s, so no catch-all); the href fixpoint over the 92 bodies found 20 extra first-party paths and all 20 301 into sitemap URLs (e.g. /self-service-kiosk -> /solutions/restaurant-kiosks), so the sitemap is the census of the marketing host. pages.tillster.com is a separate event/webinar landing SPA (3 linked event pages; sitemap.xml 404) and is outside this bound. Retrieved 2026-09-16. https://www.tillster.com/solutions/restaurant-delivery-and-marketplaces · retrieved 2026-09-16 adversarially verified

Provides a dedicated dispatch/expo screen showing undispatched orders, driver availability, and elapsed time per order, with multi-order run batching (assigning 2+ orders to one driver as a single run).

delivery-dispatch-board

Tillster ships a first-party delivery product the earlier pass missed: 'Order Manager shows store teams active locations, ETAs, and delivery statuses at a glance' (a store-facing delivery screen), a branded driver app with 'real-time order assignments', digital proof of delivery, and multi-order runs - 'Configure how many orders each driver can fulfill per run, based on vehicle type or time window' - plus hybrid overflow to third-party providers when demand spikes. Named shortfall: the page never describes an undispatched-order queue, a driver-availability display or an elapsed-time-per-order timer, and whether assignment is a manual dispatch action or automatic is unstated; this is a feature page, not an operator guide. https://www.tillster.com/solutions/restaurant-delivery-and-marketplaces · retrieved 2026-08-04

Dispatch includes a live map view with geocoded stops and system-generated route sequencing (turn order optimization) for a multi-stop run, not just a static address list. differentiator

delivery-route-map

Not scored by this record.

Captures live driver GPS position from a driver-facing mobile app and surfaces it back to the dispatch screen. differentiator

delivery-driver-tracking

Not scored by this record.

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.

Menu, pricing, modifiers, and photos publish from the POS master menu out to connected third-party marketplaces, including channel-specific price markups, without maintaining a separate menu in each portal.

delivery-menu-push

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.

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

First-party web and mobile ordering on the brand's own identity is a core product line, integrated to the brand's POS; commission model is not stated but this is not a marketplace. https://www.tillster.com/solutions · retrieved 2026-08-01

The web/app ordering menu is generated from the same POS menu record as in-store — one item edit propagates to all first-party digital channels without a separate digital menu build.

digital-menu-single-source

Central menu management propagates across kiosk, web, mobile and delivery channels, but the source of truth is Tillster's menu system, not the POS record. https://www.tillster.com/solutions · retrieved 2026-08-01

Vendor offers a branded native iOS and Android ordering app (published under the restaurant's own brand in the App Store/Play Store), not only a mobile web page or a shared multi-restaurant marketplace app. differentiator

digital-native-app

Not scored by this record.

Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels.

digital-account-saved-payment

Saved tokenized payment is documented across channels: 'Store guest payment preferences securely with tokenization. Support digital wallets, stored cards, and gift cards' (solutions/restaurant-ordering) and 'Offer tokenized, encrypted checkout on every platform, with vaulted cards and mobile wallets' (solutions/restaurant-web-and-mobile-ordering), with loyalty accrual/redemption 'seamlessly across web and app journeys' implying a persistent guest identity. Named shortfall: saved delivery addresses are described nowhere, and one-tap reorder of a previous order is only evidenced on the agent-assisted call-center channel ('Quick reorder functionality displays previous guest orders instantly', solutions/call-center-ordering-software) - no guest-facing reorder on web/mobile is documented. https://www.tillster.com/solutions/restaurant-ordering · retrieved 2026-08-04

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.

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 customer data platform plus loyalty engine is marketed as unifying guests across ordering channels; dedup/merge rules and POS in-store merge are not documented. https://www.tillster.com/solutions · retrieved 2026-08-01

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

327th, NEW EVIDENCE from inside Tillster's own shipped ordering application (order.baskinrobbins.com serves a Tillster-built Angular app whose runtime config points at Tillster infrastructure - `nativeAppVersionInfo: https://brm-cdn.tillster.com/us/prod/data/app-manifest.json` - so the code is Tillster's, deployed under a client brand). CLAIM: at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configurable program types. VERDICT: partial. EVIDENCE: the loyalty state object the app maintains carries points, visits AND tier as first-class, independently populated fields - `{...points:0, printedCardNumber:"", program:{}, referralCode:"", rewardBalances:[], tier:"", transactions:[], visits:null, visitsData:{}, walletInfo:[] ...}` - and there are separate code paths for each: `$scope.showLoyaltyVisits = () => !!($scope.loggedIn && null !== $scope.loyalty.visits)` reading `MAX_VISITS = appConfig.get("loyalty.paytronix.maxVisits")` and `VISITS_WALLET_CODES = appConfig.get("loyalty.paytronix.visitsWalletCodesToCheck")`, alongside a points/reward path (`pointCost`, `rewardBalances`) and a tier path (`getLoyaltyTierNameById(loyalty.tier)`). So two of the three accrual models (points and visit count) plus tiers are supported in the shipped product. WHY ONLY PARTIAL: the accrual engine is a THIRD PARTY - every symbol is namespaced `loyalty.paytronix.*` / `paytronixLoyaltyService`, with `USE_DIP_LOYALTY = appConfig.get("loyalty.paytronix.useDIPLoyalty")` switching between Paytronix and Tillster's own DIP loyalty - and Tillster publishes nothing that presents these as operator-CONFIGURABLE program types, which the claim requires. Retrieved 2026-09-18. https://order.baskinrobbins.com/ · retrieved 2026-09-18 adversarially verified

Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator

guest-loyalty-tiers

Not scored by this record.

Documents explicitly what loyalty lookup, accrual, and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). differentiator

guest-loyalty-offline-behavior

Not scored by this record.

Offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. differentiator

guest-loyalty-offer-stacking-rules

Not scored by this record.

Offers can be issued to a dynamically defined audience (rules over recency, frequency, spend, or items purchased) rather than only broadcast to the whole list. differentiator

guest-loyalty-targeted-offers

Not scored by this record.

Automatically computes recency/frequency/monetary or equivalent lifecycle segments (new, regular, at-risk, lapsed, VIP) without the operator building the queries. differentiator

guest-loyalty-rfm-segmentation

Not scored by this record.

Ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns rather than one-off manual sends.

guest-loyalty-lifecycle-automation

Personalized/targeted offer automation is a marketed capability; named always-on lifecycle triggers are not enumerated. https://www.tillster.com/solutions · retrieved 2026-08-01

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.

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

Upheld and now measured. The claim wants employees clocking in and out at a POS terminal with a PIN, badge or card, and Tillster sells no POS terminal -- the cited platform page enumerates the whole tool set as a customer data platform, Order Manager, Menu Manager, a recommender, kiosk software and an offers and loyalty engine. Across a 91-page corpus read 2026-09-09 -- the whole of www.tillster.com, closed as a census rather than assumed: the sitemap lists 92 URLs of which 91 return content, and an href fixpoint over every one of them surfaced 21 further internal links that all 301 into pages already listed (8 legacy product URLs into the current /solutions/ set, 11 legacy blog URLs into /blog), so the sitemap is the census here and not a floor. A fabricated sibling returns a hard 404 at 0 bytes, so absence on this host is distinguishable from a shell, `clock in`, `clock-in`, `time clock`, `timekeeping`, `payroll` and `employee management` occur zero times, tokenised and as bare substrings. The word labor does read 28 times in 15 documents and every one is an argument about labour COST -- kiosks reducing front-line pressure, self-service offsetting staffing shortages -- never a labour module. The nearest thing Tillster ships to a staff-facing device is the kiosk, which the vendor describes as guest-operated self-ordering. https://www.tillster.com/platform · retrieved 2026-09-09

Captures a photo at punch (or performs facial verification) attached to the timecard entry, with a photo-only mode available that stores no biometric template. differentiator

labor-photo-punch-verification

Not scored by this record.

Supports mobile clock-in restricted by geofence or location validation for staff who do not punch at a fixed terminal.

labor-geofenced-mobile-punch

Not scored by this record.

Records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, with the behavior documented. differentiator

labor-offline-time-punch

Not scored by this record.

Permissions are grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers.

labor-granular-rbac

CLAIM: permissions grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not fixed cashier/manager/admin tiers. VERDICT: partial - a configurable role/permission model exists, but the evidenced grants are menu/commerce back-office actions, not the register actions the claim enumerates. EVIDENCE (tillster.com/blog/restaurant-menu-management): 'Permissions are role-based, allowing organizations to define who can edit pricing, modify items, launch promotions, or manage regional configurations. This ensures local agility without sacrificing brand control.' This corrects the prior note's 'no user-role model' finding: Tillster's back office does ship configurable per-action, per-region role grants. SHORTFALL: the grantable actions shown are CMS/menu actions (edit pricing, modify items, launch promotions, manage regional configurations), not the point-of-sale operational grants in the claim (void, comp, discount, refund, drawer open) - Tillster ships no POS terminal; scoping is described as regional, not confirmed per-individual-location; no full permission catalogue is published (that would live in the Cognito-gated admin docs). Grade C (vendor feature page). Retrieved 2026-09-16. https://www.tillster.com/blog/restaurant-menu-management · retrieved 2026-09-16 adversarially verified

Manager overrides and approvals are attributed to the individual approver and written to an immutable audit trail queryable after the fact.

labor-manager-override-audit

CLAIM: manager overrides and approvals attributed to the individual approver and written to an immutable audit trail queryable after the fact. VERDICT: still unknown - the only audit/approval language found is about MENU changes, not transaction overrides. EVIDENCE (tillster.com/blog/restaurant-menu-management): 'For organizations [needing governance] ... the system ensures that menu changes are deliberate, auditable, and aligned across every location and channel' plus role-based edit permissions. This shows approval workflow + auditing exist for menu/config changes, but nothing about void/comp/discount/price-override events being attributed to the approving manager or written to an immutable, queryable trail (Tillster ships no POS terminal where such overrides would occur). No back-office audit-report catalogue is published; the client help centre at client.help.tillster.com is a Jira Service Management portal that 303-redirects every request to login. Retrieved 2026-09-16. || 330th: 330th, NEW SURFACE, negative: the production TXP operator console (admin-txp.prod.tce.tillster.com, 117-chunk / 4,814,431-byte fixpoint census, 0 misses, nonsense control 404/9 b) contains no override, approval or audit machinery - word-boundary tokenised, `audit` 0, `approval` 0, `manager` 0, `Roles` 0, `Permissions` 0, `Users` 0; the 18 `override` hits are the CSS property table and a coupon-replacement prompt (POISON, as in the 327th). The console's own human sign-in is Okta/Auth0, i.e. an identity provider rather than an in-product approver attribution model. BOUND: the anonymous slice of this console is the Experience Designer and the consumer renderer, so this is not a census of Tillster's authenticated back-office; the cell stays unknown. Retrieved 2026-09-18. adversarially verified

Builds and publishes employee shift schedules inside the same platform that holds the timekeeping data, rather than requiring a third-party scheduling app. differentiator

labor-native-scheduling

Not scored by this record.

Generates recommended staffing levels or labor hours by daypart from the operator's own POS sales history, not just a static template. differentiator

labor-demand-labor-forecast

Not scored by this record.

Displays labor cost as a percentage of sales in real time during service on a manager view or POS, not only in end-of-day or next-morning reports. differentiator

labor-realtime-labor-percent

Not scored by this record.

Warns or blocks at clock-in when an employee is approaching or would cross a configured overtime threshold, before the overtime is incurred. differentiator

labor-overtime-prevention

Not scored by this record.

Configures meal and rest break rules per state or jurisdiction, prompts required break attestation, and flags missed breaks for premium pay. differentiator

labor-break-compliance-by-state

Not scored by this record.

Supports predictive-scheduling ordinances by tracking advance-notice deadlines for published schedules and calculating predictability pay owed for employer-initiated changes.

labor-fair-workweek-support

Not scored by this record.

Enforces minor-labor restrictions (age-based maximum hours, prohibited time windows, school-day limits) at both scheduling and clock-in.

labor-minor-labor-rules

Not scored by this record.

Computes tip pooling and tip-outs automatically per shift from configurable rules (percentage of sales, hours worked, points, or role), rather than requiring a manual spreadsheet.

labor-tip-pooling-rules

Not scored by this record.

Retains a per-shift, per-employee record of tips received, amounts contributed to the pool, and amounts distributed from the pool, exportable for audit.

labor-tip-distribution-audit-trail

Not scored by this record.

Payroll export separates cash from charged qualified tips and carries a Treasury tipped-occupation code, supporting the W-2 Box 12 code TP and Box 14b reporting required for tax year 2026. differentiator

labor-qualified-tips-w2-reporting

Not scored by this record.

Vendor processes payroll itself as a first-party product (tax filing and direct deposit), as opposed to exporting to a third-party payroll provider only. differentiator

labor-native-payroll

Not scored by this record.

Exports timecards, wages, and tips in documented formats or via direct integration for at least two major payroll providers (e.g. Gusto, ADP, Paychex, QuickBooks).

labor-payroll-export-formats

Not scored by this record.

Employees can request shift swaps or claim open shifts in a self-service app, subject to a manager approval workflow that enforces overtime and role eligibility. differentiator

labor-shift-swap-workflow

Not scored by this record.

Provides digital new-hire onboarding that collects W-4 and I-9 documentation and supports E-Verify submission.

labor-digital-onboarding-i9

Not scored by this record.

Reports per-employee sales performance metrics (average check, items or category attachment rate, void and comp rate) by server or cashier. differentiator

labor-server-performance-metrics

Not scored by this record.

Supports multi-level recipe/BOM costing where a recipe can contain sub-recipes (prep items) and plate cost recalculates automatically when any component ingredient's cost changes.

inventory-recipe-bom-costing

Upheld and now measured rather than argued from the catalogue alone. Across a 91-page corpus read 2026-09-09 -- the whole of www.tillster.com, closed as a census rather than assumed: the sitemap lists 92 URLs of which 91 return content, and an href fixpoint over every one of them surfaced 21 further internal links that all 301 into pages already listed (8 legacy product URLs into the current /solutions/ set, 11 legacy blog URLs into /blog), so the sitemap is the census here and not a floor. A fabricated sibling returns a hard 404 at 0 bytes, so absence on this host is distinguishable from a shell, `bill of materials`, `theoretical usage`, `unit conversion`, `stock count`, `cycle count` and `par level` occur zero times, tokenised and as bare substrings; `recipe` reads exactly once and `food cost` exactly once, both inside blog essays -- an international-expansion piece and a menu-design piece -- and neither describes a Tillster product. Multi-level recipe costing with sub-recipes and automatic plate-cost recalculation is a back-office product Tillster does not have and does not claim; its published tool set is a customer data platform, Order Manager, Menu Manager, a recommender, kiosk software and an offers and loyalty engine, and Menu Manager is a menu-publishing surface for pricing and availability across channels, not a costing engine. https://www.tillster.com/platform · retrieved 2026-09-09

Stores purchase unit, recipe unit, and count unit per item with explicit conversion factors, plus a yield/waste percentage applied to raw-to-usable conversion.

inventory-unit-conversion-yields

Upheld and now measured. The claim wants a purchase unit, a recipe unit and a count unit per item with explicit conversion factors and a yield or waste percentage on the raw-to-usable step. Across a 91-page corpus read 2026-09-09 -- the whole of www.tillster.com, closed as a census rather than assumed: the sitemap lists 92 URLs of which 91 return content, and an href fixpoint over every one of them surfaced 21 further internal links that all 301 into pages already listed (8 legacy product URLs into the current /solutions/ set, 11 legacy blog URLs into /blog), so the sitemap is the census here and not a floor. A fabricated sibling returns a hard 404 at 0 bytes, so absence on this host is distinguishable from a shell, `unit conversion`, `yield`, `par level`, `stock count`, `cycle count` and `theoretical usage` occur zero times, tokenised and as bare substrings. The one term that is NOT assertable here is waste: it reads 44 times in 13 documents, but the sense is food waste as a business problem that better forecasting reduces, concentrated in a blog post on reducing food waste through online ordering -- it is never a yield percentage on an inventory item. Tillster publishes no inventory item record at all, so there is nothing for a conversion factor to hang on. https://www.tillster.com/platform · retrieved 2026-09-09

Produces a theoretical-vs-actual usage variance report per item for a defined count period, showing theoretical usage from POS sales times recipe, actual usage from counts plus receipts, and the variance in both units and currency. differentiator

inventory-theoretical-vs-actual

Not scored by this record.

Depletes ingredient on-hand quantities in near real time as orders are fired at the POS, including depletion driven by modifier selections, not only in an end-of-day batch. differentiator

inventory-realtime-depletion

Not scored by this record.

Automatically 86s (marks unavailable) menu items on the POS, online ordering, and connected third-party delivery menus when a component ingredient hits zero or a configured threshold. differentiator

inventory-86-auto-sync

Not scored by this record.

Supports full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts.

inventory-count-modes

Upheld and now measured. The claim wants full physical counts, ad-hoc spot counts and scheduled recurring cycle counts, each with its own variance history. Across a 91-page corpus read 2026-09-09 -- the whole of www.tillster.com, closed as a census rather than assumed: the sitemap lists 92 URLs of which 91 return content, and an href fixpoint over every one of them surfaced 21 further internal links that all 301 into pages already listed (8 legacy product URLs into the current /solutions/ set, 11 legacy blog URLs into /blog), so the sitemap is the census here and not a floor. A fabricated sibling returns a hard 404 at 0 bytes, so absence on this host is distinguishable from a shell, `stock count`, `cycle count`, `par level` and `theoretical usage` occur zero times, tokenised and as bare substrings. The word inventory does read 43 times in 17 documents, which is why this needed measuring rather than asserting -- but the occurrences are blog-level discussion of integrating with inventory systems and of stock-driven menu availability, plus the kiosk page's promise that the kiosk is 'Directly connected to the store POS for real-time pricing, menu item, and stock updates'. That is Tillster CONSUMING stock state from the brand's POS in order to suppress sold-out items, which is the opposite of owning a count. https://www.tillster.com/platform · retrieved 2026-09-09

Provides a mobile/tablet counting app supporting barcode or QR scanning that continues to accept counts with no network connectivity and syncs on reconnect.

inventory-mobile-count-offline

Not scored by this record.

Ships pre-built electronic vendor catalog and order-transmission integrations with named broadline distributors (e.g. Sysco, US Foods, Performance Food Group) that send purchase orders and receive invoices electronically rather than by emailed PDF. differentiator

inventory-vendor-catalogs-edi

Not scored by this record.

Ingests supplier invoices from photo, PDF, or email and extracts line-item detail (item, quantity, unit, price) into the inventory ledger without manual line entry. differentiator

inventory-invoice-ocr

Not scored by this record.

Tracks per-item purchase price history across invoices and alerts when a received price exceeds the prior or contracted price by a configurable threshold. differentiator

inventory-price-change-alerts

Not scored by this record.

Maintains par levels per item per location and generates suggested purchase order quantities from on-hand versus par, with at least one mode driven by a sales forecast rather than a static par. differentiator

inventory-par-auto-suggest

Not scored by this record.

Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.

inventory-waste-logging

Not scored by this record.

Supports inter-location inventory transfers as a two-sided transaction crediting the sending location and debiting the receiving location, with an in-transit or approval state.

inventory-transfers

Not scored by this record.

Supports a commissary/central kitchen model where one location produces prep items and issues or sells them to other locations at a computed transfer cost.

inventory-commissary

Not scored by this record.

Captures lot/batch numbers at receiving and links them through production to sales or transfers, enabling a backward and forward recall trace.

inventory-lot-traceability

Not scored by this record.

Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.

inventory-shelf-life-expiry

Not scored by this record.

Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.

inventory-cogs-gl-export

Not scored by this record.

Inventory and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator

inventory-native-not-partner

Not scored by this record.

Joins recipe cost to actual item sales mix to report contribution margin per menu item, and flags items whose margin fell below a configured threshold after ingredient cost changes. differentiator

inventory-menu-margin-linkage

Not scored by this record.

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

Performance dashboards and customer insights are marketed for the digital channels; refresh latency and off-premise mobile access are not documented. https://www.tillster.com/solutions · retrieved 2026-08-01

Generates a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types, and expected cash deposit in one document.

reporting-eod-closeout

Upheld, and this is the cleanest absence on the vendor. The claim wants one nightly document reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types and expected cash deposit. Every term that document is made of reads ZERO across a 91-page corpus read 2026-09-09 -- the whole of www.tillster.com, closed as a census rather than assumed: the sitemap lists 92 URLs of which 91 return content, and an href fixpoint over every one of them surfaced 21 further internal links that all 301 into pages already listed (8 legacy product URLs into the current /solutions/ set, 11 legacy blog URLs into /blog), so the sitemap is the census here and not a floor. A fabricated sibling returns a hard 404 at 0 bytes, so absence on this host is distinguishable from a shell, tokenised and as bare substrings alike: `end of day`, `end-of-day`, `close out`, `closeout`, `cash drawer`, `tender reconciliation`, `z report`, `deposit` and `settlement`. Tillster does publish analytics -- the cited page is a channel, market and segment dashboard product -- but a digital-ordering dashboard is not a cash-reconciliation packet, and Tillster never holds the drawer: the kiosk page states that 'Cash orders seamlessly routed to POS for employee-assisted payment', so cash is tendered on the brand's POS and reconciled there. The old rationale said exactly this and it survives measurement. One term had to be dropped from that list rather than published: till is unusable on this vendor because it is a substring of Tillster, and reads 1,997 times when the word boundaries are stripped. https://www.tillster.com/solutions/restaurant-data-and-analytics · retrieved 2026-09-09

Provides a product mix (PMIX) report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center.

reporting-pmix-modifier-level

Checked 2026-08-04: solutions/restaurant-data-and-analytics is the only reporting page and it describes guest-and-campaign analytics - 'Visualize key metrics and trends', 'Filter insights by channel, market, or guest segment', 'Access dashboards for each location or brand region', customer lifetime value, redemption and visit patterns. It never mentions item-level or modifier-level product mix, daypart filtering, revenue centers or gross/net sales columns, and no sample report or report catalogue is published. Absence of the words is not proof the report is missing, so this stays unresolved rather than negative. || 318th: NEW BOUND (318th): across the full 92-URL www.tillster.com census, 'product mix' 0, 'PMIX' 0, 'sales report(s)' 0. Nearest report language is item-level only: analytics 'Identify emerging trends in menu item performance'; delivery page 'Centralized reporting' by marketplace, brand, or product. No modifier-level report named. Still unknown. Retrieved 2026-09-16. || 327th: 327th: recording a bound so this cell is not re-mined from the wrong corpus. The only Tillster application readable anonymously is the GUEST ordering client (5.32 M chars), which has no reporting surface of any kind; the operator-facing console that would carry a PMIX report is documented only behind client.help.tillster.com, a gated Jira Service Desk, and the Tillster Commerce Engine hosts (dev/stage.tce.tillster.com) return a real 403 to curl with a browser UA on every path including a nonsense control. No report catalogue is published. Retrieved 2026-09-18. || 328th: 328th: the marketing corpus was RE-DERIVED rather than inherited, because the 327th found a blog page the 318th census had missed. www.tillster.com/sitemap.xml still lists exactly 92 URLs (lastmod 2026-09-16), i.e. the census is unchanged and complete; the site is Webflow, not WordPress and not HubSpot (wp-json/wp/v2/types 404s with the site's 6,623-byte 404 body, and /_hcms/search?term= 404s likewise), so neither the WP-REST custom-type route nor the HubSpot unlinked-page search sweep applies to this vendor. No new reporting surface exists to mine. Retrieved 2026-09-18. || 330th: 330th, TWO NEW SURFACES, neither a reporting catalogue. (1) APP-STORE PUBLISHER CENSUS: iTunes lookup by developer id 999763888 returns Tillster's COMPLETE published iOS set - 5 apps: Burger King Kuwait, Burger King(R) CO, Subway(R) Kuwait, Porto's Bakery & Cafe (all white-label guest ordering, bundle ids com.tillster.<brand>) and ONE operator app, `Tillster Beacon` (com.tillster.beacon.prd, v1.0.2, 2026-07-17). Beacon's vendor-authored listing (grade C) defines the operator-facing analytics Tillster ships to a mobile device, and it is KIOSK FLEET telemetry, not sales: 'real-time visibility into the performance of every kiosk', 'Real-Time Alerts: Get notified the moment a kiosk goes down', 'Remediation Steps', 'Actionable Insights: Access store and device level data'. No item, modifier, daypart or revenue-centre reporting is named in any Tillster app listing. (2) The new production operator console admin-txp.prod.tce.tillster.com (117-chunk fixpoint census) has no reporting module in its anonymous slice: `Reports` 0, `Analytics` 0, `Catalog` 0, `Publish` 0 as word-boundary tokens; its labels are all Experience-Designer component properties ('Card Grid', 'Box Price', 'Show Expiration Date'). Also dead: the 30 `*-clientportal.tillster.com` Zendesk help centres in the Wayback index are all NXDOMAIN with 0 archived article URLs. Retrieved 2026-09-18. 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.

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

CLAIM: a named organisational hierarchy of >=3 levels (enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to. VERDICT: unknown -> partial/C. EVIDENCE: (www.tillster.com/blog/restaurant-menu-management, first-party Menu Manager write-up) 'Pricing can be managed at the brand, region, franchise, store group, or individual store level, allowing global consistency with local control.' - five named levels; same page: 'Permissions are role-based, allowing organizations to define who can edit pricing, modify items, launch promotions, or manage regional configurations.'; (www.tillster.com/solutions/restaurant-data-and-analytics) 'Access dashboards for each location or brand region' and 'Filter insights by channel, market, or guest segment'; (www.tillster.com/solutions/restaurant-delivery-and-marketplaces) 'Enterprise dashboard visibility for all brands, stores, and marketplace channels.' MET: >=3 named levels (brand > region > franchise > store group > store); reporting scoped to brand region and location. SHORT: the levels are evidenced as PRICING scopes, not described as a first-class org object; permissions are shown as the right to manage regional configuration, not as a grant scoped TO a region/group; marketing grade C; the 2 'hierarchy' hits are menu hierarchy and UI hierarchy (poison). CORPUS: www.tillster.com sitemap.xml = 92 URLs, all fetched 200 (robots.txt has no Disallow; a nonsense path 404s, so no catch-all); the href fixpoint over the 92 bodies found 20 extra first-party paths and all 20 301 into sitemap URLs (e.g. /self-service-kiosk -> /solutions/restaurant-kiosks), so the sitemap is the census of the marketing host. pages.tillster.com is a separate event/webinar landing SPA (3 linked event pages; sitemap.xml 404) and is outside this bound. Retrieved 2026-09-16. https://www.tillster.com/blog/restaurant-menu-management · retrieved 2026-09-16 adversarially verified

A corporate-level menu can be authored once and published to a chosen set of locations in a single action, with a publish/version history showing what was pushed, when, and by whom.

multi-location-central-menu-publish

Central menu management across a brand's estate is a named capability; publish/version history with who-pushed-what-when is not documented. https://www.tillster.com/solutions · retrieved 2026-08-01

Corporate menu items expose per-field override rules so a location can change some attributes (e.g. price, availability) while corporate locks others (e.g. name, image, recipe), and locked fields are not editable at store level. differentiator

multi-location-local-override-policy

Not scored by this record.

Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.

multi-location-price-zones

CLAIM: one item carries different prices per location group, per order channel, and per daypart without duplicating the item record. VERDICT: partial (two of three price dimensions + no-duplication established; per-daypart price not evidenced). EVIDENCE (tillster.com/blog/restaurant-menu-management, a first-party Menu Manager feature write-up): 'Pricing can be managed at the brand, region, franchise, store group, or individual store level, allowing global consistency with local control' (location-group tiers), 'Tillster supports: Order-type based pricing (e.g., $8.00 pickup / $8.50 delivery) ... Marketplace-specific markups ... Brand-level, region-level, franchise-level, and store-level pricing ... Scheduled price updates for future deployments ... Real-time POS synchronization' (per-channel/order-type pricing), and 'When menu content, pricing, and availability are updated once, those changes can be set to flow everywhere. This approach eliminates duplication' (single item record, not duplicated). SHORTFALL: the daypart dimension is documented only for menu AVAILABILITY ('Dayparting by hour and day', 'Scheduled future deployments') and one-off 'Scheduled price updates for future deployments' - no recurring time-of-day/daypart PRICE tier is described; grade C (vendor feature page, written to sell). The data model that would confirm a matrix vs duplicated records sits behind the Cognito-gated api-docs.dev.tillster.com portal. Retrieved 2026-09-16. https://www.tillster.com/blog/restaurant-menu-management · retrieved 2026-09-16 adversarially verified

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.

The POS software runs on commodity off-the-shelf hardware (standard iPads, Android tablets, or PCs) that the operator can buy from a third party, rather than only on vendor-supplied proprietary terminals. differentiator

hardware-commodity-devices

Not scored by this record.

Vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs.

hardware-os-platforms

CLAIM: vendor documentation names the specific client operating systems supported AND states minimum OS versions and device specs. VERDICT: unknown -> partial/C. EVIDENCE: kiosk OS named - (www.tillster.com/solutions/restaurant-kiosks) 'Secure chassis and hardened Windows environment with MFA-based access, endpoint protection, and vulnerability scanning.'; consumer clients named - (www.tillster.com/blog/restaurant-menu-management) menus syndicate to 'Responsive web ordering' and 'iOS and Android mobile apps'; hardware stance - (www.tillster.com/platform/restaurant-technology) 'Deploy on any device' 'with flexible, hardware-agnostic software that runs smoothly on both new and existing kiosks.' and (restaurant-kiosks) 'Our kiosk software can even run on your existing hardware.' SHORTFALL: no minimum Windows/iOS/Android version and no device spec anywhere - 'specs' 0, 'specifications' 0 across the census; the 10 'minimum' hits are not device minimums (poison). The old rationale 'without naming client OS' was false: Windows is named for the kiosk. CORPUS: www.tillster.com sitemap.xml = 92 URLs, all fetched 200 (robots.txt has no Disallow; a nonsense path 404s, so no catch-all); the href fixpoint over the 92 bodies found 20 extra first-party paths and all 20 301 into sitemap URLs (e.g. /self-service-kiosk -> /solutions/restaurant-kiosks), so the sitemap is the census of the marketing host. pages.tillster.com is a separate event/webinar landing SPA (3 linked event pages; sitemap.xml 404) and is outside this bound. Retrieved 2026-09-16. https://www.tillster.com/solutions/restaurant-kiosks · retrieved 2026-09-16 adversarially verified

Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.

hardware-handheld-purpose-built

Not scored by this record.

The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator

hardware-handheld-battery-swap

Not scored by this record.

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

Tillster's only customer-facing terminal is the kiosk, and offline continuity is a stated design point: 'Operates on the local network to eliminate cloud latency and downtime', 'Continues functioning even during internet outages, ensuring uninterrupted service', 'Keep operations running smoothly - even during cloud outages - with local POS integration'. Named shortfall: the claim's second half is unmet - Tillster documents nowhere which functions degrade offline (card authorization, loyalty accrual, stored-card lookup), and kitchen printing and cash recording are explicitly the brand POS's job ('Cash orders seamlessly routed to POS for employee-assisted payment'), so offline survival of those paths depends on the third-party POS, not Tillster. https://www.tillster.com/solutions/restaurant-kiosks · 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

CLAIM: sells or supports a dedicated KDS with bump-bar or touch input, station routing and course/fire timing, as a FIRST-PARTY product rather than an integration-only dependency. VERDICT: unknown -> no/C. BOUND: CORPUS: www.tillster.com sitemap.xml = 92 URLs, all fetched 200 (robots.txt has no Disallow; a nonsense path 404s, so no catch-all); the href fixpoint over the 92 bodies found 20 extra first-party paths and all 20 301 into sitemap URLs (e.g. /self-service-kiosk -> /solutions/restaurant-kiosks), so the sitemap is the census of the marketing host. pages.tillster.com is a separate event/webinar landing SPA (3 linked event pages; sitemap.xml 404) and is outside this bound. The product enumeration in every page's nav ('Customer Data Platform | Order Manager | Menu Manager | Recommeder ai | Kiosk Software | Offers & Loyalty Engine') has no kitchen display. CONTROLS (tokenised, case-insensitive, all 92 bodies): 'KDS' 5 hits/4 pages and 'kitchen display' 4/4 - every one is an INTEGRATION or buyer advice, e.g. (www.tillster.com/blog/kiosks-for-restaurants) 'Tillster’s kiosk software connects directly to a restaurant’s POS and kitchen display system (KDS)' and (solutions/restaurant-ordering) 'Route orders directly to POS and kitchen systems for faster throughput and fewer errors.'; 'bump' 0; 'expo' 0; 'kitchen screen' 0; 'prep station' 0; 'course' hits are 'of course'/'correct course' (poison); 'stations' 1 = gas stations (poison). NEAR-MISS NAMED: Order Manager is a staff fulfilment tool ('Tillster’s Order Manager tool enables staff to easily fulfill kiosk and mobile orders', solutions/in-store-ordering) with order/delivery status visibility - no bump input, station routing or fire timing is attributed to it. Also: the Tillster Ordering WS spec (api.swaggerhub.com Nagarro89/ordering-web_api 5.0.141-master, 211 ops) has 0 kitchen/station/KDS operations; its only kitchen token is the field kitchenReceiptDescription. Consistent with kitchen-bump-bar-hardware no/C and kitchen-expo-consolidation no/C. Retrieved 2026-09-16. https://www.tillster.com/platform · retrieved 2026-09-16 adversarially verified

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.

Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.

extensibility-public-api-docs

Upheld, but the old rationale's premise was false and is withdrawn: it said no public developer portal or self-serve API reference exists on tillster.com, and that the only route is a demo request. A developer portal DOES exist -- this record's own sources file has cited api-docs.dev.tillster.com since an earlier pass -- and Tillster asserts the APIs on its marketing pages, the cited page promising 'Secure APIs' that 'Enforce authentication, access control, and encrypted communication between Tillster and partner systems', with the integrations page adding 'open APIs'. What is true is the thing the claim actually asks: none of it is readable without a signed relationship. Tillster's two real documentation surfaces are both closed and were re-probed today: api-docs.dev.tillster.com serves a 464-byte Vite shell for every path, including /robots.txt, rendering a Redocly client whose spec index it fetches from the S3 bucket api-docs-infra, and client.help.tillster.com is an Atlassian Confluence Cloud wiki behind authentication. Neither has ever been captured by the Wayback Machine -- the CDX index holds exactly two rows for the whole help hostname, both 301s from January 2025, and none at all for api-docs -- so this is not a wall that used to be a window. And on the marketing host itself, `developer portal`, `api reference`, `api documentation`, `swagger`, `openapi`, `sandbox`, `api key`, `oauth` and `webhook` occur zero times across a 91-page corpus read 2026-09-09 -- the whole of www.tillster.com, closed as a census rather than assumed: the sitemap lists 92 URLs of which 91 return content, and an href fixpoint over every one of them surfaced 21 further internal links that all 301 into pages already listed (8 legacy product URLs into the current /solutions/ set, 11 legacy blog URLs into /blog), so the sitemap is the census here and not a floor. A fabricated sibling returns a hard 404 at 0 bytes, so absence on this host is distinguishable from a shell, tokenised and as bare substrings. So Tillster is partner-gated, not API-less -- and the cell stays `no` because the claim is about public readability. https://www.tillster.com/platform/restaurant-technology · retrieved 2026-09-09

API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator

extensibility-api-access-cost

Not scored by this record.

The vendor publishes its partner/marketplace commercial terms (referral fee, revenue share percentage, or per-location partner fee) in public documentation.

extensibility-partner-revshare

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

Checked 2026-08-04: a developer portal does exist at api-docs.dev.tillster.com, but it is a client-rendered SPA whose spec list is loaded from AWS S3 bucket 'api-docs-infra' (us-east-1) behind an Amazon Cognito user pool - unauthenticated requests to the bucket return HTTP 403 AccessDenied, so no endpoint or auth documentation is readable. (The OAuth strings in the portal's own JS bundle are its Cognito sign-in flow, not evidence of a partner-facing OAuth API.) Public copy goes no further than 'Secure APIs - enforce authentication, access control, and encrypted communication between Tillster and partner systems' (platform/restaurant-technology) and 'open APIs' (platform/integrations); contact/partners has no developer program or certification detail. Whether partner apps get scoped, operator-granted, revocable OAuth grants or static keys cannot be determined. Unresolved. || 318th: NEW BOUND (318th): 'OAuth' 0, 'API key(s)' 0, 'developer portal' 0 across the full 92-URL www.tillster.com census (href fixpoint closed); the single 'developers' hit is UX prose. crt.sh subdomain listing shows no public developer host beyond the gated api-docs.dev.tillster.com. Still unknown. Retrieved 2026-09-16. || 327th: 327th, NEW SURFACE, negative: `oauth` 0 tokens across the 5.32 M-char Tillster ordering app; the app's own authentication is a tenant user-aggregation service (`userAggregationService: https://api.baskinrobbins.com/user-aggregation-service/tenants/br-us`) and a First Data ucom SDK, i.e. consumer sign-in, not a partner authorisation grant. The tce.tillster.com dev/stage hosts remain a real 403 (see the webhooks cell). Tillster publishes no developer portal, so a third-party app authorisation model - if one exists - is unpublished rather than absent. Retrieved 2026-09-18. || 328th: 328th: two routes ruled out for this vendor so later passes do not retry them. (a) tillster.com is a Webflow site: /wp-json/wp/v2/types and /_hcms/search?term=<word>&limit=100 both return the standard 6,6xx-byte 404 body, so there is no WordPress custom post type and no HubSpot unlinked-page index behind it; its sitemap is still exactly 92 URLs. (b) The one anonymously-reachable Tillster backend, the mobilem8 menu/web service on the client brand's api host, was probed GET-only and returns empty envelopes without a session (see the modifier-pricing row), so it publishes no authorisation model either. The partner authorisation scheme remains unpublished rather than absent. Retrieved 2026-09-18. || 330th: 330th, NEW SURFACE, first direct sight of Tillster's machine-credential model. In the production TXP operator console (admin-txp.prod.tce.tillster.com; 117-chunk fixpoint census, see the modifier-pricing row) the shipped code reads a tenant's platform credential from an ADMIN API-KEY registry: `fetch("https://api-us-east-1.tce.tillster.com/tce-experience-admin/api-keys",{method:"GET",headers:{...,"active-tenant-identifier":u}})` then `i?._embedded?.apiKeys?.find(e=>e.tenantId===u&&"CONSUMER-EXPERIENCE-API"===e.serviceName)?.id`, fetches `/tce-experience-admin/api-keys/${o}` and installs the result as `tokens:{"x-api-key":c.value,"active-brand-identifier":u}`. So API access to the Tillster Commerce Engine is a per-tenant, per-SERVICE STATIC KEY presented in an `x-api-key` header, administered inside the operator console - the shape the claim calls out as the negative case. This is NOT published as a `no` because (a) the registry itself is only reachable with an operator bearer token, so the enumeration of `serviceName` values is unseen, and (b) Tillster's partner APIs (the Delivery API, the legacy mobilem8 services) remain unpublished. POISON NAMED: `oauth` is 51 hits in this corpus and every one is a human-login SDK - Okta/Auth0 (`urn:okta:params:oauth:grant-type:webauthn`, `http://auth0.com/oauth/grant-type/mfa-otp`, `.well-known/openid-configuration`) used for the console's own staff/operator sign-in, which per merge policy is not a partner authorisation grant. DEAD ROUTES recorded so nobody re-runs them: the 30 `*-clientportal.tillster.com` help centres found in the Wayback CDX index are Zendesk (`/hc/en-us`, `/hc/signin`) but ALL 30 are NXDOMAIN today and the archive holds only landing pages and theming assets - 0 archived `/hc/*/articles/*`; the official developer signpost archived at developers.tillster.com (2019-04-23) links its Delivery API spec to https://app.swaggerhub.com/apis/JonAtkins57/DeliveryHubApi/1, which is DELETED (api.swaggerhub.com: `{"code":404,"message":"Unknown API JonAtkins57/DeliveryHubApi:1"}`, owner listing `totalCount:0`) and was never archived. Retrieved 2026-09-18. adversarially verified

The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.

extensibility-webhooks-push

Checked 2026-08-04: platform/integrations says 'Connect systems in real time through open APIs that enable fast, secure data sharing and order synchronization across channels' and 'Sync data bi-directionally between Tillster and third-party tools' - real-time bidirectional sync, but it never says whether order lifecycle events are pushed as webhooks or pulled by polling, and no event catalogue is published. The API reference at api-docs.dev.tillster.com that would settle it is Cognito-gated with its S3 spec bucket returning HTTP 403. Unresolved. || 318th: NEW BOUND (318th): the full www.tillster.com census (92 sitemap URLs; href fixpoint closed - all 20 extra paths 301 into the sitemap) has 'webhook'/'webhooks' 0 and 'event-driven' 0; the 8 'events' hits are trade shows/birthdays (poison). crt.sh for %.tillster.com lists internal api.*/cmt.*/iss.*/k8s hosts and brand clientportal hosts - no public developer-docs host besides the Cognito-gated api-docs.dev.tillster.com. Still unknown: marketing absence cannot carry a no for an API feature. Retrieved 2026-09-16. || 327th: 327th, NEW SURFACES, both negative. (1) Tillster's shipped ordering app (5.32 M chars): `webhook` 0, `oauth` 0. Its only push mechanism is a proprietary consumer pub/sub - `loyaltyPubSub: https://api.baskinrobbins.com/mobilem8-push-service/pubsub/` - which delivers loyalty messages to the guest's own app session, not order-lifecycle callbacks to a partner endpoint. (2) The two Tillster Commerce Engine hosts that the 322nd recorded as refused were RE-PROBED today with curl and a browser UA per the curl rule, and they are NOT node-fetch artefacts: https://dev.tce.tillster.com/ and https://stage.tce.tillster.com/ return a genuine 23-byte 403 on the root, on /swagger/index.html AND on a nonsense path alike, so the refusal is real and uniform. They are dev/stage in any case and could not carry a verdict. Retrieved 2026-09-18. || 330th: 330th, NEW SURFACE: the Tillster Commerce Engine does run a real-time notification bus, but the only observable subscriber is the GUEST client, and the client itself falls back to polling. From the production console's shipped code (117-chunk fixpoint census of admin-txp.prod.tce.tillster.com): `wss://ws-us-east-1.tce.tillster.com/tce-realtime-notifications?topic=${e}&filters=${t}` is opened with `topic = BRAND#<brandId>#CUSTOMER#<customerId>` and `filters = {subdomain:"ORDERS",storeId,orderId,eventType:"OrderUpdated"}`, and if the socket fails the same code polls the order endpoint `maxAttempts:30, intervalMs:2000`. The lifecycle vocabulary is the ORDER_STATE_LABEL_KEYS enumeration {Order placed, Order sent to Kitchen, Order Ready, Order Completed, Order Canceled, Order Failed} - one `eventType` (OrderUpdated), no voided/refunded events. Tokenised over the 116 files: `webhook` 0, `callbackUrl` 0, `notificationUrl` 0, i.e. there is no endpoint-registration surface anywhere in the console's public slice. This stays unknown rather than `no`/partial: a customer-topic WebSocket is not a partner webhook (adjacent, not part of the claim), and Tillster's partner-facing API is unpublished, so no public census bounds it. Retrieved 2026-09-18. adversarially verified

Webhooks are cryptographically signed (e.g. HMAC) AND documented to retry with backoff, with a replayable event log for missed deliveries. differentiator

extensibility-webhook-reliability

Not scored by this record.

A public write API accepts externally originated orders into the POS as first-class tickets that fire to KDS/printers and land in reporting.

extensibility-order-injection-api

Not scored by this record.

Menu items, modifiers, and prices can be written and updated via API, not just read. differentiator

extensibility-menu-write-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.

Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.

reliability-offline-order-entry

OVERTURNED from `no` to partial, and the old rationale was false in both halves: it said there is no on-terminal POS software and that order entry depends on the brand's POS and Tillster's cloud. Tillster's central architectural claim is the exact opposite. The cited kiosk page states that the kiosk 'Operates on the local network to eliminate cloud latency and downtime' and 'Continues functioning even during internet outages, ensuring uninterrupted service', and the platform page describes the mechanism as 'On-premise resilience' -- 'Tillster's mesh architecture keeps kiosks and core ordering systems running locally—even during major cloud outages—ensuring continuous transactions and zero disruption for guests and operators.' A reliability essay on the same host adds the cached-data detail and a dated instance: 'The most recent data is cached on each kiosk, so service continues even when cloud connectivity drops' and, of a global AWS outage the month before the essay, that 'while other systems went dark, Tillster kiosks kept running' -- the closing words sit inside an italic run, so the sentence is not quoted past it. Partial rather than yes for three reasons. The terminal in question is a guest-facing self-order kiosk, not a staff POS terminal, because Tillster sells none. Of the claim's three elements only order entry and ticket routing are covered -- kitchen routing is named among the functions that continue, but check printing is nowhere stated to survive an outage, and the kiosk page mentions printers only under health monitoring. And the evidence is vendor feature-page prose rather than documentation: `store and forward`, `offline mode` and `local mode` are each zero across the corpus, so there is no published failure envelope -- no queue depth, no expiry, no list of what degrades. Note also that the sentence 'Core functions like ordering, payment, and kitchen routing should work offline and sync automatically once the network is restored' is buyer's advice in Tillster's own essay, not a statement about Tillster, and must not be cited as one. https://www.tillster.com/solutions/restaurant-kiosks · retrieved 2026-09-09

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

Tillster's published product set - Customer Data Platform, Order Manager, Menu Manager, Recommender AI, Kiosk Software, Offers & Loyalty Engine - contains no kitchen display or kitchen printing product, so there is no Tillster-owned kitchen ticket path to keep running offline. What survives an outage is the kiosk ordering channel: 'Operates on the local network to eliminate cloud latency and downtime. Continues functioning even during internet outages' and 'Keep operations running smoothly - even during cloud outages - with local POS integration' (solutions/restaurant-kiosks). Kitchen routing and its offline behaviour belong to the brand's POS/KDS, not to Tillster. https://www.tillster.com/platform · 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

The only printer Tillster manages is the kiosk's own: 'Back-office visibility into every kiosk, including device, printer, and payment terminal health. Configurable alerts to flag issues before they impact service.' That is health monitoring and alerting on kiosk hardware - there is no configured kitchen printer in Tillster's product set (platform tools are CDP, Order Manager, Menu Manager, Recommender AI, Kiosk Software, Offers & Loyalty Engine) and therefore no automatic failover to a backup printer or KDS station. Kitchen printer redundancy sits with the brand's POS. https://www.tillster.com/solutions/restaurant-kiosks · 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.

The vendor performs the initial menu build as part of onboarding rather than leaving it entirely to the operator. differentiator

reliability-menu-build-service

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.

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

No contract terms of any kind are publicly accessible; the site's only commercial path is 'Request a Demo'. https://www.tillster.com/ · retrieved 2026-08-01

The POS software can be purchased and operated with a third-party payment processor of the operator's choice (no mandatory in-house processing lock). differentiator

commercial-processing-not-bundled

Not scored by this record.

Vendor publishes an interchange-plus (cost-plus) processing rate option with the markup stated as a specific bps + per-transaction figure, rather than only blended/flat card-present rates. differentiator

commercial-interchange-plus-published

Not scored by this record.

The processing agreement caps or prohibits unilateral vendor-initiated rate increases outside of pass-through interchange/network changes, or grants penalty-free exit on any increase. differentiator

commercial-rate-increase-clause

Not scored by this record.

Per-location and per-additional-terminal software pricing is published as specific dollar figures on the vendor's public site (not 'contact sales' only).

commercial-pricing-published

No pricing information anywhere on the site; demo request only. https://www.tillster.com/solutions · 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 lease/rental. VERDICT: unknown -> no/C, on the published-price conjunct. BOUND: CORPUS: www.tillster.com sitemap.xml = 92 URLs, all fetched 200 (robots.txt has no Disallow; a nonsense path 404s, so no catch-all); the href fixpoint over the 92 bodies found 20 extra first-party paths and all 20 301 into sitemap URLs (e.g. /self-service-kiosk -> /solutions/restaurant-kiosks), so the sitemap is the census of the marketing host. pages.tillster.com is a separate event/webinar landing SPA (3 linked event pages; sitemap.xml 404) and is outside this bound. No page carries a hardware (or any) price - consistent with commercial-pricing-published no/C; the CTA is 'Request a Demo'. CONTROLS: 'lease' 0, 'financing' 0, 'price list' 0; 'leasing' 1 and 'rental' 1, both buyer advice in blog/6-restaurant-kiosk-deployment-challenges-amp-how-to-overcome-them ('restaurant operators can consider leasing kiosks or using a kiosk program'), not a Tillster offer; 'purchase' 26 hits are guest purchases (poison). Context: Tillster is software-first ('Our kiosk software can even run on your existing hardware.', solutions/restaurant-kiosks), so kiosk hardware may be operator-sourced - but no Tillster hardware price is published anywhere, which fails the claim. Retrieved 2026-09-16. https://www.tillster.com/solutions/restaurant-kiosks · retrieved 2026-09-16 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.