Vendors / Mainstream commercial restaurant POS
talech
A bank-distributed SMB POS being folded into U.S. Bank Payment Solutions / Elavon, whose live help centre (help.talech.com, 269 published articles, several already rebranded 'Elavon Point of Sale') documents a competent single-site register - printer-based kitchen, per-action role permissions, first-party gift, own-domain online ordering - with no KDS, no delivery dispatch, one-level modifiers, flat multi-location structure and no reachable developer API.
scored live legacy rubric
- Claims in scope
- 278
- Scored
- 45
- Assessed
- 42
- Unknown
- 236
- Not applicable
- 36
- Values challenged
- 0
unknown, never as no.Identity
- Owner
- U.S. Bancorp / Elavon (talech was acquired by U.S. Bancorp's Elavon in 2019). Note: as of this check U.S. Bank's own POS page markets 'U.S. Bank Payment Solutions powered by Elavon' and does not mention the talech brand at all.
- Parent
- U.S. Bank / Elavon
- Who it is for
- Small restaurants and retailers acquired through bank merchant-services channels (U.S. Bank / Elavon branch and ISO distribution), single-location and light multi-location.
- Site
- https://www.talech.com/
Pricing
transparency: quote-only · unit: per location per month (software) + bundled per-transaction processing rate; setup fee per location · processor lock-in: yes
- Software
- Bank-channel published tiers (U.S. Bank Payment Solutions): Starter $29/mo (no setup fee), Standard $69/mo + $99 one-time setup, Premium $99/mo + $99 setup, unlimited users on all tiers. Bundled card rates 2.60% + 10c card-present, 3.50% + 15c keyed, 2.90% + 30c online. Hardware priced per device, rental or purchase, prices not published. Whether this price card is literally the talech-branded product or its successor SKU is not stated on the page.
Capabilities
Every claim is binary and checkable. Grades: A primary documentation · B product documentation · C pricing or feature page · D marketing claim · E third-party reporting · F inference with no source. A yes on a differentiator claim requires A or B.
Order capture & FOH workflow
Provides a graphical floor-plan editor where an operator can draw sections, place tables of varying shape/capacity, save multiple floor-plan layouts per location, and assign sections to servers.
order-capture-floor-plan-editor
Not scored by this record.
Order lines can be tagged to a seat number at entry, and the check can be split by seat afterward without re-keying items.
order-capture-seat-level
Not scored by this record.
Items can be assigned to courses and held, with a fire-next-course action available from a handheld or terminal that releases only that course to the kitchen.
order-capture-coursing-hold-fire
Not scored by this record.
Supports splitting a check by item, by seat, by even N-way, and by arbitrary dollar/percentage amount, and merging checks or tables back together, including after partial payment.
order-capture-split-merge
CLAIM: split by item, seat, even N-way, arbitrary $/% amount, and merge checks, incl. after partial payment. VERDICT: partial/B -- item, seat (position), even N-way and arbitrary-dollar splits and item-level merge into an existing open order are documented; percentage splits and merging after a partial payment are not stated. EVIDENCE: https://help.talech.com/s/article/Splitting-Payments (published 2025-12-08): "You can split a bill into halves, quarters, or any custom number up to 99 ways."; "Tap on the Tender Amount field. Enter the amount the customer wishes to pay towards the bill with the first payment type."; "Split by position on a ticket ... Available to restaurant merchants in the Premium tier."; "The order remains open until the bill is paid in full." https://help.talech.com/s/article/Split-Merge-a-Ticket (2025-11-19): "Select the item(s) to remove from the ticket ... An Existing Order (Move to an existing Open Order). New Order (Move items to a new order)."; "Note: Merge is a feature that is only available on talech Premium." SHORTFALL: tokenised controls over the 268-article census -- "percent" 3 hits/2 docs and "percentage" 58/30 docs, none about bill splitting; no statement that a partially paid order can be merged. Surface: live Aura census of help.talech.com (Knowledge__kav; body = Discussion__c + Steps__c + Summary__c concatenated, discovered via getObjectInfo): 268 sitemap articles all live, href fixpoint added 2 slugs that are dead (Printing-Barcode-Labels-from-talech-com, Appointment-Settings), so 268/270 held with bodies; LastPublishedDate range 2024-10-30..2026-09-11. Retrieved 2026-09-16. https://help.talech.com/s/article/Splitting-Payments · retrieved 2026-09-16 adversarially verified
Opens a bar tab against a card pre-authorization with a configurable auth amount, supports incremental re-auth as the tab grows, and auto-closes stale tabs at end of day. differentiator
order-capture-bar-tab-preauth
Not scored by this record.
An open check can be transferred between servers, tables, and devices, and the transfer is recorded in an audit log naming both employees.
order-capture-transfer-audit
Not scored by this record.
Ships a first-party handheld ordering app running natively on the handheld device (not a remote/mirrored desktop session) that can send to kitchen and take a card payment tableside.
order-capture-native-handheld
Not scored by this record.
With the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen, and tender cash, and the vendor publishes what does and does not work offline.
order-capture-offline-order-entry
The vendor publishes offline scope in three named buckets. Fully supported: 'Create/save open orders. These orders are only stored on the iPad that created the order', 'Process Cash, Check, and Other payment types', 'Local pre-authorization', PIN sign-in between employees. Limited: settings changes 'will sync when the connection is restored'; 'Open/Closed orders stored locally on iPad. The last iPad to modify an order will be able to view while offline only'; 'Table layout allows to create New Orders and view tables in use'. No access: 'Credit card transactions, tip adjust, and settlement', gift cards and store credit, refunds and exchanges, 'Reports and Customer list', 'Order syncing between different iPads', 'Editing Menu/Inventory'. Shortfalls: order state is confined to the originating iPad with no cross-device sync, so a multi-terminal floor fragments; and sending to the kitchen is named in none of the three buckets, so offline kitchen printing is not established by the vendor's own published scope. Recovery is manual on failure -- a red cloud means 'there was an error saving data' and the only remedy documented is 'Log and Clear Orders', which 'will erase the failed action(s)'. https://help.talech.com/s/article/Managing-Orders-in-Offline-Mode · retrieved 2026-08-04
Guest QR at-table ordering writes items onto the same open check as server-entered items, rather than creating a separate order ticket. differentiator
order-capture-qr-same-check
Not scored by this record.
Offers a first-party self-order kiosk that renders the same menu and modifier tree as the POS with no separate menu build, and the vendor documents ADA/accessibility conformance for it. differentiator
order-capture-kiosk-first-party
Not scored by this record.
Supports drive-thru-specific order flow: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment.
order-capture-drive-thru
Not scored by this record.
Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.
order-capture-drive-thru-timers
Not scored by this record.
Vendor ships a first-party AI voice ordering agent for phone and/or drive-thru that injects orders directly as POS orders, or publishes a documented API partner program for third-party voice AI. differentiator
order-capture-voice-ai
Not scored by this record.
Supports order throttling: per-channel capacity limits per time slot with automatic quote-time extension when kitchen load exceeds a configured threshold. differentiator
order-capture-throttling
Not scored by this record.
Accepts future-dated/scheduled orders with a per-channel lead time and automatically injects them into the make queue at a computed fire time rather than on receipt.
order-capture-scheduled-orders
Scheduled orders exist: 'Customers can easily schedule an order for pickup same-day or for a future date ... even if your business is currently closed', and the order lands on Register > Orders > Online with the chosen date/time. Release is governed by one store-level Prep Time Estimate ('This time determines when Elavon POS sends an order to the kitchen') and only in the 'Auto-send to kitchen' mode, which works on 2-minute intervals. Shortfall: no per-channel lead time -- the prep-time setting applies to website orders only and Deliverect orders 'Follow the settings from your account on Deliverect. It is not affected by your online ordering prep time estimate settings'; off-hours orders are 'placed in your queue at next opening' rather than at a computed fire time. https://help.talech.com/s/article/Online-Ordering-Features-and-Functionality · retrieved 2026-08-03
Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.
order-capture-catering
Not scored by this record.
Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator
order-capture-order-ready-signal
Not scored by this record.
Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.
order-capture-void-comp-controls
Not scored by this record.
Menu, modifiers & pricing engine
Payments & money movement
The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator
payments-processor-choice
Not scored by this record.
Vendor publishes card-processing pricing publicly (a specific flat rate or interchange-plus markup) rather than quote-only. differentiator
payments-published-rates
Not scored by this record.
Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator
payments-dual-pricing
Not scored by this record.
Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator
payments-surcharge-guardrails
Not scored by this record.
All first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay.
payments-emv-nfc
Rate card prices 'swipe/tap/insert', documenting chip and contactless acceptance; Apple Pay/Google Pay not named. https://www.usbank.com/business-banking/payment-solutions/in-person-payments/point-of-sale.html · retrieved 2026-08-01
Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. differentiator
payments-softpos-tap-to-pay
Not scored by this record.
Vendor ships a handheld that takes EMV/NFC payment at the table, including tip prompt and check splitting, without carrying the card away.
payments-pay-at-table
Not scored by this record.
Guest can scan a QR code on the printed check or table tent to view and pay the check from their own phone, with the payment closing the check in the POS automatically. differentiator
payments-qr-guest-pay
Not scored by this record.
Supports both pre-auth-then-tip-adjust and on-device tip prompt flows, with a documented batch/adjust window and a manager screen for unadjusted tips.
payments-tip-adjust
Not scored by this record.
Configurable tip pooling and distribution rules (by hours worked, sales, role percentage, or points) that produce a per-employee tip allocation exportable to payroll. differentiator
payments-tip-pooling
Not scored by this record.
Card payments can be captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. differentiator
payments-offline-store-and-forward
Not scored by this record.
Vendor publicly documents who bears the loss when a stored offline transaction declines on reconnect, and surfaces a post-reconnect report of failed offline payments. differentiator
payments-offline-decline-liability
Not scored by this record.
First-party gift cards with real-time balance tracking, redeemable across every location in the group and through the online-ordering channel.
payments-gift-cards
First-party programme: 'sell your own store issued gift cards from your talech point-of-sale (either digital/e-gift or physical), sell digital/e-gift gift cards from your online ordering site, and manage your gift cards from your point-of-sale or from talech.com'. Real-time balance handling is native -- 'Manage features directly on your point-of-sale for activation, adding balance, checking balance' plus an online balance checker. Card types are Fixed, Reloadable or Promotional. Group-wide redemption is documented by numbering ('Card numbers must be unique across all stores sharing the same master owner (single store or multi-store accounts)') and by the multi-location reference, which states gift cards are 'shared across locations' on a shared multi-store account (separated by location on a linked multi-store, which is the model for independently operated businesses). https://help.talech.com/s/article/talech-Gift-Cards · retrieved 2026-08-03
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
Authorisation is fully role-based and per-action: Register Permissions enumerate Discounts, Regular Discount, Custom Item Discount, Refund ('Issue refunds without admin approval'), Return Without Receipt, No Sale, and Voids ('Delete orders sent to the kitchen without admin approval'); where the permission is off, the action 'will require a manager or admin PIN or swipe card'. Shortfall on the audit half: only voids get an approver-attributed record -- 'Every void is recorded in talech. The voided items report will include ... the employee initiating the void, the manager approving the void, date/time, the item, the dollar amount, the reason'. The Discount Used report records only 'employees who issued the discounts', and no equivalent approver-attributed report is documented for refunds, returns or no-sales. https://help.talech.com/s/article/Employee-Permissions-Breakdown · retrieved 2026-08-03
In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator
payments-chargeback-tooling
Not scored by this record.
Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator
payments-card-on-file
Not scored by this record.
Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator
payments-payout-timing
Not scored by this record.
Vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance / P2PE listing available to merchants on request.
payments-p2pe-pci4
Not scored by this record.
Kitchen & production
Items route to specific KDS stations by item, category, order type, or revenue center, with routing rules configurable per location without vendor involvement.
kitchen-station-routing
Routing exists and is operator-configurable per location without vendor involvement: 'When orders are sent to the kitchen from the Register app, the items in that order will go to printers based on their Tag(s) or Category', set at Dashboard > Back Office > Settings > Printers > select the kitchen printer > select either Categories or Tags and tick each one 'that you would like this printer to print kitchen receipts for'. Shortfalls: the destination is a receipt printer, not a KDS station -- no kitchen display or expo screen exists anywhere in the 269-article help centre, whose sitemap contains no KDS article; and the only routing keys are product Tag and Category, so routing by order type or revenue centre is not available. Item-level routing is reachable only by giving an item its own tag. https://help.talech.com/s/article/Printers-Setup-Printers-to-Create-Kitchen-Receipts · retrieved 2026-08-04
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
talech's documented kitchen output is thermal ticket printing, not a display system: 'When orders are sent to the kitchen from the Register app, the items in that order will go to printers based on their Tag(s) or Category', configured under Back Office > Settings > Printers by selecting Categories and/or Tags per printer. There is no kitchen display, expo screen, or bump/complete state in the help centre -- the only displays documented are customer-facing displays -- so there is no screen on which multi-station items could be consolidated or an order marked complete once every station has bumped. https://help.talech.com/s/article/Printers-Setup-Printers-to-Create-Kitchen-Receipts · retrieved 2026-08-03
Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator
kitchen-course-firing
Not scored by this record.
Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator
kitchen-prep-time-pacing
Not scored by this record.
Kitchen load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator
kitchen-order-throttling
Not scored by this record.
Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator
kitchen-channel-pause-propagation
Not scored by this record.
Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator
kitchen-order-ready-callback
Not scored by this record.
KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.
kitchen-bump-bar-hardware
The claim presupposes a KDS, and talech documents none. The complete printer reference enumerates every global setting, per-printer setting (name, IP, model, font size, Categories, Tags), and both Order Ticket Printing and Receipt Printing advanced setting tables; kitchen output is a printed docket throughout. No kitchen display device, bump bar, or programmable keypad appears in this reference or in any of the peripheral setup articles (printers, scanners, card readers, customer-facing displays), so there are no supported bump-bar models to document. https://help.talech.com/s/article/Printers-General-Advanced-Settings · retrieved 2026-08-03
An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.
kitchen-all-day-counts
Not scored by this record.
Configurable target cook times per station or order type, with visual color escalation and/or audible alert when a ticket exceeds target.
kitchen-sla-alerts
Not scored by this record.
If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator
kitchen-printer-fallback
Not scored by this record.
KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator
kitchen-offline-operation
Not scored by this record.
Station screens can display item-level build/assembly detail (recipe steps, portioning, or full modifier breakout) rather than only the ticket line text. differentiator
kitchen-item-build-screens
Not scored by this record.
Sectioned/fractional topping placement (halves, quarters, specific sections) is rendered visually and unambiguously on the make-line screen or ticket. differentiator
kitchen-pizza-fractional-display
Not scored by this record.
A bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order.
kitchen-recall-refire
Not scored by this record.
Edits made in the POS to an order already displayed in the kitchen visually flag the added, changed, or removed items on the live ticket. differentiator
kitchen-order-modification-alerts
Not scored by this record.
Bumping an order ready triggers a guest-facing notification — SMS/text, app push, or an order-status display board — without a separate product purchase. differentiator
kitchen-guest-ready-notification
Not scored by this record.
Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.
kitchen-waste-logging
Not scored by this record.
Reports actual ticket and per-station times (average and percentile) sliced by daypart, station, and order channel, exportable to CSV or an API.
kitchen-speed-of-service-reporting
Not scored by this record.
Generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list.
kitchen-prep-forecasting
Not scored by this record.
Delivery, dispatch & third-party channels
Product includes a native in-house driver module: drivers are first-class entities with clock-in/out, assignment state (in-store / on-run / returning), and per-driver run history reportable from the POS itself (not via a third-party add-on).
delivery-driver-roster
Delivery in talech is an online-ordering order type with no driver concept anywhere in the product. The online-ordering settings reference enumerates the entire delivery configuration -- toggle the order type on, Payment Options, Order Amount Limits, and 'Delivery Area (Delivery order type only): Set a delivery radius for your customers who want to place an order for delivery' -- and contains no driver entity, assignment state, or run tracking; the same page notes that orders from DoorDash, Uber Eats or Grubhub 'do not automatically connect to talech ... you'll need to manually enter those orders into the talech Register'. The surrounding enumerations are equally driver-free: the Employee Permissions Breakdown lists ~25 per-action permissions with none for drivers or dispatch, the Employee Timeclock flow is a generic PIN clock-in with no assignment state (in-store / on-run) attached, the report catalogues (operations/finance, products/services, sales trends) contain no per-driver report, and the live help-centre sitemap (269 articles) has no driver or dispatch article. https://help.talech.com/s/article/Online-Ordering-Settings · retrieved 2026-08-04
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
Delivery in talech is an online-ordering order type, not a dispatch module. The Online Order Types section enumerates the entire delivery configuration -- toggle the order type on, set Payment Options, Order Amount Limits, and a Delivery Area radius -- and nothing else. There is no driver entity, assignment state, dispatch screen, elapsed-time view, or multi-order run batching anywhere in the documentation; the settings page also notes that third-party delivery orders 'do not automatically connect to talech' without the Deliverect integration. https://help.talech.com/s/article/Online-Ordering-Settings · retrieved 2026-08-03
Dispatch includes a live map view with geocoded stops and system-generated route sequencing (turn order optimization) for a multi-stop run, not just a static address list. differentiator
delivery-route-map
Not scored by this record.
Captures live driver GPS position from a driver-facing mobile app and surfaces it back to the dispatch screen. differentiator
delivery-driver-tracking
Not scored by this record.
Delivery areas can be defined as arbitrary map polygons or by drive-time isochrones, not solely as a radius or a ZIP/postcode list. differentiator
delivery-zones-polygon
Not scored by this record.
Each delivery zone carries its own independently configurable delivery fee, order minimum, and quoted promise time, applied automatically from the validated customer address.
delivery-zone-pricing
talech has one delivery area, not zones: 'Delivery Area (Delivery order type only): Set a delivery radius for your customers who want to place an order for delivery. Customers located outside this distance won't be able to place a delivery order.' Order Minimum and Order Maximum are set once per order type, and the promise time comes from a single store-wide Prep Time Range. With exactly one radius carrying one minimum and one quoted time, there is no per-zone fee, minimum, or promise time to configure. https://help.talech.com/s/article/Online-Ordering-Settings · retrieved 2026-08-03
Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.
delivery-address-validation
Not scored by this record.
Tracks per-delivery driver compensation inputs — mileage or distance driven per run, per-delivery flat reimbursement, and driver-retained tips — and exports them to payroll as separate reimbursement vs. wage lines. differentiator
delivery-driver-comp
Not scored by this record.
Provides a driver cash bank / settle-up flow that reconciles cash collected, orders assigned, and tips owed at end of shift, producing a per-driver over/short figure.
delivery-cash-reconcile
Not scored by this record.
Can hand a first-party order to an on-demand courier marketplace (DoorDash Drive, Uber Direct, Nash, Relay or equivalent) natively from the POS, with the courier quote and status returning into the order record.
delivery-daas-dispatch
Not scored by this record.
Supports hybrid dispatch: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. differentiator
delivery-daas-fallback
Not scored by this record.
Offers direct, first-party certified API integrations with DoorDash, Uber Eats, and Grubhub marketplaces (vendor-owned, not solely resold through Otter/Deliverect/Chowly/ItsaCheckmate middleware). differentiator
delivery-3p-direct-integration
Not scored by this record.
Third-party marketplace orders inject automatically into the POS as normal tickets that fire to KDS/printers without tablet re-keying or manual accept.
delivery-3p-injection
Not scored by this record.
Marking an item or modifier 86'd in the POS pushes item-level out-of-stock status to connected third-party channels in near real time, and restores it on availability (DoorDash requires item and item-option 86ing of new POS partners).
delivery-86-sync
Not scored by this record.
Store can be paused/deactivated on each connected third-party marketplace from inside the POS with a timed auto-reactivation, rather than only from each marketplace's own tablet or portal.
delivery-store-pause
Not scored by this record.
Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. differentiator
delivery-3p-reconciliation
Not scored by this record.
Vendor exposes integration health to the operator — failed/rejected order injections, connection status per channel, and alerts on failure — rather than failing silently. differentiator
delivery-injection-error-visibility
Not scored by this record.
Guests receive a branded order status / driver tracking page or SMS link on the restaurant's own domain for first-party delivery orders, driven by real order and driver state.
delivery-tracking-page
Not scored by this record.
Quoted delivery promise times adjust dynamically from current kitchen load, driver availability, and zone drive time, rather than a fixed per-store constant. differentiator
delivery-promise-time
Not scored by this record.
Vendor documents explicit offline behavior for delivery: whether cash delivery orders, driver assignment, and driver settlement continue during an internet outage.
delivery-offline-behavior
Not scored by this record.
Digital ordering & guest-facing channels
Vendor ships a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission.
digital-first-party-web
Premium tier lists 'online ordering'; commission model and POS write-back not documented. https://www.usbank.com/business-banking/payment-solutions/in-person-payments/point-of-sale.html · 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
The checkout is enumerated in full twice and contains no guest account. End-to-end: order type, table number, ready/pick-up time, contact info ('The customer can add or edit their contact information'), add tip, apply a gift card, payment, items, promo code. The features article gives the same list and states payment options are 'Credit or Debit Card, Apply Pay, Pay in Store, or Apply Gift Card'. There is no sign-in, no saved address, no stored card, and no reorder of a previous order; card details are entered on a pop-up at each order. https://help.talech.com/s/article/Online-Ordering-End-to-End-Experience · retrieved 2026-08-03
Digital checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator
digital-upsell-engine
Not scored by this record.
Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.
digital-scheduled-pacing
Not scored by this record.
Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.
digital-fulfillment-modes
Not scored by this record.
Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.
digital-qr-table
Not scored by this record.
Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator
digital-kiosk
Not scored by this record.
Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.
digital-group-ordering
Not scored by this record.
Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator
digital-catering-portal
Not scored by this record.
Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator
digital-voice-ai-phone
Not scored by this record.
Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.
digital-drivethru-ai
Not scored by this record.
Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.
digital-sms-ordering
Not scored by this record.
Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator
digital-google-order
Not scored by this record.
Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.
digital-apple-business-connect
Not scored by this record.
Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.
digital-loyalty-attach
Not scored by this record.
Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.
digital-subscriptions
Not scored by this record.
Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.
digital-promo-parity
Not scored by this record.
Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator
digital-guest-data-ownership
Not scored by this record.
Digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.
digital-checkout-pci-sca
Not scored by this record.
Digital channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator
digital-surcharge-transparency
Not scored by this record.
Guest data, loyalty & marketing
Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.
guest-loyalty-unified-profile
A single customer record does exist and accumulates transactions: the profile shows Loyalty points, Key Metrics ('days since the last visit, the average spent, and total spent') and an Activity section with Orders, Invoices, House Account and Store Credit tabs, and customers can be attached to an open or a closed order. Shortfall: no documented cross-channel identity resolution. The online-ordering checkout collects contact information without creating a guest account, and no article states that website orders match or merge into the POS customer record; no dedup/merge rule (phone or email match) is published anywhere. Group-wide identity is also conditional -- on a linked multi-store account 'the customers and house accounts will remain separated by location'. https://help.talech.com/s/article/talech-Customers-feature-new · retrieved 2026-08-03
Orders arriving from third-party marketplaces (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. differentiator
guest-loyalty-thirdparty-identity-attach
Not scored by this record.
Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.
guest-loyalty-accrual-models
CLAIM: at least two of points-per-dollar, visit/punch-count, spend-tier accrual as configuration. VERDICT: yes/B -- native loyalty offers a per-dollar and a per-visit campaign type as a setting. EVIDENCE: https://help.talech.com/s/article/customer-loyalty-program (published 2026-04-20): "Select Campaign Type to choose what type of discount campaign to create." -- "Number of Visits 1 Visit = 1 Point"; "*Amount Spent (only available in North America – not available to EU) $1.00 = 1 Point"; "Reward Pool (only available on iOS) ... 1 Point is earned for every $1 spent but you set the value of each point". Caveats: one campaign type at a time ("If you switch your campaign type ... all loyalty point balances reset to zero"); Amount Spent is not offered to EU merchants. Surface: live Aura census of help.talech.com (Knowledge__kav; body = Discussion__c + Steps__c + Summary__c concatenated, discovered via getObjectInfo): 268 sitemap articles all live, href fixpoint added 2 slugs that are dead (Printing-Barcode-Labels-from-talech-com, Appointment-Settings), so 268/270 held with bodies; LastPublishedDate range 2024-10-30..2026-09-11. Retrieved 2026-09-16. https://help.talech.com/s/article/customer-loyalty-program · retrieved 2026-09-16 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
Checked the live loyalty reference (help.talech.com/s/article/customer-loyalty-program), which enumerates every campaign setting -- campaign type (Number of Visits, Amount Spent, Reward Pool), Campaign Name, Minimum Purchase Amount, Maximum Point Balance, and Bonus Points for New Members with a Time of Award of 'After first purchase' or 'After enrollment' -- plus the rewards configuration. The only automatic trigger there is a one-off enrolment bonus-point award, not a triggered message. However, the live Download Customer List article references a separate product ('selecting Yes means the customer will receive marketing emails from talech's campaign feature'), and talech Campaigns is documented only on the decommissioned Zendesk help centre: help.talech.com/hc/en-us/articles/205011699 returns HTTP 401 to unauthenticated requests, as does the whole /hc/en-us tree. No campaign article appears in the live Salesforce sitemap (269 articles). Cannot determine whether Campaigns ships birthday, first-visit or lapsed win-back automations without reading a page that is gated. || 318th: NEW (318th): CA (362) and EU (226) help centres: "campaign(s)" only in customer-loyalty-program and Download-Customer-List-new (same as US); "birthday" 0 in each. The Elavon Operating Guide OG2026/04 ch.29 (Elavon Point of Sale) has no marketing-automation terms; "birthday" 0 in its 9,645 lines. Retrieved 2026-09-16. || 322nd: NEW (322nd): NEW SURFACE (322nd): app.talech.com, talech's current merchant back office (production; named as the US login URL in www.talech.com/config.js, "talech admin" in its analytics tags). Its HTML sits behind an AWS WAF JavaScript challenge (curl gets HTTP 202 x-amzn-waf-action: challenge), so the login page was loaded in headless Chromium with no login, and the Vite chunks it references were fetched to a fixpoint: 641 files, 12 MB, every relative ./ or assets/ reference held at 200 except remoteEntry.js (a module-federation remote on onlinebanking.usbank.com, the U.S. Bank login widget); 3 non-literal import() calls, all in the federation runtime. Source maps are NOT public: every <chunk>.js.map and /.vite/manifest.json returns the same 26,040-byte SPA HTML shell (soft 200). The bundle carries the full en_US/fr_CA i18n dictionary (index-DSJmYvf8.js, 1.37 MB) and the route table (routes.config: 42 routes). Caveat: this is the NEW admin; user.service has "redirectToClassic: /api/v1/backoffice/auth/redirect/classic" and reports offer "downloadClassicReport", so a Classic back office still exists and is not covered by this corpus. The new admin's 42-route table has no marketing or campaign route (loyalty is a settings sub-route); the loyalty dictionary is the same settings list as the help article (Campaign Type Amount Spent / Number of Visits / Reward Pool, Minimum Purchase Amount, Maximum Point Balance, Bonus Points with "afterFirstPurchase: \"After first purchase\", afterEnrollment: \"After enrollment\""). Controls over all 641 files, tokenised case-insensitive: birthday 0 ("dateOfBirth: \"Date of birth\"" is a customer field only); win-back 0; lapsed 0; "first visit" 0; "thank you" 0; newsletter 0; "email campaign" 0; "automated email/message/campaign" 0; campaign(s) 37, all the loyalty campaign plus the discount types CAMPAIGN_DISCOUNT and E_GIFT_CAMPAIGN. Poison: "customerEmails" is a transactional online-order email page (orderApproved / orderDeclined / orderDelayed); marketing 21 hits are the cookie policy (12), test ids (accounting-marketing-button, receipt-preview-marketing-message: a receipt footer message) plus a customer flag "This customer agrees to receiving marketing emails" (a consent flag, not a sending feature); unsubscribe is for daily/weekly/monthly REPORT emails. Not published as 'no': the bundle points to a Classic back office ("redirectToClassic") that this corpus does not cover, and the live help centre still mentions "talech's campaign feature". Retrieved 2026-09-17. || 329th: MERGE HOLD (proposed no/B, held unknown): The `no` is carried by a RETIRED Zendesk generation recovered from Wayback (a floor of 453 docs, not a publisher manifest). The live Salesforce help centre has no Campaigns article at all, so it does not bound the feature, and the 641-file app bundle was collected by a headless browser, not a loader fixpoint. Whether a retired-generation KB may carry a `no` is the OWNER's open policy question (qu); held until decided. If the owner accepts retired KBs, this row lands at no/B as written. PROPOSAL AS WRITTEN: CLAIM: ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns rather than one-off manual sends. VERDICT: no. NEW SURFACE (329th): the DECOMMISSIONED talech Zendesk help centre, which the 318th/322nd notes record as HTTP 401 and which held the only Campaigns documentation, was recovered whole from Wayback: CDX (help.talech.com/hc/*) returned 1,217 rows / 1,072 article URLs, deduped to 453 unique article ids, latest 200 snapshot each fetched with /web/<ts>id_/ -- 453/453 bodies, 0 failures, 1,167,129 chars of article text. EVIDENCE: the recovered Campaigns reference (article 205011699, updated 2020-05-14) documents the whole feature as a four-step MANUAL send: 'Step 1: Select the type of Campaign you would like to send a message campaign or a discount campaign... Step 2: Select recipients You can send this campaign to all customers or filter based on average spend, number of visits or days since they last visited your store. You can also manually select the customers you want to receive this campaign... Step 3: Choose template... Step 4:Confirm Once you have finalized your template, confirm the campaign details & recipients before hitting Send.' The only campaign types are 'Regular Campaigns ... used for general announcements' and 'Discount Campaigns'; 'The campaign discount can only be redeemed during the timeframe the campaign is created for.' The sibling 'What is the Campaigns feature?' (205011299) adds that it is a $29/month premium add-on and that 'This bulk sending service isn't available to Elavon customers at the moment. For bulk email services, please contact your Elavon account representative. Elavon offers its own suite of services for this feature within Fanfare loyalty.' Fanfare is a separate Elavon/third-party gift+loyalty product activated by an Elavon sales rep (article 203701595), i.e. another publisher's product, not a talech feature. 'days since they last visited' is a recipient FILTER on a one-off send, not an always-on win-back. BOUND/CONTROLS: denominator 453 retired docs / 1,167,129 chars, tokenised case-insensitive word-boundary: campaign 26 hits in only 2 docs (205011699 Campaigns + 207373126 talech Customer Loyalty Program); 'recurring|always.on|scheduled send/email/campaign' 0; win.?back 0; lapsed 0; 'first visit' 0; drip 0; 'automat\w* (email|message|campaign)' 1 hit and it is POISON (Online Ordering Setup Guide's transactional order-confirmation emails); birthday 2 hits, both POISON (a Homebase employee record field, and a 2019 build note 'Fixed birthday entry saving when editing the customer info' -- a customer DATA field, no campaign). This closes the exact gap the 322nd note named ('cannot determine whether Campaigns ships birthday, first-visit or lapsed win-back automations without reading a page that is gated'). Corroborated by the live corpora already on disk: US 268 + CA 362 + EU 226 Salesforce article bodies (no campaign article at all; birthday 0) and the app.talech.com 641-file back-office bundle (birthday/win-back/lapsed/first visit all 0), plus the Elavon Register 9.4.0 dashboard screenshot at 1000px (itunes.apple.com/lookup id=582116695, 5 iPad shots read as images) whose six tiles are Register, Orders, Tables, Cash Drawer, Reports, Back Office -- no marketing or campaigns module. Retrieved 2026-09-18. adversarially verified
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.
Triggers post-transaction feedback requests and routes responses by score, sending low scores to private service recovery and high scores toward public review sites. differentiator
guest-loyalty-review-capture-routing
Not scored by this record.
Includes a native referral mechanic with per-guest codes or links, attribution of the referred guest's first order, and two-sided rewards.
guest-loyalty-referral-program
Not scored by this record.
Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance, as an alternative to requiring a branded app download. differentiator
guest-loyalty-wallet-pass
Not scored by this record.
Provides admin tooling to fulfill guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records.
guest-loyalty-privacy-rights-tooling
Not scored by this record.
Enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log.
guest-loyalty-redemption-fraud-controls
Not scored by this record.
Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing (claim-level; verify it is a shipped product feature, not a roadmap statement). differentiator
guest-loyalty-ai-offer-recommendation
Not scored by this record.
Offers native stored-value/gift card balances tied to the same guest profile and redeemable across all locations of the brand.
guest-loyalty-stored-value-gift
Not scored by this record.
Labor & workforce
Employees clock in and out at the POS terminal using a PIN, badge, or card, with no separate time-clock hardware required.
labor-clock-in-at-pos
The Employee Timeclock reference documents POS-native time capture with no separate hardware: employees created on talech.com are 'assigned a pin number which they type in the number, then select the Clock in button' on the talech POS, after which they are 'brought to the register screen and there will be a sign at the top of the screen which confirms the clock in was successful'. Clock-out is the red circular button on the dashboard screen, PIN, then 'Clock Out', with an option to take a configured break instead (length and paid/unpaid customisable) and an offer to 'print out their hours for their shift'. Recorded hours 'automatically feed into the Labor Cost Setup' and surface in the Labor Cost report on talech.com and from the Register back-office Reports tab. The credential is a PIN, which the claim accepts; a separate 'Sign In' access code exists for employees who do not need to clock in. https://help.talech.com/s/article/Employee-Timeclock · retrieved 2026-08-04
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.
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
Permissions are per discrete action across three groups, assigned to editable roles. Register Permissions include Discounts, Regular Discount, Custom Item Discount, Refund, Return Without Receipt, No Sale ('Provides a No Sale button to open the cash drawer'), Reports, Settlement, View orders from other employees, Adjust taxes on order, Voids, Resend Orders, Transfer Orders and Cash Drawer; Store Permissions add Edit Timesheet, Edit Cash Drawer Shift, Edit Menu, Business Shift, Gift Cards, Inventory and Stock Take, Manage Employees; Business Permissions add Taxes, Loyalty and talech Web Access. Permissions are editable per role and, separately, per individual employee. Per-location scoping is documented in the multi-location reference: on a shared multi-store, 'Employees can have access to multiple locations as well as differing roles at each location'. https://help.talech.com/s/article/Employee-Permissions-Breakdown · retrieved 2026-08-03
Manager overrides and approvals are attributed to the individual approver and written to an immutable audit trail queryable after the fact.
labor-manager-override-audit
Override capture is real and attributed for voids: 'If the Void permission is not enabled, the void will require a manager or admin PIN or swipe card ... Every void is recorded in talech. The voided items report will include the employee initiating the void, the manager approving the void, date/time the void occurred, the item, the dollar amount, the reason.' It is queryable after the fact -- the Voided Items Detail report on talech.com gives 'individual transaction detail of voided items showing which item was voided, who approved it, amount voided, the reason', over date ranges of 1-365 days. Shortfall: the same manager-PIN flow covers Return and Discount overrides, but no report captures the approver for those -- the Discount Used report lists only the employee who issued the discount, and no return/refund override report is documented. https://help.talech.com/s/article/Voiding-an-Item · retrieved 2026-08-03
Builds and publishes employee shift schedules inside the same platform that holds the timekeeping data, rather than requiring a third-party scheduling app. differentiator
labor-native-scheduling
Not scored by this record.
Generates recommended staffing levels or labor hours by daypart from the operator's own POS sales history, not just a static template. differentiator
labor-demand-labor-forecast
Not scored by this record.
Displays labor cost as a percentage of sales in real time during service on a manager view or POS, not only in end-of-day or next-morning reports. differentiator
labor-realtime-labor-percent
Not scored by this record.
Warns or blocks at clock-in when an employee is approaching or would cross a configured overtime threshold, before the overtime is incurred. differentiator
labor-overtime-prevention
Not scored by this record.
Configures meal and rest break rules per state or jurisdiction, prompts required break attestation, and flags missed breaks for premium pay. differentiator
labor-break-compliance-by-state
Not scored by this record.
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.
Reports per-employee sales performance metrics (average check, items or category attachment rate, void and comp rate) by server or cashier. differentiator
labor-server-performance-metrics
Not scored by this record.
Inventory, purchasing & cost control
Supports multi-level recipe/BOM costing where a recipe can contain sub-recipes (prep items) and plate cost recalculates automatically when any component ingredient's cost changes.
inventory-recipe-bom-costing
A single-level bill of materials exists as bundles and assemblies: components are searched for and added with a quantity each, 'A bundle deducts the inventory when it's added to the order', 'An assembly deducts the inventory when it's first created as an assembly', and variations can carry a different component set per size. Shortfalls against multi-level recipe costing: components are products only -- the whole walkthrough, on Register and on talech.com, adds products to a bundle and nothing in it attaches a bundle or a prep item as a component, so there is no sub-recipe layer; there is no recipe, plate-cost or theoretical-cost object at all, cost living only as the per-product Cost and Markup % fields on the product form, and the bundle price is set by hand ('Set a price for the bundle/assembly in the Bundle Price field'), with the auto-calculated figure beside it derived from component price, not component cost -- so no plate cost recalculates when an ingredient cost changes. talech's own answer to raw-to-usable yield is arithmetic by hand: '1 bottle = 1 unit. I serve 5 glasses per bottle. 1 divided by 5 is .2.' https://help.talech.com/s/article/Creating-Product-Bundles-and-Assemblies-new · retrieved 2026-08-04
Stores purchase unit, recipe unit, and count unit per item with explicit conversion factors, plus a yield/waste percentage applied to raw-to-usable conversion.
inventory-unit-conversion-yields
The product record carries one Unit of measure, not a purchase/recipe/count triple: the Inventory section is Track Inventory, Unit of measure, Item #, Barcode and on-hand Inventory, with no conversion-factor and no yield or waste percentage field. talech's own answer for raw-to-usable conversion is a manual workaround -- to sell glasses from a bottle you build a bundle and compute the factor by hand: 'For our bottle of wine example, 1 bottle = 1 unit. I serve 5 glasses per bottle. 1 divided by 5 is .2. So, one glass of wine is going to be .2 for the quantity in the bundle.' The operator, not the system, stores the conversion, and no yield allowance is applied. https://help.talech.com/s/article/Sales-Unit-Inventory-Volume-For-Poured-Drinks-For-a-Keg-or-Bottle-from-Dashboard · retrieved 2026-08-03
Produces a theoretical-vs-actual usage variance report per item for a defined count period, showing theoretical usage from POS sales times recipe, actual usage from counts plus receipts, and the variance in both units and currency. differentiator
inventory-theoretical-vs-actual
Not scored by this record.
Depletes ingredient on-hand quantities in near real time as orders are fired at the POS, including depletion driven by modifier selections, not only in an end-of-day batch. differentiator
inventory-realtime-depletion
Not scored by this record.
Automatically 86s (marks unavailable) menu items on the POS, online ordering, and connected third-party delivery menus when a component ingredient hits zero or a configured threshold. differentiator
inventory-86-auto-sync
Not scored by this record.
Supports full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts.
inventory-count-modes
CLAIM: full physical count, ad-hoc spot counts of a subset, scheduled recurring cycle counts, per-count variance history. VERDICT: partial/B -- Stocktake covers full or subset counts and logs each change, but no scheduled/recurring cycle count and no variance record is documented. EVIDENCE: https://help.talech.com/s/article/how-to-conduct-a-stock-take-new (2025-06-11): "All Products: Shows all products that have inventory tracking on." / "Stocktake List: Shows any added product you select that you would like to adjust inventory for."; on talech.com "This screen will show stocktakes for the specified day."; "A stock take can be conducted regularly"; "Stocktake is a premium feature". https://help.talech.com/s/article/In-App-Inventory-Log (2025-11-03): Stock take "record[s] the changes in a report found on talech.com". https://help.talech.com/s/article/Inventory-Log-Register (2025-05-22): log actions "Add ... through Stock Take" / "Remove ... through a Stock Take". SHORTFALL controls over the 268-article census: "cycle count" 0, "cycle" 0, "variance" 0, "schedule"-for-counts none; "Stock Take Report" 2 hits (1 doc) with no variance field described. Surface: live Aura census of help.talech.com (Knowledge__kav; body = Discussion__c + Steps__c + Summary__c concatenated, discovered via getObjectInfo): 268 sitemap articles all live, href fixpoint added 2 slugs that are dead (Printing-Barcode-Labels-from-talech-com, Appointment-Settings), so 268/270 held with bodies; LastPublishedDate range 2024-10-30..2026-09-11. Retrieved 2026-09-16. https://help.talech.com/s/article/how-to-conduct-a-stock-take-new · retrieved 2026-09-16 adversarially verified
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.
Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.
inventory-shelf-life-expiry
Not scored by this record.
Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting.
inventory-bar-partial-bottle
Not scored by this record.
Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.
inventory-cogs-gl-export
Not scored by this record.
Inventory and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator
inventory-native-not-partner
Not scored by this record.
Reporting, BI & data access
Provides a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise.
reporting-realtime-dashboard
A browser dashboard exists off-premise on talech.com: 'Use the Dashboard to see a quick overview of the health of your business without having to open multiple reports. You'll get a summary of key metrics to help with the daily or weekly monitoring of your business' performance', over four report categories, and a single-day range defaults to 'Hour' grouping on the chart. Shortfalls: it is browser-only -- the vendor's own talech Mobile overview guide routes reporting away from the phone app ('Reports (Available in the talech.com account.)' and 'access your account online by going to talech.com on a tablet or desktop device to manage the back-end account-specific information and reports'), so there is no owner mobile app dashboard; and no data-freshness interval is stated anywhere, while the one latency the docs do state runs the other way -- cash drawer reports are 'updated nightly and include only closed shift data'. Sub-minute or within-minutes currency is therefore not established, only the daily/weekly monitoring the vendor describes. https://help.talech.com/s/article/Reports-on-talech-com · retrieved 2026-08-04
Generates a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types, and expected cash deposit in one document.
reporting-eod-closeout
The Register Summary Report is a single printable end-of-day document ('you can also print the report by selecting the print icon') covering Gross Revenue, Discounts, Refunds, Store Credit Issued, Net Revenue, Service Charges, Tax, Tips ('total dollar amount of all credit card tips collected'), and Voids; a Taxes block with taxable/non-taxable revenue per tax name; Split by Payment Type and Split by Card Type for tender reconciliation; and Receipts by Employee including 'Cash due at the end of the day/shift (cash due is cash sales minus tips)'. Expected cash deposit is completed by the Close Shift flow, whose 'optional printout will provide an over/short amount for the drawer' against Net Cash in Drawer. Filterable by employee and by date. https://help.talech.com/s/article/iPad-Understanding-Summary-Reports · retrieved 2026-08-03
Provides a product mix (PMIX) report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center.
reporting-pmix-modifier-level
A PMIX report exists but stops at item level: 'Product Mix report: Summary of products in the store inventory or sold during the selected date range. View percentage of revenue a specific product contributed to its associated category or tags', alongside Sales by Item, Sales by Category and Sales by Tag. Shortfall: no individual-modifier reporting. The Register Summary Report's Split by Category block 'breaks down each category and modifier list that generated sales', i.e. aggregated to the modifier set, not the modifier option; and talech states outright that 'Quantity tracking for modifiers, add-ons or exclusions is not something you can get reports on from your talech account'. No daypart or revenue-centre filter is offered on the Product Mix report. https://help.talech.com/s/article/reports-products-services · retrieved 2026-08-03
Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.
reporting-comps-voids-audit
Not scored by this record.
Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.
reporting-cash-over-short
Not scored by this record.
Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.
reporting-labor-productivity
Not scored by this record.
Reports per-server metrics including average check, items per check, attachment rate for named categories, and tips as a percentage of sales. differentiator
reporting-server-scorecards
Not scored by this record.
Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator
reporting-channel-profitability
Not scored by this record.
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.
Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator
reporting-public-api
Not scored by this record.
Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator
reporting-webhooks
Not scored by this record.
API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator
reporting-api-not-upcharged
Not scored by this record.
Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator
reporting-tier-paywall
Not scored by this record.
Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator
reporting-history-retention
Not scored by this record.
Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator
reporting-anomaly-alerts
Not scored by this record.
Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.
reporting-nl-query
Not scored by this record.
Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator
reporting-guest-cohorts
Not scored by this record.
Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator
reporting-sales-forecast
Not scored by this record.
Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.
reporting-tip-tax-compliance
Not scored by this record.
Multi-location, franchise & enterprise governance
Supports a named organizational hierarchy of at least three levels (e.g. enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations.
multi-location-org-hierarchy
The multi-location model is exhaustively enumerated as two flat options: 'You have two account options for connecting your businesses: shared multi-store or linked multi-store.' Both are a flat set of sites under one owner -- you 'select the individual location using the menu dropdown in the top left', 'Each report is available on a location basis for each account type', 'Orders are separated by location', and on Register 'you are prompted to select a location. All register functions, orders, and back-office settings will be specific to that location.' There is no region, group, or brand tier between owner and location, and nothing for reporting or permissions to be scoped to above a single site. https://help.talech.com/s/article/Multi-Location-Accounts-new · retrieved 2026-08-03
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
talech has no price tier or zone object; per-location pricing is achieved by duplicating the item. Sync explicitly creates a separate product record at each site -- 'If the product doesn't exist at the location being synced to, talech will create a new one ... talech will update the product at location A and create a new product at location B' -- and differing prices are produced by de-selecting price from 'the product attributes you want to sync'. There is no location group to price against, no channel price book (the online store shows the same product price, controlled only by an include/exclude toggle), and no daypart price schedule in the product-pricing fields, which are Enable Variable Pricing, Cost, Markup % and Price. https://help.talech.com/s/article/Multi-location-product-sync-new · retrieved 2026-08-03
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.
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.
Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.
multi-location-central-labor-policy
Not scored by this record.
Hardware & physical footprint
The POS software runs on commodity off-the-shelf hardware (standard iPads, Android tablets, or PCs) that the operator can buy from a third party, rather than only on vendor-supplied proprietary terminals. differentiator
hardware-commodity-devices
Not scored by this record.
Vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs.
hardware-os-platforms
CLAIM: vendor docs name client OSes and minimum OS versions/device specs. VERDICT: partial/B (downgraded from a proposed yes at merge: the claim requires minimum OS versions AND device specs; the article publishes minimum OS and app versions per register type but no RAM, storage or model-level spec for merchant-supplied iPads, phones or Android devices, which is the named shortfall). EVIDENCE: https://help.talech.com/s/article/talech-Minimum-App-Requirements (published 2025-11-20) tabulates "Register type / Minimum version of app / Minimum version of Operation System (OS)": "iOS Mobile 5.14.1 16 or greater"; "Android Mobile 5.11.1 10"; "iOS Register 7.4.0 15 or greater"; "Android Register 9.2.0 AN 9 or greater"; "talech Terminal 1.12.0 AN 10"; "Any devices operating on iOS 14 or earlier will not be compatible"; "talech Register only supports AN 9 or greater." Device classes are named per article (Poynt 5/6/C and Newland N910 "run on a modified Android operating system"; https://help.talech.com/s/article/talech-Register-Setup "It runs on an Android operating system"). Caveat: no RAM/storage spec for customer-supplied iPads/phones; back office talech.com is web. Surface: live Aura census of help.talech.com (Knowledge__kav; body = Discussion__c + Steps__c + Summary__c concatenated, discovered via getObjectInfo): 268 sitemap articles all live, href fixpoint added 2 slugs that are dead (Printing-Barcode-Labels-from-talech-com, Appointment-Settings), so 268/270 held with bodies; LastPublishedDate range 2024-10-30..2026-09-11. Retrieved 2026-09-16. https://help.talech.com/s/article/talech-Minimum-App-Requirements · retrieved 2026-09-16 adversarially verified
Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.
hardware-handheld-purpose-built
Not scored by this record.
The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator
hardware-handheld-battery-swap
Not scored by this record.
Handhelds support cellular/LTE connectivity as a documented fallback when store Wi-Fi drops, either built into the device or via a vendor-supplied failover.
hardware-handheld-lte
Not scored by this record.
Terminals continue to take orders, print to kitchen, and record cash sales with the internet down, and the vendor documents explicitly which functions degrade (card auth, loyalty lookup, refunds).
hardware-offline-mode
talech publishes offline scope explicitly, in three named buckets. Fully supported: 'Create/save open orders', 'Process Cash, Check, and Other payment types', 'Local pre-authorization', PIN sign-in between employees. Limited: cash-drawer bypass, settings changes sync on reconnect, 'Open/Closed orders stored locally on iPad', table layout can create new orders. No access: 'Credit card transactions, tip adjust, and settlement', 'Integrated electronic gift cards and store credit', 'Refunds via any type of payment or exchanges', 'Reports and Customer list', 'Order syncing between different iPads', 'Editing Menu/Inventory'. Shortfall: kitchen printing is not addressed in any of the three buckets, so the print-to-kitchen half of the claim is undocumented; and offline orders are 'only stored on the iPad that created the order', with 'the last iPad to modify an order' the only one able to view it. https://help.talech.com/s/article/Managing-Orders-in-Offline-Mode · retrieved 2026-08-03
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
talech's first-party kitchen output is thermal printing and nothing else: 'When orders are sent to the kitchen from the Register app, the items in that order will go to printers based on their Tag(s) or Category', configured per printer under Back Office > Settings > Printers, and an order reaches the kitchen via 'Select Send to dispatch an order to the kitchen printer'. No kitchen display product exists anywhere in the documentation: the complete printer settings reference enumerates every global and per-printer setting with no display device, the only screens documented are customer-facing displays, the online-ordering settings' highest automation is 'Auto-send to kitchen' addressed to stores 'equipped with kitchen printers', and the live help-centre sitemap (269 articles) contains no KDS article. With no first-party KDS there is no bump-bar or touch input and no course/fire timing to assess. https://help.talech.com/s/article/Printers-Setup-Printers-to-Create-Kitchen-Receipts · retrieved 2026-08-04
Offers a self-order kiosk running the same menu and modifier engine as the POS, in both countertop and freestanding form factors, with integrated payment and accessibility (ADA) compliance documented. differentiator
hardware-kiosk
Not scored by this record.
Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, and speaker/headset integration, with a documented timer/speed-of-service measurement.
hardware-drive-thru
Not scored by this record.
Works with standard ESC/POS thermal receipt and kitchen printers from more than one manufacturer (e.g. Epson and Star), including LAN/Ethernet printers, rather than only vendor-branded printers.
hardware-printer-compatibility
Not scored by this record.
Supports the standard peripheral set — cash drawers (including multi-drawer per terminal), barcode scanners, scales for by-weight items, and customer-facing displays — with a published compatibility list.
hardware-peripherals
Not scored by this record.
Card entry happens on a PCI-listed PTS device using validated point-to-point encryption, so the POS application and tablet stay out of PCI scope; the vendor states the merchant's SAQ type.
hardware-p2pe-terminal
Not scored by this record.
Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. differentiator
hardware-tap-to-phone
Not scored by this record.
Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator
hardware-pricing-transparency
Not scored by this record.
Hardware can be purchased outright (owned) as an alternative to a mandatory lease or subscription-bundled rental, and the vendor states which. differentiator
hardware-ownership-vs-lease
Not scored by this record.
Vendor documentation confirms whether hardware purchased from the vendor remains usable with other software after cancellation, i.e. it is not software-locked or remotely bricked. differentiator
hardware-usable-after-churn
Not scored by this record.
Publishes a hardware warranty term and a replacement/advance-exchange SLA with a stated turnaround (e.g. next-business-day depot swap). differentiator
hardware-rma-sla
Not scored by this record.
Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.
hardware-byod
Not scored by this record.
Provides a remote device-management console showing each terminal, printer, and KDS as online/offline, with remote reboot, software-version visibility, and staged rollout of updates. differentiator
hardware-remote-device-management
Not scored by this record.
Integrates with specialty beverage hardware — self-pour tap walls, flow meters, or liquor pour spouts — such that pours post to a POS tab automatically.
hardware-selfpour-scales
Not scored by this record.
Supports inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call.
hardware-callerid-integration
Not scored by this record.
Integrations, API & extensibility
Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.
extensibility-public-api-docs
MERGE NOTE: cited to the LIVE help centre, whose census (US 268 article bodies, 0 new since q314) holds no API reference; the retired article quoted below is archived at https://web.archive.org/web/20210618212525id_/https://help.talech.com/hc/en-us/articles/115004761986-How-do-I-give-Developers-API-access-to-my-talech-account- and only describes the token-provisioning flow. CLAIM: public, self-serve API reference documentation readable without a signed partner agreement, NDA or sales call. VERDICT: no. NEW SURFACES (329th): (a) the decommissioned talech Zendesk help centre recovered whole from Wayback -- 453 unique article ids, 453/453 bodies, 1,167,129 chars (see the loyalty cell for the method); (b) developer.elavon.com, the public developer portal of talech's owner Elavon/U.S. Bank (Next.js; every path including /robots.txt and /sitemap.xml returns the same soft-200 shell, so the catalogue was read from the home page's __NEXT_DATA__: 34 menu links across exactly three products -- elavon-payment-gateway, isv-and-partners, epg-merchant-portal-user-guide; 'talech' 0, 'point of sale' 0, 'POS' 0, 'webhook' 0 in that payload). EVIDENCE: the vendor's only API document, recovered at 115004761986 (updated 2021-05-13), is an access-provisioning page, not a reference: 'talech allows you to authorize 3rd party developers to access your merchant account data on your behalf. Note: Since talech's APIs provide full access, please make sure you only provide access to trusted 3rd parties. To provide API access, login to your talech account on talech.com and click on your name in the top right corner and select "Account Settings"... click on the "Generate New Token" link. Next, enter the developer name and email address and click on the "Generate API Token" button... If you have any issues providing access to your developer, our API support team will address your issue within 2 weeks.' The merchant, not the developer, provisions a token from inside the logged-in back office; no reference, no endpoint list, no base URL is published anywhere. This matches the 322nd's live finding that app.talech.com's OAuth consent page refuses unregistered apps with 'Requesting party is not registered as a talech partner. If you are the app developer, please contact support to learn how to register.' BOUND/CONTROLS: this is a PUBLICATION claim, so the bound is a publication census of every surface talech publishes: 453 retired Zendesk docs (denominator 1,167,129 chars; tokenised word-boundary: 'api reference|api documentation|developer documentation|developer portal' 0 hits; webhook 0; OAuth 0; API 27 hits in 6 docs, of which the only talech-API doc is 115004761986 and the rest are POISON -- Stripe online-ordering API keys, a Zebra scanner 'Symbol Native API (SNAPI)' programming barcode, and a French build note about Fanfare's APIs), plus the live US 268 / CA 362 / EU 226 Salesforce article bodies already censused (API 1 hit, a convergepay firewall line), plus api.talech.com answering HTTP 200 'RESTEASY003210: Could not find resource' at /swagger.json, /v2/api-docs, /api-docs, /docs and a nonsense control path alike (no spec), developer.talech.com NXDOMAIN, no api-docs/api-reference string in the 641-file app.talech.com bundle, and the parent's own public developer portal publishing a payment-gateway API with zero POS surface. Caveat for the reviewer: talech does run a real merchant API, and it is unpublished -- this `no` is on the publication of a reference, not on the API's existence. Retrieved 2026-09-18. https://help.talech.com/s/?language=en_US · retrieved 2026-09-18 adversarially verified
API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator
extensibility-api-access-cost
Not scored by this record.
A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator
extensibility-free-sandbox
Not scored by this record.
Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).
extensibility-oauth-partner-apps
CLAIM: third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static keys). VERDICT: partial (OAuth 2.0 authorization-code grant approved by the operator is shown; scoping and per-app revocation are not). NEW SURFACE (322nd): app.talech.com, talech's current merchant back office (production; named as the US login URL in www.talech.com/config.js, "talech admin" in its analytics tags). Its HTML sits behind an AWS WAF JavaScript challenge (curl gets HTTP 202 x-amzn-waf-action: challenge), so the login page was loaded in headless Chromium with no login, and the Vite chunks it references were fetched to a fixpoint: 641 files, 12 MB, every relative ./ or assets/ reference held at 200 except remoteEntry.js (a module-federation remote on onlinebanking.usbank.com, the U.S. Bank login widget); 3 non-literal import() calls, all in the federation runtime. Source maps are NOT public: every <chunk>.js.map and /.vite/manifest.json returns the same 26,040-byte SPA HTML shell (soft 200). The bundle carries the full en_US/fr_CA i18n dictionary (index-DSJmYvf8.js, 1.37 MB) and the route table (routes.config: 42 routes). Caveat: this is the NEW admin; user.service has "redirectToClassic: /api/v1/backoffice/auth/redirect/classic" and reports offer "downloadClassicReport", so a Classic back office still exists and is not covered by this corpus. EVIDENCE: the route table has "authorize: \"/authorize\"" and the settings dictionary titles it "authorize: \"Authorize Partner Permissions\"". authorize-page.component-Dj1SJIhY.js reads the OAuth parameters "clientId: \"client_id\", redirectUri: \"redirect_uri\", state: \"state\", scope: \"scope\", accessType: \"access_type\", responseType: \"response_type\"" (default response_type "code"), fetches the client from "getClientInfo: \"api/v1/integrations/oauth\"", shows "{{appName}} wants access to your talech account." with the partner's privacy policy and terms, and offers Deny / Allow buttons; Allow posts to "approveOAuth: \"api/v1/integrations/oauth/approve\"" and redirects to redirect_uri with "code" and "state"; Deny redirects with error "access denied". redirect_uri must match an allowlist of registered partners (joinhomebase.com/talech_authenticate, service-proxy.deputy.com, app.simpleorder.com/talech, onesaas, connector-talech.prd.marlin.maestrano.io, accounts.skilljar.com), otherwise "Requesting party is not registered as a talech partner." / "If you are the app developer, please contact support to learn how to register." SHORTFALL: the scope parameter is passed through but never displayed or chosen by the operator (the consent text names no permissions); no screen lists or revokes connected partner apps: controls over all 641 files, tokenised case-insensitive: revok* 9 (Proxy.revocable, URL.revokeObjectURL, and the employee-status help "An Inactive status revokes all permissions for the employee" -- all poison), disconnect 21 (all Mutation/Resize/IntersectionObserver.disconnect, poison), "connected apps" 0, "access token(s)" 0. Revocability and scoping are unstated, so partial. The Classic back office is not covered. Retrieved 2026-09-17. https://app.talech.com/assets/authorize-page.component-Dj1SJIhY.js · retrieved 2026-09-17 adversarially verified
The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.
extensibility-webhooks-push
Same evidence trail as the OAuth cell. The live integrations reference describes data movement only in business terms ('Elavon automatically sends sales totals, payments, and employee time to connected accounting and payroll platforms'; Deliverect orders 'flow directly into your POS') and never names a transport, event model, or polling-versus-push mechanism. No developer documentation is reachable: developer.talech.com does not resolve, www.talech.com/api returns HTTP 403, and the legacy API-access article at help.talech.com/hc/en-us/articles/218019803 returns HTTP 401 along with the rest of the /hc/en-us tree. Nothing establishes whether order-lifecycle webhooks are published. || 318th: NEW (318th): crt.sh certificate logs name event-api.talech.com and event-api-dev.talech.com, which suggests an internal event API, but neither answered (status 0) and nothing documents it. CA (362 bodies) and EU (226) talech help centres: "webhook(s)" 0 hits in each. Orphan US article QuickBooks-Integration-with-talech describes a once-daily sync ("your sales and payment data will continue to automatically sync each day"), a batch pattern, not webhooks. Retrieved 2026-09-16. || 322nd: NEW (322nd): NEW SURFACE (322nd): app.talech.com, talech's current merchant back office (production; named as the US login URL in www.talech.com/config.js, "talech admin" in its analytics tags). Its HTML sits behind an AWS WAF JavaScript challenge (curl gets HTTP 202 x-amzn-waf-action: challenge), so the login page was loaded in headless Chromium with no login, and the Vite chunks it references were fetched to a fixpoint: 641 files, 12 MB, every relative ./ or assets/ reference held at 200 except remoteEntry.js (a module-federation remote on onlinebanking.usbank.com, the U.S. Bank login widget); 3 non-literal import() calls, all in the federation runtime. Source maps are NOT public: every <chunk>.js.map and /.vite/manifest.json returns the same 26,040-byte SPA HTML shell (soft 200). The bundle carries the full en_US/fr_CA i18n dictionary (index-DSJmYvf8.js, 1.37 MB) and the route table (routes.config: 42 routes). Caveat: this is the NEW admin; user.service has "redirectToClassic: /api/v1/backoffice/auth/redirect/classic" and reports offer "downloadClassicReport", so a Classic back office still exists and is not covered by this corpus. Controls over all 641 files, tokenised case-insensitive: webhook(s) 0; "event api" 0. The bundle config names back-end hosts wapi-prod, data-api-prod, intsrv-prod and iai-web-app-be-prod (.us-east-1.talech.com) but no event or webhook service; the integrations routes are only deliverect, quickbooks, sage, xero, paychex, gusto. Nothing a merchant or partner can subscribe to. The server API is not covered, so still unknown. Retrieved 2026-09-17. || 329th: NEW SURFACE (329th): the decommissioned talech Zendesk help centre, recovered whole from Wayback -- 453 unique article ids, 453/453 bodies, 1,167,129 chars (CDX help.talech.com/hc/* -> 1,072 article URLs deduped by id, latest 200 snapshot via /web/<ts>id_/). It contains the only talech API document ever published, 115004761986: the credential model is a merchant-generated static bearer token ('Generate New Token' -> 'enter the developer name and email address' -> 'Generate API Token', revocable), with 'talech's APIs provide full access' and 'our API support team will address your issue within 2 weeks'. Controls over that 453-doc corpus, tokenised case-insensitive word-boundary: webhook(s) 0 hits, OAuth 0, 'api reference|api documentation|developer portal' 0; no callback, subscription or event-notification surface is named anywhere. Elavon's public developer portal (developer.elavon.com, catalogue read from the home page __NEXT_DATA__: 34 menu links, products elavon-payment-gateway / isv-and-partners / epg-merchant-portal-user-guide) contains 'webhook' 0 and no POS product at all. NOT published as `no`: talech's merchant API is itself unpublished (see the public-api-docs cell), so no public census can bound what its partner-registered endpoints emit, and the crt.sh names event-api.talech.com / event-api-dev.talech.com still answer nothing. 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.
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.
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.
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.
A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator
extensibility-data-portability-exit
Not scored by this record.
Reliability, offline & operations
Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.
reliability-offline-order-entry
Order entry survives an outage: 'Create/save open orders' and 'Local pre-authorization' are listed under Fully supported offline features, cash/check/other tenders continue, and under Limited offline features 'Table layout allows to create New Orders and view tables in use'. Shortfall: the vendor's three-bucket offline list never addresses ticket routing to kitchen printers or check printing, so those halves of the claim are undocumented; and the orders created are single-device only -- 'These orders are only stored on the iPad that created the order', with 'Order syncing between different iPads' listed under Features with no access while offline. https://help.talech.com/s/article/Managing-Orders-in-Offline-Mode · retrieved 2026-08-03
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
Re-checked against the full census rather than slug-by-slug. Surface: live Aura census of help.talech.com (Knowledge__kav; body = Discussion__c + Steps__c + Summary__c concatenated, discovered via getObjectInfo): 268 sitemap articles all live, href fixpoint added 2 slugs that are dead (Printing-Barcode-Labels-from-talech-com, Appointment-Settings), so 268/270 held with bodies; LastPublishedDate range 2024-10-30..2026-09-11. "offline" occurs in 1/268 docs (Managing-Orders-in-Offline-Mode, published list of fully supported / limited / no-access features; kitchen printing absent from all three); "KDS"/"kitchen display" occur only in Bulk-Product-Upload-new (a short-name field "printed on order tickets or displayed on KDS"); "without internet" 0; "no internet" 0. No article states whether send-to-kitchen printing works offline. The offline article is an enumeration of features, but printing is neither listed as supported nor as unavailable, so it cannot carry a no. Stays unknown. Retrieved 2026-09-16. || 318th: NEW (318th): the CA (ca.help.talech.com/canew, 362 bodies) and EU (eu.help.talech.com/eunew, 226) help centres hold the same Managing-Orders-in-Offline-Mode article (6,044 bytes; same three lists) and it is the only doc containing "offline" in each; kitchen printing is again in none of the supported / limited / no-access lists. No new evidence. Retrieved 2026-09-16. || 329th: NEW SURFACE (329th): the decommissioned talech Zendesk help centre recovered whole from Wayback -- 453 unique article ids, 453/453 bodies, 1,167,129 chars. It holds the KDS reference that the live Salesforce help centre does not publish at all (115005457843, 'Kitchen Display System (KDS) Equipment/Setup'): talech's KDS is not a software display but an Epson TM-U220B-i printer plus Epson TM Expansion Boxes and a Bematech USB bump bar driving a VGA monitor -- 'All devices will need to be on the same network'; 'KDS Printer and Expansion boxes should auto-detect in Dashboard > Back Office > Settings > Printers'; 'Check IP address of device(s). If the IP on the device does not match the entry in talech, the KDS will not receive orders'; each expansion box 'will act as individual printers' with its own categories. With the live Printer Settings reference (per-printer IP address, per-printer Categories/Tags, 'Order Ticket Exclusion List for This iPad', 'Print Order Tickets after ... After Save Order: Once an order is saved, a kitchen ticket will print automatically') this establishes that both kitchen printing and KDS routing are iPad-to-LAN-IP-device paths configured per register, with no documented server hop. It does NOT state that they survive a WAN outage, so no verdict. Controls over the 453 retired docs: offline 20 hits in 6 docs -- the retired Offline Mode article 205031779 (an older copy of the same three-way list, kitchen printing again in none of the supported / limited / no-access lists), a Scheduled Maintenance notice of 2022-01-19 (4415547386779) that reprints the SAME list a third time verbatim and again omits printing, the Register FAQ 115005403283 (offline affects only order SEQUENCE numbers: 'The app must be able to reach the talech servers to set the sequence number of the order'), and a Bluetooth-printer troubleshooting page where 'offline' means the PRINTER is off (poison). Three independent copies of the vendor's offline enumeration all omit kitchen printing and KDS, so the enumeration still cannot carry a `no`, and the architecture alone cannot carry a `yes`. Corroboration only: the Elavon Register 9.4.0 dashboard screenshot at 1000px (itunes.apple.com/lookup id=582116695) shows the documented green/yellow/red connectivity cloud bottom-left and the six tiles Register / Orders / Tables / Cash Drawer / Reports / Back Office. Retrieved 2026-09-18. adversarially verified
The system automatically fails over to a backup printer or KDS station when a configured kitchen printer is unreachable, and alerts staff.
reliability-printer-fallback
The printer reference enumerates every available setting -- five global Advanced settings, the per-printer settings (Printer Name, IP Address, Printer Model, Font size, Categories, Tags), the twelve-row Order Ticket Printing advanced table and the Receipt Printing advanced table -- and none of them designates a backup printer or KDS, defines failover on an unreachable printer, or raises a staff alert. The only routing-override mechanism is the manual 'Order Ticket Exclusion List for This iPad', which 'blocks the iPad from sending receipts to that printer' -- a deliberate exclusion, not automatic failover. https://help.talech.com/s/article/Printers-General-Advanced-Settings · retrieved 2026-08-03
The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).
reliability-sync-conflict-handling
Not scored by this record.
The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).
reliability-offline-feature-matrix
Not scored by this record.
A public, per-component status page exists showing current and historical incident state without a login.
reliability-public-status-page
Not scored by this record.
24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.
reliability-247-live-support
Not scored by this record.
The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator
reliability-onsite-install
Not scored by this record.
A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.
reliability-hardware-replacement-sla
Not scored by this record.
The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.
reliability-pci-dss-4-attestation
Not scored by this record.
Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.
reliability-mfa-role-based-access
Not scored by this record.
A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.
reliability-self-serve-training
Not scored by this record.
Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. differentiator
reliability-failover-terminal-role
Not scored by this record.
Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.
reliability-cellular-backup
Not scored by this record.
Commercial, compliance & data ownership
Vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core POS software tier. differentiator
commercial-month-to-month-contract
Not scored by this record.
Vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. differentiator
commercial-no-early-termination-fee
Not scored by this record.
The auto-renewal term and the required cancellation notice window (e.g. 30/60/90 days) are stated in publicly accessible contract terms rather than only in a signed quote.
commercial-autorenew-terms-published
CLAIM: the auto-renewal term and the cancellation notice window are stated in publicly accessible contract terms. VERDICT: yes/B (vendor legal documents, anonymous PDFs). EVIDENCE: www.talech.com/terms (AWS WAF challenge to curl; rendered in a real browser) has a footer link "Terms of Service" -> https://www.mypaymentsinsider.com/api/file/c/Operating_Guide_English (Elavon Operating Guide OG2026/04, published April 30, 2026). Its CHAPTER 29 ELAVON POINT OF SALE (renamed from talech, change log Oct 2025) says: "The Elavon Point of Sale and Elavon Application are considered Services under the Agreement." Its glossary: "Agreement" means the Master Services Agreement, Payment Device Processing Agreement, Terms of Service...; and "Payments Insider also hosts the latest version of the Terms of Service and Operating Guide." The Elavon Terms of Service (November 2025, TOS2025/10) at https://www.mypaymentsinsider.com/api/file/c/Terms_of_Service_english, section 5.1: "the Agreement will remain in effect for a period of three years ("Initial Term") ... Thereafter, the Agreement will renew automatically for successive two year terms (successive six month terms with respect to Canada) ("Renewal Term")"; 5.2(a)(i): "Company may terminate the Agreement effective at the end of the Initial Term or any Renewal Term by providing written notice of non-renewal to Elavon at least 30 days prior to the expiration of the then current term." 5.3 requires a signed Elavon form. CAVEAT: Operating Guide ch.29 Term And Termination also says "Company may terminate use of the Elavon Application for convenience at any time by deleting the Elavon Application ... and contacting Elavon", so the app licence is terminable at will while the governing Agreement auto-renews; both are public. Retrieved 2026-09-16. https://www.mypaymentsinsider.com/api/file/c/Terms_of_Service_english · retrieved 2026-09-16 adversarially verified
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
Three named tiers with specific monthly dollar figures and setup fees on the bank's public site. https://www.usbank.com/business-banking/payment-solutions/in-person-payments/point-of-sale.html · 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
Page states hardware cost varies by device and by rental vs purchase, so outright purchase exists but no price list is published. https://www.usbank.com/business-banking/payment-solutions/in-person-payments/point-of-sale.html · retrieved 2026-08-01
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.
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.
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.
Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.
commercial-privacy-dsar-tooling
Not scored by this record.
Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator
commercial-wcag-kiosk-accessibility
Not scored by this record.
POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator
commercial-dual-pricing-compliant
Not scored by this record.
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 0 values — 0 upheld, 0 downgraded, 0 upgraded. It separately resolved 31 previously unknown values. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| order-capture-scheduled-orders | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | The 2026-08-01 pass recorded talech.com as 403 with no reachable documentation. That premise is wrong: the live Salesforce help centre at help.talech.com/s/ serves 269 server-rendered articles and publishes a sitemap. Scheduled ordering is documented directly - future-dated pickup orders are accepted even while the store is closed and land on Register > Orders > Online with the customer's chosen date/time, and under Auto-send to kitchen the configured prep time 'determines when Elavon POS sends an order to the kitchen'. Held short of yes because that prep-time estimate is a single store-level setting applying to website orders only (Deliverect orders follow Deliverect's own settings), release runs on 2-minute intervals, and off-hours orders enter the queue at next opening rather than at a computed fire time. source |
| menu-pricing-nested-modifiers | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-no | The modifier data model is enumerated end to end for both Register and talech.com and is exactly one level: product -> modifier set -> options, with the set carrying Add On/Exclusion, an optional price attribute, and min/max selections. Modifier sets attach to products; nothing in either walkthrough attaches a set to an option. Three-level nesting is not merely undocumented - it has no place in the documented object model. Min/max and forced selection (minimum of 1) are present at the single level that exists. source |
| menu-pricing-modifier-price-by-parent-size | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-no | The complete product-field reference gives the Modifier Sets section only two operations - attach an existing set, and Select Defaults - with no per-product or per-variation price override, and modifier price is a single value on the shared option. talech's own comparison table draws the boundary explicitly: modifiers 'can add an additional charge to the base price'; only variations 'can configure specific quantities and cost for each individual variant'. Per-size modifier pricing therefore requires duplicating the set. source |
| menu-pricing-topping-quantity-tiers | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-no | Two complete enumerations of modifier option configuration (Register and talech.com) offer an option name and an optional price and nothing else - no quantity, tier or multiplier field. talech separately states that modifier/add-on quantity is not even reportable. source |
| payments-gift-cards | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-yes | First-party gift is a documented shipped feature across POS, online ordering and back office, with activation, add-balance and balance-check on the terminal, an online balance checker, and Fixed/Reloadable/Promotional types. Group-wide redemption is established by the card-number uniqueness rule across all stores sharing a master owner and by the multi-location reference stating gift cards are shared across locations on a shared multi-store account. source |
| payments-refund-void-controls | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | Role-based authorisation is fully documented and per-action - Discounts, Regular Discount, Custom Item Discount, Refund, Return Without Receipt, No Sale and Voids are separate permissions, with a manager or admin PIN/swipe card required where the permission is off. Not yes because the approver-attributed audit record exists only for voids; the Discount Used report records the issuing employee rather than the approver, and no refund, return or no-sale override report is documented. source |
| kitchen-expo-consolidation | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-no | talech's documented kitchen output is thermal ticket printing routed by tag or category. Across 269 live help articles there is no kitchen display, expo screen, or bump/complete state - the only displays documented are customer-facing. With no screen and no bump event there is nothing that could consolidate multi-station items or gate order completion on every station bumping. source |
| kitchen-bump-bar-hardware | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-no | The claim presupposes a KDS. The complete printer/peripheral reference enumerates every global, per-printer and advanced setting and documents printed dockets throughout; no display device, bump bar or programmable keypad appears in it or in any peripheral setup article. There are therefore no supported bump-bar models to document. source |
| delivery-dispatch-board | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-no | Delivery in talech is an online-ordering order type whose entire configuration is enumerated as a toggle plus Payment Options, Order Amount Limits and a Delivery Area radius. No driver entity, assignment state, dispatch screen, elapsed-time view or multi-order run batching exists anywhere in the documentation. source |
| delivery-zone-pricing | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-no | There is exactly one delivery area - a radius - carrying one order minimum and one store-wide prep-time-derived promise time. With a single zone there is no per-zone fee, minimum or promise time to configure. source |
| digital-menu-single-source | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-yes | The ordering site renders the POS menu filtered by a category selection and a per-product 'Include product in online store' toggle on the same product record; Product Visibility is a checkbox for point of sale and/or online store, and modifier sets carry the same online flag. One item edit propagates - there is no separate digital menu build. source |
| digital-account-saved-payment | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-no | Two independent complete enumerations of the guest checkout (end-to-end walkthrough and features reference) list order type, table number, ready time, contact info, tip, gift card, payment, items and promo code. There is no sign-in, saved address, stored card or reorder; card details are entered on a pop-up each time. source |
| guest-loyalty-unified-profile | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | A single customer record with order history, loyalty points and key metrics is documented and can be attached to open or closed orders. Held to partial because no cross-channel identity resolution is published - the online checkout collects contact details without creating a guest account and no article states website orders match into the POS record, no dedup/merge rule is documented, and on linked multi-store accounts customer lists remain separated by location. source |
| labor-granular-rbac | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-yes | Permissions are granted per discrete action across three enumerated groups - including Voids, Refund, Return Without Receipt, Discounts, No Sale, Reports, Settlement, Edit Menu and Manage Employees - assigned to editable roles and further editable per individual employee. Per-location scoping is documented: on a shared multi-store, employees can hold access to multiple locations with differing roles at each. source |
| labor-manager-override-audit | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | Void overrides are attributed and queryable: the void record names the initiating employee, the approving manager, timestamp, item, amount and reason, and the Voided Items Detail report on talech.com exposes 'who approved it' over 1-365 day ranges. Not yes because the same PIN override also gates Returns and Discounts and no report captures the approver for those - Discount Used lists only the issuing employee. source |
| inventory-unit-conversion-yields | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-no | The product record carries one Unit of measure with no conversion factor and no yield/waste percentage. talech's own documented method for raw-to-usable conversion is a manual workaround - build a bundle and enter the fraction computed by hand (1 bottle / 5 glasses = .2). A vendor-recommended workaround in place of the capability. source |
| reporting-eod-closeout | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-yes | The Register Summary Report is a single printable document reconciling gross and net revenue, discounts, refunds, store credit, service charges, tax, tips and voids, with Split by Payment Type and Split by Card Type for tender reconciliation and per-employee cash due; the Close Shift printout supplies the over/short against expected cash. Every element the claim names is documented field by field. source |
| reporting-pmix-modifier-level | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | A Product Mix report exists but is item level. Modifier reporting reaches only the modifier list (set) in the Register Summary's Split by Category block, and talech states plainly that modifier/add-on quantity is not reportable. No daypart or revenue-centre filter is offered on Product Mix. Item half met, modifier half not. source |
| multi-location-org-hierarchy | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-no | The multi-location model is exhaustively stated as two options, shared or linked multi-store, both flat sets of sites under one owner with per-location reporting, orders and settings and a location selector at login. No region, group or brand tier exists between owner and location for reporting or permissions to scope to. source |
| multi-location-central-menu-publish | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | Cross-location publishing exists - edit a product, Save Changes & Sync, choose target locations and which attributes to sync, matched on item #. Held to partial because the source of truth is another location's product record rather than a corporate menu object, syncable types are a fixed list, and no publish or version history recording what was pushed, when and by whom is documented; talech itself warns of sync issues across locations. source |
| multi-location-price-zones | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-no | Per-location pricing is achieved by duplication, which the claim explicitly excludes: sync creates a separate product record at each site and differing prices come from de-selecting price among the synced attributes. There is no location group, no channel price book, and no daypart price schedule in the product pricing fields (Enable Variable Pricing, Cost, Markup %, Price). source |
| hardware-offline-mode | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | talech publishes offline scope explicitly in three named buckets, which satisfies the documentation half of the claim. Order creation and cash/check tender are fully supported; card auth, refunds, gift/store credit, reports and customer list are named as unavailable. Held to partial because kitchen printing appears in none of the three buckets and offline orders live only on the creating iPad, with cross-iPad order syncing explicitly unavailable. source |
| reliability-offline-order-entry | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | Create/save open orders and local pre-authorisation are listed as fully supported offline, and table layout can create new orders. Held to partial because the vendor's offline list never addresses ticket routing to kitchen printers or check printing, and offline orders are single-device only with order syncing between iPads explicitly listed as unavailable. source |
| reliability-printer-fallback | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-no | The complete printer settings reference - global advanced, per-printer, order-ticket advanced and receipt advanced - contains no backup printer designation, no failover on an unreachable printer and no staff alert. The only routing override is the manual per-device Order Ticket Exclusion List, which deliberately blocks a printer rather than failing over to one. source |
| order-capture-offline-order-entry | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | The vendor publishes offline scope explicitly, in three labelled buckets, which is half of what this claim asks for. Order creation and cash/check/other tender are in the fully-supported bucket, along with local pre-authorisation and PIN sign-in. Held short of yes on two named shortfalls: orders 'are only stored on the iPad that created the order' and 'Order syncing between different iPads' sits in the no-access bucket, so on any multi-terminal floor the check state fragments during an outage; and sending items to the kitchen appears in none of the three buckets, so offline kitchen printing is simply not addressed by the published scope. Card transactions, refunds, reports and menu editing are all listed as unavailable. source |
| kitchen-station-routing | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | Self-serve routing is documented step by step: kitchen printers are assigned Categories and/or Tags in Back Office > Settings > Printers, and 'the items in that order will go to printers based on their Tag(s) or Category'. No vendor involvement is required and the assignment is per printer per location. Two shortfalls keep it off yes: the routing target is a printed kitchen receipt rather than a KDS station - no kitchen display exists in the product, and the 269-article help-centre sitemap has no KDS article - and the only routing keys are product Tag and Category, so order type and revenue centre cannot drive routing. source |
| inventory-recipe-bom-costing | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | There is a real but single-level BOM. Bundles and assemblies hold components with per-component quantities and deduct component inventory - the bundle at sale, the assembly at build - and component sets can differ per variation. What the claim asks for beyond that is absent from a walkthrough that covers both the Register and talech.com paths end to end: components are always products, never another bundle or a prep item, so there is no sub-recipe level; and there is no plate-cost object, cost existing only as the per-product Cost and Markup % fields, with bundle price entered by hand and the assisted figure computed from component price rather than cost - nothing recalculates when an ingredient cost moves. talech's own guidance for yield conversion is to divide by hand and type the result. source |
| reporting-realtime-dashboard | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-partial | talech.com carries a documented Dashboard giving 'a quick overview of the health of your business without having to open multiple reports', off-premise in a browser, with hour-level grouping on a single-day range. It falls short of the claim on both remaining halves. The mobile half is contradicted by talech's own mobile guide, which lists reports as 'Available in the talech.com account' and tells the operator to 'access your account online by going to talech.com on a tablet or desktop device' for reports - the phone POS app has no dashboard of its own. The latency half is unestablished: no refresh interval is published anywhere, the dashboard is framed as 'daily or weekly monitoring', report subscriptions run no faster than weekly, and the one stated latency in the corpus is cash drawer reports 'updated nightly'. source |
| labor-clock-in-at-pos | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-yes | A dedicated Employee Timeclock article documents the full flow on the POS itself: employees type the PIN assigned during setup on talech.com and select Clock in, a confirmation banner appears on the register screen, and clock-out is the red dashboard button plus PIN with a break option and a shift-hours printout. Hours feed the Labor Cost report automatically. No separate time-clock hardware is involved anywhere in the flow, and the claim's credential list (PIN, badge, or card) is satisfied by the PIN. source |
| delivery-driver-roster | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-no | The delivery capability is enumerated in full as an online-order type - toggle, payment options, order amount limits, one delivery radius - and no driver object exists anywhere around it: no driver permission among the ~25 in the permissions breakdown, no assignment state in the generic PIN timeclock flow, no per-driver report in any of the report catalogues, and no driver or dispatch article among the 269 in the live sitemap. Third-party delivery orders must be keyed in manually. This is the same complete-enumeration evidence that resolved delivery-dispatch-board to no; a first-class driver entity with clock-in/out, run state and run history has no place in the documented model. source |
| hardware-kds | unknown (grade F) - placeholder rationale "No public documentation located during the 2026-08-01 research pass", i.e. the cell was never examined. | resolve-to-no | Kitchen output is documented as printed receipts routed by Tag/Category, dispatched with the Send button; the complete printer reference enumerates every setting with no display device, the only screens in the product are customer-facing displays, online ordering's top automation auto-sends 'to the kitchen' for stores 'equipped with kitchen printers', and the 269-article sitemap contains no KDS article. Consistent with the already-resolved kitchen-expo-consolidation and kitchen-bump-bar-hardware cells: there is no first-party KDS, so bump-bar input and course/fire timing cannot exist. source |
Sources
Every URL this record cites. 41 in total.
- https://www.usbank.com/business-banking/payment-solutions/in-person-payments/point-of-sale.html
- https://help.talech.com/s/article/Product-Modifiers
- https://help.talech.com/s/article/Variations-vs-Modifiers
- https://help.talech.com/s/article/Creating-and-Editing-a-Product-on-talech-com-new
- https://help.talech.com/s/article/Product-Variations-new
- https://help.talech.com/s/article/Managing-Orders-in-Offline-Mode
- https://help.talech.com/s/article/Employee-Permissions-Breakdown
- https://help.talech.com/s/article/Entering-Overrides-for-Voids-Discounts-or-Returns
- https://help.talech.com/s/article/Voiding-an-Item
- https://help.talech.com/s/article/reports-operation-finance
- https://help.talech.com/s/article/reports-products-services
- https://help.talech.com/s/article/reports-payments
- https://help.talech.com/s/article/iPad-Understanding-Summary-Reports
- https://help.talech.com/s/article/Cash-Drawer-Management
- https://help.talech.com/s/article/Cash-Drawer-Summary-Reports
- https://help.talech.com/s/article/Multi-Location-Accounts-new
- https://help.talech.com/s/article/Multi-location-product-sync-new
- https://help.talech.com/s/article/Online-Ordering-Settings
- https://help.talech.com/s/article/Online-Ordering-Features-and-Functionality
- https://help.talech.com/s/article/Online-Ordering-End-to-End-Experience
- https://help.talech.com/s/article/manage-oo
- https://help.talech.com/s/article/Show-or-Hide-Products-for-Online-Ordering
- https://help.talech.com/s/article/talech-Gift-Cards
- https://help.talech.com/s/article/Gift-Card-Requirements
- https://help.talech.com/s/article/customer-loyalty-program
- https://help.talech.com/s/article/talech-Customers-feature-new
- https://help.talech.com/s/article/Download-Customer-List-new
- https://help.talech.com/s/article/Printers-Setup-Printers-to-Create-Kitchen-Receipts
- https://help.talech.com/s/article/Printers-General-Advanced-Settings
- https://help.talech.com/s/article/Printer-Settings-FAQ
- https://help.talech.com/s/article/Creating-Product-Bundles-and-Assemblies-new
- https://help.talech.com/s/article/Sales-Unit-Inventory-Volume-For-Poured-Drinks-For-a-Keg-or-Bottle-from-Dashboard
- https://help.talech.com/s/article/integrations
- https://help.talech.com/s/sitemap-topicarticle-1.xml
- https://help.talech.com/hc/en-us/articles/218019803-Requesting-API-Access
- https://help.talech.com/hc/en-us/articles/205011699-How-do-I-create-and-send-a-campaign-
- https://help.talech.com/s/article/Reports-on-talech-com
- https://help.talech.com/s/article/reports-sales-trends
- https://help.talech.com/s/article/talech-mobile-overview-guide
- https://help.talech.com/s/article/Report-Subscriptions-from-talech-com
- https://help.talech.com/s/article/Employee-Timeclock